Re: [WebERP-developers] Web-erp-developers Digest, Vol 92, Issue 4

[ExsonQu <hex...@gm...>]

*Hi, Muthu,*


           Welcome to webERP community and thanks for any constructive
comments. 

           In manufacturing environment, Purchasing request is a must in
most of time. It's an internal document instead of a PO which is used to
send to suppliers. 

          I've studied webERP's work flow and found it do not meets the
requirements most of time. Sometime users will create a PR by sales orders
instead of by the result of MRP. The purchasing request will include
materials according to BOM. So it usually will include different vendors'
data instead of only one vendor in the PO.

          The PR answer the question why we should purchase. But PO can not
answer it. That's why the PR is a must in some business environment. 

          And there are also users who use the MRP result to create a PR. 

           In my opinion, we can create two kinds of work flow for users who
need this feature. One is according to SO and one is according to MRP
result. 
            After the PR is approved, we can convert it to PO and connect to
webERP's currently work flow. It's just my 2 cents.

        And I've also noticed that in a trading environment, the PR's role
is not so important.

        Thanks and best regards!

        Exson

           



--
View this message in context: http://weberp-accounting.1478800.n4.nabble.com/Re-Web-erp-developers-Digest-Vol-92-Issue-4-tp4657151p4657156.html
Sent from the web-ERP-developers mailing list archive at Nabble.com.