Installed Base Multiple Active Instance Issue

IB Error-Multiple Active Instance issue ….on item multiple items.

Error Description:

Multiple active instances found for the item attributes provided.
Inventory Item ID: XXXX
Organization ID   : XXXXX
Sub-Inventory     : &SUBINV
Locator ID        : &LOCATOR
Action: Check for duplicate inventory records found in CSI_ITEM_INSTANCES
The parameter value (Lot / Serial) for the parameter (Item attributes) is ignored.  The transaction details entered do not match the inventory material transaction for one or more of the attributes. Pl.  Correct it and reprocesses the error.

Error Description –
The error message means that when the API looked to Installed Base for an Instance to update, it found more than one instance that met the criteria from Inventory.  This generally occurs with Non-Serialized Item Numbers (even if they are serialized at Sales Order Issue). 
 It can occur for most transaction types including the following most common types:
CSIWIPCI – WIP Component Issue
CSIWIPCR – WIP Component Return
CSISOSHP - Sales Order Shipment
CSIRMARC - Return Material Authorization
CSIWIPAC - WIP Assembly Completion
Cause

There may be different causes for occurrence of this type of issue.

1-Problem with SFM Event Manager Queue Service Set up:

Where the SFM Event Manager Queue Service threads was set to greater than ‘1’ then the transactions get processed in parallel, rather than sequentially. Which let transactions for an Item with the same attributes create two instances, if they process at the same time. (NOTE- In our case Investigation from Team Oracle ruled out this option for this issue)

2- Discrepancy in setting up item attributes with regards to serial control and lot control:

The other reason of getting the ‘multiple active instances issue’ is – The procedure csi_rma_receipt_pub.identify_source_instance was called for these records, which looks up instances based on serial number, inventory item id and lot number. Since there might be a lot of non-serialized RMA, which may returns multiple results.

3- The probable other cause for Multiple Active Instances issue may be the procedures csi_process_txn_pvt.get_src_instance_id and get_dest_instance_id do not filter for expired instances.

4.  There are a few existing bugs and patches for different scenarios which have been found to cause this error due to incorrect query logic, but in your case you hit a specific example. Your item instances were lot controlled but not serial controlled. Prior to applying the patch the code logic performed a query which looked up instances based on serial number, inventory item id and lot number. Since your items are non-serialized this query returned multiple results and therefore threw the error. The patch fixed the code logic so that it performed the search using the correct criteria for the item setup.

Note- Point 2 and 3 might be root cause of this issue.

Cause Justification

Found few of the items have Serial and Lot control discrepancy across different organization.

 As per Oracle standards, Oracle Installed Base does not support lot control set up differently across inventory organization, when the item move between control and non-control organizations. If item needs to be set as lot controlled item, it has to be done first at Master (GLO) level. Because of this reason IB Errors are coming up regularly on those items.

Solution

We have raised a SR # with Oracle support Team.

As solution Oracle has suggested to apply a patch and resubmit the error transactions.

We performed the patch application in Patch in non Prod instances and resubmit the error programs which significantly reduced the error count.

           

Solution Justification
So this is evident enough of that the above mentioned patch application with reference to the SR Number   is useful to reduce the error counts of issue ‘Multiple active Instance’.