Free Oracle 1Z0-1087-26 Practice Test Questions and Answers (2026)

In Oracle Account Reconciliation, deleting a reconciliation removes the reconciliation data and its history for the specified period, but it does not delete or clear the balances loaded into the system for that period. Furthermore, security controls mandate that standard users (such as preparers and reviewers) cannot delete reconciliations; only users assigned the Service Administrator or Power User roles possess the required privileges to delete reconciliations.

A. Reconciliations can be deleted regardless of their status (such as Open, Pending, or Closed), provided the user has administrator privileges.

B. Preparers do not have security rights to delete reconciliations; only Power Users and Service Administrators hold this capability.

- Oracle Fusion Cloud EPM

Administering Account Reconciliation

"Deleting Reconciliations"

Section: Reconciliations Management.

- Oracle EPM Center of Excellence

Reconciliation Administration Guide

Document ID: E93822-04

Chapter 6: Managing Reconciliations.

In Oracle Account Reconciliation, Group Reconciliations allow a parent reconciliation to aggregate and manage multiple individual child reconciliations. To utilize group reconciliation functionality for a profile, the underlying format used by that profile must have the "Allow Group Reconciliation" option explicitly enabled within its format properties.

B: Data Management can be used to import balance data for group reconciliations as well as individual reconciliations.

D: Sub-segment balance details are viewed within the reconciliation balance summary and child reconciliations, not a specific "Group Detail" tab.

E: Importing pre-mapped data is a general balance import capability across periods, not a defining characteristic unique to group reconciliations.

1. Oracle Fusion Cloud EPM

Administering Account Reconciliation

"Creating Group Reconciliations"

2. Oracle Fusion Cloud EPM

Administering Account Reconciliation

"Defining Formats: Allow Group Reconciliation"

In Oracle Account Reconciliation (Transaction Matching), when configuring the auto-match process, administrators define Match Rules to automatically match transactions across data sources.

1. One to One (E): This is explicitly defined in the system UI and documentation as a "Rule Type." The available Rule Types dictate the cardinality of the match and include One to One, One to Many, Many to One, and Many to Many.

2. Suggested Match (C): While technically configured under the "Match Status" drop-down in the rule creation dialog, Oracle documentation and conceptual frameworks frequently categorize rules by their intended outcome type: rules that result in a Confirmed Match and rules that result in a Suggested Match. Suggested Match rules flag potential matches that require manual review by a preparer.

A. Matches Exactly: This is a conceptual condition or criteria outcome (e.g., using the "Equals" operator without tolerance), not a designated rule type in the system.

B. Matches with Tolerance: This refers to a condition setting applied to Date or Number attributes within a rule, not a standalone rule type.

D. Adjustment: An adjustment is an action or a resulting transaction type generated during the matching process to handle variances, not a matching rule type itself.

Oracle Cloud Enterprise Performance Management: Administering Oracle Account Reconciliation, Chapter: "Defining Match Rules" (Section: Understanding Match Rule

In Oracle Account Reconciliation, loading balances via Data Management (Data Integration) takes precedence over manual or pre-mapped balance imports. When a Data Management balance load process is executed for a period that already contains pre-mapped balances, the balances loaded through Data Management overwrite the existing pre-mapped balance records for that period.

A. Data Management executes the data load task successfully without failing when encountering existing pre-mapped data.

B. Data Management loads are automated scheduled or batch processes that do not prompt the user interactively during execution.

D. Pre-mapped balances and Data Management balances are not summed; Data Management data replaces pre-mapped entries.

- Oracle Cloud Administering Oracle Account Reconciliation

Section: "Loading Balances via Data Management"

- Oracle Cloud Using Oracle Account Reconciliation

Section: "Importing Pre-mapped Balances vs. Data Integration Loads"

To configure security access and permissions for Power Users regarding profiles in Oracle Account Reconciliation, administrators must navigate through the system configuration settings. The standard navigation path is to open the Application card from the Home page, select Configuration, and then click on System Settings, where Power User security rules and profile access options are maintained.

B. Power User profile access configuration is located under Application Configuration, not under Tools Access Control.

C. Profile Segments is used for configuring segment account structures, not for managing Power User security settings.

D. Navigating directly to Application > Profiles allows managing profile instances, not global Power User security rules.

- Oracle Fusion Cloud EPM

Setting Up and Administering Account Reconciliation

"Configuring System Settings"

Section: Power User Security.

- Oracle EPM Cloud Documentation

"Administering Profile Security and Access Settings"

Chapter 3.