topic Problem with commit work when using call transaction in Application Development and Automation Discussions

Problem with commit work when using call transaction

Former Member — Tue, 28 Dec 2010 11:26:17 GMT

Hi,

I have a problem while using commit work when usin call transaction.

Following is my code snippet.

Program 1


--------
-------
Begin of PAI module 
------
-----
call transaction 'ZTCODE' using bdcdata.
------
end of PAI 
------

Program of ZTCODE


-----
-----
call function 'MPLAN_CREATE'
BAPI_TRANSACTION_COMMIT
----
call function 'MPLAN_START'
----
----

Here problem is that when I am calling my Program1 the transaction ZTCODE is called and once the control finishes the

BAPI_TRANSACTION_COMMIT statement, it is not executing the remaining statements. It is directly going back to the PAI module where the call transaction statement in the PAI module of Program1 without executing the remaining statements after the commit statement.

Please let me know your suggestions

Re: Problem with commit work when using call transaction

kesavadas_thekkillath — Tue, 28 Dec 2010 11:39:20 GMT

You have to use RACOMMIT = X in call transaction parameters.( ctuparams ).


wa_ctuparams-racommit = 'X'.  "<--
wa_ctuparams-dismode = 'A'.
wa_ctuparams-updmode = 'S'.
CALL TRANSACTION 'ABCD' USING bdcdata
                          OPTIONS FROM wa_ctuparams.

Re: Problem with commit work when using call transaction

Former Member — Tue, 28 Dec 2010 12:05:39 GMT

Hi Keshav,

Thanks a lot for your reply. My problem got resolved

Regards,

Deepti