VL10A — Collective Delivery Creation from Sales Orders

VL10A builds a worklist of sales order schedule lines that are due for delivery and lets the user turn a selection of them into one or more outbound deliveries in a single run, either interactively or in the background. The structural fact that explains most confusion is that VL10A is not a distinct program; it is transaction VL10 called with a stored selection variant restricted to sales-order sources. Every quirk of VL10 -- the tabbed worklist, the split between foreground and background processing, the separate log for creation errors -- applies identically here. Nothing is written to the database by running the selection itself; the worklist is a live read against order and schedule line status, and only the explicit create/save step generates delivery documents.

VL10A sits between order entry and goods issue. It is used once a sales order (or a batch of them) has confirmed schedule lines and is ready to ship, typically run per shipping point at the start or throughout the shipping day. It is the tool of choice when deliveries need to be created for many orders at once rather than one order at a time from VA02. VL10B is used instead when the demand source is a purchase order or stock transport order rather than a sales order; VL04 is the older, less commonly used equivalent worklist. In S/4HANA the same job is increasingly done through the Fiori 'Create Deliveries' or 'Manage Deliveries' apps, but VL10A remains available and is still the reflex tool in mixed-mode landscapes.

To reproduce a VL10A symptom outside the transaction, start in SE16 on VBAP for the order item and confirm VSTEL (shipping point) and ROUTE are populated -- a blank shipping point means the item can never appear in the worklist regardless of selection parameters. Then check VBUP for that order/item combination: LFSTA not equal to 'C' means the item is still open for delivery. Cross-check VBUK-LFGSA at header level for a delivery block. Finally look at VBEP for the schedule line delivery date and confirmed quantity, since VL10A's date range filter is applied against this table, not against VBAK.

VL10A is unchanged functionally on S/4HANA; it is still the VL10 variant for sales-order-based delivery creation and the same worklist mechanics apply. The Fiori apps for creating and managing deliveries cover the equivalent business process with a different interface and are the direction of travel for new implementations, but VL10A remains fully supported and is often still the fastest way to process a large shipping-point-level run. Where decentralized EWM is in use, delivery creation logic and blocking behavior can differ, but that is a warehouse integration difference, not a VL10A change.

Functional SD/logistics execution owns this transaction and its configuration (shipping point determination, delivery block reasons, route determination). Basis or ABAP is only pulled in for a custom BAdI interfering with delivery creation or for background job scheduling issues. A good handover includes the sales order and item number, shipping point, the exact error text from the application log, and whether the run was background or foreground.

VL03N is the natural next stop to display whatever delivery VL10A actually created and confirm its status and quantities. VL09 is used when a goods issue posted from that delivery needs to be reversed. VL10B handles the same worklist mechanics for purchase-order and stock-transfer demand rather than sales orders, and is worth knowing as the sibling transaction. VOV8 governs the sales document type settings that decide whether an order type is delivery-relevant at all, which is the configuration layer behind many empty-worklist complaints.