Master Data Inconsistency ( Forecast Release from DP to SNP )
Sometime’s during Forecast Transfer from DP to SNP, for few location-product combinations Forecast may not get released. Reason being, Deletion indicator was set or there was no Product – Location ( MatLoc ) available. Planners can identify the same from the Forecast Release job log. But Planners will be more happy if they come to know before the release of forecast instead of post forecast release. Reason Being, Planners, may not always put in Forecast Values at Product – Location level. They generally put values at a higher level which gets dis-aggregated below. As they are not aware of missing matloc or deletion indicator, they see a Demand Drop post release to SNP. To avoid the Demand Drop’s and also to alert the planner we should be able to identify those combinations beforehand.
There are many ways we can do this. We can develop Custom Report’s / BADI Macro’s to meet the requirement. But all these can be done witht he help of ABAPer only. So i have thought to use ‘ ALERTS’ in APO Demand Planning to populate the error MATLOC’s.
> Create 2 Alert Types : 1. Missing Matloc 2. Deletion Indicator was Set
> Write the Macro with below logic :
# Step 1: ( load Master Data )
Define two variables. 1. Del_Flag and 2. Proc_Type . Populate Del_Flag with LVORM Field using MATLOC_C function and Proc_Type Field with BESKZ using MATLOC_C function.
# Step 2 : Generate Alert Step Logic:
( Del_Flag ) = ‘X’
Generate Alert Deletion Flag was Set
(Proc_Type) <> X
(Proc_Type) <> P
(Proc_Type) <> E
(Proc_Type) <> F
Generate Alert MatLoc was Missing.
> Run the Macro in a Background job at Product – location level for the selection you use in the forecast transfer job. Run before the forecast release job , so that Planners will be Alerted beforehand.