620 Excavation Communication (004040)

This is the standard X12 004040 spec, with 4 loops and 23 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 (73 KB) Generate classes
The ediFabric .NET template, class TS620. It needs the common segments, composites and codes of X12 004040, one download for every transaction in the version. Download C# (1 KB) Common files (263 KB)
The intermediary model ediFabric Native loads with set_map. Download Native (53 KB)

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

ediFabric Native

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

ediFabric Native returns each 620 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 TS620. 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.

620 structure

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

IDNameUsageMax use
STTransaction Set HeaderOptional1
BGNBeginning SegmentMandatory1
N1NameMandatory2
REFReference IdentificationOptional1
Loop EXIExcavation Ticket InformationMandatory>1
EXIExcavation Ticket InformationMandatory1
DTMDate/Time ReferenceMandatory4
PERAdministrative Communications ContactOptional1
NX2Location ID ComponentOptional>1
PPAProperty LocationOptional>1
MTXTextOptional1
MEAMeasurementsOptional>1
Loop N1NameMandatory>1
N1NameMandatory1
N2Additional Name InformationOptional1
N3Address InformationOptional2
N4Geographic LocationOptional1
MSGMessage TextOptional2
PERAdministrative Communications ContactOptional2
DTMDate/Time ReferenceOptional1
Loop LIEIndividual or Event LocationOptional>1
LIEIndividual or Event LocationMandatory1
PPAProperty LocationMandatory>1
Loop LMCode Source InformationOptional>1
LMCode Source InformationMandatory1
LQIndustry CodeMandatory>1
SETransaction Set TrailerOptional1