In B2B scenarios in Big organizations, we often have situation when one partner (Sender Partner number) need to send same idoc to 100's of different recievers(receiver partner number).
Normally, We have to make one single receiver determination and have to route the Idoc to each receiver based on the condition mentioned in Receiver determination. We had same situation in one of our project where same partner was sending data to 300 different receivers.
It was very difficult to mention condition for all the receivers. It will result in more problems,complexity and also very difficult to troubleshoot the problems, if some condition is wrong or missing.
To avoid this, we used the Virtual receiver determiantion concept of XI.
Add the receiver party also using the Virtual checkbox while creating the receiver determination.
By doing this we can create receiver determination for each combination of sender partner and receiver partner. it means if we have 300 receivers for one sender. we can create 300 different receiver determinations. We do not need to mention condition for any receiver(Even it is possible to use condition within virtual receiver)
How this concept work ?
Idoc contol record contain all the information about Sender/reciever/IdocType/Partner type/Partner function.
XI read this content at runtime and determine Sender and receiver based on this information.
You need to make sure that party Identifiers are correct for both sender and receiver. if they are wrong this setup will not work
Suppose you have partner 123456 which is type KU with Partner function PY. You party will look like :
This Setup will only work for B2B scenarios. It will work for following type of Idoc to file(or any other System)
Sender type Receiver Type Will it Work ?
KU KU/LI/BP Yes
LI KU/LI/BP Yes
B KU/LI/BP Yes
Logical System KU/LI/BP Yes
KU/LI/BP Logical System No
Logical System Logical System No
We can say this setup will only work if we have ALE identifiers of Receiver partner number available i.e It is not a logical System.