American Electric Power Outbound Implementation Guide

Similar documents
09/25/2015 Functional Acknowledgment Table of Contents

997 Functional Acknowledgment

997 Functional Acknowledgment

997 Transaction 997 IBM Subset - Functional Acknowledgment /2009

997 Functional Acknowledgment

X12 Implementation Guidelines For Inbound 997 v (I )

EDI Functional Acknowledgment

Customer EDI Guidelines 997 Functional Acknowledgment

CP EDI 997 Guidelines (Version 7010)

997 Functional Acknowledgement X12 Version 4010

997 - Functional Acknowledgment Author: DOT FOODS, INC. Publication: March 3, 2005

To: Electronic Data Interchange (EDI) Partners:

Functional Acknowledgment - 997

RHODE ISLAND Electronic Business Transactions

Functional Acknowledgment

ADOBE Inbound 997 ANSI X Version: 1.0

Benteler Electronic Data Interchange Specifications Transaction 997

Functional Acknowledgment - 997

EDI 997 Functional Acknowledgement Version

997 Functional Acknowledgment

DSW Designer Shoe Warehouse

EFS 997 Functional Acknowledgment X12/V4010/997: 997 Functional Acknowledgment Version: 1.3

997 Functional Acknowledgment

Document Version FUNCTIONAL ACKNOWLEDGEMENT (ANSI X12 VERSION 4040) 10/10/2008. X12V General Parts, Inc./CARQUEST

MOBIS Alabama, LLC IMPLEMENTATION GUIDELINES FOR ASC X12 EDI CONVENTIONS FUNCTIONAL ACKNOWLEDGEMENT TRANSACTON SET (997) VERSION/RELEASE

997 Functional Acknowledgment (Inbound)

997 Functional Acknowledgment

Functional Acknowledgment Response Transaction Cycle Table of Contents

ZF Group North American Operations. EDI Implementation Guide

Rite Aid Corporation 997 Functional Acknowledgment Version

VERSION FUNCTIONAL ACKNOWLEDGEMENT 1 OF 10

997 Functional Acknowledgment

824 Application Advice X12/V4010/824: 824 Application Advice Version: 1.3

865 Purchase Order Change Acknowledgment/Request - Seller Initiated

UDC Consolidated Billing Application Advice Conventions (UDC Response to 810 for UDC Consolidated Bill Option)

990 Response to a Load Tender

EDI Specification. 997 Functional Acknowledgement. For all Trading Partners. Version: ANSI X /21/2011 V 1.0

860 Purchase Order Change Request (Buyer Initiated) X12 Version Version: 2.0

BRP Inc. ELECTRONIC DATA INTERCHANGE (EDI) IMPLEMENTATION GUIDE 865 VERSION 4010 FROM SUPPLIER. Document version 1.5

990 Response to a Load Tender

ANSI X12 version Receiving Advice/ Acceptance Certificate

Safeway Inc. EDS Department 1 of 7 UCS Map

990 RESPONSE TO A LOAD TENDER. Version:

865 Purchase Order Change Acknowledgment/Request - Seller Initiated

NAPM RAIL INDUSTRY FORUM Application Advice IMPLEMENTATION GUIDELINE FOR EDI

990 Response to a Load Tender

990 Response to a Load Tender

850 Purchase Order X12 Version Version: 2.0

997 Functional Acknowledgment

865 Purchase Order Change Acknowledgment/Request - Seller Initiated

824 Application Advice

997 Functional Acknowledgement

831 Application Control Totals

855 Purchase Order Acknowledgment. United Natural Foods

855 Purchase Order Acknowledgment

849 Response to Product Transfer

X Envelops. University Hospitals Health Systems University Hospitals of Cleveland ASNI X12 Envelops Version Functional Group ID=

Electronic Commerce Customer Guide

Amazon Purchase Order Acknowledgment

Introduction: Functional Group ID=GF

RCI 855 Purchase Order Acknowledgment

Ver 2 Rel 2 Envelope Segments -

824 Application Advice

ANSI X (Product Transfer and Resale Report) Outbound (from Eclipse) Version 4010

824 Application Advice

Introduction: Heading: Detail: Summary: Functional Group ID=TX

846 Inventory Inquiry/Advice

844 Product Transfer Account

816 Organizational Relationships

855 Purchase Order Acknowledgment

ANSI X (Lockbox) Inbound (to Eclipse) Version 4010

814 General Request, Response or Confirmation

Pos Id Segment Name Req Max Use Repeat Notes Usage 0100 ST Transaction Set Header M 1 Must use 0200 BGN Beginning Segment M 1 Must use

846 Inventory Inquiry/Advice

evo.com 855 Purchase Order Acknowledgment Author: SPS Commerce Company: evo.com Trading Partner: Created: 3/8/2013 Modified: 8/9/2017 Notes:

ICS Interchange Control Structures

850 Purchase Order X12/V4010/850: 850 Purchase Order Version: 1.0 Final Publication: 1/21/2009 Notes:

CVS/Caremark. Implementation Guide. 830 Planning Schedule with Release Capability. Version X

12/19/2017 Purchase Order Acknowledgment - 855

850 - Purchase Order Author: DOT FOODS, INC. Publication: September 24, 2008

HCHETTE BOOK GROUP USA 855 Purchase Order Acknowledgement VERSION 4010 IMPLEMENTATION GUIDE

EDI Implementation Guide Version

850 Purchase Order X12/V4010/850: 850 Purchase Order Version: 1.0 Company: JR Simplot Company Publication: 6/1/2016 Notes:

864 Text Message Mar 2016

820 Payment Order/Remittance Advice

EDI Guideline. Version: 2.2. X12/V4010/832 : 832 Price/Sales Catalog. Publication: 1/21/2019 Trading Partner: Quebec EDI Healthcare Program

GovX Purchase Order. X12/V5010/850: 850 Purchase Order

870 Order Status Report

Golfsmith 846 EDI Guidelines

860 Purchase Order Change Request - Buyer Initiated

Plex Systems IMPLEMENTATION GUIDELINES FOR ANSI X12 EDI CONVENTIONS. 824 TRANSACTION SET APPLICATION ADVICE Version Created November 11, 2015

LOOP ID - PO PO1 Baseline Item Data M 1 N2/ REF Reference Identification O >1

International Truck and Engine Corporation

850 Purchase Order. X12/V4010/850: 850 Purchase Order

997 Functional Acknowledgment

861 Receiving Advice/Acceptance Certificate

846 Inventory Inquiry/Advice. X12/V5010/846: 846 Inventory Inquiry/Advice

DSW Shoe Warehouse 832 Price/Sales Catalog Vendor Direct

Freightliner Corporation Interchange Envelope Structure

Illinois. Electronic Data Interchange. Implementation Guide For. Transaction Set ANSI ASC X12 Version Enrollment Request Version 2.

Transcription:

American Electric Power 4010 997 Outbound Implementation Guide VERSION: 1.0 Author: AEP EDI Dept. 997O4010.RTF 1

997 Functional Acknowledgment Functional Group=FA This Draft Standard for Trial Use contains the format and establishes the data contents of the Functional Acknowledgment Transaction Set (997) for use within the context of an Electronic Data Interchange (EDI) environment. The transaction set can be used 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. Heading: Pos Id Segment Name Req Max Use Repeat Notes 010 ST Transaction Set Header M 1 N1/010 020 AK1 Functional Group Response Header M 1 N1/020 LOOP ID - AK2 999999 030 AK2 Transaction Set Response Header O 1 N1/030 060 AK5 Transaction Set Response Trailer M 1 070 AK9 Functional Group Response Trailer M 1 080 SE Transaction Set Trailer M 1 Notes: 1/010 These acknowledgments shall not be acknowledged, thereby preventing an endless cycle of acknowledgments of acknowledgments. Nor shall a Functional Acknowledgment be sent to report errors in a previous Functional Acknowledgment. The Functional Group Header Segment (GS) is used to start the envelope for the Functional Acknowledgment Transaction Sets. In preparing the functional group of acknowledgments, the application sender's code and the application receiver's code, taken from the functional group being acknowledged, are exchanged; therefore, one acknowledgment functional group responds to only those functional groups from one application receiver's code to one application sender's code. There is only one Functional Acknowledgment Transaction Set per acknowledged functional group. 1/020 AK1 is used to respond to the functional group header and to start the acknowledgement for a functional group. There shall be one AK1 segment for the functional group that is being acknowledged. 1/030 AK2 is used to start the acknowledgement of a transaction set within the received functional group. The AK2 segments shall appear in the same order as the transaction sets in the functional group that has been received and is being acknowledged. 997O4010.RTF 2

ST Transaction Set Header Pos: 010 Max: 1 Loop: N/A Elements: 2 To indicate the start of a transaction set and to assign a control number Ref Id Element Name ST01 143 Transaction Set Identifier Code M ID 3/3 ST02 329 Transaction Set Control Number M AN 4/9 Semantics: 1. The transaction set identifier (ST01) used by the translation routines of the interchange partners to select the appropriate transaction set definition (e.g., 810 selects the Invoice Transaction Set). 997O4010.RTF 3

AK1 Functional Group Response Header Pos: 020 Max: 1 Loop: N/A Elements: 2 To start acknowledgment of a functional group Ref Id Element Name AK101 479 Functional Identifier Code M ID 2/2 AK102 28 Group Control Number M N0 1/9 Semantics: 1. AK101 is the functional ID found in the GS segment (GS01) in the functional group being acknowledged. 2. AK102 is the functional group control number found in the GS segment in the functional group being acknowledged. 997O4010.RTF 4

AK2 Transaction Set Response Header Pos: 030 Max: 1 Heading - Optional Loop: AK2 Elements: 2 To start acknowledgment of a single transaction set Ref Id Element Name AK201 143 Transaction Set Identifier Code M ID 3/3 AK202 329 Transaction Set Control Number M AN 4/9 Semantics: 1. AK201 is the transaction set ID found in the ST segment (ST01) in the transaction set being acknowledged. 2. AK202 is the transaction set control number found in the ST segment in the transaction set being acknowledged. 997O4010.RTF 5

AK5 Transaction Set Response Trailer Pos: 060 Max: 1 Loop: AK2 Elements: 1 To acknowledge acceptance or rejection and report errors in a transaction set Ref Id Element Name AK501 717 Transaction Set Acknowledgment Code Code NAME A Accepted E Accepted But Errors Were Noted R Rejected M ID 1/1 997O4010.RTF 6

AK9 Functional Group Response Trailer Pos: 070 Max: 1 Loop: N/A Elements: 4 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 Ref Id Element Name AK901 715 Functional Group Acknowledge Code Code NAME A Accepted E Accepted,But Errors Were Noted. P Partially Accepted,At Least One Transaction Set Was Rejected R Rejected M ID 1/1 AK902 97 Number of Transaction Sets Included M N0 1/6 AK903 123 Number of Received Transaction Sets M N0 1/6 AK904 2 Number of Accepted Transaction Sets M N0 1/6 Comments: 1. If AK901 contains the value "A" or "E", then the transmitted functional group is accepted. 997O4010.RTF 7

SE Transaction Set Trailer Pos: 080 Max: 1 Loop: N/A Elements: 2 To indicate the end of the transaction set and provide the count of the transmitted segments (including the beginning (ST) and ending (SE) segments) Ref Id Element Name SE01 96 Number of Included Segments M N0 1/10 SE02 329 Transaction Set Control Number M AN 4/9 Comments: 1. SE is the last segment of each transaction set. 997O4010.RTF 8