Why Does IB Status Change To 'Expired' After Receiving Non Serial Controlled IB Trackable Item?
Last updated on MARCH 08, 2017
Applies to:Oracle Depot Repair - Version 184.108.40.206 and later
Oracle Installed Base - Version 220.127.116.11 and later
Information in this document applies to any platform.
***Checked for relevance on 28-Jun-2015***
Why does the IB status get changed to 'Expired' after receiving a non-serial controlled IB trackable item?
According to <Note 276449.1> - Impact of Serial Control Type on Install Base Behaviour
Not serialized; no serial numbers are tracked in Install Base at all. That means that instances are not unique for Install Base. Therefore the quantity of an instance can be greater than 1. Just like onhand quantity in Inventory. New quantities of the same item can be added to the quantity of an existing instance as long as all other attributes are the same. When the quantity reaches 0 (e.g. by issuing all onhand quantity), the instance is expired automatically (end dated). When new quantities are received, the instance is reactivated. In general, whenever an item is received into inventory and the instance for that item would have the exact same values for all attributes as an existing instance, the existing instance is updated instead of a new one created.
The IB record status was set to 'Expired' because the QTY became 0 as the item is received into the subinv for repair. But the user needs to ship that back.
Why should the quantity in IB become 0?
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