"Problem" with COMMIT WORK AND WAIT

[Former Member]

Hi everyone!

I'm facing the following situation:

I have a Z program that calls MIGO, via CALL TRANSACTION. The only thing I do when calling this is filling a few fields, so the user has to complete the operation before going back to Z program.

When someone executes MIGO in the normal way, I mean, without a CALL TRANSACTION command, there was a additional step, a modification made in the standard code for someone before. But this part of the code didn't execute when calling MIGO via CALL TRANSCATION.

What I have found out is that just before this code inserted, there was a COMMIT WORK AND WAIT command, and was exactly in this point that, when using the first aproach, it leaves MIGO.

Is there a way to execute the entire process in MIGO, I mean , do not leave it at COMMIT command? I've tried to pass at CALL TRANSACTION command diferent UPDATE parameters (i.e: 'S', 'A' and 'L'), but it didn´t work as well.

I hope you could get the point!

Thanks in advance!

Raphael

[Former Member]

I've just found out something interesting about that.

When I make a CALL TRANSACTION, without passing a table bdcdata, the transaction doesn't leave at the COMMIT WORK command.

So, I think it won't work with the bdcdata!

Raphael