Community
Application Development and Automation Discussions
Join the discussions or start your own on all things application development, including tools and APIs, programming models, and keeping your skills sharp.
cancel
Turn on suggestions
Auto-suggest helps you quickly narrow down your search results by suggesting possible matches as you type.
Showing results for 
Search instead for 
Did you mean: 
Read only

How to avoid the BAPI_TRANSACTON COMMIT effect on next calling FM.

Go to solution
Former Member

‎2009 Apr 07 2:37 PM

0 Likes
501

Dear experts,

How to avoid the BAPI_TRANSACTON COMMIT effect on next calling FM in a report program.

regards

Sriram

Edited by: SRIRAM on Apr 8, 2009 5:50 PM

1 ACCEPTED SOLUTION
Read only

Go to solution
Former Member

‎2009 Apr 08 1:26 PM

0 Likes
402

Hi,

Can you elaborate...

Thanks,

Shailaja Ainala.

2 REPLIES 2
Read only

Go to solution
Former Member

‎2009 Apr 08 1:26 PM

0 Likes
403

Hi,

Can you elaborate...

Thanks,

Shailaja Ainala.

Read only

Go to solution
Former Member
In response to Former Member

‎2009 Apr 09 9:26 AM

0 Likes
402

I am calling BAPI_GOODSMVT_CANCEL ( along with BAPI_TRASACTION_COMMIT ) and WS_REVERSE_GOODS_ISSUE in the sequence as per the requirement in a report .

WS_REVERSE_GOODS_ISSUE always getting failed (with sy-subrc = 1 )becoz of the previous BAPI.

Under start-of-selection event if WS_REVERSE_GOODS_ISSUE called first and BAPI 2nd in sequence ,then every thing is fine and gettig sy-subrc = 0.

How to avoid the impact of bapi in this regard and what are all the syatem varriables need to be cleared before calling WS_REVERSE_GOODS_ISSUE .