---
schema_version: "1"
id: dfa3e4f1af6f2c15e2e97ef73188635c18867d5c85b2c455e7476e2a8bb2680e
title: Configuring Send Settings for Outbound X12 Messages
collection: mulesoft
version: current
locale: en-us
portal_url: https://docs.salesforce.com/mulesoft/current/en-us/partner-manager/latest/x12-send-settings.md
canonical_url: https://docs.mulesoft.com/partner-manager/latest/x12-send-settings
source_site: docs.mulesoft.com
content_type: documentation
content_hash: 8ede5c7a7663d64bcbf61c7532ddd8140ca086cadbec6a63f1f5b29e5ceb3339
description: MuleSoft Documentation Site
release: 2.x
latest: true
---
---
product: Partner Manager
version: 2.x
is-latest-version: true
---

# Configuring Send Settings for Outbound X12 Messages

> For the full documentation index, see: https://docs.mulesoft.com/llms.txt

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

To configure a partner’s X12 send settings:

1.  In the sidebar, select **Partners**.

2.  Select the partner for whom you want to configure the settings.

3.  In the **Validation and acknowledgement settings** section’s **Send to <partner-name>** column,
    click **X12**.

4.  In the menu, select the setting to configure:

    - [General settings](#general-settings)

    - [Authorization settings](#authorization-settings)

    - [TA1 Acknowledgment settings](#ta1-ack-settings)

    - [Global control numbers](#global-control-numbers)

    - [Character set & separators](#character-set)

5.  Click **Save**.

The values you configure in the partner’s settings page are used by default for all X12 messages
going to that partner.

You can override the settings you configure at the partner level except for TA1 and control numbers.
You can override the message-flow-level settings by selecting the **Custom** option while creating
an outbound message flow.

> [!NOTE] Your changes can take up to five minutes to take effect on the runtime.

## General Settings

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

<table><colgroup><col> <col> <col></colgroup><thead><tr><th>Setting</th><th>Description</th><th>Default Value</th></tr></thead><tbody><tr><td><p>Usage indicator (ISA15)</p></td><td><div><div><p>Indicates if the X12 transaction sent is for testing, production, or information only.</p></div><div><p>Possible values include:</p></div><div><ul><li><p>I - Information</p></li><li><p>T - Test</p></li><li><p>P - Production</p></li></ul></div></div></td><td><div><div><ul><li><p><code>P - Production</code><br>For production environments</p></li><li><p><code>T - Test</code><br>For sandbox environments</p></li></ul></div></div></td></tr><tr><td><p>Responsible agency code (GS07)</p></td><td><div><div><p>Define the standards agency responsible for the standard in the GS segment.</p></div><div><p>Possible values include:</p></div><div><ul><li><p>T - Transportation Data Coordinating Committee (TDCC)</p></li><li><p>X - Accredited Standards Committee X12</p></li></ul></div></div></td><td><p><code>X</code></p></td></tr><tr><td><p>Enforce length limits</p></td><td><div><div><p>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.</p></div></div></td><td><p>Enabled</p></td></tr><tr><td><p>Enforce conditional relationship validations</p></td><td><p>If selected, any missing conditional data elements cause the generation of the X12 transaction to fail.</p></td><td><p>Enabled</p></td></tr><tr><td><p>Enforce code set validations</p></td><td><p>If selected, Partner Manager enforces X12 code set validations, as defined in the X12 schemas.</p></td><td><p>Disabled</p></td></tr></tbody></table>

## Authorization Settings

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

<table><colgroup><col> <col> <col></colgroup><thead><tr><th>Setting</th><th>Description</th><th>Default</th></tr></thead><tbody><tr><td><p>Authorization qualifier (ISA01)</p></td><td></td><td><p>None</p></td></tr><tr><td><p>Security qualifier (ISA03)</p></td><td></td><td><p>None</p></td></tr></tbody></table>

## TA1 Acknowledgment Settings

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

<table><colgroup><col> <col> <col></colgroup><thead><tr><th>Setting</th><th>Description</th><th>Default</th></tr></thead><tbody><tr><td><p>Expect TA1 for each transmission sent to &lt;partner&gt;</p></td><td><div><div><p>If selected, sets the value in ISA14 to 1 on the generated X12 payload, indicating that a technical acknowledgment (TA1) is required.</p></div></div></td><td><p>Disabled</p></td></tr><tr><td><p>Endpoint</p></td><td><div><div><p>When the option to expect a TA1 is selected, click <strong>Select</strong> to specify the <strong>Receive from &lt;partner&gt;</strong> endpoint. Partner Manager will receive the TA1 as an inbound transmission.</p></div></div></td><td><p>None</p></td></tr></tbody></table>

## 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 acknowledgments) that are sent to a partner.

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

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

> [!NOTE] Your changes can take up to five minutes to take effect on the runtime.

## Character Set & Separators

Use the following settings to set the character encoding and delimiters for the generated X12
payload:

<table><colgroup><col> <col> <col></colgroup><thead><tr><th>Setting</th><th>Description</th><th>Default Value</th></tr></thead><tbody><tr><td><p>Character set</p></td><td><div><div><p>Set of characters allowed in string data.</p></div></div></td><td><p>EXTENDED</p></td></tr><tr><td><p>Character encoding</p></td><td><div><div><p>Character encoding for messages.</p></div></div></td><td><p>UTF8</p></td></tr><tr><td><p>Segment terminator</p></td><td><div><div><p>Segment terminator character.</p></div></div></td><td><p><code>~</code></p></td></tr><tr><td><p>Data element separator</p></td><td><div><div><p>Data element separator character (can be a hex code).</p></div></div></td><td><p><code>*</code></p></td></tr><tr><td><p>Component element separator (ISA16)</p></td><td><div><div><p>Component element separator character (can be a hex code).</p></div></div></td><td><p><code>&gt;</code></p></td></tr><tr><td><p>Line ending between segments</p></td><td><div><div><p>Character to use for line endings between segments to improve the readability of the output message text. Possible values include:</p></div><div><ul><li><p>NONE</p><div><p>Generates the EDIFACT payload as a single line with segments separated by this character</p></div></li><li><p>CR</p><div><p>Carriage return</p></div></li><li><p>CRLF</p><div><p>Carriage return and line feed</p></div></li><li><p>LF</p><div><p>Line Feed</p></div></li></ul></div></div></td><td><p>CRLF</p></td></tr><tr><td><p>Use segment line ending in last line</p></td><td><p>If <code>Yes</code>, Partner Manager applies the segment line ending character to the last segment in the payload.</p></td><td><p>No</p></td></tr></tbody></table>

## See Also

- [Creating Outbound Message Flows](https://docs.mulesoft.com/partner-manager/latest/create-outbound-message-flow)

- [Creating Partners](https://docs.mulesoft.com/partner-manager/latest/create-partner)

- [Modify Partner Settings](https://docs.mulesoft.com/partner-manager/latest/modify-partner-settings)