on 04-08-2008 1:35 PM
Hi Experts,
We are using APO 4.1. We are focusing on DP to SNP forecast release of a single product to a single location. We have monthly time buckets in DP and we are trying to come up with demands on 6 days a week (excluding Sundays) in SNP. We have set "2" as period split to SNP2 tab of product location master data so that the data is disaggregated to the workdays in the present & future and then released for the same days. Once we change the shipping calendar of the location master so that it includes 6 days a week, there is no problem about the calculation of the daily forecast release quantity. But when we try to release the forecasts to SNP, we still observe demands on Sundays which should not be the case.
For instance, we have a monthly forecast of 4000 units & 20 workdays in a month.
Here is what we want:
Mon Tue Wed Thur Fri Sat Sun ....
20 20 20 20 20 20 0 ....
Here is what we get:
Mon Tue Wed Thur Fri Sat Sun ...
20 20 20 20 20 20 20 ...
We would appreciate any kind of help on this issue.
the usual way i would do this is to do the breakup into the required days in DP itself
create an interim PA(thats exclusively used for this purpose) which has the same MPOS as the PA that you have currently but just needs one KF which you use for release and is maintaind with the same horizons as the other KF
but use a different storage bucket with months and days and has a time profile attached to it which uses a factory calendar where the non working days are maintained
instead of releasing from PA in DP to SNP... TSCOPY your Release KF from PA to PA_interim and then to SNP in one single job... the TS copy should take care of the non work days in DP itself... release to SNP is straightforward after that
there is a bit of maintainace involved...just have one PB on the interim PA for admin purposes.... add the PA to maintainance jobs such as initialization of Time series and cons check etc
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
Did you try using a time stream id in your storage bucket with calculation rule in days specify only Monday through Saturday. The data itself is stored only in 6 days.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
Thanks Raj,
But we have already done it. Otherwise, we could not have observed the right daily forecast quantities. However, we still have forecasts on Sundays. While calculating the quantities, it does not count Sundays whereas while assigning the forecasts to days, it releases also on Sundays.
Make sure the receiving calendars in Location that the forecast is released to have Sundays as non-working days. Am little surprised why behaviour is changing with shipping calendar.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
Out of curiosity do you get the desired result if the period split is kept blank ? Atleast this will help isolate the issue - whether it is some interface problem or period split issue ?
I am surprised there is a business benefit with period split of 2 since SNP is a medium term planning tool. The first week is close to meaningless anyway since no one can react to a demand in a 4-5 days horizon. Which industry are we talking about ?
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.