Personnel Actions
Promotions, transfers and pay changes, each approved by somebody other than whoever asked and applied to the employee on the day it takes effect — with the history of what changed from what.
Where to find it
Address in the console: /hrms/personnel-actions
List · 26 columns · 10 fields on its form · 3 of them required · 5 actions
Records here are not deleted. Where something must be undone it is reversed or superseded, so the trail survives.
What the list shows
These are the columns of the list, in the order they are drawn. Any of them can be sorted on, filtered on, hidden, or exported.
| Column | Kind | Field name |
|---|---|---|
| Action | Code | action_no |
| Employee | Code | employee_no |
| Name | Text | employee_name |
| Type | Status | action_type |
| Effective | Date | effective_date |
| From position | Text | from_position_title |
| To position | Text | to_position_title |
| From manager no. | Code | from_manager_no |
| From manager | Text | from_manager_name |
| To manager no. | Code | to_manager_no |
| To manager | Text | to_manager_name |
| From unit | Text | from_org_unit_name |
| To unit | Text | to_org_unit_name |
| From pay | Amount | from_base_pay |
| To pay | Amount | to_base_pay |
| Pay change % | Number | pay_change_pct |
| From pay type | Text | from_pay_type |
| To pay type | Text | to_pay_type |
| From work region | Text | from_work_state |
| To work region | Text | to_work_state |
| Status | Status | status |
| Reason | Text | reason |
| Why the type fits | Text | type_override_reason |
| Why rejected or cancelled | Text | rejected_reason |
| Rejected or cancelled by | Text | decided_by_name |
| Rejected or cancelled on | Date | decided_at |
The form
What is asked for when a record is created here. Required fields are marked; a choice drawn from a configuration list is one an administrator can extend without a release.
| Field | Type | Choices | Notes |
|---|---|---|---|
| Employee required | Choice | Looked up from existing records | |
| Type required | Choice | promotion, demotion, transfer, pay_change, reorganisation, data_correction | |
| Takes effect on required | Date | ||
| Reason | Long text | ||
| New position | Choice | Looked up from existing records | |
| New manager | Choice | Looked up from existing records | A current employee other than the person this action is for. |
| New organizational unit | Choice | Looked up from existing records | |
| New base pay | Number | ||
| New pay type | Choice | salary, hourly | |
| New work region | Text |
What you can do here
Submit primary
Asks for confirmation: Send this for approval? It cannot be edited once submitted.
Asks for: Why the type fits (only if asked)
Approve primary
Asks for confirmation: Approve this change? Dated today or earlier, it is applied to the employee at once; otherwise on its date.
Reject
Reject this personnel action
Asks for: Why*
Make effective
Asks for confirmation: Apply this change to the employee now? Refused before its date.
Cancel
Cancel this personnel action
Asks for: Why*
* required
The rules that apply here
Everything on this screen obeys the platform rules rather than rules of its own. The ones worth knowing before you use it:
- Narrowing a list — search, conditions, sort, totals, export and saved views.
- What may be changed — the five grounds a record may not be edited on.
- Companies and business units — what the switcher above this list is doing to it.
- Creating a record — required fields, where choices come from, and how the number is allocated.
- Importing a spreadsheet — this screen accepts one, and it runs through the same rules as typing.