Show TOC

Defining Receiver DeterminationsLocate this document in the navigation structure


You define a receiver determination to specify the receiver or receivers of a message, as well as conditions for the forwarding of the message to the receiver or receivers (optional).

To do this, define one or more message receivers for a sender and an outbound interface (and optionally for a virtual receiver). You also have the option of specifying the conditions to be applied when forwarding a message to the receiver. A condition generally refers to the content of a message. If the specified condition is fulfilled for a particular payload element (the corresponding element has a certain value, for example), then the message is forwarded to the specified receiver(s).

More information: Basic Routing Techniques


1. Create Receiver Determination

To create a receiver determination, perform the following steps:

  1. Call the Integration Builder.

  2. Select the create dialog box for new objects (in the menu under New ).

  3. Choose Start of the navigation path Communication Objects Next navigation step Receiver Determination End of the navigation path.

  4. Specify the communication party (optional), the communication components and the outbound interface for the sender.

  5. Optional: If you want to define the receiver determinations receiver-dependently, enter the communication party and communication component for the receiver. Select Sender Uses Virtual Receiver to show these fields.

  6. You can optionally specify a description and assign the receiver configuration to a configuration scenario or a folder.

  7. Choose Create .


You can use receiver-dependent receiver determinations when configuring Business-to-Business scenarios where the system landscape that is used is only partly known by the communication partners that are involved. In this case, communication party A can release an external view to “its” system landscape. The communication party B in connection with A then knows the externally released virtual receiver to which he can send his messages. Since communication party A now defines a receiver definition that is dependent on a virtual receiver, it can define the internal receiver system to which the message (from communication party B) is to be forwarded.

If you want to create a receiver-dependent receiver determination, select Sender Uses Virtual Receiver in the create dialog. The system then displays the input fields for the receiver (party, communication component).

2. Choose the Receiver Determination Type

There are two options for determining how receivers are determined (radio button):

  • Standard

    If you want to specify the receivers of the message (and optionally routing conditions) manually, select this receiver determination type. You can also specify conditions that refer to the content of the message.

    For a standard receiver determination you can also specify whether the configuration settings are valid for all operations of the outbound interface or whether they are to be defined separately for each operation.

    More information: Defining Standard Receiver Determinations

  • Extended

    If you want to determine the receiver of the message dynamically at runtime by means of a mapping, select this receiver determination type.

    More information: Defining Extended (Dynamic) Receiver Determination

3. Procedure if No Receiver Found at Runtime

Even if you have defined the receiver determination correctly, it is possible that the receiver of a message cannot be determined at runtime.


If you define a condition depending on the contents of a message, it can happen that the current inbound message does not contain the application data required to fulfill the condition.

You can specify what is to happen at runtime if this occurs. You have multiple options. Under Configured Receiver for If No Receiver Is Found, Proceed as Follows , select one of the following options:


Behavior at Runtime

Error message

Message processing is terminated with an error.

You can correct the configuration and restart the message processing.


Select this setting when the underlying scenario is modeled in such a way that a receiver must always be found at runtime. If a receiver is not found at runtime, it is the result of a possible configuration error.


Message processing is ended as defined by your configuration settings. Since no receiver is determined, the subsequent pipeline steps (interface determination, mapping, receiver agreement) are not processed. An error message is not sent to the sender. When you select this setting, you cannot execute the processing of the message again.


Select this setting when messages for which no receiver can be found can typically occur in the underlying scenario.

Continue Message Processing with the Following Receiver:

The message is sent to a fixed predefined receiver. You can specify the receiver in the Party and Communication Component fields (using input help).


These settings apply to asynchronous messages only. If a receiver cannot be found in synchronous communication, an error always occurs.