997 Functional Acknowledgement

To use the Functional Acknowledgment Transaction Set (997) in an EDI environment, follow the guidelines in this article.

Note: You can also view this information in Word format: Walmart.com Drop Ship Vendor_997_4010_EDI.docx

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 in 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 and 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

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) starts 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 acknowledgment 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 acknowledging 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.

Sample Spec 997 Files

---

FOR 850FOR 860FOR 850FOR 860

ISA*00* *00* *12*8478505336 *01*12571829*070426*1038*U*00401*000000008*0*P*>
GS*FA*8478505336*12571829*20070426*1038*8*X*004010
ST*997*0002
AK1*PO*000000009
AK2*850*0001
AK5*A
AK9*A*1*1*1
SE*6*0002
GE*1*8
IEA*1*000000008

ST Transaction Set Header

To indicate the start of a transaction set and to assign a control number
Usage Option: Must use

• Pos: 010
• Max: 1
• Heading – Mandatory
• Loop: N/A
• Elements: 2

Element Summary

AK1 Functional Group Response Header

To start acknowledgment of a functional group
Usage Option: Must use

• Pos: 020
• Max: 1
• Heading – Mandatory
• Loop: N/A
• Elements: 2

Element Summary

Segment Notes

• AK101 can be one of the following values:

• AG: Application Advice (824)

• IB: Inventory Inquiry/Advice (846)

• IN: Invoice Information (810, 819)

• PC: Purchase Order Change Request – Buyer Initiated (860)

• PO: Purchase Order (850)

• PR: Purchase Order Acknowledgement (855)

• SH: Ship Notice/Manifest (856)

AK2 Transaction Set Response Header

To start acknowledgment of a single transaction set
Usage Option: Must use

• Pos: 030
• Max: 1
• Heading – Optional
• Loop: AK2
• Elements: 2

Element Summary

Segment Notes

• AK201 can have one of the following values:

• 810: Invoice

• 824: Application Advice

• 846: Inventory Inquiry/Advice

• 850: Purchase Order

• 855: Purchase Order Acknowledgement

• 856: Ship Notice/Manifest

• 860: Purchase Order Change Request – Buyer Initiated

AK5 Transaction Set Response Trailer

To acknowledge acceptance or rejection and report errors in a transaction set
Usage Option: Must use

• Pos: 060
• Max: 1
• Heading – Mandatory
• Loop: AK2
• Elements: 1

Element Summary

Segment Notes

Each Transaction Set is marked as valid or rejected to indicate our validation results, but all transaction sets are rejected if the Group is rejected.

• AK501 can have one of the following values:

• A: Accepted

• W: Rejected, Assurance Failed Validity Tests

AK9 Functional Group Response Trailer

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. Usage Option: Must use

• Pos: 070
• Max: 1
• Heading – Mandatory
• Loop: N/A
• Elements: 4

Element Summary

Segment Notes

The group will never be partially accepted, even if some transaction sets were marked as accepted. The group is either fully accepted or fully rejected.

• AK901 can have one of the following values:

• A: Accepted

• R: Rejected

SE Transaction Set Trailer

To indicate the end of the transaction set and provide the count of the transmitted segments (including the beginning (ST) and ending (SE) segments)
Usage Option: Must Use

• Pos: 080
• Max: 1
• Heading – Mandatory
• Loop: N/A
• Elements: 2

Element Summary