Using MC7A for location split on release from DP to SNP

[Former Member]

We are adding locations to SNP, but do not want to add those locations to DP (because of bolt-on DP systems that would require modification).

Because of this, we plan to us MC7A to define the split between locations when we release from DP to SNP.

We are running into an issue, however, when we have the same product in multiple planning areas: From Planning Area A, I want to split forecast between Location1 (80%) and Location2 (20%); from Planning Area B I want all forecast to go to Location3.

MC7A is not defined by planning area, so this split does not work appropriately to meet our needs.

Is there any way to have different splits by planning area? Is there perhaps a user exit that we can use to point the release job to custom tables?

[Former Member · Accepted solution]

Try exploring the methods

CHANGE_DATA_BEFORE_SPLIT

You can use this method to change a characteristic values combination of product (CV_MATID) and location (CV_LOCID) before it is split (product/location split) . The method changes the external IDs. If they are changed, the values of characteristic combinations should be updated in the tables (CT_PLOBJ_CHAR and CT_PLOB_VALUES) . The messages from the implemented BAdI (Table ET_MSG_TAB) can be saved in the application log.

CHANGE_DATA_AFTER_SPLIT

You can use this method to split one characteristic combination of product and location into more product/location combinations after it ihas been split. The other (free) characteristic values cannot be changed in the table

You will find this in the BADI as given below:

mySAP SCM - Implementation Guide -> Advanced Planning and Optimization -> Supply Chain Planning -> Demand Planning (DP) -> Business Add-Ins -> Change Data During Release to SNP or R/3

Cheers,

Srinidhi