Daily basis, supply chain users (SCM users) create a large number of sales orders in response to customer Purchase Orders. The Sales Order will be closed once the goods or services have been supplied to customers, and the corresponding AR invoices will be prepared and submitted to customers for billing. The buyer may return the goods to the organization for a variety of reasons, such as a defective item, a higher price, or the dispatch of more goods than planned. Oracle Fusion Standard Process allows you to create an RMA (Return Material Authorization) order against each of the original Sales Orders individually.

It is possible that the client receives products from many sales orders but wishes to return a portion of them from each order. In that case, according to Oracle standard Supply Chain Management, users must create an RMA (Return Material Authorization) for each of the sales orders individually, which may be a time-consuming process. However, businesses users may wish to submit a single RMA (Return Material Authorization) order that includes all returns along with the original sales order reference.

Solution Approach:

To create a single RMA against multiple order related SO lines, we can build a custom screen with “Application Composer” functionality along with Groovy script that calls the REST API. It might save consumers’ significant amount of time, allowing them to devote that time to other important tasks. An illustrative solution approach is explained below; this may differ from business to business.

Screen1: The fields listed below are possible inputs in the “Create” screen built with “Application Composer” feature of Oracle Fusion.

• Business Unit: This can be defaulted based on the user’s BU from HCM.
• RMA (Return Material Authorization) Key ID: A unique ID will be generated and utilized as the primary key, upon which RMA (Return Material Authorization) orders will be made.
• *Customer Name: This field can be mandatory; search for the customer and populate it.
• Invoice Currency: Select the invoice currency.
• Bill-To: Choose Bill-To based on the customer’s name.
• Ship-To: Select Bill-To from the list based on the customer.
• Ship-To-Org: Search and select the value from LOV.
• Original Invoice#: populate the AR invoice number against the original order.
• Return Quantity: Provide the Return Quantity
• Reference Order Details such as the Original Order Number, Item Number, Ordered Quantity, Ship-To Warehouse, Item Description, and UOM can be filled in as needed.
• Similar to above, non-reference order details like item number, quantity, ship-to warehouse, item description, and UOM can also be entered as per the needed.
• Other fields, such as “created by,” “creation date,” “last updated by,” and “last updated date,” can be auto-populated based on WHO columns.

An illustration of “Create” page might be as below:

Screen2: After providing the above information, proceed with “Submit”, it will create an RMA Order, and many other fields can be populated automatically as illustrated below.

Once the above information is provided and processed, a REST API will be called internally using a Groovy script, that will generate an RMA order against multiple sales order lines from different sales orders.

Overall Process flow Diagram of this functionality:

Summary

A custom screen can be built using Oracle Fusion’s “Application Composer” feature, “Groovy Script” and the “REST API” to generate an RMA order against multiple sales order lines of different SOs. This, in turn, will save a lot of effort for users and that can be utilized for other critical business activities.