Defining Dependency Relationships Between 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.
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.
In this graphic, requests Am , A n and A o overlap with requests B x and B z.
You are working withTransport Control Using Projects.
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.
If requests do contain the same object, the system identifies which requests the object was transported in. A dialog box proposes these requests as predecessors of the current request.
You can also edit the dependency information of a request yourself, and add predecessor and successor relationships independently of the system proposals. You can also create circular relationships, meaning that the requests have to be imported together.
To do this, go to the request overview in the Transport Organizer and choose Goto → Dependency information.
For more information, seeImporting All Requests in a Project.