D96139GC10 sg1

Unauthorized reproduction or distribution prohibited Copyright 2016, Oracle and/or its affiliates
s a
h
) a
o m
p e c uide
@ h nt G
r
a tude
u m
d y -k his S
r e d se t
a r ath e to u
y (bh icens
e dd ble l
t h R ra
a r a nsfe
Bh n-tra
no
Oracle Financials Cloud:
Enterprise Structures with
General Ledger Implementation
Student Guide Volume I
D96139GC10
Edition 1.0 | July 2016 | D96876
Learn more from Oracle University at oracle.com/education/
Authors Copyright 2016, Oracle and/or its affiliates. All rights reserved.
Bruce Ingram Disclaimer

Sanjay Mall 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,
and Reviewers publish, license, post, transmit, or distribute this document in whole or in part without
the express authorization of Oracle.
Brian Aitken
The information contained in this document is subject to change without notice. If you
Abhjit Dhakephalkar find any problems in the document, please report them in writing to: Oracle University,
Julianna Dodick 500 Oracle Parkway, Redwood Shores, California 94065 USA. This document is not
warranted to be error-free.
Ivy Farren
Rashmi Goyal Restricted Rights Notice
Theresa Hickman If this documentation is delivered to the United States Government or anyone using
Barbara Kostelec the documentation on behalf of the United States Government, the following notice is
applicable:
Carolyn Luk
s a
Bernardine Rogers U.S. GOVERNMENT RIGHTS
)h a
The U.S. Governments rights to use, modify, reproduce, release, perform, display, or
Gregory Roth m
co uide
disclose these training materials are restricted by the terms of the applicable Oracle
e
license agreement and/or the applicable U.S. Government contract.
hp nt G
Deepak Seth
Xin Wang Trademark Notice
@
aofr Oracletuand/or
Linda Wong
u m
Oracle and Java are registered trademarks de its affiliates. Other names
y -k owners.
may be trademarks of their respective
i s S
Editor e d
d se t h
r
Chandrika Kennedy
a r ath e to u
Graphic Designers y (b
h ns
d le li c e
Seema Bopaiah ed
t h R rab
a r a nsfe
Kavya Bellur
B h -tra
nonKeshavamurthy
Publishers
Jayanthy
Joseph Fernandez
Contents
1 Introduction to Oracle Fusion Enterprise Structures with General Ledger

Implementation
Course Objectives 1-2
Course Approach 1-3
Oracle Fusion 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 s a
New Reference Guides 1-9 h
) a
o m
Friendly Search 1-11
p e c uide
Course Schedule 1-12
@ h nt G
Lesson Objectives 1-14 r
a tude
u m
d y -k his S
Introduction to Oracle Fusion Applications 1-15
Oracle Fusion Strategy 1-17
r e d se t
a r ath e to u
Oracle Fusion Applications: Product Families 1-18
(bh icens
Oracle Financials Cloud: Overview 1-19
y
Financials Cloud: Key Features 1-20
dd ble l
e
Implementation Discussion 1-21
R ra
r t h
a nsfe
Common Applications Configurations: Overview 1-22
a
Bh n-tra
Legal Structure 1-23
no Managerial Structure 1-24

Functional Structure 1-25
Common Application Discussion 1-26
Summary 1-28
2 Introducing Oracle Fusion Navigation

Objectives 2-2
Getting Started in Oracle Fusion Applications 2-3
Simplified Navigation 2-4
New Welcome Springboard 2-5
Favorites and Recent Items 2-6
User Interface 2-7
Dashboards 2-8
General Accounting Dashboard 2-9
Work Areas 2-10
iii
Panel 2-11
Search Panel Overview 2-12
Reports and Analytics Panel 2-13
Practice 2-1 Overview: Getting Started in Oracle Fusion Applications 2-14
Infolets versus Infotiles 2-15

Infolets Overview 2-16
Infolet Repository 2-17
Subledger Infotiles Overview 2-18
Practice 2-2 Overview: Infolets and Infotiles 2-19
Summary 2-20
3 Introducing Functional Setup Manager

Objectives 3-2
s a
Overview of Functional Setup Manager 3-3 h
) a
o m
Job Roles 3-4
p e c uide
Implementation Objects: Overview 3-5
@ h nt G
Setup Objects 3-6 r
a tude
u m
Business Objects 3-7
d y -k his S
Offerings 3-8
r e d se t
ath e to u
Offerings, Functional Areas, Options, and Features 3-9
a r
Offerings, Functional Areas, Options, and Features: Example 3-10
(bh icens
Offerings 3-11
y
e dd ble l
About Financials: Overview 3-12
t h R ra
Practice 3-1 Overview: Browsing Offerings 3-14
a r a nsfe
Configuring Offerings 3-15
Bh n-tra
Practice 3-2 Overview: Configuring Offerings (Demonstration) 3-16
no Implementation Task Flow 3-17
Implementation Project: Overview 3-18
Assign Tasks 3-19
Implementation Task Lists 3-20
Rapid Implementation Task List 3-21
Financials Task Lists 3-22
Practice 3-3 Overview: Creating an Implementation Project 3-23
Implementation Project for Ongoing Maintenance 3-24
Setup Data Export and Import: Overview 3-25
Offering Based Export 3-26
Offering Based Import 3-27
Offering Based Export and Import Process 3-28
Additional Information on Oracle Help Center 3-29
Summary 3-30
iv
4 Overview of Security
Objectives 4-2
Oracle Financial Cloud Security Methodology 4-3
Security Reference Implementation 4-4

Points to Consider When Implementing the First Project 4-5
Function and Data Security 4-7
Types of Roles 4-8
Role Inheritance 4-9
Oracle Fusion Inheritance Model 4-10
Security Example with Data Role Added 4-11
New Data Security for R11 4-12
Assigning Data Scopes to Users for New Customers Only 4-13
s a
Oracle Identity Manager 4-14 h
) a
o m
Creating Users 4-15
p e c uide
Role Provisioning Tasks 4-16
@ h nt G
Using Role Mappings 4-17 r
a tude
u m
d y -k his S
Practice 4-1 to 4-3 Overview: Using User Security 4-18
Customizing Roles 4-19
r e d se t
ath e to u
The Security Console 4-20
a r
The Security Console: Copy Feature 4-21
(bh icens
The Security Console: Compare Roles Feature 4-22
y
e dd ble l
Additional Features 4-23
t h R ra
Practice 4-4 Overview: Using the Security Console 4-24
a r a nsfe
Auditing Security 4-25
Bh n-tra
Security Resources 4-27
no Summary 4-28
5 Discussing the Vision Story and Common Applications

Objectives 5-2
Overview 5-3
Scenario 5-4
Scenario Details 5-5
Vision Corporation Analysis 5-6
Vision Corporation Structure Diagram 5-8
Vision Corporation Enterprise Structure 5-10
Vision Corporation Business Unit and Department Structure 5-11
Vision Corporation Distribution Structure 5-12
Vision Corporation Chart of Accounts Summary 5-13
Define Geographies 5-14
Geographies: Overview 5-15
v
Geography Structure 5-16
Geography Hierarchy 5-17
Geography Hierarchy Example 5-18
Geography Validations 5-19
Manage Geography Validations 5-20

Address Cleansing 5-21
Geocoding Process 5-22
Importing Geography Options 5-23
Nokia Geography Reference Data Import 5-24
File-Based Import 5-25
Managing Geography Lookups 5-26
Tax Zone Types and Zones 5-27
Run Maintain Geography Name Referencing Process 5-28
s a
Quiz 5-29 h
) a
o m
Summary 5-33
p e c uide
@ h nt G
6 Configuring Enterprise Structures r
a tude
u m
Objectives 6-2
d y -k his S
Define Enterprise Structures 6-3
r e d se t
Sharing Ledger Components Across
a t h
r Shared o u
Oracle Applications
t Components 6-5
6-4
h a
Practice 6-1 Overview: Reviewing
s e
y (b Requirements
Plan Your Implementation
i c en 6-6
e
Implementation d l l
d Simplification
e 6-7
Rapidh R b
ra Overview 6-8
r a t Implementation:
s f e
aRapid tImplementation
n Task List 6-9
Bh Rapid r a
on- ofImplementation
nChart
Process 6-10
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
vi
Completing the Accounting Configuration 6-28
Practice 6-2 Overview: Entering Data in the Rapid Implementation
Spreadsheet 6-30
Completing the Accounting Configuration 6-31
Deployment Status 6-32

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
s a
Authorities 6-40 h
) a
o m
Manage Legal Entities 6-41
p e c uide
Legal Entities Definition 6-42
@ h nt G
The Role of Your Legal Entity 6-43 r
a tude
u m
d y -k his S
Legal Entities in Transactions 6-44
r e d se t
Legal Entity and Business Units 6-45
ath e to u
Legal Entity and Divisions 6-46
a r
Legal Entity and Ledgers 6-47
(bh icens
Legal Entity and Balancing Segments 6-48
y
e dd ble l
Legal Entities and Intercompany Transactions 6-49
t h R ra
Legal Entity and Its Relationship to Intercompany Transactions 6-50
a r a nsfe
Legal Entity and Consolidation Rules 6-51
Bh n-tra
Country-Specific Legal Entity Sequences 6-52
no 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 and Reviewing Your Value Sets 7-9
Building the Chart of Accounts Structure 7-10
vii
Chart of Accounts Structure Attributes 7-11
Building the Chart of Accounts Restrictions 7-12
Chart of Accounts Instance 7-13
Account Shorthand Alias 7-14
Practice 7-2, 7-3, and 7-4 Overview: Searching for and Deploying Your Chart of
Accounts 7-16
Define Segment Values 7-17
Assign Segment Attributes 7-18
Control Accounts: Benefits 7-20
Control Accounts Explained 7-21
Practice 7-5 Overview: Entering Values 7-22
Defining Hierarchies 7-23
Account Hierarchy Purposes 7-24
s a
Account Hierarchy Example 7-25 h
) a
o m
Create Account Hierarchies 7-26
p e c uide
Create Account Hierarchies Version 7-27
@ h nt G
View Account Hierarchies 7-28 r
a tude
u m
d y -k his S
Published Account Hierarchy Example 7-29
Single Account Hierarchy 7-30
r e d se t
ath e to u
Published Account Hierarchy V2 Example 7-31
a
Troubleshooting 7-32r
(bh icens
Practice 7-6 and 7-7 Overview: Searching, Completing, and Publishing Your
y
e dd ble l
Accounting Hierarchy 7-34
t h R ra
Enabling Account Combinations 7-35
a r a nsfe
Practice 7-8 Overview: Creating an Account Combination 7-36
Bh n-tra
Manage Segment Value Attributes 7-37
no
Segment Value Security 7-38
Defining Segment Value Security Rules 7-39
General Points About Segment Value Security 7-40
Segment Value Security Examples 7-41
Segment Value Security Operators 7-42
Segment Value Security Rules and Hierarchies Example 7-43
Segment Value Security Rules with Hierarchies 7-44
Changes to an Account Hierarchy Referenced in Segment Value Security
Rules 7-45
Implementation Considerations 7-46
Implementing Segment Value Security 7-47
Segment Value Versus Data Access Set Security 7-48
Cross-Validation Rules 7-49
Cross-Validation Rules: Considerations 7-50
Dynamic Combination Creation Allowed 7-51
viii
Filters Overview 7-52
Filters and Conditions 7-53
Practice 7-9 Overview: Defining Cross-Validation Rules in a Spreadsheet 7-54
Manage an Accounting Calendar 7-55
Accounting Calendar Considerations 7-56

Start Date 7-57
Period Frequency 7-58
Period Name Format 7-59
Calendar Type 7-60
Calendars with Different Period Frequencies 7-61
Adding a Calendar Year 7-63
Practice 7-10 Overview: Verifying Your Calendar 7-64
Calendar Auditing 7-65
s a
Manage Currencies: Overview 7-66 h
) a
o m
Currency Concepts 7-67
p e c uide
Currency in Subledgers 7-68
@ h nt G
Define Currencies: Overview 7-69 r
a tude
u m
Currencies Overview 7-70
d y -k his S
r e d se t
Practice 7-11 Overview: Reviewing and Creating Currencies 7-71
ath e to u
Conversion Rate Types: Overview 7-72
a r
Cross-Currency Functionality 7-73
(bh icens
Explain Cross-Rate Rules 7-74
y
e dd ble l
Practice 7-12 Overview: Creating Conversion Rate Types 7-76
t h R ra
Daily Rates: Overview 7-77
a r a nsfe
Entering Daily Rates 7-78
Bh n-tra
Practice 7-13 and 7-14 Overview: Using Currency Rates 7-79
no Summary 7-80
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
ix
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
Practice 8-4 Overview: Defining Reporting Currencies 8-22
Define Secondary Ledgers 8-23
Secondary Ledgers: Scenarios 8-24
Secondary Ledgers: Conversion Levels 8-25
Secondary Ledger Example 8-26
Secondary Ledger Example Conclusion 8-27
Secondary Ledgers Mapping 8-28
s a
Chart of Accounts Mapping Feature 8-29 h
) a
o m
Segment Mapping Rules 8-30
p e c uide
Account Mapping Rules 8-31
@ h nt G
r
a tude
Review and Submit Accounting Configuration 8-32
u m
d y -k his S
Practice 8-5 Overview: Completing the Ledger Configuration 8-33
Balance Cubes: Overview 8-34
r e d se t
ath e to u
Balance Cubes Naming 8-35
a r
Balance Cube Dimensions 8-36
(bh icens
Manage Ledger Sets 8-37
y
e dd ble l
Practice 8-6 Overview: Creating a Ledger Set 8-38
t h R ra
Data Access Set Security: Overview 8-39
a r a nsfe
Data Access Set Security 8-40
Bh n-tra
Data Access Set Security: Example 8-42
no Practice 8-7 and 8-8 Overview: Creating a Ledger Set 8-43
Summary 8-44
9 Configuring Journal Approval

Objectives 9-2
Approval Workflow: Overview 9-3
Approval Management: Overview 9-4
Key Concepts: Stages 9-5
Key Concepts: Participants 9-6
Key Concepts: Rule Sets and Rules 9-7
Key Concepts: List Builders 9-8
Manage Task Configurations 9-10
Assignees Tree 9-12
Rule Sets 9-13
Defining Rule Settings 9-14
x
Defining Rules 9-15
IF Component 9-16
THEN Component 9-17
Rule Example 9-19
Deadlines 9-21
Notifications 9-23
Configuration 9-25
Access 9-26
Manage Approval Groups: Static 9-27
Manage Approval Groups 9-28
Manage Journal Approval Rules 9-29
Manage Journal Approval Rules Setup 9-30
Journal Approval Rule Considerations 9-31
s a
Journal Approval Rule Example 9-33 h
) a
o m
Journal Approval Hierarchies 9-34
p e c uide
Withdraw Approval 9-35
@ h nt G
Journal Status Page 9-36 r
a tude
u m
d y -k his S
Practice 9-1 Overview: Creating Journal Approval Rules 9-37
Summary 9-38
r e d se t
10 Configuring Oracle Fusiona r ath e to u
Intercompany
Objectives 10-2
y (bh icens
Intercompanyd
e d le10-3
Overview l
t h
Intercompany
f e r ab Overview 10-4
R Balancing
h ra aPayables
aExample: n s Invoice 10-5
B Example:
n r
-t Cross-Ledger Allocation Journals 10-7
o
nIntercompany Balancing: Features 10-8
Balancing Setup 10-10
Specify Ledger Options 10-11
Balancing Rules: Order of Precedence 10-12
Evaluation of Intercompany Balancing Rules 10-13
Manage Intercompany Balancing Rules 10-14
Manage Secondary and Clearing Company Balancing Options 10-17
Key Decisions and Best Practices 10-19
Practice10-1 Overview: Setting Up a New Rule 10-24
Practice 10-2 Overview: Viewing Intercompany Balancing Rules and Secondary and
Clearing Company Balancing Options 10-25
Intercompany Allocation: Overview 10-26
Intercompany Allocation: Journals 10-27
Intercompany Allocation: Transactions 10-28
Intercompany Allocation Requirements 10-29
xi
Key Setup Tasks: Create Allocation Rules 10-30
Example: Intercompany Allocations 10-31
Intercompany Allocations Example 10-37
Oracle Fusion Intercompany Transactions Overview 10-39
Intercompany General Ledger Integration 10-40

Intercompany Receivables and Payables Integration 10-41
Intercompany Transactions Dashboard 10-42
Manual Intercompany Transaction Processing Steps 10-43
Intercompany Transactions Setup 10-44
Manage Intercompany System Options 10-45
Manage Intercompany Transaction Types 10-46
Manage Intercompany Period Status 10-47
Manage Intercompany Organizations 10-48
s a
Map Intercompany Organizations 10-49 h
) a
o m
Manage Intercompany Organizations 10-51
p e c uide
Define Invoicing Options 10-52
@ h nt G
r
a tude
Manage Intercompany Customer and Supplier Assignments 10-53
u m
d y -k his S
Manage Intercompany Customer Supplier Assignments 10-54
r e d se t
Manage Intercompany Receivables Assignments 10-55
ath e to u
Define Transaction Accounts for the Intercompany Transactions 10-57
a r
Transaction Account Types 10-58
(bh icens
Intercompany Transactions: Approvals 10-59
y
e dd ble l
Example: Intercompany Transactions Approvals 10-60
t h R ra
Manage Intercompany Balancing Rules 10-61
a r a nsfe
Key Decisions and Best Practices 10-62
Bh n-tra
Intercompany Reconciliation 10-63
noReconciliation Reports 10-64
Intercompany Reporting and Analysis 10-65
Practice 10-3 Overview: Creating an Intercompany Batch 10-66
Practice 10-4 Overview: Submitting and Reviewing Reconciliation Reports 10-67
Additional References on My Oracle Support 10-68
Summary 10-69
11 Configuring Period Close Components

Objectives 11-2
Overview 11-3
Open and Close Periods Life Cycle 11-4
Accounting Period Statuses 11-5
Accounting Periods: Overview 11-6
Period Close with Oracle Financials 11-7
Period Close Section 11-8
xii
Period Close Best Practices 11-9
Practice 11-1 Overview: Opening the First Accounting Period 11-10
Period Close Checklist 11-11
Period Close Components 11-12
Allocation Concepts 11-13

Allocation Components 11-14
Defining Allocation Requirements 11-15
Generation of Allocations 11-16
Cross Ledger Intercompany Allocations 11-17
Step Down Allocation: Example One 11-18
Step Down Allocation: Example Two 11-19
Allocation Rule Concepts 11-20
Allocation Rule Deployment 11-21
s a
Allocations: Best Practices 11-22 h
) a
o m
p e c uide
Practice 11-2 Overview: Creating and Generating an Allocation Rule 11-23
Revaluation Overview 11-24
@ h nt G
Translation Overview 11-25 r
a tude
u m
d y -k his S
Revaluation and Translation Concepts 11-26
r e d se t
Revaluation and Translation Setup 11-27
ath e to u
Revaluation Process 11-28
a r
Revaluation Example 11-30
(bh icens
Practice 11-3 Overview: Creating a Revaluation 11-31
y
e dd ble l
Translation Process 11-32
t h R ra
Translation and Remeasurement Solutions 11-33
a r a nsfe
Historical Rates and Amounts 11-34
Bh n-tra
Import Journal Entries: Overview 11-35
noJournal Import Verification Process 11-36
Journal Import Validates 11-37
Reconciliation 11-38
Reconciliation Concepts 11-40
Payables Tax Reconciliation with General Ledger Report 11-41
Summary 11-42
12 Configuring Financial Reporting

Objectives 12-2
The New Financial Reporting Center: Overview 12-3
Other Reporting Tools: Overview 12-5
Access to the Financial Reporting Center 12-7
Viewing Financial Reports from the Financial Reporting Center 12-8
Live Reports and Published Snapshot Reports 12-9
Practice 12-1 Overview: Using the New Financial Reporting Center 12-10
xiii
Oracle Fusion General Ledger Balances Cube: Overview 12-11
Dimension Values in Reporting 12-12
GL Balances Cube: Dimensions 12-13
GL Balances Cube: Default Values 12-15
Dimension Values and Defaults 12-16

Smart View Overview 12-19
Smart View: Ad Hoc Analysis 12-21
Smart View: Query Designer 12-22
Creating Financial Reports 12-23
Financial Reporting Studio: Overview 12-24
Installing and Configuring the Financial Reporting Studio 12-25
Report Designer 12-26
Report Designers Standard Toolbar 12-27
s a
Financial Reporting Studio Components 12-28 h
) a
o m
Designer Toolbar 12-30
p e c uide
Grids 12-31
@ h nt G
r
a tude
Practice 12-2 Overview: Creating a Report with the Financial Reporting Studio:
u m
Defining a Grid 12-33
d y -k his S
Defining Formulas 12-34
r e d se t
ath e to u
Available Formulas 12-35
a r
(bh icens
Adding a Formula for Total Expenses 12-36
y
e dd ble l
Using Functions: Range 12-37
t h R ra
a r a nsfe
Defining a Rolling 12-Period Column 12-39
Bh n-tra
User and Grid Point of View Dimensions 12-40
no
Selecting Members 12-42
Defining the Grid and User Point of View Dimensions 12-43
Property Sheet 12-44
Property Sheet Component Objects and Features 12-45
Setting Properties 12-46
Text Box Objects 12-47
Image Objects 12-48
Adding a Logo and Title 12-49
Reviewing a Report 12-50
Practice 12-8 Overview: Reviewing a Report 12-51
Infolets Overview 12-52
Infolet Repository 12-53
xiv
General Accounting Infolets 12-54
Budgetary Control Infolets 12-58
Budget Consumed Infolet 12-59
Funds Available Infolet 12-60
Custom Infolets: Overview 12-61

Practice 12-9 Overview: Using Infolets Demonstration 12-62
Account Groups: Overview 12-63
Viewing Account Groups in the General Accounting Infolets 12-64
Defining Account Groups: Header Region 12-65
Defining Account Groups: Accounts Region 12-67
Practice 12-10 Overview: Setting Up the General Accounting Expense Infolet for All
Users Demonstration 12-68
Viewing Account Groups from the Financial Reporting Center 12-69
s a
Sunburst Tool 12-70 h
) a
o m
Sunburst Icons 12-71
p e c uide
Sunburst Options 12-72
@ h nt G
r
a tude
Practice 12-11 Overview: Viewing an Account Group from the Financial Reporting
u m
Center Demonstration 12-73
d y -k his S
r e d se t
Oracle Transactional Business Intelligence Overview 12-74
ath e to u
Oracle BI Publisher Overview 12-76
a r
Oracle Business Intelligence Publisher: Overview 12-77
(bh icens
Financial Reporting Center and Oracle BI Publisher 12-79
y
e
Summary 12-80 dd ble l
t h R ra
13 a r a Ledger
General n s feOptions
Bh Objectives
n - tra 13-2
o Suspense Accounts 13-3
nManage
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
xv
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 Profile Options 13-26
Manage Processing Schedules 13-28
Practice 13-5 Overview: Creating a Processing Schedule 13-29
Summary 13-30
14 Introducing Consolidations
Objectives 14-2
Consolidation Methods 14-3
s a
Reporting Only Consolidation Method: Example 14-4 h
) a
o m
p e c uide
Reporting Consolidation with Multiple Levels: Level One 14-6
h nt G
Reporting Consolidation with Multiple Levels: Level Two 14-7
@
Elimination Entries Example 14-8 r
a tude
u m
d y -k his S
Elimination Entries Example: Transaction 14-9
r e d se t
Elimination Entries NA Level One Example: Elimination Entry 14-10
ath e to u
Balance Transfer Consolidation Method 14-11
a r
Transfer Ledger Balances Process Parameters 14-12
(bh icens
Practice 14-1 Overview: Creating a Chart of Accounts Mapping 14-13
y
e dd ble l
Practice 14-2 Overview: Submitting the Transfer Ledger Balances Process 14-14
t h R ra
Reporting Only Versus Balance Transfer: Pros 14-15
a r a nsfe
Reporting Only Versus Balance Transfer: Cons 14-16
Bh n-tra
Oracle Hyperion Financial Management Integration Overview 14-17
noFinancial 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-5
Integration with Oracle Hyperion Planning 15-6
Importing Budget Data from a Flat File 15-7
Importing Budget Data from a Flat File: Steps 15-8
Importing Budget Data from a Spreadsheet 15-9
Importing Budget Data from a Spreadsheet: Import Correction 15-10
Practice 15-1 Overview: Uploading a Budget Using a Spreadsheet 15-11
xvi
Practice 15-2 Overview: Creating a Smart View Ad Hoc Analysis 15-12
Importing Budget Data from Smart View 15-13
Summary 15-14
Appendix A: Common Application Topics

Objectives A-2
Manage Oracle Social Network Objects A-3
Enablement Options A-4
Update Translations A-6
Practice A-1: Managing Oracle Social Network Objects Demonstration A-8
Oracle Social Network Reference Resources A-9
Define Flexfields A-10
Manage Flexfields A-11
s a
Types of Flexfields: Descriptive A-12 h
) a
o m
Flexfield Concepts A-13
p e c uide
Flexfield Segments A-14
@ h nt G
Flexfield Structure A-15 r
a tude
u m
Flexfield Context A-16
d y -k his S
Flexfield Category A-17
r e d se t
ath e to u
Flexfield Usage A-18
a r
Accessing Flexfields for Configuration A-19
(bh icens
Using the Highlight Flexfields Command A-20
y
e dd ble l
Accessing Flexfield Management Tasks and Searching for Flexfields A-21
t h R ra
Value Sets A-23
a r a nsfe
Value Set Validation A-25
Bh n-tra
Value Set Usage A-26
noDescriptive 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
xvii
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
s a
Quiz A-67 h
) a
o m
Define Attachments A-68
p e c uide
Key Concepts A-70
@ h nt G
Manage Attachment Entities A-72 r
a tude
u m
Manage Attachment Categories A-73
d y -k his S
Attachment Category Security A-75
r e d se t
ath e to u
Example A-77
Solution A-78 a r
Quiz A-79
y (bh icens
Summary A-81
e dd ble l
t h R ra
a r
Appendix n s fe
a B: Integrations and Interfaces Highlighted
Bh Objectives
t r a
on-Complete
nMost
B-2
Cloud B-3
Oracle ERP Cloud B-4
Cloud Benefits B-5
Sales and HCM B-6
On-Premises B-7
Cloud to Cloud B-8
Cloud Connectors B-9
Outbound B-10
Prepackaged ERP Cloud Integrations B-11
Cloud to Cloud B-12
Cloud to On-Premises B-13
Cloud Connectors Touchless File Based Data Import B-14
xviii
Web Services B-15
Touchless File Based Data Export B-16
Prepackaged Integration B-17
Inbound Transactions B-18
Outbound Transactions B-19

Summary B-20
s a
h
) a
o m
p e c uide
@ h nt G
r
a tude
u m
d y -k his S
r e d se t
a r ath e to u
y (bh icens
e dd ble l
t h R ra
a r a nsfe
Bh n-tra
no
xix
s a
h
) a
o m
p e c uide
@ h nt G
r
a tude
u m
d y -k his S
r e d se t
a r ath e to u
y (bh icens
e dd ble l
t h R ra
a r a nsfe
Bh n-tra
no
1
Introduction to Oracle Fusion

Enterprise Structures with
General Ledger Implementation
s a
h
) a
o m
p e c uide
@ h nt G
r
a tude
u m
d y -k his S
r e d se t
a r ath e to u
y (bh icens Copyright 2016, Oracle and/or its affiliates. All rights reserved.
e dd ble l
t h R ra
a r a nsfe
Bh n-tra
no
Course Objectives
After completing this course, you should be able to:

Use Oracle Functional Setup Manager (FSM) to implement
Oracle Fusion Financials.

Understand Financial Security.
Discuss the common applications configuration for Oracle
Fusion Financials.
Describe the configuration of enterprise structures and the
related Vision Corporation story. s a
h a
Configure Oracle Fusion General Ledger. m)
c o ide

pe t Gu
h
a r@ den
- k um Stu
e d dy this
t h r u se
a r a e to
e dd ble l
t h R ra
a r a nsfe
Bh n-tra
no
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 Fusion Financials.

May also include one or more of the following activities:
Complete a portion of the case study in FSM.
Discuss key decisions and best practices.
Complete an activity or knowledge assessment task.
s a
h
) a
o m
p e c uide
@ h nt G
r
a tude
u m
d y -k his S
r e d se t
a r ath e to u
e dd ble l
t h R ra
ara tthe
In thishcourse, n s fe
instructor:
a
B n- rintroductory
Presents
o modules.
n
Acts as a business analyst representing the case study customer.
Imparts information to assist you with the Oracle Fusion Financials implementation.
Provides review sessions as needed.

Oracle Fusion Implementation Resources
Classroom and Other Resources:

Oracle Financials Cloud: Enterprise Structures and General
Ledger Implementation Student guide (This guide and its

companion course)
Oracle Fusion Applications Help in the Applications
Oracle Fusion Technology Library on OTN
My Oracle Support (MOS)
Oracle Fusion Cloud Library s a
a
)h
Your instructor m
e co uide
Other students hp G
a r@ dent
- k um Stu
e d dy this
t h r u se
Oracle Financials a r a Implementing
Cloud: e t o Subledger Accounting
h
(b icen s
d y
d ble l
Copyright 2016, Oracle and/or its affiliates. All rights reserved.
e
R ra
r t h fe
aFusionnsTechnology
h a
Oracle
t r a Library on OTN: (http://www.oracle.com/technetwork/index.html)
B - Support (MOS) (https://support.oracle.com/): Including these documents:
non
My Oracle
- Getting Started with Oracle Fusion Applications: Common Implementation, Article ID
1387777.1 on Oracle Support
- Oracle Fusion Applications: Financials Reporting (Document 1458904.1)
Oracle Help Center (http://docs.oracle.com/cloud/latest/financialscs_gs/index.html): Including
these Oracle Financials Cloud books:
- Getting Started with Your Financials Cloud Implementation
- Implementing Enterprise Structures and General Ledger
- Using Common Features including Infolet Personalization topics
- Customizing the Applications for Functional Administrators including Infolet Customization
topics
- Implementing Financials for Asia/Pacific
- Implementing Financials for EMEA
- Using Oracle Social Network
- Security Reference for Oracle Financials Cloud
- Creating Analytics and Reports

- Using Analytics and Reports
- Using Financials for Asia/Pacific
- Using Financials for EMEA
- Using General Ledger
Oracle Hyperion Books including:
- Calculation Manager Designer's Guide
- Data Relationship Management Administrator's Guide

- Data Relationship Management Oracle GL Integration Guide
- Data Relationship Management User's Guide
- Enterprise Performance Management Workspace Administrator's Guide
- Enterprise Performance Management Workspace User's Guide
- Financial Reporting Administrator's Guide
- Financial Reporting Studio User's Guide
- Financial Reporting Charting Guide NEW s a
h
) a
- Financial Reporting User's Guide
o m
- Smart View for Office User's Guide
p e c uide
@ h nt G
r
a tude
u m
d y -k his S
r e d se t
a r ath e to u
y (bh icens
e dd ble l
t h R ra
a r a nsfe
Bh n-tra
no

Oracle Help Center: docs.oracle.com
s a
a
)h
m
co uide
e
@ hp nt G
m ar tude
y - ku is S
e d d th
r e
r a th to us
( b ha nse
d d y l i ce Copyright 2016, Oracle and/or its affiliates. All rights reserved.
R e able
th sfer
araCenter
OraclehHelp
t r a n is:
B
on-hub for all documentation and tutorials.
Central
n
Organized by major product categories including Cloud, Applications, Middleware, and
Database.
Cloud Application pages are organized by Cloud.

Oracle Cloud Application Service Pages
s a
h
) a
o m
p e c uide
@ h nt G
r
a tude
u m
d y -k his S
r e d se t
a r ath e to u
e dd ble l
t h R ra
a r
Consistent n s fe content, and link format for Cloud service pages.
aorganization,
Bh n-tra
GetoStarted
n
Videos
Books
Friendly task panel to change focus from Cloud to:
Applications
Middleware
Database
Other Documentation

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

Get Started with Oracle Applications Cloud
Set Up Oracle Applications Cloud

Customize Oracle Applications Cloud
Get Started with Oracle Financials Cloud
Use General Ledger
Use Payables Invoice to Pay
s a
Use Receivables Credit to Cash a
)h
Use Other Oracle Financials Cloud Products co m
p e u ide
h nt G
Use Oracle Social Network to Improve Collaboration
@
r
a tude
Use Oracle Transactional Business u m
Intelligence
k is S for Financials
y -
Cloud dd th
re use
r t h
a e to
a
e dd ble l
t h R ra
aravideos:
Link tohthe n s fe
http://docs.oracle.com/cloud/latest/financialscs_gs/financialscs_videos.htm
B n-Ledger
Use General
tra includes the following videos:
no
Create journal approval rules.
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.

New Reference Guides
File Based Data Import

includes links to:
Spreadsheets templates.
Load and import NEW
processes.
Tables and Views includes:
Columns
Primary and Foreign a
Keys a s
m )h
Indexes
e co uide
SOAP (Simple Object @ hp nt G
Access Protocol) Web m ar tude
Services y - ku is S
e d d th
r e
r a th to us
( b ha nse
R e able
th sfer
ara tranRepository
OraclehEnterprise has been decommissioned and the following new guides are on
B
the Oracle n - Help Center at
Cloud
no
http://www.oracle.com/webfolder/technetwork/docs/HTML/oer-redirect.html.
File Based Data Import (FBDI) is used to load data into Oracle Fusion Applications from
external sources, such as legacy systems and third-party applications. The File Based
Data Import for Oracle Financials Cloud Guide includes links to:
- Spreadsheets used to load data into Oracle Fusion Applications from external
sources, such as legacy systems and third-party applications. The spreadsheet
templates 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 Fusion Applications.
Tables and Views for Oracle Financials Cloud Guide includes:
- The tables with the basic information about the table columns, primary and foreign
keys, and indexes.
- The views, columns, and query details that are associated with each view.

SOAP (Simple Object Access Protocol) Web Services for Oracle Financials Guide
include:
- Business Object Services relationships, operations, and security.
- Service Data Objects relationships and attributes.
Note: Use SOAP web services to integrate with or extend Oracle Applications Cloud.
Through web services, you can integrate heterogeneous applications within the enterprise or
expose business functions to Oracle Cloud partners and customers over the Internet.
s a
h
) a
o m
p e c uide
@ h nt G
r
a tude
u m
d y -k his S
r e d se t
a r ath e to u
y (bh icens
e dd ble l
t h R ra
a r a nsfe
Bh n-tra
no

Friendly Search
s a
)h a
m
co uide
e
@ hp nt G
m ar tude
y - ku is S
e d d th
r e
r a th to us
( b ha nse
R e able
r h sfer
atsearch
a
h -tran entry: Just type your topic in the field.
Simple
B
nonlinks to the topic.
Comprehensive view of search results: Results show the guide as well as the topic, with
direct
Number of results and context displayed.
Refine Search task panel enables you to reduce the number of results.
Breadcrumbs appear at the top of topics you select to allow easy return to the list of
results.

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

Day One:
Introducing Oracle Fusion Financials

Introducing Functional Setup Manager for Financials
Exploring Financial Security
Configuring Common Applications
Day Two:
a
Configuring Enterprise Structures
) has
Configuring General Ledger o m e
c
pe t G u i d
h
a r@ den
- k um Stu
e d dy this
t h r u se
a r a e to
e dd ble l
t h R ra
a r a nsfe
Bh n-tra
no

Course Schedule
Day Three:
Configuring General Ledger
Configuring Journal Approval

Configuring Intercompany Balancing Rules
Day Four:
Configuring Period Close Components
Configuring Financial Reporting
s a
Day Five: h
) a
Configuring General Ledger Options o m
p e c uide
Introducing Consolidations @ h nt G
r
a tude
Introducing Budgets k u m S
d d y- this Lets Begin!
t h re use
a r a e to
e dd ble l
t h R ra
r e
a nissfprovided
a
Additional material in the appendixes for your reference.
Bh n-tra
no

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

Introduce the Oracle Fusion Applications.
Discuss Oracle Financials Cloud.

Discuss your implementation strategy.
Discuss the Common Financial Applications Configuration.
Identify your implementation needs.
s a
h
) a
o m
p e c uide
@ h nt G
r
a tude
u m
d y -k his S
r e d se t
a r ath e to u
e dd ble l
t h R ra
a r a nsfe
Bh n-tra
no

Introduction to Oracle Fusion Applications
Oracle Fusion Applications are:

An integrated suite of business applications.
Engineered to work together.

Designed to ensure that your enterprise can be modeled.
s a
a
)h
m
co uide
e
@ hp nt G
m ar tude
y - ku is S
e d d th
r e
r a th to us
( b ha nse
R e able
th sfer
ara trApplications
OraclehFusion a n are:
B -
n- nConnects and automates the entire flow of business processes across both front
An o integrated suite of business applications that:
and back office operations.

- Addresses the needs of a global enterprise.
Engineered to work together, allowing users to streamline the setup process by sharing
common setup data across applications.
Designed to ensure that your enterprise can be modeled to meet legal and management
objectives.
The decisions about your implementation of Oracle Fusion Applications are affected by your:
Industry
Business unit requirements for autonomy
Business and accounting policies
Business functions performed by business units and, optionally, centralized in shared
service centers
Locations of facilities

Introduction to Oracle Fusion Applications
s a
h
) a
o m
p e c uide
@ h nt G
r
a tude
u m
d y -k his S
r e d se t
a r ath e to u
e dd ble l
t h R ra
a r a nsfe
Bh n-tra
no

Oracle Fusion Strategy
s a
)h a
m
co uide
e
@ hp nt G
m ar tude
y - ku is S
e d d th
r e
r a th to us
( b ha nse
R e able
r th sfer
aFusion
h a
The Oracle
t r a nApplications strategy sets the new standard for innovation with its
B -
complete, standards-based platform and service-oriented architecture, and is built on two
non
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 Fusion 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 Fusion Applications: Product Families
Financial Management
Human Capital Management
Supply Chain Management

Project Portfolio Management
Procurement
Customer Relationship Management
Enterprise Governance, Risk, and Compliance Management
s a
)h a
m
co uide
e
@ hp nt G
m ar tude
y - ku is S
e d d th
r e
r a th to us
( b ha nse
R e able
th sfer
ara trApplications
OraclehFusion a n provide:
B n- modular suite of applications. You have a choice of functionalitywhether
A complete,
n o
its 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 customers enterprise information technology strategy on the Oracle
Cloud.
Oracle Fusion 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.
s a
)h a
m
co uide
e
@ hp nt G
m ar tude
y - ku is S
e d d th
r e
r a th to us
( b ha nse
R e able
th sfer
ara tranCloud
OraclehFinancials with Oracle Fusion Applications provides:
B
Open, -
nstandards-based enterprise applications that function in the cloud through a web
n o
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.
s a
h
) a
o m
p e c uide
Financials
@ h nt G
r
a tude
u m
d y -k his S
r e d se t
a r ath e to u
e dd ble l
t h R ra
a r
Innovative, n s fe multidimensional reporting platform.
a embedded,
Bh n-tra accounting of multiple reporting requirements.
Simultaneous
no
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.
s a
Suppliers. h
) a
o m
p e c uide
@ h nt G
r
a tude
u m
d y -k his S
r e d se t
a r ath e to u
e dd ble l
t h R ra
a r
Instructor-led n s fe on the students implementations.
a discussion
Bh ofn-questions
Examples
tra to ask the students:
no
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
s a
)h a
m
co uide
e
@ hp nt G
m ar tude
y - ku is S
e d d th
r e
r a th to us
( b ha nse
R e able
th sfer
Everyh ara trahas
enterprise n three fundamental structures: Legal, Business (managerial), and
B
Oracle n on- these
Functionalthat
Fusion,
are used to describe its operations and provide a basis for reporting. In
structures are implemented by using the chart of accounts and
organizations. Although many alternative hierarchies can be implemented and used for
reporting, you likely have one primary structure that organizes your business into divisions,
business units, and departments aligned by your strategic objectives.
This section introduces the Oracle Fusion Financial Applications concepts for:
Legal structure: Defines your legal entities.
Managerial structure: Defines your divisions and business units.
Functional structure: Defines your departments and organizations.

Legal Structure
s a
)h a
m
co uide
e
@ hp nt G
m ar tude
y - ku is S
e d d th
r e
r a th to us
( b ha nse
R e able
atinhthenslide r
feshows
a r
The graphic
h a s a typical group of legal entities, operating various business
B t r
n- organizations.
and functional
n o
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
s a
)h a
m
co uide
e
@ hp nt G
m ar tude
y - ku is S
e d d th
r e
r a th to us
( b ha nse
R e able
r h sfer
atmanaging
h a
Successfully
t r a n multiple businesses requires that you segregate them by their
B n-
strategic objectives and measure their results. Although related to your legal structure, the
nomanagerial
business 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
s a
)h a
m
co uide
e
@ hp nt G
m ar tude
y - ku is S
e d d th
r e
r a th to us
( b ha nse
R e able
a
Straddlingr ferbusiness organizations is a functional organization structured around
athethlegalnsand
Bhandntheir
people - tracompetencies. For example, sales, manufacturing, and service teams are
noorganizations.
functional
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? a
a s
Where are you on the spectrum of centralization versus
m )h
o ide
decentralization? ec h p t Gu
a r@ den
- k um Stu
e d dy this
t h r u se
a r a e to
e dd ble l
t h R ra
a r
Instructor-led n s fe on various aspects of the students enterprise structure. This
a discussion
Bh nhelps
discussion - trathe students think about the levels within their organization that need to be
noon and secured. The discussion leads into the next chapters on the various
reported
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 a
requirements and local statutory reporting requirements? h a s
m
Do you tend to prefer a corporate first or an autonomous
) local
c o i d e
approach? h pe t Gu
a r@ devery
Where are you on a spectrum of centralization, n centralized
or decentralized? - k um Stu
y d st hi
r e d e
r a t h t o us
( b ha nse
R e able
a r ath nsfer
Bh n-tra
no

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

Introduce the Oracle Fusion applications.
Discuss Oracle Financials Cloud.

Discuss your implementation strategy.
Discuss the Common Financial Applications Configuration.
Identify your implementation needs.
s a
h
) a
o m
p e c uide
@ h nt G
r
a tude
u m
d y -k his S
r e d se t
a r ath e to u
e dd ble l
t h R ra
a r a nsfe
Bh n-tra
no

2
Introducing Oracle Fusion

Navigation
s a
h
) a
o m
p e c uide
@ h nt G
r
a tude
u m
d y -k his S
r e d se t
a r ath e to u
e dd ble l
t h R ra
a r a nsfe
Bh n-tra
no
Objectives

Navigate Oracle Fusion Applications.
Explore dashboards.
Examine panels.
Review infolets and infotiles.
s a
h
) a
o m
p e c uide
@ h nt G
r
a tude
u m
d y -k his S
r e d se t
a r ath e to u
e dd ble l
t h R ra
a r a nsfe
Bh n-tra
no

Getting Started in Oracle Fusion Applications
s a
)h a
m
co uide
e
@ hp nt G
m ar tude
y - ku is S
e d d th
r e
r a th to us
( b ha nse
R e able
th sfer
ara trApplications
OraclehFusion a n are:
B
Designedn- from the ground up, using the latest technology advances and incorporating
n o
best practices gathered from thousands of customers.
Completely open, service-enabled enterprise applications.
Designed with features for the best-in-class user-interface designs and workflows that
optimize usability and deliver business value.
All functionality revolves around the Oracle Fusion Applications Welcome Springboard, which
can be personalized.
Note: The Welcome Springboard view changes based on your roles and privileges.

Simplified Navigation
Enhanced user interface features include: NEW

Welcome Springboard
Infolets
Infotiles
Panels
s a
)h a
m
co uide
e
@ hp nt G
m ar tude
y - ku is S
e d d th of Infolets
r Examplee
r a th to us
( b ha nse
R e able
a
Oracles r
focus s fer an exceptional user experience pervades the Oracle Applications
athon nproviding
BhCreating
Cloud. n - traa compelling, pleasing user interface that provides only what you need, right
noneed it, is of the highest priority. Advantages include:
when you
Detailed list of all the work areas that you have access to using the improved navigator.
Logical, related tasks organized into groups and displayed in a pre-determined order set
by the application.
Ability to configure tasks to meet your business needs.
Access to work areas and dashboards by clicking on the icons on the Welcome
Springboard or from the Navigator entries.

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

announcements.
Page control navigation located at the top of the pages to

access the Welcome Springboard and the infolet pages.
Navigator to access additional applications.
s a
)h a
m
co uide
e
p Control
@ hPage n t G Dots
r
a tude
u m
d y -k his S
r e d se t
a r ath e to u
e dd ble l
t h R ra
a
Navigater a Welcome
to: n s feSpringboard
Bh n-tefficiency
Improve
ra and productivity of your workforce with the simplified Welcome
no
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
s a
a
)h
m
co uide
e
@ hp nt G
m ar tude
y - ku is S
e d d th
r e
r a th to us
( b ha nse
R e able
r athWelcome
s f er
Navigatea
h -tran Springboard > Select the Favorites and Recent Items icon.
to:
B
on and Recent Items menu enables users to return to flows that have been
The Favorites
recentlynaccessed, usually within, but not limited to, a single session.

User Interface
Global Area
Panel
Tabs
Infotiles Area
s a
h
) a Panel
o m
Section p e c uide
@ h nt G
r
a tude
u m
d y -k his S
r e d se t
a r ath e to u
e dd ble l
t h R ra
a
Navigate r a Payables
to: n s fe> Invoices
Bh ncan
Each page - a
trbe
no in the divided
components
into components. The slide shows an example of the main
Oracle Fusion User Interface.
Global Area: Contains links to help you navigate user interfaces, personalized links and
tools, and the name of the user who is signed in.
Infotiles Area: Contains infotiles that give you a quick glance at key performance
indicators and that can be expanded for more details.
Section: Contains the transaction or form that requires creation, editing, or review.
Panel: Contains links to tasks, process, and reports and enables search on some
panels.
Panel Tabs: Opens several different panels including the Tasks, Search, and Report
panels.

Dashboards
Oracle Fusion dashboards provide:

Information summaries: View of the big picture as well as
prioritization.
Information monitoring: Quick action and further exploration.
Information containers: Multiple regions, dashboards, graphs,
and other objects.
s a
h
) a
o m
p e c uide
@ h nt G
r
a tude
u m
d y -k his S
r e d se t
a r ath e to u
e dd ble l
t h R ra
a
Navigate rto: n s fe > Collections Dashboard
a Collections
Bh nof-dashboards
Two types
tra are available:

no
Role-based: Examples include General Accounting, Line Manager, and Collector
dashboards.
Business intelligence-driven: Examples include Balance Sheet and Sales Pipeline
dashboards.

General Accounting Dashboard
s a
a
)h
m
co uide
e
@ hp nt G
m ar tude
y - ku is S
e d d th
r e
r a th to us
( b ha nse
R e able
r athGeneral
s f er
a
h -tran
Navigate to: Accounting Dashboard
B
nonincluding
The General
functionality
Accounting Dashboard is the main dashboard for Oracle Fusion General Ledger
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
s a
)h a
m
co uide
e
@ hp nt G
m ar tude
y - ku is S
e d d th
r e
r a th to us
( b ha nse
R e able
r athGeneral
s f er
a
h -tran
Navigate to: Accounting > Period Close
B
on isclosing
A work area
nand
opening
a grouping of similar tasks. The Period Close work area includes tasks for
accounting periods for Oracle Fusion General Ledger and subledgers.

Panel
Click on the Tasks icons to open the Panel.

Use the Panel tabs to:
Access features without leaving the current application.

Perform searches.
Tasks Panel Tab
Run reports.
Tasks
Panel
a
h a s
m )
o
c uide
p e
h nt G
r @
a tude
u m
d y -k his S
r e d se t
a r ath e to u
e dd ble l
t h R ra
a
Navigate rto: n s fe > Billing
a Receivables
Bh nan-tanchored
The panel,
ra
component on the right side of a page, contains one or more vertical
tabs ton
o
perform actions such as search, run reports, and view integrated conversations in the
context of the current task.
Open the panel by clicking on one of the panel tabs. The panel is collapsed by default.
Use the slide-out panel to access features directly from any screen without leaving the
current application or navigating through different roles or hierarchies.
View the tasks available for your user role.

Search Panel Overview
Use the Search Panel to perform local searches on the work area
you are currently using.
Search Panel Tab
Search
a
s Panel
) ha
c om ide
h pe t Gu
a r@ den
- k um Stu
e d dy this
t h r u se
a r a e to
e dd ble l
t h R ra
Navigatea rto: n s fe > Billing
a Receivables
Bh n-trapanel to perform a local search based on the work area you are currently
Use the Search
no on the Search panel tab to expand the Search panel and perform a search.
using. Click
For example, in the Billing work area, you can quickly search for a transaction by Transaction
Number, Transaction Date, or Bill-to Customer Account Number using the Search panel.

Reports and Analytics Panel
Use the Reports and Analytics panel to run any reports and
analytics available to your user role.
Reports and
Analytics
Report Panel Tab Panel
s a
a
)h
m
co uide
e
@ hp nt G
m ar tude
y - ku is S
e d d th
r e
r a th to us
( b ha nse
R e able
r s f er
athReceivables
Navigatea
h -tran
to: > Billing
B
Click on thenReports and Analytics panel tab to expand the panel and select the reports and
noyou
analytics want to view.

Practice 2-1 Overview: Getting Started in Oracle Fusion
Applications
This practice covers the following topics:
Signing in to Oracle Fusion Applications.
Exploring the following user interfaces:

Global Area including:
Accessibility
Help
Search
Personalize a
Setting and Actions menu h a s

m )
Navigator and Welcome Springboard o
c uide
Work Area and Panels p e
h nt G
Search r @
a tude
u m
y -k his S
Signing out of Oracle Fusion Applications.
d
r e d se t
a r ath e to u
e dd ble l
t h R ra
a r a nsfe
Bh n-tra
no

Infolets versus Infotiles
NEW
Infolet
An interactive container in a simplified user interface that
provides key information and user actions including:

Refreshing and running processes to update the data.
Drilling into the details behind the data.
Changing the displayed views, names, and information.
Infolets are combined on an Infolet Page that is accessed
using a page control dot on the Welcome Springboard. a
a s
Infotile m )h
A tile component that displays key information co uaidtopic
about
e e or
p
h tiles t Gon a
r @
object as part of a scrolling strip of information
a tude n
specific page. u m
d y -k his S
Each tile links to a table ofre d
detailed t
einformation.
r a th to us
( b ha nse
R e able
a r ath nsfer
Bh n-tra
no

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
s a
)h a
m
co uide
e
@ hp nt G
m ar tude
y - ku is S
e d d th
r e
r a th to us
( b ha nse
R e able
r athWelcome
s f er
a
h -tran Springboard
Navigate to:
B
nontofrom
Use infolets
way directly
view information from different sources at a glance in an efficient and timely
the Welcome Springboard. You have the right information instead of just
more data to sift through.
Mobile device support is available to take your work on the go, enabling you to close your
books quickly. You can spot trends and exceptions to gain insights about your financial
results in real-time.
Infolets are available for General Ledger, Intercompany, Budgetary Control, and Cash
Management.
Note: You can only view those infolets that you have permission to access.

Infolet Repository
The Infolet Repository displays the infolets available for each

infolet dashboard.
Infolet Repository Icon
s a
a
)h
m
co uide
e
@ hp nt G
m ar tude
y - ku is S
e d d th
r e
r a th to us
( b ha nse
R e able
r athWelcome
s f er
a
h -tran Springboard > General Accounting Infolets dot
Navigate to:
B

nonrepository displays the available set of infolets based on your access privileges.
The infolet
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.

Subledger Infotiles Overview
Use infotiles to:

Obtain detailed information from a single page.
Orient yourself in intense, repetitive, and focused tasks.
Infotile
s a
h a
) Tile
Select
m
o
c uide
p e
h nt G
r @
a tude
u m
d y -k his S
r e d se t
a r ath e to u
e dd ble l
t h R ra
a
Navigate r a Payables
to: n s fe> Invoices.
Bh n-tra to scan information across areas of interest.
Useoinfotiles

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

Practice 2-2 Overview: Infolets and Infotiles

Navigating to the General Accounting infolets.
Navigating to the Payables infotiles.

Note: Sign in with Casey.Brown and your assigned password to
perform this practice.
s a
h
) a
o m
p e c uide
@ h nt G
r
a tude
u m
d y -k his S
r e d se t
a r ath e to u
e dd ble l
t h R ra
a r a nsfe
Bh n-tra
no

Summary

Navigate Oracle Fusion Applications.
Explore dashboards.
Examine panels.
Review infolets and infotiles.
s a
h
) a
o m
p e c uide
@ h nt G
r
a tude
u m
d y -k his S
r e d se t
a r ath e to u
e dd ble l
t h R ra
a r a nsfe
Bh n-tra
no

3
Introducing Functional Setup

Manager
s a
h
) a
o m
p e c uide
@ h nt G
r
a tude
u m
d y -k his S
r e d se t
a r ath e to u
e dd ble l
t h R ra
a r a nsfe
Bh n-tra
no
Objectives

Describe Oracle Fusion Functional Setup Manager.
Browse and configure offerings and functional areas.

Review the Oracle Fusion Financials offering.
Review the reports associated with the Oracle Fusion
Financials offering.
Create an implementation project.
Explain setup data export and import. s a
h
) a
o m
p e c uide
@ h nt G
r
a tude
u m
d y -k his S
r e d se t
a r ath e to u
e dd ble l
t h R ra
a r a nsfe
Bh n-tra
no

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

application that provides:
Single interface.
Guided processes.
Configurability of the Oracle Fusion offerings.
Predefined, guided task lists.
Export and import capability.
a
Set of comprehensive reports. as )h
m
co uide
e
@ hp nt G
m ar tude
y - ku is S
e d d th
r e
r a th to us
( b ha nse
R e able
r athinterface
s f er
A a
h -tran lifeforcycle.
single all of the setup and maintenance phases across the complete
Bimplementation
non processes that facilitate navigating through planning, implementation,
Guided
deployment, and ongoing maintenance.
Configurability of the Oracle Fusion offerings to mold the offerings to fit the business
needs.
Predefined, guided task lists for full end-to-end visibility of all setup requirements, which
enable users to quickly implement what they need.
Export and import capability to let enterprises set up one instance and move the setup
and task lists to other instances.
Set of comprehensive reports to give full visibility to setup at any time.

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

Oracle Fusion Functional Setup Manager:
Application Implementation Manager

Application Implementation Consultant
s a
a
)h
m
co uide
e
@ hp nt G
m ar tude
y - ku is S
e d d th
r e
r a th to us
( b ha nse
R e able
th sfer
arathese
Usershwith
t r a n can:
roles
B
Gather n-Requirements for the Implementation: Perform this task outside of Functional
n o
Setup Manager. No setup activities are required in the Functional Setup Manager.
Configure Offerings: Define the parameters of the implementation by selecting the
options and features to be implemented for each offering.
Note: Read-only functionality to a limited number of tasks can be accessed even if these
roles are not assigned.

Implementation Objects: Overview
Different types of implementation objects are available.

Setup objects
Business objects
s a
h
) a
o m
p e c uide
@ h nt G
r
a tude
u m
d y -k his S
r e d se t
a r ath e to u
e dd ble l
t h R ra
ara tinclude:
Setuphoptions n s fe
B n- rafunctional areas, and options
Offerings,
no
Processes and features
Tasks and task lists
Business objects include:
Business documents such as person documents and purchase orders.
Transactions such as invoices, payments, and journals.

Setup Objects
Encompass multiple setup entities:

Business objects
Tasks and task lists

Processes
Features
Options, functional areas, and offerings
Consume all offerings applicable to your implementation.
Exist for the Oracle Fusion Applications. s a
h a
Cannot be modified. m) co uide
e
@ hp nt G
m ar tude
y - ku is S
e d d th
r e
r a th to us
( b ha nse
R e able
A setupa r
business s feris a self-contained representation of a business entity supported by a
ath nobject
Bhtask.nThese
setup - tra are logical representations of real-world objects. Setup business objects
nothe data entered when you perform setup tasks. Setup data entered by way of a
represent
setup task is stored in the table associated with the corresponding business object. For
example, Primary Ledger is the business object of the setup task called Manage Primary
Ledger. When the Manage Primary Ledger task is performed, the data entered is stored in the
tables associated with the Primary Ledger business object. You can:
Create custom setup objects for use with third-party or custom applications.
Create new offerings, options, features, and task lists using setup objects delivered with
the system.

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

complete business document, transaction, or other
high-level business concept.

Comprise a set of attributes and a set of methods.
Attributes store the data related to the entity you are modeling.
Methods manipulate the value of these attributes, or perform
calculations based on their values.
Are used as the lowest level for data export and import. a
a s
m )h
e co uide
@ hp nt G
m ar tude
y - ku is S
e d d th
r e
r a th to us
( b ha nse
R e able
r ath enable
s f er
h a
Business objects
t r a n you to model and develop the business entities that are part of your
B
process. n-
no objects simplifies the management of the data in your process by
Using business
encapsulating the data and business behavior associated with the business entity it
represents.
Typically business objects represent entities in an actual business, but you can also use them
to encapsulate business logic that is not associated with any particular entity.
A Financial example of a business object is a Payables invoice, which has the following
business entities:
Supplier
Invoice Header
Invoice Lines
Distributions

Offerings
The two predefined financial implementation offerings are:

Oracle Fusion Financials offering: Includes Oracle Fusion
General Ledger and Oracle Fusion Subledger Accounting

application features, as well as at least one of the subledger
financial applications.
Oracle Fusion Accounting Hub offering: Includes Oracle
Fusion General Ledger and Oracle Fusion Subledger
Accounting application features integrated with an existing a
enterprise resource planning (ERP) system or third-party h a s
)
om e
application to enhance the current reporting and canalysis.

h p e G uid
***The focus of this course is the a r@ dFusion
Oracle e nt
- k um Stu
Financials Offering.***
e d dy this
t h r u se
a r a e to
e dd ble l
t h R ra
a r a nsfe
Bh n-tra
no

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

processes is represented by selecting:
Offerings
Functional areas
Options
Features
s a
)h a
m
co uide
e
@ hp nt G
m ar tude
y - ku is S
e d d th
r e
r a th to us
( b ha nse
R e able
r athcontain
s f er
a
h -tran all of the tasks required to implement the top-level business process.
Offerings
B
nonan implementation.
Functional areas are logical groupings in an offering that you can choose to implement
during
Options are within a functional area and represent optional business processes possible
within that offering.
Features are used to define the business rules for the implementation and how the
transactions of the corresponding business process work. Features are available in
offerings, functional areas, options, or other features.

Offerings, Functional Areas, Options, and Features:
Example
s a
h
) a
o m
p e c uide
@ h nt G
r
a tude
u m
d y -k his S
r e d se t
a r ath e to u
e dd ble l
t h R ra
a
As shownr a nsfe
here:
Bh n-tra is Oracle Fusion Financials.
Theooffering
n
A functional area in that offering is Expenses.
An option in the Expenses Functional Area is Corporate Card with Expenses.
The feature is the business rules that define how the corporate card with expenses
works.
Note: An option in the Financial offering > Financial Business Intelligence Analysis functional
area is Employee Expenses Business Intelligence Analytics.
The ability to select options enables you to implement only those options and features
relevant to your implementation.
Selecting the combination of offerings, functional areas, options, and features generates the
appropriate task list dynamically.

Offerings
s a
)h a
m
co uide
e
@ hp nt G
m ar tude
y - ku is S
e d d th
r e
r a th to us
( b ha nse
R e able
r th sfer
aSetup
a
h -tranand Maintenance
Navigator >
B n
OfferingsoSection:
n
Select from the drop-down list to view all or only Provisioned offerings. The offerings are
displayed in alphabetical order.
Use the scroll bar under the icons to move quickly through the offerings.
About and Administration sections: Both are updated and provide links based on the offering
selected.
About <Name of the offering>: Provides links to documentation that assists with the
setup of your implementation.
Administration: Provides the Configure button, which changes to the Actions and Setup
buttons after you finish configuring the offering.
- To change the configuration, use the Actions button.
- To view or perform other tasks for the configuration, use the Setup button.

About Financials: Overview
Provides an offering description.

Lists reports:
With detailed information about what type of transactions and

functionality are available within the offerings.
Available in HTML, PDF, and Excel formats.
s a
h
) a
o m
p e c uide
@ h nt G
r
a tude
u m
d y -k his S
r e d se t
a r ath e to u
e dd ble l
t h R ra
a
Navigate rto:
fe Maintenance > About Financials
a Setupnsand
Bh n-tContent
Offering
ra Guide
no- Describes the detailed contents of the offering for the current version of the
application.
- Provides a functional description of the components of the offering.
Associated Features
- Displays the options, functional areas, and features for the offering used for
detailed application configuration decisions.
- Displays a list of features available with the offering, including what level the
feature is associated with, as well as the choices available.
- Depicts the dependency between the offerings and their options and features.
Setup Task Lists and Tasks
- Lists the setup tasks and task lists for an offering and functional area, related to
application configuration.
- Displays the setup tasks required to implement the functionality available in the
offering.

Related Business Objects
- Lists the business objects that the offering uses.
- Lists the applicable web service used for the export and import process.
Related Enterprise Applications
- Lists the enterprise applications the offering requires for functional setup and
transactional tasks.
- Specifies the application required based on transaction type for special offerings.
s a
h
) a
o m
p e c uide
@ h nt G
r
a tude
u m
d y -k his S
r e d se t
a r ath e to u
y (bh icens
e dd ble l
t h R ra
a r a nsfe
Bh n-tra
no

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

Setup and Maintenance page
About section reports:

Offering Content Guide
Setup Task Lists and Tasks
Related Business Objects
Related Enterprise Applications
Tasks panel s a
)h a
m
co uide
e
@ hp nt G
m ar tude
y - ku is S
e d d th
r e
r a th to us
( b ha nse
R e able
r th sfer
alook
h a
Specifically
t r atnthe Setup Task Lists and Tasks in the HTML format. Filter the required
a
B
versus the n -
nonrequired setups.
no

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

appropriate reports.
Select the offerings, functional areas, options, and features to

be implemented.
If an offering is selected but none of its options is selected, only
the basic tasks needed to implement the base functionality are
included in the task list.
Only the offerings and options selected during this process are
available when an implementation project is created. s a
)h a
Configured offerings can be updated at a later date, mparticularly
co uide
e
if offerings are implemented with a phased approach.
p
@ h nt G
r
a tude
u m
d y -k his S
r e d se t
a r ath e to u
e dd ble l
t h R ra
a
Features r a associated
are n s fe with some offerings or options. Each feature provides two or more
Bh The
choices. n - tra selection types for choices are:
valid
noor No: Indicates whether to include or to exclude the functionality.
Yes
Single Choice: Choices are mutually exclusive.
Multiple Choices: More than one choice can be selected.
Note: Additional features may appear if any dependency has been defined and the
corresponding feature choice has been selected.

Practice 3-2 Overview: Configuring Offerings
(Demonstration)
This demonstration covers the following topics:
Reviewing the Configure Offerings page.
Expanding to see the options.

Viewing the Select Feature Choices option.
s a
h
) a
o m
p e c uide
@ h nt G
r
a tude
u m
d y -k his S
r e d se t
a r ath e to u
e dd ble l
t h R ra
a r a nsfe
Bh n-tra
no

Implementation Task Flow
s a
)h a
m
co uide
e
@ hp nt G
m ar tude
y - ku is S
e d d th
r e
r a th to us
( b ha nse
R e able
r s f er
ath Applications
h a
The Implement
t r a n process includes some activities that are manual and performed
B n- Oracle Fusion Functional Setup Manager application.
outside of the
n o
Plan is the process of gathering business requirements and comparing them to the
offerings available to determine what to implement.
Install is not addressed directly with Oracle Fusion Functional Setup Manager. The
installation of the applications and instances is done for on-premises installs before the
functional setup. Install is already completed for cloud implementations.
Configure is the process of selecting the offerings, options, and features to implement.
The selections made during the configure process dynamically determine the task lists
for implementation.
Implement covers both the management and functional user aspects of assigning tasks
and due dates, as well as completing setup tasks and reporting status.
Export enables you to export the configuration setup data from one environment in order
to import the configuration into another environment in the same or a higher release.
Transact is the transaction processing done within the actual product, such as Payables.
Maintain is the process that enables you to search for tasks or task lists to perform
maintenance of setup tasks from a single user interface.

Implementation Project: Overview
An implementation project:
Uses the Setup and Maintenance work area in Oracle Fusion
Functional Setup Manager.

Starts the creation of your enterprise and its structures.
Defines the scope of the implementation.
Is populated by adding one or more related offerings or task
lists.
Provides progress reports on tasks that can be seen on a the
s a
h
Implementation Projects tab. m) c o ide

pe t Gu
h
a r@ den
- k um Stu
e d dy this
t h r u se
a r a e to
e dd ble l
t h R ra
a
Detailed r a onnyour
status s feimplementation project can be seen by:
Bh n-tthe
Clicking
ra numbers in the Assigned Tasks column.

no
Drilling down to the Implementation Project detail graphical reports in the project details
region.

Assign Tasks
After you create your implementation project:

Assign tasks to users by using the Assign Tasks button in the
implementation project.
Assign and store notes associated with the task list or task as
attachments.
Review, add, or delete users in the Assigned Users region.
s a
) h a
o m
p e c uide
@ h nt G
r
a tude
u m
d y -k his S
r e d se t
a r ath e to u
e dd ble l
t h R ra
a
Navigate rto:
fe Maintenance > Manage Implementation Projects > Fin
a Setupnsand
Bh n-tra> Expand to specific task and select row header > Assign Tasks.
Implementation
noassign tasks either by:
You can
Assigning the same users and due dates to all tasks in a task list.
Assigning individual tasks to a specific user.

Implementation Task Lists
Tasks and task lists contain features, functional areas, options,

and offerings.
Define setup objects:

Top-down to identify all the elements required.
Bottom-up to define and register the objects in Functional
Setup Manager.
Create subsets of tasks for special situations or specific
industries. a
s
Create all these options when creating a new custom) ha
c om ide
application to integrate fully with Oracle Fusion Functional
Setup Manager. h pe t Gu
@ a r e n
um Stu d
- k
e d dy this
t h r u se
a r a e to
e dd ble l
t h R ra
r abottom-up
s e
fapproach
Tip: Useaa
h -tra n when creating new objects and defining relationships.
B
AlthoughoFSMn allows you to create objects in any order, creating the dependent associated
objectsnbefore creating the parent objects (the objects that will consume the other objects) will
save you time because you will not need to edit the parent objects multiple times.

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 s a
h
) a
Create Banks, Branches, and Accounts o m
p e c uide
Manage Tax Regimes h nt G
r @
a tude
Run Jurisdiction and Rates Upload Program
m
u
-k his S
Manage Taxes d d y t
t h re use
a r a e to
e dd ble l
t h R ra
Navigatea rto:
fe Maintenance
a Setupnsand
Bh efficient
For fast, o n -traimplementations, add the Define Financials Configuration for Rapid
n
implementation task list. These task lists consist of the required tasks for your implementation,
including spreadsheet loaders to make data input easier.

Financials Task Lists
Define Common Applications Configuration for Financials.

Define Common Financials Configuration.
Define Invoicing and Payments Configuration.

Define Receivables Configuration.
Define Expense Configuration.
Define Fixed Assets Configuration.
Define Collections.
a
Define and Maintain Intercompany Processing Rules. has
m )
Define Hyperion Financial Management Integration. o
c uide
p e
h nt G
Define Budget Configuration. r @
m a tude
Define Financial Reporting. u
d y -k his S
Define Transactional Business et
red Intelligence Configuration.
r a th to us
( b ha nse
R e able
r athoptional
s f er
h a
To implement
t r a n and more advanced features, use the Financials task lists. The task
B n- in the order in which the tasks need to be completed.
lists are arranged
n o
Note: Some of these tasks are covered in the other Oracle Financials Cloud courses.

Practice 3-3 Overview: Creating an Implementation
Project
Creating an implementation project.
Including Financials and its nested offerings.

Adding Financial Configuration for the Rapid Implementation
task list.
s a
h
) a
o m
p e c uide
@ h nt G
r
a tude
u m
d y -k his S
r e d se t
a r ath e to u
e dd ble l
t h R ra
a r a nsfe
Bh n-tra
no

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

applications are implemented.
You can create a new ongoing maintenance implementation

project in one of two ways:
Do not select an offering. Add the required task lists or tasks to
the implementation project.
Select an offering and delete the task lists or tasks that are not
required.
a
has
Use Scope to simplify ongoing maintenance on a task list.
)
o m
p e c uide
@ h nt G
r
a tude
u m
d y -k his S
r e d se t
a r ath e to u
e dd ble l
t h R ra
a
Navigate rto:
fe Maintenance > Manage Implementation Projects.
a Setupnsand
Bh n-tra an ongoing maintenance implementation project that includes tasks such
Considerodefining
as: n
Manage Daily Rates
Manage Calendars
Note: Scope, as used in Oracle Fusion Functional Setup Manager, refers to an object that
allows a task list to be performed repeatedly. An example of a scope value is Business Unit,
for which you select a particular business unit and proceed to perform all setup tasks for that
business unit.

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

An entire offering.
Any of an offerings functional areas.
s a
)h a
m
co uide
e
@ hp nt G
m ar tude
y - ku is S
e d d th
r e
r a th to us
( b ha nse
R e able
r ath Fusions f er
Almost
h a
all Oracle
t r a n application implementations require moving functional setup data
B n- into another at various points in the life cycle of the applications.
from one instance
n o
For example, an enterprise application implementation is first implemented in a development
or test application instance and then deployed to a production application instance after
thorough testing.
You can move functional setup configurations of applications from one application instance
into another by exporting and importing setup data.

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

For an offering: All enabled functional areas and relevant
features.
For a single functional area: That functional area and relevant
features.
Note: Once you initiate the export process, you can:
Monitor the exports progress.
Check the exports status from the Export Offering Data as a
h
History page. m) c o ide

pe t Gu
h
a r@ den
- k um Stu
e d dy this
t h r u se
a r a e to
e dd ble l
t h R ra
a r a nsfe
Advantages:
Bh neasily
Helps - tra move your implementation or configuration across instances.
no
Does not require selecting tasks or understanding data relationships to ensure only
setup data relevant to the selected offering or functional area is exported.
Gives you flexibility to filter the setup data as needed for specific offerings or functional
areas.
Note: Some objects are not imported through configuration packages including:
Application Menu Customization
Trading Community Geography
File Common Import Object or Attribute
File Import Object, Mapping Column, or Activity
Users
Application General Preferences
Procurement Browse Category or Tree
Suppliers, Supplier Match Party Relationship, Role, News, or Notification Configuration

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

uploaded. You can:
Initiate the setup data import from the importing environment.

Monitor the imports progress.
Check the imports status from the Import Offering Data
History page.
s a
h
) a
o m
p e c uide
@ h nt G
r
a tude
u m
d y -k his S
r e d se t
a r ath e to u
e dd ble l
t h R ra
ra ansfe
aconsider:
Pointshto
B n-trmust be enabled before import.
Offerings

no
Import options must match the export file options.
Limited validation is performed before the import proceeds.
Notification of data that must be loaded manually is sent. You can enter the data and
resume the process.
Notification of errors is sent. You can correct the error or skip the option.

Offering Based Export and Import Process
s a
a
)h 3
m
co uide
e
@ hp nt G
m ar tude
y - ku is S
e d d th
r e
r a th to us
( b ha nse
R e able
Navigatea rto:
ferMaintenance > Financials Offering > Setup button > Export button >
athSetupnsand
BhNewn-Export.
Create tra
Select n
o
the offering (1) or functional area (2) you want to export or import setup data for, and
then select the Export or Import action.
Selecting Export for either a functional area or offering invokes the Export Offering
Setup Data page where you create an export process for the offering or functional area
you want to export.
Selecting Import (3) from the Actions drop-down list invokes the Import Offering Setup
Data page where you can upload and import previously exported setup data.

Additional Information on Oracle Help Center
Use these videos found under the Videos link on the Oracle Help
Center Financials page to learn more about FSM.
s a
h
) a
o m
p e c uide
@ h nt G
r
a tude
u m
d y -k his S
r e d se t
a r ath e to u
e dd ble l
t h R ra
araOracle
Link tohthe n s
Help
feCenter Financials page:
B n-tra
http://docs.oracle.com/cloud/latest/financialscs_gs/index.html
no

Summary

Describe Oracle Fusion Functional Setup Manager.
Browse and configure offerings and functional areas.

Review the Oracle Fusion Financials offering.
Review the reports associated with the Oracle Fusion
Financials offering.
Create an implementation project.
Explain setup data export and import. s a
h
) a
o m
p e c uide
@ h nt G
r
a tude
u m
d y -k his S
r e d se t
a r ath e to u
e dd ble l
t h R ra
a r a nsfe
Bh n-tra
no

4
Overview of Security
s a
h
) a
o m
p e c uide
@ h nt G
r
a tude
u m
d y -k his S
r e d se t
a r ath e to u
e dd ble l
t h R ra
a r a nsfe
Bh n-tra
no
Objectives

Understand the Cloud security methodology.
Plan your use of the security implementation.

Identify the components of data security.
Discuss how roles can be assigned automatically or
manually.
Explore the new Security Console to customize roles and
users. a
h a s
Review the audit reports and resources. )
c om ide
h pe t Gu
a r@ den
- k um Stu
e d dy this
t h r u se
a r a e to
e dd ble l
t h R ra
a r a nsfe
Bh n-tra
no

Oracle Financial Cloud Security Methodology
The 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
s a
a
)h
m
coownuide
Employees View payslip
Employees
e
@ hp only
payslip
n t G
r
a tude
u m
k is UK S Ledger
General Accounting Create and runy-reports
Manager e d
d se t h
r
a r ath e to u
e dd ble l
t h R ra
r aThe users e
fwho
a
Who:
h -tra n performs functions in your company, such as an Accounts Payable
Bsupervisor.
nonIndividual actions a user can perform, such as the ability to approve a payables
What:
invoice.
Which: The set of data that the user can perform the action on, such as payables
invoices within your assigned business units.

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 which are:
Delivered with the offering or service.
Used to meet the business needs of most enterprises. s a
)h a
m
co uide
e
@ hp nt G
m ar tude
y - ku is S
e d d th
r e
r a th to us
( b ha nse
R e able
r h sfer
atreference
h a
The security
t r a n implementation covers all functions and actions that need to be
B
secured. The -security definitions were based on industry standards. Unless you have
nonexisting functions or added new functions, you shouldnt have to create any new
customized
job or duty roles. The implementation includes:
Complete set of job roles.
Duty roles and role hierarchy for each job role.
Privileges granted to each duty role.
Data security policies for each job role.
Policies that protect personally identifiable information.
Policies enforced across tools and access methods.
Policies related to segregation of duties that are reflected in the design of duties for the
job role.
Segregation of duties conflicts.

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

Implementation Users task at the beginning of the project.
After implementing the first project, consider:

Data Access Sets: Define read and write access to entire GL
ledgers and balancing segment (company) values of ledgers.
Segment Value Security: Controls access to individual segment
values in your chart of accounts such as no access to
Company 01, Dept. 100, or Salaries account.
s a
)h a
m
co uide
e
Co CC Acct @ hp nt G I/C
a r d e
- k um Stu
e d dy this
t h r u se
a r a e to
e dd ble l
t h R ra
a
The first r a nsfe user is for creating only the initial enterprise structure and is not a
implementation
realB
h -tHCM.
personnin ra After the initial enterprise structure is complete, you can create additional
o using the Manage Users or Import Worker Users tasks. Your users require that
users innHCM
a business unit, legal entity, and other setup be added after the initial implementation.
Planning is essential:
Analyze the access requirements specific to your organization, understanding who
needs access to what.
Compare the requirements with the predefined roles in the security reference
implementation, and decide which predefined roles meet your requirements and can be
used as-shipped, and which will require customizations to meet your requirements.
Certain product areas, such as Accounts Payable and General Ledger, include multiple
roles in the reference implementation. To compare accesses granted to each role, you
can use the Compare Role feature in the Security Console.
Other segment value security considerations:
For upgraded R11 customers, if you add or remove a BU or ledger, you must regenerate
roles from that data role template.
Consider having different users define roles and provision roles.

For On-Premises Implementations Only
The Oracle Fusion Applications super user FAADMIN, by default, has all necessary access
rights for implementing Oracle Fusion HCM and administering security. This access is
provided by the following job roles:
Application Implementation Consultant
IT Security Manager
However, neither of these roles provides the required access for creating and managing
Oracle Fusion Applications users; therefore, the OIM system administrator must add the
following two OIM roles to the IT Security Manager job role:
Identity User Administrator, which carries user management entitlement.
Role Administrator, which carries role management entitlement.
Note: Assign the Xellerate Users organization to the IT Security Manager.
s a
h
) a
o m
p e c uide
@ h nt G
r
a tude
u m
d y -k his S
r e d se t
a r ath e to u
y (bh icens
e dd ble l
t h R ra
a r a nsfe
Bh n-tra
no

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

Your application is secure as delivered.
You give function and data access through roles that you
assign to users.
Function security allows you to access:
A page or a specific object.
Functionality within a page, including services, screens, and
task flows. a s
Data security consists of privileges conditionally granted h
) as:a
c o m e
Data security policies carried by roles.
pe t Gu i d
h
Human Capital Management (HCM) security a r@ dprofiles.
e n
- k um Stu
e d dy this
t h r u se
a r a e to
e dd ble l
t h R ra
a r
For example, s fecan enable users to work with journals. A data role that inherits the job
a a jobnrole
roleB
h -traaccess to the journal data within a ledger.
can provide
n
norole
The data General Accounting Manager US inherits functionality from the General
Accounting Manager job role, and it enables users to perform general ledger duties in the US
ledger.

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

roles, also called external roles, are:
Enterprise Job roles: Represent jobs that users perform in an

organization, such as Accounts Payable Manager.
Abstract roles: Represent people in the organization
independent of the jobs they perform, such as employee or
line manager.
Duty role: Logical collection of privileges that grant access toa
tasks that someone performs as part of a job, such as) ha
s
m
processing payables invoices or posting journals. co de pe t Gui
h
a r@ den
- k um Stu
e d dy this
t h r u se
a r a e to
e dd ble l
t h R ra
Assign a r
these s fe to users:
a rolesndirectly
Bh n-traYou can also create custom job roles.
Joboroles:
n
Abstract roles: All users are likely to have at least one abstract role that provides
access to a set of standard functions, such as expense reporting or procurement. You
can also create custom abstract roles.
Assign these roles to Job and Abstract roles, not directly to users:
Duty roles: You can also create custom duty roles.

Role Inheritance
s a
)h a
m
co uide
e
@ hp nt G
m ar tude
y - ku is S
e d d th
r e
r a th to us
( b ha nse
R e able
a r
Role inheritance
ferconcept in the security model. The figure illustrates the hierarchy of
ath isnaskey
job B
h -role
and duty trainheritance, which are used as the building blocks in Oracle Cloud Security.
n
no every role is a hierarchy or collection of other roles.
Almost
- Job and abstract roles inherit duty roles.
- Duty roles can inherit other duty roles.
You can also assign privileges directly to job, abstract, and duty roles.
When you assign job and abstract roles to users, they inherit all of the data and function
security associated with those roles.

Oracle Fusion Inheritance Model
s a
)h a
m
co uide
e
@ hp nt G
m ar tude
y - ku is S
e d d th
r e
r a th to us
( b ha nse
R e able
athbuilding f er
Rolesh arthe
are
t r a s
n blocks of security.
B
Youocann- start at the bottom with duty roles, which you can combine with other duty roles.
n
For example, you can combine a journal entry duty role with a journal reporting duty
role.
The job and abstract roles inherit duty roles. For example, the General Accountant job
role can have one or more duty roles.
The data roles inherit the job role and give the user access to specific data such as
ledgers, asset books, or business units.

Security Example with Data Role Added
s a
a
)h
m
co uide
e
@ hp nt G
m ar tude
y - ku is S
e d d th
r e
r a th to us
( b ha nse
R e able
r h sfer
atnow
h a
The diagram
t r a nshows Data Role added to secure Anita Kennedy to the UK Set of Data in
B - for her General Accountant Job role.
the UK Ledger
non

New Data Security for R11
NEW
Applicable to new customers only.
Does not use data role templates.
Assigns users directly to the job roles and to the appropriate

data sets.
Uses the new Manage Data Access for Users page.
Existing customers upgrading from previous releases:
Continue to utilize the old data role based model for their data
security implementation. s a
a
)h
Assign specific data sets, such as business units,oledgers,
m
warehouses, and so on. p e c uide
@ h nt G
r
Use data roles that were automaticallyagenerated de by data role
u m t u
templates. y-k is S d d th
r e e
r a th to us
( b ha nse
R e able
r athethManages f er
h a
To access
t r a n Data Access for Users page, navigate to Setup and Maintenance >
B
Manage Data - Access for Users task.
non

Assigning Data Scopes to Users for New Customers
Only
Use the Manage Data Access for Users task to assign users to
data scopes.
Assign data scopes to users by provisioned role.

Use the import capability to create a large number of
assignments.
NEW a
h a s
m )
o
c uide
p e
h nt G
r @
a tude
u m
d y -k his S
r e d se t
a r ath e to u
e dd ble l
t h R ra
r a Manage s e
fData
You use
h athe
t r a n Access for Users task to assign users to data scopes, like
B - Ledgers, and Asset Books. You can access this task from the Setup and
Business Units,
non work area.
Maintenance
You assign data scopes to users by role, and you can only assign data scopes to roles a user
has been provisioned.
You can also import assignments from a spreadsheet. By clicking on the Authorize Data
Access button in the Manage Data Access page, you can download a spreadsheet which you
can use to import the data assignments. You can prepare the data from another source, such
as your legacy system, and populate the spreadsheet, and then import.

Oracle Identity Manager
Operates in three modes:

Self-Service: You can manage your own roles and privileges.
Delegated Administration: You manage the roles and

privileges of other users.
Advanced Administration: You can manage password policies
and perform other system administrative functions.
s a
a
)h
m
co uide
e
@ hp nt G
m ar tude
y - ku is S
e d d th
r e
r a th to us
( b ha nse
R e able
r h sfer
atIdentity
a
h -tran Manager (OIM) access is granted to the predefined IT Security Manager
Oracle
Brole. n
noAdministration
Use Mode in OIM to create users and provision roles. OIM opens by
default to the self-service view.
- The title displays whether you are in Administration mode or Self-Service mode.
- To switch from Self-Service Mode to Administration Mode, click on the button in
the upper right hand corner.

Creating Users
If you are not implementing Human Capital Management

(HCM), use the Manage Users task to create users. The
Manage Users task creates a minimal person record and a

user account.
If you are implementing HCM, use the Hire an Employee task
to create users instead. The Hire an Employee task creates
the full person record as well as the user account.
Use the Create Implementation Users task to create a
a
implementation users without associating a person record. s
m )h
co uide to
Use a spreadsheet to import users from legacy applications
e
hp tUsers
Oracle Financials Cloud using the Import Worker G task.
a r@ den
- k um Stu
e d dy this
t h r u se
a r a e to
e dd ble l
t h R ra
Access a r
the n s fe
atasks above:
Bh n-Users:
Create
tra Navigate to: Setup and Maintenance > Manage Users > Create icon or
on
o Navigator > My Team > Manage Users > Create icon.
nthe
Hire an Employee: On the Navigator > My Workforce > New Person > Tasks panel >
Hire an Employee. This task creates the full person record needed by HCM, such as job
assignment, job code, department, manager, etc., as well as the user account itself.
Create Implementation Users: Navigate to: Setup and Maintenance > Create
Implementation Users > Administration tab > Create User icon.
Import Worker Users: Navigate to: Setup and Maintenance > Import Worker Users >
Create Worker > Create Spreadsheet icon or on the Navigator > My Workforce > Data
Exchange > Tasks panel > Initiate Spreadsheet Load > Create Worker > Create
Spreadsheet icon.
Note: The import process handles both user account creation and auto provisioning of roles.

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

Manually provision roles to users using Oracle Identity
Manager.
Automatically provision a role to users by defining a
relationship, called a role mapping, between the role and
some conditions.
s a
a
)h
m
co uide
e
@ hp nt G
m ar tude
y - ku is S
e d d th
r e
r a th to us
( b ha nse
R e able
r h sfer
atprovision
h a
To manually
t r a n roles, use the Create Implementation Users task from Setup and
B
Maintenancen-to access Oracle Identity Manager. Make sure you switch to Administration
noassign
mode to roles to users.
To assign a role to a specific user:
- Use the search box to search for the desired user.
- Open the user and go to the Roles tab.
- Click the Assign button to assign new roles to the user.
To assign the same role to multiple users:
- Search for the role.
- Go to the Members tab.
- Click the Assign button to assign multiple users to the same role.
Roles are automatically provisioned when one of the user's assignments matches all role-
mapping conditions and the auto provision option is selected.

Using Role Mappings
Create and manage role mapping rules.

Use the Manage Role Provisioning Rules task to create and
manage role mapping rules.

If HCM is implemented, use the Manage HCM Role
Provisioning Rules task instead.
Set a role attached to a role mapping role to:
Requestable: Qualifying users can provision roles manually to
other users. s a
)h a
Self-requestable: Users can request the role for themselves. m
Auto-provision: The system will automatically e co uroles
assign ide to
p
h nt G
users when they meet all the conditions r @
in the
a tude role mapping.
This provision the role to all users m
u doSnot already have
kwho
d y - his
the role assigned. r e d e t
r a th to us
( b ha nse
R e able
r ath allow s f er
h a
Role Mappings
t r a n you to automatically assign roles to users if they match the conditions
B - Role Mappings. As users transfer departments or change jobs, the Role
specified innthe
nocan automatically assign the correct roles to the users.
Mappings
Each role mapping rule is based on a set of attributes that can be matched to a users
assignment, such as Department, Job, and Location. For example, you may define a rule that
limits role mapping to current employees of the Finance Department whose Job is Accounting
Manager.
Roles capture the nature of work intended to be performed by the user.
A range of security roles are granted to the new user.
This enables users to access application flows that are crucial for performing the tasks.
When the list of assigned security roles is populated, you can remove or add new roles as
needed.
Note: Auto-provision: Deprovisions roles immediately from users who are no longer eligible
for roles that they currently have.

Practice 4-1 to 4-3 Overview: Using User Security

Practice 4-1: Defining role mapping.
Practice 4-2: Creating a user.

Practice 4-3: Creating an employee.
s a
h
) a
o m
p e c uide
@ h nt G
r
a tude
u m
d y -k his S
r e d se t
a r ath e to u
e dd ble l
t h R ra
a r a nsfe
Bh n-tra
no

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

security reference implementation:
Create custom job roles by copying existing roles.

Add duty roles and privileges to custom job roles.
If the privileges for a predefined job role don't match the
corresponding job in your enterprise:
Create custom job roles by copying existing roles.
Add or remove duty roles, function security privileges, and s a
h a
data security policies. m) c o ide

pe t Gu
h
a r@ den
- k um Stu
e d dy this
t h r u se
a r a e to
e dd ble l
t h R ra
a r
Best Practices s fe
a fornCustomizing Roles
B h -tra
Do o notn customize predefined roles. These predefined roles begin with the ORA_ prefix
innthe Role Code field. During each upgrade, the upgrade process updates the
predefined roles to the specifications for that release, so any customizations are
overwritten.
Always make a copy of the predefined role. Then, edit the copy and save it as a custom
role.
Compare the copy of the predefined role with the new customized role and roll back to
the delivered role, if necessary.
After a maintenance update or upgrade, compare your customized copy to the updated
predefined source role. You can see the updates to the predefined role and decide
whether to incorporate those changes into your custom role.

The Security Console
Use to customize security.

Create and edit custom roles, but not predefined roles.
Can be accessed via the Navigator menu, under Tools.

Access granted through the IT Security Manager role.
s a
)h a
m
co uide
e
@ hp nt G
m ar tude
y - ku is S
e d d th
r e
r a th to us
( b ha nse
R e able
th sfer
arastart
Beforehyou
t r n the Security Console, set two profile options that govern the behavior
using
a
B n- Console in the Manage Administrator Profile Values task.
of the Security
n o
Security Console Working App Stripe: Controls the App Stripe the user works on.
Please set this profile option to fscm, either at the site level, or for specific users with
Security Console access.
Enable Data Security Policies and User Membership Edits: Sets the preference to
enable data security policies and user membership editing in Security Console. Set this
profile option to Yes to enable both, at the site level, or for specific users.

The Security Console: Copy Feature
Steps to use the Copy feature are:

Copy a role.
Modify the default role name, code, description.

Review, add, or remove function security privileges.
Review, edit, or remove data security policies.
Review, add, or remove inherited roles.
Assign users to the target role.
a
Review the summary and impact.
) has
Submit and Close. o m e
c pe t G u i d
h
a r@ den
- k um Stu
e d dy this
t h r u se
a r a e to
e dd ble l
t h R ra
a
The Copyr a ninsthe
feature
feSecurity Console enables you to:
Bh n-default
Setoup
tra names in the Preferences section of the Security Console.
n
Review the code resources tied to each function security privilege.
Important:
To add, edit, or remove data security policies, set the profile option Enable Data Security
Policies and User Membership Edits to Yes, either at the site level or for the current
user.
To assign users to this new role, set the profile option Enable Data Security Policies and
User Membership Edits to Yes, either at the site level or for the current user.
Note: This option is only available to external roles, as you can only assign external roles to
users.

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

granted between two roles.
Launch Compare Roles directly by clicking on the button or by

choosing the Compare Roles option in the Search Results.
s a
h
) a
o m
p e c uide
@ h nt G
r
a tude
u m
d y -k his S
r e d se t
a r ath e to u
e dd ble l
t h R ra
View: har
a nsfe
All o n -tra results.
B comparison

n
Artifacts that only exist in either the first or the second role.
Artifacts that exist in both roles.
Choose to view only comparison results for:
Function security policies.
Data security policies
Inherited roles, or combinations.

Additional Features
Use the following icons on the left hand side of the page:
Roles: Copy, create, and compare roles.
Analytics: Examine data on roles.

Certificates: Review Certificates.
Administration: Save Preferences.
s a
h
) a
o m
p e c uide
@ h nt G
r
a tude
u m
d y -k his S
r e d se t
a r ath e to u
e dd ble l
t h R ra
a r a nsfe
Bh n-tra
no

Practice 4-4 Overview: Using the Security Console

Copying a role.
Comparing a role.
s a
h
) a
o m
p e c uide
@ h nt G
r
a tude
u m
d y -k his S
r e d se t
a r ath e to u
e dd ble l
t h R ra
a r a nsfe
Bh n-tra
no

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.
s a
)h a
m
co uide
e
@ hp nt G
m ar tude
y - ku is S
e d d th
r e
r a th to us
( b ha nse
R e able
r th sfer
aMembership
User Role
h a t r a n Report: You can run the report for all users, or you can optionally filter
B n- by name, department, and location.
the list of users
n o
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.
- The 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 a given role.
- The All Roles option results in one set of reports for each role.

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

- Users username
- Given name
- Surname
- Location and department
- Users status
s a
h
) a
o m
p e c uide
@ h nt G
r
a tude
u m
d y -k his S
r e d se t
a r ath e to u
y (bh icens
e dd ble l
t h R ra
a r a nsfe
Bh n-tra
no

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

security reference implementation for your application, you can:
Access the security reference manuals (SRM).

Common
Service-specific
Access the tasks available for managing roles, templates, and
security policies.
Security a
Securing Oracle a
Reference
h sfor
ERP Cloud m )
Oracle
o
c uideCloud
h peFinancials tG
Security Reference
a r@ den
for Common
- k um Stu
s
ddy thi
Features
re use
r t h
a e to
a
e dd ble l
t h R ra
e
nsf is applicable to the needs of midsized, horizontal enterprises
ara traSecurity
OraclehFinancial
B between
generally - 250 and 10,000 employees. It can be changed or scaled to accommodate
noninto vertical industries such as health care, insurance, automobiles, or food
expansion
manufacturing.
For more resources on the Oracle Help Center, see:
Oracle Financial Security Guides:
http://docs.oracle.com/cloud/latest/financialscs_gs/docs.htm.
Oracle Fusion Middleware Security Guides:
http://docs.oracle.com/middleware/1221/cross/securedocs.htm.

Summary

Understand the Cloud security methodology.
Plan your use of the security implementation.

Identify the components of data security.
Discuss how roles can be assigned automatically or
manually.
Explore the new Security Console to customize roles and
users. a
h a s
Review the audit reports and resources )
c om ide
h pe t Gu
a r@ den
- k um Stu
e d dy this
t h r u se
a r a e to
e dd ble l
t h R ra
a r a nsfe
Bh n-tra
no

5
Discussing the Vision Story and

Common Applications
s a
h
) a
o m
p e c uide
@ h nt G
r
a tude
u m
d y -k his S
r e d se t
a r ath e to u
e dd ble l
t h R ra
a r a nsfe
Bh n-tra
no
Objectives

Discuss the Vision Corporation Story elements.
Explore geography:
Structure
Hierarchy
Validation
s a
h
) a
o m
p e c uide
@ h nt G
r
a tude
u m
d y -k his S
r e d se t
a r ath e to u
e dd ble l
t h R ra
a r a nsfe
Bh n-tra
no

Overview
The Oracle Fusion Financials Implementation course is based on

a fictional yet realistic enterprise that:
Combines the common aspects of your enterprise structure.

Is used to explore and implement objects during class.
s a
h
) a
o m
p e c uide
@ h nt G
r
a tude
u m
d y -k his S
r e d se t
a r ath e to u
e dd ble l
t h R ra
a
Navigate rto:
fe Maintenance > Manage Enterprise HCM Information.
a Setupnsand
Bh n-tra
no

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 Fusion a
a s
Applications solution including Oracle Fusion General Ledger
and all of the Oracle Fusion subledgers. m )h
e co uide
Vision Corporation has 400 plus employeeshandp revenue
t G of
r @ n
$120 million. ma tude ku is S
d y -
r e d e th
r a th to us
( b ha nse
R e able
th sfer
Note:h araVision
The
t r a nCorporation story is used to demonstrate and teach the functionality in
B
Oracle Fusion- Applications to customers around the globe and does not necessarily represent
nonimplementation.
a real-world

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.
s a
)h a
m
co uide
e
@ hp nt G
Ready Set
m ar tuGo!! de
u
-k his S
d y
d se t
r e
a r ath e to u
e dd ble l
t h R ra
a
Consider r a following
the n s feelements in creating your model for your global enterprise structure.
Bh ncompany
Your - tra is required to report using US GAAP Practices, UK Statements of
no Accounting Practice, and International Financial Reporting Standards (IFRS).
Standard
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 a
during transaction entry or reporting? a s
m )h
Do you need multiple balancing segments to achieve
e co ufully
ide
balanced balance sheets across more than h p tG
r@ one nsegment?
a tude
u m
d y -k his S
r e d se t
a r ath e to u
e dd ble l
t h R ra
a r a nsfe
Bh n-tra
no

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?
s a
h
) a
o m
p e c uide
@ h nt G
r
a tude
u m
d y -k his S
r e d se t
a r ath e to u
e dd ble l
t h R ra
a r a nsfe
Bh n-tra
no

Vision Corporation Structure Diagram
s a
a
)h
m
co uide
e
@ hp nt G
m ar tude
y - ku is S
e d d th
r e
r a th to us
( b ha nse
R e able
th sfer
aramodel
This ishthe
t r a n your team has designed. The model uses numerical values to provide a
that
B n-
sample representation of your structure. The model includes the following recommendations:
n o
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.
s a
h
) a
o m
p e c uide
@ h nt G
r
a tude
u m
d y -k his S
r e d se t
a r ath e to u
y (bh icens
e dd ble l
t h R ra
a r a nsfe
Bh n-tra
no

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

Enterprise Vision Yes 999 Consolidation Ledger
Corporation Currency USD

Division Vision North No 100 No
America
Company Vision US Inc. Yes 101 US Primary Ledger
LE1 Currency USD
Company Vision US Inc. Yes 102 US Primary Ledger
LE2 Currency USD s a
) h a
Division Vision EMEA No 300
c oNo
m e
Company Vision France Yes 311 h pe Primary
France G uidLedger
Inc. a e nt EUR
r@ dCurrency
Company Vision United
um tu
Yes y-k 303is S UK Primary Ledger
e d d th
Kingdom Ltd.
h r u s e Currency GBP
r t
a e to
a
e dd ble l
t h R ra
r athe slide s e
fillustrates
h a
The chart in
t r a n the enterprise structure of your Vision Corporation entities.
B
The following - statements expand on the data in the chart.
non
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
Shared Service Center
Vision Corporation s a
BSV 103*
)h a
Payables Department All Entities Cost Centerm
co u723
p e ide
@ h nt G
r
a tude
u m
d y -k his S
r e d se t
a r ath e to u
e dd ble l
t h R ra
r athe slide s e
fillustrates
h a
The chart in
t r a n the business unit structure of your Vision Corporation entities.
B n- statements expand on the data in the chart.
The following
n o
Business units are required because financial and other transactions are processed and
secured by business units. Business units link to a default LE, but can perform business
functions for multiple LEs if those LEs share the same ledger.
A shared service center to perform the Procurement business function, including
processing requisitions and negotiating supplier terms, is optional. If used, the shared
service center must be a business unit. *The assigned BSV of 103 is only for this
example and does not exist in the Vision demo database.
Divisions are optional and can be represented with a hierarchy of cost centers or by a
second balancing segment value.
Note: Departments or cost centers are required because they track your employees and are
used in Oracle Fusion Assets and Oracle Fusion Expenses.

Vision Corporation Distribution Structure
Entity Type Entity Name Distribution

Structure
Distribution Center US Distribution Inventory

Center Organization
Warehouse Seattle Inventory
Organization
Warehouse Atlanta Inventory
Organization
Distribution Center EMEA Distribution Inventory
Center a
Organization
s
)h a
Warehouse Bristol Inventory
m
co uide
Organization
e
Warehouse Marseille @ hpInventory
n t G
r de
a tuOrganization
u m
List of Items Common d y -k his S Item Master
Item
r e d se t
Master Organization
r a t h t o u
h a s e
y (b icen Copyright 2016, Oracle and/or its affiliates. All rights reserved.
e d
d ble l
t h R ra
a
The chartr a nsthe
illustrates
fedistribution structure of your Vision Corporation entities. The following
Bh nexpand
statements - tra on the data in the chart.
no
Distribution centers and warehouses are used to receive and ship the high tech
products your firm sells.
Item master organization and inventory organizations can be added if you are tracking
your inventory transactions in Oracle Fusion Applications.

Vision Corporation Chart of Accounts Summary
s a
)h a
m
co uide
e
@ hp nt G
m ar tude
y - ku is S
e d d th
r e
r a th to us
( b ha nse
R e able
r h sfer
ataccounts
h a
The chart of
t r a n structure above shows the names of the segments and the default
B - team is proposing for Vision Corporation's three primary ledgers.
values thatnyour
n o
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.
s a
h
) a
o m
p e c uide
@ h nt G
r
a tude
u m
d y -k his S
r e d se t
a r ath e to u
e dd ble l
t h R ra
a
Navigate rto:
fe Maintenance > Define Geographies.
a Setupnsand
Bh geographies
Managing n - tra comprises:

no
Geography structures.
Geography hierarchies.
Geography validations.
Address cleansing.
Geocoding process.

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

monitors where and how you do business. You need to:
Structure and create geographical information associated with

your business when you first set up Oracle Fusion
Applications.
Use this information to facilitate business processes that rely
on geographical data. For instance, you need geographical
information to: a
Validate addresses h a s
m )
Calculate taxes o
c uide
p e
h nt G
Create sales territories @
r
a located de and shared
All your geographical information is centrally u m S t u
with other application offerings within d y -kyourhicompany.
s
r e d se t
a r ath e to u
e dd ble l
t h R ra
e
fwith
ara trcomes
OraclehFusion a n s predefined country names. You need to define the geography
B
on-requires
structure and
processnthat
hierarchy of each country associated with your business before working on any
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 s a
geography. ) h a
Country Top level c m
o ide

pe t Gu
h
State a r@level
Middle d e n
- k um Stu
e d dy this
t h r City use Bottom level
a r a e to
e dd ble l
t h R ra
a
A countrysr ageography
n s festructure determines the component geography types that can be
Bh andnthe
defined - trahierarchical relationship between them. A set of predefined geography types
no for inclusion in a country's geography structure. Additionally, you can create a
is available
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 Fusion
Applications can infer information. s a
a
)h
If you enter 94065 in a zip code of the application, the
m

application determines that the postal code belongs
e co to:
uid
e
p h nt G
California r @
a tude
u m
Redwood City
d y -k his S
r e d se t
a r ath e to u
e dd ble l
t h R ra
a r a nsfe
Bh n-tra
no

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.
s a
a
)h
m
co uide
e
@ hp nt G
m ar tude
y - ku is S
e d d th
r e
r a th to us
( b ha nse
R e able
r h sfer
athierarchy
h a
A geography
t r a n can be a Master Reference Geography Hierarchy or a User Defined
B -
GeographynHierarchy:
n o
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 countrys 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. s a
a
)h
The No Styles Format address style format is: m
co uide
e
The default address style format for a country.
@ hp nt G
r
afor deaddress in the
Used to define mapping and validationu m any
t u
country. d y -k his S
d t
t h re use
a r a e to
e dd ble l
t h R ra
You cana r
map n s fe attributes for each of the address style formats to a geography type.
a the address
ForB
h -tyou
example, ra can map the State geography type to the County address attribute for the
o n
United n
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.
s a
)h a
m
co uide
e
@ hp nt G
r
adata debe saved if
u m
If Error, t u
cannot
S fails.
d y -k hvalidation
i s
r e d se t
a r ath e to u
e dd ble l
t h R ra
You can a r a Geography
define n s fe Duplicate Validation Control at the country level. The geography
Bh control
validation n - tradetermines whether an address that did not pass geography validation
during n o entry can be saved. If the validation control is set to Error, then an address
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 s a 3. Verified
address and a
)h
address
click. m
co uide
appears in
e standardized
@ hp nt G form.
m ar tud2.eVerify
y - ku is S address and
e d d th click.
r e
r a th to us
( b ha nse
R e able
a
Address r ath nsfer
Cleansing:
Bh n-tracorrects, and standardizes addresses that you enter in a user interface.
Validates,

no
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.
s a
Longitude a
)h
m
co uide
e
@ hp nt G
Latitude
m ar tude
y - ku is S
e d d th
r e
r a th to us
( b ha nse
R e able
r ath enables f er
Spatial
h a
services
t r a n users to find points of interest such as customers, contacts, and so on
B n- and longitude coordinates of an address.
using the latitude
n o
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.
s a
)h a
m
co uide
e
@ hp nt G
m ar tude
y - ku is S
e d d th
r e
r a th to us
( b ha nse
R e able
th sfer
Note:h aracantrimport
You a n Nokia geography reference data from the Manage Geographies user
B
interface. The- Oracle-licensed Nokia data from Nave is available for the US and a growing list
non If the licensed Nave data is not available for a particular country, then the Import
of countries.
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.
s a
)h a
m
co uide
e
@ hp nt G
m ar tude
y - ku is S
e d d th
r e
r a th to us
( b ha nse
R e able
a
To import rand
fer
athset nupsgeography data, you must import geography data for the countries
B h
where you n t r a
do- business. You can import Oracle-licensed Nokia data from Nave for those
nowhere the data is available.
countries
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: s a
h
) a
Import processing details. o m
c uide
Source data to object attribute mapping. hpe G
r @ n t
Job schedule details. m a tude
u
-kjob.his S
Monitor the progress of the import d y
d se t
r e
a r ath e to u
e dd ble l
t h R ra
a
File-basedr s fe
aimport nsupports:
Bh nof-trdata
Import
a
from an external file to interface tables.
n o
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 a
codes for each geography. h a s
)
c om ide
h pe t Gu
a r@ den
- k um Stu
e d dy this
t h r u se
a r a e to
e dd ble l
t h R ra
a
You can: r a nsfe
Bh n-trthe
Rename
a
values or codes for these lookup types.

no
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. a
Create before you can define a zone for a geographical.has
m )
Zones are geographical boundaries for a zone type. o
c uide
p e
h nt G
r @
a tude
u m
d y -k his S
r e d se t
a r ath e to u
e dd ble l
t h R ra
a r
For example,
a you ncan
s fecreate a United States Tax zone type, to include various tax zones in
h
country.n-tr
the B
a
no create:
When you
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.
s a
h
) a
o m
p e c uide
@ h nt G
r
a tude
u m
d y -k his S
r e d se t
a r ath e to u
e dd ble l
t h R ra
Setuphand n s fe > Run Maintain Geography Name Referencing
araMaintenance
B n-tforraa specific address record, the CA value in the STATE column of the
For example,
no
HZ_LOCATIONS table is mapped to the master reference geography of CA.
The application runs this process whenever you create a new address or edit an existing
address in the application. Additionally, you can run this process at scheduled intervals
to maintain address data quality.
Enter parameters before running the process:
Location Table Name: HZ_LOCATIONS or PER_ADDRESSES_F
Run Type: Use the New or All value to indicate which addresses should be referenced.
Usage Code: GEOGRAPHY or TAX.
Country Code: Enter the country to process addresses for.
From and To Location ID: Use ID to filter.
Start and End Date: Use dates to filter.

Quiz
Q
Which of the following do you define first?
a. Geography Hierarchy
b. Geography Structure
c. Geography Validation
s a
h
) a
o m
p e c uide
@ h nt G
r
a tude
u m
d y -k his S
r e d se t
a r ath e to u
e dd ble l
t h R ra
Answer:abr a nsfe
Bh n-tra
no

Quiz
Q
You can import geographies using either file-based import
or geography loader.
a. True
b. False
s a
h
) a
o m
p e c uide
@ h nt G
r
a tude
u m
d y -k his S
r e d se t
a r ath e to u
e dd ble l
t h R ra
Answer:aar a nsfe
Bh n-tra
no

Quiz
Q
A zone type cannot include geographies from multiple
countries.
a. True
b. False
s a
h
) a
o m
p e c uide
@ h nt G
r
a tude
u m
d y -k his S
r e d se t
a r ath e to u
e dd ble l
t h R ra
Answer:abr a nsfe
Bh n-tra
no

Quiz
Q
Geography Name Referencing is:
a. The process of cross-referencing address elements and
geography data.
b. The process of mapping geography structure and geography
hierarchy.
c. The process of cross-referencing source file columns and
import object attributes.
d. The process of mapping zones to zone types. sa ha
)
c om ide
h pe t Gu
a r@ den
- k um Stu
e d dy this
t h r u se
a r a e to
e dd ble l
t h R ra
Answer:aar a nsfe
Bh n-tra
no

Summary

Discuss the Vision Corporation Story elements.
Explore geography:
Structure
Hierarchy
Validation
s a
h
) a
o m
p e c uide
@ h nt G
r
a tude
u m
d y -k his S
r e d se t
a r ath e to u
e dd ble l
t h R ra
a r a nsfe
Bh n-tra
no

s a
h
) a
o m
p e c uide
@ h nt G
r
a tude
u m
d y -k his S
r e d se t
a r ath e to u
y (bh icens
e dd ble l
t h R ra
a r a nsfe
Bh n-tra
no
6
Configuring Enterprise
Structures
s a
h
) a
o m
p e c uide
@ h nt G
r
a tude
u m
d y -k his S
r e d se t
a r ath e to u
e dd ble l
t h R ra
a r a nsfe
Bh n-tra
no
Objectives

Enter enterprise structures using the Rapid Implementation
spreadsheet.
Define legal jurisdictions and authorities.
Search for legal entities.
Create legal reporting units.
s a
h
) a
o m
p e c uide
@ h nt G
r
a tude
u m
d y -k his S
r e d se t
a r ath e to u
e dd ble l
t h R ra
a r a nsfe
Bh n-tra
no

Define Enterprise Structures
s a
)h a
m
co uide
e
@ hp nt G
m ar tude
y - ku is S
e d d th
r e
r a th to us
( b ha nse
R e able
th er
Beginh ara tranthesfenterprise structure from the Setup and Maintenance work area.
configuring
TheBlist of tasks
- to complete is arranged in the order in which the list should be completed.
non consists of legal entities under common control and management.
An enterprise
In this section, we will discuss:
Rapid implementation of enterprise structures
Legal jurisdictions and authorities
Legal entities
Legal reporting units

Sharing Ledger Components Across Oracle
Applications
Many components of an accounting configuration are shared with
other Oracle Fusion Applications.
s a
)h a
m
co uide
e
@ hp nt G
m ar tude
y - ku is S
e d d th
r e
r a th to us
( b ha nse
R e able
r h sfer
ataccounts,
h a
The chart of
t r a n calendar, and currencies are called the three Cs because they are the
B
three mainn -
components required to create a ledger. An accounting method is also required
no method is available.
and a seeded
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.
s a
h
) a
o m
p e c uide
@ h nt G
r
a tude
u m
d y -k his S
r e d se t
a r ath e to u
e dd ble l
t h R ra
a r a nsfe
Bh n-tra
no

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. s a
h a
)entity,
Finalize your primary balancing segment value, legal m
and business unit relationships. c o ide
h pe t Gu
r@ den
Determine your document and journal asequencing
m Stu
requirements. -ku dy this
r e d se
r t h
a e to u
a
e dd ble l
t h R ra
a
Caution: r
Plan
fe
a yournsimplementation carefully, including the above requirements, before
B h t r a
- loading your spreadsheet. Some configurations cannot be changed after the
preparing and
non is loaded.
spreadsheet

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 s a
Banks, branches, and accounts h
) a
o m
Taxes
p e c uide
Fixed assets @ h nt G
r
a tude
And many more tasks u m S
-k dy this
r e d se
r t h
a e to u
a
e dd ble l
t h R ra
Use thea r
Define n s fe Configuration for Rapid Implementation task list to streamline your
a Financials
Bhconfiguration
setup n - tra to focus only on the critical setup steps. The rapid implementation task list
nothe time needed for you to complete your key setups and enable the day-to-day
minimizes
use of Oracle Fusion Financials.
Note: You cannot perform a complete implementation using only the Rapid Implementation
task list. You need to also use the tasks in the standard Financials task list to add and update
additional setup data.

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

assists you in creating components in spreadsheets:
A chart of accounts, legal entities, hierarchies, document

sequencing, key account assignments, a fiscal calendar,
account defaulting, and financial sequencing.
Primary ledgers and business units with assignment of all
business functions to use with your subledgers.
s a
a
)h
m
co uide
e
@ hp nt G
m ar tude
y - ku is S
e d d th
r e
r a th to us
( b ha nse
R e able
a
Navigate rto:
ferMaintenance > Search > Rapid Implementation > Expand Define
athSetupnsand
Bh Financials
Common n - tra Configuration for Rapid Implementation.
no that are included are legal addresses and mapping between legal entities and
Other objects
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 s a
) ha
c om ide
h pe t Gu
a r@ den
- k um Stu
e d dy this
t h r u se
a r a e to
e dd ble l
t h R ra
Navigatea rto:
fe Maintenance > Define Financials Configuration for Rapid
a Setupnsand
Bh n-tra> Expand list.
Implementation
noefficient implementations, use the Define Financials Configuration for Rapid
For fast,
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:
1. Enter the data into the spreadsheets.
2. Upload the XML files generated from the spreadsheets.
3. The deployment process to finalize the chart of accounts
configuration is run automatically.
4. Upload the XML files generated from the spreadsheets forsthea
rest of the configuration. )h a
c om ide
h pe t Gu
a r@ den
- k um Stu
e d dy this
t h r u se
a r a e to
e dd ble l
t h R ra
a
The Rapidr n s fe task configures your enterprise structures quickly:
aImplementation
Bh nsheets
Using - tra in a workbook to upload lists of companies (legal entities), ledgers,
no units, chart of account values, and other similar data.
business
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
s a
)h a
m
co uide
e
@ hp nt G
m ar tude
y - ku is S
e d d th
r e
r a th to us
( b ha nse
R e able
th sfer
All of h aracomponents
these
t r a n in a chart of accounts can be created using Rapid Implementation
B n-
spreadsheets:
n o
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.
s a
h
) a
o m
p e c uide
@ h nt G
r
a tude
u m
d y -k his S
r e d se t
a r ath e to u
y (bh icens
e dd ble l
t h R ra
a r a nsfe
Bh n-tra
no

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.
s a
h
) a
o m
p e c uide
@ h nt G
r
a tude
u m
d y -k his S
r e d se t
a r ath e to u
e dd ble l
t h R ra
r a Sets: s e
fNavigate
a
Manage Value
h -tra n to: Setup and Maintenance > Manage Value Sets.
B
non
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. s a
)h a
m
co uide
e
@ hp nt G
m ar tude
y - ku is S
e d d th
r e
r a th to us
( b ha nse
R e able
Segmenta r
labels
fer as part of the rapid implementation configuration of your chart of
ath arensassigned
Bh structure.
accounts n - tra You can review the assigned segment labels on the Manage Key Flexfield
no page, which you access using the Manage Structures button on the Manage Chart
Structures
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.
s a
) h a
o m
p e c uide
@ h nt G
r
a tude
u m
d y -k his S
r e d se t
a r ath e to u
e dd ble l
t h R ra
e
nsf labels are available: Primary, Second, and Third Balancing.
ara trasegment
Threehbalancing
B n- balancing segment label is required.
TheoPrimary
n
The Second and Third balancing segment labels are optional, and may not be
necessary unless, for example, you need to balance at more than the legal entity level
for management reporting.

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

types, accommodating tracking of specific business expenses
across natural accounts.

Enable combining expenses and head count data into cost
centers that are useful for detailed analysis and reporting.
Are optional, but required when:
Using Oracle Fusion Assets.
Storing expense approval limits in Oracle Fusion Expenses. a
h a s
m )
o
c uide
p e
h nt G
r @
a tude
u m
d y -k his S
r e d se t
a r ath e to u
e dd ble l
t h R ra
Note:h araa cost
Add n s fe segment if you plan to add Assets or Expenses in the future,
center
tra of accounts cannot be modified.
B then-chart
because
no

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.
s a
h
) a
o m
p e c uide
@ h nt G
r
a tude
u m
d y -k his S
r e d se t
a r ath e to u
e dd ble l
t h R ra
a r a nsfe
Bh n-tra
no

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

throughout Oracle Fusion Applications.
Used in Oracle Fusion General Ledger to facilitate:

Chart of accounts mappings
Revaluations
Data access sets
Cross-validation rules
Segment value set rules a
a s
Leveraged in:
m )h
Inquiry and Reporting e co uide
Smart View queries @ hp nt G
m ar tude
Allocations
y - ku is S
e d d th
r e
r a th to us
( b ha nse
R e able
th sfer
Note:h araspreadsheet
The
t r a n creates one hierarchy. To create additional hierarchies, use the
B n-
Generate Additional Hierarchy button (which appears on the Company and Natural Account
ogenerate
sheets)nto 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
s a
Financials, with additional functionality.
a
)h
m
co uide
Is used to partition your subledgers data. p e
@ h nt G
r
a tude
u m
d y -k his S
r e d se t
a r ath e to u
e dd ble l
t h R ra
r abusiness s e
funit
h a
Normally, a
t r a n has a manager, strategic objectives, a level of autonomy, and
B
responsibility-for its profit and loss.
non

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.
s a
)h a
m
co uide
e
@ hp nt G
m ar tude
y - ku is S
e d d th
r e
r a th to us
( b ha nse
R e able
a
Navigate r athSetupnsand
to:
ferMaintenance > Create Chart of Accounts, Ledger, Legal Entities, and
Bh Units
Business n - trina Spreadsheet
nodata in a sheet like the one shown above.
You enter
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 s a
a
)h
Segment Value Security Rules m
Account Combinations e co uide
hp G
a r@ dent
- k um Stu
e d dy this
t h r u se
a r a e to
e dd ble l
t h R ra
a r a nsfe
Bh n-tra
no

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:
s a
a
Define security rules and assign the rules to your usershroles
)
using the segment value security rules spreadsheet.o m
Assign access to segment values using common p e u ide
coperators
@ h nt G
a r
such as equals, between, and is descendant of.
e
k u m Stud
d d y- this
t h re use
a r a e to
e dd ble l
t h R ra
a
Navigate rto:
fe Maintenance > Create Cross-Validation Rules in Spreadsheet.
a Setupnsand
Bh n-traexample: Balance sheet accounts are not combined with operational cost
Cross Validation
no
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.
s a
h
) a
o m
p e c uide
@ h nt G
r
a tude
u m
d y -k his S
r e d se t
a r ath e to u
e dd ble l
t h R ra
a
Navigate rto:
fe Maintenance > Manage Account Combinations > Create in
a Setupnsand
Bh n-button.
Spreadsheet tra
no

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 Owners 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 a ins
a
setup objects, such as ledgers, bank accounts, asset
h
)books,
c m
o payables
e
intercompany accounts, receivables system p
e Gu
options, i d
common options, and so on. h nt
r@ a tude
u m
d y -k his S
r e d se t
a r ath e to u
e dd ble l
t h R ra
a
Navigate r a Setupnsand
to:
fe Maintenance > Create Chart of Accounts, Ledger, Legal Entities, and
Bh Units
Business n - trina Spreadsheet.
All
o
navailable 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.
s a
)h a
m
co uide
e
@ hp nt G
m ar tude
y - ku is S
e d d th
r e
r a th to us
( b ha nse
R e able
a
Navigate r athSetupnsand
to:
ferMaintenance > Create Chart of Accounts, Ledger, Legal Entities, and
Bh Units
Business n - trina Spreadsheet.
no sequences are enabled at the legal entity level for countries with such a
For example,
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
s a
a
)h
m
co uide
e
@ hp nt G
m ar tude
y - ku is S
e d d th
r e
r a th to us
( b ha nse
R e able
r th sfer
aChart
h a
The Create
t r a nof Accounts, Ledger, Legal Entities, and Business Units workbook provides
B
six sheets.n-
no
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.
s a
h
) a
o m
p e c uide
@ h nt G
r
a tude
u m
d y -k his S
r e d se t
a r ath e to u
y (bh icens
e dd ble l
t h R ra
a r a nsfe
Bh n-tra
no

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
s a
)h a
m
co uide
e
@ hp nt G
m ar tude
y - ku is S
e d d th
r e
r a th to us
( b ha nse
R e able
a
Navigate rto:
ferMaintenance Create Chart of Accounts, Ledger, Legal Entities, and
athSetupnsand
Bh Units.
Business n - tra
no you finish preparing the data in the sheets, click the button called Validate Data. A
After
Validation Report is generated. If there are errors, correct them before proceeding.
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 > Upload Chart of Accounts. This task launches
the Upload Enterprise Structures and Hierarchies process. Select the Upload Enterprise
Structure option. Click the Choose File button and select the first zip file you have
saved. Click Submit.
Navigate to: Tools > Scheduled Processes. Verify that the process was completed.
Navigate to: Setup and Maintenance > Upload Ledger, Legal Entities, and Business
Units. Click 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.
s a
h
) a
o m
p e c uide
@ h nt G
r
a tude
u m
d y -k his S
r e d se t
a r ath e to u
y (bh icens
e dd ble l
t h R ra
a r a nsfe
Bh n-tra
no

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.
s a
h
) a
o m
p e c uide
@ h nt G
r
a tude
u m
d y -k his S
r e d se t
a r ath e to u
e dd ble l
t h R ra
a r a nsfe
Bh n-tra
no

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. a
h a s
m )
o
c uide
p e
h nt G
r @
a tude
u m
d y -k his S
r e d se t
a r ath e to u
e dd ble l
t h R ra
In a r
the
aparameters
n s feregion of the Upload Chart of Accounts process, select the first file
h saved,
Byou - traXXChartOfAccounts.xml, and submit the process.
n
no loading your chart of accounts file, deployment of the chart of accounts is
After
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. a
a
Deployed: The flexfield definition is deployed and available
s to
m )h
end users.
e co uide
Error: The deployment attempt failed. r@h nt G
p
m a tude
u
-k his S
d y
d se t
r e
a r ath e to u
e dd ble l
t h R ra
a r
Deployment
a deploys
n s fecharts of accounts in the system during each run. To verify that the
all
Bh n-Status
Deployment tra has finished, navigate to the Manage Key Flexfields page from the Setup
no
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
Practice 6-4: Verifying Deployment Was Successful

Demonstration
Practice 6-5: Uploading the Ledger, Legal Entity, and
Business Unit File
s a
h
) a
o m
p e c uide
@ h nt G
r
a tude
u m
d y -k his S
r e d se t
a r ath e to u
e dd ble l
t h R ra
a r a nsfe
Bh n-tra
no

Other Spreadsheet Uses
Oracle Fusion Applications deliver extensive spreadsheet

integration across multiple finance functions, allowing finance
users to work in a familiar environment.

Budgets can be uploaded and budget import errors can be
corrected by using the Correct Budget Import Errors
spreadsheet.
Spreadsheets are seamlessly integrated with the applications
for high-volume data entry and one-click uploads.
In addition, all reports and transactional tables can be) ha
sa
exported to Microsoft Excel for further analysis and
c om
easier
i d e
viewing of large amounts of data. hpe t Gu
a r@ den
- k um Stu
e d dy this
t h r u se
a r a e to
e dd ble l
t h R ra
a r a are nsome
The following s feexamples of where spreadsheets are used in Oracle Fusion
Bh n-tra
Applications:
no Ledger: Enter account combinations, cross-validation rules, and journals,
General
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
s a
)h a
m
co uide
e
@ hp nt G
m ar tude
y - ku is S
e d d th
r e
r a th to us
( b ha nse
R e able
r th sfer
aStructures
a
h -tran Setup Report:
Enterprise
B
on your enterprise structures configuration.
Validates
n
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
s a
)h a
m
co uide
e
@ hp nt G
m ar tude
y - ku is S
e d d th
r e
r a th to us
( b ha nse
R e able
r ath > Click
s f er
Welcome
h a page
t r a n your User Name to open Settings and Actions menu >
B n- > Run Diagnostics Tests.
Troubleshooting
n o
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. s a
a
)h
Note: When you create a legal entity, m
the application automatically creates: e co uide
p t h G
A registration for the new legal entity.ar@ e n
A main legal reporting unit. k u m Stud
- dy this
r e d se
r t h
a e to u
a
e dd ble l
t h R ra
Legal h ara tranand
jurisdictions sfeauthorities may be relevant to your Oracle Fusion Financials
B n- only if you:
implementation
UsenoOracle Fusion Payables and Oracle Fusion Receivables.
Perform tax calculations.

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

applies to a group of countries or a single country, state, county,
or parish.
Examples: French Labor Law, Singapore Transactions Tax
Law, and US Income Tax Laws.
Types of jurisdictions are:
Identifying Jurisdiction
Income Tax Jurisdiction a
a s
Transaction Tax Jurisdiction
m )h
Income tax jurisdictions and transaction tax jurisdictions e co are
u idetwo
distinct jurisdictions, but can:
p
h nt G
r @
a tude
Be defined at the same geopolitical u m
k is Ssuch as a country.
level,
d y -
Share the same legal authority. r e d e th
r a th to us
( b ha nse
R e able
r s f er
ath jurisdiction:
a
h -trinaancountry. First jurisdiction you must register with to be allowed to do
Identifying
Bbusiness
n- onSelect 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 Fusion Tax in a separate business flow.
- Contains specific needs and complexities of various taxes.
- Receives their respective rates from their suppliers.
- Requires periodic maintenance.
- Is used for legal reporting of sales and value-added taxes.

Legal Authorities Overview
A legal authority is a government or legal body that is charged

with powers to make laws, levy and collect fees and taxes,
and remit financial appropriations for a given jurisdiction.

For example, the Internal Revenue Service is the legal
authority responsible for collecting taxes and the interpretation
and enforcement of the Internal Revenue Code of the United
States.
s a
)h a
m
co uide
e
@ hp nt G
m ar tude
y - ku is S
e d d th
r e
r a th to us
( b ha nse
R e able
r th sfer
aauthority
a
Legal
h example,
t r a n information is printed on your tax reports to meet country requirements,
Bfor n- for India and Brazil.
n o
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
s a
h
) a
o m
p e c uide
@ h nt G
r
a tude
u m
d y -k his S
r e d se t
a r ath e to u
e dd ble l
t h R ra
a r a nsfe
Bh n-tra
no

Manage Legal Entities
s a
)h a
m
co uide
e
@ hp nt G
m ar tude
y - ku is S
e d d th
r e
r a th to us
( b ha nse
R e able
r h sfer
atentity
A a
h -tranis a recognized party with rights and responsibilities given by legislation.
legal
B
nonand the responsibility to account for themselves to regulators, taxation authorities,
A legal entity has the right to own property, the right to trade, the responsibility to repay
debt,
and owners according to rules specified in the relevant legislation.
A legal entitys 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. s a
a
)h
Preparing for acquisitions or disposals of parts of o the
m
enterprise. p e c uide
@ h nt G
r
Isolating one area of the business fromarisks in deanother area.
u m t u
Facilitating local compliance. dy-k his S
r e d se t
a r ath e to u
e dd ble l
t h R ra
a r
For example, s fe develops and leases properties. You can create separate legal
a yournenterprise
Bh for ndevelopment
entities - tra and leasing. This would minimize risk across your lines of business.
no

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
A legal entity must comply with the regulations of jurisdictions
s
in which they register. )h a
m
To support local reporting requirements, legalpe co uidunits
reporting e
h G
are created and registered. r@ ent a tud
u m
d y -k his S
r e d se t
a r ath e to u
e dd ble l
t h R ra
If you h arapurchases
make n s feand sell to and from companies under your control, define these
ra legal entities as customers and suppliers.
B nor-tother
companies
no
Transactions between legal entities require accounting.
Accounting for transactions between legal entities under common control (your legal
entities) is called intercompany accounting.
Legal entities can be identified as legal employers on the Manage Legal Entity page. In
Oracle Fusion Financials, the employees employed by the legal employer can be assigned as
users.

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

legal entities.
Enter legal entities on transactions that represent a movement

in value or obligation.
Ownership provides, under contract law in most countries, that
damages can be sought:
For actual losses, putting the injured party in the same state as
if they had not entered into the contract. a
a
For loss of bargain, meaning the profit that could have been
s
made on a transaction. m )h
co
e e
uid
h p G
a r@ dent
- k um Stu
e d dy this
t h r u se
DAMAGES & LOSSES
r a t o
( b ha nse
R e able
a r ath nsfer
Bh n-tra
no

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.
s a
a
)h
m
co uide
e
@ hp nt G
m ar tude
y - ku is S
e d d th
r e
r a th to us
( b ha nse
R e able
r th sfer
aunit
h a
A business
t r is n
a a unit of an enterprise that performs one or many business functions that
B n-up in a management hierarchy. A business unit can process transactions on
can be rolled
nomany
behalf of legal entities.
In Oracle Fusion Applications, use business unit as a securing mechanism for transactions.
For example, if you run your export business separately from your domestic sales business,
secure the export business data to prevent access by the domestic sales employees. To
accomplish this security, set up the export business and domestic sales business as two
separate business units.

Legal Entity and Divisions
Divisions
s a
a
)h
m
co uide
e
@ hp nt G
m ar tude
y - ku is S
e d d th
r e
r a th to us
( b ha nse
R e able
a
Divisions r ath nsfer
Bh n-tanraarea of management responsibility that can correspond to a collection of
Provide
no entities or to part of a single legal entity or of several legal entities.
legal
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.
s a
)h a
m
co uide
e
@ hp nt G
m ar tude
y - ku is S
e d d th
r e
r a th to us
( b ha nse
R e able
r h sfer
atone
a
h -traorn more legal entities to your configuration using the Assign Legal Entities
Assign
Btask.
non balancing segment values to your legal entities using the Assign Balancing
Assign
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 Fusion General Ledger supports the use of up to three

balancing segments.
Best practice is to use at least one balancing segment to
represent a legal entity to facilitate financial reporting to
regulatory agencies, tax authorities, and investors.
If you want to subdivide legal entities into lower levels for a
reporting, you can use one or two additional balancing h a s
m )
segments in your chart of accounts. c o de
h pe t Gui
a r@ den
- k um Stu
e d dy this
t h r u se
a r a e to
e dd ble l
t h R ra
Assign a r a nsegment
balancing s fe values.
Bh nuse
If you - traa balancing segment to represent legal entities, you should represent each
no entity as its own balancing segment value.
legal
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 thea
application to ensure balancing of journal entries. h a s
m )
Carefully consider whether to use multiple balancing o
c uide
h p e
segments before using a ledger. tG
r@ den
a
- k um Stu
e d dy this
t h r u se
a r a e to
e dd ble l
t h R ra
Cautiona r a nsfe
Bh na -ledger
After
tra has been used, historical balances are not automatically converted based
no the selection of additional balancing segments.
upon
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, a
which books changes to intercompany accounts by legal a s
entity
m )h
to balance and clear intercompany amounts. co de
h pe t Gui
a r@ den
- k um StuReceivables
Payables
e d dy this
t h r u se
a r a e to
e dd ble l
t h R ra
a r
Post intercompany s fe
a ntransactions directly to the General Ledger. Subledger invoicing is not
B h t r a
- these transactions get directly transferred and posted to the general ledger.
required. Instead,
To usen onfunctionality:
this
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.
s a
)h a
m
co uide
e
@ hp nt G
m ar tude
y - ku is S
e d d th
r e
r a th to us
( b ha nse
R e able
a r
Consolidation s fer process of combining the financial results of separate
athis anperiod-end
Bh n-with
subsidiaries trathe parent organization to form a single, combined statement of financial
o
results.nConsolidation 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 a
newly added Sequencing region of the Specify Ledger has
Options user interface. m )
c o e
h p e G uid
a r@ dent
- k um Stu
e d dy this
t h r u se
a r a e to
e dd ble l
t h R ra
a
Navigate rto:
fe Maintenance > Define Ledgers > Specify Ledger Options.
a Setupnsand
Bh n-Sequencing
Setothe
tra By option to either Ledger or Legal entity to enable document
n
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.
s a
h
) a
o m
p e c uide
@ h nt G
r
a tude
u m
d y -k his S
r e d se t
a r ath e to u
e dd ble l
t h R ra
a r a nsfe
Bh n-tra
no

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 a
domestic and foreign h a s
establishments. m )
o
c uide
p e
h nt G
r @
a tude
u m
d y -k his S
r e d se t
a r ath e to u
e dd ble l
t h R ra
e
funits
arareporting
Definehlegal
t r a n s by:
B
on- location, such as sales office.
A physical
n
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 a
a
this legal entitys reporting requirements in each local)area.
h s
c om ide
h pe t Gu
a r@ den
- k um Stu
e d dy this
t h r u se
a r a e to
e dd ble l
t h R ra
Note:h Multiple n fe can be associated with a legal reporting unit. However, only one
ara trregistrations
s
identifying - a defined with the legal authority used for the legal entity or legal
B nregistration
nounit can be associated with the legal reporting unit.
reporting

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

s a
h
) a
o m
p e c uide
@ h nt G
r
a tude
u m
d y -k his S
r e d se t
a r ath e to u
e dd ble l
t h R ra
a r a nsfe
Bh n-tra
no

Summary

Enter enterprise structures using the Rapid Implementation
spreadsheet.
Define legal jurisdictions and authorities.
Search for legal entities.
Create legal reporting units.
s a
h
) a
o m
p e c uide
@ h nt G
r
a tude
u m
d y -k his S
r e d se t
a r ath e to u
e dd ble l
t h R ra
a r a nsfe
Bh n-tra
no

s a
h
) a
o m
p e c uide
@ h nt G
r
a tude
u m
d y -k his S
r e d se t
a r ath e to u
y (bh icens
e dd ble l
t h R ra
a r a nsfe
Bh n-tra
no
7
Configuring General Ledger

Components
s a
h
) a
o m
p e c uide
@ h nt G
r
a tude
u m
d y -k his S
r e d se t
a r ath e to u
e dd ble l
t h R ra
a r a nsfe
Bh n-tra
no
Objectives

Manage value sets.
Review chart of accounts components.

Manage and publish account hierarchies.
Maintain segment values.
Manage cross-validation rules.
Create account combinations.
s a
Define calendars and currencies. h
) a
o m
p e c uide
@ h nt G
r
a tude
u m
d y -k his S
r e d se t
a r ath e to u
e dd ble l
t h R ra
a r a nsfe
Bh n-tra
no

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 s a
h
) a
Define and Maintain Intercompany Processing Rules m
o
c uide
Define Budget Configuration p e
h nt G
r @
Define Financial Reporting a de
um Stu
- k
e d dy this
t h r u se
a r a e to
e dd ble l
t h R ra
a
Navigate r
to: s feMaintenance > Financials > Expand list.
a Setupnand
Bh n-toptional
To implement
ra
and more advanced features, use the Financials task lists.

no 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
s a
h
) a
o m
p e c uide
@ h nt G
r
a tude
u m
d y -k his S
r e d se t
a r ath e to u
e dd ble l
t h R ra
r e
a creatensa fchart
a
To manually
h -tra of accounts:
B
on value sets.
Define
n
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.
s a
)h a
m
co uide
e
@ hp nt G
m ar tude
y - ku is S
e d d th
r e
r a th to us
( b ha nse
R e able
th sfer
ara tvalues
Do nothcreate
r a n in your value set until after the structure and instance creation because
B -
some valuenattributes, such as Allow Posting or Account Type, are not available.
no

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

chart of accounts segments.
s a
)h a
m
co uide
e
@ hp nt G
m ar tude
y - ku is S
e d d th
r e
r a th to us
( b ha nse
R e able
a
Navigate rto:
ferMaintenance > Manage Value Sets.
athSetupnsand
Bh n-istrato use only the Validation Type of Independent and the Value Data Type of
Best practice
no(Char) for your chart of accounts value sets. Use the Value Subtype of Text. You
Character
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.
s a
h
) a
o m
p e c uide
@ h nt G
r
a tude
u m
d y -k his S
r e d se t
a r ath e to u
y (bh icens
e dd ble l
t h R ra
a r a nsfe
Bh n-tra
no

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 a
values and report on each segment independently. ) ha
s
c om ide
h pe t Gu
a r@ den
- k um Stu
e d dy this
t h r u se
a r a e to
e dd ble l
t h R ra
e
Note:h ara transf value sets are not supported in Oracle Financials Cloud.
Table-validated
B nother
Table and - validation types that are available and used with different types of flexfields,
n o
such as descriptive flexfields or the Asset Category key flexfield, but not with the Accounting
Key flexfield, are:
Format only: Data is entered and not selected from a list.
Dependent: List of values for which a valid value is determined by the independent
value of another segment.
Subset: List of values that is a subset of the values in an existing independent value
set.

Practice 7-1 Overview: Searching for and Reviewing
Your Value Sets
Finding the value sets created from the spreadsheet.
Reviewing the values created from the spreadsheet.
s a
h
) a
o m
p e c uide
@ h nt G
r
a tude
u m
d y -k his S
r e d se t
a r ath e to u
e dd ble l
t h R ra
a r a nsfe
Bh n-tra
no

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.
s a
)h a
m
co uide
e
@ hp nt G
m ar tude
y - ku is S
e d d th
r e
r a th to us
( b ha nse
R e able
ath innthe r
fefuture
Making h a r
changes a s to the structure and instances of your chart of accounts is
B t r
- recommended.
difficult andnnot
n o
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.
s a
)h a
m
co uide
e
@ hp nt G
m ar tude
y - ku is S
Sample Chart of Accounts
e d d Structure
th
r e
r a th to us
( b ha nse
R e able
r er
ath nsfsecurity
Caution:
h a Remember
t r a is enabled at the value set level and applies to all segments that
B - set.
use that value
non

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
a
level. a s
)h
c om ide
h pe t Gu
a r@ den
- k um Stu
e d dy this
t h r u se
a r a e to
e dd ble l
t h R ra
a r a is fivenstofenine segments. Avoid total concatenated lengths of over 28 to 30
Best practice
Bh nas-tyou
characters ra can have problems with the chart of accounts truncating on some
no reports and it complicates data entry.
predefined

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. a
a s
)h
Determines whether dynamic insertion is enabled to generate
m
new account combinations dynamically insteadeofcoyouuicreating
de
p
them manually. @h nt G ar tude
m
ku is S
d y -
r e d e th
r a th to us
( b ha nse
R e able
r th sfer
aassign
h a
Optionally,
t r a nunique hierarchies to create relationships between the value set values for
B
on- ofinaccounts
each segment
with thenchart
the instance by the assignment of a tree code to the value set associated
instance segment.
Different value sets and values are required to meet local and statutory reporting
requirements.
At the chart of accounts structure instance level:
Optionally, override the value sets provided by default from the chart of accounts
structure.
Assign a value set with the same segment type and length to each segment.
Create hierarchies for each segment to meet financial reporting requirements.
Assign a tree code to each instance segment to indicate the source of the hierarchy
information for the associated value set.

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

a complete or partial account combination.
You can use these descriptive labels to complete journal

entries.
s a
)h a
m
co uide
e
@ hp nt G
m ar tude
y - ku is S
e d d th
r e
r a th to us
( b ha nse
R e able
a
Example rabove: s fer to General Accounting > Journals > Tasks > Create Journal.
ath nNavigate
Bh n-tenter
Youocan
ra account segment values faster and easier by using account shorthand
n during entry of journals and other accounting transactions.
aliases
The account aliases allow you to complete journal entries by selecting descriptive labels
instead of remembering complex account combinations.
The underlying account segment values default automatically into the data entry fields.
Using this feature minimizes data entry errors, eliminating the need to correct or reverse
journals.
Steps to Enable Account Shorthand Alias
Navigate to: Setup and Maintenance > Key Flexfield Structure Instance to have the
application implementation administrator enable the shorthand alias feature.
Redeploy the chart of accounts structure.

Note: The list of values of eligible Chart of Accounts instances appears in the Manage
Shorthand Aliases page, only after these two earlier steps have been completed.
Navigate to: Setup and Maintenance > Manage Shorthand Aliases page in Functional
Setup Manager, select your chart of accounts structure instance, and click the Search
button to view existing aliases.
Click the Add (+) icon to add new aliases.
s a
h
) a
o m
p e c uide
@ h nt G
r
a tude
u m
d y -k his S
r e d se t
a r ath e to u
y (bh icens
e dd ble l
t h R ra
a r a nsfe
Bh n-tra
no

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:
Searching for Your Chart of Accounts Structure and Instance
Review your structure created from the spreadsheet.

Verify your instance settings created from the spreadsheet.
Deploying a Chart of Accounts Demonstration: Use this demo
to complete the enabling of the shorthand alias option.
Creating an Account Shorthand Alias: Create an account
shorthand alias for your cash account. sa ha
)
c om ide
h pe t Gu
a r@ den
- k um Stu
e d dy this
t h r u se
a r a e to
e dd ble l
t h R ra
a r a nsfe
Bh n-tra
no

Define Segment Values
Enter valid values for each segment after adding them to the
chart of accounts structure and structure instance.
s a
)h a
m
co uide
e
@ hp nt G
m ar tude
y - ku is S
e d d th
r e
r a th to us
( b ha nse
R e able
th sfer
Each h arais tdefined
value
r a n with a name, description, and optionally a start date and end date.
B n- the Setup and Maintenance work area to the Manage Chart of Accounts Value
Navigateofrom
n
Sets page.
Click the Manage Values button to enter values for each segment. These are the values that
you use when building your account combinations.
Enable the segment value. The period of usage must fall within the start and end dates if
entered on the value.
Note: Sort Order is not used with the Accounting key flexfield.
Caution
When creating a new chart of accounts with new value sets, create the value sets
definition first and leave the values creation until after the creation of the instance and
structure.
Creating values before assigning the value set to the account structure 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.
s a
)h a
m
co uide
e
@ hp nt G
m ar tude
y - ku is S
e d d th
r e
r a th to us
( b ha nse
R e able
h sfer
ratselect
Note:hIfa
you a nYes for Summary (Parent), the application does not post to the accounts
B t r
n- that value even if Allow Posting is set to Yes. Account Type, Third Party Control
created using
noReconcile,
Account, 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 Fusion V1.)
Financial Category: Financial Category is used with Oracle Transactional Business
a
Intelligence reporting to further identify groups of accounts. This is required if you want
s
h a
to run the Payables to General Ledger Reconciliation report or the Receivables to
)
General Ledger Reconciliation report. o m
p e c uide
@ h nt G
r
a tude
u m
d y -k his S
r e d se t
a r ath e to u
y (bh icens
e dd ble l
t h R ra
a r a nsfe
Bh n-tra
no

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: a
Enforce consistency h a s
between the source system m )
o
c uide
and the GL account p e
h nt G
balance by not allowing you r @
a tude
u m S
to enter GL journals against y-k i s
d t h
control accounts. red se
a r ath e to u
e dd ble l
t h R ra
r e
aenter nGLsfjournals
h a
You cannot
t r a against control accounts because that would make the source
B - GL system out of balance.
system andnthe
no

Control Accounts Explained
s a
)h a
m
co uide
e
@ hp nt G
m ar tude
y - ku is S
e d d th
r e
r a th to us
( b ha nse
R e able
th sfer
ara tryour
Whenhdefining a n natural account segment values, you can designate an account as a
B - using the attributes on the Manage Values page from the Setup and
control account
non work area. Select one of the following options:
Maintenance
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.
s a
h
) a
o m
p e c uide
@ h nt G
r
a tude
u m
d y -k his S
r e d se t
a r ath e to u
e dd ble l
t h R ra
a r a nsfe
Bh n-tra
no

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.
s a
h
) a
o m
p e c uide
@ h nt G
r
a tude
u m
d y -k his S
r e d se t
a r ath e to u
e dd ble l
t h R ra
r a accounts e
fhierarchies
a
Create n
h -tra among your value (trees) to identify managerial, legal, or geographical
Brelationships
n set values.
n o
Define date-effective tree versions to reflect organizational changes within each
hierarchy over time.
Publish multiple hierarchies to balances cubes to allow for financial reporting and
analysis of past, present, or future data.
Note: Oracle Fusion Applications 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 Fusion Applications, chart of accounts
values and account hierarchies (trees) are maintained in DRM rather than in Oracle Fusion
Applications.

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

define three different hierarchies to be used for each chart of
accounts segment that has rollups, each for a particular purpose:

1. Hierarchies for financial reporting: Must be published to
Essbase cubes.
2. Hierarchies for allocations: Must be published to Essbase
cubes.
3. Hierarchies for cross-validation rules, revaluation, and chartaof
accounts mapping: Do not publish to the Essbase cube h a s
m )
because multiple child assignments are not supported
o
c uiind ethe
Essbase cube.
e
hp t G
a r@ den
- k um Stu
e d dy this
t h r u se
a r a e to
e dd ble l
t h R ra
r e
a nforsffinancial
a
Hierarchies
h -tparentsr reporting: Child values in these hierarchies cannot roll up to
a within a hierarchy
Bdifferent because this functionality is not supported when you
non such hierarchies to Essbase.
publish
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
s a
)h a
m
co uide
e
@ hp nt G
m ar tude
y - ku is S
e d d th
r e
r a th to us
( b ha nse
R e able
h sfer
ratrare
Note:h Inathe a n in which you can use the same hierarchical account relationships for
cases
B t r
n- allocations, cross-validation rules, revaluations, and your chart of accounts
financial reporting,
mapping nodefinition, 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.s a
a
) hto
Note: You can use the Rapid Implementation spreadsheet m

create account hierarchies, as discussed in the previous
e co uchapter.
ide
p h nt G
r @
a tude
u m
d y -k his S
r e d se t
a r ath e to u
e dd ble l
t h R ra
Note:h araRapid
The n s fe
Implementation spreadsheet can be used to maintain and create
B
hierarchies.n- t r a
no
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: sa a
Optimize parent/child relationships. m )h
View information for run-time performance that e
iscostored
u idine an
p
h nt G
additional column in a table for all parents
r@of a child.
6. Use the Set Status feature in the-k um S
Actions tu to set the
menu
a de
is
dyhierarchy.
status to active and activate
edthe he th
r us
r a t t o
( b ha nse
R e able
th sfer
Note:h aracantrcreate
You a n additional tree versions from the Rapid Implementation Enterprise
B
Structures n -
spreadsheet.
no

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.
s a
a
)h
m
co uide
e
@ hp nt G
m ar tude
y - ku is S
e d d th
r e
r a th to us
( b ha nse
R e able
r s f er
ath Hierarchies:
Managea
h -tran
Account Specify Nodes
B n Setup and Maintenance > Manage Account Hierarchies > Search > Expand
Navigateoto:
Name >nClick 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 patha
includes the tree version name. has)
o m
p e c uide
@ h nt G
r
a tude
Publish u m
d y -k his S
r e d se t
a r ath e to u
e dd ble l
t h R ra
a r a nsfe
Bh n-tra
no

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.
s a
)h a
m
co uide
e
@ hp nt G
m ar tude
y - ku is S
e d d th
r e
r a th to us
( b ha nse
R e able
th er
ara transf spreadsheets automatically create a baseline version and a current
RapidhImplementation
B n-
version.
no create your hierarchies, you should create two versions, such as baseline and
If you manually
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]
[All VF Cost Centers-V2].[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 newa
names: h a s
)
[All VF Cost Centers-V1].[999].[500] c om ide
[All VF Cost Centers-V2].[999].[500] h pe t Gu
a r@ den
- k um Stu
e d dy this
t h r u se
a r a e to
e dd ble l
t h R ra
a
The fully r a nmember
qualified s fe name path for a member may change if you originally published a
Bhhierarchy
single n - trato a cube and later published another hierarchy that includes the same chart
no value.
of accounts
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 Fusion General Ledger Hierarchies: Recommendations
and Best Practices (Doc ID 1520970.1) on My Oracle Support.

Troubleshooting
Issue Possible Resolution

Tree Version Audit Make sure parent values have the summary attribute set
Process Fails When correctly.

Activating Version. Make sure you did not mistakenly assign children to child
values.
Fix could be as simple as switching the summary attribute flag.
However, if you mistakenly made a parent value a child value
and posted transactions to that account, then a more intensive
data fix may be required.
Tree Hierarchy Submit the process to propagate and update required account
Defined in Oracle s a
hierarchies to the Essbase GL balances cube from the Publish
Fusion GL Is Not Account Hierarchies page. )h a
m
coversions
Available in Essbase
Check that the Publish option is enabled forthe
GL Balances Cubes. p e u i dethat
are to be published.
@ h nt G
r
a and
Check that a request ID is returned dtheeprocess completes
u m t u
S action button.
d y -k thehiPublish
successfully after you click
s
r e d se t
a r ath e to u
e dd ble l
t h R ra
a r a nsfe
Bh n-tra
no

Troubleshooting
Issue Possible Resolution

Error in Publish Account Make sure all users sign out of Financial Reporting,
Hierarchies or Publish Chart Smart View, and Calculation Manager during the
of Accounts Dimension submission of the publish process. You cannot have
Members and Hierarchies users connecting to the cube while running these
programs. programs.
Need a new accounting New scenario members are added in the predefined
scenario member to load value set called Accounting Scenario.
budget and forecast data into Query this predefined value set, and add a new value
Essbase GL balances cubes. for each budget or forecast that needs to be tracked
in Essbase GL balances cubes.
s a
Enabled or disabled flexfield Enabled or disabled flexfield security policies
a
) harenot
m
security policies are not in
effect for Essbase GL
automatically applied to the Essbase
after the cube was created. pe
cocubeuifidseteup
balances cube. @ h nt G
Account hierarchies must r be
a disabled e
republished
d in order to
apply newly enabledm
ku is S
or t u flexfield security
policies. dy-
r e d e th
r a th to us
( b ha nse
R e able
th sfer
Note:h ara trsecurity
Flexfield n is enabled and disabled in the Manage Value Set page.
B n- a
no

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.
s a
h
) a
o m
p e c uide
@ h nt G
r
a tude
u m
d y -k his S
r e d se t
a r ath e to u
e dd ble l
t h R ra
a r a nsfe
Bh n-tra
no

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.
s a
)h a
m
co uide
e
@ hp nt G
m ar tude
y - ku is S
e d d th
r e
r a th to us
( b ha nse
R e able
a r
For example,
fera new department as of January 1, 2014, you can create an account
athif younshave
Bh n-with
combination traa From Date of 01-JAN-2014 and the account combination becomes
o that date. This functionality enables you to create the account combinations in
non
enabled
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 Owners
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.
s a
h
) a
o m
p e c uide
@ h nt G
r
a tude
u m
d y -k his S
r e d se t
a r ath e to u
e dd ble l
t h R ra
a r a nsfe
Bh n-tra
no

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

maintenance by automatically replicating changes to segment
value attributes of the account combinations that contain that

segment value.
s a
a
)h
m
co uide
e
@ hp nt G
m ar tude
y - ku is S
e d d th
r e
r a th to us
( b ha nse
R e able
a r
For example,
fer a particular cost center segment value that had been disabled
athif younsenable
Bh nnavigate
previously, - tra to: Setup and Maintenance > Maintain Segment Value Attributes to run
noSegment Value Attributes process and re-enable all account combinations
the Inherit
containing that cost center automatically.
Prevent selected account combinations from being affected by segment value attribute
changes by selecting the Preserve Attribute check box on Manage Account Combinations.
Use the Segment Value Inheritance Exception Report to view the account combinations
that have been changed.
Individual segment value attributes override account combination attributes.
An account combination is composed of several segment values. If these segment
values have conflicting settings for Enabled, Allow Posting, From Date, or To Date, the
most restrictive of the settings for any of the individual segment values applies to the
account combination.
If you disable a segment value, the combinations that contain that value can no longer
be used, even if the Preserve Attributes check box is selected.
Note: You can also disable an account combination or change other attributes in the Manage
Account Combination page.

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

segment in your chart of accounts.
Create and edit segment value security on the Define Chart of

Accounts page from the Setup and Maintenance work area.
s a
h
) a
o m
p e c uide
@ h nt G
r
a tude
u m
d y -k his S
r e d se t
a r ath e to u
e dd ble l
t h R ra
a r a nsfe
Bh n-tra
no

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

control access to parent or detail segment values.
Secure a value set to deny access to all values by default.

Create conditions and assign them to specific data roles to
control access to your segment values.
Restrict data entry, online inquiry, and reporting to specific
values by using segment value security rules.
For example, create a segment value security rule that grantssaa
user access only to his or her own department. ) ha
Note: Segment value security is enforced in Oracle c om ide
Fusion
h pe t Gu
Applications wherever the chart of accountsr@ valuesen
a
m Stud
are used. - k u
e d dy this
t h r u se
a r a e to
e dd ble l
t h R ra
r a between s e
fsetup
h a
A distinction
t r a n and transaction user interfaces is that segment value security
B
prevents you -from seeing certain account values in transaction user interfaces, but you can
onaccount
still seenthe 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.

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.
s a
a
)h
m
co uide
e
Co CC Acct @ hp nt G I/C
a r d e
- k um Stu
e d dy this
t h r u se
a r a e to
e dd ble l
t h R ra
a
Based r s fe provisioned to users, data security policies determine which values
aon thenroles
Bofh thensegment
- tra end users can view or modify.
no access to parent or detail segment values.
Controls
For example, if the same value set is used for the balancing segment and intercompany
segment of a chart of accounts, then the same security rules apply to both. Thus, if you
create a security rule that only allows you to access balancing segment value 01, then
you are able to only perform intercompany transactions against company 01. Therefore,
if you enable segment value security rules by balancing segment, you should use two
different value sets for the company and intercompany segments.

Segment Value Security Examples
Security
Security
condition Data role policy
General associated
Cost Center Accountant with the Cost
Equal to Vision US Center value
Accounting set
Example
s a
Security
)h a
Security
condition Data role m
coassociated
policy
General
p e u i de
Account Accountant
@ h nt GAccount
with the
Equal to Vision US r
a tude value set
US Revenue u m
d y -k his S
r e d se t
a r ath e to u
e dd ble l
t h R ra
Create a r a nand
conditions s feassign them to specific data roles to control access to your segment
Bh Fornexample:
values. - tra
no security on both the cost center and account value sets that are associated with
Enable
your chart of accounts.
Assign the General Accountant Vision US data role to the user so the user has access
to cost center Accounting and account US Revenue.
Deny all other users access to all cost center and account value set values.
When access is granted by using segment value security conditions and data access roles for
a ledger:
Use only the allow account values not restricted by the security rule in entering a
journal.
View only balances for accounts during running reports.
When viewing ledger options or other setup pages in an accounting configuration, if the
accounts specified include references to an account with values to which you have not been
granted access, then you can see the account but cannot modify the secured values.

Segment Value Security Operators
Operator Usage
Equal To Secures a specific detail value. You cannot

use this operator to secure a parent value.
Not equal to Secures all detail values except the one that
you specify. You cannot use this operator to
secure a parent value.
Between Secures a range of detail values.

Is descendant of Secures the parent value itself and all of its
s a
descendants, including mid-level parentshand
) a
detail values. om e
c uid
p e
h (that G the
Is last Descendant of Secures the last descendants
r @ n t is,
detail values) of am
u
a value.
parent
t u de
d y -k his S
r e d se t
a r ath e to u
e dd ble l
t h R ra
Use anya r
of n s fe operators in your conditions to secure your segment values.
athe following
Bh n-descendant
Note: ForoIs
tra of and Is last descendant of:

n
Specify an account hierarchy (tree) and a tree version to use this operator.
Notice that the security rule applies across all the tree versions of the specified
hierarchy, as well as all hierarchies associated with the value set.

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

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

c om ide Access
pe t Gu
Granted
h 100
100 100
a r@ den
um Stu
200 300 400 Access
101 200 300 200 300 Denied
- k
201 202 203 301 302
e d
101 dy this
201 202 301 302
201 301 302 401 402
t h r u se
a r a e to
e dd ble l
t h R ra
a r a account
Retrieve n s fehierarchy from security rule: In the Management hierarchy, the 2010
h 2011
Band - a
trversions specify that the parent value 100 is secured by means of the Is
no n
descendant of operator.
Derive effective version based on system date: In the Management hierarchy, the 2011
version is the effective tree version based on the system date.
Apply security condition to get the list of descendants based on the effective tree
version: The parent value itself and all its descendants are secured based on the
effective tree version. The values in the 2011 version are: 100, 200, 300, 101, 201, 202,
301, and 302.
List of values is accessible across all versions of the secured hierarchy, and across all
hierarchies associated with the value set:
- In Management hierarchy: 2010 version, 203 is denied access. All other values
can be accessed.
- In Geographical hierarchy, 400, 401, 402 are denied access. All other values can
be accessed.

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

hierarchies are published to the cube to be effective.
For changes with hierarchical segment value security rules, or

changes in a referenced hierarchy, republish the tree versions
affected by the rule change for rules to be effective in the
cube.
Multiple processes need to be run for hierarchy changes,
including: a
Auditing h a s
m )
Activating o
c uide
p e
h nt G
Row and column flattening @
r
a tude
u m
d y -k his S
r e d se t
a r ath e to u
e dd ble l
t h R ra
Whenhyouaracreate n
news fesegment value security rules or change an existing rule that is based
n - trafilter, you must republish the tree versions affected by the rule change using
on aBhierarchical
no Account Hierarchies page.
the Publish
Republishing is required for the segment value security to become effective in the cube.
Changes to an account hierarchy previously published to the balance cube must be
republished to the cube to reflect the updated hierarchy.

Changes to an Account Hierarchy Referenced in
Segment Value Security Rules
Tree is set from an active to a draft state.
The rules referencing the account hierarchy become
noneffective.
After the hierarchy changes have been completed:
Submit the hierarchy for audit.
The hierarchy is set back to an active status.
The rules referencing the account hierarchy are effective again.
Run the row and column flattening programs to make the list a of
values available and properly secure the account values. a s
m )h
Run the Maintain Value Sets and Maintain Chart o Account
cof ide
Hierarchies. p e
h nt G u
r @
Submit the Process Account Hierarchies
u m a program
t u de to
automatically run these account
y i s S
-khierarchy-related
d t h
red se
processes in one submission.
a r ath e to u
e dd ble l
t h R ra
a r
The Maintain
fe and Maintain Chart of Account Hierarchies processes update the
a ValuensSets
h -tra to regulate ledger and data access security by storing the primary
dataBthat isnrequired
nosegment values assigned to a ledger and the specific child balancing segment
balancing
values assigned to a data access set through parent value assignments.
The Process Account Hierarchies process automatically runs the following child processes:
Tree Audit and Tree Activation
Tree Row Flattening
Tree Column Flattening
Maintain Value Sets
Maintain Account Hierarchies
Publish Hierarchies (You can choose not to run this process.)

Implementation Considerations
Submit the Publish Chart of Accounts Dimension Members and

Hierarchies program to update the balances cube for chart of
accounts value set and hierarchy changes.
s a
)h a
m
co uide
e
@ hp nt G
m ar tude
y - ku is S
e d d th
r e
r a th to us
( b ha nse
R e able
r th sfer
adid
If a
you
h -Detail t r anmake
not changes to the hierarchy assigned to a value set, select Yes in the
BPublishn Values Only field.
n o
If you are using hierarchies for your segment value security rules, publish the hierarchy
from the Manage Hierarchies page.
You don't have to use hierarchies for segment value security, but if you want your
reports to report on hierarchies that conform to hierarchical segment value security, you
need segment value security rules.
In the parameters, you select a value set and whether to publish detail values (child
values) only. If you did not make changes to the hierarchy and simply enabled or
disabled segment value security rules, then you can run this program from the
Scheduled Processes page and select Yes to publish Detail Values Only. Publishing an
entire hierarchy has a performance cost, which is why this option exists. For example, if
you have 20 hierarchies, then publishing all 20 could take a long time.

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

Create a role by giving it a
name.
Use an underscore between
each word in the name.
Define a user-friendly display
name with a hyphen before the
SVS role. a
h a s
For example, define a name of )
o m
ACCOUNTING_COST_CENTER-
p e c uide
SVS_ROLE and a display name @ h nt G
r e
for the Accounting Cost Center-SVS uma tud
role. d y -k his S
d t
t h re use
a r a e to
e dd ble l
t h R ra
a r
For segment s fe roles, the best practice is to give them a common suffix, such as
a valuensecurity
SVS
h -trvalue
B(segment a security), to more readily identify them. You can assign these custom
n
o category of Default.
roles an
role

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.
s
For features not directly related to the balances cube, the ledger
a

h a
) defined
and primary balancing segment values access appliesmas
in the selected data access set. c o d e
e Gu
pcumulative i
For features related to the balances cube, h
@ ent
the effect of

a r
the combined data access sets ignores
k u ud value security
m theStsegment
d d y- thbalancing
rules and gives access to all primary is segment values for
all ledgers. re
th to us
e
r a
( b ha nse
R e able
r ath security
s f er
a
h -tran rules:
Segment value
B
n n
Areospecified 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.
s a
)h a
m
co uide
e
@ hp nt G
m ar tude
y - ku is S
e d d th
r e
r a th to us
( b ha nse
R e able
r ath s f er
a
h -tran
Control the combinations of values you can create when you are setting up account
Bcombinations.
non whether a value of a particular segment can be combined with specific values of
Define
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.
s a
a
)h
m
co uide
e
@ hp nt G
m ar tude
y - ku is S
e d d th
r e
r a th to us
( b ha nse
R e able
Navigatea rto:
ferMaintenance > Manage Cross-Validation Rules or Create Cross
athSetupnsand
Bh Rules
Validation n - train Spreadsheet.
no

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. a
h a s
m )
o
c uide
p e
h nt G
r @
a tude
u m
d y -k his S
r e d se t
a r ath e to u
e dd ble l
t h R ra
a
Navigate rto:
fe Maintenance > Manage Chart of Account Structure Instance >
a Setupnsand
Bh > Manage
Search n - tra Structure Instances button > Create.
no the Dynamic combination creation allowed option, consider the following
When setting
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.
s a
)h a
m
co uide
e
@ hp nt G
m ar tude
y - ku is S
e d d th
r e
r a th to us
( b ha nse
R e able
a
Navigate rto:
ferMaintenance > Manage Cross-Validation Rules.
athSetupnsand
Bh nexample:
Filter - tra If you enter company Equals 102 as a filter, the application validates
nonew account combinations with 102 as the company value.
only
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:
s a
)h a
m
co uide
e
@ hp nt G
m ar tude
y - ku is S
e d d th
r e
r a th to us
( b ha nse
R e able
a
Navigate rto:
ferMaintenance > Manage Cross-Validation Rules.
athSetupnsand
Bh then-Create
Note: In o
tra Cross-Validation Rules spreadsheet, you cannot select some operators.
n following three operators are supported. The application substitutes the operator if:
Only the
A detail value is provided: Equals operator.
Two values are provided separated by a hyphen (-): Between operator.
A parent value is provided: Is Descendant Of operator.

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

Adding a validation filter to the rule.
Testing the rule.
s a
h
) a
o m
p e c uide
@ h nt G
r
a tude
u m
d y -k his S
r e d se t
a r ath e to u
e dd ble l
t h R ra
a r a nsfe
Bh n-tra
no

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 a
a
changing your accounting calendar is difficult after a period
s
m )h
status is set to open or future enterable.
e co uide
Do not change the name of the period after @ hitp nt G
m ar tude
is used. ku S
d d y- this
t h re use
a r a e to
e dd ble l
t h R ra
a r a nsfe
Bh n-tra
no

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.
s a
)h a
m
co uide
e
@ hp nt G
m ar tude
y - ku is S
e d d th
r e
r a th to us
( b ha nse
R e able
athaccountingf er
arnext
Whenhthe
t r a n s period is opened, Oracle Fusion Applications roll balance sheet
B
endingn on- of forward
account balances
balance
to the new period where the beginning balance is taken from the
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 s a
h a
period's ending balance. m) co uide
e
@ hp nt G
m ar tude
y - ku is S
e d d th
r e
r a th to us
( b ha nse
R e able
a
Importantr ath nsfer
Bh n-tmany
Considerohow
ra
years of history to load from your previous system. Calculate the start
n to one period
date back 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. as a
m )h
e co uide
@ hp nt G
m ar tude
y - ku is S
e d d th
r e
r a th to us
( b ha nse
R e able
a r ath nsfer
Bh n-tra
no

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: s a
Week1-11 h
) a

o m
Week2-11
p e c uide
Through Week52-11 @ h nt G

r
a tude
u m
d y -k his S
r e d se t
a r ath e to u
e dd ble l
t h R ra
a r a nsfe
Bh n-tra
no

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.
s a
)h a
January 1 m
co uide
e
@ hp nt G
m ar tu31
December de
u
-k his S
d y
d se t
r e
a r ath e to u
e dd ble l
t h R ra
e
fSection:
ara tFormat
PeriodhName
r a n s Examples
B
Calendarn- Period: The accounting periods are all appended with the year in which they
n o
occur based on the calendar.
Fiscal Period: If the accounting periods in the set of twelve are all assigned the year of
2012, then 2012 is appended to the period name of all 12 periods depending on the
period format selected, regardless of the year the period is actually in. For example, for
a fiscal year starting on June 1, 2015 and ending on May 31, 2016, all the periods would
be assigned 2016, so September 2015 would be assigned the date of September 2016
in the fiscal calendar.
Note: The list of values is filtered based on the selected separator and displays only the
options that match the selected separator.

Calendars with Different Period Frequencies
When you are using the period frequency of Other, you must
manually enter the calendar.
Select the period frequency of Other.

Enter the number of periods for alternative frequencies.
Enter the start and end dates manually.
OTHER
s a
h
) a
o m
p e c uide
@ h nt G
r
a tude
u m
d y -k his S
r e d se t
a r ath e to u
e dd ble l
t h R ra
a r a nsfe
Bh n-tra
no

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 a
Period numberYY. a s
m )h
You can override this format with e co uide
your own customized period names. r@h nt G
p
m a tude
u
-k his S
d y
d se t
r e
a r ath e to u
e dd ble l
t h R ra
a
In Oracle r
Fusion n s fe
a Applications, a calendar can have only one period frequency and period
B
type.
h - t r a
non

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.
s a
a
)h
m
co uide
e
@ hp nt G
m ar tude
y - ku is S
e d d th
r e
r a th to us
( b ha nse
R e able
th sfer
ara trancalendar
For anhaccounting that is associated with a ledger, changing period names or adding
B - the accounting period dimension in the balances cubes.
a year updates
non

Practice 7-10 Overview: Verifying Your Calendar

Searching for your calendar.
Reviewing your calendar.
s a
h
) a
o m
p e c uide
@ h nt G
r
a tude
u m
d y -k his S
r e d se t
a r ath e to u
e dd ble l
t h R ra
a r a nsfe
Bh n-tra
no

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.
s a
)h a
m
co uide
e
@ hp nt G
m ar tude
y - ku is S
e d d th
r e
r a th to us
( b ha nse
R e able
r th sfer
ayour
a
Audits n
h -traaccounting calendars to check for common setup errors. This feature
Bstrengthens controls during implementation and prevents potential processing problems
non to invalid calendar definitions.
related
Performs online checking of errors such as the wrong number of days assigned to a
period or nonadjusting periods that have overlapping days.
Provides online feedback in the form of error messages as the process checks for
validation errors such as date omissions, overlapping nonadjusting periods, and
nonsequential periods.

Manage Currencies: Overview
Oracle Fusion Applications 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
s a
h
) a
o m
p e c uide
@ h nt G
r
a tude
u m
d y -k his S
r e d se t
a r ath e to u
e dd ble l
t h R ra
a r a nsfe
Bh n-tra
no

Currency Concepts
s a
a
)h
m
co uide
e
@ hp nt G
m ar tude
y - ku is S
e d d th
r e
r a th to us
( b ha nse
R e able
a r
The following
fer processes are performed in Oracle Fusion Applications:
aththreenscurrency
Bh n-tra Refers to cross-currency transactions that are converted during the
Conversion:
no
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
s a
)h a
m
co uide
e
@ hp nt G
m ar tude
y - ku is S
e d d th
r e
r a th to us
( b ha nse
R e able
r th sfer
aforeign-denominated
a
Many
h -tsuch r an as Oracle Fusion
transactions are originally entered and then settled in feeder
Bsystems
n Payables and Oracle Fusion Receivables.
n o
Oracle Fusion subledgers share the same Oracle Fusion General Ledger rate table.
Different conversion rate types enable each subledger to convert transactions at
different rates daily.
Corporate procedures can assist in entering and maintaining conversion rates and
avoiding inconsistencies.

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

Currencies task list and navigate to the tasks needed to
successfully implement your currencies.
s a
)h a
m
co uide
e
@ hp nt G
m ar tude
y - ku is S
e d d th
r e
r a th to us
( b ha nse
R e able
r s f er
athpredefined
a
h -tran International Standards Organization (ISO) currencies or create new
Use the
Bones.
non the STAT currency, which is predefined, to record statistical data, such as
Enable
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. s a
a
)h
Record balances. m
co uide
e
@ hp nt G
m ar tude
y - ku is S
e d d th
r e
r a th to us
( b ha nse
R e able
th sfer
ara troranediting
Whenhcreating currencies, consider these points:
B n- Codes: After a currency is enabled, the currency code cannot be changed,
Currency
n o
even if you later disable that currency.
Date Ranges: Currency codes can be selected only for the dates within the date range
defined. If you do not enter a start date, then the currency is valid immediately. If you do
not enter an end date, then the currency is valid indefinitely.
Symbols: Some applications use currency symbols. Others, such as Oracle Fusion
General Ledger, do not, even if the currency is defined with a symbol.
Euro Currency Derivation: Derivation Type, Derivation Factor, and Derivation Effective
Date fields are used to define the relationship between the official currency (euro) of the
European Monetary Union (EMU) and the national currencies of new EMU member
states during their transition period.
Note: If you need to use a different currency code than EUR for the euro currency, you can
disable the predefined EUR currency code and create the new one.
By default, all ISO currencies are enabled. When you open the Currency list of values across
applications, you see every defined currency which can impact transaction entry. If 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.
s a
h
) a
o m
p e c uide
@ h nt G
r
a tude
u m
d y -k his S
r e d se t
a r ath e to u
e dd ble l
t h R ra
a r a nsfe
Bh n-tra
no

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

cross-currency amounts to ledger currency equivalents.
s a
h
) a
o m
p e c uide
@ h nt G
r
a tude
u m
d y -k his S
r e d se t
a r ath e to u
e dd ble l
t h R ra
a
Navigate rto:
fe Maintenance > Manage Daily Rates > Rate Types tab.
a Setupnsand
Bh n-trGeneral
Oracle Fusion
a
Ledger predefined conversion rate types are:

no
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 s a
h
) a
o m
c uide
Entered Enteredpe
@ h nt G
r
a tude
u m
d y -k his S
r e d se t
a r ath e to u
e dd ble l
t h R ra
a r a nsfe
Bh n-tra
no

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.
s a
Contra Currency: A currency other than your pivot currency a
)h
co m
that is enabled, effective, and not a statistical currency. e
p e uid
h G
a r@ dent
- k um Stu
e d dy this
t h r u se
a r a e to
e dd ble l
t h R ra
a r a creation
The automatic n s feof rates is particularly beneficial for intercompany transactions with
Bh currencies
multiple n - tra because it ensures consistency among the rates, thereby minimizing the
effect of o
nconversion 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. s a

)h a
EUR and CAD are the contra currencies. m
e co uide
@ hp nt G
From Currency To Currency ar tudeInverse Rate
Rate
m
EUR CAD y -
1.3080
ku is S .7846
e d d th
r e
r a th to us
( b ha nse
R e able
r th sfer
apivot
USD is
h a
the
t r a n
currency used by the application to create a daily rate between EUR and
B n-
CAD automatically.
n o
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.
s a
h
) a
o m
p e c uide
@ h nt G
r
a tude
u m
d y -k his S
r e d se t
a r ath e to u
e dd ble l
t h R ra
a r a nsfe
Bh n-tra
no

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.
s a
)h a
m
co uide
e
@ hp nt G
m ar tude
y - ku is S
e d d th
r e
r a th to us
( b ha nse
R e able
r athRatess f er
Sharing a
h -tran
Daily
B n rates are shared across all ledgers within an application instance and are
Daily conversion
nowhen
available you are entering cross-currency transactions in your Oracle Fusion
subledgers.
Subledger applications share the same daily rates with the general ledger, but different rate
types enable each subledger to convert transactions at different rates.

Entering Daily Rates
Enter inverse rates independently or have the application

calculate the inverse rate from the entered rate.
Use the provided spreadsheet template to load daily rates or

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. a
h a s
m )
o
c uide
p e
h nt G
r @
a tude
u m
d y -k his S
r e d se t
a r ath e to u
e dd ble l
t h R ra
a
Currency r a Manager
Rates n s fe
Bh n-Setup
Navigateoto:
tra and Maintenance > Manage Daily Rates > Daily Rates tab.
n
Warning: Always use the interface table to load your daily rates either through the
spreadsheet template or by using other file loading tools. Do not load rates directly into the
GL_DAILY_RATES table. This can corrupt your daily rates data.
Note: Use conversion rate service companies to provide you with rates that can be loaded
into the GL_DAILY_RATES_INTERFACE table automatically.

Practice 7-13 and 7-14 Overview: Using Currency
Rates
Practice 7-13: Entering Daily Rates.
Opening the spreadsheet.

Entering your rates.
Submitting the spreadsheet.
Verifying your rates were loaded successfully.
Practice 7-14: Entering a Currency Conversion Journal.
s a
h
) a
o m
p e c uide
@ h nt G
r
a tude
u m
d y -k his S
r e d se t
a r ath e to u
e dd ble l
t h R ra
a r a nsfe
Bh n-tra
no

Summary

Manage value sets.
Define chart of accounts components.

Manage and publish account hierarchies.
Maintain segment values.
Manage cross-validation rules.
s a
Define calendars and currencies. h
) a
o m
p e c uide
@ h nt G
r
a tude
u m
d y -k his S
r e d se t
a r ath e to u
e dd ble l
t h R ra
a r a nsfe
Bh n-tra
no

8
Configuring Ledgers
s a
h
) a
o m
p e c uide
@ h nt G
r
a tude
u m
d y -k his S
r e d se t
a r ath e to u
e dd ble l
t h R ra
a r a nsfe
Bh n-tra
no
Objectives

Define ledgers and ledger options.
Assign balancing segments.

Manage reporting currencies.
Map chart of accounts.
Explore the GL Balances cube.
Create ledger sets.
s a
Define GL security. h
) a
o m
p e c uide
@ h nt G
r
a tude
u m
d y -k his S
r e d se t
a r ath e to u
e dd ble l
t h R ra
a r a nsfe
Bh n-tra
no

Define Ledgers
s a
a
)h
m
co uide
e
@ hp nt G
m ar tude
y - ku is S
e d d th
r e
r a th to us
( b ha nse
R e able
Use youra r ath nsfer project or Setup and Maintenance work area to define ledgers and
implementation
Bhtasks.
related n - tra
no

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. s a
a
)h
Serves as a framework for how financial records are m
maintained for an organization. e co uide
hp G
a r@ dent
- k um Stu
e d dy this
t h r u se
a r a e to
e dd ble l
t h R ra
a r a nsfe
Bh n-tra
no

Ledgers and Accounting Configurations
s a
a
)h
m
co uide
e
@ hp nt G
m ar tude
y - ku is S
e d d th
r e
r a th to us
( b ha nse
R e able
r th sfer
ashows
a
h -tranthe enterprise structure components and their relationships to each other.
This figure
B
A ledger o n
determines the currency, chart of accounts, accounting calendar, ledger processing
options,nand 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
s a
a
)h
m
co uide
e
@ hp nt G
m ar tude
y - ku is S
e d d th
r e
r a th to us
( b ha nse
R e able
th sfer
araoftrledgers
Threehtypes a n are defined in Oracle Fusion General Ledger using the four
B
components -that are already defined: chart of accounts, calendar, currency, and accounting
non
method.
Primary Ledger: Main record keeping ledger and a required component in your
configuration. Every accounting configuration is uniquely identified by its primary ledger.
The primary ledger is closely associated with the subledger transactions and provides
context and accounting for them.
Secondary Ledger: Optional ledger linked to a primary ledger for the purpose of
tracking alternative accounting. A secondary ledger can differ from its primary ledger in
its chart of accounts, accounting calendar, currency, accounting method, or processing
options.
Reporting Currency: Optional, additional currency representation of a primary or
secondary ledger. A reporting currency can differ from its source ledger in its currency
and some processing options, but shares the same chart of accounts, accounting
calendar, and accounting method with its related ledger.

Ledgers and Subledger Accounting
Oracle Fusion Applications reflect the traditional segregation

between the general ledger and associated subledgers.
Detailed transactional information is captured in the

subledgers.
Transactions are periodically sent to Subledger Accounting for
creation of journal entries.
Transactions are imported and posted in summary or detail to
the ledger using Subledger Accounting. a
a s
Subledger Accounting is an application that is used to create
m ) h and
capture transactions. It contains accounting rules ethat
d e to
coareuiused
create detailed journal entries. @ hp nt G
r a tude
u m
d y -k his S
r e d se t
a r ath e to u
e dd ble l
t h R ra
a r
Companies
aaccount
n s fethemselves in primary ledgers and, if necessary, secondary ledgers
for
andB
h -tcurrencies.
reporting ra
n
no transactions from your subledgers are posted to your primary ledgers, and
Your
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
s a
)h a
m
co uide
e
@ hp nt G
m ar tude
y - ku is S
e d d th
r e
r a th to us
( b ha nse
R e able
r h sfer
atLedger:
a
h -tran
The Primary
B
on as the main record keeping ledger.
Performs
n
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.
s a
h
) a
o m
p e c uide
@ h nt G
r
a tude
u m
d y -k his S
r e d se t
a r ath e to u
e dd ble l
t h R ra
a r a nsfe
Bh n-tra
no

Specify Ledger Options
s a
)h a
m
co uide
e
@ hp nt G
m ar tude
y - ku is S
e d d th
r e
r a th to us
( b ha nse
R e able
r ath your s f er
h a
After configuring
t r a n primary ledger, the next step is to specify your ledger options. These
B
options: n-
no many of the accounting processes and defaults that are used in both the general
Control
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
s a
)h a
m
co uide
e
@ hp nt G
m ar tude
y - ku is S
e d d th
r e
r a th to us
( b ha nse
R e able
r s f er
ath Closing:
a
h -trbyanmoving Open
Year-End the first period of a new year to update the Retained Earnings
Baccounts the net balance from your revenue and expense account to the
non Earnings accounts by balancing segment.
Retained
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
a
Average Balance as )h
m
co uide
e
@ hp nt G
m ar tude
y - ku is S
e d d th
r e
r a th to us
( b ha nse
R e able
a r ath nsfer
Bh n-tra
no

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 s a
a
)toh
more often than assigning balancing segment values m
ledgers. e co uide
@ hp nt G
If you are implementing intercompany a r
features,d ethen assigning
u m t u
balancing segment values to legal s Sis mandatory.
y-k entities d t hi
r e d e
r a t h t o us
( b ha nse
R e able
a r
For example,
fer is recording transactions for three legal entities and another is
athif onensledger
Bh transactions
recording n - tra for two legal entities, assigning balancing segment values to your legal
o ledgers simplifies the list of values on journal entries and transactions.
entitiesnand

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.
s a
a
)h
m
co uide
e
@ hp nt G
m ar tude
y - ku is S
e d d th
r e
r a th to us
( b ha nse
R e able
a
Navigate rto:
ferMaintenance > Define Ledgers > Define Accounting Configurations >
athSetupnsand
BhBalancing
Assign n - tra Segment Values to Legal Entities
no

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

primary and secondary ledgers to represent nonlegal entity-
related transactions such as adjustments or top-side entries.

Assign each balancing segment value to a legal entity only
once.
s a
a
)h
m
co uide
e
@ hp nt G
m ar tude
y - ku is S
e d d th
r e
r a th to us
( b ha nse
R e able
a
Navigate rto:
ferMaintenance > Define Accounting Configurations > Assign Balancing
athSetupnsand
Bh Values
Segment n - trato Ledgers
noYour company hires a law, accounting, or consulting firm to do some legal or tax
Example:
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.
s a
h
) a
o m
p e c uide
@ h nt G
r
a tude
u m
d y -k his S
r e d se t
a r ath e to u
e dd ble l
t h R ra
Use thea r
Scheduled
fe page to run the report.
a nsProcess
Bh n-trto:
Navigate
a
Tools > Scheduled Processes
n o
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.
s a
h
) a
o m
p e c uide
@ h nt G
r
a tude
u m
d y -k his S
r e d se t
a r ath e to u
e dd ble l
t h R ra
a r a nsfe
Bh n-tra
no

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 majorityhof a sitsa
transactions are denominated. For example, create, m )
record,
o
csave uide
and close a transaction in the same currency h p e
to G
processing and reconciliation time. ar@ dent
Conform to local requirements, - k um
for S tu paying transaction
example,
d y this
dcurrency.
taxes is easier using a local
r e e
r a th to us
( b ha nse
R e able
th sfer
Note:h aracountries
Many
t r a n require that one of your ledgers be kept in their national currency.
B n- Currencies, you can produce financial statements using the national currency
With Reporting
n o
or alternate currencies.

Manage Reporting Currencies
s a
h
) a
o m
p e c uide
@ h nt G
r
a tude
u m
d y -k his S
r e d se t
a r ath e to u
e dd ble l
t h R ra
r a ntosfUse e
a
Business Reasons
h -tra Reporting Currencies
B
non
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
s a
)h a
m
co uide
e
@ hp nt G
m ar tude
y - ku is S
e d d th
r e
r a th to us
( b ha nse
R e able
r th sfer
acurrency
h a
A reporting
t r a n is linked to a primary or secondary ledger and can be maintained at one
B n-conversion levels.
of three data
n o
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.
s a
h
) a
o m
p e c uide
@ h nt G
r
a tude
u m
d y -k his S
r e d se t
a r ath e to u
y (bh icens
e dd ble l
t h R ra
a r a nsfe
Bh n-tra
no

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.
s a
h
) a
o m
p e c uide
@ h nt G
r
a tude
u m
d y -k his S
r e d se t
a r ath e to u
e dd ble l
t h R ra
a r a nsfe
Bh n-tra
no

Define Secondary Ledgers
s a
)h a
m
co uide
e
@ hp nt G
m ar tude
y - ku is S
e d d th
r e
r a th to us
( b ha nse
R e able
r h sfer
atledger
h a
A secondary
t r a n is an additional ledger linked to a primary ledger for the purpose of
B n-
tracking alternative accounting.
n o
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 eacha
accounting calendar. h a s
m )
Ledger currencies: Currency conversion rules are o
c uide to
required
e
hp nt Gjournals,
instruct the system how to convert the transactions,
@
ar tutodthe
e secondary
or balances from the source representation
m
k u S
ledger. dy- his
e d se t
r
a r ath e to u
e dd ble l
t h R ra
Note:h Journal n fe rules, based on the journal source and category, are required to
ara tconversion
s
provide n - ra on how to propagate journals and types of journals from the source ledger
B instructions
no
to the secondary ledger.

Secondary Ledgers: Conversion Levels
s a
h
) a
o m
p e c uide
@ h nt G
r
a tude
u m
d y -k his S
r e d se t
a r ath e to u
e dd ble l
t h R ra
a r
Secondary
fe one of the four conversion levels:
aLedgersnsuse
Bh n-trLevel:
Balance
a
Transfer Balances to Secondary Ledger process transfers only
no to the secondary ledger.
balances
Journal Level: General Ledger Posting process transfers the journal entries to the
secondary ledger.
Subledger Level: Oracle Fusion Subledger Accounting creates the subledger journals
to both the primary and secondary ledger. The Posting process transfers the remaining
journal entries to the secondary ledger.
Adjustment Only: Adjustment only secondary ledger is an incomplete accounting
representation that holds manual or automatic adjustment journal entries from General
Ledger or Oracle Fusion Subledger Accounting. This conversion level requires that the
secondary ledgers share the same chart of accounts, accounting calendar, and currency
with its primary ledger. A complete accounting representation is achieved by creating a
report that includes both the primary and secondary ledger data together.
Note: The journal and subledger data conversion levels require more processing resources
because they duplicate most general ledger and subledger journal entries, as well as general
ledger balances.

Secondary Ledger Example
You maintain a secondary ledger for your International

Financial Reporting Standards (IFRS) accounting
requirements.
Your primary ledger uses US Generally Accepted Accounting
Principles (GAAP).
You decided to select the subledger level for your IFRS
secondary ledger.
s a
h
) a
o m
p e c uide
ANSWER h nt G
r @
a tude
u m
d y -k his S
r e d se t
a r ath e to u
e dd ble l
t h R ra
a r a nsfe
Bh n-tra
no

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 a
the resources that are required by full subledger-level) ha
s
secondary ledger. c om ide
A subledger-level secondary ledger would h pe t more
provide G u
a r@ den
functionality than you need in this example.
um tu
d y -k his S
r e d se t
a r ath e to u
e dd ble l
t h R ra
a r a nsfe
Bh n-tra
no

Secondary Ledgers Mapping
s a
h
) a
o m
p e c uide
@ h nt G
r
a tude
u m
d y -k his S
r e d se t
a r ath e to u
e dd ble l
t h R ra
a
Creating r
secondary
fe follows the same steps as primary ledgers.
a nsledgers
Bh n-trtoathe Define Secondary Ledgers page from the Define Accounting
Navigate
no
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 a
ledgers and cross-ledger transfers to copy balances from a s
one
m )h
ledger to another ledger. co de
pe t Gui
h
a r@ den
- k um Stu
e d dy this
t h r u se
a r a e to
e dd ble l
t h R ra
a r a nsfe
Bh n-tra
no

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 a
value and all of its child segment values are mapped )tohaa
s
given detail target segment value. This enables you
c omto ide
process groups of source segment values in h e single
pone G u rollup
r@ den t
rule. m a tu
y - ku is S
e d d th
r e
r a th to us
( b ha nse
R e able
r th sfer
aparent
h a
Tip: Define
t r a nsource values in rollup rules with date-effective versions of a hierarchy.
B
Then use then-accounting date from the journal entries to reference the chart of accounts
mappingnothat 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. a
h a s
Parent values for each segment. )
o m
p e c uide
@ h nt G
r
a tude
u m
d y -k his S
r e d se t
a r ath e to u
e dd ble l
t h R ra
a r a nsfe
Bh n-tra
no

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. a
h a s
m )
o
c uide
p e
h nt G
r @
a tude
u m
d y -k his S
r e d se t
a r ath e to u
e dd ble l
t h R ra
a r
The Review n s fe Accounting Configuration:
aand Submit
Bh n-tthe
Updates
ra underlying table and permanently saves the settings after the accounting
no
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.
s a
h
) a
o m
p e c uide
@ h nt G
r
a tude
u m
d y -k his S
r e d se t
a r ath e to u
e dd ble l
t h R ra
a r a nsfe
Bh n-tra
no

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. a
Are automatically updated by the following general ledger a s
m )h
processes: posting, open period, and translation.
e co uide
@ hpcalled
Consist of a set of defining business entities n t G
r
a tude
dimensions. um
d y -k his S
r e d se t
a r ath e to u
e dd ble l
t h R ra
Note:h
Average n fe are tracked in a separate balances cube.
ara trbalances
s
B n- a
no

Balance Cubes Naming
s a
)h a
m
co uide
e
@ hp nt G
m ar tude
y - ku is S
e d d th
r e
r a th to us
( b ha nse
R e able
r athcubes
s f er
a
h -tran named after the chart of accounts they contain.
The balances are
B
Exampleon
n
The chart of accounts Vision Corporation has a related balances cube, also entitled
Vision Corporation.
If a chart of accounts is used by multiple ledgers with different calendars, the balances
cube names are distinguished by a number appended to their names.
If the Vision Corporation chart of accounts is used by two different ledgers, each of
which uses a different accounting calendar, two balances cubes are created with the
names Vision Corporation Chart of Accounts 1 and Vision Corporation Chart of
Accounts 2.

Balance Cube Dimensions
Dimension Description
Accounting Period Based upon the calendar of the ledger or ledger set.
Report on years, quarters, or periods.
Ledger or Ledger Set Used to select a ledger for reporting.

Charts of Accounts Segments from the charts of accounts, organized by
Segments hierarchy.
Scenario Indicates whether the balances are actual, allocated,
or actual including allocated, budgeted, or forecast.
Balance Amount Indicates whether the value is a debit or credit, and
whether it is for the beginning balance, period s a
activity, or ending balance. ) ha m
Amount Type c
Indicates whether the amounts represento Base,
i d e
hpe t Gu
Period, Quarter, or Year to Date.
r@ n
Currency Used to select the desired
k u udefor the balances.
ma currency
S t
Currency Type Used to selectdthe - his type of the balances.
y currency
e d
Availableroptions are e t
t h u s Entered, Converted, or Total.
a r a e t o
h
(b icen s
d y
d ble l
Copyright 2016, Oracle and/or its affiliates. All rights reserved.
e
R ra
r t h fe of a set of defining business entities called dimensions. This table
acube consists
s
a
A balances n
Bhthe ndimensions
details - tra that are available for creating financial reports using multidimensional
cubes. no
The General Ledger Posting process updates your balances and stores these balances in a
balances cube for efficient multidimensional analysis. This provides for efficient reporting.
Note: Dimensions are seeded and new ones cannot be added.

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

chart of accounts and calendar combination to increase the
efficiency of your period close, security administration, and

reporting.
Allows you to treat multiple ledgers as one.
s a
)h a
m
co uide
e
@ hp nt G
m ar tude
y - ku is S
e d d th
r e
r a th to us
( b ha nse
R e able
athyou ncan r
feopen
a r
For example,
h a s and close periods for multiple ledgers in a ledger set in a single
B t r
- submitting the Open and Close Period process.
submissionnby
no

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

s a
h
) a
o m
p e c uide
@ h nt G
r
a tude
u m
d y -k his S
r e d se t
a r ath e to u
e dd ble l
t h R ra
a r a nsfe
Bh n-tra
no

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.
s a
h
) a
o m
p e c uide
@ h nt G
r
a tude
u m
d y -k his S
r e d se t
a r ath e to u
e dd ble l
t h R ra
a r a nsfe
Bh n-tra
no

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

by using primary balancing segment values.
If you have primary balancing segment values assigned to a legal

entity, then you can use this feature to secure access to specific
legal entities.
Secures parent or detail primary balancing segment values.
Secures the specified parent value as well as all its
descendents, including mid-level parents and detail values. a
h a s
Requires all ledgers assigned to the data access set to ) share
o m
ec
the same chart of accounts and accounting calendar.
p t Gu ide
h
a r@ den
- k um Stu
e d dy this
t h r u se
a r a e to
e dd ble l
t h R ra
a r a nsfe
Bh n-tra
no

Data Access Set Security
s a
a
)h
m
co uide
e
@ hp nt G
m ar tude
y - ku is S
e d d th
r e
r a th to us
( b ha nse
R e able
a
FullrLedger s fer Access to the entire ledger or ledger sets. For example, this could
ath nAccess:
h read-only
Bbe - tra access to the entire ledger or both read and write access.
n
no Balancing Segment Value Access: Access to one or more primary balancing
Primary
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
s a
)h a
m
co uide
e
@ hp nt G
m ar tude
y - ku is S
e d d th
r e
r a th to us
( b ha nse
R e able
r athshows s f er
h a
This example
t r a n data access set that secures access by using primary balancing
a
B n- that correspond to legal entities.
segment values
n
Scenario
o
The Vision US Primary Ledger is assigned to this data access set.
Read-only access has been assigned to balancing segment value 131, which
represents the Vision US Heath LE 3.
Read and write access has been assigned to the other two primary balancing segment
values for legal entities, Vision US LE 1 and 2.
In summary, you can:
Create a journal batch in ledgers or with primary balancing segment values if you have
write access.
Modify a journal batch if you have write access to all ledgers or primary balancing
segment values that are used in the batch.
View a journal batch if you have read-only or write access to the ledger or primary
balancing segment values.

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

Practice 8-7: Reviewing data access set security.
Practice 8-8: Creating data access set security.
s a
h
) a
o m
p e c uide
@ h nt G
r
a tude
u m
d y -k his S
r e d se t
a r ath e to u
e dd ble l
t h R ra
a r a nsfe
Bh n-tra
no
Oracle Financials Cloud: Enterprise Structures with General Ledger Implementation 8 - <#>
Summary

Define ledgers and ledger options.
Assign balancing segments.

Manage reporting currencies.
Map chart of accounts.
Explore the GL Balances cube.
Create ledger sets.
s a
Define GL security. h
) a
o m
p e c uide
@ h nt G
r
a tude
u m
d y -k his S
r e d se t
a r ath e to u
e dd ble l
t h R ra
a r a nsfe
Bh n-tra
no

9
Configuring Journal Approval

s a
h
) a
o m
p e c uide
@ h nt G
r
a tude
u m
d y -k his S
r e d se t
a r ath e to u
e dd ble l
t h R ra
a r a nsfe
Bh n-tra
no
Objectives

Describe the key concepts of approval management.
Perform basic approval configurations.

s a
h
) a
o m
p e c uide
@ h nt G
r
a tude
u m
d y -k his S
r e d se t
a r ath e to u
e dd ble l
t h R ra
a r a nsfe
Bh n-tra
no

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.
s a
a
)h
m
co uide
e
@ hp nt G
m ar tude
y - ku is S
e d d th
r e
r a th to us
( b ha nse
R e able
r athOracles f er
h a
For workflows,
t r a n Fusion Applications use the approval management extensions of the
B - services from Oracle SOA Suite, as well as the Oracle BPM Worklist
human workflow
non
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.
Implementors to perform approval management setup, to define who should act on
which types of transactions under what conditions.

Approval Management: Overview
Approval management:
Controls 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.
s a
)h a
m
co uide
e
@ hp nt G
m ar tude
y - ku is S
e d d th
r e
r a th to us
( b ha nse
R e able
To sethup s fer
ath nmanagement,
arapproval use the following setup tasks from the Setup and
B t r a
Maintenance
n o n-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, you need the BPM Worklist Administration Duty role, which is
predefined for the Application Implementation Consultant job role.

Key Concepts: Stages
Stages organize approval flows in logical categories within a

task. For example, within a contract approval task, there can
be one stage for contract header approval and another for line
level approval.
Each task has at least one stage.
Stages and their flow (serial or parallel, and specific order) are
predefined.
s a
h
) a
o m
p e c uide
@ h nt G
r
a tude
u m
d y -k his S
r e d se t
a r ath e to u
e dd ble l
t h R ra
a r a nsfe
Bh n-tra
no

Key Concepts: Participants
A participant represents a specific set of policies and routing

within a stage.
For example, for a stage for contract approval, there can be

one participant for legal approval and another for management
approval.
Participants are predefined, and can be enabled or disabled.
Participant types:
FYI
s a
Parallel a
)h
Serial m
co uide
e
Single
@ hp nt G
Each participant has at least one predefined m ar turule
de set.
u
-k his S
d y
d se t
r e
a r ath e to u
e dd ble l
t h R ra
sfedisabled by default, but you can enable them to use them for the task.
ara tranare
Somehparticipants
YouBcannotnadd
- or edit participants, for example change the participant type.
n o
Participant 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 participant with these characteristics:
Flow: Serial or parallel, and specific order, for participants with

multiple rule sets.
Business object level: Header or line.
Voting regime: Consensus approval, majority approval, and so
on, for rule sets that route to a group of users.
In each rule, you define a condition and specify the routing usings a
a list builder. )h a
c om ide
h pe t Gu
a r@ den
- k um Stu
e d dy this
t h r u se
a r a e to
e dd ble l
t h R ra
a r a nsfe
Bh n-tra
no

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 s a
a
)h
consideration. m
Position: Starts with a given approver's position e co continues
and u ide
p
h nt G
r @
up the chain until a certain position is found.
a de
um Stu
- k
e d dy this
t h r u se
a r a e to
e dd ble l
t h R ra
a r
The following n s fe are based on structures in HCM, which must be set up
a list builders
Bh n-tra
appropriately.
no
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 participant 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 Joes supervisory chain at job level 4.
s a
h
) a
o m
p e c uide
@ h nt G
r
a tude
u m
d y -k his S
r e d se t
a r ath e to u
y (bh icens
e dd ble l
t h R ra
a r a nsfe
Bh n-tra
no

Manage Task Configurations
Reset Save
Edit task
Commit
task
s a
a
)h
m
co uide
e
@ hp nt G
Tabs for each m ar tude
task dy-
ku is S
r e d e th
r a th to us
( b ha nse
R e able
th sfer
araMaintenance
Setuphand
t r a n > Enter Manage Task Configurations in search field > Search > Click
B - in Name column.
appropriatentask
n o
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
s a
a
)h
m
co uide
e
@ hp nt G
m ar tude
y - ku is S
e d d th
r e
r a th to us
( b ha nse
R e able
th sfer
araMaintenance
Setuphand
B - in Name column > Select task in Tasks to be configured pane
appropriatentask
n o
The tabs for each task are:
General: View general information about the task as a whole. Usually you dont need to
use this tab.
Assignees: View and edit approval policies and routing.
Data: View information about data thats available for use in the rules in the task.
Usually you dont 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
Stage
Participant
s a
a
)h
m
co uide
e
@ hp nt G
m ar tude
y - ku is S
e d d th
r e
r a th to us
( b ha nse
R e able
th sfer
araMaintenance
Setuphand
B - in Name column > Select task in Tasks to be configured pane > Edit task >
appropriatentask
no tab > Switch to Vertical Layout
Assignees
Use the Assignees tab to define policies and routing.
The assignees tree shows the stages and participants within each stage.
The main boxes are stages, and the boxes within are participants.
Click the name of the stage or participant to select it.
Make sure that all unused stages and participants are disabled:
Select the stage or participant.
In the pane below the tree, click Advanced.
Select the Ignore Stage or Ignore Participant check box.

Rule Sets
Click the Go to rule icon in the

assignees tree to open rule
sets for a given participant.
Rule Set
s a
Expand Rule
a
)h
m
co uide
e
@ hp nt G
m ar tude
y - ku is S
e d d th
r e
r a th to us
( b ha nse
R e able
th sfer
araMaintenance
Setuphand
appropriatentask
no tab > Switch to Vertical Layout > Go to rule
Assignees
For example, you select the ExpenseReportApprovers participant, within the
ExpenseReportApprovalStage stage, to open the ExpenseReportRuleSet rule set that is
predefined for that participant. 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
s a
)h a
Show m
co uide
Advanced e
Settings @ hp nt G
m ar tude
y - ku is S
Use Priority field in advanced e d dsettingsthto set priority for rules.
r e
r a th to us
( b ha nse
R e able
th sfer
araMaintenance
Setuphand
appropriatentask
no tab > Switch to Vertical Layout > Go to rule > Expand > Show Advanced Settings
Assignees
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 s a
a
)h
m
co uide
IF component e
@ hp nt G
m ar tude
y - ku is S
e d d th
r e
r a th to us
THEN component
( b ha nse
R e able
th sfer
araMaintenance
Setuphand
appropriatentask
no tab > Switch to Vertical Layout > Go to rule > Expand rule
Assignees
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.
Rule
s a
a
)h
Subject Operator Criterion m
co uide
e
@ hp nt G
m ar tude
y - ku is S
Left Value e d d th Right Value Add
r s e
icon ath t o u icon condition
a r e
e dd ble l
t h R ra
araMaintenance
Setuphand n s fe > Enter Manage Task Configurations in search field > Search > Click
B ntask
appropriate - train Name column > Select task in Tasks to be configured pane > Edit task >
Assignees
To select values for the subject or criterion, click the Left Value or Right value icon to
open the Condition Browser dialog box. Whats 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 expense report total 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.
s a
a
)h
m
co uide
e
@ hp nt G
m ar tude
y - ku is S
e d d th
r e
r a th to us
( b ha nse
R e able
th sfer
araMaintenance
Setuphand
appropriatentask
Assignees
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 expense report, and that managers
manager.
- Starting Participant: The first approver is defined as the manager of the person
who submitted the expense report.
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 assignee must take action to
approve or reject the expense report.

Automatic action settings allow you to set an automatic action on tasks, to automatically
approve or reject. In this example:
- Auto Action Enabled: The expense report will not be automatically approved or
rejected, but requires explicit action from assignees.
- Auto Action: Since automatic action is not enabled, no automatic action is
specified.
The Rule Name is a meaningful name for the rule, which is displayed to assignees, in
this case, the expense report approvers.
s a
h
) a
o m
p e c uide
@ h nt G
r
a tude
u m
d y -k his S
r e d se t
a r ath e to u
y (bh icens
e dd ble l
t h R ra
a r a nsfe
Bh n-tra
no

Rule Example
s a
a
)h
m
co uide
e
@ hp nt G
m ar tude
y - ku is S
e d d th
r e
r a th to us
( b ha nse
R e able
th sfer
araMaintenance
Setuphand
appropriatentask
no tab > Switch to Vertical Layout > Go to rule > Expand rule.
Assignees
For the same rule set, you have another rule with these conditions in the IF component:
The expense report 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 CFO of the company, but in essence this parameter isnt
used because the task is automatically approved. For automatic approvals, the approval
history for the task will show the starting participant as the approver.
Top Participant: The last possible approver is the CFO of the company, Casey Brown.
If the CFO is the manager of the person who submitted the expense report, then only
one level of approval is needed because the CFO is the top participant.

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 expense report is automatically approved
if the conditions are met. The other possible action is null.
s a
h
) a
o m
p e c uide
@ h nt G
r
a tude
u m
d y -k his S
r e d se t
a r ath e to u
y (bh icens
e dd ble l
t h R ra
a r a nsfe
Bh n-tra
no

Deadlines
Use the Deadlines tab to configure when tasks expire, escalate,

or renew.
s a
a
)h
m
co uide
e
@ hp nt G
m ar tude
y - ku is S
e d d th
r e
r a th to us
( b ha nse
R e able
th sfer
araMaintenance
Setuphand
appropriatentask
notab
Deadlines
You can define the policy so that if the assignee doesnt 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 doesnt act on the task within two weeks, then:
Escalate: The task is reassigned to the assignees 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.
s a
h
) a
o m
p e c uide
@ h nt G
r
a tude
u m
d y -k his S
r e d se t
a r ath e to u
y (bh icens
e dd ble l
t h R ra
a r a nsfe
Bh n-tra
no

Notifications
Use the Notifications tab to send notifications based on task

status, for example, notify approvers when the task is assigned to
them.
s a
a
)h
m
co uide
e
@ hp nt G
m ar tude
y - ku is S
e d d th
r e
r a th to us
( b ha nse
R e able
th sfer
araMaintenance
Setuphand
appropriatentask
no tab
Notifications
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 its 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.
s a
h
) a
o m
p e c uide
@ h nt G
r
a tude
u m
d y -k his S
r e d se t
a r ath e to u
y (bh icens
e dd ble l
t h R ra
a r a nsfe
Bh n-tra
no

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.
s a
a
)h
m
co uide
e
@ hp nt G
m ar tude
y - ku is S
e d d th
r e
r a th to us
( b ha nse
R e able
th sfer
araMaintenance
Setuphand
appropriatentask
no tab
Configuration
For example, if you have a task requiring approval on individual expense lines, and you
change the Task Aggregation setting to None, then assignees would get 15 notifications for
approval if an expense report has 15 lines 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 a
choice list. a s
m )h
3. Deselect check e co uide
boxes as needed. @ hp nt G
m ar tude
y - ku is S
e d d th
r e
r a th to us
( b ha nse
R e able
th sfer
araMaintenance
Setuphand
B
o - in Name column > Select task in Tasks to be configured pane > Edit task >
appropriatentask
Accessntab
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: 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 Reorder
Member
Edit Member
s a
a
)h
m
co uide
e
@ hp nt G
m ar tude
y - ku is S
e d d th
r e
r a th to us
( b ha nse
R e able
th sfer
araMaintenance
Setuphand
t r a n > Enter Manage Approval Groups in search field > Search > Click
B - in Name column
appropriatentask
n o
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.
In this example, the routing is serial and goes from Bob Jones to Jennifer Bailey.
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.

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. a
a s
Can be static or dynamic. )h
c om ide
h pe t Gu
a r@ den
- k um Stu
e d dy this
t h r u se
a r a e to
e dd ble l
t h R ra
a
Approval r a Examples
Group n s fe
Bh n-traaspecial, ongoing project that involves a wide range of employees. You can
Youohave
n an approval group of the managers involved, who must approve expenses
create
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 Journal Approval Rules
Journal approval in Oracle Fusion applications uses:

Oracle Fusion 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.
s a
a
)h
m
co uide
e
@ hp nt G
m ar tude
y - ku is S
e d d th
r e
r a th to us
( b ha nse
R e able
r h sfer
atApproval
h a
The Journal
t r a n Process obtains the necessary management approvals for manual
B n-
journal batches.
n o
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
s a
a
)h
m
co uide
e
@ hp nt G
m ar tude
y - ku is S
e d d th
r e
r a th to us
( b ha nse
R e able
r h sfer
atapproval
a
Enable
h -tpage.r an Navigate
for the ledger in the Journal Processing section on the Specify Ledger
BOptions
n to the Specify Ledger Options page through the Define Ledgers
nolist
task in your implementation project.
Enable approval for a specific source on the Manage Journal Sources page. Navigate to
the Manage Journal Sources page through the Define General Ledger Options task list.
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:
s a
Journal approval based on the highest journal line amount a
)h per
ledger per batch. m
co uide
e
Journal approval based on the highest journal
@ hp amount
n t G per
r
ledger per batch. ma tude
ku is S
d y -
r e d e th
r a th to us
( b ha nse
R e able
a r ath nsfer
Bh n-tra
no

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 s a
h
) a
Close o m
p e c uide
Post close h nt G
r @
Quarter close ma tude ku is S
d y -
r e d e th
r a th to us
( b ha nse
R e able
r s f er
athMonth-end
a
h -tran
For example: or quarter-end closing entries can be:
B
non
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 s a
)h a
the pattern in the suggested rules. m
co uide
e
@ hp the
Define your own rules based on attributes from
n t different
G
m ar batch,
parts of your journal, including the ledger,
t u de header, or
u
line level. y-k is S d d th
r e e
r a th to us
( b ha nse
R e able
a r
For example, s fer source, account, or descriptive flexfield information as selection
athuse ncategory,
Bhfor the
criteria n - ra to be sent for approval.
tjournals
no is included in the rules because you typically define approval rules per ledger. Set
The ledger
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.

Journal Approval Hierarchies
Approval List Functionality

Type
Human Resources This method uses the HR Supervisory hierarchy levels
(HR) Supervisory and specifies 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. a
Position )h as
A relative dollar amount can be attached to a position.
Approval Group Approver groups represent functional e om idmatter
orcsubject e
h p t Gchain
experts outside the transaction's managerial
u of
authority, such as Legal or HRa r@ d e
personnel.
n
Dual Chain - kum is atStthe
Dual chains can beyprocessed
u
same time.
d d t h
t h re use
a r a e to
e dd ble l
t h R ra
Use thea r a nOracle
following s fe Fusion Approvals Management (AMX) List Builder to build your
Bh hierarchy
approval n - tra list.
Fornothe 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.

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.
s a
h
) a
o m
p e c uide
@ h nt G
r
a tude
u m
d y -k his S
r e d se t
a r ath e to u
e dd ble l
t h R ra
e
Note:h
Allocation nsf are not routed through the approval process.
ara trajournals
B n-
no

Journal Status Page
The Journals section of the General Accounting dashboard

displays the journals requiring your approval.
s a
)h a
m
co uide
e
@ hp nt G
The Journals page allows you to approve m aorr reject
t u dejournals if you
u
-k his S
are the current approver. d y
d se t
r e
a r ath e to u
e dd ble l
t h R ra
r a Generals e
fAccounting
a
Navigate to:
h -tra n > Journals
B
n n
Youomust 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.

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

following scenario:
s a
a
)h
m
co uide
e
@ hp nt G
m ar tude
y - ku is S
e d d th
r e
r a th to us
( b ha nse
R e able
a
The rules r ath nsfer
are:
Bh n1:-t1raLevel Supervisor: Approves between $500 and $10,000. One approver
Rule st
no
required.
Rule 2: 2nd Level Supervisor: Approves $10,000 or more. Two approvers required.
Rule 3: $500 or less is automatically approved. No approver required.

Summary

Describe the key concepts of approval management.
Perform basic approval configurations.

s a
h
) a
o m
p e c uide
@ h nt G
r
a tude
u m
d y -k his S
r e d se t
a r ath e to u
e dd ble l
t h R ra
a r a nsfe
Bh n-tra
no

D96139GC10 sg1

Încărcat de

Informații document

Titlu original

Drepturi de autor

Formate disponibile

Partajați acest document

Partajați sau inserați document

Opțiuni de partajare

Vi se pare util acest document?

Este necorespunzător acest conținut?

Drepturi de autor:

Formate disponibile

D96139GC10 sg1

Încărcat de

Drepturi de autor:

Formate disponibile

Unauthorized reproduction or distribution prohibited Copyright 2016, Oracle and/or its affiliates

Bruce Ingram Disclaimer

1 Introduction to Oracle Fusion Enterprise Structures with General Ledger

no Managerial Structure 1-24

2 Introducing Oracle Fusion Navigation

Infolets versus Infotiles 2-15

3 Introducing Functional Setup Manager

Security Reference Implementation 4-4

5 Discussing the Vision Story and Common Applications

Manage Geography Validations 5-20

Deployment Status 6-32

7 Configuring General Ledger Components

Accounting Calendar Considerations 7-56

Manage Reporting Currencies 8-18

9 Configuring Journal Approval

Intercompany General Ledger Integration 10-40

11 Configuring Period Close Components

Allocation Concepts 11-13

12 Configuring Financial Reporting

Dimension Values and Defaults 12-16

Custom Infolets: Overview 12-61

Manage AutoReverse Criteria Sets 13-24

Appendix A: Common Application Topics

Lookup Categories A-57

Outbound Transactions B-19

Introduction to Oracle Fusion

After completing this course, you should be able to:

Oracle Fusion Financials.

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

Each lesson in this course:

related to implementing Oracle Fusion Financials.

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

Classroom and Other Resources:

Ledger Implementation Student guide (This guide and its

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

- Data Relationship Management Administrator's Guide

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

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

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

Link to the Video Area in Oracle Help Center

Set Up Oracle Applications Cloud

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

File Based Data Import

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

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

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

This course is designed to generally follow this agenda:

Introducing Oracle Fusion Financials

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

Configuring Journal Approval

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

After completing this lesson, you should be able to:

Discuss Oracle Financials Cloud.

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

Oracle Fusion Applications are:

Engineered to work together.

and back office operations.

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

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

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

Supply Chain Management

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

Oracle Financials Cloud is a complete and integrated financial