213 Motor Carrier Shipment Status Inquiry (005040)

This is the standard X12 005040 spec, with 1 loops and 13 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 (45 KB) Generate classes

The ediFabric .NET template, class TS213. It needs the common segments, composites and codes of X12 005040, one download for every transaction in the version. Download C# (1 KB) Common files (269 KB)

The intermediary model ediFabric Native loads with set_map. Download Native (32 KB)

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

ediFabric Native

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

ediFabric Native returns each 213 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 TS213. 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.

213 structure

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

ID	Name	Usage	Max use
ST	Transaction Set Header	Optional	1
B11	Beginning Segment for Shipment Status Inquiry	Mandatory	1
C3	Currency Identifier	Optional	1
REF	Reference Information	Optional	10
L10	Weight Information	Optional	5
Loop N1	Party Identification	Optional	5
N1	Party Identification	Mandatory	1
N2	Additional Name Information	Optional	1
N3	Party Location	Optional	2
N4	Geographic Location	Optional	1
G61	Contact	Optional	2
REF	Reference Information	Optional	10
K2	Administrative Message	Optional	2
SE	Transaction Set Trailer	Optional	1