SAP Delivery Block Reasons Template: Request, Justify and Release a Block
A delivery block stops an order, a schedule line or a customer from being delivered until someone releases it. Because a block can hold up revenue, most companies want a short written record of why each reason code exists and who owns it.
Fill in
SAP Delivery Block Reasons Template
Delivery Block Reason Request
Company: Acme Components Ltd Request number: DBR-2026-014 Date: 2026-10-20 Requested by: Order management lead
Block definition
| Item | Value |
|---|---|
| Block reason code | Z1 |
| Description | Hold for export license |
| Block level | Sales document header |
| Document types affected | OR, RO, ZOR |
| Block owner | Trade compliance manager |
Business reason
Orders for controlled destinations must not be delivered until the export license number is recorded and approved by trade compliance.
Release conditions
Trade compliance enters the license reference in the order text and removes the block. Release is logged in the change documents.
Configuration checklist
| Step | Where | Done |
|---|---|---|
| Define block reason (table TVLS) | SPRO, Sales and Distribution, Shipping, Deliveries, Define Reasons for Blocking | |
| Assign block to sales document types if default | VOV8, delivery block field | |
| Assign block to delivery types as needed | Shipping delivery type settings | |
| Authorization for release | Authorization object for delivery block | |
| Test with VA01 and VL10 lists | Test client |
Approvals
Header block is held in VBAK-LIFSK, schedule line block in VBEP-LIFSP, and the customer block in KNA1-LIFSD or KNVV-LIFSD. Verify field names and the SPRO path in your release. This is a starting template for your own change process.
Blocked order report
Optional: we can build a read-only report of blocked sales documents with age, reason and owner so none sit unnoticed.
Optional. The tool and every export work without this. No spam.
How to use the template
Fill in the reason code, the description users will see, the level at which the block applies and the document types it affects. Then describe the business reason in a few lines and the exact conditions for release. Download the document as PDF or Word and attach it to the change request. For an existing block on a single order, you can use the same sheet as an exception record.
- Keep the description under 20 characters in SAP
- Name an owner who can release, not a team alias
- State the evidence needed to release
- Record every document type that sets the block automatically
Where blocks are applied
SAP supports delivery blocks at several levels. A customer master block applies to all orders for the customer, centrally or by sales area. A sales document header block holds every line of one order. A schedule line block holds individual lines. Credit management can set a block automatically, and so can the sales document type through a default block. Knowing the level matters, because a header block and a schedule line block are released in different ways.
- Customer level for compliance or dispute holds
- Header level for order approvals
- Schedule line level for partial release
- Default from the sales document type for approval flows
Releasing blocks and reporting
Blocked orders are listed by VA14L, which shows sales documents blocked for delivery. Mass release is possible through the same list when the user has the right authorization. After release, the schedule line must be confirmed again if the availability check was bypassed, so test release on both stocked and non-stocked materials. Review old blocks monthly; unreleased blocks are a common reason for late deliveries.
Common mistakes
Do not create a new block reason for every special case, since users cannot remember dozens of codes. Avoid using the delivery block as a substitute for credit management or for planning. Also make sure the block reason is assigned in the right customizing node; defining the code in TVLS alone does not make it usable on the order screen until the relevant document type and delivery type settings are in place.
Frequently Asked Questions
What is the difference between a delivery block and a billing block?
A delivery block stops goods issue and the creation of the delivery. A billing block stops invoicing. They are separate fields and reason tables. An order can be blocked for one and not the other, which is common in free of charge and pro forma processes.
Where do I define delivery block reasons?
In SPRO under Sales and Distribution, Shipping, Deliveries, Define Reasons for Blocking in Shipping. The reasons are stored in table TVLS. After defining one, assign it to document types or customers where it should apply.
How do I see all orders with a delivery block?
Use transaction VA14L, the list of sales documents due for delivery, with the blocked option, or report V_V2 style lists. You can filter by reason, sales organization and customer, then release or review the blocked documents.
Does credit management use delivery blocks?
Credit management usually sets a credit status on the document, and blocks delivery through that status, not through the delivery block field. Customer and manual delivery blocks run in parallel, so an order can be blocked for both reasons at once.
If blocked orders keep getting lost between order management, credit and logistics, we can build a read-only agent that lists every blocked line with age and owner from live SAP data.
Related Tools
SAP Credit Management Checklist
A checklist for setting up and reviewing SAP credit management in SD, from credit control area to blocked-order release.
SAPSAP Sales Document Types Reference
A searchable list of the standard SAP SD sales document types, with the SD document category and the way each one is normally used in a design.
SAPSAP Incompletion Log Checklist
A checklist to design and test SAP incompletion control so orders cannot move on with missing required data.
SAPSAP Output Determination Checklist
A checklist to design, configure and troubleshoot SAP output determination for order confirmations, delivery notes and invoices.
More SAP tools
See all- SAP Pricing Procedure Design Worksheet
- SAP Item Category Determination Reference
- SAP Billing Types Reference
- SAP SD Tables Reference (VBAK, VBAP, LIKP, VBRK and More)
- SAP SD Pricing Condition Types Reference (PR00, K004, MWST)
- SAP SD Configuration Transactions and IMG Reference
- SAP SD Go-Live and Cutover Readiness Checklist
- SAP Order-to-Cash (SD) Health Assessment
- SAP GL Account Master Data Request Template
Keep exploring
Free tools
- SAP SD Delivery Scheduling Date CalculatorWork backward from the requested delivery date through transit, loading and pick/pack times, and see if material can be ready in time.
- SAP Global Template Rollout Plan TemplateFill-in rollout plan for an SAP global template: scope, local deviation rules, wave plan and governance, laid out so each block becomes one slide.
- SAP Scheduling Agreement Delivery Schedule WorksheetLay out schedule lines for a scheduling agreement, track cumulative quantity against the target and see open balance.
ERP fixes and how-tos
- SAP VL150: Collective Processing of Documents Due for DeliverySAP VL150 mass-creates outbound deliveries for due sales orders. Learn the selection logic, why orders drop out (blocks, dates, availability), and how to fix them.
- SAP MIRO: invoice blocked for price variance, and how to release it in MRBRWhy SAP MIRO blocks an invoice for price or quantity variance, how tolerance keys in OMR6 decide it, and how to release or reject it in MRBR safely.
- Landed cost in SAP MM: planned and unplanned delivery costsHandle freight, duty and delivery costs in SAP MM: planned vs unplanned delivery costs, condition types, GR/IR posting and the effect on material valuation.
Runs with your ERP
- nShift Multi-Carrier Shipping and SAP ECCHow nShift connects SAP ECC and Business One to European carriers: booking, labels, documents and shipment data written back to SAP. Setup and pitfalls.
- Tacton CPQ with SAP S/4HANA: how the integration worksHow Tacton CPQ connects to SAP S/4HANA and ECC: reusing variant configuration rules, validated BOMs, order creation, setup steps, pitfalls and AI on top.
- SAP Ariba Invoicing with SAP S/4HANA and ECCHow SAP Ariba Invoicing captures invoices from email, PDF and images with AI OCR and routes them for matching and approval against SAP purchasing data.
AI on your ERP
- AI for SAP S/4HANA Sales and Distribution (SD) That Explains Orders, Pricing and BlocksAI for SAP S/4HANA SD: order status, delivery and billing blocks, pricing explanations and credit holds in plain English. Read-only, on-prem option.
- Get AI Value From SAP ECC Now, and Use It to De-Risk the Move to S/4HANASAP ECC 6.0 mainstream maintenance ends in 2027. Add AI value on ECC now, using its existing BAPIs and IDocs, and use it to de-risk the S/4HANA migration.
Integrations
- How to add WhatsApp to SAP ECC 6.0How to connect WhatsApp Business to SAP ECC 6.0 using BAPIs, IDocs and output determination: order status, shipment alerts, approvals and supplier replies.
- How to add WhatsApp to SAP S/4HANAHow to connect WhatsApp Business to SAP S/4HANA: OData APIs, business events, template messages, opt-in rules and two-way replies that post back to SAP.