Why Did Installed Base Create A New IB Instead Of Activating An Expired One?
(Doc ID 2305372.1)
Last updated on SEPTEMBER 07, 2017
Applies to:Oracle Installed Base - Version 12.1.3 and later
Information in this document applies to any platform.
Why the system created a new IB instead of re-activating an expired one.
User has 2 part numbers, one of which is a BOM and the other is a component in that BOM.
A : the BOM part
B : the component part
Both are serialized at sales order issue, and IB-tracked.
Both of these parts have the same serial number physically printed on them. The BOM is the item whose SN is scanned during shipment.
- A was shipped for an internal order. IB XXX was created.
- A was received in the Netherlands. IB's status was changed to EXPIRED.
- A was shipped to a customer. Status changed to CREATED. A "Component Of" configuration was established with IB YYY (below).
- B (a component in A's BOM) was shipped. IB YYY was created.
- we have a custom concurrent program that updated the serial number of IB YYY to be equal to the SN on IB XXX. Now both IBs have the same SN.
- A was RMA-ed and EXPIRED. At this time, the configuation relationship with IB YYY was expired.
- the B was also RMA-ed and EXPIRED.
- A was shipped to a customer again. A "Component Of" configuration was established with new IB ZZZ.
- instead of choosing existing IB YYY and changing it to ACTIVE, the system created a new IB (instance ZZZ) for part B.
My question is why, a brand-new IB was created for part B.
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