Re: [Web-erp-developers] wegs-erp

[skaill <sk...@ro...>]

I believe one central pool of contact info is the way to handle all contacts
including potential (for sales), customer/client and supplier/vendor.

I think I read

Debtors Master - contains customer main/billing address.  Actually I would
separate main from billing even though they're almost always the same.

CustBranch - customer branch delivery addresses.  I'm assuming this means an
order can be made out at the branch level or at least address-wise.  Haven't
tried though.

Suppliers - vendor/supplier address.  You are buying from them so no need
for a bunch of contacts or shipping addresses.

My approach is also usually to have one pool of addresses and they are
connected wherever needed.  Same as what you have for EGS.  In this way if a
supplier was also a vendor then only one address is needed for both and
updating one updates the other automatically.  Also you could add other
types of addresses without building more address tables and functions for
them.  For instance if you bought huge equipment from a supplier and needed
to have their service department contacts it would be easy under this
design.

The main challenges besides locating where all contact info is in webERP
will be pooling that contact info and finding and modifying anywhere they
are used which will likely mainly be orders and reports.

Users, banks and even the company itself have addresses that should all
probably pull from the central addresses area.

At the same time another approach would be the low impact one that Phil
suggested where contact info from webERP is fired into EGS.  EGS would need
to fire back as well and that could be accomplished by having a weberp type
code fired along with the contact info from webERP and EGS stores that in a
table so that if the contact is updated in EGS then EGS knows which
area/record in webERP needs updating.  In this way there could be an
automated procedure to update the webERP side. This is seriously not the
best of methods though.  It is interfacing and interfacing fails in many
ways.  For instance if the technology that updates webERP is not functioning
and someone updates EGS then you are out of synch.  We're doing this
currently with a client because they refuse to give up on their old Lotus
system even though they have had a powerful all inclusive ERP system for a
few years now!

Steve

----- Original Message ----- 
From: "Jake Stride" <ns...@us...>
To: <web...@li...>
Sent: Tuesday, September 21, 2004 5:33 AM
Subject: Re: [Web-erp-developers] wegs-erp


> I have been looking through the weberp database this morning and one of
> the main differences that I have come across between weberp and EGS is
> the representation of contact details (ie address/phone/fax/email/etc).
>
> In weberp am I right in saying that a company has one address, whereas
> in EGS a company can have as many 'contacts' as you like since they are
> stored in a different table. Along with each 'contact' the type of
> 'contact' can be set, so for example, when you add a company with an
> address, the address is automatically set as the default for
> billing/shipping/payment/technical/main, then when you add more
> addresses you can change which is assigned for each, so a company can
> easily have a different address for billling and shipping, and this can
> be pulled from the DB without the user having to select it for the
company.
>
> What are peoples opinions on this method of address/contact handling?
>
> Thanks
>
> Jake
>
>
> -------------------------------------------------------
> This SF.Net email is sponsored by: YOU BE THE JUDGE. Be one of 170
> Project Admins to receive an Apple iPod Mini FREE for your judgement on
> who ports your project to Linux PPC the best. Sponsored by IBM.
> Deadline: Sept. 24. Go here: http://sf.net/ppc_contest.php
> _______________________________________________
> Web-erp-developers mailing list
> Web...@li...
> https://lists.sourceforge.net/lists/listinfo/web-erp-developers