VL09 — Cancel Goods Issue for Outbound Delivery

VL09 reverses the material document that PGI created against an outbound delivery. It is a selection and mass-cancellation tool: enter shipping point, plant, delivery number range or goods movement date, execute, and the system lists every delivery matching the goods movement status filter. Selecting a line and triggering the cancellation posts a reversing movement type against the original material document, which puts the delivery's goods movement status back to not-yet-posted so it can be corrected and re-processed. The structural fact that causes most confusion: VL09 cancels the goods movement, not the delivery document and not the invoice. The delivery itself is untouched except for its status field, and if a billing document already references that delivery, the cancellation either fails outright or leaves the invoice pointing at a reversed movement.

VL09 is reached for whenever a PGI has already posted but something about it was wrong - wrong quantity, wrong batch, wrong storage location, wrong plant, or the delivery needs to be pulled back into picking for correction. It sits between goods issue and billing in the outbound flow: used after VL02N confirmed PGI, before VF01 or VF04 creates the invoice. For a single delivery, the same cancel-goods-movement function is available directly inside VL02N, so consultants use that when they are already on the delivery screen. VL09 is preferred when the reversal has to cover many deliveries at once, selected by shipping point or a date range, typically during a warehouse correction run or an end-of-day cleanup after a batch job posted PGI incorrectly.

Start with VBUK filtered on the delivery number to read the goods movement status field; a reversed movement shows a different status value than a normal completed PGI. Cross-check VBFA for that delivery number, filtering on the subsequent document category for material documents - there should be two entries, the original movement and its reversal, tied together by matching reference numbers. Pull MSEG for those material document numbers and compare movement type against its paired reversal movement type to confirm the posting actually cancelled rather than merely being requested and rejected.

VL09 behaves the same on S/4HANA as on ECC; there has been no functional redesign of the cancellation logic. There is no dedicated Fiori app that replaces the mass-selection reversal capability of VL09 - delivery monitoring apps in Fiori surface status and allow navigation to the delivery, but the actual cancel-goods-movement action is still performed through this classic transaction or the equivalent function inside VL02N.

Functional SD or logistics execution territory, worked jointly with the warehouse team that owns the physical stock movement. Escalate to MM only when the block is a closed posting period or valuation configuration. A clean handover includes the delivery number, the material document number and movement type, the goods movement date attempted, and the exact system message returned on cancellation.

Read VL03N first to see the delivery and its current goods movement status before attempting any cancellation. VF11 matters immediately after, since a billing document is the single most common blocker to a successful VL09 reversal and must be cancelled first. VL10A and VL10B are useful background for understanding how the delivery was created in the first place, which helps when deciding whether to reverse and recreate rather than correct in place.