Implementing Accounting Hub

Oracle Financials
Cloud
Implementing Accounting Hub
22A
Oracle Financials Cloud
22A
F48630-01
Copyright © 2011,2022, Oracle and/or its affiliates.
Authors: Vinetta Kumar
This software and related documentation are provided under a license agreement containing restrictions on use and disclosure and are protected
by intellectual property laws. Except as expressly permitted in your license agreement or allowed by law, you may not use, copy, reproduce, translate,
broadcast, modify, license, transmit, distribute, exhibit, perform, publish, or display in any part, in any form, or by any means. Reverse engineering,
disassembly, or decompilation of this software, unless required by law for interoperability, is prohibited.
The information contained herein is subject to change without notice and is not warranted to be error-free. If you find any errors, please report
them to us in writing.
If this is software or related documentation that is delivered to the U.S. Government or anyone licensing it on behalf of the U.S. Government, the
following notice is applicable:
U.S. GOVERNMENT END USERS: Oracle programs, including any operating system, integrated software, any programs installed on the hardware,
and/or documentation, delivered to U.S. Government end users are "commercial computer software" pursuant to the applicable Federal Acquisition
Regulation and agency-specific supplemental regulations. As such, use, duplication, disclosure, modification, and adaptation of the programs,
including any operating system, integrated software, any programs installed on the hardware, and/or documentation, shall be subject to license
terms and license restrictions applicable to the programs. No other rights are granted to the U.S. Government.
This software or hardware is developed for general use in a variety of information management applications. It is not developed or intended for
use in any inherently dangerous applications, including applications that may create a risk of personal injury. If you use this software or hardware
in dangerous applications, then you shall be responsible to take all appropriate fail-safe, backup, redundancy, and other measures to ensure its safe
use. Oracle Corporation and its affiliates disclaim any liability for any damages caused by use of this software or hardware in dangerous applications.
Oracle and Java are registered trademarks of Oracle and/or its affiliates. Other names may be trademarks of their respective owners.
Intel and Intel Xeon are trademarks or registered trademarks of Intel Corporation. All SPARC trademarks are used under license and are trademarks or
registered trademarks of SPARC International, Inc. AMD, Opteron, the AMD logo, and the AMD Opteron logo are trademarks or registered trademarks
of Advanced Micro Devices. UNIX is a registered trademark of The Open Group.
This software or hardware and documentation may provide access to or information about content, products, and services from third parties. Oracle
Corporation and its affiliates are not responsible for and expressly disclaim all warranties of any kind with respect to third-party content, products, and
services unless otherwise set forth in an applicable agreement between you and Oracle. Oracle Corporation and its affiliates will not be responsible
for any loss, costs, or damages incurred due to your access to or use of third-party content, products, or services, except as set forth in an applicable
agreement between you and Oracle.
Contents
Get Help ................................................................................................................................ i
1 Introduction to Oracle Accounting Hub Cloud 1

Overview of Define Oracle Fusion Accounting Hub Configuration for Rapid Implementation ...................................... 1
Create an Oracle Accounting Hub Cloud Rapid Implementation Project ........................................................................... 2
Overview of Oracle Accounting Hub Cloud Features ............................................................................................................. 3
How Oracle Accounting Hub Cloud Works ............................................................................................................................... 3
Overview of Accounting Configuration Offerings .................................................................................................................. 6
Overview of Implementation Options for Oracle Accounting Hub Cloud ......................................................................... 6
Setup Data Import and Export for Oracle Accounting Hub Cloud ...................................................................................... 8
Overview of Implementing Financials ...................................................................................................................................... 12
2 Enterprise Structures for Oracle Accounting Hub 15

Overview of Enterprise Structures ............................................................................................................................................ 15
Overview of Common Financials Configuration for Rapid Implementation .................................................................... 15
Overview of Initial Configuration with the Enterprise Structures Configurator .............................................................. 16
FAQs for Define Initial Configuration ....................................................................................................................................... 16
Enterprise for Oracle Accounting Hub ..................................................................................................................................... 17
Overview of Legal Jurisdictions and Authorities ................................................................................................................... 17
Overview of Geographies ............................................................................................................................................................ 18
Overview of Legal Entities .......................................................................................................................................................... 19
3 Financial Reporting Structures 21

Overview of Financial Reporting Structure ............................................................................................................................. 21
Chart of Accounts ......................................................................................................................................................................... 21
FAQs for Manage Charts of Accounts ..................................................................................................................................... 22
Overview of Value Sets ............................................................................................................................................................... 23
Account Hierarchies ..................................................................................................................................................................... 23
Segment Value Attributes .......................................................................................................................................................... 27
FAQs for Maintain Segment Values Attributes ....................................................................................................................... 31
Overview of Deploying Flexfield ................................................................................................................................................ 31
Cross-Validation Rules ................................................................................................................................................................. 32

Segment Rules and Account Rules for Chart of Accounts Mapping ................................................................................ 33
FAQ for Manage Chart of Accounts Mapping ....................................................................................................................... 34
Overview of Defining Calendars ............................................................................................................................................... 34
FAQs for Define Calendars ......................................................................................................................................................... 35
Currencies ...................................................................................................................................................................................... 36
FAQs for Manage Currencies ..................................................................................................................................................... 37
Conversion Rate Types ................................................................................................................................................................ 38
FAQs for Manage Conversion Rate Types ............................................................................................................................... 41
Daily Currency Rates .................................................................................................................................................................... 41
4 Ledgers 43
Overview of Ledger and Subledgers ....................................................................................................................................... 43
FAQs for Specify Ledger Options ............................................................................................................................................. 43
Accounting Configuration .......................................................................................................................................................... 44
FAQs for Accounting Configuration ......................................................................................................................................... 45
Assign Access to Ledger ............................................................................................................................................................ 46
General Ledger Security ............................................................................................................................................................. 47
FAQs for Manage General Ledger Security ........................................................................................................................... 48
How Balances for Reporting Currencies Are Calculated ..................................................................................................... 49
Examples of Ledger Sets ............................................................................................................................................................ 52
Accounting and Reporting Sequences .................................................................................................................................... 52
FAQs for Manage Accounting and Reporting Sequences .................................................................................................. 56
Journal Approval Rules ............................................................................................................................................................... 56
AutoPost Criteria Sets ................................................................................................................................................................. 62
FAQs for Manage AutoPost Criteria Sets ............................................................................................................................... 64
Journal Reversals ......................................................................................................................................................................... 65
Overview of Clearing Accounts Reconciliation ..................................................................................................................... 70
5 Period Close Components 71

Overview of Period Close ............................................................................................................................................................ 71
FAQs for Period Close .................................................................................................................................................................. 71
Allocations and Periodic Entries ............................................................................................................................................... 72
Overview of Recurring Entries .................................................................................................................................................. 77
Overview of Using Calculation Manger ................................................................................................................................... 77
FAQs for Manage Allocations and Periodic Entries .............................................................................................................. 78
Allocation Rules ............................................................................................................................................................................ 79
FAQs for Allocation Rules ........................................................................................................................................................... 82

Allocation Rule Sets .................................................................................................................................................................... 84
FAQs for Allocation Rule Sets ................................................................................................................................................... 88
Overview of Point of View and Allocation Components ..................................................................................................... 89
FAQs for Point of View and Allocations Components ......................................................................................................... 89
Generate Allocations and Periodic Entries Manually ............................................................................................................ 91
Overview of Revaluations ........................................................................................................................................................... 92
6 Accounting Transformation 93
Overview of Accounting Transformation Configuration ..................................................................................................... 93
Analyze Source Systems ............................................................................................................................................................. 95
Manage Source Systems ............................................................................................................................................................ 99
Manage Accounting Rules ........................................................................................................................................................ 118
Migrate the Configuration ........................................................................................................................................................ 157
Secure Accounting Transformations ...................................................................................................................................... 157
Create and Process Subledger Journal Entries .................................................................................................................... 159
FAQs for Accounting Transformation .................................................................................................................................... 160
7 Subledger Accounting 163

Overview of Manage Subledger Accounting ........................................................................................................................ 163
Upload Transaction Data .......................................................................................................................................................... 163
Accounting Hub Maintenance ................................................................................................................................................. 170
Create Accounting ...................................................................................................................................................................... 172
Subledger Journal Adjustment ................................................................................................................................................ 183
Subledger Journal Entry ........................................................................................................................................................... 185
Subledger Balances .................................................................................................................................................................... 192
Advanced Features .................................................................................................................................................................... 200
Subledger Accounting Reporting ............................................................................................................................................ 219
FAQs for Subledger Accounting ............................................................................................................................................. 226
8 Intercompany Processing Rules 229

Overview of Intercompany Processing Rules ...................................................................................................................... 229
Overview of Intercompany Balancing Rules ........................................................................................................................ 229
Overview of Intercompany Allocations ................................................................................................................................. 230
FAQs for Intercompany Allocations ....................................................................................................................................... 230
Intercompany Reconciliation .................................................................................................................................................... 231
9 Consolidations 233
Overview of Consolidation ....................................................................................................................................................... 233
Example of Mapping Segments to Financial Management Dimensions ....................................................................... 233
FAQs for Consolidations ........................................................................................................................................................... 234
10 Budget Configuration 235

Overview of Budget Configuration ........................................................................................................................................ 235
Overview of Integration with Oracle Enterprise Planning and Budgeting Cloud Service ........................................... 237
11 Financial Reporting 239

Overview of Financial Reporting ............................................................................................................................................ 239
FAQs for Financial Reporting .................................................................................................................................................. 239
Create a Financial Report ........................................................................................................................................................ 240
12 Extensions for Oracle Accounting Hub 247

Enterprise Scheduler Jobs for Oracle Accounting Hub ..................................................................................................... 247
Oracle Financials Cloud Get Help
Get Help
Get Help in the Applications
Use help icons to access help in the application. If you don't see any help icons on your page, click your user image
or name in the global header and select Show Help Icons.
Get Support
You can get support at My Oracle Support. For accessible support, visit Oracle Accessibility Learning and Support.
Get Training
Increase your knowledge of Oracle Cloud by taking courses at Oracle University.
Join Our Community

Use Cloud Customer Connect to get information from industry experts at Oracle and in the partner community. You can
join forums to connect with other customers, post questions, and watch events.
Learn About Accessibility

For information about Oracle's commitment to accessibility, visit the Oracle Accessibility Program. Videos included in
this guide are provided as a media alternative for text-based topics also available in this guide.
Share Your Feedback

We welcome your feedback about Oracle Applications user assistance. If you need clarification, find an error, or just
want to tell us what you found helpful, we'd like to hear from you.
You can email your feedback to [email protected].
Thanks for helping us improve our user assistance!
i
Oracle Financials Cloud Get Help
ii
Oracle Financials Cloud Chapter 1
Implementing Accounting Hub Introduction to Oracle Accounting Hub Cloud
1 Introduction to Oracle Accounting Hub Cloud
Overview of Define Oracle Fusion Accounting Hub

Configuration for Rapid Implementation
Use the Define Oracle Fusion Accounting Hub Configuration for Rapid Implementation task list to streamline your
setup configurations. The rapid implementation task list minimizes the time used to complete your key configurations
and enables the day-to-day use of Oracle Accounting Hub Cloud applications.
The rapid implementation task list includes tasks that are:
• Critical setup tasks.

• Setup steps that are required by most users.
To create an implementation project that includes the Define Accounting Entry Configuration for Rapid
Implementation task list, use the Manage Implementation Projects page in the Setup and Maintenance work area.
You can modify the task list as needed and assign and track each task.
Note: You are not restricted to only the setup configuration in the rapid implementation task list. You can manually
add the standard Oracle Fusion Accounting Hub offering task lists and tasks to your rapid implementation project.
Task Lists
This table contains the task lists included in the Define Oracle Fusion Accounting Hub Configuration for Rapid
Implementation task list.
Task List Description
Define Enterprise Structures Configuration Define the enterprise structures configuration that includes financial and enterprise structures.
for Rapid Implementation
Define Financials Security Configuration Define the configuration for user and data roles set up.
for Rapid Implementation
Define Accounting Entry Configuration for Define the accounting entry configuration that includes accounting transformation rules for
Rapid Implementation transactions sourced from external applications.
Define Ledger Configuration for Rapid Define the configuration that includes general ledger and intercompany.
Implementation
Define Financial Reporting Center Define the configuration that includes set up for financial reporting and integration with planning and
Configuration for Rapid Implementation financial management applications.
1
Note: The Open First Period task is a required task and is part of the task list.
Related Topics
• Creating an Oracle Accounting Hub Cloud Rapid Implementation Project: Worked Example
Create an Oracle Accounting Hub Cloud Rapid

Implementation Project
This example shows how to create an implementation project using the Oracle Fusion Accounting Hub rapid
implementation task list.
This table contains a summarization of key decisions.
Decision to Consider In This Example
What Oracle Applications are included in The Oracle applications being implemented are:
this implementation?
• General Ledger
• Subledger Accounting
• Financial Reporting Center
Are the set-up requirements unique to this No

organization?
Can the rapid implementation task Yes

lists and tasks be used for this
implementation?
Creating the Implementation Project

To create an implementation project, follow these steps:
1. From the Setup and Maintenance work area, open the Setup page. You must have the Manage
Implementation Project privilege.
2. From the Setup page, open the panel drawer and select Manage Implementation Projects.
3. Click the Create icon.
4. Enter a meaningful name and a brief description to describe your project.
5. Optionally, assign the project to a user and specify a start date.
6. Click Save and Open Project when you complete your selection.
7. You can begin to assign the tasks to the appropriate users. Select and add the Define Fusion Accounting Hub
Configuration for Rapid Implementation task list.
2
Overview of Oracle Accounting Hub Cloud Features

Oracle Accounting Hub Cloud provides a complete set of accounting tools and unparalleled access to financial data,
including:
• Oracle General Ledger features that provide:
◦ Journal entry import and creation
◦ Real time balances from a balances cube
◦ Accounting controls
◦ Close functionality
◦ Cross-ledger intercompany balancing
◦ Calculation Manager for the definition of allocation rules using complex formulas
◦ Automatic generation of allocation journals
◦ Enhanced journal approval
◦ Year-end process management
• Oracle Financial Reporting that provides:

◦ Embedded balances cube functionality
◦ Multidimensional, online analytical processing of financial information
◦ Ability to slice and dice data across dimensions
◦ Drill up, down, and across on any parent level within the chart of accounts
• Accounting transformation enables you to create subledger accounting rules that provide flexible
transformation of transaction and reference information from diverse, non-Oracle, industry applications into
accurate, detailed, auditable accounting entries. The subledger accounting journals generated for non-Oracle
applications are stored in a subledger accounting repository that is shared with the subledger accounting
journals generated by Oracle Fusion Subledger Accounting for the subledgers such as Payables, Receivables,
Assets and Inventory.
Related Topics
• Oracle Accounting Hub Cloud: How It Works
How Oracle Accounting Hub Cloud Works

The Oracle Accounting Hub Cloud process begins by using financial data from any or all of the following:
• Non-Oracle source systems including transaction and reference information from industry-specific
applications.
• Oracle Fusion subledgers including subledger journals.
• Oracle E-Business Suite, Oracle PeopleSoft, and Oracle JD Edwards general ledgers including account balances.
3
The Accounting Hub process ends with complete reporting and analysis solutions.
The Oracle Accounting Hub Cloud Components

The Accounting Hub contains the following components:
• Accounting transformation to transform external source data.

• Oracle General Ledger to enter and post journals including allocations.
• Oracle Financial Reporting Center for reporting and analysis.
• Integration with Oracle Planning and Budgeting Cloud and Oracle Financial Consolidation and Close Cloud.
This figure illustrates the Oracle Accounting Hub Cloud components.
Oracle Accounting Hub Cloud for External Source Systems

Oracle Accounting Hub Cloud enables you to perform accounting transformations on external, non-Oracle source
system data. It utilizes the same subledger accounting rules engine that is also used to flexibly create accounting for
Oracle subledgers such as Payables and Receivables. Oracle Accounting Hub Cloud includes:
• Registration of your external source systems, indicating what types of transactions or activities require
accounting from those source systems.
• Create a library of transaction and reference information that is used for defining accounting treatments.
4
• Configurable accounting rules to define accounting treatments for transactions.

• Accounting rules engine that combines transaction and reference information from source systems with
accounting rules to create detailed journals stored in an accounting repository.
• Detailed subledger accounting journal entry repository to enable audit and accounting reconciliation of
balances.
• Reports and user interface inquiries for analyzing accounting transformations.
• Configurable analytical balances based upon source system or reference attributes.
Oracle General Ledger

The Oracle General Ledger combines traditional general ledger functionality with embedded Oracle Hyperion Essbase
functionality. The general ledger functionality includes:
• Journal entry creation, including updating of account balances cubes and tables.
• Date effective trees for chart of accounts maintenance and financial reporting, including What If analysis.
• Automatic balances cube creation from the chart of accounts configuration, simplifying implementation.
• Preaggregated balances at every summarization level across each dimension of the chart of accounts and
accounting periods to improve reporting performance.
• Multidimensional analysis using dimensions, such as the chart of accounts, periods, and currency, to provide
drill down and drill through functionally.
• Drill to details and source ledger balances from summary balances.
• Intelligence and analytics embedded within the context of a journal entry, enabling quick and accurate
completion of the journal entry process. As journal entries are entered, a What If analysis to determine the
impact of the unposted journals on account balances is displayed in the user interface. The What If analysis
eliminates navigating to an inquiry page or running a report to verify the results.
• Three balancing segments available in your chart of accounts for more detailed reporting.
• Automatic intercompany balancing journal creation in both Subledger Accounting and General Ledger
applications, ensuring proper recording of transactions across legal entities.
• Calculation Manager rules using complex formulas to distribute revenue and costs throughout the organization
for consistent periodic generation of allocation journal entries.
Financial Reporting Center

The Oracle General Ledger provides a Financial Reporting Center with robust financial reporting and analysis using data
from your balances cubes. The dimensions contained in your chart of account segments become the direct source of
multidimensional analysis. Direct links are maintained to your transactional data permitting comprehensive drill-down
from journals to transaction details. Use the following tools for your reporting and analysis:
• Financial Reporting to generate your reports.

• Smart View to generate spreadsheet reports.
• Oracle Transaction Business Intelligence to report using embedded analytics
• General Accounting and Journals dashboards to perform online inquiry and dashboard publication
• Account Monitor and Account Inspector to perform online multidimensional analysis of accounting balances
Accounting Hub fits into Oracle's broader enterprise performance management framework through integration with
Oracle Planning and Budgeting Cloud and Oracle Financial Consolidation and Close Cloud. You can you can write
budget from Planning and Budgeting Cloud to General Ledger or write the actual data from General Ledger to Planning
5
and Budgeting Cloud. You can use the regular interface to load data from ERP to Financial Consolidation and Close
Cloud.
Overview of Accounting Configuration Offerings

Use the Setup and Maintenance work area in Oracle Applications to manage the configuration of legal entities, ledgers,
and reporting currencies. To create a legal entity or ledger, first create an implementation project. This implementation
project can be populated by either adding a financials-related offering or one or more task lists.
Note: Setup tasks that are not related to the ledger or legal entity setup tasks are opened from either an
implementation project or directly from the Setup and Maintenance work area.
The financial applications have two predefined implementations:
• The Oracle Accounting Hub Cloud offering is used to add the General Ledger and Subledger Accounting
application features to an existing Enterprise Resource Planning (ERP) source system to enhance reporting and
analysis.
• The Financials offering includes the General Ledger and Subledger Accounting application features and one or
more subledger financial applications.
When adding an offering to an implementation project, update the tasks displayed by adding additional tasks.
Overview of Implementation Options for Oracle

Accounting Hub Cloud
The Oracle Accounting Hub Cloud has two possible implementation scenarios that can be used separately or in
conjunction with each other. These scenarios are:
• Accounting for diverse business system events and transactions with configurable and auditable rule-based
accounting transformations.
• Expansion of financial reporting enabling creation of multidimensional, self-service reporting and analytics
with real-time accounting information from a single source with flexible formatting options.
This figure illustrates Accounting Hub implementation scenarios.
6
Accounting for Diverse Transactions

The Oracle Accounting Hub Cloud provides accounting for diverse business system events and transactions using
configurable and auditable rule-based accounting transformations. The Accounting Hub process:
• Begins with transactions and data from your non-Oracle, industry-specific subledgers and other general
ledgers.
• Generates accounting events using the Create Accounting process to create journals that can be posted to the
Oracle General Ledger from specific subledgers and other general ledgers.
• Ends with complete reporting and analysis solutions.
See the following for details on implementing this scenario: Define Accounting Transformation chapter in the Oracle
Financials Cloud Implementing Accounting Hub guide.
Expansion of Financial Reporting

Oracle Accounting Hub Cloud enables creation of multidimensional, self-service reporting and analytics with real time
accounting information from a single source with flexible formatting options. The Financial Reporting Center includes:
• Predefined financial reports

• Ability to create reports,
• Flexible options for dissemination of such reports
7
• Account Monitor and Account Inspector providing drill-down and pivot views of your balances
• Oracle Hyperion Smart View providing spreadsheet analytics
• Oracle Transaction Business Intelligence Oracle Business Intelligence Publisher provide key performance
indicators (KPI), dashboards, and flexible reporting
For more information refer to the Using EPM with Oracle Financials Cloud link on the Books for Oracle Financials Cloud
page of the Oracle Help Center at https://docs.oracle.com.
Related Topics
• Overview of Financial Reporting Center
Setup Data Import and Export for Oracle Accounting

Hub Cloud
These sections describe the manual tasks that you must complete as part of the setup data export and import
processes for the Oracle Accounting Hub Cloud offering.
This table contains manual tasks that must be completed as part of the setup data export and import processes for the
Oracle Accounting Hub Cloud offering.
Section Description
Setup tasks performed before export You must perform these tasks prior to initiating export processes for the Oracle Accounting Hub Cloud
offering.
Setup tasks performed before import You must perform these tasks prior to initiating import processes for the Oracle Accounting Hub Cloud
offering.
Setup tasks performed after import Setup data for these tasks is not imported from the source instance. Review and perform the manual
setups steps on the target instance as required.
Refer to the Oracle Applications Cloud Using Functional Setup Manager guide for the steps to perform setup data
export and import processes.
Setup Tasks Performed Before Export

Prior to initiating export processes from the source instance, you must verify and update setup for this task. Required to
ensure that data is correctly imported into the target instance.
This table contains setup tasks performed before export.
Activity Name Task Name Setup Steps
Define Chart of Accounts Manage Account Combinations Account combinations are not exported from
the source instance. Before exporting, navigate
8
to the Manage Chart of Accounts Instance

page on the source instance and verify that
dynamic insertion is enabled for your charts
of accounts. As long as dynamic insertion is
enabled, account combinations are created
automatically as needed on the target instance.
Setup Tasks Performed Before Import

Prior to initiating import processes into the target instance, you must verify and update setup for this task.
This table contains setup tasks performed before import.
Define Common Applications Configuration for Define Implementation Users The import process does not include
Oracle Accounting Hub Cloud implementation users and roles associated with
them.
For more information, see Oracle Fusion

Middleware Enterprise Deployment Guide for
Oracle Identity Management (Oracle Fusion
Applications Edition).
Setup Tasks Performed After Import

Setup data for the following tasks are not imported. Review these tasks for relevance to your implementation. For
relevant tasks, open the corresponding setup pages from your implementation project to create the setup on the target
instance as needed.
This table contains setup tasks performed after import.
Activity Name Task Name
Define General Ledger Options • Manage Journal Approval Rules

• Manage Document Sequences
Define Document Sequences Manage Document Sequences
Define Approval Management for • Manage Task Configurations for Financials

Financials
• Manage Approval Groups for Financials
Setup data for the following tasks are not imported from the source instance. Review the steps in the following table to
create the setup on the target instance as needed.
This table contains steps to create the setup on the target instance as needed.
9
Define Accounting Transformation Import Supporting Reference Initial Balances This task enables upload of initial subledger
Configuration balances for supporting references. These
balances are not imported from the source
instance, but can be loaded directly to the
target instance.
For more information, see Oracle Financials

Cloud Implementing Accounting Hub Guide,
Define Accounting Transformation.
Define Financial Reporting Configure Smart View Client for Users Manually reconfigure the Smart View client to
point to the production instance.
For more information about configuring the

Smart View client for users, refer:
• Oracle Financials Cloud Implementing

Accounting Hub Guide, Define Financial
Reporting
• The Using EPM with Oracle Financials
Cloud link on the Books for Oracle
Financials Cloud page of the Oracle Help
Center at https://docs.oracle.com
Define Financial Reporting Center Define Essbase Database Connection in Manually reconfigure the Essbase database
Configuration Workspace connection in Hyperion Workspace.

Hyperion Workspace Database Connection,
see Oracle Financials Cloud Implementing
Reporting,
Define Financial Reporting Center Configure Financial Reporting Studio Client for Manually reconfigure the Financial Reporting
Configuration Users Studio client to point to the production
instance.

Financial Reporting Studio client for users,
refer:
• Oracle Financials Cloud Implementing

Reporting
• The Using EPM with Oracle Financials
Cloud link on the Books for Oracle
Financials Cloud page of the Oracle Help
Center at https://docs.oracle.com
Define Financial Reporting Create Financial Statements Export the financial report definitions from
Workspace in the source environment.
When exporting, you can export a single report,

multiple reports in a .zip file, or an entire folder
structure in a .zip file.
10
1. Navigator > General Accounting: Financial

Reporting Center > select link: Open
Workspace for Financial Reports.
2. Navigate to Applications > BI Catalog.
3. Navigate to File > Export.
4. Save the file to the local desktop.
Import the file into Workspace in the target
environment.
1. Navigator > General Accounting: Financial

Reporting Center > select link: Open
Workspace for Financial Reports.
2. Navigate to Application > BI Catalog.
3. Navigate to File > Import.
4. Select the file you had saved during the
export.
If you import the folder structure, the entire
structure from the source instance is imported
into the existing structure on the target
instance. This could result in some redundant
folders. In this case, you can reorganize child
folders in the structure on the target instance
and delete any unneeded folders.
Define Period Close Components Manage Allocations and Periodic Entries Export the allocation rules, rule sets,
variables, and runtime prompt definitions
from Calculation Manager in the source
environment.
When exporting, you can export at the

application level or at a single rule or rule set
level.
Note:
You must export and import rules for each
application on the Essbase server separately.
1. Navigator > General Accounting: Journals

> select link: Create Allocation Rules.
2. Navigate to File > Export.
3. Save the file to the local desktop.
Import the file into Calculation Manager in the
target environment.
1. Navigator > General Accounting: Journals

> select link: Create Allocation Rules.
2. Select the specific application in which to
import the rules.
3. Navigate to File > Import.
4. Select the file you saved during the export.
Define Hyperion Financial Management Define Hyperion Financial Management Manually import the rules using the Oracle
Integration Configuration Enterprise Performance Management Life Cycle
Management tool.
For more information, refer to the Using EPM

with Oracle Financials Cloud link on the Books
11
for Oracle Financials Cloud page of the Oracle

Help Center at https://docs.oracle.com.
Define Hyperion Financial Management Define ERP Integrator Configuration for Manually import the rules using the Oracle
Integration Hyperion Financial Management Enterprise Performance Management Life Cycle
Management tool.

Define Budget Configuration Define Budget Configuration in Hyperion Manually import the rules using the Oracle
Planning Enterprise Performance Management Life Cycle
Management tool.

Define Budget Configuration Define ERP Integrator Configuration for Manually import the rules using the Oracle
Hyperion Planning Enterprise Performance Management Life Cycle
Management tool.

Overview of Implementing Financials

To start your Financials implementation, use the Application Implementation Consultant role
(ORA_ASM_APPLICATION_IMPLEMENTATION_CONSULTANT_JOB) to opt into the offerings that meet your business
requirements. Refer to the Oracle Applications Cloud Using Functional Setup Manager guide to manage the opt-in and
setup of your offerings.
Financials Offering
By using the Financials offering, you can configure how you manage financial flows, including assets, ledgers,
cash cycle, invoices and payments, accounts receivable, collections, and the setup of subledger accounting and tax
configuration.
The following table specifies the primary functional areas of this offering. For the full list of functional areas and
features in this offering, use the Associated Features report that you review when you plan the implementation of your
offering.
12
Functional Area Description
Bill Management Manage system options and user registrations.
Budgetary Control and Encumbrance Manage control budgets and encumbrance accounting, along with data access for users. Public sector
Accounting customers typically use this functional area.
Cash Management and Banking Manage banks, bank branches, and bank accounts. Additionally, define reconciliation matching rules,
bank statement transaction creation rules, parse rules, transaction codes, and transaction type
mapping. Furthermore, configure your cash positioning and cash forecasting options.
Collections Manage aging methods and collectors, as well as collections preferences, scoring data points, and
strategy tasks.
Customer Billing Manage Receivables transactions and customer billing: AutoInvoice, payment terms, transaction types,
transaction sources, memo lines, balance forward billing, and recurring billing.
Customer Payments Manage Receivables customer payments and receipts: receipt classes and methods, AutoCash rules,
Application rules, AutoMatch, Lockbox.
Expenses Manage expense report templates, approval rules, and conversion rates and policies. If applicable, opt
into using corporate cards for expenses, processing of expense receipt imaging, or integration with
travel.
Financial Reporting Center Manage the financial tools to report and analyze accounting data: Financial Reporting Center, Smart
View, Financial Reporting Studio, and Workspace.
Fixed Assets Manage asset locations, calendars, books and categories, along with depreciation methods.
General Ledger Manage ledgers, accounting configurations, journal sources and categories, and other related
accounting setup. If applicable, opt into configuring journal approval email notifications.
Intercompany Manage Intercompany transaction processing within Financials, intercompany balancing and
reconciliation.
Joint Venture Management Manage the distribution of joint venture revenue and costs among joint venture partners while
preserving essential data for tracking and auditing.
Payables Manage supplier invoice and payment options, payment terms, distribution sets, invoice tolerances,
and procurement agents.
Payments Manage payment systems, payment methods, formats, and payment process profiles. If applicable, opt
into deriving a bank account number from IBAN.
Receivables Manage the required setups to enable Receivables for transactions and receipts: Receivables system
options; Receivables activities; AutoAccounting rules; remit-to addresses; and statement cycles.
Revenue Management Manage system options for revenue management, selling price profiles, hierarchies, resources, and
Trading Community source systems.
13
Functional Area Description
Revenue Recognition Manage revenue recognition for Receivables: revenue policies and revenue contingencies.
Suppliers Configure options for suppliers and supplier data.
Transaction Tax Manage tax configuration, including tax regimes, taxes, and tax rates.
U.S. Federal Financials Manage the financial management system options specifically defined for U.S. Federal agencies.
Related Topics
• Plan Your Implementation
14
Implementing Accounting Hub Enterprise Structures for Oracle Accounting Hub
2 Enterprise Structures for Oracle Accounting

Hub
Overview of Enterprise Structures
Oracle Applications have been designed to ensure your enterprise can be modeled to meet legal and management
objectives. The decisions about your implementation of Oracle Applications are affected by your:
• Industry
• Business unit requirements for autonomy
• Business and accounting policies
• Business functions performed by business units and optionally, centralized in shared service centers
• Locations of facilities
Every enterprise has three fundamental structures that describe its operations and provide a basis for reporting.
• Legal
• Managerial
• Functional
These structures are implemented using the chart of accounts and organization hierarchies. Many alternative
hierarchies can be implemented and used for reporting.
Related Topics
• Enterprise Structures Business Process Model
• Guidelines for Configuring Global Enterprises
• Model Your Enterprise Management Structure
• Overview of Diagnostic Tests for Enterprise Structures Setup
Overview of Common Financials Configuration for Rapid

Implementation
You can use the Rapid Implementation for General Ledger workbook template to rapidly implement the following
common setup objects for enterprise structures:
• Chart of accounts, including value sets, value set values, structures, and structure instances
• Account hierarchies, represented in the application through trees and tree versions
• Accounting calendars (monthly type only)
• Legal entities
• Primary ledgers with legal entity assignments to primary balancing segment values
15
• Business units
• Rules of generating sequential IDs for transactions recorded in the application
• Select setup objects along with their accounting specifications, for various Financial applications
Related Topics
• Overview of Enterprise Structures Rapid Implementation
• Create Chart of Accounts, Ledger, Legal Entities, and Business Units in Spreadsheets
• How Charts of Accounts, Ledgers, Legal Entities, and Business Units Are Created Using Spreadsheets
• Manage Implementation Projects
Overview of Initial Configuration with the Enterprise

Structures Configurator
The Enterprise Structures Configurator is an interview-based tool that guides you through the process of setting up a
basic enterprise structure. By answering questions about your enterprise, the tool creates a structure of divisions, legal
entities, business units, and reference data sets that reflects your enterprise structure. After you create your enterprise
structure, you also follow a guided process to determine whether to use positions, and whether to set up additional
attributes for jobs and positions. After you define your enterprise structure and your job and position structures, you
can review them, make any necessary changes, and then load the final configuration.
Related Topics
• Establishing Enterprise Structures Using the Enterprise Structures Configurator: Explained
• Design an Enterprise Configuration
FAQs for Define Initial Configuration

What happens if I don't use the Enterprise Structures Configurator
to set up my enterprise structures?
The Enterprise Structures Configurator is an interview-based tool that guides you through setting up divisions, legal
entities, business units, and reference data sets. If you don't use the Enterprise Structures Configurator, then you must
set up your enterprise structure using the individual tasks that correspond to each enterprise component. In addition,
you can't set up multiple configurations and compare different scenarios. Using the Enterprise Structures Configurator
is the recommended process for setting up your enterprise structures.
16
What's an ultimate holding company?

The legal entity that represents the top level in your organization hierarchy, as defined by the legal name entered for the
enterprise. This designation is used only to create an organization tree, with these levels:
• Ultimate holding company as the top level

• Divisions and country holding companies as the second level
• Legal employers as the third level
Enterprise for Oracle Accounting Hub

Define Enterprises
An enterprise is a collection of legal entities sharing common control and management.
Enterprise Defined
When implementing Oracle Fusion Applications you operate within the context of an enterprise that has already been
created in the application for you. This is either a predefined enterprise or an enterprise that has been created in the
application by a system administrator. An enterprise organization captures the name of the deploying enterprise and
the location of the headquarters. In Oracle Fusion Applications, an organization classified as an enterprise is defined
before defining any other organizations in the HCM Common Organization Model. All other organizations are defined as
belonging to an enterprise.
Enterprise Information for Non-HCM Users

The Manage Enterprise HCM Information task includes default settings for your enterprise such as the employment
model, worker number generation, and so on. If you're not implementing Oracle Fusion Human Capital Management
(HCM), then the only action you may need to perform using this task is to change the enterprise name, if necessary. The
other settings are HCM-specific and aren't relevant outside of Oracle Fusion HCM.
Overview of Legal Jurisdictions and Authorities

You are required to register your legal entities with legal authorities in the jurisdictions where you conduct business.
Register your legal entities as required by local business requirements or other relevant laws. For example, register your
legal entities for tax reporting to report sales taxes or value added taxes.
Define jurisdictions and related legal authorities to support multiple legal entity registrations, which are used by Oracle
Fusion Tax and Oracle Fusion Payroll. When you create a legal entity, the Oracle Fusion Legal Entity Configurator
automatically creates one legal reporting unit for that legal entity with a registration.
17
Related Topics
• Jurisdictions
• Create Legal Jurisdictions, Addresses and Authorities
Overview of Geographies
Setting up your geography structure and master geographies correctly in the Trading Community Model is critical to the
proper use and management of Oracle Enterprise Resource Planning (ERP) Cloud applications.
The geography structure and master geography data is shared across multiple product families and applications.
Address validation ensures complete and valid master address data across all location entities across product
applications. In addition, complete and valid master data is critical for accurate transaction tax calculation.
You can either define your geography structure and corresponding master geographies manually or import these
geography entities. You can use the:
1. Manage Geographies page

2. Manage File Import Activities task
For more information about managing your geographies, see the Define Geographies section in the Define Enterprise
Structures chapter in the Oracle ERP Cloud Implementing Common Features for Financials and Project Portfolio
Management guide on Oracle Help Center (https://docs.oracle.com).
Manage Geographies
Use the Manage Geographies page to manually define your geography structure, hierarchy, mapping, and validation.
Manually define your geographies when you have a simple geography requirement with a limited number of
geographies within an individual country.
Manage File Import Activities

You can upload the geography structure and hierarchy using the Manage File Import Activities task. Once you upload
your geography data successfully, use the Manage Geographies page to:
• Validate your data

• Enable geography validation
• Enable tax validation
Set the address validation for applicable countries to Error to ensure that you haven't created any invalid or
incomplete master address data for any location entities. The accuracy of master address data is critical to successful
implementations.
Use data import when you have more complex geography requirements, such as for the United States and Canada.
Related Topics
• Manage Geography Structures, Hierarchies, and Validation
18
Overview of Legal Entities

A legal entity is a recognized party with rights and responsibilities given by legislation.
Here are the rights and responsibilities of legal entities:
• Own property
• Trade
• Repay debt
• Account for themselves to regulators, taxation authorities, and owners according to rules specified in the
relevant legislation
Their rights and responsibilities may be enforced through the judicial system. Define a legal entity for each registered
company or other entity recognized in law for which you want to record assets, liabilities, expenses and income, pay
transaction taxes, or perform intercompany trading.
Related Topics
• Overview
• Create Legal Entities, Registrations, and Reporting Units
• How You Create Legal Entities in the Enterprise Structures Configurator
• Model Legal Entities
19
20
Implementing Accounting Hub Financial Reporting Structures
3 Financial Reporting Structures
Overview of Financial Reporting Structure

Define your enterprise structures in your chart of accounts to track and report on your financial objectives and meet
your reporting requirements. The benefit of representing your enterprise in the chart of accounts is the functionality
which includes multidimensional reporting with its Essbase tool. Segments included in the chart of accounts become
dimensions in Essbase. The recorded data is automatically loaded into the Essbase cube when you post your journal
entries. The Essbase tool includes powerful functionality for analysis and reporting on your financial data.
Related Topics
• Represent Your Enterprise Structure in Your Chart of Accounts
• Financial Enterprise Structure Components
• Model Your Financial Reporting Structure
Chart of Accounts
Overview of Chart of Accounts
The chart of accounts is the underlying structure for organizing financial information and reporting. An entity
records transactions with a set of codes representing balances by type, expenses by function, and other divisional or
organizational codes that are important to its business. The chart of accounts facilitates aggregating data from different
operations, from within an operation, and from different business flows, thus enabling the organization to report using
consistent definitions to their stakeholders in compliance with legislative and corporate reporting standards and aiding
in management decisions.
Related Topics
• Chart of Accounts
• Chart of Accounts Components
• Essbase Character and Word Limitations
Chart of Accounts Structures and Instances

In Oracle Fusion General Ledger, the chart of accounts model is framed around the concept of a chart of accounts
structure, under which one or more chart of accounts structure instances can be created. Consider the critical choices
list here when creating your hart of accounts instances and structures.
21
Chart of Accounts Structure

When creating the segments for the chart of accounts structure, you must enter segment sequence numbers that are
consecutive and begin with the number one.
Chart of Accounts Structure Instance

For segments in your chart of account structure instance that you expect to contain a large number of distinct values,
you must perform the following steps:
• In the chart of accounts definition, mark the segment query required option as selectively required.
To perform searches in the transactional user interface, you have to specify the following segment as a
mandatory search criteria.
• Create required indexes in the GL_CODE_COMBINATIONS table for segments that are selectively required.
CAUTION: For the Accounting Key Flexfield value sets used in your chart of accounts structure and instance, you
must use independent validation only. If you use other validations, you may not be able to use the full chart of
accounts functionality, such as data security, reporting, and account hierarchy integration.
Overview of Creating and Configuring Chart of Accounts Structure

and Instances
In Oracle General Ledger, the chart of accounts model is framed around the concept of a chart of accounts structure,
for which one or more chart of accounts structure instances can be created. A chart of accounts structure defines the
key attributes for your chart of accounts. These attributes include the number of segments, the segment sequences,
the segment names, segment prompts, segment labels, for example natural account and primary balancing, and default
value sets.
Related Topics
• Create a Chart of Accounts Structure and Instance
• Example of One Chart of Accounts Structure with Many Instances
• Configure Chart of Account Segments for Business Intelligence
• Cost Centers and Departments
FAQs for Manage Charts of Accounts

How can I use future accounting segments?
To plan for future growth in the business organization that requires additional segments in the chart of accounts. Extra
segments can be added to the chart of accounts structure during your original implementation. All segments of the
chart of accounts are required and have to be enabled. The unused segments can be assigned value sets that have a
22
single value in the chart of accounts structure instance. The value is set as a default for that segment so that the extra
segments are automatically populated when an account account combination is used.
Overview of Value Sets

A value set is a group of valid values that you assign to a flexfield segment to control the values that are stored for
business object attributes.
A user enters a value for an attribute of a business object while using the application. The flexfield validates the value
against the set of valid values that you configured as a value set and assigned to the segment.
Related Topics
• Overview of Value Sets
• Value Sets for Charts of Accounts
• Create a Value Set for Your Chart of Accounts
Account Hierarchies
Overview of Trees
Trees are hierarchical data models that you can use to organize data, apply business rules, control data access, and
improve performance while querying. For example, an application maintains data of an organization called Vision
Corporation that has two departments: Marketing and Finance. The Finance department has two functional divisions:
Receivables and Payables. You can define a tree for Vision Corporation to establish a hierarchy across its departments,
and their respective functional divisions. You can use the hierarchy to manage data at various levels of the organization.
To work with trees, in the Setup and Maintenance work area, use any of the following tasks:
• Manage Tree Structures: To create and update tree structures. You must first define a tree structure to create a
tree.
• Manage Trees and Tree Versions: To create and update trees and their versions.
• Manage Tree Labels: To create and update tree labels.
Tree Structures
As the name suggests, tree structures provide you the framework to organize data such that you can establish a
hierarchy for use by the tree. So, similar to a template, a tree structure guides the creation of a tree.
Tree
A tree is an instance of the tree structure. The root node is the highest nodal point of a tree. Child nodes branch off from
the root node. Child nodes at the same level, branching off from a common parent node, are called siblings. Leaves are
details branching off from a node but not extending further down the tree hierarchy. You can create trees for multiple
data sources and share them across applications.
23
Tree Versions
A tree by default has only one version. If required, you can create and maintain more than one editable tree version. At
any point, only one tree version must be active. If you edit an existing version, it changes from active to draft. To use it
again, you must set it to active. Similar to any other version control system, versions of trees are maintained to track all
the changes that a tree undergoes in its life cycle.
Tree Labels
Tree labels are short names given to trees and tree structures. You can label the tree versions for better accessibility and
information retrieval. When nodes are created in a tree, the existing tree labels are automatically assigned to the new
tree nodes. You can use any table to store the labels and register the label data source with the tree structure.
Related Topics
• Tree Labels
• Tree Structures
Overview of Managing Account Hierarchies

Account hierarchies are defined in Oracle Fusion applications using tree functionality. Each account hierarchy is defined
as a tree with one or more versions. Tree versions are used to track account hierarchies as they change over time. For
example, an account hierarchy to summarize cost of goods has different accounts for 2011, versus 2010. The changes
are in the business operations and affect the chart of accounts values.
Chart of accounts values can be associated with multiple hierarchies by defining multiple trees. Using multiple trees
enable create financial reports for different target audiences. For example, you can use different hierarchies to track cost
centers either by geography or line of business.
Before setting up hierarchies, you may want to consider different hierarchy requirements for financial reporting,
allocations, cross validation rules, revaluations, and chart of accounts mapping.
Related Topics
• How Segment Value and Hierarchy Import Data Is Processed
• Segment Values and Hierarchies Interface Tables
• Publish an Account Hierarchy
• Hierarchies for Cross Validations, Revaluations, and Chart of Accounts Mapping
• Considerations for Hierarchy Member Names in Financial Reporting and Allocations
Overview of Maintaining Account Hierarchies

This topic describes the best practices of maintaining and publishing the account hierarchies. Account hierarchies
are used throughout Oracle Fusion General Ledger for creating financial reports, Smart View inquiries, allocation
definitions, cross validation rules, and revaluation definitions.
24
Related Topics
• Account Hierarchy Trees
• Maintenance Hierarchies
• Example of Hierarchy Maintenance
FAQs for Manage Account Hierarchies

How can I manage and review account hierarchies?
View segment value descriptions when creating, editing, or reviewing account hierarchies online. You can also export
account hierarchies to a spreadsheet to review, analyze, and report offline.
To export all nodes in the hierarchies to a spreadsheet, expand all nodes first from View -> Expand All in the Manage
Account Hierarchies: Specify Nodes page.
When do I manually submit row and column flattening for tree versions?
Row Flattening and Column Flattening for tree versions must be manually submitted in the following scenarios.
• A new tree or tree version is defined

• If the tree or tree version has any change made to it that would alter the flattened hierarchy data. For example,
adding, moving, and duplicating members. Basically, anything that impacts the flattened hierarchy data.
• If Data Relationship Management (DRM) is used with Oracle Fusion General Ledger, after running the Load
Account Values and Hierarchies process from the Scheduled Process work area to load chart of accounts
reference data from DRM to Oracle Fusion General Ledger.
• When range based hierarchy assignments are supported, if new values are added that are within the account
range assigned to the hierarchy.
Note: In this case, try submitting the flattening programs using the Online Mode first. If the newly inserted
child account value does not appear to be included in the flattened hierarchy data, then the flattening
program has to be submitted using the Force Flattening Mode, instead of Online Flattening. An issue with
the incremental flattening programs can prevent them from picking up this type of hierarchy change, so full
flattening can be required.
Note: Column flattening processed data is primarily relevant to Oracle Fusion Transactional Business Intelligence, but
there should not be any adverse impact to run both row and column flattening processes.
Overview of Managing Tree Structures

A tree structure defines the hierarchy for creating trees and prescribes rules based on which trees are created,
versioned, and accessed. You can associate multiple data sources with a tree structure. A tree is an instance of this
hierarchy. Every tree structure can contain one or more trees.
25
You can create tree structures specific to an application but you can share tree structures across applications. If you
apply version control to the tree structure, it's carried over to the trees that are based on the tree structure. Each tree
version contains at least one root node. Occasionally, a tree version may have more than one root node.
An administrator controls the access to tree structures through a set of rules that are periodically audited for validity.
Related Topics
• Guidelines for Defining the Tree Structure
• Guidelines for Managing Tree Structures
• Tree Structure Audit Results
• Guidelines for Specifying Data Sources for Tree Structures
• Guidelines for Improving the Performance of a Tree Structure
Tree Labels
Tree labels are tags that are stored on tree nodes. You can store labels in any table and register the label data source
with the tree structure. When a labeling scheme is used for trees, the selected labels are stored in the tree label entity,
and each tree node contains a reference to a tree label in the labeling scheme.
The following table lists the three ways in which tree labels are assigned to the tree nodes.
Labeling Scheme Description
Level Labels that are automatically assigned based on the data source to which the tree node belongs.
A level label points to a specific data source. For example, in a tree that reflects the organizational
hierarchy of an enterprise, all division nodes appear on one level and all department nodes on another.
Group Labels that you can arbitrarily assign to tree nodes.
Depth Labels that are automatically assigned based on the depth of the tree node within the tree. No manual
assignment is performed.
Note:
In an unbalanced hierarchy, a level may not be equal to depth.
Overview of Managing Tree Versions

You can create and edit trees and tree versions depending upon the requirement. A tree can have one or more tree
versions. When you change an existing tree, a new version is created and published. You can use the tree version audit
results to verify the tree version's correctness and data integrity.
26
Related Topics
• Guidelines for Managing Trees and Tree Versions
• Tree Version Audit Results
• How Trees and Data Sources Work Together
• Tree Nodes
Segment Value Attributes

Segment Labels
Segment labels identify certain segments in your chart of accounts structure and assign special functionality to those
segments. Best practice is to assign each segment label one time within the chart of accounts structure. Here are the
segment labels that are available to use with the chart of accounts structure.
CAUTION: Validations aren't performed when segment labels are assigned, so verify that all are assigned correctly
before using your chart of accounts.
Balancing
Ensures that all journals balance for each balancing segment value or combination of multiple balancing segment
values. You can secure access to your primary balancing segment values only with data access sets. The General Ledger
application automatically calculates and creates balancing lines as required in journal entries. For example, recognizing
an entity's receivable and the other entity's payable. The three balancing segment labels are primary, second, and third
balancing. The primary balancing segment label is required.
Cost Center
Represents the smallest segment of an organization for which costs are collected and reported. Facilitates grouping
of natural accounts by functional cost types, accommodating tracking of specific business expenses across natural
accounts. As cost centers combine expenses and headcount data into costs, they're useful for detailed analysis and
reporting. Cost centers are optional, but required for:
• Tracking depreciation, additions, and other transactions in Oracle Fusion Assets.

• Storing expense approval limits in Oracle Fusion Expense.
Natural Account
Determines the account type (asset, liability, expense, revenue, or equity), whether posting is allowed, and other
information specific to the segment value. The natural account segment is mapped to the Financial Category dimension
in the balances cube to enable ad hoc reporting and transactional dashboards. This functionality uses Oracle Fusion
Business Intelligence Enterprise Edition to analyze and drill into expense and revenue transactions. The natural account
segment label is required.
27
Intercompany
Optionally, assign the segment to be used in intercompany balancing functionality. You can't use the primary balancing
or natural account segments as the intercompany segment. You can assign the same values to both the primary
balancing and intercompany value sets. You can also assign the same value set to the primary balancing segment and
the intercompany segment. The sharing of the value set or values:
• Enables clear visibility of the due to and due from relationships inherent in intercompany accounting across the
entire organization.
• Saves maintenance and ensure completeness.
However, sharing value sets can cause problems when applying segment value security rules because the rules applied
to both segments. The rules can restrict access to certain values which may complicate entering intercompany entries.
For example, you might have access to company 01 at the balancing segment level but not company 02. As a result, you
can't enter an intercompany entry for transactions between 01 and 02.
Related Topics
• Example of Segment Labels
• How can I change segments in an existing chart of accounts structure
Example of Segment Labels

For a chart of accounts, each segment can be qualified by a label to distinctly indicate its purpose. The label designation
is used by Oracle Fusion General Ledger processes to determine how to display and process transactions and balances
that are recorded.
Scenario
You are creating your chart of accounts with six segments. General Ledger permits selection of up to thirty segments
for your chart of accounts. You must have a minimum of three required segments, as determined by the number of
required segment labels (qualifiers). Required segment labels are:
• Primary Balancing Segment: Main balancing segment typically used to represent the company dimension of
the organization. The segment set with this label can't be set with another label.
• Cost Center Segment: Smallest segment of an organization for which you collect and report costs. You are
required to create this segment if you're implementing Oracle Fusion Assets.
• Natural Account Segment: Classification of transactions and balances according to distinct account types:
asset, liability, equity, revenue, and expense accounts. The segment set with this label can't be set with another
label.
The following optional segment labels are available, and you are implementing all of them:
• Second Balancing Segment: Used to balance transactions, as needed, by an additional dimension beyond the
primary balancing segment.
• Third Balancing Segment: Used to balance transactions, as needed, by an additional dimension beyond the
primary and second balancing segments.
28
• Intercompany Segment: Used to track intercompany due to and due from balances by identifying the specific
trading company. The intercompany qualified segment cannot be set with any of the three balancing segment
qualifiers. The values in this segment's value set must be the same as the primary balancing segment.
Segment labels can only be assigned once within a chart of accounts. The following table shows the segment labels that
are assigned to each segment in the chart of accounts.
Segment Label
Company Primary Balancing Segment
Cost Center Cost Center and Second Balancing Segment
Location Third Balancing Segment
Account Natural Account Segment
Product Line Not Applicable
Intercompany Intercompany Segment
Note: Validations aren't performed when segment labels are assigned, so verify that all are assigned correctly before
using your chart of accounts.
For Oracle Transactional Business Intelligence reporting, all labeled segments of the chart of accounts are automatically
maintained in the data that reporting is based on. The granularity of information stored in the nonqualified segments
is summarized and Oracle Transactional Business Intelligence isn't able to provide detailed reporting by segments.
To maintain the ability to perform detailed reporting on such segments, create user-defined labels to qualify these
segments.
For example, one of the segments of the chart of accounts is based on product line, and none of the segment labels are
applicable. The organization must derive product line-based Oracle Transactional Business Intelligence reports. Create a
user-defined label called Product Line to use to qualify the Product Line segment of the chart of accounts.
Related Topics
• How can I change segments in an existing chart of accounts structure
Overview of Balancing Segments

Balancing segments ensure that all journals balance for each balancing segment value or combination of multiple
balancing segment values. You can secure access to your primary balancing segment values only with data access sets.
The General Ledger application automatically calculates and creates balancing lines as required in journal entries. By
enabling multiple balancing segments for your chart of accounts, you can produce financial statements for each unique
combination of segment values across one, two, or three qualified balancing segments. This ability provides you greater
29
insights into your operations as it affords you visibility along the critical fiscal dimensions you use to plan, monitor, and
measure your financial performance.
Related Topics
• Overview of Balancing Segments
• Considerations for Multiple Balancing Segments
• Example of Using Multiple Balancing Segments
Examples of Segment Value Inheritance

The Inherit Segment Value Attributes process simplifies the chart of accounts maintenance. When the characteristics
of values in the value sets are updated, such as changes to enabled status, effective date, posting allowed status, or
natural account type, all previously created account combinations that referenced such values aren't automatically
updated by these changes. The Inherit Segment Value Attributes process lets you run a controlled process to update
such existing account combinations. This process maintains and corrects the current attribute settings for those
account combinations that contain the account values that were changed.
For account combinations where the present settings must be retained and not impacted by account attribute changes,
activate the option to preserve the account combination's attributes. The Preserve Attributes option can be found on
the Manage Account Combinations page. Activating the option prevents those account combination's attributes from
being updated when the Inherit Segment Value Attributes process is run.
Scenario
For example, there are three inactive account combinations that share a common inactive cost center value of 110. The
following table lists each account combination, indicates whether the account combination is enabled, and indicates
how the Preserve Attributes option is set.
Company-Cost Center-Account Account Combination Enabled Preserve Attributes
01-110-5210 No Disabled
04-110-4310 No Enabled
03-110-6810 No Disabled
Cost center 110 is enabled and the segment value inheritance process is run. The following table shows how the status
of the account combinations changes.
01-110-5210 Yes Disabled
04-110-4310 No Enabled
30
03-110-6810 Yes Disabled
Note: After you disable a segment value and sign out of the application and back in, all account combinations
containing that segment no longer work, even if the account combination still shows enabled in the account
combination page. Use the Inherit Segment Value Attribute process to correctly set the enable option on the affected
account combinations.
FAQs for Maintain Segment Values Attributes

How can I change segments in an existing chart of accounts
structure?
The chart of accounts structure and structure instance are fundamental constructs in General Ledger accounting setup
and can't be altered once they're used. The number of segments, the segments' order, each segment's label, length,
type, and value set assignment can't be updated. These components set the foundation upon which accounting data is
recorded for ledgers that use them. Careful and thoughtful planning must precede all decisions pertaining to defining
the chart of accounts.
Overview of Deploying Flexfield

Deployment generates or refreshes the Application Development Framework (ADF) business component objects that
render the flexfield in a user interface. The deployment process adds user-defined attributes to the Web Services
Description Language (WSDL) schemas exposed by Oracle ADF services and used by SOA composites. Flexfields are
deployed for the first time during the application provisioning process. After you configure or change a flexfield, you
must deploy it to make the latest definition available to users.
If a descriptive flexfield is enabled for business intelligence, the deployment process redeploys the flexfield's business
intelligence artifacts.
You can deploy a flexfield to a sandbox for testing or to the mainline metadata for use in a test or production run time
environment. You can deploy extensible flexfields as a background process.
After deployment, the user-defined attributes are available for incorporating into the SOA infrastructure, such as
business process and business rule integration. For example, you can now write business rules that depend on the user-
defined attributes. You must sign out and sign back in to Oracle Applications Cloud to see the changes you deployed at
run time.
31
Related Topics
• Overview of Flexfield Deployment
• How Flexfield Deployment Status is Calculated
• How Deploying a Flexfield-Enabled Sandbox Works with Mainline Metadata
• Considerations for Deploying a Flexfield to a Sandbox
Cross-Validation Rules
Overview of Creating Cross-Validation Rules in a Spreadsheet
The rapid implementation solution provides a template for defining cross-validation rules in a spreadsheet. Cross-
validation rules determine whether a selected value for a particular segment of an account combination can be
combined with specific values in the other segments to form a new account combination.
In the Setup and Maintenance work area, use the following:
• Offering: Financials
• Functional Area: General Ledger
• Task: Create Cross Validation Rules in Spreadsheet
Note: The spreadsheet can only create cross-validation rules. To update existing cross-validation rules, use the
Manage Cross-Validation Rules task in the Setup and Maintenance work area.
Related Topics
• Cross-Validation Rules Spreadsheet
• Create Cross-Validation Rules in a Spreadsheet
• Edit a Cross-Validation Rule
Overview of Managing Cross-Validation Rules

You can use cross-validation rules to determine the valid account combinations that can be dynamically created as
users enter transactions or journal entries. You can also control the creation of new key flexfield code combinations
by defining cross-validation rules. Once enabled, a cross-validation rule determines whether a selected value for a
particular segment of an account combination can be combined with specific values in other segments to form a new
account combination.
32
Related Topics
• Overview of Cross-Validation Rules in General Ledger
• Cross-Validation Rules
• Considerations for Cross-Validation Rules
• How Cross-Validation Rule Violations Are Managed
• Update Existing Setup Data
Segment Rules and Account Rules for Chart of Accounts

Mapping
The chart of accounts mapping feature supports the ability to correlate a source chart of accounts to a target chart of
accounts to allow for the processing of balances or amounts. Use either segment rules, account rules, or a combination
of both in your mapping definitions. A chart of accounts mapping is used by the posting process in propagating
transactions from the primary ledger to its secondary ledger. The mapping feature is used by both balance transfer
processes for balance-level secondary ledgers as well as cross-ledger transfers. The balances are copied from one
ledger to another ledger in both processes.
You can define chart of accounts mappings using the Manage Chart of Accounts Mapping task. If you’re defining
mappings that include only segment rules, you can also use the Chart of Accounts Mapping Rules Import file-based
data import (FBDI).
Segment Rules
Use segment rules to map each segment of the target chart of accounts to an account value, or to one or two segments
in the source chart of accounts. You can select from among three different mapping methods:
• Assign a constant value for a segment in the target chart of accounts.

• Copy the value from the source segment to the corresponding target segment.
Note: To use this method, the value sets for the paired target and source segments must share identical
values.
• Use rollup rules to aggregate one or two source segments to a corresponding target segment.
◦ Create a single value mapping when a specific detail source segment value is given a detail target
segment value.
◦ Use hierarchical rollup rules when a specific parent source value and all of its child segment values are
mapped to a given detail target segment value. This provides the ability to process groups of source
segment values in one single rollup rule.
◦ Define parent source values in rollup rules when date effective versions of the hierarchy are used with the
accounting date of the transactions by the processes that reference the chart of accounts mapping. The
additional benefit of self-maintaining mappings is that if the hierarchies referenced change with time, the
applicable child values are updated automatically.
33
Account Rules
Account rules map a complete target account combination against one or more source account combinations. The
source account combinations can be defined segment by segment using:
• Single detail account values

• Detail account value ranges
• Parent values for primary balancing and natural account segments
Note: When using parent values, its child values for the date effective version of the hierarchy are processed
when the mapping is called.
FAQ for Manage Chart of Accounts Mapping

What's the difference between mapping with segment rules and
mapping with account rules?
Segment rules map target chart of accounts segments to an account value or segment of the source account of a
secondary chart of accounts. A segment is only one part of the account combination.
Account rules map a complete target account combination against one or more source account combinations.
Note: Segment and account rules can be used alone or both types of mapping rules can be used in the same
mapping set.
When do account rules override segment rules in a chart of

accounts mapping?
You can create a chart of accounts mapping using only segment rules, only account rules, or a combination of both
segment and account rules. If an overlap exists between the two types of rule, the account rule supersedes. Segment
rules are used to broadly define the relationship between two charts of accounts on a segment by segment basis.
Account rules can be used to more precisely map specific source account combinations to their target accounts.
Overview of Defining Calendars

Define an accounting calendar to create your accounting year and the periods it contains. Specify common calendar
options that the application uses to automatically generate a calendar with its periods. Specifying all the options makes
defining a correct calendar easier and more intuitive with fewer errors.
34
Related Topics
• Accounting Calendar Options
• How Accounting Calendars Are Validated
FAQs for Define Calendars

How can I identify errors in my accounting calendar?
Oracle Fusion General Ledger identifies erroneous entries online as you enter a new calendar or change data on an
existing calendar. The application also automatically validates the data when you save the calendar.
What's the difference between calendar and fiscal period naming?
The period naming format determines the year that's appended to the prefix for each period in the calendar. For the
example, your accounting year has a set of twelve accounting period with:
• Start date of September 1, 2014.

• End date is August 31, 2015.
• Period's date range following the natural calendar month date range.
Calendar period naming format: Select the calendar period format to append the period's start date's year to the prefix.
For the period covering September 1, 2014 to December 31, 2014, then 2014 or just 14, depending on the period format
selected, is appended to each period's name. For the remaining periods covering January 1, 2015 to August 31, 2015,
then 2015 or 15, is appended to each period's name.
Fiscal period naming format: Select the fiscal period format to always append the period's year assignment to the prefix.
If the accounting periods in the set of twelve are all assigned the year of 2015, then 2015 or just 15, depending on the
period format selected, is appended to the period name of all 12 periods.
When do I update an existing calendar?

Update an existing calendar before the new periods are needed as future periods, based on the future period setting
in your accounting configuration. If a complete year has been defined and validated, use the Add Year button to add
the next year quickly. Accept or change the new rows as required. For example, with the Other frequency type calendar,
dates may differ from what the application generates.
Related Topics
• What happens if I upgrade my calendar from Oracle E-Business Suite Release 12
35
What happens if I upgrade my calendar from Oracle E-Business

Suite Release 12?
The migration script assigns a period frequency that most closely matches your Oracle E-Business Suite Release 12
calendar. When you use the Oracle Fusion applications Add Year functionality for the first time, you have an opportunity
to review and change the period frequency. The Calendar Options page opens only for calendars upgraded from
Release 12 to allow one time modification.
Make your changes to the period frequency, adjusting period frequency, and period name format, including the prefix
and separator, as needed. Changes cannot conflict with the existing upgraded calendar definition. Update the calendar
name and description in the calendar header, as needed, for all calendars. Period details for a new year are generated
automatically based on the latest calendar options. You can also manually update the calendar. The modified calendar
options affect future years only.
Currencies
Considerations for Defining Currencies
Consider these points about entering the currency code, date range, or symbol for the currency, when you create or edit
currencies.
Currency Codes
You can't change a currency code after you enable the currency, even if you later disable that currency.
Date Ranges
You can enter transactions denominated in the currency only for the dates within the specified range. If you don't enter
a start date, then the currency is valid immediately. If you don't enter an end date, then the currency is valid indefinitely.
Symbols
Some applications support displaying currency symbols. You may enter the symbol associated with a currency so that it
appears along with the amount.
Related Topics
• What's the difference between precision, extended precision, and minimum accountable unit for a currency
• What's a statistical unit currency type
• Euro Currency Derivation
36
Euro Currency Derivation

Use the Derivation Type, Derivation Factor, and Derivation Effective Date fields to define the relationship between the
official currency (Euro) of the European Monetary Union (EMU) and the national currencies of EMU member states. For
each EMU currency, you define its Euro-to-EMU fixed conversion rate and the effective starting date. If you have to use
a different currency for Euro, you can disable the predefined currency and create a new one.
Derivation Type
The Euro currency derivation type is used only for the Euro, and the Euro derived derivation type identifies national
currencies of EMU member states. All other currencies don't have derivation types.
Derivation Factor
The derivation factor is the fixed conversion rate by which you multiply one Euro to derive the equivalent EMU currency
amount. The Euro currency itself must not have a derivation factor.
Derivation Effective Date

The derivation effective date is the date on which the relationship between the EMU currency and the Euro begins.
FAQs for Manage Currencies

When do I create or enable currencies?
Create or enable any currency for displaying monetary amounts, assigning currency to ledgers, entering transactions,
recording balances, or for any reporting purpose. All currencies listed in the International Organization for
Standardization (ISO) 4217 standard are supported.
The default currency is set to United States Dollar (USD).
Related Topics
• Considerations for Defining Currencies
What's the difference between precision, extended precision, and

minimum accountable unit for a currency?
Precision refers to the number of digits placed after the decimal point used in regular currency transactions. For
example, USD would have 2 as the precision value for transactional amounts, such as $1.00.
Extended precision is the number of digits placed after the decimal point and must be greater than or equal to the
precision value. For calculations requiring greater precision, you can enter an extended precision value such as 3 or 4.
That would result in the currency appearing as $1.279 or $1.2793.
37
Minimum accountable unit is the smallest denomination for the currency. For example, for USD that would be .01 for a
cent.
You can set these values for a currency using the Manage Currencies task in the Application Extensions functional area
in the Setup and Maintenance work area.
Conversion Rate Types

Guidelines for Creating Conversion Rate Types
Maintain different conversion rates between currencies for the same period using conversion rate types. The following
conversion rate types are predefined:
• Spot
• Corporate
• User
• Fixed
You can use different rate types for different business needs. During journal entry, the conversion rate is provided
automatically based on the selected conversion rate type and currency, unless the rate type is User. For User rate types,
you must enter a conversion rate. You can define additional rate types as needed. Set your most frequently used rate
type as the default. Conversion rate types can't be deleted.
Assign conversion rate types to automatically populate the associated rate for your period average and period end
rates for the ledger. For example, you can assign the conversion rate type of Spot to populate period average rates, and
the conversion rate type of Corporate to populate period end rates. Period average and period end rates are used in
translation of account balances.
Conversion rate types are used to automatically assign a rate when you perform the following accounting functions:
• Convert foreign currency journal amounts to ledger currency equivalents.

• Convert journal amounts from source ledgers to reporting currencies or secondary ledgers.
• Run revaluation or translation processes.
When creating conversion rates, decide whether to:
• Enforce inverse relationships

• Select pivot currencies
• Select contra currencies
• Enable cross rates and allow cross-rate overrides
• Maintain cross-rate rules
Enforce Inverse Relationships

The Enforce Inverse Relationship option indicates whether to enforce the automatic calculation of inverse conversion
rates when defining daily rates. The following table describes the impact of selecting or not selecting the option.
38
Action Results
Selected When you enter a daily rate to convert currency A to currency B, the inverse rate of currency B to
currency A is automatically calculated and entered in the adjacent column. If either rate is changed, the
application automatically recalculates the other rate.
You can update the application calculated inverse rate, but once you do, the related rate is updated.
The option enforces the inverse relationship is maintained but doesn't prevent you from updating the
rates.
Not Selected The inverse rate is calculated, but you can change the rate and update the daily rates table without the
corresponding rate being updated.
Select Pivot Currencies

Select a pivot currency that's commonly used in your currency conversions. A pivot currency is the central currency that
interacts with contra currencies. For example, you set up a daily rate between the US dollar (USD) and the Euro currency
(EUR) and another between the USD and the Canadian dollar (CAD). USD is the pivot currency in creating a rate between
EUR and CAD. EUR and CAD are the contra currencies. Select the pivot currency from the list of values which contains
those currencies that are enabled, effective, and not a statistical (STAT) currency. The description of the pivot currency is
populated automatically based on the currency definition.
If you want the application to create cross rates against a base currency, define the base currency as the pivot currency.
Selected pivot currencies can be changed in the Rate Types page.
Select Contra Currencies

Select currencies available on the list of values as contra currencies. The available currencies are those currencies which
are enabled, effective, not STAT currency, and not the pivot currency selected earlier. The description of the contra
currency is populated automatically based on the currency definition. Add or delete contra currencies in the Contra
Currencies region of the Rate Types page.
Enable Cross Rates and Allow Cross Rate Overrides

Check the Enable Cross Rates check box to calculate conversion rates based on defined currency rate relationships.
General Ledger calculates cross rates based on your defined cross rate rules. Associate your cross rate rules with
a conversion rate type, pivot currency, and contra currencies. Cross rates facilitate the creation of daily rates by
automatically creating the rates between contra currencies based on their relationship to a pivot currency. If the Enable
Cross Rates option is deselected after entering contra currencies, the application stops calculating cross rates going
forward for that particular rate type. All the earlier calculated cross rates for that rate type remain in the database unless
you manually delete them.
For example, if you have daily rates defined for the pivot currency, USD to the contra currency, EUR, and USD to another
contra currency, CAD, the application automatically creates the rates between EUR to CAD and CAD to EUR. You don't
have to manually define the EUR to CAD and CAD to EUR rates.
Select the Allow Cross Rates Override check box to permit your users to override application generated cross rates. If
you accept the default of not selected, the application generated cross rates can't be overridden.
Maintain Cross Rate Rules

Define or update your cross rate rules at any time by adding or removing contra currency assignments. Add a contra
currency to a cross rate rule and run the Daily Rates Import and Calculation process to generate the new rates. If you
39
remove a cross rate rule or a contra currency from a rule, any cross rates generated previously for that contra currency
remain unless you manually delete them. Changes to the rule aren't retroactive and don't affect previously stored cross
rates. The Cross Rate process generates as many rates as possible and skips currencies where one component of the set
is missing.
Note: With a defined web service that extracts daily currency conversion rates from external services, for example
Reuters, currency conversion rates are automatically updated for the daily rates and all cross currency relationships.
Related Topics
• Examples of Using Conversion Rate Types in a Journal
• What's the difference between calendar and fiscal period naming
Examples of Using Conversion Rate Types in a Journal

The four predefined conversion rate types are:
• Spot
• Corporate
• User
• Fixed
Scenario
You are the general ledger accountant for Vision US Inc. You are entering a journal entry to capture three transactions
that were transacted in three different foreign currencies.
• Canadian Dollar CAD: A stable currency

• Mexican Peso MXP: A fluctuating currency
• Hong Kong Dollar HKD: An infrequently used currency
You enter two journal lines with accounts and amounts for each foreign currency transaction. Based on your company
procedures, you select the rate type to populate the rate for Corporate and Spot rate types from your daily rates table.
You manually enter the current rate for the User rate type.
The following table lists the currency, the rate type that you select, and the reasons for the rate type selection.
Selected Currency Selected Rate Type Reason
CAD Corporate Entered a periodic type of transaction. Your

company has established a daily rate to use
for the entire month across divisions for all
transactions in Canadian dollars, a stable
currency that fluctuates only slightly over the
month.
MXP Spot Entered a periodic type of transaction. Your

company enters daily rates each day for the
Mexican peso because the currency is unstable
and fluctuates.
40
Selected Currency Selected Rate Type Reason
HKD User Entered a one time transaction. Your company

doesn't maintain daily rates for Hong Kong
dollars.
Your company doesn't currently use the Fixed rate type. From January 1, 1999, the conversion rate of the French franc
FRF against the Euro EUR was a fixed rate of 1 EUR to 6.55957 FRF. Your French operations were started in 2007, so you
maintain all your French business records in the Euro.
FAQs for Manage Conversion Rate Types

What's the difference between spot, corporate, user, and fixed rate
types?
Spot, corporate, user, and fixed conversion rate types differ based on fluctuations of the entered foreign currency and
your company procedures for maintaining daily rates.
• Spot: For currencies with fluctuating conversion rates, or when exact currency conversion is needed.
• Corporate: For setting a standard rate across your organization for a stable currency.
• User: For infrequent entries where daily rates for the entered foreign currency aren't set up.
• Fixed: For rates where the conversion is constant between two currencies.
If you have infrequent foreign currency transactions, the User rate type can simplify currency maintenance. The User
rate type can also provide an accurate conversion rate on the date of the transaction.
What's a statistical unit currency type?

The statistical unit currency type denotes the Statistical (STAT) currency used to record financial statistics in the
financial reports, allocation formulas, and other calculations.
Daily Currency Rates

Overview of GL Currency Rates Upload
Oracle Cloud ERP has various options to load currency rates. In Oracle Cloud ERP, daily currency conversion rates can
be maintained between any two currencies. You can enter daily conversion rates for specific combinations of foreign
currency, date, and conversion rate type. Oracle Cloud ERP automatically calculates inverse rates. You can override the
inverse rates that are automatically calculated.
41
The three different methods of loading currency rates are:
1. Manual load using the Create Daily Rates spreadsheet.

2. Manual load using the Import and Calculate Daily Rates file-based data import.
3. Automatic load using web services.
Related Topics
• Required Security for Loading GL Currency Rates
• Enter Daily Rates Using the Daily Rates Spreadsheet
• Load Daily Rates Automatically Using Web Services
• How Daily Rate Import Data Is Processed
Update Currency Rates

You're required to change today's daily rates that were already entered. The rates you're changing are for currency
conversion from Great Britain pounds sterling (GBP) to United States dollars (USD) for your company InFusion America.
Currency conversion rates were entered by an automatic load to the Daily Rates table. They can also be entered through
a spreadsheet.
Updating Currency Rates

1. Navigate to the Period Close work area.
Use the Period Close work area to link to close processes and currency process.
2. Click the Manage Currency Rates link.
Use the Currency Rates Manager page to create, edit, and review currency rate types, daily rates, and historical
rates.
3. Click the Daily Rates tab.
Use the Daily Rates tab to review and enter currency rates.
4. Click the From Currency list. Select the GBP - Pound Sterling list item.
5. Click the To Currency list. Select the USD - US Dollar list item.
6. Enter the dates for the daily rates that you are changing. Enter today's date.
7. Click the Rate Type list. Select the Spot list item.
8. Click the Search button.
9. Click in the Rate field. Enter the new rate of 1.7 in the Rate field.
10. Click in the Inverse Rate field. Enter the new inverse rate of 0.58822 in the Inverse Rate field.
11. Click the Save button.
Related Topics
• Guidelines for Using Desktop Integrated Excel Workbooks
42
Implementing Accounting Hub Ledgers
4 Ledgers
Overview of Ledger and Subledgers

Oracle Fusion Applications reflect the traditional segregation between the general ledger and associated subledgers.
Detailed transactional information is captured in the subledgers and periodically imported and posted in summary or
detail to the ledger.
A ledger determines the currency, chart of accounts, accounting calendar, ledger processing options, and accounting
method for its associated subledgers. Each accounting setup requires a primary ledger and optionally, one or more
secondary ledgers and reporting currencies. Reporting currencies are associated with either a primary or secondary
ledger.
The number of ledgers and subledgers is unlimited and determined by your business structure and reporting
requirements.
Related Topics
• Ledgers and Subledgers
• Primary Ledgers, Secondary Ledgers, and Reporting Currencies
• Ledgers, Legal Entities, Balancing Segments, and Business Units
• Create a Primary Ledger
• Specify Ledger Options
FAQs for Specify Ledger Options

What happens if I change the cumulative translation adjustment
account?
Changing the cumulative translation adjustment (CTA) account is a very significant revision to your accounting
configuration and should be avoided if possible. To prevent data corruption, your CTA can only be changed if you delete
translated balances.
Related Topics
• How Translated Balances Are Deleted
43
What happens if I change the retained earnings account?

Changing the retained earnings account is a very significant revision to your accounting configuration and should be
avoided if possible. To prevent data corruption, your retained earnings account can only be changed if you first perform
the following set of steps:
1. To reverse what was closed out to the incorrect retained earnings account, enter and post journals to bring
the ending balances for your income statement accounts to zero at the end of each accounting year. Use a
temporary account, such as a suspense account, for the offsetting amount.
2. Update the retained earnings account.
3. Reverse the journal entries used to bring the income statement accounts' ending account balances to zero to
reinstate each accounting year's profit and loss, and now close these out to the new retained earning's account
in the following accounting year.
Note: The recommended reversal method for the journals is Change Sign.
4. If you have translated balances for the ledger, follow the process of deleting translated balances for a change in
the retained earnings account.
Related Topics
• How Translated Balances Are Deleted
Accounting Configuration
Overview of Accounting Configuration
A balances cube stores financial balances in a multidimensional database for interactive reporting and analysis.
A ledger has a chart of accounts, calendar, currency, and accounting method. When the accounting configuration
process is submitted for a primary or secondary ledger that uses a new unique combination of chart of accounts and
calendar, a balances cube is created.
Related Topics
• Overview of Oracle General Ledger Balances Cubes
• Dimensions for Standard Balance Cubes
• Examples of Standard and Average Balances Cubes
• Considerations for GL Balance Cube Dimension Values That Are Customer-Specific
• Levels and Generations in GL Balances Cubes
Overview of Dimension Values in Reporting

For Standard Balances Cube dimensions, there are default values that if used in Smart View and on financial reports
created in Financial Reporting Studio cause #MISSING to appear when balances are returned on a report output. If
44
#MISSING appears, check that all dimensions are properly set. Particularly, check the Accounting Period, Ledger,
Scenario, and Currency dimensions, which all must have a value selected other than the default highest level value
called Gen1.
By using combinations of values for the Accounting Period, Balance Amount, and Amount Type dimensions, you can
derive different amounts to meet financial reporting requirements. In some cases, more than one combination of query
values can return the wanted information. Some duplication in the calculations for the balances cube exists to ensure
complete reporting requirements.
Related Topics
• Examples of Using Dimension Values in Reporting
• Example of Standard Balances
• Invalid Combinations of Balance Cube Dimensions
• GL Balance Cube Processes Run from User Interface
• GL Balance Cube Processes Run from Scheduled Processes Work Area
FAQs for Accounting Configuration

How can I inquire on translated balances?
You can query on Currency Type equal to Total and Currency equal to Translated Currency.
When do I rebuild the GL balances cubes?

Carefully consider requirements and work with Oracle Support before rebuilding a balances cube. Use the on-demand
programs to rebuild dimension members for each dimension and to refresh balances to the cubes rather than rebuilding
the cube. When you rebuild a cube, the process rebuilds both the standard and average balances cubes.
To rebuild cubes, run the Create Cubes process. Enter values for the following parameters:
• Chart of Accounts
• Accounting Calendar
• Starting Period
How can I refresh balances in the GL balances cubes?

Run the General Ledger Transfer Balances to Essbase process. Select your Ledger or Ledger Set and Starting Period
as parameters
45
Assign Access to Ledger

Assign Legal Entities and Balancing Segments
Optionally, assign legal entities and balancing segments to your accounting configuration.
Assign Legal Entities

Assign one or more legal entities to your accounting configuration by following these steps:
1. In the Setup and Maintenance work area, go to the following:
◦ Offering: Financials
◦ Functional Area: General Ledger
◦ Task: Assign Legal Entities, with the ledger scope set
2. Click the Select and Add icon.
3. Enter your legal entity information.
4. Click Apply.
5. Click Done.
6. Click Save and Close.
Assign Balancing Segments to Legal Entities

Assign balancing segment values to your legal entities by following these steps:
◦ Task: Assign Balancing Segment Values to Legal Entities, with the ledger scope set
2. Click the Create icon.
3. Select the balancing segment value. Optionally, add a start date.
4. Click Save and Close to close the Assign Company Values window.
Assign Balancing Segments to Ledgers

Assign balancing segment values directly to your ledger by following these steps:
◦ Task: Assign Balancing Segment Value to Ledger, with the ledger scope set
2. Select the balancing segment value.
46
3. Optionally enter a start date.

Note: The balancing segment values that are assigned to the ledger represent nonlegal entity transactions, such as
adjustments. If you use legal entities, you must assign balancing segment values to all legal entities before assigning
values to the ledger. The only available balancing segment values that can be assigned to ledgers are those not
assigned to legal entities.
Related Topics
• Overview of Balancing Segments
General Ledger Security

Overview of General Ledger Security
Oracle Financials Cloud predefines common job roles such as Accounts Payable Manager and General Accounting
Manager. You can use these roles, modify them, or create job roles as needed. A user can be assigned more than one
role, so don't define a role that includes all the accesses needed for every user.
For a listing of the predefined job roles in Oracle Financials Cloud and their intended purposes, see the Oracle Financials
Cloud Security Reference Manual in the Oracle Help Center (http://docs.oracle.com).
For more information on securing your applications, see the Oracle ERP Cloud Securing Oracle ERP Cloud guide in the
Oracle Help Center (http://docs.oracle.com).
Related Topics
• Overview of General Ledger Security
• Overview of Data Access Set Security
• Examples of Data Access Set Security
• Segment Value Security
• Example of Segment Value Security
Considerations for Enabling General Ledger Security

Enabling General Ledger Security requires taking some key decisions. Some key decisions to consider are as follows:
• Which segment in the chart of accounts must be restricted?
• Which cost center values have to be granted to different users?
• What's the name of the value set for the segment with the Cost Center label?
• What's the name of the user who can access cost centers 110 to 120?
• What's the name of the tree for the accounting flexfield?
47
• What version of the tree hierarchy does the condition apply to?
Related Topics
• Enable Security on a Chart of Accounts
• Other Financials Security Considerations
• Data Security Differences in GL Features Based on Balance Cubes
FAQs for Manage General Ledger Security

When does security take effect on chart of accounts value sets for
balances cubes?
To enforce segment value security according to defined security policies, you must enable security on the value set
before you publish the affected account hierarchies to the balances cube. Likewise, to stop enforcing segment value
security for a previously secured value set, you must disable security on the value set and then republish the account
hierarchies.
Once segment value security is enforced, you don't have to republish account hierarchies if you define new security
policies or modify existing policies for the secured value set, even if the security definition has hierarchical conditions
that use parent values.
Note: If you change an account hierarchy that's already published, you must republish to reflect the updated
hierarchy in the balances cube. Use the Publish Account Hierarchy task to republish the tree version. Republishing
the account hierarchy also ensures proper enforcement of security policies that are based on parent values included in
the changed hierarchy.
What happens when changes are made to an account hierarchy

that's referenced in segment value security rules?
The tree is set from an active to a draft state. The rules referencing the account hierarchy become ineffective.
After making changes to your hierarchy, you can submit the Process Account Hierarchies process to automatically run
the required steps for processing account hierarchies updates in one submission, including:
• Tree audit
• Tree activation
• Row flattening
• Column flattening
• Maintain value set
• Maintain account hierarchy
• Publish hierarchy
48
With a successful audit process, the hierarchy is set back to an active status. The rules referencing the account hierarchy
go back to being effective using the updated hierarchy.
Run the row and column flattening processes for the updated hierarchy as the flexfield component in the application as
well as other hierarchy processes rely on the flattened hierarchy data to come up with the list of values available to the
user to properly secure the correct account values.
Run the Maintain Value Sets and Maintain Chart of Account Hierarchies processes, particularly for hierarchy changes
to the primary balancing segment value set if such values are referenced in your primary balancing segment value
based data access sets. These processes update the data that is required to regulate ledger and data access security by
storing:
• Primary balancing segment values assigned to a ledger.

• Specific child balancing segment values assigned to a data access set through parent value assignments.
How can I secure the data in GL balances cubes?

Use data access set and segment value security to secure dimension values such as ledger and chart of account values.
For chart of accounts dimension values, security restricts the display of data associated with the secured values, but
not the selection of the values themselves. For example, when submitting a report, you can select company value 100
in your report definition when selecting the Point of View, even if you weren't granted access to that company value.
However, you can't see the data associated with company 100 in your report.
How Balances for Reporting Currencies Are Calculated

Reporting currency balances, set at the journal or subledger level, are updated when General Ledger journals are posted
and converted to your reporting currencies. This process includes:
• General Ledger manual journals, periodic journals, and allocations.

• At the subledger level, journals from Oracle Fusion Subledger Accounting.
• Other journals imported from sources other than your Oracle Fusion subledgers.
When you post a journal in a ledger that has one or more reporting currencies defined, the posting process:
• Creates journals converted to each of your reporting currencies.

• Includes them in the same batch as the original journal with a status of Posted.
Settings That Affect Reporting Currency Balances

Reporting currencies share a majority of the ledger options with their source ledger. For example, the reporting currency
uses the same suspense account and retained earnings accounts as its source ledger. However, there are certain
options that must be set specifically for reporting currencies, such as the currency conversion level. The currency
conversion levels are Balance, Journal, and Subledger.
Note: Secondary ledgers can't use subledger level reporting currencies.
49
Multiple dependencies exist between a reporting currency and its source ledger. Therefore, complete your period
opening tasks, daily journal or subledger level reporting currencies accounting tasks, and period closing tasks in the
correct order. The following table describes some of the tasks for each task type.
Type Tasks
Period Opening Open the accounting period in both your ledger and reporting currencies before you create or import
journals for the period. Converted journals are only generated in your reporting currency if the period
is open or future enterable.
Daily Enter daily conversion rates to convert journals to each of the reporting currencies.
Period Closing • Finish entering all regular and adjusting journals for the period in your ledger.
• Post all unposted journals in your ledger if not already done in the previous step.
• Post all unposted journals in your reporting currencies if not already done in the previous step.
• Run revaluation in both your ledger and reporting currencies. Post the resulting revaluation
batches in each ledger.
• As needed, translate balances in your ledger.
• Generate needed reports from both your ledger and reporting currencies.
• Close your accounting period in both your ledger and reporting currencies.
How Reporting Currencies Are Calculated

If you use reporting currencies at the journal or subledger level, journals are posted in your reporting currency when
you:
• Create accounting.
• Post journal entries.
• Translate balances.
General Ledger and Subledger Accounting automatically generate journals in your reporting currencies where the
entered currency amounts are converted to the reporting currency amounts. Other factors used in the calculation of
reporting currency balances are listed:
• Manual Journals: Enter a manual journal batch in your reporting currency at the journal or subledger level by
using the Create Journals page. Select the journal or subledger level reporting currency from the ledger's list of
values. Continue in the same manner as entering any other manual journal.
• Conversion Rounding: Use the reporting currency functionality to round converted and accounted amounts
using the same rounding rules used throughout your Oracle Fusion Applications. The reporting currency
functionality considers several factors that are a part of the currencies predefined in your applications,
including:
◦ Currency Precision: Number of digits after the decimal point used in currency transactions.
◦ Minimum Accountable Unit: Smallest denomination used in the currency. This might not correspond to
the precision.
• Converted Journals: Generate and post automatically journals in your reporting currencies when you post the
original journals in the source ledger for the following types of journals:
50
◦ Manual journals
◦ Periodic and allocation journals
◦ Unposted journals from non-Oracle subledger applications
◦ Unposted journals from any Oracle Fusion subledger that doesn't support reporting currency transfer
and import
◦ Optionally, revaluation journals
• Unconverted Journals: Rely on the subledger accounting functionality to convert and transfer Oracle Fusion
subledger journals, for both the original journal and the reporting currency journal, to the General Ledger
for import and posting. The reporting currency conversion for these journals isn't performed by the General
Ledger.
• Approving Journals: Use the journal approval feature to process reporting currency journals through your
organization's approval hierarchy. You can enable journal approval functionality separately in your source
ledger and reporting currencies.
• Document Numbers: Accept the default document numbers assigned by the General Ledger application to your
journal when you enter a journal in your ledger. The converted journal in the reporting currency is assigned
the same document number. However, if you enter a journal in the reporting currency, the document number
assigned to the journal is determined by the reporting currency.
• Sequential Numbering: Enable sequential numbering to maintain the same numbering in your reporting
currency and source ledger for journals, other than those journals for Oracle Fusion subledgers. Do not create
separate sequences for your reporting currencies. If you do, the sequence defined for the reporting currencies
is used. The sequences can cause the document numbers not to be synchronized between the ledger and
reporting currencies.
Note: General Ledger enters a document number automatically when you save your journal if:
◦ The Sequential Numbering profile option is set to Always Used or Partially Used.
◦ Automatic document numbering sequence is defined.
If you use manual numbering, you can enter a unique document number.
• Revaluation: Run periodically revaluation in your ledger and reporting currencies as necessary to satisfy the
accounting regulations of the country in which your organization operates.
• Account Inquiries: Perform inquires in the reporting currency. You can:
◦ Drill down to the journal detail for the reporting currency balance.
◦ Drill down to see the source ledger currency journal amounts from any automatically converted journal
that was created when the original journal posted.
Note: Be careful when changing amounts in a reporting currency, since the changes aren't reflected in your source
ledger. Making journal entry changes to a reporting currency makes it more difficult to reconcile your reporting
currency to your source ledger. In general, enter or change your journals in your source ledger, and then allow posting
to update the reporting currency.
Note: If you use journal or subledger level reporting currencies, statistical journals are generated for your reporting
currencies, but the journals aren't converted.
51
Examples of Ledger Sets

When you use multiple ledgers, you can group all types of ledgers in a ledger set. For example, group primary ledger,
secondary ledgers, and reporting currencies (journal and subledger levels) as long as they share the same chart of
accounts, calendar and period type.
Ledger sets are used to manage ledgers, including:

• Opening and closing of periods.
• Running reports and processes for multiple ledgers simultaneously.
• Supporting adjustments and allocations.
Regulation Requirements Example

You have 26 registered companies in Vision Corporation. The regulations require that each company is to maintain a
separate ledger. All companies share the same chart of accounts and calendar.
You set up a ledger for each company and group them into a ledger set. You can then use the ledger set to perform all
accounting activities, while the data remains partition for reporting purpose for each company.
Multiple Countries Example

You have a parent company in one country. You operations in five other countries. Each country has its own legal entity
and must report to both the parent company and the local government. All legal entities use the same chart of accounts
and calendar. Currency is different and Reporting Currency ledgers have been created. You can group all of the primary
and reporting currencies ledgers into one Ledger Set. You can then perform all accounting activities as though you had
one worldwide ledger.
Accounting and Reporting Sequences

Overview of Accounting and Reporting Sequences
When you record your journals, you can assign unique sequence numbers. Sequence numbering the journals simplifies
the task of tracing the journal entries and is a legal requirement in some countries, especially those in Europe, Asia, and
Latin America. Sequencing enables the fiscal authorities to easily verify the completeness of a company's accounting
record.
Sequential numbering of journals enables you to:

• Maintain gapless sequence numbers.
• Sequentially number subledger journal entries. Generate a sequence number for journal entries created by
subledger accounting before transferring them to general ledger.
• Sequentially number general ledger journal entries.
• Assign sequences within a ledger or legal entity.
• Generate reports based on the sequence numbers.
52
The two different types of journal sequences used with Subledger Accounting and General Ledger journals are:
• Accounting Sequences: Gapless sequence numbering for journals which is assigned when the journals are
posted or subledger accounting runs.
• Reporting Sequences: Gapless and chronological sequence numbering which is assigned to journals when the
General Ledger period is closed.
Note: You can sequence journals for ledgers (primary and secondary ledgers) and journal level and subledger level
reporting currencies as well as legal entities. If you use journal or subledger level reporting currencies, first define
sequences for the source ledger. The sequence number generated for the source ledger isn't automatically assigned
to the reporting currency journal. You must then set up accounting and reporting sequences separately for the
reporting currencies.
Related Topics
• How to Define Journal Sequences Manually
• Create Chart of Accounts, Ledger, Legal Entities, and Business Units in Spreadsheets
• Document Sequences
• Document Sequence Categories
• Guidelines for Managing Document Sequences
How to Define Journal Sequences Manually

You can manually define sequences to generate numbers for journal entries. Use the Manage Accounting and Reporting
Sequences task to search, create, and update sequences, sequence versions, and sequencing assignments. You can also
create journal sequences using the Rapid Implementation process. The process creates and assigns the sequences.
Sequences
Create, update, and search for sequences from the Sequences tab on the Manage Accounting and Reporting Sequences
page. To define a sequence, enter a unique sequence name and description. Create at least one sequence version to
complete the sequence. The sequence version indicates the series of sequence numbers to be used and the effective
date range of the series.
When you create a sequence version, you specify the:
• Effective Start Date: The default date is the current date. The date can be set to any date in the past or future.
• Effective End Date: The date when the sequence should be disabled.
• Initial Number: A positive integer that's the starting number of the sequence. The number increments by one
for each accounting entry.
Note: The Edit Sequences page displays the last sequence number used for each sequence version.
53
Sequencing Assignments
After creating your sequences, assign them various criteria to specify when the sequences are generated. Use the
Sequencing Assignments tab on the Manage Accounting and Reporting page to search, update, or create sequencing
assignments.
The following table describes the fields on the Sequencing Assignments tab.
Field Description
Ledger The ledger for which the journal entries must be sequentially numbered or that contains the legal
entity.
Legal Entity The legal entity for which the journal entries must be sequentially numbered. The Legal Entity field
appears when you set your Sequence By ledger option to Legal Entity.
Journal Entry Type Select whether general ledger or subledger entries are being sequentially numbered.
Sequencing Event The event which triggers the sequence numbering,
Sequence Validation Date The date when generating a sequence number. This date is used to determine if a sequence is available
and the sequence assignment is active.
Require Assignment for All Journals If you select this option, you must explicitly define valid Sequence Assignments, Exceptions, or
Exclusions for all journal entries.
Status Indicates if the assignment is enabled or disabled.
The following table outlines some of the different combinations of journal entry type, sequencing event, sequence
validation date, journal sorting date. For each combination, the table also indicates whether the sequence is an
accounting or reporting sequence.
Journal Entry Type Sequencing Event Sequence Validation Date Journal Sorting Date Remark
General Ledger Posting Accounting Date Accounting Date Accounting Sequence
Subledger Accounting Subledger Accounting Accounting Date Completion or Posting Date Accounting Sequence
or Accounting Date
General Ledger Period Close Accounting Date Accounting Date Reporting Sequence
General Ledger Period Close Reference Date Reference Date Reporting Sequence
Subledger Accounting Period Close Accounting Date of Reference Date Reporting Sequence
Reference Date
54
Tip: For reporting sequences, you can specify fiscal balancing segment values to specify what balancing segment
values to use with reporting sequences for period close. You can deselect the option to exclude balancing segments
with management type journals or nonfinancial journals such as, statistical journals.
The following figure shows the Fiscal Balancing Segment Values section from the Sequencing Assignment page. The
section includes the segment value, description, and an indicator for whether the segment value is selected for use with
the reporting sequence.
Sequencing Assignment Details

The following table lists and describes the fields in the Sequences section on the Create Sequencing Assignment page.
Field Description
Status Status of the assignment such as New or Used.
Priority Priority of the exception. This option is inactive unless you define an exception.
Sequence Name Name of the sequence to be assigned. A blank indicates the entries must not be sequenced.
Start Date Define the effective start date for the sequence assignment.
End Date Define the effective end date for the sequence assignment.
Journal Source Select the journal sources from the list to be sequentially numbered for a sequence event.
Journal Category Select the journal categories from the list to be sequentially numbered for a sequence event.
Accounting Event Type Select the accounting event types to be sequentially numbered (only for subledger entries).
Accounting Entry Type Select the accounting entry types to be sequentially numbered (only for subledger entries).
Document Category Select to group transactions assigned to the sequence.
55
The following figure shows the Add Exception and Add Exclusion buttons on the Create Sequencing Assignment page.
Use the following buttons to add a row:
• Add Exception: When you create an exception, the priority value is always one more than the highest number
in the Priority field. Use exceptions to assign different sequences to certain journal sources, journal categories,
accounting event types, or accounting entity types. For example, you want to include all journal sources, but
assign a different sequence for your Expense journals.
• Add Exclusion: Create exclusions to exclude specific journal sources, journal categories, accounting event
types, or accounting entity types. For example, you want to exclude journal sources and categories containing
management or statistical accounts that don't impact financial results.
FAQs for Manage Accounting and Reporting Sequences

What happens when I enable sequencing in the rapid
implementation spreadsheet?
Two sets of defaults are generated: general and country specific. The process applies the general defaults first and the
country specific defaults override general defaults. For example, using the predefined defaults, sequencing is enabled
at the ledger level. For some countries like Spain and Italy, the general defaults are overridden by country defaults and
sequences are set at the legal entity level.
Accounting and reporting sequences are generated based on the predefined country defaults. For example, for a France
ledger, accounting sequences are generated for each legal entity of the ledger. For an Italian ledger, both accounting
and reporting sequences are generated for each legal entity of the ledger.
Journal Approval Rules

Example of Creating Journal Approval Rules
You can use the Business Process Management Worklist application to configure journal approval rules. For example,
you can create journal approval rules that automatically approve a journal batch, or that route the batch for approval
based on the ledger and journal amounts.
56
This procedure creates the following approval rules:

• When the largest journal amount in a batch is more than 500, and less than 10,000, the batch requires one level
of supervisory approval.
• When the largest journal amount is 10,000 or more, two levels of supervisory approval are required.
• If the largest journal amount in a batch is 500 or less, the batch doesn't require approval or it's automatically
approved.
Create a Rule That Requires One Level of Supervisory Approval

1. In the Global menu, click the Notifications icon and select More Details. If you're using the news feed default
home page layout, then select Show All and click Worklist.
2. Select Financials. The Business Process Management Worklist application page opens.
3. Click your user name and select Administration. You can manage the journal approval rules only if you have
administrator access.
4. Click the Task Configuration tab.
5. From the Tasks to be configured pane, select the FinGLJournalApproval task.
6. Click Edit task to create the rules.
7. Click the Assignees tab. The Assignees page shows the participant tree. A participant is a user or set of
users in the approval assignment and routing definition. The journal approval task displays three predefined
participants. Typically you use only one or two participants, but have the flexibility to add more participants to
meet more complex approval requirements. Each participant is associated with one rule set, and a rule set can
have one or more approval rules.
8. On the Supervisory Journal Approver participant, click Go to rule.
9. Click the Expand icon on the Manager Approval Rule. That's the default predefined approval rule. If a journal's
ledger and source are enabled for approval, the rule is configured to send that journal for one level of approval
to the supervisor of the person who submitted the journal for approval.
10. Click the Show Advanced Settings icon.
11. Click in the Active check box to deselect it. When this check box is cleared, the approval routing process doesn't
use the rule.
12. Click the Add Rule icon.
13. In the Name field, enter the name of the rule: Between 500 and 10000.
14. Click Expand. Each rule defines the conditions for when the journal batch should be approved and by whom.
Note: The IF component evaluates the journal based on batch, journal, or journal line-level attributes. The
THEN component determines who the approval should be routed to.
15. In the IF section, click the Left Value icon. The Condition Browser window opens.
16. Click the Expand icon on the Maximum Amount Journal folder.
17. Click the Name attribute, which represents the ledger name.
18. Click OK. The Condition Browser window closes and the attribute name is populated in the Left Value field.
19. In the Right Value field, enter the name of the ledger in quotation marks, for example, enter "Vision
Corporation".
Note: The first condition uses the operator named is. This operator compares the two values.
20. Click the Add simple test icon from the list to add another condition.
21. Click the Left Value icon. The Condition Browser window opens.
22. Expand the Maximum Journal Amount folder and select the Maximum Accounted Amount Credit attribute.
This attribute stores the maximum accounted credit amount across all journals in the batch.
23. Click OK. The Condition Browser window closes.
57
24. In the second condition, click in the Operator field and select the operator named between.
25. Click the Right Value icon. The Right Operand window opens.
26. In the Operand 1 field, enter the lower limit as 500.
27. In the Operand 2 field, enter the upper limit as 10000.
28. Click OK. The Right Operand window closes.
29. To configure the action to send the journal batch for one level of supervisory approval, click the Add Action
icon in the THEN section.
30. Select Add Approver and select Supervisory.
Note: The Supervisory list builder generates the list of approvers by moving up the supervisory hierarchy
that's set up in the Human Resources application. Specify the number of approvers, the first approver, and
the highest possible approver.
31. To route the journal batch for one level of supervisory approval, in the Number of levels field, enter 1.
32. In the Starting Participant field, click Search. The Add Hierarchy Participant window opens and the Get
Manager option is selected by default.
33. For this rule, the starting participant or first approver, is going to be the manager of the person who submits
the journal batch for approval. In the Reference User field, enter Task.Workflow Submitter.
34. Click OK. The Add Hierarchy Participant window closes.
35. In the Top Participant field, click Search. The Add Hierarchy Participant window opens.
Note: The top participant is the last user in the approval hierarchy. The list builder continues to add users to
the approvers list from the supervisory hierarchy of the first approver, until the number of levels is met, or the
top participant is reached.
36. Click the Get User button.

37. In the Reference User field, enter the sign in name of the top participant within quotation marks.
38. Click OK. The Add Hierarchy Participant window closes.
39. From the Tasks to be configured pane, click Save. The Enter Comments window opens.
40. Click OK. The Enter Comments window closes and a message appears stating that the rule has been saved.
41. Click OK.
Create a Rule That Requires Two Levels of Supervisory Approval

Create a rule for the same ledger requiring two levels of supervisory approval if the largest journal amount is 10,000 or
more. Copy the first rule and make changes for this second rule.
1. Click the Assignees tab.

2. Select the first rule.
3. Click the list on the Cut icon and select Copy.
4. Click the list on the Cut icon and select Paste. The second rule appears after the first rule.
5. In the Name field for the second rule, enter Greater than 10000.
6. Click Expand.
7. The first condition in the IF section that checks for the ledger, stays the same. Change the operator of the
second condition to same or more than.
8. In the Right Value field, enter 10000.
9. In the THEN section, in the Number of levels field, enter 2.
10. Click Collapse. The second approval rule is complete.
Create a Rule That Automatically Approves Journals

Create the rule that automatically approves journals that are 500 or less for a specific ledger. The rule must also ensure
that journal batches for all other ledgers are automatically approved as well.
58
CAUTION: It's very important that the rules in a rule set cover all conditions and are collectively exhaustive. If not,
errors might occur.
1. Select the first rule.

2. Click the list on the Cut icon and select Copy.
3. Click the list on the Cut icon and select Paste. The third rule appears after the first rule.
4. Click in the Rule Name field and rename the third rule to Less than 500.
5. Click the Expand icon to open the new rule.
6. Create a condition for journals 500 or less in the specified ledger by first grouping the two existing conditions
together. In the IF section, click both conditions to select them.
7. Click the Surround selected tests with parenthesis icon. Both conditions are now enclosed within a set of
parentheses.
8. Click in the Operator field of the second condition and select same or less than from the list. The amount
automatically changes to 500.
9. Now add another condition to cover all of the other batches that don't have journals for the specified ledger.
Click the Add simple test icon. A third condition row is added after the two grouped conditions.
10. Since this new condition is mutually exclusive to the grouped conditions, click the connector to change it from
and to or.
11. Click the Left Value icon. The Condition Browser window opens.
12. Expand the Maximum Journal Amount folder and select Name.
13. Click OK. The Condition Browser window closes.
14. Click in the Operator field and select the operator named isn't.
15. In the Right Value field, enter the name of the ledger in quotation marks.
16. Now set up the automatic approval. The Supervisory list builder has two parameters that override the
supervisory approval and return a preconfigured approval action. In the THEN section, click in the Auto Action
Enabled field, and select True.
17. In the Auto Action field, enter "APPROVE". Include the quotation marks.
18. Collapse the rule.
You have now defined three rules that meet the business requirements and are collectively exhaustive. All
journal batches satisfy the conditions in at least one of the three rules and are routed for approval accordingly.
If a journal batch doesn't satisfy the conditions in at least one rule within a rule set, the rule evaluation process
would fail with errors.
19. Deploy the rules so that they can be used. On the Tasks to be configured toolbar, click the Commit Task icon.
The Enter Comments window opens.
20. Click OK. The Enter Comments window closes and a message appears stating that the data rule has been saved
and committed.
21. Click OK.
After journal approval is enabled, journal batches being posted are submitted for approval based on these rules.
Considerations for Defining Journal Approval Rules

Use approval management to define policies that apply to the journal approval workflow.
Rule Definition Consideration

One predefined approval rule exists for journal approval. If a journal's ledger and source are enabled for approval, then
that journal is sent for one level of approval to the supervisor of the person who submitted the journal for approval. You
59
can configure journal approval rules in the Business Process Management Worklist application. Open the application by
selecting the Notifications icon on the home page and clicking More Details or, by using the following in the Setup and
Maintenance work area:
• Functional Area: Application Extensions
• Task: Manage Task Configurations for Financials
For a simple approval scenario, start by defining one or all of the following journal approval rules based on:
• The highest journal line amount per ledger per batch.

• The highest journal amount per ledger per batch.
• Your stage in the period close process. For example, are you in the beginning, middle, or end of the month, or
in preclose, close, post close, or quarter close process?
The following table provides an example of rule conditions and approval actions that route a journal approval based on
maximum journal line amounts.
Condition Approval Action
Less than 50,000 USD No approval required
Between 50,000 and 100,000 USD One level of approval required
Greater than 100,000 USD Two levels of approval required
You can build your rules for combinations of ledger, entered amount, approval level, or other scenarios. In addition, you
can define rules based on attributes from different parts of your journal, including the ledger, batch, header, or line level.
For example, you can use category, source, account, or descriptive flexfield information as selection criteria for journal
approval.
Note: To prevent a submitter from approving their own journal batch, select the Skip creator for Approval List check
box on the Configuration page in the Worklist application. The approval task is then assigned to other approvers or
automatically routed to the manager of the submitter.
Approvals List Builder Considerations

List builders are the way approvals management builds the list of approvers required for a transaction based on the rule
condition. Each approval rule is associated with a list builder for generating the list of approvers.
The following table describes the list builders you can use to build a journal approval list.
List Builder Description
Supervisory Based on the employee supervisory hierarchy, which is defined in HCM. Employees must be set up
with appropriate jobs and supervisors. For example, a clerk reports to a manager, who reports to the
director.
60
List Builder Description
Job Level Based on the job level, which is defined in HCM. Employees must be set up with the appropriate job
levels and supervisors.
For example, a job level 1 employee, a clerk, reports to a job level 2 employee, a manager, who
reports to a job level 4 employee, a director. The approval list is generated based on the starting
position specified in the rule and continues until an approver with a sufficient job level is found. The
supervisory hierarchy must be defined along with the corresponding job levels.
Position Based on the position hierarchy, which is defined in HCM. The position hierarchy must be defined and
employees must be assigned the corresponding positions. Use this hierarchy if you need a hierarchy
that's different from the supervisory hierarchy, or multiple hierarchies selected based on different
attributes.
Approval Group Consists of a static predefined set of users configured to act on a task. For example, you can create
an approval group called Finance Group, consisting of users from the finance department who must
participate in the task approval.
Resource Builds the approvers list by using a specific user, enterprise group or application role.
Other Considerations
Other functionality to consider before defining approval rules.
• Both the ledger and journal source must be enabled for the approval process.
CAUTION: You should not enable journal approval for journals that come from subledgers (with subledger
journal sources). Otherwise, if a journal from a subledger isn't approved, the journal can get stuck in the
approval process. For any subledger journal sources, approvals for subledger transactions should be done in
the subledgers themselves.
• Approval is for the entire journal batch, regardless of the attributes used in the approval rules.
• If a journal requires approval, submitting a journal for posting automatically routes the journal for approval
before posting.
• A journal can be escalated to an approver by the administrator.
• The task initiator can select Withdraw Approval on the Journals page at any time in the approval process to
withdraw journals from the process. Clicking this button enables editing of the journal. After your changes
are made, submit the entry for approval again. When a journal is withdrawn, the completion status is set to
Incomplete.
• Approval notifications display a table of key journal attributes for each journal and a list of past, current, and
future approvers.
• The Journals work area displays journals requiring your approval and journals pending approval from others.
• If you're the current approver, the Journals page shows the journals to be approved or rejected.
• Allocation journals aren't routed through the approval process.
• You can review the details of the journals and journal lines included in a journal batch on the online and email
journal batch approval notifications.
61
Related Topics
• Overview of Workflow Tasks
• Overview of Managing Approvals and Notifications
AutoPost Criteria Sets

Create an AutoPost Criteria Set
In this example, you're creating an AutoPost criteria set to post the general ledger journal entries created by journal
import for your subledger transactions.
Here's the relevant setup for your Vision Corporation ledger.
• You implemented Oracle Fusion General Ledger and the subledgers Oracle Fusion Payables and Oracle Fusion
Receivables.
• You use a non-Oracle subledger called Fast Assets for fixed asset tracking and depreciation.
• You plan to automate posting of general ledger journal batches created by journal import. The automation
is to protect the subledger-sourced journal entries from edits or deletion that could cause an out-of-balance
situation between the subledgers and general ledger.
Consider these points when creating a criteria set:
• Use the All option for category and accounting period to reduce maintenance and ensure that all journal
imports are included in the posting process.
• Create a criteria set that includes all your subledger sources. Create multiple criteria sets by source only if you
must schedule different posting times to balance close activities or reduce processing time.
Create the Set

1. Go to the following:
◦ Task: Manage AutoPost Criteria Sets
2. Click Create.
3. Enter this name: All Journal Imported Entries.
4. Enter this description: Posting journals imported from the subledgers.
5. Select Enabled.
6. Select the Use Batch Creator as Approval Submitter check box if you require keeping the creator of the
journal batch as the user who submitted the batch for approval when the AutoPost Journals process runs. If
you don't select this check box, the user running the AutoPost journals process is the submitter for approval.
62
7. Enter these values and click Add Row to add each new line.
Priority Ledger or Ledger Source Category Accounting Period Balance Type

Set
1 Vision Corporation Payables All All All
2 Vision Corporation Receivables All All All
3 Vision Corporation Fast Assets All All All
8. Select Yes for the Process All Criteria check box, and enter 30 as the number of days before and after the
submission date. The process runs less often when you specify a wide range.
Tip: Schedule the process to run immediately after the Import Journals process to prevent changes to the
journals. Run the process during nonpeak times to save resources.
Related Topics
• How can I run the AutoPost process
• Examples of Manually Running the AutoPost Process
• Submit Scheduled Processes and Process Sets
Examples of Manually Running the AutoPost Process

Create an AutoPost criteria set and schedule the AutoPost Journals process to run on a regular basis following your
scheduled journal imports from your subledgers. When errors occur that prevent posting of the journal imports, you
must correct the errors and manually run the AutoPost process. The following scenarios illustrate the kinds of errors
that could occur and how you can resolve these errors.
Scenario
The following table lists the errors that prevented journal batches from posting when the scheduled AutoPost Journals
process ran.
Error Cause Solution
Unopened accounting period The journal import was imported into a future Open the period.
period. An error arises when the AutoPost
Journals process runs on a schedule because
journals can't be posted in a future period.
Invalid or no journals Journal import fails to import transactions from Correct the error that caused the journal import
the general ledger interface table. The AutoPost to fail.
Journals process runs on schedule but finds no
63
Error Cause Solution
batches to post. The posting process doesn't

run and the AutoPost Execution report shows
that no batches matched the criteria.
Invalid or no journals No journals were selected based on the posting Revise the criteria set.
criteria. Journal batches are available for
posting. The posting process doesn't run and
the AutoPost Execution report shows that no
batches matched the criteria.
After you correct the errors:
• Manually run the AutoPost Journals process by selecting the Run AutoPost option from the Tasks panel on the
journal pages.
• Click Generate on the AutoPost criteria set pages.
• Verify that the process ran successfully by reviewing the AutoPost Execution report.
Related Topics
• How can I run the AutoPost process
FAQs for Manage AutoPost Criteria Sets

How can I run the AutoPost process?
After you define an automatic posting criteria set, run the AutoPost process by clicking the Generate button on the
Manage AutoPost Criteria Sets page or the Launch AutoPost link from the Journals task pane. The AutoPost
process posts the journal batches that meet the criteria defined. Optionally, schedule the AutoPost process for specific
automatic posting criteria sets through the Schedule tab in the Schedule Process: Advanced region to run at specific
times and submission intervals.
How can I identify errors that occurred during the AutoPost

process?
Review the AutoPost process results on the AutoPost Execution report. This report is automatically created when the
process completes successfully. The report contains the batch name, accounting period, and balance type for each
posted journal batch, and lists error statuses for batches that fail to post. The unposted journals with their error status
are also displayed on the Requiring Attention tab of the Journals work area and the General Accounting Dashboard.
Note: The Requiring Attention tab also shows journals with rejected approvals.
64
Why didn't the AutoPost process post journal batches as

expected?
Verify that the posting criteria set specifies the precise criteria required to post the wanted journals. If the criteria is
correct, then verify the following:
• Journal imports completed successfully.
• Journal batches are error free and ready to post.
• Specified accounting period is open.
Journal Reversals
You can reverse journals manually by selecting a reversal action in the user interface, or you can reverse journals
automatically by running a process. Decide which approach is best for journals such as accruals, estimates, errors,
temporary adjustments, or reclassifications that require reversal. Reversing journals saves you time and helps prevent
data entry errors.
Here are the key areas to understand when reversing journals:

• Reversal Settings on Journals
• Manual Journal Reversal
• Journal Reversal Criteria Sets
• Automatic Journal Reversal
• Reversal Synchronization Between a Primary Ledger and Its Secondary Ledgers
Reversal Settings on Journals

You can enter and view a journal's reversal settings in the Reversal tab on the Create and Edit Journal pages:
• Reversal Period: Accounting period for the resulting reversal journal. Required for reversal.
• Reversal Date: Applicable only to average daily balance ledgers. Accounting date to be applied to the reversed
journal, since that's needed for calculating average balances. For ledgers that aren't average daily balance
ledgers, default logic is applied to determine the accounting date for the generated reversal.
• Reversal Method: Method for reversing amounts in the reversal journal. Select from Change Sign or Switch
Debit or Credit. The default setting is Switch Debit or Credit. The Change Sign setting means the reversal
puts the original journal amount in the same Debit or Credit column, but with the opposite (negative or
positive) sign. The Switch Debit or Credit setting means the amount is moved to the other column. Required
for reversal.
• Reversal Status: View-only state of the journal reversal. For example, Not reversed or Reversed.
You can enter a reversal period and method at any time, even after the journal is posted. If applicable, the following
values also display in the Reversal tab:
• Reversal Journal: If you're reviewing a journal that was reversed, this setting displays the name and link to the
reversal journal.
65
• Originating Journal: If you're reviewing a reversal journal, this setting displays the name and link for the journal
that was reversed.
Manual Journal Reversal

You can manually reverse posted journals that are eligible for reversal on both the Manage Journals and Edit Journal
pages. Both pages provide an action to reverse a journal and an action to reverse a batch.
On the Edit Journal page, you can select Reverse from the Batch Actions menu to reverse a journal batch, or you can
select Reverse from the Journal Actions menu to reverse a specific journal. On the Manage Journals page, you can
select rows in the Search Results section and then select the Reverse Batch or Reverse Journal buttons. To select
multiple rows at once, use the Shift or Control key. You can reverse multiple journals of the same batch, or of different
batches, or reverse entire journal batches that are eligible for reversal, based on the rows you selected.
Each reversal journal is created in its own reversal batch and the batch name starts with the word Reverses. When you
reverse a batch, a single reversal request is submitted. However, the reversal journal for each journal in the reversed
batch is still generated in its own journal batch. Reversal journals for journal-level reporting currencies are grouped into
the same reversal batch as the corresponding reversal journal of their associated primary or secondary ledger. Reversal
journals for subledger-level reporting currencies are grouped into the same reversal batch as their corresponding
primary ledger.
Here are some examples of when you might want to use batch reversal.
Scenario How It Works
You want to reverse all of the journals in When you select the reverse batch action, the Reverse Journal Batch window opens. You provide the
a batch that aren't yet reversed, using the reversal period, date, or method. The information you enter overrides any reversal settings at the
same reversal settings. For example, using journal level of journals that aren't yet reversed. All journals eligible for reversal are reversed according
the same reversal period for ledgers that to what you specified on the Reverse Journal Batch window.
aren't enabled for average balances, or the
same reversal period and date for ledgers
that are enabled for average balances. Or,
you want to use the same reversal method.
You specified reversal settings for every Leave the fields blank on the Reverse Journal Batch window. Each of these journals is reversed
journal that's not yet reversed in a batch, according to the journal's reversal settings.
and you want to process reversals more
efficiently using batch reversal.
You specified reversal settings for some, Use the Manage Journals page to reverse the batch. Leave the fields blank on the Reverse Journal
but not all, of the journals that aren't Batch window. Each of these journals is reversed according to the journal's reversal settings.
yet reversed in a batch, and you want to
process reversals more efficiently using
batch reversal.
You want to reverse multiple journals Use the Manage Journals page to select the rows for the batches and then select the reverse batch
from different batches using the reversal action. Each journal that's eligible for reversal in these batches is reversed according to the journal's
settings specified on each journal in these reversal settings.
batches.
66
Journal Reversal Criteria Sets

To provide default reversal settings to a newly-created journal based on the journal's category, or to also proceed with
automatically reversing a posted journal, create a journal reversal criteria set and assign it to a ledger. A journal reversal
criteria set contains all journal categories with their corresponding reversal settings and can be shared with any number
of ledgers.
Here's how to navigate to the journal reversal criteria set page from the Setup and Maintenance work area:
• Task: Manage Journal Reversal Criteria Sets
The Create Journal Reversal Criteria Set page lists all of the journal categories with default reversal settings. Find the
journal categories that you want to specify reversal criteria for and set the values accordingly. This table describes each
reversal setting.
Setting Values Description
Reversal Period No Default, Same Period, Next Period, Next Accounting period for the resulting reversal
Nonadjusting Period, Next Day, Same Day journal. The following values apply only to
average balance ledgers: Next Day, Same Day.
Selecting those values for a ledger that isn't an
average balance ledger is the same as selecting
the value No Default.
Reversal Date First Day, Next Day, Last Day Day of the accounting period when the journal
is to be reversed. A reversal date only applies
to average balance ledgers. You must specify a
reversal date if you select the following values
for the reversal period: Next Nonadjusting
Period, Next Period, Same Period.
Reversal Method Change Sign, Switch Debit or Credit Method for reversing amounts in the reversal
journal.
Automatic Reversal Option None, Reverse Automatically, Reverse and Post Setting that determines whether a journal is
Automatically selected for automatic reversal, and whether
the reversal journal is posted after it's reversed.
Unlike the previous settings in this table,
which are propagated directly as attributes in
the journal, this setting is used to determine
the reversal action that's applied when the
automatic reversal process is run.
After you create the journal reversal criteria set, assign it to one or more of your ledgers. Here's how to navigate to the
ledger page in the Setup and Maintenance work area where you can assign the journal reversal criteria set:
• Task: Specify Ledger Options, with the ledger scope set
67
When you create a journal for a ledger with an assigned criteria set, the journal's reversal period and method are
populated according to the criteria setting for that journal's category. This applies to journals entered through the user
interface and the Create Journal spreadsheet. You can accept the defaulted reversal values or change them at any time,
even after the journal is posted.
Automatic Journal Reversal

The automatic reversal process only selects reversible journals whose categories are enabled for automatic reversal in
the journal reversal criteria set that's assigned to the ledger. The automatic reversal option for those categories must be
set to either Reverse Automatically or Reverse and Post Automatically.
Here's how you can run the automatic reversal process:
• Select the Run AutoReverse task from the tasks pane in the Journals work area. The task opens the Scheduled
Process page for the AutoReverse Journals process. You might want to run automatic reversals this way for
one-time accruals entered in the current period, but tagged to reverse in a later period.
• Submit or schedule the AutoReverse Journals process on the Scheduled Processes page.
• Enable the ledger option Run AutoReverse After Open Period on the Specify Ledger Options page. When
enabled, the automatic reversal process is submitted with the reversal period choice of All.
Note: If you usually reverse journals on the last day of every month, don't enable this option. Instead,
schedule the automatic reversal process to run on the last day of the month. The accounting period
parameter automatically increments for each subsequent run.
The automatic journal reversal process creates one journal batch for each journal that's reversed. The names for
the reversal batch and reversal journal begin with the word Reverses. The process also produces the AutoReverse
Execution report, which prints the name of the journal batch that was submitted for reversal, along with the journal
batch accounting period. If the automatic reversal option is set to Reverse and Post Automatically, then the report also
provides information about the reversal batch.
Note: The AutoPost Journals process that's automatically submitted by the reversal process posts only the reversal
journals that it generated, not other journals that are pending posting.
If reversal synchronization is enabled (refer to the next section for details), the process generates a journal reversal
in the corresponding secondary ledger and the AutoReverse Execution report includes information about the journal
reversal batch that's generated in the secondary ledger.
After the process completes, you can review the reports for any problems and verify that all journals were processed
properly.
Here are some points to consider if you decide to run the automatic reversal process:
• If the automatic reversal option on the applicable journal reversal criteria set is set to:
◦ Reverse and Post Automatically and journal approval is enabled, journals posted by the process bypass
approval.
◦ Reverse Automatically, you must manually post the reversal journals.
• If you have an average balance ledger, the automatic reversal process doesn't check that the reversal date is
a valid business day. However, the journal validation in the journal pages and the import process perform this
check and, if necessary, roll the date to the next business day.
68
Reversal Synchronization Between a Primary Ledger and Its Secondary

Ledgers
If you have secondary ledgers, it's recommended that you enable the primary ledger option Synchronize Reversals
Between Primary and Secondary Ledgers. Reversal synchronization helps to ensure that the secondary ledger
remains as an accurate alternate representation of its corresponding primary ledger. If you enable this option, a journal
reversal (manual or automatic) in the primary ledger triggers the reversal of the corresponding journal in the associated
secondary ledger. If you didn't enable this option, you would have to actively manage the reversal of journals in the
secondary ledger, whether they were replicated from its primary ledger or created directly in the secondary ledger. To
set this option for a primary ledger, use the same navigation as you did for assigning the journal reversal criteria set to
the ledger.
Note: Reversal synchronization is relevant only for secondary ledgers with a data conversion level of Journal or
Subledger because primary ledger journal replication is applicable only to secondary ledgers at those conversion
levels. Reversals for reporting currencies at a Journal level of conversion for a primary or secondary ledger, and also
at a Subledger level for a primary ledger, are automatically synchronized with their source ledger, regardless of the
synchronization option setting.
Here's how reversal synchronization works with journal approval when you have this setup:
• You enabled journal approval in both the primary and secondary ledger.
• You enabled reversal synchronization between the two ledgers.
The reversal journal generated in the secondary ledger (for the primary ledger reversal) won't require a separate
approval.
This table shows how journals are reversed in a secondary ledger when synchronization is enabled. Journal reversal
depends on how the journals were created in the secondary ledger and on whether a reversal criteria set is assigned to
the secondary ledger.
How was the journal that's going to be Did you assign a journal reversal criteria set How is the journal reversed in the secondary
reversed created in the secondary ledger? to the secondary ledger? ledger?
The journal was replicated from the primary Yes The journal is reversed automatically when the
ledger. journal in the primary ledger is reversed. The
reversal settings in the primary ledger source
journal override any reversal settings on the
journal in the secondary ledger that's being
reversed.
Note:
Because the journal was replicated from the
primary ledger, the journal reversal criteria
set has no impact on the reversal.
The journal was created directly in the Yes If the journal category is set for automatic
secondary ledger. reversal in the secondary ledger's assigned
criteria set, you can run the automatic reversal
process in the secondary ledger. Otherwise, you
must reverse the journal manually.
69
How was the journal that's going to be Did you assign a journal reversal criteria set How is the journal reversed in the secondary
reversed created in the secondary ledger? to the secondary ledger? ledger?
The journal was replicated from the primary No The journal is reversed automatically when the
ledger. journal in the primary ledger is reversed.
The journal was created directly in the No You must specify reversal information in the
secondary ledger. journal and manually reverse the journal in the
secondary ledger.
Once set, the primary ledger option Synchronize Reversals Between Primary and Secondary Ledgers applies
to any secondary ledger of the primary ledger. The option Post Journals Automatically from Source Ledger is
set by the individual secondary ledgers of the primary ledger and controls automatic posting of secondary ledger
journals (reversals and otherwise), when the corresponding primary ledger journal is posted. To set this option, use this
navigation in the Setup and Maintenance work area:
• Task: Complete Primary to Secondary Ledger Mapping, with the primary ledger and secondary ledger scope set
Related Topics
• When does a journal become reversible
Overview of Clearing Accounts Reconciliation

Clearing accounts reconciliation offers automatic and manual methods to group, match, and reconcile related in and out
journal lines that no longer contribute to an account's ending balance. You can analyze those unreconciled journal lines
that are both relevant and responsible for the buildup of the ending balance in a clearing account.
The recommended approach for reconciling clearing accounts is to run automatic reconciliation to process the majority
of the journal lines, based on your setup. Then use manual reconciliation to resolve the journal lines that weren't
reconciled automatically. You can also reverse incorrect reconciliations. Reports are available to help with this process.
Related Topics
• Overview of Clearing Accounts Reconciliation
• Set Up Clearing Accounts Reconciliation
• Reconciliation Types
• How Tolerances Work with Manual Clearing Accounts Reconciliation
• Reconcile Clearing Accounts
70
Implementing Accounting Hub Period Close Components
5 Period Close Components
Overview of Period Close

While implementing your accounting configuration, optionally define and maintain period close components, including
allocations and periodic entries, revaluations, and historical rates.
If you use allocations, revaluation, or translation, configure the following tasks in the Define Period Close Components
task list in your implementation project:
• Manage Allocations and Periodic Entries
• Manage Revaluations
• Manage Historical Rates
Related Topics
• Overview of Opening First Period
• Overview of Close Monitor
• How You Configure Social Objects
• Period Close Components
FAQs for Period Close

How can I use social networking to effectively close the period?
Use the Social link on the Period Close work area to collaborate with members of your team or others within your
company to effectively close the period.
For example, as a controller, you keep Oracle Social Network open from the Period Close Overview page during the
period close so you can be aware of any transactions that must be posted for the period.
On the All tab:

• You see a conversation that needs your attention.
• Your boss, the chief financial officer, started a private conversation with you to announce the close of a deal
worth 15,000,000 USD and wants it booked for this period.
• You download and listen to a voice message file that the chief financial officer posted sharing details about the
delivery of the goods to help you confirm that the revenue can be posted to this period.
• You create a new conversation and invite your accounting manager to join, marking it so she knows to reply
quickly.
• Your accounting manager added you to a conversation for the revenue adjustment journal.
• Your accounting manager adds a post to the conversation confirming that the revenue is posted.
71
You navigate to the Close Monitor page to view the latest financial balances and confirm that the revenue is posted.
Depending on your job role and permissions, you can access social networking features for the following Oracle Fusion
General Ledger business activities:
• Period status
• Journal
Related Topics
• What does social networking have to do with my job
Allocations and Periodic Entries

Example of Creating an Allocation Rule and Generating Allocations
This example distributes a cost that's recorded in one account to different cost centers, based on the headcount in each
cost center. The headcount is recorded using the statistical currency, and the cost centers receiving the cost are in a
parent cost center. The chart of account consists of the following segments:
• Company
• Line of Business
• Account
• Cost Center
• Product
• Intercompany
Create the Rule

Navigate to the Calculation Manager, which is the tool for managing allocations.
1. Navigate to the Journals work area.

2. Click the Tasks icon and select the Create Allocation Rules task. The task opens the Enterprise Performance
Management workspace.
3. From the Navigate menu, select Administer, Calculation Manager.
4. Expand the Essbase application.
5. Find the balances cube for the chart of accounts that's associated with the relevant ledger and expand it.
6. Right-click the Rules node and select New from the menu. The New Rule window opens.
Tip: Since the rule is going to allocate cost based on headcount, consider including headcount in the rule
name.
7. Accept the default values for the rest of the fields and click OK. The New Rule window closes and the Rule
Designer opens in a new tab with the name of the rule you just entered.
72
Define the Point of View

Set the Point of View to default values that are fixed throughout the allocation rule. For example, if a chart of accounts
has a future-use segment that's currently not used, you can use the Point of View to set a default value such as 000.
Then you don't have to select a value for this segment when defining the rule.
1. In the Rule Palette, select the Point of View object and place it between the beginning and ending components
in the flow chart on the Designer area.
2. To have users supply the accounting period when the allocation is run, use a variable. Runtime prompt variables
make rules dynamic and reusable. Click in the Value field for the Accounting Period row.
3. Click the Actions icon and select Variable. The Select Variable window opens.
4. Select the Database category, which is the category for the specific cube. The Application category applies to
all cubes.
5. In this example, the accounting period is already defined as a variable, so select it and click OK.
6. Click the Member Selector button. The Member Selector window opens. You can set the fixed dimensions
namely, Ledger, Company, Line of Business, Product, and Intercompany segments from the Member Selector.
You can also set the Currency and Currency type. You can expand the dimensions to find the values or you can
search for them. Alternatively, instead of using the Member Selector, you can enter the values manually.
7. Select Ledger from the Dimensions drop down value.
8. Expand All Ledgers.
9. Select the appropriate ledger.
10. Click the Select icon to move the ledger to the Selections panel.
11. From the Dimensions list, select the Company, the Line of Business, the Product, the Intercompany, and the
Currency dimensions, and set them.
12. Select Currency Type from the Dimensions list.
13. Expand the Currency Type node and select Total. This selection indicates that the allocation is going to use
balances in the ledger currency, including the equivalent ledger currency balances of foreign currency journals.
Note: If you select Entered, the allocation would only use amounts where the entered currency is the
currency that was selected for the Currency dimension.
14. Click OK. The Member Selector window closes.

Fixed values have now been set for all of the segments, except the Account and Cost Center segments.
Define the Allocation Component

1. From the Rule Palette, select the Allocation object and place it between the point of view member components
in the flow chart on the Designer Area. The Allocate Wizard window opens and the Point of View tab opens.
This Point of View is specific to the Allocation component, so if you have a rule with multiple Allocation
components, you can specify a Point of View for each of them. Since this rule has only one Allocation
component, and you have already defined a Point of View, skip this step.
2. Click Next. The Source tab opens.
The source is the revenue pool to be distributed or allocated. A source can be a referenced account balance
or a user-defined amount. For this rule, the source is the communication cost. To retrieve the cost, you must
provide the account combination. You already specified values for the Company, Line of Business, Product, and
Intercompany segments in the Point of View, so the only source segments to specify here are Account and Cost
Center.
3. Click the Member Selector button. The Member Selector window opens.
a. On the Dimensions list, select Account.
73
b. Click the Search tab and search for the communications cost account.
c. Select the account and click the Select icon to move the account to the Selections section.
d. On the Dimensions list, select Cost Center.
e. Click the Search tab and search for the cost center.
f. Select the cost center and click the Select icon to move the cost center to the Selections section.
g. Click OK. The Member Selector window closes.
4. The remaining dimensions, Scenario, Balance Amount, and Amount Type, specify what balance to retrieve from
the source account. On the Allocate Wizard window, the default value for the Scenario dimension is Total for
Allocations, which is the sum of the actual and allocated amounts. Since the source for this rule only involves
actual balances, you must change the value. Click the Member Selector button. The Member Selector window
opens.
a. On the Dimensions list, select Scenario.

b. Expand Scenario in the Members tab.
c. Select Actual and click the Select button to move it to the Selections section.
Note: If you have two rules with the second rule using the allocations resulting from the first rule, use
the Allocated scenario for the second rule.
d. On the Dimensions list, select Balance Amount.

e. Expand Balance Amount in the Members tab.
f. Since the rule is going to allocate communications cost for the period, select Period Activity. Click the
Select icon to move it to the Selections section.
g. Click OK. The Member Selector window closes.
5. Accept the default value for the Amount Type dimension as Period to Date.
6. Click Next. The Allocation Range tab opens. The range is the spread of values that the source is distributed
against. In this rule, the cost is allocated across cost centers.
7. Click in the Select Value field in the Cost Center row.
8. Click the Actions icon and select Member. The Select Member window opens.
a. Select the appropriate parent value and click the Select icon to move it to the Selections section.
Note: Always select a parent value because you have to allocate across a range of values.
b. Click OK. The Member Selector window closes.

9. Click Next. The Target tab opens.
10. The target receives the allocated amount. Enter the account number within quotation marks in the Account
row.
11. Click Next. The Offset tab opens.
The offset receives the offsetting debit or credit to balance the allocation that was generated. On the Offset
tab, enter the account number in the Account row and the cost center in the Cost Center row, within quotation
marks.
CAUTION: The offset must be a child value. If you select a parent value, the allocation rule fails validation.
74
12. Click Next. The Exclude tab opens.

Note: Use the Exclude tab for partial allocations. Specifically where you want to allocate a percentage of the
total source and the percentage itself can't be entered. Instead, the percentage has to be calculated based on
all the members in the basis and then some members have to be excluded from the allocation target range.
For example, a basis contains cost centers 100, 200, 300, and 400. You want to distribute the source evenly
across each cost center, so each cost center should be allocated 25% of the source. But you have to exclude
cost center 300 from the allocation range. In this example, you would specify cost center 300 in the Exclude
tab. When the allocations are generated, 75% of the source is allocated, 25% each to cost centers 100, 200,
and 400. The 25% for cost center 300 remains unallocated because cost center 300 is excluded.
13. This particular allocation isn't excluding any values, so click Next. The Basis tab opens.
14. On the Basis tab, for the Account dimension, enter the account number that has the headcount values.
Note: The basis determines the ratio in which the source must be allocated to each member of the allocation
range. The basis could be distributing the source evenly. Or you can select specific statistical or account
balances for a particular period as the basis.
For this allocation, the ratio is going to be calculated by dividing a cost center's headcount by the total
headcount.
15. Enter Period Activity in quotation marks for the Balance Account dimension because the total headcount for
each cost center is included in one journal recorded in one period.
16. Enter STAT in quotation marks in the Currency dimension. The values for the other dimensions are derived
automatically based on the Point of View and range specified previously.
17. Click Next. The Basis-Options tab opens.
18. Accept the default settings and click Next. The Rounding tab opens.
19. Specify the rounding options in case of rounding differences when the allocation is generated. Since the
allocation is in US dollars, on the Rounding tab, enter 2 as the number of decimal places to use. Click Finish.
The Allocate Wizard window closes.
Validate the Rule

Validation is an important and required step. Validation checks for consistency against the outline of the balances cube
that it references. For example, validation checks that the offset is a child, not a parent value, and checks that entered
values exist.
1. Click the Validate icon on the toolbar. After the validation is completed, a message appears stating whether the
validation was successful.
2. Click OK.
3. Click the Validate and Deploy icon to deploy the rule and make it available for generation in the general ledger.
4. Click Yes to first save the rule.
5. After the deployment is completed, a message appears stating whether the deployment was successful.
6. Click OK.
Generate the Allocation Journal

Generate the allocation journal using the following steps:
1. Navigate to the Journals work area.

2. Click the Tasks icon.
3. Select the Generate General Ledger Allocations task.
4. In the Rule or Rule Set field, enter the name of the allocation rule. The Accounting Period prompt should
appear.
75
5. Select the accounting period.

6. The Post Allocations option is selected by default.
7. Click Submit. A confirmation message appears stating that the process was submitted.
8. Click OK.
Review the Journal
1. Navigate to the Journals work area

2. Click the Tasks icon.
3. Select the Manage Journals task.
4. Enter the first part of the allocation rule name in the Journal field.
5. Enter a value in the Accounting Period field.
6. Select Allocations in the Source field.
7. Click Search.
8. Click the Journal link to open the journal. The cost that was allocated has a credit and the debits to the different
cost centers are based on their headcount.
Now that the rule is defined, all that's needed for future accounting periods is to generate the journals.
Overview of Allocation and Periodic Entries

In Oracle Fusion General Ledger, use the Calculation Manager to create allocations and other formula journal templates
for generating periodic journal entries automatically. Allocations are defined and generated from preaggregated
balances in the GL Balances cubes, which provide the following benefits:
• Immediate real-time access to financial balances for allocations and periodic entries.
• Accelerated performance for complex allocations.
You can base formulas on multiple criteria. For example:
• Use account balances or statistical amounts to allocate shared revenue or costs across multiple organizational
units and ledgers.
• Define complex computations based on variables from different charts of accounts.
• Group journal formulas together and execute sequentially to update account balances in a step-by-step
process.
Related Topics
• Overview of Oracle Essbase Balances Cubes
• Create Recurring Journals
• Overview of Allocations and Periodic Entries
• Overview of Calculation Manager
• Allocation Security
76
Overview of Recurring Entries

Define recurring journal formulas for transactions that you repeat every accounting period, such as accruals,
depreciation charges, and allocations. Your formulas can be simple or complex. Each formula can use:
• Fixed amounts and account balances, including standard, actual amounts, statistics, and period-to-date or
year-to-date balances.
• Amounts from the current period, prior period, or same period last year.
• Amounts in your formulas, including total balances, entered currency balances, or statistical balances.
You can quickly create recurring formulas by copying and modifying existing formulas. You can:
• Define single ledger or multiple ledger recurring journal formula batches.

• Create a recurring journal formula batch that contains recurring journal entries for different ledgers.
• Define recurring journal formulas for your ledger currencies, entered currencies, and statistical currency.
Related Topics
• Types of Recurring Journals
• Create Recurring Journals
• Schedule Recurring Journals
Overview of Using Calculation Manger

In addition to the Enterprise Performance Management Workspace buttons, the Calculation Manager toolbar displays
buttons that are specific to the Calculation Manager. Not all buttons display in all the views and designers within the
Calculation Manager.
The Calculation Manager toolbar consists of the following buttons:
• Home: Displays the default start-up option for the content area.
• System View: Displays the main view within the Calculation Manager. (This is the default view).
• List View: Displays a list of objects that you can filter by application type, application, object or database type,
deployment status, and validation status.
• Custom View: Displays a view you can change with folders that you create.
• Filter Options: Opens the Filter dialog that you can use to filter objects in the List View.
• Refresh: Refreshes the view with your latest changes.
The Calculation Manager toolbar adds the following buttons when you open a rule:
• Save: Saves the object with which you are working.

• Validate: Validates the object with which you are working.
• Validate and Deploy: Validates and deploys the object with which you are working.
77
Related Topics
• Calculation Manager Menus
• How You Use Flow Charts in Rule Designer
• Calculation Manager Views
• Filter Objects in the List View
FAQs for Manage Allocations and Periodic Entries

How can I access the Calculation Manager?
Login into the Oracle Fusion General Ledger application and navigate to the Journals work area. From the Journals
work area select the Create Allocation Rules link and automatically log into the Calculation Manager in Workspace to
create new allocation rules or rule sets.
Note: The application or the balances cube that is currently selected in the General Ledger Data Access Set is
automatically selected in the Calculation Manager.
How can I create a folder in the Custom View?

In the Custom View, create folders that contain only the allocation rules, allocation rule sets, and formulas you want to
view and work with.
To create a folder in the Custom View:

1. In the System View, select View, Custom View.
2. In the Custom View, right-click the Essbase application type, and select New Folder.
3. In New Folder, enter a name for the folder.
4. Click OK.
Tip: You can create nested folders by right-clicking the folder you want to create a folder in and selecting New Folder.
How can I rename a folder in the Custom View?

Rename the folders you create in the Custom View.
To rename a folder in the Custom View:

1. In the System View, select View, Custom View.
2. In the Custom View, expand the Essbase application type.
3. Right-click the folder you want to rename, and select Rename.
4. In the Rename Folder, enter a new name for the folder.
5. Click OK.
78
How can I migrate allocation rules from one environment to

another?
You can export your allocation rules from a source environment and import them to a target environment using a
implementation projects. In the Setup and Maintenance work area, create an implementation project that includes only
the Manage Allocations and Periodic Entries task. Then use the Manage Configuration Packages task to export and
import the allocation rules.
Related Topics
• How You Use Implementation Projects to Manage Setup
• Setup Data Export and Import Using Implementation Project
• Export Setup Data Using Implementation Project
• Import Setup Data Using Implementation Project
Allocation Rules
Overview of Allocation Rules
The Calculation Manager enables you to create, validate, deploy, and administer sophisticated multidimensional
allocation rules. An allocation rule is logical expressions or formulas that are created within an application to produce a
set of resulting values. Create an allocation rule set of two or more related rules to launch the rules sequentially.
Before you create a rule or rule set, you must understand the database outline and the application with which you are
working. This information helps you create your allocation rules more efficiently. Learn the following about your data:
• How the data is stored and aggregated.

• What level the data gets loaded into the database.
• What order the calculations are performed.
• What key assumptions drive the calculations.
Create allocation rules using components like formulas, member ranges, and variables, including run time prompt
variables.
Related Topics
• Create an Allocation Rule
• Start Calculation Manager
• Create an Allocation Rule with a Formula Component
• Create an Allocation Rule with an Allocation Component
• Design an Allocation Rule
79
Edit an Allocation Rule

You can edit the structure of an allocation rule by adding to, removing, or changing its components. You can also edit
the properties of the allocation rule's components and the properties of the allocation rule itself. You can edit these
properties of an allocation rule:
• Name and caption
• Description and comments
• Range of dimensions and members
• Variables, you include in the allocation rule
Scenario
To edit an allocation rule:
1. Navigator > General Accounting: Journals > Create Allocation Rules link.
2. Navigate menu > Administration > Calculation Manager.
3. In the System View, expand the Essbase Application Type, the Application, or Database, and Rules. Do one
of these tasks:
a. Right-click the rule you want to edit, and select Open.
b. Select the rule you want to edit, and select File, Open.
4. To edit the rule, in the Rule Designer, add new components, and copy and delete existing components, from
the rule's flow chart.
Note: As you edit components in an allocation rule, you can increase or decrease the size of the component
icons and the amount of detail that is displayed in the flow chart. To edit, you use the zoom bar to zoom in
and out within the flow chart. When the flow chart is displayed in small or very small sizes, the component
captions do not display, but you can place your mouse pointer over any icon to read its caption. Regardless
of the size of the components in the flow chart, you can select a component to view its properties on the
Properties tab.
5. To delete a component from the flow chart, select the component, right-click it, and select Remove.
6. To copy and paste a component, select the component, right-click it, and select Copy. Then paste it into the
flow chart.
7. To add a new component:
8. From New Objects, drag and drop components to insert a new component into the rule's flow chart:
◦ Point of Views
◦ Allocations
◦ Formulas
9. From Existing Objects, drag existing objects from Essbase applications and drop them into the rule's flow
chart.
10. For Essbase: On Global Range, you can edit the values that is, members, variables, and functions that define
the range of values to be calculated when the rule is launched.
11. Select values for a dimension by clicking its row in the Select Value column.
12. When the Actions icon is displayed, click it, and select one of these:
◦ Variable
80
◦ Member
◦ Member
13. For Essbase: On Variables, you can create variables for the rule.
14. On Usages tab, you can view which rules and rule sets use the rule, if any. This is the information you can view
about the rules and rule sets that use the rule:
Note: On the Usages tab, you view which allocation rules and rule sets use the rule, if any. You cannot edit
any of the information on this tab. The following information is displayed for the allocation rules and rule sets
using the allocation rule:
◦ Names
◦ Database
◦ Application Name
◦ Deployment Status
◦ Validation Status
◦ Description
15. Select File, Save.
Print an Allocation Rule

You can print an allocation rule's properties, its flow chart, and the details of its components. For example, if you print
an allocation rule that contains a formula component for allocation expenses and shows:
• The formula syntax.
• The functions and variables that comprise the formula.
• A summary of the steps in the rule's flow chart but not in graphical form.
• The rule's properties.
Note: You cannot print allocation rule sets.
Scenario
To print an allocation rule:
1. Navigator > General Accounting > Journals >Create Allocation Rules link.
3. In the System View, expand the Essbase Application Type, the Application, or Database, and Rules. Select
the rule you want to print.
4. Select File, Print.
Note: You can also select File, Print from within the Rule Designer to print a rule.
5. In Print Preview, do these tasks:

6. Select the Print options:
◦ Paper size
81
◦ Print orientation: portrait or landscape.

7. Select General Rule Information to print the rule's description and other details from the Properties tab. The
details include the rule's name, the application, its owner, the date the rule was created, and the date the rule
was last modified.
8. Select Flow Chart and Expanded or Collapsed, to print the flow chart, and you want to print it with the
component details expanded or collapse.
9. Select the number of pages you want to print the components across (horizontally). Select the number of pages
to print the components down (vertically).
10. Select the Page Order options:
◦Down, then across: The components in the flow chart print down (vertically, as rows do) on the number
of pages you specified in the previous step. Then the components print across (horizontally, as columns
do) on the number of pages you specified in the previous step.
◦ Across, then down: The components in the flow chart print across (horizontally, as columns do) on the
number of pages you specified in the previous step. Then the components print down (vertically, as rows
do) on the number of pages you specified in the previous step.
11. Select the remaining Rule Information options:
◦ Select Summary, to print a summary of the components in the flow chart.

◦ Select Variable Section to print information about any variables used in the rule.
◦ Select Detail Section to print detailed information about the components in the rule.
◦ Select Page break before sections to create a page break between summary, variable, and detail
sections. This option is selected by default.
◦ Select Nested Rules to print rules contained in other rules.
12. Select Generate PDF.
13. A PDF file of the rule is opened in Adobe Acrobat.
14. Click the Print icon in Adobe Acrobat.
15. In the Print dialog, select the print options specific to the printer you are using, and click Print.
FAQs for Allocation Rules

How can I open an allocation rule?
You open an allocation rule from the System View that is displayed by default when you open Calculation Manager. You
can also open a rule using File, Open from within the tab of another rule, rule set, component, or template.
To open an allocation rule:
1. Navigator > General Accounting: Journals > Create Allocation Rules link.
3. In the System View, expand the Essbase Application Type, the Application, or Database, and Rules.
4. Do one of these tasks:
◦ Right-click the rule you want to open, and select Open.

◦ Select the rule you want to open, and select File, Open.
82
How can I save an allocation rule?

You must save an allocation rule after you create or edit it. When you save the allocation rule, it is saved to the
application and application type for which you created it. After you save it, you can validate and deploy it in Calculation
Manager. You can generate it in Oracle Fusion General Ledger.
To save an allocation rule after you create or edit it, select File, Save.
Note: To see the allocation rule in the System View after you save it, you may refresh the application list. To do this,
right-click the application type, the application, or the database (for Essbase), and select Refresh.
How can I save an allocation rule with a different name?

You can save an allocation rule with a different name using Save As. You can also copy a rule from one rule set to
another within the same rule set type using Save As. Save As creates a copy of the original rule with a different name to
distinguish it from the original.
To save an allocation rule with a different name:
2. Right-click the rule you want to save with a different name, and select Open.
3. In the Rule Designer, select File, Save As.
4. In Save As, enter the rule's new name, and select the Application Name.
5. Select the Database.
Note: You cannot change the database of a rule you save with a different name.
6. Click OK. The new rule is added to the application list in the System View.
How can I delete an allocation rule?

You delete an allocation rule from the System View. You can delete an allocation rule only if it is not used by other rules
or rule sets. If the rule is being used, you must remove the allocation rule from the rules and rule sets using it, or make
copies of it for the rules and rule sets using it, before you delete it. To see if a rule is used by other rules and rule sets,
you can show the usages of the rule.
To delete an allocation rule:
2. Make sure the rule you want to delete is not being used by another rule set or rule.
3. Right-click the rule you want to delete, and select Delete.
4. Click OK to confirm deletion of the rule.
83
Allocation Rule Sets

Overview of Allocation Rule Sets
You create an allocation rule set by combining allocation rules or allocation rule sets that can be generated sequentially.
You add rules and rule sets to a rule set by dragging and dropping them into it.
After you create and save the rule set, you can validate and deploy it. Then you can generate it in Oracle General Ledger.
Note: Rule sets are supported in Essbase aggregate storage applications used in Oracle General Ledger in sequential
mode only.
Related Topics
• Create an Allocation Rule Set
• Design an Allocation Rule Set
• Add an Allocation Rule to an Allocation Rule Set
• Edit an Allocation Rule Set
• Create and Deploy an Allocation Rule Set
Copy an Allocation Rule Set to Another Application

From the System View, you can copy an allocation rule set to another application of the same application type
(Essbase) or database.
Note: Allocation rule sets are not supported in Essbase Aggregate Storage or Block Storage applications, other than
Aggregate Storage applications used in Oracle General Ledger.
Scenario
Use the following steps to copy a rule set to another application:
1. In the System View, expand the Essbase Application Type and the Application.
2. Expand RuleSets.
Note: Only one rule set node exists for each application at the same level as the plan types and databases.
3. Right-click the allocation rule set you want to copy, and select Copy To.
Note: You can also copy an allocation rule set when you are working with it in the Ruleset Designer, and
paste it into another allocation rule set or allocation rule.
4. Select the rule set name, select Edit, Copy, open the rule or rule set into which you want to copy it, and select
Edit, Paste.
84
5. In Save As, enter a new name for the allocation rule set, or accept the default name, and select an application
and calculation or plan type. Click OK.
Note: You cannot copy the allocation rule set to more than one application and calculation or plan type.
The new allocation rule set is added to the application and calculation or plan type you selected. To see it in the System
View, you must refresh the application list. To refresh the application list, click the Refresh icon on the toolbar.
Save an Allocation Rule Set

You must save an allocation rule set after you create or edit it. When you save the allocation rule set, it is saved to the
application and application type for which you created it. After you save it, you can deploy, validate, and generate it. You
can deploy and validate it in Calculation Manager; you can generate it from Oracle General Ledger.
Scenario
To save an allocation rule set after you create or edit it, select File, Save, or click the Save icon.
Note: To see the allocation rule set within the System View after you save it, you must refresh the application list. To
do this, right-click the application type, the application, the database (Essbase), and select Refresh. You can also click
the Refresh icon on the toolbar to refresh the application list in the System View.
Save an Allocation Rule Set with a Different Name

You can save an allocation rule set with a different name using Save As. Saving it with a different name creates a copy of
the rule set.
Scenario
2. Expand RuleSets.
Note: For Essbase applications, only one rule set node exists for each application at the same level as the
plan types and databases.
3. Right-click the rule set you want to save with a different name, and select Open.
4. In the Ruleset Designer, select File, Save As.
5. In Save As, enter the rule set's new name, and select an application. Click OK.
Note: You cannot change the application type of a rule set you save with a different name. The new rule set
must have the same application type as the rule set from which the rule set is created.
The new rule set is added to the application list in the System View.
85
Delete an Allocation Rule Set

You delete an allocation rule set from the System View. You can delete an allocation rule set only if it is not being used
by other allocation rule sets. To see if it is being used by other rule sets, you can show its usages. If it is being used, you
must remove it from the allocation rule sets that are using it, or make copies of it for the allocation rule sets that are
using it, before you delete it.
Scenario
2. Expand RuleSets.
3. To make sure the rule set is not being used by another rule set, right-click it, and select Show Usages.
4. Right-click the rule set you want to delete, and select Delete.
5. Click OK to confirm deletion of the rule set.
Refresh Allocation Rules or Rule Sets

In the System View, you can refresh any level of the application list. You can refresh:
• Application Type
• Application
• Database
• One or Multiple Rule Sets or Rules
By default, when you refresh an application, application type, or database, all of the rules, rule sets, components, and
templates belonging to it are refreshed.
However, refreshing the rule sets or rules within an application does not refresh higher levels in the application list or
rule sets or rules that belong to other applications.
Note: You can also click the Refresh icon on the toolbar to refresh the entire application list in the System View.
Scenario
2. To refresh rule sets, right-click RuleSets, and select Refresh or to refresh rules, expand the database, right-click
Rules, and select Refresh.
Note: You can also right-click the application type, the application, or database that contains the allocation
rules you want to refresh, and select Refresh.
86
Show Usage of an Allocation Rule or Rule Set

You can display the allocation rules and rule sets that are using a rule or allocation rule set. Viewing the usages of rules
or rule sets is useful when deleting rules or rule sets and you must know what objects are using it.
Scenario
2. To show the usages of a rule set, expand RuleSets.
3. Right-click the rule set whose usages you want to see.
4. Select Show Usages or to show the usages of a rule, expand the database, and Rules.
5. Right-click the rule whose usages you want to see, and select Show Usages.
6. You can view this information about the rule or allocation rule set:
a. Names
b. Database
c. Application Name
d. Deployment Status
e. Validation Status
f. Description
Note: You can also view a rule or rule set's usages from within the Rule or Ruleset Designer on the
Usages tab.
7. After you review the information, click OK.
Change Owner of an Allocation Rule or Rule Set

You can change the owner of an object such as a rule, rule set, or formula in the System View. The application to
which it belongs must be deployed. By default, an object's owner is the user that creates it, unless the user changes the
ownership. Users can edit only objects they own, with the exception of administrators who can edit any objects.
Scenario
2. To change the ownership of a rule set, expand RuleSets or to change the ownership of a rule, expand the
database, and then expand Rules.
3. Right-click the object, and select Change Ownership.
4. In Change Owner, select the owner to whom you want to transfer ownership of the object.
5. Click OK.
Note: The user you assigned ownership to can edit the object.
87
FAQs for Allocation Rule Sets

How can I open an allocation rule set?
You open an allocation rule set from within the System View. You can also open a rule set from within the Ruleset
Designer, by selecting File, then Open.
To open an allocation rule set:

1. In the System View, expand the Essbase application type and the application.
2. For Essbase: Expand RuleSets, right-click the rule set you want to open, and select Open.
Note: For Essbase applications, there is only one rule set node for each application at the same level as the
databases.
How can I open an allocation rule within an allocation rule set?

You can open an allocation rule from within an allocation rule set from the System View or from the Ruleset Designer.
To open an allocation rule within an allocation rule set:

2. Expand your rule set that contains the rule you want to open.
Note: For Essbase applications, only one rule set node exists for each application at the same level as the
databases.
3. Right-click the rule you want to open, and select Open.

Note: You can also open a rule that belongs to an allocation rule set from within the Ruleset Designer. To do
this, in the Ruleset Designer, right-click the rule, and select Open.
How can I remove an allocation rule from an allocation rule set?

When you remove a rule from an allocation rule set, the rule is not deleted. The rule exists independently of the rule set
in the database.
To remove an allocation rule from an allocation rule set:

2. Expand RuleSets, right-click the rule set you want to open, and select Open.
Note: Only one rule sets node exists for each application at the same level as the plan types and databases.
3. In Ruleset Designer, right-click the rule you want to remove, and select Remove.
Select File, Save.
88
Overview of Point of View and Allocation Components

Every data value in a report is derived from the intersection of a member from each dimension in the Essbase database
connection. Financial Reporting enables a designer to place these dimensions on the report grid or user point of view.
Report viewers can change the member selected for dimensions on the user point of view. This enables report viewers
to configure the reports to fit their needs. The user point of view can also be used in books.
You create and edit point of view components from within a rule to set members, variables, and functions that contain
the global range of the point of view component. You can nest a point of view component within another point of view
component.
Allocation components contain calculations for distributing data from members at one level in the database outline to
other members in the outline. Formula components contain calculation statements that you design using members,
functions, and variables.
Related Topics
• Create a Point of View Component
• Edit a Point of View Component
• Work with Allocation Formula Components
• Create an Allocation Component
• Edit an Allocation Component
FAQs for Point of View and Allocations Components

How can I open a point of view or allocation component?
You open a point of view or allocation component from within the flow chart of the rule to which it belongs.
Note: You cannot open the allocation component from the System View.
To open a point of view or an allocation component:
1. In the System View, expand the Essbase Application Type, the Application, Database, and Rules.
2. Right-click the rule that contains the component you want to open, and select Open. The rule is displayed in
the Rule Designer.
3. When the rule opens, click the point of view component or double-click the allocation component in the rules
flow chart to open the component.
89
How can I save a point of view or allocation component ?

You save a point of view or an allocation component when you save the rule to which it belongs in the Rule Designer.
Unlike the formula components, point of view and allocation components cannot exist independently for the rule to
which they belong.
To save a point of view or allocation component:

• Select File and Save, or click the Save icon, once you finish designing a point of view or an allocation
component.
How can I copy and paste a point of view or allocation

component?
You can copy a point of view or allocation component from within the rule in which it is used, and you can paste the
component into the same or a different rule.
To copy and paste a point of view or allocation component in a rule flow chart:
1. In the System View, expand the Essbase Application Type, the Application, Database, and Rules.
2. Right-click the rule that contains the point of view or allocation component you want to copy and paste, and
select Open. The rule is displayed in the Rule Designer.
3. In the Rule Designer, right-click the point of view or allocation component you want to copy in the rules flow
chart, and select Copy to copy only the component or Copy Group to copy the component and the associated
components within it.
4. Do one of the following tasks:
◦ To paste the component into the same rule, right-click the location in the flow chart where you want to
paste the component, and select Paste.
◦ To paste the component into a different rule, open the rule, right-click the location in the flow chart
where you want to paste the component, and select Paste.
Note: You can also select Edit and Paste.
5. Select File and Save.
How can I delete a point of view or allocation component?

You delete a point of view or an allocation component from the System View. Since point of view or allocation
components can be used in only one rule, you can delete these components by removing them from the rule to which
they belong.
To delete a point of view or an allocation component:

2. Right-click the rule that contains the point of view or allocation component you want to delete, and select
Open. The rule is displayed in the Rule Designer.
3. In the Rule Designer, select the point of view or allocation component you want to delete in the flow chart.
90
4. Right-click the point of view or allocation component.

5. Select Remove to confirm the removal of the component.
Note: If the allocation component is within the point of view component, then removing the point of view
component removes the allocation component.
6. Select File and Save.
Generate Allocations and Periodic Entries Manually

This example demonstrates how to generate an allocation or periodic entry manually from the Oracle Fusion General
Ledger.
You are the General Accountant for InFusion America Inc. You have created allocation and periodic journal entry
definitions for several monthly entries. You now generate these entries.
Note: Schedule allocations and periodic entries in the Journals work area for automatic generation. The accounting
period automatically increments for each subsequent run if defined as a Run Time Prompt for the Allocation Rule
selected.
Prior to generating the allocation and periodic entries, the following tasks must be completed:
• The period is set to Open or Future Enterable. You post in open periods, but generation can take place in
either an open or future enterable period.
• The rules or rules sets have been defined, validated, and deployed successfully from the Calculation Manager.
• The journal balances, which are inputs for the allocation or periodic rules, are entered and posted in the proper
period.
Generating Allocations and Periodic Entries Manually

1. From the Navigator, click the Journals link to open the Journals work area.
2. In the task pane of the Journals page, click the Generate Allocations link to open the Submission page.
3. Optionally select one or all of the following options:
◦ Print Output
◦ E-mail me the output
◦ Notify me when this process ends
4. Select a rule or rule set from the list of values.
5. Enter the submission parameters, including Ledger, Balancing Segment Value, and Period. The application
automatically sets the last day of the submission period as the Accounting Date and Calculation Effective Date.
6. Accept the selected check box for the Post Allocations option to enable the process to post the journal entries.
If you deselect the check box for the Post Allocations option, you must either manually post or define an
AutoPost Criteria Set to post automatically.
7. Click Submit.
After the generation process is complete, the journal entries created by the process are available for inquiry on
the Journals page.
91
Overview of Revaluations
The revaluation process is used to adjust account balances denominated in a foreign currency. Revaluation adjustments
represent the difference in account balances due to changes in conversion rates between the date of the original
journal and the revaluation date. These adjustments are posted through journal entries to the underlying account with
the offset posted to an unrealized gain or loss account. All debit adjustments are offset against the unrealized gain
account and all credit adjustments are offset against the unrealized loss account. If the same account is specified in the
Unrealized Gain Account and Unrealized Loss Account fields, the net of the adjustments is derived and posted.
For balance sheet accounts, the revaluation journal entries are reversed in the next period. AutoReverse can be used
to automate the reversals. For income statement accounts that use the PTD method of revaluation, the revaluation
journals aren't reversed since each period's revaluation adjustment is for that period.
In Oracle Fusion General Ledger, the revaluation functionality provides the following advantages:
• Full multicurrency functionality to eliminate currency barriers across a global business.

• Predefined revaluation rules to ensure consistency in generation of revaluation entries each period.
• Usage of prevailing currency normalization accounting standards including:
◦ US Financial Accounting Standards Board, Financial Accounting Statement No. 52 (FAS 52), Foreign
Currency Translation.
◦ International Financial Reporting Standards, International Accounting Standard No. 21 (IAS 21), The
Effects of Changes in Foreign Exchange Rates.
• Support for multiple balancing segments to provide clarity in tracking the profitability and performance for
more distinct segments of your enterprise in any currency
Related Topics
• Revaluation Process
• Overview of Revaluation Unrealized Gains or Losses
• How Income Statement Accounts Are Revalued
• Revalue Across Multiple Balancing Segments
92
Implementing Accounting Hub Accounting Transformation
6 Accounting Transformation
Overview of Accounting Transformation Configuration

Overview of Oracle Accounting Hub Cloud
Oracle Accounting Hub provides the flexibility and control that you need in the implementation, expansion, and
maintenance of subledgers.
• 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 of detailed, auditable
journal entries.
• Use modern reporting tools 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, corporate performance, and to make business decisions.
Oracle Accounting Hub

This figure illustrates the Accounting Hub process flow.
93
For additional information about Oracle Accounting Hub Cloud, see the Oracle Financials Cloud Accounting Hub Best
Practices guide on the Oracle Help Center.
Accounting Transformations
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, and point of sales applications.
Accounting Transformation Steps

Complete the steps described in the following table in the order listed to account for transactions coming from different
source systems.
This table contains the steps in the uptake process which include analyze, build, and implement and test.
94
Implementation Phase Step Number Description
Analyze 1 Analyze transaction flows and activities to

determine the transaction life cycle to capture.
2 Analyze your accounting, management

reporting, audit, and reconciliation
requirements. Ensure that the source system
provides the required attributes to generate this
information.
Build 3 Register the source system with transaction

types and details using the rapid
implementation spreadsheet template.
4 Configure accounting rules and assign

accounting method definitions to ledgers.
Implement and Test 5 Upload transaction data for testing.
6 Perform comprehensive testing to ensure that

all accounting is correctly generated.
Related Topics
• How You Analyze Source Systems
• Register a Source System Using a Spreadsheet
• Upload Transaction Data for Accounting Hub
Analyze Source Systems

How You Analyze Source Systems
As a best practice, when performing the source system analysis complete the following:
1. Analyze and Identify Transaction Type Life Cycle

A source system that generates transactions as part of a business process has potential financial impact requiring
creation of accounting entries. As a key step to create accounting entries, these transactions must be distinctly
identified as different transaction types.
Examples of transaction types from revenue recognition or billing source systems include:
• Complete an invoice.
• Record a payment.
• Record late charges.
95
Examples of transaction types from a point of sale source systems include:
• Record an order.
• Accept a payment.
• Receive a payment.
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 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
for processing. In some cases, summarized transaction type information, such as overall customer activity for the day, is
sent for accounting transformation.
2. Analyze Accounting, Reporting, Audit, and Reconciliation Requirements for

Transaction Types
Some source systems may already produce accounting entries, while 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 determine which subledger journal entry rule set components to define for source systems data to
be transformed into subledger journal entries.
Journal entry rule set components include:
• Description rules
• Account rules
• Journal line rules
• Supporting references
Such an analysis should, at a minimum, answer the following questions:
• Under what conditions are each of the lines in the 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?
96
Using the example of a loan origination transaction type, determine what are the sources that store the transaction
information for a journal entry? Visualize the journal entries that you would like to create for a loan origination
transaction type and list all the sources for its transaction information.
This table contains a journal entry, with Side, Accounting Class, Accounting and Debit and Credit amounts.
Side Accounting Class Account Debit Credit
Debit Loan Receivables 111-000-30201-0000-206-0000-0000

500,000 USD None
Credit Cash 111-000-21355-0000-104-0000-0000

None 500,000 USD
• In the table 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 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, then the cost center is '0000'.
- If the loan type is fixed rate, then the cost center is '2120'.
For management reporting and control, what type of information is 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.
Examples of transaction attributes include:
• Amounts including entered, accounted and conversion data

• Dates
• Descriptions
• General ledger accounts
• Customer Information
• Transaction type information
• Product information
3. Additional Modeling Considerations

Additional considerations when you model the subledger per your requirements.
97
Sample questions to ask during planning:
If you have more than one transaction type:
• How do you report each of the transactions? This results in a number of transaction types.
• Do you require centralized information or separate view?
◦ For example, how do you plan to upload fixed and adjustable mortgage rate transactions, as one
subledger source system, or as separate subledger source systems?
- One subledger source system consolidates the transaction data upload and reporting view.
- Separate subledger source systems enable the use of a unique accounting event class for each
source system. With separate source systems, you can configure accounting rules for each
accounting event class. For example, you can configure the automatic reversal on accrued
subledger journal entries at a specified date or period for a specific accounting event class.
4. Analyze the Configuration of Accounting Rules in Accounting Hub

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.
Journal Entry in Source System
This figure illustrates a journal entry.
Accounting Rule Configuration in Accounting Hub
This image illustrates the subledger flow as detailed in the Manage Accounting Rules topics.
98
The next implementation step will be registering your source system, as detailed in additional topics.
Related Topics
Manage Source Systems

Register a Source System
In this procedure you register a source system into Oracle Accounting Hub.
In Oracle Accounting Hub, download the setup template:

1. On the Setup and Maintenance work area, click the Implementation Projects button.
2. Search for the FAH implementation project.
3. Expand the task list: Define Accounting Entry Configuration for Rapid Implementation.
4. Select the task: Create Subledger Application Setups in Spreadsheet.
5. Click Go to Task.
6. Select the Download Setup Template button.
7. Click Save As and save the file on your local drive.
In Microsoft Excel, populate the setup template:
1. Open the downloaded template from your local drive.
2. Review the instructions tab for instructions on completing the template.
3. Enter your data into the spreadsheet worksheets:
a. Click the Source System worksheet and enter data in these fields.
- Source System Name
99
- Source System Short Name

- Source System Transaction Name
- Source System Transaction Short Namee
b. Click the Transaction Information worksheet and enter data in these fields:
- Source Name
- Source Short Name
- Source Type
- Source Journal Display
c. Click the Line Information worksheet and enter data in these fields:
- Source Name
- Source Short Name
- Source Type
- Source Chart of Accounts Value
In Microsoft Excel, validate the setup template and generate a .zip file:
1. Click the Source System worksheet.
2. Click Validate.
3. Click OK on the confirmation message. The .zip file was created and saved in the same local folder as the
downloaded file.
In Oracle Accounting Hub, upload the .zip file.
1. Navigate to the task: Create Subledger Application Setups in Spreadsheet.
3. Click the Upload Setup File button.
4. Click Browse.
5. Browse your local drive for the .zip file you created.
6. Select the file.
7. Click Open.
8. Click Import. Wait until the process completes.
9. Click OK.
10. Click Done.
In Oracle Accounting Hub, review your new subledger application.
1. Navigate to the task: Manage Subledger Application.
3. In the Select Scope window:
◦ Select the Manage Subledger Application option.
◦ In the Subledger Application Setup drop-down list, select Select and Add.
◦ Click Apply and Go to Task.
◦ Search for the subledger name, as defined in the Source System Name field in the spreadsheet.
◦ Select the subledger.
◦ Click Save and Close.
4. Preview the registered source system on the Manage Subledger Application page.
◦ Expand Event Model components.
◦ Click Cancel.
100
5. Preview the generated sources:

◦ Select the Manage Source task.
◦ View the sources.
◦ Click Cancel.
6. Preview the assigned accounting attributes:
◦ Select the Manage Accounting Attributes task.
◦ View the accounting attributes.
◦ Click Cancel.
Related Topics
Register a Source System Using a Spreadsheet

After completing the source system transaction flow analysis, you can use a spreadsheet to register your source
systems in Accounting Hub. The spreadsheet registration accelerates the time from implementation and testing to
production.
Complete the following tasks to register your source system.
1. Download the Spreadsheet Template

Download the spreadsheet template using the Create Subledger Application Setups in Spreadsheet task.
Navigate: Setup and Maintenance work area > Define Accounting Entry Configuration for Rapid Implementation >
Create Subledger Application Setups in Spreadsheet
2. Populate the Spreadsheet Template

Populate source system and transaction information in the spreadsheet template.
The spreadsheet template has three worksheets:
1. Source System
2. Transaction Information
3. Line Information
Source System
On the Source System worksheet, enter the name of the source system and the transaction types.
In the Source System Transactions region, enter the source system name and a short name:
This table contains definitions of the Name and Short Name fields used in the spreadsheet.
Name Short Name
Name of the source system. Used as the column name in database.
101
Name Short Name
• Used as the subledger application

and event class.
Maximum length 25 characters.
This source system name is used as the registered subledger, event class, and journal source names in Accounting Hub.
• Event class represents the transaction and is used to group event types.
• Event types represent an event in the life cycle of a transaction that has accounting impact.
In the Transaction Types region, enter the transaction types.
This table contains definitions of the Name and Short Name fields used in the spreadsheet.
Name Short Name
Transaction type name. Used as the column name in database.
Maximum length 30 characters.
Transaction Information
The Transaction Information worksheet lists transaction information that can be used for accounting. These are header-
level information sources.
The worksheet includes three predefined required sources.
• By default, the Transaction Date provides the accounting date for booking the journal.
◦ You can add additional source attributes for the transaction date if there are multiple date options 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.
In the Transaction Information: List of Sources region enter the sources.
This table contains definitions of the Name, Short Name, Type and Journal Display fields used in the spreadsheet.
Name Short Name Type Journal Display?
Name of sources that appears in Used as the column header in the Used to describe the type of values Indicates whether this attribute
a drop-down list for accounting transaction data template. This from the source system. is shown on report and inquiries,
rules. template is used to upload source along with the journal.
system transactions. Available values are:
Maximum length 80 characters. Acceptable values are Yes or No.
• Text:
In the user interface, these
◦ Where length can be less than are known as user transaction

the Alphanumeric source type identifiers.
of 100 CHAR characters.
Up to ten rows can be used.
• Number:
102
Name Short Name Type Journal Display?
◦ A valid numeric data type.
• Date:
◦ A valid date data type.
• Long Text:
◦ Source type: VARCHAR2.

Where length can be greater
than the Alphanumeric
source type of 100 CHAR
characters, but is less than
1000 CHAR characters.
Up to 50 text, 10 number, 10 dates,
and 5 long text sources can be
defined.
This includes the three predefined

required sources.
Line Information
The Line Information worksheet lists 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 transaction and 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 there are multiple different values that use the same source attribute. In that case,
you must manually map the related accounting attributes with these additional sources from the user interface.
In the Transaction Lines Information: List of Sources region enter the line sources.
This table contains definitions of the Name, Short Name, Type and Chart of Accounts Value fields used in the
spreadsheet.
Name Short Name Type Chart of Accounts Value?
Name of sources that appears in Used as the column header in the Used to describe the type of values Indicates that the source can be
a drop-down list for accounting transaction data template. This from the source system. used to derive an account.
rules. template is used to upload source
system transactions. Available values are: Acceptable values are Yes or No.
Do not add Line Number source
name, as this name is reserved • Text: Only text type sources can be used
for automatically created internal in segment rules.
source.
◦ Where length can be less than
the Alphanumeric source type Examples of sources that are
Maximum length 80 characters. of 100 CHAR characters. typically used to derive the general
ledger account:
• Number:
103
Name Short Name Type Chart of Accounts Value?
◦ A valid numeric data type. • Account

• Cost center
• Date:
• Company segment value
◦ A valid date value.
• Long Text:
◦ Source type: VARCHAR2.

Where length can be greater
than the Alphanumeric
source type of 100 CHAR
characters, but is less than
1000 CHAR characters.
Up to 100 text, 30 number, 10
dates, and 5 long text sources can
be defined.
This includes the three predefined

required sources.
3. Validate
To verify the accuracy of the content in the spreadsheet template, use the Validate icon on the Source System
worksheet.
• If there is an error, 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.
4. Generate .zip File

Generate the .zip file by using the Generate .zip icon on 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.
5. Upload .zip File

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 there is any error during the upload process, you're prompted with an error message. Correct the error in the
spreadsheet in the fields noted in the error message.
104
If there is no error:
• The source system is now registered in Accounting Hub.

• One transaction object at header and line levels is created.
6. Verify Source System

Verify the uploaded source system and transaction information from the user interface.
You can update the uploaded objects from the user interface. For example:
• Accounting Event Types:
◦ 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's used to create accounting rules.
◦ You can revise the sources. These revisions are:
- Source names can be revised to be more business user-friendly so they're easily understood when
configuring accounting rules.
- Sources that correspond to accounting flexfield identifiers can be marked as such.
◦ 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 the 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.
◦ Add and update source assignments to accounting attribute.
- You can add and make updates to the source assignment to the accounting attribute if you have
other sources available. For example, when you have more than one transaction date source value.
7. Configure Accounting Rules

Next, configure the accounting rules using the sources from the transaction information.
Use the streamlined navigation across rule components to configure the accounting rules.
• Start by using the Configure Accounting Rules task from the Setup and Maintenance work area. This task is
also embedded in the Define Accounting Entry Configuration for Rapid Implementation task list.
• Highlight the subledger application that you would like to 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.
Define Accounting Methods
105
Define accounting methods to group subledger journal entry rule sets. This determines how the source system
transactions are accounted for a given ledger.
Assign journal entry rule sets to event class and event type combinations in an accounting method. This determines
how the subledger journal entries for that class or type are created.
The following are the components of a journal entry rule set:
This table contains the accounting rule names and descriptions.
Rule Description
Journal Line Rule Determine basic information about a subledger journal entry line. Such information includes whether
the line is a debit or credit, the accounting class, the currency, the amounts, and conversion rates.
Description Rule Determine the descriptions that are included on subledger journal entry headers and lines. Include
constant values, transaction attribute, and transaction information in descriptions.
Account Rule Determine which account is used for a subledger journal entry line.
Supporting Reference Optionally used to store additional source information about transactions. Are useful for reconciliation
of accounting to source systems, as well as reporting.
Conditions
You can attach conditions to journal line rules, description rules, and account rules components. A condition combines
constants, source values, and operands to indicate when a particular journal line rule, description, or account rule is
used. For example, for mortgage loans, you can elect to use a specific loan receivable account based on the loan type.
Note: To obtain a listing of accounting rule setup by ledger, submit the Subledger Accounting Method Setups Report.
Related Topics
• Accounting Transformations
• Oracle Fusion Subledger Accounting Predefined Reports
Considerations for Registering a Source System

To achieve a successful implementation of Accounting Hub, certain points must be considered.
106
Considerations
1. 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
providing better performance. Specific benefits are:
- If you run two Create Accounting processes at the same time for different applications, they are
much less likely to contend for database resources.
2. Determine what source data is required to create subledger journal entries from transactions.
3. Analyze the transaction life cycles that create accounting impact.
4. Determine how often to upload subledger transaction data into Accounting Hub. This may depend on the
immediacy and volumes of accounting requirements in your company.
Related Topics
• Accounting Event Model
Accounting Event Model

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 Accounting Hub are based on event class and event types.
• An event type must be unique within an application.
.
This figure illustrates an accounting event model for a loan application.
107
Event Class
An event class groups the related transaction information and attributes within a source system.
The event class is created using the registered source system name. For example, the Loans source system.
Event Types
When registering a source system, you can specify the event types as the transaction types of the source system.
For example, the event types Loan Origination and Loan Scheduled Payments are the types of transactions that have
differences in their functional and operational implications.
User Transaction Identifiers

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.
• When you register the source system using the spreadsheet template, use the Journal Display column to
identify sources that are the user transaction identifiers.
• You can specify up to ten columns from the transaction sources that are available for inquiry and reports.
The transaction data that identifies the transaction varies by subledger application.
Accounting event reports and inquiries display the transaction identifiers and their labels 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 the
accounting event hasn't been processed.
The user transaction identifier values are displayed at the time the accounting event reports and inquiries are run.
Accounting Sources
Sources are a key component for setting up accounting rules. Sources represent transaction and reference information
from source systems. Contextual and reference data of transactions that are set up as sources can be used in
accounting rules definitions.
When determining what sources should be available, it's helpful to begin the analysis by considering which information
from your source system has accounting impact.
Examples of sources that are accounting in nature include:

• Transaction date
• Entered currency
• Transaction amounts
In addition to sources required for accounting, there may be other sources used for reporting purposes.
Examples of information that may be useful as supporting attributes for subledger journal entries are:
• Transaction identification numbers such as:
108
◦ Loan number
◦ Customer number
◦ Billing account number
• Counterparty information
• Transaction dates
Provide a rich library of sources from your source systems for maximum flexibility when creating definitions for
subledger journal entries.
A distinct difference exists between sources and source values:
• Source is the metadata, or name of the transaction attribute, used to create accounting rules.
◦ For example: Transaction Date
• Source values are the value of the attribute, used by the Create Accounting process to create subledger journal
entries. These entries are based upon source assignments to accounting rules.
◦ For example: Aug 01, 2017
Sources
Create sources from any of these user interactions:
• Create initial sources automatically when registering a new source system configuration using the spreadsheet
mechanism.
• Add subsequent sources from the Manage Sources user interface after the initial upload of the source system.
◦ This table contains the data types that can be used when adding sources:
Source Value Data Type
Alphanumeric and fewer than 100 Alphanumeric

characters
Alphanumeric and between 100 and Long

1000 characters
Numeric Number
Date Date
Note: After adding new sources from the UI, and before importing any new transactions, you must
download the latest transaction template.
109
To set up appropriate subledger journal entry rule sets, users and those implementing must understand the origins,
meaning, and context of sources.
Use business-oriented names for sources to enable accountants and analysts to effectively create accounting rules.
• Enables users to easily identify a source.

• Ensures consistency in nomenclature.
Accounting Attribute Assignments

The Create Accounting process uses the values of sources assigned to accounting attributes and accounting rules to
create subledger journal entries.
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.
Each accounting attribute is associated with a level:
1. Header: Used when creating subledger journal entry headers.

2. Line: Used when creating subledger journal entry lines.
Minimum Required Accounting Attribute Assignments

To create a valid journal entry the following accounting attribute assignments are required. Accounting Hub predefines
the values:
This table contains the required accounting attributes.
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 details and descriptions of these attributes are included in the Accounting Attributes section.
Accounting Attributes
Accounting attribute groups are represented in these tables.
110
Accounting Date
• Accounting Hub predefines Transaction Date as the 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 in 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.
CAUTION: If the application requires automatic reversal on accrued journal entries at a specified date or
period, you must configure the Accrual Reversal Accounting Date Source attribute before configuring the
journal entry rules for an event class.
• Accounting Hub doesn't predefine any source assignment to the Accrual Reversal Accounting Date Source
accounting attribute.
This table contains the valid accounting attributes for the Accounting Date group.
Accounting Data Type Journal Entry Level Assignment to Rules Assignment Validation Rules
Attributes Required?
Accounting Date Date Header Event Class Yes Should be in open

general ledger period.
Journal Entry Rule Set
Accrual Reversal Date Header Event Class No Should be later than

Accounting Date the accounting date.
Source Journal Entry Rule Set
Distribution Identifier
• The distribution identifier information links subledger transaction distributions to their corresponding journal
entry lines.
• The Accounting Event Type Code and First Distribution Identifier accounting attributes are predefined to the
Distribution Type and Line Number sources.
This table contains the valid accounting attributes for the Distribution Identifier group.
Accounting Event Type Alphanumeric Line Event Class Yes

Code
First Distribution Alphanumeric Line Event Class Yes

Identifier
111
Entered Currency
• 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 predefines source assignment to these accounting attributes. Additional sources can be
manually assigned to support cross-currency transactions.
The table contains the valid accounting attributes for the Entered Currency group.
Entered Currency Alphanumeric Line Event Class Yes A valid currency.

Code
Journal Line Rule
Entered Amount Number Line Event Class Yes
Journal Line Rule
Ledger Currency
• The Create Accounting process uses the ledger currency accounting attributes to calculate journal entry
accounted amounts.
• Accounting Hub calculates the accounted amount as entered amount multiplied by the conversion rate. If the
entered currency is the same as the ledger currency, the Create Accounting process ignores the conversion type
and conversion rate.
• For event classes that support foreign currency transactions, and therefore more than one conversion rate and
reporting currency amount, multiple event class accounting attribute assignments are created.
◦ If a single line of transaction data is provided and the entered currency for debit and credit lines are
different, then more than one Entered Currency accounting attribute assignment is required.
This table contains the valid accounting attributes for the Ledger Currency group.
Accounted Amount Number Line Event Class No
Journal Line Rule
Conversion Date Date Line Event Class No
Journal Line Rule
Conversion Rate Number Line Event Class No
112
Journal Line Rule
Conversion Rate Type Alphanumeric Line Event Class No A valid general ledger
conversion rate type or
Journal Line Rule user.
Exchange Gain Account, Exchange Loss Account
Note: If implementing the exchange gain and loss feature, you can assign predefined account sources as the
exchange gain or loss account.
• The Create Accounting process determines whether there is an exchange gain or loss. The process derives the
account based on the account rule assigned to the journal line rule with the Gain or Loss side in the journal
entry rule set.
• If Gain or Loss journal line rules aren't defined, then the value from the source mapped to the accounting
attribute, Exchange Gain Account and Exchange Loss Account, are used as the exchange gain or loss account.
• The Create Accounting process raises an exception if unable to create exchange gain or loss line for the
transaction in these cases:
◦ If Gain or Loss journal line rules aren't defined and sources haven't been mapped to these accounting
attributes
◦ If the mapped source doesn't contain any value.
• Predefined assignments aren't provided for these accounting attributes.

• If the subledger supports foreign currency or cross-currency transactions that may result in exchange gain or
loss, Oracle recommends that you perform one of the following:
a. Define accounting rules to generate exchange gain or loss lines whenever applicable for the transaction.
- Define two journal line rules if you would like to use separate account and accounting class for
exchange gain and loss. Journal line rules with side Gain are used for the exchange gain. Journal
line rules with the side Loss are used for the exchange loss. Optionally, you can define just one
journal line rule with side the Gain or Loss if only one accounting class is used.
- Define two account rules to return the exchange gain account and the exchange loss account.
Optionally, define just one account rule if the same account is used for both the exchange gain and
loss.
- Assign the exchange gain or loss journal line rules and appropriate account rule to the journal
entry rule set.
b. Assign sources to the Exchange Gain Account and Exchange Loss Account. Populate the sources with the
account combination ID of the exchange gain or loss account already defined in Oracle General Ledger.
This table contains the valid accounting attributes for the Exchange Gain Account, Exchange Loss Account group.
113
Exchange Gain Number Header Event Class No

Account
Exchange Loss Number Header Event Class No

Account
Gain or Loss Reference
• The Create Accounting process groups lines with the same Gain or Loss Reference together when calculating
exchange gain or loss. The total of the accounted debit amount and the accounted credit amount are calculated
for lines with the same Gain or Loss Reference within a journal entry. Then, the difference between the total of
the accounted debit amount and the accounted credit amount is considered the exchange gain or loss amount
and the exchange gain or loss line is created if applicable.
• Predefined assignments aren't provided for this accounting attribute.
• Oracle recommends that you assign a header level source to this accounting attribute so that only one
exchange gain or loss line is created for a subledger journal entry, should there be any exchange gain or loss.
This table contains the valid accounting attributes for the Gain or Loss Reference group.
Gain or Loss Reference Alphanumeric Line Event Class No
Multiperiod Accounting
• The multiperiod accounting attributes are relevant to applications that require the multiperiod accounting
feature to generate accounting in more than one accounting period, for a single transaction.
• Either no multiperiod accounting attributes should be assigned to sources or all multiperiod accounting
attributes should be assigned to sources.
This table contains the valid accounting attributes for the Multiperiod Accounting group.
Multiperiod Start Date Date Line Event Class Yes, if another Required if the
accounting attribute in Multiperiod End Date
Journal Line Rule the same group has an has a value.
assignment.
Multiperiod End Date Date Line Event Class Yes, if another Required if the
accounting attribute in Multiperiod Start Date
Journal Line Rule the same group has an has a value.
assignment.
Must be later than
Multiperiod Start Date.
114
Reconciliation Reference
• The Reconciliation Reference accounting attribute is relevant to all subledger applications to enable clearing
account reconciliation from subledgers.
• The reconciliation reference is stored on subledger journal entry lines and subsequently passed to general
ledger for use in the clearing account reconciliation feature.
• To start populating reconciliation references on subledger journal entry lines, perform these steps in Subledger
Accounting:
a. Assign sources to the Reconciliation Reference accounting attribute for the event class in the Manage
Accounting Attributes page.
b. Define a new journal line rule and assign a source to the Reconciliation Reference accounting attribute.
c. Add the journal line rule to the journal entry rule set assigned to your ledger's accounting method and
activate the assignment.
Reconciliation Alphanumeric Line Event Class No

Reference
Journal Line Rule
Transfer to GL indicator
• This accounting attribute is used to indicate whether the journal entry created by the Create Accounting
process will be transferred to General Ledger. Valid values are
◦ Y or NULL - Subledger journal will be transferred to GL.

◦ N - Subledger journals won't be transferred to GL. The untransferred journal won't appear in the
subledger period close exception report, and it won't prevent the GL period close.
• When source isn't assigned to this accounting attribute, the subledger journal entry will be transferred to
General Ledger.
Transfer to GL Alphanumeric Header Event Class No

Indicator
Control Reference
• Create Accounting uses control reference accounting attributes to check control totals for a transaction by
summing up the line-level source values and comparing to the header-level source value.
115
• In case of a difference, the process reports an error to indicate a potential data issue such as a missing
transaction line.
• Sources with no values populated are treated as zeroes by the calculation.
This table contains the valid control reference accounting attributes.
Control Header Number Header Event Class No Must be equal to the

Reference sum of Control Line
Reference values for
the transaction.
Control Line Reference Number Line Event Class No
Here are some examples of using control reference:
• Check control totals for a transaction: Assign a header level Total Line Amount source to control header
reference and a line level Default Amount source to control line reference. For a transaction of three lines with
Default Amount 100, 200 and 150 respectively populate Total Line Amount in the header file with 450.
• Check missing transaction lines: Assign a header level Total Line Count source to control header reference and
a line level Line Count source to control line reference. Populate Line Count with 1 for each line and Total Line
Count in the header file with the total number of lines.
Related Topics
• How Clearing Accounts Are Reconciled Automatically
• Reconciliation References and Journal Lines
Manage Transaction Objects

You can assign transaction and reference objects for each accounting event class. Based on the transaction objects,
sources are generated and are assigned to the corresponding accounting event classes. These sources are used to
create accounting rules. Subledgers pass information to the application through transaction object tables. The columns
in these tables are named after the source codes. Transaction and reference objects hold transaction information
that's useful when creating journal entry rules for accounting. The transaction and reference objects are defined for an
accounting event class so that source assignments to accounting event class can be generated using these objects. On
the Manage Subledger Application Transaction Objects page, you can view all the transaction objects, primary reference
objects, and secondary reference objects associated with the selected event class. You can select the objects to view
the details of source mappings. The source assignments display the particulars of the source, its assignment level, and
source details.
Transaction Objects
Transaction objects refer to the tables or views from which the Create Accounting program takes the source values to
create subledger journal entries. Source values, along with accounting event identifiers, are stored in the transaction
objects. The Create Accounting program uses this information to create subledger journal entries.
116
You have several options. You can:
• Create new tables as the transaction objects and create a program to populate them.
• Use views of your transaction data as the transaction objects.
• Use your transaction data tables as the transaction objects.
Types of transaction objects:
• Header transaction objects: Header transaction objects store one row with untranslated header source values
for each accounting event. The primary key of a header transaction object is the event identifier. You need to
provide at least one header transaction object for each accounting event class. All the transaction details that
are neither translated nor their values vary by transaction line, or distribution should normally be stored in
header transaction objects. Such as the Loan Number for a loan or the Contract Number for a contract.
• Line transaction objects: Line transaction objects are relevant when there are details for the accounting event
that vary based upon 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. Line transaction objects store untranslated line-level source
values. There should be one row per distribution, identified by a unique line number. The primary key of a line
transaction object is the event identifier and transaction object line number. Transaction details that are neither
translated nor their values vary by transaction line or distribution are normally stored in line transaction objects
columns, such as the Loan Number for a loan payment.
• Multi-Language Support (MLS) transaction objects: MLS transaction objects are relevant to applications that
support the MLS feature. MLS transaction objects store translated source values. There should be one row per
accounting event and language. The primary key of a header MLS transaction object is the event identifier
and language. The primary key of a line MLS transaction object is the event identifier, transaction object line
number, and language. Transaction details that are translated, and whose values don't vary by transaction
line or distribution, are normally stored in header MLS transaction object columns. Examples include Loan
Terms for a commercial loan. Implementors can avoid having to store source values in header MLS transaction
objects by using value sets and lookup types. Transaction details that are translated, and whose values vary by
transaction line or distribution, should normally be stored in the transaction object in columns defined in a line
MLS transaction object.
Reference Objects
Reference objects are useful for storing information that's used for creating subledger journal entries. This information
may not be directly from the source system or may be used for many entries, thus making it redundant. Use reference
objects to share sources' information across applications. For example, store customer attributes, such as the customer
class or credit rating in a reference object, and then use it to account for different journal entries in a loan cycle, such
as loan origination or interest accrual. Store information, such as bond ratings and terms, and use it to account for
entries across the life of bonds, such as interest accruals or bond retirement. Reference objects can either have a direct
relationship to transaction objects (primary reference object), or be related to other reference objects (secondary
reference object).
Sources
Sources are a key component for setting up accounting rules. Sources represent transaction and reference information
from subledger applications or reference systems. Contextual and reference data of transactions that are set up as
sources can be used in accounting rules definitions. Oracle Fusion Applications predefines sources for its subledger.
When determining what sources should be available for non-Oracle applications, it's helpful to begin the analysis by
considering which information from your systems is accounting in nature. Examples of sources that are accounting in
nature include general ledger accounts that are entered on transactions, the currency of a transaction, and transaction
117
amounts. Sources that aren't always required for accounting rules include items that are related to the transaction for
other purposes than accounting. Examples of information that may not be specifically for accounting, but which may
be useful for creating subledger journal entries, are transaction identification number (loan number, customer number,
or billing account number), counter party information, and transaction dates. Provide a rich library of sources from
your subledger applications for maximum flexibility when creating definitions for subledger journal entries. Predefined
sources are provided as part of the initial data of the application.
Manage Accounting Rules

Manage Accounting Methods
Create an Accounting Method
In this procedure, you create an accounting method.
Create an Accounting Method

Navigate to the Manage Journal Entry Rule Set page.
1. From the Setup and Maintenance work area, click the Implementation Projects button.
2. Search for the FAH Implementation project.
3. Expand the task list: Define Accounting Configuration for Rapid Implementation.
4. Expand the task list: Define Accounting Rules for Rapid Implementation.
5. Select the task: Manage Accounting Methods.
Create an accounting method.
1. Click Create icon.

2. Enter Name.
3. Enter Short Name.
4. Select Chart of Accounts.
5. In the Journal Entry Rule Set Assignments region:
a. Click Create icon.
b. Enter Event Class.
c. Enter Event Type.
d. Enter Rule Set.
e. Click Save.
6. Activate the rule set assignment.
a. In the Assignments region click Activate.
Assign the Accounting Method to the Ledger

You must assign this accounting method to the ledger you use for accounting and posting journal entries.
118

3. Expand the task list: Define Ledgers.
4. Select the task: Specify Ledger Options.
6. On the Specify Ledger Options page, Subledger Accounting region, select the new Accounting Method.
Related Topics
• Accounting Method
Accounting Method
Accounting methods group subledger journal entry rule sets. This facilitates the definition of consistent accounting
treatment for each accounting event class, and accounting event type, for all subledger applications. This grouping
enables a set of subledger journal entry rule sets to be assigned collectively to a ledger.
For example:
• A subledger accounting method can be defined to group subledger journal entry rule sets that adhere to and
comply with US Generally Accepted Accounting Principles (GAAP) criteria.
• By assigning a different subledger accounting method to each related ledger, you can create multiple
accounting representations of transactions.
Accounting rules can be defined with either a top-down, or a bottom-up approach.
• Top-Down: Define the accounting method, followed by components of each rule that must be assigned to it.
• Bottom-Up: Define components for each rule and then assign them as required.
The Create Accounting process uses the accounting method definition with active journal entry rule set assignments to
create subledger journal entries.
When an accounting method is initially defined its status changes to Incomplete. The status will also be Incomplete
after modifying a component of any accounting rule associated with the assigned journal entry rule set.
CAUTION: The accounting method must be completed, by activating its journal entry rule set assignments, so that it
can be used to create accounting.
The following definitions are used to define the journal entries, and are applied as updates to the accounting method:
• Updates to the predefined accounting method
• Assignment of journal entry rule sets for an accounting event class and accounting event type from the
accounting methods page
• Assignment of accounting methods to ledgers
• Activation of subledger journal entry rule set assignments
Updates to the Predefined Accounting Method

You may update a predefined accounting method by end dating the existing assignment and creating an assignment
with an effective start date.
Assignment of Journal Entry Rule Set for Accounting Event Class and Accounting Event Type
You create the assignment of a journal entry rule set for an accounting event class and accounting event type using the
accounting method page.
119
The following should be considered for assigning rule sets:
• If the accounting method has an assigned chart of accounts you can use journal entry rule sets that:
◦ Use the same chart of accounts

◦ Are not associated with any chart of accounts
• You can assign to existing journal entry rule sets or create a new one.
Assignment of Accounting Methods to Ledgers

If the accounting method has an assigned chart of accounts, it may only be used by ledgers that use the same chart of
accounts.
If the accounting method doesn't have an assigned chart of accounts, the accounting method can be assigned to any
ledger.
Activation of Subledger Journal Entry Rule Set Assignments

You can activate the subledger journal entry rule set assignments from the Accounting Method page. You can also
submit the Activate Subledger Journal Entry Rule Set Assignments process to validate and activate your accounting set
ups.
Accounting Method and Accounting Rules

This figure illustrates the relationship of the components used in an accounting method.
120
Related Topics
• Subledger Journal Entry Rule Set
• Journal Line Rules
• Account Rules
• Description Rules
Manage Journal Entry Rule Sets

Create Journal Entry Rule Set
In this procedure, you create a journal entry rule set.
Navigate to the Manage Journal Entry Rule Set page.

5. Select the task: Manage Journal Entry Rule Set.
Create a journal entry rule set.
2. Enter Name.
4. Select Event Class.
5. Select Event Type.
6. Select Chart of Accounts.
7. In the Journal Entry region:
a. Select Description Rule you created for the header..
8. In the Journal Lines region create a credit line.
b. Select Line Type = Credit.
c. Select Journal Line Rule.
d. Select Account Combination Rule.
e. Select Line Description Rule.
9. In the Journal Lines region create a debit line.
b. Select Line Type = Debit.
c. Select Journal Line Rule.
d. Select Account Combination Rule.
e. Select Line Description Rule.
f. Select Segment Rule.
10. In the Supporting References region:
121

b. Select Supporting Reference.
c. Click Create icon.
d. Select another Supporting Reference.
11. Click Save.
12. From the Actions menu select Activate.
13. Click Yes.
15. Click Done.
Related Topics
• Subledger Journal Entry Rule Set
Subledger Journal Entry Rule Set

Subledger journal entry rule sets provide the definition for generating a complete journal entry for an accounting event.
Select the option to define the subledger journal entry rule set for a particular accounting event class or accounting
event type.
If you're using multiple ledgers to meet divergent and mutually exclusive accounting requirements, you can vary
journal entry rule sets by ledger. Each of the subledger journal entry rule sets can meet a specific type of accounting
requirements.
For example, use US Generally Accepted Accounting Principles (GAAP) oriented subledger journal entry rule sets for a
ledger dedicated to US GAAP reporting. Use French statutory accounting conventions for a ledger dedicated to French
statutory reporting. These two sets of definitions have differences based on the setup of the various components that
make up their subledger journal entry rule sets.
Predefined subledger journal entry rule sets are provided for all Oracle subledgers. If specific requirements aren't met by
predefined subledger journal entry rule sets, create a copy of the predefined definitions, rename, and modify the copied
definitions and their assignments.
Subledger journal entry rule set assignments can be made at two levels, header and line. The following are the
subcomponents of a subledger journal entry rule set:
• Description rules
• Journal line rules
• Account rules
Assignment at Header Level

Header assignments define subledger journal header information and line assignments define journal line accounting
treatment.
A header assignment includes the following:
• Accounting date (required)

• Accrual reversal accounting date (optional)
• Description rule (optional)
122
Assignment at Line Level

You can define multiple subledger journal entry rule sets for an accounting event class or accounting event type. Using
the line assignment of the journal entry rule set assigned to the accounting event class or type, a single journal entry is
generated per accounting event per ledger.
The following can be assigned to a journal entry line:
• Journal line description rule

• Journal line rule
• Account rule
• Supporting references
Assignment of Description Rules

If a description rule is defined with sources, the sources must also be assigned to the accounting event class that's
assigned to the journal entry rule set. The description rule may be assigned at either the header or line level of the
journal entry or to both levels.
Assignment of Journal Line Rules

When assigning the journal line rule, you must identify the line type: Gain, Loss, Gain or Loss, Credit, or Debit. The
journal line rule must be assigned to the same accounting event class as the one assigned to the subledger journal entry
rule set.
When assigning a journal line rule that's enabled for accounting for a business flow, the account combination and
certain accounting attribute values are copied from its related journal line having the same business flow class as the
current line. Optionally, copy the description rule into the current line instead of assigning a separate description rule.
When assigning a journal line rule that's enabled to copy from the corresponding line within the same journal entry, you
have the option to copy the account combination, the segment value, or the line description from the corresponding
line into the current line.
Assignment of Account Rules

The account rule assignment defines which accounts are used for the subledger journal line. If the account rule is set
up with a chart of accounts, it must have the same chart of accounts as the one assigned to the journal entry rule set.
When account rules are defined with sources, the sources must also be assigned to the accounting event class that's
assigned the journal entry rule set.
There are two types of account rules:
• Account Combination Rule: Assign an account combination rule to derive the account combination.
• Segment Rule: Assign a segment rule to derive a specific segment of an account. For example, a cost center or
a natural account segment.
Assignment of Supporting References

Supporting references may be used to capture transaction values on journal entry lines. A supporting reference can be
used on a journal entry rule set only if it's assigned a source from the event class of the journal entry rule set.
123
Related Topics
• Account Rules
• Supporting References
Manage Journal Line Rules

Create a Journal Line Rule
In this procedure you create a journal line rule.
Navigate to the Manage Journal Line Rules page.

5. Select the task: Manage Journal Line Rules.
Create a journal line rule on the Manage Journal Line Rules page:
2. Enter Name.
4. Enter Event Class.
5. Enter Side = Credit.
6. Enter Accounting Class.
7. Click Save and Create Another.
Repeat these steps to create another journal line rule, with a Side = Debit.
Related Topics
Journal Line Rules

Journal line rules are defined within the context of accounting event classes. A journal line rule can be used in a
subledger journal entry rule set that has the same event class. You may also assign conditions to the journal line rule.
How You Create Journal Line Rules

Journal line rules are assigned to journal entry rule sets.
To create a journal line rule, select values for options such as:
• Side (Debit, Credit, Gain or Loss)

For example, when a payables invoice is generated, the liability account should normally be credited. The
journal line rule must therefore specify the Side option as Credit. On the other hand, the payment of the
124
Payables invoice must be accounted with a debit to the liability account. A separate journal line rule must be
defined to create this debit line.
• Merge Matching Lines: To summarize subledger journal entry lines within each subledger entry. Journal entry
lines with matching criteria are merged. Here is the list of matching criteria that are used:
◦ Account combination
◦ Accounting class
◦ Anchor line (for PeopleSoft Accounting Hub Cloud)
◦ Budgetary control status
◦ Business flow class
◦ Conversion date
◦ Conversion rate
◦ Conversion rate type
◦ Currency
◦ Description
◦ Encumbrance type
◦ Gain or loss
◦ Gain or loss reference
◦ Merge matching lines
◦ Multiperiod accounting class
◦ Reconciliation reference
◦ Replaced account
◦ Rounding class
◦ Supporting references
◦ Switch side
◦ Third party
◦ Third-party site
◦ Third-party type
◦ Transaction rounding reference
• Accounting Class
◦ Select an accounting class to classify journal entry lines.

◦ For example, when a validated Payables invoice is accounted, the Item Expense and Liability journal lines
are created. In this case, the journal line rules used in the accounting rules are assigned Item Expense and
Liability accounting classes respectively.
125
• Switch Debit and Credit: Reverses a debit for a credit and a credit for a debit. For example, you can select this
option to ensure that if a negative amount is entered for a journal, the journal line is created with positive
amount in the opposite side.
• 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.
• Accounting Attributes: When creating a journal line rule, accounting attribute assignments are automatically
established. These are 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.
• Advanced Options
◦ The Subledger Gain or Less Option: Applies only to amount calculations for the primary ledger. Gain or
loss amounts aren't converted to reporting currency or nonvaluation method secondary ledgers. If the
option is selected, 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 upon conversion to the ledger currency. Foreign exchange gain or loss amounts
occur 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, groups journal lines together and
calculates transaction rounding. Subledger transaction rounding differences can occur when a
transaction has multiple-related applied-to transactions, such as a Receivables invoice that has multiple
associated receipts.
◦ The Link Journal Lines Option: Determines 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 described in this table:
This table contains the Link Journal Line Options and their descriptions.
Link Journal Lines Option Description
None No link is established.
Copy from corresponding line Build account for a journal line using segments from the offsetting entry of the current journal line.
For example, when the business process requires that a cost center incurring an expense must also
bear the invoice liability and cash outlay.
Business flow Link logically related business transactions.
For example, when recording the closing of a loan, you can link to the account that was used to book
the loan origination. Journal line rules that are linked must also be assigned the same business flow
class.
126
Defining Conditions for Journal Line Rules

You may set conditions to specify whether the journal line rule is used to create a subledger journal entry line. If the
conditions are true, the line rule is used to create a subledger journal entry line. Use sources to create these conditions.
For example, you can set up a condition that creates a journal line to record tax, only if there's tax for an invoice. The line
type and account class mentioned here are examples of sources.
• The condition for a Payables invoice tax journal line rule could be:
◦ Where Line Type = Tax

◦ When this condition is true, there's tax for a payables invoice line. A journal entry line is created to record
the accounting impact of the tax.
• Similarly, the condition for an invoice tax journal line rule could be:
◦ Where Account Class = Tax

◦ In this case, if there's an account class of Tax, the journal line is used to record the accounting impact of
the tax.
Another example is a condition that creates a journal line for freight when there are freight charges on an invoice.
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. If the conditions of all the journal line rules assigned to the journal
entry rule set aren't met, the transaction is processed without the creation of any subledger journal entries, and the
event status is set to Processed.
Note: Constant values that are used in any Conditions region must not contain the following characters:
• "
• ,
• &
• |
• (
• )
• '
For example, in the condition "Project Type" = ABC (123), the constant value following the equal sign, ABC (123),
contains restricted characters ( ) that enclose 123 and is invalid.
127
Related Topics
• Examples of Creating Condition
Manage Account Rules and Mapping Sets

Create Account Rules and Mapping Set
In this procedure you create a mapping set and account rules.
Create a Mapping Set

Navigate to the Manage Mapping Sets page.
5. Select the task: Manage Mapping Set.
Create a mapping set on the Manage Mapping Sets page.

2. Enter Name.
4. Enter Output Type.
• In the Input Source region:

a. Select Actions > Select and Add.
b. Search and select Source.
c. Click OK
• In the Chart of Accounts region:
b. Enter Chart of Accounts.
c. Enter Segment.
d. Click Save.
• In the Mappings region:
b. Enter Loan Type.
c. Enter Output for Department.
d. Click Create icon.
e. Enter additional Loan Type and Output for Department.
f. Click Save and Close.
g. Click Done.
128
Create Account Rules

Create an account rule with a Constant value type on the Manage Account Rule page.
1. Select the Manage Account Rules task.

3. Enter Name.
5. Enter Chart of Accounts.
6. Enter Rule Type.
7. Click Save.
• In the Rules region:

b. Enter Value Type = Constant.
c. Enter Chart of Account.
d. Click Save and Create Another.
Create an account rule using a segment rule type and a mapping set.
1. Enter Name.
4. Enter Rule Type = Segment.
5. Enter Segment.
6. Click Save.

b. Enter Value Type = Mapping Set.
c. Enter Value = Mapping Set name.
d. Click Save and Create Another.
Create an account rule using an account combination rule type:

2. Enter Name.
5. Enter Rule Type = Account Combination.
6. Click Save.

b. Enter Value Type = Constant.
c. Enter Value.
d. Click Save and Close.
e. Click Done.
129
Related Topics
• How You Define Account Rules
Account Rules
Account rules are used to determine the accounts for subledger journal entry lines. In addition, you can specify the
conditions under which these rules apply. Using these capabilities, you can develop complex rules for defining accounts
under different circumstances to meet your specific requirements. You can define account rules for an account,
segment, or value set.
Account Rules by Account

Define account rules by account to determine the entire account combination. For example, an account rule defined by
account can be used to determine the complete supplier liability account in Oracle Fusion Payables.
Account Rules by Segment

Define segment rules to derive a specific segment of the general ledger account. For example, a particular segment like
the company segment can be determined from the distribution account.
Another segment can be determined with the use of a constant value. Creating the account one segment at a time
offers greater flexibility, but also requires more setup.
Use both segment based and account based rules to derive a single account. Segment-specific rules are used, where
they're defined, and take the remaining values from an account-based rule. For example, you can use an account rule
which is for all segments and also separately use a rule which is for one particular segment. Segment-specific rules take
precedence over the all segments account based rule.
Combine account rules with segment rules. In this case, the segment value is derived from the segment rule to override
the corresponding segment of the account. If the segment rule has conditions associated with the priorities and none
are met, no override occurs and the segment value is derived from the account rule.
Note:
• If the returned account is end dated with a date that's the same or before the subledger journal entry
accounting date, and an alternate account is defined in the general ledger, the alternate account is used. The
original account is stored on the journal line for audit purposes
• If the alternate account is invalid, the Create Accounting process creates the journal in the invalid status. An
error message is displayed to indicate the GL account is invalid.
• If the derived account or the alternate account is invalid and the Create Accounting process is submitted with
the process event parameter set to Invalid Account, the invalid account is replaced with the suspense account
defined in the ledger option for the ledger.
130
Account Rules by Value Sets

In the absence of a chart of accounts, you may define account rules based upon value sets. 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.
Sharing Account Rules across Applications

You may share account rules across applications in the following ways.
• Assign an account rule from the same or a different application to a journal line rule in the subledger journal
entry rule set. For example, to derive an expense account for journal line rule Expense, assign the Projects Cost
Account rule owned to the Payables journal line rule Expense.
• Create an account rule based on an account rule from another application and assign it to a journal line rule.
For example, you may create an account rule Invoice Expense Account referencing Project Cost Account
assigned in the Priorities region. You may attach the Invoice Expense Account rule to the journal line rule
Expense in the journal entry rule set.
Note:
• To share an account rule across applications, all sources used by the account rule must be available for the
event class.
• If the sources are available, an account rule is assigned to a journal line rule in the journal entry rule set.
Verification occurs to confirm that all sources used by the account rule are available for the journal line rule
accounting event class. Journal line rules are only available if the sources are shared; such as reference objects.
Account Rules and Mapping Sets

Mapping sets can be used to associate a specific output value for an account or segment. You can use mapping sets in
account rules to build the account.
Account Rules Conditions

In the account rules you may specify conditions for each rule detail line. Priorities determine the order in which account
rule conditions are examined. When the condition is met, the rule associated with that priority is used. Depending on
which of the defined conditions is met, a different account rule detail is employed to create the account.
The Create Accounting process evaluates conditions based on the priority of the rule detail. When the condition is met,
the rule detail is applied.
131
• "
• ,
• &
• |
• (
• )
• '
Related Topics
• Examples of Creating Condition
• How You Define Account Rules
How You Define Account Rules

You can define an account rule using the following rule types:
• Account combination
• Segment
• Value Set
Account Combination Rules

Set up account combination rules based upon the following value types:
1. Source Value Type: Derive the account combination by specifying a source.
Sources that have been set up as accounts can be assigned to an account combination rule. Subledger
Accounting then obtains the account combination identifier from the source.
2. Constant Value Type: Establish the account as a constant value.
For example, the constant could be a completed account combination from the chart of accounts specified. An
example is the account combination, 01.000.2210.0000.000. This is the simplest way to derive an account.
3. Mapping Set Value Type: Derive the account combination by referencing a mapping set.
Set up a mapping set to determine the complete account combination from the chart of accounts specified.
132
4. Account Rule Value Type: Derive the account by referencing another account rule.
The chart of accounts is optional when defining this type of rule. If the account rule has a chart of accounts
assigned, then all the related account rules must use the same or no chart of accounts.
Note: A chart of accounts must be specified for account combination rules using constants.
Segment Rules
Set up segment rules as follows:
• When a chart of accounts is specified, create a rule to derive the value for a specific segment from the chart of
accounts.
• If the chart of accounts isn't specified, create a rule to derive the value for an account segment with a specific
qualifier.
Set up segment rules using the same methods discussed in the preceding Account Combination Rules section. By
specifying different value types, users can select the way in which the segment value is derived.
Note: A chart of accounts must be specified for segment rules using constants.
Value Set Rules

Value set based rules can be created when a chart of accounts isn't specified, enabling you to share the same rule
between more than one chart of accounts. But, only if the segments in these charts of accounts share the same value
set.
Set up value set based rules using the same methods discussed in the preceding Account Combination Rules section.
Related Topics
• Account Rules
Mapping Sets
Mapping sets provide an efficient way to define a segment or account combination value for one or more transaction or
reference attribute values. Using such input and output mappings is simpler than using complex conditions on account
rules.
Based on the value of the source input, a single segment or a full account is derived.
Examples of source input value types:

• Transaction attributes
• Reference attributes
With mapping sets you can:
• Use up to 10 transaction or reference attributes as inputs into a mapping.
• Define default output value to use when actual input values don't 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 on the user interface or use the spreadsheet available in the Export option, and
then import.
133
Export allows:
◦ Exporting a template to create mappings.

◦ Exporting all mappings created for the mapping set to add or edit the current mappings.
Example
Assume a business operates in several regions, including:
• East
• South
• West
The business has a Region segment in their chart of accounts.
The region name can be the input for the mappings to derive the value of the region segment. You can create a
mapping set that maps region names to the corresponding region code.
This table contains region names and segment values used in this example.
Input Value (Region Name) Segment Value
East 01
South 02
West 03
Additional transaction information, such as transaction type and salesperson name, could also be used as inputs to help
derive a different segment value for each combination of the input values.
134
• "
• ,
• &
• |
• (
• )
• '
Related Topics
• How You Define Mapping Sets
• Accounting Sources
How You Define Mapping Sets

Define a mapping set when you have a matrix of input values that produce distinct output values. For each input value,
specify a corresponding account combination or segment output value. One or more related pairs of these input values
with the segment or account combination output values form a mapping set.
To define a mapping set, select the input sources, output type, and mappings. The mappings section displays how input
values are mapped to output values. You can define multiple mapping sets for different combinations of input sources.
To define mapping sets:
• Specify the output type:
◦ The output type for a mapping set can be an account combination, segment, or value set.
◦ Use value set:
- If the value set is used by more than one chart of accounts,

- And the mapping set can be reused across multiple charts of accounts.
◦ Expected input or output combinations are constant across the charts of accounts.
◦ Based on the selection, the mapping set provides the value for an account, segment, or value set.
135
• Select the input source:
◦ Specify the input source for mapping.
- The input source is provided for predefined mapping sets. You can select input sources through a
lookup or value set.
- You can add up to 10 input sources in a mapping set.
• Select either the chart of accounts, segment, or value set for which mappings are to be defined depending on
the output type entered.
• Define the mappings:
◦ For a given set of input values, enter the corresponding output value.
◦ The account rule uses this value to populate either the account or the segment.
- If the output type is a value set, the output value is an individual value from the value set entered.
- If the output type is a segment, the output value is an individual segment value.
- If the output type is an account combination, the output value is an entire account.
◦ If the input source is a GL account, enter a Transaction Chart of Accounts and a GL account in the context
of the transaction chart of accounts. The transaction chart of accounts refers to the chart of accounts
with which the transaction is associated, and this is usually the primary ledger's chart of accounts.
Mapping set with account combination output type can be assigned to account rule if:
• The account rule type is account combination, and it's not associated with any chart of accounts, or
• The account rule type is account combination, and it has been assigned the same chart of account as the
mapping set.
Mapping set with segment output type can be assigned to account rule if:
• The account rule type is a segment, and it's not associated with any chart of accounts, and the segment label
matches with the segment in the mapping set, or
• The account rule type is a segment, and it has the same chart of accounts and segment of the mapping set.
Mapping set with value set output type can be assigned to account rule if:
• The account rule type is value set, and the value set on the account rule and mapping set is the same, or
• The account rule type is a segment, and the value set on the mapping set is assigned to the chart of account
and segment of the account rule.
Assign a default value to the mapping set
• In certain situations, one of the rows can be assigned as a default value in the mapping set. This can be used in
cases where it's not possible to define all the values. When defining a row as default, enter the output value and
select the Set Default button. it's not required to enter any input values.
Identifying the Sources for New Mapping Sets
• When creating a new mapping set, the input sources have to be selected based upon the Event Class, where the
mapping set will eventually be used.
• Sources may or may not have a value set or lookup type assigned. You can assign a value set or lookup type if
the input source doesn't have one assigned yet. However, the mapping set works only if the value defined in
the value set or the lookup code matches with the input source value.
136
Example to Create Mapping Set with Single Source

In the following example, the chart of accounts is set up with four segments. A mapping set is defined with a value set
for Supplier Type as described in the following table.
This table contains examples of input values and output values.
Input Value Output Value
Services 01-100-6120-000
Consulting 01-400-6110-000
Assume that two invoices are entered, one for a supplier with a type of Services and one for a supplier with a type of
Manufacturing.
When using the mapping set, the source value Supplier Type is compared with the mapping set input values to
determine the account.
In this example, there's a match for the first case; the invoice with a supplier type of Services maps to an input value.
However, the invoice with a supplier type of Manufacturing doesn't map to an input value.
This table contains the derived accounts based on the example.
Invoice Supplier Type Output Value
1 Services 01-100-6120-000
2 Manufacturing No account generated
To ensure that invoice 2 is accounted, you may want to define a default output in the existing mapping set, or modify
the account rule to which the mapping set is assigned so that a different account rule priority is applied when supplier
type is Manufacturing.
Note: When a match isn't found in the mapping set, and there's no default value, and:.
• If an account combination rule is assigned to the journal line, then the segment value from the account
combination account rule will be used on the accounting entry.
• If an account combination rule isn't assigned to the journal line, then an exception will be raised for the
accounting entry.
Example to Create Mapping Set with Multiple Sources

In the following example, multiple input sources are set up with an account combination. This table contains examples
of input values and output values.
137
Inventory Organization Sub inventory Code Costing Category Item Number Output Value
Code Identifier
M1 * * * 99-100-1110-00
M2 LAA019 * * 99-100-1120-00
M2 * * * 99-100-1110-00
P1 UXA843 L100 * 99-120-1110-00
P1 UXA843 L200 A92348425 99-220-1110-00
P1 * * * 99-130-1110-00
* * * * 99-000-1290-00
In some cases, all the input values might not be relevant. For example,
• If inventory organization is M1, then always map to 99-199-1110-00 regardless of the sub inventory, cost
category, and item number, then use * (any value) for the last three sources.
• If inventory organization is M2 and sub inventory is LAA019, then map M2 to 99-100-1120-00, and other sub
inventory codes to 99-100-1110-00.
• If inventory organization is P1
◦ And if sub inventory is UXA843, and cost category L100, then for any item number map to
99-120-1110-00
◦ And if sub inventory is UXA843, and cost category L200, and item number A92348425, then map to
99-220-1110-00
◦ For other sub inventory, cost category, and item number, map to 99-130-1110-00
• For any other input value combination, map to 99-000-1290-00. The last row can be entered with output value
and then select the Set Default button.
Use any value (*) for multiple input mapping sets to indicate that the value of a particular input should be ignored for
certain mappings. Don't leave them blank. When * is used in one of the input sources, subsequent input value must also
be *. For example, the following mappings are invalid and can't be entered.
Code Identifier
* XXX123 * * 99-100-1110-00
M * A1234 * 99-100-1110-00
* * * 99999999 99-100-1110-00
138
Code Identifier
* A1234 * 99-100-1110-00
Note: If the account rule is already assigned to the journal entry rule set, and if the accounting method is active, then
run Create Accounting to verify if the mapping set is working as expected. there's no need to activate the accounting
method again after modifying or adding any mapping.
Related Topics
• Mapping Sets
• Manage Transaction Objects
Import Subledger Accounting Mappings

You can import high volume mappings that are greater than 2,000 lines using the subledger accounting import
mappings spreadsheet template.
To do this, you must first use the Create Mapping Set page to create a mapping set rule definition with the
corresponding input sources and output types.
Let's walk through the steps to access the template:

1. Navigate to the File-Based Data Import for Oracle Financials Cloud guide.
2. In the Table of Contents, click File-Based Data Imports.
3. Click Subledger Accounting Mappings Import.
4. In the File Links section, click the link to the Excel template.
Here are few things to keep in mind when preparing your data in the worksheet:
• Enter the required information for each column. Refer to the tool tips on each column header for detailed
instructions.
• Don't change the order of the columns in the template.
• You can hide or skip the columns you don't need to use, but don't delete them.
Settings That Affect the Subledger Accounting Mappings Import Process

The Subledger Accounting Mappings Import template contains an instructions tab, a tab that represents the table where
the data is loaded, and some example tabs that contain sample mappings for different scenarios. This table shows the
tabs in the Subledger Accounting Mappings Import template and their descriptions:
Spreadsheet Tab Description
Instructions and CSV Generation Contains information about using the template and generating CSV files.
Mappings Enter information about the subledger accounting mappings you're importing into the interface table.
Example1_CCID_Output Contains an example of mappings for a mapping set rule with the account combination output type.
Example2_Segment_Output Contains an example of mappings for a mapping set rule with the segment output type.
139
Spreadsheet Tab Description
Example3_Value_Set_Output Contains an example of mappings for a mapping set rule with the value set output type.
Example4_FlexAccountComb_Input Contains an example of mappings for a mapping set rule with the account combination input source
type.
Example5_FlexfieldSegment_Input Contains an example of mappings for a mapping set rule with the segment input source type.
How Subledger Accounting Mappings Is Processed

Create the Spreadsheet
Enter the mapping information in the Mappings worksheet. Refer to the tool tips on column headers for detailed
instructions. Here are some best practices that you must follow to minimize errors while uploading the mapping data:
• Make sure that Mapping Set Short Name is in the upper case.
• Confirm that the format for the Start Date and End Date columns is YYYY-MM-DD.
• If the end date value is given for a mapping line, you must also provide a start date value.
• Make sure that the Default Mapping column has only one of the following values:
◦ Blank
◦ N
◦ Y
Note: Don't use values such as No, n, Yes, or y because they're invalid.
• Specify only one mapping line as the default mapping.

• You must provide values for all mandatory fields. The mandatory fields can differ based on the output type of
the mapping set. Here are the details of mandatory fields for different output types:
Mapping Set Output Type Mandatory Fields for Output Type Mandatory Fields for Output Value
Account Combination Chart of Accounts Account Combination
Segment Chart of Accounts Segment or Value Set
Segment
Value Set Chart of Accounts Segment or Value Set
Value Set
140
• Make sure that no space or new line character is appended to the actual data as it may result in import failure
because of value mismatch.
• To delete an existing row from the Mappings sheet, select and right-click the row. Then, click Delete. Don't
press the Delete key to delete a row because the application can consider such rows as blanks on validation.
You can also refer the example worksheets for more information. For example, how to use the account combination or
segment value as the output for the mappings.
After you finish preparing the mapping data, click the Validate button to validate date format, line numbers, required
fields, and default mapping. Correct the reported errors and save the spreadsheet template.
Generate the Zip File
After you finish preparing the spreadsheet template, you need to generate a Zip file that's used to import data into the
application. Here is how you generate the Zip file:
1. On the Instructions and CSV Generation tab of the template, click the Generate CSV File button to generate a
Zip file containing one CSV file.
You can also enter mapping information directly in a CSV file instead of the spreadsheet template. To do
this, you must enter mapping information in the CSV file in the same format as in the Subledger Accounting
Mappings Import template. Here is the order of columns in the Accounting Mappings Import template:
◦ Line Number
◦ Application Name
◦ Mapping Set Short Name
◦ Chart of Accounts Short Name
◦ Transactions Chart of Accounts Short Name
◦ Value Set Short Name
◦ Segment Short Name
◦ Account Combination
◦ Segment or ValueSet
◦ Source Value 1
◦ Source Value 2
◦ Source Value 3
◦ Source Value 4
◦ Source Value 5
◦ Source Value 6
◦ Source Value 7
◦ Source Value 8
◦ Source Value 9
◦ Source Value 10
◦ Effective Start Date
◦ Effective End Date
◦ Default Mapping
141
2. Review the generated XlaImportMappingsTemplate.csv that's appended as a worksheet in the same

spreadsheet. It must have the same number of mapping lines that exist in the Mappings worksheet.
Load File for Import
After you generate the Zip file and verify the CSV file, you must load the Zip file to the interface and application
database tables. Let's look at the steps to load the Zip file.
1. Navigate to Tools > Scheduled Processes.

2. Click Schedule New Process.
3. Select the Load Interface File for Import process and then click OK.
4. In the Process Details dialog box, select Import Accounting Setup process.
5. Upload the Zip file that you generated and click Submit.
The mapping details are imported to the interface and application database tables.
Correct Import Errors
Here is how you can correct errors that occurred while loading the CSV file:
• Review the log and output files of the Load File to Interface child process for information about the data that
caused the failure.
• The Load Interface File for Import process ends in error and the Load File to Interface child process ends in
either warning or error.
• All rows that were loaded from the CSV file are deleted, even those rows that loaded successfully. This lets you
edit the erroneous data in the spreadsheet and resubmit without having to separate the successful rows from
the rows that need modification.
These are the steps to correct errors caused when validations are performed by the application:
• Review the log and output files of the Import Accounting Setup process.
• The output file provides the summary and details of the uploaded files, including any reported error.
Secure the Upload Mapping Process
You can use the Application Implementation Consultant role to upload the mapping template. However, you can also
define new roles to do this task. Make sure that you assign these rights to the new roles:
• The privileges to manage mapping sets such as the Manage Subledger Mapping Sets and Manage Subledger
Mapping Set Value privileges.
• A duty role to load interface file for import such as the FSCM Load Interface Administration duty.
Manage Description Rules

Create Description Rules and a User-Defined Formula
In this procedure you create a user-defined formula and description rules.
Create a User-Defined Formula

Navigate to the Manage Mapping Sets page.
142

5. Select the task: Manage User-Defined formulas.
Create a formula on the Manage Formulas page.

2. Enter Name. The Short Name is created but can be updated.
3. Enter Data Type.
5. Click Save.
• In this formula you abbreviate a loan type value. For example, if the loan type is Fixed Rate, then its new value is
FR; otherwise the value is AR.
In the Expression region:
a. Click Insert Function.
i. Enter Type = Conditional.

ii. Click Search.
iii. Select IF THEN ELSE
iv. Click OK.
b. Place the cursor after the IF,.
c. Click Source.
i. Select Subledger Application.

ii. Select Name = Loan Type.
iii. Click Search.
iv. Select Loan Type.
v. Click OK.
d. Click More.
e. Select Equal To (=).
f. On the IF line, after the = enter 'Fixed Rate' including the single quotes.
g. On the THEN line, enter 'FR'.
h. On the ELSE line, enter 'AR'.
i. Validate the formula.
i. Click Validate.
ii. Click OK on the Information message.
iii. Click Save.
j. Activate the formula.
i. Click Actions > Change Status > Activate.

k. Click Save and Close.
143
Create Description Rules

In this exercise, you create a header description rule for an accounting event. In this example, we display the loan type,
event type, and the customer number at the header level of the journal entry.
Navigate to the Manage Description Rules page.
1. Click Go to Task for the Manage Description Rules task.

3. Enter Name.
5. Click Save.
6. In the Rules region, enter the description rule components.
b. In the Description Details text box enter Loan Type.
c. Click Source.
i. In the Source Search enter Type, Formula.
ii. Select the formula you created in the prior step.
iii. Click OK.
d. In the Description Details text box, place your cursor at the end of the text and append:
e. Click Source.
f. Search by Name: Accounting Event Type Name.
g. Click OK.
h. In the Description Details text box, place your cursor at the end of the text and append:
i. Click Source.
j. Search by Name: Customer Number.
k. Click OK.
8. Click Save and Create Another.
In this exercise, you create a line description for an accounting event. In this example, we display the loan rate at the line
level of the journal entry.

2. Enter Name.
4. Click Save.
5. In the Rules region, enter the description rule components.
b. In the Description Details text box enter Rate:.
c. Click Source.
i. In the Source Search enter Name, Loan Rate.
ii. Click OK.
8. Click Done.
144
Related Topics
Description Rules
Use descriptions rules to define the elements of a description that appears on the subledger journal entry at the header
or the line. The definition determines both the content and sequence in which the elements of the description appear.
You can assign a condition to a description rule to determine that the description is selected for display if the condition
is satisfied.
Description Rule Definition

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.
Build descriptions using the available sources for the application.
The following is the description details that have been entered, using a literal and a source:
• Loan Origination Date = Origination Date
◦ Literal = Loan Origination Date

◦ Source = Origination Date
For example:
• Source value of the Origination Date = 11/01/11

• Journal entry description = Loan Origination Date 11/01/11
Related Topics
• Creating Conditions : Examples
Examples of Creating Condition

The following provides examples of defining an account rule with a condition.
145
Example 1: User-Defined Real Estate Application Account Rule Condition Example

This example defines an account rule for assignment to a loan journal line. The account rule has two priorities, a
mapping set and a constant.
• The first priority creates an output for an account based on the mapping set rule definition.
◦ A condition is created using the first priority rule. This rule is only used if the condition is met.
- The condition is Credit Status must not be null.

- The accounts derived from the mapping set rule are used if the Credit Status has a valid value.
Otherwise, the accounts derived from the entered constants value from the second priority are
used.
◦ This table contains the setup of the condition for the first priority:
( Source Operator Value )
( "Credit Status" isn't null )
• The second priority creates an output from a constant value (0.9100030.50034206331.0.0.0). No condition is
associated with the second priority.
Example 2: Oracle Fusion Assets Account Rule Condition Example

This example defines a rule for a capital purchase. The rule is applied if the distribution account cost center is the same
as the liability account cost center, and the asset tracking option is Yes.
This condition can be expressed as:
• Where Distribution Cost Center = Liability Cost Center and Asset Tracking option = Yes
This table contains the setup of the condition formula.
( Source Delimiter Segment Operator Value Delimiter Segment ) And Or
( "Distribution . "Cost = "Liability . "Cost ) 'AND'

Account" Center" Account" Center"
( "Asset = Yes )
Indicator"
The following two rows of data are used in the accounting event, to which the account rule and condition applies.
Account Rule Condition Example: Accounting Event Data
This table contains the values to which the condition is applied.
146
Account Invoice 1 Invoice 2 Asset Indicator
Distribution Account 02-640-2210-1234 01-780-6120-0000 Yes
Liability Account 01-640-2210-0000 02-782-2210-0000 Yes
In the Accounting Event Data table, assume the cost center segment is the second segment. When the account rule with
this condition is used the account rule is applied to derive the account of Invoice 1 only. For Invoice 2, (assets tracking
option = Yes), the cost center for the Distribution and Liability accounts aren't the same. Both conditions must be met in
order for the rule to apply.
Note:
• When an account source is used, you must also use a specific segment. Select All if the full account is required
to be used in the condition instead of a specific segment.
• The condition uses the account source and distribution account, along with a segment that you must provide.
In this example, the cost center segment is provided.
• When adding a user-defined formula or a condition to other setup rules, after selecting a source, the source
name is suffixed by an additional string such as (Payable, S, S) if the same source name is used in more than
one subledger. This additional string indicates:
◦ which subledger owns the source,

◦ whether it's a system source(S) or application source(A), and
◦ what's its type, S for source, F for user defined formula.
If the source is a GL account source, then:
• <SOURCE_CODE>. All means the entire GL account combination is used.
• <SOURCE_CODE>.<SEGMENT_QUALIFIER> means one of the segments from the GL account combination is
used.
Manage User-Defined Formulas

In this procedure, you create a user-defined formula for an existing Payables description rule.

Navigate to the Manage Formulas page.
147
◦ Functional Area: Any subledger (for example, Payables, Receivables, Projects, Fixed Assets, Collections,
and so on)
◦ Task: Manage User-Defined Formulas
Create a formula on the Manage Formulas page.

2. Enter Name. The Short Name is created but can be updated.
3. Enter Data Type.
5. Click Save.
• This formula is used in a description rule for the Invoices event class.
In the Expression region:
a. Click Insert Function.
i. Enter Type = Conditional.
ii. Click Search.
iii. Select IF THEN ELSE
iv. Click OK.
b. Place the cursor after the IF.
c. Click Source.
i. Select Subledger Application.
ii. Select Name = Intercompany.
iii. Click Search.
iv. Select Intercompany Invoice Indicator.
v. Click OK.
d. Click More.
e. Select Equal To (=).
f. On the IF line, after the = enter 'Y' including the single quotes.
g. On the THEN line, click Insert Function.
i. Select Type = Alphanumeric.
ii. Click Search.
iii. Select Concatenate.
iv. Click OK.
h. Double-click String1, and replace with 'Intercompany Invoice'.
i. Double-click String2.
i. Double-click Source.
ii. Select Subledger Application = Payables.
iii. Enter Name = Invoice Number.
iv. Click Search.
v. Select Invoice Number.
vi. Click OK.
j. Copy and pasts the THEN clause Concatenate('Intercompany Invoice',"Invoice Number") to the ELSE
clause.
148
k. Remove 'Intercompany Indicator'.

l. Validate the formula.
i. Click Validate.
ii. Click OK on the Information message.
iii. Click Save.
m. Activate the formula.
i. Click Actions > Change Status > Activate.
n. Click Save and Close.
Add the User-Defined Formula to a Description Rule

Add the user-defined formula to an existing description rule.

◦ Functional Area: Any subledger (for example, Payables, Receivables, Projects, Fixed Assets, Collections,
and so on)
◦ Task: Manage Description Rules
2. Click Edit on the Invoice Type description rule.
a. Remove the existing source.
b. Click Source button.
c. Search by Type
d. Select Invoice Header with Type.
e. Click Save and Close.
Note: When defining a user-defined formula or a condition to other setup rules, after selecting a source, the source
name is suffixed by an additional string such as (Payable, S, S) if the same source name is used in more than one
subledger. This additional string indicates:
• which subledger owns the source,
• whether it's a system source(S) or application source(A), and
• what's its type, S for source, F for user defined formula.
If the source is a GL account source, then
• <SOURCE_CODE>.All means the entire GL account combination is used.
• <SOURCE_CODE>.<SEGMENT_QUALIFIER> means one of the segments from the GL account combination is
used.
Note: A user-defined formula isn't supported in the transaction account builder.
149
Related Topics
• Manage User-Defined Formulas
Manage User-Defined Formulas

You can use Subledger Accounting user-defined formulas to derive a value that's used in a journal entry, such as a
journal amount or description.
Formula Usage and Assignments

A user-defined formula can be used to:
• Calculate a numeric value
• Derive an alphanumeric value

• Return a date value
It can also be used in any of the following accounting rule components:
• Journal line rule
• Account rule
• Mapping set
• Description rule
• Supporting reference
Formula Definition
Define user-defined formulas using sources for the selected event class. Predefined functions and conditions can also
be used to derive the resulting value.
• Enter source in double quotes (").
• Enter constant values in single quotes (').
• Enter date values in the format YYYY-MON-DD.
Example 1
A user-defined formula has been defined to use in the description rule for the journal entry rule set for the Invoice event
class.
Steps:
1. Define a formula:
◦ IF "Project Number" IS NOT NULL AND "Invoice Date" >= '2015-Jan-01'
THEN Concatenate("Project Number", "Invoice Number")
ELSE Concatenate("Supplier Name", "Invoice Number")
150
2. Use the formula in a description rule.

3. Assign the description rule to a journal entry rule set.
Results:
Accounting is created for two project invoices and one nonproject invoice.
This table contains the invoices created by example 1.
Invoice Invoice Details Journal Entry Description
1 Invoice number = MA0024 ABC Inc.MA0024
Invoice date = 2014-Dec-11
Supplier name = ABC Inc.
Project number = 12345
2 Invoice number = MA0045 12345MA0045
Invoice date = 2015-Jan-30
Project number = 12345
3 Invoice number = MA0012 ABC Inc.MA0012
Invoice date = 2015-Jan-15
Example 2
A journal entry is recorded for the actual 401k funding every quarter. The monthly accrued amount entry is created for
each month of the quarter using the following user-defined formula.
Note that the accrual entry is to be reversed at the beginning of the next month by the accrual reversal feature.
Steps:
1. Define a formula:
◦ "Fund Balance" / 3 * "Month Number in the Quarter"

2. Assign the formula to the Entered Amount accounting attribute for the event class.
3. Use the formula as the Entered Amount for the journal line rule.
4. Assign the journal line rule to the journal entry rule set.
Fund balance = 1,200 USD
This table contains the monthly entries created using example 2.
151
Month Results
1 Accrual amount for the first month in the quarter: 1200 / 3 * 1 = 400
2 Accrual amount for the second month in the quarter: 1200 / 3 * 2 = 800
3 Accrual amount for the third month in the quarter: 1200 /3 * 3 = 1200
Predefined Formula Functions

The following predefined functions are available to be used in user-defined formulas.
This table contains a listing of predefined formula functions.
Type Function Description Example
Alphanumeric Concatenate Concatenate two strings into one Concatenate('This is ', 'a test.')
single string. returns 'This is a test'.
Alphanumeric Substring Extract part of a string. Substring('How are you?', 3,5)

returns 'w are'.
Alphanumeric ToText Convert a numeric value to text. ToText("Tax Rate") returns the tax
rate in text format.
Note:
A formula with ToText can't be
used in a rule condition.
Date FirstDayOfYear Return the first day of the calendar FirstDayOfYear('2013-Jul-11')

year based on the parameter. returns '01-Jan-2013' in date
format.
Date LastDayOfYear Return the last day of the calendar LastDayOfYear('2013-Jul-11')

year based on the parameter. returns '31-Dec-2013' in date
format.
Date FirstDayOfMonth Return the first day of the month FirstDayOfMonth('2013-Jul-11')

based on the parameter. returns '01-Jul-2013' in date format.
Date LastDayOfMonth Return the last day of the month LastDayOfMonth('2013-Jul-11')

based on the parameter. returns '31-Jul-2013' in date format.
Date AddMonth Return the date of specified AddMonth('2013-Jul-11',2) returns

number of months after the date in 11-Sep-2013 in date format.
parameter.
152
Type Function Description Example
Numeric YearNum Return the year of a date source in YearNum('2012-Feb-28') returns

4-digit format. the number 2012.
Numeric MonthNum Return the month of a date source MonthNum('2012-Feb-28') returns

in numeric format. the number 2.
Numeric DayNum Return the day of date source in DayNum('2012-Feb-28') returns the
numeric format. number 28.
Numeric Round Round a number to a specific Round(183.1123, 2) returns 183.11

decimal place.
Round(183.1123, -1) returns 180
Numeric RoundUp Round up a number to integer. RoundUp(0.01) returns 1.
RoundUp(1.50) returns 2.
Numeric RoundDown Round down a number to integer. RoundDown(0.01) returns 0.
RoundDown(1.50) returns 1.
Numeric Power Return the power of a number. Power(3,2) returns 9.
Numeric NumberOfGLPeriod Return the number of If accounting calendar

nonadjustment accounting periods is defined as Monthly,
between two dates. NumberOfGLPeriod('2013-Jul-11',
'2013-Oct-10') returns 4.
• If start date isn't the first day
of an accounting period it's
counted as one period.
• If end date isn't the last day
of an accounting period, it's
counted as one period.
Numeric ToInteger Convert a text value to integer. ToInteger("Cost Center Segment")

returns the cost center segment
value as a numeric value.
Related Topics
• Overview of Subledger Journal Entry
• How You Create a Manual Subledger Journal Entry
• Accrual Reversals
153
Manage Supporting References

Supporting References
Supporting references are used to store additional source information about a subledger journal entry at the line level.
Supporting references are a powerful tool to capture transaction attributes in journal lines. You can use these tags to
report on entries, reconcile entries back to source systems, or even maintain balances at the attribute level.
• Define supporting references once and reuse by assigning sources of different event classes or source systems
to the same supporting reference.
• You can link one source per event class to each supporting reference. The subledger or source system uses
the supporting reference name to store the source values. This standardizes supporting reference information,
even if it comes from disparate source systems.
Supporting references can be defined using either of these options (located on tabs):
• With Balances:
◦ Select the With Balances tab in the supporting reference definition to have balances maintained when the
supporting reference is associated.
◦ For balance sheet accounts, supporting reference balances are carried forward to the first period of the
accounting calendar's year.
◦ For Profit and Loss accounts, supporting reference balances are set to zero in the first period of the
accounting calendar's year.
◦ A limit of thirty supporting references with balances can be defined. You can consider adding more
source assignments to predefined supporting references, rather than creating a new one.
Supporting references with balances establish subledger balances for a particular source and account for a
particular combination of supporting references plus the account combination.
For example:
◦ If a journal line contains a supporting reference that includes two sources, Customer Type and Customer
Name.
◦ Balances are created for the account combination, plus customer name and customer type.
• Without Balances:
◦ You can assign up to 30 SR without balance to each journal line.
◦ Consider using a journal entry header or line description if:
- No balance is maintained for a supporting reference.
- No supporting reference details are needed for reports.
Note: Caution: Using supporting references instead of descriptions may impact accounting engine
performance.
Examples of how you may want to use supporting reference balances are to:
• Facilitate reconciliation back to the subledgers and source systems by tagging journal entries with the
transaction and reference attributes.
154
• Create balances by dimensions not captured in the chart of accounts.

• Reporting using dimensions not captured in the chart of accounts.
• Enrich Oracle Fusion Business Intelligence Applications reporting on subledger journals.
• Profit and loss balances by dimensions not captured in the chart of accounts.
Define supporting references to hold additional supporting information for detailed account balance maintenance or
reconciliation and reporting requirements.
Related Topics
• Considerations for Supporting Reference Assignments
Create Supporting References

Here's how you can create supporting references:
1. Navigate to the Manage Supporting References page.
2. Click the With Balances tab.
4. Enter Name.
6. In the Sources region:
a. Search Subledger Application.
b. Source and select Source.
c. Click OK.
7. Repeat these steps to create another supporting reference.
Related Topics
Assign Supporting References

Supporting References can be assigned to journal line rules. Here's how you can assign supporting references:
1. On the Manage Supporting References page, navigate to the Assignments tab.
2. Click on the Add Assignments button.
3. In the Select Scope pop-up window, select the Subledger Application and Event Class to limit the scope for
which supporting references are to be assigned.
4. In the new pop-up window, select the associated supporting references and the configured journal line rules.
5. Click save to assign the supporting references to the selected journal line rules.
Note: Journal Line Rules can span across different Journal Entry Rule sets.
View and Delete Supporting Reference Assignments

You can use the Assignments tab to view and delete the existing supporting reference assignments also.
View Supporting Reference Assignments
• Select supporting references from the search criteria to view assignments across all subledger applications.
155
• Alternatively, select subledger application and event class to view the assignments for a particular subledger
application.
Delete Supporting Reference Assignments

To delete an existing supporting reference assignment, select the required supporting reference and click on the Delete
Assignments button.
Considerations for Supporting Reference Assignments

You may want to analyze account balances and financial results by different transaction attributes. However, transaction
information such as salesperson, customer, or supplier are typically not stored in the general ledger because of the
volume of general ledger balances it would create. Therefore, you're not able to analyze general ledger data categorized
by transaction attributes.
You can perform this type of reporting and analysis using supporting reference information from subledger
transactions. This feature enables you to create balances based upon transaction attributes not typically stored as
segments in the general ledger chart of accounts.
For example, you can report on receivables balances by salesperson, customer, credit risk category, item, or any other
combination of transaction attributes.
Supporting references can be used to:
• Provide additional information about a subledger journal entry line.

• Establish a subledger balance for a particular supporting reference value.
• Assist with reconciliation of account balances.
• Provide additional detail information for financial managerial analysis.
You can assign supporting references at the subledger journal entry line level.
Tips for Assigning Supporting References
• You can add or delete supporting reference assignments for user-defined journal entry rule set only.
• The Manage Supporting References page can only display up to 1000 assignments. Provide additional search
criteria to narrow down your search results, especially when you need to add or delete assignments.
Assigning Supporting References at the Subledger Journal Entry Line

Assigning supporting references to subledger journal entry lines enables you to maintain detailed balances, by
supporting reference value, for general ledger accounts.
Related Topics
• Assign Supporting References
156
Migrate the Configuration

Considerations for Migrating Accounting Rules
Use the export and import functionality in the Setup and Maintenance work area to perform migration of setup data.
When migrating accounting rules, you must migrate task lists in entirety and fulfill some requirements.
Full Task List Migration

This table contains the task lists used to migrate in full, depending on the offering.
Offering Task List
Oracle Fusion Accounting Hub Define Accounting Transformation Configuration
Oracle Fusion Financials Define Subledger Accounting Rules
Define Transaction Account Rules
Support isn't provided for a partial task list migration.
You may migrate setup data for specific applications only. Note that supporting references, accounting options, and
accounting class usages are migrated for all applications, regardless of the applications specified.
Migration Requirements
Prior to migration, journal entry rule sets and accounting methods must be successfully activated. Invalid journal entry
rule sets or accounting methods cause import failure.
Ensure that your setup data migration includes all dependent business objects from other required setup modules,
such as Define Ledgers. The import sequencing of these dependent business objects must be prior to accounting rules
business objects.
Secure Accounting Transformations

Security for Accounting Transformations in Accounting Hub
Accounting transformations require both function and data security privileges.
157
Oracle Accounting Hub security for accounting transformations includes:

• Setup task security
◦ Security to register source systems into Accounting Hub.
◦ Security to configure accounting rules to define accounting treatments for transactions.
• Transactional task security
◦ Security to create subledger journal entries (manual subledger journal entries or those generated by the
Create Accounting process).
◦ Security to review and generate reports of subledger journal entry headers and lines.
Security to Perform Setup Tasks
Use the Define Accounting Transformation Configuration task in the Setup and Maintenance work area to integrate your
external source system with the Accounting Hub.
To register your external source system and configure accounting rules, the setup user must be provisioned with a role
that includes the following duty roles:
• Application Implementation Consultant

• Accounting Hub Integration
• In the security reference implementation, the Financial Application Administrator job role hierarchy includes
the Accounting Hub Administration Duty role. This role provides the access to integrate your external source
systems with accounting transformations.
Security to Perform Transactional Tasks

To import transaction data for accounting and posting in general ledger, the user must be provisioned with a job role
that is associated with the Accounting Hub Integration duty role.
• The Import Subledger Accounting Transactions privilege is assigned to the Accounting Hub Integration duty
role. This role enables the user to submit the Import Subledger Accounting Transactions process. This process
also creates accounting entries and posts them in the general ledger.
To create and view subledger journal entries as an independent task, you must have the access necessary to perform
the tasks. These tasks can be opened from the Oracle General Ledger, Journals work area. You must have access to the
work area, as well as all of the ledgers (primary, secondary and reporting currency) in which the journal entry is posted.
The following are defined in the security reference implementation:
• The General Accounting Manager job role hierarchy includes duty roles that provide the entitlement to manage
general accounting functions. This entitlement provides access to the general ledger, Journals work area.
The following duty role must be assigned directly to the General Accounting Manager job role to provide access to
create and view subledger journal entries:
• Accounting Hub Integration Duty
Alternatively, you can assign the Subledger Accounting Duty and Subledger Accounting Reporting Duty roles to any of
the following general ledger job roles:
• Chief Financial Officer
158
• Controller
• Financial Analyst
• General Accountant
For more information about available setup job roles, duty roles, and privileges, see the Oracle Financials Cloud Security
Reference guide on the Oracle Help Center.
Related Topics
• Data Security
Create and Process Subledger Journal Entries

How Subledger Journal Entries are Created and Processed in
Accounting Hub
The Create Accounting process uses the uploaded transaction data and accounting rules to create subledger journal
entries. For example, a subledger journal entry rule set specifies that the customer name should appear in the
description of a subledger journal entry line. The customer name value is obtained from the customer name source data
provided by the uploaded transaction data.
This figure illustrates the Create Accounting process.
159
How Subledger Journal Entries Are Created and Processed in Accounting Hub
1. The source system transactions are uploaded into Universal Content Management.
2. The transactions are then imported into Accounting Hub using the Import Accounting Transactions process.
3. The Create Accounting process is automatically submitted.
4. Subledger journal entry rule set definitions and sources from transaction data are applied to create subledger
journal entries.
5. The subledger journal entries are summarized and imported to Oracle General Ledger.
FAQs for Accounting Transformation

What's the character limit for supporting reference values?
Supporting reference values can be up to 30 characters long.
160
Why can't I assign some account rules to a rule set?

You can only assign account rules to rule sets that use sources from the same subledger application. Review the account
rule, its condition, and any mapping sets or user-defined formula it references, and verify that no sources from other
applications are used.
Can I delete a source that's no longer used in accounting rules?

No, you can't delete such a source. However, you can stop populating the corresponding field in the data template.
How can I use a mapping set across subledger applications?

You can't use a mapping set across subledger applications. Instead, use the setup data export and import to replicate
mapping set data across subledger applications.
Related Topics
Can I restrict access by subledger application?

You can use data security policies to address such requirements.
Related Topics
161
162
Implementing Accounting Hub Subledger Accounting
7 Subledger Accounting
Overview of Manage Subledger Accounting

In the Manage Subledger Accounting activity, you can generate journal entries for source system transactions, create
adjustment entries, and review accounting results.
You can:
• Create accounting for a batch of transactions by submitting an offline process.
• Create manual adjustment entries.
• Review generated journal entries and projected balances on views and reports.
Upload Transaction Data

Upload Transaction Data for Accounting Hub
You can import transaction data from a source system that has accounting entries created in Accounting Hub. After
completing the source system's registration and the accounting rules' configuration, you can upload the transaction
using a spreadsheet.
This figure illustrates the upload transaction data processes. You can upload the transaction data manually or through
an automated process.
Manually Upload Transaction Data

To upload the transaction data manually, follow these sequential steps:
1. Download the transaction data template using the Manage Subledger Application task.
163
2. Save the file on a local drive.

3. Extract the three files contained in the downloaded template.
a. Metadata.txt
- The metadata file contains key information about the source system.
b. XlaTrxH.csv
- This file contains the header-level columns for the transaction data that can be populated.
- The column names match the short name of the sources that were included in the Transaction
Information worksheet during the registration of your source system.
- One column that's available in the header and line file is the Transaction Number. The Transaction
Number links the header and its corresponding lines information.
c. XlaTrxL.csv
- This file contains the line-level columns for the transaction data that can be populated.
- The column names match the short name of the sources that were included in the Line
Information worksheet during the registration of your source system.
4. Populate the header and line CSV files.
Note: Both XlaTrxH.csv and XlaTrxL.csv files may contain column names that aren't used by the subledger,
such as Character9, Date2, Long Character1 and so on. You can leave the unused column blank when
populating transaction data in these files.
5. Select and compress the three files.

◦ The file names must remain the same as the downloaded files.
◦ As a best practice, Oracle recommends that the .zip file has a unique name that includes a subledger
source and date stamp.
◦ The .zip file must begin with XlaTransaction.
◦
We recommend you suffix the file with the subledger source name and date to identify the file uniquely.
For example, XlaTransactionRetailLoan050417.zip.
6. Upload the .zip file into Universal Content Management.
CAUTION: You must assign the Accounting Hub Integration Duty Role to a user-defined job role to perform
this step. Also, you must ensure that the user is also assigned the General Accounting Manager job role.
Otherwise, you must add the Upload Data for Accounting Hub Import role to the job role. Alternatively, you
can assign the Subledger Accounting Duty and Subledger Accounting Reporting Duty roles to any of the
following general ledger job roles:
◦ Chief Financial Officer
◦ Controller
◦ Financial Analyst
◦ General Accountant
◦ Navigate: Navigator > Tools > File Import and Export.

◦ Click Create.
164
◦ Browse for the compressed file.

◦ Select account: fin/fusion/AccountingHub/Import.
◦ Save and Close.
◦ View the file upload results in the Search Results region.
7. Submit the Import Accounting Transactions process.
◦ Navigate: Navigator > Scheduled Processes.

◦ This process imports accounting transactions from Universal Content Management, creates accounting
entries and posts the journal entries to the general ledger.
Optionally, you can choose to upload the transaction data to the interface tables, import transaction data
from the interface tables, and create accounting as separate processes. To do this, you enable the Flexible
Configuration of Accounting Hub Cloud Service feature. Refer to the Advanced Features for Importing
Transaction Data to Accounting Hub topic for details.
If there are invalid entries, query journal entries with Invalid status from the Review Journal Entries task, view the
transaction, and correct the errors directly. Refer to the Correct Accounting Hub Transaction Data for Invalid Entries
topic for details.
Note: Error correction is dependent on the dependent on the Update Subledger Transactions privilege. You can
remove or add the privilege per your company's policy.
You can also run the Accounting Hub Maintenance process with the Purge invalid transactions mode to delete invalid
transaction data along with the resulting invalid subledger journal entries, modify the data in CSV files and import them
again. Refer to Accounting Hub Maintenance for more details.
By default, uploaded transaction data are kept in the Accounting Hub Cloud for 90 days. Transactions that are
used to create multiperiod accounting entries are kept until the end date of the multiperiod duration. You can
change the transaction retention period's duration to any value between 30 days and 458 days. To change the
accounting retention period, navigate to the Manage Subledger Accounting Lookups page, and specify a value for the
ORA_XLA_AHC_RETENTION_DAYS lookup type.
Automated Processing Options

Automated processing options are available to bring the transaction data files from the registered source systems
into Accounting Hub. This includes data from other external sources, such as other company-specific 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 are imported into Accounting Hub using the Universal Content Management
with one of three available integration options:
◦ Oracle WebCenter Content Document Transfer Utility

◦ Oracle UCM Web Services
◦ ERP Integration Service, upload to UCM
• Import the transaction data using the Import Accounting Transactions process.
• The Create Accounting process is automatically called, resulting in the creation of journal entries.
165
For more information about automated processing options, see the following resources in the Oracle Help Center:
• Oracle Fusion Middleware Developer's Guide for Content Server: Using Oracle UCM Web Services
• Oracle Integration Cloud Service
• Oracle Accounting Hub Best Practice guide
Upload Encrypted Data

You can use data encryption to secure data files sent to the Accounting Hub Cloud Service. In this case, the Import
Accounting Transactions process decrypts the data files using the Cloud private key and then starts the load and import
process.
Here are the steps to upload encrypted transaction data:
1. On the Certificates tab of Security Console, generate a PGP public and private key pair. Then, export the Cloud
public key.
2. In an external encryption utility, you generate the customer side key pair by using the Cloud public key.
3. Export the customer public key.
4. On the Certificates tab of Security Console, import the customer public key.
5. In an external encryption utility, encrypt the transaction data ZIP file using the Cloud public key.
6. When uploading the encrypted .zip file into UCM, provide encryption details in the Comments field in the
following format:
FileEncryption=PGPUNSIGNED;FA_ALIAS=CLOUD_KEY;CUSTOMER_ALIAS=YOUR_KEY
Where, CLOUD_KEY is the Cloud public key alias, YOUR_KEY is the customer public key alias.
Note: You can provide the comments using the AppendFileComment operation of the ERP Integration
Service or through WebCenter Content Server.
Testing
Once the setup is complete, testing should be comprehensive to ensure that all accounting is correctly generated.
At a minimum, this should include testing for the following:
• Sources are available for creating subledger journal entries.
◦ Review available sources from the Manage Sources user interface.

◦ Confirm that when you configure accounting rules, sources are available for use.
• Subledger journal entries accurately reflect the accounting rules.
We also suggest that you test the following:
• Subledger journal entries contain the appropriate dates, amounts, descriptions, and accounts.
• Conditions used to determine journal line rules, account rules, or descriptions are valid.
• Subledger journal entries are successfully transferred and posted to general ledger and reflected in subledger
accounting balances.
166
Note: To perform detailed diagnostics on the underlying transaction sources used to accounting journal entries,
follow the Subledger Accounting diagnostic framework business process flow. See the Diagnose Subledger
Accounting Event Data: Explained topic for details.
Gain Insight Using Journal Entries

Once you have the accounted subledger journal entries in Accounting Hub, you can use the posted journal entries to
gain insightful information.
• To streamline period close activities, perform a reconciliation of subledger journal entries with the posted
journal entries in the GL or the source system, on a regular basis.
◦ Review the supporting references report that tracks specific accounts in the subledger. Reconcile with the
same account in the general ledger.
◦ The Supporting References report is a user-defined analysis using OTBI subject areas; Subledger
Accounting - Journals Real Time, and Subledger Accounting - Supporting References Real Time.
• Review the accounting reports to gain insight on your current business performance with the configured
analytical metrics, such as supporting references.
• Perform queries on specific accounts in the general ledger and drill down to its corresponding subledger
journal entries and transaction data.
Related Topics
• Use the Supporting References Report
• Import and Export PGP Certificates
Advanced Features for Importing Transaction Data to Accounting

Hub
You have the flexibility to upload transaction from Universal Content Manager to the interface table, import accounting
transactions from the interface table, and create accounting as three separate processes. For example, you can choose
to split a large batch of accounting transactions into multiple data files and import them to interface table separately.
After all the files are uploaded, you can submit the Import Accounting Transactions from Interface process to import
all transactions into Accounting Hub and create accounting. Optionally, you can create accounting using the Create
Accounting process at a later stage.
To have such a flexibility for importing transaction data, you have to do these tasks:
• Enable the Flexible Configuration of Accounting Hub Cloud Service feature.

• Download and use the updated transaction template.
• Configure parameters for the Import Accounting Transactions process.
• Configure parameters for the Import Accounting Transactions from Interface process.
Enable the Flexible Configuration of Accounting Hub Cloud Service Feature

The Flexible Configuration of Accounting Hub Cloud Service feature is enabled by default unless you disable it manually.
We highly recommend keeping this feature enabled because many other dependent features may not be supported
167
if you disable it. Note that you can't opt-out from this advanced feature if any of your subledgers already has Support
Transaction Reversal enabled.
You must download a new transaction template and populate the template with the source value in corresponding
columns. The new template displays the unused columns in XlaTrxH.csv and XlaTrxL.csv files as CHAR1,
CHAR2, CHAR3...., NUMBER1, NUMBER2, NUMBER3...., DATE1, DATE2, DATE3...., LONG_CHAR1, LONG_CHAR2,
LONG_CHAR3....and so on. You can't remove these columns from the template, but you can keep these columns blank if
unused.
Configure Parameters for the Import Accounting Transactions Process

The following table describes the parameters you can configure for the Import Accounting Transaction process:
Parameter Description
Import from Interface Select whether to upload transaction data to the interface table and import transaction from interface
to Accounting Hub in a single step.
Choose Yes if the transaction data for an import set is in a single data file.
Choose No if the transaction data for an import set is split into multiple data files. In this case, you
can wait until all the transaction data is imported to the interface table and then submit the Import
Accounting Transaction from Interface to import the transactions to Accounting Hub.
Import Set The group of transactions that are processes together. If this information isn't entered, each data file is
considered a single import set.
Create Accounting Select whether to submit create accounting process after transactions are imported from the interface
table.
Report Style Select the format in which the report output is generated.
Transfer to General Ledger Select whether to transfer the subledger journal entries to General Ledger.
Post in General Ledger Select whether to post subledger journal entries in General Ledger.
Update Subledger Balances Select whether to submit update subledger account balances process to update supporting reference
balance after create accounting process is complete.
Configure Parameters for the Import Accounting Transactions from Interface Process
You use the Import Accounting Transaction from Interface process to import transaction data from interface tables
into Accounting Hub. For example, you may choose to load transactions to interface tables without triggering the
import in the same run. Later, you can use the Import Accounting Transactions from Interface process to import these
transactions. This is an optional process, and you only need to run this if the Import Accounting Transactions process is
submitted with Import from Interface = N.
The following table describes the parameters you can configure for the Import Accounting Transaction from Interface
process:
168
Parameter Description
Subledger Application Select the subledger application for which you want to import accounting transactions from interface
table and create accounting.
Import Set The group of transactions that are processes together. If this information isn't entered, each data file is
considered a single import set.
Create Accounting Select whether to submit create accounting process after transactions are imported from the interface
table.
Report Style Select the format in which the report output is generated.
Transfer to General Ledger Select whether to transfer the subledger journal entries to General Ledger.
Post in General Ledger Select whether to post subledger journal entries in General Ledger.
Update Subledger Balances Select whether to submit update subledger account balances process to update supporting reference
balance after create accounting process is complete.
Validations for the Import Accounting Transactions Process

To ensure that the transaction data is uploaded correctly and without any errors, you need to review it before uploading.
You should check for the following elements while reviewing the transaction data.
• The .zip file
◦ The name of the .zip file must begin with XlaTransaction.

◦ There's exactly one metadata file in the .zip file.
◦ The header and line transaction files exist in the .zip file.
• Metadata
◦ The metadata file contains a valid application short name.
• Header transaction file
◦ The header file contains the source header row.

◦ All the sources or the column names in the header row are valid.
◦ The source header row of the header transaction file contains Transaction_number, Transaction_type,
and Ledger_name.
◦ All headers have at least one line for non-reversal records. Line record is optional for reversal header
record.
169
• Line transaction file
◦ The line transaction file contains the source header row.

◦ The source header row of the line transaction file contains Transaction_number.
◦ All lines have at least one header.
• Ledger setup
◦ The ledger is setup in subledger accounting.

◦ The ledger is allowed to process events. Do not use reporting or secondary ledgers with the valuation
method disabled.
◦ The ledger and even type details are valid.
• Data type
◦ The date and number columns are in the correct format.

◦ The date format must be YYYY-MM-DD.
Accounting Hub Maintenance

Overview of Accounting Hub Maintenance
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
Note: You must contact the help desk before you use the Restructure indexes to optimize performance mode.
Delete Final Accounted Transactions

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.
170
Note: You should carefully evaluate the reasons for extending the retention period because it can adversely impact
application performance. If you require any key transaction information for analysis and reconciliation, you should use
them as attributes of the resulting accounting entries. So, you need not retain the processed transaction data for a
longer duration.
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.
Note: You can edit the default schedule of the Accounting Hub Maintenance process to control when to run the
process. To do so, select an instance of the Accounting Hub Maintenance process on the Scheduled Processes page.
Then, click Edit Schedule and modify the schedule.
Delete Unaccounted Transactions

You can run the Accounting Hub Maintenance process in the Purge unaccounted transactions mode to delete
unaccounted transactions that were incorrectly imported.
Delete Invalid Transactions

You run the Accounting Hub Maintenance process in the Purge invalid transactions mode to delete invalid transaction
data along with the resulting invalid subledger journal entries.
Note: Optionally, you can enable the Automatically delete invalid transactions option on the Manage Subledger
Application page. This lets the Create Accounting for Data Set process automatically run the Accounting Hub
Maintenance process in the Purge invalid transactions mode and delete invalid transaction data at the end of the run.
Run the Accounting Hub Maintenance Process to Delete

Transactions
Here are the steps to run the Accounting Hub Maintenance process and delete the invalid, unaccounted, or final
transactions:
1. On the Scheduled Processes Overview page, click Schedule New Process.
2. In the Schedule New Process dialog box, search for Accounting Hub Maintenance, and then click OK.
3. In the Process Details dialog box, select the mode as Purge invalid transactions, Purge unaccounted
transactions, or Purge final accounted transactions.
Note: You must contact the help desk before you use the Restructure indexes to optimize performance
mode.
4. Next, select the subledger application and ledger.

5. Click Submit.
CAUTION: When you submit the Accounting Hub Maintenance process in the Purge 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.
171
What is Deleted
Here's the information that's deleted for eligible transactions in the different modes of the Accounting Hub
Maintenance process:
Information Purge final accounted Purge unaccounted transactions Purge invalid transactions
transactions
Transaction records in transaction Deleted Deleted Deleted

objects
Transaction entity records Not deleted Deleted Deleted
Accounting events including Not deleted Deleted Deleted

reversal events
Incomplete accrual reversal journal Not deleted N/A Deleted only if the associated
entries accrual entries are also deleted
Invalid journal entries in the N/A N/A Deleted

primary ledger as well as
any reporting currencies and
secondary ledgers
Correcting the Transactions

When you run the Accounting Hub Maintenance process in the Purge invalid transactions or Purge unaccounted
transactions mode, the application generates these files:
• An output file listing the deleted transactions.

• Two CSV files with transaction header and line details for the deleted transactions.
The layout of the CSV files follows the updated transaction templates. You can review the CSV files, change the source
value as needed, and import the accounting transactions again.
Create Accounting
Subledger Accounting Options for Accounting Hub
Subledger accounting options define how certain accounting processing should be done for transactions of a given
subledger at a ledger level. These options are set up for the primary and secondary ledgers only.
172
Manage Subledger Accounting Options

This task is accessed from the Setup and Maintenance work area. The page is displayed in the context of a primary or
secondary ledger. All registered subledger applications are displayed. If you created additional accounting event classes
after initial ledger setup, run the Update Subledger Accounting Options process to incorporate these event classes.
The Manage Subledger Accounting Options task provides the ability to edit:
• Accounting Options
• System Options
Edit Accounting Options

This page displays the subledger accounting options for the ledger. You can review and update the options. The view for
this page depends on the subledger application type and the ledger type (primary or secondary).
The views are as follows:
• The Defaults and Ledger options view displays the accounting program defaults and the event class options for
the following:
◦ A primary ledger for a subledger application.

◦ A secondary ledger for a subledger application.
• The Ledger options view displays the event class options for a subledger application, and secondary ledger.
General Options
• Subledger Accounting Enabled
This option is visible only for secondary ledgers in the ledger options view. Enable or disable the subledger
application for the ledger. No entries are generated by subledger accounting for an application if subledger
accounting is disabled for the secondary ledger.
• General Ledger Journal Entry Summarization
◦ This option determines whether subledger journal entries are summarized or grouped when they're
transferred to General Ledger.
This table contains the General Ledger Journal Entry Summarization options and a description of those
options.
Option Description
Summarize by general ledger period Default option.
Indicates that all subledger entry lines are summarized into a single general ledger entry if they
have the same:
◦ Accounting period
◦ General ledger journal category
◦ Account
173
Option Description
◦ Entered currency
◦ Side
◦ Balance type
Disabled if the ledger uses daily balancing.
The general ledger effective date defaults to the last date of the accounting period.
Summarize by general ledger date Indicates that all subledger entry lines are summarized into a general ledger entry if they have
the same:
◦ Accounting date
◦ General ledger journal category
◦ Account
◦ Entered currency
◦ Side
◦ Balance type
The general ledger effective date is equal to the subledger accounting date.
174
Option Description
• Reversal Method
Use the Reversal Method option to determine how the reversal subledger journal entries are generated in
subledger accounting. The options are:
◦ Switch debit and credit (default): reverses a debit for a credit and a credit for a debit.
◦ Change Sign: The reversal entry keeps the same side as the original entry, but the sign is changed.
• Enable Posting from Subledger
Use the Enable Posting from Subledger option to enable or disable posting of subledger journals to GL.
This option is selected by default and allows subledger users to:
◦ Create subledger adjustment journals from UI or spreadsheet and post them to GL.
◦ Create subledger journals from the import accounting transactions process and post them to GL.
◦ Create subledger journals from the create accounting process and post them to GL.
If you disable this option, subledger users can:
◦ Create subledger adjustment journals from UI or spreadsheet and transfer them to GL but not post to GL.
◦ Create subledger journals from the import accounting transactions process and transfer them to GL but
not post to GL.
◦ Create subledger journals from the create accounting process and transfer them to GL but not post to GL.
Note: Users must have the Post to GL privilege to effectively use the Enable Posting from Subledger option.
If you already have two segregated roles for subledger users and GL users, the users can continue to perform
their roles.
• Rounding Rule
Use the Rounding Rule option to determine which option to use for rounding. Subledger accounting rounds to
the minimum accountable unit or ledger currency precision.
Tip: For examples described in the Rounding Rule Options table, assume that the precision is 2 and the
minimum account unit is 0.01.
This table contains the Rounding Rule options and a description of those options.
Option Description
Up Amount rounded up. For example, 5.983 (USD) is rounded to 5.99 (USD).
175
Option Description
Down Amount rounded down. For example, 5.988 (USD) is rounded to 5.98 (USD).
Nearest Amount rounded to nearest number. However, if the difference between Up and Down options
is equal, the amount is rounded up. For example, 5.985 (USD) is rounded to 5.99 (USD).
Journal Categories Options
• The table describes the event class option that can be overridden. Note that only the Journal Category event
class can be overridden.
This table contains the Journal Categories Options, and a description of those options.
Option Description
Journal Category Defined in the accounting rules for an event class. Any valid journal category defined in General
Ledger can be used.
Edit System Options

The following three regions are available:
• Create Accounting Processing Options

• Event Class Options
• Transfer to General Ledger Processing Options
Create Accounting Processing Options
• Number of Create Accounting Workers

• Processing Unit Size
This table contains the Create Accounting Processing options and a description of those options.
Column Name Description
Processing Unit Size Approximate batch size for high volume general ledger transfer flow, and is also the general
ledger import batch size. If not specified, the corresponding accounting processing unit size is
used.
◦ You can define the processing unit size to process a large number of items in one commit cycle. A
processing unit is the number of transactions processed by the Create Accounting process in one commit
cycle. Create Accounting processes the default processing unit size at the application level.
• Stop at Error Limit
176
◦ Maximum number of events allowed to fail before canceling account program.
Note: In actual cases, the Create Accounting process may continue to process transactions even after the
Stop at Error Limit is reached and may result in more errors than the error limit. This happens because
transactions are processed in batches. If the application starts processing a batch, it continues to process all
the transactions in the batch even if the Stop at Error Limit is reached.
Event Class Options
• Event Class
On the Manage Subledger Accounting Options page, you can select the subledgers for each ledger or ledger set, and
specify the Processing Unit Size for each event class.
Transfer to General Ledger Processing Options
• Number of General Ledger Transfer Workers

Importing information from subledgers is done using subledger accounting. Posting from the subledger application
transfers data to the general ledger interface and journal entry tables.
As part of your configuration, you can specify whether the Create Accounting process is to split the creation process
into multiple workers (processors). The benefit of splitting the creation process is that:
• Accounting can be generated more efficiently with more resources allocated to complete the process.
• You can have multiple processors running in parallel to create the entries in a shorter period of time.
One restriction is the capacity of the hardware that's being used by the application. The more available processors, the
more you can allocate to the Create Accounting process.
The decision for how many processors to use is made based upon expected volumes and the processing window. In
other words, how much time is allocated to creating accounting. Accounting is often done as a nightly batch process, to
facilitate application availability during work hours.
Dependencies exist between the overall completion status of the Create Accounting process and the workers. In
general, the parent doesn't update to the Completed status until all the workers successfully complete.
The process that allows transfer of subledger journal entries to general ledger uses separate processing workers that
are specialized in general ledger transfer. A lightweight general ledger transfer parent process is used to distribute the
workload to the workers. To transfer entries even faster, you can have a number of parallel processing workers used for
high volume general ledger transfer flow. If not specified, the corresponding accounting processors are used.
Related Topics
• Update Subledger Accounting Balances Process
177
How You Submit Accounting Process

The Create Accounting process is an Oracle Enterprise Scheduler process. It can be submitted as a request from the
Scheduled Processes Monitor window to create journal entries for a batch of events. It has input parameters that
determine the execution mode and the selection criteria for events.
This figure illustrates the submission of the Create Accounting process.
This table contains the parameters for the Create Accounting process as submitted in the Scheduled Processes Monitor
window.
Prompt Description
Subledger Application Source system for which the Create Accounting process is being executed.
Ledger Ledger name for which the Create Accounting process is being executed.
Process Category Selecting a process category indicates that all associated accounting event classes and their
accounting event types are selected for processing.
End Date End date puts a filter on the selection of events. Only events having an event date on or before the end
date are selected for accounting.
Default value is current system date. If the process is scheduled to execute periodically, after the initial
process, the End Date for each subsequent scheduled process is incremental.
Accounting Mode Accounting mode; Draft or Final
Default value is Final.
Process Events Adds other filter criteria for the Create Accounting process to select events:
178
Prompt Description
All: Process all events.
Errors: Process only those events that have previously been processed in error.
Invalid Accounts: Process only those events that have previously been processed in error. Replace any
invalid accounts with the suspense account.
Default value is All.
Report Style Users can select the type of details to display on the execution report. The report can be printed in
Summary, Detail, or No report.
Default value is Summary.
Transfer to General Ledger Indicates whether the Create Accounting process should submit the Transfer to GL process; Yes, No.
Default value is Yes.
Post in General Ledger Indicates if users, who have been granted the posting privilege, want to submit General Ledger posting;
Yes or No.
Journal Batch Batch name used by Transfer to GL to decide on the batch name for the batch created in Oracle Fusion
General Ledger.
When a value for the batch name isn't provided, the journal import default is used.
Free text field.
Include User Transaction Identifiers Default value is No.
Related Topics
• Guidelines for Reviewing a Subledger Journal Entry
• How You Manage Subledger Journal Adjustments
• Disable Posting Subledger Transactions to the General Ledger
179
Tips to Improve Accounting Performance

Here are some tips and recommendations to improve Create Accounting program performance:
• You must control the Create Accounting job submission. For example, only submit the Create Accounting jobs
for the same application/same ledger simultaneously if the application is in row lock mode.
• You must understand that the maximum volume for an application is equal to the number of ledger
combinations. So, for example, if an application with a ledger has 1000 mn and 1 mn volume, you should
consider 1mn as your target volume and set workers accordingly.
◦ For volume up to few thousand, you can restrict 1 worker.
◦ For volume > 50K, increase CA workers to 3 with processing unit size 1000, GL_transfer workers 2
processing unit size 10K.
You can achieve optimum performance by staggering the Create Accounting runs for various application-
ledger combinations.
• Set up Manage Subledger Accounting Options UI in Functional Setup Manager (FSM) to control multiple
accounting sub-processes per Create Accounting process request.
• You can change the Number of Create Accounting Workers from the System Options in the Manage Subledger
Accounting Options page. The number of workers default is 1. Be careful while changing this parameter. For
example, if the production environment is of M6 size and Create Accounting takes a long time as there is only
one worker set up now, it could help if you increase it up to 4 or 6.
• The Create Accounting program performance also depends on the number of Accounting Hub applications
available and transaction volume being processed at a time. For example, if transaction volume is high
(100,000 +) in one of the Create Accounting request scope, increase the workers incrementally to improve
the performance. Note that a large number ( > 10) of workers per Accounting hub application running Create
Accounting in parallel can have contention and can adverse the performance.
Best Practices
Here are some best practices to deal with Create Accounting program performance issues:
• The performance of the Create Accounting program depends on the time taken by various child jobs spawned
by the program. Therefore, follow the below steps to increase the number of workers for Create Accounting and
transfer to the GL subprogram:
a. From the Setup and Maintenance work area, navigate to the Define Accounting Transformation
Configuration task and go to Manage Subledger Accounting Options. Search for your ledger, expand
and open the Cost Management application. Edit the System options to change the Number of Create
Accounting Workers from 1 to 10 and change the Number of General Ledger Transfer Workers to 2.
b. Cancel the running Create Accounting job and resubmit a new one.
• Ensure the profile option Enable SLA debug mode is turned off.
• Ensure no Finest log levels are enabled.
• Select the Transfer to GL option as No.
180
Create Accounting Execution Report

When you submit the Create Accounting process, the Create Accounting Execution Report is submitted automatically
if the Create Accounting process completes with a success or warning status. The Create Accounting process output
contains a message with the Create Accounting Execution Report request identifier. Use this request identifier to
retrieve the execution report output.
Create Accounting Execution Report

Besides the automatic generation, you can also generate the Create Accounting Execution Report using these criteria:
• Submit the Create Accounting process.

• Use the request identifier of the wanted Create Accounting process that was run previously by the same user.
However, no other Create Accounting process should have been run with the same criteria.
Diagnose Subledger Accounting Event Data

You can use the diagnostic framework to know why the accounting was created in a particular way or why there are
errors. The diagnostic framework stores data that is used in the creation of a journal entry so you can use the data to
analyze accounting issues. It provides the transaction data that is referenced during accounting through accounting
rules and ledger setup. Most errors occur because either the source system information or the accounting rules are not
as expected.
Here are some ways in which you can use the diagnostic framework.
• In the implementation phase, you can launch the Accounting Event Diagnostic report to review the source
values available in the transaction objects.
• On a daily basis, you can use the Accounting Event Diagnostic report to troubleshoot exceptions.
Diagnostic Framework Features

The diagnostic framework features are as follows:
• SLA: Diagnostic Enabled: This option controls whether diagnostic information is gathered by the Create
Accounting process. Use with caution. Selecting this option can cause slow performance.
• Diagnostic Framework Execution: When the SLA: Diagnostic Enabled option is set to Yes, the diagnostic
framework is executed simultaneously with the Create Accounting process. The diagnostic framework data is
stored in the diagnostic tables.
• Accounting Event Diagnostic Report: To view the diagnostic framework report, users submit the Accounting
Event Diagnostic process with the appropriate report parameters.
• Purge Accounting Event Diagnostic Data: Purging is useful when accounting is successfully created so that the
volume of information in the report does not increase to a point where it becomes unusable.
Diagnostic framework data purged:
◦ When the data collected can be purged by running the process.
◦ When the administrator launches the Purge Accounting Event Diagnostic Data process.
181
Diagnostic Framework Business Process Flow

The following steps describe the diagnostic framework business process flow:
1. The administrator sets the SLA: Diagnostics Enabled option to Yes for the user or responsibility.
2. Users submit the Create Accounting process that automatically executes the diagnostic framework to populate
the diagnostic tables. The diagnostic framework gathers source values and other information from the
transaction objects.
3. Users submit the Accounting Event Diagnostic process to view the diagnostic report. Based on the information
in the diagnostic report, users may determine if additional or resubmission of information from source systems
is required. They may also determine if any updates to the accounting rules is required.
4. Users run the Create Accounting process again to generate subledger journal entries for events that had an
error.
5. The administrator submits the Purge Accounting Event Diagnostic Data process to purge the results of the
diagnostic framework.
Post Subledger Transactions to the General Ledger

Post subledger journals to the general ledger when you create accounting, or run the Post Subledger Journal Entries
process to transfer and post at a later time.
To post to General Ledger:
• Make sure that the Enable Posting from Subledger option is enabled so that you can automatically post
subledger journals to GL.
Note: If the Enable Posting from Subledger option is disabled, you can't post the subledger journal to GL
but you can transfer the subledger journal to GL.
• Alternatively, you must have the privilege to execute this task.

With the required privileges and settings, you can select the Account and Post to Ledger option to create and post
journal entries to the general ledger, during the online Create Accounting process.
• If you don't have the privilege to post, select Account in Final to create journal entries and transfer to General
Ledger.
• You can view the output of the Post Subledger Journal Entries process for the summary of the transfer process.
You can manually run the Create Accounting process to create accounting for a batch of transactions. Set the following
parameters to create journal entries and post to the general ledger.
• Accounting Mode is set to Final.

• Transfer to General Ledger is set to Yes.
• Post in General Ledger is set to Yes.
◦ If you don't have the privilege to post or posting from the Enable Posting from Subledger option is
disabled, the Post in General Ledger parameter isn't available.
Related Topics
• Disable Posting Subledger Transactions to the General Ledger
182
Subledger Journal Adjustment

How You Manage Subledger Journal Adjustments
Subledger journal adjustments enable easier audit and reconciliation because you can store transaction information
directly with journal adjustments. You can enter and complete subledger journal adjustment entries from the user
interface or upload using a spreadsheet.
You can perform the following actions on your subledger journal adjustments, depending on their status:
• Edit
• Duplicate
• Reverse
• Delete
• Complete
Editing a Subledger Journal Adjustment

When editing a subledger journal adjustment, you can perform the following tasks:
• Edit the journal header information, if the status isn't Final.

• Edit and create journal lines, including accounts.
• Enter the debit, and credit amounts.
• Enter the accounting class.
• View the impact on general ledger account balances should the adjustment be completed.
• Post the journal.
Note: If the Enable Posting from Subledger option is disabled or you don't have posting privilege, the
adjustment journal is transferred to GL but not posted.
You can also edit incomplete subledger journal adjustments.
• Examples of header information which can be updated:

◦ Ledger
◦ Accounting date
◦ Accounting period
Note: If the accounting date falls in both the non-adjusting and adjusting periods, the value of
accounting period on the Create Subledger Journal Entry page defaults to the non-adjusting period.
You can overwrite it with the adjusting period if required.
◦ Category
◦ Description
• Examples of subledger journal adjustment line information which can be updated:
183
◦ Account
◦ Accounting class
◦ Entered amount
◦ Journal adjustment lines
◦ Select supporting references and assign values to them.
• Edit default currency options to be assigned to a subledger journal adjustment.

• Edit or redefine the subledger journal adjustment description.
Duplicating Subledger Journal Adjustments

As a time saving feature, you may copy an existing adjustment.
The duplication feature is enabled for all existing subledger journal adjustments, regardless of status. It includes the
ability to copy complete information required for a subledger journal adjustment header and line.
Note: All fields can be edited when an adjustment is duplicated.
Reversing Subledger Journal Adjustments

You can reverse subledger journal adjustments in Final status. Reversal options are populated from accounting options.
• Switch debit and credit.

• Change sign.
Deleting Subledger Journal Adjustments

Oracle Fusion Subledger Accounting provides the ability to delete a subledger journal adjustment that's not in Final
status. The ability to delete subledger journal adjustments ensures that users have the flexibility to correct errors
without technical support.
Completing Subledger Journal Adjustments

You can complete subledger journal adjustments in Final and Post to General Ledger status.
Related Topics
• Projected Balances
How You Create a Manual Subledger Journal Entry

The application enables the user to create manual subledger journal entries online.
Creating a Manual Subledger Journal Entry

This includes the ability to:
• Enter the complete information required for a manual subledger journal entry.
184
• Enter subledger journal entry descriptions.

• Select a supporting reference and supply the supporting reference value to a subledger journal entry line.
• Assign a descriptive flexfield to a subledger journal entry header or subledger journal entry line.
• Populate default values for an entered currency for a created subledger journal entry line.
• Enter default conversion type, date, and rate information to establish a default currency for the journal that's
different than its associated ledger currency.
• View projected balances of entered and accounted journal line amounts.
• Complete and post subledger journal entries.
Note: The ability to post subledger journals to the General Ledger is dependent on your security profile. If
you don't have the privilege to post, creating a manual subledger journal entry with a Final completion status
includes the transfer to General Ledger.
Related Topics
• Projected Balances
• Post Subledger Transactions to the General Ledger
Guidelines for Validating a Third-Party Control Account

If third-party control accounts are enabled, and the account entered is a third-party control account, you must enter
third-party information in the journal entry.
Example
If an account is defined as a Supplier type third-party control account the subledger journal entry lines that use that
account must include supplier information.
When a valid third-party control account is assigned to a journal line, you're required to provide third-party information,
such as name and site.
Submit the Third-Party Balances Report to display subledger balances and account activity information for suppliers
and customers.
The Customer or Supplier subledger third-party balances are updated when the journal is completed to a Final status.
Subledger Journal Entry

Overview of Subledger Journal Entry
You can create subledger journal entries by using one of two methods:
• Use the Create Accounting process to process accounting events using accounting rules.
• Create manual subledger journal entries.
185
Subledger journal entries are always created in a given subledger application context. When the subledger journal entry
is complete, the appropriate sequence names and numbers are assigned. If applicable, corresponding secondary ledger
and reporting currency journal entries are also created.
Manual journal entries can be entered for primary ledgers or for secondary ledgers. Manual journals for primary ledgers
are automatically created only for associated reporting currencies, not secondary ledgers.
Related Topics
• How You Create a Manual Subledger Journal Entry
• Guidelines for Reviewing a Subledger Journal Entry
Guidelines for Reviewing a Subledger Journal Entry

Subledger journal entries can be reviewed whether they were created from processing accounting events, or manually
entered.
You can search subledger journal entries directly, or search for journal entries with a specific status, unprocessed
accounting events, or subledger journal entry lines.
Advanced search functionality, including the ability to use multiple search criteria is available.
Review Subledger Journal Entries

Perform an inquiry on unprocessed accounting events, subledger journal entries and subledger journal entry lines
based on multiple selection criteria.
• Create, edit, duplicate, reverse or delete a manual subledger journal entry

• View detailed information about the subledger journal entry
• View a subledger journal entry in the T-Accounts format
• View transactions underlying the accounting event or the subledger journal entry
• View supporting references associated with the subledger journal entry and lines
• View tagged subledger journal entries or create a tag on the subledger journal entry
• Perform subledger journal corrections by editing the account directly on a completed journal entry. Review the
original entry together with the correction for easier reconciliation.
◦ To correct the account on a subledger journal you must have the Override Subledger Journal Entry
privilege.
Note: If the Enable Posting from Subledger option is enabled, the corrected entry is transferred and
posted to GL. However if the option is disabled, the corrected entry is transferred to GL but not posted.
Related Topics
• Considerations for Supporting Reference Assignments
186
Analyze Journal Entry

Using analyze journal entry feature, you can understand how the accounting engine evaluates the different rules,
conditions, and accounting attribute assignments to derive the journal header and lines in an accounting entry.
You can view the source values and understand how a particular condition, formula got evaluated successfully between
others or why a particular rule priority was evaluated successfully. This can help you diagnose any rule setup-related
accounting errors or explain why the accounting entries were generated in a specific manner.
Enable Feature
Here are the steps to enable analyze journal entry feature:
1. From the Navigator menu, select Tools > Security Console.

2. Navigate to the Roles tab and click on the Create Role button.
3. Enter basic role information and select Role Category > Financials - Job Roles.
4. Navigate to the Function Security Policies train stop and add the function security policy > Review Accounting
Diagnostic.
5. Navigate to the Users train stop and add the user to which you want to provide access to the Analyze Journal
Entry page.
6. Navigate to Summary train stop and click on the Save and Close button.
7. From the Navigator menu, select Tools > Scheduled Processes.
8. Click on the Schedule New Process button, search and submit the process > Import User and Role Application
Security Data.
Navigate to Analyze Journal Entry Page

You can navigate to the Analyze Journal Entry page in the following ways:
• From View Accounting pop-up window
You can navigate to the Analyze Journal Entry page from the existing View Accounting pop-up window
accessible from the Subledger Transaction pages after accounting transactions in Draft or Final status. You can
select any journal line in the window and click on the Analyze Journal Entry button to view the specific journal
line analysis.
Note: The View Accounting window may display journal lines of multiple event classes or event types which
could pertain to different journal entries; however, the Analyze Journal Entry page is always displayed in the
context of a specific journal entry. So, all journal lines displayed in the View Accounting window may not
always be displayed on the Analyze Journal Entry page.
• From Review Journal Entries page
You can also navigate to the Analyze Journal Entry page from the existing Review Journal Entries page, which
is accessible from the Subledger Transaction or the General Accounting Journals Work area, after accounting
transactions in Draft or Final status. To navigate to the Analyze Journal Entry page, query any journal entry
using the search parameters and then select the record in the Search Results table. Click on the Analyze Journal
Entry button in the Journal Entry Details section to view the specific journal entry analysis.
187
• From Manage Accounting Errors page
You can also navigate to the Analyze Journal Entry page from the new Manage Accounting Errors page, which
is accessible from the General Ledger Journals Work area, after accounting transactions in Draft or Final status.
To navigate to the Analyze Journal Entry page, query accounting errors using the search parameters, select the
appropriate record in the Search Results table and click on the Analyze Journal Entry button.
Note: You can view Journal Entry Analysis for Invalid accounting entries if a journal entry was created for the
event. No details would be displayed if a journal entry creation was unsuccessful.
Subledger Journal Header Analysis

Every Subledger Journal Entry consists of a journal header and its corresponding journal lines. The Analyze Journal
Entry page is divided into two tabs - The Journal Header tab and the Journal Lines tab, which render details about
subledger accounting rules used in the subledger journal header vis-a-vis in the subledger journal lines region.
The Journal Header tab displays the following information about the journal entry :
• Overall Information about the Subledger Journal Entry is displayed in the topmost section. It displays details
of the Subledger Accounting Method, Journal Entry Rule Set, and other details for the specific Event Class and
Event Type.
• Subledger Accounting Rules section displays the Description Rule, and Accounting Attributes information in 2
different sub-tabs.
• The Description Rule tab displays the description rule details used to generate the Journal Entry Description.
• The Accounting Attributes tab displays the journal header related accounting attributes (For example:
Accounting Date) along with the source values used.
• Rule Details section is a child section of the Subledger Accounting Rules section displaying further details about
a rule.
• In a specific Description Rule, the Rule Details section displays the Priorities and Formula defined in the
description rule.
• You can view the evaluation status of the priorities and review the source values to understand why a specific
rule priority got applied successfully.
Subledger Journal Lines Analysis

The Journal Lines tab displays details about subledger accounting rules used to generate all the journal lines for a
specific journal entry. The page follows a hierarchical structure where you can select specific records in the upper
sections to view the subledger accounting rules and further details in child sections.
The Journal Lines tab displays the following information :
• The Journal Lines section is displayed as the topmost section, and it shows all the journal lines for the
subledger journal entry being analyzed.
• The Source Distribution section is a child section of the Journal Lines section. It displays all the distributions
that were merged to generate a specific journal line. A single record would be displayed with line-level details
for subledgers where distribution level information isn't captured
◦ This section has a custom implementation for Payables and Receivables (exceptions include - Bills
Receivable transactions) distributions fetching the distribution details from their respective distribution
tables.
188
◦ For other subledgers, a generic layout has been used to display the source distribution identifiers and
distribution type, and distribution amount.
• Subledger Accounting Rules section is a child section of the Source Distribution section. It displays the Journal
Line Rule, Description Rule, Account and\or Segment Rules, and Supporting Reference details in different sub-
tabs, which were used for a specific source distribution.
◦ Journal Line Rules tab displays the journal line rule details used to generate the specific journal line.
◦ Description Rules tab displays the description rule details, which were used to generate the Journal Line
Description.
◦ The Account Rules tab displays all the account and\or segment rules, generating the account
combination on the journal line.
◦ The Supporting References tab displays the supporting reference details along with the source value
used.
• Special Cases \ Exceptions:
◦ For business flow based accounting entries, since the account or description may be based on a related
accounting entry from the upstream transaction, no subledger accounting rules would be displayed.
◦ For reversal accounting entries where the subledger uses a transaction or line reversal, a message will be
displayed indicating the entry was generated due to reversal.
◦ For certain other cases (Multi-period Accounting, Account Override, Inter\Intracompany Balancing,
Entered Currency, Balancing, and so on) where the accounting entry is system generated and no
subledger accounting rules are used in the process, a message will be displayed indicating the same.
• Rule Details section is a child section of the Subledger Accounting Rules section displaying further details about
any specific rule.
◦ In the context of a specific Journal Line Rule, the Rule Details section displays the Condition, Advanced
Options, Accounting Attributes, and Formula defined in the journal line rule.
◦ In a specific Description Rule, the Rule Details section displays the Priorities and Formula defined in the
description rule.
◦ In a specific Account or Segment Rule, the Rule Details section displays the Priorities and Formula
defined in the account or segment rule.
◦ In the Supporting References tab, the Rule Details section displays the formula defined in the supporting
references.
◦ You can view the evaluation status of the priorities, review the source values to understand why a specific
rule priority or condition got applied successfully.
Projected Balances
Use the projected balances feature to view the impact on account balances for selected subledger journal entry lines.
The projected balances flow has the following business benefits:
• The creation and validation of unposted manual journal entries by providing immediate information about the
account balances for the selected journal lines.
• The validation and reconciliation of posted journal entries by providing immediate information about the
account balances for the selected journal lines.
189
Projected Balances
Subledger Accounting manual journal entry and General Ledger manual journal entry, approval, and inquiry pages
display projected or current balances including the current journal entry line amounts. Depending on whether the
journal is posted or not, the current balance (for the period of the journal) is displayed or calculated.
The projected balance region displays the projected balances for the account that includes the amounts of the selected
journal entry line. Additionally, if more than one journal line for same account of the selected journal line exists, then the
projected balance amount includes the impact from each journal line. The Period To Date, Quarter To Date, and Year To
Date balances are also available.
• For unposted journals, the period balance is projected by summing the current balance with the subledger
journal entry line amounts
• For posted journals, the opening balance and the period activity are calculated using the current balance and
journal line amount
Projected balances increases accuracy when booking entries to reconcile accounts.
Manage Accounting Reversals

To create an accounting reversal for a transaction or transaction distribution, the transaction objects should include the
appropriate header or line level accounting reversal options.
Accounting reversals enables you to reverse the accounting impact of a previously accounted transaction distribution or
all existing accounting for a transaction.
Accounting reversal terminology includes the following:
• Reversed (original) Distribution
◦ Refers to a transaction distribution that although successfully accounted, is either incorrect or canceled.
The transaction distribution is therefore reversed.
• Reversal Distribution
◦ Refers to a transaction distribution which reverses the effect of the original distribution on transaction
balances. Typically, reversal distributions are identical to the reversed distributions in all respects except
for entered (ledger) amounts that reverse the sign of the original.
• Replacement Distribution
◦ Refers to a transaction distribution which replaces the reversed distribution with the correct value.
Distribution Examples
This table contains distribution examples.
Invoice Distribution Line Invoice Line Type Accounting Date Amount Description
Number
1 Item 10-Jan-2013 1000 Reversed
190
Invoice Distribution Line Invoice Line Type Accounting Date Amount Description
Number
2 Item 12-Jan-2013 -1000 Reversal (of line 1)
3 Item 12-Jan-2013 2000 Replacement (of line 1)
Transaction Total 2000
Note that the original accounting impact of the reversed distributions is undone, even if the subledger journal setups or
accounting configurations have changed since the original subledger journal entry was generated.
Related Topics
• How You Manage Subledger Journal Adjustments
Correct Accounting Hub Transaction Data for Invalid Entries

You can correct errors on uploaded transaction data using the Review Journal Entries page:
• Search for subledger journal entries with an invalid status.

• 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.
Related Topics
191
Subledger Balances
Adjust Supporting Reference Initial Balances
Supporting References provides you the flexibility to store and report on additional information about a subledger
journal at the journal line level. You can choose to use supporting references with balances to record subledger balances
for a source using a combination of supporting references plus the chart of account combination.
The Import Supporting Reference Initial Balances spreadsheet lets you upload the initial balances for Supporting
References. The initial balance is the starting balance for a supporting reference in the context of an application, ledger,
and account combination.
Note: When using the Manage Configuration Packages task to export or import setup data, initial balances that have
been imported into one environment aren't going to be migrated into another. You must import balances separately
into each environment you maintain.
Access the task from the Setup and Maintenance work area.
Initialize Supporting Reference Balances when no balances exist
Let's say you already maintain a balance for certain dimensions in the legacy system which aren't available in Oracle
Fusion and want to bring in those balances when migrating to Oracle Fusion Cloud ERP. Let's assume supporting
reference balances are to be initialized against the supporting references - Account Number, Customer Category, Line
Type, Country Code, State Code as follows:
Ledger Subledger Period Account Currency Balance Balance Account Customer Line Type Country State
Combination (Debit) (Credit) Number Category Code Code
Vision Payables Jun-20 01-120-2210-0000-000

USD 12654 76768 Gold Goods US NY
Operations
Vision Payables Jun-20 01-120-2210-0000-000

USD 2030 76576 Silver Services US CA
Operations
You must navigate to the Adjust Supporting Reference Balances task and download the spreadsheet template. Use the
Adjust Supporting Reference Balances ADFdi spreadsheet to initialize supporting reference balances for the supporting
references - Account Number, Customer Category, Line Type, Country Code, State Code. The journal entry that gets
created in the background doesn't have supporting reference information for both sides that’s, the supporting reference
is NULL for the offsetting entry. In this example journal entries get created as follows:
Period Account Entered Entered Currency Accounted Accounted ANALYTICAL_

SR1 SR2 SR3 SR4 SR5
Combination
(Debit) (Credit) (Debit) (Credit) BALANCE_
FLAG
6/20/2021 01-120-2210-0000-000
12654 EUR 15050 P 76768 Gold Goods US NY
192

SR1 SR2 SR3 SR4 SR5
Combination
FLAG
6/20/2021 01-120-2210-0000-00012654 EUR 15050
6/20/2021 01-110-2240-0000-0002030 USD 2030 P 76456 Silver Services US CA
6/20/2021 01-110-2240-0000-000
2030 USD 2030
The journal entries created for initializing the supporting reference balances are created in Final status but not
transferred to GL, if all validations are successful. If you don't want balances to be maintained in the entered currency
( XLA_ENABLE_ENTERED_CURR_BAL_SUPP_REF is disabled), the supporting reference balances table is updated as
follows on initialization:
LEDGER_ APPL_ID PERIOD CCID PERIOD_ PERIOD_ SR1 SR2 SR3 SR4 SR5
ID BALANCE_ BALANCE_
DR CR
1 200 6/20/2021 01-120-2210-0000-000

15050 76768 Gold Goods US NY
1 200 6/20/2021 01-110-2240-0000-000 2030 76456 Silver Services US CA
If you maintain balances in the entered currency (XLA_ENABLE_ENTERED_CURR_BAL_SUPP_REF is enabled), the

supporting reference balances table is updated as follows on initialization:
LEDGER_ APPL_ PERIOD CCID PERIOD_ PERIOD_ PERIOD_ PERIOD_ ENTERED_SR1 SR2 SR3 SR4 SR5
ID ID BALANCE_BALANCE_ENTERED_ENTERED_CURRENCY_
DR CR BALANCE_BALANCE_CODE
DR CR
1 200 6/20/2021 01-120-2210-0000-000

15050 12654 EUR 12654 Gold Goods US NY
1 200 6/20/2021 01-110-2240-0000-000

2030 2030 USD 76456 Silver Services US CA
Adjust Supporting Reference Balances when balances exist
Let's say supporting reference balances already exist and you just want to adjust the balances. Assuming
supporting reference balances are existing for the following account and supporting reference combination in the
XLA_AC_BALANCES table and you want to do an upward adjustment of 200.00 USD.
DR CR
1 200 6/20/2021 01-120-1210-0000-000

12354 76768 Bronze Goods US NY
193
Navigate to the Adjust Supporting Reference Balances task and downloads the spreadsheet template. Use the Adjust
Supporting Reference Balances ADFdi spreadsheet to update supporting reference balances.
Manual journal entry is created in the background having supporting reference information for one of the lines which
is used to adjust balances, supporting reference is NULL for the offsetting entry. In this example journal entries get
created as follows:

SR1 SR2 SR3 SR4 SR5
Combination
FLAG
6/20/2021 01-120-1210-0000-000
200 USD 200 P 76768 Bronze Goods US NY
6/20/2021 01-120-1210-0000-000200 USD 200
The journal entries created for adjusting the supporting reference balances are created in Final status but not
transferred to GL, if all validations are successful. If you don't want balances to be maintained in the entered currency
(XLA_ENABLE_ENTERED_CURR_BAL_SUPP_REF is disabled), the supporting reference balances table is updated as
follows on initialization:
DR CR
1 200 6/20/2021 01-120-1210-0000-000

12554 76768 Bronze Goods US NY
Related Topics
• Update Subledger Accounting Balances Process
Adjust Control Balances

The volume of transactions to be processed using control balance transfer is significantly lower as journals are created
in summary mode to transfer the balance. Irrespective of which transactions are updated; the Unpaid Invoice, Paid
Invoices or Historical transactions, you have the flexibility to choose for which period and account combination you
want to transfer balances. Audit trail is maintained as existing journals in final status aren't impacted, for control
account balance transfer operation new SLA journals are created. You can adjust control balances as needed using the
spreadsheet interface regardless of accounting period status since entries aren't transferred to GL.
Transfer Control Balances due to Party Merge
Lets us say a party merge was triggered and you want to transfer control balances from the old party and site to the new
party and site. In this example let's assume Supplier - Office Depot, site - NY is merged with supplier - Office Supplies,
site - NY. Supplier - Office Depot, Site - NY has the following control balance records in SLA control balances table.
194
LEDGER_ID APPL_ID PERIOD CCID BEGINNING_ BEGINNING_ PERIOD_ PERIOD_ PARTY PARTY_
BALANCE_ BALANCE_ BALANCE_ BALANCE_ SITE
DR CR DR CR
1 200 4/20/2021 01-110-2210-0000-000 1200 2200 Office Depot NY
1 200 4/20/2021 01-110-2240-0000-000 2030 Office Depot NY
1 200 5/20/2021 01-000-1210-0000-000 1000 200 Office Depot NY
1 200 5/20/2021 01-000-1220-0000-000 500 100 Office Depot NY
Supplier - Office Depot is acquired by Office Supplies. Supplier - Office Depot, Site - NY is merged with new supplier -
Office Supplies, site - NY. You can use the Adjust Control Balances ADFdi spreadsheet to transfer control balances to the
new supplier - Office Supplies, site - NY.
The journal entries created for transferring control balances are created in Final status but not transferred to GL. The
control balances table is updated as follows on transfer:
DR CR DR CR
1 200 4/20/2021 01-110-2210-0000-000 1200 2200 Office Depot NY
1 200 4/20/2021 01-110-2240-0000-000 2030 Office Depot NY
1 200 5/20/2021 01-000-1210-0000-000 1000 200 Office Depot NY
1 200 5/20/2021 01-000-1220-0000-000 500 100 Office Depot NY
1 200 4/20/2021 01-110-2210-0000-000 1000 Office Depot NY
1 200 4/20/2021 01-110-2210-0000-000 1000 Office NY

Supplies
1 200 4/20/2021 01-110-2240-0000-000 2030 Office Depot NY
1 200 4/20/2021 01-110-2240-0000-000 2030 Office NY

Supplies
1 200 5/20/2021 01-000-1210-0000-000 1200 Office Depot NY
1 200 5/20/2021 01-000-1210-0000-000 1200 Office NY

Supplies
1 200 5/20/2021 01-000-1220-0000-000 400 Office Depot NY
195
DR CR DR CR
1 200 5/20/2021 01-000-1220-0000-000 400 Office NY

Supplies
Adjust Control Balances for a Party and Site
Let's say that you haven't enabled control accounts initially but at a later point of time you want to initialize control
balances for a party and site Or you already maintain control account balances in legacy system and want to bring in
those balances while upgrading to Oracle Fusion cloud ERP. Let's assume control balances are to be initialized against
supplier - Advanced Devices, site - San Jose as follows:
Ledger Subledger Period Account Accounted Accounted Supplier Site

Combination (Debit) (Credit)
Vision Payables 6/20/2021 01-120-2210-0000-000

12654 Advanced San Jose
Operations Devices
Vision Payables 6/20/2021 01-110-2240-0000-000 2030 Advanced San Jose

Operations Devices
The Application Implementation Consultant configures the natural accounts 2210 and 2240 as control accounts in the
FND setup and submits the Inherit Segment Value attributes program. You can use the Adjust Control Balances ADFdi
spreadsheet to initialize control balances for the supplier - Advanced Devices, site - San Jose.
As in the initialize case, the journal entry that gets created doesn't have party information for both sides. So in this
example, it gets created as follows:
Period Account Combination Accounted (Debit) Accounted (Credit) Supplier Site
6/20/2021 01-120-2210-0000-000 12654 Advanced Devices San Jose
6/20/2021 01-120-2210-0000-000 12654
6/20/2021 01-110-2240-0000-000 2030 Advanced Devices San Jose
6/20/2021 01-110-2240-0000-000 2030
The journal entries created for initializing control balances are created in Final status but not transferred to GL. The
control balances table is updated as follows on initialization:
196
DR CR DR CR
1 200 6/20/2021 01-120-2210-0000-000 12654 Advanced San Jose

Devices
1 200 6/20/2021 01-110-2240-0000-000 2030 Advanced San Jose

Devices
Third-Party Control Account Balances Report

This topic includes details about how you use the Third-Party Balances Report.
Overview
You can use the Third-Party Control Account Balances Report to review subledger accounting third-party control
account balances and activity for suppliers and customers.
Here is a screenshot of the Third-Party Control Account Balances Report.
Key Insights
You can view these information in the Third-Party Control Account Balances Report:
• Third-party balances for subledger accounting third-party control accounts.
197
• Subledger journal entry lines that add up to the total period activity for each control account, third party, and
third-party site.
• Third party and third-party site information.
• User transaction identifiers for the associated entries.
Report Parameters
Let's look at the parameters of the Third-Party Control Account Balances Report.
Name Description
Journal Source Select from a list of enabled journal sources mapped to an accounting generating subledger
application.
Ledger Select a ledger.
You must have access to the ledger either directly through a GL Data Access Set or through a:
• Business unit
• Asset book
• Payroll security assignment
From Accounting Period Indicate the beginning period for the report data.
To Accounting Period Indicate the ending period for the report data.
Third-Party Type Select the type of third party defined for the subledger application for the journal source. Values are
Customer, Supplier, and All.
Third-Party Name Select a customer or supplier based on the third party type.
Third-Party Site Select a third-party site for the supplier or customer identified by third-party name.
From Third-Party Number Indicate the beginning of the range of customer or supplier numbers based on the third party type.
To Third-Party Number Indicate the ending of the range of customer or supplier numbers greater than or equal to the From
value.
Include User Transaction Identifier Specify whether the user transaction identifiers are included in the report data.
Account Filter Enter the filtering conditions on the account. You can select all segments for the selected ledger and
define conditions including account value ranges.
Frequently Asked Questions

These are some frequently asked questions about the Third-Party Control Account Balances Report.
198
FAQ Answer
How do I find this report? Schedule and run this report from the Scheduled Processes work area on the Navigator menu.
Who uses this report? • Financial Accountant

• Financial Manager
• Financial Specialist
When do I use this report? Use this report when you want to review subledger accounting third-party control account balances
and activity for suppliers and customers.
What type of report is this? Oracle Business Intelligence Publisher
Related Topics
• Guidelines for Validating a Third-Party Control Account
• Accounting Attribute Assignments
• Third-Party Detail and Balances Reports
Update Subledger Accounting Balances Process

Use the Update Subledger Accounting Balances process (XLABABUP) to update subledger supporting reference
balances and third-party control account balances.
This process is run automatically following the Create Accounting process. It should be run manually if the auto run fails
for any reason.
Run the report from the Scheduled Processes page and optionally schedule the process to run periodically.
Note: Draft entries do not update balances. To include accurate balances, transactions must be accounted in Final.
Parameters
Subledger Application
List of all user accessible accounting generating subledgers.
Ledger
The list of ledgers is based on the user accessible business units, asset books or legal entities. Only the list of ledgers
associated with those business units, asset books or legal entities is shown.
Related Topics
• Import Supporting Reference Initial Balances Process
199
Carry Forward Subledger Accounting Balances Process

The Carry Forward Subledger Accounting Balances process will carry forward supporting reference balances and third-
party control account balances to the current period for a ledger. This process is automatically initiated when the
accounting period is newly opened.
Note: The process can also be submitted manually if the initial process executed abnormally when the accounting
period was opened.
Parameters
Ledger
The list of ledgers is based on the business units, asset books or legal entities that a subledger user has access to. Only
the list of ledgers associated with those business units, asset books or legal entities is shown.
Accounting Period
All periods for the accounting calendar and period type associated with the selected ledger.
Related Topics
• Viewing Projected Balances : Points to Consider
Advanced Features
Accounting Class Usages
Accounting class usages is a classification or grouping of accounting event classes to be used in a report or process
based on subledger journal entries. A report or process referring to such a group would only process subledger journal
entries tagged with the accounting event classes defined in the group.
Manage Accounting Class Usages Task

The Manage Accounting Class Usages task enables you to group accounting event classes. Use Accounting Class
Usages assignments to determine which subledger journal entry lines to retrieve for a particular process. For example,
for mass additions a subledger can define accounting class usages to identify the journal entry lines that must be
processed to create records for another subledger.
Defining Accounting Class Usages

Use the Manage Accounting Class Usages task to create assignments that may be associated with a ledger. In the
Accounting Class Assignments region, assign accounting classes to an assignment definition.
Predefined processes and assignment definitions cannot be deleted or updated. You can copy a predefined assignment
definition and modify if necessary.
200
Accrual Reversals in Accounting Hub

To use accrual reversal, you assign application or standard date sources to the Accrual Reversal Accounting Date Source
accounting attribute. When this accounting attribute has a value, the Create Accounting process generates an entry that
reverses the accrual entry.
Here's what you do to define how and when accrual reversals are automatically performed:
• Indicate that an accounting event is eligible for accrual reversal.

• Determine when the accrual is reversed.
• Schedule the Create Accrual Reversal Accounting process to generate the reversal entries of the accrual.
Note: You must not enable reversal in General Ledger journal for the journal source and category if accrual reversal is
implemented in subledger.
Accrual Reversal Process Steps

This flow chart shows the accrual reversal process in Accounting Hub.
201
Note: End Date: The date till when the Create Accounting process selects accounting events for processing.
202
1. Assign a date source to the Accrual Reversal Accounting Date Source accounting attribute at the event class
level.
Use this attribute to schedule the automatic reversal of a journal entry. On the Manage Accounting Attributes
page, assign any standard date source or one of these application sources to the Accrual Reversal Accounting
Date Source accounting attribute as a nondefault assignment:
◦ 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: If a default source is assigned to the Accrual Reversal Accounting Date Source accounting attribute, it
will be assigned to all the journal entry rule set defined for the event class.
2. Define a journal entry rule set for the event type for which you would like to use the accrual reversal feature and
select an accrual reversal accounting date source.
3. Import Accounting Transaction with accrual transactions.
4. The Import Accounting Transaction process automatically submits the Create Accounting process that creates
both accrual and reversal journal entries.
If that accrual entry has exceptions, you must resolve the exceptions and then manually submit the Create
Accounting process again.
For all valid accrual journal entries, the Create Accounting process also creates the accrual reversal journal
entry. Reversals can either be done by switching the debit and credit side on entries or by using negative
amounts. You use the Reversal Method option on the Manage Subledger Accounting Options page to specify
the method to use for reversals.
Here are the factors that affect the status of the accrual reversal journal entry:
◦ The status of the accounting period of the accrual reversal journal entry
◦ The end accounting date specified in the Create Accounting request parameters
This table summarizes how the application sets the status of an accrual reversal journal entry in different
conditions:
Condition Open or Future Entry Closed Accounting Period Never Opened Accounting
Accounting Period Period
The accrual reversal event Creates the reversal entry with ◦ Adjusts the accounting
date to the next open or
◦ Adjusts the accounting
date to the next open
is processed by the Create the status specified in the
future period. Creates period. Creates the reversal
Accounting process as part Import Accounting Transactions the reversal entry with entry with the status
of the Import Accounting process. the status specified in specified in the Import
Transactions process. the Import Accounting Accounting Transactions
Transactions process. process.
◦ If no open period is found,
creates the journal entry
with the error status. with the incomplete status.
203
Condition Open or Future Entry Closed Accounting Period Never Opened Accounting
Accounting Period Period
The Create Accounting process Creates the reversal entry with Adjusts the accounting date to ◦ Adjusts the accounting
date to the next open
is submitted separately and the status specified in the Create the next open or future period.
period.
accrual reversal date is on or Accounting request. Creates the reversal entry with
before the end accounting date. the status specified in the Create - If the adjusted accounting
Accounting request. date is before end date
of the Create Accounting
process, creates the
reversal entry with the
status specified in the
Create Accounting request.
- If the adjusted accounting
date is after end date of the
Create Accounting process,
creates the reversal entry
with the incomplete status.
with the incomplete status.
The Create Accounting process Creates the reversal entry with ◦ Adjusts the accounting
date to the next open or
Creates the reversal entry with
is submitted separately and the incomplete status. the incomplete status.
future period. Creates the
accrual reversal date is after the reversal entry with the
end accounting date. incomplete status.
with the error status.
5. Submit Create Accrual Reversal Accounting to process any incomplete accrual reversal journal entries. This
process validates the reversal entry and changes the reversal entry to Final status, if it passes validation.
6. Schedule the Create Accrual Reversal Accounting process to run automatically in each accounting period. As a
best practice, run before closing the period.
7. View accrual reversal accounting entries.
Related Topics
• Examples of Accrual Reversal
• How You Submit the Create Accrual Reversal Accounting Process
• Overview of Subledger Journal Entry
• Accounting Attribute Assignments
• Subledger Accounting Options
Examples of Accrual Reversal

The following examples describe how accrual reversals are scheduled and accounted.
Example 1
A company receives materials worth 100 (USD) on the 30th of the month but hasn't been invoiced. The following journal
entry is created when the material is received to record the accrual.
204
This table contains a journal entry.
Account Entered DR Entered CR Accounted DR (USD) Accounted CR (USD)
Accrual Expense 100.00 100.00
Accrual Liability 100.00 100.00
The accrual reversal accounting date is set to First Day of Next Accounting Period. The following journal entry is created
to reverse the accrual.
This table contains the reversal journal entry.
Accrual Liability 100.00 100.00
Accrual Expense 100.00 100.00
Example 2
Future trading requires a margin account that's market-to-market on a daily basis. This means that the investor or
ledger's gains or losses on the position are reflected on a daily basis. If the margin account is less than a specified
amount (the maintenance of the margin), a margin call is issued. This requires the holder of the account to replenish the
account to the initial margin level or close out the position.
The investor or ledger must mark the account to market each day. The entry booked from the day before must be
reversed to reflect the new position.
Journal Entry Creation
• The following journal entry creation date is June 1, 2006.

• Accounting date: 01-Jun-2006
This table contains the journal entry.
Loss 100.00 100.00
Margin Liability 100.00 100.00
Reverse the Journal Entry
• The accrual reversal accounting date is set to Next Day. The following journal entry is created to reverse the
journal entry from June 1.
205
• Accounting Date: 02-Jun-2006
Loss 100.00 100.00
Reflect the New Position
• On June 2, a new journal entry is created to reflect the new position, which will be reversed on June 3.
Loss 105.00 105.00
Reverse the Accrual
• On June 3, the following journal entry is created to reverse the accrual from June 2.
Loss 105.00 105.00
Related Topics
• How You Submit the Create Accrual Reversal Accounting Process
206
How You Submit the Create Accrual Reversal Accounting Process

The Create Accrual Reversal Accounting process processes incomplete accrual reversal journal entries with accounting
dates that fall on or before the End Date parameter specified. If the incomplete accrual reversal accounting entries are
validated successfully, they're set to Final status and then posted to the general ledger, dependent on the parameters.
Report Parameters
This table contains the parameters for the Create Accrual Reversal Accounting process.
Prompt Description
Subledger Application Source system for which the Create Accrual Reversal Accounting process is being executed.
Ledger Ledger name for which the Create Accrual Reversal Accounting process is being executed.
Process Category The process category indicates that all associated accounting event classes and their accounting event
types are selected for processing.
End Date End date puts a filter on the selection of journal entries. Only incomplete journal entries having an
accounting date on or before the end date are selected for accounting.
Default value is current system date.
Process Events Adds other filter criteria for the Create Accounting process to specific events:
• All: Process all incomplete journal entries and meets the End Date selection criteria
• Errors: Process only those entries that have previously been processed in error.
• Invalid Accounts: Process only those events that have previously been processed in error. Replace
any invalid accounts with the suspense account.
Default value is All.
Report Identify the type of details to display on the execution report. The report can be printed in Summary,
Detail, or No report.
Default value is Summary.
Transfer to General Ledger Indicates whether the Create Accrual Reversal Accounting process should submit the Transfer to GL
process; Yes, No.
Post in General Ledger Indicates whether to submit General Ledger posting after Transfer to GL process is complete.
Journal Batch Batch name for General Ledger journal entries.
207
Related Topics
• Examples of Accrual Reversal
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 defer the recognition of revenue or prepaid expense 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.
Note: You can only preview multiperiod journal entries for a single accounting period.
Multiperiod Accounting Process Flow

This figure illustrates the multiperiod accounting process flow.
208
1. Enter transaction with multiperiod accounting date range.

2. Create accounting event. Populate multiperiod accounting Start and End dates in transaction objects.
3. Submit the Create Accounting process.
◦ Final entry created for initial entry? Yes
- Submit Create Accounting process to generate multiperiod journal entries

◦ Final entry created for initial entry? No
- Draft entry created for initial entry? Yes
◦ Resolve exception.
- Draft entry created for initial entry? No
◦ Submit the Create Multiperiod Accounting process to generate multiperiod journal entries.
Implementation Steps
Implementation Step Process Flow
This figure illustrates the implementation steps.
209
1. Define a user-defined formula determining how to distribute the entered amount across accounting periods. If
required, you can use the new multiperiod predefined sources. For example:
◦ Multiperiod Original Entered Amount

◦ Multiperiod Recognized Entered Amount
◦ Last Multiperiod Accounting Date
◦ Number of Days in Current Accounting Period
2. Define Multiperiod Classes using the Manage Subledger Accounting Lookups task.
◦ Lookup Type: ORA_XLA_MULTIPERIOD_CLASS

3. 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.
4. 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.
5. 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.
6. Assign the journal entry rule set to the accounting method.
210
7. Schedule the Create Multiperiod Accounting process to run after the Create Accounting process so that
recognition journal entries are properly booked each period. If multiperiod accounting is also implemented in
any of the subledger level secondary ledgers, you must schedule the Create Multiperiod Accounting process for
the primary ledger as well as each of its subledger level secondary ledgers.
Related Topics
• Example of Multiperiod Accounting
• Considerations for Multiperiod Accounting
Example of Multiperiod Accounting

The subledger multiperiod accounting and user-defined formula features provide the ability to satisfy the FASB 91
accounting requirement. This requirement of deferred recognition of fee and direct loan cost is met by modifying the
recognition of fee amounts with user-defined formulas.
Example
A personal 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
Upon loan origination on 01-JUL-2016 the origination fee must be booked as unearned income:
Initial Journal Entry for Loan Fee
This table contains the journal that is created when the loan is originated.
Entered DR (USD) Entered CR (USD)
Receivable 300.00
Unearned Fee Income 300.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. For example:
Monthly Journal Entry for Loan Fee
This table contains of the journal achieved using a user-defined formula.
Unearned Fee Income 50.00
211
Loan Fee Income 50.00
Using Multiperiod Subledger Accounting Rules

Accounting Hub users can define subledger accounting rules to create the multiperiod accounting entries. For example:
This table contains the usage of journal lines rules, account rules and the usage associated with multiperiod accounting.
Journal Line Rules Account Rules Usage
Unearned Fee Income Unearned Fee Income Account Journal line rule for the deferral entry.
• Side = Credit Used to generate a credit line to the unearned

fee income account.
• Multiperiod Option = No
• 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 the recognition entry.
• Side = Credit Used by the Create Multiperiod Accounting

process to generate future entries with prorate
• Multiperiod Option = Yes amounts, such as the CR 50.00 (USD) in the
example.
• Multiperiod Class = Loan fee
• Accounting attributes:
◦ 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 current accounting period.
• Assign the user-defined formula to the Entered Amount accounting attribute.
• The Create Multiperiod Accounting process calculates entered amount for the multiperiod entries as:
Entered Amount = Amount Returned by User-Defined formula - Multiperiod Recognized Entered Amount
◦ Where 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.
212
Sample User-Defined Formulas

These sample user-defined formula definitions can be used to prorate the loan fee amount.
Prorate by Number of Periods
• To prorate the entered amount evenly across each period:

" Multiperiod Original Entered Amount" * NumberofGLPeriod ("Origination Date", "Last Day of Current
Accounting Period") / NumberofGLPeriod ("Origination Date", "Maturity Date")
◦ Where the:
- Multiperiod Original Entered Amount, Origination Date and Maturity Date are standard application
sources (Application: Loans).
- Last Day of Current Accounting Period is a system source (Application: Subledger Accounting).
- NumberofGLPeriod is a predefined numeric function.
• The entered amount for the multiperiod journal would be calculated as follows:
This table contains the calculation that occurs in the Create Multiperiod Accounting process.
Accounting Date Number of Periods Since Multiperiod Recognized Amount Returned from Multiperiod Journal
Multiperiod Start Date Entered Amount (A) User-Defined Formula (B) Entered Amount (B-A)
31-Jul-16 1 0.00 300.00*1/6=50.00 50.00
31-Aug-16 2 0.00+50.00=50.00 300.00*2/6=100.00 100.00-50.00=50.00
30-Sep-16 3 50.00+50.00=100.00 300.00*3/6=150.00 150.00-100.00=50.00
31-Oct-16 4 100.00+50.00=150.00 300.00*4/6=200.00 200.00-150.00=50.00
30-Nov-16 5 150.00+50.00=200.00 300.00*5/6=250.00 250.00-200.00=50.00
31-Dec-16 6 200.00+50.00=250.00 300.00*6/6=300.00 300.00-250.00=50.00
Note: These columns are calculated by the Create Multiperiod Accounting process:
• Amount Returned from User-Defined Formula (B)
• Multiperiod Journal Entered Amount (B-A)
Prorate by Number of Days
• To prorate entered amount by the actual number of days in each period:

" Multiperiod Original Entered Amount" * ("Last Day of Current Accounting Period" - "Origination Date"
+ 1) / ("Maturity Date" - "Origination Date" +1)
• The entered amount for the multiperiod journal is calculated as follows:
213
This table contains the calculation that occurs in the Create Multiperiod Accounting process.
Accounting Date Number of Days Since Multiperiod Recognized Amount Returned from Multiperiod Journal
Multiperiod Start Date Entered Amount (A) User-Defined Formula (B) Entered Amount (B-A)
31-Jul-16 31 0.00 300.00*31/184.00=50.54 50.54
31-Aug-16 62 0.00+50.54=50.54 300.00*62/184.00=100.09 100.09-50.54=50.55
30-Sep-16 92 50.54+50.55=100.09 300.00*92/184.00=150 150.00-100.09=48.91
31-Oct-16 123 100.09+48.91=150.00 300.00*123/184.00=200.54 200.54-150.00=50.54
30-Nov-16 153 150.00+50.54=200.54 300.00*153/184.00=249.46 249.46-200.54=48.92
31-Dec-16 184 200.54+48.92=249.46 300.00*184/184.00=300.00 300.00-249.46=50.54
• Note that rounding differences, if any, are included in the resulting entered amount for the multiperiod journals.
Prerequisites
• Provide date format sources to store the multiperiod start and end dates in transaction objects.
• For the event class that supports multiperiod accounting, assign these sources to the accounting attributes:
◦ Multiperiod Start Date

◦ Multiperiod End Date
• Define the multiperiod class in the subledger accounting lookup. The multiperiod class is used to identify the
journal line for which the amount is prorated across multiple accounting periods.
Tip: Accounted amounts for multiperiod journals are calculated by the Create Multiperiod Accounting process
prorating proportionally to the entered amount. Rounding error differences are included in the prorated amount.
Multiperiod transaction data must be available in transaction objects until the last multiperiod entry has been
accounted in final status.
Related Topics
• Multiperiod Accounting
• Manage User-Defined Formulas
214
Considerations for Multiperiod Accounting

To achieve a successful implementation of multiperiod accounting, the following points must be taken into
consideration.
Determine when to raise a new accounting event

Determine when a new accounting event must be raised throughout the life cycle of a multiperiod transaction.
• If only the multiperiod start and end dates are changed, a new accounting event isn't required. As the
transaction object is maintained to provide the new multiperiod start date, the impact of the change is reflected
in the next multiperiod journal.
• Raise a new accounting event if the amount is changed, or a transaction is canceled after the transaction is
accounted in a Final status.
If the multiperiod start date is changed after the transaction is accounted, it's not necessary to raise a new accounting
event. The assumption is that all other transaction attributes remain the same. If the transaction object is maintained
to provide the new multiperiod start date, the impact of the change is reflected in the next multiperiod journal. This
depends on the prorate method and is also true for future journal entries.
However, if the transaction amount is changed after the transaction is accounted; the new accounting event is needed,
which affects the total deferral amount.
Tip: We suggest a detailed analysis be performed to determine whether to raise a new accounting event when
transaction attributes are updated.
Raise a transaction reversal event

Consider the multiperiod journal accounting date when raising the transaction reversal event.
Set the reversal accounting date to a date after the last multiperiod journal with Final status. A reversal entry reverses all
existing final entries, including the multiperiod journals, with the reversal accounting date.
For example, the transaction accounting date is on 01-Feb and multiperiod journals have been created for February and
March with a Final status. If the transaction is canceled, the cancellation event should be set to 01-Apr or the first day of
the next open period, whichever is later.
Provide the multiperiod start and end dates

The multiperiod start date and multiperiod end date must be provided in transaction objects for event classes that
support multiperiod accounting. These date sources are mapped to the accounting attributes Multiperiod Start Date
and Multiperiod End Date for the event class. They must both be blank or both be populated in the transaction objects.
Once a multiperiod journal is created in Final status, the multiperiod end date should not be modified to any day prior to
the accounting date of the last multiperiod journal in the primary and secondary ledgers.
215
Deferring the multiperiod end date

When you're deferring the multiperiod end date, then the recognition amount has to be adjusted. As the recognition
line isn't generated based on the journal line rule, the switch debit and credit option isn't applicable. The appropriate
offsetting entry for the positive or negative amount is generated to offset the extra recognition.
For example, if you're extending for 3 months and have already run the multiperiod accounting for the first 2 months,
you would have recognized more than the amount required to offset; hence a negative entry will be generated.
Provide the multiperiod transaction data

Multiperiod transaction data must be available in subledger transaction objects until the last multiperiod entry is
accounted in Final status.
At least one line level transaction object is required for the event class to use multiperiod feature. Ensure transaction
objects are populated with current data for the multiperiod transaction throughout the life cycle of multiperiod, even if
the transaction is accounted.
For example, if the multiperiod start date is changed after the transaction is accounted but not all future entries have
been accounted. The new multiperiod start date should be populated in the transaction object. This enables the Create
Multiperiod Accounting process to calculate the prorate amount according to the modified multiperiod date range.
Process the multiperiod accounting

Multiperiod recognition entries are created based on transaction objects data and accounting rule definition at the time
the Create Multiperiod Accounting process is executed.
• The entered amount value for the multiperiod journal is calculated by a formula. This formula is assigned to the
Entered Amount accounting attribute on the multiperiod journal line rule.
• The accounted amount value for multiperiod journals is calculated by the Create Multiperiod Accounting
process, prorating proportionally to the entered amount, including rounding differences.
Multiperiod accounting entries aren't created:
• If any subledger level reporting currency or secondary ledger is disabled, although the multiperiod transaction
may not be fully recognized yet.
• If subledger level reporting currency is added after the journal is created in Final status, the multiperiod journal
isn't created for the new reporting currency.
• If the transaction accounting date is prior to the first open period of a reporting currency or secondary ledger,
the journal isn't created for the reporting currency or secondary ledger.
Multiperiod transactions are processed by the Create Multiperiod Accounting process only once for each accounting
period and transaction.
• Don't modify the multiperiod start date for a transaction to a date in a prior accounting period of the last
multiperiod journal in primary and secondary ledgers.
• If the multiperiod start date for a transaction is modified to a date in a prior accounting period, accounting
periods that were previously processed for the transaction by the Create Multiperiod Accounting process aren't
processed, regardless of the period status. Any adjustment in the prorated amount due to change of start date
will be accounted in the next accounting period.
216
Related Topics
Overview of Sequencing of Accounting Entries

The following sequences are attached to subledger journal entries or general ledger journal entries. These two
sequences aren't mutually exclusive and can coexist in the same journal entry.
Accounting Sequence
The accounting sequence is assigned to subledger journal entries at the time that the journal entry is completed. The
sequence is assigned in the completion date order using the accounting date as the date criterion for determining the
sequence to be used.
Reporting Sequence
The reporting sequence is assigned to both subledger journal entries and general ledger journal entries when the
accounting period is closed. This sequence is used by most of the legal reports required in some countries as the main
sorting criterion to display the journal entries.
Note: In some related documents, this sequence is referred to as the chronological sequence.
Related Topics
• Overview of Accounting and Reporting Sequences
• How to Define Journal Sequences Manually
Subledger Accounting Profile Options

Set values for each profile option to specify how Oracle Fusion Subledger Accounting controls access to and processes
data.
Profile Options
The table contains the profile options that are available for subledger accounting.
Profile Option Profile Display Name Profile Description
XLA_DIAGNOSTIC_MODE Diagnostics Enabled Control whether transaction data used in

accounting generation should be gathered for
diagnostics.
XLA_DISABLE_GLLEZL Journal Import Disabled Control whether subledger journal entries are
imported to the general ledger.
217
Profile Option Profile Display Name Profile Description
XLA_ENABLE_TRANSFER_TO_EBS_GL Enable Transfer to Oracle EBS GL Specify whether the target for transfer and post
subledger journal entries is Oracle E-Business
Suite General Ledger.
XLA_ENABLE_TRANSFER_TO_PSFT_GL Enable Transfer to Oracle PeopleSoft GL Specify whether the target for transfer and post
subledger journal entries is Oracle PeopleSoft
General Ledger.
XLA_OTE_OLA_POLLING_INTERVAL Online Accounting Request Polling Interval Set the interval in seconds for online
accounting engine to check for incoming
accounting requests.
XLA_OTE_OLA_PROCS Number of Online Accounting Processes Set the number of processes for online
accounting.
XLA_OTE_OLA_TIMEOUT_LIMIT Online Accounting Processing Timeout Limit Set the number of seconds online accounting
engine attempts to process a transaction before
timing out.
XLA_SHOW_ZERO_AMT_JRNL Zero Amount Journal Lines Displayed Show zero amount journal lines.
ORA_XLA_DELETE_TARGET_MAPPINGS_ON_ Delete and Upload Mapping Set Values on Enable the deletion of existing mapping
IMPORT Import set values in the target environment when
importing mapping sets.
Related Topics
• Overview of Profile Options
Transaction Reversal
You can import a new transaction record to Accounting Hub to reverse the accounting of a transaction in the same
batch or an existing transaction.
Make sure that the new transaction record includes these values:
• The same transaction number as the transaction you want to reverse.

• The value of the reversal indicator as Y.
Here's what happens when you import the new transaction record. Accounting Hub generates a reversal accounting
that offsets the accounting of the original transaction.
Example of Transaction Reversal

Let's say that an accounting transaction with transaction number 1001 is imported and accounted in Accounting Hub
successfully. Later, this transaction is canceled in the source system.
218
To reverse the accounting transaction created in Accounting Hub, you import a new accounting transaction with the
same transaction number 1001 and set the reversal indicator as Y. After the new accounting transaction record is
imported, Accounting Hub creates journal entries to offset the accounting effect from the original transaction.
Before You Start

Here are some of the things you must do before you can start using transaction reversals:
• Enable the Flexible Configuration of the Accounting Flow feature.

• Opt in to enable this feature.
• Enable transaction reversal for subledgers that use this feature.
• Download and use the latest transaction template for the subledger.
Other Implementation Considerations

You might be wondering how to reverse a multiperiod accounting transaction. In such a case, make sure that the
transaction date for the reversal record is on or after the accounting date of the last multiperiod accounting entry of the
transaction being reversed.
Subledger Accounting Reporting

Oracle Fusion Subledger Accounting Predefined Reports
Oracle Subledger Accounting provides accounting reports for fiscal and internal control purposes.
The reports are comprehensive from a financial standpoint and include the best source of information for each type of
journal entry. These reports can be used in lieu of the General Ledger-based journals and account analysis reports to
see detailed subledger journal entries as well as supporting transaction information.
Scheduled Processes work area
Reports can be scheduled and run from the Scheduled Processes work area found in Tools on the Navigator.
Reports and Analytics work area
In some cases, reports are also:
• These reports are available from the Reports and Analytics work area, found in Tools on the Navigator, or from
other work areas.
• Opened using links that deploy the business intelligence (BI) catalog.
The following table contains the primary predefined reports by type:
Account Analysis Reports
This table contains a listing of Subledger Accounting account analysis reports.
219
Display Name Description
Account Analysis Report Provides drill down information about the movement on a particular account for a period or range of
periods. It only includes journal entries posted to general ledger.
Account Analysis by Legal Entity Report Prints account balances by account combination and selected segments with subledger journal details,
including third-party information and sequences. Flexible grouping and sorting options are provided at
submission.
Journal Reports
This table contains a listing of Subledger Accounting journal reports.
Daily Journals Report Lists subledger journal activity for a given period or date range, journal source, entered currency, and
journal batch. Report prints detailed subledger journal lines prior to general ledger summarization.
Third party and transaction details are also listed for the journal lines.
Journal Entries Report Displays detailed information for subledger and general ledger journal entries. Groups report by ledger,
journal source, journal category, and event class at submission.
Journal Ledger Report Lists the accounting entries with subledger details like transaction number, transaction date, and line
description, using flexible sorting options that are provided at report submission. This report provides
a real audit trail between general ledger and subledgers to satisfy legal and business requirements.
Journals and Third Party Report Prints all journals posted in Oracle Fusion General Ledger for the accounting period. The report
provides accounting and reporting sequence details, detailed subledger accounting entry lines
reporting level regardless of the ledger journals summarization. Assists in verifying that all journals
are accurately recorded in chronological order with no gaps. It uses legal sequencing rules for both
accounting entries and source documents.
Subledger Detail Journal Report Displays information about the posted general ledger journal batches that originate from Oracle Fusion
Receivables and Oracle Fusion Payables subledgers. The report prints subledger details like transaction
number, transaction date, transaction amount in entered and ledger currency.
Third Party Reports
This table contains a listing of Subledger Accounting third party reports.
Third-Party Balances Report Displays subledger balance and account activity information for suppliers and customers.
Third-Party Account Balance Report Prints account and original third-party transactions impacting the account during a particular period of
time. The report is run to ensure that subledger and general ledger balances reconcile, and to identify
possible reasons for any discrepancies.
Third-Party Balances Summary Report Displays information for each account of the third party and third-party site, and account
identification. This report can be used as a tool for auditing third-party accounts.
220
Third-Party Detail and Balances Report Provides third party account balances and accounting activity details for the requested accounting
period range. You can review the accounting process details by third party and audit third-party
accounts in detail.
Other Subledger Accounting Reports
This table contains a listing of other Subledger Accounting reports.
Accounting Event Diagnostic Report Shows the transaction data used in accounting. The data is collected when the profile option SLA:
Enable Diagnostics is set and the Create Accounting process is run.
Subledger Accounting Method Setups Displays the accounting setups for a subledger application and accounting method.
Report
Subledger Period Close Exceptions Report Lists all accounting events and journal entries that fail period close validation. Groups report by ledger,
period, journal source, journal category, and event class at submission.
To run predefined reports, navigate to the Scheduled Processes work area and follow these steps:
1. Click the Schedule New Process button

2. Search on the process name.
3. Enter your parameters.
4. Enter your process options and schedule.
5. Click Submit.
Subledger Accounting Subject Areas, Folders, and Attributes

To create real-time analyses for Oracle Fusion Subledger Accounting you should be familiar with subject areas, folders,
and attributes.
Subject Areas
To create an analysis, you begin by selecting a subject area from which you select columns of information to include in
the analysis. For example, to create an analysis of journal information, you begin by selecting a Subledger Accounting-
Journals Real Time subject area. Subject areas are based around a business object or fact. In this example, the subject
area is based on the column in the subledger entries tables.
Subledger Accounting has 2 specific subject areas:
• Subledger Accounting- Journals Real Time

• Subledger Accounting - Supporting References Real Time
221
Folders
Each subject area has one fact folder and a number of dimension folders. Fact folders contain attributes that can be
measured, meaning that they're numeric values like journal debit and credit amounts. Fact folders are in the list of
folders and are usually named after the subject area. Dimension folders contain attribute and hierarchical columns like
journal name and accounting period.
Some folders appear in more than one subject area, such as Time. These are referred to as common folders or common
dimensions.
Each folder within a subject area may have a different level of granularity. For example:
• Accounting Class has accounting class attributes.

• Bill-to Customer has subfolders and attributes within the subfolders.
Attributes
Finally, each dimension folder contains attributes (columns), such as balance type and posting date. This figure
illustrates the structure of subject areas, folders, and attributes.
This figure illustrates the subject area listing that includes the Subledger Accounting - Journals Real Time subject area,
folders, and attributes.
222
The figure illustrates these components:
• Subject area: Subledger Accounting - Journals Real Time

• Dimension - Presentation Folder: Accounting Class
• Dimension - Attributes: Accounting Class Code, Accounting Class Description and Accounting Class Meaning.
• Fact - Presentation Folder: Journals
• Fact - Measures: Journal Line Accounted Amount CR, Journal Line Accounted Amount DR, Journal Line
Entered Amount CR, Journal Line Entered Amount DR, Journal Line Statistical Amount, Unrounded Accounted
Amount CR, Unrounded Accounted Amount DR, Unrounded Entered Amount CR, and Unrounded Entered
Amount DR.
223
Related Topics
• How Data Is Structured for Analytics
Access the Create Multiperiod Accounting Execution Report

When you submit the Create Multiperiod Accounting process, the Create Multiperiod Accounting Execution Report is
automatically submitted. In this report, you can see entries created by the Create Multiperiod Accounting process.
Here is what you do to recreate a Create Multiperiod Accounting Execution Report.
• Submit the Create Multiperiod Accounting process.

• Use the same request identifier of the required Create Multiperiod Accounting process that was run previously
by the same user. Also, no other Create Multiperiod Accounting process should have been run with the same
criteria.
Related Topics
Use the Supporting References Report

In this procedure, you create and view the supporting references report in OTBI (Oracle Transactional Business
Intelligence).
Create a Supporting References Report

Before you create a supporting reference report, you must ensure that supporting references are assigned to journal
lines in the journal entry rule set and then the accounting created .
1. From the Home page, click Navigator > Reports and Analytics.
2. Open the Create drop down.
3. Select Analysis.
224
4. Select Subject Area: Subledger Accounting - Supporting Reference Real Time.
a. In the Create Analysis region of the Select Columns page, expand the Subject Area.
b. Expand the folders and select the desired columns.
- Click the Add icon to move columns to the Selected Columnsregion.

- To rename columns, select the column row and click the Edit icon.
- Resequence columns by using the arrows.
This table contains column names used in the supporting references report.
Folder Column
Journal Source Journal User Source Name
Ledger Ledger Name
Supporting Reference Balance Select the appropriate supporting references

Details
Rename as wanted.
GL Account Concatenated Segments
Ledger Ledger Currency
Time Accounting Period Name
Supporting Reference Balances Period Balance Dr
Period Balance Cr
c. Click Next button.

5. On the Select Views page:
a. Enter the report Title.

b. Select Table option.
c. Click Next .
d. Click theNext button again to skip the Edit Table page.
225
6. On the Sort and Filter page:
a. Click Add Filter.

b. Select Ledger Name.
c. Select Operator 'is equal to'.
d. Enter wanted ledger name.
e. To add another filter. Click Add Filter.
f. Select Journal User Source Name.
g. Select Operator 'is equal to'.
h. Enter wanted journal user source name.
i. Click Submit.
7. On the Create Analysis page:
a. Enter Analysis Name.

b. In the Save In region, select My Folders.
c. Click Submit.
d. Click OK.
View the Supporting References Report

View the supporting reference report from the navigation pane.
1. Expand the navigation pane.

2. Expand My Folders.
3. Click your report name.
4. Click View action.
5. The supporting reference balances report is displayed.
Note: If you don't see any data, the balances may not yet be updated. In that case, you must run the Update
Subledger Accounting Balances process and then view again.
Related Topics
FAQs for Subledger Accounting

Can I have multiple event classes for applications created in
spreadsheets?
No, use multiple event types instead. The setup upload creates a separate event type for each transaction type defined
in the Source System worksheet. You can also add new event types in the event model from the Manage Subledger
Application page.
226
Can I have subledger accounting entries in Adjustment Only

ledgers?
No, you can use Adjustment Only ledgers for General Ledger manual journals only. However, you can define a
Subledger level secondary ledger with valuation method enabled and use it for subledger journal adjustments. You
can then create a ledger set to combine the secondary ledger with the primary ledger. Use the ledger set while running
reports to obtain a complete accounting representation that includes both transactional data and adjustments.
Can I import transactions into adjusting periods directly?

No, you can import accounting transactions only to nonadjusting periods. However, you can create subledger journal
adjustments in adjusting periods from the Create Subledger Journal Entry page. You can also upload subledger journal
adjustments in adjusting periods using the Create Subledger Journals spreadsheet.
Can I enable flexible configuration only for select subledger

applications?
No. If you enable the Flexible Configuration of Accounting Hub Cloud Service End to End Flow feature, it applies to all
subledger applications.
Can I adjust accounting date when processing backdated

transactions?
Backdated transactions would be accounted with errors if the corresponding accounting period is closed. You can delete
invalid transactions, adjust dates in the data file, and import again.
Related Topics
• Overview of Accounting Hub Maintenance
• Run the Accounting Hub Maintenance Process to Delete Transactions
227
228
Implementing Accounting Hub Intercompany Processing Rules
8 Intercompany Processing Rules
Overview of Intercompany Processing Rules

Define intercompany system options to set up intercompany processing rules at the enterprise level, based on your
specific business needs.
To maintain consistency throughout an enterprise, intercompany transaction processing rules should be defined at the
enterprise level. By standardizing these rules, an enterprise can minimize disputes, decrease processing time, and cut
administrative costs.
Before setting up intercompany system options, you must determine how to process your intercompany transactions.
For example, to:
• Enforce an enterprise-wide currency or allow intercompany transactions in local currencies.

• Allow receivers to reject intercompany transactions.
• Determine the minimum transaction amount that's processed.
Related Topics
• Intercompany System Options
• Manage Intercompany Organizations
• Customer and Supplier Assignment
• Intercompany Receivables Assignments
Overview of Intercompany Balancing Rules

Intercompany balancing rules are used to generate the accounts needed to balance journals that are out of balance by
legal entity or primary balancing segment values. You specify the intercompany receivables and intercompany payables
accounts that you want to use as the template for building the intercompany receivables and intercompany payables
accounts. The intercompany balancing feature then uses these rules to generate the accounts of the balancing lines it
creates.
Journals lines are first summarized by the legal entity and are balanced by the legal entity. Since a legal entity can have
many primary balancing segment values, it's possible that a journal could have multiple lines for a legal entity with
different primary balancing segment values. In that case, when intercompany balancing is done, the lowest primary
balancing segment value within each legal entity in the journal is used. After this, balancing occurs across balancing
segment values within each legal entity.
These same rules are also used to generate the intercompany receivables account and intercompany payables account
of transactions entered in the Intercompany module.
The intercompany balancing rules are also used to generate the intercompany receivables account for the provider side
of an intercompany transaction. The balancing rules also used to generate the intercompany payables account for the
receiver side of an intercompany transaction.
229
Related Topics
• Intercompany Balancing Rules
• Example of Intercompany Balancing Rules
• Examples of Using Chart of Accounts Rules for Intercompany Balancing
• Example of Additional Intercompany Balancing and Clearing Options
Overview of Intercompany Allocations

The two processes you can use for intercompany allocation generation are Generate Intercompany Allocations
and Generate General Ledger Allocations. You can use both processes for single-ledger allocations or cross-ledger
allocations. The Generate Intercompany Allocations process updates Oracle Fusion Intercompany tables. The Generate
General Ledger Allocations process updates Oracle Fusion General Ledger tables.
Related Topics
• How Intercompany Allocations Are Generated
• Example of Generating Intercompany Receivables and Intercompany Payables Accounts for Manual
Transactions
• Cross-Ledger Allocations
• Examples of Cross-Ledger Allocations
FAQs for Intercompany Allocations

How can I use social networking to discuss intercompany
allocation adjustments with cost center owners?
Use the social feature on the Intercompany Transactions work area to invite others to share information.
Here's how you use the social feature:
1. Navigate to the Intercompany Transactions work area.

2. Search for the intercompany transaction.
3. Click Social and then click Share. Optionally, click Join to join an existing conversation.
4. Create a related conversation. And invite other cost center owners to join the conversation.
5. Upload the allocation spreadsheet for them to review.
As cost center owners, you can post questions. And other cost center owners can see responses to the questions
because they're owners.
Each cost center owner can validate their intercompany allocation in the conversation itself. This creates a lasting
record.
230
Related Topics
• What does social networking have to do with my job
Intercompany Reconciliation
Generate the Intercompany Reconciliation Report
Use the Reconciliation Report to reconcile your inner company accounts.
Perform the following steps to generate the Intercompany Reconciliation Report:
1. Navigate to the Springboard items from the landing page.

2. Click General Accounting Infolets.
3. On the IC Reconciliation infolet, click Reconcile Intercompany Accounts to start the Extract Intercompany
Reconciliation process.
4. Click Actions and then click Run.
5. Select the value for the report parameters: Provider Ledger, Provider Accounting Period, and Additional
Currency.
Note: Ensure that the entries in the fields Provider Ledger and Provider Accounting Period match the
ledger on the dashboard. The Additional Currency must also match the currency of the ledger on the
dashboard.
6. Select Conversion Rate Type and Conversion Date. These two parameters are enabled after you select the
Additional Currency.
7. Click Submit.
8. Click Refresh until you see the report.
Note: The Period summary report is displayed only after the Extract Intercompany Reconciliation process is
completed.
9. Click Actions drop-down list and select History toview previously run reports in thePeriod Summary. If the
Provider Legal Entity or Receiver Legal Entity is displayed as 'unassigned', it means the primary balancing
segment value on the balancing line isn't assigned to a legal entity.
10. Select an item under Entered Amount Difference in Transaction Currency column to view the Summary by
Source report.
231
11. Review Intercompany Receivables GL Balanceand Intercompany Payables GL Balance in the Summary by
Source report. Identify the roles which have a higher balance and the journal lines that are in one, but may not
be in the other balance.
Note: If there is a difference between the Intercompany receivables and payables amounts, drill down further
on both intercompany receivables and payables amounts to identify the journal lines that appear in one but
not the other.
a. Click the line which appears in one but not the other.
b. On the Journal Lines page, click the journal name to review it and determine if it has been
correctly posted to the intercompany account.
c. If the journal has been posted incorrectly, reverse it so that the Intercompany Receivables GL
Balance and Intercompany Payables GL Balance accounts on Summary by Source report match.
Overview of Intercompany Reconciliation

Intercompany reconciliation provides you with reports to assist you with reconciling your intercompany receivables and
intercompany payables accounts and identifying differences.
The main goal of the reports is to make it easy for you to identify either the receiver side or provider side of a
transaction that has not been posted to the intercompany receivables or intercompany payables account.
The reports show the following intercompany lines:
• Intercompany receivables and intercompany payables lines generated by the intercompany balancing feature.
• Intercompany receivables and intercompany payables lines generated for the provider and receiver of each
intercompany transaction.
The following are not included on the intercompany reconciliation reports:
• Ledger balancing lines generated when the primary balancing segment value is in balance but either the
second balancing segment or the third balancing segment is out of balance
• Clearing company balancing lines
Related Topics
• Intercompany Reconciliation
• Prepare Intercompany Reconciliation Reporting Information
232
Implementing Accounting Hub Consolidations
9 Consolidations
Overview of Consolidation
Select the best consolidation solution for your enterprise:
• Reporting Only Consolidations: If your subsidiaries and corporate ledger share the same chart of accounts
and calendar.
• Balance Transfer Consolidations: If your subsidiaries and corporate ledger have either or both different charts
of accounts and different calendars.
• Financial Management Consolidations: If there are complex factors 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 data sources that are not general ledger that are required to
support nonfinancial or industry-specific metrics, disclosures, and footnote schedules.
Related Topics
• Example of Reporting Only Consolidation Method
• Example of Balance Transfer Consolidation Method:
• Reporting Only or Balance Transfer Consolidation Methods
• Example of Multiple Levels of Reporting Consolidation
• Examples of Elimination Entries
Example of Mapping Segments to Financial

Management Dimensions
When integrating with Oracle Hyperion Financial Management, you can use the following dimensions for consolidation.
Map one to one, or concatenate segments into a single Hyperion Financial Management dimension.
The following figure shows an example of mapping segments in Accounting Hub to dimensions in
Hyperion Financial Management. In this example:Company is mapped to Entity.Department and
Location are concatenated and mapped to Department.Account and Subaccount are concatenated and
233
Implementing Accounting Hub Consolidations
mapped to Account.Product is mapped to Product.Program isn't mapped and its data is summarized.
Note: Data is summarized across segments that aren't mapped to dimensions.
FAQs for Consolidations

How can I secure balance transfer drill down?
The balance transfer drill-down feature is secured with the same privilege that controls the existing account balance
inquiry features. A specific data access set is not required to drill down from the target ledger to the source ledger to
view the balance transfer information. As long as you have read or write access to the target ledger you can drill down to
the source ledger. However, you are limited to just that drill path and cannot see other journals for the target ledger.
234
Implementing Accounting Hub Budget Configuration
10 Budget Configuration
Overview of Budget Configuration

In Oracle General Ledger, you can load budget data to perform variance reporting.
If you use a third-party budgeting application or don't use a budgeting application, there are two ways to load budgets
into the GL Balances Cube.
• Importing Budget Data from a Flat File: Export budget data from your budgeting application to a comma
separated values .csv file. Use the Import General Ledger Budget Balances file-based data import to prepare
and generate flat files in a .csv format. You can use Oracle Application Development Framework Desktop
Integrator correction worksheets to correct validation errors, delete rows with errors, and resubmit the
corrected error rows.
Note: For more information about file-based data import, see the File-Based Data Import for Oracle
Financials Cloud guide.
• Importing Budget Data from a Spreadsheet: You can access the budget load spreadsheet from the General
Accounting Dashboard. Enter, load, and correct budget data in the ADF Desktop Integrator spreadsheet
tool. Use this tool to prepare and load budget data for multiple ledgers and periods with a common chart of
accounts instance. The list of values and the web picker help you select valid values. This simplified data entry
reduces errors and alerts you to errors as you enter the data in the spreadsheet. Error correction is done in the
same spreadsheet.
235
The following figure shows the process flow for budget upload. Prepare your budget
data, upload it using a spreadsheet or flat file, and report on the budget data.
CAUTION: When the GL Balances Cube is rebuilt, the process retains the budget balances as well as the actual
balances. Only the budget balances loaded using the spreadsheet or flat file through the GL Budget Balances
interface table are retained. Create reports in Smart View or Financial Reporting to verify that the budget data was
loaded correctly.
Related Topics
• Import Budget Data from a Spreadsheet
• How General Ledger Budget Balance Import Data Is Processed
• Import Budget Data from a Flat File
• Correct Budget Import Errors Using a Spreadsheet
• Overview of Oracle Hyperion Planning
236
Overview of Integration with Oracle Enterprise Planning

and Budgeting Cloud Service
Integrate with Oracle Enterprise Planning and Budgeting Cloud Service to synchronize your budget and actual amounts
for financial reporting and analysis.
The integration between Oracle Enterprise Planning and Budgeting Cloud Service enables you to:
• Integrate Oracle Fusion General Ledger data with the Oracle Enterprise Performance Management Cloud.
• Automate the import of data into the Oracle EPM Cloud applications.
• Schedule or manually run the integration process after selecting the source ledger from Oracle Fusion General
Ledger and setting up the mappings.
For more information on completing the setup for integration with Oracle Enterprise Planning and Budgeting, Financials
Cloud Service, see the Integrating Financials Cloud with EPM Cloud section in the Administering Data Management for
Oracle Enterprise Performance Management Cloud guide in the Oracle Help Center (http://docs.oracle.com).
237
238
Implementing Accounting Hub Financial Reporting
11 Financial Reporting
Overview of Financial Reporting

The Financial Reporting Center is a powerful tool for reviewing, designing, and presenting financial reports and analytic
data. It adds self-service functionality for the Oracle Fusion Applications and Oracle Accounting Hub. The financial
reports are available immediately on both computers and mobile devices, which leads to quicker decision making.
The Financial Reporting Center is intended to be the primary user interface for financials end users to access all seven
report types.
Related Topics
• Overview of Financial Reporting Center
• Set Up Financial Reporting Center and Smart View
• Considerations for Implementing Financial Reporting Center
• Oracle General Ledger Predefined Reports
• General Ledger Subject Areas, Folders, and Attributes
FAQs for Financial Reporting

How can I apply permissions to objects from Financial Reporting in
Workspace?
Open the Permission dialog box from the Tasks list to set permissions for a catalog object. Permissions determine
which user, group, or role can view, open, or modify the object. If you display this dialog box while working in the catalog
in Workspace, any permission changes that you specify are applied immediately. If you display this dialog box as part of
the Batch Scheduler wizard, then the permission changes are not applied until you run the batch.
How can I migrate Financial Reports from one environment to

another?
You can export your financial reports from a source environment and import them to a target environment using
implementation projects.
Only the financial reports in the /shared/Custom/Financials folder are exported, so make sure to copy all the
financial reports, or the folders containing them, to this folder. In the Setup and Maintenance work area, create an
implementation project that includes only the Create Financial Statements task. Then use the Manage Configuration
Packages task to export and import the reports.
239
Note: For the Financial Reporting report definition migration service, from a source to a target environment,
references to version IDs of dimension members hierarchies are synchronized to their version IDs in the target
environment.
Related Topics
• How You Use Implementation Projects to Manage Setup
• Setup Data Export and Import Using Implementation Project
• Exporting Setup Data Using Implementation Project: Procedure
• Importing Setup Data Using Implementation Project: Procedure
Create a Financial Report

Define a Basic Financial Report Using the Reporting Web Studio
You can use Financial Reporting Web Studio to design traditional financial report formats such as balance sheets, profit
and loss statements, and cash flow reports. You can also design nontraditional reports for financial or analytic data that
include text and graphics.
In this example, you're designing a basic financial report. This is the first of six topics on designing a financial report
with Financial Reporting Web Studio.
1. From the Financial Reporting Center work area, select the Tasks panel tab and click Open Workspace for
Financial Reports.
2. On the Tools menu, select Launch Financial Reporting Web Studio.
3. On the File menu, select New, Report.
4. On the toolbar, click the Grid icon. Grids are tables that contain data from external database connections.
5. In the design canvas, draw a box to create the grid. The Database Connection Properties dialog box opens.
Tip: When creating a grid, best practice is to leave space in the design canvas for other objects, such as a
company logo and report title.
6. Select the Data Sources list and select the data source for the chart of accounts that the report is based on. A
unique cube exists for each combination of chart of accounts and accounting calendar.
Tip: Best practice is to always turn on suppression in financial reports at the Database Connection Server
level. You can verify the setting by highlighting the grid, and then selecting Data Query Optimization
Settings on the Task menu. For most reports, best practice is to turn on suppression for the entire grid. Then
turn suppression off for columns and rows that must always display. For more information about suppression
settings, refer to the Defining Basic Conditional Suppression section in the Financial Reporting Web Studio
User's guide.
7. Click OK. The Dimension Layout dialog box opens.
240
Arrange the Dimensions

Use the Dimension Layout dialog box to arrange the dimensions on your report. For this report, the accounting periods
display on the columns and the revenue and expense account information displays on the rows. The company appears
on each page and can be selected at runtime.
1. Drag the Accounting Period dimension to the Columns axis.

2. Drag the Account dimension to the Rows axis.
3. Drag the Company dimension to the Page axis.
4. Click OK to close the Dimension Layout dialog box.
Define the Rows

Use the Select Members dialog box to define the revenue and expense account rows.
1. Select the revenue parent account.

a. Double-click the Account cell. The Select Members dialog box opens with a default member selected.
b. Remove the default Account selection from the Selected area by clicking it to select it and then clicking
the Remove from Selected icon.
c. In the Search field, enter the value for the account that represents total revenue and click the Search
icon.
d. Select the account from the search results and click OK. The account moves to the Selected area.
e. Click OK. The Select Members dialog box closes.
2. Now insert a text row to add space between the revenue and expense accounts.
a. Select the last row in the grid by clicking the row header.
b. On the Insert menu, select Row, then Text.
3. Insert a row for the expense accounts.
a. Right-click the last row header.
b. On the Insert Row menu, select Data. Notice the default value for the new row is the revenue parent
account.
4. Select the expense parent accounts.
a. Double-click the account value in the new expense account row. The Select Members dialog box opens
with the revenue parent account selected.
b. Remove the revenue parent account selection from the Selected area by clicking to select it and then
clicking the Remove from Selected icon.
c. In the Available area, expand the Account member, and continue expanding until you find the expense
parent accounts for the report.
d. Select the accounts and click the Add to Selected icon to move them to the Selected area.
e. Select the Place selections into separate rows option so each account appears in its own row on the
report.
f. Click OK. The Select Members dialog box closes.
Save and Preview the Report

Save the report and leave it open for the next topic, which is adding a formula to a financial report.
1. Click the Save icon.

2. Select the folder with your name and enter the report name and description.
241
3. Click Save.
4. Optionally preview the report in HTML or PDF format using the File menu or toolbar.
Add Formulas to a Financial Reporting Report

In this example, you define a formula to summarize the expense account balances on your financial report. This is the
second of six topics on designing a financial report with Financial Reporting Web Studio.
Before you start, do the steps described in the Define a Basic Financial Report Using the Reporting Web Studio topic,
then follow these steps.
1. Right-click the last row header, select Insert Row and select Formula.
2. Click in the empty cell in the new row.
3. In the Heading Row Properties pane, select the Custom Heading option, enter Total Expenses and click the
Update icon. The new heading appears in the report.
4. Select the row header for the formula row. The SUM function appears in the design canvas.
5. In the Formula bar, click the Sum(0) button and enter the formula and cell references in the formula text box.
Because the expense rows appear one after the other, you can use the first row number and the last row
number with a colon in between. For example, Sum([3:5]). If the rows weren't contiguous, you could put
brackets around each row number and separate them with commas. For example, Sum([3], [5], [6]).
6. Validate the formula syntax by clicking the check mark icon in the toolbar. Validation checks the validity of the
formula, not if the data is available.
7. Save the report and leave it open for the next topic, which is defining a range function. Optionally preview the
report.
Define Range Functions for a Financial Reporting Report

In this example, you define a range function to report across multiple accounting periods. You configure the range to
present balances for the last 12 months from the period selected at runtime. This is the third of six topics on designing a
financial report with Financial Reporting Web Studio.
Before you start, do the steps described in these topics.

1. Define a Basic Financial Report Using the Reporting Web Studio
2. Add Formulas to a Financial Reporting Report
Now follow these steps.
1. Double-click the Accounting Period cell. The Select Members dialog box opens.
2. Remove the default accounting period from the Selected area by clicking it to select it and then clicking the
Remove from Selected icon.
3. Click the Functions tab.
4. Select Range from the list.
5. Click the Add to Selected icon. The Range dialog box opens.
6. Define the starting member for the range.
a. On the Start Member row, click the Lookup Selection icon in the Value column.
b. Click the Functions tab.
242
c. Select the Relative Member function to define the periods that display on the report relative to the
period specified at runtime.
d. Click OK. The Relative Member dialog box opens.
e. On the Member row, click the Lookup Selection icon in the Value column.
f. Select Current Point of View for Accounting Period so you can enter the starting period for the report.
g. Click OK.
h. On the Offset row, enter -11 in the Value field.
The offset determines the first period of the range. The starting period in the range function is always
the oldest period. Because this is a rolling 12 period report, enter -11 to include the 11 periods prior to the
period you enter at runtime. The member selection for the End Member parameter determines period 12.
i. Click OK.
7. Define the ending member for the range.
a. On the End Member row, click the Lookup Selection icon in the Value column.
b. Select Current Point of View for Accounting Period.
c. Click OK.
d. Click OK to close the Range dialog box.
e. Click OK to close the Select Members dialog box.
8. Save the report and leave it open for the next topic, which is defining a grid point of view. Optionally preview
the report.
Set User and Grid Points of View for a Financial Reporting Report
In this example, you set a user point of view and a grid point of view for a financial report. This is the fourth of six topics
on designing a financial report with Financial Reporting Web Studio.
All financial reporting reports have a user point of view and a grid point of view. Best practice is to use a combination of
both.
If you want users to select certain dimension members at runtime, then those dimensions should be set in the
user point of view. Selections for user point of view members are global for a user and data source. This means the
application saves and applies them to any other report that has the same dimensions set to the user point of view. By
default, all dimensions are set to the user point of view and must be selected at runtime. If you want your report to
always use certain dimension selections, then select the specific members in the grid point of view.
Note: Members of a grid point of view only display in HTML.
In this example you set the Ledger, Scenario, Balance Amount and Currency dimensions to use the grid point of view.

3. Define Range Functions for a Financial Reporting Report
1. Select the cell in the grid that represents the intersection of the rows and columns. The Grid Properties pane
opens.
2. In the Grid Properties pane, click the Grid Point of View check box.
243
3. In the design canvas, click the Ledger: User Point of View for Ledger button. The Select Members dialog box
opens.
4. Expand the Ledger member and continue to expand until you find the ledger to include on the report. Select
the ledger.
5. Click Apply Selection.
6. Select Scenario from the Dimension list to select the type of balance to use on the report.
7. Expand the Scenario member and select Actual.
9. Select Balance Amount from the Dimension list.
10. Expand the Balance Amount member and select Period Activity.
12. Select Currency from the Dimension list.
13. Search for USD.
14. Click OK to accept the search result.
16. Click OK to close the Select Members dialog box.
17. Save the report and leave it open for the next topic, which is setting page and grid properties. Optionally,
preview the report.
Work with Grid Point of View Setup and Page Axis for a Financial
Reporting Report
In this example, you change the grid point of view setup and set the page member selection to a prompt on your
financial report. This is the fifth of six topics on designing a financial report with Financial Reporting Web Studio.
Before you start, do the tasks described in these topics.

4. Set User and Grid Points of View for a Financial Reporting Report
1. Click the first cell in the grid to select all of the rows and columns.
2. Right-click and select Grid Point of View Setup from the list. The Setup Grid Point of View dialog box opens.
a. To prevent the Balance Amount dimension from being changed at runtime, select the Lock Member
Selection option.
b. Click OK. The Setup Grid Point of View window closes.
3. In the Grid Properties pane:
a. Click the Drill Through option to allow drilling from the report to the General Ledger transaction data.
b. Click the Suppression section to view the suppression settings.
c. Enter 0 in the Zero Values field to set the text option for rows with zero values. If necessary, you could
also suppress the display of rows with zero values, rows with missing data, and rows with errors.
4. Set a runtime prompt for the Company dimension so you have the flexibility of selecting any company or
combination of companies at runtime. In this example, you want to restrict the valid list of companies that can
be selected at runtime.
a. On the grid, click the Pages label. The Company dimension appears in the design canvas.
244
b. Click the Company button. The Select Members dialog box opens.
c. Remove the default Company selection from the Selected area by clicking it to select it and then clicking
d. Select Prompt for Company.
e. Click the Add to Selected icon to move the selection to the Selected area.
f. Click OK. The Define Prompts dialog box opens.
g. Click the Lookup icon in the Choices List field. The Select Members dialog box opens.
h. Remove the default Company selection from the Selected area by clicking it to select it and then clicking
i. Expand the Company member, and continue expanding until you find and select the default companies
you want to display in the prompt.
j. Click the Add to Selected icon to move the companies to the Selected area.
k. Click OK. The Select Members window closes.
l. On the Define Prompts dialog box, click in the Member Name field and select Alias. The actual company
label displays in the prompt list of values instead of a numeric company value, making the prompt more
user-friendly.
m. Click OK. The Define Prompts window closes.
5. Click the Pages label on the grid. The Page Properties pane opens.
a. In the Page Properties pane, select the Alias: Default option so each page of the report shows the name
of the company instead of the number.
6. Select the four data rows in the grid so all of the rows have the same settings.
a. In the Heading Row Properties pane, select the Alias: Default option in the Heading Row Properties pane
to display the revenue and expense account names instead of the accounts.
b. In the Heading Row Properties pane, select the Allow Expansion option so you can expand the parent
account values to view the detail child values.
7. Save the report and leave it open for the next topic, which is formatting your financial report and adding a
graph. Optionally, preview the report.
Add Formats and Graphs to a Financial Reporting Report

In this example, you add formats and graphs to a financial report. This is the sixth and final topic in a series of topics on
designing a financial report with Financial Reporting Web Studio.

4. Set User and Grid Points of View for a Financial Reporting Report
5. Work with Grid Point of View Setup and Page Axis for a Financial Reporting Report
1. In the report object browser, select the name of the report, which is the first object.
2. Add a logo.
a. In the report layout, drag the header line to make space for the logo and title.
b. In the Header section, click the Add Report Object icon and select Image.
245
c. In the Image Properties pane, click Browse and select your company logo.
3. Add a title.
a. Select the name of the report in the report object browser.

b. In the Header section, click the Add Report Object and select Text. As an alternative, you can click the
Text icon in the toolbar and draw the text box. The text box opens.
c. Enter the report title.
d. Select the title text and use the format toolbar to adjust the font size, center the text, and change the font
style to bold.
4. Change the page orientation.
a. Select the name of the report in the report object browser.

b. On the File, menu, select Page Setup.
c. In the Page Setup dialog box, select the Landscape option.
d. Click OK.
5. Add a chart.
a. In the Body section, click the Add Report Object icon and select Chart.
b. In the Chart Properties pane, select the Line chart type.
c. To show only the expense account rows, deselect row 1, and select rows 3, 4, and 5 in the Data Range
section.
d. Click the Format Chart button. The Format Chart dialog box opens.
e. In the Appearance tab, enter the title for the chart. For example, Expenses by Period.
f. Click the Legend tab and enter a title for the legend. For example, Type of Expenses.
g. Click the Axes tab and enter a title for the Metadata axis. For example, Period. Enter a title for the
Primary Axis. For example, Dollars.
h. Click the Refresh Chart button to preview the chart on the Format Chart dialog box.
i. Click OK. The Format Chart dialog box closes.
6. Save the report and optionally, preview it.
For more information about Financial Reporting Web Studio, select the Using EPM with Oracle Financials Cloud link
from the All Books for Oracle Financials Cloud page of the Oracle Help Center at https://docs.oracle.com.
246
Implementing Accounting Hub Extensions for Oracle Accounting Hub
12 Extensions for Oracle Accounting Hub
Enterprise Scheduler Jobs for Oracle Accounting Hub

Overview of Managing Job Definitions and Job Sets
Users run scheduled processes based on jobs to process data and, in some cases, to provide report output. Each job has
a job definition which, for example, determines the parameters that users can set. Jobs are based on Oracle Enterprise
Scheduler Services. Using Enterprise Scheduler Jobs tasks, you can define job definitions, list of values sources, and job
sets.
• Job Definitions: Contain the metadata about the job and the options available to users. A job definition is
defined by a job type, such as Oracle Analytics Publisher or PL/SQL Job type or others.
• List of Values Sources: Determine where a list of values for the parameters in a job definition comes from and
what the specific values are.
• Job Sets: Collections of several jobs in a single process set that the users submit instead of running separate
jobs.
The various Enterprise Scheduler Jobs tasks are:
• Manage Enterprise Scheduler Job Definitions and Job Sets for Financial, Supply Chain Management, and
Related Applications
• Manage Enterprise Scheduler Job Definitions and Job Sets for Human Capital Management and Related
Applications
• Manage Enterprise Scheduler Job Definitions and Job Sets for Customer Relationship Management and
Related Applications
In the Setup and Maintenance work area, you can find these tasks in the Application Extensions functional area, or,
depending on your offering, another functional area. If you don't see the task, make sure that the Enterprise Scheduler
Job Definitions and Job Sets feature is enabled at the offering level in the Offerings work area.
Related Topics
• Manage List of Values Sources
• Job Definitions
• Job Sets
• Overview of Scheduled Processes
• Configure Offerings
Manage List of Values Sources

A list of values source for job definitions determines where a list of values comes from and what the specific values
are. Users can select from the list when they set parameters. For example, the list of values for a Country parameter
gives users a list of countries to choose from. You can create list of values sources to use in job definitions that you
247
or someone else created. Parameters in predefined job definitions can have lists of values too, but not from list of
values sources that you can manage. But if you duplicate a predefined job definition, list of values sources might
be automatically created for your new job definition. You can manage those sources as you would a source that you
created yourself.
Here's how you get started to create, edit, or delete list of values sources:
1. In the Setup and Maintenance work area, go to the Manage Enterprise Scheduler Job Definitions and Job
Sets task in the Application Extensions functional area. Or, depending on your offering, you might use a
different functional area.
Note: If you don't see the task, make sure that the Enterprise Scheduler Job Definitions and Job Sets feature
is enabled at the offering level.
2. Click the Manage List of Values Sources tab. If you don’t see anything here, that just means you haven’t created
any sources or duplicated any predefined job definitions that would result in automatically creating list of
values sources.
3. Go on to create or edit list of values sources.
Create List of Values Source

Create a source based on predefined view objects or your own SQL query. For predefined view objects, contact your
help desk to find out if there are any that meet your needs. And to get the view object's full path, which you enter when
creating the list of values source.
1. On the Manage List of Values Sources tab, click the Create icon.
2. In the Create List of Values Source dialog box, select something from the Application Name list that's related
to your list of values. If you don't know what to select or can't find anything that applies, just select Application
Toolkit.
3. In the User List of Values Source Name field, enter a name that helps you identify your list of values source.
4. From the LOVType list, select Predefined to use a view object or User Defined to use a SQL query.
5. If you selected Predefined, then in the List of Values Source Definition Name field, enter the full path of the
view object that your help desk provided.
If you selected User Defined, enter your own SQL in the Query field.
◦ Your query can't have any aggregate function like DISTINCT, SUM, MAX, or AVG in the direct select
clause. It can't have UNION, UNION ALL, INTERSECT, or MINUS either.
◦ If you absolutely need to use any of those functions, you need to wrap the query in another select clause.
Here are a couple examples:
Don't Use This Use This Instead
SELECT DISTINCT SELECT MEANING FROM (SELECT DISTINCT MEANING MEANING FROM FND_
CHANNEL.MEANING MEANING FROM LOOKUP_VALUES_TL);
FND_LOOKUP_VALUES_TL
select lookup_code as SELECT LOOKUPCODE FROM (select lookup_code as LookupCode from fnd_
LookupCode from fnd_lookup_ lookup_values_b where lookup_type='EXM_REPORT_STATUS' UNION select
values_b where lookup_ 'NULL' as LookupCode from dual)
type='EXM_REPORT_STATUS'
UNION select 'NULL' as
LookupCode from dual
248
Don't Use This Use This Instead
6. Make sure everything looks fine and then click Save and Close. You can't change most of the things about your
source after you create it.
Edit or Delete List of Values Source

Here are some things to know about editing and deleting list of values sources, which you can do on the Manage List of
Values Sources tab.
• You can edit only the application name and description.

• When you delete a list of values source, you can't find it and manage it any more, but it's not really gone. Any
job definitions using that source can continue using it. So after you delete a source, you can't create another
one later with the same name, even though you won't be able to find the deleted one. To avoid confusion, it's
recommended that you don't ever delete any list of values source. Just create new ones as needed, with unique
names.
Related Topics
• Configure Offerings
249
250

Implementing Accounting Hub

Uploaded by

Copyright:

Available Formats

Implementing Accounting Hub

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

Implementing Accounting Hub

Uploaded by

Copyright:

Available Formats

What are some restrictions on using the software?

What are some restrictions on using the software?

How can list of values sources be created or edited?

How can list of values sources be created or edited?

Oracle Financials

Implementing Accounting Hub

Copyright © 2011,2022, Oracle and/or its affiliates.

Authors: Vinetta Kumar

Get Help ................................................................................................................................ i

1 Introduction to Oracle Accounting Hub Cloud 1

2 Enterprise Structures for Oracle Accounting Hub 15

3 Financial Reporting Structures 21

Cross-Validation Rules ................................................................................................................................................................. 32

5 Period Close Components 71

FAQs for Allocation Rules ........................................................................................................................................................... 82

7 Subledger Accounting 163

8 Intercompany Processing Rules 229

10 Budget Configuration 235

11 Financial Reporting 239

12 Extensions for Oracle Accounting Hub 247

Join Our Community

Learn About Accessibility

Share Your Feedback

You can email your feedback to [email protected].

Thanks for helping us improve our user assistance!

1 Introduction to Oracle Accounting Hub Cloud

Overview of Define Oracle Fusion Accounting Hub

The rapid implementation task list includes tasks that are:

• Critical setup tasks.

Task List Description

Create an Oracle Accounting Hub Cloud Rapid

This table contains a summarization of key decisions.

Decision to Consider In This Example

Are the set-up requirements unique to this No

Can the rapid implementation task Yes

Creating the Implementation Project

Overview of Oracle Accounting Hub Cloud Features

• Oracle Financial Reporting that provides:

How Oracle Accounting Hub Cloud Works

The Oracle Accounting Hub Cloud Components

• Accounting transformation to transform external source data.

This figure illustrates the Oracle Accounting Hub Cloud components.

Oracle Accounting Hub Cloud for External Source Systems

• Configurable accounting rules to define accounting treatments for transactions.

Oracle General Ledger

Financial Reporting Center

• Financial Reporting to generate your reports.

Overview of Accounting Configuration Offerings

The financial applications have two predefined implementations:

Overview of Implementation Options for Oracle

Accounting for Diverse Transactions

Expansion of Financial Reporting

• Predefined financial reports

Setup Data Import and Export for Oracle Accounting

Setup Tasks Performed Before Export

This table contains setup tasks performed before export.

Activity Name Task Name Setup Steps

Activity Name Task Name Setup Steps

to the Manage Chart of Accounts Instance