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
SAP S/4HANA Cloud systems have the quarterly 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 Q to P transport process in capital "The Q to P transport process in detail" of the online help, and Summary of the Service Center Cutoff Dates (Calendar days) and Recommendation for other services request in order to include them before the Upgrade via our roadmap.
Q2P, transport, consistent version, inconsistent, Q system, P system, 2 weeks, SAP S/4HANA Cloud, SMC, SAP MARKETING CLOUD , KBA , SV-CLD-FRM-INF , Implementation Framework Infrastructure , CEC-MKT-BF , Basic Functions , Problem