We use the 824 for our Purchasing application and it has been very useful
in letting our vendors know when their invoices had errors and were not
paid, and why they were not paid. It is driven by the application, not an
EDI requirement to know the status of the 810. (In our case the 857). For
that we, of course, use the 997.
Chris Kelly-Winslow
Computer Systems Programmer/Analyst Sr.
United States Postal Service
(650)377-1392
[EMAIL PROTECTED]
______________________________ Reply Separator _________________________________
Subject: RE: EDI 810 question
Author: [EMAIL PROTECTED] at INTERNET
Date: 6/1/01 2:05 PM
The 997 is a functional response to any X12 document... it's purpose is to
communicate the syntactical validity of the document sent against either the
dictionary or IC.. however, semantic information (business specific) as
provided in an 855 for an 850 is not available in a specific transaction
against the 810.
But... there is a rarely used transaction: the 824, that was created to be
used in this manner... basically it can be used to return back information
about the received document from a business level. I believe the looseness
of this transaction was cause for its lack of use... basically... it can
defeat the purpose of an automated and parse able document, since you send
mostly freehand text... but nonetheless, it's not bad...
Here is the specific 997 and 824 definitions, which I reread from time to
time just to refamiliarize myself with the inherit differences:
997 - Functional Acknowledgment:
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.
824 - Application Advice:
This Draft Standard for Trial Use contains the format and establishes the
data contents of the Application Advice Transaction Set (824) for use within
the context of an Electronic Data Interchange (EDI) environment. The
transaction set can be used to provide the ability to report the results of
an application system's data content edits of transaction sets. The results
of editing transaction sets can be reported at the functional group and
transaction set level, in either coded or free-form format. It is designed
to accommodate the business need of reporting the acceptance, rejection or
acceptance with change of any transaction set. The Application Advice should
not be used in place of a transaction set designed as a specific response to
another transaction set (e.g., purchase order acknowledgement sent in
response to a purchase order).
Cheers!
~Rob
Robert Fox
Director of Product Development
Softshare
EM: [EMAIL PROTECTED]
PH:(805) 899-2366
FX: (805) 882-2599
-----Original Message-----
From: Scott Rogers [mailto:[EMAIL PROTECTED]]
Sent: Friday, June 01, 2001 9:55 AM
To: Scott Meade; [EMAIL PROTECTED]
Subject: re: EDI 810 question
Greetings,
The 997 is the Functional Acknowledgement for an 810. There is not a
specific transaction set for the 810 versus a PO.
Scott Rogers
[EMAIL PROTECTED]
>> Attached File: c:\program files\goldmine\MailBox\Attach\~gmE03A.htm
------ XML/edi Group Discussion List ------
Homepage = http://www.XMLedi-Group.org
Unsubscribe = send email to: [EMAIL PROTECTED]
Leave the subject and body of the message blank
Questions/requests: [EMAIL PROTECTED]
To receive only one message per day (digest format)
send the following message to [EMAIL PROTECTED],
(leave the subject line blank)
digest xmledi-group your-email-address
To join the XML/edi Group complete the form located at:
http://www.xmledi-group.org/xmledigroup/mail1.htm
------ XML/edi Group Discussion List ------
Homepage = http://www.XMLedi-Group.org
Unsubscribe = send email to: [EMAIL PROTECTED]
Leave the subject and body of the message blank
Questions/requests: [EMAIL PROTECTED]
To receive only one message per day (digest format)
send the following message to [EMAIL PROTECTED],
(leave the subject line blank)
digest xmledi-group your-email-address
To join the XML/edi Group complete the form located at:
http://www.xmledi-group.org/xmledigroup/mail1.htm
------ XML/edi Group Discussion List ------
Homepage = http://www.XMLedi-Group.org
Unsubscribe = send email to: [EMAIL PROTECTED]
Leave the subject and body of the message blank
Questions/requests: [EMAIL PROTECTED]
To receive only one message per day (digest format)
send the following message to [EMAIL PROTECTED],
(leave the subject line blank)
digest xmledi-group your-email-address
To join the XML/edi Group complete the form located at:
http://www.xmledi-group.org/xmledigroup/mail1.htm
