With the approaching end of support for SAP ECC in 2027, many SAP teams are gearing up for a transition from ECC R/3 to ECC S/4 HANA. While a Greenfield, new build approach is an option, most SAP users opt for a Bluefield or Brownfield transition, especially those with significant investments in custom code and proprietary business processes.
S/4 Transition Landscape Architecture
A dual system landscape is typically set up for a Bluefield or Brownfield transition to properly introduce and test existing ECC processes and code on the new S/4 platform. This involves creating a copy of the production (PRD) system for the new S/4 development (DEV) system and usually another copy for the test (TST) system. Meanwhile, ECC BAU (Business As Usual) support continues within the existing ECC landscape, while the transition to the S/4 HANA platform takes place in the newly created S/4 HANA landscape.
Figure 1 S/4 HANA Landscape Setup
A three-step process is typically followed to prepare the dual landscape systems, although not necessarily in the same order; the steps include: Copy, Mask, and Reduce.
Figure 2 S/4 System Setup Process
Security
Security is a crucial consideration, as the copied systems from the PRD system contain production data that may be sensitive and "at risk." Since DEV and TST systems cannot be shielded from developers or testers during the transition process, data anonymization is required to protect sensitive data.
Sizing
Another essential aspect is sizing, as SAP PRD systems often contain large amounts of data, sometimes up to 10TB or more, that is not necessary for development or testing. Unless anonymized, this replicated data poses risks, and it is impractical to run a DEV or TST system with all the production data. Therefore, data reduction is necessary.
Specialized Toolsets
Specialized toolsets offered by various software vendors, including SAP, can help with the copy, masking, and reducing process. While third-party tools may come at a higher cost, many users report that they are more automated, simpler to use and administer, and provide more flexible outcomes than SAP-provided tools. One such suite of tools is the Libelle DataSuite (LDS) from Libelle AG.
Libelle DataSuite (LDS)
The Libelle DataSuite is a framework that houses a range of tools designed to assist SAP basis teams in managing SAP systems and data. For the use cases discussed above, the suite includes three tools that can be used as a uniform solution for the copy, masking, and reducing exercise.
Libelle SystemCopy
Libelle SystemCopy (LSC): An end-to-end SAP system copy automation tool that fully automates pre-check and post-copy tasks, ensuring a fault-free homogeneous system copy. LSC speeds up the copy process and ensures consistency that may be hard to achieve with manual processes or other semi-automated tools.
Libelle DataMasking
Libelle DataMasking (LDM): Anonymizes selected Master Data as part of the LSC post-copy process, rendering it safe for exposure to the S/4 project team. LDM uses proprietary algorithms to transpose actual data into realistic fictional data, suitable for testing and analysis but useless for other purposes.
Libelle DataReducer
Libelle DataReducer (LDR): Automatically reduces the amount of data as part of the LSC post-copy process because LSC produces an exact, homogeneous copy of production data.
Figure 3 Libelle DataSuite SystemCopy Process
Final Word
By leveraging specialized tools like the Libelle DataSuite, SAP teams can ensure a smoother and more secure transition to S/4 HANA, minimizing risks associated with sensitive data exposure and unnecessary data storage in non-production systems.
For more information, see www.legupsoftware.com/solutions
