Diff between Maintain Order at runtime in Interface determination and EOIO

[Former Member]

Hi All,

Whats the diff between Maintain Order at runtime in Interface determination and EOIO and when do we use these?

Regards,

XIer

[Former Member · Accepted solution]

HI

Whats the diff between Maintain Order at runtime in Interface determination and EOIO and when do we use these?

Maintain Order at runtime - will allow the system to decide data need to be pushed to which receiver. This is very useful when you have more than one receiver and you wanted to confirm delivery of one before another in consecutive steps.

EOIO will allow you to even split the messages in defined queues and process then one by one. This is useful when you have bunch of data coming in and you want them not to stuck at IE or prioritize them as per requirement.

In brief EOIO works message(can be multiple payloads) level for PI and Maintain order works at payload level for receiver.

Thanks

Gaurav

[VijayKonam · Accepted solution]

Check Aamirs reply here -

VJ

[SudhirT]

Hi,

Maintain order at runtime is for the different interfaces used, this property maintains the sequense EOIO for different interfaces . By removing this check EO comes into picture for interfaces. for more info refer to

http://help.sap.com/saphelp_nw04/helpdata/en/42/ea20e737f33ee9e10000000a1553f7/frameset.htm

and EOIO is to make sure that all the messages are processed in sequential order.

Thanks!

[Former Member]

It is the context that makes them different.

Maintain Order at runtime in Interface determination -> applies at order to be maintained at the receiver level...

EOIO -> applies order at the message level.