When Yielding from Batch Reserved to Sales Order, Reservations Not Created in Order in Which Transactions Entered
(Doc ID 2033810.1)
Last updated on FEBRUARY 27, 2019
Applies to:Oracle Process Manufacturing Process Execution - Version 12.1.3 and later
Information in this document applies to any platform.
On : 12.1.3 version, Batches
Customer creates a batch from a sales order using the OPM Make to Order (MTO) functionality. This creates a reservation reserving the planned batch output to the sales order. When the product is actually yielded from the batch, the batch reservation (type Job or Schedule) is converted to an Inventory reservation - the material yielded from the batch is reserved to the sales order.
The customer yields more from the batch than the sales order requires. The quantity needed for the sales order is yielded in one WIP Completion transaction into one subinventory and locator and the additional quantity is yielded in a second WIP Completion transaction into a different subinventory and locator. Both WIP Completion transactions are done at the same time. The customer expects the material yielded from the first entered transaction to be reserved to the sales order, but this is not happening. Regardless of the sequence in which the data is entered, the system is reserving the material from the "other" subinventory and locator, and then reserving part of the material that the customer expects to be reserved.
The problem seems to be that the transactions are not processed in the order in which they are entered. Regardless of which transaction the customer enters on the first line, the system does not create the transactions in that order. It appears that the order of the transactions are possibly being based on the locator_id of the locator into which the material is being yielded. But then in addition to this, the reservations (at least based on reservation_id) are also not being created in the same order as the transactions. See Testcase for further details.
Customer expects to be able to enter the WIP Completion transactions in a certain order so that they can control which one is reserved to the sales order
The issue can be reproduced at will with the following steps:
1. Create a batch using MTO.
2. Create two or more WIP Completion transactions in the batch.
The issue has the following business impact:
Due to this issue, sales order reservations are being created against the wrong locator and sometimes the wrong subinventory.
To view full details, sign in with your My Oracle Support account.
Don't have a My Oracle Support account? Click to get started!
In this Document