Hi all
I no longer have access to a 7.11 system to fully verify but here are my two cents anyway.
1. Message splitting on AE
As far as I can remember, the restriction on message splitting on the Adapter Engine was on XI 3.0 and PI 7.0. ABAP based adapters like IDoc and XI cannot accept messages split using the multi-mapping technique, which then necessitated workarounds such as editing the IDocs XSD to unbounded.
From PI 7.11 onwards, this restriction is no longer valid, I'm very sure of this at least for the IDoc adapter. We no longer need the workaround, and just by changing occurrence to unbounded for a target IDoc in MM/OM would suffice. I can't remember if this restriction was lifted for the ABAP-based XI adapter as well.
Note: I'm not sure where PI 7.1 is with regards to this.
2. XI 3.0 on SOAP adapter
This is available as of PI 7.11. Refer section 2.3 of the following document. This was to allow for ICO-based scenarios (which was introduced in 7.11) for proxy interfaces.
How to Set Up the Communication between ABAP Backend and SOAP Adapter using XI Protocol
So my suggestion for this is:-
i) Go for message based mapping split (multi-mapping) with receiver XI adapter first
ii) If XI adapter does not work, change to SOAP adapter with XI 3.0
In general, I think it's preferable to perform the split for each employee, rather than sending the whole bunch into the proxy. This allows for easier error handling - if any employee processing fails in the proxy, only that particular message will fail. If the whole bunch is sent, if you want to reprocess a failed message, you need to implement logic to determine which employee processed successfully or not, before reprocessing it.
Regards
Eng Swee
Message was edited by: Eng Swee Yeoh