VL 150 — VL 150 — Only Part of the Material Quantity Is Available for Delivery
SAP message VL 150 means delivery creation can confirm only part, or none, of the requested material quantity under the availability-check rules used for the delivery. Physical stock alone is not enough to explain the result; ATP scope, confirmations, batch or plant context, requirements and preceding-document availability must be checked before changing the delivery quantity.
SAP VL 150 troubleshooting for outbound delivery creation, ATP availability, partial confirmation and delivery quantity problems in VL01N/VL10 and S/4HANA.
Published 25 Sept 2026· 750 words
What it means
VL 150 is issued during delivery creation when the system determines that only a smaller quantity than requested is available for delivery. The message commonly appears in VL01N, collective delivery processing and S/4HANA delivery apps. It is an availability-check result, not simply a stock-overview result. A material can show unrestricted stock and still trigger VL 150 because ATP considers requirements, receipts, confirmed quantities, scope-of-check settings, plant/storage context, batches and other availability elements. In S/4HANA with advanced ATP, the relationship between the sales-order confirmation and the delivery availability check is especially important.
Root causes
The most common cause is genuine shortage after considering existing requirements and confirmations. Another is different availability-check scope between the sales order and the delivery, so the order can be confirmed under one rule while the delivery is restricted under another. Batch determination can reduce the eligible quantity when only specific batches satisfy the delivery. Stock may also be in the wrong plant, storage location or stock type, or reserved by other requirements. In aATP scenarios, negative cumulative ATP or product-allocation/backorder decisions can affect confirmation. Timing matters too: a receipt expected for the order date may not yet be available for the delivery date.
What to inspect
Start from the sales order and delivery-relevant schedule line. Compare ordered quantity, confirmed quantity and requested delivery date. Check the plant and availability-check group/rule used by the sales order and delivery. Review ATP details rather than relying only on stock overview. In S/4HANA, inspect product availability and any aATP controls such as backorder processing, product allocation or alternative-based confirmation if they are active. If batch determination is used, verify the batches considered and their available quantities. Also check whether open deliveries or reservations already consume the same stock. For collective processing, inspect the log because the message can be one result among several delivery creation checks.
Resolution path
If the shortage is real, adjust the delivery quantity or wait for/expedite a valid receipt according to the business process. If the order and delivery use inconsistent availability-check settings, align the configuration only after confirming the intended business rule. For batch-related shortages, correct batch stock, selection criteria or determination where appropriate; do not simply remove batch controls. In aATP, review the confirmation strategy rather than changing stock quantities manually. If a preceding document has an outdated confirmation, rerun the appropriate availability or backorder process. Retest delivery creation with the same plant, date, batch and quantity to ensure the fix addresses the real ATP condition.
The fix people try first (and why it fails)
Users often override the delivery quantity, change dates or move stock merely to bypass VL 150. These actions can create downstream warehouse or customer-service issues if the ATP logic still says the quantity is unavailable. Another weak fix is to loosen the availability-check scope without assessing order confirmation and delivery behavior across the sales process. That can overconfirm material and shift the shortage to picking or goods issue. The correct approach is to understand why the delivery ATP result differs from expectations and change stock, confirmation or configuration only in line with the intended fulfillment policy.
Whose problem this is
SD owns the delivery process and availability-check configuration. Supply planning or ATP teams own confirmation strategy, especially in aATP environments. Warehouse/EWM teams may need to validate stock type, batch and physical availability when ERP stock appears inconsistent with execution. MM or production planning may own expected receipts. Integration teams are relevant when external ATP or stock feeds are involved. ABAP should not be used to suppress VL 150; the message is the result of standard availability logic and should be resolved through supply, confirmation or configuration.
Common pitfalls
Do not equate unrestricted stock with ATP quantity. Do not compare only the sales-order confirmation; the delivery can use a different check. Check date and plant carefully. Batch-managed materials can have enough total stock but insufficient eligible batch stock. In collective delivery processing, read the complete log rather than the headline message. For S/4HANA aATP, remember that backorder processing or allocation can deliberately redistribute confirmations. Finally, if VL 150 appears only after a configuration change, compare the scope of check and confirmation strategy before looking for data corruption.
Take the next diagnostic step
Use these ERPClimb resources to explore the scenario. Verify all actions in your SAP system before making production changes.
- SAP Error Message Decoder →
Decode any message class and number into its area, long text and first checks.
- ERPClimb AI Copilot →
Describe the transaction and the message to get ranked causes and checks.
Related SAP objects
Reviewed pages this object connects to in the ERPClimb knowledge graph.
Source: ERPClimb — https://erpclimb.com/sap-messages/vl-150ERPClimb is an independent platform and is not affiliated with SAP SE. Reference pages are written and reviewed by SAP consultants for learning and troubleshooting.