1z0-1054-26 Oracle Financials Cloud: General Ledger 2026 Implementation Professional Questions and Answers

The two valid Data Access Set types are Full access and Read Only access. A Data Access Set is a security feature that defines the access level that users have to ledger data, such as balances, budgets, or journals. A Data Access Set type is an attribute that determines the type of access that users have to ledger data within a Data Access Set. The two valid Data Access Set types are Full access and Read Only access. Full access allows users to view and enter data for ledger data within a Data Access Set. Read Only access allows users to view but not enter data for ledger data within a Data Access Set. Full Ledger is not a valid Data Access Set type, but an option that determines whether a Data Access Set grants access to all balancing segment values in a ledger or only specific balancing segment values. Primary Balancing Segment Value is not a valid Data Access Set type, but an attribute that identifies the legal entity or business unit for which financial statements are prepared and balanced. Read and Write access is not a valid Data Access Set type, but an alternative term for Full access. Reference: Oracle Financials Cloud: General Ledger 2022 Implementation Professional Objectives - Define Ledgers 12

Invoicing behavior for intercompany transactions is controlled by the Intercompany Transaction Type. The transaction type determines whether the intercompany transaction is transferred directly to General Ledger or whether it requires invoicing through Receivables and Payables. This is why the invoicing option must be selected for the relevant transaction type, not merely in system options or on the intercompany organization. Assigning Receivables and Payables business units is necessary when invoices are required, but that assignment does not itself enable invoicing for the transaction flow. The key setup decision is made at the transaction type level. Oracle documentation explains that intercompany transaction type attributes determine whether transactions are sent to General Ledger or require invoice generation in Receivables and Payables.

A primary ledger is the main ledger for a legal entity or business unit that records all accounting transactions and maintains the accounting balances. A secondary ledger is an optional ledger that is associated with a primary ledger and maintains accounting balances in a different accounting representation. A reporting currency is an optional currency that is associated with a primary ledger and maintains accounting balances in a different currency. In this scenario, the subsidiary company needs to produce fiscal reports under local GAAP and local currency, as well as report to the parent company using IFRS and not local currency. Therefore, the subsidiary company should configure a primary ledger with the local accounting convention and local currency, and a secondary ledger with the IFRS accounting convention and not local currency. A reporting currency with the local accounting convention or the IFRS accounting convention would not meet the requirement, as it would only maintain balances in a different currency, not a different accounting representation. A primary ledger with the IFRS accounting convention would not meet the requirement, as it would not comply with the local GAAP. References:

Oracle Financials Cloud Implementing Enterprise Structures and General Ledger, Chapter 2: Ledgers, Primary Ledgers, Secondary Ledgers, and Reporting Currencies

Oracle Financials Cloud Using General Ledger, Chapter 1: Introduction, Ledgers and Subledgers, Primary Ledgers, Secondary Ledgers, and Reporting Currencies

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 Shorthand Aliases

Select the chart of accounts that you want to create the alias for. In this case, it is the Corporate chart of accounts.

Click on the Add Row icon to create a new alias. Enter the following information:

Alias Name: RevDom

Account Template: 101-2000-400000-000-000-000

Description: Revenue Domestic for Supremo Fitness, Line of Business 2, and US Operations Cost Center

Enabled: Yes

Start Date: Today’s date

End Date: Blank

Click on the Save and Close button to save the alias.

You have successfully created a shorthand alias for the US Chart of Accounts. For more information, you can refer to the following resources:

Account Aliases

Enter a GL Account Alias

Short Hand Alias in Fusion Financials Key Flexfield

How to Enable Account Shorthand Aliases

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:

Navigate to the Setup and Maintenance work area and search for the task Manage Chart of Accounts Structures.

Click on the Create icon to create a new Chart of Accounts Structure. Enter the following information:

Structure Code: 07COA

Structure Name: 07 Chart of Accounts

Description: Chart of Accounts for candidate 07

Number of Segments: 5

Click on the Next button to define the segments. Enter the following information for each segment:

Segment Number: 1

Segment Name: Company

Value Set Code: 07Corporate Company

Value Set Name: 07 Corporate Company

Maximum Size: 3

Balancing: Yes

Segment Label: Company

Segment Number: 2

Segment Name: Cost Center

Value Set Code: 07Corporate Cost Center

Value Set Name: 07 Corporate Cost Center

Maximum Size: 4

Balancing: No

Segment Label: Cost Center

Segment Number: 3

Segment Name: Account

Value Set Code: 07Corporate Account

Value Set Name: 07 Corporate Account

Maximum Size: 8

Balancing: No

Segment Label: Natural Account

Segment Number: 4

Segment Name: Product

Value Set Code: 07Corporate Product

Value Set Name: 07 Corporate Product

Maximum Size: 3

Balancing: No

Segment Label: Product

Segment Number: 5

Segment Name: Intercompany

Value Set Code: 07Corporate Company

Value Set Name: 07 Corporate Company

Maximum Size: 3

Balancing: No

Segment Label: Intercompany

Click on the Next button to review the summary and click on the Save and Close button to save the Chart of Accounts Structure.

Navigate to the Setup and Maintenance work area and search for the task Manage Chart of Accounts Structure Instances.

Click on the Create icon to create a new Chart of Accounts Structure Instance. Enter the following information:

Structure Code: 07COA

Structure Name: 07 Chart of Accounts

Description: Chart of Accounts for candidate 07

Chart of Accounts Structure: 07COA

Enabled: Yes

Allow Dynamic Inserts: Yes

Click on the Next button to review the summary and click on the Save and Close button to save the Chart of Accounts Structure Instance.

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

Chart of Accounts Structures and Instances

Chart of Accounts Components

Minimum Steps For Financial Enterprise Structures Configuration

Overview of Creating and Configuring Chart of Accounts Structure and Instances

Day-to-day operational monitoring in Oracle General Ledger focuses on identifying open operational activity and intercompany processing exceptions that could delay accounting or period close. The Open Subledgers infolet helps monitor subledgers that are still open and may require action before period close. The IC Transactions infolet supports monitoring of intercompany transaction activity and exceptions. “Close Monitor” is broader close-management functionality, not simply an operational infolet. “Unallocated” may relate to allocations, but it is not one of the two primary day-to-day monitoring infolets in this question. Oracle documentation describes the Open Subledgers infolet as tracking modules still open and providing drill-down capability into the close process, while General Accounting infolets provide quick access to important operational information.

The source is where you specify the amount to be allocated. You can use various sources, such as account balances, fixed amounts, or statistical balances. In this case, you want to use the statistical balance of the floor area as the source of the allocation. The basis is where you specify the driver or factor that determines how the source amount is distributed among the targets. The target is where you specify the destination accounts that receive the allocated amount. The offset is where you specify the account that records the opposite side of the allocation entry. The allocation range is where you specify the scope of the allocation, such as the ledger, balancing segment, or legal entity. References:

Oracle Financials Cloud Implementing Enterprise Structures and General Ledger, Chapter 3: Allocations and Periodic Entries, Allocation Components

Oracle Financials Cloud Using General Ledger, Chapter 3: Allocations and Periodic Entries, Overview

The three labels that are required when designing the chart of account structure for this project are Primary Balancing, Cost center, and Natural Account. A chart of account structure is composed of segments that represent different dimensions of accounting information, such as company, department, account, or project. Each segment has a label that indicates its function or purpose within the chart of accounts. The Primary Balancing label is required for the segment that identifies the legal entity or business unit for which financial statements are prepared and balanced. The Cost center label is required for the segment that identifies the organizational unit or function that incurs expenses or generates revenues. The Natural Account label is required for the segment that identifies the nature of an account, such as asset, liability, revenue, or expense. The Intercompany Segment label is not required when designing the chart of account structure for this project, as this is an optional label for the segment that identifies intercompany transactions between different legal entities or business units within the same enterprise. The Secondary Balancing label is not required when designing the chart of account structure for this project, as this is an optional label for the segment that identifies an additional balancing dimension other than the primary balancing segment, such as fund or region. Reference: Oracle Financials Cloud: General Ledger 2022 Implementation Professional Objectives - Define Chart of Accounts 12

 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

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.

To add a global branding logo and more predefined transactional attributes to the journal approval email notification, you should copy (or customize) and edit the layout template and the data model. The layout template is a file that defines the appearance and content of the notification, such as text, images, tables, or charts. The data model is a file that defines the data sources and queries that provide data for the notification, such as predefined transactional attributes. You can copy (or customize) and edit the layout template and the data model using Oracle Analytics Publisher reports. You do not need to copy (or customize) and edit the output type, as this is a setting that determines the format of the notification output, such as HTML or PDF. You do not need to copy (or customize) and edit the data source, as this is a component of the data model that specifies where data for the notification comes from, such as an SQL query or an XML file. You do not need to copy (or customize) and edit the sub template, as this is a file that contains reusable content or logic that can be referenced by multiple layout templates. Reference: Oracle Financials Cloud: General Ledger 2022 Implementation Professional Objectives - Configure Workflow Approvals and Notifications 12