I thought of that and should have added that it's not hard with UNIX shell scripting to narrow it down to files only from that customer and only 850's. This, of course, is a quick and dirty fix for a problem that will rarely happen. I have never experienced it, but then I move around a lot so don't necessarily see all of those types of issues.
Dave Records Records Consulting, LLC Phone: 616.583.0090 Email: [email protected] On Jun 8, 2011, at 9:41 AM, Brian Lehrhoff wrote: > My thoughts and position on items like this are pretty clear - we get the > mail, > we carry the mail, > we deliver the mail. Any edit or logic really belongs outside of the > translator. > > I like Dave's idea about file sizes, although another document may exceed the > max size for 500 850s. Another option would be to not automatically process > (1) > old ISA by number (turn on the Gentran check) or (2) old GS (ditto) or (3) do > some sort of routing by date (send to error if the document - not the > interchange - is older than ## days.) > > You now have a compelling reason to update the dup check. > > If you pass the idocs one at a time to SAP ... can you batch them, test in a > shell script, and route to error if the batch > ##? > > At least you know the stress tests worked :) > > Brian Lehrhoff, EA ([email protected]) > Messaging Consultant 201-913-4506 > Upgrade your Quickbooks for 20% off at http://ea.brianlehrhoff.com > Circular 230 Notice is located at http://ea.brianlehrhoff.com/230notice.html > > ________________________________ > From: Steven Santillo <[email protected]> > To: [email protected] > Sent: Wed, June 8, 2011 8:45:57 AM > 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? > > ------------------------------------ > > ... > 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] ------------------------------------ ... 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/
