Skip to Content
Former Member
May 28, 2013 at 09:40 AM

Inbound IDoc: "Maintain Order at Runtime" vs "Unbounded" IDoc



I have a classic scenario "File -> PI -> ECC (IDocs DEBMAS)".

For which I defined my flow with a "MaxOccurs=Unbounded for DEBMAS", so PI will send only ONE "unbounded" message with inside several IDocs DEBMAS. After that, in ECC, thanks to ALE config, all DEBMAS will be process one by one... So classic !

Now, I would like to be sure that all DEBMAS IDocs are processed in the exact same sequence that they were in my source file, and so in my ONE outbound "Unbounded" message. For that, in Interface Determination (PI -> ECC IDoc DEBMAS), I use a "Maintain Order at Runtime".

But is it enough?

Does this option "Maintain Order at Runtime" is compatible with an "Unbounded" message ?

because, when ECC receives an "Unbounded" message, it opens this envelop, but are we you sure, ECC will well process IDocs in same sequence and not in parrallel tasks...

or Do we have to define a Serialization ?

Please share with me your feedback.



PI 7.11 + ECC 6.0 (702)