Symptom
Transport request of type Central Business Configuration has status Modifiable and you're unable to release transport request due to dependencies.
OR
In Import Collection App, Collections are failed with status "Automation Import Validation Failed" and Error: Collection XYZ version depends on missing transport request XYZ.
OR
Transport Request of type Customizing Request has status "Request has Dependencies" and in the logs there's the following message: "Request depends on request XXXXX. Resolve dependencies or merge requests."
Environment
SAP S/4HANA Cloud Public Edition
Cause
Dependency checks may require you to release some transport requests in a specific sequence, to avoid import errors and inconsistencies in the target system. You should plan transports so that any dependencies are managed accordingly. It is not always possible to fix issues with transport dependencies by merging the transports, as transport requests of different types cannot be merged; they have to be released in the correct sequence instead. This is especially important when transports for reference content have dependencies to transports for business configuration. The transport without dependencies should be released first, and then the dependent transport.
Resolution
Requests of type Central Business Configuration:
To release those transport requests, maintain the sequence of the TR and check this dependency error by following the steps below:
- Go to the Export Customizing Transports app.
- Filter request type Central Business Configuration.
- Open latest TR which has status 'Request Has Dependencies'.
- Click on Log.
Follow the procedure and Release the TR "ZTXXXXXXXX" First, "ZTXXXXXXXX" --> The release order is 1 and so on
Take over the ownership of a request with the type of Central Business Configuration by selecting it and selecting Assign To Me.
To release the request
- Select the request and click Release > Execute.
- Select the request with the status Checking or Release Started and click Refresh.
Note: All Tasks of the request type Central Business Configuration must have the status released.
Requests of type Customizing:
As per procedure under "Request depends on request XYZ. Resolve dependencies or merge requests.":
There are several options to resolve the dependencies, depending on their nature:
- If there are only dependencies in one direction, release request XYZ first.
-
- In case that the entries which create dependencies are located on multiple requests, it is sufficient to release one of these requests
- If there are interdependencies between the requests, merge current request with request XYZ and release all the changes together.
- If request XYZ is not ready to be released and there are only few dependencies, add the entries causing the dependencies from request XYZ to the current request.
For merge, check Managing Customizing Requests | SAP Help Portal > Merge Request.
Dependency related to Key User Extensibility:
If any TR shows a dependency related to key user extensibility (e.g., dependency of TABU T685 on the extension item CT_ACC_SEQ YY1_XX ZXX), export the item YY1_XX ZXX from the customizing tenant first.
Steps to Export Key User Extensibility Items:
- Open the Extensibility Inventory app.
- Search for the item (e.g., YY1_XX ZXX).
- Click on Change History to check if the item is part of any software collection.
- If a collection exists (e.g., YY1_)
- Copy the collection name.
- Go to the Export Software Collection app.
- Search for the collection (e.g., YY1_).
- Click Add Item and then Export the collection.
- Once the key user extensibility item is exported, return to the Export Customizing Transports app and attempt to release the transport request again.
See Also
Keywords
Export Customizing Transports, Central Business Configuration, CBC TR, Transport request, Request Has Dependencies, Modifiable, request type Central Business Configuration, S4_PC, S4_1C, X4BC , KBA , BC-SRV-APS-EXT-SL , Manage and Import Software Collections , BC-CUS-TOL-CTO , Export Customizing Transports App , How To