There are two different styles to building the channels required for this transformation, a one channel approach and a two channel approach. Both use the "standard EDI outbound channel" as documented in the EDI manual. Channel building is also covered in the iSM manual.

The One Channel Approach

Copy the sample standard channel and all of its components, renaming so they all have unique names. This is done to protect the components from inadvertent changes later on. Add your process flow to the route. Point the listener to the directory that SAP is dropping the IDocs into, and emit to the proper location.

You may have multiple channels, one for each trading partner. Your channel will also run in a serial fashion, split, transform #1, transform #2, next split.

The Two Channel Approach

Create a new channel that just contains the process flow in the route. Use your favorite style to link the two channels, internal listener, directory, and queue. Use the standard channel to run the Ebix transformation.

In this example, channel #1 and channel #2 each run independently and simultaneously. Channel #2 is a standard component that can be reused for many flows. ASN will start to create while the IDoc is still being processed.