on 03-15-2013 9:32 AM
I am using the 'maximum allowed lateness' parameter on the APO product master, with APO V5.1.
Suppose lateness = 200 hours, and I have a fixed planned order of 10,000 available 1 week after a demand of 1000, then I see via the product view that there is pegging between the demand and the order, as expected. But if I then run the product heuristic, a new planned order of 1000 is still created 'in time' to meet the demand.
If however I set the 'alert threshold for lateness' also to be 200 hours, then when I run the product heuristic there is now no new planned order created 'in time', and I just see the fixed planned order pegged to the demand.
Is this expected behaviour?
Thanks for any advice on this...
Hi,
yes, that is like it is coded. Strange but true.
the entry in the field Maximum Lateness of a Receipt controls the liveCache pegging.
the entry in the field Alert Threshold for Lateness controls the net requirements calculation in PP/DS heuristics.
It took me a debug session to find that out.
BR Frank
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.