212 Motor Carrier Delivery Trailer Manifest (004020)

This is the standard X12 004020 spec, with 6 loops and 34 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 (50 KB) Generate classes
The ediFabric .NET template, class TS212. It needs the common segments, composites and codes of X12 004020, one download for every transaction in the version. Download C# (1 KB) Common files (254 KB)
The intermediary model ediFabric Native loads with set_map. Download Native (39 KB)

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

ediFabric Native

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

ediFabric Native returns each 212 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 TS212. 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.

212 structure

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

IDNameUsageMax use
STTransaction Set HeaderOptional1
ATABeginning Segment for Motor Carrier Delivery Trailer ManifestMandatory1
B2ASet PurposeMandatory1
L11Business Instructions and Reference NumberOptional300
Loop N1NameOptional1
N1NameMandatory1
N2Additional Name InformationOptional1
N3Address InformationOptional2
N4Geographic LocationOptional1
G61ContactOptional1
G62Date/TimeOptional1
L11Business Instructions and Reference NumberOptional10
Loop AT7Shipment Status DetailsMandatory1
AT7Shipment Status DetailsMandatory1
G62Date/TimeOptional5
MS1Equipment, Shipment, or Real Property LocationOptional1
Loop MS2Equipment or Container Owner and TypeOptional1
MS2Equipment or Container Owner and TypeMandatory1
M7Seal NumbersOptional1
AT9Trailer or Container Dimension and WeightOptional1
Loop LXAssigned NumberOptional9999
LXAssigned NumberMandatory1
L11Business Instructions and Reference NumberOptional10
AT7Shipment Status DetailsOptional1
BLRTransportation Carrier IdentificationOptional1
MANMarks and NumbersOptional9999
AT8Shipment Weight, Packaging and Quantity DataOptional1
Q7Lading Exception CodeOptional10
G62Date/TimeOptional5
TSDTrailer Shipment DetailsOptional1
Loop OIDOrder Identification DetailOptional999999
OIDOrder Identification DetailMandatory1
SDQDestination QuantityOptional9999
Loop N1NameOptional1
N1NameMandatory1
N2Additional Name InformationOptional1
N3Address InformationOptional2
N4Geographic LocationOptional1
L11Business Instructions and Reference NumberOptional5
SETransaction Set TrailerOptional1