topic Re: Problem with COMMIT WORKS command in Application Development and Automation Discussions

Problem with COMMIT WORKS command

marcin_cholewczuk — Thu, 27 Sep 2007 08:45:56 GMT

Hello all,

I’ve a little problem. It seams that I don’t understand how ‘commit work’ command works. When I’m calling transaction with USING parameter:

CALL TRANSACTION 'FPSA' USING itab_bdcdata.

When inside of that transaction ‘Commit works’ occur, than commit is being executed and transaction is ending which is not good, because there is still code left that should be executed.

When I run transaction without USING

CALL TRANSACTION 'FPSA'

Everything works fine. I’ve tried using UPDATE addition in CALL FUNCTION, but without result. Does anybody know what is the problem?

Re: Problem with COMMIT WORKS command

Former Member — Thu, 27 Sep 2007 09:06:17 GMT

Hi,

I had a similar error. When I called perform or a call transaction and after that code I called commit works, nothing works.

I must use commit and rollback work in the same block of code, and everything works fine. So I think that for a correct use, all code must be inside the same code block for working properly.

Re: Problem with COMMIT WORKS command

Maciej_DomagaBa — Thu, 27 Sep 2007 09:32:30 GMT

This is meant to work exactly as you described:

A transaction called with CALL TRANSACTION USING returns right after COMMIT occurs - if you don't provide any additional options.

There is a way to make such transaction continue with the code after the commit. You just have to use "OPTIONS FROM" addition of the "CALL TRANSACTION" statement - parameter RACOMMIT.

For more information put the cursor on CALL TRANSACTION statement in your abap code and press F1.

regards

good luck

Re: Problem with COMMIT WORKS command

marcin_cholewczuk — Thu, 27 Sep 2007 11:27:24 GMT

I've found that out, but still thankyou.