Before an EPM (Enterprise Performance Management) administrator can import a Machine Learning (ML) model into Oracle Planning, a prerequisite task must be completed by data scientists. According to Oracle’s "Bring Your Own ML" feature in the Planning application, the process begins with data scientists gathering historical data related to a business problem, training an ML algorithm, and generating a Predictive Model Markup Language (PMML) file using a third-party data science tool or Oracle Data Science Cloud. This PMML file represents a fully trained ML model that can then be imported into the Planning application by an EPM administrator.

Option A is correct because it aligns with this prerequisite step: the ML model must be pretrained and saved as a PMML file before the import process can begin. Option B is incorrect because Groovy rules are not created by data scientists to evaluate historical data; instead, these rules are automatically generated by the Planning application during the import process to integrate the ML model with the application. Option C is also incorrect, as EPM administrators do not generate PMML files by creating data models and pushing data—instead, they import an existing PMML file. Finally, Option D is incorrect because while EPM administrators may create data maps and Groovy rules as part of the deployment process, this occurs after the PMML file is imported, not before.

The Oracle Planning 2024 Implementation documentation emphasizes that the "Bring Your Own ML" functionality relies on importing a prebuilt PMML file, making the data scientists' role in building and training the model a mandatory first step.

References:

Oracle Planning 2024 Implementation Study Guide: "Bring Your Own ML: About Machine Learning Model Import" (docs.oracle.com, Published 2024-09-04).

Oracle EPM Cloud Documentation: "Importing ML Models" (docs.oracle.com, Published 2022-06-17, updated for 2024).

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.

References:

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

To track the utilization of employees in the Projects module of Oracle Planning 2024, the Workforce module must be enabled first. Employee utilization in Projects refers to tracking how employees’ time and costs (e.g., hours worked, labor expenses) are allocated to specific projects. The Workforce moduleprovides the foundational data—such as employee details, roles, salaries, and hours—required to calculate utilization metrics. Once Workforce is enabled and configured with employee data, the Projects module can leverage this data via integration to track utilization against project tasks and budgets.

A. Projects module before Financials module: Incorrect. Enabling Projects before Financials does not address employee utilization tracking, as Financials focuses on revenue and expense planning, not employee-specific data.

B. Financials module before Projects module: Incorrect. Financials provides financial planning capabilities but does not manage employee data or utilization, which is a Workforce function.

C. Workforce module before Projects module: Correct. Workforce must be enabled first to define employee data, which Projects then uses to track utilization through integration (e.g., via data maps or direct links).

D. Projects module before Workforce module: Incorrect. Enabling Projects first without Workforce would limit utilization tracking, as Projects relies on Workforce for employee-related data.

The Oracle documentation specifies that Workforce is a prerequisite for detailed employee utilization tracking in Projects, making C the correct sequence.

References:

Oracle Planning 2024 Implementation Study Guide: "Integrating Workforce with Projects" (docs.oracle.com, Published 2024-09-20).

Oracle EPM Cloud Documentation: "Tracking Utilization in Projects" (docs.oracle.com, Published 2023-12-15, updated for 2024).