---
schema_version: "1"
id: ab01ef05e7a5089ccebe4a1cf2e3ffe0cdeaf462668523635e75a58d66a06526
title: X12 EDI Connector 2.17 Control Numbers
collection: mulesoft
version: current
locale: en-us
portal_url: https://docs.salesforce.com/mulesoft/current/en-us/x12-edi-connector/2.17/x12-edi-connector-control-numbers.md
canonical_url: https://docs.mulesoft.com/x12-edi-connector/2.17/x12-edi-connector-control-numbers
source_site: docs.mulesoft.com
content_type: documentation
content_hash: d51f4b69bb1f84a5318fcb6a907c4eaa444260db2eea761499221736fc141f07
description: MuleSoft Documentation Site
release: "2.17"
latest: false
---
---
product: X12 EDI Connector
version: 2.17
---

# X12 EDI Connector 2.17 Control Numbers

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

Using the Write operation in the Anypoint Connector for X12 EDI Connector (X12 EDI Connector), you
can generate control numbers on the generated X12 payload by:

- Managing global control numbers through control number keys

- Managing identifier combination control numbers

- Using your own control number

## Manage Global Control Numbers Through Control Number Keys

If your organization or your trading partner have must maintain unique interchange, group, or
transaction set control numbers across different identifier combinations and document types:

- Set the configuration `Use supplied values` to `false`.

- Leverage the control number key configurations (at the configuration level or operation level) to
  set a key unique to the partner.

  By default, the control number key configurations pass dynamically at the operation level. You can
  then use this group control number key across different identifiers and transaction types for the
  same partner.

![X12 EDI Connector Control Numbers](/mulesoft/current/en-us/x12-edi-connector/2.17/_images/X12-edi-control-number.jpg)

## Manage Identifier Combination Control Numbers

If you want the connector to automatically maintain control number sequencing based on the
sender/receiver identifiers and you do not require global control numbers at a partner level, then
set the Write configuration `Use supplied values` to `false`. When no value passes into the optional
interchange, group, or transaction number key configurations, the sender/receiver identifier
combination is the default.

## Use Your Own Control Number

If you must generate the control numbers and use them on the EDI payload, you can set the parameter
`Use supplied values` to `true`, and map the control number on the payload in the DataWeave map.