SD / O2Cbeginner

SD Delivery Processing Part 1: What an Outbound Delivery Is and Why It Matters

Key takeaway

The outbound delivery as the shipping document of order-to-cash: when it is created, what it contains (header, items, shipping point, route, dates), the activities it drives (picking, packing, goods issue) and how it connects sales orders to warehouse, inventory and billing.

What this complete series covers

Learn Delivery Processing in a clear, practical sequence — from the basic idea to real project use, troubleshooting, and interview-ready understanding.

Who it is for: Best for SAP consultants, developers, and learners who want a practical understanding of Delivery Processing.
Prerequisites: Basic SAP S/4HANA navigation and an understanding of the business process are helpful. Configuration or transaction steps require suitable access to a practice or project system.
Final outcome: By the end, you should be able to explain Delivery Processing clearly, follow the main end-to-end flow, apply it in a project scenario, and troubleshoot the most common issues.

Part 1: SD Delivery Processing Part 1: What an Outbound Delivery Is and Why It Matters
Understand the business purpose of the delivery document, its position in the O2C cycle, and why it exists as a separate object from the sales order and billing document.
Part 2: SD Delivery Processing Part 2: Delivery Types and Delivery Item Categories
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.
Part 3: SD Delivery Processing Part 3: Collective Delivery Creation, Scheduling and Route Determination
How due sales orders are grouped into deliveries using the VL10 transaction family, how scheduling dates are calculated, and how route determination assigns a shipping route to each delivery.
Part 4: SD Delivery Processing Part 5: Architecting Delivery Processing at Scale
An architect-level view of designing delivery processing for high-volume, multi-warehouse enterprises, covering EWM integration models, mass processing/background job design, outpu
Part 5: SD Delivery Processing Part 4: Packing and Handling Units in Outbound Deliveries
Advanced handling of warehouse picking confirmation, batch determination, and handling unit (HU) packing for outbound deliveries, including integration points with WM/EWM and commo

System and release assumptions: Examples focus on SAP S/4HANA. Exact apps, transaction codes, configuration paths, and field names can vary by release and deployment model.

Explanation

📌 KEY POINTS
✅ The outbound delivery (LIKP/LIPS) starts the shipping process: it is created from confirmed, due sales order schedule lines.
✅ One delivery = one shipping point, one ship-to, one route, one delivery date — orders are split or combined accordingly.
✅ Deliveries drive picking, packing, loading and post goods issue (PGI), which reduces stock and posts cost of goods sold.
✅ Delivery-related billing is created from the delivery after PGI.
⚠️ A delivery cannot be created for items that are not confirmed, not due, blocked or incomplete.

━━━━━━━━━━━━━━━━━━━━
▶ WHAT THIS SERIES COVERS
Part 1: What an outbound delivery is
Part 2: Delivery types and delivery item categories
Part 3: Collective delivery creation, scheduling and route determination
Part 4: Packing and handling units in outbound deliveries
Part 5: Architecting delivery processing at scale

━━━━━━━━━━━━━━━━━━━━
▶ 1. POSITION IN ORDER-TO-CASH

Order → delivery → picking/packing → PGI → invoice.
The delivery is the logistics document; the order is the commercial one.

━━━━━━━━━━━━━━━━━━━━
▶ 2. WHAT A DELIVERY CONTAINS

Header: shipping point, ship-to, route, dates (picking, loading, goods issue, delivery), weights.
Items: material, quantity, plant, storage location, batch, picking status.
Partners, texts, output (delivery note).

━━━━━━━━━━━━━━━━━━━━
▶ 3. WHEN IT IS CREATED

Selection date: material availability or loading date reached.
Individually (VL01N) or collectively (VL10 delivery due list).
Order must be confirmed, not blocked, complete for delivery.

━━━━━━━━━━━━━━━━━━━━
▶ 4. WHAT FOLLOWS

Picking (WM/EWM or lean), packing (HUs), loading.
PGI: 601 movement, stock reduction, COGS posting.
Billing due list for delivery-related billing.

━━━━━━━━━━━━━━━━━━━━
▶ 5. STATUS AND FLOW

Picking, packing, goods movement, billing status on the delivery.
Document flow shows order → delivery → goods issue → invoice.

━━━━━━━━━━━━━━━━━━━━
▶ STEP BY STEP

Create an order that is confirmed for today.
Create a delivery with VL01N.
Check header dates, shipping point and route.
Pick and post goods issue; check document flow.

✅ CHECKPOINT: you can explain why one order created two deliveries.

Code example

ABAP Code

===== STEP 1: tables =====LIKP delivery header   LIPS delivery items   VBFA document flow   VEKP/VEPO handling units ===== STEP 2: key transactions =====VL01N create delivery (single)     VL10A/VL10C/VL10G delivery due list (collective)VL02N change (pick, pack, PGI)     VL03N display     VL06O outbound delivery monitor ===== STEP 3: delivery header dates =====Picking date → loading date → goods issue date → delivery date (from delivery scheduling) ===== STEP 4: split criteria (examples) =====Different shipping point, ship-to, route, incoterms or delivery date → separate deliveries

Real project scenario

A distributor's customers complained about receiving three trucks for one order. The order had items from two plants and two storage conditions; each item got a different shipping point, so three deliveries were created. The team reviewed shipping point determination (OVL2) and the customer's delivery requirements: ambient and cold items could share a truck with separate compartments, so one shipping point with loading groups for both was defined, reducing split deliveries by 60%.

Common mistakes

Expecting deliveries for unconfirmed or blocked items.
Ignoring split criteria (shipping point, route, ship-to).
Confusing delivery date with goods issue date.
Billing before PGI in delivery-related scenarios.
Not using document flow in investigations.

Best practices

Understand split criteria before designing shipping points.
Monitor the delivery due list daily.
Use the delivery monitor (VL06O) for status.
Keep scheduling master data accurate.
Explain delivery statuses to users.

Interview angle

Questions: "What is an outbound delivery?", "When can a delivery be created?", "Why are deliveries split?"
Strong answer: LIKP/LIPS logistics document created from confirmed due schedule lines; one shipping point, ship-to, route and date per delivery; drives picking, packing, PGI and billing; blocked, unconfirmed or incomplete items cannot be delivered.

Practice this lesson

Quick check

1. What is the primary purpose of running the delivery due list transaction (e.g., VL10 series) in outbound delivery processing?

2. What does Post Goods Issue update?

3. A delivery cannot be created from a sales order. Which should you check first?

Interview questions

1. A distribution company's retail customers receive several partial deliveries for one order. Explain how deliveries are formed and how you would reduce splits.

Answer it in your own words first, then compare.

2. A production issue is reported in Delivery Processing. What would you check first, and how would you troubleshoot it systematically?