Problem with 'CALL TRANSACTION'

[Former Member]

Hello,

I'm having the following problem:

When I perform an operation (button click to send an e-mail), somewhere in an user-exit I have a call to a 'Z' function module (FM X). That FM X calls the same transaction I was before using batch data. Everything works fine.

Now imagine that I click the same button again (without leaving the transaction) to try to send a new e-mail. Somewhere in the code I have another FM (FM Y) for sending mails with a "commit work" statement. The second time, after the commit work, everything is different because the program jumps to the end of FM X. I suppose this is happening because I'm using the same session and I must have some kind of parameters saved in memory.

Do you know a way to call FM Y without the program returning to FM X?

Thanks in advance.

Regards,

ricardo

[Former Member]

Difficult to understand the exact scenario, you give too much information, please keep things the simplest possible.

Are you talking about CALL TRANSACTION ... USING ... ? (also called CTU, it uses BDC technology)

In that case, by default, any COMMIT WORK stops the transaction. If you use OPTIONS FROM keyword to CTU, with field RACOMMIT = 'X', then the COMMIT WORK do not stop the transaction any more.

[Sandra_Rossi]

Difficult to understand the exact scenario, you give too much information, please keep things the simplest possible.

Are you talking about CALL TRANSACTION ... USING ... ? (also called CTU, it uses BDC technology)

In that case, by default, any COMMIT WORK stops the transaction. If you use OPTIONS FROM keyword to CTU, with field RACOMMIT = 'X', then the COMMIT WORK do not stop the transaction any more.

[Former Member]

you can try making ur FM run in update task. Check the attributes.