DP Realignment - 2


Skip to end of metadata
Go to start of metadata

Purpose

This Wiki page is to provide necessary information about how realignment works in demand planning. Some basic concepts, settings and system logic is explained.

Overview

Topics included in this page:
    • Basic Concepts
      Explain basic concepts about realignment
    • Realignment Steps
    • Explain how to create realignment steps and his functionalities
    • Settings in /SAPAPO/RLGCOPY
    • Explain the settings of transaction /SAPAPO/RLGCOPY useful for realignment run
    • Realignment Execution
    • Here you can find how to run realignment and also best practices

Basic Concepts

You can use realignment to generate new characteristic value combinations based on existing characteristic value combinations of a MPOS and copy data from the source combinations to the new ones. You can also specify that the system should delete the original characteristic value combinations and corresponding data (delete source).
The system also copy notes to the target combinations and change generated selections to reflect the realigned CVCs. Please note that data realignment is not valid for navigational attributes because such attributes are not included in characteristic value combinations.

Realignment steps

The system carries out a data realignment in a realignment run. You define the individual steps of this realignment run in a realignment table through transaction /SAPAPO/RLGCOPY based on a Master Planning Object Structure. The realignment steps are below:
First you should select the Master Planning Object Structure for which you want to realign data and then:
1. Maintain the realignment table: The realignment table is created once, in the first time that you try to maintain realignment table entries. This table is created based on the given MPOS clicking on "Create/change table". It's possible to restrict the characteristics for realignment, you will get a message asking if you want to restrict the characteristics in a dialog box. If you choose yes, you will get another dialog box where you can deselect individual characteristics and they will not be included in realignment.Then you will get the table. To create a new step you can click on "create step" button:
2. Maintain steps: To maintain the realingment steps you should click on "Maintain entries". To create a new step you should clik on "create step" button. And you will get the following:
Here you have to fill the following fields:
  • Step status: describes if the realignment step was already completed successfully (X),if the step is ready to be performed ( ) or if is in editing mode (D). As you are creating  a new step, the step status should be blank, but after running the realignment, If you want to check if the step was already completed, you can check the status afterwards
  • Validity date: the date from which a realignment step is taken into account if you run the realignment. Only the realignment steps with validity date before the date of realignment run will be taken into account.
  • Delete source: You should set this flag, if the source combination should be deleted during realignment. Please note that all data for the key figures are deleted with the combination. Make sure you don't need the data before set this indicator and execute realignment.
  • Copy factor: Here you specify the proportion of the original value that should be copied to the new one. The default is 100% and the maximum is 999%.
  • Copy logic: If you already have values for the destination combination, you can choose M if you want to overwrite this value or A if you want to sum the new value with the old one.
  • And finally you will have the value for the source and destination combinations.

To create the other steps you can copy from the existing ones or create a new blank one. Please note that, if you select different values in the from and to fields, the realignment run will create new characteristic value combination and also new time series for these CVCs. And, as explained above, if you selected the delete source indicator, the original characteristic value combinations and time series will be deleted. After maintaining all the relevant information, you will have a realignment table:
Please note that in the step status you can have the following:
Realignment step has been executed successfully which means you have the step status X (realignment step was already completed successfully) when you double click on this step.
Draft status which means realignment has not been executed yet and will not be executed until you change the status to open, and you can see you have step status as D (editing mode) if you double click on your step.
Open status: this step will be executed in the next run after the validity date. If you double click on this step you will see that you have a step status blank (ready to be performed).

Other settings

In transaction /SAPAPO/RLGCOPY you can find other settings than "maintain entries" and "create/change table" as you can see in the image below:
Under the key figure tab, you can select if you want to realign data for all key figures or individual key figures. If you want to select just some key figures you choose the second option and select the ones you want to include in the realignment run and the ones you want to be initialized (if applicable).
You can also realign an InfoCube. Please note that restriction of key figures is not supported for InfoCubes, but all the processes are the same as described above. The infocube should contain all the characteristics existent in the realignment table for the MPOS. The field "Only realign InfoCube" must be used if you want to realign only the InfoCube and don't want to include the master planning object structure.

Execution of realignment

  • You can run realignment in background or online just clicking F8.It's recommended to run the realignment periodically as a background job at night. This is recommended due to performance reasons and also to make sure that the CVCs used in the realignment table are not locked for any user durint ghe realignment run.
  • The realignment run execute all steps where the status is blank (ready to be performed) which the validity date is before the day of the execution.
  • Background execution is terminated after the first error in realignment to avoid inconsistencies. Please note that the previous steps are not canceled.

https://wiki.scn.sap.com/wiki/display/SCM/10.+Data+Realignment


Comments

Post a Comment

Popular posts from this blog

Common CIF Errors

Most common error messages that we face when analyzing CIF execution. For every error message we have a few recommended actions and possible root causes. 1. Order version __ __ not valid at date __ . Root causes:  PPM/PDS or production version is no longer valid at order date of execution.  No available PPM/PDS orPV at order’s date of execution.  PPM or PDS has not been ciffed correctly to APO. Solution: Check production version status is not locked. Update new validity dates for production version. Cif changes to APO in order to update the PPMs or PPDs. Re-explode the orders where necessary. 2. Product ____ doesn’t exist in an active integration model. Root causes:  Material intergation model is not active.  Product has cross-plant status as blocked.  Material has MRP type different than X_*. Solution:  Check and correct the cross-plant status of the product..  Check and correct the MRP type of the product (X_).  Activate the integration model and C
Read more

SO Deleted but appears in MD04

1) Please check any Open delivery is exist for the order, if yes delete the Delivery 2) Close the order by order rejection 3) run SDRQCR21 in SE38 with data transfer , planning file entry and processing per material tick 4) This will remove the planning file entry and demand and run MRP 5) If problem still exist , then raise a Question to SAP with the help of Basis https://archive.sap.com/discussions/thread/1863626 Data transfer This parameter will be selected in order to update Sales and Delivery Requirements in Database by applying the Correction. Comparison This parameter will be used to improve the performance and run-time execution and will not reconstructs the Database for all Materials/Plant in the selection. Planning Entry If this parameter is selected then the report creates entries for the planning run for the affected Materials/Plant in order to make sure that the material should be included in next MRP run. Processing per Materi
Read more

Automating CIF Delta Report Reprocessing

Image
CIF is the standard interface between APO and ECC used to transfer master data (uni-directional) and transaction data (bi-directional). But very often due to some master data issue transaction data does not flow through and gets stuck in CIF queue. SAP provides CIF Delta Reconciliation Report (commonly know as CCR) that compares transaction data for given product-location between APO & ECC to list the differences. This output result is typically reviewed by production support team and necessary processing action (one of Send to ECC, Send to APO, Delete in ECC and Delete in APO action button) executed to reconcile the transaction data differences. Any APO consultant doing CIF monitoring on regular basis knows the effort required and also over time turns monotonous. However the choice of action to be taken is limited (most of the cases only 1 of the 4 actions possible) based on the transaction data object type (like Purchase Requisition, Purchase / Stock Transfer Order, Planned Ord
Read more