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).

To track the utilization of employees in the Projects module of Oracle Planning 2024, the Workforce module must be enabled first. Employee utilization in Projects refers to tracking how employees' time and costs (e.g., hours worked, labor expenses) are allocated to specific projects. The Workforce module provides the foundational data-such as employee details, roles, salaries, and hours-required to calculate utilization metrics. Once Workforce is enabled and configured with employee data, the Projects module can leverage this data via integration to track utilization against project tasks and budgets.
A . Projects module before Financials module: Incorrect. Enabling Projects before Financials does not address employee utilization tracking, as Financials focuses on revenue and expense planning, not employee-specific data.
B . Financials module before Projects module: Incorrect. Financials provides financial planning capabilities but does not manage employee data or utilization, which is a Workforce function.
C . Workforce module before Projects module: Correct. Workforce must be enabled first to define employee data, which Projects then uses to track utilization through integration (e.g., via data maps or direct links).
D . Projects module before Workforce module: Incorrect. Enabling Projects first without Workforce would limit utilization tracking, as Projects relies on Workforce for employee-related data.
The Oracle documentation specifies that Workforce is a prerequisite for detailed employee utilization tracking in Projects, making C the correct sequence.
Oracle Planning 2024 Implementation Study Guide: "Integrating Workforce with Projects" (docs.oracle.com, Published 2024-09-20).
Oracle EPM Cloud Documentation: "Tracking Utilization in Projects" (docs.oracle.com, Published 2023-12-15, updated for 2024).