When we will go for Ectended Interface Determination

[Former Member]

extended interface determination example give me any one...

Regards,

Vinay

[rajasekhar_reddy14 · Accepted solution]

Enhanced (Mapping-Based) Interface Determination

Use

In an enhanced interface determination, you do not enter the inbound interfaces manually, but first select a multi-mapping. You get the inbound interfaces from the target interfaces of the multi-mapping. The inbound interfaces are determined at runtime during the mapping step.

You typically use an enhanced interface determination if the source message has an element with occurrence 0 ... unbounded (for multiple items of a data record) and you want multiple messages (for the individual items) to be generated at runtime.

For example, you want to split an overall booking for a trip comprising connecting flights into individual booking orders (for each leg of the trip).

You cannot realize this usage case with a standard interface determination (without using an integration process). A standard interface determination does allow you to specify multiple (N) inbound interfaces (with different mapping). In this case, N messages with the same payload and different receiver interfaces are generated from the source message before the mapping step; these are then transformed differently depending on the receiver interface. Therefore it is conceivable to write the mappings in such a way that the first mapping from the source message generates a message that only contains the first item, the second mapping generates a messages that only contains the second item, and so on. However, this no longer works if the number of items can vary with each new source message.

You can use an enhanced interface determination to configure a mapping-based message split for this usage case. You assign the interface determination a multi-mapping that has a target interface with an element with occurrence 0...unbounded. At runtime, the individual messages (for the individual items) are calculated in the mapping step. First, the individual messages are grouped into a bulk message. Then, the bulk message is transferred to the Adapter Engine. The Adapter Engine then splits the bulk message up into the individual messages (see figure).

Procedure at Runtime During Message Split

Note that both the bulk message and all individual messages each have a message header with a receiver interface (see figure).

Receiver Interfaces of Bulk Messages and Individual Messages

The header of the individual messages contains the relevant receiver interface. It is based on the definition of the multi-mapping. Note that the receiver interfaces of the individual messages may be different. The receiver interface of the bulk message is always InterfaceCollection (namespace http://sap.com/xi/XI/System).

If the message split only results in one message, the original message structure remains the same. In this case, a bulk message containing just one individual message is not created.

You can also assign a multi-mapping with multiple different target interfaces to an enhanced interface determination (1:n transformation). Each target interface can contain elements with occurrence 0 ... unbounded.

Messages cannot be sent by using different Adapter Engines in a mapping-based message split. This affects configuration thus: All receiver agreements that have a receiver interface from the mapping entered in the key must only be assigned communication channels with the following adapter types:

- RFC adapter

- SAP Business Connector adapter

- File/FTP adapter

- JDBC adapter

- JMS adapter

- SOAP adapter

- Marketplace adapter

- Mail adapter

- RNIF adapter

- CIDX adapter

The adapters also have to all run on the same Adapter Engine.

Adapters developed by partners also support a mapping-based message split if they run on the same Adapter Engine.

Attachments from the original message are not appended to the messages resulting from the message split.

Activities

To execute a mapping-based message split, perform the following steps:

...

1. Integration Repository: Define the multi-mapping (see Developing Multi-Mappings for Message Splits).

2. Integration Directory: Define the interface determination.

Note the following:

○ The outbound interface of the multi-mapping must be entered as the sender interface in the key of the interface determination.

○ The interface determination type must be set to Enhanced.

○ Select the multi-mapping you defined previously from the Integration Repository.

To select the interface mapping, use the input help ( ).

The target interfaces of the interface mapping are displayed in the Inbound Interfaces frame.

The number of messages (for an inbound interface) created in the mapping step is displayed in the Occurrence column.

regards,

Raj