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

[Former Member]

Hi,

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.

Thanks.

Mickael

PI 7.11 + ECC 6.0 (702)

[Former Member · Accepted solution]

I suggest checking out SAP Help on serializing IDocs. "Maintain Order at Runtime" is only relevant for Multiple Inbound Interfaces.

Regards, Martin

[Former Member · Accepted solution]

Hi Martin,

So that confirms what I saw in this Help SAP Interface Determination after wrote this post.

But by doing on serializing IDocs., in ECC, I will have Idocs in status 75... well... maybe in that case, I have not choice...

so "Maintain Order At Runtime" is not THE magic button that I expected (not for my case),

Thanks.

Mickael

[udo_martens]

Hi Mickael,

this checkbox will control messages after a split by interface determination - if the determination finds more than one interface.

The checkbox has no meaning for you, because the messages actually are splitted outside PI (or in the receiver adapter). From my point of view you need to split the messages in a BPM mapping and post them in modus EOIO.

/Udo

[Former Member]

Hi Udo,

Thanks.

BPM is not indicated in this case, in my mind. coz to do a split of an "unbounded" IDoc... well... that's the same than using the standard Idoc ( ! ) without "MaxOccurs = unbounded" IDoc.

Regards

Mickael