Skip to Content
Former Member
Mar 15, 2007 at 09:04 AM

Ensure complete transaction commit



I have a scenario where one message from a legacy system can map into one or more messages.


                   -> DEBMAS06 (0..unbounded)

message -> XI -> ADR3MAS02 (0..unbounded)

                   -> LINK01 (0..unbounded)


Is it possible to ensure that the complete transaction is on tRFC before commit?

Right now I have a parallel flow where the split is done in the interface determination. And I have no chance of stopping successful processed messages, if an error should occur in another flow!?!

I did the scenario as a BPM, where all transformation (mapping) is done before the individual send steps are executed. Not that it is very likely, but the possibility of one send step successfully sends the IDOC, followed by another send step that fails, could occur. This means that it is not 100% transactional handled.

What I would like, is a way to put the IDOC's on the tRFC queue, and first release them, when all messages are successfully in place!

Any ideas?