Category value for payroll is deleted
Posted: January 16th, 2012, 10:39 pmWhen category value used for payroll is deleted/ Error Message: ## not found in syentity.
BPI payroll requires at least one payroll department to be defined, so it automatically creates the default “1 Department 1”. Even if a user doesn't care about payroll departments, he/she will be forced to keep at least one department defined and assign all employees to that department.
When C21 converts BPI Payroll, it automatically converts it to “Payroll departmentalization by category”, which is a mode equivalent to the way BPI works. In this mode each employee is initially defined a Category 1 value and it is required that some value be assigned to that field.
What it looks like has happened is that the Configure/Categories command was used to delete some values. It should not have let a value used in emloyees Category 1 field to be deleted. In this case, the “Department 1” category was assigned an internal reference number of 842. That number is stored in the employee master with other records that need to refer to a category value. When this category value was deleted, the master definition of entity number 842 was deleted. Subsequently, any processing of the employee master or other payroll records that tries to “de-reference 842” causes the message about “842 not found in syentity”.
What you need to do is define at least one category value and be sure that each employee configuration has an assignment for “Category 1”.
BPI payroll requires at least one payroll department to be defined, so it automatically creates the default “1 Department 1”. Even if a user doesn't care about payroll departments, he/she will be forced to keep at least one department defined and assign all employees to that department.
When C21 converts BPI Payroll, it automatically converts it to “Payroll departmentalization by category”, which is a mode equivalent to the way BPI works. In this mode each employee is initially defined a Category 1 value and it is required that some value be assigned to that field.
What it looks like has happened is that the Configure/Categories command was used to delete some values. It should not have let a value used in emloyees Category 1 field to be deleted. In this case, the “Department 1” category was assigned an internal reference number of 842. That number is stored in the employee master with other records that need to refer to a category value. When this category value was deleted, the master definition of entity number 842 was deleted. Subsequently, any processing of the employee master or other payroll records that tries to “de-reference 842” causes the message about “842 not found in syentity”.
What you need to do is define at least one category value and be sure that each employee configuration has an assignment for “Category 1”.