>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. If you can identify the data as containing an ISA or an attempt at an ISA segment, you could return an interchage with a TA1 Interchange Acknowledgement segment with reject status and some applicable reason code. . If it's more malformed than that, then I think your only option is to wait for the sender to tell you he never got either TA1 or 997 Or fire up Ye Olde Telephone. Michael C. Mattias Tal Systems Inc. Racine WI [email protected] ------------------------------------ ... 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/
