In Oracle Planning 2024 Implementation, business rules are essential for automating calculations, data manipulations, and complex logic within the application. The platform provides multiple features to assist users in creating these rules efficiently, as outlined in the Oracle documentation. The two features that directly help users create business rules are:

A . Add calculations by using preformed system templates, such as clearing data, copying data, aggregating data, and so on: Oracle Planning offers predefined system templates that simplify rule creation. These templates enable users to quickly implement common operations like clearing data, copying data between dimensions, or aggregating data without writing complex code from scratch. This feature is particularly useful for users who may not have advanced scripting skills, as it provides a guided, template-driven approach to rule design.

C . Design sophisticated rules that solve use cases that normal business rules cannot solve by using Groovy business rules: Groovy business rules extend the capabilities of standard business rules by allowing users to write custom logic using the Groovy scripting language. This feature is designed for advanced use cases, such as dynamic calculations based on runtime conditions or complex data manipulations that go beyond the scope of traditional rules. It empowers users to address specialized business requirements efficiently.

B . Add calculations in calculation script syntax by switching to Script Mode: While Script Mode exists and allows users to write calculations using a script-based syntax (e.g., Essbase calc scripts), it is not highlighted as a primary 'feature' for creating business rules in the Oracle Planning 2024 context. It is more of a mode of operation rather than a distinct feature assisting rule creation.

D . Rules are represented graphically in a flow chart into which you can drag and drop components to design the rule: Although graphical rule design was a feature in older Hyperion Planning versions (e.g., Calculation Manager's graphical interface), Oracle Planning 2024 documentation does not emphasize a drag-and-drop flowchart interface as a current primary method for rule creation. Instead, it focuses on templates and Groovy scripting.

Reference

Oracle Enterprise Performance Management Cloud Documentation: 'Working with Business Rules' (docs.oracle.com, updated 2024). This section details the use of 'system templates for calculations' and 'Groovy business rules' as key features for rule creation.

Oracle Planning 2024 Implementation Study Guide: Confirms that predefined templates (e.g., for clearing or aggregating data) and Groovy rules are core features to assist users in designing business rules.

When designing reports in Oracle Cloud EPM Planning using Report Designer, data sources and report objects (e.g., grids, charts) have specific capabilities. The two true statements about data sources in reports are:

A . Insert charts in the report header to provide a quick visual summary of data: Incorrect. Report Designer does not support inserting charts directly into the report header; charts are added as objects within the report body, linked to data sources.

B . Include a chart in your report without displaying the underlying data grid: Correct. You can create a chart object tied to a data source (e.g., a grid) and configure it to display only the chart, suppressing the grid for a cleaner visual presentation.

C . Control the way a report object is printed on the page relative to other report objects: Correct. Report Designer allows you to adjust the layout and positioning of report objects (e.g., grids, charts) relative to each other, controlling how they appear when printed or exported.

D . Insert a report object into the report if you are in Modify mode: Incorrect. While you modify reports in Report Designer, there's no specific ''Modify mode'' restriction---objects can be inserted during initial design or edits, but this is not a data source-specific feature.

The Oracle documentation verifies that B and C reflect Report Designer's flexibility with data sources and object management, making them the correct answers.

Oracle Planning 2024 Implementation Study Guide: 'Designing Reports with Report Designer' (docs.oracle.com, Published 2024-09-30).

Oracle EPM Cloud Documentation: 'Report Designer Data Sources' (docs.oracle.com, Published 2023-12-05, updated for 2024).

In Oracle Planning 2024, pushing data between cubes (e.g., from one cube to another within the same application) can be accomplished using specific tools. The two methods that facilitate this are:

A . Data Integration: Incorrect. Data Integration is used to import data from external sources (e.g., files, other systems) into Planning, not to push data between cubes within the same application.

B . Data Maps: Correct. Data Maps allow you to define mappings and push data between cubes (or applications) using Smart Push or manual execution. This is a primary method for intra-application data movement.

C . Copy Data: Correct. The Copy Data feature enables administrators to copy data from one cube to another within the same Planning application, specifying dimensions and members to transfer.

D . Import Data: Incorrect. Import Data is designed to bring external data into a cube from a file, not to push data between existing cubes.

Both Data Maps (with Smart Push for real-time updates) and Copy Data (for batch-style transfers) are explicitly supported for moving data between cubes, as per Oracle's documentation, making B and C the correct answers.

Oracle Planning 2024 Implementation Study Guide: 'Moving Data Between Cubes' (docs.oracle.com, Published 2024-09-05).

Oracle EPM Cloud Documentation: 'Data Maps and Copy Data Features' (docs.oracle.com, Published 2023-12-25, updated for 2024).

When designing a report in Reports for Oracle Enterprise Performance Management Cloud and encountering an error (indicated by a red bar above the report header), the issue often stems from report object configuration. The two possible causes are:

A . The report name is blank when you use a text function to display the name: Incorrect. A blank report name might cause display issues, but it's not a common cause of a report object error flagged by a red bar---errors typically relate to objects or data sources, not naming.

B . The report object overlaps with another report object: Correct. Overlapping objects (e.g., grids, charts) can cause rendering or validation errors in Report Designer, triggering an error indicator like a red bar due to layout conflicts.

C . The data source connection for the report is no longer valid: Correct. If the data source (e.g., a cube or grid definition) becomes invalid (e.g., deleted, renamed, or inaccessible), the report cannot retrieve data, resulting in an error marked by a red bar.

Oracle Planning 2024 Implementation Study Guide: 'Troubleshooting Reports in Report Designer' (docs.oracle.com, Published 2024-10-20).

Oracle EPM Cloud Documentation: 'Report Designer Error Handling' (docs.oracle.com, Published 2023-11-25, updated for 2024).

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.

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