Community opinion requested: I am looking to integrate Payroll functions into Human resources component. I studied the current status of the component and looked at the Datamodel resource book and see the entities are exactly copied, except for the the paycheck where we did not follow the book and used the Invoice for that.
Although normally the datamodels in the book are pretty good, for the HR component there are some strange things which make it difficult to understand: Payrol benefits: 1. PartyBenefit is linked to employment (same key) but is called PartyBenefit, why not EmploymentBenefit? 2. BenefitType now should link to invoiceItemType Payrol deductions: 1. Deduction is only linked to a paymentId with an amount. We now use the invoiceItem for that, so this entity is redundant. 3. DeductionType seems to be ok (better name: EmplDeductionType) but should now be linked to invoiceItemType instead of Deduction. 4. The entity PartyBenefit or better EmploymentBenefit is missing completely and should have a similar function as PartyBenefit but then subtracted from the gross amount in payroll. Employment Pay history: PayHistory has the same key as employment so why is the name not called EmploymentPayHistory? Because the entities do not start with employment they are also not listed together in the entity list and therefore this part is difficult to understand. Anybody any preferences or strong opinions here? I do not expect that this part of the system is used? I am prepared to put some effort to change this, if we agree that it is not required to write any data-migration tools. Regards, Hans -- http://www.antwebsystems.com : Quality OFBiz support for competitive rates....
