423 Rail Industrial Switch List (006030)

This is the standard X12 006030 spec, with 5 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 (98 KB) Generate classes
The ediFabric .NET template, class TS423. 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 (75 KB)

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

ediFabric Native

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

ediFabric Native returns each 423 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 TS423. 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.

423 structure

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

IDNameUsageMax use
STTransaction Set HeaderOptional1
BGNBeginning SegmentMandatory1
DTMDate/Time ReferenceOptional3
LQIndustry Code IdentificationOptional1
QTYQuantity InformationOptional3
Loop N1Party IdentificationMandatory5
N1Party IdentificationMandatory1
N2Additional Name InformationOptional1
N3Party LocationOptional1
N4Geographic LocationOptional1
PERAdministrative Communications ContactOptional1
Loop LXTransaction Set Line NumberOptional150
LXTransaction Set Line NumberMandatory1
XDPlacement/Pull DataOptional1
Loop N7Equipment DetailsOptional500
N7Equipment DetailsMandatory1
YNQYes/No QuestionOptional10
DTMDate/Time ReferenceOptional10
XDPlacement/Pull DataOptional5
R2Route InformationOptional1
N1Party IdentificationOptional1
N4Geographic LocationOptional1
L5Description, Marks and NumbersOptional5
D9Destination StationOptional1
F9Origin StationOptional1
PERAdministrative Communications ContactOptional2
LH2Hazardous Classification InformationOptional2
LH6Hazardous CertificationOptional6
QTYQuantity InformationOptional2
N9Extended Reference InformationOptional10
Loop LH1Hazardous Identification InformationOptional1000
LH1Hazardous Identification InformationMandatory1
LH2Hazardous Classification InformationOptional4
LH3Hazardous Material Shipping Name InformationOptional10
LFHFree-form Hazardous Material InformationOptional20
LEPEPA Required DataOptional3
LH4Canadian Dangerous RequirementsOptional4
LHTTransborder Hazardous RequirementsOptional3
LHRHazardous Material Identifying Reference NumbersOptional5
PERAdministrative Communications ContactOptional5
Loop N1Party IdentificationOptional10
N1Party IdentificationMandatory1
N3Party LocationOptional2
N4Geographic LocationOptional1
PERAdministrative Communications ContactOptional2
SETransaction Set TrailerOptional1