Contact Free trial Login

Configure X12 Send (Outbound) Settings

Partner Manager enables you to configure the X12 envelope parameters, delimiters, validation rules, character encoding, and control numbers to apply when sending an outbound X12 transmission to a trading partner.

Configure the Send Settings

  1. In the left navigation menu, select the partner for whom to configure the send settings.

  2. In the Validation and acknowledgment settings section, under Send to <partner-name>, click X12.

  3. In the menu on the left, select the setting to configure:

  4. Click Save.

The values you configure in the partner’s settings page are used by default for all X12 messages going to that trading partner. You can override the settings you configure at the partner level, with the exception of TA1 and control numbers, at the message flow level by selecting the Custom option while creating an outbound message flow.

It can take up to five minutes for your configuration changes to sync with Mule.

General Settings

Use the following settings to configure the transaction usage, the responsible standards agency, and to enforce length limits and conditional relationship validations:

Setting Description Default Value

Usage indicator (ISA15)

Indicates if the X12 transaction sent is for testing, production or information only.

Possible values include:

  • I - Information

  • T - Test

  • P - Production

  • P - Production
    For production environments

  • T - Test
    For sandbox environments

Responsible agency code (GS07)

Define the standards agency responsible for the standard in the GS segment.

Possible values include:

  • T - Transportation Data Coordinating Committee (TDCC)

  • X - Accredited Standards Committee X12

X

Enforce length limits

If selected, any data elements with a length outside of the definition in the X12 schema cause the generation of the X12 transaction to fail.

Enabled

Enforce conditional relationship validations

If selected, any missing conditional data elements will cause the generation of the X12 transaction to fail.

Enabled

Authorization Settings

Use the following settings to configure the authorization and security qualifier for the transactions:

Setting Description Default

Authorization qualifier (ISA01)

None

Security qualifier (ISA03)

None

TA1 Acknowledgment Settings

Use the following settings to configure whether a technical acknowledgment is required, and the receive endpoint for the acknowledgment:

Setting Description Default

Expect TA1 for each transmission sent to <partner>

If selected, sets the value in ISA14 to 1 on the generated X12 payload indicating that a Technical acknowledgement (TA1) is required.

Disabled

Endpoint

When the option to expect a TA1 is selected, click Select to specify the Receive from <partner> endpoint the acknowledgment will be received from as an inbound transmission.

None

Global Control Numbers

Partner Manager applies a global control number at the partner level on the X12 interchanges and functional groups generated from outbound message flows. These control numbers are sequenced across all message types (including functional acknowledgements) that are sent to a trading partner.

The control number starts with a default value of 1, and is sequentially increased as your organization begins sending outbound transmissions.

If you need to set the control number sequence value to a different number to maintain sequencing and avoid duplication:

  1. Click Change and enter the desired control number.

  2. Click Save.

It can take up to five minutes to apply the change at runtime.

Character Set and Separators

These settings enable you to set the character encoding and delimiters to use on the generated X12 payload:

Setting Description Default Value

Character set

Characters allowed in string data.

Possible values include:

  • Basic

  • Extended

  • Unrestricted

Extended

Character encoding

Character encoding for messages.

Possible values include:

  • PLATFORM

  • ASCII

  • ISO8859_1

  • IBM1047

  • UTF8

UTF8

Segment terminator

Segment terminator character.

~

Data element separator

Data element separator character.

*

Component element separator (ISA16)

Component element separator character.

>

Line ending between segments

Line ending to add between segments. This allows you to add line endings between segments to improve the readability of the output message text.

Possible values include:

  • NONE
    X12 payload generated will be a single line, with segments separated by the segment terminator character

  • CR
    Carriage Return

  • CRLF
    Carriage Return & Line Feed

  • LF
    Line Feed

CRLF

Was this article helpful?

💙 Thanks for your feedback!

Edit on GitHub