In Oracle Planning 2024’s Workforce module, Merit-Based Planning involves planning salary increases or adjustments based on employee performance (merit). To perform this, you need workforce data at a level of granularity that includes individual employee details. The two levels required are:
A. Merit: Incorrect. "Merit" is not a granularity level; it’s a planning concept or assumption applied to employee data, not a structural level of detail.
B. Employee and Job: Correct. This level combines employee-specific data (e.g., individual identity) with job-specific data (e.g., role, grade), enabling merit-based adjustments tailored to both the person and their position.
C. Job: Incorrect. Job-level granularity (e.g., aggregated data for a role) lacks individual employee details, which are necessary for merit-based planning.
D. Employee: Correct. Employee-level granularity provides the individual data (e.g., current salary, performance rating) needed to calculate merit increases for specific employees.
Merit-Based Planning requires at least Employee-level detail, and often Employee and Job for more precise planning (e.g., tying merit to job roles or grades). The Oracle documentation confirms these as the key granularity levels for this functionality, making B and D the correct answers.
[References: , Oracle Planning 2024 Implementation Study Guide: "Merit-Based Planning in Workforce" (docs.oracle.com, Published 2024-10-10). , Oracle EPM Cloud Documentation: "Workforce Granularity Levels" (docs.oracle.com, Published 2023-11-15, updated for 2024)., , ]
Submit