on 07-22-2016 4:32 PM
Hi All,
I am releasing the forecast from DP to SNP.
Both DP and SNP have weekly bucket so not using any period split profile.
Forecast is not getting released for first 5 weeks and then the forecast is fine in SNP from 6th weeks onwards.
I tried to search the answer for this unique behavior but couldn't get.
Thanks in advance for your help.
Regards,
Prabhat
Hello, by which functionality do you perform forecast release? MC90 or DP background job?
How did you check the released forecast? Please go to /sapapo/rrp3, check [forecast] tab, can you see the forecasts there?
BR, Ada
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
Thanks Ada for your reply.
I am using releasing the forecast by background and MC90 - both ways. Result is same.Checking the release forecast by going to the SNP planning book.
I have attached the screenshot of the forecast view.
What does the different column mean ?
Plnd Qty
Withdrawl Qty
Allocated
Rem. Plnd. Qty
Thanks again ,
Prabhat
Hi Prabhat,
so actually the forecast release works fine even for the first 5 weeks. The reason you don't see them in //RRP3 is simply related to the fact that the forecast has been fully withdrawn, i.e. goods issue postings have fully depleted the gross forecast.
Please check out Ada's very helpful wiki where you perfectly explained the forecast consumption topic. This article answers all your questions:7. Forecast Consumption and Reduction - Supply Chain Management (SCM) - SCN Wiki
I hope this helps.
regards Peter
Hi Ada,
From your Wiki Page:--
"
Withdrawal quantity is written to database table /sapapo/dp_head and /sapapo/dp_sched.
As of APO3.1, the withdrawal quantity is also written into the liveCache forecast order data into field ORIGINAL_QUANITY. EXCEPTION: if descriptive characteristics are used, the withdrawal quantity is ONLY written into the liveCache order data. Nothing is written into the database table. "
Can we display this PGI quantity in the SNP planning book ?
Regards,
Prabhat
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
Thanks Ada and Peter for your help
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
Hi Prabhat,
there might be various reasons why the forecast has not been released as expected. The typical ones are:
1) Data view for release only starts at bucket x+6 (in case of release via background job)
2) Wrongly filled selection option for online release via //MC90
3) Forecast consumption takes place which fully consumes all gross forecast for the first 5 weeks (check //RRP3->forecast tab as suggest by expert )
4) Badi implementation manipulating released data
regards Peter
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
, If you are releasing the forecast by using DP Background job, then Please check in Data view from where the release is happening, may be there could be a chance of offset value/Data range set to release after 5 weeks.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
User | Count |
---|---|
8 | |
4 | |
3 | |
2 | |
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.