Record assignments, jobs and working patterns
An assignment records where and how an employee works during a period. It links to that employee's employment. Only one primary assignment can cover a date; concurrent job splits are not implemented here.
Fields
| Field | Rule | Example |
|---|---|---|
| Employment Id | Required, existing employment for this employee | First employment |
| Effective From / To | Required start, optional inclusive end; contained in employment | 1 October onward |
| Business Unit Id | Required authorised existing unit | BHS-NORTH |
| Manager Employee Id | Optional accessible employee; no reporting cycle | Jonah's Employee ID |
| Department Code / Position Code | Optional text, max 50 each | SUPPORT / OFFICER |
| Job Title | Required, max 150 | Support Officer |
| Job Grade / Cost Centre Code / Location Code | Optional text, max 50 each | G2 / OPS-N / NORTH |
| Work Arrangement | Required: ONSITE, HYBRID or REMOTE | HYBRID |
| Fte | Required 0.01–1.0; up to four decimals | 0.8000 |
| Weekly Hours | Required 0.01–168; up to two decimals | 30.00 |
| Work Schedule Code | Optional text, max 50 | DAY-4 |
| Change Reason | Required, max 500 | Initial approved assignment |
Add and verify
- Open employee detail → Assignments → Add assignments.
- Select the correct Employment Id and effective dates.
- Select the unit and, if applicable, manager using employee-number search.
- Enter job facts, arrangement, FTE, weekly hours and approved reference codes.
- Enter the reason, save, reload and verify the full record.
FTE/hours are independent inputs. Recording 0.8 FTE and 30 hours does not cause the application to infer a full-time week, schedule attendance or calculate pay. Reference codes are text, not automatically created department/position masters.
Transfer example
Amira moves from North to South on 1 December. End the North assignment on 30 November, save and verify. Add the South assignment from 1 December within the same employment where appropriate. Review manager, cost centre, work pattern and reason explicitly.
Assignment changes do not grant Amira's login access to South or revoke North grants. Historical assignment/employment relationships can still make the master visible to existing unit-scoped HR users. Review login access separately in Administration.
Recovery
An overlap means the predecessor remains open or shares a day. A missing employment choice can mean its employer unit is outside your scope or employment-view lookup rights are missing. A manager rejection can mean scope or a cycle; do not substitute a User ID. A failed successor save does not undo a previously saved predecessor closure. Reload and complete the approved timeline.