Contact Free trial Login

Create and Configure an Outbound Message Flow

Create an outbound message flow to receive application messages from your backend systems, transform and send the translated EDI message to your trading partners.

After you create the outbound message flow, you configure the receive endpoint, source message type, target message type, and target endpoint.

Create an Outbound Message Flow

  1. From your Anypoint Partner Manager Sandbox or Production environment, select Message Flows in the left navigation menu.

  2. Click New message flow > Send to partner in the upper right of the page.

  3. Select an existing Partner from the list and click Select.
    A new message flow is created.

  4. Alternatively, you can create a new partner:

    1. From the Select a partner dialog, click New to create a new partner.

    2. Follow the process to create a Trading Partner.

    3. Click Create Partner and Message Flow.

Configure the Source at Host Endpoint

  1. Expand the Source at <host-name> section.

  2. In Endpoint:Source at <host-name>, click Select.

  3. To use an existing receiving endpoint:

    1. Select the endpoint from the list and click Select in the lower right side of the page.
      The endpoint is added to the message flow, and you see a message that tells you the endpoint is missing an identifier.

    2. Click Add to add a unique identifier for the endpoint.

  4. To create a new receiving endpoint:

    1. Click New on the right of the search box.

    2. From the Owner drop-down, select the endpoint’s owner.

    3. From the Protocol drop-down, select the protocol and configure it according to the protocol you select:

  5. Click Save.
    The endpoint is added to the message flow.

Configure the Source Message Type

  1. Expand the Source message type section, and click Select.

  2. To use an existing message type:

    1. Select the message type from the list and click Select in the lower right side of the page.
      The message type is added to the message flow.

  3. To create a new message type:

    1. Click New on the right side of the search box.

    2. From Format, select either:

      • XML

      • JSON

    3. From Schema, click Choose file and browse to the location of your custom schema.

    4. Accept the default value for Message type identifier or enter a new value.

    5. Click Choose file to browse to the location of the DataWeave map, and select it.

    6. Click Save.

  4. Under the Reference IDs section:

    1. Click Select to add the reference identifier for the trading partner.

    2. From the <host-name> reference ID drop-down list, select your organization’s internal reference ID (such as business unit name) as it would appear in the data element of the source JSON/XML payload from your backend systems.

Configure the Target Message Type

  1. Expand the Message type section.

  2. Click Select to select a message type or to create a new message type.

  3. To use an existing message type, select the message type from the list and click Select.

  4. To create a new message type:

    1. Click New on the right of the search box.

    2. From Format, select X12.

    3. From Version, select the X12 version.

    4. From Message type, select the message type.

    5. From schema select Use standard X12-<version>-<message-type> or select Customize to define a custom schema.

    6. Click Save.
      The message type and its validation settings are added to the message flow.

  5. In the Acknowledgment section, select the Expect functional acknowledgment checkbox if you expect to receive functional acknowledgments (997) back from your trading partner.

  6. Click Select to specify the endpoint from which to receive the acknowledgement transactions from your partner.

  7. Alternatively, you can create a new receive from partner endpoint:

    1. Click New.

    2. From Owner, select the endpoint owner.

    3. From Protocol, select the protocol and configure it accordingly:

      • AS2

      • SFTP

    4. Click Save.

  8. In Mark overdue after, accept the default value of 24 Hours or configure values based on when you want the outbound transaction to be designated as overdue for an acknowledgment, according to the SLAs you have with your trading partner.
    When functional acknowledgement is not received within the specified timer value, Partner Manager marks the outbound transactions as Overdue.

  9. In the X12 Settings drop-down list, select the X12 settings.

    By default, Partner Manager uses the X12 send settings that are configured in the trading partner profile page for message validation, delimiters, and character encoding.

    If you want to apply custom validation settings and delimiters for the message flow you are setting up, you can select Custom X12 settings and provide custom configuration values.

  10. In X12 Identifiers, select the sender and receiver identifiers that are configured under the host and trading partner profiles to use them on the X12 ISA and GS segments.

Import the Translation Map

Expand the Map section and click Import to translate the application message format to EDI.

Follow these instructions to create your application message-to-outbound EDI map (XML or JSON) in Anypoint Studio.

Verify the Message Flow is Complete

Partner Manager dynamically validates the message flow configuration elements for completeness and displays a green checkmark if all the building blocks of the message flow are complete. After you verify the configurations, you are ready to deploy the message flow.

Was this article helpful?

💙 Thanks for your feedback!

Edit on GitHub