Transformation Step 

Use

You use a transformation step ( ) to do the following:

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

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.

For more information about making correct use of transformation steps and mappings, see: Checklist: Making Correct Use of Mappings.

Attachments for n:1 and 1:n Transformations

If the messages you want to bundle contain attachments, the system gathers them together and appends them to the bundled message.

If the message you want to split contains attachments, the system replicates them and appends them to all the messages once they have been split.

Exception

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

More information: Exception Handling

Activities

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

More information: Multi-Mappings

The Business Process Engine always uses the most recent version of the mapping.

       2.      Specify 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.

Example

For examples of how to use transformation steps, see:

Example: Collecting and Bundling Messages from One Interface

Example: Collecting and Bundling Messages from Multiple Interfaces