SAP ABAP IMG Activity OLQN-WL (Process Return Delivery to Vendor)
Hierarchy
☛ BBPCRM (Software Component) BBPCRM
   ⤷ CRM (Application Component) Customer Relationship Management
     ⤷ CRM_APPLICATION (Package) All CRM Components Without Special Structure Packages
       ⤷ QI (Package) QM IMG and area menu
IMG Activity
ID OLQN-WL Process Return Delivery to Vendor  
Transaction Code S_ALR_87004493   IMG Activity: OLQN-WL 
Created on 19981222    
Customizing Attributes OLQN-WL   Process Return Delivery to Vendor 
Customizing Activity    
Document
Document Class SIMG   Hypertext: Object Class - Class to which a document belongs.
Document Name OLQN-WL    

In this step, you make the settings required to process returns that arise from complaints against a vendor.

Several partial processes for returns are triggered from a quality notification. These include:

  • Stock transfer postings
  • Quality inspections
  • Return deliveries
  • Debits or credit memo requests

At the goods receipt inspection or at the subsequent storage and processing of goods, defects can be identified that can be traced back to the vendor or manufacturer. As a first step, you create a quality notification that documents the problem and forms the basis for the appropriate corrective tasks. To prevent the damaged goods from being used, the department responsible can post the stock available in the warehouse from unrestricted-use stock to blocked stock or to inspection stock. (Stock types).

Note: If the Warehouse Management (WM) component is installed and the inspection lot (or goods receipt document in the case of a skip), can be determined, the system uses this data to find all the individual quantities and goods movements and helps you to collect all defective quantities in one storage location.

You have several options for further processing. If necessary, the partial quantity that can still be used can be sorted and the defective partial quantity sent for rework or scrapped. The defective quantity can also be returned to the vendor with a request for a replacement quantity.

If you decide to return the goods, you can do so either with or without reference to the original purchase order or goods receipt. If you reference the original document, the system reduces the delivered quantity contained in the original purchase order. If you do not use a reference, the system creates a separate return delivery purchase order, which then forms the basis for the actual return delivery.

In both scenarios a delivery is created, the accompanying papers (such as delivery note, complaint against a vendor with defect data, 8D report) are printed, the goods issue is posted and the vendor is sent an invoice. The return delivery purchase order and credit memo request or debit display reference the quality notification from which they were triggered. You can trace the document flow in the notification.

Preconditions

  • Material Master Record
    The material type must be set so that both purchasing and sales an distribution data can be maintained, if the shipping of returned goods to the vendor is to be supported. To do this, you must define a transportation group and a loading group in the general sales and distribution data.
    Inspection type 08 must be active in the inspection setup, so that an inspection lot is created, when the stock is transfer posted to inspection stock.
  • Vendor Master Record
    A vendor master record with an account group as well as a customer master record must exist for the vendors.
    If you set the Returns with shipping processing indicator in the purchasing data for the vendor, the system requests the data for the vendor relating to the customer. This data must have been created with an account group for the sold-to party (or must be created if no data exists). The shipping data (for example, the shipping condition in the sales data area for the customer master record must be maintained. If you want to use the ERS procedure for vendors, you can activate the automatic goods receipt settlement for returns.
    Note: If the control indicators are not ready for input, when you maintain the master record, you must modify the screen control for the vendor account group.
  • Purchasing Info Record
    If the system can access a purchasing info record for the supply relationship, it proposes the appropriate price and terms of payment, even if there is no reference to an original document.
  • Release Procedure
    If you define a release procedure for purchasing you must make sure that the order type return delivery is not included in the release procedure, when defining the release strategy, so that the system can create the return delivery automatically.

Standard settings

The standard system contains all the required quality notification functions. These include:

  • Tasks
    These are contained in catalog 2, in code group QM-G2.
  • Default tasks for the action box with their related function modules. The following functions are delivered with the standard system:
    • Transfer posting from unrestricted-use stock to blocked stock
    • Transfer posting from unrestricted-use stock to inspection stock
    • Making the usage decision
    • Assigning the purchasing document
    • Creating a return delivery
    • Changing the outbound delivery
  • Follow-up actions (and their related function modules) The standard system contains the following follow-up actions:
    • Making the usage decision (UD)
    • Creating the outbound delivery (DELIVERY)
    • Changing the outbound delivery VL02

Recommendation

Copy the standard settings from client 000 into the current client.
If you want to define your own code groups and codes in the task catalog with names, based on the examples contained in the standard system, you must also modify the corresponding follow-up actions.

Use the recommendation for implementing the IMG (hypertext link in the IMG structure) in place of displaying the IMG text in the SAPscript editor, using the screen display function).

Activities

Check the following Customizing settings:

  1. The GR reversal despite invoice at GR related invoice verification must be allowed for the movement types that are used for the return delivery:
    • 161 return delivery without reference to the original document
    • 122 return delivery with reference to the original document
  2. At partner determination for the delivery, the partner determination procedure RLL (return delivery to vendor should be assigned to the delivery types RL (return to vendor - return delivery with reference to purchase order) and RLL (return to vendor without reference to purchase order)
    Note: You can find the assignment of the partner determination procedures to the delivery types in the function for maintaining the partner determination procedure for the partner object "delivery".
  3. Since the plant that receives the returned goods from a delivery subsequently becomes the issuing plant, a sales area (sales organization, distribution channel and division) must be assigned to this plant.
  4. The shipping point must be set for the shipping condition that is used, the loading group and the plant.

Further notes

You can find more information about this subject in the note database under note 113844.

Business Attributes
ASAP Roadmap ID 204   Establish Functions and Processes 
Mandatory / Optional 2   Optional activity 
Critical / Non-Critical 2   Non-critical 
Country-Dependency A   Valid for all countries 
Assigned Application Components
Documentation Object Class Documentation Object Name Current line number Application Component Application Component Name
SIMG OLQN-WL 0 HLA0001806 A HLA0006218  
Maintenance Objects
Maintenance object type    
History
Last changed by/on SAP  19990212 
SAP Release Created in