AccountingHub 20C StudentGuide

Oracle Financials Cloud:
Accounting Hub
Fundamentals for 20C
Student Guide
September 2020
1
Oracle Financials Cloud:

Accounting Hub Fundamentals Overview
Course Objectives
After completing this course, you should be able to:

• Identify the key features of Oracle Accounting Hub Cloud
• Describe Navigation
• Use Oracle Functional Setup Manager (FSM) and the security features to implement
Oracle Accounting Hub Cloud
• Describe enterprise structures, financial reporting structures, ledgers, and the Vision
story
• Configure accounting transformations
• Discuss period close components
• Create financial reports
Oracle Financials Cloud: Accounting Hub Fundamentals 1 - 2

Lesson Objectives
After completing this lesson, you should be able to:

• List the available implementation resources
• Describe the course schedule
• List the key features of Oracle Accounting Hub Cloud
• Discuss the rapid implementation approach of registering source systems
• Describe Accounting Hub Cloud reporting options

Oracle Accounting Hub Cloud Overview
The graphic in the slide depicts the Accounting Hub Cloud’s features and integrations.
Oracle Accounting Hub Cloud provides the flexibility and control that you need in the implementation,
expansion, and maintenance of subledgers. You can:
• Configure user-defined subledgers to adopt in a flexible business environment
• Configure accounting rules to meet your corporate and statutory requirements
• Automate to control the processes from transforming source system data to recording detailed,
auditable journal entries
• Use the modern reporting tools that are available in Oracle Cloud to reconcile accounted journal
entries. This can lessen the accumulative work required at the end of the accounting period.
You can also gain insightful information for your day-to-day business, for corporate
performance, and for making business decisions.
The Oracle Accounting Hub Cloud also integrates and aligns information from virtually any and multiple
source systems into Oracle Financial Cloud Services. It gives customers the freedom and flexibility to
choose the tools they want to use to run their business as they start their transition to cloud-based
computing. This capability provides a smooth transition to cloud computing for our Oracle Financials
Cloud customers, because they can continue their financial operations on existing systems without
disruption while centralizing critical information for management decisions, audit, and compliance to a
central cloud service for easy access across the globe. The core capability of Accounting Hub Cloud, our
robust accounting engine, delivers flexible modeling that captures rich elements from our customers’
existing business systems. This would significantly offload the burden on external financial reporting
processes to deliver business performance insights.

Oracle Accounting Hub Cloud Components
The Accounting Hub Cloud provides the following set of accounting tools:
• Oracle General Ledger
• Oracle Financial Reporting
• Accounting Transformations Using Accounting Rules
• Outbound Integration with Oracle E-Business Suite and PeopleSoft General Ledgers
Oracle General Ledger

• Provides journal entry import and creation, real-time balances, accounting controls, and close
functionality
• Contains intercompany balancing, a calculation manager for definition of allocation rules by
using complex formulas, automatic generation of allocation journals, enhanced journal
approval, and year-end process management
• Provides embedded balances cube functionality with multidimensional, online analytical
processing (OLAP) of financial information
Oracle Financial Reporting

• Uses Oracle General Ledger Balances Cube (GL Balances Cube)
- Every time a transaction or journal is posted in General Ledger, the balances cubes
are updated at the same time with pre-aggregated balances at every level of
summarization in your account hierarchy.
- This is leveraged by reports for quick processing.
• Processes and deploys complete financial reports across your enterprise in multiple formats.
• Provides embedded balances cube functionality with multidimensional, online analytical
processing of financial information.

• Slices and dices data across dimensions
• Drills up, down, and across on any parent level within the chart of accounts
Accounting Transformations by using Accounting Rules

• Provides flexible accounting transformation of transactions
• Creates journal entries and transfers reference information from diverse, non-Oracle, industry
applications into accurate, detailed, auditable accounting entries in Oracle General Ledger
Outbound Integration with Oracle E-Business Suite and PeopleSoft General Ledgers
• Enables the ability to publish output files from the Accounting Hub with journals in EBS and
PeopleSoft format.
• Enables customers to transition to cloud General Ledger in phases.

Rapid Implementation Approach to Registering
Source Systems and Uploading Transactions
The graphic in the slide depicts the quick setup checklist for rapid implementation of the Oracle
Accounting Hub Cloud.
The Oracle Accounting Hub Cloud offers a simplified and streamlined source system registration and
automation-ready transaction upload to financials cloud. The Accounting Hub Cloud provides two
additional spreadsheets to:
• Register source systems: We have simplified the Accounting Hub Cloud source system
registration with a rapid implementation approach. This accelerates the Accounting Hub
Cloud implementation for registering new source systems.
• Upload transaction data: You can upload transaction data for the registered Accounting Hub
Cloud subledger in .csv format. Optionally, you can automate the processes from uploading
to creating accounting journal entries. This increases day-to-day control of financials and
management reporting.

Accounting Transformation: Accounting Methods
Overview
The graphic in the slide illustrates the components of Accounting Methods.
Accounting Methods group subledger journal entry rule sets together to define a consistent accounting
convention across all accounting event classes and accounting event types for all source systems. An
Accounting Method is attached to the primary and secondary ledgers, and is the 4th C in a ledger
configuration.
The Accounting Methods include the following required elements:

• Journal Entry Rules Sets
• Journal Line Rules
• Account Rules
The Accounting Methods include the following optional elements:

• Description Rules
• Supporting References
• Mapping Sets
• Custom Formulas

The Financial Reporting Center Overview
The graphic in the slide depicts the various reporting tools that are available for financial reporting.
The Financial Reporting Center is intended to be the primary user interface for General Ledger
reporting. The Financial Reporting Center:
• Offers state-of-the-art reporting and analytics capabilities
• Reports from the Oracle General Ledger Balances Cube (GL Balances Cube) for consistent,
timely, and accurate information for all users
• Performs multidimensional analysis and pivot with drilldown to journal detail and to both
Oracle and non-Oracle subledger transactions
• Retrieves results from the report objects and definitions stored in the Enterprise Performance
Management System Workspace, Fusion Edition (EPM Workspace) under the BI Catalog
The Financial Reporting Center includes access to the following types of reports:
• Financial Reports: Reports are built off the Oracle Hyperion Financial Reporting Studio by
using the data in the Oracle General Ledger Balances Cube, for example, company income
statements and balance sheets. These reports are mainly run by users in General Ledger.
• Account Groups and Sunburst: These are used to monitor key accounts in General Ledger.
When a user creates an account group, it becomes visible in the Financial Reporting Center
with the Sunburst visualization tool. The Sunburst visualization tool enables you to interact
with your account balances across various business dimensions in order to view balances
from different perspectives.

• Smart View Reports: Smart View is a multidimensional pivot analysis tool that is combined
with full Microsoft Office functionality as an add-in. It enables you to interactively analyze
your balances and define reports by using a familiar spreadsheet environment. These queries
are mainly for users in General Ledger. One user can upload a query by using Workspace, and
then from the Financial Reporting Center, another user can download the query to the local
drive for use.
• Oracle Transactional BI Analyses: These analyses and reports are built off of transactional
tables by using Subject Areas. These reports can be run by Accounting Hub users, General
Ledger users, and Intercompany users.
• Oracle Transactional BI Dashboards: Dashboards put all the information, functions, and
actions that business users need to do their job in one place. They are built off Oracle
Transactional BI objects such as analyses and reports. These reports can be run by
Accounting Hub users, General Ledger users, and Intercompany users.
• Business Intelligence Publisher Reports: Most of these reports are predefined and must first
be submitted and resubmitted to see the latest data by the Oracle Enterprise Scheduler
System (ESS) through the Scheduled Processes navigation. These reports can be run by
Financials users.
Note: The icons in the graph in the slide are used in the Financial Reporting Center to represent each
type of report.

Other Reporting Tools Overview
The six other tools for reporting in Financials are:
Other Reporting Tools Report Type

General Accounting Dashboard and Account Inspector Account Groups
Reports and Analytics Oracle Transactional BI Objects
BI Catalog All Report Types except BI Publisher Reports
EPM Workspace Reports, Books, Snapshot Reports, Snapshot Books,

Financial Reporting Batches, and Batch Scheduler
Enterprise Scheduler System (ESS) Oracle BI Publisher Reports
The table in the slide details the other reporting tools and the corresponding report types.
Even though the Financial Reporting Center is designed to be the main user interface for a financial
end user’s reporting needs, some users may choose to use any of the six other tools for reporting in
Financials such as:
• General Accounting Dashboard: This provides access to Account Groups and uses the
Account Monitor to efficiently monitor and track key account balances in real time.
• Account Inspector: You can perform ad hoc queries from account groups and financial
reports through drilldown to underlying journals and subledger transactions.
• Reports and Analytics: This other reporting tool has a panel that reflects the folder structure
of the BI Catalog. Users can access and run any Oracle Transactional BI analysis, report, or
dashboard. Users cannot run financial reports or BI Publisher reports from this interface. This
interface can be used by all Financials users.
• BI Catalog: This is a component of the Enterprise Performance Management Workspace
where you can run all report types. You cannot run BI Publisher reports from here.
• EPM Workspace: You can create Reports, Books, Snapshot Reports, Snapshot Books,
Financial Reporting Batches, and Batch Scheduler, and schedule batches to automatically run
and burst to email.
• Enterprise Scheduler System (ESS): Only BI Publisher reports can be submitted from this
interface. Users access this interface by navigating to Tools > Scheduled Processes. Most
Financials users have access to this interface to run standard reports for General Ledger,
Payables, Receivables, and so on.

Summary
In this lesson, you should have learned how to:

• List the available implementation resources
• Describe the course schedule
• List the key features of Oracle Accounting Hub Cloud
• Discuss the rapid implementation approach of registering source systems
• Describe the Accounting Hub Cloud reporting options

2
Introducing Oracle Cloud Navigation

Objectives

• Navigate Oracle Cloud Applications.
• News Feed home page springboard layout.
• Explore dashboards.
• Examine panels.
• Describe personalizations.

Getting Started in Oracle Cloud Applications: News
Feed Home Page Springboard
Administrators can set the default home page layout to any of the following:
• Panel
• Banner
• News Feed
Navigate to: News Feed Home Page.

Oracle Cloud Applications are:
• Designed from the ground up, using the latest technology advances and incorporating best
practices gathered from thousands of customers.
• Completely open, service-enabled enterprise applications.
• Designed with features for the best-in-class user-interface designs and workflows that optimize
usability and deliver business value.
All functionality revolves around an Oracle Cloud Applications Home Page, which you can personalize:
• Get a quick glance at your work-related conversations and announcements.
• Use the Application link icons to navigate to pages and dashboards.
• Access the Navigator to access additional applications.
Note: The Home Page view changes based on your roles and privileges.

The News Feed Home page layout is a modern theme with a unique icon style. The global header icons
render in an Outline style:
• Show Help and Access Accessibility Settings are in the Settings and Actions menu.
• Set Help Options to enable the help icons that appear by default on the pages.
• Leads the industry trends by offering a content rich, yet simple to use interface that presents
enterprise information to help you make informed decisions and take quick actions. Easy
navigation that is consistent across various devices such as desktop, tablet, and smartphone.
When set, this home page contains:
• An Applications section.
• A series of updates with important information that you can view at a glance, such as Things
to Finish, News and Announcements, and Analytics.
• A list of quick actions, if available to quickly perform some key tasks.

Sections: Things to Finish and News and
Announcements
• Things to Finish Section shows:
– My Work Items
– My Notifications
• Use Show More and Show
Less to toggle between these views.
• News and Announcements Section shows:
– Employee News
– Active Announcements
Things to Finish section:
• Provides you with a count of any pending notifications that are assigned to you and may
require an action from you.
• A new count link named Created by Me lists the approval requests that you have created.
Click the link to navigate to a full list of notifications pertaining to that count.
• Items listed in the Things to Finish section are same as the notifications listed in the global
header.
- The list displays the latest notifications first and allows you to scroll horizontally to
view more notifications. You can clear a notification from the list by clicking the
Close icon.
- When you clear a notification, the count does not change since no action is taken on
the notification.

News and Announcements
• The News and Announcements section displays all active announcements available to you.
- Click an announcement image to view more details.
- Use the Previous and Next icons to navigate through various announcements.
• When no active announcements are available, this section does not display any content.
• Administrators must create an announcement and add an image to display it in the News and
Announcements section of the home page. If no image is added, only the subject of the
announcement is displayed on the home page.

Analytics Section
• The Analytics section displays:

– A set of infolets.
– Other configurable pages as tabs.
• Use the Refresh link to load or refresh the content
in this section when the refresh data message appears.
Navigate to: Springboard > Analytics.
This screenshot show the General Accounting Infolets.
Use infolets to view information at a glance from different sources in an efficient and timely way
directly from the Welcome Springboard. You have the right information instead of just more data to
sift through.
Mobile device support is available to take your work on the go enabling you to close your books
quickly. You can spot trends and exceptions to gain insights about your financial results in real-time.
In Financials there are currently four choices of Analytics displays:
• Cash Management Infolets
• General Accounting Infolets
• User-Defined Infolets
• Order to Cash Infolets
Use the Infolet list icon at the top of the section to select your infolets.
Note: You can only view those infolets that you have permission to access.

News Feed Navigator
• The Navigator reflects the

contemporary look of the News Feed
home page layout.
• Some global header features are not
available, such as:
– The Watchlist
– Favorites
– Recent Items
The Navigator has:
• Page entries for work areas such as Sandboxes, Migration, Appearance, Structure, User
Interface Text, Business Objects, Application Composer, and Page Integration move from
the Tools group to a group called Configuration.
• Page entries for standalone work areas, such as Getting Started, Social, My Dashboard,
Marketplace, and Setup and Maintenance, are part of a Others group.
• A contemporary look of the News Feed home page layout. Its content is displayed to provide
a top level group or cluster view for easy navigation or an expanded list view.
Tips And Considerations
Administrators can define the display settings of the home page sections using the Home Page Layout
page of the Appearance work area. You can use the Visible field for a section to show or hide it on the
home page, and the Move Up and Move Down icons to adjust the relative positions of the sections on
the home page.
For groups with associated quick actions, administrators can use the Navigation Configuration page of
the Structure work area to configure them. Click the group name to edit it, and then click the Quick
Actions tab to create more quick actions or make changes to the existing ones, such as rename, show
or hide, and reorder them.
To launch the applications on your mobile device, ensure that you have disabled the pop-up blocker
for your device.

Personalizing the Springboard
With the Personalize Springboard feature you can:

• Remove Application Icon Links
• Add Application Icon Links
• Remove Application Groupings
Navigate to: New Feed Home Page Springboard.
From any Application Grouping name, click on the Plus sign to use the Personalize Springboard
feature.

Adding and Removing Applications from the
Springboard
Navigate to: News Feed Home Page Springboard > Click on the Plus sign.
The Personalize Springboard feature enable you to:
• Add an Application: For an application that are not visible on the springboard, select the
checkbox next to the application. For example, check the box next to File Import and Export
application under the Tools grouping name to activate that application on your springboard.
Note: You must have the privilege for that application otherwise it is not available to be added
to the grouping.
• Remove an Application: For applications that are no longer needed but might be needed in
the future, deselect the checkbox.
• Remove the Application Grouping Name: To remove the entire Application Grouping name,
deselect all the checkboxes under that grouping. For example, if you are done with your
implementation and want to remove My Enterprise from you springboard; deselect Offerings,
Enterprise, and New Features.
Note: Removing an application or an application grouping name does not remove it from the
Navigator. Therefore, if you need to get to an application that you have removed from your
springboard you can still get to through the Navigator.

User Interface
Global Area
Panel Tabs
Panel
Section
Navigate to: Financial Reporting Center.
Each page can be divided into components. The slide shows an example of the main components in
the Oracle Cloud User Interface.
• Global Area: Contains links to help you navigate user interfaces, personalized links and tools,
and the name of the user who is signed in.
• Section: Contains the transaction or form that requires creation, editing, or review.
• Panel: Contains links to tasks, process, and reports and enables search on some panels.
• Panel Tabs: Opens several different panels including the Tasks, Search, and Report panels.

General Accounting Dashboard
Navigate to: General Accounting > General Accounting Dashboard.
The General Accounting Dashboard is the main dashboard for Oracle General Ledger functionality
including Journals and Period Close.
The General Accounting Dashboard contains the following sections:
• Account Monitor
• Intercompany Transactions
• Journals
• Closing Status
• Process Monitor
The General Accounting Dashboard contains the following functionality with direct links:
• Journals
• Period Close
• Inquiry and Reporting
• Planning and Budgeting

Work Areas
Navigate to: General Accounting > Period Close.
A work area is a grouping of similar tasks. The Period Close work area includes tasks for opening and
closing accounting periods for Oracle General Ledger and subledgers.

Panel
Click on the Tasks icons to open the panel. Use the panel tabs to:
• Access features without leaving the current application.
• Perform searches.
Tasks Panel Tab
• Run reports.
Tasks
Panel
Navigate to: General Accounting > Journals.
The panel, an anchored component on the right side of a page, contains one or more vertical tabs to
perform actions to enable you to search, run reports, and view integrated conversations in the context
of the current task.
• Open the panel by clicking one of the panel tabs. The panel is collapsed by default.
• Use the slide-out panel to access features directly from any screen without leaving the
current application or navigating through different roles or hierarchies.
• View the tasks available for your user role.

Practice 2-1 Overview: Getting Started in Oracle
Cloud Applications
This practice covers the following topics:
1. Running the session warmer scripts.
2. Signing in to Oracle Cloud Applications.
3. Exploring the News Feed Home page.
4. Signing out of Oracle Cloud Applications.

Personalizations Overview
With personalizations, you can:

• Set user preferences.
• Using Structure Work Area
• Save searches.
• Configure table columns.

Setting User Preferences
Navigate to: Your username > Set Preferences.
User preferences enable you to set many defaults that affect your user experience. The preferences
include the following tasks:
• Regional: You can set your territory, date format, time format, number format, currency, and
time zone.
• Language: You can set which language you want for your:
- Default Language: The setting that displays the language used at initial sign in.
- Current Session Language: This setting overrides the default language for the
current session only. For example, your default language is set to Spanish and you
need to process several reports in English. Rather than having to set the report
language process option for each report to English, you can set your current session
language to English to have all of the reports’ output be in English.
- Display Name Language: The setting that displays all person names including your
own name in the global area, in a specific language. For example, if your display
name language is Spanish and your name is Alexander, then you see your name as
Alejandro.

• Accessibility: You can set the accessibility as the default mode or you can choose to use a
screen reader. You can also set the color contrast to standard or high and you can set the font
size to large or medium.
• Password: You can change your password according to you company’s policy.
• Proxies: You can designate another user as a proxy to sign in to the application and perform
tasks on your behalf. Proxies are helpful when you can't perform the tasks in person during a
specific period.
• Watch list: You can set which categories or items you want to include in your watch list. You
can access your watch list from the Watch list icon on the home springboard. For example,
you might want to track your expense reports.
• Oracle WebCenter Portal: You can set your general preferences, password, my accounts,
messaging, APPLCORE_PORTRAIT, presence, subscriptions, search, and e-mail. The Oracle
WebCenter Portal is a web platform that allows organizations to quickly and easily create
intranets, extranets, composite applications, and self-service portals, providing users a more
secure and efficient way of consuming information and interacting with applications,
processes, and other users.

Saved Searches
Using saved searches, you can:

• Create any number of saved searches.
• Make a default search.
• Have it run automatically.
Navigate to: General Accounting > Journals > Tasks panel > Manage Journals
A saved search captures search criteria and other settings so that you can easily run the same search
again later. These saved searches in the local area aren't the same as those for the global search.
You can change the settings, rename, or delete any of your saved searches.
Some saved searches in the local area are available for you to use as Watchlist items.

Configuring Table Columns
You can perform the following actions on

columns directly from the table:
• Sort data
• Reorder
• Adjust the widths
You can perform the following actions on
columns from the Manage Columns window:
• Hide or show
• Reorder
Changes to columns become a user
personalization and will persist between sessions.
Navigate to: General Accounting > Journals > Tasks panel > Manage Journals
From the tables, you can:
• Sort either ascending or descending on a specific column.
• Reorder the columns by dragging them to the desired location.
• Adjust the widths by dragging the side of the column.
From the Manage Columns window, you can
• Hide or show any of the available columns.
• Reorder any of the visible columns.

Practice 2-2 Overview: Using Personalizations

• Setting user preferences.
• Creating a saved search.
• Configuring columns.

Summary

• Navigate Oracle Cloud Applications.
• News Feed home page springboard layout.
• Explore dashboards.
• Examine panels.
• Describe personalizations.

3
Financials Setup Overview

Objectives

• Explain the benefits and key concepts of Oracle Functional Setup Manager.
• Use the opt in feature to enable offerings, functional areas, and features.
• Manage setup data.
• Explore audit polices and report.
• Use export and import to set up your data.
• Explain how to migrate data you setup from test to production.

What is Functional Setup Manager?
Plan Opt In
Functional Setup Manager provides an

integrated, end-to-end applications
Maintain
Setup
setup and administration process.
Deploy
The Oracle Functional Setup Manager facilitates initial setup and ongoing maintenance. The
Functional Setup Manager guides you through the ongoing steps including:
• Planning: Identify the offerings you want to implement. Evaluate what functional
areas and features to opt into and prepare accordingly for their setup requirements.
• Opting In: Select the offerings, functional areas, and features that best fit your
business requirements by enabling them.
• Setting up: Use setup tasks to enter setup data necessary for your enabled offerings
and functional areas.
• Deploying: Move your verified setup data from the test environment to a production
environment and deploy to all users to start transaction processing.
• Maintaining: Update setup data or opt into configuration of the functional areas
and features as necessary.
• The Application Implementation Consultant job role has full access to perform all
Functional Setup Manager-related activities. Other users must include the
Functional Setup User role in addition to other roles or privileges needed to perform
specific setup activities.

• For more detailed information about security requirements for Functional Setup
Manager, refer to the Security Reference for Oracle Applications Cloud Common
Features guide in the All Books for Oracle Cloud page of the Oracle Help Center
(docs.oracle.com

Functional Setup Manager Benefits
1
Centralized Setup Guided Process 2
Single interface for all Oracle Cloud Applications. Task lists guide you through recommended setup.
Easier Management of
Configurable
3
Opt into functional areas and features to fit
Setup Data 4
business needs. No guessing with built-in prerequisites and
dependencies.
5
Setup Data Migration Reporting 6
Export and Import of setup data between Comprehensive reporting for setup data
environments. validation.
The screenshot of the Offerings shows the wide range of offerings available with Oracle
Cloud. All of these offerings use the Functional Setup Manager, which provides you with
many benefits including:
• Centralized Setup: A single interface for all your Oracle Cloud applications.
• Guided Process: The offering task lists guide you through the recommended setup
tasks.
• Configurable: An opt in approach to functional areas and features that can be

configured to your business needs.
• Easier Management of Setup Data: The built-in prerequisites and dependencies

eliminate uncertainty and eases the management of setup data.
• Setup Data Migration: The export and import process move setup data smoothly
between environments.
• Reporting: The comprehensive validation reporting exists to help you confirm your
setup data is valid.
Functional Setup Manager also offers the following:
• Standardized application configuration and setup experience.
• Flexible processes for managing setup:

- Setup by functional areas for an adopt-as-you-go approach.
- Implementation projects to manage exception setup situations.
- Upload functionally to enter setup data in bulk.

Key Concepts
Offerings Functional Areas Features
Navigate to: My Enterprise > Offerings.
• Offerings: Functional groupings within Oracle Cloud Applications representing

enterprise business processes that are subscribed and administered as a unit.
• Functional Areas: Functional modules such as business sub-processes within an

offering.
• Features: Optional or alternative business methods and practices applicable to a

functional area. Depending on the setup requirements for a feature, you can:
- Select if the feature either applies or it does not.
- Select one choice to apply to the feature out of multiple choices.
- Select many choices to apply to the feature out of the multi-choices

available.

Review Offerings and Prepare to Opt In
1. Navigate to: My Enterprise > Offerings.
2. Select the Offering you want to
implement.
3. View a detailed description.
4. Check the Status to determine if the
offering is enabled.
5. Use the Opt In Features button to
manage opt in configuration.
6. Optionally, expand the Related
Documents to learn about
implementation requirements.
Before using any Oracle Cloud Applications, you must opt into relevant offerings and their
features by enabling them.
Two Financials related offerings are available. Select one or both of them according to your
subscription.
• Financials offering: Includes Oracle General Ledger and Oracle Subledger

Accounting application features, as well as at least one of the subledger financial
applications.
• Accounting Hub offering: Includes Oracle General Ledger and Oracle Subledger
Accounting application features integrated with an existing enterprise resource
planning (ERP) system or third-party application to enhance the current reporting
and analysis.
Select an offering by clicking on the icon to see a detailed description. The current status of
the offering is also shown. In the beginning, the offering status shows Not enabled.
Use the Opt In Features button to opt into the features that are applicable to your business
requirements.
• If you need to change the opt in configuration of the offering, use the same button.
• Before you proceed to opt in, expand the Related Documents section to review
details about the implementation requirements of the offering to help you plan
your implementation.

Opt into Offering, Functional Areas, and Features
Offering, functional areas, and sub
functional areas are shown in a hierarchy.
1. Check Enable to opt in:
a. A child cannot be enabled unless
the parent is enabled.
b. A non optional functional area is
enabled automatically when the
parent is enabled.
2. Use Edit icon to open Edit Features to
opt into related features.
Navigate to: My Enterprise > Offering > select your offering > Opt In button.
In the Opt In page:
• The first row shows the Offering and the subsequent rows show the offering’s
functional areas. If sub functional areas exist they are shown underneath their
parents.
• To opt in, select the Enable checkboxes of the offering and the functional areas.
- If a child is not optional, then the child is enabled and displayed as read-
only when the parent is enabled. For example, when the Supplier Invoice
Processing parent is opted into, the Payables child functional area is
enabled. Child functional areas that are not optional, are enabled or
disabled automatically when their parent is enabled or disabled.
- A child cannot be enabled unless its parent is enabled. For example, to

enable Collections, Customer Invoice Processing must be enabled first.
• Click the Edit icon in the Features column to enable and opt into related features.

Review What’s New and Opt into New Features After
Upgrade
After an upgrade of the Oracle Cloud
applications, go to the New Features page.
• Review newly introduced features for
your enabled offerings.
• Enable the Show Help icon to display
the Learn More column.
• Use the Opt In button to go to the Edit
Features pages to enable the new
features.
Navigate to: My Enterprise > New Features.
Consult additional help topics from the Learn More icon to better understand the new
features.

Practice 3-1 and Demonstration 3-2
This practice and demonstration cover the following topics:

• Practice 3-1: Browsing offerings and reviewing related documents for planning your
implementation.
• Demonstration 3-2:
– Opting into an offering and its functional areas and features.
– Reviewing and opting into the new features of your enabled offerings after your
Cloud applications are upgraded.

Manage Setup Data with Complete Transparency to
Requirements
Navigate to: Others > Setup and Maintenance
Achieve optimal setup results with auto-generated, best-practices task lists.
• Built-in prerequisites and data dependencies minimize overlooked requirements.
• Configurable opt in features prevent wasted effort in unnecessary setup.
• Direct access to setup pages enables managing setup data in the correct sequence.
• List of required tasks expedites transaction readiness.

Manage Setup Data Your Way Using Flexible
Processes
Functional Area Based Implementation Project Based
Utilize functional module based setup for Manage exception cases by using highly
adopt-as-you-go approach. configurable task lists.
Functional Area Based:
• This setup process is ideal for an enterprise looking for a simpler implementation
approach that follows setup best-practices.
• After you enable an offering and configure the opt-in selection of its functional
areas and features, you can set up the offering by using its functional areas as a
guide.
• This adopt-as-you-go approach to functional setup gives you the flexibility to set
up different functional areas of the offering at different times.
• For example, you can begin with setup of the functional areas you require
immediately to start transactions. You can then set up other functional areas as you
adopt additional offering functionality over time.
Implementation Project Based:
• An implementation project is a list of setup tasks you use to implement your Oracle
Applications Cloud.
• With this method, you create an implementation project to generate a list of setup
tasks, assign tasks to various users who are responsible for managing setup data,
and monitor progress of the completion of the setup tasks.

Manage Setup Data Using Functional Areas
Using the functional areas setup method is
the best practice for configuring your
Oracle Cloud applications.
Begin by:
1. Navigating to the Setup and
Maintenance page.
2. Select the desired functional area.
3. Check the Shared link to see other
offerings sharing this functional area.
Note: All enabled functional areas based on
opt-in configuration of the offering are
displayed.
The offerings you enable determine:
• The order of the setup sequence that helps you avoid data dependency errors.
• The content in the Shared link which indicates if more than one enabled offering
contains that functional area.
• If the setup tasks are mandatory. An asterisk indicates if the functional area has
mandatory setup tasks.

Related Setup Tasks
Navigate to: Others > Setup and Maintenance.
When a functional area is selected, the related setup tasks are listed in the Task section.
• If the functional area has mandatory setup tasks then those are shown by default.
• Use the Show drop down list to select All Tasks to display optional tasks.
• If the functional area has NO mandatory tasks, then ALL setup tasks are displayed.
Display order of the tasks reflects the sequence in which they should be performed to
address data dependencies.
To enter setup data, drill down on the task name to open the appropriate page.

Tasks with Scope
Navigate to: Others > Setup and Maintenance.
Some tasks require a context called Scope before their setup data can be entered. If setup
data is segmented by a specific context or scope, you can perform the setup task iteratively,
such as assigning different ledger options to different primary ledgers. For example: Ledger
Options for the Vision Brazil primary ledger can be different from ledger options assigned to
the Vision Canada primary ledger.
Use the link in the Scope column to:
• Select a scope value if not already selected.
• Changed the currently selected scope value.

Manage Setup Data Using Implementation Projects
An implementation project is a list of setup

tasks you use to implement your Oracle
Applications Cloud.
Using this method, you create an
implementation project to:
1. Generate a list of setup tasks.
2. Assign tasks to various users who are
responsible for managing setup data.
3. Monitor progress of the completion of
the setup tasks.
Navigate to: Others > Setup and Maintenance > Task panel > Manage Implementation
Project.
Note: This method is best suited when you have a need to modify the default setup best
practices, or manage setup as a project by assigning responsibility of managing setup data to
a broad group of users and monitor their progress.

Create an Implementation Project
1 Use Create icon.
2 Enter basic information.
Select offering and functional areas you want to

3 implement and then use Save and Open Project button.
Projects > Create icon.
When you create an implementation project:
Generate the initial list of tasks by selecting one of your enabled offerings.
• If you plan to use more than one offering, create a separate implementation project
for each one of them.
• Selecting an offering, which automatically selects the offering’s core functional

areas, you may also select none, some, or all of the optional functional areas of the
offering that are also enabled.
Use your selection of the offering and the functional areas as a template.
• A task list hierarchy is generated for the implementation project.
• The task list hierarchy includes the tasks that are associated at the time with your
selected offering and functional areas, and their dependent features that are
enabled.
• Within the task list hierarchy, the tasks are organized according to prerequisite and
dependency requirements of the setup data.

Note: Oracle recommends that you enter setup data in the same sequence as the tasks to
avoid missing prerequisite data.

Review and Assign Tasks
1. Review generated task list.

2. Use the Assign Tasks button to assign users to tasks.
– Assigned To column shows the user to whom the task is assigned.
– Due Date column shows the due date specified for the user.
Project > Assign Tasks.
You can assign the tasks of an implementation project to the users who are responsible for
managing setup data represented by those tasks.
• Typically, each setup task is assigned to a single individual.
• However, you may also assign multiple individuals to the same task if your
implementation project requires such assignment.
• Each of the individuals has the flexibility to perform the task and manage setup
data independently of the other users assigned to the same task.
If you specify due dates for completing the assigned tasks, you can monitor the progress of
the task assignments and the progress of the overall implementation project. If you assign
multiple people to a task, you can assign the same due date to each person or you can assign
a different due date.

Perform Assigned Implementation Tasks
Functional users to whom setup tasks are assigned, select:

• Their implementation project.
• An assigned task.
• Scope, if applicable.
• Go to Task icon to enter setup data.
Navigate to: Others > Setup and Maintenance > Tasks panel > Manage Implementation
Project.
If you are a user to whom setup tasks from an implementation project have been assigned,
then a consolidated list of all of your assigned tasks is presented to you.
• Use each task from the list to enter setup data that the task represents.
• If you have a long list of assigned tasks, you can filter the list by due date, task
status, or implementation project name to find a task more easily.
• In addition, you can search for a specific task in the list by the task name.
Note: You must have the proper security privileges to perform a task.

Searching for a Task
If you know the name of the task, you can easily perform a search.
Navigate to: Others > Setup and Maintenance > Task panel > Search
You can use the search feature in Functional Setup Manager.
• Search for a task using the full or partial name of the task.
• Use of a partial name does not require wildcards and is not case sensitive.
The search feature can also be used for ongoing maintenance.
Note: Some of the tasks and features are not accessible using the search feature if scope is
required or if the offering has not been enabled.

Rapid Implementation Task List
Define Common Financials Configuration for Rapid Implementation
• Manage Geographies
• Create Chart of Accounts, Ledger, Legal Entities, and Business Units in Spreadsheet
• Upload Chart of Accounts
• Upload Ledger, Legal Entities, and Business Units
• Create Cross-Validation Rules in Spreadsheet
• Create Banks, Branches, and Accounts
• Manage Tax Regimes and Taxes
• Run Jurisdiction and Rates Upload Program
Note: This is a sample and not a complete list of tasks.
Projects > Edit your implementation project > Select and Add icon. Search for %Rapid% to
see all Rapid Implementation task and task lists.
• Use the Define Financials Configuration for Rapid Implementation task list to
streamline your setup configuration to focus only on the critical setup steps. The
rapid implementation task list minimizes the time needed for you to complete your
key setups and enable the day-to-day use of Oracle Financials Cloud.
• The rapid implementation task list includes tasks that are:
- Critical setup tasks for initial setup.
- Setup steps that are required by most users.
• To create an implementation project that includes the Define Financials

Configuration for Rapid Implementation task list, use the Manage Implementation
Projects page in the Setup and Maintenance work area. The application
implementation manager can customize the task list and assign and track each task.
Note: You are not restricted only to the setup configuration in the rapid implementation task
list. You can manually add the standard Financials offering task lists and tasks to your rapid
implementation project to change and update your setup.

Practice 3-3: Accessing Task Lists and Tasks

• Using functional areas of an offering.
• Using an Implementation Project.

Configure Auditable Setup Attributes and View Audit
NE
Report
• Configure setup attributes for audit from the Setup and Maintenance work area.
• Track changes to these attributes using the Audit Report.
Auditing is used to monitor user activity and all configuration, security, and data changes
that have been made to an application.
• Auditing involves recording and retrieving information pertaining to the creation,

modification, and removal of business objects.
• Auditing takes into account all the operations performed on an object and its
attributes, such as create, update, and delete.
• All actions performed on the business objects and the modified values are also
recorded.
• The audit information is stored without any intervention of the user or any explicit
user action.
• Use audit policies to select specific business objects and attributes to be audited.
The decision to create policies usually depends on the type of information to be
audited and to the level of detail required for reporting.
Note; Your configuration settings determine which attributes to audit for a given object, and
when the audit starts and ends.

Audit History Enablement
Oracle Financials Cloud currently supports audit history on several key business
objects.
• Individually configure and enable auditing of each business object.
• By default, auditing is disabled for all applications.
Navigate to: Setup and Maintenance > Setup: Financials > Applications Extensions > Manage
Audit Polices.
Steps to enable:
• You must configure the business objects and select the attributes before enabling
audit otherwise auditing remains inactive.
• Ensure that you have a role with the assigned privilege Manage Audit Policies.
• To view the history or to create a report, you must have a role with the assigned
privilege View Audit History.
• To open the Audit History work area, from the Navigator menu, select audit reports.
Tips and Considerations:
• Audit enables tracking the change history of particular attributes of a business

object, provided those objects are selected for audit and auditing is enabled for that
application.
• Your configuration settings determine which attributes to audit for a given object,
and when the audit starts and ends.
• Auditing takes into account all the operations performed on an object and its
attributes, such as create, update, and delete.

Manage Setup Data Entry in Bulk
Navigate to: Others > Setup and Maintenance > Actions menu on a task.
Note: If the Action menu is not showing, go to View > Columns > check Actions.
Use a CSV file format based setup data export and import by task as an alternative to
entering data using the user interface. Use this method if:
• You have a substantial number of setup data records with few attributes to enter for
a setup task.
• Entering this data using the setup page is cumbersome and prone to errors.
• Functional Setup Manager provides you the ability to export and import setup data
for a specific task that meet these requirements using a CSV file.
Messages inform you if CSV child rows are skipped because:
• Parent rows do not exist or are not selected in the import.
• Duplicate rows are found. The remaining rows are processed.
Note: Check with the product documentation to validate if a task supports CSV export or
import that you may require.

Export and Import CSV Processes
1. Select a task and use the Action button to create a CSV export file.
– Select whether to export an empty file when creating new data or to export existing
data for an update.
– If Scope is enabled, then optionally filter exported data.
– When the processing completes, download the file and review data.
2. Select a task and use the Action button to create CSV import process.
– Upload the CSV file package containing appropriate data.
– Review the processing results.
– Verify the imported data.
Navigate to: Others > Setup and Maintenance > Actions > Export or Import to CSV File.
These export and import processes can be used outside of the export and import pages in
Functional Setup Manager (FSM) by using the following application programming interfaces
(APIs):
• FSM SOAP Service
• FSM REST API
SOAP and REST are two different standards of web services. These APIs are available if you
want to utilize a CSV export and import and invoke the process external to Functional Setup
Manager.
• For example, use this method if you are moving to Oracle Cloud applications from
Oracle E-Business or other systems where you have setup data such as legal
entities, business units, chart of account, so on. You can write your own web
services to extract setup from your existing systems to a CSV file, and then leverage
these web service APIs to import that data into the Oracle Cloud applications.
• See the following documents for more details on using these APIs:
- SOAP Web Services for Common Features in Oracle Applications Cloud

Guide > Business Object Services chapter > Setup Data Export and Import
topic in the Oracle Help Center.

- FSM: Setup Data Export and Import Service Usage (Doc ID 2156193.1) in My
Oracle Support.
Note: The CSV export option is now available for all setup tasks which are enabled for
regular XML export, import. The title for each of the column is same as the corresponding
database column attribute name or in some cases user friendly names. These column name
will be mostly the table column name without any underscores. In some cases where the
same column, for example effective_start_date, exists in more than once the process will
append numeral like effectiveStartDate1, effectiveStartDate2, which will be displayed as
column heading in CSV file.

Copying Setup
• Get the benefit of creating multiple copies of complex but similar setups quickly.
• Reduce data entry effort. You only need to:
– Setup one time.
– Make a copy.
– Make changes to the copy as needed.
Navigate to: Others > Setup and Maintenance > Task panel > Copy Configurations.
For example, create a business unit structure and then copy the setup to create a new
business unit structure whose setup data requirements are similar to the original business
unit.
• Start the copy process by selecting an existing setup configuration, whose setup
data is then copied to a staging area.
• Modify the setup data in the staging area according to the requirements of the new
setup configuration you want to create.
• Submit an import process which creates the new setup configuration.
• Review your new setup configuration to ensure that the setup meets your
requirements.
Note: You can also make additional changes to the imported data, if needed.

Migration Overview
Two migration options:

• Classic Migration is the default
migration.
• Unified Migration: After you opt in to
the Unified Sandbox feature:
– Enabled to be used.
– Changed to the appearance and
behavior of the feature.
Classic Migration
• Migrate all configurations in the source environment.
• Manually download the configuration set from the source and manually upload it
into the target.
• Preview configurations in the target environment before applying them.
Unified Migration
• Register the target environment in the source environment.
• Migrate only (optionally) new changes if both environments are synchronized.
• Preview your configurations in this sandbox instance before applying them to the
mainline.
• Understand that a migration set is:
- Automatically sent to the target environment for import, if the target is

registered and available at the time.
- Imported into a sandbox instance before it's applied to the target

environment.

For more information, see Oracle Help Center: Oracle Applications Cloud Configuring and
Extending Applications guide.

Classic Migration
• Export and import setup data by:

– Offerings and Functional Areas.
– Or, Implementation Projects.
– Built-in sequential task list helps to avoid data dependency errors.
• Use Scope to filter and export sub set of data.
• Leverage the Comparison Report before import to avoid unexpected data override.
Navigate to: Others > Setup and Maintenance > Actions > Export or Import.
Almost all Oracle Cloud implementations require moving functional setup data from one
instance to another at various points in their life cycle.
• For example, you might first implement in a development or test application

instance and then deploy to a production application instance after testing.
• You can move functional setup configurations of applications from one application
instance into another by exporting and importing setup data.
Note: The instances need to be at the same code level.

Best Practices for Managing Setup Across
Environments
• Enter setup data and verify transactions in Test.
• After setup data passes verification, for example, UAT (User Acceptance Testing):
– Export from Test.
– Import into Production. TEST
Export and Import
P2T
(if needed)
PRODUCTION
Note: If Test requires refresh from Production, then use P2T (Production to Test), a reverse
production-to-test process to synchronize the test to production instances before
performing incremental setup in the test instance.

Best Practices for Managing Setup: Using a Gold Copy
1. Enter setup data in Gold.
2. When ready to verify, export from Gold
and import into Test. GOLD
3. Verify transaction in Test, for example, Export and

using UAT. Import
Export and
Import
4. If setup data requires changes, repeat
Export and
step 1 to 3. Import TEST
Offering, if
5. After setup data passes verification, needed
export from Gold and import into
Production.
P2T, if
PRODUCTION needed
• In the next testing cycle, if Test requires a refresh from Production, then use P2T.
• If Gold requires a refresh from Production, then rebuild Gold, export Offerings from
Production and import into Gold. This method brings over setup data from
Production into Gold without bringing over transaction data.
Note: A Gold copy (environment) is an operating standard for many enterprises, particularly
large ones. In this environment, your setup data is maintained as the source of truth or
system of record.

How Does Setup Import Manage Data?
• If a record exists in the configuration package, but does not exist in the target, then
the import creates the record.
• If a record does not exist in the configuration package, but exists in the target, then
the import does nothing to the record.
SOURCE TARGET
Export and Upload and

Download Import
Configuration
Package
If a record exists in both the configuration package and the target, then:
• If all attribute values are the same in both, the import does nothing to the record.
• If any attribute values of the record are different, the import updates the record in
the target with the values in the configuration package.

Export an Offering or a Functional Area
1. Export entire offering or a functional
area for initial migration.
2. Optionally, select scope to filter the Export entire
offering for initial
exported data. migration.
3. When the export completes, download
the file to import.
4. Review tasks related to setup data that
Export a functional
are not be migrated by import. area for incremental
maintenance.
5. Download data reports to verify
exported data.
Navigate to: Others > Setup and Maintenance > Actions > Export.
During export, appropriate setup data is identified as follows:
• When you export setup data for an offering, the export definition includes setup
data for all enabled functional areas and relevant features in the offering.
• When you export setup data for a single functional area within an offering, the
export definition includes only setup data for that functional area and relevant
features.
The export setup data process generates different reports that you can review in the
application or download for offline review.
Navigate to: Others > Setup and Maintenance > Actions > Export > View All > select your
export > Actions > Download to see the following reports:
• Process Results Summary Report: Shows what setup data was exported, appears in
order by business objects, and includes information on any errors encountered
during the export process.
• Setup Data Report: Lists all the setup data in the processed configuration package
and includes individual reports for each business object.
• Process Results Report: Is available as a text file showing the status of an export
including detailed information on the errors encountered during the process.

Create a Comparison for an Offering or Functional
Areas
Set up data comparisons to identify the differences between the setup data of two
configuration packages, or two different versions of the same configuration package.
• Use a comparison to learn how data for a given implementation has changed over
time.
• Review a comparison to identify the differences among one or multiple business
objects relevant to a configuration.
Navigate to: Others > Setup and Maintenance > Actions > Compare Setup Data.
Three columns display the number of discrepancies:
• In Both With Mismatch: Indicates how many records exist in both sources but have
some differences.
• Only in Configuration 1: Indicates how many records exist only in the first source
and do not exist in the second source.
• Only in Configuration 2: Indicates how many records exist only in the second source
and do not exist in the first source.

Import an Offering or a Functional Area
1. Import an entire offering for an initial migration or a functional area for incremental
maintenance.
2. Upload the exported file.
– The offering or functional area level from export must match.
– Optionally, use a data comparison before importing to avoid accidental override.
– Or, choose to import the feature configuration from the source system.
3. Review and process the displayed tasks, which represent setup data that must be migrated
manually before the import process begins.
4. Resubmit the import process.
5. Review the comparison results and if satisfied, continue to import.
6. When the import completes, review and process the displayed tasks which represent setup data
that must be migrated manually after import.
Navigate to: Others > Setup and Maintenance > Actions > Import.
Use the Import Offering Setup Data page to upload and import previously exported setup
data. During import, a configuration package created by the export process is uploaded.
• All setup data contained in the configuration package is imported into the
environment you initiate the setup data import from.
• The offering and functional area must already be enabled for the implementation
before you can import setup data into the environment.
• In some environments, the feature selection is not selected. Use the feature
configuration to ensure desired features are imported.
• One you initiate the import process, monitor the progress and check the status
from the Import Offering Data History page.

Export and Import an Implementation Project
1. Create a Configuration Package by selecting an Implementation Project.
2. Review business objects such as setup data to be exported.
3. Optionally select scope to filter data.
4. When export completes:
– Download file to import.
– Review tasks related to setup data that are not be migrated by import.
– Download data reports to verify exported data.
5. Upload and then import the exported Configuration Package.
6. When process completes, review import results.
7. Review and process the displayed tasks representing setup data that must be migrated
manually.
Navigate to: Others > Setup and Maintenance > Tasks panel > Manage Configuration
Packages > Create icon.
Use an implementation project as the source for exporting setup data when you are required
to modify the list of tasks or of objects.
• The tasks and their associated business objects in the selected implementation
project define the setup export and import definition for the configuration package.
• Depending on your needs, when you create a configuration package based on an

implementation project, you can also modify some additional aspects.
- Exclude some of the business objects from the configuration you selected
to export.
- Change the default import sequence of the business objects.
- Filter the setup data to export.
While the export definition remains the same for each version, the setup data can be
different if you modified the data in the time period between the different runs of the export
process.

Because each version of the configuration package has a snapshot of the data in the source
instance, you can compare and analyze various versions of the configuration package to see
how the setup data changed.
Navigate to: Others > Setup and Maintenance > Tasks panel > Manage Configuration
Packages > Upload button.
All setup data contained in the configuration package is imported into the environment you
initiate the setup data import from.
• In the target application instance, the setup import process:
- Inserts all new data from the source configuration package that does not
already exist.
- Updates any existing data with changes from the source.
• Setup data that exists in the target instance but not in source remains unchanged.

Learn More: Video Tutorials
Video Tutorials • Managing Setup using Implementation

Projects
• Configure Offerings
• Enter data for assigned setup tasks
• Reviewing and Opting Into New
Features • Exporting Setup Data to Configuration
Packages
• Setting Up Offerings
• Comparing Setup Data Using
• Set up Offerings with Scope
Configuration Packages
• Export/Import Setup Data Using CSV
• Importing Setup Data from
• Exporting Offering Setup Configuration Packages
• Importing Offering Setup • Generating Setup Data Reports
• Comparing Setup Data During Import
Link to the Oracle Help Center Financials page:

https://docs.oracle.com/en/cloud/saas/financials/20b/index.html to learn more about
Functional Setup Manager. The videos listed in the slide are found under the Videos link on
the Oracle Help Center Financials page.

Learn More: User Guides
Functional Setup Manager Guide

1. Using Functional Setup Manager
Product Specific Guides

1. Getting Started Guides
2. Implementation Guides
Link to the Oracle Help Center Financials page:

https://docs.oracle.com/en/cloud/saas/financials/20b/index.html to learn more about
Functional Setup Manager. The Functional Setup Manager guide and other product specific
guides are listed under the Books link.

Summary
In this lesson, you should have learned to:

• Explain the benefits and key concepts of Oracle Functional Setup Manager.
• Use the Opt In feature to enable offerings, functional areas, and features.
• Manage setup data.
• Explore audit polices and report.
• Use export and import to set up your data.
• Explain how to migrate data you setup from test to production.

4
Overview of Security
Objectives

• Understand the Oracle Security Model.
• Discuss using the Security Console.
• Examine the changes to the common security features.
• Review security resource materials.

Oracle Financials Cloud Security Methodology
Cloud security methodology can be summarized with the simple statement: WHO can
do WHAT on WHICH set of data.
• Who: The user.
• What: Individual actions a user can perform.
• Which: The set of data.
Who What Which Data

General Accountant Enter and post journals. UK Ledger
Employees View pay slip. Employee’s pay slip only
General Accounting Manager Creates and runs reports. UK Ledger
• Who: The user who performs functions in your company, such as an General Accounting
Manager.
• What: Individual actions a user can perform, such as the ability to create and run reports.
• Which: The set of data that the user can perform the action on, such as UK Ledger.

Security Model: Role Based Access Control
• Users can have any number of roles.

Role
• Roles grant access to functions and Journal
data. Management.
Vison Operations
• Functions and data accessed is
determined by the combination of Intercompany
roles. User Linda Swift Transactions
Entry
General Ledger
Reporting
For example, user Linda Swift has the following roles:
• Journal Management
• Intercompany Transactions Entry
• General Ledger Reporting
Linda can access her journal data for Vision Operations, intercompany transactions, and general
ledger data though reports..

Security Reference Implementation
Oracle Financials Cloud comes with a predefined security reference implementation

which consists of:
• A baseline set of predefined security definitions.
– Job roles that closely match real life jobs.
– Duty roles.
• A set of security components that are:
– Delivered with the offering or service.
– Used to meet the business needs of most enterprises.
The security reference implementation covers all functions and actions that need to be secured. The
security definitions are based on industry standards. You do not need to create new job or duty roles.
The implementation includes:
• Complete set of job roles.
• Duty roles and role hierarchy for each job role.
• Privileges granted duty and job roles.
• Data security policies for each job role.
• Policies that protect personal identifiable information.
• Policies enforced across tools and access methods.
• Segregation of duties policies respected in the design of duties for the job role.
• Segregation of duties conflicts.

Job and Duty Roles
• Job roles represent the job that you hire a worker to perform.
• Duty roles represent logical groups of tasks that are performed in a job.
• You can:
– Create custom job and duty roles by copying existing duty roles and job roles.
– Assign job roles to users, not to duty roles.
For example, a job role can enable users to work with journals. A job role that inherits the duty role can
provide access to the logical groups of tasks.
The duty role General Ledger Reporting provides access to all balances and transaction inquiry and
reporting privileges for General Ledger to the General Accountant job role.

GL Predefined Job Roles
• General Accounting Manager: Manages general accounting functions. These roles

also use the General Accounting Manager role and have the same system access
level:
– CFO: Top corporate financial officer making appropriation and expenditure
decisions.
– Controller: Chief accountant overseeing all accounting functions of the
organization.
• General Accountant: Records and reports financial transactions, accounting
adjustments, accruals and allocations.
• Financial Analyst: Provides analysis on the financial performance of the organization.
• General Accounting Manager
- Record and approve journal entries and allocations.
- Create and maintain budgets.
- Perform revaluations and translations.
- Run reconciliations.
- Consolidate financial data.
- Manage period close.
- Inquire and report on financial balances and transactions.
- Create custom queries and reports.
- Manage accounting system reference data and setups.
• General Accountant
- Record journal entries and allocations.
- Enter budgets.
- Perform revaluations and translations.

- Run reconciliations.
- Inquire and report on financial balances and transactions.
- Review accounting system reference data and setups.
• Financial Analyst
- Perform balance and transaction inquiry and drilldown.
- Run pre-defined and ad hoc financial reports.
- Review accounting system reference data and setups.

Privileges
• Roles assign privileges.

• Privileges provide access to functionality in the application.
• For example, the General Accountant Role contains the Manage Journal Activities
Privilege.
You can assign privileges to roles.
Navigate to: Tools > Security Console > Search for General Accountant role > Edit Role > Next > Cancel.
Navigate to: Tools > Security Console > Search for General Accountant role > Show Graph.

Resources
• Privileges assign resources.

• Resources represent various application artifacts.
• For example, tasks, menu items, buttons, regions, so on.
• You cannot manage or edit resources.
For example, the Manage Journal Activities: Details resource contains the menu items Manage
Journals and other tasks. The Receivables resource contains the prompt for the Billing work area and
the Marketing resource contains the menu prompt for the Campaigns work area.

Data Security Policies
Data Security Polices:

• Control access to data.
• Are granted to a role.
Components of a policy are:
• Database Resource: Table where data
is stored.
• Data Set: Where access is granted.
• Condition: Used to define the Data Set.
• Actions: Performed on the data.
Navigate to: Tools > Security Console > Analytics tab > Database Resources tab.
Navigate to: Tools > Security Console > Search for General Accountant role > Edit Role > Next twice >
Create Data Security Policy.
Navigate to: Tools > Security Console > Analytics tab > Database Resources tab.
You can review information about data security policies that grant access to a database resource, or
about roles and users granted access to that resource.
Data security consists of privileges conditionally granted to a role and used to control access to the
data. A privilege is a single, real world action on a single business object. A data security policy is a
grant of a set of privileges to a principal on an object or attribute group for a given condition. A grant
authorizes a role, the grantee, to actions on a set of database resources.

Analyze Data Security Policies by Resource
• Analyze data security policies by database resource.

• View roles and users that are authorized to the database resource.
• Export the information displayed in the tables.
Navigate to: Tools > Security Console > Analytics tab > Database Resources.
A database resource is an object, object instance, or object instance set. An entitlement is one or more
allowable actions applied to a set of database resources.
• By default, users are denied access to all data.
• Data security makes data available to users by the following means.
- Policies that define grants available through provisioned roles
- Policies defined in application code
• You secure data by provisioning roles that provide the necessary access. Data roles also can
be generated based on HCM security profiles. Data roles and HCM security profiles enable
defining the instance sets specified in data security policies.
- When you provision a job role to a user, the job role limits data access based on the
data security policies of the inherited duty roles.
- When you provision a data role to a user, the data role limits the data access of the
inherited job role to a dimension of data.

Role Inheritance
Role inheritance is a key concept in the security model. The figure illustrates the hierarchy of job and
duty role inheritance which are used as the building blocks in Oracle Cloud Security.
• Almost every role is a hierarchy or collection of other roles.
• Job and abstract roles inherit duty roles.
- For example, the General Accountant job role can have one or more duty roles.
- An abstract role is a type of enterprise role that is not specific to a particular job. The
reference implementation contains predefined abstract roles, such as Employee or
Contingent Worker. Abstract roles inherit duty roles as a means of accessing
application functions and data that users require to perform the tasks associated
with the duties of work not specific to a particular job such as running reports and
processes.
• Duty roles can inherit other duty roles.
• You can also assign privileges directly to job, abstract, and duty roles.
• When you assign job and abstract roles to users, they inherit all of the data and function
security associated with those roles.

Security Features Overview
• Improved Security Console • User Name Generation Rules • Notification Templates
• Enhanced Role Visualization • Password Policies • Password Reset Process
• Upgrade-Safe Management • Administrator Password • User Password Changes
of Factory Shipped Roles Management Audit Report
• Tabular Role Hierarchy View • User Account Locking • Self-Service External
Identity Provider Setup
• Search in Role Hierarchy • User Password Management:
Visualization Self-Service • Bridge for Microsoft Active
Directory
• User Account Management • User Account Locking

Accessing the Security Console
• Use the Security Console to implement, customize, and manage security.

• Create and edit custom roles, as well as create and manage user accounts.
• Access the Security Console through the Navigator menu, under Tools or from the
Welcome Springboard or using the Functional Setup Manager.
Navigate to: Tools > Security Console.
Functional Setup Manager Navigations to Security Console:
• Navigate to: Others > Setup and Maintenance > Setup: Financials > Initial Users > All Tasks >
Create Implementation Users.
• Navigate to: Others > Setup and Maintenance > Setup: Financials > User and Security >
Manage Job Roles.
Manage Duties.
Manage Data Security Policies.
Access to the Security Console is granted through the predefined IT Security Manager role.

Using the Security Console for Roles and Users
• Select the Roles tab to manage roles.

• Select the User Accounts tab to manage user accounts.
• You can view role analytics, manage certificates, and manage Security Console
administration options.
Navigate to: Tools > Security Console.
Within the Security Console, select the Roles tab to manage roles, and the User Accounts tab to
manage user accounts.
You can view role analytics, manage certificates, and manage Security Console administration options.

Compare Roles Feature
• Use to compare the function and data security policies granted between two roles.
• Launch Compare Roles directly by clicking on the button or by choosing the Compare
Roles option in the Search Results.
Navigate to: Tools > Security Console > Roles tab > Search for a role > Compare Roles.
View:
• All comparison results.
• Artifacts that only exist in either the first or the second role.
• Artifacts that exist in both roles.
Choose to view only comparison results for:
• Function security policies.
• Data security policies
• Inherited roles, or combinations.

Move Function and Data Security Policies
• Move function and data security policies from the first role to the second role during
role comparison.
• Export the data displayed in the role comparison results table.
You can make some updates to the second role in the comparison without having to edit the role
explicitly. That is, you can copy a selected function or data security policy from the first role to the
second role when you set:
• Filter Criteria to either Function security policies or Data security policies
• Show to Only in first role
• Note: The second role in the comparison must be a custom role.
• To copy a selected policy to the second role, you click Add to Second Role.
Note: Add to Second Role button is enabled only on the following conditions:
• Second Role is a user-defined role.
• User has Edit Role privilege.
• Filter Criteria does not include a role hierarchy.
• Show is set to Only in first role.

Manage Data Access for Users Page
All users are assigned an appropriate data set using the Manage Data Access for Users
page.
The Manage Data Access for Users is available to all products in Oracle Enterprise
Resource Planning, including:
• Financials
• Procurement
• Project Management
• Risk Management
• Adaptive Intelligent Apps
Navigate to: Others > Setup and Maintenance > Financials > Users and Security > Manage Data Access
for Users.
Data assignments are specific to a role, therefore a user must first be assigned to a role before data
assignments can be created in the Manage Data Access for Users page.
• When selecting a role, the selection is limited to the roles that are currently assigned to the
selected user.
• Required data security policies are only present against the corresponding predefined roles.

Processes to Align the Security Console Tables
• Import User and Role Application Security Data: Import user and role data from LDAP
and store in Applications Security tables.
• Retrieve Latest LDAP Changes: Synchronizes users, roles, and role grants with
definitions in LDAP.
• Send Pending LDAP Requests: Manages requests to create or update users, roles, and
role grants in LDAP.
Navigate to: Tools > Scheduled Processes > Schedule New Process.
Run Retrieve Latest LDAP Changes:
• You run Retrieve Latest LDAP Changes if you believe data-integrity or synchronization issues
may have occurred between Oracle Cloud Applications and your LDAP directory server. For
example, you may notice differences between roles on the Security Console and roles on the
Create Role Mapping page.
• Retrieve Latest LDAP Changes process has been in fusion since the beginning. It copies users
and roles information from identity store and policy store to fusion application's person
tables, which will be used by fusion application functions.
Import User and Role Application Security Data process:
• You must run the Import User and Role Application Security Data process to set up and
maintain the Security Console. During implementation, you perform the Import Users and
Roles into Application Security task to run this process. It copies users, roles, privileges, and
data security policies from the LDAP directory, policy store, and Applications Core Grants
schema to Oracle Fusion Applications Security tables. Having this information in the Oracle
Fusion Applications Security tables makes the assisted search feature of the Security Console
fast and reliable.
• Import User and Role Application Security Data process was introduced in fusion release 9. It
copies users and roles information from identity store and policy store to ASE tables in fusion
application database. Security console and fusion application's audit reports use the ASE
tables.

• From release 9 to 11, you need to run Import User and Role Application Security Data Process
first to populate data into ASE tables as the Security console retrieved users or roles
information from fusion database's ASE tables.
• From Release 12 onwards, Security console retrieves users or roles information directly from
identity store and policy store. However it still uses information in ASE tables for some search
functions.
Lightweight Directory Application Protocol(LDAP): A standard, extensible directory access protocol. It is

a common language that LDAP clients and servers use to communicate.
LDAP was conceived as an Internet-ready, lightweight implementation of the International

Standardization Organization (ISO) X.500 standard for directory services. It requires a minimal amount
of networking software on the client side, which makes it particularly attractive for Internet-based, thin
client applications.
The LDAP standard simplifies management of directory information in three ways:
• It provides all users and applications in the enterprise with a single, well-defined, standard
interface to a single, extensible directory service. This makes it easier to rapidly develop and
deploy directory-enabled applications.
• It reduces the need to enter and coordinate redundant information in multiple services
scattered across the enterprise.
• Its well-defined protocol and array of programmatic interfaces make it more practical to
deploy Internet-ready applications that leverage the directory.

Automatic Data Provisioning
• Automatically assign data security

contexts to users.
• Occurs at the same time roles are
automatically provisioned to users.
• Automatic assignments are based on
rules similar to role mappings.
• Users acquire a data assignment
automatically when at least one of
their work assignments satisfies the
conditions required.
Oracle Financials Cloud supports:
• Automatic provisioning of roles to users.
• Automatically assign data security contexts to users at the same time roles are automatically
provisioned to users.
• Automatic assignments are based on rules similar to role mappings.
• Automatic data provisioning occurs if:
- At least one of the user’s assignments matches all data-mapping conditions on a

Data Provisioning Rule
- At least one role is automatically provisioned to the user using Role Provisioning
Rules
The matched Data Provisioning Rule includes data assignments for a role that is automatically
provisioned to the user.
• The process of automatic data provisioning and deprovisioning is very similar to automatic
role provisioning and deprovisioning.
• For example: If a worker is hired into the Finance Department of the London office, the
worker acquires the relevant data assignments automatically if:

- An appropriate role provisioning rule exists for Finance Department and/or London
office
- At least one of the affected roles in the role provisioning rule is also automatically
provisioned to the user.
Provisioning occurs when you create or update worker assignments. All changes to work assignments
cause review and update of a worker's automatically provisioned roles as well as data assignments.
Users lose automatically provisioned data assignments when they no longer satisfy the data
provisioning conditions.
For example: If a worker is relocated from the London office to another office.
• Data assignments that were automatically provisioned for workers working at the London
office are lost automatically.
• You can also manually deprovision automatically provisioned data assignments at any time.
When you terminate a work relationship, the user automatically loses all automatically provisioned
data assignments, similar to how the user would automatically lose all automatically provisioned roles.
To enable Automatic Data Provisioning, Navigate to: Others > Setup and Maintenance > Setup:
Financials > Change Feature Opt in link > Financials: Edit icon under Features > Enable Data Security
Auto-Provisioning for ERP > Done.
Once a data provisioning rule is defined users will acquire data assignments automatically when:
• At least one of their work assignments satisfies the conditions in the data provisioning rule.
• The corresponding roles in the applicable data assignments are also automatically
provisioned.
Note
• Automatic Data Provisioning requires the use of Automatic Role Provisioning.
• Data security assignments would only be automatically provisioned to users for roles that are
automatically provisioned to users.

Demonstration 4-1 Overview: Defining a Job Role
This demonstration covers defining a job role.

Practice 4-2 Overview: Adding a Job Role to Your
User
This practice covers adding a job role to your user.

Upgrade-Safe Management of Factory Shipped Roles
• You can identify a predefined (factory shipped) Oracle role when viewing the role.
• Predefined Oracle roles are locked and you cannot customize the Oracle delivered
functional and data security policies associated with these roles.
Navigate to: Tools > Security Console > Search for IT Security Manager role.
Predefined Oracle roles are displayed in a different color in the graph visualizer. In the Security
Console, you can identify predefined roles by the ORA_ prefix in the Role Code field.
• Predefined roles can not be changed to add or remove duties.
• Privileges and resources are protected. You cannot create or modify these components.
• Locking down these security artifacts enables safe upgrades to predefined roles, since the
possibility of conflict with customer introduced changes to these roles is now eliminated.
Best solution to update a role or other components, create copies and update the copies instead.

Role Visualization
• View certain components of a role in the graphic visual.

• View the privileges, aggregate privileges, or roles assigned to a role.
• View the graph in full screen mode and pan over a specific region in the graph.
Navigate to: Tools > Security Console > Roles tab > Search for Roles > click Show Graph button.
Arrows connect the nodes to define relationships among them. You can trace paths from any item in a
role hierarchy either toward users who are granted access or toward the privileges that roles can grant.
For complex roles, these features enable you to reduce the amount of information visualized and to
focus on the area within the role hierarchy that requires your attention.
In a visualization, nodes form circular or arc patterns.
• The nodes in each circle relate directly to a node at the center of the circle.
• That focal node represents the item you select to generate a visualization, or one you expand
in the visualization.
• For example, a job role might consist of several duty roles. If you were to select the job role as
the focus of a visualization and if you set the Security Console to display paths leading toward
privileges, an initial image shows nodes representing the duty roles encircling a node
representing the job role.
You can manipulate the image by:
Expanding or Collapsing Nodes:
• You can expand nodes or collapse them. To expand a node is to reveal roles, privileges, or
users to which it connects. To collapse a node is to hide those items.

• In the earlier example, you might expand one of the duty-role nodes. It would then occupy
the center of its own circle of nodes. Each would represent a subsidiary duty role or a privilege
belonging to the duty role you expanded.
• To expand or collapse nodes:
- Make a selection in the Expand Toward option to determine whether nodes expand
toward privileges or toward users.
- Select a node and right-click.
- Select one of these options:
• Expand reveals nodes to which the selected node connects directly, and Collapse hides those
nodes.
• Expand All reveals all generations of connecting nodes, and Collapse All hides those nodes.
Note: These options appear only when appropriate. For example, a Collapse option appears only when
the selected node is already expanded.

Role Visualization
• Enlarging or Reducing the Image.

• Enhancing Your View.
Enlarging or Reducing the Image
• If the image is large enough, each node displays the name of the item it represents.
• If the image is smaller, symbols replace the names: U signifies user, R signifies role, P signifies
privilege, and A signifies aggregate privilege.
• If the image is smaller still, the nodes are unlabeled.
• Use tools located at the upper right of a visualization:
- Plus: Zoom in (enlarge the image). You can also use the mouse wheel to zoom in.
- Minus: Zoom out (reduce the image). You can also use the mouse wheel to zoom
out.
- Circle: Click to activate a magnifying glass. When this feature is active, hover over
nodes to enlarge them temporarily.
- Use the mouse wheel to zoom in or out of the area beneath the magnifying glass.
- Click the circle button again to deactivate the magnifying glass.
- Square: Click to center the image and size it so that it is as large as it can be and still
fit entirely in its display window. Nodes that you have expanded remain expanded.

Enhancing Your View
• Use these techniques to enhance your view of a visualization, or of nodes within it:
- If nodes are labeled with symbols or are unlabeled, hover over any node to display
the name of the user, role, or privilege it represents.
- Click the background of the visualization, then drag the entire image in any
direction.

Search in Role Hierarchy Visualization
• You can search and quickly locate security nodes in the role hierarchy visualization.
• You can search for privileges, roles, or users in the visualization.
Navigate to: Tools > Security Console > search for your role > click Show Graph button.
On the Security Console, search for and select the user.
• A visualization appears showing the user and any roles that the user inherits directly.
• User and role names appear on hover.
To expand an inherited role:
• Select the role and right-click.
• Select Expand.

Tabular Role Hierarchy View
• View role hierarchies in a tabular view.

• Switch between the graphic visualizer view and the tabular view.
• Analyze using a tabular view of direct and indirect assigned privileges for a role.
• Export the data to Excel.
Navigate to: Tools > Security Console > Roles tab > Search for role > click Export to Excel button.

User Account Management
• You can create and manage implementation user accounts within Oracle Cloud
Applications Security.
• You can assign roles to these user accounts.
Navigate to: Tools > Security Console > Users tab.
You can also search, retrieve, and manage user accounts automatically created for employees,
contingent workers, supplier contacts, or partner contacts.
The following function security privileges are required for this feature.
• Create User Account
• Delete User Account
• Edit User Account
• View User Account
Job Role Name required is: IT Security Manager

Administrator Password Management
As an administrator, your can:

• Manage passwords of other users using the Security Console.
• Auto-generate or manually enter a password for a user account.
• Define password lifecycle and complexity policies.
Navigate to: Tools > Security Console > Users tab > search for user > select Action drop box > Reset
Password.
The password will be automatically validated against the defined password complexity rules and
expiration policies.

User Account Locking
• As an administrator, you can lock user accounts.

• If you lock a user account, you will be temporarily preventing the user from logging in
with that user account.
• You can unlock a locked user account.
Navigate to: Tools > Security Console > Users tab > search for user > select user name > select Action
drop box> select Lock Account.
You can temporarily inactivate a user account by locking that user account in Oracle Cloud
Applications Security. You can unlock a locked user account.

User Password Management: Self-Service
• You can manage your own user account password using the Security Console.
• The password will be automatically validated against the defined password lifecycle
and complexity policies.
Navigate to: Drop down arrow next to your user name > Set Preferences > Password > Enter your New
Password and Confirm New Password > Save and Close.

User Password Changes Audit Report
• You can generate a report that lists password changes made by users.
• The report can be generated for changes made by specific users or for all changes
made during a specific period.
Navigate to: Tools > Scheduled Processes > Run User Password Changes Audit Report.
The following function security privilege is required for this feature:
• Privilege Name: Run User Password Changes Audit Report
• Job Role Name: IT Security Manager

Users Categories
• Categorizes and segregate users based on the various functional and operational
requirements.
• Provides you with an option to group a set of users such that the specified settings
apply to everyone in that group. Typical scenarios in which you may want to group
users are:
– Users have different preferences in receiving automated notifications from the
Security Console.
– An external application for a group of users was built using the REST APIs.
• Specify Next URL: The user group is redirected to the external application when using
the Security Console to reset passwords or create new users.
• Enable notification: Enabled by default.
- Can disable them if required.
- Enable or disable notifications separately for each user category.
Navigate to Tools > Security Console > User Categories tab

User Categories: For example, employees of your organization using the organization's single sign-on
don't require notifications from the Security Console about creating new users, password expiry, or
password reset. However, the suppliers of your organization who aren't using the organization's single
sign-on, must receive such notifications from the Security Console.
Note: You can assign a user to only one category.
• Specify Next Url: For example, a user places a password reset request and receives an email
for resetting the password. After the new password is authenticated, the user can be directed
to a website or application. If nothing is specified, the user is directed to Oracle Applications
Cloud Sign In page. You can specify only one URL per user category.
• Notifications: Sent for a set of predefined events. To trigger a notification, you must create a
notification template and map it to the required event. Depending on the requirement, you
can add or delete a template that is mapped to a particular event.

- Cannot edit or delete predefined notification templates that begin with the prefix
ORA. You can only enable or disable them. However, you can update or delete the
user-defined templates.
- User Category feature supports both SCIM protocol and HCM Data Loader for
performing any bulk updates.

Add Users to User Category
You can add users to a user category in three different ways:

• Create a user category and add users to it.
• Add users to an existing user category.
• Specify the user category for an existing user.
Navigate to: Tools > Security Console > User Categories tab
Create and delete a user category only using the Security Console.
• Use them in SCIM REST APIs and data loaders.
• Can not rename a user category.
• Can delete user categories.
- Ensure that no user is associated with that user category or you can not proceed
with the delete task.
- Click the X icon in the row to delete the user category on the User Categories page.

User Name Generation Rules
• You can define the user name generation rules used to auto-generate the user name
in Oracle Cloud Applications Security.
• User name generation rules can be based on the user’s first and last names, e-mail or
person number.
• You can choose to use a system generated user name if the rule fails to generate a
user name.
Navigate to: Tools > Security Console > User Categories link.

Password Policies
• You can define policies for password management.

• These policies can define the duration for various password lifecycle events like
password expiration and password warning generation.
• You can set the complexity of generated passwords by choosing from a pre-defined
list of rules.
Navigate to: Tools > Security Console > User Categories link.
The following function security privilege is required:
• Privilege Name: Run Password Expiry Job
• Job Role Name: IT Security Manager
To set the password policy, you perform the Manage Applications Security Preferences task, which
opens the Password Policy link of the Security Console User Categories tab. In the Password Policy
section, you select appropriate values. You can also change the enterprise policy at any time on the
Security Console. Select Navigator > Tools > Security Console.
• Days Before Password Expiration: Specifies the number of days for which a password remains
valid. After this period, users must reset their passwords. By default, users whose passwords
expire must follow the Forgot Password process. Default: 90 days.
• Days Before Password Expiry Warning: Specifies when a user is notified that a password is
about to expire. By default, users are prompted to sign in and change their passwords. This
value must be equal to or less than the value of the Days Before Password Expiration option.
Default: 80 days.
• Hours Before Password Reset Token Expiration: When users request a password reset, the
user is sent a password-reset link. This option specifies how long a reset-password link
remains active. If the link expires before the password is reset, then reset must be requested
again. You can enter any value between 1 and 9999. Default: 4 hours.

• Password Complexity: Specifies whether passwords must be simple, complex, or very
complex. Password validation rules identify passwords that fail the selected complexity test.
Default: Simple.
• Disallow last password: Select to ensure that the new password is different from the last
password. Default: No.
• Administrator can manually reset password: Passwords can be either generated automatically
or reset manually by the IT Security Manager or IT Auditor. Select this option to allow user
passwords to be reset manually. All passwords, whether reset manually or generated
automatically, must satisfy the current complexity rule. Default: Yes.
Note: Users are notified when passwords are about to expire, have already expired, or have been reset
only if appropriate notification templates are enabled. The predefined notification templates for these
events are:
• Password Expiry Warning Template.
• Password Expiration Template.
• Password Reset Template.

Notification Templates
• You can define or edit custom notification templates for user account life cycle
events.
• You can use predefined notification templates.
Navigate to: Tools > Security Console > User Categories tab > find or create user or use Default >
Notifications
By default, users are notified automatically of changes to their user accounts and passwords. These
notifications are based on notification templates. Many templates are predefined, and you can create
custom templates. During implementation, you identify the notifications that you plan to use and
disable any that are not needed. These templates are used to generate notifications for events like
user account created, user password reset, and user password expiry warning.
Each template is associated with a predefined event. For example, the Password Reset Template is
associated with the password-reset event. You can see the notification templates and their associated
events on the Notifications subtab of the Security Console User Category tab.
• Password Expiry Warning Template: Warns the user that a password is expiring soon and
provides instructions for resetting the password.
• Password Expiration Template: Notifies the user that a password has expired and provides
instructions for resetting the password.
• Forgot User Name Template: Sends the user name to a user who requested the reminder.
• Password Generated Template: Notifies the user that a password has been generated
automatically and provides instructions for resetting the password.
• Password Reset Template: Sends a reset-password link to a user who performed the Reset
Password action on the My Account page.

• Password Reset Confirmation Template: Notifies the user when a password has been reset.
• New Account Template: Notifies a user when a user account is created and provides a reset-
password link.
• New Account Manager Template: Notifies the user's manager when a user account is created.
Note: Do not edit the predefined templates, as your changes are lost on upgrade. Create custom
templates and disable the predefined versions. Each predefined event can be associated with only one
enabled notification template at a time.

Security Resources
To review the roles and other components that make up the security reference
implementation for your application, you can:
• Access the security reference manuals (SRM).
– Common
– Service-specific
• Access the tasks available for managing roles, templates, and security policies.
Oracle ERP Cloud Oracle Financials Cloud

Securing ERP Security Reference for
Financials
Oracle Applications Cloud

Security Reference for Common Features
Oracle Financial Cloud Security is applicable to the needs of midsized, horizontal enterprises generally
between 250 and 10,000 employees. It can be changed or scaled to accommodate expansion into
vertical industries such as health care, insurance, automobiles, or food manufacturing.
For more resources on the Oracle Help Center, see:
• Oracle Financial Cloud Security Guides:

https://docs.oracle.com/en/cloud/saas/financials/20b/books.html
• Oracle Cloud Middleware Security Guides: https://docs.oracle.com/en/middleware/fusion-

middleware/security-toolkit/12.2.1.4/books.html

Summary
In this lesson, you should have:

• Understand the Oracle Security Model.
• Discuss using the Security Console.
• Examine the changes to the common security features.
• Review security resource materials.

5
Enterprise Structures and Ledgers Overview

Objectives

• Describe enterprise structures
• Describe reporting structure setups
• Describe ledgers
• List the Rapid Implementation tasks
Note: This lesson is intended to either introduce or refresh the concepts of setups for enterprise
structures, reporting structures, and ledgers. For more detailed knowledge, you can take the Oracle
Financials Cloud: Enterprise Structures and General Ledger course.

Common Applications Configuration for Accounting
Hub Cloud
• Enterprise Structures
• Ledgers
Common Applications Configurations include the following setups:
• Enterprise Structures
- Legal entities, legal jurisdictions, and legal authorities
- Financial Reporting Structures: Chart of accounts, Calendar, and Currencies
- Geographies
• Ledgers: Primary, Secondary and Reporting

Legal Entities Defined
• A legal entity is a registered company or other entity recognized in law.

• Each legal entity has a separate legal identifier and therefore, conducts different
aspects of your business.
Legal Entities:
• Own the assets of an enterprise
• Record sales and pay taxes on sales
• Make purchases and incur expenses
• Perform Intercompany trading
An Enterprise may have more than one legal entity:
• To comply with corporate taxation and other compliance laws within local jurisdictions
• To prepare for acquisitions or disposals of parts of an enterprise
• To isolate one area of business from risks in another area. For example, your enterprise
develops and leases properties. You can create separate legal entities for development and
leasing. This would minimize risk across lines of businesses.
Legal entities are required by Oracle Accounting Hub Cloud if a company is implementing intercompany
balancing.

Legal Entity, Ledgers, and Balancing Segment Values
• Legal entities can be associated with ledgers.

• When several legal entities share a ledger, use a balancing segment value for each
legal entity.
The different ways in which legal entities can be associated with ledgers are as follows:
• One Legal Entity – One Ledger: This configuration does not require that a balancing
segment be assigned to the legal entity.
• Multiple Legal Entities – One Ledger: This is possible only if all the legal entities share the
same chart of accounts, calendar, currency, and accounting convention. You should assign
each legal entity its own balancing segment value.
Assigning a Balancing Segment Value
• Facilitates producing a trial balance and balance sheet by legal entity
• Secures the Ledger by balancing segment values to ensure that only journals with those
balancing segment values are posted

Legal Entities and Intercompany Transactions
Transactions that cross legal entities are accounted for as intercompany transactions.
• General Ledger supports three balancing segments.
• Journals are balanced automatically at posting.
Intercompany transactions can be enabled for:
• Three balancing segments: For example, you might set the company segment in your chart
of accounts as the primary balancing segment, the cost center segment as the second
balancing segment, and a line of business as the third. The total debits and credits must
balance per balancing segment, per journal entry.
• Automatic balancing at posting: Balancing rules are set up to ensure that journal lines are
added to the journal automatically at posting to balance the total debits and credits.

Financial Reporting Structures Overview
The graphic in the slide illustrates the four C’s of financial reporting structure setups.
Another important implementation task is to define financial reporting structures. These structures affect
the outcome of all financial reports. The financial reporting structures include the four C’s:
• Chart of Accounts
• Calendar
• Currency
• Accounting Method or Convention
The Accounting Method is covered in detail in the lesson titled “Accounting Transformation
Configuration.”

Chart of Accounts Components
The graphic in the slide depicts the chart of accounts components.
All these components in a chart of accounts in Oracle Cloud Applications can be created by using
Rapid Implementation spreadsheets:
• Chart of Accounts Structure: Defines the key attributes for your chart of accounts, such as
the number of segments, segment sequences, segment names, segment prompts, default
values sets, and segment labels (such as Natural Account and Primary Balancing). A structure
can have up to 30 segments with each segment 25 characters long and a maximum total
length of 240 characters. However, a best practice is to have 5 to 9 segments in your chart of
accounts.
• Chart of Accounts Structure Instance: Inherits all the attributes of the chart of accounts
structure, by default. This means that all instances of the same structure share a common
shape and have the same segments in the same order. However, at the chart of accounts
instance level, you can override the default value set assignments for your segments and
assign a unique account hierarchy that determines the parent and child relationships
between the value set values.
• Value Sets: Are attached to each segment to provide formatting such as size and alpha-
numeric values, and the validation of the set of values used with that segment. You can think
of a value set as a container for your values.
• Segments: Combines with other segments to create the account combination. Each segment
has a value set attached to it to provide formatting and validation of the set of values used
with that segment.

• Segment Labels: Identifies certain segments in your chart of accounts and assigns special
functionality to those segments
• Deploy: Generates or refreshes the components that activate the chart of accounts in a user
interface. To use a chart of accounts, it must have been deployed.
• Values: Is the set of valid values that you assign to a flexfield segment
• Security Rules: Are applied at the value set level to secure data. If a value set is secured, all
chart of accounts segments that refer to that value set are affected by the value set’s defined
security rules.
• Cross-Validation Rules: Determine which account combinations are created dynamically as

your users enter transactions or journal entries
• Account Combinations: Contain a completed code of segment values that uniquely identifies
an account in the chart of accounts.

Assigning Segment Labels
• Segment labels qualify certain

segments with needed roles.
• For example, assign a segment label of
Primary Balancing to a Company
segment to indicate that journals must
balance by Company.
The graphic in the slide shows the segment labels.
The segment labels qualify certain segments in your chart of accounts with needed roles in General
Ledger. The labels are:
• Balancing: One segment is required to be labeled as the Primary Balancing segment. The
Second and Third balancing segments are optional.
• Natural Account: This label is also required. It determines the account type (asset, liability,
expense, revenue, or equity) and other information that is specific to the segment value. It
facilitates processes in the General Ledger application, such as retained earnings posting, and
therefore, is required.
• Cost Center: This label facilitates grouping of expenses by departments. It is not required for
General Ledger but is required if you are using Assets and Expenses.
• Intercompany: This label is used to balance intercompany journals. It is also not required.
• Local Use: This label is required for some country-specific localizations.
• Management: This is a future label that creates another layer of security on a ledger.

Accounting Calendar Overview
An accounting calendar contains years and periods. You must also include:
• Start Date
• Period Frequency
• Period Name Format
• Period Type
When defining an accounting calendar, you must include the following:
• Start Date: It is a best practice to specify a calendar start date that is a full year before the
actual start date of your ledger. After you open your first period, you cannot open a prior
period from the start date.
• Period Frequency: The choices are Monthly, Weekly, Quarterly, Yearly, 4-4-5, 4-5-4, and so
on. You can also define one or more adjusting periods.
• Period Name Format: Choose from a flexible format by using alpha or numeric values and
various separators, for example, Dec-16 or 12-16.
• Period Type: Calendar or Fiscal

Manage Currencies Overview
• Oracle Cloud Applications provides full cross-currency functionality to meet the

needs of global companies.
• Currency functionality is designed in accordance with:
– United States Statement of Financial Accounting Standards 52 (SFAS #52)
– International Accounting Standards 21 (IAS 21) requirements
Use the predefined International Standards Organization (ISO) currencies or create new ones.
• Enable currencies to use them for your financial transactions and processes.
• Enable the STAT currency, which is predefined, to record statistical data, such as employee
head count, labor hours, or units sold. Statistical data is used in allocation journal calculations
to spread related costs over different cost centers. For example, in a manufacturing
operation, use labor hours to allocate the costs of a product to the different cost centers that
performed the work.
The Define Currencies task list consists of the following tasks:
• Manage Currencies: Enable and create currencies to use when recording cross-currency
transactions and running accounting processes.
• Manage Conversion Rate Types: Create and manage conversion rate types to categorize the
relationships between your currencies and daily rates.
• Manage Daily Rates: Enter rates by using a spreadsheet, and then manage the daily,
periodic, and historical rates that are used to record transactions or in processes involving
multiple currencies.

Ledgers Overview
The graphic in the slide depicts the three types of ledgers.
Three types of ledgers are defined by using the four reporting structures: Chart of accounts, calendar,
currency, and Accounting Method. The number of ledgers is unlimited and determined by your
business structure and reporting requirements.
• Primary Ledger: Main record-keeping ledger and a required component in your

configuration. Every accounting configuration is uniquely identified by its primary ledger. The
primary ledger is closely associated with the subledger transactions, and provides context
and accounting for them.
• Secondary Ledger: Optional ledger that is linked to a primary ledger for the purpose of
tracking alternative accounting. A secondary ledger can differ from its primary ledger in its
chart of accounts, accounting calendar, currency, Accounting Method, or processing options.
If a secondary ledger has a different chart of accounts than its primary, a chart of accounts
mapping is required. A secondary ledger is defined with one of the following four conversion
levels:
- Balance Level: The Transfer Balances to Secondary Ledger process transfers only
balances to the secondary ledger.
- Journal Level: The General Ledger Posting process transfers journal entries to the
secondary ledger.
- Subledger Level: Oracle Subledger Accounting creates subledger journals to both

the primary and secondary ledgers. The Posting process transfers the remaining
journal entries to the secondary ledger.

- Adjustment Only: The Adjustments Only secondary ledger is an incomplete
accounting representation that holds only manual or automatic adjustment journal
entries from General Ledger or Oracle Subledger Accounting. This conversion level
requires that the secondary ledgers share the same chart of accounts, accounting
calendar, and currency with its primary ledger. A complete accounting
representation is achieved by creating a report that includes both the primary and
secondary ledger data together.
• Reporting Currency: Optional, additional currency representation of a primary and/or

secondary ledger. A reporting currency differs from its source ledger in its currency and some
processing options, but shares the same chart of accounts, accounting calendar, and
Accounting Method with its related ledger. A reporting ledger is defined with one of the
following three conversion levels:
- Balance level: Only General Ledger balances are maintained in the reporting
currency through the Translation process.
- Journal level: The General Ledger Posting process transfers and converts journal
entries to the reporting currency.
- Subledger level: Subledger Accounting creates subledger journals to the reporting

currency. General Ledger converts the remaining journal entries to the reporting
currency during the Posting process.

Ledger Structure
The diagram in the slide shows the three types of ledgers and their relationships to one another. The
primary ledger can have one or more legal entities assigned to it and each legal entity can have assigned
balancing segment values. If legal entities and balancing segment values are assigned to a primary
ledger, the associated secondary ledger inherits them.

Rapid Implementation Process
The Create Chart of Accounts, Ledger, Legal Entities, and Business Units rapid
implementation process consists of the following steps:
1. Enter data into the spreadsheets.
2. Upload the XML files generated from the spreadsheets.
3. Run the deployment process to finalize the chart of accounts configuration.
4. Upload the XML files generated from the spreadsheets for the rest of the
configuration.
The Rapid Implementation process configures your enterprise structures quickly:
• Using sheets in a workbook to upload lists of companies (legal entities), ledgers, business units,
chart of account values, and other similar data
• Enabling tracking of your financial objectives and meeting of your reporting requirements
• Creating multiple hierarchies for any chart of accounts segment, either during initial setup or at
a later point. Use the Hierarchies Only sheet in the Rapid Implementation spreadsheet to create
new hierarchies or add new versions to existing hierarchies after your enterprise structures
have been created.

Practices 5-1 – 5-3 Overview
• Practice 5-1: Entering Data in Rapid Implementation Spreadsheet

• Practice 5-2: Uploading the Chart of Accounts File
• Practice 5-3: Uploading the Financials Common Entities File

Deploying the Accounting Flexfield
• Deployment generates the chart of accounts business objects to make them available
in the user interface.
• When you deploy the Accounting flexfield, all charts of accounts in the system are
deployed.
• You must deploy again after any new configurations or changes to a chart of
accounts.
Deployment of the Accounting flexfield generates or refreshes the Application Development

Framework (ADF) business component objects that render the Accounting flexfield in a user interface.
The deployment process adds the user-defined attributes to the Web Services Description Language
(WSDL) schemas that are exposed by Oracle ADF services and that are used by Service-Oriented
Architecture (SOA) composites. Flexfields are deployed for the first time during the application
provisioning process.
Deployment deploys all charts of accounts in the system during each run. To verify the Deployment
Status, navigate to the Manage Chart of Accounts Structures page from the Setup and Maintenance
work area. The status can be:
• Edited: The flexfield definition has not been deployed or changes have been made to the
structure, structure instances, or value sets.
• Patched: The flexfield definition has been modified through a patch, but the flexfield has not
yet been deployed, so the patched definition is not reflected.
• Deployed to Sandbox: The flexfield is deployed and available in a flexfield-enabled sandbox.
• Deployed: The flexfield definition is deployed and available to end users.
• Error: The deployment attempt failed.
After you configure or change a flexfield, you must deploy it to make the latest definition available to
end users.

Specifying Ledger Options
The graphic in the slide illustrates the various ledger options that are available.
The rapid implementation upload from the spreadsheet populates many of the ledger options. After
uploading, the next step is to verify and specify ledger options for the primary ledger. These options
include:
• General Information: This includes the ledger name, description, currency, and chart of
accounts.
• Accounting Calendar: Select a first open period and the number of future enterable periods.
• Subledger Accounting: This includes the Accounting Method and the journal language.
• Period Close: You must provide account combinations for Retained Earnings and Cumulative
Translation Adjustments. Plus, you must choose whether to use the features of Net Closing
Balance Journal to Create Income Statement and Balance Sheet Closing. Finally, you can
provide the Default Period End and Average Rate types.
• Journal Processing:
- Balancing: Choose to Enable Suspense and if so, provide Default Expense Account,
Rounding Account, Entered Currency Balancing Account, and if so, the Balancing
Threshold Percent.
- Entry: Choose to Enable journal approval; Notify when prior period journal; Allow
mixed and statistical journals; and Validate reference date.

- Import: Choose to Separate journals by accounting date during journal import.
- Intercompany: Specify whether to enable Intercompany Balancing.
- Reversal: Specify Journal Reversal Criteria Set, whether to Run AutoReverse after
the open period, and whether to Synchronize Reversals between the primary and
secondary ledgers.
• Sequencing: Select to sequence by ledger, legal entity, or not at all; to Enforce Document
Sequencing for Payables, Receivables, or not at all; and to Enforce chronological order on
document dates.

Review and Submit Accounting Configuration
Navigate to: Others > Setup and Maintenance > Accounting Hub Cloud Offering >
Setup > General Ledger > Review and Submit Accounting Configuration.
• Select your ledgers and click the Submit button.
• A green check mark in the Status column shows that your configuration is completed
and confirmed.
Note: This process runs by primary ledger and processes related secondary ledgers,
reporting currencies, and legal entities, and creates the Balances cube*.
*For more information about the Balances cube, see the next section.

Practices 5-4 – 5-6 Overview
• Practice 5-4: Completing the Ledger Configurations

• Practice 5-5: Managing Data Access for Your User
• Practice 5-6: Opening Your General Ledger Periods

Summary

• Describe enterprise structures
• Describe reporting structure setups
• Describe ledgers
• List the Rapid Implementation tasks

6
Accounting Transformation Configuration

Objectives

• Explain the accounting transformation process.
• List the key features of accounting transformation.
• Describe the implementation process of accounting transformation.
• Manage the accounting transformation Accounting Methods.
• Create and process accounting entries.
• List the optional manual features of subledger accounting.
• Explain the advanced features of subledger accounting.

Accounting Transformation Overview
The graphic in the slide depicts the Accounting Hub Cloud’s features and integrations.
Accounting transformation refers to the process of converting transactions or activities from

source systems into journal entries.
Source systems are typically industry-specific applications that are either purchased from
third parties or built internally within the customer organization. Examples of such source
systems include: core banking applications, insurance policy administration applications,
billing applications, loan processing applications, and point of sales applications.
You can also register legacy systems or transaction systems with limited accounting and use
Accounting Hub Cloud for account derivation and as a unified accounting engine repository.

Planning and Modeling Subledgers
Accounting Hub Cloud offers the flexibility to plan and model subledger applications
for managing transaction data file uploads. For example:
The graphic in the slide illustrates two types of subledger modeling.
The first is a third-party loans application that consists of multiple product lines. It can be
modeled with a distinct number of subledgers that is equal to the number of product lines.
The second is a third-party billing application with a global business operation in the US and
UK, and can be registered as one subledger.
Source systems are modeled as separate subledger applications when:
• The transaction sources are mapped to different source systems
• A need exists to have separate control over accounting and other business operation
decisions for a specific source system

Accounting Transformation Implementation Steps
The accounting transformations implementation process includes the following:
• Analyzing your current non-Oracle systems to determine which source systems have
transactions or activities that need to be accounted and reported via the Accounting
Hub Cloud
• Building the subledger application by registering the source system and its
transactional events and activities, which have financial impact in the Accounting Hub
Cloud, to make them eligible for accounting
• Implementing and testing Accounting Methods by assigning them to ledgers to create

a complete definition of the accounting convention for the transactions and activities
for each source system

Step 1: Analyze and Identify Transaction Life Cycle in
the Source System
Analyze source system transactions or activities to determine what transaction types
to capture.
Examples of transaction types from retail loans source systems include:
• Loan origination
• Loan interest approval
• Loan interest accrual reversal
• Loan scheduled payment
• Loan late payment
• Loan charge off
A source system that generates transactions as part of a business process has potential
financial impact that requires creation of accounting entries. As a key step to creating
accounting entries, these transactions must be distinctly identified as different transaction
types.
A transaction type and its associated transaction data typically relate to a single document or
transaction. However, the nature of source systems may prevent them from extracting this
discrete information and sending it to Accounting Hub Cloud for processing. In some cases,
summarized transaction type information, such as overall customer activity for the day, is sent
for accounting transformation. Transaction types become Accounting Events in Accounting
Hub Cloud.
Complete the following analysis to identify accounting events:

• Determine the subledger requirements: for example, how many subledgers are to be
created?
- Using the same subledger enables you to share subledger accounting rules,
and lets you report across all data easily.
- Using separate subledgers provides more security across applications and
less data in each process run, thus providing better performance. A specific
benefit is when you run two Create Accounting processes at the same time
for different applications, they are much less likely to contend for database
resources.

• Determine what source data is required to create subledger journal entries from
transactions.
• Analyze the transaction life cycles that create an accounting impact.
• Determine how often to upload subledger transaction data into Accounting Hub
Cloud. This may depend on the immediacy and volumes of accounting requirements
in your company.

Step 2: Analyze Accounting, Reporting, Audit, and
Reconciliation Requirements for Transaction Types
Such an analysis should, at a minimum, answer the following questions:
• Under what conditions are each of the lines in a subledger journal entry created?
• What is the line type, debit or credit, of each subledger journal entry line?
• What description is used for the subledger journal entry?
• How are the accounts derived for the entry?
• What information may be useful for reconciling the subledger journal entry to the
source system?
Some source systems may already produce accounting entries, whereas others may produce
raw transactions with no associated accounting.
As part of the analysis, determine how much transformation is required to produce subledger
journal entries.
Next, examine the components of the journal entry rule set to determine what rules are
required to produce the required subledger journal entries.
This exercise helps to determine which subledger journal entry rule set components to define
for the source systems data to be transformed into subledger journal entries.
The journal entry rule set components include:
• Description rules
• Account rules
• Journal line rules
• Supporting references

Loan Source System Analysis Example
Type Account Description Currency Debit Credit
Loan Origination 101.10.15300.000.000.000 Mr. John Doe USD 100,000.00 0.00
Cash 101.10.11100.000.000.000 Mr. John Doe USD 0.00 100,000.00
When setting up a new subledger application, you must know about the transactions in your
source system and determine which attributes you want in the accounted journal entries.
These attributes can come from the transaction information or transaction lines. For
example, the graphic in the slide displays source system data and a journal entry for a loans
system.
Plan and model the subledger:
• Visualize the journal entries that are expected to be accounted.
• Analyze the accounting and reporting transaction attributes in the source system.
• Preview how accounting rules are configured in Accounting Hub Cloud and mapped
into your accounting and reporting requirements.
• Model the source system to meet your business requirement in Accounting Hub
Cloud.
In the table in the slide, the example identifies the sources for the journal lines and accounts
in a source system:
• Each debit and credit journal line is identified and defined for each transaction type.
• When a loan is originated, the loan receivables account is debited and the cash
account is credited.

• The cost center segment of the Loan Receivables accounts can have two values,
depending on the loan type value:
- If the loan type is adjustable rate, the cost center is '0000'.
- If the loan type is fixed rate, the cost center is '2120'.
For management reporting and control, what type of information is to be extracted from
journal entries?
For example: Account group used to drill down from General Ledger to subledger journal
entries:
• Total loan receivables amount booked by the loan officer
• Journal entry line description with loan number and transaction date
At the end of this exercise, you have a list of transaction attributes that are required to obtain
the appropriate accounting entries from Accounting Hub Cloud.
Examples of transaction attributes:
• Amounts including entered, accounted, and conversion data
• Dates
• Descriptions
• General Ledger accounts
• Customer information
• Transaction type information
• Product information

Accounting Event Model Overview
The graphic in the slide represents an accounting event model for a Loan application.
Accounting events represent transactions that may have financial significance, for example,
issuing a loan and disposing of an asset. Financial accounting information can be recorded for
these events and accounted by the Create Accounting process. When you define accounting
events, determine from a business perspective which activities or transactions that occur in
your source system may create a financial impact.
• Events with significantly different fiscal or operational implications are classified into
different accounting event types.
• Event types are categorized into accounting event classes.
• Accounting definitions in the Accounting Hub Cloud are based on an event class and
event types.
• An event type must be unique within an application.
Event Class
An event class groups related transaction information and attributes within a source system.
An event class is created by using the registered source system name, for example, the Loans
source system. The Accounting Hub Cloud supports only one event class per application.

Event Types
When registering a source system, you can specify event types as the transaction types of the
source system. For example, the event types Loan Origination and Loan Scheduled Payments
are types of transactions that have differences in their functional and operational implications.

Accounting Attribute Assignments for Accounting
Hub Cloud
The Create Accounting process uses the values of sources assigned to accounting
attributes and accounting rules to create subledger journal entries.
Each accounting attribute is associated with a level when creating subledger journal
entries:
• Header
• Line Accounting Attribute Predefined Source Assignment
Accounting Date Transaction Date
Distribution Type Accounting Event Type Code
Entered Amount Default Amount
Entered Currency Code Default Currency
First Distribution Identifier Line Number
The Create Accounting process uses the sources assigned to accounting attributes to copy
values from transaction data to subledger journal entries. For example, you may map the
invoice entered currency to the subledger journal entry entered currency.
To create a valid journal entry, the following accounting attribute assignments are required.
Accounting Hub Cloud predefines the values:
• Accounting Date:
- Accounting Hub Cloud predefines Transaction Date as Accounting Date.

The Create Accounting process uses it to derive the accounting date of
journal entries.
- The Accrual Reversal Accounting Date Source attribute is relevant to

applications that must perform automatic reversal on accrued journal entries
at a specified date or period. You can assign application and standard date
sources to the Accrual Reversal Accounting Date on the Accounting
Attribute Assignments page. When the Accrual Reversal Accounting Date
Source attribute returns a value, the Create Accounting process generates
an entry that reverses the accrual entry.
- Accounting Hub Cloud does not predefine any source assignment to the
Accrual Reversal Accounting Date Source accounting attribute.

• Entered Currency Code:
- Entered currency accounting attributes are required for all applications. The
Create Accounting process uses them to populate the journal entry line
entered currency and amounts.
- The entered currency accounting attributes must always be assigned to

sources. The sources assigned to the entered currency accounting
attributes must always contain a value.
- Accounting Hub Cloud predefines source assignment to the Entered

Currency Code and Entered Amount accounting attributes at the line level.
Additional sources can be manually assigned to support cross-currency
transactions.
• First Distribution Identifier:
- The distribution identifier information links subledger transaction

distributions to their corresponding journal entry lines.
- The Distribution Type and First Distribution Identifier accounting

attributes are predefined to the Accounting Event Type Code and Line
Number sources.

Step 3: Register Source Systems
The graphic in the slide depicts the quick setup checklist for rapid implementation of
Accounting Hub Cloud.
Oracle Accounting Hub Cloud in the cloud now delivers a rapid implementation approach to
registering source systems.
A simplified source system spreadsheet registration process creates the complete registration
in one step. Create a new subledger application by registering the transaction source system
by using a spreadsheet.
After configuring accounting rules, upload the transaction data in a spreadsheet to create
accounting entries.

Registering a Source System Flow
The graphic in the slide depicts the tasks to register a source system.
After completing the source system transaction flow analysis, you can use a spreadsheet to
register your source systems in Accounting Hub Cloud. Spreadsheet registration accelerates
the time from implementation and testing to production.
Complete the following tasks to register your source system:
• Download the Spreadsheet Template.
• Populate the Spreadsheet Template.
• Validate the Spreadsheet Content.
• Generate the .zip File.
• Upload the .zip File
• Verify the Source System.

Downloading the Spreadsheet Template
Download the spreadsheet template by using the Create Subledger Application Setups
in Spreadsheet task.
Navigate to: Others > Setup and Maintenance > Tasks panel tab > Search > Enter Create
Subledger Application > Search icon > Click on Create Subledger Application Setups in
Spreadsheet > Download Setup Template.

Populating the Spreadsheet Template
Spreadsheet > Download Setup Template > Open with > OK > Instructions worksheet.
The spreadsheet template has three worksheets:
• Source System
• Transaction Information
• Line Information

The Source System Worksheet
Spreadsheet > Download Setup Template > Open with > OK > Source System worksheet.
The Source System worksheet has two sections.
In the Source System Transactions section, enter:
• Name: The name of the source system. This name is used for the registered
subledger application, event class, and journal source in Accounting Hub Cloud. It
has a maximum length of 25 characters. An event class represents the transaction
and is used to group event types.
• Short Name: This is used as the column name in the database.
In the Transaction Types section, enter:
• Name: The name of the transaction types. It has a maximum length of 30

characters. Each transaction type is used as an event type grouped under the event
class, and represents an event in the life cycle of a transaction that has accounting
impact.
• Short Name: This is used as the column name in the database.

The Transaction Information Worksheet
Spreadsheet > Download Setup Template > Open with > OK > Transaction Information
worksheet.
The Transaction Information worksheet lists transaction information as sources that are
used for setting up accounting rules. These are header-level information sources.
The worksheet includes three predefined required sources:

• Transaction Date: Provides the accounting date for booking a journal. You can add
additional source attributes for the transaction date if multiple date options exist
that are used as accounting date.
• Transaction Number: Links the transaction and line information
• Ledger Name: Is the reporting entity for which journal entries are booked in the
General Ledger
To define more sources, enter:

• Name: This name appears in a drop-down list for the accounting rules. Maximum
length is 80 characters.
• Short Name: This is used as the column header in the transaction data template.
This template is used to upload source system transactions.

• Type: This is used to describe the type of values from the source system. The
available values are:
- Text: The length can be less than the alphanumeric source type of 100
CHAR values.
- Number: This must be a valid numeric type.
- Date: This must be a valid date value.
- Long Text: This is a source type of VARCHAR2, where the length can be
greater than the alphanumeric type of 100 CHAR values, but less than
1000 CHAR values.
• Journal Display: Indicates whether this attribute is shown on a report and in

inquiries along with the journal. Acceptable values are Yes and No. In the user
interface, these are known as user transaction identifiers. Up to 10 rows can be
used. User transaction identifiers constitute the user-oriented key of the underlying
subledger transaction. These identifiers are primarily used in accounting events
inquiry and on accounting event reports, to uniquely identify transactions. The
transaction data that identifies the transaction varies by subledger application.
Accounting event reports and inquiries display the transaction identifiers and their
labels as appropriate for the corresponding event class. The user transaction
identifiers can be displayed for an event regardless of its status. This includes the
case when an accounting event has not been processed. The user transaction
identifier values are displayed at the time the accounting event reports and
inquiries are run.
Note: Up to 50 text, 10 number, 5 date, and 5 long text sources can be defined. This includes
the three predefined required sources.

The Line Information Worksheet
Navigate to: Setup and Maintenance > Tasks panel tab > Search > Enter Create Subledger
Application > Search icon > Click on Create Subledger Application Setups in Spreadsheet >
Download Setup Template > Open with > OK > Line Information worksheet.
The Line Information worksheet lists the types of transaction information that can have
more than one value per transaction, for example, an order or invoice line item amount.
The worksheet includes three predefined required sources:
• Transaction Number: Links the transaction header with the line information
• Default Amount: Holds transaction amount values for use in accounting
• Default Currency: Holds entered currency values for use in accounting
Additional sources can be added if multiple and different values need to use the same source
attribute. In that case, you must manually map the related accounting attributes with these
additional sources from the user interface. To do so, enter the following:
• Name: This name appears in a drop-down list for the accounting rules. Maximum
length is 80 characters. Do not add Line Number as a source name because this
name is reserved for an automatically created internal source.
• Short Name: This is used as the column header in the transaction data template.
This template is used to upload source system transactions.

• Type: This is used to describe the type of values from the source system. The
available values are:
- Text: The length can be less than the alphanumeric source type of 100
CHAR characters.
- Number: This must be a valid numeric type.
- Date: This must be a valid date value.
- Long Text: This is a source type of VARCHAR2, where the length can be
greater than the alphanumeric type of 100 CHAR characters, but less than
1000 CHAR characters.
• Chart of Accounts Value: Indicates that the source can be used to derive an
account. Acceptable values are Yes and No. Only text type sources can be used in
segment rules. Examples of sources that are typically used to derive General Ledger
accounts are:
- Account
- Cost Center
- Company

Validating the Spreadsheet Content and Generating
the .zip File
Spreadsheet > Download Setup Template > Open with > OK > Source System worksheet.
To verify the accuracy of the content in the spreadsheet template, use the Validate button on
the Source System worksheet tab.
If an error is generated, you receive an error message:
• A Validation Report worksheet is created.
• Open the Validation Report worksheet to review the error.
• Correct the error and validate the content again.
Generate the .zip file by using the Generate .zip button in the Source System worksheet.
You receive a notification that the .zip file was created and saved in the same local folder as
the downloaded spreadsheet template.

Uploading the .zip File
Spreadsheet > Download Setup Template.
Use the Create Subledger Application Setups in Spreadsheet task to upload the .zip file:
• Use the Upload Setup File button.
• Browse for your .zip file.
• Select Import.
If errors exist during the upload process, you are prompted with an error message. Correct
the error in the spreadsheet in the fields noted in the error message.
The file Upload creates subledger application setups in a single step, including journal
source, journal category, event model, transaction objects, sources and accounting attribute
assignments. If no errors exist:
• The source system is now registered in Accounting Hub Cloud
• One transaction object at the header and line levels is created
Note: If you need to override the uploaded source system information, you can re-upload
the spreadsheet template for the same source system if you have not created any
accounting rules for the uploaded source system.

Verifying That the Source System Was Created
Navigate to: Others > Setup and Maintenance > Fusion Accounting Hub Offering > Accounting
Transformations > Manage Subledger Application.
Navigate to: Others > Setup and Maintenance > Fusion Accounting Hub Offering > Accounting
Transformations > Manage Sources.
The transaction attributes created as part of upload can now be used to configure accounting
rules through the Subledger Accounting user interface as usual.
Verify that the uploaded source system created the new subledger application and the
transaction information. You can update the uploaded objects from the user interface. For
example: Accounting Event Types. You can add new event types.
Sources:
• Assign and update value set and lookup type assignments. Whenever appropriate,
sources can have lookup types or value sets assigned. Assigning a value set or
lookup type enables you to predefine valid values for the source that is used to create
accounting rules.
• You can revise:
- The source names to be more business user-friendly so that they are easily
understood when configuring accounting rules

- The sources that correspond to Accounting flexfield identifiers. Users can
select Other or a named segment from the chart of accounts.
• You can add sources from the user interface. The download of a new transaction data
template includes this newly added source.
Accounting Attribute Assignments: An accounting attribute is a piece of a journal entry.

The mapping of sources to accounting attributes specifies how the Create Accounting
process gets the value for each piece of the journal entry. For example, the Entered Currency
attribute is used to map source values to the entered currency field for subledger journal
entry lines. You can add and update source assignments to accounting attributes. You can
add and make updates to the source assignment to an accounting attribute if you have other
sources available, for example, when you have multiple transaction date sources.

Transaction Objects
Transaction objects hold transaction information that is used when creating journal
entry rules for accounting.
When registering a source system in Accounting Hub Cloud:
• Transaction objects are automatically created based on the transaction information
of the registered source system. One header-level object and one line-level
transaction object are created.
• Then sources are automatically generated based on the transaction objects, and are
assigned to the corresponding accounting event class. Sources are used to create
accounting rules.
The following are the transaction object types:
Header Transaction Object
• Header transaction objects store one row with header source values for each
transaction.
• Each transaction is identified by its unique transaction number.
• Each transaction is also automatically assigned an event.
• Transaction details, whose values do not vary by transaction line or distribution,

should normally be stored in header transaction objects.
- Examples of sources normally stored in header transaction objects include

the Loan Number for a loan or the Contract Number for a contract.
Line Transaction Object
• Line transaction objects store details of transactions that vary based on transaction
attributes. For example, a mortgage transaction for loan origination may have multiple
amounts, each related to different components of the loan. There may be a loan
origination amount, closing cost amounts, and escrow amounts. Each of these
amounts could be captured as separate lines, along with an indication of the amount
type.

• One row per distribution is linked to the associated transaction by transaction number.
Each row is also automatically assigned a line number. Transaction details, whose
values vary by transaction line or distribution, are normally stored in line transaction
object columns, for example, the Loan Number for a loan payment.

Practice 6-1 Overview: Registering a Source System

• Downloading the spreadsheet template.
• Populating the spreadsheet template.
• Validating the spreadsheet content.
• Generating a .zip file.
• Uploading the .zip file.
• Verifying that the source system was created.

Step 4: Configuring Accounting Rules
Accounting Methods group subledger journal entry rule sets together to define a consistent
accounting convention across all accounting event classes and accounting event types for all
source systems. An Accounting Method is attached to the primary and secondary ledgers,
and is the 4th C called the Accounting Convention in a ledger configuration. The three other
C’s are Chart of Accounts, Calendar, and Currency.
Accounting Methods include the following required elements:
• Journal Entry Rules Sets: Each subledger application has a unique journal entry
rule set that groups all the rules together for creating journals.
• Journal Line Rules: This rule defines the debit and credit side of the journal.
Journal line rules are assigned to journal entry rule sets.
• Account Rules: This rule derives the GL account or segment for each debit and
credit of a journal. Account rules are configured with journal line rules on journal
entry rule sets.
Accounting Methods include the following optional elements:
• Description Rules: This rule enables you to concatenate any source system values
and constant values to generate a dynamic description at the journal header or line
level. For example, it might include an invoice number, customer name, or supplier
name. It can provide any information useful for drilldown detail.

• Supporting References: These are used to store additional source information
about transactions, and are useful for reconciliation of accounting to source
systems, as well as reporting. .
• Mapping Sets: This element maps your source system transaction attributes to
your Oracle Fusion chart of accounts. It is used on account rules to derive an
account combination or segment.
• User-Defined Formulas: You can use their results as sources and input values in
many of the subledger accounting rule definitions.

Predefined Accounting Methods
Oracle predefines three Subledger Accounting Methods:

• Standard Accrual
• Standard Accrual with Encumbrances
• Standard Accrual for China
For an accounting transformation to occur, a Subledger Accounting Method (Accounting

Method) must be configured. Companies that are implementing Accounting Hub Cloud and
not using any Fusion subledgers need to create a Subledger Accounting Method. However,
some companies may use a mixture of Fusion subledgers and non-Oracle subledgers. The
Accounting Methods that Oracle owns cannot be modified. Users must duplicate a
predefined Accounting Method, and then modify it or create a new one. Oracle predefines
three Subledger Accounting Methods:
• Standard Accrual: This Accounting Method can be used in most commercial

company primary ledgers by using Fusion subledgers.
• Standard Accrual with Encumbrances: This Accounting Method can be used by

public sector organizations by using Fusion subledgers.
• Standard Accrual for China: This Accounting Method is used exclusively by

companies operating in China.

Managing Accounting Methods and Rules Flow
Following is the order that this course takes to demonstrate how to set up
Accounting Methods and rules:
• Mapping Sets (optional) • Supporting References (optional)
• Account Rules • Journal Line Rules
• User-Defined Formulas (optional) • Journal Entry Rule Sets
• Multiperiod Accounting Classes • Subledger Accounting Method
(optional)
• Description Rules (optional)
The order that this course has taken may not necessarily be the order that your company will
take. However, some of the rules and rule sets are dependent on each other and need to follow
a certain order.
It is a best practice to create the lowest setting first. For example, because an Account Rules
might need to use a Mapping Set, the Mapping Set should be defined first.

Configure Accounting Rules with a Streamlined
Navigation Across Rule Components
Navigate to: Others > Setup and Maintenance > Setup: Fusion Accounting Hub > Accounting
Transformation > Configure Accounting Rules
You can configure accounting rules with a streamlined navigation across rule components.
• Select the Configure Accounting Rules task from the Setup and Maintenance work
area.
• Highlight the subledger application that you use to configure accounting rules.
• On the Configure Accounting Rules user interface, navigate across the rule
components that you would like to create or edit.
The Accounting Hub Administration role is required to access the Configure Accounting
Rules task.

How the Different Types of Rules Fit Together
Navigate to: Others > Setup and Maintenance > Fusion Accounting Hub Offering > Setup >
Accounting Transformation > Manage Subledger Journal Entry Rule set.
The Journal Entry Rule Set includes:
• Journal Line Rules: The debit and credit lines to be generated
• Account Combination and Segment Rules: Which accounts to use
• Accounting Date: How to determine the accounting date
• Description Rules: At the journal entry level, line level, or both
• Supporting References: At the debit line, credit line, or both
Journal line rules, account rules, and accounting date are required to generate a journal
entry.
After the accounting rules are all defined, you assign them to a particular event class or type
to determine how a balanced journal entry is generated for that event class or type.
You can define multiple subledger journal entry rule sets for an accounting event class or
accounting event type. A single journal entry is generated per accounting event per ledger by
using the line assignments from the journal entry rule set assigned to the accounting event
class or accounting event type.

Loan Source System Example of Accounting Rules
.
Type Account Description Currency Debit Credit
Loan Origination 101.10.15300.000.000.000 Mr. John Doe USD 100,000.00 0.00
Cash 101.10.11100.000.000.000 Mr. John Doe USD 0.00 100,000.00
Journal Line Rule Account Rule Description Rule
The graphic in the slide illustrates how the accounting rules create different parts of a journal
entry.
With the analyzed transaction information and subledger model completed, evaluate the
usage of accounts rules. Understand the functional usage for each rule component and the
requirements for accounting and reporting.
Note: Configuring these accounting rules is covered in detail later in this lesson.

Mapping Sets Overview
Mapping sets are used by account rules to provide an efficient way to derive segment values or
account combination values (output) from one or more source transaction or reference attribute
values (input). Using such input and output mappings is simpler than using complex conditions
on account rules.
Mapping sets can use a segment, an account combination, or a value set as output. For
example, a mapping set can derive values for a single segment, such as a cost center from the
source system’s product descriptions, or a full account combination, such as the Accounts
Receivable account from the customer.
With mapping sets, you can:
• Use up to 10 transaction or reference attributes as inputs into a mapping
• Define a default output value to use when actual input values do not match the
mappings
• Use wildcards for multiple input mapping sets to indicate that the value of a particular
input should be ignored for certain mappings.

• Enter the mappings directly in the user interface or use the spreadsheet available in
the Export option, and then Import. Export enables:
- Exporting a template to create new mappings
- Exporting all mappings already created to add or edit the current mappings
• Reuse on more than one account rule

Creating Mapping Sets
Mapping sets require the following:

• Name and Short Name
• Output Type
• Subledger Application
• Input Sources
• Chart of Accounts or Value Set
• Mapping Input and Output Values
When creating a mapping set, the following is required:
• Name and Short Name: Give your mapping sets a meaningful name because it is
available in a list of values in an account rule. Short Name is used as a code in the
table, cannot have any spaces, and must be uppercase.
• Output Type: You can choose Segment, Account Combination, or Value Set. The
output type determines what other elements are required. For example, Segment
requires a Chart of Accounts segment to be identified, such as Cost Center.
• Subledger Application: Mapping sets are unique to each subledger application in

order to know which input sources to make available. This is scoped at the start of
the new mapping set.
• Input Sources: You must choose, based on the subledger application and event
class, the source for the values to be used in the input section. You can use up to 10
sources as inputs into a mapping.
• Chart of Accounts or Value Set: The output type determines what is required.
- Segment Output Type: Chart of Accounts name and segment are
required.
- Account Combination: Chart of Accounts name is required.
- Value Set: Value set name is required.

• Mapping Input and Output Values: You can enter the mappings directly in the
user interface, use the spreadsheet available in the Export option, and then Import,
or use the FSM Import/Export web service. With input and output values, you can:
- Map the input source values (Note: No list of values is available.) to the
output values (Note: A list of values is available.)
- Define a default output value to use when actual input values do not
match the mappings.
- Use wildcards for multiple input mapping sets to indicate that the value of
a particular input should be ignored for certain mappings.

Import Mappings of Mapping Sets
You can import mappings of mappings sets rules using a spreadsheet template.
Import high volume of mappings of mapping set rules using the subledger accounting file-
based data import spreadsheet template.

Practice 6-2 Overview: Creating a Mapping Set
This practice covers creating a mapping set.

Account Rules Overview
Account rules are ultimately used in journal entry rule sets to derive the accounts for
the debits and credits of an event class.
Account rules have three main elements:
• Rule Type
• Value Type
• Conditions
Account rules are the most critical elements of an Accounting Method because they derive the
accounts for the debits and credits of an event class.
Multiple account rules are used in a journal entry rule set, at least one for debit and one for
credit.
Similar to mapping sets, account rules require a name, short name, and subledger application.
The three elements of an account rule are detailed in subsequent slides.

Rule Types
Account rules must be one of three types:

• Account
• Segment
• Value Sets
Rule types are similar to the mapping set output type:
• Account Rules by Account: Define account rules by account to determine the

entire account combination. If using a mapping set in the account rule, the mapping
set must be defined with the same Account Combination output type.
• Account Rules by Segment: Define segment rules to derive a specific segment of

the account. If using a mapping set in the account rule, the mapping set must be
defined with the same segment or with a value set that is assigned to the chart of
accounts and segment of the account rule. If both an account combination rule and
a segment rule are assigned to a journal line in the journal entry rule set, the
segment rule takes precedence over the account rule in that particular segment.
• Account Rules by Value Sets: Define account rules based on value sets rather than
chart of accounts. This enables you to share the same rule between more than one
chart of accounts, if the segments in these charts of accounts share the same value
set. If using a mapping set on the account rule, the mapping set must also be
defined with the Value Set.

Value Types
Account rules have five value types:

• Account Rule
• Constant
• Mapping Set
• Source
• Formula
Value types determine where or how the system finds the account combination value,
segment value, or value set value. The choices are:
• Account Rules: Use an existing account rule. This is useful if you are using a
condition. If the condition is not met, you can use an existing account rule as the
second priority.
• Constant: Use a specific value for the account combination value, segment value, or
value set value. For example, you need to use a specific liability account for the
Invoice event class. You can have the constant achieve this.
• Mapping Sets: Use to associate specific source values with GL accounts or segment
values.
• Source: Use a source where an account combination or a segment value exists in

the source system. For example, an external billing system might have a revenue
account on the invoice it creates. So the source could be the revenue account
column of the staging table.
• Formula: Use a user-defined formula for more complex rules.

Account Rules Best Practices
Define an account rule once and use it multiple times:

• Define a source or constant-based account combination rule.
• If possible, use an account combination rule rather than building segment by
segment.

Conditions
• Conditions are used to refine the details of the results of the journal created by the
Accounting Method.
• The Create Accounting process evaluates conditions based on the priority of the rule
detail. When the condition is met, the rule is applied.
• The following accounting rules can have conditions:
– Account Rule
– Description Rule
– Journal Line Rule
Conditions can help refine the details needed on the results of the journal generated from the
Accounting Method during the Creating Accounting process.
For example, you might want a specific account number generated for billings dated this year
over next year. The account rule condition could achieve this. When using a condition, you
must have at least two priority lines on the account rule. Priority 1 would be for this year and
priority 2 for the next year. The Create Accounting process evaluates conditions based on the
priority of the rule detail. When the condition is met, the rule detail is applied.
- Journal line rule conditions determine whether a journal line rule and its
associated account rules and description rules are used to create the
subledger journal entry line.
• Account Rules
- These determine the accounts for the subledger journal entry lines.
• Description Rules
- These determine both the content and sequence in which the elements of a
description appear.

Conditions
Constant values that are used in any Conditions section must not contain the following
characters:
“ , & | ( ) ‘
For example, in the condition “Project Type” = ABC (123), the constant value that follows the
equal sign—ABC (123)—contains the restricted characters “( ),” which enclose 123 and are
invalid.

Practice 6-3 Overview: Creating Account Rules

• Creating an account rule by using a mapping set and a condition.
• Creating two account rules by using a constant.

User-Defined Formulas
• Use the results as sources and input values in many subledger accounting rule
definitions.
• User-Defined formulas facilitate complex derivation logic for subledger journal
entries.
Operators
Navigate to: Others > Setup and Maintenance > Accounting Hub Cloud Offering > Setup >
Accounting Transformations > Manage User-Defined Formulas.
You can now define user-defined formulas and use their results as sources and input values
in many of the subledger accounting rule definitions.
This facilitates complex derivation logic for subledger journal entries such as amounts,
accounts, and descriptions when values are not readily available in the source transaction
systems.
A user-defined formula can be used to:
• Calculate a numeric value
• Derive an alphanumeric value
• Return a date value
It can be used in any of the following accounting rule definitions:
• Journal line rule: Use as a source on a condition or a source of amounts.
• Account rule: Use as a value type on the rule, condition, or both.

• Mapping set: Use as an input value.
• Description rule: Use as a value type on the rule, condition, or both.
• Supporting reference: Use as a source.

Formula Definition
Define user-defined formulas by using sources for the selected event class. Predefined
functions and conditions can also be used to derive the resulting value.
• Enter source enclosed in double quotation marks (").
• Enter constant values enclosed in single quotation marks (').
• Enter date values in the format YYYY-MON-DD.

Predefined Formula Functions
Type Function Description Example
Concatenate two strings into a Concatenate('This is ', 'a test.')

Alphanumeric Concatenate
single string. returns 'This is a test'.
Substring('How are you?', 3,5)

Alphanumeric Substring Extract part of a string.
returns 'w are'.
FirstDayOfYear('2013-Jul-11')
Return the first day of the calendar
Date FirstDayOfYear returns '01-Jan-2013' in date
year based on the parameter.
format.
LastDayOfYear('2013-Jul-11')
Return the last day of the calendar
Date LastDayOfYear returns '31-Dec-2013' in date
year based on the parameter.
format.
The table in the slide lists the type, function, description, and example of the predefined
formulas.
Within the formula expressions, you can use various operators such as addition, subtraction,
multiplication, division, greater than, smaller than, and so on, to derive values from standard
sources and constants. Calculations can be nested by using parenthesis.
You can also use three condition functions:
• IF THEN
• IF THEN ELSE
• IsPositiveInteger


FirstDayOfMonth('2013-Jul-11')
Return the first day of the month
Date FirstDayOfMonth returns '01-Jul-2013' in date
based on the parameter.
format.
LastDayOfMonth('2013-Jul-11')
Return the last day of the month
Date LastDayOfMonth returns '31-Jul-2013' in date
based on the parameter.
format.
Return the date a specified number AddMonth('2013-Jul-11',2)

Date AddMonth of months after the date in the returns 11-Sep-2013 in date
parameter. format.
Return the year of a date source in YearNum('2012-Feb-28') returns

Numeric YearNum
four-digit format. the number 2012.

Return the month of a date source MonthNum('2012-Feb-28')

Numeric MonthNum
in numeric format. returns the number 2.
Return the day of a date source in DayNum('2012-Feb-28') returns

Numeric DayNum
numeric format. the number 28.
Round a number to a specific Round(183.1123, 2) returns 183.11

Numeric Round
decimal place. Round(183.1123, -1) returns 180
RoundUp(0.01) returns 1.
Numeric RoundUp Round up a number to integer.
RoundUp(1.50) returns 2.
formulas.

RoundDown(0.01) returns 0.
Numeric RoundDown Round down a number to integer.
RoundDown(1.50) returns 1.
Numeric Power Return the power of a number. Power(3,2) returns 9.
Return the number of non-adjustment If accounting calendar is

accounting periods between two dates. defined as Monthly,
•If start date is not the first day of an NumberOfGLPeriod('2013-Jul-
accounting period, it is counted as one 11', '2013-Oct-10') returns 4.
Numeric NumberOfGLPeriod
period.
•If end date is not the last day of an
accounting period, it is counted as one
period.
formulas.


If source value = 123, it returns
text value ‘123.’
Alphanumeric ToText Convert numeric source values to text.
If source value = 123.45, it
returns text value ‘123.45.’
If source value = ‘123’, it returns
Convert text format source values to text value 123.
Numeric ToNumber
numeric values. If source value = ‘123.45’, it
returns text value 123.45.
formulas.

Practice 6-4 Overview: Creating a User-Defined
Formula
This practice covers creating a user-defined formula to calculate an adjusting
mortgage rate.

Creating Description Rules
Use description rules to define the elements of a description that appear on the
subledger journal entry at the header level, line level, or both.
• The definition determines both the content and the sequence of the elements of the
description.
• Assign conditions to indicate that the description is selected for display only if the
conditions are satisfied. Conditions are associated with priorities such as account
rules.
• Subledger journal line descriptions are transferred to the General Ledger only if the
General Ledger Journal Entry Summarization option is set to either of the following:
– Group by General Ledger period
– Group by General Ledger date
• A description rule can be defined with combinations of source and literal values. If
sources are used in the rule, the accounting event class associated with the sources
determines in which subledger journal entry rule set the description rule can be
selected and used.
• You can build descriptions by using any available source from the application or user-
defined formula.
• For example, you want to see Customer Name and Transaction Type on the header
of the subledger journal. The following are the description details that are entered by
using literals and sources:
- Literal = Customer:, Source = Customer Name
- Literal = , (Comma)
- Literal = Transaction:, Source = Transaction Type
• The result in the journal would be, “Customer: Advantage Corp, Transaction: Invoice.”
• Line descriptions can be transferred to the General Ledger based on the General
Ledger Journal Entry Summarization options.

- If the value is Group by GL Date or Group by Accounting Period, each line
description for each journal entry transferred to the GL in the same group is
displayed and visible.
- If the value is Summarize by GL Date or Summarize by Accounting Period

and if all the lines can be summarized, each line description is not displayed
on the General Ledger journal entries.
- In both cases, when drilling down to subledger, all descriptions are still
available and displayed

Practice 6-5 Overview: Creating a Description Rule
This practice covers creating a description rule for the Personal Loan subledger.

Creating Supporting References
• Supporting references are used to store additional source information about a

subledger journal entry at the line level.
• Supporting references can optionally calculate or maintain a balance based on a
transactional data source transferred through Subledger Accounting.
• Supporting reference balances are not transferred to the General Ledger.
Supporting references can be defined by using either of the following options (located on
tabs):
• With Balances:
- Facilitates reconciliation back to the subledgers and source systems by

tagging the journal entries with transaction and reference attributes
- Creates a report on balances by dimensions not captured in the chart of

accounts
- Enriches Oracle Fusion Business Intelligence Applications reporting on

subledger journals
- Can be carried forward into the next fiscal year or start over each fiscal
year. For example, you may maintain a balance of revenue each year by
account manager.
• Supporting references with balances are limited to 30 definitions. You can consider
adding more source assignments to predefined supporting references, rather than
creating a new one.

• Without Balances:
- Aids in slicing and dicing the data of a journal
• Supporting references without balances are unlimited in terms of the number of

definitions.
Note: Supporting reference balances are not transferred to the General Ledger and are
accessible only in Oracle Transactional BI reports and analysis.

Practice 6-6 Overview: Creating a Supporting
Reference
This practice covers creating a supporting reference for the Personal Loan subledger
to track loans by loan officer.

Creating Journal Line Rules
The journal line rule determines how each debit and credit entry is created. It defines
the following:
• Accounting class
• Side as debit, credit, gain, or loss
• Sources that drive the values on the entry, such as amount. Accounting attributes link
sources to specific journal entry line values such as the accounted amount.
• Advanced setup features, such as business flows, rounding options, and multiperiod
accounting.
Note: Refer to the Oracle Financials Cloud: Implementing Subledger Accounting Guide
for more information about journal line rule advanced options.
Following are the characteristics of journal line rules:
• Are defined within the context of accounting event classes
• Are used in subledger journal entry rule sets that have the same event class
• Can contain conditions that determine when they are used to create a line
To create a journal line rule, select values for options such as:
• Side: Debit, Credit, Gain, or Loss. For example, to create a journal line rule to
capture revenue, you could create a credit line rule.
• Merge Matching Lines: To summarize or not to summarize subledger journal entry

lines within each subledger entry. This setting does not affect the journal in the
General Ledger. It affects the detail seen in Subledger Accounting from the
drilldown. The choices are:
- No: No summarization of lines
- All: Lines merged only if they share the same account combination,
description, supporting reference values, and accounting class. This
merges debits and credits together.
- Debit or Credit: Only the Debits merged together for the same account
combination and only the Credits merged together.

• Accounting Class: To classify journal entry lines. For example, a line that is used to
record the collection of cash would typically have an accounting class of Asset.
• Conditions: To restrict the use of a journal line rule by controlling when a particular
journal line rule is used by the Create Accounting process. For example, generate a
freight expense line if freight charges exist. Or generate a tax line if tax is associated
with a transaction. The journal line is created only if the conditions evaluate to true.
Advanced Options
• The Subledger Gain or Loss Option: Applied only to amount calculations for the
primary ledger. Gain or loss amounts are not converted to reporting currency or
non-valuation method secondary ledgers. If the option is enabled, the journal line
holds the gain or loss amounts calculated by the subledger. The gain or loss amount
is calculated as the difference in applied amounts due to fluctuations in conversion
rates, based on conversion to the ledger currency. Foreign exchange gain or loss
occurs when two related transactions, such as an invoice and its payment, are
entered in a currency other than the ledger currency, and the conversion rate
fluctuates between the times that the two are accounted.
• The Rounding Class Option: Along with transaction rounding, grouping together
of journal lines and calculation of the transaction rounding difference. Subledger
transaction rounding differences can occur when a transaction has multiple, related,
applied-to transactions, such as a Receivables receipt applied to multiple invoices.
• The Link Journal Lines Option: If using the business flow of the same entry,
determination of whether the journal line rule is set up to establish a link between
the accounting of transactions that are related both within the same application and
across applications. The alternatives are:
- None: No link is established.
- Copy from corresponding line: Build an account for a journal line by

using segments from the offsetting entry of the current journal line.
• Multiperiod Accounting: This feature enables you to create accounting entries

across more than one accounting period, for a single accounting event. For
example, allocate a prepaid expense across multiple accounting periods.
Accounting Attributes Assignments: When creating a journal line rule, accounting attribute
assignments are automatically established based on the default accounting attribute
assignments for that journal line rule’s accounting event class. You can override this default
mapping of standard sources to accounting attributes. The list of values for the source
override includes all sources assigned to the accounting attribute for the event class
associated with the journal line rule. For example, the accounting attribute can be Amount,
GL date, Currency, and so on.

Practice 6-7 Overview: Creating a Journal Line Rule
This practice covers creating a journal line rule.

Journal Entry Rule Sets Overview
Each subledger application typically has one journal entry rule set per transaction type
that contains the rules for creating journals. It contains the following:
• Event Class and Type
• Account or Segment Rules
• Descriptions (Optional)
• Supporting References (Optional)
Each registered subledger application has its own journal entry rule set definition that joins all
the other accounting rules together. At least one line must be defined for each event class and
type combination. Each line must contain the following:
• A journal line rule
• Account or segment rules or both
Each line can optionally contain:
• A description rule
• A supporting reference
After saving the journal entry rule set, the system automatically runs the Update Subledger
Accounting Options process. This process activates the subledger accounting options for the
new subledger application. The subledger accounting options include GL transfer
summarization option, rounding option, reversal method, and so on.

Creating Journal Entry Rule Sets
Journal entry rule sets define the following:

• Journal Entry Rule Set Header
• Journal Header
• Journal Lines
Before defining the journal header and lines, the journal entry rule set header must be
defined. It contains the following:
• Name and Short Name
• Event Class: For example, Billing System
• Event Type: For example, Billing Created
• Chart of Accounts: Required only if any account rules to be used in the journal
entry rule set have been defined with a chart of accounts. The two chart of accounts
must be the same.
The journal entry header contains:
• Accounting Date: Determines in which accounting period and date the journal is
posted. You can choose from three different sources:
- Standard: You can use Transaction Date, which is the date of the
transaction in the external subledger application.
- Application: You can choose to use the Journal Entry Creation Date, which
is the date the journal is created by the Create Accounting process or the
Accounting Event Date, which is the date the journal is transferred to the
Accounting Events table.

- Formula: You can use the formula rule to create your own rule.
• Description Rule (Optional): If you defined a description rule, you may add it here
or at the line level.
The journal entry lines contain the following:
• Type: This includes Debit, Credit, Gain or Loss, Gain, or Loss
• Journal Line Rule: The journal lines rules side must match the line type chosen.
• Accounting Class: This defaults from the journal line rule.
• Account Combination Rule and Segment Rules: You can include both types on
the line. For example, you can put an account combination rule on the revenue or
credit line to derive the complete combination. Then put a segment rule on cost
center to override the combination rule’s cost center value with a different value. If
rules are defined with sources, all sources must have been assigned to the same
event class associated to the journal entry rule set.
• Line Description Rule (Optional)
Supporting references (Optional): Each journal line can have a supporting reference or
multiple supporting references. A supporting reference can be used in a journal entry rule set
only if it is defined with a source from the event class of that journal entry rule set.

Practice 6-8 Overview: Creating a Journal Entry Rule
Set
This practice covers creating a journal entry rule set.

Accounting Methods Overview
Accounting Methods are required for accounting transformations. You can:

• Modify a predefined Accounting Method (with restrictions)
• Duplicate an existing or predefined Accounting Method, and then modify it
• Create a new Accounting Method
For an accounting transformation to occur, a Subledger Accounting Method (Accounting

Method) must be configured and assigned to the primary ledgers and the subledger level
secondary ledgers. The ways to configure an Accounting Method are:
• Duplicating an existing or predefined Accounting Method, and then modifying it. This
is a best practice if you are also implementing other Oracle Cloud Subledger
Applications.
• Creating a new Accounting Method without duplicating an existing one. It is

recommended that you do this only if you are not implementing any Oracle Cloud
subledgers.

Creating Accounting Methods
When creating an Accounting Method, you do the following:

• Give it a name
• Optionally attach a chart of accounts
• Assign the journal entry rule sets by event class and event type for the subledger
application
• Activate the journal entry rule set assignments
• Assign the Accounting Method to a ledger or ledgers in Specify Ledger Options
At the time of creation of an Accounting Method, you do the following:
• Give it a name: Naming conventions are important and should reflect the nature of
the Accounting Method. For example, if you are creating an Accounting Method for
a secondary ledger by using GAAP rules, you might name it: Standard Accrual SL
US.
• Optionally attach a chart of accounts: If a Journal Entry Rule Set is defined with a
chart of accounts, you must attach the same chart of accounts to the Accounting
Method.
• Assign Journal Entry Rule Sets: For each event class-event type combination,
assign a journal entry rule set. The Create Accounting process uses the rule set to
create journals. You can assign multiple journal entry rule sets to an event class or
type by using non-overlapping effective dates. This can be used to accommodate
changes in Accounting Methods due to new regulations or corporate policies.
• Activate the Journal Entry Rule Set Assignments: Click the Activate button in the
journal entry rule set assignments section. All the assigned journal entry rule sets
must be Active for the Accounting Method to be used by the Create Accounting
process. This validates the journal entry rule set and its subcomponents. It also
generates compiled code for the accounting engine.

• Assign the new Accounting Method to a ledger or ledgers: When assigning an
Accounting Method to a ledger, you must select an Accounting Method that uses
the same chart of accounts, or an Accounting Method that does not have an
assigned chart of accounts. Accounting Methods are required on both primary
ledgers and subledger-level secondary ledgers.

Valuation Methods for Accounting Hub Cloud
Subledgers
• Transfer directly to a Secondary Ledger.
• Meet management reporting and country-specific accounting requirements.
• Configure valuation method-enabled subledgers.
• Examples of when to use this feature:
– Value financial instruments differently between international and local accounting
standards.
– Represent income and expense differently for management accounting purposes.
This feature:
• Enables transfers directly to a secondary ledger for a non-seeded subledger.
• Is available in the seeded subledgers such as fixed assets and cost accounting.
• Uses different bases of valuing transactions and accounts for the transactions in
different ledgers to meet various management reporting and country-specific
accounting requirements.
• Uses different amounts for accounting and creating materially different accounting
representations.
Benefits: This feature can reduce:
• Accounting costs by ensuring that the process of generating variable financial

statements is automated.
• Audit risks by using general ledger reporting features plus the Fusion Accounting
Hub accounting repository. Auditors are able to trace and track the bookings to
both ledgers.

Valuation Methods Example
Product System
FAH Billing
Accounting Accounting
Representation Representation
US GAAP IFRS
In this example, The Product System, for instance, a billing system, can simultaneously feed
two different accounting representations or the ledgers in General Ledger.
• One of these representations is based upon US GAAP (Generally Accepted

Accounting Principles) and another is based upon IFRS (International Financial
Reporting Standards).
• There are material differences between US GAAP and IFRS.
• A primary ledger is used for corporate profit and loss statements, while a secondary
ledger can carry alternate representations as well as a different level of granularity
in general ledger balances.

Configuring Subledger Applications to Support
Multiple Valuation Methods
1. Setting the Subledger Application context.
2. From Fusion Accounting Hub implementation project, go to Manage Subledger
Accounting Options task after setting the Subledger Application context.
3. Search for the Secondary Ledger.
a. Expand list of components for the ledger and click on Edit Accounting Options for
the subledger application.
b. Enable the Valuation Method Ledger option.
4. Run the Update Subledger Accounting Options process for the subledger application.
• Enable Subledger applications and Ledgers for valuation method support before
creating any transaction data.
• Send transaction feeds separately to secondary ledgers enabled for valuation

method.

Migrating the Accounting Transformation
Configuration
• Migrate setup task lists from one instance to another for specific subledger
applications or all subledger applications.
• Use the export and import functionality in the Functional Setup Manager.
When migrating accounting rules from one instance to another, you must migrate task lists
in their entirety. The migration requirements are as follows:
• The journal entry rule sets and Accounting Methods must be successfully activated.
Invalid journal entry rule sets or Accounting Methods cause import failure.
• Your setup data migration must include all dependent business objects from other
required setup tasks, such as Define Ledgers. The import sequencing of these
dependent business objects must be before accounting rules business objects.
Note: See the lesson titled “Introducing Functional Setup Manager” for additional
information about the export and import process.

Enhanced Export and Import of Subledger
Accounting Setup Data
• Allows you to export and import high
volume Subledger Accounting setup data.
Groups setup data in batches and generate
JERS
• Service
multiple data files.
• Export and import in batches is enabled for Account
Rules
the these services: Service
– Journal Entry Rule Sets (JERS)

Service Mapping
Sets
Service
– Mapping Sets Service
Description
– Account Rules Service Rules
Service
– Description Rules Service
Enhancement allows you to export and import high volume Subledger Accounting setup data.
with improved scalability and performance.
The setup export and import services automatically group setup data in batches and generate
multiple data files to make it easier to migrate high volume setup data.
For exporting, a single zip file is generated to include all the setup data.
• You can download the zip file and import it into the target instance.
• If a Subledger Accounting Rule is in both the source and target instance, the rule in the
target instance is replaced with the same rule exported from the source instance.
• When a mapping set is imported to a target instance, the mappings that are already in
target instance but not in the source instance, remain in the target instance.

Revised Task Lists
• The task order for the following task lists are improved:
– Define Transaction Accounts
– Manage Accounting Rules
– Define Subledger Accounting Methods
– Define Accounting Rules for Rapid Implementation
Navigate to: Setup and Maintenance > Setup: Fusion Accounting Hub > Task Panel >
Search.
The task order for the following task lists are improved to facilitate export and import in
batches.

Practices 6-9 Overview: Creating a Subledger
Accounting Method
• Creating a subledger accounting method.
• Assigning your new accounting method to your ledger.

Step 5: Uploading Transaction Data from a
Spreadsheet for Testing
The graphic in the slide depicts how to upload transactions from a spreadsheet.
At a minimum, testing should ensure the following:
• The subledger journal entries are successfully created and tie back to the source
system.
• The subledger journal entries are accurately produced as required.
• The subledger journal entries contain the appropriate dates, amounts, descriptions,
and accounts.
• The conditions used to determine journal line rules, account rules, or descriptions are
valid.
Note: The list is not intended to be comprehensive.
Manually Upload Transaction Data: To upload transaction data manually, perform the following
sequential steps:
Download the transaction data template by using the Manage Subledger Application task.

Extract the three files contained in the downloaded template.
• Metadata.txt: The metadata file contains key information about the source system.
It also contains related information that you must know when populating the
transaction spreadsheet for upload, for example, the required data format. This
metadata file includes:
- Creation date
- Application short name Date format
- Transaction header file name
- Transaction line file name
• XlaTrxH.csv
- This file contains the header-level columns for the transaction data that
can be populated.
- The column names match the short names of the sources that were
included in the Transaction Information worksheet during the registration
of your source system.
- One column that is available in the header and line file is the Transaction
Number. The Transaction Number links the header and its corresponding
lines information.
• XlaTrxL.csv
- This file contains the line-level columns for the transaction data that can
be populated.
- The column names match the short names of the sources that were
included in the Line Information worksheet during the registration of your
source system.

Step 5: Uploading Transaction Data from a
Spreadsheet for Testing
Populate the header and line CSV files. Each transaction in the header file requires at least on
record in the line file and vice versa. You can also use PAAS or other tool to transform
transaction data from the source system into the required format.
Compress the three files by using a Zip file format.

• The name of the .zip file must begin with XlaTransaction.
• To uniquely identify the file, we recommend that you suffix the file with the
subledger source name and date, for example: XlaTransactionRetailLoan050417.zip.
Upload the .zip file into Universal Content Management. Note: You must have the
Accounting Hub Cloud Integration Duty Role to import accounting transaction data to
perform this step.
• Navigate: Navigator > Tools > File Import and Export.
• Click Upload.
• Browse for the compressed file.
• Select account: fin/fusion/AccountingHub/Import.
• Save and Close.
• View the file upload results in the Search Results section.

Note: Error correction is dependent on the Update Subledger Transactions privilege. You can
remove or add the privilege per your company's policy.
The uploaded transaction data is kept in the Accounting Hub Cloud for 90 days. Exceptions
include:
• Transactions that are used to create multiperiod accounting entries. This type of
transaction is kept until the end date of the multiperiod duration.
• Unaccounted transactions. These transactions are not purged, even if they are
more than 90 days old.

Automated Processing Options
Transaction data in CSV format can be imported into Accounting Hub Cloud by using
one of three available integration options:
• Oracle WebCenter Content Client command-line tool
• Oracle UCM Web Services
• ERP Integration Service, upload to UCM
Automated processing options are available to bring transaction data files from the registered
source systems into Accounting Hub Cloud. This includes data from other external sources,
such as other user-defined applications, transaction applications, or legacy applications.
Optionally, data transformation processing may be required for data sourced from PaaS or
other external files.
Transaction data in CSV format can be imported into Accounting Hub Cloud by using Universal
Content Management (UCM) with one of three available integrations. You can set up your
external source system to automatically upload or download files in UCM. Of the three options,
the first two options are recommended, because they are easier to use and can handle larger
files.
Options:
• The Oracle WebCenter Content Client command-line tool is a command-line tool that
transfers files from an external system into UCM.
- You must provide basic information, such as the URL, UCM username and
password, name of the file to transfer, and the UCM account to transfer it
into.
- Additional documentation is available in the Oracle Fusion Applications

Common Implementation Guide in the section titled “External Integration.”

• Oracle UCM Web Services is a web service that can be called directly to upload an
attached file to UCM by using the same code as the Oracle WebCenter Content
Client command-line tool.
- Examples of Java code and libraries are available for download.
- You must modify them with basic information, such as the URL, UCM
username and password, name of the file to transfer, and the UCM account
to transfer it into.
- Documentation is available in Oracle Fusion Middleware Developer’s Guide

for Universal Content Management in the section titled “Using Oracle UCM
Web Services.”
- Customers should use GenericSoapService. Note that the documentation

for GenericSoapService indicates that it does not use MTOM and thus
cannot handle larger files, but this is no longer true.
• ERP Integration Service is a web service that can be called directly to upload an
attached file to UCM. This is documented through the Oracle Financial Cloud
documentation. You must write or generate code to call the web service.
Import the transaction data by using the Import Accounting Transactions process.

Accounting Hub Maintenance Overview
You can use the Accounting Hub Maintenance process to delete invalid, unaccounted,
and finally accounted
transactions. Here are the different modes in which you can run this process:
• Purge Final Accounted Transactions
• Purge Unaccounted Transactions
• Purge Invalid Transactions
89 © 2020, Oracle and/or its affiliates. All rights reserved.
The Accounting Hub Maintenance process is scheduled automatically by the Import

Accounting Transactions process in the Purge final accounted transactions mode to delete
processed transactions after the specified transaction retention period. However, Accounting
Hub retains some transactions beyond the transaction retention period:
• Transactions that are used to create multiperiod accounting entries. This type of
transactions is kept until the end date of the multiperiod duration.
• Unaccounted and invalid transactions aren't purged even after the transaction
retention period.
By default, the transaction retention period is of 90 days. However, you can change the
duration of transaction retention period based on your requirements. To change the
accounting retention period, on the Manage Subledger Accounting Lookups page, specify a
value for the ORA_XLA_AHC_RETENTION_DAYS lookup type. The minimum value of
transaction retention period can be 30 days and the maximum value can be 458 days.
When you delete final accounted transactions only the corresponding transaction objects
records are deleted. The associated accounting events, transaction entities, and subledger
journal entries remain intact for future analysis and audit purposes.

Export Accounting Errors When Purging Invalid
Transactions
The ERP Integration Web Service can be leveraged to extract and purge transactions
that are not successfully accounted by the accounting process.
• Submit the Accounting Hub Maintenance process in the Purge Invalid and
Unaccounted Transaction mode to delete accounting transactions that:
– Are imported into Accounting Hub for a particular ledger and subledger
– Are not yet accounted successfully.
• Import the corrected transaction data again.
• Reuse the same transaction number to import the accounting
transaction again after they are purged from Accounting Hub.
When you purge invalid transactions from Accounting Hub, the accounting errors for the
purged transactions are exported to an execution report. You can review the accounting
errors in the execution
report, update the accounting transactions accordingly, and then import the corrected
transactions to Accounting Hub again.
List of information that gets deleted for eligible transactions:
• Transaction records in transaction objects.
• Transaction entity records.
• Accounting events including reversal event.
• Invalid journal entries in these ledgers:
- Primary ledger and associated reporting currencies.
- Non-valuation method secondary ledgers.
- Valuation method secondary ledger.
• Incomplete accrual reversal journal entries.

The process generates:
• An output file listing the deleted transactions.
• Two CSV files with transaction header and line details for the deleted transactions
that you can modify the source value as needed and import the accounting
transactions again.
• The CSV output files have same layout as the updated transaction template
introduced with the Flexible Configuration feature.
Note: When the Accounting Hub Maintenance process is submitted in the Purge Invalid and
Unaccounted Transactions mode, it deletes all eligible transactions for the ledger and
subledger in the program parameter. To avoid unintended deletion of unprocessed
transaction, run this process only after all the import accounting transaction and create
accounting processes are completed for the ledger and subledger.

Flexible Configuration of the Accounting Flow
You can choose to run various portions of the accounting flow separately, or run the
entire process from end-to-end.
Navigate to: Setup and Maintenance > Setup: Fusion Accounting Hub > Change Feature Opt In
> For the Fusion Accounting Hub, click the Features icon.
You can choose from three different methods of handling the accounting flow:
• Do not enable the Flexible Configuration feature.
• Enable the Flexible Configuration feature and upload data in single runs.
• Enable the Flexible Configuration feature and upload data in an import set.
Enable this feature from the Functional setup Manager Feature Opt In page. After you enable
this feature, you must download a new transaction template and map the sources to the
corresponding columns in the new template.
The feature is: Flexible Configuration of Accounting Hub Cloud Service End to End Flow.

Not Enabling the Flexible Configuration Feature
Choosing this option enables you to create

accounting in:
• Final
• Draft
Navigate to: Tools > Scheduled Processes > Search for Import Accounting Transactions.
If you choose not to enable to Flexible Configuration option, you can choose to create
accounting in:
• Draft: This enables you to view the journal entries from the Review Subledger
Journals page by searching with the Status of Draft. Using Draft mode is important for
testing new subledger accounting methods. Draft mode is also useful to help ensure
that segregation of duties is enforced. This enables one user to import the journals
and another user to post the journals.
• Final: This enables you to run the entire process from end-to-end. It imports the
journals, creates accounting entries, and posts the journal entries to the General
Ledger.
If any invalid entries are created, query journal entries with Invalid status from the Review
Subledger Journals page, view the transaction, and correct the errors directly.

Enabling the Flexible Configuration Feature
Navigate to: Tools > Scheduled Processes > Search for Import Accounting Transaction
Navigate to: Tools > Scheduled Processes > Search for Import Accounting Transactions from
Interface.
After enabling the Flexible Configuration feature the Import Accounting Transaction process is
enhanced with additional parameters.
You can then choose one of two ways to handle the accounting flow:
• Upload Data in Single Runs: With Import from Interface set to Yes, you can load and import
transaction data in a single run. You can then either Create Accounting in Final or Draft and
choose the Report Style of Summary, Detail, or None. You can also choose to Transfer to
General Ledger and Update Supporting Reference Balances submitted at the same time.
• Upload Data in an Import Set: With Import from Interface set to No, you can split a large batch of
data into multiple zip files and import them individually with same import set name. This allows
you to load data in multiple runs and still have them validated as a group when you import
transactions from the interface later on. When you are ready to import the group or set, you run
the Import Accounting Transactions from Interface process rather than the Import Accounting
Transactions process. The Import Accounting Transactions from Interface process has the same
parameters or options as the Import Accounting Transactions except the first parameter is Import
Set instead of Data File.

Transaction Reversal
You can import a transaction record with the value of the reversal indicator as Y to
generate reversal accounting that offsets the accounting of the original transaction in
Accounting Hub.
Navigate to: My Enterprise > New Features > Offering: Fusion Accounting Hub > Got to Opt in.
For example, an accounting transaction with transaction number 1001 is imported and accounted in
Accounting Hub successfully. Later, this transaction is canceled in the source system. You can import an
accounting transaction with same transaction number 1001 and set the reversal indicator as 'Y'. After the
new accounting transaction record is imported, new journal entries are created to offset the accounting
effect from the original transaction.
To take advantage of this feature, you must enable the Flexible Configuration of the Accounting Flow
feature. Use the Opt-In UI to enable this feature.
After you enable this feature, you must enable transaction reversal in the Manage Subledger Application
task for subledgers that will uptake this feature. You also need to download a new transaction template and
map the sources to the corresponding columns in the new template.

Practice 6-10 Overview: Uploading Transaction Data
from a Spreadsheet
• Downloading and extracting a transaction .zip file.
• Entering data in the transaction spreadsheets.
• Zipping the completed transaction spreadsheets.
• Uploading the transaction .zip file in Draft mode.

Subledger Journal Entries in Accounting Hub Cloud
The Create Accounting process goes through the following flow:
• The source system transactions are uploaded into Universal Content Management.
• The transactions are then imported into Accounting Hub Cloud by using the Import
Accounting Transactions process.
• The Create Accounting process is automatically submitted.
• Subledger journal entry rule set definitions and sources from transaction data are
applied to create subledger journal entries.
• The subledger journal entries are summarized and imported to Oracle General
Ledger.
• The journals are then posted to the GL Balances Cube.
• Financial reports are generated from the GL Balances Cube.
Note: It is a best practice to have summary journals, and then drill down to details in
Subledger Accounting’s repository.

Step 6: Ensure that All Accounting is Correctly
Generated
Methods Used to Review the Accounted Journal Entries:
• These predefined reports can be used to view the journal entries:
– Journal Import Execution Report
– Create Accounting Execution Report
– Journal Entries Report
– Account Analysis Report
• Use the General Accounting > Journals user interface.
• Create an Oracle Transactional BI report or analysis.
You can run the following reports to review the journal entries created from your source
system:
• Journal Import Execution Report: This is generated automatically after the Import
Accounting Transactions process automatically runs.
• Create Accounting Execution Report: This is generated automatically after the

Import Accounting Transactions process automatically runs the Create Accounting
Process. The Create Accounting Execution Report runs in summary by default. It
can be in detail or summary if run by the Create Accounting process. It details the
following by Event Class and Ledger:
- Number of Documents
- Number of Events Processed
- Number of Events with Warning
- Number of Events in Error
- Journal Entries Count
- Journal Entries (if run in Detail)

• Journal Entries Report: This must be submitted or scheduled to run from
Scheduled Processes. It lists detailed information about subledger and General
Ledger journal entries by journal source, ledger, and accounting period.
• Account Analysis Report: This must be submitted or scheduled to run from

Scheduled Processes. It details Oracle General Ledger account balance changes by
using subledger journal entry information.
You can also navigate to: General Accounting > Journals > Tasks panel tab > Journals
Manage Journals or Subledger Accounting > Review Subledger Journals.
Finally, you can create an Oracle Transactional BI report or analysis using the Subledger
Accounts – Journals Real Time subject area.

Correcting Accounting Hub Transaction Data for
Invalid Entries
You can correct errors in uploaded transaction data by using the Manage Journals
work area.
Navigate to: General Accounting > Journals > Tasks panel tab > Subledger Accounting >
Review Subledger Journals.
To correct errors, perform the following:
• Using the Review Subledger Journals task, search for subledger journal entries
based on Status Invalid.
• View the transaction.
• Correct the transaction attributes as required. The following predefined attributes

cannot be updated:
- Application Name
- Event Type
- Ledger Name
- Transaction Date
- Transaction Number
- Line Number

• Save the update.
• Resubmit the Create Accounting process.

Searching for Subledger Journals by Transaction
Number
Navigate to: General Accounting > Journals > Tasks panel tab > Subledger Accounting >
Review Subledger Journals.
Search results are displayed faster when you search for subledger journals by transaction
number. This enables you to review the accounting results of a specific transaction without
having to sort through multiple records.
Experience faster performance when searching by transaction number for Accounting Hub
Cloud journals and journal lines in Review Journal Entries.

Practice 6-11 Overview: Viewing the Draft Journals
and Posting the Journals in Final Status
• Viewing the draft journals.
• Posting the journals in final status.
• Drilling down from a journal in GL to view your subledger journal entries.

Adjustment Features of Subledger Accounting
In Subledger Accounting, you can also use the following features:

• Manual Subledger Journal Entries
• Account Override on a Subledger Journal Entry
Oracle Subledger Accounting also provides the following features to make manual
adjustments to existing accounting:
• Manual Subledger Journal Entries: This is useful for creating adjustments that
cannot or do not have a transaction associated with it.
- It is available from General Ledger in the Create Subledger Journal task or

the Create Subledger Journals in Spreadsheet task.
- These journal entries are processed through subledger accounting, and

then transferred and posted to Oracle Fusion General Ledger.
- The transferred journal has the subledger name as the source of the
journal.
• Account Override on a Subledger Journal Entry: You can use the account
override feature to change the General Ledger account on an existing subledger
journal that is generated by the Import Accounting Transactions process or the
Create Accounting process and is in the Final status, regardless of its posting status.

This feature:
- Ensures proper accounting and expedites error correction by editing

accounts directly on a completed subledger journal entry
- Is available from General Ledger in the Review Subledger Journals and

Manage Journals tasks
- Provides an audit trail by keeping the original entry visible. A reason for
the adjustment is also recorded.
- Does not adjust the original source transaction

Subledger Journals in Adjusting Periods
You can enter subledger journals in adjusting periods using the application interface
or ADFDi spreadsheets.
• If the accounting date falls in both the non-adjustment and adjustment periods, the
value of accounting period on the Create Subledger Journal Entry page defaults to
the non-adjustment period.
• You can overwrite it with the adjustment period if required.
• Similarly, use the Create Subledger Journals spreadsheet to post a subledger journal
in the adjustment or non-adjustment period.

Advanced Features of Subledger Accounting
The advanced features include:

• Subledger Accounting Profile Options
• Accrual Reversals
• Multiperiod Accounting
The advanced features of Subledger Accounting are:
• Subledger Accounting Profile Options: Set values for each profile option to
specify how Oracle Fusion Subledger Accounting controls access to and processes
data.
• Accrual Reversals: The Create Accounting process generates an entry that reverses
the accrual entry.
• Multiperiod Accounting: This enables you to create accounting entries across

more than one accounting period for a single accounting event.

Subledger Accounting Profile Options
Profile Option Profile Display Name Profile Description

Control whether transaction data
XLA_DIAGNOSTIC_MODE Diagnostics Enabled used in accounting generation should
be gathered for diagnostics.
Control whether subledger journal
XLA_DISABLE_GLLEZL Journal Import Disabled entries are imported to General
Ledger.
Specify whether the target for
transfer and post-subledger journal
XLA_ENABLE_TRANSFER_TO_EBS_GL Enable Transfer to Oracle EBS GL
entries is Oracle E-Business Suite
General Ledger.
Specify whether the target for
Enable Transfer to Oracle transfer and post-subledger journal
XLA_ENABLE_TRANSFER_TO_PSFT_GL
PeopleSoft GL entries is Oracle PeopleSoft General
Ledger.
Zero Amount Journal Lines
XLA_SHOW_ZERO_AMT_JRNL Show zero amount journal lines.
Displayed

Accrual Reversals Flow
Accrual Reversal Process Steps:
• Assign a date source to the Accrual Reversal Accounting Date Source accounting
attribute from the Manage Accounting Attributes task. Use this attribute to schedule
the automatic reversal of a journal entry. Assign any standard date source or one of
the following application sources to the Accrual Reversal Accounting Date Source
accounting attribute:
- Next Day: The accounting date of the accrual reversal is the next day
following the accounting date of the accrual entry.
- First Day of Next Accounting Period: The accounting date of the accrual
reversal entry is the first day of the following accounting period.
- Last Day of Next Accounting Period: The accounting date of the accrual
reversal entry is the last day of the following accounting period.
Note: You can override the Accrual Reversal Accounting Date Source accounting attribute
values on the journal entry rule set if multiple sources have been assigned to the accounting
attribute.
• Assign a desired source to the Accrual Reversal Accounting Date field in the journal
entry rule set for the rule set that is used to generate the accrual entry.
• Create an accounting event in the subledger application.

• Submit the Import Accounting Transaction process with the data files that contain
the accrual entry from the source system. The Import Accounting Transaction
process and its subprocesses create the accrual journal entry to negate the impact
of the accrual entry. The Manage Subledger Accounting Options, Reversal Method
option enables entries to appear as debit and credit signs reversed or to have
negative amounts. The status of the accrual reversal journal entry is based on both
the accounting period status of the accrual reversal journal entry and the
accounting date.
• Submit the Create Accrual Reversal Accounting process to complete accrual

reversals in future accounting periods as the periods are opened.
• View the accrual reversal accounting entries.

Multiperiod Accounting
Multiperiod accounting enables you to create accounting entries across more than one
accounting period for a single accounting event. The functionality is primarily used to allocate
prepaid expense or revenue across multiple accounting periods.
You can:
• Determine how to distribute the amount across accounting periods
• Specify a prepaid expense or deferral account
• Preview Multiperiod journal entries before creating and posting final entries:
- Submit the Create Multiperiod Accounting process in Draft mode.
- Review the Multiperiod journal entries in the Create Multiperiod Accounting

Execution Report.

Implementation Steps
Define a user-defined formula that determines how to distribute the entered amount across
accounting periods. If required, you can use the Multiperiod predefined sources. For
example:
• Multiperiod Original Entered Amount
• Multiperiod Recognized Entered Amount
• Last Multiperiod Accounting Date
• Number of Days in Current Accounting Period
Define a non-multiperiod journal line rule for the deferral entry specifying the Multiperiod
Class. This rule is used to post the fee amount to the deferral account.
Important: First, define Multiperiod classes by using the Manage Subledger Accounting
Lookups task.
Define a Multiperiod journal line rule for the recognition entry:
• Enable the Multiperiod option and assign the same Multiperiod Class.
• Assign the user-defined formula to the Entered Amount accounting attribute.
• Assign relevant sources to the Multiperiod Start Date and Multiperiod End Date
accounting attributes.

Assign both journal line rules to the same journal entry rule set with:
• A deferral account rule assigned to the non-multiperiod journal line rule
• A revenue or expense account rule assigned to the Multiperiod journal line rule
Schedule the Create Multiperiod Accounting process to run after the Create Accounting
process so that recognition journal entries are properly booked each period.

Multiperiod Accounting Example: Loan Origination
Fees
Upon loan origination on 01-JUL-2016, the origination fee must be booked as
unearned income.
Initial Journal Entry for Loan Fee:
Entered DR (USD) Entered CR (USD)

Receivable 300.00 0.00
Unearned Fee Income 0.00 300.00
The subledger multiperiod accounting and user-defined formula features provide the ability to
meet and comply with accounting requirements, such as the FASB 91, for recognizing loan
origination fees over the life of the loan. This requirement of deferred recognition of fee and
direct loan cost is met by defining the recognition of fee amounts with user-defined formulas.
Example
A loan was originated with the following information:
• Origination date: 01-Jul-2016
• Origination fee: USD 300.00
• Loan duration: 6 months
• Maturity date: 31-Dec-2016

Multiperiod Accounting Example: Loan Origination
Fees
Monthly Journal Entry for Loan Fee:
Entered DR (USD) Entered CR (USD)

Unearned Fee Income 50.00 0.00
Loan Fee Income 0.00 50.00
The unearned fee income must be split over the life of the loan. Each portion must be
recognized as income in the corresponding accounting periods, between Jul-2016 and Dec-
2016. The amounts in each period would depend on the proration formula used.

Using Multiperiod Subledger Accounting Rules
Accounting Hub users can define subledger accounting rules to create the Multiperiod
accounting entries. For example:
Journal Line Rules Account Rules Usage

Unearned Fee Income Unearned Fee Income Account Journal line rule for deferral entry
 Side = Credit Used to generate a credit line to the
 Multiperiod Option = No
unearned fee income account
 Multiperiod Class = Loan Fee
The Entered Amount accounting attribute is

mapped to a source that provides the fee amount.
Loan Fee Income Loan Fee Income Account Journal line rule for recognition entry
 Side = Credit Used by the Create Multiperiod Accounting
 Multiperiod Option = Yes
process to generate future entries with
 Multiperiod Class = Loan fee
prorate amounts, such as the CR 50.00
(USD) in the preceding example
 Multiperiod Start Date = Origination date
 Multiperiod End Date = Maturity date
The Entered Amount accounting attribute is

mapped to a formula to prorate the fee amount.
Define a user-defined formula to calculate the total entered amount to be recognized from the
Multiperiod start date until the end of the current accounting period. Assign the formula to the
Entered Amount accounting attribute of the Loan Fee Income journal line rule.
The Create Multiperiod Accounting process calculates the entered amount for Multiperiod
entries as:
Entered Amount = Amount Returned by user-defined Formula - Multiperiod Recognized

Entered Amount
• The Multiperiod Recognized Entered Amount is calculated and stored in the

Accounting Hub data model as the total amount recognized for the transaction in prior
periods.
• The approach handles any rounding differences in prorated entered currency

amounts.

Nested Formula Definitions
Define a formula by using an existing user-defined formula to derive a value for a

subledger accounting entry.
Define the commonly used formulas and reuse them in other formulas for consistency
and ease of maintenance.
Complex formula example: To defer revenue recognition for loan origination fee over
the life of the loan:
Prorated fee = Fee / (Maturity date - Origination date + 1) * (Last day of current accounting period - Origination date + 1)
1. Create a complex formula to prorate the fee amount by number of days in each period.
2. Take the total fee amount and divide it by the number of days in the loan life to determine
a daily fee amount.
3. Multiply the daily fee amount by the number of days since loan origination to generate
the prorate fee amount to be recognized by the current period.

Create a Nested Formula
Define simple formula to calculate loan duration and days since origination and use
the formula in the prorated fee formula definition.
1. Create a user-defined formula to calculate loan duration.
2. Create another user-defined formula to calculate days since origination.

Create a Nested Formula
3. Create a formula to calculate the prorated fee amount using the above formulas.
a. In the Expression section of the prorated fee formula, click the Source button.
b. Search and select the formulas defined in previous steps to define the prorated fee
formula.
You can now use the prorated fee formula to derive the entered amount on the fee
revenue recognition multiperiod journal line.
Entered amount = Prorated fee - Multiperiod recognized entered amount

Summary

• Explain the accounting transformation process.
• List the key features of accounting transformation.
• Describe the implementation process of accounting transformation.
• Manage the accounting transformation Accounting Methods.
• Create and process accounting entries.
• List the optional manual features of subledger accounting.
• Explain the advanced features of subledger accounting.

7
Period Close Components

Objectives

• Describe the General Ledger accounting cycle
• Describe the Period Close monitors
• Open and close a period
• Discuss the Period Close components

General Ledger Accounting Cycle
Open period
Create, Import,
Close period and Reverse
Journals
Run Financial
Reports General Post Journals
Ledger
Review Review
Balances and Balances and
Perform Perform
Reconciliation Reconciliation
Run
Perform Revaluation
Consolidations and
Translation
The graphic in the slide depicts the General Ledger accounting cycle.
The General Ledger accounting cycle uses the following steps:
• Open an accounting period.
• Create manual journals, import subledger journals, and reverse accrual journals.
• Post your journal batches manually or automatically. Posting populates the GL Balances Cube
and the GL_Balances table.
• Review the balances created by the posted journals and reconcile the balances to your source
subledgers. Review and resolve subledger period close exceptions, if any.
• If multi-currency journals exist, run the period-end revaluation process. If subsidiary ledgers in
different currencies exist, run the translation process.
• If subsidiary ledgers exist, perform consolidation to the parent or corporate ledger.
• Produce financial reports and perform online inquiries to review current account balances.
• Close the current accounting period.
• Open the next accounting period.

Period Close Overview Workspace
Monitor various aspects of the business:
Feature Benefit
Close Status Provides insights on close readiness
Subledger Outstanding Transactions Promotes efficiency in tying up loose ends that impact accuracy
and completeness of accounting close
Translation Status Quickly highlights whether translated data is available and

current
Intercompany Period Provides a concise recap of completed intercompany
transactions
The table in the slide contains the features and the corresponding benefits of the Period Close
Workspace.
When you initially navigate to the Period Close function, an Overview workspace becomes available to
monitor various aspects of the business. These views give insight to ensure that everything is
completed before closing the period. It provides real-time visibility into the period close process from
your subledgers to your General Ledger across the entire enterprise.
Note: The subledger monitors and detail are applicable only to companies that have implemented
Oracle Cloud Financials. An Accounting Hub Cloud implementation does not include subledger
activities.
The various monitors are:
• Close Status: Provides high-level period status information for GL and subledgers along with
quick access to update the period status. You can view a period status by a single ledger or a
ledger set.
• Subledger Outstanding Transactions: Provides information about subledger transactions

that are Unaccounted, Accounted but not Transferred, in Error, and in Draft mode. Drilldown
to detail is also available.
• Translation Status: Alerts users to out-of-date translations by balancing segment value and
translation currency.

• Intercompany Period Status: If using intercompany periods, provides the status of the
periods. It also provides intercompany open transactions by intercompany transaction type
with drilldown to detail.

Period Close Components
The Period Close workspace includes the following components:

• Accounting Periods
• Multicurrency
• Balances Transfer
• Year-End Processing
The Period Close workspace centralizes all the components needed to effectively close a GL period in a
timely manner. The components are:
• Accounting Periods: The two functions that are available to dynamically change the status of
a period are:
- Manage Accounting Periods: Used to view and change the status of accounting
periods by ledger
- Close Monitor: Used to view the status of an accounting period by ledger set and
edit the status of an accounting period by ledger
• Multicurrency: Used to process the multicurrency transactions that are needed before
closing a period. Multicurrency includes:
- Revalue Balances: The process to revalue unrealized balances at the end of the
month
- Translate Balances: Used to translate the ending balances of a ledger before
consolidation
- Manage Currency Rate: Used to input currency rates for the daily, period end, and
historic rates needed for the revalue and translation processes
- Create Income Statement Closing Journals
- Create Balance Sheet Closing Journals

• Balance Transfer: Used to transfer balances from a primary ledger to a secondary ledger.
This is needed only if this is not set up to occur automatically at the posting of the primary
ledger.
• Year-End Processing: Two functions are available for countries requiring their financial
statements to be closed:

Open and Close Period Statuses
An accounting period can be:

• Open
• Closed
• Permanently Closed
• Future Enterable
• Never Opened
The screenshot in the slide shows the Accounting Period Statuses page.
Navigate to: General Accounting > Period Close > General Ledger (Open).
The accounting period statuses are:
• Open: All eligible journals can be entered, imported, and posted. An unlimited number of
periods can be opened but doing so may confuse users entering journals.
• Closed: No journals can be entered, imported, or posted. You can reopen closed periods if
you need to enter and post any journals.
• Permanently Closed: No journals can be entered, imported, or posted. Periods cannot be

reopened. Use this status only to archive old data.
• Future Enterable: Journals can be entered and imported but cannot be posted. You specify
in Ledger Options the number of future periods from the most current open period. You can
change the number of Future Enterable periods at any time.
• Never Opened: The application sets all new periods to Never Opened until you change the
status.

Multicurrency Component
Process the multicurrency transactions that are needed before closing a period.
Multicurrency includes:
• Revalue Balances
• Translate Balances
• Manage Currency Rate
• Revalue Balances: The process to revalue unrealized balances at the end of a month
• Translate Balances: Used to translate the ending balances of a ledger before consolidation
• Manage Currency Rate: Used to input currency rates for the daily, period end, and historic
rates that are needed for the revalue and translation processes

Revalue Balances Overview
The process of adjusting the accounted value of foreign currency denominated

balances according to current conversion rates. Revaluations:
• Represent the difference in the value of a balance due to changes in conversion rates
between the date of the original journal entry and the revaluation date
• Post as adjustments through journal entries to the underlying account with the offset
posted to an unrealized gain or loss account

Revaluation Process
The graphic in the slide illustrates the revaluation process.
Prerequisites:
• Define an unrealized gain/loss account.
• Define a period end rate type and create a period end rate for each currency if required.
Running a Revaluation:
• Revaluation is run at the end of each accounting period as part of the close process to revalue
the balance sheet accounts that are denominated in a foreign currency in accordance with
SFAS 52 (US).
• The journal is then reversed at the beginning of the next period.
• The process is repeated until the transactions are settled.
• The Realized Gain/Loss is recorded in the appropriate subledger and transferred to Oracle
General Ledger at the time the obligation is settled.
Currencies:
• Revaluation can be run for a single foreign currency or for all currencies.
• When you run revaluation, General Ledger creates a revaluation batch that contains a separate
journal entry for each revalued foreign currency.

Revaluation Example
The graphic in the slide is an illustration of a revaluation with unsettled Receivables foreign currency
denominated balances.
At the end of the accounting period, the revaluation process creates an unposted journal to record the
change in the converted balances to the Unrealized Gain/Loss account. The journal is posted, and
then reversed at the beginning of the next reporting period. In this example:
• The original journal entry in Euro remains the same
• At period end, the exchange rate has changed to 1.2885
• The receivable is still 10,000 Euro, but is now $12,885 US Dollars
• The offset of $100 is recorded in the Unrealized Gain account
Note: A similar process may be run for unsettled Payables foreign currency denominated balances as
well.
General Ledger creates the revaluation adjustments in your ledger currency. It automatically defines
the reversal period for your revaluation journals if the category has been set to automatically reverse.

For Average Balance Ledgers:
• When you revalue balances in an average balance ledger, General Ledger revalues only actual
balances.
• When you post the revaluation journal entries to update your standard balances, the system
recalculates your average balances automatically.
For Reporting Currency Ledgers: Under the SFAS 52 re-measurement (temporal method translation),
it is necessary to re-measure the foreign currency gains or losses recorded in your primary ledger
currency and record the gains or losses in the reporting ledger currency.

Translation Overview
Process of converting accounted balances from one currency to another target

currency:
Running a Translation:
• Restates the primary ledger currency account balances into a reporting currency ledger with the
balances conversion level
• Translates actual balances from ledger currency to foreign currencies for online inquiries,
reports, and consolidations
• Supports multiple balancing segments for the Retained Earnings and Cumulative Translation
Adjustment accounts
• Is done after you have completed all journal entries for an accounting period
Retranslate if you post additional journal entries or change your translation rates after running translation
for a period.

Translation Conversion Rates by Account Type
Account Type Conversion Rate Type

Revenue and Expenses Daily Rates – Period Average Rates
Balance Sheet – Assets and Liabilities Daily Rates – Period End Rates
Balance Sheet – Owner’s Equity Historical Rates
The table in the slide lists the account types and the corresponding conversion rate types.
Use the Manage Currency Rates function to maintain all conversion rates. All daily rates and historical
rates can be imported through a spreadsheet interface or through an interface table.

Consolidation Methods
The graphic in the slide depicts the three consolidation methods.
Select the best Oracle Accounting Hub Cloud consolidation solution for your enterprise:
• Reporting Only Consolidations: If your subsidiaries and your corporate ledger share the
same chart of accounts and calendar
• Balance Transfer Consolidations: If your subsidiaries and your corporate ledger have either
different chart of accounts or calendars, or both
• Financial Management Consolidations: If complex factors exist in your financial

consolidation requirements such as:
- Complex company structures such as joint ventures, minority interest holdings,

partially or fully owned subsidiaries
- Multiple heterogeneous systems, including non-General Ledger data sources that

are required to support non-financial or industry-specific metrics, disclosures, and
footnote schedules

Reporting Only Consolidation Method: Example
The graphic in the slide depicts how Vision Corporation uses the Reporting Only consolidation method.
To use the Reporting Only method, Vision Corporation uses secondary ledgers and reporting currencies
to align all ledgers to the corporate chart of accounts, calendar, and currency. Vision Corporation then
groups the primary and secondary ledgers that share the same chart of accounts and calendar in a
ledger set.
• The Vision Corporate ledger is an elimination ledger to hold elimination entries.
• Financial Reporting functionally is used to create the consolidation reports.
All subsidiaries and your corporate ledger share the same calendar.
The Vision UK subsidiary has a local chart of accounts and local currency. This subsidiary uses a
secondary ledger to record balances in the corporate chart of accounts and the corporate currency.
The Vision Canada subsidiary has a local currency and uses the reporting currency functionality to
record balances in the corporate currency.

With the Reporting Only consolidation method, perform the following tasks:
• Translate balances to the corporate currency for ledgers that are not in the corporate currency.
Include these ledgers in the ledger set. In the example, the reporting currency and the
secondary ledgers are included in the ledger set.
• Create eliminating entries.
• Report by using the ledger set and the corporate currency as parameters to view the
consolidated balances.

Balance Transfer Consolidation Method
The graphic in the slide shows how Vision Corporation uses the Balance Transfer consolidation method.
If multiple subsidiaries and the corporate ledger do not share the same chart of accounts and calendar,
use the Balance Transfer consolidation method and the reporting solutions listed in the graphic in the
slide.
Perform the following to use the Balance Transfer consolidation method:
• Translate balances to the corporate currency for ledgers that are not in the corporate currency.
• Create a chart of accounts mapping to map subsidiary account values to the corporate chart of
accounts.
• Transfer balances from the subsidiaries to the corporate consolidation ledger.
• Run the Transfer Ledger Balances process, which transfers between any source and target
ledger pair, or the Balance Transfer process for Balance Level secondary ledgers.
• Create eliminating entries by using journal entries or the Calculation Manager in the corporate
consolidation ledger.
• Generate a report on the consolidated balances net of eliminations in the corporate

consolidation ledger.

Oracle Hyperion Financial Management Integration
Overview
The graphic in the slide illustrates how the Oracle Hyperion Financial Management application integrates
with various ERPs.
To integrate to Oracle Hyperion Financial Management through the Enterprise Resource Planning (ERP)
Integrator, perform the following steps:
• Use the integration to bring General Ledger balances to Oracle Hyperion Financial
Management to perform complex consolidations.
• Drill through from Oracle Hyperion Financial Management to Oracle General Ledger and Oracle
E-Business Suite General Ledger balances.

Summary

• Describe the General Ledger accounting cycle
• List the Period Close monitors
• Open and close a period
• Discuss the Period Close components

8
Configuring Financial Reporting

Objectives

• Describe the features of the Financial Reporting Center.
• Describe Smart View key features.
• Create financial reports using the Financial Reporting Web Studio.
• Understand Infolets and Account Groups.
• View an account group and use the Sunburst visualization tool.
• Discuss Oracle Transactional BI reports.
• Understand BI Publisher reports.

The Financial Reporting Center with General Ledger
Overview
The graphic depicts the various reporting tools available for Cloud Financials.
The Financial Reporting Center is intended to be the primary user interface for General Ledger
reporting. The Financial Reporting Center:
• Offers state-of-the-art reporting and analytics capabilities.
• Reports from the Oracle General Ledger Balances Cube (GL Balances Cube) for consistent,
timely, and accurate information for all users.
• Retrieves results from the report objects and definitions stored in the Enterprise Performance
Management System Workspace, Fusion Edition (EPM Workspace) under the BI Catalog for
Financial Reports.
Financial Reports are read from Shared > Custom > Financials and My Folders. All other report types
can be saved anywhere in the BI Catalog, however, any custom content should be in the Shared >
Custom folder. It is also possible to create sub-folders within the Shared > Custom > folder.
Includes access to these types of reports:
• Financial Reports: Reports built off the Oracle Financial Reporting Web Studio using data in
the Oracle General Ledger Balances Cube. For example, company income statements and
balance sheets. These reports are mainly run by users in General Ledger.

• Account Groups and Sunburst: Used to monitor key accounts in General Ledger. When a
user creates an account group it becomes visible in the Financial Reporting Center with the
Sunburst visualization tool. The Sunburst visualization tool enables you to interact with your
account balances across various business dimensions in order to view balances from different
perspectives. Account groups are only used in General Ledger.
• Smart View Reports: A multi-dimensional pivot analysis tool combined with full Microsoft
Office functionality as an add-in. Smart View enables you to interactively analyze your
balances and define reports using a familiar spreadsheet environment. These queries are
mainly for users in General Ledger. One user can upload a query using Workspace and then
from Financial Reporting Center another user can download the query to their local drive for
use.
• Oracle Transactional BI Analyses: These analyses and reports are built off of transactional
tables using Subject Areas. These reports can be run by users in General Ledger, Payables,
Receivables, Cash Management, Intercompany, and so on.
• Oracle Transactional BI Dashboards: Dashboards put all the information, functions and
actions that a business user needs to do their job in one place. Dashboards are built off Oracle
Transactional BI objects like analyses and reports. These reports can be run by users in
General Ledger, Payables, Receivables, Cash Management, Intercompany, and so on.
• Business Intelligence Publisher Reports: Most of these reports are predefined and must
first be submitted and resubmitted to see the latest data by the Oracle Enterprise Scheduler
System (ESS) through the Scheduled Processes navigation. These reports can be run by
financials users.
Note: The icons in the graph are used in the Financial Reporting Center to represent each type of
report.

Other Reporting Interfaces Overview
The secondary user interfaces for financial users to access other reports are:
Other Reporting Interfaces Report Type

General Accounting Dashboard and Account Inspector Account Groups
Reports and Analytics Oracle Transactional BI Objects
BI Catalog All Report Types except BI Publisher Reports
EPM Workspace Reports, Books, Snapshot Reports, Snapshot Books,

Financial Reporting Batches, and Batch Scheduler
Enterprise Scheduler System (ESS) Oracle BI Publisher Reports
Even though the Financial Reporting Center is designed to be the main user interface for a financial
end user’s reporting needs, some users may choose to use any of the other interfaces for reporting in
financials such as:
• General Accounting Dashboard: Provides access to Account Groups and uses the Account
Monitor to efficiently monitor and track key account balances in real-time.
• Account Inspector: Perform ad hoc queries from account groups and financial reports
through drill down to underlying journals and subledger transactions.
• Reports and Analytics: This other reporting interface has a panel that reflects the folder
structure of the BI Catalog. Users can access and run any Oracle Transactional BI analysis,
report or dashboard. Users cannot run Financial Reports or BI Publisher reports from this
interface. This interface can be used by all financials users.
• BI Catalog: A component of the Enterprise Performance Management Workspace where you

can run all report types. You cannot run BI Publisher reports from here.
• EPM Workspace: Create Reports, Books, Snapshot Reports, Snapshot Books, Financial
Reporting Batches, and Batch Scheduler and schedule batches to automatically run and burst
to email.
• Enterprise Scheduler System (ESS): Only BI Publisher reports can be submitted from this
interface. Users access this interface by navigating to Tools > Scheduled Processes. Most
financial users have access to this interface to run standard reports for all the financial
applications.

Access to the Financial Reporting Center
The following user roles get access automatically:

• General Accounting Manager
• General Accountant
• Budget Manager
Other users must have the privileges added to their role.

Viewing Financial Reports from the Financial
Reporting Center
Financial Reports are:
• Balance Sheets
• Income Statements
• Cash Flow Statements
Navigate to: Financial Reporting Center > Search for Balance Sheet > Open > OK
Financials users use the Financial Reporting Web Studio to access and run all of their financial reports.
In Oracle Financials Cloud, financial reports are any reports designed or created in the Oracle Financial
Reporting Web Studio. Financial Reporting Web Studio reports must be saved in the My Folder
directory or Shared Folder/Custom/Financials directory before they can be accessed in Financial
Reporting Center. This constraint only applies to Financial Reporting Web Studio reports, not to other
types of reports.

Live Reports and Published Snapshot Reports
Boardroom-Ready Financial Reports

• Multiple output options including PDF, HTML, and Excel.
• Live reports are interactive and the data can be refreshed dynamically.
• Published snapshot reports have static data.
• Ability to expand parent values to view the next level of the hierarchy within the
reports.
• Drill down to underlying journals and subledger transactions.
Run boardroom-ready financial reports displayed in a web page, PDF document or excel spreadsheet
with embedded charts and graphs.
There are two types of financial reports that can be run from the Financial Reporting Center:
• Live Reports: Are interactive and a user can change the user point of view or report
parameters and instantly refresh the results.
• Published Snapshot Reports: Are static and cannot be refreshed with new data. They are
literally a snapshot in time.
On both types of reports, users can expand on any parent to the next parent level and keep drilling
down through multiple levels of your hierarchy.
You can drill down to detail balances or use the account inspector to see the journal lines, and
subledger transactions.

Practice 12-1 Overview: Viewing a Financial Report
from the Financial Reporting Center
This practice covers Reviewing a Balance Sheet report from the Financial Reporting
Center.

Oracle General Ledger Balances Cube: Overview
Before creating financial statements or doing analysis on balances, it is useful to understand the
Oracle General Ledger Balances Cube (GL Balances Cube) and it’s dimensions.
The GL Balances Cube uses pre-aggregated balances. Unlike relational database systems with many
narrow tables, preaggregated data warehouses prejoin tables, creating fat tables with highly redundant
columns. This type of database precalculates totals to improve runtime performance.
A new standard balances cube is created automatically when an accounting configuration is submitted
for a primary or secondary ledger that uses a new unique combination of chart of accounts and
calendar.
A new balances cube is also created when a secondary ledger is added to an existing accounting
configuration and uses a new unique combination of chart of accounts and calendar. The balances
cubes are named after the chart of accounts they contain.
The balances cube:
• Is automatically updated by the following general ledger processes: posting, open period, and
translation.
• Consists of a set of defining business entities called dimensions.

Dimension Values in Reporting
You can derive different amounts to meet financial reporting requirements by using
various combinations of dimension members.
Dimensions are used in the following reporting tools and features:
• Financial Reporting Web Studio
• Smart View
• Live reports
Before a report or analysis can produce results, all the cube dimension’s must have a value. The value
can be defined in the report definition or at the time of submission.
Both the Financial Reporting Web Studio and Smart View offer a member selector to define the
dimension’s member values within the report or analysis.
When running a live report, a dimension is either:
• Selected as an initial prompt.
• Selected while viewing the results.

GL Balances Cube: Dimensions
Dimension Description
Accounting Period Based upon the calendar of the ledger or ledger
set. Report on years, quarters, or periods. If the ledger
tracks average daily balances, this includes an option
to select date.
Ledger or Ledger Set Used to select a ledger for the reporting. Multiple
ledgers may be in the same cube if they share a
common chart of accounts.
Chart of Accounts Segments Each segment from the charts of accounts becomes a
separate dimension organized by hierarchy. A default
hierarchy is provided that includes all segment values.
• The GL Balances Cube consists of a set of defining business entities called dimensions.
Dimensions are used when creating a report and in many cases when running a financial
report.
• The table details in this slide and the next show the dimensions that are available for creating
financial reports using multidimensional cubes.
• Dimensions are seeded and new ones cannot be added.

GL Balances Cube: Dimensions
Dimension Description
Scenario Indicates whether the balances are actual, allocated, total for
allocations, encumbrance, budgeted, or forecast.
Balance Amount Indicates whether the value is a debit or credit, and whether it is
for the beginning balance, period activity, or ending balance.
Amount Type Indicates whether the amounts represent Base, Period to Date,
Quarter to Date, or Year to Date. If the ledger tracks average
daily balances, the amount type can be the period average
base, period to date, or quarter to date.
Currency Used to select the desired currency for the balances.
Currency Type Used to select the currency type of the balances. Available
options are entered, converted, or total.

Default Values
Many dimensions have default member values that can be used for a report or
analysis.
However, the following dimensions require a selected member value:
• AccountingPeriod
• Ledger
• Scenario
• Currency
• As previously stated, before a report or analysis can produce results, all the cube dimensions
must have a member value. Oracle provides a default member value for many of the
dimensions to simplify report writing and submission.
• However, AccountingPeriod, Ledger, Scenario, and Currency are defaulted with only a
placeholder and require that a member value be selected.
• If a member value is not valid or not defined then a financial report or Smart View query
returns #MISSING instead of a balance.
• The next several slides detail the dimensions, the possible values, if the default value is
required to be selected or what the default value is equivalent to and any additional
information about the dimension. For example, the Balance Amount dimension has a default
value called Balance Amount which is equivalent to the Ending Balance (net) member value.

Dimension Values and Defaults
Dimension Possible Default Value Additional Information

Values
Accounting • Years Must select a Without the Accounting Period, the
Period • Quarters value financial reports, Smart View queries, and
• Monthly Account Inspector display #MISSING.
• Weekly
• Daily
Ledger • Ledgers Must select a Without a Ledger or Ledger Set, the
• Ledger Sets value financial reports, Smart View queries, and
Account Inspector display #MISSING.
Chart of Each segment There is a separate dimension for each
accounts has a default segment of the chart of accounts used by
dimensions account the cube.
hierarchy with Hierarchies published to the GL Balances
detail values. Cube from the Publish Account
Hierarchies process are included.

Dimension Possible Default Additional Information

Values Value
• Actual Must select a Additional scenario values of Budget, Forecast Q1,
• Budget value and Forecast Q2 may be added to the Accounting
• Forecast Scenario value set. These additional values are
published to every cube.
Amount Type • Base Amount Type, Base is necessary because this is the value used to
• PTD which is the store all balances posted at the lowest level.
• QTD equivalent of PTD, QTD, and YTD are calculated values.
• YTD Base
Currency All ISO Must select a Without a currency, the financial reports, Smart
currencies value View queries, or allocation display #MISSING.
Note: Do now select Allocated or Total for Allocated as the value for Scenario.

Dimension Possible Values Default Value Additional

Information
Balance • Balance Amount Balance
Amount • Beginning Balance Dr Amount, which
• Beginning Balance Cr is equivalent to
• Beginning Balance (net) the Ending
• Period Activity Dr Balance (net)
• Period Activity Cr
• Period Activity (net)
• Ending Balance Dr
• Ending Balance Cr
• Ending Balance (net)
Currency • Total Currency Type,
Type • Entered which is the
• Converted From equivalent of
Total

Smart View Overview
With Smart View you can create:

• Ad Hoc Analyses.
• Financial reports using the Query Designer.
Smart View is a multi-dimensional pivot analysis tool combined with full Microsoft Office functionality
as an add-in. Smart View enables you to interactively analyze your balances and define basic financial
reports using a familiar spreadsheet environment. These queries are mainly for users in General
Ledger. One user can upload a query using Workspace and then from Financial Reporting Center
another user can download the query to their local drive for use.

Ad Hoc Analysis
Use Smart View functionality with Excel spreadsheets to:

• Retrieve and analyze data by selecting members.
• Perform a variety of operations, including formatting and designing your reports.
• Use functions.
A Smart View analysis allows you to:
• Drag dimensions to rows or columns.
• Perform multidimensional analysis, pivoting, and drill down.
• Drill from any parent to the next parent level within Excel.
• Drill to detail balances, journal lines, and subledger transactions.
• Utilize Excel’s built-in features including calculations and graphs.
• Save reports and queries offline, and then reconnect to live data by accessing the
spreadsheet.
• E-mail the spreadsheet to distribute reports.
Note: If you are familiar with the dimensions and members of your database, you can use a free-form
mode by typing dimension and member names directly into cells to design and create an ad hoc grid.
Optionally, your reporting administrator can upload to new Financial Reporting Center for other users
to use as a template.

Query Designer
Create financial reports such as Income Statements and Balance Sheets for internal
use.
Use Smart View functionality with Excel spreadsheets to:
• Retrieve and analyze data by selecting members.
• Perform a variety of operations, including formatting, graphing, and drilling through.
The Smart View Query Designer is a tool that is used to create basic financial reports such as Income
Statements and Balance Sheets. The reports designed in Smart View are recommended to only be
used internally. Boardroom ready financial reports should be defined through the Financial Reporting
Web Studio.

Creating Financial Reports
• Design traditional financial report formats such as balance sheets, profit and loss
statements, and cash flow reports.
• Design nontraditional reports for financial or analytic data that include text and
graphics.
Note
• The material presented in this lesson is an introduction to creating reports.
• More information can be found in the Oracle Hyperion Financial Reporting Web Studio User's.

Creating Financial Reports
• Design traditional financial report formats such as balance sheets, profit and loss
statements, and cash flow reports.
• Design nontraditional reports for financial or analytic data that include text and
graphics.
Note
• The material presented in this lesson is an introduction to creating reports.
• More information can be found in the Oracle Hyperion Financial Reporting Web Studio User's
Guide.

Financial Reporting Web Studio Overview
The Financial Web Reporting Studio enables report authors to use a graphical report
layout with report components, such as text boxes, grids, images, and charts, to design
reports.
Benefits include:
• Single Sign-On support and no longer having to install additional client software.
• Ability to edit existing reports using the Windows or web version of Financial
Reporting Web Studio.
The Financial Reporting Web Studio is a client based financial report definition tool that:
• Uses drag and drop functionality to create a grid to design the rows, columns and pages of
the financial report.
• Has additional report components such as text boxes, images, and charts that may be
included on a report.
• Contains grids and other objects that are reusable across multiple reports.
• Uses the GL Balances Cube dimensions on either rows, columns, pages, or Point of Views
(POV).
• Allows rows and columns that can be either data, formulas, or text.
• Can include calculations or mathematical functions.

Financial Reporting Web Studio
Use the Financial Reporting Web Studio to:

• Create and edit reports.
• Select toolbar buttons or menu commands to add report components to the report
body.
• Do standard formatting.
• Preview your report in print preview, PDF or HTML.
After launching the Financial Reporting (FR) Web Studio, window opens that is used to create new
reports or open an existing report definition to edit it.
The FR Web Studio has the toolbar and menu commands needed to create or edit reports. The toolbar
includes all the components of the report and all the standard formatting functions.
The FR Web Studio creates a report palette where all the components are placed.
The FR Web Studio also enables you to preview the report in print preview, PDF, or HTML.

Financial Reporting Web Studio Layout
25
Navigate to: Others > Financial Reporting Center > Tasks panel tab > Open Workspace for Financial
Reports > Tools > Launch Reporting Web Studio….

FR Web Studio’s Standard Toolbar
The Standard toolbar contains shortcuts to standard features.

Button Description
New Report Opens a report palette
Open Opens the dialog box to select an existing report
Save Saves a report or object in the repository
Repository Opens the repository
Print Opens the print dialog box
Print Preview Displays the active report in the print preview window
Web Preview Displays the active report in a web browser
The table lists the Standard toolbar buttons and corresponding descriptions.
You can use the View menu to display or hide the Standard toolbar.

FR Web Studio Components
Component Description
Header An area where you can display text on each page of a report. You can add other report objects
to a header.
Text Box A report object that can contain text, or functions that retrieve data such as report setting,
data values, point of (POV) values, or dimension members.
Grid A report object in which retrieves data in the rows, columns, and page axes.
Chart A report object that displays data from a specified grid. Charts are graphical representations
of the data in a grid.
Image A report object that contains a graphic or an image file, which can be included in the
following formats: .gif, .jpg, .ico, cur, and .bmp. You can add images to the body of the report
or to a header or footer. Note: (.bmp) images greatly increases the size of your report and
may affect performance.
Footer An area where you can display text on each printed page of a report. You can also add images
to a footer.
The table lists the components and descriptions of the Financial Reporting Web Studio tool.

FR Web Studio Components
Component Description
Row A horizontal display of information in a gird. A row can contain text, data, or derived data
from a calculation. You can format individual rows in girds.
Column A vertical display of information in a grid. A column can contain text, data, of derived
data from a calculation. You can format individual columns in girds.
Page The third intersecting reference on a grid report object. A page repeats the data on the
row and column over multiple members of additional dimensions. You can define
members on a page or show different views of data without rerunning the report.
Cell An intersection of a row, column, page, and POV for a grid. Note: You can format
individual cells in a grid.
The table lists the components and descriptions of the Financial Reporting Web Studio tool.

FR Web Studio Toolbar
The FR Web Studio toolbar contains shortcuts to report objects.
Button Description
New Grid Inserts a new grid on the report palette
Text Box Inserts a text box on the report palette
Image Inserts an image on the report palette
Chart Inserts a chart on the report palette
The table lists the Designer toolbar buttons and corresponding descriptions.
You can use the View menu to display or hide the Designer toolbar.

Grids
Grids are the foundation for a financial report and extract data from the GL Balances
Cube.
A grid is the foundation for a financial report. It is a graphical representation of components that
extracts the data from the GL balances cube. When you add a grid to the report palette, you log in and
connect to a GL balances cube. There are 4 basic components on a grid:
• Point of View Dimensions: You select which Point of View (POV) dimension to include on the
rows, columns, and pages. All the GL balances cube dimensions are always in a POV. A POV is
either at the grid or user level. This chapter covers the difference between grid POV and user
POV later on.
• Rows: For most financial reports rows usually are defined with account numbers, so you could
select the Account dimension where an account number would be the member. You would
then select which account numbers go on each row. However, other dimensions can be
selected.
• Columns: For most financial reports columns are usually defined with accounting periods, so
you would select the Accounting Period dimension. However, other dimensions can be
selected.
• Pages: A common selection for page dimension is the balancing segment or company. If your
company has more than company, the report results with a page per company.

With grids you can also:
• Include more than one grid on the report palette. One report can then extract data from more
than one data source.
• Use an existing grid to reuse the preformatted design.
• Select the members of the dimensions.
• Use formulas, functions and text to define the grid content.

Practice 12-2 Overview: Defining a Grid

• Defining a new report and grid.
• Selecting the point of view dimensions for the grid.
• Selecting account dimension members.
• Saving a report.

Defining Formulas
The formula bar:

• Is centrally located below the tool bar and resembles the formula bar in Excel.
• Allows for dynamic selection of functions from a drop-down list.
• Contains a field for the entry of formulas.
• Permits defining, editing, and deleting of formulas in a cell’s column or row.
• Validates the syntax of the formula.

Available Formulas
From the Formula drop-down list, you can choose:
Formula Formula Formula Formula

Abs() Eval() Random() VariancePercent()
Average() IfThen() Rank()
AverageA() Mod() Round()
Cell[row.col] Max() Row()
Column[] Min() Sort()
Count() PercentOFTotal() Sum()
CountA() Pi() Truncate()
Difference() Product() Variance()
For example, use the Sum() formula to calculate total expenses. The syntax for the formula includes
the row numbers to be summed up.
If the rows are contiguous, the following syntax is allowed: Sum([3:5]). The rows 3, 4 and 5 are included
in the calculation.
If the rows are not contiguous, for example, Subtotals or you need to sum up Total Revenue and Total
Expenses, then the following syntax would be used: Sum([1],[6]).
Note: For more details on the available formulas, see the Oracle Hyperion Financial Reporting Web
Studio User's Guide.

Practice 12-3 Overview: Adding a Formula for Total
Expenses

• Adding a formula for total expenses.
• Validating the formula syntax.

Using Functions: Range
When using the range function, you must:

• Define the StartMember.
• Specify the Offset number.
• Define the EndMember.
Functions can be used on a dimension if a specific member value is not used. Functions give more
flexibility to the report for returning the desired data. Since this is only an Introduction to the Financial
Reporting Studio more information can be found in the Oracle Hyperion Financial Reporting Web
Studio User's Guide or by taking one of these Oracle University courses: Oracle Hyperion Financial
Reporting for Essbase and Planning or Oracle Hyperion Financial Reporting for Financial Management.
The range function is useful for creating multiple columns or rows of data with one initial setup. For
example, your company requires a rolling 12 Period Income Statement. Use the range function on the
Column AccountingPeriod dimension to achieve this. When using the Range Function, you must:
• Define the StartMember.
• Specify the Offset Number.
• Define the EndMember.
For this example, the Startmember would use another function called RelativeMember. The
RelativeMember would be defined as Current Point of View. Next, you would need to specify the
Offset. The Offset can be a positive or negative number. If you used -12 then the first column on the
report would display 12 periods back from the Current Point of View. The Current Point of View is the
period the report is targeting. For example, If you want to see a report from Jan-14 through Dec-14
with Dec-14 as the “Current Point of View” you would need to define the EndMember or the last
column in the range as Current Point of View.

Practice 12-4 Overview: Defining a Rolling 12-Period
Column
This practice covers using the range function to create a rolling 12-Period column.

User and Grid Point of View Dimensions
Navigate to: Others > Financial Reporting Center > Tasks panel tab > Open Workspace for Financial
Reports > Tools > Launch Financial Reporting Web Studio.
All remaining dimensions are represented either in the grid POV or the user POV.
• If a dimension is in the grid POV then the members selected only apply to that 1 grid.
• Dimension members in the user POV apply to all grids on the report.
The AccountingPeriod dimension in the screenshot is in both the grid POV and the user POV.
• On the grid POV the member value is User Point of View for AccountingPeriod. That member
value makes the AccountingPeriod visible on the user POV.
• The member selected for AccountingPeriod on the user POV is 12-14 which means all grids on
the report return results for 12-14.
All dimensions on the grid are either on a Row, Column, Page, or the grid POV. Dimensions are only
visible on the user POV bar if they meet the following conditions:
• Dimensions not currently defined on a row, a column, or a page.
• Dimensions on a row, a column, or a page that are flagged for the Current POV like the
AccountingPeriod dimension above.
• Dimensions without a member selected on a grid POV. The system defaults the User Point of
View.

• The Ledger dimension in the screen shot is on the Grid POV with a member Value of US
Primary Ledger. Therefore, that dimension is not visible on the User POV. It has been defined
at the Grid level
• Dimensions without a member selected on a grid POV. The system defaults the User Point of
View.
• The Ledger dimension in the screen shot is on the Grid POV with a member Value of US
Primary Ledger. Therefore, that dimension is not visible on the User POV. It has been defined
at the Grid level

Selecting Members
Use the Select Members dialog box to select members:

• Member Value
• Prompt
• Same As
• Current Point of View
• User Point of View
The following choices are available when selecting a member for a dimension:
• Member Value: the specific value or values stored in the GL Balances Cube. For example, the
member value for the Account Dimension would be an account number.
• Prompt: At runtime, the user must select a member or members for the report to run. The
report itself can contain a default member which the user can accept or change. Prompt also
enables the report writer to filter the dimension members from which the user can select
when running the report.
• Same As: Creates a column or row member selection with the same member selection setting
as another column or row.
• Current Point of View: Acts as a variable that employs the POV to specify the member of a
dimension when the report is run.
• User Point of View: Defaults on the dimension when no member is selected. After the report
is generated, the parameters can be modified by the end user.

Practice 12-5 Overview: Defining the Grid and User
Point of View Dimensions

• Defining the Grid and User Point of View Dimensions.
• Setting up the Grid Point of View.
• Setting up a Prompt for a Point of View Dimension.

Property Sheet
Use the Property Sheet to set various options for a report component:
• Grid
• Page
• Heading Row
• Chart
Use the Property Sheet to set various options for the currently selected report component.
The property sheet features change based on the report object selected and are unique to the selected
report object. There are several objects available, depending on the type of report component selected.
By default, property sheets are displayed on the right side of the designer. You can hide the property
sheet window.
• To hide a property sheet that is displayed, deselect View menu > Property Sheet.
• To display a properties sheet that is hidden, select View menu > Property Sheet.

Property Sheet Component Objects and Features
Object Features
Grid General: Database Connection; Headings for Member Labels; Autosizing;
Drill Through; Suppression: Suppress If Zero, If Missing, and If Error; Text
Options for Zero Values, No Data and Error.
Page Member Labels: Member Name, Alias: Default or Both, Heading Height,
Page Printing Positioning.
Heading Row Headings Member labels: Member Name, Alias: Default or Both, Allow
Expansion, Auto Calculation.
Chart A report object that displays data from a specified grid. Charts are graphical
representations of the data in a grid.
The above table is just a small sampling of the available objects and associated features. More
information can be found in the Oracle Hyperion Financial Reporting Web Studio User's Guide or by
taking one of these Oracle University courses: Oracle Hyperion Financial Reporting for Essbase and
Planning or Oracle Hyperion Financial Reporting for Financial Management.

Practice 12-6 Overview: Setting Properties

• Setting the Grid Properties.
• Setting the Page Properties.
• Setting the Heading Row Properties.

Text Box Objects
Text box objects allow you to:

• Enter text or text functions.
• Move, resize, or reposition the text box.
• Set the border, shading, and positioning.
• Store them in the repository.
Text box objects can contain text or text functions. For example, you can enter a label, a description, or
a function that retrieves the current date in a text box. You can also copy text from a word editor.
You can add text boxes to the header, footer, and body of the report.
A text box object can be saved in the repository and then be used on numerous reports. For example,
you can use the same text box on all of your Balance Sheet reports to ensure consistency across all
companies.

Image Objects
Adding Images:
• Insert images into the header, footer, and body of a report.
• Support for multiple graphic formats.
Images are report objects that contain graphics. You can add images to the header, footer, and body of
the report. You can then resize, and position as needed.
You can include the following image formats in a report:
• Bitmaps: BMP and DIB
• Graphic Interchange Format: GIF
• Joint Photographic Experts Groups: JPEG and JPG
• Icon: ICO and CUR

Practice 12-7 Overview: Adding a Logo and Title

• Adding a logo.
• Inserting a title.

Reviewing a Report
You can preview the reports from the Financial Reporting Web Studio. Use the preview to ensure the
report is correct before making it available in Workspace.
When the report is saved to Workspace it must be saved as one of these two types:
• Live: A dynamic and interactive type of report. The user may select certain dimension values
either through a prompt or by clicking on the dimension after the report has run. The data
refreshes every time the report is run or printed.
• Snapshot: Reports that contain data retrieved at the time the report is saved as a snapshot.
The data in a snapshot report remains the same; changes in the database since the snapshot
was last saved are not reflected when it is previewed or printed. The user cannot select any
dimension values.
Once the report is saved in Shared Folders in Workspace it can be made available to users to run from
the Financial Reporting Center. If the report is designed with prompts, those prompts are displayed
when you preview or run the report. You must respond to the prompt and provide the requested
information by selecting members from the prompt list.

Practice 12-8 Overview: Reviewing a Financial Report

• Previewing a report in the Financial Reporting Web Studio.
• Making edits if necessary.
• Opening the report from the Financial Reporting Center.
• Drilling down to detail balances.

Infolets: Overview
• Monitor performance with user configurable interactive dashboards based on user-

defined Oracle Transactional BI reports.
• Drill from dashboards to detailed reports.
Navigate to: Welcome Springboard > Custom Infolets Dot.
Monitor performance with interactive dashboards based upon balances and supplemental information
such as targets and performance goals using highly configurable Oracle Transactional Business
Intelligence reports.
Drill from performance measures to details to investigate and analyze performance differences.

Account Groups: Overview
• Account groups are easy-to-use reporting components that save queries on account
balances requiring regular monitoring.
• The output from your rules can be displayed in:
– The Financial Reporting Center
– The Account Monitor
– General Accounting Infolets
With Account Groups, you define tolerance rules to create self-monitoring accounts. Tolerance rules
are set using criteria comparing two balances. The comparison looks for an increase or decrease that is
above or below a percentage or constant amount threshold. When the criteria are met, the output is
can be displayed in:
• The Financial Reporting Center: The results are viewed in either a table or the Sunburst
feature.
• Account Monitor: From the General Accounting Dashboard.
• General Accounting Infolets: Can be viewed on either the Allocation, Expenses or Revenue
General Accounting Infolets.
There are additional enhancements and features in Account Groups including the ability to:
• Share your account group with other users.
• Use the account group interchangeably for all ledgers that belong to the same balances cube
containing the new option to dynamically derive the ledger for the query.
• Label each account group row with a short name that is easily recognizable in the infolet
details.
• Support for additional comparison options including Not Equal and Equal.

Viewing Account Groups in the General Accounting
Infolets
Automatically Included with Setup
Infolet
Available Shipped Job Roles Needed
Financial Analyst
Revenues Yes General Accountant Yes
General Accounting Manager
Financial Analyst
Expenses Yes General Accountant Yes
Financial Analyst
Allocations Yes General Accountant Yes
With the General Accounting Infolets you can display the account group results for revenue, expense,
and allocation information. Before the account group-based infolets are set up, a link appears on the
infolet that is used to open the setup page. For example, the link that appears on the Expenses infolet
says: Set up Expense Accounts.
You can also setup the account groups from the Account Monitor in the General Accounting
Dashboard.
The infolet names are derived from the account group names. You can override the name for your
infolet using Edit Title > View on the Action menu. You can give each account group row a short name
that is displayed in infolet details.
The signage display options are applied to the Account Monitor display. Define the signage options by
clicking on the down arrow next to your user name > select the: Setting and Actions menu > Set
Preferences For the infolets, the signage is already set to show:
• Revenue amounts as a positive when the balances are a credit (CR).
• Expense accounts as a positive when the balances are a debit (DR).

Defining Account Groups: Header Region
The account group mechanism provides an easy-to-use and highly configurable tool to determine
what is displayed in the Revenues, Expenses and Allocations infolets.
In the header region, specify these elements:
• Name and Description: Provide a meaningful name and description. If being used on an
infolet, the infolet name is derived from the account group name.
• Display in: Determines where the account group is viewed. The choices are:
- Account Monitor: The account group is visible in the financial reporting center and
the account monitor.
- Allocations: The account group is displayed in the allocations infolet, the financial
reporting center, and the account monitor.
- Expenses: The account group is visible in the expenses infolet, the financial
reporting center and the account monitor.
- Revenue: The account group is visible in the revenue infolet, the financial reporting
center and the account monitor.

• Set as Default: Since there can be more than one account group, one account group must be
the default for each Display In type. The financial reporting center and the account monitor
can view more than one account group. The infolets can only view the one default account
group.
• Dynamically derive ledger: A account group can only be based on one chart of accounts. The
best practice is to have the same chart of accounts across ledgers, and then you can
potentially use the same account group across your ledgers. If you do not want to use an
account for all ledgers, add the specific ledger to each account group row. If you check this
option when setting up the account group:
- The application selects the ledger for you based on your selected data access set
and ledger.
- The ledger column in the account group row is not displayed.
• Time Option: To specify the target to evaluate the current performance against. The choices
are Accounting Period, Quarter or Year.
• Comparison Option: Determines the balance type the account group uses. The comparison
options are based on the Time Option chosen. You can select a budget, forecast, or prior
performance. Some of the choices are Budget PTD or QTD or YTD, Previous Period, Prior
Year PTD, QTD or YTD.
• Scenario: If the Budget Comparison Option is chosen, you must provide the budget scenario.
The choices are budget or forecast.
• Access:
- Private: Only the user that created the account group can access the account group
in infolets, the financial reporting center, and the account monitor.
- Public: This allows any user with proper security privileges to view the account group
in infolets, the financial reporting center, and the account monitor. Note: Only one
infolet account group can be public. If another user creates a new public account
group it replaces the first one created. Also, if a public account group exists and a
user creates their own default private infolet account group, their new private
account group infolet overrides the Public infolet account group just for that user.
- Shared: Allows the creator of the account group to select which users access. After
choosing the Shared Access, navigate to View > Manage to add the users to the
account group.

Defining Account Groups: Accounts Region
Every account group can have more than one account to monitor. You can use the same accounts on
more than one account group. For example, you might want to monitor 5 travel expense accounts two
different ways. One to compare current period to previous period and the other one to compare
current period to budget. Comparing in two time periods requires 2 different account groups using the
same 5 accounts but different header definitions.
The Account region contains:
• Account: An account combination based on a chart of accounts. The account can use either
parent values or detailed account values. If a parent value is used the user can drilldown to
detail.
• Change and Threshold: You can choose:
- Always Display a change: No threshold is required since this option always displays
the difference.
- Only display when there is an Increase or Decrease by amount or percent: Select

when the Threshold percent or amount is required.
- Not Equal: Required on the Allocations Infolet. The Threshold must be set to 0 to
enable the infolet to display accounts that have not been fully allocated.

Demonstration 12-9 Overview: Setting Up the
General Accounting Expense Infolet for All Users
This demonstration covers the following topics:
• Creating an public account group for the Expense infolet.
• Viewing the Expense infolet.

Generation of Reports and Account Groups Settings
• Tag the parent accounts that are your

highest level and comprehensive
revenue and operating expenses
accounts.
• Optionally, assign the expanded
account type of Expenses - Top Cost
of Sales Parent Account if this is
applicable.
In the Natural Accounts worksheet of the Rapid Implementation Enterprise Structure Setup
spreadsheet, you provide your natural account segment value set and account hierarchy along with
account type tags for the account values.
You also tag the parent accounts that are your highest level and comprehensive revenue and
operating expenses accounts.
Use the expanded account types of:
• Revenue - Top Revenue Parent Account
• Expenses - Top Operating Expenses Parent Account
Optionally, also assign the expanded account type of Expenses - Top Cost of Sales Parent Account if
this is applicable for your scenario.
The Generate Financial Reports and Account Groups process uses these parent accounts as the basis
for deriving the accounts that are referenced in the reports it creates.
The process:
• Takes the immediate descendants of these parent accounts to define the rows of the reports.
• Automatically generates a set of Financial Reporting reports and Account Groups according
to the accounting configuration defined in the Rapid Implementation spreadsheet after this is
successfully submitted.

Different variations of the Financial Reporting income statements are generated depending on
whether both the top operating expense and top cost of sales accounts are tagged.
If the optional top cost of sales account is provided, the income statements Financial Reporting
reports also include a gross margin section.

Generation of Reports and Account Groups
• An individual set of Financial Reporting reports is generated for each ledger that is
defined within that Rapid Implementation accounting configuration.
• Reports Generated include:
Rolling Monthly Income Statement

Income Statement
Trial Balances by Consolidated

Ledger Currency Income Statement
Trial Balances by Rolling Quarterly

Entered Currency Income Statement
• The process also generates three Account Groups.
The three Account Groups include two for the infolets, Revenues and Expenses, and one for the Close
Monitor, Close Monitor Summary Income Statement.
A set of these three account groups is generated for the balances cube, to be shared among all the
ledgers that are part of that balances cube.

Generate Financial Reports and Account Groups
Process
You can submit the process at any time to automatically create Financial Reporting
reports and Account Groups.
Pick the specific tree and tree version of the parent account that you wish to base the
generated reports on.
To submit the Generate Financial Reports and Account Groups process:
Select the chart of accounts and accounting calendar which identifies the balances cube and ledgers
for which you wish to generate the reports.
Specify the top three parent revenue and expenses account values to base the generated reports.
• Revenue - Top Revenue Parent Account
• Expenses - Top Operating Expenses Account
• Expenses - Top Cost of Sales Parent Account (optional)
The Generate Financial Reports and Account Groups process uses these parent accounts as the basis
for deriving the accounts that are referenced in the reports it creates by taking the immediate
descendants of these parent accounts to define the rows of the reports.
The process generates a set of Financial Reporting reports and Account Groups for the selected
balances cube and its ledgers.
Depending on whether both the top operating expense and top cost of sales accounts are tagged,
different variations of the income statements are generated. If the optional top cost of sales account is
provided, the income statement reports also include a gross margin section.
When specifying each of the top parent account, you can pick the specific tree and tree version of the
parent account that you wish to base the generated reports. Use the Search feature to look for the
specific parent account by one or more criteria, using value, description, tree and tree version

When specifying each of the top parent account, you can pick the specific tree and tree version of the
parent account that you wish to base the generated reports on.
Use the Search feature to look for the specific parent account by one or more criteria, using value,
description, tree and tree version.
Tips And Considerations
• When specifying the top parent accounts to submit the Generate Financial Reports and
Account Groups process, you can pick a specific tree and tree version for each parent
account.
• All three parent account values can be from different trees and tree versions, although ideally,
you would choose a common tree and tree version for all of them so that the hierarchy basis
of all the rows in the report is consistent.
• The Generate Financial Reports and Account Groups process creates an initial set of Financial
Reporting reports for each ledger included in the request submission.
• To prevent the unchecked proliferation of such Financial Reporting reports, unless the
original reports created were renamed or deleted, a resubmission of the report generation
process will not generate new Financial Reporting reports for the ledgers.
• In contrast, for Account Groups, a new set is generated for the balances cube with each
submission of the report generation process.
• The Revenues and Expenses Account Groups created by the report generation program are
automatically set as the defaults for your Revenues and Expenses infolets in the General
Accounting Home Page if there is no existing Account Group already associated as their
defaults.
• The Close Monitor Summary Income Statement, can be assigned to your ledger sets when
you complete the Close Monitor setup.
Role Information
You must have one of the following roles to submit the Generate Financial Reports and Account
Groups process:
• Financial Analyst
• General Accountant or General Accounting Manager
• Financial Application Administrator
• Application Implementation Consultant
You must have one of the following roles to work directly with the account groups and Financial
Reporting reports created:
• Financial Analyst, General Accountant or General Accounting Manager

Copy Account Group
• Make a copy of an existing account group.

• Modify to satisfy a different reporting requirement.
• Use the Copy Account Group feature to make a copy of an existing account group, which can
then be readily modified to satisfy a different reporting requirement by having another
Account Group variation.
• You can make a copy of any account group to which you have access, whether it is an
Account Group you own, an Account Group that is shared with you, or an Account Group that
is public.
• You are marked as the owner of the copied Account Group. The default is set to Private
Access but you can change it to a different setting depending on your requirements.

Viewing Account Groups from the Financial
Reporting Center
Account Group results can be viewed:
• As a table.
• In the Sunburst tool.
Navigate to: Financial Reporting Center > Search for an account group.
• Use the Account Group drop-down list to select other account groups.
• Change the Accounting Period in the drop-down list to compare results.
• Select Show/Hide Segments to add or remove segments from the table view.
• Select View as Sunburst to see the account group data in a graphical interface.

Sunburst Tool
The Sunburst visualization tool allows you to interact with your account balances
across various business dimensions in order to view balances from different
perspectives.
For example, you can view quarterly regional sales and identify sales trends that are visually
represented by size and color to indicate whether that region's sales increased or decreased over the
quarter.
• Each Sunburst ring represents a different segment of the accounting flexfield.
• The order of the rings is displayed on the control panel on the right.
• The controls can also be used to change which segments are displayed in the Sunburst.

Sunburst Icons
Use the icons to drill into and out of various segments.

• Move Ring Toward Center
• Move Ring Away from Center
• Keep Only
• Remove Only
• Zoom In
• Zoom Out
The Sunburst consists of colored concentric circles and the interactive controls and legends in the
panel on the right and the top left of the Sunburst.
• Each node, slice, or wedge represents a breakdown of the balances by the parent or child
segment values included in the account group.
• The width of the node represents the relative contribution of each segment value balance to
the total.
• The Sunburst emphasizes the most important contributors because they occupy more space.

Sunburst Options
Use the options on the right to further analyze

the account group data.
• Account Group selection drop-down list
• Accounting Period drop-down list
• Segment drop-down list
• Move and position arrows
• Colors selection boxes and thresholds
• Other Thresholds
• Reset
• The color of the nodes represents a comparison with the previous period or budget. By
default:
- Green implies increased revenue or decreased costs.
- Red implies decreased revenue or increased costs.
- Yellow represents little or no change.
• The colors and color thresholds can be changed using controls in the right hand panel.
• Contributions that are small relative to the total revenue and that result in very narrow nodes
are grouped into the Other node.
• The Other threshold, by default 2% of the circumference of the Sunburst, can be changed
using controls in the right hand panel.

Demonstration 12-10 Overview: Viewing an Account
Group from the Financial Reporting Center
• Searching for an account group.
• Viewing the results in the table view.
• Reviewing an account group in the Sunburst tool.

Demonstration 12-11 Overview: Generating Financial
Reports and Account Groups
• Submitting the Generate Financial Reports and Account Groups process.
• Viewing a Financial Report the process generated.
• Viewing the account groups the process generated.

Oracle Transactional Business Intelligence Overview
Oracle Transactional Business Intelligence (Oracle Transactional BI) is a set of highly interactive
reporting tools providing strategic insight into a business answering questions that are critical to
executives and manages for making responsible business decisions. It reports directly from the
transactional tables and returns the results in real time thus eliminating the need for a data
warehouse. You can access your finished Analyses, Reports, and Dashboards from the Financial
Reporting Center.
With Oracle Transactional BI developers and end users alike can create meaningful analyses and
reports eliminating the need for SQL skills and resulting in real time information using these tools:
• BI Composer: Allows users to create analyses and reports using graphs, charts, and tables.
• BI Answers: Allows developers to create analyses and reports using graphs, charts, and tables.
• BI Mobile App Designer: Allows developers to create analyses and reports using graphs,
charts, and tables for use on mobile devices.
From the analyses and reports, developers can then create:
• Dashboards: Allows users to access analyses, reports, links and so on, all in one place.
• Custom Infolets: Allows users to monitor performance using dashboards or other Oracle
Transactional BI objects.
Oracle Transactional BI uses the Oracle BI Catalog which is the same one as used by the Financial
Reporting Center’s EPM Workspace thus unifying the look and feel for the end-user.

Financial Reporting Center and Oracle Transactional
BI
From the Financial Reporting Center, you can access:
• Analyses
• Reports
• Dashboards

Oracle BI Publisher Overview
Enterprise reporting solution for authoring, managing, and delivering electronically or

through print all of your highly formatted documents, such as:
• Operational reports
• Electronic funds transfer documents
• Government PDF forms
• Checks
• A scalable solution for delivering high-fidelity, pixel-perfect reports in multiple formats, for
example, for tax auditing and fulfilling country-specific statutory requirements.
• Used to generate printable output that presents specific information from a predetermined
template, for example, for invoices, dunning letters, and other external-facing documents.
• Used for generating high-volume operational reports and production runs.

Oracle Business Intelligence Publisher: Overview
• Oracle BI Publisher provides many predefined or seeded reports for Oracle Cloud Financials.
Predefined BI Publisher reports for Oracle Financials Cloud are set up to be submitted as
scheduled processes through the Enterprise Scheduler System (ESS) in Oracle Cloud
Applications. The Open link, therefore, is not available by default for these reports in the BI
Catalog.
• Because it supports diverse document requirements with flexible customization capabilities,

developers can use layout editors to edit exiting layouts or create new layouts.
• BI Publisher can only use a layout to produce results. A layout determines the details, the
placement of data, and the look and feel of the output results.
• One BI Publisher report can support more than one layout allowing an end-user to obtain
different results as needed for the one or multiple data sources. Layouts generate high
fidelity, pixel-perfect reports to PDF, RTF, Microsoft Excel, Microsoft PowerPoint, and static
HTML.
• Also, at the time of submission, an end-user can choose to have the report produce multiple
outputs using different layouts at the same time. In other words, one submission can produce
the same report in PDF and another in HTML at the same time. Or one submission can
produce one report using layout1 and another using layout2 at the same time.
• Because BI Publisher uses XML technology, the report output delivery supports multiple
destination types, including printers, faxes, e-mail, and e-commerce.

Financial Reporting Center and Oracle BI Publisher
Easily access reports initially run from Scheduled Processes.
Navigate to: Tools > Scheduled Processes > Submit the Payables Invoice Register > Home > Financial
Reporting Center > Search for the Payables Invoice Register BI Publisher report.
• After a user initially submits a BI Publisher report from Scheduled Processes (ESS), they can
access the report from the new Financial Reporting Center. If the report is submitted again,
both the initial results and the new results are available by selecting the date and time from
the report’s History drop down.
• The report is only available in the Financial Reporting Center for the user that initially
submitted it.
• Note: After initially running the report from Scheduled Processes, you must also open the
document from the output region before it becomes available in the Financial Reporting
Center.

Summary

• Describe the features of the new Financial Reporting Center.
• Describe Smart View key features.
• Create financial reports using the Financial Reporting Web Studio.
• Understand Infolets and Account Groups.
• View an account group and use the Sunburst visualization tool.
• Discuss Oracle Transaction BI reports.
• Understand BI Publisher reports.

A
Additional Resources
Lesson Objectives

• Find additional application resources
• Use the Oracle Help Center to find additional information
• Access helpful video content to learn more about specific features
Oracle Financials Cloud: Accounting Hub Fundamentals A - 2

Oracle Cloud Implementation Resources
Classroom and Other Resources:

• Oracle Financials Cloud: Payables to Cash Management Implementation Student
Guide (this guide)
• Oracle Financials Cloud: Using Payables
• Oracle Cloud Applications Help in the Applications
• Oracle Technology Library on OTN
• My Oracle Support (MOS)
• Oracle Help Center
• Oracle Customer Connect
• cloud.oracle.com
• Oracle Technology Library on OTN: http://www.oracle.com/technetwork/index.html
• My Oracle Support (MOS) (https://support.oracle.com/), which includes the following

documents:
- Getting Started with Oracle Cloud Applications: Common Implementation, Article ID

1387777.1 on Oracle Support
- Oracle Cloud Applications: Financials Reporting (Document 1458904.1)
• Oracle Help Center (https://docs.oracle.com/en/), including the following Oracle Financials

Cloud books:
- Getting Started with Your Financials Cloud Implementation
- Implementing Accounting Hub
- Implementing Enterprise Structures and General Ledger
- Using Common Features for Oracle Applications Cloud (including infolet

personalization topics)
- Customizing the Applications for Functional Administrators (including infolet

customization topics)
- Using Oracle Social Network
- Security Reference for Oracle Financials Cloud

- Creating Analytics and Reports for Financials Cloud
- Administering Analytics and Reports for Oracle Financials
- Using Analytics and Reports for Financials Cloud
- Using General Ledger
- Using Hyperion Calculation Manager
- Using Hyperion Enterprise Performance Management Workspace
- Using Hyperion Financial Reporting
- Using Hyperion Financial Reporting Charting
- Using Hyperion Financial Reporting Mobile
- Using Smart View for Office
- Administering Essbase Administration Services
- Administering Essbase Administration Services Online Help
- Administering Essbase Database
- Administering Hyperion Enterprise Performance Management Workspace Enterprise

Oracle Help Center: docs.oracle.com
Oracle Help Center is:
• Central hub for all documentation and tutorials.
• Organized by major product categories including Cloud, Applications, Middleware, and

Database.

Cloud Application Services Pages
Links to application families and to Get Started.
Consistent organization, content, and link format for Cloud service pages: Friendly task panel to use to
change focus from Cloud to:
• Cloud Applications
• Cloud Intrastructure
• Cloud Platform
• Cloud Marketplace
• Cloud at Customer

Financials Home Page
The Financials Home Page in Oracle Help Center gives you access to:
• The ability to select your update.
• List of help topics by task.
• Links to videos and books (guides).
• Option to start your subscription.
• Links to the new features.

Video Subject Areas in the Oracle Help Center
The Videos are grouped by these categories:

• Get Started
• Specific Videos on how to use each Financial application
• Implement
• Configure and Extend
• Analyze and Report
• Other Playlists
Link to the videos: https://docs.oracle.com/en/cloud/saas/financials/19c/videos.html
Accounting Hub and Subledger Accounting include the following videos:
• Register a source system.
• Upload transaction data for accounting.
• Create a journal line rule.
• Create account rules and mapping sets.
• Create descriptions with a custom formula.
• Create supporting references.
• Create a journal entry rule set.
• Create an Accounting Method.
• Use the supporting references report.
Note: New videos are constantly being added.

Reference Guides
• File Based Data Import includes links

to:
– Spreadsheets templates
– Load and import processes
• Tables and Views includes:
– Columns
– Primary and Foreign Keys
– Indexes
• SOAP (Simple Object Access Protocol)
Web Services
Navigate to: Oracle Help Center (https://docs.oracle.com/en/) > Applications > Fusion Cloud
Applications > Financials > Books. The guides are in the Development section.
• File Based Data Import (FBDI) is used to load data into Oracle Cloud Applications from
external sources, such as legacy systems and third-party applications. The File Based Data
Import for Oracle Financials Cloud Guide includes links to:
- Spreadsheets used to load data into Oracle Cloud Applications from external
sources, such as legacy systems and third-party applications. The spreadsheet
templates help to structure, format, and generate the data file according to the
requirements of the target application tables.
- File-based load process to load the data files into the interface tables.
- Application-specific data import processes to transfer data from interface tables to

the application tables in your Oracle Cloud Applications.
• Tables and Views for Oracle Financials Cloud Guide includes:
- The tables with the basic information about the table columns, primary and foreign
keys, and indexes.
- The views, columns, and query details that are associated with each view.
• SOAP (Simple Object Access Protocol) Web Services for Oracle Financials Cloud Guide
include:.

- Business Object Services relationships, operations, and security
- Service Data Objects relationships and attributes
Note: Use SOAP web services to integrate with or extend Oracle Applications Cloud. Through web
services, you can integrate heterogeneous applications within the enterprise or expose business
functions to Oracle Cloud partners and customers over the Internet.

Friendly Search
Navigate to: Oracle Help Center (https://docs.oracle.com/en/) > Applications and type a word or
phrase in the Search box. You can:
• Enter a simple search entry: Just type your topic in the field.
• Review a comprehensive view of search results: Results show the guide as well as the topic
with direct links to the topic.
• View the number of results and context displayed.
• Refine the Search task pane to reduce the number of results.
• Follow the breadcrumbs that appear at the top of topics you select to allow easy return to the
list of results.

Summary

• Find additional application resources
• Use the Oracle Help Center to find additional information
• Access helpful video content to learn more about specific features

AccountingHub 20C StudentGuide

Uploaded by

Document Information

Original Title

Copyright

Available Formats

Share this document

Share or Embed Document

Sharing Options

Did you find this document useful?

Is this content inappropriate?

Copyright:

Available Formats

AccountingHub 20C StudentGuide

Uploaded by

Copyright:

Available Formats

Oracle Financials Cloud:

Oracle Financials Cloud:

After completing this course, you should be able to:

Oracle Financials Cloud: Accounting Hub Fundamentals 1 - 2

After completing this lesson, you should be able to:

Oracle Financials Cloud: Accounting Hub Fundamentals 1 - 3

Oracle Financials Cloud: Accounting Hub Fundamentals 1 - 4

Oracle General Ledger

Oracle Financial Reporting

Oracle Financials Cloud: Accounting Hub Fundamentals 1 - 5

Accounting Transformations by using Accounting Rules

Oracle Financials Cloud: Accounting Hub Fundamentals 1 - 6

Oracle Financials Cloud: Accounting Hub Fundamentals 1 - 7

The graphic in the slide illustrates the components of Accounting Methods.

The Accounting Methods include the following required elements:

The Accounting Methods include the following optional elements:

Oracle Financials Cloud: Accounting Hub Fundamentals 1 - 8

Oracle Financials Cloud: Accounting Hub Fundamentals 1 - 9

Oracle Financials Cloud: Accounting Hub Fundamentals 1 - 10

The six other tools for reporting in Financials are:

Other Reporting Tools Report Type

Reports and Analytics Oracle Transactional BI Objects

BI Catalog All Report Types except BI Publisher Reports

EPM Workspace Reports, Books, Snapshot Reports, Snapshot Books,

Enterprise Scheduler System (ESS) Oracle BI Publisher Reports

Oracle Financials Cloud: Accounting Hub Fundamentals 1 - 11

In this lesson, you should have learned how to:

Oracle Financials Cloud: Accounting Hub Fundamentals 1 - 12

Introducing Oracle Cloud Navigation

After completing this lesson, you should be able to:

Oracle Financials Cloud: Accounting Hub Fundamentals 2 - 2

Navigate to: News Feed Home Page.

Oracle Financials Cloud: Accounting Hub Fundamentals 2 - 3

Oracle Financials Cloud: Accounting Hub Fundamentals 2 - 4

Things to Finish section:

Oracle Financials Cloud: Accounting Hub Fundamentals 2 - 5

- Click an announcement image to view more details.

Oracle Financials Cloud: Accounting Hub Fundamentals 2 - 6

• The Analytics section displays:

Navigate to: Springboard > Analytics.

This screenshot show the General Accounting Infolets.

In Financials there are currently four choices of Analytics displays:

• Cash Management Infolets

• General Accounting Infolets

• Order to Cash Infolets

Oracle Financials Cloud: Accounting Hub Fundamentals 2 - 7

• The Navigator reflects the

The Navigator has:

Tips And Considerations

Oracle Financials Cloud: Accounting Hub Fundamentals 2 - 8

With the Personalize Springboard feature you can:

Navigate to: New Feed Home Page Springboard.

Oracle Financials Cloud: Accounting Hub Fundamentals 2 - 9

The Personalize Springboard feature enable you to:

Oracle Financials Cloud: Accounting Hub Fundamentals 2 - 10

Navigate to: Financial Reporting Center.

Oracle Financials Cloud: Accounting Hub Fundamentals 2 - 11

Navigate to: General Accounting > General Accounting Dashboard.

The General Accounting Dashboard contains the following sections:

• Inquiry and Reporting

• Planning and Budgeting

Oracle Financials Cloud: Accounting Hub Fundamentals 2 - 12

Navigate to: General Accounting > Period Close.