Oracle Online Training Materials – Usage Agreement

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 Partner’s
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 Partner’s 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 Oracle’s 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 Oracle’s 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.

. Oracle Proprietary and Confidential. Overview Financial Enterprise Structures • Financial enterprise structures are the entities that define the reporting. All rights reserved. Oracle and/or its affiliates. legal and business aspects of your enterprise * Covered in a separate implementation training: Oracle Fusion Financials Enterprise Structures Implementation and Configuration Considerations – Part 2 5 Copyright © 2011.

Overview Key Features • Financial reporting structures • Charts of accounts • Value Sets • Chart of accounts structures • Chart of accounts structure instances • Account hierarchies • Cross validation rules • Calendars • Accounting calendars • Transaction calendars • Currencies • Currencies • Conversion rate types and daily rates 6 Copyright © 2011. Oracle Proprietary and Confidential. Oracle and/or its affiliates. All rights reserved. .

All rights reserved. . Financial reporting structures Charts of accounts 7 Copyright © 2011. Oracle Proprietary and Confidential. Oracle and/or its affiliates.

segments. . segment labels and value sets • Reuse the same chart of accounts structure to create different chart of accounts structure instances that fit your enterprise needs • Create and publish date-effective hierarchies to reflect parent/child relationships between your segment values 8 Copyright © 2011. Oracle Proprietary and Confidential. Oracle and/or its affiliates. All rights reserved. Feature Summary (1/2) Financial reporting structures – Charts of accounts Create your charts of accounts to organize and track your financial transactions and reporting • Define your chart of accounts structure.

Feature Summary (2/2) Financial reporting structures – Charts of accounts • Define segment value security rules against your value sets to control access to parent and detail values across any chart of accounts segment • Define cross-validation rules to prevent creating account combinations when certain values across segments are combined 9 Copyright © 2011. Oracle and/or its affiliates. All rights reserved. Oracle Proprietary and Confidential. .

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. .

All rights reserved. Oracle Proprietary and Confidential. . Oracle and/or its affiliates. Key Decisions (2/2) Financial reporting structures – Charts of accounts 11 Copyright © 2011.

Implementation Concepts (1/9) Financial reporting structures – Charts of accounts Chart of accounts structure Chart of accounts structure instance 12 Copyright © 2011. Oracle Proprietary and Confidential. All rights reserved. . Oracle and/or its affiliates.

geared towards flexibility and minimizing setup efforts • Defines the number of segments. labels and default value set for each segment • Chart of accounts structure instance • Also referred to as chart of accounts • Multiple charts of accounts can share the same structure. segment sequence. but each may be customized differently to fit your transactional and reporting requirements: • Value set • Account hierarchy • Dynamic combination creation 13 Copyright © 2011. All rights reserved. . Oracle Proprietary and Confidential. Implementation Concepts (2/9) Financial reporting structures – Charts of accounts • Chart of accounts structure • Building block of your chart of accounts implementation. Oracle and/or its affiliates.

Oracle and/or its affiliates. . Oracle Proprietary and Confidential. Implementation Concepts (3/9) Financial reporting structures – Charts of accounts • Example: Chart of accounts structures and instances Primary Primary Second Second Natural Natural balancing balancing balancing balancing account account segment segment segment segment segment segment 1 2 3 Dynamic Dynamic account account Dynamic Dynamic account account creation creation disabled disabled creation creation enabled enabled 14 Copyright © 2011. All rights reserved.

a financial category and other key transactional attributes Second balancing segment Optional Third balancing segment Optional Intercompany segment Optional – used in intercompany balancing. Oracle Proprietary and Confidential. It is recommended that you enable the cost center segment for your chart of accounts. All rights reserved. Cost center segment Only required if accounting for certain transactions in Fusion Financials. If this is a new chart of accounts implementation. you should enable the intercompany segment. Management segment Do not use – planned for a future release 15 Copyright © 2011. Oracle and/or its affiliates. Implementation Concepts (4/9) Financial reporting structures – Charts of accounts • Segment labels (qualifiers) • Segment labels assign special functionality to certain segments in your chart of accounts structure • You may use up to 3 balancing segments to allow for more granular transaction tracking and financial reporting Segment label Usage Primary balancing segment Required – ensures that all journals are balanced for each primary balancing segment value Natural account segment Required – mapped to an account type. .

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. . Oracle Proprietary and Confidential. All rights reserved. present or future data 1 2 16 Copyright © 2011. Oracle and/or its affiliates.

Oracle and/or its affiliates. Implementation Concepts (6/9) Financial reporting structures – Charts of accounts • Segment value security • Define security rules against your value sets to control access to parent or detail segment values • Securing a value set denies access to all values by default. All rights reserved. Oracle Proprietary and Confidential. 17 Copyright © 2011. you enable security on both the Cost Center and Account value sets that are associated with your chart of accounts. Create conditions and assign them to specific data roles to control access to your segment values •In this example. . •All other users will be denied access to all cost center and account value set values. •Users assigned the “General Accountant – InFusion USA” data role will have access to cost center ‘Accounting’ and account ‘US Revenue’.

as well as all hierarchies associated with the value set. the detail values) of a parent value. Oracle and/or its affiliates. Is descendent of Secures the parent value itself and all of its descendents. the security rules apply across all tree versions of the specified hierarchy. You cannot use this operator to secure a parent value. All rights reserved. You cannot use this operator to secure a parent value. 18 Copyright © 2011. However. you must specify an account hierarchy (tree) and a tree version. as well as all hierarchies associated with the value set. Oracle Proprietary and Confidential. To use this tree operator. However. . including mid-level parents and detail values. Between Secures a range of detail values. Implementation Concepts (7/9) Financial reporting structures – Charts of accounts • Segment value security (cont’d) • 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 must specify an account hierarchy (tree) and a tree version. the security rules apply across all tree versions of the specified hierarchy. Not equal to Secures all detail values except one that you specify. To use this tree operator. Is last descendent of Secures the last descendents (i.e.

the 2011 version of the management hierarchy is the currently active version. For data security purposes. but a change in the cost center responsibilities requires you to create a 2011 version to highlight the new parent/child relationships. You originally secure (using the “Is descendent of” operator) the cost center “100” in the 2010 version of your management hierarchy. Legend Management hierarchy Geographical hierarchy 2010 version 2011 version 2010 version Access granted Access denied 19 Copyright © 2011. Oracle Proprietary and Confidential. Oracle and/or its affiliates. Implementation Concepts (8/9) Financial reporting structures – Charts of accounts • Segment value security (cont’d) Security rule based on hierarchical operator Your cost center segment has 2 account hierarchies: a management and a geographical hierarchy. All rights reserved. .

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.event under which the rule will be evaluated • Validation filter . . in case the underlying segment values violate the validation rules • Defined in terms of a condition filter and a validation filter • Condition filter . Create the following cross-validation rule to prevent creating new account combinations that violate this requirement: 20 Copyright © 2011.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. Oracle Proprietary and Confidential. Oracle and/or its affiliates. All rights reserved.

chart of block of your setup. . secondary segments balancing segments. Create instances multiple charts of accounts (structure instances) that share the same structure. thus allowing more tracking segment granular transaction tracking and financial reporting. Oracle and/or its affiliates. but customize each differently to fit your enterprise needs. Deltas with EBS Financial reporting structures – Charts of accounts R12 EBS Fusion Added benefits No chart of Chart of accounts The chart of accounts structure is the building accounts structures structures. geared towards flexibility accounts structure and minimizing implementation efforts. One balancing Up to 3 balancing Create your chart of accounts based on up to 3 segment. Flexfield Flexfield 21 Copyright © 2011. Segment Qualifier Segment Label N/A – nomenclature change. All rights reserved. Compile Accounting Deploy Accounting N/A – nomenclature change. Oracle Proprietary and Confidential.

follow the steps below: 1. Oracle Proprietary and Confidential. Oracle and/or its affiliates. Create your chart of accounts (structure instance) 4. Create your chart of accounts structure and specify your segment labels 3. All rights reserved. (Optional) Create and publish your account hierarchies 6. Create your value set values and specify mandatory attributes 5. (Optional) Define cross validation rules 22 Copyright © 2011. Best Practices (1/11) Financial reporting structures – Charts of accounts • To streamline your chart of accounts implementation. (Optional) Define segment value security rules 7. Create your value sets with no values 2. .

•After you complete your accounting configuration and begin your transaction cycle. Oracle and/or its affiliates. or modifying its key attributes. accounts? •Plan ahead and anticipate the growth of your enterprise by defining one or more “future” segments. making changes to the segments is neither recommended nor supported. . Best Practices (2/11) Financial reporting structures – Charts of accounts • General implementation considerations Implementation question Recommendations and best practices How do I design the •Design the structure of your chart of accounts carefully. 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. or the attributes of its segments •Creating a new chart of accounts (structure instance). 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. Oracle Proprietary and Confidential. All rights reserved. This includes: •Creating a new chart of accounts structure. or modifying its key attributes. Assign those segments a default value to streamline data entry in your Flexfield components. including structure of my chart of the number of segments and their sequence.

“Allow Posting”. 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. etc. This ensures that the key attributes of creating my value set? your values (e. Set the maximum length to correspond to the width of the chart of accounts segment to which it is assigned.g. What value data type and Use the “Character” data type and the “Text” subtype. We recommend restricting values to uppercase only and numeric values to be zero-filled by default.) can be specified. . Should I start defining Associate your value set to a chart of accounts before defining values immediately after your value set values. 24 Copyright © 2011. 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. “Account Type”. Oracle Proprietary and Confidential. which subtype should I use? are typical in natural account segment values. The should I use? “Dependent” validation type is planned for a future release. Oracle and/or its affiliates. All rights reserved.

How should I define my •All segment labels can only be assigned once throughout segment labels? the chart of accounts structure. and may be co-assigned with the cost center segment. Oracle and/or its affiliates. . however. •The following segment labels are mandatory: “Primary Balancing Segment” and “Natural Account Segment”. •Do not use the management segment label. All rights reserved. •The second/third balancing segments are optional. for new implementations. Oracle Proprietary and Confidential. and the assigned segment cannot be qualified with any other segment label. 25 Copyright © 2011. you should use this segment and assign the same values to both the primary balancing and intercompany value sets to enable clear visibility of the due to and due from relationships inherent in intercompany accounting. Best Practices (4/11) Financial reporting structures – Charts of accounts • Chart of accounts structure Implementation question Recommendations and best practices When should I create my You must create your chart of accounts structure after creating chart of accounts your value sets because the structure must be assigned a structure? default value set. It is planned for a future release. Each must be assigned to only segment. •The Intercompany segment is optional.

Must the segment The chart of accounts structure defines the number of sequence be gapless? segments and the segment sequence for your chart of accounts. All rights reserved. . Oracle Proprietary and Confidential. Best Practices (5/11) Financial reporting structures – Charts of accounts • Chart of accounts structure (cont’d) Implementation question Recommendations and best practices How do I choose my We recommend that you set the display width of each of your segment display width? segments to correspond to the maximum length of the value set to which it is assigned. Oracle and/or its affiliates. 26 Copyright © 2011. You must use sequential numbering (beginning with number 1) and avoid any gaps in the display order of your segments.

How do I associate an For each segment. . Oracle Proprietary and Confidential. 27 Copyright © 2011. Turn off creation? dynamic creation to prevent creating new account combinations throughout the Fusion Financials pages and processes. Should I turn on We recommend turning on the setting for dynamic combination dynamic combination creation until all setup-related activities are finalized. 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. consider creating one structure and customize your charts of accounts accordingly to fit your enterprise needs. and only limit it to the Account Combinations UI. Oracle and/or its affiliates. If your structure instances? enterprise needs identical structures for different charts of accounts. All rights reserved. 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.

28 Copyright © 2011. For segments that you expect to have a large number of distinct values. •You must create indexes in the GL_CODE_COMBINATIONS table for segments that are selectively required. When performing search in a transactional page. you must perform the following steps: •In the chart of accounts definition. All rights reserved. Best Practices (7/11) Financial reporting structures – Charts of accounts • Chart of accounts (cont’d) Implementation question Recommendations and best practices How do I choose my All chart of accounts segment attributes are inherited from the segment attributes? chart of accounts structure. mark the segment “Query Required” option as “Selectively required”. you must ensure that all segments be required and displayed in your chart of accounts by turning on the “Required” and “Displayed” attribute. you will have to specify the segment as a mandatory search criteria. Additionally. Oracle and/or its affiliates. . Oracle Proprietary and Confidential.

“Allow Posting”. Changing the summary flag attribute after completing your accounting configuration (ledger setup) is neither recommended nor supported. “Account Type”) are displayed and can be specified. An exception to this rule is the natural account value for the net income account in Fusion General Ledger. How should I set the This flag is not used directly in this release. All rights reserved. How should I set the You must this attribute to “Yes” for a detail value. Oracle and/or its affiliates. and to “No” Allow Posting attribute? for a parent value. When do I use a If you plan to use OTBI reporting. 29 Copyright © 2011. and Summary attribute? to “Yes” for a parent value. you must specify a financial Financial Category? category for your natural account values. Oracle Proprietary and Confidential. How should I set the You must set the Summary flag to “No” for a detail value. and to “Yes” for attribute? parent values. This ensures that the key attributes creating my value set? (e.g. for which you must set this flag to “No”. Best Practices (8/11) Financial reporting structures – Charts of accounts • Value set values Implementation question Recommendations and best practices Should I start defining We recommend defining your value set values after creating values immediately after your chart of accounts. but we Allow Budgeting recommend setting it to “No” for detail values. .

you must manually run the Inherit Segment Value Attributes process .g. . Is it OK to run the following processes: create new or modify •Maintain Value Sets – updates value set values in Fusion existing value set General Ledger tables. Oracle Proprietary and Confidential. Oracle and/or its affiliates. etc. “Start Date”. If you modify your segment value attributes (e. Best Practices (9/11) Financial reporting structures – Charts of accounts • Value set values (cont’d) Implementation question Recommendations and best practices I completed my If you create new value set values after your accounting accounting configuration (ledger setup) is complete. and want the associated account combinations to inherit them. 30 Copyright © 2011. All rights reserved. “Account Type”.). you must manually configuration. values? •Publish Chart of Accounts Dimension Members – publishes chart of accounts dimension member changes to balances cubes associated with the value set’s chart(s) of accounts. “End Date”. “Allow Posting”.

they will only be available for transactional flows. The effective dates for your tree hierarchy? versions must not overlap. you can mark your hierarchies for publishing and they will be picked up when your ledger setup is complete. How do I define tree •Define date-effective tree versions for your account hierarchies to versions for my reflect organizational changes over time. •When specifying the data source for your hierarchy. 31 Copyright © 2011. •You must save your data source parameters before proceeding to the next screen in your account hierarchy definition. Oracle Proprietary and Confidential. you must perform an online audit to validate your version for any structural or functional errors. set its status to “Active”. Otherwise. Oracle and/or its affiliates. •Before using your tree version. you must specify the same value set code for both parent and detail values. 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. . If you have not finalized your accounting configuration. You can only transact with and report on active versions. All rights reserved. •To activate your tree version and ready it for use. 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.

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). Best Practices (11/11) Financial reporting structures – Charts of accounts • Account hierarchies (cont’d) Implementation question Recommendations and best practices How do I ensure that When you create new account hierarchies. . 32 Copyright © 2011. •Maintain Chart of Accounts Hierarchies – updates chart of accounts hierarchies in Fusion General Ledger tables. All rights reserved. otherwise you will no longer be able to remove it from your cube outlines. Oracle and/or its affiliates. you must manually run the following updates to existing processes: ones go into effect? •Column Flattening and Row Flattening – run these online processes on a specific tree version to flatten the parent/detail value relationships in your tree version and ready it for your transactional and reporting flows. •Publish Chart of Accounts Dimension Members – publishes chart of accounts dimension member and hierarchy changes to balances cubes associated with the value set’s chart(s) of accounts. or make changes to new hierarchies or existing hierarchies. Oracle Proprietary and Confidential. •Maintain Value Sets – updates value set values in Fusion General Ledger tables.

Oracle and/or its affiliates. Oracle Proprietary and Confidential. . All rights reserved. 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.

. Financial reporting structures Calendars 34 Copyright © 2011. Oracle and/or its affiliates. Oracle Proprietary and Confidential. All rights reserved.

Oracle and/or its affiliates. All rights reserved. Oracle Proprietary and Confidential. . Feature Summary Financial reporting structures – Calendars Create your calendars to record and track your transactions by accounting periods and business days • Create your accounting calendars to record your transactions into accounting periods and monitor the close cycle across your entire enterprise • Create your transaction calendars to track your business and non-business days for average balance processing 35 Copyright © 2011.

. 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. All rights reserved. Oracle and/or its affiliates. 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 manually define the period start/end dates 36 Copyright © 2011. Oracle Proprietary and Confidential.

. Implementation Concepts (2/3) Financial reporting structures – Calendars • Accounting Calendars (cont’d) • Creating the calendar initially generates 1 year worth of periods • If needed. Oracle and/or its affiliates. Oracle Proprietary and Confidential. customize the generated period names/dates while abiding by the basic validation rules: • The period names must be unique • The period numbers must be unique within a year • The standard period dates must not overlap • There must be no gaps between the standard period dates or numbers • An adjusting period date range must overlap with that of a standard period • Generate additional years using the same parameters that you initially specified to create your calendar 37 Copyright © 2011. All rights reserved.

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. . Oracle Proprietary and Confidential. All rights reserved. Oracle and/or its affiliates. • Customize the generated dates to account for holidays or non- business days specific to your enterprise 38 Copyright © 2011.

and this creation process has greatly been improved to allow the automatic generation of accounting periods. 39 Copyright © 2011. Period type Not applicable The EBS “Period Type” concept is no longer exposed in the Fusion Financials screens. Deltas with EBS Financial reporting structures – Calendars R12 EBS Fusion Added benefits Manual definition Automatic generation The implementation of accounting calendars of accounting of accounting periods has been streamlined in Fusion Financials to periods allow the system to automatically generate the accounting periods for commonly used standard/adjusting period frequencies. All rights reserved. Oracle Proprietary and Confidential. If your enterprise uses a custom calendar. . you must define the period details manually. and avoid erroneous data entries. Oracle and/or its affiliates. You must create a new accounting calendar for different period types (frequencies). This allows you to save the time and effort of defining periods manually.

add the 2011 year to your calendar. Oracle and/or its affiliates. •Select the fiscal year format to append the year associated with the period. cannot run translation for the first period of an accounting How does this impact calendar. 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 period’s start date 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. regardless of its date range. For example. keep in mind the following rule: You Fusion General Ledger. Therefore. All rights reserved. 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. and intend to run translation for that same Jan-11 period. 40 Copyright © 2011. we do my accounting calendar not allow to create a calendar year with a fewer number of periods than what the period frequency dictates. start your calendar in Jan-10 (2010 year). . and then assign this calendar to your ledger with Jan-11 as the first opened period. to the period name. In the current release of Fusion General Ledger. if you plan to start transacting in Jan-11. Oracle Proprietary and Confidential.

Oracle Proprietary and Confidential. Oracle and/or its affiliates. Relevant Setup Tasks Financial reporting structures – Calendars 41 Copyright © 2011. All rights reserved. .

Oracle Proprietary and Confidential. . Oracle and/or its affiliates. Financial reporting structures Currencies 42 Copyright © 2011. All rights reserved.

Oracle and/or its affiliates. Oracle Proprietary and Confidential. All rights reserved. Feature Summary Financial reporting structures – Currencies Maintain your currencies and define daily rates to record and run cross-currency transactions and accounting processes • Enable predefined currencies or create new currencies to use across your financial applications • Maintain your conversion rate types to categorize the relationships between your currencies and daily rates • Define daily rates between your currencies to record transactions or run processes involving multiple currencies 43 Copyright © 2011. .

. Oracle Proprietary and Confidential. Oracle and/or its affiliates. All rights reserved. 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. . Oracle Proprietary and Confidential. but you can define new rate types to fit your business needs Rate Type Description Corporate Generally used for standard market rates throughout your organization Spot Generally used to perform conversion based on the rate on a specific date EMU Fixed Used to define rates between the EUR currency and the national EMU currencies User The daily rates for the User rate type will be provided during data entry • Enable cross rates if you want the system to automatically derive the daily rates for each pair of currencies in a set consisting of a pivot currency and one or more contra currencies • Select a default conversion rate type to be used to derive the default daily rate in a foreign currency transaction 45 Copyright © 2011. Implementation Concepts (2/3) Financial reporting structures – Currencies • Conversion rate types • Categorize the relationships between your currencies and daily rates using different conversion rate types • The rate types below are predefined in Fusion General Ledger. All rights reserved.

but different rate types provide each subledger the ability to convert transactions at different rates 46 Copyright © 2011. Oracle Proprietary and Confidential. Oracle and/or its affiliates. . All rights reserved. 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. Implementation Concepts (3/3) Financial reporting structures – Currencies • Daily Rates • A daily rate defines the exchange rate relationship between 2 currencies.

You may also use the user interface to update or delete existing daily rates. . All rights reserved. update or delete rates? daily rates. •Alternatively. 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. Oracle and/or its affiliates. Run the “Import and Calculate Daily Rates” process to import your rates into the daily rates table and ready them for use. Oracle Proprietary and Confidential. your enterprise may decide to use its own processing mechanism to upload rates directly to the daily rates interface table. 47 Copyright © 2011.

Oracle and/or its affiliates. Oracle Proprietary and Confidential. All rights reserved. Relevant Setup Tasks Financial reporting structures – Currencies 48 Copyright © 2011. .

All rights reserved. . Oracle and/or its affiliates. Oracle Proprietary and Confidential. Additional Resources • Oracle Fusion Enterprise Structures Implementation and Configuration Considerations • Oracle Fusion Financials Enterprise Structures Implementation and Configuration Considerations – Part 2 • Oracle Fusion General Ledger Implementation and Configuration Considerations 49 Copyright © 2011.