Job and position structures

Configure the job structure — the flexfield defining what attributes a job carries — then the position structure the same way. Set the code generation method: manual, automatic, or rule-based. Deploy, and verify. Then look at what an undeployed structure looks like on the create page. Same deployment lesson as any flexfield: nothing appears until you deploy, and seeing the before state is the fastest way to make that stick. Code generation matters for data loading later. Automatic codes and a bulk load can fight each other, so decide the code strategy before you get to the data loading module rather than during it. And structures are hard to change once objects exist, so design the attributes with HR before building — a small instance of this module's whole argument.

In this module: Module 6 · Jobs and Positions

1. 1The decision that shapes everythingFree preview
2. 2Jobs and job catalogue design
3. 3Job and position structures
4. 4Creating jobs
5. 5Positions: what they add
6. 6Creating positions
7. 7FTE, work hours and workday defaults
8. 8Position synchronization
9. 9Configuring position synchronization
10. 10Position hierarchies
11. 11Evaluation criteria and valid grades
12. 12Position approvals
13. 13Loading workforce structures by spreadsheet
14. 14What breaks
15. 15Lab briefing: one model, or two?