ATP over-commit / over-confirm, missing entries in VBBE?

created by Josh Cheron in SAP ERP Sales and Distribution (SAP SD) - View the full discussion

*Apologies if this has been covered somewhere and I've not found it. We've also got SAP itself engaged in this issue but pe
community has seen this before.*

Hi everyone,

We're encountering an issue for the last few months (since February) where fast runners are over-committing within ATP and causing sto
center. The DC can't process deliveries that drop as they confirmed inventory that wasn't actually in stock and when the users try to proc
[obviously.] CO09 shows more commits than stock available.

We've had limited mitigating the issue with SDRQCR21 & RVV05IVB.

One observation we made is that rows don't seem to end up in VBBE when they should, which allows there to appear to be
available to commit than actually exists. This is even though the delivery items are LIPS-SUMBD = 'A'.

It appears that these over-commit scenarios could be tied to batch determination, as this is the only plant where that is a feature, though
group and affected materials aren't assigned to that loading group.

All of the materials in question are availability check 02. We don't think they need to be CH just because we're using batch determination
batches on the orders) but is it a truism we haven't accounted for? Note 201613, which is very old, seems to suggest that you used to ha
batch determination framework only prior to 4.0, but beyond that you could use something else, presumably including 02.

And thoughts or suggestions would be greatly appreciated.

Thanks much,
Josh C.
Sudbury, MA, USA
Reply to this message by going to SCN
Start a new discussion in SAP ERP Sales and Distribution (SAP SD) at SCN

SCN Newsletters

Get the latest news from SAP Community Network on SAP HANA, cloud, mobile, and more by e-mail. Sign up for free today.

Mandatory Disclosure Statements: http://www.sap.com/company/legal/impressum.epx

This e-mail may contain trade secrets or privileged, undisclosed, or otherwise confidential information. If you have received this e-mail in
notified that any review, copying, or distribution of it is strictly prohibited. Please inform us immediately and destroy the original transmitta
cooperation.

Click here to Reply or Forward