Transport Depency Trace

Question

Hi,
We have around 30 TR (across FICO, HR & Logistics module). Due to poor TR management list by project, we are not able to identify the sequence & DEPENDENCY of the TRs manually.
Are there any methods we can use to ensure the TRs sequenced with dependencies correctly before proceeding for transport?
Thank you.

Answer 1

Hello Raj,
unfortunately, there isnu2019t any transaction available to check the dependencies between objects in transport requests.
Actually finding out the dependencies and the correct order to be imported can be very time consumingu2026
If the requests have been already released, you can check in table E071 if the same object has been included in more than one request; if an object can be found in several requests, the next step would be to find which is the correct order (that is, which request should be imported first). This is a little bit more complicatedu2026 if the object is a program, function module, etc. you can check the version management of that object (in the development system), there you will find which transport request contains the latest version of the object and, therefore, which transport request must be the last one in the import sequence.
There's also a table which the TMS mechanism uses to cross check objects within two or more requests: table E070DEP  ("Change & Transport System: Dependencies of Requests").
Are they using Projetcs to control the transport requests? If you use projects to control your transports, but your projects overlap, then you must define dependency relationships between the objects that belong to different projects but contain some of the same objects. As per your problem description, this step was either missing or has failed.
FYI, when you import requests, the system analyzes the dependency relationships and lets the transport administrator know that more requests have to be imported to ensure the correct sequence. This is just a warning though, and the import can be continued.
Also, when you release a request, the system automatically checks whether the request's object list overlaps with the object lists of released requests from other projects that have already been released. But again, this is a warning and you can proceed if you wish w/o taking any action.
I hope this information helps.
Best regards,
Tomas Black