From: Dale S. <dal...@sh...> - 2006-10-18 21:00:15
|
<!DOCTYPE html PUBLIC "-//W3C//DTD HTML 4.01 Transitional//EN"> <html> <head> <meta content="text/html;charset=ISO-8859-1" http-equiv="Content-Type"> </head> <body bgcolor="#ffffff" text="#000000"> Hi James, good points. I think you really bring up two separate issues:<br> <br> Problem 1. Documents that relate to transactions (e.g., check stubs, bank receipts, packing slips, etc.). With the right scanner software, you should be able to scan documents and produce JPG files directly (no faxing needed), and upload them to a Wiki interfaced to WebERP. Although I agree with you that a Wiki isn't the best solution, if you locked down the Wiki privileges so, for example, only the user with permission to do a goods receipts in WebERP could attach packing slips in the associated Wiki page, I think you'd have a workable solution with appropriate controls.<br> <br> Problem 2. Documents that relate to part numbers - the things you buy, sell, or build (e.g., data sheets, drawings, cad files, etc.). Personally, once an organization progresses past a one or two-man shop, it needs the structure of a formal EDMS with check-in, check-out and change-approval (aka ECO) workflow. Perhaps not right away, but things get confusing fast if there isn't a good system right from the start. I personally like "eDMS" (<a class="moz-txt-link-freetext" href="http://www.no-sod.org">http://www.no-sod.org</a>), which is web-based, written in PHP like WebERP, licensed under the GPL, and, at least in my limited evaluation, meets all the basic needs.<br> <br> I envision the engineering department working with eDMS directly to put the data in, with others (e.g., purchasers, receivers, job schedulers, etc.) working in WebERP and linking to eDMS to get the information. This simplifies things, since WebERP only has to pull information from eDMS. You'd have to decide how to handle part numbers. In this environment, the engineering group's probably using an internally developed "smart numbering" system they prefer, which simply means the part is created in WebERP after it's been created first in eDMS, and referencing the engineering part number used in eDMS.<br> <br> eDMS would be a better solution for Problem 1 (transaction documents) than a Wiki would be (better control and a better audit trail), but it would be more complicated than solving Problem 2 since WebERP users would want to push documents into eDMS from WebERP. As far as I'm aware, creating documents in eDMS can currently only be done by working directly in eDMS, so along with a more complicated interface it would also need code changes to eDMS (an API of sorts).<br> <br> Sorry I can't contribute more than ideas at the moment, but if you'd like to bash holes in my grand vision for design and manufacturing SME's using interfaced web-based, PHP, GPL licensed, point-solution applications, check out <a class="moz-txt-link-freetext" href="http://dalescott.no-ip.org/?Alchemy_-_Framework">http://dalescott.no-ip.org/?Alchemy_-_Framework</a> (criticism invited!)<br> <br> Dale<br> <br> <br> James Palof wrote: <blockquote cite="mid...@we..." type="cite"> <pre> This has been posted before and never answered well. What is needed is the ability to upload images, pdfs, or docs of paper work with most processes in the system. For instance, when we recieve money there is a check stub, and bank reciept that is coupled with every the invoice. We have relied on this before to save large amounts of money under dispute. So we have be scanning in every checkstub with the bank reciept taped to it and calling the file that invoice number.jpg. Sometimes you can not beat showing the bank the actual reciept. For the recievables there is a physical packing slip that needs to be scanned in the system that goes with that recievable. Sometimes you can not beat showing the shipping company the actual reciept. For payables, two of our banks give us pdfs of the cleared checks. I would like to "store" "link" those images with the payable portion. For everypart in inventory there is a datasheet, drawing, cad file, that needs to be entered into the system. I am not asking for document control, just the ability to upload more than just images for parts. There should be the ability to upload as many files for the parts, invoice, recievable, payables as desires. It is very frustarting that the only example of this is to be limited to image. This was slightly covers by "Alan Beard" <a class="moz-txt-link-rfc2396E" href="mailto:al...@na..."><al...@na...></a> in his responce to Re: [webERP-users] Purchase Invoices scanned copies but could be elabrated on for more tables. James</pre> <br> <pre> WIKI is not the answer in my opinion. Any thoughts? </pre> <p> </p> <hr size="1">Do you Yahoo!?<br> Get on board. <a href="http://us.rd.yahoo.com/evt=40791/*http://advision.webevents.yahoo.com/mailbeta">You're invited</a> to try the new Yahoo! Mail. <pre wrap=""> <hr size="4" width="90%"> ------------------------------------------------------------------------- Using Tomcat but need to do more? Need to support web services, security? Get stuff done quickly with pre-integrated technology to make your job easier Download IBM WebSphere Application Server v.1.0.1 based on Apache Geronimo <a class="moz-txt-link-freetext" href="http://sel.as-us.falkag.net/sel?cmd=lnk&kid=120709&bid=263057&dat=121642">http://sel.as-us.falkag.net/sel?cmd=lnk&kid=120709&bid=263057&dat=121642</a></pre> <pre wrap=""> <hr size="4" width="90%"> _______________________________________________ web-ERP-users mailing list <a class="moz-txt-link-abbreviated" href="mailto:web...@li...">web...@li...</a> <a class="moz-txt-link-freetext" href="https://lists.sourceforge.net/lists/listinfo/web-erp-users">https://lists.sourceforge.net/lists/listinfo/web-erp-users</a> </pre> </blockquote> </body> </html> |