3668048 - Different transport request IDs for the same software collection version in test and production systems - SAP S/4HANA Cloud Public Edition

• Different transport request IDs for the same software collection version in test and production systems.

• Manage and Import Software Collections
• SAP S/4HANA Cloud Public Edition

The system is functioning correctly, it's an expected behavior. It should not be concerned about the differences in transports between the test and production systems. To maintain consistency, always verify the key parameters 'Name' and 'Collection Version' for Key User Extensibility software collections. 

The reasons for this system behavior: 

During Export ATO checks whether the preceding version has already been deployed to production. If it has been, we send only one transport with all changed, new and deleted items in the collection. In any other case we send a second transport that contains all objects that had not yet been deployed to production. When the new collection version is registered in the target system (TST or PRD) ATO decides which transport to register depending on the import status of all preceding versions. This can differ in TST and PRD depending on the local situation.

Depending on the state of deployment in the respective system, the Import Collection app decides which of the two transports is needed for consistent deployment.

transport issue, sap s/4hana cloud public edition, key user extensibility tools, transport management, export software collection, transport request ID mismatch, software collection, import collection , KBA , BC-SRV-APS-EXT-SL , Manage and Import Software Collections , Problem