Using Special Functions in Deliveries

The outbound delivery may contain shipping-related conditions, such as shipping or freight costs. You can enter the condition values manually or determine them using the SD pricing condition technique.

You can print the conditions on the delivery note and transfer them to the billing document, but you cannot transfer them from the preceding documents to the outbound delivery.

To implement the conditions, use the standard Customizing settings for pricing (condition type definition, maintaining the pricing procedure). Assign the pricing procedure to the delivery type.

If business partners are involved in the shipping process, or if some functions are performed by non-SAP systems, you need to exchange information with these other parties or systems. Normally, electronic data interchange (EDI) messages are used for external communication, and Application Link Enabling (ALE) messages are used for internal communication.

The delivery interface groups together all EDI and ALE messages that refer to the delivery. They are all based on IDoc DELVRY07. This is the data structure, consisting of segments, that contains the fields for the delivery and other fields relevant for shipping such as route and batch characteristics.

Output control of the delivery at header level triggers the population of the IDoc fields. The system provides appropriate message types for the communication scenarios represented by the IDoc in the standard SAP S/4HANA system.

When you call up the log of incomplete items, the system checks if the data in the outbound delivery is complete. From the generated list, you can branch directly to the screen for maintaining the incomplete fields.

You can call the log of incomplete items from delivery processing or select incomplete delivery documents using a special report. This creates a worklist of documents that require processing.

In the outbound delivery, the system can check the completeness of a delivery at both header and item level. In Customizing, you can control which fields, if not already specified, cause an outbound delivery to be incomplete, and what effects these incomplete fields have on follow-on activities, such as picking, packing, goods issue, and billing (for example, packing may be not allowed if the item volume is not specified). The selection of the fields that cause a delivery to be incomplete depends on the delivery type and the delivery item category.

In addition, you can set partner functions and texts as "Required" by using the corresponding Customizing functions. If specifications for a required partner function are missing in the document or if a required text does not exist, a note is entered in the log of incomplete items.

When creating and processing deliveries, you can access numerous other functions that the system can perform either automatically or on request.