Concepts

This module tracks each employee's history at your company. Their status, their salary, their job and/or position, their department, etc.

Every time there is a change to the employee's status, a new history record (a movement) is created, with a new effective date.

• A movement's end date is the start date of the next movement.
• The first movement is their HIRE.
• The last one is (usually) the employee's current status, which may be terminated (TERM). This movement has no end date.

The person module also keeps the employee's current status, picked up automatically from this employment history module.

Level of detail

Movements are infrequent. Most employees will only have a few each year:

• Cost of living raise, seniority raise or grade advancement. Maybe changing schedule or job or department, etc.

Daily variations, such as performing different jobs, go in the Attendance Detail (TIMEDT) module. Other changes might be events. A vacation absence, for example, belongs in attendance detail, not JOBHIST.

• Think of the JOBHIST changes as the low frequency long waves, and the TIMEDT transactins as the high-frequency waves.

Movements

A movement is a change in the employee's status, e.g. a hire, pay increase, transfer, change in job title, layoff, etc. Normally, the employee's last movement specifies his/her current status.

Every movement – from it's effective date to end date – describes a slice of time in the employee's work life. It is a snapshot of that period, with all the data fields filled in about him/her at that moment. Together, they create a complete history of the employee.

Someone's employment history should be a history what actually happened to them. If there is an error here, correct it. It is not meant to be an audit trail of what you entered and corrected.

• Do not enter new movements to make corrections – just correct the error.
• Do not change a record when the employee's status (in real life) changes – instead, create a new movement

Major/minor movements

Some movements involve a change in the employee's employment status, e.g. a hiring movement could involve the active employee status. Other movements do not affect employment status.

• Each movement has a code from the JACTION table. In this table, you can optionally associate a new employment status with a movement.

  A movement with an associated employment status, such as a hire or termination movement, is called a "major movement". Applying it to an employee, changes their employment status (JSTAT).

Entering data

Add to change

To report a new employee status, you must add, from the Employment history window, a new movement in JOBHIST file (usually at the end, with a date later than the others). There you can also correct a movement already entered for an employee, or even add a new movement to the history.

Entering a new movement

When enter a new movement: once you enter the date, Umana fills in the employee status as of that date. You just need to enter what has been changed.

• You will mostly be entering new movements, dated after the last one on file.
• You can enter a movement in between two others: an intermediate movement. Umana fills in the status information for that date, and your change represents a the employee's status at that moment. Changes are NOT automatically propagated to subsequent movements.

All changes save at once

The Employment history window is unique in that you can modify many records (movements) for a single employee before saving. So as long as you are in Edit mode, you can delete a movement and the deletion will only be saved (permanently) once you click on Save.

Employees and their managers

An employee's manager can be specified explicitly, or implicitly, or by following the hierarchy of the positions he holds. For a full discussion see Supervision and Reporting relationships