Skip to Content
Technical Articles
Author's profile photo Kumar Chockalingam

Overview on SAP Carve-out Project

In today’s dynamic business companies restructure often, merging and demerging activities are part of it. This leads to carve-out projects in SAP system. This blog is about key areas involved in these projects.


Carve-out project is about de-linking of business operations from the parent company and move to separate system or another existing system. Either seller or buyer can do carve-out activities and also it can be done before or after identifying the potential buyer.

Following are options and this can be have any combinations from seller and buyer perspective

Source system Target system

1. Delink specific company code

2. Delink specific plants from company code

3. Delink specific product lines from existing plant and company code

1.  Addition of new company code

2.  Addition of new plants to the new company code or existing company code

3.  Addition new product lines to new plant and company code or existing plant and company code


In concept phase, business process owner of source and target system involve in scope definition of system architecture, business process, migration, de-migration, testing and cutover.



To summarise, carve-out projects are critical as this should not impact existing process of the target sytem. Also, migration to target should be followed by a de-migration activity in the source system.



Assigned Tags

      You must be Logged on to comment or reply to a post.
      Author's profile photo Purushottam Arote
      Purushottam Arote

      Good Blog.

      Author's profile photo Deepthi Gandham
      Deepthi Gandham

      Informative and Comprehensive.. Good work!!

      Author's profile photo Arulmurugan Veluchamy
      Arulmurugan Veluchamy

      Well Articulated, thanks.

      In Carve out, do we need to talk about new processes?

      As per my understanding, in carve out, as-is needs to be carry forwarded from source to new/target instance based on customer specific requirement ( normally company code, region specific content etc.,,)

      Am i wrong?

      Author's profile photo Andreas Niestroj
      Andreas Niestroj

      There are some good points in this overview.

      However, you have commented on stock which has to be migrated out of the system.

      For the stock I would just move it out via movement type 562.

      But how do you solve the Open Items: customer open items generated from SD orders. Actually the item stay with the source system, but it also exists in the target system.
      How do you solve the situation - you cannot just reverse the posting - there is the SD order would initiate the invoice again.

      Any idea

      Kind regards