Re: [SQL-Ledger-users] Q. on the TO-DO list. (Payroll update)

[Wayne <inf...@pi...>]

Hi  Steve,
I was going to hold off on offering some suggestion
until I understand what is going on in the code, but
if anyone is going to develope the payroll I would
suggest that we look at the data model a little further.
The suggertion I'm going to make is not my own. If
folks like to purchase the book "The Data Model
Resource Book"  ISBN 0-471-15364-8
you can see where I'm coming from.
This book has good data model for  a business.
One enity that is present is a "Party", a party is
a person or and organization. One then associates
a relationship to a "Party". This will help to reduce
data redundancy. For example, if I have an employee
that happens to be a vendor, then the party is in
my DB only once , as a person, and I only have to
establish the relationship this enity has. That
relationship would be "employee" and  "vendor".
I know I'm leaving alot of description out, but
I think if people purchase the book it would give
the group a good model to follow.
Later.
Wayne
P.S. I should also point out that I'm learning Perl
to convert the system to Python. I hope that
doesn't offend anyone.


Steve Doerr wrote:

> Hi Wayne/everybody.
>
> Wayne wrote:
>
> > Hello,
> > I see on the TO-DO list that  Steve has started
> > a payroll system and Roderick has started  aging
> > reports. Are these avaiable to view?
> > Thanks.
> > Wayne.
>
> I started a payroll system and there isn't anything that can be loaded
> or used yet.  If anyone wants to help or has any input on it, please let
> me know and I'll send you what I have.  I've got an employee package and
> a few of the sql tables started.
>
> Here's what I have planned - it's a three part system and it just
> follows existing forms and modules.
>
> 1.  An entry form and perl module to set up an employee's information
> (i.e. name, address, pay rate, withholdings/deductions).  This is going
> to write each employee's info to the database, which will be called and
> applied to their pay period data when you enter and run payroll.  I've
> got a separate table for deductions/withholdings that will have a two
> part id, one associates them with an employee id and one numbers them.
> It should be able to hold an infinite number and types of deductions for
> employees in any country (that's the goal).
>
> 2.  An entry form and perl module to enter each employee's data for the
> pay period (hours worked, vacation taken, sick time taken, etc.).
> You'll also be able to run and post the pay period data here.
>
> 3. Reports.
>
> That's a brief overview of payroll.
> Steve