Free 1Z0-1080-25 Practice Test Questions and Answers (2026)

Oracle EPM Cloud security is cumulative and permission-driven.

B. Both Users and Power Users can design (build or modify) an artifact when they are explicitly granted Build/Manage permission on that object.

C. Folder security is inherited: giving a user/group permission on a folder grants the same permission on every item inside it, unless a different permission is set on an individual item.

D. Access to dimension members is enforced at run time; a User or Power User can view or update only those members for which he or she has been granted the appropriate (read, write, none) member security.

A. Users and Power Users receive Write to all members only when no member security is defined, and they receive Read (not Write) on artifacts by default; therefore the blanket statement is false.

1. Oracle Enterprise Performance Management Cloud

“Administering Access Control

” Rev. May 2024

Section “Artifact Permissions – Build

” p. 18: “Users or Power Users with Build permission can create or modify artifacts.”

2. Ibid.

Section “Inherited Folder Permissions

” p. 22: “Permissions assigned to a folder are propagated to every artifact in that folder unless explicit permissions are set on the artifact.”

3. Ibid.

Section “Member Access Security

” p. 11: “A user can interact only with members for which he or she has been granted access.”

4. Oracle Planning Cloud

“Getting Started with Planning

” Section “Default Security

” p. 9: Describes default write to members and read-only access on artifacts

confirming why Option A is inaccurate.

In Oracle EPM Cloud Planning, Dashboards 2.0 are designed to provide rich, interactive visualizations. The data for the charts and other visual components within these dashboards can be sourced from three specific types of artifacts. These are existing forms, which present a curated slice of data; ad hoc grids, which allow for flexible, user-driven data exploration; and entire cubes, which provide access to a broad set of data for high-level analysis. These three sources provide the foundation for building dynamic and insightful dashboards.

C. Reports: Reports are distinct objects that can be placed on a dashboard alongside charts, but they are not used as a direct data source for creating a chart within Dashboards 2.0. E. Spreadsheets: Spreadsheets are not a direct data source for Dashboards 2.0. Data must first be loaded from a spreadsheet into a Planning cube before it can be visualized on a dashboard.

1. Oracle Corporation. (2024). Working with Planning for Oracle Enterprise Performance Management Cloud. Chapter 8: Designing Dashboards 2.0, Section: "About Dashboards 2.0".

Quote: "You can create dashboards that include up to six charts, each with its own data source, which can be a form, ad hoc grid, or cube." This section explicitly lists the three valid data sources.

2. Oracle Corporation. (2024). Administering Planning for Oracle Enterprise Performance Management Cloud. Chapter 10: Designing Dashboards 2.0, Section: "Creating a Dashboard 2.0".

Reference: This chapter details the process of creating a dashboard, where the first step after adding a chart is to select a data source. The available options presented in the user interface and documentation are Forms, Ad Hoc Grids, and Cubes.

Under IFRS 16 within Oracle Lease Accounting, a rent-free period is configured by creating a payment schedule line for the specific interval and setting the payment amount to zero. The system's core calculation engine for the Right-of-Use asset and Lease Liability amortization is fundamentally driven by the defined lease periods (e.g., monthly, quarterly) and the payment frequency. The rent-free period is simply one or more periods within this structure where the payment is zero, while interest accretion and asset amortization calculations continue as normal over the entire lease term.

A. Lease payments are set to the index rate.

This is incorrect. Index rates are used for variable lease payments that fluctuate based on an external index, a concept distinct from a rent-free period.

C. Calculations are based on a date range.

This is less precise. While a date range defines the rent-free interval, the system's calculations are processed on a periodic basis (e.g., monthly) according to the payment frequency.

1. Oracle Financials Cloud

Using Lease Accounting

24B

F91423-02

Chapter 5: Leases

Section: Create Payments.

The documentation states: "You can create a single payment for the entire lease term or create multiple payments for different periods of the lease term... For example

you can create a payment of zero for the first three months of the lease as a rent-free period." This directly supports option B. The entire process described for creating payment schedules is based on defining the number of periods and the frequency

which supports option D.

2. Oracle Financials Cloud

Implementing Lease Accounting

24B

F91421-02

Chapter 2: Lease Accounting Configuration

Section: Lease Accounting Configuration.

This guide details the setup of system options

including calendars and frequencies. It establishes that the fundamental basis for all lease processing and calculations is the defined periodicity. This provides foundational evidence for why calculations are based on periods and frequency (Option D)

not just a generic date range.

Groovy rules significantly extend the capabilities of standard business rules in Oracle EPM Cloud Planning. Key benefits include the ability to dynamically construct and execute Essbase calculation scripts at runtime based on user context or data (A). Groovy allows for complex, procedural logic (e.g., loops, conditional statements) to be performed on data grids entirely in memory, which is highly efficient for multi-step calculations before results are saved to the database (D). Furthermore, Groovy provides robust validation and error-handling mechanisms, enabling developers to validate user input from runtime prompts (RTPs) before execution and to validate data on forms before submission, preventing invalid data entry (E).

B: Member formulas are defined directly on members in the Dimension Editor using standard Essbase calculation syntax, not Groovy scripting. C: While Groovy can perform these actions on forms, this option is less comprehensive. Options D and E describe the more fundamental capabilities (in-memory procedural calculation and validation) that enable this specific use case and many others.

1. Oracle Cloud, Designing with Calculation Manager for Oracle Enterprise Performance Management Cloud (Release 24.05), Chapter 11: About Groovy Business Rules.

Page 11-1: "With Groovy rules, you can... Dynamically generate calculation scripts at runtime based on the context that is defined in the Groovy script." (Supports A).

Page 11-1: "Perform complex procedural calculations in memory before submitting the results to the database." (Supports D).

Page 11-1: "Add validation checks for runtime prompt values before running calculations, add data validation checks before submitting data, and add error handling." (Supports E).

2. Oracle Cloud, EPM Cloud Groovy Rules Java API Reference (Release 24.05), Class: Grid.

The documentation for the Grid (and related DataGrid) class describes methods for iterating through cells (each), getting and setting cell values (getCell, setCell), and performing operations on this in-memory representation of data before it is saved, which is the foundation for the benefit described in option D.

3. Oracle Cloud, Designing with Calculation Manager for Oracle Enterprise Performance Management Cloud (Release 24.05), Chapter 11: Working with Groovy Business Rules.

Section: Validating Runtime Prompts: "You can use Groovy business rules to validate runtime prompt values before a rule is launched." This section provides examples of accessing the rtps object to perform validation, directly supporting option E.

Section: Launching a Business Rule from a Groovy Rule: This section details how to build a string representing an Essbase calculation script and execute it using operation.application.getCube(CUBENAME).executeCalculationScript(calcScript), which directly supports the dynamic generation described in option A.

The "Rollup" calculation rule is specifically designed to aggregate data up the defined business hierarchies, such as Entity and Account dimensions. This process sums the values from lower-level (child) members to their respective higher-level (parent) members. Running this rule is essential after data input or changes at the base level to ensure that consolidated totals are accurately reflected in reports and analyses at all summary levels of the organization.

B. Prepare Plans: This rule is used to initialize a planning scenario, typically by seeding it with data from another source like actuals or a previous plan, not for hierarchical aggregation.

C. Calculate Actuals: This rule executes specific calculations on the "Actuals" scenario data, such as deriving financial ratios or other calculated metrics, rather than performing a general aggregation.

D. Prepare Forecast: Similar to "Prepare Plans," this rule is used to initialize a forecast scenario, often by seeding it with a combination of actual and plan data.

1. Oracle Corporation. (2024). Administering Financials for Oracle Enterprise Performance Management Cloud. EPM-AGFCS Document.

Section: "Financials Business Rules"

Content: This section explicitly describes the out-of-the-box rules. It states

"Use the Rollup business rule to aggregate data through the Entity and Account hierarchies." It also defines the other rules: "Use the Prepare Plan business rule to seed your plan from Actuals

" "Use the Prepare Forecast business rule to seed your forecast from Actuals and your current plan

" and "Use the Calculate Actuals business rule to calculate actuals for all Financials accounts." This directly supports 'A' as the correct answer for aggregation and differentiates it from the other options.

2. Oracle Corporation. (2024). Designing with Calculation Manager for Oracle Enterprise Performance Management Cloud. EPM-DCMCS Document.

Section: "About Aggregating and Calculating Data"

Content: This document provides the foundational concepts

explaining that aggregation (a rollup) is the process of calculating data for parent members by consolidating the data of their children. This aligns with the function described in the question as necessary to "analyze data at various levels of the business hierarchy."

To perform indirect cash flow statement planning within Oracle's Financials module, you must enable the Income Statement, Balance Sheet, and the Cash Flow Statement features. The indirect method for calculating cash flow begins with Net Income, which is derived from the Income Statement. It then adjusts for non-cash items and changes in working capital (e.g., accounts receivable, inventory, accounts payable), which are tracked on the Balance Sheet. Enabling the Cash Flow Statement feature itself is necessary to perform the consolidation and view the resulting statement. The system enforces this dependency by automatically selecting the Income Statement and Balance Sheet when the Cash Flow Statement is enabled.

C. Revenue: This is a sub-component of the Income Statement. The requirement is to enable the entire Income Statement feature, which includes revenue planning.

E. Expense: This is a sub-component of the Income Statement. The requirement is to enable the entire Income Statement feature, which includes expense planning.

1. Oracle® Cloud Enterprise Performance Management

Administering Planning

Release 24.05

F85844-11

Chapter 8: Administering Financials. In the section "Enabling Financials Features

" the documentation states: "If you select Cash Flow Statement

Income Statement and Balance Sheet are selected automatically and cannot be cleared. For Cash Flow

you can select either the Indirect or Direct method

or both." This directly confirms the dependency and requirement to enable all three features.

2. Oracle® Cloud Enterprise Performance Management

Working with Planning

Release 24.05

F85843-11

Chapter 10: Working with Financials. The section "About the Cash Flow Statement" explains the methodology: "For the indirect method

cash flow is calculated based on changes in the Balance Sheet and Income Statement." This supports the necessity of having both the Balance Sheet and Income Statement enabled to provide the required data inputs.

Mass Update forms in the Oracle EPM Cloud Workforce module are designed for planners to efficiently manage employee and job data after an initial data load from an external HR system. These forms specifically handle exceptions and adjustments. Their primary functions include adding new records for employees or jobs that were not part of the data load file (such as new hires or transfers) and applying the pre-configured default rates and assumptions. Additionally, they allow for the modification of properties for existing employees, including the crucial ability to override system-calculated defaults for compensation, benefits, and taxes to reflect specific circumstances.

A. Mass Update forms are for adding or updating records, not for mass deletion of specific data elements like salary. Running a data map is a separate administrative action, not performed on these forms.

B. This is incorrect. A key purpose of Mass Update forms is to handle exceptions, which includes adding compensation or other details for an existing employee who was missed in the data load file.

1. Oracle Cloud EPM

Working with Planning

Chapter 8: Working with Workforce

Section: Managing Existing Employees with Mass Updates.

This section explicitly states the capabilities of Mass Update forms: "After you load data from your HR systems

you can use the Mass Update forms to perform tasks that can add or update existing employee and job data." It then lists specific actions

including:

"Add a new record for an existing employee who was not in the load file

and apply configured defaults." (This directly supports option C).

"Change existing properties and then override default assignments and rates." (This directly supports option D).

"Change the status of an employee."

"Transfer an employee."

"Change an employee's job."

The pre-built Workforce module in Oracle EPM Planning is designed with a specific, fixed dimensionality, which includes a limited number of custom dimensions (typically two). A primary driver for creating a custom BSO (Block Storage Option) plan type is when a client's business requirements for workforce planning exceed these structural limitations. If a client needs to plan and analyze workforce data by more than the available custom dimensions (for example, by Project, Skill Set, and a custom Geography dimension), the standard Workforce module cannot be configured to accommodate this. A custom BSO plan type provides the necessary flexibility to design a cube with any number of required dimensions.

A. Planning salary by Position is a standard capability of the pre-built Workforce module and does not require a custom solution. C. Different levels of granularity within a shared dimension like Entity are managed through hierarchy design and security, not by creating a new plan type. D. The total number of dimensions in the application is not the direct driver; the specific dimensional requirements for the workforce planning process itself are what matter. E. A custom BSO cube would likely suffer from the same slow aggregation performance if it has similar size and sparse dimensionality. The standard architectural solution for slow BSO aggregation is typically an ASO (Aggregate Storage Option) reporting cube, not another BSO cube.

1. Oracle EPM Cloud, Administering Planning, Chapter 8: About Workforce: The documentation outlines the structure of the pre-built Workforce business process. It states, "Workforce provides two custom dimensions that you can enable and define to analyze expenses by dimensions that are not part of the predefined dimensions..." This confirms the limitation on the number of custom dimensions, directly supporting why option B is a valid reason to build a custom plan type.

2. Oracle EPM Cloud, Administering Planning, Chapter 2: Creating a Custom Application: This chapter details the process of building applications from scratch. It implicitly supports the rationale for option B by explaining that custom applications (and plan types) allow for complete control over the dimensionality, which is necessary when pre-built modules are too restrictive.

3. Oracle Essbase 21c, Database Administrator's Guide, Chapter 1: Oracle Essbase Overview, "Block Storage Cubes vs. Aggregate Storage Cubes": This foundational document explains the architectural differences between BSO and ASO. It clarifies that BSO is for complex calculations but can face performance challenges with large, sparse dimensions. ASO is designed for fast aggregation on large, sparse data sets. This supports the reasoning that building another BSO cube (Option E) is not the correct solution for BSO aggregation performance issues.

Navigation flows are the primary feature in Oracle Planning for customizing the user interface. Administrators use navigation flows to control how users interact with the application by defining the visibility and arrangement of cards, clusters, and tabs. This includes the ability to add, remove, or reorder the vertical and horizontal tabs that appear on a specific card, thereby tailoring the business process interface to the needs of different user roles.

A. Configure: The "Configure" option within the Application cluster is used for setting up application-level definitions like dimensions and user variables, not for customizing the user interface layout.

B. Valid intersections: This feature defines rules for valid data entry combinations at the cell level to ensure data integrity. It does not affect the user interface's visual components like tabs or cards.

D. Infolets: Infolets are interactive visual containers on the home page that display high-level, essential information. They are a component of the UI, not the tool used to customize other UI elements like tabs on a card.

1. Oracle Cloud EPM

Administering Planning

"Designing Custom Navigation Flows": "Navigation flows are the way that you control how users

groups

and roles navigate through the business process to perform tasks. You can customize the user interface by changing what is displayed on the Home page... You can also customize the tabs that are displayed on a card..."

2. Oracle Cloud EPM

Administering Planning

"Customizing Cards and Tabs": This section explicitly details the process: "You can customize the vertical and horizontal tabs that are displayed on a card. For example

you can hide tabs that a role does not need to see

or you can change the order in which tabs are displayed."

The Oracle Planning Jobs console allows administrators to automate and schedule various administrative and data management tasks. Among the available job types that can be scheduled are: Data Map: To move data between cubes. Import Data and Export Data: For loading data into and extracting data from the application. Refresh Database: To update the application with metadata changes and restructure the database. Merge Data Slices: To improve performance by merging incremental data slices in Hybrid BSO cubes. These jobs can be scheduled to run immediately, at a specific future time, or on a recurring basis.

A. Promote Planning Unit: This is a manual user action within the approvals process and cannot be scheduled as a system job from the Jobs console. D. Create Snapshot: This is an environment maintenance task performed through the Migration utility or automated via EPM Automate, not a schedulable job type within the Planning interface.

1. Oracle Corporation. (2024). Administering Planning for Oracle Enterprise Performance Management Cloud. "Managing Jobs". The documentation lists the available job types for scheduling, which include "Data Maps", "Import Data", "Export Data", "Refresh Database", and "Merge Data Slices". It does not list "Promote Planning Unit" or "Create Snapshot" as schedulable job types within the Planning Jobs console.

Valid Intersections in Oracle Planning are rules that define valid combinations of members across different dimensions. Their primary purpose is to enhance data integrity and guide user input. They achieve this by filtering member lists in forms and runtime prompts to show only valid combinations (E). This allows for the enforcement of specific business logic, such as ensuring certain programs are only associated with specific periods or departments (C). A direct consequence of applying these rules in data forms is that cells representing invalid member combinations are made read-only, thereby preventing users from entering data into invalid intersections (B).

A. This is incorrect. Valid Intersections do the opposite; they create filtered lists of members to prevent users from selecting invalid combinations. A nonfiltered list is the default behavior without Valid Intersections.

D. This is incorrect. Valid Intersections do not prevent the execution of Calculation Manager rules. They filter the member choices within the runtime prompts that a rule may use, but the rule itself will still execute.

1. Oracle Cloud EPM

Administering Planning

"Working with Valid Intersections" section.

This section states

"Valid intersections enable you to define rules that filter members of one dimension based on the members of another dimension... When you define valid intersections

you can prevent users from entering invalid data by making cells read-only in forms." This directly supports options B and E. The document provides an example: "...you can specify that certain products are sold only in certain markets

" which is analogous to the scenario in option C.

2. Oracle Cloud EPM

Designing with Calculation Manager for Oracle Enterprise Performance Management Cloud

"About Runtime Prompts" section.

This guide specifies

"If valid intersections are defined for a dimension

the member selector for the runtime prompt displays only the valid members for that dimension." This confirms that Valid Intersections filter runtime prompts

supporting option E and refuting option D's claim of preventing rule execution. It also contradicts option A by confirming that lists are filtered

not nonfiltered.

When scheduling a job to import data in Oracle Planning, the data file must reside in a server-side location accessible by the automated process. The EPM Cloud inbox serves as this server-side staging repository. Users upload files to the inbox, and then scheduled jobs can be configured to select and process these files directly from that server location. This allows for unattended, server-to-server data loading operations without requiring a user to be actively connected or to upload a file from their local machine at the time of execution.

A. You select the data locally: This option is for interactive, on-demand data loads initiated by a user from their own computer, not for automated, scheduled jobs that run on the server. C. You select the Include Metadata option: This option specifies the content of the file (i.e., whether it contains metadata in addition to data), not the location of the source file. D. You refresh the database after importing data: This is a separate, subsequent action performed after the data import is complete to aggregate the new data. It is not part of selecting the data source.

1. Oracle Cloud, Administering Planning, "Importing Data": "For scheduled jobs, you must select a file from the Inbox/Outbox. For immediate jobs, you can select a file from your local computer or from the Inbox/Outbox." This directly confirms that scheduled jobs must use files from the server's inbox.

(Source: Oracle Help Center, EPM Cloud - Administering Planning, Chapter 8: Importing and Exporting Data and Metadata, Section: Importing Data.)

2. Oracle Cloud, Administering Data Management for Oracle Enterprise Performance Management Cloud, "Uploading Files to the Oracle EPM Cloud Library": "You can upload files to the server where they can be selected for import and export operations. You upload files to the inbox/outbox server folders." This establishes the inbox/outbox as the designated server location for files used in data operations.

(Source: Oracle Help Center, EPM Cloud - Administering Data Management, Chapter 2: Administering Data Management, Section: Uploading Files to the Oracle EPM Cloud Library.)

Events in IPM Insights are used to model and explain significant, identifiable occurrences that cause anomalies, such as spikes or dips, in historical data. These can be one-time (e.g., a product launch) or recurring (e.g., an annual promotion). By associating these historical anomalies with defined events, the predictive engine can better understand the underlying data patterns. This allows for more accurate future-looking predictions, as you can schedule future events and the system will forecast an anticipated impact, enabling proactive planning and resource allocation.

A. Only events marked as "Active" are considered during the prediction process; inactive events are ignored.

C. Events are used to explain and attribute spikes or falls to a specific cause, not to normalize or distribute the data over time.

E. IPM Insights provides the flexibility to exclude specific historical data points (spikes or falls) from the analysis if they are deemed irrelevant outliers.

1. Oracle® Enterprise Performance Management Cloud

Administering Planning

Release 24.05

F85733-11

Chapter 16: Working with IPM Insights.

Section: About Events: "Events are typically one-off or recurring events that historically led to spikes or declines in data... Using events helps you plan ahead for the events and take advantage of opportunities by allowing you to see anticipated spikes and falls in the insight data for specific events." (This directly supports options B and D).

Section: Creating and Managing Events: This section describes setting an event's status to "Active" or "Inactive

" implying that only active events are used in processing. (This refutes option A).

Section: Analyzing Insights: "You can also exclude a data point from the analysis." (This directly refutes option E).

To include asset-related expenses from the Capital business process in Financials reporting, you must first enable the integration between the two modules. This is configured within the Capital business process settings. By specifically enabling the "Expense" component for integration, you instruct the system to push calculated data, such as depreciation and amortization, from Capital to the corresponding accounts in the Financials module. This enablement is the primary setup step that creates the necessary data pathways for reporting.

B. Adding a custom dimension in Financials is for data model extension and does not establish the automated data flow from the Capital module.

C. While mapping accounts is a necessary configuration step, the integration for the "Expense" component must be enabled first before the mapping becomes effective.

D. The integration is configured in the source module (Capital), not through a non-existent "Asset Expenses Wizard" in the target Financials module.

1. Oracle Help Center. Administering Planning for Oracle Enterprise Performance Management Cloud. Chapter 10: Setting Up Capital

Section: "Integrating Capital with Financials". The documentation states

"To integrate Capital with Financials

from the Capital configuration page

select the Financials business process features you want to integrate with Capital." This directly corresponds to enabling the integration for components like "Expense".

2. Oracle Help Center. Administering Planning for Oracle Enterprise Performance Management Cloud. Chapter 10: Setting Up Capital

Section: "Defining Capital Account and Dimension Mappings". This section details the process of mapping accounts

which is performed after the initial integration is enabled on the configuration page

confirming that enabling the feature (as in option A) is the prerequisite step.

The Project Benefits feature in Oracle Fusion Project Management is specifically designed to capture, track, and manage the anticipated value a project will deliver. This includes both financial and nonfinancial benefits. By enabling this option, project managers can create a benefit plan that outlines these expected outcomes. This plan serves as a crucial part of the project's business case, helping to justify its initiation and providing a baseline against which to measure its success beyond simple cost and revenue metrics.

A. Planning detailed project revenue is a core function of Project Billing and contract management, not the primary purpose of the broader Project Benefits feature.

B. This option is too specific and misrepresents the feature's purpose. Project Benefits is not designed to calculate benefits derived from workforce expenses.

D. Planning detailed project expenses is handled through project budgeting, forecasting, and cost management functionalities, which are distinct from benefit planning.

1. Oracle Fusion Cloud Project Management

"Project Benefit Plans: Explained": "Benefit plans enable you to capture the anticipated financial and nonfinancial benefits of a project. You can create a benefit plan to support the business case for a project and to track the realization of benefits throughout the project life cycle." (This document directly states the purpose is to capture both financial and nonfinancial benefits to support the business case).

2. Oracle Fusion Cloud Project Management

"Implementing Project Financial Management and Grants Management"

Chapter: Project Foundation Configuration: Project Types: In the section describing the configuration of project types

enabling "Project Benefits" is listed as the step required to "create a benefit plan to capture the anticipated financial and nonfinancial benefits of a project." (This confirms the feature's role in planning for nonfinancial benefits).

When configuring the Projects business process in Oracle Planning, you can enable different project types. If you choose to enable capital project planning, there is a direct dependency on the Capital business process. The Capital module provides the necessary framework for managing capital assets, calculating depreciation, and handling other capital-expenditure-related logic. Therefore, to plan for capital projects within the Projects module, the Capital module must also be enabled and configured to support these functionalities.

B. Workforce must also be configured. Workforce integration is optional for planning labor costs on projects; it is not a mandatory prerequisite for enabling capital projects. C. All modules must be enabled. This is incorrect. Oracle EPM Cloud Planning is modular, allowing organizations to enable only the specific business processes they need. D. Strategic Modeling must be enabled. Strategic Modeling is a separate business process for long-range strategic planning and is not a required dependency for the operational and capital planning integration between Projects and Capital.

1. Oracle Help Center, Administering Planning for Oracle Enterprise Performance Management Cloud, "Enabling Projects".

In the section describing the steps to enable the Projects business process, the documentation explicitly states: "To enable capital project planning, you must also enable Capital." This establishes the direct dependency required to use the capital project features.

2. Oracle Help Center, Administering Capital for Oracle Enterprise Performance Management Cloud, "Integrating Capital with Projects".

This section details how the two modules work together. It notes, "When you integrate Capital with Projects, you can create and manage capital projects that require funding approval, and then track them as they become assets." This confirms that the functionality for capital projects relies on the integration of both modules.

In Oracle's Workforce Planning module, Salary Grade assumptions are used to define the pay structure and associated compensation policies for different levels of jobs. The Salary Rate is a fundamental component, defining the pay range (often with minimum, midpoint, and maximum values) for a specific grade. Additionally, the Merit Rate, which dictates the percentage for performance-based salary increases, can be configured at the Salary Grade level. This allows organizations to apply different merit guidelines to various employee tiers, directly linking performance rewards to the established salary structure.

A. Partial Payment Factor: This is a global assumption used for prorating compensation for employees hired or terminated mid-period, not an attribute of a specific salary grade. B. Salary Basis: This defines the pay frequency (e.g., Annual, Monthly, Hourly) and is typically an attribute of a Job or a global default, not an assumption set within the salary grade itself.

1. Oracle EPM Cloud Documentation, Administering Planning Modules, "Defining Salary Grades": This section details the process of setting up salary grades. It explicitly states, "For each salary grade, you can specify properties such as the minimum, midpoint, and maximum salary rate." This directly supports that Salary Rate (C) is a key component.

2. Oracle EPM Cloud Documentation, Administering Planning Modules, "Setting Assumptions for Merit-Based Planning": This documentation explains how merit rates are configured. It notes that merit assumptions can be set by various dimensions, including Salary Grade. The business rule "Calculate Merit" uses these assumptions, confirming that Merit Rate (D) can be a salary grade-level assumption.

3. Oracle EPM Cloud Documentation, Administering Planning Modules, "Setting Assumptions for New Hires and Terminations": This source describes the configuration of proration logic, stating, "You can specify the partial payment factor to use for new hires and terminations." This confirms the Partial Payment Factor (A) is a global, not a grade-specific, assumption.

Smart Push is a feature in Oracle Planning that enables the real-time movement of data from a source cube (typically a Block Storage Option - BSO cube) to a target reporting cube (typically an Aggregate Storage Option - ASO cube) immediately after a user saves data in a form. This functionality is configured by first creating a Data Map, which defines the source, target, and dimensional mappings for the data transfer. The Data Map is then associated with a specific data form, and the "Enable Smart Push" option is selected for that form.

B. Data Integration: Data Integration is a tool for batch-oriented data loading and transformations from various sources, not for user-initiated, real-time data pushes from forms. C. EPM Automate: EPM Automate is a command-line utility used for automating administrative and maintenance tasks. It is not involved in the interactive Smart Push process triggered by a user saving a form. D. Business Rules: While business rules can be designed to move data, Smart Push is a distinct, pre-configured feature based on Data Maps. A business rule is not the client or tool that uses Smart Push on forms.

1. Oracle Cloud, Administering Planning, EPM-SA, "About Smart Push": "To use Smart Push, you first define a data map to specify the source and target for the data. After you define the data map, you can enable Smart Push on a form so that when a user saves data in the form, the data is pushed to the reporting cube." (Section: Moving Data)

2. Oracle Cloud, Administering Planning, EPM-SA, "Configuring Smart Push for a Form": "You can configure Smart Push for a form to move data from the form's underlying cube (source) to another cube (target) when the form is saved. Prerequisite: Create a data map to define the data to be moved from the source cube to the target cube." (Section: Designing Forms)

3. Oracle Cloud, Administering Planning, EPM-SA, "Defining a Data Map": This section details the process of creating the data map, which is the foundational object required to configure and use Smart Push. It states, "Data maps enable you to move data between cubes." (Section: Moving Data)

To track the utilization of employees in Oracle Projects, the employees must first exist as defined workers within the system. The Oracle Workforce module, part of Human Capital Management (HCM), is where employee records, assignments, and other essential data are created and maintained. This foundational employee data is a prerequisite for defining them as project enterprise labor resources. Without enabling the Workforce module and setting up employees, the Projects module has no resource data to track for utilization, time, or costing purposes.

A. Projects module before Financials module: While Financials is critical for project costing and billing, the core requirement for tracking employee utilization is the existence of employee records, which originate from the Workforce module.

B. Financials module before Projects module: This sequence is common for financial projects, but for tracking employee-specific utilization, the employee data from the Workforce module is the primary prerequisite, not the financial structures.

D. Projects module before Workforce module: This is logically incorrect. You cannot track or manage employees within the Projects module if they have not been created and defined in the Workforce module first.

1. Oracle Fusion Applications Help

Implementing Project Financial Management

Chapter: Set Up Project Resources

Section: Project Enterprise Labor Resources.

The documentation states: "To be a project enterprise labor resource

a person must be an employee or a contingent worker with an active assignment in Oracle Fusion Human Capital Management." This explicitly establishes that HCM (Workforce) setup is a prerequisite for using employees as resources in Projects.

2. Oracle Fusion Applications Help

Using Project Costing

Chapter: Labor Costs

Section: How Labor Costs Are Processed.

This section details that labor cost processing relies on employee assignments and attributes managed in Oracle Fusion HCM. It explains that "The process derives the human resource assignment for the employee from Oracle Fusion Human Capital Management." This confirms the dependency of Project Costing on HCM data.

3. Oracle Fusion Applications Help

Implementing Global Human Resources

Chapter: Workforce Structures

Section: Manage Jobs.

This guide outlines the foundational steps for setting up workforce structures

including jobs and positions. These structures are then used to create employee records

which are subsequently consumed by other modules like Project Management to define resources. The entire chapter demonstrates that workforce setup is a foundational activity.

The Default navigation flow is a system-defined artifact in Oracle EPM Cloud Planning. While it cannot be fundamentally altered by renaming or deleting it to protect system integrity, it can be managed in other ways. Administrators can copy the Default flow to use it as a template for creating custom navigation flows. Additionally, the Default flow can be deactivated, but only if another custom navigation flow is set as active for the users or groups. The system requires at least one active navigation flow.

C. Rename: The system-defined Default navigation flow is a protected artifact and cannot be renamed.

D. Delete: The Default navigation flow is required by the system as a fallback and base template; therefore, it cannot be deleted.

1. Oracle Cloud

Administering Planning for Oracle Enterprise Performance Management Cloud

Release 24.05

F81473-11

Chapter 11: Designing Custom Navigation Flows.

Section: Managing Navigation Flows: This section explicitly states

"You cannot rename or delete the default navigation flow." This directly supports why options C and D are incorrect.

Section: Copying a Navigation Flow: This section details the procedure for copying an existing navigation flow

which is a common action performed on the Default flow to create a custom version. This supports option B.

Section: Activating and Deactivating Navigation Flows: This section explains the concept of active versus inactive flows. It describes how to change the status

implying that the "Deactivate" operation is possible on any flow

including the Default

as long as another is made active. This supports option A.