Lets a customer request a return, checks eligibility against the order line and the warranty, creates the return order, and releases the credit once the goods arrive.
Today a return starts with an email to customer service, who looks up the order, asks the warehouse whether the goods came back and asks finance to raise the credit. The customer learns the outcome when the credit note appears, often weeks later.
The customer picks the order line on the portal screen, enters the quantity and the reason and adds photos. The app reads the sales order line, the delivery date and the warranty, and shows customer service whether the return falls inside the return window for that item and customer. On approval the app creates the return order in the ERP through the released interface and sends the RMA number and the label to the customer. When the warehouse receives the goods on the mobile screen and grades their condition, the app creates the credit memo request for the received quantity, or a replacement order, and tells the customer.
| Lane | Does |
|---|---|
| Customer | requests the return on the portal screen with the order line, quantity, reason and photos |
| Customer service | checks eligibility, approves or offers an alternative, sends the RMA |
| Warehouse | receives the goods against the RMA on the mobile screen and grades their condition |
| Finance | releases the credit memo request or the replacement order |
Every screen renders for desktop and mobile; portal screens are the same screens delivered to an outside login.
| Screen | What is on it |
|---|---|
| S01 Return request | portal screen: recent order lines of the customer, quantity, reason code, photos, preferred outcome (credit or replacement); submit |
| S02 Eligibility | order line and delivery date, days since delivery against the return window, warranty status, customer block, earlier returns on the line; eligible indicator with the reason; approve, offer alternative, decline |
| S03 RMA | return order number, return label, ship-to warehouse, expected arrival date, instructions; sent to the customer and shown on the portal |
| S04 Goods receipt | mobile screen: scan the RMA, count per line, grade A, B or C, photos; post receipt button |
| S05 Settlement | credit memo request for the received quantity at the order line price, or a replacement order; deduction for grade C with reason; approve |
| S06 Board | returns by reason, age and value; RMAs awaiting goods; credits released within 2 days of receipt; share restocked |
The first object is the main one; each system page shows the real table or resource behind every handler.
| Object | Why the app reads it | See it on |
|---|---|---|
| Return order | return orders and their returns deliveries: quantity expected, quantity received, reason, status | S/4HANA · Oracle Fusion · Salesforce · Snowflake |
| Sales order line | the sales order line that shipped: date, quantity, price, value | S/4HANA · Oracle Fusion · Salesforce · Snowflake |
| Customer master | the account: block status, terms, return window agreed | S/4HANA · Oracle Fusion · Salesforce · Snowflake |
| Warranty | warranty on the item where the return is a warranty claim | S/4HANA · Oracle Fusion · Salesforce · Snowflake |
| Object | What changes |
|---|---|
| Return order | return order created with reason, quantity and the original order line; receipt posted against it when the goods arrive |
| Sales order line | credit memo request created against the original order line for the received quantity, or a replacement order at zero price |
Start: A customer submits S01, or customer service enters a return on the customer's behalf.
| Step | Moves when |
|---|---|
| Request submitted | order line, quantity and reason present; photos for a damage reason |
| Eligibility checked | days since delivery within the return window for the item and customer, or the warranty covers the fault; customer service approves |
| RMA created | return order number from the ERP; label and instructions sent; 14-day arrival clock starts |
| Goods received | returns delivery posted with the counted quantity and grade; differences from the requested quantity flagged |
| Settled | credit memo request or replacement order created; a credit above 5,000 or a grade C deduction goes to the customer service lead |
| Closed | customer informed with the credit note number; return order completed |
| Component | Trigger → action → outcome |
|---|---|
| btn_check | on click → read the delivery date of the order line, the return window for the item and the warranty → show eligible or the reason, enable btn_approve |
| btn_approve | on click → call the return order interface with the line, quantity and reason → store the RMA number, send the label and instructions to the customer |
| btn_post_receipt | on tap → post the returns delivery receipt with the counted quantity and grade → open S05 for the received lines |
| btn_settle | on click → create the credit memo request or the replacement order against the original line → notify the customer, close the case |
| Step | Time limit and escalation |
|---|---|
| Eligibility decision | 1 working day, then the customer service lead is reminded |
| Goods arrival | 14 calendar days after the RMA, then the customer is reminded; the RMA expires after 30 days |
| Settlement | 2 working days after receipt, then the finance lead is copied |
Names, places and figures are illustrative; the pattern is the catalogue's.
Tomás, a distributor's buyer in Monterrey, requested a return of 40 damaged cartons at 16:40 on a Friday with 3 photos. Ana, in customer service in Guadalajara, saw on Monday at 08:10 that 12 days had passed since delivery, inside a 30-day window, approved the return at 08:20, and the RMA number and label reached Tomás a minute later. The cartons arrived on Thursday at 10:15; the warehouse operator scanned the RMA, graded 38 cartons A and 2 C, and the credit memo request for the 38 posted the same afternoon. The board showed 9 days from request to credit, against 6 weeks the year before.
The objects with their real names, the criteria in that system's fields, the write interface and what to set up first.
Return order read from VBAK · VBAP (VBTYP = 'H') · LIKP returns; also on SAP ECC.
Open the S/4HANA page →Return order read from Order Management REST: salesOrdersForOrderHub (return lines) · returnOrders; also on Oracle E-Business Suite.
Open the Oracle Fusion page →Return order read from ReturnOrder · ReturnOrderLineItem; CRM.
Open the Salesforce page →Return order read from CONFORMED.RETURN_ORDER; lakehouse.
Open the Snowflake page →Other systems connect through the same handlers; see how SmartApps connect.
About 30 minutes to a first running screen on your live rows, and 5 working days to the production-grade version described here, most of it spent agreeing screens and criteria with the process owner.
Any of SAP S/4HANA, Oracle Fusion Cloud, Salesforce, Snowflake, with the objects read in place; the pages above show the objects and the write path for each. Two systems at once is one handler per object per system.
Roles on portal screens see only the rows the access policy allows, and their steps are logged like everyone else's.
Every step, value, decision, notification and write-back acknowledgement of every instance, with the version of the app, append-only.
Bring the process and the systems it touches. In the first session we register the data handlers, draw the levels or the lanes and run the first screen on your live rows.