Configuration of Advance Return Management
Configuration of Advance Return Management
This document covers the complete configuration of ARM, screen information, and test cases for
better understanding.
Index:
7. Test cases.
8. Important tables.
Normal Return: With traditional returns, an order is created, return delivery is processed, and a
refund is issued to the customer. However, the fate of the returned stock (whether it is scrapped,
moved to another plant, sent for internal or external repair, or returned to the original vendor) is
unclear.
Advance Return Management: Advanced Return Management introduces an additional tab, 'Return,'
which has the capability to handle all kinds of possible business scenarios.
This highlighted gap can be easily addressed and monitored with Advance Return Management.
From the order itself, you can decide whether it should be a replacement or a refund. If the user is
certain about the decision, they can select the follow-up code to generate the document directly
from the order (referred to as a Counter Return).
If the user is unsure, they can first receive the goods in the warehouse and then make a decision
about what should be done with the stock."
2. Explanation of the Return Tab:
ARM introduces a new sales document type, RE2, which includes an additional tab for returns. (You
can activate this tab for other document types by creating a new document type copy of RE2;
detailed configuration will be covered later.)
All the aforementioned activities are made possible through this Return tab and Warehouse
Inspection (which will be explained in detail in a separate section)."
1.Return Reason:
This is the customer's justification for the return or replacement of a product. SAP does not provide
any predefined list; we can configure it as per our requirements. Additionally, it does not have any
impact on document processing; it is merely a drop-down text for informational purposes.
Configuration details are covered in a separate section."
2.Follow Up activity: -
This is one of the important fields in the Return tab, which will determine your document flow.
We use SAP standard FU codes and do not create our own FU codes."
This is similar to the Follow-Up code. If we are certain about the next activity, we can select it
here.
4.Refund Type: -
Refund type determines how you are going to compensate the customer, whether by
providing a refund or by replacing the returned product. Both options are not possible per
line; you can have a multi-line sales order with different types of FU codes, refund codes, and
refund types.
Only two options are available.
5.Refund Control:
Refund Control determines how the compensation decided in the Refund Type is processed.
Here, you decide how the compensation document should be created, whether
automatically or manually. You also determine at what level the system generates the refund
or replacement document, such as from the order or warehouse inspection, after a vendor
refund, etc. The behavior of Refund Control is not absolute; it depends on the Follow-Up
activity and Refund Type. The system allows sensible options only
6.Customer Inspection Code: -
While returning, customers may inspect the product condition on their site before shipping it
back to the seller. This information can be captured in a free-form drop-down text or list. It
can be configured according to business requirements.
It does not create an inspection document. It has no impact on document processing and is
solely for capturing information
7. Customer Comments:
These are free text comments from customers that we can capture. They have no impact on
document processing and are captured for informational purposes only.
8.Inspection code:
When goods reach the plant from the customer location, users will inspect the product.
Depending on the condition of the product, they select an inspection code. This code reflects
the actual product condition entered by the user during goods receipt into the plant. The list
can be configured as per business requirements. It creates an inspection document. If we are
not aware of the actual goods condition when creating the order, it can be skipped. Once the
goods are received into the plant, you can capture the receipt condition/inspection code
during warehouse inspection (MSR_INSPWH)
9.Comments:
Free text / User can enter Additional comments while receiving goods into plant.
10.Next Plants:
In a real-time scenario, after goods are received from the customer location, an initial
screening occurs. Then, depending on the product condition for repair, repackaging, or resale
purposes, it moves to another location. Users need to enter the plant where the stock should
move. This field requires a value when you select the FU code 'ship to other plant,' which can
be inter or intra. If we are not aware of the next plant, it can be skipped. Once the goods are
received into the plant, you can capture the next plant during warehouse inspection
(MSR_INSPWH).
11 Supplier:
Here, the user needs to enter the vendor number when selecting the Follow-Up code as 'ship
to vendor.' If the product being returned by the customer was purchased from a third-party
vendor/manufacturer and the business wants to return it to the vendor to receive a refund
against the same, this information is necessary.
12.Vendor RMA: -
13.Replancement Material: -
If a customer requests a replacement of material instead of a refund for the returned item,
indicating that they wish to exchange the original product for a replacement. The business
may decide to compensate the customer with a different version of the same product for
various reasons. With the help of a suitable combination of Follow-Up code and Refund type,
users can perform this activity.
14.Replacement Quantity:
15 Supplying Plants:
16 Approval:
17.Refund code:
Its Rejection reason drop down list user Can selected & Reject after Releasing Credit memo
Request.
The decision regarding returning goods can be made at the order level (counter return), where you
know the physical status of the goods. If not, then the business should first receive the goods
physically into the plant, conduct quality inspection, and then decide on the refund type and refund
control.
As per my understanding, at a high level, we can divide ARM into two categories: decisions made
from the order versus decisions made from warehouse inspection (MSR_INSPWH).
Follow-up activities can be executed from the order, warehouse inspection (MSR_INSPWH), or both
Follow-
Activity Activity Can be
Up Brief Description
Description perform
Activity
04 Ship to Order Level & 1. In this case, the product is received into the plant and
Other Plant Warehouse then shipped to another plant for purposes such as
Inspection resale, repackaging, or repair.
(MSR_INSPWH) 2. This process constitutes a return Stock Transport Order
(STO) in ARM.
3. Both inter and intra STOs are possible depending on
the company code of the ship-to plant and receiving
plant.
Delivery
into Plant -
Customer requests a return, but the material is unknown
09 Materials Order Level
or interim order.
Still
Unknown
Transfer to
Warehouse When we receive stock in VL02N, the stock is moved to
Free
11 Inspection block status. Now, in the warehouse inspection, we have
Available
(MSR_INSPWH) the option to unblock it.
Stock
Warehouse
Transfer to If the received stock is not up to the mark, we can move it
12 Inspection
Scrap to scrap.
(MSR_INSPWH)
Material
Without receiving the stock, a refund or replacement can
Remains at
13 Order Level be given to the customer. The system does not create a
Customer
delivery, and there is no warehouse inspection.
Site
Immediately
Move to Received stock can be directly moved to the target
14 Order Level
Specified storage location from the order level.
Stock
Transfer to Warehouse
Received stock can be directly moved to the target
15 Specified Inspection
storage location from the inspection level.
Stock (MSR_INSPWH)
Transfer to Warehouse
18 Scrap for Inspection The stock is removed from inventory.
Customer (MSR_INSPWH)
The Warehouse Inspection (MSR_INSPWH) screen is used when you have selected the Follow-up
code '001,' which signifies that the goods have been received into the plant.
When a return sales order is created (RE2), an automatic delivery is generated, and goods receipt
(PGR) against the received stock is performed. At this point, the stock is moved to a block status.
The next step involves conducting a quality inspection of the stock and making a final decision on
whether to accept or reject the received stock.
To access the Warehouse Inspection screen, you can enter the transaction code MSR_INSPWH.
When you access the Warehouse Inspection (MSR_INSPWH) screen, you will encounter a selection
screen where you can choose options based on your requirements by selecting the appropriate radio
button.
The inspection document typically consists of two main sections: the header section and the item
section. These sections provide information about the inspection document as a whole (header) and
details about each individual item being inspected (item).
. Header: -
1. Header: -
Basic Data: This section displays information that flows from the sales order to your inspection
document. You do not have the option to edit this data.
Inspection Result: In this section, the user captures the inspection results and updates other relevant
details.
Logistical Follow Up: In this section, decisions are made regarding the next actions for the received
stock from the customer based on the inspection results.
Note :
Note:
If you enter the above information at the header level, it will automatically flow to the item level.
However, if you have different observations of inspection for each item, or if you want to carry out
different results for each item, or if you want to further split the received line and make decisions for
each unit, you must perform inspection at the item level.
Item: -
Similar to the header, the item section allows you to capture results specific to each item. Here, you
can specify the outcome for each individual item. Additionally, you have the option to perform a
partial refund for some quantity and provide a replacement for the remaining quantity.
For example, if you received 10 units from the customer, you can choose to refund 5 units and
provide a replacement for the remaining 5 units.
Configuration
1. Must Configuration once of ARM is activated: -
Note:
Once ARM is activated, standard configurations and document types are already in place, requiring
no further action.
If the business requires a custom document type, they can copy the standard document type and
create a new parallel leg.
However, once ARM is activated, a few essential configurations still need to be completed.
1.When initiating an advanced returns process, the system assigns a unique number to identify the
process. This number is derived from the number range defined for advanced returns process IDs.
2.The advanced returns process begins with the creation of a returns order, returns purchase order,
or returns stock transport order.
3.All advance return orders are assigned an MSR_ID, which can be used for tracking purposes in all
ARM-relevant tables.
4.The relationship between MSR_ID and advance return orders can be found in the VBAK table.
Logistics – General -> Advanced Returns Management -> Material Inspection->Basic Setting For
Martial Inspection->Basic Setting For Martial Inspection->Specify catalog and code groups for
material Inspection.
Advanced Returns Management General Settings Define Number Ranges for Advanced Returns
Process IDS
1. Inspection code need to maintain.
2. Specify Catalog and Code Group for Material Inspection Specify Catalog and Code Group
for Inspection by Customer.
Catalogs -Collection of codes with related contents. Catalogs are used to encode qualitative contents
described in text
Inspection by you-Is Receipt conditions, once the Goods Receive into plant (MSR_INSPWH -tcode).
Inspection by customer-If customer already done quality inspection from there end & share Input
we can capture while Sales order Creation Itself the can reflected in MSR_INSPWH in separate Fields
We can have different Code group for customer Inspection & Material Inspection
1. In this Customizing activity, we define and configure the catalogs that are used for inspection
codes
(Inspection by you and inspection by customer)
Logistics – General, choose Advanced Returns Management Material Inspection Basic Setting For
Martial Inspection Basic Setting For Martial Inspection Specify catalog and code groups for material
Inspection.
Define Catalog- R
Edit Catalog- Choose Edit Catalog to enter a code group (YWHINSP) for the catalog defined for your
inspections and assign the inspection codes to that code group
Example: -
Code Description
01 01-Box Closed
02 02-Product Good
03 03-Product Sealed
Choose Edit Catalog to enter a code group for the catalog defined for the inspection by the
customer and assign the inspection codes to that code group.
1. Specify that the catalogs and code groups that you define here are relevant for material
inspection in Advanced Returns Management.
Enter the catalog and the code group for the inspection codes,
Logistics – General ->Advanced Returns Management-> Material Inspection ->Basic Setting For
Martial Inspection-> Specify catalog and code groups for material Inspection.
Enter the catalog and the code group for the inspection codes of an inspection performed by the
customer.Logistics -> General-> Advanced Returns Management ->Material Inspection-> Basic Setting
For Martial Inspection ->Specify catalog and code groups for Inspection by Customer.
1. Inspection document Number range. –
We define the specific number interval 02 of the number ranges for inspection outcomes that is
relevant for ARM.
1. After an inspection outcome, the system assigns a unique number that identifies the
inspection outcome for Each line or split line.
2. This number is taken from the number range Assigned in this node.
3. Only an internal number assignment is supported for the inspection outcome; that is, the
ERP system automatically assigns a consecutive number from the defined number range.
4. If we need to transfer data from inspection documents to SAP CRM (for billing returns stock
transport orders), document numbers must have a maximum of 10 digits.
SAP has not assigned any Number range by default. We need to maintain as per Business
Requirement.
We define Return Reason for customer Return, it basically text Id along with text used for Return
Order Creation.In Customizing for Logistics – General, choose Advanced Returns
Management Customer Returns Define Return Reasons for Customer Returns.
Material Management:
SPRO->Material Management ->Purchasing ->Purchase Order->Return Order->Advance Return
Management
Now Let’s discuss each Configuration in detail from SPRO->Logistic General->Advance Return
Management View.
1. General Settings: -
1.In this Configuration you activated/Deactivate FU code & also you have option to Rename it as per
business Requirement.
2.Maintain Number Range for MSR ID, this is very Important Number Range to be maintain.
Whenever we Create Advance Return order each Order get associate with MSR_ID (Process ID No.)
you can find in VBAK-MSR_ID.
The Number range which we maintain it assign to each order. SAP Offer New tables for advance
return management (which I will cover in details) . In each transaction data MSR_ID is key fields.
Eg
3.When we Create Advance Return Order based on Follow up code, follow document get generated
eg Return delivery, Purchase orders, CMR, etc
Here basically you associate what document type the system should consider when user selected
Follow up code.If you are not using standard document type RE2 , then definitely you need to
maintain entry here
IG2: Cross Company Invoice (if Receiving plant & sales organization company code are different)
The system uses the specified supplier return reasons for the returns purchase orders or returns
stock transport orders that the system creates automatically as logistical follow-up documents for
customer returns orders.
5.while Creating a return order, if you Selected Follow up code 02 or 14 what should be Movement
type you can assign here.
This assignment is again your Schedule line category. Based on Schedule line category. Which you
determine in you advance return order you can assign here.
7. The Use case is when you move stock to free available stock from warehouse Inspection or When
you are receiving stock into plant STO process. We can define stock type against plant.
9.Like above (point Number 3) you specify Repair Order against Return Order RE2.
If you are Using Z order type & business into Repair activity, you must assign document type here.
Create Goods Movement: If you tick system Create martial document from Block to Repair order.
Without Tick
Create Repair Item: If you tick system Created Repair Item into Repair order.
10.In External Repair Vendor is Involved, you need to assign Purchase Order type here.
2.Customer Returns: -
1.In this configuration you activated you Order type in Advance Return Oder.
All the Sales Order type for which Sales document Category is H, you see list here in this
Configuration.
2. In this configuration you activated you Credit Memo Request type for Advance Return Oder.
All the Sales Order type for which Sales document Category is K, you see list here in this
Configuration.
All the Sales Order type for which Sales document Category is I, you see list here in this
Configuration.
5.Specify Requirement Types for Non-Valuated Returns Stock: - You have Specify Requirement type
but as we are doing Return mostly business don’t need this as ATP is not Required.
6.Activate and Rename Refund Control: By Default, you can use Whatever Refund SAP offer. Even you
go new entry you have same list available.
7.Specify Movement Types for Immediate Goods Receipts: Repeated Configuration node
Configuration Covered above.
8.Define Return Reasons for Customer Returns: Repeated Configuration node Configuration Covered
above.
9.Define Returns Refund Codes: We define Return Refund Code for customer Return, it basically text
Id along with text used for Return Order Creation. No Impact on document flow.
You can Use this attribute for you control refund amount let’s say you have 03 code Description 30%
Refund. You can use this code to reduce final price by calling this in Routine of Pricing procedure.
10 & 11. Both Matrix to determine for auto document Creation based Inspection code, Return
Reason, Follow up code.
New Matrix
Old Matrix: Determine Refund code based on Inspection code by user After Physical inspection &
Return Reason
12.same like above, based on Customer Inspection code you determine Refund code
Note:- I Personally don’t find all this matrix much Useful, but if it suits for your business Requirement
Definity use it.
13.We configure the default values follow-up activity, the Material Received checkbox and refund
control based on plant and sales office.
Again, this Matrix only but useless as in real time business decide Follow action not based on plant &
sales office.
It should be based on type of Product Return, Quality Inspection result & Business Situation (like
Demand in market for the Product).
14.Specify Plants Requiring Approval Check: If any user is Create Return Order & he is not Authorize
to Create Return Order for that plant. Approval block will be active for order. Authority
object MSR_PLANT
15.Specify Settings at Client Level: Need to Explore never use it.
16.Assign Payment Types to Returns Order Types: Again, It’s Matrix only. By default, you can assign
Payment type based on Different advance Return Type. Mostly used in Retail business.
3.Supplier Returns: -
1. Activate Advanced Returns Management for Purchase Order Types: -In this configuration you
activated Purchase Order type for ARM (NB2,UB2 NB2C ) .if you are using your Own PO type
2.Define Return Reasons for Supplier Returns: -Similar to Customer return Reason you Create
attribute for Vendor Return Reasons. This List will available in PO Dropdown.
3.Define Rejection Reasons for Supplier Returns: - Create attribute for Vendor Return Reasons. This
List PO Dropdown.
4.Specify Settings for Replacement Materials from Vendor: In this Configuration you Define PO type
for Replacement Materials from Vendor & Tightly Fitting ARM PO types.
In this Configuration Document you mind more details ( I have not tested yet Will Update more
about this in Future after testing same).
5.Specify Default Billing Types for Intercompany Store Returns: - In this configuration, you assign
Intercompany billing type for Cross Company STO against Delivery.
7.Configure Default Values for Returns Refund Codes:-It is Matrix based on Inspection Code & Order
Reason you determine Refund Code into Advance Return Purchase Order.
4.Material Inspection: -
1. Define and Configure Catalog for Inspection Codes: Already Covered in Must Configuration
Section
2. Specify Catalog and Code Group for Material Inspection: Already Covered in Must
Configuration Section
3. Specify Catalog and Code Group for Inspection by Customer: Already Covered in Must
Configuration Section
4. Configure Authorization for Follow-Up Activities: -In this Configuration you Create
Authorization profile, under that Authorization profile whatever Follow-Up Activities that is
only allow that only user can perform. Kind of Authorization
5. Define Number Range for Inspection Outcome: Already Covered in Must Configuration
Section
6. Configure Print Settings: Print Option is available from warehouse Inspection; you Can
configure Adobe Form at company code level.
7.Define Blocks for Follow-Up Activities: If you are Not sure on Follow-Up Activities you assign block
at warehouse Inspection this will stop further processing.
8.Define Screen Layout for Material Inspection: Here we have option to Modified specific field similar
to Account group. I personally will say don’t touch this config unless you have any specific
Requirements.
Test case :-
Create Order with FU code 001 :- (Stock will received into plant & after quality Inspection you can
make decision).
System will Create Auto delivery LR2 as RE2 type (VOV8) is configured as immediate Delivery.
Once PGR(VL02N) is done you Delivery will be ready for Warehouse Inspection.
Tcode: MSR_INSPWH
In this Screenshot, you can see Above option available as next Logistical activity.
On Refund:-While Order Creation we haven’t Decide now we Can release CMR from here or we
Release CMR & put Rejection if don’t to refund Customer.
Both Replacement & Refund are possible. Just you need divide total line qty into Refund &
Replacement correctly.it should less or greater than line-Item Qty.
Let me choice Send back to customer. From Return Order-> Return tab-> click on Return Overview
If we selected Ship to Vendor.
Normal STO
Cross Company STO: Intercompany Invoice get added as stock is transferred between two
companies.
If we selected Transfer to Specified stock.
Non WM
1. For WM to manage plant system Create Outbound Delivery to ensure we should be able to
Create Transfer Order /Pick stock from different BINS
2. I personally think SAP should given a same option in Non-WM Manage Plant. In Realtime
when do stock movement there will be physical movement (for move to scrap or specified
stock).
3. If Delivery document will their delivery it be Can consolidate into Shipment (base on business
Criteria with help this logistic Can be managed in Non WM or WM manage Plants.
WM
1. No Compensation allow in Inhouse or External Repair (you can’t Create CMR ->CM or
Replacement Order)
2. Only Option is Create CMR & Put on Rejection From warehouse Inspection.
If we selected, send back to Customer: I found this case Gap We Need to do PGI for Send
back to customer delivery & Goods Movement document is no link in the Overview.
Now Let me perform a few activities from the Order level directly.
8.Important table:
All tables of ARM start with MSR* you can directly search in SE16N.
Table Usage