Recording Employee Movement Checklist
Select “Record Employee Movement Checklist” from the left pane.
The “Record Employee Movement Checklist” page appears.
The system displays the following.
Date Format |
The date format applicable to the login user. |
Enter the following.
Employee Movement Unit |
From the drop-down list box, select the employee movement unit. |
Employment Unit |
From the drop-down list box, select the employment unit. |
Movement Type |
From the drop-down list box, select any one of the following movement types
|
Grade Set |
From the drop-down list box, select the grade set. |
Grade |
From the drop-down list box, select the grade. |
Work Location |
From the drop-down list box, select the work location. |
Department |
The department to which the employee belongs. Help available |
Position |
The position of the employee. Help available |
Note: The option 'ALL' listed in drop-down list boxes, Grade Set, Grade, Work Location and '*' for Position and Department, would also be considered as a value.
Example, if there is a definition for Grade Set GS1, Grade G1, and Work Location 'ALL' mapped to a role, then another definition for the Grade Set GS1, Grade G1, and Work Location WL1 would not be allowed.
Select the “Get” pushbutton.
The system displays the following in the “Role Checklist Mapping” multiline, if the role checklist mapping exists for the selected criteria.
Alternatively, the system only displays the S# and Role in the “Role Checklist Mapping” multiline at the first instance.
S# |
The serial number in the multiline. |
Role |
The role to which the employee must be mapped to maintain the checklist against the role. Example, HR, Admin |
Note: The Role may be system defined or User defined. Examples of System Defined Role are: Supervisor, Functional Supervisor 1, Functional Supervisor 2, Administrative Supervisor, Final Authorizer. and Department Supervisor. Examples of User defined roles are HR Role, Admin, Library etc. User defined roles are defined through Quick codes. Mapping between Movement type, Role and Check list is done in Additional Masters for Master ID – MVCHK( Movements Checklist) where, Key 1 is Employee Movement unit code, Key 2 is Employment unit code. Parameters are used to store attributes. Parameter1 for Movement Type , Parameter2 for Role and Parameter3 for Checklist .
Example: Parameter1 – P00 (Promotion)
Parameter2 – ADMIN (Administration)
Parameter3 – SWCRD(Swipe Card)
Multiple Checklists under multiple roles could be defined for a selected movement type.
Enter the following in the “Role Checklist Mapping” multiline at the first instance.
Checklist Description |
The description of the checklist. Example, ID Cards or Keys. |
Employee Code |
The unique code of the employee. Help available |
Employee Name |
The name of the employee. |
To indicate whether a history of the modifications must be maintained
Enter the following.
Modification Option |
Select “Correct” or “Update” from the drop-down list box.
|
New Effective From |
If the edit option you chose is “Update”, specify the date from which the current modification will be in effect. The system maintains the “Effective To Date” of the previous record to be one day less than the “New Effective From” date. |
Select the “Previous” pushbutton beside the “Data Access History” field, to view the previous changes, if any, made to the selected role-checklist mapping.
If no previous record exists, the system will display the current record.
Note: When you click “Previous” pushbutton, the system will display the previous record in the database, provided you had chosen “Update” in the “Edit Option” drop-down list box.
Select the “Next” pushbutton in the “Access Data History” field, to view the next change of the role-checklist mapping.
Select the “Save” pushbutton to save the details.
6 Hyperlinked text below
Use this page to record or edit the employee movement checklist.