X12 Implementation. Guidelines. For. Inbound Functional Acknowledgement. (997i)



Similar documents
997 Functional Acknowledgment

X12 Implementation. Guidelines. For. Transfer Version (996o)

999 Implementation Acknowledgment. Version: 1.0 Draft

Arkansas Blue Cross Blue Shield EDI Report User Guide. May 15, 2013

Implementation Guidelines For ANSI X12 Interchange Control Structures Inbound & outbound. (v2002)

Portland General Electric Implementation Standard

IMPLEMENTATION GUIDELINES FOR ANSI ASC X12 EDI CONVENTIONS FILE TRANSFER (996) TRANSACTION SET

Implementation Guidelines: ANSI X12 Transaction Set 824 Application Advice DOCUMENT NUMBER: ICS S

Eaton Corporation Electronic Data Interchange (EDI) Standards Application Advice (824) Version 4010

Pos. Seg. Req. Loop No. ID Name Des. Max.Use Repeat LOOP ID IT IT1 Baseline Item Data M PID Product / Item Description M

997 MUST be sent to Safeway to confirm receipt of 824 transmission. This is unrelated to EDI syntax errors as reported on 997.

EDI GUIDELINES INVOICE 810 VERSION 4010

Receiving Advice/Acceptance Certificate - SERVICE PARTS ONLY

TEXAS INSTRUMENTS. Acknowledge / Rejection Advice Message CONTRL. Based on EDIFICE Issue 1 (Based on EDIFACT Version 92.1)

Connect COMMENTS REPORT ALL OPEN COMMENTS x290 Implementation Acknowledgment For Health Care Insurance

ANSI X12 version Text Message

EDI GUIDELINES. Motor Carrier Load Tender 204 VERSION

HP SYSTEMS UNIT. Companion Guide: Electronic Data Interchange Reports and Acknowledgements

DoD Transportation Electronic Data Interchange (EDI) Convention

X12 Implementation Guidelines For Outbound Receiving Advice v (861O)

944 Warehouse Stock Transfer Receipt Advice. X12/V4030/944: 944 Warehouse Stock Transfer Receipt Advice

824 Application Advice

Transaction Set Application Advice

BLUE CROSS AND BLUE SHIELD OF LOUISIANA DENTAL CLAIMS COMPANION GUIDE

IMPLEMENTATION GUIDELINES FOR ANSI ASC X12 EDI CONVENTIONS APPLICATION ADVICE (824) TRANSACTION SET

Applies to Version 6 Release 5 X12.6 Application Control Structure

EDI 214 ANSI X12 Version 4010 Transportation Carrier Shipment Status Message

Electronic Data Interchange

DLMS Supplement to Federal IC 996H GENCOMM / XML ADC 416 DoD M

214 Transportation Carrier Shipment Status Message

810 Invoice Revised 01/26/15

Electronic Data Interchange

How To Use Ansi X12N For A Business

ANSI X12 version Planning Schedule with Release Capability

EDI Compliance Report

810 Invoice ANSI ASC X12 Version 4010

Combined Insurance Company of America

Virginia Implementation Standard

3/31/08 ALTRA INDUSTRIAL MOTION Invoice Inbound 810 X Page 1 Created by Ralph Lenoir

Implementation Guideline

BORGWARNER IMPLEMENTATION GUIDELINE FOR V PLANNING SCHEDULE

Purpose of the 270/271 Health Care Eligibility Benefit Inquiry and Response

810 Invoice. Version: 2.3 Final. X12/V4010/810 : 810 Invoice. Advance Auto Parts. Publication: 3/17/2014 Trading Partner: Notes:

Delivery/Return Acknowledgment or 895 Adjustment UCS

EDI 210 Invoice. Motor Freight 210 Invoice with Stop Offs. Version: 1.0 ANSI X Draft

ANSI ASC X.12 Standard Version 4010 Transaction Set 214 Transportation Carrier Shipment Status Message

ANSI X12 version Remittance Advice

820 Payroll Deducted and Other Group Premium Payment for Insurance Products

Unified Grocers 820 EFT Specifications Remittance Advice Document Structure

CREDIT CARD BULK PROVIDER REQUIREMENTS

KANSAS CITY SOUTHERN EDI On-Boarding Guide

ANSI X12 version Advance Ship Notice

Electronic Data Interchange (EDI) Standards 810 Invoice Version 4010

CVS/Caremark. Implementation Guide. 810 RX DC Invoice. Version X

Your Choice. Page 1 of 10 Release 4 (May 2015) WEB-BSC

EDI IMPLEMENTATION GUIDE. 856 ANSI X12 V4010 Ship Notice/Manifest Regular (Non Steel)

Clearinghouse Screen Instructions for ANSI837

850 Purchase Order. X12/V4030/850: 850 Purchase Order. Version: 1.0 Draft

Electronic Data Interchange- Inbound Payments EDI 820/EFT Specifications for Duke Energy

84 LUMBER ELECTRONIC DATA INTERCHANGE VENDOR IMPLEMENTATION PROGRAM INFORMATION PACKAGE 810 INVOICES VERSION August 21, 2007

Supply Chain Merchandise Logistics E-Commerce Purchase Order

AMTEX IMPLEMENTATION GUIDELINES FOR EDI CONVENTIONS

214 Transportation Carrier Shipment Status Message - LTL

Reading a 999 File and how to fix Rejections using ClinicPro s Reference Files

The information in this document will be common for all X12N implementation guides.

CSX EDI 824 Application Advice Version:

820 Payroll Deducted and Other Group Premium Payment for Insurance Products

Data Exchange and Protocol Process Flows for Electric Deregulation in The State of New Jersey

ACE HARDWARE 810 INVOICE (FOR CREDIT MEMO ONLY) ANSI X PLEASE DO NOT TRANSMIT WAREHOUSE OR REBATE CREDIT MEMOS.

VERSION: ANSI X

ADOBE ANSI X Version: 1.0

Ultramar Ltd IMPLEMENTATION GUIDE

810 Invoice ANSI X.12 Version 5010

Customer EDI Guidelines United States 810 Invoice

PURCHASE ORDER RESPONSE

WPS Health Solutions

867 Product Transfer and Resale Report Ver/Rel Electronic Data I nterchange. Utility Industry Group Implementation Guideline.

WPS Health Insurance

Geisinger Health Plan

CVS/Caremark. Implementation Guide. 852 Product Activity Data Warehouse Movement. Version X

Invoice. Transaction Set (810) (Outbound from TI)

EDI Acknowledgement Transactions 1.1 Strategy for Oregon Trading Partners

ANSI X Product Transfer and Resale Report

SECTION II - EDI AT HUD... Strategic Plan... Business Process Overview... Technical Environment... Communications...

Now, suppliers can also select EDI as a method for receiving Change and Cancel Orders.

Toyota Boshoku America EDI Implementation Manual Version 1 for: TBA o TBIN o TBMS o TBCA - Woodstock o TBCA - Elmira

S.2.2 CHARACTER SETS AND SERVICE STRING ADVICE: THE UNA SEGMENT

945 Warehouse Shipping Advice

Xerox EDI Direct Claims Gateway Communication Document for ASC X12N 837 Health Care Claim Transaction Submission

IBM Gentran:Server for Microsoft Windows. HIPAA and NCPDP Compliance Guide

810 Invoice. Introduction: Heading: Functional Group ID=IN

846 Inbound Inventory Advice WITH VENDOR DIRECT (TO CONSUMER) ORDERS Macy s VICS Version 4010 VICS Document Mapping Effective 08/27/2007

EDIFACT MESSAGE IMPLEMENTATION GUIDELINES RECEP:0:2:FH:

835 Health Care Claim Payment/Advice Functional Group=HP

Geisinger Health Plan

EDI GUIDELINES PURCHASE ORDER 850 VERSION 4010

Florida Blue Health Plan

How To Write A Health Care Exchange Transaction

810 - Invoice. Set Number Set Name - Invoice Functional Group - IN

276/277 HIPAA Transaction Companion Guide HIPAA/V005010X212 VERSION: 1.0 DATE: 02/05/2014

Transcription:

X12 Implementation Guidelines For Inbound Functional Acknowledgement (997i)

997 Functional Acknowledgment Functional Group ID=FA Introduction: The purpose of this standard is to define the control structures for a set of acknowledgments to indicate the results of the syntactical analysis of the electronically encoded documents. The encoded documents are the transaction sets, which are grouped in functional groups, used in defining transactions for business data interchange. This standard does not cover the semantic meaning of the information encoded in the transaction sets. Pos. Seg. Req. Loop Notes and No. ID Name Des. Max.Use Repeat Comments M 010 ST Transaction Set Header M 1 M 020 AK1 Functional Group Response Header M 1 LOOP ID - AK2 999999 030 AK2 Transaction Set Response Header O 1 LOOP ID - AK3 999999 040 AK3 Data Segment Note O 1 050 AK4 Data Element Note O 1 060 AK5 Transaction Set Response Trailer O 1 M 070 AK9 Functional Group Response Trailer M 1 M 080 SE Transaction Set Trailer M 1 FD997I (002002) 2 October 5, 2001

Segment: ST Transaction Set Header Position: 010 Loop: Usage: Mandatory Purpose: To indicate the start of a transaction set and to assign a control number Notes: ST*997*0001 M ST01 143 Transaction Set Identifier Code M ID 3/3 Code uniquely identifying a Transaction Set 997 X12.20 Functional Acknowledgment M ST02 329 Transaction Set Control Number M AN 4/9 Identifying control number assigned by the originator for a Transaction Set. Also see: Data Interchange Control Number (28.) This number must match the value in SE02. FD997I (002002) 3 October 5, 2001

Segment: AK1 Functional Group Response Header Position: 020 Loop: Usage: Mandatory Purpose: To start acknowledgment of a functional group Notes: AK1*PO*12345 M AK101 479 Functional Identifier Code M ID 2/2 Code identifying a group of application related transaction sets This value must match the functional group identifier GS01 or the group being acknowledged. M AK102 28 Data Interchange Control Number M N0 1/9 Assigned number originated and maintained by the sender Control number must match number of GS06 of group being acknowledged. FD997I (002002) 4 October 5, 2001

Segment: AK2 Transaction Set Response Header Position: 030 Loop: AK2 Optional Usage: Optional Purpose: To start acknowledgment of a single transaction set Notes: AK2*850*0002 M AK201 143 Transaction Set Identifier Code M ID 3/3 Code uniquely identifying a Transaction Set Must match the value in ST01 of transaction being acknowledged. M AK202 329 Transaction Set Control Number M AN 4/9 Identifying control number assigned by the originator for a Transaction Set. Also see: Data Interchange Control Number (28.) Must match the value in ST02 of transaction being acknowledged. FD997I (002002) 5 October 5, 2001

Segment: AK3 Data Segment Note Position: 040 Loop: AK3 Optional Usage: Optional Purpose: To report errors in a data segment and identify the location of the data segment Notes: AK3*FST*10**2 M AK301 721 Segment ID Code M ID 2/3 Code defining the segment ID of the data segment in error. See Segment Directory. M AK302 719 Segment Position in Transaction Set M N0 1/6 The numerical count position of this data segment from the start of the transaction set: the transaction set header is count position 1 AK303 447 Loop Identifier Code O ID 1/4 Code identifying a loop within the transaction set which is bounded by the related LS and LE segments (corresponding LS and LE segments must have the same value for loop identifier). (Note: The loop ID number given on the transaction set diagram is recommended as the value for this data element in segments LS and LE.) AK304 720 Segment Note Code O ID 1/3 Code indicating the error found processing the data segment. AK305 720 Segment Note Code O ID 1/3 Code indicating the error found processing the data segment. AK306 720 Segment Note Code O ID 1/3 Code indicating the error found processing the data segment. AK307 720 Segment Note Code O ID 1/3 Code indicating the error found processing the data segment. AK308 720 Segment Note Code O ID 1/3 Code indicating the error found processing the data segment. FD997I (002002) 6 October 5, 2001

Segment: AK4 Data Element Note Position: 050 Loop: AK3 Optional Usage: Optional Purpose: To report errors in a data element and identify the location of the data element Notes: AK4*2*680*1 M AK401 722 Element Position in Segment M N0 1/2 This is used to indicate the relative position of the data element in error in this data segment. The count starts with 1 for the data element immediately following the segment ID. This value is 0 for an error in the segment ID. AK402 725 Data Element Reference Number O N0 1/4 Reference number used to locate the Data Element Dictionary. M AK403 723 Data Element Syntax Error Code M ID 1/3 Code indicating the error found after syntax edits of a data element AK404 724 Copy of Bad Data Element O AN 1/99 This is a copy of the data element in error FD997I (002002) 7 October 5, 2001

Segment: AK5 Transaction Set Response Trailer Position: 060 Loop: AK2 Optional Usage: Optional Purpose: To acknowledge acceptance or rejection and report errors in a transaction set Notes: AK5*E*2 M AK501 717 Set Acknowledge Code M ID 1/1 Code indicating if the transaction set is accepted or rejected after transfer. AK502 718 Transaction Set Note Code O ID 1/3 Code indicating the error found in processing the transaction set. AK503 718 Transaction Set Note Code O ID 1/3 Code indicating the error found in processing the transaction set. AK504 718 Transaction Set Note Code O ID 1/3 Code indicating the error found in processing the transaction set. AK505 718 Transaction Set Note Code O ID 1/3 Code indicating the error found in processing the transaction set. AK506 718 Transaction Set Note Code O ID 1/3 Code indicating the error found in processing the transaction set. FD997I (002002) 8 October 5, 2001

Segment: AK9 Functional Group Response Trailer Position: 070 Loop: Usage: Mandatory Purpose: Notes: To acknowledge acceptance or rejection of a functional group and report the number of included transaction sets from the original trailer, the accepted sets, and the received sets in this functional group AK9*A*1*1*1 M AK901 715 Functional Group Acknowledge Code M ID 1/1 This indicates if the full or partial functional group is accepted or rejected after transfer. M AK902 97 Number of Transaction Sets Included M N0 1/6 Total number of transaction sets included in the functional group or interchange (transmission) group terminated by the trailer containing this data element M AK903 123 Number of Received Transaction Sets M N0 1/6 Number of Transaction Sets received M AK904 2 Number of Accepted Transaction Sets M N0 1/6 Number of accepted Transaction Sets in a Functional Group AK905 716 Functional Group Note Code O ID 1/3 Code indicating the error found processing the functional group. AK906 716 Functional Group Note Code O ID 1/3 Code indicating the error found processing the functional group. AK907 716 Functional Group Note Code O ID 1/3 Code indicating the error found processing the functional group. AK908 716 Functional Group Note Code O ID 1/3 Code indicating the error found processing the functional group. AK909 716 Functional Group Note Code O ID 1/3 Code indicating the error found processing the functional group. FD997I (002002) 9 October 5, 2001

Segment: SE Transaction Set Trailer Position: 080 Loop: Usage: Mandatory Purpose: Notes: To indicate the end of the transaction set and provide the count of the transmitted segments (including the beginning (ST) and ending (SE) segments) SE*6*0001 M SE01 96 Number of Included Segments M N0 1/6 Total number of segments included in a transaction set including ST and SE segments M SE02 329 Transaction Set Control Number M AN 4/9 Identifying control number assigned by the originator for a Transaction Set. Also see: Data Interchange Control Number (28.) FD997I (002002) 10 October 5, 2001

Data Element Dictionary 715 Functional Group Acknowledge Code REPRESENTATION = ID 1/1 This indicates if the full or partial functional group is accepted or rejected after transfer. CODE A E P R DEFINITION The transmitted functional group is accepted. An acceptance of a functional group is an acceptance of all transaction sets in that functional group. The transmitted functional group is accepted, but errors are noted. This means that the sender must not resend this data. Part of the transmitted functional group is accepted by transaction set. The transmitted functional group is rejected. A rejection of a functional group is a rejection of all transaction sets in that functional group. Depending on the error reason, the sender may resend this data. 716 Functional Group Note Code REPRESENTATION = ID 1/3 Code indicating the error found processing the functional group. CODE DEFINITION 1 Functional Group Not Supported 2 Functional Group Version Not Supported 3 Functional Group Trailer Missing 4 The data interchange control number in the header and trailer do not match. The value from the header is used in the acknowledgment. 5 Number of Included Transaction Sets Does Not Match Actual Count 717 Set Acknowledge Code REPRESENTATION = ID 1/1 Code indicating if the transaction set is accepted or rejected after transfer. CODE A E R DEFINITION The transmitted transaction set is accepted. The transmitted transaction set is accepted, but errors are noted. This means that the sender must not resend this data. The transmitted transaction set is rejected. Depending on the error reason, the sender may resend this data. 718 Transaction Set Note Code REPRESENTATION = ID 1/3 Code indicating the error found in processing the transaction set. CODE DEFINITION 1 Transaction Set Not Supported 2 Transaction Set Trailer Missing 3 The transaction set control number in the header and trailer do not match. The value from the header is used in the acknowledgment. 4 Number of Included Segments Does Not Match Actual Count 5 One or More Segments in Error FD997I (002002) 11 October 5, 2001

720 Segment Note Code REPRESENTATION = ID 1/3 Code indicating the error found processing the data segment. CODE DEFINITION 1 Unrecognized segment ID 2 Unexpected segment 3 Mandatory segment missing 4 Loop Occurs Over Maximum Times 5 Segment Within Loop Exceeds Maximum Use 723 Data Element Syntax Error Code REPRESENTATION = ID 1/3 Code indicating the error found after syntax edits of a data element CODE DEFINITION 1 Mandatory data element missing 2 Conditional required data element missing. 3 Too many data elements. 4 Data element too short. 5 Data element too long. 6 Invalid character in data element. 7 Invalid code value. 8 Invalid Date 9 Invalid Time FD997I (002002) 12 October 5, 2001

Example GS~FA~CESWA~AP13A~011008~0802~000000176~X~002002 ST~997~0001 AK1~SS~000000176 AK2~862~0001 AK5~A AK9~A~1~1~1 SE~6~0001 GE~1~000000176IEA~1~000000176 GS*FA*V3F1A*F159B*011005*1012*000001774*X*002002\ ST*997*0001\ AK1*FA*1909\ AK2*997*19090001\ AK3*AK1*2\ AK4*3**6*000001502\ AK5*R*5\ AK2*997*19090002\ AK3*AK1*2\ AK4*3**6*000001510\ AK5*R*5\ AK9*R*2*2*0\ SE*12*0001\ GE*1*000001774\ FD997I (002002) 13 October 5, 2001