The three options for cbs’ Selective Data Transition approach to S/4HANA migration
Meet the Authors
Key Takeaways
⇨ The cbs Selective Data Transition (SDT) methodology offers flexibility for S/4HANA migration, allowing organisations to transition at their own pace rather than being limited to greenfield or brownfield methods.
⇨ Users can choose from three different data migration approaches—client transfer, system merge, and shell conversion - each tailored to specific organisational needs and configurations.
⇨ The migration process involves creating a target system in S/4HANA, with options for transferring ABAP repositories and configurations, emphasising the importance of a customised approach to data integration.
In the last Mastering SAP piece covering cbs’ Selective Data Transition approach to S/4HANA migration, we discussed how organisations are no longer beholden to a greenfield or brownfield migration method. The cbs SDT methodology can provide firms with the necessary flexibility to transition over to S/4HANA at their own pace.
Through selectively transferring different types of data to upgraded systems using cbs SDT, users can choose three different approaches when it comes to actually migrating crucial process data. While SAP DMLT will handle the transfer of data, firms need to decide on what specific approach would best suit their needs.
Client transfer
Explore related questions
For this approach, organisations will be required to select a client underlying master data and pick the data that needs to be transported to S/4HANA. Once this simple step is done, users can start the procedure of transitioning through SAP.
Company code transfer
The company code transfer procedure can let clients select a company code from an already existing environment that is laden with underlying master and transactional data, including configuration, and start to transition to S/4HANA. This approach can be done by utilising the master information or transitional data gathered from undergoing the procedure.
System merge
Integrating data from two or more clients can help create an empty instance within S/4HANA. The clients a firm decides on merging need to be from SAP systems, but said SAP ERP systems don’t all need to be uniformly the same.
Once a transitioning approach has been selected, it’s time to create a target system – the place where the data is to be moved as a whole during the migration. The mix-and-match technique requires users to create a new SAP S/4HANA system. When this approach is chosen, users can just start transferring ABAP repositories and configurations accordingly – but it has to be done manually.
Another technique involves the shell conversion approach; beginning with the creation of a shell copy of the PROD environment currently available to the user. Transactional or master data isn’t needed for the shell copy, the ABAP repository and configuration settings are the only vital components required. Once the shell has been made, organisations will need to transfer the ABAP repository and the configuration simultaneously. Due to the lack of transactional data available, the process will be a quick one.
Now that you have an idea of what utilising the cbs SDT approach involves, check out part three in our series on selective data transition to find out why it could be the ideal transformation path for your organisation.
Premium