Practice Free 1z0-1054-26 Oracle Financials Cloud: General Ledger 2026 Implementation Professional Exam Questions Answers With Explanation

The Intercompany Reconciliation report is a tool that helps you reconcile your intercompany transactions and identify any discrepancies between the provider and receiver sides. The report shows the entered or transaction amount of the accounting entries booked to the intercompany receivables and payables accounts for a pair of provider and receiver legal entities. The accounted amounts may be different when the conversion rates used for the intercompany receivables and payables are different. Therefore, you can run the report using an additional currency and conversion rate that converts all amounts into a common currency for comparison. This option helps you manage the currency risk and the conversion rate fluctuations for intercompany transactions. The report also displays the intercompany receivables and payables balances in summary for a period, and any differences between them. You can drill down on the links to view the balances by source and then by journal lines. You have full drill-down capabilities to the general ledger journal, subledger accounting entry, and source receivables or payables transaction. References:

Intercompany Reconciliation

Intercompany Reconciliation Reports

According to Oracle documentation, two reasons why a Financial Reporting Web Studio report may not appear as a choice in Financial Reporting Center are: You have not saved it in the Shared Folder/Custom/Financials directory, and you have not uploaded it to Financial Reporting Center. Financial Reporting Web Studio enables you to design and generate reports with grids, charts, images, and text boxes using data from various sources. Financial Reporting Center enables you to access and run all types of reports from a single user interface. To make a Financial Reporting Web Studio report available in Financial Reporting Center, you must save it in the Shared Folder/Custom/Financials directory and upload it to Financial Reporting Center using Workspace. Therefore, options A and C are correct. Option B is incorrect because saving it in the MyFolders directory does not make it available in Financial Reporting Center. Option D is incorrect because downloading it to your local drive does not make it available in Financial Reporting Center.

Oracle General Ledger balances cubes are created based on the unique combination of Chart of Accounts and accounting calendar. In this scenario, all four ledgers use the same Chart of Accounts, so the Chart of Accounts does not create additional cube variation. However, the calendars do. Two ledgers share one calendar, while the other two ledgers each use their own distinct calendar. That produces three unique Chart of Accounts and calendar combinations: shared calendar combination, second distinct calendar combination, and third distinct calendar combination. Therefore, three balances cubes are created automatically. The candidate answer “two balance cubes” is incorrect. Oracle documentation states that General Ledger balances cubes are created for each combination of Chart of Accounts and accounting calendar.

Currency translation is used to restate ledger-currency balances into another currency for reporting, consolidation, or management reporting. In Oracle General Ledger, translation is commonly used when a subsidiary maintains its functional currency but the parent company requires financial statements in a different reporting or consolidated currency. This is different from revaluation, which adjusts foreign-currency-denominated account balances using current rates and records unrealized gains or losses. It is also different from transaction conversion, which converts individual transactions into the ledger currency at transaction time. Translation operates on account balances, not individual source transactions. Oracle documentation describes translation as restating actual account balances from the ledger currency to a reporting currency using translation processes and rates.

According to the Oracle documentation34, account hierarchies are defined in Oracle Fusion applications using tree functionality. Each account hierarchy is defined as a tree with one or more versions. You can have only one version of a hierarchy published to the Essbase cube at any time (option A). Child values in these hierarchies can belong to only one parent (option D). Option B is incorrect becausehierarchies for reporting and allocations must be published to Essbase cubes5. Option C is incorrect because it contradicts option B.

You should define the default intercompany balancing rule at the legal entity level, because each ledger has one legal entity assigned to it and each legal entity is associated with one balancing segment value. This way, you can specify the intercompany receivables and payables accounts for each legal entity and ensure that the journals are balanced by legal entity or primary balancing segment values. A ledger-level rule would apply to all legal entities in the ledger, which may not be appropriate if they have different intercompany accounts. A primary balancing segment rule would apply to all ledgers that share the same chart of accounts, which may not be desirable if they have different intercompany rules. A chart of accounts rule would apply to all ledgers and legal entities that use the same chart of accounts, which may not be feasible if they have different intercompany segments or accounts. References:

Intercompany Balancing Rules, Section: Define Intercompany Balancing Rules

Overview of Intercompany Balancing Rules, Section: Define Intercompany Balancing Rules

Troubleshooting Guide For Intercompany Balancing, Section: 1. Journals and subledger accounting entries are not being balanced for intercompany activity

Implement General Ledger, Section: Intercompany Balancing

 Here are the steps you need to follow:

In the Setup and Maintenance work area, go to the following:

Offering: Financials

Functional Area: Financial Reporting Structures

Task: Manage Chart of Accounts Mapping

Select the source chart of accounts (UK) and the target chart of accounts (CA) that you want to map.

Click on the Segment Rules tab to define the segment mapping rules. Enter the following information for each segment:

Segment Number: 1

Segment Name: Company

Mapping Type: Value

Source Value: *

Target Value: *

Segment Number: 2

Segment Name: LoB

Mapping Type: Value

Source Value: *

Target Value: *

Segment Number: 3

Segment Name: Account

Mapping Type: Range

Source From Value: 1000

Source To Value: 1999

Target Value: 11101

Mapping Type: Range

Source From Value: 2000

Source To Value: 2999

Target Value: 22100

Mapping Type: Range

Source From Value: 3000

Source To Value: 3999

Target Value: 34000

Mapping Type: Range

Source From Value: 4000

Source To Value: 4999

Target Value: 42000

Mapping Type: Range

Source From Value: 5000

Source To Value: 99999999

Target Value: 51100

Segment Number: 4

Segment Name: Cost Center

Mapping Type: Value

Source Value: 0

Target Value: Balance Sheet

Mapping Type: Value

Source Value: 000

Target Value: Balance Sheet

Mapping Type: Value

Source Value: *

Target Value: 610

Segment Number: 5

Segment Name: Product

Mapping Type: Value

Source Value: *

Target Value: *

Segment Number: 6

Segment Name: Intercompany

Mapping Type: Value

Source Value: *

Target Value: *

Click on the Save and Close button to save the segment mapping rules.

You have successfully created a Chart of Accounts mapping for the given scenario. For more information, you can refer to the following resources:

Overview of the Chart of Accounts Mapping Page

Chart of Accounts Structures and Instances

How To Create A Chart Of Accounts Mapping For A Secondary Ledger

How To Bulk Upload The Mapping Rules In “Manage Chart of Accounts Mapping”

Centralized Management of Chart of Accounts Configurations