|
[EDI-L Mailing List Archive Home]
[Message List]
[Reply To This Message]
RE: APERAK transaction
Since APERAK is the "Application error and acknowledgement message", this is
referring to application-level errors which generally would not be handled
automatically by your translator (of course, your mileage may vary). The
received data would be processed by the translator and passed to the application
which would perform application-level edits which would have to be translated
back into an APERAK for shipment (implying a map from the app edits to APERAK).
As such it's closer in use and intent to X12's 824. You might say CONTRL is to
997 as APERAK is to 824.
Hope that helps.
Best regards,
Bill Chessman
Inovis(tm)
-----Original Message-----
From: Gina Coomer [mailto:
Sent: Thursday, July 08, 2004 1:15 PM
To:
Subject: [EDI-L] APERAK transaction
Dear group
I have been informed that we need to send an APERAK transaction for our
inbound EDIFACT messages. Has anyone worked with this message?
The standards define this as 'Application and Error message' which sounds
similar to the CONTRL message. Does this need to be mapped or should the
translator automatically generate this? Any sample data might make this
more clear.
Thank you in advance for any help.
Gina Ann Coomer
Smith Heating Supplies
[Non-text portions of this message have been removed]
.
Please use the following Message Identifiers as your subject prefix: <SALES>,
<JOBS>, <LIST>, <TECH>, <MISC>, <EVENT>, <OFF-TOPIC>
Access the list online at: http://groups.yahoo.com/group/EDI-L
Yahoo! Groups Links
|
 |
Subscribe in XML format
| RSS 2.0 |
|
| Atom 0.3 |
|
|
Cart
