Lot Genealogy Includes Ingredient Lots That Were Deleted From Batch (Creating WIP Return Transaction) (Doc ID 1452103.1)

Last updated on MAY 09, 2017

Applies to:

Oracle Process Manufacturing Process Execution - Version 12.1.1 and later
Oracle Inventory Management - Version 12.1.1 and later
Information in this document applies to any platform.

Symptoms

On : 12.1.1 version, Lot Genealogy,

ACTUAL BEHAVIOR
---------------
When viewing lot genealogy for a lot that was yielded from an OPM batch, the Lot Genealogy source inquiry and report show an ingredient lot that was consumed in the batch (through a WIP Issue), even though that consumption was later reversed and corrected using Correct Material Transactions, which creates a reversing WIP Return. In other words, even though the net quantity consumed was 0, the lot genealogy still shows the lot as if it had gone into making the product lot, when in fact it did not.

It's true that the Transaction history shows both the WIP Issue and the WIP Return that was created behind the scenes, but it also shows every other transaction that was ever done for the "deleted" ingredient lot (at least on the online inquiry), so it is not even obvious that these were both for the batch that yielded the product lot.

EXPECTED BEHAVIOR
-----------------------
Customer expects this to work as it did in OPM 11i Inventory lot genealogy, where only lots with a non-zero net consumption in the batch were shown.

STEPS
-----------------------
The issue can be reproduced at will with the following steps:
1. Consume a lot of an ingredient in a batch (i.e., do a WIP Issue).
2. Yield a lot of the product (WIP Completion).
3. Using Correct Material Transactions, change the ingredient lot to a different lot and click Correct. This creates a WIP Return of the original lot and a new WIP Issue for the new lot. The WIP Return reverses out the WIP Issue.

BUSINESS IMPACT
-----------------------
The issue has the following business impact:
Due to this issue, Lot Genealogy shows source lots that are not actually a part of the source. The customer sends lot genealogy information to their customers, and they have to manually remove the lots that did not actually go into making the product.

Cause

Sign In with your My Oracle Support account

Don't have a My Oracle Support account? Click to get started

My Oracle Support provides customers with access to over a
Million Knowledge Articles and hundreds of Community platforms