When a transport is imported into a merge target system a merge transport of copies will be created in the target system. This will be a new local transport in the merge system with a copy of all the objects from the original transport in it.

All merges into each system will be appended to an open merge request until it is released. This means that a single merge transport can have many source transports attached to it.

Merge transports are named in TE as follows:
Merge request for 5 request(s) : 20141105: 185204

The merge transports need to be released before being moved down the relevant transport paths:

Notes for BI/BW merges:

  • The merge process works by adding all objects from the original source transport to a local transport of copies. As BI renames some object types to local system names when they are imported, the objects in the merge transport are also renamed automatically by TE
  • If the import of the transport into the merge development system has any import errors the renaming process by TE will not always work as some of the objects won’t have been successfully imported yet. It is therefore important to fully address these issues and re-import the source transport so that the merge transport can be fixed by TE before it is released

The Related Merge Requests tab in the transport forms shows either the related merge transport or, for the merge transport itself, it shows the original source transports:


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