SAP Knowledge Base Article - Public

2821149 - Error VL150 is issued during delivery creation - SAP S/4 HANA CLOUD

Symptom

During delivery creation, error messages below are issued.

  • Error message VL150 - 'Only & & of material & & available'
  • Error message VL367 - 'An item with no delivery quantity is not permitted. Item will be deleted.'

Environment

  • SAP S/4 HANA Cloud
  • Advanced ATP

Reproducing the Issue

  1. Go to Create Outbound Delivery APP
  2. Enter shipping point, date, sales order number
  3. Press Continue

Cause

  1. There is not enough quantity available for the confirmation of the delivery although the material has enough available quantity in Stock Overview: Basic List APP.
  2. Different scope of checks (Configure Scope of Availability Check (ID 101099)) for the preceding document (e.g. sales order) and follow-up document (delivery).
  3. Negative cumulated ATP quantity in Monitor Product Availability APP.
  4. Sufficient available stock on storage location level but not on plant level.
  5. ATP quantities are checked against a storage location in spite of no storage location has been determined in the predecessor sales document so the system should check available quantities on plant level only.
  6. Inconsistencies.

Resolution

For cause 1:

You have to use Monitor Product Availability APP to check the availability situation for a material. Other APPs, such as Stock Overview: Basic List APP, are not suitable to check the availability situation for a material.

The checking rule for deliveries is 'B'. This is hard coded. If you are working with special stocks then you have to use the checking rule 'B' for the delivery + the special stock indicator e.g. 'E'.  When you are using special stocks then you also have to fill the special stock element (sales order, WBS element, sold-to-party) on the initial screen of Monitor Product Availability APP in order to get meaningful results.

For cause 2:

Sales orders are checked with checking rule A in the SAP standard. This is hard coded. If you check orders with a scope of check that allows more than the scope of check of deliveries (for example, the order can confirm against replenishment lead time (Check Horizon), the delivery cannot) then sales requirements must not taken into account in the scope of check of the deliveries. The same is valid when you include some receipts in the scope of check for the sales orders and those receipts are not included in the scope of check of the deliveries.
You can check the scope of check in Configure Scope of Availability Check (ID 101099). Please consider also in SAP KBA 3295962.

For cause 3:

If you have a negative cumulated ATP quantity then it will also prevent a confirmation of the delivery. The reason for this is that the ATP calculation of stocks and receipts first deducts the negative cumulated ATP quantity regardless when this occured.

For example, you have a sales order confirmed with 10 pcs and you have a negative cumulated ATP quantity of 10 pcs. When you now create the delivery for the sales order then the confirmed quantity of the sales order (10 pcs) will be released so that this quantity can be passed to delivery for confirmation. But as there is a negative cumulated ATP quantity the released confirmed quantity of the sales order will be used to cover the negative cumulated ATP quantity. Therefore, it is not possible to confirm the delivery.

For cause 4:

The ATP checks in all specified segments: In each case in 'plant' and, if specified, also in 'storage location' and 'batch'. The ATP result is the minimum of all checks that were carried out.

Please consider the following example:

Starting situation:

  stock requirement confirmed ATP quantity
plant 100 pcs     100 pcs
storage location 1 10 pcs     10 pcs
storage location 2 90 pcs     90 pcs

If now a requirement is checked (20 pcs) only on plant level, the ATP quantity on plant level will be reduced, but the atp quantity on storage location level will not be reduced because it is not known which storage location the requirement should be assigned  to:

  stock requirement confirmed ATP quantity
plant 100 pcs  20 pcs  20 pcs 80 pcs (100-20)
storage location 1 10 pcs     10 pcs
storage location 2 90 pcs    

90 pcs

--> confirmation over 20 pcs.

Now a further requirement is checked also on storage location level (90 pcs, storage location 2), so also plant level MUST be checked, otherwise it can result in an overconfirmation situation.(20 pcs of 100 pcs are  already assigned to a requirement, therefore only 80 pcs are available):

  stock requirement confirmed ATP quantity
plant 100 pcs  90 pcs  80 pcs 0 pcs (100-20-80)
storage location 1 10 pcs     10 pcs
storage location 2 90 pcs  90 pcs  80 pcs

10 pcs (90-80)

The whole quantity of 90 pcs could be confirmed on storage location level but on plant level only 80 pcs are available, so the system can only confirm 80 pcs.
If batches are involved then both the batch and the batch/storage location levels have to be considered.

For cause 5:

Please check whether storage location determination is active for the concerned delivery item category. If this function is active, the system will determine a storage location at delivery creation, based on the customization settings. ATP check is performed for all the relevant storage levels. If there is a storage location determination, the system will check ATP quantities on the selected storage location as well. If there is no available quantity on the selected storage location, error message VL150 (and VL367) will be raised.

Please note that storage location determination in delivery documents works only if there is no storage location determined in the predecessor sales document. If there is a storage location given in the predecessor sales document, this storage location will be simply copied into the delivery document.

 

For cause 6:

Inconsistencies can prevent the confirmation of a delivery, too. This could be for example the case if an already completed sales order is still blocking the available quantity.

The system is scheduled to clear up the inconsistencies once week automatically (it is scheduled for Sundays night usually). In case you cannot wait or the inconsistencies are frequently created, please create a case for CA-ATP-PAC-2CL component.

See Also

3193069 - All knowledge resources for aATP on SAP S/4HANA Cloud

3341145 - ATP result doesn't match the qty available in Monitor Stock / Requirements List APP - SAP S/4 HANA CLOUD

3295962 - Calculation of the Replenishment Lead Time - SAP S/4 HANA CLOUD

SAP Help - Monitor Product Availability

SAP Help - Manage Your Solution

Keywords

VL367, VL 367, VL150, Es sind nur & & von Material & & verfügbar, Position ohne Liefermenge ist nicht zulässig (Position wird gelöscht), Lieferung, Verfügbarkeitsprüfung, Prüfumfang, Sonderbestand, Wiederbeschaffungszeit, Lagerortfindung, "An item with no delivery quantity is not permitted. Item will be deleted",  "Position ohne Liefermenge ist nicht zulässig (Position wird gelöscht)", "Poste sans quantité à livrer non autorisé; Poste va être supprimé", "Posiz. non ammessa senza qtà di consegna (Posiz. cancellata)", "Positie zonder leveringshoevh niet toegestaan (positie wordt verwijderd)", "Item não é permitido sem quantidade a fornecer (item será eliminado)", "No se permiten posiciones sin cantidad a entregar (se borra la posición)", RCC, VL10B. , KBA , CA-ATP-PAC-2CL , ATP: Product Availability Check (Public Cloud) , CA-ATP-2CL , Available to Promise (ATP) (Public Cloud) , Problem

Product

SAP S/4HANA Cloud all versions