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

In Oracle Planning 2024, scheduling jobs such as a weekly data import is managed through the Jobs interface, which provides options for automation, monitoring, and notifications. Let's evaluate the provided statements to identify the two that are true:
* A. You can check the execution status of a job only if it completed: This is false. The Jobs console in Oracle EPM allows users to check the status of a job (e.g., Running, Completed, Failed) at any time, not just after completion. Real-time monitoring is a key feature.
* B. You can set the daily maintenance time when scheduling cloning environment jobs: This is false.
Daily maintenance time is a system-wide setting controlled by administrators via Application Settings, not something adjustable when scheduling specific jobs like cloning or data imports.
* C. You can set to receive notifications when the job has completed: This is true. When scheduling a job (e.g., Import Data), users can enable email notifications to be alerted upon job completion, success, or failure, enhancing job management.
* D. You can schedule an Import Data job to run later at intervals: This is true. The scheduling feature supports recurring jobs, such as weekly data imports, allowing users to define the start time and frequency (e.g., daily, weekly) for tasks like importing data from external sources.
* E. You can delete that are currently processing: This is false. Jobs that are currently processing (i.e., in a "Running" state) cannot be deleted until they complete or fail, as per Oracle's job management rules.
Thus, the two true statements are C and D, reflecting the flexibility of scheduling recurring Import Data jobs and receiving completion notifications, both of which are explicitly supported in Oracle Planning 2024.
References:
Oracle Planning 2024 Implementation Study Guide: "Managing Jobs and Scheduling" (docs.oracle.com, Published 2024-08-22).
Oracle EPM Cloud Documentation: "Scheduling Jobs in Planning" (docs.oracle.com, Published 2023-12-10, updated for 2024).
Oracle Planning Administration Guide: "Monitoring and Notifications" (docs.oracle.com, Published 2024-10-
01).