This new ShiftLeft Analyser enables you to indicate what other transports in a TE path contain the same objects as those contained within the transport(s) being analysed. It was requested by a few existing customers that want to stop new versions being imported into a system until an older version that had already been imported into that system had been tested and moved forward.

The analyser can look for the object in other transports i) Forward, ii) Backward or iii) Forward and Backward in the TE path, depending on how the exact requirement

Note that another ShiftLeft analyser “Changes to same objects” can be used to identify other transports containing the same object(s) in the same control point.

Configuration Steps


CHECK_BACK_AND_FORWARD: Define whether you want to look only Forward, only Backward or both Backward and Forward in the Path.

IGNORE_SAME_TASK: Can be used if you want to ignore other transports assigned to same Business Task that contain the same object(s).

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.


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