H2R 202 · SHAPE
Workforce structures define where work belongs before a person is hired.
Legal entities, business units, departments, jobs, positions, locations, and cost objects connect people decisions to security, workflows, payroll, and reporting.
HR MANAGER LENS
What must the business decide?
This capability becomes useful only when policy, ownership, employee experience, controls, measures, and exceptions are explicit.
Operating model
Decide which legal entities, business units, departments, locations, jobs, and positions represent how work is governed.
Position control
Decide when an approved position is mandatory, who may create or change it, and how vacancy and headcount are controlled.
Propagation
Agree which position attributes should flow to an incumbent and which employee values remain deliberately independent.
Governance
Name owners for structure changes, effective dates, approvals, cost ownership, and exception resolution.
ACCOUNTABILITY
Who owns what?
HR / organisation design
Owns structure policy, job architecture, and effective-dated changes.
Manager
Requests positions and validates reporting, location, and work requirements.
Finance / workforce planning
Confirms budget, headcount, cost centre, and reporting impact.
ONE RECORD TRAIL
Follow one decision into its successor evidence
These records are connected, but they do not share one owner, date model, permission boundary, or completion status.
- 01AUTHORIZEWorkforce request or approved headcount
Business purpose, owner, budget, country, timing and approval establish why work may exist.
- 02STRUCTUREPosition and foundation objects
Position, parent position, job, legal entity, department, location and cost centre establish where work belongs.
- 03ACTIVATEJob Information or requisition
The approved structure becomes employee assignment or recruiting demand with an effective date.
- 04PROVEWorkflow, sync result and downstream reference
History, approval, position-to-job result, requisition or incumbent record explain the outcome.
CONSULTANT LENS
How SAP represents the capability
Position is an MDF object connected to Job Information and shared foundation objects such as Legal Entity, Business Unit, Division, Department, Location, Job Classification, Pay Grade, and Cost Center. Position-to-Job Information synchronization, event reasons, workflows, and RBP determine what propagates and who may act.
DIAGNOSTIC EVIDENCE
Diagnose using the owning record and hand-off
Separate an undesired business result from missing setup, failed execution, wrong effective date, insufficient permission, or broken integration.
Position code, status, effective dates, parent position, job, organisation, location, cost centre, incumbent and vacancy state.
Workflow, change reason, permission target population, position-to-job sync result, admin alert and correction history.
Requisition reference, incumbent Job Information, payroll/cost allocation impact, reporting hierarchy and integration event.
OPERATING VIEW
Exceptions and measures that deserve ownership
Common exceptions
- Position exists but is not approved or vacant
- Position and incumbent Job Information disagree
- Future-dated hierarchy is correct but current view is used
- Manager can view or create outside the intended population
Useful measures
- Approved versus unapproved positions
- Vacancy age and position-fill rate
- Position-to-job synchronization exceptions
- Positions without valid owner, cost centre, or reporting line
WORKED SCENARIO
One decision carried into system evidence
A new warehouse shift requires twelve positions. HR creates them under the approved department and manager; Finance confirms the cost centre and headcount. A future-dated change moves the positions next month without rewriting current reporting history.
- When is a position required before recruiting?
- Which fields propagate to Job Information?
- Who may create, correct, insert, or deactivate a position?
- How are reorganisations dated, approved, tested, and communicated?
Connect this capability to lifecycle hand-offs, integration ownership, payroll, Finance, and exception triage.