Managing Global HR Data and Transactions

Key points the exam tests

• Contingent Workers are contractors/temps tracked in HCM for directory, security, and journeys purposes without full payroll processing.
• Pending Workers have all basic personal data entered before their start date, allowing access provisioning and onboarding journeys to begin early.
• 'Correct History' modifies a past record in-place (changing history). 'Update' creates a new effective-dated row going forward — preserving history.
• AORs define which HR person is responsible for which workers/BUs, routing tasks and controlling which records the HR specialist can view.
• Rehire creates a new Work Relationship under the existing Person record — avoiding duplicate person records in the system.
• The Assignment is where the actual 'what job, what department, what grade, who they report to' details live, nested under a Work Relationship with a Legal Employer.
• Seniority Dates track service-length milestones that can differ from the original hire date (e.g., adjusted for breaks in service or specific plan rules), used to drive eligibility for certain benefits or recognition.
• Manager Self-Service exposes common HR transactions (promotion, transfer, compensation change) directly to line managers, reducing dependency on HR for routine actions.
• Manager-initiated self-service transactions are typically routed through approval rules and notifications — the transaction doesn't take effect until the approval chain completes.
• Document Records let HR store, categorize, and track expiry of worker compliance documents, distinct from general employment records.
• Person (core identity) sits above Work Relationship (link to a Legal Employer), which sits above one or more Assignments (the specific job/position/department details).
• Resource Alerts can be configured to query Document Record data on a schedule and notify HR when documents (like visas) are approaching expiry.
• When a manager submits a self-service HR transaction, the workflow/approval engine generates notifications routing the request to the appropriate approver(s).
• Contingent Workers (contractors, temps) are tracked in HCM — appearing in directories, subject to security, potentially included in journeys — without being run through the employer's own payroll.
• The Hiring flow is a guided process that captures the full set of data — personal info, work relationship, and assignment details — required to properly establish a new worker in the system.
• The Assignment is where day-to-day employment specifics live — job, position, department, grade, reporting line, and FTE — distinct from the higher-level Work Relationship and Person records.
• This layered model supports scenarios like a worker holding two concurrent part-time assignments under a single employment relationship — a single combined record couldn't represent that flexibly.
• Document Records store the document and its expiry date; combining this with alerting capability lets HR get proactively notified before a compliance document lapses.
• Manager self-service transactions are still subject to the organization's approval workflow configuration — the routing/oversight happens through Approval Rules, not by restricting who can initiate the transaction.
• Seniority Date exists precisely to decouple 'length of service for eligibility purposes' from the literal Hire Date — useful after breaks in service, transfers, or M&A situations.
• Work Relationship links a Person to a Legal Employer; the Assignment captures the specific job/position/department details — together these define employment, distinct from security or journey objects.