In Oracle Planning 2024, Groovy Rules enhance business logic flexibility. Oracle supports two main types of Groovy Rules:
A . Rules that overwrite member formulas that combine operators and calculation functions, and perform calculations on members in Dimension Editor: Incorrect. Groovy Rules do not overwrite member formulas in the Dimension Editor; they operate at runtime and are defined in the Rules editor, not as static dimension overrides.
B . Rules that can dynamically generate calculation scripts at run time based on contexts such as runtime prompts, the POV, the current grid, and so on: Correct. Oracle supports Groovy Rules that generate dynamic calc scripts based on runtime contexts (e.g., POV, grid data, prompts), enabling adaptive calculations.
C . Pure Groovy rules that can perform data validations and cancel the operation if the data entered violates company policies: Correct. Pure Groovy Rules can validate data (e.g., checking ranges or policies) and cancel operations (e.g., via exceptions), a key feature for enforcing business rules.
D . Rules that dynamically calculate data and perform validation checks in tile charts and infolets: Incorrect. Groovy Rules operate on cubes and forms, not directly within tile charts or infolets, which are UI elements driven by underlying data, not rule execution points.
The Oracle documentation confirms B (dynamic script generation) and C (data validation) as supported Groovy Rule types, making them the correct answers.
Oracle Planning 2024 Implementation Study Guide: "Groovy Rules in Planning" (docs.oracle.com, Published 2024-10-15).
Oracle EPM Cloud Documentation: "Supported Groovy Rule Types" (docs.oracle.com, Published 2023-11-20, updated for 2024).

In Oracle Planning 2024's Projects module, revenue and expense calculations are driven by specific assumptions that influence project financials. The three types of assumptions that directly drive these calculations are Working days and hours, Standard rates, and Project rates:
A . Working days and hours: This assumption defines the available time for project execution (e.g., days per week, hours per day), directly impacting labor costs and revenue projections based on resource utilization.
C . Standard rates: These are predefined rates (e.g., hourly or daily rates for labor or equipment) applied across projects unless overridden, driving cost and revenue calculations consistently.
E . Project rates: These are project-specific rates that override standard rates when defined, allowing for tailored revenue and expense calculations based on unique project requirements.
B . Plan start year: This is incorrect because, while it sets the timeline for planning, it does not directly drive revenue or expense calculations-it's a temporal parameter, not an assumption affecting financial data.
D . Program mappings: This is incorrect because program mappings relate to integrating data across programs, not driving revenue or expense calculations within Projects.
Oracle Planning 2024 Implementation Study Guide: "Configuring Projects Assumptions" (docs.oracle.com, Published 2024-10-10).
Oracle EPM Cloud Documentation: "Revenue and Expense Planning in Projects" (docs.oracle.com, Published 2023-11-25, updated for 2024).
F). Discount rates: This is incorrect because discount rates are used for net present value (NPV) or financial analysis, not as a direct driver of revenue and expense assumptions in Projects.