:

To modify the journal approval notification, you need to copy (or customize) and edit the layout

template and the data model of the Analytics Publisher report. The layout template defines the

appearance and content of the notification, such as the text, fields, tables, and images. The data

model defines the data sources and queries that provide the data for the notification, such as the

journal attributes, amounts, and statuses. You can use Template Builder for Word to edit the layout

template and Analytics Publisher to edit the data model. You also need to download the Workflow

Notification Subtemplate, which is a common subtemplate that contains the header and footer of

the notification. You can preview the modified notification using the subtemplate and the data

model. Reference:

Modify Journal Approval Notifications with Analytics Publisher

[Creating Analytics and Reports for Financials Cloud]

:

According to Oracle documentation2, your users can personalize the Springboards and Work Areas to

suit their individual working styles in these two ways: They can format certain tables by hiding and

showing columns, moving columns, and resizing columns, and they can use “+” under the Apps

section of the News Feed homepage. Springboards and Work Areas are user interface components

that enable users to access tasks and information relevant to their roles. Users can customize these

components by adding or removing tiles, changing layouts, filtering data, and formatting tables.

Therefore, options A and D are correct. Option B is incorrect because users have more control over

configuring their Springboards and Work Areas than just resizing columns. Option C is incorrect

because users do not need to have the System Administrator configuring pages for them using Page

Composer.

According to the Oracle documentation12, the Intercompany Reconciliation Report can be run using

an additional currency and conversion rate that converts all amounts into a common currency for

comparison (option C). The report also includes ledger balancing lines generated when the primary

balancing segment value is in balance, but either the second or third balancing segment values are

not (option B). Option A is incorrect because you can drill down to the general ledger journal,

subledger accounting entry, and source receivables or payables transaction2. Option D is incorrect

because the report displays the intercompany receivables and intercompany payables balances in

summary for a period, and any differences between them1. Option E is incorrect because the report

does not display clearing company balancing lines2.

Balances cubes are multidimensional databases that store financial balances for interactive reporting

and analysis. A balances cube is created for each unique combination of ledger and currency, and it

contains dimensions such as chart of accounts segments, periods, scenarios, and other user-defined

attributes. New dimensions can be added to a balances cube by using the Manage Balances Cube

Dimensions task in General Ledger. Balances cubes are updated automatically when journals are

posted in General Ledger, and they can also be refreshed manually by using the Refresh Balances

Cube task. Balances cubes are not affected by the Translation or Revaluation processes, as these

processes only update the balances tables in General Ledger. Reference:

Overview of Oracle General Ledger Balances Cubes1

Considerations for General Ledger Balances Cubes2

Overview of Oracle Essbase Balances Cubes3

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

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 because hierarchies for reporting and allocations must be published to Essbase cubes5.

Option C is incorrect because it contradicts option B.

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

The two options that allow access to the BI Catalog for creating an Oracle Transactional Business

Intelligence analysis are Reports and Analytics and Enterprise Performance Management Workspace.

Reports and Analytics is a tool that allows users to access, create, edit, and share reports and

analyses using data from various sources, including Oracle Transactional Business Intelligence. Users

can access Reports and Analytics from various pages in Oracle Fusion Applications or from Oracle

Fusion Cloud Service Console. Enterprise Performance Management Workspace is a tool that allows

users to access, create, edit, and share reports and analyses using data from various sources,

including Oracle Transactional Business Intelligence. Users can access Enterprise Performance

Management Workspace from Oracle Fusion Cloud Service Console or from a web browser. Universal

Content Management Workspace is not an option that allows access to the BI Catalog for creating an

Oracle Transactional Business Intelligence analysis, as this is a tool that allows users to manage

documents and other digital content in Oracle Fusion Applications. Business Process Management

Workspace is not an option that allows access to the BI Catalog for creating an Oracle Transactional

Business Intelligence analysis, as this is a tool that allows users to monitor and manage business

processes in Oracle Fusion Applications. Scheduled Processes is not an option that allows access to

the BI Catalog for creating an Oracle Transactional Business Intelligence analysis, as this is a tool that

allows users to submit, monitor, and manage scheduled processes in Oracle Fusion

Applications. Reference: Oracle Financials Cloud: General Ledger 2022 Implementation Professional

Objectives - Use Oracle Transactional Business Intelligence (OTBI) 12