Best Practice for table/database design

[psycoperl]

Hi All, I am working on a database that keeps track of booklets we receive, process, package and ship out; and want to get some best practice and design ideas...

We recieve booklets for processing from 5 different sites, what we want to do is keep track of:
When we receive a package of booklets the site, date recieved and quantity received
When we process the booklets, the site, the date processed and quantity processed
when we package the booklets for shipping, site we are prepareing, the date packaged and the quantity packaged
When the packages are actually picked up by messenger, the site, the date picked up and the quantity picked up.

I am not sure if I should use 4 tables, one each for receive, process, package, messenger or if there is another way.

Because we may process all the booklets from a site's delivery at different dates or may process multiple deliveries from the same site at one time. I need to keep track what what is in each stage.

 

[xenou]

I'd go with one table with a column of TransactionType or TransType, something like that: RECV, PROC, SHIP, RCPT (or just a numeric type ID: 1,2,3,4). Wonder would you need to keep track of lots or is a booklet a booklet a booklet.

 

[psycoperl]

I'd go with one table with a column of TransactionType or TransType, something like that: RECV, PROC, SHIP, RCPT (or just a numeric type ID: 1,2,3,4). Wonder would you need to keep track of lots or is a booklet a booklet a booklet.

Thanks.

A booklet is a booklet, on average we get any where from 1 to 500 per site at a time. I will see how this works.