VL01N — Create an outbound delivery
VL01N creates an outbound delivery for a sales document. It is the shipping step of order-to-cash: the delivery collects the items that are due, carries picking and packing quantities, and becomes the document that posts goods issue. Which items can be delivered depends on dates, availability, blocks and delivery-relevant configuration.
Outbound delivery creation: what makes an item due, what the delivery document controls, and why deliveries fail to include lines.
Reviewed by an ERPClimb SAP consultant on 13 Sept 2026· 579 words
What VL01N is for
VL01N creates the outbound delivery that turns a commercial agreement into a physical shipment. The delivery is a separate document with its own type, item categories and organisational assignment, and it carries the quantities that warehouse staff will pick, pack and issue. Creating it also updates the sales order it references, so the order shows what has been delivered and what is still open. Because goods issue is posted from the delivery rather than the order, this is the point where stock and, in most designs, the cost of goods sold begin to move.
When it is used in order-to-cash
The delivery step comes after the sales order is complete and unblocked, and before billing. Individual deliveries are created here when a shipment needs attention: a specific order that must go out today, a partial shipment agreed with the customer, or a test during a project cycle. High-volume operations create most deliveries collectively from a due list and use this transaction for exceptions, which is exactly why consultants need to understand what makes an item due in the first place. Support work often lands here when a user reports that an order cannot be delivered.
How it is used in practice
You enter the shipping point that will process the shipment, a selection date and the sales document to be delivered. The system proposes the items that are due for that shipping point and date, and you adjust delivery quantities where a partial shipment is intended. Picking quantities are then confirmed, packing is recorded if the process requires it, and goods issue is posted either from the delivery or from the warehouse process, depending on the design. Save creates the delivery document and updates the order status. A warehouse-managed or EWM-managed process replaces manual picking with warehouse tasks, so confirm which design is live before troubleshooting quantities.
Fields and objects that matter
- Shipping point, which decides who ships and therefore which items are proposed
- Selection date, which controls the horizon of items treated as due
- Delivery quantity per item, where a partial delivery is agreed and recorded
- Delivery type and item category, which control picking, packing and goods-issue behaviour
- Batch, storage location and stock information where the material requires them
- Delivery header LIKP and delivery items LIPS, the persisted delivery data
Common pitfalls and how they show up
- No items proposed because the selection date is earlier than the confirmed schedule line date
- A delivery block on the order or the customer that quietly excludes the order from selection
- Unconfirmed availability, so the line exists on the order but has no quantity to ship
- A shipping point mismatch between the order line and the shipping point being used
- An incomplete order or missing shipping-relevant master data stopping the delivery before it starts
- Partial delivery expectations that contradict the customer or item settings, producing a quantity nobody agreed
- Treating a picking or warehouse-task problem as a delivery-creation problem and looking in the wrong document
Related SAP objects
Reviewed pages this object connects to in the ERPClimb knowledge graph.
Learn this properly
Lessons and topics
ERPClimb is an independent platform and is not affiliated with SAP SE. Reference pages are written and reviewed by SAP consultants for learning and troubleshooting.