Logistics and warehouse on S/4HANA

Returns authorization on SAP S/4HANA

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 HANDLERSS/4HANA · READ IN PLACES01 Return requestS02 EligibilityS03 RMAS04 Goods receiptS05 SettlementS06 Boarddh_return_orderReturn orderVBAK · VBAP (VBTYP = 'H') · LIKP returnsdh_sales_order_lineSales order lineVBAK · VBAP · VBEPdh_customer_masterCustomer masterKNA1 · KNB1 · KNVVdh_warrantyWarrantyBGMK · BGMS (master warranties) ·EQUI.GWLENWRITE BACK TO S/4HANAReturn order → BAPI_CUSTOMERRETURN_CREATE · BAPI_SALESORDER_CHANGESales order line → BAPI_SALESORDER_CHANGE · BAPI_SALESORDER_CREATEFROMDAT2rows stay in S/4HANA · access rules applied at read time · each write acknowledged and logged
The screens of the app, the data handler behind each, and the S/4HANA object it reads in place. Writes below the line go through released interfaces with an acknowledgement.
4
objects read in place from S/4HANA
catalogue
6
screens on those rows
catalogue
5 days
to production-grade
estimate
2
objects written back
catalogue
0
rows copied to build it
product
What the app reads

The S/4HANA objects behind each handler

Tables are read in place through the SAP connector, using released read interfaces; changed rows arrive through change capture where the basis team allows it. The rows stay in SAP.

ObjectRead fromFields the app usesFreshness
Return orderVBAK · VBAP (VBTYP = 'H') · LIKP returnsVBAK.VBELN (number) · VBAK.KUNNR (customer) · VBAP.MATNR (material) · VBAP.KWMENG (qty)live; change capture where enabled
Sales order lineVBAK · VBAP · VBEPVBAK.VBELN (number) · VBAP.POSNR (line) · VBAK.KUNNR (customer) · VBAP.MATNR (material)live; change capture where enabled
Customer masterKNA1 · KNB1 · KNVVKNA1.KUNNR (id) · KNA1.NAME1 (name) · KNA1.LAND1 (country) · KNVV.VKORG (sales org)live; change capture where enabled
WarrantyBGMK · BGMS (master warranties) · EQUI.GWLENEQUI.EQUNR (equipment) · EQUI.SERNR (serial) · EQUI.GWLDT (warranty start) · EQUI.GWLEN (warranty end)live; change capture where enabled
The trigger

The start criterion in S/4HANA's own fields

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

This app starts from a screen, so the first read happens when the instance opens; the criteria on the arrows use the fields above.

Start

A customer submits S01, or customer service enters a return on the customer's behalf. The instance then reads its rows from S/4HANA through the handlers above.

What the app writes back

Through released interfaces

Writes go through released BAPIs and IDocs. Each call returns a document number or an error message, and the app records both beside the decision.

ObjectWhat changesInterface
Return orderreturn order created with reason, quantity and the original order line; receipt posted against it when the goods arriveBAPI_CUSTOMERRETURN_CREATE · BAPI_SALESORDER_CHANGE
Sales order linecredit memo request created against the original order line for the received quantity, or a replacement order at zero priceBAPI_SALESORDER_CHANGE · BAPI_SALESORDER_CREATEFROMDAT2
Acknowledged and logged

Each write stores the identifier S/4HANA returns beside the decision, the person and the time, so the log answers who changed what, and the reconciliation shows it arrived.

Access and prerequisites

What is in place before the first build

SAP roles are mapped to Lima access policies once. A buyer who sees purchasing organisation 1000 in SAP sees the same rows in the app.

  • An SAP user for the connector with read authorisation on the objects the app uses
  • The BAPIs the app writes with, enabled for that user
  • Network path to the application server (PrivateLink or VPN)
  • Change capture switched on for the objects that should refresh within minutes
Register the handlers4 objects from the catalog; each shows its rows at once.
Also on SAP ECC

The same app on SAP ECC

On SAP ECC the same objects live in the classic tables named beside each row; MATDOC becomes MKPF and MSEG, ACDOCA becomes BKPF and BSEG. The BAPIs are the same.

ObjectOn S/4HANAOn SAP ECC
Return orderVBAK · VBAP (VBTYP = 'H') · LIKP returnssame tables
Sales order lineVBAK · VBAP · VBEPsame tables
Customer masterKNA1 · KNB1 · KNVVsame tables
WarrantyBGMK · BGMS (master warranties) · EQUI.GWLENsame tables
Nearby

This app on other systems, and other apps on S/4HANA

Returns authorization on

Other apps on S/4HANA

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.
Read in placeThe rows stay in S/4HANA; the handler sends the filter and the columns and S/4HANA returns the matching rows.
Questions

Does this app copy data out of S/4HANA?

The screens read through handlers that leave the rows in S/4HANA. History the app needs at scale is landed in the lake by the Backbone, which is the exception by design.

What does S/4HANA need to allow?

The prerequisites above: an integration identity with read rights on the objects listed and write rights on the interfaces named, connectivity, and the scopes agreed with the process owner.

Can I run it on SAP ECC as well?

Yes. The screens, criteria and roles stay; the handlers are re-bound to the other system's objects, listed above.

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.