997 Functional Acknowledgement

Transcription

1 Global Procurement Functional Acknowledgement 1 of 11 12/17/2002 7:41 PM 997 Functional Acknowledgement Segment Usage Becoming an IBM Supplier Publications e-procurement Feedback Table 5. Segment usage, requirements, max use and loop infmation. Pos Seg Description Req Max Use Loop Repeat 010 *ST Header M *AK1 Functional Group Response Header M 1 > BEGIN AK2 LOOP > *AK2 Response Header O 1 >> BEGIN AK3 LOOP >> *AK3 Data Segment Note O AK4 Note O 99 >> END AK3 LOOP >> 060 AK5 Response Trailer M 1 > END AK2 LOOP > 070 AK9 Functional Group Response M 1 Trailer 080 SE Trailer M 1 Notes * (ST) * (ST) * (ST) These acknowledgments shall not be acknowledged, thereby preventing an endless cycle of acknowledgments of acknowledgments. 0 The Functional Group Header Segment (GS) is used to start the envelope f the Functional Acknowledgment s. 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; therefe, 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 per acknowledged functional group. * (AK1) AK1 is used to respond to the functional group header and to start the acknowledgement f a functional group. There shall be one AK1 segment f the functional group that is being acknowledged.

2 2 of 11 12/17/2002 7:41 PM * (AK2) AK2 is used to start the acknowledgement of a transaction set within the received functional group. The AK2 segments shall appear in the same der as the transaction sets in the functional group that has been received and is being acknowledged. Comments * (AK3) The data segments of this standard are used to rept the results of the syntactical analysis of the functional groups of transaction sets; they rept the extent to which the syntax complies with the standards f transaction sets and functional groups. They do not rept on the semantic meaning of the transaction sets (f example, on the ability of the receiver to comply with the request of the sender). Header/Detail/Summary Infmation ST - Header To indicate the start of a transaction set and to assign a control number. Table 6. ST - Header ST Name ST Control Number Semantic Notes Req. Data M Z 3/3 Description 997 X12.20 Functional Acknowledgement M AN 4/9 01 The transaction set identifier (ST01) used by the translation routines of the interchange partners to select the appropriate transaction set definition. AK1 - Functional Group Response Header To start acknowledgment of a functional group. Table 7. AK1 - Functional Group Response Header

3 3 of 11 12/17/2002 7:41 PM Name AK Functional Identifier AK Group Control Number Semantic Notes Req. Data Description M Z 2/2 See Appendix A M Z N0 1/ AK101 is the functional found in the GS segment (GS01) in the functional group being acknowledged. AK102 is the functional group control number found in the GS segment in the functional group being acknowledged. AK2 - Response Header To start acknowledgment of a single transaction set. Table 8. AK2 - Response Header Name Req. Data AK M Z 3/3 Identifier AK M Z AN 4/9 Control Number Semantic Notes Description AK201 is the transaction set found in the ST segment (ST01) in the transaction set being acknowledged. AK202 is the transaction set control number found in the ST segment in the transaction set being acknowledged. AK3 - Data Segment Note To rept errs in a data segment and to identify the location of the data segment. Table 9. AK3 - Data Segment Note

4 4 of 11 12/17/2002 7:41 PM Name Req. Data Description AK Segment M 2/3 AK Segment Position M N0 1/6 in AK Loop Identifier O AN 1/4 AK Segment Syntax Err O 1/3 1 Unrecognized segment 2 Unexpected segment 3 Mandaty segment missing 4 Loop Occurs Over Maximum Times 5 Segment Exceeds Maximum Use 6 Segment Not in Defined Transaction Set 7 Segment Not in Proper Sequence AK Segment Syntax Err O 1/3 Same as above - Element 720 AK Segment Syntax Err O 1/3 Same as above - Element 720 AK Segment Syntax Err O 1/3 Same as above - Element 720 AK Segment Syntax Err O 1/3 Same as above - Element 720 AK4 - Note To rept errs in a data element and to identify the location of the data element. Table 10. AK4 - Note

5 5 of 11 12/17/2002 7:41 PM AK AK AK AK Name Element Position in Segment Reference Number Copy of Bad Data Element Req. Data M N0 1/2 O N0 1/4 M 1/3 Description 1 Mandaty data element missing 2 Conditional required data element missing. 3 Too many data elements. 4 Data element too sht. 5 Data element too long. 6 Invalid character in data element. 7 Invalid code value. 8 Invalid Date 9 Invalid Time 10 Exclusion Condition Violated O AN 1/99 AK5 - Response Trailer To acknowledge acceptance rejection and to rept errs in a transaction set. Table 11. AK5 - Response Trailer

6 6 of 11 12/17/2002 7:41 PM AK AK AK AK AK AK Name Req. Data Acknowledgment M 1/1 Description A Accepted E Accepted, But Errs Were Noted. M Rejected, Message Authentication (MAC) Failed R Rejected X Rejected, Content After Decryption Could Not Be Analyzed AK9 - Functional Group Response Trailer To acknowledge acceptance rejection of a functional group and rept the number of included transaction sets from the iginal trailer, the accepted sets, and the received sets in this functional group. Table 12. AK9 - Functional Group Response Trailer

7 7 of 11 12/17/2002 7:41 PM AK Name Functional Group Acknowledge AK Number of s Included AK Number of Received s AK904 2 Number of Accepted s AK Functional Group AK Functional Group AK Functional Group AK Functional Group AK Functional Group Semantic Notes Req. Data M 1/1 A E M P R X M N0 1/6 M N0 1/6 M N0 1/6 Description Accepted Accepted, But Errs Were Noted. Rejected, Message Authentication (MAC) Failed Partially Accepted, At Least One Was Rejected Rejected Rejected, Content After Decryption Could Not Be Analyzed 01 If AK901 is 'A' 'E', then the transmitted functional group is accepted. If AK901 is 'R', then the transmitted group is rejected. APPENDIX A Validation Tables

8 8 of 11 12/17/2002 7:41 PM The following is a list of validation tables used in this Functional Acknowledgement (997) Subset version 003 release 040. Table : 479X340 Description: Functional Identifier Length of Data Description Length of Entries of Entries Description 02 CH Y 63 Entry Description AG Acceptance/Rejection Advice (999) and Application Advice (824) AN Return Merchandise Authization and Notification (180) AR Warehouse Stock Transfer Shipment Advice (943) AW Warehouse Inventy Adjustment Advice (947) BS Shipment and Billing Notice (857) CA Purchase Order Change Acknowledgment/Request - Seller Initiated (865) CI Consolidated Service Invoice/Statement (811) DX Direct Exchange Delivery and Return Infmation (894, 895) FA Functional Acknowledgment (997) GC Damage Claim s (920, 924, 925, 926) IA Air Freight Details and Invoice (110) IB Inventy Inquiry/Advice (846) IM Mot Carrier Freight Details and Invoice (210) IN Invoice Infmation (810,819) LB Lockbox (823) MI Mot Carrier Shipment Status Inquiry (213) MS Material Safety Data Sheet (848) OW Warehouse Shipping Order (940) PC Purchase Order Change Request - Buyer Initiated (860) PD Product Activity Data (852) PO Purchase Order (850) PR Purchase Order Acknowledgement (855) PS Planning Schedule with Release Capability (830) PT Product Transfer and Resale Rept (867) QM Transptation Carrier Shipment Status Message (214)

9 9 of 11 12/17/2002 7:41 PM RA Payment Order/Remittance Advice (820) RC Receiving Advice/Acceptance Certificate (861) RQ Request f Quotation (840) and Contract Award (836) RR Response to Request F Quotation (843) RS Order Status Infmation (869, 870) RT Rept of Test Results (863) SA Air Shipment Infmation (104) SC Price/Sales Catalog (832) SH Ship Notice/Manifest (856) SM Mot Carrier Shipment Infmation (204) SP Specifications/Technical Infmation (841) SS Shipping Schedule (862) SW Warehouse Shipping/Delivery Infmation (945, 946) TD Trading Partner Profile (838) TF Electronic Filing of Tax Return Data (813) TX Text Message (864) UC Unifm Commercial Filing (154) WA Product Service s (140, 141, 142, 143) Table : 716X340 Description: Functional Group Length of Data Description Length of Entries of Entries Description 03 CH Y 63 Entry Description 1 Functional Group Not Suppted 2 Functional Group Version Not Suppted 3 Functional Group Trailer Missing 4 Group Control Number in the Functional Group Header and Trailer 5 Number of Included s Does Not Match Actual Count 6 Group Control Number Violates Syntax 10 Authentication Key Name Unknown 11 Encryption Key Name Unknown 12 Requested Service (Authentication Encryption) Not Available 13 Unknown Security Recipient

10 10 of 11 12/17/2002 7:41 PM 14 Unknown Security Originat 15 Syntax Err in Decrypted Text 16 Security Not Suppted 17 Increct Message Length (Encryption Only) 18 Message Authentication Failed 19 S1E Security End Segment Missing f S1S Security Start Segment 20 S1S Security Start Segment Missing f S1E End Segment 21 S2E Security End Segment Missing f S2S Security Start Segment 22 S2S Security Start Segment Missing f S2E Security End Segment Table : 718X340 Description: Length of Data Description Length of Entries of Entries Description 03 CH Y 63 Entry Description 1 Not Suppted 2 Trailer Missing 3 Control Number in Header and Trailer Do Not Match 4 Number of Included Segments Does Not Match Actual Count 5 One Me Segments in Err 6 Missing Invalid Identifier 7 Missing Invalid Control Number 8 Authentication Key Name Unknown 8 Authentication Key Name Unknown 9 Encryption Key Name Unknown 10 Requested Service (Authentication Encrypted) Not Available 11 Unknown Security Recipient 12 Increct Message Length (Encryption Only) 13 Message Authentication Failed 15 Unknown Security Originat 16 Syntax Err in Decrypted Text 17 Security Not Suppted

11 11 of 11 12/17/2002 7:41 PM 19 S1E Security End Segment Missing f S1S Security Start Segment 20 S1S Security Start Segment Missing f S1E Security End Segment 21 S2E Security End Segment Missing f S2S Security Start Segment 22 S2S Security Start Segment Missing f S2E Security End Segment 23 Control Number Not Unique within the Functional APPENDIX B Source s There are no source codes f this document. Update / Change Summary Updated level of HyperText Markup Language (HTML) f use on the Wld Wide Web. [ Top of Page Previous Page Table of Contents ]