Dear SAP Friends,
Happy Reading !!!!!!!!
Welcome to one of the Interesting Topic in SAP APO Demand Planning
With the “new normal” we all came across recently, divestment is the focus area of the business houses. Executing SAP carve-out projects on ECC or S/4HANA smoothly and effectively is critical in the success of a merger or acquisition. These SAP projects has to undergo long laundry list for SAP and non-SAP applications demerger. Here in this blog post we will be discussing about how SAP APO Demand Planning can be carved out.
There are multiple carve-out strategies, following figure represents one of the strategy where initially systems got separated in same system and later in second phase it separated for respected organizations, please refer to SAP Blog posts for carve-out.
Key Areas in SAP APO – Demand Planning to focus on for separation:
Phase I
Phase II
Includes all the steps from Phase I, additionally to perform:
Data load options from source system to SAP APO - BWl
Realignment
Create new CVC for the new locations, as all the products needs to be mapped to new location as follows:
Use realignment function to generate new CVC based on existing CVC of a Master Planning Object Structure (MPOS), and to copy data from the existing CVC (source) to the new CVC (target). One can also specify to deletes the original CVC and its data.
Performs the following activities:
Tcode: /SAPAPO/RLGCOPY
Realigning InfoCubes
If you have a requirement to realign the data at infocube level, that is also possible, which have a similar structure to the Master Planning Object Structure(MPOS). The InfoCube must contain all the characteristics that are in the realignment table for the MPOS.
The main advantage of realignment over copy is that realignment creates the target CVC’s if they are not available in the POS.
Update Selection Profiles
Use the transaction /SAPAPO/MC77 to update the selection profile, in our scenarios we have to update the new plants or create the selection profiles with new plants.
User restrictions
As now there will be 2 different organizations in single system, there might be a requirement that one planner responsible for planning for one location should not see or plan the data for other locations, there are multiple ways to implement the user restrictions:
Proportional factor
As the proportional factors are dependent on CVC hence it is required to delete the old CVC (CVC of the products which are new plants now)
The resulting proportional factors for a CVC are time-dependent. The system calculates them for each time bucket within the horizon. This is how the system calculates the proportional factors.
For more information on other steps, please visit the community page. Here you will be able to leverage learnings from carve-out challenges and details about SAP APO, SAP news, SAP customer stories and other resources to stay ahead and ensure business continuity.
If you have remaining questions and need further guidance, navigate to SAP’s Ask a Question site to receive answers from SAP Supply Chain experts.
Happy Reading !!!!!!!!
Welcome to one of the Interesting Topic in SAP APO Demand Planning
With the “new normal” we all came across recently, divestment is the focus area of the business houses. Executing SAP carve-out projects on ECC or S/4HANA smoothly and effectively is critical in the success of a merger or acquisition. These SAP projects has to undergo long laundry list for SAP and non-SAP applications demerger. Here in this blog post we will be discussing about how SAP APO Demand Planning can be carved out.
There are multiple carve-out strategies, following figure represents one of the strategy where initially systems got separated in same system and later in second phase it separated for respected organizations, please refer to SAP Blog posts for carve-out.
SAP Carve-out
Key Areas in SAP APO – Demand Planning to focus on for separation:
Phase I
- Deciding the strategy to have separate SAP APO BW structure or use the same for carve-out data (In this blogpost we will be considering same BW structure).
- Creation of Master data in APO (Product, Location, CVC, etc.)
- Load Master data from source system (ECC) to SAP APO BW
- Delete the CVCs for products moved to new plants
- Creation of new selection profiles
- Update the RemainCo selection profiles by removing the products moved to new company.
- Update proportional factors.
- Update the process chain
- Validate any data specific hard coding in custom programs
- Introduce authorization control
Phase II
Includes all the steps from Phase I, additionally to perform:
- Validate the source and target system connections
- System clone
- Delete Master and Transaction Data
- Reload data or SpinCo
Data load options from source system to SAP APO - BWl
Realignment
Create new CVC for the new locations, as all the products needs to be mapped to new location as follows:
realignment
Use realignment function to generate new CVC based on existing CVC of a Master Planning Object Structure (MPOS), and to copy data from the existing CVC (source) to the new CVC (target). One can also specify to deletes the original CVC and its data.
Performs the following activities:
- It copies notes to the target CVC and does not overwrite an existing note.
- It changes generated selections to reflect the realigned CVC.
Tcode: /SAPAPO/RLGCOPY
Realigning InfoCubes
If you have a requirement to realign the data at infocube level, that is also possible, which have a similar structure to the Master Planning Object Structure(MPOS). The InfoCube must contain all the characteristics that are in the realignment table for the MPOS.
The main advantage of realignment over copy is that realignment creates the target CVC’s if they are not available in the POS.
Update Selection Profiles
Use the transaction /SAPAPO/MC77 to update the selection profile, in our scenarios we have to update the new plants or create the selection profiles with new plants.
User restrictions
As now there will be 2 different organizations in single system, there might be a requirement that one planner responsible for planning for one location should not see or plan the data for other locations, there are multiple ways to implement the user restrictions:
- Create authorization roles under ‘APO 3.0 Authorization Object:..’ and specify the locations which planner wanted to view or change in the planning book (/SAPAPO/SDP94)
- Implement the BADI: /SDP_SELECTOR and restrict the planners for the locations
- Above 2 methods are not called for all tcodes, if you want to restrict the planners from all the tcode, you can implement the enhancements, majorly in 2 function modules
- /SAPAPO/LOC_LOCNO_GET_LOCID
- /SAPAPO/LOC_LOCID_GET_LOCATION
Proportional factor
As the proportional factors are dependent on CVC hence it is required to delete the old CVC (CVC of the products which are new plants now)
The resulting proportional factors for a CVC are time-dependent. The system calculates them for each time bucket within the horizon. This is how the system calculates the proportional factors.
- In each time bucket, the system sums the key figure values of all the CVC. The time bucket has been specified by the user.
- In each time bucket, the system divides the key figure value of each CVC by the total obtained in step (1), thus obtaining a proportional factor for each time bucket.
For more information on other steps, please visit the community page. Here you will be able to leverage learnings from carve-out challenges and details about SAP APO, SAP news, SAP customer stories and other resources to stay ahead and ensure business continuity.
If you have remaining questions and need further guidance, navigate to SAP’s Ask a Question site to receive answers from SAP Supply Chain experts.
- SAP Managed Tags:
| User | Count |
|---|---|
| 5 | |
| 5 | |
| 3 | |
| 2 | |
| 2 | |
| 1 | |
| 1 | |
| 1 | |
| 1 | |
| 1 |
