M1 and M2 of QoS = EO/EOIO

[Former Member]

The the case of Qos is EO/EOIO, the XML Message worflow is:

1. The application writes application data to its database tables.

2. Integration Engine is called for the first time (EO/EOIO), Message M1 generated

3. Integration Engine is called for the second time (EO/EOIO), Message M2 generated

4. Application ends transation with an explicit COMMIT WORK

Can anybody explain what is difference between first and second IE call?

[Former Member · Accepted solution]

Well its a little hard for me to understand your exact problem,anyways based upon what i understood.

if QoS is EO for the first call and that gets stuck then it won't affect the second call,but if the QoS for the first call is EOIO and it gets stuck then 2nd call will get stuck too

is this what you are looking for ?

[Former Member · Accepted solution]

Well, you are right. Let me explain the in more detail. In the scenario of Client Proxy communicate with XI. at the sender side. the M1 and M2 are created as I described above according to online dicumentation. Just cannot understand why 2 messages are created

[Former Member · Accepted solution]

Do you mean that you sent one message from Client Proxy which created 2 message in SAP XI?

If so then make sure you have only communication channel (XI) and R/3 only one program sends a message.

Gaurav Jain

Edited by: Gaurav Jain on Jun 20, 2008 12:14 AM

[Former Member · Accepted solution]

No, I mean 1 call why will generate 2 message? according to online documentation

[Former Member]

should be 2 different msgs