Enhanced Interface Determination

Posted on Apr. 22, 2010 at 10.45 AM - Chennai, India

When do we use this feature?

We 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. 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.

Implementation Steps:

1. Message Mapping

Define Multi Mapping.

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).

2. Interface Determination.

• 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 we have defined in the Repository.

Life is beautiful! Let's make it meaningful and colorful!