For example, an employee can be

[hasinam2206]

Employee lists are imported from Timex and assignments are made in 1C. Timex then collects event data and transfers the information back to the accounting system. On the one hand, the ability to directly enter employees into the Timex database gives it autonomy, on the other hand, it creates situations that we will now discuss. How the problem manifested itself When synchronizing 1C:ZUP–Timex, errors began to occur in certain cases: Associated with duplication of employees and positions.

That is, a person goes to work, and the clock in Timex venezuela mobile database is empty, as if he did not check in at the checkpoint. After analyzing the situation, it became clear that the error is caused by the fact that in 1C:ZUP the employee is linked to an incorrect Timex employee due to the presence of duplicates in the latter. This is due to the ability to enter an employee directly in Timex.
entered into the control system twice: unloading from 1C in the position of “Chief Specialist” (correctly, in accordance with the staffing schedule); directly to the Timex database in the position of “Leading Specialist” (incorrect). If an employee in 1C:ZUP is linked to the "Leading Specialist" in Timex, then his timesheet in 1C will be empty. Timex has a standard option to redefine the EmployeeLink–ID_Timex connection, but the scheme is complex and duplicates must be searched for manually, i.

e. wait until an error occurs in the timesheet and correct it immediately. Related to an incorrect code in the timesheet. The error occurred when an employee left maternity leave early (code OZ). When the document "Return from maternity leave" was issued in 1C:ZUP, Timex did not cancel the employee's vacation status. As a result, timesheets with the designation "OZ" were uploaded to 1C:ZUP when the employee was not at work, for example, on weekends.