Goods Receipt: How the Head Office Handles the Sto (SAP Library

Goods Receipt: How the Head Office Handles the Store Goods Receipt

Use

When the central R/3 system processes the intermediate documents (IDocs) concerning the store goods receipts, it attempts to match up the goods receipts with reference documents in the R/3 system. It can assign the goods receipts to the following documents:

Purchase orders placed with an external vendor
Orders placed with an internal vendor (distribution center)
Deliveries
Shipping notifications
Rough goods receipts

The reference document can be contained in the IDoc. If it is missing from the IDoc, the system attempts to find the associated purchase order. If more than one possible purchase order is found, the system triggers action on the part of the user so that the exception is processed.

If no purchase order is found, the system proceeds in one of two ways, depending on how it is configured: User action is triggered so that the exception is processed. A purchase order is created in the background. In this case, the goods receipt is then posted referencing the new purchase order.

Features

Open Quantity Check

The system checks the quantity that is still to be received. If the open quantity is smaller than the goods receipt quantity or the quantity being reversed, the system triggers the exception processing function:

· If the goods receipt is for a purchase order, it checks the quantities in the purchase order history.

· If the goods receipt is for a delivery, it attempts to find the purchase order for the delivery.

- If it finds the order item for the delivery item, it checks the purchase order history.

- If no order item exists for the delivery item, it checks the document flow of the delivery and is thus able to calculate the open quantity.

When a store goods receipt in posted in the central R/3 system, either the purchase order history or the document flow is updated (depending on the document referenced).

Identifying an Item

An item in a store goods receipt can be identified via the following data in the intermediate document:

· EAN

This is the usual way in which an article is identified, if no other information is given to the contrary. When this is indicated in the intermediate document, the system can automatically determine the unit of measure assigned to the EAN. If a different unit of measure was transferred in the IDoc, this is ignored by the system.

· Article number in the central R/3 system

The system uses this to determine the base unit of measure for the article.

· Vendor article number

Since this number can only be unique for the one vendor, it is best also to include the vendor number in the intermediate document.

· Shipping unit number in the central R/3 system

A shipping unit always has a unique number and can be broken down into the individual articles and quantities in the central R/3 system if the shipping unit number and the items contained in it have been maintained there. Shipping units can be made known to the system in shipping notifications from a vendor, for example.

An intermediate document must always contain a quantity. The only exception to this is when it contains a shipping unit. The quantity of a shipping unit is always 1.