Incorrrect Duplicate Reuse of Serial Number On Component Issue Transaction For Issued Out Serial Number (Doc ID 2069004.1)

Last updated on APRIL 22, 2016

Applies to:

Oracle Inventory Management - Version 12.1.3 and later
Information in this document applies to any platform.

Symptoms

The transaction data entry is allowing component item material under serial control to issue the identical component serial number to multiple distinct WIP Assemblies.
As example serial number SA1 is issued to assembly AA1 and shipped out of inventory on September 30th. Again component serial number SA1 is now issued to new assembly AA2 on October 1st.


Expected Behavior
Application should not allow to issue the same item serial numbers to new assembly AFTER already assigned to other assembly and shipped offsite.

 

Steps
The issue can be reproduced at will with the following steps:
1) Perform a work order-less completion for assembly "A" serials 1234 to 1235 (qty 2). The serial status is now "Resides in stores".
2) Issue assembly "A" into assembly "B" via work order-less completion, specifying serials 1234-1235 as the component serials to issue. The serial status is now "Issued out of Stores".
3) Perform a work order-less completion for assembly "A" again with serials 1234 to 1235 (qty 2) and the system allows the transaction. The serial status returns to "Resides in stores".


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