Delivery Types in SAP SD
Delivery Types in SAP SD
Delivery Types in SAP SD
Delivery Type
A classification that distinguishes between different types of delivery.
Use
The delivery type determines how the system processes a delivery. For example, depending on the delivery
type, the system determines which screens to present and which data to request from the user.
SD document category
A classification for the different types of documents that you can process in the sales and distribution
system (for example: quotations, sales orders, deliveries, and invoices).
Use
The document category determines how the system stores and keeps track of document data. It enables the
system to provide you with status information about delivery processing, billing, and documents that are
used for reference (for example, inquiries and quotations).
Use
When creating a document with internal number assignment, the system assigns a number that lies within
the appropriate number range.
Procedure
1. Determine which internal number ranges are provided for the relevant document type. Choose
the function "Maintain number range" of the document type (for example, Purchase order ->
Maintain number range) for this purpose.
2. Choose a number range and note its number.
3. Enter the number of the desired number range.
Use
When creating a document with external number assignment, the user must enter a document number that
lies within the corresponding number range.
Procedure
1. Determine which external number ranges are provided for the relevant document type. Choose
the function "Maintain number range" of the document type (for example: Purchase order ->
Maintain number range) for this purpose.
2. Choose a number range and note its number.
3. Enter the number of the desired number range.
Use
Note that in delivery processing, the area for item numbers above 900000 is reserved for special items
(batch split and packaging material items) and cannot be used for normal delivery items.
Choose the item number increment so that you know that the item number area will not be above 900000 for
processing of your business transactions.
Use
When you create delivery documents that do not refer to existing orders, you must provide some of the
control criteria that are normally copied from a sales document header into the delivery document.
Example
A delivery document, for example, needs information about which item types need to be defined.
Procedure
You can define a pseudo order type in Table TVAK. When you create a delivery that does not refer to an
existing order, the system automatically uses the pseudo order type.
Use
You can create your own routines according to the needs of your organization.
Example
During delivery processing, you may want to create delivery items for returnable packaging. You may also
want the system to process these items and, for example, keep track of stocks of the packaging material.
You can create a routine that identifies such items and processes them accordingly.
Example
The text procedure for a sales document header could include the following text types:
A standard header text that the system automatically includes in the document
Use
You can assign statistics groups to each of the following:
Item category
Customer
Material
When you generate statistics in the logistics information system, the system uses the combination of
specified statistics groups to determine the appropriate update sequence. The update sequence in turn
determines for exactly which fields the statistics are generated.
Use
If you want to manually change the route during delivery processing, you can also specify whether you want
the system to check the validity of the new route. The system checks the route against table TROAL, which
lists the routes that the system permits as actual routes in delivery processing.
Note that, if the system automatically determines a new route, the system does not carry out an additional
check of this new route against table TROAL.
Explanation
During the checks to see whether two preceding document items can be collected in one delivery, the
following criteria are valid with reference to the partner data:
A delivery split always occurs when the preceding items are assigned to the same partner functions
but different partners. The delivery is also split when the partners are the same but have different
addresses.
If one of the two items to be collected as a freight forwarder as an additional partner function, then
a delivery split always takes place and the items cannot be delivered in a joint delivery. This system
behavior also takes into account the prominent role of the freight forwarder in the delivery process.
If the additional partner function in one of the items is not a freight forwarder, then the items can be
collected into one delivery, and the additional function is copied into the header of the joint delivery.
If you do not require this system behavior, you can use the indicator to force a delivery split.
Use
Set this indicator if different partner functions in the preceding items to be delivered should always cause the
system to perform a delivery split.
Output Type
Specifies the kind of output to be produced.
Use
The output type is predefined for your area of the R/3 System. If alternative choices are possible, you can
list them by pressing F4.
Examples
The output type can specify, for example, a printed form that you need for internal use or a form that you
want to send to a customer or vendor (for example, an order confirmation). The output type can also be an
internal electronic mail message that you want to send to staff in another department.
Use
You define partner determination procedures in SD Customizing through Functions -> Partner determinat.
In sales documents, for example, you can specify the partner determination procedure according
to sales document type and item category. During order entry, the system first proposes partners
from the customer master record of the sold-to party. If this information does not exist in the
customer master, the system automatically proposes the mandatory partners from the partner
determination procedure that you specify in the document header.
For billing documents, for example, you can specify a partner determination procedure where the
sold-to party, bill-to party, and payer are mandatory but the ship-to party is not (for billing, you
are more interested in who orders and pays for the goods than in who receives them).
Reschedule deliveries
You can control whether a redetermination of shipping deadlines should be run for backlogged deliveries
using this indicator.
During rescheduling, it is assumed that the activities that are to be carried out for the backlog delivery can
begin on the current day at the earliest. The new shipping deadlines are redetermined from the current date
using forward scheduling.
Procedure
Set the indicator to 'X' if you want to reschedule backlog deliveries.
If the indicator is set to 'Y' deadlines are redetermined even if there is a change in the routes that were
transferred from the order, or if a new route plan is determined.
If the indicator is set to 'A, then the deadlines are also redetermined for the criteria entered under 'Y' even if
a new weighting group is determined when you create or change items.
If this indicator is not set, the deadlines are copied directly from the order with no changes.