CALL TRANSACTION: Parameter RACOMMIT has no effect ?

[Former Member]

Hello fellow ABAPers,

we have a COMMIT WORK in a program called with CALL TRANSACTION

that prematurely leads to its abortion ( which I know is normal ).

I tried the parameter RACOMMIT of structure CTU_PARAMS which

can be referred to by using additional command parameters as follows:

DATA: ctu_parameters TYPE ctu_params.
ctu_parameters-dismode = 'E'.
ctu_parameters-updmode = 'A'.
ctu_parameters-racommit = 'X'. "No abortion by COMMIT WORK
CALL TRANSACTION USING itab_bdcdata OPTIONS FROM ctu_parameters.

Setting ctu_parameters-racommit to 'X' is supposed to suppress this effect

(no premature end of the transaction on COMMIT WORK), but it doesn't

seem to have any effect.

Does anybody know how to make it work ?

looking forward to your ansers

Andreas

[RichHeilman]

It is my understanding that the CALL TRANSACTION does an implicit COMMIT WORK when the transaction is complete, so to me there is no reason to do anything with a COMMIT WORK explicitly. Exactly what is the program supposed to do?

Regards,

Rich Heilman

[Former Member]

Hello Rich,

the program is an own written dialog that can either be called up directly from

the Easy Access menu or by double clicking an approval workitem from the

business workplace which then over a business object method does the

CALL TRANSACTION. By providing the necessary screens in the bdcdata-

structure and by calling the transaction in MODE "E" we can directly prompt

the user with the appropriate detail information screen.

Until recently the only thing that happened in the related "User_Command"

section was to trigger a workflow-event that ended the approval workitem.

Now we have a couple of other tables that we want to do UPDATEs/INSERTs

in (and make sure it did happen) before we trigger the confirming event.

Now in the CALL TRANSACTION way of calling the program from the business

workplace the function call for "SAP_WAPI_CREATE_EVENT" is not reached

any more.

regards

Andreas

P.S.: I'm looking forward to reading the book "Next Generation ABAP

Development" that I've ordered today ( I suppose the author R.Heilman

is you ? )

[RichHeilman]

Interesting requirement, but I'm sure that I can not offer anything without actually digging into it. Again, I would have assumed that when the CALL TRANSACTION is finished, anything done within the CALL TRANSACTION would be commit immediatly, with no chance of rollback. You are saying that some funciton within the CALL TRANSACTION is not being fired?

P.S. Yes, that is me, hope you enjoy and can learn some new stuff in the process.

Regards,

Rich Heilman

[Former Member]

Hello Rich,

thanks for your input that at least helped clearing our thoughts.

We will redesign our combination of additional data saving that is

supposed to go along with the confirmation of the approval workitem,

in order to circumvent this problem.

best regards

Andreas