Show TOC

Bundling, Splitting, and Transforming MessagesLocate this document in the navigation structure

Use

In an integration process you can transform messages. To do so, use a transformation step that calls an appropriate mapping program.

You can execute the following transformations:

  • n:1 Transformation: Bundles multiple messages into one message, for example, individual purchase order items into one purchase order.
  • 1:n Transformation: Splits a message into multiple messages, for example, a purchase order into the individual purchase order items.
  • 1:1 Transformation: Converts a message into another message, for example, a message that is defined by interface A is converted to message that is defined by interface B.

Mappings

Since no receiver information is available in the transformation step, there can be no value mapping within the transformation step. If the messages to be transformed give values in different formats, for example different date formats, you must first 'normalize' the values before the messages can be processed in the process. To do so, define a message mapping with a corresponding value mapping.

More information:

Checklist: Making Correct Use of Mappings

Message Mappings

Value Mapping

Attachments for n:1 and 1:n Transformations

If the messages you want to bundle contain attachments, the system collects them together and appends them to the bundled message. The source system or source systems must ensure that the attachments each have a unique name. If they do not, the most recently received attachment overwrites any attachments with the same name.

If the message you want to split contains attachments, the system replicates them and appends them to all the new messages.

Procedure

Define a Mapping

  1. In the Integration Repository, define an interface mapping with the relevant mapping programs.

    More information: Multi Mappings

    The Business Process Engine (BPE) always uses the most up-to-date version of the mapping.

Define a Transformation Step

  1. Insert a transformation step at the relevant position in the integration process.
  2. Enter the interface mapping in the attributes for the transformation step.

    Depending on the interface mapping that you specify, the relevant source and target messages are displayed.

  3. For each source or target message, specify the container element that contains the message reference or that the message reference is to be written to.
  4. Specify whether the system is to create a new transaction for the transformation step.

    No New Transaction: You can expect better system performance if the system does not create a new transaction. Only select this setting if the mapping does not require write-to access to the database.

    Create New Transaction: Select this setting if the mapping requires write-to access to the database.

    More information: Define Transactional Behavior of an Integration Process

  5. You can specify an exception that is to be thrown when a system error (a permanent error) occurs.

    More information: Exception Handling

Example