2707813 - SAP S/4HANA Cloud Public Edition: Configuration Transport import time to P system

A Business Change Project was created in the Q-system, the required configurations were completed and added to the project. The release also went smoothly, no issues were detected after clicking "Proceed to Run" or "Proceed to Deploy" button.

After the successful completion, the transported data is not visible in the SSCUIs in the P system immediately.

 SAP S/4HANA Cloud Public Edition

The change project will be queued for transport into the P system and not imported straightaway.

Transported configurations/data will be imported to the P system approximately at 11 pm of the system’s data center time. The duration time depends on the amount of the transported data, but should not exceed 1 hour.

If this is not acceptable and the immediate, emergency import is needed to P system, please follow the process on the Activate Roadmap Execute Configuration Transport Sprints.

More information regarding SAP S/4HANA Cloud Public Edition Data Center Locations and availability can be found at SAP Cloud Trust Center.

Q2P, BCP, CBC, MYS, execute, framework, master data, config, display, Manage your solution, Configure your solution, Self-Service-Configurations-UI, Import Collection, Proceed to Run, Export Software Collection
, KBA , SV-CLD-FRM-APP , Flexorg, Foreign Key Check , SV-CLD-FRM-INF , Implementation Framework Infrastructure , SV-CLD-SSC , Self-Service-Configurations-UI , Problem

SAP S/4HANA Cloud Public Edition all versions ; SAP S/4HANA Cloud all versions