Multi-mapping and BPM (integration process) always use to go hand-in-hand. Since SPS14, this isnt true anymore. In the case of message splits (1:n transformations), multi-mappings can now be created and used in non-BPM scenarios. Referred to in many different ways, but most commonly as mapping-based message splits, this new enhancement affords SAP NetWeaver XI developers an opportunity to take BPM out of the equation for message split based scenarios.
Here are the highlights to get this set up:
In design, create a multi-mapping as if it was being done for a multi-mapping within an integration process transformation. Multi-mapping for a mapping-based message split is created in the same way.
In the Messages tab, you set the cardinality (i.e. occurrence) for the target messages.
Again, for the Interface Mapping, proceed as normal.
For mapping-based interface determination, a new option is available starting with SPS14. A radio button option called Type of Interface Determination exists in which option Standard is the default. Choose Enhanced.
Selecting this option changes the Interface Determination screen as shown below. For parameter Interface Mapping, value help is available to select the corresponding Interface Mapping previously set up in design. Mapping-based message split and interface determination is ready to go.
In the monitor (SXMB_MONI), notice that after the Request Message Mapping pipeline step, there are multiple SubMainDocuments under Payloads.
A mapping-based message split will ultimately produce n individual messages, but not until it reaches the Adapter Engine (AE). Inside the Integration Engine (IE), the messages are grouped together and persisted as one bulk message. The bulk message is sent to the AE where it splits the bulk message into individual messages and persists them. This, along with the absence of the usual overhead included in a integration process, drastically reduces resource consumption and improves performance.
- Messages that result from the split in a mapping-based message split are sent using one AE. So only adapters running on the AE are supported. In particular, this means that target IDOC message splits are not supported since the IDOC adapter is not part of the AE.
- The target system of the message splits cannot be an integration process.
- Attachments from the original message are not appended to the messages resulting from the message split.