Job
ConceptfoundationA reusable definition of a role, holding an effective start date, a job set, a name and a code that is unique within its set, plus the grades valid for it. It describes the work, not the person doing it.
What people get wrong
The confusions are the difficulty. Each one is a belief that sounds right and is not.
- That a job belongs to a person. It does not: the person belongs to a job through an assignment, and the same job can be held by several people at once.
- That the grades you list against a job are enforced. They are advisory unless PER_ENFORCE_VALID_GRADES is set to Yes, and its documented default is No.
Recall it
What does a job hold, and what makes it reusable rather than belonging to a person?
A job holds an effective start date, a job set, a name and a code that must be unique within its set, plus the grades valid for it. It is reusable because it describes work rather than a person: several people, often in several positions and business units, hold the same job at once, so a rule written against the job reaches every holder. A code created in the Common set cannot then be created in any other set.
Memory hook: A job is the noun. Describe the work once and let the people come and go.
Rests on COREHR-JOB-001, COREHR-JOB-002.
Taught in
Related
- Terminology glossary — what a term means, and what people get wrong when they use it