
As the SAP's enterprise cloud software landscape continuously evolves, it is of paramount importance to harmonize the landscape for all the customers. 3-System landscape conversion program is thus one of SAP’s strategic programs.
The 3-system landscape (3SL) architecture provisions three systems—Development (D), Test (T), and Production (P)—to customers. This separation facilitates advanced development projects and enables developer extensibility options, leveraging SAP Central Business Configuration (CBC) to configure business processes within SAP S/4HANA Cloud Public edition. CBC’s objective is to allow the customer to implement end-to-end business processes across the intelligent enterprise from a central place.
Historically, SAP S/4HANA Cloud installations were based on a 2-system landscape consisting of a Quality and a Production system. Some of these SAP S/4HANA Cloud Public edition customers utilized the solution builder framework via the “Manage Your Solution” app while others have access to CBC to configure their business processes. The 3SL/CBC Conversion program aims to transition all 2SL customers to 3SL/CBC.
Upon conversion, customers must take a few steps to ensure their new test system resembles their current quality system. Two critical steps include:
These steps traditionally involve tedious manual copying of communication arrangements, systems, and users. Additionally, the new test system provided to customers lacks master and transactional data which to some customer offers a chance to load clean master and transaction test data but to the others involves manual steps to migrate data from their development system.
To address these challenges, SAP has developed two key services: the Cloud Integration Automation Service (CIAS) and the Test Data Conversion (TDC) Service.
The CIAS re-wiring procedure guides customers through a workflow-like process to select source and target systems. It then automatically copies communication arrangements, systems, and users, eliminating much of the manual work. This automation not only saves time but also reduces the risk of errors, ensuring a smooth transition to the new system.
The TDC service ensures business continuity by transferring historical test data from the development system's customizing tenant to the new test system. This includes test automates, number ranges, multi-bank connectivity, and output management settings. By automating the transfer of master and test transactional data, TDC enables seamless testing in the new environment, allowing customers to continue their operations without interruption.
In summary, the Cloud Integration Automation Service and the Test Data Conversion Service streamlines processes, reduces manual workload post conversion to 3SL.
Thank you Calin Cernea for your contributions and leading the workstream to enable these innovations.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
User | Count |
---|---|
7 | |
6 | |
5 | |
4 | |
3 | |
3 | |
3 | |
3 | |
2 | |
2 |