Configuring Core HCM

Key points the exam tests

• A Legal Employer is a type of Legal Entity that employs workers and is the base for employment relationships in Oracle HCM.
• RDS partitions reference data so it can be shared (Common Set) or isolated per Business Unit — controlling which BUs share jobs, grades, departments, etc.
• Position Management pre-defines slots (positions) with headcount budgets, enabling vacancy tracking and hiring approval against approved positions.
• LDGs partition by country legislation. Each country's payroll statutory rules are separate, so 3 countries = 3 LDGs.
• The hierarchy flows: Enterprise (top) → Legal Entity (registered company) → Business Unit (operational) → Department (organizational unit).
• Geography Structures define the hierarchy of Geographic Entities (country, state, city, postal code) used for address validation and geography-based reporting.
• Geography Validation checks entered address data (state, city, postal code) against the configured Geography Structure to prevent inconsistent or invalid address entries.
• Work Schedules define the standard working pattern (days, hours, shifts) assigned to workers via their assignment, used by absence duration and time calculations.
• Organization Trees visually represent how organizational units relate to each other, supporting hierarchical reporting, security profile scoping, and analysis of the HCM structure.
• Salary Basis is a foundational compensation setting configured early — it defines the pay frequency/unit (hourly, monthly, annual) that grade rates and worker salaries are expressed against.
• Reference Data Sets give fine-grained control: some reference data (like a common Job list) can be shared across all BUs via a Common Set, while other data (like Departments) can be scoped to a single BU.
• System-wide settings and profile options let implementers customize enterprise-level defaults and behaviors early in the configuration process, before workforce structures are built on top.
• Work Schedules determine which days/hours count as scheduled working time — changing it directly affects how absence duration and other time-based calculations are computed going forward.
• The choice between Job and Position Management is a foundational configuration decision typically set at the Legal Employer or Business Unit level, shaping how workforce structures are administered thereafter.
• RDS partitioning is configured per object type, so an implementer can choose a Common Set for Departments while assigning BU-specific sets for Jobs — full flexibility per data type.
• A Legal Employer is linked to the LDG matching its operating country/legislation, ensuring the correct statutory payroll and compliance rules apply to workers under that employer.
• Enterprise Structures form the foundation that Reference Data Sets, workforce structures, security profiles, and payroll setup all build upon — hence they're configured first in an implementation sequence.
• While a Grade defines a single pay band/level, a Grade Ladder sequences several grades or steps together to represent a career/pay progression path within an organization.
• Business Units are an operational/reporting concept, not strictly tied to legal structure — the decision is driven by how the organization wants to partition data and operations, which can differ from its legal entity count.
• Work Schedules are foundational objects configured ahead of time (defining working days/hours/patterns) before they can be assigned to any worker's assignment record.
• Legal Entity and Business Unit are core Enterprise Structure objects, foundational to setup. Journey Templates, Approval Rules, and Sandboxes are configured later, on top of this foundation.