To budget for future headcount and related personnel expenses (e.g., salary, benefits, taxes) in Oracle Planning 2024, the Workforce module must be enabled and configured. This module is specifically designed for detailed employee planning, including:
A . Financials: Incorrect. Financials focuses on revenue, expense, and financial statement planning at an aggregated level, not detailed headcount or personnel expenses like benefits and taxes.
B . Strategic Modeling: Incorrect. Strategic Modeling is for high-level scenario analysis (e.g., mergers, long-term strategies), not granular headcount budgeting.
C . Sales Planning: Incorrect. Sales Planning (if available as a custom module) targets sales forecasts and quotas, not employee-related expenses.
D . Workforce: Correct. Workforce enables budgeting for headcount (e.g., hiring plans) and calculates associated costs-salaries, benefits (e.g., health insurance), and taxes (e.g., payroll taxes)-with predefined and customizable options.
The Oracle documentation confirms that Workforce is the module tailored for headcount and personnel expense budgeting, making D the correct answer.
Oracle Planning 2024 Implementation Study Guide: "Overview of Workforce Module" (docs.oracle.com, Published 2024-10-05).
Oracle EPM Cloud Documentation: "Planning Personnel Expenses" (docs.oracle.com, Published 2023-11-25, updated for 2024).

In Oracle Planning 2024, approval units manage the review process. The two true statements are:
A . You can have up to three scenario/version combinations per approval unit: Incorrect. There's no strict limit of three scenario/version combinations per approval unit; multiple combinations are possible based on hierarchy design.
B . Approval units are combinations of scenario, version, and entity or part of an entity: Correct. Approval units are defined by Scenario (e.g., Budget), Version (e.g., Working), and Entity (e.g., Department) or entity hierarchies, forming the basis of the approval process.
C . Approval units can also include secondary dimensions within any entity: Correct. Secondary dimensions (e.g., Product, Project) can be added to approval units within an entity to refine the scope of approval.
D . You can set the option in Application Settings to include detailed annotations for approval units: Incorrect. Annotations are cell-level notes, not an Application Settings option tied to approval units; they're managed separately.
The Oracle documentation confirms B and C as accurate descriptions of approval units, making them the correct answers.
Oracle Planning 2024 Implementation Study Guide: "Approval Units Overview" (docs.oracle.com, Published 2024-09-15).
Oracle EPM Cloud Documentation: "Configuring Approval Units" (docs.oracle.com, Published 2023-12-10, updated for 2024).

In Oracle Planning 2024 Implementation's Workforce module, configuring merit-related settings for employees involves specifying eligibility criteria and timing, such as a hire date cutoff for existing employees to receive merit increases and the month when merit adjustments begin. The Merit Assumptions option is the correct choice for this purpose.
B . Merit Assumptions: This feature allows administrators to define merit-related parameters, including the "hire by" date (the date by which employees must be hired to be eligible for merit) and the "merit start month" (the month when merit increases take effect). It provides a centralized way to set these assumptions, ensuring they are applied consistently across the workforce plan.
A . Workforce Assumptions: This option covers broader workforce settings (e.g., default hire dates, salary assumptions), but it does not specifically address merit eligibility or timing details like hire-by dates or merit start months.
C . Merit Rates: This pertains to defining the percentage or amount of merit increases, not the eligibility dates or start month for merit application.
D . Merit Month: While this might seem relevant, "Merit Month" is not a standalone option in Workforce. It is a setting typically configured within Merit Assumptions, not an independent feature.
The Merit Assumptions option is explicitly designed to handle these merit-specific configurations, making it the most suitable choice.
Oracle Enterprise Performance Management Cloud Documentation: "Administering Workforce - Merit Assumptions" (docs.oracle.com, updated 2024). States that "Merit Assumptions allow setting the hire-by date for merit eligibility and the merit start month." Oracle Planning 2024 Implementation Study Guide: Confirms that Merit Assumptions is used to specify eligibility criteria and timing for merit increases in Workforce.