Objective
You can create a single outbound delivery manually with or without reference to a sales order. However, you cannot use this approach to deliver purchase orders or other requests.
If you use collective processing, you can create deliveries for both sales orders and purchase orders. This type of processing automatically creates multiple outbound deliveries, and can be executed either online or by a background task (for example, using an overnight run).
The delivery due list is a worklist of all operations requiring deliveries. You use various criteria to select the documents that you need to deliver using collective processing. Then, the system automatically creates the outbound deliveries.
If the shipping criteria (for example, shipping point, route, ship-to party) are the same, the system can combine sales documents to form one outbound delivery, if required (order combination). This option must of course be requested by the customer and recorded using the Order Combination field (as a default in the customer master, or alternatively in the header of a specific order or orders). Alternatively, the system may split an order into several outbound deliveries if the shipping criteria are different in the various order items.
You use delivery scenarios to model the different business processes for deliveries. When you process the delivery due list, you choose the most appropriate scenario.
Note
The following are the important SAP Notes for transaction code VL10:
Collective note VL10 (for errors)
Collective note VL10 consulting
These are collective notes; they constitute a list of other SAP Notes about the topic (delivery due list).
A delivery scenario models a business process for delivering goods for orders that are due to be shipped. For example, one delivery scenario might support the creation of deliveries for sales orders on an item-by-item basis, whereas another might enable you to deliver stock transport orders on an order-by-order basis. A range of delivery scenarios is delivered as standard in SAP S/4HANA.
Using user roles (also known as list profiles), you can model your requirements for the delivery process. User roles enable you to fine-tune your processing of the delivery due list, allowing you to control the scope of selection, the display of the delivery due list, and the delivery type.
In the standard system, a user role is assigned to each delivery scenario. You can maintain the user roles in Customizing. If users always or frequently work with the same scenario, they can configure it to meet their personal requirements and use it as their default scenario (user specific delivery scenario).
The following parameters and values have to be defined for creating a user-specific delivery scenario:
| Parameter ID | Parameter Value |
|---|---|
| LE_VL10_SZENARIO | VL10 |
| LE_VL10_PROFIL | Key for list profile |
| LE_VL10_USER_VARIANT | Variant name |
Delivery lists can be complicated, because you can maintain several settings, and each on of these settings has several dependencies.
Depending on which documents you want to deliver using the delivery due list, you can choose one of the delivery scenarios that are available. A delivery scenario models a business process for delivery. The system stores delivery scenarios permanently.
For example: to create outbound deliveries for a particular material, a clerk of a shipping point might select the sales order items scenario (VL10C). Each delivery scenario is assigned a user role (technically referred to as a list profile). This consists of fine tuning for the processing of the list of selected deliveries.
A user role contains the following settings:
The list profile or user role is found automatically through the selected delivery scenario, and can be changed or overridden manually in the selection screen (User role tab page), if you allow this in the delivery scenario. You can also maintain your own user roles in Customizing, and assign them to the various delivery scenarios. These settings are then valid for the whole company.
If required, you can specify a default delivery scenario for each user, and a default list profile for each default delivery scenario. This can than be accessed via transaction code VL10 (or through the "User-Specific Delivery Scenario" menu). To do this, you must set the user parameters LE_VL10_SZENARIO and LE_VL10_PROFIL. If you have to store a particular selection variant for a user, you use user parameter LE_VL10_USER_VARIANT to do this.
The different criteria for selecting documents due for delivery are displayed on tabs. The number of tabs and the selection criteria differ according to the delivery scenario and user role.
Users can define variants in their user-specific scenarios and, thus, create user-specific selection criteria. When you have made your selection, the system displays a list of all documents due for delivery that correspond to your selection criteria. The settings in the user role also affect how the list is displayed. There are many SAP List Viewer functions available within the list, such as sort, sum, and filter.
From the list, you can create deliveries online or in the background, and branch to the relevant documents. You can also change the display of the list while you are using it by accessing display variants.
Note
The system does not process the delivery due list in order of priority. Orders which meet the required selection criteria all have the same status. See also SAP Note 13441. (Keep in mind that this note refers to transaction code VL04.)
In order to create deliveries combining multiple orders, you must allow this in the system for the order items concerned. This is controlled via the field Order combination which, if set in the customer master, defaults into all order headers and items for this customer. The field may also be manually set and unset in the order at both header and item level. In addition, a number of other criteria must be fulfilled for a combined delivery, some of the which are optional. For example: the incoterms can be selected or deselected as a split criterion in the copying control settings.
Keep in mind that SAP Note 22609 is obsolete. The following are relevant SAP Notes:
Why was there a delivery split during creation?
Split analysis activation during delivery creation
Delivery split when creating deliveries
If you use the field ZUKRL in a copying control routine for "Data transfer VBAK", fields that normally do not cause splits can be turned into split criteria (combination criteria). For example: the item number can be used as a split criterion if you require that each delivery should contain only one item. Furthermore, in Customizing, you can also activate a delivery split according to warehouse numbers.
Note
See the following video to learn more about the determination of the picking location:Note
When, in a document, you have a combination of fields with the field for the storage conditions empty, the effect of this on the determination of the picking location is that only table entries with really no value in the storage conditions field are found as a search result. This means that an empty field entry cannot be used to mean "generic" or "for all other values".
You can change or add to delivery documents after you have saved them. For example, you could add items to the outbound delivery. These items may refer to other orders (deliver order function). The same split criteria apply to the additional orders as to the combination of orders during collective processing.
You can also add items to the outbound delivery without referring to an order. For these items, the system determines the item category using the usual rules. However, when you have created an outbound delivery, you can no longer change critical information, such as the ship-to party and shipping point.
Output is a communication tool that supports the exchange of information between you and your partners. Output can be sent from different objects such as an outbound delivery, a group of outbound deliveries, or a handling unit. For example, the delivery note and the packing list are created on the basis of the outbound delivery, and the freight list is created on the basis of a group of outbound deliveries.
You can make output determination dependent on different criteria. The condition technique provides you with flexible control options.
Using condition technique, you can manage the following features of output:
In the outbound delivery, there is a distinction between header and item output. Header output refers to the entire document (for example, a delivery note). You can also create item output for each document item (for example, a quality inspection certificate).
For handling units, you typically print labels. The standard system provides sample forms for output types. You can adapt these to suit your own company-specific requirements.
Log in to track your progress & complete quizzes