3547695 - Export Customizing Transports - Frequently Asked Questions - SAP S/4HANA Cloud Public Edition

Export Customizing Transports - Frequently Asked Questions

SAP S/4HANA Cloud Public Edition

1. User is not able to release a transport request.

1. SAP_CORE_BC_BCT_TRN_REL_PC (3414407 - Basic Information on Export Customizing Transports App - SAP for Me).
2. Transport request needs to be assigned to the user (Managing Customizing Requests | SAP Help Portal > Assign To Me).
3. All tasks need to be released (Managing Customizing Requests | SAP Help Portal > Release Request).

   

2. User is not able to create new transport requests/tasks:

Refer to the following documentation:

• Flexible Transport Mode and Simple Transport Mode  
• Simple Transport Mode in 3-System Landscape Transport Management in S/4HANA Cloud Public Edition

   

3. Error "Dependency of TABU T685 to extension item CT_ACC_SEQ YY1_XYZ ZXYZ. Export the item first."

User needs to export item YY1_XYZ ZXYZ from customizing tenant first.

The Extensibility Inventory application can be used to search by key user extensibility items, i.e. YY1_XYZ.

It is possible to check whether the item has been included in a software collection by checking the Change History.

If the item hasn't been included in a software collection yet, user needs to use the Export Software Collection application to include this item in an existing software collection or create a new one.

Once the key user extensibility item of type "Condition Technique Access Sequence" is exported, it should be possible to release the transport request from Export Customizing Transports application.

3532828 - "Dependency of TABU T685 to extension item CT_ACC_SEQ YY1_xxx. Export the item first." error displays, when releasing transport in app Export Customizing Transports - SAP S/4HANA Cloud Public Edition - SAP for Me

  

4. Error "Dependency of TABU APOC_C_FORM to extension item OM_FM_TMPL YY1_XYZ. Export the item first"

User needs to export item YY1_XYZ from customizing tenant first.

The Extensibility Inventory application can be used to search by key user extensibility items, i.e. YY1_XYZ.

It is possible to check whether the item has been included in a software collection by checking the Change History.

If the item hasn't been included in a software collection yet, user needs to use the Export Software Collection application to include this item in an existing software collection or create a new one.

Once the key user extensibility item of type "Custom Form" is exported, it should be possible to release the transport request from Export Customizing Transports application.

   

5. "Request depends on request XYZ. Resolve dependencies or merge requests."

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 more information about dependencies, please refer to Transport Dependencies | SAP Help Portal

Managing Customizing Requests | SAP Help Portal > Merge Request.

3462787 - Transport Request has status "Request Has Dependencies" in Export Customizing Transports app

   

6. "Tax code XYZ for procedure XYZ is open in transport request XYZ". "Tax code XYZ in country/region XYZ exists in open transport request XYZ". "Veto Check message was issued by application component FI-GL-GL-F."

Refer to 3359506 - Error FOT_TDT121 in export customizing transport - SAP for Me

   

7. "Referencing task XYZ not yet released"

Release any tasks belonging to your request. A request can't be released until all its tasks have been released.

Refer to Managing Customizing Requests | SAP Help Portal > Release Request

   

8. "The request will depend on request XYZ in import system."

This is an information message. User can still release the transport request that is throwing this message but it will be required to import it along with this transport request in the target system.

    

9. "Release the following CBC transports in the correct sequence" and "Release of XYZ not allowed. Release predecessor CBC transports first".

While trying to release a transport request, the following errors appear.

Release the following CBC transports in the correct sequence.
Please release CBC transport XYZ2 first. The release order is 1.
Please release CBC transport XYZ3 first. The release order is 2.
Please release CBC transport XYZ4 first. The release order is 3.
Release of XYZ1 not allowed. Release predecessor CBC transports first.
Request consistency check ended with errors.
Release check for request XYZ1 started in background

Central Business Configurations transport requests must be exported and imported in a strict sequence. If one of the transports contains unwanted content, the unwanted content must correct/remove and transport it in a later request that is imported at the same time.

Refer to the following documentation:

Transports | SAP Help Portal

    

10. "Request depends on request XYZ. Resolve dependencies or merge requests."

Refer to 3560339 - Resolving transport dependencies by modifying the original customizing request - SAP for Me 

    

11. "Transport the BP ID Category XXX for BP ID Type XXX" (Message no. MD_BP057)

Refer to 3501263 - Transport the BP ID Category XXX for BP ID Type XXX - Export Customizing Transports app in S/4HANA Cloud. - SAP for Me 

     

12. After releasing a transport request, the status of the transport request is "Request Has Dependencies".

Refer to 3462787 - Transport Request type Central Business Configuration has status "Request Has Dependencies." - SAP for Me

     

13. Why "Move" and "Delete" options are disabled for a customizing transport task?

Transport requests having attribute Semantic Business Configuration Locks (SAP_SBCL_CONTROLLED) have move and delete options disabled. 

   

14. is it possible to merge a Central Business Configuration transport request with a customizing transport request?

No, merge is only possible between transport requests of the same type.

15.Error "Export for transport type CBC is locked. No target System available." displays when releasing a TR using app Export Customizing Transports.

Refer to 3523296 - Error "Export for transport type CBC is locked. No target System available." displays when releasing a TR using app Export Customizing Transports- SAP S/4HANA Cloud Public Edition - SAP for Me 

Export Customizing Transports, Release transport request, dependency, task, release, , KBA , BC-CUS-TOL-CTO , Export Customizing Transports App , BC-SRV-APS-EXT-SL , Manage and Import Software Collections , Problem

SAP S/4HANA Cloud Public Edition all versions