<Insert Picture Here>

Differences Between EBS R12 General Ledger and

Fusion General Ledger Release 9
Agenda

• EBS GL R12 vs. Fusion GL R9

 EBS GL versus Fusion GL
EBS GL
Unified chart of accounts (Acctg Flex) that
includes segments, qualifiers and value sets
One Balancing Segment and a Secondary
Tracking Segment
Management segment qualifier
Dependent value set available
Segment Qualifier
Compile Accounting Flexfield
No Date Effective Hierarchy
Parent/child relationships defined when
defining segment values
Segment Value Security at Segment level
Segment Value Security: Grant by default
Fusion GL
Separation of COA structure and instance
Three Balancing Segments; no secondary
tracking segment
No management segment in V1
No dependent value set in V1
Terminology Change: Segment Label
“Deploy” Chart of Accounts
Date Effective Hierarchies
Parent/child relationships created separately
when defining hierarchies
Segment Value Security at Value Set level
(Creates issues if you share the same value set
between Co and Interco segments)
Segment Value Security: Deny by default
 EBS GL versus Fusion GL

EBS GL Fusion GL
Segment Value Security does NOT use Segment Value Security uses conditions, such
conditions as Equal to, Not Equal to, Between, etc.
Relational Balances (balances stored in Multi-dimensional balances (embedded Essbase
tables) cube)
Summary Templates required to stored Balances pre-aggregated and stored at every
summarized balances summarization level
No ability to assign parent values Can leverage trees (hierarchies) for:
(hierarchies) to: • Segment Value Security Rules
• Cross-validation rules • Cross-validation rules
• COA Mapping • COA Mapping
• Revaluations

Note: Use a different hierarchy than reporting,

analysis, and allocations
No condition filters on cross validation rules Cross validation rules use both a condition
(enabled or not enabled) filter and validation filter
 EBS GL versus Fusion GL
EBS GL
Balance level reporting currency created
automatically when Translation is run
Mass Allocations, Recurring Journals, and
AutoAllocations
Web ADI for spreadsheet integration
Global Consolidation System (GCS)
Accounting Setup Manager
Budget Journals
Only USD currency enabled out of the box
Fusion GL
Balance level reporting currency must be
defined in advance before Translation is run
Hyperion Calculation Manager (graphical tool
that can leverage trees for allocations)
ADFdi (ADF Desktop Integration) for
spreadsheet integration
Note: Must be installed as an add-on to Excel
Hyperion Financial Management (HFM)
Note: GL offers a light-weight consolidation
solution using balance transfer programs
Functional Setup Manager
No Budget Journals; Can only upload budget
balances directly to Essbase Cube
All currencies enabled; manually disable those
currencies you do NOT use to limit the list of
values
 EBS GL versus Fusion GL
EBS GL
Document Sequencing for GL and SLA
Journals
No Sequencing at Legal Entity Level or
via spreadsheet
Accounting Calendars: Manual definition
of accounting periods
No spreadsheet to create Cross-Validation
Rules and Account Combinations
No defaulting of accounts across setup UIs
Reconciliation flag at Chart of Accounts
level
No mobile-support for financial reporting
Fusion GL
No Document Sequencing; Only Accounting and
Reporting Sequences
(R9) Sequencing at Legal Entity Level using a
spreadsheet setup UI
Accounting Calendars: Automatic generation
of accounting periods
(R9) Rapid Implementation Spreadsheets
available
(R9) Defaulting of accounts to setup UIs
Reconciliation planned for future release
(R9) Mobile Financial Reporting Center
 Why COA Structure Separated from the Instance

• In R12 EBS, Data Access Sets were limited to ledgers

that shared the same COA and Calendar.
• We intended to expand Data Access Sets to be set at the
COA structure level where you have the same shape,
but you might have different value sets for different
countries.
• Best practice is to have a one to one relationship
between the chart of accounts structure and charts of
accounts instance.
• Do NOT have multiple COA instances share the same
structure.

Copyright © 2012, Oracle and/or Copyright

its affiliates.©All rights
2011, reserved.
Oracle Oracle
and/or Proprietary
its affiliates. Alland Confidential
rights reserved. Oracle Proprietary and Confidential.