Defining Extended (Dynamic) Receiver Determination

You can define that the receiver of a message is determined dynamically at runtime by a mapping program. Instead of creating the receivers in the receiver determination manually, you assign a mapping to the receiver determination and this returns a list of receivers at runtime.

A typical usage case is if you do not yet know the names of the receivers at configuration time. In this case, you can define a mapping program, for example, which reads a list of receivers from a table or from the payload of the message at runtime.

In the standard case (manual entry of receiver), you can of course also formulate conditions that relate to the content of the message. However, you have to specify the names of the receivers to which the message is sent under the formulated condition explicitly in the receiver determination. If you define that the receiver of the message is to be determined dynamically at runtime by a mapping program, you do not need to commit to any specific receiver names at this stage.

You can specify party and communication component for each receiver.

Perform the following steps in the Integration Directory:

1. Create a receiver determination and choose the Extended option (radio button).

2. Enter the outbound interface of the operation mapping from step 1 in the key of the receiver determination as the outbound interface (see prerequisites).

3. Assign this operation mapping to the receiver determination.