108 Response to a Motor Carrier Rate Proposal (005020)

This is the standard X12 005020 spec, with 2 loops and 12 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 (33 KB) Generate classes
The ediFabric .NET template, class TS108. It needs the common segments, composites and codes of X12 005020, one download for every transaction in the version. Download C# (1 KB) Common files (267 KB)
The intermediary model ediFabric Native loads with set_map. Download Native (25 KB)

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

ediFabric Native

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

ediFabric Native returns each 108 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 TS108. 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.

108 structure

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

IDNameUsageMax use
STTransaction Set HeaderOptional1
BGNBeginning SegmentMandatory1
BLRTransportation Carrier IdentificationMandatory1
G62Date/TimeOptional10
Loop N1Party IdentificationMandatory10
N1Party IdentificationMandatory1
N2Additional Name InformationOptional1
N3Party LocationOptional2
N4Geographic LocationOptional1
PERAdministrative Communications ContactOptional5
Loop CA1Rate Request IdentifierMandatory99999
CA1Rate Request IdentifierMandatory1
LC1Lane CommitmentsMandatory1
SETransaction Set TrailerOptional1