payrol entities and payrolinvoiceItemtype
----------------------------------------- Key: OFBIZ-2143 URL: https://issues.apache.org/jira/browse/OFBIZ-2143 Project: OFBiz Issue Type: Improvement Reporter: Hans Bakker Just a reminder to not forget. Currently it is possible to create apayrolslip inludinbg check. The maojor items on a payslip are: 1.salary/hourly wages 2.Deductions 3. Tax now it appears there are other tables in the system which are very similar or even duplicate information: 1. BenefitType 2. DeductionType 3. TaxType we could consider using the field "hasTable=y" for these payrol invoice item types -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online. |
[ https://issues.apache.org/jira/browse/OFBIZ-2143?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Hans Bakker updated OFBIZ-2143: ------------------------------- Description: Just a reminder to not forget. Currently it is possible to create apayrolslip inludinbg check. The maojor items on a payslip are: 1.salary/hourly wages 2.Deductions 3. Tax now it appears there are other tables in the system which are very similar or even duplicate information: 1. BenefitType 2. DeductionType 3. TaxAuthorityRateType we could consider using the field "hasTable=y" for these payrol invoice item types was: Just a reminder to not forget. Currently it is possible to create apayrolslip inludinbg check. The maojor items on a payslip are: 1.salary/hourly wages 2.Deductions 3. Tax now it appears there are other tables in the system which are very similar or even duplicate information: 1. BenefitType 2. DeductionType 3. TaxType we could consider using the field "hasTable=y" for these payrol invoice item types > payrol entities and payrolinvoiceItemtype > ----------------------------------------- > > Key: OFBIZ-2143 > URL: https://issues.apache.org/jira/browse/OFBIZ-2143 > Project: OFBiz > Issue Type: Improvement > Reporter: Hans Bakker > > Just a reminder to not forget. > Currently it is possible to create apayrolslip inludinbg check. The maojor items on a payslip are: > 1.salary/hourly wages > 2.Deductions > 3. Tax > now it appears there are other tables in the system which are very similar or even duplicate information: > 1. BenefitType > 2. DeductionType > 3. TaxAuthorityRateType > we could consider using the field "hasTable=y" for these payrol invoice item types -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online. |
In reply to this post by Nicolas Malin (Jira)
[ https://issues.apache.org/jira/browse/OFBIZ-2143?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12669157#action_12669157 ] Hans Bakker commented on OFBIZ-2143: ------------------------------------ I did some investigations in the HR component concerning payrol. 1.Because we are now using the invoice/invoiceItem/invoiceItemType instead of the paymentCheck, i would like to propose to drop the entity "deduction" which is now replaced by the invoiceItem which states the amount. 2. Currently the salary is defined by the emplPosition -> employee positionType -> rate Amount. For smaller companies this is rather complicated. I would like to suggest add a rateTypeId on the employment to override this relationship. Together with the partyId the salary (rateAmount) can be retrieved from the rateAmount entity. if anybody has any other ideas let me know.....i will continue implementing this. > payrol entities and payrolinvoiceItemtype > ----------------------------------------- > > Key: OFBIZ-2143 > URL: https://issues.apache.org/jira/browse/OFBIZ-2143 > Project: OFBiz > Issue Type: Improvement > Reporter: Hans Bakker > > Just a reminder to not forget. > Currently it is possible to create apayrolslip inludinbg check. The maojor items on a payslip are: > 1.salary/hourly wages > 2.Deductions > 3. Tax > now it appears there are other tables in the system which are very similar or even duplicate information: > 1. BenefitType > 2. DeductionType > 3. TaxAuthorityRateType > we could consider using the field "hasTable=y" for these payrol invoice item types -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online. |
On Jan 30, 2009, at 11:58 PM, Hans Bakker (JIRA) wrote: > 2. Currently the salary is defined by the emplPosition -> employee > positionType -> rate Amount. For smaller companies this is rather > complicated. I would like to suggest add a rateTypeId on the > employment to override this relationship. Together with the partyId > the salary (rateAmount) can be retrieved from the rateAmount entity. As an optional override that sounds fine. -David |
Free forum by Nabble | Edit this page |