Picking and Auto Detail Of OPM Batch Doesn't Always Reserve or Pick In Correct FIFO Order
(Doc ID 1502866.1)
Last updated on FEBRUARY 03, 2019
Applies to:Oracle Inventory Management - Version 12.1.3 and later
Oracle Process Manufacturing Process Execution - Version 12 and later
Information in this document applies to any platform.
***Checked for relevance on 10-Jul-2014***
When receiving the same lot into the same subinventory and locator a second time after having received it earlier, the moqd.orig_date_received is not the same as for the original receipt, and because of this, FIFO picking does not always select the oldest inventory.
The customer noticed this in a scenario in which inventory was inadvertently consumed in a batch with a WIP Issue, but then was put back using a WIP Return. The inventory now has a moqd.orig_date_received equal to the transaction date of the WIP Return instead of the date the inventory was originally received. This does not make sense from a business perspective. This is the most troublesome part of this issue. Note that although this was noticed using a WIP Issue and WIP Return in a batch, this can happen in other scenarios also, it is not specific to WIP transactions in OPM batches.
This is a result, though, of a broader issue. Receive a lot, let's say LOTA, into inventory, through a misc receipt, a WIP Completion, a WIP Return, whatever. The moqd.date_received and moqd.orig_date_received are set to the transaction date, for example, April 11. Receive more of the same lot, even into the same subinventory and locator, with a later transaction date, for example, May 11. This creates a new row in moqd, with both the date_received and orig_date_received set to May 11, even though the original date that the lot was received was April 11. Because of this, once the row in moqd from April 11 is used up, FIFO picking (or AutoDetail Batch based on FIFO picking rules) will select lots that were received between April 11 and May 11 even though LOTA is actually an older lot. This does not really make business sense; it is one lot in one subinventory and locator, it is not really two different "inventories" and so it should all be treated the same, using the same date, in regards to FIFO and picking or OPM batch AutoDetail (which uses the Picking code to create detailed reservations).
Note that this happens regardless of the setting of the profile INV: FIFO for Original Receipt Date.
Should picking rules with the FIFO option for Lot even use moqd date received data instead of lot creation date, since lot creation date as of R12 is set to the date the lot is first received into inventory, not the date the lot record was created? If you want to use the date received, isn't this what Receipt Date Asc under the Subinventory and Locator fields on picking rules for?
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
|This document is being delivered to you via Oracle Support's Rapid Visibility (RaV) process and therefore has not been subject to an independent technical review.|