VL10B — Delivery Due List by Purchase Order

VL10B runs the same delivery due list logic as VL10 and VL10A but opens on a selection screen built around the purchase order number, purchasing document type, and supplying plant instead of sales order fields. It exists because stock transport orders (STOs) and cross-company stock transfers are procurement documents from the receiving plant's point of view, but the actual outbound delivery is still created against a sales-and-distribution document at the supplying plant. The structural fact that explains most confusion: for cross-company STOs, SAP generates a sales order automatically in the background when the PO is saved, and VL10B is really selecting deliveries against that generated sales order, filtered by the PO number as a search key. If that background sales order was never created, or was created with an item category that is not delivery-relevant, VL10B has nothing to find, regardless of how correct the PO looks.

VL10B sits in the plant-to-plant and cross-company replenishment flow, between purchase order creation at the receiving plant and goods issue at the supplying plant. A consultant reaches for it when the logistics team at the supplying plant has been handed a PO number and needs to create the outbound delivery, but has no visibility into (or interest in) the sales order number that SAP generated behind it. It is chosen over VL10A when the business process is procurement-led (STO, subcontracting-related transfer, intercompany stock transfer) rather than sales-order-led. On S/4HANA it is increasingly replaced in day-to-day use by the corresponding Fiori delivery creation app, but VL10B remains the fallback when the Fiori variant configuration does not cover the scenario or when working in a system without the app activated.

In SE16 on VBFA, filter on the purchase order number in the preceding document field with document category matching a purchase order and check whether a subsequent sales order (VBTYP_N for order) exists at all. If no row appears, the background sales order was never generated and VL10B will never show the PO. If it exists, pull that sales order number into VBAP and check the schedule line category and delivery block fields on the item; a non-delivery-relevant schedule line category or an active delivery block explains an empty VL10B result even though the PO and sales order both look complete.

The selection logic and underlying tables are unchanged on S/4HANA; VL10B still filters the same delivery due list by PO number. The practical difference is that S/4HANA offers a Fiori app for creating outbound deliveries that many sites use for the sales-order-driven case, while STO and cross-company scenarios often continue to rely on VL10B because the app's variant configuration does not always cover purchasing-document-based selection cleanly. No structural change to the background sales order generation mechanism for cross-company STOs.

Functional SD, usually the consultant covering shipping and cross-company stock transfer configuration, owns VL10B behavior and the item category determination behind it. A clean handover names the PO number, the generated sales order number from VBFA, the plant pair, and whether the failure is 'nothing found' versus 'found but blocked', so the receiving consultant does not have to re-derive the document chain from scratch.

VL10A is the direct counterpart for sales-order-driven delivery due lists and is worth comparing side by side to see how little of the underlying logic actually differs. VOV8 explains the sales document type configuration behind the automatically generated cross-company sales order, which is where the schedule line category and delivery relevance trace back to. VL03N is the fastest way to inspect a delivery once VL10B has created one, and VL09 is the tool for reversing a goods issue or delivery created in error during testing of this flow.