Delivery Types, Item Categories, and Delivery-Relevant Configuration
Learn how delivery document types, delivery item categories, and copy control settings determine what gets delivered, how, and from where, including shipping point and storage location determination.
Explanation
Once a consultant understands why a delivery exists, the next step is understanding the configuration levers that control how deliveries are created and structured. Several interlocking configuration elements govern this behavior. Delivery document type: Similar to sales document types, the delivery document type (commonly the standard outbound delivery type used for most scenarios, with variants for returns deliveries or other special processes) controls default values such as order combination allowed, whether partial delivery is permitted at item level by default, and which output/print determination applies. Different business processes (standard sales, returns, stock transfer, subcontracting) typically use distinct delivery types because their downstream postings and item category behavior differ. Item category in the delivery: Just as the sales order has item categories, the delivery has its own item category (often defaulted from the sales document item category via configuration, but can differ). This delivery item category controls behavior like whether the item is relevant for picking, whether batch determination is triggered, and how quantity and value updates flow into inventory management. Configuration determines the default delivery item category per combination of sales document item category and other criteria, and it can be overridden by the system only within allowed rules, not manually redefined without configuration change. Schedule line category delivery relevance: On the sales order side, the schedule line category has a delivery-relevant indicator. This is the actual switch that determines whether a schedule line ever becomes eligible for delivery creation. If this indicator is off (as with certain third-party or consignment-related scenarios where goods movement is handled differently), no delivery will ever be created for that line no matter what other settings exist. Shipping point determination: The shipping point (the organizational unit responsible for executing shipping activities) is determined using a combination of shipping condition (from the customer master or sales document), loading group (from the material master), and plant. Consultants configure a shipping point determination table that maps these combinations to a default shipping point, with a manual override possible on the order if authorized. Incorrect or incomplete shipping point determination is one of the most common causes of 'delivery cannot be created' errors in new material or new customer setups, because the combination is simply missing from the table. Storage location determination: For the delivery to know where to pick stock from, storage location determination logic considers the shipping point, plant, and storage condition (or similar criteria depending on design) to propose a storage location. Missing or ambiguous storage location determination often surfaces as a delivery being created without a storage location, blocking picking until manually corrected. Copy control (order to delivery): Copy control rules between the sales document type and delivery type govern which data is copied, how quantities are proposed, and whether pricing or other conditions are redetermined at delivery level. Copy control also enforces requirements routines that can block delivery creation entirely if certain business conditions are not met (for example, a credit block or incomplete document). Understanding these layers together lets a consultant diagnose precisely where a delivery-creation problem originates: is it the schedule line category (never eligible), the shipping point/storage location determination (data missing), or copy control (business rule blocking it)? This layered diagnostic approach is essential in production support where tickets simply say 'delivery not created' with no further detail.
Real project scenario
A newly onboarded plant began processing orders for a material that had not previously shipped from that location. Orders saved successfully, but delivery creation failed with a generic error about shipping point. The root cause was that the shipping point determination table had no entry for the new plant and loading group combination introduced for that material. The functional consultant added the missing determination entry after confirming with the logistics team which shipping point should service that plant, resolving the issue without any development effort.
Common mistakes
• Trying to fix delivery creation issues by changing the delivery document type when the real gap is in schedule line category delivery relevance. • Forgetting that shipping point determination depends on shipping condition, loading group, and plant together, not any single field. • Assuming storage location will always default correctly; not validating determination logic for new plants or storage locations during rollout. • Overlooking copy control requirements routines when a delivery silently fails to generate despite seemingly correct master data.
Best practices
• Maintain a documented shipping point and storage location determination matrix as part of configuration documentation, updated whenever new plants or materials are onboarded. • Test delivery creation explicitly for every new plant/material/customer combination during UAT, not just order creation. • Keep delivery item category defaults aligned with sales item category behavior to avoid inconsistent picking or batch determination. • Review copy control requirements routines whenever a new sales document type is introduced to confirm they do not unintentionally block delivery creation.
Interview angle
A frequent scenario question is 'a sales order is complete but no delivery gets created - how do you troubleshoot?' Strong candidates walk through checking schedule line category delivery relevance, shipping point/storage location determination, copy control requirements, and any blocks (credit, billing), rather than guessing at a single cause.