424 Rail Carrier Services Settlement (006030)

This is the standard X12 006030 spec, with 4 loops and 22 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 (96 KB) Generate classes
The ediFabric .NET template, class TS424. 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 (71 KB)

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

ediFabric Native

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

ediFabric Native returns each 424 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 TS424. 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.

424 structure

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

IDNameUsageMax use
STTransaction Set HeaderOptional1
BSWBeginning Segment for Carrier?s Services SettlementMandatory1
CURCurrencyMandatory1
Loop N1Party IdentificationOptional5
N1Party IdentificationMandatory1
N2Additional Name InformationOptional1
N3Party LocationOptional1
N4Geographic LocationOptional1
PERAdministrative Communications ContactOptional2
Loop CICarrier Interchange AgreementOptional20
CICarrier Interchange AgreementMandatory1
DTMDate/Time ReferenceOptional1
AMTMonetary Amount InformationOptional1
MEAMeasurementsOptional2
Loop SWCSwitching ConditionsOptional999
SWCSwitching ConditionsMandatory1
Loop EDEquipment DescriptionOptional9999
EDEquipment DescriptionMandatory1
DTMDate/Time ReferenceOptional5
SWDSwitching DetailsOptional1
SWRSwitching RatesOptional2
NM1Individual or Organizational NameOptional1
F9Origin StationOptional1
D9Destination StationOptional1
NTENote/Special InstructionOptional1
SETransaction Set TrailerOptional1