Service: How To Default Revision From Depot Repair / Charges into Order Management
(Doc ID 261568.1)
Last updated on SEPTEMBER 27, 2021
Applies to:Oracle Teleservice - Version 11.5.6 to 188.8.131.52 [Release 11.5]
Oracle Order Management - Version 11.5.6 to 184.108.40.206 [Release 11.5.6 to 11.5.10]
Oracle Depot Repair - Version 11.5.6 to 220.127.116.11 [Release 11.5]
Information in this document applies to any platform.
This article describes the setup that is required to enable automatic booking of RMAs, submitted from Service Charges or Depot Repair, for items under revision control.
Currently, such RMAs are processed through charges, using ASO APIs to submit the Sales Order. The ASO APIs do not pass revision numbers to Order Management. Therefore defaulting rules need to be set up for Order Management to have the correct revision number default in which enables booking of the RMA.
The setup described below should default the revision from the first (return) charge line it finds for the item being returned. The link between the RMA and the charge line is the service request for which the charges were submitted. This service request number is stored in the order line as source document. Implicitly, this means that if there are multiple return charge lines for that service request AND for the same item, the defaulting happens more or less randomly. This would only be a problem when different revisions of the same item are returned against the same service request. Currently, there is no possibility to find the correct charge line (id) related to the order line at the time of defaulting the revision on the order line. After submitting the order, the order line id gets stored in the charge line, but then the revision on the order line cannot be defaulted anymore automatically. In cases like this, the booking of the order will NOT fail because there will be a valid revision on the order line. The user will need to open the order and verify the revisions manually.
The below scripts and setup has been tested and verified at the time it was created. However, due to changing versions over time, it is not unlikely that certain parameters may change. The below steps can be used as a guideline and are intended as such.
Since it involves custom code, this is not supported through Oracle Support Services.
To view full details, sign in with your My Oracle Support account.
Don't have a My Oracle Support account? Click to get started!