Transport Case mixing up clients: Source objects form different clients are imported into one destination client

Document ID : KB000087340
Last Modified Date : 14/04/2018
Show Technical Document Details
Issue:
Error Message :
N/A

The Transport Case is mixing up clients: Source objects form different clients are imported into one destination client.

In case a Transport Case contains objects from different clients, the objects should be loaded to the corresponding client in the destination system (if not specified differently).

So objects from client 1 should be loaded into client 1, objects from client 2 should be loaded into client 2, and so on.


However the DB Load mixes up the clients and all objects are loaded to the same client.
 
Investigation
 
3 objects in 3 different clients are unloaded to one transport case (TC):
0EMb0000001Fd9g.png
 
After loading the TC to another system it looks like this:
0EMb0000001Fd9l.png
 
The log file of the Load Utility shows that the wrong client was used:

 
20171005/103459.324 - U00021126 Client '1977': Importing object 'JOBS.WIN.TRANSPORT_1977' of type 'JOBS'.
20171005/103459.857 - U00021126 Client '1977': Importing object 'JOBS.WIN.TRANSPORT_0005' of type 'JOBS'.
20171005/103500.033 - U00021126 Client '1977': Importing object 'JOBS.WIN.TRANSPORT_0000' of type 'JOBS'.
 
 
Environment:
OS Version: N/A
Cause:
Cause type:
Defect
Root Cause: Bug in DB.Load: The Load Utility reads the client form the transport case correct. However, when inserting the object, always the same client is used.
Resolution:
Update to a fix version listed below or a newer version if available.

Fix Status: In Progress

Fix Version(s):
Component(s): DB Load Utility

Automation Engine - TBD
Additional Information:
Workaround :
Use the transport only for one client at one time.