210 Motor Carrier Freight Details and Invoice (007040)

This is the standard X12 007040 spec, with 12 loops and 59 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 (103 KB) Generate classes
The ediFabric .NET template, class TS210. 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 (84 KB)

Use the 210 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 210 files into TS210 objects. See ediFabric .NET.

ediFabric Native

Map version 007040 to the Native model with set_map, then parse 210 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 210 classes in Python, Java, Node.js, Go, Rust or C

ediFabric Native returns each 210 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 TS210. 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 210, see the 210 transaction guide.

210 structure

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

IDNameUsageMax use
STTransaction Set HeaderMandatory1
B3B3Mandatory1
C2C2Optional1
C3C3Optional1
ITDITDOptional1
L11L11Optional300
G62G62Optional6
R3R3Optional12
H3H3Optional6
K1K1Optional10
Loop N1N1Optional10
N1N1Mandatory1
N2N2Optional1
N3N3Optional2
N4N4Optional1
L11L11Optional5
Loop N7N7Optional10
N7N7Mandatory1
M7M7Optional2
Loop OIDOIDOptional999999
OIDOIDMandatory1
SDQSDQOptional10
Loop S5S5Optional999
S5S5Mandatory1
L11L11Optional10
G62G62Optional10
H3H3Optional6
Loop OIDOIDOptional999999
OIDOIDMandatory1
SDQSDQOptional10
Loop N1N1Optional2
N1N1Mandatory1
N2N2Optional1
N3N3Optional2
N4N4Optional1
L11L11Optional5
Loop N7N7Optional10
N7N7Mandatory1
M7M7Optional2
Loop LXLXOptional99999
LXLXMandatory1
L11L11Optional20
L5L5Optional30
H1H1Optional3
H2H2Optional2
L0L0Optional10
L1L12Optional50
L4L4Optional10
L7L7Optional10
K1K1Optional10
Loop OIDOIDOptional999999
OIDOIDMandatory1
SDQSDQOptional10
Loop N1N1Optional999999
N1N1Mandatory1
N2N2Optional1
N3N3Optional2
N4N4Optional1
L11L11Optional10
Loop CD3CD3Optional999999
CD3CD3Mandatory1
L11L11Optional20
H6H6Optional10
L9L9Optional50
PODPODOptional1
G62G62Optional1
Loop OIDOIDOptional999999
OIDOIDMandatory1
SDQSDQOptional10
L3L3Optional1
SETransaction Set TrailerMandatory1