Define Employee Information in Time and Attendance

… the name of the employee.

The last name should be entered first followed by a comma and the first name since it is used in sorting orders and for sorting.

… the ID of the person who last affected the current employee record.

You can use the M3 log function on this field meaning you can track the changes made to this record, that is, see who made changes to the record and when. (Use 'Settings – Security' (SES800) and 'Field Audit Trail. Perform' (SES110) to activate this function.)

… whether the employee is active, that is to be included in calculations, printouts, etc.

An example of when an employee may not be active is when Personnel Management defines a new employee's information before he/she actually begins his/her new job.

… the facility to which the employee belongs.

Facilities are defined in 'Facility. Open' (CRS008)

… the department to which the current employee belongs.

Departments can, for example, be used to block the access of employees that belong to particular departments to certain parts of Time and Attendance.

… the planning area to which the current employee belongs.

Planning areas can, for example, be used to block the access of employees that belong to particular planning areas to certain parts of Time and Attendance.

… the schedule on which the current employee's calendar is to be based and created.

The employee's calendar is automatically created when you press Enter to proceed to the F panel and can be reviewed in 'Employee. Connect Calendar' (CRS510).

This field is used in combination with the 'Work schedule from date' field.

… the date from which the calendar is to be created.

This field makes it possible to change an employee's work time at any time during the year (from working days to nights, for example).

… the week in the schedule string from which the calendar is to be valid.

When you enter or delete a value in this field, the employee calendar is updated from the 'work schedule from date' to the end of the current year.

If the first week in the schedule string is to be used as the starting week, leave this field blank.

… the ID of the card that the employee received for identification during reporting via the reporting terminal.

This card number is specific for both the employee and company.

… the employee group to which the employee belongs. This group defines the employee's authorization level.

Employee groups are defined in 'TIM Employee Group. Open' (TMS120).

… whether operation time should be calculated irrespective of employee attendance.

The valid alternatives are

0 = Always calculate operation time

1 = Only calculate operation time for the times that the employee is present.

… how overtime is to be calculated for the employee. This method functions in combination with the specified conditions in 'Work Hour Group. Connect Time Type' (TMS110) and 'Settings – Time and Attendance' (TMS950).

The valid alternatives are

0 = No overtime is calculated

1 = Overtime is calculated according to a completed work hour measurement for each scheduled day

2 = Overtime is calculated beyond the specified flex limits for the employee. The 'Calculation method – flextime' field must contain 1 for this method

3 = Overtime is always calculated after ordinary work hours.

… how flextime is to be calculated for the employee.

The valid alternatives are

0 = Employee does not use flextime

1= Flextime calculated according to flextime schedule

2 = Standard flextime.

If alternative 1 is used, flextime is generated from the flextime limits created in (CRS525). Each clock-in/out is checked against the limit values and reconciled with the work hour definition in (CRS505) for the respective day.

If alternative 2 is used, the total present time is daily reconciled with the scheduled time and the difference is generated to the flextime balance.

… the time type to which calculated flextime is to be connected.

This time type must be defined as time category 5.

… the time type to which calculated attendance is connected.

This time type must be defined as time category 3.

… the time type to which actual attendance is connected.

The actual attendance time is the time that an employee is present, regardless of what his/her schedule and other definitions indicate for them.

This time type must be defined as time category 0.

… the time type to which missing time is connected.

Missing time is any time that is left over after the time calculation subtracts the employee's in/out records from his/her scheduled time if no reason for absence has been specified.

This time type must be defined as time category 6.

… whether the employee has the right to vary his/her workday.

This means that employee can affect his/her starting and finishing times but that the number of hours that the employee is to complete per day (as defined by his/her calendar) is not affected or changed.

The valid alternatives are

0 = No

1 = Yes.

The employee only has the right to utilize the variable workday functionality if he/she clocks in/out using ordinary time.

… the number of minutes by which the employee's clock-in must differ from the start of his/her ordinary work hours before the variable workday function is activated.

This field is used in combination with the 'Variable workday' field.

… a user-defined time type attached to a number of minutes to be generated each day that the employee is in attendance.

Example

This can be useful for companies that apply a certain number of minutes worked daily to compensate for company holidays.

… the time type to which run time is connected.

This time type must be defined as time category 0.

… the time type to which setup time is connected.

This time type must be defined as time category 0.

… whether the employee is a piece rate worker.

The valid alternatives are

0 = No

1 = Yes.

… the date to which date the employee's times have been calculated in Time and Attendance.

When entering an employee record for the first time, enter the date before the employee will actually start his/her employment. Subsequently, the field will automatically be updated and must not be changed manually.

… the date to which the employee's time transactions have been transferred to the history or payroll.

When entering an employee record for the first time, enter the date on which the employee starts his/her employment. Subsequently, the field will automatically be updated and must not be changed manually.