Enterprise Resource Planning Blogs by SAP
Get insights and updates about cloud ERP and RISE with SAP, SAP S/4HANA and SAP S/4HANA Cloud, and more enterprise management capabilities with SAP blog posts.
cancel
Showing results for 
Search instead for 
Did you mean: 
zeynepengland
Product and Topic Expert
Product and Topic Expert
4,254

The SAP S/4HANA Cloud 2502 release is around the corner! As part of SAP’s commitment to delivering two major upgrades per year, it’s essential to take the necessary steps to ensure a smooth transition. Since upgrade dates are fixed and apply to all customers simultaneously, being prepared is the key.

Key Milestones:

  • The Q-System will be upgraded first, and the P-System will follow. 

  • Regression testing occurs during the interim period.

 

I have been supporting S/4HANA Public Cloud customers since 2017 as a Customer Success Manager and here are the top 5 steps to keep in mind to make this process seamless:

 

1. Review the Release Notes

Stay informed about the latest features, enhancements, and changes in the S/4HANA Public Cloud 2502 release by reviewing the release notes.

 

2. Check Business Roles in Your Q-System

Some Business Catalogs will be deprecated and replaced with new ones or renamed. Deprecated catalogs will be removed two releases later. To stay ahead:

  • Regularly review retired Business Catalogs and any new scope items.

  • Make sure to favorite the SAP Note 3533745 to stay up to date with changes. There is an excel file attached to the note which explains the changes.

  • Implement necessary changes promptly to ensure continuity.

 

3. Test Your Existing Business Processes

Conduct regression tests in your Q-System immediately after the upgrade. For efficient testing:

  • Utilize the Test Automation Tool for SAP S/4HANA Cloud to automate test scripts of your end-to-end business scenarios

  • If you opted for Post Upgrade Test (PUT), then SAP executes these smoke tests based on the active scope you have on your behalf as a means of helping you identify as early as possible where there may be regression issues to resolve. This is an optional free service that you can sign up

  • Refer to Testing in S/4HANA Cloud for more information.

  • Manually test the following:

    • Output management/forms

    • Business role/authorizations

    • Analytics

    • Interfaces

    • Extensions

    • Scenarios utilizing expert configuration are not covered by standard automated test scripts. Depending on the business process, your own automated test scripts can be created.

 

4. Create Regression Tickets

If defects are identified during regression testing, report them promptly via the SAP for Me platform.

  • Include ‘[R]’ in the Subject to indicate issues related to Upgrade Regression Testing.

  • These tickets are prioritized, ensuring faster resolution and code fixes.

 

5. Move the change project

During the interim period between the Q and P upgrades, your Q-System and P-System will have different code bases, halting transport changes.

  • It is recommended to move existing business change projects (BCP) to P using the Q2P transport process latest the Wednesday prior to the Q-System upgrade.

  • If you plan to extend the scope ( activate a new scope item or country), make sure you plan testing and activation accordingly.

 

Register for 2502 Early Release Webinars: Want to explore the new features more deeply? Register for the webinars tailored to each Line of Business (LOB).

Is there any other steps that you would add? Let me know in the comments or send me a message!

2 Comments