Hi Matt, I've been meaning to reply to this. I understand what you're saying, but that is precisely the purpose of the 997. Now, neither I nor anyone else would expect the 997 to give a segment by segment and element by element description of what is wrong with the inbound data. However; if the data has a good ISA/GS/ST, you can tell what type of transaction it is and who it's from. If it also has a valid SE/GE/IEA, then, I hate to say it, but it's your translator that's the problem. The 997 should spit out with whatever the first error is that it encounters. You say the segments are out of order, well, that means the first error (which should go into the 997) is either "missing mandatory segment MEA" or "unexpected segment MEA" (for example). In fact, I just checked and even if there's no SE, there's a code for that in the AK2 for that, as well.
So, I feel for you with the bad data people, but you need to look to your vendor, data such as you've described shouldn't crash a good translator. Good Luck, Leah On Thu, Jan 8, 2009 at 4:46 PM, Matt Shults <matrixe...@yahoo. com <mailto:matrixeyes% 40yahoo.com> > wrote: > The ISA and GS are good but things go south rapidly on the first ST, > segments out of order, HL loops all fouled up -- the partner has had a > history of intermittant data quality, but recently had some personnel > turnover and something was changed on their side. One suspects if they have > a tool they are mis-using it. > > As I say we handle it now with a simple automated email, but I was thinking > it would be nice to provide > some more technical feedback like a 997. > > I since heard back from the vendor went back, and tried saving the 997 > anyway, all I got was a mal-formed 997 since the framework was never able to > finish parsing the doc. I could put more work into it but I think the > automated email notification combined with the missing 997 will have to > suffice. > > Some very good feedback, I thank you all! > > Matt > > > > ------------ --------- --------- >> >> >> >> >> >> >> To: ed...@yahoogroups. com <mailto:EDI- L%40yahoogroups. com> >> From: Matt Shults <matrixe...@yahoo. com <mailto:matrixeyes% 40yahoo.com> > >> Date sent: Thu, 8 Jan 2009 11:27:58 -0800 (PST) >> Subject: [EDI-L] <TECH> How to responde to severly >> mal-formed EDI files >> when we cannot gen a 997 >> >> > We use a product from EDIdEV which is a programmer framework tool for >> > EDI. When we receive an inbound file that is so mal-formed, the >> > framework throws a general error and is not able to generate a 997. >> > Right now we catch that and send an email to the TP technical contact >> > about the file. >> > >> > I'm wondering is there a better approach? If we were to fabricate a 997 >> for such a situation I'm not even sure what we would populate it with since >> we can't parse a single transaction. >> > >> > Thanks! >> > Matt Shults >> > <TECH> >> > >> > >> > >> > >> > ------------ --------- --------- ------ >> > >> > ... >> > Please use the following Message Identifiers as your subject prefix: >> <SALES>, <JOBS>, <LIST>, <TECH>, <MISC>, <EVENT>, <OFF-TOPIC> >> > >> > Job postings are welcome, but for job postings or requests for work: >> <JOBS> IS REQUIRED in the subject line as a prefix.Yahoo! Groups Links >> > >> > >> > >> > >> > __________ Information from ESET NOD32 Antivirus, version of virus >> signature database 3751 (20090108) __________ >> > >> > The message was checked by ESET NOD32 Antivirus. >> > >> > http://www.eset. com >> > >> > >> > >> >> Earl Wertheimer >> ea...@spe-edi. com <mailto:earlw% 40spe-edi. com> >> http://www.spe- edi.com >> >> >> ------------ --------- --------- ------ >> >> ... >> Please use the following Message Identifiers as your subject prefix: >> <SALES>, <JOBS>, <LIST>, <TECH>, <MISC>, <EVENT>, <OFF-TOPIC> >> >> Job postings are welcome, but for job postings or requests for work: >> <JOBS> IS REQUIRED in the subject line as a prefix.Yahoo! Groups Links >> >> >> >> > > [Non-text portions of this message have been removed] [Non-text portions of this message have been removed] [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> Job postings are welcome, but for job postings or requests for work: <JOBS> IS REQUIRED in the subject line as a prefix.Yahoo! Groups Links <*> To visit your group on the web, go to: http://groups.yahoo.com/group/EDI-L/ <*> Your email settings: Individual Email | Traditional <*> To change settings online go to: http://groups.yahoo.com/group/EDI-L/join (Yahoo! ID required) <*> To change settings via email: mailto:[email protected] mailto:[email protected] <*> To unsubscribe from this group, send an email to: [email protected] <*> Your use of Yahoo! Groups is subject to: http://docs.yahoo.com/info/terms/
