Defining Extended Receiver Determination (Dual-Stack)

Procedure

Define a suitable mapping in the ES Repository.
More information: Mapping Messages to Each Other Using Mapping Objects

In particular, do the following:

Define an operation mapping and assign the abstract service interface ReceiverDetermination as the target interface. The service interface ReceiverDetermination is in the Enterprise Services Repository in the software component SAP BASIS (namespace http://sap.com/xi/XI/System).

Define the message mapping or mapping program that is to determine the receivers at runtime. Assign this message mapping or mapping program to the operation mapping specified before.

Note
The service interface uses the message type Receivers and the data type Receivers. The data type Receivers describes a list of receivers and has the following structure:

The following instance of the data type Receivers contains two receivers. The first receiver comprises a party (element Party) and communication component (element Service) and is identified by a DUNS number; the second receiver comprises a communication component without a party.

End of the note.
Syntax
1. ```
<Receivers>
```
2. ```
<Receiver>
```
3. ```
<Party agency="016" scheme="DUNS"></Party>
```
4. ```
<Service>"MyService"</Service>
```
5. ```
</Receiver>
```
6. ```
<Receiver>
```
7. ```
<Party agency="http://sap.com/xi/XI" scheme="XIParty"></Party>
```
8. ```
<Service>"ABC_200"</Service>
```
9. ```
</Receiver>
```
10. ```
</Receivers>
```
End of the code.
You can specify party and communication component for each receiver.
Define an extended receiver determination in the Integration Directory
Enter the outbound interface of the operation mapping from above in the key of the receiver determination as the outbound interface. Assign this operation mapping to the receiver determination.

More information: Defining Extended Receiver Determination
Define the remaining configuration objects in Integration Directory (interface determination, sender and receiver agreements).

Note
As you can use wildcards (*) to mask the keys of these configuration objects, you can leave out the names of the receivers.

Usage of wildcards therefore makes it possible to fully source out the determination of receivers to a mapping look-up executed at runtime. With other words, the names of the receivers don't need to be known already at configuration time.

More information on usage of wildcards: Defining Configuration Objects Generically/Specifically

End of the note.

Note Note

If the mapping program returns an XML file with empty or missing <Service></Service> tag, the message is routed to the default receiver (that is configured in the receiver determination under If No Receiver Is Found, Proceed as Follows, option Select the Following Receiver:).

End of the note.