Oracle Fusion Financials Student Guide Part1

Oracle Financials Cloud:
Financials Implementation for R11
Student Guide - Volume I

D000PTGC10
Edition 1.0 | June 2016
Learn more from Oracle University at oracle.com/education/
Author Copyright © 2016, Oracle and/or its affiliates. All rights reserved.
Disclaimer
Kathryn Wohnoutka
This document contains proprietary information and is protected by copyright and
Publisher other intellectual property laws. You may copy and print this document solely for your
own use in an Oracle training course. The document may not be modified or altered
Sumesh Koshy in any way. Except where your use constitutes "fair use" under copyright law, you
may not use, share, download, upload, copy, print, display, perform, reproduce,
publish, license, post, transmit, or distribute this document in whole or in part without
the express authorization of Oracle.
The information contained in this document is subject to change without notice. If you
find any problems in the document, please report them in writing to: Oracle University,
500 Oracle Parkway, Redwood Shores, California 94065 USA. This document is not
warranted to be error-free.
Restricted Rights Notice
If this documentation is delivered to the United States Government or anyone using

the documentation on behalf of the United States Government, the following notice is
applicable:
U.S. GOVERNMENT RIGHTS

The U.S. Government’s rights to use, modify, reproduce, release, perform, display, or
disclose these training materials are restricted by the terms of the applicable Oracle
license agreement and/or the applicable U.S. Government contract.
Trademark Notice
Oracle and Java are registered trademarks of Oracle and/or its affiliates. Other names
may be trademarks of their respective owners.
Contents
1 Introduction to Oracle Financials Cloud Implementation

Course Objectives 1-2
Course Approach 1-3
Oracle Fusion Implementation Resources 1-4
Oracle Help Center: docs.oracle.com 1-5
Oracle Cloud Application Service Pages 1-6
Video Subject Areas on the Oracle Help Center 1-7
New Reference Guides 1-8
Friendly Search 1-10
Lesson Objectives 1-11
Introduction to Oracle Fusion Applications 1-12
Oracle Financials Cloud: Overview 1-13
Financials Cloud: Key Features 1-14
Implementation Discussion 1-15
Common Applications Configurations: Overview 1-16
Common Application Discussion 1-17
Summary 1-19
2 Introducing Oracle Fusion Navigation

Objectives 2-2
Getting Started in Oracle Fusion Applications 2-3
Simplified Navigation 2-4
New Welcome Springboard 2-5
Favorite and Recent Items 2-6
User Interface 2-7
Dashboards 2-8
General Accounting Dashboard 2-9
Work Areas 2-10
Panel 2-11
Search Panel Overview 2-12
Reports and Analytics Panel 2-13
Practice 2-1 Overview: Getting Started in Oracle Fusion Applications 2-14
Infolets versus Infotiles 2-15
Infolets Overview 2-16
Infolet Repository 2-17
iii
Subledger Infotiles Overview 2-18
Practice 2-2 Overview: Exploring Infolets and Infotiles 2-19
Summary 2-20
3 Introducing Functional Setup Manager

Objectives 3-2
Overview of Functional Setup Manager 3-3
Job Roles 3-4
Implementation Objects Overview 3-5
Setup Objects 3-6
Business Objects 3-7
Offerings 3-8
Offerings, Functional Areas, and Features 3-9
Offerings, Functional Areas, and Features: Example 3-10
Offerings 3-11
About Financials: Overview 3-12
Practice 3-1 Overview: Browsing Offerings 3-14
Configuring Offerings 3-15
Demonstration 3-2 Overview: Configuring Offerings 3-16
Implementation Task Flow 3-17
Implementation Project: Overview 3-18
Assign Tasks 3-19
Rapid Implementation Task List 3-20
Financials Task Lists 3-21
Practice 3-3 Overview: Creating an Implementation Project 3-22
Implementation Project for Ongoing Maintenance 3-23
Setup Data Export and Import: Overview 3-24
Offering Based Export 3-25
Offering Based Import 3-26
Offering Based Export and Import Process 3-27
Additional Information on Oracle Help Center 3-28
Summary 3-29
4 Overview of Security
Objectives 4-2
Oracle Financial Cloud Security Methodology 4-3
Security Reference Implementation 4-4
Points to Consider When Implementing the First Project 4-5
Function and Data Security 4-7
New Data Security for R11 4-8
Assigning Data Scopes to Users for New Customers Only 4-9
iv
Types of Roles 4-10
Role Inheritance 4-11
Security Example with Data Role Added 4-12
Oracle Identity Manager 4-13
Creating Users 4-14
Role Provisioning Tasks 4-15
Using Role Mappings 4-16
Practice 4-1 to 4-3 Overview: Using User Security 4-17
Customizing Roles 4-18
The Security Console 4-19
The Security Console: Copy Feature 4-20
The Security Console: Compare Roles Feature 4-21
Additional Features 4-22
Practice 4-4 Overview: Using the Security Console 4-23
Auditing Security 4-24
Security Resources 4-26
Summary 4-27
5 Discussing the Vision Story and Common Applications

Objectives 5-2
Overview 5-3
Scenario 5-4
Scenario Details 5-5
Vision Corporation Analysis 5-6
Vision Corporation Structure Diagram 5-8
Vision Corporation Enterprise Structure 5-10
Vision Corporation Business Unit and Department Structure 5-11
Vision Corporation Distribution Structure 5-12
Vision Corporation Chart of Accounts Summary 5-13
Define Geographies 5-14
Geographies: Overview 5-15
Geography Structure 5-16
Geography Hierarchy 5-17
Geography Hierarchy Example 5-18
Geography Validations 5-19
Manage Geography Validations 5-20
Address Cleansing 5-21
Geocoding Process 5-22
Importing Geography Options 5-23
Nokia Geography Reference Data Import 5-24
File-Based Import 5-25
v
Managing Geography Lookups 5-26
Tax Zone Types and Zones 5-27
Run Maintain Geography Name Referencing Process 5-28
Quiz 5-29
Summary 5-33
6 Configuring Enterprise Structures

Objectives 6-2
Define Enterprise Structures 6-3
Sharing Ledger Components Across Oracle Applications 6-4
Practice 6-1 Overview: Reviewing Shared Components 6-5
Plan Your Implementation Requirements 6-6
Implementation Simplification 6-7
Rapid Implementation: Overview 6-8
Rapid Implementation Task List 6-9
Rapid Implementation Process 6-10
Chart of Accounts Components 6-11
What Is a Value Set? 6-13
Assigning Segment Labels 6-14
Balancing Segment Labels 6-15
Cost Center Segment Labels 6-16
Other Segment Labels 6-17
Defining Hierarchies: Overview 6-18
Manage Business Units 6-19
Rapid Implementation Workbook 6-20
GL Rapid Implementation Additional Features 6-21
Cross-Validation Rules and Segment Value Security Rules 6-22
Account Combinations 6-23
Account Defaulting 6-24
Country-Specific Document and Journal Sequencing 6-25
Rapid Implementation Spreadsheets 6-26
Completing the Accounting Configuration 6-28
Practice 6-2 Overview: Entering Data in the Rapid Implementation Spreadsheet 6-
30
Completing the Accounting Configuration 6-31
Practice 6-3 to 6-5 Overview: Completing the Rapid Implementation Process 6-33
Other Spreadsheet Uses 6-34
Enterprise Structures Setup Report 6-35
Diagnostic Tests for Enterprise Structures Setup Data 6-36
Define Legal Jurisdictions and Authorities 6-37
Legal Jurisdictions: Overview 6-38
vi
Legal Authorities Overview 6-39
Practice 6-6 to 6-8 Overview: Reviewing a Legal Jurisdictions and Authorities 6-40
Manage Legal Entities 6-41
Legal Entities Definition 6-42
The Role of Your Legal Entity 6-43
Legal Entities in Transactions 6-44
Legal Entity and Business Units 6-45
Legal Entity and Divisions 6-46
Legal Entity and Ledgers 6-47
Legal Entity and Balancing Segments 6-48
Legal Entities and Intercompany Transactions 6-50
Legal Entity and Its Relationship to Intercompany Transactions 6-51
Legal Entity and Consolidation Rules 6-52
Country-Specific Legal Entity Sequences 6-53
Practice 6-9 Overview: Searching for Your Legal Entity 6-54
Manage Legal Reporting Units 6-55
Legal Reporting Units Points to Consider 6-56
Practice 6-10 Overview: Viewing a Legal Reporting Unit 6-57
Summary 6-58
7 Configuring General Ledger Components

Objectives 7-2
Financials Task Lists 7-3
Accounting Configuration Prerequisites 7-4
Creating Chart of Accounts Considerations 7-5
Define Value Sets 7-6
Validation and Value Sets 7-8
Practice 7-1 Overview: Searching for and Reviewing Your Value Sets 7-9
Building the Chart of Accounts Structure 7-10
Chart of Accounts Structure Attributes 7-11
Building the Chart of Accounts Restrictions 7-12
Chart of Accounts Instance 7-13
Account Shorthand Alias 7-14
Practice 7-2, 7-3, and 7-4 Overview: Searching for and Deploying Your Chart of
Accounts 7-16
Define Segment Values 7-17
Assign Segment Attributes 7-18
Control Accounts Benefits 7-20
Control Accounts Explained 7-21
Practice 7-5 Overview: Entering Values 7-22
Defining Hierarchies 7-23
vii
Account Hierarchy Purposes 7-24
Account Hierarchy Example 7-25
Create Account Hierarchies 7-26
Create Account Hierarchies Version 7-27
View Account Hierarchies 7-28
Published Account Hierarchy Example 7-29
Single Account Hierarchy 7-30
Published Account Hierarchy V2 Example 7-31
Troubleshooting 7-32
Practice 7-6 and 7-7 Overview: Searching, Completing, and Publishing Your
Accounting Hierarchy 7-34
Enabling Account Combinations 7-35
Practice 7-8 Overview: Creating an Account Combination 7-36
Manage Segment Value Attributes 7-37
Segment Value Security 7-38
Defining Segment Value Security Rules 7-39
General Points About Segment Value Security 7-40
Segment Value Security Examples 7-41
Segment Value Security Operators 7-42
Segment Value Security Rules and Hierarchies Example 7-43
Segment Value Security Rules with Hierarchies 7-44
Changes to an Account Hierarchy Referenced in Segment Value Security Rules 7-
45
Implementation Considerations 7-46
Implementing Segment Value Security 7-47
Segment Value Versus Data Access Set Security 7-48
Cross-Validation Rules 7-50
Cross-Validation Rules Considerations 7-51
Dynamic Combination Creation Allowed 7-52
Filters Overview 7-53
Filters and Conditions 7-54
Practice 7-9 Overview: Defining Cross-Validation Rules in a Spreadsheet 7-55
Manage an Accounting Calendar 7-56
Accounting Calendar Considerations 7-57
Start Date 7-58
Period Frequency 7-59
Period Name Format 7-60
Calendar Type 7-61
Calendars with Different Period Frequencies 7-62
Adding a Calendar Year 7-64
Practice 7-10 Overview: Verifying Your Calendar 7-65
viii
Calendar Auditing 7-66
Manage Currencies Overview 7-67
Currency Concepts 7-68
Currency in Subledgers 7-69
Define Currencies Overview 7-70
Currencies Overview 7-71
Practice 7-11 Overview: Reviewing and Creating Currencies 7-72
Conversion Rate Types: Overview 7-73
Cross-Currency Functionality 7-74
Explain Cross-Rate Rules 7-75
Practice 7-12 Overview: Creating Conversion Rate Types 7-77
Daily Rates: Overview 7-78
Entering Daily Rates 7-79
Practice 7-13 and 7-14 Overview: Using Currency Rates 7-80
Define Ledgers 7-81
Ledgers and Accounting Configurations 7-82
Define Ledger Components 7-84
Ledgers and Subledger Accounting 7-85
Manage Primary Ledgers 7-86
Practice 7-15 Overview: Searching for Your Ledger 7-87
Specify Ledger Options 7-88
Processes Using Ledger Options 7-89
Practice 7-16 Overview: Verifying Your Ledger Options 7-90
Balancing Segment Value Assignments: Overview 7-91
Balancing Segment Value Assignments to Legal Entities 7-92
Balancing Segment Values Assignments to Ledgers 7-93
Balancing Segment Value Assignment Report 7-94
Practice 7-17 Overview: Verifying Legal Entities and Balancing Segments
Assignments 7-95
Manage Reporting Currencies 7-96
Reporting Currencies Conversion Levels 7-98
Practice 7-18 Overview: Defining Reporting Currencies 7-100
Define Secondary Ledgers 7-101
Secondary Ledgers Scenarios 7-102
Secondary Ledgers Conversion Levels 7-103
Secondary Ledger Example 7-104
Secondary Ledger Example Conclusion 7-105
Secondary Ledgers Mapping 7-106
Chart of Accounts Mapping Feature 7-107
Segment Mapping Rules 7-108
Account Mapping Rules 7-109
ix
Review and Submit Accounting Configuration 7-110
Practice 7-19 Overview: Completing the Ledger Configuration 7-111
Balance Cubes: Overview 7-112
Balance Cubes Naming 7-113
Balance Cube Dimensions 7-114
Manage Ledger Sets 7-115
Practice 7-20 Overview: Creating a Ledger Set 7-116
Data Access Set Security Overview 7-117
Data Access Set Security 7-118
Data Access Set Security: Example 7-120
Practices 7-21 and 7-22: Data Access Set Security 7-121
Overview 7-122
Open and Close Periods Life Cycle 7-123
Accounting Period Statuses 7-124
Accounting Periods Overview 7-125
Period Close with Oracle Financials 7-126
Period Close Section 7-127
Period Close Best Practices 7-128
Practice 7-23 Overview: Opening the First Accounting Period 7-129
Period Close Checklist 7-130
Period Close Components 7-131
Allocations Concepts 7-132
Allocation Components 7-133
Defining Allocations Requirements 7-134
Generation of Allocations 7-135
Cross Ledger Intercompany Allocations 7-136
Step Down Allocation Example One 7-137
Step Down Allocation Example Two 7-138
Allocation Rule Concepts 7-139
Allocation Rule Deployment 7-140
Allocations: Best Practices 7-141
Practice 7-24 Overview: Creating and Generating an Allocation Rule 7-142
Revaluation Overview 7-143
Translation Overview 7-144
Revaluation and Translation Concepts 7-145
Revaluation and Translation Setup 7-146
Revaluation Process 7-147
Revaluation Example 7-149
Practice 7-25 Overview: Creating a Revaluation 7-150
Translation Process 7-151
Translation and Remeasurement Solutions 7-152
x
Historical Rates and Amounts 7-153
Import Journal Entries Overview 7-154
Journal Import Verification Process 7-155
Journal Import Validates 7-156
Reconciliation 7-157
Reconciliation Concepts 7-159
Payables Tax Reconciliation with General Ledger Report 7-160
Summary 7-161
8 Configuring Oracle Fusion Intercompany

Objectives 8-2
Intercompany Overview 8-3
Intercompany Balancing Overview 8-4
Example: Payables Invoice 8-5
Example: Cross Ledger Allocation Journals 8-7
Intercompany Balancing Features 8-8
Balancing Setup 8-10
Balancing Rules: Order of Precedence 8-13
Evaluation of Intercompany Balancing Rules 8-14
Manage Intercompany Balancing Rules 8-15
Manage Secondary and Clearing Company Balancing Options 8-18
Key Decisions and Best Practices 8-20
Demonstration 8-1 Overview: Setting Up a New Rule 8-25
Practice 8-2 Overview: Viewing Intercompany Balancing Rules and Secondary and
Clearing Company Balancing Options 8-26
Intercompany Allocation Overview 8-27
Intercompany Allocation Journals 8-28
Intercompany Allocation Transactions 8-29
Intercompany Allocation Requirements 8-30
Key Setup Tasks: Create Allocation Rules 8-31
Example: Intercompany Allocations 8-32
Intercompany Allocations Example 8-38
Oracle Fusion Intercompany Transactions Overview 8-40
Intercompany General Ledger Integration 8-41
Intercompany Receivables and Payables Integration 8-42
Intercompany Transactions Dashboard 8-43
Manual Intercompany Transaction Processing Steps 8-44
Intercompany Transactions Setup 8-45
Manage Intercompany System Options 8-46
Manage Intercompany Transaction Types 8-47
xi
Manage Intercompany Period Status 8-48
Manage Intercompany Organizations 8-49
Map Intercompany Organizations 8-50
Manage Intercompany Organizations 8-52
Define Invoicing Options 8-53
Manage Intercompany Customer and Supplier Assignments 8-54
Manage Intercompany Customer Supplier Assignments 8-55
Manage Intercompany Receivables Assignments 8-56
Define Transaction Accounts for the Intercompany Transactions 8-58
Transaction Account Types 8-59
Intercompany Transactions Approvals 8-60
Example: Intercompany Transactions Approvals 8-61
Manage Intercompany Balancing Rules 8-62
Key Decisions and Best Practices 8-63
Intercompany Reconciliation 8-64
Reconciliation Reports 8-65
Intercompany Reporting and Analysis 8-66
Practice 8-3 Overview: Creating an Intercompany Batch 8-67
Practice 8-4 Overview: Submitting and Reviewing Reconciliation Reports 8-68
Additional References on My Oracle Support https://support.oracle.com 8-69
Summary 8-70
9 Configuring Financial Reporting

Objectives 9-2
The New Financial Reporting Center Overview 9-3
Other Reporting Tools Overview 9-5
Access to the Financial Reporting Center 9-7
Viewing Financial Reports from the Financial Reporting Center 9-8
Live Reports and Published Snapshot Reports 9-9
Practice 9-1 Overview: Using the New Financial Reporting Center 9-10
Oracle Fusion General Ledger Balances Cube Overview 9-11
Dimension Values in Reporting 9-12
GL Balances Cube: Dimensions 9-13
GL Balances Cube: Default Values 9-15
Dimension Values and Defaults 9-16
Smart View Overview 9-19
Smart View: Ad Hoc Analysis 9-21
Smart View: Query Designer 9-22
Creating Financial Reports 9-23
Financial Reporting Studio Overview 9-24
Installing and Configuring the Financial Reporting Studio 9-25
xii
Report Designer 9-26
Report Designer’s Standard Toolbar 9-27
Financial Reporting Studio Components 9-28
Designer Toolbar 9-30
Grids 9-31
Practice 9-2 Overview: Creating a Report with the Financial Reporting Studio:
Defining a Grid 9-33
Defining Formulas 9-34
Available Formulas 9-35
Practice 10-3 Overview: Creating a Financial Report: Adding a Formula for Total
Expenses 9-36
Using Functions: Range 9-37
Practice 9-4 Overview: Creating a Financial Report: Defining a Rolling 12-Period
Column 9-39
User and Grid Point of View Dimensions 9-40
Selecting Members 9-42
Practice 10-5 Overview: Creating a Financial Report: Defining the Grid and User
Point of View Dimensions 9-43
Property Sheet 9-44
Property Sheet Component Objects and Features 9-45
Practice 9-6 Overview: Creating a Financial Report: Setting Properties 9-46
Text Box Objects 9-47
Image Objects 9-48
Practice 9-7 Overview: Creating a Financial Report: Adding a Logo and Title 9-49
Reviewing a Report 9-50
Practice 9-8 Overview: Reviewing a Report 9-51
Infolets Overview 9-52
Infolet Repository 9-53
General Accounting Infolets 9-54
Budgetary Control Infolets 9-58
Budget Consumed Infolet 9-59
Funds Available Infolet 9-60
Custom Infolets Overview 9-61
Practice 9-9 Overview: Using Infolets Demonstration 9-62
Account Groups Overview 9-63
Viewing Account Groups in the General Accounting Infolets 9-64
Defining Account Groups: Header Region 9-65
Defining Account Groups: Accounts Region 9-67
Practice 9-10 Overview: Setting up the General Accounting Expense Infolet 9-68
Viewing Account Groups from the Financial Reporting Center 9-69
Sunburst Tool 9-70
xiii
Sunburst Icons 9-71
Sunburst Options 9-72
Practice 9-11 Overview: Viewing an Account Group from the Financial Reporting
Center Demonstration 9-73
Oracle Transactional Business Intelligence Overview 9-74
Oracle BI Publisher Overview 9-76
Oracle Business Intelligence Publisher: Overview 9-77
Financial Reporting Center and Oracle BI Publisher 9-79
Summary 9-80
10 Configuring Business Units and Reference Data Sets

Objectives 10-2
Common Applications Configuration for Financials 10-3
Business Units Overview 10-4
Business Unit Structure: Example 10-5
Business Unit Definition Considerations 10-6
Implementing Business Units Overview 10-7
Managing Business Units 10-8
Assigning Business Unit Functions. 10-9
Managing Service Provider Relationships. 10-11
Service Provider Model for Procurement Services 10-12
Service Provider Model for Payables Payment Services 10-13
Payment Services Model: Dedicated 10-14
Payment Services Model: Self-Service 10-15
Payment Services Model: Dedicated and Self-Service 10-16
Practice 10-1 Overview: Viewing Your Business Unit 10-17
Practice 10-2 Overview: Viewing the Assigned Business Unit Functions 10-18
Manage Reference Data Sets 10-19
Reference Data Sharing: Overview 10-20
Practice 10-3 Overview: Creating a Reference Data Set 10-21
Determinant and Determinant Types 10-22
Determinant Types 10-23
Assignments to One Set Only, with Common Values 10-24
Assigning Sets to Business Units 10-25
Manage Reference Data Partitions 10-26
Assignments to One Set Only, with No Common Values 10-27
Assignments to Multiple Sets, with No Common Values 10-28
Payables Payment Terms Example 10-29
Reference Data Set: Examples 10-30
Setting Up Payment Terms for Reference Data Sharing 10-31
Practice 10-4 Overview: Managing your Business Unit Set Assignment 10-33
xiv
Practice 10-5 Overview: Provisioning Data Roles 10-34
Summary 10-35
11 Configuring Oracle Fusion Tax

Objectives 11-2
Understanding Oracle Fusion Tax 11-3
Practice 11-1 Overview: Viewing Calculated Tax on a Payables Transaction
Demonstration 11-5
Tasks to Configure Oracle Fusion Tax 11-6
Define Taxes for Rapid Implementation Task List 11-7
Rapid Implementation Spreadsheets 11-8
Tax Configuration Workbook 11-9
Tax Implementation Workbook 11-10
Tax Setup Spreadsheets 11-12
Define Tax Configuration Task List 11-13
Define Advanced Tax Configuration Task List 11-15
Oracle Fusion Tax Architecture 11-16
Tax Requirements Organization 11-18
Foundation Tax Configuration 11-19
Examples of Foundation Tax Setup 11-20
Setting Up Foundation Tax Components 11-21
Configuration Owners and Options 11-22
Tax Regimes 11-23
Taxes 11-24
Tax Statuses 11-26
Tax Jurisdictions 11-27
Tax Rates 11-28
Tax Recovery Rates 11-29
Practice 11-2 Overview: Creating a US Sales Tax Using the Tax Configuration
Workbook 11-30
Practice 11-3 Overview: Creating a VAT Tax Using the Tax Configuration Workbook
(Optional) 11-31
Setting Up Party Tax Profiles 11-32
Tax Classification Code 11-34
Setting Up Advanced Tax Configuration 11-35
Tax Rule Configuration 11-36
Key Building Blocks of Tax Rules 11-37
Tax Determination Process 11-38
Step 1: Determine Applicable Tax Regimes and Candidate Taxes 11-39
Steps 2 and 3: Determine Place of Supply and Tax Jurisdiction and Tax Applicability
11-41
xv
Step 4: Determine Tax Registration 11-43
Step 5: Determine Tax Status 11-44
Step 6: Determine Tax Rate 11-45
Simplified Tax Line Override Setup 11-46
Step 7: Determine Taxable Basis 11-47
Step 8: Determine Tax Calculation 11-48
Step 9 (if applicable): Determine Tax Recovery 11-49
Setting Up Withholding Tax Configuration 11-50
Calculating Withholding Taxes 11-51
Enabling Withholding Tax Configuration 11-52
Withholding Tax Regime to Rates 11-53
Withholding Tax Rules 11-55
Setting Up Tax Point Basis 11-56
Setting Up Delivery-Based Tax Calculation 11-57
Setting Up Transaction Tax Thresholds 11-59
Calculating Transaction Tax Thresholds 11-60
Setting Up Tax Box Allocations 11-61
Setting Up Tax Reporting Configuration 11-62
Setting Up Global Tax Reporting 11-63
Reporting and Analysis 11-64
Verifying Tax Configuration 11-65
Practice 11-4 Overview: Using the Tax Simulator to Test a Receivables Transaction
11-66
Practice 11-5 Overview: Enabling your Tax for Transactions 11-67
Summary 11-68
12 Configuring Subledger Accounting

Objectives 12-2
Oracle Fusion Subledger Accounting: Overview 12-3
The Create Accounting Process 12-4
Accounting Methods Overview 12-5
Accounting Event Model Example 12-7
Payables Accounting Event Model 12-8
Accounting Methods Overview 12-10
How the Different Types of Rules Fit Together 12-12
Managing Accounting Methods and Rules Flow 12-13
Accounting Methods: Custom Formulas 12-14
Manage Custom Formulas: Explained 12-15
Manage Custom Formulas: Formula definition 12-16
Manage Custom Formulas: Predefined Formula Functions 12-17
Enabling Custom Formulas 12-21
xvi
Accounting Methods: Mapping Sets 12-22
Creating Mapping Sets 12-23
Accounting Methods: Account Rules 12-25
Creating Account Rules: Rule Type 12-26
Creating Account Rules – Value Types 12-27
Account Rules Best Practices 12-28
Conditions 12-29
Practice 12-1 Overview: Creating Three Account Rules. 12-31
Accounting Methods: Description Rules 12-32
Expanded Subledger Journal Entry Descriptions 12-34
Practice 12-2 Overview: Creating a Description Rule. 12-35
Accounting Methods: Supporting References 12-36
Accounting Methods: Journal Line Rules 12-37
Practice 12-3 Overview: Creating Two Journal Line Rules. 12-39
Accounting Methods: Journal Entry Rule Sets 12-40
Creating Journal Entry Rule Sets 12-41
Activating a Subledger Journal Entry Rule Sets 12-43
Practice 12-4 Overview: Creating a Journal Entry Rule Set 12-44
Accounting Methods 12-45
Creating or Modifying Accounting Methods 12-46
Practices 12-5 Overview: Duplicating and Modifying an Accounting Method. 12-48
Accounting Methods: Migrating the Accounting Configuration 12-49
Create Accounting Process 12-50
Create and Process Subledger Journal Entries 12-51
Practices 12-6 Overview: Submitting Create Accounting in Draft and Viewing the
Subledger Journal in Payables. 12-52
Practices 12-7 Overview: Submitting Create Accounting in Final/Post 12-53
Manual Features of Subledger Accounting 12-54
Improved Online Accounting Messages 12-55
Expanded Accounting Lines Window 12-56
Summary 12-57
13 Configuring Oracle Fusion Payables

Objectives 13-2
Required tasks to Configure Payables 13-3
Payables Terminology 13-4
Flow of Default Values 13-6
Managing Procurement Agents 13-7
Practice 13-1 Overview: Defining Your User as a Procurement Agent. 13-8
Managing Payment Terms 13-9
Payment Terms Due Date and Discount Dates 13-10
xvii
Day of Month Payment Term Example 13-11
Defaults and Predefined Payment Terms 13-12
Practice 13-2 Overview: Creating a Payment Term 13-13
Managing Common Options for Payables and Procurement 13-14
Default Distributions 13-15
Automatic Offsets 13-17
Automatic Offset by Primary Balancing Segment 13-19
Automatic Offset by All Segments, Except Natural Account 13-20
Currency Conversion 13-21
Expense Accruals 13-22
Self-Billed Invoices 13-23
Legal Entity Information 13-24
Practice 13-3 Overview: Managing Common Options for Payables and Procurement
13-25
Manage Invoice Options 13-26
Manage Invoice Options: Invoice Entry 13-27
Manage Invoice Options: Matching 13-31
Manage Invoice Options: Discount 13-32
Manage Invoice Options: Prepayment 13-33
Manage Invoice Options: Approval 13-34
Manage Invoice Options: Interest 13-35
Manage Invoice Options: Payment Request 13-36
Manage Invoice Options: Self-Service Invoices 13-37
Practice 13-4 Overview: Managing Invoice Options 13-38
Manage Payment Options 13-39
Practice 13-5 Overview: Managing Payment Options 13-41
Optional Tasks to Configure Payables 13-42
Define Automated Invoice Processing Configuration 13-43
Manage Payables Calendars 13-45
Manage Tax Reporting and Withholding Tax Options 13-46
Income Tax Reporting Options 13-47
Withholding Tax Options 13-48
Manage Payables Lookups 13-50
Manage Payables Descriptive Flexfields 13-51
Manage Payables Document Sequences 13-53
Manage Distribution Sets 13-55
Practice 13-6 Overview: Managing Distribution Sets 13-56
Manage Invoice Tolerances 13-57
Manage Invoice Holds and Releases 13-59
Manage Aging Periods 13-60
Define Payables Tax and Withholding 13-61
xviii
Manage Tax Regions 13-62
Manage Reporting Entities 13-63
Additional Withholding Tax Setups 13-65
Manage Interest Rates 13-66
Manage Bank Charges 13-67
Summary 13-68
14 Configuring Oracle Fusion Payments: Payables

Objectives 14-2
Practice 14-1 Overview: Creating Banks, Branches and Accounts Using a
Spreadsheet. 14-3
Practice 14-2 Overview: Creating a Payment Document for a Bank Account. 14-4
Overview of Oracle Fusion Payments 14-5
Overview of Disbursements for Payments 14-6
The Disbursements Process 14-7
Key Decision and Best Practice for Payment Processing 14-8
Key Decision and Best Practices for Payment Selection Criteria 14-9
Service Provider Model for Payables Payment Services 14-10
Payment Services Model: Dedicated 14-11
Payment Services Model: Self-Service 14-12
Payment Services Model: Dedicated and Self-Service 14-13
Configuring Payment System Connectivity Overview 14-14
Prerequisites for Configuring Payment System Connectivity 14-15
Disbursement Payment File Formats 14-16
Key Decision and Best Practices for Using Formats 14-17
Practice 12-1 Overview: Creating a Disbursement Payment File Format. 14-19
Transmission Configuration Concepts 14-20
Key Decision and Best Practices for Using Transmission Protocols 14-21
Practice 12-2 Overview: Creating the Transmission Configuration. 14-22
Managing Payment Systems 14-23
Practice 14-3 Overview: Creating a Payment System 14-24
Defining Disbursements 14-25
Prerequisites for Defining Disbursements 14-26
Disbursement Payment Methods 14-27
Creating Usage Rules for Payment Methods 14-29
Using Validations 14-30
Creating or Assigning Validations to Payment Methods 14-32
Choosing Predefined Validations 14-33
Creating User-Defined Validations 14-34
Manage Payment Method Defaulting Rules 14-35
Practice 14-4 Overview: Creating a Payment Method. 14-36
xix
Manage Payment Codes 14-37
Manage Payment Process Profiles 14-38
Prerequisites for Defining Payment Process Profiles 14-39
Payment Process Profile Concepts 14-40
Creating a Payment Process Profile 14-41
Payment Process Profiles: Usage Rules Tab 14-42
Payment Process Profiles: Payment System Tab 14-43
Payment Process Profiles: Payment Tab 14-44
Payment Process Profiles: Payment File Tab 14-45
Payment Process Profiles: Grouping Tab 14-48
Payment Process Profiles: Reporting Tab 14-49
Managing Disbursement System Options 14-51
Practice 14-5 Overview: Creating a Payment Process Profile. 14-52
Payment Document and Reference Numbers 14-53
Payment Process Requests 14-54
Payment Process Requests: Selection Criteria Tab 14-55
Payment Process Requests: Payment and Processing Options Tab 14-57
Practice 14-8 Overview: Submit a Payment Process Request 14-61
Summary 14-62
15 Configuring Oracle Fusion Receivables

Objectives 15-2
Order to Cash 15-3
Configuring Receivables: Rapid Implementation 15-4
Configuring Receivables: Complete Your Setup 15-7
Managing the Receivables System Options 15-8
Managing Receivables System Options: Billing and Revenue General information
15-9
Managing Receivables System Options: Billing and Revenue Accounting 15-11
Receivables System Options: Billing and Revenue Transactions 15-12
Receivables System Options: Billing and Revenue Transaction and Statement
Delivery Using E-Mail 15-14
Receivables System Options: Billing and Revenue Late Charges 15-15
Receivables System Options: Billing and Revenue Customers 15-16
Receivables System Options: Billing and Revenue AutoInvoice 15-17
Receivables System Options: Billing and Revenue Tuning Segments 15-18
Receivables System Options: Cash Processing General Information 15-19
Receivables System Options: Cash Processing Application Exception Rule 15-21
Receivables System Options: Cash Processing Accounting 15-22
Receivables System Options: Cash Processing Automatic Receipts 15-23
Receivables System Options: Cash Processing Bills Receivable 15-24
xx
Rapid Implementation and Receivables System Options 15-25
Rapid Implementation: System Option Settings 15-26
Practice 15-1 Overview: Reviewing Receivables System Options 15-29
Managing AutoAccounting Rules 15-30
AutoAccounting Rules: Table Names and Constant Values 15-31
Rapid Implementation: AutoAccounting 15-33
Practice 15-2 Overview: Reviewing AutoAccounting Rules 15-34
Managing Remit-to Addresses 15-35
Remit-to Addresses: Automatic Assignment 15-36
Rapid Implementation and the Remit-to-Address for a Business Unit 15-37
Practice 15-3 Overview: Reviewing Remit-to Addresses 15-38
Managing Receivables Activities 15-39
Receivables Activities: Setup 15-40
Rapid Implementation and Receivables Activities 15-41
Rapid Implementation: Receivables Activities 15-42
Practice 15-4 Overview: Reviewing Receivables Activities 15-43
Managing Statement Cycles 15-44
Statement Cycles 15-45
Rapid Implementation and Statement Cycles 15-47
Practice 15-5 Overview: Reviewing Statement Cycles 15-48
Defining Approval Limits 15-49
Implementation Considerations for Transactions 15-50
Set Up Document Sequences 15-51
Define Users for Credit Memo Workflow 15-52
Set Up Balance Forward Billing 15-54
Manage Value Sets 15-55
Customers and Parties 15-58
The Trading Community Model 15-59
Managing Customers 15-60
Manage Customer Profile Classes 15-61
Defining Profile Classes: Profile Class Tab 15-62
Profile Classes: Late Charges Tab 15-64
Practice 15-6 Overview: Creating a Customer Profile Class. 15-66
Customer Model 15-67
Creating an Organization Customer: Header 15-68
Creating a Customer: Address 15-70
Creating a Customer: Address Business Purposes 15-72
Uploading Customer Data 15-74
Practice 15-7 Overview: Creating a Customer. 15-75
AutoInvoice Process 15-76
xxi
AutoInvoice Interface Tables 15-78
Implement AutoInvoice: Profile Option Settings 15-80
Implement AutoInvoice: Transaction Flexfields 15-82
Implement AutoInvoice: Optional Setups 15-83
AutoInvoice Grouping Rule Transaction Attributes 15-84
Grouping Rules 15-85
Line Ordering Rules 15-86
Import Exceptions Overview 15-87
Define Payment Terms 15-89
Define Transaction Types 15-91
Define Transaction Types: Using Natural Application 15-92
Define Transaction Types 15-93
Practice 15-8 Overview: Defining a Transaction Type 15-95
Define Transaction Sources 15-96
Defining Transaction Sources for AutoInvoice 15-99
Define Transaction Sources for CPQ Cloud Integration 15-100
Practice 15-9 Overview: Defining a Transaction Source 15-102
Define Memo Lines 15-103
Set Up Balance Forward Billing 15-104
Defining Remittance Banks and Bank Accounts 15-105
Practice 15-10 Overview: Creating Banks, Branches, and Accounts Using a
Spreadsheet 15-106
Receipt Class, Receipt Method, and Bank Account Relationship 15-107
Defining Receipt Classes 15-108
Receipt Methods 15-110
Practice 15-11 Overview: Creating a Receipt Class and Receipt Method 15-111
Defining Receipt Sources 15-112
Practice 15-12 Overview: Creating a Receipt Source 15-113
AutoCash Rules 15-114
Define Application Rule sets 15-115
Define Application Rules: Tax Treatment Option 15-116
Define AutoMatch Rules 15-117
Define AutoMatch Rules: Threshold Settings 15-118
Define AutoMatch Rules: AutoMatch Calculation 15-119
Define Receipt Application Exception Rules 15-120
Implementation Considerations for Lockbox 15-122
Implementation Considerations for Lockbox: Receipt Match By and SmartReceipts
15-123
Implementation Considerations for Revenue Management 15-124
Settings for Revenue Recognition 15-125
Revenue Scheduling Rules 15-126
xxii
Revenue Scheduling Rules: Rule Types 15-127
Define Revenue Policies 15-128
Define Revenue Contingencies 15-130
Summary 15-133
16 Configuring Oracle Payments: Receivables

Objectives 16-2
Defining Remittance Banks and Bank Accounts 16-3
Practice 16-1 Overview: Creating Banks, Branches, and Accounts Using a
Spreadsheet 16-4
Receipt Class, Receipt Method, and Bank Account Relationship 16-5
Defining Receipt Classes 16-6
Receipt Methods 16-8
Practice 16-2 Overview: Creating a Receipt Class and Receipt Method 16-9
Defining Receipt Sources 16-10
Practice 16-3 Overview: Creating a Receipt Source 16-11
AutoCash Rules 16-12
Define Application Rule sets 16-13
Define Application Rules: Tax Treatment Option 16-14
Define AutoMatch Rules 16-15
Define AutoMatch Rules: Threshold Settings 16-16
Define AutoMatch Rules: AutoMatch Calculation 16-17
Define Receipt Application Exception Rules 16-18
Implementation Considerations for Lockbox 16-20
Implementation Considerations for Lockbox: Receipt Match By and SmartReceipts
16-21
Summary 16-22
17 Configuring Oracle Fusion Cash Management

Objectives 17-2
Cash Management: Overview 17-3
Cash Management Setups for Automatic Reconciliation Overview 17-4
Set Up Banks, Branches, and Accounts 17-6
Manage and Maintain Banks 17-7
Manage and Maintain Branches 17-8
Manage and Maintain Accounts 17-10
Manage and Maintain Accounts: General Tab 17-11
Manage and Maintain Accounts: Payment Documents 17-12
Manage and Maintain Accounts: Control Tab 17-13
Manage and Maintain Accounts: Security Tab 17-15
Manage and Maintain Accounts: Business Unit Access Tab 17-16
xxiii
Configuring Cash Management Rapid Implementation 17-17
Bank Statement Processing Overview 17-18
Key Setup Tasks for Bank Statement Processing 17-19
Manage Cash Transaction Type Mapping 17-20
Bank Statement Transaction Codes 17-21
Practice 17-1 Overview: Creating Transaction Codes 17-23
Payment Code Map Groups 17-24
Code Map Group Example 17-26
Bank Statement Formats 17-27
Parse Rule Sets 17-28
Parse Rule Set Example 17-29
Bank Statement Transaction Creation Rules 17-31
Practice 17-2 Overview: Managing Bank Statement Transaction Creation Rule 17-
33
Bank Statement Reconciliation Setups 17-34
Bank Statement Reconciliation Matching Rules 17-35
Practice 17-3 Overview: Managing Bank Statement Matching Rules 17-37
Bank Statement Reconciliation Tolerance Rules 17-38
Creating Reconciliation Tolerance Rules 17-39
Practice 17-4 Overview: Managing Bank Statement Tolerance Rules 17-41
Reconciliation Rule Sets 17-42
Practice 17-5 Overview: Managing Reconciliation Rule Sets 17-43
Practice 17-6 Overview: Assigning a Rule Set to a Bank Account 17-44
Defining Subledger Accounting Rules: Cash Management Accounting Event Model
17-45
Performing Bank Statement Reconciliation 17-46
Practice 17-7 Overview: Performing a Bank Statement Reconciliation with
Autoreconciliation. 17-48
Reporting and analysis 17-49
Cash Management Dashboard 17-50
Cash Management Infolets 17-51
Cash Positioning and Forecasting – Cash Balances 17-53
Cash Position Page 17-54
5 Day Forecast Page 17-55
Transactions Cube 17-56
Ready to Use Smart View Templates 17-57
Manual Transactions 17-58
Bank Account Transfers 17-59
Ad Hoc Payments 17-61
Setup Options in Payments 17-62
Intraday Bank Statement Support 17-63
xxiv
External Cash Transactions Attachments 17-64
Summary 17-65
18 Configuring Oracle Fusion Advanced Collections

Objectives 18-2
Advanced Collections Overview 18-3
Data Points and Formulas: Example 18-9
How Data Points, Scoring Formulas, and Strategies Work Together 18-11
Related Fusion Applications Requirements 18-13
Practice 18-1 Overview: Guided Tour of Advanced Collections Demonstration 18-14
Aging Methods Overview 18-15
Creating Aging Methods 18-16
Practice 14-2 Overview: Creating an Aging Method 18-17
Collectors Overview 18-18
Creating Collectors 18-19
Practice 18-3 Overview: Creating a Collector 18-20
Manage Dunning Configurations 18-21
Creating Dunning Configurations 18-22
Predefined Dunning Templates 18-24
Practice 18-4 Overview: Reviewing Dunning Templates Demonstration 18-25
Manage Collections Preferences 18-26
Global Preferences 18-27
Preferences 18-29
Manage Collections Preferences 18-30
Manage Collections Methods 18-31
Manage Collections Scoring Data Points 18-32
Manage Collections Scoring Formula 18-33
Manage Collections Strategy Tasks 18-34
Practice 18-5 Overview: Creating a Strategy Task 18-36
Manage Collections Strategies 18-37
Creating a Strategy 18-39
Practice 14-6 Overview: Creating a Strategy 18-40
Optional Implementation Configurations 18-41
Manage Collections Lookups 18-42
Manage Collections Note Types and Mapping 18-44
Managing Note Descriptive Flexfields 18-45
Advanced Collection Metrics 18-46
Demonstration Overview: Enabling Advanced Collection Metrics 18-48
Advanced Collections Metrics Tips 18-49
xxv
Summary 18-50
19 Configuring Assets
Objectives 19-2
Implementing Assets 19-3
Planning Your Implementation 19-4
Inquiring About Your Company’s History 19-5
Obtaining Existing Asset Information 19-6
Determining the Conversion Period 19-7
Define Fixed Assets Configuration 19-8
Define Fixed Assets Configuration for Rapid Implementation 19-9
Prerequisite Setup 19-10
Creating a New Assets Implementation Spreadsheet 19-11
Updating an Existing Assets Implementation 19-12
Demonstration 19-1 Overview: Updating an Existing Assets Configuration 19-13
Managing Assets Key Flexfields and Value Sets 19-14
Location Key Flexfield Implementation: Considerations 19-15
Category Key Flexfield Implementation: Considerations 19-17
Defining Your Flexfield Segments 19-18
Managing Asset Locations 19-19
Defining Asset Locations 19-20
Asset Key Flexfield Implementation: Considerations 19-21
Defining Your Flexfield Segments 19-22
Practice 19-2 to 19-4 Overview: Reviewing and Defining Asset Key Flexfields 19-
23
Managing System Controls 19-24
Defining Your System Controls 19-25
System Controls Implementation: Considerations 19-27
Practice 19-5 Overview: Review Asset System Control Options Demonstration 19-
28
Managing Fiscal Years and Calendars 19-29
Defining Fiscal Years 19-31
Fiscal Year Implementation: Considerations 19-33
Defining Asset Calendars 19-34
Calendar Implementation: Considerations 19-37
Prorate Conventions: Concepts 19-39
Prorate Conventions: Examples 19-42
Retirement Conventions 19-43
Prorate Convention Implementation: Considerations 19-44
Optional Implementation Steps 19-48
Practice 19-6 Overview: Managing Fiscal Years 19-49
xxvi
Practice 19-7 Overview: Managing Asset Calendars 19-50
Practice 19-8 Overview: Managing Prorate Conventions 19-51
Managing Asset Books 19-52
Corporate Books 19-53
Asset Book Setup 19-54
Asset Book Accounts 19-56
Asset Book Rules 19-57
Practice 19-9 Overview: Managing Asset Books 19-59
Tax Books 19-60
Asset Books and Ledgers, Subledgers, and Business Units 19-61
Asset Book Implementation: Considerations 19-64
Defining Your Asset Book: Multiple Depreciation Requirements 19-66
Defining Your Asset Book: Multiple Currency Representations 19-67
Defining Your Asset Book: Multiple Accounting Representations 19-69
Implementation Questions 19-70
Reference Data Sharing Across Asset Books 19-72
Reference Data Sharing: Overview 19-73
Determinant and Determinant Types 19-74
Reference Data Sharing Across Asset Books 19-75
Assignments to One Set Only, with Common Values 19-76
Assignments to One Set Only, with No Common Values 19-77
Reference Data Sharing: US Company Example 19-78
Reference Data Sharing: Multinational Company Example 19-79
Managing Asset Categories 19-80
Defining Asset Categories 19-82
Defining Default Depreciation Rules 19-84
Defining Oracle Fusion General Ledger Accounts 19-85
Category Implementation: Considerations 19-86
Practice 19-10 Overview: Managing Asset Categories 19-87
Managing Cash-Generating Units 19-88
Cash-generating Units Example 19-89
Managing Distribution Sets 19-90
Defining Distribution Sets 19-91
Managing Profile Options 19-92
Profile Options Settings 19-93
Managing Lookups 19-96
Managing Descriptive Flexfields 19-99
Managing Asset Keys 19-103
Practice 19-11 Overview: Provisioning Data Roles to the User Account 19-105
Summary 19-106
xxvii
20 Configuring Oracle Expenses
Objectives 20-2
Rapid Implementation Overview 20-3
Managing Expenses System Options 20-4
Expenses System Options Concepts 20-5
User Options for Expense Report 20-6
Corporate Options for Expense Report 20-7
Processing Options for Expense Report 20-9
Using Printable Expense Reports 20-10
Assigning a Printable Expense Report to an Existing Business Unit 20-11
Practice 20-1: Managing System Options 20-12
Setting Up Expense Report Templates 20-13
Expense Report Template Concepts 20-14
Defining Expense Report Templates Considerations 20-15
Defining Default Expense Report Templates 20-16
Inactivating Expense Report Templates 20-17
Defining Default Expense Report Templates 20-18
Expense Types Overview 20-19
Create Expense Type 20-20
Itemize Expense Types 20-21
Set Up Project-Enabled Expense Types 20-23
Enable Tax Classification Code 20-24
Modifying Expense Account Segments 20-25
Practice 20-2 Overview: Creating an Expense Report Template 20-26
Configuring Expense Approval Rules Overview 20-27
Expense Approval Rules Overview 20-28
Setting Up Expense Approval Rules 20-29
Manage Expense Report Approval Rules Tasks 20-30
Manage Expense Report Approval Rules 20-31
Defining Conversion Rates 20-34
Selecting a Business Unit 20-35
Defining Conversion Rates and Conversion Rate Types 20-36
Specifying a Conversion Rate Policy 20-37
Practice 20-4 to 20-5 Overview: Viewing a Conversion Rate Policy Warning and
Error 20-38
Define Expense Policies and Rules 20-39
Managing Policies by Expense Category 20-40
Enforcing Expense Policies 20-41
Common Components of Category-Based Expense Policies 20-42
Mandatory Setup Tasks for Category-Based Expense Policies 20-44
xxviii
Practice 20-6 to 20-9: Setting Up Expense Policies and Rules 20-45
Tasks for Setting Up a Mileage Policy 20-46
Setting Up a Mileage Policy 20-47
Creating a Mileage Policy 20-48
Specifying Eligibility Rules 20-49
Specifying Mileage Rate Determinants 20-50
Defining the Add-On Rates 20-51
Practice 20-10: Setting up a Mileage Expense Policy 20-53
Tasks for Setting Up an Entertainment Policy 20-54
Setting Up an Entertainment Policy 20-55
Creating an Entertainment Policy 20-56
Practice 20-11 : Setting up an Accommodations Expense Policy 20-60
Setting Up Corporate Cards 20-61
Configuring Credit Card Data 20-62
Overview of Corporate Card Transaction Processing 20-63
Configuring Corporate Card Issuers 20-65
Managing Corporate Card Programs 20-67
Configuring Corporate Card Programs 20-68
Downloading Corporate Card Transaction Files 20-69
Uploading Corporate Card Transactions with Encrypted Corporate Card Numbers
20-70
Practice 20-12 to 20-13: Setting Up and Creating Corporate Card Programs 20-71
Specifying a Corporate Card Usage Policy 20-72
Practice 20-14: Setting Up a Corporate Card Usage Policy Warning 20-75
Uploading Corporate Card Transactions with Encrypted Corporate Card Numbers
20-76
Processing Expense Reports Containing Both Pay 20-77
Payment Options for Corporate Transactions 20-78
Processing Corporate Issuer Payment Requests for Company Pay Transactions
20-80
Creating Corporate Card Issuer Payment Requests Transactions 20-81
Settings for Corporate Card Issuer Payment Requests 20-82
Processing Corporate Card Issuer Payment Requests for Company Pay
Transactions 20-83
Populating Payables Open Invoice Interface Tables 20-84
Creating Corporate Card Issuer Payment Requests 20-85
Handling Processed and Rejected Expense Reports 20-86
Individual Pay 20-87
Individual Pay Payment Option 20-88
Accounting for Corporate Card Transactions 20-90
Accounting for Corporate Card Transactions: Individual Pay 20-92
xxix
Accounting for Corporate Card Transactions: Both Pay 20-93
Accounting for Corporate Card Transactions: Company Pay 20-94
Setting Up Receipt Management Policies 20-96
Specifying Receipt Management Policies 20-97
Specifying Receipt Management 20-98
Specifying Type of Receipts 20-99
Granularity of Receipt Requirements 20-100
Specifying Receipt Requirements 20-101
Creating Expense Report Receipt and Notification Rule 20-102
Practice 20-15: Creating Receipt and Notification Rules 20-103
Setting Up Travel 20-104
Integrating with GetThere 20-105
Benefits of Integrating with Travel Partners 20-106
Benefits of Setting Up Travel Integration 20-107
Setting Up Travel Integration 20-108
Configuring Travel Partner and Travel Sites 20-109
Scheduling the Import Travel Itinerary Process 20-110
Assigning a Travel Administrator 20-111
Setting Up Optional Travel Tasks 20-112
Enabling Automatic Creation of Trip-Based Expense Reports 20-113
Setting Up Centrally-Billed Travel Cards 20-114
Setting Up Travel Itinerary Validation Rules 20-115
Setting Up Centrally-Billed Travel Cards 20-116
Third-Party Expense Reimbursements 20-117
Processing Third-Party Expense Reimbursements 20-118
Setting Up Third-Party\ Expense Reimbursements 20-121
Exporting Data from Expenses to a Third-Party Application 20-122
Using Mobile Devices to Increase Productivity 20-123
Setting Up the Mobile Device Application 20-126
Enabling Expenses Mobile Application 20-127
Using the Mileage Tracker 20-128
Submitting an Expense Report from a Mobile Device 20-129
Mobile Expense Lines That Cannot Be Included in an Expense Report 20-130
Mobile Expense Report with a Status of Saved 20-131
Mobile Expense Report with a Status of Pending Manager Approval 20-132
Summary 20-133
xxx
1
Introduction to Oracle Financials
Cloud Implementation
Copyright © 2016, Oracle and/or its affiliates. All rights reserved.

Course Objectives
After completing this course, you should be able to:

• Use Oracle Functional Setup Manager (FSM) to implement
Oracle Fusion Financials.
• Understand Financial Security.
• Discuss the common applications configuration for Oracle
Fusion Financials.
• Describe the configuration of enterprise structures and the
related Vision Corporation story.
• Configure Oracle Fusion Financial Applications.
Oracle Financials Cloud: Financials Implementation for R11 1 - 2

Course Approach
Each lesson in this course:

• Begins with your instructor presenting important concepts
related to implementing Oracle Fusion Financials.
• May also include one or more of the following activities:
– Complete a portion of the case study in FSM.
– Discuss key decisions and best practices.
– Complete an activity or knowledge assessment task.
In this course, the instructor:

• Presents introductory modules.
• Acts as a business analyst representing the case study customer.
• Imparts information to assist you with the Oracle Fusion Financial implementation.
• Provides review sessions as needed.

Oracle Fusion Implementation Resources
Classroom and Other Resources:

• Oracle Financials Cloud: Financials Implementation (This
guide and its companion course)
• Oracle Fusion Applications Help in the Applications
• Oracle Fusion Technology Library on OTN
• My Oracle Support (MOS)
• Oracle Fusion Cloud Library
• Your instructor
• Other students
•Oracle Financials Cloud: Implementing Subledger Accounting

• Oracle Fusion Technology Library on OTN:

(http://www.oracle.com/technetwork/index.html)
• My Oracle Support (MOS): (https://support.oracle.com/ ) including this documents:
- Getting Started with Oracle Fusion Applications: Common Implementation, Article
ID 1387777.1 on Oracle Support
- Oracle Fusion Applications: Financials Reporting (Document 1458904.1
• Oracle Help Center: (http://docs.oracle.com/cloud/latest/financialscs_gs/index.html)
including these Oracle Financials Cloud books:
- Getting Started with Your Financials Cloud Implementation
- Implementing Enterprise Structures and General Ledger
- Using Common Features including Infolet Personalization topics
- Customizing the Applications for Functional Administrators including Infolet
Customization topics
- Security Reference for Oracle Financials Cloud
- Creating Analytics and Reports
- Using Analytics and Reports

Oracle Help Center: docs.oracle.com
Oracle Help Center is:

• Central hub for all documentation and tutorials.
• Organized by major product categories including Cloud, Applications, Middleware, and
Database.
• Cloud Application pages are organized by Cloud.

Oracle Cloud Application Service Pages
Consistent organization, content, and link format for Cloud service pages.
• Get Started
• Videos
• Books
Friendly task panel to use to change focus from Cloud to:
• Applications
• Middleware
• Database
• Other Documentation

Video Subject Areas on the Oracle Help Center
Link to the Video Area in Oracle Help Center

• Get Started with Oracle Applications Cloud
• Set Up Oracle Applications Cloud
• Customize Oracle Applications Cloud
• Get Started with Oracle Financials Cloud
• Use General Ledger
• Use Payables Invoice to Pay
• Use Receivables Credit to Cash
• Use Other Oracle Financials Cloud Products
• Use Oracle Social Network to Improve Collaboration
• Use Oracle Transactional Business Intelligence for Financials
Cloud
Link to the videos: http://docs.oracle.com/cloud/latest/financialscs_gs/financialscs_videos.htm

Note: New videos are constantly being added.

New Reference Guides
• File Based Data Import

includes links to:
– Spreadsheets templates.
– Load and import
processes. NEW
• Tables and Views includes:
– Columns
– Primary and Foreign
Keys
– Indexes
• SOAP (Simple Object
Access Protocol) Web
Services
Oracle Enterprise Repository has been decommissioned and the following new guides are on
the Oracle Cloud Help Center at
http://www.oracle.com/webfolder/technetwork/docs/HTML/oer-redirect.html.
• File Based Data Import (FBDI) is used to load data into Oracle Fusion Applications from
external sources, such as legacy systems and third-party applications. The File Based
Data Import for Oracle Financials Cloud Guide includes links to:
- Spreadsheets used to load data into Oracle Fusion Applications from external
sources, such as legacy systems and third-party applications. The spreadsheet
templates helps to structure, format, and generate the data file according to the
requirements of the target application tables.
- File-based load process to load the data files into the interface tables.
- Application-specific data import processes to transfer data from interface tables to
the application tables in your Oracle Fusion Applications
• Tables and Views for Oracle Financials Cloud Guide includes:
- The tables with the basic information about the table columns, primary and foreign
keys, and indexes.
- The views, columns, and query details that are associated with each view.

• SOAP (Simple Object Access Protocol) Web Services for Oracle Financials Guide
include:
- Business Object Services relationships, operations, and security.
- Service Data Objects relationships and attributes.
Note: Use SOAP web services to integrate with or extend Oracle Applications Cloud. Through
web services, you can integrate heterogeneous applications within the enterprise or expose
business functions to Oracle Cloud partners and customers over the Internet.

Friendly Search
• Simple search entry: Just type your topic in the field.

• Comprehensive view of search results: Results show the guide as well as the topic with
direct links to the topic.
• Number of results and context displayed.
• Refine Search task panel enables you to reduce the number of results.
• Breadcrumbs appear at the top of topics you select to allow easy return to the list of
results.

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

• Introduce the Oracle Fusion applications.
• Discuss Oracle Financials Cloud.
• Discuss your implementation strategy.
• Discuss the Common Financial Applications Configuration.
• Identify your implementation needs.

Introduction to Oracle Fusion Applications
Oracle Fusion Applications is:

• An integrated suite of business applications.
• Engineered to work together.
• Designed to ensure that your enterprise can be modeled.
Oracle Fusion Applications is:

• An integrated suite of business applications that:
- Connects and automates the entire flow of business processes across both front
and back office operations.
- Addresses the needs of a global enterprise.
• Engineered to work together, allowing users to streamline the setup process by sharing
common setup data across applications.
• Designed to ensure that 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

Oracle Financials Cloud: Overview
Oracle Financials Cloud is a complete and integrated financial

management solution with:
• Automated financial processing.
• Effective management control.
• Real-time visibility to financial results.
Oracle Financials Cloud with Oracle Fusion Applications provides:

• Open, standards-based enterprise applications that function in the cloud through a web
browser.
• Broad suite of capabilities including:
- General Ledger
- Accounts Payable
- Accounts Receivable
- Fixed Assets
- Expenses
- Advanced Collections
- Cash Management
- Centralized accounting, tax, payment, and intercompany engines
• Improved performance, lower IT costs, and better analysis and reporting results.

Financials Cloud: Key Features
• Multidimensional reporting platform.

• Multiple reporting requirements.
• Role-based dashboards.
• Embedded transactional intelligence.
• Imaging integration.
• Spreadsheet integration.
Financials
• Innovative, embedded, multidimensional reporting platform.

• Simultaneous accounting of multiple reporting requirements.
• Role-based dashboards that push issues and work to users.
• Embedded transactional intelligence that guides users’ decisions by providing key
business indicators in a graphical, real-time dashboard.
• Imaging integration for supplier invoices.
• Extensive spreadsheet integration across finance functions to simplify data entry.

Implementation Discussion
Discuss the needs for your implementation:

• Scope of the project.
• Schedule and agenda of the project.
• People involved in the project.
• Applications to be implemented.
• Employees.
• Customers.
• Suppliers.
Instructor-led discussion on the student’s implementations.

Examples of questions to ask the students:
• What is the scope of your project?
• How soon will you go live?
• Are you using consultants or in-house staff members?
• What subledgers are you implementing?
• Will you use Oracle HCM?
• Are you in sales and do you have customers?
• Will you use invoice imaging?

Common Applications Configurations: Overview
• Legal Structure
• Managerial Structure
• Functional Structure
Every enterprise has three fundamental structures: Legal, Business (managerial), and
Functional—that are used to describe its operations and provide a basis for reporting. In
Oracle Fusion, these structures are implemented by using the chart of accounts and
organizations. Although many alternative hierarchies can be implemented and used for
reporting, you likely have one primary structure that organizes your business into divisions,
business units, and departments aligned by your strategic objectives.
This section introduces the Oracle Fusion Financial Applications concepts for:
• Legal structure: Defines your legal entities.
• Managerial structure: Defines your divisions and business units.
• Functional structure: Defines your departments and organizations.

Common Application Discussion
Discuss the needs for your implementation:

• 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?
Instructor-led discussion on various aspects of their enterprise structure. This discussion

helps the students think about the levels within their organization that need to be reported on
and secured. The discussion leads into the next chapters on the various enterprise structures
used by Oracle Applications to create reporting and security hierarchies.
The questions continue in the next slide.

Common Application Discussion
• Security Structure
– What level of security and access is allowed?
– Are area or local managers and the people that report to them
secured to transactions within their own area of responsibility?
– Are the company transactions largely performed by a corporate
department or shared service center or within each local area?
• 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?

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

• Introduce the Oracle Fusion applications.
• Discuss Oracle Financials Cloud.
• Discuss your implementation strategy.
• Discuss the Common Financial Applications Configuration.
• Identify your implementation needs.

2
Introducing Oracle Fusion
Navigation

Objectives

• Navigate Oracle Fusion Applications.
• Explore dashboards.
• Examine panels.
• Review infolets and infotiles.

Getting Started in Oracle Fusion Applications
Oracle Fusion Applications are:

• Designed from the ground up, using the latest technology advances and incorporating
best practices gathered from thousands of customers.
• Completely open, service-enabled enterprise applications.
• Designed with features for the best-in-class user-interface designs and workflows that
optimize usability and deliver business value.
All functionality revolves around the Oracle Fusion Applications Welcome Springboard, which
can be personalized.
Note: The Welcome Springboard view changes based on your roles and privileges.

Simplified Navigation
Enhanced user interface features include: NEW

• Welcome Springboard
• Infolets
• Infotiles
• Panels
Example of Infolets
Oracle’s focus on providing an exceptional user experience pervades the Oracle Applications
Cloud. Creating a compelling, pleasing user interface that provides only what you need right
when you need it is of the highest priority. Advantages include:
• Detailed list of all the work areas that you have access to using the improved navigator.
• Logical, related tasks organized into groups and displayed in a pre-determined order set
by the application.
• Ability to configure tasks to meet your business needs.
• Access to work areas and dashboards by clicking on the icons on the Welcome
Springboard or from the Navigator entries.

New Welcome Springboard
• Quick glance at your work-related conversations and

announcements.
• Page control navigation located at the top of the pages to
access the Welcome Springboard and the infolet pages.
• Navigator to access additional applications.
Page Control
Dots
Navigate to: Welcome Springboard

• Improve efficiency and productivity of your workforce with the simplified Welcome
Springboard that is optimized for tables and mobile devices. Other features include:
• Use the page control dots that appears at the top of the Welcome Springboard to switch
between the that page and new infolet pages.
• Use the icons on the Welcome Springboard to easily access relevant work areas and
dashboards. Alternatively, use the Navigator to access any additional applications.
• Take advantage of the fact that no additional steps are required to enable the Welcome
Springboard.
• Maintain your personalization and customization of the home page in earlier releases,
which is preserved on My Dashboard.

Favorite and Recent Items
Navigate to: Welcome Springboard > Select the Favorites and Recent Items icon.
The Favorite and Recent Items menu enables users to return to flows that have been recently
accessed, usually within, but not limited to, a single session.

User Interface
Global Area
Panel
Tabs
Infotiles Area
Panel
Section
Navigate to: Payables > Invoices

Each page can be divided into components. The slide shows an example of the main
components in the Oracle Fusion User Interface.
• Global Area: Contains links to help you navigate user interfaces, personalized links and
tools, and the name of the user who is signed in.
• Infotiles Area: Contains infotiles that give you a quick glance as key performance
indicators and expand for more details.
• Section: Contains the transaction or form that requires creation, editing, or review.
• Panel: Contains links to tasks, process, and reports and enables search on some
panels.
• Panel Tabs: Opens several different panels including Tasks, Search, and Report panels.

Dashboards
Oracle Fusion dashboards provide:

• Information summaries: View of the big picture as well as
prioritization.
• Information monitoring: Quick action and further exploration.
• Information containers: Multiple regions, dashboards, graphs,
and other objects.
Navigate to: Collections > Collections Dashboard

Two types of dashboards are available:
• Role-based: Examples include General Accounting, Line Manager and Collector
dashboards.
• Business intelligence-driven: Examples include Balance Sheet and Sales Pipeline
dashboards.

General Accounting Dashboard
Navigate to: General Accounting Dashboard

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

Work Areas
Navigate to: General Accounting > Period Close

A work area is a grouping of similar tasks. The Period Close work area includes tasks for
opening and closing accounting periods for Oracle Fusion General Ledger and subledgers.

Panel
Click on the Tasks icons to open the Panel

Use the Panel tabs to:
• Access features without leaving the current application.
• Perform searches.
Tasks Panel Tab
• Run reports.
Tasks
Panel
Navigate to: Receivables > Billing

The panel, an anchored component on the right side of a page, contains one or more vertical
tabs to perform actions such as search, run reports, and view integrated conversations in the
context of the current task.
• Open the panel by clicking on one of the panel tabs. The panel is collapsed by default.
• Use the slide-out panel to access features directly from any screen without leaving the
current application or navigating through different roles or hierarchies.
• View the tasks available for your user role.

Search Panel Overview
Use the Search Panel to perform local searches on the work area
you are currently using.
Search Panel Tab
Search
Panel

Use the Search panel to perform a local search based on the work area you are currently
using. Click on the Search panel tab to expand the Search panel and perform a search.
For example, in the Billing work area, you can quickly search for a transaction by Transaction
Number, Transaction Date, or Bill-to Customer Account Number using the Search panel.

Reports and Analytics Panel
Use the Reports and Analytics panel to run any reports and
analytics available to your user role.
Report and
Analytics
Report Panel Tab Panel

Click on the Reports and Analytics panel tab to expand the panel and select reports and
analytics you want to view.

Practice 2-1 Overview: Getting Started in Oracle Fusion
Applications
This practice covers the following topics:
• Signing in to Oracle Fusion Applications.
• Exploring the following user interfaces:
– Global Area including:
— Accessibility
— Help
— Search
— Personalize
— Setting and Actions menu
— Navigator and Welcome Springboard
– Work Area and Panels
– Search
• Signing out of Oracle Fusion Applications.

Infolets versus Infotiles
NEW
Infolet
• An interactive container in a simplified user interface that
provides key information and user actions including:
– Refreshing and running processes to update the data.
– Drilling into the details behind the data.
– Changing the displayed views, names, and information.
• Infolets are combined on an Infolet Page that is accessed
using a page control dot on the Welcome Springboard.
Infotile
• A tile component that displays key information about a topic or
object as part of a scrolling strip of information tiles on a
specific page.
• Each tile links to a table of detailed information.

Infolets Overview
• Select the page control dot at the top of the Welcome

Springboard to view a specific infolet page.
• Use the dots to return to the Welcome Springboard.
• Use the arrow in the lower corner of the infolet to change
views.
• Click on the Actions menu in the top right corner of the infolet.
Page Control Dots

Use infolets to view information at a glance from different sources in an efficient and timely
way directly from the Welcome Springboard. You have the right information instead of just
more data to sift through.
Mobile device support is available to take your work on the go enabling you to close your
books quickly. You can spot trends and exceptions to gain insights about your financial
results in real-time.
Infolets are available for General Ledger, Intercompany, Budgetary Control, and Cash
Management.
Note: You can only view those infolets that you have permission to access.

Infolet Repository
• The Infolet Repository displays the infolets available for each

infolet dashboard.
Infolet Repository Icon
Navigate to: Welcome Springboard > General Accounting Infolets dot

The infolet repository displays the available set of infolets available based on your access
privileges.
• Click the Infolet Repository icon in the upper right hand corner or the page, then select
or deselect the infolets you want to use and drag and drop infolets in the order that you
want them displayed.
• Click the Actions menu in the upper right hand to view a list of actions that can be
performed for that infolet. The list varies by infolet. For example, actions:
- View the last updated date on when process ran.
- Run extracts.
- Refresh the view.
- Edit title and enable views
- Hide the infolet
• Use infolets to aggregate key information for a specific area, for example, your sales
pipeline, employee turnover, or other business transactions.

Subledger Infotiles Overview
Use infotiles to:

• Obtain detailed information from a single page.
• Orient yourself in intense, repetitive, and focused tasks.
Infotile Select
Tile
Navigate to: Payables > Invoices.

• Use infotiles to scan information across areas of interest.
• Navigate among infotiles to have related details are refreshed in the content area of the
page.
• Glance to see what is going on and then click the Select Tile arrow to open and scan the
details.
• Find infotiles on the Assets, Receivables, and Payables landing pages and the Billing or
the Expenses work areas.
Note: No additional steps are required to enable this feature.

Practice 2-2 Overview: Exploring Infolets and Infotiles

• Navigating to the General Accounting infolets.
• Navigate to the Payables infotiles.
Note: Sign in with Casey.Brown and your assigned password to
perform this practice.

Summary
In this lesson, you should have learned to:

• Navigate Oracle Fusion Applications.
• Explore dashboards.
• Examine panel drawers and panels.
• Review infolets and infotiles.

3
Introducing Functional Setup
Manager

Objectives

• Describe Oracle Fusion Functional Setup Manager.
• Browse and configure offerings and functional areas.
• Review the Oracle Fusion Financials offering.
• Review the reports associated with the Oracle Fusion
Financials offering.
• Create an implementation project.
• Explain setup data export and import

Overview of Functional Setup Manager
Functional Setup Manager is a one-stop planning-to-deployment

application that provides:
• Single interface.
• Guided processes.
• Configurability of the Oracle Fusion offerings.
• Predefined, guided task lists.
• Export and import capability.
• Set of comprehensive reports.
• A single interface for all of the setup and maintenance phases across the complete
implementation life cycle.
• Guided processes that facilitate navigating through planning, implementation,
deployment, and ongoing maintenance.
• Configurability of the Oracle Fusion offerings to mold the offerings to fit the business
needs.
• Predefined, guided task lists for full end-to-end visibility of all setup requirements, which
enable users to implement quickly what they need.
• Export and import capability to let enterprises set up one instance and move the setup
and task lists to other instances.
• Set of comprehensive reports to give full visibility to setup at any time.

Job Roles
The following job roles are required to access information within

Oracle Fusion Functional Setup Manager:
• Application Implementation Manager
• Application Implementation Consultant
Users with these roles can:

• Gather Requirements for the Implementation: Perform this task outside of Functional
Setup Manager. No setup activities are required in the Functional Setup Manager.
• Configure Offerings: Define the parameters of the implementation by selecting the
features to be implemented for each offering.
Note: Read-only functionality to a limited number of tasks can be accessed even if these roles
are not assigned.

Implementation Objects Overview
Different types of implementation objects are available.

• Setup objects
• Business objects
Setup objects include:

• Offerings and functional areas
• Processes and features
• Tasks and task lists
Business objects include:
• Business documents such as person documents and purchase orders.
• Transactions such as invoices, payments, and journals.

Setup Objects
• Encompass multiple setup entities:

– Business objects
– Tasks and task lists
– Processes
– Features
– Functional areas and offerings
• Consume all offerings applicable to your implementation.
• Exist for the Oracle Fusion Applications
• Cannot be modified.
A setup business object is a self-contained representation of a business entity supported by a

setup task. These are logical representations of real-world objects. Setup business objects
represent the data entered when you perform setup tasks. Setup data entered by way of a
setup task is stored in the table associated with the corresponding business object. For
example, Primary Ledger is the business object of the setup task called Manage Primary
Ledger. When the Manage Primary Ledger task is performed, data entered is stored in the
tables associated with the Primary Ledger business object. You can:
• Create custom setup objects for use with third-party or custom applications.
• Create new offerings, features, and task lists using setup objects delivered with the
system.

Business Objects
• Consist of collections of the logical entities that make up a

complete business document, transaction, or other
high-level business concept.
• Comprise a set of attributes and a set of methods.
– Attributes store the data related to the entity you are modeling.
– Methods manipulate the value of these attributes, or perform
calculations based on their values.
• Are used as the lowest level for data export and import.
Business objects enable you to model and develop the business entities that are part of your
process.
Using business objects simplifies the management of the data in your process by
encapsulating the data and business behavior associated with the business entity it
represents.
Typically business objects represent entities in an actual business, but you can also use them
to encapsulate business logic that is not associated with any particular entity.
A Financial example of a business object is a Payables invoice which has the following
business entities:
• Supplier
• Invoice Header
• Invoice Lines
• Distributions

Offerings
The two predefined financial implementation offerings are:

• Oracle Fusion Financials offering: Includes Oracle Fusion
General Ledger and Oracle Fusion Subledger Accounting
application features, as well as at least one of the subledger
financial applications.
• Oracle Fusion Accounting Hub offering: Includes Oracle
Fusion General Ledger and Oracle Fusion Subledger
Accounting application features integrated with an existing
enterprise resource planning (ERP) system or third-party
application to enhance the current reporting and analysis.
***The focus of this course is the Oracle

Fusion Financials Offering***

Offerings, Functional Areas, and Features
The decision tree for the implementation of specific business

processes is represented by selecting:
• Offerings
• Functional areas
• Features
• Offerings contain all of the tasks required to implement the top-level business process.
• Functional areas are logical groupings in an offering that you can choose to implement
during an implementation.
• Features are used to define the business rules for the implementation and how the
transactions of the corresponding business process work. Features are available in
offerings, functional areas, or other features.

Offerings, Functional Areas, and Features: Example
As shown here:
• The offering is Oracle Fusion Financials.
• A functional area in that offering is Expenses.
• An feature the Expenses Functional Area is Corporate Card with Expenses. The feature
includes the business rules that define how the corporate card with expense works.
Selecting the combination of offerings, functional areas, and features generates the
appropriate task list dynamically.

Offerings
Navigator > Setup and Maintenance

Offerings Section:
• Select from the drop down list to view all or only Provisioned offerings. The offerings are
displayed in alphabetical order.
• Use the scroll bar under the icons to move quickly through the offerings.
About and Administration sections: Both are updated and provide links based on the offering
selected.
• About <Name of the offering>: Provides links to documentation that assists with the
setup of your implementation.
• Administration: Provides the Configure button which changes to the Actions and Setup
buttons after you finish configuring the offering.
- To change the configuration, use the Actions button.
- To view or perform other tasks for the configuration, use the Setup button.

About Financials: Overview
• Provides an offering description.

• Lists reports:
– With detailed information about what type of transactions and
functionality are available within the offerings.
– Available in HTML, PDF, and Excel formats.
Navigate to: Setup and Maintenance > About Financials

• Offering Content Guide
- Describes the detailed contents of the offering for the current version of the
application.
- Provides a functional description of the components of the offering.
• Associated Features
- Displays the functional areas and features for the offering used for detailed
application configuration decisions.
- Displays a list of features available with the offering, including what level the
feature is associated with, as well as the choices available.
- Depicts the dependency between the offerings and their features.
• Setup Task Lists and Tasks
- Lists the setup tasks and task lists for an offering and functional area, related to
application configuration.
- Displays the setup tasks required to implement the functionality available in the
offering.

• Related Business Objects
- Lists the business objects that the offering uses.
- Lists the applicable web service used for the export and import process.
• Related Enterprise Applications
- Lists the enterprise applications the offering requires for functional setup and
transactional tasks.
- Specifies the application required based on transaction type for special offerings.

Practice 3-1 Overview: Browsing Offerings
This practice covers exploring the following components:

• Setup and Maintenance page
• About section reports:
– Offering Content Guide
– Setup Task Lists and Tasks
– Related Business Objects
– Related Enterprise Applications
• Tasks panel
Specifically look at the Setup Task Lists and Tasks in the HTML format. Filter the required
versus the nonrequired setups.

Configuring Offerings
• Review all of the available offerings, functional areas, and

appropriate reports.
• Select the offerings, functional areas, and features to be
implemented.
– If an offering is selected, but none of its features, only the basic
tasks needed to implement the base functionality are included
in the task list.
– Only the offerings and features selected during this process are
available when an implementation project is created.
– Configured offerings can be updated at a later date, particularly
if offerings are implemented with a phased approach.
Features are associated with some offering. Each feature provides two or more choices. The
valid selection types for choices are:
• Yes or No: Indicates to include or to exclude functionality.
• Single Choice: Choices are mutually exclusive.
• Multiple Choices: More than one choice can be selected.
Note: Additional features may appear if any dependency has been defined and the
corresponding feature choice has been selected.

Demonstration 3-2 Overview: Configuring Offerings
This demonstration covers the following topics:

• Reviewing the Configure Offerings page.
• Expanding the offering to see the financial features.
• Viewing the Setup Tasks page.

Implementation Task Flow
The Implement Applications process includes some activities that are manual and performed
outside of the Oracle Fusion Functional Setup Manager application.
• Plan is the process of gathering business requirements and comparing them to the
offerings available to determine what to implement.
• Install is not addressed directly with Oracle Fusion Functional Setup Manager. The
installation of the applications and instances is done for on-premises installs before the
functional setup. Install is already completed for cloud implementations.
• Configure is the process of selecting the offerings, and features to implement. The
selections made during the configure process dynamically determine the task lists for
implementation.
• Implement covers both the management and functional user aspects of assigning tasks
and due dates, as well as completing setup tasks and reporting status.
• Export enables you to export the configuration setup data from one environment in order
to import the configuration into another environment in the same or a higher release.
• Transact is the transaction processing done within the actual product, such as Payables.
• Maintain is the process that enables you to search for tasks or task lists to perform
maintenance of setup tasks from a single user interface

Implementation Project: Overview
An implementation project:
• Uses the Setup and Maintenance work area in Oracle Fusion
Functional Setup Manager.
• Starts the creation of your enterprise and its structures.
• Defines the scope of the implementation.
• Is populated by adding one or more related offerings or task
lists.
• Provides progress reports on tasks that can be seen on the
Implementation Projects tab.
Detailed status on your implementation project can be seen by:

• Clicking the numbers in the Assigned Tasks column.
• Drilling down to the Implementation Project detail graphical reports in the project details
region.

Assign Tasks
After you create your implementation project:

• Assign tasks to users by using the Assign Tasks button in the
implementation project.
• Assign and store notes associated with the task list or task as
attachments.
• Review, add, or delete users in the Assigned Users region.
Navigate to: Setup and Maintenance > Implementations > Manage Implementation Projects >
Fin Implementation > Expand to specific task and select row header > Assign Tasks.
You can assign tasks either by:
• Assigning the same users and due dates to all tasks in a task list.
• Assigning individual tasks to a specific user.

Rapid Implementation Task List
Define Common Financials Configuration for Rapid

Implementation
• Manage Geographies
• Create Chart of Accounts, Ledger, Legal Entities, and
Business Units in Spreadsheet
• Upload Chart of Account
• Upload Ledger, Legal Entities, and Business units.
• Create Cross-Validation Rules in Spreadsheet
• Create Banks, Branches, and Accounts
• Manage Tax Regimes
• Run Jurisdiction and Rates Upload Program
• Manage Taxes
Navigate to: Setup and Maintenance

For fast, efficient implementations, add the Define Financials Configuration for Rapid
implementation task list. These task lists consist of the required tasks for your implementation
including spreadsheet loaders to ease data input.

Financials Task Lists
• Define Common Applications Configuration for Financials.

• Define Common Financials Configuration.
• Define Invoicing and Payments Configuration.
• Define Receivables Configuration.
• Define Expense Configuration.
• Define Fixed Assets Configuration.
• Define Collections.
• Define and Maintain Intercompany Processing Rules.
• Define Hyperion Financial Management Integration.
• Define Budget Configuration.
• Define Financial Reporting.
• Define Transactional Business Intelligence Configuration.
To implement optional and more advanced features use the Financials task lists. The task
lists are arranged in the order in which the tasks need to be completed.
Note: Some of these tasks are covered in the other Oracle Financials Cloud courses.

Practice 3-3 Overview: Creating an Implementation
Project
• Creating an implementation project.
• Including Financials and its nested offerings.
• Adding Financial Configuration for the Rapid Implementation
task list.

Implementation Project for Ongoing Maintenance
• Maintenance activities are generally performed after the

applications are implemented.
• You can create a new ongoing maintenance implementation
project in one of two ways:
– Do not select an offering. Add the required task lists or tasks to
the implementation project.
– Select an offering and delete the task lists or
tasks that are not required.
• Use Scope to simplify ongoing maintenance on a task list.
Navigate to: Setup and Maintenance > Tasks > Implementation > Manage Implementation
Projects.
Consider defining an ongoing maintenance implementation project that includes tasks such
as:
• Manage Daily Rates
• Manage Calendars
Note: Scope, as used in Oracle Fusion Functional Setup Manager, refers to an object that
allows a task list to be performed repeatedly. An example of a scope value is Business Unit,
for which you select a particular business unit and proceed to perform all setup tasks for that
business unit.

Setup Data Export and Import: Overview
Setup data can be exported and imported for either:

• An entire offering.
• Any of an offerings functional areas.
Almost all Oracle Fusion application implementations require moving functional setup data
from one instance into another at various points in the life cycle of the applications.
For example, an enterprise application implementation is first implemented in a development
or test application instance and then deploy to a production application instance after
thorough testing.
You can move functional setup configurations of applications from one application instance
into another by exporting and importing setup data.

Offering Based Export
Export: The export definition includes setup data:

• For an offering: All enabled functional areas and relevant
features.
• For a single functional area: That functional area and relevant
features.
Note: Once you initiate the export process, you can:
• Monitor export’s progress
• Check the export’s status from the Export Offering Data
History page.
Advantages:
• Helps easily move your implementation or configuration across instances.
• Does not require selecting tasks or understanding data relationships to ensure only
setup data relevant to the selected offering or functional area is exported.
• Gives you flexibility to filter the setup data as needed for specific offerings or functional
areas.
Note: Some objects are not import through configuration packages including:
• Application Menu Customization
• Trading Community Geography
• File Common Import Object or Attribute
• File Import Object, Mapping Column, or Activity
• Users
• Application General Preferences
• Procurement Browse Category or Tree
• Suppliers, Supplier Match Party Relationship. Role, News, or Notification Configuration

Offering Based Import
Import: A configuration package created by the export process is

uploaded. You can:
• Initiate the setup data import from the importing environment.
• Monitor the import’s progress.
• Check the import’s status from the Import Offering Data
History page.
Points to consider:
• Offerings must be enabled before import.
• Import options must match the export file options.
• Limited validation is performed before the import is proceed.
• Notification of data that must be loaded manually is sent. You can enter the data and
resume the process.
• Notification of errors are sent. You can correct the error or skip the option.

Offering Based Export and Import Process
Navigate to: Setup and Maintenance > Financials Offering > Setup button > Export button >
Create New Export.
Select the offering (1) or functional area (2) you want to export or import setup data for, and
then select Export or Import action.
• Selecting Export for either a functional area or offering invokes the Export Offering
Setup Data page where you create an export process for the offering or functional area
you want to export.
• Selecting Import (3) on the Actions button drop down list invokes the Import Offering
Setup Data page where you can upload and import previously exported setup data.

Additional Information on Oracle Help Center
Use these videos found under the Videos link on the Oracle Help
Center Financials page to learn more about FSM.
Link to the Oracle Help Center Financials page:

http://docs.oracle.com/cloud/latest/financialscs_gs/index.html

Summary

• Describe Oracle Fusion Functional Setup Manager.
• Browse and configure offerings and functional areas.
• Review the Oracle Fusion Financials offering.
• Review the reports associated with the Oracle Fusion
Financials offering.
• Create an implementation project.
• Explain setup data export and import

4
Overview of Security

Objectives

• Understand the Cloud security methodology.
• Plan your use of the security implementation.
• Identify the components of function and data security and
tasks associated with these components.
• Discuss how roles can be assigned automatically or manually
to users.
• Explore the new Security Console to manage user security.
• Review the audit reports and resources.

Oracle Financial Cloud Security Methodology
Cloud security methodology can be summarized with the simple

statement: “WHO can do WHAT on WHICH set of data.”
• Who: The user.
• What: Individual actions a user can perform.
• Which: The set of data.
Who What Which Data

General Accountant Enter and post UK Ledger
journals
General Accounting Creates and runs UK Ledger
Manager reports
• Who: The user who performs functions in your company, such as an General
Accountant.
• What: Individual actions a user can perform, such as the ability to enter and post
journals.
• Which: The set of data that the user can perform the action on, such as general ledger
journals with in your assigned ledger.

Security Reference Implementation
Oracle Financials Cloud comes with a predefined security

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

Points to Consider When Implementing the First Project
• Define at least one implementation user using the Create

Implementation Users task at the beginning of the project.
• After Implementing the First Project consider:
– Data Access Sets: Define read and write access to entire GL
ledgers and balancing segment (company) values of ledgers.
– Segment Value Security: Controls access to individual segment
values in your chart of accounts such as no access to
Company 01, Dept. 100, or Salaries account.
Co CC Acct I/C
The first implementation user is for creating only the initial enterprise structure and is not a
real person in HCM. After the initial enterprise structure is complete, you can create additional
users in HCM using the Manage Users or Import Worker Users tasks. Your users require that
a business unit, legal entity, and other setup be added after the initial implementation.
Planning is essential:
• Analyze the access requirements specific to your organization, understanding who
needs access to what.
• Compare the requirements with the predefined roles in the security reference
implementation, and decide which predefined roles meet your requirements and can be
used as-shipped, and which will require customizations to meet your requirements.
• Certain product areas, such as Accounts Payable and General Ledger, include multiple
roles in the reference implementation. To compare accesses granted to each role, you
can use the Compare Role feature in the Security Console.

For On-Premises Implementations Only
The Oracle Fusion Applications super user FAADMIN, by default, has all necessary access
rights for implementing Oracle Fusion HCM and administering security. This access is
provided by the following job roles:
• Application Implementation Consultant
• IT Security Manager
However, neither of these roles provides the required access for creating and managing
Oracle Fusion Applications users; therefore, the OIM system administrator must add the
following two OIM roles to the IT Security Manager job role:
• Identity User Administrator, which carries user management entitlement.
• Role Administrator, which carries role management entitlement.
Note: Assign the Xellerate Users organization to the IT Security Manager.

Function and Data Security
Oracle Financials Cloud uses role-based access control (RBAC).

• Your application is secure as delivered.
• You give function and data access through roles that you
assign to users.
• Function security allows you to access:
– A page or a specific object.
– Functionality within a page, including services, screens, and
task flows.
• Data security consists of privileges conditionally granted as:
– Data security policies carried by roles.
– Human Capital Management (HCM) security profiles.
For example, a job role can enable users to work with journals. A data role in an upgraded
implementation that inherits the job role can provide access to the journal data within a ledger.
The data role General Accounting Manager – US inherits functionality from the General
Accounting Manager job role and it enables users to perform general ledger duties in the US
ledger.
Note: New implementations assigns users directly to the job roles and to the appropriate data
sets instead of using role templates.

New Data Security for R11
NEW
Applicable to new customers only.
• Does not use data role templates
• Assigns users directly to the job roles and to the appropriate
data sets.
• Uses the new Manage Data Access for Users page.
Existing customers upgrading from previous releases:
• Continue to utilize the old data role based model for their data
security implementation.
• Assign specific data sets, such as business units, ledgers,
warehouses, and so on.
• Use data roles that were automatically generated by data role
templates.
To access the Manage Data Access for Users page, navigate to Setup and Maintenance >
Manage Data Access for Users task.

Assigning Data Scopes to Users for New Customers
Only
Use the Manage Data Access for Users task to assign users to
data scopes.
• Assign data scopes to users by provisioned role.
• Use the import capability to create a large number of
assignments.
NEW
You use the Manage Data Access for Users task to assign users to data scopes, like
Business Units, Ledgers, and Asset Books. You can access this task from the Setup and
Maintenance work area.
You assign data scopes to users by role, and you can only assign data scopes to roles a user
has been provisioned.
You can also import assignments from a spreadsheet. By clicking on the Authorize Data
Access button in the Manage Data Access page, you can download a spreadsheet which you
can use to import the data assignments. You can prepare the data from another source, such
as your legacy system, and populate the spreadsheet, then import.

Types of Roles
Three role types can be assigned to users. These enterprise

roles, also called external roles, are:
• Enterprise Job roles: Represent jobs that users perform in an
organization, such as Accounts Payable Manager.
• Abstract roles: Represent people in the organization
independent of the jobs they perform, such as employee or
line manager.
• Duty role: Logical collection of privileges that grant access to
tasks that someone performs as part of a job, such as
processing payables invoices or posting journals.
Assign these roles directly to users:

• Job roles: You can also create custom job roles.
• Abstract roles: All users are likely to have at least one abstract role that provides access
to a set of standard functions, such as expense reporting or procurement. You can also
create custom abstract roles. In addition, the Employee role is important to assign to a
user as it allows users to submit ESS jobs, among other general functions that an
employee would have.
Assign these roles to Job and Abstract roles, not directly to users:
• Duty roles: You can also create custom duty roles.

Role Inheritance
Role inheritance is a key concept in the security model. The figure illustrates the hierarchy of
job and duty role inheritance which are used as the building blocks in Oracle Cloud Security.
• Almost every role is a hierarchy or collection of other roles.
- Job and abstract roles inherit duty roles.
- Duty roles can inherit other duty roles.
• You can also assign privileges directly to job, abstract, and duty roles.

Security Example with Data Role Added
For upgrading implementations, the diagram now shows Data Role added to secure Anita
Kennedy to the UK Set of Data in the UK Ledger for her General Accountant Job role.
Note: New implementations assigns users directly to the job roles and to the appropriate data
sets instead of using role templates.

Oracle Identity Manager
Operates in three modes

• Self-Service: You can manage your own roles and privileges.
• Delegated Administration: You manage the roles and
privileges of other users.
• Advanced Administration: You can manage password policies
and do other system administrative functions.
• Oracle Identity Manager (OIM) access is granted to the predefined IT Security Manager
role.
• Use Administration Mode in OIM to create users and provision roles. OIM opens by
default to the self-service view.
- The title displays whether you are in Administration mode or Self Service mode.
- To switch from Self-Service Mode to Administration Mode, click on the button in
the upper right hand corner.

Creating Users
• If you are not implementing Human Capital Management

(HCM) use the Manage Users task to create users. The
Manage Users task creates a minimal person record and a
user account
• If you are implementing HCM, use the Hire an Employee task
to create users instead. Hire an Employee task creates the full
person record as well as the user account
• Use the Create Implementation Users task to create
implementation users without associating a person record.
• Use a spreadsheet to import users from legacy applications to
Oracle Financials Cloud using the Import Worker Users task.
Access the tasks above:

• Create Users: Navigate to: Setup and Maintenance > Manage Users > Create icon or on
the Navigator > My Team > Manage Users > Create icon.
• Hire an Employee: On the Navigator > My Workforce > New Person > Tasks panel >
Hire an Employee. This task creates the full person record needed by HCM, such as job
assignment, job code, department, manager, etc, as well as the user account itself.
• Create Implementation Users: Navigate to: Setup and Maintenance > Create
Implementation Users > Administration tab > Create User icon.
• Import Worker Users: Navigate to: Setup and Maintenance Import Worker Users >
Create Worker > Create Spreadsheet icon or on the Navigator > My Workforce > Data
Exchange > Tasks panel > Initiate Spreadsheet Load > Create Worker > Create
Spreadsheet icon.
Note: The import process handles both user account creation and auto provisioning of roles.

Role Provisioning Tasks
Roles can be provisioned (assigned) to users:

• Manually provision roles to users using Oracle Identity
Manager.
• Automatically provision a role to users by defining a
relationship, called a role mapping, between the role and
some conditions.
To manually provision roles, use the Create Implementation Users task from Setup and
Maintenance to access Oracle Identity Manager. Make sure you switch to Administration
mode to assign roles to users.
• To assign a role to a specific user:
- Use the search box to search for the desired user.
- Open the user and go to the Roles tab.
- Click the Assign button to assign new roles to the user.
• To assign the same role to multiple users:
- Search for the role.
- Go to the Members tab
- Click the Assign button to assign multiple users to the same role.
Roles are automatically provisioned when one of the user's assignments matches all role-
mapping conditions and the auto provision option is selected.

Using Role Mappings
Create and manage role mapping rules.

• Use the Manage Role Provisioning Rules task to create and
manage role mapping rules.
• If HCM is implemented, use the Manage HCM Role
Provisioning Rules task instead.
Set a role attached to a role mapping role to: :
• Requestable: Qualifying users can provision roles manually to
other users.
• Self-requestable: Users can request the role for themselves.
• Auto-provision: The system will automatically assign roles to
users when they meet all the conditions in the role mapping.
This provision the role to all users who do not already have
the role assigned.
Role Mappings allow you to automatically assign roles to users if they match the conditions
specified in the Role Mappings. As users transfer departments or change jobs, the Role
Mappings can automatically assign the correct roles to the users.
Each role mapping rule is based on a set of attributes that can be matched to a user’s
assignment, such as Department, Job, and Location. For example, you may define a rule that
limits role mapping to current employees of the Finance Department whose Job is Accounting
Manager.
Roles capture the nature of work intended to be performed by the user.
• A range of security roles are granted to the new user.
• This enables users to access application flows that are crucial for performing the tasks..
For example, you may define a rule that limits role mapping to current employees of the
Finance Department whose job is Accounting Manager.
When the list of assigned security roles is populated, you can remove or add new roles as
needed.
Note: Auto-provision: Deprovisions roles immediately from users who are no longer eligible
for roles that they currently have.

Practice 4-1 to 4-3 Overview: Using User Security
These practices cover the following topics:

• Practice 4-1: Defining role mapping.
• Practice 4 -2: Creating a user.
• Practice 4-3: Creating an employee.

Customizing Roles
If jobs exist in your enterprise that aren't represented in the

security reference implementation:
• Create custom job roles by copying existing roles.
• Add duty roles and privileges to custom job roles.
If the privileges for a predefined job role don't match the
corresponding job in your enterprise:
• Create custom job roles by copying existing roles.
• Add or remove duty roles, function security privileges, and
data security policies.
Best Practices for Customizing Roles

• Do not customize predefined roles. These predefined roles begin with the ORA_ prefix
in the Role Code field. During each upgrade, the upgrade process updates the
predefined roles to the specifications for that release, so any customizations are
overwritten.
• Always make a copy of the predefined role. Then, edit the copy and save it as a custom
role.
• Compare the copy of the predefined role with the new customized role and roll back to
the delivered role, if necessary.
• After a maintenance update or upgrade, compare your customized copy to the updated
predefined source role. You can see the updates to the predefined role and decide
whether to incorporate those changes into your custom role.

The Security Console
• Use to customize security.

• Create and edit custom roles, but not predefined roles.
• Can be accessed via the Navigator menu, under Tools.
• Access granted through the IT Security Manager role.
Before you start using Security Console, set two profile options that govern the behavior of
the Security Console in the Manage Administrator Profile Values task.
• Security Console Working App Stripe: Controls the App Stripe the user works on.
Please set this profile option to fscm, either at the site level, or for specific users with
Security Console access.
• Enable Data Security Policies and User Membership Edits: Sets the preference to
enable data security policies and user membership editing in Security Console. Set this
profile option to Yes to enable both, at the site level, or for specific users.

The Security Console: Copy Feature
The copy feature steps are:

• Copy a role.
• Modify the default role name, code, description.
• Review, add, or remove function security privileges.
• Review, edit, or remove data security policies.
• Review, add, or remove inherited roles.
• Assign users to the target role.
• Review the summary and impact.
• Submit and Close.
The Copy feature in the Security Console enables you to:

• Set up default names in the Preferences section of the Security Console.
• Review the code resources tied to each function security privilege.
Important:
• To add, edit, or remove data security policies, set the profile option Enable Data Security
Policies and User Membership Edits to Yes, either at the site level or for the current
user.
• To assign users to this new role, set the profile option Enable Data Security Policies and
User Membership Edits to Yes, either at the site level or for the current user..
Note: This option is only available to external roles, as you can only assign external roles to
users.

The Security Console: Compare Roles Feature
• Use to compare the function and data security policies

granted between two roles.
• Launch Compare Roles directly by clicking on the button or by
choosing the Compare Roles option in the Search Results.
View:
• All comparison results.
• Artifacts that only exist in either the first or the second role.
• Artifacts that exist in both roles.
Choose to view only comparison results for:
• Function security policies.
• Data security policies
• Inherited roles, or combinations.

Additional Features
Use the icons on the left hand side of the page to:
• Roles: Copy, create, and compare roles.
• Analytics: Examine statistical data on roles.
• Certificates: Review Certificates.
• Administration: Save Preferences.

Practice 4-4 Overview: Using the Security Console

• Copying a role.
• Comparing a role.

Auditing Security
The following audit reports are available:

• User Role Membership Report: List of users and provisioned
roles.
• User and Role Access Audit Report: List of users and
provisioned function and data accesses
• Inactive Users Report: List of inactive users.
User Role Membership Report: You can run the report for all users, or you can optionally filter
the list of users by name, department, and location.
User and Role Access Audit Report: Report can be run for one user, all users, one role or all
roles.
• One User / All Users
- Separate report outputs show role hierarchy with privileges, tabular listing of
privileges, and list of data security policies provisioned to the user.
- All Users option results in one set of reports for each user
• One Role / All Roles
- Separate report outputs show role hierarchy with privileges, tabular listing of
privileges, and list of data security policies for given role
- All Roles option results in one set of reports for each role

Inactive Users Report: Use this report to identify users who have not signed in for a period of
time that you define.
• Run the Import User Login History process as a prerequisite
• Provide the inactivity period, in days as a report parameter. The default is 30.
• Optionally filter the list of users by name, department, location, and last activity date.
• Shows all inactive users that match the criteria and the following data:
- Number of days that the user has been inactive
- User’s username
- Given name
- Surname
- Location and department
- User’s status

Security Resources
To review the roles and other components that make up the

security reference implementation for your application, you can:
• Access the security reference manuals (SRM).
– Common
– Service-specific
• Access the tasks available for managing roles, templates, and
security policies.
Security
Securing Oracle Reference for
ERP Cloud Oracle
Financials Cloud
Security Reference
for Common
Features
Oracle Financial Security is applicable to the needs of midsized, horizontal enterprises

generally between 250 and 10,000 employees. It can be changed or scaled to accommodate
expansion into vertical industries such as health care, insurance, automobiles, or food
manufacturing.
For more resources on the Oracle Help Center, see:
• Oracle Financial Security Guides:
http://docs.oracle.com/cloud/latest/financialscs_gs/docs.htm.
• Oracle Fusion Middleware Security Guides:
http://docs.oracle.com/middleware/1221/cross/securedocs.htm

Summary

• Understand the Cloud security methodology.
• Plan your use of the security implementation.
• Identify the components of data security and tasks associated
with these components.
• Discuss how roles can be assigned automatically or manually
to users.
• Explore the new Security Console to customize users.
• Review the audit reports and resources.

5
Discussing the Vision Story and
Common Applications

Objectives

• Discuss the Vision Corporation Story elements.
• Explore geography:
– Structure
– Hierarchy
– Validation

Overview
The Oracle Fusion Financials Implementation course is based on

a fictional yet realistic enterprise that:
• Combines the common aspects of your enterprise structure.
• Is used to explore and implement objects during class.
Navigate to: Setup and Maintenance > Manage Enterprise HCM Information.

Scenario
• Your company, Vision Corporation, is a multinational

conglomerate that operates primarily in the United States (US)
and the United Kingdom (UK). The focus of this class is on the
operations in these two countries.
• Vision Corporation has recently expanded their operations to
China and France. In the future, you expand to other countries
in Europe and around the world.
• Vision Corporation has purchased an Oracle Fusion
Applications solution including Oracle Fusion General Ledger
and all of the Oracle Fusion subledgers.
• Vision Corporation has 400 plus employees and revenue of
$120 million.
Note: The Vision Corporation story is used to demonstrate and teach the functionality in
Oracle Fusion Applications to customers around the globe and does not necessarily represent
a real-world implementation.

Scenario Details
• Your product line includes high technology products.

• You have two distribution centers and four warehouses that
share a common item master in the US, UK, and France.
• You are leading the Enterprise Structure team for your
implementation project and are designing the model for your
global enterprise structure including your US, UK, and France
operations.
Ready Set Go!!
Consider the following elements in creating your model for your global enterprise structure.
• Your company is required to report using US GAAP Practices, UK Statements of
Standard Accounting Practice, and International Financial Reporting Standards (IFRS).
• Your managers need reports that show profit and loss for their lines of business.
• Your corporate managers require reports showing total organizational performance with
drill-down capability.
• Your company has all administrative, accounts payable, procurement, accounts
receivable, billing, and human resources functions performed at your corporate
headquarters.

Vision Corporation Analysis
Questions and decisions that need to be addressed before

implementation starts:
• How many and what type of ledgers (primary, secondary, or
reporting) do you need to achieve proper statutory reporting?
• Do you use business units and balancing segments to
represent your divisions and businesses?
• Do you need to secure your chart of accounts segment values
to prevent unauthorized use and access to those values
during transaction entry or reporting?
• Do you need multiple balancing segments to achieve fully
balanced balance sheets across more than one segment?

Vision Corporation Analysis
• Do you need one or more business units in which to perform

all your business functions?
• Do you have a procurement shared-service center to process
requisitions and negotiate supplier terms for your other
business units across your enterprise?
• What other aspects of your business affect your enterprise
structure?

Vision Corporation Structure Diagram
This is the model that your team has designed. The model uses numerical values to provide a
sample representation of your structure. The model includes the following recommendations:
Create three separate primary ledgers representing your separate legal entities.
• Vision North America Inc.
• Vision France Inc.
• Vision United Kingdom Ltd.
Consolidate results for your high technology business across the enterprise in a corporate
consolidation ledger.
Process all US, UK, and France general and administrative costs processed by the Shared
Service Center Corporate Business Unit.

Demonstration Solution Services instance with the following limitations:
• Due to space, only some of the Vision Corporation entities are shown.
• This version of the demo environment does not include a shared service center. The
one shown here is for discussion purposes.
• This version of the demo environment has data loaded only for US1 LE1 and US1 BU.

Vision Corporation Enterprise Structure
Entity Type Entity Name Legal Entity BSV Ledger/Currency

Enterprise Vision Yes 999 Consolidation Ledger
Corporation Currency USD
Division Vision North No 100 No
America
Company Vision US Inc. Yes 101 US Primary Ledger
LE1 Currency USD
Company Vision US Inc. Yes 102 US Primary Ledger
LE2 Currency USD
Division Vision EMEA No 300 No
Company Vision France Yes 311 France Primary Ledger

Inc. Currency EUR
Company Vision United Yes 303 UK Primary Ledger
Kingdom Ltd. Currency GBP
The chart in the slide illustrates the enterprise structure of your Vision Corporation entities.
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 required. Optionally they can be 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.
• At least one ledger is required in an implementation in which you record your accounting
transactions.
• Divisions are optional and can be represented with a hierarchy of cost centers or by a
second balancing segment value.

Vision Corporation Business Unit and Department
Structure
Entity Name Legal Entity Value
US1 BU US 1 LE 1 BSV 101
US 2 BU US 1 LE 2 BSV 102
France BU France BSV 311
UK BU United Kingdom BSV 303

Corporate BU
Vision Corporation BSV 103*
Shared Service Center
Payables Department All Entities Cost Center 723
The chart in the slide illustrates the business unit structure of your Vision Corporation entities.
The following statements expand on the data in the chart.
• Business units are required because financial and other transactions are processed and
secured by business units. Business units link to a default LE, but can perform business
functions for multiple LEs if those LEs share the same ledger.
• A shared service center to perform the Procurement business function, including
processing requisitions and negotiating supplier terms, is optional. If used, the shared
service center must be a business unit. *The assigned BSV of 103 is only for this
example and does not exist in the Vision demo database.
• Divisions are optional and can be represented with a hierarchy of cost centers or by a
second balancing segment value.
Note: Departments or cost centers are required because they track your employees and are
used in Oracle Fusion Assets and Oracle Fusion Expenses.

Vision Corporation Distribution Structure
Entity Type Entity Name Distribution

Structure
Distribution Center US Distribution Inventory
Center Organization
Warehouse Seattle Inventory
Organization
Warehouse Atlanta Inventory
Organization
Distribution Center EMEA Distribution Inventory
Center Organization
Warehouse Bristol Inventory
Organization
Warehouse Marseille Inventory
Organization
List of Items Common Item Item Master
Master Organization
The chart illustrates the distribution structure of your Vision Corporation entities. The following
statements expand on the data in the chart.
• Distribution centers and warehouses are used to receive and ship the high tech
products your firm sells.
• Item master organization and inventory organizations can be added if you are tracking
your inventory transactions in Oracle Fusion Applications.

Vision Corporation Chart of Accounts Summary
The chart of accounts structure above shows the names of the segments and the default
values that your team is proposing for Vision Corporation's three primary ledgers.
Sample Accounts:
• Vision US 101.10.11200.000.000.000 Cash Account
• Vision France 311.30.101000.000.000.000 Capital Account
• Vision UK 303.30.1100.000.000.000 Cash Account
Note: Each segment of the sample accounts corresponds to the segments listed in the boxes
below. For example, 101.10.12190.000.000.000 stands for:
Company 101, LOB (Line of Business) 10, Account 11210, Cost Center 000, Product 000,
Intercompany 000.

Define Geographies
Use the Define Geographies

task list to create and manage
geographies used for real-time
address validation and tax
calculation.
Navigate to: Setup and Maintenance > Define Geographies.

Managing geographies comprises:
• Geography structures.
• Geography hierarchies.
• Geography validations.
• Address cleansing.
• Geocoding process.

Geographies: Overview
Geographical information is a critical asset that defines and

monitors where and how you do business. You need to:
• Structure and create geographical information associated with
your business when you first set up Oracle Fusion
Applications.
• Use this information to facilitate business processes that rely
on geographical data. For instance, you need geographical
information to:
– Validate addresses
– Calculate taxes
– Create sales territories
All your geographical information is centrally located and shared
with other application offerings within your company.
Oracle Fusion comes with predefined country names. You need to define the geography
structure and hierarchy of each country associated with your business before working on any
process that requires geographical data. You can do this by either importing geography data
or setting it up manually.

Geography Structure
• Geography: A boundary such as a country, state, province, or

city.
• Geography Type: A divisional grouping of geographies.
– Geopolitical, for example, city, province, and district.
– Physical, for example, island and mountain.
• Geography structure defines:
– The hierarchy of the geography types or levels.
– How geography types relate to each other for a given
geography.
Country Top level
State Middle level
City Bottom level
A country’s geography structure determines the component geography types that can be
defined and the hierarchical relationship between them. A set of predefined geography types
is available for inclusion in a country's geography structure. Additionally, you can create a
geography type to add it to the country structure. Each geography type is added below the
current lowest level. You cannot delete a geography type that has related geography data.
Oracle recommends that you plan the geography structure before creating it. Also, if you want
to delete a geography type that is not at the lowest level in the country structure, then you
must delete the geography type level and all the levels below it.
For example, the geography structure for the United States comprises the State, County, City,
and Zip Code geography types. In the United States geography structure, the State
geography type is the highest level within the country geography structure, followed by the
County as the second level, City as the third level, and Postal Code as the lowest level within
the country structure.
You can define a geography structure in two ways:
• Create the geography structure using the Manage Geographies pages.
• Import the geography structure from a source file or using interface tables.

Geography Hierarchy
The geography hierarchy establishes a conceptual parent/child

relationship between geographies.
For example, in the US geography hierarchy the state of
California is defined as the parent of San Mateo County:
• Which is the parent of Redwood City.
• Which is the parent of the zip code 94065.
Based on these hierarchical relationships, Oracle Fusion
Applications can infer information.
• If you enter 94065 in a zip code of the application, the
application determines that the postal code belongs to:
– California
– Redwood City

Geography Hierarchy Example
Because the top level of any geography hierarchy is Country, a

geography hierarchy contains countries and their child
geographies such as state, county, and city.
A geography hierarchy can be a Master Reference Geography Hierarchy or a User Defined

Geography Hierarchy:
• Master Reference Geography Hierarchy: The source of truth for geography data. It
consists of master reference geography types and geographies. For example, Country is
a universally recognized geography type, and United States is considered a master
geography. Master Reference Geography Hierarchy data is used as the source for
validating addresses, and for creating user-defined geography hierarchies.
• User Defined Geography Hierarchy: A classification of geographical data, containing
entities with arbitrary boundaries, such as tax zones that encompass various US states
in each zone. A user-defined geography hierarchy comprises geographical data, either
created from the master reference data or entered manually.

Geography Validations
Geography validation determines:

• The geography mapping.
• Validation for a country’s address styles.
• Overall geography validation control for a country.
You can define:
• Multiple address style formats for a country.
• Geography mapping and validation for each of the address
style formats.
The No Styles Format address style format is:
• The default address style format for a country.
• Used to define mapping and validation for any address in the
country.
You can map the address attributes for each of the address style formats to a geography type.
For example, you can map the State geography type to the County address attribute for the
United Kingdom. For each address component, you can enable:
• List of values: Specifies whether the geography type will appear in a list of values during
address entry in user interfaces. You must enable a list of values only if you have
sufficient geography data. This ensures address data quality while creating new
addresses by displaying a list of values from the geography data during address entry.
• Tax validation: Specifies whether the geography type will be included in tax validation.
This ensures that the addresses are valid, based on the geography hierarchy data, for
tax calculation.
• Geography validation: Specifies whether the geography type will be included in
geography validation. This ensures that a new address will have correct geographic
data, based on the geography hierarchy data.

Manage Geography Validations
Whether the level is validated.
If error, data cannot be saved if

validation fails.
You can define Geography Duplicate Validation Control at the country level. The geography
validation control determines whether an address that did not pass geography validation
during address entry can be saved. If the validation control is set to Error, then an address
that has failed validation cannot be saved and the errors are saved in the status. If the
validation control is set to No Validation, all addresses are saved including incomplete and
invalid addresses.

Address Cleansing
1. Enter 3. Verified
address and address
click. appears in
standardized
form.
2. Verify
address and
click.
Address Cleansing:
• Validates, corrects, and standardizes addresses that you enter in a user interface.
• Validates the entire address against an external directory of addresses.
• Transforms the address to the postal standard form attributes.
• Ensures real-time, consistent address representation by checking whether address data
entered conforms to a particular format.
Note: Address line attributes are defined in the Address Style format, which specifies the
layout of an address.
Real-time address cleansing for a country has the following levels:
• None: Specifies that the country does not have real-time address cleansing.
• Optional: Specifies that you can optionally cleanse address data during address entry.
You can select the option to perform real-time address cleansing, and receive a
corrected, standardized address.

Geocoding Process
• Determines the latitude and longitude coordinates for a

location.
• Uses latitude and longitude coordinates from spatial services
to provide points of interest to sales representatives, such as
customer and contact address.
• Is used to display customers in the vicinity of a mobile
address.
Longitude
Latitude
Spatial services enable users to find points of interest such as customers, contacts, and so on
using the latitude and longitude coordinates of an address.
After the latitude and longitude coordinates are available from geocoding, you can use the
spatial services feature to identify points of interest, such as customer and contact addresses,
in the vicinity.
By default, the Geocoding option is disabled. You can enable the Geocoding option on the
Setup and Maintenance > Manage Geographies page.
If the Geocoding feature is enabled, the feature can be scheduled to run at regular time
intervals so that newly created or updated locations are picked up and decoded whenever
you create or update an address using the user interface, web services, bulk import, or file-
based import.
You can schedule the Populate Location Latitude and Longitude process at regular intervals
in the Scheduled Processes work area to populate the latitude and longitude information for
the addresses you enter in the application.

Importing Geography Options
You can import geography data using one of the following

options:
• Import Nokia geography reference data.
• Import third-party geography data using file-based data
import.
• Use the Geography Loader to populate interface tables.
Note: You can import Nokia geography reference data from the Manage Geographies user
interface. The Oracle-licensed Nokia data from Nave is available for the US and a growing list
of countries. If the licensed Nave data is not available for a particular country, then the Import
Nokia Data action is disabled.
Import Third-party Geography Data Using File-based Data Import: You can use the file-based
import process, if you plan to provide geographic data details in a source file. The process
reads the data in the source file, populates the interface tables, and imports the data into the
application destination tables.

Nokia Geography Reference Data Import
• Import Oracle-licensed Nokia data from Nave for those

countries where the data is available.
• Import Nokia geography data using the Manage Geographies
task.
– Search for the country.
– Select Import Nokia Data from the Actions menu.
To import and set up geography data, you must import geography data for the countries
where you do business. You can import Oracle-licensed Nokia data from Nave for those
countries where the data is available.
If the licensed Nave data is not available for a particular country, then the Import Nokia Data
action is disabled. In this case, you must license geography data from another vendor and
import it from a file.
The Nokia Data import option is supported for the following countries:
Austria, Belgium, Bulgaria, Canada, Switzerland, Czech Republic, Germany, Denmark, Spain,
Finland, France, Greece, Hungary, Ireland, Iceland, Italy, Mexico, Norway, Poland, Portugal,
Romania, Russia, Sweden, Turkey, and United States.

File-Based Import
Use the file-based import process if you plan to provide

geographic data details in a source file. The process:
• Reads the data in the source file.
• Populates the interface tables.
• Imports the data into the application destination tables.
File-based import process includes the following steps:
• Create an external file containing the import data.
• Define an import activity with:
– Import processing details.
– Source data to object attribute mapping.
– Job schedule details.
• Monitor the progress of the import job.
File-based import supports:

• Import of data from an external file to interface tables.
• Transfer of data from interface tables to application tables.
For more information, go to
• File Based Data Import for Oracle Financials Cloud Guide on the Help Center.
• My Oracle Support Article 1564536.1: Oracle Sales Cloud File-Based Data Import
Guide.

Managing Geography Lookups
Geography lookup types provide choices related to geographies,

such as address validation methods.
Two extensible geography lookups that you can customize are:
• HZ_GEO_DATA_PROVIDER: Specifies the source of
geography data such as user entered or from third party
providers such as TAXWARE.
• HZ_GEO_IDENTIFIER_SUBTYPE: Identifier sub type for
geography, for example, primary and alternate names and
codes for each geography.
You can:
• Rename the values or codes for these lookup types.
• Add new extensible codes to these lookups types.

Tax Zone Types and Zones
Zone types and zones define a geographical boundary, based on

master geography hierarchy data, that can be used to create tax
or shipping zones.
• Zone types:
– Categorize and group related zones together.
– Can include geographies from anywhere in the world
– Can be restricted to contain geographies from within a
specified country.
– Create before you can define a zone for a geographical
• Zones are geographical boundaries for a zone type.
For example, you can create a United States Tax zone type, to include various tax zones in
the country.
When you create:
• A zone type that is restricted to a country, you can define the geography types or
geographies that can be used to create a zone.
• A zone, you will need to either create the zone under an existing zone type, or you will
need to create a new zone type and then create the zone.

Run Maintain Geography Name Referencing Process
Geography Name Referencing process :

• Validates and maps address elements of existing location
information against master reference geographies.
• Establishes a cross reference between location information
columns and geography data.
• Needs to be run only if you make changes to the geography
data that impact addresses, or to troubleshoot issues.
Setup and Maintenance > Run Maintain Geography Name Referencing

For example, for a specific address record, the CA value in the STATE column of the
HZ_LOCATIONS table is mapped to the master reference geography of CA.
• The application runs this process whenever you create a new address or edit an existing
address in the application. Additionally, you can run this process at scheduled intervals
to maintain address data quality.
Enter parameters before running the process:
• Location Table Name: HZ_LOCATIONS or PER_ADDRESSES_F
• Run Type: Use the New or All value to indicate which addresses should be referenced.
• Usage Code: GEOGRAPHY or TAX.
• Country Code: Enter the country to process addresses for.
• From and To Location ID: Use ID to filter.
• Start and End Date: Use dates to filter.

Quiz
Q
Which of the following do you define first?
a. Geography Hierarchy
b. Geography Structure
c. Geography Validation
Answer: b

Quiz
Q
You can import geographies using either file-based import
or geography loader.
a. True
b. False
Answer: a

Quiz
Q
A zone type cannot include geographies from multiple countries.
a. True
b. False
Answer: b

Quiz
Q
Geography Name Referencing is:
a. The process of cross-referencing address elements and
geography data.
b. The process of mapping geography structure and geography
hierarchy.
c. The process of cross-referencing source file columns and
import object attributes.
d. The process of mapping zones to zone types.
Answer: a

Summary

• Discuss the Vision Corporation Story elements.
• Explore geography:
– Structure
– Hierarchy
– Validation

6
Configuring Enterprise
Structures

Objectives

• Enter enterprise structures using the Rapid Implementation
spreadsheet.
• Define legal jurisdictions and authorities.
• Search for legal entities.
• Create legal reporting units.

Define Enterprise Structures
Begin configuring the enterprise structure from the Setup and Maintenance work area.
The list of tasks to complete is arranged in the order in which the list should be completed.
An enterprise consists of legal entities under common control and management.
In this section, we will discuss:
• Rapid implementation of enterprise structures
• Legal jurisdictions and authorities
• Legal entities
• Legal reporting units

Sharing Ledger Components Across Oracle
Applications
Many components of an accounting configuration are shared with
other Oracle Fusion Applications.
The chart of accounts, calendar, and currencies are called the three Cs because they are the
three main components required to create a ledger. An accounting method is also required
and a seeded method is available.
For example, Payables uses the account structure to record invoice distributions, the
accounting calendar to record the date of the invoice, currencies and rate types to record
invoice amounts in different currencies, and the journal categories and sources to book the
accounting entry.

Practice 6-1 Overview: Reviewing Shared Components

• Viewing accounting period.
• Viewing journal source and categories.
• Viewing account number created by the components in your
chart of accounts as you enter a journal.

Plan Your Implementation Requirements
• Determine your chart of accounts segments.

• Create your segment values and hierarchies data in the
specified format.
• Identify your legal entities, addresses, and business units.
• Determine your key accounts that are used to track
accounting activities, for example, retained earnings, cash,
accounts receivable, accounts payable, and revenue.
• Determine your calendar start date.
• Finalize your primary balancing segment value, legal entity,
and business unit relationships.
• Determine your document and journal sequencing
requirements.
Caution: Plan your implementation carefully, including the above requirements, before
preparing and loading your spreadsheet. Some configurations cannot be changed after the
spreadsheet is loaded.

Implementation Simplification
• Financials standard task list contains 900+ tasks.

• Financials rapid implementation task list contains 90+ tasks.
– Critical setup tasks for initial setup.
– Setup steps that are required by most users.
• Rapid Implementation task list includes spreadsheets to
quickly create:
– Enterprise structures including legal entities
– Account defaults and financial sequences
– Banks, branches, and accounts
– Taxes
– Fixed assets
– And many more tasks.
Use the Define Financials Configuration for Rapid Implementation task list to streamline your
setup configuration to focus only on the critical setup steps. The rapid implementation task list
minimizes the time needed for you to complete your key setups and enable the day-to-day
use of Oracle Fusion Financials.
Note: You cannot perform a complete implementation using only the Rapid Implementation
task list. You need to also use the tasks in the standard Financials task list to add and update
additional setup data.

Rapid Implementation: Overview
Rapid implementation is used on Oracle Fusion applications and

assists you in creating components in spreadsheets:
• A chart of accounts, legal entities, hierarchies, document
sequencing, key account assignments, a fiscal calendar,
account defaulting, and financial sequencing.
• Primary ledgers and business units with assignment of all
business functions to use with your subledgers.
Navigate to: Setup and Maintenance > Search > Rapid Implementation > Expand the Define
Common Financials Configuration for Rapid Implementation.
Other objects that are included are legal addresses and mapping between legal entities and
the primary business segments.

Rapid Implementation Task List
Define Financials Configuration for Rapid Implementation:

• Define Common Financials Configuration for Rapid
Implementation
• Define Financials Security Configuration for Rapid
Implementation
• Define Ledger Configuration for Rapid Implementation
• Define Financial Reporting Center Configuration for Rapid
Implementation
Navigate to: Setup and Maintenance > Define Financials Configuration for Rapid
Implementation > Expand list.
For fast, efficient implementations, use the Define Financials Configuration for Rapid
implementation task list. These task lists consist of the required tasks for your implementation
including spreadsheet loaders. The task lists are arranged in the order in which the tasks
need to be completed.
Note: The list above is the areas that are covered in this course and is not a complete list.

Rapid Implementation Process
The Create Chart of Accounts, Ledger, Legal Entities, and

Business Units rapid implementation task consists of the following
steps:
1. Enter the data into the spreadsheets.
2. Upload the XML files generated from the spreadsheets.
3. The deployment process to finalize the chart of accounts
configuration is run automatically.
4. Upload the XML files generated from the spreadsheets for the
rest of the configuration.
The Rapid Implementation task configures your enterprise structures quickly:

• Using sheets in a workbook to upload lists of companies (legal entities), ledgers,
business units, chart of account values, and other similar data.
• Creating multiple hierarchies for any chart of accounts segment, either during initial
setup or at a later point. Use the Hierarchies Only sheet in the Rapid Implementation
spreadsheet to create new hierarchies or add new versions to existing hierarchies after
your enterprise structures have been created.
• Note: The spreadsheet template includes a detail instruction sheet on how to do the
setup step by step and also how to create the hierarchies at later point of time.

Chart of Accounts Components
All of these components in a chart of accounts can be created using Rapid Implementation
spreadsheets:
• Chart of Accounts Structure: Defines the key attributes for your chart of accounts, such
as the number of segments, segment sequences, segment names, segment prompts,
default value sets, and segment labels such as Natural Account and Primary Balancing.
• Chart of Accounts Structure Instance: Inherits by default all 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. Oracle best practice is to map your chart of
accounts structure to one and only one instance.
• Value Sets: Attached to each segment to provide formatting and validation of the set of
values used with that segment. You can think of a value set as a container for your
values.
• Segments: Combine with other segments to create the account combination. Each
segment has a value set attached to it to provide formatting and validation of the set of
values used with that segment.

• Segment Labels: Identify certain segments in your chart of accounts and assign special
functionality to those segments
- Note: The Management segment label is descoped in V1.
• Deploy: Generates or refreshes components that activate the chart of accounts in a user
interface. To use a chart of accounts, it must have been deployed.
• Values: Set of valid values that you assign to a chart of accounts segment.
• Segment Value Security Rules: Applied at the value set level to secure the data. If a
value set is secured, all chart of accounts values of the value set are prohibited by
default. And you are required to give access specifically to users you want to use them.
Also all the segments that use the value set are affected by the value set's defined
security rules.
• Cross-Validation Rules: Determine which account combinations are created dynamically
as your users enter transactions or journal entries.
• Account Combinations: Contain a completed code of segment values that uniquely
identifies an account in the chart of accounts.

What Is a Value Set?
• Controls types of values can be used in key and descriptive

flexfields such as chart of accounts segment values.
• Determines the attributes of your segments such as length,
zero-fill, right-justify, alphanumeric, and value security.
• Controls how validation is performed. For example, a list of
values must be created and used.
Manage Value Sets: Navigate to: Setup and Maintenance > Manage Value Sets.
• Assign one value set to each chart of accounts segment.
• Share the same value sets across multiple charts of accounts to facilitate consolidation if
the values are the same and have the same meaning.
• Use the same value set more than once within the same chart of accounts structure if
the same values are used for the balancing and intercompany segments.
Note
• Changing the attributes of a value set affects all chart of accounts segments using that
value set.
• If segment value security rules are applied to the shared value set used for the company
and intercompany segments, problems may arise with intercompany values used to
record cross-ledger transactions.

Assigning Segment Labels
• Segment labels indicate

that a segment is used in a
particular manner.
• For example, assign a
segment label of Primary
Balancing to a Company
segment to indicate that
journals must balance by
company.
Segment labels are assigned as part of the rapid implementation configuration of your chart of
accounts structure. You can review the assigned segment labels on the Manage Key Flexfield
Structures page, which you access using the Manage Structures button on the Manage Chart
of Accounts page.
Note: The Management segment label shows in the user interface but not currently supported
in Oracle Cloud applications.

Balancing Segment Labels
• Ensures that all journals balance by balancing segment value,

or by a combination of balancing segment values if multiple
balancing segment values are used.
• Enables you to create balance sheets and trial balances by
balancing segment.
• Enables you to define data access security across additional
levels.
Three balancing segment labels are available: Primary, Second, and Third Balancing.
• The Primary balancing segment label is required.
• The Second and Third balancing segment labels are optional, and may not be
necessary unless, for example, you need to balance at more than the legal entity level
for management reporting.

Cost Center Segment Labels
• Facilitate grouping of natural accounts by functional cost

types, accommodating tracking of specific business expenses
across natural accounts.
• Enable combining expenses and head count data into cost
centers that are useful for detailed analysis and reporting.
• Are optional, but required when:
– Using Oracle Fusion Assets.
– Storing expense approval limits in Oracle Fusion Expenses.
Note: Add a cost center segment if you plan to add Assets or Expenses in the future, because
the chart of accounts cannot be modified.

Other Segment Labels
• Natural Accounts:
– Determines the account type (asset, liability, expense, revenue,
or equity) and other information specific to the segment value.
– Facilitates processes in the General Ledger application, such
as retained earnings posting, and therefore is required.
• Intercompany:
– Optionally assigns the segment to be used in intercompany
balancing functionality.

Defining Hierarchies: Overview
• Leverage the common date-effective tree model employed

throughout Oracle Fusion Applications.
• Used in Oracle Fusion General Ledger to facilitate:
– Chart of accounts mappings
– Revaluations
– Data access sets
– Cross-validation rules
– Segment value set rules
• Leveraged in:
– Inquiry and Reporting
– Smart View queries
– Allocations
Note: The spreadsheet creates one hierarchy. To create additional hierarchies, use the
Generate Additional Hierarchy button (which appears on the Company and Natural Account
sheets) to generate multiple hierarchies for any chart of accounts segment, either during initial
setup or at a later time, by using this button to create new hierarchies or add new versions to
existing hierarchies after your enterprise structures have been created.

Manage Business Units
A business unit:
• Represents a unit of an enterprise that performs one or many
business functions.
• Can be consolidated in both a managerial and legal hierarchy.
• Can process procurement transactions on behalf of many
legal entities.
• Is similar to the operating unit in prior versions of Oracle EBS
Financials, with additional functionality.
• Is used to partition your subledgers data.
Normally, a business unit has a manager, strategic objectives, a level of autonomy, and
responsibility for its profit and loss.

Rapid Implementation Workbook
Begin by downloading the workbook using the Create Chart of

Accounts, Ledger, Legal Entities, and Business Units in
Spreadsheet task on the Setup and Maintenance work area.
Navigate to: Setup and Maintenance > Create Chart of Accounts, Ledger, Legal Entities, and
Business Units in Spreadsheet
You enter data in a sheet like the one shown above.
• Use the validate and generate buttons to validate and generate two files after entering
the data on your enterprise structures.
• Import and deploy a file to automatically create a ledger with legal entities, a balances
cube, and business unit or units with all business functions enabled. The legal entities
that use the ledger are associated with it and assigned balancing values. A primary
ledger is created for each distinct country of your legal entities.
• Add Segment Sheets button: You create spreadsheets to enter values and hierarchies
for additional segments by entering the segments on the Chart of Accounts, Calendar,
and Ledger sheet and then clicking the Add Segment Sheets button.

GL Rapid Implementation Additional Features
The enhanced Rapid Implementation solution enables users to

quickly implement enterprise structures by using a spreadsheet
interface to configure the following setup components.
• Account Defaulting
• Sequencing Configuration
These features complement the existing Rapid Implementation
setups with their own spreadsheets:
• Cross-Validation Rules
• Segment Value Security Rules
• Account Combinations

Cross-Validation Rules and Segment Value Security
Rules
• Cross-Validation Rules:
– Create rules to prevent certain account combinations from
being created
– Define condition and validation filters on the cross-validation
rules spreadsheet.
– Assign values using common operators such as equals,
between, and is descendant of.
• Segment Value Security Rules:
– Define security rules and assign the rules to your users’ roles
using the segment value security rules spreadsheet.
– Assign access to segment values using common operators
such as equals, between, and is descendant of.
Navigate to: Setup and Maintenance > Create Cross-Validation Rules in Spreadsheet.
Cross Validation example: Balance sheet accounts are not combined with operational cost
centers.

Account Combinations
• Create entire account combinations for your chart of accounts

using a spreadsheet.
• Typically, create account combinations when dynamic
insertion is disabled to force users to only use predefined
account combinations
• Create only prevalidated account combinations.
Navigate to: Setup and Maintenance > Manage Account Combinations > Create in
Spreadsheet button.

Account Defaulting
• Create with your natural account value set values in the Rapid
Implementation spreadsheet.
• Tag natural account values with an extended account type
such as Assets – Accounts Receivable, Assets – Asset
Clearing, and Owner’s Equity – Retained Earnings.
– Financial category, which is used to facilitate Oracle Business
Intelligence Applications (OBIA) Reporting, is automatically
assigned.
– Tagged natural accounts are used to generated accounts in
setup objects, such as ledgers, bank accounts, asset books,
intercompany accounts, receivables system options, payables
common options, and so on.
Business Units in Spreadsheet.
• All available extended account types must be assigned to one natural account value.
The extended account types help create default accounts automatically across multiple
product setup user interfaces. For example Payables and Receivables setup options.
• You should assign an extended account type only to a postable detail-level natural
account value, and you must assign a particular extended account type only to one
account. Likewise, a detail natural account value can be assigned only one extended
account type.
• Specify at least one detail account value for the other segments in the chart of accounts
besides the company and natural account segments. The detail account value is used to
create the account combination supplied by default into Oracle Financials Cloud setup
objects.

Country-Specific Document and Journal Sequencing
• Use the Financials Sequences worksheet in the Rapid

Implementation spreadsheet.
• Create document, accounting and reporting sequences,
versions, and assignments for your ledgers or legal entities,
based on your country-specific sequencing requirements.
• Capture country information about your setup to create
country-specific defaults for sequencing.
Business Units in Spreadsheet.
For example, sequences are enabled at the legal entity level for countries with such a
requirement like Spain, Italy, and France. Sequencing is not enabled for other countries
where sequencing is not required, for example, the Untied States, even if you provide
sequencing. The data is skipped.

Rapid Implementation Spreadsheets
The Create Chart of Accounts, Ledger, Legal Entities, and Business Units workbook provides
six sheets.
• Instructions: Read the planning tips, loading process, best practices, and
recommendations. The Instruction sheet includes a link to a completed sample data
workbook.
• Chart of Accounts, Calendar, and Ledger
• Business Units
• Companies and Legal Entities
• Natural Accounts
• Financial Sequences
For the intercompany segment, no sheet is created. The application uses the value set and
values from the company segment for its value set and values.

Note: If you plan to secure your company segment values using segment value security rules,
do not assign the Intercompany Segment qualifier to the intercompany segment.
Not assigning the qualifier ensures that:
• Your company and intercompany segments use different value sets.
• That the Segment Value Security Rules assigned to your Company value set do not
affect your intercompany segment.

Completing the Accounting Configuration
Validate and generate the files using the buttons on the

spreadsheet:
• Step 1: Validate data and correct any errors.
• Step 2: Generate Chart of Accounts File
• Step 3: Generate Ledger, LE, and BU File
Navigate to: Setup and Maintenance Create Chart of Accounts, Ledger, Legal Entities, and
Business Units.
• After you finish preparing the data in the sheets, click the button called Validate Data. A
Validation Report is generated. If there are errors, correct them before proceeding.
• Click on the button called Generate Chart of Accounts File. The process generates a zip
file for the entered chart of accounts and hierarchies setup data. Save the file.
• Click the button called Generate Ledger, LE, and BU File. The process generates a zip
file for the entered ledger, legal entities, and business units setup data. Save the file.
• Navigate to: Setup and Maintenance > Upload Chart of Accounts. This task launches
the Upload Enterprise Structures and Hierarchies process. Select the Upload Enterprise
Structure option. Click the Choose File button and select the first zip file you have
saved. Click Submit.
• Navigate to: Tools > Scheduled Processes. Verify that the process was completed.
• Navigate to: Setup and Maintenance > Upload Ledger, Legal Entities, and Business
Units. Click on the Upload Enterprise Structure radio button. Click the Choose File
button to select the second zip file you have saved. Click Submit.
• Navigate to the Scheduled Processes page. Verify that the process was completed .

Note: When you upload the Rapid Implementation spreadsheets, the system automatically:
• Deploys the chart of accounts.
• Creates two versions of your hierarchy, Base and Current.
- Runs the flattening and auditing programs
- Sets their status to Active.
• Publishes all hierarchies for you.
• Submits the Accounting Configuration.
• Creates the cubes based on your chart of accounts and calendar combination.

Practice 6-2 Overview: Entering Data in the Rapid
Implementation Spreadsheet
• Entering segments and corresponding data.
• Validating the data entry.
• Generating files of data to upload.

Completing the Accounting Configuration
• Upload using the Upload Chart of Accounts task from the

Setup and maintenance work area to run the upload process
for the first file you saved.
• Note that deployment happens automatically after the upload
as of Release 11.
• Upload using the Upload Ledger, Legal Entities, and Business
Units task from the Setup and Maintenance work area to run
the upload process for the second file you saved.
• In the parameters region of the Upload Chart of Accounts process, select the first file
you saved, XXChartOfAccounts.xml, and submit the process.
• After loading your chart of accounts file, deployment of the chart of accounts is
automatic. Deployment deploys all charts of accounts in the system.
• After deployment is successfully, upload the second file you saved
(XXFinancialsCommonEntities.xml) by selecting it in the parameters region of the
Upload Ledger, Legal Entities, and Business Unit process.

Deployment Status
• Edited: The flexfield definition has not been deployed or

changes have been made to the structure, structure
instances, or value sets.
• Patched: The flexfield definition has been modified through a
patch, but the flexfield has not yet been deployed, so the
patched definition is not reflected.
• Deployed to Sandbox: The flexfield is deployed and available
in a flexfield-enabled sandbox.
• Deployed: The flexfield definition is deployed and available to
end users.
• Error: The deployment attempt failed.
Deployment deploys all charts of accounts in the system during each run. To verify that the
Deployment Status has finished, navigate to the Manage Key Flexfields page from the Setup
and Maintenance work area. It stops when an error occurs. You must fix the errors and run
the process again until successful.

Practice 6-3 to 6-5 Overview: Completing the Rapid
Implementation Process
These practices and demonstration cover the following topics:
• Practice 6-3: Uploading the Chart of Accounts File
• Practice 6-4: Verifying Deployment Was Successful
Demonstration
• Practice 6-5: Uploading the Ledger, Legal Entity, and
Business Unit File

Other Spreadsheet Uses
• Oracle Fusion Applications deliver extensive spreadsheet

integration across multiple finance functions, allowing finance
users to work in a familiar environment.
• Budgets can be uploaded and budget import errors can be
corrected by using the Correct Budget Import Errors
spreadsheet.
• Spreadsheets are seamlessly integrated with the applications
for high-volume data entry and one-click uploads.
• In addition, all reports and transactional tables can be
exported to Microsoft Excel for further analysis and easier
viewing of large amounts of data.
The following are some examples of where spreadsheets are used in Oracle Fusion
Applications:
• General Ledger: Enter account combinations, cross-validation rules, and journals,
correct journal import errors, and upload currency conversion rates within a
spreadsheet. You can also upload budgets and correct budget import errors.
• Payables: Enter supplier invoices and correct invoice import errors.
• Assets: Set up key asset features, such as asset categories, physical locations, asset
keys, books, and category book defaults, prepare asset source lines, and complete
asset details within a spreadsheet and then import them.
• Expenses: Employees can also enter their expense reports in Microsoft Excel. You can
enter employees using spreadsheets too.
• Receivables: Process customer receipts and upload customer data.
• Tax: Configure transaction taxes according to local and international tax requirements.
• Country-Specific Sequences: Generate country-specific sequencing setup using the
predefined country defaults that are based on commonly used, known sequencing
requirements.

Enterprise Structures Setup Report
Enterprise Structures Setup Report:

• Validates your enterprise structures configuration.
• Provides the detailed listing of chart of accounts, segments, value sets, ledgers, legal
entities, business units, and account hierarchy information.
• Creates an auditable report in multiple formats such as HTML, PDF, RTF, Excel (*.xlsx),
Power Point (*.pptx), and CSV to improve your off-line analysis requirements.
• Runs as a scheduled process with one parameter; Chart of Accounts name.
Report security prerequisites:
• 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

Diagnostic Tests for Enterprise Structures Setup Data
Welcome page > Click your User Name to open Settings and Actions menu >
Troubleshooting > Run Diagnostics Tests.
You can run diagnostic tests to perform 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 perform the diagnostic tests, you must be granted
the Application Diagnostics Regular User job role.
• When you have been granted the role, you can view the link to run the diagnostics tests.
• If you have the Application Diagnostics Viewer job role, you can view the diagnostic test
results, but not run new tests.

Define Legal Jurisdictions and Authorities
Register your legal entities:

• With legal authorities in the jurisdictions where you conduct
business.
• As required by local business requirements or other relevant
laws.
Additional considerations:
• Define jurisdictions and related legal authorities to support
multiple legal entity registrations.
Note: When you create a legal entity,
the application automatically creates:
– A registration for the new legal entity.
– A main legal reporting unit.
Legal jurisdictions and authorities may be relevant to your Oracle Fusion Financials
implementation only if you:
• Use Oracle Fusion Payables and Oracle Fusion Receivables.
• Perform tax calculations.

Legal Jurisdictions: Overview
A legal jurisdiction is one in which a particular piece of legislation

applies to a group of countries or a single country, state, county,
or parish.
• Examples: French Labor Law, Singapore Transactions Tax
Law, and US Income Tax Laws.
• Types of jurisdictions are:
– Identifying Jurisdiction
– Income Tax Jurisdiction
– Transaction Tax Jurisdiction
Income tax jurisdictions and transaction tax jurisdictions are two
distinct jurisdictions, but can:
• Be defined at the same geopolitical level, such as a country.
• Share the same legal authority.
• Identifying jurisdiction: First jurisdiction you must register with to be allowed to do

business in a country.
- Select only one as the identifying jurisdiction if more than one jurisdiction exists
with which a legal entity needs to register to commence business.
- Select the one you use to uniquely identify your legal entity as the identifying
jurisdiction.
• Income tax jurisdiction: Imposes taxes on your financial income generated by all your
entities within their jurisdiction.
- Create income tax jurisdictions to properly report taxes to legal authorities.
- Remit income taxes to legal authorities.
• Transaction tax jurisdiction:
- Created through Oracle Fusion Tax in a separate business flow.
- Contains specific needs and complexities of various taxes.
- Receives their respective rates from their suppliers.
- Requires periodic maintenance.
- Is used for legal reporting of sales and value-added taxes.

Legal Authorities Overview
• 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 legal
authority responsible for collecting taxes and the interpretation
and enforcement of the Internal Revenue Code of the United
States.
• Legal authority information is printed on your tax reports to meet country requirements,
for example, for India and Brazil.
• Legal authorities are defined on the Manage Legal Authorities page under the Define
Legal Jurisdictions and Authorities for Financials task list.
• Tax authorities are a subset of legal authorities and you define them using the same
setup page.

Practice 6-6 to 6-8 Overview: Reviewing a Legal
Jurisdictions and Authorities
• Practice 6-6: Reviewing an Existing Legal Jurisdiction
• Practice 6-7: Reviewing Legal Addresses for Legal Entities
and Reporting Units
• Practice 6-8: Creating a Legal Authority

Manage Legal Entities
• A legal entity is a recognized party with rights and responsibilities given by legislation.
• A legal entity has the right to own property, the right to trade, the responsibility to repay
debt, and the responsibility to account for themselves to regulators, taxation authorities,
and owners according to rules specified in the relevant legislation.
• A legal entity’s rights and responsibilities can be enforced through the judicial system.

Legal Entities Definition
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.
• Perform intercompany trading.
A legal entity has a separate legal identity and conducts aspects
of your business for the following reasons:
• Complying with corporate taxation within local jurisdictions.
• Preparing for acquisitions or disposals of parts of the
enterprise.
• Isolating one area of the business from risks in another area.
• Facilitating local compliance.
For example, your enterprise develops and leases properties. You can create separate legal
entities for development and leasing. This would minimize risk across your lines of business.

The Role of Your Legal Entity
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 sales.
– Make purchases and incur expenses.
– Perform other transactions.
• A legal entity must comply with the regulations of jurisdictions
in which they register.
• To support local reporting requirements, legal reporting units
are created and registered.
If you make purchases and sell to and from companies under your control, define these
companies or other legal entities as customers and suppliers.
• Transactions between legal entities require accounting.
• Accounting for transactions between legal entities under common control (your legal
entities) is called intercompany accounting.
Legal entities can be identified as legal employers on the Manage Legal Entity page. In
Oracle Fusion Financials, the employees employed by the legal employer can be assigned as
users.

Legal Entities in Transactions
• Assets and liabilities of the enterprise are owned by individual

legal entities.
• Enter legal entities on transactions that represent a movement
in value or obligation.
• Ownership provides, under contract law in most countries, that
damages can be sought:
– For actual losses, putting the injured party in the same state as
if they had not entered into the contract.
– For loss of bargain, meaning the profit that could have been
made on a transaction.
DAMAGES & LOSSES

Legal Entity and Business Units
A business unit that serves your enterprise as a shared service

center can process transactions on behalf of many legal entities.
A legal entity can be:
• Explicit on your transactions.
• Inferred from other reference entities that are themselves
linked to a single legal entity.
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.
In Oracle Fusion Applications, use business unit as a securing mechanism for transactions.
For example, if you run your export business separately from your domestic sales business,
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.

Legal Entity and Divisions
Divisions
Divisions
• Provide an area of management responsibility that can correspond to a collection of
legal entities or to part of a single or of several legal entities.
• Aggregate financial results for divisions by legal entity or by combining parts of multiple
legal entities.
• Define date-effective hierarchies for the segment that represents the management entity
in the chart of accounts to facilitate the aggregation and reporting by division.

Legal Entity and Ledgers
• Use the Define Accounting Configuration tasks list to specify

which ledger a legal entity uses to perform accounting.
• When several legal entities share a ledger, use a balancing
segment value for each legal entity.
• Assign one or more legal entities to your configuration using the Assign Legal Entities
task.
• Assign balancing segment values to your legal entities using the Assign Balancing
Segment Values to Legal Entities task.
• Assign balancing segment values directly to your ledger using the Assign Balancing
Segment Value to Ledger.
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.

Legal Entity and Balancing Segments
• Accounting for your operations means you must produce a

trial balance and balance sheet by legal entity.
• Oracle Fusion General Ledger supports the use of up to three
balancing segments.
• Best practice is to use at least one balancing segment to
represent a legal entity to facilitate financial reporting to
regulatory agencies, tax authorities, and investors.
• If you want to subdivide legal entities into lower levels for
reporting, you can use one or two additional balancing
segments in your chart of accounts.
Assign balancing segment values.

• If you use a balancing segment to represent legal entities, you should represent each
legal entity as it's own balancing segment value.
• If you account for each legal entity in a separate ledger, then no requirement exists to
identify the legal entity with a balancing segment value within that ledger.
• If you want to create consolidated management reporting across legal entities, you can
use a single ledger to represent multiple legal entities. This is possible when the legal
entities are governed by the same legislative requirements, such as operating in the
same country.

• If the legal entities are not governed by the same legislative requirements, you may
need to store them in separate ledgers.
• You cannot change to multiple balancing segments after you have begun to use the
ledger because you historical data is not balanced by the new multiple balancing
segments.
- Example: A legal entity that operates in France should not be accounted in the
same ledger as a legal entity that operates in Ireland.

Legal Entities and Intercompany Transactions
Transactions that cross legal entities are accounted for as

intercompany transactions.
• If you use multiple balancing segments, the total debits and
credits must balance, per balancing segment, per journal
entry.
• If needed, balancing lines, using general ledger accounts as
specified in the intercompany secondary and clearing
company balancing options, are automatically added by the
application to ensure balancing of journal entries.
• Carefully consider whether to use multiple balancing
segments before using a ledger.
Caution
• After a ledger has been used, historical balances are not automatically converted based
upon the selection of additional balancing segments.
• You cannot change to multiple balancing segments after you have begun to use the
ledger because your historical data is not balanced by the new multiple balancing
segments.

Legal Entity and Its Relationship to Intercompany
Transactions
After you have created transactions for your companies or other
types of legal entities, and assigned values in the appropriate
balancing segment to them, intercompany accounting will
maintain balances synchronized between them by:
• Automatic generation of balancing lines as the application
creates accounting to record due to or from legal entity
receivables, payables, or both.
• Manual or automatic intercompany balancing journal creation,
which books changes to intercompany accounts by legal entity
to balance and clear intercompany amounts.
Receivables
Payables
Post intercompany transactions directly to the General Ledger. Subledger invoicing is not
required. Instead, these transactions get directly transferred and posted to the general ledger.
To use this functionality:
• Define processing options.
• Select the intercompany account combinations that are used to create intercompany
transactions. Account combinations for intercompany transactions are derived
automatically based upon your intercompany setup.
• Set up intercompany organizations for your legal entities to limit the number of trading
parties. Intercompany organizations within the same legal entity are 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.

Legal Entity and Consolidation Rules
• When you have specified which balancing segments are used

by which companies or other types of legal entities, then
define consolidation elimination rules using your balancing
segments.
• Defining consolidation elimination rules creates a relationship
between the legal entities for eliminating intercompany
balances.
Consolidation is a period-end process of combining the financial results of separate

subsidiaries with the parent organization to form a single, combined statement of financial
results. Consolidation is a year end process when companies prepare their balance sheets.

Country-Specific Legal Entity Sequences
• Meet the statutory requirements in many European and Latin

American countries to sequentially number financial
transactions and accounting entries at the legal entity level
without having to implement a single ledger and business unit
per legal entity configuration.
• Meet these requirements even with multiple legal entities tied
to a single ledger and business unit.
• Configure sequencing by choosing appropriate options in the
newly added Sequencing region of the Specify Ledger
Options user interface.
Navigate to: Setup and Maintenance > Define Ledgers > Specify Ledger Options.
• Set the Sequencing By option to either ledger or legal entity to enable document
sequencing in subledger transactions and accounting and reporting sequencing in
subledger and general ledger journals.
• Set the Sequencing By option to none to disable sequencing.
• Set the Enforce chronological order on document date to Yes to generate chronological
sequence numbers. This is enforced only when sequencing is at legal entity level.
• Select the Enforce Document Sequencing option for Payables and Receivables if
sequencing is to be enforced for Payables and/or Receivables transactions. If this option
is selected, the transaction cannot be saved without a document sequence number
assigned to it.
Start using legal entity-based sequences, either at year-end or when new ledgers and legal
entities are implemented. You can use Rapid Implementation to automatically complete the
sequencing settings based on your country-specific needs. This includes enabling sequencing
for legal entity.

Practice 6-9 Overview: Searching for Your Legal Entity

• Searching for your legal entity.
• Reviewing a legal entity registration.

Manage Legal Reporting Units
• Each of your legal entities

must have at least one legal
reporting unit.
• When a legal entity is
created, a legal reporting
unit with the same name is
automatically created.
• You can define both
domestic and foreign
establishments.
Define legal reporting units by:

• A physical location, such as sales office.
• A logical unit, such as:
- Groups of employees subject to different reporting requirements.
- A Human Capital Management (HCM) system in which you use your
legal reporting units to model your tax reporting units.
Note: A tax reporting unit can be used to group workers for the purpose of tax reporting.

Legal Reporting Units Points to Consider
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:
• If the legal entity establishes operations requirements for each
local area in a country that requires reporting of employment
and sales taxes locally as well as nationally.
• If you need more than one legally registered location to meet
this legal entity’s reporting requirements in each local area.
Note: Multiple registrations can be associated with a legal reporting unit. However, only one
identifying registration defined with the legal authority used for the legal entity or legal
reporting unit can be associated with the legal reporting unit.

Practice 6-10 Overview: Viewing a Legal Reporting Unit
This practice covers viewing a legal reporting unit.

Summary

• Enter enterprise structures using the Rapid Implementation
spreadsheet.
• Define legal jurisdictions and authorities.
• Search for legal entities.
• Create legal reporting units.

7
Configuring General Ledger
Components

Objectives

• Manage chart of accounts components.
• Manage and publish account hierarchies.
• Define calendars and currencies.
• Define ledgers and ledger options.
• Explore the GL Balances cube.
• Open and close periods.
• Allocate balances.
• Manage revaluations and translations.
• Reconcile balances.

Financials Task Lists
Financials:
• Define Common Applications Configuration for Financials
Define Implementation Users
– Define Enterprise Structures for Financials
– Define Ledgers
– Define Security for Financials
– Define Approval Management for Financials
• Define Common Financials Configuration
• Define and Maintain Intercompany Processing Rules
• Define Budget Configuration
• Define Financial Reporting
Navigate to: Setup and Maintenance > Financials > Expand list.
To implement optional and more advanced features use the Financials task lists.
• The task lists are arranged in the order in which the tasks need to be completed.
• The Define Common Applications Configuration for Financials task list contains
implementation and administration tasks.
Note: The list above is the areas that are covered in this course and is not a complete list.

Accounting Configuration Prerequisites
To manually create a chart of accounts:

• Define value sets.
• Define a chart of accounts structure and instance.
• Define valid segment values.
• Define account hierarchies.
To complete optional steps if required by your implementation requirements:
• Create cross-validation rules.
• Create account combinations.
• Define segment value security rules.
Note: All these steps can be done in the Rapid Implementation spreadsheets.

Creating Chart of Accounts Considerations
• You must create value sets first and then add the value sets to
your structure and instance.
• After creating the structure and instance and assigning your
value sets, create values for the value sets.
Do not create values in your value set until after the structure and instance creation because
some value attributes, such as Allow Posting or Account Type, are not available.

Define Value Sets
Use value sets to control the characteristics and format of the

chart of accounts segments.
Navigate to: Setup and Maintenance > Manage Value Sets.

Best practice is to use only the Validation Type of Independent and the Value Data Type of
Character (Char) for your chart of accounts values sets. Use the Value Subtype of Text. You
can enter only numbers for your values even with the Value Data Type of Character, if you
desire.
• Module: You need to specify a module because the Manage Vale sets user interface is
shared across multiple applications.
• Maximum Length: Maximum width of each segment value.
• Uppercase only: All alpha values are uppercase. Best practice is to select this option
because when Oracle applications sort, it is by number first, then capital letters, and
finally lower-case letter. Example: mmm would be under ZME because the lower-case
values come after the capitalized values.
• Zero fill: If selected, right justify and zero-fill numbers are used. If you have the right-
justify zero-fill numbers check box selected, and your Maximum Length is 3, then your
segment value would be 001. However, if your Maximum Length is 4, then your segment
value would be 0001.

• Use a value set more than once within the same chart of accounts structure when the
same set of values is used for the balancing and intercompany segments, unless you
plan on defining segment value security rules for the balancing segment.
Note: Segment value security rules are defined at the value set level. If using segment value
security rules, the best practice is to create two values sets that use the same values for both
the company and intercompany segments rather than using the same value set for both
segments.
For example: If both the company and intercompany segments share the same value set and
you use segment value security rules to secure company values 101 and 102, then
intercompany transactions are limited to only 101 and 102.

Validation and Value Sets
When you define value sets, you also need to determine how you
want to validate your values.
Independent Validation
• Lists of values are independently displayed when you
complete the segment in the account combination.
• You must use independent validation and the data type of
character for your chart of accounts value sets. This structure
enables you to build a hierarchical tree structure from the
values and report on each segment independently.
Note: Table validated value sets are not supported in Oracle Financials Cloud.
Table and other validation types that are available and used with different types of flexfields,
such as descriptive flexfields or the Asset Category key flexfield, but not with the Accounting
Key flexfield, are:
• Format only: Data is entered and not selected from a list.
• Dependent: List of values for which a valid value is determined by the independent
value of another segment.
• Subset: List of values that is a subset of the values in an existing independent value set.

Practice 7-1 Overview: Searching for and Reviewing
Your Value Sets
• Finding the value sets created from the spreadsheet.
• Reviewing the values created from the spreadsheet.

Building the Chart of Accounts Structure
The decisions you make when designing your chart of accounts

are very important.
• Plan carefully.
• Customize your account structure.
• Choose the number of segments and formatting.
Making changes in the future to the structure and instances of your chart of accounts is
difficult and not recommended.
• Plan carefully to create an account structure that meets the current needs of your
organization and anticipates future requirements.
• Customize your account structure for your industry and reporting requirements.
• Choose the number of segments, as well as the length, name, and order of each
segment carefully.

Chart of Accounts Structure Attributes
The chart of accounts structure defines the key attributes for your
chart of accounts:
• Number of segments.
• Segment sequences.
• Segment names and prompts.
• Segment labels, for example natural account and balancing.
• Default value sets.
Sample Chart of Accounts Structure
Caution: Remember security is enabled at the value set level and applies to all segments that
use that value set.

Building the Chart of Accounts Restrictions
• Create up to 30 segments with a maximum of 25 characters

per segment for a concatenated total length of 250 characters
including the segment separators.
• Limit maximum length of all segments plus the segment
separator.
• Define each segment name and sequentially order the
segments, starting with 1.
• Use a default value set, which can be changed at the
instances level.
Best practice is five to nine segments. Avoid total concatenated lengths of over 28 to 30
characters as you can have problems with the chart of accounts truncating on some
predefined reports and complicates data entry.

Chart of Accounts Instance
• Appears in the user interfaces and processes.

• By default, inherits all the attributes of the chart of accounts
structure, meaning that all structure instances of the same
structure:
– Share a common shape.
– Contain the same segments in the same order.
• Permits overriding the default value set assignments for your
segments.
• Determines whether dynamic insertion is enabled to generate
new account combinations dynamically instead of you creating
them manually.
Optionally, assign unique hierarchies to create relationships between the value set values for
each segment in the instance by the assignment of a tree code to the value set associated
with the chart of accounts instance segment.
Different value sets and values are required to meet local and statutory reporting
requirements.
At the chart of accounts structure instance level:
• Optionally, override the value sets provided by default from the chart of accounts
structure.
• Assign a value set with the same segment type and length to each segment.
• Create hierarchies for each segment to meet financial reporting requirements.
• Assign a tree code to each instance segment to indicate the source of the hierarchy
information for the associated value set.

Account Shorthand Alias
NEW
• An account shorthand alias is a word or code that represents

a complete or partial account combination.
• You can use these descriptive labels to complete journal
entries
Example above: Navigate to General Accounting > Journals > Tasks > Create Journal.
• You can enter account segment values faster and easier by using account shorthand
aliases during entry of journals and other accounting transactions.
• The account aliases allow you to complete journal entries by selecting descriptive labels
instead of remembering complex account combinations.
• The underlying account segment values default automatically into the data entry fields.
Using this feature minimizes data entry errors, eliminating the need to correct or reverse
journals.
Steps to Enable Account Shorthand Alias
• Navigate to: Setup and Maintenance > Key Flexfield Structure Instance to have the
application implementation administrator enable the shorthand alias feature.
• Redeploy the chart of accounts structure.

Note: The list of values of eligible Chart of Accounts instances appears in the Manage
Shorthand Aliases page, only after these two above steps have been completed.
• Navigate to: Setup and Maintenance > Manage Shorthand Aliases page in Functional
Setup Manager, select your chart of accounts structure instance and click the Search
button to view existing aliases.
• Click the Add (+) icon to add new aliases.

Practice 7-2, 7-3, and 7-4 Overview: Searching for and
Deploying Your Chart of Accounts
This practice and demonstration cover the following topics:
• Searching for Your Chart of Accounts Structure and Instance
– Review your structure created from the spreadsheet.
– Verify your instance settings created from the spreadsheet.
• Deploying a Chart of Accounts Demonstration: Use this demo
to complete the enabling of the shorthand alias option.
• Creating an Account Shorthand Alias: Create an account
shorthand alias for your cash account.

Define Segment Values
Enter valid values for each segment after adding them to the
chart of accounts structure and structure instance.
Each value is defined with a name, description, and optionally a start date and end date.
Navigate from the Setup and Maintenance work area to the Manage Chart of Accounts Value
Sets page.
Click the Manage Values button to enter values for each segment. These are the values that
you use when building your account combinations.
Enable the segment value. The period of usage must fall within the start and end dates if
entered on the value.
Note: Sort Order is not used with the Accounting key flexfield.
Caution
• When creating a new chart of accounts with new value sets, create the value sets
definition first and leave the values creation until after the creation of the instance and
structure.
• Creating values before assigning the value set to the account structure prevents the
ability to define the required attributes on the values and make them unusable for the
chart of accounts.

Assign Segment Attributes
• Assign attribute options for

your segment values.
• Attributes appear based on
the segment label options
assigned to the segments
during chart of accounts
creation and vary by
segment.
Note: If you select Yes for Summary (Parent), the application does not post to the accounts
created using that value even if Allow Posting is set to Yes. Account Type, Third Party Control
Account, Reconcile, and Financial Category attributes are available only on the Natural
Account segment values. The Financial Category is a predefinded list where you can add
additional values.
• Summary: Yes indicates this value is a parent value.
• Allow Posting: Enter Yes to enable posting to the account. If you set Allow Posting to
No, you cannot post to the account. If you are defining a parent segment value, you
must enter No because you cannot post to parent accounts.
• Allow Budgeting: Enter Yes to perform budgeting for accounts with this segment value. If
you are defining a parent segment value, you must enter No.

• Account Type:
- Define an account type for each natural account segment value.
- Select the type of proprietary account: Asset, Liability, Owners' Equity, Revenue,
Expense, Budgetary Debit, Budgetary Credit.
- Select either Asset or Expense for statistical accounts. If you enter Asset, the
balance in the account carries forward year to year. If you choose Expense, your
statistical balance zeros-out at the end of the fiscal year.
- Do not change the account type for a value that has been used or has a balance
without first consulting Oracle Support.
• Third Party Control Account: Subledger Accounting maintains the account balance for
third party control accounts by ledger, period, account combination, Party, and Party ID.
• Reconcile: Enter Yes for Reconcile to allow reconciliation for natural accounts that
should balance to zero. (Not supported in Oracle Fusion V1.)
• Financial Category: Financial Category is used with Oracle Transactional Business
Intelligence reporting to further identify groups of accounts. The is required if you want to
run the Payables to General Ledger Reconciliation report or the Receivables to General
Ledger Reconciliation report.

Control Accounts Benefits
• Error prevention: Prevent

users from entering data
from unauthorized sources.
• Improved data integrity:
Allow only approved
sources to post to an
account.
• Streamlined reconciliation:
Enforces consistency
between the source system
and the GL account
balance by not allowing you
to enter GL journals against
control accounts.
You cannot enter GL journals against control accounts because that would make the source
system and the GL system out of balance.

Control Accounts Explained
When defining your natural account segment values, you can designate an account as a
control account using the attributes on the Manage Values page from the Setup and
Maintenance work area. Select one of the following options:
• Customer: You can only use that account when you enter customers, such as
Receivables invoices. Any subledger journal entry lines which use that account must
include customer information.
• Supplier: You can only use that account where you enter suppliers and supplier sites,
such as Payables invoices. Any subledger journal entry lines which use that account
must include supplier information.
• Third Party: You cannot enter manual journal entries from General Ledger or Subledger
Accounting.
• Restrict Manual GL Journals: You cannot enter manual journals from GL, but you can
enter journals from Subledger Accounting.
• No: Not a control account.

Practice 7-5 Overview: Entering Values

• Adding new values.
• Setting value attributes.

Defining Hierarchies
• A given segment in the chart of accounts can have multiple

hierarchies.
• Each hierarchy can have multiple versions.
• Financial results from any accounting period can be analyzed
by using any version of any account hierarchy.
• Create account hierarchies (trees) to identify managerial, legal, or geographical

relationships among your value set values.
• Define date-effective tree versions to reflect organizational changes within each
hierarchy over time.
• Publish multiple hierarchies to balances cubes to allow for financial reporting and
analysis of past, present, or future data.
Note: Oracle Fusion Applications offers ready-to-use integration with Oracle Hyperion Data
Relationship Management (DRM) for management of chart of accounts reference data
including segment values, business rules, cross-validation rules, and hierarchies. If you
decide to implement DRM integration with Oracle Fusion Applications, chart of accounts
values and account hierarchies (trees) are maintained in DRM rather than in Oracle Fusion
Applications.

Account Hierarchy Purposes
Create multiple hierarchies for different purposes. For example,

define three different hierarchies to be used for each chart of
accounts segment that has rollups, each for a particular purpose:
1. Hierarchies for financial reporting: Must be published to
Essbase cubes.
2. Hierarchies for allocations: Must be published to Essbase
cubes.
3. Hierarchies for cross-validation rules, revaluation, and chart of
accounts mapping: Do not publish to the Essbase cube
because multiple child assignments are not supported in the
Essbase cube.
• Hierarchies for financial reporting: Child values in these hierarchies cannot roll up to
different parents within a hierarchy because this functionality is not supported when you
publish such hierarchies to Essbase.
• Hierarchies for allocations: Used with Calculation Manager in creating allocation rules.
• Hierarchies for cross-validation rules, revaluation, and chart of accounts mapping:
- Are created within the same hierarchy and must be associated with a chart of
accounts instance.
- Associate only one hierarchy with a chart of accounts instance, per segment.
- Can have the same child roll up to different parents.
- Are not available for reporting and allocations.

Account Hierarchy Example
Note: In the rare cases in which you can use the same hierarchical account relationships for
financial reporting, allocations, cross-validation rules, revaluations, and your chart of accounts
mapping definition, you can define just one hierarchy.

Create Account Hierarchies
Use the Manage Account Hierarchies page to search for, create,

and edit account hierarchies.
To create a hierarchy:
1. Click the Create Tree icon to open the definition of the tree.
2. Enter the name, code, tree structure, and description for the
tree.
3. Enter the data source parameters to designate the value set
and whether parent or detail values are used in the hierarchy.
Note: You can use the Rapid Implementation spreadsheet to
create account hierarchies as discussed in the previous chapter.
Note: The Rapid Implementation spreadsheet can be used to maintain and create hierarchies.
The spreadsheet automatically:
• Creates two versions of your hierarchy (Baseline and Current).
• Runs the flattening and auditing programs.
• Sets their status to Active.
• Publishes all hierarchies for you.

Create Account Hierarchies Version
1. Search for the tree you just created to add a tree version.
2. Enter the name, description, and effective start date for the
tree version.
3. Select the data source values to use.
4. Use the Audit Results section to start the Audit process to
verify the correctness of the tree.
5. Use the Column Flattening and Row Flattening features in the
Actions menu to:
– Optimize parent/child relationships.
– View information for run-time performance that is stored in an
additional column in a table for all parents of a child.
6. Use the Set Status feature in the Actions menu to set the
status to active and activate the hierarchy.
Note: You can create additional tree versions from the Rapid Implementation Enterprise
Structures spreadsheet.

View Account Hierarchies
• Manage and review your account hierarchies more efficiently

both online and offline.
• View segment value descriptions when creating, editing, or
reviewing account hierarchies.
• Export account hierarchies from the tree version to a
spreadsheet for review, analysis, and reporting offline.
Manage Account Hierarchies: Specify Nodes

Navigate to: Setup and Maintenance > Manage Account Hierarchies > Search > Expand
Name > Click the version (if created or create the version) > Click Next.
Viewing account hierarchies is available from the tree version when you are creating or
editing the tree version. If you want to review and export all nodes in the hierarchies to a
spreadsheet, you must expand all nodes first from View -> Expand All before reviewing or
exporting.

Published Account Hierarchy Example
• Each combination of a tree plus tree version is published as a

different account hierarchy to the balances cube.
• To uniquely identify values in trees, each chart of accounts
value in the hierarchy is assigned a fully qualified member
name path in the cube to guide in selecting values during
general ledger processes.
• When a chart of accounts detail or parent value is assigned to
multiple tree versions, the fully qualified member name path
includes the tree version name.

Single Account Hierarchy
Only a single tree version, V1, exists when a financial report is

defined.
• The tree version includes the chart of accounts value 500 for
a cost center.
• The path does not include a tree version name, because only
one tree version is in the cube.
• The fully qualified name path will be 500.
Rapid Implementation spreadsheets automatically creates a baseline version and a current

version.
If you manually create your hierarchies, you should create two versions, such as baseline and
current, where the baseline hierarchy's effective date occurs before the current hierarchy's
effective date. If you do not create two versions, when you create a new hierarchy version, it
changes the fully qualified member name and you must then update every report and
allocation definition that was defined.

Published Account Hierarchy V2 Example
A new tree version V2 is published.

• The fully qualified member name path changes because two
versions are now available.
– [All VF Cost Centers-V1].[999].[500]
• Any configurations in financial reports, allocations, and Smart
View queries that referenced the original fully qualified name
path 500 must be updated to use either of the following new
names:
The fully qualified member name path for a member may change if you originally published a
single hierarchy to a cube and later published another hierarchy that includes the same chart
of accounts value.
If the fully qualified member name path changes, you must update existing financial reports,
allocation rules, and Smart View template that refer to that member. Otherwise, such
processes will have errors.
Important: Creating two hierarchies in the beginning eliminates the need to update your
reports and rules.
For more information, see: Oracle Fusion General Ledger Hierarchies: Recommendations
and Best Practices (Doc ID 1520970.1) on My Oracle Support.

Troubleshooting
Issue Possible Resolution
Tree Version Audit • Make sure parent values have the summary attribute set
Process Fails correctly.
When Activating • Make sure you did not mistakenly assign children to
Version. child values.
• Fix could be as simple as switching the summary
attribute flag. However, if you mistakenly made a parent
value a child value and posted transactions to that
account, then a more intensive data fix may be required.
Tree Hierarchy • Submit the process to propagate and update required
Defined in Oracle account hierarchies to the Essbase GL balances cube
Fusion GL Is Not from the Publish Account Hierarchies page.
Available in • Check that the Publish option is enabled for the versions
Essbase GL that are to be published.
Balances Cubes.
• Check that a request ID is returned and the process
completes successfully after you click the Publish action
button.

Troubleshooting
Issue Possible Resolution
Error in Publish Account Make sure all users sign out of Financial
Hierarchies or Publish Reporting, Smart View, and Calculation Manager
Chart of Accounts during the submission of the publish process. You
Dimension Members and cannot have users connecting to the cube while
Hierarchies programs. running these programs.
Need a new accounting • New scenario members are added in the
scenario member to load predefined value set called Accounting
budget and forecast data Scenario.
into Essbase GL balances • Query this predefined value set, and add a new
cubes. value for each budget or forecast that is needed
to be tracked in Essbase GL balances cubes.
Enabled or disabled • Enabled or disabled flexfield security policies
flexfield security policies are not automatically applied to the Essbase
are not in effect for cube if set up after the cube was created.
Essbase GL balances • Account hierarchies must be republished in
cube. order to apply newly enabled or disabled
flexfield security policies.
Note: Flexfield security is enabled and disabled in the Manage Value Set page.

Practice 7-6 and 7-7 Overview: Searching, Completing,
and Publishing Your Accounting Hierarchy
These practice cover the following topics:
• Searching for your tree.
• Searching for your tree version.
• Completing your account hierarchy.
• Publishing your account hierarchy.

Enabling Account Combinations
• New account combinations are always enabled.

• An account combination cannot be deleted.
• To discontinue using an account combination, deselect the
Enabled check box for the account combination or use the To
Date to end date the account combination.
• The From Date is used to enable an account combination as
of a particular date.
For example, if you have a new department as of January 1, 2017, you can create an account
combination with a From Date of 01-JAN-2014 and the account combination becomes
enabled on that date. This functionality enables you to create the account combinations in
advance.
To create an account combination, navigate from the Setup and Maintenance work area to
the Manage Account Combinations page. Additionally, you can set the following attributes
from 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 for transactions and journal entries.
• Alternative Account: To use an alternative account combination when this one is
disabled.

Practice 7-8 Overview: Creating an Account
Combination
This practice covers the following topic:
• Creating an account for your Sales cost center.

Manage Segment Value Attributes
Oracle Fusion General Ledger eases chart of accounts

maintenance by automatically replicating changes to segment
value attributes of the account combinations that contain that
segment value.
For example, if you enable a particular cost center segment value that had been disabled
previously, navigate to: Setup and Maintenance > Maintain Segment Value Attributes to run
the Inherit Segment Value Attributes process and re-enable all account combinations
containing that cost center automatically.
Prevent selected account combinations from being affected by segment value attribute
changes by selecting the Preserve Attribute check box on Manage Account Combinations.
• Use the Segment Value Inheritance Exception Report to view the account combinations
that have been changed.
• Individual segment value attributes override account combination attributes.
• An account combination is composed of several segment values. If these segment
values have conflicting settings for Enabled, Allow Posting, From Date, or To Date, the
most restrictive of the settings for any of the individual segment values applies to the
account combination.
• If you disable a segment value, the combinations that contain that value can no longer
be used, even if the Preserve Attributes check box is selected.
Note: You can also disable an account combination or change other attributes in the Manage
Account Combination page.

Segment Value Security
Controls access to value set values associated with any segment

in your chart of accounts.
Create and edit segment value security on the Define Chart of
Accounts page from the Setup and Maintenance work area.

Defining Segment Value Security Rules
Set up segment value security rules against your value sets to

control access to parent or detail segment values.
• Secure a value set to deny access to all values by default.
• Create conditions and assign them to specific data roles to
control access to your segment values.
• Restrict data entry, online inquiry, and reporting to specific
values by using segment value security rules.
For example, create a segment value security rule that grants a
user access only to his or her own department.
Note: Segment value security is enforced in Oracle Fusion
Applications wherever the chart of accounts values are used.
A distinction between setup and transaction user interfaces is that segment value security
prevents you from seeing certain account values in transaction user interfaces, but you can
still see the account combinations with the secured values in setup user interfaces.
• If you try to update the field in the setup user interface, you won't be able to use those
values.
• For transaction, balance, and activity query user interface, the segment value security
prevents both the viewing and using of the secured values.
• Segment value security control is both for Read and Write access control.

General Points About Segment Value Security
• Specifies that data security be applied to the values in the

segments that use the value set.
• Applies at the value set level. If a value set is secured, every
usage of the value set in a segment is secured.
• Applies only to independent value sets.
• Applies mainly when data is being created or updated, and to
account combination tables for query purposes.
Co CC Acct I/C
• Based on the roles provisioned to users, data security policies determine which values
of the segment end users can view or modify.
• Controls access to parent or detail segment values.
• For example, if the same value set is used for the balancing segment and intercompany
segment of a chart of accounts, then the same security rules apply to both. Thus, if you
create a security rule that only allows you to access balancing segment value 01, then
you are able to only perform intercompany transactions against company 01. Therefore,
if you enable segment value security rules by balancing segment, you should use two
different value sets for the company and intercompany segments.

Segment Value Security Examples
Security Security
condition Data role policy
General associated
Cost Center Accountant with the Cost
Equal to – Vision US Center value
Accounting set
Example
Security Security
condition Data role policy
General associated
Account Accountant with the
Equal to – Vision US Account
US Revenue value set
Create conditions and assign them to specific data roles to control access to your segment
values. For example:
• Enable security on both the cost center and account value sets that are associated with
your chart of accounts.
• Assign the General Accountant – Vision US data role to the user so the user has access
to cost center Accounting and account US Revenue.
• Deny all other users access to all cost center and account value set values.
When access is granted by using segment value security conditions and data access roles for
a ledger:
• Use only the allow account values not restricted by the security rule in entering a
journal.
• View only balances for accounts during running reports.
When viewing ledger options or other setup pages in an accounting configuration, if the
accounts specified include references to an account with values to which you have not been
granted access, then you can see the account but cannot modify the secured values.

Segment Value Security Operators
Operator Usage
Equal To Secures a specific detail value. You cannot
use this operator to secure a parent value.
Not equal to Secures all detail values except one that you
specify. You cannot use this operator to
secure a parent value.
Between Secures a range of detail values.

Is descendant of Secures the parent value itself and all of its
descendants, including mid-level parents and
detail values.
Is last Descendant of Secures the last descendants (that is, the

detail values) of a parent value.
Use any of the following operators in your conditions to secure your segment values.
Note: For Is descendant of and Is last descendant of:
• Specify an account hierarchy (tree) and a tree version to use this operator.
• Notice that the security rule applies across all the tree versions of the specified
hierarchy, as well as all hierarchies associated with the value set.

Segment Value Security Rules and
Hierarchies Example
Retrieve Derive Apply security List of values is

account effective condition to accessible across
hierarchy version get the list of all versions of the
from based on descendants secured hierarchy,
security system based on the and across all
rule. date. effective tree hierarchies
version. associated with the
value set.
Example
Legend
Management hierarchy Geographical hierarchy
2010 version 2011 version 2010 version

Access
Granted
100
100 100
200 300 400 Access
101 200 300 200 300 Denied
201 301 302 401 402

201 202 203 301 302 101 201 202 301 302
• Retrieve account hierarchy from security rule: in the Management hierarchy the 2010
and 2011 versions specify that the parent value 100 is secured by means of the Is
descendant of operator.
• Derive effective version based on system date: In the Management hierarchy the 2011
version is the effective tree version based on the system date.
• Apply security condition to get the list of descendants based on the effective tree
version: The parent value itself and all its descendants are secured based on the
effective tree version. The values in the 2011 version are: 100, 200, 300, 101, 201, 202,
301, and 302.
• List of values is accessible across all versions of the secured hierarchy, and across all
hierarchies associated with the value set:
- In Management hierarchy: 2010 version, 203 is denied access. All other values
can be accessed.
- In Geographical hierarchy, 400, 401, 402 are denied access. All other values can
be accessed.

Segment Value Security Rules with Hierarchies
• Segment value security rules must be defined before account

hierarchies are published to the cube to be effective.
• For changes with hierarchical segment value security rules, or
changes in a referenced hierarchy, republish the tree versions
affected by the rule change for rules to be effective in the
cube.
• Multiple processes need to be run for hierarchy changes,
including:
– Auditing
– Activating
– Row and column flattening
When you create new segment value security rules or change an existing rule that is based
on a hierarchical filter, you must republish the tree versions affected by the rule change using
the Publish Account Hierarchies page.
• Republishing is required for the segment value security to become effective in the cube.
• Changes to an account hierarchy previously published to the balance cube must be
republished to the cube to reflect the updated hierarchy.

Changes to an Account Hierarchy Referenced in
Segment Value Security Rules
• Tree is set from an active to a draft state.
• The rules referencing the account hierarchy become
noneffective.
• After the hierarchy changes have been completed:
– Submit the hierarchy for audit.
— The hierarchy is set back to an active status.
— The rules referencing the account hierarchy are effective again.
– Run the row and column flattening programs to make the list of
values available and properly secure the account values.
– Run the Maintain Value Sets and Maintain Chart of Account
Hierarchies.
– Submit the Process Account Hierarchies program to
automatically run these account hierarchy-related
processes in one submission.
The Maintain Value Sets and Maintain Chart of Account Hierarchies processes update the
data that is required to regulate ledger and data access security by storing the primary
balancing segment values assigned to a ledger and the specific child balancing segment
values assigned to a data access set through parent value assignments.
The Process Account Hierarchies process automatically runs the following child processes:
• Tree Audit and Tree Activation
• Tree Row Flattening
• Tree Column Flattening
• Maintain Value Sets
• Maintain Account Hierarchies
• Publish Hierarchies (You can choose not to run this process.)

Implementation Considerations
Submit the Publish Chart of Accounts Dimension Members and

Hierarchies program to update the balances cube for chart of
accounts value set and hierarchy changes.
• If you did not make changes to the hierarchy assigned to a value set, select Yes in the
Publish Detail Values Only field.
• If you are using hierarchies for your segment value security rules, publish the hierarchy
from the Manage Hierarchies page.
• You don't have to use hierarchies for segment value security, but if you want your
reports to report on hierarchies that conform to hierarchical segment value security, you
need segment value security rules.
• In the parameters, you select a value set and whether to publish detail values (child
values) only. If you did not make changes to the hierarchy and simply enabled or
disabled segment value security rules, then you can run this program from the
Scheduled Processes page and select Yes to publish Detail Values Only. Publishing an
entire hierarchy has a performance cost, which is why this option exists. For example, if
you have 20 hierarchies, then publishing all 20 could take a long time.

Implementing Segment Value Security
In Oracle Identity Manager (OIM):

• Create a role by giving it a
name.
• Use an underscore between
each word in the name.
• Define a user-friendly display
name with a hyphen before the
SVS role.
For example, define a name of
ACCOUNTING_COST_CENTER-
SVS_ROLE and a display name
for the Accounting Cost Center-SVS
role.
For segment value security roles, the best practice is to give them a common suffix, such as
SVS (segment value security), to more readily identify them. You can assign these custom
roles a role category of Default.

Segment Value Versus Data Access Set Security
• Segment value security rules assigned to the user through

various roles that reference the same secured value set are
always in effect simultaneously.
• Data access set security is different depending on whether the
General Ledger features being secured are based directly on
the balances cube.
– Assign multiple data access sets referencing the same
balances cube to a user.
— For features not directly related to the balances cube, the ledger
and primary balancing segment values access applies as defined
in the selected data access set.
— For features related to the balances cube, the cumulative effect of
the combined data access sets ignores the segment value security
rules and gives access to all primary balancing segment values for
all ledgers.
Segment value security rules:

• Are specified for a particular value set.
• Work directly or indirectly with the balances cube.
The following General Ledger features are based directly on the balances cube:
• Inquire on Detail Balances
• Account Monitor
• Account Inspector
• Financial Reporting
• Smart View
• Allocations
All other General Ledger features are just indirectly based on the balances cube.

Note: Balance cube security for a data access set is defined as either:
• Full Ledger.
• All Values, in the case of the Specific Balancing Segment Value access type. These will
be treated as the user having access to all values of the balancing segment value set.

Cross-Validation Rules
• Prevent the creation of invalid account combinations by

setting up cross-validation rules.
• Define cross-validation rules before entering account
combinations.
• Use cross-validation rules in combination with dynamic
insertion.
• Controls the combinations of values you can create when you are setting up account
combinations.
• Defines whether a value of a particular segment can be combined with specific values of
other segments.
• Differs from segment value security rules validation, which controls access to a segment
value rather than preventing a combination of segment values.
• Used to prevent the creation of combinations that should never exist, such as preventing
balance sheet accounts from being combined with cost centers for revenue and
expenses.

Cross-Validation Rules Considerations
• Validates and applies only to new accounts. You should

define and enable cross-validation rules prior to entering
accounts.
• Does not affect existing accounts.
Note: Revise cross-validation rules at any time, but remember
that they prevent only the creation of new invalid account
combinations.
Navigate to: Setup and Maintenance > Manage Cross-Validation Rules or Create Cross
Validation Rules in Spreadsheet.

Dynamic Combination Creation Allowed
• Enable this feature to permit users to create new account

combinations as they enter data.
• If the feature is not enabled, you can enter only new account
combinations of segment values using the Manage Account
Combinations page.
• Cross-validation rules are important even if this feature is not
enabled to prevent creation of invalid combinations
accidentally.
Navigate to: Setup and Maintenance > Manage Chart of Account Structure Instance > Search
> Manage Structure Instances button > Create.
When setting the Dynamic combination creation allowed option, consider the following
features.
• You can allow account combinations to be added automatically as you enter them in
transactions, including when you define a ledger. Alternatively, you can require all
accounts to be defined manually in the Manage Accounts Combinations window.
• Frequently, companies enable Dynamic combination creation allowed while they are
entering historical data from a legacy system. They then disable the feature to ensure
tighter control over the creation of new account combinations.

Filters Overview
Use Condition and Validation filters:

• To narrow down the search the application has to do before
performing validation.
• To determine whether an account combination is created.
Navigate to: Setup and Maintenance > Manage Cross-Validation Rules.

• Filter example: If you enter company Equals 102 as a filter, the application validates
only new account combinations with 102 as the company value.
• Condition example: Enter company 102 and cost center 139 with Does not equal
operators to prevent any account combinations from being created with those two
values, regardless of the other values used in the account combination.

Filters and Conditions
The following operators are available for both the Condition Filter
and Validation Filter.
Navigate to: Setup and Maintenance > Manage Cross-Validation Rules.

Note: In the Create Cross-Validation Rules spreadsheet you cannot select some operators.
Only the following three operators are supported. The application substitutes the operator if:
• A detail value is provided: Equals operator.
• Two values are provided separated by a hyphen (-): Between operator.
• A parent value is provided: Is Descendant Of operator.

Practice 7-9 Overview: Defining Cross-Validation Rules
in a Spreadsheet
• Creating a new cross-validation rule.
• Adding a condition to the rule.
• Adding a validation filter to the rule.
• Testing the rule.

Manage an Accounting Calendar
Create a calendar to define an accounting year and the periods

that it contains.
• Specify common calendar options that the application uses to
automatically generate a calendar with its periods.
• Define your calendar with at least one year before the period
in which you start entering transactions or uploading historical
data.
• Make choices carefully when specifying the options, because
changing your accounting calendar is difficult after a period
status is set to open or future enterable.
• Do not change the name of the period after it is used.

Accounting Calendar Considerations
• Foreign currency translations cannot be performed in the

initial period opened for your ledger.
• Select the earliest period carefully. After you open the first
accounting period, prior periods cannot be opened.
When the next accounting period is opened, Oracle Fusion Applications rolls balance sheet
account balances forward to the new period where the beginning balance is taken from the
ending balance of the prior period except when the new period crosses fiscal/calendar years.

Start Date
• Start Date specifies a calendar start date that is a full year

before the start date of the year of the first translation period
for your ledger.
• Remember that translation cannot be run in the first period of
a calendar.
– Translation requires that the first period that is translated for the
ledger must be at least the second defined period in the
ledger's calendar.
– Translation derives an opening balance based on the prior
period's ending balance.
Important
Consider how many years of history to load from your previous system. Calculate the start
date back to one period before the beginning of the history.

Period Frequency
Period Frequency:
• Use period frequency to set the interval for each subsequent
period to occur.
• For example, monthly, quarterly, yearly, 4-4-5, 5-4-4, or 4-5-4.
Adjusting Period Frequency
• Use the adjusting period frequency to control when the
application creates adjusting periods.
• The default is None, which adds no adjusting periods.

Period Name Format
Period Name Format section: User-Defined Prefix

• Optionally, enter your own prefix.
• For example:
– Define a weekly calendar.
– Enter a prefix of Week.
– Enter “-” as the separator.
– Format of Period numberYY fiscal year.
– The application creates the names:
— Week1-11
— Week2-11
— Through Week52-11

Calendar Type
In the Period Name Format section, select the calendar type:

• Calendar Period: Select a calendar period format to append
the period year (matches the calendar on the wall year) to the
prefix.
• Fiscal Period: Select a fiscal period format to always append
the end-of-year date assignment (year of the last period in
year) to the prefix.
January 1
December 31
Period Name Format Section Examples

• Calendar Period: The accounting periods are all appended with the year in which they
occur based on the calendar.
• Fiscal Period: If the accounting periods in the set of twelve are all assigned the year of
2012, then 2012 is appended to the period name of all 12 periods depending on the
period format selected regardless of the year the period is actually in. For example, for a
fiscal year starting on June 1, 2015 and ending on May 31, 2016, all the periods would
be assigned 2016, so September 2015 would be assigned the date of September 2016
in the fiscal calendar.
Note: The list of values is filtered based on the selected separator and displays only the
options that match the selected separator.

Calendars with Different Period Frequencies
When you are using the period frequency of Other, you must
manually enter the calendar.
• Select the period frequency of Other.
• Enter the number of periods for alternative frequencies.
• Enter the start and end dates manually.
OTHER

Calendars with Different Period Frequencies
The application generates the period names, year, and quarter

number.
• For example, select the period frequency of Other and enter
52 as the number of periods when you want to define a
weekly calendar.
• The period format region is hidden.
• The application generates a temporary
period name using a fixed format of
Period numberYY.
• You can override this format with
your own customized period names.
In Oracle Fusion Applications a calendar can have only one period frequency and period type.

Adding a Calendar Year
For manually entered calendars:

• Click the Add Year button on the Edit Calendar page.
– The application populates the field with the next year or creates
a blank year, depending on your period frequency.
• If a blank year is created, manually enter the periods for the
new year.
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.

Practice 7-10 Overview: Verifying Your Calendar

• Searching for your calendar.
• Reviewing your calendar.

Calendar Auditing
• Calendar validation is automatic and prevents serious

problems when you begin using the calendar.
• After you set a calendar period status to open or future
enterable, you cannot edit the period.
• The calendar validation runs automatically when you save the
calendar.
• Audits your accounting calendars to check for common setup errors. This feature
strengthens controls during implementation and prevents potential processing problems
related to invalid calendar definitions.
• Performs online checking of errors such as the wrong number of days assigned to a
period or nonadjusting periods that have overlapping days.
• Provides online feedback in the form of error messages as the process checks for
validation errors such as date omissions, overlapping nonadjusting periods, and
nonsequential periods.

Manage Currencies Overview
• Oracle Fusion Applications provides full cross-currency

functionality to meet the needs of global companies.
• Currency functionality is designed in accordance with:
– United States Statement of Financial Accounting Standards 52
(SFAS #52)
– International Accounting Standards 21 (IAS 21) requirements

Currency Concepts
The following three currency processes are performed in Oracle Fusion Applications:
• Conversion: Refers to cross-currency transactions that are converted during the
accounting transformation to the currency of the ledger in which the transaction takes
place.
• Revaluation: Adjusts asset or liability accounts that may be materially understated or
overstated at the end of a period due to a fluctuation in the conversion rate between the
time the transaction was entered and the end of the period.
• Translation: Restates an entire ledger or a set of balances for a company from the
ledger currency to a reporting currency.

Currency in Subledgers
• Many foreign-denominated transactions are originally entered and then settled in feeder
systems such as Oracle Fusion Payables and Oracle Fusion Receivables.
• Oracle Fusion subledgers share the same Oracle Fusion General Ledger rate table.
• Different conversion rate types enable each subledger to convert transactions at
different rates daily.
• Corporate procedures can assist in entering and maintaining conversion rates and
avoiding inconsistencies.

Define Currencies Overview
In the Setup and Maintenance work area locate the Define

Currencies task list and navigate to the tasks needed to
successfully implement your currencies.
• Use the predefined International Standards Organization (ISO) currencies or create new
ones.
• Enable the STAT currency, which is predefined, to record statistical data, such as
employee headcount, labor hours, or units sold. Statistical data is used in allocation
journal calculations to spread related costs over different cost centers. For example, in a
manufacturing operation, use labor hours to allocate the costs of a product to the
different cost centers that performed the work.
The Define Currencies task list consists of the following tasks:
• Manage Currencies: Enable and create currencies to use when recording cross-
currency transactions and running accounting processes.
• Manage Conversion Rate Types: Create and manage conversion rate types to
categorize the relationships between your currencies and daily rates.
• Manage Daily Rates: Enter and manage daily, periodic, and historical rates used to
record transactions or in processes involving multiple currencies.
Note: The Manage Conversion Rate Types and the Manage Daily Rates tasks open the
Currency Rates Manager page.

Currencies Overview
• Create currencies to use, for example, for reporting purposes

or in cases of newly created countries or currencies.
• Use any of the ISO currencies to:
– Display monetary amounts in
other currencies.
– Assign them to ledgers.
– Enter cross-currency
transactions and journal
entries.
– Record balances.
When creating or editing currencies, consider these points:

• Currency Codes: After a currency is enabled, the currency code cannot be changed,
even if you later disable that currency.
• Date Ranges: Currency codes can be selected only for the dates within the date range
defined. If you do not enter a start date, then the currency is valid immediately. If you do
not enter an end date, then the currency is valid indefinitely.
• Symbols: Some applications use currency symbols. Others, such as Oracle Fusion
General Ledger, do not, even if the currency is defined with a symbol.
• Euro Currency Derivation: Derivation Type, Derivation Factor, and Derivation Effective
Date fields are used to define the relationship between the official currency (euro) of the
European Monetary Union (EMU) and the national currencies of new EMU member
states during their transition period.
Note: If you need to use a different currency code than EUR for the euro currency, you can
disable the predefined EUR currency code and create the new one.
By default, all ISO currencies are enabled. When you open the Currency list of values across
applications, you see every defined currency which can impact transaction entry. if they only
use a handful of the currencies, disable the other currencies to reduce the list of values.

Practice 7-11 Overview: Reviewing and Creating
Currencies
• Verifying what currencies are enabled.
• Creating a new currency.

Conversion Rate Types: Overview
Conversion rate types are assigned to currency rates to convert

cross-currency amounts to ledger currency equivalents.
Navigate to: Setup and Maintenance > Manage Daily Rates > Rate Types tab.
Oracle Fusion General Ledger predefined conversion rate types are:
• Spot: Represents rates for a specific date. Usually entered daily.
• Corporate: Represents standard rates determined by senior financial management and
used over a period of time throughout your enterprise. Usually used with stable
currencies that have minor fluctuations over time.
• User: Represents rates entered by users during cross-currency journal entry creation for
infrequently used currencies or currencies that fluctuate over time.
• EMU Fixed: Represents rates used by countries joining the European Union during the
transition period to the euro currency from their national currency.
Note: Define additional rate types to use with rates for special needs.

Cross-Currency Functionality
• Records transactions, journal entries, and reports in any

currency.
• Enters daily rates online or automatically.
• Performs currency conversion online and in real time.
• Complies with Generally Accepted Accounting Principles
(GAAP)
Automatically
Calculated
Entered Entered

Explain Cross-Rate Rules
Cross-rates facilitate the creation of daily rates by automatically

deriving the rates from the relationship between contra currencies
and a pivot currency.
• Pivot Currency: A currency linked to the two contra currencies
to enable the automatic creation of the daily rates between the
contra currencies. Select a pivot currency that is commonly
used in your currency conversions and is enabled, effective,
and not a statistical currency.
• Contra Currency: A currency other than your pivot currency
that is enabled, effective, and not a statistical currency.
The automatic creation of rates is particularly beneficial for intercompany transactions with
multiple currencies because it ensures consistency among the rates, thereby minimizing the
effect of conversion rate differences during the intercompany elimination process.

Explain Cross-Rate Rules
For example, 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).
From Currency To Currency Rate Inverse Rate
USD EUR 0.7748 1.2907
USD CAD 1.0134 0.9868
• USD is the pivot currency.

• EUR and CAD are the contra currencies.
From Currency To Currency Rate Inverse Rate
EUR CAD 1.3080 .7846
USD is the pivot currency used by the application to create a daily rate between EUR and
CAD automatically. Note: If the Enable Cross-Rates check box is deselected after you enter
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.

Practice 7-12 Overview: Creating Conversion Rate
Types
• Creating a conversion rate type.
• Defining a cross-rates pivot currency.
• Defining two contra currencies.

Daily Rates: Overview
• Define the conversion rate relationship between two

currencies, using a specific conversion rate type on a
particular date.
• Create rates between any two currencies that you have
enabled in your applications instance, regardless of your
ledger currency.
Sharing Daily Rates

Daily conversion rates are shared across all ledgers within an applications instance and are
available when you are entering cross-currency transactions in your Oracle Fusion
subledgers.
Subledger applications share the same daily rates with the general ledger, but different rate
types enable each subledger to convert transactions at different rates.

Entering Daily Rates
• Enter inverse rates independently or have the application

calculate the inverse rate from the entered rate.
• Use the provided spreadsheet template to load daily rates or
you can map the rates directly to the
GL_DAILY_RATES_INTERFACE table to automatically insert,
update, or delete daily rates in the GL_DAILY_RATES table.
Note: The application validates the rows in the interface table
before making changes in the GL_DAILY_RATES table.
Currency Rates Manager

Navigate to: Setup and Maintenance > Manage Daily Rates > Daily Rates tab.
Warning: Always use the interface table to load your daily rates either through the
spreadsheet template or by using other file loading tools. Do not load rates directly into the
GL_DAILY_RATES table. This can corrupt your daily rates data.
Note: Use conversion rate service companies to provide you with rates that can be loaded
into the GL_DAILY_RATES_INTERFACE table automatically.

Practice 7-13 and 7-14 Overview: Using Currency
Rates
• Practice 7-13: Entering Daily Rates.
– Opening the spreadsheet.
– Entering your rates.
– Submitting the spreadsheet.
– Verifying your rates were loaded successfully.
• Practice 7-14: Entering a Currency Conversion Journal.

Define Ledgers
Use your implementation project or Setup and Maintenance work area to define ledgers and
related tasks.

Ledgers and Accounting Configurations
The process of designing the enterprise structure, including the

accounting configuration:
• Starts an implementation.
• Includes determining financial, legal, and management
reporting requirements.
• Requires setting up primary and secondary ledgers.
• Entails making currency choices.
• Involves examining consolidation considerations.
• Serves as a framework for how financial records are
maintained for an organization.

Ledgers and Accounting Configurations
This figure shows the enterprise structure components and their relationships to each other.
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, can include one or
more secondary ledgers and reporting currencies.
• Reporting currencies are additional currency representations of primary ledgers or
secondary ledgers.
• The number of ledgers is unlimited and determined by your business structure and
reporting requirements.

Define Ledger Components
Three types of ledgers are defined in Oracle Fusion General Ledger using the four
components that are already defined: chart of accounts, calendar, currency, and accounting
method.
• Primary Ledger: Main record keeping ledger and a required component in your
configuration. Every accounting configuration is uniquely identified by its primary ledger.
The primary ledger is closely associated with the subledger transactions and provides
context and accounting for them.
• Secondary Ledger: Optional ledger linked to a primary ledger for the purpose of tracking
alternative accounting. A secondary ledger can differ from its primary ledger in its chart
of accounts, accounting calendar, currency, accounting method, or processing options.
• Reporting Currency: Optional, additional currency representation of a primary or
secondary ledger. A reporting currency can differ from its source ledger in its currency
and some processing options, but shares the same chart of accounts, accounting
calendar, and accounting method with its related ledger.

Ledgers and Subledger Accounting
Oracle Fusion Applications reflect the traditional segregation

between the general ledger and associated subledgers.
• Detailed transactional information is captured in the
subledgers.
• Transactions are periodically sent to Subledger Accounting for
creation of journal entries.
• Transactions are imported and posted in summary or detail to
the ledger using Subledger Accounting.
Subledger Accounting is an application that is used to create and
capture transactions. It contains accounting rules that are used to
create detailed journal entries.
Companies account for themselves in primary ledgers and, if necessary, secondary ledgers
and reporting currencies.
• Your transactions from your subledgers are posted to your primary ledgers, and
possibly, secondary ledgers or reporting currencies.
• Local and corporate compliance can be achieved through an optional secondary ledger,
providing an alternative 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, and you can convert your local currency to your parent's ledger currency to
report your consolidated financial results using reporting currencies or translation.

Manage Primary Ledgers
The Primary Ledger:

• Performs as 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 used to book journals to record the impact of subledger transactions.
To determine the number of primary ledgers:
• Begin with your financial, legal, and management reporting requirements.
• Consider corporate year-end and local government regulations and taxation.
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
representing 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 in their ledger currency from your foreign subsidiaries.

Practice 7-15 Overview: Searching for Your Ledger

• Searching for your primary ledger.
• Verifying your primary ledger.

Specify Ledger Options
After configuring your primary ledger, the next step is to specify your ledger options. These
options:
• Control many of the accounting processes and defaults that are used in both the general
ledger and the subledgers.
• Are required if marked with an asterisk *.
• Require the account combinations to be created in advance or dynamic inserts to be
turned on at the chart of accounts instance level to enter the Retained Earnings and
other accounts.
• Note: Dynamic inserts can be toggled off and on if you want them to be turned
off after setting up the ledger options page.
• Affect balances and journals.

Processes Using Ledger Options
• Year-End Closing
• Translation
• Journal Posting
• Revaluation
• Year-End Closing: Open the first period of a new year to update the Retained Earnings
accounts by moving the net balance from your revenue and expense account to the
Retained Earnings accounts by balancing segment.
• Translation: Run to translate your ledger currency to another currency. Any currency
exchange difference is posted to the Cumulative Translation Adjustment account.
• Journal Posting: Run to update balances. The posting process handles all balancing
including suspense, entered currency, intercompany, and rounding.
• Revaluation: Run to calculate unrealized gains or losses on foreign currency fluctuations
on transactions.

Practice 7-16 Overview: Verifying Your Ledger Options
This practice covers the following sections on the Specify Ledger

Options page:
• Accounting Calendar
• Subledger Accounting
• Period Close
• Journal Processing
• Sequencing
• Average Balance

Balancing Segment Value Assignments: Overview
• Assignment of primary balancing segment values to legal

entities and ledgers is performed within the context of a single
accounting setup.
– If you assign balancing segment values, you limit your ledger
transactions to just those values you assigned.
– If you do not assign balancing segment values, then all
balancing segment values are available for journal and
transaction processing.
• Assignment to legal entities is a best practice and is used
more often than assigning balancing segment values to
ledgers.
• If you are implementing intercompany features, then assigning
balancing segment values to legal entities is mandatory.
For example, if one ledger is recording transactions for three legal entities and another is
recording transactions for two legal entities, assigning balancing segment values to your legal
entities and ledgers simplifies the list of values on journal entries and transactions.

Balancing Segment Value Assignments to Legal
Entities
• Assign values to legal entities before assigning them to the
ledgers.
• Use the values to identify legal entities during transaction
processing and reporting.
• Use the values to ease accounting for your operations to
regulatory agencies and tax authorities.
Navigate to: Setup and Maintenance > Define Ledgers > Define Accounting Configurations >
Assign Balancing Segment Values to Legal Entities

Balancing Segment Values Assignments to Ledgers
• Assign specific primary balancing segment values to your

primary and secondary ledgers to represent nonlegal entity-
related transactions such as adjustments or top-side entries.
• Assign each balancing segment value to a legal entity only
once.
Navigate to: Setup and Maintenance > Define Accounting Configurations > Assign Balancing
Segment Values to Ledgers
Example: Your company hires a law, accounting, or consulting firm to do some legal or tax
work related to incorporation to determine the most advantageous legal entity configuration
for their organization. You don't want to charge that cost to any one legal entity but would
prefer to book it to the corporate ledger for now. You would charge the ledger-based
balancing segment value instead of legal entity-based balancing segment value. You can
allocate charges to the legal entities after you have determined an appropriate way to
distribute the cost.

Balancing Segment Value Assignment Report
• Shows all primary balancing segment values assigned to legal

entities and ledgers across accounting setups.
• Ensures the completeness of your accounting configuration
and the accuracy of your assignments.
• Enables you to quickly identify these errors and view any
unassigned values.
Use the Scheduled Process page to run the report.

• Navigate to: Tools > Scheduled Processes
• Enter the parameters:
- Value Set
- From Balancing Segment
- To Balancing Segment
- Assignment Status for All, Ledger only, Legal Entity only, or Unassigned
- Accounting Configuration (ledger name)
- Show Only Balancing Segment Values with Multiple Assignments – Default is No.
• Submit.

Practice 7-17 Overview: Verifying Legal Entities and
Balancing Segments Assignments
• Assigning your legal entity to your ledger.
• Verifying your legal entity and business segment assignments.

Manage Reporting Currencies
• Reporting currencies maintain and report subledger

and general ledger journal entries or balances
in additional currencies.
• Each primary and secondary ledger is defined with a ledger
currency.
• Reporting currencies:
– Record your business transactions and accounting data for that
ledger.
– 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.
– Conform to local requirements, for example, paying transaction
taxes is easier using a local currency.
Note: Many countries require that one of your ledgers be kept in their national currency.
With Reporting Currencies, you can produce financial statements using the national currency
or alternate currencies.

Manage Reporting Currencies
Business Reasons to Use Reporting Currencies

• Useful for consolidation reporting and analysis.
• No need to physically move balances to create views of consolidation data.
• Beneficial for parent consolidation entities that share the same chart of accounts and
calendar with their subsidiaries.

Reporting Currencies Conversion Levels
A reporting currency is linked to a primary or secondary ledger and can be maintained at one
of three data conversion levels.
• Balance level: Only general ledger balances are maintained in the reporting currency
through the Translation process. Typically the least expensive, requiring duplication of
only the balance level information.
• Journal level: General Ledger Posting process transfers the journal entries to the
reporting currency.
• Subledger level: Subledger Accounting creates the subledger journals to the reporting
currency. General Ledger converts the remaining journal entries to the reporting
currency during the Posting process.
Note
• Journal and subledger data conversion levels require more storage and processing
because most general ledger and subledger journals, plus general ledger balances, are
replicated.

• Do not use journal or subledger-level reporting currencies if your organization needs to
translate your financial statements only to your parent company's currency for
consolidation purposes. Standard translation functionality meets this need.
• A full accounting representation of your primary ledger is maintained at the subledger-
level reporting currency. Secondary ledgers cannot use subledger-level reporting
currencies.

Practice 7-18 Overview: Defining Reporting Currencies

• Creating reporting currencies.
• Assigning ledger options.
• Assigning currency translation options.
• Entering error handling options.
• Defining journal conversion rules.

Define Secondary Ledgers
A secondary ledger is an additional ledger linked to a primary ledger for the purpose of
tracking alternative accounting.
• Differs from its primary ledger by using a different accounting method, chart of accounts,
accounting calendar, currency, and/or processing options.
• Receives all or some of the journal entries processed in the primary ledger, based on
your configuration options.

Secondary Ledgers Scenarios
If the primary and secondary ledgers use different:

• Charts of accounts: The chart of accounts mapping is required
to instruct the system how to propagate journals from the
source to the target chart of accounts.
• Accounting calendars: The accounting date is used to
determine the corresponding nonadjusting period in the
secondary ledger. The date mapping table provides the
correlation between dates and nonadjusting periods for each
accounting calendar.
• Ledger currencies: Currency conversion rules are required to
instruct the system 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.

Secondary Ledgers Conversion Levels
Secondary Ledgers use one of the four conversion levels:

• Balance Level: Transfer Balances to Secondary Ledger process transfers only balances
to the secondary ledger.
• Journal Level: General Ledger Posting process transfers the journal entries to the
secondary ledger.
• Subledger Level: Oracle Fusion Subledger Accounting creates the subledger journals to
both the primary and secondary ledger. The Posting process transfers the remaining
journal entries to the secondary ledger.
• Adjustment Only: Adjustment only secondary ledger is an incomplete accounting
representation that holds manual or automatic adjustment journal entries from General
Ledger or Oracle Fusion Subledger Accounting. This conversion level requires that the
secondary ledgers share the same chart of accounts, accounting calendar, and currency
with its primary ledger. A complete accounting representation is achieved by creating a
report that includes both the primary and secondary ledger data together.
Note: The journal and subledger data conversion levels require more processing resources
because they duplicate most general ledger and subledger journal entries, as well as general
ledger balances.

Secondary Ledger Example
• You maintain a secondary ledger for your International

Financial Reporting Standards (IFRS) accounting
requirements.
• Your primary ledger uses US Generally Accepted Accounting
Principles (GAAP).
• You decided to select the subledger level for your IFRS
secondary ledger.

Secondary Ledger Example Conclusion
Use an Adjustment Only Level Secondary Ledger instead.

• Because most of the accounting is identical between US
GAAP and IFRS, this is a more powerful solution.
• You do not need to perform a difference comparison because
all your entries are in the adjustment ledger.
• Your secondary ledger contains only the adjustment journal
entries and balances necessary to convert your US GAAP
accounting to the IFRS accounting, which uses a fraction of
the resources that are required by full subledger-level
secondary ledger.
• A subledger-level secondary ledger would provide more
functionality than you need in this example.

Secondary Ledgers Mapping
Creating secondary ledgers follows the same steps as primary ledgers.

• Navigate to the Define Secondary Ledgers page from the Define Accounting
Configurations task list in the Setup and Maintenance work area.
• Select the additional option of Data Conversion Level for secondary ledgers on the
Create Secondary Ledger page.

Chart of Accounts Mapping Feature
• Enables you to correlate a source chart of accounts to a target

chart of accounts to allow for creating journals using an
alternative chart of accounts.
• Uses segment rules, account rules, or a combination of both.
• Provides the posting program with the directions needed to
propagate general ledger entries from the primary ledger to
the secondary ledger.
• Directs balance transfer programs for balance-level secondary
ledgers and cross-ledger transfers to copy balances from one
ledger to another ledger.

Segment Mapping Rules
Segment rules serve to map each segment of the target chart of

accounts to an account value or segment in the source
account. Segment rules:
• Assign a constant value for a segment in the target chart of
accounts.
• Copy the value from the source segment to the corresponding
target segment.
• Use hierarchical rollup rules when a specific parent source
value and all of its child segment values are mapped to a
given detail target segment value. This enables you to
process groups of source segment values in one single rollup
rule.
Tip: Define parent source values in rollup rules with date-effective versions of a hierarchy.
Then use the accounting date from the journal entries to reference the chart of accounts
mapping that falls within the effective date of the hierarchy. This gives the additional benefit of
self-maintaining mappings because the hierarchies referenced change with time and the
applicable child values are processed automatically.

Account Mapping Rules
Define account rules as part of a chart of accounts mapping.

Account rules:
• Map a complete target account combination against one or
more source account code combinations.
• Define the source account code combinations segment by
segment using:
– Single detail account values.
– Detail account value ranges.
– Parent values for each segment.

Review and Submit Accounting Configuration
Navigate to the Review and Submit Accounting Configuration

page from the Define Accounting Configurations task list in the
Setup and Maintenance work area.
• Select your ledgers and click the Submit button.
• A green check mark in the Status column shows that your
configuration is completed and confirmed.
Note: This process runs by primary ledger and processes related
secondary ledgers, reporting currencies, and legal entities.
The Review and Submit Accounting Configuration:

• Updates the underlying table and permanently saves the settings after the accounting
configuration has been completed. Some settings cannot be changed or deleted.
• Creates the accounting configuration and a balances cube when setup is completed.

Practice 7-19 Overview: Completing the Ledger
Configuration
• Completing the Ledger Configuration
• Opening the First Accounting Period
– Selecting your data access set.
– Opening the period.

Balance Cubes: Overview
• Are created automatically when an accounting configuration is

submitted for a ledger based on the chart of accounts and
calendar combinations.
• Store your financial balances in a multidimensional model to
enable interactive financial reporting and analysis.
• Preaggregate your balances at every possible point of
summarization, ensuring access to financial data and
eliminating the need for an external data warehouse.
• Are automatically updated by the following general ledger
processes: posting, open period, and translation.
• Consist of a set of defining business entities called
dimensions.
Note: Average balances are tracked in a separate balances cube.

Balance Cubes Naming
The balances cubes are named after the chart of accounts they contain.
Example
• The chart of accounts Vision Corporation has a related balances cube, also entitled
Vision Corporation.
• If a chart of accounts is used by multiple ledgers with different calendars, the balances
cube names are distinguished by a number appended to their names.
• If the Vision Corporation chart of accounts is used by two different ledgers, each of
which uses a different accounting calendar, two balances cubes are created with the
names Vision Corporation Chart of Accounts 1 and Vision Corporation Chart of
Accounts 2.

Balance Cube Dimensions
Dimension Description
Accounting Period Based upon the calendar of the ledger or ledger set.
Report on years, quarters, or periods.
Ledger or Ledger Set Used to select a ledger for reporting.
Charts of Accounts Segments from the charts of accounts, organized by
Segments hierarchy.
Scenario Indicates whether the balances are actual, allocated,
or actual including allocated, budgeted, or forecast.
Balance Amount Indicates whether the value is a debit or credit, and
whether it is for the beginning balance, period
activity, or ending balance.
Amount Type Indicates whether the amounts represent Base,
Period, Quarter, or Year to Date.
Currency Used to select the desired currency for the balances.
Currency Type Used to select the currency type of the balances.
Available options are Entered, Converted, or Total.
A balances cube consists of a set of defining business entities called dimensions. This table
details the dimensions that are available for creating financial reports using multidimensional
cubes.
The General Ledger Posting process updates your balances and stores these balances in a
balances cube for efficient multidimensional analysis. This provides for efficient reporting.
Note: Dimensions are seeded and new ones cannot be added.

Manage Ledger Sets
• Enables you to group multiple ledgers that share the same

chart of accounts and calendar combination to increase the
efficiency of your period close, security administration, and
reporting.
• Allows you to treat multiple ledgers as one.
For example, you can open and close periods for multiple ledgers in a ledger set in a single
submission by submitting the Open and Close Period process.

Practice 7-20 Overview: Creating a Ledger Set

• Creating a ledger set.

Data Access Set Security Overview
Grants access to ledger, ledger set, or specific primary balancing

segment values that are associated with a ledger.
Create and edit data access set security on the Manage Data
Access Sets page from the Setup and Maintenance work area or
from your implementation project.

Data Access Set Security
Secures access to ledgers, ledger sets, and portions of ledgers

by 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.
• Secures parent or detail primary balancing segment values.
• Secures the specified parent value as well as all its
descendents, including mid-level parents and detail values.
• Requires all ledgers assigned to the data access set to share
the same chart of accounts and accounting calendar.

Data Access Set Security
• Full Ledger Access: Access to the entire ledger or ledger sets. For example, this could
be read-only access to the entire ledger or both read and write access.
• Primary Balancing Segment Value Access: Access to one or more primary balancing
segment values for that ledger. You can specify read-only, read and write access, or a
combination of the two for different primary balancing segment values for different
ledgers and ledger sets.

Data Access Set Security: Example
This example shows a data access set that secures access by using primary balancing
segment values that correspond to legal entities.
Scenario
• The Vision US Primary Ledger is assigned to this data access set.
• Read-only access has been assigned to balancing segment value 131, which
represents the Vision US Heath LE 3.
• Read and write access has been assigned to the other two primary balancing segment
values for legal entities, Vision US LE 1 and 2.
In summary, you can:
• Create a journal batch in ledgers or with primary balancing segment values if you have
write access.
• Modify a journal batch if you have write access to all ledgers or primary balancing
segment values that are used in the batch.
• View a journal batch if you have read-only or write access to the ledger or primary
balancing segment values.

Practices 7-21 and 7-22: Data Access Set Security
These practices cover the following topics:

• Practice 7-20: Reviewing Data Access Set Security
• Practice 7-21: Creating Data Access Set Security

Overview
After creating your enterprise structures and ledger, perform the accounting process that
imports transactions for subledger and posts the balances in the General Ledger. Use the
following steps:
1. Open an accounting period.
2. Enter subledger transactions.
3. Run the Create Accounting process and transfer the journals to the GL_Interface table.
4. Import journals into the general ledger.
5. Post your journal batches manually or automatically. Posting populates the GL Balance
Cube and the GL_Balances table.
6. Produce financial reports and perform online inquiries to review current account
balances.
7. Close the current accounting period.
8. Open the next accounting period.

Open and Close Periods Life Cycle
Open and close periods for multiple ledgers in a ledger set in a

single submission.
Accounting periods move through a life cycle:

1. Future Enterable
2. Open
3. Closed
4. Permanently Closed

Accounting Period Statuses
Accounting Period Statuses

• Open: Open to enter and post journals.
• Closed: Close after finishing your month-end processing.
• Permanently Closed: Permanently close before archiving
data.
• Future Enterable: Use to enter and import journals before
opening the next periods
• Never Opened: Use to indicate new periods.
Accounting Period Statuses additional information:

• Open: An unlimited number of periods can be opened, but doing so may slow the
posting process and can confuse users entering journals.
• Closed: Reopen closed periods before you can post journals.
• Permanently Closed: Permanently closed periods cannot be reopened.
• Future Enterable: Journal cannot be posted in a Future Enterable period. Specify a
numerical value in the Specify Ledger Options page to permit entering journals but not
posting them in future periods. You can change the number of Future Enterable periods
at any time.
• Never Opened: The application sets all new periods to Never Opened until you change
the status.

Accounting Periods Overview
Open the first period of the ledger when you are ready to transact
in one of these ways:
1. Navigate to: Setup and Maintenance > Define Ledger > Open
First Period. Click the Submit button to launch the open period
process.
2. Use the Close Status region in the General Accounting
dashboard.
3. Access the Manage Accounting Periods task in the Period
Close work area.
4. Run the process in the Process Monitoring work area, which
provides a framework for launching, monitoring, and
maintaining processes across Oracle Fusion Financials.
The Close Status region provides real time visibility into the period close process from your
subledgers to your General Ledger across the entire enterprise.

Period Close with Oracle Financials
Manage period close better with various monitors to gauge

different aspects of the period close:
Feature Benefit
Close Status Monitor High level period status information for GL
and subledger in different formats.
Subledger Outstanding Summarized outstanding subledger
Transactions Monitor transactions by category with drill to details.
Translation Status Monitor Alert users to out of date translations by
balancing segment value and translation
currency.
Intercompany Period Status Concise recap of period status by
intercompany transaction type with open
transactions count and detail drill.
Additional features:
• Close Status Monitor: Provides insights on close readiness along with quick access to
update the period status.
• Subledger Outstanding Transactions Monitor: Promotes efficiency for tying up loose
ends that impact accuracy and completeness of accounting close.
• Translation Status Monitor: Quickly highlights if translated data is available and
current.
• Intercompany Period Status: Further streamlines with optional sweep of unconcluded
transactions to future period.

Period Close Section
Navigate to: Period Close

The Period Close section provides real time visibility into the period close process from your
subledgers to your General Ledger across the entire enterprise.
Single Ledger View
• Focus on a single ledger’s period status by Oracle Fusion General Ledger and the
subledger for the period.
• View details for partially closed subledger periods.
• Review subledger business units and asset books for the ledger.
• Drill down to period status details of that ledger for all periods.
• Navigate conveniently to submit open and close period processes after status review for
General Ledger and subledgers.
Ledger Set View
• Summary view of period status across multiple ledgers in a ledger set.
• Matrix of General Ledger and subledger period status for each ledger.

Period Close Best Practices
Period Close Item Period Close Tool

Ensure that all transactions for the period are Journals and
transferred and posted to the General Ledger. Intercompany
Transactions Infolets
Tie out Payables and Receivables subledger AP and AR Reconciliation
balances to the General Ledger. Infolets
All intercompany transactions for the period Intercompany
have been transferred, and both sender and Transactions Infolets
receiver have accounted for their side of the
transaction.
Outstanding journal entries for the period are Journals Infolet
resolved before closing the period.
Translated balances are current before running Translation Status Portlet
final reports on translated balances.
Subledger periods are closed before proceeding Close Status Monitor,
to close the General Ledger period. Open Subledger Infolet

Practice 7-23 Overview: Opening the First Accounting
Period
• Selecting your data access set.
• Opening the period.

Period Close Checklist
• Transfer and import data from other sources.

• Confirm that transactions imported from other sources have
completely made its way into the General Ledger.
• Verify all journals are posted.
• Perform allocations.
• Revalue foreign currency balances.
• Reconcile account balances.
• Translate balances to parent’s currency using period end and
historical rates.
• Consolidate subsidiary ledgers.
• Run reports and perform financial analysis.
• Close the period and open the next period.
Best practice is for you to develop a comprehensive period close checklist that includes
Oracle Fusion Applications tasks and other enterprise tasks outside Oracle Fusion
Applications.

Period Close Components
• While implementing your accounting configuration, optionally

define and maintain the period close components to complete
your accounting configurations setup.
• Period close components include the following tasks under the
Define Period Close Components task list:
– Manage Allocations and Periodic Entries
– Manage Revaluations
– Manage Historical Rates
The Mange Historical Rates task includes the Daily Rates tab. Daily rates are also needed for
the revaluation and translation processes.
Note: Define Period Close components also include the Manage Close Monitor Setup. The
Close Monitor setup is comprised 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.

Allocations Concepts
Use the following components during allocation rule design:

• Source: Cost or revenue pool which is allocated.
• Basis: Formula to distribute the amounts.
• Target: Receiver of the allocated or calculated amount.
• Offset: Receiver for the offsetting debit or credit to balance the
generated allocation or formula.
• Validation: Checks the validity of the allocation definition.
• Scenario: Dimension for classifying balances data.
• Run Time Prompt: Variable where the user supplies the value
when an allocation rule is run.
• Source: The amount or accounts used by the computation in a formula component. Can
be a referenced account balance or it can just be a user defined amount.
• Basis: Formula used to define how the amounts in the source pool are to be divided
among the target lines.
• Target: Can be a group of accounts represented by a parent.
• Offset: Can be a group of accounts.
• Validation: Checks for consistency against the outline of the balances cube it
references. The process does not confirm that balances are available to be allocated.
• Scenario: Examples: Actual, Budget, Forecast1, and Forecast2. Use one of two specific
seeded scenarios for step down allocations:
- Allocated: Temporarily holds the allocated values during the rule generation
process
- Total for Allocations: The sum of Actual and Allocated amounts.
• Run Time Prompt: A user-defined element used at the time of the rule definition and
makes the rule highly dynamic and reusable. Examples of Run Time Prompts are
Accounting Period or Primary Balancing Segment Value.

Allocation Components
Calculation Manager provides an automated solution to flexibly distribute revenues and costs
across the enterprise or to record formulaic recurring adjustments. Define rules to generate
formula-based journals.
The graphic above shows the components of allocation rules:
• Allocation: Define the account values used to derive the source, target, allocation range,
basis and offset.
• Formula: Define the calculation that allocates the source to the target and offset
accounts.
• Point of View: Define the dimension values that point the allocation to the correct ledger,
balancing segment value, accounting period, balance type and currency.

Defining Allocations Requirements
• Complex formula definitions

– Optimally design formulas in a graphical environment with
Allocation Wizard.
– Real time check of rule definitions to validate rules.
– Minimize setup and maintenance time with reusable formula
components.
– Use combinations of available mathematical operators to
achieve complex calculations.
– Combine formula components to build complex allocations.
• Enhanced allocation formula scope and longevity
– Use the same allocation rules for similar allocations that are in
different accounting periods or with other variables*.
– Leverage hierarchy versioning with parent account values in
formulas.
*Other variables can include run time prompts for accounting period, balancing segment
values, ledgers, and user-defined variables add flexibility to your allocation rules.

Generation of Allocations
• Leverage preaggregated multidimensional balances to

maximize efficiency in executing complex calculations.
• Integration of allocation generation mechanism with enterprise
scheduler with flexibility of generating immediately or in the
future.
• Seamless process from generation to posting to reversal of
allocation.
• Creation of rule sets to achieve multi-step cascading
allocations.
• Audit trail for allocated amounts with well documented rules.

Cross Ledger Intercompany Allocations
Define a rule to allocate across ledgers by specifying a ledger set

in the Allocation Range. Any number of ledgers can be included in
a single allocation formula.
• Submit the Generate Intercompany Allocations process if you
require intercompany transactions or invoicing for your
allocations.
• Submit the Generate General Ledger Allocations process if
you only need allocation journals generated.
• Ensure that the ledgers are within a ledger set when allocating
across different ledgers.
• Define intercompany balancing rules that can be used for
generating receivables and payables accounts for cross-
ledger allocations or allocations transferred to the
intercompany module.
Use one of these two methods for generating journals.

• Generate General Ledger Allocations: Allows you to create journals to allocate amounts
in a single ledger or across different ledgers in a ledger set. If the allocation is across
multiple ledgers, each ledger’s journals are balanced using the Intercompany balancing
rules.
• Generate Intercompany Allocations: Allows you to create intercompany transactions
from allocation lines for a single or multiple ledgers. The intercompany transaction type
you select when submitting the process determines if manual approvals and invoicing
are required for the intercompany transactions created from the allocation.

Step Down Allocation Example One
Use Only Allocated Amounts
In this example, you allocate only the $100 that was allocated to 1A ($70) and 1B ($30), not
the actual amounts in each: 1A ($700) and 1B ($60).

Step Down Allocation Example Two
Using Actual and Allocated Amounts
In this example, you allocate not only the $100 that was allocated to 1A ($70) and 1B ($30),
but also the actual amounts in each: 1A ($700) and 1B ($60) for a total of:
• $770 for 1A ($700 actuals plus $70 allocated)
• 2Aa $550
• 2Ab $220
• $90 for 1B ($60 actuals plus $30 allocated)
• 2Ba $75
• 2B1 $15

Allocation Rule Concepts
• Use rules in the Calculation Manager to group calculations.

• Design a rule by dragging components from the Rule Palette
area to the flow chart.
• Each component performs a separate task.
• Add Point of View, Formula, or Allocation components.
• Use rule validation to store rules and rule sets in Calculation
Manager database and to validate them against the
dimension metadata. The validation process ensures that:
– All members are valid for the dimensions within the application.
– All functions exist, have the correct number of parameters, and
are valid for the application type.

Allocation Rule Deployment
• Use rule deployment to deploy allocation rules before you

generate them from Allocation Generation page.
• Rules do not exist for generation until they are successfully
deployed.
• Deploy rules from the Validate and Deploy button on the
toolbar.

Allocations: Best Practices
Implementation Question Recommendations and best practices
How do I avoid invalid Validate the rules and rule sets during definition
definitions? time and fix the errors.
How do I automate the Use the enterprise scheduler to schedule the
allocation generation generation of allocation definition at the optimal
process? time.
Select option to automatically post the
generated allocation and formula journals.
Leverage reversal criteria sets if there are
requirements to reverse the allocation journals
in the future.
Can I use Calculation For fully reciprocating eliminations, use a (-1)
Manager to generate multiplier against the source elimination balance
elimination entries for to compute the target elimination balance.
consolidations? For other types of eliminations, use formulas
applying the required math operators and
variables such as ownership percentages to
compute the elimination amount.
Indicate the same account for the source and target if you wish to eliminate the source
balance directly.
The following are limitations 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.

Practice 7-24 Overview: Creating and Generating an
Allocation Rule
These practices covers the following topics:
• Creating an Allocation Rule.
– Creating a new value.
– Creating two journals to use as the source and the basis.
– Creating an allocation rule.
• Generating an Allocation.
– Generating an allocation journal.
– Using the Post Allocation option.
– Reviewing your journal.

Revaluation Overview
Process of adjusting the accounted value of foreign currency

denominated balances according to current conversion rates.
Revaluations:
• Represent the difference in the value of the balance due to
changes in conversion rates between the date of the original
journal entry and the revaluation date.
• Post as adjustments through journal entries to the underlying
account with the offset posted to an unrealized gain or loss
account.
• Are offset in journal entries:
– Debits against an offsetting credit to the unrealized gain
account.
– Credits against an offsetting debit to the unrealized loss
account.
Note: 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.

Translation Overview
Process of converting accounted balances from one currency to

another target currency.
• Run translation after you have completed all journal entries for
an accounting period and run revaluation.
• Retranslate if you post additional journal entries or change
your translation rates after running translation for a period.
Revaluation and translation are used to support multicurrency financial accounting

requirements.

Revaluation and Translation Concepts
Concept Description
Revaluation Definition Reusable rules that define how to
generate a revaluation.
Rate Type A category of conversion rates that
identifies which rates are used by the
revaluation and translation processes.
Daily Rates Currency exchange rates that are
used by the revaluation and
translation processes
Historical Rates/Amounts Currency exchange rates or amounts
that are assigned to specific accounts
of a ledger that are used by the
translation process.
• Revaluation Definition: Includes which accounts to revalue, for which entered currency,
applying rates of what rate type and the debit and credit offset accounts to use against
the revaluation adjustment.
• Daily Rates: Each rate is characterized by a from-currency, to-currency, rate type, and
date.
• Historical Rates and Amounts: The historical rate or amount assigned to an account
overrides the period end or period average rate that would normally be used to translate
the account.
Note: A frequent misunderstanding s that the system comes up with the periodic average rate
automatically (based on the daily rates entered for the whole period). Actually you must enter
the average rate for the period.

Revaluation and Translation Setup
Navigate to the following highlighted tasks to perform your

revaluation and translation configuration.
The Currency Rates Manager is the tool that covers all these setups, including rate types.
Run Revalue Balances and Translate Balances from the Period Close work area's task panel.
Note: The Translation Period is treated as first ever translated period if no translation has
previously submitted for that ledger to that target currency. Whereas, if translation has already
previously submitted, then the translation period is treated as a translate-up-to-this-period
parameter.

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

Note: This is only an illustration with unsettled Receivables foreign currency denominated
balances. Similar process may be run for unsettled Payables foreign currency denominated
balances as well.
Note: General Ledger creates the revaluation adjustments in your ledger currency. General
Ledger will automatically define the reversal period for your Revaluation Journals if the
Category has been set to automatically reverse.
• Average Balance Ledgers
- When you revalue balances in an average balance ledger, General Ledger only
revalues actual balances.
- When you post the revaluation journal entries to update your standard balances,
the system recalculates your average balances automatically.
Reporting Currencies: Under the SFAS 52 remeasurement, the temporal method translation,
it is necessary to remeasure foreign currency gains or losses recorded in your primary ledger
currency and recorded them in the reporting ledger currency.

Revaluation Example
At the end of the accounting period, the revaluation process creates an unposted journal to
record the change in the converted balances to the Unrealized Gain/Loss Account. The
journal is posted, and then reversed at the beginning of the next reporting period. In this
example:
• The original journal entry in Euro remains the same.
• At period end, the exchange rate has changed to 1.2885
• The receivable is still 10,000 Euro, but is now $12,885 US Dollars.
• The offset of $100 is recorded in the Unrealized Gain account.

Practice 7-25 Overview: Creating a Revaluation

• Defining a revaluation.
• Generating your revaluation.
• Verifying your journal entry.

Translation Process
Running Translation
• Restates your ledger currency account balances into a reporting currency.
• Translates actual balances from ledger currency to other currencies for online inquiries,
reports, and consolidations.
• Supports multiple balancing segments for the Retained Earnings and Cumulative
Translation Adjustment accounts.
• Is done after you have completed all journal entries and revaluations for an accounting
period.
Note: If you post additional journal entries or change your translation rates after running
translation for a period, you must retranslate.

Translation and Remeasurement Solutions
Translation:
• Converts the general ledger balances from the ledger
currency to a reporting currency.
• Used if investing overseas to convert net equity.
Remeasurement:
• Restates an entire ledger or balances for a company from the
ledger currency to another currency.
• Uses historical rates for non-monetary items,
• Records the cumulative translation adjustment as part of profit
or loss.
• If the other currency is the reporting currency, no translation is
required. If not, then translation is run after remeasurement.
More information:
• Transaction Currency: Currency used on a transaction.
• Accounting Currency: Currency used to account for the transaction in the general
ledger.
• Ledger Currency: Currency of the ledger.
• Reporting Currency: Currency that general ledger balances are translated into.
• Both methods use period to average rate type for Income Statements.

Historical Rates and Amounts
• Weighted average rate for transactions that occur at different

times.
• Used to present balances in the reporting currency according
to the historical rates applicable to the account activities that
make up the account balance.
• Can stabilize the translated balances by defining fixed
historical rates for long-term accounts.
• Used with highly inflationary currencies to remeasure specific
historical account balances in accordance with United States
Financial Accounting Standards Board 8.
Historical rates and amounts are:

• More precise than period end rates for equity accounts.
• Defined before running translation to avoid having to retranslate your balances.
• A positive value treated as a credit amount since historical rates and amounts are often
associated with equity accounts.

Import Journal Entries Overview
• Transfer data into the GL_INTERFACE table from the subledgers using the Create
Accounting process. The Journal Import process pulls the information from the Interface
table to create valid, postable journal entries in Oracle Fusion General Ledger.
• Initiate the Create Accounting process from Oracle Fusion subledgers, such as Oracle
Fusion Payables or Oracle Fusion Receivables.
• Choose to transfer and post in the General Ledger. If you do not choose to transfer to
the General Ledger from the subledger, then you must run the Transfer Journal Entries
to GL separately in the subledgers.
• The Journal Import process loads the data from the GL_INTERFACE table into the
journal tables of General Ledger.
• Import data from non-Oracle feeder systems from the GL_INTERFACE table.
• Journal information can be transferred in detail or summary.

Journal Import Verification Process
Journal Import Process

• Validates all of your data, before it creates journal entries in Oracle Fusion General
Ledger.
• Assigns balances to the suspense account to balance the entry if you allow suspense
posting for your general ledger.
• Replaces disabled accounts with alternate accounts if the alternate account is set up on
the Manage Account Combination page.
• Rejects all other invalid lines and they remain in GL_INTERFACE table.
• Prints your error lines in the Journal Import Execution report.

Journal Import Validates
• Account combinations.
• Unbalanced journal entries.
• Accounting periods.
• Foreign currency errors.
• Other miscellaneous items.
Important: Before closing your general ledger, verify that all journal entries have been
imported from the GL_Interface table. If not, troubleshoot the remaining entries.

Reconciliation
• Reconcile account balances online or through reports using

integrated inquiry, reporting, and analysis tools.
• Drill down from account balances to journals and underlying
subledger transactions through a single drill path.
• Run predefined standard reports to help reconcile account
balances, such as subledger to general ledger reconciliation,
intercompany reconciliation, trial balance, journals, and
account analysis reports.
• Use the Journal, AP, and AR Recondition infolets.
Reconciliation of subledgers to the General Ledger

ensures integrity of financial data.
The Oracle Financials enables you to quickly reconcile your General Ledger to these
subledgers.
• The subledger transactions must be accounted and posted to the General Ledger as a
prerequisite to the reconciliation process.
• The posting process updates the General Ledger balances after which reconciliation
reports can be run to start the reconciliation process.
Comprehensive Account Analysis reports include beginning and ending account balances
along with all journal entries that constitute the accounts activities, and contain source,
category, and references, which are fully documented to easily trace back to the origin of the
balance.

Reconciliation
Drill from the transferred balances in the target ledger to source

ledger journal balances.
Navigate to: Financial Reporting Center > Vision Corporate Consolidated Balance Sheet >
Click on a UK balance > Drill to Account Inspector > Click on the Corporate balance link >
Click on the Period Activity in the Inquire Detail Balances page > Click on the Debit amount in
the Journal Lines page.
You can easily reconcile balances that were transferred to a target ledger to the balances,
journals, and subledger transactions from the source ledgers.
• Drill from the Entered amount, which resulted from a balance on the Journal Lines page
or the Journals page in the target ledger.
• Analyze details such as the accounting period and accounts used in the source ledger
for transferring journal line amounts to the target ledger.
Considerations
If the source and the target ledgers do not share a ledger currency, the source ledger is
translated to the target ledger's ledger currency before balances can be transferred. The
balance transfer drill down shows the reporting currency balances for the source ledger in the
target ledger currency as part of the drill path.

Reconciliation Concepts
Reconciliation Solution
Requirement
Subledger to General Receivables to Ledger Reconciliation and
Ledger reconciliation Payables to Ledger Reconciliation Reports:
reports to match • Streamline reconciliation respectively from
Accounts Payable and Receivables and Payables to General Ledger.
Accounts Receivable • Automatically matches subledger transactions
transaction entries to to accounting entries to accelerate the
General Ledger reconciliation and close processes.
accounting entries. • Identifies exceptions to guide your
reconciliation efforts.
Drilldown to originating Direct drilldown to supporting journals and
transactions. transactions is provided for visibility to source
information.
Reconciling high data Analyze report output in a spreadsheet
volume. environment.
The specific subledger to ledger reconciliation reports are designed for the automatic
reconciliation process and therefore not available for editing. It is straightforward to create
similar reports.
Note: To view chart of accounts segments and the corresponding Essbase cube dimensions
in OTBI Reports such as Receivables to Ledger Reconciliation and Payables to Ledger
Reconciliation reports, you need to set up the Chart of Accounts segments, enable them for
BI Reporting, and map the chart of accounts and cubes in the BI Repository.
Refer to Oracle Fusion Transactional Business Intelligence Administrator's Guide for more
detailed setup steps.

Payables Tax Reconciliation with General Ledger
Report
• Reconcile the Payables tax transactions with the tax account
balances in General Ledger.
• Create for a specific journal entry source, ledger, legal entity,
or General Ledger account.
Select a
specific
reporting
level.
Use the new Payables Tax Reconciliation with General Ledger Report to reconcile the
Payables tax transactions with the tax account balances in General Ledger. You can also
simplify the reconciliation process by running the report for a specific Journal Entry Source,
Ledger, Legal entity or General Ledger account.
Note: Create a separate tax account for each tax rate code to simplify the reconciliation.

Summary

• Manage chart of accounts components.
• Manage and publish account hierarchies.
• Define calendars and currencies.
• Define ledgers and ledger options.
• Explore the GL Balances cube.
• Open and close periods.
• Allocate balances.
• Manage revaluations and translations.
• Reconcile balances.

8
Configuring Oracle Fusion
Intercompany

Objectives

• Explain the intercompany features.
• Set up intercompany balancing.
• Set up the intercompany transactions.
• Run intercompany reconciliation and reporting.

Intercompany Overview
Oracle Fusion Intercompany module consists of three areas of

functionality:
• Intercompany Balancing: Supports business activity between
legal entities or between management entities within the same
enterprise.
• Intercompany Transactions: Allows manual creation of
transactions through the user interface, spreadsheet entry,
transaction import, and transaction generation from
allocations.
• Intercompany Reconciliation: Provides reports for visual
comparison of intercompany receivables and payables
accounts and drill down capabilities.
Note: This lesson covers only the Intercompany module in Oracle Fusion Financials.
Intercompany functionality is also available in Oracle Fusion PPM (Projects) and SCM
(Supply Chain), which are not covered here. The Intercompany accounts setup is centralized,
so the Intercompany Accounts defined in Financials are also used by PPM and SCM for
consistency and accuracy.

Intercompany Balancing Overview
• Generates Due to and Due From journal lines automatically

based on centralized intercompany setup.
• Supports multiple balancing segments
• Generates Intercompany accounts for cross ledger allocations
• Performs balancing when:
– Subledger journal entries are created
– General ledger journals are posted.
• When subledger accounting entries including Payables, Receivables, Fixed assets,

Inventory or GL journals are out of balance by any of the balancing segments,
intercompany automatically generates the necessary lines to balance them and ensure
debits equal credits for all balancing segments.
• The centralized setup of intercompany balancing rules for all products streamlines the
setup required for balancing.
• Up to three of the segments in a chart of accounts can be balanced by intercompany. By
balancing and eliminating intercompany activity at the legal entity level, it helps meet
legal reporting requirements that require external financial statements to exclude
intercompany activity. Additional balancing segments facilitate management reporting if
balance sheet reporting is required at the cost center, department, or other level below
legal entity.
• For accounting across multiple ledgers as in cross-ledger allocations, intercompany
accounts are generated to ensure each ledger’s entries are balanced.
• The Balancing program is called when subledger accounting entries are created and
when journals are posted.

Example: Payables Invoice
Primary Balance Segment Account Intercompany Segment Debit Credit
Original Transaction Lines:

Vision Foods Berkeley Expense 500
Vision Foods Marin Expense 700
Vision Stockton Citrus Liability 1200
Intercompany Lines to balance the transaction:
Vision Foods Berkeley Intercompany Payables Vision Stockton Citrus 500
Vision Stockton Citrus Intercompany Receivable Vision Foods Berkeley 500
Vision Foods Marin Intercompany Payable Vision Stockton Citrus 700

Vision Stockton Citrus Intercompany Receivable Vision Foods Marin 700
* Example from Manage Intercompany Transactions – Intercompany Balancing Functional Overview
An employee in the Vision Foods Berkeley business unit creates a $500 purchase order (PO)
for a new laptop he needs and the PO gets all the required approvals.
An employee in the Vision Foods Marin business unit creates a $700 purchase order (PO) for
a new laptop he needs and the PO gets all the required approvals.
Vision Stockton Citrus is the Shared Service Center, and it has negotiated a contract with Dell
for all the PC orders of the US owned companies.
Vision Stockton Citrus is the customer placing the order with Dell.
Dell Ships the PCs to Vision Foods Berkeley and Vision Foods Marin.
Dell sends the Invoice to Vision Stockton Citrus.
Vision Stockton Citrus enters the invoice in Payables and matches the invoice lines to the
POs that were created earlier by Vision Foods Berkeley and Vision Foods Marin.

The invoice is approved. SLA creates accounting for the invoice.
Since Vision Foods Berkeley, Vision Foods Marin, and Vision Stockton Citrus are all modeled
as different primary balancing segments, when SLA creates the accounting for the invoice,
SLA calls the Intercompany Balancing program to generate additional balancing lines to
balance the accounting entry. The chart of accounts has three segments: legal entity,
account, intercompany segment. The account combinations generated for the intercompany
lines clearly identify the trading partners of the intercompany transaction.

Example: Cross Ledger Allocation Journals
Journal Ledger Account Debit Credit
1 Vision USA 3111-000-4111-0000 170,000
Vision USA 3111-000-1301-2257 129,000
Vision USA 3111-000-1301-2258 11,000
Vision USA 3111-000-1301-1232 12,000
Vision USA 3111-000-1301-1234 18,000
2 Vision Canada 2257-000-6111-0000 129,000
Vision Canada 2258-000-6111-0000 11,000
Vision Canada 2257-000-2101-3111 129,000
Vision Canada 2258-000-2101-3111 11,000
3 Vision China 1232-000-6111-0000 12,000
Vision China 1234-000-6111-0000 18,000
Vision China 1232-000-2106-3111 12,000
Vision China 1234-000-2106-3111 18,000
• Cross ledger allocations are another example where intercompany balancing rules are
used to generate intercompany receivables and payables accounts so that each
ledger’s journals are balanced.
• In this example an allocation is generated by submitting the Generate General Ledger
Allocations process and it has resulted in a journal across multiple ledgers.
• The process adds intercompany clearing lines shown in green to balance each journal
so that the intercompany allocation across the three ledgers can be posted successfully.

Intercompany Balancing Features
• Balances up to three segments per chart of account

• Balances single ledger journals and cross-ledger allocation
journals
• Identifies intercompany trading partners if intercompany
segment is used
• Provides high level rules at the chart of accounts level or more
granular level rules at ledger, legal entity or primary segment
value
• Creates rule by Source and Category combination
• Provides Clearing company options for handling many-to-
many journals
• Up to three of the segments in a chart of accounts can be balanced by intercompany.

Balancing and eliminating intercompany activity at the legal entity level helps meet legal
reporting requirements that require external financial statements to exclude
intercompany activity.
• Balancing lines are generated for single ledger journals or accounting entries that are
out of balance. Balancing also handles cross-ledger allocations by adding the
appropriate intercompany receivables or payables line to each ledger’s journal.
• If the chart of accounts structure has a segment designated as the intercompany
segment then the trading partner can be easily identified as the balancing lines are
populated with the relevant trading partner segment value.
• Intercompany automatically generates the balancing lines based on intercompany setup
(that is also used for manually entered intercompany transactions) so minimal manual
intervention is necessary to keep all transactions and journals in balance. This reduces
attention needed by accounting staff, freeing up resources to work on other value-added
activities.

• Intercompany balancing rules can be created at multiple levels – chart of accounts,
ledger, legal entity and primary balancing segment allowing users to fine tune how they
want their balancing done.
• Additionally, rules can be created by specific source and category combinations or they
can be created to cover all source and category combinations. Rules for generating the
intercompany receivables and payables accounts for transactions entered into the
Intercompany module, are also defined in the same place and these are created for
specific or all intercompany transaction types.
• Oracle recommends defining clearing company options for handling many-to-many
journals.
• Third party applications can take advantage of the intercompany balancing functionality
if they integrate with SLA or GL, since both SLA and GL call the balancing engine to
balance journals that are unbalanced.

Balancing Setup
• Enable Intercompany Accounting in Ledger Definition

• Manage Intercompany Balancing Rules
• Manage Secondary and Clearing Company Options
• Enable Intercompany Accounting option in Ledger Definition: When defining a ledger,

enable the Intercompany Accounting option to allow SLA and GL to call the
Intercompany Balancing program if needed to balance journals.
• Manage Intercompany Balancing Rules: This is where you define the intercompany
receivable account and intercompany payable that is used to build the intercompany
accounts to balance out-of-balance journals and subledger accounting entries. The
accounts specified in the balancing rules are a template for the actual intercompany
accounts generated. Flexible setup options allow you to define intercompany rules at the
chart of accounts, ledger, legal entity and primary segment levels. This allows for a
single rule for example to be defined at the chart of accounts level if all balancing across
all ledgers for that chart of account use the same natural account and you have an
intercompany segment that can track the trading partner.

• Manage Secondary and Clearing Company Balancing Options: If a journal is balanced
by primary balancing segment value, but not balanced by the second and/or third
balancing segment, then Manage Secondary and Clearing Company Balancing Options
is where you define the intracompany receivable and payable accounts used to
generate the accounts for balancing this scenario. You should also specify how you
want to handle many-to-many journals where it is not possible to identify which debit line
should balance against each credit line and vice versa.

Specify Ledger Options
Navigate to: Setup and Maintenance > Specify Ledger Options

• Enabling this checkbox ensures that all journals and subledger accounting entries are
balanced by the primary, second, and third balancing segments. Journals are balanced
during posting and subledger accounting entries are balanced during the Create
Accounting process.
• You can assign legal entities to the ledger and assign primary balancing segment values
to your legal entities. Performing this assignment enables you to define legal entity-level
intercompany balancing rules. Otherwise, you can define just chart of account-level,
ledger-level, or balancing segment-level intercompany balancing rules.

Balancing Rules: Order of Precedence
This figure displays an example of balancing rules precedence. The balancing process tries to
match a setup rule at the lowest level and if one cannot be found, it looks for a rule at the next
level down, continuing through the levels until it finds a rule that can be used. The order of
precedence is:
• Primary balancing segment rules
• Legal entity rules
• Ledger rules
• Chart of accounts rules

Evaluation of Intercompany Balancing Rules
Intercompany Balancing evaluates the journal source and journal

category combination when determining which rule to use for
balancing. The order of precedence is:
• Specific journal source and journal category

• Journal source and journal category of Other
• Journal source of Other and specific journal category
• Journal source of Other and journal category of Other
Best Practice:
• Set up a chart of accounts rule for every chart of accounts structure with source and
category of Other to cover all sources and categories.
• Set up a chart of accounts rule for every chart of accounts structure with transaction type
of All Other to cover all transaction types.
This practice ensures that Intercompany Balancing always finds a rule to generate accounts
for balancing and for intercompany transactions.
Note: Balancing evaluates COA, Ledger, Legal Entity and Primary Balancing Segment level
rules before evaluating source, category and transaction type.

Manage Intercompany Balancing Rules
Chart of Accounts
Navigate to: Setup and Maintenance > Manage Intercompany Balancing Rules > Chart of
Account Rules tab
• This slide shows rules defined for source and category of Other so these rules are used
for balancing journals and subledger accounting entries for all sources and categories if
no other rule matches at the Primary Segment, Legal Entity or Ledger level.
• Note that there are rules for intercompany transaction type of All Other so these rules
are only used for determining the intercompany receivables and intercompany payables
accounts for transactions entered in the intercompany module if no other rule matches
at the Primary Segment, Legal Entity or Ledger level.

Primary Balancing Segment Level Rule
Navigate to: Setup and Maintenance > Manage Intercompany Balancing Rules > Primary
Segment Rules tab
• In this slide you can see the rule between primary balancing segments values 3111 and
3121. As you can see from the rule, it is possible to set up intercompany balancing rules
at a very granular level.
• This rule is used if a journal is out of balance between primary balancing segment
values 3111 and 3121 in ledger Vision Foods – USA ledger, despite the fact that a chart
of accounts rule exists and matches the chart of accounts used for the journal. This is
because the primary segment rules take precedence over the chart of accounts rules.
The order of precedence is primary balancing segment rules, legal entity rules, ledger
rules and finally chart of accounts rules.

Primary Balancing Segment Level Rule
This screen shot displays the fields for the primary segment rules as you scroll across the
page.

Manage Secondary and Clearing Company Balancing
Options
Navigate to: Setup and Maintenance > Manage Secondary and Clearing Company Balancing
Options
Set Secondary and Clearing Company Balancing Options if you have chosen to implement
one or more of the following features:
- Balancing Segments 2 and/or 3
- Clearing Company balancing
- Detail balancing rather than summarization when balancing within a single legal
entity. Note that when balancing across legal entities, we always summarize
balancing lines generated.
This slide shows you the setup for Vision Foods – USA Ledger. In this screen shot you can
see the receivables account, payables account for a given ledger, source and category.
These accounts are used if a journal is balanced by its primary balancing segment but is not
balanced by balancing segments 2 and/or 3.
It is possible to set up different accounts by source/category combination.

Manage Secondary and Clearing Company Balancing
Options
Navigate to: Setup and Maintenance > Manage Secondary and Clearing Company Balancing
Options
• This slide displays the fields for the Secondary and Clearing Company Balancing
Options as you scroll across the page.
• For the last row (source of Autocopy and category of Additions) the option has been set
to use a clearing company value of 1201 for all many-to-many legal entity journals and
all many-to-many primary balancing segment value journals.

Key Decisions and Best Practices
Intercompany Balancing
Topic Decisions
What is the The intercompany segment is a segment of the chart of accounts
structure that has the Intercompany Flexfield qualifier enabled.
intercompany You can implement an intercompany segment in your COA to track
segment? the trading partner for each intercompany transaction.
What are the To assist with reconciling intercompany and help with identifying
elimination entries needed.
advantages of If you use the intercompany segment, you can set up your rules to
having use a single natural account value for the intercompany payable
intercompany account, and a single natural account value for the intercompany
segment? receivable account per chart of accounts.
Balancing will populate the intercompany segment with the trading
partner allowing you to identify the partners in each intercompany
line. This substantially reduces the setup needed.

Topic Decisions
How is it populated? The Intercompany Balancing program automatically populates the
intercompany segment with the trading partner segment value when
it generates Due To/Due From journal lines to balance a journal.

Topic Decisions
Do I use COA level We recommend to use a COA level rule that applies to the majority of
rule, or require lower the transactions.
level rules?
You can then create lower level rules for handling exceptions to the
COA level rule where you need a different intercompany payable or
receivable accounts. Refer to example below for the order of
precedence.
Order Rules COA From Ledger / From LE / From PBSV / Source Category Transaction Receivables Payables
To Ledger To LE To PBSV Type Account Account
1
From : VisionUSA From : VisionEast From: 03
PBSV To: VisionCAD To: VisionWest To: 05 Other Other None 01-000-1110-000 01-000-1120-000
2
Legal From : VisionUSA From : VisionEast
Entity To: VisionCAD To: VisionWest Other Other None 01-000-1210-000 01-000-1220-000
3
From : VisionUSA
Ledger To: VisionCAD Other Other None 01-000-1310-000 01-000-1320-000
4
COA US COA Other Other None 01-000-1410-000 01-000-1420-000

Topic Decisions
Can I use the same Instead of sharing the same value set, it is recommended to use a
value set for different value set for primary balancing segment and intercompany
Balancing segment segment, where both value sets have the same values. If the primary
balancing segment and intercompany segment shares the same
and Intercompany value set, then when segment value security is enabled, it also
segment? affects the intercompany segment. Securing a value set denies
access to all values by default. See example below.
Chart of accounts structure
Primary Second Natural Intercompany

balancing balancing account Segment
segment segment segment
Company Department Account Intercompany
Company Account value Intercompany

Department
value set value set set value set
Consistent Values for Primary Balancing Segment and Intercompany Segment:

Ensure the values for the primary balance segment are exactly the same in name and
description as the values for the intercompany segment. Each value represents a trading
entity, no matter if it’s the provider or receiver of an intercompany transaction. Therefore, each
value should have the same meaning whether it appears as a primary balancing segment
value for a provider, or as an intercompany segment value for a receiver. For example, if US
represents the United States, US should have the same meaning as a primary balancing
segment value or as an intercompany segment value so that users are assured it represents
the United States legal entity.
Intercompany Segment:
Having an intercompany segment in your chart of accounts can decrease the amount of setup
and maintenance needed for intercompany balancing rules. With an intercompany segment,
you can set up per chart of accounts, a single natural account value for the intercompany
payable account, and a single natural account value for the intercompany receivable account,
and use the intercompany segment value to identify the trading partner in an account
combination. The Intercompany Balancing program automatically populates the intercompany
segment value when it generates due to/due from journal lines to balance a journal.

Topic Decisions
Does the company have You would use the same values for the primary balancing
more than one COA, and segment for all charts of accounts in your enterprise for
transactions span more accurate identification of trading partners.
than one COA?
I am upgrading and my No, you can still use all Intercompany features. However we
current chart of accounts strongly recommend an Intercompany segment for new
does not have an implementations, due to the reasons discussed earlier.
Intercompany Segment, do
I need to add one in
Fusion?
Do I need to setup one You do not need to set up rules at every level. Instead if you
rule for each of the use an intercompany segment and your business practice
balancing rules, e.g. one allows for one intercompany receivable natural account and
one intercompany payables natural account, you can set up
for Primary Balancing one rule at the chart of accounts level.
Segment Rule, Legal
Entity Rule, etc?

Demonstration 8-1 Overview: Setting Up a New Rule
This demonstration covers creating a new balancing rule.

Practice 8-2 Overview: Viewing Intercompany
Balancing Rules and Secondary and Clearing Company
Balancing Options
• Searching for your intercompany balancing rules.
• Searching for your secondary and clearing company
balancing options.
• Entering and posting GL journals with mixed balancing
segment value assignments.

Intercompany Allocation Overview
General Ledger Allocations

• Balances intercompany allocation journals across ledgers
automatically using intercompany accounts
• Allows flexible rules to derive the intercompany receivables
and payables accounts for cross ledger allocations
Intercompany Allocations
• Generates intercompany allocation transactions automatically
• Allows manual or automatic approval from all trading partners
• Provides invoice generation
• Processes single or multiple ledger intercompany transactions
• Allows flexible rules to derive the intercompany receivables
and payables accounts for intercompany allocations
• The general ledger intercompany allocations feature handles allocations across different
ledgers within a ledger set having the same chart of accounts, by adding the appropriate
intercompany receivables or intercompany payables lines to each ledger’s journal in
order that it can be imported into GL.
• The intercompany accounts are generated based on the centralized intercompany
balancing rules.
• The intercompany allocations feature takes allocation lines for a single ledger or across
different ledgers in a ledger set with the same chart of accounts and turns them into
intercompany transactions. This enables allocations to leverage intercompany
functionality like the invoicing feature.

Intercompany Allocation Journals
• Automatically balances intercompany allocation journals

across ledgers using intercompany accounts
• Provides configurable flexible rules to derive the intercompany
receivables and payables accounts
Navigate to: General Accounting > Journals > Generate General Ledger Allocations
• This feature ensures that if an allocation journal crosses multiple ledgers, the
appropriate intercompany clearing line is added to the journal for each ledger so it can
be successfully posted without the need to use a suspense account.
• The accounts for the clearing lines come from the intercompany balancing rules and
these can be configured at the chart of accounts, ledger, legal entity or primary segment
level.

Intercompany Allocation Transactions
• Automatically generates intercompany allocation transactions

• Allows manual or automatic approval from all trading partners
• Provides invoice generation
• Processes single or multiple ledger allocations
Navigate to: General Accounting > Journals > Generate Intercompany Allocations
• You can create intercompany transactions from allocation lines.
• The provider and receiver are determined from the primary balancing segment value of
each allocation line, the balancing segment to legal entity assignments and the
intercompany organizations setup.
• The intercompany transaction type you choose when submitting the process, drives
whether the intercompany transactions created requires manual approval or invoice
generation.
• These transactions can be for a single ledger where the provider and receiver are in the
same ledger, or they can be across multiple ledgers where the provider and receivers
are in different ledgers.

Intercompany Allocation Requirements
• All ledgers for an intercompany allocation across ledgers must

share the same chart of accounts
• In the current release
– Only one allocation component can be used per allocation rule
– Intercompany allocations across ledgers must be One-to-Many
• Allocation lines that cross multiple ledgers can be automatically balanced if they have
the same chart of accounts (i.e. they belong to the same ledger set)
• In the current release of this feature only one allocation component can be used for an
allocation that crosses multiple ledgers.
• Allocations must have either one debit line or one credit line. The other side can have as
many lines as required.

Key Setup Tasks: Create Allocation Rules
Navigate to: Journal Accounting > Journals > Tasks Panel Tab > Create Allocation Rules
Allocation Tasks are found in the Journals Work Area
To Create Allocation Rules:
- Access the Journals Work area
- Select Create Allocation Rules from the Tasks menu.
- This opens a new browser window with Oracle Enterprise Performance
Management System Workspace, Fusion Edition.
To Generate Allocations:
- Return to the GL browser window and select the Generate Allocations Task from
the Tasks in the Journals Work Area
To Generate Intercompany Allocations:
- Return to the GL browser window and select the Generate Intercompany
Allocations Task from the Tasks in the Journals Work Area

Example: Intercompany Allocations
Expense Allocation Scenario
Vision USA Ledger
Vision HQ
Vision Vision Vision Vision

Ontario Quebec West East
Vision Canada Ledger Vision China Ledger
• In this example overhead expenses are incurred by the Vision HQ legal entity on behalf
of the entire corporation.
• Vision Ontario and Vision Quebec are assigned to the Vision Canada ledger and Vision
West and Vision East are assigned to the Vision China ledger. Vision HQ is assigned to
the Vision USA ledger.
• Overhead expenses are allocated from Vision HQ to the other legal entities in the
corporate structure.

General Ledger Setup

Ledger Legal Entity Company
Vision USA Vision HQ 3111
Vision Canada Vision Ontario 2257

Vision Quebec 2258
Vision China Vision West 1232
Vision East 1234
In this example, we have three ledgers, each with legal entities and company segment values
assigned to each legal entity.

Intercompany Setup
Legal Entity Intercompany
Organization
Vision HQ Vision HQ
Vision Ontario Vision Ontario
Vision Quebec Vision Quebec
Vision West Vision West
Vision East Vision East
Intercompany Rule Receivable Account Payable Account

Co-CC-Acct-Interco Co-CC-Acct-Interco
Chart of Accounts 3111-000-1301-0000 3111-000-2101-0000
Ledger – Vision China 1232-000-1306-0000 1232-000-2106-0000
• In this example, we have a one-to-one mapping between legal entities and

intercompany organizations.
• We also have intercompany rules set up at the chart of accounts level and a single rule
set up at the ledger level for Vision China.
• Intercompany accounts for Vision USA and Vision Canada are built using the chart of
accounts rule and intercompany accounts for Vision China are built using the ledger
level rule.

Calculation Manager Setup: Overhead Expense Allocation Rule

Type Ledger Details
Allocation Source Vision USA 3000-000-4110-0000
Allocation Target Vision Canada All Company Values

Vision China Cost Center 000
Account 6111
Allocation Offset Vision USA 3111-000-4111-0000
• Vision Corporation allocates overhead expenses from the Vision HQ legal entity in the
Vision USA ledger, to the remaining legal entities in the corporate structure.
• The amount in the overhead expense account is allocated across all company values
based on pre-defined percentages. The offset account is in the Vision USA ledger.

Allocation Lines Generated

Ledger Account Debit Credit
Vision USA 3111-000-4111-0000 170,000
Vision Canada 2257-000-6111-0000 129,000
Vision Canada 2258-000-6111-0000 11,000
Vision China 1232-000-6111-0000 12,000
Vision China 1234-000-6111-0000 18,000
• When the Overhead Expense Allocation rule is run, it generates an allocation from the
Vision USA ledger to the Vision Canada and the Vision China ledgers.
• You can choose to create journals from this allocation rule or alternatively, intercompany
transactions. You do this by submitting the appropriate process and selecting the
Overhead Expense Allocation rule.

1. Journals Created from Expense Allocation Lines
Journal Ledger Account Debit Credit
1 Vision USA 3111-000-4111-0000 170,000

Vision USA 3111-000-1301-2257 129,000
Vision USA 3111-000-1301-2258 11,000
Vision USA 3111-000-1301-1232 12,000
Vision USA 3111-000-1301-1234 18,000
2 Vision Canada 2257-000-6111-0000 129,000
Vision Canada 2258-000-6111-0000 11,000
Vision Canada 2257-000-2101-3111 129,000
Vision Canada 2258-000-2101-3111 11,000
3 Vision China 1232-000-6111-0000 12,000
Vision China 1234-000-6111-0000 18,000
Vision China 1232-000-2106-3111 12,000
Vision China 1234-000-2106-3111 18,000
• Submit the Generate General Ledger Allocations process to create journals from this
allocation.
• The process adds intercompany clearing lines displayed in green to balance each
journal so that the intercompany allocation across the three ledgers can be posted
successfully.

Intercompany Allocations Example
2. Intercompany Transactions Created from Expense Allocation

Lines: Provider Distributions
Provider Receiver Transaction Provider Provider Account Debit Credit
Distribution
Vision Vision Ontario 1 1 3111-000-4111-0000 129,000

HQ
Vision Ontario 1 2 3111-000-1301-2257 129,000
Vision Quebec 2 1 3111-000-4111-0000 11,000
Vision Quebec 2 2 3111-000-1301-2258 11,000
Vision West 3 1 3111-000-4111-0000 12,000
Vision West 3 2 3111-000-1301-1232 12,000
Vision East 4 1 3111-000-4111-0000 18,000
Vision East 4 2 3111-000-1301-1234 18,000
• Submit the Generate Intercompany Allocations process to create transactions from your
allocation. The process creates intercompany transactions from the allocation lines and
submit the batch for processing.
• Provider distributions are shown in this slide. The process adds the intercompany
receivables or payables lines as required to balance the distributions. In this example
the provider intercompany receivable lines are displayed in green.

Intercompany Allocations Example
2. Intercompany Transactions Created from Expense Allocation

Lines: Receiver Distributions
Provider Receiver Transaction Receiver Receiver Account Debit Credit
Distribution
Vision Vision Ontario 1 1 2257-000-6111-0000 129,000

HQ
Vision Ontario 1 2 2257-000-2101-3111 129,000
Vision Quebec 2 1 2258-000-6111-0000 11,000
Vision Quebec 2 2 2258-000-2101-3111 11,000
Vision West 3 1 1232-000-6111-0000 12,000
Vision West 3 2 1232-000-2106-3111 12,000
Vision East 4 1 1234-000-6111-0000 18,000
Vision East 4 2 1234-000-2106-3111 18,000
The receiver intercompany payables lines are displayed in green.

Oracle Fusion Intercompany Transactions Overview
• Provides spreadsheet-based data entry.

• Provides automatic account generation for intercompany
transactions.
• Allows approval from all trading partners.
• Ensures online validation.
• Generates transactions from allocations created from
Calculation Manager.
• Balances transactions with multiple distributions and different
primary balancing segment values if required, during Posting
or Create Accounting processing.
• Allows manual creation of transactions through the user interface, spreadsheet entry,
transaction import, and transaction generation from allocations.
• Uses the Subledger Accounting Transaction Account Builder to generate accounts for
intercompany transactions to reduce data entry and prevent data entry errors.
• Sends intercompany transactions to all involved trading partners for approval.
• Ensures online validation of transactions before transferring them to GL to minimize
reconciliation issues.
• Controls which transactions require approval. Transaction types determine if
transactions are manually approved or automatically approved after an entry passes all
validation.
• Allows control of whether invoices are generated or not by using different transaction
types.

Intercompany General Ledger Integration
Oracle Oracle General

Intercompany Ledger
Transfer to GL GL Balances
Web UI
Open
Drilldown
Interfaces
(Import)
Drilldown
Excel
(FDI)
Journal
Entries
• Transfer intercompany transactions directly to the general ledger if you do not need
intercompany invoices.
• The general ledger transfer process enables you to automatically transfer to multiple
ledgers with a single submission request.
• When you have posted transactions in the general ledger, you can inquire on account
balances or journal lines, and drill down to the source intercompany transaction.

Intercompany Receivables and Payables Integration
Create Accounting
Oracle Oracle Oracle

Oracle
Intercompany Receivables Payables General Ledger
Transfer to GL Create AR Invoice

GL Balances
Web UI AR Invoice AP Invoice
Open
Drilldown Record AP Invoice
Interfaces
(Import)
Drilldown
Drilldown Drilldown
Excel
(FDI) Dr Cr Dr Cr
Subledger Subledger Drilldown

Accounting Accounting
Journal
Entries
Drilldown
This is applicable only if you intend to generate invoices for intercompany transactions as is
required in some legal jurisdictions. You can create physical invoices in Oracle Fusion
Receivables and record them in Oracle Fusion Payables.
• Enter the transactions using the user interface, Oracle Application Development
Framework Desktop Integrator, import them from an external source or generate them
from allocations created by Calculation Manager.
• Create receivables invoices for the appropriate intercompany customers by running the
Transfer to Receivables process, which makes use of the Import AutoInvoice program.
• Record the invoice in Payables by running Transfer to Payables. The invoices
generated in the Receivables system are recorded in the Payables system against the
intercompany suppliers, with the same amount and accounting date.
• Run the Create Accounting process in Receivables and Payables.
• Transfer accounting entries to the General Ledger with the option to automatically run
journal import and posting.
• Drill down from general balances or journal lines to general ledger journal entries, then
to the subledger journal entry, and finally to the source receivables or payables
transaction.

Intercompany Transactions Dashboard
• Provides intercompany accountants with the information they

need to perform their daily jobs.
• Allows proactive monitoring of incomplete or unapproved
transactions in the work area.
• Facilitates collaboration with trading partners and coworkers
to complete the process.
• Provides easy access to transaction screens and reports.
Navigate to: Intercompany Accounting > Transactions

The dashboard for Intercompany transactions is available to review transactions requiring
attention, requiring approval, that are new, and have import errors and for drill down to edit or
view transaction details.

Manual Intercompany Transaction Processing Steps
1. Create manual intercompany transactions using:

– Create Transaction task
– Create Batch in Spreadsheet task
– Custom program to transfer transaction data from an external
system into interface tables.
– Generate intercompany transactions from allocations.
2. Create, edit, and optionally submit intercompany transactions
for approval.
3. Transfer transactions:
– To Oracle Fusion General Ledger as journal entries that are
then posted.
– To Oracle Fusion Receivables where invoices are generated.
– To Oracle Fusion Payables to be recorded as payables
invoices.
• The intercompany transactions processing flow involves creating a transaction first. This
can be done in the user interface, via spreadsheet or import or through the Generate
Intercompany Allocations process.
• The transaction then needs to be submitted for manual or automatic approval.
• Once approved, the transaction has to be transferred to general ledger or if it requires
invoicing, it has to be transferred first to receivables and then payables.

Intercompany Transactions Setup
The following setup is required:

• Define Intercompany System Options
• Define Intercompany Transaction Types
• Define Intercompany Period Status
• Create Intercompany Organization
• Define Invoicing Options
• Define Transaction Account Rules
• Define Intercompany Balancing Rules

Manage Intercompany System Options
Define intercompany system options to set up intercompany

processing rules at an enterprise level.
Navigate to: Setup and Maintenance > Manage Intercompany System Options
• Generate automatic batch numbering or allow manual batch number entry.
• Enforce an enterprise-wide currency or allow intercompany transactions in any currency.
• Determine the minimum transaction amount allowed for an intercompany transaction.
• Choose a conversion rate type that is used when transferring foreign currency
transactions to general ledger, receivables and payables.
• Allow receiver to reject intercompany transactions.
• Set an intercompany calendar that can then be used to open and close periods by
intercompany transaction type.
• Specify a default intercompany transaction type.
• Summarize distributions for receivables invoicing to control if intercompany provider
distribution lines for each transaction are summarized into a single receivables invoice
line, or shown as separate lines on the receivables invoice.

Manage Intercompany Transaction Types
Define intercompany transaction types to process your

transactions. You can also determine whether invoicing in
receivables and payables is required, and whether manual
approval is required.
Navigate to: Setup and Maintenance > Manage Intercompany Transaction Types
• Control entry of intercompany transactions by opening and closing periods by
transaction type.
• Define intercompany balancing rules by intercompany transaction type.
Identify transaction types with the following options:
• Manual Approval: Requires receivers to manually approve transactions.
• Invoicing: Determines whether the transactions are routed to Receivables and Payables
for invoice generation and recording or if they are routed directly to General Ledger for
posting.
- This option can be overridden by the Manage Legal Jurisdiction legal function,
which contains the Generate intercompany invoice option.
- If the invoicing option for the transaction type is not enabled, but either the provider
legal entity or receiver legal entity has the legal function Generate intercompany
invoice assigned, invoices are generated.

Manage Intercompany Period Status
The opening and closing of intercompany periods by transaction

type controls whether users can enter transactions for a specific
intercompany period and intercompany transaction type.
• Navigate to: Setup and Maintenance > Manage Intercompany Period Status
• Identify the calendar to be used for intercompany functionality by selecting the calendar
in the Manage Intercompany System Options task. You can select the predefined
general ledger calendar that you want to use for intercompany periods.
• Change the selected calendar if the intercompany period status is either Never Opened
or Closed.
• Open and close periods as well as initiate the Sweep Transactions process to move
open transactions from one period to a future period.

Manage Intercompany Organizations
• Create intercompany organizations and assign legal entities to

them.
– One-to-one mapping between an intercompany organization
and a legal entity OR
– Multiple intercompany organizations mapped to a single legal
entity
• Act either as a provider or a receiver in intercompany
transactions.
• Initiate an intercompany transaction only for those
organizations that you can access.
• Associate an organization to a receivables BU and a payables
BU if it engages in transactions requiring invoicing
• Disable intercompany organizations that have no open
transactions.
Optionally, you can assign receivables and payables business units to the organization if you
require invoice generation.
If the organization will be a provider that raises intercompany invoices, it needs to be
associated to a receivables BU.
If the organization will be a receiver that needs to record payables invoices in AP, it needs to
be associated to a payables BU.
When you create an organization, the following attributes should be considered:
• Legal Entity
• Receivables Business Unit
• Payables Business Unit
• Default Organization Contact

Map Intercompany Organizations
One intercompany organization to one legal entity
Example
The graphic provides an example of mapping each legal entity to one intercompany
organization.
• In the Legal Entity scenario, a one-to-one mapping exists between legal entities and
intercompany organizations.

Map Intercompany Organizations
Multiple intercompany organizations to one legal entity
Map Intercompany Organizations to lower-level management entities if you want to use

manual transactions for activity between cost centers or divisions.

Manage Intercompany Organizations
Navigate to: Setup and Maintenance > Manage Intercompany Organizations

Create intercompany organizations and map them to legal entities and if invoicing is required,
map them to receivables and payables business units.

Define Invoicing Options
• To define the rules for generating intercompany invoices.

• To generate invoices for intercompany transactions using
Oracle Fusion Receivables and Oracle Fusion Payables.
Navigate to: Setup and Maintenance > Define Invoicing Options

• Intercompany transactions that need invoices to be generated for them, require the
following additional setup.
- Customer Supplier Association – Each legal entity requiring invoicing must be
associated with a customer account and/or supplier.
- Intercompany Receivables Assignments – Each receivables business unit
requiring invoicing must be associated with a receivables transaction type and a
receivables memo line and this can be done per intercompany transaction type.

Manage Intercompany Customer and Supplier
Assignments
• Use these assignments to identify the customer that is used
for intercompany invoices when this legal entity is a receiver
and the supplier that is be used when this legal entity is a
provider.
• Associate each legal entity with one supplier and one
customer account.
• Associate each legal entity with a customer account, supplier
or both.
• Customer Account: Assign a unique customer account to the legal entity of the
organization that receives and approves intercompany transactions. The customer
account must have an active bill-to site that is marked as a Primary site and it must be
an internal customer. Create and maintain customers in Oracle Receivables.
• Supplier: Assign a unique supplier to the legal entity of the organization that initiates
intercompany transactions. Create and maintain Suppliers in Oracle Procurement. The
supplier must have an active primary pay site.
• Additional Considerations: A customer or a supplier can be associated with only one
legal entity. The customer account and supplier assigned to the legal entity can be
modified at any time.

Manage Intercompany Customer Supplier Assignments
Navigate to: Setup and Maintenance > Manage Intercompany Customer and Supplier
Assignments
For each legal entity engaged in intercompany activity that requires invoicing, assign a
customer account and supplier chosen from the available list of values.

Manage Intercompany Receivables Assignments
• You must complete a receivables assignment if you require

invoices for your Intercompany transactions.
– Choose the receivables business unit and Intercompany
transaction type.
– Assign the Receivables transaction type and Receivables
memo line that the receivables application uses to generate an
invoice.
• A default Receivables transaction type and Receivables
memo line are provided.
• Intercompany provides a default Receivables transaction type of Intercompany and a

default Receivables memo line of Global Intercompany. These defaults are used when
no other assignments exist. However, you can set up individual assignments for each
Receivables business unit and Intercompany transaction type to override the default
values.
• First, select a business unit and Intercompany transaction type, and then select the
Receivables transaction type and Receivables memo line. Both Receivables transaction
types and Receivables memo lines are set-enabled objects and you associate a
reference set with the BU for these two objects. Then the transaction processing
identifies the correct setup to use based on the reference set associated.

Manage Intercompany Receivables Assignments
Navigate to: Setup and Maintenance > Manage Intercompany Receivables Assignments
Assign receivables transaction type and receivables memo line to each combination of
business unit and intercompany transaction type.

Define Transaction Accounts for the Intercompany
Transactions
Navigate to: Setup and Maintenance > All Tasks > Define Transaction Account Rules
The Define Transaction Accounts task list provides the ability to configure the revenue and
expense accounts for your provider and receiver distributions.
Transaction account definitions are assigned at the ledger and subledger levels. Transaction
attributes are used in account rules, which are used in transaction account definitions.

Transaction Account Types
• Transaction Account Types are:

– Intercompany Provider Distribution Account
– Intercompany Receiver Distribution Account
• Assign to Transaction Account Type:
– Account combination or segment rules.
– Sources are available to use in the account rules.
Navigate to: Setup and Maintenance > Manage Transaction Account Types
Intercompany uses the attributes of the batch, such as transaction type and provider and
receiver legal entities to ascertain which rule to use.
Intercompany is used to build the provider and receiver distribution accounts, for example, the
income and expense accounts.
• Intercompany Provider Distribution Account: Used for the distribution account for the
provider side of the transaction.
• Intercompany Receiver Distribution Account: Used for the receiver side of the
transaction.

Intercompany Transactions Approvals
• The following setup is required:

• FinFunTransactionApproval
– Transaction approval flow.
– Set up as many groups and rules as required.
• FinFunInterDistRequestForAction
– Flow when provider submits without entering any receiver
distributions AND transaction does not require manual
approval.
– Create approval group for each receiver organization
containing all users that have access to that organization
• Intercompany approval rules are integrated with Approval Management extensions

(AMX) and used in the Intercompany module.
• You must set up the FinFunTransactionApproval task so that transactions requiring
manual approval works.
• Additionally, you need to set up FinFunInterDistRequestForAction task to handle the
situation where a transaction that does not require manual approval, and is
automatically approved, is submitted without the receiver distribution. This incomplete
transaction cannot be automatically approved until the receiver distribution is entered
therefore the SOA task generates a notification requesting the receiver distribution be
entered.

Example: Intercompany Transactions Approvals
• Receiver Org = Vision Foods

• Users with Access = A Brown, C Jones, D Smith
• Vision Foods Approval Group should contain A Brown, C
Jones, D Smith, so ALL these users receives the notification
that receiver distributions need to be entered.
• Once the receiver distribution is entered in the inbound
screen, the transaction is automatically be set to Approved
• In this example the receiver organization can be accessed by three users, A Brown, C
Jones and D Smith. These users can all enter receiver distributions for this organization
on the inbound screen.
• An approval group Vision Foods is created and all three users are added to it.
• When a transaction with receiver organization Vision Foods is submitted without
receiver distributions entered, each of the three users in the group receives a notification
that receiver distributions need to be entered.
• Once one of them enters the distribution, the transaction status is automatically be set to
Approved.
• If the Vision Foods approval group only contained A Brown and C Jones but D Smith
who also has access to the organization, entered the receiver distribution despite not
receiving the notification, the transaction would not be set to Approved and would
remain in the Received status. The recommendation is to ensure that each receiver
organization is associated with an approval group containing all of the users who have
access to that organization.

Navigate to: Setup and Maintenance > Manage Intercompany Balancing Rules
• Intercompany Balancing Rules by Transaction Type are used to generate the
intercompany receivables account for the provider and the intercompany payables
account for the receiver.
• If an intercompany transaction has many distribution lines with many different primary
segment values, it needs to be balanced when it is posted to general ledger or when it is
transferred to Receivables and Payables and create accounting is run. In this scenario,
Intercompany Balancing Rules by Source and Category combination are used to
balance the accounting for the transaction.

Intercompany Organizations
Topic Decisions
Can I have more than one You achieve this by creating multiple intercompany
receivables business unit organizations, assigned to the same legal entity. Each
and one payables organization can have a different receivables and payables
business unit.
business unit assigned to
a legal entity for
intercompany transaction
processing?

Intercompany Reconciliation
The Intercompany Reconciliation process starts with running the

Prepare Intercompany Reconciliation Reporting Information
process from within the reconciliation work area.
• Choose from a variety of parameters to determine what data
appears on your reports. For example, choose the provider
legal entity and receiver legal entity for which you want to run
reconciliation.
• When the Prepare Intercompany Reconciliation Reporting
Information process has finished successfully, choose your
request from the list of requests under the BI Publishing
Options section and view the report.
This report displays the intercompany receivables and intercompany payables balances in
summary for a period, and any differences between them.
Drill down from the hyperlinks to view the balances by source and then by journal lines. You
have full drill-down capabilities to the general ledger journal, subledger journal entry, and
source receivables or payables transaction.
Intercompany reconciliation leverages Business Intelligence reports to display the data from
the extract process. The reports themselves are not available to be submitted from the
Schedules Processes page.

Reconciliation Reports
Intercompany Reconciliation:
• Provides reports to assist you with reconciling your
intercompany receivables and intercompany payables
accounts, and to identify any differences.
• Enables you to identify either the receiver or provider side of
an intercompany transaction that is not posted to the
Intercompany Receivables or Intercompany Payables
accounts.
The reports show the following intercompany lines:
• Intercompany Receivables and Intercompany Payables lines
generated by the Intercompany Balancing feature.
• Intercompany Receivables and Intercompany Payables lines
generated for the provider and receiver of each intercompany
transaction.
Intercompany reconciliation reports do not include:

• Clearing company balancing lines.
• Ledger balancing lines generated when the primary balancing segment value is in
balance but either the second balancing segment or the third balancing segment values
are out of balance.
The reconciliation reports show the entered or transaction amounts of the journal entries
booked to the intercompany receivables and payables accounts for a pair of provider and
receiver legal entities. Because the accounted amounts may be different if the conversion
rates used for the intercompany receivables and intercompany payables are different, you can
run the reports using an additional currency and conversion rate that converts all amounts into
a common currency for comparison.

Intercompany Reporting and Analysis
• Use the Intercompany Transaction Summary and Account

Details reports to display information about your intercompany
transactions. These reports are Business Intelligence (BI)
Publisher reports.
• Use Oracle Transactional Business Intelligence (OTBI) to
perform ad hoc queries on intercompany transaction attributes
and details.
• Use OTBI to perform intercompany analysis based on the
distribution accounts from intercompany transactions.
Navigate to: Tools > Scheduled Processes

Practice 8-3 Overview: Creating an Intercompany Batch

• Submitting the Prepare Intercompany Reconciliation
Reporting Information process
• Reviewing the reconciliation report

Practice 8-4 Overview: Submitting and Reviewing
Reconciliation Reports
• Submitting the Prepare Intercompany Reconciliation
Reporting Information process
• Reviewing the reconciliation report

Additional References on My Oracle Support
https://support.oracle.com
• Fusion Intercompany Invoicing Flow: Doc ID 1584586.1
• Fusion Intercompany Transactions: Process Flow: Doc
1351148.1
• How to Create an Approval Rule for Intercompany Covering
the FinFunTransactionApproval Task: Doc ID 1588306.1
• Intercompany Transactions Troubleshooting Guide: Doc ID
1587957.1
Additional References on My Oracle Support https://support.oracle.com

Summary

• Explain the intercompany features.
• Set up intercompany balancing.
• Set up the intercompany transactions.
• Run intercompany reconciliation and reporting.

9
Configuring Financial Reporting

Objectives

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

The New Financial Reporting Center Overview
The New Financial Reporting Center is intended to be the primary user interface for General
Ledger reporting. The Financial Reporting Center:
• Offers state-of-the-art reporting and analytics capabilities.
• Reports from the Oracle Fusion General Ledger Balances Cube (GL Balances Cube) for
consistent, timely, and accurate information for all users.
• Retrieves results from the Financial Report objects and definitions stored in the
Enterprise Performance Management System Workspace, Fusion Edition (EPM
Workspace) under the BI Catalog.
Includes access These types of reports:
• Financial Reports: Reports built off 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. The Sunburst
visualization tool allows you to interact with your account balances across various
business dimensions in order to view balances from different perspectives.
• Smart View Reports: Smart View is a multidimensional pivot analysis tool 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. The new Financial Reporting Center is only a place for
users to upload an existing Smart View query in order to download it to their local drive
for use.
• Oracle Transactional BI Analyses: These analyses and reports are built off of
transactional tables using Subject Areas. These reports can be run by users in General
Ledger, Payables, Receivables, Cash Management, Intercompany, and so on.
• Oracle Transactional BI Dashboards: Dashboards put all the information, functions and
actions that a business user needs to do their job in one place. Dashboards are built off
Oracle Transactional BI objects like analyses and reports. These reports can be run by
users in General Ledger, Payables, Receivables, Cash Management, Intercompany,
and so on.
• Business Intelligence Publisher Reports: Most of these reports are predefined and must
first be submitted and resubmitted to see the latest data by the Oracle Enterprise
Scheduler System (ESS) through the Scheduled Processes navigation. These reports
can be run by users in General Ledger, Payables, Receivables, Cash Management,
Intercompany, and so on.
• BI Mobile Apps: Mobile App Designer is an application that enables you to create multi
touch 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.
Note: The icons in the graph are used in the Financial Reporting Center to represent each
type of report.

Other Reporting Tools Overview
There are 6 other Tools for Reporting in Financials:
Other Reporting Tool Report Type

Account Monitor
General Accounting Dashboard Financial Reports
Account Inspector
Reports and Analytics Oracle Transactional BI Objects
BI Catalog All Report Types except BI Publisher
Reports
EPM Workspace available from the Reports, Books, Snapshot Reports,
Financial Reporting Center. Snapshot Books, Financial Reporting
Batches, and Batch Scheduler
Enterprise Scheduler System (ESS) Oracle BI Publisher Reports
Even though the Financial Reporting Center is designed to be the main user interface for a
financial end user’s reporting needs, some users may choose to use any of the 6 other tools
for reporting in financials such as:
• General Accounting Dashboard: Provides access to:
- Account Monitor: Efficient monitoring and tracking of key account balances in real-
time
- Financial Reports: Access to live reports and books and published snapshot
reports and books created in Financial Reporting Studio, with multiple output
options including HTML, PDF, Excel, or Excel in Query-Ready mode using Smart
View enabled formats.
- Account Inspector: Perform ad hoc queries with drill down to underlying journals
and subledger transactions

• Reports and Analytics: This other reporting tool has a panel that reflects the folder
structure of the BI Catalog. Users can access and run any Oracle Transactional BI
analysis, report or dashboard. Users cannot run Financial Reports or BI Publisher
reports from this interface. This interface can be used by all financials users.
• BI Catalog: A component of the Enterprise Performance Management Workspace where
you can run all report types. You cannot run BI Publisher reports from here.
• EPM Workspace: Create Reports, Books, Snapshot Reports, Snapshot Books, Financial
Reporting Batches, and Batch Scheduler and schedule batches to automatically run and
burst to email.
• Enterprise Scheduler System (ESS): Only BI Publisher reports can be submitted from
this interface. User 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.

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

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

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

Live Reports and Published Snapshot Reports
Boardroom-Ready Financial Reports

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

Practice 9-1 Overview: Using the New Financial
Reporting Center
• Navigating to the Financial Reporting Center.
• Running a Balance Sheet report.

Oracle Fusion General Ledger Balances Cube
Overview
Before creating financial statements or doing analysis on balances, it is useful to understand

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

Dimension Values in Reporting
You can derive different amounts to meet financial reporting

requirements by using various combinations of dimension
members.
Dimensions are used in the following reporting tools and features:
• Financial Reporting Studio
• Smart View
• Live reports
Before a report or analysis can produce results, all the cube dimension’s must have a value.
The value can be defined in the report definition or at the time of submission.
Both the Financial Reporting Studio and Smart View offer a member selector to define the
dimension’s member values within the report or analysis.
When running a live report, a dimension either becomes an initial prompt or allows the user to
choose a new dimension value dynamically while viewing the results.

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

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

GL Balances Cube: Default Values
Many dimensions have default member values that can be used

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

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

Dimension Possible Default Additional Information

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

Dimension Possible Values Default Additional

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

Smart View Overview
Smart View is:

• Microsoft Excel Based Reporting
• Optionally, available for upload to Financial Reporting Center
and then download to your local drive for use.
• Smart View has two main tools:
– Ad hoc Analysis: Enables you to interactively analyze
balances.
– Financial Reports: Define reports like income statements and
balance sheets using a familiar spreadsheet environment.
Smart View is a multidimensional pivot analysis tool combined with full Excel functionality.
Smart View is a Microsoft Office add-in that must be loaded to each client.
Download the installation files in Workspace from Navigator > Financial Reporting Center >
Open Workspace for Financial Reporting > Tools > Install > Smart View. Alternatively,
download Smart View from
http://www.oracle.com/technetwork/middleware/epm/downloads/smart-view-1112x-
1594693.html.
You can install Smart View only on Windows operating systems. Once Smart View is
installed, it must be configured to connect to Oracle Fusion Applications. Obtain the Smart
View Shared Connections URL information from your system administrator or derive the URL
following these steps:
1. Open Workspace for Financial Reporting from the Financial Reporting Center task
panel.
2. Edit the Workspace URL, for example, if the Workspace URL is https://fusionsystemtest-
p-external-bi.us.oracle.com/workspace/index.jsp.Remove index.jsp and add
SmartViewProviders at the end of the URL.

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.
3. Copy the URL.
4. Open Excel.
5. Navigate to the Smart View menu > Options > Advanced.
6. Paste the URL in the Shared Connections URL field.
7. Click on the OK button.

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

• Retrieve and analyze data by selecting members.
• Perform a variety of operations, including formatting and
designing your reports.
• Use functions.
A Smart View analysis allows you to:

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

Smart View: Query Designer
Create financial reports such as Income Statements and Balance

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

Creating Financial Reports
• Design traditional financial report formats such as balance

sheets, profit and loss statements, and cash flow reports.
• Design nontraditional reports for financial or analytic data that
include text and graphics.
Note
• The material presented in this lesson is an introduction to creating reports.
• More information can be found in the Oracle Hyperion Financial Reporting Studio User's
Guide or by taking one of these Oracle University courses: Oracle Hyperion Financial
Reporting for Essbase and Planning or Oracle Hyperion Financial Reporting for
Financial Management.

Financial Reporting Studio Overview
Financial Reporting Studio enables report authors to use a

graphical report layout with report components, such as text
boxes, grids, images, and charts, to design reports.
The Financial Reporting Studio is a client based financial report definition tool that:
• Uses drag and drop functionality to create a grid to design the rows, columns and pages
of the financial report.
• Has additional report components such as text boxes, images, and charts that may be
included on a report.
• Contains grids and other objects that are reusable across multiple reports.
• Uses the GL Balances Cube dimensions on either rows, columns, pages, or Point of
Views (POV).
• Allows rows and columns that can be either data, formulas, or text.
• Can include calculations or mathematical functions.

Installing and Configuring the Financial Reporting
Studio
Financial Reporting Studio is client-based software.
Download the installation files from Workspace by navigating to:
Financial Reporting Center > Click on the Tasks panel drawer >
Open Workspace for Financial Reporting. Once Workspace is
launched, click Tools > Install > Financial Reporting Studio.
After completing the installation, obtain financial reporting server
information from your system administrator to connect from the
local client to the Oracle Fusion instance.
Note: For more information on configuring Financial Reporting Studio client for users, see
Oracle Hyperion Enterprise Performance Management System Installation and Configuration
Guide for Oracle Hyperion Enterprise Performance Management. Especially the following
topics:
• Installing Financial Reporting Studio and Financial Reporting Print Server.
• Configuring the Financial Reporting Print Server.
• Administrative Information for Financial Reporting.

Report Designer
Use the Report Designer to:

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

Report Designer’s Standard Toolbar
The Standard toolbar contains shortcuts to standard features.
Button Description
New Report Opens a report palette.

Open Opens the dialog box to select an existing report.
Save Saves a report or object in the repository.
Repository Opens the repository.
Print Opens the print dialog box.
Displays the active report in the print preview
Print Preview
window.
Web Preview Displays the active report in a web browser.
You can use the View menu to display or hide the Standard toolbar. The table above
describes the Standard toolbar buttons.

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

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

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

Grids
Grids are the foundation for a financial report and extract data
from the GL Balances Cube.
A grid is the foundation for a financial report. It is a graphical representation of components

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

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

Practice 9-2 Overview: Creating a Report with the
Financial Reporting Studio: Defining a Grid
• Defining a new report and grid.
• Selecting the point of view dimensions for the grid.
• Selecting account dimension members.
• Saving a report.

Defining Formulas
The formula bar:

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

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

Practice 10-3 Overview: Creating a Financial Report:
Adding a Formula for Total Expenses

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

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

• Define the StartMember.
• Specify the Offset number.
• Define the EndMember.
Functions can be used on a dimension if a specific member value is not used. Functions give
more flexibility to the report for returning the desired data. Since this is only an Introduction to
the Financial Reporting Studio more information can be found in the Oracle Hyperion
Financial Reporting Studio User's Guide or by taking one of these Oracle University courses:
Oracle Hyperion Financial Reporting for Essbase and Planning or Oracle Hyperion Financial
Reporting for Financial Management.
The range function is useful for creating multiple columns or rows of data with one initial
setup. For example, your company requires a rolling 12 Period Income Statement. Use the
range function on the Column AccountingPeriod dimension to achieve this. When using the
Range Function, you must:
• Define the StartMember.
• Specify the Offset Number.
• Define the EndMember.

For this example, the Startmember would use another function called RelativeMember. The
RelativeMember would be defined as Current Point of View. Next, you would need to specify
the Offset. The Offset can be a positive or negative number. If you used -12 then the first
column on the report would display 12 periods back from the Current Point of View. The
Current Point of View is the period the report is targeting. For example, If you want to see a
report from Jan-14 through Dec-14 with Dec-14 as the “Current Point of View” you would
need to define the EndMember or the last column in the range as Current Point of View.

Defining a Rolling 12-Period Column

• Using the range function to create a rolling12-Period column.

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

The Ledger dimension in the screen shot is on the Grid POV with a member Value of US
Primary Ledger. Therefore, that dimension is not visible on the User POV. It has been defined
at the Grid level

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

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

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

Property Sheet
Use the Property Sheet to set various options for a report

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

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

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

Text Box Objects
Text box objects allow you to:

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

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

Adding a Logo and Title
• Adding a logo.
• Inserting a title.

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

Practice 9-8 Overview: Reviewing a Report

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

Infolets Overview
• Select the page control dot at the top of the Welcome

Springboard to view a specific infolet page.
• Use the dots to return to the Welcome Springboard.
• Use the arrow in the lower corner of the infolet to change
views.
• Click on the Actions menu in the top right corner of the infolet.
Page Control Dots

Use infolets to view information at a glance from different sources in an efficient and timely
way directly from the Welcome Springboard. You have the right information instead of just
more data to sift through.
Mobile device support is available to take your work on the go enabling you to close your
books quickly. You can spot trends and exceptions to gain insights about your financial
results in real-time.
Infolets are available for General Ledger, Intercompany, Budgetary Control, and Cash
Management.
Note: You can only view those infolets that you have permission to access.

Infolet Repository
• The Infolet Repository displays the infolets available for each

infolet dashboard.
Infolet Repository Icon
Navigate to: Welcome Springboard > General Accounting Infolets dot

The infolet repository displays the available set of infolets available based on your access
privileges.
• Click the Infolet Repository icon in the upper right hand corner or the page, then select
or deselect the infolets you want to use and drag and drop infolets in the order that you
want them displayed.
• Click the Actions menu in the upper right hand to view a list of actions that can be
performed for that infolet. The list varies by infolet. For example, actions:
- View the last updated date on when process ran.
- Run extracts.
- Refresh the view.
- Edit title and enable views
- Hide the infolet
• Use infolets to aggregate key information for a specific area, for example, your sales
pipeline, employee turnover, or other business transactions.

General Accounting Infolets
• Tracking the financial close process with:

– Close Calendar
– Open Subledgers
• Managing day to day operations with:
– Journals
– IC (Intercompany) Transactions
– Allocations (Unallocated Costs)
Tracking the financial close process with:

• Close Calendar:
- Shows the ledger and accounting period referred to by all the General Accounting
Infolets on the page.
- Shows where you are in your close cycle for that accounting period.
- Enables you to change the ledger or specify an override for the accounting period
assigned by the application by navigating to Setting and Actions menu > Set
Preferences.
- Has a positive value if the number of days are past the accounting period. For
example, the positive number of 64 in the image above, shows that you are 64
days beyond the end date of the 12-15 accounting period which ended on Dec 31,
2015.
- Has a negative value if the number of days are until the end of the accounting
period.
• Open Subledgers: Displays the subledgers that are still open for the accounting period
based on the period status for each module.

Managing day to day operations with
• Journals: Provides a quick overview that shows:
- How many journals are outstanding for the accounting period based on user’s
defined threshhold.
- The total amount of all outstanding transactions including journals that are
unposted and incomplete pending approval or in an error status.
• IC (Intercompany) Transactions: Displays the total amount and batch count of all
transactions that have not completed the intercompany transaction flow based on the
user’s defined threshold.
• Allocations (Unallocated Costs): Indentifies the residuals amounts from allocations and
provides insight into remaining account details, balances, and activities. This infolet
requires a user defined account group.
- The colored portion of the circle shows the number of accounts that have been
fully allocated.
- The uncolored portion indicates the number of allocations that still have balances.
- The amount in the middle indicates the remaining allocation balance.

General Accounting Infolets
• Monitoring reconciliations with:

– IC (Intercompany) Reconciliation
– AP Reconciliation
– AR Reconciliation
• Assessing financial performance with:

– Revenues
– Expenses
Control your account reconciliations between your subledgers and general ledger, and
between your intercompany payables and receivables by monitoring reconciliations with:
• IC (Intercompany) Reconciliation:
- Speeds up intercompany reconciliation by highlighting variances between amounts
due from providers and receivers.
- Provides drill down to the report detailing the transactions that are not in balance.
• AP Reconciliation: Obtains an immediate calculation of the variance between your
payable subledger balance compared to what is shown in the general ledger.
• AR Reconciliation: Obtains an immediate calculation of the variance between your
receivable subledger balance compared to what is shown in the general ledger.
Note: Both the AP and AR Reconciliation infolets include extra options on the Actions menu
that allow you to run the intercompany extracts and refresh the view.

• Feature a quick click that opens a waterfall chart with more detail on the variances when
you click anywhere on the infolet. The chart:
- Explains the differences by identifying the classes of variance and the expected
magnitude in each of these reconciled items.
- Has green bars that represent a variance that is additive, which means you add
the variance to the subledger balance to match to the GL balance.
- Has red bars that indicate there is a decrease.
- Provides hover over controls that show you the precise amount and walk you
through the reconciliation itself.
- Provides a link from the bottom to allow you to view a summary reconciliation
report. You can drill down into the actual transactions from within the reconciliation
report.
Assessing financial performance with:
• Revenues: This infolet requires a user defined account group.
- Enables you to assess your financial performance by obtaining an instant view of
your revenue and expense performance.
- Highlights the best and worst performing revenue accounts determined by the
results for the period ended.
• Expenses: This infolet requires a user defined account group.
- Identifies the expense account with the most unfavorable variance between results
for the current period and a target or baseline,
- amount shown is the variance between the current balance of the account
compared to its target. A variance percentage with a performance indicator arrow
is also displayed.

Budgetary Control Infolets
Budgetary Control infolets enable you to track funds availability

and funds consumption on your critical control budgets.
Navigate to: Welcome Springboard > General Accounting Infolets dot.

There are 5 user configured infolets for budget consumed and 5 for funds available.
To configure the budgetary control infolets you must setup budget account groups.

Budget Consumed Infolet
• Displays the budget consumption for a specified group of

budget accounts.
Budget Consumed
Budget Consumed
Infolet Back
Infolet Front
Using the Budget Consumed infolet you can:

• Expand the infolet to see the budget accounts with the highest consumption
percentages for the control budget.
• View the funds available details by clicking on the budget account link on the expanded
view.

Funds Available Infolet
• Displays the funds available amount and percentage for

a specified budget account.
• Click on the funds available amount link to view
additional funds available details for the budget account

Custom Infolets Overview
• Monitor performance with user configurable interactive

dashboards based on user defined Oracle Transactional BI
reports.
• Drill from dashboards to detailed reports.
Navigate to: Welcome Springboard > Custom Infolets Dot.

Monitor performance with interactive dashboards based upon balances and supplemental
information such as targets and performance goals using highly configurable Oracle
Transactional Business Intelligence reports.
Drill from performance measures to details to investigate and analyze performance
differences.

Practice 9-9 Overview: Using Infolets Demonstration

• Navigating to the General Accounting infolets
• Exploring the various General Accounting infolets.
Note: Sign in with Casey.Brown and your assigned password to
perform this practice.

Account Groups Overview
• Account groups are easy-to-use reporting components that

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

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

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

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

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

Practice 9-10 Overview: Setting up the General
Accounting Expense Infolet
This practice demonstrates the following topics:
• Creating an public account group for the expense infolet.
• Viewing the Expense Infolet.

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

Sunburst Tool
The Sunburst visualization tool allows you to interact with your

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

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

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

Sunburst Options
Use the options on the right to further analyze

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

Practice 9-11 Overview: Viewing an Account Group
from the Financial Reporting Center Demonstration
This practice demonstrates the following topics:
• Searching for an account group.
• Viewing the results in the table view.
• Reviewing an account group in the Sunburst tool.

Oracle Transactional Business Intelligence Overview
Oracle Transactional Business Intelligence (Oracle Transactional BI) is a set of highly

interactive reporting tools providing strategic insight into a business answering questions that
are critical to executives and manages for making responsible business decisions. It reports
directly from the transactional tables and returns the results in real time thus eliminating the
need for a data warehouse. You can access your finished Analyses, Reports, and
Dashboards from the Financial Reporting Center.
With Oracle Transactional BI developers and end users alike can create meaningful analyses
and reports eliminating the need for SQL skills and resulting in real time information using
these tools:
• BI Composer: Allows users to create analyses and reports using graphs, charts, and
tables.
• BI Answers: Allows developers to create analyses and reports using graphs, charts, and
tables.
• BI Mobile App Designer: Allows developers to create analyses and reports using
graphs, charts, and tables for use on mobile devices.

From the analyses and reports, developers can then create:
• Dashboards: Allows users to access analyses, reports, links and so on all in one place.
• Custom Infolets: Allows users to monitor performance using dashboards or other
Oracle Transactional BI objects.
Oracle Transactional BI uses the Oracle BI Catalog which is the same one as used by the
Financial Reporting Center’s EPM Workspace thus unifying the look and feel for the end-user.

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

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

Oracle Business Intelligence Publisher: Overview
Oracle BI Publisher provides many predefined or seeded reports for Oracle Cloud Financials.
Predefined BI Publisher reports for Oracle Fusion Financials are set up to be submitted as
scheduled processes through the Enterprise Scheduler System (ESS) in Oracle Cloud
Applications. The Open link, therefore, is not available by default for these reports in the BI
Catalog.
Because it supports diverse document requirements with flexible customization capabilities,
developers can use layout editors to edit exiting layouts or create new layouts.
BI Publisher can only use a layout to produce results. A layout determines the details, the
placement of data, and the look and feel of the output results.
One BI Publisher report can support more than one layout allowing an end-user to obtain
different results as needed for the one or multiple data sources. Layouts generate high fidelity,
pixel-perfect reports to PDF, RTF, Microsoft Excel, Microsoft PowerPoint, and static HTML.

Also, at the time of submission, an end-user can choose to have the report produce multiple
outputs using different layouts at the same time. In other words, one submission can produce
the same report in PDF and another in HTML at the same time. Or one submission can
produce one report using layout1 and another using layout2 at the same time.
Because BI Publisher uses XML technology, the report output delivery supports multiple
destination types, including printers, faxes, e-mail and e-commerce.

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

Summary

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

10
Configuring Business Units and
Reference Data Sets

Objectives

• Explain business unit features.
• Discuss business unit considerations.
• Define business units.
• Understand the service provider model.
• Explain reference data sets and business functions.
• Discuss reference data sharing.

Common Applications Configuration for Financials
Common Applications Configurations are generally shared across all the financial applications
and include the following setups:
• Legal Structures (covered in the previous lesson)
• Financial Reporting Structures: Chart of Accounts and Calendars (covered in the
previous lesson)
• General ledger: Ledgers (covered in the previous lesson)
• Organization Structures: Business Units that:
- Process transactions.
- Produce Management reports.
- Secure transactional data.
• Reference Data Sets: Reflect your business rules and policies and can differ from country
to country. 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.

Business Units Overview
A Business Unit is an organization within an enterprise that performs one or many business
functions that can be rolled up in a management hierarchy.
Normally it has a manager, strategic objectives, a level of autonomy, and a responsibility for its
profit and loss.
Use Business units for:
• Processing of transactions: Process transactions on behalf of one or many legal entities.
• Management reporting: Rolls up in divisions or a management hierarchy based on the
structure of your chart of accounts to provide reporting to managers at all levels of your
organization.
• Security of transactional data: Secures subledger transactions. For example, if you run
your export business separately from your domestic sales business, 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.
• Reference data definition and sharing: Use the reference data sets that reflect your
business rules and policies and can differ from country to country. 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.

Business Unit Structure: Example
In this example Vision Corporation has 5 business units:

• One for each legal entity.
• One Corporate BU to act as a shared services center (Service Provider Model) for
procurement and payables payments.

Business Unit Definition Considerations
• How will you structure your ledgers, legal entities, and

business unit rollups?
• Do any financial reports need to be generated by business
unit?
• How can you set up your departments or business unit
accounts to achieve departmental hierarchies that align
accurately with 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 your business
units?

Implementing Business Units Overview
To Implement a Business Unit, you must:

• Manage Business Units.
• Assign Business Unit Functions.
• Manage Service Provider Relationships.
• Manage Business Unit Set Assignment.

Managing Business Units
The Manage Business Unit task allows you to:

• Create business units.
• Edit business units.
Business units can be created by either the rapid implementation spreadsheet upload or
through the Manage Business Unit task. If the business unit is created by the spreadsheet you
may need to navigate to the Manage Business Unit task to edit or add to some of the
properties.
The properties of a business unit are:
• Name: It is important to name your business units to reflect your organizational structure.
• Manager (Optional): Assign the manager responsible for the profit and loss of the
organization.
• Location (Optional): Based on geography Locations defined at implementation time.
• Default Set: This is the default Data Reference Set for the BU. If uploading from the rapid
implementation spreadsheet, the Common Set is automatically defaulted. You can create
your own reference data set and assign an existing BU to that set.

Assigning Business Unit Functions.
A business unit can perform many business functions in Oracle

Fusion Applications. A business function:
• Represents a business process, or an activity that can be
performed by people working within a business unit.
• Describes how a business unit is used.
• Functions that generate financial transactions will require a
primary ledger and a default legal entity.
Following are a list of Business Functions that relate to the Procure to Pay process:
• Expense management
• Materials management
• Inventory management
• Payables invoicing
• Payables Payments
• Procurement
• Receiving
• Requisitioning

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 associated to the same
ledger. Those business functions are:
• Expense management
• Materials management
• Payables invoicing
• Receiving
• Requisitioning
Note: The Below Legal Entity check box is used by Supply Chain Financials Orchestration. The
check box appears when you select Materials Management or Requisitioning business
functions. Such a business unit works with only one legal entity. In Financials, since a BU can
work for multiple legal entities, the check box is irrelevant.

Managing Service Provider Relationships.
Shared service centers are supported in the following ways:

• Service Provider Model: Allows a business unit to act as a
service provider to client business units. Personnel in a
shared service center can process transactions on behalf of
client business units.
• Business Unit Security: Allows personnel in a shared service
center access to the data for other business units.
The service provider model defines relationships between business units for a specific
business function. One business unit will be identified as a service provider and the other BU
as its client.
Use the service provider model to centralize Procurement and Payables payment business
functions.
Business Unit Security expands and creates a relationship between the transactions and the
data that users can process.

Service Provider Model for Procurement Services
In this example:
• Business unit BU 1 provides procurement services for business unit BU 2.
• Business unit BU 2 performs requisitioning and payables invoicing.

Service Provider Model for Payables Payment Services
You can implement the following types of payment service

models:
• Dedicated
• Self-Service
• Dedicated and Self-Service
With centralized payment processing, you:

• Have better control of supplier payments. You can:
- Group credit memos from one invoice business unit with standard invoices of other
business units, thereby reducing net cash flows.
- Communicate effectively with your suppliers and reconcile any disputes.
• Develop and use organizational skills effectively.
• Reduce processing costs by generating consolidated payments for invoices across
multiple invoice business units.

Payment Services Model: Dedicated
In the dedicated model, the payment business unit:

• Works solely as an outsourced payment processing unit.
• Services other invoice business units.
In this example, the US Headquarters business unit provides payment services for both the US
West and US East business units.

Payment Services Model: Self-Service
In the self-service model, the invoice business unit:

• Acts as its own payment services provider.
• Services itself.
In this example, the UK business unit processes its own payments.

Payment Services Model: Dedicated and Self-Service
In the dedicated and self-service model, the payment business

unit:
• Services other invoice business units.
• Services itself.
In this example, the UK business unit processes payments for:

• Its own invoices.
• Invoices for the Japan business unit.

Practice 10-1 Overview: Viewing Your Business Unit

• Reviewing your business unit.
• Viewing the assigned business unit business functions.
• Saving your business unit set assignment.
• Reviewing a service provider relationship.

Practice 10-2 Overview: Viewing the Assigned
Business Unit Functions
This practice covers the following topics
• Viewing the assigned business unit functions.

Manage Reference Data Sets
Reference data sharing helps organizations share common setup

data without unnecessary duplication.
• Define reference data and divide the data into partitions called
reference data sets.
• Assign the reference data sets based on your business needs
across your organizational entities.
Oracle Fusion Applications contains two predefined sets:
• Common
• Enterprise
You can create more reference data sets based on your business
and data sharing requirements.
For example, an organization has several business units and each business unit uses different
payment terms on a customer invoice. Instead of each business unit creating and maintaining
individual payment terms, you can define the payment terms reference data at the organization
level and partition the data (create reference data sets) so different payment terms are
assigned to each business unit.

Reference Data Sharing: Overview
• Create reference sets across tables or lookup types.

• Share information and data processing options among the
determinant types, such as business unit or asset book.
• Create separate and common sets and subsets for each
business unit or to share across several business units
depending upon its business requirement.
Manage Reference Data Sets: Use this page to create the Set Code, Set Name, and
Description fields that can then be assigned to reference data.
Manage Set Assignments for Set Determinant Type: Use this page to assign the reference
data sets to relevant reference objects.
• Select Common Set to share it across the organization.
• For multiple assignments, you can classify different types of reference data sets into
groups and assign them to reference entity objects.
• The assignment takes into consideration the determinant type, determinant, and
reference group, if any.

Practice 10-3 Overview: Creating a Reference Data Set

• Creating a reference data set.

Determinant and Determinant Types
• Determinant Type: The point of reference used in the data

assignment process. You can share the partitioned reference
data based on a business context setting called the
determinant type.
• Determinant: The value that qualifies the selected determinant
type.
For example, when managing set assignments for the set determinant type, if you select
Business Unit as the determinant type, you must provide the name of the business unit as the
corresponding determinant.

Determinant Types
The available determinant types used in the reference data

assignment are:
• Asset Book: A book that records information about assets
including their acquisition, depreciation, and retirement. An
asset book is tied to a ledger.
• Business Unit: A department or organization within an
enterprise.
• Cost Organization: An 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.

Assignments to One Set Only, with Common Values
• Most commonly used method.

• Allows defining reference data object instance across all sets.
• For example, Receivables Payment Types are assigned
to a:
– Common set that is available to all the business units. With the
common set, you do not have to explicitly assign transaction
types to each business unit.
– Business unit–specific set of transaction types.
– At transaction entry, the list of values for transaction types
includes transaction types from the set assigned to the
business unit, as well as transaction types assigned to the
common set that is shared across all business units.
EXAMPLE

Assigning Sets to Business Units
When you define a business unit, you assign the business unit a
default set. That default set becomes the set for the Payables
Payment Terms reference group.
Manage Set Assignments

Navigate to: Setup and Maintenance > Manage Implementation Projects > XXImplementation
Project > Financials > Define Common Applications Configuration for Financials > Define
Business Units > Manage Business Unit Set Assignment > Go to Task.
In this example, for business unit US1 Business Unit, the reference data set called Common
Set is assigned to the reference data object Payables Payment Terms.
Note: Use the Manage Business Unit Set Assignment task to change the default set.

Manage Reference Data Partitions
The graphic illustrates the partition of the Receivables Payment Terms into three reference
data sets: Enterprise, Common, and Shared. These sets are assigned to your four business
units. For example, you are entering an invoice for US2 Business Unit. The payment terms that
appear in the invoice's list of values are: Net 15 and Net 20 from the Shared Set, and Net 30
and Net 60 from the Common Set.
Types of reference data sets depicted:
• Common Set: Used globally across the organization as a common set. Add the Common
Set to the global Receivables Payment Terms, Net 30 or Net 60, to be used in all
business units.
• Shared Set: Used by a few business units, US1 and US2, that work with similar data and
therefore share the sets. Add the Shared Set to Receivables Payment Terms, Net 15 or
Net 20, that are defined by country or region where a few business units belonging to that
country or region use it.
• Enterprise Set: Unique to that business unit and not shared by any other business unit
within that organization. Add the Enterprise Set to the Receivables Payment
Term, Prepayment, defined by line of business and used only by that line of business
irrespective of the country or region where it operates.

Assignments to One Set Only, with No Common Values
• Simplest form.
• 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.
– Shared across multiple asset books, but all the values are
contained in only one set.
EXAMPLE

Assignments to Multiple Sets, with No Common Values
• Allows a reference data object instance to be assigned to

multiple sets. For example, Payables payment terms uses this
method. Each payment term can be assigned to one or more
than one sets.
– Assign the payment term Net 30 to several sets.
– Assign payment terms Net 15, Net 20, Net 60, Immediate, and
Prepayment to only one of your reference data sets.
• Provides payment terms to an invoice from only one reference
data set, the set assigned to the invoice’s business unit.
CONTINUED

Payables Payment Terms Example
Example: In the graphic, the US1 BU set provides Net 30, Immediate, and Prepayment. A
special shared reference data set was created to provide Net 30 and Net 60 for the UK
Financial Services and the US High Tech Bus. The US2 BU set uses the following payment
terms available: Net 15, Net 20, and Net 30.

Reference Data Set: Examples
Application Reference Data Object Method of Data Sharing
Payables Payment Terms Assignments to multiple sets, no

common values allowed
Receivables Remit-to Addresses Assignment to one set only, with
common values
Receivables Payment Terms Assignment to one set only, with
common values
Tax Tax Classification Codes Assignment to one set only, with
common values
Assets Depreciation Ceilings Assignment to one set only,
no common values allowed
Assets Depreciation Methods Assignment to one set only,
with common values
The list contains some of the reference data objects for the Oracle Fusion Financial
Applications that can be shared across business units and the method by which the reference
data for each is shared.

Setting Up Payment Terms for Reference Data Sharing
• Assign a reference data set to a business unit.

• Generate a data role for a reference data set.
• Provision a data role to the implementor.
• Create a payment term.
• Assign a reference data set to a business unit: Assign the business unit a reference data
set for the reference object Payables Payment Terms.
• Generate a data role for a reference data set: To assign a reference data set to a
payment term, you must first generate a data role for that reference data set. Generate
the data role using the predefined data role template called Financials Common Module
Template for SetID.
• Provision a data role to the implementor: Assign the reference data set data role to the
implementor who creates payment terms.
• Creating a payment term: Assign one or more reference data sets to the payment term in
the Set Assignment section on the Manage Payment Terms page.

Important: You must assign the predefined payment term Immediate to the reference data set
that is assigned to the business unit before you can define common options for Payables and
Procurement.
Note: You can assign payment terms to the predefined common set, which works like any other
set. The payment terms are available only to business units using the common set as the
reference data set, unless you assign the payment terms to other reference data sets as well.

Practice 10-4 Overview: Managing your Business Unit
Set Assignment
This practice covers the following topics
• Assigning your reference data set to the Payables payment
term object.

Practice 10-5 Overview: Provisioning Data Roles

• Searching for your user in Oracle Identity Manager.
• Assigning the data role for your business unit and SetID to
your user.

Summary

• Explain business unit features.
• Define business units.
• Discuss business unit considerations.
• Explain reference data sets and business functions.
• Discuss reference data sharing.

Oracle Fusion Financials Student Guide Part1

Uploaded by

Document Information

Copyright

Available Formats

Share this document

Share or Embed Document

Sharing Options

Did you find this document useful?

Is this content inappropriate?

Copyright:

Available Formats

Oracle Fusion Financials Student Guide Part1

Uploaded by

Copyright:

Available Formats

Oracle Financials Cloud:

Financials Implementation for R11

Student Guide - Volume I

Restricted Rights Notice

If this documentation is delivered to the United States Government or anyone using

U.S. GOVERNMENT RIGHTS

1 Introduction to Oracle Financials Cloud Implementation

2 Introducing Oracle Fusion Navigation

3 Introducing Functional Setup Manager

5 Discussing the Vision Story and Common Applications

6 Configuring Enterprise Structures

7 Configuring General Ledger Components

8 Configuring Oracle Fusion Intercompany

9 Configuring Financial Reporting

10 Configuring Business Units and Reference Data Sets

11 Configuring Oracle Fusion Tax

12 Configuring Subledger Accounting

13 Configuring Oracle Fusion Payables

14 Configuring Oracle Fusion Payments: Payables

15 Configuring Oracle Fusion Receivables

16 Configuring Oracle Payments: Receivables

17 Configuring Oracle Fusion Cash Management

18 Configuring Oracle Fusion Advanced Collections

Copyright © 2016, Oracle and/or its affiliates. All rights reserved.

After completing this course, you should be able to:

Copyright © 2016, Oracle and/or its affiliates. All rights reserved.

Oracle Financials Cloud: Financials Implementation for R11 1 - 2

Each lesson in this course:

Copyright © 2016, Oracle and/or its affiliates. All rights reserved.

In this course, the instructor:

Oracle Financials Cloud: Financials Implementation for R11 1 - 3

Classroom and Other Resources:

•Oracle Financials Cloud: Implementing Subledger Accounting

• Oracle Fusion Technology Library on OTN:

Oracle Financials Cloud: Financials Implementation for R11 1 - 4

Copyright © 2016, Oracle and/or its affiliates. All rights reserved.

Oracle Help Center is:

Oracle Financials Cloud: Financials Implementation for R11 1 - 5

Copyright © 2016, Oracle and/or its affiliates. All rights reserved.

Oracle Financials Cloud: Financials Implementation for R11 1 - 6

Link to the Video Area in Oracle Help Center

Copyright © 2016, Oracle and/or its affiliates. All rights reserved.

Link to the videos: http://docs.oracle.com/cloud/latest/financialscs_gs/financialscs_videos.htm

Oracle Financials Cloud: Financials Implementation for R11 1 - 7

• File Based Data Import

Copyright © 2016, Oracle and/or its affiliates. All rights reserved.

Oracle Financials Cloud: Financials Implementation for R11 1 - 8

Oracle Financials Cloud: Financials Implementation for R11 1 - 9

Copyright © 2016, Oracle and/or its affiliates. All rights reserved.

• Simple search entry: Just type your topic in the field.

Oracle Financials Cloud: Financials Implementation for R11 1 - 10

After completing this lesson, you should be able to:

Copyright © 2016, Oracle and/or its affiliates. All rights reserved.

Oracle Financials Cloud: Financials Implementation for R11 1 - 11

Oracle Fusion Applications is:

Copyright © 2016, Oracle and/or its affiliates. All rights reserved.

Oracle Fusion Applications is:

Oracle Financials Cloud: Financials Implementation for R11 1 - 12

Oracle Financials Cloud is a complete and integrated financial

Copyright © 2016, Oracle and/or its affiliates. All rights reserved.

Oracle Financials Cloud with Oracle Fusion Applications provides:

Oracle Financials Cloud: Financials Implementation for R11 1 - 13

• Multidimensional reporting platform.

Copyright © 2016, Oracle and/or its affiliates. All rights reserved.