DomainKey-Signature: a=rsa-sha1; q=dns; c=nofws;
        s=beta; d=gmail.com;
        h=received:message-id:date:from:to:subject:cc:in-reply-to:mime-version:content-type:references;
        b=J7f8j8r8CEWGUh5ATvorOjBoL6UUTtXNdsU7MimqzNM8QSUFGKfODTPyrb9LDfSqIb7fEBUPd27U9atPicI5EoZAiCWeWQ/51dqIi3mM3JzJuC7f9cAXn7tR57emaQ6Ed9uicF2z6bTUFYZVHs4lrCwYM8X93AaFHMR6kZndVK0=
Message-ID: <cd4305c10608081219r6e16510dueedb7d4cac256a1f@mail.gmail.com>
Date: Tue, 8 Aug 2006 15:19:39 -0400
From: "Juan Carlos Reyes Pacheco" <juancarlosreyesp@gmail.com>
To: "Dennis Williams" <oracledba.williams@gmail.com>
Subject: Re: ot: Please reference to excellent Enterprise Resrouce Planning book references
Cc: oracle-l@freelists.org
In-Reply-To: <de807caa0608080734k6bc5b158h7bf842c3d0e55fd@mail.gmail.com>
MIME-Version: 1.0
Content-Type: multipart/alternative; boundary="----=_Part_81515_17778647.1155064779376"
References: <cd4305c10608080641o6405c454pd930f061ee98e965@mail.gmail.com>
	 <de807caa0608080734k6bc5b158h7bf842c3d0e55fd@mail.gmail.com>
Sender: oracle-l-bounce@freelists.org
Errors-to: oracle-l-bounce@freelists.org
Precedence: normal
Reply-to: juancarlosreyesp@gmail.com
------=_Part_81515_17778647.1155064779376
Content-Type: text/plain; charset=ISO-8859-1; format=flowed
Content-Transfer-Encoding: 7bit
Content-Disposition: inline

Thanks a lot Dennis, I know how big they are, but if you want to start one,
you have to start from somewhre, I know about accounting, employee, etc.
What I was looking was good sources for ideas designing erps.


On 8/8/06, Dennis Williams <oracledba.williams@gmail.com> wrote:
>
> Juan,
>
> You've set a rather ambitious task for yourself. First of all, ERP is
> mainly a buzzword. It consists of whatever a company decides it should. As
> you have stated, an ERP consists of modules. The modules are where the real
> significance is, the real brains. The rest is just how you get the modules
> to communicate. Usually the key module is the general ledger module, since
> money is the key resource in an organization and the general ledger tracks
> the money. There are other modules that usually round out a fully-fledged
> accounting system such as budgeting, accounts payable, accounts receivable.
> Then there are other modules that companies have come to expect from a
> fully-fledged ERP system such as payroll, support for human relations, and
> perhaps inventory control. But the point is that at some point there is
> discretion whether to include particular modules or not in a vendor's ERP
> design, depending on what the vendor's clients are requesting, and where the
> vendor's competence lies.
>     To develop any of these modules would take an education in that
> subject and years of professional practice. A company which wishes to
> develop one of these modules first hires a team of competent professionals
> in that subject area to design that module.
>     Once you've developed individual modules, then you must decide how the
> modules will exchange information. A key decision is how frequently the
> modules need to exchange information. Sometimes it must be real-time.
> Sometimes you want an overnight cycle. Sometimes it is a month-end
> accounting cycle.
>     In summary, ERP systems, even small ones, tend to be vast, sprawling
> affairs with complexity that boggles the imagination. But the number of
> features varies according to the size of organization which purchases them.
> Take payroll for example. Say you are a payroll clerk paying a dozen
> employees at a small organization. You just need a very simple payroll
> program to assist you. Maybe only one employee has a garnishment against
> his/her wages. You just handle that manually without assistance from the
> program. Now, suppose you manage a payroll department for a medium-sized
> company and you pay thousands of employees. Now there will be hundreds of
> people with garnishments against their wages so you must have a payroll
> program with a good garnishment feature or you'll spend a lot of time each
> month handling the garnishments manually. So small organizations use simple,
> cheap programs with few features, while large organizations use complex,
> expensive programs with many, many features. Hopefully this gives you some
> small insights into the ERP landscape.
>     From the point of view of a database administrator, it is all tables
> and demanding users. You aren't expected to be an expert in any of the ERP
> modules. But you must ensure the users don't encounter any database errors
> and fix any errors promptly and courteously. You should have a professional
> demeanor that lets you work with many types of people.
>
> Dennis Williams
>


-- 
----------------------------------------
http://www.oracleboliviaspecialists.com/

Oracle Certified Profesional 9i 10g
Orace Certified Professional Developer 6i

10 years of experience from Oracle 7 to Oracle10g and developer 6i

------=_Part_81515_17778647.1155064779376
Content-Type: text/html; charset=ISO-8859-1
Content-Transfer-Encoding: quoted-printable
Content-Disposition: inline

Thanks a lot Dennis, I know how big they are, but if you want to start one,=
 you have to start from somewhre, I know about accounting, employee, etc.<b=
r>What I was looking was good sources for ideas designing erps.<br><br><br>
<div><span class=3D"gmail_quote">On 8/8/06, <b class=3D"gmail_sendername">D=
ennis Williams</b> &lt;<a href=3D"mailto:oracledba.williams@gmail.com">orac=
ledba.williams@gmail.com</a>&gt; wrote:</span><blockquote class=3D"gmail_qu=
ote" style=3D"border-left: 1px solid rgb(204, 204, 204); margin: 0pt 0pt 0p=
t 0.8ex; padding-left: 1ex;">
<div><div>Juan,</div>
<div>&nbsp;</div>
<div>You've set a rather ambitious task for yourself. First of all, ERP is =
mainly a buzzword. It consists of whatever a company decides it should. As =
you have stated, an ERP consists of modules. The modules are where the real=
 significance is, the real brains. The rest is just how you get the modules=
 to communicate. Usually the key module is the general ledger module, since=
 money is the key resource in an organization and the general ledger tracks=
 the money. There are other modules that usually round out a fully-fledged =
accounting system such as budgeting, accounts payable, accounts receivable.=
 Then there are other modules that companies have come to expect from a ful=
ly-fledged ERP system such as payroll, support for human relations, and per=
haps inventory control. But the point is that at some point there is discre=
tion whether to include particular modules or not in a vendor's ERP design,=
 depending on what&nbsp;the vendor's&nbsp;clients are requesting, and where=
&nbsp;the vendor's&nbsp;competence lies.
</div>
<div>&nbsp;&nbsp;&nbsp; To develop any of these modules would take an educa=
tion in that subject and years of professional practice. A company which wi=
shes to develop one of these modules first hires a team of competent profes=
sionals in that subject area to design that module.
</div>
<div>&nbsp;&nbsp;&nbsp; Once you've developed individual modules, then you =
must decide how the modules will exchange information. A key decision is ho=
w frequently the modules need to exchange information. Sometimes it must be=
 real-time. Sometimes you want an overnight cycle. Sometimes it is a month-=
end accounting cycle.
</div>
<div>&nbsp;&nbsp;&nbsp; In summary, ERP systems, even small ones, tend to b=
e vast, sprawling affairs with complexity that boggles the imagination. But=
 the number of features varies according to the size of organization which =
purchases them. Take payroll for example. Say you are a payroll clerk payin=
g a dozen employees at a small organization. You just need a very simple pa=
yroll program to assist you. Maybe only one employee has a garnishment agai=
nst his/her wages. You just handle that manually without assistance from th=
e program. Now, suppose you manage a payroll department for a medium-sized =
company and you pay thousands of employees. Now there will be hundreds of p=
eople with garnishments against their wages so you must have a payroll prog=
ram with a good garnishment feature or you'll spend a lot of time each mont=
h handling the garnishments manually. So small organizations use simple, ch=
eap programs with few features, while large organizations use complex, expe=
nsive programs with many, many features. Hopefully this gives you some smal=
l insights into the ERP landscape.
</div>
<div>&nbsp;&nbsp;&nbsp; From the point of view of a database administrator,=
 it is all tables and demanding users. You aren't expected to be an expert =
in any of the ERP modules. But you must ensure the users don't encounter an=
y database errors and&nbsp;fix any errors promptly and courteously. You sho=
uld have a professional demeanor that lets you work with many types of peop=
le.
</div></div><div><span class=3D"sg">
<div>&nbsp;</div>
<div>Dennis Williams</div>

</span></div></blockquote></div><br><br clear=3D"all"><br>-- <br>----------=
------------------------------<br><a href=3D"http://www.oracleboliviaspecia=
lists.com/">http://www.oracleboliviaspecialists.com/</a><br><br>Oracle Cert=
ified Profesional 9i 10g
<br>Orace Certified Professional Developer 6i<br><br>10 years of experience=
 from Oracle 7 to Oracle10g and developer 6i

------=_Part_81515_17778647.1155064779376--
--
http://www.freelists.org/webpage/oracle-l