Delivery Document creation using buffered data?

robphelan — Sun, 13 Jul 2014 17:50:51 GMT

We're using BAPIs to create an STO with estimated volumes/dates.

But, when the Actual information comes in, we first update the STO with actual volume, then create a delivery document. The problem is that the delivery document is using the estimated volume even though we've committed the volume change and can pull up the STO to see it prior to Delivery create.

For STO, we're using:

BAPI_PO_CREATE1 and

BAPI_PO_CHANGE

For Delivery creation, we're using:

BAPI_OUTB_DELIVERY_CREATE_STO

It seems that the Delivery is reading buffered information rather than what's actually been committed to the DB. Is there a way to bypass the buffer when calling this BAPI?

thanks,

Robert

Re: Delivery Document creation using buffered data?

robphelan — Mon, 14 Jul 2014 17:36:04 GMT

Found a note that has addressed the issue

2008537 - Short dump while changing a replenishment delivery multiple times in one transaction

topic Re: Delivery Document creation using buffered data? in Application Development and Automation Discussions

Delivery Document creation using buffered data?

Re: Delivery Document creation using buffered data?