Oracle Fusion General Ledger

Release 9
Copyright © 2013, Oracle and/or it’s affiliates. All rights reserved.
 Key Product Features
Fusion General Ledger
Journals Multi-Currency & Multi-GAAP
• Extensive spreadsheets for entering journals and • Translation, revaluations, and currency conversion
correcting journal import errors • Spreadsheet-based currency rates upload (daily and
• Multi-currency journals historical rates)
• Journal copy • Support for multiple accounting representations (i.e.,
• Robust, wizard-like allocations with Calculation Manager IFRS and local rules)
• Recurring Journals/Allocations across periods and across
ledgers
• Greater collaboration with Oracle Social Network integration
Productivity
• Role-based dashboards and work areas that:
Watch this video about Oracle Social Network integration in Fusion Proactively monitor transactions and push work to
Financial Applications users
Allow collaboration with participants
Monitor account balances
Monitor the close status across ledgers/subledgers

Copyright © 2013, Oracle and/or it’s affiliates. All rights reserved.

 Key Product Features (continued)
Fusion General Ledger

Reporting & Analysis

• Flexible chart of accounts (up to 30 segments)
• Multiple balancing segments (up to 3)
• Segment value security to prevent certain users from viewing certain sensitive account balances
• Date-effective hierarchies (trees)
• Multi-dimensional reporting and analysis on live data
• Self-service access to reports from Financial Reporting Center Watch this video about the Financial Reporting Center

• (R9) Mobile Financial Reporting Center

• (R9) Sunburst Visualization Tool for Reporting and Analysis
• Account Monitor to track anomalies in account balances in real-time
• FR for board-room ready financial reports
• SmartView for interactive, ad hoc reporting and analysis within a spreadsheet Watch this video about SmartView

Copyright © 2013, Oracle and/or it’s affiliates. All rights reserved.

 Key Product Features (continued)
Fusion General Ledger

Period Close
• Centralized Close Monitor to monitor the close status of subledgers and ledgers

Watch this video about the Close Monitor

• Reconciliation reports to reconcile AP and AR with GL with drill downs to underlying transactions
• Drill down capability from target ledger balances to source ledgers if balances were transferred
• (Non-Cloud Implementations) Integration with Oracle EPM (i.e., Hyperion Planning and Budgeting,
Hyperion Financial Close Management, Hyperion Disclosure Management)
• (R9 Cloud Implementations) Integration with Oracle Hyperion Planning and Budgeting Cloud Service

Copyright © 2013, Oracle and/or it’s affiliates. All rights reserved.

 Key Product Features (continued)
Fusion General Ledger

Close Monitor

Copyright © 2013, Oracle and/or it’s affiliates. All rights reserved.

 Key Product Features
Fusion General Ledger

Setup
• Centralized setup using Functional Setup Manager
• File-based spreadsheet loaders for upload /maintenance of segment values and hierarchies
• Migration of setup data across instances (i.e., test and production)
• Rapid Implementation Spreadsheets to create the following:
 Multiple legal entities  (R9.2) Account Combinations
 Multiple ledgers (one per country)  (R9.2) Cross-Validation Rules
 Multiple business units  (R9.2) Segment Value Security
 One Accounting Calendar
 (R9) Account Defaulting to Other Setup UIs
 (R9) Document and Journal Sequencing

Copyright © 2013, Oracle and/or it’s affiliates. All rights reserved.

 Key Product Features
Fusion General Ledger

Setup
• Diagnostic tests to perform health check and data validation on the following :
 Chart of Accounts  Legal Entities and Legal Reporting Units
 Value Sets and Values  Ledgers Setup
 Account Hierarchies Versions  Document and Journal Sequences (includes Accounting and
 Accounting Calendars Reporting Sequences

Copyright © 2013, Oracle and/or it’s affiliates. All rights reserved.

 Key Setup Tasks: Rapid Implementation for Financials Task List

Copyright © 2013, Oracle and/or it’s affiliates. All rights reserved.

 Key Setup Tasks: Financials Offering

Copyright © 2013, Oracle and/or it’s affiliates. All rights reserved.

 Implementation Considerations

Accounting Calendar Budget Upload

• Always create a few extra periods in advance of the • Best practice is to always use the ADFdi spreadsheet
initial period. You cannot change the calendar later. “Create Budgets via Spreadsheet” task in the GAM
• Foreign currency translation cannot be performed in the Dashboard.
initial period opened for your ledger. Consider defining a • The following are ignored for Budget Upload to the
complete prior year. Essbase Cube:
• Do not change the name of the period after you have  Cross Validation Rules
opened the period.
 Segment Value Security Rules
 Data Access Set Security
Currency Translation
Note: Only Budget Scenario Security is followed
• You must first define a balance level reporting currency
BEFORE you run translation in the target currency.

Copyright © 2013, Oracle and/or it’s affiliates. All rights reserved.

 Implementation Considerations

Chart of Accounts
1. Must create your value sets then COA structure and instance before assigning values to the value sets.
2. You must deploy your chart of accounts before use.
3. If enabling segment value security, users will not be able to use the values until you explicitly grant them access.
4. If you want segment value security to apply for reports, you should consider using the reporting hierarchy that has been
published to Essbase Cubes. You may need 2 different hierarchies: One for Reporting users & another for data entry folks.
5. In setup UIs, if Segment Value Security is enabled, you will see account combinations with those secured values but if you
try to update the field, you won't be able to use those secured values.
6. For transaction and reporting UIs, if Segment Value Security is enabled, you will NOT be able to view and use the
secured values.
7. If using a Company and Intercompany Segment that share the same values, segment value security rules apply at the
value set level. So if you want to secure access to company values, best practice is to NOT share the same value set for
both segments.
8. Use the validation type of “Independent “or “Table Validated” with the Data Type of “Character” and Subtype of “Text.”
9. Have a one to one mapping between a chart of accounts structure and instance. In other words, do not have multiple
instances associated with the same structure.
Copyright © 2013, Oracle and/or it’s affiliates. All rights reserved.
 Implementation Considerations
Considerations for Implementing Segment Value Security
• Do I need segment value security?
Implement segment value security if you need to control access to parent and detail values across
any chart of accounts segment.

• Is it different from data access set security?

Data access set security controls access to ledgers and primary balancing segment values only in
Fusion General Ledger. We recommend using data access security to secure your primary
balancing segment values, and segment value security to secure all other segment values.

• How is it different from cross validation rules?

Cross-validation rules only prevent the creation of new account combinations in case the
underlying segment values violate the validation rules you specify. Segment value security
controls the access to the values of each chart of accounts segment, irrespective of the values in
other segments.

Copyright © 2013, Oracle and/or it’s affiliates. All rights reserved.

 Key Concepts
How Does Segment Value Security Work
Segment value security is enforced in Oracle Fusion Applications where ever
the charts of accounts values are used.
• When entering journals
You can only use account values for which the access is granted using segment security rules.

• When running reports or performing inquiry against a ledger

You can only view financial data for accounts for which the access is granted using segment
security rules.

• When viewing setup objects

If accounts specified in the setup include references to an account with values you have not been
granted access to, you can see the account but will not be able to use that secured value if you
select to modify the setup.

Copyright © 2013, Oracle and/or it’s affiliates. All rights reserved.

 Best Practices
Implementing Segment Value Security (1/3)
• Segment value security is enabled at the value set level and will affect
all chart of accounts that reference that value set.

• Segment value security only applies to independent value sets.

• Securing a value set denies access to all values by default. Users that
need to access values will need to be specifically granted access.

• When enabling or disabling segment value security for a value set,

you need to re-deploy your key accounting flexfield.

Copyright © 2013, Oracle and/or it’s affiliates. All rights reserved.

 Best Practices
Implementing Segment Value Security (2/3)
• Create custom external roles for the purpose of grouping segment value security rules to be
assigned to one or more users.
• Plan for the number of segment value security external roles you need to represent unique
segment value security profiles across your users.
• You can assign multiple security rules related to a particular segment value security profile to
the same segment value security role (Think of these roles as SVS rule sets)
• Create these roles ahead of defining the segment value security rules so that the roles are
available.
• Assign the rules to roles once you have defined them to create a complete data security
policy.
• Assign a segment value security role to the users that require that particular SVS data
security profile

Copyright © 2013, Oracle and/or it’s affiliates. All rights reserved.

 Best Practices
Implementing Segment Value Security (3/3)
Creating segment value security roles:
In Oracle Identity Manager (OIM):
1. Create a role by giving it a name.
2. Use an underscore between each word in the name.
3. Define a user friendly display name with a hyphen before the SVS Role at the
end of the name. For example, define a Name of
ACCOUNTING_COST_CENTER-SVS_ROLE and a display name of Accounting
Cost Center-SVS Role.
Note: For segment value security roles, the best practice is to give them a common
suffix, such as SVS (segment value security), to more readily identify them. You
can assign these custom roles a Role Category of Default.

Copyright © 2013, Oracle and/or it’s affiliates. All rights reserved.

 Segment Value Security Policies

•In this example, you enable

Security
SVS Role Security policy security on both the Cost
condition
associated Center and Account value
“Accounting with the Cost sets that are associated with
Cost Center Cost Center- Center value your chart of accounts.
Equal to SVS Role”
Example

set
“Accounting” •Users assigned the
“Accounting Cost Center-SVS
Role” and “US Revenue
Account-SVS Role” will have
Security access to cost center
SVS Role Security policy ‘Accounting’ and account ‘US
condition
associated Revenue’.
“US Revenue with the
Account Account-SVS Account value •All other users will be denied
Equal to Role” set access to all cost center and
“US Revenue” account value set values.

Copyright © 2013, Oracle and/or it’s affiliates. All rights reserved.

 Segment Value Security Rules Operators
You may use any of the following operators in your conditions to
secure your segment values:
Operator Usage
Equal to Secures a specific detail value. You cannot use this operator to secure a parent value.
Not equal to Secures all detail values except one that you specify. You cannot use this operator to
secure a parent value.
Between Secures a range of detail values.
Is descendant of Secures the parent value itself and all of its descendants, including mid-level parents and
detail values. To use this tree operator, you must specify an account hierarchy (tree) and
a tree version. However, the security rules apply across all tree versions of the specified
hierarchy, as well as all hierarchies associated with the value set.
Is last descendant of Secures the last descendants (i.e. the detail values) of a parent value. To use this tree
operator, you must specify an account hierarchy (tree) and a tree version. However, the
security rules apply across all tree versions of the specified hierarchy, as well as all
hierarchies associated with the value set.

Copyright © 2013, Oracle and/or it’s affiliates. All rights reserved.

 Segment Value Security Rules and Hierarchies
An Example
List of values is accessible across
Retrieve account Derive effective Apply security condition all versions of the secured
hierarchy from version based on to get the list of hierarchy, and across all
security rule system date descendants based on hierarchies associated with the
Management Management the effective tree version value set
hierarchy/2010 version hierarchy/2011 version The parent value itself and
is specified when is the effective tree In Management hierarchy/2010
all its descendants will be
securing parent value version based on the version, 203 is denied access. All
secured based on the
100 using the ‘Is system date other values can be accessed
effective tree version. The
descendant of’ values are: 100, 200, 300, In Geographical hierarchy,
operator 101, 201, 202, 301, 302 400/401/402 are denied access. All
other values can be accessed
Example

Legend
Management hierarchy Geographical hierarchy

2010 version 2011 version 2010 version Access granted

100 100 100

Access denied
101 200 300 200 300 200 300 400

201 202 203 301 302 101 201 202 301 302 201 301 302 401 402

Copyright © 2013, Oracle and/or it’s affiliates. All rights reserved.

 Segment Value Security Rules with Hierarchies
• Segment value security rules must be defined before account hierarchies are published
to cube to be effective.
• For changes with hierarchical segment value security rules, or changes in a referenced
hierarchy, republish the tree versions affected by the rule change for rules to be effective
in the cube.
• Multiple processes need to be run for hierarchy changes, including auditing, activating,
row and column flattening. For changes to the primary balancing segment hierarchy,
you also need to run the value set and hierarchies maintenance programs to ensure
effective security enforcement.
• You can submit the Process Account Hierarchies program to automatically run these
account hierarchies related processes in one submission.

Copyright © 2013, Oracle and/or it’s affiliates. All rights reserved.

 Implementation Considerations

Publishing Dimension Members and Hierarchies to the Balances Cube

Submit the Publish Chart of Accounts Dimension Members and Hierarchies program to update the balances cube for chart of
accounts value set and hierarchy changes. If you did NOT make changes to the hierarchy assigned to a value set, select YES
to Publish Detail Values Only.

Copyright © 2013, Oracle and/or it’s affiliates. All rights reserved.

 Segment Value vs. Data Access Set Security
• Segment value security rules assigned to the user via his various roles that reference the same
secured value set are always in effect simultaneously

• Data access set security can be a little different depending whether working with those General
Ledger features that are based directly on the balances cube versus those that are not.
– User can be assigned multiple data access sets referencing the same balances cube.

– When working on features not directly related to the balances cube, the specific ledger and primary balancing
segment values access as defined in the user’s selected data access set will apply.

– When working directly with the balances cube, the cumulative effect of the user's combined data access sets for
that cube will be enforced. User will simultaneously have access to the sum of all primary balancing segment
values for all ledgers granted to him via his combined data access sets when working with the balances cube.

Copyright © 2013, Oracle and/or it’s affiliates. All rights reserved.

 Implementation Consideration
Hierarchies – Foundation of Reporting

Copyright © 2013, Oracle and/or it’s affiliates. All rights reserved.

 Implementation Considerations

Hierarchies (Trees)
1. Carefully consider different hierarchy requirements for reporting, allocations, cross validation rules, revaluations, and
chart of accounts mapping. You should use a different hierarchy for reporting & analysis and allocations.
2. Hierarchies used for reporting & analysis and allocations cannot have the same child value rolling up to 2 different
parents.
3. When using hierarchies for reporting and allocations, you must publish them to create the Essbase cubes.
4. Always create at least two hierarchy versions before creating any financial reports or allocations. This will force the fully
qualified member name path to be generated and refers to the full tree name and tree versions. This will minimize report
maintenance if you must add tree versions in the future.
5. Non-reporting and non-allocation hierarchies CAN have the same child rolling up to multiple parents.
6. Hierarchies used for cross validations, revaluations, segment value security, and chart of accounts mapping have to be
defined within the SAME hierarchy. The hierarchy must then be associated with a chart of accounts instance.
7. You can only associate one hierarchy with a chart of accounts instance, per segment.
8. It is best practice to create a top-most root node (Level 0) unless the hierarchy is used for cross validations, revaluations,
or chart of accounts mapping. For the latter, you need at least three level 0 nodes for easy selection.

Copyright © 2013, Oracle and/or it’s affiliates. All rights reserved.

 Implementation Considerations
Process Account Hierarchies for any hierarchy changes

Manually submit the Process Account Hierarchies under the following scenarios:
• When a new tree or tree version is defined.
• If the tree or tree version has changes that would alter the flattened hierarchy data, such as adding, moving, or duplicating members, or
anything that impacts the flattened hierarchy data.
• If Data Relationship Manager (DRM) is used with Fusion GL, after running the Load Account Values and Hierarchies (LoadMasterData)
program from ESS to load chart of accounts reference data from DRM to Fusion GL.
• If new COA values are added that are within the account range assigned to the hierarchy.
• Process Account Hierarchies (New in R9) automatically run the following process
• Tree Audit and Tree Activation
• Tree Row Flattening
• Tree Column Flatenning
• Maintain Value Sets
• Maintain Account Hierarchies
• Publish Hierarchies (you can choose not to run this process)

Copyright © 2013, Oracle and/or it’s affiliates. All rights reserved.

 Trouble Shooting
Issue Possible Resolution
COA Deployment Error • Re-run the deployment process and expand the progress details window to determine the
point of failure.
• Ensure the required qualifiers (primary balancing and natural account segments) are defined.
• Make sure the tree that has been assigned to a value set referenced in a COA structure
instance is ACTIVE. In order for the deployment process to proceed, at least one active
version must be set for the tree.
• Make sure all chart of accounts instance definitions are completely defined.
Tree Version Audit Process Fails • Make sure parent values have the summary attribute set correctly.
When 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 Defined in Fusion • Submit the process to propagate and update required account hierarchies to the Essbase GL
GL is Not Available in Essbase balances cube from the Publish Account Hierarchies page.
GL Balances Cubes
• Check that the Publish option is enabled for the versions that are to be published.
• Check that a Request ID is returned and the process completes successfully after clicking the
Publish action button.
Copyright © 2013, Oracle and/or it’s affiliates. All rights reserved.
 Trouble Shooting (continued)
Issue Possible Resolution

Error in Publish Account Hierarchies or • Make sure all users sign out of Financial Reporting, Smart View, and Calculation
Publish Chart of Accounts Dimension Manager during the submission of the publish process. You cannot have users
Members and Hierarchies programs connecting to the cube while running these programs.

Enabled or disabled flexfield security • Enabled or disabled flexfield security policies are not automatically applied to the
policies are not in effect for Essbase GL Essbase cube if these were set after the cube was created.
balances cube
• Account hierarchies must be republished in order to apply newly enabled or
disabled flexfield security policies.
Note: Flexfield security is enabled and disabled in the Value Set page
Need a new accounting scenario member • New scenario members are added in the seeded value set called Accounting
to load budget and forecast data into Scenario.
Essbase GL balances cubes
• Query this seeded value set, and add a new value for each budget or forecast that
is needed to be tracked in Essbase GL balances cubes.

Copyright © 2013, Oracle and/or it’s affiliates. All rights reserved.

 Additional References
Support.Oracle.Com
• Getting Started with Oracle Fusion Applications: Common Implementation
(Doc 1387777.1)
• Getting Started with Oracle Fusion Applications: Common Reporting (Doc
1458898.1)
• Getting Started with Oracle Fusion Applications: Financials Reporting (Doc
1458904.1)
• Getting Started with Oracle Fusion Applications: Enterprise Structures for
Financial (Doc 1387746.1)
• Oracle® Fusion Applications Common Implementation Guide 11g Release 1
(11.1.2) Part Number E20360-02

Copyright © 2013, Oracle and/or it’s affiliates. All rights reserved.

 Additional References
docs.oracle.com/cd/E37017_01/nav/financials.htm
Fusion Financials
• Understanding Enterprise Structures
• Oracle Fusion Financials Understanding Financials
• Using Common Features
• Oracle Financials Cloud Using Accounting Transactions, Tax Transactions, and
Reporting

EPM
• Enterprise Performance Management Workspace Administrator's Guide
• Oracle Enterprise Performance Management Workspace User's Guide

Copyright © 2013, Oracle and/or it’s affiliates. All rights reserved.

 Additional References

Essbase
• Essbase Database Administrator's Guide
• Essbase Studio User's Guide
Hyperion
• Hyperion Data Relationship Management Administrator's Guide
• Hyperion Data Relationship Management Oracle GL Integration Guide
• Hyperion Data Relationship Management User's Guide
• Hyperion Financial Reporting Administrator's Guide
• Hyperion Financial Reporting Studio User's Guide
• Hyperion Financial Reporting User's Guide
• Hyperion Provider Services Administration Guide
• Hyperion Smart View for Office User's Guide

Copyright © 2013, Oracle and/or it’s affiliates. All rights reserved.

 Other Fusion Documentation
• http://docs.oracle.com/cd/E48434_01/nav/financials.htm

Copyright © 2013, Oracle and/or it’s affiliates. All rights reserved.

 Other Fusion Documentation
• https://fusionhelp.oracle.com/

Copyright © 2013, Oracle and/or it’s affiliates. All rights reserved.

 Fusion Cloud Documentation
• https://docs.oracle.com/cloud

Copyright © 2013, Oracle and/or it’s affiliates. All rights reserved.