Cloud General Ledger Book PDF

Oracle
Financials Cloud
Implementing Enterprise Structures
and General Ledger
Release 13 (update 17B)

Oracle Financials Cloud
Implementing Enterprise Structures and General Ledger
Release 13 (update 17B)

Part Number E84479-03
Copyright 2011-2017, Oracle and/or its affiliates. All rights reserved.
Authors: Kathryn Wohnoutka, Barbara Kostelec
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 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, then 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.
The business names used in this documentation are fictitious, and are not intended to identify any real companies currently or previously in existence.
Oracle customers that have purchased support have access to electronic support through My Oracle Support. For information, visit http://www.oracle.com/
pls/topic/lookup?ctx=acc&id=info or visit http://www.oracle.com/pls/topic/lookup?ctx=acc&id=trs if you are hearing impaired.
Contents
Preface i
1 Enterprise Structures Introduction 1

Enterprise Structures: Overview ................................................................................................................................ 1
Enterprise Structures Business Process Model: Explained ........................................................................................ 3
Global Enterprise Configuration: Points to Consider .................................................................................................. 5
Modeling Your Enterprise Management Structure in Oracle Fusion: Example ............................................................ 6
Running Diagnostic Tests for Enterprise Structures Setup Data: Explained .............................................................. 10
Enterprise Structures Setup Report: Explained ........................................................................................................ 10
Setup Data Import and Export for Oracle Fusion Financials: Explained .................................................................... 11
Natural Languages: Points to Consider ................................................................................................................... 17
Initial Configuration .................................................................................................................................................. 17
Social Networks ...................................................................................................................................................... 22
2 Reference Data Sharing 29

Reference Data Sharing: Explained ......................................................................................................................... 29
Reference Data Sets: Explained .............................................................................................................................. 29
Reference Data Sets and Sharing Methods: Explained ........................................................................................... 30
Business Units and Reference Data Sets: How They Work Together ...................................................................... 31
Creating Reference Data Sets in the Enterprise Structures Configurator: Explained ................................................. 34
Assigning Reference Data Sets to Reference Objects: Points to Consider ............................................................... 34
Items and Supplier Site Reference Data Sharing: Explained .................................................................................... 35
FAQs for Reference Data Sharing ........................................................................................................................... 36
3 Enterprise 41
Enterprise: Explained ............................................................................................................................................... 41
Managing Enterprise Information for Non-HCM Users: Explained ............................................................................ 41
Manage Locations .................................................................................................................................................. 41
Legal Jurisdictions and Authorities .......................................................................................................................... 43
Define Lookups ....................................................................................................................................................... 48
Manage Descriptive Flexfields ................................................................................................................................. 55
Define Profile Options ............................................................................................................................................. 64
4 Geographies 69
Define Geographies: Overview ................................................................................................................................ 69
5 Legal Entities 71
Legal Entities: Explained ......................................................................................................................................... 71
Legal Entity in Oracle Fusion: Points to Consider .................................................................................................... 72
Creating Legal Entities in the Enterprise Structures Configurator: Points to Consider ............................................... 74
Creating Legal Entities, Registrations, and Reporting Units: Examples ..................................................................... 76
Manage Legal Entity HCM Information .................................................................................................................... 78
Manage Legal Entity Tax Profile .............................................................................................................................. 85
Define Legal Reporting Units ................................................................................................................................... 88
6 Financial Structures 91
Rapid Implementation ............................................................................................................................................. 91
Chart of Accounts ................................................................................................................................................. 108
Value Sets ............................................................................................................................................................. 121
Chart of Accounts Structures and Instances ......................................................................................................... 126
Flexfield Deployment ............................................................................................................................................. 133
General Ledger Security ........................................................................................................................................ 144
Cross-Validation Rules .......................................................................................................................................... 167
FAQs for Chart of Accounts Mappings ................................................................................................................. 177
Account Hierarchies .............................................................................................................................................. 177
Account Combinations .......................................................................................................................................... 199
Accounting Calendars ........................................................................................................................................... 202
Currencies ............................................................................................................................................................. 206
Conversion Rate Types ......................................................................................................................................... 207
Daily Rates ............................................................................................................................................................ 210
7 Ledgers 217
Accounting Configuration Offerings: Overview ....................................................................................................... 217
Ledgers and Subledgers: Explained ...................................................................................................................... 217
Ledgers: Points to Consider ................................................................................................................................. 218
Financial Ledgers: How They Fit Together ............................................................................................................ 221
Creating Primary Ledgers: Example ...................................................................................................................... 224
Ledger Options ..................................................................................................................................................... 225
Assign Access to Ledger ...................................................................................................................................... 228
Reporting Currencies ............................................................................................................................................ 230
Review and Submit Accounting Configuration ....................................................................................................... 232
Opening First Period: Overview ............................................................................................................................. 251
Clearing Accounts Reconciliation: Overview .......................................................................................................... 251
Setting Up Clearing Accounts Reconciliation: Procedure ....................................................................................... 253
Reconciliation Types: Explained ............................................................................................................................ 253
Tolerances and Manual Clearing Accounts Reconciliation: How It Works .............................................................. 256
8 Intercompany Setup 259

Manage Intercompany System Options ................................................................................................................ 259
Manage Intercompany Organizations .................................................................................................................... 261
Define Invoicing Options ....................................................................................................................................... 261
Manage Intercompany Balancing Rules ................................................................................................................ 262
Manage Intercompany Allocations ......................................................................................................................... 277
Intercompany Organization Configuration Examples .............................................................................................. 288
9 General Ledger Options 297

Ledger Sets: Examples ......................................................................................................................................... 297
Data Access Set Security: Overview ..................................................................................................................... 297
Data Access Set Security: Examples .................................................................................................................... 298
Manage Accounting and Reporting Sequences .................................................................................................... 299
Manage Journal Approval Rules ............................................................................................................................ 307
Manage AutoPost Criteria Sets ............................................................................................................................. 312
Manage Journal Reversal Criteria Sets .................................................................................................................. 314
Define Lookups ..................................................................................................................................................... 317
Manage Descriptive Flexfields ............................................................................................................................... 324
Define Profile Options ........................................................................................................................................... 333
10 Period Close 337

Close Monitor: Overview ....................................................................................................................................... 337
Configuring Social Objects in Oracle Social Network: Explained ............................................................................ 339
Period Close Components: Explained ................................................................................................................... 339
FAQs for Period Close .......................................................................................................................................... 340
Manage Allocations and Periodic Entries .............................................................................................................. 341
Define Allocation Rules ......................................................................................................................................... 358
Define Allocation Rule Sets ................................................................................................................................... 370
Working with Point of View and Allocation Components ....................................................................................... 379
Use Allocation Variables ........................................................................................................................................ 390
Generating Allocations and Periodic Entries Manually: Worked Example ................................................................ 398
Manage Revaluations ............................................................................................................................................ 399
11 Business Units 405

Business Units: Explained ..................................................................................................................................... 405
Business Functions: Explained .............................................................................................................................. 406
Creating Business Units in the Enterprise Structures Configurator: Points to Consider ........................................... 408
Copying Business Unit Configurations: Procedure ................................................................................................ 411
Override Business Unit Account Segment Values: Examples ................................................................................. 413
FAQs for Business Units ....................................................................................................................................... 415
Manage Service Provider Relationships ................................................................................................................. 416
Business Function Properties ................................................................................................................................ 419
12 Workforce Structures and Facilities 423

Managing Enterprise Information for Non-HCM Users: Explained .......................................................................... 423
Manage Divisions .................................................................................................................................................. 423
Manage Departments ............................................................................................................................................ 426
Manage Jobs ........................................................................................................................................................ 428
Manage Facility Shifts, Workday Patterns, and Schedules .................................................................................... 437
Manage Inventory Organizations ........................................................................................................................... 440
Manage Item Organizations .................................................................................................................................. 445
13 Hyperion Financial Management Integration 449

Oracle Hyperion Financial Management: Overview ................................................................................................ 449
Integration with Hyperion Financial Management: Overview ................................................................................... 450
14 Budget Configuration 451

Budget Uploads: Overview .................................................................................................................................... 451
Importing Budget Data from a Flat File: Explained ................................................................................................ 452
Loading Data to the Budget Interface Table: Explained ......................................................................................... 454
Importing Budget Data from a Spreadsheet: Explained ......................................................................................... 455
Budget Correction with Oracle ADF Desktop Integrator: Explained ........................................................................ 457
Oracle Hyperion Planning: Overview ..................................................................................................................... 458
Integration with Oracle Enterprise Planning and Budgeting Cloud Service: Overview ............................................. 459
15 Financial Reporting 461

Financial Reporting Center Implementation: Points to Consider ............................................................................. 461
Financial Reporting Center: How It Works ............................................................................................................. 461
Setting Up Your Financial Reporting Center: Critical Choices ................................................................................ 464
Managing Financial Reporting Studio Versions: Explained ..................................................................................... 467
Create Financial Statements: Explained ................................................................................................................ 471
Configuring an Account Group: Example .............................................................................................................. 490
Migrating Financial Reports: Instructions ............................................................................................................... 492
General Ledger Subject Areas, Folders, and Attributes: Explained ........................................................................ 493
Define Transactional Business Intelligence Configuration: Overview ....................................................................... 496
FAQs for Financial Reporting ................................................................................................................................ 497
Oracle Financials Cloud Preface
Preface
This preface introduces information sources that can help you use the application.
Oracle Applications Help

Use the help icon to access Oracle Applications Help in the application. If you don't see any help icons on your page,
click the Show Help icon in the global header. Not all pages have help icons. You can also access Oracle Applications
Help at https://fusionhelp.oracle.com.
Using Applications Help

Watch: This video tutorial shows you how to find help and use help features.

Additional Resources
Community: Use Oracle Applications Customer Connect to get information from experts at Oracle, the
partner community, and other users.
Guides and Videos: Go to the Oracle Help Center to find guides and videos.
Training: Take courses on Oracle Cloud from Oracle University .
Documentation Accessibility
For information about Oracle's commitment to accessibility, visit the Oracle Accessibility Program website at Oracle
Accessibility Program .
Access to Oracle Support

Oracle customers that have purchased support have access to electronic support through My Oracle Support. For
information, visit http://www.oracle.com/pls/topic/lookup?ctx=acc&id=info or visit http://www.oracle.com/pls/topic/lookup?
ctx=acc&id=trs if you are hearing impaired.
Comments and Suggestions

Please give us feedback about Oracle Applications Help and guides! You can send e-mail to:
oracle_fusion_applications_help_ww_grp@oracle.com.
i
Oracle Financials Cloud Preface
ii
Oracle Financials Cloud Chapter 1
Implementing Enterprise Structures and General Ledger Enterprise Structures Introduction
1 Enterprise Structures Introduction
Enterprise Structures: Overview

Oracle Fusion Applications have been designed to ensure your enterprise can be modeled to meet legal and management
objectives. The decisions about your implementation of Oracle Fusion 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
In Oracle Fusion, these structures are implemented using the chart of accounts and organization hierarchies. Many alternative
hierarchies can be implemented and used for reporting. You are likely to have one primary structure that organizes your
business into:
Divisions
Business Units
Departments
1
Aligned these structures with your strategic objectives.
Legal Structure
The figure above shows a typical group of legal entities, operating various business and functional organizations. Your ability
to buy and sell, own, and employ comes from your charter in the legal system. A corporation is:
A distinct legal entity from its owners and managers.

Owned by its shareholders, who may be individuals or other corporations.
Many other kinds of legal entities exist, such as sole proprietorships, partnerships, and government agencies.
A legally recognized entity can own and trade assets and employ people in the jurisdiction in which the entity is registered.
When granted these privileges, legal entities are also assigned responsibilities to:
Account for themselves to the public through statutory and external reporting.
Comply with legislation and regulations.
Pay income and transaction taxes.
Process value added tax (VAT) collection on behalf of the taxing authority.
Many large enterprises isolate risk and optimize taxes by incorporating subsidiaries. They create legal entities to facilitate legal
compliance, segregate operations, optimize taxes, complete contractual relationships, and isolate risk. Enterprises use legal
entities to establish their enterprise's identity under the laws of each country in which their enterprise operates.
In the figure above:
A separate card represents a series of registered companies.

Each company, including the public holding company, InFusion America, must be registered in the countries where
they do business.
2
Each company contributes to various divisions created for purposes of management reporting. These are shown as
vertical columns on each card.
For example, a group might have a separate company for each business in the United States (US), but have its United
Kingdom (UK) legal entity represent all businesses in that country.
The divisions are linked across the cards so that a business can appear on some or all of the cards. For example, the air
quality monitoring systems business might be operated by the US, UK, and France companies. The list of business divisions
is on the Business Axis.
Each company's card is also horizontally striped by functional groups, such as the sales team and the finance team. This
functional list is called the Functional Axis. The overall image suggests that information might, at a minimum, be tracked
by company, business, division, and function in a group environment. In Oracle Fusion Applications, the legal structure is
implemented using legal entities.
Management Structure
Successfully managing multiple businesses requires that you segregate them by their strategic objectives, and measure their
results. Although related to your legal structure, the business organizational hierarchies do not have to be reflected directly in
the legal structure of the enterprise. The management structure can include divisions, subdivisions, lines of business, strategic
business units, profit, and cost centers. In the figure above, the management structure is shown on the Business Axis. In
Oracle Fusion Applications, the management structure is implemented using divisions and business units as well as being
reflected in the chart of accounts.
Functional Structure
Straddling the legal and business organizations is a functional organization structured around people and their competencies.
For example, sales, manufacturing, and service teams are functional organizations. This functional structure is represented
by the Functional Axis in the figure above. You reflect the efforts and expenses of your functional organizations directly on the
income statement. Organizations must manage and report revenues, cost of sales, and functional expenses such as research
and development and selling, general, and administrative expenses. In Oracle Fusion Applications, the functional structure is
implemented using departments and organizations, including sales, marketing, project, cost, and inventory organizations.
Enterprise Structures Business Process Model: Explained

In Oracle Fusion Applications, the Enterprise Performance and Planning Business Process Model illustrates the major
implementation tasks that you perform to create your enterprise structures. This process includes:
Set Up Enterprise Structures business process, which consists of implementation activities that span many product
families.
Information Technology, a second Business Process Model which contains the Set Up Information Technology
Management business process.
Define Reference Data Sharing, which is one of the activities in this business process and is important in the
implementation of the enterprise structures. This activity creates the mechanism to share reference data sets across
multiple ledgers, business units, and warehouses, reducing the administrative burden and decreasing the time to
implement.
3
The following figure and tablet describe the Business Process Model structures and activities.
Business Process Model (BPM)
Activities
Define Enterprise
Define Enterprise Structures

Enterprise Planning and
Performance Management Define Legal Jurisdictions and Authorities
Define Legal Entities
Set Up Enterprise Define Business Units

Structures
Define Financial Reporting Structures
Define Chart of Accounts
Define Ledgers
Define Accounting Configurations
Define Facilities
Information Technology
Set Up Information
Define Reference Data Sharing
Technology Management
The table describes each BPM activity.
BPM Activities Description
Define Enterprise Define the enterprise to get the name of the deploying enterprise and the location of the
headquarters.

Define Enterprise Structures Define enterprise structures to represent an organization with one or more legal entities under
common control. Define organizations to represent each area of business within the enterprise.

4
BPM Activities Description
Define Legal Jurisdictions and Define information for governing bodies that operate within a jurisdiction.
Authorities

Define Legal Entities Define legal entities and legal reporting units for business activities handled by the Oracle Fusion
Applications.

Define Business Units Define business units of an enterprise to perform one or many business functions that can be rolled
up in a management hierarchy. A business unit can process transactions on behalf of many legal
entities. Normally, it has a manager, strategic objectives, a level of autonomy, and responsibility for
its profit and loss.

Define Financial Reporting Structures Define financial reporting structures, including organization structures, charts of accounts,
organizational hierarchies, calendars, currencies and rates, ledgers, and document sequences
which are used in organizing the financial data of a company.

Define Chart of Accounts Define chart of accounts including hierarchies and values to enable tracking of financial transactions
and reporting at legal entity, cost center, account, and other segment levels.

Define Ledgers Define the primary accounting ledger and any secondary ledgers that provide an alternative
accounting representation of the financial data.

Define Accounting Configurations Define the accounting configuration that serves as a framework for how financial records are
maintained for an organization.

Define Facilities Define your manufacturing and storage facilities as Inventory Organizations if Oracle Fusion tracks
inventory balances there and Item Organizations if Oracle Fusion only tracks the items used in the
facility but not the balances.

Define Reference Data Sharing Define how reference data in the applications is partitioned and shared.

Note: Some product-specific implementation activities are not listed here and depend on the applications
you are implementing. For example, you can implement Define Enterprise Structures for Human Capital
Management, Project Management, and Sales Management.
Global Enterprise Configuration: Points to Consider

Start your global enterprise structure configuration by discussing what your organization's reporting needs are and how to
represent those needs in the Oracle Fusion Applications. The following are some questions and points to consider as you
design your global enterprise structure in Oracle Fusion.
Enterprise Configuration
Business Unit Management
Security Structure
Compliance Requirements
5
Enterprise Configuration
What is the level of configuration needed to achieve the reporting and accounting requirements?
What components of your enterprise do you need to report on separately?
Which components can be represented by building a hierarchy of values to provide reporting at both detail and
summary levels?
Where are you on the spectrum of centralization versus decentralization?
Business Unit Management

What reporting do I need by business unit?
How can you set up your departments or business unit accounts to achieve departmental hierarchies that report
accurately on your lines of business?
What reporting do you need to support the managers of your business units, and the executives who measure
them?
How often are business unit results aggregated?
What level of reporting detail is required across business units?
Security Structure
What level of security and access is allowed?
Are business unit managers and the people that report to them secured to transactions within their own business
unit?
Are the transactions for their business unit largely performed by a corporate department or shared service center?
Compliance Requirements
How do you comply with your corporate external reporting requirements and local statutory reporting requirements?
Do you tend to prefer a corporate first or an autonomous local approach?
Where are you on a spectrum of centralization, very centralized or decentralized?
Modeling Your Enterprise Management Structure in Oracle

Fusion: Example
This example uses a fictitious global company to demonstrate the analysis that can occur during the enterprise structure
configuration planning process.
6
Scenario
Your company, InFusion Corporation, is a multinational conglomerate that operates in the United States (US) and the United
Kingdom (UK). InFusion has purchased an Oracle Fusion Enterprise Resource Planning (ERP) solution including Oracle Fusion
General Ledger and all of the Oracle Fusion subledgers. You are chairing a committee to discuss creation of a model for your
global enterprise structure including both your US and UK operations.
InFusion Corporation
InFusion Corporation has 400 plus employees and revenue of 120 million US dollars. Your product line includes all the
components to build and maintain air quality monitoring (AQM) applications for homes and businesses. You have two
distribution centers and three warehouses that share a common item master in the US and UK. Your financial services
organization provides funding to your customers for the initial costs of these applications.
Analysis
The following are elements you must consider in creating your model for your global enterprise structure.
Your company is required to report using US Generally Accepted Accounting Principles (GAAP) standards and UK
Statements of Standard Accounting Practice and Financial Reporting Standards. How many ledgers do you want to
achieve proper statutory reporting?
Your managers need reports that show profit and loss (revenue and expenses) for their lines of business. Do you
use business units and balancing segments to represent your divisions and businesses? Do you secure data by two
segments in your chart of accounts which represents each department and legal entity? Or do you use one segment
that represents both to produce useful, but confidential management reports?
Your corporate management requires reports showing total organizational performance with drill-down capability to
the supporting details. Do you need multiple balancing segment hierarchies to achieve proper rollup of balances for
reporting requirements?
Your company has all administrative, account payables, procurement, and Human Resources functions performed at
their corporate headquarters. Do you need one or more business units in which to perform all these functions? How
is your shared service center configured?
Global Enterprise Structure Model

The following figure and table summarize the model that your committee has designed and uses numeric values to provide a
sample representation of your structure. The model includes the following recommendations:
Creation of three separate ledgers representing your separate legal entities:
InFusion America Inc.

InFusion Financial Services Inc.
InFusion UK Services Ltd.
7
Consolidation of results for application components, installations, and maintenance product lines across the
enterprise
All UK general and administrative costs processed at the UK headquarters
US Systems' general and administrative costs processed at US Corporate headquarters
US Financial Services maintains its own payables and receivables departments
InFusion United States InFusion United Kingdom

(US) Division (UK) Division
InFusion Financial
InFusion UK Systems Ltd.
Services Inc.
InFusion America Inc. Primary Ledger (GBP)
Primary Ledger
Primary Ledger (USD) with Reporting Currency
(USD)
Standard, Jan - Dec (USD)
Average Balancing
Standard, Jan - Dec
May-April
BU 1 BU 2 BU 3
US Systems Fin Services UK Systems
BU 4
Corporate Administration, Procurement, and HR Shared Services Center
US LE 2 UK LE 4
US LE 1 US LE 3
Bal Seg 201, Bal Seg 103, 301,
Bal Seg 101 Bal Seg 102
202, 203 302, 303
US Distribution UK Distribution
Center Center
US Warehouse US Warehouse UK Warehouse

West East
Common Item
Master
8
In this chart, the green globe stands for required and gold globe stands for optional setup. The following statements expand
on the data in the chart.
The enterprise is required because it serves as an umbrella for the entire implementation. All organizations are
created within an enterprise.
Legal entities are also required. They can be optionally mapped to balancing segment values or represented
by ledgers. Mapping balancing segment values to legal entities is required if you plan to use the intercompany
functionality. The InFusion Corporation is a legal entity but is not discussed in this example.
At least one ledger is required in an implementation in which you record your accounting transactions.
Business units are also required because financial transactions are processed in business units.
A shared service center is optional, but if used, must be a business unit.
Divisions are optional and can be represented with a hierarchy of cost centers or by a second balancing segment
value.
Departments are required because they track your employees.
Optionally, add an item master organization and inventory organizations if you are tracking your inventory
transactions in Oracle Fusion Applications.
9
Note: Some Oracle Fusion Human Capital Management and Oracle Sales Cloud implementations do not
require recording accounting transactions and therefore, do not require a ledger.
Running Diagnostic Tests for Enterprise Structures Setup

Data: Explained
You can run diagnostic tests to perform a health check and data validation on the following enterprise structures setup data:
Chart of Accounts
Value Sets and Values
Account Hierarchies Versions
Accounting Calendars
Legal Entities and Legal Reporting Units
Ledgers Setup
To access the Diagnostic Dashboard and execute the diagnostic tests, you must be granted the Application
Diagnostics Regular User job role.
Once you have been granted the role, then you can view the link to run the diagnostics tests under the
Troubleshooting on Settings and Actions menu on your Welcome page.
If you have the Application Diagnostics Viewer job role, you can view the diagnostic test results, but not run tests.
Use the following steps:
To access the Diagnostic Dashboard and execute the diagnostic tests, you must be granted the Application
Diagnostics Regular User job role.
To view the link to run the diagnostics tests under the Troubleshooting on Settings and Actions menu on your
Welcome page after you have been granted the user role.
Note: If you have the Application Diagnostics Viewer job role, you can view the diagnostic test results, but
not run tests.
Enterprise Structures Setup Report: Explained

Validate your enterprise structures configuration using the Enterprise Structures Setup Report. This report provides the
detailed listing of chart of accounts, segments, value sets, ledgers, legal entities, business units, and account hierarchy
information. Use this auditable report in multiple formats such as HTML, PDF, RTF, Excel (*.xlsx), Power Point (*.pptx), and
CSV to improve your off-line analysis requirements.
How it Works
Run as a scheduled process with one parameter; Chart of Accounts name.
10
Report Security
You must be assigned the following job roles:
GL_General_Accounting_Setup_Review_Duty
FUN_Enterprise_Structures_Administration_Duty
The duty roles are assigned with privileges including managing and reviewing accounting configurations.
The following predefined job roles have these duty roles assigned:
Application Implementation Consultant
Application Implementation Administrator
Setup Data Import and Export for Oracle Fusion Financials:

Explained
The following sections describe the manual tasks that you must complete as part of the setup data export and import
processes for the Oracle Fusion Financials offering.
Section Description
Setup tasks performed before export Perform these tasks prior to starting export processes for the Financials offering.

Setup tasks performed before import Perform these tasks prior to starting import processes for the Financials offering.

Setup tasks performed after import Review and perform the manual setup steps on the target instance as required. Setup data for these
tasks is not imported from the source instance.

Setup tasks not requiring data import Perform these tasks on the target instance as required. These setup tasks do not require data
import.

Refer to the Oracle Fusion Functional Setup Manager User's Guide for the steps to perform setup data export and import
processes.
Setup Tasks Performed Before Export

Prior to starting the export processes from the source instance, you must verify and update setup for the following task.
Verifying the setup ensures that data is correctly imported into the target instance.
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 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
11

insertion is enabled, account combinations
are created automatically as needed on the
target instance.

Setup Tasks Performed Before Import

Prior to starting import processes into the target instance, you must verify and update setup for the following task.
Define Common Applications Configuration Define Implementation Users The import process does not include
for Financials implementation users and roles associated
with them.

For more information, see Oracle Fusion
Middleware Enterprise Deployment Guide for
Oracle Identity Management.

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.
Activity Name Task Name
Define General Ledger Options Manage Journal Approval Rules

Define Approval Management for Manage Task Configurations for Financials

Financials Manage Approval Groups for Financials

Define Tax Geographies Manage Tax Geographies

Define Payables Define Automated Invoice Processing Configuration

Manage Payables Document Sequences
Define Image Processing Configure Document Capture Parameters

Define Customer Billing Configuration Manage Salesperson Account References

Define Customer Payments Manage Receivables Specialist Assignment Rules

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.
12
Define Credit Card Data Extend Employee Matching Rules Write custom PL/SQL code to extend the
predefined criteria for automatically matching
new corporate cards to employees to
incorporate your company-specific criteria. If
you use a custom matching rule, then the PL/
SQL package is not imported to the target
instance. You can create the package in the
target instance or copy the package to the
target instance and compile it.

Define Customer Create Customer Manually create customers, using the Create
Customer task in Functional Setup Manager,
or import customer information by running
the Trading Community Model Data Import
program.

Define Customer Manage Customers Manually maintain customer information

using the Manage Customer task in
Functional Setup Manager, or by running
the Trading Community Model Data Import
program.

Configure Payment System Connectivity Manage BI Publisher Templates

Manually import any new or updated Oracle
Business Intelligence Publisher (Oracle BI
Publisher) templates. Use the Oracle BI
Publisher archiving feature, or alternatively
perform the following steps:
1. Download the template file from the

source Oracle BI Publisher catalog.
2. Update or create a new template in
the target Oracle BI Publisher catalog.
3. Upload the source template file to the
target template.
Define Subledger Accounting Rules Import Supporting Reference Initial Balances This task allows upload of initial subledger
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 Fusion
Accounting Hub Implementation Guide,
Define Accounting Transformation.

Configure Payment System Connectivity Integrate External Payment Systems Setup entities resulting from this integration
are exported and imported through the
Transmission Configuration service. However
any work performed outside of Oracle Fusion
Applications to integrate with a payment
system must be applied to the production
environment manually. Examples include
custom code, routers, or dedicated lines to
facilitate communication.

Define Payments Security Manage System Security Options This setup cannot be imported and must be
set up again in a production instance. Use
13

the steps documented in the Oracle Fusion
Applications Post-Installation Guide.

Define Financial Reporting Center Configure Smart View Client for Users
Configuration Manually reconfigure the Smart View client to
point to the production instance.
For more information about configuring the

Smart View client for users, see:
Oracle Fusion Accounting Hub

Implementation Guide, Define
Financial Reporting
Oracle Enterprise Performance
Management System Installation
and Configuration Guide for Oracle
Enterprise Performance Management,
Installing Smart View and other topics
Oracle Hyperion Smart View for Office
User's Guide for Oracle Hyperion
Smart View
Define Financial Reporting Center Define Essbase Database Connection in Manually reconfigure the Essbase database
Configuration Workspace connection in Hyperion Workspace.

For more information about configuring
the Hyperion Workspace Database
Connection, see Oracle Fusion Accounting
Hub Implementation Guide, Define Financial
Reporting,

Define Financial Reporting Center Configure Financial Reporting Studio Client

Configuration for Users Manually reconfigure the Financial Reporting
Studio client to point to the production
instance.
For more information about configuring the

Financial Reporting Studio client for users,
see:
Oracle Fusion Accounting Hub

Implementation Guide, Define Financial
Reporting.
Oracle Enterprise Performance Management

System Installation and Configuration
Guide for Oracle Enterprise Performance
Management. Refer to the following topics:
Installing Financial Reporting Studio

and Financial Reporting Print Server
Configuring the Financial Reporting
Print Server
Administrative Information for Financial
Reporting
14
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.
1. Navigator > General Accounting:

Financial Reporting Center > Open
Workspace for Financial Reports.
2. Navigate > Applications > BI Catalog.
3. File > Export.
4. Save the file to the local desktop.
Import the file into Workspace in the target

environment.

Financial Reporting Center > Open
Workspace for Financial Reports.
2. Navigate > Applications > BI Catalog.
3. 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 run time 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.


Journals > Create Allocation Rules.
2. Navigator > Administer > Calculation
Manager
3. File > Export.
4. Save the file to the local desktop.
15
Import the file into Calculation Manager in the

target environment.

Journals > Create Allocation Rules.
2. Navigator > Administer > Calculation
Manager
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
Lifecycle Management tool.

For more information, see the Oracle
Hyperion Artifact Lifecycle Management
Utility User's Guide.

Define Hyperion Financial Management Define ERP Integrator Configuration for Manually import the rules using the Oracle
Integration Hyperion Financial Management Enterprise Performance Management


Define Budget Configuration Define Budget Configuration in Hyperion Manually import the rules using the Oracle
Planning Enterprise Performance Management


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


Setup Tasks Not Requiring Data Import

The following tasks in the setup task list are available to support your overall implementation approach. These tasks do not
require any data to be imported. You can perform these tasks on the target instance as required.
Define Tax Configuration Run Jurisdiction and Rates Upload Program

Manage Simulator Transactions
Define Fixed Assets Configuration Verify Data Role Generation for Asset Books

16
Define Disbursements Grant Payment Function Access

Configure Payment System Connectivity View Validations

Natural Languages: Points to Consider

Natural languages are all the languages that humans use, written and spoken. If a language is enabled, then users can
associate it with entities, for example as languages spoken by sales representatives. When managing natural languages,
consider tasks to perform and best practices for entering particular values.
Tasks
Once you add a language, it can't be deleted, but just disabled. You can optionally associate natural languages with
International Organization for Standardization (ISO) languages and territories, just for reference.
Values
When you create a natural language, use the alpha-2 ISO code as the language code, or, if not available, then alpha-3. If the
language is not an ISO language, then use x- as a prefix for the code, for example x-ja for a Japanese dialect. Use the sgn
code of ISO-639-2 for sign languages, followed by territory code, for example sgn-US for American Sign Language. You can
also use Internet Assigned Numbers Authority (IANA) language tags.
The natural language description must be the language name with territory name in parenthesis where needed, for example
English (Australia) and English (Canada).
Initial Configuration
Establishing Enterprise Structures Using the Enterprise Structures

Configurator: Explained
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.
17
This figure illustrates the process to configure your enterprise using the Enterprise Structures Configurator.
Establish Establish Job

Review Load
Enterprise and Position
Configuration Configuration
Structures Structures
Determine
Divisions
Position Usage
Define
Legal Entities Enterprise-Level
Attributes
Define Contextual
Business Units
Attributes
Reference Data
Sets
Business Unit
Set Assignment
Assign Reference
Data Sets to
Locations
To be able to use the Enterprise Structures Configurator, you must select the Enterprise Structures Guided Flow feature for
your offerings on the Configure Offerings page in the Setup and Maintenance work area. If you don't select this feature, then
you must set up your enterprise structure using individual tasks provided elsewhere in the offerings, and you can't create
multiple configurations to compare different scenarios.
Establish Enterprise Structures

To define your enterprise structures, use the guided flow within the Establish Enterprise Structures task to enter basic
information about your enterprise, such as the primary industry. You then create divisions, legal entities, business units,
and reference data sets. The Establish Enterprise Structures task enables you to create multiple enterprise configurations
so that you can compare different scenarios. Until you load a configuration, you can continue to create and edit multiple
configurations until you arrive at one that best suits your enterprise.
Establish Job and Position Structures

You also use a guided process to determine whether you want to use jobs only, or jobs and positions. The primary industry
that you select in the Establish Enterprise Structures task provides the application with enough information to make an
initial recommendation. You can either accept the recommendation, or you can answer additional questions about how you
18
manage people in your enterprise, and then make a selection. After you select whether to use jobs or positions, you are
prompted to set up a descriptive flexfield structure for jobs, and for positions if applicable. Descriptive flexfields enable you to
get more information when you create jobs and positions.
Review Configuration
You can view a result of the interview process prior to loading the configuration. The review results, show the divisions, legal
entities, business units, reference data sets, and the management reporting structure that the application will create when you
load the configuration.
Load Configuration
You can load only one configuration. When you load a configuration, the application creates the divisions, legal entities,
business units, and so on. After you load the configuration, you then use individual tasks to edit, add, and delete enterprise
structures.
Rolling Back an Enterprise Structure Configuration: Explained

The Enterprise Structures Configurator (ESC) provides the ability to roll back an enterprise configuration in the following
circumstances:
Roll Back a Configuration Manually

You can manually roll back an enterprise configuration after loading it, for example, because you decide you do not want to
use it. Clicking the Roll Back Configuration button on the Manage Enterprise Configuration page rolls back any enterprise
structures that were created as a part of loading the configuration.
Roll Back a Configuration Automatically

If an error occurs during the process of loading the configuration, then the application automatically rolls back any enterprise
structures that were created before the error was encountered.
Designing an Enterprise Configuration: Example

This example illustrates how to set up an enterprise based on a global company operating mainly in the US and the UK with a
single primary industry.
Scenario
InFusion Corporation is a multinational enterprise in the high technology industry with product lines that include all the
components that are required to build and maintain air quality monitoring systems for homes and businesses. Its primary
locations are in the US and the UK, but it has smaller outlets in France, Saudi Arabia, and the United Arab Emirates (UAE).
Enterprise Details
In the US, InFusion employs 400 people and has company revenue of 120 million US dollars.. Outside the US, InFusion
employs 200 people and has revenue of 60 million US dollars.
19
Analysis
InFusion requires three divisions.
The US division covers the US locations.

The Europe division covers UK and France.
Saudi Arabia and the UAE are covered by the Middle East division.
InFusion requires legal entities with legal employers, payroll statutory units, tax reporting units, and legislative data groups for
the US, UK, France, Saudi Arabia, and UAE, to employ and pay its workers in those countries.
InFusion requires a number of departments across the enterprise for each area of business, such as sales and marketing, and
a number of cost centers to track and report on the costs of those departments.
InFusion has general managers responsible for business units within each country. Those business units may share reference
data. Some reference data can be defined within a reference data set that multiple business units may subscribe to. Business
units are also required for financial purposes. Financial transactions are always processed within a business unit.
Resulting Enterprise Configuration

Based on this analysis, InFusion requires an enterprise with multiple divisions, ledgers, legal employers, payroll statutory units,
tax reporting units, legislative data groups, departments, cost centers, and business units.
20
This figure illustrates the enterprise configuration that results from the analysis of InFusion Corporation.
InFusion
Corporation
US Europe Middle East

Division Division Division
Extensions for
Localization
Support
- UAE
- Saudi Arabia
US UK France
Tax Reporting Tax Reporting Tax Reporting
Unit Unit Unit
Legal Legal Legal
Entity Entity Entity
Legislative Legislative Legislative
Data Group Data Group Data Group
Business Unit Business Unit Business Unit
Cost Cost Cost Cost

Center Center Center Center
Sales Marketing Marketing Sales
Department Department Department Department
(US) (US) (UK) (France)
21
FAQs for 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 do not 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.
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
What's the default reference data set?

The reference data set that is assigned to a business unit for all reference data groups, such as grades, locations,
departments, and jobs. You can override the default reference data set for any reference data group.
What happens if I override the set assignment?

For the selected business unit, you can override the default reference data set for one or more reference data groups. For
example, assume you have three reference data groups: Vision 1 SET, Vision 2 SET, and Vision 3 SET, where Vision SET 1 is
the default set for business unit United Kingdom Vision 1 BU. You can override the default so that:
Grades are assigned to Vision 2 SET.
Departments are assigned to Vision 3 SET.
Jobs are assigned to the default set, Vision 3 SET.
When do I create or edit ISO languages?

Edit the names and descriptions of International Organization for Standardization (ISO) languages to determine how they
appear in the application. The ISO languages are a part of the ISO 639 standard. If any change to the ISO standard doesn't
reflect in the application, you can update the ISO alpha-2 code or add languages to provide up-to-date information.
When do I edit languages?

Installed languages automatically appear on the Manage Languages page. This page also displays all languages that are
available for installation and translation. Each dialect is treated as a separate language.
Generally, you don't need to edit any of the detailed fields unless absolutely necessary.
When do I create or edit time zones?

Though all standard time zones are provided, enable only a subset for use in lists of time zone values. You can add time
zones if new zones became standard and the application isn't yet patched with the latest values.
22
Social Networks
Managing Oracle Social Network Objects: Explained

Use the Manage Oracle Social Network Objects task for managing the Oracle Social Network Objects. The integration
of Oracle Social Network with applications and business processes brings key attributes from the applications to share,
socialize, and update information. This helps in making better business decisions based on additional information that you
obtain and analyze within your social network environment.
Use the Manage Oracle Social Network Objects page to set up and define:
The business objects and attributes to enable
The enablement method for social network integration with Oracle Applications Cloud
To open the Manage Oracle Social Network Objects page, start in the Setup and Maintenance Overview page and search
for the Manage Oracle Social Network Objects task.
Use Oracle Social Network to:

Discuss projects and plans in public forums
Maintain:
Membership groups
Activity feeds of the people you select
Facilitate:
One-on-one Conversations
Reviews
Document sharing
Note: Oracle Social Network is currently available in Cloud implementations only.
An important aspect of managing Oracle Social Network objects is enabling business objects for integration.
Enabling Business Objects for Integration

A business object can't be shared within social network until a functional administrator or implementor:
Accesses the Manage Oracle Social Network Objects page in Oracle Applications Cloud
Enables the business object for social network integration
Related Topics
How can I update translations?
Synchronize Business Objects: Explained
What happens if I synchronize business objects?
23
What happens if I update translations?
Enabling Social Networking on Objects: Critical Choices

You can determine whether information about a business object, such as benefit plans or sales accounts, displays in Oracle
Social Network. If you enable an object for sharing, you allow users to collaborate on the object through social networking.
You can choose whether all instances of an object are shared, or only at the user's discretion. You can also choose which
attributes are shared, such as names, details, and who made the last update.
In addition to a wide range of predefined objects, you can share:

Custom objects and attributes created in Application Composer
Custom fields created in descriptive flexfields
Use the Manage Oracle Social Network Objects task in the Setup and Maintenance work area.
After you click Enable Object, select one of the following enablement options:
Manual
Automatic
No
Manual
If you select this option, which is recommended, you let users decide whether to share each instance of the object with
the social network. Once shared, all updates to the enabled attributes of the instance appear on the social network. If the
instance is deleted, that information is also shared.
Click Enable All to enable all objects for all applications. Enable All automatically applies the Manual option, which means
that the user can choose whether to share an object instance.
Automatic
With this option, news about all instances of the object appears on the social network, including:
Every newly created instance
All subsequent updates to the enabled attributes
Deletion of any instances
No
With this option, which is the default value, no news about the object appears on the social network.
Note: When you click Disable Object, the enabled setting of the selected business object is automatically
changed to No.
After you enable a business object, you must enable one or more attributes of the object. Only the enabled attributes are
shared. The Status column in the Business Objects table indicates which enabled business objects don't yet have an enabled
attribute. For these objects, only the following information appear on the social network:
Internal bookkeeping information, when creating or updating an instance of the object.
24
News that an instance is deleted.
Related Topics
How can I update translations?
What happens if I update translations?
Synchronize Business Objects: Explained
What happens if I synchronize business objects?
Configuring Social Objects in Oracle Social Network: Explained

Before you can start using the social object, for example, accounting period, journal, or intercompany transaction in Oracle
Social Network, configure the social object using the Manage Oracle Social Network Objects task on the Setup and
Maintenance task list page.
The configuration consists of enabling the social object and its attributes for use on the Oracle Social Network. For example,
for the accounting period social object, enable the following attributes: Ledger, Period Name, Period Start Date, and Period
End Date. You also configure the enablement method of the social object. The methods are: No, Manual, and Automatic.
The configuration applies to all instances of that social object in the application and to all ledgers. You can automatically
create an conversation by setting the option in Managing Oracle Social Network Objects user interface.
Note: Oracle Social Network is currently only available in Oracle Cloud implementations.
FAQs for Social Networks

How can I enable flexfield segments for Oracle Social Network Cloud Service?
When you manage Oracle Social Network Objects during setup and maintenance, search for the business object that
includes descriptive flexfields. Select the attributes that are defined as flexfield segments and enable them.
How can I use social networking to discuss external transactions with the general
accounting manager?
Use the Social link on the View External Transaction page to invite others to a conversation to discuss external transactions.
You are a cash manager reviewing the external cash transactions created from bank interest and charges. Before accounting
for these transactions and posting them to the general ledger, you must inform the general accounting manager that the
journal entries are being created.
From the Manage External Transaction page, search for the transaction you want to discuss, in the search results, click on
the transaction number to review in the conversation:
1. Click Social to open Oracle Social Network.
2. Click the Share button.
3. Create a new conversation.
4. Invite the general accounting manager to join the conversation.
25
The general accounting manager reviews and confirms the created journals from the external transactions can be posted to
the general ledger.
After reviewing the transactions with general accounting manager, the cash manager can account for the transactions and
post them to the general ledger.
Depending on your job role and permissions, you can access social networking features for the following Oracle Fusion Cash
Management activities:
Bank statement
External cash transaction
Related Topics
What does social networking have to do with my job?
How can I use social networking to discuss intercompany allocation adjustments with
cost center owners?
Use the Social link on the Intercompany Transactions work area to invite others to a conversation to address the adjustments.
For example, the monthly intercompany allocation of administration costs changed substantially to more accurately reflect
resource usage. You need the cost center owners to validate their intercompany allocation.
From the Intercompany Transactions work area:

1. Search for the intercompany transaction.
2. Click Social to open Oracle Social Network. Click the Share button, or click Join if collaboration has already been
initiated.
3. Create a new related conversation.
4. Invite all of the cost center owners to join the conversation.
5. Upload the allocation spreadsheet for the cost center owners' review.
The cost center owners can post questions and because the other cost center owners are members, they can see your
responses to the questions. Each cost center owner validates their intercompany allocation in the conversation itself, which
creates a lasting record.
Related Topics
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.
26
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.
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
27
28
Implementing Enterprise Structures and General Ledger Reference Data Sharing
2 Reference Data Sharing
Reference Data Sharing: Explained

Reference data sharing facilitates sharing of configuration data such as jobs and payment terms, across organizational
divisions or business units. You define reference data sets and determine how common data is shared or partitioned across
business entities to avoid duplication and reduce maintenance effort. Depending on the requirement (specific or common),
each business unit can maintain its data at a central location, using a set of values either specific to it or shared by other
business units.
A common reference data set is available as the default set, which can be assigned to several business units sharing the
same reference data. For commonly used data such as currencies, you can use the common reference data set and assign it
to multiple business units in various countries that use the same currency. In cases where the default set can't be assigned to
an entity, you can create specific sets. The data set visible on the transactional page depends on the sharing method used to
share reference data.
For example, XYZ Corporation uses the same grades throughout the entire organization. Instead of different business units
setting up and using the same grades, XYZ Corporation decides to create a set called Grades, which contains the grades. All
business units in the organization have the Grades set so that the grades can be shared and used.
Note: For specific information about configuring reference data sharing for a particular object or product, refer
to the relevant product documentation.
Reference Data Sets: Explained

Reference data sets are logical groups of reference data that various transactional entities can use depending on the
business context. You can get started using either the common reference data set or the enterprise set depending on your
implementation requirement. You can also create and maintain custom reference data sets, while continuing to use the
common reference data set.
Consider the following scenario. Your enterprise can decide that only some aspects of corporate policy should affect
all business units. The remaining aspects are at the discretion of the business unit manager to implement. This enables
your enterprise to balance autonomy and control for each business unit. For example, your enterprise holds business unit
managers accountable for their profit and loss, but manages working capital requirements at a corporate level. Then, you can
let managers define their own sales methods, but define payment terms centrally. As a result, each business unit has its own
reference data set for sales methods and one central reference data set for payment terms assigned to all business units.
Partitioning
Partitioning reference data and creating data sets provide you the flexibility to handle the reference data to fulfill your business
requirements. You can share modular information and data processing options among business units with ease. You can
create separate sets and subsets for each business unit. Alternatively, you can create common sets or subsets to enable
sharing reference data between several business units, without duplicating the reference data.
29
The following figure illustrates the reference data sharing method. The user can access the data assigned to a specific set in a
particular business unit, as well as access the data assigned to the common set.
can also access ...
has
access to ...
Common Set
UK
Business Unit
contains ... Tokyo Paris Berlin
UK
Location Set
London Oxford Cambridge
Related Topics
Defining Default Reference Data Sets: Points to Consider
Reference Data Sets and Sharing Methods: Explained

Oracle Fusion Applications reference data sharing feature is also known as SetID. The reference data sharing functionality
supports operations in multiple ledgers, business units, and warehouses. As a result, there is a reduction in the administrative
burden and the time to implement new business units. For example, you can share sales methods, or transaction types
across business units. You may also share certain other data across asset books, cost organizations, or project units.
The reference data sharing features use reference data sets to which reference data is assigned. The reference data sets
group assigned reference data. The sets can be understood as buckets of reference data assigned to multiple business units
or other application components.
Reference Data Sets

You begin this part of your implementation by creating and assigning reference data to sets. Make changes carefully as
changes to a particular set affect all business units or application components using that set. You can assign a separate
set to each business unit for the type of object that is being shared. For example, assign separate sets for payment terms,
transaction types, and sales methods to your business units.
30
Your enterprise can determine that certain aspects of your corporate policy can affect all business units. The remaining
aspects are at the discretion of the business unit manager to implement. This allows your enterprise to balance autonomy
and control for each business unit. For example, your enterprise holds business unit managers accountable for their profit and
loss, but manages working capital requirements at a corporate level. In such a case, you can let managers define their own
sales methods, but define payment terms centrally. In this example:
Each business unit has its own reference data set for sales methods.
One central reference data set for payment terms is assigned to all business units.
The reference data sharing is especially valuable for lowering the cost of setting up new business units. For example,
your enterprise operates in the hospitality industry. You are adding a new business unit to track your new spa services.
The hospitality divisional reference data set can be assigned to the new business unit to quickly set up data for this entity
component. You can establish other business unit reference data in a business unit-specific reference data set as needed.
Reference Data Sharing Methods

Variations exist in the methods used to share data in reference data sets across different types of objects. The following list
identifies the methods:
Assignment to one set only, no common values allowed. This method is the simplest form of sharing reference
data that allows assigning a reference data object instance to one and only one set. For example, Asset Prorate
Conventions are defined and assigned to only one reference data set. This set can be shared across multiple asset
books, but all the values are contained only in this one set.
Assignment to one set only, with common values. This method is the most commonly used method of sharing
reference data that allows defining reference data object instance across all sets. For example, Receivables
Transaction Types are assigned to a common set that is available to all the business units. You need not explicitly
assign the transaction types to each business unit. In addition, you can assign a business unit-specific set of
transaction types. At transaction entry, the list of values for transaction types includes the following:
Transaction types from the set assigned to the business unit.

Transaction types assigned to the common set that is shared across all business units.
Assignment to multiple sets, no common values allowed. The method of sharing reference data that allows a
reference data object instance to be assigned to multiple sets. For instance, Payables Payment Terms use this
method. It means that each payment term can be assigned to one or more than one set. For example, you assign
the payment term Net 30 to several sets, but assign Net 15 to a set specific only to your business unit. At transaction
entry, the list of values for payment terms consists of only the set that is assigned to the transaction's business unit.
Note: Oracle Fusion Applications contains a reference data set called Enterprise. Define any reference data that
affects your entire enterprise in this set. Also update the data set going forward as you create new reference
data items.
Business Units and Reference Data Sets: How They Work

Together
Reference data sharing enables you to group set-enabled reference data such as jobs or grades to share the data across
different parts of the organization. Sets also enable you to filter reference data at the transaction level so that only data
assigned to certain sets is available to be selected. To filter reference data, Oracle Fusion Human Capital Management
31
(HCM), applications use the business unit on the transaction. To set up reference data sharing in Oracle Fusion HCM, you
create business units and sets, and then assign the sets to the business units.
Common Set Versus Specific Sets

Some reference data in your organization may be considered global, and should therefore be made available for use within
the entire enterprise. You can assign this type of data to the Common Set, which is a predefined set. Regardless of the
business unit on a transaction, reference data assigned to the Common Set is always available, in addition to the reference
data assigned to the set that corresponds to the business unit on the transaction.
Other types of reference data can be specific to certain business units, so you can restrict the use of the data to those
business units. In this case, you can create sets specifically for this type of data, and assign the sets to the business units.
Business Unit Set Assignment

When you assign reference data sets to business units, you assign a default reference data set to use for all reference data
types for that business unit. You can override the set assignment for one or more data types.
Example: Assigning Sets to Business Units

InFusion Corporation has two divisions: Lighting and Security, and the divisions each have two locations. Each location has
one or more business functions.
The following figure illustrates the structure of InFusion Corporation.
Enterprise
Division Division
InFusion Lighting InFusion Security
Legal Entity Legal Entity Legal Entity Legal Entity

Japan US UK India
Sales Marketing Sales Sales Sales Marketing
When deciding how to create business units, InFusion decides to create them using the country and business function level.
Therefore, they created the following business units:
Sales_Japan
32
Marketing_Japan
Sales_US
Sales_UK
Marketing_India
Sales_India
Because locations, departments, and grades are specific to each business unit, InFusion does not want to share these types
of reference data across business units. They create a reference data set for each business unit so that data of those types
can be set up separately. Because the jobs in the Sales business function are the same across many locations, InFusion
decides to create one additional set called Jobs. They override the set assignment for the Jobs reference data group and
assign it to the Jobs set. Based on these requirements, they create the following sets:
Sales_Japan_Set
Mktg_Japan_Set
Sales_US_Set
Sales_UK_Set
Mktg_India_Set
Sales_India_Set
Grades_Set
The following table describes the default set assignment and the set assignment overrides for each business unit in InFusion:
Business Unit Default Set Assignment Set Assignment Overrides
Sales_Japan Sales_ Japan_Set for grades, departments, Jobs set for jobs
and locations

Marketing_ Japan Mktg_Japan_Set for grades, departments, None

and locations

Sales_US Sales_US_Set for grades, departments, and Jobs set for jobs
locations

Sales_UK Sales_UK_Set for grades, departments, and Jobs set for jobs
locations

Marketing_ India Mktg_India_Set for grades, departments, and None

locations

Sales_India Sales_ India_Set for grades, departments, Jobs set for jobs
and locations

When setting up grades, departments, and locations for the business units, InFusion assigns the data to the default set for
each business unit. When setting up jobs, they assign the Jobs set and assign the Common Set to any jobs that may be
used throughout the entire organization.
When using grades, departments, and locations at the transaction level, users can select data from the set that corresponds
to the business unit they enter on the transaction, and any data assigned to the Common Set. For example, for transactions
33
for the Marketing_Japan business unit, grades, locations, and departments from the Mktg_Japan_Set is available to select, as
well as from the Common Set.
When using jobs at the transaction level, users can select jobs from the Jobs set and from the Common Set when they enter
a sales business unit on the transaction. For example, when a manager hires an employee for the Sales_India business unit,
the list of jobs is filtered to show jobs from the Jobs and Common sets.
The following figure illustrates what sets of jobs can be accessed when a manager creates an assignment for a worker.
can also select jobs

from...
can select jobs from...
Jobs Set Common Set
Sales Sales Sales Administrative

Consultant Manager Executive Assistant
Creating Reference Data Sets in the Enterprise Structures

Configurator: Explained
If you created business units automatically, then the Enterprise Structures Configurator automatically creates reference data
sets for you. The Enterprise Structures Configurator creates one reference data set for each business unit. You can add
additional sets, but you cannot delete any of the sets that were created automatically.
A standard set called the Enterprise set is predefined.
Common Set
The Common set is a predefined set that enables you to share reference data across business units. When you select set-
enabled data at the transaction level, the list of values includes data in the:
Common set
Set associated with the data type for the business unit on the transaction
For example, when you create an assignment, the list of values for grades includes grade in the:
Common set
Set that is assigned to grades for the business unit in which you creating the assignment
34
Assigning Reference Data Sets to Reference Objects:

Points to Consider
You can assign the reference data sets to reference objects using the Manage Reference Data Set Assignments page. For
multiple assignments, you can classify different types of reference data sets into groups and assign them to the reference
entity objects. The assignment takes into consideration the determinant type, determinant, and reference group, if any.
Determinant Types
The partitioned reference data is shared using a business context setting called the determinant type. A determinant type
is the point of reference used in the data assignment process. The following table lists the determinant types used in the
reference data assignment.
Determinant Type Description
Asset Book Information about the acquisition, depreciation, and retirement of an asset that belongs to a ledger
or a business unit.

Business Unit The departments or organizations within an enterprise.

Cost Organization The organization used for cost accounting and reporting on various inventory and cost centers
within an enterprise.

Project Unit A logical organization within an enterprise that is responsible for enforcing consistent project
management practices.

Reference Data Set References to other shared reference data sets.

Determinant
The determinant (also called determinant value) is a value that corresponds to the selected determinant type. The determinant
is one of the criteria for selecting the appropriate reference data set.
Reference Groups
A transactional entity may have multiple reference entities (generally considered to be setup data). However, all reference
entities are treated alike because of similarity in implementing business policies and legal rules. Such reference entities in your
application are grouped into logical units called reference groups. For example, all tables and views that define Sales Order
Type details might be a part of the same reference group. Reference groups are predefined in the reference groups table.
35
Items and Supplier Site Reference Data Sharing: Explained

Some products, such as items and supplier sites, required special logic for reference data sharing and have implemented
their own domain-specific ways for sharing data.
Items
If you share your items across warehouses or manufacturing facilities, you can access them through a common item
master. Configure one or multiple item masters for your enterprise, based your enterprise structure. A single item master
is recommended because it provides simpler and more efficient maintenance. However, in rare cases, it may be beneficial
to keep multiple item masters. For example, if you acquire another enterprise and want to continue to operate your lines of
business separately, maintaining a second item master might be the best decision.
Suppliers Sites
You can approve particular suppliers to supply specified commodities and authorize your business units to buy from those
suppliers when the need arises. For example, you might be a household cleaning products manufacturer and need dyes,
plastics, and perfumes to make your products. You purchase from a central supplier 70% of your perfume supplies with an
additional supplier, in reserve, from whom you purchase the remaining 30%. At the same time, each of your business units
purchases plastics and dyes from the same supplier, but from different local supplier sites to save transportation costs.
To implement business unit-specific supplier sites, Oracle Fusion Procurement supports a method for defining suppliers sites
as owned and managed by the business unit responsible for negotiating the supplier terms. Your other business units that
have a service provider relationship defined with your procurement business unit subscribe to the supplier sites using the
supplier site assignments feature. In addition, Procurement allows sharing of the following procurement data objects across
business units:
Supplier qualification data, such as approved supplier lists
Catalog content, such as agreements, smart forms, public shopping lists, and content zones
Procurement configuration data
FAQs for Reference Data Sharing
What reference data objects can be shared across business units?

The following table contains the reference data objects for the Oracle Fusion Applications that can be shared across business
units and the method in which the reference data for each is shared.
Application Name Reference Data Object Method of Sharing
Trading Community Model Customer Account Relationship Assignment to one set only, no common
values allowed

36
Trading Community Model Customer Account Site Assignment to one set only, no common
values allowed

Trading Community Model Salesperson Assignment to one set only, no common

values allowed

Opportunity Management Sales Method Group Assignment to one set only, with common
values

Work Management Assessment Templates Assignment to one set only, with common
values

Enterprise Contracts Contract Types Assignment to one set only, with common
values

Sales Sales Method Assignment to one set only, with common

values

Common Components Activity Templates Assignment to one set only, with common
values

Payables Payment Terms Assignment to multiple sets, no common

values allowed

Receivables Accounting Rules Assignment to one set only, with common

values

Receivables Aging Buckets Assignment to one set only, with common

values

Receivables Auto Cash Rules Assignment to one set only, with common
values

Receivables Collectors Assignment to one set only, with common

values

Receivables Lockbox Assignment to one set only, with common

values

Receivables Memo Lines Assignment to one set only, with common

values

Receivables Payment Terms Assignment to one set only, with common

values

Receivables Remit To Address Assignment to one set only, with common

values

37
Receivables Revenue Contingencies Assignment to one set only, with common

values

Receivables Transaction Source Assignment to one set only, with common

values

Receivables Transaction Type Assignment to one set only, with common

values

Advanced Collections Collections Setups Assignment to one set only, with common
values

Advanced Collections Dunning Plans Assignment to one set only, with common
values

Tax Tax Classification Codes Assignment to multiple sets, no common

values allowed

Human Resources Departments Assignment to one set only, with common

values

Human Resources Jobs Assignment to one set only, with common

values

Human Resources Locations Assignment to one set only, with common

values

Human Resources Grades Assignment to one set only, with common

values

Project Billing Project and Contract Billing Assignment to multiple sets, no common
values allowed

Project Foundation Project Accounting Definition Assignment to one set only, no common
values allowed

Project Foundation Project Rates Assignment to one set only, with common
values

Order Management Hold Codes Assignment to one set only, with common
values

Order Management Orchestration Process Assignment to one set only, with common
values

38
What reference data objects can be shared across asset books?

The following list contains the reference data objects for Oracle Fusion Assets that can be shared across asset books and the
method in which the reference data for each is shared.
Assets Bonus Rules Assignment to one set only, no common

values allowed

Assets Depreciation Ceilings Assignment to one set only, no common

values allowed

Assets Depreciation Methods Assignment to one set only, with common

values

Assets Asset Descriptions Assignment to one set only, no common

values allowed

Assets Property Types Assignment to one set only, with common

values

Assets Prorate Conventions Assignment to one set only, no common

values allowed

Assets Asset Queue Names Assignment to one set only, with common
values

Assets Retirement Types Assignment to one set only, with common

values

Assets Unplanned Types Assignment to one set only, with common

values

What reference data objects can be shared across cost

organizations?
The following table contains the reference data objects for Oracle Fusion Cost Management that can be shared across cost
organizations and the method in which the reference data for each is shared.
Cost Management Cost Structure Assignment to one set only, no common

values allowed

39
What reference data objects can be shared across project units?

The following table contains the reference data objects for Oracle Fusion Project Foundation that can be shared across
project units and the method in which the reference data for each is shared.
Project Foundation Project Definition Assignment to multiple sets, no common

values allowed

Project Foundation Project Transaction Types Assignment to multiple sets, no common

values allowed

40
Implementing Enterprise Structures and General Ledger Enterprise
3 Enterprise
Enterprise: Explained
An enterprise is a collection of legal entities under 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.
Managing Enterprise Information for Non-HCM Users:

Explained
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 are 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 are not relevant outside of Oracle Fusion HCM.
Manage Locations
Locations: Explained
A location identifies physical addresses of a workforce structure, such as a department or a job. You create and manage
locations using the Manage Locations task in the Workforce Structures work area.
You can also create locations to enter the addresses of external organizations that you want to maintain, such as employment
agencies, tax authorities, and insurance or benefits carriers.
The locations that you create exist as separate structures that you can use for reporting purposes, and in rules that determine
employee eligibility for various types of compensation and benefits. You enter information about a location only once.
Subsequently, when you set up other workforce structures you select the location from a list.
Location Sets
When you create a location, you must associate it with a set. Only those users who have access to the set's business unit
can access the location set and other associated workforce structure sets, such as those that contain departments and jobs.
41
Note the following:
You can also associate the location to the common set so that users across your enterprise can access the location
irrespective of their business unit.
When users search for locations, they can see the locations that they have access to along with the locations in the
common set.
The following figure shows how locations sets restrict access to users.
can also access ...
has
access to ...
Common Set
UK
Business Unit
contains ... Tokyo Paris Berlin
UK
Location Set
London Oxford Cambridge
Uploading Locations Using a Spreadsheet

If you have a list of locations already defined for your enterprise, you can upload them from a spreadsheet.
To use this option:
Download a spreadsheet template

Add your location information to the spreadsheet
Upload directly to your enterprise configuration
You can upload the spreadsheet multiple times to accommodate revisions.
Related Topics
Uploading Workforce Structures Using a Spreadsheet: Explained
42
FAQs for Manage Locations

Why can't I see my location in the search results?
You can search for approved locations only. Also, if you created a location in Oracle Fusion Trading Community Model,
then you can't access that location from Oracle Fusion Global Human Resources. For use in Oracle Fusion HCM, you must
recreate the location from the Manage Locations page.
What happens if I select a geographic hierarchy node when I'm creating or editing a
location?
The calendar events that you created for the geographic node start to apply for the location and may impact the availability
of worker assignments at that location. You manage locations using the Manage Locations task in the Workforce Structures
work area.
The geographical hierarchy nodes available for selection on the Locations page display from a predefined geographic
hierarchy.
Related Topics
Worker Availability: How It Is Determined
What happens if I select an inventory organization when I am creating or editing a

location?
The location is available for selection in purchase documents of that inventory organization in Oracle Fusion Inventory
Management. If you don't select an inventory organization, then the location is available in purchase documents across all
inventory organizations.
What happens if I inactivate a location?

Starting from the effective date that you entered, you can no longer associate the location with other workforce structures,
assignments, or applications. If the location is already in use, it will continue to be available to the components that currently
use it.
How can I associate a location with an inventory organization?

From the Oracle Fusion Global Human Resources, go to the Manage Locations page. Use the Manage Locations task in the
Workforce Structures work area.
To appear on the Create or Edit Location pages, your inventory organization must be effective on today's date and must exist
in the location set that you selected.
Legal Jurisdictions and Authorities
43
Jurisdictions and Legal Authorities: Explained

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.
Jurisdictions: Explained
Jurisdiction is a physical territory such as a group of countries, country, state, county, or parish where a particular piece of
legislation applies. French Labor Law, Singapore Transactions Tax Law, and US Income Tax Laws are examples of particular
legislation that apply to legal entities operating in different countries' jurisdictions. Judicial authority may be exercised within a
jurisdiction.
Types of jurisdictions are:
Identifying Jurisdiction
Income Tax Jurisdiction
Transaction Tax Jurisdiction
Identifying Jurisdiction
For each legal entity, select an identifying jurisdiction. An identifying jurisdiction is your first jurisdiction you must register
with to be allowed to do business in a country. If there is more than one jurisdiction that a legal entity must register with
to commence business, select one as the identifying jurisdiction. Typically the identifying jurisdiction is the one you use to
uniquely identify your legal entity.
Income tax jurisdictions and transaction tax jurisdictions do not represent the same jurisdiction. Although in some countries,
the two jurisdictions are defined at the same geopolitical level, such as a country, and share the same legal authority, they are
two distinct jurisdictions.
Income Tax Jurisdiction

Create income tax jurisdictions to properly report and remit income taxes to the legal authority. Income tax jurisdictions by
law impose taxes on your financial income generated by all your entities within their jurisdiction. Income tax is a key source of
funding that the government uses to fund its activities and serve the public.
Transaction Tax Jurisdiction

Create transaction tax jurisdictions through Oracle Fusion Tax in a separate business flow, because of the specific needs
and complexities of various taxes. Tax jurisdictions and their respective rates are provided by suppliers and require periodic
maintenance. Use transaction tax jurisdiction for legal reporting of sales and value added taxes.
44
Legal Authorities: Explained

A legal authority is a government or legal body that is charged with powers to make laws, levy and collect fees and taxes, and
remit financial appropriations for a given jurisdiction.
For example, the Internal Revenue Service is the authority for enforcing income tax laws in United States. In some countries,
such as India and Brazil, you are required to print legal authority information on your tax reports. Legal authorities are defined
in the Oracle Fusion Legal Entity Configurator. Tax authorities are a subset of legal authorities and are defined using the same
setup flow.
Legal authorities are not mandatory in Oracle Fusion Human Capital Management (HCM), but are recommended and are
generally referenced on statutory reports.
Creating Legal Jurisdictions, Addresses and Authorities: Examples

Define legal jurisdictions and related legal authorities to support multiple legal entity registrations, which are used by Oracle
Fusion Tax and Oracle Fusion Payroll.
Legal Jurisdictions
Create a legal jurisdiction by following these steps:
1. Navigator > Setup and Maintenance > Manage Legal Jurisdictions > Go to Task.
2. Select Create.
3. Enter a unique Name, United States Income Tax.
4. Select a Territory, United States.
5. Select a Legislative Category, Income tax.
6. Select Identifying, Yes. Identifying indicates the first jurisdiction a legal entity must register with to do business in a
country.
7. Enter a Start Date if desired. You can also add an End Date to indicate a date that the jurisdiction may no longer
be used.
8. Select a Legal Entity Registration Code, EIN or TIN.
9. Select a Legal Reporting Unit Registration Code, Legal Reporting Unit Registration Number.
10. Optionally enter one or more Legal Functions.
11. Save and Close.
Legal Addresses for Legal Entities and Reporting Units

Create a legal address for legal entities and reporting units by following these steps:
1. Navigator > Setup and Maintenance > Manage Legal Address > Go to Task.
2. Select Create.
3. Select Country.
4. Enter Address Line 1, Oracle Parkway.
5. Optionally enter Address Line 2, and Address Line 3.
6. Enter or Select the postal code, 94065.
7. Select Geography 94065 and Parent Geography Redwood Shores, San Mateo, CA.
8. Optionally enter a Time Zone, US Pacific Time.
9. OK.
45
10. Save and Close.
Legal Authorities
Create a legal authority by following these steps:
1. Navigator > Setup and Maintenance >Manage Legal Authorities > Go to Task.
2. Enter the Name, California Franchise Tax Board.
3. Enter the Tax Authority Type, Reporting.
Note: Create an address for the legal authority.

4. Select Create.
5. The Site Number is automatically assigned.
6. Optionally enter a Mail Stop.
7. Select Country, United States
8. Enter Address Line 1, 121 Spear Street, Suite 400.
9. Optionally enter Address Line 2, and Address Line 3.
10. Enter or Select the postal code, 94105.
11. Select Geography 94105 and Parent Geography San Francisco, San Francisco, CA.
12. OK.
13. Optionally enter a Time Zone, US Pacific Time.
14. Optionally click the One-Time Address check box.
15. The From Date displays today's date. Update if necessary.
16. Optionally enter a To Date to indicate the last day the address can be used.
Note: You can optionally enter Address Purpose details.

17. Select Add Row.
18. Select Purpose.
19. The Purpose from Date will default to today's date.
20. Optionally enter a Purpose to Date.
21. OK.
22. Save and Close.
Creating Legal Entities, Registrations, and Reporting Units: Examples

Define a legal entity for each registered company or other entity recognized in law for which you want to record assets,
liabilities, and income, pay transaction taxes, or perform intercompany trading.
Legal Entity
Create a legal entity by following these steps:
1. Navigator > Setup and Maintenance > Manage Legal Entity > Go to Task.
2. Accept the default Country, United States.
3. Enter Name, InFusion USA West.
4. Enter Legal Entity Identifier, US0033.
5. Optionally enter Start Date. When the start date is blank the legal entity is effective from the creation date.
6. Optionally enter an End Date.
46
7. Optionally, if your legal entity should be registered to report payroll tax and social insurance, select the Payroll
statutory unit check box.
8. Optionally, if your legal entity has employees, select the Legal employer check box.
9. Optionally, if this legal entity is not a payroll statutory unit, select an existing payroll statutory unit to report payroll tax
and social instance on behalf of this legal entity.
10. Enter the Registration Information
11. Accept the default Identifying Jurisdiction, United States Income Tax.
12. Search for and select a Legal Address, 500 Oracle Parkway, Redwood Shores, CA 94065.
The legal address must have been entered previously using the Manage Legal Address task.
13. OK.
14. Optionally enter a Place of Registration.
15. Enter the EIN or TIN.
16. Enter the Legal Reporting Unit Registration Number.
17. Save and Close.
18. Navigator > Setup and Maintenance > Define Legal Entries > Manage Legal Entity > Select to set scope.
19. Select the Manage Legal Entity.
20. In the *Legal Entity list, select Select and Add.
21. Click Apply and Go to Task.
22. Select your legal entity.
23. Save and Close on the very bottom of the window.
This sets the scope for your task list to the selected legal entity.
24. Save and Close.
Legal Entity Registrations

A legal entity registration with the same name as that of the legal entity is created by default. To verify this, locate the Manage
Legal Entity Registrations task and then select Go to Task. To create another registration for the legal entity follow these
steps:
1. Navigator > Setup and Maintenance > Manage Legal Entity Registrations: Verify that the Legal Entity scope
value is set correctly.
2. Go to Task.
3. Select Create.
4. Enter Jurisdiction.
5. Enter Registered Address.
6. Enter Registered Name.
7. Optionally enter Alternate Name, Registration Number, Place of Registration, Issuing Legal Authority, and
Issuing Legal Authority Address, Start Date, and End Date.
8. Save and Close.
Legal Reporting Unit

When a legal entity is created, a legal reporting unit with the same name as that of the entity is also automatically created. To
create more legal reporting units or modify the settings follow these steps:
1. Navigator > Setup and Maintenance > Define Legal Reporting Unit. > Manage Legal Reporting Unit. Verify that
the Legal Entity scope value is set correctly.
2. Go to Task
3. Select Create.
4. Enter Territory, United States.
47
5. Enter Name.
6. Optionally enter a Start Date.
7. Enter Registration Information.
8. Search for and select Jurisdiction.
9. Enter Main Legal Reporting Unit information.
10. Select the value Yes or No for the Main Legal Reporting Unit. Set value to yes only if you are creating a new main
(primary) legal reporting unit.
11. Enter the Main Effective Start Date, 1/1/11.
12. Save and Close.
Related Topics
Legal Entities: Explained
Planning Legal Reporting Units: Points to Consider
Legal Entity in Oracle Fusion: Points to Consider
Define Lookups
Lookups: Explained
Lookups are lists of values in applications. You define a list of values as a lookup type consisting of a set of lookup codes,
each code's translated meaning, and optionally a tag. End users see the list of translated meanings as the available values for
an object.
Lookups provide a means of validation and lists of values where valid values appear on a list with no duplicate values. For
example, an application might store the values Y and N in a column in a table, but when displaying those values in the user
interface, Yes or No (or their translated equivalents) should be available for end users to select. For example, the two lookup
codes Y and N are defined in the REQUIRED_INDICATOR lookup type.
The following table contains an example of a lookup type for marital status (MAR_STATUS) that has lookup codes for users to
specify married, single, or available legal partnerships.
Lookup Code Meaning Tag
M Married Not applicable

S Single Not applicable

R Registered Partner +NL

DP Domestic Partner -FR, AU

In this case, tags are used for localizing the codes. All legislations list Married and Single. Only the Dutch legislation lists
Registered Partner. And all legislations except France and Australia also list Domestic Partner.
48
When managing lookups, you need to understand the following.

Using lookups in applications
Customization levels
Accessing lookups
Enabling lookups
The three kinds of lookups: standard, common, and set enabled
Using Lookups in Applications

Use lookups to provide validation or a list of values for a user input field in a user interface.
An example of a lookup used for validation is a flexfield segment using a table-validated value set with values from a lookup
type. An example of a lookup in a list of values is a profile option's available values from which users select one to set the
profile option. Invoice Approval Status gives the option of including payables invoices of different approval statuses in a
report. The lookup code values include All, so that users can report by all statuses: Approved, Resubmitted for approval,
Pending or rejected, and Rejected.
Customization Level
The customization level of a lookup type determines whether the lookups in that lookup type can be edited. This applies data
security to lookups.
Some lookup types are locked so no new codes and other changes can be added during implementation or later, as needed.
Depending on the customization level of a lookup type, you may be able to change the codes or their meanings. Some
lookups are designated as extensible, so new lookup codes can be created during implementation, but the meanings of
predefined lookup codes cannot be modified. Some predefined lookup codes can be changed during implementation or later,
as needed.
The customization levels are user, extensible, and system. The following table shows the lookup management tasks permitted
at each customization level.
Permitted Task User Extensible System
Deleting a lookup type Yes No No

Inserting new codes Yes Yes No

Updating start date, end date, Yes Yes, only if the code is not No
and enabling the lookup code predefined data

Deleting codes Yes Yes, only if the code is not No

predefined data

Updating tags Yes No No

Updating module Yes No No

Predefined data means LAST_UPDATED_BY = SEED_DATA_FROM_APPLICATION.
If a product depends on a lookup, the customization level must be system or extensible to prevent deletion.
49
Once the customization level is set for a lookup type, it can't be modified. The customization level for lookup types created
using the Define Lookups page is by default set at the User level.
Standard, Common, and Set-Enabled Lookups

The following table shows the available types of lookups.
Lookup Type Description
Standard Lists the available codes and translated meanings.

Set enabled Associates a reference data set with the lookup codes.

Common Legacy lookups or lookups that have attributes.

Standard lookups are the simplest form of lookup types consisting only of codes and their translated meaning. They differ
from common lookups only in being defined in the standard lookup view. Common lookups exist for reasons of backward
compatibility and differ from standard lookups only in being defined in the common lookup view. These can also be lookups
having attribute columns. Set enabled lookup types store lookup codes that are enabled for reference data sharing. At
runtime, a set-enabled lookup code is visible because the value of the determinant identifies a reference data set in which the
lookup code is present.
Accessing Lookups
Standard, set-enabled, and common lookups are defined in the Standard, Set-enabled, and Common views, respectively.
Applications development may define lookups in an application view to restrict the UI pages where they may appear.
In lookups management tasks, lookups may be associated with a module in the application taxonomy to provide criteria
for narrowing a search or limiting the number of lookups accessed by a product specific task such as Manage Purchasing
Lookups.
Enabling Lookups
A lookup type is reusable for attributes stored in multiple tables.
Enable lookups based on the following.
Selecting an Enabled check box
Specifying an enabled start date, end date, or both
Specifying a reference data setdeterminant
If you make changes to a lookup, users must sign out and back in before the changes take effect. When defining a list of
values for display rather than validation, limit the number of enabled lookup codes to a usable length.
For more information on the predefined lookups and lookup codes, open the Setup and Maintenance work area, and use the
tasks in the Define Lookups task list.
Translating Lookups
You can translate the lookups that you defined to the preferred language(s) without changing the language session of the
application. Use the translation option available on the lookup code table. By default, for each lookup, all the permitted
language rows in the translator dialog box appear in the source language (the current session language). When you edit a
particular language entry, you can modify the translated meaning and description to the language in which you want the
lookup to appear. Once the updates are made, the end-users can view the lookup in the translated text.
50
Note: You can add the translation for only as many languages as are permitted by the administrator. The
functionality to limit the number of languages displayed on the dialog box is controlled through the Translation
Editor Languages profile option. It can be set at the SITE or USER level. If nothing is specified, all active
languages are displayed.
Related Topics
Modules in Application Taxonomy: Explained
Managing a Standard Lookup: Example

Creating a new standard lookup involves creating or selecting a lookup type containing the lookup code. The task also
involves determining appropriate values for the lookup codes and their meanings. You can only create or edit lookup codes
for a particular lookup type if its customization level supports it.
Creating a Lookup Type Called COLORS

Your enterprise needs a list of values for status to be used on a process. The lookups are colors, so the lookup type you
create is COLORS. The following table lists a mapping between the lookup type parameters and the actual values assigned to
those parameters to create the required list of values.
Lookup type parameters Value
Lookup type name COLORS

Meaning Status

Description Status by color

Module Oracle Fusion Middleware Extensions for Oracle Application

After you define the lookup type, you need to define the lookup codes and their related details. The following table lists the
lookup codes you define for the COLORS lookup type.
Lookup Code Meaning Enabled Display Sequence
BLUE Urgent No 4

RED Stop Yes 1

GREEN Proceed Yes 3

YELLOW Check Yes 2

51
The Resulting Data Entry List of Values

Only the enabled lookup codes appear in the list of values for the COLORS lookup type. You must select one of them to
complete the activity.
The following table lists the meanings and the codes that were enabled. They appear in the order of the defined display
sequence.
Meaning Lookup Code
Stop RED

Check YELLOW

Proceed GREEN

Analysis
The BLUE lookup code was not enabled and does not appear in the list of values. The display sequence of values in the list of
values is alphabetic, unless you enter a number manually to determine the order of appearance. Number 1 indicates the first
value that appears in the list. Only lookups that are enabled and active between start and end dates are visible.
The Transaction Table

When users enter one of the values from the list of values for the lookup type COLORS, the transaction table records
the lookup code. The following table contains an example, where the lookup code is stored in the Status column of the
transaction table.
Transaction number User name Status
1 Jane RED

2 Bob YELLOW

3 Alice BLUE

The status for one user is BLUE because at the time they entered a value, BLUE was enabled. Disabling a lookup code does
not affect transaction records in which that code is stored. Data querying and reporting have access to disabled lookup
codes in transaction tables.
Managing Set-Enabled Lookups: Examples

Creating a new set-enabled lookup is similar to creating a standard lookup with the addition of specifying a reference data set
determinant for the lookup codes. You can only create or edit lookup codes for a particular lookup type if its customization
level supports it.
52
The reference data set for a set-enabled lookup code is part of its foreign key. This is unlike other set-enabled entities. Use
the Manage Set Assignments task to define and manage reference data set assignments.
Selecting a Reference Group for a Set-Enabled Lookup Type

Specify a reference group for a set-enabled lookup type to indicate which reference data set assignments are available for its
lookup codes. For example a COLORS lookup type might be set-enabled for a Countries reference group that includes the
US and EU reference data set assignments.
Selecting a Reference Data Set for a Set-Enabled Lookup

The reference data set determines which lookup code is included in the list of values. For example, there are two references
data sets - one for the US and the other for EU. If a COLORS lookup type contains RED, YELLOW, ORANGE, and GREEN
lookup codes, you can enable one RED lookup code from the US reference data set and another RED lookup from the EU
reference data, each lookup code having different meanings.
The following table elaborates the example, how these two reference data sets (US and EU) contain one lookup code that is
common, but each differing in its lookup meaning.
Reference Data Set Lookup Code Lookup Meaning
US RED Red

US YELLOW Yellow

US GREEN Green

EU RED Rouge

EU ORANGE Orange

Some lookup codes may be unique to one or another reference data set as the ORANGE lookup is to the EU reference data
set in the example.
In another example in the following table, a lookup type called HOLD_REASON provides a list of reasons for putting a
contract renewal on hold. Reference data sets determine which codes are included in the Hold Reason list of values.
US SEC SEC Compliance Review

US DIR Needs Director's Approval

US VP Needs Vice President's Approval

CHINA CSRC Pending China Securities Regulatory

Commission Review

CHINA PR Needs President's Approval

53
COMMON REQUESTED Customer Request

Referring to the example in the table, when end-users place a contract on hold in the US business unit, the three reason
codes in the US set are available. When placing a contract on hold in the China business unit, the two codes in the China set
are available.
FAQs for Define Lookups

How can I access predefined lookups?
Search for predefined lookups using the Define Lookups task list:
1. In the Setup and Maintenance work area, search for the Define Lookups task list and expand it to view the tasks.
2. Open the task that corresponds to the lookups you are searching for.
3. Enter any of the search parameters and click Search. If you don't know the lookup type or the meaning, use the
Module field to filter search results.
4. Click a lookup type to view its lookup codes.
Tip: Click the Query By Example icon to filter the lookup codes.
Related Topics
Using Query By Example: Procedure
How can I edit lookups?

On the Define Lookups page, you can edit the existing lookup codes of a lookup type or add new lookup codes. To open the
page, navigate to the Setup and Maintenance work area and search for the Define Lookup task list.
The task list contains three tasks:
Standard Lookups
Common Lookups
Set-enabled Lookups
Each task contains a predefined set of lookup types classified and stored as per the functionality. Open a task to search and
edit the required lookup. However, you may not be able to edit a lookup if its customization level doesn't support editing.
Why can't I see my lookup types?

Lookup types are classified using tasks that involve a group of related lookups, such as Manage Geography Lookups. Each
task gives you access only to certain lookup types. However, the generic tasks provide access to all lookups types of a kind,
such as common lookups associated with the Manage Common Lookups task.
If the lookup types in an application are available in the standard, common, or set-enabled lookups view, they are central
to an application. However, lookup types defined for a specific application are managed using the task or task list for that
application.
54
What's the difference between a lookup type and a value set?

A lookup type consists of lookups that are static values in a list of values. Lookup code validation is a one to one match.
A table-validated value set may consist of values that are validated through a SQL statement, which allows the list of values to
be dynamic. The following table brings out the differences between a lookup type and a value set.
Tip: You can define a table-validated value set on any table, including the lookups table. Thus, you can change
a lookup type into a table-validated value set that can be used in flexfields.
Area of Difference Lookup Type Value Set
List of values Static Dynamic if the list is table-validated

Validation of values One to one match of meaning to code Validation by format or inclusion in a table
included in a lookup view, or through the
determinant of a reference data set

Format type of values char varchar2, number, and so on

Length of value Text string up to 30 characters Any type of variable length from 1 to 4000

Duplication of values Never. Values are unique. Duplicate values allowed

Management Both administrators and end-users manage Usually administrators maintain these, except
these, except system lookups or predefined some product flexfield codes, such as GL for
lookups at the system customization level, Oracle Fusion General Ledger that the end-
which can't be modified. users maintain.

Both lookup types and value sets are used to create lists of values from which users select values.
A lookup type cannot use a value from a value set. However, value sets can use standard, common, or set-enabled lookups.
What's a lookup tag used for?

A tag is an additional label attached to the lookup. Tags are user defined and can be grouped depending on the user's
requirement to make search convenient and effective.
The same tag may be used across lookup categories. In such cases, tags are used as a refined search criterion to filter
information across several groups and get the custom search result.
How can I search for a specific lookup code?

Use the Query By Example functionality to sort through hundreds of lookup codes for a lookup type, and display a specific
lookup code. Enter the first few characters of the lookup code value in any of the relevant fields to filter the records.
Note: The search functionality is case sensitive.
55
Manage Descriptive Flexfields
Descriptive Flexfields: Explained

Use descriptive flexfields to add custom attributes to business object entities, and define validation for them.
All the business object entities that you can use in the application are enabled for descriptive flexfields. However, configuring
descriptive flexfields is an optional task.
Context
A descriptive flexfield can have only one context segment to provide context sensitivity. The same underlying database
column can be used by different segments in different contexts.
For example, you can define a Dimensions context that uses the following attributes:
ATTRIBUTE1 column for height

ATTRIBUTE2 column for width
ATTRIBUTE3 column for depth
You can also define a Measurements context that uses the same columns for other attributes:
ATTRIBUTE1 column for weight

ATTRIBUTE2 column for volume
ATTRIBUTE3 column for density
Segments and Contexts

The following table lists the different types of descriptive flexfield segments.
Segment Type Run Time Appearance
Global segment Always available

Context segment Determines which context-sensitive segments are displayed

Context-sensitive segment Displayed depending on the value of the context segment

56
The following figure displays a descriptive flexfield having one context segment called Category for which there are three
values: Resistor, Battery, and Capacitor. Additionally, the descriptive flexfield comprises two global segments that appear in
each context, and three context-sensitive segments that only appear in the specific context.
Context-
Context Global sensitive
segment segments segments
Attributes: Category G1 G2 A3 A4 A5
Context: Context:
Resistor Capacitor
Context:
Battery
G1 G1
G2 G2
A3 A4
A4 A5
G1
G2
A3
A4
A5
Application development determines the number of segments available for configuring. During implementation, configure the
flexfield by determining the following:
Attributes to add using the available segments

Context values
The combination of attributes in each context
Value Sets
For each global and context-sensitive segment, you configure the values permitted for the segment. Based on it, the values
that end users enter are validated, including interdependent validation among the segments.
Protected Descriptive Flexfield Data

Application developers may mark some data configurations in a descriptive flexfield as protected, indicating that you can't
edit them.
57
Related Topics
Value Sets: Explained
Managing Flexfields: Points to Consider
Planning Descriptive Flexfields: Points to Consider

Once you have identified a flexfield to configure, plan the configuration in advance. Compile a list of the UI pages and other
artifacts in your deployment that are affected by the configuration. Verify that you are provisioned with the roles needed to
view and configure the flexfield. View the flexfield using the Highlight Flexfields command in the Administration menu while
viewing the run time page where the flexfield appears. Plan how you will deploy the flexfield for test and production users.
Review the tools and tasks available for managing flexfields, such as the Define Flexfields task list, Manage Sandboxes, and
Highlight Flexfields for adding and editing flexfield segments.
Planning a descriptive flexfield can involve the following tasks:
1. Identify existing parameters.
2. Identify existing context values and whether the context value is derived.
3. Identify custom attributes and plan the descriptive flexfield segments, segment properties, and structure.
4. Plan validation rules.
5. Plan initial values.
6. Plan attribute mapping to Oracle Business Intelligence objects.
Identify Existing Descriptive Flexfield Parameters

Some descriptive flexfields provide parameters that can be used to specify the initial value of a descriptive flexfield segment.
The parameter is external reference data, such as a column value or a session variable. For example, if a flexfield has a user
email parameter, you can configure the initial value for a customer email attribute to be derived from that parameter.
Review the list of available parameters in the Derivation Value field in the Create Segment page for a descriptive flexfield. If
you decide to use one of the parameters to set an initial value, select that parameter from the Derivation Value drop-down
list when you add the descriptive flexfield segment.
Evaluate Whether the Context Value Is Derived

The context value for a descriptive flexfield might have been preconfigured to be derived from an external reference. For
example, if the context is Marriage Status, then the value might be derived from an attribute in the employee business object.
When the context value is derived, you might need to take the derived values and their source into consideration in your plan.
To determine whether the context value is derived, access the Edit Descriptive Flexfield task to view the list of configured
context values for the flexfield. The Derivation Value field in the Context Segment region displays a list of available parameters.
If context values have been preconfigured, see Oracle Applications Cloud Help for product-specific information about the use
of those values.
Plan the Segments, Segment Properties, and Structure

Identify the custom attributes you need for a business object to determine the segments of the descriptive flexfield. Determine
the segment properties such as the prompt, display type, or initial value.
The structure of the descriptive flexfield is determined by its global, context, and context-sensitive segments. Plan a global
segment that captures an attribute for every instance of the business object. Plan a context for segments that depend on
a condition of situation applying to a particular instance of the business object. Plan context-sensitive segments to capture
attributes that are relevant in the context.
58
There is only one context segment available for descriptive flexfields. If you have more than one group of custom attributes
where you could use the context segment, you will have to pick one group over the others, based on your company's needs
and priorities, and add the other custom attributes as global segments.
Plan Validation Rules

Define each segment's validation rules and check if value sets exist for those rules or you must create new ones. If you must
create a value set, you can create it either before configuring the flexfield or while creating or editing a segment.
When determining a segment's validation rules, consider the following questions:
What is the data type - character, date, date and time, or number?
Does the segment require any validation beyond data type and maximum length?
Should a character type value be restricted to digits, or are alphabetic characters allowed?
Should alphabetic characters automatically be changed to uppercase?
Should numeric values be zero-filled?
How many digits can follow the radix separator of a numeric value? In base ten numeric systems, the radix separator
is decimal point.
Does the value need to fall within a range?
Should the value be selected from a list of valid values? If so, consider the following questions:
Can you use an existing application table from which to obtain the list of valid values, or do you need to create
a custom list?
If you are using an existing table, do you need to limit the list of values using a WHERE clause?
Does the list of valid values depend on the value in another flexfield segment?
Is the list of valid values a subset of another flexfield segment's list of values?
Plan Initial Values

For every segment, list the constant value or SQL statement, if any, to use for the initial value of the custom attribute.
Plan How Segments Map to Oracle Business Intelligence Objects

You can extend descriptive flexfields into Oracle Transactional Business Intelligence (OTBI) for ad hoc reporting purposes.
Determine the descriptive flexfield segments to be made available for reporting, and select the BI Enabled check box
accordingly on the Manage Descriptive Flexfields page. You must run a process to extend the BI enabled segments into
OTBI. For more information about extending the BI enabled segments into OTBI, see the Setup and Configuration chapter in
the Oracle Transactional Business Intelligence Administrator's Guide.
Depending on the reporting needs, you may map similar context-sensitive attributes from different contexts to the same
attribute in OTBI. For example, there may be a segment tracking the Product Color attribute in different contexts of a context
sensitive descriptive flexfield. You can use segment labels to map these context-sensitive attributes together by defining a
segment label and updating the BI Label list accordingly.
Related Topics
Flexfield Segment Properties: Explained
Deriving and Setting Default Segment Values: Explained
59
Managing Descriptive Flexfields: Points to Consider

Configuring descriptive flexfields involves managing the available flexfields registered with your Oracle Applications Cloud
database and configuring their flexfield-level properties, defining and managing descriptive flexfield contexts, and configuring
global and context-sensitive segments.
Every descriptive flexfield is registered to include a context segment, which you may choose to use or not.
In general, configuring descriptive flexfields involves:

1. Creating segment labels for business intelligence enabled flexfields.
2. Configuring global segments by providing identity information, the initial default value, and the display properties.
3. Configuring the context segment by specifying the prompt, whether the context segment should be displayed, and
whether a value is required.
4. Configuring contexts by specifying a context code, description, and name for each context value, and adding its
context-sensitive segments, each of which is configured to include identifying information, the column assignment,
the initial default value, and the display properties.
The following aspects are important in understanding descriptive flexfield management:
Segments
Adding segments to highlighted descriptive flexfields
Usages
Parameters
Delimiters
Initial Values
Business Intelligence
Segments
You can assign sequence order numbers to global segments and to context-sensitive segments in each context. Segment
display is always in a fixed order. You cannot enter a number for one segment that is already in use for a different segment.
Value sets are optional for context segments and follow specific guidelines:
The value set that you specify for a context segment consists of a set of context codes.
Each context code corresponds to a context that is appropriate for the descriptive flexfield.
The value set must be independent or table-validated.
If table-validated, the WHERE clause must not use the VALUESET.value_set_code or SEGMENT.segment_code
bind variables.
The value set must be of data type Character with the maximum length of values being stored no larger than the
context's column length.
If you don't specify a value set for a context segment, the valid values for that context segment are derived from the
context codes. The definition of each context segment specifies the set of context-sensitive segments that can be
presented when that context code is selected by the end user.
For reasons of data integrity, you cannot delete an existing context. Instead, you can disable the associated context
value in its own value set by setting its end date to a date in the past.
You can configure the individual global segments and context-sensitive segments in a descriptive flexfield. These
segment types are differentiated by their usage, but they are configured on application pages that use most of the
same properties.
60
Adding Segments to Highlighted Descriptive Flexfields

When you highlight flexfields on a run time page and use an Add Segment icon button to create a segment, the segment
code, name, description, table column, and sequence number are set automatically. If you use an Add Segment icon button
to configure descriptive flexfield segments, you cannot use an existing value set. Value sets are created automatically when
you add the segments. You can enter the valid values, their descriptions, and the default value or specify the formatting
constraints for the value set, such as minimum and maximum values.
Depending on display type, the value set you create using the Add Segment icon button is either an independent value set
or a format-only value set. The following table shows which type of value set is created depending on the segment display
component you select.
Display Component Value Set Created Using Add Segment
Check Box Independent

Drop-down List Independent

List of Values Independent

Radio Button Group Independent

Text Field With Search Independent

Text box Format Only

Text area Format Only

Date/Time Format Only

Tip: After you add a context value, refresh the page to see the new value.
Usages
Descriptive flexfield usages allow for the same definition to be applied to multiple entities or application tables, such as a
USER table and a USER_HISTORY table. Descriptive flexfield tables define the placeholder entity where the flexfield segment
values are stored once you have configured the descriptive flexfield. When you configure a flexfield, the configuration applies
to all its usages.
Parameters
Some descriptive flexfields provide parameters, which are attributes of the same or related entity objects. Parameters are
public arguments to a descriptive flexfield. Parameters provide outside values in descriptive flexfield validation. You use
parameters to set the initial value or derivation value of an attribute from external reference data, such as a column value or
a session variable, rather than from user input. Parameters can be referenced by the logic that derives the default segment
value, and by table-validated value set WHERE clauses.
61
Delimiters
A segment delimiter or separator visually separates segment values when the flexfield is displayed as a string of concatenated
segments.
Initial Values
The SQL statement defining an initial value must be a valid statement that returns only one row and a value of the correct
type.
You can use two types of SQL statements:
SQL statement with no binding. For example, select MIN(SALARY) from EMPLOYEES.
SQL statement with bind variables. You can use the following bind variables in the WHERE clause of the SQL
statement.
:{SEGMENT.<segment_code>}: Identifies a segment in the same context.

:{CONTEXT.<context_code>;SEGMENT.<segment_code>}: Identifies a segment in a different context. The
context must be in the same category or in an ancestor category, and it cannot be a multiple-row context.
:{VALUESET.<value_set_code>}: Identifies the closest prior segment in the same context that is assigned to
the specified value set.
:{FLEXFIELD.<internal_code>}: Identifies a flexfield.
For more information about using bind variables, see the help for value sets.
Selecting a global, context, or context-sensitive segment's BI Enabled check box specifies that the segment is available for
use in Oracle Business Intelligence.
When the flexfield is imported into Oracle Business Intelligence, the label you selected from the BI Label drop-down list
equalizes the segment with segments in other contexts, and maps the segment to the logical object represented by the label.
Related Topics
Defining Value Sets: Critical Choices
Why can't I edit my flexfield or value set configuration?
Enabling Descriptive Flexfield Segments for Business Intelligence:

Points to Consider
A descriptive flexfield that is registered in the database as enabled for Oracle Business Intelligence (BI) includes a BI Enabled
setting for each of its segments. When a global, context, or context-sensitive segment is BI-enabled, it is available for use in
Oracle Business Intelligence.
The following aspects are important in understanding BI-enabled flexfield segments:
Flattening business components to use BI-enabled segments in Oracle BI
62
Equalizing segments to prevent duplication and complexity in the flattened component

Mapping attributes of flattened business components to logical objects in Oracle BI
Managing the labels that map segments to logical objects in Oracle BI
After you deploy a business intelligence-enabled flexfield, use the Import Oracle Fusion Data Extensions for Transactional
Business Intelligence process to import the flexfield changes into the Oracle Business Intelligence repository. Users can make
use of the newly-generated attributes in business intelligence applications. For example, a user can generate a report that
includes attributes added by the descriptive flexfield. For additional information about logical objects and import, refer to the
Oracle Transactional Business Intelligence Administrator's Guide.
Flattening
When you deploy a business intelligence-enabled descriptive flexfield, the deployment process generates an additional
set of flattened Application Development Framework (ADF) business components in addition to the usual ADF business
components and ADF faces run time artifacts that are generated during deployment. The flattened business components
include attributes for business intelligence-enabled segments only. Flattening means each custom column in each context
shows up as an attribute in an Oracle Business Intelligence folder.
Flattened components include one attribute for the BI-enabled context-segment, and one attribute for each business
intelligence-enabled global segment. For BI-enabled context-sensitive segments, consider the following:
If you assigned a label to the segment, the flattened components include an additional single attribute representing
segments with that label.
If you didn't assign a label, the flattened components include a discrete attribute for each BI-enabled context-
sensitive segment in each context.
Mapping to Logical Objects in Business Intelligence

You can simplify reporting by representing similar segments as a single logical object in Business Intelligence.
If you assign a label to any set of context-sensitive segments that serve the same purpose in different contexts, you can
consolidate or equalize the segments into a single attribute. This prevents duplication and the extra workload and complexity
that result from the flattening process. For example, a United States context might have a Passport segment and a Canada
context might have Visa segment. If you assign the NationalID segment label to both the Passport and Visa segments, they
are equalized into the same NationalID attribute in the flattened business component.
Non-labeled context-sensitive segments aren't equalized across context values, so the flattened components include a
separate attribute for each context-sensitive segment for each context value. It may not be possible to equalize similarly
labeled segments if they have incompatible data types or value set types.
Assign a label to a global segment, context segment, or context-sensitive segment to map the corresponding attribute in the
flattened components to a logical object in Oracle Business Intelligence. Using labels to map segments to BI logical objects
minimizes the steps for importing the flexfield into Oracle Business Intelligence.
Note: Assigning a label to a context-sensitive segment serves to equalize the attribute across contexts, as well
as map the equalized attribute to business intelligence.
Managing Labels
You may assign a predefined label (if available) to segments or create new labels for assignment, as needed. Specify a
code, name, and description to identify each label. In the BI Object Name field, enter the name of the logical object in Oracle
Business Intelligence to which the segment label should map during import. Specifying the BI logical object minimizes the
63
steps for importing the flexfield into Oracle Business Intelligence and helps to equalize context-sensitive segments across
contexts.
If no labels are assigned to a BI-enabled segment, or the BI Object Name on the assigned label doesn't exist in business
intelligence, you must manually map the segment to the desired logical object when importing into Oracle Business
Intelligence.
In addition, context-sensitive segments without labels cannot be equalized across context values. The flattened components
include a separate attribute for each non-labeled context-sensitive segment in each context.
Importing to Oracle Business Intelligence Repository

After you deploy a business intelligence-enabled flexfield, import the flexfield changes into the Oracle Business Intelligence
repository to make use of the newly flattened business components in business intelligence and then propagate the flexfield
object changes. When you import the metadata into the Oracle Business Intelligence repository, you must do so as the
FUSION_APPS_BI_APPID user.
To import flexfield changes into the Oracle Business Intelligence repository in Oracle Cloud implementations, run the Import
Oracle Fusion Data Extensions for Transactional Business Intelligence process. For additional information about import, refer
to the Oracle Transactional Business Intelligence Administrator's Guide.
Note: When you import a flexfield into the Oracle Business Intelligence repository, you see both <name>_ and
<name>_c attributes for each segment, along with some other optional attributes. The <name> attribute contains
the value. The <name>_c attribute contains the code of the value set that the value comes from, and is used for
linking to the value dimension. You must import both attributes.
Related Topics
Enabling Key Flexfield Segments for Business Intelligence: Points to Consider
FAQs for Manage Descriptive Flexfields

How can I access predefined flexfields?
Search for predefined flexfields using the Define Flexfields task list:
1. In the Setup and Maintenance work area, search for the Define Flexfields task list and expand it to view the tasks.
2. Open the task that corresponds to the flexfields you are searching for.
3. Enter any of the search parameters and click Search.
Tip: If you don't know the flexfield name or the code, use the Module field to filter search results.
4. Click a flexfield to view its details.
Define Profile Options
64
Hierarchy in Profile Levels: Explained

The hierarchy in profile levels determines the context for making a profile option effective.
You can enable a profile option at the following levels:
Site level (lowest): The entire site of deployment
User level (highest): A specific user
After you create or edit a profile option on the Manage Profile Options page, you must enable it. You can enable it at multiple
levels. The setting at the highest enabled level takes precedence over the lower levels. User level is the highest in the
hierarchy and always takes precedence over the settings at the site level.
On the Manage Administrative Profile Values page, set the profile value at any of the enabled levels of the profile option.
Example of Profile Option Hierarchy

The following table shows an example of setting the currency profile option at different levels.
Profile Level Hierarchy Currency
Site Lowest Euro

User Highest US Dollar

For this example, there are two users, John and Lisa. For John, the user-level profile value currency is set to US Dollar. If the
Currency profile option is enabled only at the site level, both John and Lisa would see Euro as the default currency. If the
profile option is enabled at the user level, users having a different currency set as their currency profile value would see only
that currency. In this case, John would see US Dollar as the default currency. If the Currency profile option is enabled at the
user level and there is no user level currency defined, the site level setting takes effect. When both site and user levels are
enabled, the value for the user level takes precedence over the site level value.
Managing Profile Categories: Points to Consider

You can create profile categories to group profile options based on their functional similarities and their use. In the Setup and
Maintenance work area, search for the Manage Profile Categories task.
Profile categories help administrators or implementors in retrieving profile options using a search criterion on the Manage
Administrator Profile Values page.
Managing Profile Categories

Consider the following options while managing profile categories:
Create profile categories and add existing profile options to them
Add newly created profile options to existing custom profile categories
Note: While you can add a profile option to more than one category, some profile categories are predefined and
restricted from any modifications. So, you can't edit them or add profile options to them.
65
Setting Display Sequence for the Profile Options

You must set the display sequence for each profile option that you add to a profile category. Display sequence determines
the order in which the profile options appear in a search result, based on the profile category. You can set the sequence
beginning with zero or one for the first profile option to display, and proceed sequentially to assign the values to the remaining
profile options.
The following table demonstrates the effect of the display sequence on the profile options when they are retrieved as search
results.
Profile Category Included Profile Option - Assigned Display Display Sequence of Profile Options in the
Sequence Search Results
Attachments Attachment File Directory - 2 1. Indicate Attachments

Indicate Attachments - 1 2. Attachment File Directory
Setting Profile Option Values: Procedure

Each profile option contains specific values that determine how it affects the application. You can add or modify the values
for each profile option. Select or enter the value for one or more of the available levels (site, product, and user) so that each
setting takes effect at the intended level.
Setting the Profile Value

1. In the Setup and Maintenance work area, search for and open the Manage Administrator Profile Values task.
2. Search for and select the profile option.
3. In the Profile Values section, click Add. A new row is added for you to specify the following conditions:
Profile Level: Specify the level at which the profile value is to be set. If the profile value applies to the entire site,
select Site.
Product Name: If you select Product as the profile level, select a product and specify the associated profile
value.
User Name: If you select User as the profile level, select the user name and specify the associated profile
value.
Profile Value: Select or enter the value corresponding to the selected profile level.
Note: For an existing entry, you can modify only the profile value.
4. Repeat step 3 to add more rows and set the profile values.
5. Click Save and Close.
Note: Changes in the profile values take effect for a user on the next sign in.
66
FAQs for Define Profile Options

How can I access predefined profile options?
Search for predefined profile options using the Define Profiles task list:
1. In the Setup and Maintenance work area, search for the Manage Profile Options task and open it.
2. Enter any of the search parameters and click Search.
Tip: If you don't know the profile option code or the display name, use the Application or Module fields
to filter search results.
3. Click a profile option to view its details.
67
68
Implementing Enterprise Structures and General Ledger Geographies
4 Geographies
Define Geographies: Overview

Setting up your geography structure and master geographies correctly in the Trading Community Model is critical to the
proper utilization 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 to ensure accurate transaction tax calculation.
You can either define your geography structure and corresponding master geographies manually or import these geography
entities. Options include using 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 Financials Cloud Implementing Common Features 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, you can 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 no invalid or incomplete master address data is
created 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
Geography Structure, Hierarchy, and Validation: How They Fit Together
Managing Geography Structures, Hierarchies, and Validation: Worked Example
Importing Geographies Using File-Based Import: Explained
69
Implementing Enterprise Structures and General Ledger Geographies
Oracle Financials Cloud Implementing Common Features
70
Implementing Enterprise Structures and General Ledger Legal Entities
5 Legal Entities
Legal Entities: Explained
A legal entity is a recognized party with rights and responsibilities given by legislation.
Legal entities have the following rights and responsibilities to:
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.
A legal entity has responsibility for elements of your enterprise for the following reasons:
Facilitating local compliance
Minimizing the enterprise's tax liability
Preparing for acquisitions or disposals of parts of the enterprise
Isolating one area of the business from risks in another area. For example, your enterprise develops property and
also leases properties. You could operate the property development business as a separate legal entity to limit risk to
your leasing business.
The Role of Your Legal Entities

In configuring your enterprise structure in Oracle Fusion Applications, the contracting party on any transaction is always the
legal entity. Individual legal entities:
Own the assets of the enterprise
Record sales and pay taxes on those sales
Make purchases and incur expenses
Perform other transactions
Legal entities must comply with the regulations of jurisdictions, in which they register. Europe now allows for companies to
register in one member country and do business in all member countries, and the US allows for companies to register in one
state and do business in all states. To support local reporting requirements, legal reporting units are created and registered.
You are required to publish specific and periodic disclosures of your legal entities' operations based on different jurisdictions'
requirements. Certain annual or more frequent accounting reports are referred to as statutory or external reporting. These
reports must be filed with specified national and regulatory authorities. For example, in the United States (US), your publicly
owned entities (corporations) are required to file quarterly and annual reports, as well as other periodic reports, with the
Securities and Exchange Commission (SEC), which enforces statutory reporting requirements for public corporations.
Individual entities privately held or held by public companies do not have to file separately. In other countries, your individual
entities do have to file in their own name, as well as at the public group level. Disclosure requirements are diverse. For
71
example, your local entities may have to file locally to comply with local regulations in a local currency, as well as being
included in your enterprise's reporting requirements in different currency.
A legal entity can represent all or part of your enterprise's management framework. For example, if you operate in a large
country such as the United Kingdom or Germany, you might incorporate each division in the country as a separate legal
entity. In a smaller country, for example Austria, you might use a single legal entity to host all of your business operations
across divisions.
Legal Entity in Oracle Fusion: Points to Consider

Oracle Fusion Applications support the modeling of your legal entities. If you make purchases from or sell to other legal
entities, define these other legal entities in your customer and supplier registers. These registers are part of the Oracle Fusion
Trading Community Architecture.
When your legal entities are trading with each other, represent them as legal entities and as customers and suppliers in
your customer and supplier registers. Use legal entity relationships to determine which transactions are intercompany and
require intercompany accounting. Your legal entities can be identified as legal employers and therefore, are available for use in
Human Capital Management (HCM) applications.
Several decisions you should consider when you create legal entities.
The importance of using legal entity on transactions
Legal entity and its relationship to business units
Legal entity and its relationship to divisions
Legal entity and its relationship to ledgers
Legal entity and its relationship to balancing segments
Legal entity and its relationship to consolidation rules
Legal entity and its relationship to intercompany transactions
Legal entity and its relationship to worker assignments and legal employer
Legal entity and payroll reporting
Legal reporting units
The Importance of Using Legal Entities on Transactions

All of the assets of the enterprise are owned by individual legal entities. Oracle Fusion Financials allow your users to enter legal
entities on transactions that represent a movement in value or obligation.
For example, a sales order creates an obligation on the legal entity that books the order to deliver the goods on the
acknowledged date. The creation also creates an obligation on the purchaser to receive and pay for those goods. Under
contract law in most countries, damages can be sought for both:
Actual losses, putting the injured party in the same state as if they had not entered into the contract.
What is called loss of bargain, or the profit that would have made on a transaction.
In another example, if you revalued your inventory in a warehouse to account for raw material price increases, the revaluation
and revaluation reserves must be reflected in your legal entity's accounts. In Oracle Fusion Applications, your inventory within
an inventory organization is managed by a single business unit and belongs to one legal entity.
72
Legal Entity and Its Relationship to Business Units

A business unit can process transactions on behalf of many legal entities. Frequently, a business unit is part of a single legal
entity. In most cases, the legal entity is explicit on your transactions. For example, a payables invoice has an explicit legal
entity field. Your accounts payables department can process supplier invoices on behalf of one or many business units.
In some cases, your legal entity is inferred from your business unit that is processing the transaction. For example, Business
Unit ACM UK has a default legal entity of InFusion UK Ltd. When a purchase order is placed in ACM UK, the legal entity
InFusion UK Ltd is legally obligated to the supplier. Oracle Fusion Procurement, Oracle Fusion Project Portfolio Management,
and Oracle Fusion Supply Chain applications rely on deriving the legal entity information from the business unit.
Legal Entity and Its Relationship to Divisions

The division is an area of management responsibility that can correspond to a collection of legal entities. If wanted, you can
aggregate the results for your divisions by legal entity or by combining parts of other legal entities. Define date-effective
hierarchies for your cost center or legal entity segment in your chart of accounts to facilitate the aggregation and reporting by
division. Divisions and legal entities are independent concepts.
Legal Entity and Its Relationship to Ledgers

One of your major responsibilities is to file financial statements for your legal entities. Map legal entities to specific ledgers
using the Oracle Fusion General Ledger Accounting Configuration Manager. Within a ledger, you can optionally map a legal
entity to one or more balancing segment values.
Legal Entity and Its Relationship to Balancing Segments

Oracle Fusion General Ledger supports up to three balancing segments. Best practices recommend one segment represents
your legal entity to ease your requirement to account for your operations to regulatory agencies, tax authorities, and investors.
Accounting for your operations means you must produce a balanced trial balance sheet by legal entity. If you account for
many legal entities in a single ledger, you must:
1. Identify the legal entities within the ledger.
2. Balance transactions that cross legal entity boundaries through intercompany transactions.
3. Decide which balancing segments correspond to each legal entity and assign them in Oracle Fusion General
Ledger Accounting Configuration Manager. Once you assign one balancing segment value in a ledger, then all
your balancing segment values must be assigned. This recommended best practice facilitates reporting on assets,
liabilities, and income by legal entity.
Represent your legal entities by at least one balancing segment value. You may represent it by two or three balancing
segment values if more granular reporting is required. For example, if your legal entity operates in multiple jurisdictions in
Europe, you might define balancing segment values and map them to legal reporting units. You can represent a legal entity
with more than one balancing segment value. Do not use a single balancing segment value to represent more than one legal
entity.
In Oracle Fusion General Ledger, there are three balancing segments. You can use separate balancing segments to represent
your divisions or strategic business units to enable management reporting at the balance sheet level for each. This solution is
used to empower your business unit and divisional managers to track and assume responsibility for their asset utilization or
return on investment. Using multiple balancing segments is also useful when you know at the time of implementation that you
are disposing of a part of a legal entity and want to isolate the assets and liabilities for that entity.
Implementing multiple balancing segments requires every journal entry that is not balanced by division or business unit, to
generate balancing lines. You cannot change to multiple balancing segments after you begin using the ledger because your
historical data is not balanced by the new balancing segments. Restating historical data must be done at that point.
73
If your enterprise regularly spins off businesses or holds managers accountable for utilization of assets, identify the business
with a balancing segment value. If you account for each legal entity in a separate ledger, no requirement exists to identify the
legal entity with a balancing segment value.
While transactions that cross balancing segments don't necessarily cross legal entity boundaries, all transactions that cross
legal entity boundaries must cross balancing segments. If you make an acquisition or are preparing to dispose of a portion of
your enterprise, you may want to account for that part of the enterprise in its own balancing segment even if the portion is not
a separate legal entity. If you do not map legal entities sharing the same ledger to balancing segments, you cannot distinguish
them using intercompany functionality or track individual equity.
Legal Entity and Its Relationship to Consolidation Rules

In Oracle Fusion Applications you can map legal entities to balancing segments and then define consolidation rules using
your balancing segments. You are creating a relationship between the definition of your legal entities and their role in your
consolidation.
Legal Entity and Its Relationship to Intercompany Transactions

Use Oracle Fusion Intercompany feature to create intercompany entries automatically across your balancing segments.
Intercompany processing updates legal ownership within the enterprise's groups of legal entities. Invoices or journals
are created as needed. To limit the number of trading pairs for your enterprise, set up intercompany organizations and
assign then to your authorized legal entities. Define processing options and intercompany accounts to use when creating
intercompany transactions and to assist in consolidation elimination entries. These accounts are derived and automatically
entered on your intercompany transactions based on legal entities assigned to your intercompany organizations.
Intracompany trading, in which legal ownership isn't changed but other organizational responsibilities are, is also supported.
For example, you can track assets and liabilities that move between your departments within your legal entities by creating
departmental level intercompany organizations.
Tip: In the Oracle Fusion Supply Chain applications, you can model intercompany relationships using business
units, from which legal entities are derived.
Legal Entity and Its Relationship to Worker Assignments and Legal Employer
Legal entities that employ people are called legal employers in the Oracle Fusion Legal Entity Configurator. You must enter
legal employers on worker assignments in Oracle Fusion HCM.
Legal Entity and Payroll Reporting

Your legal entities are required to pay payroll tax and social insurance such as social security on your payroll. In Oracle Fusion
Applications, you can register payroll statutory units to pay and report on payroll tax and social insurance for your legal
entities. As the legal employer, you might be required to pay payroll tax, not only at the national level, but also at the local
level. You meet this obligation by establishing your legal entity as a place of work within the jurisdiction of a local authority.
Set up legal reporting units to represent the part of your enterprise with a specific legal reporting obligation. You can also
mark these legal reporting units as tax reporting units, if the legal entity must pay taxes as a result of establishing a place of
business within the jurisdiction.
74
Creating Legal Entities in the Enterprise Structures

Configurator: Points to Consider
Use the Enterprise Structures Configurator (ESC), to create legal entities for your enterprise automatically, based on the
countries in which divisions of your business operate, or you can upload a list of legal entities from a spreadsheet.
Automatically Creating Legal Entities

If you are not certain of the number of legal entities that you need, you can create them automatically. To use this option, you
first identify all of the countries in which your enterprise operates. The application opens the Map Divisions by Country page,
which contains a matrix of the countries that you identified, your enterprise, and the divisions that you created. You select
the check boxes where your enterprise and divisions intersect with the countries to identify the legal entities that you want
the application to create. The enterprise is included for situations where your enterprise operates in a country, acts on behalf
of several divisions within the enterprise, and is a legal employer in a country. If you select the enterprise for a country, the
application creates a country holding company.
The application automatically creates the legal entities that you select, and identifies them as payroll statutory units and legal
employers. For each country that you indicated that your enterprise operates in, and for each country that you created a
location for, the application also automatically creates a legislative data group.
Any legal entities that you create automatically cannot be deleted from the Create Legal Entities page within the Enterprise
Structures Configurator. You must return to the Map Divisions by Country page and deselect the legal entities that you no
longer want.
Example: Creating Legal Entities Automatically

InFusion Corporation is using the ESC to set up its enterprise structure. The corporation has identified two divisions, one for
Lighting, and one for Security. The Lighting division operates in Japan and the US, and the Security division operates in the
UK and India.
This figure illustrates InFusion Corporation's enterprise structure.
Enterprise
Division Division
Japan US UK India
75
This table represents the selections that InFusion Corporation makes when specifying which legal entities to create on the
Map Divisions by Country page.
Country Enterprise InFusion Lighting InFusion Security
Japan No Yes No

US No Yes No

UK No No Yes

India No No Yes

Based on the selections made in the preceding table, the ESC creates the following four legal entities:
InFusion Lighting Japan LE
InFusion Lighting US LE
InFusion Security UK LE
InFusion Security India LE
Creating Legal Entities Using a Spreadsheet

If you have a list of legal entities already defined for your enterprise, you can upload them from a spreadsheet. To use this
option, you first download a spreadsheet template, then add your legal entity information to the spreadsheet, and then
upload directly to your enterprise configuration. You can export and import the spreadsheet multiple times to accommodate
revisions.
Related Topics
What's an ultimate holding company?
Using Desktop Integrated Excel Workbooks: Points to Consider
Creating Legal Entities, Registrations, and Reporting Units:

Examples
Define a legal entity for each registered company or other entity recognized in law for which you want to record assets,
liabilities, and income, pay transaction taxes, or perform intercompany trading.
Legal Entity
Create a legal entity by following these steps:
1. Navigator > Setup and Maintenance > Manage Legal Entity > Go to Task.
2. Accept the default Country, United States.
76
3. Enter Name, InFusion USA West.

4. Enter Legal Entity Identifier, US0033.
5. Optionally enter Start Date. When the start date is blank the legal entity is effective from the creation date.
6. Optionally enter an End Date.
7. Optionally, if your legal entity should be registered to report payroll tax and social insurance, select the Payroll
statutory unit check box.
8. Optionally, if your legal entity has employees, select the Legal employer check box.
9. Optionally, if this legal entity is not a payroll statutory unit, select an existing payroll statutory unit to report payroll tax
and social instance on behalf of this legal entity.
10. Enter the Registration Information
11. Accept the default Identifying Jurisdiction, United States Income Tax.
12. Search for and select a Legal Address, 500 Oracle Parkway, Redwood Shores, CA 94065.
The legal address must have been entered previously using the Manage Legal Address task.
13. OK.
14. Optionally enter a Place of Registration.
15. Enter the EIN or TIN.
16. Enter the Legal Reporting Unit Registration Number.
17. Save and Close.
18. Navigator > Setup and Maintenance > Define Legal Entries > Manage Legal Entity > Select to set scope.
19. Select the Manage Legal Entity.
20. In the *Legal Entity list, select Select and Add.
21. Click Apply and Go to Task.
22. Select your legal entity.
23. Save and Close on the very bottom of the window.
This sets the scope for your task list to the selected legal entity.
24. Save and Close.
Legal Entity Registrations

A legal entity registration with the same name as that of the legal entity is created by default. To verify this, locate the Manage
Legal Entity Registrations task and then select Go to Task. To create another registration for the legal entity follow these
steps:
1. Navigator > Setup and Maintenance > Manage Legal Entity Registrations: Verify that the Legal Entity scope
value is set correctly.
2. Go to Task.
3. Select Create.
4. Enter Jurisdiction.
5. Enter Registered Address.
6. Enter Registered Name.
7. Optionally enter Alternate Name, Registration Number, Place of Registration, Issuing Legal Authority, and
Issuing Legal Authority Address, Start Date, and End Date.
8. Save and Close.
77
Legal Reporting Unit

When a legal entity is created, a legal reporting unit with the same name as that of the entity is also automatically created. To
create more legal reporting units or modify the settings follow these steps:
1. Navigator > Setup and Maintenance > Define Legal Reporting Unit. > Manage Legal Reporting Unit. Verify that
the Legal Entity scope value is set correctly.
2. Go to Task
3. Select Create.
4. Enter Territory, United States.
5. Enter Name.
6. Optionally enter a Start Date.
7. Enter Registration Information.
8. Search for and select Jurisdiction.
9. Enter Main Legal Reporting Unit information.
10. Select the value Yes or No for the Main Legal Reporting Unit. Set value to yes only if you are creating a new main
(primary) legal reporting unit.
11. Enter the Main Effective Start Date, 1/1/11.
12. Save and Close.
Manage Legal Entity HCM Information
HCM Organization Models: Examples

These examples illustrate different models for human capital management (HCM) organizations that include a legislative data
group (LDG). This example includes LDGs, which aren't an organization classification, to show how to partition payroll data by
associating them with a payroll statutory unit.
Simple Configuration
This example illustrates a simple configuration that does not include any tax reporting units.
Note the following:
The legal employer and payroll statutory units are the same, sharing the same boundaries.
Reporting can only be done at a single level. Countries such as Saudi Arabia and the United Arab Emirates (UAE)
might use this type of model, as these countries report at the legal entity level.
78
This figure illustrates a simple configuration where the enterprise has only one legal entity, which is both a payroll statutory unit
and a legal employer.
Enterprise
Division
Legislative Legal Entity

Data Group
PSU
Legal
Employer
Multiple Legal Employers and Tax Reporting Units

This example illustrates a more complex configuration. In this enterprise, you define one legal entity, InFusion US as a payroll
statutory unit with two separate legal entities, which are also legal employers. This model shows multiple legal employers that
are associated with a single payroll statutory unit. Tax reporting units are always associated with a specific legal employer (or
employers) through the payroll statutory unit.
The implication is that payroll statutory reporting boundaries vary from human resources (HR) management, and you can
categorize the balances separately by one of the following:
Payroll statutory unit

Legal employer
Tax reporting unit
This configuration is based on tax filing requirements, as some tax-related payments and reports are associated with a higher
level than employers. An example of a country that might use this model is the US.
79
This figure illustrates an enterprise that has one payroll statutory unit and multiple legal employers and tax reporting units.
Enterprise
US Division
InFusion US
Legal Entity
USA Legislative
Data Group PSU
US LE 1 InFusion Inc
Legal Entity Legal Entity
Legal Legal
Employer Employer
Tax Reporting
Unit
InFusion Corp USA InFusion Holding

Tax Reporting Unit Tax Reporting Unit
One Payroll Statutory Unit and Two Tax Reporting Units

This model makes no distinction between a legal employer and a payroll statutory unit. You define tax reporting units as
subsidiaries to the legal entity.
In this enterprise, legal entity is the highest level of aggregation for payroll calculations and reporting. Statutory reporting
boundaries are the same for both payroll and HR management. An example of a country that might use this model is France.
80
This figure illustrates an example of an organization with one legal entity. The legal entity is both a legal employer and a payroll
statutory unit and that has two tax reporting units.
Enterprise
Division
InFusion France
Legal Entity
France
Legislative Data PSU
Group
Legal
Employer
InFusion Colombes InFusion Lyon

Tax Reporting Unit Tax Reporting Unit
One Payroll Statutory Unit with Several Tax Reporting Units

In this model, the enterprise has one legal entity. Legal employers and tax reporting units are independent from each other
within a payroll statutory unit, because there is no relationship from a legal perspective. Therefore, you can run reporting on
both entities independently.
Using this model, you wouldn't typically:
Report on tax reporting unit balances within a legal employer

Categorize balances by either or both organizations, as required
An example of a country that might use this model is India.
81
This figure illustrates an enterprise with one legal entity that is a payroll statutory unit and a legal employer. The tax reporting
units are independent from the legal employer.
Enterprise
India Division
InFusion India Pvt. Ltd

Legal Entity
India PSU
Legislative Data
Group
Legal
Employer
InFusion InFusion
Hyderabad Bangalore
Tax Reporting Tax Reporting
Unit Unit
PT1 PT2 PF1 PF2

Tax Tax Tax Tax
Reporting Reporting Reporting Reporting
Unit Unit Unit Unit
ESI1 ESI2 IT1 IT2

Tax Tax Tax Tax
Reporting Reporting Reporting Reporting
Unit Unit Unit Unit
Multiple Payroll Statutory Units with Several Tax Reporting Units

In this model, the enterprise has two legal entities. The legal employers and tax reporting units are independent from each
other within a payroll statutory unit, because there is no relationship from a legal perspective. Therefore, you can run reporting
on both entities independently.
Using this model, you wouldn't typically:
Report on tax reporting unit balances within a legal employer

Categorize balances by either or both organizations, as required
82
An example of a country that might use this model is the United Kingdom (UK).
This figure illustrates an enterprise with two legal entities, and legal employers and tax reporting units are independent from
each other.
Enterprise
Division
Legislative
Data Group
Legal Entity Legal Entity
PSU PSU
Legal
Employer
Tax Tax Legal Entity

Reporting Reporting
Unit Unit Legal
Employer
Related Topics
Legislative Data Groups: Explained
83
Payroll Statutory Units, Legal Employers, and Tax Reporting Units:

How They Work Together
When you set up legal entities, you can identify them as legal employers and payroll statutory units, which makes them
available for use in Oracle Fusion Human Capital Management (HCM). Depending on how your organization is structured, you
may have only one legal entity that is also a payroll statutory unit and a legal employer, or you may have multiple legal entities,
payroll statutory units, and legal employers.
Legal Employers and Payroll Statutory Unit

Payroll statutory units enable you to group legal employers so that you can perform statutory calculations at a higher level,
such as for court orders or for United Kingdom (UK) statutory sick pay. In some cases, a legal employer is also a payroll
statutory unit. However, your organization may have several legal employers under one payroll statutory unit. A legal employer
can belong to only one payroll statutory unit.
Payroll Statutory Units and Tax Reporting Units

Payroll statutory units and tax reporting units have a parent-child relationship, with the payroll statutory unit being the parent.
Tax Reporting Units and Legal Employers

Tax reporting units are indirectly associated with a legal employer through the payroll statutory unit. One or more tax reporting
units can be used by a single legal employer, and a tax reporting unit can be used by one or more legal employers. For
example, assume that a single tax reporting unit is linked to a payroll statutory unit. Assume also that two legal employers are
associated with this payroll statutory unit. In this example, both legal employers are associated with the single tax reporting
unit.
Use the Manage Legal Reporting Unit HCM Information task to designate an existing legal reporting unit as a tax reporting
unit. If you create a new legal reporting unit that belongs to a legal employer (that is not also a payroll statutory unit), you
select a parent payroll statutory unit and then, when you run the Manage Legal Reporting Unit HCM Information task, you
designate it as a tax reporting unit and select the legal employer.
Related Topics
What's a tax reporting unit?
FAQs for Manage Legal Entity HCM Information

What's a legal employer?
A legal employer is a legal entity that employs workers. You define a legal entity as a legal employer in the Oracle Fusion Legal
Entity Configurator.
The legal employer is captured at the work relationship level, and all assignments within that relationship are automatically
with that legal employer. Legal employer information for worker assignments is also used for reporting purposes.
What's a payroll statutory unit?

Payroll statutory units are legal entities that are responsible for paying workers, including the payment of payroll tax and social
insurance. A payroll statutory unit can pay and report on payroll tax and social insurance on behalf of one or many legal
84
entities, depending on the structure of your enterprise. For example, if you are a multinational, multiple company enterprise,
then you register a payroll statutory unit in each country where you employ and pay people. You can optionally register a
consolidated payroll statutory unit to pay and report on workers across multiple legal employers within the same country. You
associate a legislative data group with a payroll statutory unit to provide the correct payroll information for workers.
Manage Legal Entity Tax Profile
Party Tax Profiles: Explained

A tax profile is the body of information that relates to a party's transaction tax activities. A tax profile can include main and
default information, tax registration, tax exemptions, party fiscal classifications, tax reporting codes, configuration options, and
service subscriptions.
Set up tax profiles for the following parties involved in your transactions:
First parties
Third parties
Tax authorities
First Parties
Set up tax profiles for your first-party legal entities, legal reporting units, and business units.
First-party legal entities identify your organization to the relevant legal authorities, for example, a national or international
headquarters. Legal entities let you model your external relationships to legal authorities more accurately. The relationships
between first-party legal entities and the relevant tax authorities normally control the setup of the transaction taxes required
by your business. Under most circumstances, the tax setup is used and maintained based on the configuration of the legal
entity. Enter the default information, party fiscal classifications, tax reporting codes, and configuration options for your legal
entities. You can also specify if you're using the tax services of an external service provider for tax calculation.
First-party legal reporting units identify each office, service center, warehouse, and any other location within the organization
with a tax requirement. A legal reporting unit tax profile is automatically created for the headquarter legal entity. Set up
additional legal reporting unit tax profiles for those needed for tax purposes. For legal reporting units, enter the default
information, tax registrations, party fiscal classifications, and tax reporting codes. Also, define tax reporting details for your
VAT and global tax reporting needs for tax registrations of tax regimes that allow this setup.
Business units organize your company data according to your internal accounting, financial monitoring, and reporting
requirements. To help you manage the tax needs of your business units, you can use the business unit tax profile in either of
two ways:
Indicate that business unit tax setup is used and maintained based on the configuration of the associated legal entity
at transaction time. The tax setup of the associated legal entity setup is either specific to the legal entity or shared
across legal entities using the Global Configuration Owner setup.
Indicate that tax setup is used and maintained by a specific business unit. Create configuration options for the
business unit to indicate that the subscribed tax content is used for the transactions created for the business unit.
For business units that maintain their own setup, enter the default information, tax reporting codes, configuration options, and
service providers as required.
85
Third Parties
Set up third-party tax profiles for parties with the usage of customer, supplier, and their sites. Enter the default information,
tax registrations, party fiscal classifications, and reporting codes required for your third parties or third-party sites. You can set
up tax exemptions for your customers and customer sites.
Banks are also considered third parties. When a bank is created, the tax registration number specified on the bank record is
added to the party tax profile record in Oracle Fusion Tax. You can't modify the party tax profile for a bank as it's view only.
You can only modify the bank record.
Note: You don't need to set up party tax profiles for third parties. Taxes are still calculated on transactions for
third parties that don't have tax profiles.
Tax Authorities
Set up a tax authority party tax profile using the Legal Authorities setup task. The tax authority party tax profile identifies a tax
authority party as a collecting authority or a reporting authority or both. A collecting tax authority manages the administration
of tax remittances. A reporting tax authority receives and processes all company transaction tax reports.
The collecting and reporting tax authorities appear in the corresponding list of values on all applicable Oracle Fusion Tax
pages. All tax authorities are available in the list of values as an issuing tax authority.
Related Topics
Specifying Third-Party Tax Profile Options: Points to Consider
When does a party tax profile get created for a third party?
Specifying First-Party Tax Profile Options: Points to Consider

Set up first-party tax profiles for all legal entities, legal reporting units, and business units in your organization that have a
transaction tax requirements. How you set up your first parties can impact the tax calculation on your transactions.
The first-party tax profile consists of:
Defaults and controls: Applicable to legal entities and legal reporting units. Business units that use their own tax
setup don't have defaults and controls.
Tax registrations: Applicable to legal reporting units.
Party fiscal classifications: Applicable to legal entities and legal reporting units.
Tax reporting codes: Applicable to legal entities, legal reporting units, and business units who don't use the tax setup
of the legal entity.
Configuration options: Applicable to legal entities and business units who don't use the tax setup of the legal entity.
Service subscriptions: Applicable to legal entities and business units who don't use the tax setup of the legal entity.
86
Defaults and Controls

The following table describes the defaults and controls available at the first-party tax profile level:
Option Description
Automatically self-assess taxes on purchases.

Set as self-assessment (reverse
charge)
Rounding Level Perform rounding operations on the:
Header: Applies rounding to calculated tax amounts once for each tax rate per invoice.
Line: Applies rounding to the calculated tax amount on each invoice line.
The rule that defines how the rounding must be performed on a value involved in a taxable
Rounding Rule transaction. For example, up to the next highest value, down to the next lowest value, or nearest.

Note:If you defined a rounding precedence hierarchy in the configuration owner tax option
settings for the combination of configuration owner and event class, Oracle Fusion Tax
considers the rounding details in the applicable tax profile.

This first party intends to send or receive invoices with invoice line amount inclusive of the tax
Set Invoice Values as Tax Inclusive amount.

Note:This option overrides the tax inclusive handling setting at the tax level, but not at the
tax rate level.

Tax Registrations
Set up a separate tax registration to represent each distinct registration requirement for a first-party legal reporting unit.
Oracle Fusion Tax uses tax registrations in tax determination and tax reporting. If your first party has more than one tax
registration under the same tax regime, then the application considers the tax registration in the order: tax jurisdiction; tax; tax
regime.
You must enable the Use tax reporting configuration option on the first-party tax regime to allow entry of global tax
reporting configuration details during tax registration setup for legal reporting units for these tax regimes.
Party Fiscal Classifications

If applicable, associate first-party fiscal classification codes with this party. The party fiscal classification codes you enter
become part of tax determination for invoices associated with this party. Specify start and end dates to control when these
fiscal classifications are applicable for this party and transaction.
For legal entities, you can view the associated legal classifications that were assigned to the tax regime defined for this first
party. The legal classifications are used in the tax determination process, similar to the party fiscal classifications.
Tax Reporting Codes

Set up tax reporting types to capture additional tax information on transactions for your tax reports for your first parties.
Depending on the tax reporting type code, you either enter or select a tax reporting code for this party. Specify start and end
dates to control when these tax reporting codes are applicable.
87
Configuration Options
The legal entities and business units in your organization are each subject to specific sets of tax regulations as designated by
the tax authorities where you do business. Use configuration options to associate legal entities and business units with their
applicable tax regimes. You can set up tax configuration options when you create a tax regime or when you create a party tax
profile. Both setup flows display and maintain the same party and tax regime definitions.
Service Subscriptions
Oracle Fusion Tax lets you use the tax services of external service providers for tax calculation of US Sales and Use Tax on
Receivables transactions. The setup for provider services is called a service subscription. A service subscription applies to the
transactions of one configuration option setup for a combination of tax regime and legal entity or business unit. Set up service
subscriptions when you create a tax regime or when you create a party tax profile for a first-party legal entity or business unit.
Related Topics
Tax Registrations: Explained
Configuration Options: Explained
Setting Tax Reporting Configuration Controls for VAT: Critical Choices
Party Information: Explained
Rounding Precedence Hierarchy: How It's Determined
FAQs for Manage Legal Entity Tax Profile

When does a party tax profile get created for a legal entity?
The legal entity party tax profile is automatically created when a legal entity record is created.
When a legal entity is created through a back-end process, a legal entity party tax profile is created, when you:
Save a tax regime to which the legal tax entity subscribes.

Save the configuration owner tax option that are defined for the legal entity.
You can also create a party tax profile for a legal entity manually. Use the Create Legal Entity Tax Profile page or edit the tax
profile that was automatically generated with the relevant tax information.
Define Legal Reporting Units
Planning Legal Reporting Units: Points to Consider

Each of your legal entities has at least one legal reporting unit. Some legal reporting units can also be referred to as
establishments. You can define either domestic or foreign establishments. Define legal reporting units by physical location,
such as sales offices. For example, set up legal reporting units to represent your company and its offices for tax reporting.
88
Planning Legal Reporting Units

Plan and define your legal reporting units at both the local and national levels if you operate within the administrative
boundaries of a jurisdiction that is more granular than country. For example, your legal entity establishes operations in a
country that requires reporting of employment and sales taxes locally as well as nationally. Therefore, you need more than
one legally registered location to meet this legal entity's reporting requirements in each local area. Additionally, legal entities
in Europe operate across national boundaries, and require you to set up legal reporting units for the purposes of local
registration in each country. There can be multiple registrations associated with a legal reporting unit. However, only one
identifying registration can be defined by the legal authority used for the legal entity or legal reporting unit and associated with
the legal reporting unit.
89
90
Implementing Enterprise Structures and General Ledger Financial Structures
6 Financial Structures
Rapid Implementation
Enterprise Structures Rapid Implementation: Overview

You can use Rapid Implementation spreadsheet template to rapidly implement Oracle Fusion enterprise structures and set up
the following objects:
Chart of accounts, including value sets, value set values, structures, and structure instances
Account hierarchies including trees and tree versions
Accounting calendars (monthly type only)
Legal entities including legal addresses, jurisdictions, and identifiers
Primary ledgers with legal entity assignments to primary balancing segment values
Business units
Document and journal sequencing.
Below are the Functional Setup Manager tasks which are required to be performed to rapidly implement the Oracle Fusion
General Ledger:
Create Chart of Accounts, Ledger, Legal Entities, and Business Units in Spreadsheet: Downloads the rapid
implementation excel spreadsheet template.
Upload Chart of Accounts: Starts the Create Enterprise Structure process from the Scheduled Process page
using the upload data file as a parameter. You must upload your first file, ChartOfAccounts.xml, is created using the
template. Monitor the process for the successful completion.
Deploy Chart of Accounts: Opens the Manage Chart of Accounts Instance page. Select the accounting
flexfield and press the Deploy button to deploy the accounting flexfield.
Upload Ledger, Legal Entities, and Business Units: Starts the Create Enterprise Structure process from
the Scheduled Process page with the upload data file as a parameter. You must upload your second file,
FinancialsCommonEntities.xml, created using the template and monitor for the successful completion of the process.
The following are best practices and recommendations:

Design your chart of accounts carefully, including the number and sequence of segments.
Identify the aspects of your business that you want to track and analyze, such as company, division, cost center,
department, account, and line of business.
Anticipate future growth and reporting requirements by defining one or more future segments. Assign those
segments with a default value to streamline data entry.
Create account hierarchies to reflect managerial, legal, or geographical relationships between your value set values.
Your financial balances are preaggregated at each parent level in your hierarchy, thus allowing fast and robust
account inquiry and drill down.
Note: Once you begin using your chart of accounts, making changes to the segments is neither recommended
nor supported.
91
Preparing and Loading Enterprise Structures Rapid Implementation

Templates: Worked Example
Your company is implementing Oracle Fusion General Ledger using the rapid implementation methodology to create your
enterprise structures.
Use the Microsoft Excel template to rapidly implement the following enterprise structures: chart of accounts, hierarchies, legal
entities, accounting calendar, primary ledgers, business units, and journal and document sequences.
Gathering the Data

Start your implementation carefully, by first gathering the necessary data:
1. Determine your chart of accounts segments.

2. Compile your segment values and hierarchies data.
3. Identify your legal entities and business units.
4. Determine your retained earnings account.
Preparing the Template Data Sheets

Complete the data sheets for each enterprise structure. Character and word limitations exist and apply to Essbase and all
Oracle Fusion General Ledger configurations. See topic: Essbase Character and Word Limitations.
1. Complete the COA, Calendar, and Ledger data sheet with the setup data for your chart of accounts, calendar, and
ledger, as shown in this table.
Field Values
Name
Enter the name of the primary ledger. A primary ledger is created for each unique country entered
on the Companies and Legal Entities sheet. For example:
One of the legal entities is based in United States and another in Canada.
The name provided is Vision Ledger.
Two primary ledgers, Vision Ledger US and Vision Ledger CA, are created.
Currency Select the primary ledger currency from the list of values.

Period Frequency
Select from the following values:
Monthly
4/4/5
4/5/4
4 week
Adjusting Periods
Select from the following values.
None
Once at year end
92
Field Values
Once at beginning of year and once at end of the year
Once at mid of year and once at year end
Quarterly
Fiscal Year Start Date Enter the start date of the accounting calendar using the format mm/dd/yyyy.

Segment Enter the segment name for each segment.

Segment Label
Assign one of the following segment labels from the list of values to your segments.
Primary, Second, and Third Balancing
Second Balancing and Cost Center
Cost Center
Natural Account
Intercompany
Local Use
Other considerations:
Primary Balancing and Natural Account are required.
Assign segment labels once.
The Intercompany segment is optional. If specified, the segment reuses the value set
created for the Primary Balancing segment.
The Second and Third Balancing are optional. Second balancing segment may be
assigned with the cost center segment.
Short Prompt Enter a short prompt for each segment.

Display Width Enter a display width for each segment.

Add Segment Sheets button After entering all your segments, click this button. A data sheet is created for each additional
segment where you can enter the segment values and hierarchies. The segment value and
hierarchies data entry sheets for your primary balancing segment and natural account segment
are provided.

2. Complete the Business Units data entry sheet if needed, as shown in this table.
Field Values
Name
Enter the name of your business units (BUs).The process enables all the functions and sets the
following:
Reference Data Set is Common.
The primary ledger created in this process is the default ledger for all BUs.
First entered legal entity on the Companies and Legal Entities data sheet is the default legal
entity for all BUs.
93
Field Values
Default Legal Entry Name Determines the primary ledger assigned to the business unit.

3. Complete the Companies and Legal Entities data entry sheet for your companies, hierarchies, and legal entity data,
as shown in this table.
Field Values
Parent9 to Parent1 To define hierarchies, enter the parent values in Parent9 to Parent1 column. The first-level parent
is entered in the Parent1 column. The parent of Parent1 is entered in the column Parent2 and so
on.

Child
Enter all the child values or level0 values which are your postable account values in this column.
No parent values are entered in this column.
Duplicate values are not allowed.
Enter a required value and description on each row until the last row.
Plan the hierarchies before you start entering them in this template.
Company Description Name of the company. For example, Vision Corporation, Vision US, and Vision UK.

Legal Entity: Name Optionally enter a legal entity name.

Legal Entity: Identifier Legal identifier such as a tax ID or government registration number.

Legal Entity: Country Select from the list of values provided. The identifying jurisdiction is derived from the country you
select.

Legal Entity: Address Line Enter the address in comma-separated format.

Legal Entity: City, State, County, Address for the legal entity.
Province, and Postal Code

Legal Entity: Registration Number Identifies legal entities registered for your company and recognized in law for which you want to
record and perform transactions.

Legal Entity: Reporting Unit Identifier for the lowest level component of a legal structure that requires registrations. Map the
Registration Number legal entity details to the primary balancing segment value. If the legal entity maps to multiple
primary balancing segment values consecutively, only specify the legal entity for the first primary
balancing segment value.

4. Complete the Natural Accounts data entry sheet, as shown in this table.
Field Values
Parent9 to Parent1 and Child Enter your parent values in these columns. First-level parents are entered in the column Parent1
and so on. Duplicate values are not allowed.

Description Provide descriptions for each of the parent values as well as the child values.
94
Field Values

Account Type Categorizes the accounts. Account type is used to determine which account to use in application
processes such as retained earnings calculation at the end of the year. The account type is also
used in the upload processes to create general ledger and subledger (Payables and Receivables)
accounts in some setup pages. Select the appropriate values from the list for each account.

Financial Category An optional field that is used with Oracle Business Intelligence applications. The predefined values
consist of the standard financial categories. For example: Accounts payable, Accounts receivable,
Accrued liabilities, Accumulated depreciation, Cash, and Common stock.

5. To create more than one hierarchy for any of your chart of accounts segments during the initial setup.
a. Click the Generate Additional Hierarchy button on the segment's worksheet. This creates a new worksheet
and populates it with the data already entered for that segment.
b. Change this data as required for the new hierarchy.
Note: For the company segment, adding legal entity information is not supported on this sheet.
Note: With this button you can create hierarchies, but not new versions of existing hierarchies.
6. Complete the Financial Sequences data entry sheet, as shown in this table.
Field Values
Enabled Enter Yes to enable the sequence.

Restart
Enter the period of time used to restart the sequence. Select:
Annually
Monthly
Never
Initial Value Enter a whole number greater than 1. All versions of the sequence start with the same number.

7. Click the Step 1: Validate button to validate the workbook data.
Loading the Templates

1. After you finish preparing the data in the sheets, click the Step 2: Generate Chart of Accounts File button on the
COA, Calendar, and Ledger sheet. The process generates an XML data file called ChartOfAccounts.xml.
2. Save the file in a local directory.
3. Click the Step 3: Generate Ledger, LE, and BU File button on the COA, Calendar, and Ledger sheet. The
process generates an XML data file called FinancialsCommonEntities.xml.
4. Save the file in a local directory.
5. On the Setup and Maintenance page in the Functional Setup Manager, search for and select the Upload Chart of
Accounts task. This task runs the Upload Enterprise Structures process.
6. Click the Upload File button and select the first file you saved, which is ChartOfAccounts.xml.
7. Click Submit. The Scheduled Processes page opens.
95
8. Verify that the process completes without errors or warnings.

9. Click Done.
10. Select the Deploy Chart of Accounts task on the Setup and Maintenance page. Select the Deploy button for the
accounting flexfield.
11. Refresh the page until the green check mark appears and verifies that the deployment was successful.
12. On the Setup and Maintenance page, select the Upload Ledger, Legal Entities, and Business Units task. This
runs the Upload Enterprise Structures process.
13. Click the Upload File button and select the second XML file you saved, which is FinancialsCommonEntities.xml.
14. Click Submit. The Scheduled Processes page opens.
15. Verify that the process completed without errors or warnings.
16. Click Done.
Running Automatic Processes

1. The following processes are run automatically during the rapid implementation flow to configure the ledger and
associated setup and create the balances cubes:
Submit Account Configuration, which includes general ledger balances cube creation
Online Audit of Hierarchy Data of tree and tree versions
Row and Column Flattening of hierarchy data
Publish Hierarchies
Create Chart of Accounts, Ledger, Legal Entities, and Business Units

in Spreadsheets: Explained
Represent enterprise structures of your chart of accounts, ledger, legal entities, and business unit configuration to track and
report on your financial objectives and meet your reporting requirements. These components are the underlying structure for
organizing financial information and reporting.
The chart of accounts within the ledger facilitates:
Aggregating data from different operations, from within an operation, and from different business flows
Consistent definitions to your stakeholders in compliance with legislative and corporate reporting standards and aids
in management decisions
Rapid implementation is a way to configure a financial enterprise and financial reporting structures quickly using sheets in a
workbook that upload lists of:
Companies (legal entities)
Ledgers by country
Business units
Chart of accounts and segment values
Segment value hierarchies
Financial sequences
Required subledger accounts
Once the sheets have been uploaded, the application creates your:
Chart of accounts structure and instance
96
Segment value hierarchies

Key accounts such as retained earnings
Required subledger accounts
Calendar
Primary ledgers by country
Legal entities and their locations
Business units
Document and journal sequences
The following figure shows the relationship of these components.
Legal Entities
Incurred
(Companies)
Transactions
Calendar
Balancing
Segments Identified by
Currency
Business Units
Ledger
with Business
Chart of Functions
Accounts
Recorded in
Cost Natural
Centers Accounts
Subledgers
Other
Segments
Subledger
Transferred to
Accounting
Method
Legal Entity: Identifies a recognized party with rights and responsibilities given by legislation, which has the right to
own property and the responsibility to account for themselves.
Chart of Accounts: Configures accounts consisting of components called segments that are used to record
balances and organize your financial information and reporting.
97
Segment: Contains a value set that provides formatting and validation of the set of values used with that segment.
When combined, several segments create an account combination for recording your transactions and journal
entries.
Segment Label: Identifies certain segments in your chart of accounts and assigns special functionality to those
segments. The required segment labels are:
Balancing Segment: Ensures that all journals balance for each balancing segment value or combination of
multiple balancing segment values to use in financial processes and reporting. The three balancing segment
labels are: Primary balancing segment, Second balancing segment, and Third balancing segment. The
Primary balancing segment label is required and must be the first segment in the Rapid Implementation
spreadsheet.
Natural Account: Facilitates processes in the General Ledger application, such as retained earnings posting.
For each child value, you must assign an Account Type. You can select from one of the general choices to
mark the account value as an Asset, Liability, Owner's Equity, Revenue, or Expense account.
If the account is used by the rapid implementation solution to provide accounts for setup objects, select
the appropriate Expanded Account Type value for the child account. Examples of expanded account types
required for setup objects are:
Owner's Equity - Retained Earnings: To set up General Ledger ledgers.

Liability - Accounts Payable: To set up Payables common options.
Asset - Accounts Receivable: To set up Receivables receipt methods.
Accounts tagged with expanded account types are automatically assigned a financial category. You can
override the default category in the Financial Category field, or leave it out.
Cost Center: Facilitates grouping of natural accounts by functional cost types, accommodating tracking of
specific business expenses across natural accounts.
Ledger: Maintains the records and is a required component in your configuration. The rapid implementation
process:
Creates your primary ledgers by combining your chart of accounts, calendar, and currency as well as other
required options defined in the sheets.
Assigns a default value for the fourth component, which is the subledger accounting method. The subledger
accounting method is used to group subledger journal entry rule sets together to define a consistent
accounting treatment.
Note: The standard accrual method is the default subledger accounting method assigned to the
primary ledger.
Creates a General Ledger balances cube for each ledger with a unique chart of accounts and calendar
combination. Each segment is created as a dimension in the balances cube along with the standard cube
dimensions.
Business Units with Business Functions: Identifies where subledger transactions are posted and provides
access to perform subledger business processes. When configured, business units are assigned to a primary ledger
and a default legal entity.
Subledger: Captures detailed transactional information, such as supplier invoices, customer payments, and asset
acquisitions. Uses subledger accounting to transfer transactional balances to the ledger where they are posted.
98
Note: Segment Value Hierarchies: You can create more than one hierarchy for any of your chart of accounts
segments during initial setup. You can also create additional hierarchies after the initial setup is done by
uploading the rapid implementation spreadsheet data. Document and Journal Sequences: You can create
sequences for each legal entity or ledger based on the predefined country defaults. Document sequences are
created for:
Payables invoices
Payments
Receivables invoices
Receivables credit memos
Receivables adjustment activities
Reporting and accounting journal sequences are created for subledger journals and General Ledger journals.
Create Chart of Accounts, Ledger, Legal Entities, and Business Units

in Spreadsheets: How They're Processed
The Create Chart of Accounts, Ledger, Legal Entities, and Business Units rapid implementation process consists of four
steps.
1. Entering data into the sheets.
2. Verifying the entered data and resolving the errors, if any.
3. Uploading the first file generated.
4. After successful upload of the first file, uploading the second file generated for the rest of the configuration.
Process Overview
Begin by downloading the Rapid Implementation for General Ledger workbook using the Create Chart of Accounts, Ledger,
Legal Entities, and Business Units in Spreadsheet task on the Setup and Maintenance work area.
99
The following figure illustrates the Create Chart of Accounts, Ledger, Legal Entities, and Business Units process, what data is
entered into each sheet of the workbook, and the components that the process creates.
Enter Upload Creates
Chart of Accounts Ledgers including

Segments, Calendar, Associated Balance
and Ledgers Options Cubes
Business Units
Business Units Names with All Business
Functions Assigned
Primary Balancing
Company Values, Legal
Segments, Dimensions,
Entity Values, and
Hierarchies, and Legal
Hierarchies
Entity Registrations
Natural Account Segments,

Natural Account Values
Dimensions, Key Accounts,
and Hierarchies
and Hierarchies
Other Segments,
Other Segment Values
Dimensions, and
and Hierarchies
Hierarchies
Document and Journal

Financial Sequences Sequences by Ledger or
Legal Entities
The Rapid Implementation for General Ledger workbook includes the following sheets:
Instructions
Chart of Accounts, Calendar, and Ledger
Business Units
Companies and Legal Entities
Natural Accounts
Financial Sequences
100
Sheets for entering other segment values and hierarchies for additional segments of your chart of accounts are created
automatically by entering the segments on the Chart of Accounts, Calendar, and Ledger sheet and then clicking Add
Segment Sheets or Generate Additional Hierarchy on that same sheet.
Instructions Sheet
Read the planning tips, loading process, best practices, and recommendations. Refer to the sample data worksheet to get an
idea of how to enter the data and generate the required upload files.
The following figure shows the link to the sample data template on the Instructions sheet.
Chart of Accounts, Calendar, and Ledger Sheet

Enter the data to create your ledger, chart of accounts, currency, and calendar, and to set the required ledger options.
Name: Enter the name of your primary ledgers.
Note: A primary ledger is created for each unique country entered in the Companies and Legal Entities
sheet. The country code is appended to the name you have specified to create the primary ledger. For
example, if one of the legal entities is based in the United States and another in Canada, and the ledger
name is InFusion Ledger, then two primary ledgers, InFusion Ledger US and InFusion Ledger CA, are
created. All the primary ledgers that are created use the same chart of accounts, account hierarchies, and
accounting calendar. Legal entities and their primary balancing segment values are assigned to the primary
ledger of their respective countries.
101
Currency: Enter the ledger currency in which most of your transactions are entered if you're not entering legal entity
data. If you're entering legal entities, leave the field blank. The currency is supplied by default based on the country.
Period Frequency: Select one of the available frequencies.
Adjusting Periods: Select the number of periods that are used to enter closing, auditing, or other adjustments in
the General Ledger at quarter or year end. The entries are tracked in the adjusting period and not in your monthly
activity.
Fiscal Year Start Date: Enter the start date of your calendar for the ledgers. The date can't be changed after the
ledgers are created.
Caution: Select a period before the first period in which you plan to load history or perform translations to
enable running translation. You can't run translation in the first defined period of a ledger calendar.
Chart of Accounts section: Enter your segments, segment labels, short prompts, and display width data that's
used to create your chart of accounts. Plan this data carefully because you're defining the basic structure for your
accounting and reporting.
Segment: Enter the names of your segments.
Segment Label: Select which segment the application uses for certain processing, such as the Primary
Balancing Segment, which is used to balance journal entries.
Note: If you select an Intercompany Segment label, you must complete at least one intercompany
rule. You must also select the Enable Intercompany Balancing option using the Specify Ledger
Options task for the Balancing API to perform intercompany balancing. Also note that the same
hierarchy specified for the primary balancing segment is also used for the intercompany balancing
segment automatically.
Note: If you plan to enable segment value security rules for the primary balancing segment,
then you should not assign the Intercompany Segment label to the Intercompany segment. By
default, the Rapid Implementation spreadsheet assigns the same value set to the Company and
Intercompany segments if the Intercompany Segment label is assigned. If you want to use segment
value security rules for the Company segment where a user can only access Company 01, that user
can't transact with other companies in an intercompany transaction because segment value security
rules are assigned at the value set level. What you should do instead is not assign the Intercompany
Segment label to the Intercompany segment. Use the Add Segment Sheets button to add sheets
for any unqualified segments, and assign the values directly. Obviously, you will want to assign the
same values to the Company and Intercompany segments. You must then assign the Intercompany
segment label to this segment by navigating to Edit Key Flexfield Segment Intercompany using the
application pages to use the intercompany segment in intercompany balancing.
Short Prompt: Enter a short name for the segment for the application to use.
Display Width: Enter the segment size. Select carefully and leave room for growth. For example, if you have
89 cost centers, enter 3 for the display length to allow for more than 100 cost centers in the future.
Add Segment Sheets button: Select to create sheets for additional segments. Only the Company and Natural
Accounts sheets are provided.
From the new segment sheet, you can click Generate Additional Hierarchy to create more than one hierarchy for
any of your chart of account segments. This creates a worksheet and populates it with the data already entered for
102
that segment. Change this data as required for the new hierarchy. You can create additional hierarchies during initial
setup or after the initial setup is done.
Step 1: Validate button: Click to validate your entered data. An actionable validation report is generated if any errors
occur in data entry. Correct these errors before proceeding by clicking each error on the report. Clicking the error
navigates you to the exact sheet and cell on that sheet where the error can be found.
Step 2: Generate Chart of Accounts File button: Click to create a file that is then uploaded to create the chart of
accounts structures, values, and hierarchies.
Step 3: Generate Ledger, LE, and BU File button: Click to create a file that is then uploaded to create ledgers,
legal entities and their locations, business units (BU), and document and journal sequences.
Business Units Sheet

Enter the name of your business units and related default legal entities.
You can enter more than one business unit per ledger. Business units are created with entered names. Based on the default
legal entity entered in the Business Units sheet, the respective country's primary ledger is supplied by default for the business
unit. The first legal entity that is associated with the ledger is supplied by default for all the business units of that country.
Companies and Legal Entities Sheet

Enter a list of your legal entities with their addresses, registration number, reporting unit registration number, and assigned
parent or child value. You can create up to nine levels of parent values to use to roll up your legal entities to meet corporate
and local reporting requirements.
103
The registration number identifies legal entities registered for your company and recognized in law for which you want to
record and perform transactions. The reporting unit registration number identifies the lowest level component of a legal
structure that requires registrations.
To create additional hierarchies for the company segment for reporting or other purposes, click the Generate Additional
Hierarchy button on this sheet. This creates a worksheet and populates it with the data already entered for that segment.
Change this data as required for the new hierarchy. You can create additional hierarchies during initial setup or after the initial
setup is done.
Note: For the Company segment, adding legal entity information isn't supported on the new hierarchy's sheet.
Note: When a new hierarchy sheet is created, the name for that sheet is derived by adding a counter to the
sheet name. For example, when you click Generate Additional Hierarchy on the Companies and Legal
Entities sheet, the new sheet is named Companies and Legal Entities 1. When you click Generate Additional
Hierarchy again, another sheet is generated with the name Companies and Legal Entities2.
104
Natural Accounts Sheet

Enter your account values that are used to record the type of balance.
Parent Values, Child Values and Descriptions: Enter to create segment values and build hierarchies. Child
values are the postable account values. To define hierarchies, enter parent values. Hierarchies are used for chart of
accounts mappings, revaluations, data access sets, cross-validation rules, and segment value security rules. The
balances cube and account hierarchies are also used for financial reporting, Smart View queries, and allocations.
Account Type: Enter to identify the type of account: Asset, Liability, Revenue, Expense, or Owner's Equity. Account
types are used in year-end close processes and to correctly categorize your account balances for reporting.
If the account is used by the rapid implementation solution to provide accounts for setup objects, select the
appropriate Expanded Account Type value for the child account. Examples of expanded account types required for
setup objects are:
Owner's Equity - Retained Earnings: To set up General Ledger ledgers.
Liability - Accounts Payable: To set up Payables common options.
Asset - Account Receivable: To set up Receivables receipt methods.
Accounts tagged with expanded account types are automatically assigned a financial category. You can override the
default category in the Financial Category field, or leave it out.
Financial Category: Enter to identify groups of accounts for reporting with Oracle Transactional Business
Intelligence.
Generate Additional Hierarchy: To create additional hierarchies for the company segment for reporting or other
purposes, click the Generate Additional Hierarchy button on this sheet. This creates a worksheet and populates
it with the data already entered for that segment. Change this data as required for the new hierarchy. You can create
additional hierarchies during initial setup or after the initial setup is done.
105
Financial Sequences Sheet

Enable document or journal sequences to assign unique numbers to your transactions to meet legal requirements.
The transactions the document sequences are created for include:

Payables invoices
Payments
Receivables invoices
Receivables credit memos
Receivables adjustment activities
Reporting and accounting journal sequences are created for:

Subledger journals
General Ledger journals
Complete the following steps on the Sequences sheet:

1. Restart: Set to restart the numbering based on one of the following criteria:
Annually: Restart sequence numbers once a year.

Monthly: Restart sequence numbers each month.
Never: Never restart sequences numbers. Continue with the same sequence.
2. Initial Value: The beginning number in the sequence.
Upload the Sheets

After you complete the other sheets, return to the Chart of Accounts, Calendar, and Ledger sheet and perform the following
steps:
1. Click Step 1: Validate. The process validates your data entry. Ensure the validation report has no errors.
2. Click Step 2: Generate Chart of Accounts File. The process generates a data file called ChartOfAccounts.xml
with the entered chart of accounts and hierarchies setup data. Save the file to a network or local drive.
3. Click Step 3: Generate Ledger, LE, and BU File. The process generates a data file called
FinancialsCommonEntities.xml with the entered ledger, legal entities, and business unit setup data. Save the file to a
network or local drive.
106
4. Navigate to the Setup and Maintenance work area. Search for and select the Upload Chart of Accounts task. The
Upload Enterprise Structures and Hierarchies process is launched.
5. Accept the default selection of the Upload Enterprise Structure option.
6. Click Browse and select the first file that you saved called ChartOfAccounts.xml.
7. Click Submit.
9. Navigate to the Setup and Maintenance work area. Search for and select the Upload Ledger, Legal Entities, and
Business Units task. The Upload Enterprise Structures and Hierarchies process is launched.
10. Accept the default selection of the Upload Enterprise Structure option.
11. Click Browse and select the second file that you saved called FinancialsCommonEntities.xml.
12. Click Submit.
Tip: You can't change the chart of accounts, accounting calendar, or currency for your ledgers after the setup is
created. Open the first accounting period to begin entering data with a user that has proper access to the newly-
created primary ledger.
Create Additional Hierarchies After Initial Setup

To create more than one hierarchy for any of your chart of account segments after the initial enterprise structure setup:
1. Click the Generate Additional Hierarchy button on the segment's sheet for which you want to create the
additional tree or tree version. This creates a new worksheet and populates the sheet with the data already entered
for that segment. Change the data as required for the new hierarchy.
2. To create the hierarchy based on the data in the particular sheet in context only, click the Generate File for This
Hierarchy Only button. This generates a .zip file for the particular hierarchy. Perform the following steps to either
create a new tree or a new version for an existing tree for the particular segment.
3. Navigate to the Setup and Maintenance work area. Search for and select the Upload Chart of Accounts task. The
Upload Enterprise Structures and Hierarchies process is launched.
107
4. Select the Upload Hierarchy option.
5. Select to either create a hierarchy or tree version as per your requirement.

6. Specify the required parameters.
7. Click Choose File and select the .zip file that you saved earlier.
8. Click Submit.
Related Topics
Create Hierarchies in a Spreadsheet: Example
Chart of Accounts
Key Flexfields: Explained

Key flexfields provide a means to capture a key such as a part number, a job code, or an account code. A key flexfield
consists of one or more segments, where each segment can have a meaning.
For example, a part number 10-PEN-BLA-450 might correspond to a black pen from supplier #450 sold by division #10
(office supplies). Behind the scenes, the application uses a unique number, 13452, for this part, but the user always sees the
10-PEN-BLA-450 part number.
The following aspects are important to understanding key flexfields:

Architecture
Segments and segment labels
108
Structures
Segment and structure instances
Combinations
Dynamic combination creation
Security
Key flexfields aren't optional. You must configure key flexfields to ensure that your applications operate correctly. You
configure and maintain key flexfield definitions with the Manage Key Flexfields task. To get a list of predefined key flexfields,
open the Setup and Maintenance work area, and use the Manage Key Flexfields task. For information about specific key
flexfields, see the help for the product where the associated business component is implemented.
Architecture
Flexfield metadata is stored in the flexfield metadata tables. When you configure a key flexfield, you define metadata about the
key flexfield covering aspects such as:
Segments are in a structure
Structures in the flexfield
Value sets in each segment
Based on the flexfield metadata, actual part numbers are captured at run time as a combination of segment values and
stored in a combinations table. A combinations table contains all the segment columns for a flexfield, a unique ID column,
and a structure instance number column. The structure instance number column differentiates multiple arrangements of the
segment columns. For example, a part number containing multiple segments can be represented by a key flexfield. A part
number key flexfield has a corresponding combinations table. In that table, the flexfield stores a list of the complete codes,
with each segment of the code in a column, with the corresponding unique ID and structure instance number for the code.
When users define a new part number or maintain existing part numbers in the parts catalog, they directly maintain rows in
the combinations table.
The foreign key table contains a different business entity than the combinations table. For example, the business entity in the
foreign key table is order lines or invoice lines that contain foreign key references to parts for ordering. Any number of foreign
key tables can reference a particular entity represented by a key flexfield.
Segments and Segment Labels

A key flexfield contains segments and a segment label identifies a particular segment within a key flexfield. Segment labels are
defined and made available by the product development. A segment contains the following details:
A prompt
A short prompt
Display width
The sequential position of the segment within the key flexfield structure
The range type
Column name of the attribute being stored by the segment
A default value set
A label for the segment
Applications identify a particular segment for some purpose such as security or computations. Segment name or segment
order cannot reliably identify a segment because key flexfield segments can be configured to appear in any order with any
prompts. A segment label functions as a tag for a segment.
109
For example, the requirement is to identify which segment in the accounting flexfield contains balancing information and
which segment contains natural account information. A segment label determines which segment you are using for natural
account information. When you define your accounting flexfield, you must specify which segment label apply to which
segments. Some labels must be unique, and cannot be applied to more than one segment in each structure. Other labels are
required, and must be applied to at least one segment in each structure.
A segment label helps a user searching for segments, such as the Cost Center label for all segments across key flexfields that
store a value for the cost center.
Structures
A key flexfield structure definition includes the number of segments and their order.
In some applications, different users like to see different segment structures for the same flexfield. A key flexfield can have
multiple structures if registered to support more than one structure.
The flexfield can display different fields for different users based on a data condition in your application data, such as the value
of another field entered by the user or the user's role. For example, the correctly formatted local postal address for customer
service inquiries differs based on locale. A postal address key flexfield could display different segments and prompts for
different users based on a location condition in your application data, such as the user's role or a value entered by the user.
Each structure can have one or more segments. Thus a segment is a child of a structure. To store a particular segment, such
as Cost Center, in two different structures, you must define the segment separately in each structure. Each structure may
have one or more structure instances. Each instance of a structure shares the same number and order of segments, but
differs in the values or value sets used in validating the segments.
Structure and Segment Instances

You can define multiple configurations of a key flexfield structure. These structure instances have the same segment
structure, in the same sequence order. They differ primarily in how each segment is validated. You define a structure instance
for each key flexfield and each key flexfield structure instance.
The segments in a key flexfield structure instance are segment instances. A segment instance is a segment with a specific
value set assigned to it. If a key flexfield is registered with a tree structure, you can specify a tree code for a segment instance.
Combinations
A combination is a complete code, or combination of segment values that makes up the code, that uniquely identifies an
object.
For example, each part number is a single combination, such as PAD-YEL-11x14 or 01-COM-876-7BG-LTN. In these
combinations, the hyphen is the segment separator. If you have ten parts, define ten combinations. A valid combination
is an existing or new combination that can be used because it's currently active and doesn't violate cross-validation or
security rules. A combination has different segments depending on the flexfield structure being used for that combination. Any
combination is associated with only one particular flexfield structure.
Many applications refer to a key flexfield combination by using the name of the entity or the key flexfield itself. For example,
Assets uses the asset key flexfield and refers to one of its combinations as an asset key or asset key flexfield. In another
example, Oracle Fusion General Ledger refers to combinations of the accounting flexfield as account or GL account.
Each key flexfield has one corresponding table, known as the combinations table, where the flexfield stores a list of the
complete codes, with one column for each segment of the code, together with the corresponding unique ID number (an
account combination ID) for that code. Then, other tables in the application have a column that stores just the unique ID for
the code. For example, you may have a part number code, such as PAD-YEL-11x14. The Parts combinations table stores
that code along with its ID, 57494. If your application lets you take orders for parts, you might then have an Orders table that
stores orders for parts. That Orders table would contain a single column that contains the part ID, 57494, instead of several
columns for the complete code PAD-YEL-11x14. Typically, one combinations page maintains the key flexfield, where the key
110
flexfield is the representation of an entity in your application. Maintain individual combinations, such as part numbers in the
combinations page.
Dynamic Combination Creation

Dynamic combination creation is the insertion of a new valid combination into a combinations table from a page other than
the combinations page. The following table lists the levels at which dynamic combination creation may be enabled.
Level Of Dynamic Combination Creation Controlled By:
Flexfield Application development

Each usage or reference to the key Application development

flexfield

Structure instance Administrators and implementation consultants

Other Administrators and implementation consultants

If your key flexfield or certain usages or references of the key flexfield don't permit dynamic combination creation, you may
control whether dynamic combination creation is enabled for each structure instance. If enabled, a user can enter a new
combination of segment values using the flexfield window from a foreign key page. For example, when entering a transaction,
a GL user can enter a new expense account combination for an account that doesn't yet exist. Your application creates
the new account by inserting the new combination into the combinations table behind the scenes. Assuming that the new
combination satisfies any existing cross-validation rules, the flexfield inserts the new combination into the combinations table,
even though the combinations table isn't the underlying table for the foreign key page.
Related Topics
Managing Key Flexfields: Points to Consider
Key Flexfield Structures: Explained
Planning Key Flexfields: Points to Consider

Your first step in planning your key flexfields is to determine which key flexfields your application requires. Your plan should
include:
The purpose of the key flexfield

The number and length of its available segment columns
Whether your key flexfield permits more than one structure
Whether more than one structure must be defined
The number, order and length of your segments for each structure
111
Before You Begin

Once you have identified a flexfield, plan its configuration in advance. Compile a list of the UI pages and other artifacts in your
deployment that are affected by the configuration. Verify that you are provisioned with the roles required to view and configure
the flexfield. Use the Highlight Flexfields command in the Administration menu to view the run time page where the flexfield
appears. Plan how you deploy the flexfield for test and production users. Review the tools and tasks available for managing
flexfields, such as the Define Flexfields task list and Manage Sandboxes.
If you plan to use value sets, create them before configuring the key flexfield. You cannot create value sets for key flexfields at
the time that you add and configure key flexfield segments.
Access to Flexfield-Related Tasks

To configure flexfields and value sets, you must have access to the Define Flexfields task list or tasks for managing product-
specific flexfields. Contact your security administrator for details. For information about product-specific flexfield tasks, such
as Manage Fixed Assets Key Flexfields, consult the product-specific documentation.
Restrictions
If you plan to use value sets, create them before configuring the flexfield. Plan your key flexfield configuration to scale to
your enterprise needs. For example, if you expect to disable old cost centers and enable new ones frequently, plan a larger
maximum size for your cost center value set so that you can have more available values. A 3-character value set with one
thousand available values provides more room for changes than a 2-character value set with 100 available values.
Note the code name of the flexfield you intend to configure so that you find it easily in the Define Flexfield task list or tasks
for managing product-specific key flexfields. In some cases you can customize how the flexfield appears on the page. See
product-specific documentation to determine any restrictions on using product-specific key flexfields.
Reporting
To report on your data by certain criteria or sub-entities, such as account number or project or region, consider making that
sub-entity a distinct segment, rather than combining it with another sub-entity. You can categorize and report on smaller
discrete units of information.
Related Topics
Flexfields and Value Sets: Highlights
Planning Value Sets: Points to Consider
Essbase Character and Word Limitations

The following is a comprehensive list of character and word limitations that apply to Essbase. All of the limitations apply to all
of the Oracle General Ledger configurations summarized in the table.
The following table shows how the General Ledger configuration maps to Essbase.
General Ledger Configuration Maps to Essbase
Chart of Account Name Cube Name

Chart of Account Segment Name Dimension Name

Chart of Accounts Segment Value Dimension Member Name
112
General Ledger Configuration Maps to Essbase

Chart of Accounts Segment Value Alias for Member

Description

Tree and Tree Version Name Dimension Member Name

Primary Ledger Name Dimension Member Name in Ledger Dimension

Secondary Ledger Name Dimension Member Name in Ledger Dimension

Reporting Currency Name Dimension Member Name in Ledger Dimension

Ledger Set Name Dimension Member Name in Ledger Dimension

Accounting Calendar Period Names Dimension Member Name in Accounting Period Name

Scenario Name Defined in Predefined Dimension Member Name in Scenario Dimension

Value Set Called Accounting Scenario

Even if case sensitivity is enabled in an aggregate storage outline for which duplicate member names is enabled, do not use
matching dimension names with only case differences. For example, do not:
Name two dimensions Product and product.
Use quotation marks or brackets.
Use tabs in dimension, member, or alias names.
Use accent characters.
Use the characters for dimension or member names.
Restricted Characters
The following table lists the characters that are restricted and cannot be used at the beginning of dimension, member, or alias
names.
Character Meaning
@ at sign

\ backslash

, comma

- dash, hyphen, or minus sign

For the accounting calendar period names, you can use a hyphen or an underscore in the middle of
an accounting calendar period name. For example: Jan-15 or Adj_Dec-15 can be used successfully.

= equal sign
113
Character Meaning

< less than sign

() parentheses

. period

+ plus sign

' single quotation mark

_ underscore

For the accounting calendar period names, you can use a hyphen or an underscore in the middle of
an accounting calendar period name. For example: Jan-15 or Adj_Dec-15 can be used successfully.

| vertical bar

Other Restrictions
Don't place spaces at the beginning or end of names. Essbase ignores such spaces.
Don't use the following types of words as dimension or member names:
Calculation script commands, operators, and keywords.
Report writer commands.
Function names and function arguments.
Names of other dimensions and members (unless the member is shared).
Generation names, level names, and aliases in the database.
The following table lists additional words that should not be used.
List 1 List 2 List 3
ALL AND ASSIGN

AVERAGE CALC CALCMBR

COPYFORWARD CROSSDIM CURMBRNAME

DIM DIMNAME DIV

DYNAMIC EMPTYPARM EQ

EQOP EXCEPT EXP

114
List 1 List 2 List 3
EXPERROR FLOAT FUNCTION

GE GEN GENRANGE

GROUP GT ID

IDERROR INTEGER LE

LEVELRANGE LOOPBLOCK LOOPPARMS

LT MBR MBRNAME

MBRONLY MINUS MISSING, #MISSING

MUL MULOP NE

NON NONINPUT NOT

OR PAREN PARENPARM

PERCENT PLUS RELOP

SET SKIPBOTH SKIPMISSING

SKIPNONE SKIPZERO TO

TOLOCALRATE TRAILMISSING TRAILSUM

UMINUS UPPER VARORXMBR

XMRONLY $$$UNIVERSE$$$ #MI

Chart of Accounts: Explained

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.
A well-designed chart of accounts provides the following benefits:
Effectively manages an organization's financial business.

Supports the audit and control of financial transactions.
Provides flexibility for management reporting and analysis.
115
Anticipates growth and maintenance needs as organizational changes occur.

Facilitates an efficient data processing flow.
Enables delegation of responsibility for cost control, profit attainment, and asset utilization.
Measures performance against corporate objectives by your managers.
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.
Best practices include starting the design from external and management reporting requirements and making decisions about
data storage in the general ledger, including thick versus thin general ledger concepts.
Thick Versus Thin General Ledger: Critical Choices

Thick versus thin general ledger is standard terminology used to describe the amount of data populated and analysis
performed in your general ledger. Thick and thin are the poles; most implementations are somewhere in between. Here are
some variations to consider:
A general ledger used in conjunction with an enterprise profitability management (EPM) product, which has data
standardized from each operation, is a thin general ledger. Use this variation if your solution is project-based, and
Oracle Fusion Project Portfolio Management is implemented. More detailed reporting can be obtained from the
Projects system. In the thin general ledger, business units, divisions, and individual departments are not represented
in the chart of accounts.
A thick general ledger:
Has segments representing all aspects.

Captures every detail of your business.
Runs frequent posting.
Defines many values in each segment.
A thick general ledger is designed to serve as a repository of management data for a certain level of management.
For example, a general ledger designed to provide management data to supervise operations, such as daily sales,
without invoice details.
A primary and secondary ledger, with one thick general ledger and the other a thin general ledger, provides dual
representation to meet reporting requirements.
Thin General Ledger

With a thin general ledger, you use the general ledger for internal control, statutory reporting, and tracking of asset ownership.
You minimize the data stored in your general ledger. A thin general ledger has many of the following characteristics:
Minimal chart of accounts
Short list of cost centers

Short list of natural accounts
Short list of cost accounts
Summary level asset and liability accounts
Low number of optional segments
116
Infrequent posting schedule
A thin general ledger:

Has natural accounts at a statutory reporting level, for example, payroll expense, rent, property taxes, and utilities.
Has cost centers at the functional expense level, such as Research and Development or Selling, General, and
Administrative, rather than at department or analytic levels.
Omits business unit, division, and product detail.
One example of an industry that frequently uses a thin general ledger is retail. In a retail organization, the general ledger tracks
overall sales numbers by region. A retail point of sales product tracks sales and inventory by store, product, supplier, markup,
and other retail sales measures.
Thick General Ledger

With a thick general ledger, you use the general ledger as a detailed, analytic tool, performing analytic functions directly in the
general ledger. Data is broken down by many reporting labels, and populated frequently from the subledgers.
You maximize the data stored in the general ledger. A thick general ledger has many of the following characteristics:
Maximum use of the chart of accounts
Long list of natural accounts

Long list of cost centers
Long list of costing accounts
Detailed asset and liability accounts
Frequent posting schedule
A thick general ledger had details for cost of goods sold and inventory balances and track property plant and equipment
at a granular level. Cost centers represent functional expenses, but also roll up to departmental or other expense analysis
levels. Using product and location codes in optional segments can provide reporting by line of business. Posting daily, at the
individual transaction level, can maximize the data stored in the general ledger.
One example of an industry that frequently uses a thick general ledger is electronic manufacturers. Detail on the revenue line
is tagged by sales channel. Product is structured differently to provide detail on the cost of goods sold line, including your
bill of materials costs. The general ledger is used to compare and contrast both revenue and cost of goods sold for margin
analysis.
Other Considerations
Consider implementing a thick ledger if there are business requirements to do any of the following:
Track entered currency balances at the level of an operational dimension or segment of your chart of accounts, such
as by department or cost center
Generate financial allocations at the level of an operational dimension or segment
Report using multiple layered and versions of hierarchies of the operational dimension or segment from your general
ledger
Consider implementing a thin ledger in addition to a thick ledger, if there are additional requirements for:
Minimal disclosure to the authorities in addition to the requirements listed above. For example, in some European
countries, fiscal authorities examine ledgers at the detailed account level.
Fiscal only adjustments, allocations, and revaluations, which don't impact the thick general ledger.
117
The important consideration in determining if a thick ledger is the primary or secondary ledger is your reporting needs. Other
considerations include how the values for an operational dimension or segment are derived and the amount of resources
used in reconciling your different ledgers. If values for an operational dimension or segment are entered by the user, then a
thick primary ledger is the better choice.
However, if values for the operational segment are automatically derived from attributes on transactions in your subledger
accounting rules, then use a thick secondary ledger. This decision affects the amount of:
Storage and maintenance needed for both the general ledger and subledger accounting entries
System resources required to perform additional posting
In summary, you have:
Minimum demand on storage, maintenance, and system resources with the use of a thin ledger
Greater demand on storage, maintenance, and system resources with the use of a thick ledger
Greatest demand on storage, maintenance and system resources with the use of both thick and thin ledgers
Note: Generally speaking, there is a trade-off between the volume of journals and balances created and
maintained versus system resource demands. Actual performance depends on a wide range of factors
including hardware and network considerations, transaction volume, and data retention policies.
Summary
The factors you should consider in your decision to use a thick or thin general ledger for your organization, are your:
Downstream EPM system and its capabilities

Business intelligence system and its capabilities
Subledger systems and their capabilities and characteristics, including heterogeneity
General ledger reporting systems and their capabilities
Maintenance required for the thick or thin distributions and record keeping
Maintenance required to update value sets for the chart of accounts segments
Preferences of the product that serves as a source of truth
Level at which to report profitability including gross margin analysis
Industry and business complexity
118
Chart of Accounts: How Its Components Fit Together

The important elements in a basic chart of accounts in Oracle Fusion Applications included a structure that defines the
account values, segments and their labels, and rules (security and validation). Account combinations link the values in the
segments together and provide the accounting mechanism to capture financial transactions.
Chart of
Accounts
Segment Segments Value Sets

Labels
Primary Balancing
Second Balancing
Rules Values
Third Balancing
Cost Center
Security
Natural Account
Cross Validation
Account
Intercompany
Combinations
Management
Chart of Accounts
The chart of accounts defines the number and attributes of various segments, including:
Order of segments
Width of segments
Prompts
Segment labels, such as balancing, natural account, and cost center.
The chart of accounts further defines:

Combination of value sets associated with each segment
Type of segment
119
Default values for the segments

Additional conditions designating the source of the values using database tables
Required and displayed properties for the segments
Segments
A chart of accounts segment is a component of the account combination. Each segment has a value set attached to it to
provide formatting and validation of the set of values used with that segment. The combination of segments creates the
account combination used for recording and reporting financial transactions. Examples of segments that may be found in a
chart of accounts are company, cost center, department, division, region, account, product, program, and location.
Value Sets and Values

The value sets define the attributes and values associated with a segment of the chart of accounts. You can think of a value
set as a container for your values. You can set up your flexfield so that it automatically validates the segment values that
you enter against a table of valid values. If you enter an invalid segment value, a list of valid values appears automatically so
that you can select a valid value. You can assign a single value set to more than one segment, and you can share value sets
across different flexfields.
Caution: You must use Independent validation only for the Accounting Key Flexfield value sets. Other
validations prevent you from using the full chart of accounts functionality, such as data security, reporting, and
account hierarchy integration. Dependent values sets are not supported.
Segment Labels
Segment labels identify certain segments in your chart of accounts and assign special functionality to those segments.
Segment labels were referred to as flexfield qualifiers in Oracle E-Business Suite. Here are the segment labels that are
available to use with the chart of accounts.
Balancing: Ensures that all journals balance for each balancing segment value or combination of multiple balancing
segment values to use in trial balance reporting. The three balancing segment labels are: primary, second, and third
balancing. The primary balancing segment label is required.
Cost Center: 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 are useful for detailed analysis and reporting. Cost centers are optional, but required if you are accounting for
depreciation, additions, and other transactions in Oracle Fusion Assets, and for storing expense approval limits in
Oracle Fusion Expense Management. If you are implementing Oracle Fusion Procurement, you can use cost centers
for business intelligence reporting and to route transactions for approval.
Natural Account: Determines the account type (asset, liability, expense, revenue, or equity) and other information
specific to the segment value. The natural account segment label is required.
Management: Optionally, denotes the segment that has management responsibility, such as the department, cost
center, or line of business. Also can be attached to the same segment as one of the balancing segments to make
legal entity reporting more granular.
Intercompany: Optionally, assigns the segment to be used in intercompany balancing functionality.
Note: All segments have a segment qualifier that enables posting for each value. The predefined setting is Yes
to post.
120
Account Combinations
An account combination is a completed code of segment values that uniquely identifies an account in the chart of accounts,
for example 01-2900-500-123, might represent InFusion America (company)-Monitor Sales (division)-Revenue (account)-Air
Filters (product).
Rules
The chart of accounts uses two different types of rules to control functionality.
Security rules: Prohibit certain users from accessing specific segment values. For example, you can create a
security rule that grants a user access only to his or her department.
Cross-validation rules: Control the account combinations that can be created during data entry. For example, you
may decide that sales cost centers 600 to 699 should enter amounts only to product sales accounts 4000 to 4999.
FAQs for Chart 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 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.
Value Sets
Chart of Accounts Values Sets: Critical Choices

A value set is the collection of account values that are associated with a segment of a chart of accounts structure instance.
When creating values sets, consider the following critical choices:
Module Designation
Validation Type
Format Assignments
Security Rules
Values Definition
Module Designation
The module designation is used to tag value sets in Oracle Fusion Applications and sets the value sets apart during upgrades
and other processes. Chart of accounts value sets upgraded from Oracle E-Business Suite Release 12 generically bear
the module value of Oracle Fusion Middleware. When creating value sets for a chart of accounts, the module can be
specified as Oracle Fusion General Ledger to distinctly identify its intended use in an accounting flexfield, basically a chart
of accounts.
121
Validation Type
Assign one of the following validation types to chart of accounts value sets:
Independent: The values are independently selected when filling out the segment in the account combination.
Table Validated: The values are stored in an external table to facilitate maintenance and sharing of the reference
data.
Caution: You must use Independent validation only for the Accounting Key Flexfield value sets. Other
validations prevent you from using the full chart of accounts functionality, such as data security, reporting, and
account hierarchy integration. Dependent values sets are not supported.
Format Assignments
Value sets for chart of accounts must use the Value Data Type of Character. The Value Subtype is set to Text. These
two setting support values that are both numbers and characters, which are typical in natural account segment values. Set
the maximum length of the value set to correspond to the length of the chart of accounts segment to which it is assigned.
Best practices recommend restricting values to Upper Case Only or Numeric values that are zero filled by default.
Security Rules
If flexfield data security rules are to be applied to the chart of accounts segment associated with the value set, the Enable
Security check box must be checked for the assigned value set. In addition, assign a data security resource name to enable
creation of a data security object automatically for the value set. The data security object is used in the definition of flexfield
data security rules.
Value Definition
Once these basic characteristic are defined for the value set, values can be added to the set in the Manage Values page.
Set the values to conform to the value set length and type.
Enter the value, its description, and its attributes including the Enable check box, Start Date, and End Date.
Assign the following attributes: Parent or Summary check box, Posting is allowed, and Budgeting is allowed.
Note: If the value set is used with a natural account segment, the value also requires you set the Natural
Account Type, with one of the following values: Asset, Liability, Equity, Revenue, or Expense. Other
attributes used are Third-Party Control Account, Reconciliation indicator, and Financial Category used
with Oracle Transaction Business Intelligence reporting. Oracle Fusion General Ledger best practice is to define
the values for the value set after the value set is assigned to a chart of accounts structure instance. Otherwise
you are not able to define the mandatory value attributes, such as the summary indicator, posting allowed, and
account type for natural account segment. The attributes must be added after the value set is assigned to a
chart of accounts structure instance.
Creating a Value Set for Your Chart of Accounts: Example

Create your value sets before creating your chart of accounts. A value set can be shared by different charts of accounts or
across different segments of the same chart of accounts.
122
Scenario
You are creating a company value set to be used in your chart of accounts for your enterprise, InFusion America, Inc. Follow
these steps:
1. Navigator > Setup and Maintenance > Manage Chart of Accounts Value Sets >Go to Task.
2. Click the Create icon on the toolbar of the Search Results table. The Create Value Set page opens.
3. Enter a unique Value Set Code, InFusion America Company, and an optional Description, Company values for
4. Select General Ledger from the list in the Module field.
5. Select Independent as Validation Type.
Note: You must use Independent validation only for the Accounting Key Flexfield value sets. Other
validations prevent you from using the full chart of accounts functionality, such as data security, reporting,
and account hierarchy integration. Dependent values sets are not supported.
6. Select Character as the Validation Data Type.
7. Save and Close.
Enabling Key Flexfield Segments for Business Intelligence: Points to

Consider
A key flexfield registered in the database as enabled for Oracle Business Intelligence (BI) includes a BI Enabled setting for
each of its segment instances. When a segment instance is BI-enabled, it's available for use in Oracle Business Intelligence.
The following aspects are important in understanding BI-enabled key flexfield segments.
use of the newly-generated attributes in business intelligence applications. For additional information about logical objects and
import, refer to the Oracle Transactional Business Intelligence Administrator's Guide.
Flattening
When you deploy a business intelligence-enabled key flexfield, the deployment process generates an additional set of
flattened business components for use in business intelligence. The flattened business components include attributes for
business intelligence-enabled segment instances only.
If you assigned a label to a segment, the flattened components include a single attribute representing all segment instances
with that label. If you didn't assign a label, the flattened components include a discrete attribute for each BI-enabled segment
instance in each structure.

You can simplify reporting by representing similar segments as a single logical object in Business Intelligence. If you assign
a label to segments that serve the same purpose in different structures, you can consolidate the segments into a single
123
attribute. This prevents duplication and the extra workload and complexity that result from the flattening process. For
example, an organization may have more than one definition of its key accounting flexfield to support different requirements
for accounting reporting. A US Accounting Flexfield structure may have a segment called Subaccount to track project
expenditures. The same type of information may be tracked in a UK accounting flexfield structure with a segment called
Project. Equalize these two segments to create a single list of values for reporting.
Non-labeled segments aren't equalized across context values, so the flattened components include a separate attribute for
each segment for each structure. It may not be possible to equalize similarly labeled segments if they have incompatible data
types or value set types.
Assign a label to a segment to map the corresponding attribute in the flattened components to a logical object in Oracle
Business Intelligence. Using labels to map segments to BI logical objects minimizes the steps for importing the flexfield into
Oracle Business Intelligence. Assigning a label to a segment serves to equalize the attribute across structures, as well as map
the equalized attribute to business intelligence.
Managing Labels
You may assign a predefined label (if available) to segments or create labels for assignment, as needed. Specify a code,
name, and description to identify each label. In the BI Object Name field, enter the name of the logical object in Oracle
structures.
intelligence, you must manually map the segment to the required logical object when importing into Oracle Business
Intelligence. In addition, segments without labels cannot be equalized across structures. The flattened components include a
separate attribute for each non-labeled segment in each structure.

repository to make use of the newly flattened business components in business intelligence. Then propagate the flexfield
<name>_c attributes for each segment, along with some other optional attributes. The <name>_ attribute contains
Related Topics
Enabling Descriptive Flexfield Segments for Business Intelligence: Points to Consider
124
Configuring Chart of Account Segments for Business Intelligence:

Explained
To map the Oracle General Ledger accounting flexfield in the Oracle Fusion Transaction Business Intelligence (BI) Repository
file (RPD) for Oracle Fusion Financials, populate values in the Manage Key Flexfields user interface. These values enable the
chart of accounts segments for Oracle Fusion Transactional BI. The values also provide the mapping with BI Object names
that are used as dimensions for each of the chart of accounts segments.
Follow these steps to select the BI enabled option for all chart of account segments that you intend to map in the RPD.
1. From your implementation project or the Setup and Maintenance page, query for Manage Key Flexfields > Go
to Task.
2. Enter GL# in the Key Flexfield Code field.
3. Click Search.
4. Click Manage Structure Instances.
5. Click Search.
6. Click the specific chart of accounts and click the Edit icon.
7. Click the specific segment and click the Edit icon.
8. Select the BI enabled option.
9. Click Save. This should be done for all segments in every chart of accounts structure instance that you intend to be
mapped in the RPD.
11. Click Done.
Follow these steps to specify a BI object name for each segment label. This name is the logical table name in the RPD that is
used as the dimension for the corresponding segment.
1. From your implementation project or the Setup and Maintenance page, query for Manage Key Flexfields > Go
to Task.
2. Enter GL# in the Key Flexfield Code field.
3. Click Search.
4. Select the Actions menu and click Manage Segment Labels.
5. Populate the BI Object Name field for all the segment labels that must be mapped in the RPD. Complete the fields,
as shown in this table.
Segment Label Code BI Object Name
FA_COST_CTR Dim - Cost Center

GL_BALANCING Dim - Balancing Segment

GL_ACCOUNT Dim - Natural Account Segment

6. Click Save.
Note: For all the nonqualified segment labels, populate the BI Object Name with one of the following values:
Dim - GL Segment1
125
Dim - GL Segment2
Dim - GL Segment3
Dim - GL Segment4
Dim - GL Segment5
Dim - GL Segment6
Dim - GL Segment7
Dim - GL Segment8
Dim - GL Segment9
Dim - GL Segment10
Deploy the flexfield using the Deploy Flexfield button on the Manage Key Flexfields page. For more information about
extending both key and descriptive flexfields into Oracle Fusion Transactional BI, refer to the Oracle Fusion Transactional
Business Intelligence Administrator's Guide.
Chart of Accounts Structures and Instances
Creating One Chart of Accounts Structure with Many Instances:

Example
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.
Scenario
Your company, InFusion Corporation, is a multinational conglomerate that operates in the United States (US) and the United
Kingdom (UK). InFusion has purchased an Oracle Fusion enterprise resource planning (ERP) solution including Oracle Fusion
General Ledger and all of the Oracle Fusion subledgers. You are chairing a committee to discuss creation of a model for your
global financial reporting structure including your charts of accounts for both your US and UK operations.
InFusion Corporation has 400 plus employees and revenue of $120 million. Your product line includes all the components to
build and maintain air quality monitoring (AQM) systems for homes and businesses.
Analysis
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.
Chart of Accounts Model

The chart of accounts structure provides the general outline of the chart of accounts and determines the number of
segments, the type, the length, and the label (qualifier) of each segment. This forms the foundation of the chart of accounts
definition object.
For each chart of accounts structure, it is possible to associate one or more chart of accounts structure instances. Chart of
accounts structure instances under the same structure share a common configuration with the same segments, in the same
126
order, and the same characteristics. Using one chart of accounts structure with multiple instances simplifies your accounting
and reporting.
At the chart of accounts structure instance level, each segment is associated with a value set that conforms to the
characteristic of that segment. For example, you assign a value set with the same segment type and length to each segment.
You are using hierarchies with your chart of accounts segments. Each structure instance segment is assigned a tree code
to indicate the source of the hierarchy information for the associated value set. The same value set can be used multiple
times within the same or across different chart of accounts instances within the same structure or in different structures. This
functionality reduces your segment value creation and maintenance across your charts of accounts.
The collective assignment of value sets to each of the segments forms one chart of accounts instance. At the chart of
accounts structure instance level, you can select to enable dynamic insertion. Dynamic insertion allows the creation of
account code combinations automatically the first time your users enter that new account combination. The alternative is
to create them manually. By deciding to enable dynamic insertion, you save data entry time and prevent delays caused by
the manual creation of new code combinations. Well defined cross validation rules help prevent the creation of inappropriate
account code combinations.
Perform deployment after a new chart of accounts structure and structure instances are defined or any of their modifiable
attributes are updated. Deployment validates and regenerates the necessary objects to enable your charts of accounts and
chart of accounts structure instances. By unifying and standardizing you organization's chart of accounts, you are positioned
to take full advantage of future functionality in Oracle Fusion General Ledger.
In summary, you are recommending to your company to unify the organization's chart of accounts in a single chart of
accounts structure based on chart of accounts commonalities across ledgers. You have also decided to use the chart of
accounts structure instance construct to serve different accounting and reporting requirements by using value sets specific to
each of your entities.
Creating Chart of Accounts Structure and Instances: Examples

In Oracle 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. 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.
The chart of accounts instance is exposed in user interfaces and processes. By default, a chart of accounts instance inherits
all of the attributes of the chart of accounts structure, meaning that all instances of the same structure share a common
shape and have the same segments in the same order. However, at the chart of accounts instance level, you can override the
default value set assignments for your segments and assign a unique account hierarchy that determines the parent and child
relationships between the value set values. At the chart of accounts instance level, you can determine whether to generate
new account combinations dynamically instead of creating them manually.
Chart of Account Structure

You are creating a chart of accounts structure as you set up a chart of accounts for your enterprise, InFusion America, Inc.
Follow these steps:
1. From the Setup and Maintenance work area, navigate to the Manage Chart of Accounts task.
2. Select the General Ledger module and click Search.
3. Click Manage Structures to open the Manage Key Flexfield Structures page.
4. Select the General Ledger row and click the Create icon to open the Create Key Flexfield Structure page.
5. Enter a unique structure code, INFUSION_AM_COA_STRUCTURE, and name, InFusion America COA
Structure. Provide an optional description, InFusion America Inc. chart of accounts structure.
6. Select a delimiter to visually separate the segment values.
127
7. Click Save.
8. To create a new segment, click the Create icon to open the Create Key Flexfield Segment page.
a. Complete the fields, as shown in this table.
Field Value
Segment Code INFUSION_AM_CO

Name InFusion America Company

Description InFusion America Inc.

Sequence Number 1

Prompt Company

Short Prompt CO

Display Width 2

Column Name Segment1

Default Value Set Code INFUSION_ AM_COMPANY

b. Select a segment label, Primary Balancing Segment, to indicate its purpose within your chart of accounts.
Note: Two segment labels are required: primary balancing segment and natural account segment.
These labels are not used with each other or with other labels in a specific segment.
c. Click Save and Close.
d. Click Done.
e. Define additional segments following the same process.
Chart of Account Instance

You are creating a chart of accounts instance as you set up your chart of accounts for your enterprise, InFusion America, Inc.
Follow these steps:
1. From the Setup and Maintenance work area, navigate to the Manage Chart of Accounts task.
2. Select the General Ledger module and click Search.
3. Select the General Ledger row and click Manage Structure Instances to open the Manage Key Flexfield
Structure Instance page.
4. Click the Create icon to open the Create Key Flexfield Structure Instance page.
5. Enter a unique structure instance code, INFUSION_AM_COA_INSTANCE, and name, InFusion America COA
Instance. Provide an optional description, InFusion America Inc. chart of accounts structure instance.
6. Select the Dynamic combination creation allowed option to indicate that you want to dynamically generate
account combinations.
7. Associate your instance with the structure InFusion America Structure.
128
Note: By default, an instance inherits the key attributes of the associated structure. Some attributes, such
as the value set assigned to each the segment, can be modified.
8. Click Save.
9. To modify an instance segment, select the segment row and click Edit.
10. Select the Required, Displayed, and BI enabled options.
Note: Select the Required and Displayed options for all segments including those intended for future
use. The recommended best practice is to define one segment for future use and set a default value.
This ensures room for expansion in your chart of accounts and that the extra segment is populated in the
account combinations. Select the BI (Business Intelligence) enabled option to use key flexfield segments
in Oracle Fusion Transactional Business Intelligence. The business intelligence option is only valid when
enabled on segments with segment labels. The second step is to populate the BI Object Name field for
each of the segment labels on the Manage Segment Label page opened from the Manage Key Flexfields
page.
11. Click OK.
13. Define additional instances following the same process.
Note: Alternatively, proceed directly with creating your value set values by selecting the corresponding
Value Set Code in the Segment Instances table.
14. Click Done.
15. Click Deploy Flexfield.
16. Click OK.
Balancing Segments: Explained

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.
The three balancing segment labels are:
Primary
Second
Third
Note: The primary balancing segment label is required.
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
insights into your operations as it affords you visibility along the critical fiscal dimensions you use to plan, monitor, and
measure your financial performance.
The following explains processes that use balancing segments.

Intercompany balancing: Adds lines to unbalanced journals using intercompany rules.
129
Opening first period of the accounting year: Calculates retained earnings amounts at the level of granularity that
totals revenue and expense account balances for multiple balancing segment value combinations. This applies to
standard and average balances.
Importing journals: Adds lines using the suspense account on unbalanced journals.
Posting journals: Adds additional lines to unbalanced journals for the following enabled account types:
Suspense
Rounding
Net income
Retained earnings
Cumulative translation adjustments from replication of revaluation journals to reporting currencies and for
multiple reporting currency account type specific conversion
Posting prior period journals: Calculates any income statement impact and posts to the appropriate retained
earnings account.
Translating balances: Supports multiple balancing segments for the following accounts:
Retained earnings: Calculated translated retained earnings are post to the retained earnings accounts by
balancing segment. Retained earnings accounts represent the summing of the translated revenue and
expense accounts across multiple balancing segment values.
Cumulative translation adjustment: Amounts posted by balancing segment to these accounts represents
currency fluctuation differences between ranges of accounts which use different rate types. For example,
period end rates are used for asset and liability accounts and historical rates for equity accounts.
Revaluing Balances: Supports multiple balancing segments when calculating gain or loss accounts.
Creating Opening Balances: Initializes reporting currency balances by converting from the total primary currency. Any
difference in the reporting currency amounts is offset by populating retained earnings accounts.
Closing year end: Supports multiple balancing segments when calculating the income statement offset and closing
account in the closing journals.
Multiple Balancing Segments: Points to Consider

Oracle Fusion General Ledger supports tracking financial results at a finer level of granularity than a single balancing segment.
In addition to the required primary balancing segment for the chart of accounts, which is typically associated with the
company dimension of a business organization, two additional segments of the chart of accounts can be optionally qualified
as the second and third balancing segments respectively. Possible chart of accounts segments that can be tagged as
these additional balancing segments include cost center or department, additional aspects of a business commonly used in
measuring financial results.
Several points must be consider when using multiple balancing segments:
Journal entry processing

Implementation timing
Change options
Migration adjustments
130
Journal Entry Processing

Multiple balancing segments ensure that account balances come from journal entries where the debits equal the credits.
The financial reports are properly generated for each unique instance of account value combinations across the balancing
segments. Consider this option carefully as it provides more granular reporting but requires more processing resources.
Implementation Timing
When using optional second and third balancing segments, remember that these chart of accounts segment labels are set
from the beginning of time. Ensure that balances are immediately maintained in accordance with the necessary balancing
actions to produce consistent financial reporting for the wanted business dimensions. Multiple balancing segment ledgers
that are not maintained from the beginning of time, require extensive manual balance adjustments to catch up and realign the
balances.
Note: Do not set a segment already qualified as a natural account or intercompany segment as any of the three
balancing segments. Validations are not performed when segment labels are assigned, so verify that all are
assigned correctly before using your chart of accounts.
Change Options
Once a segment has been enabled and designated as a balancing segment, you must not change the segment. Do not
disable the segment or remove the segment labels. These settings must be consistently maintained throughout the life of the
chart of accounts to control the accuracy and integrity of the financial data.
Migration Adjustments
For charts of accounts migrated from Oracle E-Business Suite to Oracle Fusion General Ledger that uses a second and third
balance segments, steps must be taken to ensure the proper transition. The required adjustments are extensive.
For ledgers associated with a migrated chart of accounts, the balances must be adjusted manually. The manual adjustment
is to ensure that the second and third balancing segments are consistent as though these segment labels have been in place
since the beginning of entries for these ledgers. Recomputing and updating of the following processes is required to reflect
the correct balancing for each account using the second and third balancing segments.
Intercompany balancing
Suspense posting
Rounding imbalance adjustments on posting
Entered currency balancing
Revaluation gains or losses
Retained earnings calculations at the opening of each new fiscal year
Cumulative translation adjustments during translation
Note: All previously translated balances must also be purged. New translations must be run to properly account
for translated retained earnings and cumulative translation adjustments with the correct level of balancing.
Related Topics
How can I change segments in an existing chart of accounts structure?
131
Using Multiple Balancing Segments: Example

This simple example illustrates balancing along two balancing segments for a simple chart of accounts with three segments.
Scenario
Your company has a chart of accounts with two balancing segments and three segments, qualified as follows:
Company: Primary balancing segment
Cost Center: Second balancing segment
Account: Natural account segment
The following table shows a journal that was entered to transfer advertising and phone expense from company 1, cost center
A to company 2, cost center B.
Line Account Debit Credit
1 Company 1-Cost Center A- 600 0

Advertising Expense Account

2 Company 2-Cost Center B- 0 600



Phone Expense Account



The posting process creates journal lines to balance the entry across the primary and second balancing segments, company
and cost center. The following table shows all of the journal lines, including balancing lines 5 through 8, which were
automatically created.









Balancing Account
132


Balancing Account


Balancing Account


Balancing Account

Flexfield Deployment
133
Introducing the Oracle Fusion Financials Deployment Options:

Overview
The following deployment options are available:
On-Premises
Applications
Public Cloud Private Cloud
Applications Applications
Hybrid
On-Premises: Hardware, software licenses, and support that you buy and host at one or more of your sites.
Public Cloud: Services are available to the general public and offered on a subscription basis, with no requirements
to buy additional licenses or support. The services are hosted over the Internet by Oracle or Oracle business partners
that offer business process outsourcing solutions.
Private Cloud: Application-managed and technology-managed services that are offered for Oracle software and
hardware, are available internally behind a firewall, and are hosted over the Internet by Oracle or Oracle business
partners that offer business process outsourcing solutions.
Hybrid: Combinations you select including maintaining some or all of your existing legacy applications on-premises
and buying additional products that are hosted on the private or public cloud.
The following table lists each deployment option, along with key benefits and information about monitoring, security, patching,
and upgrades.
134
Deployment Option Key Benefits Monitoring, Security, Patching, and Upgrades
On-Premises You decide what you must do with the You are responsible.
hardware, software licenses and support you
bought. You decide what to host.

Public Cloud You select services available on the public Provider of the services responsible within
cloud on subscription basis. the provisions of the subscription.

Private Cloud Oracle provides management, monitoring, Oracle is responsible.

patching, security, and upgrade services.

Hybrid Flexibility and lower implementation costs Depends on the combination.

depending on the combination of products.

Run Deployment: Examples

After uploading the Chart of Accounts spreadsheet, deploy the accounting flexfield
Scenario
1. (N) Setup and Maintenance > Deploy Chart of Accounts task > (B) Deploy the Accounting Flexfield.
2. (I) Refresh until the green check mark appears and verifies that the deployment is successful.
Note: This action deploys all instances of the accounting flexfield. If there are errors in any instance the process
stops. Correct the errors and run the process again.
Flexfield Deployment: Explained

Deployment generates or refreshes the Application Development Framework (ADF) business component objects that render
the flexfield in a user interface. The deployment process adds custom 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 custom 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 custom attributes. You must
sign out and sign back in to Oracle Applications Cloud to see the changes you deployed in the run time.
The following aspects are important in understanding flexfield deployment:

Deployment Status
Initial Deployment Status
135
Metadata Validations
Metadata Synchronization
Deployment as a Background Process
Export of Artifacts from Flexfield MDS
Deployment Status
Every flexfield has a deployment status. The following table lists the different deployment statuses.
Deployment Status Meaning
Edited The flexfield metadata definition hasn't been deployed yet. Updates of the metadata definition aren't
applied in the run time environment yet.

Patched The flexfield metadata definition has been modified through a patch or a data migration action,
but the flexfield hasn't yet been deployed. So, the updated definition isn't reflected in the run time
environment.

Deployed to Sandbox The current metadata for the flexfield is deployed in ADF artifacts and available as a flexfield-enabled
sandbox. The status of the sandbox is managed by the Manage Sandboxes task available to the
Administrator menu of the Setup and Maintenance work area.

Deployed The current metadata for the flexfield is deployed in ADF artifacts and available to users. No changes
have been made to the flexfield after being deployed to the mainline metadata.

Error The deployment attempt in the mainline metadata failed.

Note: Whenever a value set definition changes, the deployment status of a flexfield that uses that value set
changes to edited. If the change results from a patch, the deployment status of the flexfield changes to patched.
Initial Deployment Status of Flexfields

The Oracle Applications Cloud implementation loads flexfield metadata into the database. This initial load sets the flexfield
status to Edited. During installation, the application provisioning process deploys the flexfields of the provisioned applications,
setting their status to Deployed if no errors occur.
In a provisioned application, deployed flexfields are ready to use. In some cases, flexfield availability at run time requires
setup, such as defining key flexfields.
Metadata Validation
Use the Validate Metadata command to view possible metadata errors before attempting to deploy the flexfield. Metadata
validation is the initial phase of all flexfield deployment commands. By successfully validating metadata before running the
deployment commands, you can avoid failures in the metadata validation phase of a deployment attempt. The deployment
process ends if an error occurs during the metadata validation phase. Metadata validation results don't affect the deployment
status of a flexfield.
Metadata Synchronization
When an extensible or descriptive flexfield is deployed, the deployment process regenerates the XML schema definition
(XSD). As a result, the custom attributes are available to web services and the SOA infrastructure.
136
After deploying a flexfield configuration, you must synchronize the updated XML schema definition (XSD) files in the MDS
repositories for each SOA application.
Note: To synchronize the updated XSD files in the MDS repositories in Oracle Cloud implementations, log a
service request using My Oracle Support at http://support.com/
Deployment as a Background Process

You can deploy extensible flexfields offline as a background process and continue working in the session without having to
wait for the deployment to complete. You can queue up several extensible flexfields and deploy as a background process.
The flexfields are deployed, one at a time, in the order that you deploy them to the queue. You must deploy extensible
flexfields with more than 30 categories as a background process.
You can remove an extensible flexfield from the deployment queue with the Cancel Background Deployment command.
When an extensible flexfield is deployed in a background process, its offline status indicates that the flexfield is in a
background deployment process. A flexfield's offline status is cleared and its deployment status updated when the
background deployment process has completed.
Export of Artifacts from Flexfield MDS

You can export business components from MDS for descriptive, extensible, or key flexfields, mainly for use in troubleshooting
issues with flexfields. Use Download Flexfield Archive on the Manage Flexfields page to export MDS artifacts of the
selected flexfield, and import them to an archive on your local computer. You can use these archived business components
of flexfields for troubleshooting purposes.
Alternatively, export the deployed artifacts using exportMetadata WLST.
Related Topics
Flexfields and Oracle Applications Cloud Architecture: How They Work Together
Why did my flexfield changes not appear in the run time UI?
Flexfield Deployment Status: How It's Calculated

Flexfield deployment status indicates how the flexfield metadata definition in the Oracle Applications Cloud database relates
to the Application Development Framework (ADF) business components residing in an Oracle Metadata Services (MDS)
Repository.
The following aspects are important in understanding how flexfield deployment status is calculated:
Settings that affect flexfield deployment status
How deployment status is calculated
Settings That Affect Flexfield Deployment Status

If you have made a change to a flexfield and expect a changed deployment status, ensure that you have saved your changes.
No settings affect flexfield deployment status.
How Deployment Status Is Calculated

If the flexfield definition has been edited through the Define Flexfields activity task flows, the status is Edited. The latest
flexfield metadata definition diverges from the latest deployed flexfield definition. Any change, including if a value set used in a
flexfield changes, changes the deployment status to Edited. If a flexfield has never been deployed, its status is Edited.
137
Note: When an application is provisioned, the provisioning framework attempts to deploy all flexfields in that
application.
If you deploy the flexfield to a sandbox successfully, the status is Deployed to Sandbox. The latest flexfield metadata definition
in the application matches with the metadata definition that generated ADF business components in a sandbox MDS
Repository. Whether the sandbox is active or not doesn't affect the deployment status. If the flexfield was deployed to a
sandbox and hasn't been edited or redeployed to the mainline metadata since then, the status remains Deployed to Sandbox
independent of whether the sandbox is active, or who is viewing the status.
If you deploy the flexfield successfully to the mainline metadata, the status is Deployed. The latest flexfield metadata definition
in the application matches the metadata definition that generated ADF business components in a mainline MDS Repository.
Change notifications are sent when a flexfield is deployed successfully to the mainline metadata. If either type of deployment
fails and that the current flexfield definition isn't deployed, the status is Error. The deployment error message gives details
about the error. The latest flexfield metadata definition in the application likely diverges from the latest successfully deployed
flexfield definition.
If the flexfield definition has been modified by a patch, the status is Patched. The latest flexfield metadata definition in the
application diverges from the latest deployed flexfield definition. If the flexfield definition was Deployed before the patch and
then a patch was applied, the status changes to Patched. If the flexfield definition was Edited before the patch and then a
patch was applied, the status remains at Edited to reflect that there are still changes (outside of the patch) that aren't yet in
effect.
When a deployment attempt fails, you can access the Deployment Error Message for details.
Related Topics
Managing Extensible Flexfields: Points to Consider
Deploying a Flexfield-Enabled Sandbox: How It Works With Mainline

Metadata
The flexfield definition in a sandbox corresponds to the flexfield metadata definition in the Oracle Fusion Applications database
at the time the flexfield was deployed to the sandbox. When the flexfield is ready for end users, the flexfield must be deployed
to the mainline metadata.
A flexfield-enabled sandbox uses the following components.
Flexfield metadata in the Oracle Applications Cloud database

Flexfield business components in a sandbox Oracle Metadata Services (MDS) repository
User interface customizations for the flexfield in the mainline MDS repository
The following figure shows the two types of deployment available in the Manage Flexfield tasks of the Define Flexfields activity.
Deploying a flexfield to a sandbox creates a sandbox MDS Repository for the sole purpose of testing flexfield behavior. The
sandbox is only accessible to the administrator who activates and accesses it, not to users generally. Deploying a flexfield to
the mainline metadata applies the flexfield definition to the mainline MDS Repository where it is available to end users. After
138
deploying the flexfield to the mainline metadata, customize the page where the flexfield segments appear. Customization of
the page in the sandbox MDS Repository cannot be published to the mainline MDS Repository.
Access
Deploy flexfield to
sandbox to
sandbox.
test flexfield.
Flexfield
Metadata in Yes
Flexfield Business
Oracle Fusion
Components in Metadata
Applications
Services (MDS) Flexfield-
Database
Test in sandbox? Repository Sandbox enabled
Sandbox
Define
Flexfields
Deploy flexfield for

other users? Flexfield Business
Deployed
Components in Metadata
Flexfield
Services (MDS)
Yes Repository Mainline
Flexfield
Definition Access
Deploy flexfield.
mainline.
MDS
customizations?
Customizations in Yes
Metadata Services
Repository (MDS) Mainline
Sandbox Metadata Services Repository Data

Deploying the flexfield to a sandbox generates the Application Development Framework (ADF) business components of a
flexfield in a sandbox MDS Repository for testing in isolation.
Caution: Don't customize flexfield segment display properties using Page Composer in a flexfield-enabled
sandbox as these changes will be lost when deploying the flexfield to the mainline metadata.
139
Mainline Metadata Services Repository Data

The Oracle Fusion Applications database stores the single source of truth about a flexfield. When the flexfield is deployed, the
ADF business component objects that implement the flexfield in the run time user interface are generated in the mainline MDS
Repository from this source.
Related Topics
Managing Customizations Using Sandboxes: Explained
Deploying a Flexfield to a Sandbox: Points to Consider

Deploying a flexfield to a sandbox creates a flexfield-enabled sandbox. Each flexfield-enabled sandbox contains only one
flexfield.
You can test the run time behavior of a flexfield in the flexfield-enabled sandbox. If changes are needed, you return to the
Define Flexfield tasks to change the flexfield definition.
When you deploy a flexfield to sandbox, the process reads the metadata about the segments from the database, generates
flexfield Application Development Framework (ADF) business component artifacts based on that definition, and stores in the
sandbox only the generated artifacts derived from the definition.
When you deploy a flexfield sandbox, the process generates the name of the flexfield sandbox, and that flexfield sandbox is
set as your current active sandbox. When you next sign in to the application, you can see the updated flexfield configurations.
The Oracle Applications Cloud global header displays your current session sandbox.
Note: Unlike a standalone sandbox created using the Manage Sandboxes tool, the sandbox deployed for
a flexfield contains only the single flexfield. You can manage flexfield sandboxes, such as setting an existing
flexfield sandbox as active or deleting it, using the Manage Sandboxes tool.
When you deploy a flexfield to the mainline metadata after having deployed it to the sandbox, the sandbox-enabled flexfield is
automatically deleted.
Sandbox MDS Repository Data

The sandbox data lets you test the flexfield in isolation without first deploying it in the mainline metadata where it could be
accessed by users.
Caution: Don't customize flexfield segment display properties using Page Composer in a flexfield-enabled
sandbox as these changes will be lost when deploying the flexfield to the mainline metadata.
Managing a Flexfield-Enabled Sandbox

When you deploy a flexfield as a sandbox, that flexfield-enabled sandbox automatically gets activated in your user session.
When you sign back in to see the changes, the sandbox is active in your session.
You can only deploy a flexfield to a sandbox using the Define Flexfields task flow pages.
You also can use the Manage Sandboxes feature in the Administration menu of the Setup and Maintenance work area to
activate and access a flexfield-enabled sandbox.
140
Note: Whether you use the Define Flexfields or Manage Sandboxes task flows to access a flexfield-enabled
sandbox, you must sign out and sign back in before you can see the changes you deployed in the run time.
You cannot publish the flexfield from the sandbox to the mainline metadata. You must use the Define Flexfields task flow
pages to deploy the flexfield for access by users of the mainline metadata because the flexfield configuration in the mainline
metadata is the single source of truth.
Related Topics
Why did my flexfield changes not appear in the run time UI?
Managing Customizations Using Sandboxes: Explained
Deploying Flexfields Using the Command Line: Explained

You can use the Manage Key Flexfields, Manage Descriptive Flexfields, and Manage Extensible Flexfields tasks to deploy
flexfields. You can also use WebLogic Server Tool (WLST) commands for priming the Oracle Metadata Services (MDS)
Repository with predefined flexfield artifacts and for deploying flexfields.
The following table describes the available commands.
WebLogic Server Tool Command Description
Deploys all flexfields for the specified enterprise application. Only flexfields whose status is other
deployFlexForApp than deployed are affected by this command, unless the option is enabled to force all flexfields to be
deployed, regardless of deployment status.

Initial application provisioning runs this command to prime the MDS Repository with flexfield
artifacts.

Deploy a single flexfield regardless of deployment status

deployFlex
Deploys flexfield changes that have been delivered using a flexfield Seed Data Framework (SDF)
deployPatchedFlex patch. Deploys flexfields that have a Patched deployment status.

Displays MDS label of flexfield changes for viewing and deleting patching labels.
deleteFlexPatchingLabels
Displays list containing flexfields that aren't deployed or failed deployment.

validateFlexDeploymentStatus
Executing these commands outputs a report at the command line. The report provides the following information for every
flexfield that is processed.
Application identity (APPID)

Flexfield code
Deployment result, such as success or error
141
In case of errors, the report lists the usages for which errors occurred. If a run time exception occurs, the output displays the
trace back information. For each WLST flexfield command, adding the reportFormat='xml' argument returns the report as an
XML string.
Consider the following aspects of command-line deployment.
Preparing to use the WLST flexfield commands

Using the deployFlexForApp command
Using the deployFlex command
Using the deployPatchedFlex command
Using the deleteFlexPatchingLabels command
Using the validateFlexDeploymentStatus command
Closing WLST and checking the results
Preparing To Use the WLST Flexfield Commands

You can only execute the WLST flexfield commands on a WebLogic Administration Server for a domain that has a running
instance of Oracle Fusion Middleware Extensions for Oracle Application.
For more information about deploying the Oracle Fusion Middleware Extensions for Oracle Application to the server domains,
see the Oracle Fusion Applications Developer's Guide.
Ensure that the AppMasterDB data source is registered as a JDBC data source with the WebLogic Administration Server and
points to the same database as the ApplicationDB data source.
Start the WebLogic Server Tool (WLST) if not currently running.
UNIX:
sh $JDEV_HOME/oracle_common/common/bin/wlst.sh
Windows:
wlst.cmd
Connect to the server, replacing the user name and password arguments with your WebLogic Server user name and
password.
connect('wls_username', 'wls_password', 'wls_uri')
The values must be wrapped in single-quotes. The wls_uri value is typically T3://localhost:7101.
For more information about the WLST scripting tool, see the Oracle Fusion Middleware Oracle WebLogic Scripting Tool.
Using the deployFlexForApp Command

The deployFlexForApp command translates the product application's predefined flexfield metadata into artifacts in the MDS
Repository.
142
Note: This command is run automatically when you provision applications. However, if you customize
applications, you have to manually run it following the order of tasks as given here:
1. Configure your application to read the flexfield artifacts from the MDS Repository.
2. Run the deployFlexForApp command.
3. Sign in to the application.
This sequence of steps is required even if there is no predefined flexfield metadata.
This command doesn't deploy flexfields that have a status of Deployed unless the force parameter is set to 'true' (the default
setting is 'false').
For more information about priming the MDS partition with configured flexfield artifacts, see the Oracle Fusion Applications
Developer's Guide.
From the WLST tool, execute the following commands to deploy the artifacts to the MDS partition, replacing
product_application_shortname with the application's short name wrapped in single-quotes.
deployFlexForApp('product_application_shortname'[, 'enterprise_id'] [,'force'])
In a multi-tenant environment, replace enterprise_id with the Enterprise ID to which the flexfield is mapped. Otherwise,
replace with 'None' or don't provide a second argument.
To deploy all flexfields regardless of their deployment status, set force to 'true' (the default setting is 'false'). To deploy all
flexfields in a single-tenant environment, you either can set enterprise_id to 'None', or you can use the following signature:
deployFlexForApp(applicationShortName='product_application_shortname',force='true')
The application's short name is the same as the application's module name. For more information about working with
application taxonomy, see the Oracle Fusion Applications Developer's Guide.
Using the deployFlex Command

From the WLST tool, execute the following command to deploy a flexfield, replacing flex_code with the code that identifies
the flexfield, and replacing flex_type with the flexfield's type, either descriptive flexfield, key flexfield, or extensible flexfield.
The values must be wrapped in single-quotes.
deployFlex('flex_code', 'flex_type')
Optionally, execute the following command if the flexfield is an extensible flexfield, and you want to deploy all the flexfield's
configurations.
Note: By default, extensible flexfields are partially deployed. That is, only the pages, contexts, or categories that
had recent changes, are deployed.
deployFlex('flex_code', 'flex_type', ['force_Complete_EFF_Deployment'])
where, forceCompleteEFFDeployment=None
Using the deployPatchedFlex Command

Use the deployPatchedFlex command for situations where the patching framework doesn't initiate the command, such as
when an application has been patched offline.
If the installation is multi-tenant enabled, the command deploys all patched flexfields for all enterprises. This command isn't
intended to be initiated manually.
Check with your provisioning or patching team, or the task flows for managing flexfields, to verify that the flexfield has a
Patched deployment status.
143
From the WLST tool, execute the following command to deploy the artifacts to the MDS partition.
deployPatchedFlex()
Execute the following command to deploy all flexfields that have either a READY status or an ERROR status.
deployPatchedFlex(mode='RETRY')
Using the deleteFlexPatchingLabels Command

Whenever you deploy flexfield changes to MDS using the deployPatchedFlex() WLST command, an MDS label is created in
the format FlexPatchingWatermarkdate+time. Use the deleteFlexPatchingLabels command to inquire about and delete these
labels.
From the WLST tool, execute the deleteFlexPatchingLabels () command with no arguments to delete the flexfield patching
labels.
To output a list of flexfield patching labels, execute the command with the infoOnly argument, as follows:
deleteFlexPatchingLabels(infoOnly='true')
Using the validateFlexDeploymentStatus Command

The validateFlexDeploymentStatus() WLST command checks the deployment status of all flexfields in an Oracle Fusion
Applications deployment.
validateFlexDeploymentStatus()
Use this command to verify that all flexfields in the current instance of provisioned Java EE applications are deployed.
Closing WLST and Checking the Results

To close the tool, execute the command: disconnect().
Optionally, sign in the application, open user interface pages that contain flexfields, and confirm the presence of flexfields for
which configuration exists, such as value sets, segments, context, or structures.
General Ledger Security
General Ledger Security: Explained

General ledger functions and data are secured through job roles, data access sets, and segment value security rules.
Functional Security
Functional security, which is what you can do, is managed using job roles. The following job roles are predefined for Oracle
Fusion General Ledger:
General Accounting Manager
General Accountant
Financial Analyst
Each job role includes direct privilege grants, as well as duty role assignments, to provide access to application functions that
correspond to their responsibilities. For example, the General Accounting Manager role grants comprehensive access to all
General Ledger functions to the general accounting manager, controller, and chief financial officer in your organization.
144
Data Security
Data security, which controls what action can be taken against which data, is managed using:
Data access sets

Segment value security rules
Data access sets can be defined to grant access to a ledger, ledger set, or specific primary balancing segment values
associated with a ledger. You decide whether each data access set provides read-only access or read and write access to
the ledger, ledger set, or specific primary balancing segment values, which typically represent your legal entities that belong to
that ledger. Primary balancing segment values without a specific legal entity association can also be directly assigned to the
ledger.
Segment value security rules control access to data that is tagged with the value set values associated with any segment in
your chart of accounts.
Security Assignment
Use the Security Console to assign users roles (job roles, as well as roles created for segment value security rules or others).
Use the Manage Data Access Set Data Access for Users task to assign users data access sets as the security context paired
with their General Ledger job role assignments.
For more information about security assignments, see the Securing Oracle ERP Cloud guide.
Data Access Set Security: Overview

Data Access Sets secure access to ledgers, ledger sets, and portions of ledgers using primary balancing segment values.
If you have primary balancing segment values assigned to a legal entity, then you can use this feature to secure access to
specific legal entities.
You can combine ledger and ledger set assignments in single data access sets if the ledgers share a common chart of
accounts and calendar. If you have primary balancing segment values assigned to a legal entity within the ledger, then
you can use data access sets to secure access to specific legal entities. You can also secure access to primary balancing
segments assigned directly to the ledger.
When a ledger or ledger set is created, a data access set for that ledger or ledger set is automatically created, giving full read
and write access to those ledgers. You can also manually create data access sets to give read and write access, or read-only
access to entire ledgers or portions of the ledger represented as primary balancing segment values.
145
This figure shows how data access sets consist of an access set type and an access level.
Data Access Set
Access Set
Access Level
Type
Primary
Full Ledger Balancing Read Only Read and Write
Segment Value
The Full Ledger access set type provides access to the entire ledger or ledger set. This could be for read-only access or
both read and write access to the entire ledger.
The Primary Balancing Segment Value access set type provides access to one or more primary balancing segment values
for that ledger. This access set type security can be specified by parent or detail primary balancing segment values. The
specified parent value and all its descendants, including middle level parents and detail values are secured. You can specify
read only, read and write access, or combination of both, for different primary balancing segment values for different ledgers
and ledger sets.
Data Access Set Security: Examples

This example shows a data access set that secures access by using primary balancing segment values that correspond to
legal entities.
146
Scenario
This figure shows a data access set for the US Financial Services Ledger. The access set type is Primary Balancing Segment
Value, with each primary balancing segment values representing different legal entities. One access set assignment provides
read-only access and the other, read and write access to the corresponding legal entities' primary balancing segment value.
US Financial Services Ledger
Access Level Read and

Read Only
Write
Primary 131 101 102

Balancing Insurance Banks Capital
Segment
Values
View Journals View, Create, Post Journals

Actions View Balances View and Update Balances
View and Run Reports View and Run Reports
Read-only access has been assigned to primary balancing segment value 131, which represents the Insurance legal entity.
Read and write access has been assigned to the other two primary balancing segment values 101 and 102, which represent
the Banks and Capital legal entities.
For this data access set, the user can:
View the journals, balances, and reports for primary balancing segment value 131 for the Insurance legal entity.
Create journals and update balances, as well as view journals, balances and reports for primary balancing segment
value 101 and 102 for legal entities Banks and Capital.
Note: In financial reporting, the list of ledgers isn't secured by data access sets when viewing a report in
Preview mode. Users can view the names of ledgers they don't have privileges to view. However, the data from
a secured ledger doesn't appear on the report.
Segment Value Security: Explained

Set up segment value security rules on value sets to control access to parent or detail segment values for chart of accounts
segments, also called flexfield segments. Segment value security rules restrict data entry, online inquiry, and reporting.
147
Secured Value Sets

When you enable security on a value set, access to all values for that value set is denied. To control access to value set
values, you enable security on the value set, create conditions, and then assign the conditions to roles. The roles should be
created solely for the purpose of segment value security. The roles are then assigned to users.
If a value set is secured, every usage of that value set in a chart of accounts structure instance is secured. For example the
same security applies if that value set is:
Used for two or more segments in the same chart of accounts, such as the primary balancing and intercompany
segments
Shared across different segments of different charts of accounts
Secured Segment Values

Segment value security applies mainly when data is created or updated, and when account combinations are queried.
When you have access to secured account values, you can view and use those secured values across all modules of the
applications where there are references to accounting flexfields including:
Transaction entry pages

Balances and transactions inquiry pages
Setup pages
Reports
On setup pages, you can still view referenced account combinations with secured account values, even if you haven't been
granted access to those secured values. However, if you try to update such references, you can't use those secured values.
On reports, you can view balances for secured account values only if you have access to those secured values.
Note: You can enforce segment value security for inquiries and reporting based on any hierarchy, even
hierarchies that aren't published to the reporting cube.
148
Segment Value Security Implementation

This figure shows the steps for defining and implementing security rules for segment values.
Security Console Manage Value Sets Page
Create roles for

segment value Enable security
security
Create conditions
Create policies
Manage Chart of Accounts

Structures Page
Assign roles to users
Deploy the flexfield
Publish Account Hierarchies

Page
Publish account
hierarchy version
To define segment value security roles:

Create segment value security roles.
Enable security on the value set.
Note: You can enable security only on value sets with a type of Independent.
Create conditions for the rule.
149
Create policies to associate the conditions with the role.

Deploy the accounting flexfield.
Publish the account hierarchies.
Assign the role to users.
Whenever you assign segment value security roles to a user, the rules from the user's assigned roles can be applied together.
All of the segment value security roles assigned to a user pertaining to a given value set are simultaneously applied when the
user works with that value set. For example, one rule provides access to cost center 110 and another rule provides access
to all cost centers. A user with both of these segment value security rules has access to all cost centers when working in a
context where that value set matters.
Segment Value Security Conditions

When you create a condition, you specify an operator. The following table describes the operators that you can use.
Operator Usage
Equal to Provides access to a specific detail or child value.

Don't use to provide access to a parent value.
Not equal to Provides access to all detail and child values, except the one that you specify.
Don't use to provide access to a parent value.
Between Provides access to a detail range of values.

Is descendant of Provides access to the parent value itself and all of its descendants including middle level
parents and detail values.
Is last descendant of Provides access to the last descendants for example, the detail values of a parent value.

Tip: For the operators Is descendant of and Is last descendant of:

Specify an account hierarchy (tree) and a tree version to use these operators.
Understand that the security rule applies across all the tree versions of the specified hierarchy, as well as all
hierarchies associated with the same value set of the specified hierarchy.
Segment Value Security: Examples

You can set up segment value security rules on value sets to control access to parent or detail segment values for chart of
accounts segments. Segment value security rules restrict data entry, online inquiry, and reporting.
The following example describes why and how you might want to use segment value security.
Securing Values for the Cost Center and Account Segments

For this scenario, only certain users should have access to the Accounting cost center and the US Revenue account. To
create a complete data security policy that restricts segment value access to those users:
1. Plan for the number of roles that represent the unique segment value security profiles for your users. For this
scenario, you can create two roles, one for the cost center segment and one for the account segment.
150
2. Use the Security Console to create the roles. Append the text SVS-role to the role names so it's clear the roles are
solely for segment value security. For this scenario, you create roles Accounting Cost Center-SVS Role and US
Revenue Account-SVS Role.
3. Use the Manage Segment Value Security Rules task to enable security on the cost center and account value sets
that are associated with the chart of accounts.
4. Create a condition for each value set. For example, the condition for the Accounting cost center is that the cost
center is equal to Accounting.
5. Create a policy to associate the conditions to the roles. For example, create a policy to assign the condition for the
Accounting cost center to the role Accounting Cost Center-SVS Role.
6. Use the Security Console to assign the appropriate role to the appropriate user. For example, assign the role
Accounting Cost Center-SVS Role to the users who should have access to the Accounting cost center.
This figure shows how the conditions and roles combine to create the security policies for this scenario.
Security Condition Role Security Policy
Cost Center + Accounting Cost = Associated

Equal to Center-SVS Role with the Cost Center
Example
Accounting Value Set
Security Condition Role Security Policy
Account + US Revenue = Associated

with the Account
Equal to Account-SVS Role
US Revenue Value Set
Enabling Security on a Chart of Accounts: Worked Example

This example demonstrates how to enable security on a chart of accounts to control access to specific segment values.
The following table summarizes the key decisions for this scenario.
Decisions to Consider In This Example
Which segment in the chart of accounts must be restricted? Cost center

Which cost center values have to be granted to different users? Child values 110 to 120
Child value 310
Parent value 400 and all its children
All cost centers
What's the name of the value set for the Cost Center segment? Cost Center Main

What's the name of the user who can access cost centers 110 to Casey Brown
120?

What's the name of the tree for the accounting flexfield? All Corporate Cost Centers

151
What version of the tree hierarchy does the condition apply to? V5

Summary of the Tasks and Prerequisites

This example includes details of the following tasks you perform when defining and implementing segment value security.
1. Define roles for segment value security rules.

2. Enable segment value security for the value set.
3. Define the conditions.
4. Define the policies.
5. Deploy the accounting flexfield.
6. Publish the account hierarchies.
7. Assign segment value security roles to users.
Perform the following prerequisites before enabling security on a chart of accounts:
To work with the Security Console, you need the IT Security Manager role assigned to your user setup.
To work with value sets and profile options, you need the Financial Application Administrator role.
Set the Enable Data Security Polices and User Membership Edit profile to Yes.
Defining Roles for Segment Value Security Rules

To create a complete data security policy, create the roles first so that they're available for
assignment to the segment value security rules.
1. In the Tools work area, open the Security Console.
2. Perform the following steps four times to create four roles.
3. Click Create Role.
4. On the Create Role page, complete the fields as shown in this table, and then click Next, Next, Next, Next, Next,
Save and Close.
5. Click OK and complete the fields, as shown in this table.
Field Role 1 Role 2 Role 3 Role 4
Cost Center 110-120 Cost Center 310 SVS Cost Center 400 SVS Cost Center All SVS
Role Name SVS Role Role Role Role

CC_ 110_ CC_ 310_SVS_ROLE CC_ 400_SVS_ROLE CC_ ALL_SVS_ROLE

Role Code 120_SVS_ROLE

Default Default Default Default

Role Category
Access to cost centers Access to cost center Access to parent cost Access to all cost
Description 110 to 120. 310. center 400 and all its centers.
children.

152
The following figure shows the Create Role page for the first role.
Enabling Segment Value Security for the Value Set

1. In the Setup and Maintenance work area, search for and select the Manage Segment Value Security Rules task.
2. In the Value Set Code field, enter Cost Center Main and click Search.
3. In the Search Results section, click Edit to open the Edit Value Set page.
4. Select the Security enabled option.
5. In the Data Security Resource Name field, enter Secure_Main_Cost_Center_Values.
6. Click Save.
153
The following figure shows the Edit Value Set page after enabling security for the Cost Center Main value set.
Defining the Conditions

Use conditions to specify the segment values that require security.
Segment value security rules that provide access to all segment values, and segment value security rules that provide access
to single nonparent segment values, don't need a condition. Instead, you can define the policy to cover all values, and you
can define a policy to cover a single nonparent segment value provided that you know the internal ID for that segment value. If
you don't know the internal ID, you can create a condition for that single segment value.
In this scenario, the internal ID for segment value 310 isn't known, so the following steps create all of the conditions, except
for the access to all cost centers, which the policy definition can cover.
1. Click Edit Data Security to open the Edit Data Security page.
2. On the Condition tab, click Create to open the Create Database Resource Condition window.
3. Enter CC 110 - 120 in the Name field.
4. Enter Cost Centers 110 to 120 in the Display Name field.
5. Accept the default value of All for the Match field.
Matching to all conditions means that all conditions apply simultaneously. Matching to any condition means that any
of the conditions would apply.
6. Click Add in the Conditions section.
7. Select VALUE for the Column Name field.
8. Select Between for the Operator field.
Note: You can select one of the following operators: Equal to, Not equal to, Between, Is descendant of,
Is last descendant of.
9. Enter 110 in the first Value field and 120 in the second Value field.
154
The following figure shows the definition of the first condition.
10. Click Save.

11. To create the next database resource condition for segment value 310, click Create on the Condition tab.
12. Enter CC 310 in the Name field.
13. Enter Cost Center 310 in the Display Name field.
14. Click Add in the Conditions section.
16. Select Equal to for the Operator field.
17. In the Value field, enter 310.
155
The following figure shows the definition of the second condition.
18. Click Save.

19. To create the next database resource condition for parent value 400, click Create on the Condition tab.
20. Enter CC 400 in the Name field.
21. Enter Parent Cost Center 400 in the Display Name field.
22. In the Condition section, click Add.
24. Select the Tree Operators option.
25. For the Operator field, select Is a last descendant of, which restricts access to the parent cost center 400 and all of
its children, including intermediary parents.
Note: For the Tree Operators field, you can only select Is a last descendant of or Is a descendant of.
26. In the Value column, click the Select Tree Node icon to open the Select Tree Node window.
156
The following figure shows the Select Tree Node window.
27. In the Tree Structure field, select Accounting Flexfield Hierarchy. This signifies that you are choosing among trees
that are used as accounting flexfield, or charts of accounts, hierarchies.
28. In the Tree field, select All Corporate Cost Centers.
29. In the Active Tree Version field, select V5.
30. In the Tree Node field, select the Select from hierarchy button. The Tree Node section opens.
31. In the Tree Node section, expand the nodes and select 400.
157
The following figure shows the Select Tree Node window after completing the fields.
32. Click OK.
158
The following figure shows the definition of the third condition.
33. Click Save.
Defining the Policies

Create policies to assign conditions to segment value security roles.
1. On the Edit Data Security page, click the Policy tab.
2. Click Create to open the Create Policy window.
3. On the General Information tab, enter Policy for 110-120 in the Name field.
4. Accept the default value of General Ledger in the Module field.
5. Enter 9/1/16 in the Start Date field.
The following figure shows the General Information tab on the Create Policy page for the first policy.
6. Select the Role tab and click Add to open the Select and Add window.
7. Enter 110 in the Role Name field.
8. Select hcm in the Application field.
159
Roles with the Default category are created in the hcm application.
9. Click Search.
The following figure shows the Select and Add window after the search.
10. Select Cost Center 110-120 SVS Role and click OK.
The following figure shows the Role tab on the Create Policy page for the first condition.
11. Select the Rule tab.

12. Accept the default setting of Multiple Values in the Row Set field.
Note: The Row Set field determines the range of value set values affected by the policy.
If Multiple Values is selected, a condition must be specified.
If All Values is selected, then the policy grants access to all values in the value set and no condition is
needed.
If Single Value is selected, then the internal Value ID for the segment value must be specified and no
condition is needed.
13. Click Search on the Condition field.

14. Select Cost Centers 110 to 120 for the Condition field and click OK.
160
The following figure shows the Rule tab on the Create Policy page for the first policy.

16. Click OK to confirm.
17. Repeat steps 2 through 13 to create the rest of the policies, using the values in the following table.
Field Policy 2 Policy 3 Policy 4
General Information tab, Name Policy for 310 Policy for 400 Policy for all cost centers

General Information tab, Start 9/1/16 9/1/16 9/1/16

Date

Role tab, Role Name Cost Center 310 SVS Role Cost Center 400 SVS Role Cost Center All SVS Role

Rule tab, Row Set Multiple Values Multiple Values All Values

Rule tab, Condition Cost Center 310 Parent Cost Center 400 Not Applicable

18. Click Done.
Deploying the Accounting Flexfield

You must deploy the accounting flexfield for the segment value security changes to take effect.
1. In the Setup and Maintenance work area, search for and select the Manage Chart of Accounts Structures task.
2. In the Module field, select General Ledger and click Search.
3. Select the row for the Accounting Flexfield and click Deploy Flexfield.
161
The following figure shows the Manage Chart of Accounts Structure page with the Accounting Flexfield row selected.
4. Click OK.
Publishing the Account Hierarchies

1. In the Setup and Maintenance work area, search for and select the Publish Account Hierarchies task.
2. In the Hierarchy field, select All Corporate Cost Centers.
3. In the Hierarchy Version field, select V5.
4. Click Search.
5. In the Search Results section, expand the hierarchy row.
6. Select the row for the hierarchy version V5.
7. Click Publish.
8. Click OK.
Assigning Segment Value Security Roles to Users

1. In the Tools work area, open the Security Console.
2. Enter Cost Center 110-120 SVS Role in the Search field and click Search.
3. In the Search Results section, select the down arrow icon and select Edit Role.
162
The following figure shows the search results for Cost Center 110-120 SVS Role on the Roles page.
4. Click Next four times to navigate to the Edit Role: Users page.
5. Click Add User.
6. Enter Casey in the Search field and click Search.
7. Click Add User to Role to add Casey Brown to the role.
8. Click OK to confirm.
The following figure shows the Edit Role page with the user Casey Brown added to the role.
9. Repeat steps 2 through 8 to add the other roles to different users as needed.
163
Difference in Data Security for GL Features Directly and Indirectly

Based on the Balances Cube
When a user is assigned multiple data access sets for the same balances cube with different security specifications for ledger
or primary balancing segment value access, a difference is manifested in the data security for those GL features based
directly on the cube and those that are not.
General Ledger features based directly on the balances cube are:

Inquire on Detail Balances
Account Monitor
Account Inspector
Financial Reporting
Smart View
Allocations
All other General Ledger features are indirectly based on the balances cube.
When working on features not directly related to the balances cube, you select a specific data access set and you
only work with that one data access set at a time. The defined ledger and primary balancing segment value access
for the selected data access set are enforced
When working directly with the balances cube, the cumulative effects of your combined data access sets for
that cube are enforced. From your combined data access sets of that cube, balances cube security separately
constructs the access filter for the ledger dimension and primary balancing segment values dimension independently
of the other dimensions. This means the specific combination of ledger and primary balancing segment
values access as defined in each distinct data access set are not enforced as such. Instead, you have access
simultaneously to all the ledgers and all the primary balancing segment values granted to you through your combined
data access sets.
Note: Balances cube security grants access to all values of the balancing segment value set for a data access
set defined as either of the following:
Full ledger
All Values: Specific Balancing Segment Values Access Type
With segment value security rules assigned to you through your various roles, the security rules are in effect simultaneously
whether working directly or indirectly with the balances cube.
Segment value security rules are specified for a particular value set. Therefore, as you are working on anything that references
the secured value set, all segment value security rules for that value set that are assigned to you through any of your roles are
in effect at the same time, regardless of the specific role the rule was assigned to or the particular role that you are working
with at the moment. In other words, segment value security rules are cumulative or the union of all the segment value security
rules you have assigned to you through your roles. If you have one role assigned to your user that only grants access to cost
center 200, and another role that grants access to cost centers 300 through 500, then you can access to cost centers 200
and 300 through 500.
When working on features not directly based on the balances cube, such as journal entry pages, the primary balancing
segment values you can access are based on the intersection of:
Primary balancing segment values granted to you through your current selected data access set.
164
All your assigned segment value security rules pertaining to the primary balancing segment value set across all your
assigned roles.
So if a balancing segment value is only granted in either of the selected data access set or a segment value security rule, this
balancing segment value is not available to you.
In contrast, for features directly based on the balances cube, your access is based on the cumulative union of:
Primary balancing segment values granted to you through all your assigned data access sets related to the balances
cube you are working with.
Any segment value security rule grants to that primary balancing segment value set across all your role assignments.
Example
In contrast with the preceding discussion about using separate segment value security roles for segment value security rule
assignments, the following example shows the data access set and segment value security rules assignments both going
to the same role. This setup is used to more easily illustrate the difference in how security works for features directly and
indirectly related to the balances cube.
In this example, you are assigned the DAS1 and DAS2 roles with different data access sets primary balancing segment
values.
The following table lists each role with its corresponding data set and primary balancing segment values.
Role Data Access Set Primary Balancing Segment Value
DAS1 Data Access Set 1 01



The following table shows the same roles and primary balancing segment values that are also assigned to you through a
segment value security rule.
Role Primary Balancing Segment Value
DAS1 01

DAS2 03

DAS3 02

Select Data Access Set 1
1. For features not directly based on balances cube: You can access Primary Balancing Segment 01 which is the
intersection of values from:
Data access set for Role DAS1.
Security rules grants for Roles DAS1 and DAS2.
165
2. For features directly based on balances cube: You can access Primary Balancing Segments 01, 02, and 03 which
are the union of values from data access set and security rules for Roles DAS1 and DAS2
Select Data Access Set 2
1. For features not directly based on a balances cube: You can't access any primary balancing segment value because
there is no intersection of values from:
Data access set for Role DAS2.
Security rules grants for Roles DAS1 and DAS2.

2. For features directly based on balances cube: You can access primary balancing segments 01, 02, and 03, which
are the union of values from data access set and security rules for Roles DAS1 and DAS2.
FAQs for General Ledger Security

When does security take effect on chart of accounts value sets for balances cubes?
For new security policies to be effective, the security policies must be defined before the account hierarchies are published to
the cube. When you create segment value security rules or change an existing rule that is based on a hierarchical filter, you
must republish the tree version. Use the Publish Account Hierarchies page to republish the tree version and for the security to
become effective.
Note: Changes to an account hierarchy previously published to the balances cube require that the hierarchy be
republished to the cube to reflect the updated hierarchy.
What happens when changes are made to an account hierarchy that is 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
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.
166
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.
Cross-Validation Rules
Cross-Validation Rules in General Ledger: Overview

You can use cross-validation rules to determine the valid account combinations that can be dynamically created as users
enter transactions or journal entries. 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.
For example, your organization has determined that the company Operations can't use the cost center Marketing. You can
define a cross-validation rule such that, if the company is Operations, then validate that the cost center isn't Marketing. New
account combinations have to satisfy all of the cross-validation rules enabled for the chart of accounts before they can be
created.
Entry and Maintenance

You can create cross-validation rules using the Create Cross Validation Rules in Spreadsheet task or the Manage Cross-
Validations Rules task. Use the spreadsheet task to quickly enter large volumes of rules during implementation. Use the
Manage Cross-Validation Rules task to add a one-off rule or edit existing rules.
To edit error messages for cross-validation rules, use the Manage Messages for General Ledger task.
Tip: When you export or import cross-validation rules to a new instance using an export or import project in the
Functional Setup Manager, you must add the Manage Messages for General Ledger task before the Manage
Cross-Validation Rules task. You must export or import the messages before exporting or importing the cross-
validation rules.
Existing Account Combinations

If account combinations already exist that violate newly enabled cross-validation rules, those account combinations continue
to be valid. Before disabling existing account combinations that violate your rules and that you no longer use, move the
balances in those accounts to the correct accounts. Then disable the account combinations manually to prevent further
posting. Best practice is to define and enable cross-validation rules before: account combinations are created, transactions or
journal entries are imported or entered, balances are loaded.
167
Cross-Validation Rules: Explained

You can control the creation of new key flexfield code combinations by defining cross-validation rules. A cross-validation
rule defines validation across segments and enforces whether a value of a particular segment can be combined with specific
values of other segments to form a new combination.
The following table compares segment validation to cross-segment validation:
Type of validation Type of control
Segment validation Controls the values you can enter for a particular segment

Cross-segment validation Controls the combinations of values that administrators and end users can create for key flexfields

Note: You can use cross-validation rules for any key flexfield that has cross-validation enabled. See the
documentation for your key flexfield to determine if it supports cross validation.
Cross-validation rules prevent the creation of combinations with values that can't coexist in the same combination.
For example, your company requires that all revenue accounts must have a specific department. Therefore, account
combinations that have revenue account values, such as all values between 4000 and 5999, must have a corresponding
department value other than 000, which indicates no department is specified. You can define cross-validation rules that
disallow creation of combinations with incompatible segments, such as 4100-000 or 5000-000.
Alternatively, suppose your accounting key flexfield has an Organization segment with two possible values, 01 and 02. You
also have a Natural Account segment with many possible values, but company policy requires that Organization 01 uses the
natural account values 001 to 499 and Organization 02 uses the natural account values 500 to 999. You can create cross-
validation rules to ensure that users cannot create a general ledger account with combinations of values such as 02-342 or
01-750.
The following aspects are important to understanding cross-validation rules:

Rule Definitions
Enforcement
Timing
Rule Definitions
The following table contains definitions used in cross-validation rules:
Rule Definition Purpose
Name Uniquely identifies cross-validation rules in a deployment.

Description Helps administrators identify the purpose of the rule.

Error message Explains why the attempted combination violates the rule.

Start Date, End Date Indicates the period of time when the rule is in effect.
168
Rule Definition Purpose

Enabled Determines whether the rule is enforced.

Condition filter Determines the conditions under which an enabled cross-validation rule should be evaluated.

Validation filter Determines the validation that the rule enforces when that condition is met.

When the event specified in the condition filter is applicable, the validation filter condition must be satisfied before the
combination can be created. If the event specified in the condition filter isn't applicable, then the combination is considered to
pass the rule and the rule won't be evaluated even if it is enabled.
Note: If you don't specify any statement in the condition filter, then the condition is always true and the rule is
always evaluated.
Enforcement
Cross-validation prevents creation of invalid combinations by administrators using maintenance pages and end users using
dynamic insertion in foreign key pages.
Enabled rules are enforced when there is an attempt to create a new combination of segment values. Disabled rules are
ignored. Deleting the rule has the same effect, but you can re-enable a disabled rule.
Timing
When users attempt to create a new combination, the key flexfield evaluates any cross-validation rules that are enabled and in
effect.
Note: Cross-validation rules have no effect on combinations that already exist. The flexfield treats any existing
invalid combinations that pre-date the rule as valid.
If you want to prevent users from using previously existing combinations that are no longer valid according to your cross-
validation rules, manually disable those combinations using the combinations page for that key flexfield.
When defining a cross-validation rule, specify a start and end date to limit the time when the rule is in effect. The rule is valid
for the time including the From and To dates.
Cross-Validation Rules: Points to Consider

To validate the key flexfield combinations of segment values across segments, optimize your cross-validation rules to improve
the experience of administrators and users.
Consider the following when defining cross-validation rules:
Filters
Rule Complexity
Maintenance
169
Filters
A cross-validation rule includes a condition filter and a validation filter. The rule is evaluated using the following logical order: If
the condition filter is satisfied, then apply the validation filter.
The condition filter describes the event under which the rule is evaluated. If the event specified in the condition filter isn't
applicable, then the rule isn't evaluated, even if enabled. When the event specified in the condition filter is applicable, the
validation filter condition must be satisfied before the combination can be created.
For example, your organization has determined that a certain company value called Operations can't use a specific cost
center called Marketing. You can define a cross-validation rule to validate your combinations.
1. The rule evaluates the company condition filter.

2. When company is equal to Operations, the rule evaluates the cost center validation filter.
3. When cost center is equal to Marketing, the rule prevents a combination from being created.
4. The error message you defined for the rule displays to inform the user that the attempted combination violates the
rule.
Such a rule doesn't affect the creation of combinations with Marketing cost center and company values other than
Operations.
Rule Complexity
For optimal performance and ease of understanding, define several simple validation rules instead of using one complex rule.
Simple validation rules let you provide a more specific error message and are easier to maintain over time.
Avoid rules that control validation across more than two segments, where possible. While you can define cross-validation
rules that span two or more segments, it becomes difficult to interpret cross-validation error messages and rectify invalid key
flexfield combinations.
Maintenance
To maintain consistent validation, review existing key flexfields when you update your cross-validation rules. Regardless of
your current validation rules, you can use an existing key flexfield combination if it's enabled. Therefore, to ensure accurate
validation, you must review your existing combinations and disable any combinations that don't match the criteria of your new
rules.
Tip: To keep this type of key flexfield maintenance to a minimum, decide upon your cross-validation rules when
you first set up your key flexfield structure. Define cross-validation rules before creating combinations and before
combinations are used in transactions.
To prevent users from using existing combinations that are no longer valid according to your cross-validation rules, disable
them using the combinations page.
Cross-Validation Rules Spreadsheet: Explained

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.
You can download the spreadsheet using the Create Cross Validation Rules in a Spreadsheet task. This task is included in
the following task lists:
Define Common Financials Configuration for Rapid Implementation
170
Define Enterprise Structures Configuration for Rapid Implementation
Note: The spreadsheet can only create cross-validation rules. To update existing cross-validation rules, use the
Manage Cross-Validation Rules task.
Spreadsheet Overview
The cross-validation rules spreadsheet includes two sheets. One sheet provides the template for creating cross-validation
rules and the other sheet has instructions. The Instructions sheet includes:
An overview
An explanation of the template
Steps to fill in the template
An example
The following figure shows the Create Cross Validation Rules sheet.
The following table describes each field and column on the sheet.
Field or Column Description
Worksheet Status The upload results for the worksheet. The application updates this field when you submit the
spreadsheet.

Chart of Accounts The chart of accounts for which the cross-validation rules are defined.

Changed The indicator that the row has been updated. The application updates this field.

Row Status The upload results for the row. The application updates this field when you submit the spreadsheet.

Name The name that uniquely identifies the cross-validation rules in a deployment.

Description The purpose for the cross-validation rule.

171
Field or Column Description
Error Message The explanation to users for why the attempted combination violates the cross-validation rule.

Condition Filter Segment The segments of the chart of accounts that constitute the condition filter.

Condition Filter Values The values of the condition filter segment that determine whether the cross-validation rule is
evaluated.

Validation Filter Segment The segments of the chart of accounts that constitute the validation filter.

Validation Filter Values The values of the validation filter segment used to enforce a new account combination.

Note: Cross-validation rules created from the spreadsheet are automatically enabled and don't have a start or
end date.
Steps to Use the Template

To use the spreadsheet template:
1. Select the chart of accounts.
2. Enter a suitable name, description, and error message in the respective columns.
3. Select the condition filter segment. To add more than one segment to the condition filter, use the next row. Repeat
the rule name and select the condition filter segment.
4. Provide the segment values that constitute the condition filter in the Condition Filter Values column.
Enter detail values separated by commas for multiple detail values, for example: 5501,5502,5503.
Enter detail values separated by a hyphen for a range of values. You can enter multiple ranges using the
comma as the range separator, for example: 3001-3030,3045-3200.
Enter a parent value to select all of the detail values that are descendants of the specified parent. You can
enter multiple parent values using commas as the separator, for example: 1000,2000.
You could enter all of the previously listed values in the same cell, for example:
1000,2000,3001-3030,3045-3200,5501,5502,5503.
5. Select the validation filter segment. To add more than one segment to the validation filter, use the next row. Repeat
the rule name and select the validation filter segment.
6. Provide the segment values that constitute the validation filter in the Validation Filter Values column in the same
way as specified for the condition filter.
7. Review the data that you entered and click Submit to publish the cross-validation rules.
8. Review the upload results in the Worksheet Status and Row Status fields.
Creating Cross-Validation Rules in a Spreadsheet: Worked Example

This example shows how to create two cross-validation rules using the Cross-Validation Rules spreadsheet.
The following table summarizes key decisions for this scenario.
What's the name of the chart of accounts? US Chart of Accounts
172

What segments make up the chart of accounts? Company

Department
Account
Product
What cross-validation rules have to be created? Companies 131 and 151 have only one department,
department 40. Department 40 produces only one product,
represented by segment value 211. All account combinations
for these two companies must have department 40 and
product 211.
Company 202 has three manufacturing departments: 10,20,30.
All three departments work only with products 235 and 236. All
account combinations for company 202 must have only these
three departments and these two products.
Creating Cross-Validation Rules

1. Navigate to the Setup and Maintenance work area and search for the Create Cross Validation Rules in Spreadsheet
task.
2. Click the Create Cross Validation Rules in Spreadsheet link to open the spreadsheet.
3. Complete the fields, as shown in this table, to create the rule for companies 131 and 151.
Row 1 Values
Name Companies 131 and 151

Description Valid department and product for companies 131 and 151.

Error Message Companies 131 and 151 can only be used with department 40 and product 211.

Condition Filter Segment Company

Condition Filter Values 131,151

Validation Filter Segment Department

Validation Filter Values 40

4. Complete the fields, as shown in this table, to complete the rule for companies 131 and 151.
Row 2 Values
Name Companies 131 and 151

Validation Filter Segment Product

Validation Filter Values 211

173
5. Complete the fields, as shown in this table, to create the rule for company 202.
Row 3 Values
Name Company 202

Description Valid products for company 202 manufacturing departments.

Error Message Manufacturing departments 10, 20, and 30, of company 202, can only be used with products 235
or 236.

Condition Filter Segment Company

Condition Filter Values 202

Validation Filter Segment Product

Validation Filter Values 235,236

6. Complete the fields, as shown in this table, to complete the rule for company 202.
Row 4 Values
Name Company 202

Condition Filter Segment Department

Condition Filter Values 10-30

174
This figure shows the spreadsheet with the rules.
7. Click Submit to upload the cross-validation rules.

8. Click OK on the Upload Options window to accept the default setting.
9. Review the upload results.
Editing a Cross-Validation Rule: Example

Cross-validation rules prevent specific combinations of segment values in account combinations. You can use the Manage
Cross-Validation Rules task to edit existing rules or to create one-off rules.
Scenario
Your organization has a cross-validation rule called Companies 131 and 151, which restricts account combinations for those
companies to department 40 and product 211. Account combinations for both companies should now include department
30. To edit the cross-validation rule, perform these steps.
1. Navigate to the Setup and Maintenance work area. Search for and select the Manage Cross-Validation Rules task.
175
2. Select the chart of accounts for your organization and select the Companies 131 and 151 cross-validation rule. The
following figure shows the condition and validation filters for that rule.
3. Click the Validation Filter icon.

4. Click Add Fields and select the Department segment.
5. Accept the default operator, which is Equals, and select department 30. The following figure shows the updated
validation filter.
6. Click OK.
7. Click Save. The following figure shows the saved validation filter.
176
8. To update the error message, search for and select the Manage Messages for General Ledger task. Query the error
message name for the cross-validation rule and edit the message to include department 30.
FAQs for Chart of Accounts Mappings
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 the chart of

accounts mapping?
Segment rules and account rules can be exclusively used in a chart of accounts mapping. You can use a combination of
both. If there is an overlap 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.
Account Hierarchies
Trees: Overview
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.
In the Setup and Maintenance work area, search for and use the Manage Trees and Tree Versions task to organize data into
hierarchies.
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.
177
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.
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.
In the Setup and Maintenance work area, search for and use the following tasks to work with trees:
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.
Account Hierarchy Trees: Explained

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.
Using Account Hierarchies: Explained

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.
Financial Reporting and Allocations: You can use the same hierarchy for both reporting and allocations purposes, or you
can have different hierarchies for reporting and for allocations purposes. Hierarchies that are used in financial reporting and
allocations must be published to Oracle Essbase. You can select which hierarchies you publish to Essbase. Any hierarchy
that is published to Essbase cannot have a single child value roll up to multiple parents. If you have requirements to have a
single child roll up to multiple parents, it has to be defined using multiple hierarchies.
178
Cross Validation Rules, Revaluations, and Chart of Accounts Mappings: You need one hierarchy for each segment that
is used for cross validation rules, revaluation, and chart of accounts mapping. Hierarchies used for cross validations,
revaluations, or chart of accounts mapping have to be defined within the same hierarchy. The hierarchy must then be
associated with a chart of accounts instance. You can only associate one hierarchy with a chart of accounts instance, per
segment.
You can optionally publish this hierarchy to Essbase to use the same hierarchy for reporting and allocations. Note the
restriction that any hierarchy that is published to Essbase cannot have a single child value roll up to multiple parents. If you
require the same child to roll up to different parents within the hierarchy, then create a different hierarchy for reporting and
allocation rules.
If you use the same hierarchical account relationships for financial reporting, allocations, cross validation rules, revaluations,
and chart of accounts mapping definition, define one hierarchy. However, if you need multiple hierarchies, define the
hierarchies using multiple trees.
Importing Segment Values and Hierarchies: Explained

Use the Import Segment Values and Hierarchies process to load segment values and hierarchies if you maintain chart of
accounts reference data outside Oracle Fusion applications. You can load the segment values and hierarchies by populating
two tables: GL_SEGMENT_VALUES_INTERFACE and GL_SEGMENT_HIER_INTERFACE, and by running the Import
Segment Values and Hierarchies process.
Note: You can load data to interface tables using predefined templates and the Load Interface File for Import
scheduled process, which are both part of the External Data Integration Services for Oracle Cloud. For more
information about file-based data import, see the File Based Data Import guide for your cloud services.
You can use the GL_SEGMENT_VALUES_INTERFACE table to load segment values and the
GL_SEGMENT_HIER_INTERFACE table to load segment value hierarchies to Oracle Fusion applications. For more
information about tables, see the Tables and Views for Oracle Financials Cloud guide.
Assigning Values for Columns in the GL_SEGMENT_VALUES_INTERFACE table

You must enter values in all columns of the interface table that require values for the Import Segment Values and Hierarchies
process to be successful.
The following table describes the columns that require values.
Name Value
STATUS_CODE
Enter the value NEW to indicate that you are bringing new segment value data.
VALUE_SET_CODE Enter the value set code for the segment values.

VALUE Enter the segment value.

SUMMARY_FLAG
Select N if the segment value is a child value or Y if the segment value is a parent value.
ENABLED_FLAG:
Select Y to enable the segment value. Enter N to disable the segment value.
179
Name Value
ACCOUNT_TYPE:
Enter the natural account type if the segment value is for a natural account segment.
A: Asset
L: Liability
E: Expense
O: Owner's Equity
R: Revenue
ALLOW_ POSTING_FLAG
Select Y if posting is allowed for this segment value. Select N if posting is not allowed.
OBJECT_ VERSION_ NUMBER

Enter default value of 1.
The following table describes the columns that are optional.
Name Value
START_ DATE_ACTIVE Enter the start date of the segment value.

END_ DATE_ACTIVE Enter the end date of the segment value.

THIRD_ PARTY_ CTRL_ACCOUNT

Enter the third-party control account value. Valid values are: CUSTOMER, SUPPLIER, R for restrict
manual journals, Y, and N.
FINANCIAL_ CATEGORY Enter a financial category value for Oracle Transactional Business Intelligence reporting. Valid values
are values defined for the FINANCIAL_ CATEGORY lookup type.

DESCRIPTION Different description columns exist for different languages. To see segment value description in a
different language installation, you populate the segment description for that language too.

The following columns should remain blank. The Import Segment Values and Hierarchies process uses them for internal
processing, or doesn't currently use them.
CREATION_DATE
CREATED_BY
LAST_UPDATE_DATE
LAST_UPDATE_LOGIN
LAST_UPDATED_BY
SEGMENT_VALUE_INTERFACE_ID
REQUEST_ID
LOAD_REQUEST_ID
Assigning Values for Columns in the GL_SEGMENT_HEIR_INTERFACE table

You must enter values in all columns of the interface table that require values for the Import Segment Values and Hierarchies
process to be successful.
180
Name Value
STATUS_CODE
Enter the value NEW to indicate that you are loading new hierarchy data.
VALUE_SET_CODE Enter the value set code for the segment values.

TREE_CODE Enter the hierarchy name (tree code).

TREE_VERSION NAME Enter the hierarchy version name (tree version name).

TREE_ VERSION_ START_ Enter the date that the tree version is activated.
DATE_ACTIVE

TREE_ VERSION_ END_ DATE_ACTIVE Enter the date that the tree version is inactivated.

VALUE Enter the segment value.

PARENT_VALUE
Select N if the segment value is a child value or Y if the segment value is a parent value.
DEPTH Enter the depth of the hierarchy that shows the many ancestors the segment value has in the
hierarchy.

OBJECT_ VERSION_ NUMBER

Enter default value of 1.
The following columns should remain blank. The Import Segment Values and Hierarchies process uses them for internal
processing or doesn't currently use them.
CREATION_DATE
CREATED_BY
LAST_UPDATE_DATE
LAST_UPDATE_LOGIN
LAST_UPDATED_BY
SEGMENT_VALUE_INTERFACE_ID
REQUEST_ID
LOAD_REQUEST_ID
Related Topics
External Data Integration Services for Oracle Cloud: Overview
Tables and Views for Oracle Financials Cloud
File-Based Data Import for Oracle Financials Cloud
181
Loading Data to the Segment Value and Hierarchies Interface Tables:

Explained
Load the segment values and hierarchies to the interface table by using the following steps.
1. Load segment values and hierarchies to comma separated values (.csv) files. The file-based data import for Segment
Values and Hierarchies Import has a template that you can use. For more information about file-based data import,
see the File-Based Data Import for Oracle Financials Cloud guide.
2. Follow the instructions in the template to upload the .csv file.
3. Run the Load Interface File for Import process.
4. After the data is loaded to the interface table, run the Import Segment Values and Hierarchies process to load the
segment values and hierarchies.
Related Topics
Publishing an Account Hierarchy: Example

Publish an account hierarchy to finalize a new or edited account hierarchy. Account hierarchies organize data and enable
the creation of groups and rollups of information that exist within an organization. After creating or editing an accounting
hierarchy, run the Publish Account Hierarchies, Maintain GL Value Sets, and Maintain Chart of Account Hierarchies processes
before using the new or changed account hierarchy.
Scenario
You have made changes to your InFusion America account hierarchy. Follow these steps to publish your account hierarchy.
1. Navigator > Setup and Maintenance.
2. Enter the Publish Account Hierarchies into the Name field. Click Search.
3. Click the Go to Task to open the Publish Account Hierarchies page.
4. Search for your InFusion America account hierarchy.
5. Expand to open the versions of your hierarchy.
6. Click the Publish button on the tool bar.
Note: For a new hierarchy, scroll over to verify the Publish check box is checked.
Hierarchies for Cross Validations, Revaluations, and Chart of

Accounts Mapping: Explained
Hierarchies you create for reporting or allocations may not be suitable for setting up cross validations, revaluation, and chart
of accounts mapping rules.
For example, if you must enforce a cross validation rule that a set of 20 departments is applicable only to a certain company,
then you can group the 20 departments under a hierarchy node and refer to that hierarchy node in the cross validation rule.
182
Cross Validations, Revaluations, and Chart of Accounts Mapping

For hierarchies for cross validations, revaluations, and chart of accounts mapping:
Create hierarchies for cross validations, revaluation, or chart of accounts mapping within one hierarchy. Associate
this hierarchy to the chart of accounts segment instance in the chart of accounts instance setup page. You can only
associate one hierarchy with the chart of accounts instance. You can create separate root nodes for each segment
of the hierarchy.
Create an account hierarchy for each of the segments that are used in the rule set ups. Depending on your
requirements, not all segments may need a hierarchy.
Use the same child to roll up to different parents if you need different roll ups for cross validations, revaluations, and
chart of accounts mapping.
Flatten and audit the hierarchy after the hierarchies are complete and set it to an active status.
Associate the hierarchy to the chart of accounts segment instance.
Redeploy the accounting flexfield after the chart of accounts instance is updated.
If you have the duplicate segment values in a hierarchy, you should not publish the hierarchies to Oracle Essbase.
Naming Financial Reporting and Allocations Hierarchies: Points to

Consider
You must publish hierarchies for financial reporting and allocations to Oracle Essbase cubes. When a hierarchy is published to
an Essbase cube, a fully qualified member name is generated for each node in the hierarchy. This fully qualified member name
is used to refer to the node in the hierarchy in financial reports and allocation rules.
Each combination of tree plus tree version is published as a different account hierarchy to Essbase cubes.
When a chart of accounts child or parent value is assigned to multiple hierarchy versions, the fully qualified member name
includes the hierarchy version name.
Member Names and Financial Reporting and Allocations Hierarchies

You must consider the implications to your financial reports, allocation rules, and Smart View templates if the member name
changes due to hierarchy changes. The points to considered are:
The member name for a member can change if you originally published a single hierarchy to a cube and later
published another hierarchy. The change happens if the member includes the same chart of accounts value.
If the fully qualified member name changes, you must update existing financial reports, allocation rules, and Smart
View templates that refer to that member. Otherwise, such processes have errors.
For example, only a single hierarchy version, V1, existed when you defined a financial report. The hierarchy version includes
the chart of accounts value of 500 for a cost center. The path does not include a hierarchy version name, since there is only
one hierarchy version in the cube. The fully qualified name path is 500.
Later, you publish a new hierarchy version, V2. The fully qualified member name changes since there are now two versions
and cost center 500 is associated with two hierarchy versions, V1 and V2. When selecting the value 500, the cube has logic
to uniquely identify the member. The fully qualified member name for the two hierarchy versions is now:
[All VF Cost Centers-V1].[999].[500]
[All VF Cost Centers-V2].[999].[500]
183
Note: The fully qualified member can also be shortened by the cube logic, such as [Cost_Center]@[Cost Center
Level 29 Code]|[500].
Update configurations, such as financial reports, allocation rules, or Smart View queries that referenced the original name
path of 500 with the correct name.
Related Topics
Initial Publishing of Account Hierarchies: Points to Consider
Maintain Account Hierarchies: Overview

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.
Maintenance of Hierarchies: Explained

As your organization changes or there are updates to your chart of accounts values, you can make updates to your hierarchy
versions. Changes must be in the two hierarchy versions to minimize errors related to member name paths in financial
reports, allocation rules, or Smart View queries. Both hierarchy versions must be published to the balances cube.
To keep an audit history, copy the hierarchy version and use the copy as the version for audit history. After you copy the
hierarchy version, modify that same version to use as the latest version. You do not have to change reports.
Hierarchy Versions Configuration

Perform the following steps before updating the current hierarchy version:
1. Copy the current hierarchy version to create cost center 2011 to keep an audit history for year 2011.
2. Update the effective date for the Current hierarchy version to the current period. Set the effective dates for the
copied hierarchy version to what the past dates were.
3. Make all of your current hierarchy changes to the Current hierarchy version.
4. Set the status to Active again.
5. Delete the Baseline hierarchy version in the Manage Account Hierarchies page. You do not unpublish the
hierarchy from the cube, as long as you follow the naming conventions discussed in the following steps.
6. Copy the Current hierarchy version and name it Baseline. You must name it the same exact name because
Baseline still exists in the cube. The procedures overwrite the hierarchy version named Baseline in the cube.
7. Use effective dates that do not overlap and that are before periods used by previously active hierarchy versions.
8. Set the status for the Baseline hierarchy version to Active.
9. Publish both hierarchy versions, Current and Baseline, to their respective cube.
10. Publish the cost center 2011 to the cube if the version is still needed for financial reporting, Smart View queries, or
allocation rules.
11. Review the published results using Smart View.
You have the following three versions:
1. The new copied version: This version is used to track the history of the old master version, for example, cost center
2011 and have been end dated.
2. Current version: This version has been modified to reflect the new hierarchy and is now active.
184
3. Baseline version: This version should continue to be the duplicate of the master version. Rather than modifying this
manually, delete the old baseline version and create another copy of the master. Modify the master version. These
steps should be followed each time when there are hierarchy changes that must be published.
Note: Best practices recommend that if there are changes, you update the hierarchies before completing
period close and financial reporting.
Maintaining Hierarchies: Examples

You can update the hierarchy for any changes that must be reflected in 2012. The following example illustrates how to
maintain your hierarchy.
Your organization, Vision Operations:

Decided in 2010 to begin using Oracle Fusion General Ledger, effective January 1, 2011.
Uses a single chart of accounts named Corporate Chart of Accounts. Since you only have one chart of accounts,
this is also the name of your cube.
Uses hierarchy to capture its cost center roll ups by line of business. The name of this hierarchy is named Cost
Centers Hierarchy.
The following graphic displays the relationships between the hierarchy versions and the cube:
185
Maintaining and Updating Your Hierarchy

At the end of 2011, your organization, Vision Operations, makes organizational changes to its lines of business. You add new
cost centers and a new line of business. As a result, you must update your cost center hierarchies to ensure that financial
reporting reflects the new organization hierarchy.
Do not make changes to the Cost Center Master hierarchy version if no account value changes have been made and the
current hierarchies are working.
However, since there are changes you must:
1. Copy and backup the Cost Center Current hierarchy version to maintain history.
2. Make changes to the Cost Center Current hierarchy version and change it to the new effective dates.
3. Delete the hierarchy version named Baseline. You do not unpublish the hierarchy from the cube, as long as you
follow the naming conventions discussed in the following steps.
4. Copy the Current hierarchy version after changes are completed and name it Baseline.
5. Publish the Current hierarchy version again.
6. Publish the new Baseline hierarchy version again.
After publishing both versions, there are still only two hierarchy versions in the cubes. The version name must always be the
same across all periods. The name is reference in the financial reports. allocation rules, and Smart View queries. For example,
Cost Center Current and Cost Center Baseline. Do not have a version named 2011 Cost Center, or 2012 Cost Center
Current, or 2012 Cost Center Baseline.
This example assumes an annual change. It can also be quarterly, monthly, or as needed. Follow these steps for any
hierarchy changes at any time for even regular maintenance, such as adding values or moving values in the hierarchy. Best
practices recommend keeping your current and baseline hierarchy versions in sync.
186
The following graphic displays steps to update your hierarchy versions:
FAQs for 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 perform row and column flattening for tree versions

manually?
Row Flattening and Column Flattening for tree versions need to be manually submitted under the following scenarios.
When a new tree or tree version is defined.
187
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.
Tree Structures
Tree Structures: Explained
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.
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 is 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.
Tree Structure Definition: Points to Consider

While creating a tree structure, you must specify important details on the Create Tree Structure: Specify Definition page. As
the source of the tree structure, you may either select the predefined tree structures and proceed with the definition or create
custom tree structures.
Tree Node Selection

The data in Tree Node table maps to the data in nodes of the tree structure. You must select the correct and most
appropriate tree node table to define the tree structure, based on which you establish the tree hierarchy. This selection also
affects the level of security that is set on a tree node and its child entities.
Tree Sharing Mode

Use the following options to determine the mode of sharing a tree structure across the applications.
Open: Indicates that the tree is associated with all reference data sets.
Set ID: Indicates that the tree is associated with a specific reference data set.
188
Customization
You can customize the predefined tree structures as well as those you create. However, customizing a predefined tree
structure is restricted and permitted through additional privileges. Customization is limited to specific tree nodes and lower in
the tree hierarchy.
Multiple Tree Versions

Although multiple tree versions can exist together, Oracle recommends only one version be active at any given time.
However, if required, you can have more tree versions to be in the active state for the same date range. You can use this
flexibility to select the tree version you want to implement.
Managing Tree Structures: Points to Consider

You can create, edit, and delete tree structures. You can also change the status of a tree structure and audit the changes.
Creating and Editing Tree Structures

When you edit an active tree structure, the status of the tree structure and all associated trees and their versions changes
to draft. To reuse a tree structure, create a copy of the tree without copying the associated trees and tree versions. After
making changes, set the status again to active. If you delete a tree structure, all the associated trees and tree versions are
automatically deleted.
For information about working with the offering-specific predefined tree structures, refer to the relevant product
documentation.
Status
When you change the status of a tree structure, the status of the trees and tree versions associated with that tree structure
also changes.
The following table lists the different statuses of a tree structure.
Status Meaning
Draft In a modified state, or not yet in use.

Active In use, indicating that one or more trees or tree versions are created from the tree structure.

Inactive Not in use.

Tree Structure Audit Results: Explained

Use the tree structure audit results to verify the tree structure's correctness and data integrity. The audit results include the
following details:
The name of the validator, which is a specific validation check
The result of the validation, including a detailed message
Corrective actions to take if there are any validation errors
Running an Audit
Setting the status of a tree structure to active automatically triggers an audit of that tree structure. To manually trigger an
audit, select Audit from the Actions menu on the Manage Tree Structures page. The Tree Structure Audit Result table shows
a list of validations that ran against the selected tree structure.
189
Audit Validators
The following table lists the validators used in the audit process and describes what each validator checks for. It also lists
possible causes for validation errors and suggests corrective actions.
Validator Page Description (what is Possible Cause for Suggested Corrective

validated) Validation Failure Action
Restrict By Set ID Manage Tree Structures: Even when the check If reference data set
Specify Data Sources If you select the box is selected, one or restriction is required
Reference Data Set more data source view for this tree structure,
check box for the objects doesn't contain include a reference data
Restrict Tree Node List a reference data set set attribute on all data
of Values Based on attribute. sources. Otherwise,
option, each of its data deselect the check box.
source view objects must
have a reference data set
attribute.
Available Label Data Manage Tree Structures: Any of the Correct the
Sources Specify Data Sources If you select a list item specified label specified label
from Labeling Scheme data source view data source view
to specify a labeling objects doesn't object.
scheme, the label data exist. Correct the
source view object
Any of the primary keys of
specified for each
specified label the specified label
data source must be
data source view data source view
accessible. Also, the
objects doesn't object.
primary keys must be
have primary keys. Do one of the
valid. This restriction
doesn't apply if you When a label following:
select None from the list. data source view
object is initially Correct
the primary
defined, the keys in the
database registers label data
the primary keys source
for the view view object
object. If the view to match
object is later the primary
modified such keys that
that its primary were earlier
keys no longer registered
match the primary in
keys that were FND_TS_DATA_SOURCE.
registered earlier,
this validation fails. Correct
the primary
keys
registered
in that table
to match
the new
view object
definition.
Row Flattened Table Manage Tree Structures: You must specify a valid The specified Correct the row flattened
Name Specify Performance row flattened table for table doesn't exist table definition.
Options the tree structure. It can in the database.
either be the standard The specified
row flattened table FND_ table doesn't
TREE_NODE_RF or a contain the same
custom table. columns as the

190

FND_TREE_NODE_RF
table.
Available Data Sources Add Data Source Each data source view Any of the Correct the
object specified for the specified data specified data
tree structure must be source view source view
accessible, and all its objects doesn't object.
primary key attributes exist. Correct the
must be valid. When you define a duplicate column
data source view in the registered
object, keep the primary keys.
Use non-defined Correct the
primary key primary keys
columns check of the specified
box deselected. data source view
The database object.
automatically Correct any
registers the mismatch in data
primary keys for types.
the view object.
Select this check
box if you want
the database
to register the
primary keys
you specify.
However, if the
registered primary
keys contain any
duplicates, this
validation fails.
The Use non-
defined primary
key columns
check box is
selected in a data
source, but the
list of specified
primary key
columns doesn't
match the primary
keys defined in
the corresponding
data source view
object.
Any common
attribute that
exists in both the
data source view
object and the
tree node view
object isn't of the
same data type in
both view objects.
Column Flattened Table Manage Tree Structures: You must specify a valid The specified Correct the column
Name Specify Performance column flattened table for table doesn't exist flattened table definition.
Options the tree structure. It can in the database.
either be the standard The specified
row flattened table FND_ table doesn't
TREE_NODE_CF or a contain the same
custom table. columns as the
191

FND_TREE_NODE_CF
table.
Restrict by Date Manage Tree Structures: Even when the check If the date restriction
Specify Data Sources If you select the Date box is selected, one or is required for this tree
Range check box for more of its data source structure, include the
the Restrict Tree Node view objects doesn't effective start date
List of Values Based contain effective start and effective end date
on option for a tree date and end date attributes on all data
structure, each of its data attributes. sources. Otherwise,
source view objects must deselect the check box.
have effective start date
and end date attributes.
This validation doesn't
take place when the
check box isn't selected.
Tree Node Table Name Manage Tree Structures: You must specify a valid No table is Correct the tree node
Specify Definition tree node table for the specified in the table definition.
tree structure. It can Tree Node Table
either be the standard field.
row flattened table The specified
FND_TREE_NODE or a table doesn't exist
custom table. in the database.
The specified
table doesn't
contain the same
columns as the
FND_TREE_NODE
table.
Specifying Data Sources for Tree Structures: Points to Consider

The data sources provide the items for establishing hierarchy in a tree structure. In the tree management infrastructure, these
data sources are Oracle ADF business components view objects, which are defined by application development.
Labeling Schemes
Selecting a labeling scheme determines how the tree nodes are labeled. You may select a labeling scheme to assign at the
data source level, at the parent node level, or keep it open for customers assignment. You may also choose not to have any
labeling scheme. However, if you decide to use any of the labeling schemes, select the following additional options, to restrict
the list of values that appear under the selected tree node.
Allow Ragged Nodes: To include nodes that have no child nodes, and are shorter than the remaining nodes in the
entire hierarchy.
Allow Skip Level Nodes: To include nodes that are at the same level but have parent nodes at different levels.
Restriction of Tree Node Values

You can decide the depth of the tree structure by selecting an appropriate value from the list. Keeping the depth limit open
renders an infinite list of values.
Using the following options, you can restrict the list of values that appear for selection under a specific tree node.
Date Range: Specifies whether a selection of nodes should be restricted to the same date range as the tree
version.
Allow Multiple Root Nodes: Allows you to add multiple root nodes when creating a tree version.
192
Reference Data Set: Specifies whether a selection of nodes should be restricted to the same set as the tree.
Data Source Values and Parameters

Tree data sources have optional data source parameters with defined view criteria and associated bind variables. You can
specify view criteria as a data source parameter when creating a tree structure, and edit the parameters when creating a tree.
Multiple data sources can be associated with a tree structure and can have well-defined relationships among them.
Note: Parameter values customized at the tree level override the default values specified at the tree-structure
level.
The data source parameters are applied to any tree version belonging to that data source, when performing node operations
on the tree nodes. Data source parameters also provide an additional level of filtering for different tree structures. The tree
structure definition supports three data source parameter types.
Bound Value: Captures any fixed value, which is used as part of the view criteria condition.
Variable: Captures and binds a dynamic value that is being used by the data source view object. This value is used
by the WHERE condition of the data flow.
View Criteria: Captures the view criteria name, which is applied to the data source view object.
You can also specify which of the data source parameters are mandatory while creating or editing the tree structure.
View objects from the Oracle ADF business components are used as data sources. To associate the view object with the tree
structure, you can pick the code from Oracle ADF business component view objects and provide the fully qualified name of
the view object, for example, oracle.apps.fnd.applcore.trees.model.view.FndLabelVO.
Specifying Performance Options for a Tree Structure: Points to Consider

Tree structures are heavily loaded with data. As a tree management guideline, use the following settings to improve
performance of data rendering and retrieval.
Row Flattening
Column Flattening
Column Flattened Entity Objects
BI View Objects
Row Flattening
Row flattening optimizes parent-child information for run-time performance by storing additional rows in a table for instantly
finding all descendants of a parent without initiating a CONNECT BY query. Row flattening eliminates recursive queries, which
allows operations to perform across an entire subtree more efficiently.
To store row flattened data for the specific tree structure, users can either use the central FND_TREE_NODE_RF table or they can
register their own row flattened table. For example, in a table, if Corporation is the parent of Sales Division (Corporation-Sales
Division), and Sales Division is the parent of Region (Sales Division-Region), a row-flattened table contains an additional row
with Corporation directly being the parent of Region (Corporation-Region).
Column Flattening
Column flattening optimizes parent-child information for runtime performance by storing an additional column in a table for all
parents of a child.
To store column flattened data for the specific tree structure, users can either use the central FND_TREE_NODE_CF table or
they can register their own column flattened table. For example, in a table, if Corporation is the parent of Sales Division
(Corporation-Sales Division), and Sales Division is the parent of Region (Sales Division-Region), a flattened table in addition
193
to these columns, contains three new columns: Region, Sales Division, and Corporation. Although positioned next to each
other, the column Region functions at the lower level and Corporation at the higher level, retaining the data hierarchy.
Column Flattened Entity Object

In the absence of a column-flattened table, if you need to generate the business component view objects for your tree
structure for the flattened table, use the tree management infrastructure to correctly provide the fully qualified name of the
entity object for the column flattened table.
BI View Object
View objects from Business Intelligence can be used as data sources, eliminating the need to create new types of data
sources. This field is to store the fully qualified name for the BI view object generated by the tree management for business
intelligence reporting and usage The BI view object is a combination of the tree data source and column flattened entity.
Using this option prevents data redundancy and promotes greater reuse of existing data, thereby improving the performance
of the tree structure.
Search View Object

Specify the full name of the view object for the tree node to ensure that search operations performed on the tree node are
efficient.
Manage Tree Labels

Tree Labels: Explained
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.

194
Manage Trees and Tree Versions

Managing Trees and Tree Versions: Points to Consider
You can create and edit trees and tree versions depending upon the requirement. A tree can have one or more tree versions.
When changes are made to an existing tree, a new version is created and published.
Creating and Editing Trees

Trees are created based on the structure defined in the tree structure. You can create trees, modify existing trees, and delete
trees. If you want to copy an existing tree, you can duplicate it. You can also select and copy the associated tree versions.
Creating a tree involves specifying the tree definition and specifying the labels that are used on its nodes. If the selected tree
structure has data sources and parameters defined for it, they appear on the page allowing you to edit the parameter values
at the tree node level.
Note: Parameter values customized at the tree level will override the default values specified at the tree-
structure level.
Creating and Editing Tree Versions

Tree versions are created at the time of creating trees. Each tree must contain a version.
Editing an existing tree provides you with the option of updating the existing version. You can also edit the existing version
that lies nested under the tree in the search results.
When you edit a tree version bearing Active status, the status changes to Draft until the modifications are saved or canceled.
Tree Version Audit Results: Explained

Use the tree version audit results to verify the tree version's correctness and data integrity. The audit results include the
following details:
The name of the validator, which is a specific validation check
The result of the validation, including a detailed message
Corrective actions to take if there are any validation errors
Running an Audit
An audit automatically runs whenever a tree version is set to active. You can also manually trigger an audit on the Manage
Trees and Tree Versions page, using Actions > Audit. The Tree Version Audit Result table shows a list of validations that ran
against the selected tree version.
Validation Details
The following table lists the validators used in the audit process and describes what each validator checks for. It also lists
possible causes for validation errors and suggests corrective actions.
Validator Description (what is checked) Possible Cause for Validation Suggested Corrective Action
Failure
Effective Date The effective start and end dates The effective end date is set to a Modify the effective start and
of the tree version must be valid. value that is not greater than the end dates such that the effective
effective start date.
195
Failure
start date is earlier than the
effective end date.

Root Node Even if the check box is Modify the tree version such that
On the Manage Tree Structures: deselected, the tree version has there is exactly one root node.
Specify Data Sources page, if multiple root nodes.
the Allow Multiple Root Nodes
check box for the Restrict Tree
Node List of Values Based on
option is not selected, and if the
tree structure is not empty, the
tree version must contain exactly
one root node. This validation
does not take place if the check
box is selected.
Data Source Maximum Depth The tree version has data at a Modify the tree version such
For each data source in the tree depth greater than the specified that all nodes are at a depth that
structure, on the Data Source depth limit on one or more data complies with the data source
dialog box, if the data source sources. depth limit.
is depth-limited, the data in the
tree version must adhere to
the specified depth limit. This
validation doesn't apply to data
sources for which the Maximum
Depth field is set to Unlimited.
Duplicate Node Even when the check box is Remove any duplicate nodes
On the Data Source dialog deselected, the tree version from the tree version.
box, if the Allow Duplicates contains duplicate nodes.
check box isn't selected, the
tree version must not contain
more than one node with the
same primary key from the
data source. If the check box is
selected, duplicate nodes are
permitted.
Available Node All nodes in the tree version A node in the tree version Remove any orphaned nodes
must be valid and available in the doesn't exist in the data from the tree version. Update
underlying data source. source. Deleting data tree reference nodes so that they
items from the data reference existing tree versions.
source without removing
the corresponding nodes
from the tree version can
result in orphaned nodes
in the tree version. For
example, if you added
node A into your tree
version, and subsequently
deleted node A from
the data source without
removing it from the tree
version, the validation
fails.
The tree version contains
a tree reference node,
which references another
tree version that does not
exist.
196
Failure
Node Relationship All nodes must adhere to the The tree structure has data Modify the tree version such that
relationships mandated by the sources arranged in a parent- the nodes adhere to the same
data sources registered in the child relationship, but the nodes parent-child relationships as the
tree structure. in the tree don't adhere to the data sources.
same parent-child relationship.
For example, if the tree structure
has a Project data source with
a Task data source as its child,
Task nodes must always be
under Project nodes in the tree
version. This validation fails if
there are instances where a
Project node is added as the
child of a Task node.

SetID Restricted Node Even when the check box is Modify the tree version such that
On the Manage Tree Structures: selected, the tree version has all nodes in the tree have data
Specify Data sources page, if nodes whose data source values sources with reference data set
the Set ID check box is selected belong to a different reference matching that of the tree.
to enable the Restrict Tree data set than the tree.
Node List of Values Based
on option for each tree node,
the underlying node in the data
source must belong to the same
reference data set as the tree
itself. This restriction doesn't
apply when the check box is not
selected.
Label Enabled Node The tree structure has a labeling Assign a label to any node that
On the Manage Tree Structures: scheme but the tree version has doesn't have a label.
Specify Data Sources page, if a nodes without labels.
labeling scheme is specified for
the tree structure by selecting
a list item from the Labeling
Scheme list box, all nodes must
have labels. This restriction
doesn't apply when you select
None from the Labeling
Scheme list box.
Date Restricted Node Even when the check box Ensure that all nodes in the tree
On the Manage Tree Structures: is selected, there are data version have effective date range
Specify Data Sources page, if source nodes that have a for the effective date range for
the Date Range check box is date range beyond the tree the tree version.
selected to enable the Restrict version's effective date range.
Tree Node List of Values For example, if the tree version
Based on option for a tree is effective from Jan-01-2012
structure, each node in the to Dec-31-2012, all nodes
underlying data source must in the tree version must be
have an effective date range effective from Jan-01-2012 to
same as the effective date Dec-31-2012 at a minimum. It
range of the tree version. This is acceptable for the nodes to
restriction doesn't apply if the be effective for a date range that
check box isn't selected. extends partly beyond the tree
version's effective date range
(for example, the node data
source value is effective from
Dec-01-2011 to Mar-31-2013).
It isn't acceptable if the nodes
are effective for none or only a
part of the tree version's effective
197
Failure
date range (for example, the
node data source value are
effective only from Jan-01-2012
to June-30-2012).

Multiple Active Tree Version Even when the check box isn't Set no more than one tree
On the Manage Tree Structures: selected, there is more than one version to Active within the same
Specify Definition page, if the active tree version in the tree for date range and set the others to
Allow Multiple Active Tree the same date range. inactive or draft status.
Versions check box isn't
selected for the tree structure,
there must not be more than
one active tree version under a
tree at any time. This restriction
doesn't apply if the check box is
selected.
Range Based Node Even when the check box isn't Ensure that any range nodes
On the Data Source dialog box, selected, there are range-based in your tree version are from a
if the Allow Range Children nodes from a data source. data source that allows range
check box isn't selected, range- children.
based nodes are not permitted
from that data source. This
restriction doesn't apply if the
check box is selected.
Terminal Node Even when the check box isn't Modify the tree version such that
On the Data Source dialog box, selected, values from a data all terminal nodes are from data
if the Allow Use as Leaves source are added as leaf nodes sources for which this check box
check box isn't selected, values (terminal nodes). is selected.
from that data source can't
be added as leaves (terminal
nodes) to the tree version. This
restriction doesn't apply if the
Usage Limit For each data source value that

On the Data Source dialog box, Even if the Use All Values isn't yet available, add nodes to
if the Use All Values option option is selected, there are the tree version.
is selected to set the Usage values in the data source that
Limit for the data source, every aren't in the tree version.
value in the data source must
appear as a node in the tree.
This restriction doesn't apply if
None option is selected.
Trees and Data Sources: How They Work Together

Data sources are the foundation of tree management. Tree structures, trees, and tree versions establish direct and real-
time connectivity with the data sources. Changes to the data sources immediately reflect on the Manage Trees and Tree
Versions page and wherever the trees are being used.
Metadata and Data Storage

Tree structures contain the metadata of the actual data and the core business rules that manifest in trees and tree versions.
You can select and enable a subset of trees to fulfill a specific purpose in that application.
198
Access Control
Source data is mapped to tree nodes at different levels in the database. Therefore, the changes you make to the tree nodes
affect the source data. Access control set on trees prevents unwanted data modifications in the database. Access control
can be applied to the tree nodes or anywhere in the tree hierarchy.
Adding Tree Nodes: Points to Consider

Tree nodes are points of data convergence where a tree branches into levels. Nodes are the building blocks of a tree
structure and are attached to tree versions. Whenever you create or edit a tree version, you need to specify its tree node.
In the Setup and Maintenance work area, search for the Define Trees task and access the Manage Trees and Tree Versions
page.
Managing Tree Nodes

You can create, modify, or delete tree nodes on the Tree Version: Specify Nodes page. To add a tree node, ensure that
the tree structure with which the tree version is associated is mapped to a valid data source. You can also duplicate a tree
node if the multiple root node feature is enabled.
Node Levels
Usually, the nodes at a particular level represent similar information. For example, in a tree that reflects the organizational
hierarchy, all nodes representing divisions appear at one level and all the department nodes on another. Similarly, in a tree
that organizes a user's product catalog, the nodes representing individual products might appear at one level and the nodes
representing product lines on the immediate higher level.
The following node levels are in use:
Root node: The highest node in the tree structure

Parent node: The node that branches off into other nodes
Child node: The node that is connected to a node higher in hierarchy (parent node)
Sibling node: Nodes that are at the same level and belong to the same parent node
Leaf node: Entities branching off from a node but not extending further down the tree hierarchy
Node Types
A tree node has the following node types.
Single: Indicates that the node is a value by itself.
Range: Indicates that the node represents a range of values and possibly could have many children. For example, a
tree node representing account numbers 10000 to 99999.
Referenced Tree: Indicates that the tree node is actually another version for the tree based on the same tree
structure, which is not physically stored in the same tree. For example, a geographic hierarchy for the United States
can be referenced in a World geographic hierarchy.
Account Combinations
199
Manage Account Combinations: Explained

Account combinations contain a completed set of segment values that uniquely identifies an account in the chart of accounts.
01-100-1420-003
02-100-1420-005
01-200-1420-002
02-100-1420-004
Account combinations:
Are enabled when created by default.

Cannot be deleted.
Use the From Date to be enabled as of a particular date. For example, if you have a new department as of January
1, 2014, create the account combinations in advance by using a From Date of 01-JAN-2014 to enable the
combinations on that date.
Are discontinue by:
Deselecting the Enabled check box.
Entering a To Date to end date.
Set the following attributes on the Manage Account Combinations page:
Preserve Attributes: To prevent changed segment values from overriding values defined at the account
combination level when running the Inherit Segment Value Attributes process.
Type: To identify the type of account, Asset, Liability, Revenue, Expense, and Owner's Equity.
From and To Dates: To enable or disable the account combination on a specific date.
Allow Posting: To use the account combination in journals.
Alternative Account: To use an alternative account combination when this one is disabled.
Related Topics
Creating an Account Combination : Examples
Account Aliases: Explained

Define account shorthand aliases to speed entry of account segment values.
If you enable shorthand alias when you define your chart of accounts, then you can define aliases, or codes, which represent
complete or partial accounts.
200
Oracle Fusion General Ledger can currently use this feature in the following user interfaces:
Journal lines in the Create Journal page.
Create Journal in Spreadsheet for both Single Journal and Multiple Journals modes.
Manage Account Combinations in the Alternate Account field.
Manage Intercompany Outbound Transactions and Manage Intercompany Inbound Transactions pages.
Other pages where the account list of values selector is present.
Note: Account Groups in the Account Monitor region and the Inquire and Analyze Balances page are based
on the underlying GL Balances cube. These pages do not present you with a list of values to search and select
accounts. Therefore, you are not able to leverage shorthand aliases.
Enabling Shorthand Aliases

The administrator or implementor is required to select the Shorthand alias enabled option as part of the chart of accounts
structure instance definition. Freeze and compile your account structure in the Manage Chart of Accounts Structure
Instances page when you are ready to begin using your structure. You must recompile your chart of accounts structure
instance every time you make changes to your structure and segments, including enabling or disabling shorthand entries.
The following features and functionality apply to shorthand aliases.

The segment value security is automatically enforced when creating or maintaining aliases.
Cross-validation rules are not imposed since the aliases template account combinations do not update the account
combinations.
The alias field is displayed when you select the account list of values selector in the data entry regions where the
selector appears. The field is enabled for both the list of values and search functionality. You can also enter segment
values directly in the account value fields, thus ignoring the alias functionality.
Enter GL Account Aliases: Examples

You are assigned the task of defining shorthand account aliases to speed up journal entry.
Enter a Partial Account Alias

Use these steps to enter a partial account alias for your account payables account.
1. Navigator > Setup and Maintenance> All Tasks > Manage Shorthand Aliases.
2. Click the Add Row icon.
3. Enter the Name: AP.
4. Enter the Account Template by entering 101 in the Company segment and 221000 in the Account segment.
5. Enter Description: Accounts Payables account.
6. Verify that the Enabled option is selected.
7. Accept today's date as the Start Date.
8. Leave the End Date blank.
9. Click Save.
Enter a Full Account Alias

Use these steps to enter a full account alias for your cash account.
1. Navigator > Setup and Maintenance> All Tasks > Manage Shorthand Aliases.
2. Click the Add Row icon.
201
3. Enter the Name: Cash.

4. Enter the Account Template values, as shown in this table.
Field Value
Company 101

LOB 00

Account 111000

Sub-Account 000

Product 000

Intercompany 000

5. Enter Description: Cash account.

6. Verify that the Enabled option is selected.
7. Accept today's date as the Start Date.
8. Leave the End Date blank.
FAQs for Account Combinations

What happens if I run the Inherit Segment Value Attributes process?
Running the process eases chart of accounts maintenance by automatically replicating changes to segment value attributes
of the account combinations that contain that segment value.
For example, enable a particular cost center segment value that had been disabled previously. Navigate from the Scheduled
Processes page to run the Inherit Segment Value Attributes process and re-enable all account combinations containing
that cost center automatically.
Use the Segment Value Inheritance Exception Report to view the account combinations that have been changed.
Prevent selected account combinations from being affected by selecting the Preserve Attribute check box in the Manage
Account Combinations page.
Note:
Individual segment value attributes override account combination attributes.
Conflicting settings for Enabled, Allow Posting, From Date, or To Date are resolved by using the most
restrictive of the settings of the individual segment values.
Disabling a segment value disables the combinations containing that value, even if the Preserve Attributes
202
Accounting Calendars
Defining Accounting Calendars: Critical Choices

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. The choices you make when specifying the following options are
critical, because it is difficult to change your accounting calendar after a period status is set to open or future enterable.
Budgetary control only
Start Date
Period Frequency
Adjusting Period Frequency
Period Name Format
Note: In Oracle Fusion, the common calendar types, monthly, weekly, 4-4-5, 4-5-4, 5-4-4, 4-week, quarterly,
and yearly, are automatically generated. This functionality makes it easier to create and maintain accounting
calendars. By using the period frequency option, you no longer have to go through the tedious task of defining
each period manually.
Budgetary Control Only Check Box

Select the check box for Budgetary control only to use the calendar for budgetary control only. Budgetary Control refers to
the group of system options and the validation process of determining which transactions are subject to validation against
budgets and budget consumption to prevent overspending.
Start Date
If you plan to run translation, specify a calendar start date that is a full year before the start date of the year of the first
translation period for your ledger. Translation cannot be run in the first period of a calendar. Consider how many years of
history you are going to load from your previous system and back up the start date for those years plus one more. You
cannot add previous years once the first calendar period has been opened.
Period Frequency
Use period frequency to set the interval for each subsequent period to occur, for example, monthly, quarterly, or yearly. If you
select the period frequency of Other, by default, the application generates the period names, year, and quarter number. You
specify the start and end dates. You must manually enter the period information. For example, select the period frequency of
Other and enter 52 as the number of periods when you want to define a weekly calendar. For manually entered calendars,
when you click the Add Year button, the application creates a blank year. Then, you must manually enter the periods for the
new year. The online validation helps prevent erroneous entries.
If the 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.
Note: In Oracle Fusion applications a calendar can only have one period frequency and period type. Therefore,
if you have an existing calendar with more than one period type associated with it, during the upgrade from
Oracle E-Business Suite, separate calendars are created based on each calendar name and period type
combination.
203
Adjusting Period Frequency

Use the adjusting period frequency to control when the application creates adjusting periods. For example, some of the
frequencies you select add one adjusting period at year end, two at year end, or one at the end of each quarter. The default
is None which adds no adjusting periods. If you select the frequency of Other, the Number of Adjusting Periods field is
displayed. Enter the number of desired adjusting periods and then, manually define them.
Period Name Format Region

In the Period Name Format region enter the following fields:
User-Defined Prefix: An optional feature that allows you to enter your own prefix. For example, define a weekly
calendar and then enter a prefix of Week, - as the separator, and the period name format of Period numberYY fiscal
year. The application creates the names of Week1-11, Week2-11, through Week52-11.
Format: A predefined list of values filtered on the selected separator and only displays the options that match the
selected separator.
Year: The year displayed in the period names is based on the selected period name format and the dates the period
covers or if the period crosses years, on the year of the start date of the period.
For example, April 10, 2010 to May 9, 2010 has the period name of Apr-10 and December 10, 2010 to
January 9, 2011 has the name of Dec-10.
If period frequency is Other, then the period format region is hidden. The application generates a temporary
period name for calendars with period frequency of Other, using a fixed format of Period numberYY. You can
override this format with your own customized period names.
Note: For an accounting calendar that is associated with a ledger, changing period names or adding a year
updates the accounting period dimension in the balances cubes.
Calendar Validation: How It Works with the Accounting Calendar

Calendar validation is automatic and prevents serious problems when you begin using a calendar. Once you set a calendar
period status to open or future enterable, you can't edit the period.
Settings That Affect Calendar Validation

Calendar validation runs automatically after you save the calendar.
How a Calendar Is Validated

The following table lists the validation checks that are performed when an accounting calendar is saved.
Validation Data Example
Unique period number 2 assigned for two periods

Unique period name Jan-17 entered twice

Period number beyond the maximum 13 for a 12 period calendar with no adjusting periods
number of periods per year

204
Validation Data Example
Entered period name contains spaces Jan 17

Single or double quotes in the period Jan '17

name

Nonadjusting periods with overlapping 01-Jan-2017 to 31-Jan-2017 and 30-Jan-2017 to 28-Feb-2017

dates

Period date gaps 01-Jan-2017 to 28-Jan-2017 and 31-Jan-2017 to 28-Feb-2017

Missing period numbers Periods 1 through 6 are defined for a calendar with 12 months

Period number gaps 1, 3, 5

Period numbers not in sequential order Period 1 covers 01-Jan-2017 to 31-Jan-2017 and period 2 covers 01-Mar-2017 to 31-Mar-2017,
by date and period 3 covers 01-Feb-2017 to 28-Feb-2017.

Quarter number gaps 1, 3, 4

Quarters not in sequential order by 1, 3, 2, 4

period

Period start or end dates more than one July 1, 2015 in a 2017 calendar
year before or after the fiscal year

FAQs for Accounting 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 is 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.
205
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.
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
Defining Currencies: Points to Consider

When creating or editing currencies, consider these points relevant to entering the currency code, date range, or symbol for
the currency.
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.
Euro Currency Derivation: Explained

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.
206
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 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).
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.
Minimum accountable unit is the smallest denomination for the currency. For example, for USD that would be .01 for a cent.
In Setup and Maintenance work area, search for the Manage Currencies task to set these values for a currency.
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.
Conversion Rate Types
Creating Conversion Rate Types: Critical Choices

Maintain different conversion rates between currencies for the same period using conversion rate types. The following
conversion rate types are predefined:
Spot
Corporate
207
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.
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 is 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.
208
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.
Check the Allow Cross Rates Override check box to permit your users to override application generated cross rates. If you
accept the default of unselected, the application generated cross rates cannot 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 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.
Using Rate Types: Examples

The four predefined conversion rate types are:
Spot
Corporate
User
Fixed
209
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.

HKD User Entered a one time transaction. Your

company does not maintain daily rates for
Hong Kong dollars.

Your company does not 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 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.
210
Daily Rates
Load GL Currency Rates: Overview

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.
The three different methods of loading currency rates are:
1. Manual load using the Daily Rates spreadsheet
2. Manual load using File Based Data Import process.
3. Automatic load using web services.
Note: If you encounter errors loading currency rates, you can correct the errors and reload.
Entering Daily Rates Manually: Worked Example

You are required to enter the daily rates for currency conversion from Great Britain pounds sterling (GBP) to United States
dollars (USD) for 5 days for your company InFusion America Inc.
In order to load rates using the Daily Rates Spreadsheet, you need to install Oracle ADF Desktop Integration client software.
Oracle ADF Desktop Integration is an Excel add-in that enables desktop integration with Microsoft Excel workbooks. Users
can download the installation files from Navigator > Tools > Download Desktop Integrator Installer.
Entering Daily Rates

1. Navigator > Period Close.
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 Create in Spreadsheet button.
Use the Create Daily Rates spreadsheet to enter daily rates in a template that you can save and reuse.
5. Click in the From Currency field. Select the GBP - Pound Sterling list item.
6. Click in the To Currency field. Select the USD - US Dollar list item.
7. Click in the Conversion Rate field. Select the Spot list item
8. Click in the From Conversion field. Enter a valid value: 10/1/2014.
9. Click in the To Conversion Date field. Enter a valid value: 10/5/2014.
10. Click in the Conversion Rate field. Enter a valid value: 1.6.
11. Click the Submit > OK twice.
12. Review the Record Status column to verify that all rows were loaded successfully.
211
13. Save template to use to enter daily rates frequently. You can save the spreadsheet to either a local drive or a shared
network drive.
14. Optionally, edit the rates from the Daily Rates user interface or resubmit the spreadsheet.
Related Topics
GL Currency Rates File Based Load: Examples

Oracle File Based Data Import (FBDI) is used when you must load high volume of daily rates data to Oracle Cloud ERP.
Scenario
You are assigned the task to upload daily rates for your company. You have decided to use the File Based Data Import and
perform the following steps.
Note: For more information about file-based data import, see the File Based Data Import for Oracle Financials
Cloud guide.
1. Download the Daily Rates template called DailyRatesImportTemplate.xlsm from the File Based Data Import for Oracle
Financials Cloud guide.
2. Enter the rates data in the FBDI template. To prepare your data in a spreadsheet format, use XLS templates.
a. The first worksheet in each template provides instructions for using the template.
b. Save a copy of the file.
c. Enable macros using Options > Enable this content radio button.
3. Validate data.
You can use template design to perform extensive validations at the preliminary level.
Checks data formats and other field checks. if a rate overlap is present for a particular combination of From

and To Currency code and rate type. Errors are identified and presented in a separate sheet for the users to
review and correct
Checks if a rate overlap is present for a particular combination of From and To Currency codes and rate
type.
Identifies errors and presents them in a separate sheet for the users to review and correct them before
revalidating.
4. Generate daily rates .zip file.
Generate daily rates .zip file containing the validated and formatted comma-separated values (.csv) file by selecting
Generate Daily Rates button within the template.
5. Upload file in Universal Content Management (UCM) system which is a single platform for managing contents across
your enterprise.
a. Use Navigator > File Import and Export to upload the file in the UCM server.
b. Use the Account as fin/generalLedger/import when uploading.
c. Save and Close.
212
6. Run Load Interface File for Import Process from Navigator -> Tools-> Scheduled processes->Schedule
New Process. This process:
a. Validates the data before uploading the data to the GL Daily Rates Interface table.
b. Allows review the error log and correction of errors before running the process again.
c. Populate GL Daily Rates table automatically as a post import process once data is successfully validated.
7. Review the imported rates by navigating to Manage Currency Rates page.
Note: For more information see: Load Currency Rates To Oracle Fusion ERP Cloud (Doc ID 1950660.1) on My
Oracle Support.
Related Topics
File Based Data Import for Oracle Financials Cloud
Automatic Load Using Web Services: Examples

If you have a rate subscription source that provides daily rates, use a web service to fully automate the loading of the rates
using the File Based Data Import. The external web service FinancialUtilService enables you to upload data files to the
Oracle Universal Content Management (UCM), and launch the processes to import the rates to Oracle Cloud ERP.
Scenario
You are setting up an automatic process to load your company's daily rates.
Process Steps:
1. Get rates file from the designated external source.
If you have a rate subscription source that provides daily rates, then you can call web service to collect the file and to
feed into Oracle Data Integrator (ODI) or alternatively to a temporary storage in the UCM that in turn can be fed into
ODI for further processing.
2. Prepare and validate data.
You would need to perform data transformation to fit the format of the spreadsheet template. These data processing
steps can be accomplished using the ability extended by Oracle Data Integrator (ODI).
The .csv data file needs to be provided and transformed in the specific format, in the exact column sequence as in
the .xlsm file and data types as expected. For example, the .csv file provides columns such as from currency code,
to currency code, dates in canonical format, conversion rate type, and the rate.
3. Call web service uploadFileToUcm.
Automatically upload the formatted, validated file from ODI into the Universal Content Management (UCM).
4. Call web service submitESSJobRequest.
Submit the Load Interface File for Import process to load data into GL Daily Rates interface table.
5. Call web service getESSJobStatus.
Verify the status of request submitted in previous step. If the process ended in errors, you may need to correct them
and then resubmit the process.
6. The process to submit the import rates from interface table to GL Daily Rates table happens automatically as a
post process to the submit the Load Interface File for Import process performed in step four.
213
7. Once the Import and Calculate Daily Rates process completes successfully, you can verify and review the rates
from the Currency Rates Manager page.
Security Required for Loading GL Currency Rates: Explained

The following tables lists the security privileges and duties that you must be assigned for tasks related to loading rates to
Oracle Cloud ERP.
Tasks Privilege Duties
Creating rate types Define Conversion Rate Type Daily Rates Administration, General
Accounting Manager

Maintaining daily conversion rates Maintain Daily Conversion Rate Daily Rates Administration, General
Accounting Manager

Importing rate to Cloud ERP Run Daily Rates Import and Calculation Daily Rates Administration, General
Process Accounting Manager

Viewing daily conversion rates View Daily Conversion Rate Daily Rates Administration, General
Accounting Setup Review

Updating Currency Rates: Worked Example

You are required to change today's daily rates that were already entered. The rates you are 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.
214
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
215
216
Implementing Enterprise Structures and General Ledger Ledgers
7 Ledgers
Accounting Configuration Offerings: Overview
The Setup and Maintenance work area in the Oracle Fusion Applications is used 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 Fusion Accounting Hub offering: Used to add the Oracle Fusion General Ledger and Oracle Fusion
Subledger Accounting application features to an existing enterprise resource planning (ERP) system to enhance the
reporting and analysis.
The Oracle Fusion Financials offering includes the Oracle Fusion General Ledger and Oracle Fusion Subledger
Accounting application features and one or more subledger financial applications.
When adding an offering to an implementation project, customize the tasks displayed by adding additional tasks.
Related Topics
What's an implementation project?
What's a functional area?
What's an offering?
Ledgers and Subledgers: Explained

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.
Single Ledger
If your subsidiaries all share the same ledger with the parent company or they share the same chart of accounts and
calendar, and all reside on the same applications instance, you can consolidate financial results in Oracle Fusion General
Ledger in a single ledger. Use Oracle Fusion Financial Reporting functionality to produce individual entity reports by balancing
segments. General Ledger has three balancing segments that can be combined to provide detailed reporting for each legal
entity and then rolled up to provide consolidated financial statements.
217
Multiple Ledgers
Accounting operations using multiple ledgers can include single or multiple applications instances. You need multiple ledgers
if one of the following is true:
You have companies that require different account structures to record information about transactions and balances.
For example, one company may require a six-segment account, while another needs only a three-segment account
structure.
You have companies that use different accounting calendars. For example, although companies may share fiscal
year calendars, your retail operations require a weekly calendar, and a monthly calendar is required for your
corporate headquarters.
You have companies that require different functional currencies. Consider the business activities and reporting
requirements of each company. If you must present financial statements in another country and currency, consider
the accounting principles to which you must adhere.
Subledgers
Oracle Fusion Subledgers capture detailed transactional information, such as supplier invoices, customer payments, and
asset acquisitions. Oracle Fusion Subledger Accounting is an open and flexible application that defines the accounting rules,
generates detailed journal entries for these subledger transactions, and posts these entries to the general ledger with flexible
summarization options to provide a clear audit trail.
Ledgers: Points to Consider

Companies account for themselves in primary ledgers, and, if necessary, secondary ledgers and reporting currencies.
Transactions from your subledgers are posted to your primary ledgers and possibly, secondary ledgers or reporting
currencies based on balance, subledger, or journal level settings. Local and corporate compliance can be achieved through
an optional secondary ledger. Provide an alternate accounting method, or in some cases, a different chart of accounts.
Your subsidiary's primary and secondary ledgers can both be maintained in your local currency. You can convert your
local currency to your parent's ledger currency to report your consolidated financial results using reporting currencies or
translation.
Primary Ledgers
A primary ledger:
Is the main record-keeping ledger.
Records transactional balances by using a chart of accounts with a consistent calendar and currency, and
accounting rules implemented in an accounting method..
Is closely associated with the subledger transactions and provides context and accounting for them.
To determine the number of primary ledgers, your enterprise structure analysis must begin with your financial, legal, and
management reporting requirements. For example, if your company has separate subsidiaries in several countries worldwide,
enable reporting for each country's legal authorities by creating multiple primary ledgers that represent each country with the
local currency, chart of accounts, calendar, and accounting method. Use reporting currencies linked to your country-specific
primary ledgers to report to your parent company from your foreign subsidiaries. Other considerations that affect the number
of primary ledgers required are:
Corporate year end
218
Ownership percentages
Local government regulations and taxation
Secondary ledgers
Secondary Ledgers
A secondary ledger:
Is an optional ledger linked to a primary ledger for the purpose of tracking alternative accounting.
Can differ from its primary ledger by using a different accounting method, chart of accounts, accounting calendar,
currency, or processing options.
When you set up a secondary ledger using the Manage Secondary Ledger task, you select a data conversion level. The data
conversion level determines what level of information is copied to the secondary ledger. You can select one of the following
levels: Balance, Journal, Subledger, or Adjustment Only.
Balance: When you run the Transfer Balances to Secondary Ledger process, balances are transferred from the
primary ledger to the secondary ledger.
Journal: When you post journals in the primary ledger, the posting process copies the journals to the secondary
ledger for the sources and categories that you specify in the Journal Conversion Rules section on the Map Primary to
Secondary Ledger page.
In the Journal Conversion Rules section, you can do one of the following:
Accept the default setting of Yes for the journal source and category combination of Other, and then specify
the source and category combinations to exclude from the conversion.
Set the journal source and category combination of Other to No, and then specify the source and category
combinations to include in the conversion.
Subledger: When you post journals in the primary ledger, the posting process copies the journals to the secondary
ledger for the sources and categories that you specify in the Journal Conversion Rules section on the Map Primary
to Secondary Ledger page. To prevent duplication, posting doesn't copy any journal that originated from subledgers,
regardless of the settings in the Journal Conversion Rules section.
Caution: You don't have to specify journal conversion rules for your subledgers because journal
conversion rules are applicable only to postings from Oracle Fusion General Ledger. The Create
Accounting process automatically produces accounting for both the primary and secondary ledgers,
regardless of the journal conversion rule settings.
Adjustment Only: This level is an incomplete accounting representation that holds only adjustments. The
adjustments can be manual adjustments or automated adjustments from subledger accounting. This type of
secondary ledger must share the same chart of accounts, accounting calendar, period type, and currency as the
associated primary ledger.
Tip: To obtain a complete secondary accounting representation that includes both transactional data and
adjustments, use ledger sets to combine the ledgers when running reports.
Example
Your primary ledger uses US Generally Accepted Accounting Principles (GAAP) and you maintain a secondary ledger for
International Financial Reporting Standards (IFRS) accounting requirements. You first decide to use the subledger conversion
level for the IFRS secondary ledger. However, since most of the accounting between US GAAP and IFRS is identical,
219
the adjustment only level is the better solution for the secondary ledger. The subledger level requires duplication of most
subledger and general ledger journal entries and general ledger balances. The adjustment only level transfers only the
adjustment journal entries and balances necessary to convert your US GAAP accounting to the IFRS accounting. Thus,
requiring less processing resources.
Tip: To avoid difficult reconciliations, use the same currency for primary and secondary ledgers. Use reporting
currencies or translations to generate the different currency views to comply with internal reporting needs and
consolidations.
Reporting Currencies
Reporting currencies maintain and report accounting transactions in additional currencies. Consider the following before
deciding to use reporting currencies.
Each primary and secondary ledger is defined with a ledger currency that is used to record your business
transactions and accounting data for that ledger.
Best practices recommend that you maintain the ledger in the currency in which the majority of its transactions are
denominated. For example, create, record, and close a transaction in the same currency to save processing and
reconciliation time.
Compliance, such as paying local transaction taxes, is also easier using a local currency.
Many countries require that your accounting records be kept in their national currency.
If you maintain and report accounting records in different currencies, you do this by defining one or more reporting currencies
for the ledger. When you set up a reporting currency using the Manage Reporting Currency task, you select a currency
conversion level. The currency conversion level determines what level of information is copied to the reporting currency.
You can select one of the following levels: Balance, Journal, Subledger.
Balance: When you run the Translate General Ledger Account Balances process, balances are transferred from the
specified ledger to the reporting currency and converted.
Journal: When you post journals, the posting process copies the journals to the reporting currency for the sources
and categories that you specify in the Journal Conversion Rules section on the Create or Edit Reporting Currency
pages.
In the Journal Conversion Rules section, you can do one of the following:
Accept the default setting of Yes for the journal source and category combination of Other, and then specify
the source and category combinations to exclude from the conversion.
Set the journal source and category combination of Other to No, and then specify the source and category
combinations to include in the conversion.
Subledger: When you generate accounting in the primary ledger, the Create Accounting process produces
accounting for both the primary ledger and the reporting currency. When you post the journals in the primary
ledger, the posting process copies the journals to the reporting currency for the sources and categories that
you specify in the Journal Conversion Rules section on the Create or Edit Reporting Currency pages. To prevent
duplication, posting doesn't copy any journal that originated from subledgers, regardless of the settings in the
Journal Conversion Rules section.
Caution: You don't have to specify journal conversion rules for your subledgers because journal
conversion rules are applicable only to postings from Oracle Fusion General Ledger. The Create
Accounting process automatically produces accounting for both the primary ledger and the reporting
currency, regardless of the journal conversion rule settings.
220
Note: A full accounting representation of your primary ledger is maintained in any subledger level reporting
currency. Secondary ledgers cannot use subledger level reporting currencies.
Do not use journal or subledger level reporting currencies if your organization translates your financial statements to your
parent company's currency for consolidation purposes infrequently. Standard translation functionality meets this need.
Consider using journal or subledger level reporting currencies when any of the following conditions exist.
You operate in a country whose unstable currency makes it unsuitable for managing your business. As a
consequence, you manage your business in a more stable currency while retaining the ability to report in the
unstable local currency.
You operate in a country that is part of the European Economic and Monetary Union (EMU), and you select to
account and report in both the European Union currency and your National Currency Unit.
Note: The second option is rare since most companies have moved beyond the initial conversion to the EMU
currency. However, future decisions could add other countries to the EMU, and then, this option would again be
used during the conversion stage.
Financial Ledgers: How They Fit Together

The process of designing an enterprise structure, including the accounting configuration, is the starting point for an
implementation. This process often includes determining financial, legal, and management reporting requirements, setting up
primary and secondary ledgers, making currency choices, and examining consolidation considerations.
This figure shows the enterprise structure components and their relationships to each other. Primary ledgers are connected
to reporting currencies and secondary ledgers to provide complete reporting options. Legal entities are assigned to ledgers,
221
both primary and secondary, and balancing segments are assigned to legal entities. Business units must be connected to
both a primary ledger and a default legal entity. Business units can record transactions across legal entities.
Corporate
Primary
Ledger
Reporting
Currency
Subsidiary
Secondary
Primary
Ledgers
Ledgers
Mapping Chart of
Accounts
Business
Units
Legal Legal
Entities Entities
Transactions
Balancing Balancing
Segments Segments
Primary Ledgers
A primary ledger is the main record-keeping ledger. Create a primary ledger by combining a chart of accounts, accounting
calendar, ledger currency, and accounting method. To determine the number of primary ledgers, your enterprise structure
analysis must begin with determining financial, legal, and management reporting requirements. For example, if your company
has separate subsidiaries in several countries worldwide, create multiple primary ledgers representing each country with the
local currency, chart of accounts, calendar, and accounting method to enable reporting to each country's legal authorities.
If your company just has sales in different countries, with all results being managed by the corporate headquarters, create
one primary ledger with multiple balancing segment values to represent each legal entity. Use secondary ledgers or reporting
currencies to meet your local reporting requirements, as needed. Limiting the number of primary ledgers simplifies reporting
because consolidation is not required. Other consideration such as corporate year end, ownership considerations, and local
government regulations, also affect the number of primary ledgers required.
222
Secondary Ledgers
A secondary ledger is an optional ledger linked to a primary ledger. A secondary ledger can differ from its related primary
ledger in chart of accounts, accounting calendar, currency, accounting method, or ledger processing options. Reporting
requirements, for example, that require a different accounting representation to comply with international or country-specific
regulations, create the need for a secondary ledger.
If the primary and secondary ledgers use different:
Charts of accounts, a chart of accounts mapping is required to instruct the application on how to propagate journals
from the source chart of accounts to the target chart of accounts.
Accounting calendars, the accounting date, and the general ledger date mapping table are used to determine the
corresponding nonadjusting period in the secondary ledger. The date mapping table also provides the correlation
between dates and nonadjusting periods for each accounting calendar.
Ledger currencies, currency conversion rules are required to instruct the application on how to convert the
transactions, journals, or balances from the source representation to the secondary ledger.
Note: Journal conversion rules, based on the journal source and category, are required to provide instructions
on how to propagate journals and types of journals from the source ledger to the secondary ledger.
Reporting currencies are the currency you use for financial, legal, and management reporting. If your reporting currency is not
the same as your ledger currency, you can use the foreign currency translation process or reporting currencies functionality
to convert your ledger account balances in your reporting currency. Currency conversion rules are required to instruct
the application on how to convert the transactions, journals, or balances from the source representation to the reporting
currency.
Legal Entities
Legal entities are discrete business units characterized by the legal environment in which they operate. The legal environment
dictates how the legal entity should perform its financial, legal, and management reporting. Legal entities generally have
the right to own property and the obligation to comply with labor laws for their country. They also have the responsibility to
account for themselves and present financial statements and reports to company regulators, taxation authorities, and other
stakeholders according to rules specified in the relevant legislation and applicable accounting standards. During setup, legal
entities are assigned to the accounting configuration, which includes all ledgers, primary and secondary.
Balancing Segments
You assign primary balancing segment values to all legal entities before assigning values to the ledger. Then, assign specific
primary balancing segment values to the primary and secondary ledgers to represent nonlegal entity related transactions
such as adjustments. You can assign any primary balancing segment value that has not already been assigned to a legal
entity. You are allowed to assign the same primary balancing segment values to more than one ledger. The assignment of
primary balancing segment values to legal entities and ledgers is performed within the context of a single accounting setup.
The Balancing Segment Value Assignments report is available to show all primary balancing segment values assigned to legal
entities and ledgers across accounting setups to ensure the completeness and accuracy of their assignments. This report
allows you to quickly identify these errors and view any unassigned values.
223
Business Units
A business unit is a unit of an enterprise that performs one or many business functions that can be rolled up in a management
hierarchy. When a business function produces financial transactions, a business unit must be assigned a primary ledger, and
a default legal entity. Each business unit can post transactions to a single primary ledger, but it can process transactions for
many legal entities. Normally, it has a manager, strategic objectives, a level of autonomy, and responsibility for its profit and
loss. You define business units as separate task generally done after the accounting setups steps.
The business unit model:

Allows for flexible implementation
Provides a consistent entity for controlling and reporting on transactions
Enables sharing of sets of reference data across applications
For example, if your company requires business unit managers to be responsible for managing all aspects of their part of the
business, then consider using two balancing segments, company and business unit to enable the production of business unit
level balance sheets and income statements.
Transactions are exclusive to business units. In other words, you can use business unit as a securing mechanism for
transactions. For example, if you have an export business that you run differently from your domestic business, use business
units to secure members of the export business from seeing the transactions of the domestic business.
Creating Primary Ledgers: Example

Create a primary ledger as your main record-keeping ledger. Like any other ledger, a primary ledger records transactional
balances by using a chart of accounts with a calendar, currency, and accounting rules implemented in an accounting
method. The primary ledger is closely associated with the subledger transactions and provides context and accounting for
them.
Scenario
You have been assigned the task of creating a primary ledger for your company InFusion America.
1. Navigator > Define Accounting Configurations > Manage Primary Ledgers > Go to Task.
2. Click the Create icon.
3. Complete the fields, as shown in this table.
Field Value
Name InFusion America

Description InFusion America primary ledger for recording transactions.

Chart of Accounts InFusion America Chart of Accounts

Accounting Calendar Standard Monthly

224
Field Value
Currency USD

Accounting Method Standard Accrual

4. Click Save and Edit Task List to navigate back to the accounting configuration task list.
Note: You can't change the chart of accounts, accounting calendar, or currency for your ledger after
you save the ledger.
Ledger Options
Specifying Ledger Options: Worked Example

This example demonstrates specifying the ledger options for your primary ledger. Your company, InFusion Corporation, is
a multinational conglomerate that operates in the United States (US) and the United Kingdom (UK). InFusion has purchased
an Oracle Fusion Enterprise Resource Planning (ERP) solution including Oracle Fusion General Ledger and all of the Oracle
Fusion subledgers.
After completing your InFusion America Primary Ledger, select Specify Ledger Options under the Define Accounting
Configuration task list on the Functional Setup Manager page.
Note: Both primary and secondary ledgers are created in the same way and use the same user interface to
enable their specific ledger options.
Reviewing General Options

1. Accept the Name and Description defaults for the ledger selected.
2. Review the Currency and Chart of Accounts for the specified ledger, which are automatically populated.
Setting Accounting Calendar Options

1. Review the Accounting Calendar that defaults from your ledger.
2. Select Jan-2017 as the First Open Period for your ledger.
Select a period after the first defined period in the ledger calendar to enable running translation. You cannot run
translation in the first defined period of a ledger calendar. In this example, your calendar began with Jan-2016.
3. Enter 3 for the Number of Future Enterable Periods.
Any value between 0 and 999 periods can be specified to permit entering journals but not posting them in future
periods. Minimize the number of open and future periods to prevent entries in the wrong period.
Selecting Subledger Accounting Options

1. Accept the default Accounting Method from your ledger.
2. Select US American English as your Journal Language.
225
Completing the Period Close Options

1. Enter your Retained Earnings Account: 101-00-31330000-0000-000-0000-0000.
This account is required for general ledger to move the revenue and expense account balances to this account at
the end of the accounting year.
2. Enter your Cumulative Translation Adjustment Account: 101-00-31350000-0000-000-0000-0000.
The Cumulative Translation Adjustment (CTA) account is required for ledgers running translation.
3. Do not enter a Default Period End Rate Type or Default Period Average Rate Type.
The values entered here are used as the default for balance level reporting currency processing. InFusion America
Primary Ledger is using the subledger level reporting currency processing.
Specifying Journal Processing Options

Field Value
Enable Suspense General Ledger

Default Suspense Account 101-00-98199999-0000-000-0000-0000

Rounding Account 101-10-98189999-0000-000-0000-0000

Entered Currency Balancing Account 101-10-98179999-0000-000-0000-0000

Balancing Threshold Percent 10

Field Value
Enable journal approval Click to enable journal approval functionality. Approval rules must be created in the Oracle Fusion
Approvals Management.

Notify when prior period journal Notify the user when a prior period date is selected on a journal entry.

Allow mixed and statistical journals Enter both monetary and statistical amounts on the same line in a journal entry.

Validate reference date Requires a reference date in an open or future enterable period.

3. Click the Separate journals by accounting date during journal import for the Import option to create individual
journal entries for each accounting date.
4. For the Reversal options, select InFusion America Accrual Set from the list of values in the Journal Reversal
Criteria Set field and click the Launch AutoReverse after open period to reverse accrual journal entries
automatically when a new period is opened.
5. Click the Enable intercompany accounting for the Intercompany option to enable automatic balancing for
primary, second, and third balancing segments) on intercompany journals and transactions.
226
To complete the intercompany accounting functionality, you must define intercompany rules.
Related Topics
Journal Posting Process: How Single Currency Journals Are Balanced
Journal Posting Process: How Multicurrency Journals Are Balanced
Assigning Legal Entities and Balancing Segments: Examples

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

Assign one or more legal entities to your configuration by following these steps:
1. Navigator > Setup and Maintenance work area > Define Ledgers > Define Accounting Configurations >
Assign Legal Entities task.
2. If scope is:
Not set: Select Scope link > Assign Legal Entities radio button > In the Primary Ledger drop down Select
and Add > Apply and Go To Task > Select your ledger > Save and Close.
Set, click Go to Task
3. Click the Select and Add icon.
4. Enter your legal entity.
5. Apply > Done.
6. Save and Close.
Assign Balancing Segments to Legal Entities

Assign balancing segment values to your legal entities by following these steps:
Assign Balancing Segment Values to Legal Entities task.
2. If scope is:
Not set: Select Scope link > Assign Balancing Segment Values to Legal Entities radio button > In the
Primary Ledger drop down Select and Add > Apply and Go To Task > Select your ledger > Save and
Close.
Set, click Go to Task.
4. Select the balancing segment value. Optionally, add a Start Date.
5. Save and Close to close the create page.
6. Save and Close.
Assign Balancing Segments to Ledgers

Assign balancing segment values directly to your ledger by following these steps:
Assign Balancing Segment Value to Ledger task.
227
2. If scope is:
Not set: Select Scope link > Assign Balancing Segment Value to Ledger radio button > In the Primary
Ledger drop down Select and Add > Apply and Go To Task > Select your ledger > Save and Close.
3. Select the balancing segment value.
4. Optionally enter a start date.
5. Save and Close.
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
FAQs for Ledger Options

What happens if I change the cumulative adjustment account?
To avoid data corruption, your cumulative adjustment account (CTA) can only be changed if you first perform the following set
of steps:
Purge all translated balances.
Change the CTA account.
Rerun translation.
What happens if I change the retained earnings account?

To avoid data corruption, your retained earnings account can only be changed if you first perform the following set of steps:
Enter and post journals to bring the ending balances for your income statement accounts to zero at the end of each
accounting year
Purge actual translated balances
Update the retained earnings account
Reverse the journal entries use to bring the ending account balances to zero and rerun translation
Assign Access to Ledger
228
Assigning Legal Entities and Balancing Segments: Examples

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

Assign one or more legal entities to your configuration by following these steps:
Assign Legal Entities task.
2. If scope is:
Not set: Select Scope link > Assign Legal Entities radio button > In the Primary Ledger drop down Select
and Add > Apply and Go To Task > Select your ledger > Save and Close.
Set, click Go to Task
3. Click the Select and Add icon.
4. Enter your legal entity.
5. Apply > Done.
6. Save and Close.
Assign Balancing Segments to Legal Entities

Assign balancing segment values to your legal entities by following these steps:
Assign Balancing Segment Values to Legal Entities task.
2. If scope is:
Not set: Select Scope link > Assign Balancing Segment Values to Legal Entities radio button > In the
Primary Ledger drop down Select and Add > Apply and Go To Task > Select your ledger > Save and
Close.
4. Select the balancing segment value. Optionally, add a Start Date.
5. Save and Close to close the create page.
6. Save and Close.
Assign Balancing Segments to Ledgers

Assign balancing segment values directly to your ledger by following these steps:
Assign Balancing Segment Value to Ledger task.
2. If scope is:
Not set: Select Scope link > Assign Balancing Segment Value to Ledger radio button > In the Primary
Ledger drop down Select and Add > Apply and Go To Task > Select your ledger > Save and Close.
3. Select the balancing segment value.
4. Optionally enter a start date.
5. Save and Close.
229
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
Reporting Currency Balances: How They're 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.
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.
230
Type Tasks
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:
Manual journals
Periodic and allocation journals
Unposted journals from non-Oracle subledger applications
Unposted journals from any Oracle Fusion subledger that does not 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 is not 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
231
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 are not 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 are not converted.
Review and Submit Accounting Configuration
232
Oracle Fusion General Ledger Balances Cube: Overview

A balances cube is an online analytical application (OLAP) database that maintains financial balances in a multidimensional
database. A balances cube is created when an accounting configuration is submitted for a primary or secondary ledger that
uses a new unique combination of chart of accounts and calendar.
Chart of
Accounts Primary or
Secondary
Ledger
Calendar
Accounting
Configuration
Process
Currency
Accounting
Method
The balances cubes are named after the chart of accounts they contain.
A balances cube:
Stores your financial balances in a multidimensional enable real time, interactive financial reporting and analysis.
Preaggregates your balances at every possible point of summarization. Preaggregation ensures immediate access to
financial data and eliminates the need for an external data warehouse for financial reporting.
233
Is uniquely identified by the combination of a chart of accounts and an accounting calendar. Average balances are
tracked in a separate balances cube.
Is automatically synchronized by the following general ledger processes: posting, open period, and translation.
Consists of a set of defining business entities called dimensions. Dimensions in a cube determine how data is
accumulated for reporting and analytical purposes
Are referred to as an application or database connection in the user interfaces for:
Financial Reports
Smart View
Calculation Manager
Note: Account balances were maintained in relational tables in Oracle E-Business Suite General Ledger. The
Oracle Fusion General Ledger updates balances in real time to the relational tables and the General Ledger
Balances cubes. Most inquiry and reporting are now performed from the General Ledger Balances cubes and
not from the relational tables.
Standard Balances Cube Dimensions: Explained

A balances cube consists of a set of defining business entities called dimensions. These dimensions are available for creating
financial reports, Smart View queries, and allocations using multidimensional cubes.
The following table describes the dimensions and provides example values.
Dimension Description Examples
Accounting Period Based upon the calendar of the ledger or 2012

ledger set. Report on years, quarters, or Quarter-1
periods. Jan-12

Ledger or Ledger Set Used to select a ledger for the reporting. Vision North America Ledger Set
Multiple ledgers may be in the same cube if Vision US Primary Ledger
they share a common chart of accounts.

Chart of Accounts Segments Uses a separate dimension for each of the Company: Vision America: 101
segments from the charts of accounts. Cost Center: Sales: 400
Organized by hierarchy. A default hierarchy Account: Cash: 1110
is provided that includes all detail segment
values. Hierarchies published in the Publish
Account Hierarchies user interface are
included.

Scenario Budget 2012

Indicates if the balances represented are
Actual
actual or budget amounts. Allocation-related
dimensions are predefined members and Forecast 2013
required for allocation solutions. Allocation
dimensions are not used directly by end
users.
Budget scenario dimension members

are user-defined in the Oracle Fusion
234
Dimension Description Examples

Applications value set called Accounting
Scenario. The dimension members appear in
the cube after running the Create Scenario
Dimension Members process.
Balance Amount Indicates if the value is the beginning Beginning Balance (DR, CR, or Net)
balance, period activity, or ending balance. Period Activity (DR, CR, or Net)
Debit, Credit, and Net amounts are available Ending Balance (DR, CR, or Net)
for reporting.

Amount Type Indicates whether the amounts represent Base

Base, Period to Date, Quarter to Date, or PTD: Period to Date
Year to Date. QTD: Quarter to Date

YTD: Year to Date
Currency Used to select the wanted currency for the All ISO Currencies
balances. USD: US Dollar
JPY: Japanese yen
Currency Type Used to select the currency type of the Total

balances. Entered
Converted From (for each ISO
currency)
Note: Dimensions are predefined and new ones cannot be added.
Creating GL Balances Cubes: Examples

There are two types of Oracle Fusion General Ledger Balances cubes: Standard Balances cubes and Average Balances
cubes.
Standard Balances Cubes

A new standard balances cube is created whenever an accounting configuration is submitted for a ledger, either primary or
secondary, that uses a new unique combination of chart of accounts and accounting calendar. Cubes are named after the
chart of accounts.
Two examples of standard balance cubes:
1. The chart of accounts, InFusion US Chart of Accounts has a related cube entitled, InFusion US Chart of Accounts.
If a chart of accounts is used by multiple ledgers with different calendars, the cube names are distinguished by
appending a number to their names.
2. The InFusion US Chart of Accounts is used by two different ledgers, each of which has a different accounting
calendar, one with a standard calendar year ending December 31st and the other with a fiscal year ending May 31st.
Two cubes are created. The cubes are named InFusion US Chart of Accounts and InFusion US Chart of Accounts 2.
Average Balances Cubes

Average balances cubes use different dimensions than the standard balances cubes therefore require their results be stored
in separate cubes. If the average balances option is enabled for a ledger, a second average balances cube is automatically
235
created based upon the same criteria of a unique combination of chart of accounts and accounting calendar. Average
balances cubes are named with ADB (average daily balances) plus the name of the associated chart of accounts.
For example, for a chart of accounts, InFusion US Chart of Accounts, the average balances cube name is ADB InFusion
US Chart of Accounts. Numbers are appended to the name when more than one calendar is used by the same chart of
accounts. The numbering is determined and shared with the related standard balances cubes. The standard cube called
InFusion US Chart of Accounts 3 has a corresponding average balance cube entitled ADB InFusion US Chart of
Accounts 3.
Customer Specific GL Balances Cube Dimension Values: Points to

Consider
In creating your cube, take in to consideration the dimensions that are you, the customer, define and those that are partially
or completely predefined by Oracle Fusion Applications.
Two dimensions, Chart of Accounts and Scenario, have customer specific dimension values and require user
procedures to populate the cube
Accounting Period, Currency, and Ledger dimensions are customer specific, but are automatically created in the
cubes from the changes made in the applicable user interfaces.
Other dimensions, such as Amount Type and Balance Amount, have only predefined members.
The following are points to consider in setting up and populating cubes for the Chart of Accounts and Scenario dimension
members.
Create Account Hierarchies

Account hierarchies for your chart of account dimensions are created in the Manage Account Hierarchies page or
the Manage Trees and Trees Versions page after setting up your value sets, chart of accounts, and values.
Create account hierarchies (trees) to identify managerial, legal, or geographical relationships between your value set
values.
Define date-effective tree versions to reflect organizational changes within each hierarchy over time.
The tree version must be in an active or inactive status to be published. Draft versions cannot be published.
Note: From your implementation project, Navigate > Define Common Applications Configuration >
Define Enterprise Structures > Define Financial Reporting Structures > Define Chart of Accounts >
Manage Account Hierarchies > Go to Task.

Next, after defining the tree versions, publish account hierarchies (tree versions) to the cube. Before publishing, set the
following profile option: GL: Set Cube Alias to Segment Value Description. Consider the following points when setting the
profile option.
The member alias displayed in the Oracle Fusion General Ledger balances cubes.
Yes displays only the segment value description, for example: Cash.
No displays value plus the segment value description, for example: 1110 Cash.
When you change the profile option setting, republish the hierarchy.
Default value is No.
236
No is necessary when there are duplicate segment value descriptions in the same value set. The descriptions are
stored in the Alias in the cube. Aliases must be unique in a dimension in the cube. For example, if the description
West existed for more than two segment values in the Cost Center value set the entire cube creation process fails.
Note: Essbase cubes display only the first 80 characters in the description, so the first 80 characters in
the description must be unique.
If duplicate segment value descriptions exist, the cube can be created with the profile set to No. At anytime the value
of the profile can be changed to Yes after the duplicates are removed. At that time, the account hierarchies (tree
versions) must be published or republished to the cube.
If you set the profile value to Yes, and then decide to rebuild a cube from a process run in Enterprise Scheduler or
create a cube by submitting an accounting configuration and duplicate descriptions exist, the create cubes process
errors. You have two options at that point:
Set the profile value to No and run the Create Cubes process. For a new ledger with a new chart of accounts
and accounting calendar combination, submit the accounting configuration.
Remove the duplicates across all dimensions, not just a single segment. Then run the Create Cubes or
resubmit the accounting configuration.
From your implementation project, Navigate > Define Common Applications Configuration > Define Enterprise
Structures > Define Financial Reporting Structures > Define Chart of Accounts > Publish Account Hierarchies >
Go to Task. Use the Publish Account Hierarchies page to search and publish account hierarchies.
Select the Publish check box. This is indicator of what to include in balances cube by selecting the check box or
what you don't want to include in balances cube by removing the check from the check box.
Select the rows. Functionality allows for select multiple rows to be selected.
Select the Publish button to update the balances cubes. A process is generated.
Navigator > Tools > Scheduled Processes to monitor the process.
Note: Use Smart View to verify that the account hierarchies were correctly published.
Define Scenario Dimension Members

The customer specific Scenario dimension members are defined in the Manage Value Sets and Manage Values pages in
the value set called Accounting Scenario. Any customer specific Scenario dimension is included in all balances cubes.
Best practice is to setup the customer specific Scenario members in this value set before you create your first ledger and run
the Accounting Configuration process. The Accounting Configuration process generates your balances cubes.
If the cubes already existed, you can run the Create Scenario Dimension Members process to update the balances cubes
for the new members.
Note: If you are on a release before the Create Scenario Dimension Members process is available, you have
to rebuild the cubes with the Create Cubes process to add the Scenario dimension in the cube. Follow the
guidelines for creating cubes before running process.
237
Default Dimension Values in Reporting: Explained

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 #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.
The following table lists dimensions, available and default dimension values, and provides guidance on selecting the correct
dimension values.
Dimension Possible Values Default Value Additional Information
Accounting Period Years, quarters, and period Accounting Period = Accounting You must always select an
Period (Gen1) accounting period for each
financial report including User
Point of View, Smart View query,
or allocation including Point of
View. If you do not specify a valid
Accounting Period, the financial
reports, Smart View queries,
and Account Inspector displays
#MISSING.

Ledger Includes ledgers and ledger sets Ledger = Ledger (Gen1) If you do not specify a specific
Ledger or Ledger Set, the
financial reports, Smart View
queries, and Account Inspector
queries display #MISSING

Chart of accounts dimensions Not Applicable Highest level (Gen1)

There is a separate dimension
for each segment of the chart
of accounts used by the cube.
Each segment has a default
account hierarchy that includes
all the detail values for the
segment but not parent values.
Only account hierarchies (tree
versions) published from the
user interface are available in the
cube.
Scenario Not Applicable Scenario = Scenario represents Predefined values are Actual,
the sum of all values: Actual + Allocated, and Total for
Allocated + Total for Allocations Allocated. Additional scenario
+ Budget + Forecast. Select a values for Budget, Forecast
value for this dimension. Q1, and Forecast Q2 may be
available if they have been added
to the Accounting Scenario value
set. These additional values are
Note:Must always select a
published to every cube.
Scenario dimension.

Balance Amount Beginning Balance DR, Balance Amount = Balance Not Applicable
CR, or Net Amount (Gen1) which is the
Period Activity DR, CR, or equivalent of Ending Balance.
Net
238
Dimension Possible Values Default Value Additional Information

Ending Balance DR, CR,
or Net
Balance Amount (same as
Ending Balance)
Amount Type Base, PTD, QTD, YTD Amount Type = Amount Type Base is necessary because this
(Gen1) which is the equivalent of is the value used to store from
Base. posting all balances at the lowest
level. PTD, QTD, and YTD are
calculated values.

Currency All ISO currencies (250+). Highest level (Gen1) Similar to Accounting Period and
Ledger, there may not be an
appropriate default for Currency
since different Ledgers have
different ledger currencies. If you
don't specify a valid currency in
a financial report, Smart View
query, or allocation, you get a
result of #MISSING.

Currency Type Total, Entered, and Converted Currency Type = Currency Type Not Applicable
from for each ISO currency = (Gen1), which is the equivalent of
each ISO currency. Total.

Average Balances Cubes Dimensions

The following dimensions are included in the average balances cube in this order. Most comments from standard cube are
applicable unless stated.
Accounting Period: Valid values are years, quarters, accounting period and day, which is equivalent to accounting
date.
Ledger
Separate dimension for each Chart of accounts segment
Scenario
Amount Type valid values are: PATD, QATD, and YATD
Currency
Currency Type
GL Balances Cube Terminology: Explained

Levels and generations are cube terminology used to describe hierarchies in Oracle Fusion General Ledger balances cubes.
Levels
Levels are used to describe hierarchy levels. Levels are numbered from the lowest hierarchy level. For example, the detail
chart of accounts segment values are Level 0. The immediate parent is Level 1; the next parent is Level 2.
239
Generations
Generations (Gen) describe hierarchy levels starting with the highest level of the hierarchy and moving down through the
generations of the same.
An example for generations is as follows:
Accounting Period = Accounting Period is Gen 0
Year is Gen 1
Quarter is Gen 2
Period is Gen 3
Ledger = Ledger is Gen 1
All Ledgers is Gen 2
VF USA is Gen 3
Ledger Set (any ledger set) is Gen 2
Company = Company is Gen 1
All Company Values, for example detail values, is Gen 2
11010 is Gen 3
Tree 1 V1 is Gen 2
[Tree 1 V1].[10000] is Gen 3
[Tree 1 V1].[10000].[11000] is Gen 4
Tree 2 V1 is Gen 2
[Tree 2 V1].[10000] is Gen 3
[Tree 1 V1].[10000].[11000] is Gen 4
Note: Similar levels and generations apply to the other dimension, including chart of accounts dimensions and
those that are not chart of accounts dimensions.
Using Dimension Values in Reporting: Examples

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
240
return the wanted information. Some duplication in the calculations for the balances cube exists to ensure complete reporting
requirements.
Accounting
Amount Balance Period =
Type = Base + Amount + Year, Qtr,
Month
Reporting needs can be completed using the Balance Amount dimension, Amount Type equal to Base, and the Accounting
Period equal to Year, Quarter, or Month.
However, the Amount Type dimension is still required for the following reasons:
To get the complete QTD (Quarter to Date) reporting requirements for the first and second month in a quarter.
Complete QTD can only be achieved using QTD and Accounting Period = Month.
PTD (Period to Date) and YTD (Year to Date) are also available to ensure more consistency reporting with the E-
Business Suite Release 12.
Obtaining Quarter Information

This example shows how to obtain quarter information.
QTD for the first and second months of a quarter can only be achieved using Amount Type dimension equal to QTD.
The end of quarter information can be derived from the Accounting Period dimension equal to Quarter or with the
Amount Type equal QTD.
Obtaining End of Year Information

This example shows how to obtain end of year information.
Accounting Period equal to Year and Balance Amount equal to Ending Balance and Amount Type equal to Base or
YTD.
Accounting Period equal to a specific month and Balance Amount equal to Period Activity and Amount Type equal to
YTD.
When the Balance Amount equals the Balance Amount or the Balance Amount equals the Ending Balance, this
results in an Ending Balance.
Note: Ending Balance is always the ending balance regardless of Amount Type member setting or Accounting
Period member setting (period, quarter or year).
Standard Balances: Example

You have loaded your Oracle E-Business Suite Release 12 balances into your new Oracle Standard Balances Cube. Now you
want to query the results to verify that the data was loaded correctly.
241
Scenario
The tables show the amounts loaded into the balances cube from your R12 balances and the calculated balances for:
Ending balance
Year to date (YTD)
Quarter to date (QTD
The first table is the balance sheet-based balances and the second table is for income statement-based balances.
Oracle E-Business Suite R12 Balances

The following table shows the beginning balance sheet balances, activity, ending balances, and YTD and QTD amounts, for
each month.
Month Beginning Balance Activity Loaded to Ending Balance Calculated YTD QTD
Loaded to Cube Cube
Jan 200 20 220 20 20

Feb 220 30 250 50 50

Mar 250 25 275 75 75

Apr 275 50 325 125 50

May 325 40 365 165 90

Jun 365 45 410 210 135

Jul 410 100 510 310 100

Aug 510 200 710 510 300

Sep 710 140 850 650 440

Oct 850 150 1000 800 150

Nov 1000 100 1100 900 250

Dec 1100 400 1500 1300 650

The following table shows the beginning income statement balances, activity, ending balances, and YTD and QTD amounts,
for each month.
242
Month Beginning Balance Activity Loaded to Ending Balance Calculated YTD QTD
Loaded to Cube Cube
Jan 0 70 70 70 70

Feb 70 20 90 90 90

Mar 90 30 120 120 120

Apr 120 100 220 220 100

May 220 200 420 420 300

Jun 420 250 670 670 550

Jul 670 50 720 720 50

Aug 720 300 1020 1020 350

Sep 1020 130 1150 1150 480

Oct 1150 110 1260 1260 110

Nov 1260 200 1460 1460 310

Dec 1460 500 1960 1960 810

Analysis
These two tables show the results available from Oracle General Ledger from your R12 loaded and aggregated balances in
the balances cube.
Oracle General Ledger Balances

The following table shows the results for the balance sheet balances in the balances cube.
Accounting Period Balance Amount Amount Type Value Comments R12 Amount Type
Equivalent
May Beginning Balance YTD 200 Jan Beginning Not Applicable

Balance

May Period Activity YTD 165 Jan to May Activity YTD-Actual as of

May

May Ending Balance YTD 365 May Ending Balance YTD-Actual as of

May

243
Equivalent
May Beginning Balance QTD 275 Apr Beginning Not Applicable

Balance

May Period Activity QTD 90 Apr-May Activity QTD-Actual as of

May

May Ending Balance QTD 365 May Ending Balance QTD-Actual as of

May

May Beginning Balance PTD 325 May Beginning Not Applicable

Balance

May Period Activity PTD 40 May Activity PTD-Actual as of

May

May Ending Balance PTD 365 May Ending Balance PTD-Actual as of

May

May Beginning Balance Base 325 May Beginning Not Applicable

Balance

May Period Activity Base 40 May Activity PTD-Actual as of

May

May Ending Balance Base 365 May Ending Balance YTD-Actual as of

May

Q2 Beginning Balance QTD 275 April Beginning Not Applicable

Balance

Q2 Period Activity QTD 135 Always Apr-Jun QTD-Actual as of

Jun

Q2 Ending Balance QTD 410 Ending Balance QTD-Actual as of

always as of Jun Jun

Q2 Ending Balance YTD 410 Ending Balance YTD-Actual as of


Q2 Beginning Balance Base 275 Apr Beginning Not Applicable

Balance

Q2 Period Activity Base 135 Always Apr-Jun QTD-Actual as of

Jun

Q2 Ending Balance Base 410 Ending Balance YTD-Actual as of


244
Equivalent
Year Beginning Balance YTD 200 Jan Beginning Not Applicable

Balance

Year Period Activity YTD 1300 Jan-Dec Activity YTD-Actual as of

Dec

Year Ending Balance YTD 1500 Ending Balance YTD-Actual as of

always as of Dec Dec

Year Beginning Balance Base 200 Jan Beginning Not Applicable

Balance

Year Period Activity Base 1300 Jan-Dec Activity YTD-Actual as of

Dec

Year Ending Balance Base 1500 Ending Balance YTD-Actual as of


The following table shows the results for the income statement balances.
Equivalent
May Beginning Balance YTD 0 Jan Beginning Not Applicable

Balance

May Period Activity YTD 420 Jan to May Activity YTD-Actual as of

May

May Ending Balance YTD 420 May Ending Balance YTD-Actual as of

May

May Beginning Balance QTD 120 Apr Beginning Not Applicable

Balance

May Period Activity QTD 300 Apr-May Activity QTD-Actual as of

May

May Ending Balance QTD 420 May Ending Balance QTD-Actual as of

May

May Beginning Balance PTD 220 May Beginning Not Applicable

Balance

May Period Activity PTD 200 May Activity PTD-Actual as of

May

245
Equivalent
May Ending Balance PTD 420 May Ending Balance PTD-Actual as of

May

May Beginning Balance Base 220 May Beginning Not Applicable

Balance

May Period Activity Base 200 May Activity PTD-Actual as of

May

May Ending Balance Base 420 May Ending Balance YTD-Actual as of

May

Q2 Beginning Balance QTD 120 Apr Beginning Not Applicable

Balance

Q2 Period Activity QTD 550 Period Activity QTD-Actual as of

Always Apr-Jun Jun

Q2 Ending Balance QTD 670 Ending Balance QTD-Actual as of


Q2 Ending Balance YTD 670 Ending Balance YTD-Actual as of


Q2 Beginning Balance Base 120 Apr Beginning Not Applicable

Balance

Q2 Period Activity Base 550 Period Activity QTD-Actual as of

always Apr-Jun Jun

Q2 Ending Balance Base 670 Ending Balance YTD-Actual as of


Year Beginning Balance YTD 0 Jan Beginning Not Applicable

Balance (always
zero for Income
Statement)

Year Period Activity YTD 1960 Jan-Dec Activity YTD-Actual as of

Dec

Year Ending Balance YTD 1960 Ending Balance YTD-Actual as of


Year Beginning Balance Base 0 Jan Beginning Not Applicable

Balance (always
zero for Income
Statement)

246
Equivalent
Year Period Activity Base 1960 Jan-Dec Activity YTD-Actual as of

Dec

Year Ending Balance Base 1960 Ending Balance YTD-Actual as of


Invalid Balance Cube Dimension Combinations: Explained

By using various combinations for the Accounting Period, Balance Amount, and Amount Type dimensions, you can derive
different amounts to meet financial reporting requirements.
The following table shows the combinations of the accounting period, balance amount, and amount type dimensions that
don't return data.
Accounting Period Balance Amount Amount Type
Year Beginning Balance QTD

Year Period Activity QTD

Year Ending Balance QTD

Year Beginning Balance PTD

Year Period Activity PTD

Year Ending Balance PTD

Q2 Beginning Balance YTD

Q2 Period Activity YTD

Q2 Beginning Balance PTD

Q2 Period Activity PTD

Q2 Ending Balance PTD

247
GL Balance Cube Related Processes Run from User Interfaces

On application pages, you can run processes that create, rebuild, publish, and maintain Oracle General Ledger balances
cubes, including automatically run child processes.
The Create Accounting Configuration process updates the underlying table and permanently saves the settings after
the accounting configuration has been completed. The process also runs the Create Accounting Configuration: Create
Cubes child process, which creates the accounting configuration and a balances cube when setup is completed. Both
standard and average daily balances (ADB) cubes, if enabled, are processed in the same request. To run the accounting
configuration process, navigate to the Review and Submit Accounting Configuration task.
The Publish Chart of Account Hierarchies process creates the structural hierarchy for the chart of accounts. Both
standard and average daily balances (ADB) cubes, if enabled, are processed in the same request. The process also runs the
Publish Chart of Account Hierarchy Versions child process, one child process runs for each combination of value set and
chart of accounts. To run the publication process, navigate to the Publish Account Hierarchies task.
The Create Ledger Set process updates the underlying tables and creates a ledger set. It affects both standard and ADB
cube types, if enabled, in the same request. To run the ledger set process, navigate to the Manage Ledger Sets task.
The following table describes the child processes for the Create Ledger Set process and indicates the affected cube types.
Child Process Description Cube Type
Create Accounting Configuration: Process Runs processes necessary to process Not applicable to the cube
Accounting Configuration accounting configuration and ledger set data.

Create Ledger Set Dimension Members Creates and updates ledger set members in Standard and ADB, if enabled, in same
a balances cube. request

The following table describes other cube parent and child processes and their related cube types that can be submitted from
other pages or processes.
Parent Process Child Process Description Cube Type Additional Information
Create Ledger Dimension Not Applicable Creates ledger dimension Standard and ADB, if Navigate to the Manage
Member for Reporting member for reporting enabled, in same request Reporting Currencies
Currency currency. task and the Create
Reporting Currency
page. Run for new
reporting currencies
added after accounting
configuration has
completed.

Update Ledger Not Applicable Updates ledger Standard and ADB, if Navigate to the Manage
Dimension Member for dimension member for enabled, in same request Reporting Currencies
Reporting Currency reporting currency. task and the Update
page. This process
runs for new reporting
currencies added after
accounting configuration
has completed.
248
Parent Process Child Process Description Cube Type Additional Information

Not Applicable Publish Chart of Publishes chart of Standard and ADB, if Runs only from the
Accounts Dimension accounts dimension enabled, in same request journal posting process
Members: Detailed member changes to when detailed values
Values Only balances cubes and do not exist in the GL
updates dimension balances cube during
members for any new or posting.
changed segment values.

GL Balance Cube Related Processes Run in Enterprise Scheduler

Service
On the Scheduled Processes page, you can run the processes to create, rebuild, publish, and maintain Oracle General
Ledger balances cubes.
The Create Cube process creates or rebuilds a balances cube based on a combination of chart of accounts and accounting
calendar. The process automatically runs child processes for standard and average daily balance (ADB) cubes, if enabled.
The following table describes the child processes for creating a cube and also indicates the type of cube the process creates,
whether standard or ADB.
Create Cube: Initialize Cube Starts the process to import data into the Standard
balances cube.

Create Cube: Create Calendar Dimension Creates the calendar dimension members Standard
Members and Hierarchies and hierarchies for a balances cube.

Create Cube: Create Ledger Dimension Creates the ledger dimension members for a Standard
Members balances cube.

Create Cube: Publish Chart of Accounts Publishes chart of accounts and hierarchy Standard
Dimension Members and Hierarchies changes to balances cubes and updates
dimension members for any new or changed
segment values.

Create Average Daily Balance Cube Determines the amount required to manually ADB
adjust general ledger account average
balances to reflect the differences between
the original and revalued customer open
items.

Create Cube: Initialize Average Balances Begins the process to import average ADB
Cube balances into the balances cube.

Create Cube: Create Daily Dimension Creates the daily calendar dimension ADB
Members and Hierarchies members and hierarchies for a balances
cube.
249

Create Cube: Create Ledger Dimension Creates the ledger dimension members for a ADB
Members balances cube.

Create Cube: Publish Chart of Accounts Publishes chart of accounts and hierarchy ADB
Dimension Members and Hierarchies changes to balances cubes and updates
dimension members for any new or changed
segment values.

Create Cube: Transfer General Ledger Transfer balances to balances cubes. Standard and ADB, if enabled, in same
Balances to Essbase request

The Publish Chart of Accounts Dimension Members and Hierarchies process publishes chart of accounts dimension
member and hierarchy changes to balances cubes and updates dimension members for any new or changed segment
values. The process affects both standard and ADB cubes in the same request, if ADB cubes are enabled. The process
submits the child process Update Chart of Accounts Dimension Members and Hierarchies, which updates chart of
accounts dimension member and hierarchy changes to Essbase.
The Transfer General Ledger Balances to Essbase process refreshes standard cube, and average balances cube if
enabled, in the General Ledger balances cube.
The following table describes other cube processes that are run in the Enterprise Scheduler Service, and indicates the type of
cube affected.
Parent Process Description Cube Type
Create Accounting Period Dimension for Creates the accounting period dimension Standard
Standard Cube members.

Create Ledger Dimension Members Creates and updates ledger dimension Standard and ADB, if enabled, in same
members including primary ledgers, request
secondary ledgers, reporting currencies, and
ledger sets in the balances cubes.

Create Currency Dimension Members Creates and updates all currencies in every Standard and ADB, if enabled, in same
balances cube. request

Create Scenario Dimension Members Creates and updates all scenario dimension Standard and ADB, if enabled, in same
members when new scenarios are created or request
existing scenarios are changed.

Create Accounting Period Dimension for Creates the accounting period dimension ADB
Average Daily Balances Cube members in the average daily balances cube.

Create Rules XML File for BI Extender Creates rules XML file for a specific Essbase Standard and ADB, if enabled, in same
Automation cube, used for BI extender automation. request

To run the cube process, use the following steps in the Scheduled Processes work area from the Navigator menu.
1. Click Schedule New Process.
250
2. Search the process name.

3. Enter the parameters.
4. Enter the process options and schedule.
5. Click Submit.
FAQs for Review and Submit 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
Opening First Period: Overview

For all ledgers, primary, secondary, and journal and subledger level reporting currencies, open the first period of the ledger
when you are ready to transact in that period.
1. To open the first period of your ledgers, navigate to the Open First Period task in the primary ledger task list.
2. Click the Go to Task icon.
3. On the submission page, select the ledger and the period to open.
4. Click the Submit button to submit the open period process.
You can use other ways to open the first period or subsequent periods without going into the Setup and Maintenance work
area. You can maintain the ledgers' period statuses from the:
Close Status region in the General Accounting Dashboard. The Close Status region provides real-time visibility
into the period close process from your subledgers to your General Ledger across the entire enterprise.
Manage Accounting Periods task in the Period Close work area.
Process Monitoring work area, which provides a framework for submitting, monitoring and maintaining processes
across Oracle Fusion Financials.
251
Clearing Accounts Reconciliation: Overview

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 following figure shows the process flow for clearing accounts reconciliation.
Reconcile Clearing
Accounts
Automatic or Reconcile Clearing

Manual?
Manual Accounts Manually
Automatic
Reconcile Clearing
Reverse Reverse
Accounts Yes
Reconciliation? Reconciliation
Automatically
No
Run Clearing
Accounts
Reconciliation
Reports
Additional
Close Accounting
Yes Reconciliation No
Period
Required?
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.
252
Related Topics
Reconciling Clearing Accounts: Procedure
Setting Up Clearing Accounts Reconciliation: Procedure

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 ending balance.
Steps to Enable
To use clearing accounts reconciliation, perform the following steps:
1. Enable primary and secondary ledgers for clearing accounts reconciliation, as required. Select the Enable Clearing
Accounts Reconciliation option in the Reconciliation section on the Specify Ledger Options page.
2. On the Manage Values page, set the Reconcile attribute to Yes for each of the reconcilable clearing account values
in the natural account segment.
3. Run the Inherit Segment Value Attributes process to update existing account combinations with the subsequent
changes to the segment value.
4. Use the Manage Clearing Accounts Reconciliation setup task to configure and maintain clearing account
reconciliation types and the associated reconciliation rules. You can find the task under the Define General Ledger
Options task list in the Functional Setup Manager.
Related Topics
Security Reference for Oracle Financials Cloud
Enabling Journal Lines for Clearing Accounts Reconciliation: How It Works
Reconciliation Types: Explained

Reconciliation types consist of one or more reconcilable clearing accounts and their associated reconciliation rules. Use the
Manage Clearing Accounts Reconciliation task to configure and maintain them.
Chart of Accounts Level or Ledger Level

You can define reconciliation types at a chart of accounts level or at a ledger level. Chart of accounts level reconciliation types
apply to all associated primary and secondary ledgers that are enabled for reconciliation. For ease of maintenance, define
reconciliation types at the chart of accounts level.
If a ledger requires reconciliation rules that vary from the associated chart of accounts' rules, you can specify the ledger when
creating the reconciliation type. You can select from among the primary and secondary ledgers enabled for clearing accounts
reconciliation that use the chart of accounts you selected.
The Manage Clearing Accounts Reconciliation page automatically displays all reconciliation types, whether defined at a chart
of accounts level or a ledger level.
253
Note: If you submit the automatic reconciliation process for all reconciliation types, the process reconciles
ledger-specific reconciliation types first, followed by chart of accounts level types.
Reconciliation Type Names

Use unique names for reconciliation types. Maintaining a consistent naming convention is recommended. Consider
appending the chart of accounts or ledger name as a suffix to distinguish between chart of accounts level and ledger level
definitions. Following this convention helps you identify the appropriate definitions on the various reconciliation processing
pages. This practice also helps to keep reconciliation type names unique within the application, and across ledgers and
charts of accounts.
Account Matching Rules and Account Filters

When you create a reconciliation type, you must select an account matching rule. The account matching rule identifies the
chart of account segments that are significant for finding matching journal lines during the reconciliation process. Conversely,
the selection implies which segments are insignificant and irrelevant during the reconciliation process. Those irrelevant
segments aren't considered when grouping and matching eligible journal lines that are reconciled together.
The account matching rules are:

By Primary Balancing Segment, Natural Account
By Primary Balancing Segment, Natural Account, Cost Center
By Account Combination
After you select the account matching rule, use the account filter to specify the segment values that belong to valid clearing
account combinations. You would typically specify segment values only for those segments that are part of the account
matching rule that you selected. At a minimum, you must specify a value for one of the segments. Most likely, you would
provide a value for the natural account segment. If you don't specify values for a segment, the reconciliation process
considers all of the underlying child values for that segment as valid values in a clearing account combination, when matching
and grouping together related journal lines.
If you specify values for a segment that's not part of the account matching rule, journal lines across the specified values for
that segment are reconciled together.
For example, a chart of accounts has the following segments and child values:
Company: Primary balancing segment values of 01, 02, 03
Cost Centers: 000, 100, 200
Natural Accounts: Range of 00000 - 99999
Products: 100, 200
The chart of accounts is used by the Vision Services (USA) ledger, which has been enabled for reconciliation. The
reconciliation type has the following attributes:
Name: Approved Claims
Account Matching Rule: By Primary Balancing Segment, Natural Account
Account Filter:
Cost Center: 100 to 200
Natural Accounts: 22100 to 22101
254
This table shows how the process groups the journal lines together for matching and reconciliation, for the Vision Services
(USA) ledger and the Approved Claims reconciliation type.
Set 1 Set 2 Set 3 Set 4 Set 5 Set 6
01-100-22100-100 01-100-22101-100 02-100-22100-100 02-100-22101-100 03-100-22100-100 03-100-22101-100

01-100-22100-200 01-100-22101-200 02-100-22100-200 02-100-22101-200 03-100-22100-200 03-100-22101-200

01-200-22100-100 01-200-22101-100 02-200-22100-100 02-200-22101-100 03-200-22100-100 03-200-22101-100

01-200-22100-200 01-200-22101-200 02-200-22100-200 02-200-22101-200 03-200-22100-200 03-200-22101-200

In this example, the journal lines are grouped together into six sets. Because the account matching rule is By Primary
Balancing Segment, Natural Account, each primary balancing segment value (01, 02, 03) is combined with each natural
account segment value that's in the account filter (22100, 22101), into its own set.
Since the product segment isn't part of the account matching rule or account filter, each set includes all of the product
segment values (100, 200).
Lastly, the cost center segment isn't part of the account matching rule, but it's included in the account filter. The cost center
segment values are 000, 100, and 200, but the account filter specifies only 100 and 200. This means that the journal lines
eligible for reconciliation are limited to account combinations with cost centers 100 and 200. And, since the cost center isn't
part of the account matching rule, each set includes journal lines containing both cost centers 100 and 200.
In summary, even though the following account combinations include primary balancing segment values 01, 02, and 03, and
natural account segment values 22100 and 22101, they're excluded from the reconciliation because the cost center is 000.
01-000-22100-100
01-000-22100-200
01-000-22101-100
01-000-22101-200
02-000-22100-100
02-000-22100-200
02-000-22101-100
02-000-22101-200
03-000-22100-100
03-000-22100-200
03-000-22101-100
03-000-22101-200
Reconciliation Start Date and Last Automatic Reconciliation Run

Every reconciliation type has a reconciliation start date. The reconciliation start date, and the criteria you specify when
reconciling automatically or manually, are used to retrieve the clearing account journal lines eligible for reconciliation. Only
journal lines with an accounting date after the reconciliation start date are available for reconciliation.
255
The Manage Clearing Accounts Reconciliation page displays the date of the last successful automatic reconciliation run. You
can use this date to track and monitor completed and pending reconciliations. Clearing accounts reconciliation, as an integral
part of period close activities, can be planned accordingly.
Tolerances for Manual Reconciliation

You can set up amount and percentage tolerances for manual reconciliation. When the net accounted amount of the journal
lines is within the tolerance, the lines can be reconciled together using manual reconciliation. If you:
Leave both the amount and percentage tolerance fields blank, then there is no tolerance.
Specify a value in one of the two tolerance fields, that amount or percentage becomes the applicable tolerance.
Specify both an amount and a percentage, the stricter of the two tolerances is applied.
The percentage tolerance is calculated on the higher of the grouped journal lines total debit or credit amounts. The amount
tolerance is based on the absolute amount in the ledger currency.
Changes to Reconciliation Types

You can change the reconciliation type name, description, tolerance percentage or amount, reconciliation start date, and
whether the reconciliation type is active. The edited reconciliation type becomes the applicable definition for any future
reconciliation processes subsequent to the edit. Existing journal line groups that were already reconciled aren't affected by
the changes. You can still reverse groups that were previously reconciled.
Inactive Reconciliation Types

Inactive reconciliation types are ineligible for automatic and manual clearing accounts reconciliation processing, starting
from the moment they're inactivated. Also, the submission page for the Unreconciled Transactions report doesn't display
inactive reconciliation types as a report parameter. You can however, use inactive reconciliation types when submitting the
Reconciled Transactions report, as well as on the Reverse Reconciliation page.
Related Topics
Automatic Clearing Accounts Reconciliation: How It Works
Manually Reconciling Clearing Accounts: Procedure
Tolerances and Manual Clearing Accounts Reconciliation:

How It Works
When you define reconciliation types for clearing accounts reconciliation, you can specify an amount tolerance, a percentage
tolerance, or both. These tolerances apply only to the manual reconciliation process. The percentage tolerance is calculated
on the higher of the grouped journal lines total debit or credit amounts. The amount tolerance is based on the absolute
amount in the ledger currency. If you specify both an amount tolerance and a percentage tolerance, the stricter of the two is
applied.
256
How Tolerances Are Applied

As an example, a reconciliation type has the following definition:
Chart of accounts level

Account Matching Rule: By Account Combination
Account Filter: 01-000-22100
Tolerance percentage: 1
Tolerance amount: 5
This table shows the journal lines eligible for reconciliation that were retrieved on the Manual Reconciliation page.
Journal Line Account Combination Accounted Amount (Debit) Accounted Amount (Credit)
1 01-000-22100 100.00 None

2 01-000-22100 None 98.00

Total debits are 100.00 and total credits are 98.00. The higher of the two is 100.00. The percentage tolerance of 1 is applied
against 100.00. One percent of 100.00 is 1. The amount tolerance is 5. The stricter of the two is applied, so in this example,
the tolerance of 1 is applied. The difference between total debits of 100.00 and total credits of 98.00 is 2. This difference is
higher than the applicable tolerance of 1, so the two journal lines remain unreconciled.
257
258
Implementing Enterprise Structures and General Ledger Intercompany Setup
8 Intercompany Setup
Manage Intercompany System Options
Intercompany System Options: Explained

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 is processed.
System Options
Changing and saving a system option has no effect on intercompany transactions already in progress. Intercompany system
options only affect new intercompany transactions, and are not retroactive to any transactions previously entered.
The system options are:

Intercompany Batch Numbering
The intercompany batch numbering option defines whether to use system generated or manual transaction batch
numbering. Choose one of the following options to create intercompany batch numbers:
System Generated: Generates intercompany batch numbers.
Manual: Lets you manually enter the batch number.
Intercompany Currency
Standardize transaction processing by selecting an intercompany currency. Intercompany transactions created in

the Intercompany module are always entered in this currency. This simplifies transaction processing, and eliminates
foreign conversion rate fluctuation risks. If you select an Intercompany currency, that currency is defaulted into
the Minimum Transaction Currency field. It overwrites any other currency in that field and the field cannot be
updated.
Minimum Transaction Amount
The minimum transaction amount represents a minimum threshold intercompany transaction amount. This amount
prevents the submission of immaterial transactions for small amounts that do not add value. To implement this rule,
you must first select an Intercompany currency. That currency is defaulted into the minimum transaction currency
for processing intercompany transactions. These two system options ensure that when comparing a transaction
259
amount to the minimum transaction amount, the two numbers are entered in the same currency, allowing for an
accurate comparison.
Conversion Rate Type
Select a conversion rate type that is used when transferring foreign currency intercompany transactions to General
Ledger, Receivables and Payables.
Note: The foreign currency intercompany transactions are not stored in the ledger currency in the
Intercompany module.
Allow Receiver to Reject Transaction
Use this system option to determine if receivers of intercompany transactions can reject transactions or not. For
example, if your company policy requires intercompany transactions be approved, but does not allow receivers to
reject the transactions, then you can set this system option to No.
Intercompany Calendar and Period Type
You can have an intercompany calendar that is separate from the general ledger calendar. This ensures that the
opening and closing of intercompany periods can be controlled separately from the general ledger calendar. You can
limit the creation of intercompany transactions by using the intercompany calendar to close periods by transaction
type. For example, you can prevent users from creating intercompany sales transactions beyond the 20th of each
month by closing the period for that transaction type on the 20th, but keep the period open for the other transaction
types until the 25th of the month..
Select a calendar from the available general ledger calendars in the list of values.
To update the intercompany calendar to use a different general ledger accounting calendar, the intercompany period
status for all intercompany transaction types must either be Never Opened or Closed.
The Period Type value is predefined from the selected accounting calendar and cannot be updated. It indicates the
type of period defined for that calendar.
Default Transaction Type
Select a transaction type that will default when new intercompany batches are created.
Summarize Distributions for Receivables Invoicing
Specify this option while setting up the Intercompany System Options by selecting a Yes or No. When you select
Yes, the provider distribution lines are summarized to generate one receivables invoice line. Intercompany passes the
Transaction description to the receivables invoice line. Note that the accounting of the receivables invoice still shows
each provider line separately.
When you select No for the Summarize Distribution for Receivables Invoicing option, each provider distribution line
is passed to Receivables to be generated as a separate receivables invoice line. In this case, Intercompany passes
each Provider Line description to the receivables invoice line.
Transactions Types: Explained

Use intercompany transaction types to manage the processing of intercompany transactions. When you create an
intercompany transaction you must select an intercompany transaction type.
260
The attributes of the transaction type determine how the intercompany transaction is processed. A transaction type helps you
to specify if a transaction is transferred directly to General Ledger or if it requires invoicing in Receivables and Payables. The
transaction type also determines if a transaction requires manual approval. Use the Manage Intercompany Transaction Types
task from the Setup and Maintenance work area to set up and maintain intercompany transaction types.
Intercompany Period Status: Explained

If you chose to use an intercompany calendar on your Systems Options, you can open and close periods by transaction type
on the Intercompany Period Status screen. Intercompany periods cannot be closed if there are transactions for that period
that are in the Sent, Error, or Received status. These transactions must be swept to the next period before closing the period.
Manage Intercompany Organizations
Managing Intercompany Organizations: Explained

The Manage Intercompany Organizations task allows you to define intercompany organizations and assign them to a legal
entity. The intercompany organization can act either as a provider or a receiver in an intercompany transaction.
Optionally assign a receivables and payables business unit to the organization if you require invoice generation. Invoices are
generated in Oracle Fusion Receivables and Oracle Fusion Payables for the business units specified.
You can initiate an intercompany transaction only for those organizations that you have access to. If a new organization is
added after the application is configured, the intercompany accountant or administrator should ensure that access is given to
the appropriate users.
An organization can be disabled if there are no open transactions, and all transactions for that organization are either in a New
or Complete status.
Legal Entity
Each intercompany organization must be associated with a legal entity, but you can associate more than one organization to
a legal entity.
Receivables and Payables Business Units

The available business units are those associated with the ledger to which the selected legal entity belongs. This assignment
is optional, but is needed when the organization is engaged in intercompany activity requiring intercompany invoices.
If you enter the wrong receivables or payables business units, you can still correct them as long as the organization is not yet
used in an intercompany transaction, regardless of the transaction status.
Define Invoicing Options
261
Customer and Supplier Assignment: Explained

The intercompany customer and supplier assignments are used to derive the customers and suppliers for intercompany
invoicing. You can associate a legal entity with either a customer account or supplier, or both. Each legal entity can only have
one customer account and one supplier assigned to it.
Customer Account
Assign a unique customer account to the legal entity of the organization that receives and approves intercompany
transactions. The customer account type must be Internal and it must have an active bill-to site with primary selected. Each
customer account can have multiple sites each associated with a different receivables business unit. This allows invoicing for
the customer in a variety of receivables business units.
Supplier
Assign a unique supplier to the legal entity of the organization that initiates intercompany transactions. The supplier must have
an active primary pay site. Each supplier can have multiple sites, each associated to a different payables business unit.
Intercompany Receivables Assignments: Explained

Use Oracle Fusion Intercompany to generate invoices for intercompany transactions.
Defining Receivables Assignments

Set up your receivables assignments by mapping an intercompany transaction type and a receivables business unit to the
receivables transaction type and receivables memo line. Oracle Fusion Receivables will use the receivables transaction type
and the receivables memo line to process intercompany transactions transferred to the receivables application. You can
configure specific receivables transaction types, and receivables memo lines, that you use for each intercompany transaction
type for a receivables business unit.
Manage Intercompany Balancing Rules
Intercompany Balancing Rules: Explained

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 is 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.
262
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.
Defining Intercompany Balancing Rules

You can define intercompany balancing rules at the following levels:
1. Primary balancing segment
2. Legal entity
3. Ledger
4. Chart of accounts
The rules are evaluated in the order shown above. For example, you can define a Primary Balancing Segment rule and a
Legal Entity level rule. If both rules can be used to balance a particular journal, the Primary Balancing Segment rule is used, as
it has a higher precedence.
You have flexibility in defining your intercompany balancing rules. You can have a simple setup in which you define one rule
for your chart of accounts. This rule is used for all intercompany balancing for all ledgers that use this chart of accounts.
Alternatively, you can have a more granular set of rules. For example, you can define a different rule for each legal entity and
one chart of accounts rule to cover any gaps in your rule definitions. You can gain even more granularity by defining rules for
specific journal and category combinations or intercompany transaction types.
Using Chart of Accounts Rules for Intercompany

Use chart of accounts rules for intercompany balancing. You have flexibility in defining your intercompany balancing rules with
the setup of a single chart of accounts rule to use for all ledgers that use this chart of accounts. When you create a chart of
accounts rule, you specify the chart of accounts, intercompany receivables, and intercompany payables accounts you want
to use, as well as the source and category. It is recommended that the intercompany receivables account be an asset type
account, and the intercompany payables account be a liability type account.
You can define rules that are applied to a specific source and category, such as Payables and Invoices, or a specific
intercompany transaction type, such as Intercompany Sales. Alternatively, you can choose to create rules for all sources and
categories by selecting the source of Other and the category of Other.
Intercompany Balancing will then evaluate the journal source and journal category combination in determining which rule to
use for balancing. The order of precedence is as follows.
Specific journal source and journal category
Specific journal source and journal category of Other
Journal source of Other and specific journal category
Journal source of Other and journal category of Other
Additional Intercompany Balancing and Clearing Company Options

Additional Intercompany Balancing and Clearing options are used to balance the second balancing segment or the third
balancing segment or both, when a transaction is unbalanced by one of these segments but is already balanced by the
primary balancing segment. This option is defined for a ledger but you can create rules for various Source and Category
combinations.
Additional Intercompany Balancing and Clearing options include the following settings:
Intercompany Receivables and Intercompany Payables accounts: You can use as the accounts as the template to
build balancing accounts for balancing segment 2 and balancing segment 3 when the journal is already balanced by
primary balancing segment.
263
Summarization options: You can choose to summarize lines within a legal entity before balancing lines are generated
by choosing the Summary Net option. Alternatively choose the Detail options so lines are not summarized before
balancing within a legal entity. Note that summarization always applies to balancing lines generated in a cross legal
entity scenario.
Clearing company options: Oracle recommends always setting clearing company options to handle many-to-many
journals as this avoids balancing failing during General Ledger Posting or Subledger Accounting Create Accounting
process.
Clearing Company Options

You can choose to set clearing company options to balance a many-to-many journal. Set the following options to manage
your clearing company balancing.
Clearing Company Condition: Choose when to use a clearing company.
Use clearing company only for intracompany journals.

Use clearing company for all many-to-many journals.
Error out if many-to-many journal. This is the default value for this option.
Clearing Company Source: Choose how the clearing company value is derived for your balancing lines, from the
following options:
Default clearing balancing segment value.

Manually entered clearing balancing segment value. Note that if you select Manually entered clearing
balancing segment value, you will need to manually enter a value in the create journals screen. This option will
not work for subledger accounting entries as they do not have a field on the user interface to enter this value.
Clearing Company Value: If you selected Default clearing balancing segment value for Source, you must select a
primary balancing segment value in this field. This is the value used to balance your intracompany or many-to-many
journals.
Intercompany Balancing Rules: Examples

This topic provides examples of intercompany balancing rules and the intercompany balancing lines generated. These rules
are used to generate the accounts needed to balance journals that are out of balance by legal entity or primary balancing
segment values.
Intercompany Balancing Rules Precedence

In this example the legal Entity InFusion Textiles intercompany manufacturing activities are tracked separately from its non-
manufacturing activities. In order to achieve this legal entity level rules are defined specifically between the legal entity InFusion
Textiles and the two manufacturing legal entities, InFusion Products (East) and InFusion Products (West). A chart of accounts
rule is created to cover all other intercompany activities.
Setup
InFusion USA Chart of Accounts
Segment Name Company (CO) Cost Center (CC) Division (DIV) Account (ACCT) Intercompany (IC)
Segment Qualifier Primary Balancing Second Balancing Third Balancing Account Intercompany
Segment Segment Segment Segment
264
Segment Name Company (CO) Cost Center (CC) Division (DIV) Account (ACCT) Intercompany (IC)

Ledger, Legal Entity, Primary Balancing Segment Value Assignments
Ledger Legal Entity Primary Balancing Segment Value
InFusion USA InFusion Farms 3100, 3200, 3300, 3400, 3500

InFusion USA InFusion Textiles 4000

InFusion USA InFusion Products (East) 5000

InFusion USA InFusion Products (West) 6000

InFusion USA 1000, 9000

Chart of Accounts Rule
Rule Number Chart of AR Account AP Account Source Category Transaction Type

Accounts
1 InFusion 1000 - 000 - 1000 - 000 - Other Other None

USA Chart of 0000 - 13050 - 0000 - 21050 -
Accounts 0000 0000

Legal Entity Level Rule
Rule No. From Legal To Legal AR Account AP Account Source Category Transaction
Entity Entity Type
2 InFusion InFusion 1000 - 000 - 1000 - 000 - Other Other None

Textiles Products 0000 - 13020 0000 - 21020
(West) - 0000 - 0000

3 InFusion InFusion 1000 - 000 - 1000 - 000 - Other Other None

Textiles Products 0000 - 13030 0000 - 21030
(East) - 0000 - 0000

Journal Balancing
Journal before Balancing
Line Line Type Legal CO CC DIV ACCT IC Debit Credit

Entity
1 Expense InFusion 3100 100 1200 52330 0000 150

Farms

265
Line Line Type Legal CO CC DIV ACCT IC Debit Credit

Entity

Products
(East)


Products
(West)

4 Liability InFusion 4000 500 1300 40118 0000 650

Textiles

Journal Balancing
Journal after Balancing
Uses Line Line Legal CO CC DIV ACCT IC Debit Credit

Rule Type Entity

Farms


Products
(East)


Products
(West)

4 Liability InFusion 4000 500 1300 40118 0000 650

Textiles

1 5 IC AR InFusion 4000 500 1300 13050 3100 150

Textiles

1 6 IC AP InFusion 3100 100 1200 21050 4000 150

Farms

3 7 IC AR InFusion 4000 500 1300 13030 5000 200

Textiles

1 8 IC AP InFusion 5000 100 1200 21050 4000 200

Products(East)

2 9 IC AR InFusion 4000 500 1300 13020 6000 300

Textiles

266
Uses Line Line Legal CO CC DIV ACCT IC Debit Credit

Rule Type Entity
1 10 IC AP InFusion 6000 200 1300 21050 4000 300

Products
(West)

Using Chart of Accounts Rules for Intercompany Balancing:

Examples
The following are some examples using chart of accounts rules for Intercompany balancing.
One-to-One Balancing: Example

In these scenarios, you choose to track intercompany balancing for companies with values 3000, and 4000 to separate
intercompany accounts. You will set up specific rules at the primary balancing segment value level for this. A chart of
accounts rule is created for all other intercompany activity.
Setup
Segment Qualifier Primary Balancing Balancing Segment Segment Segment Intercompany

Segment 2 Segment
Segment Name Company Cost Center Product Account Intercompany

(CO) (CC) (PROD) (ACCT) (IC)

Ledger, Legal Entity, and Primary Balancing Segment Value Assignments
InFusion USA InFusion Farms 3000


InFusion USA InFusion Production 5000


Rule No. 1: Chart of Accounts Rule

Chart of Accounts: InFusion USA
Source: Other
Category: Other
Transaction Type: None
267
IC Account CO CC PROD ACCT IC
AR Account 1000 000 0000 13010 0000

AP Account 1000 000 0000 21010 0000

Rule No. 2: Primary Balancing Segment Rules

From Ledger and To Ledger: InFusion USA
From Primary Segment Value: 3000
To Primary Segment Value: 4000
Source: Other
Category: Other
AR Account 1000 000 0000 13011 0000

AP Account 1000 000 0000 21011 0000

Rule No. 3: Primary Balancing Segment Rule

Source: Other
Category: Other
AR Account 1000 000 0000 13012 0000

AP Account 1000 000 0000 21012 0000


Source: Other
Category: Other
268
AR Account 1000 000 0000 13013 0000

AP Account 1000 000 0000 21013 0000


Source: Other
Category: Other
AR Account 1000 000 0000 13014 0000

AP Account 1000 000 0000 21014 0000

Journal No. 1: One-to-One Legal Entity Journal

Source: Manual
Category: Adjustment
Line Account Debit Credit Description Uses Rule No.
1 5000- 100- 1200- 150

52330- 0000

2 4000- 110- 1200- 150

41111- 0000

3 5000- 100- 0000- 150 Intercompany 1

21010- 4000 Balancing Line

4 4000- 110- 0000- 150 Intercompany 5


Journal No. 2: One-to-Many Legal Entity with Multiple Primary Balancing Segment Values for a legal Entity
Note: Balancing summarizes across a legal entity and first performs intercompany balancing using the lowest
primary balancing segment value within the legal entity. In the following example, 1000 and 9000 are assigned to
the same legal entity so first 1000 is used to perform intercompany balancing. Then balancing is performed for
1000 and 9000, that is, the primary balancing segments within a legal entity.
269
Source: Manual
Category: Adjustment
1 3000-100-1200- 150
52330- 0000

2 4000-110-1200- 140
41111- 0000

3 1000-120-1000- 30
52345-0000

4 9000-130-2000- 40
52330-0000

5 3000- 100- 0000- 140 Intercompany 2


6 4000- 110- 0000- 140 Intercompany 4


7 3000-100-0000- 10 Intercompany 1
21010-1000 Balancing Line

8 1000-120-0000- 10 Intercompany 1
13010-3000 Balancing Line

9 1000-120-0000- 40 Ledger 1
21010-9000 Intercompany
Balancing Line

10 9000-130-0000- 40 Ledger 1
13010-1000 Intercompany
Balancing Line

Many-to-Many Balancing: Example

In this section, we look at many-to-many primary balancing segment value journals and many-to-many legal entity journals.
For many-to-many primary balancing segment journals, a clearing company is used if it is available. If no clearing
company is available, balancing is done using a default rule that matches the largest debit with largest credit and so
on.
For many-to-many legal entity journals, a clearing company is required to balance a journal.
Setup
270

Segment 2 Segment


InFusion USA InFusion Farms 3111, 3121, 3199, 3899



InFusion USA InFusion Sales 3251

Many-to-Many Primary Balancing Segment Values Within One Legal Entity Balanced
Using a Clearing Company: Example
Rule No. 1: Chart of Accounts

Source: Auto copy
Category: Accrual
AR Account 3111 000 0000 11020 0000

AP Account 3251 000 0000 21021 0000


To Primary Segment Value: All other
Source: Auto copy
Category: Accrual
271
AR Account 3111 000 0000 11018 0000

AP Account 3111 000 0000 21030 0000

Additional Intercompany Balancing and Clearing Options
Source: Auto copy

Category: Accrual
Journal Lines
1 3111-000-000- 10
52330-0000

2 3121-000-000- 20
52330-0000

3 3199-000-000- 14
52330-0000

4 3899-000-000- 16
52330-0000

5 3199-000-000- 14 Ledger 1 and clearing

11020-3371 Intercompany company value
balancing line 3371


balancing line 3371


balancing line 3371


balancing line 3371


balancing line 3371


balancing line 3371

272

balancing line 3371


balancing line 3371

90 90

Many-to-Many Legal Entity with a Clearing Company: Example

Source: Other
Category: Other
AR Account 3111 000 0000 11020 0000

AP Account 3251 000 0000 21021 0000


Source: Auto copy
Category: Accrual
Condition Source Value
Use clearing company for all many-to-many Default clearing balancing segment value 3899
journal

Journal Lines
1 3111-000-000- 10
52330-0000

2 3311-000-000- 20
52330-0000

3 3211-000-000- 14
52330-0000
273

4 3251-000-000- 16
52330-0000


21021-3899 Intercompany company 3899
balancing line


balancing line


balancing line


balancing line


balancing line


balancing line


balancing line


balancing line

90 90

Many-to-Many Primary Balancing Segment within a Legal Entity and No Clearing

Company Specified: Example
The default rule is used which applies largest debit to largest credit and so on.

Source: Other
Category: Other
274
AR Account 3111 000 0000 13011 0000

AP Account 3111 110 0000 21081 0000

Balancing will take the line with the largest debit which is line number 2 and balance it against the largest credit which is line
4. Then it takes the balance of line 2 and balance this against line 3 and so on.
Journal Lines
Line Account Debit Credit Description Notes
1 3111-000-000- 10
52330-0000

2 3121-000-0000- 20
52330-0000

3 3199-000-0000- 14
52330-0000

4 3899-000-0000- 16
52330-0000

5 3899-000-0000- 16 Ledger First, Line 4, the

13011-3121 Intercompany largest credit is
balancing line balanced against
line 2, the largest
debit

6 3121-000-0000- 16 Ledger First, Line 4, the

21081-3899 Intercompany largest credit is
balancing line balanced against
line 2, the largest
debit

7 3199-000-0000- 4 Ledger Remainder of line 2

13011-3121 Intercompany is balanced against
balancing line line 3, which is the
next largest credit
amount

8 3121-000-0000- 4 Ledger Remainder of line 2

21081-3199 Intercompany is balanced against
balancing line line 3, which is the
next largest credit
amount

9 3199-000-0000- 10 Ledger Finally, line 1 is

13011-3111 Intercompany balanced against
balancing line the remainder of line
3.

275
Line Account Debit Credit Description Notes
10 3111-000-0000- 10 Ledger Finally, line 1 is

21081-3199 Intercompany balanced against
balancing line the remainder of line
3.

60 60

Additional Intercompany Balancing and Clearing Options: Examples

This topic provides examples of additional intercompany balancing and clearing options, the setup required, and the journal
before and after balancing.
Additional Intercompany Balancing Segment Options

In this scenario the enterprise has the second balancing segment and the third balancing segment enabled for its chart of
accounts. The journal is balanced by primary balancing segment but is out of balance by the second balancing segment and
the third balancing segment.
Setup
Segment Primary Second Third Balancing Product Account Intercompany

Qualifier Balancing Balancing Segment Segment
Segment Segment
Segment Name Company Cost Center Division Product Account Intercompany

(CO) (CC) (DIV) (PROD) (ACCT) (IC)

Ledger, Legal Entity, Primary Balancing Segment Value Assignments


InFusion USA InFusion Products (East) 5000

InFusion USA InFusion Products (West) 6000


276
Rule Number Ledger Source Category Transaction Type AR Account AP Account
1 InFusion USA Other Other None 1000 - 000 -200 1000 - 000 -
- 0000 - 13010 - 100- 0000 -
0000 21010 - 0000

Journal Balancing
Journal Before Balancing
Line Line Legal CO CC DIV PROD ACCT IC Debit Credit

Type Entity
1 Expense InFusion 3100 100 110 1200 52330 0000 150

Farms

2 Liability InFusion 3100 500 330 1300 40118 0000 150

Farms

Journal Balancing
Journal after Balancing
Line Legal CO CC DIV PROD ACCT IC Debit Credit Uses

Entity Rule
1 InFusion 3100 100 110 1200 52330 0000 150

Farms

2 InFusion 3100 500 330 1300 40118 0000 150

Farms

3 InFusion 3100 100 110 0000 21010 0000 150 1

Farms

4 InFusion 3100 500 330 0000 13010 0000 150 1

Farms

Related Topics
Additional Intercompany Balancing and Clearing Options: Explained
Manage Intercompany Allocations
277
Intercompany Allocations: How They Are Processed

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.
Settings That Affect Intercompany Allocations

The following table describes the parameters for the Generate Intercompany Allocations and Generate General Ledger
Allocations processes.
Parameter Generate Intercompany Allocation Process Generate General Ledger Allocations Process
Rule or Rule Set Select the rule or rule set to create allocation Select the rule or rule set to create allocation
calculations. calculations.

Intercompany Transaction Type Select the type of transactions that are Not Applicable
grouped together and are identified by the
type of intercompany transaction.

Post Allocations Not Applicable Select to book amounts spread from one
account to another.

Process Cross-Ledger Allocations Not Applicable Process allocations that run across more
than one ledger.

Use Intercompany Accounts Not Applicable Post allocation transactions to the

intercompany accounts determined by the
FUN application programming interface (API).

This option appears only for cross-ledger
allocations.

Use Suspense Account Not Applicable Post allocation transactions to the suspense
account, if one exists. Cross-ledger
allocations are processed using Journal
Import.

This option appears only for cross-ledger
allocations.

How Intercompany Allocations are Processed Using the Generate Intercompany

Allocations Process
The Generate Intercompany Allocations process:
1. Calls the FUN API to create intercompany transactions and process the allocation lines.
2. Extracts the allocation lines from the General Ledger interface table and populates the Intercompany interface tables.
3. Removes the allocation lines from the General Ledger interface table upon successfully populating the Intercompany
interface tables.
278
4. Generates a batch by provider legal entity and groups lines by receiver legal entity so that there is one transaction
per legal entity.
5. Uses the entered currency amounts for populating the Intercompany interface tables.
How Intercompany Allocations are Processed Using the Generate General Ledger
Allocations Process
The Generate General Ledger Allocations process:
1. Uses Journal Import to process the intercompany allocations if you select to post allocations for single ledger
journals.
2. Calls the FUN API to generate the intercompany accounts if the rule or rule set contains cross-ledger lines. You
select to process cross-ledger allocations using the intercompany accounts.
Note: If you select to process cross-ledger allocations using the suspense account, Journal Import
processes the allocation lines.
3. Provides the intercompany receivables or intercompany payables account lines for cross-ledger allocations going to
General Ledger.
4. Populates the General Ledger interface table with the appropriate line for each ledger of the cross-ledger allocation.
Generating Intercompany Receivables and Intercompany Payables

Accounts for Manual Transactions: Examples
The receivables (AR) and payables (AP) accounts for manual intercompany transactions are generated automatically by
Oracle Fusion Intercompany. Enter distributions for the transaction and intercompany generates the receivables and payables
accounts, based on the intercompany balancing rules setup.
Intercompany uses the transaction type, provider legal entity, receiver legal entity, primary balancing segment value of the first
provider distribution and the primary balancing segment value of the first receiver distribution to ascertain which rule to apply.
Intercompany then uses the rule, and the balancing segment values of the first provider distribution to build the intercompany
receivable account combination for the provider side of the transaction. Similarly, intercompany builds the intercompany
payables account for the receiver side of the transaction, based on the first receiver distribution account.
Intercompany will evaluate the rules in the following order.
1. Primary balancing segment rules

2. Legal entity level rules
3. Ledger level rules
4. Chart of accounts rules
If there is no matching rule at the lower levels, then intercompany will use the chart of accounts rule. It is therefore
recommended that you set up a chart of accounts rule for every chart of accounts structure you have. This will ensure that
intercompany will always find a rule to use to generate the intercompany receivables and intercompany payables accounts for
transactions.
Intercompany will then evaluate the transaction type in determining which rule to use to generate the receivables or payables
account. A rule with a specific transaction type takes precedence over a rule defined for the All Other transaction type.
279
Generating Intercompany Receivables and Intercompany Payables Accounts for Manual

Transactions Example
In this scenario you choose to track your intercompany sales for the farming and textile companies separately from other
intercompany activities. Separate intercompany accounts are used for these two companies. A chart of accounts rule is
created for all other intercompany activity.
Setup

Segment 2 Segment






Chart of Accounts Rule
Rule No. 1

Source: None
Category: None
Transaction Type: All Other
AR Account 1000 000 0000 13020 0000

AP Account 1000 000 000 21020 000

Legal Entity Rules
280
Rule No. 2
From Legal Entity: InFusion Farms
To Legal Entity: InFusion Textiles
Source: None
Category: None
Transaction Type: Intercompany (IC) Sales
AR Account 1000 000 0000 13011 0000

AP Account 1000 000 0000 21011 0000

Rule No. 3
From Legal Entity: InFusion Farms
To Legal Entity: InFusion Production
Source: None
Category: None
AR Account 1000 000 0000 13012 0000

AP Account 1000 000 0000 21012 0000

Rule No. 4
From Legal Entity: InFusion Textiles
To Legal Entity: InFusion Farms
Source: None
Category: None
AR Account 1000 000 0000 13013 0000

AP Account 1000 000 0000 21013 0000
281

Rule No. 5
From Legal Entity: InFusion Textiles
To Legal Entity: InFusion Production
Source: None
Category: None
AR Account 1000 000 0000 13014 0000

AP Account 1000 000 0000 21014 0000

Intercompany Accounts Generated for Intercompany Debit Transactions
Provider Distribution and Intercompany Receivable Account
This table displays the Provider side of the transaction.
Transaction Transaction Type Provider LE Receiver LE Provider Provider AR Uses Rule No.
Distribution Account
Generated
1 IC Sales InFusion Farms InFusion Textiles 3100- 100- 3100- 100- 2

1200- 52330- 0000- 13011-
0000 4000

2 IC Adjustments InFusion Farms InFusion Textiles 3100- 100- 3100- 100- 1

1200- 52330- 0000- 13020-
0000 4000

3 IC Sales InFusion InFusion Farms 5000- 120- 5000- 120- 1

Production 1300- 52345- 0000- 13020-
0000 3200

Receiver Distribution and Intercompany Payable Account
This table displays the Receiver side of the transaction.
Transaction Transaction Type Receiver LE Provider LE Receiver Receiver Uses

Distribution AR Account
Generated
1 IC Sales InFusion Textiles InFusion Farms 4000- 110- 4000- 110- 4

1200- 41111- 0000- 21013-
0000 3100
282
Transaction Transaction Type Receiver LE Provider LE Receiver Receiver Uses

Distribution AR Account
Generated

2 IC Adjustments InFusion Textiles InFusion Farms 4000- 110- 4000- 110- 1

1200- 41111- 0000- 21020-
0000 3100

3 IC Sales InFusion Farms InFusion 3200- 130- 3200- 130- 3

Production 1200- 41112- 0000- 21012-
0000 5000

Intercompany Accounts Generated for Intercompany Credit Transactions
Provider Distribution and Intercompany Receivable Account
Transaction Transaction Type Provider LE Receiver LE Provider Provider AR Uses Rule No.
Distribution Account
Generated
4 IC Sales InFusion Farms InFusion Textiles 3100- 100- 3100- 100- 2

0000- 52330- 0000- 13011-
0000 4000

5 IC Adjustments InFusion Farms InFusion Textiles 3100- 100- 3100- 100- 1

1200- 52330- 0000- 13020-
0000 4000

6 IC Sales InFusion InFusion Farms 5000- 120- 5000- 120- 1

Production 1300- 52345- 0000- 13020-
0000 3200

Receiver Distribution and Intercompany Payable Account
This table displays the Receiver side of the transaction.
Transaction Transaction Type Receiver LE Provider LE Receiver Receiver Uses Rule No.
Distribution AP Account
Generated
4 IC Sales InFusion Textiles InFusion Farms 4000- 100- 4000- 100- 4

1200- 41111- 0000- 21013-
0000 3100

5 IC Adjustments InFusion Textiles InFusion Farms 4000- 100- 4000- 100- 1

1200- 41111- 0000- 21020-
0000 3100

6 IC Sales InFusion Farms InFusion 3200- 130- 3200- 130- 3

Production 1200- 41112- 0000- 21012-
0000 5000

283
Cross-Ledger Allocations: How They Are Processed

Journals can be for a single ledger or multiple ledgers within a ledger set. When you create cross-ledger allocations,
they must have only one debit or one credit line. The other side of the journal can have as many lines as you need. The
process adds an intercompany receivables or intercompany payables line to each ledger's journal so it can be posted. The
intercompany receivables and payables accounts are generated based on the intercompany balancing rules.
Settings That Affect Allocations

General Ledger Allocations
For the Generate General Ledger Allocations process, set the following parameters to create allocation journals:
Parameter Description
Rule or Rule set Select the rule or rule set to create allocation lines.

Post Allocations Select to automatically post allocation journals after they have been imported.

Intercompany Allocations
For the Generate Intercompany Allocations process, set the following parameters to create intercompany allocations:
Parameter Description
Rule or Rule set Select the rule or rule set to create allocation calculations.

Intercompany Transaction Type Select the transaction type to be used to create the intercompany transactions.

How Allocations are Processed Using the Generate General Ledger Allocations Process
The Generate General Ledger Allocations process creates journals from the allocation lines generated by the rule or rule set.
Journals can be for a single ledger or multiple ledgers. If the allocation lines span multiple ledgers each journal is balanced
using the intercompany balancing rules. When you create cross-ledger allocation rules each rule must only result in either
one debit line or one credit line with as many lines on the other side as you need. The process then adds intercompany
receivables or intercompany payables lines to cross-ledger journals so they can be imported into the relevant ledger.
How Allocations are Processed Using the Generate Intercompany Allocations Process
The Generate Intercompany Allocations process creates an intercompany batch, transactions, provider distributions
and receiver distributions from the allocation lines generated by the rule or rule set. The process creates intercompany
transactions in the entered currency of the allocation lines.
The Intercompany uses the primary balancing segment values, the balancing segment to legal entity assignments and the
intercompany organizations set up to create transactions from your allocation.
You can create intercompany transactions from either single ledger or cross-ledger allocation lines. To successfully process
cross-ledger allocations you must have either one debit line or one credit line per allocation but as many lines as required for
284
the other side. The single debit or single credit line forms the provider side of the transaction and the lines on the other side
form the receiver side of the transaction.
Cross-Ledger Allocations: Examples

You can process cross-ledger allocations by choosing to create them as general ledger journals or intercompany
transactions. Choose to generate journals from an allocation rule or rule set by submitting the Generate General Ledger
Allocations process. This process provides options to balance any cross-ledger journal with a receivables or payables line.
You can also choose to create intercompany transactions from an allocation rule or rule set by submitting the Generate
Intercompany Allocations process. This creates intercompany transactions that optionally can be routed to Receivables for
invoice generation.
The following scenario illustrates generating balancing journal entries as well as intercompany transactions for cross-ledger
allocations.
Intercompany Allocation Entries

At month end the accountant allocates a portion of any centrally incurred expenses across all organization units that
contribute to, or benefit from, that expenditure, based upon a calculation that represents a reasonable allocation of how
that expense should be split. By doing this allocation, the Income Statement or Profit and Loss statement for each of those
organization units shows a fair representation of its share of operational costs.
In many cases, allocations only take place between departments within one subsidiary, but there may be other costs that are
shared between subsidiaries on a regular basis.
For example, marketing expense is incurred within a central corporate ledger, and is allocated to the United States (US),
Canadian (CA), and United Kingdom (UK) organizations based on sales volume. These organizations are separate legal
entities with their own separate ledgers. The US organization bears 50% of the cost and the CA and UK organizations each
bear 25% of the cost.
The Marketing Costs allocation rule is set up to generate the following allocation lines.
Ledger Account Debit Credit Description
InFusion USA 3111-110-0000-41110-0000 USD 500 Allocation Line

InFusion UK 3411-000-0000-52330-0000 USD 250 Allocation Line

InFusion Canada 3511-120-0000-52330-0000 USD 250 Allocation Line

The intercompany balancing rules are set up to use the following accounts.
Receivables Account: 3000-000-0000-13011-0000
Payables Account: 3000-000-0000-21081-0000
Generate General Ledger Allocations Using Intercompany Accounts

Submit the Generate General Ledger Allocations process and choose your Rule or Rule Set. Select Process Cross-Ledger
Allocations and Use Intercompany Accounts options to use intercompany balancing rules to generate the receivables and
payables accounts required to balance cross-ledger allocation journal lines.
285
The following journals are created for the Marketing Costs allocation rule.
InFusion USA journal after cross-ledger balancing:
InFusion USA 3111-110-0000-41110-0000 USD 500 Allocation Line

InFusion USA 3111-110-0000-13011-3411 USD 250 Cross-Ledger

Intercompany Allocation
with Ledger InFusion UK

InFusion USA 3111-110-0000-13011-3511 USD 250 Cross-Ledger

with Ledger InFusion
Canada

InFusion UK journal after cross-ledger balancing:
InFusion UK 3411-000-0000-52330-0000 USD 250 Allocation Line

InFusion UK 3411-000-0000-21081-3111 USD 250 Cross-Ledger

USA

InFusion Canada journal after cross-ledger balancing:
InFusion Canada 3511-120-0000-52330-0000 USD 250 Allocation Line

InFusion Canada 3511-120-0000-21081-3111 USD 250 Cross-Ledger

USA

Generate Intercompany Allocations

Submit the Generate Intercompany Allocations process to create intercompany transactions. If you need invoices for your
allocations choose an intercompany transaction type that requires invoicing so the intercompany transactions get routed to
Receivables for invoice generation.
Ledger, Legal Entity, and Primary Balancing Segment assignments are set up as follows:
Ledger Legal Entity Primary Balancing Segment
InFusion USA USA Corp 3111
286
Ledger Legal Entity Primary Balancing Segment

InFusion UK UK Corp 3411

InFusion Canada Canada Corp 3511

Intercompany organizations are set up as follows.
Intercompany Organization Legal Entity
USA Sales USA Corp

UK Sales UK Corp

Canada Sales Canada Corp

The following intercompany transactions are created for the Marketing Costs allocation rule.
Batch 101:
Provider Transaction Number Distribution Number Distribution account Debit Credit
USA Sales 1 1 3111-110-0000-41110-0000 USD 250

2 3111-110-0000-13011-3411
USD 250

2 1 3111-110-0000-41110-0000 USD 250

2 3111-110-0000-13011-3511
USD 250

Receiver Transaction Number Distribution Number Distribution account Debit Credit
UK Sales 1 1 3411-000-0000-52330-0000
USD 250

2 3411-000-0000-21081-3111 USD 250

Canada Sales 2 1 3511-120-0000-52330-0000

USD 250

2 3511-120-0000-21081-3111 USD 250

287
FAQs for Manage Intercompany Allocations

How can I use social networking to discuss intercompany allocation adjustments with
cost center owners?
Use the Social link on the Intercompany Transactions work area to invite others to a conversation to address the adjustments.
For example, the monthly intercompany allocation of administration costs changed substantially to more accurately reflect
resource usage. You need the cost center owners to validate their intercompany allocation.
From the Intercompany Transactions work area:
1. Search for the intercompany transaction.

2. Click Social to open Oracle Social Network. Click the Share button, or click Join if collaboration has already been
initiated.
3. Create a new related conversation.
4. Invite all of the cost center owners to join the conversation.
5. Upload the allocation spreadsheet for the cost center owners' review.
The cost center owners can post questions and because the other cost center owners are members, they can see your
responses to the questions. Each cost center owner validates their intercompany allocation in the conversation itself, which
creates a lasting record.
Related Topics
Intercompany Organization Configuration Examples
Intercompany Organization Configuration: Example

This topic provides examples of intercompany organizations with various options.
The intercompany module allows you to create intercompany transactions that have an invoice associated with them. If you
require invoices for your intercompany transactions, you must complete the following additional intercompany setup.
Associate your provider intercompany organization to a receivables business unit and your receiver intercompany
organization to a payables business unit.. The invoice for your intercompany transaction will be raised in the
receivables business unit and it will be recorded in the payables business unit.
Associate a supplier to your provider legal entity and a customer account to your receiver legal entity.
Note: The Intercompany module leverages the Invoicing and Customer features in Receivables to
generate invoices for intercompany transactions. The Supplier feature in Procurement and the Payables
Invoicing feature are leveraged to record the invoice in Payables.
288
Intercompany Organization Configuration: Example

In this example, Vision Corporation has two legal entities, Vision Operations legal entity and Vision Services legal entity which
provide goods and services to each other. The company has a requirement to record intercompany activity between these
legal entities. In some circumstances, Vision Operations legal entity provides goods to Vision Services legal entity and in other
circumstances Vision Services legal entity provides services to Vision Operations legal entity. Therefore it is necessary for
each of these legal entities to be able to invoice the other legal entity as well as record a payables invoice received from the
other legal entity.
The following figure illustrates the Intercompany Organization Setup.
Receivables
Business Unit
Operations AR
Intercompany Legal Entity
Organization Vision
Vision Operations Legal
Operations Entity
Payables
Business Unit
Operations AP
Receivables
Business Unit
Services AR
Organization Vision Services
Vision Services Legal Entity
Payables
Business Unit
Services AP
The following figure illustrates the Customer And Supplier assignments.
289
Customer
Account 123
Legal Entity
Vision Operations
Legal Entity
Supplier 123
Customer
Account 456
Legal Entity
Vision Services
Legal Entity
Supplier 456
The following table describes Vision Operations Intercompany Organization as a Provider.
Type Intercompany Legal Entity Receivables Payables Business Comments

Organization Business Unit Unit
Provider Vision Operations Vision Operations Operations AR Operations AP AR invoice will

Legal Entity be created in
Operations AR
business unit which
is the receivables
business unit of the
Provider. Customer
will be the one
assigned to Vision
Services Legal
Entity.

Receiver Vision Services Vision Services Services AR Services AP

Legal Entity AP Invoice will be
created in Services
AP business
unit which is the
Payables business
unit of the Receiver.
Supplier will be the
one assigned to
Vision Operations
Legal Entity.

The following table describes the required Customer Supplier Assignments setup.
290
Type Legal Entity Customer Account Customer Account Supplier Supplier Site
Provider Vision Operations Supplier 123 Supplier 123 must

Legal Entity have a site with
Primary Pay site
purpose enabled
in Services AP
business unit

Receiver Vision Services Customer Account Customer Account

Legal Entity 456 456 must have a Bill
To site in Operations
AR business unit.

The table describes the Invoices created.
Type Legal Entity Invoices
Provider Vision Operations Legal Entity AR Invoice 101 raised for Customer Account
456 in Operations AR business unit.

Receiver Vision Services Legal Entity AP Invoice 101 recorded for Supplier 123 in
Services AP business unit.

Scenario
The following table describes the Vision Operations Intercompany Organization as a Receiver.

Receiver Vision Operations Vision Operations Operations AR Operations AP AP Invoice will

Legal Entity be created in
Operations AP
business unit which
is the payables
Receiver. Supplier
will be the one
assigned to Vision
Services Legal Entity

Provider Vision Services Vision Services Services AR Services AP AR invoice will be

Legal Entity created in Services
AR business
unit which is the
receivables business
unit of the Provider.

Customer will be
the one assigned to
Vision Operations
Legal Entity.

291
The following table describes the required Customer Supplier Assignments setup.
Type Legal Entity Customer Account Customer Site Supplier Supplier Site
Receiver Vision Operations Customer Account Customer Account

To site in Services
AR business unit.

Provider Vision Services Supplier 456 Supplier 456 must

Primary Pay site
purpose enabled
in Operations AP
business unit

The table describes the Invoices created.
Type Legal Entity Invoices
Receiver Vision Operations Legal Entity AP Invoice 102 recorded for Supplier 456 in
Operations AP business unit

Provider Vision Services Legal Entity AR Invoice 102 raised for Customer Account
123 in Services AR business unit

Intracompany Organization Configuration: Example

The following example explains Intracompany Invoices.
In this example, Vision Corporation has one legal entity, Vision Operations Legal Entity which is associated with multiple
intercompany organizations within the corporate structure. In the configuration shown below Vision Operations intercompany
organization provides goods to Vision Administration intercompany organization and in other circumstances Vision
Administration provides services to Vision Operations. The business has a requirement for each of these intercompany
organizations to be able to invoice the other as well as record a payables invoice received from the other intercompany
organization.
292
Intercompany Organizations Setup

The following figure illustrates the Intercompany Organizations Setup.
Receivables
Business Unit
Operations AR
Organization Vision
Vision Operations Legal
Operations Entity
Payables
Business Unit
Operations AP
Receivables
Business Unit
Intercompany Operations AR
Legal Entity
Organization
Vision Operations
Vision
Legal Entity
Administration
Payables
Business Unit
Administration
AP
The following figure illustrates the Customer And Supplier assignments.
293
Customer
Account 456
Legal Entity
Vision Operations
Legal Entity
Supplier 123
The following table describes the Intracompany Organization as a Provider:

Provider Vision Operations Vision Operations Operations AR Operations AP AR invoice

Legal Entity is created in
Operations AR
business unit which
is the receivables
Provider. Customer
is the one assigned
to Vision Operations
Legal Entity.

Receiver Vision Vision Operations Operations AR Administration AP AP Invoice

Administration Legal Entity is created in
Administration AP
business unit which
is the payables
Receiver. Supplier
is the one also
assigned to Vision
Operations Legal
Entity

The following table describes the required Customer Supplier Assignments Setup.
294
Type Legal Entity Customer Account Customer Site Supplier Supplier Site
Provider Vision Operations Supplier 123 Supplier 123 must

Primary Pay site
purpose enabled in
Administration AP
business unit

Receiver Vision Operations Customer Account Customer Account

To site in Operations
AR business unit.

The following table describes the Invoices created.
Type Intercompany Organization Legal Entity Invoice
Provider Vision Operations Vision Operations Legal Entity AR Invoice 101 raised for
Customer Account 456 in
Operations AR business unit

Receiver Vision Administration Vision Operations Legal Entity AP Invoice 101 recorded for
Supplier 123 in Administration
AP business unit

295
296
Implementing Enterprise Structures and General Ledger General Ledger Options
9 General Ledger Options
Ledger Sets: Examples

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.
Data Access Set Security: Overview

Data Access Sets secure access to ledgers, ledger sets, and portions of ledgers using primary balancing segment values.
If you have primary balancing segment values assigned to a legal entity, then you can use this feature to secure access to
specific legal entities.
You can combine ledger and ledger set assignments in single data access sets if the ledgers share a common chart of
accounts and calendar. If you have primary balancing segment values assigned to a legal entity within the ledger, then
you can use data access sets to secure access to specific legal entities. You can also secure access to primary balancing
segments assigned directly to the ledger.
297
When a ledger or ledger set is created, a data access set for that ledger or ledger set is automatically created, giving full read
and write access to those ledgers. You can also manually create data access sets to give read and write access, or read-only
access to entire ledgers or portions of the ledger represented as primary balancing segment values.
This figure shows how data access sets consist of an access set type and an access level.
Data Access Set
Access Set
Access Level
Type
Primary
Full Ledger Balancing Read Only Read and Write
Segment Value
The Full Ledger access set type provides access to the entire ledger or ledger set. This could be for read-only access or
both read and write access to the entire ledger.
The Primary Balancing Segment Value access set type provides access to one or more primary balancing segment values
for that ledger. This access set type security can be specified by parent or detail primary balancing segment values. The
specified parent value and all its descendants, including middle level parents and detail values are secured. You can specify
read only, read and write access, or combination of both, for different primary balancing segment values for different ledgers
and ledger sets.
Data Access Set Security: Examples

This example shows a data access set that secures access by using primary balancing segment values that correspond to
legal entities.
298
Scenario
This figure shows a data access set for the US Financial Services Ledger. The access set type is Primary Balancing Segment
Value, with each primary balancing segment values representing different legal entities. One access set assignment provides
read-only access and the other, read and write access to the corresponding legal entities' primary balancing segment value.
US Financial Services Ledger
Access Level Read and

Read Only
Write
Primary 131 101 102

Balancing Insurance Banks Capital
Segment
Values
View Journals View, Create, Post Journals

Actions View Balances View and Update Balances
View and Run Reports View and Run Reports
Read-only access has been assigned to primary balancing segment value 131, which represents the Insurance legal entity.
Read and write access has been assigned to the other two primary balancing segment values 101 and 102, which represent
the Banks and Capital legal entities.
For this data access set, the user can:
View the journals, balances, and reports for primary balancing segment value 131 for the Insurance legal entity.
Create journals and update balances, as well as view journals, balances and reports for primary balancing segment
value 101 and 102 for legal entities Banks and Capital.
Note: In financial reporting, the list of ledgers isn't secured by data access sets when viewing a report in
Preview mode. Users can view the names of ledgers they don't have privileges to view. However, the data from
a secured ledger doesn't appear on the report.
Manage Accounting and Reporting Sequences
299
Accounting and Reporting Sequences: Overview

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.
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 is not
automatically assigned to the reporting currency journal. You must then set up accounting and reporting
sequences separately for the reporting currencies.
Related Topics
Create Chart of Accounts, Ledger, Legal Entities, and Business Units in Spreadsheets: Explained
Defining Journal Sequences Manually: Explained

Define sequences manually 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.
300
The following figure explains the process involved in sequence setups, which includes defining and assigning sequences.
Sequence
Numbering
Define Sequences
Define Sequences
Assignments
Define Sequence Define Sequencing

Define Sequences Assign Sequences
Versions Context
Define Exceptions Define Exclusions
Sequences
Create, update, and search for sequences and sequence versions in the Sequences tab on the Manage Accounting and
Reporting page.
Define Sequences: To define a sequence, enter a unique sequence name and sequence description.
Define Sequence Versions: Create at least one sequence version to complete the sequence. A sequence version
indicates the series of sequence numbers to be used and the effective date range of the series.
The following table describes the fields on the Sequences tab.
Field Description
Status Displays the status of the sequence. The status could be New, Used, and Disabled.

Effective Start Date The effective start date uses the current system date, but can be set to any date in the past or
future.

Effective End Date The date when the sequence should be disabled.

301
Field Description
Initial Number An integer that is greater than zero. The number increments by one for each accounting entry.

Last Number Used Last generated sequence number for the version.

Sequencing Assignments
After creating your sequences, assign them with 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 Name 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 sequencing contexts.
Journal Entry Type Sequencing Event Sequence Validation Journal Sorting Date Remark
Date
General Ledger Posting Accounting Date Accounting Date Accounting Sequence

Subledger Accounting Subledger Accounting Accounting Date Completion or Posting Accounting Sequence
Date or Accounting Date

General Ledger Period Close Accounting Date Accounting Date Reporting Sequence

General Ledger Period Close Reference Date Reference Date Reporting Sequence

302
Journal Entry Type Sequencing Event Sequence Validation Journal Sorting Date Remark
Date
Subledger Accounting Period Close Accounting Date of Reference Date Reporting Sequence
Reference Date

Tip: For reporting sequences, you can specify Fiscal Balancing Segment Values to specify what balancing
segment values you can 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.
Sequencing Assignment Details

The following table explains 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.

303
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 do not impact financial results.
Document Sequences: Explained

You can assign a document sequence number to each business document or business event to uniquely identify it. For
example, you can assign a document sequence number to an invoice that gets generated in response to a purchase order.
However, you must enable the document sequencing option for that business document or event to start assigning the
number. A document sequence number is useful in tracking completed or failed transactions.
You can set up document sequencing in three different modes:
Automatic
Manual
Gapless
Note: Plan your document sequencing carefully before you start applying sequence numbers. Avoid switching
to a different mode after you saved your work on the Manage Document Sequences and Manage Document
Sequence Categories pages.
Automatic Sequencing
Automatic document sequencing assigns a unique number to each document automatically when the document is
generated. That unique number is stored in the database. You can set an initial value for the numbering sequence. Thereafter,
the numbering is sequential by date and time of creation. If you don't provide an initial value, the application sets the default
initial value as 1.
Manual Sequencing
Use the manual sequencing mode to assign a unique number to each document before the document is generated. In
manual sequencing, the numeric ordering and completeness of a transaction is not automatically enforced. As a result, users
304
can skip or omit numbers when entering the sequence value. However, each time a user assigns a number, the application
validates its uniqueness.
Gapless Sequencing
Gapless sequencing is similar to automatic sequencing. It automatically generates a unique number for each document,
but does that only for successfully generated documents. Sequence numbers are not assigned to incomplete or failed
documents. As a result, the sequence is maintained for all the successfully generated documents.
Additionally, you can control the gapless document sequencing by enforcing the Transaction Date Validation option. When
enabled, this option checks for the transaction date of a particular document and assigns the sequence number accordingly,
to chronologically maintain the documents. The sequence numbers and the transaction dates are chronologically correlated
to prevent any mismatch of a new document sequence being assigned to an older document or vice versa.
Note: Use this type of sequencing only if necessary because it may affect the performance of the application
and slow down transaction processing.
Related Topics
Document Sequence Categories: Explained

A document sequence category is a set of documents that share similar characteristics and that are formed into a logical
group. Document sequence categories simplify the task of assigning number sequences to specific documents. Instead of
assigning a number to each document, you assign a document sequence to one or more document sequence categories.
The document sequence category automatically takes care of numbering the documents.
A document sequence category identifies the database table that stores documents resulting from transactions that your
users enter. When you assign a sequence to a category, the sequence numbers the documents that are stored in a particular
table. You must create document sequence categories to be able to manage the task of assigning document sequences.
Note: Once a document sequence category is created, you can't change the application, the category code,
or the table name. Therefore, carefully consider these details and plan your document sequencing requirement
before you begin working with the application.
Once you create a document sequence category, it is available for use under the Document Sequences: Assignments
section on the Manage Document Sequences page. The Category field contains the name of the document sequence
category. After you create a document sequence, you can assign it to a document sequence category.
Document Sequences: Points to Consider

Sequencing documents is an important business and legal requirement. Therefore, you must first decide the appropriate
document sequence to use for a set of documents. Before you begin, here are a few prerequisites:
Determine beforehand the mode of document sequencing, because you can't switch to other types once a
sequence is in use.
Note details such as the document sequence and document sequence category, for later reference.
305
Identify if there are any restrictions or configuration prerequisites.
Note: Products that implement document sequencing have specifications about its usage. Refer to the
corresponding product documentation for specific details and also to determine if there are any restrictions or
configuration prerequisites.
Creating and Editing Document Sequences

You can create document sequences that are automatic, manual, or gapless, depending on the business or legal
requirement. By default, the current date is considered as the start date. The sequence definition never expires if you don't
provide an end date. Among the several options used in creating and editing document sequences, the following options are
functionally more important and therefore must be carefully determined:
Determinant Type: Select to limit the document sequencing activity to certain documents that belong to a specific
business entity, such as Ledger, Tax Registration, and so on.
Initial Value: Enter a value for the first document in your sequence. This field applies only to sequences with
automatic or gapless numbering types. Sequence numbers must not be greater than eight digits. If you leave this
field blank, the first document is automatically assigned a value of 1. Once a document sequence is defined, you
can't change this initial value.
Creating and Editing Document Sequence Categories

Document sequence categories are defined to make it easy to assign document sequence definitions to a group of
documents instead of to individual documents. Each document sequence category is mapped to a specific table, where the
documents belonging to that category are stored. When specifying the table, you must consider the following points:
When the sequential numbering feature checks for completeness or generates a report, it locates the category's
documents in the table.
Select only those tables that belong to the application associated with the category.
Once a category is defined, you can't switch to another table.
Assigning Document Sequences

Identify the documents to be numbered before assigning them a document sequence. For each document sequence, there
can be only one active assignment to a document sequence category, and a determinant value (if applicable). As part of
the assignment, specify whether the document is created automatically (for example, due to a batch process, or manually
through a form). If you don't specify an end date, the assignment continues to remain active throughout the process cycle.
If a determinant type was specified for the document sequence, then enter a specific determinant value related to the
determinant type.
At run time, when users create documents, the document sequence to be assigned is determined based on the following:
An active assignment that matches the correct combination of category
The numbering method
The date range containing the transaction date
Auditing Document Sequences

You can audit document sequences, if required, to provide an audit trail of the document sequences used in a specific
product. However, before enabling the audit functionality for a document sequence, you must have created an audit table for
the specific document sequence, using appropriate details. Enabling the audit functionality is permitted only for newly created
document sequences. You can't audit document sequences that are already in use by a specific product.
For more information about defining a document sequence audit table, see the Oracle Fusion Applications Developer's Guide.
306
Related Topics
Managing Modules in Application Taxonomy: Points to Consider
FAQs for Manage Accounting and Reporting Sequences

What happens if 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.
Manage Journal Approval Rules
Approval Management: Highlights

Use approval management to define policies that apply to approval workflows. For example, to reflect your own corporate
policies, you can specify levels of approval for expense reports over a particular amount and determine how the approvals are
routed.
Approval management:
Controls workflows for business objects such as expense reports.
Enables you to define complex, multistage task routing rules.
Integrates with the setup in Human Capital Management (HCM) to derive approvers based on the supervisory
hierarchy.
To define approval management, use the Define Approval Management task list in the Setup and Maintenance work area.
The task list includes setup tasks for managing workflow task configurations and approval groups.
Task Configuration
Manage rule sets and rules that control approval flows.
To configure a predefined approval policy, select the predefined rule set and click the Edit Task icon.
To disable a predefined rule set, select the Ignore participant check box for that rule set.
To edit the rules within a predefined rule set, you can insert, update, or delete while in edit mode.
You can configure a specific rule to automatically approve a task without sending it to any approver.
Modify the routing for that rule so that it is sent to the initiator (which means the requestor is the approver).
Set the Auto Action Enabled option to True.
307
Enter APPROVE in the Auto Action field.
Approval Groups
Each approval group includes a set of users that you configure to act on tasks in a certain pattern. Tasks can be defined to
get routed to an approval group instead of an individual user.
You can nest approval groups within approval groups.
You have two options for defining the group:
Static: Select the specific users to include in the group.
Dynamic: Provide the logic to use to determine the users in the group.
Customization
You can also customize predefined approval workflows, for example to add post-approval activities or additional stages (not
available for Oracle Cloud implementations).
Refer to the Oracle Fusion Applications Extensibility Guide for Developers.
See: Customizing and Extending SOA Components
Approving Journals: Points to Consider

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 you enable the ledger and the source for approval, then the journal
entry is sent for one level of approval. Configure the approval rules using the Define Approval Management task list in the
Setup and Maintenance work area. 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.
Where you are 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?
Select the Skip creator for Approval List option on the journal approval rules configuration page to prevent the submitter
from approving a journal batch. If the journal batch submitter is found to be one of the approvers, then you can select to skip
the journal submitter as an approver. Then assign the approval task to other approvers or automatically route the approval
task to the submitter's manager.
The following table provides an example of the rule conditions and approval actions that you can configure for different
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

308
Condition Approval Action
Greater than 100,000 USD Two levels of approval required

Build your rules for combinations of ledger, entered amount, approval level, or other scenarios. In addition, define your rules
based on attributes from the different parts of your journal, including the ledger, batch, header, or line level. For example, use
category, source, account, or descriptive flexfield information as selection criteria for journal approval.
Approvals List Builder Considerations

The following table describes the list builders you can use to build a journal approval list.
List Builder Functionality Additional Information
Human Resources (HR) Supervisory The HR supervisory hierarchy levels are The most effective when the General
selected. The number of levels available for Accountant enters the journals. For example,
approval is specified. if an accountant enters a journal, he needs
approval from his manager. If his manager
enters a journal, he needs approval from his
manager, and so on up the hierarchy for the
specified number of levels. Self-approval can
be set at any level in the hierarchy.

Job Level A relative dollar amount is attached to a Enable self-approval to allow approval of
job. The approval list moves up the HR journals created within your authority limit.
Supervisory hierarchy to the point where
approval finds a job with the necessary
approval amount.

Position A relative dollar amount is attached to a

position. Use this hierarchy if you need:

A hierarchy different than the HR
Supervisory hierarchy
Multiple hierarchies that must be
selected based on different attributes.
Approval Group Approver groups represent functional Not Applicable

or subject matter experts outside the
transaction's managerial chain of authority,
such as Legal or Human Resource
personnel.

Dual Chain Dual chains can be processed at the same Not Applicable
time.

Note: Best practices: Select the Job Level, HR Supervisory, or Position list builder for your journal approval
rules.
Other Considerations
Other functionality to consider before defining approval rules.
Approval is for the entire journal batch regardless of the attributes used in the approval rules.
309
For the job and position level approvals, the approval list continues up the hierarchy until it finds the approver with
the correct approval authority.
If the 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 Withdraw Approval button on the Journals page is used anytime 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 region of the dashboard displays journals requiring your approval and journals pending approval from
others.
If you are the current approver, the Journals page shows the journals to be approved or rejected.
Allocation journals are not 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.
Note: Approval is enabled at the ledger and source level. Both the ledger and journal source must be enabled
for the approval process.
Creating a Journal Approval Rule: Worked Example

This example demonstrates how to create a journal approval rule.
You are the General Accountant for InFusion America Inc. who has been tasked with setting up Journal Approval functionality.
Creating a journal rule is the first step.
Creating a Journal Approval Rule

1. Navigate to the Business Process Management BPM Worklist to review and access tasks that you want to
perform.
2. On the Task Configurator tab, click the FinGlJournalApproval (1.0) link.
3. Select the Data Driven tab to configure task data that drives the rules.
4. Create a supervisory rule set and a journal approval rule within that rule set. A supervisory rule set ascends the
primary supervisory hierarchy, starting at the requester or at a given approver, and generates the approval chain.
5. In the Select Rule Set field, select the SoaOLabel.JournalApprovalStage: Supervisory_JournalApprovalRuleSet rule
set.
6. Click the Edit Task icon.
7. Click the New Rule button and select the New Rule list item.
8. In the Name field, enter Approval for More than 10,000 dollars.
9. Expand the new rule and complete the fields, as shown in this table.
Field Value
Description Approval rule for journals equal to or more than 10,000 dollars.

Tree Mode Selected

310
Field Value
ROOT JournalBatch

10. In the IF section, click the Test option to begin creating the IF statement for the condition of the rule.
11. To create the IF statement, complete the fields, as shown in this table.
Field Value
Variable enableJeApprovalFlag

Operator is

Value "Y"

12. Click the Insert Test button to create the second IF statement.
Field Value
Variable maxLineNetAmount

Operator same or more than

Value 10000

14. To create the THEN statement for the condition of the rule set, select Supervisory.
15. Click the Create Action button.
Field Value
Response Type Required

Starting Participant HierarchyBuilder. get Manager"supervisor"

Top Participant HierarchyBuilder. get Principal("jcooper")

17. Click Save.

18. Click OK.
19. Collapse the rule set.
20. Click the Commit Task button to deploy the journal approval rule.
Creating Journal Approval Rules

Watch: This video tutorial shows you how to create journal approval rules that either automatically approve a journal batch or
that route the batch for supervisory approvals based on the ledger and journal amounts.
311
Manage AutoPost Criteria Sets
Creating an AutoPost Criteria Set: Worked Example

This example shows how to create an AutoPost Criteria Set to post your general ledger journal entries that were created by
the journal import process for your subledger transactions. Your enterprise, InFusion Corporation:
Implemented Oracle Fusion General Ledger and the Oracle Fusion subledgers: Payables and Receivables.
Uses a non-Oracle subledger called Fast Assets for fixed asset tracking and depreciation.
Plans to automate posting of general ledger journal batches created by the journal import process to protect the
subledger sourced journal entries from edits or deletion that might cause an out-of-balance situation between the
subledgers and general ledger.
Consider the following points while 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.
Creating an AutoPost Criteria Set

Create your AutoPost Criteria Set to automatically post journal entries from both Oracle and non-Oracle subledgers.
1. On the Manage AutoPost Criteria Sets page, click the Create icon to open the Create AutoPost Criteria Set page.
2. Enter the criteria set name: All Journal Imported Entries.
3. Select the Enabled check box.
4. Enter the description: Posting journals imported from the subledgers.
5. Click the Add Row icon to add each new line.
Priority Ledger or Ledger Set Source Category Accounting Period
1 InFusion Corporation Payables All All

Ledger

2 InFusion Corporation Receivables All All

Ledger

3 InFusion Corporation Fast Assets All All

Ledger

7. For all three sources, select Yes for the Process All Criteria option, and enter 30 as the number of days before
and after submission date. Setting the before and after day with a wide range of days enables the process to run
less often.
312
9. Schedule the process to run immediately after the journal import process to prevent changes to the journals. Run the
process during nonpeak times to save resources.
Manually Generating the AutoPost Process: Examples

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 Correct the error that caused the journal
from the general ledger interface table. The import to fail.
AutoPost Journals process runs on schedule
but finds no 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 Revise the criteria set.
posting 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.
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
313
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 my 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.
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.
Manage Journal Reversal Criteria Sets
314
Automatic Journal Reversals: How They Are Processed

The ability to submit journal reversals automatically enables you to automate and streamline your journal reversal process. If
you generate a large number of journal reversals for month end closing, use the automatic reversal functionality to save time
and reduce entry errors.
AutoReverse Journals Process
Journal Journal
Reversal Posting
Process Process
Posting
Execution
Report
AutoReverse AutoReverse
Process Execution
Report
Create/Edit
Journal Reversal Generate Reversal New Period Opens
Criteria Set
OR
Manually Generate
or Schedule
Settings That Affect Journal Reversals

The journal must meet the following criteria to be automatically reversed:
Balance type is Actual.
Category is enabled to be automatically reversed.
Reversal period is open or future enterable.
Posted but not yet reversed.
Not a reversal journal. Reversal journals cannot be reversed in Oracle Fusion General Ledger.
Not a posted journal for a reporting currency that was replicated from its source journal. Reporting currency journals
that were replicated from a source journal are reversed when the source journal is reversed.
Not a posted journal that originated from Oracle Fusion Subledger Accounting with a frozen source.
315
A new ledger option called Launch AutoReverse After Open Period enables generation of automatic journal reversals
when an accounting period is first opened. This ledger option replaces the former profile option called GL: Launch
AutoReverse After Open Period. If you reverse your journals on the last day of every month, disable the ledger option to
automatically run reversals when the period is opened. Then schedule the AutoReverse process to run on the last day of
every month. The accounting period automatically increments for each subsequent run.
How Automatic Journal Reversals Are Processed

The following table describes the criteria used to create journal reversal criteria sets, which automatically reverse and
optionally post journals.
Criteria Functionality Options
Category Required. All journal categories are listed.

The journal category you set as the reversal
option. Journals entered with this category
are selected for reversal and optionally,
posting.

Reversal period No default

Required.
Same period
Next period
The accounting period of the reversal journal. Next nonadjusting
The Next day option is only applicable to
Next day
average daily balance ledgers. Nonaverage
daily balance ledgers and consolidation
average daily balance ledgers treat the Next
day option in the same manner as the No
default option.
Reversal day Required for average daily balance ledgers First day
only. Last day
Next day
The day of the period on which to reverse the
journal.

Reversal method Required. Change sign

Switch debit or credit
The method for changing the amounts in the
reversal entry.

Automatic reversal option Required. None

Reverse automatically
The option to reverse and post journals Reverse and post automatically
automatically. Journals are posted after they
are reversed.

After creating your journal reversal criteria sets, assign them to ledgers. Journal reversal criteria set can be shared and
assigned to multiple ledgers. Also secure journal reversal criteria set definitions using definition access set security to prevent
unauthorized users from using, viewing, or modifying the journal reversal criteria.
If the automatic reversal option is set to reverse and post automatically, the AutoPost process posts the journals generated by
the AutoReverse process. The process does not post other journals. You manually post reversal journals that were generated
outside of the AutoReverse process.
316
Note: Journals posted by the AutoReverse process always bypass approval.
General Ledger automatically creates the AutoReverse Execution report when the AutoReverse process completes
successfully. The report prints the journal name and reversal period for each journal that is successfully reversed and whether
the reversal journal is submitted for posting. The AutoPost Execution report is created automatically when the AutoPost
process finishes. These reports help you diagnose any problems and verify that all journals were processed properly.
Note: The AutoReverse process does not check that the reversal date is a valid business day for an average
balance ledger. The journal validation in the journal pages or import process does the check and if necessary,
rolls the date to the next business day.
Define Lookups
Lookups: Explained
Lookups are lists of values in applications. You define a list of values as a lookup type consisting of a set of lookup codes,
each code's translated meaning, and optionally a tag. End users see the list of translated meanings as the available values for
an object.
Lookups provide a means of validation and lists of values where valid values appear on a list with no duplicate values. For
example, an application might store the values Y and N in a column in a table, but when displaying those values in the user
interface, Yes or No (or their translated equivalents) should be available for end users to select. For example, the two lookup
codes Y and N are defined in the REQUIRED_INDICATOR lookup type.
The following table contains an example of a lookup type for marital status (MAR_STATUS) that has lookup codes for users to
specify married, single, or available legal partnerships.
Lookup Code Meaning Tag
M Married Not applicable

S Single Not applicable

R Registered Partner +NL

DP Domestic Partner -FR, AU

In this case, tags are used for localizing the codes. All legislations list Married and Single. Only the Dutch legislation lists
Registered Partner. And all legislations except France and Australia also list Domestic Partner.
When managing lookups, you need to understand the following.

Using lookups in applications
Customization levels
Accessing lookups
317
Enabling lookups
The three kinds of lookups: standard, common, and set enabled
Using Lookups in Applications

Use lookups to provide validation or a list of values for a user input field in a user interface.
An example of a lookup used for validation is a flexfield segment using a table-validated value set with values from a lookup
type. An example of a lookup in a list of values is a profile option's available values from which users select one to set the
profile option. Invoice Approval Status gives the option of including payables invoices of different approval statuses in a
report. The lookup code values include All, so that users can report by all statuses: Approved, Resubmitted for approval,
Pending or rejected, and Rejected.
Customization Level
The customization level of a lookup type determines whether the lookups in that lookup type can be edited. This applies data
security to lookups.
Some lookup types are locked so no new codes and other changes can be added during implementation or later, as needed.
Depending on the customization level of a lookup type, you may be able to change the codes or their meanings. Some
lookups are designated as extensible, so new lookup codes can be created during implementation, but the meanings of
predefined lookup codes cannot be modified. Some predefined lookup codes can be changed during implementation or later,
as needed.
The customization levels are user, extensible, and system. The following table shows the lookup management tasks permitted
at each customization level.
Permitted Task User Extensible System
Deleting a lookup type Yes No No

Inserting new codes Yes Yes No

Updating start date, end date, Yes Yes, only if the code is not No
and enabling the lookup code predefined data

Deleting codes Yes Yes, only if the code is not No

predefined data

Updating tags Yes No No

Updating module Yes No No

Predefined data means LAST_UPDATED_BY = SEED_DATA_FROM_APPLICATION.
If a product depends on a lookup, the customization level must be system or extensible to prevent deletion.
Once the customization level is set for a lookup type, it can't be modified. The customization level for lookup types created
using the Define Lookups page is by default set at the User level.
318
Standard, Common, and Set-Enabled Lookups

The following table shows the available types of lookups.
Lookup Type Description
Standard Lists the available codes and translated meanings.

Set enabled Associates a reference data set with the lookup codes.

Common Legacy lookups or lookups that have attributes.

Standard lookups are the simplest form of lookup types consisting only of codes and their translated meaning. They differ
from common lookups only in being defined in the standard lookup view. Common lookups exist for reasons of backward
compatibility and differ from standard lookups only in being defined in the common lookup view. These can also be lookups
having attribute columns. Set enabled lookup types store lookup codes that are enabled for reference data sharing. At
runtime, a set-enabled lookup code is visible because the value of the determinant identifies a reference data set in which the
lookup code is present.
Accessing Lookups
Standard, set-enabled, and common lookups are defined in the Standard, Set-enabled, and Common views, respectively.
Applications development may define lookups in an application view to restrict the UI pages where they may appear.
In lookups management tasks, lookups may be associated with a module in the application taxonomy to provide criteria
for narrowing a search or limiting the number of lookups accessed by a product specific task such as Manage Purchasing
Lookups.
Enabling Lookups
A lookup type is reusable for attributes stored in multiple tables.
Enable lookups based on the following.
Selecting an Enabled check box

Specifying an enabled start date, end date, or both
Specifying a reference data setdeterminant
If you make changes to a lookup, users must sign out and back in before the changes take effect. When defining a list of
values for display rather than validation, limit the number of enabled lookup codes to a usable length.
For more information on the predefined lookups and lookup codes, open the Setup and Maintenance work area, and use the
tasks in the Define Lookups task list.
Translating Lookups
You can translate the lookups that you defined to the preferred language(s) without changing the language session of the
application. Use the translation option available on the lookup code table. By default, for each lookup, all the permitted
language rows in the translator dialog box appear in the source language (the current session language). When you edit a
particular language entry, you can modify the translated meaning and description to the language in which you want the
lookup to appear. Once the updates are made, the end-users can view the lookup in the translated text.
319
Note: You can add the translation for only as many languages as are permitted by the administrator. The
functionality to limit the number of languages displayed on the dialog box is controlled through the Translation
Editor Languages profile option. It can be set at the SITE or USER level. If nothing is specified, all active
languages are displayed.
Related Topics
How can I access predefined lookups?

Creating a new standard lookup involves creating or selecting a lookup type containing the lookup code. The task also
involves determining appropriate values for the lookup codes and their meanings. You can only create or edit lookup codes
for a particular lookup type if its customization level supports it.
Creating a Lookup Type Called COLORS

Your enterprise needs a list of values for status to be used on a process. The lookups are colors, so the lookup type you
create is COLORS. The following table lists a mapping between the lookup type parameters and the actual values assigned to
those parameters to create the required list of values.
Lookup type parameters Value
Lookup type name COLORS

Meaning Status

Description Status by color

Module Oracle Fusion Middleware Extensions for Oracle Application

After you define the lookup type, you need to define the lookup codes and their related details. The following table lists the
lookup codes you define for the COLORS lookup type.
BLUE Urgent No 4

RED Stop Yes 1

GREEN Proceed Yes 3
320

YELLOW Check Yes 2

The Resulting Data Entry List of Values

Only the enabled lookup codes appear in the list of values for the COLORS lookup type. You must select one of them to
complete the activity.
The following table lists the meanings and the codes that were enabled. They appear in the order of the defined display
sequence.
Meaning Lookup Code
Stop RED

Check YELLOW

Proceed GREEN

Analysis
The BLUE lookup code was not enabled and does not appear in the list of values. The display sequence of values in the list of
values is alphabetic, unless you enter a number manually to determine the order of appearance. Number 1 indicates the first
value that appears in the list. Only lookups that are enabled and active between start and end dates are visible.
The Transaction Table

When users enter one of the values from the list of values for the lookup type COLORS, the transaction table records
the lookup code. The following table contains an example, where the lookup code is stored in the Status column of the
transaction table.
Transaction number User name Status
1 Jane RED

2 Bob YELLOW

3 Alice BLUE

The status for one user is BLUE because at the time they entered a value, BLUE was enabled. Disabling a lookup code does
not affect transaction records in which that code is stored. Data querying and reporting have access to disabled lookup
codes in transaction tables.
Related Topics
321

Creating a new set-enabled lookup is similar to creating a standard lookup with the addition of specifying a reference data set
determinant for the lookup codes. You can only create or edit lookup codes for a particular lookup type if its customization
level supports it.
The reference data set for a set-enabled lookup code is part of its foreign key. This is unlike other set-enabled entities. Use
the Manage Set Assignments task to define and manage reference data set assignments.
Selecting a Reference Group for a Set-Enabled Lookup Type

Specify a reference group for a set-enabled lookup type to indicate which reference data set assignments are available for its
lookup codes. For example a COLORS lookup type might be set-enabled for a Countries reference group that includes the
US and EU reference data set assignments.
Selecting a Reference Data Set for a Set-Enabled Lookup

The reference data set determines which lookup code is included in the list of values. For example, there are two references
data sets - one for the US and the other for EU. If a COLORS lookup type contains RED, YELLOW, ORANGE, and GREEN
lookup codes, you can enable one RED lookup code from the US reference data set and another RED lookup from the EU
reference data, each lookup code having different meanings.
The following table elaborates the example, how these two reference data sets (US and EU) contain one lookup code that is
common, but each differing in its lookup meaning.
US RED Red

US YELLOW Yellow

US GREEN Green

EU RED Rouge

EU ORANGE Orange

Some lookup codes may be unique to one or another reference data set as the ORANGE lookup is to the EU reference data
set in the example.
In another example in the following table, a lookup type called HOLD_REASON provides a list of reasons for putting a
contract renewal on hold. Reference data sets determine which codes are included in the Hold Reason list of values.
322
US SEC SEC Compliance Review

US DIR Needs Director's Approval

US VP Needs Vice President's Approval

CHINA CSRC Pending China Securities Regulatory

Commission Review

CHINA PR Needs President's Approval

COMMON REQUESTED Customer Request

Referring to the example in the table, when end-users place a contract on hold in the US business unit, the three reason
codes in the US set are available. When placing a contract on hold in the China business unit, the two codes in the China set
are available.
Related Topics
FAQs for Define Lookups

On the Define Lookups page, you can edit the existing lookup codes of a lookup type or add new lookup codes. To open the
page, navigate to the Setup and Maintenance work area and search for the Define Lookup task list.
The task list contains three tasks:
Standard Lookups
Common Lookups
Set-enabled Lookups
Each task contains a predefined set of lookup types classified and stored as per the functionality. Open a task to search and
edit the required lookup. However, you may not be able to edit a lookup if its customization level doesn't support editing.

Lookup types are classified using tasks that involve a group of related lookups, such as Manage Geography Lookups. Each
task gives you access only to certain lookup types. However, the generic tasks provide access to all lookups types of a kind,
such as common lookups associated with the Manage Common Lookups task.
If the lookup types in an application are available in the standard, common, or set-enabled lookups view, they are central
to an application. However, lookup types defined for a specific application are managed using the task or task list for that
application.
323

A lookup type consists of lookups that are static values in a list of values. Lookup code validation is a one to one match.
A table-validated value set may consist of values that are validated through a SQL statement, which allows the list of values to
be dynamic. The following table brings out the differences between a lookup type and a value set.
Tip: You can define a table-validated value set on any table, including the lookups table. Thus, you can change
a lookup type into a table-validated value set that can be used in flexfields.
Area of Difference Lookup Type Value Set
List of values Static Dynamic if the list is table-validated

Validation of values One to one match of meaning to code Validation by format or inclusion in a table
included in a lookup view, or through the
determinant of a reference data set

Format type of values char varchar2, number, and so on

Length of value Text string up to 30 characters Any type of variable length from 1 to 4000

Duplication of values Never. Values are unique. Duplicate values allowed

Management Both administrators and end-users manage Usually administrators maintain these, except
these, except system lookups or predefined some product flexfield codes, such as GL for
lookups at the system customization level, Oracle Fusion General Ledger that the end-
which can't be modified. users maintain.

Both lookup types and value sets are used to create lists of values from which users select values.
A lookup type cannot use a value from a value set. However, value sets can use standard, common, or set-enabled lookups.

A tag is an additional label attached to the lookup. Tags are user defined and can be grouped depending on the user's
requirement to make search convenient and effective.
The same tag may be used across lookup categories. In such cases, tags are used as a refined search criterion to filter
information across several groups and get the custom search result.
How can I search for a specific lookup code?

Use the Query By Example functionality to sort through hundreds of lookup codes for a lookup type, and display a specific
lookup code. Enter the first few characters of the lookup code value in any of the relevant fields to filter the records.
Note: The search functionality is case sensitive.
324
Manage Descriptive Flexfields
Descriptive Flexfields: Explained

Use descriptive flexfields to add custom attributes to business object entities, and define validation for them.
All the business object entities that you can use in the application are enabled for descriptive flexfields. However, configuring
descriptive flexfields is an optional task.
Context
A descriptive flexfield can have only one context segment to provide context sensitivity. The same underlying database
column can be used by different segments in different contexts.
For example, you can define a Dimensions context that uses the following attributes:
ATTRIBUTE1 column for height

ATTRIBUTE2 column for width
ATTRIBUTE3 column for depth
You can also define a Measurements context that uses the same columns for other attributes:
ATTRIBUTE1 column for weight

ATTRIBUTE2 column for volume
ATTRIBUTE3 column for density
Segments and Contexts

The following table lists the different types of descriptive flexfield segments.
Segment Type Run Time Appearance
Global segment Always available

Context segment Determines which context-sensitive segments are displayed

Context-sensitive segment Displayed depending on the value of the context segment

325
The following figure displays a descriptive flexfield having one context segment called Category for which there are three
values: Resistor, Battery, and Capacitor. Additionally, the descriptive flexfield comprises two global segments that appear in
each context, and three context-sensitive segments that only appear in the specific context.
Context-
Context Global sensitive
segment segments segments
Attributes: Category G1 G2 A3 A4 A5
Context: Context:
Resistor Capacitor
Context:
Battery
G1 G1
G2 G2
A3 A4
A4 A5
G1
G2
A3
A4
A5
Application development determines the number of segments available for configuring. During implementation, configure the
flexfield by determining the following:
Attributes to add using the available segments

Context values
The combination of attributes in each context
Value Sets
For each global and context-sensitive segment, you configure the values permitted for the segment. Based on it, the values
that end users enter are validated, including interdependent validation among the segments.
Protected Descriptive Flexfield Data

Application developers may mark some data configurations in a descriptive flexfield as protected, indicating that you can't
edit them.
326
Related Topics
Planning Descriptive Flexfields: Points to Consider

Once you have identified a flexfield to configure, plan the configuration in advance. Compile a list of the UI pages and other
artifacts in your deployment that are affected by the configuration. Verify that you are provisioned with the roles needed to
view and configure the flexfield. View the flexfield using the Highlight Flexfields command in the Administration menu while
viewing the run time page where the flexfield appears. Plan how you will deploy the flexfield for test and production users.
Review the tools and tasks available for managing flexfields, such as the Define Flexfields task list, Manage Sandboxes, and
Highlight Flexfields for adding and editing flexfield segments.
Planning a descriptive flexfield can involve the following tasks:
1. Identify existing parameters.
2. Identify existing context values and whether the context value is derived.
3. Identify custom attributes and plan the descriptive flexfield segments, segment properties, and structure.
4. Plan validation rules.
5. Plan initial values.
6. Plan attribute mapping to Oracle Business Intelligence objects.
Identify Existing Descriptive Flexfield Parameters

Some descriptive flexfields provide parameters that can be used to specify the initial value of a descriptive flexfield segment.
The parameter is external reference data, such as a column value or a session variable. For example, if a flexfield has a user
email parameter, you can configure the initial value for a customer email attribute to be derived from that parameter.
Review the list of available parameters in the Derivation Value field in the Create Segment page for a descriptive flexfield. If
you decide to use one of the parameters to set an initial value, select that parameter from the Derivation Value drop-down
list when you add the descriptive flexfield segment.
Evaluate Whether the Context Value Is Derived

The context value for a descriptive flexfield might have been preconfigured to be derived from an external reference. For
example, if the context is Marriage Status, then the value might be derived from an attribute in the employee business object.
When the context value is derived, you might need to take the derived values and their source into consideration in your plan.
To determine whether the context value is derived, access the Edit Descriptive Flexfield task to view the list of configured
context values for the flexfield. The Derivation Value field in the Context Segment region displays a list of available parameters.
If context values have been preconfigured, see Oracle Applications Cloud Help for product-specific information about the use
of those values.
Plan the Segments, Segment Properties, and Structure

Identify the custom attributes you need for a business object to determine the segments of the descriptive flexfield. Determine
the segment properties such as the prompt, display type, or initial value.
327
The structure of the descriptive flexfield is determined by its global, context, and context-sensitive segments. Plan a global
segment that captures an attribute for every instance of the business object. Plan a context for segments that depend on
a condition of situation applying to a particular instance of the business object. Plan context-sensitive segments to capture
attributes that are relevant in the context.
There is only one context segment available for descriptive flexfields. If you have more than one group of custom attributes
where you could use the context segment, you will have to pick one group over the others, based on your company's needs
and priorities, and add the other custom attributes as global segments.
Plan Validation Rules

Define each segment's validation rules and check if value sets exist for those rules or you must create new ones. If you must
create a value set, you can create it either before configuring the flexfield or while creating or editing a segment.
When determining a segment's validation rules, consider the following questions:
What is the data type - character, date, date and time, or number?
Does the segment require any validation beyond data type and maximum length?
Should a character type value be restricted to digits, or are alphabetic characters allowed?
Should alphabetic characters automatically be changed to uppercase?
Should numeric values be zero-filled?
How many digits can follow the radix separator of a numeric value? In base ten numeric systems, the radix separator
is decimal point.
Does the value need to fall within a range?
Should the value be selected from a list of valid values? If so, consider the following questions:
Can you use an existing application table from which to obtain the list of valid values, or do you need to create
a custom list?
If you are using an existing table, do you need to limit the list of values using a WHERE clause?
Does the list of valid values depend on the value in another flexfield segment?
Is the list of valid values a subset of another flexfield segment's list of values?
Plan Initial Values

For every segment, list the constant value or SQL statement, if any, to use for the initial value of the custom attribute.
Plan How Segments Map to Oracle Business Intelligence Objects

You can extend descriptive flexfields into Oracle Transactional Business Intelligence (OTBI) for ad hoc reporting purposes.
Determine the descriptive flexfield segments to be made available for reporting, and select the BI Enabled check box
accordingly on the Manage Descriptive Flexfields page. You must run a process to extend the BI enabled segments into
OTBI. For more information about extending the BI enabled segments into OTBI, see the Setup and Configuration chapter in
the Oracle Transactional Business Intelligence Administrator's Guide.
Depending on the reporting needs, you may map similar context-sensitive attributes from different contexts to the same
attribute in OTBI. For example, there may be a segment tracking the Product Color attribute in different contexts of a context
sensitive descriptive flexfield. You can use segment labels to map these context-sensitive attributes together by defining a
segment label and updating the BI Label list accordingly.
Related Topics
328

Configuring descriptive flexfields involves managing the available flexfields registered with your Oracle Applications Cloud
database and configuring their flexfield-level properties, defining and managing descriptive flexfield contexts, and configuring
global and context-sensitive segments.
Every descriptive flexfield is registered to include a context segment, which you may choose to use or not.
In general, configuring descriptive flexfields involves:

1. Creating segment labels for business intelligence enabled flexfields.
2. Configuring global segments by providing identity information, the initial default value, and the display properties.
3. Configuring the context segment by specifying the prompt, whether the context segment should be displayed, and
whether a value is required.
4. Configuring contexts by specifying a context code, description, and name for each context value, and adding its
context-sensitive segments, each of which is configured to include identifying information, the column assignment,
the initial default value, and the display properties.
The following aspects are important in understanding descriptive flexfield management:
Segments
Adding segments to highlighted descriptive flexfields
Usages
Parameters
Delimiters
Initial Values
Segments
You can assign sequence order numbers to global segments and to context-sensitive segments in each context. Segment
display is always in a fixed order. You cannot enter a number for one segment that is already in use for a different segment.
Value sets are optional for context segments and follow specific guidelines:
The value set that you specify for a context segment consists of a set of context codes.
Each context code corresponds to a context that is appropriate for the descriptive flexfield.
The value set must be independent or table-validated.
If table-validated, the WHERE clause must not use the VALUESET.value_set_code or SEGMENT.segment_code
bind variables.
The value set must be of data type Character with the maximum length of values being stored no larger than the
context's column length.
If you don't specify a value set for a context segment, the valid values for that context segment are derived from the
context codes. The definition of each context segment specifies the set of context-sensitive segments that can be
presented when that context code is selected by the end user.
329
For reasons of data integrity, you cannot delete an existing context. Instead, you can disable the associated context
value in its own value set by setting its end date to a date in the past.
You can configure the individual global segments and context-sensitive segments in a descriptive flexfield. These
segment types are differentiated by their usage, but they are configured on application pages that use most of the
same properties.
Adding Segments to Highlighted Descriptive Flexfields

When you highlight flexfields on a run time page and use an Add Segment icon button to create a segment, the segment
code, name, description, table column, and sequence number are set automatically. If you use an Add Segment icon button
to configure descriptive flexfield segments, you cannot use an existing value set. Value sets are created automatically when
you add the segments. You can enter the valid values, their descriptions, and the default value or specify the formatting
constraints for the value set, such as minimum and maximum values.
Depending on display type, the value set you create using the Add Segment icon button is either an independent value set
or a format-only value set. The following table shows which type of value set is created depending on the segment display
component you select.
Display Component Value Set Created Using Add Segment
Check Box Independent

Drop-down List Independent

List of Values Independent

Radio Button Group Independent

Text Field With Search Independent

Text box Format Only

Text area Format Only

Date/Time Format Only

Tip: After you add a context value, refresh the page to see the new value.
Usages
Descriptive flexfield usages allow for the same definition to be applied to multiple entities or application tables, such as a
USER table and a USER_HISTORY table. Descriptive flexfield tables define the placeholder entity where the flexfield segment
values are stored once you have configured the descriptive flexfield. When you configure a flexfield, the configuration applies
to all its usages.
Parameters
Some descriptive flexfields provide parameters, which are attributes of the same or related entity objects. Parameters are
public arguments to a descriptive flexfield. Parameters provide outside values in descriptive flexfield validation. You use
parameters to set the initial value or derivation value of an attribute from external reference data, such as a column value or
330
a session variable, rather than from user input. Parameters can be referenced by the logic that derives the default segment
value, and by table-validated value set WHERE clauses.
Delimiters
A segment delimiter or separator visually separates segment values when the flexfield is displayed as a string of concatenated
segments.
Initial Values
The SQL statement defining an initial value must be a valid statement that returns only one row and a value of the correct
type.
You can use two types of SQL statements:
SQL statement with no binding. For example, select MIN(SALARY) from EMPLOYEES.
SQL statement with bind variables. You can use the following bind variables in the WHERE clause of the SQL
statement.
:{SEGMENT.<segment_code>}: Identifies a segment in the same context.
:{CONTEXT.<context_code>;SEGMENT.<segment_code>}: Identifies a segment in a different context. The
context must be in the same category or in an ancestor category, and it cannot be a multiple-row context.
:{VALUESET.<value_set_code>}: Identifies the closest prior segment in the same context that is assigned to
the specified value set.
:{FLEXFIELD.<internal_code>}: Identifies a flexfield.
For more information about using bind variables, see the help for value sets.
Selecting a global, context, or context-sensitive segment's BI Enabled check box specifies that the segment is available for
use in Oracle Business Intelligence.
When the flexfield is imported into Oracle Business Intelligence, the label you selected from the BI Label drop-down list
equalizes the segment with segments in other contexts, and maps the segment to the logical object represented by the label.
Related Topics
Defining Value Sets: Critical Choices
Why can't I edit my flexfield or value set configuration?
Enabling Descriptive Flexfield Segments for Business Intelligence:

Points to Consider
A descriptive flexfield that is registered in the database as enabled for Oracle Business Intelligence (BI) includes a BI Enabled
setting for each of its segments. When a global, context, or context-sensitive segment is BI-enabled, it is available for use in
Oracle Business Intelligence.
331
The following aspects are important in understanding BI-enabled flexfield segments:

use of the newly-generated attributes in business intelligence applications. For example, a user can generate a report that
includes attributes added by the descriptive flexfield. For additional information about logical objects and import, refer to the
Oracle Transactional Business Intelligence Administrator's Guide.
Flattening
When you deploy a business intelligence-enabled descriptive flexfield, the deployment process generates an additional
set of flattened Application Development Framework (ADF) business components in addition to the usual ADF business
components and ADF faces run time artifacts that are generated during deployment. The flattened business components
include attributes for business intelligence-enabled segments only. Flattening means each custom column in each context
shows up as an attribute in an Oracle Business Intelligence folder.
Flattened components include one attribute for the BI-enabled context-segment, and one attribute for each business
intelligence-enabled global segment. For BI-enabled context-sensitive segments, consider the following:
If you assigned a label to the segment, the flattened components include an additional single attribute representing
segments with that label.
If you didn't assign a label, the flattened components include a discrete attribute for each BI-enabled context-
sensitive segment in each context.

You can simplify reporting by representing similar segments as a single logical object in Business Intelligence.
If you assign a label to any set of context-sensitive segments that serve the same purpose in different contexts, you can
consolidate or equalize the segments into a single attribute. This prevents duplication and the extra workload and complexity
that result from the flattening process. For example, a United States context might have a Passport segment and a Canada
context might have Visa segment. If you assign the NationalID segment label to both the Passport and Visa segments, they
are equalized into the same NationalID attribute in the flattened business component.
Non-labeled context-sensitive segments aren't equalized across context values, so the flattened components include a
separate attribute for each context-sensitive segment for each context value. It may not be possible to equalize similarly
labeled segments if they have incompatible data types or value set types.
Assign a label to a global segment, context segment, or context-sensitive segment to map the corresponding attribute in the
flattened components to a logical object in Oracle Business Intelligence. Using labels to map segments to BI logical objects
minimizes the steps for importing the flexfield into Oracle Business Intelligence.
Note: Assigning a label to a context-sensitive segment serves to equalize the attribute across contexts, as well
as map the equalized attribute to business intelligence.
Managing Labels
You may assign a predefined label (if available) to segments or create new labels for assignment, as needed. Specify a
code, name, and description to identify each label. In the BI Object Name field, enter the name of the logical object in Oracle
332
contexts.
intelligence, you must manually map the segment to the desired logical object when importing into Oracle Business
Intelligence.
In addition, context-sensitive segments without labels cannot be equalized across context values. The flattened components
include a separate attribute for each non-labeled context-sensitive segment in each context.

repository to make use of the newly flattened business components in business intelligence and then propagate the flexfield
<name>_c attributes for each segment, along with some other optional attributes. The <name> attribute contains
Related Topics
Enabling Key Flexfield Segments for Business Intelligence: Points to Consider
Define Profile Options
Hierarchy in Profile Levels: Explained

The hierarchy in profile levels determines the context for making a profile option effective.
You can enable a profile option at the following levels:
Site level (lowest): The entire site of deployment

User level (highest): A specific user
After you create or edit a profile option on the Manage Profile Options page, you must enable it. You can enable it at multiple
levels. The setting at the highest enabled level takes precedence over the lower levels. User level is the highest in the
hierarchy and always takes precedence over the settings at the site level.
On the Manage Administrative Profile Values page, set the profile value at any of the enabled levels of the profile option.
333
Example of Profile Option Hierarchy

The following table shows an example of setting the currency profile option at different levels.
Profile Level Hierarchy Currency
Site Lowest Euro

User Highest US Dollar

For this example, there are two users, John and Lisa. For John, the user-level profile value currency is set to US Dollar. If the
Currency profile option is enabled only at the site level, both John and Lisa would see Euro as the default currency. If the
profile option is enabled at the user level, users having a different currency set as their currency profile value would see only
that currency. In this case, John would see US Dollar as the default currency. If the Currency profile option is enabled at the
user level and there is no user level currency defined, the site level setting takes effect. When both site and user levels are
enabled, the value for the user level takes precedence over the site level value.
Managing Profile Categories: Points to Consider

You can create profile categories to group profile options based on their functional similarities and their use. In the Setup and
Maintenance work area, search for the Manage Profile Categories task.
Profile categories help administrators or implementors in retrieving profile options using a search criterion on the Manage
Administrator Profile Values page.
Managing Profile Categories

Consider the following options while managing profile categories:
Create profile categories and add existing profile options to them
Add newly created profile options to existing custom profile categories
Note: While you can add a profile option to more than one category, some profile categories are predefined and
restricted from any modifications. So, you can't edit them or add profile options to them.
Setting Display Sequence for the Profile Options

You must set the display sequence for each profile option that you add to a profile category. Display sequence determines
the order in which the profile options appear in a search result, based on the profile category. You can set the sequence
beginning with zero or one for the first profile option to display, and proceed sequentially to assign the values to the remaining
profile options.
The following table demonstrates the effect of the display sequence on the profile options when they are retrieved as search
results.
Profile Category Included Profile Option - Assigned Display Display Sequence of Profile Options in the
Sequence Search Results
Attachments Attachment File Directory - 2 1. Indicate Attachments

Indicate Attachments - 1 2. Attachment File Directory
334
Related Topics
Setting Profile Option Values: Procedure
335
336
Implementing Enterprise Structures and General Ledger Period Close
10 Period Close
Close Monitor: Overview

The Close Monitor:
Provides information about the period close status for a given accounting period across multiple products for related
ledgers in a hierarchical ledger set based display.
Uses the hierarchical ledger set to mirror the consolidation relationships and roll ups of entities across the enterprise.
Summarizes period close status information for each ledger across multiple products and for each consolidation
node across multiple ledgers.
Provides the contact information of the manager for a given node on the ledger set hierarchy.
Summarizes high-level income statement results for each entity and aggregates this financial information at each
consolidation node.
Displays each of these elements of information, period status, manager information, and financial data, in separate
tags that are navigated to for each node of the interactive hierarchical display.
Provides views for a given ledger set, for a particular accounting period, and currency.
The period status information that is displayed is broken down by application module including General Ledger, Payables,
Receivables, Asset, Projects, and Costing. Some modules track their entity at a more granular level, such as:
Business units for Payables, Receivables, and Projects
Asset Books for Assets
Cost Organization Books for Costing
The Close Monitor indicates the number of the subunits by module for the ledgers. It also displays the fractional indicator,
where applicable, of how many of the subunits are at the closed status.
Secondary ledgers, journal level, or transaction level reporting currencies cannot be associated with subledger business
units for Payables, Receivables, and Projects. As such, if the ledger set displayed in the hierarchy includes members that
are secondary ledgers, journal, or subledger level reporting currencies, the period status indicated in the Close Monitor for
such subledger modules is based on its related primary ledger. Asset books and cost organization books can be associated
with all types of ledgers. Therefore in the case of the Assets and Costing modules, their period status for secondary ledger
or reporting currencies is shown accordingly for the books directly associated with them. Otherwise, their period statuses are
derived from the books associated with their primary ledgers.
Setting Up the Close Monitor

The Close Monitor setup consists of a ledger set hierarchy definition whereby a predefined ledger set is addressed, with each
ledger and ledger set assigned a manager who is responsible for its financial close, and a logo to represent the entity in the
display.
Note: The list of managers available for assignment contains the persons defined in the Human Capital
Management (HCM) module of Oracle Fusion Applications. The attributes defined in HCM, such as the picture of
the person and contact details, are shown in the Close Monitor.
337
The ledger set serves as the foundation of this setup.

The members of the Close Monitor hierarchy must share a common chart of accounts and calendar.
The financial data displayed in the Close Monitor is derived from the account group assigned to the ledger set,
therefore, an assignment is required. The account group:
Must include two line items whose account designations respectively query the total revenues and total
expenses of the organization.
Reflects a summarized income statement in the financial data tab of the Close Monitor.
All ledgers in the ledger set share a common chart of accounts and the selection of accounts are equally applicable
throughout the nodes in the ledger set hierarchy.
When working with ledger sets that include members that are also ledger sets, you can choose any of the ledger
sets in the selector to indicate the starting ledger set to display in the Close Monitor.
If different account groups are assigned to each ledger set member in such a ledger set, the account group used to
display the financial data is the one assigned to the ledger set specified in the selector in the Close Monitor.
To have meaningful comparison and summation along the ledger set hierarchy:
Assign ledgers to the ledger set that have a relevant currency representation that matches the intended group
currency that the Close Monitor displays the financial data in.
Select the appropriate primary, secondary, or reporting currency ledger for assignment to the ledger set.
Alternately, use translated balances (balance level reporting currency) in the ledger set selection to satisfy the
common group currency requirement if needed.
Viewing the Close Monitor

You choose a ledger set, an accounting period, and currency as the view criteria for the Close Monitor display. You can alter
this selection at any time.
For example, change the currency displayed by:

Working with a global ledger set.
Shifting the focus to a lower-level ledger set that is aggregating at the continental level, such as North America, that
uses a different group currency.
Including the ledger with the relevant currency representation that matches the selected group currency that the
Close Monitor financial data is displayed in.
Note: If matching financial data for a ledger in the selected currency is not available, a message is displayed
stating that the requested financial data is not available.
The Close Monitor supports different zoom levels to enable you to:
Accommodate viewing a larger ledger set hierarchy in its entirety, given the limited display area of the user interface.
Show detail information for each node which can vary, decreasing and simplifying in content as you zoom out further
to accommodate showing more nodes in a single view.
Hover over the more summarized node to view the complete set of information for that node at the 100% zoom
level.
Leave the zoom level at 100% and move around the display to other ledger sets or ledgers currently not in view.
338
Note: A view control panel that can be exposed on demand allows you to adjust the zoom level, pan across the
hierarchy, flip the display tabs, and switch the hierarchy display format.
Configuring Social Objects in Oracle Social Network:

Explained
Before you can start using the social object, for example, accounting period, journal, or intercompany transaction in Oracle
Social Network, configure the social object using the Manage Oracle Social Network Objects task on the Setup and
Maintenance task list page.
The configuration consists of enabling the social object and its attributes for use on the Oracle Social Network. For example,
for the accounting period social object, enable the following attributes: Ledger, Period Name, Period Start Date, and Period
End Date. You also configure the enablement method of the social object. The methods are: No, Manual, and Automatic.
The configuration applies to all instances of that social object in the application and to all ledgers. You can automatically
create an conversation by setting the option in Managing Oracle Social Network Objects user interface.
Note: Oracle Social Network is currently only available in Oracle Cloud implementations.
Related Topics
Managing Oracle Social Network Objects: Explained
Configuring Social Objects in Oracle Social Network: Explained
Period Close Components: Explained

While implementing your accounting configuration, optionally define and maintain the period close components to customize
your accounting configurations setup.
Period close components include allocations, period entries, revaluation, and historical rates.
If you use allocations, revaluation, or translation, configure the following tasks under the Define Period Close Components
parent task in your implementation project:
Manage Allocations and Period Entries
Manage Revaluations
Manage Historical Rates
Manage Allocations and Period Entries

Manage Allocations and Period Entries is a manual task in the implementation project. Use the Calculation Manager to
create allocations and other formula journal templates for generating periodic journal entries automatically. Base formulas on
multiple criteria.
You must perform an external procedure outside the Setup and Maintenance work area to complete this task. To set up your
allocations rules, navigate to the Journals work area and click the Create Allocations Rules task from the Tasks pane. This
339
task navigates you to Calculation Manager, a framework that enables you define your allocation rules and formulas using a
graphical interface and intuitive step-by-step wizards.
Manage Revaluations
Defines currency revaluation options, such as the range of accounts to revalue and the gain or loss accounts. Revaluation is
done to adjust foreign entered amounts due to currency fluctuations. Navigate to the Manage Revaluations page, and define
and generate your revaluation definitions.
Manage Historical Rates

Historical rates are the weighted average rate for transactions that occur at different points in time. Used by the application to
calculate the conversion rate on equity account balances during foreign currency translation of the balance sheet.
Navigate to the Currency Rates Manager page to define and maintain your historical rates that are used in the translation
process. In Oracle Fusion General Ledger, you can currently define historical rates using an ADF Desktop Integrator
spreadsheet.
To create historical rates, specify the required Ledger and the other optional fields, as needed. Click the Create in
Spreadsheet button to open the spreadsheet for uploading.
To update the existing historical rates for your ledgers, click the Edit in Spreadsheet button, the spreadsheet is prepopulated
with the existing historical rates.
Note: Before using the historical rates spreadsheet, install the ADF Desktop Integrator client as an add-on to
Microsoft Excel.
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.
340
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
Manage Allocations and Periodic Entries
Allocation and Periodic Entries: Overview

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.
The Calculation Manager provides flexibility, automation, intelligence, and control in distributing costs and revenues across
the enterprise. In addition, the Calculation Manager:
Includes runtime variables, rules, formulas, and rule sets stored in Oracle Essbase.
Distributes revenues or costs with recursive allocation rules.
Creates complex formula rules using formula components.
Contains an Allocation Wizard to define allocation and formula rules.
Uses real-time checking of rule definitions to validate correctness of rules.
Minimizes setup and maintenance time with reusable components.
Simplifies allocation generation mechanism by integrating with enterprise schedule.
Groups rules together in rule sets and cascading allocations for efficient processing.
Creates primary, statistical, or foreign currency allocation and formula rules.
Access the Calculation Manager from the Tasks pane of the General Accounting dashboard or Journals work area by
clicking the:
Define Allocation Rules link to define or modify allocation definitions
Generate Allocations link to run the allocation process
341
Note: Adobe Flash Player 10 or higher is a required component for the Calculation Manager. Upgrade your
Adobe Flash Player if the Calculation Manager's performance slows down after upgrading your browser. For
more information, see:
Designer's Guide for Oracle Hyperion Calculation Manager
Related Topics
Designer's Guide for Oracle Hyperion Calculation Manager
Calculation Manager: Overview

The Calculation Manager creates, validates, deploys, and administers sophisticated allocation rules. In the Calculation
Manager:
Base formulas on multiple criteria, such as account balances or statistical amounts, to allocate shared revenue or
costs across multiple organizational units.
Use complex computations based on different variables to automatically calculate allocated amounts.
Group journal formulas together and executed sequentially to update account balances step-by-step.
There are three types of objects that can be created in Calculation Manager:
Components: Contain formulas, points of view, or allocation objects.

Rules: Contain components such as points of view, formulas, and templates, which are used to create allocation
calculations.
Rule Sets: Contain sets of rules that can be calculated sequentially
Note: The following are limitation in Oracle Fusion General Ledger.

Allocation rules cannot be shared across rule sets in Calculation Manager.
Within a rule or rule set, the same target or offset cannot be written to by multiple rule components.
When generating allocation rules with run time prompts other than the User Point of View in an allocation rule
component, an error occurs.
342
Oracle Essbase Balances Cubes: Overview

Oracle Essbase is embedded within Oracle General Ledger and provides multidimensional balances cubes. Every time a
transaction or journal is posted in General Ledger, the balances cubes are updated at the same time.
GL Balances
Journal
Post
Journal
Import Total for
Actual + Allocated = Allocations
GL INTERFACE Table
Allocations Engine
Journal Entries
-X =
+
Allocation
Formula
Allocation Entries Write-back
The flowing table lists and describes Essbase Dimensions and provides examples of dimension members.
Dimension Description Example
Accounting Period Based upon the calendar of the ledger or 2012

ledger set. Report on years, quarters, or QTR-1
periods. JAN-12

Ledger or Ledger Set Used to select a ledger for the reporting. InFusion North America Ledger Set
Multiple ledgers may be in the same cube if InFusion US Primary Ledger
they share a common chart of accounts.

Chart of Accounts Segments Uses a separate dimension for each of the Company: InFusion America: 101
segments from the charts of accounts. Cost Center: Sales: 400
Organized by hierarchy. A default hierarchy Account: Cash: 1110
is provided that includes all detail segment
values. Hierarchies published in the Publish
Account Hierarchies user interface are
included.
343
Dimension Description Example

Scenario Budget 2012

Indicates if the balances represented are
Actual
actual or budget amounts. Allocation-related
dimensions are predefined members and Forecast 2013
required for allocation solutions. Allocation
dimensions are not used directly by end
users.
Budget scenario dimension members are

user-defined in the Accounting Scenario
value set and appear in the cube after
running Create Scenario Dimension
Members process.
Balance Amount Indicates if the value is the beginning Beginning Balance (DR, CR, or Net)
balance, period activity, or ending balance. Period Activity (DR, CR, or Net)
Debit, Credit, and Net amounts are available Ending Balance (DR, CR, or Net)
for reporting.

Amount Type Indicates whether the amounts represent Base

Base, Period to Date, Quarter to Date, or PTD: Period to Date
Year to Date. QTD: Quarter to Date

YTD: Year to Date
Currency Used to select the wanted currency for the All ISO Currencies
balances. USD: US Dollar
JPY: Japanese yen
Currency Type Used to select the currency type of the Total

balances. Entered
Converted From (for each ISO
currency)
Creating an Allocation Rule and Generating Allocations

Watch: This video tutorial shows you how to create an allocation rule and generate allocation journals.
Allocation Security: Explained

To access the Calculation Manager, you must be assigned one or more of the four privileges and permissions.
The following privileges and permissions are associated with the Calculation Manager:
Generate General Ledger Allocation Formula - Generate Allocation and Periodic Entries: Permits generation of
allocation and periodic entries.
Define General Ledger Allocation Formula - Manage Allocation Rules or Rulesets through Calculation Manager:
Grants the ability to update allocation rules or rule sets owned by the user with view access to all allocation rules or
rule sets regardless of their ownership.
344
Define Self Managed General Ledger Allocation Formula - Manage Allocation Rules or RuleSets through Calculation
Manager: Grants the ability to update allocation rules or rule sets, but limited to the ones owned by the user.
Administer General Ledger Allocation Formula - Administer Allocation Rules or RuleSets through Calculation
Manager: Grants the ability to update all aspect of allocation rules or rule sets including the ownership attribute,
regardless of the original definition's ownership.
Migrating Allocation Rules: Instructions

Migrating Allocation Rules consists of two tasks:
1. Exporting from the Source Instance
2. Importing to the Target Instance
Exporting from the Source Instance

To export from the source instance:
1. Sign in to the Oracle Fusion Home page of the source environment with Application_Implementation_Consultant.
3. Click Manage Implementation Projects in the Task pane.
4. Click the Create icon to add an implementation project.
5. Enter the basic information and click Next.
6. On the Create Implementation Project: Select Offerings to Implement page, verify that the Include check box is
deselected for all the projects.
7. Click Save and Open Project.
8. Click the Select and Add icon to add a task.
9. Change Search to Tasks and search for Manage Allocations and Periodic Entries.
10. Select Manage Allocations and Periodic Entries and click Apply. The task is added to the Implementation
Project page in the background.
11. Click Done.
12. Click Done for the implementation project.
13. In the Tasks pane, click Manage Configuration Packages.
14. Click the Create icon to create a configuration project.
15. Search for your implementation project in the Name field and enter or modify the basic information.
16. Select the option Setup task list and setup data.
17. Click Next and then Submit.
18. Answer Yes to the message.
19. Click Refresh until the process finishes.
20. Click the Download icon, select the download Configuration Package, and save it to a local disk.
Importing to the Target Instance

This process imports the allocations and periodic entries.
To import to the target instance:

1. Sign in to the Oracle Fusion Home page of the target environment with Application_Implementation_Consultant.
3. Click Manage Configuration Packages.
4. Click Upload to upload the configuration package that was downloaded in the export process.
5. Click Browse to find the file, then Get Details, and then Submit.
6. In the Export and Import Processes, click Import Setup Data to import the data.
7. On the Import Setup Data page, accept or change defaults as needed.
345
8. Click Next to navigate through the pages and then Submit.

9. Click Refresh until the submitted process finishes.
Manage Recurring Entries

Recurring Journals: Overview
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.
Recurring Journal Types: Explained

You normally use three types of recurring journal entries to reduce data entry time and increase accuracy for journal entries
that repeat each period.
Skeleton
Dr Temporary Labor <No Amounts>

Cr Salaries Payable <No Amounts>
Standard
Dr Auto Lease Expense 10,000 dollars

Cr Amounts Payable 10,000 dollars
Formula
Dr Bad Debt Expense <Variable Amounts>

Cr Bad Debt Reserve <Variable Amounts>
1. Skeleton Journal Entries: Contain the same accounts each period, but have different amounts. After you generate
skeleton journal entries, edit the unposted journal batch by entering the journal line amounts on the Edit Journals
page.
Use skeleton journal entries to record statistical journals, such as headcount, units sold, barrels of oil, or other
statistical factors. For example, to enter headcount for your cost centers each period:
Define a skeleton entry with your headcount accounts.
346
Generate the skeleton entries.
Enter the actual headcount amounts before posting the batch.
Note: Set the journal entry to reverse automatically at the beginning of the next period if you enter the
total headcount each period. Otherwise, if you only enter the change in the headcount each period, a
reversing journal is not required.
Best practices recommend that you create skeleton recurring journal entries in spreadsheets or copy existing
journals.
To create journals in spreadsheets:
Navigator > Journals.
Select the Create Journal in Spreadsheet link to download the workbook template once.
Create and save the skeleton journal entry.
Each period open the template and enter the amount for the journal lines already in the template.
Upload the batch.
Open the journal in the Edit Journal page and add the amounts.
Once the updates are made, save, complete, and post the journal batch.
To copy journals:
Navigator > Journals > Manage Journals.
Search for the journal you want to copy.
Open the journal.
Click on the Batch Actions Menu > Copy.
Make wanted changes to the new journal.
Save, complete, and post the journal batch.

2. Standard Recurring Journal Entries: Contain the same accounts and amounts each period. Just as with skeleton
recurring journal entries, best practices recommend that you create standard recurring journals in spreadsheets.
Navigator > Journals.
Select the Create Journal in Spreadsheet link to download the workbook template once.
Create and save the standard journal entry.
Each period, upload, and submit the batch with posting selected.
The recurring journal batch is created and posted.

3. Recurring Journal Formula Entries: Contain formulas created using the formula component and allocation wizard
in the Calculation Manager. These formulas calculate journal amounts that vary from period to period and are
based on existing account balances or other criteria.
Use recurring journal entries to perform simple or complex allocations or eliminations. For example, you can allocate:
A portion of your rent expense to another division.
347
A pool of marketing costs to several departments based on the ratio of department revenues to total
revenues.
Creating Recurring Journals: Example

This example shows how to define and generate formula recurring journals that are automatically generated every period.
You must have:
A role that can access the Journals work area in Oracle General Ledger.
A duty that can access the Create Allocation Rules task.
The following assumptions apply:

The chart of accounts includes segments for company, department, account, subaccount, and product.
Account 1210 is the trade receivables account.
The period-to-date activity in account 1210 is 100,000 USD.
Here are the goals for this example.

Create a journal that populates a monthly allowance for bad debt based on 5% period-to-date activity in the trade
receivables account.
Account 7730 is the bad debt expense account and account 1260 is the allowance for bad debt account.
A formula rule must be defined to generate the following journal entry for the period Apr-17 and thereafter.
DR 01.000.7730.0000.000 5,000 USD
CR 01.000.1260.0000.000 5,000 USD
This worked example includes details for the following tasks:

1. Configuring the Formula Rule
2. Creating the Runtime Prompt Variable
3. Creating the Rule Set
4. Generating the Allocation Journal
Configuring the Formula Rule

Create a formula rule.
1. Navigate to the Journals work area.
2. From the Tasks pane, click Create Allocation Rules.
3. Navigate to the Administer menu option and then select Calculation Manager. Calculation Manager opens in a new
browser window and a cube is highlighted based on the data access set selected in the Journals work area.
4. Expand Essbase.
5. Expand VF_USA_Accounting_Flexfield (your cube).
6. Expand db.
7. Highlight the Rules row, right-click, and select New from the menu.
8. Enter the Rule Name: Special Bad Debt Allocation, accept the other defaults, and click OK.
9. The Rule Designer opens in a new tab. Under New Objects, click, hold, and drag the Point of View object. Place it
between the Begin and End nodes in the Rule Designer.
10. Enter a Caption: Point of View.
11. Perform the following steps to enter a Variable Dimension Value:
Click the Value field for Accounting Period.
Click the Actions icon and select Variable from the drop-down list. A new window opens.
348
Under Category, select Database from the drop-down list.

Click Accounting_Period.
Click OK.
12. Perform the following steps to enter other member dimension values:
Click the Value field for another dimension.
Click the Actions icon and select Member from the drop-down list.
Select a member and click the Add icon to move the member to the Selections panel.
Click OK. Repeat for all dimensions to include in the Point of View.
In this scenario, the following are fixed dimension values:
Company: 01
Department: 000
Subaccount: 0000
Product: 000
Currency: USD
Currency Type: Total
Under New Objects, click, hold, and drag the Formula component and place it between the Point of View
nodes in the Rule Designer.
Enter a Caption: Bad Debts Calculation.
Enter the offset member.
Click Next.
In this scenario, the offset is defined as account 1260, the allowance for bad debt. The offset is child combination
01.000.1260.0000.000 when combined with the fixed member dimension values in the Point of View.
13. Perform the following steps to enter the Formula member dimension value:
In this scenario, the formula member dimension value is defined as account 7730. The bad debt expense is charged
to child combination 01.000.7730.0000.000 and combined with the fixed member dimension values in the Point of
View.
Click the icon for the formula field and select Member from the drop-down list.
Select the Account dimension value, highlight the row, and click the Select icon to move the value to the
Selections panel.
In this scenario, the goal is to calculate an allowance for bad debt based on the period-to-date activity in trade
receivables account 1210. Trade receivable is child combination 01.000.1210.0000.000 when combined with
the fixed member dimension values in the Point of View.
Repeat for the other formula member values and click OK when all formula members are selected.
In this scenario, the following dimension values are selected. Selection of members for the following
dimensions is required for the source in a formula component.
Scenario: Actual
Balance Amount: Period Activity
Amount Type: PTD
Multiply the formula expression by .05.
Click the Save icon.
349
Click the Validate and Deploy icon.
Creating the Runtime Prompt Variable

Create a runtime prompt variable as an optional component of a rule. When you generate an
allocation based on a rule with a defined runtime prompt variable, you are prompted to specify a
dimension member for the variable. The variable is used in the allocation calculation.
For example, use a runtime prompt variable of Accounting Period, which prompts you to specify the period to use in the
allocation calculation. A runtime prompt variable can be created once and used in multiple rules.
3. Once the Calculation Manager opens in a new browser window, a cube is highlighted based on the data access set
selected in Journals work area. To define the runtime prompt, select Variables under the Tools menu.
4. Expand to the db under the cube, highlight the row, right-click the row, and select New from the menu.
5. The Variable Designer opens in a new tab. A default value must be entered and the variable name can't contain any
spaces. Complete the fields, as shown in this table.
Field Value
Name AccountingPeriod

Type Member

Dimension AccountingPeriod

Default Value Apr-17

RTP Selected

RTP Text Enter Accounting Period

6. Click the Save icon. The runtime prompt variable is ready for use.
Creating the Rule Set

Rule sets are created by combining two or more related rules together to enable sequential allocating
of balances.
3. After the Calculation Manager opens in a new browser window, expand to Rule Sets under the highlighted cube.
Highlight the row, right-click the row, and select New from the menu.
4. Enter the rule set name and click OK.
5. The Ruleset Designer opens in a new tab. Expand to the db under the cube for which the rule set is created, expand
the rules, and drag the rules under the rule set.
6. Click the row for the rule set, click the Variables tab, and select Merge Variables.
Merge variables means that common variables among all of the rules in the rule set are merged. You only have to
select the runtime prompt value once when submitting the Generate General Ledger Allocations process.
7. Click the Save icon.
8. Click the Validate and Deploy icon.
350
Generating the Allocation Journal

Start the allocation process to create the journal entries that populate the account balances.
2. From the Tasks pane, click Generate General Ledger Allocations.
3. Select a rule or rule set and enter any runtime prompt values.
4. Click Submit.
5. The Generate General Ledger Allocations task submits four processes consecutively (three, if the Post Allocations
option isn't is selected). The processes calculate the allocation, write the results to the GL_INTERFACE table, import
the journal batches, and post the journal batches to the General Ledger.
Scheduling Recurring Journals: Examples

You can create processing schedules for recurring journal entries that have been defined in the Calculation Manager.
Scheduling automates the monthly generation of the entries and speeds up the close process.
You can define multiple schedules for each calendar in General Ledger. These schedules can be increment by accounting
period based on any calendar defined. Schedules are shared across ledgers.
Scenario
In this example, you have created a reserve for bad debt recurring journal entry in the Calculation manager. Now, add a
recurring schedule to the entry to generate the entry once a month on the last day.
1. Navigator. The Generate Allocations > Journals > Generate General Ledger Allocations page opens.
2. Select the Rule or Rule Set: Reserve for Bad Debt.
3. Specify Accounting Period: Blank
Note: The Accounting Period field appears if you use the Run-Time Prompt in your rule and select
Accounting Period as the run-time variable.
4. Check Post Allocations.

5. Select the Advanced button.
6. Select the Schedule tab.
7. Click Using a schedule.
8. Select Frequency: Monthly.
9. Select Repeat: By Date.
10. Enter start and end dates.
351
11. Click the Submit button.
12. The generation process waits in the Schedule Processes page until the schedule time, which in this example is the
last day of the current month.
Manage Allocation Entries

Calculation Manager Toolbar: Explained
In addition to the Oracle Hyperion 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).
352
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 customize 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.
Calculation Manager Menus: Explained

Calculation Manager menus and menu options display in addition to Oracle Hyperion Enterprise Performance Management
Workspace menus and menu options. The menus and options vary depending on the view you are using and the object
with which you are working. The default view of the Calculation Manager displays the following menus when you launch
Calculation Manager, System View.
Note: This topic describes the Calculation Manager menu options only.
File Menu
Enables you to create objects, open and close objects, import and export objects, print rules, and log off.
Note: Not all of these file menu options are available for the products that use Calculation Manager.
New, Rule: Creates a rule
New, RuleSet: Creates a rule set
Edit Menu
Enables you to edit objects you select. The Edit menu is available from most of the views and from within the Rule and
Component definition pages.
Edit, Delete: Deletes an object selected in the System, List, or Custom View
Edit, Copy: Copies selected text
Edit, Paste: Pastes text from the clipboard
Edit, Copy Group: Copies a component group
Note: The Edit menu is not available within the Deployment View.
View Menu
Enables you to open different views.
View, View Pane: Displays or hides a list of existing and new objects that you can add to rules, rule sets,
components, and templates.
Note: View Pan is the only View menu option available from within the Rule Designer and Ruleset
Designer.
353
View, List View: Displays a list of the objects you select on the Filter dialog. The filter dialog enables you to create a
filtered list, by application type of applications, databases, and objects.
View, System View: Displays a list of the Essbase applications, databases, and objects to which you have access.
The System View is the default view.
View, Custom View: Displays a view that you can customize with folders that you create. This view enables you to
organize objects in a way that is meaningful to you.
View, Deployment View: Displays a list, by application type and application, of the rules and rule sets that are
deployed and not deployed with their deployment and validation status.
Tools Menu
Enable you to install other products, search for objects, create a filtered list of objects for the List View, edit the caption of an
object, and access the Variable Navigator and Variable Designer.
Tools, Filter: Opens the Filter dialog from which you can filter by application type, application, object type (rule,
rule set, formula or script component, or template), calculation type, plan type, database, deployment status, and
validation status. You can also select All to display all application types, applications, objects, and databases,
regardless of their deployment and validation status.
Tools, Variables: Opens the Variable Navigator in which you can navigate to a location for which you want to create,
edit, copy, or delete a variable. From the location you select in the Variable Navigator, you can display the Variable
Designer in which you can create, edit, copy, and delete variables for components.
Note: The two menu options listed aren't available within the Deployment view.
Actions Menu
Enables you to validate and deploy objects you select in the views and from within the Rule and Ruleset Designers. Not all of
the Actions menu options are available from within the views and designers.
Actions, Validate: Validates the rule, rule set, and formula component you selected
Note: This is the only Actions menu option available from within the Deployment View.
Actions, Deploy: Deploys the rules or rule sets you selected.

Actions, Quick Deploy: Deploys the rule in fewer steps than regular deployment by using a shortcut to one or more
applications.
Note: This feature is available only from within the Rule Designer for Essbase business rules.
Using Flow Charts: Explained

View rules and templates, and the components they include, in a flow chart within the Rule Designer. When you open a rule,
move among the components, for example, formulas, ranges, and loops, by selecting them in the flow chart. Increase or
decrease the size of the flow chart to view or hide details of the components.
When you select a component in the flow chart, its properties, usages, and other information are displayed in tabs. As
you move among the components, the tabs change. For example, if you open an allocation rule and select the formula
component in the flow chart the following properties are displayed:
Properties of the formula, such as name, description, application, and application type to which the formula belongs
354
Usages of the formula, such as which rules and templates the formula is used in.
Text of the formula, such as the variables, members, and functions, that are displayed in the tabs.
Views: Explained
Views enable you to see Calculation Manager objects in different contexts. For example, the Deployment View displays
objects according to whether they are deployed or not deployed. The Custom View displays objects according to filters and
criteria that you select.
The Calculation Manager contains the following views:
List View
System View
Custom View
Deployment View
View Pane
List View
The List View contains a filtered list of Essbase applications or databases, and objects, rule sets, rules, or formula
components, filter according to your criteria.
System View
The System View is the default view that is displayed when you start the Calculation Manager. It contains a list of all of the
applications and objects to which you have access. Your privileges are determined by the role you are assigned in Shared
Services. For each object, the owner, the user who made the last change, and the date the changes were last made are
listed.
Custom View
The Custom View enables you to create folders and move objects into them to create a view that contains only your objects.
This view enables you to organize objects in a way that is meaningful to you.
Deployment View
The Deployment View contains a list of the rules and rule sets that are deployable with their deployment and validation status.
From this view, select rules and rules sets in an application to make them deployable. Deploy one or more rules or rule sets
(partial deployment), or deploy all rules and rule sets in an application (full deployment).
View Pane
The View Pane enables you to create or open an object. Depending on whether you are working in a rule or a rule set, the
Rule or Ruleset Palette, is displayed in the View Pane. In the palette, move new and existing objects into the rule, rule set, or
flow chart.
When working with views display or hide the View Pane using the View menu. In the Custom View, move new and existing
objects from the View Pane into the custom folders you create. In the System and List views, the View Pane is hidden by
default. In the Deployment View, the View Pane is not available.
Note: The View Pane content varies depending on which view you are in and whether you are working with a
rule set, rule, template, or component.
The following table lists the tasks that can be performed from the various views in the Calculation Manager.
355
Tasks List View System View Custom View Deployment
Create, open, rename, Yes Yes Yes Yes

delete, refresh, and close
objects

Set preferences Yes Yes Yes Yes

Import and export Yes Yes Yes Yes

objects

Show the usages of Yes Yes Yes Yes

objects

Create a copy of objects Yes Yes Yes Yes

Print a business rule Yes Yes Yes Yes

Select views Yes Yes Yes Yes

Sign out Workspace Yes Yes Yes Yes

Work with favorites Yes Yes Yes Yes

Perform an advanced Yes Yes Yes Yes

search

Start help Yes Yes Yes Yes

Filter objects in the view Yes No No No

according to criteria you
specify

Work with variables Yes Yes No Yes

Validate objects Yes No No Yes

Create a shortcut to a No Yes No No

business rule

Import and export No Yes Yes No

business rules and other
objects

Validate and migrate No Yes Yes No

objects

Change the owner of an No No Yes Yes

object

356
Tasks List View System View Custom View Deployment
Deploy objects No No No Yes

Filtering Objects in the List View: Examples

You can use filters in the List View to filter objects according to:
Application Type that is populated by default with the application type, such as Essbase, your application or
database, in which you are creating the new rule.
Object type, such as allocation rules, allocation rule sets, and formula components
Deployment or validation status
Scenario
To create a filtered list of objects in the List View:
1. From the System View, select View, List View.
The Filter dialog is displayed the first time you open the List View. If you select filtering options, then close the List
View to work in the System or Custom View. When you reopen the List View, the filter dialog is not displayed. To
change the filtering options when you reopen the List View, select Tools, Filter to open the Filter dialog.
2. In the Filter dialog, on Filter Options, under Application Type, select Essbase.
3. Do one of these tasks:
For Essbase: In the Application and Object Type fields, select the applications and object types you want to
display in the List View. The default is All.
Under Deployed Status and Validated Status, clear any check boxes of selections you do not want to display.
All check boxes are selected by default.
Tip: Click Reset to reset the dialog with default values.
On Advanced Options, for Object Label, select one of these options to display only objects whose names
match the criteria:
Starts With, to display only objects whose names start with characters you specify.
Ends With, to display only objects whose names end with characters you specify.
Contains, to display only objects whose names contain characters you specify.
Matches, to display only objects whose names match characters you specify.
Enter the characters that are common to the names of the objects you want to display.
Select Ignore case to display objects whose names contain characters in either upper or lower case, even if
the case does not match the case of the text you entered in step 6.
In Created By, enter the name of the user who created objects you want to display.
In Modified By, enter the name of the user who modified objects you want to display.
For Created Date, select After, Before, or Between to display only objects that were created after, before, or
between dates you specify. Between is the default. Click the list of values to display calendars from which you
can select dates.
For Modified Date, select After, Before, or Between to display only objects that were modified after, before,
or between dates you specify. (Between is the default.) Click the list of values to display calendars from which
you can select dates.
357
For Any Text, select an option to display only objects containing text that starts with, ends with, contains,
or matches text that you enter. To display objects that include this text regardless of its case, select Ignore
case.
4. Click OK.
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.
Define Allocation Rules
358
Allocation Rules: Explained

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.
Creating an Allocation Rule: Example

You can create one or more allocation rules to use to allocate balances, as needed for financial reporting from the System
View. You can also create an allocation rule from the List, Custom, and Deployment Views.
Scenario
To create a new rule:
1. Navigator > General Accounting: Journals > Create Allocation Rules link.
2. Navigate menu > Administration > Calculation Manager.
3. File menu > New > Rule.
4. In New Rule, enter the rule's name.
5. Enter the Application Type: Essbase.
Note: The application type is populated by default with the application type in which you are creating the
new rule.
6. Select an Application Name. The application name must be a valid Essbase application such as your chart of
accounts name.
7. Select the Database.
Note: If you expand the following options in the System View: Essbase > your Application > Database
name, then right-click Rules and select New to create a new rule, the New Rule dialog is populated with
the Application Type, the Application, and the Database you are working in within the System View.
8. Click OK. The new rule is displayed in the Rule Designer.
359
Starting Calculation Manager: Worked Example

This example demonstrates how to begin to create allocations and other journal templates with formulas, to generate periodic
journal entries automatically.
Starting Calculation Manager

1. Navigate to the General Accounting, Journals work area.
2. In the General Accounting, Journals work area, click the Create Allocation Rules link.
3. In the Enterprise Performance Management System Workspace, select Administer, then Calculation Manager from
the Navigate menu.
4. In Allocation Manager, select Variables from the Tools menu.
5. Expand the Essbase tree.
6. Expand the database to which you want to add a rule set. For this example, expand VF_USA_Accounting_Flexfield.
7. Right-click the db icon and select New from the list.
Note: If the database already has a rule set, you can add a rule by right-clicking the rule set and selecting
New.
8. On the Properties tab, complete the fields, as shown in this table.
Field Value
Name Balancing_ Segment_Value

Type Member

Dimension Company

Default Value 3888

RTP Text Enter Company Text

9. Click Save.
Creating an Allocation Rule with an Allocation Component: Worked

Example
This example demonstrates how to create an allocation rule with allocation components.
You are the General Accountant for InFusion America Inc. You are creating an allocation rule with allocation components.
A rule consists of calculations that are grouped into components. When you design allocation rules, you add variables to
components. Variables assume the values that you define for them. Replacement variables provide a substitution value when
you design or generate an allocation rule.
360
Creating an Allocation Rule with an Allocation Component

1. Click the Navigator.
2. Click the Journals link under General Accounting to access the Journals work area.
3. Click the Create Allocation Rules link.
4. In the Enterprise Performance Management System Workspace, click the Navigate menu.
5. Select Administer and then Calculation Manager.
6. On the System View tab of Calculation Manager, expand the Essbase tree.
7. Expand the VF_USA_Accounting_Flexfield tree node.
8. Expand the db tree item.
9. Right-click the Rules tree item.
10. Select New.
11. In the New Rule dialog box, enter EMEA Overhead Distribution in the Name field.
12. Click OK.
You design a rule by dragging components from the Rule Palette to the Rule Designer flow chart. Each component
performs a separate task. You can add Point of View, Allocation, or Formula components to your rule.
You enter additional rule details on the Properties tab.
13. In the Rule Palette area, drag the Point of View object to the Rule Designer area.
The begin and end components of the rule appear in the Rule Designer work area.
14. On the Point of View tab, click in the Ledger field of the Dimension value table.
15. Click the Actions button for the Ledger field.
16. Select Member.
17. In the Member Selector dialog box, expand the Ledger tree, and expand the All Ledgers tree node.
18. Click the Vision Operations (USA) tree item and click Select to move it to the Selections panel.
19. Click OK.
20. Repeat the preceding steps and complete the following dimension fields, as shown in this table.
Field Value
Company "All Company Values","00"

Sub-Account "All Sub-Account Values", "0000"

Product "All Product Values", "[Product]@[000]"

Currency "USD"

21. From the Rule Palette, drag Allocation to the Rule Designer panel.
22. In the Allocate Wizard, click in the Value column of the AccountingPeriod field.
23. Click the Actions button.
24. Select Variable.
25. In the Select Variable dialog box, select Database in the Category field.
26. Click the Balancing_Segment_Value field, and click OK.
27. Click Next.
28. Click in the Select Value column of the Company field.
30. Select Member.
361
31. In the Member Selector dialog box, expand the Company tree.
32. Expand the All Company Values tree item.
33. Click the 00 tree item.
34. Click Select to move it to the Selections panel.
35. Click Next.
36. Use the preceding procedure and complete the dimension fields, as shown in this table.
Field Value Action
Department "[Department]@[000]" Member

Account an account Member

37. Click Save and then OK.
Creating an Allocation Rule with a Formula Component: Worked

Example
This example demonstrates how to create an allocation rule with a formula component.
You are the General Accountant for InFusion America Inc. You are tasked with creating an allocation rule with a formula
component.
Rules are based on formulas. The formulas use multiple criteria. For example, you can use account balances or statistical
amounts to allocate shared revenue or costs across multiple organizational units. You can define complex computations
based on variables from various charts of accounts. You can group journal formulas together and execute them sequentially
to update account balances in a step-by-step process.
Creating an Allocation Rule with a Formula Component

7. Expand the VF_USA_Accounting_Flexfield tree item.
8. Expand the db tree node.
9. Right-click the Rules tree item and select New.
10. In the New Rule dialog box, enter EMEA Overhead Distribution in the Name field and click OK.
You design a rule by dragging components from the Rule Palette to the Rule Designer flow chart. Each component
performs a separate task. You can add Point of View, Allocation, or Formula components to your rule.
You enter additional rule details on the Properties tab.
11. On the Properties tab, complete the fields, as shown in this table.
Field Value
Name Reserve for bad debts.
362
Field Value

Description This formula rule calculates the reserve needed for bad debts.

12. In the Rule Palette area, drag the Point of View object to the Rule Designer area.
13. In the Point of View area, enter POV in the Caption field.
14. Click in the Ledger field.
15. Click the Actions button for the Ledger field.
16. Select Member.
17. In the Member Selector dialog box, expand the Ledger tree.
18. Expand the All Ledgers tree item.
19. Click the EMEA_PC_PL tree item.
20. Click the Select button to move the ledger to the selected panel.
21. Click OK.
22. Repeat the preceding steps to complete the fields, as shown in this table.
Field Value
Company "[All Company Values]. [3888]"

Cost_Center "000"

Program "[All Program Values]. [0000]"

Location "[Location]@[0000]"

Division "[All Division Values]. [0000]"

Product "[All Product Values]. [0000]"

Intercompany "[All Intercompany Values]. [0000]"

Currency "USD"

Currency Type "Total"

23. Click the Actions button for the AccountingPeriod field.

24. Select Variable.
25. In the Select Variable dialog box, select Database in the Category field.
26. Select the Accounting_Period variable and click OK.
27. To define the formula, drag the Formula object from the Rule Palette to the POV loop in the Rule Designer.
28. On the Formula tab, enter Bad Debts Calculation in the Caption field.
29. Click in the Enter formula field.
30. Click the Actions button for the Enter formula field.
31. Select Member.
32. In the Member Selector dialog box, select Scenario in the Dimensions field.
363
33. Expand the Scenario tree and click the Actual tree node.
34. Click the Select button to move Actual to the Selections panel.
35. Repeat the preceding steps to select the remaining dimensions and members for the formula and complete the
fields, as shown in this table.
Field Value
Balance Amount Ending Balance

Amount Type YTD

Account 1399

36. Click OK.

37. To enter a formula to create 5 percent of total accounts receivable as reserve for bad debts, in the Enter formula
field, at the end of the formula you just created, enter *.05*-1.
38. To specify the target members, click in the Enter member name field.
40. Select Member.
41. In the Member Selector dialog box, expand the Account tree until the account 75555 appears.
42. Click account 75555.
43. Click the Select button to move the account to the Selections panel.
44. Click OK.
45. To specify offset members, on the Formula tab, enter "13005" in the Offset Member field.
46. Click Save.
47. Click OK.
48. Click the Validate button and then the OK button to acknowledge validation of the rule.
49. To deploy the rule, click the Quick Deploy button in the toolbar.
50. On the Deployment Status dialog box, click OK to acknowledge successful deployment.
Designing an Allocation Rule: Example

An allocation rule is a Calculation Manager object that consists of calculations. The calculations are grouped into
components. A rule can contain one or more components.
You create an allocation rule for an Essbase application. The rule is represented graphically in a flow chart into which you can
drag and drop components to design the rule.
Scenario
To design an allocation rule:
1. Navigate to the Journals work area and click the Create Allocations Rules task from the Tasks pane.
2. Click Navigate > Administration > Calculation Manager.
3. In the System View, perform one of these tasks:
Click File > New > Rule. Expand the Essbase Application Type, the Application, and the Calculation Type,
Plan Type, or Database.
Right-click Rules and select New.
364
4. In New Rule, enter the rule's name, the Application Type Essbase, and the Application Name. The application
name must be a valid Essbase application.
6. OK.
Note: If you right-click Rules and select New to create a new allocation rule, the New Rule dialog is
populated with the Application Type, the Application, and the Calculation, Plan Type, or Database
you are working in within the System View.
7. To design the allocation rule, from the Rule Palette, drag new and existing objects, and drop them into the flow
chart within the Rule Designer.
Note: You can also create objects such as formulas and scripts independently of the rule, and add them
to the rule later.
8. From New Objects, drag and drop these components to insert a new component into the rule's flow chart:
Point of Views:
Allocations:
Formulas:
9. On Properties, enter properties for the rule.
Note: The number and contents of the tabs change as you add components to the rule and move
along the rule's components in the flow chart. To enter properties and other information for the rule's
components, select the component in the flow chart. You can optionally:
Edit the name by entering a new one of up to 50 characters. The name defaults from the New Rule
dialog.
Enter a description of up to 255 characters for the rule.
Enter a caption for the rule. The caption displays in the flow chart.
Enter comments for the rule. For example, you may want to tell the users how to use the rule.
10. For Essbase: On Global Range, specify what dimensions are common to all of the components in the rule by
selecting values, for example, members, variables, and functions for each dimension. The values you select for the
dimensions are the values that are calculated when the rule is launched.
a. Select values for a dimension by clicking its row in the Select Value column.
b. When the Actions icon is displayed, click the icon, and select one of these:
Variable
Member
Function
11. For Essbase: On Variables, select Merge Variables to merge all instances of the same variable used in the
allocation rule so only the first instance of each variable is displayed when the rule is launched. If you do not select
this check box, all instances of each variable are displayed.
Note: If you select Merge Variables, the first value that the user enters for the runtime prompt is used
for all subsequent occurrences of that runtime prompt during validation and launch.
365
12. On the Usages tab, you view which allocation rules and rule sets use the rule, if any. You cannot edit any of the
information about this tab. The following information is displayed for the allocation rules and rule sets using the
allocation rule:
Names
Application Name
Deployment Status
Validation Status
Description
Note: By default, an allocation rule is not used by any allocation rules or rule sets when create.
13. Repeat these steps for each component you want to add to the allocation rule.
Note: As you add components to 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. You can use the zoom bar
to zoom in and out within the flow chart. You can select a component to view its properties and edit a
component on the Properties tab.
14. Select File, Save.

15. After you design and save the rule, you can do any of these tasks:
Print it.
Validate it.
Deploy it.
Generate it from within Oracle General Ledger by navigating to the Journals work area and clicking Generate
General Ledger Allocations from the Tasks pane.
Editing Allocation Rules: Example

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:
366
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
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
367
Printing Allocation Rules: Example

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
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.
368
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 Define 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:
3. In the System View, expand the Essbase Application Type, the Application, or Database, and Rules.
Right-click the rule you want to open, and select Open.

Select the rule you want to open, and select File, Open.
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.
369
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.
Define Allocation Rule Sets
Allocation Rule Sets: Explained

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.
Creating an Allocation Rule Set: Example

You can create an allocation rule set from the System View. You can also create an allocation rule from the List, Custom, and
Deployment views, and from within the Ruleset Designer.
Scenario
To create an allocation rule set:
2. Navigate menu > Administer > Calculation Manager.
3. Enter the rule set's name.
4. Enter the application type: Essbase.
5. Select an application name.
6. Select a database.
370
Note: From the System View, if you right-click RuleSets and select New to create an allocation rule set,
the New Ruleset dialog is populated with the application type, application, and database in which you
are working.
7. Click OK. The new rule set is displayed in the Ruleset Designer.
Creating an Allocation Rule Set With Deployment: Worked Example

This example demonstrates how to create an allocation rule set.
You are the General Accountant for InFusion America Inc. You are tasked with creating an allocation rule set.
You create rule sets by combining two or more related rules (or rule sets) so you can launch the rules or rule sets sequentially.
Creating an Allocation Rule Set

7. Expand the VF_USA_Accounting_Flexfield tree item.
8. Right-click the Rules tree node and select New.
9. In the New RuleSet dialog box, enter EMEA Overhead Distribution, and click OK.
10. Expand the VF_USA_Accounting_Flexfie tree in the Rule Set Palette, then expand the db tree node and then the
Rules tree node.
11. Drag EMEA Overhead Distribution from the Rule Set Palette to the Ruleset Designer panel.
12. Drag EMEA - Allocation of Indirect Costs from the Rule Set Palette to the Ruleset Designer panel.
13. Click EMEA Overhead Distribution Rule Set in the Ruleset Designer.
14. Click the Variables tab in the lower panel of the work area.
15. Select Merge Variables.
If a rule set has the same variable used across rules in a rule set, you can merge the rules. Then at generation time,
the input is taken from that variable as the run time prompt.
16. Click Save and then OK.
Before you deploy rule sets, you validate them to ensure that there are no syntax errors. Validation ensures that all of
the following criteria are met:
All members of all dimensions in the application are valid.

All functions exist, have the correct number of parameters, and are valid for the application type.
All variable references that are used in rules are valid. Replacement variables are replaced with the correct
strings and then validated.
The generated script contains no syntax errors.
You can deploy rules and rule sets to Oracle Fusion General Ledger. You execute a partial deployment by deploying
one or more (but not all) rules and rule sets. You execute a full deployment by deploying all rules and rule sets in the
current application.
371
Rules and rule sets that are deployed can be generated from the Allocation Generation page.
To deploy multiple rules and rule sets but not all; in Deployment View, select the check boxes of the rules and
rule sets that you want to deploy.
To deploy only one rule or rule set in the current application; then in Deployment View, select the one rule or
rule set option.
Designing an Allocation Rule Set: Example

After you create a rule set in the New RuleSet dialog, the rule set is displayed in the Ruleset Designer.
Scenario
To create an allocation rule set:
1. Navigate to the Journals work area and select Create Allocation Rules from the Tasks pane.
2. From the Navigate menu, select Administration, then Calculation Manager.
3. In the System View, expand the Essbase application type and the application.
4. For Essbase: Right-click RuleSets and select New.
Note: For Essbase applications, only one rule sets node for each application at the same level as the
databases.
5. In New RuleSet, do these tasks:
a. Enter the rule set's name

b. Select the Application Type as Essbase
c. Select the Application Name.
d. As you selected Essbase as the application type, select the Database.
e. OK.
6. In the Ruleset Designer, to create the rule set, from Ruleset Palette, drag existing rules and rule sets and drop
them into the flow chart.
Note: You can use the Move Up and Move Down icons on the Ruleset Designer pane to reorder the
rules in the rule set. Rules in General Ledger applications are launched sequentially within a rule set, so the
order of the rules is important.
7. On Properties, enter properties for the rule set. In the Ruleset Designer, if you select a rule or rule set within the
rule set you are creating; its properties are displayed on Properties instead of the new rule set's properties.
Optionally, enter the following:
a. The name by entering a new one of up to 50 characters. The name defaults from the New RuleSet dialog.
b. A description of up to 255 characters for the rule set.
c. Comments for the rule set. For example, you may want to enter a comment that describes what the allocation
rule set does.
372
8. On Usages tab, you view which allocation rules and rule sets use the rule, if any. You cannot edit any of the
information about this tab. The following information is displayed for the allocation rules and rule sets using the
allocation rule:
a. Names
b. Database
c. Application Name
d. Deployment Status
e. Validation Status
f. Description
Note: By default, a rule set is used by no other rule sets when you create it.
9. On Variables, select Merge Variables to merge all instances of the same variable used in the rules within this rule
set so only the first instance of each variable is displayed when the rule is launched. If you do not select this check
box, all instances of each variable are displayed.
Note: If you select Merge Variables, the first value that the user enters for the runtime prompt is used
for all subsequent occurrences of that runtime prompt during validation and launch.
Adding an Allocation Rule to an Allocation Rule Set: Examples

You can add an allocation rule to an allocation rule set that belongs to the same application type. The rules in the rule set can
be launched sequentially or simultaneously.
Scenario
To add an allocation rule to an allocation rule set:
1. In the System View, expand the Essbase Application Type and the Application.
2. Expand RuleSets, right-click the rule set you want to open, and select Open.
Note: Only one rule set node exists for each application at the same level as the plan types and
databases.
3. In the Ruleset Designer, in Existing Objects, expand the application and the plan type or calculation type that
contains the rule you want to add.
4. To add the rule, drag and drop it into the Ruleset Designer.
5. Repeat step 4 for each rule you want to add to the rule set.
Editing Allocation Rule Sets: Examples

You can edit the following properties of an allocation rule set:
Allocation rule components
Allocation rule name
373
Allocation rule description

Allocation rule comments
Scenario
To edit an allocation rule set:
1. Navigator > General Accounting > Journals > Create Allocation Rules link.
3. In the System View, expand Essbase Application Type and the Application.
4. Expand your rule set by right-clicking the rule set you want to edit, and selecting Open.
databases.
5. In the Ruleset Designer, add, copy, delete and change the order of new rules and rule sets:
a. To delete a rule or rule set from the rule set, select the rule or rule set, right-click it, and select Remove.
b. To add a rule or rule set to the rule set, from Existing Objects, drag existing rules and rule sets from Essbase
applications, and drop them into the Ruleset Designer.
Note: The rules and rule sets you add to the rule set must belong to the same application type as
the rule set you are editing.
c. To open a rule or rule set in the rule set, right-click the rule or rule set, and select Open.
d. To reorder the rules and rule sets within the rule set, you can use the Move Up and Move Down icons on the
Ruleset Designer pane.
6. On Properties, edit properties of the rule set. (In the Ruleset Designer, if you select a rule that you added to this
rule set, the properties are displayed on the Properties tab.)
7. Optional: Edit the name by entering a new one of up to 50 characters. (The name defaults from the New RuleSet
dialog.)
8. Optional: Edit the description by entering a new one of up to 255 characters.
9. Edit the Enable Parallel Execution selection. If you want the rules and rule sets in the rule set to run
simultaneously, select this option, to run sequentially, clear this option. By default, the rules and rule sets in a rule set
run sequentially: each rule or rule set in the rule set must run without errors before the next rule or rule set is run.
10. If the rule set contains nested rule sets which have a different Enable Parallel Execution setting than the parent rule
set, the setting of the nested rule set applies. For example, if you have rule set1 that is marked for parallel processing
and it contains rule1, rule2, and rule set2 that is marked for sequential processing, the rules and rule sets in rule set2
are processed sequentially, even though rule set1 is marked for parallel processing.
11. Edit the comments.
12. On the Usages tab, you view which allocation rules and rule sets use the rule, if any. You cannot edit any of the
information that appears on this tab. The following information is displayed for the allocation rules and rule sets
using the allocation rule:
a. Names
b. Calculation or Plan Type
c. Application Name
f. Description
374
Copying an Allocation Rule Set to Another Application: Example

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:
2. Expand RuleSets.
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.
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.
Saving an Allocation Rule Set: Example

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.
375
Saving an Allocation Rule Set with a Different Name: Example

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.
Deleting an Allocation Rule Set: Example

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.
Refreshing Allocation Rules or Allocation Rule Sets: Example

In the System View, you can refresh any level of the application list. You can refresh:
Application Type
Application
Database
376
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.
Showing the Usages of a Rule or Allocation Rule Set: Example

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
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.
377
Changing the Owner of an Object: Example

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.
FAQs for Define 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.
378
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.
Working with Point of View and Allocation Components
Working with Point of View Components: Overview

Every data value in a report is derived from the intersection of a member from each dimension in the Essbase database
connection. Oracle Fusion Financial Reporting enables a designer to place these dimensions on the report grid or user point
of view (POV). Report viewers can change the member selected for dimensions on the user POV. This enables report viewers
to customize the reports to fit their needs. The user POV can also be used in books.
You create and edit POV components from within a rule to set members, variables, and functions that comprise the global
range of the POV component. You nest a POV of View component within another POV 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.
Creating a Point of View Component: Example

You create a Point of View component from within a rule to set members, variables, and functions that contain the global
range of that Point of View component.
You can also define or edit the caption that displays in the flow chart and the comments that are entered for the values
selected for each of the dimensions in the Point of View.
379
Scenario
To create a Point of View component:
3. In the System View, select File menu, New, Rule. Expand the Essbase Application Type, the Application, and the
Calculation Type, Plan Type, or Database and Rules.
4. Right-click rules you want to open, and select Open. The rule is displayed in the Rule Designer.
5. After you determine where in the rule's flow chart you want to create the Point of View component, from the New
Objects Palette, drag the Point of View component and drop it into that location in the flow chart.
6. On the Point of View tab, enter a caption to identify the Point of View component. The caption is displayed in the
flow chart of any rule that uses it.
7. Optional: Perform one of these tasks to define the Point of View global range:
a. Click Variable Selector to select or create variables to define the Point of View. If you select a variable, you
can select Link Variable Dynamically to ensure the variable is updated dynamically when changes are made
to it.
b. Click Member Selector to select members to define the Point of View.
c. Click in the row of a dimension in the Value column to type the names of members that define the Point of
View.
d. Click in the row of a dimension, click the Actions icon, and select one of these options to enter members:
Members
Variables: You can use a variable to fill the Point of View component. The variable must be defined at
the database level and must be of the Member Range type.
Functions: The functions you enter should return level 0 members only and should include the at sign @
before the function name. You can enter these functions:
@Level0Descendant
@Sibling
@UDA
@Attribute
Note: The Level0Descendant and Sibling functions require a member name as a

parameter.
Note: If a global range is defined for the rule for which you are creating the Point of View component, the
Point of View tab displays the rule's member selections by default. To see if a global range is defined
for the rule, select the Begin or End tab in the flow chart. Then click the Global Range tab to see if any
members, functions, or variables are defined.
8. To enter a comment for the members you select for a dimension, click Comment.
9. Click Reset Grid to clear any entries you made to the grid.
380
Editing a Point of View Component: Example

You can edit the members, variables, and functions that contain the global range of the Point of View component. You can
also edit the caption that displays in a flow chart and the comments that are entered for the values selected for each of the
dimensions in the Point of View.
Scenario
To edit a Point of View component:
Calculation Type, Plan Type, or Database.
4. Right-click the rule, and select Open.
5. In the Rule Designer, select the Point of View component you want to edit in the flow chart to display its properties.
You can edit any of these properties of a Point of View component.
a. The caption displays in the rule's flow chart.
b. The members, variables, and functions that define the Point of View.
c. Whether any variables used in the Point of View component are updated dynamically when changes are made
to the variables.
d. Whether comments are entered for the dimensions and members that define the global range of the Point of
View.
e. Whether the values of the members in the Point of View component are calculated when the rule to which it
belongs is validated or launched.
Working with Allocation Formula Components: Examples

An allocation formula component is composed of formula calculation statements. These examples show performing the
following actions on formula components:
Creating
Opening
Editing
Deleting
Copying and pasting
Showing usages
Creating Formula Components

To create the calculation statements of a formula, you enter or select members and variables. As you create the formula,
each of its calculation statements is listed in a row within a grid in the Component Designer. You can create a formula
component from the System View or from within the Rule Designer. A formula component exists as an independent object
in the database, so it can be shared among allocation rules.
1. From the System View, expand the Essbase Application Type, the Aggregate Storage Application, and the
Database.
381
2. Right-click Formulas, and select New.

3. Enter the formula's Name.
4. Enter the Application Type (Essbase).
5. Select an Application Name such as Vision Chart of Accounts. The application name must be a valid Essbase
aggregate storage application.
6. Select the Essbase Database.
Note: Right-click Formulas, and select New to create a new formula, the New Formula dialog. The
dialog is populated with the application type, the application, and the database you are working in within
the System View.
7. Click OK. The formula is displayed in the Component Designer.
8. In the Component Designer, on Properties tab, optionally complete these steps:
a. Verify that the Shared check box is selected by default.
Note: You cannot select or clear the Shared check box. To create a formula that is not shared,
open an allocation rule, and then drag a new formula component into the allocation rule's flow
chart. The shared check box is not selected. If you decide to make the formula shared, select the
Shared check box.
b. Edit the formula's name by entering a new one of up to 50 characters. The name defaults from the New
Formula dialog.
Note: Names of members in Essbase aggregate storage applications can be the same. If there
is a name that is not unique, the name is marked when the object is validated. If this occurs, you
must enter the full path for the member. The full path syntax is [Dimension name]. [Parent name].
[Member name.]
c. Enter a description of up to 255 characters for the formula.
d. Enter a caption for the formula. The caption is displayed in the Rule Designer flow chart. If you do not enter a
caption, the component's name is displayed in the flow chart.
e. Enter comments for the formula. For example, you may want to tell users how the formula component should
be used.
9. On Formula, enter a caption for the formula.
10. The Offset Member is the total amount of all of the formulas in the formula component. Click the Ellipsis icon to
select a member.
Note: You can define an offset member manually within the formulas that you create. The offset defined
in the formula component is calculated as the sum of all calculated amounts.
11. To create a formula statement, click in the first formula statement row before the equal sign. Then enter a member or
cross dimension member selection, or click Actions to select:
A variable
One or more members
12. To complete the formula statement, click in the row after the equal sign. Then enter a member or cross dimension
member selection, or click Actions to select a variable or member.
13. For each formula statement row, click the Comments icon to enter optional comments about the formula statement.
382
14. On Usages, you can view the rules that use the formula component.
15. Select File > Save.
Opening Formula Components

You can open a formula component from the System View or within the Rule Designer flow chart of a rule that uses the
formula component.
Database.
2. Expand Formulas.
Right-click the formula you want to open, and select Open.
Double-click the formula you want to open.
Note: The formula component opens in the Component Designer. To open a formula component
within a rule, open it from within the rule's flow chart by right-clicking the formula component. Select
Open or double-click the component.
Editing Formula Components

You can edit the formula statements that contain a formula component and the formula component's comments, caption,
name, and description.
Database and the Formulas.
2. Select the formula component you want to edit.
3. Right-click the formula component, and select Open.
4. In the Component Designer, you can edit any of these properties of a formula component:
Caption
Formula statements
Name
Description
Comments
Deleting Formula Components

You can delete a formula component only if the component is not being used in any allocation rules. To see if any allocation
rules are using the formula component, you can show the formula component's usages.
If the formula component is being used by a rule, and you don't want the formula component, remove it from the rule, then
delete it. If the formula component is being used in a rule, and you no longer need the rule, you can delete the rule. If no
allocation rules use the formula component, you can delete the component.
To delete a formula component:

1. In the System View, expand the Essbase application type, the Essbase aggregate storage application, the database,
and Formulas.
2. Right-click the formula you want to delete, and select Show Usages to make sure no allocation rules are using the
formula component.
3. Remove the formula component from any allocation rules that are using it.
383
4. In the System View, right-click the formula you want to delete, and select Delete.
5. Confirm deletion of the formula.
Copying and Pasting Formula Components

You can copy a formula component from a rule and paste it into the same, or a different, rule. You can also copy the contents
of the grid within a formula component and paste the contents into the same, or a different, formula component. You cannot
copy a formula component and paste it into another formula component or another component type.
To copy and paste a formula component:

and Rules.
2. Right-click the rule that contains the formula component you want to copy, and select Open.
3. In the Rule Designer flow chart, right-click the formula component you want to copy, and select Copy.

To paste the formula component into the same rule flow chart, right-click in the location of the flow chart, and
select Paste.
To paste the formula component into a different rule flow chart, open the rule where you want to paste the
component. Then right-click in the location, and select Paste.
Showing a Formula Component's Usages

You can see which allocation rules are using a formula component, and other information, by displaying the formula
component's usages from the System View.
To show a formula component's usages:

and Formulas.
2. Right-click the formula whose usages you want to see, and select Show Usages.
3. You can view this information about the formula component:
The names of the allocation rules that are using the formula component.
The application names of the allocation rules that are using the formula component.
The database names of the allocation rules that are using the formula component.
The owner of the formula component.
Whether the allocation rules that are using the formula component are deployed.
Whether the allocation rules that are using the formula component are validated.
A description of the allocation rules that are using the formula component.
Note: You can also view a formula component's usages from within the Component Designer on the Usages
tab.
Creating an Allocation Component: Example

You create an allocation component from within a rule; it exists only in that rule and cannot be shared among allocation rules.
384
Scenario
To create an allocation component:
Calculation Type, Plan Type, or Database.
4. Right-click the rule you want to open, and select Open. The rule is displayed in the Rule Designer.
5. After you determine where in the rule's flow chart you want to create the allocation component, from the New
Objects Palette, drag the Allocation component and drop it into that location in the flow chart.
6. In the Calculation Manager, on the Point of View tab, for each dimension listed that you do not want to vary during
the allocation, do one of these tasks, and then click Next.
a. Select a predefined selection from Use Predefined Selection to populate the dimensions listed with values.
b. Click the Member Selector icon to select members and variables for each of the dimensions listed. Make
sure that all members you select are valid level 0 members.
c. Select a dimension in the list, and click Actions to select a member or variable.
Note: If you drop a Point of View component within another Point of View component, the second
Point of View inherits the members, variables, and functions from the first Point of View. In the
Member Selector, the dimensions listed in the current step are available for selection from
Dimension. This enables you to select members and functions for any of the dimensions listed in
the current step.
7. In the Calculation Manager, on the Source for each dimension listed, select a member whose data you want to
allocate by doing one of these tasks. You must select a member for each dimension listed. The source members can
be members that are not level 0.
If the predefined selection does not enter a value for each dimension listed, you must enter a value for any
dimensions that are empty.
b. Click the Member Selector icon to select a member for each of the dimensions listed.
c. Select a dimension in the list, and click Actions to select a member or variable. You cannot use functions in
this step of the Allocation component.
d. Optional, to allocate a specific value, enter an amount to be allocated instead of the selecting members.
8. If the source amount you want to allocate is zero, select one of these options from the drop-down list.
a. Select the next pool record.

b. Stop processing the allocation.
9. Click Next.
10. On Allocation Range, enter the parent member for the dimensions you want to use for the allocation. To enter the
parent member, do one of these tasks, and then click Next.
b. Click the Member Selector icon to select the parent member for the dimension to which to allocate the data.
c. Enter a parent member, or select a dimension in the list. Click the Actions icon to select the parent member
(of the main dimension) to which to allocate the data. The data is allocated to the level 0 member (that is, the
lowest member in the outline, with no members under it).
385
11. On Target, for the remaining dimensions, select a level 0 member to which to allocate the data. Perform one of
these tasks and click Next.
b. Click the Member Selector icon to select members for each of the dimensions listed.
c. Select a dimension in the list, and click the Actions icon to select a member or variable.
12. On Offset, perform one of these tasks and click Next:
Note: You must specify members for the offset; you cannot leave it empty.
13. Optional: On Exclude, select any members you want to exclude from the allocation. Perform one of these tasks and
click Next.
14. On Basis perform these tasks:
a. Select an allocation method to specify how the data should be allocated.
i. Select Allocate evenly to allocate data values in the allocation range evenly. Then on Basis Options
for evenly method, specify what you want to be done if the basis is negative, zero, has missing
values, or if all members are excluded.
ii. Select Allocate using a basis to calculate a percentage to be applied to each member in the
allocation range. Then on Basis Options, specify what you want to be done if the basis is negative or
equal to zero.
b. Any dimension members you do not specify are inherited from the Point of View you defined previously, but
you can override those Point of View selections by doing one of these tasks:
i. Select a predefined selection from Use Predefined Selection to populate the dimensions listed with
values.
ii. Click the Member Selector icon to select a member for each of the dimensions listed.
iii. Select a dimension in the list, and click the Actions icon to select a member or variable.
15. Click Next.
16. On Rounding, complete these steps. The members you select in this step must be a part of the allocation range.
a. Enter the number of decimal places to use for this allocation, or click the Actions icon to select a member or
variable that represents this value.
b. Select where to place the rounding difference.
i. Select Define location to specify a member or members on which to place the rounding difference.
Perform the following steps.
a. Select a predefined selection from Use Predefined Selection to populate the dimensions listed
with values.
b. Click the Member Selector icon to select a member for each of the dimensions listed.
386
ii. Select Use biggest value to round data values to their largest values.
iii. Select Use smallest value to round data values to their smallest values.
iv. Select Discard rounding error to use allocated data values as they are.
17. Click Finish.
Editing an Allocation Component: Example

You can edit an allocation component by opening the rule to which it belongs. When the rule is displayed in the Rule
Designer, you can view the allocation component's properties by selecting it in the rule's flow chart.
Scenario
To edit an allocation component:
Calculation Type, Plan Type, or Database and Rules.
4. Select the rule that contains the allocation component you want to edit.
5. Right-click the rule, and select Open.
6. In the Rule Designer, select the allocation component you want to edit in the flow chart to display its properties.
You can edit any of these properties of an allocation component.
a. The member whose data you want to allocate.
b. The level 0 members to which you want to allocate data.
c. The data and the amount of the data you want to allocate.
d. How you want the data processed:
The total amount of the data allocated written to an offset member.
The data allocated evenly or in different amounts using a driver.
The allocated data rounded, and if so, how it should be rounded.
Removing Members and Functions from an Allocation Component:

Worked Example
You can remove members from formula, script, condition, and member and data range components. Similarly, you can
remove functions from formula, script, and condition components.
When you remove members and functions from a component, they are not deleted from the database. To remove members
and functions from a shared component, you must first ensure that the component is not shared.
Remove Members or Functions from a Component

To remove members or functions from a component:
1. In the System View, expand the application type, the application, the calculation type or the database (Essbase).
2. Expand Rules or Templates, depending on whether the component is in a rule or template.
3. Right-click the rule or template that contains the component you want to add a member to, and select Open.
387
4. When the rule or template opens, in its flow chart, select the component that contains the member or function you
want to remove.
5. Click the Actions icon, and select Member.
6. From Dimensions > Member Selector, select the dimension that contains the member or function you want to
remove.
7. Click the Deselect icon to move the member or function from the Selections panel to the Members or Functions
panel.
8. To remove members from multiple dimensions, click Next, and repeat steps 5 and 6.
9. Click OK.
10. Select File > Save.
Searching for Members: Worked Example

You can search for members within the Member Selector.
Searching for Members

To search for members:
1. In the System View tab, expand the Essbase application type.

2. Expand the application, the calculation type (Financial Management), the plan type (Planning), or the database
(Essbase).
4. Right-click the rule or template that contains the component for which you want to search for members, and select
Open.
5. When the rule or template opens, in its flow chart, select the component for which you want to search for members.
6. Click the Actions icon, and select Member
7. In Member Selector window, select the dimension that contains the member for which you want to search.
8. Optional: From the Menu icon you can customize the display of members in the Member Selector window by
performing these tasks:
Select or clear the options in Show to display or hide the member's name, alias, description, and count. (By
default, the name and alias of the member is displayed.)
Select Collapse All to hide the members in the dimension you selected. (By default, the outline is collapsed
when you select a dimension.)
9. Select the Search tab.
a. From the Find field, select a type of member to search for, a member name or its description.
b. Enter the name of the member, or its description, to search for, or to display all members in the dimension,
accept the default wildcard.
c. Click Search.
If the member is found, the member is selected in the Results section. If more than one member matches your
search criteria, locate the appropriate members from the list.
d. Optional: Click Advanced Search to search for the member by name, alias, or one of its properties.
e. Select the member or members, and click the Select icon to move them to the Selections panel.
10. Click OK.
388
Searching for Members by Name, Alias, or Property: Worked

Example
You can use Advanced Search within the Member Selector to search for a member by name, alias, or one of its properties.
Searching for Members by Name, Alias, or Property

To search for a member by name, alias, or property:
1. From the Member Selector, select the Search tab, and click Advanced Search.
2. In Find Members > Search By, select one of these options:
Name: To search for the member by its name. Then move to step 4.
Alias: To search for the member by its alias. Then move to step 4.
Property: To search for the member by one of its properties. Then move to step 3.
3. If you selected Property, enter or select a Property Name.
4. Enter a value for the name, alias, or property.
5. Click OK. If the alias, name or property is found, the field is selected in the outline on Members.
When you search for members by alias, all members that have aliases matching the search criteria are highlighted in
the outline, even members with aliases in other languages are highlighted. However, only aliases for members in the
language being used are displayed in the Member Selector.
6. Optional: If more than one member matches your search criteria, locate the appropriate members from the list.
FAQs for Working with Point of Views and Allocation Components

How can I open a point of view or an 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.
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.
389
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:
If you want 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.
If you want 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 an 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 belongs to.
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.
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.
Use Allocation Variables
Working with Variables: Explained

Variables assume values that you define for them. You can use them in components while designing allocation rules and
templates.
390
You can create variables from the System View and from within the Component Designer by starting the Variable
Designer. When you create a variable within the Component Designer, the variable is associated with the rule that contains
the component. You can also create variables from the System View, and associate them with allocation rules, calculation or
plan types, databases, or applications that you select.
Two types of variables exist.

Execution: When the rule is started, the calculation defined for the variable is performed. You can use execution
variables in formula, condition, or loop components.
Note: Execution variables are not supported in Essbase aggregate storage applications, including those
used in Oracle General Ledger.
Replacement: When you are designing or creating the rule, the variable is substituted with a calculation. You can
use replacement variables in formula components.
You can create several types of execution and replacement variables.
Note: The variables you can create differ depending on what application type you are working in and
whether you are creating an execution or replacement variable.
You can create variables that prompt users to enter information when they start a rule. These run time prompt variables
prompt users for information regarding members, text, dates, or numbers. The prompts indicate the type of data that is
expected.
Up to four database objects with which you can associate a variable exist, depending on which application type you are
creating a variable for. A variable can exist in multiple objects simultaneously and can have the same name in each object.
For all user use Application. If you select application, the variable can be used within the application with which you
are working when you create the variable.
For Essbase users use Database. If you select database, the variable can be used within the database you are
working when you create the variable.
For Essbase users use Rule: If you select rule, the variable can be used within the rule with which you are working
when you create the variable.
Creating a Variable from the System View: Worked Example

You can create a variable from the System View or from within the Component Designer by running the Variable Designer.
Creating a Variable from the System View

You can create a variable from the System View or from within the Component Designer by running the Variable
Designer.
To create a variable from the System View:

1. In the System View, select Tools > Variables.
2. In the Variable Navigator, expand the Essbase application type.
3. Essbase users: Right-click an application, and select New to create a variable that can be used in that application
only.
4. Enter a description for the variable.
391
5. If you include this variable in a group, enter the group name. The group name is displayed under the Group column
after you save and refresh the variables.
6. If the variable is a runtime prompt variable, select Use Last Entered Value. The prompt the user last entered is
displayed as the default value the next time the prompt occurs.
This option can be selected only if the variable has runtime prompts.
7. In the Value table, enter values for the variable. The values you enter change depending on the selected variable
type.
Repeat these steps for each variable you want to create.
Entering Variable Values for a Numeric Variable: Worked Example

A numeric variable can be Essbase replacement variable.
Entering Values for a Planning or Essbase Numeric Variable

To enter values for an Essbase numeric variable:
1. In the System View, select Tools, Variables.
Right-click an application, and select New to create a variable that can be used in that application only.
Right-click a database, and select New to create a variable that can be used in that database only.
Right-click a rule, and select New to create a variable that can be used in that rule only.
4. From Type, select Numeric.
5. Enter a default value for the variable.
Entering Variable Values for a String Variable: Worked Example

A string variable can be an Essbase replacement variable. A string variable must be alphanumeric and not more than 255
characters. It can contain a null value, but cannot contain a leading ampersand (&) character in the value.
Enter Values for a Planning or Essbase Replacement String Variable

To enter values for an Essbase replacement string variable:
1. In the System View, select Tools , Variables.
4. From Type, select String.
5. In the Value table, enter a value for the variable.
6. By default, RTP is selected. If you do not want to create a run time prompt for this variable, clear RTP.
392
If you do not select RTP, you must enter a value for the variable.
7. If you selected RTP, enter the run time prompt text you want to display for users.
Entering Values for an Array Variable: Worked Example

An array variable can be an Essbase execution variable. Arrays contain a list of values that can be multidimensional.
Typically, arrays are used to store variables as part of a member formula. The size of the array variable is determined by the
number of members in the corresponding dimension. For example, if the Scenario dimension has four members, the following
command creates an array called Discount with four entries. You can use more than one array at a time.
Array Discount
To enter values for an array variable:

4. From Type, select Array.
5. In the Value field, enter a value for the variable.
Entering Values for a Member Range Variable: Worked Example

A member range variable can be an Essbase replacement variable. The member range variable should contain a range of
members inclusive of, and between, two specified members.
Entering Values for a Member Range Variable

To enter values for a member range variable:

5.
6. From Type, select Member Range.
393
7. In the Value table, do the following: is you are creating a member range for Essbase.
a. If you are creating a member range variable for Essbase:
i. For each dimension for which you want to define a member range, enter or use the Member Selector
to select limits for the member range. (The dimensions that display are the dimensions that belong to
the application for which you are creating the variable.)
Note:
ii. Enter or use the Member Selector to select values for the member range. You can select multiple
members and functions for each dimension listed.
Entering Variable Values for a Cross Dimension Variable: Worked

Example
A cross dimension variable is an Essbase replacement variable. It contains a range of members from multiple dimensions that
enable you to run allocation rules across dimensions.
Entering Values for a Cross Dimension Variable

To enter values for a cross dimension variable:

4. From Type, select Cross Dimension.
5. For each dimension listed, in the Value table, enter or use the Member Selector to select limits for the variable.
You must select RTP before you enter text in the Limits field.
6. Enter or use the Member Selector to select a value for the variable. You can select a member or a function.
7. Repeat step 5 through step 6 to select values for the all of the dimensions.
Entering Variable Values for a Dimension Variable: Worked Example

A dimension variable is an Essbase replacement variable. This variable contains a dimension that you select.
Enter Values for a Dimension Variable

To enter values for a dimension variable:

394

4. From Type, select Dimension.
5. In the Value table, select a dimension. The dimensions displayed belong to the application for which you are creating
the variable.
Entering Variable Values for Members Variable: Worked Example

The member and member variables are Essbase replacement variables. These variables contain a member or multiple
members from a dimension that you select.
Enter Values for a Member or Member Variable

To enter values for a member or members variable:
4. From Type, select Member or Members.
5. In the Value table, select a dimension. The dimensions that display are the dimensions that belong to the application
for which you are creating the variable.
6. Enter or use the Member Selector to select limits for the variable. You can select members only from the dimension
you select in step 3. You can also select functions.
7. Enter or use the Member Selector to select a value for the variable. You can select one member or function for a
member variable and multiple members and functions members variables.
Entering Variable Values for Percent Variables: Worked Example

The percent variable is an Essbase replacement or execution variable. This variable contains a percentage that you specify.
Entering Values for a Percent Variable

To enter values for a percent variable:
395
4. From Type, select Percent.

5. In the Value table, click in Limits to define minimum and maximum values for the variable.
6. Enter a numeric value for the variable.
7. Select whether missing data values can be allowed.
8. Select File,Save.
Displaying the Uses of a Variable: Worked Example

You can display the allocation rules and templates that use variables. When you show the uses of a variable, the following
information is displayed:
Names of the allocation rules and templates that are using the variable.
Application names of the allocation rules and templates that are using the variable.
Calculation types, plan types, or databases of the allocation rules and templates that are using the variable.
Owners of the allocation rules and templates that are using the variable.
Whether the allocation rules and templates that are using the variable are deployed.
Whether the allocation rules and templates that are using the variable are validated.
Description of the allocation rules and templates that are using the variable.
Displaying the Uses of a Variable

To display the use of a variable:
2. In the Variable Navigator, select the database object that contains the variable whose usages you want to view.
The variables defined for that object are displayed on the tabs in the Variable Designer.
3. Right-click the variable whose usages you want to view, and select Show Usages.
4. After you review the information, click OK.
Copying a Variable: Worked Example

You can copy a variable with the same name into the same or a different application using the copy and paste option. You
can also copy a variable with a different name into the same or a different application using the Save As option.
Copy a Variable with a Different Name using the Save As Option

To copy a variable with a different name using the Save As option:
1. In the System View, select Tools, Variables
2. In the Variable Navigator, do one of the following tasks:
Expand Essbase, and select the application, database, or rule associated with the variable you want to copy.
The variables associated with the object you select are displayed on the Replacement, or Execution tab, or
both.
3. Right-click the variable you want to copy, and select Save As.
4. Enter a new name for the variable, then select the application, and the calculation type, plan type, or database, or
accept the defaults.
By default, the variable is copied to the same application and calculation type, or database in which the variable is
created.
396
Refreshing Variables: Worked Example

You can refresh the list of variables in the Variable Navigator to see the updated list after you add, delete, or make changes to
variables.
Refreshing Variables
To refresh the list of variables in the Variable Navigator:
1. In the System View, select Tools,Variables
2. In the Variable Navigator, create, edit, or delete a variable.
3. On the Replacement or Execution tab, right-click, and select Refresh.
Editing a Variable: Overview

You can edit any property of a variable from the Variable Designer. When you update a variable that was previously
validated, any component that uses the variable is no longer validated. You must validate each component again.
Deleting a Variable: Worked Example

You can delete a variable or variables from the Variable Designer if they are not used in any components or member
formulas. If a variable is used in a component, you must remove the variable from the component before you delete it.
Deleting a Variable
To delete a variable:
2. In the Variable Navigator, expand the Essbase application type and the application.
3. Do one of the following tasks:
If the variable is a database variable, select the database with which the variable is associated.
If the variable is a rule variable, select the rule with which the variable is associated.
If the variable is an application variable, select the application with which the variable is associated.
Any variables associated with the application type, the application, the calculation type, or database, and the rule are
displayed on the Replacement or Execution tab.
4. On the Replacement or Execution tab, right-click the variable you want to delete, and click Delete.
5. In the Delete Confirmation dialog box, click Yes to confirm deletion of the variable.
Selecting a Variable: Worked Example

You can select a variable from various locations. You can select variables:
When you create components from within the Component Designer
When you create design time prompts from within the Template Designer
397
From other locations
Selecting a Variable
To select a variable:
1. In the System View, expand Essbase application type.

2. Expand the application, the calculation type, or the database (Essbase).
4. Right-click the template or rule that contains the component you want to add a variable to, and select Open.
5. When the rule or template opens, in its flow chart, select the component for which you want to insert a variable.
6. In the tabs, do one of the following tasks:
For member range, data range, and fixed loop components, in the Variable field, select the Variable icon.
For formula components, click the Actions icon, and select Variable.
For script components, click the Insert a Variable icon.
For condition components, start the Condition Builder, select Actions> Variable.
7. In Select Variable then, do one of these tasks:
Click Create to access the Variable Designer to create a new variable.

Select an existing variable from Category and select the object to associate with the variable. By default, the
variable is associated with the application for which you create it.
8. On Replacement or Execution, select one or more variables to insert into the component. Use Ctrl + Click or Shift +
Click to select multiple variables.
9. Click OK. The variables are inserted into the component.
Generating Allocations and Periodic Entries Manually:

Worked Example
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.
398
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.
Manage Revaluations
Revaluation Process: Explained

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 (FASB) Financial Accounting Statement No. 52 (FAS 52), Foreign
Currency Translation.
International Financial Reporting Standards (IFRS) International Accounting Standard No. 21 (IAS 21), The
Effects of Changes in Foreign Exchange Rates.
399
Support for multiple balancing segments to provide clarity in tracking the profitability and performance for more
distinct segments of your enterprise in any currency
Definition
When defining your revaluations, perform the following:
Include accounts for tracking gains and losses, currency conversion rates, and the number of entered currencies to
revalue.
Define separate revaluation definitions for each class of accounts, using a different rate type for each class.
Select various conversion types and methodologies for different account ranges, such as:
Current rates and year-to-date (YTD) method for balance sheet accounts.
Average rates and period-to-date (PTD) method for income statement accounts.
Note: Income statement accounts can also be revalued using YTD method.
Hierarchies and flexible account selection criteria, such as usage of parent values from your account hierarchy, streamlines
maintenance of revaluation definitions. The parent values can be selected for the primary balancing and the natural account
segments using the Is a last descendant of operator. Leveraging hierarchy versions extends your revaluation definitions
during organizational changes. Adjust account selection criteria monthly to retrieve the accounts that must be revalued for the
current accounting period.
Share revaluation definitions across ledgers that have the same chart of accounts to reduce maintenance.
Generation
Generating revaluations include:
Using defined revaluation criteria and automatically generating entries to shorten your close process.
Selecting automatic posting as part of the generate revaluation criteria to help you to achieve processing efficiency.
Scheduling revaluations to run during off peak hours to save your processing resources.
Using date effective account hierarchies to generate revaluations to keep results in line with your current organization
structures.
Always run revaluation to bring monetary balances to current rates before performing currency translation or remeasurement.
Note: When the revaluation process is scheduled to run automatically, the accounting period increments on
each subsequent run.
Revaluation Execution Report

The Revalue Balances process automatically generates the Revaluation Execution report when you run revaluation. This
report shows the details of your account balance revaluation and the journal batches created after running revaluation. The
report includes:
Currencies and revaluation rates used to revalue your accounts.
Unrealized gain or loss account in which you recorded net gains and losses.
Range of accounts revalued.
Names of your batch and journals that the revaluation process created for each foreign currency.
Total debits and credits of the created entries.
400
If the Revaluation process cannot locate rates for one or more currencies, balances are not revalued for those currencies.
In this case, the Revaluation process completes with a warning and the execution report lists which currencies are missing
rates.
Accounting for Unrealized Gain or Loss on Revaluation: Explained

Revaluation launches a process that revalues the ledger currency equivalent balances for the accounts and currencies you
select, using the appropriate current rate for each currency. Resulting unrealized gain or loss amounts are posted to the
unrealized gain or loss accounts or to the cumulative translation adjustment account. The revaluation journal is created,
balanced, and posted automatically by balancing segment values.
Revaluation journal entries are created to adjust the ledger currency balances for conversion rate fluctuations, in accordance
with:
Statement of Financial Accounting Standards (SFAS) No. 52, Foreign Currency Translation
International Accounting Standard (IAS) 21, The Effects of Changes in Foreign Exchange Rates
The revaluation journal entries generated and posted in the primary ledger are automatically generated, converted, and
posted to each of their reporting currencies. Define the cumulative translation adjustment account in the reporting currency
prior to running revaluation.
Entering Values for an Array Variable: Worked Example

An array variable can be an Essbase execution variable. Arrays contain a list of values that can be multidimensional.
Typically, arrays are used to store variables as part of a member formula. The size of the array variable is determined by the
number of members in the corresponding dimension. For example, if the Scenario dimension has four members, the following
command creates an array called Discount with four entries. You can use more than one array at a time.
Array Discount
To enter values for an array variable:

4. From Type, select Array.
5. In the Value field, enter a value for the variable.
Income Statement Accounts Revaluation Rule: Explained

Revaluation is the process which adjusts asset or liability accounts that may be materially understated or overstated. The
fluctuation in the conversion rate occurs between the time the transaction was entered and the time revaluation takes place.
401
You may want to revalue income statement accounts as well. The Income Statement Accounts Rule indicates whether
period-to-date (PTD) or year-to-date (YTD) method is to be used when revaluing income statement accounts.
Click the Income Statement radio buttons on the Create Revaluation page to revalue income statement accounts using
PTD or YTD balances.
If you select to revalue PTD balances for income statement accounts, the process continues to appropriately revalue
YTD balances for balance sheet accounts. If the range of accounts consists of both income statement and balance sheet
accounts and you select PTD as an option for income statement account revaluation rule, the revaluation:
Creates separate revaluation journal for the income statement accounts

Creates weighted average YTD balances using period rates from each corresponding period against the PTD
account balance.
Is in compliance with the Statement of Financial Accounting Standards (SFAS) No. 52, Foreign Currency Translation.
When you run revaluation on your income statement accounts, the process produces two separate journal entries; one
that revalues your balance sheet accounts and another for your income statement accounts. You do not reverse the PTD
revaluation journal for your income statement accounts in the subsequent period. The revaluation only applies to last period's
activity.
Note: This functionality only applies when the range of accounts in the revaluation definition consist of income
statement and balance sheet accounts. Normally only balance sheets accounts are revalued.
Revaluing Across Multiple Balancing Segments: Worked Example

This example demonstrates how to revalue foreign currency balances across multiple balancing segments. Your company,
InFusion America, Inc. has three lines of business. You revalue foreign currency account balances for two divisions, Air
Components and Repair Parts. The Installation Services line of business doesn't have foreign currency transactions. Your
company is the primary balancing segment and your lines of business are represented in the secondary balancing segment.
Note: Enable up to three balancing segments to use the multiple balancing segment feature.
The following are points to consider in running the revaluation process.
The revaluation process posts the resulting gain or loss amounts against the unrealized gain or loss accounts,
substituting the balancing segment values appropriately for all balancing segments.
Gain or loss accounts and revaluation account ranges aren't validated against your data access set security when
the revaluation definition is created because the ledger context isn't known at the time of definition.
Data access set security is enforced when the Revalue Balances process is run. Limited write access to the gain or
loss accounts due to inadequate access results in an error.
Segment value security rules are enforced when you enter account ranges and the unrealized gain and loss
accounts. Only segment values that you have access to are available in the list of values.
Account ranges that you have read and write access to are revalued. Account combinations that you don't have
access to are ignored.
The revaluation process expands the parent primary balancing segment to the child values. Data access set security
applies to the child values only, not the parent value.
The posting process supports multiple balancing segments for calculating the entry to the Cumulative Translation
Adjustment accounts when replicating revaluation journals to reporting currencies.
402
Defining Revaluations
1. Navigator > Setup and Maintenance > Manage Revaluations.
2. On the Manage Revaluations page, click the Create icon.
Field Value
Name InFusion America Revaluation

Description Revaluation for all foreign currency balances.

Chart of Accounts InFusion America Chart of Accounts

Currency Leave blank.

Note:If blank, all currencies are revalued and after saving, the field automatically displays:
All currencies.

Conversion Rate Type Daily

Days to Roll Forward 5

Unrealized Gain Account 011-00-96600000-0000-000-000

Unrealized Loss Account 011-00-96700000-0000-000-000

Income Statement Account Basis PTD

Post Automatically Yes

4. In the Revaluation Accounts section, click the Add Row icon.

5. Click the Change filter conditions icon to enter the filter used to select the accounts to revalue.
6. Click Add Fields and select Company.
7. Accept the default operator of Equals and select 11 from the list of Company segment values.
8. Click Add Fields and select Lines of Business.
9. Change the operator to Between and select 30 for Air Components and 40 for Repair Parts.
10. Click Add Fields and select Account from the list.
11. Change the operator to Between and enter values 10000000 and 29999999.
12. Click OK to accept the filters.
Optionally, click Save and then click Generate to save and run the revaluation immediately.
403
404
Implementing Enterprise Structures and General Ledger Business Units
11 Business Units
Business Units: Explained

A business unit is a unit of an enterprise that performs one or many business functions that can be rolled up in a management
hierarchy. A business unit can process transactions on behalf of many legal entities. Normally, it has a manager, strategic
objectives, a level of autonomy, and responsibility for its profit and loss. Roll business units up into divisions if you structure
your chart of accounts with this type of hierarchy.
In Oracle Fusion Applications you do the following:
Assign your business units to one primary ledger. For example, if a business unit is processing payables invoices,
then it must post to a particular ledger. This assignment is required for your business units with business functions
that produce financial transactions.
Use a business unit as a securing mechanism for transactions. For example, if you run your export business
separately from your domestic sales business, then secure the export business data to prevent access by the
domestic sales employees. To accomplish this security, set up the export business and domestic sales business as
two separate business units.
The Oracle Fusion Applications business unit model provides the following advantages:
Enables flexible implementation
Provides consistent entity that controls and reports on transactions
Shares sets of reference data across applications
Business units process transactions using reference data sets that reflect your business rules and policies and can differ from
country to country. With Oracle Fusion Application functionality, you can share reference data, such as payment terms and
transaction types, across business units, or you can have each business unit manage its own set depending on the level at
which you want to enforce common policies.
In countries where gapless and chronological sequencing of documents is required for subledger transactions, define your
business units in alignment with your legal entities to ensure the uniqueness of sequencing.
In summary, use business units for:

Management reporting
Transaction processing
Transactional data security
Reference data sharing and definition
Brief Overview of Business Unit Security

A number of Oracle Fusion Applications use business units to implement data security. You assign roles like Accounts
Payable Manager to users to permit them to perform specific functions, and you assign business units for each role to
users to give them access to data in those business units. For example, users which have been assigned a Payables role
for a particular business unit, can perform the function of payables invoicing on the data in that business unit. Roles can
be assigned to users manually using the Security Console, or automatically using provisioning rules. Business Units can be
assigned to users using the Manage Data Access for Users task in Setup and Maintenance.
405
Related Topics
Business Functions: Explained

A business unit can perform many business functions in Oracle Fusion Applications.
Business Functions
A business function represents a business process, or an activity that can be performed by people working within a business
unit and describes how a business unit is used. The following business functions exist in Oracle Fusion applications:
Billing and revenue management
Collections management
Customer contract management
Customer payments
Expense management
Incentive compensation
Marketing
Materials management
Inventory management
Order fulfillment orchestration
Payables invoicing
Payables payments
Procurement
Procurement contract management
Project accounting
Receiving
Requisitioning
Sales
Although there is no relationship implemented in Oracle Fusion Applications, a business function logically indicates a presence
of a department in the business unit with people performing tasks associated with these business functions. A business
unit can have many departments performing various business functions. Optionally, you can define a hierarchy of divisions,
business units, and departments as a tree over HCM organization units to represent your enterprise structure.
Note: This hierarchy definition is not required in the setup of your applications, but is a recommended best
practice.
Your enterprise procedures can require a manager of a business unit to have responsibility for their profit and loss statement.
In such cases, any segment that allows the identification of associated revenue and costs can be used as a profit center
identification. The segment can be qualified as a cost center segment.
406
However, there are cases where a business unit is performing only general and administrative functions, in which case your
manager's financial goals are limited to cost containment or recovering of service costs. For example, if a shared service
center at the corporate office provides services for more commercially-oriented business units, it does not show a profit and
therefore, only tracks its costs.
In other cases, where your managers have a responsibility for the assets of the business unit, a balance sheet can be
produced. The recommended best practice to produce a balance sheet is to setup the business unit as a balancing segment
in the chart of accounts. The business unit balancing segment can roll up to divisions or other entities to represent your
enterprise structure.
When a business function produces financial transactions, a business unit must be assigned to a primary ledger, and a
default legal entity. Each business unit can post transactions to a single primary ledger, but it can process transactions for
many legal entities.
The following business functions generate financial transactions and will require a primary ledger and a default legal entity:
Billing and revenue management

Collections management
Customer payments
Expense management
Materials management
Payables invoicing
Project accounting
Receiving
Requisitioning
Business Unit Hierarchy: Example

For example, your InFusion America Company provides:
Air quality monitoring systems through your division InFusion Air Systems
Customer financing through your division InFusion Financial Services
The InFusion Air Systems division further segments your business into the System Components and Installation Services
subdivisions. Your subdivisions are divided by business units:
System Components by products: Air Compressors and Air Transmission

Installation Services by services: Electrical and Mechanical
407
The following figure shows an example of a business unit hierarchy.
InFusion Air Systems InFusion Financial

Division Services Division
System Components Installation Services

Subdivision Subdivision
Air Air Electrical Mechanical

Compressors Transmission Services Services
Business Unit Business Unit Business Unit Business Unit
Oracle Fusion applications facilitates independent balance sheet rollups for legal and management reporting by offering
up to three balancing segments. Hierarchies created using the management segment can provide the divisional results.
For example, it is possible to define management segment values to correspond to business units, and arrange them in a
hierarchy where the higher nodes correspond to divisions and subdivisions, as in the Infusion US Division example above.
Creating Business Units in the Enterprise Structures

Configurator: Points to Consider
Business units are used within Oracle Fusion applications for management reporting, processing of transactions, and security
of transactional data. Using the Enterprise Structures Configurator (ESC), you create business units for your enterprise either
automatically or manually.
Automatically Creating Business Units

To create business units automatically, you must specify the level at which to create business units. Business units within your
enterprise may be represented at one of two levels:
Business function level, such as Sales, Consulting, Product Development, and so on.
408
A more detailed level, where a business unit exists for each combination of countries in which you operate and the
functions in those countries.
You can automatically create business units at the following levels:
Country
Country and Division
Country and business function
Division
Division and legal entity
Division and business function
Business function
Legal entity
Business function and legal entity
Select the option that best meets your business requirements, but consider the following:
If you use Oracle Fusion Financials, the legal entity option is recommended because of the manner in which financial
transactions are processed.
The business unit level that you select determines how the application automatically creates reference data sets.
After you select a business unit level, the application generates a list of business units, and you select the ones you want
the application to create. If you select a level that has two components, such as country and division, then the application
displays a table listing both components. You select the check boxes at the intersections of the two components.
The business units listed by the application are suggestions only, and are meant to simplify the process to create business
units. You aren't required to select all of the business units suggested. When you navigate to the next page in the ESC guided
flow, the Manage Business Units page, you can't delete any of the business units created automatically. You must return to
the Create Business Units page and deselect any business units that you no longer want.
Example: Selecting Business Unit Levels

InFusion Corporation is using the Enterprise Structures Configurator to set up its enterprise structure. InFusion has identified
two divisions, one for Lighting, and one for Security. They operate in four countries: US, UK, Japan, and India, and they have
created a legal entity for each of the countries. The sales and marketing functions are based in both India and Japan, while
the US and the UK have only the sales function.
409
This figure illustrates InFusion Corporation's enterprise structure.
Enterprise
Division Division
Legal Entity Legal Entity Legal Entity Legal Entity

Japan US UK India
Sales Marketing Sales Sales Sales Marketing
The following table lists the options for business unit levels and the resulting business units that the application suggests for
InFusion Corporation.
Business Unit Level Suggested Business Units
Country US
UK
Japan
India
Country and Division InFusion Lighting: Japan

InFusion Lighting: US
Infusion Security: UK
Infusion Security: India
Country and business function Sales: Japan

Marketing: Japan
Sales: US
Sales: UK
Marketing: India
Sales: India
Division InFusion Lighting

InFusion Security
Division and Legal Entity InFusion Lighting: Japan

InFusion Lighting: US
Infusion Security: UK
410
Business Unit Level Suggested Business Units

Infusion Security: India
Division and Business Function InFusion Lighting, Sales

InFusion Lighting, Marketing
InFusion Security, Sales
InFusion Security, Marketing
Business Function Sales

Marketing
Legal Entity Legal Entity: Japan

Legal Entity: US
Legal Entity: UK
Legal Entity India
Legal Entity and Business Function Legal Entity: Japan, Sales

Legal Entity: Japan, Marketing
Legal Entity: US, Sales
Legal Entity: UK, Sales
Legal Entity India, Marketing
Legal Entity India, Sales
Manually Creating Business Units

If none of the levels for creating business units meets your business needs, you can create business units manually, and
you create them on the Manage Business Units page. If you create business units manually, then no reference data sets are
created automatically. You must create them manually as well.
Related Topics
What reference data objects can be shared across asset books?
Copying Business Unit Configurations: Procedure

Use the Copy Configuration feature to create new business units by copying existing business units. For example, if you have
business units that share similar configurations, you can create copies of the first business unit and make adjustments for the
setup differences.
411
The following figure illustrates the steps in the copy configuration process.
Create Copy
Edit Staged Import Staged
Configuration
Configuration Configuration
Request
Fix Errors Review Copied

(If applicable) Configuration
Creating a Copy Configuration Request

Create a copy request by identifying the business unit you want to copy, and assigning a name to the request. You can
review the business objects that will be copied to the new business unit.
1. Navigate to the Create Copy Configuration Request page.
2. In the Copy Configuration field, select Copy Business Unit Configuration for Financials.
3. Select the business unit to copy.
4. Enter the name for the copy request.
5. Click Submit.
Editing a Staged Configuration

Edit the business unit copy by selecting specific account segment values to override, or accepting the source values.
1. Click the Ready to edit link for your request name.
2. In the Override Business Unit Account Segment Values page, enter a name for the new business unit.
3. Enter an organization code.
4. For each account segment value, specify whether to use the same values as the original business unit, or select a
new value.
Importing a Staged Configuration

Start the process to import a staged configuration, or return to the Override Business Unit Account Segment Values page to
make changes.
1. Click the Ready to import link for your request name.
2. In the Review and Import Staged Configuration page, take one of the following actions:
Click Import to import the staged configuration.
Click Edit to return to the Override Business Unit Account Segment Values page to make changes.
412
Fixing Errors
If you encounter any errors during the staging configuration process, click the Ready to fix errors link to review the new
business unit configuration data. Click the Download icon to view the process status details of each copied business object.
Reviewing the Copied Configuration

Use the task list to review the business objects for your new business unit and make changes as needed.
1. Click the Ready to review link for your request name.

2. In the Copy Business Unit Configuration for Financials page, use the task list to navigate to each task. Review the
newly copied data and make adjustments for your new business unit.
Override Business Unit Account Segment Values: Examples

Use override business unit account segment values to specify the account segment values for a new business unit created by
the copy business unit configuration process. Determine the source and target values for your business units and use these
two values for the same chart of accounts or for the same primary ledger.
The following scenarios illustrate the impact of using this option to:
Use the same values as the original business unit.

Select new values that are different from the original business unit.
The following table lists selected account values of the original business unit for both scenarios:
Account Name Account Values
Tax Account 01-000-2520-0000-000

Cross Currency Rounding Account 01-740-7826-0000-000

Realized Gains Account 01-740-7830-0000-000

Realized Losses Account 01-740-7840-0000-000

Header Rounding Account 01-740-7827-0000-000

Using Identical Account Segment Values

In this scenario, you are creating the new business unit with account segment values that are identical to the original business
unit. The following table illustrates the settings on the Override Business Unit Account Segment Values page.
413
Business Unit Organization Code Primary Ledger Default Legal Entity
Vision Operations FR Vision Operations FR Vision Operations USA Vision Operations

Procure-to-Pay Default Account Order-to-Cash Default Account Segment Values

Segment Values
Company: Use source Company: Use source

Department: Use source Department: Use source

Sub-Account: Use source Sub-Account: Use source

Product: Use source Product: Use source

The following table lists the resulting account segment values:
Tax Account 01-000-2520-0000-000





Overriding Account Segment Values

In this scenario, you are creating a new business unit named Vision Operations JP for a different company, and the company
segment value should represent the company value of 05. The following table illustrates the settings on the Override Business
Unit Account Segment Values page.
Business Unit Organization Code Primary Ledger Default Legal Entity
Vision Operations JP Vision Operations JP Vision Operations USA Vision Operations


Segment Values
Company: 05 Company: 05
414

Segment Values

Department: Use source Department: Use source

Sub-Account: Use source Sub-Account: Use source

Product: Use source Product: Use source

The following table lists the resulting account segment values:
Tax Account 05-000-2520-0000-000





FAQs for Business Units
What's the difference between business units in Oracle E-Business

Suite and Oracle Fusion Applications?
In Oracle E-Business Suite, operating units are used to determine in which ledger a given subledger transaction is accounted
and to partition set up reference data, processing and security.
In Oracle Fusion Applications, enable business units with all their business functions to replace your operating units in the
Oracle E-Business Suite. Oracle Fusion Applications provide the additional functionality of assigning a manager to the
business unit.
What's the difference between business units in Oracle PeopleSoft

and Oracle Fusion Applications?
Oracle PeopleSoft business units and Oracle E-Business Suite operating units have been combined to create the new Oracle
Fusion Applications business unit functionality.
415
In Oracle PeopleSoft Enterprise, a business unit housed the configuration of only one business function.
A business unit can be configured for multiple business functions in Oracle Fusion Applications. The advantage is you no
longer have to name multiple business units with the same name as you did in PeopleSoft Enterprise.
In PeopleSoft Enterprise, business units can be consolidated in a hierarchy. You can see the results of a single business unit
or a set of business units. PeopleSoft Enterprise also enables you to produce financial statements for a business unit.
In Oracle Fusion Applications, this is accomplished by creating a business unit representation in a chart of accounts and
building appropriate hierarchies.
Manage Service Provider Relationships
Service Provider Model: Explained

In Oracle Fusion applications, the service provider model defines relationships between business units for a specific business
function, identifying one business in the relationship as a service provider of the business function, and the other business unit
as its client.
Procurement Example
The Oracle Fusion Procurement product family has taken advantage of the service provide model by defining outsourcing of
the procurement business function. Define your business units with requisitioning and payables invoicing business functions
as clients of your business unit with the procurement business function. Your business unit responsible for the procurement
business function takes care of supplier negotiations, supplier site maintenance, and purchase order processing on behalf of
your client business units. Subscribe your client business units to the supplier sites maintained by the service providers, using
a new procurement feature for supplier site assignment.
416
In the InFusion example below, business unit four (BU4) serves as a service provider to the other three business units (BU1,
BU2, and BU3.) BU4 provides the corporate administration, procurement, and human resources (HR) business functions,
thus providing cost savings and other benefits to the entire InFusion enterprise.
InFusion United States InFusion United Kingdom

(US) Division (UK) Division
InFusion Financial
Services Inc. InFusion UK Systems Ltd.
Primary Ledger Primary Ledger (GBP) with
Primary Ledger (USD)
(USD) Reporting Currency (USD)
Standard, Jan - Dec
Average Balancing Standard, Jan - Dec
May-April
BU 1 BU 2 BU 3
US Systems Fin Services UK Systems
BU 4
Corporate Administration, Procurement, and HR Shared Services Center
Shared Service Centers: Explained

Oracle Fusion Applications enables defining relationships between business units to outline which business unit provides
services to the other business units.
Service Provider Model

The service provider model centralizes the following business functions:
Procurement
Services business units that enable the Requisitioning business function.
Processes requisitions and negotiates supplier terms for client business units.
Payables Payment
Services business units that enable the Payables Invoicing business function.
Processes payments for client business units.
Customer Payments
Services business units that enable the Billing and Revenue Management business function.
417
Processes payments for the transactions of client business units assigned the Billing and Revenue
Management business function.
This functionality is used to frame service level agreements and drive security. The service provider relationships provides you
with a clear record of how your business operations are centralized. For other centralized processing, business unit security
is used (known in Oracle EBS as Multi-Org Access Control). This means that users who work in a shared service center have
the ability to get access and process transactions for many business units.
Related Topics
Centralized Payment Processing Across Business Units: Explained
Shared Service Center: Points to Consider

Oracle Fusion applications supports shared service centers in two ways. First, with business unit security, which allows your
shared service centers personnel to process transactions for other business units called clients.
Second, the service provider model expands on this capability to allow a business unit and its personnel in a shared service
center to work on transactions of the client business units. It is possible to view the clients of a service provider business unit,
and to view service providers of a client business unit.
Your shared service centers provide services to your client business units that can be part of other legal entities. In such
cases, your cross charges and recoveries are in the form of receivables invoices, and not merely allocations within your
general ledger, thereby providing internal controls and preventing inappropriate processing.
For example, in traditional local operations, an invoice of one business unit cannot be paid by a payment from another
business unit. In contrast, in your shared service center environment, processes allowing one business unit to perform
services for others, such as paying an invoice, are allowed and completed with the appropriate intercompany accounting.
Shared service centers provide your users with access to the data of different business units and can comply with different
local requirements.
Security
The setup of business units provides you with a powerful security construct by creating relationships between the functions
your users can perform and the data they can process. This security model is appropriate in a business environment where
local business units are solely responsible for managing all aspects of the finance and administration functions.
In Oracle Fusion applications, the business functions your business unit performs are evident in the user interface for setting
up business units. To accommodate shared services, use business unit security to expand the relationship between functions
and data. A user can have access to many business units. This is the core of your shared service architecture.
For example, you take orders in many businesses. Your orders are segregated by business unit. However, all of these orders
are managed from a shared service order desk in an outsourcing environment by your users who have access to multiple
business units.
Benefits
In summary, large, medium, and small enterprises benefit from implementing share service centers. Examples of functional
areas where shared service centers are generally implemented include procurement, disbursement, collections, order
management, and human resources. The advantages of deploying these shared service centers are the following:
Reduce and consolidate the number of control points and variations in processes, mitigating the risk of error.
Increase corporate compliance to local and international requirements, providing more efficient reporting.
418
Implement standard business practices, ensuring consistency across the entire enterprise and conformity to
corporate objectives.
Establish global processes and accessibility to data, improving managerial reporting and analysis.
Provide quick and efficient incorporation of new business units, decreasing start up costs.
Establish the right balance of centralized and decentralized functions, improving decision making.
Automate self-service processes, reducing administrative costs.
Permit business units to concentrate on their core competencies, improving overall corporate profits.
Business Function Properties
Customer Contracts Business Unit Setup: Explained

Using the Specify Customer Contract Management Business Function Properties task, available by navigating to
Setup and Maintenance work area and searching on the task name, you can specify a wide variety of business function
settings for customer contracts in a specific business unit. The selections you make for these business functions impact how
Oracle Enterprise Contracts behaves during contract authoring.
Using the Specify Customer Contract Management Business Function Properties task, manage these business
function properties:
Enable related accounts
Set currency conversion details
Note: You must select a default currency in the customer or supplier business function properties page, if
not populated automatically from the ledger assigned to the business unit in the assign business function
setup task.
Manage project billing options

Set up clause numbering
Set up the Contract Terms Library
The setup options available for the Contract Terms Library are applicable to both customer and supplier contracts,
and are described in the business unit setup topic for the Contract Terms Library. That topic is available as a related
link to this topic.
Enabling Related Customer Accounts

Contract authors can specify bill-to, ship-to, and other accounts for the parties in a contract. Enable the related customer
accounts option if you want accounts previously specified as related to the contract party to be available for selection.
Managing Currency Conversion Options

If your organization plans to transact project-related business in multiple currencies, then select the multicurrency option. This
allows a contract author to override a contract's currency, which is derived from the ledger currency of the business unit. It
also enables the contract author to specify currency conversion attributes to use when converting from the bill transaction
currency to the contract currency and from the invoice currency to the ledger currency.
419
In the Bill Transaction Currency to Contract Currency region, enter currency conversion details that will normally be used,
by all contracts owned by this business unit, to convert transaction amounts in the bill transaction currency to the contract
currency. Newly created contracts contain the default currency conversion values, but you can override the values on any
contract, if needed.
In the Invoice Currency to Ledger Currency region:

Enter invoice transaction conversion details if the invoice and ledger currencies can be different.
Enter revenue transaction conversion details if the revenue and ledger currencies can be different for as-incurred and
rate-based revenue.
Managing Project Billing Options

The options available for selection in the Project Billing region control the behavior of project invoicing and revenue
recognition for contracts with project-based work. Project billing can act differently for external contracts (customer billing) or
intercompany and interproject contracts (internal billing).
Set these options, which apply to all contracts:

Select the Transfer Revenue to General Ledger option if you want to create revenue accounting events and
entries, and transfer revenue journals to the general ledger. If this option is not selected, then revenue can still be
generated, but will not be transferred to the general ledger.
Indicate if a reason is required for credit memos that are applied to invoices.
There are two sets of the following options, one for customer billing and a second for internal billing:
Select an invoice numbering method, either Manual or Automatic. The invoice numbering method is the method
that Oracle Fusion Receivables uses to number its invoices, upon release of draft invoices from Project Billing.
If the invoice numbering method is Manual, then select an invoice number type, which sets the type of
Receivables invoice numbers that are allowed. Valid values are Alphanumeric and Numeric.
If the invoice numbering method is Automatic, then enter the next invoice number to use when generating
Receivables invoice numbers.
Select the Receivables batch source to use when transferring invoices to Receivables.
Set this option only for customer billing:

Indicate if you want contract authors to manually enter the Receivables transaction type on the customer contracts
they create.
Managing Clause Numbering

You can choose to number clauses manually or automatically.
If you choose the automatic numbering method, you must select a determinant level for the numbering. You must then select
the appropriate clause sequence category from document sequences that you set up for this numbering level.
Contract Terms Library Business Unit Setup: Explained

You can specify a wide variety of Contract Terms Library settings for either customer or supplier contracts within each
business unit, by using either the Specify Customer Contract Management Business Function Properties or the
Specify Supplier Contract Management Business Function Properties tasks. These tasks are available by navigating to
the Setup and Maintenance work area and searching on the task name.
420
For the Contract Terms Library in each business unit, you can:
Enable clause and template adoption.
Set the clause numbering method.
Set the clause numbering level for automatic clause numbering of contracts.
For a contract with no assigned ledger or legal entity, set the document sequence to Global or Business Unit level.
Enable the Contract Expert enabling feature.
Specify the layout for printed clauses and contract deviation reports.
Enabling Clause Adoption

If you plan to use clause adoption in your implementation, then set up the following:
1. Specify a global business unit
You must designate one of the business units in your organization as the global business unit by selecting the
Global Business Unit option. This makes it possible for the other local business units to adopt and use approved
content from that global business unit. If the Global Business Unit option is not available for the business unit you
are setting up, this means that you already designated another business unit as global.
2. Enable automatic adoption
If you are implementing the adoption feature, then you can have all the global clauses in the global business unit
automatically approved and available for use in the local business by selecting the Autoadopt Global Clauses
option. If you do not select this option, the employee designated as the Contract Terms Library Administrator must
approve all global clauses before they can be adopted and used in the local business unit. This option is available
only for local business units.
3. Specify the administrator who approves clauses available for adoption
You must designate an employee as the Contract Terms Library administrator if you are using adoption. If you do not
enable automatic adoption, then the administrator must adopt individual clauses or localize them for use in the local
business unit. The administrator can also copy over any contract terms templates created in the global business unit.
The clauses and contract terms templates available for adoption are listed in the administrator's Terms Library work
area.
Setting Clause Numbering Options

You can set up automatic clause numbering for the clauses in the business unit by selecting Automatic in the Clause
Numbering field and setting the clause numbering level. Then select the appropriate clause sequence category for the
specified numbering level. You must have previously set up document sequences for the document sequence categories
of global, ledger, and business unit. If clause numbering is manual, contract terms library administrators must enter unique
clause numbers each time they create a clause.
You can choose to display the clause number in front of the clause title in contracts by selecting the Display Clause
Number in Clause Title option.
Enabling Contract Expert

You must select the Enable Contract Expert option to be able to use the Contract Expert feature in a business unit. This
setting takes precedence over enabling Contract Expert for individual contract terms templates.
Specifying the Printed Clause and Deviations Report Layouts

For each business unit, you can specify the Oracle BI Publisher RTF file that serves as the layout for:
The printed contract terms
421
Enter the RTF file you want used for formatting the printed clauses in the Clause Layout Template field.
The contract deviations report
The RTF file you select as the Deviations Layout Template determines the appearance of the contract deviations
report PDF. This PDF is attached to the approval notification sent to contract approvers.
Related Topics
How the Selection of a Business Unit Affects Clauses and Other Objects in the Library
Contract Expert: How It Works
Contract Printing and Layout Templates: Explained
Supplier Contracts Business Unit Setup: Explained

You can specify a variety of business function settings for supplier contracts in a specific business unit using the Specify
Supplier Contract Management Business Function Properties task, available by selecting Setup and Maintenance from
the Navigator and searching on the task name.
The selections you make for these business functions impact how the Contract Terms Library behaves during supplier
contract authoring.
Note: The customer must select a default currency in the customer or supplier business function properties
page, if not automatically populated from the ledger assigned to the business unit in the assign business function
setup task.
Managing Contract Terms Library Setup Options

The setup options available for the Contract Terms Library are applicable to both customer and supplier contracts, and are
described in the business unit setup topic for the Contract Terms Library. That topic is available as a related link to this topic.
422
Implementing Enterprise Structures and General Ledger Workforce Structures and Facilities
12 Workforce Structures and Facilities

Managing Enterprise Information for Non-HCM Users:
Explained
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 are 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 are not relevant outside of Oracle Fusion HCM.
Manage Divisions
Divisions: Explained
Managing multiple businesses requires that you segregate them by their strategic objectives and measure their results.
Responsibility to reach objectives can be delegated along the management structure. Although related to your legal structure,
the business organizational hierarchies do not reflect directly the legal structure of the enterprise. The management entities
and structure can include:
Divisions and subdivisions
Lines of business
Other strategic business units
Their own revenue and cost centers
These organizations can be included in many alternative hierarchies and used for reporting, as long as they have
representation in the chart of accounts.
Divisions
A division refers to a business-oriented subdivision within an enterprise, in which each division organizes itself differently to
deliver products and services or address different markets. A division can operate in one or more countries, and can be many
companies or parts of different companies that are represented by business units.
A division is a profit center or grouping of profit and cost centers, where the division manager is responsible for achieving
business goals including profits. A division can be responsible for a share of the company's existing product lines or for a
separate business. Managers of divisions may also have return on investment goals requiring tracking of the assets and
liabilities of the division. The division manager generally reports to a top corporate executive.
By definition a division can be represented in the chart of accounts. Companies can use product lines, brands, or
geographies as their divisions: their choice represents the primary organizing principle of the enterprise. This may coincide
with the management segment used in segment reporting.
Oracle Fusion Applications supports a qualified management segment and recommends that you use this segment to
represent your hierarchy of business units and divisions. If managers of divisions have return on investment goals, make the
423
management segment a balancing segment. Oracle Fusion applications permit up to three balancing segments. The values of
the management segment can be business units that roll up in a hierarchy to report by division.
Historically, divisions were implemented as a node in a hierarchy of segment values. For example, Oracle E-Business Suite
has only one balancing segment, and often the division and legal entity are combined into a single segment where each value
stands for both division and legal entity.
Use of Divisions in Oracle Fusion Human Capital Management (HCM)

Divisions are used in HCM to define the management organization hierarchy, using the generic organization hierarchy. This
hierarchy can be used to create organization-based security profiles.
Adding a New Division After Acquiring a Company: Example

This example describes how you can restructure your enterprise after acquiring a new division.
Scenario
You are part of a senior management team at InFusion Corporation. InFusion is a global company with organizations in the
following countries:
United States (US)
United Kingdom (UK)
France
China
Saudi Arabia
United Arab Emirates (UAE)
The company's main area of business is in the high tech industry, and it recently acquired a new company. You must analyze
the company's current enterprise structure and determine the new organizations to create in the new company.
Details of the Acquired Company

The acquired company is a Financial Services business based in Germany. The Financial Services business differs significantly
from the high tech business. Therefore, you want to keep the Financial Services company as a separate business with all the
costs and reporting managed by the Financial Services division.
Analysis
The following table summarizes the key decisions that you must consider when determining what new organizations to set up
and how to structure the enterprise.
Decision to Consider In This Example
Create location? The Financial Services company and its departments are based in Frankfurt. Therefore, you only
have to create one location.

Create separate division? Yes. Although the new division will exist in the current enterprise structure, you want to keep the
Financial Services company as a separate line of business. By creating a separate division, you can
manage the costs and reporting separately from the InFusion Corporation. Additionally you don't
have to modify any organizations in the enterprise setup.

424
Decision to Consider In This Example
Create business unit? Yes. The Financial Services business requires you to create several jobs that don't exist in your high
tech business. You can segregate the jobs that are specific to financial services in a new business
unit.

How many departments? The Financial Services company currently has departments for sales, accounting, and marketing. As
you have no plans to downsize or change the company, you can create three departments to retain
the structure.

How many cost centers? Although you can have multiple cost centers to track the department costs, you decide to create
one cost center for each department.

How many legal entities?

Define a legal entity for each registered company or some other entity recognized by law. Using the
legal entity, you can:
Record assets
Record liabilities
Record income
Pay transaction taxes
Perform intercompany trading
In this case, you only need one legal entity.
You must define the legal entity as a legal employer and payroll statutory unit. As the new division
operates only from Germany, you can configure the legal entity to suit Germany's legal and statutory
requirements.
Note: You can identify the legal entity as a payroll statutory unit. When you do so, the
application transfers the legal reporting unit associated with the legal entity to Oracle
Fusion HCM as a tax reporting unit.

Create legislative data group? Yes. Because you currently don't employ or pay people in Germany, you must create one legislative
data group to run payroll for the workers in Germany.

Resulting InFusion Enterprise Structure

Based on the analysis, you must create the following:
One new division

One new location
Three new departments
Three new cost centers
One new legal entity
One new legislative data group
425
The following figure illustrates the structure of InFusion Corporation after adding the new division and the other organizations.
InFusion
Corporation
US Europe Asia Others Germany Financial

Division Division Division Division Services Division
DE Financial Legal Legal Employer

Services Entity and Payroll
Statutory Unit
Tax
Business Unit Reporting
Unit
Legislative
Data
Group
Cost Cost Cost

Centre Centre Centre
Frankfurt Frankfurt Frankfurt
Sales Marketing Accounting
Department Department Department
Manage Departments
Cost Centers and Departments: Explained

The two important components to be considered in designing your enterprise structure are cost centers and departments.
A cost center represents the smallest segment of an organization for which you collect and report costs. A department is an
organization with one or more operational objectives or responsibilities that exist independently of its manager and has one or
more workers assigned to it.
426
Cost Centers
A cost center represents the destination or function of an expense rather than the nature of the expense which is represented
by the natural account. For example, a sales cost center indicates that the expense goes to the sales department.
A cost center is generally attached to a single legal entity. To identify the cost centers within a chart of accounts structure use
one of these two methods:
Assign a cost center value in the value set for each cost center. For example, assign cost center values of PL04 and
G3J1 to your manufacturing teams in the US and India. These unique cost center values allow easy aggregation of
cost centers in hierarchies (trees) even if the cost centers are in different ledgers. However, this approach requires
defining more cost center values.
Assign a balancing segment value with a standardized cost center value to create a combination of segment values
to represent the cost center. For example, assign the balancing segment values of 001 and 013 with cost center
PL04 to represent your manufacturing teams in the US and India. This creates 001-PL04 and 013-PL04 as the cost
center reporting values. The cost center value of PL04 has a consistent meaning. This method requires fewer cost
center values to be defined. However, it prevents construction of cost center hierarchies using trees where only
cost center values are used to report results for a single legal entity. You must specify a balancing segment value in
combination with the cost center values to report on a single legal entity.
Departments
A department is an organization with one or more operational objectives or responsibilities that exist independently of its
manager. For example, although the manager may change, the objectives do not change. Departments have one or more
workers assigned to them.
A manager of a department is typically responsible for:
Controlling costs within their budget
Tracking assets used by their department
Managing employees, their assignments, and compensation
The manager of a sales department may also be responsible for meeting the revenue targets.
The financial performance of departments is generally tracked through one or more cost centers. In Oracle Fusion
Applications, departments are defined and classified as Department organizations. Oracle Fusion Human Capital
Management (HCM) assigns workers to departments, and tracks the headcount at the departmental level.
The granularity of cost centers and their relationship to departments varies across implementations. Cost center and
department configuration may be unrelated, identical, or consist of many cost centers tracking the costs of one department.
Department Classifications: Points to Consider

A department can be classified as a project organization, sales and marketing organization, or cost organization.
Oracle Fusion Human Capital Management (HCM) uses trees to model organization hierarchies. It provides predefined tree
structures for department and other organizational hierarchies that can include organizations with any classification.
Project Organization
Classify departments as a project owning organization to enable associating them with projects or tasks. The project
association is one of the key drivers for project access security.
In addition, you must classify departments as project expenditure organizations to enable associating them to project
expenditure items. Both project owning organizations and project expenditure organizations can be used by Oracle Fusion
427
Subledger Accounting to derive accounts for posting Oracle Fusion Projects accounting entries to Oracle Fusion General
Ledger.
Sales and Marketing Organization

In Oracle Sales Cloud, you can define sales and marketing organizations. Sales organization hierarchies are used to report
and forecast sales results. Salespeople are defined as resources assigned to these organizations.
In some enterprises, the HCM departments and hierarchies correspond to sales organizations and hierarchies. Examining
the decision on how to model sales hierarchies in relationship to department hierarchies when implementing Customer
Relationship Management to eliminate any possible redundancy in the definition of the organizations is important.
The following figure illustrates a management hierarchy, in which the System Components Division tracks its expenses in
two cost centers, Air Compressors and Air Transmission. At the department level, two organizations with a classification of
Department are defined, the Marketing Department and Sales Department. These two departments can be also identified as
a Resource Organizations, which enable assigning resources, such as salespeople, and other Oracle Sales Cloud specific
information to them. Each department is represented in the chart of accounts by more than one cost center, enabling
granular as well as hierarchical reporting.
System Components Division
Air Air
Compressors Transmission
Business Unit Business Unit
Sales Marketing
Department Department
US East US West
Cost Center Cost Center
Cost Organization
Oracle Fusion Costing uses a cost organization to represent a single physical inventory facility or group of inventory storage
centers, for example, inventory organizations. This cost organization can roll up to a manager with responsibility for the cost
center in the financial reports.
A cost organization can represent a costing department. Consider this relationship when determining the setup of
departments in HCM. No system dependencies are required for these two entities, cost organization and costing department,
to be set up in the same way.
428
Manage Jobs
Jobs: Explained
Jobs are typically used without positions by service industries where flexibility and organizational change are key features. As
part of your initial implementation, you specify whether to use jobs and positions, or only jobs.
Basic Details
Basic details for a job include an effective start date, a job set, a name, and a code.
A job code must be unique within a set. Therefore, you can create a job with the code DEV01 in the US set and another job
with the same code in the UK set. However, if you create a job with the code DEV01 in the Common set, then you can't
create a job with the same code in any other set.
Benchmark Information
You can identify a job as being a benchmark job. A benchmark job represents other jobs in reports and salary surveys. You
can also select the benchmark for jobs. Benchmark details are for informational purposes only.
Progression Information
A progression job is the next job in a career ladder. Progression jobs enable you to create a hierarchy of jobs and are used to
provide the list of values for the Job field in the Promote Worker and Transfer Worker tasks.
The list of values includes the next three jobs in the progression job hierarchy. For example, assume that you create a job
called Junior Developer and select Developer as the progression job. In the Developer job, you select Senior Developer as
the progression job. When you promote a junior developer, the list of values for the new job will include Developer and Senior
Developer. You can select one of these values, or select another one.
Jobs and Grades

You can assign grades that are valid for each job. If you're using positions, then the grades that you specify for the job
become the default grades for the position.
Evaluation Criteria
You can define evaluation criteria for a job, including the evaluation system, a date, and the unit of measure for the system.
The Hay system is the predefined evaluation system that's available. An additional value of Custom is included in the list of
values for the Evaluation System field, but you must add your own criteria and values for this system.
Uploading Jobs Using a Spreadsheet

If you have a list of jobs already defined for your enterprise, you can upload them from a spreadsheet.
To use this option:

1. Download a spreadsheet template.
2. Add your job information to the spreadsheet.
3. Upload directly to your enterprise configuration.
429
You can upload the spreadsheet multiple times to accommodate revisions.
Related Topics
Job and Position Lookups: Explained
Enforcing Grades at Assignment Level: Points to Consider
Jobs and Positions: Critical Choices

Jobs and positions represent roles that enable you to distinguish between tasks and the individuals who perform those tasks.
Note the following:

The key to using jobs or positions depends on how each is used.
Positions offer a well-defined space independent of the person performing the job.
Jobs are a space defined by the person.
A job can be defined globally in the Common Set, whereas a position is defined within one business unit.
You can update the job and department of a position at any time. For example, if you hire someone into a new role
and want to transfer the position to another department.
During implementation, one of the earliest decisions is whether to use jobs or a combination of jobs and positions. The
determinants for this decision are:
The primary industry of your enterprise
How you manage your people
Primary Industry of Your Enterprise

The following table outlines information about Primary industries and how they set up their workforce.
Primary Industry Workforce Setup
Mining Positions

Utilities Positions

Manufacturing Positions

Retail Trade Positions

Transportation and Warehousing Positions

Educational Services Positions

Public Transportation Positions
430
Primary Industry Workforce Setup

Agriculture, Forestry, Fishing, and Jobs

Hunting

Construction Jobs

Wholesale Trade Jobs

Information Jobs

Finance and Insurance Jobs

Professional, Scientific, and Technical Jobs

Services

Management of Companies and Jobs

Enterprises

Administrative and Support and Waste Jobs

Management and Remediation Services

Arts, Entertainment, and Recreation Jobs

Accommodation and Food Services Jobs

Other Services (Except Public Jobs

Administration)

Management of People
Consider the following scenarios how industries manage their employee turnover:
Scenario 1: Replace employees by rehiring to the same role.
Scenario 2: Replace headcount but the manager uses the headcount in a different job.
Scenario 3: Rehire employees to the same position, but the manager requests reallocation of budget to a different
post.
The following table displays suggestions of what the industry should use, either jobs or positions, in the above three
scenarios:
Industry Scenario 1 Scenario 2 Scenario 3
Project (An industry that Positions Jobs Jobs

supports project-based forms of
organization in which teams of
specialists from both inside and
outside the company report to
project managers.)

431
Industry Scenario 1 Scenario 2 Scenario 3
Controlled (An industry that Positions Positions Positions

is highly structured in which
all aspects of work and
remuneration are well organized
and regulated. )

Manufacturing Positions Jobs Positions

Retail Positions Jobs Positions

Education Positions Jobs Positions

Other Positions Jobs Jobs

Related Topics
Grades and Grade Rates: How They Work with Jobs, Positions, Assignments, Compensation, and Payroll
Job and Position Structures: Explained

Job and position structures identify the descriptive flexfield structure that enables you to specify additional attributes that
you want to capture when you define jobs and positions. Job and position attributes provide further detail to make jobs and
positions more specific. You also use attributes to define the structure of your jobs and positions. You can specify attributes
at the enterprise level for jobs and positions, at the business unit level for positions, and at the reference data set level for
jobs. Job and position structures are optional.
Enterprise-Level Job Attributes

When you define a job, you enter a value for the name of the job. To make job names more specific, set up attributes to
identify additional details about the job, such as the nature of the work that is performed or the relative skill level required. If
these attributes apply to all jobs within your enterprise, set up enterprise-level job attributes. Standard capabilities mean that
you can use the different segments of the name to identify common jobs or job holders for analysis or compensation, or for
grouping records in reports, for example, to find all jobs of a specific job type. You should not use attributes with values that
change regularly, for example, salary ranges or expense approval levels that change every year.
432
This figure illustrates how job type and job level provide further details for the HR Application Specialist job.
Job Attributes
Job Name Job Type Job Level
HR Application
Consultant 4
Specialist
Enterprise-Level Position Attributes

Position attributes at the enterprise level are similar to those for jobs. Each position that you define identifies a specific role
in the enterprise, which you can manage independently of the person in the position. A position belongs to one specific
department or organization. The name of each position must be unique. To simplify the process of managing unique names
for positions, set up enterprise-level attributes to identify separate components of the position name. For example, you can
set up an attribute for position title and one for position number. When defining the attributes that make up the structure of
a position name, consider whether any of your attributes are part of the definition of a common job type. Using job types for
a position can help you manage common information that applies to many different positions. For example you can define a
job type of Manager.Level 1 and use this for comparison of positions across departments or lines or business, or for setting
common job requirements. You can then define multiple manager type positions in your HR department, each of which has
responsibility for a different management function or group.
433
This figure illustrates how title and position number provide further details for the manager position.
Position Attributes
Position
Position Name Title
Number
Assistant
Manager Store 10050
Manager
Business Unit-Level Attributes for Positions

If you have information that you want to capture for positions that is specific to each business unit, then you can define
attributes at the business unit level for positions. When you create positions, these attributes appear in addition to any
enterprise-level attributes. For example, you may want to identify the sales region for all positions in the sales business unit.
You can set up a text attribute called Sales Region and use it to enter the necessary information when creating positions for
the sales business unit.
Reference Data Set-Level Attributes for Jobs

If you have information for jobs that applies to specific reference data sets, set up attributes for jobs at the reference data set
level. When you create jobs, these attributes appear in addition to any enterprise-level attributes. For example, you may want
to identify all information technology (IT) jobs within a specific set. You can set up a text attribute called Function and use it to
enter IT in jobs that you create that perform an IT function within a specific set.
Jobs: Example
Jobs are typically used without positions by service industries where flexibility and organizational change are key features.
Software Industry
For example, XYZ Corporation has a director over the departments for developers, quality assurance, and technical writers.
Recently, three developers have left the company.

The director decides to redirect the head count to other areas.
Instead of hiring all three back into development, one person is hired to each department, quality assurance, and
technical writing.
434
In software industries, the organization is fluid. Using jobs gives an enterprise the flexibility to determine where to use head
count, because the job only exists through the person performing it. In this example, when the three developers leave XYZ
Corporation, their jobs no longer exist, therefore the corporation has the flexibility to move the headcount to other areas.
This figure illustrates the software industry job setup.
XYZ Corporation
Technology
Department
Quality Assurance
Developer Technical Writer
Specialist
Job Titles
Positions: Examples
Positions are typically used by industries that use detailed approval rules, which perform detailed budgeting and maintain
headcounts, or have high turnover rates.
Retail Industry
ABC Corporation has high turnovers. It loses approximately 5% of its cashiers monthly. The job of the cashier includes
three positions: front line cashier, service desk cashier, and layaway cashier. Each job is cross-trained to take over another
cashier's position. When one cashier leaves from any of the positions, another existing cashier from the front line, service
desk or layaway can assist where needed. But to ensure short lines and customer satisfaction, ABC Corporation must
replace each cashier lost to turnover. Since turnover is high in retail it's better for this industry to use positions.
Note the following:
An automatic vacancy is created when an employee terminates employment.

The position exists even when there are no holders. Having the position continue to exist is important if the person
who leaves the company is a manager or supervisor with direct reports.
All direct reports continue reporting to the position even if the position is empty.
You don't have to reassign these employees to another manager or supervisor. The replacement manager is
assigned to the existing position.
Also, an added advantage to using Positions is when you hire somebody new, many of the attributes are inherited from the
position. This speeds up the hiring process.
435
This figure illustrates the retail position setup.
Store Manager
Phil Jones
Assistant Store
Manager
Anita Camp
Cash Supervisor
Currently vacant
Service Desk
Front Line Cashier Layaway Cashier
Cashier
10 positions 2 positions
3 positions
Health Care Industry

Health care is an industry that must regulate employment, roles, and compensation according to strict policies and
procedures. Fixed roles tend to endure over time, surviving multiple incumbents. Industries that manage roles rather than
individuals, where roles continue to exist after individuals leave, typically model the workforce using positions.
The hospital has a structured headcount and detailed budgeting. For example, a specific number of surgeons, nurses, and
interns of various types are needed. These positions must be filled in order for the hospital to run smoothly. Use jobs and
positions when you apply detailed headcount rules.
436
This figure illustrates the hospital position setup.
Hospital
Jobs Surgeon Nurse Intern
Licensed
Cardiac Neural Registered Cardiac Neural
Practical
Surgeon Surgeon Nurse Intern Intern
Nurse
Positions
General Nursing General
Surgeon Aide Intern
FAQs for Manage Jobs

What's the difference between a job set and a job family?
A job family is a group of jobs that have different but related functions, qualifications, and titles. They are beneficial for
reporting. You can define competencies for job families by associating them with model profiles.
A job set is an organizational partition of jobs. For example, a job set can include global jobs for use in all business units,
or jobs for a specific country or line of business. When you select a job for a position or an assignment, you can view the
available jobs in your business unit set and the common set.
Related Topics
What's a job set?
Manage Facility Shifts, Workday Patterns, and Schedules
Schedule Components: How They Fit Together

Schedules are comprised of workday patterns and exceptions. Workday patterns are comprised of shifts. You can also
create exceptions, nonworking days, to the schedules.
437
Begin by creating shifts and then assigning those shifts to workday patterns. Next, create a schedule that is a collection of
workday patterns and any exception dates.
Shift Workday Pattern
Schedule
Exceptions
Shift
A shift is a period of time, typically expressed in hours, and it can be defined by a start time and an end time, or a duration. A
shift can be for a work period or an off period. You can create time, duration, and elapsed shifts.
438
Workday Pattern
A workday pattern is a collection of shifts for a specific number of days. You can create time, duration, and elapsed workday
patterns.
Exception
An exception is a record of a date that overrides the availability of a resource to which a schedule has been assigned. For
example, a resource is assigned a schedule that includes December 25 as a working day. An exception can be created for
December 25 and applied to that schedule to override resource availability for that date. Exceptions can also be for a date
time period such as 9 a.m. to 11 a.m. on December 25th.
Schedule
A schedule is defined by a start date, an end date, and a sequence of workday patterns to be followed between those dates.
A schedule can also contain exception dates that override the availability of resources to which the schedule is assigned.
Quarter types such as 4-4-5, 4-5-4 are supported.
Managing Shifts: Examples

A shift is a period of time, typically expressed in hours, that is used to build workday patterns. Workday patterns are used to
build schedules. There are multiple types of shifts you can create. The following scenarios illustrate each type.
Managing Time Shifts

Next month you are adding a second shift for your manufacturing operations. This new shift will start right after your regular
first shift. You can create a time shift that starts at 4:00 p.m. and ends at 12:00 a.m. There are restrictions in updating existing
shifts and patterns. Shifts and patterns cannot be updated if the change affects a schedule, that is they are associated to
a schedule. If a shift is created but not assigned to a pattern (or assigned to a pattern but the pattern is not assigned to a
schedule) it can be updated. If a pattern is created and not assigned to a schedule it can be updated.
Managing Time Shifts with Punch Details

Your division has decided that the employees in the office must clock in and out for lunch starting next week. All employees
will take the same lunch hour. Add punch shift details to the existing shift so that employees punch in at 8:00 a.m.; they
punch out for lunch from 11:30 a.m. to 12:30 p.m.; they punch back in at 12:30 p.m.; and they punch out for the day at 5:00
p.m.
Managing Time Shifts with Flexible Details

Jorge Sanchez is a contractor who is starting work in your department next week. His hours will be flexible, so you need to
create a new time shift with flexible details that he can use to record his time. He will have a flexible start time from 7:00 a.m.
to 9:00 a.m. and a flexible end time from 4:00 p.m. to 6:00 p.m. His core work hours will be from 9:00 a.m. to 4:00 p.m.
Managing Duration Shifts

One of the divisions in your organization does not use fixed start and end times for its daily shifts; the division only records the
total duration of the shift and indicates if resources are available or not during that time. All of the employees in the division are
available for 24 hours straight, and then they are not available for the next 24 hours. You should create a duration shift that
indicates that resources are available for 24 hours, and create a second duration shift that indicates that resources are not
available for 24 hours.
439
Managing Elapsed Shifts

The employees in the Human Resources department all work 8 hours a day, but the start and end times vary by employee.
Some employees start at early as 6:00 a.m., while others don't start until 9:00 a.m. Create an elapsed shift with a duration of
8 hours, where all employees are assumed to be available for the number of hours in the shift at any time during the day.
Managing Workday Patterns: Examples

A workday pattern is a collection of shifts for a specific number of days. There are multiple types of workday patterns you can
create. The following scenarios illustrate each type.
Managing Time Workday Patterns

Your department works a Monday through Friday workweek with 8 hour shifts each day. Time patterns always have time
shifts. That is, the shift will have start time and end time. You can create a time workday pattern with a length of 7 days and
details of an 8 hour time shift for days 1 through 5. Days 6 and 7 are considered nonworking days.
Managing Duration Workday Patterns

A new group of employees starts next month, and each employee will work a schedule where he or she is available for 10
hours, and then not available for the next 16 hours, and then available for 10 hours again, and so on. This pattern starts on
midnight of the first day of the next month. Create a duration workday pattern with a 10-hour available duration shift, followed
by a 16-hour not available duration shift. Do not specify the pattern length or start and end days, and the pattern will repeat
for the length of the schedule to which it is associated.
Managing Elapsed Workday Patterns

In the summer, several divisions in your organization work only 4 hours on Fridays. They work extended hours on
Wednesdays and Thursdays to cover the 4 hours they will not work on Fridays. Create an elapsed workday pattern with
a length of 7 days. Days 1 and 2 will have an 8-hour shift assigned, while days 3 and 4 will have a 10-hour shift assigned.
Finally, day 5 will have a 4-hour shift assigned. As in the time workday pattern, days 6 and 7 are considered nonworking days.
Manage Inventory Organizations
Inventory Organizations: Explained

An inventory organization is a logical or physical entity in the enterprise that is used to store definitions of items or store and
transact items.
You select the following usages in the inventory organization's properties:
Item management
Item and inventory management
Item Management
Inventory organizations used for item management, which are the same as item organizations, store only definitions of
items. Use inventory organizations for item management when the storage or movement of inventory does not need to be
440
physically or financially tracked. For example, in a retail implementation you can create an inventory organization for item
management to store the names of items that are listed by and sold through each retail outlet, while a different system tracks
physical inventory and transactions. If it is necessary in the future, you can change an inventory organization's usage from
item management to item and inventory management in the inventory organization's properties.
Item and Inventory Management

Inventory organizations used for item and inventory management store and transact items, in addition to item definitions.
An inventory organization used for item and inventory management is associated with one business unit, one legal entity,
and one primary ledger. Use inventory organizations for item and inventory management when the storage or movement of
inventory needs to be physically and financially tracked. Inventory organizations used for item and inventory management
can represent facilities such as manufacturing centers, warehouses, or distribution centers. You cannot change an inventory
organization's use from item and inventory management to item management.
Related Topics
What's an item master organization?
Inventory Organization: Critical Choices

In Oracle Fusion, storage facilities, warehouses, and distribution centers are implemented as inventory organizations.
Inventory organizations are:
Managed by a business unit, with the materials management business function enabled.
Mapped to a legal entity and a primary ledger.
Two types of inventory organizations exist.
Manufacturing facilities
Storage facilities
Storage and manufacturing facilities are related to other organizational entities through a business unit that stores,
manufactures, and distributes goods through many factories, warehouses, and distribution centers. The material parameters
are set for both the facilities, enabling movement of material in the organization. This business unit has the business function
of Materials Management enabled. Oracle Fusion Applications permit many inventory organizations to be assigned to one
business unit.
Distribution Center as an Inventory Organization

A distribution center can store inventory that is the responsibility of different business units. In this situation, assign an
inventory organization to each business unit as a representation of the inventory in the distribution center. The multiple
inventory organizations representing the inventory are defined with the same location to show that they are a part of the same
distribution center.
441
In the following figure the two business units, Air Compressors and Air Transmission, share one distribution center in Atlanta.
The two inventory organizations, Air Compressors and Air Transmission represent the inventory for each business unit in the
Atlanta distribution center and are both assigned the Atlanta location.
Air Air
Compressors Transmission
Business Unit Business Unit
Products Warehouse Products Warehouse

Air Compressors Air Transmission
Inventory Organization Inventory Organization
Distribution
Center
Location Atlanta
Legal Entities Own Inventory Organizations

A legal entity owns the inventory located in a storage or manufacturing facility. This ownership is assigned through the
relationship of the inventory organization representing the inventory and the legal entity assigned to the inventory organization.
The legal entity assigned to the inventory organization shares the same primary ledger as the inventory organization's
business unit.
The inventory is tracked in the inventory organization owned by the legal entity of which the business unit is part. All
transactions are accounted for in the primary ledger of the legal entity that owns the inventory.
442
The figure below illustrates the inventory owned by InFusion Air Quality legal entity. The InFusion Air Quality legal entity
is associated with the Air Compressors business unit, which is associated with the two Air Compressors inventory
organizations. Therefore, InFusion Air Quality legal entity owns the entire inventory in both the Dallas and Atlanta locations.
Air InFusion
Compressors Air Quality Legal
Business Unit Entity

Atlanta Dallas
Air Compressors Air Compressors
The default legal entity assigned to the business unit must be the
same as the legal entity assigned to the inventory organization.
Facility Schedules Are Associated with Inventory Organizations

A prerequisite to defining an inventory organization is to define a facility schedule. Oracle Fusion Applications permit you to
associate an inventory organization with a schedule.
Facility schedules permit creating workday calendars for inventory organizations that are used in the Oracle Fusion Supply
Chain Management product family. For example, use workday calendars in the scheduling of cycle counts and calculating
transit time.
Inventory Organization Prerequisites: Points to Consider

You can create a new inventory organization, or select an existing organization to define as an inventory organization.
Before creating inventory organizations:

Set up inventory organization dependencies
Plan inventory organization parameters
Setting Up Inventory Organization Dependencies

When you create an inventory organization, you must associate it to dependencies, such as business units and legal entities.
For this reason, create these dependencies before creating an inventory organization.
Planning Inventory Organization Parameters

Before creating an inventory organization, plan the inventory organization's parameters
Consider the following when planning to configure an inventory organization's parameters
Which schedule to use
443
Which inventory organization to serve as the item master organization

Whether to configure locator control and if so, the level at which to enforce the locator control
How you want to configure movement request settings such as pick slip batch size and replenishment movement
request grouping
Consider the size of your operation, your usage of subinventories, and the type of labor or equipment required when
considering whether you want to use organization- or subinventory-level replenishment movement request grouping.
How you want to configure lot, serial, and packing unit generation settings
To make appropriate choices for these settings, you should be familiar with:
Your company's guidelines for creating lot names, serial numbers, and packing unit numbers
Whether your company requires you to assign the same lot number to multiple items in the same organization,
or a specific lot number to only one item in the same organization
Whether your company requires you to place purchase order or shipping order material under lot control
How you want to configure item sourcing details, such as the picking rule to use, and whether to specify the
inventory organization as a logistics services organization
Rounding the Reorder Quantity: How It Affects Min-Max Planning

Reorder Calculations
When you specify to round reorder quantities, min-max planning reorders for item subinventories are automatically rounded
up or down.
Settings That Affect Rounding the Reorder Quantity

Reorder quantities for an item subinventory are calculated based on:
The setting that you select for the Round Order Quantity parameter on the Manage Inventory Organization
Parameters page, General tab, of the inventory organization containing the item subinventory
The value that you specify for the Fixed Lot Multiple text box on the Add Item to Subinventory window
How Rounding the Reorder Quantity Affects Min-Max Planning Reorder Quantity
Calculations
If you enable rounding the reorder quantity for the inventory organization, and specify the fixed lot multiple for the item
subinventory, the reorder quantity is rounded up. If you disable rounding the reorder quantity for the inventory organization,
and specify the fixed lot multiple for the item subinventory, the reorder quantity is rounded down.
Note: To round reorder quantities, you must specify a fixed lot multiple.
Example: Rounding the Reorder Quantity

Assume that the reorder quantity is 24. If you enable rounding the reorder quantity and specify 10 for the fixed lot multiple,
the reorder quantity is rounded up to 30. If you disable rounding the reorder quantity and keep the fixed lot multiple at 10, the
reorder quantity is rounded down to 20.
444
Selecting Lot Number Uniqueness Control: Critical Choices

Select one of the following lot number uniqueness control options to apply to the items in your inventory organization:
No uniqueness control
Across items
No Uniqueness Control
You can assign the same lot number to multiple items in the same inventory organization and across inventory organizations.
The following table provides an example of how lot numbers are generated when uniqueness control is not applied, both
within and across inventory organizations.
Within Inventory Organization Across Inventory Organizations
Item AS100 (printer) / Lot LN100 Item AS100 (printer) / Lot LN100

Item AS101 (laptop computer) / Lot Item AS101 (laptop computer) / Lot LN100
LN100

Across Items
You can only assign a unique lot number to a single item in one inventory organization. If the same item is also in a different
inventory organization, you must assign that item a unique lot number. The following table provides an example of how lot
numbers are generated when uniqueness control is applied across items, both within and across inventory organizations.
Within Inventory Organization Across Inventory Organizations
Item AS100 (printer) / Lot LN100 Item AS100 (printer) / Lot LN300

Item AS101 (laptop computer) / Lot Item AS101 (laptop computer) / Lot LN400
LN200

FAQs for Manage Inventory Organizations

What happens if I select the Supplier item sourcing type for replenishment?
Items are replenished from an external supplier.
What happens if I create an inventory organization as a logistics services organization?

The inventory organization is not costed, and shipment lines from different logistics service provider customers cannot be
packed in the same packing unit.
445
Manage Item Organizations
Item Organization: Explained

An item organization defines an item when inventory balances are not stored and inventory storage or inventory movement
is not reflected in the Oracle Fusion Applications. For example, you would use an item organization in a retail scenario, if
you need to know the items that are listed by and sold through each retail outlet even though inventory and transactions are
recorded in another system. In Oracle Sales Cloud, item organizations are used to define sales catalogs.
Note:
Items belong to an item organization.
Item attributes that are associated with financial and accounting information are hidden from the item if it exists
within the item organization.
Item organizations can be changed by administrators to an inventory organization by updating the necessary
attributes. There is no difference in the way items are treated in these two types of organizations except that
there cannot be any financial transactions in the downstream applications for items that are assigned to an item
organization.
Item Master Organization: Explained

An item master organization lists and describes items that are shared across several inventory organizations or item
organizations.
446
The following example shows the choice between inventory organizations that track inventory transactions, stored in two
warehouses, and item organizations that just track items, listed in two sales catalogs.
Item Master
Inventory Organization
Holds definition of all items
and tracks transactions.

Atlanta Dallas
Item Master
Item Organization
Holds definition of all items and
does not track transactions.
Catalog Catalog
US West Sales US East Sales
Item Organization Item Organization
For the most efficient processing, you should:
Have a single item master.

Include an item and its definition of form, fit, and function only once in the item master.
Separate the item master organization from organizations that store and transact items.
Note: Oracle Fusion permits multiple item masters, however, use this capability cautiously. If you acquire
a company, there may be value in keeping the old item master for a transition period. If you manage your
subsidiaries as separate businesses, there may be reduced value in a single item master.
447
448
Implementing Enterprise Structures and General Ledger Hyperion Financial Management Integration
13 Hyperion Financial Management

Integration
Oracle Hyperion Financial Management: Overview

Oracle Hyperion Financial Management is a comprehensive, web-based application that delivers global collection, financial
consolidation, reporting, and analysis in one highly scalable solution. Financial Management can be licensed and integrated
with the Oracle Fusion Accounting Hub to provide expanded financial consolidation, reporting, and analysis functionality.
Financial Management supports these features:
Comprehensive view of your enterprise financial information that provides key performance and operating metrics
from global sources
Close features that include intercompany reconciliations and a consistent set of data and business measures
Powerful multidimensional analysis that identifies and reports sources of profitability and cash flow at corporate, cost
center, product, brand, customer, and channel levels
Flexible what-if scenario management that dynamically consolidates and reports all financial budgets, forecasts and
plans, producing statements as assumptions and facts change
High-volume, preformatted reports that deliver timely including financial information for internal management and
external regulatory and government bodies
The following table provides installation and configuration activities and documentation references.
Activity Documentation
Installation of Financial Management Oracle Hyperion Enterprise Performance Management System Installation and Configuration Guide
for Oracle Hyperion Enterprise Performance Management

Configuration of Financial Management Oracle Hyperion Enterprise Performance Management System Installation and Configuration
including extended analytics Guide for Oracle Hyperion Enterprise Performance Management
Oracle Hyperion Financial Management Administrator's Guide for Oracle Hyperion Financial
Management
Integration of Financial Management Oracle Hyperion Financial Data Quality Management ERP Integration Adapter for Oracle Applications
Administrator's Guide

License and integration with Oracle Oracle Hyperion Financial Close Management Administrator's Guide for Oracle Hyperion Financial
Hyperion Financial Close Management, Close Management
which enables you to define, execute,
and report on the interdependent
activities of a financial close period. It
provides centralized monitoring of all
close process tasks and provides a
visible, automated, repeatable process
for running close processes.

License and integration with Oracle Oracle Hyperion Disclosure Management User's Guide for Oracle Hyperion Disclosure Management
Hyperion Disclosure Management,
which helps companies ensure the
449
Implementing Enterprise Structures and General Ledger Hyperion Financial Management Integration
Activity Documentation
completeness and accuracy of external
and statutory financial reports, and
their transformation into specifically
stylized statutory filings using extensible
Business Reporting Language.

Note: Two integration points exist between Financial Management and the Oracle Fusion Governance, Risk,
and Compliance solution set. Both integrations are delivered and deployed as Oracle Fusion Governance, Risk,
and Compliance Blueprint solutions. See the Oracle Fusion Governance, Risk, and Compliance documentation.
Integration with Hyperion Financial Management: Overview

For Oracle Cloud implementations, integrate with on-premise Oracle Hyperion Financial Management for advanced financial
consolidations by manually exporting your balances from Oracle Fusion Accounting Hub and loading them to Oracle Hyperion
Financial Management. Export your balances using either financial reports or Smart View.
For other implementations, Oracle Fusion Applications provides integration between Oracle Fusion Accounting Hub and
Oracle Hyperion Financial Management through Oracle Financial Data Quality Management ERP Integrator adapter. To
complete the post-installation setup for the ERP Integrator adapter, see Oracle Hyperion Financial Data Quality Management
ERP Integrator Adapter for Oracle Applications Administrator's Guide.
Related Topics
Oracle Fusion Accounting Hub: How It Works
Oracle Fusion Accounting Hub Features: Overview
450
Implementing Enterprise Structures and General Ledger Budget Configuration
14 Budget Configuration
Budget Uploads: Overview

In Oracle Fusion 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
451
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.
Budget Preparation
Upload
Scenario: Budget
ADFdi Spreadsheet
Comma Separated Flat File
Budget Reporting
Financial Reporting
General Accounting Dashboard
Adhoc Analysis with Smart View
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
452
Importing Budget Data from a Flat File: Explained

Use the Upload Budgets processes to integrate budget information from other budgeting applications such as Oracle
Hyperion Planning. You can load your budget amounts to the General Ledger balances cube by populating the
GL_BUDGET_INTERFACE table and running the Validate and Upload Budgets process. You can load budgets for multiple
periods and for multiple ledgers with the same chart of accounts in a single load process. Note that the budget data isn't
loaded to the GL_BALANCES table and only loaded to the balances cube for variance reporting purposes.
Note: You can load data to interface tables using predefined templates and the Load Interface File for Import
scheduled process, which are both part of the External Data Integration Services for Oracle Cloud. For more
information about file-based data import, see the File Based Data Import guide for your cloud services.
Assigning Values for Columns in the GL_BUDGET_INTERFACE Table

For budget import to be successful, you must enter values in the columns of the interface table that require values.
Name Value
RUN_NAME Enter a name to identify the budget data set being imported.

STATUS Enter the value NEW to indicate that you are loading new budget data.

LEDGER_ID Enter the appropriate ledger ID value for the budget amount. You can view the ledger ID for your
ledgers on the Manage Primary Ledgers page. The ledger ID column is hidden by default, but you
can display it from the View Columns menu. If you enter multiple ledgers for the same run name, all
of the ledgers must share the same chart of accounts.

BUDGET_NAME Enter the appropriate budget name value for the budget line. You define the budget names in the
Accounting Scenario value set.

PERIOD_NAME Enter the period name that you are loading the budget data for. You can load budget data to Never
Opened, Future Enterable, and Open periods only.

CURRENCY_CODE Enter the currency for the budget.

SEGMENT1 to SEGMENT30 Enter valid and enabled account values for each segment in the chart of accounts.

BUDGET_AMOUNT Enter the amount in the ledger currency for account types, expense and assets.

OBJECT_ VERSION_ NUMBER For Oracle Cloud implementations, leave this field blank as the application automatically populates
this when you load the data from the secure FTP server. For other implementations, you can set the
column to a value of 1.

453
These columns remain blank because the budget import process either uses these columns for internal processing, or
doesn't currently use them.
CHART_OF_ACCOUNTS_ID
CODE_COMBINATION_ID
ERROR_MESSAGE
CREATION_DATE
CREATED_BY
LAST_UPDATE_DATE
LAST_UPDATE_LOGIN
LAST_UPDATED_BY
REQUEST_ID
LOAD_REQUEST_ID
Related Topics
External Data Integration Services for Oracle Cloud: Overview
Loading Data to the Budget Interface Table: Explained

Load the budget amounts to the interface table by performing the following steps.
1. Export budget data from your budgeting application to a comma separated values (.csv) file. The file-based data
import for Import General Ledger Budget Balances has a template that you can use. For more information about file-
based data import, see the File Based Data Import for Oracle Financials Cloud guide.
2. Upload the zipped .csv file to the UCM directory fin/bugetBalance/import.
3. Launch the scheduled process called Load Interface File for Import and select the following parameters:
Import process: Validate and Upload Budgets
Data file: Select the name of the zipped .csv file

4. Run the Validate and Upload Budgets process to load the budget amounts to the General Ledger balances cube.
454
5. Review the logs for validation errors. If there are validation errors, correct the data in the template and regenerate
the .csv file. Then resubmit the data by repeating steps 3 and 4.
Flat File Import Process
CSV File
Log Load Interface File for Import

Process
GL Budget Interface
Log
Validate and Upload
Log
Upload Budgets
GL Balances Cube
Related Topics
455
Importing Budget Data from a Spreadsheet: Explained

Use Oracle Application Development Framework (ADF) Desktop Integrator to enter, load, and correct budget data. This
functionality uses a new interface table called the GL_BUDGET_INTERFACE and requires the duty role, Budget Entry Duty.
Budget Import
Budget Import Oracle ADF Desktop Integrator import functionality is similar to the journal import sheet in Oracle Fusion
General Ledger. You may use this tool to create and upload budget data. From the General Accounting Dashboard page,
download the import worksheet.
The budget import uses the Accounting Scenario value set for the budget being loaded. The Run Name is used as an
identifier for the imported data set. The Oracle ADF Desktop Integrator budget import functionality:
Supports multiple ledgers but a single chart of accounts instance

Allows multiple calendars and periods
Supports entered currencies in addition to the ledger currency
Contains user-friendly lists of values
Performs most validations on the worksheet
456
Secures values by data access sets
ADFdi Spreadsheet Import Process
ADFdi Spreadsheet
ADFdi Load Process
GL Budget Interface
Log
Validate and Upload
Log
Upload Budgets
GL Balances Cube
Note: The ADF Desktop Integrator spreadsheet contains a Record Status column that shows if the rows upload
successfully or with errors. Use the spreadsheet where the data was entered to enter the corrections.
Budget Correction with Oracle ADF Desktop Integrator:

Explained
Oracle ADF Desktop Integrator correction functionality is similar to the journal correction sheet in Oracle Fusion General
Ledger. You use this tool to correct the flat file import errors.
457
The correction spreadsheet functionality:

Uses segment labels based on the data access set
Contains user friendly lists of values
Performs most validations on the worksheet
Allows updating or marking the row for deletion.
Correcting Data
To use the correction spreadsheet functionality perform the following steps:
1. From the General Accounting Dashboard page, you set the data access set and download the correction
worksheet.
2. After the correction worksheet is downloaded, you query for the rows in error. Pick the run name for which there are
validation errors and click on the Search button. This populates the budget rows in error.
3. Correct the rows in error or mark for deletion and submit the journal correction spreadsheet. Any errors will be
reported on the worksheet.
4. If the row status indicates an error, double-click it to see the error details and take necessary action. You can use the
list of values to quickly correct data that is in error.
Oracle Hyperion Planning: Overview

Oracle Hyperion Planning is a comprehensive, web based, budgeting and planning application. Planning can be licensed and
integrated with the Oracle Fusion Accounting Hub to provide expanded budgeting and planning functionality.
Oracle Hyperion Planning:
Delivers global collection of data and financial consolidation
Enables data entry, analysis, and reporting, including personalizing data entry forms
Facilitates budgeting collaboration, communication, and control across multidivisional global enterprises
Drives the planning process
Provides a framework for perpetual planning, with attention to managing volatility and frequent planning cycles
Promotes modeling using complex business rules and allocations
Integrates with Smart View so you can design worksheets in Microsoft Excel to enter, format, analyze, and report on
data
The following table provides installation and configuration activities and documentation references.
Activities Documentation
Installation of Planning Oracle Hyperion Enterprise Performance Management System Installation and Configuration Guide
for Oracle Hyperion Enterprise Performance Management

Configuration of Planning Oracle Hyperion Planning

Integration of Planning Oracle Hyperion Financial Data Quality Management ERP Integration Adapter for Oracle Applications
Administrator's Guide
458
Activities Documentation

Integration with Oracle Enterprise Planning and Budgeting

Cloud Service: Overview
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).
459
460
Implementing Enterprise Structures and General Ledger Financial Reporting
15 Financial Reporting
Financial Reporting Center Implementation: Points to

Consider
The Financial Reporting Center adds self-service functionality for the Oracle Fusion Applications and the Oracle Fusion
Accounting Hub. The financial reports are available immediately on both computers and mobile devices, which leads to
quicker decision making.
Note: To access the reports in Financial Reporting Center, store the reports in the My Folder or Shared Custom
directories.
Job Roles and Duty Roles

The following table shows the predefined job roles and their associated duty roles.
Predefined Job Role Duty Roles
General Accountant Financial Reporting Management

Account Balances Review
General Accounting Manager Financial Reporting Management

Financial Analyst Financial Reporting Management

Business Process Model Information

The features are part of the Manage Financial Reporting and Analysis detailed business process.
The following table shows the activities and tasks for that business process.
Activity Task
Prepare Financial Reports Generate Financial Statements

Analyze Financial Performance Inquire and Analyze Balances

461
Financial Reporting Center: How It Works

The Financial Reporting Center is intended to be the primary user interface for financials end users to access all seven report
types.
Financial Reporting Center Overview
Financial Reporting Center Other Reporting Tools
Can be used for the

Financial same 7 report types
Account Groups Smart View
Reporting Studio
and Sunburst Reports
Reports
Oracle Transactional BI Oracle Transactional BI

Analyses Dashboards
Oracle BI Publisher
BI Mobile Apps
Reports
Oracle Fusion General

Ledger Balances Cube
Enterprise Performance
Management Workspace
Oracle Transaction Tables
Reports can be accessed through various methods. However, the Financial Reporting Center provides access to every type
of report, is intended to be the primary user interface for financials end users, and is tablet and smartphone friendly.
Financial Reports are read from the Shared > Custom > Financials and My Folders directories. All other report types can
be saved anywhere in the BI Catalog however, any custom content should be in the Shared > Custom folder. Subfolders
can be created within the Shared > Custom folder.
Seven types of reports can be run from the Financial Reporting Center and from the other reporting tools.
Financial Reports: These reports are built off of the Oracle Financial Reporting Studio using data in the Oracle Fusion
General Ledger balances cube. For example, company income statements and balance sheets. These reports are
mainly run by users in General Ledger.
Account Groups and Sunburst: Account groups are used to monitor key accounts in General Ledger. When a user
creates an account group, it becomes visible in the Financial Reporting Center with the Sunburst visualization tool.
462
The Sunburst visualization tool lets you interact with your account balances across various business dimensions to
view balances from different perspectives. Account groups are used only in General Ledger.
Smart View Reports: Smart View is a multidimensional pivot analysis tool combined with full Excel functionality.
Smart View enables you to interactively analyze your balances and define reports using a familiar spreadsheet
environment. These queries are mainly for users in General Ledger. To share Smart View queries, users can email
them to other users, or they can upload the queries to the Financial Reporting Center where users can download
them to a local drive for use. The Financial Reporting Center is only a place for users to upload and download Smart
View queries.
Note: To upload a Smart View report to the Financial Reporting Center: select the Open Workspace for
Financial Reports task, navigate to the BI Catalog, and select Upload from the Tasks section. Be sure to
upload the Excel file to one of the folder locations mentioned previously.
Oracle Transactional Business Intelligence Analyses: These analyses and reports are built off of transactional
tables using subject areas. These reports can be run by users in General Ledger, Payables, Receivables, Cash
Management, Intercompany, and so on.
Oracle Transactional Business Intelligence Dashboards: Dashboards put all the information, functions, and actions
that a business user must have to do their job in one place. Dashboards are built off of Oracle Transactional
Business Intelligence objects like analyses and reports. These reports can be run by users in General Ledger,
Payables, Receivables, Cash Management, Intercompany, and so on.
Oracle Business Intelligence Publisher Reports: Most of these reports are predefined and must first be submitted
and resubmitted to see the latest data by the Oracle Enterprise Scheduler through the Scheduled Processes
navigation. These reports can be run by users in General Ledger, Payables, Receivables, Cash Management,
Intercompany, and so on.
BI Mobile Apps: Oracle Business Intelligence Mobile App Designer is an application that enables you to create
multitouch information-driven applications with rich interaction, rich visualization, and rich media, for mobile devices
such as iPhone, iPad, Android phone, tablet, and more. These reports can be run by users in General Ledger,
Payables, Receivables, Cash Management, Intercompany, and so on.
Other Reporting Tools Overview

Six other tools are available for reporting in Financials.
The following table lists the other reporting tools and the types of reports they support.
Other Reporting Tools Report Type
General Accounting Dashboard and Account Groups

Account Inspector

Reports and Analytics Oracle Transactional Business Intelligence Objects

BI Catalog All Report Types, Except Oracle Business Intelligence Publisher Reports

Enterprise Performance Management Reports, Books, Snapshot Reports, Snapshot Books, Financial Reporting Batches, and Batch
Workspace Scheduler

Enterprise Scheduler System Oracle Business Intelligence Publisher Reports

463
Even though the Financial Reporting Center is designed to be the main user interface for a financial end user's reporting
needs, some users may choose to use any of the six other tools for reporting in financials, such as:
General Accounting Dashboard, which provides access to Account Groups: Uses the Account Monitor to efficiently
monitor and track key account balances in real time.
Account Inspector: Perform ad hoc queries from account groups and financial reports through drill down to
underlying journals and subledger transactions.
Reports and Analytics: This reporting tool has a panel that reflects the folder structure of the BI Catalog. Users
can access and run any Oracle Transactional Business Intelligence analysis, report or dashboard. Users can't run
Financial Reports or Oracle Business Intelligence Publisher reports from this interface. This interface can be used by
all financials users.
BI Catalog: A component of the Enterprise Performance Management Workspace where you can run all report
types, except for Oracle Business Intelligence Publisher reports.
Enterprise Performance Management Workspace: Create reports, books, snapshot reports, snapshot books,
Financial Reporting batches, and batch scheduler, and schedule batches to automatically run and burst to email.
Enterprise Scheduler System: Only Oracle Business Intelligence Publisher reports can be submitted from this
interface. Users access this interface by navigating to Tools > Scheduled Processes. Most financial users have
access to this interface to run standard reports for General Ledger, Payables, Receivables, and so on.
Setting Up Your Financial Reporting Center: Critical

Choices
Oracle Fusion Financial Reporting Center is a powerful tool for reviewing, designing, and presenting financial reports and
analytic data. The critical choices required to configure and install the components in Financial Reporting Center consist of:
Configuring the Financial Reporting Center
Installing and configuring Financial Reporting Studio, performed by your end users
Installing Smart View, performed by your end users
Configuring Workspace Database Connection, performed by your administrator
Configuring Oracle Transactional BI Dimensions
Configuring Financial Reporting Center

You have access to the reports in the Financial Reporting Center and Workspace installed with Oracle Fusion Financial
Applications. Your Oracle Fusion Business Intelligence (BI) administrator defines the folder structure in Workspace. The
administrator considers your company's security requirements for folders and reports, as well as report distribution
requirements for financial reporting batches.
Security can be set on folders and reports from Workspace.
You are granted access to the folders and reports you want to view by your BI administrator.
Installing and Configuring Financial Reporting Studio

Oracle Financial Reporting Studio is client-based software. If you open Oracle Fusion Applications from Oracle Cloud, you
connect to the Financial Reporting Studio through a Windows Remote Desktop Connection. Report authors download
464
installation files for Financial Reporting Studio from Workspace by clicking Navigator > Financial Reporting Center >
Tasks panel drawer > Open Workspace for Financial Reporting. Once Workspace is started, click Tools > Install >
Financial Reporting Studio. After performing the prerequisites and completing the installation, start the Financial Reporting
Studio. Provide your user ID, password, and the Server URL. Derive the Server URL information by following the steps:
1. Open Navigator > Financial Reporting Center > Tasks panel drawer > Open Workspace for Financial
Reporting.
2. Edit the Workspace URL and remove workspace/index.jsp.
3. Following are two examples of Server URLs:
If the Workspace URL is https://fusionsystemtest-p-external-bi.us.oracle.com/workspace/index.jsp, the

Server URL is https://fusionsystemtest-p-external-bi.us.oracle.com.
If the Workspace URL is https://fusionsystemtest-p-external-bi.us.oracle.com:10622/workspace/index.jsp,
the Server URL is https://fusionsystemtest-p-external-bi.us.oracle.com:10622.
4. Copy the modified URL to the Server URL field.
Note: For end users installing the Oracle Fusion Financials Reporting Studio, the installer starts a separate
console window. The installer continues to run for a brief time after the installation completes the setup tasks.
The process is normal, expected, and applies to Oracle Reporting Studio installations in both the Oracle Fusion
Applications and Enterprise Performance Manager modes. Wait for the console window to close, which happens
automatically, before clicking the Finish button on the Financial Reporting Studio Installation dialog box. If you
click the Finish button before the console window closes, the Financial Reporting Studio installation may not
complete.
Note: You must save a new report before attempting to preview it with Web Preview.
Prerequisites needed for installing the Financial Reporting Studio are:
1. Financial Reporting Studio Client Certifications that are found at: http://www.oracle.com/technetwork/middleware/bi-
foundation/hyperion-supported-platforms-085957.html.
2. Microsoft Office installed on your users' computers.
Installing Smart View

Smart View is an Excel add-in that must be loaded on each client. To download Smart View, click Navigator > Financial
Reporting Center > Tasks panel drawer > Open Workspace for Financial Reports. Once the workspace is started,
click Tools > Install > Smart View.
Note: Since Smart View is an add-in to Microsoft Office products, you can install Smart View only on a
Windows operating system.
Once Smart View is installed, you must configure the connection using the Smart View Shared Connections URL. You can
derive the Shared Connections URL by following these steps:
1. From the Financial Reporting Center task panel, select Open Workspace for Financial Reporting.
2. Edit the workspace URL by removing index.jsp and adding SmartViewProviders at the end.
Note: The following URL is an example for a Cloud-based environment. If the workspace URL
is https://efops-rel5st4-cdrm-external-bi.us.oracle.com:10622/workspace/index.jsp, the Shared
Connections URL is https://efops-rel5st4-cdrm-external-bi.us.oracle.com:10622/workspace/
SmartViewProviders.
465
3. Copy the URL.

4. Open Excel.
5. From the Smart View menu, click Options > Advanced.
6. Paste the URL in the Shared Connections URL field.
7. Click OK.
For more information about configuring Smart View client for users, see Oracle Smart View for Office User's Guide.
To connect Oracle Fusion General Ledger Balances cubes in Smart View:

1. Open Smart View from your Start menu > Programs > Microsoft Office > Microsoft Excel 2007.
2. Navigate to the Smart View menu > Open. On the Start on the ribbon, click Smart View Panel that appears in the
list of values under the ribbon. The task pane opens.
3. Click Shared Connections on the task pane.
4. Sign in with your user name and password.
5. Click the Select Server to proceed list of values.
Note: If the Essbase Server is not there, then it has to be added. Use the following steps:
a. Click the Add Essbase Server link.
b. Specify the Essbase Server login and password.
c. Expand the Essbase server and locate the cube under it.
6. Select Oracle Essbase from the list of shared connections.
7. Click the Expand to expand the list of cubes.
8. Expand your cube (name of your chart of accounts).
9. Click db. A list of functions appears on the bottom of the panel.
10. Click the analysis link.
Note: You must perform these steps only once for a new server and database.
To set how the name and alias of the Essbase database appears:
1. Click Options on the ribbon > select the Member Options > select Member Name Display.
2. Set one of these three options:
Distinct Member Name. Only shows the full Essbase distinct path.
Member Name and Alias: Shows both the member name and the alias.
Member Name Only. Shows only the member name.
Note: The Smart Slice feature is not supported in Oracle Fusion General Ledger. For all other documentation,
refer to the Oracle Smart View for Office User's Guide.
Configuring Workspace Database Connections

Administrators must create database connections from Workspace so users can access the cubes from Workspace and
Financial Reporting Studio.
Note: Ledger setup has to be completed before the database connection can be created. Oracle Fusion
General Ledger balances cubes are created as part of ledger setup. A separate cube is created for each
combination of chart of accounts and accounting calendar. A database connection is needed for each cube.
466
Steps to define a database connection are:

1.Start at the Navigator by selecting Financial Reporting Center.
2.From the Financial Reporting Center task panel, select Open Workspace for Financial Reporting.
3.From within Workspace select the Navigator menu > Applications >BI Catalog.
4.Select Tools menu > Database Connection Manager.
5.Select New button.
6.Enter a user-friendly name for the Database Connection Name.
7.Enter Essbase as the Type, your server, user name, and password.
8.Select Application (cube) and Database from the list of values. Expand the Application name to see the related
Database.
9. Click the OK button twice to save your selections.
10. Click Close button in the Database Connection Manager window to save your connection.
For more information about configuring Essbase database connections in Workspace see: Database Administrator's Guide
for Oracle Essbase.
Note: The database connection is available in both Workspace and Financial Reporting Studio. Optionally,
it can be set up in Financial Reporting Studio when putting grids on a report. This should only be done by an
administrator.
Configuring Oracle Transactional BI Dimensions

Within Oracle Transactional Business Intelligence (BI), Accounting Segment Dimensions such as Balancing segment or Cost
Center segment are based on the Chart of Accounts configuration. These segments can be configured to be tree-enabled,
which means that hierarchies are defined upon the segment values for rollup purposes. In such scenarios, you must filter by
a specific hierarchy when performing ad hoc queries against tree-based accounting segments. Incorrect results may occur
if tree filters are not applied. To apply tree filters, create a filter condition on Tree Filter attributes in Accounting Segment
Dimensions.
Note: For information, see: Administering Transactional Analyses at http://docs.oracle.com/cloud/latest/

common/OATBI/toc.htm.
Managing Financial Reporting Studio Versions: Explained

You could run into issues with Financial Reporting Studio reports if the Financial Reporting Studio version on your client is
different from the Financial Reporting server version in the application. You must therefore manage the Financial Reporting
Studio client version during the course of the regular Oracle Fusion Applications Cloud updates.
Using Financial Reporting Studio Between Test and Production Updates

Your test environment is always updated before your production environment.
During this period, the version of the Financial Reporting server on your test environment may be different than the version
on your production environment. When this happens, the existing Financial Reporting Studio client currently installed on your
computer may not work with your test environment due to the version mismatch between its server and client. Thus, during
this period, you must uninstall and reinstall the Financial Reporting Studio client from the test or production environment
accordingly, depending on which environment you work on, to ensure the client version matches the server version.
467
Using Financial Reporting Studio After the Production Update

After the production environment is updated, the Financial Reporting Studio versions for the test and production
environments will be the same.
If you already installed Financial Reporting Studio from the test environment, you won't have to make any changes.
Otherwise, you should immediately uninstall, download, and reinstall Financial Reporting Studio from the financial reporting
workspace in the production environment.
Comparing the Client and Server Versions

To compare the Financial Reporting Studio client version with the Financial Reporting server version, perform the following
steps:
1. Launch Financial Reporting Studio.

2. From the Help menu, select About Reporting Studio.
3. Compare the Oracle Hyperion Financial Reporting version with the Report Server Version to confirm that they
match.
468
The following figure shows an example of matching client and server versions. The Oracle Hyperion Financial Reporting
version is 11.1.2.4.505 and the Report Server Version is 11.1.2.4.560.0505.
You can also check the server version from the Help menu of the financial reporting workspace.
1. From the Financial Reporting Center, select the Open Workspace for Financial Reports task.
2. From the Help menu, select About Oracle Enterprise Performance Management System Workspace.
3. Click Show Details.
The following figure shows an example of the report server version from the financial reporting workspace.
469
Installing Financial Reporting Studio

Perform the following prerequisite steps:
1. Uninstall the previous version, if any, using the Windows Control Panel.
2. Delete the existing directory structure. For example, C:\Oracle\Middleware\EPMSystem11R1\products
\FinancialReportingStudio.
3. Restart your computer.
Download the version of the Financial Reporting Studio from that environment's workspace:
1. Navigate to the Financial Reporting Center and select the Open the Financial Reporting Workspace task.
2. From the menu, select Tools > Install > Financial Reporting Studio and save the file.
3. Right-click the executable file and select Run as administrator.
Caution: Don't close the following command window that appears near completion. It will
automatically close itself.
470
4. Click Finish on the install window after the command window closes.
Lastly, when designing reports, you can't design a Financial Reporting Studio report using a client version that's higher than
the report server version, and then export or import the report to a lower client version level. The report may not work.
Create Financial Statements: Explained

In Oracle Hyperion Financial Reporting Studio, you can 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
471
include text and graphics. Use Financial Reporting Studio, a client-based application launched from your desktop, to create
your reports. Perform the following basic tasks to begin defining this report.
1. Open Financial Reporting Studio on your desktop.
Tip: The first time you sign in, you must set the Server URL in this format: https://<servername>-bi-
ext.us.oracle.com:port.
2. Click the New Report icon on the toolbar, or from the File menu, select New > Report. Use the Report Pallet
page as the container to build your report.
3. Click the New Grid icon on the toolbar.
472
4. Click and drag to select a large area of the grid in which to create your report.
5. On the Select a Database Connection window, click the Database Connection list.
6. Select your database. A unique cube exists for each combination of chart of accounts and accounting calendar.
7. Click OK.
Tip: Best practice is to always turn suppression on in financial reports. This should be done at the Database
Connection Server. You can verify this by doing the following: (highlight the grid > Menu > Task > Data Query
Optimization Settings). The normal best practice for most reports is to turn suppression on for the entire
grid, and then turn it off for certain columns and rows that must always display. For more information about
suppression settings, see Using the Basic Option in Conditional Suppression in the Designing with Financial
Reporting Studio for Oracle Planning and Budgeting Cloud guide at http://docs.oracle.com/cloud/latest/epm-
common/CSFSU/ch09s04s02.html#BEGIN.
Set the Row, Column, and Page Points of View

Set the point of view dimensions and accounts for the rows, columns, and page levels.
1. Use the Dimension Layout window to arrange your dimensions.

2. Click and drag the:
Accounting Period dimension to the Columns section.
Account dimension to the Rows section.
473
Company dimension to the Pages section.
3. Click OK. The Dimension Layout window closes.

4. To select the data to use in your report, double-click the Account cell on the grid to open the Select Members
window.
5. In the Selected section of the window, click the default Account member.
6. Click the Remove icon to move the Account member out of the Selected section.
7. In the Available section of the window, click the Expand icon on the Account node.
8. Continue to expand that node selecting:
Accounts
[Account]@[T]
95001
9. Select the 95011 revenue member.
474
10. Click the Add icon to move the revenue member to the Selected section.
11. Click OK. The Select Members window closes.

12. From the File menu, select Save As.
13. Select My Folders.
14. Enter the report name of XXInFusion Income Statement.
15. Click Save.
16. Right-click the row header for the last row in the grid, which is the row with revenue account 95011.
17. From the Insert Row menu, select Text to add a blank row.
18. Right-click the row header on the new blank row.
19. From the Insert Row menu, select Data to add a row for expenses. The default value for the new row contains
revenue account 95011.
20. Add expense accounts by double-clicking default account 95011 on row 3.
21. Click the Remove All icon to move default account 95011 out of the Selected section.
22. In the Available section, expand Accounts - V1, [Account]@[T], 95001, 95021.
23. Select accounts: 50000, 60000, and 70000.
24. Click Add to move the accounts to the Selected section.
475
25. Select the Place selections into separate rows option.
26. Click OK.

27. Click Save in the toolbar and leave the report open for the next activity.
Add a Formula
Add a formula to calculate total expenses.
1. Right-click the row header for the row after row 5.

2. From the Insert Row menu, select Formula.
3. Click in the blank cell on row 6.
4. Click the Custom Heading option in the properties pane and enter the heading of Total Expenses.
5. Click the row header for the formula row.
6. Click the Sum() button. The formula Sum() is entered into the Edit box.
7. Enter these cell references into the formula: [3], [4], [5].
476
8. Validate the formula syntax by clicking the check mark icon in the toolbar.
9. Click Save and leave the report open for the next activity.
Define Columns Using a Range Function

To create 12 rolling period columns for the report, define columns using the range function.
1. Double-click the Accounting Period cell on the first column in the grid.
2. On the Select Members window, click the Remove All icon to remove the default accounting period from the
Selected section.
3. Click the AccountingPeriod in the Selected window.
4. Click the Functions tab.
5. Click the Range list item.
6. Click Add to move the Range function to the Selected section.
477
7. Click OK.
8. Use the Edit Range Function window to add the range function start and end members or to select a hierarchy to
use to select your report data.
9. Select the StartMember row.
10. Click in the Value field.
11. Select Lookup > Functions.
12. Click the RelativeMember list item.
13. Add.
14. Select the Member row.
15. Click in the Value field > Lookup
16. Click the Current Point of View list item.
17. Add > OK.
18. The Offset value determines periods to include from the current point of view. Since this is a rolling 12-month report,
enter -12.
19. OK twice.
20. Click the EndMember list item > Lookup
21. Click the Current Point of View list item.
22. Add.
23. OK three times until you return to your report.
24. Save. Leave the report open for the next activity.
Define User Points of View

Define the user points of view for the dimensions and specify values for those dimensions.
1. Select the Grid object.
2. Right-click the Grid object.
3. Grid Point of View. The points of view appear on the Select Members window.
4. Ledger: User Point of View for Ledger.
478
5. Expand:
Ledger
All Ledgers
6. Highlight the Ledger item to include in the report: InFusion USA PL.
7. Select Scenario.
8. Expand Scenario.
9. Select Actual as the Scenario member to determine what should be included in the columns.
10. Select Balance Amount.
11. Expand the Balance Amount.
12. Select Period Activity as the balance amount to include in the report.
13. Select Currency.
14. Expand Currency.
15. Search for and select USD from the list.
16. Click the USD list item.
479
17. OK.
18. Right-click the Grid object.

19. Click the Grid Point of View Setup.
20. Scroll down and click the Balance Amount list button.
21. Select the Nothing, Lock Member Selection option.
22. OK.
23. Double-click the Pages object.
24. Remove.
25. Select the Prompt for Company list item.
480
26. Add.
27. OK.
28. Select Lookup.
29. Click the Default Member list icon.
30. Remove.
31. Expand.
Company.
All Company Values.

32. Select the required companies: 101 - US 1 LE 1 BU 1 and 102 - US 1 LE 2 BU 2.
33. Add.
34. OK.
35. Click the Member Labels in Prompt Selection Dialog list button.
481
36. Select the Alias list item.
37. OK.
38. Open the Page Properties dialog box. If it does not open, click View menu > Property Sheet.
39. Double-click the Pages object.
482
40. Click the Alias: Default option.
41. Click the first cell in Row 1.

42. Open the Heading Row Properties dialog box.
483
43. Click the Alias: Default option.
44. Click the Grid object.

45. Open the Grid Properties dialog box.
46. Click the Suppression list item.
484
47. Enter 0 in the Zero Values field.
48. Open the Heading Row Properties dialog box.

49. Click an entry in the row.
50. Click the Allow Expansion option.
51. Click the Grid object.
52. Open the Grid Properties dialog box.
53. Click the Drill Through option.
54. Save. Leave the report open for the next activity.
Add Company Logo and Title

Insert your company's logo and add a title to the report.
1. Click Image. (Third icon in the second set of icons on the toolbar.)
2. Find your company's logo in your file system.
3. Click Open.
4. Drag and drop the cursor over the report pallet to determine the length and width of the image.
5. Save.
6. Click Text. (Second icon in the second set of icons on the toolbar).
7. Drag and drop the cursor over the report pallet to determine the length and width of the title.
8. Enter Rolling 12 Month Income Statement.
485
9. Format > Font.

10. Select Bold and 14 as the Font Size.
11. Center Text.
12. File > Page Setup option.
13. Click Landscape.
14. Click Workspace Size. If needed, you can adjust the Width and Height with the up and down arrows.
15. OK > Save.
Preview Report
Preview the report both in the Financial Reporting Studio and the Financial Reporting Center.
In Financial Reporting Studio
1. File > Print Preview.

2. Accept the default selections.
486
3. OK.
4. Use the Next Page to see all the columns.

5. Edit the report definition as needed.
In Financial Reporting Center
1. Sign in the Oracle Fusion Applications.

2. Navigator > General Accounting: Financial Reporting Center > My Folders > XXInFusion Income
Statement.
3. View as HTML.
4. OK to the Respond to Prompts window to keep the default companies.
487
5. Click the AccountingPeriod.
6. Expand:
a. AccountingPeriod
b. 2012
488
c. Qtr2-12
7. Select 02-12.
489
8. OK.
Related Topics
Designing with Financial Reporting Studio for Oracle Planning and Budgeting Cloud
Configuring an Account Group: Example

Configuration of an account group enables you to create self-monitoring accounts that help you eliminate the surprise of
account anomalies during your close process.
Scenario
You have been given the task to set up account groups. Follow these steps to define account groups that track key account
balances by purpose, category, and comparison criteria.
1. Navigate to the General Accounting Dashboard page.
2. Select View > Account Group > Create. Other options include:
Edit to change an existing account group.

Manage to create, edit, or delete account groups. In the Manage Account Group you can enable sharing of
account groups with other users.
3. Enter the account group name and description. The name is used by default on the infolet, but can be changed
using the Actions menu on the infolet.
4. Select the Display In option to determine if the account group is displayed in an infolet or the Account Monitor only.
Select one:
Account Monitor
490
Allocations
Expenses
Revenues
Note: The last three Display In choices are for the specific infolets. The account group settings
must be defined to be consistent with the particular infolets targeted to track revenues, expenses, or
allocations pools. In the Account Monitor, you can also select one of the infolet account groups to
display in the Account Monitor. Any account group regardless of Display In setting can be displayed in
the Financial Reporting Center.
5. Select the Set as default check box if the account group is used as the default account in the infolet or Account
Monitor. The setting of a default for each display target is specific to the user. The setting gives the user a unique
default view of account groups in various display targets.
6. You can set four locations to project the account group results. The projected locations are the Account Monitor and
the three General Ledger Infolets. You can set a specific default account group for each of the projected locations.
7. Click Dynamically derive ledger to enable the application to apply the account group to any ledger in the same
balances cube. The ledger derived is based on your data access set and ledger selection.
Note: If you don't select this option, enter a ledger on each account row.
8. Select a Time Option and Comparison Option as shown in the following table.
Time Option Comparison Option
Accounting Period

Budget PTD
Budget QTD
Budget YTD
Prior period PTD
Prior year PTD
Prior year QTD
Prior year YTD
Quarter

Budget QTD
Budget YTD
Prior quarter QTD
Prior year QTD
Prior year YTD
Year

Budget YTD
Prior year YTD
Tip: If you are using a budget comparison option, select your budget name for the Scenario.
491
9. Set Access.
Private: For your use only.

Public: For use by all users who have access to the same balance cube of that account group.
Shared: For use by users you specify and have access to the same balance cube of that account group.
Note: To set shared access, navigate to the Manage Account Group page.
10. Enter the accounts you want to monitor in the Accounts section.
a. Give each account group a short name that is easily recognizable in the infolet details. The name displays in
the infolet and in the Name column of the Account Monitor. Account groups that were defined before Release
11 do not have names as this is a new feature. Names can be added by navigating to the Actions menu >
Edit on the Account Monitor region on the General Accounting Dashboard.
b. Optionally enter a ledger.
c. Enter either parent or child values for each segment of the account.
d. Select when to display the account in the Change field.
Always Display
Decrease by Less than Amount
Decrease by Less than Percentage
Decrease by More than Amount
Increase by More than Amount
Increase by Less than Amount
Increase by Less than Percentage
Increase by More than Percentage
Decrease by More than Percentage
Not Equal
Equal
e. Enter Threshold which is the criteria that is being measures against. Threshold is used in conjunction with
the Change selection.
11. Click Save and Close or Save and Create Another.
Migrating Financial Reports: Instructions

This process consists of two tasks:

This process exports only the financial reports under /shared/Custom/Financials. Make sure to copy all the financial reports or
the folders containing them to this folder.
492
To export from the source instance:
1. Copy all the financial reports or the folders containing them to the folder /shared/Custom/Financials.
2. Sign in to the Oracle Fusion Home page of the source environment with Application_Implementation_Consultant.
3. Select Navigator > Setup and Maintenance.
4. Click Manage Implementation Projects in the Tasks pane.
5. Click the Create icon to add a new implementation project.
6. Enter the basic information and click Next.
7. On the Create Implementation Project: Select Offerings to Implement page, verify that the Include check box is
deselected for all the projects.
8. Click Save and Open Project.
9. Click the Select and Add icon to add a task.
10. Select Tasks from the Search list and search on the task called Create Financial Statements.
11. Select Create Financial Statements > Apply. The task is added to the Implementation Project page in the
background.
12. Select Done.
13. Click Done for the implementation project.
14. In the Tasks pane, click Manage Configuration Packages.
15. Click the Create icon to create a new configuration project.
16. Search for your implementation project in the Name field and enter or modify the basic information.
17. Select the option Setup task list and setup data.
18. Click Next > Submit.
19. Answer Yes to the message.
21. Click the Download icon, select Download Configuration Package, and save to a local disk.

This process imports the financial reports under /shared/Custom/Financials.
To import to the target instance:
1. Sign in to the Oracle Fusion Home page of the target environment with Application_Implementation_Consultant.
2. Select Navigator > Setup and Maintenance.
3. Click Manage Configuration Packages.
4. Click Upload to upload the configuration package that was downloaded in the export process.
5. Select Browse to find the file, then click Get Details, and then Submit.
6. In the Export and Import Processes table, click Import Setup Data to import the data.
7. When the Import Setup Data page appears, accept or change defaults as needed.
8. Click Next to navigate through the pages and then Submit.
Note: For the Financial Reporting report definition migration service from a source to target instance, references
to version IDs of dimension members hierarchies are synchronized to their version IDs in the target instance.
493
General Ledger Subject Areas, Folders, and Attributes:

Explained
To create real-time analyses for General Ledger, 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 General Ledger - 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 columns in the journal tables.
General Ledger has four general ledger-specific subject areas:
General Ledger - Balances Real Time

General Ledger - Journals Real Time
General Ledger - Period Status Real Time
General Ledger - Transactional Balances Real Time
Tip: To create a report that queries balances and allows drill down to journals, use the General Ledger -
Transactional Balances Real Time and the General Ledger - Journals Real Time subject areas. Other than that,
it is advised that you do not create reports that cross subject areas. Such reports may result in less than optimal
performance and are hard to maintain.
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 are numeric values like journal debit and credit amounts. Fact folders are usually listed after
dimension 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:
Journal Approval has approval attributes.

Journal Batches has subfolders and attributes under the subfolders.
494
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.
In the preceding figure, the following components are shown:
Subject area: General Ledger - Journals Real Time

Dimension - Presentation Folder: Approval Status
Dimension - Attributes: Approval Status Code, Approval Status Description, and Approval Status Meaning.
Fact - Presentation Folder: Lines
495
Fact - Measures: Accounted Credit, Accounted Debit, Entered Credit, Entered Debit, and Statistical Quantity
Related Topics
Data Structure for Analytics: Explained
Define Transactional Business Intelligence Configuration:

Overview
Use the Define Transactional Business Intelligence task list in the Setup and Maintenance work area to complete configuration
of business intelligence in your application. Some tasks in this task list are performed during Oracle Applications Cloud
provisioning and require no further action from you. The Define Transactional Business Intelligence Configuration task list
includes the following tasks:
Optimize Transactional Business Intelligence Repository
Trim unused projects from the business intelligence repository based on configured Oracle Applications Cloud
offerings. This optimization is automated during the provisioning process and requires no further action from you.
Manage Transactional Business Intelligence Connections
Review data source connections in the physical layer of the business intelligence repository. Connections are set up
and reviewed during the provisioning process, and this task requires no further action from you.
Manage Security for Transactional Business Intelligence
Review security for business intelligence users. The default security configuration can be modified. Refer to the
security documentation for your cloud services to review or change the default user security model.
Configure Key Flexfields for Transactional Business Intelligence
Define the key flexfield segments and validation for use as classification keys. You must define these key flexfields for
Oracle Fusion Transactional Business Intelligence to operate correctly.
Configure Descriptive Flexfields for Transactional Business Intelligence
Define validation and display properties of descriptive flexfields, which are used to add custom attributes to entities.
You enable and import flexfields for use in analyses.
Import Essbase Cubes into Transactional Business Intelligence Repository for Financials General Ledger
Import Essbase cubes into the business intelligence repository. You must perform this task if you're using Oracle
Fusion General Ledger.
Manage User Currency Preferences in Transactional Business Intelligence
Manage user currency preferences, which control regional currency settings, currency used in reports, and
corporate currency.
Related Topics
Essbase Rule File and Cubes: Overview
Configuring Flexfields for Use in Analyses: Overview
496
Configuring Descriptive Flexfields for Transactional Business Intelligence: Overview
Importing Flexfield Changes: Overview
Setting Currency Preferences for Analytics
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 store and edit Financial Reporting objects?

First installed Oracle BI EE as part of Oracle Fusion Applications. Then store and edit new objects that you create for Oracle
Hyperion Financial Reporting in Workspace in the Oracle BI Presentation Catalog. Perform operations on those objects in
the catalog similarly to how you work with other objects, such as copying and modifying properties. See the documentation
for Hyperion Financial Reporting for complete information on working with objects. Financial Reporting report designers can
also access the Financial Reporting objects in the Financial Reporting Studio.
497
498
Oracle Financials Cloud Glossary
Glossary
accounting flexfield
The structure that determines the chart of accounts, including the number and order of the individual segments, as well as
assigning the value sets to the segments.
accounting method
A set of journal entry rules which determine how a subledger journal entry is created for each event class or event type.
accounting period
The fiscal period used to report financial results, such as a calendar month or fiscal period.
application feature
A standardized functionality that is available to implemented.
application identity
Predefined application level user with elevated privileges. An application identity authorizes jobs and transactions for which
other users are not authorized, such as a payroll run authorized to access a taxpayer ID while the user who initiated the job is
not authorized to access such personally identifiable information.
assignment
A set of information, including job, position, pay, compensation, managers, working hours, and work location, that defines a
worker's or nonworker's role in a legal employer.
AutoPost criteria sets

A grouping of options and submission frequencies used to select journal entries for automatic posting.
balances cube
A multidimensional database that holds accounting financial data. The cube allows different views of the balances to be
quickly displayed.
balancing segment
A chart of accounts segment used to automatically balance all journal entries for each value of this segment.
business function
A business process or an activity that can be performed by people working within a business unit. Describes how a business
unit is used.
business unit
A unit of an enterprise that performs one or many business functions that can be rolled up in a management hierarchy.
499
calendar event
A period that signifies an event, such as a public holiday or a training course, that impacts worker availability.
chart of accounts
The account structure your organization uses to record transactions and maintain account balances.
clause adoption
Reusing a clause from the global business unit in local business units either by adopting the clause without change or by
localizing it.
clause localization
A type of clause adoption where the adopted clause is edited to suit the local business unit needs.
clause numbering level

Specifies the determinant type of the document sequence for automatic clause numbering
clearing company
The intercompany clearing entity used to balance the journal.
context
A grouping of flexfield segments to store related information.
context segment
The flexfield segment used to store the context value. Each context value can be associated with a different set of context-
sensitive segments.
context-sensitive segment
A flexfield segment that may or may not appear depending upon a context. Context-sensitive segments are custom attributes
that apply to certain entity rows based on the value of the context segment.
contract deviations
Differences between the contract terms in a contract and those in the contract terms template applied to that contract and
any deviations from company policies as determined by Contract Expert feature rules.
Contract Expert
A feature that lets you create and evaluate business rules in the terms library such that the contract terms meet your business
standards, by suggesting contract changes or additional clauses.
500
Contract Terms Library

A repository of standard clauses, contract terms templates, and business rules built using Contract Expert.
corporate rate type

Rate you define to standardize rates used in conversion of one currency to another over a period of time. This rate is generally
a standard market rate determined by senior financial management for use throughout the organization.
cost center
A unit of activity or a group of employees used to assign costs for accounting purposes.
cost organization
A grouping of inventory organizations that indicates legal and financial ownership of inventory, and which establishes common
costing and accounting policies.
country holding company

A legal entity that acts on behalf of several divisions within an enterprise, and is the legal employer in a country.
cube
A block of data that contains three or more dimensions. An Essbase database is a cube.
department
A division of a business enterprise dealing with a particular area of activity.
descriptive flexfield
Customizable expansion space, such as fields used to capture additional descriptive information or attributes about an entity,
such as a customer case. You may configure information collection and storage based on the context.
determinant
A value that specifies the use of a reference data set in a particular business context.
determinant type
An optional value that affects document sequencing in a transaction. The available determinant types are Business Unit,
Ledger, Legal Entity, and Tax Registration.
determinant type
The value that affects sharing of reference data in a transaction across organizations, such as a business unit or a cost
organization.
determinant value
A value specific to the selected determinant type of a document sequence. If Ledger is the determinant type for a document
sequence, the determinant value is the specific ledger number whose documents are numbered by the document sequence.
It is relevant in a document sequence assignment only if the document sequence has a determinant type.
501
division
A business-oriented subdivision within an enterprise. Each division is organized to deliver products and services or address
different markets.
document sequence
A unique number that is automatically or manually assigned to a created and saved document.
enterprise
An organization with one or more legal entities under common control.
fixed rate type

Rate you set between two currencies that remains constant. For example, a rate set between the euro currency and each
Economic and Monetary Union (EMU) currency during the conversion to the euro currency.
flexfield
A flexible data field that you can customize to contain one or more segments or store additional information. Each segment
has a value and a meaning.
flexfield segment
An extensible data field that represents an attribute and captures a value corresponding to a predefined, single extension
column in the database. A segment appears globally or based on a context of other captured information.
grade
A component of the employment model that defines the level of compensation for a worker.
inventory organization
A logical or physical entity in the enterprise that tracks inventory transactions and balances, stores definitions of items, and
manufactures or distributes products.
item master
A collection of data that describes items and their attributes recorded in a database file.
item organization
Item definition where inventory balances are not stored and movement of inventory is not tracked in the applications. Item
attributes that carry financial and accounting information are hidden.
item subinventory
An association of an item with a subinventory that is created when you add an item to a subinventory.
job
A generic role that is independent of any single department or location. For example, the jobs Manager and Consultant can
occur in many departments.
502
journal
An element of a journal entry consisting of the name, accounting date, category, ledger, and currency for single currency
journal entries. Used to group journal lines.
journal batch
An element of a journal entry consisting of the name, source, and accounting period. Used to group journals for processing
and easier querying.
key flexfield
Configurable flexfield comprising multiple parts or segments, each of which has a meaning either individually or in combination
with other segments. Examples of key flexfields are part numbers, asset category, and accounts in the chart of accounts.
key flexfield segment instance

A single occurrence of a key flexfield segment in a key flexfield structure instance.
key flexfield structure

The arrangement of segments in a key flexfield. In some cases, you can define multiple structures for a single key flexfield.
key flexfield structure instance

An occurrence of a key flexfield structure that shares the same order of segments as other instances of the key flexfield
structure. However, each instance uses different value sets to validate the segments.
legal authority
A government or legal body that is charged with powers such as the power to make laws, levy and collect fees and taxes,
and remit financial appropriations for a given jurisdiction.
legal employer
A legal entity that employs people.
legal entity
An entity identified and given rights and responsibilities under commercial law through the registration with country's
appropriate authority.
legal jurisdiction
A physical territory, such as a group of countries, single country, state, county, parish, or city, which comes under the purview
of a legal authority.
legal reporting unit

The lowest level component of a legal structure that requires registrations. Used to group workers for the purpose of tax and
social insurance reporting or represent a part of your enterprise with a specific statutory or tax reporting obligation.
503
legislative data group

A means of partitioning payroll and related data. At least one legislative data group is required for each country where the
enterprise operates. Each legislative data group is associated with one or more payroll statutory units.
line of business
Set of one or more highly related products which service a particular customer transaction or business need. Refers to an
internal corporate business unit.
lookup code
An option available within a lookup type, such as the lookup code BLUE within the lookup type COLORS.
lookup type
The label for a static list that has lookup codes as its values.
mainline metadata
The primary branch of metadata that a sandbox is published to. Once published, changes made in the sandbox become
available to all users.
manufacturing facilities
Employed in the making of goods for sale such as a factory or plant.
model profile
A collection of the work requirements and required skills and qualifications of a workforce structure, such as a job or position.
natural account
Categorizes account segment values by account type, asset, liability, expense, revenue, or equity, and sets posting,
budgeting, and other options.
natural account segment

A chart of accounts segment used to categorize your accounting transactions by account type: asset, liability, owner's equity,
revenue, or expense.
offering
A comprehensive grouping of business functions, such as Sales or Product Management, that is delivered as a unit to
support one or more business processes.
party fiscal classification

A classification used by a tax authority to categorize a party for a tax.
payroll statutory unit

A legal entity registered to report payroll tax and social insurance. A legal employer can also be a payroll statutory unit, but a
payroll statutory unit can represent multiple legal employers.
504
position
A specific occurrence of one job that is fixed within one department. It is also often restricted to one location. For example,
the position Finance Manager is an instance of the job Manager in the Finance Department.
primary balancing segment value

A segment value used to represent a legal entity in the chart of accounts and automatically balance all intercompany and
intracompany transactions and journal entries.
primary ledger
Main record-keeping ledger.
profile option
User preferences and system configuration options that users can configure to control application behavior at different levels
of an enterprise.
project expenditure organization

An organization that can incur expenditures and hold financial plans for projects.
Query By Example
The row of fields directly above table column headers, used for filtering the data in the table.
reference data
Data in application tables that is not transactional or high-volume, which an enterprise can share across multiple
organizations. For example, sales methods, transaction types, or payment terms.
reference data set

Contains reference data that can be shared across a number of business units or other determinant types. A set supports
common administration of that reference data.
reference group
A logical collection of reference data sets that correspond to logical entities, such as payment terms defined across multiple
tables or views. Based on the common partitioning requirements across entities, the reference data sets are grouped to
facilitate data sharing among them.
registration
The record of a party's identity related details with the appropriate government or legal authorities for the purpose of claiming
and ensuring legal and or commercial rights and responsibilities.
sandbox
A testing environment that isolates untested code changes from the mainline environment so that these changes don't affect
the mainline metadata or other sandboxes.
505
service provider model

A business unit that provides specific business functions for another business unit.
set
Classified and grouped reference data that organizational entities share.
set enabled
A property that describes entities that an organization shares as reference data. For example, you can indicate a lookup,
customer, location, or document attachment as set enabled.
spot rate type

Rate you enter to perform conversion based on this rate as of a specific date. This rate applies to the immediate delivery of a
currency.
storage facilities
Commercial building for storage of goods such as a warehouse.
subject area
A set of columns, or pieces of data, related to a specific business object or area.
tax registration
The registration of a party with a tax authority that confers tax rights and imposes certain tax obligations.
territory
A legally distinct region used in the country field of an address.
tree
Information or data organized into a hierarchy with one or more root nodes connected to branches of nodes. A tree must
have a structure where each node corresponds to data from one or more data sources.
tree structure
A set of guidelines or a framework applied to create a tree, include data, version a tree, or access a tree.
tree version
An instance of a tree that includes life cycle elements such as start and end dates, and indicates whether the tree is active. If
a tree is associated with a reference data set, all tree versions belong to one set.
506
user rate type

Rate you enter at journal entry time to convert foreign currency transactions to your ledger currency.
value set
A predefined set to validate the values that a user enters in the application. The set may be hierarchical.
work relationship
An association between a person and a legal employer, where the worker type determines whether the relationship is a
nonworker, contingent worker, or employee work relationship.
workflow
An automated process that passes a task from one user (or group of users) to another to view or act on. The task is routed in
a logical sequence to achieve an end result.
507
508

Cloud General Ledger Book PDF

Enviado por

Dados do documento

Título original

Direitos autorais

Formatos disponíveis

Compartilhar este documento

Compartilhar ou incorporar documento

Opções de compartilhamento

Você considera este documento útil?

Este conteúdo é inapropriado?

Direitos autorais:

Formatos disponíveis

Cloud General Ledger Book PDF

Enviado por

Direitos autorais:

Formatos disponíveis

Oracle

Release 13 (update 17B)

Release 13 (update 17B)

Authors: Kathryn Wohnoutka, Barbara Kostelec

1 Enterprise Structures Introduction 1

2 Reference Data Sharing 29

8 Intercompany Setup 259

9 General Ledger Options 297

10 Period Close 337

11 Business Units 405

12 Workforce Structures and Facilities 423

13 Hyperion Financial Management Integration 449

14 Budget Configuration 451

15 Financial Reporting 461

Oracle Applications Help

Using Applications Help

Training: Take courses on Oracle Cloud from Oracle University .

Access to Oracle Support

Comments and Suggestions

1 Enterprise Structures Introduction

Enterprise Structures: Overview

Aligned these structures with your strategic objectives.

A distinct legal entity from its owners and managers.

In the figure above:

A separate card represents a series of registered companies.

Enterprise Structures Business Process Model: Explained

Business Process Model (BPM)

Define Enterprise Structures

Define Legal Entities

Set Up Enterprise Define Business Units

Define Chart of Accounts

Define Accounting Configurations

The table describes each BPM activity.

BPM Activities Description

BPM Activities Description

Global Enterprise Configuration: Points to Consider

Business Unit Management

Modeling Your Enterprise Management Structure in Oracle

Global Enterprise Structure Model

InFusion America Inc.

InFusion United States InFusion United Kingdom

US Warehouse US Warehouse UK Warehouse

Running Diagnostic Tests for Enterprise Structures Setup

Use the following steps:

Enterprise Structures Setup Report: Explained

Setup Data Import and Export for Oracle Fusion Financials:

Setup Tasks Performed Before Export

Activity Name Task Name Setup Steps

Activity Name Task Name Setup Steps

Setup Tasks Performed Before Import

Activity Name Task Name Setup Steps

Setup Tasks Performed After Import

Activity Name Task Name

Define General Ledger Options Manage Journal Approval Rules

Define Approval Management for Manage Task Configurations for Financials

Define Tax Geographies Manage Tax Geographies

Define Payables Define Automated Invoice Processing Configuration

Define Image Processing Configure Document Capture Parameters

Define Customer Billing Configuration Manage Salesperson Account References

Define Customer Payments Manage Receivables Specialist Assignment Rules

Activity Name Task Name Setup Steps

Define Customer Manage Customers Manually maintain customer information

Configure Payment System Connectivity Manage BI Publisher Templates