101 Name and Address Lists (004040)

This is the standard X12 004040 spec, with 3 loops and 12 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 (56 KB) Generate classes
The ediFabric .NET template, class TS101. 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 (39 KB)

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

ediFabric Native

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

ediFabric Native returns each 101 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 TS101. 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.

101 structure

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

IDNameUsageMax use
STTransaction Set HeaderOptional1
BGNBeginning SegmentMandatory1
Loop DTMDate/Time ReferenceMandatory>1
DTMDate/Time ReferenceMandatory1
N1NameMandatory>1
Loop N9Reference IdentificationOptional>1
N9Reference IdentificationMandatory1
Loop LXAssigned NumberMandatory>1
LXAssigned NumberMandatory1
IN2Individual Name Structure ComponentsOptional>1
NX2Location ID ComponentOptional>1
REFReference IdentificationOptional>1
SPAStatus of Product or ActivityOptional1
COMCommunication Contact InformationOptional>1
SETransaction Set TrailerOptional1