• Overtake: Does the transport contain a newer version of any objects that also appear on older transports that have not yet been imported into the target system?
    If so, when the older request is imported in future you risk overwriting the target system objects with old out of date versions.
  • Regression: Does the transport contain an older version of any objects that have been previously imported into the target system?
    If so you risk overwriting the target system objects with old out of date versions.

Parameters:

KEY_NO_RELATED_VIEWS: By default, when transporting table entries, views that use the same table in key fields will be considered a conflict. This behaviour can be turned off with this flag.

KEY_NO_WILDCARDS: If this flag is set, wildcards are not considered when searching for conflicting table entries.

NO_CACHE: Turn off conflict cache (always recalculate the conflicts from the actual object lists).

SHOW_CONFLICTING_OBJ_KEYS: Show the actual table entries that are in conflict. (This is not purely display but can have performance implications since when you don’t show the keys, you can stop at the first conflict, but otherwise it needs to go on.)

Feedback

Was this helpful?

Yes No
You indicated this topic was not helpful to you ...
Could you please leave a comment telling us why? Thank you!
Thanks for your feedback.

Post your comment on this topic.

Post Comment