EDI Implementation Guide ANSI X12 997 004010 Version 1.4 Authors: ZF NAO EDI Team Publication Date: May 12, 2005 Created: May 1, 2005 Modified: May 13, 2005
Table of Contents Introduction... 1 ZF Group NAO Contacts... 2 Configuration and Setup... 3 Sample Production Data... 3 Functional Acknowledgment... 5 Interchange Control Header... 7 Functional Group Header... 9 Transaction Set Header... 11 Functional Group Response Header... 12 Loop AK2... 13 Transaction Set Response Header... 14 Loop AK3... 15 Data Segment Note... 16 Data Element Note... 17 Transaction Set Response Trailer... 18 Functional Group Response Trailer... 19 Transaction Set Trailer... 21 Functional Group Trailer... 22 Interchange Control Trailer... 23
Introduction This document provides an explanation of the structure and data content of the ASC ANSI X12 997 transaction set issued by ZF Group North American Operations (NAO). Contact must be made with our EDI Group before any ASC ANSI X12 997 transaction set will be tested with the supplier. A receiver ID will be determined at the time of contact. We require that the ASC ANSI X12 997 transaction set be sent back within 48 hours of you receiving any ASC ANSI X12 transaction from us. Our EDI Group will strive to implement new ANSI-X12 transaction sets and update existing sets, as the efficient exchange of information becomes more critical to the success of our organizations. We will work closely with our supplier community to implement these changes. Bill Roeding EDI Team Leader ZF Corporate Services LLC Corporate Information Technology 205 West Fourth Street, Suite 1140 Cincinnati, OH 45202 Phone (513) 744-3700 Fax (513) 744-3710 Email: bill.roeding@zf.com Version 1.4 EDI Implementation Guide: ANSI X12 997 004010 Page 1
ZF Group NAO Contacts North American Headquarters ZF Group NAO 15811 Centennial Drive Northville, MI 48167 Corporate Information Technology ZF Corporate Services LLC 205 West Fourth Street, Suite 1140 Cincinnati, OH 45202 ZF Group NAO Help Desk 513-744-3700 ZF Group NAO EDI Support Email edi-support.nao@zf.com ZF Group NAO EDI Team Leader Bill Roeding bill.roeding@zf.com Version 1.4 EDI Implementation Guide: ANSI X12 997 004010 Page 2
Configuration and Setup Version/Release Level ZF Group NAO uses the ANSI X12 version 004010 for the 997 transaction set. Value Added Network Frequency of transmission Sender Identification ZF Group NAO uses Sterling Commerce Information Broker as our data communication network service (877-432-4300). As specified in the plant-supplier agreement. ZF Group NAO uses the facility DUNS number with a 01 qualifier. DUNS No. Facility Code Facility Location 848466603 LC01 ZF Lemforder Brewer, ME 024058567 LC03 ZF Lemforder - Hebron, KY 033314019 LC4M ZF Lemforder Components - Duncan, SC 838667152 LC4S ZF Lemforder Systems - Duncan, SC 054975029 LC05 ZF Lemforder - Lancaster, SC 123851045 LC06 ZF Lemforder Lapeer, MI 131662855 LC08 ZF Lemforder Chicago, IL 185581852 LC09 ZF Lemforder Newton, NC 009413373 ZFIM ZF Marine - Ft. Lauderdale, FL 933874026 (AZFG, ZAGT, ZFIG) ZF Industries - Gainesville, GA 877009449 ZFIC ZF Industries Vernon Hills, IL 965061609 ZFIT ZF Industries - Tuscaloosa, AL Receiver Identification Web-based EDI solutions In most cases the receiver ID is the supplier s DUNS number. Special cases will be mutually agreed upon between ZF Group NAO and the supplier. SupplyOn - Internet marketplace for suppliers. Telephone 011 49 1805 SUPPLYON (from North America) or From outside the USA/Canada, +49 800-SU PP LY ON (+49 800-78 77 59 66) E-mail: Info@SupplyOn.com Contact the EDI staff to learn more about receiving EDI data over the Internet. Sample Production Data ISA*00* *00* *ZZ*123456789 *01*131662855 *050504*1702*U*00401*000000070*0*P*>~ Version 1.4 EDI Implementation Guide: ANSI X12 997 004010 Page 3
GS*FA*123456789*131662855*20050504*1702*54*X*004010~ ST*997*0054~ AK1*PS*42~ AK2*830*42~ AK5*A~ AK9*A*1*1*1~ SE*6*0054~ GE*1*54~ IEA*1*000000070~ Version 1.4 EDI Implementation Guide: ANSI X12 997 004010 Page 4
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. Not Defined: Pos ID Segment Name Req Max Use Repeat Notes Usage ISA Interchange Control Header M 1 Must use GS Functional Group Header M 1 Must use Heading: Pos ID Segment Name Req Max Use Repeat Notes Usage 010 ST Transaction Set Header M 1 N1/010 Must use 020 AK1 Functional Group Response Header M 1 N1/020 Must use LOOP ID - AK2 999999 N1/030L 030 AK2 Transaction Set Response Header O 1 N1/030 Used LOOP ID - AK3 999999 C1/040L 040 AK3 Data Segment Note O 1 C1/040 Used 050 AK4 Data Element Note O 99 Used 060 AK5 Transaction Set Response M 1 Must use Trailer 070 AK9 Functional Group Response M 1 Must use Trailer 080 SE Transaction Set Trailer M 1 Must use Not Defined: Pos ID Segment Name Req Max Use Repeat Notes Usage GE Functional Group Trailer M 1 Must use IEA Interchange Control Trailer M 1 Must use 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. Version 1.4 EDI Implementation Guide: ANSI X12 997 004010 Page 5
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/030L 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. 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. Comments: 1/040L The data segments of this standard are used to report the results of the syntactical analysis of the functional groups of transaction sets; they report the extent to which the syntax complies with the standards for transaction sets and functional groups. They do not report on the semantic meaning of the transaction sets (for example, on the ability of the receiver to comply with the request of the sender). 1/040 The data segments of this standard are used to report the results of the syntactical analysis of the functional groups of transaction sets; they report the extent to which the syntax complies with the standards for transaction sets and functional groups. They do not report on the semantic meaning of the transaction sets (for example, on the ability of the receiver to comply with the request of the sender). Version 1.4 EDI Implementation Guide: ANSI X12 997 004010 Page 6
Interchange Control Header Pos: Max: 1 ISA Not Defined - Mandatory Loop: N/A Elements: 16 User Option (Usage): Must use To start and identify an interchange of zero or more functional groups and interchange-related control segments. Element Summary: Ref ID Element Name Req Type Min/Max Usage ISA01 I01 Authorization Information Qualifier M ID 2/2 Must use Description: Code to identify the type of information in the Authorization Information. ISA02 I02 Authorization Information M AN 10/10 Must use Description: Information used for additional identification or authorization of the interchange sender or the data in the interchange. The type of information is set by the Authorization Information Qualifier (I01). ISA03 I03 Security Information Qualifier M ID 2/2 Must use Description: Code to identify the type of information in the Security Information. ISA04 I04 Security Information M AN 10/10 Must use Description: Used for identifying the security information about the interchange sender or the data in the interchange. The type of information is set by the Security Information Qualifier (I03). ISA05 I05 Interchange ID Qualifier M ID 2/2 Must use Description: Qualifier to designate the system/method of code structure used to designate the sender or receiver ID element being qualified. ISA06 I06 Interchange Sender ID M AN 15/15 Must use Description: Identification code published by the sender for other parties to use as the receiver ID to route data to them. The sender always codes this value in the sender ID element. ISA07 I05 Interchange ID Qualifier M ID 2/2 Must use Description: Qualifier to designate the system/method of code structure used to designate the sender or receiver ID element being qualified. ISA08 I07 Interchange Receiver ID M AN 15/15 Must use Description: Identification code published by the receiver of the data. When sending, it is used by the sender as their sending ID, thus other parties sending to them will use this as a receiving ID to route data to them. ISA09 I08 Interchange Date M DT 6/6 Must use Version 1.4 EDI Implementation Guide: ANSI X12 997 004010 Page 7
Description: Date of the interchange, expressed as YYMMDD. ISA10 I09 Interchange Time Description: Time of the interchange, expressed as HHMM. ISA11 I10 Interchange Control Standards Identifier Description: Code to identify the agency responsible for the control standard used by the message that is enclosed by the interchange header and trailer. ISA12 I11 Interchange Control Version Number Description: Code specifying the version number of the interchange control segments. ISA13 I12 Interchange Control Number Description: A control number assigned by the interchange sender. ISA14 I13 Acknowledgment Requested Description: Code sent by the sender to request an interchange acknowledgment (TA1). ISA15 I14 Usage Indicator Description: Code to indicate whether data enclosed by this interchange envelope is test, production or information. ISA16 I15 Component Element Separator Description: Type is not applicable. The component element separator is a delimiter and not a data element; this field provides the delimiter used to separate component data elements within a composite data structure. This value must be different than the data element separator and the segment terminator. M TM 4/4 Must use M ID 1/1 Must use M ID 5/5 Must use M N0 9/9 Must use M ID 1/1 Must use M ID 1/1 Must use M 1/1 Must use Example: ISA*00* *00* *ZZ*123456789 *01*131662855 *050504*1702*U*00401*000000070*0*P*>~ Version 1.4 EDI Implementation Guide: ANSI X12 997 004010 Page 8
Functional Group Header Pos: Max: 1 GS Not Defined - Mandatory Loop: N/A Elements: 8 User Option (Usage): Must use To indicate the beginning of a functional group and to provide control information. Element Summary: Ref ID Element Name Req Type Min/Max Usage GS01 479 Functional Identifier Code Description: Code identifying a group of application-related transaction sets. M ID 2/2 Must use Code Name FA Functional Acknowledgment (997) GS02 142 Application Sender's Code M AN 2/15 Must use Description: Code identifying party sending transmission; codes agreed to by trading partners. GS03 124 Application Receiver's Code M AN 2/15 Must use Description: Code identifying party receiving transmission; codes agreed to by trading partners. GS04 373 Date M DT 8/8 Must use Description: Date expressed as CCYYMMDD. GS05 337 Time M TM 4/8 Must use Description: Time expressed in 24-hour clock time as follows: HHMM, or HHMMSS, or HHMMSSD, or HHMMSSDD; where H = hours (00-23), M = minutes (00-59), S = integer seconds (00-59) and DD = decimal seconds. Decimal seconds are expressed as follows: D = tenths (0-9) and DD = hundredths (00-99). GS06 28 Group Control Number M N0 1/9 Must use Description: Assigned number originated and maintained by the sender. GS07 455 Responsible Agency Code Description: Code identifying the issuer of the standard; this code is used in conjunction with Data Element 480. M ID 1/2 Must use Version 1.4 EDI Implementation Guide: ANSI X12 997 004010 Page 9
GS08 480 Version / Release / Industry Identifier Code Description: Code indicating the version, release, sub release, and industry identifier of the EDI standard being used, including the GS and GE segments. If code in DE455 in GS segment is X, then in DE 480 positions 1-3 are the version number; positions 4-6 are the release and sub release level of the version; and positions 7-12 are the industry or trade association identifiers (optionally assigned by user); if code in DE455 in GS segment is T, then other formats are allowed. M AN 1/12 Must use Code Name 004010 Draft Standards Approved for Publication by ASC X12 Procedures Review Board through October 1997 Semantics: 1. GS04 is the group date. 2. GS05 is the group time. 3. The data interchange control number GS06 in this header must be identical to the same data element in the associated functional group trailer, GE02. Comments: 1. A functional group of related transaction sets, within the scope of X12 standards, consists of a collection of similar transaction sets enclosed by a functional group header and a functional group trailer. Example: GS*FA*123456789*131662855*20050504*1702*54*X*004010~ Version 1.4 EDI Implementation Guide: ANSI X12 997 004010 Page 10
Transaction Set Header Pos: 010 Max: 1 ST Heading - Mandatory Loop: N/A Elements: 2 User Option (Usage): Must use To indicate the start of a transaction set and to assign a control number. Element Summary: Ref ID Element Name Req Type Min/Max Usage ST01 143 Transaction Set Identifier Code M ID 3/3 Must use Description: Code uniquely identifying a Transaction Set. ST02 329 Transaction Set Control Number Description: Identifying control number that must be unique within the transaction set functional group assigned by the originator for a transaction set. M AN 4/9 Must use 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). Example: ST*997*0054~ Version 1.4 EDI Implementation Guide: ANSI X12 997 004010 Page 11
AK1 Functional Group Response Header Pos: 020 Max: 1 Heading - Mandatory Loop: N/A Elements: 2 User Option (Usage): Must use To start acknowledgment of a functional group. Element Summary: Ref ID Element Name Req Type Min/Max Usage AK101 479 Functional Identifier Code M ID 2/2 Must use Description: Code identifying a group of application-related transaction sets. AK102 28 Group Control Number Description: Assigned number originated and maintained by the sender. M N0 1/9 Must use 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. Example: AK1*PS*42~ Version 1.4 EDI Implementation Guide: ANSI X12 997 004010 Page 12
Loop AK2 Pos: 030 Repeat: 999999 Optional Loop: AK2 Elements: N/A To start acknowledgment of a single transaction set. Loop Summary: Pos ID Segment Name Req Max Use Repeat Usage 030 AK2 Transaction Set Response Header O 1 Used 040 Loop AK3 O 999999 Used 060 AK5 Transaction Set Response Trailer M 1 Must use Version 1.4 EDI Implementation Guide: ANSI X12 997 004010 Page 13
AK2 Transaction Set Response Header Pos: 030 Max: 1 Heading - Optional Loop: AK2 Elements: 2 User Option (Usage): Used To start acknowledgment of a single transaction set. Element Summary: Ref ID Element Name Req Type Min/Max Usage AK201 143 Transaction Set Identifier Code M ID 3/3 Must use Description: Code uniquely identifying a Transaction Set. AK202 329 Transaction Set Control Number Description: Identifying control number that must be unique within the transaction set functional group assigned by the originator for a transaction set. M AN 4/9 Must use 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. Example: AK2*830*42~ Version 1.4 EDI Implementation Guide: ANSI X12 997 004010 Page 14
Loop AK3 Pos: 040 Repeat: 999999 Optional Loop: AK3 Elements: N/A To report errors in a data segment and identify the location of the data segment. Loop Summary: Pos ID Segment Name Req Max Use Repeat Usage 040 AK3 Data Segment Note O 1 Used 050 AK4 Data Element Note O 99 Used Version 1.4 EDI Implementation Guide: ANSI X12 997 004010 Page 15
Data Segment Note Pos: 040 Max: 1 AK3 Heading - Optional Loop: AK3 Elements: 4 User Option (Usage): Used To report errors in a data segment and identify the location of the data segment. Element Summary: Ref ID Element Name Req Type Min/Max Usage AK301 721 Segment ID Code M ID 2/3 Must use Description: Code defining the segment ID of the data segment in error. AK302 719 Segment Position in Transaction Set M N0 1/6 Must use Description: 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 AN 1/6 Used Description: The loop ID number given on the transaction set diagram is the value for this data element in segments LS and LE. AK304 720 Segment Syntax Error Code Description: Code indicating error found based on the syntax editing of a segment. O ID 1/3 Used Version 1.4 EDI Implementation Guide: ANSI X12 997 004010 Page 16
Data Element Note Pos: 050 Max: 99 AK4 Heading - Optional Loop: AK3 Elements: 4 User Option (Usage): Used To report errors in a data element or composite data structure and identify the location of the data element. Element Summary: Ref ID Element Name Req Type Min/Max Usage AK401 C030 Position in Segment M Comp Must use Description: Code indicating the relative position of a simple data element or the relative position of a composite data structure combined with the relative position of the component data element within the composite data structure in error. The count starts with 1 for the simple data element or composite data structure immediately following the segment ID. 722 Element Position in Segment M N0 1/2 Must use Description: Used to indicate the relative position of a simple data element or the relative position of a composite data structure with the relative position of the component within the composite data structure in error. In the data segment, the count starts with 1 for the simple data element or composite data structure immediately following the segment ID. 1528 Component Data Element Position in O N0 1/2 Used Composite Description: To identify the component data element position within the composite that is in error. AK402 725 Data Element Reference Number O N0 1/4 Used Description: Reference number used to locate the data element in the Data Element Dictionary. AK403 723 Data Element Syntax Error Code M ID 1/3 Must use Description: Code indicating the error found after syntax edits of a data element. AK404 724 Copy of Bad Data Element Description: This is a copy of the data element in error. O AN 1/99 Used Semantics: 1. In no case shall a value be used for AK404 that would generate a syntax error, e.g., an invalid character. Version 1.4 EDI Implementation Guide: ANSI X12 997 004010 Page 17
AK5 Transaction Set Response Trailer Pos: 060 Max: 1 Heading - Mandatory Loop: AK2 Elements: 6 User Option (Usage): Must use To acknowledge acceptance or rejection and report errors in a transaction set. Element Summary: Ref ID Element Name Req Type Min/Max Usage AK501 717 Transaction Set Acknowledgment Code M ID 1/1 Must use Description: Code indicating accept or reject condition based on the syntax editing of the transaction set. AK502 718 Transaction Set Syntax Error Code O ID 1/3 Used Description: Code indicating error found based on the syntax editing of a transaction set. AK503 718 Transaction Set Syntax Error Code O ID 1/3 Used Description: Code indicating error found based on the syntax editing of a transaction set. AK504 718 Transaction Set Syntax Error Code O ID 1/3 Used Description: Code indicating error found based on the syntax editing of a transaction set. AK505 718 Transaction Set Syntax Error Code O ID 1/3 Used Description: Code indicating error found based on the syntax editing of a transaction set. AK506 718 Transaction Set Syntax Error Code Description: Code indicating error found based on the syntax editing of a transaction set. O ID 1/3 Used Example: AK5*A~ Version 1.4 EDI Implementation Guide: ANSI X12 997 004010 Page 18
AK9 Functional Group Response Trailer Pos: 070 Max: 1 Heading - Mandatory Loop: N/A Elements: 9 User Option (Usage): Must use 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. Element Summary: Ref ID Element Name Req Type Min/Max Usage AK901 715 Functional Group Acknowledge Code M ID 1/1 Must use Description: Code indicating accept or reject condition based on the syntax editing of the functional group. AK902 97 Number of Transaction Sets Included M N0 1/6 Must use Description: Total number of transaction sets included in the functional group or interchange (transmission) group terminated by the trailer containing this data element. AK903 123 Number of Received Transaction Sets M N0 1/6 Must use Description: Number of Transaction Sets received. AK904 2 Number of Accepted Transaction Sets M N0 1/6 Must use Description: Number of accepted Transaction Sets in a Functional Group. AK905 716 Functional Group Syntax Error Code O ID 1/3 Used Description: Code indicating error found based on the syntax editing of the functional group header and/or trailer. AK906 716 Functional Group Syntax Error Code O ID 1/3 Used Description: Code indicating error found based on the syntax editing of the functional group header and/or trailer. AK907 716 Functional Group Syntax Error Code O ID 1/3 Used Description: Code indicating error found based on the syntax editing of the functional group header and/or trailer. AK908 716 Functional Group Syntax Error Code O ID 1/3 Used Description: Code indicating error found based on the syntax editing of the functional group header and/or trailer. AK909 716 Functional Group Syntax Error Code Description: Code indicating error found based on the syntax editing of the functional group header and/or trailer. O ID 1/3 Used Version 1.4 EDI Implementation Guide: ANSI X12 997 004010 Page 19
Comments: 1. If AK901 contains the value "A" or "E", then the transmitted functional group is accepted. ZF Group North American Operations Example: AK9*A*1*1*1~ Version 1.4 EDI Implementation Guide: ANSI X12 997 004010 Page 20
Transaction Set Trailer Pos: 080 Max: 1 SE Heading - Mandatory Loop: N/A Elements: 2 User Option (Usage): Must use To indicate the end of the transaction set and provide the count of the transmitted segments (including the beginning (ST) and ending (SE) segments). Element Summary: Ref ID Element Name Req Type Min/Max Usage SE01 96 Number of Included Segments M N0 1/10 Must use Description: Total number of segments included in a transaction set including ST and SE segments. SE02 329 Transaction Set Control Number Description: Identifying control number that must be unique within the transaction set functional group assigned by the originator for a transaction set. M AN 4/9 Must use Comments: 1. SE is the last segment of each transaction set. Example: SE*6*0054~ Version 1.4 EDI Implementation Guide: ANSI X12 997 004010 Page 21
Functional Group Trailer Pos: Max: 1 GE Not Defined - Mandatory Loop: N/A Elements: 2 User Option (Usage): Must use To indicate the end of a functional group and to provide control information. Element Summary: Ref ID Element Name Req Type Min/Max Usage GE01 97 Number of Transaction Sets Included M N0 1/6 Must use Description: Total number of transaction sets included in the functional group or interchange (transmission) group terminated by the trailer containing this data element. GE02 28 Group Control Number Description: Assigned number originated and maintained by the sender. M N0 1/9 Must use Semantics: 1. The data interchange control number GE02 in this trailer must be identical to the same data element in the associated functional group header, GS06. Comments: 1. The use of identical data interchange control numbers in the associated functional group header and trailer is designed to maximize functional group integrity. The control number is the same as that used in the corresponding header. Example: GE*1*54~ Version 1.4 EDI Implementation Guide: ANSI X12 997 004010 Page 22
Interchange Control Trailer Pos: Max: 1 IEA Not Defined - Mandatory Loop: N/A Elements: 2 User Option (Usage): Must use To define the end of an interchange of zero or more functional groups and interchange-related control segments. Element Summary: Ref ID Element Name Req Type Min/Max Usage IEA01 I16 Number of Included Functional Groups M N0 1/5 Must use Description: A count of the number of functional groups included in an interchange. IEA02 I12 Interchange Control Number Description: A control number assigned by the interchange sender. M N0 9/9 Must use Example: IEA*1*000000070~ Version 1.4 EDI Implementation Guide: ANSI X12 997 004010 Page 23