216 Motor Carrier Shipment Pickup Notification (005010)

This is the standard X12 005010 spec, with 1 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 (30 KB) Generate classes
The ediFabric .NET template, class TS216. 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 (22 KB)

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

ediFabric Native

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

ediFabric Native returns each 216 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 TS216. 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.

216 structure

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

IDNameUsageMax use
STTransaction Set HeaderOptional1
PUNBeginning Segment for Motor Carrier Pickup NotificationMandatory1
G61ContactOptional1
TEMPickup TotalsOptional1
PRFPurchase Order ReferenceOptional>1
AT5Bill of Lading Handling RequirementsOptional10
K2Administrative MessageOptional1
Loop N1Party IdentificationMandatory2
N1Party IdentificationMandatory1
N2Additional Name InformationOptional1
N3Party LocationOptional2
N4Geographic LocationOptional1
SETransaction Set TrailerOptional1