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:
The outbound delivery process is represented in the system by the following documents:
The posting change process is represented in the system by the following documents:
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) .
A document comprises a document header and any number of document items. The following figure shows the structure of a delivery document.
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.
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 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:
Partner processing
Process codes
Reference document types
Date types
SAP delivers predefined status profiles for the standard processes in delivery processing.
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