D96139GC30 sg2

Oracle Internal & Oracle Academy Use Only
Oracle Financials Cloud: Enterprise

Structures with General Ledger
Implementation
Student Guide – Volume II

D96139GC30
November 2018 | D101491
Learn more from Oracle University at education.oracle.com

Authors Copyright © 2018, Oracle and/or its affiliates. All rights reserved.
Bruce Ingram Disclaimer
Kishore Singh This document contains proprietary information and is protected by copyright and
Kathryn Wohnoutka 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
in any way. Except where your use constitutes "fair use" under copyright law, you
Technical Contributors 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
and Reviewers the express authorization of Oracle.
Abhjit Dhakephalkar
The information contained in this document is subject to change without notice. If you
Julianna Dodick 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
Ivy Farren warranted to be error-free.
Rashmi Goyal
Restricted Rights Notice
Anant Iyer
Barbara Kostelec 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
Carolyn Luk applicable:
Sanjay Mall
U.S. GOVERNMENT RIGHTS
Bernardine Rogers 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
Gregory Roth license agreement and/or the applicable U.S. Government contract.
Deepak Seth
Trademark Notice
Angie Shahi
Xin Wang Oracle and Java are registered trademarks of Oracle and/or its affiliates. Other names
may be trademarks of their respective owners.
Linda Wong
Publisher
Srividya Rameshkumar
321121201818C
Contents
1 Introduction to Oracle Cloud Enterprise Structures with General Ledger

Implementation
Course Objectives 1-2
Course Approach 1-3
Oracle Cloud Implementation Resources 1-4
Oracle Help Center: docs.oracle.com 1-6

Oracle Cloud Application Service Pages 1-7
Video Subject Areas on the Oracle Help Center 1-8
Reference Guides 1-9
Friendly Search 1-11
Course Schedule 1-12
Lesson Objectives 1-14
Introduction to Oracle Cloud Applications 1-15
Oracle Cloud Strategy 1-16
Oracle Cloud Applications: Product Families 1-17
Oracle Financials Cloud: Overview 1-18
Financials Cloud: Key Features 1-19
Implementation Discussion 1-20
Common Applications Configurations: Overview 1-21
Legal Structure 1-22
Managerial Structure 1-23
Functional Structure 1-24
Common Application Discussion 1-25
Summary 1-27
2 Introducing Oracle Cloud Navigation

Objectives 2-2
News Feed Home Page Layout 2-3
Sections: Things to Finish and News and Announcements 2-4
Analytics Section 2-5
Navigator 2-6
Predefined Aquamarine Theme for News Feed Home Page Layout 2-7
Getting Started with Other Themes 2-8
Navigation Components 2-9
Welcome Springboard 2-10
iii
Favorites and Recent Items 2-11
User Interface 2-12
General Accounting Dashboard 2-13
Work Areas 2-14
Panel 2-15
Search Panel Overview 2-16
Practice 2-1 Overview: Running session warmer scripts 2-17
Practice 2-2 Overview: Getting Started in Oracle Cloud Applications 2-18
Infolets versus Infotiles 2-19
Infolets Overview 2-20
Infolet Repository 2-21

Infolets in the Newsfeed Theme 2-22
Practice 2-3 Overview: Exploring Infolets 2-23
Personalizations Overview 2-24
Setting User Preferences 2-25
Structure Work Area 2-27
Recreate Legacy Dashboards Using the Page Integration Tool 2-28
Saved Searches 2-29
Configuring Table Columns 2-30
Practice 2-4 Overview: Using Personalizations 2-31
Summary 2-32
3 Financials Setup Overview

Objectives 3-2
What is Functional Setup Manager? 3-3
Functional Setup Manager Benefits 3-4
Key Concepts 3-5
Review Offerings and Prepare to Opt In 3-6
Opt into Offering, Functional Areas, and Features 3-7
Review What’s New and Opt into New Features After Upgrade 3-8
Practice 3-1 and Demonstration 3-2 3-9
Manage Setup Data with Complete Transparency to Requirements 3-10
Manage Setup Data Your Way Using Flexible Processes 3-11
Manage Setup Data Using Functional Areas 3-12
Related Setup Tasks 3-13
Tasks with Scope 3-14
Manage Setup Data Using Implementation Projects 3-15
Create an Implementation Project 3-16
Review and Assign Tasks 3-17
Perform Assigned Implementation Tasks 3-18
Searching for a Task 3-19
iv
Rapid Implementation Task List 3-20
Practice 3-3: Accessing Task Lists and Tasks 3-21
Configure Auditable Setup Attributes and View Audit Report 3-22
Audit History Enablement 3-23
Manage Setup Data Entry in Bulk 3-24
Export and Import CSV Processes 3-25
Practice 3-4 (Optional) Managing Setup Data by Bulk Entry Using CSV Files 3-26
Copying Setup 3-27
Practice 3-5: (Optional) Copying Setup Data 3-28
Efficient Setup Data Migration 3-29
Best Practices for Managing Setup Across Environments 3-30

Best Practices for Managing Setup: Using a Gold Copy 3-31
How Does Setup Import Manage Data? 3-32
Export an Offering or a Functional Area 3-33
Create a Comparison for an Offering or Functional Areas 3-34
Import an Offering or a Functional Area 3-35
Export and Import an Implementation Project 3-36
Practice 3-6: (Optional) Migrating Setup Data 3-38
Learn More: Video Tutorials and User Guides 3-39
Summary 3-40
4 Overview of Security
Objectives 4-2
Oracle Financials Cloud Security Methodology 4-3
Security Model: Role Based Access Control 4-4
Security Reference Implementation 4-5
Job and Duty Roles 4-6
GL Predefined Job Roles 4-7
Privileges 4-9
Resources 4-10
Data Security Policies 4-11
Analyze Data Security Policies by Resource 4-12
Role Inheritance 4-13
Security Features Overview 4-14
Using Security Console 4-15
Compare Roles Feature 4-17
Move Function and Data Security Policies 4-18
Manage Data Access for Users Page 4-19
Automatic Data Provisioning 4-20
Processes to be Performed on Users and Roles 4-22
Practice 4-1 to 4-2 Overview: Using the Security Console 4-23
v
Practice 4-3 to 4-5 Overview: Creating and Managing User 4-24
Upgrade-Safe Management of Factory Shipped Roles 4-25
Enhanced Role Visualization 4-26
Search in Role Hierarchy Visualization 4-28
Tabular Role Hierarchy View 4-29
User Account Management 4-30
Users Categories 4-31
Add Users to User Category 4-32
User Name Generation Rules 4-33
User Name Generation Rule and Password Policy by User Category 4-34
Password Policies 4-35

Administrator Password Management 4-37
User Account Locking 4-38
User Password Management: Self-Service 4-39
Password Reset Process 4-40
User Password Changes Audit Report 4-41
Notification Templates 4-42
Practice 4-6 Overview: Managing Password Security and Notifications 4-44
Bridge for Microsoft Active Directory 4-45
Auditing Security 4-46
Security Resources 4-48
Summary 4-49
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-9
Vision Corporation Business Unit and Department Structure 5-10
Vision Corporation Distribution Structure 5-11
Vision Corporation Chart of Accounts Summary 5-12
Define Geographies 5-13
Geographies: Overview 5-14
Geography Structure 5-15
Geography Hierarchy 5-16
Geography Hierarchy Example 5-17
Geography Validations 5-18
Manage Geography Validations 5-19
vi
Address Cleansing 5-20
Geocoding Process 5-21
Importing Geography Options 5-22
Nokia Geography Reference Data Import 5-23
File-Based Import 5-24
Managing Geography Lookups 5-25
Tax Zone Types and Zones 5-26
Run Maintain Geography Name Referencing Process 5-27
Summary 5-28
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-27
Rapid Implementation Spreadsheet Sample Reports Preview 6-29
Practice 6-2 Overview: Entering Data in the Rapid Implementation
Spreadsheet 6-30
Completing the Accounting Configuration 6-31
Deployment Status 6-32
vii
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
Legal Authorities: Overview 6-39
Practice 6-6 to 6-8 Overview: Reviewing Legal Jurisdictions and Legal
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-49
Legal Entity and Its Relationship to Intercompany Transactions 6-50
Legal Entity and Consolidation Rules 6-51
Country-Specific Legal Entity Sequences 6-52
Practice 6-9 Overview: Searching for Your Legal Entity 6-53
Manage Legal Reporting Units 6-54
Legal Reporting Units: Points to Consider 6-55
Practice 6-10 Overview: Viewing a Legal Reporting Unit 6-56
Summary 6-57
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 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
viii
Practice 7-2, 7-3, and 7-4 Overview: Searching for and Deploying Your Chart of
Accounts 7-15
Define Segment Values 7-16
Assign Segment Attributes 7-17
Control Accounts Benefits 7-19
Control Accounts Explained 7-20
Practice 7-5 Overview: Entering Values 7-21
Defining Hierarchies 7-22
Account Hierarchy Purposes 7-23
Account Hierarchy Example 7-24
Create Account Hierarchies 7-25

Create Account Hierarchies Version 7-26
View Account Hierarchies 7-27
Published Account Hierarchy Example 7-28
Implementation Considerations 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 Implementation 7-41
Segment Value Security Examples 7-43
Segment Value Security Operators 7-44
Conditions 7-45
Implementing Segment Value Security 7-46
Segment Value Versus Data Access Set Security 7-47
Cross-Validation Rules 7-48
Cross-Validation Rules: Considerations 7-49
Dynamic Combination Creation Allowed 7-50
Filters Overview 7-51
Filters and Conditions 7-52
Practice 7-9 Overview: Defining Cross-Validation Rules 7-53
Manage an Accounting Calendar 7-54
Accounting Calendar Considerations 7-55
Start Date 7-56
ix
Period Frequency 7-57
Period Name Format 7-58
Calendar Type 7-59
Calendars with Different Period Frequencies 7-60
Adding a Calendar Year 7-62
Practice 7-10 Overview: Verifying Your Calendar 7-63
Calendar Auditing 7-64
Manage Currencies Overview 7-65
Currency Concepts 7-66
Currency in Subledgers 7-67
Define Currencies: Overview 7-68

Currencies Overview 7-69
Practice 7-11 Overview: Reviewing and Creating Currencies 7-70
Conversion Rate Types Overview 7-71
Cross-Currency Functionality 7-72
Explain Cross-Rate Rules 7-73
Practice 7-12 Overview: Creating Conversion Rate Types 7-75
Daily Rates Overview 7-76
Entering Daily Rates 7-77
Practice 7-13 and 7-14 Overview: Using Currency Rates 7-78
Summary 7-79
8 Configuring Ledgers
Objectives 8-2
Define Ledgers 8-3
Ledgers and Accounting Configurations 8-4
Define Ledger Components 8-6
Ledgers and Subledger Accounting 8-7
Manage Primary Ledgers 8-8
Practice 8-1 Overview: Searching for Your Ledger 8-9
Specify Ledger Options 8-10
Processes Using Ledger Options 8-11
Practice 8-2 Overview: Verifying Your Ledger Options 8-12
Balancing Segment Value Assignments: Overview 8-13
Balancing Segment Value Assignments to Legal Entities 8-14
Balancing Segment Values Assignments to Ledgers 8-15
Balancing Segment Value Assignment Report 8-16
Practice 8-3 Overview: Verifying Legal Entities and Balancing Segment
Assignments 8-17
Manage Reporting Currencies 8-18
Reporting Currencies: Conversion Levels 8-20
x
Practice 8-4 Overview: Defining Reporting Currencies 8-21
Define Secondary Ledgers 8-22
Secondary Ledgers: Scenarios 8-23
Secondary Ledgers: Conversion Levels 8-24
Secondary Ledger Example 8-25
Secondary Ledger Example Conclusion 8-26
Secondary Ledgers Mapping 8-27
Chart of Accounts Mapping Feature 8-28
Segment Mapping Rules 8-29
Account Mapping Rules 8-30
Review and Submit Accounting Configuration 8-31

Practice 8-5 Overview: Completing the Ledger Configuration 8-32
Balance Cubes: Overview 8-33
Balance Cubes Naming 8-34
Balance Cube Dimensions 8-35
Manage Ledger Sets 8-36
Practice 8-6 Overview: Creating a Ledger Set 8-37
Data Access Set Security: Overview 8-38
Data Access Set Security 8-39
Data Access Set Security: Example 8-41
Practice 8-7 and 8-8 Overview: Creating a Data Access Set 8-42
Summary 8-43
9 Configuring Journal Approval

Objectives 9-2
Approval Workflow: Overview 9-3
Approval Management: Overview 9-4
Manage Journal Approval Rules 9-5
Manage Journal Approval Rules Setup 9-6
Journal Approval Rule Considerations 9-7
Journal Approval Rule Example 9-9
Key Concepts: Assignees 9-10
Key Concepts: Rule Sets and Rules 9-11
Key Concepts: List Builders 9-12
Journal Approval Hierarchies 9-14
Manage Task Configurations 9-15
Assignees Tree 9-17
Rule Sets 9-18
Defining Rule Settings 9-19
Defining Rules 9-20
IF Component 9-21
xi
THEN Component 9-22
Rule Example 9-24
Deadlines 9-25
Notifications 9-26
Configuration 9-27
Access 9-28
Manage Approval Groups 9-29
Manage Approval Groups: Static 9-30
Journal Status Page 9-31
Withdraw Approval 9-32
Practice 9-1 Overview: Creating Journal Approval Rules 9-33

Simplified Workflow Rules Configuration 9-34
Rules Template 9-35
Data Sets 9-36
Configurable Email Notifications for Journal Approval 9-38
Configurable Email Notifications Process 9-39
Email Components 9-40
Adding a Branding Logo and Modifying Shared Components 9-41
Configurable Email Notifications Implementation Best Practices 9-42
Enabling Email Notifications 9-43
Using Quick Parts for Workflow Email Notifications 9-44
Summary 9-45
10 Configuring Oracle Intercompany

Objectives 10-2
Intercompany Overview 10-3
Intercompany Balancing Overview 10-4
Payables Invoice Example 10-5
Cross-Ledger Allocation Journals Example 10-6
Intercompany Balancing: Features 10-7
Balancing Setup 10-9
Specify Ledger Options 10-10
Balancing Rules: Order of Precedence 10-11
Manage Intercompany Balancing Rules 10-12
Manage Additional Intercompany Balancing and Clearing Options 10-15
Key Decisions and Best Practices 10-16
Demonstration10-1 Overview: Setting Up a New Rule 10-21
Practice 10-2 Overview: Viewing Intercompany Balancing Rules and Secondary and
Clearing Company Balancing Options 10-22
Intercompany Allocation Overview 10-23
Intercompany Allocation Journals 10-24
xii
Intercompany Allocation Transactions 10-25
Intercompany Allocation Requirements 10-26
Create Allocation Rules Setup Tasks 10-27
Intercompany Allocations Example 10-28
T – Accounts: Journal 1 10-34
Intercompany Allocations Example 10-37
Oracle Intercompany Transactions Overview 10-39
Evaluation of Intercompany Balancing Rules 10-40
Intercompany General Ledger Integration 10-41

Intercompany Receivables and Payables Integration 10-42
Intercompany Transactions Dashboard 10-43
Manual Intercompany Transaction Processing Steps 10-44
Intercompany Transactions Setup 10-45
Manage Intercompany System Options 10-46
Manage Intercompany Transaction Types 10-47
Manage Intercompany Period Status 10-48
Manage Intercompany Organizations 10-49
Map Intercompany Organizations 10-50
Manage Intercompany Organizations 10-52
Define Invoicing Options 10-53
Manage Intercompany Customer and Supplier Assignments 10-54
Manage Intercompany Receivables Assignments 10-56
Define Transaction Accounts for the Intercompany Transactions 10-58
Transaction Account Types 10-59
Intercompany Transactions: Approvals 10-60
Intercompany Transactions Approvals Example 10-61
Manage Intercompany Balancing Rules 10-62
Key Decisions and Best Practices 10-63
Intercompany Reconciliation 10-64
Reconciliation Reports 10-65
Intercompany Reporting and Analysis 10-66
Practice 10-3 Overview: Creating an Intercompany Batch 10-67
Practice 10-4 Overview: Submitting and Reviewing Reconciliation Reports 10-68
Additional References on My Oracle Support 10-69
Summary 10-70
11 Configuring Period Close Components

Objectives 11-2
Overview 11-3
xiii
Close Monitor Overview 11-4
Close Monitor Explained 11-5
Setting Up the Close Monitor 11-6
Navigating in the Close Monitor 11-7
Viewing in the Close Monitor 11-8
Open and Close Periods Life Cycle 11-9
Accounting Period Statuses 11-10
Accounting Periods: Overview 11-11
Period Close with Oracle Financials 11-12
Close Status Section 11-13
Period Close Best Practices 11-14

Practice 11-1 Overview: Opening the First Accounting Period 11-15
Period Close Checklist 11-16
Period Close Components 11-17
Allocation Concepts 11-18
Allocation Components 11-19
Defining Allocation Requirements 11-20
Generation of Allocations 11-21
Cross Ledger Intercompany Allocations 11-22
Step Down Allocation: Example One 11-23
Step Down Allocation: Example Two 11-24
Allocation Rule Concepts 11-25
Allocation Rule Deployment 11-26
Allocations: Best Practices 11-27
Practice 11-2 Overview: Creating and Generating an Allocation Rule 11-28
Revaluation Overview 11-29
Translation and Reporting Currencies Overview 11-30
Revaluation and Translation Concepts 11-31
Revaluation and Translation Setup 11-32
Revaluation Process 11-33
Revaluation Example 11-35
Practice 11-3 Overview: Creating a Revaluation 11-36
Translation Process 11-37
Translation and Remeasurement Solutions 11-38
Historical Rates and Amounts 11-39
Import Journal Entries: Overview 11-40
Journal Import Verification Process 11-41
Journal Import Validates 11-42
Reconciliation 11-43
Reconciliation Concepts 11-45
Clearing Accounts Reconciliation 11-46
xiv
Steps to Enable Clearing Accounts Reconciliation 11-47
Other Considerations 11-48
Performing Clearing Accounts Reconciliation 11-49
Practice 11-4 Overview: Clearing Accounts Reconciliation 11-51
Payables Tax Reconciliation with General Ledger Report 11-52
Summary 11-53
12 Configuring Financial Reporting

Objectives 12-2
Financial Reporting Center Overview 12-3
Other Reporting Interfaces Overview 12-5

Access to the Financial Reporting Center 12-6
Viewing Financial Reports from the Financial Reporting Center 12-7
Live Reports and Published Snapshot Reports 12-8
Practice 12-1 Overview: Viewing a Financial Report from the Financial Reporting
Center 12-9
Oracle General Ledger Balances Cube: Overview 12-10
Dimension Values in Reporting 12-11
GL Balances Cube: Dimensions 12-12
Default Values 12-14
Dimension Values and Defaults 12-15
Smart View Overview 12-18
Ad Hoc Analysis 12-19
Query Designer 12-20
Creating Financial Reports 12-21
Financial Reporting Studio: Overview 12-22
Installing and Configuring the Financial Reporting Studio 12-23
Report Designer 12-24
Report Designer’s Standard Toolbar 12-25
Financial Reporting Studio Components 12-26
Designer Toolbar 12-28
Grids 12-29
Practice 12-2 Overview: Creating a Report with the Financial Reporting Studio:
Defining a Grid 12-30
Defining Formulas 12-31
Available Formulas 12-32
Adding a Formula for Total Expenses 12-33
Using Functions: Range 12-34
Defining a Rolling 12-Period Column 12-35
xv
User and Grid Point of View Dimensions 12-36
Selecting Members 12-37
Defining the Grid and User Point of View Dimensions 12-38
Property Sheet 12-39
Property Sheet Component Objects and Features 12-40
Setting Properties 12-41
Text Box Objects 12-42
Image Objects 12-43

Adding a Logo and Title 12-44
Reviewing a Report 12-45
Practice 12-8 Overview: Reviewing a Financial Report 12-46
Infolets: Overview 12-47
Account Groups: Overview 12-48
Viewing Account Groups in the General Accounting Infolets 12-49
Defining Account Groups: Header Region 12-50
Defining Account Groups: Accounts Region 12-52
Demonstration 12-9 Overview: Setting Up the General Accounting Expense Infolet
for All Users 12-53
Generation of Reports and Account Groups Settings 12-54
Generation of Reports and Account Groups 12-55
Generate Financial Reports and Account Groups Process 12-56
Copy Account Group 12-58
Viewing Account Groups from the Financial Reporting Center 12-59
Sunburst Tool 12-60
Sunburst Icons 12-61
Sunburst Options 12-62
Demonstration 12-10 Overview: Viewing an Account Group from the Financial
Reporting Center 12-63
Demonstration 12-11 Overview: Generating Financial Reports and Account
Groups 12-64
Oracle Transactional Business Intelligence Overview 12-65
Financial Reporting Center and Oracle Transactional BI 12-66
Oracle BI Publisher Overview 12-67
Oracle Business Intelligence Publisher: Overview 12-68
Financial Reporting Center and Oracle BI Publisher 12-69
Summary 12-70
xvi
13 General Ledger Options
Objectives 13-2
Manage Suspense Accounts 13-3
Practice 13-1 Overview: Creating a Suspense Account 13-5
Manage Statistical Units of Measure 13-6
Practice 13-2 Overview: Creating a Statistical Unit of Measure 13-7
Manage Journal Sources and Categories 13-8
Journal Sources 13-9
Journal Categories 13-10
Practice 13-3 Overview: Creating a Special Journal Source and Category 13-11
Sequencing Options 13-12

Manage Document Sequences 13-14
Document Sequences: Types 13-15
Manage Accounting and Reporting Sequences 13-16
Configurable Sequencing Assignment Options 13-17
Accounting and Reporting Sequences Setup 13-18
Enforcing Accounting and Reporting Document Sequences 13-19
Practice 13-4 Overview: Creating an Accounting Sequence 13-20
Manage AutoPost Criteria Sets 13-21
AutoPost Criteria Sets: Parameters 13-22
AutoPost Criteria Sets: Elements 13-23
Manage AutoReverse Criteria Sets 13-24
Manage Accounting Automation 13-26
Additional Considerations for Accounting Automation 13-27
Manage Profile Options 13-28
Manage Processing Schedules 13-30
Practice 13-5 Overview: Creating a Processing Schedule 13-31
Summary 13-32
14 Introducing Consolidations
Objectives 14-2
Consolidation Methods 14-3
Reporting Only Consolidation Method: Example 14-4
Reporting Consolidation with Multiple Levels: Level One 14-6
Reporting Consolidation with Multiple Levels: Level Two 14-7
Elimination Entries Example 14-8
Elimination Entries Example: Transaction 14-9
Elimination Entries NA Level One Example: Elimination Entry 14-10
Balance Transfer Consolidation Method 14-11
Transfer Ledger Balances Process Parameters 14-12
Practice 14-1 Overview: Creating a Chart of Accounts Mapping 14-13
xvii
Practice 14-2 Overview: Submitting the Transfer Ledger Balances Process 14-14
Reporting Only Versus Balance Transfer: Pros 14-15
Reporting Only Versus Balance Transfer: Cons 14-16
Oracle Hyperion Financial Management Integration Overview 14-17
Financial Management Integration Option 14-18
Financial Management Integration Implementation 14-19
Mapping Segments to Financial Management Dimensions 14-20
Summary 14-21
15 Introducing Budgets
Objectives 15-2

Budgeting Preparation 15-3
Budget Scenario Dimensions 15-4
Integration with Oracle Hyperion Planning 15-5
Importing Budget Data from a Flat File 15-6
Importing Budget Data from a Flat File: Steps 15-7
Importing Budget Data from a Spreadsheet 15-8
Importing Budget Data from a Spreadsheet: Import Correction 15-9
Practice 15-1 Overview: Uploading a Budget Using a Spreadsheet 15-10
Practice 15-2 Overview: Creating a Smart View Ad Hoc Analysis 15-11
Summary 15-12
A Appendix A: Common Application Topics

Objectives A-2
Manage Oracle Social Network Objects A-3
Enablement Options A-4
Update Social Network Translations A-6
Update Translations A-7
Demonstration A-1: Managing Oracle Social Network Objects A-8
Oracle Social Network Reference Resources A-9
Define Flexfields A-10
Manage Flexfields A-11
Types of Flexfields: Descriptive A-12
Flexfield Concepts A-13
Flexfield Segments A-14
Flexfield Structure A-15
Flexfield Context A-16
Flexfield Category A-17
Flexfield Usage A-18
Accessing Flexfields for Configuration A-19
Using the Highlight Flexfields Command A-20
xviii
Accessing Flexfield Management Tasks and Searching for Flexfields A-21
Value Sets A-23
Value Set Validation A-25
Value Set Usage A-26
Descriptive Flexfields A-27
Descriptive Flexfields: Segments A-28
Descriptive Flexfields: Context Segment A-29
Descriptive Flexfields A-30
Adding Flexfield Segments on Application Pages A-31
Extensible Flexfields A-35
Extensible Flexfields Context A-37

Extensible Flexfields A-38
Extensible Flexfield Example A-39
Key Flexfields A-43
Key Flexfield Structure A-45
Key Flexfield Instances A-46
Key Flexfields A-47
Tips for Managing Key Flexfields A-49
Flexfield Implementation Flow A-51
Flexfield Reference Resources A-53
Define Lookups A-54
Sample Lookup Type A-55
Lookup Components A-56
Lookup Categories A-57
Manage Lookups A-58
Customize Lookups A-59
Define Profile Options A-60
Profile Options A-62
Profile Option Categories A-63
Profile Option Levels A-64
Profile Option Values A-65
Profile Options for Common Setup A-66
Quiz A-67
Define Attachments A-68
Key Concepts A-70
Manage Attachment Entities A-72
Manage Attachment Categories A-73
Attachment Category Security A-75
Example A-77
Solution A-78
xix
Quiz A-79
Summary A-81
B Appendix B: Implementing Financials for Asia/Pacific and EMEA

Objectives B-2
Managing Enterprise Financial Data Export Options for China B-3
Defining the Structure for Natural Accounts for China B-4
Enterprise Additional Account Attributes for China B-5
Summary B-6
C Appendix C: Predefined Reports for General Ledger

Objectives C-2
General Ledger C-3
GL BI Publisher Reports C-4
Practice C-1 Overview: Running a GL BI Publisher Report C-10
General Ledger Oracle Transactional BI Reports C-11
General Ledger Subject Areas C-12
Practice C-2 Overview: Running a General Ledger OTBI Report C-13
Intercompany C-14
Intercompany BI Publisher Reports: Reconciliation Reports C-15
Intercompany BI Publisher Reports C-16
Intercompany Oracle Transactional BI Reports C-17
Practice C-3 Overview: Running an Intercompany Transaction Summary
Report C-18
Budgetary Control C-19
Budgetary Control BI Publisher Reports C-20
Budgetary Control Subject Areas C-23
Subledger Accounting C-24
Subledger Accounting Predefined Reports Overview C-25
Subledger Accounting BI Publisher Reports C-26
Subledger Accounting Subject Areas C-29
Practice C-4 Overview: Running a Subledger Accounting BI Publisher Report C-30
Accounting Hub C-31
Accounting Hub Reports C-32
Summary C-36
xx
10
Configuring Oracle Intercompany

Copyright © 2018, Oracle and/or its affiliates. All rights reserved.
Objectives
After completing this lesson, you should be able to:

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

Oracle Financials Cloud: Enterprise Structures with General Ledger Implementation 10 - 2

Intercompany Overview
The Oracle Intercompany module consists of three areas of functionality:

• Intercompany Balancing: Supports accounting for business activity:
– Across different legal entities.
– Across different primary balancing segment values within the same legal entity.
– Across different second balancing segment values and across different third
balancing segment values.
• 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 Financials Cloud. Intercompany
functionality is also available in Oracle 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.

Payables Invoice Example
Original Transaction Lines:
Primary Balance Segment Account Intercompany Debit Credit
Segment
Vision Foods Berkeley Expense 500
Vision Foods Marin Expense 700
Vision Stockton Citrus Liability 1200
Intercompany Lines to balance the transaction:

Vision Stockton Citrus Intercompany Receivable Vision Foods Berkeley 500
Vision Foods Berkeley Intercompany Payables Vision Stockton Citrus 500

Vision Stockton Citrus Intercompany Receivable Vision Foods Marin 700
Vision Foods Marin Intercompany Payable Vision Stockton Citrus 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 segment values, 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.

Cross-Ledger Allocation Journals Example
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
The process adds intercompany clearing lines which include the intercompany values (the ending segment)
added to balance each journal. The intercompany allocation across the three ledgers can now be posted
successfully.

Intercompany Balancing: Features
• Balances up to three segments per chart of accounts.

• 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 rules 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
by balancing segment value.. 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 as one of its chart of accounts 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: Others > Setup and Maintenance > Financials > General Ledger > Specify Ledger Options
• Checking the Enable intercompany accounting 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. Note: If the primary balancing segment values are not
assigned to legal entities, then balancing occurs by primary balancing segment value and second
and third balancing segment values if enabled.

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, 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
Note: Intercompany rules defined by Transaction Type are not used for balancing.

Manage Intercompany Balancing Rules
Chart of Accounts

Navigate to: Others > Setup and Maintenance > Financials > Intercompany > 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

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

Balancing Rules > Primary Segment Rules tab
This screenshot displays the fields for the primary segment rules as you scroll across the page.

Manage Additional Intercompany Balancing and Clearing Options

Navigate to: Others > Setup and Maintenance > Financials > Intercompany > Manage Additional
Intercompany Balancing and Clearing Options
Set Additional Intercompany Balancing and Clearing Options if you have chosen to implement one or more
of the following features:
• Second or Third Balancing Segments
• 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 Japan Primary Ledger. In this screenshot, 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 second or third balancing segments.
It is possible to set up different accounts by source/category combination.

Key Decisions and Best Practices
Intercompany Balancing
Topic Decisions
What is the intercompany The intercompany segment is a segment of the chart of accounts
segment? structure that has the Intercompany Flexfield qualifier enabled.
You can implement an intercompany segment in your COA to track the
trading partner for each intercompany transaction.
What are the advantages To assist with reconciling intercompany transactions and help with
of having intercompany identifying elimination entries needed.
segment? If you use the intercompany segment, you can set up your rules to use a
single natural account value for the intercompany payable account, and
a single natural account value for the intercompany 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 a COA level rule, We recommend using a COA level rule that applies to the majority of the
or require lower-level transactions.
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
account. Refer to the 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
From : VisionUSA From : VisionEast
Legal 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 value Instead of sharing the same value set, it is recommended that you use a
set for Balancing segment different value set for primary balancing segment and intercompany
and Intercompany segment, where both value sets have the same values. If the primary
segment? balancing segment and intercompany segment share the same value set,
then when segment value security is enabled, it also affects the
intercompany segment. Securing a value set denies access to all values by
default. See example below.
Primary Second Natural Intercompany
balancing balancing account Segment
segment Chart
segment of accounts structure 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 more You would use the same values for the primary balancing segment
than one COA, and do for all charts of accounts in your enterprise for accurate identification
transactions span more than one of trading partners.
COA?
I am upgrading and my current No, you can still use all Intercompany features. However we strongly
chart of accounts does not have recommend an Intercompany segment for new implementations, due
an Intercompany Segment. Do I to the reasons discussed earlier.
need to add one?

Do I need to set up one rule for You do not need to set up rules at every level. Instead if you use an
each of the balancing rules, e.g. intercompany segment and your business practice allows for one
one for Primary Balancing intercompany receivable natural account and one intercompany
Segment Rule, Legal Entity Rule, payables natural account, you can set up one rule at the chart of
etc? accounts level.

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


Practice 10-2 Overview: Viewing Intercompany Balancing Rules and
Secondary and Clearing Company Balancing Options
This practice covers the following topics:
• 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.

Create Allocation Rules Setup Tasks

Navigate to: General 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, Cloud 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.

Intercompany Allocations Example
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.

T – Accounts: Journal 1
Vision USA with Canada Vision USA with Canada

3111-000-1301-2257 3111-000-1301-2258
129,000 11,000
Vision USA
129,000 11,000 3111-000-4111-0000
170,000
Vision USA with China Vision USA with China 170,000
3111-000-1301-1232 3111-000-1301-1234
12,000 18,000

12,000 18,000
These T-Accounts show the entries in the Vision USA ledger from intercompany transactions with China
and Canada.

Vision Canada Vision Canada

2257-000-6111-0000 2258-000-6111-0000
129,000 11,000
129,000 11,000
Vision Canada Vision Canada

2257-000-2101-3111 2258-000-2101-3111
129,000 11,000

129,000 11,000

Vision China Vision China

1232-000-6111-0000 1234-000-6111-0000
12,000 18,000
12,000 18,000
Vision China Vision China

1232-000-2106-3111 1234-000-2106-3111
12,000 18,000

12,000 18,000

2. Intercompany Transactions Created from Expense Allocation Lines: Provider Distributions
Provider Receiver Transaction Provider Provider Account Debit Credit

Distribution
Vision HQ Vision Ontario 1 1 3111-000-4111-0000 129,000
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.

2. Intercompany Transactions Created from Expense Allocation Lines: Receiver

Distributions
Provider Receiver Transaction Receiver Receiver Account Debit Credit
Distribution
Vision HQ Vision Ontario 1 1 2257-000-6111-0000 129,000
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 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.

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.
Note: Balancing evaluates COA, Ledger, Legal Entity and Primary Balancing Segment level rules before
evaluating source, category and transaction type in the rule.

Intercompany General Ledger Integration
Oracle Intercompany Oracle General Ledger
Transfer to GL GL Balances
Web UI
Open Interfaces
Drilldown
(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 Interfaces
Drilldown Record AP Invoice
(Import)
Drilldown
Drilldown Drilldown
Excel
(FDI) Dr Cr Dr Cr

Subledger Accounting Subledger Accounting Drilldown
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 Receivables and record them in Oracle
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 General Ledger as journal entries that are then posted.
– To Oracle Receivables where invoices are generated.

– To Oracle 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: Others > Setup and Maintenance > Financials > Intercompany > 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.

Transaction Types
• Define 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.
• Note:
- Provider: An organization, business, or individual which offers service to others in exchange
for payment.
- Receiver: An organization, business, or individual which receives products or services from
others in exchange for payment.

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: Others > Setup and Maintenance > Financials > Intercompany > 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

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 Receivables and
Oracle Payables.

Navigate to: Others > Setup and Maintenance > Tasks Panel > Search > 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 used for 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 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 and Supplier Assignments

Customer Supplier Association
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

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: Others > Setup and Maintenance > Tasks Panel > Search > 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 that are available to use in the account rules.

Navigate to: Others > Setup and Maintenance > Financials > Intercompany > 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.

Intercompany Transactions Approvals Example
• Receiver Org = Vision Foods

• Users with Access = A Brown, C Jones, D Smith
• Vision Foods Approval Group should contain A Brown, C Jones, and D Smith, so ALL
these users receive the notification that receiver distributions need to be entered.
• Once the receiver distribution is entered in the inbound screen, the transaction is
automatically 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 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.


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 and organizations, assigned to the same legal entity. Each
one payables business unit organization can have a different receivables and payables
assigned to a legal entity for business unit.
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 the Run option from the Menu and select 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.

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 report shows 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. You can
also run the report 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 10-3 Overview: Creating an Intercompany Batch

• Creating an intercompany batch.
• Reviewing the intercompany balancing rules.


Practice 10-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
• Intercompany Invoicing Flow: Doc ID 1584586.1

• 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
In this lesson, you should have learned how to:

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


11
Configuring Period Close Components

Objectives

• Discuss the Close Monitor.
• Open and close periods.
• Allocate balances.
• Manage revaluations.
• Run translations.
• Import journal entries.
• Reconcile balances.


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:
• Open an accounting period.
• Enter subledger transactions.
• Run the Create Accounting process and transfer the journals to the GL_Interface table.
• Import journals into the general ledger.
• Post your journal batches manually or automatically. Posting populates the GL Balance Cube and
the GL_Balances table
• Enter adjusting journal entries such as allocations and revaluations done in General Ledger
• Produce financial reports and perform online inquiries to review current account balances.
• Close the current accounting period.
• Open the next accounting period.

Close Monitor Overview
• Provides information on the period close status for a given accounting period across
multiple products for related ledgers in a hierarchical ledger set based display.
• Uses the hierarchical ledger set to mirror the consolidation relationships and roll ups of
entities across the enterprise.
• Summarizes period close status information for each ledger across multiple products
and for each consolidation node across multiple ledgers.
• Provides the contact information of the manager for a given node on the ledger set
hierarchy.
• Summarizes high level income statement results for each entity and aggregates this
financial information at each consolidation node.

• Provides views for a given ledger set, for a particular accounting period, and currency.
The period status information that is displayed is broken down by application module including General
Ledger, Payables, Receivables, Asset, Projects, and Costing. Some modules track their entities at a more
granular level, such as:
• Business units for Payables, Receivables, and Projects
• Asset Books for Assets
• Cost Organization Books for Costing

Close Monitor Explained

The Close Monitor indicates:

• The number of subunits by module for the ledgers.
• The fractional indicator, where applicable, of how many of the subunits are at closed status. For
example, in this graphic Receivables has 2 of 2 modules in the Close Pending status.
Secondary ledgers, journal level, or transaction level reporting currencies cannot be associated with
subledger business units for Payables, Receivables, and Projects. The ledger set displayed in the hierarchy:
• Members that are secondary ledgers, journal, or subledger level reporting currencies.
• The period status indicated in the Close Monitor for such subledger modules based on its related
primary ledger.
Asset books and cost organization books can be associated with all types of ledgers. Assets and Costing
modules period status for secondary ledger or reporting currencies is shown:
• For the books directly associated with them.
• Or derived from the books associated with their primary ledgers.

Setting Up the Close Monitor
The Close Monitor setup is comprised of:

• A predefined ledger set hierarchy definition
• An assigned a manager to each ledger set or ledger who is responsible for its financial
close
• A logo to represent the entity in the display.

The list of managers are defined in the Human Capital Management (HCM) module. The attributes defined
in HCM, such as the picture of the person and contact details, are shown in the Close Monitor.
• The members of the Close Monitor hierarchy must share a common chart of accounts and calendar.
• The financial data displayed in the Close Monitor is derived from the account group assigned to the
ledger set. The account group:
- Must include two line items whose accounts query the total revenues and total expenses of
the organization.
- Reflects a summarized income statement in the financial data tab of the Close Monitor.
• You can choose any of the ledger sets in the selector to indicate the top starting ledger set to display
in the Close Monitor.
• To have meaningful comparison and summation:
- Assign the appropriate primary, secondary, or reporting currency ledger to the ledger set.
- Assign ledgers to the ledger set that have a currency that matches the Close Monitor display
currency.
- Alternately, use translated balances (balance-level reporting currency) in the ledger set to
meet the common group currency requirement.

Navigating in the Close Monitor
Control Panel Icons:

• Across:
– Change the view.
– Provide different layouts.
– Close the Control Panel
• Down: Zoom to Fit, In, or Out.
Under the Close Status panel:
• Dots to navigate to:
– Close Status

– Manager
– Profit and Loss
• Show or Hide icon to see Ledger data.

Viewing in the Close Monitor
Select a ledger set, an accounting period, and currency as the view criteria.
• For example, change the currency displayed by:
– Working with a global ledger set.
– Shifting the focus to a lower level ledger set that is aggregating at the continental
level, such as North America, that uses a different group currency.
• The Close Monitor supports different zoom levels to enable you to:
– Accommodate viewing a larger ledger set hierarchy in its entirety.
– Show detail information for each node which can vary, decreasing and simplifying in
content as you zoom out further to show more nodes in a single view.
– Hover over the more summarized node and expand out to a particular node.

– Leave the zoom level at 100% and move around the display to other ledger sets.
• A view control panel that can be exposed on demand allows you to adjust the zoom level, pan
across the hierarchy, flip the display tabs, and switch the hierarchy display format
• If matching financial data for a ledger in the selected currency is not available, a message is
displayed stating that the requested financial data is not available.

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:
• Never Opened
• Future Enterable
• Open
• Closed
• 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: Others > Setup and Maintenance > Tasks Panel > Search > 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 Financials Cloud.

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 by
Transactions Monitor 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.

Close Status Section

Navigate to: General Accounting > Period Close

The Close Status 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 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 transferred and Journals and Intercompany
posted to the General Ledger. Transactions Infolets
Tie out Payables and Receivables subledger balances to the AP and AR Reconciliation Infolets
General Ledger.
All intercompany transactions for the period have been Intercompany Transactions
transferred, and both sender and receiver have accounted Infolets
for their side of the transaction.
Outstanding journal entries for the period are resolved before Journals Infolet
closing the period.
Translated balances are current before running final reports Translation Status Portlet

on translated balances.
Subledger periods are closed before proceeding to close the Close Status Monitor, Open
General Ledger period. Subledger Infolet
You can also evaluate reported financial performance to see if there are required adjustments by using the
Revenue and Expense infolets as the referenced tool, along with standard and FR reports.

Practice 11-1 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 their 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 Cloud
Applications tasks and other enterprise tasks outside Oracle Cloud 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.

Allocation Concepts
Use the following components during allocation rule design:

• Source: Cost or revenue pool which is allocated.
• Basis: Formula to distribute the amounts.
• Allocation Range: Spread of values to which to allocate the data.
• 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: Determines the percentage to be applied to each allocated member. The basis determines
the percentage to be applied to each allocated member. An account such as head count or other
statistical unit can be use in the calculation of the basis.
• Allocation Range: Can be a group of members such as cost center represented by a parent.
• Target: Can be a group of accounts represented by a parent and receives the results of the
allocation.
• Offset: Can be a group of accounts. The offset can be the same account as the source to zero out
the source or to another account to leave the source intact.
• 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.
• Runtime Prompt: A user-defined element used at the time of the rule definition and makes the rule
highly dynamic and reusable. Examples of Runtime 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 Allocation 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, which 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 the 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 the
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 definitions? Validate the rules and rule sets during definition time and fix
the errors.
How do I automate the allocation Use the enterprise scheduler to schedule the generation of
generation process? allocation definition at the optimal time.
Select the 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 Manager to For fully reciprocating eliminations, use a (-1) multiplier
generate elimination entries for against the source elimination balance to compute the target

consolidations? elimination balance.
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 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 11-2 Overview: Creating and Generating an Allocation Rule

• 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 and Reporting Currencies 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.
Reporting Currencies:
• Representations of a primary or secondary ledger in another currency.
• Share the same chart of accounts, accounting calendar, and accounting method as their related
ledger.
• Used for online inquires, reporting and consolidation.

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 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. For the equity translation method, this may also require revaluing accounts
also in the case where there are activities denominated in the reporting currency in the case of non-

monetary accounts.

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 11-3 Overview: Creating a Revaluation

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


Translation Process

In this example, a Canadian company has a Mexican subsidiary. The translation process is run on the
subsidiary ledger to convert balances from the Mexican peso (MXP) to the Canadian dollar (CAD). The
figure shows an example of the translation.
• The period end rate of 0.75 translates 100,000 MXP in assets to 75,000 CAD, and translates 60,000
MXP in liabilities to 45,000 CAD.
• The historical rate of 0.70 translates 40,000 MXP in Owner's Equity to 28,000 CAD.
As a result, an offset of 2,000 CAD in the translation currency, created by the different rates, is recorded in
the Cumulative Translation Adjustment (CTA) account.
Running Translation
• Has these prerequisites:
- Running revaluations.
- Defining period end, average, and historical rates as needed.
• 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 (CTA) accounts. Note: For translation, the CTA is specifically relevant. Retained
Earnings multiple balancing segment support is also relevant outside of the translation context in
other features such as posting and opening the first period of a fiscal year.
• 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
Equity Translation:
• Restates the general ledger balances from the ledger currency to a reporting currency.
• Used if investing overseas to convert net equity.
Remeasurement:
• Restates 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 generally use period to average rate type for income statement items and period end
rate type balance sheet items. Historical rates or amounts can be assigned to specific accounts for
their translation.

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.
• 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 General Ledger.
• Initiate the Create Accounting process from Oracle subledgers, such as Oracle Payables or Oracle
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.
• Use the Journal Import file-based data import (FBDI) to upload journal entry data from external
sources into Oracle General Ledger.

Journal Import Verification Process

Journal Import Process

• Validates all of your data, before it creates journal entries in Oracle 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 applications enables you to quickly reconcile your General Ledger to the subledgers,
for example Receivables, Payables, Cash Management, and Intercompany.
• 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 Requirement Solution

Subledger to General Ledger • Receivables to Ledger Reconciliation and Payables to Ledger
reconciliation reports to match Reconciliation Reports:
Accounts Payable and Accounts • Automatically match subledger transactions to accounting
Receivable transaction entries to entries to accelerate the reconciliation and close processes.
General Ledger accounting entries. • Identify exceptions to guide your reconciliation efforts.
Intercompany reconciliation reports • Prepare Intercompany Reconciliation Reporting Information
to assist you with reconciling your process:
intercompany receivables and • Is run from within the reconciliation work area.
intercompany payables accounts, • Displays the details in a series of pages with drill down
and to identify any differences. capability.

Drilldown to originating Direct drilldown to supporting journals and transactions is
transactions. provided for visibility to source information.
Reconciling high data volume. Analyze report output in a spreadsheet 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 Cloud Transactional Business Intelligence Administrator's Guide for more detailed setup
steps.

Clearing Accounts Reconciliation
NEW
• Enable ledger and natural account segment
values for clearing account reconciliation.
• Define reconciliation types that represent
reconcilable clearing accounts.
• Enter journal lines with reconciliation
references.
• Perform automatic or manual
reconciliations.
• Perform reverse reconciliation to correct a
previous reconciliation.

• Run reconciliation reports and perform
inquiries.
Clearing accounts reconciliation offers sophisticated automatic and manual methods to group, match, and
reconcile related “in” and “out” journal lines.
• Define reconciliation types that represent reconcilable clearing accounts (for example, asset
clearing, accounts payable accrual, unbilled receivables) and their associated reconciliation rules, in
one central setup location.
• Enter journal lines with reconciliation references to automatically reconcile them with minimal user
intervention and enhanced productivity as “Post Journals”.
• Use tolerances when performing manual reconciliation, to further enhance the success rate of
journal lines getting reconciled.
• Correct previous reconciliations by subsequently reversing them.
• Run reconciliation reports and perform inquiries to retrieve and analyze reconciled and unreconciled
journal lines.

Steps to Enable Clearing Accounts Reconciliation
• Enable both the ledger and natural account segment values.

– Select the Enable Clearing Accounts Reconciliation option
– Set the Reconcile attribute of the natural account segment values to YES.
• Run the Inherit Segment Value Attributes process.
• View and manage existing reconciliation types.
• Click the Add (+) icon to create reconciliation types and their associated rules.
• Tip: To easily distinguish reconciliation types on processing pages, add a suffix with the
name of the chart of accounts or ledger to reconciliation type names

Steps to enable clearing accounts reconciliation:

• Both the ledger and natural account segment values that are subjected to reconciliation, must be
enabled for clearing accounts reconciliation.
- Select the Enable Reconciliation option in the Reconciliation section on the Specify Ledger
Options page.
- Set the Reconcile attribute of the natural account segment values, that are subjected to
reconciliation, to Yes on the Manage Values page.
• Run the Inherit Segment value Attributes process to subsequently update existing account
combinations with the changes to the Reconcile attribute on the natural account segment values.
When the preceding steps have been completed, navigate to: Others > Setup and Maintenance > Financials
> General Ledger > Manage Clearing Accounts Reconciliation.
• View and manage existing reconciliation types.
• Click the Add (+) icon to create reconciliation types and their associated rules, as required.

Other Considerations
• Upload and import clearing account journal lines containing reconciliation references into
GL using spreadsheet-based methods (file-based data import, Oracle ADF Desktop
Integration).
• Configure subledger accounting rules to automatically populate reconciliation references
in subledger journal lines.
• Note: The ledger as well as the natural account segment values must be enabled for
reconciliation before journal import process can successfully import reconciliation
reference information on clearing account journal lines.
• Run the Enable Journal Lines for Clearing Accounts Reconciliation process to make
posted historical journals eligible for clearing accounts reconciliation.

Note
• Users must be assigned the Manage Clearing Accounts Reconciliation Setup privilege to set up and
manage reconciliation types and their associated reconciliation rules.
• The predefined job roles of Financial Applications Administrator, General Accounting Manager, and
General Accountant have this privilege assigned by default, either through the General Accounting
Functional Administration Duty or the Period Close Management Duty.
• Reconcile Clearing Accounts and Run Clearing Accounts Reconciliation Reports privileges provide
access to reconciliation processing pages and reconciliation reports respectively.
• The predefined job roles of General Accounting Manager and General Accountant have these
privileges assigned by default.

Performing Clearing Accounts Reconciliation
Reconciliation Process Overview

Run automatic reconciliation and Clearing Account Reconciliation Report helps in reviewing the
review the execution report. results of automatic reconciliation.
Review reconciliation results. Drill down to the journals from the Manage Journals page to view
the reconciliation details.
Reverse reconciliations. Incorrect reconciliations can be corrected by reversing the

reconciliation.
Perform a manual reconciliation. Navigate to General Accounting > Journals > Clearing Accounts

Reconciliation > Reconcile Clearing Accounts Manually.
Run reconciliation reports. • Reconciled Transactions report
• Unreconciled Transactions report
Automatic Reconciliation
• Perform automatic reconciliation to quickly reconcile a majority of the “in” and “out” related journals.
Navigate to General Accounting > Journals > Clearing Accounts Reconciliation > Reconcile Clearing
Accounts Automatically or submit the process Reconcile Clearing Accounts Automatically from
scheduled processes. The automatic reconciliation execution report provides a summary information
of the total number of journal lines that were selected for processing, reconciled successfully and
remaining unreconciled.
Reversing Reconciliations
• Incorrect reconciliations can be corrected by reversing reconciliation. Navigate to General
Accounting > Journals > Clearing Accounts Reconciliation > Reverse Reconciliation to retrieve one
or more reconciliation groups and the underlying reconciled clearing account journal lines.
• Select the check box to the left of the reconciliation group and click Reverse Reconciliation to
complete the reverse reconciliation process.
• The reversed reconciled journals will go back to the overall pool of unreconciled journal lines.
• These journals can be reconciled again using the automatic or manual reconciliation process.
Manual Reconciliations
• Navigate to General Accounting > Journals > Clearing Accounts Reconciliation > Reconcile Clearing
Accounts. Select journals by checking the boxes displayed on the left of the journal line records.
Click Reconcile to complete the manual reconciliation.
• Unlike automatic reconciliation, manual reconciliation doesn’t mandate the presence of reconciliation
reference information in the related journal lines.

Reconciliation Reports
• Reconciled Transactions Report – This report provides details of clearing account journal lines that
have been successfully reconciled by both automatic and manual reconciliation processes.
• Unreconciled Transactions Report – This report lists all unreconciled clearing account journal lines
that have been rejected by either automatic or manual reconciliation processes, as well as those
lines that have not yet been subjected to reconciliation. The sum of all the unreconciled lines should
typically be equal to the closing balance of clearing account.
Note
• The reversed reconciled journals will go back to the overall pool of unreconciled journal lines.
• These journals can be reconciled again using the automatic or manual reconciliation process.
• Before reversing clearing account journals, first perform a reverse reconciliation on the already
reconciled journal lines. Use the Reversible Detail column on the Manage Journals page to
understand why a clearing account journal cannot be reversed.

Practice 11-4 Overview: Clearing Accounts Reconciliation

• Configurations for Clearing Accounts Reconciliation.
• Automatic Reconciliation.


Payables Tax Reconciliation with General Ledger Report
• Reconcile the Payables tax transactions with the tax account balances in General
Ledger.
• Create the report 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

• Discuss the Close Monitor.
• Open and close periods.
• Allocate balances.
• Manage revaluations.
• Run translations.
• Import journal entries.
• Reconcile balances.


12
Configuring Financial Reporting

Objectives

• Describe the features of the 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.
• Discuss Oracle Transactional BI reports.
• Understand BI Publisher reports.


Financial Reporting Center Overview
Financial Reporting Center is intended to be the primary user interface for financials end
users to access all seven report types.

You can access reports using various methods. However, the Financial Reporting Center gives access to
every type of report and is intended to be the primary user interface for financials end users and is tablet
and smartphone friendly.
Financial Reports are read from Shared > Custom > Financials and My Folders. All other report types can
be saved anywhere in the BI Catalog, however, any custom content should be in the Shared > Custom
folder. It is also possible to create sub-folders within the Shared > Custom > folder.
The seven types of reports that can be run from the Financial Reporting Center and other reporting
interfaces are:
• Financial Reports: Reports built off the Oracle Financial Reporting Studio using data in the Oracle
General Ledger Balances Cube. For example, company income statements and balance sheets.
These reports are mainly run by users in General Ledger.
• Account Groups and Sunburst: Used to monitor key accounts in General Ledger. When a user
creates an account group it becomes visible in the Financial Reporting Center with the Sunburst
visualization tool. The Sunburst visualization tool enables you to interact with your account balances
across various business dimensions in order to view balances from different perspectives. Account
groups are only used in General Ledger.
• Smart View Reports: A multi-dimensional pivot analysis tool combined with full Microsoft Office
functionality as an add-in. Smart View enables you to interactively analyze your balances and define
reports using a familiar spreadsheet environment. These queries are mainly for users in General
Ledger. One user can upload a query using Workspace and then from Financial Reporting Center
another user can download the query to their local drive for use.

• Oracle Transactional BI Analyses: These analyses and reports are built off of transactional tables
using Subject Areas. These reports can be run by users in General Ledger, Payables, Receivables,
Cash Management, Intercompany, and so on.
• Oracle Transactional BI Dashboards: Dashboards put all the information, functions and actions that
a business user needs to do their job in one place. Dashboards are built off Oracle Transactional BI
objects like analyses and reports. These reports can be run by users in General Ledger, Payables,
Receivables, Cash Management, Intercompany, and so on.
• Business Intelligence Publisher Reports: Most of these reports are predefined and must first be
submitted and resubmitted to see the latest data by the Oracle Enterprise Scheduler System (ESS)
through the Scheduled Processes navigation. These reports can be run by 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 multitouch
information-driven applications with rich interaction, rich visualization, and rich media, for mobile
devices such as iPhone, iPad, Android phone, tablet, and more. These reports can be run by users
in General Ledger, Payables, Receivables, Cash Management, Intercompany, and so on.

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

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

Financial Reporting Batches, and Batch Scheduler

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

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

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


Viewing Financial Reports from the Financial Reporting Center
Financial Reports are:

• Balance Sheets
• Income Statements
• Cash Flow Statements

Navigate to: Financial Reporting Center > Search for Balance Sheet > Open > OK
Financials users use the Financial Reporting 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 accessed 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

• Multiple output options including PDF, HTML, and Excel.
• Live reports are interactive and the data can be refreshed dynamically.
• Published snapshot reports have static data.
• Ability to expand parent values to view the next level of the hierarchy within the reports.
• Drill down to underlying journals and subledger transactions.

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

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


Oracle General Ledger Balances Cube: Overview

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

Dimension Values in Reporting
You can derive different amounts to meet financial reporting requirements by using various
combinations of dimension members.
Dimensions are used in the following reporting tools and features:
• Financial Reporting 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 is either:
• Selected as an initial prompt.
• Selected while viewing the results.

GL Balances Cube: Dimensions
Dimension Description
Accounting Period Based upon the calendar of the ledger or ledger
set. Report on years, quarters, or periods. If the ledger
tracks average daily balances, this includes an option to
select date.
Ledger or Ledger Set Used to select a ledger for the reporting. Multiple
ledgers may be in the same cube if they share a
common chart of accounts.
Chart of Accounts Segments Each segment from the charts of accounts becomes a
separate dimension organized by hierarchy. A default

hierarchy is provided that includes all segment values.
• The GL Balances Cube consists of a set of defining business entities called dimensions. Dimensions
are used when creating a report and in many cases when running a financial report.
• The table details in this slide and the next show the dimensions that are available for creating
financial reports using multidimensional cubes.
• Dimensions are seeded and new ones cannot be added.

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

Currency Used to select the desired currency for the balances.
Currency Type Used to select the currency type of the balances. Available
options are entered, converted, or total.

Default Values
Many dimensions have default member values that can be used for a report or analysis.
However, the following dimensions require a selected member value:
• AccountingPeriod
• Ledger
• Scenario
• Currency

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

Dimension Values and Defaults
Dimension Possible Default Value Additional Information
Values
Accounting • Years Must select a Without the Accounting Period, the financial
Period • Quarters value reports, Smart View queries, and Account
• Monthly Inspector display #MISSING.
• Weekly
• Daily
Ledger • Ledgers Must select a Without a Ledger or Ledger Set, the financial
• Ledger Sets value reports, Smart View queries, and Account
Inspector display #MISSING.
Chart of Each segment has There is a separate dimension for each

accounts a default account segment of the chart of accounts used by the
dimensions hierarchy with cube.
detail values. Hierarchies published to the GL Balances
Cube from the Publish Account Hierarchies
process are included.

Dimension Possible Default Additional Information

Values Value
Scenario • Actual Must select a Additional scenario values of Budget, Forecast Q1,
• Budget value and Forecast Q2 may be added to the Accounting
• Forecast Scenario value set. These additional values are
published to every cube.
Amount Type • Base Amount Type, Base is necessary because this is the value used to
• PTD which is the store all balances posted at the lowest level.
• QTD equivalent of PTD, QTD, and YTD are calculated values.
• YTD Base

Currency All ISO Must select a Without a currency, the financial reports, Smart
currencies value View queries, or allocation display #MISSING.
Note: Do now select Allocated or Total for Allocated as the value for Scenario.

Dimension Possible Values Default Value Additional

Information
Balance • Balance Amount Balance Amount,
Amount • Beginning Balance Dr which is
• Beginning Balance Cr equivalent to the
• Beginning Balance (net) Ending Balance
• Period Activity Dr (net)
• Period Activity Cr
• Period Activity (net)
• Ending Balance Dr
• Ending Balance Cr
• Ending Balance (net)

Currency Type • Total Currency Type,
• Entered which is the
• Converted From equivalent of
Total

Smart View Overview
With Smart View you can create:

• Ad Hoc Analyses.
• Financial reports using the Query Designer.

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

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

• Retrieve and analyze data by selecting members.
• Perform a variety of operations, including formatting and designing your reports.
• Use functions.

A Smart View analysis allows you to:

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

Query Designer
Create financial reports such as Income Statements and Balance Sheets for internal use.
Use Smart View functionality with Excel spreadsheets to:
• Retrieve and analyze data by selecting members.
• Perform a variety of operations, including formatting, graphing, and drilling through.

The Smart View Query Designer is a tool that is used to create basic financial reports such as Income
Statements and Balance Sheets. The reports designed in Smart View are recommended to only be used
internally. Boardroom ready financial reports should be defined through the Financial Reporting 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 a 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 Cloud 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.
Note: Best practice is to always turn suppression on in financial reports. This should be done at the
Database Connection Server. You can verify this by doing the following: (highlight grid > Menu > Task >
Data Query Optimization Settings). The normal best practice for most reports is to turn suppression on for
the entire grid, and then turn it off for certain columns and rows that must always display.

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.
Print Preview Displays the active report in the 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 view (POV) values, or dimension members.
Grid A report object 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 increase
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 grid. A row can contain text, data, or derived
data from a calculation. You can format individual rows in grids.
Column A vertical display of information in a grid. A column can contain text, data, or derived
data from a calculation. You can format individual columns in grids.
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 log in and connect to a GL
balances cube. There are 4 basic components on a grid:
• Point of View Dimensions: You select which Point of View (POV) dimension to include on the rows,
columns, and pages. All the GL balances cube dimensions are always in a POV. A POV is either at
the grid or user level. This chapter covers the difference between grid POV and user POV later on.
• Rows: For most financial reports rows usually are defined with account numbers, so you could select
the Account dimension where an account number would be the member. You would then select
which account numbers go on each row. However, other dimensions can be selected.
• Columns: For most financial reports columns are usually defined with accounting periods, so you
would select the Accounting Period dimension. However, other dimensions can be selected.
• Pages: A common selection for page dimension is the balancing segment or company. If your
company has more than company, the report results with a page per company.
With grids you can also:
• Include more than one grid on the report palette. One report can then extract data from more than
one data source.
• Use an existing grid to reuse the preformatted design.
• Select the members of the dimensions.
• Use formulas, functions and text to define the grid content.

Practice 12-2 Overview: 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 list, you can choose:

Formula Formula Formula Formula
Abs() Eval() Random() VariancePercent()
Average() IfThen() Rank()
AverageA() Mod() Round()
Cell[row.col] Max() Row()
Column[] Min() Sort()
Count() PercentOFTotal() Sum()

CountA() Pi() Truncate()
Difference() Product() Variance()
For example, use the Sum() formula to calculate total expenses. The syntax for the formula includes the row
numbers to be summed up.
If the rows are contiguous, the following syntax is allowed: Sum([3:5]). The rows 3, 4 and 5 are included in
the calculation.
If the rows are not contiguous, for example, Subtotals or you need to sum up Total Revenue and Total
Expenses, then the following syntax would be used: Sum([1],[6]).
Note: For more details on the available formulas, see the Oracle Hyperion Financial Reporting Studio
User's Guide.

Reporting Studio: 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.

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


User and Grid Point of View Dimensions

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

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.

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


Property Sheet
Use the Property Sheet to set various options for a report component:
• Grid
• Page
• Heading Row
• Chart

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

Property Sheet Component Objects and Features
Object Features
Grid General: Database Connection; Headings for Member Labels; Autosizing;
Drill Through; Suppression: Suppress If Zero, If Missing, and If Error; Text
Options for Zero Values, No Data and Error.
Page Member Labels: Member Name, Alias: Default or Both, Heading Height, Page
Printing Positioning.
Heading Row Headings Member labels: Member Name, Alias: Default or Both, Allow
Expansion, Auto Calculation.
Chart A report object that displays data from a specified grid. Charts are graphical

representations of the data in a grid.
The above table is just a small sampling of the available objects and associated features. More information
can be found in the Oracle Hyperion Financial Reporting 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.

Reporting Studio: Setting Properties
• Setting the Grid Properties.
• Setting the Page Properties.
• Setting the Heading Row Properties.


Text Box Objects
Text box objects allow you to:

• Enter text or text functions.
• Move, resize, or reposition the text box.
• Set the border, shading, and positioning.
• Store them in the repository.

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

Image Objects
Adding Images:
• Insert images into the header, footer, and body of a report.
• Support for multiple graphic formats.

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

Reporting Studio: 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 12-8 Overview: Reviewing a Financial 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
• Monitor performance with user configurable interactive dashboards based on user-

defined Oracle Transactional BI reports.
• Drill from dashboards to detailed reports.

Navigate to: Welcome Springboard > Custom Infolets Dot.

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

Account Groups: Overview
• Account groups are easy-to-use reporting components that save queries on account
balances requiring regular monitoring.
• The output from your rules can be displayed in:
– The Financial Reporting Center
– The Account Monitor
– General Accounting Infolets

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

Viewing Account Groups in the General Accounting Infolets
Automatically Included with Setup

Infolet
Available Shipped Job Roles Needed
Financial Analyst
Revenues Yes General Accountant Yes
General Accounting Manager
Financial Analyst
Expenses Yes General Accountant Yes

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

Defining Account Groups: Header Region

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

• Set as Default: Since there can be more than one account group, one account group must be the
default for each Display In type. The financial reporting center and the account monitor can view
more than one account group. The infolets can only view the one default account group.
• Dynamically derive ledger: A account group can only be based on one chart of accounts. The best
practice is to have the same chart of accounts across ledgers, and then you can potentially use the
same account group across your ledgers. If you do not want to use an account for all ledgers, add
the specific ledger to each account group row. If you check this option when setting up the account
group:
- The application selects the ledger for you based on your selected data access set and
ledger.
- The ledger column in the account group row is not displayed.
• Time Option: To specify the target to evaluate the current performance against. The choices are
Accounting Period, Quarter or Year.
• Comparison Option: Determines the balance type the account group uses. The comparison options

are based on the Time Option chosen. You can select a budget, forecast, or prior performance.
Some of the choices are Budget PTD or QTD or YTD, Previous Period, Prior Year PTD, QTD or
YTD.
• Scenario: If the Budget Comparison Option is chosen, you must provide the budget scenario. The
choices are budget or forecast.
• Access:
- Private: Only the user that created the account group can access the account group in
infolets, the financial reporting center, and the account monitor.
- Public: This allows any user with proper security privileges to view the account group in
infolets, the financial reporting center, and the account monitor. Note: Only one infolet
account group can be public. If another user creates a new public account group it replaces
the first one created. Also, if a public account group exists and a user creates their own
default private infolet account group, their new private account group infolet overrides the
Public infolet account group just for that user.
- Shared: Allows the creator of the account group to select which users access. After choosing
the Shared Access, navigate to View > Manage to add the users to the account group.

Defining Account Groups: Accounts Region

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

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


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

highest level and comprehensive
revenue and operating expenses
accounts.
• Optionally, assign the expanded
account type of Expenses - Top Cost
of Sales Parent Account if this is
applicable.

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

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

Entered Currency Income Statement
• The process also generates three Account Groups.

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

Generate Financial Reports and Account Groups Process
You can submit the process at any time to automatically create Financial Reporting reports
and Account Groups.
• Pick the specific tree and tree version of the parent account that you wish to base the
generated reports on.

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

Tips And Considerations
• When specifying the top parent accounts to submit the Generate Financial Reports and Account
Groups process, you can pick a specific tree and tree version for each parent account.
• All three parent account values can be from different trees and tree versions, although ideally, you
would choose a common tree and tree version for all of them so that the hierarchy basis of all the
rows in the report is consistent.
• The Generate Financial Reports and Account Groups process creates an initial set of Financial
Reporting reports for each ledger included in the request submission.
• To prevent the unchecked proliferation of such Financial Reporting reports, unless the original
reports created were renamed or deleted, a resubmission of the report generation process will not
generate new Financial Reporting reports for the ledgers.
• In contrast, for Account Groups, a new set is generated for the balances cube with each submission
of the report generation process.
• The Revenues and Expenses Account Groups created by the report generation program are

automatically set as the defaults for your Revenues and Expenses infolets in the General Accounting
Home Page if there is no existing Account Group already associated as their defaults.
• The Close Monitor Summary Income Statement, can be assigned to your ledger sets when you
complete the Close Monitor setup.
Role Information
You must have one of the following roles to submit the Generate Financial Reports and Account Groups
process:
• Financial Analyst
• General Accountant
• Financial Application Administrator
• Application Implementation Consultant
You must have one of the following roles to work directly with the account groups and Financial Reporting
reports created:
• Financial Analyst, General Accountant

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

• Modify to satisfy a different reporting requirement.

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

Viewing Account Groups from the Financial Reporting Center
Account Group results can be viewed:

• As a table.
• In the Sunburst tool.

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

Sunburst Tool
The Sunburst visualization tool allows you to interact with your account balances across
various business dimensions in order to view balances from different perspectives.

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

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

• Move Ring Toward Center
• Move Ring Away from Center
• Keep Only
• Remove Only
• Zoom In
• Zoom Out

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

Sunburst Options
Use the options on the right to further analyze

the account group data.
• Account Group selection drop-down list
• Accounting Period drop-down list
• Segment drop-down list
• Move and position arrows
• Colors selection boxes and thresholds
• Other Thresholds
• Reset

• The color of the nodes represents a comparison with the previous period or budget. By default:
- Green implies increased revenue or decreased costs.
- Red implies decreased revenue or increased costs.
- Yellow represents little or no change.
• The colors and color thresholds can be changed using controls in the right hand panel.
• Contributions that are small relative to the total revenue and that result in very narrow nodes are
grouped into the Other node.
• The Other threshold, by default 2% of the circumference of the Sunburst, can be changed using
controls in the right hand panel.

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


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


Oracle Transactional Business Intelligence Overview

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

Financial Reporting Center and Oracle Transactional BI
From the Financial Reporting Center, you can access:

• Analyses
• Reports
• Dashboards


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

through print all of your highly formatted documents, such as:
• Operational reports
• Electronic funds transfer documents
• Government PDF forms
• Checks

• A scalable solution for delivering high-fidelity, pixel-perfect reports in multiple formats, for example,
for tax auditing and fulfilling country-specific statutory requirements.
• Used to generate printable output that presents specific information from a predetermined template,
for example, for invoices, dunning letters, and other external-facing documents.
• Used for generating high-volume operational reports and production runs.

Oracle Business Intelligence Publisher: Overview

• Oracle BI Publisher provides many predefined or seeded reports for Oracle Cloud Financials.
Predefined BI Publisher reports for Oracle Financials Cloud are set up to be submitted as scheduled
processes through the Enterprise Scheduler System (ESS) in Oracle Cloud Applications. The Open
link, therefore, is not available by default for these reports in the BI Catalog.
• Because it supports diverse document requirements with flexible customization capabilities,
developers can use layout editors to edit exiting layouts or create new layouts.
• BI Publisher can only use a layout to produce results. A layout determines the details, the placement
of data, and the look and feel of the output results.
• One BI Publisher report can support more than one layout allowing an end-user to obtain different
results as needed for the one or multiple data sources. Layouts generate high fidelity, pixel-perfect
reports to PDF, RTF, Microsoft Excel, Microsoft PowerPoint, and static HTML.
• Also, at the time of submission, an end-user can choose to have the report produce multiple outputs
using different layouts at the same time. In other words, one submission can produce the same
report in PDF and another in HTML at the same time. Or one submission can produce one report
using layout1 and another using layout2 at the same time.
• Because BI Publisher uses XML technology, the report output delivery supports multiple destination
types, including printers, faxes, e-mail, and e-commerce.

Financial Reporting Center and Oracle BI Publisher
Easily access reports initially run from Scheduled Processes.

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

Summary

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


13
General Ledger Options

Objectives

• Manage suspense accounts.
• Manage statistical units of measure.
• Manage journal sources and categories.
• Manage document and journal sequencing.
• Manage AutoPost and AutoReverse criteria sets.
• Manage Accounting Automation.
• Manage general ledger profile options.

• Manage processing schedules.

Manage Suspense Accounts
Use suspense accounts to post balancing amounts for out of balance journal entries.
The out of balance amount for the journal entry is automatically placed in the suspense
account, enabling you to post the transaction.
To use suspense accounts:
• Enable the suspense account at the ledger level in accounting configuration.
• Specify a suspense account.

If you define a suspense account for your ledger, posting automatically creates suspense journal lines for
unbalanced journals as shown in the example above.
Note: Do not assign a suspense account if you want to require balanced journal entries. Using suspense
accounts generally increases the time it takes to reconcile general ledger balances to source system totals.

Manage Suspense Accounts
Define additional suspense accounts, by source and category, to further segregate your out
of balance postings.
• Additional suspense accounts must be associated with a source and category.
• Multiple combinations of source and category can be assigned the same suspense
account.
• Journal posting automatically creates a suspense account for each balancing segment
value.
• Select Other for the journal source and journal category to enable suspense posting for
all journal entries.

Suspense accounts are also used by the Create Accounting process as a fall back for invalid accounts.
See the Manage Account Rules in the Accounting Transformation Configuration lesson for additional
information.

Practice 13-1 Overview: Creating a Suspense Account
This practice covers creating a suspense account.


Manage Statistical Units of Measure
Associate statistical amounts with monetary amounts by using statistical units of measure.
This enables you to enter both monetary and statistical amounts in a single journal entry
line.
Identify the account segments you want to associate with a statistical unit, such as:
• Payroll account and hours worked.
• Building maintenance account and square feet.


Practice 13-2 Overview: Creating a Statistical Unit of Measure
This practice covers creating a statistical unit to record statistical amounts.


Manage Journal Sources and Categories
• Journal Sources: Indicate where your journal entries originate.

• Journal Categories: Help you differentiate journal entries by purpose or type, such as
accrual, payments, or receipts.


Journal Sources
• Define your own journal sources for non-Oracle feeder systems.

• Specify whether to import detail reference information for summary journals imported
from your Oracle subledger applications.
• Required if you want to be able to drill down to the original subledger transaction from
balances in general ledger.
• If you have journal approval enabled for your ledger, use journal sources to enforce
management approval of journals before they are posted.
• If you are using average balance processing, select an effective date rule for your
journal source.

With journal sources, you can:

• Define intercompany and suspense accounts for specific sources.
• Run the AutoPost program for specific sources.
• Import journals by source.
• Freeze journals imported from subledgers to prevent users from making changes to any journals that
have been transferred to general ledger from that source. This ensures that transactions from your
subledger systems reconcile with those posted in general ledger.
• Report on journals by source using the Journals Day Book and General Journals reports.

Journal Categories
• When you create journal entries, you must accept the default or specify a category.
• With journal categories, you can:
– Define intercompany and suspense accounts for specific categories.
– Use document sequences to sequentially number journals by category.
– Define journal categories for accruals and estimates. Use these categories when you
define criteria for AutoReverse and AutoPost.
– Report on journal categories that appear in standard reports, such as the Journals
Day Book and General Journals report.
– Run reports by category, by source, or by category and source.

For example, for month end close, you might run a report listing all journals that were created for the period
with a category of accruals. This way you can review the accrual entries created before finalizing your close.

Practice 13-3 Overview: Creating a Special Journal Source and
Category
• Creating a special journal source to indicate the source of the journal.
• Creating a special category to classify your journal entries.


Sequencing Options
Sequencing simplifies the cumbersome task of tracing your journal entries for reporting and
auditing purposes.
• Use Document Sequences to:
– Assign unique numbers to your journal entries when they get created.
– Meet business and legal requirements in some countries.
• Use Accounting Sequences to:
– Assign gapless, unique numbers to your journal entries when posted.
– Provide gapless sequence numbers for posted journal entries in chronological posting
order.


Sequencing Options
• Use Reporting Sequences to:

– Assign gapless, unique numbers to your journal entries upon period close.
– Satisfy legal requirements by fiscal authorities that verify the completeness of a
company’s accounting records.
– Provide gapless sequence numbers for posted journal entries in logical order.
• Use one, two, or all these types of sequencing at the same time to meet different needs.


Manage Document Sequences
Configure using a variety of configurable attributes including:

• Category of the document.
• Application or module.
• Type: Automatic, gapless, or manual.
• Effective start and end dates.
• Applicable ledger.

• Uniquely number your journal entries when created, enabling you to account for every journal entry.
• After defining document sequences, you must assign a specific sequence to an application and
category.

Document Sequences: Types
Type What does it do? When do you use it?

Manual You must assign a unique number to each You want flexibility in assigning a
journal when it is created. Sequential ordering sequence number that is
and completeness are not enforced. meaningful.
Automatic The system sequentially assigns a unique You want sequential ordering by the
number for each journal, but ensures that the date and time of the journal
journal was successfully created before creation.
assigning the number.
Gapless The system sequentially assigns a unique You want sequential tagging by
number to each journal as it is successfully journal creation order and do not
created. want to lose sequence numbers

due to incomplete or failed journal
creation.

Manage Accounting and Reporting Sequences
Consist of:
• Gapless sequential numbering
for your general ledger and
subledger journal entries.
• One or more non-overlapping,
date-effective versions.
• Versions that determine the
initial number assigned to the
journal entries using sequence
for the specified date range.


Configurable Sequencing Assignment Options

Variety of configurable sequencing assignment options used to meet your specific needs.
• Gapless sequential numbering for your general ledger and subledger journal entries.
• A sequence consists of one or more non-overlapping date-effective versions.
• The versions determine the initial number assigned to the journal entries using this sequence for the
specified date range.

Accounting and Reporting Sequences Setup
• How do you restart a sequence? If you need to restart numbering the journal entries
periodically:
– Define additional versions for your sequence.
– Assign them non-overlapping effective date ranges.
• Can a sequence be shared between general ledger and subledger journal entries? Yes.
Sharing the same sequence between your general ledger and subledger journal entries
for the same ledger and sequence type:
– Ensures that a gapless sequence of numbers is assigned to your journal entries
across general ledger and subledger journal entries.
– Simplifies auditing and tracing of journals regardless of their origin.


Enforcing Accounting and Reporting Document Sequences
• Document sequencing can be enforced by the Sequence Numbering Enforced profile

option at the following profile levels: Site, Product, and User.
• You can choose one of the following options:
– Not Used: The system does not enforce document sequencing for your journal
entries. Enter a unique number.
– Partially Used: The system enforces document sequencing for all the sequences that
are assigned a category. If no active sequence has been assigned to the journal
category, a warning message displays and you can proceed.
– Always Used: The system enforces document sequencing for all categories. If no
active sequence has been assigned to your journal category, you cannot proceed

until you define and assign a sequence.

Practice 13-4 Overview: Creating an Accounting Sequence

• Creating a sequence.
• Creating a sequence version.
• Creating a sequence assignment.
• Establishing associations for your sequence.
• Entering a journal entry to test your sequence.


Manage AutoPost Criteria Sets

To facilitate journal batch posting, define multiple criteria sets that include a range of journal effective dates
and multiple AutoPost priorities. Then, schedule the AutoPost criteria set to run based on parameters you
specify.
For example, if you are a bank, you routinely post journals from your core banking system after running
journal import to record daily customer deposits and loan activities.
You can then schedule the AutoPost program to run at the beginning of each week. Oracle General Ledger
automatically selects and posts your deposits and loans journal entries to update your cash balances.

AutoPost Criteria Sets: Parameters
• Define multiple AutoPost criteria sets and enter parameters that select journal batches
for posting based on:
– Ledger or Ledger Set
– Journal Source
– Journal Category
– Accounting Period


AutoPost Criteria Sets: Elements
• Use the All option for Source, Category, and Accounting Period to reduce maintenance
and ensure that all journal imports are included in the posting process.
• Assign a number to the Priority on each row of criteria. The number must be a value
from 1 to 99, where 1 is the highest priority and 99 is the lowest.
• Enter Yes in Process All Criteria to run all priorities, or No and the Number of Criteria to
Process in the next field to process only a certain number of criteria. This helps balance
the load on the server.
• Enter a number in the Number of Days Before or After Submission to indicate the range
of days before and after the processing date the application needs to check for journal
batches to include in the posting process.

Note: Batches with higher priorities are posted first. You can use the same priority number more than once.

Manage AutoReverse Criteria Sets
If you routinely generate and post a large number of journal reversals as part of your month
end closing and opening procedures, using the automatic reversal functionality saves you
time and reduces entry errors.
The journal must meet the following criteria to be automatically reversed:
• Balance type is Actual.
• Category is enabled to be automatically reversed.
• Reversal period is open or future enterable and specified for the batch to be reversed.
• Posted but not yet reversed.
• Not a reversal journal.

• Not a posted journal for a reporting currency or subledger.
Reporting currency journals that were replicated from a source journal are reversed when the source journal
is reversed.

Manage AutoReverse Criteria Sets

Enable the check box Run AutoReverse after open period in the Journal Processing section of the Specify
Ledger Options page to automatically generate journal reversals when an accounting period is opened.
Note: This ledger option replaces the former profile option called GL: Launch AutoReverse After Open
Period. If you prefer to reverse your journals on the last day of the accounting period, disable the ledger
option to automatically launch reversals when the period is opened. Then schedule the AutoReverse
process.

Manage Accounting Automation
Streamline and automate your end-to-end

accounting and transaction processes with
the accounting automation feature including:
• Import Daily Rates
• Create Accounting
• Import Journals
• Posting

Navigate to: Others > Setup and Maintenance > Setup: Financials > General Ledger > Manage Accounting
Automation.
The data flows through all of the required processing steps with no user intervention, while making it easy to
involve the right people at the right time to resolve exceptions. This ensures the continuous availability of the
most accurate and up-to-date financial information.
• Users are notified of exceptions and shown how to resolve them to prevent interruption in the
accounting process.
• Users can also be notified of errors generated during the transaction accounting process.
Main Components of the Accounting Automation Feature:
• When you opt in, the Manage Accounting Automation setup page automatically opens where you
can complete the setup.
• Email notification and report for the default user: Summary of processed data, errors and pending
approvals to the specified default user.
• Email notification and report for the other specified users: Summary of errors and pending approvals
to the specified users.
Steps to Enable
Use the Manage Accounting Automation setup page to enable and schedule the accounting automation.
You can also optionally specify the users to be notified of the errors generated while processing accounting
transactions, based on the ledger or ledger set, and the category under which an error falls.

Additional Considerations for Accounting Automation
• Transaction data for all of the ledgers (primary, secondary, and journal and subledger
level reporting currencies) in the system is processed.
• You must submit journal batches that require approval manually or use the AutoPost
process.
• If you are using or plan to use any form of coexistence do not enable.
• Accounting is only generated for events with an accounting date of system date or
earlier.

Role Information
The Accounting Automation feature is secured by the Manage Accounting Automation Setup and Run
Accounting Automation Program privileges. The new accounting automation privileges are assigned to the
General Accounting Functional Administration Duty, which rolls up to the Financial Application Administrator
and Application Implementation Consultant job roles..
Additional Considerations
• Incomplete journal batches are not picked up by Accounting Automation for posting.
• Accounting Automation does not pick up transactions that were created on a date before Automation
was enabled, unless the transaction has an accounting date that is the same as, or later than, the
date that Automation was enabled.
• If you use Oracle Receivables and plan to enable Accounting Automation, you must schedule a run
of the Create Receivables Accounting process daily, before the Accounting Automation scheduled
time.

Manage Profile Options
Profile options are global configuration settings that users can modify to change the way an
application works. For example, set the default data access set or financial reporting host.
A profile option is made up of the following:

• Code and Name: Unique identifiers.
• Application: Product such as General Ledger.

Manage Profile Options
• Module: Subsection of an application such as Journals or Currencies.

• Values: Setting such as Adjustment for Default Journal Category.
• Categories: Optional groupings of profile options used for searching and defining data
security.
• Levels: Site, Product, and User.

Profile Option Levels

In an application, the display and availability of profile options depends upon the level at which it is enabled.
The different levels are:
• Site: Lowest level that unless superseded by another level provides accessibility to all the users of
the application, across the site.
• Product: Mid level that applies to the selected product family such as Oracle Financials Cloud and its
specific users. For the same user, the profile option at this level supersedes any site level profile
option setting.
• User: Highest level that applies to the specific user or user role and supersedes any product or site
level setting that was earlier associated with the user. The User Name is entered in the Profile
Values region.

Manage Processing Schedules
• Create Oracle Financials processing schedules based on different calendars.

• Automatically generate processes based on the schedules you define.
• Schedules are shared across ledgers.
• Define multiple schedules for each calendar in General Ledger.


Practice 13-5 Overview: Creating a Processing Schedule

• Creating a schedule to add to your reports.
• Adding your schedule to a report.


Summary

• Manage suspense accounts.
• Manage statistical units of measure.
• Manage journal sources and categories.
• Manage document and journal sequencing.
• Manage AutoPost and AutoReverse criteria sets.
• Manage Accounting Automation.
• Manage general ledger profile options.

• Manage processing schedules.

14
Introducing Consolidations

Objectives

• Discuss consolidation methods.
• Explore the reporting consolidation option.
• Examine the balance transfer consolidation option.
• Define integration with Oracle Hyperion Financial Management with Oracle General
Ledger.


Consolidation Methods

Select the best Oracle General Ledger consolidation solution for your enterprise:
• Reporting Only Consolidations: If your subsidiaries and your corporate ledger share the same chart
of accounts and calendar.
• Balance Transfer Consolidations: If your subsidiaries and your corporate ledger have either or both
different charts of accounts and different calendars.
• Financial Management Consolidations: If there are complex factors in your financial consolidation
requirements such as:
- Complex company structures such as joint ventures, minority interest holdings, partially or
fully owned subsidiaries.
- Multiple heterogeneous systems including non general ledger data sources that are required
to support non-financial or industry specific metrics, disclosures, and footnote schedules.

Reporting Only Consolidation Method: Example
Corporate Ledger Set
Corporate Chart of Financial Reporting
Accounts (COA) and Analysis
Corporate Currency
Subsidiary
Primary Ledger 1 Financial Reporting
Corporate COA
Balance Level
Local Currency
Corporate COA
Reporting Currency in General Accounting
Corporate Currency Dashboard
Subsidiary
Use
Primary Real time Analysis
Ledger 2 with Smart View
Secondary Ledger
Local COA
Balance Level
Local Currency
Corporate COA
Corporate Currency Online Inquiry
Corporate Primary
Ledger

Corporate COA BI Publisher
Corporate Currency
Adjustment Ledger Oracle Transactional

Corporate COA Business
Corporate Currency Intelligence
All subsidiaries and your corporate ledger share the same calendar.
One of your subsidiaries has a local chart of accounts and local currency. This subsidiary uses a secondary
ledger to record balances in the corporate chart of accounts and the corporate currency.
One subsidiary has a local currency and use reporting currency functionality to record balances in the
corporate currency.
With the Reporting Only Consolidation method, perform the following tasks:
• Group the ledgers in a ledger set. This assumes the ledgers share the same chart of accounts and
calendar.
• Translate balances to the corporate currency for ledgers not in the corporate currency. Include these
ledgers in the ledger set. In the example, the Reporting Currency and Secondary Ledgers are
included in the ledger set.
• Create eliminating entries.
• Report using the ledger set and the corporate currency as parameters to view the consolidated
balances.
Note: If each entity’s ledger has a different chart of accounts or calendar from the corporate chart of
accounts and calendar, a secondary ledger would need to be maintained that conforms to the common
chart of accounts and calendar so that this could be included in the consolidation ledger set.

Reporting Only Consolidation Method: Example
Your company, Vision Corporation, needs to You have four entities:

consolidate across its entities worldwide • Vision US
using the Reporting Only Consolidation
Method. • Vision Canada
• Vision UK
• Vision Germany

• Vision Corporation uses secondary ledgers and reporting currencies to align all ledgers to the
corporate chart of accounts, calendar, and currency.
• The Vision Corporate ledger is an elimination ledger to hold the elimination entries.
• Financial Reporting functionally is used to create the consolidation reports.

Reporting Consolidation with Multiple Levels: Level One
Vision North America Elimination Ledger Vision EMEA Elimination Ledger with:
with: • Vision UK
• Vision US • Vision Germany
• Vision Canada

The Vision Corporation Consolidation can happen at two levels. For level one, both ledger sets have been
created for the three ledgers to enable creation of consolidation reports in Financial Reporting.
Level One creates eliminations for transactions between Vision US and Vision Canada and then for
transactions between Vision UK and Vision Germany.

Reporting Consolidation with Multiple Levels: Level Two
• Vision Corporate elimination ledger is used to record elimination entries between all four
entities.
• A ledger set has been created for the five ledgers to enable creation of consolidation
reports in Financial Reporting.

Level two creates eliminations for transactions between all four subsidiaries.

Elimination Entries Example
The arrows represent the business transactions occurring between the entities.

The balances need to be eliminated in the consolidation are between entities within each ledger set.

Elimination Entries Example: Transaction
Vision US pays Vision Canada 10,000 USD for copper wiring.
Company Company Debit Credit

Vision US Expense due 10,000 USD
from Vision Canada
Vision US I/C Payable due 10,000 USD
from Vision Canada
Vision Canada I/C 10,000 USD
Receivable from Vision US

Vision Canada Revenue 10,000 USD
received from Vision US

Elimination Entries NA Level One Example: Elimination Entry
• The eliminations are accomplished using the Calculation Manager by creating allocation
rules.
• The elimination adjustments are recorded in an elimination ledger.
Company Company Debit Credit

Vision US I/C Payable 10,000 USD
Vision US Expense 10,000 USD
Vision Canada 10,000 USD

Revenue

Vision Canada I/C 10,000 USD
Receivable

Balance Transfer Consolidation Method

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

Transfer Ledger Balances Process Parameters
• Source and Target Ledgers

• Chart of Accounts Mapping
• Source Ledger and Target Ledger Period
• Run Journal Import
• Create Summary Journals
• Run AutoPost
• Balancing Segment


Practice 14-1 Overview: Creating a Chart of Accounts Mapping
This practice covers Mapping chart of accounts.


Practice 14-2 Overview: Submitting the Transfer Ledger Balances
Process
This practice covers submitting the transfer ledger balances process.


Reporting Only Versus Balance Transfer: Pros
Reporting Only Consolidation

• No need to run additional processes to consolidate unless ledgers have a different
currency than the consolidation currency.
• View the consolidated balances anytime. This cannot be done in the Balance Transfer
Consolidation method because that method requires a balance transfer be done to
achieve consolidation.
• Faster close.
Balance Transfer Consolidation: Does not require a standardized chart of accounts and
calendar.

When reviewing balances that use either consolidation method, verify that the translation to the
consolidation currency is current.

Reporting Only Versus Balance Transfer: Cons
• Reporting Only Consolidation: Requires a standardized chart of accounts and calendar

for the subsidiaries and corporate ledgers to group ledgers into ledger sets.
• Balance Transfer Consolidation:
– May require an additional consolidation ledger to maintain balances or the current
parent ledger can serve as the consolidation ledger.
– You need to run the balance translation process if the currency is different from the
consolidation currency, and then run the transfer processes to view the consolidated
balances.
– Maintaining charts of accounts mappings can be labor intensive.
– Outdated balance transfers have to be reversed and posted, and then a new balance

transfer process needs to be run every time the source ledger's balance changes.
Additional Information for Balance Transfer Consolidation:

• You can use your parent ledger and just transfer the subsidiary balances directly into that ledger.
• When the source ledger’s balances change may require translation to be run again if ledger currency
is different than consolidation currency. The previous transfer will need to be reversed and the
transfer run again.

Oracle Hyperion Financial Management Integration Overview


Financial Management Integration Option
• The Oracle Accounting Hub Cloud natively integrates to Cloud GL and Cloud GL
includes integration to Hyperion Financial Management through the Enterprise Resource
Planning (ERP) Integrator.
• Use the integration to bring general ledger balances from the Oracle General Ledger to
Oracle Hyperion Financial Management to perform complex consolidations.
• Drill through from Oracle Hyperion Financial Management to the Oracle General Ledger
balances.


Financial Management Integration Implementation
• Map chart of accounts values and hierarchies from the Oracle General Ledger to the
Oracle Hyperion Financial Management dimensions.
• Load data from the general ledger balances table to Oracle Hyperion Financial
Management after performing account transformation of the Oracle General Ledger
chart of accounts in Oracle Hyperion Financial Management.
• Perform advanced consolidation in Oracle Hyperion Financial Management.
• Drill through from Oracle Hyperion Financial Management to the Oracle General Ledger
balances stored in the general ledger balances table.


Mapping Segments to Financial Management Dimensions
Map one to one or concatenate segments into a single Oracle Hyperion Financial
Management dimension.

When integrating with Oracle Hyperion Financial Management, you can use the above dimensions for
consolidation.
Data is summarized across segments that are not mapped to Oracle Hyperion Financial Management
dimensions.
In this example:
• Company is mapped to Company.
• Cost Center and Line of Business are concatenated and mapped to Department
• Account is mapped to account.
• Product is mapped to Product.
• Intercompany is not mapped and its data is summarized.

Summary

• Discuss consolidations methods.
• Explore the reporting consolidation option.
• Examine the balance transfer consolidation option.
• Define integration with Oracle Hyperion Financial Management with Oracle General
Ledger.


15
Introducing Budgets

Objectives

• Describe budgeting preparation.
• Explain integration with Oracle Hyperion Planning.
• Define the budget scenario dimension.
• Load data with ADFdi and Oracle Smart View.


Budgeting Preparation
Budgeting preparation can be done with:

• Oracle Hyperion Planning, Cloud Edition.
• Importing Budget Data from a flat file.
• Importing Budget Data from a Spreadsheet.

2
In Oracle General Ledger, you can load budget data to perform variance reporting.
• Oracle Hyperion Planning, Cloud Edition: Load more complex budgeting data into the GL Balances
Cube.
• Importing Budget Data from a Flat File: Export budget data from your budgeting application to a
comma separated values .csv file. Use the Import General Ledger Budget Balances file-based data
import to prepare and generate flat files in a .csv format. You can use Oracle Application
Development Framework Desktop Integrator correction worksheets to correct validation errors,
delete rows with errors, and resubmit the corrected error rows.
Note: For more information about file-based data import, see the File Based Data Import for Oracle
Financials Cloud guide.
• Importing Budget Data from a Spreadsheet: You can access the budget load spreadsheet from the
General Accounting Dashboard. Enter, load, and correct budget data in the ADF Desktop Integrator
spreadsheet tool. Use this tool to prepare and load budget data for multiple ledgers and periods with
a common chart of accounts instance. The list of values and the web picker help you select valid
values. This simplified data entry reduces errors and alerts you to errors as you enter the data in the
spreadsheet. Error correction is done in the same spreadsheet.

Budget Scenario Dimensions
• Specify as many distinct budget scenarios as needed for every business plan or outlook
to track budget balances.
• Define the budget versions in the Accounting Scenario predefined value set.
• Run the Create Scenario Dimension Members process to publish the budget versions to
the Scenario dimensions in the Oracle General Ledger balances cubes.
• Share budget scenarios across ledgers.


Integration with Oracle Hyperion Planning
• Load your budgets from Planning to the Oracle Accounting Hub Cloud using ERP
(Enterprise Resource Planning) Integrator.
• Perform budget monitoring in General Accounting Dashboard.

Note: If you are already using Oracle Hyperion Planning (Planning) or want to use it for complex budgeting
requirements, use the integration to bring budget amounts into the Oracle Accounting Hub Cloud
(Accounting Hub).
Budget complexity is a function of how distributed the budgeting process is. In other words, do you distribute
budgets across your enterprise that are then aggregated and approved? In such a case, Planning may be
desirable.

Importing Budget Data from a Flat File
• Integrate budget information from other non-Oracle budgeting applications.

• Load budgets for multiple periods and for multiple ledgers.

Use the Upload Budgets processes to integrate budget information from other non Oracle budgeting
applications. You can load your budget amounts to the General Ledger balances cube by populating the
GL_BUDGET_INTERFACE table and running the Validate and Upload Budgets process. You can load
budgets for multiple periods and for multiple ledgers with the same chart of accounts in a single load
process. Note that the budget data is not loaded to the GL_BALANCES table and only loaded to the
balances cube for variance reporting purposes.
Note: You can load data to interface tables using predefined templates and the Load Interface File for
Import scheduled process, which are both part of the External Data Integration Services for Oracle Cloud.
For more information about file-based data import, see the File Based Data Import guide for your cloud
services.

Importing Budget Data from a Flat File: Steps
Perform the following:

• Export Budget Data.
• Upload the zipped .csv file.
• Launch the Load Interface File for Import process.
• Run the Validate and Upload Budgets process.
• Review the Logs for errors.

Load the budget amounts to the interface table by performing the following steps.
• Export budget data from your budgeting application to a comma separated values (.csv) file. The file-
based data import for Import General Ledger Budget Balances has a template that you can use. For
more information about file-based data import, see the File Based Data Import for Oracle Financials
Cloud guide.
• Upload the zipped .csv file to the UCM directory fin/budgetBalance/import.
• Launch the scheduled process called Load Interface File for Import and select the following
parameters:
- Import process: Validate and Upload Budgets
- Data file: Select the name of the zipped .csv file
• Run the Validate and Upload Budgets process to load the budget amounts to the General Ledger
balances cube.
• Review the logs for validation errors. If there are validation errors, correct the data
in the template and regenerate the .csv file. Then resubmit the data by repeating
steps 3 and 4.

Importing Budget Data from a Spreadsheet
• Use Oracle Application Development Framework (ADF) Desktop Integrator.

• Uses a interface table called GL_BUDGET_INTERFACE.

Use Oracle Application Development Framework (ADF) Desktop Integrator to enter, load, and correct
budget data. This functionality uses a interface table called the GL_BUDGET_INTERFACE and requires the
duty role, Budget Entry Duty.
Budget Import
• Budget Import Oracle ADF Desktop Integrator import functionality is similar to the journal import
sheet in Oracle General Ledger. You may use this tool to create and upload budget data. From the
General Accounting Dashboard page, download the import worksheet.
• The budget import uses the Accounting Scenario value set for the budget being loaded. The Run
Name is used as an identifier for the imported data set. The Oracle ADF Desktop Integrator budget
import functionality:
• Supports multiple ledgers but a single chart of accounts instance
• Allows multiple calendars and periods
• Supports entered currencies in addition to the ledger currency
• Contains user-friendly lists of values
• Performs most validations on the worksheet
• Secures values by data access sets

Importing Budget Data from a Spreadsheet: Import Correction
The ADF Desktop Integrator spreadsheet:

Contains a Record Status column that shows if the rows upload successfully or with errors.
Allows you to use the spreadsheet where the data was entered to enter the corrections.

To use the correction spreadsheet functionality, perform the following steps:

• From the General Accounting Dashboard page, you set the data access set and download the
correction worksheet.
• After the correction worksheet is downloaded, you query for the rows in error. Pick the run name for
which there are validation errors and click on the Search button. This populates the budget rows in
error.
• Correct the rows in error or mark for deletion and submit the budget correction spreadsheet. Any
error are reported on the worksheet.
• If the row status indicates an error, double-click it to see the error details and take necessary action.
You can use the list of values to quickly correct data that is in error.

Practice 15-1 Overview: Uploading a Budget Using a Spreadsheet

• Creating a budget scenario dimension member.
• Submitting the Create Scenario Dimension Members process demonstration.
• Uploading a budget from a spreadsheet.


Practice 15-2 Overview: Creating a Smart View Ad Hoc Analysis
This practice covers creating a Smart View ad hoc analysis to view your budget numbers.


Summary

• Describe budgeting preparation.
• Explain integration with Oracle Hyperion Planning.
• Define the budget scenario dimension.
• Load data with spreadsheet and using a flat file.


A
Appendix A: Common Application Topics

Objectives

• Manage Oracle Social Network Objects.
• Define Flexfields.
• Define Lookups.
• Define Profile Options.
• Define Attachments.

Oracle Financials Cloud: Enterprise Structures with General Ledger Implementation A - 2

Manage Oracle Social Network Objects

To manage Oracle Social Network objects, use the Manage Oracle Social Network Objects task in the
Setup and Maintenance work area.
Enabling Business Objects for Integration
• You can determine whether information about a business object, such as benefit plans or sales
accounts, appears in social network.
• If you enable an object for sharing, users can collaborate on the object through social networking.
You can choose whether all instances of an object are shared, or only at the user's discretion. You
can also choose which attributes are shared, such as names and details, and who made the last
update.
• To open the Manage Oracle Social Network Objects page, start on the Setup and Maintenance
Overview page and search for the Manage Oracle Social Network Objects task.

Enablement Options
The following enablement options are available for enabling social network objects on the
Manage Oracle Social Network Objects page:
• Manual
• Automatic
• No

• Manual: (Recommended) Lets users decide whether to share each instance of the object with the
social network. When shared, all updates to the enabled attributes of the instance appear on the
social network. If the instance is deleted, that information is also shared.
Note: Click Enable All to enable all objects for all applications. Enable All automatically applies the
Manual option, which means that the user can choose whether to share an object instance.
• Automatic: Notifications about all instances of the object appears on the social network, including:
- Every newly created instance
- All subsequent updates to the enabled attributes
- Deletion of any instances
• No: (Default value) No notifications about the object appears on the social network.
• Note: When you click Disable Object, the enabled setting of the selected business object is
automatically changed to No.

Enablement Options
After you enable an object, you must enable one or more attributes of the object.
• Only the enabled attributes are shared.
• The Status column in the Business Objects table indicates which enabled business
objects have or do not have enabled attributes.

For business objects with no enabled attributes, only the following information appears on the social
network:
• Internal bookkeeping information when you create or update an instance of the object.
• News that an instance is deleted.

Update Social Network Translations
Use Update Translations on the Manage Oracle Social Network Objects page for
subsequent updates to labels and attributes.
For example, if a new language pack is installed in Oracle Applications Cloud, click Update

Translations to send the updated labels and their translations to social network.
Use Update Translations at the:

• Business Objects table level to send translations for a selected business object to social network.
This button is enabled only when you select a row for a business object with the enablement option
as Manual or Automatic.
• Manage Oracle Social Network Objects page level to send translations for all business objects with
the enablement option as Manual or Automatic to social network.
Note: When you save the enablement of a business object, Update Translations sends the translations. You
don’t need to click Update Translations after saving the enablement.
When you click Update Translations, you:
• Send translations for all business objects with enablement as Manual or Automatic to social network.
• Synchronize the newly translated text from Oracle Applications Cloud so that it can be used within
social network. This means that you can:
- Install and enable a new language.
- Take a language patch at any time.
• Send attribute labels and business object names to social network for use in its user interface.

Update Translations
Note
• In social network, the attribute or business object labels appear in the language of your
locale. If you change the locale, then these labels appear in the updated language.
• The data appears in the language in which it was originally sent to social network.
• If you have previously sent an instance of the business object to social network, then the
instance data is not updated even when you click Update Translations.


Demonstration A-1: Managing Oracle Social Network Objects
This demonstration covers the following topic: Enabling Oracle Social Network objects on
the Manage Oracle Social Network Objects page.


Oracle Social Network Reference Resources
Related Resources:
• Oracle Cloud Applications Common Implementation Guide
• https://osn-fusioncrm.oracle.com/osn/web/help/index.html?locale=en
• https://cloud.oracle.com/mycloud/f?p=service:socialnetwork_faq:0


Define Flexfields


Manage Flexfields
To manage flexfields, use the Define Flexfields tasks in the Setup and Maintenance work
area.
A flexfield:
• Provides a means to customize application features without programming.
• Extends a business object with additional data fields to capture enterprise information.
• Consists of segments representing different data or values.
• Stores data in database table columns, one for each segment.
• Appears to end users as attributes of information.


Types of Flexfields: Descriptive
Flexfield Type Description Examples

Descriptive Optional customizable • Components of a student's contact
expansion space in the user information.
interface for additional • Tracking asset specifics, such as the
information. number of floors, square footage, and
date of insurance renewals.
Extensible Similar to descriptive A list of countries where an electronic item
flexfields, but with is compatible based on country-specific
advanced capacities such standards such as power line frequency
as categories. and item attributes such as signal
resolution.

Key Mandatory key for • Unique item numbers.
identifying business entities • Account numbers.
using an enterprise-defined • A composite key that collates location,
code. price, and shipping time.

Flexfield Concepts

A single flexfield can capture multiple attributes, which you can display in the user interface as fields. The
figure shows several fields added to an order page by defining a part number key flexfield, and additionally a
descriptive flexfield for capturing part type and sales representative information.

Flexfield Segments
• Represent attributes of entities (business objects)

• Can appear:
– Based on a structure or context.
– Globally wherever the flexfield is implemented.
• Can be made available to an application as groups of attributes called contexts.
• Can be assigned a value set that determines which values are valid for the segment.

Of the business objects that are defined to include a flexfield, some can accommodate descriptive flexfields
and others accommodate extensible flexfields or key flexfields, at the discretion of application development.
Flexfield attributes are available across the deployment, such as in Web Services, Oracle Business
Intelligence, desktop integration with Application Development Framework, and Oracle Cloud Search. Any
UI page presenting the business object includes the flexfield attributes that extend the business object.
Oracle Business Intelligence reports include flexfield attributes.

Flexfield Structure
A flexfield structure is:

• Only relevant to key flexfields.
• A specific configuration of key flexfield segments.
• Composed of one or more instances each of which:
– Contains the same number and order of segments.
– Differ in the allowable values or value sets attached to the segments.


Flexfield Context
A flexfield context is:

• Relevant only to descriptive and extensible flexfields.
• A grouping of attributes that makes segments available to an application.
• A set of context-sensitive segments that stores a particular type of related information.
Note:
– Descriptive flexfield segments can be context-sensitive.
– Extensible flexfield segments must be context-sensitive.
• A way of reusing the same database column for a similar or different segment based on
different needs.


Flexfield Category
• Relevant only in extensible flexfields.

• A grouping of contexts.
• A hierarchy of categories.


Flexfield Usage
• Is set when application development registers the flexfield.

• Specifies the application and table the flexfield is associated with.


Accessing Flexfields for Configuration
To configure a flexfield, access it in one of the following ways:

• Using the Highlight Flexfields command.
• Accessing flexfield management tasks and searching for flexfields.


Using the Highlight Flexfields Command
In highlight mode, you can use the:

• Information icon to access details about the flexfield.
• Configure the Flexfield icon to add segments and configure them with advanced options
on segments.
• Add Global Segment icon to add global segments with common options for descriptive
flexfields.
• Add New Context icon to add context values for descriptive flexfields.
• Add Context-Sensitive Segment icon to add context-sensitive segments with common
options for the selected context value of the descriptive flexfield.

Use the Highlight Flexfields command in the Administration menu of the Setup and Maintenance work area
to identify the location of flexfields on the run-time page.

Accessing Flexfield Management Tasks and Searching for Flexfields
Use the flexfield management tasks in the Setup and Maintenance work area. From the task
list, search for Define Flexfields on All Tasks tab.
Tip: Use the Business Object parameter to search Application Key Flexfields, Application
Descriptive Flexfields, and Application Extensible Flexfields to find all tasks related to
flexfields.

Note: To access tasks for configuring flexfields and value sets, you must be provisioned with roles that
entitle you to access the Define Flexfields task list or tasks for managing product-specific flexfields. Contact
your security administrator for details. For information about product-specific flexfield tasks, such as Manage
Purchasing Descriptive Flexfields, consult the product-specific documentation in Oracle Cloud Applications
Help.

Accessing Flexfield Management Tasks and Searching for Flexfields
To manage any flexfield across all Oracle Cloud Applications products, search for the Define
Flexfields task list and access the following tasks:
• Manage Descriptive Flexfields
• Manage Extensible Flexfields
• Manage Key Flexfields
After searching for and selecting the required flexfields, you can use the Configure Flexfield
icon to view and configure the flexfields.


Value Sets
• A set of values assigned to a flexfield segment or other entity outside of flexfields.

• The basis of validation for a value entered into a flexfield segment by an end user.
• Defined before you configure the key flexfield, because you assign value sets to each
segment when you configure the key flexfield.

Security on Value Sets

• Set up segment value security rules on value sets to control access to parent or detail segment
values for your chart of accounts segments.
• Restrict data entry, online inquiry, and reporting.
• Create and edit segment value security rules on the Define Chart of Accounts page from the Setup
and Maintenance work area.
Note: You can create value sets when you create or edit descriptive and extensible flexfield segments.
When you use the Add Global Segment and Add Context-Sensitive Segment icons in Highlight Flexfields
mode, value sets are created automatically when a segment is created.

Value Sets

The figure shows a value set being used for a descriptive flexfield segment.

Value Set Validation
Validation Types Description

Format only End users enter data rather than selecting values from a list.
Independent The list of values consists of valid values you specify.
Dependent A valid value in a list of values derives from the independent value of
another segment.
Subset The list of values is a subset of the values in an existing independent
value set.
Table The values derive from a column in an application table, which can
optionally be limited by a WHERE clause.


Value Set Usage
• Specifies the segment where the value set is assigned.

• Indicates which flexfields use a shared value set.
You can use value sets additionally for supplying values to regular user interface fields, such
as in Oracle Cloud Contracts.

If your application has more than one language installed, or you may install one or more additional
languages for your application in the future, select Translatable. If you select Translatable, you do not need
to provide translated values now, but you cannot change this option if you decide to provide them later.

Descriptive Flexfields
A descriptive flexfield:
• Is often optional.
• Provides a way to add custom attributes to entities and define validation and display
properties for custom attributes.
• Is enabled for most business entities.
• Consists of segments that are made available to end users as individual fields in the
application user interface.


Descriptive Flexfields: Segments
• Correspond to custom attributes of entities.

• Are generally standalone and need not be related or treated together with other
segments as a combination.
• Are of the following types:
– Global segment, which is always available.
– Context segment, which determines the context-sensitive segments that are
displayed.
– Context-sensitive segment, which is displayed depending on the value of the context
segment.


Descriptive Flexfields: Context Segment
• Need not be assigned a value set.

• If assigned a value set, you can use only table-validated or independent value sets.
• Note
– The data type must be character.
– The maximum length of the values being stored must not be larger than the column
length of the context.


Descriptive Flexfields
The number of segments available for configuring is determined by the number of columns
reserved by application development to store segment values. During implementation,
determine which attributes to add using the:
• Available columns
• Context values
• Combination of attributes in each context
The same column can be used for attributes in different contexts, such as Height in
Context1 and Color in Context2.

For each global and context-sensitive segment, you configure the values allowed for the segment and how
the values that are entered by end users should be validated, including interdependent validation among the
segments.

Adding Flexfield Segments on Application Pages
For adding segments and configuring them with advanced options on segments (such as
change a segment’s sequence number, or configure a descriptive flexfield segment’s
business intelligence label), use the Configure Flexfield icon.


To configure segments with common options, use the following icons on an application page
where descriptive flexfields are highlighted:
• Add Global Segment: To add global segments for descriptive flexfields. Global segments
are always relevant, irrespective of context values.
• Add New Context: To add context values for descriptive flexfields.
• Add Context-Sensitive Segment: To add context-sensitive segments for the selected
context value of the descriptive flexfield.

• The context segment immediately precedes the Add New Context icon.
• The values that you add using the Add New Context icon appear in the drop-down list of the context
segment after you refresh the page.
• You must select a context value from the context drop-down list, and then use the Add Context-
Sensitive Segment icon to add a segment specific to that context value.
• You must sign out and sign in to the application again to view the changes you make using the
following icons:
- Configure Flexfield
- Add Global Segment
- Add Context-Sensitive Segment

When you use the Add Global Segment and Add Context-Sensitive Segment icons:
• You must accept the automatically set:
– Segment code
– Name and description
– Table column
– Sequence number
• You must accept the automatically created value set.
• You can enter valid values, including:
– Valid values descriptions

– The default value
– Formatting constraints for the value set, such as minimum and maximum values
Depending on the display type, the value set created by the Add Global Segment and Add Context-
Sensitive Segment icons is one of the following value sets:
• An independent value set
• A format-only value set

The following table shows which type of value set is created depending on the display
component you select:
Display Component Type of Value Set

• Check box Independent
• Drop-down List
• List of Values
• Radio Button Group
• Pop up List of Values
• Text Box Format Only

• Text Area
• Date and Time

Extensible Flexfields
Extensible flexfields are like descriptive flexfields, with some additional features.
With extensible flexfields, you can:
• Have multiple groups of custom attributes attached to a single entity. Each group of
custom attributes is a context. In addition, different entity rows can have different groups
of attributes (or contexts) based on the value of the category. This is in contrast to
descriptive flexfields for which the attributes vary based on the context.
• Add as many context-sensitive segments to the flexfield as you need. You are not limited
by the number of segments predefined and registered for the flexfield.


• Configure a one-to-many relationship between the entity and its extended attribute rows.
• Configure attributes in contexts, which serve as groups of attributes. Attributes in a
context appear together in the user interface.


Extensible Flexfields Context
• Can be defined as single-row, meaning a one-to-one relationship between the entity and
its extended attribute rows.
• Can be defined as multirow, meaning a one-to-many relationship between the entity row
and its extended attribute rows.
• Can be set to store translatable free-form text values.
• Is reusable throughout extensible flexfield categories.


• An extensible flexfield category enables you to:

– Use the category value (that each entity row has) to determine which attribute groups
(contexts) apply to the row.
– Assign different combinations of contexts to different categories to capture different
information about different entity rows.
• An extensible flexfield page:
– Combines contexts into a group that is presented together in the application user
interface.
– Corresponds to one extensible flexfield category, with a separate section of the page
for each associated context.

Note
For some extensible flexfields, you can define categories in a hierarchy. When you use hierarchical
categories, the entity displays attributes from contexts that are:
• Directly associated with the category
• Defined in parent categories of the category

Extensible Flexfield Example
You can specify whether end users can enter one set of data or multiple sets of data for a
context.
For example, if you have a job positions entity that stores information about different
positions in your organization, you can configure additional contexts that store a list of
requirements for that position.


To start with, the job positions entity includes fields for the following attributes:
• Position ID
• Position code
• Description
• Department
• Location
• Hiring status
• Whether the job is permanent or temporary

• Whether the job is full-time or part-time

• You then can extend the list of job positions to capture the following classes of attributes:
– Educational requirements, such as degrees
– Certifications and licenses required for the position
– Travel required for this position

Implement this by setting up context values corresponding to each group of custom attributes. Setting up
context values means specifying segments for each context, such as various degrees in an educational
requirements context and various credentials in a certification and license requirements context. You set up
a job position category that contains the three contexts for the three classes of attributes you want to
capture, and set up a page for that category.


When users create a job in the job positions category, they see the additional attributes. When users define
job position requirements, they select the education level, credentials, and travel required by the position.

Key Flexfields
A key flexfield:
• Provides a means of capturing a key, such as a part number, a job code, or an account
code that represents an entity in your application.
• Consists of one or more segments, where each segment can have a meaning.
• Is not optional and must be configured to ensure that your applications operate correctly.
• Is provided by applications development and is configured and maintained with the
Manage Key Flexfields task.


Key Flexfields
• Have one corresponding combinations table containing the complete codes or

combinations of segment values that make up the codes.
• Can be used in different ways on different pages:
– Combination maintenance page, where users maintain individual combinations
directly.
– Foreign key page, where users manipulate rows containing code combination IDs
(CCID).
– Partial usage page, where users may be presented with only parts of the
configuration based on a product’s transaction table.


Key Flexfield Structure
• Defines the following segment options:

– What segments to include
– Number of segments
– Segment sequence
– Segment labels where applicable, for example, natural account and primary
balancing in general ledger
– Value sets
• Sets the maximum number of segments allowed in your key flexfield combinations table.
• Allows one or more alternate structure instances that can have different value sets.

• Includes a delimiter to visually separate segment values when the key flexfield is
displayed in the user interface.

Key Flexfield Instances
All key flexfield structure instances:

• Contain the same:
– Set of segments
– Arrangement of segments
– Properties at the segment and structure levels
• May differ in whether dynamic combination creation is allowed, which means a new valid
combination is inserted into a combinations table from a page other than the
combination maintenance page.


Key Flexfields
Key flexfield segment instances in a key flexfield structure instance may differ in the
following aspects:
• Value set
• Default type and default value
• Tree code defining a hierarchical relationship to other segment values of a key flexfield
registered with a tree structure
• Whether the segment is any of the following:
– Required
– Displayed

– Enabled for business intelligence
– Optional or required as a query criterion in a key flexfield combination search

Key Flexfields
The predefined key flexfields are:

• Account Alias Flexfield
• Accounting Flexfield
• Asset Key Flexfield
• Budgeting Flexfield
• Category Flexfield
• Cost Allocation Flexfield
• Item Categories

• Location Flexfield
• Locator Flexfield
• People Group Flexfield
• Valuation Unit Flexfield

Tips for Managing Key Flexfields
• When you configure a key flexfield, define metadata about the key flexfield, such as how
many segments are in a structure, how many structures the flexfield uses, and what
value sets each segment uses.
For example, you can use one group of value sets for the US and another for France.
• You must add segments in the order that your key requires. After they are deployed, the
order can’t be changed.
• If you change the configuration of a key flexfield, such as the delimiter, the change
affects the previously stored key flexfields with that structure.
• Enable segments to indicate that they are in use and appear at run time.


Tips for Managing Key Flexfields
• Don’t change the number, order, and maximum length of segments after you have
acquired flexfield data.
• To protect the integrity of your data, disable a segment if you have already used it to
enter data.
• You can dynamically create account code combinations when entering data by enabling
dynamic insertion on the Key Flexfield Instance page.
• At any time, enable or disable allowing dynamic combination creation.
• Define cross-validation rules to ensure that the dynamic combination creation process
doesn’t create incorrect account combinations.


Flexfield Implementation Flow

Managing flexfields involves registering, planning, configuring, and deploying flexfields. Applications
developers develop and register flexfields. Administrators and implementors configure flexfields and
optionally customize their appearance in the user interface.

Flexfield Implementation Flow
There are two types of deployment:

• A sandbox-enabled flexfield for testing flexfield behavior in a sandbox MDS repository
that is accessible only to the administrator who activates and accesses it, not to users
generally.
• A mainline-enabled flexfield for applying the flexfield definition to the mainline MDS
repository where it is available to end users.
After deploying the flexfield to the mainline, you can customize the page where the flexfield
segments appear.


Flexfield Reference Resources
Related Resources:
• Oracle Cloud Applications Implementing Common Features
• Oracle Applications Cloud Extending the Applications
• Oracle Cloud Applications Developer's Guide
To view flexfields in the Oracle Enterprise Repository, see
https://fusionappsoer.oracle.com/oer/.


Define Lookups


Sample Lookup Type
Lookup Type Lookup Code Meaning Tag Enabled
TICKET_CLASS ANY Any class Any 

depending
upon availability
BUSINESS Business class Business 
FIRST First class First 

ECONOMY Economy class Economy 
Per the settings shown in the table, users would see the following values in the list on the application UI to
determine the ticket class:
• Any
• Business
• Economy

Lookup Components
• Lookup Type: A static list of values that users use to make entries in the application.
• Lookup Code: An internal application code for each lookup that is not visible to users.
• Meaning: The actual UI term that appears in the lookup list of values.
• Tag: A label associated with the lookup.
• Enabled: A status that determines the availability of the meaning within the selection list
for the lookup type.

• Lookup Type: This is the name of the field that appears on the setup UI and not on the application UI
where you make the selection.
• Meaning: The actual UI term associated with the lookup code. It is the item that appears in the list on
the application UI against the specific field name, and can be selected by users to indicate their
choice.
• Tag: Certain product offerings use lookup tags for functionality that is specific to that product. Refer
to the product offering specific documentation for more information. If no such use of tag is
documented, the tag is ignored.
• Enabled: If you do not enable it, the value does not appear in the selection list at run time.

Lookup Categories
• Standard Lookups: Consist of lookup codes and their meanings.

• Common Lookups:
– Available for internal system administrative use.
– Used by more than one application.
• Set-Enabled Lookups: Contain lookup codes that are part of a reference data.
– Use sets to enable various values in the lookup for different sets of users.
– Select an attribute at run time to determine which set-enabled lookup is visible to the
users.

• An example of a Set-Enabled Lookup: The attribute east-coast or west-coast in the location

determinant determines whether it is the east-coast or the west-coast location, depending on the
selected lookup.
• Lookup codes and their meanings are valid within a specified date range. If a date range is not
specified, the lookup codes and meanings have indefinite validity from the time they are created.

Manage Lookups
• Define the three types of lookups in:

– Standard view
– Common view
– Set-enabled view
• Lookups are:
– Enabled
– Associated with a module
– Striped by application taxonomy to provide a criterion for narrowing a search or
limiting the number of lookups accessed by a product-specific task such as Manage
Purchasing Lookups

You can create new lookup types and also add new lookup codes and meanings to the existing lookup
types, depending on the access permissions granted to you. But for the lookups and lookup values to
appear as values in the lists, they need to be enabled.
• To enable a lookup type, you need to enable at least one of its lookup codes and that code must be
in a valid date range.
• By default, most lookup types are enabled at the time of deployment. You can disable the ones that
you do not require.
Note: Applications development can define lookups in an application view to restrict the UI pages where
they appear.
Navigate to:
• Others > Setup and Maintenance > Tasks Panel > Search > Enter Define Lookups in the
Name field > Expand > Manage Standard Lookups
Name field > Search > Expand > Manage Common Lookups
Name field > Search > Expand > Manage Set Enabled Lookups

Customize Lookups
• Based on the defined customization levels.

• Restricted to the extent to which customization is allowed.
• The following levels of customization are defined:
– User: Create or modify all parameters of a lookup type.
– Extensible:
— Modify only certain aspects of the lookup type such as the dates.
— Add new lookup codes.
— Cannot delete the lookup type.
– System:
Cannot add or delete any aspect of the lookup type.

—
— Modify only its meaning.

Define Profile Options


Define Profile Options
In this section, you will learn key concepts about:

• Profile Options
• Profile Option Categories
• Profile Option Levels and Values
• Profile Options for Common Setup


Profile Options
Profile options are global configuration settings that users can modify to change the way an
application works.
For example, settings such as user preferences and application configuration parameters
can be modified per the user’s requirements.

You can use profile options to modify:

• The look and behavior of the application's user interface
• User preferences such as settings used for social networking
• The business logic of the application
• Log settings and processing options that determine how and where information is stored
A profile option consists of:
• Name
• Application and module
• Values
• Categories and Hierarchy level
You can modify any of these constituents of the existing profile options, but system administrators must
have enabled the profile option for modification.
The use of profile options is guided by the functional requirements. To determine which profile options to
use in the implementation project, refer to the product offering-specific documentation.

Profile Option Categories
Profile options are grouped into categories depending on the functional area in which the
profile options are used.
Profile option categories facilitate searching and defining data security.
A profile option can be grouped into more than one category.

For example, in Oracle Receivables, the Transactions profile option category groups the profile options that
are related to Receivables transactions processing, such as:
• Require Adjustment Reason
• Invoices with Unconfirmed Receipts
• Use Invoice Accounting for Credit Memos

Profile Option Levels
In an application, the display and availability of profile options depends on the hierarchy
level at which it is enabled.

The hierarchy levels are:

• Site level: The lowest level of hierarchy (unless superseded by any other level) that provides
accessibility to all users of the application across the deployment site. In a multitenant environment,
Site is scoped per tenant.
• Product level: The next level in the hierarchy that applies to the selected product family (product
offering within Oracle Cloud, such as Financials) and its specific users. For the same user, the profile
option at this level supersedes any site level profile option setting.
• User level: The highest level in the hierarchy that applies to the specific user or user role. Also, it
supersedes any product or site level setting that was defined for that user.
Note: Profile options defined at higher levels override the profile options at the lower level.
Profile values determine application behavior at a specific selected level. Contexts, such as user session or
accessed product, determine which profile option value is associated with the profile option name.
The following example of the AFLOG_LEVEL profile option shows how the profile values determine
application logging at various levels.

Profile Option Values
Profile values determine application behavior at a specific selected level. Contexts, such as
user session or accessed product, determine which profile option value is associated with
the profile option name.

This example of the AFLOG_LEVEL profile option shows how the profile values determine application
logging at various levels:
• Site
- Profile option value: Severe
- Effect: Log activities at the site level indicating failures within the environment
- Result: Only administrators are notified
• Product/Product Family (CRM/SCM)
- Profile option value: Warning
- Effect: Log activities that are specific to the product family
- Result: Administrators and product-specific implementation consultants are notified
• User (Bob)
- Profile option value: Info
- Effect: Log activities pertaining to user actions such as invalid user name or password, or
account locked out
- Result: Administrators, implementation consultants, and users are notified

Profile Options for Common Setup
You can set up a common profile option, such as logging, which applies to the entire
applications suite.

By default, logging is set to SEVERE at the Site level. To diagnose or troubleshoot any problem, set logging
to FINEST at the User level for a particular user so that you can examine the logs in detail.
As a result, actions of that particular user are captured in the finest level possible. The benefit of this setting
is that it does not affect other users and does not impact logging or performance at the Site level.
Another example could be the use of the profile option FND_SERVER_TIMEZONE to record the time zone
of the database instance. The selected profile value and the hierarchy level at which the profile option is set
determines the time stamp on all the transactions performed on that server. Usually, such profile options are
applied only at the site level because of their universal impact.
You can find these profile options under the Manage Profile Options task on the Setup and Maintenance
Overview page.

Quiz Q
For a profile option, if you set the hierarchy level for both site and user, the site level
hierarchy takes precedence over the user level hierarchy.
a. True
b. False

Answer: b

Define Attachments
This section describes the tasks in the Define Attachments task list:
• Manage Attachment Entities
• Manage Attachment Categories

Navigate to:
• Others > Setup and Maintenance > Tasks Panel > Search > Enter Define Attachments in the Name
field > Search > Expand > Manage Attachment Entities
• Others > Setup and Maintenance > Tasks Panel> Search > Enter Define Attachments in the Name
field > Search > Expand > Manage Attachment Categories

Define Attachments


Key Concepts
Attachments are:
• Pieces of supplementary information that users can associate with specific business
objects. For example, users might attach receipts to expense reports.
• URLs, desktop files, or text.
• Stored in a content server.

When attachments are stored in the Oracle Enterprise Content Management document repository, users
can select folders or files from the repository as attachments.
Attachment entities
• Identify the business object that attachments can be attached to.
• Are typically named after the primary table or view used to store information about the business
object.
Attachment categories
• Classify attachments. For example, when users add an attachment to an expense report, they can
select a category to indicate whether the attachment is a receipt, travel itinerary, and so on.
• Can optionally be used to restrict access. For example, users with a specific role are not given
access to one of the expense report attachment categories, so they cannot select it when adding
attachments to their reports. They also cannot see any attachments assigned to the category.
• Are assigned to attachment entities so that each category is tied to the relevant business objects.
Note: Each attachment entity must have at least one assigned category. Otherwise, users cannot add
attachments for the corresponding business object.

Key Concepts
• The UIs across Oracle Cloud Applications facilitate adding attachments, where
applicable.
• Depending upon the roles and access levels, you may view, add, update, or delete
attachments.

Where access is not granted, users cannot view any attachment. For example, if a user does not have
access to a specific expense report, then the same user cannot access attachments for the expense report.

Manage Attachment Entities
• Attachment entity is a database entity – a table or a view.

• An attachment entity represents business objects with which the actual attachments can
be associated.
• You can either use the predefined entities or create new ones.

• An attachment entity name should match the name of the table or view that represents the business
object to attach to. The name is also used in the repository folder that is automatically created to
store attachments for the entity.
• The attachment entity display name should be something that users know to represent the business
object.

Manage Attachment Categories
Attachment UIs for users to add or manage attachments are fully functional and do not
require setup.
Predefined attachment categories are already assigned to attachment entities.

For your changes to appear in attachment UIs for users, the users must sign out and sign in again to clear
the cache for categories. If your new categories are still not displayed, then the specific attachment UI likely
has predefined restrictions on categories in place. Check with your administrator or help desk.
Note: The Manage Attachment Entities task can also be used to assign categories to entities. You do not
need to use this page unless you are performing additional or technical configuration.
If an entity has only one category, then:
• All attachments added for the corresponding business object are automatically assigned to that
category.
• The Category attribute is hidden in the UIs where users add or view attachments for the business
object.

Manage Attachment Categories
• Create new attachment categories as needed and assign to relevant attachment entities.
• Remove the association of categories with specific entities.

Example of creating new attachment categories

Your company wants to identify attachments that fulfill a specific fiscal requirement. You can create a new
category and assign it to all attachment entities representing business objects that are relevant to the
requirement.
Example of removing the association of categories
A predefined category is not relevant to any of your users for certain business objects, so you remove its
association with those objects.

Attachment Category Security
You or a technical administrator can implement data security on attachment categories to

determine:
• Which categories users can access when adding attachments.
• What actions they can perform on attachments assigned to those categories.

For an attachment category or set of categories, assign one or more of the privileges to roles. For details,
see the Oracle Cloud Applications Developer's Guide.
After the security rules are in place, you or your technical administrator can use the Security Enabled check
box on the Manage Attachment Entities page to enable this security for specific attachment entities.
Note: If security is enabled for an attachment entity before any data security rules are in place for a
particular category, then that category will not be visible to anyone until rules are in place or security is
disabled.
In some cases, data security for categories is predefined. For example, predefined attachment categories
are available for suppliers and receivers. Both types of users can go to the same page with an attachment
UI, but see only the categories that they can access based on security.

Attachment Category Security
Each action is captured by predefined privileges:

• Read: Read Application Attachment
(FND_READ_APPLICATION_ATTACHMENT_DATA)
• Update: Update Application Attachment
(FND_UPDATE_APPLICATION_ATTACHMENT_DATA)
• Delete: Delete Application Attachment
(FND_DELETE_APPLICATION_ATTACHMENT_DATA)

For example, the Expense Report attachment entity currently has three attachment categories:
• Receipts
• Missing Receipts Declaration
• Travel Itinerary

Example
• You need to track the mileage of cars that belong to your company.
• Your users record miles traveled in a log book, scan the relevant page, and attach the
image file as part of their expense reports.
• The clerks handling the corporate fleet vehicles need to see these attachments, but
should not view the other types of attachments for expense reports. The managers of
users submitting the expense reports can view all categories.


Solution
To implement this security:

• Use the Manage Attachments Category page to create a Mileage attachment category
and associate it with the Expense Report attachment entity.
• Define data security so that the role for the clerk can see only the Mileage category,
while the role for the manager can see all categories.
• Select the Enable Security check box on the Manage Attachment Entities page for the
Expense Report entity.


Quiz Q
Attachment categories are assigned to specific attachment entities:
a. So that the categories are available for the relevant business objects.
b. Because these are the entities with the Enable Security check box selected.
c. Only on the Manage Attachment Categories page.
d. All of the above.

Answer: a
You would not assign categories to security-enabled entities. Security is optional.
You can also assign categories to entities using the Manage Attachment Entities page.

Quiz Q
Attachments can be created without an assigned attachment category.
a. True
b. False

Answer: b
All attachments must have an assigned category. Even if the attachment entity has only one associated
category, attachments are automatically assigned to that category and the user does not see a field to select
a category.

Summary

• Manage Oracle Social Network Objects.
• Define Flexfields.
• Define Lookups.
• Define Profile Options.
• Define Attachments.


B
Appendix B: Implementing Financials for

Asia/Pacific and EMEA

Objectives
After completing this lesson, you should be able to set up the following :
• Manage Enterprise Financial Data Export Options for China.
• Defining the Structure for Natural Accounts for China.
• Create Enterprise Additional Account Attributes for China.

Oracle Financials Cloud: Enterprise Structures with General Ledger Implementation B - 2

Managing Enterprise Financial Data Export Options for China
Export financial data from the following into a format specified by the National Audit Office of
the People's Republic of China.
• Oracle General Ledger
• Oracle Payables
• Oracle Receivables
• Oracle Subledger Accounting
• Oracle Assets

To be able to export data, provide the following:

• Financial Information
• Accounting Book Information
• Depreciation Method Formula

Defining the Structure for Natural Accounts for China
The account structure flexfield specifies the structure code for the natural account structure.
It indicates the hierarchy of natural account against the local statutory requirement.
For example, local government requires that the natural account must have eight digits, the
first four digits for the first level, the next two digits for the second level, and the last two
digits for the third level. The structure in this case is 4-2-2.

Define the subsidiary account sources based on the chart of accounts. There are three types of subsidiary
account sources available:
• Chart of account segments: Segments in chart of accounts except for natural account segment and
company segment.
• Third party and employee supplier information: Customers, suppliers, and employees can be taken
as subsidiary account.
• Project: A seeded supporting reference populates the project number to be a subsidiary account.
You can specify about 30 subsidiary segments. Subsidiary segment is mapped to subsidiary account
sequentially when saving.

Enterprise Additional Account Attributes for China
The Create Enterprise Additional Account Attributes for China process creates two
additional attributes for natural accounts under the chart of accounts:
• Cash-Related Account for China attribute to export cash related journals.
• Balance Side for China attribute to export data from general ledger.

You can run this process only once to register the customer value attributes. It's recommended that you run
the process before setting up the chart of accounts and enterprise financial data export options for China.

Summary
After completing this lesson, you should have learned to set up the following:
• Manage Enterprise Financial Data Export Options for China.
• Defining the Structure for Natural Accounts for China.
• Create Enterprise Additional Account Attributes for China.


C
Appendix C: Predefined Reports for General

Ledger

Objectives

• Describe the predefined Oracle Business Intelligence Publisher reports.
• Discuss the predefined Oracle Transactional Business Intelligence reports.
• Understand the predefined subject areas.

Oracle Financials Cloud: Enterprise Structures with General Ledger Implementation C - 2

General Ledger
Oracle General Ledger provides predefined reports that are used in the close process and to
verify setup of the accounting configuration.
• Account Analysis Reports
• Journal Reports
• Trial Balance Reports
• Reconciliation Reports
• Chart of Accounts Reports


GL BI Publisher Reports
Title Description
General Ledger Journal and Retrieves information for the reports that require journal entries and account balances.
Balance Report The account balances can be printed for selected levels of the hierarchy for actual,
encumbrance, or budget balance types.
General Ledger Journal Provides general ledger journal activity optionally for a given period or date range, and
Entry Report optionally other criteria including journal source, entered currency, and journal batch.
Flexible grouping and sorting options are provided at report submission.
General Ledger Trial Lists detailed or summary actual account balances and activity by ledger, balancing
Balance Report segment, and account segment. The report prints the value, description, and debit or
credit balance for the beginning and ending period, along with the debits and credits for
the period. The report can print income statement, balance sheet, or all balances for a

selected range of accounting code combinations.
The table lists the title and description of reports.

Title Description
Account Analysis for Contra Account Lists contra account balances by natural account segment, primary
Report balancing segment and optionally a third segment for each journal entry.
Lists the subledger document number for transactions imported from
subldegers.
Average Balance Audit Account Provides the detailed account activity that created the aggregate balances
Analysis Report and related average balances. Used to research how average balances are
calculated for an account. Displays daily average balance information for
the selected accounts for the specified date range.
General Ledger Account Details Report Provides periodic journal activity for each general account to reconcile
beginning and ending account balances. Includes journal source, category,
name, description, reference, accounting date, and amount.

Journals Report Provides journal activity details such as ledger, accounting date, posting
date, source, category, journal batch name, journal name, reference, line
accounts, line descriptions, and amounts. Subtotals are provided for each
journal, journal batch and source. It also includes reconciliation information
for clearing accounts.

Title Description
Journals Batch Summary Report Provides posted journal batches details such as ledger, entered currency,
balancing segment value, category, source, batch name, and entered amounts.
Subtotals of entered amounts are provided for each category, accounting period
, and balancing segment value.
Journals Batch Summary Report Provides posted journal batches details such as ledger, entered currency,
balancing segment value, category, source, batch name, and entered amounts.
Subtotals of entered amounts are provided for each category, accounting period
, and balancing segment value.
Journals Details Report Provides detailed information on general ledger journals of the selected posting
status such as ledger, source, category, accounting date, line accounts, line
descriptions, and amounts.


Title Description
Journals Day Book Report Provides posted journal details by accounting date such as ledger,
balancing segment value, source, category, subledger document
sequence, document number, line accounts, line descriptions, and
amounts. The journals are sorted by document number.
Trial Balance Lists period debits, period credits, beginning, and ending account balances
summarized by natural account or account combination or natural account
plus another segment.
Trial Balance – Average Report Lists ending account balances and period, quarter, and year average-to-
date balances on an accounting date for the selected accounts.

Chart of Accounts Mapping Rules Provides details of the segment and account rules defined for a specific
Report chart of accounts mapping considering the effective tree versions for the
selected date.

Title Description
Balancing Segment Value Assignment Report Lists the assignment of primary balancing segment
values to legal entities and ledgers across accounting
setups to identify overlapping and unassigned balancing
segment values.
General Ledger and Subledger Accounting by Journal Lists account balances or selected segment balances
Lines Report with subledger journal details including entered amounts,
third-party name, journal source, journal category, and
reporting and accounting sequences. Total number of
debit and credit documents are also listed.
Enterprise Structures Setup Report Provides a detailed listing of the chart of accounts
structures, segments, values sets, ledgers, legal entities,

business units, segment values, and account hierarchy
information. The report can be scheduled to run
automatically at periodic intervals to track any changes to
the overall enterprise structures setup.

Title Description
Reconciled Transactions Report Provides details of clearing accounts journal lines that
have been successfully reconciled by both automatic and
manual reconciliation processes.
Unreconciled Transactions Report Lists all unreconciled clearing accounts journal lines that
have been rejected by either automatic or manual
reconciliation processes, as well as those lines that have
not yet been subjected to reconciliation.


Practice C-1 Overview: Running a GL BI Publisher Report

• Scheduling and submitting the Trial Balance report.
• Viewing the Trial Balance report.


General Ledger Oracle Transactional BI Reports
Title Description
Account Analysis Report Provides the beginning, periodic activity and ending balances for the selected
accounts and periods. Drill down on the periodic activity balance provides journal
details and transactions details including journal source, category, transaction number,
and event class. It also includes reconciliation information for clearing accounts.
General Journals Report Provides the journals activity for the selected period. The content can be filtered by
ledger set, ledger, entered currency, approval status, date range, account, source,
category, journal batch, and batch status.
Trial Balance Report Provides the beginning, periodic activity and ending balances summarized by
balancing segment, natural account, and cost center for the selected ledger,
accounting period, and currency.


General Ledger Subject Areas
Title Description
General Ledger – Balances Real Time Real-time information on general ledger balances.
General Ledger – Journals Real Time Real-time information on general ledger journals.
General Ledger – Period Status Real Time Real-time information on general ledger period statuses.
General Ledger – Transactional Balances Real Time Real-time information on general ledger balances.


Practice C-2 Overview: Running a General Ledger OTBI Report

• Running the Account Analysis report.
• Viewing the Account Analysis report.


Intercompany
Oracle Financials Common Module, Intercompany provides predefined reports that are used
in reviewing and reconciling transactions.
• Intercompany Reconciliation Reports
• Intercompany Transaction Summary Reports
• Intercompany Account Details Reports


Intercompany BI Publisher Reports: Reconciliation Reports
Three reports list the processing results of the Prepare Intercompany Reconciliation
Reporting Information process.
Title Description
Intercompany Reconciliation Information about the intercompany receivables and intercompany payables
Period Summary Report accounts summarized by period.
Intercompany Reconciliation Information about the intercompany receivables and intercompany payables
Summary By Source Report accounts summarized by journal source. Drill down to detail.
Intercompany Reconciliation Information about journal lines posted to the intercompany receivables or
Journal Lines Report intercompany payables account. Drill down to detail.

The reconciliation process generates the above reports and is dependent on the Prepare Intercompany
Reconciliation Reporting Information process for the report output.
The Prepare Intercompany Reconciliation report is submitted from the Scheduled Processes work area or
from the Intercompany work area by selecting the Intercompany Reconciliation task.

Intercompany BI Publisher Reports
Title Description
Intercompany Account Details Report Generates information about accounting details of outbound
and inbound intercompany transactions. Outbound transaction
accounts include provider distribution and provider receivables
accounting. Inbound transaction accounts include receiver
distribution and payables accounting.
Intercompany Transaction Summary Lists the intercompany transactions based on the submission
Report selection criteria. Information includes provider organization,
receiver organization, batch, and transaction details.


Intercompany Oracle Transactional BI Reports
Intercompany has one predefined Oracle Transactional BI report and subject area you can
use to create your own custom reports.
Report Title Description
Intercompany Transaction Provides information about intercompany transaction lines grouped by outbound
Summary Report and inbound transactions. The report can be customized for one or more
intercompany organizations.
Subject Area Description

Financials Common Module - Intercompany Transactions Real-time information on intercompany transactions.
Real Time Subject Area

Practice C-3 Overview: Running an Intercompany Transaction
Summary Report
• Running the Intercompany Transaction Summary report.
• Viewing the Intercompany Transaction Summary report.


Budgetary Control
Oracle Budgetary Control provides predefined reports that are used by the public sector and
commercial organizations to define and manage budgets and actual costs, and comply with
legal requirements.
• Budget Import Execution Report
• Budget Import Analysis Reports
• Budgetary Control Results Reports
• Budgetary Control Exception Analysis Report
• Budgetary Control Analysis Reports


Budgetary Control BI Publisher Reports
Title Description
Budget Import Execution Report States the overall import result, and provides a statistical summary
of control budgets into which the budget data is successfully
imported; provides the detailed errors if the import fails.
Budget Import Analysis Report: Control Lists the control budgets, budget accounts, budget periods, and
Budget Balance amounts that are impacted by each imported budget line item.
Budget Import Analysis Report: Budget Lists the budget release histories and future budget release
Release for Consumption schedules for control budgets that do not allow their budget
amounts to be available for consumption until they are released.


Budgetary Control Results Reports
Title Description
Budgetary Control Lists the impacted control budget, account, and period for a specific transaction as a
Results Report result of budgetary control validation.
Budgetary Control Lists the impacted control budget, account, and period for a group of transactions as
Results for Batch Report a result of budgetary control validation in a batch process.
Budgetary Control Lists the budgetary control failures by control budget period. The budget account,
Exception Analysis transaction type, number, amount, and action are listed.
Report


Budgetary Control Analysis Reports
Title Description
Budgetary Control Lists fund budget and consumption balance for a specific control budget in a range of
Analysis - Funds periods. The budget, commitment, obligation, and expenditure balance by cost center
Available Trend Report and account are also listed.
Budgetary Control Lists funds available by control budget account and period. Budget consumption from
Analysis - View Funds transactions is listed along with the impacted commitment, obligation, and
Available Report expenditure, and funds available balances.
Budgetary Control Lists control budget accounts by period with consumption and without consumption.
Analysis - Account Account balance and transaction details are also listed.

Activities Report

Budgetary Control Subject Areas
Oracle Budgetary Control has one predefined Oracle Transactional Business Intelligence
report, but you can create your own custom reports using the predefined Budgetary Control
subject areas:
Title Description
Budgetary Control - Transactions Real Time Real-time details of transactions and their impact on
budget balances for the ad hoc analysis of budget
consumption and funds available. New attributes added.
The enhancements include new attributes for requisition
header, requisition lines, requisition project information and
requisition distribution amounts; purchase order
headcount, lines, distribution amounts; payable invoice
distribution information; and manual journals.

Budgetary Control - Balances Real Time Available to report budget balances. Users can
report on budget, consumption, reservation category,
available fund balances and control budget details.

Subledger Accounting
Oracle Subledger Accounting provides accounting reports for fiscal and internal control
purposes.
The reports are:
• Comprehensive from a financial standpoint.
• Include the best source of information for each type of journal entry.

These reports can therefore be used in lieu of the General Ledger-based journals and account analysis
reports if you need to see detailed subledger journal entries as well as supporting transaction information.

Subledger Accounting Predefined Reports Overview
Oracle Subledger Accounting provides predefined accounting reports for fiscal and internal
control purposes.
• Account Analysis Report
• Accounting Event Diagnostic Report
• Journal Entries Report
• Subledger Period Close Exceptions Report
• Third Party Balances Report
• Subledger Accounting Method Setups Report
• Create Accounting Execution Report

• Supporting References Report
• Multiperiod Accounting Execution Report
Note: No predefined Oracle Transactional Business Intelligence Reports exist for Subledger Accounting.

Subledger Accounting BI Publisher Reports
The following benefits have been added to the Account Analysis and the Journal Entries
reports:
• Report extracts have been enhanced to include reconciliation information for clearing
accounts.
• BIP templates can be customized to list the clearing account reconciliation details.
Title Description
Account Analysis Report Provides drill down information about the movement on a particular account for
a period or range of periods for posted journal entries.
Accounting Event Analysis Report Shows the transaction data used in accounting. The data is collected when the
profile option SLA: Enable Diagnostics is set and the Create Accounting

process is run.
Journal Entities Displays detailed information for subledger and general ledger journal entries;
groups report by ledger, journal source, journal category, and event class at
submission.

Title Description
Subledger Period Close Lists all accounting events and journal entries that fail period close
Exceptions Report validation. Reasons for failure include incomplete transactions, unprocessed
accounting events, invalid journal entries, and journal entries that have not
been transferred. Groups report by ledger, period, journal source, journal
category, and event class at submission.
Third-Party Balances Report Displays subledger balance and account activity information for suppliers
and customers.
Subledger Accounting Method Displays the accounting setups for a subledger application and accounting

Setups Report method.

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

displays entries created by the Create Multiperiod Accounting process.

Subledger Accounting Subject Areas
Subledger Accounting has no predefined Oracle Transactional BI reports. You can use one
of the two subject areas to create your own custom reports.
New dimension folders are added for Sequences and Supporting Reference to report
supporting documents and supporting reference balances.
To simplify the subject area, code columns, such as balance type code and fund status
code, are hidden in the subject area. Instead customers can use related description columns
for these code columns for reporting.
Any existing reports that use these hidden code columns will continue to function. These
description columns have Double Column feature enabled that automatically supports
Multilanguage translation in string filtering.

Title Description
Subledger Accounting – Journals Real Time Real-time information on accounting detail journals.
Subledger Accounting – Supporting References Real-time information on subledger transaction supporting
Real Time reference details.

Practice C-4 Overview: Running a Subledger Accounting BI
Publisher Report
• Submitting the Journal Entries report.
• Viewing the Journal Entries report.


Accounting Hub
Oracle Accounting Hub:

• Provides the following set of accounting tools:
– Oracle General Ledger
– Oracle Financial Reporting
– Oracle Accounting Transformations (Subledger Accounting)
• Provides accounting reports for third-party transactions and for both subledger and
general journal entries.
• The reports are:
– Comprehensive from a financial standpoint.

– Include the best source of information for each type of journal entry.

Accounting Hub Reports
Title Description
Third-Party Balances Summary Displays information for each account of the third party and third-party site,
Report and account identification. This report is a tool for auditing third-party
accounts.
Third-Party Detail and Balances Provides third-party account balances and accounting activity details for a
Report period. You can review the accounting process details by third party and
audit third-party accounts in detail.
Third-Party Account Balance Report Prints account and original third-party transactions impacting the account
during a particular period. The report is run to ensure that subledger and
general ledger balances reconcile, and to identify possible reasons for any
discrepancies.


Title Description
General Ledger and Subledger Prints account balances by account with subledger journal details. The
Account Analysis Report report displays entered amounts, third-party information, sequences,
and total number of debit and credit documents.
General Ledger and Subledger Lists account balances or selected segment balances with subledger
Accounting by Journal Lines Report journal details, including entered amounts, third-party name, journal
source, journal category, and reporting and accounting sequences. Total
number of debit and credit documents is also listed.

Account Analysis by Legal Entity Prints account balances by accounting code combination and selected
Report segments with subledger journal details, including third-party information
and sequences. Flexible grouping and sorting options are provided at
submission.

Title Description
Daily Journals Report Lists subledger journal activity for a given period or date range, journal
FAH source, entered currency, and journal batch. The report prints detailed
subledger journal lines prior to general ledger summarization. Third party
and transaction details are also listed for the journal lines.
Subledger Detail Journal Report FAH Displays information about the posted general ledger journal batches that
originate from Oracle Receivables and Oracle Payables subledgers. The
report prints subledger details like transaction number, transaction date,
and transaction amount in entered and ledger currency.


Title Description
Journal Ledger Report Lists the accounting entries with subledger details like
transaction number, transaction date, and line
description, using flexible sorting options that are
provided at report submission. This report provides a
real audit trail between general ledger and subledgers
to satisfy legal and business requirements.


Summary
In this lesson, you should have learned to:

• Describe the predefined Oracle Business Intelligence Publisher reports.
• Discuss the predefined Oracle Transactional Business Intelligence reports.
• Understand the predefined subject areas.


D96139GC30 sg2

Uploaded by

Document Information

Original Title

Copyright

Available Formats

Share this document

Share or Embed Document

Sharing Options

Did you find this document useful?

Is this content inappropriate?

Copyright:

Available Formats

D96139GC30 sg2

Uploaded by

Copyright:

Available Formats

Oracle Internal & Oracle Academy Use Only

Oracle Financials Cloud: Enterprise

Student Guide – Volume II

Learn more from Oracle University at education.oracle.com

Bruce Ingram Disclaimer

Oracle Internal & Oracle Academy Use Only

1 Introduction to Oracle Cloud Enterprise Structures with General Ledger

Oracle Internal & Oracle Academy Use Only

2 Introducing Oracle Cloud Navigation

Oracle Internal & Oracle Academy Use Only

3 Financials Setup Overview

Oracle Internal & Oracle Academy Use Only

Oracle Internal & Oracle Academy Use Only

5 Discussing the Vision Story and Common Applications

6 Configuring Enterprise Structures

Oracle Internal & Oracle Academy Use Only

Oracle Internal & Oracle Academy Use Only

7 Configuring General Ledger Components

Oracle Internal & Oracle Academy Use Only

Oracle Internal & Oracle Academy Use Only

Oracle Internal & Oracle Academy Use Only

9 Configuring Journal Approval

Oracle Internal & Oracle Academy Use Only

10 Configuring Oracle Intercompany

Oracle Internal & Oracle Academy Use Only

11 Configuring Period Close Components

Oracle Internal & Oracle Academy Use Only

12 Configuring Financial Reporting

Oracle Internal & Oracle Academy Use Only

Oracle Internal & Oracle Academy Use Only

Oracle Internal & Oracle Academy Use Only

Oracle Internal & Oracle Academy Use Only

A Appendix A: Common Application Topics

Oracle Internal & Oracle Academy Use Only

B Appendix B: Implementing Financials for Asia/Pacific and EMEA

C Appendix C: Predefined Reports for General Ledger

Oracle Internal & Oracle Academy Use Only

Configuring Oracle Intercompany

Oracle Internal & Oracle Academy Use Only

After completing this lesson, you should be able to:

Oracle Internal & Oracle Academy Use Only

Oracle Financials Cloud: Enterprise Structures with General Ledger Implementation 10 - 2

The Oracle Intercompany module consists of three areas of functionality:

Oracle Internal & Oracle Academy Use Only

Copyright © 2018, Oracle and/or its affiliates. All rights reserved.

Oracle Financials Cloud: Enterprise Structures with General Ledger Implementation 10 - 3

Oracle Internal & Oracle Academy Use Only

Oracle Financials Cloud: Enterprise Structures with General Ledger Implementation 10 - 4

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

Oracle Internal & Oracle Academy Use Only

Vision Foods Marin Intercompany Payable Vision Stockton Citrus 700

* Example from Manage Intercompany Transactions – Intercompany Balancing Functional Overview

Copyright © 2018, Oracle and/or its affiliates. All rights reserved.

Oracle Financials Cloud: Enterprise Structures with General Ledger Implementation 10 - 5

Journal Ledger Account Debit Credit

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