on 09-29-2011 11:56 AM
Hi
We buy some products from a vendor, and we'd like to place orders at him only monday and friday in order to not have too many shipments coming in.
In R3 this would easily be done with a planning calendar, and we've tried to do the same thing in APO by creating a time stream that is open on the relevant days.
However this seems to be ignored by the heuristic (the plant we need this in runs planning in APO).
Are we missing something about planning calendars in APO? Is this really not the way to force procurement elements to be placed on specific days?
Regards
Simon Pedersen
Edited by: Simon Pedersen on Sep 29, 2011 12:56 PM
Hi,
You have to assign the created calendar to your location in /SAPAPO/LOC3. Please try and revert.
Regards,
Manimaran M.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
I've thought a bit more about this. Putting a shipping calendar on the vendor will actually not be a good idea in our situation.
It could easily happen that other plants also in the system would buy the same product from him, if we then limit shipping to specific days this would lock in this delivery pattern.
This would not be a good idea.
Is it really correct that planning calendars in APO does not work the same as in R/3 in regards to placing procurement elements on the relevant days? We really just need the same functionality as we have in R/3.
I've found out some more about this.
You can actually get the heuristic to consider the planning calendar on the material master in APO.
On lot size->procedure you set period type K, number of periods 1 and in planning calendar you insert your timestream which you have generated to match whatever planning buckets you want (in my case I have buckets only on friday and monday).
BUT!
This is not enough, on the "Quantity and data determination" tab you need to check the "use period factor" box.
Now when you run the heuristic, it actually uses the planning calendar when placing the preqs.
For our use this is a lot better than locking things in on location level.
Hello Simon,
The right solution for you is use period factor. For example with period factor 0.500 the P.Req will be created Thursday.
The lot size in APO has a correspondence on ECC side. You control from ECC the lot size parameters in APO.
The parameters are: Lot size, Min/Max lot size, Rounding value, Safety Stock, Safety time, etc..
At the limit, if you have a real issue you can create a Lot Size Profile on APO side. So, the CIF transfer will not modify your APO's parameters.
Also, you should have just one integration model for each object (e.g. Material).
Hope that can help you!
Thanks.
Regards, Marius
Hi Simon,
Which Heuristic did you use to resoLve this requirement, Is it SNP or PPDS Heuristic?
I had read that SNP heuristic is not going to consider Planning Calender assigned in the Lot size tab of the product master in APO.
Please share you information. Thank you.
Regards
PK
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.