web-erp-developers

[WebERP-developers] Other feature to develop

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

*Dear all,*

            Thank you for your great efforts to webERP. 

            I'd like to know if it need to develop following features or we
have work around for it:

            1. Vendor status management. Currently, we have customers status
management such as watch, liquid, good etc. But we have no corresponding
feature with suppliers. I think it's also a need feature to record suppliers
status such as assessment, qualified, non-conformance. We can only issue PO
to qualified vendors.

            2. IM is very popular even between businesses today, shall we
add a IM contact address for customer branches?

            3. We have some control about sales people login now. But
sometime, roles such as sales group leaders have to view whole group's
customer data, is there any workaround or we just have to develop some new
feature.

           Any comments are welcome!

            Thanks and best regards!

            Exson



--
View this message in context: http://weberp-accounting.1478800.n4.nabble.com/Other-feature-to-develop-tp4657319.html
Sent from the web-ERP-developers mailing list archive at Nabble.com.

Re: [WebERP-developers] Other feature to develop

[Phil D. <ph...@lo...>]

Hi Exson,

Thanks for your great efforts to make webERP better.

That's an interesting idea - perhaps for 1 it needs to be by item - so 
perhaps they are ok to provide widget X but not widget Y.

2. Yes if we can work out a URL to initiate IM then would be good

3. Not quite so clear on this one. I think the salesman logic got a bit 
messy - not clear on how you see this evolving.

Did the warehouse management development work ever get completed?

Best regards

Phil

Phil Daintree
Logic Works Ltd - +64 (0)275 567890
http://www.logicworks.co.nz

On 03/04/14 14:26, ExsonQu wrote:
> *Dear all,*
>
>              Thank you for your great efforts to webERP.
>
>              I'd like to know if it need to develop following features or we
> have work around for it:
>
>              1. Vendor status management. Currently, we have customers status
> management such as watch, liquid, good etc. But we have no corresponding
> feature with suppliers. I think it's also a need feature to record suppliers
> status such as assessment, qualified, non-conformance. We can only issue PO
> to qualified vendors.
>
>              2. IM is very popular even between businesses today, shall we
> add a IM contact address for customer branches?
>
>              3. We have some control about sales people login now. But
> sometime, roles such as sales group leaders have to view whole group's
> customer data, is there any workaround or we just have to develop some new
> feature.
>
>             Any comments are welcome!
>
>              Thanks and best regards!
>
>              Exson
>
>
>
> --
> View this message in context: http://weberp-accounting.1478800.n4.nabble.com/Other-feature-to-develop-tp4657319.html
> Sent from the web-ERP-developers mailing list archive at Nabble.com.
>
> ------------------------------------------------------------------------------
> _______________________________________________
> Web-erp-developers mailing list
> Web...@li...
> https://lists.sourceforge.net/lists/listinfo/web-erp-developers
>

Re: [WebERP-developers] Other feature to develop

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

*Hi, Phil,*

           Thank you for your nice comments.

           1. Thumb has almost completed the bin management module. I've
created an distributed version based on 4.10. I'll send it to you later. 

           2. Yes. It's better to assessment suppliers based on items. The
situation seems a little complicated. Need more consideration to this. 

           3. Currently, the salesman can only review their own customer
data if they are marked as salesman login. But we found that sometime some
users have 2 salesman accounts, they have to login and logout to see the
accounts they owned. And if there are several sales groups, the group leader
will not see their team's status. Thumb has created a team feature. Do we
need to add this feature to webERP? It seems more like a CRM concept. And
another scenario is that, some users will have one team to manage sales
orders, their responsibility will be classified by customer's type. For
instance, Clerk A will be responsible for customer type A, and Clerk B will
be responsible for customer type B. Shall this features is needed?

           Thanks and best regards!

           Exson 



--
View this message in context: http://weberp-accounting.1478800.n4.nabble.com/Other-feature-to-develop-tp4657319p4657321.html
Sent from the web-ERP-developers mailing list archive at Nabble.com.

Re: [WebERP-developers] Other feature to develop

[Phil D. <ph...@lo...>]

Yes I think the team leader is a CRM thing... if a user is allowed to 
see all salesman then it is simple and we also have the option for a 
saleman only login. I think it is probably a mod specific to the 
business that it was done for more than having widespread appeal.

Phil

Phil Daintree
Logic Works Ltd - +64 (0)275 567890
http://www.logicworks.co.nz

On 03/04/14 22:23, ExsonQu wrote:
> *Hi, Phil,*
>
>             Thank you for your nice comments.
>
>             1. Thumb has almost completed the bin management module. I've
> created an distributed version based on 4.10. I'll send it to you later.
>
>             2. Yes. It's better to assessment suppliers based on items. The
> situation seems a little complicated. Need more consideration to this.
>
>             3. Currently, the salesman can only review their own customer
> data if they are marked as salesman login. But we found that sometime some
> users have 2 salesman accounts, they have to login and logout to see the
> accounts they owned. And if there are several sales groups, the group leader
> will not see their team's status. Thumb has created a team feature. Do we
> need to add this feature to webERP? It seems more like a CRM concept. And
> another scenario is that, some users will have one team to manage sales
> orders, their responsibility will be classified by customer's type. For
> instance, Clerk A will be responsible for customer type A, and Clerk B will
> be responsible for customer type B. Shall this features is needed?
>
>             Thanks and best regards!
>
>             Exson
>
>
>
> --
> View this message in context: http://weberp-accounting.1478800.n4.nabble.com/Other-feature-to-develop-tp4657319p4657321.html
> Sent from the web-ERP-developers mailing list archive at Nabble.com.
>
> ------------------------------------------------------------------------------
> _______________________________________________
> Web-erp-developers mailing list
> Web...@li...
> https://lists.sourceforge.net/lists/listinfo/web-erp-developers
>

Re: [WebERP-developers] Other feature to develop

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

*Hi,Phil,*

            Thank you for your reply. 

           Although it seems a CRM like feature, the main reason is that our
search engine is not so flexible as expected. 

           For instance, those control is a search limit issue. Why not
think about to revise the search engine to provide more choices to users or
developers?

           Thanks and best regards!

           Exson
           



--
View this message in context: http://weberp-accounting.1478800.n4.nabble.com/Other-feature-to-develop-tp4657319p4657323.html
Sent from the web-ERP-developers mailing list archive at Nabble.com.

Re: [WebERP-developers] Other feature to develop

[rfthomas <rf...@as...>]

Phil and Exson,

The system currently allows for having multiple vendors for an item.  A
vendor may have a status of preferred for an item.  This information is kept
in the PurchData table in the preferred field.  0 = normal, 1 = preferred

Why not create a table with choices for this field as is done for UOM, etc.? 
1 retaining it's value, but other values being allowed as defined in the
purchase status table, e.g. 0 - normal, 1 - preferred, 2 - unaproved, ...

Would such be an acceptable solution?  This is used in only a few scripts.

Bob Thomas



--
View this message in context: http://weberp-accounting.1478800.n4.nabble.com/Other-feature-to-develop-tp4657319p4657373.html
Sent from the web-ERP-developers mailing list archive at Nabble.com.

Re: [WebERP-developers] Other feature to develop

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

*Hi, Bob,*

         It's a concise solution! 

         We can improve suppliers' management by this. 

         Best regards!

         Exson

         



--
View this message in context: http://weberp-accounting.1478800.n4.nabble.com/Other-feature-to-develop-tp4657319p4657375.html
Sent from the web-ERP-developers mailing list archive at Nabble.com.

Re: [WebERP-developers] Other feature to develop

[Phil D. <ph...@lo...>]

Makes sense in principle. Can you explain a bit more how vendors would move between these statuses and where we might use these other statuses or is this for integration with an external quality system or just report in?
-- 
Phil Daintree
+64(0)275 567890
Skype: daintree

On April 26, 2014 3:04:27 AM NZST, rfthomas <rf...@as...> wrote:
>Phil and Exson,
>
>The system currently allows for having multiple vendors for an item.  A
>vendor may have a status of preferred for an item.  This information is
>kept
>in the PurchData table in the preferred field.  0 = normal, 1 =
>preferred
>
>Why not create a table with choices for this field as is done for UOM,
>etc.? 
>1 retaining it's value, but other values being allowed as defined in
>the
>purchase status table, e.g. 0 - normal, 1 - preferred, 2 - unaproved,
>...
>
>Would such be an acceptable solution?  This is used in only a few
>scripts.
>
>Bob Thomas
>
>
>
>--
>View this message in context:
>http://weberp-accounting.1478800.n4.nabble.com/Other-feature-to-develop-tp4657319p4657373.html
>Sent from the web-ERP-developers mailing list archive at Nabble.com.
>
>------------------------------------------------------------------------------
>Start Your Social Network Today - Download eXo Platform
>Build your Enterprise Intranet with eXo Platform Software
>Java Based Open Source Intranet - Social, Extensible, Cloud Ready
>Get Started Now And Turn Your Intranet Into A Collaboration Platform
>http://p.sf.net/sfu/ExoPlatform
>_______________________________________________
>Web-erp-developers mailing list
>Web...@li...
>https://lists.sourceforge.net/lists/listinfo/web-erp-developers

Re: [WebERP-developers] Other feature to develop

[rfthomas <rf...@as...>]

Phil,

In the current system, when one looks at an inventory item the list of
vendors is displayed with each vendor's status, i.e. preferred or not.  The
additional status would allow for better information with respect to
vendors.  In addition, we deal in areas where there is government control,
e.g. Aircraft Engines, Surgical Instruments, etc. It is necessary to qualify
vendors for certain items.  By having status flags, maintained by the
appropriate staff, allows people with limited knowledge of the vendors to
make a reasonable choice.

Appropriate staff would manually modify vendor status.  We routinely get
calls from customers requiring annual updates on certifications and
capabilities.

There are times when one of our engineers is at a customer site and needs
something shipped from a vendor immediately.  Staff trying to obtain the
item, don't necessarily know all of the vendors.  If the preferred vendor is
out of stock, they need to know who is approved and go through the list with
some confidence that they will get a properly certified item.

This change would allow for capturing knowledge in the database rather than
relying on possibly one person's recollection or a totally separate
database.

Depending on other's needs, we would view this as a nice to have feature.

Bob



--
View this message in context: http://weberp-accounting.1478800.n4.nabble.com/Other-feature-to-develop-tp4657319p4657379.html
Sent from the web-ERP-developers mailing list archive at Nabble.com.

Re: [WebERP-developers] Other feature to develop

[Phil D. <ph...@lo...>]

Understood - good idea.

Phil

Phil Daintree
Logic Works Ltd - +64 (0)275 567890
http://www.logicworks.co.nz

On 26/04/14 09:01, rfthomas wrote:
> Phil,
>
> In the current system, when one looks at an inventory item the list of
> vendors is displayed with each vendor's status, i.e. preferred or not.  The
> additional status would allow for better information with respect to
> vendors.  In addition, we deal in areas where there is government control,
> e.g. Aircraft Engines, Surgical Instruments, etc. It is necessary to qualify
> vendors for certain items.  By having status flags, maintained by the
> appropriate staff, allows people with limited knowledge of the vendors to
> make a reasonable choice.
>
> Appropriate staff would manually modify vendor status.  We routinely get
> calls from customers requiring annual updates on certifications and
> capabilities.
>
> There are times when one of our engineers is at a customer site and needs
> something shipped from a vendor immediately.  Staff trying to obtain the
> item, don't necessarily know all of the vendors.  If the preferred vendor is
> out of stock, they need to know who is approved and go through the list with
> some confidence that they will get a properly certified item.
>
> This change would allow for capturing knowledge in the database rather than
> relying on possibly one person's recollection or a totally separate
> database.
>
> Depending on other's needs, we would view this as a nice to have feature.
>
> Bob
>
>
>
> --
> View this message in context: http://weberp-accounting.1478800.n4.nabble.com/Other-feature-to-develop-tp4657319p4657379.html
> Sent from the web-ERP-developers mailing list archive at Nabble.com.
>
> ------------------------------------------------------------------------------
> Start Your Social Network Today - Download eXo Platform
> Build your Enterprise Intranet with eXo Platform Software
> Java Based Open Source Intranet - Social, Extensible, Cloud Ready
> Get Started Now And Turn Your Intranet Into A Collaboration Platform
> http://p.sf.net/sfu/ExoPlatform
> _______________________________________________
> Web-erp-developers mailing list
> Web...@li...
> https://lists.sourceforge.net/lists/listinfo/web-erp-developers
>