on 07-28-2009 3:59 PM
In order entry, our availability check is looking only at inventory and RLT... so that if stock is unavailable, the line item gets confirmed for a future date based on the material's RLT. We have noticed, however, that every night when backorder rescheduling runs, the confirmed date is pushed out one day later (assuming that no inventory exists still). So it appears that BO rescheduling is recalulating the confirmed date based on the current date + RLT.
Does this make sense? Is there any way we can make the original confirmed date stick? We don't want to use the Fixed Date & Qty flag on the schedule line screen, because we want to be able to pull the confirmation (and delivery) in earlier if the inventory is available earlier... we just don't want it to keep getting pushed later.
This boils down to a business question.
Say you have a material with a 30 day RLT.
On Day 1, an order is placed - and due to no stock or planned receipt of stock with the 30 days - the delivery date is moved out 30 days based on the RLT.
Now it's day 29, you run the backorder report and there is still insufficient stock / replensihment plan within the next 30 days.
==> Do you want to keep the promised delivery date of day 30 - or is day 59 more realistic?
More to the point, why hasn't stock been acquired or a replenishment plan / order been created in the previos 29 days?
The RLT shouldbe set so that there is a very high likelyhood that the order can be fulfullled ini that time line.
To me, it makes sense to keep pushing out the date. When stock actually shows up in sufficient quantity, the date will be moved back up.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
Hi
Please let me know whether you are using the standard backorder rescheduling program or a Z program?
Cheers
Chandra
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
User | Count |
---|---|
89 | |
7 | |
6 | |
3 | |
3 | |
3 | |
3 | |
3 | |
3 | |
2 |
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.