In Oracle Planning 2024, data maps with Smart Push or manual execution can push various types of data between cubes within the same application or across applications. However, not all items can be transferred. The item that cannot be pushed is:
A . Comments: Incorrect. Comments (cell-level annotations) can be pushed between cubes using data maps, provided the mappings include the necessary dimensions.
B . Attachments: Incorrect. Attachments linked to data cells can be transferred via data maps, as long as the target cube supports them and the mapping is configured correctly.
C . Data change history: Correct. Data change history (audit trails tracking who changed what and when) is not transferable via data maps. It is metadata tied to the source cube's audit log, not a pushable data element.
D . Supporting detail: Incorrect. Supporting detail (breakdowns of aggregated values) can be pushed between cubes if the target cube is configured to accept it and the mapping includes it.
The Oracle documentation specifies that data change history is excluded from data map transfers, as it's a system-maintained log, not a user-editable or movable data type, making C the correct answer.
Oracle Planning 2024 Implementation Study Guide: "Data Maps and Pushable Items" (docs.oracle.com, Published 2024-10-05).
Oracle EPM Cloud Documentation: "Smart Push Capabilities" (docs.oracle.com, Published 2023-12-15, 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.
D . The size of the inserted graphic is too large: Incorrect. While large graphics might affect performance or formatting, they do not typically cause a report object error flagged by a red bar-size issues are more likely to impact display than functionality.
The Oracle documentation identifies B (object overlap) and C (invalid data source) as frequent causes of errors in Report Designer, making them the correct answers.
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 Implementation, Forms 2.0 represents an enhanced version of the form design and functionality framework compared to Forms 1.0. To develop forecasts using Forms 2.0, existing forms must be transitioned from the older version to the newer one, as they are not automatically compatible or universally enabled.
D . Migrate the forms you want to work with in Forms 2.0 from Forms 1.0 to Forms 2.0: This is the correct statement. Oracle provides a migration process to convert Forms 1.0 forms to Forms 2.0, enabling users to leverage the advanced features of Forms 2.0 (e.g., improved navigation, dynamic rows/columns, and enhanced usability). This migration is selective, meaning only the forms you choose to use with Forms 2.0 need to be migrated, and it is not a one-time global setup.
A . Set up Forms 2.0 in your environment one time and it will work with all your applications: Forms 2.0 is not a one-time environment-wide setup. It requires specific forms to be migrated or designed for Forms 2.0 compatibility, and not all applications automatically adopt it.
B . Switch between Forms 1.0 and Forms 2.0 by selecting the Forms Version in Application Settings: There is no such toggle in Application Settings to switch between Forms 1.0 and Forms 2.0. The transition to Forms 2.0 involves migration rather than a simple version switch.
C . Redesign forms 1.0 forms so that they are set up to work with Forms 2.0: While redesigning is an option for creating new Forms 2.0-compatible forms, the standard process for existing forms is migration, not a complete redesign from scratch. Migration preserves the form structure while adapting it to Forms 2.0.
The migration process ensures that users can take advantage of Forms 2.0's capabilities while maintaining continuity with existing form designs, aligning with Oracle's recommended approach.
Oracle Enterprise Performance Management Cloud Documentation: "Working with Forms - Forms 2.0" (docs.oracle.com, updated 2024). States that "to use Forms 2.0, migrate existing Forms 1.0 forms to Forms 2.0 using the provided migration tools." Oracle Planning 2024 Implementation Study Guide: Confirms that migrating Forms 1.0 to Forms 2.0 is the true setup process for leveraging Forms 2.0 in forecasting.

In Oracle Planning 2024, the Application cluster in the navigator includes cards for managing application settings and features. The card that allows you to enable modules (e.g., Workforce, Projects) is:
A . Settings: Incorrect. Settings is not a card in the Application cluster; it's typically a broader system-level option, not specific to module enablement.
B . Configure: Correct. The Configure card in the Application cluster provides access to the Enable Features page, where administrators can turn on modules like Financials, Workforce, or Projects.
C . Tools: Incorrect. The Tools card offers utilities (e.g., diagnostics, job scheduling), not module enablement.
D . Enable Features: Incorrect. While "Enable Features" is the specific action/page, it is accessed via the Configure card, not a standalone card in the Application cluster.
E . Cube Editor: Incorrect. Cube Editor is for managing cube structures (e.g., dimensions), not enabling modules.
The Oracle documentation specifies that the Configure card is the entry point for enabling modules, making B the correct answer.
Oracle Planning 2024 Implementation Study Guide: "Enabling Modules in Planning" (docs.oracle.com, Published 2024-08-30).
Oracle EPM Cloud Documentation: "Application Cluster Navigation" (docs.oracle.com, Published 2023-12-05, updated for 2024).