Skip to Content

EDI IDs in Jitterbit EDI

Trading partners in Jitterbit EDI identify each other using a Partner ID (also referred to as an ISA ID in the user interface) whose format depends on the EDI standard in use:

EDI Standard Format Total length
X12 Two fixed characters (0–9 or A–Z) + hyphen + 1–15 characters (0–9 or A–Z) 4–18 characters
EDIFACT 1–4 characters (0–9 or A–Z) + hyphen + 1–35 characters (0–9 or A–Z) 3–40 characters
TRADACOMS Exactly 12 alphanumeric characters 12 characters

For X12 and EDIFACT, the prefix before the hyphen is the EDI qualifier code. The EDI standard for a partner is determined by the first EDIXml workflow associated with that partner. Format validation is skipped if the partner has no EDIXml workflows.

Note

Your own EDI ID doesn't follow the table above; it uses one format regardless of EDI standard: a qualifier of up to 4 alphanumeric characters, plus a required ID of 1–35 alphanumeric characters. The qualifier is mandatory (1–4 characters) the first time you set up an EDI ID for a new environment, and optional (0–4 characters) when adding additional EDI IDs afterward via Preferred ID (ISA ID's).

Note

When creating a new trading partner, only the uniqueness of the ID is validated. Format validation applies only when adding IDs to an existing partner that has at least one EDIXml workflow.

Important notes when choosing your EDI ID

  • Don't use your authentic EDI ID on test or QA environments. Use it only when setting up your production EDI environment.

  • Each ID must be unique across all environments where Jitterbit EDI is enabled. Attempting to add an ID that is already assigned to another trading partner fails. Work with your trading partner to ensure your ID is unique and that proper communication can be established.

  • Attempting to add a duplicate Preferred ID (whether it's already assigned to the same trading partner or to another one in the same environment) is also rejected. For the exact error messages and how to resolve them, see EDI ID or Preferred ID addition fails: ID already in use.

Set up an EDI ID

The first time you add a trading partner to an environment, the Generating Your EDI ID dialog opens for you to set up an EDI ID for your company.

Read the contents of the dialog carefully, then enter values for the following fields:

  • Qualifier Code: Enter a qualifier, 1–4 alphanumeric characters (0–9 or A–Z). For example, AAAA. See the EDI qualifier codes reference for commonly used values.

  • EDI ID: Enter your company's EDI (ISA) identifier, 1–35 alphanumeric characters (0–9 or A–Z). For example, ABCD12T, where a trailing test-only character distinguishes a test environment ID from your production ID.

Click Continue to save the values and continue to add your first partner.

Tip

If you need to use a different EDI ID, use the Preferred ID (ISA ID's) tab to add additional IDs, assign any as the new ID, and remove previous ones. This is useful if there are errors with the initial ID entry or if an alternative ID is required.

Preferred ID (ISA ID's)

Preferred IDs are your default IDs used to route EDI transactions to and from your trading partners.

There are two sets of preferred IDs:

  • Partner ID: The ID that trading partners use with all their vendors.

  • EDI ID: Your internal ID that your trading partner uses to identify you on their network.

Find preferred IDs

To find the preferred IDs for a partner, follow these steps:

  1. Select EDI > Trading Partners.

  2. In the Trading partners panel, select a partner.

  3. In the configuration drawer, select the EDI settings tab.

  4. Expand the Preferred ID (ISA ID's) section:

    EDI Settings

Assign preferred IDs

Once you add a trading partner and create your first workflow, the default IDs (partner ID and EDI ID) are automatically assigned. You can re-assign either of the IDs by clicking the Assign icon for any other assigned ID.

The system uses the assigned IDs in outbound EDI transactions when processing them, unless you override them.

Delete or replace an ID

During account setup, an EDI ID is created. While it's best practice to avoid using your production EDI ID in test or QA environments (thereby reserving it for production), this might not always be possible.

If you need a different EDI ID, there are two options:

  • If you want a different ID (like a test ID), create and assign the new EDI ID, delete the original, and then reuse the original ID in another environment.

  • Use a new environment within your current organization, create a new EDI ID, then delete the original environment.

Use preferred IDs in transactions

Inbound transactions

All preferred IDs in your list are valid and can be used for inbound transactions whether they are assigned or not. This is important for testing, and for when trading partners or your internal systems have different subsidiaries or companies that you want to route data to.

Outbound transactions

When sending outbound transactions to your trading partners, the assigned preferred IDs are used within the transformation as the default values in your outbound EDI transactions. However, you have the option to override the assigned preferred IDs with any other preferred ID. This may be necessary if the trading partner or your internal IDs need to be changed to align with a subsidiary or another entity within your or your trading partner's business.

Override a preferred ID in outbound transactions

To override the IDs, you must set the following values within the request transformation used as input for an EDI for Cloud v2 Send Document activity in Studio:

ID Qualifier ISA ID
EDI ID ISA05_ID_Qualifier ISA06_Sender_ID
Partner ID ISA07_ID_Qualifier ISA08_Receiver_ID

Tip

For outbound transactions, the sender and receiver IDs are reversed compared to inbound transactions.

For the position of these elements within the raw ISA segment, see the interchange control header/trailer reference.

Example

The two images below show a transformation, and the contents of the transformation showing the overridden IDs:

Example ISA outbound fulfillment

Example transformation expanded

Important

Values set in a transformation are used for all outbound transactions within the workflow.

Troubleshooting

For related troubleshooting, see the following in the EDI troubleshooting guide: