197 Real Estate Title Evidence (005040)

This is the standard X12 005040 spec, with 10 loops and 43 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 (91 KB) Generate classes
The ediFabric .NET template, class TS197. It needs the common segments, composites and codes of X12 005040, one download for every transaction in the version. Download C# (1 KB) Common files (269 KB)
The intermediary model ediFabric Native loads with set_map. Download Native (68 KB)

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

ediFabric Native

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

ediFabric Native returns each 197 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 TS197. 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.

197 structure

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

IDNameUsageMax use
STTransaction Set HeaderOptional1
BGNBeginning SegmentMandatory1
Loop N1Party IdentificationMandatory5
N1Party IdentificationMandatory1
N2Additional Name InformationOptional2
N3Party LocationOptional2
N4Geographic LocationOptional1
REFReference InformationOptional12
PERAdministrative Communications ContactOptional3
Loop PIDProduct/Item DescriptionMandatory>1
PIDProduct/Item DescriptionMandatory1
REFReference InformationMandatory12
DTPDate or Time or PeriodOptional1
MSGMessage TextOptional>1
Loop NM1Individual or Organizational NameOptional5
NM1Individual or Organizational NameMandatory1
N2Additional Name InformationOptional1
N3Party LocationOptional1
N4Geographic LocationOptional1
Loop EFIElectronic Format IdentificationOptional>1
EFIElectronic Format IdentificationMandatory1
BINBinary Data SegmentOptional1
Loop NX1Property or Entity IdentificationOptional>1
NX1Property or Entity IdentificationMandatory1
NX2Location ID ComponentOptional>1
PDSProperty Description/Legal DescriptionOptional20
PDEProperty Metes and Bounds DescriptionOptional>1
Loop FGSForm GroupMandatory10
FGSForm GroupMandatory1
DTPDate or Time or PeriodOptional2
FPTFinancial ParticipationOptional1
MSGMessage TextOptional>1
N9Extended Reference InformationOptional>1
Loop IN1Individual IdentificationOptional>1
IN1Individual IdentificationMandatory1
IN2Individual Name Structure ComponentsOptional30
AMTMonetary Amount InformationOptional2
M1InsuranceOptional1
MSGMessage TextOptional10
Loop LQIndustry Code IdentificationOptional>1
LQIndustry Code IdentificationMandatory1
DTPDate or Time or PeriodOptional3
REFReference InformationOptional>1
MSGMessage TextOptional>1
Loop IN1Individual IdentificationOptional>1
IN1Individual IdentificationMandatory1
IN2Individual Name Structure ComponentsOptional30
M1InsuranceOptional20
MSGMessage TextOptional4
Loop LXTransaction Set Line NumberOptional1
LXTransaction Set Line NumberMandatory1
G86Signature IdentificationOptional1
SETransaction Set TrailerOptional1