Skip to Content

To simplify the adoption of SAP S/4 HANA into our day to day business SAP Best Practices play an important role. They provide Pre-configured, ready to run business processes which include core business processes with role specific, responsive and simple user experience thus making the on-premise and cloud editions faster time to value.

As the name suggests Best Practice Execution for S/4 HANA offers the Quality and validation for the Cloud Editions. It provides the quality assurance for the SAP Best practice process to see whether a product or service being developed is meeting specified requirements or intended purpose. Best Practice Execution increase our customer confidence and company’s credibility, to improve work processes and efficiency, and to enable our organization to better compete with others. Best Practice Execution offers check for both Globalized and Localized scope items.

Our team supports 3 releases for cloud editions of S/4 HANA.

Nth release

(N-1)th release

(N-2)th release

In nth release or we can say development release we test scenarios from P2D (Planning to Development) to ECC (Emergency Correction Close). Between P2D to DC we usually do takt regression testing for once in every takt. Between DC to ECC which is known as release phase we perform testing for both global templates as well as localizations.

During takt regressions, testing is done only for unchanged scenarios while during the release phase testing is performed for both changed and unchanged scenarios.

Moving on to (N-1)th release, this phase usually falls between ECC and RTC (Release to Customer). The main area of interest during this phase is testing of Hotfix Collections where all scenarios for the Global templates are validated. We validate the scenarios once in two Hotfixes (Every 15 days a Hotfix is released to customer).

Apart from Hotfixes our team also contributes towards validation of scenarios for up-selling and Q2P testing which is purely on demand with limited scope.

(N-2)th release

In this particular release we extend our support from RTC to EoM (End of Maintenance). Similar to (N-1) release here also we validate Hotfix collections for (N-2) release. This activity goes on till end of maintenance of that particular release of cloud edition.

Hence we support from the planning phase of a cloud edition release till its end of maintenance and validate all the scenarios whether it is globalization or localization via all test types (Hotfix, Up-selling, Q2P, Takt, Release)

To report this post you need to login first.

Be the first to leave a comment

You must be Logged on to comment or reply to a post.

Leave a Reply