Position changes will be requested via EAF for existing employees or via Kenexa Brass/Ring for changes to vacant or soon to be vacant positions.
Changes can be made as date tracked updates or may require that a new position version is created and the prior version is ‘Eliminated’.
Date tracked changes (updates) when change in:
- Grade
- FTE
- Any DFF field […] (Comp Codes, IPEDS, etc)
- Date Effective Name (Number, Funding, Version, Title)
- Title is only updated if there is a spelling or other error that did not require a new JDQ
New Version must be created when there is a change in:
- Title change due to new JDQ or job duties
- Job change (see mapping document - Job classifications.xlsx)
- HR Organization change
Position change scenarios and approvals:
General workflow in OnBase (changes for existing employees)
- EAF is in HRA Approve Queue with all approvals, notes and supporting documentation
- Comp and HRA have reviewed and updated EAF with Notes added to EAF
- JDQ is uploaded into OnBase by Comp
- Position is created with appropriate effective date (generally the first of the month of the date of the change) – new JDQ is added (download from OnBase and add to paperclip)
- Position is added to employee assignment with appropriate effective date
- Prior version of position change status to ‘Eliminated’ same day as assignment change date
General workflow in Kenexa BrassRing (changes for current vacant positions)
- Requisition routed for approval for position changes
- Comp has reviewed and uploaded JDQ as attachment to req
- Position is created with appropriate effective date (generally the first of the month of the change)– new JDQ is added (download from Kenexa and add to paperclip)
- Run integration from Oracle (eBiz) to Kenexa Brass/Ring
- Requisition is updated with new version and approved to move on in approval chain
- Prior version of position change status to ‘Eliminated’ if no current occupant