240 Motor Carrier Package Status (006030)

This is the standard X12 006030 spec, with 8 loops and 28 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 (51 KB) Generate classes
The ediFabric .NET template, class TS240. It needs the common segments, composites and codes of X12 006030, one download for every transaction in the version. Download C# (1 KB) Common files (274 KB)
The intermediary model ediFabric Native loads with set_map. Download Native (40 KB)

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

ediFabric Native

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

ediFabric Native returns each 240 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 TS240. 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.

240 structure

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

IDNameUsageMax use
STTransaction Set HeaderOptional1
BGNBeginning SegmentMandatory1
Loop N1Party IdentificationOptional>1
N1Party IdentificationMandatory1
N2Additional Name InformationOptional2
N3Party LocationOptional2
N4Geographic LocationOptional1
Loop LXTransaction Set Line NumberMandatory>1
LXTransaction Set Line NumberMandatory1
Loop N1Party IdentificationOptional1
N1Party IdentificationMandatory1
N2Additional Name InformationOptional2
N3Party LocationOptional2
N4Geographic LocationOptional1
NM1Individual or Organizational NameOptional1
NTENote/Special InstructionOptional1
Loop EFIElectronic Format IdentificationOptional1
EFIElectronic Format IdentificationMandatory1
BINBinary Data SegmentMandatory1
Loop L11Business Instructions and Reference NumberMandatory>1
L11Business Instructions and Reference NumberMandatory1
MS2Equipment or Container Owner and TypeOptional>1
Loop LSLoop HeaderOptional1
LSLoop HeaderMandatory1
Loop MANMarks and Numbers InformationOptional>1
MANMarks and Numbers InformationMandatory1
L11Business Instructions and Reference NumberOptional>1
AT7Shipment Status DetailsOptional>1
CD3Carton (Package) DetailOptional>1
NM1Individual or Organizational NameOptional1
Q7Lading Exception StatusOptional>1
LELoop TrailerMandatory1
Loop EFIElectronic Format IdentificationOptional1
EFIElectronic Format IdentificationMandatory1
BINBinary Data SegmentMandatory1
SETransaction Set TrailerOptional1