Inbound Delivery

Definition
The inbound delivery is a document containing all the data required for triggering and monitoring the complete inbound delivery process. This process starts on receipt of the goods in the yard and ends on transferal of the goods at the final putaway, production or outbound delivery.

Use
The inbound delivery is used as a working object in the inbound delivery process. You use this document in delivery processing when executing the following actions: Registering the delivery in the yard Unloading the delivery Canceling the unloading of the delivery Placing the delivery into stock (putaway) Canceling the delivery putaway Adjusting the delivery quantity to the quantity posted in the goods receipt (in case of overdelivery or underdelivery. Adjusting the delivery quantity and the transferred quantity In this case, the delivery quantity is adjusted to the quantity posted in the goods receipt. The quantity in the inbound delivery notification is also adjusted and a new inbound delivery is created. Posting a goods movement Canceling a goods movement Creating items Deleting items You can save, validate and delete an inbound delivery.

Structure
For a description of the structure, see Documents in Delivery Processing.

Integration
The inbound delivery is created after activating an inbound delivery notification. The inbound delivery adopts all the relevant data from the inbound delivery notification. The execution of the actions depends on the settings in the Post Processing Framework (PPF).

Documents in Delivery Processing

Use
A document contains all the data required to document and control a business process. Various documents are used in delivery processing to control the processes. The inbound delivery process is represented in the system by the following documents:
Inbound delivery notification

Inbound delivery

The outbound delivery process is represented in the system by the following documents:
Outbound delivery Request Outbound delivery order Outbound Delivery

The posting change process is represented in the system by the following documents:
Posting change request Posting change

The internal stock transfer process is mapped in the system using the Internal Stock Transfer document. Every document provides various actions that are used to control the individual subsequent processes. The execution of the actions depends on the settings in the Post Processing Framework (PPF).

Structure
A document comprises a document header and any number of document items. The following figure shows the structure of a delivery document.

Document Header The document header contains general data and data that is relevant for the following documents:
Inbound delivery

Outbound delivery Posting change Internal stock transfer

This data is valid for the entire document. This data includes:
Goods receiving office or shipping office Scheduling data (for example, shipping or delivery date) Weights and volumes for the complete inbound/outbound delivery Ship-from party, sold-to party and goods recipient numbers

The document header is defined in the system by the document category and the document type. The document category classifies the different documents that can be processed by the system in delivery processing. It is defined by the system and cannot be changed. The following document categories exist in delivery processing:
Inbound delivery notification Inbound delivery Outbound delivery request Outbound delivery order Outbound delivery Posting change request Posting change Internal Stock Transfer

The document type classifies the documents with regard to the complete delivery process. The document type defines the business aspects of a document. The following figure shows a possible relationship between the document category and the document type in the inbound delivery process. In this case, only one document type (Z100) is used for the complete inbound delivery process.

Using the document type determination, you can derive several document types from a document category and therefore define certain delivery processes. The following figure shows a relationship between the document category and the document type whereby two different document types were derived from one document type.

The document type Z100 is defined for the document category inbound delivery notification. Document types Z200 and Z300 are defined for the document category inbound delivery. The document type determination defines that document types Z200 and Z300 are to be derived from document type Z100 in the inbound delivery process. In Customizing for Delivery Processing, you can define your own document types and document type determination. Document Items In the document items, you find the data relevant to the individual items. It includes:
Material number Delivery quantity Location specifications (goods receiving point, unloading point) Putaway date or picking date Weights and volumes of the individual items Tolerances for underdelivery or overdelivery

The document items are defined in the system by the item category and by the item type. The item category classifies the different items that can be processed by the system for delivery processing. It is defined by the system and cannot be changed. The following item categories exist in delivery processing:
Normal delivery item Return item

Text item Packaging item Value item (in documents of the outbound delivery only)

The item type classifies the items for a document type with regard to the complete delivery process. The item type defines the business aspects of the document items. As for the document header, for the document items, you can also configure your business process via the item type and the item type determination in Customizing for Delivery Processing. Service Profiles Service profiles define how a document is processed in the system as well as its business scope. Two types of service profile exist:
System profile Customer profile (for example, status profile, text profile and incompleteness profile)

The system profile is not configurable and is linked to the document categories and item categories. The customer profiles are linked to the document types and to the item types. In Customizing for Delivery Processing, you can define more customer profiles and therefore adjust the documents to suit your business process. In delivery processing, you can configure the following functions using the customer profiles:
Status management Quantity offsetting Text management Field control Incompleteness check Actions in the Post Processing Framework Partner processing Process codes Reference document types Date types

SAP delivers predefined status profiles for the standard processes in delivery processing. General Settings The general settings for the documents in delivery process are not controlled by the service profiles. You can define the following general settings in Customizing for Delivery Processing:
Number range intervals Delivery priority

Shipping conditions Incoterms

You can find more information in Customizing for Delivery Processing.

Menu Paths and Customizing Paths for Delivery Processing

The following section describes where you can find delivery processing functions.

Menu Paths
For the inbound delivery, start from the SAP Easy Access screen and choose Extended Warehouse Management p Delivery Processing p Inbound Delivery. For the outbound delivery, start from the SAP Easy Access screen and choose Extended Warehouse Management p Delivery Processing p Outbound Delivery. For the posting change, start from the SAP Easy Access screen and choose Extended Warehouse Management p Delivery Processing p Posting Change. For the internal stock transfer, on the SAP Easy Access screen, choose Extended Warehouse Management p Delivery Processing p Maintain Internal Stock Transfer.

Customizing
Processing document and item types:
For the inbound delivery, in the Implementation Guide (IMG) for Extended Warehouse Management choose Goods Receipt Process p Inbound Delivery. For the outbound delivery, in the IMG for EWM choose Goods Issue Process p Outbound Delivery. For the posting change or internal stock transfer, in the IMG for EWM choose Internal Warehouse Processes p Delivery Processing p Posting Changes or Stock Transfers.

General Settings: To define the cross-process settings, such as services, in the IMG for EWM chooseCross-Process Settings p Delivery Processing. Business Add-Ins (BAdIs):
For the outbound delivery, in the IMG for EWM choose Business Add-Ins (BAdIs) for Extended Warehouse Management p Goods Issue Process p Outbound Delivery. For the cross-process settings, such as services, in the IMG for EWM choose Business AddIns (BAdIs) for Extended Warehouse Management p Cross-Process Settings p Delivery Processing. For the warehouse-internal processes, such as posting changes or stock transfers, in the IMG for EWM choose Business Add-Ins (BAdIs) for Extended Warehouse Management p Internal Warehouse Processes p Posting Change Delivery or Stock Transfer Delivery.

Inbound Delivery Notification

Definition
The inbound delivery notification is a document containing all the relevant logistics data in the inbound delivery process right from the origin of the inbound delivery process (shipping notification, delivery note or purchase order, for example).
The shipping notification from the supplier is saved in the inbound delivery notification.

Use
You use the inbound delivery notification to save the logistics data transferred data from a reference document in order to create an inbound delivery.
Using the inbound delivery notification, you can also process or reject incoming changes to an existing inbound delivery.

Structure
For a description of the structure, see Documents in Delivery Processing.

Integration
The execution of the actions depends on the settings in the Post Processing Framework (PPF).
The following configuration exists in the standard system: The delivery process receives a message from a reference document with all the relevant logistics data. An inbound delivery notification is created automatically as a result of this message. All the information contained in the message is saved in the inbound delivery notification. An inbound delivery is created automatically from the inbound delivery notification. Changing an existing inbound delivery: If a change to an existing inbound delivery is rejected, an inactive inbound delivery notification (inactive version) is created in addition to the existing active inbound delivery notification. You can process the data in the inactive inbound delivery notification and you can create a new inbound delivery by activating the request manually.