report errors in incoming edi to sender

[GoogleCodeExporter]

When receiving many edi-messages, receiving 'wrong' edi-message is unavoidable 
(when receiving 100.000edi-files per month, with 0.1% errors, this is 3 errors 
per day).
You want to be able to report this to sender. (eg email, but could this alo be 
a x12 997?)
- identify partner
- identify message (editype, messagetype, timestamp, messageID, etc)
- errors should be clear...(that is a nice one!)
- get communication/communicationID; eg via partner-lookup
This is certainly not always possible....send report to admin in  these cases.

Original issue reported on code.google.com by hjebb...@gmail.com on 6 Sep 2013 at 5:36

[GoogleCodeExporter]

I think actually bots errors are mostly quite clear... but not to the 
non-technical person. So if the partner has a person who understands EDI this 
is a good option. But often I find I need to enhance the error report with some 
explanation, examples of how to fix it, etc.

Original comment by mjg1964 on 22 Dec 2013 at 12:03

[GoogleCodeExporter]

yes.
want I want to realize is to send 997 or errorreports back to to the
edi-partners.
this is what USretailers do.
So I am trying to have eg the partner-information available (in ta-table)
under 'most' errors.
(this will never work 100% of course).

basically a script runs last in the run, to collect emails/997's per
partner.
uput is highly customized (eg have name of retailer in email, links to
detailed information in the errortype, etc.

Original comment by hjebb...@gmail.com on 22 Dec 2013 at 7:20

[GoogleCodeExporter]

For incoming edi several types of errors can occur:
1  low-level errors, eg separator problems, non-valid xml
2  fatal parse errors, eg unknown segment, segment at wrong place
3. non-fatal parse errors: bots understands the message, but there are errors: 
eg to many repeats, field too long.
4. Errors generated in mapping script
5. Errors when generating outgoing messages

Goal is to retrieve better information from edi-files for reporting (email 
reports, 997).
Improvements:
- type-3 errors set right partnerID's & references.
- type-2 errors for x12/edifact set partnerID's & references.

Original comment by hjebb...@gmail.com on 28 Dec 2013 at 1:04

• Changed state: Started

[GoogleCodeExporter]

Original comment by hjebb...@gmail.com on 14 Jan 2014 at 12:25

• Changed title: report errors in incoming edi to sender

[GoogleCodeExporter]

Original comment by hjebb...@gmail.com on 10 Sep 2014 at 2:43

• Changed state: Done