3088223 - QoS EOIO doesn't propagate to receiver system in correct order in case of mapping split

You have configured mapping split in the Integrated Configuration scenarios but find the execution time not following the order of the arrival time of the messages in the receiver system as messages are in different queues. Even the sequence of the message in PI/PO system & receiver system is exactly the same. EOIO sequence is respected and the message creation date in both systems are the same. You would like to have the messages processed in the same queue to ensure the execution date happens in order as well.

You have tried following options but still cannot achieve this requirement.

1. SAP Note 2125230 - The QoS EOIO does not propagate to receiver system over XI protocol
2. Maintain staging and logging in Integrated Configuration level as BI=3,MS=3 per SAP Blog --> Part: Scenario-specific staging/logging using advanced settings of Integrated Configuration.
   Integrated Configuration scenarios with Quality of Service EOIO and mapping split should be configured to store the message at Receiver Determination step (e.g. MS=3 or BI=3,MS=3) in order to generate properly the serialization of parent messages and related subsequences. If there were multiple messages related to each other logically, you would see them within the sequence. This is when the sequence of processing matters and EOIO is enforced.

• SAP NetWeaver
• SAP Process Integration

Process Integration, PI, Process Orchestration, PO, NetWeaver, XI, AEX, EOIO, message, split, mapping split, ICO, Integrated Configuration, sequence, Maintain order at runtime, XI_OUTBOUND_SUBSEQ , KBA , BC-XI-CON-MSG , Messaging System , BC-XI-CON-AFW , J2EE Adapter Framework , Problem