2791664 - No transports are allowed during software upgrade

No transports are allowed from Q system to P system in the two weeks where the P system is not at the same release as the Q system.

SAP S/4HANA Cloud Public Edition (2-System Landscape only)

SAP Central Business Configuration (2-System Landscape only)

SAP Marketing Cloud

SAP S/4HANA Cloud Public Edition systems have half year software upgrade. New functionality is delivered each quarter and requires action to keep the process flowing smoothly. The upgrade dates are not flexible, and all customers are upgraded during the same weekends.

The Q-System will be upgraded first. Then, two weeks later, the P-System will be upgraded. During the time between the Q and P upgrades, regression testing occurs.

If the P-system has not been provisioned, it must be requested at least 15 days prior to the Q-system upgrade so that both the P and Q-systems are on the same base release.

Beginning with the upgrade preparation, no extensibility development can be carried out. In the two weeks where the P system is not at the same release as the Q system, no transports are allowed.

You can learn more about the upgrade and maintanence schedule in below documentation:

• 2825498 - Planned Maintenance Timelines for S/4HANA Public Cloud and Marketing Cloud System
• Release Upgrade Timeline, Best Practice and FAQ.pptx (SAP Customer)

• Prepare for Quarterly Upgrade
• 2825498 - Planned Maintenance Timelines for S/4HANA Public Cloud and Marketing Cloud System

Q2P, transport, consistent version, inconsistent, Q system, P system, 2 weeks, SAP S/4HANA Cloud Public Edition, SMC, SAP MARKETING CLOUD, CBC, Central Business Configuration, 2SL. , KBA , period , SV-CLD-FRM-INF , Implementation Framework Infrastructure , X4-CBC-PRX , Consumption - Project Experience , CEC-MKT-BF , Basic Functions , Problem