Skip to main content

SAP SD - Advance Return Management for customer Returns

In all Sales Business Cycles, Returns from customers are Normal, Returns can be expected when

1.  Customers expected Quality is  not met by the  product delivered

2. Some times Customers Orders more products than it is required

3.  DOA or Miss shipments ( wrong Products delivered).

In above all cases, Customers will return the material,  and these returns can be handeleted by ADVANCE RETURNS MANAGEMENT



ADVANCE RETURN ORDER : 

                         Advance Return Order is the document  which initiates the Customer Returns
                        It Controls , how a return should happen and its Results

We have to enter

 RETURN  REASON :  Reason for Customer Reason

MATERIAL RECEIVED :  Identifies that the Physical material in the warehouse and initiates immediate delivery

FOLLOW UP ACTIVITY: This activity control, how the return material should be treated Whether to repair, scraped or to send for  inspection

REFUND CONTROL:  this will ensure how the refund is processed for returned material

There are 5 Scenarios in Advance Material returns process

1. Materials received

2. Advance Notice

3. Inspection at customer

4. Direct return to vendor

5. Material status still unknown 


1. Advance Return Document type :RE2  ( As per the standard ) in VA01




2.  Inspection of the material , Received from the customer under the path


LOGISTICS-->CENTRAL FUNCTIONS-->ADVANCE RETURN MANAGEMENT-->ENTER MATERIAL INSPECTION IN WAREHOUSE



all above scenarios are differentiated based on different Follow up activities



The Configuration of Advance Return Order lies in SPRO---Sales and distribution-->sales-->Advance Returns management


We will discuss how Advance Returns will work for Supplier returns

please post your questions under comments sections

Labels:

Comments

Post a Comment

Popular posts from this blog

SAP PM/CS / EAM : Refurbishment Process

Refurbishment A refurbishment order is a standard Maintenance Order type. In customizing for order, we first create an order type ( such as PM04) In the configuration we have to create a new order type in OIOA and activate this for Refurbishment process. Process flow: Business process steps 1. Damaged equipment/ spares if can be repaired will be done by the PM order of type PM04 2. Equipment/Spares needs repairing should have the item code if it is serialized item then with the serial number. 3. Item should have the valuation type for repair category too. 4. Create PR through refurbishment order for repair of the item with split valuation type of repair. Proper G/L codes and order for the repair indent should be provided in the indent 5. After approval of the requisition, the requisition and item should be send to the stores/Purchase section for further actions. 6. Stock will get updated after MIGO of the item 7. The activity type cost
2 comments
Read more

TO MAKE INACTIVE CONDITION ACTIVE IN SAP

This blogger contains details on how to set an INACTIVE CONDITION  to ACTIVE while processing Sales Order content: 1.  BUSINESS REQUIREMENT Due to some legal restrictions in Russia, Russia Local Plant cannot hold any stock for the material and hence it is non valuated which means the Standard Price is Zero ( 0 $ ) The stock will be replenished from another company code and we used our Standard Third Party process  in which PR is created which will be converted to PO and when we do GR, the Standard Price of that plant is calculated in the GR. The baseline pricing structure is mapped in such a way that VPRS is calculated from the Material master and on which 15% markup is added as base price. Since the Cost price in VPRS condition is Zero Markup calculated on VPRS will be obviously calculates to Zero and both conditions were set as INACTIVE as per the condition properties 2.  CREATE SALES ORDER we will create a sales order for a material, whose standard Price
3 comments
Read more

SAP SD/CS/PS /PM : System status and User Status a differentiation

In SAP, Master Data and Transaction data is controlled by system status.  But there are certain limitation where system status cannot be used, In such instances a User status can be used. We will see how a system status and User status functions in a particular transaction. Let's understand what is "SYSTEM STATUS" and  "USER STATUS" from system perspective. SYSTEM STATUS:-                                                       A system status is set by the system automatically upon executing a function. It                            Specifies that a particular function was carried out on an Object, be it a                            Transaction ( like Service Order) or a master Data ( serial Number).                            User Cannot Control or interfere system status .  This status cannot be deleted or                              changed.  For example, When i release either Service Order or Production Order system status "REL" i
3 comments
Read more