286 Commercial Vehicle Credentials (005010)

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

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

ediFabric Native

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

ediFabric Native returns each 286 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 TS286. 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.

286 structure

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

IDNameUsageMax use
STTransaction Set HeaderOptional1
BGNBeginning SegmentMandatory1
CURCurrencyOptional1
Loop NM1Individual or Organizational NameOptional>1
NM1Individual or Organizational NameMandatory1
N2Additional Name InformationOptional2
N3Party LocationOptional2
N4Geographic LocationOptional1
N9Extended Reference InformationOptional>1
PERAdministrative Communications ContactOptional>1
DTMDate/Time ReferenceOptional>1
Loop SPISpecification IdentifierMandatory>1
SPISpecification IdentifierMandatory1
Loop HLHierarchical LevelMandatory>1
HLHierarchical LevelMandatory1
Loop LMCode Source InformationMandatory>1
LMCode Source InformationMandatory1
Loop LQIndustry Code IdentificationMandatory>1
LQIndustry Code IdentificationMandatory1
N9Extended Reference InformationOptional>1
DTMDate/Time ReferenceOptional>1
MEAMeasurementsOptional>1
QTYQuantity InformationOptional>1
PDLPayment DetailsOptional1
AMTMonetary Amount InformationOptional>1
YNQYes/No QuestionOptional>1
VEHVehicle InformationOptional>1
DVIDynamic Vehicle InformationOptional>1
TC2CommodityOptional>1
N12Equipment EnvironmentOptional>1
H1Hazardous MaterialOptional>1
MSGMessage TextOptional>1
Loop NM1Individual or Organizational NameOptional>1
NM1Individual or Organizational NameMandatory1
N2Additional Name InformationOptional2
N3Party LocationOptional2
N4Geographic LocationOptional1
N9Extended Reference InformationOptional>1
PERAdministrative Communications ContactOptional>1
EMSEmployment PositionOptional1
DTMDate/Time ReferenceOptional>1
MEAMeasurementsOptional>1
QTYQuantity InformationOptional>1
YNQYes/No QuestionOptional>1
TD5Carrier Details (Routing Sequence/Transit Time)Optional>1
SETransaction Set TrailerOptional1