on 03-31-2017 11:20 PM
Hi Gurus,
The Forecast that is generated in DP in Months does not match the Forecast in SNP in Months. We generate a forecast in monthly buckets. We use constant model. So imagine a forecast of 100K across the entire horizon in Monthly Buckets. Our DP Storage Bucket Profile is set to Weeks/Months. Because we plan at a weekly level in SNP, we publish the Forecast to SNP in Weeks. Meaning we publish the Forecast from DP via Mass Processing from a DP Planning Book that is in Weekly Buckets. The DP and SNP Weekly forecasts match up when looking at the Weekly Data Views. However, when we look at the Monthly Data View in SNP, we'll see spikes in the forecast throughout the horizon. It seems the forecast spikes at the end of each month. This has caused a lot of confusion and confrontation between the Demand and Supply Planners.
I figure this has to do with Time-Series Dissaggregation and the systems use of Technical Periods, but I would like to know the best way to get both Monthly and Weekly Numbers to match. Any insight would be greatly appreciated. Thank you.
Hi,
Use your Monthly data view in DP to release the forecast.
In Release profile use Period split profile which should be from Monthly to weekly. And if you want You can use distribution function as well in the release profile to pass the forecast on particular day or on percentage basis.
Thanks,
Venu
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
Hi Neil,
You figured out correctly that the most common cause is that the release takes place according to the values in the "storage buckets".
Best solution here is that you create your own periods using fiscal year variant and release accordingly or you can try using badi /SAPAPO/SDP_RELDATA.
Hope this helps.
Thanks & Regards,
Sonali
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
User | Count |
---|---|
15 | |
4 | |
3 | |
2 | |
1 | |
1 | |
1 | |
1 | |
1 |
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.