Advanced Returns Management For Customer Returns PDF
Advanced Returns Management For Customer Returns PDF
Returns
In today's business climate, customers assume that accepting returns is a part of your sales
cycle. Returns from customers are occurring on a more frequent basis. Customers expect
high-quality products that meet or exceed their standards. Customers also order more
product than they require and return the extra. Customers expect quick and efficient
processing of their return deliveries and refunds. An inefficient returns process can affect
your ability to retain existing customers.
Comparing Customer Returns With and Without using Advanced Returns Management
(ARM)
The topic of this unit is Advanced Returns Management (ARM). ARM extends the traditional
returns functionality available in SAP S/4HANA Sales and Procurement: advanced processing
options are available for both customer and supplier returns.
So what is the traditional functionality for processing returns? Let's take customer returns as
an example. When you create a sales order in the SAP S/4HANA system using document type
RE (Returns) , you are creating a returns order using the traditional returns functionality; a
returns delivery can be created, a goods receipt into returns stock can be posted for this
returns delivery and a credit memo can be issues to the customer. No advanced processing
options are available when using this document type, like customer refund control using
refund codes, defining a set of logistical follow-up activities to be initiated automatically,
automatically creating a credit memo request for credit memo approval, etc.
When you create a sales order in the SAP S/4HANA system using document type RE2
(Advanced Returns) , you are triggering a returns process using the Advanced Returns
Management (ARM) functionality.
Advanced Returns Management (ARM) was originally released as a part of Enhancement
Package 4 for SAP ERP/ECC 6.0. Its roots are in the Retail industry solution that SAP created
in the past. Some retail terminology (like the concept of a Store) can still be seen within the
functionality.
Lesson: Advanced Returns Management for Customer Returns
The business functions that contain the Advanced Returns Management (ARM) functionality
are called OPS_ADVRETURNS_1and OPS_ADVRETURNS_ . I2n an SAP S/4HANA system, they
are both part of the set of always_on business functions. In the so-called switch framework
(transaction code SFW5) where you can check the status of certain business functions and
switch them on and sometimes off again, they can be found in the folder S/
4H_ALWAYS_ON_FUNCTIONS. This means that the ARM functionality is available in every
standard SAP S/4HANA system.
Available Scenarios
ARM offers the ability to handle multiple returns scenarios that companies potentially face.
There are many variables that will cause one return to be handled differently from another
return.
In ARM, the user can select the scenarios and outcomes required from within the advanced
returns sales order. In sales order type RE2 (Advanced Returns) , the user can set-up the
required returns scenario on the Returns tab page. Some of the fields here are configured to
work together in various possible combinations. If a user is selecting an incompatible
combination of field values, the system will issue an error message. Some of the functionality
in certain scenarios will not work if the required Business-add in's (BAdI's) have not been
configured.
Possibilities in Customer Returns
The advanced returns order type allows you to determine how the returns process will
proceed further and what the outcome will be. From within a single advanced returns order,
you can manage multiple line items, with each line item possibly having a different outcome
based on what is required for that item. Below is a set of questions that might influence the
chosen field values in the details of a returns order item.
What triggered the returns process?
The material needs to be sent to the supplier from which you purchased the material.
The material needs to stay in the location where the return delivery was received.
The material needs to be returned from an administration point of view, but will physically
remain at the customer.
The material will be returned and moved immediately to a specific stock type such as
available stock or blocked stock.
Inspection needs to happen at the customer's site prior to returning the materials to your
location.
Inspection needs to happen at your supplier after the material are returned to your
supplier.
A refund will be issued immediately upon saving the advanced returns order.
A refund will be issued to your customer after you receive a refund from your supplier.
The Return Reason field allows you to store a return reason for an order item which serves as
identification for the order item. An example is Product Defective .
The Material Received check box identifies that the material is physically in your control and
that the SAP S/4HANA system should immediate create a returns delivery.
The Follow-Up Activity field determines what should be done with the material. Examples are:
Receive into Plant and Immediately Move to Scrap .
The Refund Control field determines if, how, and when a refund should be processed for the
returned materials.
The Refund Code field determines the refund amount as a percentage of the original sales
price of the item. Refund determination can be performed in a separate transaction as well.
Using the SAP GUI, choose Logistics Central Functions Advanced Returns
Management Returns Refund Determination or use transaction code MSR_CR.DOf course,
this transaction can also be made available for the user as a tile in the SAP Fiori launchpad.
The Inspection Code field allows for the recording of the condition of the returned material.
The inspection code could also be used to trigger a refund code. Inspection can take place in
your warehouse using the returns delivery document number, the handling unit number, or
the inspection number as a reference. Inspections can also be entered in the SAP S/4HANA
system using a separate transaction. Using SAP GUI, choose Logistics Central
Functions Advanced Returns Management Material Inspection or use transaction code
MSR_INSPW.HAgain: this transaction can be made available to a user as a tile in the SAP Fiori
launchpad of this user.
There are dependencies between field values on the Returns tab in the advanced returns
order. Depending on one field entry, there may be other fields that will be required for input;
an example is the follow-up activity Ship to Vendor . If you select this follow-up activity, you
also need to enter the vendor (supplier) to which the returned material needs to be shipped. If
you don't do this, the sales order will be considered as incomplete.
Monitoring Returns
You can use the so-called Returns Overview to monitor the status and the progress of a
certain advanced returns process for an item.
Figu Returns Overview
From within the returns overview, you can perform follow-on activities
such as creating the return delivery and credit memo or restarting a
certain document creation step. You can view the returns overview for
an individual line item within an advanced returns order (as can beseen
on the above screen-shot). You can also call the returns overview using a
separate transaction, which also allows you to view multiple return
items and documents simultaneously.
From the returns overview, you can see the related documents that
were created as result of a certain returns process. You can also adjust
the layout of the monitor. To start the returns overview via a separate
transaction, choose: Logistics Central
Functions Advanced Returns Management Returns
Overview and then Display Returns Overview for CustomerReturns if
you want to see the overview for customer returns. You can also use
transaction code MSR_TRC_Cto see the overview for customer returns.
This transaction can be integrated as a tile into the SAP Fiori
launchpad for a user of the SAP S/4HANA system.