How to Auto Populate Reference to Installation Detail for Non-Serialized Item RMA
Last updated on NOVEMBER 14, 2017
Applies to:Oracle Installed Base - Version 188.8.131.52 to 12.2.6 [Release 11.5 to 12.2]
Information in this document applies to any platform.
This datafix has been approved by development for customer consumption 13/Feb/2012.
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 non-serialized IB-trackable item is returned through an RMA receipt or RMA fulfillment, Installed Base is expecting the user to enter a reference instance number into every RMA line's installation details form. This information will be used when the actual receipt/fulfillment is processed. The instance specified will be updated according to the receiving transaction. If the instance number has not been populated on the RMA line, Installed Base is not able to determine what IB Instance has actually returned/cancelled and will therefore not be able to process the transaction.
When an RMA without required instance information is received, the transaction will raise the following IB Transaction Error:
Additional to that, the Install Base Error Correction and Data Synchronization process creates a list of RMA lines without instance information where it would be required. This list can be found in the output file of the program under the heading: "Non serialized RMAs without installation details". This report is created regardless of the mode the program ran for (Report, Correction or Synchronization).
When users are not accustomed to entering the required information for RMAs, the list of RMAs with missing installation details can grow rapidly (refer to <Note 364518.1> for how to prevent this). Also, it is not uncommon that no instances are available to be selected in the installation details for different reasons. These factors (and others) can make it difficult to enter all missing information, which is normally a manual process.
To make that process easier, this note provides a package that will automatically populate a reference instance into the installation details for the erred transactions and then resubmit the error. The package follows the following rules:
1. When original sales order information is entered in RMA line, then the instance created through original order line will be used.
2. When original sales order is still not processed to Installed Base, this RMA line will not be processed until original order line is processed.
3. IF RMA line does not refer to any original order line or no instance can be found through original order line, then instance owned by matched customer will be used.
When there are one or more instances that have an earlier active_start_date than the RMA receipt, it populates the installation details of the RMA with one or more of those instances until the sum of instances' quantity matches the RMA's quantity base on FIFO (the oldest instance will be picked first)
When there are one or more instances that have an earlier active_start_date than RMA transaction_date existed, it updates the installation details of the RMA with all those available instances. If the total quantity of instances is still less than the RMA's quantity, the package will do following base on input parameter user choose
a. If user choose 'Create Instance' = 'Y' then package will create instance to match RMA quantity and entered new created instance in installation detail of this order line, then process the RMA line.
b. If user choose 'Create Instance' = 'N' then package will check if there is any pending OM shipment to same customer prior to current RMA. If pending order is not found, package will update inventor instance's quantity
where RMA receives quantity to and process this RMA without expiring any customer product. If pending order is found, then package will skip this RMA and warn user to process the stuck OM shipment transaction first.
4. When no instance is found for the RMA fulfillment line, the line will be skipped and processed_flag = 'D' will be put into the error transaction table so the user will not see them in reprocessing form
Sign In with your My Oracle Support account
Don't have a My Oracle Support account? Click to get started
Million Knowledge Articles and hundreds of Community platforms