IDocs - Selection Criteria

[Former Member]

In an IDoc to IDoc scenario, what will be different behaviour in the following cases.

>If the reciever is not ready, with a QOS - EOIO.

>If the reciever is not ready, with a QOS - EO.

Any links or docs in this direction would help me.

-Naveen.

[Former Member]

Hi

can u pl expand QOS, EO, EOIO?

thanx

kiran

[Former Member]

Hi Naveen and Kiran,

You have this SAP Help which explains the Quality of Service (QoS):

http://help.sap.com/saphelp_nw2004s/helpdata/en/41/b714fe5ffc11d5b3ea0050da403d6a/content.htm

With that you will understand the difference between the three possibilities: BE, EO and EOIO.

Regards

Mickael

[bhavesh_kantilal]

Hi,

When you ask Receiver not ready , does it imply that the R3 system is down?

In this case, the TRFC that connects to the R3 system ( using RFC destination created in SM59 ) will contain a TRFC error / entry in Sm58. it will retry according to the retry interval. Corresponding Jobs can be scheduled to restart these messages according to some time period.

The QOS has no effect on this behavior. As and when the R3 system gets up, EOIO will process the message in the same order as they are waiting in the QUEUE.

Regards,

Bhavesh

[MichalKrawczyk]

Hi,

with EO you can restart any queue entry

with EOIO only the first one

Regards,

michal

[bhavesh_kantilal]

Mike,

><i>with EO you can restart any queue entry

with EOIO only the first one</i>

I did not think of this Good one.

Regards,

Bhavesh

[Former Member]

Bhavesh and Michael,

Thanks for your inputs.

Bhavesh,

<i>When you ask Receiver not ready , does it imply that the R3 system is down?</i>

Yeah.

Bhavesh and Michael,

Any other inputs.....please