Tips for Strategic Regression Testing of Multiple Rollout Locations
- by Sapna N. Modi, SAP Business Unit Automation Lead, L&T Infotech Ltd.
- December 10, 2009
This guide can serve as a basis for regression testing for requirements that are specific to rollout locations under the umbrella of a large global rollout.
The SAP rollout concept is important for businesses operating across different geographic locations that have centralized, common operating functions in their SAP systems. A rollout ensures uniform operations as well as a global view of the business. This central view means analytics data is easily available. SAP Solution Manager reduces the rollout implementation cycle time with its project template, realization options, and testing reutilization capabilities.
After the headquarters or reference location goes live in your SAP system, you must plan the rollout to other locations. The rollout location usually copies about 80% to 85% of the functionality of the reference implementation. The remaining functionality meets local legal requirements and you cannot copy it. You need to plan for the testing of any functionality specific to those rollout locations.
Rollout location implementations follow the same ASAP roadmap as the reference implementation project. You can download the Web-based roadmap from SAP Service Marketplace (SMP login required). The system-based roadmap is available in SAP Solution Manager’s RMMAIN transaction. The ASAP roadmap phases are:
- Phase I: Local project preparation
- Phase II: Local business blueprint
- Phase III: Local realization
- Phase IV: Local final preparation
- Phase V: Local go-live and support
In this article, I concentrate on the first three phases in detail.
Would you like to see this full item?