We actually have one Vendor that sends us 45,000 Invoices each week (1 transmission). We Process the EDI file through TLE into one large file (45.000 IDOCs) we then have a UNIX script that splits these into 5MB files. The reason for this is because we use MQ Series to post these to SAP and MQ has a size limit, therefore we breakdown the file to manageable size(s). Our one file now becomes 15 files with X number of IDOC's...The UNIX script actual reads the file size....then breaks it down and appends 1 IDOC at a time.
Question I have though is was the EDI file from the customer in ISA sequence? What if your translator had sequence checking on, would this have helped... From: "Hurd, Richard [SLCUS]" <[email protected]> To: "Leah Halpin" <[email protected]> Cc: "Steven Santillo" <[email protected]>, <[email protected]> Date: 06/08/2011 11:48 AM Subject: Re: [EDI-L] Need your comments... Sent by: [email protected] We too send one order per idoc. Where we have challenges is over 999 lines in an order and orders that span a truck (operationally, homie don't do that.). Our order creation logic splits orders to multiple sales orders for over 999 lines; over one truckload (cube and/or weight) and we also create one order for each sdq destination in a crossdock order (with a special order type of ZCDO.) --- Sent from my iPhone. Replies may be delayed. On Jun 8, 2011, at 9:15 AM, "Leah Halpin" <[email protected]> wrote: > Hi Steven, > I agree that this is an extremely rare event, perhaps a conversation between your TP and your wigged out management is in order. And, since the problem is in SAP, use SAP to solve it, after all, if you really did get 22K orders, wouldn't that be GREAT for business? Your ERP system is the place to make business logic work, not your EDI system. > > > I do have one thought, which is to ask if you really sent one "file" to SAP. The way we do it is to create a separate IDOC for each order. That way, SAP has, in this case, 22,600 IDOCs to deal with, not one. I'm not an SAP expert, but I think someone could perhaps write a batch process to filter/deal with large numbers of PO's/IDOCs in SAP. I know at a former position, we wrote a batch process for one TP who regularly sent a LOT of data (not 22K, but upwards of 1-2K) and a batch process was written to take care of those particular IDOCs at 3am. > > > Good luck, > > > Leah > > > > ________________________________ > From: Steven Santillo <[email protected]> > To: [email protected] > Sent: Wednesday, June 8, 2011 8:45 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? > > > > > [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 > > > > [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/
