Rachel, Excellent mantra, however, I don't think it's reasonable to expect your trading partners are suddenly going to resend several years worth of PO's. You can't allow for everything and it wasn't the translation/data content that was the issue. If you tried to make your code bullet proof, you would still be writing your first program. Also, I think the wisdom of PT Barnum applies here:“You Will Never Go Broke Underestimating the Intelligence of the American Public” – PT Barnum Or maybe we should keep in mind Mr. Murphy's law. Either way, some TP (or user), somewhere, somehow, is sure to F up your best written code, no matter how much you test. That's just human nature.
Leah ________________________________ From: Rachel Foerster & Associates <[email protected]> To: 'Steven Santillo' <[email protected]>; [email protected] Sent: Wednesday, June 8, 2011 12:33 PM Subject: RE: [EDI-L] Need your comments... Hardly a knee jerk reaction in my opinion. My personal mantra is that all programs that I code must be fault tolerant internally and then must never pass data or files to downstream programs that would cause that program to abend or go off into the wild blue yonder. Rachel Foerster 847-872-8070 From: [email protected] [mailto:[email protected]] On Behalf Of Steven Santillo Sent: Wednesday, June 08, 2011 7:46 AM To: [email protected] Subject: [EDI-L] Need your comments... We have a few hunderd EDI partners and receive a few thousand EDI files a day. Our application is SAP. The issue: one of our partners had a problem and passed us an 850 file with 22600 PO's. All their PO's from the last 3 years. Gentran Server Unix translated the file which took well over an hour and passed it to SAP. This file sucked the life out of SAP and it took about 12 hours to stablaize SAP. To me this was an extremely rare event but now managment wants EDI to check all files and not pass anyhting over to SAP if the file has more than 500 PO's. This is a knee jerk reaction. I don't feel the need to either check the count of BEG segments or EDI_DC segments and suspend files. Has this type of thing happened to anyone else? My thinking is that if we must add this check then SAP should not only check files size but PO dates. (dupe check didn't work because these POs from 2008-2010 were on another system and not brought over to SAP.) Any thoughts? [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: [email protected] [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/
