Hello Everybody,
I am downright desperate.
I need some "Pro Bono" help regarding a solution I'm working on for my father's company.
He owns a Manufacturers' Representative firm, and I am having the hardest time building him a working solution
The main problem lies in tracking his rep's commissions, and having the ability to split them up if they share a sale.
I have created a work flow type of interface, but the data doesn't always seem go through the relationships.
Here is a summary:
[Customers]----<[Orders]------<[invoices]>--------[Commissions Recieved]--------<[Commissions Payable]
To walk you through the process
1.) A customer writes an order with us, that customer usually has a default rep by territory.
2.) Orders are sent to the Manufacturer ( this step is not necessary in the database)
a.) At this point it is determined if the commission will be split between two (or more) reps.
b.) Part of the commission is also given to the house, to pay for overhead, and expenses
3.) When the order is received by the Manufacturer, it is fulfilled, and sent to the customer.
4.) Once the order is shipped with an Invoice, we receive a copy of the Invoice (usually) and match the Order with the Invoice (Do I need a One to One link here since one order will only have one matched invoice?)
a.) I should mention we don't always receive an invoice for our order, or an order for an invoice (but we still get commission).
b.) We even receive some invoices scribbled on notebook paper.
5.) The invoices are then compiled by Manufacturer, Where we get a total for the commissions due.
a.) Sometimes they send commissions along with Invoice copies
b.) Other times only partial payments are made on commissions due.
6.) Reps are payed bi-weekly only what is shipped (the invoice total) to the customers, and only on what is received in commissions in those periods.
I have literally been working on this solution for months, and have been racking (possibly frying it) my brain.
Currently they rely on custom software that was given and tested on them back in 1999. So it was developed to work in OS 9.
Which means the newest OS it will run on is 10.4. thanks to OS 9 virtualization support.
Hence the application is very buggy and full of error messages, but somehow it works.
The developer had since abandoned the project and was actually hired on by Apple.
Any advice you'd be willing to share would be HUGELY appreciated.
This is my first database ever, and so far the experience has not been pleasant.