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:
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.
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.
screen control for the vendor account group.
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.The standard system contains all the required quality notification functions. These include:
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).
Check the following Customizing settings:
GR
reversal despite invoice at GR related invoice verification must
be allowed for the movement types that are used for the return
delivery:
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)
sales area (sales organization, distribution channel and
division) must be assigned to this plant.
shipping point must be set for the shipping condition that is
used, the loading group and the plant.You can find more information about this subject in the note database under note 113844.