D96139GC30 sg1

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

Structures with General Ledger
Implementation
Student Guide – Volume I

D96139GC30
November 2018 | D101490
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
1
Introduction to Oracle Cloud Enterprise

Structures with General Ledger Implementation

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

• Use Oracle Functional Setup Manager to implement Oracle Financials Cloud.
• Understand Financial Security.
• Discuss the common applications configuration for Oracle Financials Cloud.
• Describe the configuration of enterprise structures and the related Vision Corporation
story.
• Configure Oracle Financials General Ledger on Cloud.

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

Course Approach
Each lesson in this course:

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

In this course, the instructor:

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

Oracle Cloud Implementation Resources
Classroom and Other Resources:

• Oracle Financials Cloud: Enterprise Structures and General Ledger Implementation
Student guide (this guide and its companion course)
• Oracle Cloud Applications Help in the Applications
• Oracle Technology Library on OTN
• My Oracle Support (MOS)
• Oracle Financials Cloud Library
• Your instructor
• Other students

• Oracle Technology Library on OTN: (http://www.oracle.com/technetwork/index.html)

• My Oracle Support (MOS) (https://support.oracle.com/): Including these documents:
- Getting Started with Oracle Cloud Applications: Common Implementation, Article ID
1387777.1 on Oracle Support
- Oracle Cloud Applications: Financials Reporting (Document 1458904.1)
• Oracle Help Center (http://docs.oracle.com/cloud/latest/financialscs_gs/index.html): Including these
Oracle Financials Cloud books:
- Getting Started with Your Financials Cloud Implementation
- Implementing Enterprise Structures and General Ledger
- Using Common Features for Oracle Applications Cloud (including infolet personalization
topics)
- Customizing the Applications for Functional Administrators (including infolet customization
topics)
- Implementing Financials for Asia/Pacific
- Implementing Financials for EMEA
- Using Oracle Social Network
- Security Reference for Oracle Financials Cloud
- Creating Analytics and Reports for Financials Cloud
- Administering Analytics and reports for Oracle Financials

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

- Administering Essbase Database
- Administering Hyperion Enterprise Performance Management Workspace Enterprise

Oracle Help Center: docs.oracle.com

Oracle Help Center is:

• Central hub for all documentation and tutorials.
• Organized by major product categories including Cloud, Applications, Middleware, and Database.
• Cloud Application pages are organized by Cloud.
Friendly task panel to change focus from Cloud to:
• Applications
• Middleware
• Database
• Other Documentation

Oracle Cloud Application Service Pages

Consistent organization, content, and link format for Cloud service pages.
• Get Started
• Applications
• Videos
• Books

Video Subject Areas on the Oracle Help Center
• Get Started with Oracle Applications Cloud

• Set Up Oracle Applications Cloud
• Customize Oracle Applications Cloud
• Get Started with Oracle Financials Cloud
• Use General Ledger
• Use Subledger Accounting
• Use Payables Invoice to Pay
• Use Receivables Credit to Cash

• Use Other Oracle Financials Cloud Products
• Use Oracle Social Network to Improve Collaboration
• Use Oracle Transactional Business Intelligence for Financials Cloud
Link to the videos: http://docs.oracle.com/cloud/latest/financialscs_gs/financialscs_videos.htm

Use General Ledger includes the following videos:
• Create journal approval rules.
• Create an allocation rule and generate allocations
• Manage intercompany reconciliation.
• Define a basic financial report.
• Add formulas to a financial report.
• Define range functions for a financial report.
• Add grid points of view for a financial report.
• Set the page and grid properties for a financial report.
• Add formatting and graphing to a financial report.
Note: New videos are constantly being added.

Reference Guides
• File-Based Data Import includes links to:

– Spreadsheets templates.
– Load and import processes.
• Tables and Views includes:
– Columns
– Primary and Foreign Keys
– Indexes
• SOAP (Simple Object Access Protocol)
Web Services

Oracle Enterprise Repository has been decommissioned and the following link redirects you to the location
of the new guides:
http://www.oracle.com/webfolder/technetwork/docs/HTML/oer-redirect.html.
Click on the Oracle Help Center Link > Cloud > Financials > Books > guides in the Development section.
• File Based Data Import (FBDI) is used to load data into Oracle Cloud Applications from external
sources, such as legacy systems and third-party applications. The File Based Data Import for Oracle
Financials Cloud Guide includes links to:
- Spreadsheets used to load data into Oracle Cloud Applications from external sources, such
as legacy systems and third-party applications. The spreadsheet templates help to structure,
format, and generate the data file according to the requirements of the target application
tables.
- File-based load process to load the data files into the interface tables.
- Application-specific data import processes to transfer data from interface tables to the
application tables in your Oracle Cloud Applications.
• Tables and Views for Oracle Financials Cloud Guide includes:
- The tables with the basic information about the table columns, primary and foreign keys, and
indexes.
- The views, columns, and query details that are associated with each view.

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

Friendly Search

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

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

Course Schedule
This course is designed to generally follow this agenda:

Day One:
• Introducing Oracle Financials Cloud
• Introducing Functional Setup Manager for Financials
• Exploring Financial Security
• Configuring Common Applications
Day Two:
• Configuring Enterprise Structures

• Configuring General Ledger

Course Schedule
Day Three:
• Configuring General Ledger
• Configuring Journal Approval
• Configuring Intercompany Balancing Rules
Day Four:
• Configuring Period Close Components
• Configuring Financial Reporting
Day Five:

• Configuring General Ledger Options
• Introducing Consolidations
• Introducing Budgets Let’s Begin!
Additional material is provided in the appendixes for your reference.

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

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


Introduction to Oracle Cloud Applications
Oracle Cloud Applications are:

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


• An integrated suite of business applications that:
- Connects and automates the entire flow of business processes across both front and back
office operations.
- Addresses the needs of a global enterprise.
• Engineered to work together, enabling users to streamline the setup process by sharing common
setup data across applications.
• Designed to ensure that your enterprise can be modeled to meet legal and management objectives.
The decisions about your implementation of Oracle Cloud Applications are affected by your:
• Industry
• Business unit requirements for autonomy
• Business and accounting policies
• Business functions performed by business units and, optionally, centralized in shared service
centers
• Locations of facilities

Oracle Cloud Strategy

The Oracle Cloud Applications strategy sets the new standard for innovation with its complete, standards-
based platform and service-oriented architecture, and is built on two main pillars:
• Complete Solutions: Based on a complete and integrated product strategy.
• Complete Choice: Offers customers the option of plugging into other Oracle and non-Oracle
solutions on the Oracle Cloud.
The Oracle applications strategy adapts quickly to changing business needs while lowering integration costs
and other short and long-term costs.
The Oracle Financials strategy provides:
• A complete and integrated financial management solution that sets the foundation for good
governance and consistent growth.
• Tools that help organizations make better decisions, increase efficiency, reduce costs, and continue
innovation.
• A comprehensive solution that supports reporting with the right information at the right time.

Oracle Cloud Applications: Product Families
• Financial Management
• Human Capital Management
• Supply Chain Management
• Project Portfolio Management
• Procurement
• Customer Relationship Management
• Enterprise Governance, Risk, and Compliance Management

Oracle Cloud Applications provide:

• A complete, modular suite of applications. You have a choice of functionality—whether it’s an
individual module, product family, or the complete suite on the Oracle Cloud.
• A broad scope, with a few exceptions, in terms of global coverage.
• Strong support for North America, Western Europe, Asia-Pacific, and Latin America.
• A way to work that matches what end users do through role-based dashboards, embedded business
intelligence, and collaboration tools that dramatically increase productivity and improve decision
making.
• Flexible implementation of applications in a modular fashion using delivery strategies that meet the
customer’s enterprise information technology strategy on the Oracle Cloud.
Oracle Financials helps companies meet their obligations in key areas such as:
• Compliance
• Financial Control
• Regulatory Reporting
• Cost Containment
• Risk Management

Oracle Financials Cloud: Overview
Oracle Financials Cloud is a complete and integrated financial management solution with:
• Automated financial processing.
• Effective management control.
• Real-time visibility to financial results.

Oracle Financials Cloud with Oracle Cloud Applications provides:

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

Financials Cloud: Key Features
• Multidimensional reporting platform.

• Multiple reporting requirements.
• Role-based dashboards.
• Embedded transactional intelligence.
• Imaging integration.
• Spreadsheet integration.
Financials

• Innovative, embedded, multidimensional reporting platform.

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

Implementation Discussion
Discuss the needs for your implementation:

• Scope of the project.
• Schedule and agenda of the project.
• People involved in the project.
• Applications to be implemented.
• Employees.
• Customers.
• Suppliers.

Instructor-led discussion on the students’ implementations.

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

Common Applications Configurations: Overview
• Legal Structure
• Managerial Structure
• Functional Structure

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

Legal Structure

The graphic in the slide shows a typical group of legal entities, operating various business and functional
organizations.
A corporation is a distinct legal entity from its owners and managers. The corporation is owned by its
shareholders, who may be individuals or other corporations. Many other kinds of legal entities exist, such as
sole proprietorships, partnerships, and government agencies.
A legally recognized entity can own and trade assets and employ people in the jurisdiction in which it is
registered. When granted these privileges, legal entities are also assigned responsibilities to:
• Account for themselves to the public through statutory and external reporting.
• Comply with legislation and regulations.
• Pay income and transaction taxes.
• Process value-added tax (VAT) collection on behalf of the taxing authority.
Many large enterprises isolate risk and optimize taxes by incorporating subsidiaries. They create legal
entities to facilitate legal compliance, segregate operations, optimize taxes, complete contractual
relationships, and isolate risk. Enterprises use legal entities to establish the identity of their enterprise under
the laws of each country in which their enterprise operates.

Managerial Structure

Successfully managing multiple businesses requires that you segregate them by their strategic objectives
and measure their results. Although related to your legal structure, the business managerial organizational
hierarchies do not need to be reflected directly in the legal structure of the enterprise. The management
structure can include:
• Divisions
• Subdivisions
• Lines of business
• Strategic business units
• Cost centers

Functional Structure

Straddling the legal and business organizations is a functional organization structured around people and
their competencies. For example, sales, manufacturing, and service teams are functional organizations.
You reflect the efforts and expenses of your functional organizations directly on the income statement.
Organizations must manage and report:
• Revenues
• Cost of sales
• Functional expenses such as research and development (R&D) and selling, general, and
administrative (SG&A) expenses

Common Application Discussion
Discuss the needs for your implementation:

• What is the level of configuration needed to achieve the reporting and accounting
requirements?
• What components of your enterprise do you need to report on separately?
• Which components can be represented by building a hierarchy of values to provide
reporting at both detail and summary levels?
• Where are you on the spectrum of centralization versus decentralization?

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

Common Application Discussion
• Security Structure
– What level of security and access is allowed?
– Are area or local managers and the people that report to them secured to
transactions within their own area of responsibility?
– Are the company transactions largely performed by a corporate department or shared
service center or within each local area?
• Compliance Requirements
– How do you comply with your corporate external reporting requirements and local
statutory reporting requirements?
– Do you tend to prefer a corporate first or an autonomous local approach?

– Where are you on a spectrum of centralization, very centralized or decentralized?

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

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


2
Introducing Oracle Cloud Navigation

Objectives

• Navigate Oracle Cloud Applications.
• News Feed home page layout.
• Predefined aquamarine theme for News Feed home page layout
• Explore dashboards.
• Examine panels.
• Review infolets and infotiles.
• Understand the Financials user experience.

• Describe personalizations.

News Feed Home Page Layout
• Optional default home page layout called News Feed.

• Administrators can set the default home page layout to any of the following:
– Panel
– Banner
– News Feed

News Feed Home page layout is an optional modern theme with an new icon style to go with it.
• The global header icons render in an Outline style..
- Show Help and Access Accessibility Settings are in the Settings and Actions menu.
- Set Help Options task in the Setup and Maintenance work area to enable the help icons that
appear by default on the pages where they are available.
Leads the industry trends by offering a content rich, yet simple to use interface that presents enterprise
information in a news feed layout to help you make informed decisions and take quick actions. Easy
navigation that is consistent across various devices such as desktop, tablet, and smartphone.
When set, this home page contains:
• An Applications section.
• A series of updates with important information that you can view at a glance, such as Things to
Finish, News and Announcements, and Analytics.
• A list of quick actions, if available to quickly perform some key tasks.
To enable the Homepage News Feed unified layout:
• Enable a sandbox.
• Open the Main Menu.
• Open the Configuration group and then select Appearance.
• Navigate to the Themes tab.
• Change the Default Home Layout to News feed.
• Save the change.
• Apply the sandbox.

Sections: Things to Finish and News and Announcements
• Things to Finish Section shows:

– My Work Items
– My Notifications
• Use Show More and Show Less to
toggle between these views.
• News and Announcements Section

shows:

– Employee News
– Active Announcements
Things to Finish section:

• Provides you with a count of any pending notifications that are assigned to you and may require an
action from you.
• A count link named Created by Me lists the approval requests that you have created. Click the link to
navigate to a full list of notifications pertaining to that count.
• Items listed in the Things to Finish section are same as the notifications listed in the global header.
- The list displays the latest notifications first and allows you to scroll horizontally to view more
notifications. You can clear a notification from the list by clicking the Close icon.
- When you clear a notification, the count does not change since no action is taken on the
notification.
News and Announcements
• The News and Announcements section displays all active announcements available to you.
- Click an announcement image to view more details.
- Use the Previous and Next icons to navigate through various announcements.
• When no active announcements are available, this section does not display any content.
• Administrators must create an announcement and add an image to display it in the News and
Announcements section of the home page. If no image is added, only the subject of the
announcement is displayed on the home page.

Analytics Section
• The Analytics section displays:

– A set of infolets.
– Other configurable pages as tabs.
• Use the Refresh link to load or refresh the content in this section when the refresh data
message appears.
– .

In Financials there are currently four choices of Analytics displays:

• Cash Management Infolets
• General Accounting Infolets
• User-Defined Infolets
• Order to Cash Infolets
Use the Infolet list icon at the top of the section to select your infolets.

Navigator
• The Navigator reflects the contemporary look of the News Feed home page layout.
• Some global header features, such as the Watchlist and Favorites and Recent Items are
not available on your home page with the News Feed layout.

The Navigator has:

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

Predefined Aquamarine Theme for News Feed Home Page Layout
• A theme named Aquamarine is part of the predefined themes available for selection on
the Themes page of the Appearance work area.
• 14 predefined themes exist for you to choose from and apply to your application.
• The icon type called Outline is available.

To support the default home page layout, News feed, a theme named Aquamarine is part of the predefined
themes available for selection on the Themes page of the Appearance work area. A wide range of 14
predefined themes exist for you to choose from and apply to your application.
An icon type called Outline is available, which you can set for your existing themes using the Themes page
of the Appearance work area.

Getting Started with Other Themes


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

Navigation Components
User interface features include:

• Welcome Springboard
• Infolets
• Infotiles*
• Panels

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

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

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

Navigate to: Welcome Springboard.

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

Favorites and Recent Items

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

User Interface
Global Area
Panel Tabs
Panel
Section

Navigate to: Financial Reporting Center.

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

General Accounting Dashboard

Navigate to: General Accounting > General Accounting Dashboard.

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

Work Areas

Navigate to: General Accounting > Period Close.

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

Panel
Click on the Tasks icons to open the panel. Use the panel tabs to:
• Access features without leaving the current application.
• Perform searches.
• Run reports. Tasks Panel Tab
Tasks
Panel

Navigate to: Receivables > Billing.

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

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

Search Panel
Navigate to: Financial Reporting Center.

Use the Search panel to perform a local search based on the work area you are currently using. Click on the
Search panel tab to expand the Search panel and perform a search.

Practice 2-1 Overview: Running session warmer scripts
This practice covers Running session warmer scripts.


Practice 2-2 Overview: Getting Started in Oracle Cloud Applications
This practice covers the following topics:

• Signing in to Oracle Cloud Applications.
• Exploring the following user interfaces:
– Global Area including:
— Accessibility
— Help
— Search
— Personalize
— Setting and Actions menu
— Navigator and Welcome Springboard

– Work Area and Panels
– Search
• Signing out of Oracle Cloud Applications.

Infolets versus Infotiles
Infolet
• An interactive container in a simplified user interface that provides key information and
user actions including:
– Refreshing and running processes to update the data.
– Drilling into the details behind the data.
– Changing the displayed views, names, and information.
• Infolets are combined on an Infolet Page that is accessed using a page control dot on
the Welcome Springboard.
Infotile

• A tile component that displays key information about a topic or object as part of a
scrolling strip of information tiles on a specific page.
• Each tile links to a table of detailed information.
Infolets are available for General Ledger, Intercompany, Budgetary Control, and Cash Management.
Note: You can only view those infolets that you have permission to access.
Infotiles are used in the subledgers, not General Ledger.

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

Navigate to: Welcome Springboard.

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

Infolet Repository
The Infolet Repository displays the infolets available for each infolet dashboard.
Infolets Repository Icon

Navigate to: Welcome Springboard > General Accounting Infolets dot.

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

Infolets in the Newsfeed Theme
• Use the Analytics section of the Newsfeed Springboard.

• Use the scroll bar to scroll to the desired infolets.
• Use the Infolets Repository Icon to select or deselect infolets.


Practice 2-3 Overview: Exploring Infolets
This practice covers exploring the various infolets in the Newsfeed theme.


Personalizations Overview
With personalizations, you can:

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


Setting User Preferences

Navigate to: Your username > Set Preferences.

User preferences enable you to set many defaults that affect your user experience. The preferences include
the following tasks:
• Regional: You can set your territory, date format, time format, number format, currency, and time
zone.
• Language: You can set which language you want for your:
- Default Language: The setting that displays the language used at initial sign in.
- Current Session Language: This setting overrides the default language for the current
session only. For example, your default language is set to Spanish and you need to process
several reports in English. Rather than having to set the report language process option for
each report to English, you can set your current session language to English to have all of
the reports’ output be in English.
- Display Name Language: The setting that displays all person names including your own
name in the global area, in a specific language. For example, if your display name language
is Spanish and your name is Alexander, then you see your name as Alejandro.
• Accessibility: You can set the accessibility as the default mode or you can choose to use a screen
reader. You can also set the color contrast to standard or high and you can set the font size to large
or medium.
• Password: You can change your password according to you company’s policy.

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

Structure Work Area
• Enhanced to enable administrators to configure an infolet page as the default landing

page for users.
• Set the Default Landing Page field for an infolet to Yes, No, or Expression Language
(EL) expression.

Navigate to: Configuration > Structure.

The Structure work area enables administrators configure an infolet page as the default landing page for
users.
On the Home Configuration tab of the Structure work area, an administrator can set the Default Landing
Page field for an infolet to Yes, No, or EL expression which allows page authors to use simple expressions
to dynamically access data from JavaBeans components.
Steps to Enable: An administrator can set an infolet page as the default landing page using the Home
Configuration tab of the Structure work area.
Tips And Considerations: The option to set an infolet page as the default landing page is available on the
Home Configuration page for only specific infolet pages.

Recreate Legacy Dashboards Using the Page Integration Tool
For previously created dashboards for hosting third party applications, recreate by:
• Identifying the predefined dashboards using the Structure tool.
• Checking whether you had previously used the dashboards in your application.
• Viewing and copying the URL to the third party application, which you had hosted on
these dashboards, using the Page Composer tool.
• Recreating the pages using the Page Integration tool.
Note: Prerequisite is to activate a sandbox.

Ten predefined menu entries (D1-D10) for 10 configurable pages existed in earlier versions of Oracle Cloud
applications to create and configure your own dashboards for hosting third party applications.
Starting from release 13.18.10 (18C), these dashboards are not longer available because they are not
consistent with the new look and feel of the application.

Saved Searches
Using saved searches, you can:

• Create any number of saved searches.
• Make a default search.
• Have it run automatically.

Navigate to: Journals > Tasks panel > Manage Journals

A saved search captures search criteria and other settings so that you can easily run the same search again
later. These saved searches in the local area aren't the same as those for the global search.
You can change the settings, rename, or delete any of your saved searches.
Some saved searches in the local area are available for you to use as Watchlist items.

Configuring Table Columns
You can perform the following actions on

columns directly from the table:
• Sort data
• Reorder
• Adjust the widths
You can perform the following actions on
columns from the Manage Columns
window:
• Hide or show

• Reorder
Changes to columns become a user
personalization and will persist between
sessions.
Navigate to: Journals > Tasks panel > Manage Journals

From the tables, you can:
• Sort either ascending or descending on a specific column.
• Reorder the columns by dragging them to the desired location.
• Adjust the widths by dragging the side of the column.
From the Manage Columns window, you can
• Hide or show any of the available columns.
• Reorder any of the visible columns.

Practice 2-4 Overview: Using Personalizations

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


Summary

• Navigate Oracle Cloud Applications.
• Explore dashboards.
• Examine panels.
• Review infolets and infotiles.
• Understand the Financials user experience.
• Describe personalizations.


3
Financials Setup Overview

Objectives

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


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

integrated, end-to-end applications
Maintain setup and administration process.
Setup

Deploy
The Oracle Functional Setup Manager facilities initial setup and ongoing maintenance. The Functional
Setup Manager guides you through the ongoing steps including:
• Planning: Identify the offerings you want to implement. Evaluate what functional areas and features
to opt into and prepare accordingly for their setup requirements.
• Opting In: Select the offerings, functional areas, and features that best fit your business requirements
by enabling them.
• Setting up: Use setup tasks to enter setup data necessary for your enabled offerings and functional
areas.
• Deploying: Move your verified setup data from the test environment to a production environment and
deploy to all users to start transaction processing.
• Maintaining: Update setup data or opt into configuration of the functional areas and features as
necessary. Setup Manager.
• The Application Implementation Consultant job role has full access to perform all Functional Setup
Manager-related activities. Other users must include the Functional Setup User role in addition to
other roles or privileges needed to perform specific setup activities.
• For more detailed information about security requirements for Functional Setup Manager, refer to the
Security Reference for Oracle Applications Cloud Common Features guide in the All Books for
Oracle Cloud page of the Oracle Help Center (docs.oracle.com).

Functional Setup Manager Benefits
1
Centralized Setup Guided Process 2
Single interface for all Oracle Task lists guide you through
Cloud Applications. recommended setup.
Easier Management of
Configurable
3 Setup Data 4
Opt into functional areas and
features to fit business needs. No guessing with built-in
prerequisites and dependencies.
5
Setup Data Migration Reporting 6
Export and Import of setup data

Comprehensive reporting for
between environments. setup data validation.
The screenshot of the Offerings shows the wide range of offerings available with Oracle Cloud. All of these
offerings use the Functional Setup Manager, which provides you with many benefits including:
• Centralized Setup: A single interface for all your Oracle Cloud applications.
• Guided Process: The offering task lists guide you through the recommended setup tasks.
• Configurable: An opt in approach to functional areas and features that can be configured to your
business needs.
• Easier Management of Setup Data: The built-in prerequisites and dependencies eliminate
uncertainty and eases the management of setup data.
• Setup Data Migration: The export and import process move setup data smoothly between
environments.
• Reporting: The comprehensive validation reporting exists to help you confirm your setup data is
valid.
Functional Setup Manager also offers the following:
• Standardized application configuration and setup experience.
• Flexible processes for managing setup:
- Setup by functional areas for an adopt-as-you-go approach.
- Implementation projects to manage exception setup situations.
- Upload functionally to enter setup data in bulk.

Key Concepts
Offerings Functional Areas Features

Navigate to: My Enterprise > Offerings.

• Offerings: Functional groupings within Oracle Cloud Applications representing enterprise business
processes that are subscribed and administered as a unit.
• Functional Areas: Functional modules such as business sub-processes within an offering.
• Features: Optional or alternative business methods and practices applicable to a functional area.
Depending on the setup requirements for a feature, you can:
- Select if the feature either applies or it does not.
- Select one choice to apply to the feature out of multiple choices.
- Select many choices to apply to the feature out the multi-choices available.

Review Offerings and Prepare to Opt In
1. Navigate to: My Enterprise > Offerings.

2. Select the Offering you want to
implement.
3. View a detailed description.
4. Check the Status to determine if the
offering is enabled.
5. Use the Opt In Features button to
manage opt in configuration.
6. Optionally, expand the Related

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

Opt into Offering, Functional Areas, and Features
Offering, functional areas, and sub

functional areas are shown in a hierarchy.
1. Check Enable to opt in:
a. A child cannot be enabled unless
the parent is enabled.
b. A non optional functional area is
enabled automatically when the
parent is enabled.
2. Use Edit icon to open Edit Features to
opt into related features.

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

Review What’s New and Opt into New Features After Upgrade
After an upgrade of the Oracle Cloud

applications, go to the New Features page.
1. Review newly introduced features for
your enabled offerings.
2. Enable the Show Help icon to display
the Learn More column.
3. Use the Opt In button to go to the Edit
Features pages to enable the new
features.

Navigate to: My Enterprise > New Features.

Consult additional help topics from the Learn More icon to better understand the new features.

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

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


Manage Setup Data with Complete Transparency to Requirements

Navigate to: Others > Setup and Maintenance

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

Manage Setup Data Your Way Using Flexible Processes
Functional Area Based Implementation Project Based
Utilize functional module based setup for Manage exception cases by using highly
adopt-as-you-go approach. configurable task lists.

Functional Area Based:

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

Manage Setup Data Using Functional Areas
Using the functional areas setup method is

the best practice for configuring your Oracle
Cloud applications.
Begin by:
1. Navigating to the Setup and
Maintenance page.
2. Select the desired functional area.
3. Check the Shared link to see other
offerings sharing this functional area.

Note: All enabled functional areas based on
opt-in configuration of the offering are
displayed.
The offerings you enable determine:

• The order of the setup sequence that helps you avoid data dependency errors.
• The content in the Shared link which indicates if more than one enabled offering contains that
functional area.
• If the setup tasks are mandatory. An asterisk indicates if the functional area has mandatory setup
tasks.

Related Setup Tasks

Navigate to: Others > Setup and Maintenance.

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

Tasks with Scope

Navigate to: Others > Setup and Maintenance.

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

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

tasks you use to implement your Oracle
Applications Cloud.
Using this method, you create an
implementation project to:
1. Generate a list of setup tasks.
2. Assign tasks to various users who are
responsible for managing setup data.
3. Monitor progress of the completion of
the setup tasks.

Navigate to: Others > Setup and Maintenance > Task panel > Manage Implementation Project.
Note: This method is best suited when you have a need to modify the default setup best practices, or
manage setup as a project by assigning responsibility of managing setup data to a broad group of users and
monitor their progress.

Create an Implementation Project
1 Use Create icon.
2 Enter basic information.

3 Select offering and functional areas you want to
implement and then use Save and Open Project
button.
Navigate to: Others > Setup and Maintenance > Task panel > Manage Implementation Projects > Create
icon.
When you create an implementation project:
Generate the initial list of tasks by selecting one of your enabled offerings.
• If you plan to use more than one offering, create a separate implementation project for each one of
them.
• Selecting an offering, which automatically selects the offering’s core functional areas, you may also
select none, some, or all of the optional functional areas of the offering that are also enabled.
Use your selection of the offering and the functional areas as a template.
• A task list hierarchy is generated for the implementation project.
• The task list hierarchy includes the tasks that are associated at the time with your selected offering
and functional areas, and their dependent features that are enabled.
• Within the task list hierarchy, the tasks are organized according to prerequisite and dependency
requirements of the setup data.
Note: Oracle recommends that you enter setup data in the same sequence as the tasks to avoid missing
prerequisite data.

Review and Assign Tasks
1. Review generated task list.

2. Use the Assign Tasks button to assign users to tasks.
– Assigned To column shows the user to whom the task is assigned.
– Due Date column shows the due date specified for the user.

Navigate to: Others > Setup and Maintenance > Task panel > Manage Implementation Project > Assign
Tasks.
You can assign the tasks of an implementation project to the users who are responsible for managing setup
data represented by those tasks.
• Typically, each setup task is assigned to a single individual.
• However, you may also assign multiple individuals to the same task if your implementation project
requires such assignment.
• Each of the individuals has the flexibility to perform the task and manage setup data independently
of the other users assigned to the same task.
If you specify due dates for completing the assigned tasks, you can monitor the progress of the task
assignments and the progress of the overall implementation project. If you assign multiple people to a task,
you can assign the same due date to each person or you can assign a different due date.

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

• Their implementation project.
• An assigned task.
• Scope, if applicable.
• Go to Task icon to enter setup data.

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

Searching for a Task
If you know the name of the task, you can easily perform a search.

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

Rapid Implementation Task List
Define Common Financials Configuration for Rapid Implementation

• Manage Geographies
• Create Chart of Accounts, Ledger, Legal Entities, and Business Units in Spreadsheet
• Upload Chart of Accounts
• Upload Ledger, Legal Entities, and Business Units
• Create Cross-Validation Rules in Spreadsheet
• Create Banks, Branches, and Accounts
• Manage Tax Regimes

• Run Jurisdiction and Rates Upload Program
• Manage Taxes
Note: This is a sample and not a complete list of tasks.
Navigate to: Others > Setup and Maintenance > Task panel > Manage Implementation Projects > Edit your
implementation project > Select and Add icon. Search for %Rapid% to see all Rapid Implementation task
and task lists.
• Use the Define Financials Configuration for Rapid Implementation task list to streamline your setup
configuration to focus only on the critical setup steps. The rapid implementation task list minimizes
the time needed for you to complete your key setups and enable the day-to-day use of Oracle
Financials Cloud.
• The rapid implementation task list includes tasks that are:
- Critical setup tasks for initial setup.
- Setup steps that are required by most users.
• To create an implementation project that includes the Define Financials Configuration for Rapid
Implementation task list, use the Manage Implementation Projects page in the Setup and
Maintenance work area. The application implementation manager can customize the task list and
assign and track each task.
Note: You are not restricted only to the setup configuration in the rapid implementation task list. You can
manually add the standard Financials offering task lists and tasks to your rapid implementation project to
change and update your setup.

Practice 3-3: Accessing Task Lists and Tasks

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


Configure Auditable Setup Attributes and View Audit Report
NE
• Configure setup attributes for audit from the Setup and Maintenance work area.
• Track changes to these attributes using the Audit Report.

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

Audit History Enablement
Oracle Financials Cloud currently supports audit history on several key business objects.
• Individually configure and enable auditing of each business object.
• By default, auditing is disabled for all applications.

Navigate to: Others > Setup and Maintenance > Setup: Financials > Applications Extensions > Manage
Audit Polices.
Steps to enable:
• You must configure the business objects and select the attributes before enabling audit otherwise
auditing remains inactive.
• Ensure that you have a role with the assigned privilege Manage Audit Policies.
• To view the history or to create a report, you must have a role with the assigned privilege View Audit
History.
• To open the Audit History work area, from the Navigator menu, select audit reports.
Tips and Considerations:
• Audit enables tracking the change history of particular attributes of a business object, provided those
objects are selected for audit and auditing is enabled for that application.
• Your configuration settings determine which attributes to audit for a given object, and when the audit
starts and ends.
• Auditing takes into account all the operations performed on an object and its attributes, such as
create, update, and delete.

Manage Setup Data Entry in Bulk

Navigate to: Others > Setup and Maintenance > Actions menu on a task.
Note: If the Action menu is not showing, go to View > Columns > check Actions.
Use a CSV file format based setup data export and import by task as an alternative to entering data using
the user interface. Use this method if:
• You have a substantial number of setup data records with few attributes to enter for a setup task.
• Entering this data using the setup page is cumbersome and prone to errors.
• Functional Setup Manager provides you the ability to export and import setup data for a specific task
that meet these requirements using a CSV file.
Note: Check with the product documentation to validate if a task supports CSV export or import that you
may require.

Export and Import CSV Processes
1. Select a task and use the Action button to create a CSV export file.
– Select whether to export an empty file when creating new data or to export existing
data for an update.
– If Scope is enabled, then optionally filter exported data.
– When the processing completes, download the file and review data.
2. Select a task and use the Action button to create CSV import process.
– Upload the CSV file package containing appropriate data.
– Review the processing results.
– Verify the imported data.

Navigate to: Others > Setup and Maintenance > Actions > Export or Import to CSV File.
These export and import processes can be used outside of the export and import pages in Functional Setup
Manager (FSM) by using the following application programming interfaces (APIs):
• FSM SOAP Service
• FSM REST API
SOAP and REST are two different standards of web services. These APIs are available if you want to utilize
a CSV export and import and invoke the process external to Functional Setup Manager.
• For example, use this method if you are moving to Oracle Cloud applications from Oracle E-
Business or other systems where you have setup data such as legal entities, business units, chart of
account, so on. You can write your own web services to extract setup from your existing systems to
a CSV file, and then leverage these web service APIs to import that data into the Oracle Cloud
applications.
• See the following documents for more details on using these APIs:
- SOAP Web Services for Common Features in Oracle Applications Cloud Guide > Business
Object Services chapter > Setup Data Export and Import topic in the Oracle Help Center.
- FSM: Setup Data Export and Import Service Usage (Doc ID 2156193.1) in My Oracle
Support.

Practice 3-4 (Optional) Managing Setup Data by Bulk Entry Using
CSV Files
• Creating CSV files from the Manage Business Unit task.
• Viewing the CSV files created.


Copying Setup
• Get the benefit of creating multiple copies of complex but similar setups quickly.
• Reduce data entry effort. You only need to:
– Setup one time.
– Make a copy.
– Make changes to the copy as needed.

Navigate to: Others > Setup and Maintenance > Task panel > Copy Configurations.
For example, create a business unit structure and then copy the setup to create a new business unit
structure whose setup data requirements are similar to the original business unit.
• Start the copy process by selecting an existing setup configuration, whose setup data is then copied
to a staging area.
• Modify the setup data in the staging area according to the requirements of the new setup
configuration you want to create.
• Submit an import process which creates the new setup configuration.
• Review your new setup configuration to ensure that the setup meets your requirements.
Note: You can also make additional changes to the imported data, if needed.

Practice 3-5: (Optional) Copying Setup Data
This demonstration covers the following alternative processes to manage setup data:
• Copying setup data from the US1 Business Unit.
• Fixing an error.


Efficient Setup Data Migration
• Export and import setup data by:

– Offerings and Functional Areas.
– Or, Implementation Projects.
– Built-in sequential task list helps to avoid data dependency errors.
• Use Scope to filter and export sub set of data.
• Leverage the Comparison Report before import to avoid unexpected data override.

Navigate to: Others > Setup and Maintenance > Actions > Export or Import.
Almost all Oracle Cloud implementations require moving functional setup data from one instance to another
at various points in their life cycle.
• For example, you might first implement in a development or test application instance and then
deploy to a production application instance after testing.
• You can move functional setup configurations of applications from one application instance into
another by exporting and importing setup data.
Note: The instances need to be at the same code level.

Best Practices for Managing Setup Across Environments
• Enter setup data and verify transactions in Test.

• After setup data passes verification, for example, UAT (User Acceptance Testing):
– Export from Test.
– Import into Production.
TEST
Export and
Import

P2T
(if needed)
PRODUCTION
Note: If Test requires refresh from Production, then use P2T (Production to Test), a reverse production-to-
test process to synchronize the test to production instances before performing incremental setup in the test
instance.

Best Practices for Managing Setup: Using a Gold Copy
1. Enter setup data in Gold.

2. When ready to verify, export from Gold
GOLD
and import into Test.
3. Verify transaction in Test, for example, Export and
using UAT. Export and Import
Import
4. If setup data requires changes, repeat
Export and
step 1 to 3. Import TEST
Offering, if
5. After setup data passes verification, needed
export from Gold and import into
Production.

P2T, if
PRODUCTION needed
• In the next testing cycle, if Test requires a refresh from Production, then use P2T.
• If Gold requires a refresh from Production, then rebuild Gold, export Offerings from Production and
import into Gold. This method brings over setup data from Production into Gold without bringing over
transaction data.
Note: A Gold copy (environment) is an operating standard for many enterprises, particularly large ones. In
this environment, your setup data is maintained as the source of truth or system of record.

How Does Setup Import Manage Data?
• If a record exists in the configuration package, but does not exist in the target, then the
import creates the record.
• If a record does not exist in the configuration package, but exists in the target, then the
import does nothing to the record.
• If a record exists in both the configuration package and the target, then:
– If all attribute values are the same in both, the import does nothing to the record.
– If any attribute values of the record are different, the import updates the record in the
target with the values in the configuration package.
SOURCE TARGET

Export and Upload and
Download Import
Configuration
Package

Export an Offering or a Functional Area
1. Export entire offering or a functional

area for initial migration.
2. Optionally, select scope to filter the
Export entire offering
exported data. for initial migration.
3. When the export completes, download
the file to import.
4. Review tasks related to setup data that
are not be migrated by import.
Export a functional area for
5. Download data reports to verify incremental maintenance.
exported data.

Navigate to: Others > Setup and Maintenance > Actions > Export.
During export, appropriate setup data is identified as follows:
• When you export setup data for an offering, the export definition includes setup data for all enabled
functional areas and relevant features in the offering.
• When you export setup data for a single functional area within an offering, the export definition
includes only setup data for that functional area and relevant features.
The export setup data process generates different reports that you can review in the application or
download for offline review.
Navigate to: Others > Setup and Maintenance > Actions > Export > View All > select your export > Actions >
Download to see the following reports:
• Process Results Summary Report: Shows what setup data was exported, appears in order by
business objects, and includes information on any errors encountered during the export process.
• Setup Data Report: Lists all the setup data in the processed configuration package and includes
individual reports for each business object.
• Process Results Report: Is available as a text file showing the status of an export including detailed
information on the errors encountered during the process.

Create a Comparison for an Offering or Functional Areas
Set up data comparisons to identify the differences between the setup data of two
configuration packages, or two different versions of the same configuration package.
• Use a comparison to learn how data for a given implementation has changed over time.
• Review a comparison to identify the differences among one or multiple business objects
relevant to a configuration.

Navigate to: Others > Setup and Maintenance > Actions > Compare Setup Data.
Three columns display the number of discrepancies:
• In Both With Mismatch: Indicates how many records exist in both sources but have some
differences.
• Only in Configuration 1: Indicates how many records exist only in the first source and do not exist in
the second source.
• Only in Configuration 2: Indicates how many records exist only in the second source and do not exist
in the first source.

Import an Offering or a Functional Area
1. Import an entire offering for an initial migration or a functional area for incremental
maintenance.
2. Upload the exported file.
– The offering or functional area level from export must match.
– Optionally, use a data comparison before importing to avoid accidental override.
– Or, choose to import the feature configuration from the source system.
3. Review and process the displayed tasks, which represent setup data that must be
migrated manually before the import process begins.
4. Resubmit the import process.

5. Review the comparison results and if satisfied, continue to import.
6. When the import completes, review and process the displayed tasks which represent
setup data that must be migrated manually after import.
Navigate to: Others > Setup and Maintenance > Actions > Import.
Use the Import Offering Setup Data page to upload and import previously exported setup data. During
import, a configuration package created by the export process is uploaded.
• All setup data contained in the configuration package is imported into the environment you initiate
the setup data import from.
• The offering and functional area must already be enabled for the implementation before you can
import setup data into the environment.
• In some environments, the feature selection is not selected. Use the feature configuration to ensure
desired features are imported.
• One you initiate the import process, monitor the progress and check the status from the Import
Offering Data History page.

Export and Import an Implementation Project
1. Create a Configuration Package by selecting an Implementation Project.

2. Review business objects such as setup data to be exported.
3. Optionally select scope to filter data.
4. When export completes:
– Download file to import.
– Review tasks related to setup data that are not be migrated by import.
– Download data reports to verify exported data.
5. Upload and then import the exported Configuration Package.
6. When process completes, review import results.

7. Review and process the displayed tasks representing setup data that must be migrated
manually.
Navigate to: Others > Setup and Maintenance > Tasks panel > Manage Configuration Packages > Create
icon.
Use an implementation project as the source for exporting setup data when you are required to modify the
list of tasks or of objects.
• The tasks and their associated business objects in the selected implementation project define the
setup export and import definition for the configuration package.
• Depending on your needs, when you create a configuration package based on an implementation
project, you can also modify some additional aspects.
- Exclude some of the business objects from the configuration you selected to export.
- Change the default import sequence of the business objects.
- Filter the setup data to export.
While the export definition remains the same for each version, the setup data can be different if you modified
the data in the time period between the different runs of the export process.
Because each version of the configuration package has a snapshot of the data in the source instance, you
can compare and analyze various versions of the configuration package to see how the setup data
changed.
Navigate to: Others > Setup and Maintenance > Tasks panel > Manage Configuration Packages > Upload
button.
All setup data contained in the configuration package is imported into the environment you initiate the setup
data import from.

• In the target application instance, the setup import process:
- Inserts all new data from the source configuration package that does not already exist.
- Updates any existing data with changes from the source.
• Setup data that exists in the target instance but not in source remains unchanged.

Practice 3-6: (Optional) Migrating Setup Data
This demonstration covers the following topics:

• Exporting a functional area.
• Viewing the importing a functional area.
• Viewing the Comparison Report to verify the difference between the source and target
environments demonstration.


Learn More: Video Tutorials and User Guides
Video Tutorials • Importing Setup Data from Configuration

• Configure Offerings Packages
• Reviewing and Opting Into New • Export/Import Setup Data Using CSV
Features
• Setting Up Offerings Functional Setup Manager Guide
• Set up Offerings with Scope • Using Functional Setup Manager
• Exporting Offering Setup
• Importing Offering Setup Product Specific Guides
• Exporting Setup Data to Configuration • Getting Started Guides

Packages • Implementation Guides
Link to the Oracle Help Center Financials page:

http://docs.oracle.com/cloud/latest/financialscs_gs/index.html to learn more about Functional Setup
Manager by using:
• The videos listed in the slide are found under the Videos link on the Oracle Help Center Financials
page.
• The Functional Setup Manager guide and other product specific guides.

Summary
In this lesson, you should have learned to:

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


4
Overview of Security

Objectives

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


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

General Accountant Enter and post journals. UK Ledger
Employees View pay slip. Employee’s pay slip only

General Accounting Manager Creates and runs reports. UK Ledger
• Who: The user who performs functions in your company, such as an Accounts Payable supervisor.
• What: Individual actions a user can perform, such as the ability to approve a payables invoice.
• Which: The set of data that the user can perform the action on, such as payables invoices within
your assigned business units.

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

• Roles grant access to functions and
Role
data.
HR Specialist
• Functions and data accessed is Vision Operations
determined by the combination of roles.
Role
User Linda Swift
Employee

Role
Line Manager
For example, user Linda Swift has the following roles:

• HR Specialist Vision Operations
• Employee
• Line Manager
Linda can access her human resource data for Vision Operations, her own employee information, and the
employees and other data related to the area she manages.

Security Reference Implementation
Oracle Financials Cloud comes with a predefined security reference implementation which
consists of:
• A baseline set of predefined security definitions.
– Job roles that closely match real life jobs.
– Duty roles.
• A set of security components that are:
– Delivered with the offering or service.
– Used to meet the business needs of most enterprises.

The security reference implementation covers all functions and actions that need to be secured. The
security definitions are based on industry standards. You do not need to create new job or duty roles. The
implementation includes:
• Complete set of job roles.
• Duty roles and role hierarchy for each job role.
• Privileges granted duty and job roles.
• Data security policies for each job role.
• Policies that protect personal identifiable information.
• Policies enforced across tools and access methods.
• Segregation of duties policies respected in the design of duties for the job role.
• Segregation of duties conflicts.

Job and Duty Roles
• Job roles represent the job that you hire a worker to perform.
• Duty roles represent logical groups of tasks that are performed in a job.
• You can:
– Create custom job and duty roles by copying existing duty roles and job roles.
– Assign job roles to users, not to duty roles.

For example, a job role can enable users to work with journals. A duty role that inherits the job role can
provide access to the journal data within a ledger.
The duty role General Ledger Reporting provides access to all balances and transaction inquiry and
reporting privileges for General Ledger to the General Accountant job role.

GL Predefined Job Roles
• General Accounting Manager: Manages general accounting functions. These roles also
use the General Accounting Manager role and have the same system access level:
– CFO: Top corporate financial officer making appropriation and expenditure decisions.
– Controller: Chief accountant overseeing all accounting functions of the organization.
• General Accountant: Records and reports financial transactions, accounting
adjustments, accruals and allocations.
• Financial Analyst: Provides analysis on the financial performance of the organization.

• General Accounting Manager

- Record and approve journal entries and allocations.
- Create and maintain budgets.
- Perform revaluations and translations.
- Run reconciliations.
- Consolidate financial data.
- Manage period close.
- Inquire and report on financial balances and transactions.
- Create custom queries and reports.
- Manage accounting system reference data and setups.
• General Accountant
- Record journal entries and allocations.
- Enter budgets.
- Perform revaluations and translations.
- Run reconciliations.
- Inquire and report on financial balances and transactions.
- Review accounting system reference data and setups.

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

Privileges
• Roles assign privileges.

• Privileges provide access to functionality in the application.
• For example, the General Accountant Role contains the Manage Journal Activities
Privilege.
• You can assign privileges to roles.


Resources
• Privileges assign resources.

• Resources represent various application artifacts.
• For example, tasks, menu items, buttons, regions, so on.
• You cannot manage or edit resources.

For example, the Manage Journal Activities: Details resource contains the menu items Manage Journals
and other tasks. The Receivables resource contains the prompt for the Billing work area and the Marketing
resource contains the menu prompt for the Campaigns work area.

Data Security Policies
Data Security Polices:

• Control access to data.
• Are granted to a role.
Components of a policy are:
• Database Resource is the table where
data is stored.
• Data Set is where access is granted.
• Condition is used to define the Data Set.
• Actions which are performed on the

data.
Navigate to: Tools > Security Console > Analytics tab > Database Resources tab.
You can review information about data security policies that grant access to a database resource, or about
roles and users granted access to that resource.
Data security consists of privileges conditionally granted to a role and used to control access to the data. A
privilege is a single, real world action on a single business object. A data security policy is a grant of a set of
privileges to a principal on an object or attribute group for a given condition. A grant authorizes a role, the
grantee, to actions on a set of database resources. A database resource is an object, object instance, or
object instance set. An entitlement is one or more allowable actions applied to a set of database resources.
• By default, users are denied access to all data.
• Data security makes data available to users by the following means.
- Policies that define grants available through provisioned roles
- Policies defined in application code
• You secure data by provisioning roles that provide the necessary access. Data roles also can be
generated based on HCM security profiles. Data roles and HCM security profiles enable defining the
instance sets specified in data security policies.
- When you provision a job role to a user, the job role limits data access based on the data
security policies of the inherited duty roles.
- When you provision a data role to a user, the data role limits the data access of the inherited
job role to a dimension of data.

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

• View roles and users that are authorized to the database resource.
• Export the information displayed in the tables.

Navigate to: Tools > Security Console > Analytics tab.

Role Inheritance

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

Security Features Overview
• Security Console • User Account Management • User Password Management:

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


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

• Create and edit custom roles, as well as create and manage user accounts.
• Access the Security Console through the Navigator menu, under Tools or from the
Welcome Springboard.

Navigate to: Tools > Security Console from the Newsfeed theme.
Access to the Security Console is granted through the predefined IT Security Manager role.

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

• Select the User Accounts tab to manage user accounts.
• You can view role analytics, manage certificates, and manage Security Console
administration options.

Navigate to: Tools > Security Console.

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

Compare Roles Feature
• Use to compare the function and data security policies granted between two roles.
• Launch Compare Roles directly by clicking on the button or by choosing the Compare
Roles option in the Search Results.

Navigate to: Tools > Security Console > Roles tab > Search for a role > Compare Roles.
View:
• All comparison results.
• Artifacts that only exist in either the first or the second role.
• Artifacts that exist in both roles.
Choose to view only comparison results for:
• Function security policies.
• Data security policies
• Inherited roles, or combinations.

Move Function and Data Security Policies
• Move function and data security policies from the first role to the second role during role
comparison.
• Export the data displayed in the role comparison results table.
• Note: Add to Second Role button is enabled only on the following conditions:
– Second Role is a user-defined role.
– User has Edit Role privilege.
– Filter Criteria does not include a role hierarchy.
– Show is set to Only in first role.


Manage Data Access for Users Page
All users are assigned an appropriate data set using the Manage Data Access for Users
page.
The Manage Data Access for Users is available to all products in Oracle ERP Cloud,
including:
• Financials
• Procurement
• Project Portfolio Management
• Supply Chain Management
• Incentive Compensation

Navigate to: Others > Setup and Maintenance > Financials > Users and Security > Manage Data Access for
Users
Data assignments are specific to a role, therefore a user must first be assigned to a role before data
assignments can be created in the Manage Data Access for Users page.
• When selecting a role, the selection is limited to the roles that are currently assigned to the selected
user.
• Required data security policies are only present against the corresponding predefined roles.

Automatic Data Provisioning
• Automatically assign data security

contexts to users.
• Occurs at the same time roles are
automatically provisioned to users.
• Automatic assignments are based on
rules similar to role mappings.
• Users acquire a data assignment
automatically when at least one of their
work assignments satisfies the
conditions in the relevant data

provisioning rule and the corresponding
role in the applicable data assignment is
also automatically provisioned.
Oracle Financials Cloud supports:

Automatic provisioning of roles to users.
Automatically assign data security contexts to users at the same time roles are automatically provisioned to
users.
• Automatic assignments are based on rules similar to role mappings.
• Automatic data provisioning occurs if:
- At least one of the user’s assignments matches all data-mapping conditions on a Data
Provisioning Rule
- At least one role is automatically provisioned to the user using Role Provisioning Rules
- The matched Data Provisioning Rule includes data assignments for a role that is
automatically provisioned to the user.
• The process of automatic data provisioning and deprovisioning is very similar to automatic role
provisioning and deprovisioning.
For example: If a worker is hired into the Finance Department of the London office, the worker acquires the
relevant data assignments automatically if:
• An appropriate role provisioning rule exists for Finance Department and/or London office
• At least one of the affected roles in the role provisioning rule is also automatically provisioned to the
user.
Provisioning occurs when you create or update worker assignments. All changes to work assignments
cause review and update of a worker's automatically provisioned roles as well as data assignments.

Users lose automatically provisioned data assignments when they no longer satisfy the data provisioning
conditions.
For example: If a worker is relocated from the London office to another office.
• Data assignments that were automatically provisioned for workers working at the London office are
lost automatically.
• You can also manually deprovision automatically provisioned data assignments at any time.
When you terminate a work relationship, the user automatically loses all automatically provisioned data
assignments, similar to how the user would automatically lose all automatically provisioned roles.
To enable Automatic Data Provisioning:
• First opt-in the feature Data Security Auto-Provisioning for ERP.
• Navigate to: My Enterprise > New Features.
• Navigate to: Setup and Maintenance > Setup: Financials > Manage Data Access for Users task >
Data Provisioning Rules button.

• Once a data provisioning rule is defined users will acquire data assignments automatically when:
- At least one of their work assignments satisfies the conditions in the data provisioning rule.
- The corresponding roles in the applicable data assignments are also automatically
provisioned.
Note
• Automatic Data Provisioning requires the use of Automatic Role Provisioning.
• Data security assignments would only be automatically provisioned to users for roles that are
automatically provisioned to users.

Processes to be Performed on Users and Roles
• Import User and Role Application Security Data: Import user and role data from LDAP
and store in Applications Security tables.
• Retrieve Latest LDAP Changes: Synchronizes users, roles, and role grants with
definitions in LDAP.
• Send Pending LDAP Requests: Manages requests to create or update users, roles, and
role grants in LDAP.

Navigate to: Tools > Scheduled Processes > Schedule New Process.
Lightweight Directory Application Protocol(LDAP): A standard, extensible directory access protocol. It is a
common language that LDAP clients and servers use to communicate.
• LDAP was conceived as an Internet-ready, lightweight implementation of the International
Standardization Organization (ISO) X.500 standard for directory services. It requires a minimal
amount of networking software on the client side, which makes it particularly attractive for Internet-
based, thin client applications.
• The LDAP standard simplifies management of directory information in three ways:
- It provides all users and applications in the enterprise with a single, well-defined, standard
interface to a single, extensible directory service. This makes it easier to rapidly develop and
deploy directory-enabled applications.
- It reduces the need to enter and coordinate redundant information in multiple services
scattered across the enterprise.
- Its well-defined protocol and array of programmatic interfaces make it more practical to
deploy Internet-ready applications that leverage the directory.

Practice 4-1 to 4-2 Overview: Using the Security Console

• Practice 4-1: Copying a role.
• Practice 4-2: Comparing a role.


Practice 4-3 to 4-5 Overview: Creating and Managing User

• Practice 4-3: Creating an employee.
• Practice 4-4: Editing your user.
• Practice 4-5: Managing your user.


Upgrade-Safe Management of Factory Shipped Roles
• You can identify a predefined (factory shipped) Oracle role when viewing the role.
• Predefined Oracle roles are locked and you cannot customize the Oracle delivered
functional and data security policies associated with these roles.

Navigate to: More... > Tools > Security Console > Search for IT Security Manager role > Edit Role.
Predefined Oracle roles are displayed in a different color in the graph visualizer. In the Security Console,
you can identify predefined roles by the ORA_ prefix in the Role Code field.
• Predefined roles can not be changed to add or remove duties.
• Privileges and resources are protected. You cannot create or modify these components.
• Locking down these security artifacts enables safe upgrades to predefined roles, since the possibility
of conflict with customer introduced changes to these roles is now eliminated.
Best solution to update a role or other components, create copies and update the copies instead.

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

• View the privileges, aggregate privileges, or roles assigned to a role.
• View the graph in full screen mode and pan over a specific region in the graph.

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

• To expand or collapse nodes:
- Make a selection in the Expand Toward option to determine whether nodes expand toward
privileges or toward users.
- Select a node and right-click.
- Select one of these options:
• Expand reveals nodes to which the selected node connects directly, and Collapse hides those
nodes.
• Expand All reveals all generations of connecting nodes, and Collapse All hides those nodes.
Note: These options appear only when appropriate. For example, a Collapse option appears only when the
selected node is already expanded.
Enlarging or Reducing the Image
• If the image is large enough, each node displays the name of the item it represents.
• If the image is smaller, symbols replace the names: U signifies user, R signifies role, P signifies

privilege, and A signifies aggregate privilege.
• If the image is smaller still, the nodes are unlabeled.
• Use tools located at the upper right of a visualization:
- Plus: Zoom in (enlarge the image). You can also use the mouse wheel to zoom in.
- Minus: Zoom out (reduce the image). You can also use the mouse wheel to zoom out.
- Circle: Click to activate a magnifying glass. When this feature is active, hover over nodes to
enlarge them temporarily.
- Use the mouse wheel to zoom in or out of the area beneath the magnifying glass.
- Click the circle button again to deactivate the magnifying glass.
- Square: Click to center the image and size it so that it is as large as it can be and still fit
entirely in its display window. Nodes that you have expanded remain expanded.
Enhancing Your View
• Use these techniques to enhance your view of a visualization, or of nodes within it:
- If nodes are labeled with symbols or are unlabeled, hover over any node to display the name
of the user, role, or privilege it represents.
- Click the background of the visualization, then drag the entire image in any direction.

Search in Role Hierarchy Visualization
• You can search and quickly locate security nodes in the role hierarchy visualization.
• You can search for privileges, roles, or users in the visualization.

Navigate to: Tools > Security Console.

On the Security Console, search for and select the user.
• A visualization appears showing the user and any roles that the user inherits directly.
• User and role names appear on hover.
To expand an inherited role:
• Select the role and right-click.
• Select Expand.

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

• Switch between the graphic visualizer view and the tabular view.
• Analyze using a tabular view of direct and indirect assigned privileges for a role.
• Export the data to Excel.

Navigate to: Tools > Security Console > Roles tab > Search for role > select role.

User Account Management
• You can create and manage implementation user accounts within Oracle Cloud
Applications Security.
• You can assign roles to these user accounts.

Navigate to: Tools > Security Console > User tab.

You can also search, retrieve, and manage user accounts automatically created for employees, contingent
workers, supplier contacts, or partner contacts.
The following function security privileges are required for this feature.
• Create User Account
• Delete User Account
• Edit User Account
• View User Account
Job Role Name required is: IT Security Manager

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

– Can disable them if required.
– Enable or disable notifications separately for each user category. NE
Navigate to: Tools > Security Console > User Category tab
• User Categories: For example, employees of your organization using the organization's single sign-
on don't require notifications from the Security Console about creating new users, password expiry,
or password reset. However, the suppliers of your organization who aren't using the organization's
single sign-on, must receive such notifications from the Security Console.
• Note: You can assign a user to only one category.
• Specify Next Url: For example, a user places a password reset request and receives an email for
resetting the password. After the new password is authenticated, the user can be directed to a
website or application. If nothing is specified, the user is directed to Oracle Applications Cloud Sign
In page. You can specify only one URL per user category.
• Notifications: Sent for a set of predefined events. To trigger a notification, you must create a
notification template and map it to the required event. Depending on the requirement, you can add or
delete a template that is mapped to a particular event.
- Can not edit or delete predefined notification templates that begin with the prefix ORA. You
can only enable or disable them. However, you can update or delete the user-defined
templates.
- User Category feature supports both SCIM protocol and HCM Data Loader for performing
any bulk updates.

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

• Create a user category and add users to it.
• Add users to an existing user category.
• Specify the user category for an existing user.

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

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

Navigate to: Tools > Security Console > Administration tab.

User Name Generation Rule and Password Policy by User Category
• Ability to set User Name Generation Rule by User Category

• Rule applies to the users within that user category.

Navigate to: Tools > Security Console > User Categories > Create > Edit.
The User Name Generation Rule was the default rule for all users of a particular implementation.
From this update, you can set the rule on a specific user category. That rule would apply to the users within
that user category.

Password Policies
• You can define policies for password management.

• These policies can define the duration for various password lifecycle events like
password expiration and password warning generation.
• You can set the complexity of generated passwords by choosing from a pre-defined list
of rules.

Navigate to: Tools > Security Console > Administration tab.

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

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

Administrator Password Management
As an administrator, you can:

• Manage passwords of other users using the Security Console.
• Auto-generate or manually enter a password for a user account.
• Define password lifecycle and complexity policies.

Navigate to: Tools > Security Console > Users tab > search for user > select user > Edit > Reset Password.
The password will be automatically validated against the defined password complexity rules and expiration
policies.

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

• If you lock a user account, you will be temporarily preventing the user from logging in
with that user account.
• You can unlock a locked user account.

Navigate to: Tools > Security Console > Users tab > search for user > select user name > Edit > Reset
Password.
You can temporarily inactivate a user account by locking that user account in Oracle Cloud Applications
Security. You can unlock a locked user account.

User Password Management: Self-Service
• You can manage your own user account password using the Security Console.
• The password will be automatically validated against the defined password lifecycle and
complexity policies.

Navigate to: Drop down arrow next to your user name > Set Preferences > Password > Enter your Current
Password, then your New Password, and Confirm New Password > Save and Close.

Password Reset Process
• A notification email is sent to the user who requests a password reset.

• The user is required to click on this link, within a specific period of time, to change the
password.

Navigate to: Tools > Security Console > Administration tab > Notifications > Enable Notifications
Replaces the previous flow where users were required to answer a series of challenge questions to reset
the password.

User Password Changes Audit Report
• You can generate a report that lists password changes made by users.
• The report can be generated for changes made by specific users or for all changes
made during a specific period.

Navigate to: Tools > Scheduled Processes > Run User Password Changes Audit Report.
The following function security privilege is required for this feature:
• Privilege Name: Run User Password Changes Audit Report
• Job Role Name: IT Security Manager

Notification Templates
• You can define or edit custom notification templates for user account life cycle events.
• You can use predefined notification templates.

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

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

Practice 4-6 Overview: Managing Password Security and
Notifications
This practice covers Managing password security features and notification templates.


Bridge for Microsoft Active Directory
• Automatically synchronize user account

information between Oracle Cloud
Applications Security and Microsoft
Active Directory.
• Simplify Single Sign-On by downloading
and installing the Active Directory Bridge
from the Security Console.
• Define mapping attributes using the
Bridge for Active Directory page.

Navigate to: Tools > Security Console > Administration tab > Bridge for Active Directory

Auditing Security
The following audit reports are available:

• User Role Membership Report: List of users and provisioned roles.
• User and Role Access Audit Report: List of users and provisioned function and data
accesses
• Inactive Users Report: List of inactive users.

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

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

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

ERP
Oracle Applications Cloud:
Security Reference for
Common Features
Oracle Financial Cloud Security is applicable to the needs of midsized, horizontal enterprises generally
between 250 and 10,000 employees. It can be changed or scaled to accommodate expansion into vertical
industries such as health care, insurance, automobiles, or food manufacturing.
For more resources on the Oracle Help Center, see:
• Oracle Financial Cloud Security Guides:
https://docs.oracle.com/en/cloud/saas/financials/18c/books.html
• Oracle Cloud Middleware Security Guides:
http://docs.oracle.com/middleware/1221/cross/securedocs.htm

Summary
In this lesson, you should have:

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


5
Discussing the Vision Story and Common

Applications

Objectives

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


Overview
The Oracle Financials Cloud Implementation course is based on a fictional yet realistic
enterprise that:
• Combines the common aspects of your enterprise structure.
• Is used to explore and implement objects during class.

Navigate to: Others > Setup and Maintenance > Financials > Enterprise Profile > Manage Enterprise HCM
Information.

Scenario
• Your company, Vision Corporation, is a multinational conglomerate that operates

primarily in the United States (US) and the United Kingdom (UK). The focus of this class
is on the operations in these two countries.
• Vision Corporation has recently expanded their operations to China and France. In the
future, you will expand to other countries in Europe and around the world.
• Vision Corporation has purchased an Oracle Cloud Applications solution including
Oracle Cloud General Ledger and all of the Oracle subledgers.
• Vision Corporation has 400 plus employees and revenue of $120 million.

Note: The Vision Corporation story is used to demonstrate and teach the functionality in Oracle Cloud
Applications to customers around the globe and does not necessarily represent a real-world implementation.

Scenario Details
• Your product line includes high technology products.

• You have two distribution centers and four warehouses that share a common item
master in the US, UK, and France.
• You are leading the Enterprise Structure team for your implementation project and are
designing the model for your global enterprise structure including your US, UK, and
France operations.

Ready Set Go!!
Consider the following elements in creating your model for your global enterprise structure.
• Your company is required to report using US GAAP Practices, UK Statements of Standard
Accounting Practice, and International Financial Reporting Standards (IFRS).
• Your managers need reports that show profit and loss for their lines of business.
• Your corporate managers require reports showing total organizational performance with drill-down
capability.
• Your company has all administrative, accounts payable, procurement, accounts receivable, billing,
and human resources functions performed at your corporate headquarters.

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

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


Vision Corporation Analysis
• Do you need one or more business units in which to perform all your business functions?
• Do you have a procurement shared-service center to process requisitions and negotiate
supplier terms for your other business units across your enterprise?
• What other aspects of your business affect your enterprise structure?


Vision Corporation Structure Diagram

This is the model that your team has designed. The model uses numerical values to provide a sample
representation of your structure. The model includes the following recommendations:
Create three separate primary ledgers representing your separate legal entities.
• Vision North America Inc.
• Vision France Inc.
• Vision United Kingdom Ltd.
Consolidate results for your high technology business across the enterprise in a corporate consolidation
ledger.
Process all US, UK, and France general and administrative costs processed by the Shared Service Center
Corporate Business Unit.
Demonstration Solution Services instance with the following limitations:
• Due to space, only some of the Vision Corporation entities are shown.
• This version of the demo environment does not include a shared service center. The one shown
here is for discussion purposes.
• This version of the demo environment has data loaded only for US1 LE1 and US1 BU.

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

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

Company Vision France Inc. Yes 311 France Primary Ledger
Currency EUR
Company Vision United Yes 303 UK Primary Ledger
Kingdom Ltd. Currency GBP
The chart in the slide illustrates the enterprise structure of your Vision Corporation entities. The following
statements expand on the data in the chart.
• The enterprise is required because it serves as an umbrella for the entire implementation. All
organizations are created within an enterprise.
• Legal entities are required. Optionally they can be mapped to balancing segment values or
represented by ledgers. Mapping balancing segment values to legal entities is required if you plan to
use the intercompany functionality.
• At least one ledger is required in an implementation in which you record your accounting
transactions.
• Divisions are optional and can be represented with a hierarchy of cost centers or by a second
balancing segment value.

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

Corporate BU
Vision Corporation BSV 103*
Shared Service Center
Payables Department All Entities Cost Center 723

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

Vision Corporation Distribution Structure
Entity Type Entity Name Distribution Structure
Distribution Center US Distribution Inventory Organization

Center
Warehouse Seattle Inventory Organization
Warehouse Atlanta Inventory Organization
Distribution Center EMEA Distribution Center Inventory Organization
Warehouse Bristol Inventory Organization

Warehouse Marseille Inventory Organization
List of Items Common Item Item Master Organization

Master
The chart illustrates the distribution structure of your Vision Corporation entities. The following statements
expand on the data in the chart.
• Distribution centers and warehouses are used to receive and ship the high tech products your firm
sells.
• Item master organization and inventory organizations can be added if you are tracking your inventory
transactions in Oracle Cloud Applications.

Vision Corporation Chart of Accounts Summary

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

Define Geographies
Use the Define Geographies task list to

create and manage geographies used for
real-time address validation and tax
calculation.

Navigate to: Others > Setup and Maintenance > Tasks Panel > Search > Define Geographies.
Managing geographies comprises:
• Geography structures.
• Geography hierarchies.
• Geography validations.
• Address cleansing.
• Geocoding process.

Geographies: Overview
Geographical information is a critical asset that defines and monitors where and how you do
business. You need to:
• Structure and create geographical information associated with your business when you
first set up Oracle Cloud Applications.
• Use this information to facilitate business processes that rely on geographical data. For
instance, you need geographical information to:
– Validate addresses
– Calculate taxes
– Create sales territories

All your geographical information is centrally located and shared with other application
offerings within your company.
Oracle Cloud comes with predefined country names. You need to define the geography structure and
hierarchy of each country associated with your business before working on any process that requires
geographical data. You can do this by either importing geography data or setting it up manually.

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

• Geography Type: A divisional grouping of geographies.
– Geopolitical, for example, city, province, and district.
– Physical, for example, island and mountain.
• Geography structure defines:
– The hierarchy of the geography types or levels.
– How geography types relate to each other for a given geography.
Country Top level

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

Geography Hierarchy
The geography hierarchy establishes a conceptual parent/child relationship between

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

– California
– Redwood City

Geography Hierarchy Example
Because the top level of any geography hierarchy is Country, a geography hierarchy
contains countries and their child geographies such as state, county, and city.

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

Geography Validations
Geography validation determines:

• The geography mapping.
• Validation for a country’s address styles.
• Overall geography validation control for a country.
You can define:
• Multiple address style formats for a country.
• Geography mapping and validation for each of the address style formats.
The No Styles Format address style format is:

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

Manage Geography Validations
Whether the level is validated.

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

Address Cleansing
1. Enter the 3. Verified address

address and click. appears in the
standardized form.

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

Geocoding Process
• Determines the latitude and longitude coordinates for a location.

• Uses latitude and longitude coordinates from spatial services to provide points of interest
to sales representatives, such as customer and contact addresses.
• Is used to display customers in the vicinity of a mobile address.
Longitude

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

Importing Geography Options
You can import geography data using one of the following options:
• Import Nokia geography reference data.
• Import third-party geography data using file-based data import.
• Use the Geography Loader to populate interface tables.

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

Nokia Geography Reference Data Import
• Import Oracle-licensed Nokia data from Nave for those countries where the data is
available.
• Import Nokia geography data using the Manage Geographies task.
– Search for the country.
– Select Import Nokia Data from the Actions menu.

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

File-Based Import
Use the file-based import process if you plan to provide geographic data details in a source
file. The process:
• Reads the data in the source file.
• Populates the interface tables.
• Imports the data into the application destination tables.
The file-based import process includes the following steps:
• Create an external file containing the import data.
• Define an import activity with:
– Import processing details.

– Source data to object attribute mapping.
– Job schedule details.
• Monitor the progress of the import job.
File-based import supports:

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

Managing Geography Lookups
Geography lookup types provide choices related to geographies, such as address validation
methods.
Two extensible geography lookups that you can customize are:
• HZ_GEO_DATA_PROVIDER: Specifies the source of geography data such as user
entered or from third party providers such as TAXWARE.
• HZ_GEO_IDENTIFIER_SUBTYPE: Identifier sub type for geography, for example,
primary and alternate names and codes for each geography.

You can:
• Rename the values or codes for these lookup types.
• Add new extensible codes to these lookups types.

Tax Zone Types and Zones
Zone types and zones define a geographical boundary, based on master geography
hierarchy data, that can be used to create tax or shipping zones.
• Zone types:
– Categorize and group related zones together.
– Can include geographies from anywhere in the world.
– Can be restricted to contain geographies from within a specified country.
– Create before you can define a zone for a geographical.
• Zones are geographical boundaries for a zone type.

For example, you can create a United States Tax zone type, to include various tax zones in the country.
When you create:
• A zone type that is restricted to a country, you can define the geography types or geographies that
can be used to create a zone.
• A zone, you will need to either create the zone under an existing zone type, or you will need to
create a new zone type and then create the zone.

Run Maintain Geography Name Referencing Process
The Geography Name Referencing process:

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

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

Summary

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


6
Configuring Enterprise Structures

Objectives

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


Define Enterprise Structures

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

Sharing Ledger Components Across Oracle Applications
Many components of an accounting configuration are shared with other Oracle Cloud
Applications.

The chart of accounts, calendar, and currencies are called the three Cs because they are the three main
components required to create a ledger. An accounting method is also required and a seeded method is
available.
For example, Payables uses the account structure to record invoice distributions, the accounting calendar to
record the date of the invoice, currencies and rate types to record invoice amounts in different currencies,
and the journal categories and sources to book the accounting entry.

Practice 6-1 Overview: Reviewing Shared Components

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


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

• Create your segment values and hierarchies data in the specified format.
• Identify your legal entities, addresses, and business units.
• Determine your key accounts that are used to track accounting activities, for example,
retained earnings, cash, accounts receivable, accounts payable, and revenue.
• Determine your calendar start date.
• Finalize your primary balancing segment value, legal entity, and business unit
relationships.
• Determine your document and journal sequencing requirements.

Caution: Plan your implementation carefully, including the above requirements, before preparing and
loading your spreadsheet. Some configurations cannot be changed after the spreadsheet is loaded.

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

• Financials rapid implementation task list contains 90+ tasks.
– Critical setup tasks for initial setup.
– Setup steps that are required by most users.
• Rapid Implementation task list includes spreadsheets to quickly create:
– Enterprise structures including legal entities
– Account defaults and financial sequences
– Banks, branches, and accounts
– Taxes

– Fixed assets
– And many more tasks
Use the Define Financials Configuration for Rapid Implementation task list to streamline your setup
configuration to focus only on the critical setup steps. The rapid implementation task list minimizes the time
needed for you to complete your key setups and enable the day-to-day use of Oracle Financials Cloud.
Note: You cannot perform a complete implementation using only the Rapid Implementation task list. You
need to also use the tasks in the standard Financials task list to add and update additional setup data.

Rapid Implementation: Overview
Rapid implementation is used on Oracle Cloud applications and assists you in creating
components in spreadsheets:
• A chart of accounts, legal entities, hierarchies, document sequencing, key account
assignments, a fiscal calendar, account defaulting, and financial sequencing.
• Primary ledgers and business units with assignment of all business functions to use with
your subledgers.

Navigate to: Others > Setup and Maintenance > Tasks Panel > Search > Rapid Implementation > Expand
Define Common Financials Configuration for Rapid Implementation.
Other objects that are included are legal addresses and mapping between legal entities and the primary
business segments.

Rapid Implementation Task List
Define Financials Configuration for Rapid Implementation:

• Define Common Financials Configuration for Rapid Implementation
• Define Financials Security Configuration for Rapid Implementation
• Define Ledger Configuration for Rapid Implementation
• Define Financial Reporting Center Configuration for Rapid Implementation

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

Rapid Implementation Process
The Create Chart of Accounts, Ledger, Legal Entities, and Business Units rapid
implementation task consists of the following steps:
• Enter the data into the spreadsheets.
• Upload the XML files generated from the spreadsheets.
• The deployment process to finalize the chart of accounts configuration is run
automatically.
• Upload the XML files generated from the spreadsheets for the rest of the configuration.

The Rapid Implementation task configures your enterprise structures quickly:

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

Chart of Accounts Components

All of these components in a chart of accounts can be created using Rapid Implementation spreadsheets:
• Chart of Accounts Structure: Defines the key attributes for your chart of accounts, such as the
number of segments, segment sequences, segment names, segment prompts, default value sets,
and segment labels such as Natural Account and Primary Balancing.
• Chart of Accounts Structure Instance: Inherits by default all the attributes of the chart of accounts
structure, meaning that all instances of the same structure share a common shape and have the
same segments in the same order. However, at the chart of accounts instance level, you can
override the default value set assignments for your segments and assign a unique account hierarchy
that determines the parent and child relationships between the value set values. Oracle best practice
is to map your chart of accounts structure to one and only one instance.
• Value Sets: Attached to each segment to provide formatting and validation of the set of values used
with that segment. You can think of a value set as a container for your values.
• Segments: Combine with other segments to create the account combination. Each segment has a
value set attached to it to provide formatting and validation of the set of values used with that
segment.
• Segment Labels: Identify certain segments in your chart of accounts and assign special functionality
to those segments.
• Note: The Management segment label is descoped in V1.

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

What Is a Value Set?
• Controls what types of values can be used in key and descriptive flexfields such as chart
of accounts segment values.
• Determines the attributes of your segments such as length, zero-fill, right-justify,
alphanumeric, and value security.
• Controls how validation is performed. For example, a list of values must be created and
used.

Manage Value Sets

Navigate to: Others > Setup and Maintenance > Tasks Panel > Search > Manage Value Sets.
• Assign one value set to each chart of accounts segment.
• Share the same value sets across multiple charts of accounts to facilitate consolidation if the values
are the same and have the same meaning.
• Use the same value set more than once within the same chart of accounts structure if the same
values are used for the balancing and intercompany segments.
Note
• Changing the attributes of a value set affects all chart of accounts segments using that value set.
• If segment value security rules are applied to the shared value set used for the company and
intercompany segments, problems may arise with intercompany values used to record cross-ledger
transactions.

Assigning Segment Labels
• Segment labels indicate that a segment

is used in a particular manner.
• For example, assign a segment label of
Primary Balancing to a Company
segment to indicate that journals must
balance by company.

Segment labels are assigned as part of the rapid implementation configuration of your chart of accounts
structure. You can review the assigned segment labels on the Manage Key Flexfield Structures page, which
you access using the Manage Structures button on the Manage Chart of Accounts page.
Note: The Management segment label shows in the user interface but is not currently supported in Oracle
Cloud applications.

Balancing Segment Labels
• Ensures that all journals balance by balancing segment value, or by a combination of

balancing segment values if multiple balancing segment values are used.
• Enables you to create balance sheets and trial balances by balancing segment.
• Enables you to define data access security across additional levels.

Three balancing segment labels are available: Primary, Second, and Third Balancing.
• The Primary balancing segment label is required.
• The Second and Third balancing segment labels are optional, and may not be necessary unless, for
example, you need to balance at more than the legal entity level for management reporting.

Cost Center Segment Labels
• Facilitate grouping of natural accounts by functional cost types, accommodating tracking

of specific business expenses across natural accounts.
• Enable combining expenses and head count data into cost centers that are useful for
detailed analysis and reporting.
• Are optional, but required when:
– Using Oracle Assets.
– Storing expense approval limits in Oracle Expenses.

Note: Add a cost center segment if you plan to add Assets or Expenses in the future, because the chart of
accounts cannot be modified.

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


Defining Hierarchies: Overview
• Leverage the common date-effective tree model employed throughout Oracle Cloud
Applications.
• Used in Oracle General Ledger to facilitate:
– Chart of accounts mappings
– Revaluations
– Data access sets
– Cross-validation rules
– Segment value set rules
• Leveraged in:
– Inquiry and Reporting

– Smart View queries
– Allocations
Note: The spreadsheet creates one hierarchy. To create additional hierarchies, use the Generate Additional
Hierarchy button (which appears on the Company and Natural Account sheets) to generate multiple
hierarchies for any chart of accounts segment, either during initial setup or at a later time. Use this button to
create new hierarchies or add new versions to existing hierarchies after your enterprise structures have
been created.

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

Normally, a business unit has a manager, strategic objectives, a level of autonomy, and responsibility for its
profit and loss.

Rapid Implementation Workbook
Begin by downloading the workbook using the Create Chart of Accounts, Ledger, Legal
Entities, and Business Units in Spreadsheet task on the Setup and Maintenance work area.

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

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


Cross-Validation Rules and Segment Value Security Rules
• Cross-Validation Rules:
– Create rules to prevent certain account combinations from being created.
– Define condition and validation filters on the cross-validation rules spreadsheet.
– Assign values using common operators such as equals, between, and is descendant
of.
• Segment Value Security Rules:
– Define security rules and assign the rules to your users’ roles using the segment
value security rules spreadsheet.
– Assign access to segment values using common operators such as equals, between,
and is descendant of.

Navigate to: Others > Setup and Maintenance > Tasks Panel > Search > Create Cross-Validation Rules in
Spreadsheet.
Cross Validation example: Balance sheet accounts are not combined with operational cost centers.

Account Combinations
• Create entire account combinations for your chart of accounts using a spreadsheet.
• Typically, create account combinations when dynamic insertion is disabled to force users
to only use predefined account combinations.
• Create only prevalidated account combinations.
• Use the Import Account Combinations file-based data import process to import and
update account combinations.

Navigate to: Others > Setup and Maintenance > Tasks Panel > Search > Manage Account Combinations >
Create in Spreadsheet button.

Account Defaulting
• Create with your natural account value set values in the Rapid Implementation
spreadsheet.
• Tag natural account values with an extended account type such as Assets – Accounts
Receivable, Assets – Asset Clearing, and Owner’s Equity – Retained Earnings.
– Financial category, which is used to facilitate Oracle Business Intelligence
Applications (OBIA) Reporting, is automatically assigned.
– Tagged natural accounts are used to generate accounts in setup objects, such as
ledgers, bank accounts, asset books, intercompany accounts, receivables system
options, payables common options, and so on.

Legal Entities, and Business Units in Spreadsheet.
• All available extended account types must be assigned to one natural account value. The extended
account types help create default accounts automatically across multiple product setup user
interfaces. For example, Payables and Receivables setup options.
• You should assign an extended account type only to a postable detail-level natural account value,
and you must assign a particular extended account type only to one account. Likewise, a detail
natural account value can be assigned only one extended account type.
• Specify at least one detail account value for the other segments in the chart of accounts besides the
company and natural account segments. The detail account value is used to create the account
combination supplied by default into Oracle Financials Cloud setup objects.

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

• Create document, accounting, and reporting sequences, versions, and assignments for
your ledgers or legal entities, based on your country-specific sequencing requirements.
• Capture country information about your setup to create country-specific defaults for
sequencing.

Legal Entities, and Business Units in Spreadsheet.
For example, sequences are enabled at the legal entity level for countries with such a requirement like
Spain, Italy, and France. Sequencing is not enabled for other countries where sequencing is not required,
for example, the United States. Even if you provide sequencing, the data is skipped.

Rapid Implementation Spreadsheets

The Create Chart of Accounts, Ledger, Legal Entities, and Business Units workbook provides six sheets.
• Instructions: Read the planning tips, loading process, best practices, and recommendations. The
Instruction sheet includes a link to a completed sample data workbook.
• Chart of Accounts, Calendar, and Ledger
• Business Units
• Companies and Legal Entities
• Natural Accounts
• Financial Sequences
For the intercompany segment, no sheet is created. The application uses the value set and values from the
company segment for its value set and values.
Note: If you plan to secure your company segment values using segment value security rules, do not assign
the Intercompany Segment qualifier to the intercompany segment.
Not assigning the qualifier ensures that:
• Your company and intercompany segments use different value sets.
• The Segment Value Security Rules assigned to your Company value set do not affect your
intercompany segment.

Completing the Accounting Configuration
Validate and generate the files using the buttons on the spreadsheet:
• Step 1: Validate data and correct any errors.
• Step 2: Generate Chart of Accounts File.
• Step 3: Generate Ledger, LE, and BU File

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

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

Rapid Implementation Spreadsheet Sample Reports Preview

The preview reports incorporate elements of the Rapid Implementation setup you have provided, including
derivation of the report rows based on the top parent revenue and expense account values you have
tagged.
In addition to previewing the reports that will be automatically generated, you can also validate whether you
have set up your natural accounts reporting hierarchy in a way that aligns to reporting needs because this is
reflected in the sample reports.
If the natural account hierarchy requires adjustments, you can make those corrections now before actually
creating the account hierarchies in the application because this only happens when you finally submit the
accounting configuration in the Rapid Implementation spreadsheet.
Validation Routine
• The validation routine marks errors as actionable items in a Validation Report worksheet that it
dynamically generates for the workbook.
• You can review these anomalies and make the corrections as indicated.
• In the Field column, it notes the item that is an issue, and includes a text hyperlink. Click the
hyperlink to navigate to the appropriate field in the spreadsheet requiring an update.
Tips And Considerations
Use the sample completed Rapid Implementation Enterprise Structure Setup spreadsheet provided in the
Instructions worksheet in the workbook to familiarize yourself with the feature and see the resulting
accounting configuration and generated reports corresponding to the definition in the sample spreadsheet.
Key Resources
The Instructions worksheet in the Rapid Implementation Enterprise Structure spreadsheet contains
important information on how to use the spreadsheet and submit the accounting configuration.

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


Completing the Accounting Configuration
• Upload using the Upload Chart of Accounts task from the Setup and Maintenance work
area to run the upload process for the first file you saved.
• Note that deployment happens automatically after the upload as of Release 11.
• Upload using the Upload Ledger, Legal Entities, and Business Units task from the Setup
and Maintenance work area to run the upload process for the second file you saved.

• In the parameters region of the Upload Chart of Accounts process, select the first file you saved,
XXChartOfAccounts.xml, and submit the process.
• After loading your chart of accounts file, deployment of the chart of accounts is automatic.
Deployment deploys all charts of accounts in the system.
• After deployment is successful, upload the second file you saved
(XXFinancialsCommonEntities.xml) by selecting it in the parameters region of the Upload Ledger,
Legal Entities, and Business Unit process.

Deployment Status
• Edited: The flexfield definition has not been deployed or changes have been made to the
structure, structure instances, or value sets.
• Patched: The flexfield definition has been modified through a patch, but the flexfield has
not yet been deployed, so the patched definition is not reflected.
• Deployed to Sandbox: The flexfield is deployed and available in a flexfield-enabled
sandbox.
• Deployed: The flexfield definition is deployed and available to end users.
• Error: The deployment attempt failed.

Deployment deploys all charts of accounts in the system during each run. To verify that the Deployment
Status has finished, navigate to the Manage Key Flexfields page from the Setup and Maintenance work
area. Deployment stops when an error occurs. You must fix the errors and run the process again until
successful.

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


Other Spreadsheet Uses
• Oracle Cloud Applications deliver extensive spreadsheet integration across multiple

finance functions, allowing finance users to work in a familiar environment.
• Budgets can be uploaded and budget import errors can be corrected by using the
Correct Budget Import Errors spreadsheet.
• Spreadsheets are seamlessly integrated with the applications for high-volume data entry
and one-click uploads.
• In addition, all reports and transactional tables can be exported to Microsoft Excel for
further analysis and easier viewing of large amounts of data.

The following are some examples of where spreadsheets are used in Oracle Cloud Applications:
• General Ledger: Enter account combinations, cross-validation rules, and journals, correct journal
import errors, and upload currency conversion rates within a spreadsheet. You can also upload
budgets and correct budget import errors.
• Payables: Enter supplier invoices and correct invoice import errors.
• Assets: Set up key asset features, such as asset categories, physical locations, asset keys, books,
and category book defaults, prepare asset source lines, and complete asset details within a
spreadsheet and then import them.
• Expenses: Employees can also enter their expense reports in Microsoft Excel. You can enter
employees using spreadsheets too.
• Receivables: Process customer receipts and upload customer data.
• Tax: Configure transaction taxes according to local and international tax requirements.
• Country-Specific Sequences: Generate country-specific sequencing setup using the predefined
country defaults that are based on commonly used, known sequencing requirements.

Enterprise Structures Setup Report

Enterprise Structures Setup Report:

• Validates your enterprise structures configuration.
• Provides the detailed listing of chart of accounts, segments, value sets, ledgers, legal entities,
business units, and account hierarchy information.
• Creates an auditable report in multiple formats such as HTML, PDF, RTF, Excel (*.xlsx), Power Point
(*.pptx), and CSV to improve your offline analysis requirements.
• Runs as a scheduled process with one parameter: Chart of Accounts name.
Report security prerequisites:
• You must be assigned the following job roles:
- GL_General_Accounting_Setup_Review_Duty
- FUN_Enterprise_Structures_Administration_Duty
• The duty roles are assigned with privileges including managing and reviewing accounting
configurations.
• The following predefined job roles have these duty roles assigned:
- Application Implementation Consultant
- Application Implementation Administrator

Diagnostic Tests for Enterprise Structures Setup Data

Welcome page > Click your User Name to open Settings and Actions menu > Troubleshooting > Run
Diagnostics Tests.
You can run diagnostic tests to perform health check and data validation on the following enterprise
structures setup data:
• Chart of Accounts
• Value Sets and Values
• Account Hierarchies Versions
• Accounting Calendars
• Legal Entities and Legal Reporting Units
• Ledgers Setup
To access the Diagnostic Dashboard and perform the diagnostic tests, you must be granted the Application
Diagnostics Regular User job role.
• When you have been granted the role, you can view the link to run the diagnostics tests.
• If you have the Application Diagnostics Viewer job role, you can view the diagnostic test results, but
not run new tests.

Define Legal Jurisdictions and Authorities
Register your legal entities:

• With legal authorities in the jurisdictions where you conduct business.
• As required by local business requirements or other relevant laws.
Additional considerations:
• Define jurisdictions and related legal authorities to support multiple legal entity
registrations.
• Note: When you create a legal entity, the application automatically creates:
– A registration for the new legal entity.
– A main legal reporting unit.

Legal jurisdictions and authorities may be relevant to your Oracle Financials Cloud implementation only if
you:
• Use Oracle Payables and Oracle Receivables.
• Perform tax calculations.

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

countries or a single country, state, county, or parish.
• Examples: French Labor Law, Singapore Transactions Tax Law, and US Income Tax
Laws.
• Types of jurisdictions are:
– Identifying Jurisdiction
– Income Tax Jurisdiction
– Transaction Tax Jurisdiction
Income tax jurisdictions and transaction tax jurisdictions are two distinct jurisdictions, but

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

Legal Authorities: Overview
• A legal authority is a government or legal body that is charged with powers to make
laws, levy and collect fees and taxes, and remit financial appropriations for a given
jurisdiction.
• For example, the Internal Revenue Service is the legal authority responsible for
collecting taxes and the interpretation and enforcement of the Internal Revenue Code of
the United States.

• Legal authority information is printed on your tax reports to meet country requirements, for example,
for India and Brazil.
• Legal authorities are defined on the Manage Legal Authorities page under the Define Legal
Jurisdictions and Authorities for Financials task list.
• Tax authorities are a subset of legal authorities and you define them using the same setup page.

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


Manage Legal Entities

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

Legal Entities Definition
Define a legal entity for each registered company or other entity recognized in law for which
you want to:
• Record assets, liabilities, expenses, and income.
• Pay transaction taxes.
• Perform intercompany trading.
A legal entity has a separate legal identity and conducts aspects of your business for the
following reasons:
• Complying with corporate taxation within local jurisdictions.
• Preparing for acquisitions or disposals of parts of the enterprise.

• Isolating one area of the business from risks in another area.
• Facilitating local compliance.
For example, your enterprise develops and leases properties. You can create separate legal entities for
development and leasing. This would minimize risk across your lines of business.

The Role of Your Legal Entity
The contracting party on any transaction is always the legal

entity.
• Individual legal entities:
– Own the assets of the enterprise.
– Record sales and pay taxes on sales.
– Make purchases and incur expenses.
– Perform other transactions.
• A legal entity must comply with the regulations of jurisdictions in which they register.
• To support local reporting requirements, legal reporting units are created and registered.

If you make purchases and sell to and from companies under your control, define these companies or other
legal entities as customers and suppliers.
• Transactions between legal entities require accounting.
• Accounting for transactions between legal entities under common control (your legal entities) is
called intercompany accounting.
Legal entities can be identified as legal employers on the Manage Legal Entity page. In Oracle Financials
Cloud, the employees employed by the legal employer can be assigned as users.

Legal Entities in Transactions
• Assets and liabilities of the enterprise are owned by individual legal entities.
• Enter legal entities on transactions that represent a movement in value or obligation.
• Ownership provides, under contract law in most countries, that damages can be sought:
– For actual losses, putting the injured party in the same state as if they had not
entered into the contract.
– For loss of bargain, meaning the profit that could have been made on a transaction.

DAMAGES & LOSSES

Legal Entity and Business Units
A business unit that serves your enterprise as a shared service center can process
transactions on behalf of many legal entities. A legal entity can be:
• Explicit on your transactions.
• Inferred from other reference entities that are themselves linked to a single legal entity.

A business unit is a unit of an enterprise that performs one or many business functions that can be rolled up
in a management hierarchy. A business unit can process transactions on behalf of many legal entities.
In Oracle Cloud Applications, use business unit as a securing mechanism for transactions. For example, if
you run your export business separately from your domestic sales business, secure the export business
data to prevent access by the domestic sales employees. To accomplish this security, set up the export
business and domestic sales business as two separate business units.

Legal Entity and Divisions
Divisions

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

Legal Entity and Ledgers
• Use the Define Accounting Configurations task list to specify which ledger a legal entity
uses to perform accounting.
• When several legal entities share a ledger, use a balancing segment value for each legal
entity.

• Assign one or more legal entities to your configuration using the Assign Legal Entities task.
• Assign balancing segment values to your legal entities using the Assign Balancing Segment Values
to Legal Entities task.
• Assign balancing segment values directly to your ledger using the Assign Balancing Segment Value
to Ledger task.
Note: The balancing segment values that are assigned to the ledger represent nonlegal entity transactions,
such as adjustments. If you use legal entities, you must assign balancing segment values to all legal entities
before assigning values to the ledger. The only available balancing segment values that can be assigned to
ledgers are those not assigned to legal entities.

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

Assign balancing segment values.

• If you use a balancing segment to represent legal entities, you should represent each legal entity as
its own balancing segment value.
• If you account for each legal entity in a separate ledger, then no requirement exists to identify the
legal entity with a balancing segment value within that ledger.
• If you want to create consolidated management reporting across legal entities, you can use a single
ledger to represent multiple legal entities. This is possible when the legal entities are governed by
the same legislative requirements, such as operating in the same country.
• If the legal entities are not governed by the same legislative requirements, you may need to store
them in separate ledgers.
• You cannot change to multiple balancing segments after you have begun to use the ledger because
your historical data is not balanced by the new multiple balancing segments.
- Example: A legal entity that operates in France should not be accounted in the same ledger
as a legal entity that operates in Ireland.

Legal Entities and Intercompany Transactions
Transactions that cross legal entities are accounted for as intercompany transactions.
• If you use multiple balancing segments, the total debits and credits must balance, per
balancing segment, per journal entry.
• If needed, balancing lines, using general ledger accounts as specified in the
intercompany secondary and clearing company balancing options, are automatically
added by the application to ensure balancing of journal entries.
• Carefully consider whether to use multiple balancing segments before using a ledger.

Caution
• After a ledger has been used, historical balances are not automatically converted based upon the
selection of additional balancing segments.
• You cannot change to multiple balancing segments after you have begun to use the ledger because
your historical data is not balanced by the new multiple balancing segments.

Legal Entity and Its Relationship to Intercompany Transactions
After you have created transactions for your companies or other types of legal entities, and
assigned values in the appropriate balancing segment to them, intercompany accounting will
maintain balances synchronized between them by:
• Automatic generation of balancing lines as the application creates accounting to record
due to or from legal entity receivables, payables, or both.
• Manual or automatic intercompany balancing journal creation, which books changes to
intercompany accounts by legal entity to balance and clear intercompany amounts.
Receivables

Payables
Post intercompany transactions directly to the General Ledger. Subledger invoicing is not required. Instead,
these transactions get directly transferred and posted to the general ledger. To use this functionality:
• Define processing options.
• Select the intercompany account combinations that are used to create intercompany transactions.
Account combinations for intercompany transactions are derived automatically based upon your
intercompany setup.
• Set up intercompany organizations for your legal entities to limit the number of trading
parties. Intercompany organizations within the same legal entity are also supported.
For example, you can track assets and liabilities that move between your departments within your legal
entities by creating departmental-level intercompany organizations.

Legal Entity and Consolidation Rules
• When you have specified which balancing segments are used by which companies or
other types of legal entities, then define consolidation elimination rules using your
balancing segments.
• Defining consolidation elimination rules creates a relationship between the legal entities
for eliminating intercompany
balances.

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

Country-Specific Legal Entity Sequences
• Meet the statutory requirements in many European and Latin American countries to
sequentially number financial transactions and accounting entries at the legal entity level
without having to implement a single ledger and business unit per legal entity
configuration.
• Meet these requirements even with multiple legal entities tied to a single ledger and
business unit.
• Configure sequencing by choosing appropriate options in the Sequencing region of the
Specify Ledger Options user interface.

Navigate to: Others > Setup and Maintenance > Financials > General Ledger > Specify Ledger Options.
• Set the Sequencing By option to either Ledger or Legal entity to enable document sequencing in
subledger transactions and accounting and reporting sequencing in subledger and general ledger
journals.
• Set the Sequencing By option to none to disable sequencing.
• Set the Enforce chronological order on document date to Yes to generate chronological sequence
numbers. This is enforced only when sequencing is at legal entity level.
• Select the Enforce Document Sequencing option for Payables and Receivables if sequencing is to
be enforced for Payables and/or Receivables transactions. If this option is selected, the transaction
cannot be saved without a document sequence number assigned to it.
Start using legal entity-based sequences, either at year-end or when new ledgers and legal entities are
implemented. You can use Rapid Implementation to automatically complete the sequencing settings based
on your country-specific needs. This includes enabling sequencing for legal entity.

Practice 6-9 Overview: Searching for Your Legal Entity

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


Manage Legal Reporting Units
• Each of your legal entities must have at

least one legal reporting unit.
• When a legal entity is created, a legal
reporting unit with the same name is
automatically created.
• You can define both domestic and
foreign establishments.

Define legal reporting units by:

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

Legal Reporting Units: Points to Consider
Plan and define your legal reporting units at both the local and national levels if you operate
within the administrative boundaries of a jurisdiction that is more granular than country.
For example:
• If the legal entity establishes operations requirements for each local area in a country
that requires reporting of employment and sales taxes locally as well as nationally.
• If you need more than one legally registered location to meet this legal entity’s reporting
requirements in each local area.

Note: Multiple registrations can be associated with a legal reporting unit. However, only one identifying
registration defined with the legal authority used for the legal entity or legal reporting unit can be associated
with the legal reporting unit.

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


Summary

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


7
Configuring General Ledger Components

Objectives

• Manage value sets.
• Review chart of accounts components.
• Manage and publish account hierarchies.
• Maintain segment values.
• Manage cross-validation rules.
• Create account combinations.
• Define calendars and currencies.


Financials Task Lists
Financials:
• Define Common Applications Configuration for Financials Define Implementation Users
– Define Enterprise Structures for Financials
– Define Ledgers
– Define Security for Financials
– Define Approval Management for Financials
• Define Common Financials Configuration
• Define and Maintain Intercompany Processing Rules
• Define Budget Configuration

• Define Financial Reporting
Navigate to: Others > Setup and Maintenance > Tasks Panel > Manage Implementation Projects > FIN
Implementation Project > Financials > Expand list.
To implement optional and more advanced features, use the Financials task lists.
• The task lists are arranged in the order in which the tasks need to be completed.
• The Define Common Applications Configuration for Financials task list contains implementation and
administration tasks.
Note: The list above includes the areas that are covered in this course and is not a complete list.

Accounting Configuration Prerequisites

To manually create a chart of accounts:

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

Creating Chart of Accounts: Considerations
• You must create value sets first and then add the value sets to your structure and
instance.
• After creating the structure and instance and assigning your value sets, create values for
the value sets.

Do not create values in your value set until after the structure and instance creation because some value
attributes, such as Allow Posting or Account Type, are not available.

Define Value Sets
Use value sets to control the characteristics and format of the chart of accounts segments.

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

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

Validation and Value Sets
When you define value sets, you also need to determine how you want to validate your
values.
Independent Validation
• Lists of values are independently displayed when you complete the segment in the
account combination.
• You must use independent validation and the data type of character for your chart of
accounts value sets. This structure enables you to build a hierarchical tree structure from
the values and report on each segment independently.

Note: Table-validated value sets are not supported in Oracle Financials Cloud.
Table and other validation types that are available and used with different types of flexfields, such as
descriptive flexfields or the Asset Category key flexfield, but not with the Accounting Key flexfield, are:
• Format only: Data is entered and not selected from a list.
• Dependent: List of values for which a valid value is determined by the independent value of another
segment.
• Subset: List of values that is a subset of the values in an existing independent value set.

Practice 7-1 Overview: Searching for Your Value Sets

• Finding the value sets created from the spreadsheet.
• Reviewing the values created from the spreadsheet.


Building the Chart of Accounts Structure
The decisions you make when designing your chart of accounts are very important.
• Plan carefully.
• Customize your account structure.
• Choose the number of segments and formatting.

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

Chart of Accounts Structure Attributes
The chart of accounts structure defines the key attributes for your chart of accounts:
• Number of segments.
• Segment sequences.
• Segment names and prompts.
• Segment labels, for example, natural account and balancing.
• Default value sets.

Sample Chart of Accounts Structure
Caution: Remember security is enabled at the value set level and applies to all segments that use that value
set.

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

concatenated total length of 250 characters including the segment separators.
• Limit maximum length of all segments plus the segment separator.
• Define each segment name and sequentially order the segments, starting with 1.
• Use a default value set, which can be changed at the instance level.

Best practice is five to nine segments. Avoid total concatenated lengths of over 28 to 30 characters as you
can have problems with the chart of accounts truncating on some predefined reports and it complicates data
entry.

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

• By default, inherits all the attributes of the chart of accounts structure, meaning that all
structure instances of the same structure:
– Share a common shape.
– Contain the same segments in the same order.
• Permits overriding the default value set assignments for your segments.
• Determines whether dynamic insertion is enabled to generate new account combinations
dynamically instead of you creating them manually.

Optionally, assign unique hierarchies to create relationships between the value set values for each segment
in the instance by the assignment of a tree code to the value set associated with the chart of accounts
instance segment.
Different value sets and values are required to meet local and statutory reporting requirements.
At the chart of accounts structure instance level:
• Optionally, override the value sets provided by default from the chart of accounts structure.
• Assign a value set with the same segment type and length to each segment.
• Create hierarchies for each segment to meet financial reporting requirements.
• Assign a tree code to each instance segment to indicate the source of the hierarchy information for
the associated value set.

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

account combination.
• You can use these descriptive labels to complete journal entries.

Example above: Navigate to General Accounting > Journals > Tasks > Create Journal.
• You can enter account segment values faster and easier by using account shorthand aliases during
entry of journals and other accounting transactions.
• The account aliases allow you to complete journal entries by selecting descriptive labels instead of
remembering complex account combinations.
• The underlying account segment values default automatically into the data entry fields. Using this
feature minimizes data entry errors, eliminating the need to correct or reverse journals.
Steps to Enable Account Shorthand Alias
• Navigate to: Setup and Maintenance > Tasks Panel > Search > Manage Key Flexfields > Manage
Structure Instances to have the application implementation administrator enable the shorthand alias
feature.
• Redeploy the chart of accounts structure.
Note: The list of values of eligible Chart of Accounts instances appears in the Manage Shorthand Aliases
page, only after these two earlier steps have been completed.
• Navigate to: Setup and Maintenance > Financial Reporting Structures > Manage Shorthand Aliases
page in Functional Setup Manager, select your chart of accounts structure instance, and click the
Search button to view existing aliases.
• Click the Add (+) icon to add new aliases.

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


Define Segment Values
Enter valid values for each segment after adding them to the chart of accounts structure and
structure instance.

• Each value is defined with a name, description, and optionally a start date and end date.
• Navigate from the Setup and Maintenance work area to the Manage Chart of Accounts Value Sets
page.
• Click the Manage Values button to enter values for each segment. These are the values that you use
when building your account combinations.
• Enable the segment value. The period of usage must fall within the start and end dates if entered on
the value.
• You can use the Import Segment Values and Hierarchies file-based data import (FBDI) to upload
segment values from external sources into Oracle General Ledger.
• Note: Sort Order is not used with the Accounting key flexfield.
Caution
• When creating a new chart of accounts with new value sets, create the value sets definition first and
leave the values creation until after the creation of the instance and structure.
• Creating values before assigning the value set to the account structure restricts the ability to define
the required attributes on the values and makes them unusable for the chart of accounts.

Assign Segment Attributes
• Assign attribute options for your

segment values.
• Attributes appear based on the segment
label options assigned to the segments
during chart of accounts creation and
vary by segment.

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

• Account Type:
- Define an account type for each natural account segment value.
- Select the type of proprietary account: Asset, Liability, Owners' Equity, Revenue, Expense,
Budgetary Debit, Budgetary Credit.
- Select either Asset or Expense for statistical accounts. If you enter Asset, the balance in the
account carries forward year to year. If you choose Expense, your statistical balance zeros-
out at the end of the fiscal year.
- Do not change the account type for a value that has been used or has a balance without first
consulting Oracle Support.
• Third Party Control Account: Subledger Accounting maintains the account balance for third party
control accounts by ledger, period, account combination, Party, and Party ID.
• Reconcile: Enter Yes for Reconcile to allow reconciliation for natural accounts that should balance to
zero. (Not supported in Oracle Cloud V1). For Clearing Accounts enter Yes for Reconcile to make
them available for automatic or manual reconciliations using Clearing Accounts Reconciliation.

• Financial Category: Financial Category is used with Oracle Transactional Business Intelligence
reporting to further identify groups of accounts. This is required if you want to run the Payables to
General Ledger Reconciliation report or the Receivables to General Ledger Reconciliation report.

Control Accounts Benefits
• Error prevention: Prevent users from

entering data from unauthorized
sources.
• Improved data integrity: Allow only
approved sources to post to an account.
• Streamlined reconciliation: Enforce
consistency between the source system
and the GL account balance by not
allowing you to enter GL journals
against control accounts.

You cannot enter GL journals against control accounts because that would make the source system and the
GL system out of balance.

Control Accounts Explained

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

Practice 7-5 Overview: Entering Values

• Adding new values.
• Setting value attributes.


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

• Each hierarchy can have multiple versions.
• Financial results from any accounting period can be analyzed by using any version of
any account hierarchy.

• Create account hierarchies (trees) to identify managerial, legal, or geographical relationships among
your value set values.
• Define date-effective tree versions to reflect organizational changes within each hierarchy over time.
• Publish multiple hierarchies to balances cubes to allow for financial reporting and analysis of past,
present, or future data.
• You can use the Import Segment Values and Hierarchies file-based data import to upload
hierarchies from external sources into Oracle General Ledger. Note: Oracle Cloud Applications offer
ready-to-use integration with Oracle Hyperion Data Relationship Management (DRM) for
management of chart of accounts reference data including segment values, business rules, cross-
validation rules, and hierarchies. If you decide to implement DRM integration with Oracle Cloud
Applications, chart of accounts values and account hierarchies (trees) are maintained in DRM rather
than in Oracle Cloud Applications.

Account Hierarchy Purposes
Create multiple hierarchies for different purposes. For example, define three different
hierarchies to be used for each chart of accounts segment that has rollups, each for a
particular purpose:
1. Hierarchies for financial reporting: Must be published to Essbase cubes.
2. Hierarchies for allocations: Must be published to Essbase cubes.
3. Hierarchies for cross-validation rules, revaluation, and chart of accounts mapping: Do
not publish to the Essbase cube because multiple child assignments are not supported
in the Essbase cube.

• Hierarchies for financial reporting: Child values in these hierarchies cannot roll up to different parents
within a hierarchy because this functionality is not supported when you publish such hierarchies to
Essbase.
• Hierarchies for allocations: Used with Calculation Manager in creating allocation rules.
• Hierarchies for cross-validation rules, revaluation, and chart of accounts mapping:
- Are created within the same hierarchy and must be associated with a chart of accounts
instance.
- Associate only one hierarchy with a chart of accounts instance, per segment.
- Can have the same child roll up to different parents.
- Are not available for reporting and allocations.

Account Hierarchy Example

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

Create Account Hierarchies
Use the Manage Account Hierarchies page to search for, create, and edit account
hierarchies.
To create a hierarchy:
1. Click the Create Tree icon to open the definition of the tree.
2. Enter the name, code, tree structure, and description for the tree.
3. Enter the data source parameters to designate the value set and whether parent or
detail values are used in the hierarchy.
Note: You can use the Rapid Implementation spreadsheet to create account hierarchies, as
discussed in the previous chapter.

Note: The Rapid Implementation spreadsheet can be used to maintain and create hierarchies.
The spreadsheet automatically:
• Creates two versions of your hierarchy (Baseline and Current).
• Runs the flattening and auditing programs.
• Sets their status to Active.
• Publishes all hierarchies for you.

Create Account Hierarchies Version
1. Search for the tree you just created to add a tree version.
2. Enter the name, description, and effective start date for the tree version.
3. Select the data source values to use.
4. Use the Audit Results section to start the Audit process to verify the correctness of the
tree.
5. Use the Column Flattening and Row Flattening features in the Actions menu to:
– Optimize parent/child relationships.
– View information for run-time performance that is stored in an additional column in a
table for all parents of a child.

6. Use the Set Status feature in the Actions menu to set the status to active and activate
the hierarchy.
Note: You can create additional tree versions from the Rapid Implementation Enterprise Structures
spreadsheet.

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

Manage Account Hierarchies: Specify Nodes

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

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

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

Publish

Implementation Considerations
Submit the Publish Chart of Accounts Dimension Members and Hierarchies program to
update the balances cube for chart of accounts value set and hierarchy changes.

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

Single Account Hierarchy
Only a single tree version, V1, exists when a financial report is defined.
• The tree version includes the chart of accounts value 500 for a cost center.
• The path does not include a tree version name, because only one tree version is in the
cube.
• The fully qualified name path will be 500.

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

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

• The fully qualified member name path changes because two versions are now available.
– [All VF Cost Centers-V1].[999].[500]
• Any configurations in financial reports, allocations, and Smart View queries that
referenced the original fully qualified name path 500 must be updated to use either of the
following new names:

The fully qualified member name path for a member may change if you originally published a single
hierarchy to a cube and later published another hierarchy that includes the same chart of accounts value.
If the fully qualified member name path changes, you must update existing financial reports, allocation rules,
and Smart View templates that refer to that member. Otherwise, such processes will have errors.
Important: Creating two hierarchies in the beginning eliminates the need to update your reports and rules.
For more information, see: Oracle General Ledger Hierarchies: Recommendations and Best Practices (Doc
ID 1520970.1) on My Oracle Support.

Troubleshooting
Issue Possible Resolution

Tree Version Audit • Make sure parent values have the summary attribute set correctly.
Process Fails When • Make sure you did not mistakenly assign children to child values.
Activating Version.
• Fix could be as simple as switching the summary attribute flag.
However, if you mistakenly made a parent value a child value and
posted transactions to that account, then a more intensive data fix may
be required.
Tree Hierarchy Defined • Submit the process to propagate and update required account
in Oracle General hierarchies to the Essbase GL balances cube from the Publish Account
Ledger is not Available Hierarchies page.
in Essbase General • Check that the Publish option is enabled for the versions that are to be

Ledger Balances published.
Cubes.
• Check that a request ID is returned and the process completes
successfully after you click the Publish action button.

Troubleshooting
Issue Possible Resolution

Error in Publish Account Make sure all users sign out of Financial Reporting, Smart
Hierarchies or Publish Chart of View, and Calculation Manager during the submission of the
Accounts Dimension Members publish process. You cannot have users connecting to the cube
and Hierarchies programs. while running these programs.
Need a new accounting scenario • New scenario members are added in the predefined value
member to load budget and set called Accounting Scenario.
forecast data into Essbase GL • Query this predefined value set, and add a new value for
balances cubes. each budget or forecast that needs to be tracked in Essbase
GL balances cubes.
Enabled or disabled flexfield • Enabled or disabled flexfield security policies are not

security policies are not in effect automatically applied to the Essbase cube if set up after the
for Essbase GL balances cube. cube was created.
• Account hierarchies must be republished in order to apply
newly enabled or disabled flexfield security policies.
Note: Flexfield security is enabled and disabled in the Manage Value Set page.

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


Enabling Account Combinations
• New account combinations are always enabled.

• An account combination cannot be deleted.
• To discontinue using an account combination, deselect the Enabled check box for the
account combination or use the To Date to end date the account combination.
• The From Date is used to enable an account combination as of a particular date.

For example, if you have a new department as of January 1, 2014, you can create an account combination
with a From Date of 01-JAN-2014 and the account combination becomes enabled on that date. This
functionality enables you to create the account combinations in advance.
To create an account combination, navigate from the Setup and Maintenance work area to the Manage
Account Combinations page. Additionally, you can set the following attributes from the Manage Account
Combinations page:
• Preserve Attributes: To prevent changed segment values from overriding values defined at the
account combination level when running the Inherit Segment Value Attributes process.
• Type: To identify the type of account - Asset, Liability, Revenue, Expense, and Owner’s Equity.
• From and To Dates: To enable or disable the account combination on a specific date.
• Allow Posting: To use the account for transactions and journal entries.
• Alternative Account: To use an alternative account combination when this one is disabled.

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


Manage Segment Value Attributes
Oracle General Ledger eases chart of accounts maintenance by automatically replicating

changes to segment value attributes of the account combinations that contain that segment
value.

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

Segment Value Security
• 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.

When you have access to secured account values, you can view and use those secured values across all
modules of the applications where there are references to accounting flexfields including:
• Transaction entry pages
• Balances and transactions inquiry pages
• Setup pages
• Reports
Navigation to Segment Value Security Rules : Setup and Maintenance > Financial Reporting Structures>
Search for Manage Segment Value Security Rules in All Tasks search region

Defining Segment Value Security Rules
Set up segment value security rules to:

• Secure a value set to deny access to all values by default.
• Create conditions and assign the rules to specific external roles to control access to your
segment values. The roles should be created solely for the purpose of segment value
security. The roles are then assigned to users.
• Restrict data entry, online inquiry, and reporting to specific values by using segment
value security rules.
For example, create a segment value security rule that grants a user access only to his or
her own department.

Note: Segment value security is enforced in Oracle Cloud Applications wherever the chart of
accounts values are used.
On setup pages, you can still view referenced account combinations with secured account values, even if
you haven't been granted access to those secured values. However, if you try to update such references,
you can't use those secured values. On reports, you can view balances for secured account values only if
you have access to those secured values.
A distinction between setup and transaction user interfaces is that segment value security prevents you from
seeing certain account values in transaction user interfaces, but you can still see the account combinations
with the secured values in setup user interfaces.
• If you try to update the field in the setup user interface, you won't be able to use those values.
• For transaction, balance, and activity query user interface, segment value security prevents both the
viewing and using of the secured values.
• Segment value security control is both for Read and Write access control.
Note: You can enforce segment value security for inquiries and reporting based on any hierarchy, even
hierarchies that aren't published to the reporting cube.

General Points About Segment Value Security
• Specifies that data security be applied to the values in the segments that use the value
set.
• Applies at the value set level. If a value set is secured, every usage of the value set in a
segment is secured.
• Applies only to independent value sets.
• Applies mainly when data is being created, or updated, and to account combination
tables for query purposes to.

Co CC Acct I/C
For example:
• If the same value set is used for the balancing segment and intercompany segment of a chart of
accounts, then the same security rules apply to both.
• If you create a security rule that only allows you to access balancing segment value 01, then you are
able to only perform intercompany transactions against company 01.
• If you enable segment value security rules by balancing segment, you must use two different value
sets for the company and intercompany segments.

Segment Value Security Implementation

Prerequisites:
• To work with the Security Console, you need the IT security Manager role assigned to your user
setup.
• To work with value sets and profile options, you need the Financial Application Administrator role.
• Set the Security Console Working App Stripe Profile to fscm.
• Set the Enable Security Polices and User membership Edit profile to Yes.
To define segment value security roles:
• Create segment value security roles.
• Enable security on the value set.
Note: You can enable security only on values sets with a type of Independent.
• Create conditions for the rule.
• Create policies to associate the conditions with the role.
• Deploy the accounting flexfield.
• Publish the account hierarchies.
• Assign the role to users.
Whenever you assign segment value security roles to a user, the rules from the user's assigned roles can
be applied together.
• All of the segment value security roles assigned to a user pertaining to a given value set are
simultaneously applied when the user works with that value set.

• For example, one rule provides access to cost center 110 and another rule provides access to all
cost centers.
• A user with both of these segment value security rules has access to all cost centers when working
in a context where that value set matters.

Segment Value Security Examples
Security Segment Value

Condition Security Role Security policy
Associated with
Cost Center Accounting the Cost Center
Equal to Cost Center – Value Set
Accounting SVS Role
Example
Security Segment Value

condition Security Role Security policy

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

Segment Value Security Operators
Operator Usage
Equal To Provides access to a specific detail value. You cannot
use this operator to secure a parent value.
Not equal to Provides access to all detail values except the one that
you specify. You cannot use this operator to secure a
parent value.
Between Provides access to a range of detail values.
Is descendant of Provides access to the parent value itself and all of its
descendants, including mid-level parents and detail
values.

Is last Descendant of Provides access to the last descendants (that is, the
detail values) of a parent value.
Use any of the following operators in your conditions to secure your segment values.
Note: For Is descendant of and Is last descendant of:
• Specify an account hierarchy (tree) and a tree version to use this operator.
• Understand that the security rule applies across all the tree versions of the specified hierarchy, as
well as all hierarchies associated with the same value set of the specified hierarchy.
• For the Tree Operators field, you can only select Is a las descendant of or Is a descendant of.

Conditions
• Segment value security rules do not need a condition if:

– The rule provides access to all segment values.
– Segment values security rules provide access to single nonparent segment values.
• You can define:
– A policy to cover all values.
– A policy to cover a single nonparent segment value provided:
— You know the internal ID for that segment value.
— If you do not know the internal ID, you can create a condition for that single segment
value.
• Matching to all conditions means that all conditions apply simultaneously.

• Matching to any condition means that any of the conditions would apply.
The Row Set field determines the range of value set values affected by the policy.
• If Multiple Values is selected, a condition must be specified.
• If ALL Values is selected, then the policy grants access to all values in value set and no condition is
needed.
• If Single Value is select then the internal Value ID for the Segment value must be specified and no
condition is needed.
Note
• Match All can be used only in the case where there is a single row defined in the Conditions table.
• Match Any can be used in the case where multiple rows are defined in the Conditions table.

Implementing Segment Value Security
In Security Console:
• Create a role by giving it a
name.
• Use an underscore between
each word in the name.
• Define a user-friendly display
name with a hyphen before the
SVS role.
For example, define a name of
ACCOUNTING_COST_CENTER-

SVS_ROLE and a display name
for the Accounting Cost Center-SVS
role.
For segment value security roles, the best practice is to give them a common suffix, such as SVS (segment
value security), to more readily identify them. You can assign these custom roles a role category of Default.

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

Segment value security rules:

• Are specified for a particular value set.
• Work directly or indirectly with the balances cube.
The following General Ledger features are based directly on the balances cube:
• Inquire on Detail Balances
• Account Monitor
• Account Inspector
• Financial Reporting
• Smart View
• Allocations
All other General Ledger features are just indirectly based on the balances cube.
Note: Balance cube security for a data access set is defined as either:
• Full Ledger.
• All Values, in the case of the Specific Balancing Segment Value access type. These will be treated
as the user having access to all values of the balancing segment value set.

Cross-Validation Rules
• Prevent the creation of invalid account combinations by setting up cross-validation rules.

• Define cross-validation rules before entering account combinations.
• Use cross-validation rules in combination with dynamic insertion.

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

Cross-Validation Rules: Considerations
• Validate and apply only to new accounts. You should define and enable cross-validation
rules prior to entering accounts.
• Do not affect existing accounts.
Note: Revise cross-validation rules at any time, but remember that they prevent only the
creation of new invalid account combinations.

Navigate to: Others > Setup and Maintenance > Financial Reporting Structures > Manage Cross-Validation
Rules or Create Cross Validation Rules in Spreadsheet.
Cross-Validation Rule Violations Process:
• List and optionally disable account combinations that violate cross-validation rules for a given chart
of accounts
• Preserve attributes of account combinations to prevent the Inherit Segment Value process from re-
enabling them
Navigate to: Tools > Scheduled Process > Schedule New Process > Manage Cross-Validation Rule
Violations Process

Dynamic Combination Creation Allowed
• Enable this feature to permit users to create new account combinations as they enter
data.
• If the feature is not enabled, you can enter only new account combinations of segment
values using the Manage Account Combinations page.
• Cross-validation rules are important even if this feature is not enabled to prevent
creation of invalid combinations accidentally.

Navigate to: Others > Setup and Maintenance > Financial Reporting Structures > Manage Chart of Account
Structure Instance > Search > Manage Structure Instances button > Create.
When setting the Dynamic combination creation allowed option, consider the following features.
• You can allow account combinations to be added automatically as you enter them in transactions,
including when you define a ledger. Alternatively, you can require all accounts to be defined
manually in the Manage Account Combinations window.
• Frequently, companies enable Dynamic combination creation allowed while they are entering
historical data from a legacy system. They then disable the feature to ensure tighter control over the
creation of new account combinations.

Filters Overview
Use Condition and Validation filters:

• To narrow down the search the application has to do before performing validation.
• To determine whether an account combination is created.

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

Filters and Conditions
The following operators are available for both the Condition Filter and the Validation Filter:

Rules.
Note: In the Create Cross-Validation Rules spreadsheet, you cannot select some operators. The following
operators are only supported. The application substitutes the operator if:
• A detail value is provided: Equals operator.
• Two values are provided separated by a hyphen (-): Between operator.
• A parent value is provided: Is Descendant Of operator.
• To specify that a detail value should not be selected, prefix the value with the less than and greater
than symbols <>.

Practice 7-9 Overview: Defining Cross-Validation Rules

• Creating a new cross-validation rule.
• Adding a condition to the rule.
• Adding a validation filter to the rule.
• Testing the rule.


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


Accounting Calendar Considerations
• Foreign currency translations cannot be performed in the initial period opened for your
ledger.
• Select the earliest period carefully. After you open the first accounting period, prior
periods cannot be opened.

When the next accounting period is opened, Oracle Cloud Applications roll balance sheet account balances
forward to the new period where the beginning balance is taken from the ending balance of the prior period
except when the new period crosses fiscal/calendar years.

Start Date
• Start Date specifies a calendar start date that is a full year before the start date of the
year of the first translation period for your ledger.
• Remember that translation cannot be run in the first period of a calendar.
– Translation requires that the first period that is translated for the ledger must be at
least the second defined period in the ledger's calendar.
– Translation derives an opening balance based on the prior period's ending balance.

Important
Consider how many years of history to load from your previous system. Calculate the start date back to one
period before the beginning of the history.

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


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

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

— Week2-11
— Through Week52-11

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

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

December 31
Period Name Format Section: Examples

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

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


Calendars with Different Period Frequencies
The application generates the period names, year, and quarter number.
• For example, select the period frequency of Other and enter 52 as the number of periods
when you want to define a weekly calendar.
• The period format region is hidden.
• The application generates a temporary period name using a fixed format of Period
numberYY.
• You can override this format with your own customized period names.

In Oracle Cloud Applications, a calendar can have only one period frequency and period type.

Adding a Calendar Year
For manually entered calendars:

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

For an accounting calendar that is associated with a ledger, changing period names or adding a year
updates the accounting period dimension in the balances cubes.

Practice 7-10 Overview: Verifying Your Calendar

• Searching for your calendar.
• Reviewing your calendar.


Calendar Auditing
• Calendar validation is automatic and prevents serious problems when you begin using
the calendar.
• After you set a calendar period status to open or future enterable, you cannot edit the
period.
• The calendar validation runs automatically when you save the calendar.

• Audits your accounting calendars to check for common setup errors. This feature strengthens
controls during implementation and prevents potential processing problems related to invalid
calendar definitions.
• Performs online checking of errors such as the wrong number of days assigned to a period or
nonadjusting periods that have overlapping days.
• Provides online feedback in the form of error messages as the process checks for validation errors
such as date omissions, overlapping nonadjusting periods, and nonsequential periods.

Manage Currencies Overview
• Oracle Cloud Applications provide full cross-currency functionality to meet the needs of
global companies.
• Currency functionality is designed in accordance with:
– United States Statement of Financial Accounting Standards 52 (SFAS #52)
– International Accounting Standards 21 (IAS 21) requirements


Currency Concepts

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

Currency in Subledgers

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

Define Currencies: Overview
In the Setup and Maintenance work area, locate the Define Currencies task list and navigate
to the tasks needed to successfully implement your currencies.

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

Currencies Overview
• Create currencies to use, for example, for reporting purposes or in cases of newly
created countries or currencies.
• Use any of the ISO currencies to:
– Display monetary amounts in other currencies.
– Assign them to ledgers.
– Enter cross-currency transactions and journal entries.
– Record balances.

When creating or editing currencies, consider these points:

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

Practice 7-11 Overview: Reviewing and Creating Currencies

• Verifying what currencies are enabled.
• Creating a new currency.


Conversion Rate Types Overview
Conversion rate types are assigned to currency rates to convert cross-currency amounts to
ledger currency equivalents.

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

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

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


Explain Cross-Rate Rules
Cross-rates facilitate the creation of daily rates by automatically deriving the rates from the
relationship between contra currencies and a pivot currency.
• Pivot Currency: A currency linked to the two contra currencies to enable the automatic
creation of the daily rates between the contra currencies. Select a pivot currency that is
commonly used in your currency conversions and is enabled, effective, and not a
statistical currency.
• Contra Currency: A currency other than your pivot currency that is enabled, effective,
and not a statistical currency.

The automatic creation of rates is particularly beneficial for intercompany transactions with multiple
currencies because it ensures consistency among the rates, thereby minimizing the effect of conversion rate
differences during the intercompany elimination process.

Explain Cross-Rate Rules
For example, set up a daily rate between the US dollar (USD) and the euro currency (EUR)
and another between the USD and the Canadian dollar (CAD).
From Currency To Currency Rate Inverse Rate
USD EUR 0.7748 1.2907
USD CAD 1.0134 0.9868
• USD is the pivot currency.

• EUR and CAD are the contra currencies.

From Currency To Currency Rate Inverse Rate
EUR CAD 1.3080 .7846
USD is the pivot currency used by the application to create a daily rate between EUR and CAD
automatically.
Note: If the Enable Cross-Rates check box is deselected after you enter contra currencies, the application
stops calculating cross-rates going forward for that particular rate type. All the earlier calculated cross-rates
for that rate type remain in the database unless you manually delete them.

Practice 7-12 Overview: Creating Conversion Rate Types

• Creating a conversion rate type.
• Defining a cross-rate pivot currency.
• Defining two contra currencies.


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

Sharing Daily Rates:

• Daily conversion rates are shared across all ledgers within an application instance and are available
when you are entering cross-currency transactions in your Oracle subledgers.
• Subledger applications share the same daily rates with the general ledger, but different rate types
enable each subledger to convert transactions at different rates.
Import and Calculate Daily Rates:Use the Import and Calculate Daily Rate file-based data import (FBDI) to
upload daily currency conversion rates into Oracle General Ledger. You can download a daily rates
spreadsheet template to use to prepare your currency data.

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

Currency Rates Manager

Navigate to: Others > Setup and Maintenance > Financial Reporting Structures > Manage Daily Rates >
Daily Rates tab.
Warning: Always use the interface table to load your daily rates either through the spreadsheet template or
by using other file loading tools. Do not load rates directly into the GL_DAILY_RATES table. This can
corrupt your daily rates data.
Note: Use conversion rate service companies to provide you with rates that can be loaded into the
GL_DAILY_RATES_INTERFACE table automatically.
You can use the Import and Calculate Daily Rate file-based data import (FBDI) to upload daily currency
conversion rates into Oracle General Ledger.

Practice 7-13 and 7-14 Overview: Using Currency Rates

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


Summary

• Manage value sets.
• Define chart of accounts components.
• Manage and publish account hierarchies.
• Maintain segment values.
• Manage cross-validation rules.
• Define calendars and currencies.


8
Configuring Ledgers

Objectives

• Define ledgers and ledger options.
• Assign balancing segments.
• Manage reporting currencies.
• Map chart of accounts.
• Explore the GL Balances cube.
• Create ledger sets.
• Define GL security.


Define Ledgers

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

Ledgers and Accounting Configurations
The process of designing the enterprise structure, including the accounting configuration:
• Starts an implementation.
• Includes determining financial, legal, and management reporting requirements.
• Requires setting up primary and secondary ledgers.
• Entails making currency choices.
• Involves examining consolidation considerations.
• Serves as a framework for how financial records are maintained for an organization.


Ledgers and Accounting Configurations

This figure shows the enterprise structure components and their relationships to each other.
A ledger determines the currency, chart of accounts, accounting calendar, ledger processing options, and
accounting method for its associated subledgers.
• Each accounting setup requires a primary ledger and, optionally, can include one or more secondary
ledgers and reporting currencies.
• Reporting currencies are additional currency representations of primary ledgers or secondary
ledgers.
• The number of ledgers is unlimited and determined by your business structure and reporting
requirements.

Define Ledger Components

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

Ledgers and Subledger Accounting
Oracle Cloud Applications reflect the traditional segregation between the general ledger and
associated subledgers.
• Detailed transactional information is captured in the subledgers.
• Transactions are periodically sent to Subledger Accounting for creation of journal
entries.
• Transactions are imported and posted in summary or detail to the ledger using
Subledger Accounting.
Subledger Accounting is an application that is used to create and capture transactions. It
contains accounting rules that are used to create detailed journal entries.

Companies account for themselves in primary ledgers and, if necessary, secondary ledgers and reporting
currencies.
• Your transactions from your subledgers are posted to your primary ledgers, and possibly, secondary
ledgers or reporting currencies.
• Local and corporate compliance can be achieved through an optional secondary ledger, providing an
alternative accounting method, or in some cases, a different chart of accounts.
• Your subsidiary's primary and secondary ledgers can both be maintained in your local currency, and
you can convert your local currency to your parent's ledger currency to report your consolidated
financial results using reporting currencies or translation.

Manage Primary Ledgers

The Primary Ledger:

• Performs as the main record keeping ledger.
• Records transactional balances by using a chart of accounts with a consistent calendar and
currency, and accounting rules implemented in an accounting method.
• Is used to book journals to record the impact of subledger transactions.
To determine the number of primary ledgers:
• Begin with your financial, legal, and management reporting requirements.
• Consider corporate year-end and local government regulations and taxation.
For example, if your company has separate subsidiaries in several countries worldwide, enable reporting for
each country's legal authorities by creating multiple primary ledgers representing each country with the local
currency, chart of accounts, calendar, and accounting method. Use reporting currencies linked to your
country-specific primary ledgers to report to your parent company in their ledger currency from your foreign
subsidiaries.

Practice 8-1 Overview: Searching for Your Ledger

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


Specify Ledger Options

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

Processes Using Ledger Options
• Year-End Closing
• Translation
• Journal Posting
• Revaluation

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

Practice 8-2 Overview: Verifying Your Ledger Options
This practice covers the following sections on the Specify Ledger Options page:
• Accounting Calendar
• Subledger Accounting
• Period Close
• Journal Processing
• Sequencing
• Average Balance


Balancing Segment Value Assignments: Overview
• Assignment of primary balancing segment values to legal entities and ledgers is

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

For example, if one ledger is recording transactions for three legal entities and another is recording
transactions for two legal entities, assigning balancing segment values to your legal entities and ledgers
simplifies the list of values on journal entries and transactions.

Balancing Segment Value Assignments to Legal Entities
• Assign values to legal entities before assigning them to the ledgers.

• Use the values to identify legal entities during transaction processing and reporting.
• Use the values to ease accounting for your operations to regulatory agencies and tax
authorities.

Navigate to: Others > Setup and Maintenance > Financials > General Ledger > Assign Balancing Segment
Values to Legal Entities

Balancing Segment Values Assignments to Ledgers
• Assign specific primary balancing segment values to your primary and secondary
ledgers to represent nonlegal entity- related transactions such as adjustments or top-
side entries.
• If you use legal entities, assign balancing segment values to all legal entities first before
assigning the remaining balancing segment values to the ledger..

Navigate to: Others > Setup and Maintenance > Financials > General Ledger > Assign Balancing Segment
Values to Ledger
Example: Your company hires a law, accounting, or consulting firm to do some legal or tax work related to
incorporation to determine the most advantageous legal entity configuration for their organization. You don't
want to charge that cost to any one legal entity but would prefer to book it to the corporate ledger for now.
You would charge the ledger-based balancing segment value instead of legal entity-based balancing
segment value. You can allocate charges to the legal entities after you have determined an appropriate way
to distribute the cost.

Balancing Segment Value Assignment Report
• Shows all primary balancing segment values assigned to legal entities and ledgers
across accounting setups.
• Ensures the completeness of your accounting configuration and the accuracy of your
assignments.
• Enables you to quickly identify errors and view any unassigned values.

Use the Scheduled Process page to run the report.

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

Practice 8-3 Overview: Verifying Legal Entities and Balancing
Segment Assignments
• Assigning your legal entity to your ledger.
• Verifying your legal entity and business segment assignments.


Manage Reporting Currencies
• Reporting currencies maintain and report subledger

and general ledger journal entries or balances
in additional currencies.
• Each primary and secondary ledger is defined with a ledger currency.
• Reporting currencies:
– Record your business transactions and accounting data for that ledger.
– Maintain the ledger in the currency in which the majority of its transactions are
denominated. For example, create, record, and close a transaction in the same
currency to save processing and reconciliation time.
– Conform to local requirements, for example, paying transaction taxes is easier using

a local currency.
Note: Many countries require that one of your ledgers be kept in their national currency.
With Reporting Currencies, you can produce financial statements using the national currency or alternate
currencies.

Manage Reporting Currencies

Business Reasons to Use Reporting Currencies

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

Reporting Currencies: Conversion Levels

3
A reporting currency is linked to a primary or secondary ledger and can be maintained at one of three data
conversion levels.
• Balance level: Only general ledger balances are maintained in the reporting currency through the
Translation process. Typically the least expensive, requiring duplication of only the balance level
information.
• Journal level: General Ledger Posting process transfers the journal entries to the reporting currency.
• Subledger level: Subledger Accounting creates the subledger journals to the reporting currency.
General Ledger converts the remaining journal entries to the reporting currency during the Posting
process.
Note
• Journal and subledger data conversion levels require more storage and processing because most
general ledger and subledger journals, plus general ledger balances, are replicated.
• Do not use journal or subledger-level reporting currencies if your organization needs to translate
your financial statements only to your parent company's currency for consolidation purposes.
Standard translation functionality meets this need.
• A full accounting representation of your primary ledger is maintained at the subledger-level reporting
currency. Secondary ledgers cannot use subledger-level reporting currencies.

Practice 8-4 Overview: Defining Reporting Currencies

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


Define Secondary Ledgers

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

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

• Charts of accounts: The chart of accounts mapping is required to instruct the system
how to propagate journals from the source to the target chart of accounts.
• Accounting calendars: The accounting date is used to determine the corresponding
nonadjusting period in the secondary ledger. The date mapping table provides the
correlation between dates and nonadjusting periods for each accounting calendar.
• Ledger currencies: Currency conversion rules are required to instruct the system how to
convert the transactions, journals, or balances from the source representation to the
secondary ledger.

Note: Journal conversion rules, based on the journal source and category, are required to provide
instructions on how to propagate journals and types of journals from the source ledger to the secondary
ledger.

Secondary Ledgers: Conversion Levels

4
Secondary Ledgers use one of the four conversion levels:

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

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

ANSWER

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

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


Secondary Ledgers Mapping

Creating secondary ledgers follows the same steps as primary ledgers.

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

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


Segment Mapping Rules
Segment rules serve to map each segment of the target chart of accounts to an account
value or segment in the source account. Segment rules:
• Assign a constant value for a segment in the target chart of accounts.
• Copy the value from the source segment to the corresponding target segment.
• Use hierarchical rollup rules when a specific parent source value and all of its child
segment values are mapped to a given detail target segment value. This enables you to
process groups of source segment values in one single rollup rule.

Tip: Define parent source values in rollup rules with date-effective versions of a hierarchy. Then use the
accounting date from the journal entries to reference the chart of accounts mapping that falls within the
effective date of the hierarchy. This gives the additional benefit of self-maintaining mappings because the
hierarchies referenced change with time and the applicable child values are processed automatically.

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

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


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

The Review and Submit Accounting Configuration:

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

Practice 8-5 Overview: Completing the Ledger Configuration

• Completing the Ledger Configuration.
• Opening the First Accounting Period.
– Selecting your data access set.
– Opening the period.


Balance Cubes: Overview
• Are created automatically when an accounting configuration is submitted for a ledger

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

Note: Average balances are tracked in a separate balances cube.

Balance Cubes Naming

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

Balance Cube Dimensions
Dimension Description
Accounting Period Based upon the calendar of the ledger or ledger set. Report on
years, quarters, or periods.
Ledger or Ledger Set Used to select a ledger for reporting.
Charts of Accounts Segments from the charts of accounts, organized by hierarchy.
Segments
Scenario Indicates whether the balances are actual, allocated, or actual
including allocated, budgeted, or forecast.
Balance Amount Indicates whether the value is a debit or credit, and whether it is
for the beginning balance, period activity, or ending balance.
Amount Type Indicates whether the amounts represent Base, Period, Quarter, or

Year to Date.
Currency Used to select the desired currency for the balances.
Currency Type Used to select the currency type of the balances. Available options
are Entered, Converted, or Total.
This table details the dimensions that are available for creating financial reports using multidimensional
cubes.
The General Ledger Posting process updates your balances and stores these balances in a balances cube
for efficient multidimensional analysis. This provides for efficient reporting.
Note: Dimensions are predefined and new ones cannot be added.

Manage Ledger Sets
• Enables you to group multiple ledgers that share the same chart of accounts and
calendar combination to increase the efficiency of your period close, security
administration, and reporting.
• Allows you to treat multiple ledgers as one.

For example, you can open and close periods for multiple ledgers in a ledger set in a single submission by
submitting the Open and Close Period process.

Practice 8-6 Overview: Creating a Ledger Set
This practice covers creating a ledger set.


Data Access Set Security: Overview
Grants access to ledger, ledger set, or specific primary balancing segment values that are
associated with a ledger.
Create and edit data access set security on the Manage Data Access Sets page from the
Setup and Maintenance work area or from your implementation project.


Data Access Set Security
Secures access to ledgers, ledger sets, and portions of ledgers by using primary balancing
segment values.
If you have primary balancing segment values assigned to a legal entity, then you can use
this feature to secure access to specific legal entities.
• Secures parent or detail primary balancing segment values.
• Secures the specified parent value as well as all its descendants, including mid-level
parents and detail values.
• Requires all ledgers assigned to the data access set to share the same chart of
accounts and accounting calendar.


Data Access Set Security

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

Data Access Set Security: Example

This example shows a data access set that secures access by using primary balancing segment values that
correspond to legal entities. One access set assignment that provides read-only access and the other, read
and write access to the corresponding legal entities' primary balancing segment value.
This figure shows:
• A data access set for the Vision US Primary Ledger.
• The access set type of Primary Balancing Segment Value, with each primary balancing segment
values representing different legal entities.
• Read-only access has been assigned to primary balancing segment value 131, which represents the
Vision US 2 Health legal entity.
• Read and write access has been assigned to the other two primary balancing segment values 101
and 102, which represent the Vision US 1 LE 1 and LE 2 legal entities.
For this data access set, the user can:
• View the journals, balances, and reports for primary balancing segment value 131 for Vision US 2
Health legal entity.
• Create journals and update balances, as well as view journals, balances, and reports for primary
balancing segment value 101 and 102 for legal entities Vision US 1 LE 1 and LE 2 legal entities
Note: In financial reporting, the list of ledgers is not secured by data access sets when viewing a report in
Preview mode. You can view the names of ledgers that you do not have privileges to view. However, the
data from a secured ledger does not appear on the report.

Practice 8-7 and 8-8 Overview: Creating a Data Access Set
This practice covers creating a ledger set.

• Practice 8-7: Reviewing data access set security.
• Practice 8-8: Creating data access set security.


Summary

• Define ledgers and ledger options.
• Assign balancing segments.
• Manage reporting currencies.
• Map chart of accounts.
• Explore the GL Balances cube.
• Create ledger sets.
• Define GL security.


9
Configuring Journal Approval

Objectives

• Describe the key concepts of approval management.
• Perform basic approval configurations.
• Configure email notifications.


Approval Workflow: Overview
Workflow is an automated process that:

• Passes tasks from a user, a group of users, or an application to another user or group
for consideration or action.
• Routes tasks in a logical sequence to achieve an end result.
A workflow human task is anything that requires attention or action from users. Examples of
tasks include approving an expense report or journals.

For workflows, Oracle Cloud Applications use the approval management extensions of the human workflow
services from Oracle SOA Suite, as well as the Oracle BPM Worklist application.
Oracle SOA Suite:
• Is a comprehensive software suite used to build, deploy, and manage service-oriented architectures
(SOA).
• Provides a human workflow service that handles all interactions with users or groups in business
processes.
Oracle BPM Worklist provides the user interface for:
• Users to access tasks assigned to them and perform actions based on their roles in the workflow.
• Implementers to perform approval management setup, to define who should act on which types of
transactions under what conditions.

Approval Management: Overview
Approval management:
• Controls approval workflows for business objects such as journal entries.
• Enables you to define complex, multistage task routing rules.
• Integrates with the setup in Human Capital Management (HCM) to derive approvers
based on the supervisory hierarchy.

To set up approval management, use the following setup tasks from the Setup and Maintenance work area,
which take you to Oracle BPM Worklist.
• Manage Approval Groups: Optionally create and maintain sets of users who can act on workflow
tasks, for example a chain of approvers for journal approvals.
• Manage Task Configurations: Define approval rules that determine how and when journals are
routed for approval. For example, you can specify the amount that a journal batch must meet to be
automatically approved and not sent to any approver.
To access these setup tasks for journal approvals, use the Manage Journal Approval Rules task. For other
approvals use the BPM Worklist Administration Duty role, which is predefined for the Application
Implementation Consultant job role.

Manage Journal Approval Rules
Journal approval in Oracle Cloud applications uses:

• Oracle Cloud Approvals Management (AMX)
• Oracle Business Process Execution Language (BPEL)
This process:
• Determines if approval is required.
• Submits the batch to approvers (if required).
• Notifies appropriate individuals of the approval results.

The Journal Approval Process obtains the necessary management approvals for manual journal batches.
The process gives one of four results:
• Approval Not Required: The journal batch does not need approval.
• Approved: The journal batch was approved by all necessary approvers.
• Rejected: The journal batch was rejected by an approver.
• Validation Failed: The journal batch failed the validation process and was never submitted to the
approver.

Manage Journal Approval Rules Setup
Enable Journal Approval

3
Specify Journal Sources

Create Journal Approval
Rules
• Enable approval for the ledger in the Journal Processing section on the Specify Ledger Options
page. Navigate to the Specify Ledger Options page through the General Ledger Functional area
from Financials Task in Setup and Maintenance.
• Enable approval for a specific source on the Manage Journal Sources page. Navigate to the Specify
Ledger Options page through the General Ledger Functional area from Financials Task in Setup and
Maintenance. Click on Setup, open the General Ledger functional area, select the Specify Ledger
Options and click on Select to set scope. After selecting your ledger, click Save and Close.
• Create approval rules to reflect your corporate or departmental policies in approving journal entries.
Note: Approval is for the entire journal batch. If a journal requires approval, submitting it for posting
automatically sends it for approval before posting.

Journal Approval Rule Considerations
The application comes with one predefined approval rule. If you enable the ledger and the
source for approval, then the journal entry is sent one level up in the supervisory hierarchy
for approval.
You must configure the approval rules in the Oracle Business Process Management (BPM)
Worklist application user interface. For a simple approval scenario, start by defining one of
these rules:
• Journal approval based on the highest journal line amount per ledger per batch.
• Journal approval based on the highest journal amount per ledger per batch.


Journal Approval Rule Considerations
Journal approval behavior is based on where you are in the period close process.
For example, ask yourself, which stage are you in:
• Beginning
• Middle
• End of the month
• Pre-close
• Close
• Post close

• Quarter close
For example: Month-end or quarter-end closing entries can be:

• Larger amounts than entries that are earlier in the month and can need more levels of approval.
• Entered by employees with more authority so need less levels of approval.

Journal Approval Rule Example
• Enter the following approval rules to apply to your journal batch when your maximum
journal line amount is:
– Less than 50,000 United States dollars (USD): No approval required.
– Between 50,000 to 100,000 USD: Requires one level of approval.
– Greater than 100,000 USD: Requires two levels of approval.
• Build your rules for every combination of ledger, entered amount, approval level, or other
needed scenarios by using the pattern in the suggested rules.
• Define your own rules based on attributes from the different parts of your journal,
including the ledger, batch, header, or line level.

For example, use category, source, account, or descriptive flexfield information as selection criteria for the
journals to be sent for approval.
The ledger is included in the rules because you typically define approval rules per ledger. Set the options
that enable journal approval at the ledger level and by journal source. This allows the approval process to
determine which journals to send for approval.

Key Concepts: Assignees
• An assignee represents a specific set of policies and routing.

– For example, you can route a journal to the supervisor of the person who entered the
journal or to an another manager based on the dollar amount of the journal.
– Assignees are predefined, and can be enabled or disabled.
• Assignee types:
– FYI
– Parallel
– Serial
– Single
•

Each assignee has at least one predefined rule set.
Some assignees are disabled by default, but you can enable them to use them for the task. You cannot add
or edit assignees, for example change the Assignee type.
Assignee Types
• FYI: Task requires no action from assignees, other than to take note of the task.
• Parallel: Task can be routed to multiple people at the same time.
• Serial: Task can be routed to one person at a time, according to a defined routing.
• Single: Task is routed to multiple people at the same time, but only requires approval from the first
responder.

Key Concepts: Rule Sets and Rules
Rule sets are collections of rules, and they are predefined for each assignee with these
characteristics:
• Flow: Serial or parallel, and specific order, for assignees with multiple rule sets.
• Business object level: Header or line.
In each rule, you define a condition and specify the routing using a list builder.


Key Concepts: List Builders
A list builder is a mechanism to determine the task assignees, usually approvers, for
example, based on going up the supervisory hierarchy.
List builders include:
• Supervisory: Hierarchy of employees and managers.
• Resource: A specific user or application role.
• Approval Group: A set of specific users.
• Job Level: Supervisory hierarchy with job levels in consideration.
• Position: Starts with a given approver's position and continues up the chain until a
certain position is found.

The following list builders are based on structures in HCM, which must be set up appropriately.
• Supervisory: The hierarchy of employees, with defined job roles, and their managers.
For example:
- Joe Smith, Accounting Assistant
- Alex Park, Accounting Manager
- Anna Lee, Senior Accounting Manager
- Jane Brown, Director of Accounting
- Mike Green, Vice President of Finance
- If two levels of approvals are required, and Joe Smith submits a journal for approval, then
approvals from Alex Park and Anna Lee are required.
• Job Level: The supervisory hierarchy with job levels in consideration. The approval list is generated
based on the starting assignee specified in a rule and continuing until an approver with a sufficient
job level is found.

• For example:
- Joe Smith, Accounting Assistant (job level 1)
- Alex Park, Accounting Manager (job level 2)
- Anna Lee, Senior Accounting Manager (job level 3)
- Jane Brown, Director of Finance (job level 4)
- Mike Green, Vice President of Finance (job level 4)
- If job level 4 approvals are required, then the last approver for journal is Jane Brown, who is
the first person in Joe’s supervisory chain at job level 4.

Journal Approval Hierarchies
Approval List Type Functionality

Human Resources (HR) This method uses the HR Supervisory hierarchy levels and specifies
Supervisory the number of levels available for approval.
Job Level A relative dollar amount can be attached to a job. The approval list
moves up the HR Supervisory hierarchy to the point it finds a job with
the necessary approval amount.
Position A relative dollar amount can be attached to a position.
Approval Group Approver groups represent functional or subject matter
experts outside the transaction's managerial chain of authority, such
as Legal or HR personnel.

Dual Chain Dual chains can be processed at the same time.
Use the following Oracle Cloud Approvals Management (AMX) List Builder to build your approval hierarchy
list.
• For the job and position level approvals, the approval list continues up the hierarchy until it finds the
approver with the correct approval authority.
• A journal can be escalated to a new approver by the administrator.
Note: Best practices are to select Job Level, HR Supervisory, or Position list builders for your journal
approval rules.
A Resource list builder is also available.
The rules in a rule set need to cover all scenarios. Otherwise the rule evaluation can fail. For example:
• If one rule checks for the Condition Journal Category is equal to Adjustment
• Another rule should check for the Condition Journal Category is not equal to Adjustment.

Manage Task Configurations
Reset Save
Edit task
Commit
task
Tabs for each

task

Navigate to: Others > Setup and Maintenance > Enter Manage Task Configurations in search field > Search
> Click appropriate task in Name column.
In the Tasks to be configured pane, review the predefined tasks in the server domain, which generally maps
to a product family, and edit tasks as needed.
To edit a task:
• Select a task in the Tasks to be configured pane.
• Click the Edit task icon in the pane toolbar. You are in edit mode and can select other tasks to edit
without clicking Edit task again.
• Make changes in the tabs for the task.
• Click the Save icon in the toolbar. Your changes are retained even if you sign out, but are not yet in
effect. To discard all changes, saved or not, click the Reset icon.
• Click the Commit task icon to deploy your saved changes so that they are in effect.
Note: If the task is not predefined as rule-based, then the behavior does not need to be changed, and you
cannot edit the task. When you select such a task, you get a message stating that no rules metadata is
associated with the task.

Manage Task Configurations

> Click appropriate task in Name column > Select task in Tasks to be configured pane
The tabs for each task are:
• General: View general information about the task as a whole. Usually you don’t need to use this tab.
• Assignees: View and edit approval policies and routing.
• Data: View information about data that’s available for use in the rules in the task. Usually you don’t
need to use this tab.
• Deadlines: Define deadlines for the task, and policies for task expiration and escalation.
• Notifications: Set up notifications to be sent to people with respect to the task.
• Access: Determine access to perform specific actions on the task.
• Configuration: Define settings for the task.

Assignees Tree
Assignee

> Click appropriate task in Name column > Select task in Tasks to be configured pane > Edit task >
Assignees tab > Switch to Vertical Layout
Use the Assignees tab to define policies and routing.
The assignees tree shows the stages and assignees within each stage.
• The main boxes are stages, and the boxes within are assignees.
• Click the name of the stage or assignee to select it.
Make sure that all unused stages and assignees are disabled:
• Select the stage or assignee.
• In the pane below the tree, click Advanced.
• Select the Ignore Stage or Ignore Assignee check box.

Rule Sets
Click the Go to rule icon in the Assignees tree to open rule sets for a given assignee.
Rule Set
Expand/Collapse Rule

Assignees tab > Switch to Vertical Layout > Go to rule
For example, you select the Supervisory_JournaApprovalRuleSet assignee, to open the
Supervisory_JournalApprovalRuleSet rule set that is predefined for that assignee. This rule set contains
three predefined rules that you can edit by clicking the Expand button.
Note: For ease of maintenance, consider editing existing rule sets instead of creating new ones. You should
not have to create or delete rule sets.

Defining Rule Settings
• Make sure each valid rule being used is active.

– Expand the rule.
– Click Show Advanced Settings.
– Select the Active check box.
Expand
Show Advanced

Settings
• Use Priority field in advanced settings to set priority for rules.
Assignees tab > Switch to Vertical Layout > Go to rule > Expand > Show Advanced Settings
Set priorities for rules if you want some rules to take precedence over other rules in the same rule set. The
priority value for each rule is relative to other rules. In other words, there is no predefined meaning for
Medium, other than that it takes precedence over rules that are set at Low, Lower, or Lowest.

Defining Rules
• Click the Validate button as you define rules, to test whether your definitions work.
• Check the Business Rule Validation - Log sub tab for any issues to address.
Rule set
Validate
Rule

IF component
THEN component
Assignees tab > Switch to Vertical Layout > Go to rule > Expand rule
At least one rule in a rule set must evaluate to true.
The Business Rule Validation – Log sub tab appears below the rules, at the bottom of the Assignees tab,
after you click the Validate button.
Each rule consists of IF and THEN components.

IF Component
• The IF component contains at least one

condition to determine when the rule is
applied.
• Each condition contains a subject,
operator, and criterion.
Subject Operator
Criterion

Right Value
icon
Left Value icon Add condition
• To select values for the subject or criterion, click the Left Value or Right value icon to open the
Condition Browser dialog box. What’s available in the condition browser depends on what you are
editing.
• To add another condition, click the down arrow at the end of the last defined condition.
• In this example, the conditions for the rule are:
- The journal must be more than 1000, and
- The employee is not inactive
Note: You can have multiple conditions for one rule.

THEN Component
The THEN component contains actions that define what happens if the conditions in the IF
component are met.

The THEN component consists of the list builder and related attributes, response type, automatic action
setting, and rule name.
• The list builder and related attributes define how task assignees are derived. In this example:
- List Builder: The selected list builder is Supervisory, so approvals go up the employment
reporting chain.
- Number of levels: Two levels up the supervisory hierarchy are required - the manager of
person who submitted the journal, and that manager’s manager.
- Starting Participant: The first approver is defined as the manager of the person who
submitted the journal.
• The Response type indicates if the assignees are required to address the task or if they are just to
receive an FYI notification. In this example, the participant must take action to approve or reject the
journal.

• Automatic action settings allow you to set an automatic action on tasks, to automatically approve or
reject. In this example:
- Auto Action Enabled: Set to True so the journal is automatically approved or sent to the
assignees.
- Auto Action: Since automatic action is set to “APPROVE”, automatic action is specified.
• The Rule Name is a meaningful name for the rule, which is displayed to assignees, in this case, the
journal approvers.

Rule Example

Assignees tab > Switch to Vertical Layout > Go to rule > Expand rule.
For the same rule set, you have another rule with these conditions in the IF component:
• The journal total must be the same or less than 1000, and
• The employee is not inactive
If the condition is met, then based on the values in THEN component, the task receives automatic approval.
• Number of levels: Is set to 1, which must be the case if you enable automatic action.
• Starting Participant: Is set to the task creator.
• Top Participant: Is set to the last possible approver, which in this example is the CFO of the
company, Casey Brown. Depending on the approval settings:
- The starting participant shows as the approver if the task is automatically approved.
- If the starting participant submits the journal, there will be one or more levels of approval.
- If the manger submitted the journal, then there is only one level of approval, the CFO.
• Auto Action Enabled: Is set to True, so that the specified action automatically occurs if the conditions
are met.
• Auto Action: Is set to “APPROVE” so that the journal is automatically approved if the conditions are
met. The other possible action is null.

Deadlines
Use the Deadlines tab to configure when tasks expire, escalate, or renew.

Deadlines tab.
You can define the policy so that if the assignee doesn’t act on the task within a certain period of time after it
was assigned, then:
• Escalate: The task is reassigned up the approval chain, for example to a manager or director.
Escalation policies use the LDAP directory, while the list builder uses the HCM hierarchy, so make
sure that both are in sync.
• Expire: The task expires and the requester needs to resubmit it. Expired tasks are automatically
rejected.
• Renew: The task is still assigned to the same assignee. You determine the number of times the task
can be renewed. After all renewal periods have passed, then the task expires.
For example, you enter 14 days for the Duration fields, with the Static check box selected. If the assignee
doesn’t act on the task within two weeks, then:
• Escalate: The task is reassigned to the assignee’s manager.
• Expire: The task expires and the requester needs to resubmit it.
• Renew: The task is still assigned to the same assignee. If another two weeks pass, then the task is
renewed again, because the Maximum Renewals field has a value of 2. After four weeks have
passed, the task expires if the assignee still takes no action.

Notifications
Use the Notifications tab to send notifications based on task status, for example, notify
approvers when the task is assigned to them.

Notifications tab.
Enter notification content under Notification Header. Click the Enable Reminder check box to send reminder
notifications based on when the task is assigned or when it’s about to expire.
Recipient Types:
• Approver: Users who have already acted on the task up to this point.
• Assignees: User who is assigned to take action on the task.
• Initiator: User who submitted or created the task.
• Owner: User with administration access to the task. This type is not used for any of your users.
• Reviewer: Users who can add comments and attachments to a task.
Note
• If the task has rules with the FYI response type, then notifications are also sent based on the rule
conditions. You can use these notification settings or the FYI rules, or both. For example, you can
delete the notifications in the Notification Settings section if you prefer to use the FYI rules to send
notifications based on certain criteria, not just task status.
• The order of the notifications determines priority. For example, if one user would receive multiple
notifications at the same time, based on the list order, then that user would receive only the
notification that has the highest priority.

Configuration
On the Configuration tab, under the Miscellaneous section, make sure to leave the Task
Aggregation option in its default setting.
Notifications are sent depending on the setting:
• None: As many times as the task is assigned to the user.
• Once per task: To the assignee only one time in the entire task life cycle.
• Once per stage: To the assignee only one time in a stage.

Configuration tab.
For example, if you have a task requiring approval on individual journals, and you change the Task
Aggregation setting to None, then assignees would get 15 notifications for approval if there are 15 journals
for approval.

Access
On the Access tab, you can take away access to perform certain actions on the task.
1. Open the Actions section.
2. For a specific task action,
open the Individuals with
access choice list.
3. Deselect check boxes as
needed.

> Click appropriate task in Name column > Select task in Tasks to be configured pane > Edit task > Access
tab.
Individuals with access:
• Approver: Users who have already acted on the task up to this point.
• Assignees: User who is assigned to take action on the task.
• Initiator: User who submitted or created the task.
• Owner: User with administration access to the task. This type is not used for any of your users.
• Reviewer: Users who can add comments and attachments to a task.

Manage Approval Groups
Use the Approval Groups tab in Oracle BPM Worklist to define sets of users that can be
selected for an Approval Group list builder. Tasks would be routed to the specified group of
users.
Approval groups:
• Can be nested within other approval groups.
• Are stored at the server level and not shared across domains. For example, you cannot
use the same group for Financials and HCM.
• Can be static or dynamic.

Approval Group Examples

• You have a special, ongoing project that involves a wide range of employees. You can create an
approval group of the managers involved, who must approve journals related to the project.
• You have certain categories of requisitions that require pre-approval from a select group of people.
You can create an approval group containing the users who all must approve such requisitions in
parallel before additional approvals can be made.

Manage Approval Groups: Static
• You select specific users to include in the group and specify the flow of tasks from one
user to another.
• If the group is used in a rule set that has parallel routing, then the task is passed to all
users in the group at the same time.
Add Member
Edit Member

Navigate to: Others > Setup and Maintenance > Enter Manage Approval Groups in search field > Search >
Click appropriate task in Name column.
To edit or reorder a member of the group, first select the member in the chart and then click the Edit
Member, Push Member Up, or Push Member Down icons.
Note
• Static Approval Group requires ongoing maintenance because it uses named users. For example, if
a user leaves the company or change departments, you must update the Approval Group.
• Dynamic approval groups are not available in Oracle Cloud implementations.

Journal Status Page
The Journals section of the General Accounting dashboard displays the journals requiring
your approval.

The Journals page allows you to approve or reject journals if you are the current approver.
Navigate to: General Accounting > Journals

• You must have the privilege to approve journals to view your journals that need approval in the
Journals region.
• Journals requiring approval by others are also shown.
• Approval notifications display a table of key journal attributes for each journal and a list of past,
current, and future approvers.

Withdraw Approval
• The Withdraw Approval button on the Journals page:

– Is used at anytime in the approval process to withdraw journals from the process.
– Allows you to edit the journal.
– Sets the completion status of the journal to Incomplete.
– Submits the entry for approval again after your changes.

Note: Allocation journals are not routed through the approval process.

Practice 9-1 Overview: Creating Journal Approval Rules
This practice covers creating journal approval rules for the following scenario:

The rules are:

• Rule 1: 1st Level Supervisor: Approves between $500 and $10,000. One approver required.
• Rule 2: 2nd Level Supervisor: Approves $10,000 or more. Two approvers required.
• Rule 3: $500 or less are automatically approved. No approver required.

Simplified Workflow Rules Configuration
• Create rules for Payables Invoice Approval and General Ledger Journal Approval
workflows using spreadsheets.
• Simplify the process of creating and managing workflow rules by using a template.
• Download the spreadsheet template, enter data, and upload it using the Manage
Workflow Rules in Spreadsheet task.
Rule Template
Section

Upload History
Section
Navigate to: Others > Setup and Maintenance > Financials > Application Extensions > Show: All Tasks >
Manage Workflow Rules in Spreadsheet.
To download a template, select the required workflow and click the Download icon.
In the Rule Templates section, each workflow record stores a copy of the template used for the last
successful rule upload. Use this template to review and modify the existing rules.
The Upload History section displays the status of the past uploads. The upload history details are specific to
the workflow selected in the Rule Templates section.

Rules Template
• The templates provide a simple layout for defining workflow rules in accordance with
your organization’s approval policy.
• The following shows an Invoice Approval Rules Sheet with sample rules.
Column Headers with
Tooltips

Manage Workflow Rules in Spreadsheet > Download Invoice Approval > Invoice Approval Sample Template
1.
Refer to the tooltips on each column header for instructions on how to enter the rule information. You can
define approval rules to send approval notifications to:
• Approval groups
• Members of supervisory or job based hierarchies
• Specific users
• Users with specific application roles
You can also create rules to Auto Reject or Auto Approve.

Data Sets
• Data sets simplify the rule creation and maintenance process.

• If the approver for a transaction varies depending on certain transaction attributes, you
can use Data Sets while defining the approval rule.
• You can define a mapping between the approver and relevant transaction attributes.
Data Sets Sheet with

Sample Data

Manage Workflow Rules in Spreadsheet > Download Invoice Approval > Invoice Approval Sample Template
1 > Data Sets Tab.
Note: You can only use Data Sets for Payables Invoice Approval templates.
• In this example, transactions require approval by an approval group. However, the approval group
varies based on the combination of business unit on the invoice and the cost center segment value
on the invoice distributions.
• For rules created using this data set, the approval notification is sent to the appropriate approval
group for each invoice.
• If new cost centers are added to your organization, you only need to add more rows in the data set
and upload the rule file again.
• Aspects of the Business Rule
• Before defining rules in the template, you must analyze your approval policy and identify the
approval requirements. Each distinct approval requirement can be considered as a business rule.
• Before entering rules into the spreadsheet, consider the following aspects of the business rule:
- Which transactions require approval and who should approve them ?
- Which transactions require auto approval or auto rejection ?
- Do you need to send For Your Information (FYI) notifications for approvals under this rule ?
- Which transactions do not require approval under this rule, that is, the transactions for which
this approval rule is not applicable.
Note: While defining business rules, make sure that you define all aspects of a business rule in one rule
block. A rule block is a group of rows in the workflow rules spreadsheet where you define all aspects of the
business rule. Each subsequent business rule should be defined in a new rule block.

• While all rule aspects defined within a rule block are processed simultaneously, rule blocks are
processed in sequence. Therefore, you must consider the sequence in which the rules should be
processed before defining the rules.
• When using data sets for defining Payables Invoice Approval rules, you must add a reference to the
data set name in the rule definition by adding a prefix of ‘$’ to the data set name. For example, $FIN
APPROVAL GROUPS.
• A copy of the rule template of the last successful rule upload is stored on the Manage Workflow
Rules in the Spreadsheet page for each workflow. You can download this template to review or
modify the rules.
• Once you create rules using the rule templates, use the spreadsheet method only for any future
maintenance of rules.
Caution: Every successful rule upload using a spreadsheet template overrides the existing rules for the
workflow.

Configurable Email Notifications for Journal Approval
Oracle Business Intelligence (BI) Publisher reports are used to generate the email content
and format for journal approval workflow email notifications. You can enable BI Publisher-
based journal approval email notifications, which are ready to use as delivered.
• No additional configuration is required unless you want to edit a copy of the predefined
reports to tailor the body of the emails, based on your specific needs.
• Microsoft Word templates can be optimized for mobile devices and are easily
configurable.
• Comprehensive list of attributes are provided to modify the email notifications according
to your requirements.
• Both layout and content can be changed. For example, add images, change colors,

styling, add or remove attributes, and modify text.
You can:
• Revert to the classic approval notifications at any time by disabling the feature using the Feature Opt
In page in Functional Setup Manager.

Configurable Email Notifications Process
The email notifications process:

• Is same as generating other types of report output.
• Involves various types of objects in the BI catalog working together to generate the
output used for email notifications.

Business Intelligence Catalog Objects

• Data Sources: Store the attributes and attribute values for business objects and transactions in the
application. An example of data sources is transaction tables.
• Data Model: Determines which attributes from data sources are available to be included in the email
and how that data is retrieved.
• Subtemplate: Provides common components, for example a branding logo and buttons, that can be
reused in multiple reports.
• Style Template: Provides styles such as the type of lines and fonts to use in tables, or the font type,
size, and color to use for headings.
• Report: Contains a layout template that determines:
- Which attributes appear in the email, from the data model used for the report.
- What the email looks like, leveraging components from the subtemplate and styles from the
style template used for the report.
• HTML: Output generated from the report.
• Email: Sent to users as part of a business flow, with the HTML output embedded in the email body.
Note: Each workflow task with configurable email notifications has a corresponding predefined report in the
BI catalog.

Email Components
Notification
Header
• Workflow email notifications are based

on report layout templates. Button
s
• When editing a copy, follow a
predefined layout for consistency.
• The callouts in the figure identify the
email components.
Notification
Body

Approval
History
Buttons
Link to
Transaction
Details
Email Components Description

• Notification header: Lists key attributes of the workflow task and the associated transaction.
• Buttons: Such as Approve and Reject are used on the task.
• Notification body: Includes transaction and line level details, displayed in tables, or sets of attributes
with corresponding values. The data model for the report restricts the total number of rows displayed
in some of the tables.
If the limit is exceeded, the table footer provides a link to the transaction details page, where users
can view all the rows. To change this limit, you can edit a copy of the data model.
• Approval history: Includes any attachments that users in the history uploaded for the task. You can't
edit this component.
• Link to transaction details links to both of the following:
- Corresponding transaction page.
- Task details in the worklist.
Modify Email Notifications Recommendations:
• Maintain the general structure.
• Don’t remove essential elements such as the action buttons.
• Don’t change the styles in your layout template.
• Don't edit a copy of the style template and apply that to your email; the predefined style template
should still apply to your email notification.

Adding a Branding Logo and Modifying Shared Components
In a copy of the predefined subtemplate you can:

• Add a branding logo to appear at the beginning of your emails.
• Change the button text.
• Change the text of the links that open the worklist in the application.

A predefined subtemplate contains action buttons and links for workflow email notifications based on
predefined report layouts.
Note: You must edit a copy of the subtemplate in the Custom folder of the BI Catalog. Do not directly update
the predefined subtemplate. The exact steps can vary depending on your version of Microsoft Word.

Configurable Email Notifications Implementation Best Practices
• Never edit predefined notifications.

• Do not rename standard BI catalog components, such as reports or subtemplates.
• Preview your changes before publishing.
• Do not modify any hyperlinks in the subtemplate file.

• Use the Copy feature for reports and subtemplate rather than editing predefined notifications.
• Copy data models, paste into the My Folder , and edit the copies.
- Before saving a local copy of the subtemplate file, disable the Update links on the save
option in Microsoft Word.
- Subtemplates are used across product areas and any modifications to the subtemplate affect
all notifications using it.

Enabling Email Notifications
• Use the Feature Opt In page in the Functional Setup Manager (FSM) to enable or
disable email notifications.
• Email notifications are not enabled by default.

To enable this feature:

Navigate to: Others > Setup and Maintenance > Setup: Financials > Change Feature Opt In link > Select
General Ledger Features icon > Configurable Journal Email Notifications.
• Check Journal Approval Notifications.
• Click Done to return to the Setup: Financials page.
The feature can be accessed through existing shipped duty roles.
• Business Intelligence Consumer: To receive predefined notifications. Commonly shipped through
Financials job roles as well as some abstract roles.
• Business Intelligence Authoring and BI Data Model Developer. To configure the predefined
notifications. Shipped through the Application Implementation Consultant job role.
The business processes associated with this feature are:
• Manage Invoices and Manage Payments for Payables
• Financial Control and Reporting for General Ledger
• Workforce Deployment for Expenses.

Using Quick Parts for Workflow Email Notifications
Use the Quick Parts feature in Microsoft Word to easily insert reusable pieces of formatted
content.
• Complete prerequisite steps to add the predefined Quick Parts content into your Quick
Parts gallery.
• Add Quick Parts content to Workflow Email Notification.
• Preview your layout template changes before uploading the .rtf file.
The predefined Quick Parts content is available in a style template .dotx file on My Oracle
Support.

Prerequisites
To get the predefined Quick Parts content into your Quick Parts gallery:
Open Configurable Email Notifications: Implementation Considerations (2215570.1) on My Oracle Support
at https://support.oracle.com.
Download the .dotx file and save it to your Microsoft Word template folder, for example C:\Users\<user
name>\AppData\Roaming\Microsoft\Templates.
To preview your layout template changes before uploading the .rtf file back to the Business Intelligence (BI)
catalog.
• Generate sample report data from the data model for the report that you're editing.
• Download a local copy of the subtemplate that applies to the layout template.
For more information see: Using Quick Parts for Workflow Email Notifications: Explained in the Oracle Help
Center at:
http://slc15alq.us.oracle.com/staging/docs/64/s20041164/en/FM_CommonImplementationGuide_20041164f
v/define-approval-management.html#OAIMP2408009

Summary

• Describe the key concepts of approval management.
• Perform basic approval configurations.
• Configure email notifications.



D96139GC30 sg1

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 sg1

Uploaded by

Copyright:

Available Formats

Oracle Internal & Oracle Academy Use Only

Oracle Financials Cloud: Enterprise

Student Guide – Volume I

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

Introduction to Oracle Cloud Enterprise

Oracle Internal & Oracle Academy Use Only

After completing this course, you should be able to:

Oracle Internal & Oracle Academy Use Only

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

Each lesson in this course:

Oracle Internal & Oracle Academy Use Only

In this course, the instructor:

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

Classroom and Other Resources:

Oracle Internal & Oracle Academy Use Only

• Oracle Technology Library on OTN: (http://www.oracle.com/technetwork/index.html)

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

Oracle Internal & Oracle Academy Use Only

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

Oracle Internal & Oracle Academy Use Only

Oracle Help Center is:

Oracle Financials Cloud: Enterprise Structures with General Ledger Implementation 1 - 6

Oracle Internal & Oracle Academy Use Only

Oracle Financials Cloud: Enterprise Structures with General Ledger Implementation 1 - 7

• Get Started with Oracle Applications Cloud

Oracle Internal & Oracle Academy Use Only

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

Link to the videos: http://docs.oracle.com/cloud/latest/financialscs_gs/financialscs_videos.htm

Oracle Financials Cloud: Enterprise Structures with General Ledger Implementation 1 - 8

• File-Based Data Import includes links to: