Last updated on MAY 19, 2017
Applies to:Oracle Install Base - Version 220.127.116.11 to 12.1.3 [Release 11.5 to 12.1]
Information in this document applies to any platform.
This datafix has been approved by development for Customer consumption 18-May-2012.
IMPORTANT: The information contained in this document may contain omissions, inaccuracies or other errors. It is provided "as is" and without warranty. Oracle does not warrant that the information in the materials is up to date or error free, nor does it provide any other warranties, whether expressed or implied in law, including the implied warranties of merchantability or fitness for a particular purpose. The materials are not a program or documentation under the terms of your license agreement(s) with Oracle. In no event shall Oracle be liable for any direct, indirect, incidental, special or consequential damages, or damages for loss of profits, revenue, data or use, incurred by you or any third party, whether in an action in contract or tort, arising from your access to, or use of, this information.
If you have any questions or concerns please contact Oracle Support before running the script.
When a WIP Job is completed for Lot Controlled Items and the Lot Number changes, or the
Assembly Number changes, the issued Instance for the job is not being expired. This causes Installed Base to have "orphaned" records.
Expect the issued Instance should go to Quantity '0' and the status should update to 'EXPIRED'
when the new Instance is created under the WIP Completion.
-- Steps To Reproduce:
The issue can be reproduced at will with the following steps:
1. Create a WIP Job for a Lot Controlled Item and issue the Item
2. Complete the job with the same Item, but a different Lot or Assemble Number
3. Observe that the issued instance is not expired
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