3422033 - Gaps in delivery item numbering when using Group ATP - SAP S/4HANA Cloud Public Edition

Delivery item numbering deviates between the creation of a delivery document using single record processing (e.g. VL01N) or mass creation process (e.g. VL10*, Batch Jobs). This happens when single delivery items selected for delivery creation cannot be created due to customizing settings. In the mass processing transaction the numbering is not consecutive and may not start with the lowest increment.

SAP S/4HANA Cloud Public Edition

For a sales order A, 5 items have been confirmed by ATP check and have a schedule line record with confirmed quantity. For the relevant delivery item category, items with a zero quantity are not allowed during delivery document creation. Item numbers in the delivery are not transferred from the sales document.

Based on this the delivery document is created. For sales document item 10 & 30 no quantity is available at the time of delivery document creation. The corresponding delivery items cannot be created due to customizing settings above. This will result in the following delivery document items being created:

When a delivery document is created using the Group ATP functionality, the delivery items are created first with the full quantity requested. During this creation phase, delivery item numbers are drawn and assigned to the created delivery items. In a next step the ATP check is executed against all delivery items. This results in delivery items with zero quantity. Afterwards relevant customizing checks are executed and items with zero quantity are removed from the delivery document. 

A re-numbering of the delivery items is not executed. This leads to gaps in the delivery document items.

A sequential gap-less delivery item numbering when creating delivery documents cannot be expected.

This is expected behavior.

Delivery Item Numbering, Group ATP, VL01N, VL10*, Batch Jobs, ATP check, Schedule Line, Confirmed Quantity, Re-numbering , KBA , LE-SHP-DL-2CL , Delivery Processing (Public Cloud) , CA-ATP-2CL , Available to Promise (ATP) (Public Cloud) , Problem