Maintain Order at runtime : Pi 7.30 Single sack

[former_member189558]

Hello,

We are using PI 7.30 Single stack. This version is not having the "Maintain Order at Runtime option" . . However we need to achieve this.

Our scenario is File to Idoc (ADRMAS and CREMAS) and ADRMAS needs to be created first before CREMAS.

We made the entire scenario EOIO , but still the idocs are getting created in ECC inconsistently. Can anybody suggest how can we achieve this.

Thanks and Regards,

Himadri

[Former Member]

Hi,

I dont have access to the version which u have mentioned above, but Maintian order at runtime ensure that if u have entered multiple inbound interfaces then they all will pass in a sequential manner from PI....but it doesnt not guarentees the same sequential processing of message in the target system

Thanks

Amit Srivastava

[Former Member]

Hello.

How did you manage the creation of 2 different IDOCS? do you have one target for them and the content of the file decide which one to create? or do you have 2 receivers (message split)?

in the case of 2 receivers - you have to use BPM - as the EOIO will ensure an old ADRMAS will not be processed before a new ADRMAS, and an old CREMAS will not be processed before a new CREMAS, but it is possible that all the CREMAS IDOCs will be processed while none of the  ADRMAS processed at all (or in short the EOIO - is per IDOC type)

If you need further help - please enclose a screenshot of you integration builder configuration objects.

Hope this information helped,

Imanuel Rahamim.

[former_member189558]

BPM is out of question

[Former Member]

Hello.

Please look at this first: http://scn.sap.com/thread/3196345

As you are using single stack - meaning you have to use IDOC_AAE - and that adapter got EOIO starting from PI 7.31

Even if you did have that option - notice that without BPM your solution will probably not be very esthetic...

Can you please show me how did you configure the scenario in that case?

remember you can't use two receivers - as each of the queues will be EOIO on its own.

Please enclose screenshots of your message mapping, operation mapping and every part of your ICO including each of the communication channels.

Good luck,

Imanuel Rahamim.