I use Sterling Integrator and I make my archives YYYY_MM and inside that by transID and Direction \\server\EDI_Archive\2011_06\850IB for instance, plus one Inbound_original and outbound_original so I have everything I get before and after I do anything to it. SI automatically creates folders as I create the names from process data so this is perpetual. Every 3 months or so I zip the folders so I only have 3 months unzipped. I keep roughly a year of data. It never fails as soon as I zip a month within days someone will ask me about something inside it, but its still easy to get to. I have a bunch of working folder in another main folder where I keep scripts, parms, temp working folders, chargebacks and a series of folders that will initiate particular actions on anything you drop in there. Any file that gets dumped in Translate_inbound for instance will be collected and fed to an EDI_Deenvelope process and anything that gets written to Pending_partner will get FTP'd to that partner. Everything that isn't FTP is AS2 of some sort, be it direct or with the VAN so I set them up to behave like the AS2 folders.
On Jun 29, 2011, at 7:59 PM, Rich Silva wrote: > Personally I like separating the Inbox, Outbox, Specs and Reports so > I have: > > . DOCSIN > > . DOCSOUT > > . REPORTS > > . GUIDES > > I know from past issues that I almost always am chasing an issue for a > specific Partner, so within the DOCSIN and DOCSOUT I have a folder > for each > Partner. > > . DOCSIN\WalMart > > . DOCSIN\Dillards > > or > > . DOCSOUT\PCWC > > . DOCSOUT\ODW > > For awhile I had considered further breaking each of those folders > down by > Document like: > > . DOCSIN\WalMart\850 > > . DOCSIN\WalMart\860 > > . DOCSIN\WalMart\816 > > But I abandoned that as it usually seemed that research into a > specific > issue often touched more than one document from the Partner in a > day, so > having them in a single folder was good. > > Further, my "Incoming Document Names" tend to be very "simple" (e.g. > WalMart.850.txt), but my outgoing documents have (at least) the date > builtin > (e.g. PWCW.945.<CYMD>.txt) > > Oh, and I don't think the question was vague. Suggested asked for. > Suggestions given. Its up to the receiver of advice to take it or > not. and > to apply it as they might. > > From: [email protected] [mailto:[email protected]] On Behalf > Of > thatoneguyeric > Sent: Wednesday, June 29, 2011 11:03 AM > To: [email protected] > Subject: [EDI-L] Brand new EDI folder structure- Need ideas and > suggestions > > I'm setting up a brand new EDI folder structure. I'd like to get > some ideas > or suggestions on the best way to setup this new folder structure. > We have a > few hundred clients. > > Any suggestions are appreciated. > > [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/
