214 Transportation Carrier Shipment Status Message (007040)

This is the standard X12 007040 spec, with 4 loops and 24 segment positions, as OpenEDI JSON, an ediFabric C# template and an ediFabric Native model. To change it for a trading partner, customize it in the EDI Spec Builder.

Loading the spec…
The spec as an OpenAPI 3 schema with x-openedi-* extensions, for ediFabric Native, ediFabric Cloud and the EDI Spec Builder. Download OpenEDI (57 KB) Generate classes
The ediFabric .NET template, class TS214. It needs the common segments, composites and codes of X12 007040, one download for every transaction in the version. Download C# (1 KB) Common files (233 KB)
The intermediary model ediFabric Native loads with set_map. Download Native (44 KB)

Use the 214 spec in your code

ediFabric .NET

Add the C# template and its common files to your project, or reference the template NuGet package, and read 214 files into TS214 objects. See ediFabric .NET.

ediFabric Native

Map version 007040 to the Native model with set_map, then parse 214 files to JSON from Python, Java, C or C#. See Convert between EDI and JSON.

OpenEDI

Select Customize in Spec Builder to copy the spec under your own name, change it for your partner, and parse files against it in EdiNation, ediFabric Native or ediFabric Cloud. Read about OpenEDI.

Generate 214 classes in Python, Java, Node.js, Go, Rust or C

ediFabric Native returns each 214 as JSON, with the property names of the OpenEDI schema. To work with that JSON as typed objects, generate classes from the OpenEDI file in your language and deserialize the JSON into TS214. Serialize the objects back to JSON to build EDI with ediFabric Native. The classes keep the loops, segments, lengths and code lists, but not the EDI data formats, so validate files with ediFabric Native. Read more in Generate a class from OpenEDI.

Python: datamodel-code-generator. Node.js: openapi-typescript. Java, Go, Rust and C: OpenAPI Generator.

For a sample file, the same data as JSON, and code to parse, validate and generate the 214, see the 214 transaction guide.

214 structure

Loops and segments of the standard 214, with their usage and maximum repeats.

IDNameUsageMax use
STTransaction Set HeaderMandatory1
B10B10Mandatory1
MS3MS3Optional12
Loop LXLXMandatory999999
LXLXMandatory1
L11L11Optional999
MANMANOptional9999
Q7Q7Optional10
K1K1Optional10
AT5AT5Optional10
AT8AT8Optional10
Loop AT7AT7Mandatory10
AT7AT7Mandatory1
MS1MS1Optional1
MS2MS2Optional2
K1K1Optional1
M7M7Optional1
Loop N1N1Optional5
N1N1Mandatory1
N2N2Optional1
N3N3Optional2
N4N4Optional1
G62G62Optional1
L11L11Optional10
Loop OIDOIDOptional999999
OIDOIDMandatory1
SDQSDQOptional10
SETransaction Set TrailerMandatory1