103 Abandoned Property Filings (004030)

This is the standard X12 004030 spec, with 6 loops and 49 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 (97 KB) Generate classes
The ediFabric .NET template, class TS103. It needs the common segments, composites and codes of X12 004030, one download for every transaction in the version. Download C# (1 KB) Common files (259 KB)
The intermediary model ediFabric Native loads with set_map. Download Native (71 KB)

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

ediFabric Native

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

ediFabric Native returns each 103 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 TS103. 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.

103 structure

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

IDNameUsageMax use
STTransaction Set HeaderOptional1
BGNBeginning SegmentMandatory1
BPRBeginning Segment for Payment Order/Remittance AdviceOptional1
NTENote/Special InstructionOptional>1
TRNTraceOptional1
CURCurrencyOptional1
REFReference IdentificationOptional>1
DTMDate/Time ReferenceOptional>1
AMTMonetary AmountOptional1
Loop NM1Individual or Organizational NameOptional>1
NM1Individual or Organizational NameMandatory1
N2Additional Name InformationOptional>1
N3Address InformationOptional>1
N4Geographic LocationOptional1
REFReference IdentificationOptional>1
PERAdministrative Communications ContactOptional>1
Loop N1NameMandatory>1
N1NameMandatory1
N2Additional Name InformationOptional>1
N3Address InformationOptional>1
N4Geographic LocationOptional1
INIIncorporation InformationOptional1
TC2CommodityOptional1
AMTMonetary AmountOptional>1
QTYQuantityOptional>1
NM1Individual or Organizational NameOptional>1
REFReference IdentificationOptional>1
DTMDate/Time ReferenceOptional>1
YNQYes/No QuestionOptional>1
Loop PERAdministrative Communications ContactOptional>1
PERAdministrative Communications ContactMandatory1
N3Address InformationOptional>1
N4Geographic LocationOptional1
REFReference IdentificationOptional>1
Loop LXAssigned NumberMandatory>1
LXAssigned NumberMandatory1
BLNBalance InformationMandatory>1
DTPDate or Time or PeriodOptional>1
INTInterestOptional>1
PDSProperty Description/Legal DescriptionOptional1
REFReference IdentificationOptional>1
Loop SHISecurity Holding InformationOptional1
SHISecurity Holding InformationMandatory1
DTMDate/Time ReferenceOptional>1
AMTMonetary AmountOptional>1
QTYQuantityOptional>1
PCTPercent AmountsOptional>1
Loop NM1Individual or Organizational NameOptional>1
NM1Individual or Organizational NameMandatory1
N2Additional Name InformationOptional1
N3Address InformationOptional>1
N4Geographic LocationOptional1
DTMDate/Time ReferenceOptional>1
REFReference IdentificationOptional>1
SETransaction Set TrailerOptional1