Human Resource Management in Workday HCM
Core concepts
Workday HCM organizes people around a worker record, which links to a position (if positions are managed) or stands alone. A worker can hold multiple jobs, be a contingent worker, or be a pre-hire. Supervisory organizations define reporting lines and drive security and approval routing; company, cost center, and location are separate hierarchies. Business processes (hire, change job, terminate, transfer) are configured with steps, approvals, and conditional routing. Effective dating is the central mechanic: every change is future-dated or back-dated and the system keeps history, so questions often hinge on what a record looks like as of a date.
Traps
- Confusing supervisory organization (who reports to whom) with company or cost center (financial/legal structures).
- Assuming a termination deletes history - it does not; the worker becomes terminated as of an effective date.
- Mixing business process policy (who approves) with security group membership (who can see/do).
- Forgetting that requisition-based and position-based hiring differ in what must exist first.
Rule of thumb
Read every scenario as "as of what date, and which organization type?" If the question asks who approves, think business process routing; if it asks who can view, think security group and domain policy.
Worked example
An employee transfers from Company A to Company B on the 1st. A question asks which cost center their prior paycheck reflects. Answer: the pay period and effective date govern - the change job is effective the 1st, so time before that date belongs to the old organization. Anchor on effective date, not on when the transaction was entered.