From: ExsonQu <hex...@gm...> - 2013-12-10 14:31:35
|
*Hi, Tim,* Thank you for your example. I think webERP current authorization part is far from perfect. Or I'm not smart enough to understand the system thoroughly and creatively. I agree that we should do more discussion and hope to find an agreement. Best regards! Exson <quotation tim> I think that we first have to understand how all these processes will work in real life situations, and once we have, then the authorisation process for those systems will become more obvious. I have no problem using different authorisation methods for different processes if that is the best way. For instance Jo (cc'd on this mail for info) wrote recently about having an authorisation system for stock location transfers. I like this idea very much, but cannot get my head around exactly how that would work. Should the authoriser be the sender, the receiver, or someone else entirely? To take two real life examples: To transfer a container of electrical goods from the Mombasa warehouse to the Kampala warehouse is a strategic business decision. The costs in doing this transfer are high, and so the decision has to be taken high up in the organisation. To transfer two packets of paracetamol tabs from the main pharmacy to a sub pharmacy in a hospital is a minor procedure, easily reversed if necessary. Such transfers could happen several times a day, and require little or no authorisation. To webERP both of the above are identical. They are simply stock location transfers, so how to setup an authorisation system that covers everything? It cannot be just on stock valuation, as would you want someone transferring $1 of stock from your Shanghai warehouse to your Buenos Aires warehouse without authorisation? Its an interesting subject and requires a lot of discussion as there will be many scenarios we have not yet thought of. Tim </quotation> -- View this message in context: http://weberp-accounting.1478800.n4.nabble.com/Shall-we-find-a-another-regular-way-to-manage-authority-tp4657044p4657071.html Sent from the web-ERP-developers mailing list archive at Nabble.com. |