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. Reference:

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

Data access sets are collections of ledgers that define the data security for users who access General

Ledger. Users can only access the ledgers that are assigned to them through data access sets. To

allow users with the General Accountant job role to access the UK Ledger, you need to create a data

access set that includes the UK Ledger and assign it to the user/role combination. You also need to

specify the access privilege for the data access set, which can be Full Ledger, Both Read and Write, or

Read Only. In this case, you need to select Both Read and Write to allow read/write access to the full

ledger. Reference:

Implement General Ledger

GL_ACCESS_SET_LEDGERS

The Default Data Access Set

Overview of General Ledger Security

The two true statements for the resulting revaluation run are that you have an unrealized exchange

gain recorded and you have an unrealized exchange loss recorded. Revaluation is a process that

adjusts foreign currency balances to reflect current exchange rates at period end. Revaluation creates

journal entries to record unrealized exchange gains or losses on foreign currency balances based on

revaluation rates defined for each currency. In this scenario, you have a balance on the Accounts

Payable Liability Account of 100,000 Euros which is equivalent to USD 136,550 at month end. The

month end exchange rate for revaluation is 1 Euro = 1.3755 USD. Therefore, after revaluation, your

balance on the Accounts Payable Liability Account will be USD 137,550 (100,000 x 1.3755). This

means you have an unrealized exchange gain of USD 1,000 (137,550 - 136,550) on your Accounts

Payable Liability Account because your liability in foreign currency has decreased in terms of your

ledger currency due to exchange rate fluctuations. Revaluation will create a journal entry to debit

your Accounts Payable Liability Account by USD 1,000 and credit your Unrealized Exchange Gain

Account by USD 1,000 to record this gain. The original journal entry in Euros is not updated by

revaluation, as revaluation only creates new journal entries to adjust foreign currency balances in

terms of ledger currency based on revaluation rates. There is no unrealized exchange gain or loss

calculated by revaluation, as revaluation does calculate unrealized exchange gains or losses on

foreign currency balances based on revaluation rates.

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. Reference:

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

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 style template, as this is a file that defines the styles and formatting of the notification

elements, such as fonts, colors, or margins. 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

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

When integrating with Oracle Hyperion Financial Management, you can use the following

dimensions for consolidation: Entity, Scenario, Year, Period, Value, Account, Intercompany, Custom1

to Custom4, and View. You can map one to one, or concatenate segments from your source General

Ledger to a single Hyperion Financial Management dimension. For example, you can map Company

to Entity, Department to Department, and Account to Account. However, if you have segments in

your source General Ledger that cannot be mapped to any Hyperion Financial Management

dimension, such as Program, then the data is summarized across those segments. This means that

the data is aggregated to the highest level of the unmapped segments, and the detail information is

lost. For example, if you have Program as a segment in your source General Ledger, and you do not

map it to any Hyperion Financial Management dimension, then the data is summarized by Program,

and you cannot see the data by individual Program values in Hyperion Financial

Management. Reference:

Example of Mapping Segments to Financial Management Dimensions

Overview of the Chart of Accounts Mapping Page

According to Oracle documentation1, the most efficient way to update your existing cross-validation

rules when you have redesigned your chart of accounts is to use Cross-Validation Rules Import file-

based data import (FBDI). FBDI enables you to import cross-validation rules from a spreadsheet

template into General Ledger. You can use FBDI to create new rules, update existing rules, or delete

rules. Therefore, option C is correct. Option A is incorrect because using the Manage General Ledger

Security page does not enable you to update cross-validation rules. Option B is incorrect because

creating Cross-Validation Rules desktop-integrated spreadsheet does not enable you to update cross-

validation rules. Option D is incorrect because using the Manage Cross-Validation Rules page does

not enable you to update cross-validation rules efficiently.

According to Oracle documentation2, you should create a Data Access Set that allows access to the

UK Ledger to allow users with the General Accountant job role to access the UK Ledger. A Data Access

Set is a security feature that defines the ledgers and balancing segment values that a user can access.

You can assign Data Access Sets to users or roles using the Manage Data Access for Users page.

Therefore, option B is correct. Option A is incorrect because assigning the security context value of

UK Ledger to the user/role combination does not enable access to the ledger. Option C is incorrect

because assigning the General Accounting Manager role to those users does not enable access to the

ledger. Option D is incorrect because assigning the UK reference set to the user/role combination

does not enable access to the ledger.

According to Oracle documentation3, you can opt out of the period close checking feature for these

three subledgers by using the lookup ORA_GL_INCLD_STRICT_PRD_CLOSE: Receipt accounting,

Receivables, and Assets. The period close checking feature prevents you from closing a General

Ledger period if there are any open subledger periods that exist for that ledger. You can opt out of

this feature for specific subledgers by using the lookup ORA_GL_INCLD_STRICT_PRD_CLOSE and

setting the Enabled flag to No for those subledgers. Therefore, options A, B, and D are correct. Option

C is incorrect because Revenue Management is not a subledger that can be opted out of the period

close checking feature. Option E is incorrect because Order Management is not a subledger that can

be opted out of the period close checking feature.

Query Designer is a Smart View tool that enables you to create and modify ad hoc queries on

General Ledger balances cubes. You can use Query Designer to select the dimensions, members, and

filters that you want to include in your query, and then retrieve the data in a grid format in Excel. You

can also save, open, and refresh your queries as needed. Query Designer is the best tool for

producing an income statement on a regular basis using Smart View, because it allows you to easily

access and analyze the income and expense accounts, as well as the ledger, period, currency, and

other dimensions that are relevant for your report. You can also customize the layout and format of

your grid, and use Excel functions and features to enhance your report. Reference:

Overview of Smart View

Creating an Ad Hoc Analysis in Smart View