433 Railroad Reciprocal Switch File (003050)

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

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

ediFabric Native

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

ediFabric Native returns each 433 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 TS433. 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.

433 structure

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

IDNameUsageMax use
STTransaction Set HeaderOptional1
BGNBeginning SegmentMandatory1
N1NameMandatory1
N2Additional Name InformationOptional2
N3Address InformationOptional1
N4Geographic LocationOptional1
Loop SMSStation Codes SegmentMandatory4
SMSStation Codes SegmentMandatory1
SMRCross ReferenceMandatory1
N4Geographic LocationOptional1
PIPrice Authority IdentificationOptional1
Loop CDShipment ConditionsOptional150
CDShipment ConditionsMandatory1
SIDStandard Transportation Commodity Code IdentificationOptional2
BLRTransportation Carrier IdentificationOptional20
N4Geographic LocationOptional50
SETransaction Set TrailerOptional1