topic Re: How to avoid the BAPI_TRANSACTON COMMIT effect on next calling FM. in Application Development and Automation Discussions https://community.sap.com/t5/application-development-and-automation-discussions/how-to-avoid-the-bapi-transacton-commit-effect-on-next-calling-fm/m-p/5408417#M1241972 <HTML><HEAD></HEAD><BODY><P>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 .</P><P>WS_REVERSE_GOODS_ISSUE always getting failed (with sy-subrc = 1 )becoz of the previous BAPI.</P><P></P><P>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.</P><P></P><P>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 .</P></BODY></HTML> Thu, 09 Apr 2009 08:26:07 GMT Former Member 2009-04-09T08:26:07Z How to avoid the BAPI_TRANSACTON COMMIT effect on next calling FM. https://community.sap.com/t5/application-development-and-automation-discussions/how-to-avoid-the-bapi-transacton-commit-effect-on-next-calling-fm/m-p/5408415#M1241970 <HTML><HEAD></HEAD><BODY><P>Dear experts,</P><P></P><P>How to avoid the BAPI_TRANSACTON COMMIT effect on next calling FM in a report program.</P><P>regards</P><P>Sriram</P><P></P><P>Edited by: SRIRAM on Apr 8, 2009 5:50 PM</P></BODY></HTML> Tue, 07 Apr 2009 13:37:30 GMT https://community.sap.com/t5/application-development-and-automation-discussions/how-to-avoid-the-bapi-transacton-commit-effect-on-next-calling-fm/m-p/5408415#M1241970 Former Member 2009-04-07T13:37:30Z Re: How to avoid the BAPI_TRANSACTON COMMIT effect on next calling FM. https://community.sap.com/t5/application-development-and-automation-discussions/how-to-avoid-the-bapi-transacton-commit-effect-on-next-calling-fm/m-p/5408416#M1241971 <HTML><HEAD></HEAD><BODY><P>Hi,</P><P></P><P>Can you elaborate...</P><P></P><P>Thanks,</P><P>Shailaja Ainala.</P></BODY></HTML> Wed, 08 Apr 2009 12:26:53 GMT https://community.sap.com/t5/application-development-and-automation-discussions/how-to-avoid-the-bapi-transacton-commit-effect-on-next-calling-fm/m-p/5408416#M1241971 Former Member 2009-04-08T12:26:53Z Re: How to avoid the BAPI_TRANSACTON COMMIT effect on next calling FM. https://community.sap.com/t5/application-development-and-automation-discussions/how-to-avoid-the-bapi-transacton-commit-effect-on-next-calling-fm/m-p/5408417#M1241972 <HTML><HEAD></HEAD><BODY><P>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 .</P><P>WS_REVERSE_GOODS_ISSUE always getting failed (with sy-subrc = 1 )becoz of the previous BAPI.</P><P></P><P>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.</P><P></P><P>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 .</P></BODY></HTML> Thu, 09 Apr 2009 08:26:07 GMT https://community.sap.com/t5/application-development-and-automation-discussions/how-to-avoid-the-bapi-transacton-commit-effect-on-next-calling-fm/m-p/5408417#M1241972 Former Member 2009-04-09T08:26:07Z