When enabling pre-built business processes like Financials or Capital, you don't create custom dimensions from scratch. Instead, the framework provides a set of placeholder dimensions (e.g., Custom1, Custom2). To use them, you navigate to the configuration task for the business process (e.g., Configure: Financials), and within the Map/Rename Dimensions section, you enable and rename these placeholders to fit your specific business needs. This process maps the generic custom dimension to your business-specific requirement.

A. Application Overview is used to enable or disable entire business processes and features, not for creating or renaming individual dimensions within them.

B. This describes adding a dimension to a custom BSO/ASO cube, not the specific process for enabling custom dimensions within a pre-built business process.

C. Data Management is a tool for loading data and metadata into existing dimensions; it is not used to create or define the application's dimensional structure.

1. Oracle® Cloud Administering Planning for Oracle Enterprise Performance Management Cloud

Release 24.05

F85953-11

Chapter 6: "Customizing Financials". Section: "Mapping and Renaming Custom Dimensions". The documentation states

"For custom dimensions that you want to use in the business process

on the Map/Rename Dimensions tab

select Enable. Then

rename the dimension."

When enabling Workforce features for the first time, certain foundational choices must be made that cannot be altered later. The option to include Employee Demographics (such as gender, veteran status, or ethnicity) is one such choice. If you do not select this option during the initial setup, you cannot add it incrementally later without re-creating the application. This is because it fundamentally alters the dimensionality and structure of the Workforce cube. Other features can typically be enabled incrementally after the initial setup.

A. Mapping Projects with Workforce is a configuration step for integration, not a one-time, irreversible feature enablement choice within Workforce setup.

C. This describes a data integration process between Assets and Workforce, not a foundational feature that must be enabled at the very beginning.

D. Consolidating reports and pushing data to Strategic Modeling is a reporting and integration strategy, not a feature that must be enabled during initial setup.

- Oracle® Cloud Enterprise Performance Management Cloud

Administering Planning Modules

E93973-28

Chapter 3

"Enabling Workforce Features

" Section "Workforce Features You Can Enable

" p. 38. The documentation notes: "You must select Employee Demographics the first time you enable features. You can't enable this feature later."

Groovy business rules provide advanced calculation and data manipulation capabilities within Oracle EPM Cloud Planning. They can be created and edited in application types that allow for custom business logic. This includes Custom applications, which are built from scratch; Module-based applications (part of the Enterprise SKU, such as Financials or Workforce), where Groovy can extend the pre-built functionality; and FreeForm applications, which offer maximum flexibility for custom model development.

B. Hybrid is a cube storage and processing architecture (combining BSO and ASO features), not a distinct application type. Groovy rules can run on hybrid cubes, but "Hybrid" is not the application category.

E. Reports are part of the reporting and analysis layer (Narrative Reporting or Reporting Web Studio). They are used for data visualization and do not execute server-side Groovy business rules like Planning applications do.

1. Oracle Cloud. (2024). Designing with Calculation Manager for Oracle Enterprise Performance Management Cloud. Release 24.02

Chapter 11

"Working with Groovy Business Rules

" section "About Groovy Business Rules." The documentation specifies that Groovy rules are supported in Planning (Custom)

Planning Modules (Module)

and FreeForm applications.

The predefined navigation flow for both the Revenue and Expenses card clusters in the Financials business process is designed to guide users through a logical planning sequence. It starts with a high-level "Overview," then moves to planning methods like "Driver and Trend Based" for automated calculations. For more specific scenarios, "Rolling Forecast" and "Direct Entry" cards are available. Finally, the "Income Statement" card allows users to see the consolidated results of their inputs. This sequence provides a structured approach from high-level analysis to detailed input and final review.

B. This sequence is illogical; for example, an "Overview" would typically come at the beginning, not after detailed input methods.

C. This order is also not standard. High-level overviews generally precede detailed input methods like "Direct Input" or "Driver Based" planning.

D. This option lists several components, but the sequence is not the standard one provided in the out-of-the-box navigation flow.

1. Oracle Cloud EPM

Working with Planning for Financials

"Navigating in Financials

" Section: "Financials Cards and Clusters." The documentation illustrates the default layout

showing the sequence of cards for Revenue and Expense planning starts with Overview

followed by Driver and Trend Based

Direct Entry

and concludes with reporting forms like the Income Statement.

Data maps, which are used by the Smart Push feature, define the data movement between a source and a target cube. Oracle EPM Cloud supports creating these maps for several key integration paths. This includes pushing data from a Planning application to Financial Consolidation and Close (D), pulling data from Financial Consolidation and Close into Planning (C), and moving data between two separate Planning cloud instances (E). These paths facilitate common planning, consolidation, and reporting cycles.

A. While pushing data from Planning to Tax Reporting is a valid path, the question asks for three, and C, D, and E represent the most fundamental integration patterns with core EPM modules.

B. Pushing data from Tax Reporting to Planning is a valid data map configuration, but it is generally less common than the other options listed.

Oracle Cloud EPM

Administering Planning

"Pushing Data". The documentation states you can use Smart Push to move data "...between different Planning environments

or from Planning to another Oracle EPM Cloud service

such as Financial Consolidation and Close..." This confirms options D and E.

Oracle Cloud EPM

Administering Financial Consolidation and Close

"Managing Data Maps". The documentation states: "The source can be a Financial Consolidation and Close cube. The target can be a cube in another EPM Cloud service

such as Planning." This confirms option C.

Mass Update forms in the Workforce module are powerful tools for managing employee and job data in bulk. They allow administrators and planners to perform two key actions efficiently. First, they can add new records for existing employees, such as a new job assignment or a compensation change, and automatically apply pre-configured defaults. Second, they can modify the properties of existing records, such as changing an employee's status or location, and override any default assignments or rates with specific values as needed.

A: Mass Update forms are primarily for adding or updating data, not for mass deletion of specific data points like salary.

B: This is incorrect; Mass Update forms are specifically designed to handle such scenarios, allowing you to add new records for existing employees.

- Oracle EPM Cloud

Administering Workforce Planning

"Updating Employee and Job Data". The documentation describes using Mass Update forms to "add a new record for an existing employee" and to "change existing properties and override default assignments and rates." This confirms the actions listed in options C and D are primary functions of these forms.

Within the Workforce module, Oracle Planning provides several forms for performing mass updates. The specific form designed to update employee properties (e.g., status), job properties (e.g., title), or salary-related information (e.g., grade, rate) for multiple employees simultaneously is the "Synchronize Definitions" form. This tool is essential for administrators to efficiently manage changes across a large workforce, such as applying cost-of-living adjustments or reorganizing job roles. It directly modifies the core definitional data for selected employees or jobs.

A. Synchronize Defaults: This form applies changed default values from job settings to existing employees; it does not perform arbitrary mass updates of properties.

B. Process Updated Data: This form is used to run compensation calculations after data has been updated, not to perform the update itself.

C. Process Data and Synchronize Defaults: This is a composite action that runs calculations and synchronizes defaults, but it is not the primary form for mass property updates.

Oracle Cloud

Administering Workforce

EPM-WFP

"Performing a Mass Update". The documentation specifies the purpose of each mass update form

stating for "Synchronize Definitions": "Update employee properties

job properties

or salary-related information for a group of existing employees."

To integrate Financials, Workforce, and Projects and share the Project dimension, two key configurations are required in the Workforce module. First, since Workforce does not have a native Project dimension, a custom dimension must be enabled and renamed to "Project" to match the dimension in the other modules, enabling it to be shared. Second, to "track employee utilization," the planning granularity in Workforce must be set to include "Employee." This ensures that plans and actuals are captured at the individual employee level, which is necessary to assign them to projects and track their specific contributions.

A. In Projects, ensure that the Employee driver-based expense is enabled: This is a subsequent step in the Projects module to pull data, not a prerequisite for sharing the dimension or setting the required granularity in Workforce.

D. In Financials, rename one of the custom dimensions to "Project" and enable it: Financials has a native Project dimension that can be enabled directly; renaming a custom dimension is incorrect and unnecessary.

1. Oracle Cloud EPM

Administering Projects

EPM-PJ

"Integrating Projects with Other Business Processes

" Section: "Integrating with Workforce." The documentation explicitly states the prerequisites: "In Workforce

enable a custom dimension and rename it to Project" and "In Workforce

ensure the planning granularity includes Employee."

2. Oracle Cloud EPM

Administering Workforce

EPM-WF

"Integrating Workforce with Other Business Processes

" Section: "Setting up Integration with Projects." This guide confirms that to share project details

a custom dimension must be configured as the Project dimension and that employee-level detail is required for utilization tracking.

In Workforce, the Merit Assumptions option lets administrators enter parameters that control merit processing, including 1) Hire Cut-Off Date—employees hired after this date are ineligible for merit—and 2) Merit Month—the month in which merit increases begin. Enabling Merit Assumptions therefore satisfies both requirements stated in the scenario.

A. Workforce Assumptions covers generic items such as default working hours, not hire cut-off or merit timing.

C. Merit Rates stores percentage or amount rates but does not define eligibility dates or start month.

D. Merit Month is a single assumption value visible only after Merit Assumptions is enabled; it is not itself an enable-option.

1. Oracle EPM Cloud

Administering Workforce Planning

“Setting Up Merit Assumptions

” Table 3-4 (Merit Month

Hire Cut-Off Date).

2. Oracle EPM Cloud

Administering Workforce Planning

“Enabling Workforce Features

” step 4 (enable Merit Assumptions).

Under IFRS 16, a rent-free period is a type of lease incentive. Within Oracle's lease accounting solution, this is modeled by setting the lease payments to zero for the specified duration. The system defines these periods not by a continuous date range, but by discrete planning periods (e.g., Jan-23, Feb-23) in conjunction with the lease's overall payment frequency (e.g., Monthly, Quarterly). This allows the calculations for the Right-of-Use asset and Lease Liability to correctly account for the zero cash flow during those specific periods while amortizing the total lease cost over the entire lease term.

A. The index rate is used for calculating variable lease payments that are tied to an index like the CPI, not for rent-free periods.

C. While the period occurs within a date range, the system's calculation logic is based on discrete periods and frequency, which is a more precise description.

- Oracle® Cloud Enterprise Performance Management Cloud

Administering Capital

F54463-03

Chapter 4

"Managing Leases

" Section "Adding Leases

" p. 58. (Describes setting up lease terms

including payment amounts and frequency).

- Oracle® Cloud Enterprise Performance Management Cloud

Administering Capital

F54463-03

Chapter 4

"Managing Leases

" Section "Lease Incentives

" p. 61. (Explains that incentives like rent-free periods affect the initial measurement of the lease liability and right-of-use asset

which implies a zero payment for the period).