cancel
Showing results for 
Search instead for 
Did you mean: 

Backorder Rescheduler revising already committed batches

Former Member
0 Kudos

We found an issue with our backorder recheduler job (runs the V_V2 transaction on regular intervals) where the following occurred:

We have an order with a first ship date 2 days in the future. When the order was entered, the batch containing the last 3 units was committed to the order (we entered the batch on the sales order line as well). Later that day, another order for 2 units of the same part was entered, with ship date = current date. On order entry, the availability check placed this on backorder, as no quantities were available. When the backorder recheduler next ran, it uncommitted 2 of the units form the first order and gave them to the 2nd one. Unfortunately, we did not catch this until the first order showed up on the next morning's backorder report.

The V_V2 transaction is set to allocate in shipping date order, which for not yet committed orders is how we want new inventory allocating, but we would also like to have confidence that when we commit actual batches to a future order, they stay with it.

Thanks

Accepted Solutions (0)

Answers (1)

Answers (1)

Former Member
0 Kudos

So the solution to this is not a configuration issue at all. To be sure that committed batches do not get reallocated, all we needed to do is click on the Fixed date and qty check box on the scheduled line on the order itself.

Edited by: MFleischer on Jun 28, 2011 11:34 AM