Hi David, sound like a good idea, my suggestion was just to follow the database design book. This is less work so sure we can do that.....
we do need however special invoiceItemtypes and therefore a new invoiceType, Please let me know because as usual...my customers want this quick and it would be nice if we could now agree on this implementation? So an invoiceType called "Salary" and types like (US) withholding tax, 401-deduction etc...and the mapping against a glAccount for which we can use the existing invoiceItemTypeGlAccount mapping.... when this new Invoice type is created, we can create the items at the same time and have the user (in the first phase) fill in the values calculated by hand. (gross salary can be taken from the HR component if available) In the second phase we will calculate the values by the system, but that can be discussed later... an acceptable approach? Regards, Hans On Fri, 2009-01-09 at 16:14 -0800, David E Jones wrote: > Why not just use Invoice* and Payment? These are used elsewhere for > outgoing payments and such, and Invoice has the itemized detail > structure that you're looking for. > > -David > > > On Jan 9, 2009, at 6:21 AM, Hans Bakker wrote: > > > I am looking to add payroll functions. > > > > anybody any ideas/concerns? > > > > actions: > > 1. add entity "PayCheckItem" with key paymentId and paymentItemSeqId > > and with "PayCheckItemType" and other fields > > 2. add services, screens ad forms in accounting > > 3. add automatic calculation using data from HR > > > > input appreciated! > > > > -- > > Antwebsystems.com: Quality OFBiz services for competitive prices > > > -- Antwebsystems.com: Quality OFBiz services for competitive prices
