ISENDS Intermediary system enablement or disablement message (D01A)

This is the standard EDIFACT D01A spec, with 8 loops and 34 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.

Standard spec Customize in 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 (63 KB) Generate classes
The ediFabric .NET template, class TSISENDS. It needs the common segments, composites and codes of EDIFACT D01A, one download for every transaction in the version. Download C# (1 KB) Common files (57 KB)
The intermediary model ediFabric Native loads with set_map. Native supports X12 today, and EDIFACT is coming. Download Native (1 KB)

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

ediFabric Native

Native supports X12 today, and EDIFACT is coming. When it's available, map version D01A to this Native model with set_map to parse ISENDS files to JSON from Python, Java, C or C#. See ediFabric Native.

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 ISENDS classes in Python, Java, Node.js, Go, Rust or C

The OpenEDI file describes each ISENDS as JSON. To work with ISENDS data as typed objects, generate classes from the OpenEDI file in your language; the root class is TSISENDS. The classes keep the loops, segments, lengths and code lists, but not the EDI data formats. Read more in Generate a class from OpenEDI.

Python: datamodel-code-generator. Node.js: openapi-typescript. Java, Go, Rust and C: OpenAPI Generator.

ISENDS structure

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

IDNameUsageMax use
UNHMessage HeaderOptional1
BGMBEGINNING OF MESSAGEMandatory1
ATTATTRIBUTEMandatory1
DTMDATE/TIME/PERIODOptional9
Loop PNAPARTY IDENTIFICATIONMandatory9
PNAPARTY IDENTIFICATIONMandatory1
ADRADDRESSOptional9
Loop CTACONTACT INFORMATIONOptional9
CTACONTACT INFORMATIONMandatory1
COMCOMMUNICATION CONTACTOptional9
GEIPROCESSING INFORMATIONOptional9
SEQSEQUENCE DETAILSOptional1
ATTATTRIBUTEOptional9
Loop RFFREFERENCEOptional9
RFFREFERENCEMandatory1
DTMDATE/TIME/PERIODOptional9
Loop ICDINSURANCE COVER DESCRIPTIONOptional99
ICDINSURANCE COVER DESCRIPTIONMandatory1
RFFREFERENCEOptional9
DTMDATE/TIME/PERIODOptional9
MKSMARKET/SALES CHANNEL INFORMATIONOptional9
Loop PRCPROCESS IDENTIFICATIONOptional9
PRCPROCESS IDENTIFICATIONMandatory1
GEIPROCESSING INFORMATIONOptional1
DTMDATE/TIME/PERIODOptional9
Loop ATTATTRIBUTEOptional9
ATTATTRIBUTEMandatory1
MOAMONETARY AMOUNTOptional1
PCDPERCENTAGE DETAILSOptional1
RCSREQUIREMENTS AND CONDITIONSOptional9
Loop DOCDOCUMENT/MESSAGE DETAILSOptional9
DOCDOCUMENT/MESSAGE DETAILSMandatory1
QRSQUERY AND RESPONSEOptional1
Loop RNGRANGE DETAILSOptional9
RNGRANGE DETAILSMandatory1
GEIPROCESSING INFORMATIONOptional9
MOAMONETARY AMOUNTOptional9
RFFREFERENCEOptional9
DTMDATE/TIME/PERIODOptional9
MKSMARKET/SALES CHANNEL INFORMATIONOptional9
ICDINSURANCE COVER DESCRIPTIONOptional9
UNTMessage TrailerOptional1