Skip to content
X12 EDI

AT&T Inc. X12 754 Routing Instructions

Plan X12 754 Routing Instructions for AT&T Inc. / AT&T (New ISA ID: 108024050B2B). Connect document identifiers to your business records, test exception handling and track each exchange to completion.

Segments
16
Loops
2
X12 754
Partner references ↗

Implementation guide

AT&T Inc. / AT&T (New ISA ID: 108024050B2B): 754 mapping and validation

X12 754 Routing Instructions is used when routing details are issued in response to a shipment need. Preserve routing reference, order and shipment so the routing instruction in your business system stays connected to the original document.

This document is listed for AT&T Inc. / AT&T (New ISA ID: 108024050B2B). Confirm the version, required fields and responses that apply to your account.

Map records and test the business result
Document or decisionRecord and matching IDsWhat to test
Match the business record routing instruction

routing reference, order and shipment

  • Define which combination of routing reference, order and shipment identifies one business record, its lines and any later revision.
Update the receiving system Processing the routing instruction

ID assigned by the receiving system and processing result

  • Match instructions to the correct open routing request.
  • Test a carrier reassignment after warehouse planning and require the shipping record to be updated.
Check the processing result Processing status for the routing instruction

Original document reference and matching response

  • Reconcile the routing instruction with the source after a timeout before sending it again. A lost response can occur after the destination has already processed the document.

The document reference includes 16 segments. Use the segment reference below to locate the relevant parts of the message. Check required fields and repetition limits in the partner guide.

How the related documents differ

Each message represents a different business event. Use shared references to connect the records while tracking each message’s outcome separately.

Implementation steps

  1. Choose the starting event and owner

    Decide which application acts when routing details are issued in response to a shipment need. Name the operational owner of the routing instruction and the team that resolves rejected or ambiguous messages.

  2. Keep record IDs connected

    Map routing reference, order and shipment. Confirm qualifiers, code lists, units and date/time meaning against the agreed X12 version and AT&T Inc. guide. Preserve the source reference alongside any new destination identifier.

  3. Test failures before launch

    Run the failure cases in the mapping table against realistic routing instruction data. Check how the receiving system reports a rejection and how your team corrects it without creating a duplicate.

  4. Track every document to completion

    Record transport delivery and document validation separately from successful routing instruction processing. Give unresolved errors an owner and check the receiving system before approving retries.

Go-live checklist

  • An approved 754 sample and the agreed version and partner guide are available.
  • The mapping tests pass with realistic routing instruction data.
  • Each submitted document can be traced through delivery, validation and processing in the receiving system.
  • Your team knows how to investigate and recover a rejected or timed-out routing instruction without processing it twice.

Transaction context

Where 754 Routing Instructions fits on AT&T (New ISA ID: 108024050B2B)

AT&T Inc. channels
2 of 2

2 of AT&T Inc.'s 2 channels list 754

Trading partners
5

partner references list 754

Channels
6

channel entries list 754

Document structure

X12 754 Routing Instructions at the element level

The X12 754 reference contains 23 segment entries and 64 data elements; 40 are marked mandatory in this reference. Use the version and partner guide agreed for your account to confirm required fields.

Segments
23
Data elements
64
Mandatory elements
40
Segments with elements marked mandatory in this reference
Segment Elements Mandatory
BGN 4 3
N1 2 1
N2 1 1
N3 1 1
LX 1 1
BLR 1 1
SMD 2 2
MSI 2 1
Key identifiers in 754
  • Transaction Set Purpose Code
  • Reference Identification
  • Date
  • Entity Identifier Code
  • Name
  • Address Information
  • Assigned Number
  • Standard Carrier Alpha Code
Segment reference — 16 segments 2 loops · X12 754 Routing Instructions
ISA Interchange Control Header 16 elements

To start and identify an interchange of zero or more functional groups and interchange-related control segments

GS Functional Group Header 8 elements

To indicate the beginning of a functional group and to provide control information

ST Transaction Set Header 2 elements

To indicate the start of a transaction set and to assign a control number

BGN Beginning Segment 4 elements

To indicate the beginning of a transaction set

N1 Loop Repeat: 5
N1 Party Identification 2 elements

To identify a party by type of organization, name, and code

N2 Additional Name Information 1 element

To specify additional names

N3 Party Location 1 element

To specify the location of the named party

N4 Geographic Location 4 elements

To specify the geographic place of the named party

LX Loop Repeat: 9,999
LX Transaction Set Line Number 1 element

To reference a line number in a transaction set

L11 Business Instructions and Reference Number 3 elements

To specify instructions in this business relationship or a reference number

BLR Transportation Carrier Identification 1 element

To transmit the identifying SCAC code and effective date and time for the data in the transaction set

SMD Consolidated Shipment Manifest Data 2 elements

To transmit shipment manifest data

OID Order Information Detail 5 elements

To specify order information detail

SE Transaction Set Trailer 2 elements

To indicate the end of the transaction set and provide the count of the transmitted segments (including the beginning (ST) and ending (SE) segments)

G62 Date/Time 4 elements

To specify pertinent dates and times

MSI Multi-stop Shipment Information 2 elements

To specify multi-stop shipment information

Related references

754 Routing Instructions on other AT&T Inc. channels

Compare the listed channel references and confirm their current implementation guides.

Showing 1 of 1 references

Browse the full directory

Related references

Other transactions in AT&T (New ISA ID: 108024050B2B)

Other EDI documents listed on this channel.

AT&T Inc. / AT&T (New ISA ID: 108024050B2B) EDI 754 questions

Common questions about 754 Routing Instructions on the AT&T (New ISA ID: 108024050B2B) channel.

What is X12 754 Routing Instructions used for?

754 is used when routing details are issued in response to a shipment need. It carries information for the routing instruction. Match it to your business system using routing reference, order and shipment.

Is 754 required for AT&T Inc. / AT&T (New ISA ID: 108024050B2B)?

754 is listed for AT&T Inc. / AT&T (New ISA ID: 108024050B2B). Confirm the required version and direction for your business unit and account with the partner.

What should I map for X12 754?

Start with routing reference, order and shipment and the target routing instruction. Define duplicate detection, allowed updates and response correlation before mapping individual fields. Use the partner guide to check required fields and their formats.

How should I test 754 error handling?

Match instructions to the correct open routing request. Test a carrier reassignment after warehouse planning and require the shipping record to be updated. Also test a lost response after destination processing so that a retry cannot create an unintended duplicate or repeated adjustment.

How does 754 relate to other EDI messages?

X12 856 Ship Notice Manifest is a related document also listed on AT&T (New ISA ID: 108024050B2B). Match these documents through their order, shipment or invoice references. Agree which response marks each business step as complete.

Connect AT&T Inc. EDI to your business systems

See how Stacksync can fit your enterprise EDI workflow. Bring one partner guide and a sample exchange to plan the system mapping, exception handling and production rollout.