cancel
Showing results for 
Search instead for 
Did you mean: 

Incorrect ATP results at delivery creation level

Former Member
0 Kudos

This is regarding SAP Available To Promise (ATP) check (performed at delivery creation level) related concern. As part of design, the client specific delivery workbench uses standard delivery BAPI " BAPI_OUTB_DELIVERY_CREATE_SLS" to create outbound deliveries of sales orders. Per OVZ9, ATP check is active only at delivery creation level and consider only open non-PGI'ed deliveries for net available stock calculation. (Note: orders have no ATP schedule lines and open orders requirements are not considered at delivery creation level per OVZ9).

In production system, during mass delivery creation, we observed an issue where standard BAPI is throwing "0 stock available" (even if stock is available) message and not creating delivery for some line items. However, in the second attempt delivery gets created everytime with no issues for the same line item (note: stock was sufficient and no incoming stock was observed between first and second attempt).

This issue occurs at frequent intervals in production system and is impacting the business as it splits the deliveries for an order, eventually, creating additional shipment cost & deliveries re-consolidation work per DC level.

The issue in not getting reproduced at non-production system.

Can someone please help?

Accepted Solutions (0)

Answers (1)

Answers (1)

Lakshmipathi
Active Contributor
0 Kudos

Did you try creating mass delivery creation via VL06G? If so, what was the outcome ? I strongly feel, this is definitely related to some incorrect code validation set at delivery level.