Professional Documents
Culture Documents
Use of the information, documents and online training courses (collectively, Materials) found on this area of the Site constitutes
agreement with the following terms and conditions (as well as those set forth in the Purpose and Disclaimer sections below):
1. Oracle is pleased to allow its business partner (Partner) to download and copy the Materials found on this area of the Site. The
Materials are proprietary information of Oracle. Partner or other third party at no time has any right to resell, redistribute or create
derivative works from the Materials. The use of the Materials is restricted to the non-commercial, internal training of the Partners
employees only. The Materials may not be used for training, promotion, or sales to customers or other partners or third parties.
2. Oracle is a registered trademark of Oracle Corporation and/or its affiliates. Other names may be trademarks of their respective
owners.
3. Oracle disclaims any warranties or representations as to the accuracy or completeness of any Materials. Materials are provided "as is"
without warranty of any kind, either express, implied or statutory, including without limitation the implied warranties of merchantability,
satisfactory quality, fitness for a particular purpose, accuracy, timeliness and non-infringement of third-party rights. The information
contained herein is subject to change without notice.
4. Under no circumstances shall Oracle be liable for any loss, damage, liability or expense incurred or suffered which is claimed to have
resulted from use of these Materials. As a condition of use of the Materials, Partner agrees to indemnify Oracle from and against any and
all actions, claims, losses, damages, liabilities and expenses (including reasonable attorneys' fees) arising out of Partners use of the
Materials.
1 Copyright 2011, Oracle and/or its affiliates. All rights reserved. Oracle Proprietary and Confidential.
Purpose:
This document provides an overview of features and enhancements included in Oracle Fusion Applications 11gR1 Release 11.1.1.5.0
and applicable updates. It is intended solely to help you assess the business benefits of upgrading your existing Oracle Products to
this release, or implementing completely new Oracle developed products, and planning your I.T. Projects.
Disclaimer:
This document in any form, software or printed matter, contains proprietary information that is the exclusive property of Oracle. Your
access to and use of this confidential material is subject to the terms and conditions of your Oracle Software License and Service
Agreement or other applicable contract with Oracle, with which you agree to comply. This document and information contained
herein may not be disclosed, copied, reproduced or distributed to anyone outside Oracle without Oracles prior written consent. This
document is not part of your license agreement nor can it be incorporated into any contractual agreement with Oracle or its
subsidiaries or affiliates.
This document is intended to outline our general product direction. It is intended for informational purposes only and solely to assist you
in planning for the implementation and upgrade of the product features described. Release information contained in this document
is not a firm development plan. Release information published here should not be used as the basis for customer delivery
commitments, as part of marketing efforts, or during contract negotiations. This is not a commitment to deliver any material, code, or
functionality, and should not be relied upon in making purchasing decisions. The development, release, and timing of any features
or functionality, and inclusion or not thereof in the commercially available version of the Software, if any, is subject to change at any
time and is always at Oracles sole discretion. This document is not considered part of the applicable program documentation.
Due to the nature of the product architecture, it may not be possible to safely include all features described in this document without
risking significant destabilization of the code.
2 Copyright 2011, Oracle and/or its affiliates. All rights reserved. Oracle Proprietary and Confidential.
<Insert Picture Here>
Agenda
1. Overview
2. Key Features
Financial Reporting Structures
Charts of accounts
Calendars
Currencies
3. Additional Resources
4 Copyright 2011, Oracle and/or its affiliates. All rights reserved. Oracle Proprietary and Confidential.
Overview
Financial Enterprise Structures
* Covered in a separate implementation training: Oracle Fusion Financials Enterprise Structures Implementation and
Configuration Considerations Part 2
5 Copyright 2011, Oracle and/or its affiliates. All rights reserved. Oracle Proprietary and Confidential.
Overview
Key Features
6 Copyright 2011, Oracle and/or its affiliates. All rights reserved. Oracle Proprietary and Confidential.
Financial reporting structures
Charts of accounts
7 Copyright 2011, Oracle and/or its affiliates. All rights reserved. Oracle Proprietary and Confidential.
Feature Summary (1/2)
Financial reporting structures Charts of accounts
8 Copyright 2011, Oracle and/or its affiliates. All rights reserved. Oracle Proprietary and Confidential.
Feature Summary (2/2)
Financial reporting structures Charts of accounts
9 Copyright 2011, Oracle and/or its affiliates. All rights reserved. Oracle Proprietary and Confidential.
Key Decisions (1/2)
Financial reporting structures Charts of accounts
10 Copyright 2011, Oracle and/or its affiliates. All rights reserved. Oracle Proprietary and Confidential.
Key Decisions (2/2)
Financial reporting structures Charts of accounts
11 Copyright 2011, Oracle and/or its affiliates. All rights reserved. Oracle Proprietary and Confidential.
Implementation Concepts (1/9)
Financial reporting structures Charts of accounts
12 Copyright 2011, Oracle and/or its affiliates. All rights reserved. Oracle Proprietary and Confidential.
Implementation Concepts (2/9)
Financial reporting structures Charts of accounts
13 Copyright 2011, Oracle and/or its affiliates. All rights reserved. Oracle Proprietary and Confidential.
Implementation Concepts (3/9)
Financial reporting structures Charts of accounts
Dynamic
Dynamic account
account Dynamic
Dynamic account
account
creation
creation disabled
disabled creation
creation enabled
enabled
14 Copyright 2011, Oracle and/or its affiliates. All rights reserved. Oracle Proprietary and Confidential.
Implementation Concepts (4/9)
Financial reporting structures Charts of accounts
15 Copyright 2011, Oracle and/or its affiliates. All rights reserved. Oracle Proprietary and Confidential.
Implementation Concepts (5/9)
Financial reporting structures Charts of accounts
Account hierarchies
Create account hierarchies (trees) to identify managerial, legal or
geographical relationships between your value set values
Define date-effective tree versions to reflect organizational
changes within each hierarchy over time
Publish multiple hierarchies to balances cubes to allow for
financial reporting and analysis of past, present or future data
16 Copyright 2011, Oracle and/or its affiliates. All rights reserved. Oracle Proprietary and Confidential.
Implementation Concepts (6/9)
Financial reporting structures Charts of accounts
17 Copyright 2011, Oracle and/or its affiliates. All rights reserved. Oracle Proprietary and Confidential.
Implementation Concepts (7/9)
Financial reporting structures Charts of accounts
Is last descendent of Secures the last descendents (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.
18 Copyright 2011, Oracle and/or its affiliates. All rights reserved. Oracle Proprietary and Confidential.
Implementation Concepts (8/9)
Financial reporting structures Charts of accounts
Legend
Management hierarchy Geographical hierarchy
Access denied
19 Copyright 2011, Oracle and/or its affiliates. All rights reserved. Oracle Proprietary and Confidential.
Implementation Concepts (9/9)
Financial reporting structures Charts of accounts
Cross-validation rules
Determine what segment values may be combined with other
values across different segments of your chart of accounts
Prevent the creation of new account combinations only, in case
the underlying segment values violate the validation rules
Defined in terms of a condition filter and a validation filter
Condition filter - event under which the rule will be evaluated
Validation filter - condition that the account combination must
satisfy before it can be created
Your enterprise has determined that the Operations company value cannot
use the Marketing department. Create the following cross-validation rule to
prevent creating new account combinations that violate this requirement:
20 Copyright 2011, Oracle and/or its affiliates. All rights reserved. Oracle Proprietary and Confidential.
Deltas with EBS
Financial reporting structures Charts of accounts
21 Copyright 2011, Oracle and/or its affiliates. All rights reserved. Oracle Proprietary and Confidential.
Best Practices (1/11)
Financial reporting structures Charts of accounts
22 Copyright 2011, Oracle and/or its affiliates. All rights reserved. Oracle Proprietary and Confidential.
Best Practices (2/11)
Financial reporting structures Charts of accounts
Can I start using my You must deploy (compile) the Accounting Flexfield every time you
chart of accounts create new or make structural changes to your chart of accounts and
immediately after account hierarchies, to ensure that the new changes take effect across
creating or updating it? all applicable flows in Fusion Financials. This includes:
Creating a new chart of accounts structure, or modifying its key
attributes, or the attributes of its segments
Creating a new chart of accounts (structure instance), or modifying its
key attributes, or the attributes of its segments
Associating an account hierarchy to a chart of accounts segment
Enabling or disabling segment value security on a value set
23 Copyright 2011, Oracle and/or its affiliates. All rights reserved. Oracle Proprietary and Confidential.
Best Practices (3/11)
Financial reporting structures Charts of accounts
Value sets
Implementation question Recommendations and best practices
What validation type Only Independent and Table validations are supported. The
should I use? Dependent validation type is planned for a future release.
What value data type and Use the Character data type and the Text subtype, which
subtype should I use? are typical in natural account segment values. We recommend
restricting values to uppercase only and numeric values to be
zero-filled by default.
What should be the The maximum length of your value set must be limited to 25
maximum length of my characters due to a constraint in the account combinations
value set? table in Fusion General Ledger. Set the maximum length to
correspond to the width of the chart of accounts segment to
which it is assigned.
Should I start defining Associate your value set to a chart of accounts before defining
values immediately after your value set values. This ensures that the key attributes of
creating my value set? your values (e.g. Allow Posting, Account Type, etc.) can be
specified.
24 Copyright 2011, Oracle and/or its affiliates. All rights reserved. Oracle Proprietary and Confidential.
Best Practices (4/11)
Financial reporting structures Charts of accounts
25 Copyright 2011, Oracle and/or its affiliates. All rights reserved. Oracle Proprietary and Confidential.
Best Practices (5/11)
Financial reporting structures Charts of accounts
26 Copyright 2011, Oracle and/or its affiliates. All rights reserved. Oracle Proprietary and Confidential.
Best Practices (6/11)
Financial reporting structures Charts of accounts
Chart of accounts
Implementation question Recommendations and best practices
How do I define my The chart of accounts (structure instance) definition is based on
chart of accounts the chart of accounts structure it is associated with. If your
structure instances? enterprise needs identical structures for different charts of
accounts, consider creating one structure and customize your
charts of accounts accordingly to fit your enterprise needs.
How do I associate an For each segment, you may assign an account hierarchy (Tree
account hierarchy to Code attribute) that will be used for general ledger processing,
my segments? as well as allocations and financial reporting.
27 Copyright 2011, Oracle and/or its affiliates. All rights reserved. Oracle Proprietary and Confidential.
Best Practices (7/11)
Financial reporting structures Charts of accounts
28 Copyright 2011, Oracle and/or its affiliates. All rights reserved. Oracle Proprietary and Confidential.
Best Practices (8/11)
Financial reporting structures Charts of accounts
29 Copyright 2011, Oracle and/or its affiliates. All rights reserved. Oracle Proprietary and Confidential.
Best Practices (9/11)
Financial reporting structures Charts of accounts
30 Copyright 2011, Oracle and/or its affiliates. All rights reserved. Oracle Proprietary and Confidential.
Best Practices (10/11)
Financial reporting structures Charts of accounts
Account hierarchies
Implementation Recommendations and best practices
question
How do I create a new You must implement all your account hierarchies (trees) based on the
account hierarchy? seeded Accounting Flexfield Hierarchy tree structure.
When specifying the data source for your hierarchy, you must specify
the same value set code for both parent and detail values.
You must save your data source parameters before proceeding to the
next screen in your account hierarchy definition.
How do I define tree Define date-effective tree versions for your account hierarchies to
versions for my reflect organizational changes over time. The effective dates for your tree
hierarchy? versions must not overlap.
Before using your tree version, you must perform an online audit to
validate your version for any structural or functional errors.
To activate your tree version and ready it for use, set its status to
Active. You can only transact with and report on active versions.
Do I need to publish my You must publish your account hierarchies to cubes if you plan to use
account hierarchies? them for allocations and financial reporting. Otherwise, they will only be
available for transactional flows. If you have not finalized your accounting
configuration, you can mark your hierarchies for publishing and they will
be picked up when your ledger setup is complete.
31 Copyright 2011, Oracle and/or its affiliates. All rights reserved. Oracle Proprietary and Confidential.
Best Practices (11/11)
Financial reporting structures Charts of accounts
Can I delete an account You must decommission (unpublish) a tree version from your
hierarchy? balances cubes before deleting it (or deleting its associated
hierarchy), otherwise you will no longer be able to remove it from
your cube outlines.
32 Copyright 2011, Oracle and/or its affiliates. All rights reserved. Oracle Proprietary and Confidential.
Relevant Setup Tasks
Financial reporting structures Charts of accounts
(1) Covered in the Oracle Fusion General Ledger Implementation and Configuration Considerations implementation training
(2) Navigate to this task to run the Inherit Segment Value Attributes process
33 Copyright 2011, Oracle and/or its affiliates. All rights reserved. Oracle Proprietary and Confidential.
Financial reporting structures
Calendars
34 Copyright 2011, Oracle and/or its affiliates. All rights reserved. Oracle Proprietary and Confidential.
Feature Summary
Financial reporting structures Calendars
35 Copyright 2011, Oracle and/or its affiliates. All rights reserved. Oracle Proprietary and Confidential.
Implementation Concepts (1/3)
Financial reporting structures Calendars
Accounting Calendars
Generate your accounting periods automatically by specifying your
calendar attributes from a pool of commonly used standard/adjusting
period frequencies, and other key parameters
Period frequency Adjusting period frequency
Weekly None
4/4/5 1 year end
4/5/4 1 year beginning and 1 year end
5/4/4 1 mid year and 1 year end
4 Week 2 year end
Monthly 1 mid year and 2 year end
Quarterly Quarterly
Yearly
Other
Other
If your organization uses a custom type of calendar that does not fit
any of the seeded frequencies, then you must use the Other period
frequency, and manually define the period start/end dates
36 Copyright 2011, Oracle and/or its affiliates. All rights reserved. Oracle Proprietary and Confidential.
Implementation Concepts (2/3)
Financial reporting structures Calendars
37 Copyright 2011, Oracle and/or its affiliates. All rights reserved. Oracle Proprietary and Confidential.
Implementation Concepts (3/3)
Financial reporting structures Calendars
Transaction Calendars
Implement transaction calendars only if your enterprise requires
ledgers with average balance processing
Generate your transaction dates automatically by specifying the
business day schedule.
Customize the generated dates to account for holidays or non-
business days specific to your enterprise
38 Copyright 2011, Oracle and/or its affiliates. All rights reserved. Oracle Proprietary and Confidential.
Deltas with EBS
Financial reporting structures Calendars
Period type Not applicable The EBS Period Type concept is no longer
exposed in the Fusion Financials screens. You
must create a new accounting calendar for
different period types (frequencies), and this
creation process has greatly been improved to
allow the automatic generation of accounting
periods.
39 Copyright 2011, Oracle and/or its affiliates. All rights reserved. Oracle Proprietary and Confidential.
Best Practices
Financial reporting structures Calendars
Accounting Calendars
Implementation question Recommendations and best practices
What is the difference This impacts what year to append when generating the period
between calendar year names for your accounting calendar:
and fiscal year formats? Select the calendar year format to append the year of the periods
start date to the period name.
Select the fiscal year format to append the year associated with the
period, regardless of its date range, to the period name.
I plan to run the If you plan to run the translation process for any ledger associated
translation process in with your accounting calendar, keep in mind the following rule: You
Fusion General Ledger. cannot run translation for the first period of an accounting
How does this impact calendar. In the current release of Fusion General Ledger, we do
my accounting calendar not allow to create a calendar year with a fewer number of periods
than what the period frequency dictates. Therefore, we recommend
implementation?
that you add a full extra year in your accounting calendar before the
first opened period of any ledger using this calendar. For example, if
you plan to start transacting in Jan-11, and intend to run translation
for that same Jan-11 period, start your calendar in Jan-10 (2010
year), add the 2011 year to your calendar, and then assign this
calendar to your ledger with Jan-11 as the first opened period.
40 Copyright 2011, Oracle and/or its affiliates. All rights reserved. Oracle Proprietary and Confidential.
Relevant Setup Tasks
Financial reporting structures Calendars
41 Copyright 2011, Oracle and/or its affiliates. All rights reserved. Oracle Proprietary and Confidential.
Financial reporting structures
Currencies
42 Copyright 2011, Oracle and/or its affiliates. All rights reserved. Oracle Proprietary and Confidential.
Feature Summary
Financial reporting structures Currencies
Maintain your currencies and define daily rates to record and run
cross-currency transactions and accounting processes
43 Copyright 2011, Oracle and/or its affiliates. All rights reserved. Oracle Proprietary and Confidential.
Implementation Concepts (1/3)
Financial reporting structures Currencies
Currencies
All ISO currencies are predefined; you must enable the
currencies you need for your financial transactions and
processes
The STAT currency is also predefined and should be used for
statistical data entry
If needed, you can define new currencies and customize them to
fit your enterprise transactional requirements
44 Copyright 2011, Oracle and/or its affiliates. All rights reserved. Oracle Proprietary and Confidential.
Implementation Concepts (2/3)
Financial reporting structures Currencies
45 Copyright 2011, Oracle and/or its affiliates. All rights reserved. Oracle Proprietary and Confidential.
Implementation Concepts (3/3)
Financial reporting structures Currencies
Daily Rates
A daily rate defines the exchange rate relationship between 2
currencies, using a specific conversion rate type and on particular
conversion date
Daily rates are shared across all ledgers in Fusion General Ledger
Subledger applications share the same daily rates with the general
ledger, but different rate types provide each subledger the ability to
convert transactions at different rates
46 Copyright 2011, Oracle and/or its affiliates. All rights reserved. Oracle Proprietary and Confidential.
Best Practices
Financial reporting structures Currencies
Daily rates
Implementation question Recommendations and best practices
How do I create daily Use the ADFdi spreadsheet to create, update or delete
rates? daily rates. You may also use the user interface to update or
delete existing daily rates.
Alternatively, your enterprise may decide to use its own
processing mechanism to upload rates directly to the daily
rates interface table. Run the Import and Calculate Daily
Rates process to import your rates into the daily rates table
and ready them for use.
47 Copyright 2011, Oracle and/or its affiliates. All rights reserved. Oracle Proprietary and Confidential.
Relevant Setup Tasks
Financial reporting structures Currencies
48 Copyright 2011, Oracle and/or its affiliates. All rights reserved. Oracle Proprietary and Confidential.
Additional Resources
49 Copyright 2011, Oracle and/or its affiliates. All rights reserved. Oracle Proprietary and Confidential.