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

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

 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

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

Geography validation is a feature that enables you to validate the address information entered for a location against the geography hierarchy defined for a country. You can set the Geography Validation for Country option to one of the following values:

No Validation: No validation is performed on the address information.

Warning: A warning message is displayed if the address information does not match the geography hierarchy, but the user can still save the address.

Error: An error message is displayed if the address information does not match the geography hierarchy, and the user cannot save the address until the error is corrected. To ensure that only valid addresses are entered in the system, you should set the Geography Validation for Country option to Error. This will prevent users from saving erroneous address data and enforce data quality and accuracy. References:

Oracle Financials Cloud: Enterprise Structures with General Ledger Implementation, Chapter 2: Define Geographies, Section: Geography Validation

Oracle Financials Cloud: Implementing Enterprise Structures and General Ledger, Chapter 2: Define Geographies, Section: Geography Validation

If you use insert in the spreadsheet to load the monthly historical rates by using FBDI, the existing historical rate for a specific ledger, currency, account combination, and accounting period will be replaced by the new rate. This is because the insert action will overwrite the existing rate with the new rate in the GL_HISTORICAL_RATES_INT table. If you want to preserve the existing rate, you should use update or delete actions instead. References:

How Historical Rates Import Data Is Processed, Section: Use the Historical Rates Import file-based data import (FBDI) template to import historical rates from external and legacy sources to Oracle General Ledger

Import Historical Rates, Section: Details

Entering Historical Rates, Section: Entering Historical Rates

 Intercompany processing will balance a journal using the accounts identified here for the UK Ledger when the journal is balanced by the primary balancing segment value (BSV) but not by second or third BSV. A BSV is a segment in the chart of accounts that identifies a legal entity or business unit for which financial statements are prepared and balanced. A primary BSV is required for every ledger and is used to balance journal entries within a ledger. A secondary or tertiary BSV is optional and is used to balance journal entries across different dimensions other than the primary BSV, such as fund or region. Intercompany processing is a feature that enables intercompany transactions between different legal entities or business units within the same enterprise. Intercompany processing uses intercompany balancing rules to generate intercompany receivables and payables accounts for cross-ledger or cross-BSV journals. Intercompany processing will balance a journal using the accounts identified here for the UK Ledger when the journal is balanced by the primary BSV but not by second or third BSV, as this indicates that there is an intercompany transaction between different legal entities or business units within the UK Ledger that requires intercompany balancing. Intercompany processing will not balance a journal using the accounts identified here for the UK Ledger when there is a many-to-many journal and you want to use a clearing company, as this is a scenario that involves multiple legal entities or business units across different ledgers that requires a separate clearing company ledger to perform intercompany balancing. Intercompany processing will not balance a journal using the accounts identified here for the UK Ledger when the journal is not balanced by the primary BSV, as this is an invalid scenario that violates the accounting rules and prevents posting of the journal. Intercompany processing will not balance a journal using the accounts identified here for the UK Ledger when the journal is balanced by second balancing segment value, as this is an incomplete scenario that does not specify whether the journal is also balanced by primary and third BSV. Reference: Oracle Financials Cloud: General Ledger 2022 Implementation Professional Objectives - Configure and Process Intercompany 12

According to Oracle documentation3, when you need to set up a calendar for the year Apr-XX to Mar-YY where YY is the following year, and you would like the periods to be named according to the year they fall in, you should choose Fiscal Year as the format. A Fiscal Year format enables you to define periods based on fiscal years that span two calendar years. Therefore, option A is correct. Option B is incorrect because a Calendar Year format defines periods based on calendar years that start on January 1st and end on December 31st. Option C is incorrect because a Period format defines periods based on any number of days or weeks. Option D is incorrect because a Year format defines periods based on calendar years that start on any month other than January and end on any month other than December.

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

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