topic Re: Synchronized BAPI posting in Application Development and Automation Discussions

Synchronized BAPI posting

Former Member — Sun, 18 Sep 2011 06:41:11 GMT

Hi,

We have developed a Z transaction to post goods issue, goods reciept and confirmation of production order.We are using three BAPIs for :

Production Order header level confirmation(BAPI_PRODORDCONF_CREATE_HDR)

Goods Issue to production order (BAPI_GOODSMVT_CREATE)

Goods Receipt against production order (BAPI_GOODSMVT_CREATE)

Currently we are committing all three BAPIs one by one. We are using

BAPIs for production order confirmation cancellation and goods movement

cancellation in case of any error. This is not acceptable as per

business because it causes reversal document and consumes a number

range too.

If we use single BAPI transaction commit for all the BAPIs , it does

not work as SAP LUW gets refreshed after every BAPI. Moreover it will

write data of only last BAPI to data base or it will give some error.

Kindly suggest if we can commit all the three BAPIs in such a way that

either all gets committed successfully(without errors) or neither gets

committed whenever there is any error in any BAPI in sequence.

Regards.

Re: Synchronized BAPI posting

jitendra_it — Sun, 18 Sep 2011 07:32:22 GMT

Hi me_sappp,

Please check below thread.

Thanks

Jitendra

Re: Synchronized BAPI posting

sjeevan — Mon, 19 Sep 2011 02:56:23 GMT


We are using BAPIs for production order confirmation cancellation 
and goods movement cancellation in case of any error.

In PP Shop Floor standard process Production order confirmation, goods issue to production and goods receipt from production are independent of each other unless you implement any badi which changed this.

So, my suggestion would be to do all the three. Normally there will not be any error in confirmation (unless you're using collective orders then you cannot confirm before the subordinate orders) and goods receipt from production. The errors are most probably gonna be in goods issue and they're collected in a table AFFW and can be manually fixed through TCode COGI.

But if you wanna do all the three only if none of them has errors you can use the WAIT option in the thread quoted by the above poster.