Defining Extended Receiver Determinations 
When using routing conditions or routing rules in receiver determinations, the receivers of a message are determined at runtime by evaluating the condition (which depends on the content of the message). However, the names of the receivers have already been defined at configuration time in the Integration Directory (dual-stack installation option: in the receiver determination object; Advanced Adapter Engine Extended (AEX): integrated configuration, Receiver tab).
When you configure routing that way (referred to as standard receiver determination), you have to specify the receiver names as part of the configuration procedure in Integration Directory.
A more flexible way to configure routing is offered by the extended receiver determination.
In an extended receiver determination, you can specify a mapping program that takes over the task of finding out the actual receivers at runtime. You can design the mapping program that way that the receivers of the message are read from a list that might be part of an external data source (mapping look-up approach).
This approach has the following advantages:
Storing receiver names in an external data source allows to update of the receiver list without the need of a cache refresh.
Storing receiver names outside the Integration Directory allows non-integration experts to maintain receivers.
Extended receiver determination is supported for both kinds of message processing (dual-stack and the Advanced Adapter Engine message processing).
More information:
Defining Extended Receiver Determination (Dual-Stack) (dual-stack message processing)
Note
This procedure is only relevant in case you have a dual-stack SAP NetWeaver PI installation and configure message processing using both stacks (Integration Engine and Advanced Adapter Engine).
Defining Extended Receiver Determination (Advanced Adapter Engine) (message processing using the Advanced Adapter Engine only)
Note
This procedure is relevant in case you have a dual-stack SAP NetWeaver PI installation and configure message processing using the Advanced Adapter Engine only (bypassing the Integration Engine).