Transportation

Many of the transportation industry’s business activities rely on X12's work, including air, marine, rail, motor freight, customs, logistics and multi-modal.

There are many transaction sets used extensively in the transportation industry including: Vehicle Shipping Order (120), Motor Carrier Freight Details and Invoice (210), Motor Carrier Bill of Lading (211), Transportation Carrier Shipment Status Message (214), Shipping Instructions (304), Rail Carrier Shipment Information (404)

Subcommittee: X12I

Available Resources

  • Design Rules & Guidelines
  • Control Standards
  • EDI Standard Transaction Sets
  • Reference Models
  • EDI Standard Table Data
  • EDI Standard XSDs

Design Rules & Guidelines

The Design Rules and Guidelines assist standards developers of X12-syntax-based messages achieve consistent and technically appropriate transaction sets that meet the needs of the user community.

Sample - Design Rules and Guidelines

Control Standards

Control standards define all the basic syntax aspects of the X12 EDI Standard. Included are the Interchange, Application, Interconnect Mailbag, and Security Control Structures, as well as the Semantic Impact for implementation of EDI structures.

Sample - Interchange Control Structure

Transaction Sets

An X12 transaction set is a semantically meaningful unit of information exchanged between trading partners. A transaction set may consist of a transaction set header segment, security header segments, assurance header segments, one or more data segments and loop control segments in a specified order, one transaction security value segment for each assurance header present, one transaction security trailer segment for each security header segment present, and a transaction set trailer segment.

Sample - 856 Ship Notice/Manifest Transaction Set

Reference Models

Reference models describe related business processes, computer applications, or business data flows, and are intended to assist in system development. Examples include control structures and standards for handling acknowledgments, and how to create XML element names from X12 implementation guides.

Sample - Acknowledgment Reference Model

Table Data

Table data files are inert raw data intended to be imported into existing applications by software developers or implementers. It is not intended to replace Implementation Guides, X12 Technical Reports, or the X12 Standard, but may be useful in saving considerable time compared to manually building and maintaining protocol to work with EDI toolsets especially if you intend to handle several transaction sets and versions.

Sample - EDI Standard Table Data readme.txt

XSDs

X12 XSDs are mechanically generated from the same database as the implementation guides and EDI standard. Both the TR3 and EDI schemas are W3C-compliant XML Schema Definition (XSD) files. Using X12's auto-generated XSDs saves considerable time compared to manually building and maintaining XSD.

Sample - 008030 Ship Notice/Manifest (856) EDI Standard Transaction Set XSD Schema