X12 Control Structure

Data Element / Min/Max / Definition / Value / Notes
ISA01 / 2/2 / Authorization Qualifier / 00 – No Authorization Present
05 – DoD Communication ID
06 – Federal Communication ID / Use ‘00’ for DLMS
ISA02 / 10/10 / Authorization ID / Trading Partner Specific / Use Blank for DLMS
ISA03 / 2/2 / Security Information Qualifier / 00 – No Security Info Present
01 – Password / Use ‘00’ for DLMS
ISA04 / 10/10 / Security Information / Trading Partner Specific / Use Blank for DLMS
ISA05 / 2/2 / Interchange Sender ID Qualifier / 01 – DUNS Number
02 – SCAC
04 – IATA
08 – UCC EDI
09 – X.121
10 – DoDAAC
16 – DUNS + 4
ZZ – Mutually Defined
ISA06 / 15/15 / Interchange Sender ID / Trading Partner Specific / Most Commercial VANs use either DTDN or GOVDP qualified with ZZ to identify DAASC as the trading partner. DLMS trading partners use S36121 qualified with 10 to identify DAASC
ISA07 / 2/2 / Interchange Receiver ID Qualifier / 01 – DUNS Number
02 – SCAC
04 – IATA
08 – UCC EDI
09 – X.121
10 – DoDAAC
16 – DUNS + 4
ZZ – Mutually Defined
ISA08 / 15/15 / Interchange Receiver ID / Trading Partner Specific / See ISA06
ISA09 / 6/6 / Interchange Date / YYMMDD / Use UTC (GMT)
ISA10 / 4/4 / Interchange Time / HHMM / Use UTC (GMT)
ISA11 / 1/1 / <4030 - Interchange Control Standards ID
>4030 - Repetition Separator / U – US EDI Community
Hex 1E or ‘ / For version prior to 4030 this was a constant “U”, for 4030 and above this is any of the recognized Element Separators as long as it doesn’t duplicate one that is already used.
ISA12 / 5/5 / Interchange Control Version Number / Trading Partner specific, dependent upon Implementation Convention used. / Expressed as , for example;
04030
ISA13 / 9/9 / Interchange Control Number / Must uniquely identify the ISA envelope over an extended period of time.(one year)
ISA14 / 1/1 / Acknowledgement Requested / 0 – None / This refers to TA1 acknowledgements, NOT 997
ISA15 / 1/1 / Usage Indicator / I - Information
T- Test
P- Production
ISA16 / 1/1 / Composite Element Separator / Trading partner specific / Hex 1F is recommended, “\” can be used as the printable version
GS01 / 2/2 / Functional ID / Transaction Set specific / See the Implementation Convention
GS02 / 2/12 / Application Sender Code / Trading Partner Specific / Use S36121 to identify DAAS Processing.
GS03 / 2/12 / Application Receiver Code / Trading Partner Specific
GS04 / 8/8 / Date / CCYYMMDD
GS05 / 4/4 / Time / HHMM
GS06 / 1/9 / Group Control Number / Must uniquely identify the group envelope over an extended period of time.(one year)
GS07 / 1/1 / Responsible Agency Code / X – ASC X12 Committee
GS08 / 6/12 / Version/Release Number / Trading Partner Specific – dependant upon Implementation Convention used, must be the same version as the ISA / Can include additional information regarding the specific release. Example BSM instance carries Implementation Convention information; 004030-940R

Separators

Name / Recommended (Non-printable) / Printable (presents data in a viewable format)
Data Element Separator / Hex 1D / *
Segment Terminator / Hex 1C / ~
Composite Element Separator / Hex 1F / \
Repetition Separator / Hex 1E / ‘