Appendix 6 - X12 Control Structures and Separators



AP6. APPENDIX 6X12 CONTROL STRUCTURES AND SEPARATORSAP6.1. GENERALAs noted in Chapter 5, X12 Control Structures and Segment/Element Separators are defined in the following tables:AP6.1.1. X12 Control Structures. The approved Defense Logistics Management Standards (DLMS) American National Standards Institute (ANSI) X12 Control Structures are defined in T1, below:Table A6.T1. X12 Control StructuresDataElementMin/MaxDefinitionValueNotesISA012/2Authorization Qualifier00 – No Authorization Present05 – DoD Communication ID06 – Fed. Communication ID ISA0210/10Authorization IDTrading Partner SpecificUse Blank for DLMSISA032/2Security Info. Qualifier00 – No Security Info 01 – PasswordUse ‘00’ for DLMSISA0410/10Security Info.Trading Partner SpecificUse Blank for DLMSISA052/2Interchange Sender ID Qualifier01 – DUNS Number02 – SCAC04 – IATA08 – UCC EDI09 – X.12110 – DoDAAC16 – DUNS + 4ZZ – Mutually DefinedISA0615/15Interchange Sender IDTrading Partner SpecificMost 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 DAAS eBus. ISA072/2Interchange Receiver ID Qualifier01 – DUNS Number02 – SCAC04 – IATA08 – UCC EDI09 – X.12110 – DoDAAC16 – DUNS + 4ZZ – Mutually DefinedISA0815/15Interchange Receiver IDTrading Partner SpecificSee ISA06ISA096/6Interchange DateYYMMDDUse UTC (GMT)ISA104/4Interchange TimeHHMMUse UTC (GMT)ISA111/1<4030 -InterchangeControl Standards ID>4030 - Repetition SeparatorU – US EDI CommunityHex 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.ISA125/5Interchange Control Version NumberTrading Partner specific, dependent upon implementation Convention used.Expressed as , for example; 04030ISA139/9Interchange Control NumberMust uniquely identify the ISA envelope over an extended period of time.(one year)ISA141/1Acknowledge-ment Requested0 - NoneThis refers to TA1 acknowledgements, NOT 997ISA151/1Test IndicatorT - TestP - ProductionISA161/1Composite Element SeparatorTrading partner specificHex 1F is recommended, “\” can be used as the printable versionGS012/2Functional IDTransaction Set specificSee the Implementation ConventionGS022/12Application Sender CodeTrading Partner SpecificUse S36121 to identify DAAS Processing.GS032/12Application Receiver CodeTrading Partner SpecificGS048/8DateCCYYMMDDGS054/4TimeHHMMGS061/9Group Control NumberMust uniquely identify the group envelope over an extended period of time.(one year)GS071/1Responsible Agency CodeX – ASC X12 CommitteeGS086/12Version/Release No.Trading Partner Specific -dependent upon Implementation Convention used, must be the same version as the ISACan include additional information regarding the specific release. example BSM instance carries Implementation Convention information; 004030-940R AP6.1.2. Segment/Element Separators. The approved DLMS ANSI X12 Separators are defined in T2, below:Table A6.T2. X12 Segment/Element SeparatorsNameRecommended(Non-printable)Printable (data in view-able format) EXAMPLES ONLYData Element SeparatorHex 1D*Segment TerminatorHex 1C~Composite Element Sep.Hex 1F\Repetition SeparatorHex 1E‘ ................
................

In order to avoid copyright disputes, this page is only a partial summary.

Google Online Preview   Download