Hi Guys,
This is for the EDI starter. Below is the complete detail of EDI 997 segment and element details.
997 Functional Acknowledgment Transaction Layout:
| No. | SegID | Name | Description | Example | M/O |
| 010 | ST | Transaction Set Header | To indicate the start of a transaction set and to assign a control number | ST*997*382823~ | M |
| ST01 | Code uniquely identifying a Transaction Set | M | |||
| ST02 | Identifying control number that must be unique within the transaction setfunctional group assigned by the originator for a transaction set | M | |||
| 020 | AK1 | Functional Group Response Header | To start acknowledgment of a functional group | AK1*QM*2459823 | M |
| AK101 | Code identifying a group of application related transaction setsIN Invoice Information (810)SH Ship Notice/Manifest (856) | ||||
| AK102 | Assigned number originated and maintained by the sender | ||||
| 030 | AK2 | Transaction Set Response Header | To start acknowledgment of a single transaction set | AK2*856*001 | M |
| AK201 | Code uniquely identifying a Transaction Set810 Invoice856 Ship Notice/Manifest | M | |||
| AK202 | Identifying control number that must be unique within the transaction setfunctional group assigned by the originator for a transaction set | M | |||
| 040 | AK3 | Data Segment Note | To report errors in a data segment and identify the location of the data segment | AK3*TD3*9 | O |
| AK301 | Segment ID Code | Code defining the segment ID of the data segment in error (See Appendix A -Number 77) | |||
| AK302 | Segment Position in Transaction Set | The numerical count position of this data segment from the start of thetransaction set: the transaction set header is count position 1 | |||
| 050 | AK4 | Data Element Note | To report errors in a data element or composite data structure and identify the location ofthe data element | AK4*2**2 | O |
| AK401 | Position in Segment | Code indicating the relative position of a simple data element, or the relativeposition of a composite data structure combined with the relative position ofthe component data element within the composite data structure, in error; thecount starts with 1 for the simple data element or composite data structureimmediately following the segment ID | |||
| AK402 | Element Position in Segment | This is used to indicate the relative position of a simple data element, or therelative position of a composite data structure with the relative position of thecomponent within the composite data structure, in error; in the data segmentthe count starts with 1 for the simple data element or composite data structureimmediately following the segment ID | |||
| AK403 | Data Element Syntax Error Code | Code indicating the error found after syntax edits of a data element1 Mandatory Data Element Missing2 Conditional Required Data Element Missing3 Too Many Data Elements4 Data Element Too Short5 Data Element Too Long6 Invalid Character in Data Element7 Invalid Code Value8 Invalid Date9 Invalid Time10 Exclusion Condition Violated | |||
| AK404 | Copy of Bad Data Element | This is a copy of the data element in error | |||
| 060 | AK5 | AK5 Transaction Set Response Trailer | To acknowledge acceptance or rejection and report errors in a transaction set | AK5*A~AK5*R*5~ | M |
| AK501 | Transaction Set Acknowledgment Code | Code indicating accept or reject condition based on the syntax editing of thetransaction setA AcceptedE Accepted But Errors Were NotedR Rejected | |||
| AK502 | Transaction Set Syntax Error Code | Code indicating error found based on the syntax editing of a transaction set1 Transaction Set Not Supported2 Transaction Set Trailer Missing3 Transaction Set Control Number in Header and TrailerDo Not Match4 Number of Included Segments Does Not Match ActualCount5 One or More Segments in Error6 Missing or Invalid Transaction Set Identifier7 Missing or Invalid Transaction Set Control Number | |||
| 070 | AK9 | Functional Group Response Trailer | To acknowledge acceptance or rejection of a functional group and report the number ofincluded transaction sets from the original trailer, the accepted sets, and the received setsin this functional group | AK9*A*1*1*1~AK9*R*1*1*0~ | M |
| AK901 | Functional Group Acknowledge Code | Code indicating accept or reject condition based on the syntax editing of thefunctional groupA AcceptedE Accepted, But Errors Were Noted.R Rejected | |||
| AK902 | Number of Transaction Sets Included | Total number of transaction sets included in the functional group orinterchange (transmission) group terminated by the trailer containing this dataelement | |||
| AK903 | Number of Received Transaction Sets | Number of Transaction Sets received | |||
| AK904 | Number of Accepted Transaction Sets | Number of accepted Transaction Sets in a Functional Group | |||
| AK905 | Functional Group Syntax Error Code | Code indicating error found based on the syntax editing of the functional groupheader and/or trailer1 Functional Group Not Supported2 Functional Group Version Not Supported3 Functional Group Trailer Missing4 Group Control Number in the Functional Group Headerand Trailer Do Not Agree5 Number of Included Transaction Sets Does Not MatchActual Count6 Group Control Number Violates Syntax | |||
| 080 | SE | Transaction Set Trailer | To indicate the end of the transaction set and provide the count of the transmittedsegments (including the beginning (ST) and ending (SE) segments) | SE*9*223~ | M |
| SE01 | Number of Included Segments | Total number of segments included in a transaction set including ST and SEsegments | |||
| SE02 | Transaction Set Control Number | Identifying control number that must be unique within the transaction setfunctional group assigned by the originator for a transaction set |
posted @ Friday, June 18, 2010 3:13 AM
