SAP VL150: Collective Processing of Documents Due for Delivery

Run and troubleshoot mass delivery creation

1. 1Open VL10 (the standard collective processing transaction; VL150 is an older equivalent still present in some systems) and select the appropriate variant - VL10A for sales orders, VL10B for purchase orders (stock transfers), VL10C for both.
2. 2Enter your selection criteria: shipping point, delivery creation date range, and optionally sold-to party, route or order number to narrow the run.
3. 3Execute and review the result list, which splits into documents that will be delivered versus documents that dropped out with a reason.
4. 4For orders missing from the deliverable list, use the log/error tab in the same screen to see why - common reasons are delivery block, incomplete order, credit hold, or availability check failure.
5. 5Clear a delivery block by removing it on the order header (VA02, Shipping tab) if authorized, or route it to the person who set the block (commonly credit management or a manual shipping hold).
6. 6For incomplete orders, use VA02 to find and fill the missing field the incompletion log flags (often a required shipping or billing field).
7. 7For availability failures, check ATP via CO09 for the material and plant, and either confirm a later delivery date, expedite stock, or authorize a partial delivery per the item category's settings.
8. 8Rerun VL10 for the corrected documents, or process them individually via VL01N once each blocking issue is resolved.

Why orders drop out of the selection

Partial deliveries and item category control

Common pitfalls

• !Releasing a delivery block without knowing why it was set can ship an order that credit management or export compliance deliberately held - confirm with the department that owns the block type before clearing it.
• !Widening the VL10 date range to catch more orders can also pull in documents that are due but not yet meant to ship (e.g. future-dated for logistics planning reasons) - check the business intent before mass-processing a wider window.
• !An order that looks complete in VA03 can still fail VL10 if the incompletion log flags a shipping-specific field not visible on the standard overview screen - always check the log rather than eyeballing the order.
• !Partial delivery behavior depends on both item category and customer master settings together; changing one without checking the other can produce unexpected full-block or over-split delivery behavior.
• !Running VL10 with too broad a selection on a large dataset can be slow and lock resources during peak order entry - schedule large collective runs as background jobs where possible.