To set up weekly planning for 18 continuous months in Oracle Planning 2024's Financials module, specific options must be selected when initially enabling features via the Configure card. The three required options are:
A . Time Frame Granularity: Incorrect. This is not a specific option in the Enable Features page; granularity (e.g., weeks) is controlled by Weekly Planning, not a separate setting.
B . Rolling Forecast: Correct. Enabling Rolling Forecast allows planning over a continuous 18-month horizon, dynamically updating as time progresses, which aligns with the requirement for ongoing weekly planning.
C . Weeks to Months Mapping: Correct. This option defines how weekly data rolls up into monthly totals, essential for reporting and analysis over the 18-month period in a weekly planning setup.
D . Weekly Planning: Correct. Enabling Weekly Planning sets the periodicity to weeks instead of months, allowing budgeting and forecasting at a weekly level for the 18 months.
E . Custom Periods: Incorrect. Custom Periods allow defining non-standard time periods, but they are not required for weekly planning over 18 months-Weekly Planning and standard calendar setups suffice.
The Oracle documentation confirms that Rolling Forecast, Weeks to Months Mapping, and Weekly Planning are the key features to enable for weekly planning over an extended horizon like 18 months, making B, C, and D the correct answers.
Oracle Planning 2024 Implementation Study Guide: "Enabling Weekly Planning in Financials" (docs.oracle.com, Published 2024-09-10).
Oracle EPM Cloud Documentation: "Configuring Rolling Forecasts and Weekly Planning" (docs.oracle.com, Published 2023-11-20, updated for 2024).

In Oracle Planning 2024, Service Administrators can use the Clone Snapshot feature to create an exact copy of the current application in a target environment. This feature automates all actions required for cloning, including removing the existing application and data in the target environment (if any) and replacing it with a snapshot of the source environment. The process involves exporting a snapshot from the source, deleting the target environment's current application and data, and then importing and applying the snapshot to recreate the application identically.
A . Replicate Snapshot: This is incorrect because "Replicate Snapshot" is not a defined feature in Oracle Planning. Replication typically implies duplicating data without necessarily overwriting the target, which doesn't align with the requirement of removing existing content.
B . Migration Export: This is incorrect because Migration Export only exports application artifacts (e.g., metadata, data) to a file for manual transfer or backup, but it does not automate the removal of the target environment's content or the import process.
C . Clone Snapshot: This is correct. The Clone Snapshot feature, available under the Environment management tools, fully automates the cloning process, including deletion of the target environment's application and data, followed by the recreation of the source application.
D . Migration Backup: This is incorrect because Migration Backup creates a backup file for recovery purposes but does not involve cloning or overwriting a target environment.
The Oracle Planning 2024 documentation specifies that Clone Snapshot is designed for such end-to-end automation, making it the ideal choice for Service Administrators to replicate an application across environments efficiently.
Oracle Planning 2024 Implementation Study Guide: "Managing Environments with Clone Snapshot" (docs.oracle.com, Published 2024-09-15).
Oracle EPM Cloud Documentation: "Cloning Environments in Planning" (docs.oracle.com, Published 2023-10-20, updated for 2024).

In Oracle Planning 2024's Capital module, enabling Named Assets allows planning for specific, individually tracked assets (e.g., equipment, buildings) rather than generic asset categories. The two tasks you can perform when enabling Named Assets are:
A . Add the names of assets to plan at the detail level: Correct. When enabling Named Assets, you can specify the names of individual assets (e.g., "Truck A," "Building 1") to plan their costs, depreciation, and other details at a granular level.
B . Specify the likely number of tangible and intangible assets that you want to add in a planning cycle: Incorrect. While you estimate a maximum number of Named Assets during enablement, you don't specify them by tangible/intangible categories-the distinction is managed later in asset planning, not at enablement.
C . Decrease the number of named assets after enabling Named Assets: Incorrect. Once Named Assets is enabled with a maximum number, you cannot decrease this limit directly; it requires reconfiguration or disabling/re-enabling the feature, which is not a standard task.
D . Increase the number of named assets after enabling Named Assets: Correct. After enablement, you can increase the maximum number of Named Assets (e.g., from 100 to 150) via the Configure card, allowing more assets to be added as needed.
The Oracle documentation confirms that A (adding asset names) and D (increasing the count post-enablement) are supported tasks for Named Assets, making them the correct answers.
Oracle Planning 2024 Implementation Study Guide: "Enabling Named Assets in Capital" (docs.oracle.com, Published 2024-09-20).
Oracle EPM Cloud Documentation: "Capital Named Assets Configuration" (docs.oracle.com, Published 2023-11-10, updated for 2024).