Positions Manage Data Requirements
Positions Data Overview
Positions are approved full-time equivalency units of a job in a location.
Positions Data Elements
Element | Description | Example |
|---|---|---|
Code | Unique identifier for a position, often a position control number or position number. | 4158 |
Job Code | Unique identifier for the job this position is for. | 4627 |
Location Code | The work location/payroll location/home location of this position. | 106 |
FTE | The FTE approved for this position. | 1.0 |
Start Date | The first date the position is valid for an employee to hold an assignment in this position. | 2014-07-05 |
End Date | The last date the positions is valid for an employee to hold an assignment in this position. | 2019-06-30 |
Positions are unique by code and start_date. The end_date may be NULL, and is expected to be filled in when a position becomes inactive for assignment. All other fields are required. Imports and uploads with the same code and start_date will update all other fields. The location_code is a string value that is meant to represent the payroll work location or home location or similar concepts found in most HR systems. This is where someone reports to work or based on who their manager is. This data can be used as part of our permissions for who can view certain positions.
Positions Data Validations
code, job_code, location_code, fte, and start_date are not null.
code and start_date are unique.
job_code matches an existing job.
fte greater than or equal to 0.
start_date less than end_date OR end_date is NULL.