App catalogue Logistics and warehouse

Returns authorization

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.

SCREENSDATA HANDLERSSOURCE OBJECTS, READ IN PLACES01 Return requestscreenS02 EligibilityscreenS03 RMAscreenS04 Goods receiptscreenS05 Settlementscreendh_return_Return orderdh_soSales order linedh_customerCustomer masterdh_warrantyWarrantyS/4HANAVBAK · VBAPS/4HANAVBAK · VBAP · VBEPS/4HANAKNA1 · KNB1 · KNVVS/4HANABGMK · BGMSrows stay in the source · access rules apply at read time · writes go through the source's released interface and are confirmed
The screens, the data handlers behind them and the objects each handler reads in place on S/4HANA. Other systems have their own page.
5 days
of configuration to a production-grade version
estimate
6
screens, desktop and mobile
catalogue
4
data handlers, read in place
catalogue
4
systems with a page for this app
catalogue
3
clocks with escalation
catalogue
What it does

Today, and with the app

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.

Who takes part

Process app: lanes and boxes first, then screens per box, then roles, then the criteria on each arrow

LaneDoes
Customerrequests the return on the portal screen with the order line, quantity, reason and photos
Customer servicechecks eligibility, approves or offers an alternative, sends the RMA
Warehousereceives the goods against the RMA on the mobile screen and grades their condition
Financereleases the credit memo request or the replacement order
Screens

6 screens, composed from the handlers

Every screen renders for desktop and mobile; portal screens are the same screens delivered to an outside login.

ScreenWhat is on it
S01 Return requestportal screen: recent order lines of the customer, quantity, reason code, photos, preferred outcome (credit or replacement); submit
S02 Eligibilityorder 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 RMAreturn order number, return label, ship-to warehouse, expected arrival date, instructions; sent to the customer and shown on the portal
S04 Goods receiptmobile screen: scan the RMA, count per line, grade A, B or C, photos; post receipt button
S05 Settlementcredit memo request for the received quantity at the order line price, or a replacement order; deduction for grade C with reason; approve
S06 Boardreturns by reason, age and value; RMAs awaiting goods; credits released within 2 days of receipt; share restocked
Data handlers

4 objects, read where they live

The first object is the main one; each system page shows the real table or resource behind every handler.

ObjectWhy the app reads itSee it on
Return orderreturn orders and their returns deliveries: quantity expected, quantity received, reason, statusS/4HANA · Oracle Fusion · Salesforce · Snowflake
Sales order linethe sales order line that shipped: date, quantity, price, valueS/4HANA · Oracle Fusion · Salesforce · Snowflake
Customer masterthe account: block status, terms, return window agreedS/4HANA · Oracle Fusion · Salesforce · Snowflake
Warrantywarranty on the item where the return is a warranty claimS/4HANA · Oracle Fusion · Salesforce · Snowflake

Written back

ObjectWhat changes
Return orderreturn order created with reason, quantity and the original order line; receipt posted against it when the goods arrive
Sales order linecredit memo request created against the original order line for the received quantity, or a replacement order at zero price
The flow

From the trigger to the last write

THE FLOW · RETURNS AUTHORIZATION1Requestsubmittedorder line, quantityand reason present;photos for a damagereason2Eligibilitycheckeddays since deliverywithin the returnwindow for the itemand customer, or thewarranty covers thefault; customerservice approves3RMA createdreturn order numberfrom the ERP; labeland instructionssent; 14-day arrivalclock starts4Goods receivedreturns deliveryposted with thecounted quantity andgrade; differencesfrom the requestedquantity flagged5Settledcredit memo requestor replacement ordercreated; a creditabove 5,000 or agrade C deductiongoes to the customerservice lead6Closedcustomer informedwith the credit notenumber; return ordercompleted
Each step and the criterion that moves it.

Start: A customer submits S01, or customer service enters a return on the customer's behalf.

StepMoves when
Request submittedorder line, quantity and reason present; photos for a damage reason
Eligibility checkeddays since delivery within the return window for the item and customer, or the warranty covers the fault; customer service approves
RMA createdreturn order number from the ERP; label and instructions sent; 14-day arrival clock starts
Goods receivedreturns delivery posted with the counted quantity and grade; differences from the requested quantity flagged
Settledcredit memo request or replacement order created; a credit above 5,000 or a grade C deduction goes to the customer service lead
Closedcustomer informed with the credit note number; return order completed
Actions, clocks and measures

What the components do, what the clocks enforce, what the board shows

ComponentTrigger → action → outcome
btn_checkon 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_approveon 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_receipton tap → post the returns delivery receipt with the counted quantity and grade → open S05 for the received lines
btn_settleon click → create the credit memo request or the replacement order against the original line → notify the customer, close the case

Clocks

StepTime limit and escalation
Eligibility decision1 working day, then the customer service lead is reminded
Goods arrival14 calendar days after the RMA, then the customer is reminded; the RMA expires after 30 days
Settlement2 working days after receipt, then the finance lead is copied

Measures

returns decided within 1 daydays from RMA to credit notereturns by reason codeshare of returned goods restockedcredit value per month
A day with the app

Illustrative

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.

illustrative scenario · Returns authorization
On your systems

One page per system

The objects with their real names, the criteria in that system's fields, the write interface and what to set up first.

Other systems connect through the same handlers; see how SmartApps connect.

Terms on this page

RMAReturn merchandise authorisation: the return order number that lets a customer send goods back and tells the warehouse what to expect.
Credit memo requestThe sales document that leads to a credit note on the customer's account for the returned quantity.
Return windowThe number of days after delivery in which a return is accepted for an item and a customer.
Questions

How long does it take to have this running?

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.

Which system does it run on?

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.

Who takes part from outside the company?

Roles on portal screens see only the rows the access policy allows, and their steps are logged like everyone else's.

What does the audit record hold?

Every step, value, decision, notification and write-back acknowledgement of every instance, with the version of the app, append-only.

See this app on your data

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.