Conflict Analysis (0035) checks if the transport contain objects that have also been changed on the target system. This is used for conflict analysis when moving from one system to another (e.g. when merging from a production support development path to a project development path).
Parameters
| Parameter | Description |
|---|---|
| COMPREHENSIVE | If set, the analyser will report on all conflicts and objects. |
| EXCLUDE_MERGED | if set, the analyser will ignore any conflicts before last merge. |
| EXCLUDE_TOC | if set, the analyser will ignore any conflicts with Transport of Copies. |
| GLOBALMERGECHECK | By default, only transports that originate in the target system are checked for conflicts. If this flag is switched on, then all transports in the target are checked, regardless of their original system. There is a potential performance downside to having this functionality active. |
| SHOW_CONFLICTING_OBJ_KEYS | If set, the analyser will show the actual table entries that are in conflict. This is purely display but can still 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. |
| UNRELEASED_TRANSPORT_CHECK | If set, the analyser will also indicate in the results whether the conflicting transport is released or not. |
| USE_CACHE | If set, the analyser uses cached results, otherwise it is always recalculated. |
Post your comment on this topic.