Enterprise Resource Planning Blog Posts by SAP
cancel
Showing results for 
Search instead for 
Did you mean: 
FabianAckermann
Product and Topic Expert
Product and Topic Expert
898

With SAP S/4HANA Cloud Public Edition, customers benefit from regular upgrades and updates that bring the latest innovations, enhanced security, and improved performance. With SAP Central Business Configuration serving as the single entry point for scoping, organizational structures, and configuration activities, it is natural that upgrade cycles involve certain considerations within SAP Central Business Configuration.

Why Protective Measures Matter During Upgrades

Think of these measures as the safety rails on your system. By locking down critical operations (transports, data migrations, extensibility) during upgrade windows, SAP ensures the upgrade process can run smoothly without unintended side effects − protecting the system from half-done changes or version mismatches.

With SAP rolling out major upgrades twice a year (typically in February and August) and regular updates (hotfix collections) every two weeks between major upgrades, having a clear restriction schedule allows customers to adopt innovations in a controlled, manageable way. For more information on the schedule, please refer to:

Protective Measures and Best Practices

  • Keep your team well informed about upcoming upgrade cycles.
  • Avoid initial activation around upgrade time, as it’s typically time consuming.
  • Avoid large deployments to prevent stuck deployments or partial content activation.
  • Perform business configuration activities until 8 hours before system downtime.
  • Make changes to your scope or organizational structure up until the content upgrade begins.
  • For the parallel line, avoid initiating rebase and merge before the upgrade starts, as these actions lock the workspace.
  • Avoid scheduling critical go-lives and User Acceptance Testing (UAT) around upgrades.
  • For the 2-system landscape, in addition to the above, avoid releasing transport requests from the quality system to the production system.

SAP Central Business Configuration Impacts

Let’s look at how the SAP Central Business Configuration system behaves during these system upgrades.

1. During Update: Here’s the update maintenance schedule for the SAP S/4HANA Cloud Public Edition, 3-system landscape:

Update windows and time of workspace locking per regionUpdate windows and time of workspace locking per region

  • Please note that deployments are automatically locked 12 hours before the software update starts, aligning with the timing of the Major Upgrade Window (MUW).
  • Business configuration activities can be performed until the system enters downtime.
  • Organizational structure updates, scope extensions, and new country activations are allowed until the content update begins and the SAP Central Business Configuration workspace becomes locked. 

2. During Upgrade: Here’s the upgrade maintenance schedule for the SAP S/4HANA Cloud Public Edition, 3-system landscape:

Upgrade windows and time of workspace locking per regionUpgrade windows and time of workspace locking per region

  • Please note that deployments are automatically locked 30 hours before the software upgrade starts, aligning with the timing of the Major Upgrade Window (MUW).
  • Business configuration activities can be performed until 12 hours before the system enters downtime.

Organizational structure updates, scope extensions, and new country activations are allowed until the content update begins and the SAP Central Business Configuration workspace becomes locked.

References
To learn more, check out the following resources:

That wraps up the new features this time. Did you like this blog? If so, please leave us a thumbs up at the top. Also, make sure to follow the SAP Central Business Configuration tag or follow this dedicated blog collection to stay up to date with the latest blog posts.