301 Confirmation (Ocean) (005050)

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

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

ediFabric Native

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

ediFabric Native returns each 301 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 TS301. 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.

301 structure

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

IDNameUsageMax use
STTransaction Set HeaderOptional1
B1Beginning Segment for Booking or Pickup/DeliveryMandatory1
G61ContactOptional3
Y6AuthenticationOptional2
Y3Space ConfirmationMandatory1
Loop Y4Container ReleaseOptional10
Y4Container ReleaseMandatory1
W09Equipment and TemperatureOptional1
N9Extended Reference InformationOptional100
R2ARoute Information with PreferenceOptional25
Loop N1Party IdentificationOptional4
N1Party IdentificationMandatory1
N2Additional Name InformationOptional1
N3Party LocationOptional2
N4Geographic LocationOptional1
G61ContactOptional3
Loop R4Port or TerminalMandatory20
R4Port or TerminalMandatory1
DTMDate/Time ReferenceOptional15
W09Equipment and TemperatureOptional1
H3Special Handling InstructionsOptional6
EAEquipment AttributesOptional5
Loop LXTransaction Set Line NumberMandatory999
LXTransaction Set Line NumberMandatory1
N7Equipment DetailsOptional1
W09Equipment and TemperatureOptional1
K1RemarksOptional10
L0Line Item - Quantity and WeightOptional1
L5Description, Marks and NumbersOptional1
L4MeasurementOptional1
L1Rate and ChargesOptional1
Loop H1Hazardous MaterialOptional10
H1Hazardous MaterialMandatory1
H2Additional Hazardous Material DescriptionOptional10
Loop LH1Hazardous Identification InformationOptional100
LH1Hazardous Identification InformationMandatory1
LH2Hazardous Classification InformationOptional4
LH3Hazardous Material Shipping Name InformationOptional10
LFHFree-form Hazardous Material InformationOptional25
LEPEPA Required DataOptional3
LH4Canadian Dangerous RequirementsOptional1
LHTTransborder Hazardous RequirementsOptional3
LHRHazardous Material Identifying Reference NumbersOptional5
PERAdministrative Communications ContactOptional5
V1Vessel IdentificationOptional2
V9Event DetailOptional10
SETransaction Set TrailerOptional1