5122123, 103 AM 1519607 -Eror message VL150 raised at delivery creation [ZD” SAP Knowledge Base Article 1513607 - Error message VL150 raised at delivery creation Component: LE-SHP-GF-AC (Availability control Delivery), Version: 12, Released On: 03.09.2020 | Symptom You are notable to creale a delivery because of = Error message VL150 - 'Only & & of material & & available’ = Error message VL367 - ‘An item with no delivery quantity is not permitted. Item will be deleted.’ | Environment + Logistics Execution (LE) + SAP ERP Central Component + SAP ERP + SAP Enhancement Package for SAP ERP + SAP Enhancement Package for SAP ERP, version for SAP HANA + SAP S/4HANA + SAP S/4HANA Cloud | Cause 1. There is not enough quantity available for the confirmation of the delivery although you can see enough available quantity in transaction MMBE or MD04. 2. Different scope of checks (transaction OVZ9) for the preceding document (e.g, sales order) and follow-up document (delivery) Negative cumulated ATP quantity in transaction C009 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. ae | Resolution For cause 1 You have to use transaction C009 to check the availability situation for a material. Transaction MDO4 or MMBE are ot suitable to check the availabilty situation for a material. Please consider SAP Note 547118 (/sap/supportInotes/547118) question 1. itpsuserapps support sap com/saplsupport/stminetasiprin/0001513607Mlanguage=£&token=FO12008£92 128097 9B00BF4EFT41486E 165122123, 103 AM 1519607 -Eror message VL150 raised at delivery creation 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 fil the special stock element (sales order, WBS element, sold-to-party) on the initial screen of transaction C009 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, 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 transaction OVZ9. Please also consider SAP Note 547512 (/sap/supportinotes/547512) question 6 and SAP Note 36520 (/sap/supportinotes/36520). For cause 3: Ifyou 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 pes and you have a negative cumulated ATP quantity of 10 cs. When you now create the delivery for the sales order then the confirmed quantity of the sales order (10 pes ) 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, itis not possible to confirm the delivery. Please also consider SAP Note 547118 (/sap/supportinotes/547118) question 4 and SAP Note 153355, (sap/supportinotes/153355). For cause 4: The ATP checks in all specified segments: In each case in ‘plant’ and, if specified, also in ‘storage location’ and ‘patch’. 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 pes 100 pes storage location 4 10 pes 10 pes storage location 2 90 pes 90 pes If now a requirement is checked (20 pes) 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: itpsluserapps support sap com/saplsuppot/stminetasiprin/0001513607Mlanguage=£&token=FO12008£92 128097 9B00BFAEF741486E 2185122123, 103 AM 1519607 -Eror message VL150 raised at delivery creation stock requirement confirmed ATP quantity plant 100 pes 20 pes 20 pes 80 pes (100-20) storage location 4 10 pes 10 pes storage location 2 90 pes 90 pes -> confirmation over 20 pes. Now a further requirement is checked also on storage location level (90 pes, storage location 2), so also plant level MUST be checked, otherwise it can result in an overconfirmation situation.(20 pes of 100 pcs are already assigned to a requirement, therefore only 80 pes are available): stock requirement confirmed ATP quantity plant 100 pes 90 pes 80 pos 0 pes (100-20-80) 10 pes 10 pes storage location 2 90 pes 90 pes 80 pes 10 pes (90-80) The whole quantity of 90 pes could be confirmed on storage location level but on plant level only 80 pes are available, so the system can only confirm 80 pes. If batches are involved then both the batch and the batch/storage location levels have to be considered, Please also consider SAP Note 547118 (/sap/supportinotes/547118) question 6. For cause 5: Please check whether storage location determination is active for the concerned delivery item category (transaction OVLP, field BELGO). If this function is active, the system will determine a storage location at delivery creation, based on the customization settings of transaction OVL3. 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. Storage location determination can also be controlled in include MVSOAFZZ, in form USEREXIT_LGORT_DETERMINATION. This user exit provides an alternative to apply a specific logic for storage location determination 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. SAP Knowledge Base Article 1837190 (/sap/support/notes/1837190) deals with the different types of hitps:/userapps support sap com/saplsuppet'stminctes/prit/00016 13607 Mlanguage=&token=F012098597 1BS0979BOOSFAEF741486E ais5122123, 103 AM 1519607 -Eror message VL150 raised at delivery creation inconsistencies and how they can be resolved. | Keywords VL367, VL 367, VL150, Es sind nur & & von Material & & verfiigbar, Position ohne Liefermenge ist nicht zulissig (Position wird geléscht), Lieferung, Verfiigbarkeitspriifung, Priifumfang, Sonderbestand, Wiederbeschaffungszeit, Lagerortfindung, "An item with no delivery quantity is not permitted. Item will be deleted”, "Position ohne Liefermenge ist nicht zulassig (Position wird geléscht)", "Poste sans quantité a livrer non autorisé; Poste va étre supprimé", "Posiz. non ammessa senza qta di consegna (Posiz. cancellata)", "Positie zonder leveringshoevh niet toegestaan (positie wordt verwijderd)*, "Item nao é permitido sem quantidade a forecer (item sera eliminado)", "No se permiten posiciones sin cantidad a entregar (se borra la posicién)", RCC, VL10B. | Attributes key Value other Componens SD-BF-AC (vaiabilly Check) ther Components LE-SHP-DL (Delvery Processing) | Products Products SAP ERP Central Component all versions SAP ERP all versions SAP S/4HANA all versions SAP enhancement package for SAP ERP all versions SAP enhancement package for SAP ERP, version for SAP HANA all versions | This document refers to SAP Note/KBA Title 1837190, No ATP confirmation due to inconsistency (/sap/supportinotes/1837190) 547512 FAQ: Customizing for ATP in R/S (/sap/support/notes/547512) 547118 FAQ: Result of ATP calculation (/sap/supportinotes/547118) itpsluserapps support sap com/saplsuppert/stminetes/prin/0001613607 Mlanguage=€&token=F012908E92 128097 9B008F4EF741486E ais572213, 1.08 AM 1519607 -Error message VL160 raised at dalvery creation 36520 Availabilty check for delivery (/sap/supportinotes/36520) 153355 No availability owing to negative ATP quantity (/sap/supportinotes/153355) | This document is referenced by SAP Title Note/KBA. 2799378 ATP result does not match the quantity available in MMBE / MD04 (/sap/supportnotes/2799378 ) 2196410 Everything about ERP ATP check and SD scheduling (/sap/supportnotes/2196410 ) 2191777 Cause and solution for error/information messages and Dumps that are raised during the atp check or scheduling (/sap/support¢notes/2191777 ) 2150057 Troubleshooting guide for ERP ATP check (/sap/supportinotes/2150057 ) 1893237 Everything about transaction Co09 (/sap/support/notes/1893237 ) 1669121 Redundant entries in ATP screen when you do new ATP check (/sap/supportinotes/1669121 ) itpsluserapps support sap com/saplsuppot/stminetasiprin/0001513607Mlanguage=£&token=FO12008£92 128097 9B00BFAEF741486E 55