Monday, 03 May 2021 02:03

Business Scenarios and technical Approaches for SAP Carve-Outs

Written by Lorenz Praefcke
Rate this item
(0 votes)
Source https://blogs.sap.com/2021/05/04/business-scenarios-and-technical-approaches-for-sap-carve-outs/
“© 2020. SAP SE or an SAP affiliate company. All rights reserved.” “Used with permission of SAP SE”

We’ve spent some time now talking about what an SAP carve-out is, as well as some of the nuances that makes these types of projects unique. I think it’s time we dive a bit deeper into the topic and touch on some of the general business scenarios customers may come across during a carve-out project.

It is generally agreed that SAP shops face one of three business scenarios. Keep reading to understand what these are, and when they may or may not make sense to pursue during your project.

Business Scenarios for SAP carve-outs

  1. Carve-out in SAP clone: this is simply a 1:1 copy of the productive SAP system and results in no functional change. This is by far the least complex of the scenarios, and at times may require zero external assistance as it can be typically executed with experienced in-house basis resources. Perfect solution for small systems, in internally driven carve-outs, since you don’t have to worry about proprietary or confidential data ending in the wrong hands. Making a full system copy is not always feasible, especially when talking about large databases, as you must double the hardware required to run a full copy of a productive SAP system. There are additional task related to data deletion that can be performed in post using specialized tools such as SAP LT or our very own cbs ET Enterprise Transformer.
  2. Carve-out in new SAP: this is a move to another SAP ECC, SAP S/4HANA, or a different SAP system with different configuration. The key here is that data needs to be transformed into new SAP processes, or in the event of SAP S/4HANA new data structures and functionality. This is the most common scenario for two party M&A deals. Here you have two options, you can use the clone approach described above, and then resolve conflicting configuration and z-codes to match the target system. You can also selectively carve-out the relevant data in scope, transform it on the fly, before importing into the target system or a shell copy. At the end of the day, there is always some configuration and z-code work that needs to be performed before the data is compatible with the target structures.
  3. Carve-Out in any new ERP: here we are dealing with an unknown target ERP system or a non-SAP ERP. This scenario is quite common as well. On the target side this will be quite similar to a
Continue reading here
Read 60 times

Leave a comment

Make sure you enter all the required information, indicated by an asterisk (*). HTML code is not allowed.