Oracle Fusion Financials Cloud Implementation Guide

Oracle
Financials Cloud
Getting Started with Your
Implementation
Release 9
Oracle Financials Cloud Getting Started with Your Implementation

Part Number E53190-01
Copyright 2011-2014, Oracle and/or its affiliates. All rights reserved.
Authors: Mary Kalway, Kathryn Wohnoutka, Reshma Shaik
This software and related documentation are provided under a license agreement containing restrictions on use and disclosure and are protected by
intellectual property laws. Except as expressly permitted in your license agreement or allowed by law, you may not use, copy, reproduce, translate, broadcast,
modify, license, transmit, distribute, exhibit, perform, publish, or display any part, in any form, or by any means. Reverse engineering, disassembly, or
decompilation of this software, unless required by law for interoperability, is prohibited.
The information contained herein is subject to change without notice and is not warranted to be error-free. If you find any errors, please report them to
us in writing.
If this is software or related documentation that is delivered to the U.S. Government or anyone licensing it on behalf of the U.S. Government, the following
notice is applicable:
U.S. GOVERNMENT END USERS: Oracle programs, including any operating system, integrated software, any programs installed on the hardware, and/
or documentation, delivered to U.S. Government end users are "commercial computer software" pursuant to the applicable Federal Acquisition Regulation
and agency-specific supplemental regulations. As such, use, duplication, disclosure, modification, and adaptation of the programs, including any operating
system, integrated software, any programs installed on the hardware, and/or documentation, shall be subject to license terms and license restrictions
applicable to the programs. No other rights are granted to the U.S. Government.
This software or hardware is developed for general use in a variety of information management applications. It is not developed or intended for use in
any inherently dangerous applications, including applications that may create a risk of personal injury. If you use this software or hardware in dangerous
applications, then you shall be responsible to take all appropriate fail-safe, backup, redundancy, and other measures to ensure its safe use. Oracle
Corporation and its affiliates disclaim any liability for any damages caused by use of this software or hardware in dangerous applications.
Oracle and Java are registered trademarks of Oracle Corporation and/or its affiliates. Other names may be trademarks of their respective owners.
Intel and Intel Xeon are trademarks or registered trademarks of Intel Corporation. All SPARC trademarks are used under license and are trademarks or
registered trademarks of SPARC International, Inc. AMD, Opteron, the AMD logo, and the AMD Opteron logo are trademarks or registered trademarks of
Advanced Micro Devices. UNIX is a registered trademark of The Open Group.
This software or hardware and documentation may provide access to or information on content, products and services from third parties. Oracle Corporation
and its affiliates are not responsible for and expressly disclaim all warranties of any kind with respect to third-party content, products, and services. Oracle
Corporation and its affiliates will not be responsible for any loss, costs, or damages incurred due to your access to or use of third-party content, products,
or services.
For information about Oracle's commitment to accessibility, visit the Oracle Accessibility Program website at http://www.oracle.com/pls/topic/lookup?
ctx=acc&id=docacc
Oracle customers have access to electronic support through My Oracle Support. For information, visit http://www.oracle.com/pls/topic/lookup?
ctx=acc&id=info or visit http://www.oracle.com/pls/topic/lookup?ctx=acc&id=trs if you are hearing impaired.
Oracle Financials Cloud
Getting Started with Your Implementation
Contents
Preface
Introducing Oracle Financials Cloud
Introduction to Implementing Oracle Financials Cloud: Overview

Oracle Financials Cloud: Overview
............................................................................................................................ 1
Working with Your System Integrator: Overview
............................................................................... 1
........................................................................................................ 5
Getting Started with Oracle Cloud
Purchasing and Activating Oracle Cloud Application Services: Highlights .................................................................. 6

Implementing Financials Security: Overview
General Ledger Security: Explained
Payables Security: Explained
.............................................................................................................. 7
........................................................................................................................ 10
.................................................................................................................................. 10
Other Financials Security Considerations: Explained
................................................................................................ 11
Oracle Cloud Application Services Security: Explained

Signing in and Accessing Setup Tasks: Procedure
............................................................................................ 11
................................................................................................. 13
Define Implementation Users Tasks: Points to Consider

Preparing the IT Security Manager Role: Procedure
Creating Implementation Users: Procedure
......................................................................................... 13
................................................................................................ 15
............................................................................................................. 16
Creating Data Roles for Implementation Users: Procedure
...................................................................................... 18
Implementing Oracle Financials Cloud

Manage Application Implementation: Overview
22
....................................................................................................... 22
Getting Started with an Implementation: Overview
.................................................................................................. 23
Define Financials Configuration for Rapid Implementation: Overview ........................................................................ 25

Creating an Oracle Fusion Financials Rapid Implementation Project: Worked Example ............................................ 26
Set Up Geographies
............................................................................................................................................... 27
Implementing Enterprise Structures: Procedure

Implementing General Ledger: Procedure
............................................................................................................... 34
Implementing Cash Management: Procedure

Implementing Tax: Procedure
....................................................................................................... 31
.......................................................................................................... 40
................................................................................................................................. 40
Implementing Payables and Payments: Procedure

Implementing Assets: Procedure
.................................................................................................. 43
............................................................................................................................. 46
Implementing Expenses: Procedure
........................................................................................................................ 48
Implementing Receivables and Payments: Procedure
Intercompany Balancing Rules: Explained
............................................................................................................... 53
Intercompany Balancing Rules: Examples
............................................................................................................... 54
Defining Financial Data Security

Define General Ledger Security: Explained
60
.............................................................................................................. 60
Data Access Set Security: Overview
....................................................................................................................... 61
Data Access Set Security: Examples
...................................................................................................................... 62
Segment Value Security: Examples
......................................................................................................................... 63
Enabling Security on a Chart of Accounts: Example
............................................................................................. 49
Configuring Financial Reporting

Financial Reporting Center: How It Works
Define Financial Reporting Center
............................................................................................... 64
67
.............................................................................................................. 67
........................................................................................................................... 68
Configure Smart View Client for Users
.................................................................................................................... 71
Configure Financial Reporting Studio Client for Users
............................................................................................. 74
Define Essbase Database Connections in Workspace
............................................................................................ 75
Create Financial Statements: Explained
.................................................................................................................. 77
Uploading Data for Oracle Financials Cloud
95
Create Chart of Accounts, Ledger, Legal Entities, and Business Units in Spreadsheets: Explained .......................... 95
Create Chart of Accounts, Ledger, Legal Entities, and Business Units in Spreadsheets: How They Are Processed ... 98
Create Hierarchies in a Spreadsheet: Example
GL Cross-Validation Rules: Overview
..................................................................................................... 107
.................................................................................................................... 108
Creating a Cross-Validation Rule: Example
........................................................................................................... 109
Cash Management Rapid Implementation: Overview

Tax Configuration Workbook: Explained
............................................................................................. 110
................................................................................................................ 111
Creating Tax Setup Using the Tax Configuration Workbook: Worked Example ...................................................... 112
Budget Uploads
.................................................................................................................................................... 113
Introduction to External Data Integration
120
Integration with Financial External Systems: Points to Consider
............................................................................ 120
Preface
Preface
This Preface introduces information sources available to help you use Oracle Applications.
Oracle Applications Help

Use the help icon to access Oracle Applications Help in the application.
Note
If you don't see any help icons on your page, click the Show Help button in the global area. Not all pages have
help icons.
You can also access Oracle Applications Help at https://fusionhelp.oracle.com/.
Oracle Applications Guides

To find other guides for Oracle Applications, go to:
Oracle Applications Help, and select Documentation Library from the Navigator menu.
Oracle Help Center at http://docs.oracle.com/
Other Information Sources

My Oracle Support
Oracle customers have access to electronic support through My Oracle Support. For information, visit http://
www.oracle.com/pls/topic/lookup?ctx=acc&id=info or visit http://www.oracle.com/pls/topic/lookup?ctx=acc&id=trs if you
are hearing impaired.
Oracle Enterprise Repository for Oracle Fusion Applications

Oracle Enterprise Repository for Oracle Fusion Applications (http://fusionappsoer.oracle.com) provides details on assets (such
as services, integration tables, and composites) to help you manage the lifecycle of your software.
Documentation Accessibility
For information about Oracle's commitment to accessibility, visit the Oracle Accessibility Program website at http://
www.oracle.com/pls/topic/lookup?ctx=acc&id=docacc.
Comments and Suggestions

Please give us feedback about Oracle Applications Help and guides! - Send e-mail to:
oracle_fusion_applications_help_ww_grp@oracle.com. - Click your user name in the global area of Oracle Applications Help,
and select Send Feedback to Oracle.
Chapter 1
Introduction to Implementing Oracle Financials

Cloud: Overview
This document provides a high level introduction to Oracle Financials Cloud.
Note
This guide covers the basic requirements used to create an implementation project. The tasks presented in this
document are intended for a quick introduction or pilot implementation. This document does not include all set up
and security tasks that are appropriate for a complete implementation.
The rapid implementation setups for Financials include implementing:
Users
Enterprise Structures
Bank, Branches, and Bank Accounts
Tax
Ledgers
Business Units
Financial Reporting
Payables and Payments
Assets
Expense Reporting
Receivables and Payments
Note
References to related help accompany each of the steps. The help and additional information is available from:
Oracle Financials Cloud Implementing Financials guide.
Oracle Cloud Learning Center.
Oracle Fusion Applications Help embedded in the applications.
Oracle Financials Cloud: Overview

Oracle Financials Cloud delivers a complete solution that includes:
General Ledger
Chapter 1
Payables
Receivables
Payments
Cash Management
Tax
Expenses
Assets
Use these applications with their integrated social networking tools, business intelligence, compliance reporting, and mobile
data access to facilitate:
Financial accounting
Transaction processing
Payment delivery
Cash reconciliation
Employee expense processing
Asset management
Chapter 1
Access data through pages that contain:

Navigation tools in the global area at the top of the page.
Task and search panes in the regional area on the left side of the page.
Chapter 1
Analytics and tools panes in the contextual area at the right side of the page.
A transactions area where most work is done, in the center of the page.
From the pages within the applications, access:

Embedded analytics that enable actionable insight by providing access to information or data that helps complete
a transaction or analysis data.
Interactive dashboards that provide:
Information summaries providing a high level overview.
Chapter 1
Information monitoring and drill down capability.
Transaction information that is central to one or more business processes.
Business intelligence content that is complementary to one or more business processes.

Note
The main page within Oracle Financials Cloud is the Oracle Fusion Home, which is a collection of
dashboards. and opens by default to the Welcome dashboard. The other dashboards appear as tabs
across the top of the page.
Real-time reporting that allows:
Viewing relevant reports and analytics for each individual work area.
Exploring predefined analyses.
Creating and editing of analyses from the Reports and Analytics pane or work area.
Optionally, access to the Oracle Business Intelligence (BI) Enterprise Edition through the Reports and
Analytics pane. New objects and changes to existing objects that you make in Oracle BI Enterprise Edition are
reflected and available from Oracle Financials Cloud.
Viewing and running financial reports from the Financial Reporting Center which is a single point of entry for
general ledger financial reporting functions. The Financial Reporting Center includes:
Tools to create and format financial report including Financial Reporting Studio and Workspace.
Live and interactive financial reports with multiple output options including HTML, PDF, Excel, or Excel in
Query Ready mode using Smart View Enabled formats.
Drill down to underlying journals and subledger transactions with the Account Inspector.
Multiple reporting methods for ad-hoc analysis, efficient monitoring, and tracking of key account balances in
real-time with the Account Monitor.
Working with Your System Integrator: Overview

After you determine the applications that you want to implement, complete any steps that you determined are needed for
your implementation plan in Oracle Fusion Global Human Resources first to ensure that dependencies with the Oracle Fusion
Financials are met.
If needed, see: Oracle Cloud Getting Started with Oracle HCM Cloud
Your system integrator uses his or her implementation expertise to help you with a smooth transition to the Oracle Financials
Cloud. They also use the Rapid Start procedures to help you achieve a successful implementation in the shortest time
possible.
Chapter 2
Purchasing and Activating Oracle Cloud Application

Services: Highlights
Purchase and activate Oracle Cloud Application Services from the Oracle Cloud web site, https://cloud.oracle.com.
The whole process involves:
Requesting and activating trial subscriptions.
Purchasing and activating your services.
Verifying that the services are activated, monitoring the services, and performing other administrative tasks.
Purchasing and activating any Oracle Cloud service is described in the Oracle Cloud Getting Started with Oracle Cloud
document. All of the following references in this section point to that document.
Note
Not everything in that document is relevant to Oracle Cloud Application Services, for example details about Oracle
Java Cloud Service and Oracle Database Cloud Service.
Terminology and User Roles

Before you proceed, you should understand terms that are used in documentation about Oracle Cloud.
See: Oracle Cloud Terminology
You should also be familiar with roles for users of the Oracle Cloud web site or of the actual service.
See: Oracle Cloud User Roles and Privileges
Requesting and Activating Trial Subscriptions

Oracle Cloud Application Services are available through free trial subscriptions. After you request trial subscriptions,
you activate, monitor, and manage the services for use before purchase.
See: Overview of Getting a Trial Subscription
Purchasing and Activating Services

Your buyer or an Oracle sales representative orders a cloud service and specifies information about the account
administrator during the ordering process.
See: Ordering an Oracle Cloud Service
The account administrator receives an e-mail with a link to activate the service. As part of activation, the account
administrator provides information about the administrator who performs the functions of both the service
administrator and the identity domain administrator.
See: Activating Your Order for an Oracle Cloud Service
Chapter 2
Next Steps
The administrator who was identified during the activation process:
Verifies that the service is activated.

See: Verifying a Service Is Up and Running
Manages and monitors the service.

See: Using My Account to Activate and Monitor Oracle Cloud Services
See: Using My Services to Monitor and Administer Oracle Cloud Services
Optionally creates initial administrator and implementation users before enterprise structures setup.
See: Define Implementation Users Tasks: Points to Consider
Alternatively, the administrator sets up enterprise structures and then creates service users, including
functional implementors.
Functional implementors perform configuration and setup steps.

Developers can add custom features and extend the application.
Implementing Financials Security: Overview

In Oracle Fusion Applications, roles provide access to functions and data. The roles assigned to a user determine what the
user can see and do. Access is not granted to users directly.
Oracle Financials Clouds predefines common job roles such as Accounts Payable Manager and General Accounting
Manager. You can use these roles, modify them, or create new job roles as needed. A user can be assigned more than one
role, so don't define a role that includes all the accesses needed for every user.
Users and Roles
Chapter 2
The following table is an example of key job responsibilities and roles that are assigned in Oracle Fusion Financials to provide
the necessary system capabilities.
Key Duties
Chief financial officer duties including:
Monitors financial performance.
Roles Assigned
General Accounting Manager - All Access
Line Manager
Provides financial results to outside stake holders

Analyses variances across the enterprise
Controller duties including:
Provides status of financial condition by
interpreting, and reporting financial data
Achieves budget objectives
Prepares special reports by analyzing and
summarizing information and trends
Manages the general accounting functions

including:
Journal entry review and approval
Reconciliation
Account balance analysis
Financial reporting
General Accounting Manager

Tax Manager
Cash Manager
Line Manager

Financial Application Administrator
Line Manager
Manages billing and collections

Maintains setup and reference data on an ongoing
basis
Oversees accounts payable operations and is

responsible for:
Creating payments
Managing override exceptions
Monitoring and analyzing accounts payable

balances
Accounts Payable Manager

Asset Accounting Manager
Cash Manager
Line Manager
Chapter 2

Key Duties
Submitting tax and withholding reports to

meet regulatory requirements
Ensuring that company payment policies are

followed

Roles Assigned
Monitors and manages assets

Manages payroll
Reconciles bank statements
Maintains setup and reference data on an ongoing
basis
Financial reporting
Financial Analyst - Read Only
General accounting
General Accountant
Journal entries
Asset Accountant
Processes inbound invoices
Accounts Payable Specialist
Matches invoices to purchase orders and receipts
Configures the Oracle Fusion Applications system
System Administrator
Configures and performs ongoing maintenance of

their system security
IT Security Manager
Integrates existing systems
Responsible for profit and loss in their respective

businesses
Performs initial implementation

Procurement Application Administrator
Financial Analyst - Read Only: Access further restricted
to their respective business areas using data access
security based on the chart of accounts structure
Application Implementation Manager

Application Implementation Consultant
Creating Users and Assigning Roles

Create and sync your user accounts with their employee records by running the Run User and Roles
Synchronization Process task.
Chapter 2
Proceed to assign the appropriate roles to users.

Use role provisioning rules to automatically assign commonly used roles such as Employee and Line Manager.
Manually assign roles that are assigned to a limited number of users.
Note
For a listing of all predefined job roles in Oracle Fusion Financials and their intended purposes, please refer to the
Security Reference Manual.
General Ledger Security: Explained

Oracle Fusion General Ledger includes the following predefined roles:
General Accountant
Financial Analyst
For each of these predefined roles, the included duties grant access to application functions and data that corresponds
to their responsibilities. For example, the General Accounting Manager role grants comprehensive access to all general
ledger functions to both the Chief Financial Officer and the Controller.
General Ledger uses data roles to provide access to specific ledgers. Access is granted for individual ledgers or for a set of
ledgers. You decide whether each role provides read-only access or read and write access. For example, grant the ability to
create journal entries and modify existing journal entries or the ability to only view journals.
General Ledger automatically creates the data roles that provide single ledger access. You then manually set up the
consolidated accesses to other ledgers.
Payables Security: Explained

In Oracle Fusion Payables you secure access to invoices and payments by business unit. You can access invoices and
payments for viewing or processing only in the business units to which you have permission. The permission must be
explicitly granted to each user using data roles.
Payables is integrated to the document repository for processing scanned invoices. Edit access to the document repository is
granted to the following predefined roles:
Accounts Payable Manager
Accounts Payable Specialist
Accounts Payable Supervisor
The following predefined roles have view-only access to the document repository:
Cost Accountant
Project Accountant
10
Chapter 2
Other Financials Security Considerations: Explained

Common functionality that is not job specific, such as creating expense reports and purchase requisitions, are granted to
abstract roles like Employee, Line Manager, and Purchase Requestor.
Oracle Financials Cloud includes the following roles that are designed for initial implementation and the ongoing management
of setup and reference data:
Application Implementation Manager: Used to manage implementation projects and assign implementation
tasks.
Application Implementation Consultant: Used to access all setup tasks.
Note
For ongoing management of setup and reference data, the Financial Application Administrator, a predefined
administrator role, provides access to all financial setup tasks.
Segregation of Duties Considerations
Segregation of duties (SOD) separates activities such as approving, recording, processing, and reconciling results so you can
more easily prevent or detect unintentional errors and willful fraud.
Oracle Financials Cloud includes roles that have been defined with a knowledge of a set of SOD policies that are included in
the Oracle Cloud Access Controls Governor product. The job roles are based on those commonly defined in business and
the duty definitions are defined using the Oracle Cloud SOD policies.
For example, the privilege Create Payments is incompatible with the privilege Approve Invoice. The predefined Accounts
Payable Manager role has the privileges of Force Approve Invoices and Create Payments.
When you assess and balance the cost of duty segregation against reduction of risk, you may determine that the Accounts
Payable Manager role is not allowed to perform force approve invoices and remove this privilege.
Data Security Considerations
Use data security to restrict access to journal entries and balances based on certain values in the chart of accounts,
such as specific companies and cost center values, to individual roles.
Control data security to protect your organization as it grows and hires additional staff members, each responsible
for only a portion of the business activities.
For more information, see:
Oracle Enterprise Repository
Oracle Fusion Applications Financials Security Reference Manual
Oracle Cloud Application Services Security: Explained

Security in Oracle Cloud Application Services is the same as for any other kind of Oracle Fusion Applications deployment.
However, the experience of getting started and managing initial users is slightly different.
Aspects of security that are specific to Oracle Cloud Application Services involve the following:
Initial environment and sign in
11
Chapter 2
Initial user administration

Infrastructure
Aspects of security that are equivalent for any type of deployment involve the following:
Ongoing user administration
Managing roles and security policies
Initial Environment and Sign In

Oracle provides your account administrator with a link to activate and access the service. Oracle creates one initial user for
you. Sign in as the initial user to create other users, including the service administrator, the identity domain administrator, and
users who must perform implementation tasks.
Initial User Administration

If your enterprise requires additional implementation users for security administration before setting up enterprise structures,
the service administrator performs the Define Implementation Users tasks.
Defining implementation users can include these tasks:
Creating users
Creating data roles
Provisioning users with roles
The service administrator can also perform delegated administration tasks such as resetting passwords of other
administrators.
Ongoing User Administration

After you set up basic enterprise structures, create and manage users by using the hiring processes in Human Capital
Management (HCM) or performing the Manage Users task.
User management includes provisioning users with roles that provide access to functions and data in Oracle Cloud
Application Services. You can also set up rules that automate role provisioning according to your criteria. You set up these
rules through the Manage HCM Role Provisioning Rules task.
Managing Roles and Security Policies

The Oracle Fusion Applications security reference implementation provides predefined roles and policies, as well as data role
templates that generate data roles for non-HCM users based on your enterprise structures setup.
You can view the security reference implementation using the following resources:
User interfaces where you perform application security tasks
Security reference manuals for each offering
Oracle Enterprise Repository for Oracle Fusion Applications
To extend the security reference implementation with roles and policy modifications needed by your enterprise, use tasks
such as:
Manage Job Roles
Manage Role Templates
12
Chapter 2
Manage Data Security Policies

Manage Duties
Infrastructure
Your Oracle Cloud Application Services integrate with identity management domains. For information about using your
existing local users in an Oracle Applications Cloud service with Federated Single Sign-on (SSO), see Configuring Identity
Synchronization in Oracle Fusion Cloud Services [ID 1513123.1] and Fusion Applications Technology: Master Note on Fusion
Federation [Doc ID 1484345.1] on My Oracle Support, https://support.oracle.com.
The following optional security features are currently not available in Oracle Cloud Application Services.
Oracle Database Advanced Security
Oracle Data Masking
Signing in and Accessing Setup Tasks: Procedure

Oracle provides one user account and password for signing in to Oracle Applications Cloud services. This is the service
administrator account.
Before your enterprise has generated task lists, implementors and application users can access setup tasks by searching for
the task in the Setup and Maintenance Overview page. After task lists have been generated, users can access their assigned
tasks or the task lists for the offerings included in their project. For example, the Define Common Applications Configuration
task list for each offering includes the Define Implementation Users tasks.
The following procedure assumes that the administrator has not yet configured an offering and set up task lists.
1. Access your Oracle Cloud Application Services by using the universal resource locator (URL) link provided by
Oracle.
2. Sign in using the administrator user account and password provided by Oracle based on your activation request.
Initial sign-in prompts you to reset your password.
3. Access tasks as follows:
a. Go to Navigator > more... > Tools > Setup and Maintenance.
b. On the Overview page, click the All Tasks tab.
c. Search for the task by entering the name in the Search field.
d. Click Search.
e. In the search results, perform the task by clicking its Go to Task icon.
Define Implementation Users Tasks: Points to

Consider
The Define Implementation Users task list includes tasks for creating users, optionally creating data roles, and provisioning
users with roles before you have set up enterprise structures. After you have set up enterprise structures, do not use the
Define Implementation Users tasks for creating any users that you need a Human Capital Management (HCM) record for.
13
Chapter 2
Important
All Oracle Fusion Applications offerings include HCM Foundation. Performing the Manage Users task to create
users always creates an associated HCM record even if you are not implementing full HCM.
Creating Implementation Users

The users you create using the Create Implementation Users task are created in Oracle Identity Manager.
Use Create Implementation Users task under the following circumstances:
Before setting up enterprise structures if your enterprise needs additional users such as a dedicated security
administrator or implementation users for setting up enterprise structures
If you require user accounts that must not have an associated HCM record
The service administrator user that is provided by Oracle for generating task lists and setting up enterprise structures is a user
created using this task. The service administrator user is provisioned with the following roles:
IT Security Manager
Application Implementation Consultant
Application Diagnostics Administrator
Optionally Creating Data Roles for Implementation Users

The predefined Application Implementation Consultant role may be too broad for your security needs. As an alternative to
provisioning an implementation user with the Application Implementation Consultant role to access all enterprise structures,
you may need implementation users with access restricted to enterprise structures for specific products. Use the Create
Data Roles for Implementation Users task to create a data role based on a job role with less broad access, such as the HCM
Application Administrator job role.
For example, you can create a View All data role, such as a View All Financials Application Administrator data role. This data
role is based on the Financials Application Administrator job role and combines the entitlements that have been granted to
that role with unrestricted access to data on the secured objects that the role is authorized to access.
Provisioning Roles to Implementation Users

The Create Implementation Users task includes provisioning the user you have created with predefined roles.
For example, assign a role to the implementation user that provides the access necessary for setting up the enterprise.
Depending on need, provision the implementation user with the predefined Applications Implementation Consultant role.
Caution
The Application Implementation Consultant has broad access. It is a very useful role for experimentation or setting
up a pilot environment, but may not be suitable for implementation users in a full implementation project or for
application users.
After basic enterprise structures have been set up you can provision additional users with product family-specific
administrator data roles, such as a data role based on the predefined Financials Applications Administrator.
If you create additional roles, such as optionally creating data roles before enterprise structures setup, provision those roles to
existing implementation users by performing the Provision Roles to Implementation Users task.
14
Chapter 2
Preparing the IT Security Manager Role: Procedure

To perform the Define Implementation Users tasks, the IT Security Manager job role must be given user and role management
access by adding the job role as a member of the Identity User Administrators role and Role Administrators role in Oracle
Identity Manager.
Important
The IT Security Manager role comes predefined in Oracle Applications Cloud. This procedure is necessary only for
on premise implementations.
Warning
This expansion of the IT Security Manager job role can pose a security risk. If you are averse to this type of risk,
you can skip defining implementation users before enterprise structure setup. Instead, use the administrator user
to set up enterprise structures and then create service users as Human Capital Management (HCM) records.
1. While signed into Oracle Identity Manager as the administrator user, click the Administration link in the upper right
of the Oracle Identity Manager.
This accesses the Welcome to Identity Manager Delegated Administration menu.
2. In the Roles list of tasks, click Advanced Search - Roles.
3. Search for the Identity Users Administrators role by entering the role name in Display Name and clicking Search.
4. In the Search Results, click the role's Display Name.
5. On the Hierarchy tab, select Inherits From and click Add.
6. In the Add Parent Role to: IDENTITY USER ADMINISTRATORS window, select the role category: Common - Job
Roles.
7. Click the arrow icon to show the list of available roles. Select IT Security Manager and move it to the Roles to Add
list.
8. Click Save.
9. Search for the Role Administrators role, and repeat steps 3 to 8 to add that role to the IT Security Manager role's
role inheritance.
10. Assign the IT Security Manager role to the Xellerate Users organization.
a. In the Welcome to Identity Manager Delegated Administration menu (see step 1, above), in the Organizations
list of tasks, click Advanced Search - Organizations.
b. Search for the Xellerate Users organization by entering Xellerate Users in Display Name and clicking Search.
c. In the Search Results, click the organization's Display Name.
d. On the Xellerate Users page, click the Administrative Roles link in the row of links above the Xellerate
Users.
e. In the Organization Detail > Administrative Roles subwindow, click Assign.
15
Chapter 2
f. In Filter By Role Name of the Details window, enter:

*IT_SECURITY_MANAGER*
g. Click Find.
h. Enable Read, Write, Delete, and Assign.
i. Click Assign.
j. Click Confirm.
Note
This changed definition of the IT Security Manager job role is available in the identity store, but not available in
Human Capital Management (HCM) unless the administrator performs the Run User and Roles Synchronization
Process task.
Creating Implementation Users: Procedure

Perform the Create Implementation Users task to create user accounts in Oracle Identity Manager if your enterprise requires
user accounts that are not associated with records in Human Capital Management (HCM). These users principally set up
enterprise structures and administer security.
Aspects of defining implementation users in Oracle Identity Manager involve:
Initial Sign In and Accessing Tasks
Creating implementation users
Provisioning roles to implementation users
Defining Implementation Users after Enterprise Structures Setup
Note
The following tasks assume that the administrator has not yet configured an offering or set up task lists.
Creating Implementation Users

This procedure creates additional users for security administration and setting up enterprise structures. If the single
administrator provided by Oracle is sufficient for configuring offerings, generating task lists, and setting up enterprise
structures, you can skip this task.
1. Sign in as the administrator user.
Warning
The administrator user provided by Oracle is provisioned with the IT Security Manager job role. Be sure
this user has signed into Oracle Identity Manager and prepared the IT Security Manager job role to
include the necessary user and role management entitlement.
16
Chapter 2
2. Access the Create Implementation Users task.

3. In Oracle Identity Manager click Create User.
4. Provide the following attributes. The example values show creating a dedicated IT security manager.
Attribute
Value
Example
Last name
<any valid string>
Smith
Organization
Xellerate Users
N/A
User Type
Non Worker
N/A
User login
<any valid string>
MY_ SECURITY_ ADMIN
Password
<any valid string>
SeKur1TyPa$$w0Rd
a. In the Organization field, enter Xellerate Users. Or click the Search icon, then in the Organization Search sub
window, click the Search arrow without entering anything in the Search field, select the Xellerate Users
organization in the search results, and click Add.
b. Set the User Type. For example, Non Worker.
c. Enter the desired user login and password.
For details, see the Creating Users section in the Oracle Fusion Middleware User's Guide for Oracle Identity
Manager.
5. Click Save.
Provisioning Roles to Implementation Users

Creating an implementation user includes provisioning the user with roles. Review the available predefined roles by either
viewing them in the user interfaces where security tasks are performed or in the security reference implementation manual for
each Oracle Fusion Applications offering.
1. On the Roles tab in the user creation page, click Assign.
2. In the Add Role window, search for a role by entering the initial letters of the role name in the Display Name Begins
With field. For example, enter IT for the IT Security Manager job role or App for the Application Implementation
Consultant job role.
Important
If you are provisioning the IT Security Manager job role for defining implementation users before
enterprise structures setup, be sure the IT Security Manager job role has been prepared for user and role
management in Oracle Identity Manager.
17
Chapter 2
3. Click Search.
4. Select the desired role from the search results. For example, IT Security Manager or Application Implementation
Consultant.
5. Click Add.
6. Repeat steps 2-5 to add other roles.
7. Click Assign.
8. Close the User page.
If you are creating an application implementation consultant user for setting up enterprise structures and need to limit their
access to data, create data roles using the Create Data Roles for Implementation Users task and then provision those roles to
the user you have created by performing the Provision Roles to Implementation Users task.
Defining Users after Enterprise Structures Setup

Do not use the Create Implementation Users task after your enterprise has been set up unless you need users specifically
defined in Oracle Identity Manager only and without an associated HCM record.
Once you have basic enterprise structures set up, such as a legal entity and business unit, you can create implementation
users by the following means:
Manage Users task
Hiring processes if you are implementing Human Capital Management (HCM)
For more information about the Manage Users task, see the Define Security chapter in the Oracle Fusion Applications
Common Implementation Guide
Creating Data Roles for Implementation Users:

Procedure
Implementation users who are created using the Create Implementation Users task for setting up product-specific enterprise
structures may need to be provisioned with roles with restricted data access. See the Oracle Fusion Applications Security
Reference Manuals for information about the available predefined Oracle Fusion Applications roles.
Aspects of performing the Create Data Roles for Implementation Users task involve:
Creating View All data roles
Creating reference data sharing data roles
Provision the data roles to implementation users
Note
The following tasks assume that the administrator has not yet configured an offering or set up task lists. If basic
enterprise structures have been set up, provision automatically generated data roles to users.
18
Chapter 2
Creating a View All Data Role

You create a View All data role, such as a View All Financials Application Administrator data role, so that when you provision
this role to an implementation user using the Provision Roles to Implementation Users, the user's access is restricted to
financials data on the secured objects that the role is authorized to access.
1. Sign into Oracle Fusion Applications.
2. Access the Create Data Roles for Implementation Users from the Setup and Maintenance Overview page.
3. In the Manage HCM Data Roles page, click the Create Data Role icon. For details about Manage HCM Data Roles
tasks, see the Oracle Fusion Applications Workforce Deployment Implementation Guide.
4. Create a View All data role, such as a "HCM Application Administrator View All" data role with the Human Capital
Management Application Administrator as the base job role. In Security Criteria, make the following selections:
a. Grant access to all data for all the security profiles by selecting View All for each field.
b. Grant access for Person and Public Person by selecting View All People.
c. Click Review.
d. Verify the data is correct.
e. Click Submit.
5. Provision the implementation user who sets up HCM with this View All data role, such as the HCM Application
Administrator View All data role, by performing the Provision Roles to Implementation Users task.
Important
Once an implementation user with a View All data role has completed HCM setup, it may be prudent to revoke
the role by performing the Revoke Data Role from Implementation Users task. Provision the View All data role only
when HCM setup changes are necessary.
Creating a Reference Data Sharing Data Role

Create a reference data sharing (Set ID) data role to secure data reference sets in HCM.
1. Access the Manage Role Templates task.
2. In the Authorization Policy Manager, click Role Templates.
3. Search for role template names starting with the data stripe.
For example, search Hcm (case sensitive) to select the templates you need to generate data roles, such as the
HcmCmpSetId template for generating a data role that gives access to compensation data.
4. In each template:
a. Open the template.
b. Click Generate Roles.
c. Open the Policies tab.
19
Chapter 2
d. Below the Data Security Policies, open the Actions tab.

e. Deselect the Manage Assignment Grade option.
f. Click Apply.
g. Open the Summary tab.
h. Under Generated Roles, expand the Valid Roles section.
The list of roles includes sets of COMMON and ENTERPRISE data roles for each job and includes any data
roles for sets that are created by the Manage Reference Data Sets task.
i. Highlight each reference data set data role template and click Refresh Role.
j. Re-enable the Manage Assignment Grade option using steps 4 c - 4 e, above.
k. Under Generated Roles, expand the Valid Roles section, highlight each reference data set data role template,
and click Refresh Role to refresh the data security policies.
5. For the reference data set data role templates, verify that data security policies exist and are properly created for
each valid data reference set.
6. In Authorization Policy Manager, on the Home tab, in the Global section, search for external roles containing
COMMON.
a. Select an HCM-related row in the search results.
b. Select Open Role.
c. View the details of the corresponding COMMON reference data set external role.
d. Select Find Global Policies.
e. Validate that row(s) exist in the Data Security Policies table for the respective COMMON set. If not, refresh
roles again using the above steps.
7. Repeat steps 6 a - 6 e above, for ENTERPRISE and any External Role sets you have created.
Provision Implementation Users with Data Roles

Provision the implementation user who sets up HCM with reference data set data roles by performing the Provision Roles to
Implementation Users task. The steps for this task are the same as provisioning roles as part of the Create Implementation
Users task.
Note
If the scheduled Run User and Roles Synchronization Process has not run, the data roles you created may not be
available for selection on the Roles tab of the User Creation page in Oracle Identity Manager.
The user provisioned with the data roles you created can now proceed with enterprise structures setup.
1. Access the Provision Roles to Implementation Users task from the Setup and Maintenance Overview page.
2. In Oracle Identity Manager, select Advanced Search - Users.
20
Chapter 2
3. On the Users page, search for the user login of the user to whom you want to provision the View All and Set ID data
roles.
4. Select the user by opening the Display Name link.
5. Open the Roles tab.
6. Click Assign and select all applicable rows containing the data roles you want to provision the user with. If the
scheduled Run User and Roles Synchronization Process has not run, the data roles may not be available for
selection.
7. Click Assign again.
8. The user provisioned with the predefined roles or the data roles you created can now proceed with enterprise
structures setup.
Related Topics
Creating an HCM Data Role: Worked Example
Synchronization of User and Role Information with Oracle Identity Management: How It's Processed
21
Chapter 3
Manage Application Implementation: Overview

The Manage Applications Implementation business process enables rapid and efficient planning, configuration,
implementation, deployment, and ongoing maintenance of Oracle Fusion applications through self-service administration.
The Setup and Maintenance work area offers you the following benefits:
Prepackaged Lists of Implementation Tasks
Task lists can be easily configured and extended to better fit with business requirements. Auto-generated, sequential
task lists include prerequisites and address dependencies to give full visibility to end-to-end setup requirements of
Oracle Fusion applications.
Rapid Start
Specific implementations can become templates to facilitate reuse and rapid-start for comparable Oracle Fusion
applications across many instances.
Comprehensive Reporting
A set of built-in reports helps to analyze, validate and audit configurations, implementations, and setup data of
Oracle Fusion applications.
With Oracle Fusion Functional Setup Manager you can:
Learn about and analyze implementation requirements.
Configure Oracle Fusion applications to match your business needs.
Achieve complete visibility to setup requirements through guided, sequential task lists downloadable into Excel for
project planning.
Enter setup data through easy-to-use user interfaces available directly from the task lists.
Export and import data from one instance to another for rapid setup.
Validate setup by reviewing setup data reports.
Implement all Oracle Fusion applications through a standard and consistent process.
The following documentation resources are available for learning how to configure Oracle Fusion Applications.
Functional Setup Manager Developer's Guide
Common Implementation Guide
Customer Data Management Implementation Guide
Enterprise Contracts Implementation Guide
Marketing Implementation Guide
22
Chapter 3
Sales Implementation Guide

Fusion Accounting Hub Implementation Guide
Financials Implementation Guide
Compensation Management Implementation Guide
Workforce Deployment Implementation Guide
Workforce Development Implementation Guide
Incentive Compensation Implementation Guide
Procurement Implementation Guide
Project Execution Management Implementation Guide
Project Financial Management Implementation Guide
Getting Started with an Implementation: Overview

To start an Oracle Fusion Applications implementation, you must set up one or more initial users using the super user
that was created during installation and provisioning of the Oracle Fusion Applications environment, or using the initial
administrator user provided by Oracle for Oracle Cloud implementations. Because Oracle Fusion Applications is secure as
delivered, the process of enabling the necessary setup access for initial users requires the following steps when getting
started with an implementation:
1. If you are not starting an Oracle Cloud implementation, sign into Oracle Identity Manager (OIM) as the OIM
Administration users and provision the IT Security Manager job role with roles for user and role management.
This enables the super user account, which is provisioned with the IT Security Manager job role, to create
implementation users.
2. For starting all implementations, sign in as the user with initial access: either the Oracle Fusion Applications
installation super user or the initial Oracle Cloud administrator user.
3. Select an offering to implement, and generate the setup tasks needed to implement the offering.
4. Perform the following security tasks:
a. Synchronize users and roles in the Lightweight Directory Access Protocol (LDAP) store with HCM user
management by using the Run User and Roles Synchronization Process task.
b. Create an IT security manager user by using the Create Implementation Users task.
c. Provision the IT security manager with the IT Security Manager role by using the Provision Roles to
Implementation Users task.
5. As the newly created IT security manager user, sign in to Oracle Fusion Applications and set up at least one
implementation user for setting up enterprise structures.
a. Create an implementation user by using the Create Implementation Users task.
b. Provision the implementation user with the Application Implementation Manager job role or the Application
Implementation Consultant job role by using the Provision Roles to Implementation Users task. The
23
Chapter 3
Application Implementation Consultant job role inherits from all product-specific application administrators
and entitles the necessary View All access to all secured objects.
c. Optionally, create a data role for an implementation user who needs only the limited access of a productspecific Application Administrator by using the Create Data Role for Implementation Users. Then assign the
resulting data role to the implementation user by using the Provision Roles to Implementation Users task.
The figure shows the task flow from provisioning the IT Security Manager job role with the user and role management
entitlement to creating and provisioning implementation users for enterprise setup.
Related Topics
Initial Security Administration: Critical Choices
User and Role Synchronization: Explained
24
Chapter 3
Enterprise Structures: Overview
Define Financials Configuration for Rapid

Implementation: Overview
Use the Define Financials Configuration for Rapid Implementation task list to streamline your setup configuration to focus only
on the critical setup steps. The rapid implementation task list minimizes the time needed for you to complete your key setups
and enable the day-to-day use of Oracle Fusion Financials.
The rapid implementation task list includes tasks that are:
Critical setup tasks for initial setup.
Setup steps that are required by most users.
To create an implementation project that includes the Define Financials Configuration for Rapid Implementation task list, use
the Manage Implementation Projects page in the Setup and Maintenance work area. The application implementation manager
can customize the task list and assign and track each task.
Note
You are not restricted to only the setup configuration in the rapid implementation task list. You can manually add
the standard Financials offering task lists and tasks to your rapid implementation project to change and update
your setup.
Task Lists
The Define Financials Configuration for Rapid Implementation task list contains the following task lists. These task lists
incorporate setup tasks related to specific functional areas within your Oracle Fusion Financials implementation.
Task List
Description
Define Common Financials Configuration for Rapid

Implementation
Define the common configuration for Oracle Fusion

Financials rapid implementation, which includes
enterprise structures and banks setup.
Define Transaction Taxes for Rapid Implementation
Configure tax setup according to local and international

tax requirements.
Define Ledger Configuration for Rapid Implementation
Define the configuration for Oracle Fusion General

Ledger rapid implementation that includes general
ledger and intercompany.
Define Financial Reporting Center Configuration for

Rapid Implementation
Define the configuration for Financial Reporting Center

rapid implementation that includes setup for financial
reporting and integration with planning and financial
management applications.
25
Chapter 3
Task List
Description
Define Invoicing and Payments Configuration for Rapid

Implementation
Define invoicing and payments configuration for Oracle

Fusion Payables rapid implementation.
Define Expenses Configuration for Rapid Implementation
Define corporate expense policies and rules, expense

types, and expense report approval rules for Oracle
Fusion Expenses rapid implementation.
Define Fixed Assets Configuration for Rapid

Implementation
Define the configuration for Oracle Fusion Assets rapid

implementation.
Define Receivables Configuration for Rapid

Implementation
Define the configuration for Oracle Fusion Receivables

rapid implementation.
Define Financials Security Configuration for Rapid

Implementation
Define the configuration for user and data roles setup for
Oracle Fusion Financials rapid implementation.
Note
The Open First Period task is a required task and is also part of the Define Financials Configuration for Rapid
Implementation task list.
Configuring Rapid Implementation Tasks Lists

Based on the applications you are implementing, you can streamline your task lists even more. For example, when you are
only implementing:
Oracle Fusion Payables, Expenses, and Assets: Delete the Define Receivables Configuration for Rapid
Implementation task lists from your implementation project:
Oracle Fusion Receivables: Delete the following task lists from your implementation project:
Define Invoicing and Payments Configuration for Rapid Implementation

Define Expenses Configuration for Rapid Implementation
Define Fixed Assets Configuration for Rapid Implementation
Creating an Oracle Fusion Financials Rapid

Implementation Project: Worked Example
This example shows how to create an implementation project for the Oracle Fusion Financials rapid implementation task list.
The following table summarizes key decisions for this scenario:
26
Chapter 3
Decision to Consider
In This Example
What Oracle Fusion applications are included in this

implementation?
The Oracle Fusion applications being implemented are:

General Ledger
Financial Reporting Center
Payables
Receivables
Expenses
Assets
Cash Management
Tax
Are the setup requirements unique to this organization?
No
Can the rapid implementation task lists and tasks be

used for this implementation?
Yes
Creating the Implementation Project

1. Navigator > Setup and Maintenance > Manage Implementation Projects link.
2. Click Create in the Search Results table.
3. On the Create Implementation Project: Enter Basic Information page, enter Implementation ProjectFIN_Rapid_Implementation in the Name field.
4. Click in the Description field to automatically update the name in the description.
5. Click the Save and Open Project button.
6. On the Implementation Project: Implementation Project-FIN_Rapid_Implementation page, click Add in the Task
Lists and Tasks table.
7. On the Select and Add: Task Lists and Task dialog box, enter %Rapid Implementation% in the Name field.
Use wildcard characters if you do not know the exact name of the task list or task.
8. Search .
9. Select the Define Financials Configuration for Rapid Implementation row.
10. Done.
11. On the Implementation Project: Implementation Project-FIN_Rapid_Implementation page, expand the task list to see
the task lists and tasks associated with your implementation project.
12. Done.
Set Up Geographies
Setting up your geography structure correctly is critical to the proper running of Oracle Fusion applications. The geography
structure and data is shared across all applications. The geography structure is used both for third-party site and address
27
Chapter 3
information, and to group geographical regions into territories that share the same requirement, such as a tax zone. You need
at least one level under the country level, such as STATE or CITY, to trigger the processes that assign geography records to
users.
Create and manage geographies used for real-time address validation and tax calculation.
In the following steps, you define the country structure for the United States and adding the state of California and the county
of Alameda to the country hierarchy.
Geography Structure
In the Manage Geographies page, search for United States and click the Structure Defined button to define the country
structure for the United States.
The Manage Geography Structure page allows you to define the geography structure of a country. You can either copy an
existing country structure or create a new country structure. Alternatively, you can use the Manage File Import Activities
task to import geography structure using a csv or xml file.
1.
2.
3.
4.
5.
6.
7.
8.
9.
10.
11.
12.
13.
14.
Click the Create button to create a new country structure.

Click the State list item in the Add Geography Type list.
Click Add to include the State geography type as the first level in the geography structure.
You can add subsequent levels such as County and City to the geography structure, by selecting the appropriate
geography type and clicking the Add button.
Click the Add Geography Type list.
Click the County list item.
Click the Add button.
You can also create additional geography types, if they are not available in the list.
Click the Create and Add Geography Type button.
Enter the new geography type name into the Geography Type field. Enter a valid value, such as City.
Click the Save and Close button.
Click the Add Geography Type list.
Click the Postal Code list item.
Click the Add button.
28
Chapter 3
15. Click the Save and Close button.
Geography Hierarchy
In the Manage Geographies page, click the Hierarchy Defined button to define the geography hierarchy data.
The Manage Geography Hierarchy page allows you to define a geography hierarchy. You can add geographies for each
geography type to create a hierarchy for the country.
1.
2.
3.
4.
5.
6.
7.
Create the state of California under United States. Click the United States object.
In the Geography Hierarchy region, click the Create button.
Enter the information into the Name field. Enter California.
Click the Save and Close button.
Create the Alameda county under the California state. Click the California object.
In the Geography Hierarchy region, click the Create button.
Enter the information into the Name field. Enter Alameda.

9. You can add subsequent levels such as City and Postal Code to the geography hierarchy, by selecting the
appropriate geography and clicking the Create button in the Manage Geography Hierarchy page.
Geography Validation
In the Manage Geographies page, click the Validation Defined button to define the geography mapping, validation for a
country's address styles, and the overall geography validation control for a country.
The Manage Geography Validation page allows you to specify the geography validations of a country.
The No Styles Format is the default address style format for a country, which can be used to define mapping and validation
for any address in the country.
29
Chapter 3
You can create address style formats in the Manage Address Formats page. Address formats specify the layout of an
address, including the address components and their position in the layout.
1. Click the No Styles Format object.
2. You can map geography types to address attributes for each address style format to be used for tax or geography
validation.
3. Click the State list item.
4. Click the Enable List of Values option to specify whether the geography type will appear as a list of values during
address entry in user interfaces.
5. Click the Tax Validation option to specify whether the geography type will be included in tax validation. A
transaction that involves an address with the included geography type must have correct geography information to
be considered valid for tax calculation.
6. Click the Geography Validation option to specify whether the geography type will be included in geography
validation.
7. The Geography Validation Control determines if an address that did not pass geography validation during
address entry can be saved or not. If the validation control is set to Error, then an address that has failed validation
cannot be saved. If the validation control is set to No Validation, all addresses are saved including incomplete and
invalid addresses.
8. Click the Error list item.
Address Cleansing
In the Manage Geographies page, click the Address Cleansing Defined button to validate, correct, and standardize
addresses that you enter in a user interface.
While geography validation validates the geography attributes of an address, address cleansing validates both geography
attributes and the address line attributes.
1. Click the Real-Time Address Cleansing Level list.
30
Chapter 3
2. Click the Optional list item.
3. Click in the Save and Close field.
Implementing Enterprise Structures: Procedure

The Enterprise Structures task list provides a framework for developing and managing your chart of accounts, ledgers, legal
entities, and business units to meet your accounting and reporting requirements.
31
Chapter 3
Setting Up Enterprise Structures

The tasks in the following list relate to the setup of enterprise structures. These are the basic steps for setup. These tasks
appear in the setup task list in the Setup and Maintenance work area; however, in your task list the tasks may be interspersed
with other tasks that do not need to be performed before you can use Oracle Fusion Financials.
Note
After performing all the enterprise structures tasks, run diagnostic tests for the enterprise structures setup data.
See; Oracle Financials Cloud Implementing Enterprise Structures and General Ledger guide: Define Chart of
Accounts for Enterprise Structures: Running Diagnostic Tests for Enterprise Structures Setup Data: Explained.
Each task is performed by the Application Implementation Consultant.
1. Manage geographies.
Perform the task Manage Geographies to enable the list of values for address fields in user interfaces.
32
Chapter 3
See: Oracle Financials Cloud Implementing Common Features guide: Define Enterprise Structures chapter:
Define Geographies section:
Importing Geographies: Explained
Importing Country Structures Using File-Based Import: Explained
Importing Geographies Using File-Based Import: Explained
Importing Geographies Using File-Based Data Import: Worked Example
Managing Geography Structures, Hierarchies, and Validation: Worked Example
2. Create chart of accounts, ledger, legal entities, and business units in a spreadsheet.
Perform the task Create Chart of Accounts, Ledger, Legal Entities, and Business Units in Spreadsheet
to create a spreadsheet for entering the primary ledger and all the accompanying enterprise structures. The
spreadsheet entry includes the chart of accounts with segment values and account hierarchies, associated
business units, associated legal entities, and rules for generating sequential IDs for transactions recorded in the
system, as well as select setup objects along with their accounting specifications for the various modules of
Oracle Fusion Financials.
See: Oracle Financials Cloud Implementing Enterprise Structures and General Ledger guide: Define Chart of
Accounts for Enterprise Structures: Manage Chart of Accounts section:
Create Chart of Accounts, Ledger, Legal Entities, and Business Units in Spreadsheets: Explained
Create Chart of Accounts, Ledger, Legal Entities, and Business Units in Spreadsheets: How They Are
Processed
3. Upload the chart of accounts file.
Perform the task Upload Chart of Accounts to load the chart of accounts structure, including segments and
value sets from spreadsheet.
Accounts for Enterprise Structures: Manage Chart of Accounts section: Create Chart of Accounts, Ledger,
Legal Entities, and Business Units in Spreadsheets: How They Are Processed
4. Deploy chart of accounts structure.
Perform the task Deploy Chart of Accounts to run the deployment process for the chart of accounts so that
it can be used in ledger and account setup.
Accounts for Enterprise Structures: Manage Chart of Accounts section: Define Chart of Accounts for Enterprise
Structures: Manage Chart of Accounts section: Create Chart of Accounts, Ledger, Legal Entities, and Business
Units in Spreadsheets: How They Are Processed.
See: Oracle Financials Cloud Implementing Common Features guide: Define Enterprise Structures chapter:
Define Legal Entities: Manage Legal Entity section:
Legal Entities: Explained
Legal Entity in Oracle Fusion: Points to Consider
See:
Oracle Financials Cloud Implementing Common Features guide: Define Enterprise Structures chapter:
Define Business Units: Manage Business Units section: Business Units: Explained.
33
Chapter 3
5. Upload the ledger, legal entities, and business units.
Perform the task Upload Ledger, Legal Entities, and Business Units to load the key enterprise structures,
including the ledger, legal entities, and business units, that depend on the chart of accounts.
Accounts for Enterprise Structures: Manage Chart of Accounts section: Create Chart of Accounts, Ledger,
Legal Entities, and Business Units in Spreadsheets: How They Are Processed.
Implementing General Ledger: Procedure

The Define Ledger Configuration for Rapid Implementation and Define Financial Reporting Configuration for
Rapid Implementation task lists provide a framework for developing and managing general ledger features including:
Ledger Sets
Data Access Sets
Intercompany Balancing Rules
Journal Approval Rules
Journal AutoPost Criteria Sets
Journal Reversal Criteria Sets
Accounting and Reporting Sequences
Revaluations
Historical Rates
Financial Reporting Center
Financial Reporting Studio
Smart View
Budgets
Setting Up General Ledger

The tasks in the following lists relate to the setup of general ledger. These are the basic steps for setup. These tasks appear
in the setup task list that was generated in the Setup and Maintenance work area. Your task lists contain tasks that may be
interspersed with other tasks that are not required to implement the Oracle Fusion Financials.
For setting up general ledger, each task is performed by the Application Implementation Consultant.
34
Chapter 3
Define Ledgers Configuration for Rapid Implementation

All documentation references are from the Oracle Financials Cloud Implementing Enterprise Structures and General Ledger
guide unless otherwise stated in the reference.
1. Manage ledger sets.
Perform the task Manage Ledger Sets to enable review and update existing collections of ledgers intended
for batch processing or financial reports, and create new collections.
See: Define Ledgers chapter:

Ledgers and Subledgers: Explained
Ledgers: Points to Consider
Financial Ledgers: How They Fit Together
Creating Primary Ledgers: Example
Specifying Ledger Options: Worked Example
Assigning Legal Entities and Balancing Segments: Examples
35
Chapter 3
2. Manage data access sets.
Perform the task Manage Data Access Sets to review and update existing groups of ledgers intended for
data security and create new groups.
See: Define Ledgers chapter:

3. Manage intercompany balancing rules.
Perform the task Manage Intercompany Balancing Rules to define rules to assign intercompany receivables
and intercompany payables accounts for transactions unbalanced by legal entity or management entity.
See: Define and Maintain Intercompany Processing Rules chapter

Manage Intercompany System Options
Manage Intercompany Organizations
Define Invoicing Options
Manage Intercompany Balancing Rules
Manage Ledger Balancing Options
4. Manage journal approval rules.
Perform the task Manage Journal Approval Rules to run review and update rules to route journal entries
through the approval process.
See: Define Ledgers chapter: Manage Journal Approval Rules
See: Oracle Financials Cloud Implementing Common Features guide: Define Approval Management chapter:
Approval Management: Highlights
5. Manage AutoPost criteria sets.
Perform the task Manage AutoPost Criteria Sets to review and update existing automatic journal posting
settings and define new settings.
See: Define Ledgers chapter: Manage AutoPost Criteria Sets
6. Manage journal reversal criteria sets.
Perform the task Manage Journal Reversal Criteria Sets to review and update existing automatic journal
reversal settings and define new settings.
See: Define Ledgers chapter: Manage Journal Reversal Criteria Sets
7. Manage accounting and reporting sequences.
Perform the task Manage Accounting and Reporting Sequences to review and update existing journal
posting and period close sequencing definitions and create new definitions.
36
Chapter 3
See: Oracle Financials Cloud Implementing Common Features guide: Maintain Common Reference Objects
chapter: Define Document Sequences
See: Define Ledgers chapter: Manage Accounting and Reporting Sequences section:
Accounting and Reporting Sequences: Overview
Defining Journal Sequences Manually: Explained
What happens if I enable sequencing in the rapid implementation spreadsheet
8. Manage allocations and periodic entries.
Perform the task Manage Allocations and Periodic Entries to review, update, and create allocation and
periodic definitions and journal entries. Generate journal entries from the allocation and periodic definitions.
See: Define Period Close chapter: Manage Allocations and Periodic Entries section
Allocation and Periodic Entries: Overview
Calculation Manager: Overview
Oracle Essbase Balances Cubes: Overview
Allocation Security: Explained
See: Define Period Close chapter: Manage Recurring Journals section
Recurring Journals: Overview
Recurring Journal Types: Explained
Creating Recurring Journals: Example
Generating Allocations and Periodic Entries Manually: Worked Example
9. Manage revaluation definitions.
Perform the task Manage Revaluations to review and update existing calculations of unrealized gains and
losses on foreign currency transactions, and define new calculations.
See: Define Period Close chapter: Manage Revaluations Rules section
Revaluation Process: Explained
Accounting for Unrealized Gain or Loss on Revaluation: Explained
Income Statement Accounts Revaluation Rule: Explained
Revaluing Across Multiple Balancing Segments: Worked Example
Defining Revaluations
10. Manage historical rates
Perform the task Manage Historical Rates to review and update existing currency historical conversion
information, and create new conversion information.
37
Chapter 3
See: Define Currencies and Currency Rates chapter: Manage Daily Rates section
Entering Daily Rates Manually: Worked Example
Updating Currency Rates: Worked Example
11. Open the first period.
Perform the task Open First Period to open the first accounting period so you can begin recording
transactions.
See: Define Period Close chapter:

Opening First Period: Overview
Close Monitor: Overview
Define Financial Reporting Center Configuration for Rapid

Implementation
All documentation references are from the Oracle Financials Cloud Implementing Enterprise Structures and General Ledger:
Define Financial Reporting Ledgers chapter.
1. Define Financial Reporting Center configuration:
Perform the task Define Financial Reporting Center Configuration to define and manage technical
configuration options for the Oracle Fusion Financial Reporting Center.
See:
Setting Up Your Financial Reporting Center: Critical Choices
Migrating Financial Reports: Instructions
38
Chapter 3
Mobile Financial Reporting Implementation: Points to Consider
2. Define Essbase database connections:
Perform the task Define Essbase Database Connections in Workspace to define database connections to
connect to Essbase in Workspace.
See: Setting Up Your Financial Reporting Center: Critical Choices
3. Configure Financial Reporting Studio client:
Perform the task Configure Financial Reporting Studio Client for Users to install Financial Reporting
Studio client on users' computers to create financial reports.
4. Configure Smart View Client:
Perform the task Configure Smart View Client for Users to install Smart View client on users' computers to
perform balance inquiry.
5. Define budget scenarios.
Perform the task Define Budget Scenarios to define scenarios to track budgets for different periods or
forecasts.
See: Define Budget Configuration chapter:

Budget Uploads: Overview
Importing Budget Data from a Flat File: Explained
39
Chapter 3
Loading Data to the Budget Interface Table: Explained

Importing Budget Data from a Spreadsheet: Explained
Budget Correction with Oracle ADF Desktop Integrator: Explained
Implementing Cash Management: Procedure

The Oracle Fusion Cash Management product provides a framework for developing and managing your banks, bank
branches, and bank accounts.
Setting Up Cash Management
The tasks in the following list relate to the setup and uploading of banks, bank branches, and bank accounts. These are the
basic tasks that appear in the Setup and Maintenance work area.
For setting up cash management, each task is performed by the Application Implementation Consultant. All documentation
references are from the Oracle Financials Cloud Implementing Payables Invoice to Pay: Define Cash Management and
Banking Configuration chapter 10.
1. Create banks, branches, and accounts in a spreadsheet.
Perform the task Create Banks, Branches, and Accounts in Spreadsheet to create your bank, branch,
and account information and loaded it into the Oracle Fusion Cash Management.
2. Upload banks, branches, and accounts.
Perform the task Upload Banks, Branches, and Accounts to import your bank, branch, and account
information into the Oracle Fusion Cash Management.
See:
Implementing Tax: Procedure

Oracle Fusion Tax provides a single-point solution for managing your transaction and withholding tax requirements.
Oracle Fusion Tax:
Uniformly delivers tax services to all Oracle Fusion application business flows through one application interface.
Provides features for uploading third-party tax partner content.
Is configurable and scalable for adding and maintaining country-specific tax content.
Setting Up Oracle Fusion Tax

The Define Taxes for Rapid Implementation task list provides you the required and most frequently used setup tasks for
implementation scenarios. Using spreadsheets, you can upload your tax setups to create tax regimes, taxes, tax rates, and
tax rules as an example.
Use the standard Define Tax Configuration task list for the ongoing incremental maintenance of your tax setup and those
limited tax configurations that cannot be set up or updated using the rapid implementation approach.
40
Chapter 3
For setting up Oracle Fusion Tax, each task is performed by the Application Implementation Consultant or the Tax Manager.
All documentation references are from these chapters in the Oracle Financials Cloud Implementing Tax guide:
Tax Configuration Using Rapid Implementation
Tax Configuration
1. Manage tax regimes.
Perform the task Manage Tax Regimes to create and maintain tax regimes for the taxes in each country and
geographic region where a separate tax or collection of taxes apply.
Use the Tax Configuration Workbook to upload all common tax setups. Use the Tax Implementation Workbook
to upload your organization-specific setups such as tax regime subscriptions.
You can also use the individual Tax Regimes and Tax Regime Subscriptions spreadsheets to exclusively create
tax regimes and tax regime subscriptions.
See:
Creating Tax Setup Using the Tax Configuration Workbook: Worked Example
Creating Tax Setup Using Tax Partner Content in the Tax Configuration Workbook: Worked Example
Tax Implementation Workbook: Explained
Creating Tax Setup Using the Tax Implementation Workbook: Worked Example
Creating a Tax Regime Using the Manage Tax Regimes Spreadsheet: Worked Example
2. Run jurisdiction and rates upload program.
Perform the task Run Jurisdiction and Rates Upload Program to upload US sales and use tax jurisdictions
and tax rates from a tax partner.
See:
Tax Configuration Content Upload Program: How It Is Processed
3. Manage taxes.
Perform the task Manage Taxes to create and maintain details for the taxes of tax regimes.
Use the Tax Configuration Workbook to upload all common tax setups. Use the Tax Implementation Workbook
to upload your organization-specific tax account assignments.
You can also use the individual Taxes spreadsheet to create taxes for a tax regime or a collection of tax
regimes.
See:
41
Chapter 3
Tax Implementation Workbook: Explained
Creating Tax Setup Using the Tax Implementation Workbook: Worked Example
4. Manage tax rates and tax recovery rates.
Perform the task Manage Tax Rates and Tax Recovery Rates to create and maintain details for tax rates
and tax recovery rates.
Use the Tax Configuration Workbook to upload all common tax setups.
You can also use the individual Tax Rates, Tax Rate Accounts, Tax Recovery Rates, and Tax Recovery Rate
Accounts spreadsheets to create tax statuses, tax jurisdictions, tax rates, tax recovery rates, and tax accounts
where needed.
See:
5. Manage tax rules.
Perform the task Manage Tax Rules to create and maintain tax rules that define the conditions under which
the exceptions to the default taxability apply.
Use the Tax Configuration Workbook to upload all common tax setups.
You can also use the individual Tax Rules spreadsheet to create tax rules details.
See:
6. Manage tax registrations.
Perform the task Manage Tax Registrations to create and maintain tax registration information related to a
party's transaction tax obligation with a tax authority for a tax jurisdiction where it conducts business.
Use the Tax Implementation Workbook to upload your organization-specific tax registrations.
See:
Tax Registrations: Explained
7. Manage tax exemptions.
Perform the task Manage Tax Exemptions to create and maintain tax exemptions to reduce or increase the
tax rate applied to a transaction.
42
Chapter 3
See:
Tax Exemptions: Explained
8. Manage simulator transactions.
Perform the task Manage Simulator Transactions to verify tax configuration for taxes that are enabled for
transactions, for simulation, or for both by processing real-time transactions without affecting active data.
See:
Tax Simulator: Explained
Implementing Payables and Payments: Procedure

To get started with Oracle Fusion Payables and Oracle Fusion Payments, the Invoicing and Payments Configuration for Rapid
Implementation task list provides a framework for managing setups for Oracle Fusion Procurement that are required to set up
Payables, as well as the setup steps of common options, distribution sets, and invoice tolerances for Payables and the setup
steps of disbursement system options, payment methods, and payment process profiles for Payments.
Setting Up Payables and Payments

The tasks in the following list relate to the setup of Payables and Payments.
For setting up Payables and Payments, each task is performed by the Application Implementation Consultant. References to
help topics in the following tasks are from the following publications:
Oracle Financials Cloud Implementing Payables Invoice to Pay
General Payables Options chapter, Manage Common Options for Payables and Procurement section
Payables Configuration chapter
Disbursements chapter
Oracle Procurement Cloud Implementing Procurement
Define Purchasing Configuration chapter, Define Procurement Agents section
Oracle Procurement Cloud Using Procurement
Manage Supplier Information chapter, Manage Supplier Profiles section
1. Configure Procurement business function, procurement agents, and suppliers.
Perform the task Configure Procurement Business Function, Procurement Agents, and Suppliers,
which includes configuring:
The procurement business function for the procurement business unit to specify procurement document
control, document defaults, document numbering, and related settings.
Procurement agent access to information, such as purchasing documents and suppliers.
43
Chapter 3
Suppliers, sites, and other supplier-related information.
See: Define Procurement Agents section

Create Procurement Agent: Critical Choices
See: Manage Supplier Profiles section

Supplier Model: Explained
Supplier Import Process: Explained
Supplier Sites and Supplier Site Assignments: Explained
2. Manage common options for Payables and Procurement.
Perform the task Manage Common Options for Payables and Procurement to set the controls and default
values that are used by both Payables and Procurement, such as the default liability account and whether to
accrue expense items at time of receipt or at period end.
See: Manage Common Options for Payables and Procurement section

Common Options for Payables and Procurement: Critical Choices
Default Distributions: Explained
Offset Segments: Critical Choices
Accruing Expense Items: Critical Choices
Note
You can skip this step if you have used the Rapid Implementation spreadsheet for General Ledger to
create the ledger, legal entities, and business units.
3. Manage distribution sets.
Perform the task Manage Distribution Sets to define a distribution set, which is a list of accounts with or
without percentages. When you create an invoice that is not associated with a purchase order, you can enter
the distribution set name to automatically create the invoice distributions with a predefined set of accounts.
If the distribution set has percentages, the invoice line amount is automatically distributed to the accounts,
otherwise you must enter the amounts manually.
See: Payables Configuration chapter

Distribution Sets: Explained
4. Manage invoice tolerances.
Perform the task Manage Invoice Tolerances to define acceptable variances between invoice, purchase
order, and receipt information. You can define both percentage-based and amount-based tolerances. Invoices
that exceed the specified tolerances are placed on hold during the invoice validation process.
See: Payables Configuration chapter

Invoice Tolerances: Explained
44
Chapter 3
5. Manage disbursement system options.

Note
Payments provides predefined setups for Steps 5 to 7. You do not need to modify the predefined setups
unless you wish to change disbursement system options, or create customized payment methods or
payment process profiles.
Perform the task Manage Disbursement System Options to manage payment processing options at the
enterprise and business unit level.
6. Manage payment methods.
Perform the task Manage Payment Methods to define or manage payment methods and to attach or update
validations that are assigned to them. See:
Payment Methods: Explained
Payment Method Defaulting: Explained
Setting Up User-Defined Validations for Payment Methods or for Payment Files: Worked Example
7. Manage payment process profiles.
Perform the task Manage Payment Process Profiles to define or manage payment process profiles, which
are entities that determine the payment processing type, grouping of installments, grouping of payments, and
the definition of usage rules based on payment methods, disbursement bank accounts, business units, and
currencies. See:
Payment Process Profiles: Explained
45
Chapter 3
Implementing Assets: Procedure

The Assets task list provides a framework for developing and managing your Assets flexfields, system controls, fiscal years,
locations, calendars, prorate conventions, asset books, and asset categories to enable your accounting and reporting
requirements.
Setting Up Assets
The tasks in the following list relate to the setup of Oracle Fusion Assets. These are the basic steps for setup. These tasks
appear in the setup task list in the Setup and Maintenance work area; however, in your task list the tasks may be interspersed
with other tasks that do not need to be performed before you can use Oracle Fusion Financials.
For setting up Assets, each task is performed by the Application Implementation Manager. All documentation references are
from the Oracle Financials Cloud Implementing Assets guide, unless otherwise noted.
1. Manage fixed assets flexfield value sets.
Perform the task Manage Fixed Assets Flexfield Value Sets to create value sets.
See: Oracle Applications Cloud Extending the Applications for Functional Administrators guide: Flexfields for
Custom Attributes chapter
Flexfield Management section: Flexfields and Value Sets: How They Work Together
Manage Value Sets section
Value Sets: Explained
Defining Value Sets: Critical Choices
46
Chapter 3
2. Manage Assets key flexfields.
Perform the task Manage Fixed Assets Key Flexfields to create flexfield segments that let you:
Create categories and group assets by financial information using the Asset Category key flexfield.
Group your assets by non-financial information using the Asset Key flexfield.
Group and track your assets by physical location using the Location flexfield.
See: Assets Flexfields chapter

Asset Category Key Flexfield: Explained
Asset Key Flexfield: Explained
Location Flexfield: Explained
3. Manage system controls.
Perform the task Manage System Controls to:

Enter the enterprise name that appears on your reports.
Establish the oldest date placed in service.
Define your key flexfield structures.
Define your automatic asset numbering.
See: Assets Flexfields chapter: System Controls: Explained
4. Manage fiscal years.
Perform the task Manage Fiscal Years to create a standard set of periods used to prepare annual financial
statements for reporting and tax purposes.
See: Asset Books chapter: Fiscal Years: Explained
5. Manage asset locations.
Perform the task Manage Asset Locations to create locations to group and track your assets by physical
location.
See: Assets Flexfields chapter: Location Flexfield: Explained

See: Oracle Applications Cloud Extending the Applications for Functional Administrators guide: Flexfields for
Custom Attributes chapter: Flexfields and Oracle Fusion Application Architecture: How They Work Together
6. Manage asset calendars.
Perform the task Manage Asset Calendars to define depreciation calendars and prorate calendars according
to your company's needs.
See: Asset Books chapter

Creating Calendars: Points to Consider
47
Chapter 3
Creating an Asset Calendar: Worked Example

7. Manage prorate conventions.
Perform the task Manage Prorate Conventions to create conventions used to determine how much
depreciation to take in the first and last year of an asset's life.
See: Asset Books chapter: Prorate and Retirement Conventions: Explained
8. Manage asset categories.
Perform the task Manage Asset Categories to define information that is common to a group of assets, such
as the depreciation method and the prorate convention.
See: Asset Categories chapter

Asset Categories: Explained
Creating an Asset Category: Worked Example
Asset Category Key Flexfield: Explained
9. Manage asset books.
Perform the task Manage Asset Books to organize depreciation rules, accounts, and calendars by asset
book.
See: Asset Books chapter

Creating or Modifying Asset Books: Points to Consider
Creating a Corporate Book: Worked Example
Creating a Tax Book: Worked Example
Implementing Expenses: Procedure

The Define Expenses Configuration for Rapid Implementation task list provides a framework for developing and managing
your system options, expense report templates, approval rules, and conversion rates and policies.
The tasks in the Define Expenses Configuration for Rapid Implementation task list enable expense entry, approval, and
reimbursement processing in Expenses.
Setting Up Expenses
To set up Expenses, each task is performed by the Application Implementation Consultant. References to help topics in the
following tasks are from the Oracle Financials Cloud Implementing Expenses: Expense Policies and Rules chapter.
1. Manage expenses system options.
Perform the task Manage Expenses System Options to define setup options for managing expense entry
and processing for all business units.
Confirm that the default settings are aligned with your business practices.
48
Chapter 3
2. Manage expense report templates.

Perform the task Manage Expense Report Templates to define expense types applicable to your company
and group them into expense templates. Expense templates are defined by business units. The expense
templates available in expense report entry is determined by the business unit of the employees.
Specify receipt requirements when you define expense types.
See:
Expense Templates: Points to Consider
Can expense types be used across expense templates?
Configuring Expense Policies: Points to Consider.
3. Manage expense approval rules.
Perform the task Manage Expense Approval Rules to define expense report approval rules based on your
company's approval policies.
Modify the predefined rules as needed.
See:
Configuring Approval Rules: Explained
Defining Approval Rules: Explained
Note
To enable audit of expense reports, you must define audit rules in addition to approval rules.
4. Manage conversion rates and policies.

Perform the task Manage Conversion Rates and Policies to select the conversion rate type for each
business unit.
See: Configuring Expense Policies: Points to Consider
Implementing Receivables and Payments: Procedure

The Receivables task list provides a framework for developing and managing your accounts receivable environment. This
includes the necessary setups in Oracle Fusion Receivables and the related setups in Oracle Fusion Payments.
Defining the Receivables and Payments Configuration

The tasks in the following list relate to the setup of Receivables and Payments for Receivables. These are the basic steps for
setup.
For setting up Receivables and Payments for Receivables, each task is performed by the Application Implementation
Consultant. All documentation references are from these chapters in Oracle Financials Cloud Implementing Receivables
Credit to Cash:
Define Common Accounts Receivable Configuration
49
Chapter 3
Manage Receivables System Options

Define Customer Billing Configuration
Define Customer Payments
Configure Payment System Connectivity
Define Funds Capture
Define Customer
1. Manage Receivables system options.
Perform the task Manage Receivables System Options to manage the basic settings of your Receivables
environment.
See: Manage Receivables System Options chapter:

Updating System Option Records: Critical Choices
Using Header Level Rounding: Example
Tax Invoice Printing Options
Tuning Segments: Explained
Log File Message Levels: Explained
Transaction Delivery E-Mail Subject Line: Examples
Transaction Delivery Using E-Mail: How It Works
Setting Up Oracle B2B to Send Receivables Transactions in XML: Procedures
Setting Up B2B XML Invoicing for Receivables: Explained
Processing XML Transactions for Receivables: Explained
2. Manage Receivables activities.
Perform the task Manage Receivables Activities to set up default accounting information for all activities in
accounts receivable other than transaction processing and receipt processing.
See: Define Common Accounts Receivable Configuration: Define Receivables Activities section:
Receivables Activity Types
GL Account Source
Tax Rate Code Source
3. Manage AutoAccounting rules.
Perform the task Manage AutoAccounting Rules to set up default accounting information for Receivables
transaction processing.
See: Define Customer Billing Configuration: Define AutoAccounting section:

AutoAccounting Account Types and Segment Values
50
Chapter 3
AutoAccounting Structure: Points to Consider

Using AutoAccounting to Derive Accounting Flexfield Segments: Example
4. Manage remit-to addresses.
Perform the task Manage Remit-to Addresses to assign remit-to addresses to Receivables transactions.
See: Define Customer Billing Configuration: FAQs for Remit-to Addresses section:
How can I use remit-to addresses?
How does AutoInvoice validate remit-to addresses?
How can I define a default remit-to address?
Why did the country appear?
Why do I verify the address?
5. Manage standard memo lines.
Perform the task Manage Standard Memo Lines to define memo lines for line items that are not inventory
items.
See: Define Customer Billing Configuration: Define Memo Lines section: Revenue Accounts and Memo Lines:
Explained
6. Manage funds capture payment methods.
Perform the task Manage Funds Capture Payment Methods to define funds capture payment methods to
enable customers to remit payments. Payments supports bank account transfers for automated funds capture
processing.
7. Manage funds capture process profiles.
Perform the task Manage Funds Capture Process Profiles to define profiles for funds capture processing
with rules for authorization and settlement handling.
See: Define Funds Capture chapter: Funds Capture Process Profile: Explained
8. Manage internal payees.
Perform the task Manage Internal Payees to set up one or more business units that use a payment
processor or gateway to receive funds from customers.
9. Manage payment systems.
Perform the task Manage Payment Systems to define external organizations, such as banks or payment
processors, that process funds capture and disbursement transactions.
See: Configure Payment System Connectivity chapter

Validations: Critical Choices
Formats: Explained
51
Chapter 3
Transmission Protocol: Explained

Transmission Configuration: Explained
Configuring Your Communication Channel to a Payment System: Explained
Payment System: Explained
Payment System Account: Explained
Importing a Security Credential File: Procedures
10. Manage receipt classes and methods.
Perform the task Manage Receipt Classes and Methods to set up the steps required for receipts and to set
up default accounting information for receipt processing.
See: Define Customer Payments: Define Receipt Classes and Methods section:
Remittance Methods and Clearance Methods
Automatic Receipt Processing: Points to Consider
Fund Transfer Error Handling: Explained
Remittance Bank Accounts: Explained
11. Manage lockbox.
Perform the task Manage Lockbox to set up a lockbox to create receipts automatically from data supplied by
your remittance bank.
See: Define Customer Payments: Define Lockbox section:

Processing Lockbox Files: How It Works
Lockbox Interface Table AR_PAYMENTS_INTERFACE_ALL
Using a Custom Matching Rule with Lockbox: Explained
Match Receipts By Method: Explained
12. Manage transmission formats for lockbox.
Perform the task Manage Transmission Formats for Lockbox to set up lockbox transmission formats. The
transmission formats ensure that data is correctly transferred from your remittance bank.
See: Define Customer Payments: Define Transmission Formats for Lockbox section:
Validating the Lockbox File Transmission: How It Works
Lockbox Transmission Formats
Lockbox Transmission Format Record Types
Lockbox Transmission Format Field Types
52
Chapter 3
13. Manage statement cycles.
Perform the task Manage Statement Cycles to set up statements and statement cycles that determine when
to send statements to your customers.
See: Define Common Accounts Receivable Configuration: Define Statements section:

Setting Up for Statements: Procedure
Statement Cycles: Example
14. Create customer.
Perform the task Create Customer to create customer records for all organizations and persons with whom
you do business.
See: Define Customer chapter: Define Customer Account section and Manage Customers section:
Customer Account Relationships: Explained
Customer Account Uses: Points to Consider
Customer Addresses: Points to Consider
Related Contact Sites: Explained
Customer and Party: Explained
Party Relationships: Explained
15. Manage approval limits.
Perform the task Manage Approval Limits to set approval limits for each of your users for specific
transactions and amount ranges per currency.
See: Define Common Accounts Receivable Configuration: Define Approval Limits section: Approval Limits
Document Types.
Intercompany Balancing Rules: Explained

Intercompany balancing rules are used to generate the accounts needed to balance journals that are out of balance by legal
entity or primary balancing segment values.
You specify the intercompany receivables and intercompany payables accounts you want to use. The intercompany
balancing feature then uses these rules to generate the accounts of the balancing lines it creates.
Defining Intercompany Balancing Rules

You can define intercompany balancing rules at the following rule levels:
1. Primary balancing segment
2. Legal entity
3. Ledger
4. Chart of accounts
53
Chapter 3
The rules are evaluated in the order shown above. For example, you can define a Primary Balancing Segment rule and a
Legal Entity level rule. If both rules are used to balance a particular journal, the Primary Balancing Segment rule is used, as it
has a higher precedence.
You have flexibility in defining your intercompany balancing rules. You can have a simple setup in which you define one rule
for your chart of accounts. This rule is used for all intercompany balancing for all ledgers that use this chart of accounts.
Alternatively, you can have a more granular set of rules. For example, you can define a different rule for each legal entity and
one chart of accounts rule to cover any gaps in your rule definitions. You can gain even more granularity by defining rules for
specific journal and/or category combinations or intercompany transaction types.
Intercompany Balancing Rules: Examples

This topic provides examples of intercompany balancing rules and the intercompany balancing lines generated. These rules
are used to generate the accounts needed to balance journals that are out of balance by legal entity or primary balancing
segment values.
Simple Chart of Accounts

In this scenario you have one chart of accounts for all ledgers. The chart of accounts has an intercompany segment. You
are using this intercompany segment and the company segment to identify the intercompany trading partners for each
transaction. You do not have a need to track their intercompany activity at a granular level such as by journal source and
journal category or by intercompany transaction type.
Setup
InFusion USA Chart of Accounts
Segment
Qualifier
Primary
Balancing
Segment
Second
Balancing
Segment
Third
Balancing
Segment
Account
Intercompany
Segment
Segment
Name
Company
(CO)
Cost Center
(CC)
Product
(PROD)
Account
(ACCT)
Intercompany
(IC)
Ledger, Legal Entity, Primary Balancing Segment Value Assignments
Ledger
Legal Entity
Primary Balancing Segment

Value
InFusion USA
InFusion Farms
3100, 3200, 3300, 3400, 3500
InFusion USA
InFusion Textiles
4000
InFusion USA
InFusion Products (East)
5000
54
Chapter 3
Ledger
Legal Entity

Value
InFusion USA
InFusion Products (West)
6000
InFusion USA
1000, 9000
Chart of Accounts Rule

Rule
Number
Chart of
Accounts
AR
Account
AP
Account
Source
Category
Transaction
Type
InFusion
USA
Chart of
Accounts
1000 - 000
- 0000 13010 0000
1000 - 000
- 0000 21010 0000
Other
Other
None
Journal Balancing
Journal before Balancing
Line
Line
Type
Legal
Entity
CO
CC
PROD
ACCT
IC
Debit
Expense
InFusion
Farms
3100
100
1200
52330
0000
150
Liability
InFusion
Textiles
4000
500
1300
40118
0000
Credit
150
Journal Balancing
Uses
Rule
Journal after Balancing
Line
Line
Type
Legal
Entity
Company Cost
Center
Product
Account Intercompany
Debit
Expense
InFusion
Farms
3100
100
1200
52330
0000
Liability
InFusion
Textiles
4000
500
1300
40118
0000
Credit
150
150
55
Chapter 3
Uses
Rule
Line
Line
Type
Legal
Entity
Company Cost
Center
Product
Account Intercompany
Debit
Credit
IC
AP
InFusion
Farms
3100
100
1200
21010
4000
150
IC
AR
InFusion
Textiles
4000
500
1300
13010
3100
150
Legal Entity and Chart of Accounts Rules

In this example the legal Entity InFusion Textiles intercompany manufacturing activities are tracked separately from its nonmanufacturing activities. In order to achieve this legal entity level rules are defined specifically between the legal entity InFusion
Textiles and the two manufacturing legal entities, InFusion Products (East) and InFusion Products (West). A chart of accounts
rule is created to cover all other intercompany activities.
Setup
InFusion USA Chart of Accounts
Segment
Qualifier
Primary
Balancing
Segment
Second
Balancing
Segment
Third
Balancing
Segment
Account
Intercompany
Segment
Segment
Name
Company
Cost Center
Product
Account
Intercompany
Ledger, Legal Entity, Primary Balancing Segment Value Assignments
Ledger
Legal Entity

Value
InFusion USA
InFusion Farms
3100, 3200, 3300, 3400, 3500
InFusion USA
InFusion Textiles
4000
InFusion USA
InFusion Products (East)
5000
InFusion USA
InFusion Products (West)
6000
InFusion USA
1000, 9000
56
Chapter 3
Chart of Accounts Rule

Rule
Number
Chart of
Accounts
AR
Account
AP
Account
Source
Category
Transaction
Type
InFusion
USA
Chart of
Accounts
1000 - 000
- 0000 13050 0000
1000 - 000
- 0000 21050 0000
Other
Other
None
Legal Entity Level Rule

Rule No.
From
Legal
Entity
To Legal
Entity
AR
Account
AP
Account
Source
Category
Transaction
Type
InFusion
Textiles
InFusion
Products
(West)
1000 000 0000 13020 0000
1000 000 0000 21020 0000
Other
Other
None
InFusion
Textiles
InFusion
Products
(East)
1000 000 0000 13030 0000
1000 000 0000 21030 0000
Other
Other
None
Journal Balancing
Journal before Balancing
Line
Line
Type
Legal
Entity
CO
CC
PROD
ACCT
IC
Debit
Expense
InFusion
Farms
3100
100
1200
52330
0000
150
Expense
InFusion
Products
(East)
5000
100
1200
52340
0000
200
Expense
InFusion
Products
(West)
6000
200
1300
52345
0000
300
Credit
57
Chapter 3
Line
Line
Type
Legal
Entity
CO
CC
PROD
ACCT
IC
Debit
Liability
InFusion
Textiles
4000
500
1300
40118
0000
Credit
650
Journal Balancing
Uses
Rule
Journal after Balancing
Line
Line
Type
Legal
Entity
CO
CC
PROD
ACCT
IC
Debit
Expense
InFusion
Farms
3100
100
1200
52330
0000
150
Expense
InFusionProducts
5000
(East)
100
1200
52340
0000
200
Expense
InFusionProducts
6000
(West)
200
1300
52345
0000
300
Liability
InFusion
Textiles
4000
500
1300
40118
0000
IC
AR
InFusion
Textiles
4000
500
1300
13050
3100
IC
AP
InFusion
Farms
3100
100
1200
21050
4000
IC
AR
InFusion
Textiles
4000
500
1300
13030
5000
IC
AP
InFusionProducts(East)
5000
100
1200
21050
4000
IC
AR
InFusion
Textiles
500
1300
13020
6000
10
IC
AP
InFusionProducts
6000
(West)
200
1300
21050
4000
4000
Credit
650
150
150
200
200
300
300
58
Chapter 3
59
Chapter 4
Define General Ledger Security: Explained

General Ledger has several security features including:
Data Access Set Security: Grants access to a ledger, ledger set, or specific primary balancing segment values 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.
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 or your implementation project.
Function and Data Security: Secures features and data with privileges that are mapped to roles.
Access through the Define Security task list on the Setup and Maintenance work area or your implementation
project.
Use Oracle Identity Manager (OIM) to manage user and user-role assignments.
Use Authorization Policy Manager (APM) to manage data roles and duty roles.
Defining Segment Value Security Rules

Set up segment value 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. Create conditions and assign them to specific data roles
to control access to your value set values.
Restrict data entry, online inquiry, and reporting to specific values by using segment value security rules.
General Points About Segment Value Security:
Used with flexfield segments.
Applies at the value set level. If a value set is secured, every usage of the value set in the chart of accounts structure
is secured. For example, if the same value set is used for the legal entity and intercompany segments of the chart of
accounts, the same security is applied to both segments.
Applies only to independent value sets.
Specifies that data security be applied to segment values that use the value set. Based on the roles provisioned to
users, data security policies determine which values of the segment users can view or modify.
Applies mainly when data is created or updated, and to account combination tables for query purposes.
Controls access to parent or detail segment values.
Note
A distinction between setup and transactions user interfaces is that segment value security prevents you from
seeing certain account values in transaction user interfaces but you can still see the account combinations with
the secured values in setup user interfaces.
If you try to update the field in the setup user interface, you cannot use those secured values. For transaction,
balance, and query activity type user interfaces, the 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.
60
Chapter 4
Related Topics
How can I secure GL balances cubes

Data Access Sets secure access to ledgers, ledger sets, and portions of ledgers 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 midlevel parents and detail values.
Requires all ledgers assigned to the data access set to share chart of accounts and accounting calendar.
When a ledger is created, a data access set for that ledger is automatically created; giving full read and write access to that
ledger. Data access sets are automatically created when you create a new ledger set as well. You can also manually create
your data access sets to give read only access or partial access to select balancing segment values in the ledger.
You can combine ledger and ledger set assignments to a single data access set you create as long as the ledgers all share
a common chart of accounts and calendar. When a data access set is created, data roles are automatically created for that
data access set. Three data roles are generated for each data access set, one for each of the Oracle Fusion General Ledger
roles:
General Accountant
Financial Analyst
The data roles then must to be assigned to your users before they can use the data access set.
Full Ledger Access: Access to the entire ledger or ledger sets. For example, this could mean read only access to
the entire ledger or both read and write access.
61
Chapter 4
Primary Balancing Segment Value: Access one or more primary balancing 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.
Note
Security by management segment consistent with the primary balancing segment as used above is not currently
available.

This example shows two data access sets that secure access by using primary balancing segment values that correspond to
legal entities.
Scenario
The figure shows the actions enabled when an access level is assigned to a balancing segment representing legal entities (LE)
for one of the two access levels:
Read Only
Read and Write
InFusion USA Primary Ledger is assigned to this Data Access Set.

Read only access has been assigned to balancing segment value 131 that represents the InFusion USA Health
LE3.
62
Chapter 4
Read and write access has been assigned to the other two primary balancing segment values 101 and 102 that
represent InFusion USA Health LE1 and LE2.
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.
Segment Value Security: Examples

Segment value security is enforced in Oracle Fusion Applications where ever the charts of accounts values are used.
Scenario
1. When entering a journal for a ledger with a secured chart of accounts, you can only use account values for which
the access is granted using segment security rules.
2. When running reports against a ledger with a secured chart of accounts, you can only view balances for accounts
for which the access is granted using segment security rules.
3. When viewing ledger options in an accounting configuration, if the accounts specified include references to an
account with values you have not been granted access to, you can see the account but not be able to enter that
secured value if you select to modify the setup.
Example
Create conditions and assign them to specific data roles to control access to your segment values. For example:
1. Enable security on both the cost center and account value sets that are associated with your chart of accounts.
2. Assign the General Accountant - InFusion USA data role to have access to cost center Accounting and account US
Revenue.
3. Deny all other users access to the specified cost center and account values.
Segment Value Security Operators
63
Chapter 4
Use any of the following operators in your conditions to secure your segment values:
Operator
Equal to
Usage
Secures a detail specific value.
Don't use this operator to secure a parent value.
Not equal to
Secures all detail values except the one that you

specify.
Don't use this operator to secure a parent value.
Between
Secures a detail range of values.
Is descendent of
Secures the parent value itself and all of its descendents

including mid level parents and detail values.
Is last descendent of
Secures the last descendents, for example the detail

values of a parent value.
Tip:
For Is descendent of and Is last descendent of:
Specify an account hierarchy (tree) and a tree version to use this operator.
Understand that the security rule applies across all the tree versions of the specified hierarchy, as well as all
hierarchies associated with the value set.
Enabling Security on a Chart of Accounts: Example

Enabling security for a chart of accounts controls access to values in your account segments. To enable security:
Create and assign conditions and polices to rules.
Specific data roles to control access during journal entry, account inquiry, and reporting.
Note
Before proceeding with these steps, determine what roles are defined and assigned in Oracle Identity Manager
(OIM) for each ledger and its chart of accounts. The definition of security policies requires specifying roles that are
impacted by these rules.
Important: As soon as segment value security is enabled on the chart of accounts, all users are denied access
to that chart of accounts. The system administrator must specifically grant security policies to the users' roles to
enable the users to access their values for that chart of accounts.
64
Chapter 4
Scenario
In this example, you are responsible for creating a segment value security rule for each of your segments of your InFusion
America chart of accounts.
1. Ensure that your tree and tree version definitions are properly set up.
Note
This step is important if you plan on using tree operators in your policy definitions since the policy may
not provide the expected action if the hierarchy is not properly defined.
2. Navigate to the Setup and Maintenance page.
3. In the All Tasks tab, search for Manage Segment Value Security Rules. Click the Go to Task.
4. Enter the wanted information into the Value Set Code field. Click Search.
5. With the value set highlighted, click Edit.
6. Enable the Security enabled check box.
7. Enter the Data Security Resource Name.
8. Click Edit Data Security to begin defining the security condition and policy.
9. With the Condition tab selected, click Create to begin creating the condition.
Note
While defining each condition, you can select to specify whether it uses tree operators or regular
operators. Only the following operators are supported.
For non-tree operators select from:

Equal to
Not Equal to
Between
Not Between
For tree operators select from:

Is a last descendent of
Is a descendent of
65
Chapter 4
10. Click Save.

11. On the Policy tab, click Create in the General Information tab.
12. Enter information in the General Information tab.
13. Select the Role tab and search for the relevant data role to assign to this policy.
14. Click the Rule tab to associate the relevant condition with the policy.
Note
The Row Set field determines the range of value set values affected by the policy.
If Multiple Values is selected, then a condition must be specified.
If All Values is selected, then the policy grants access to all values in the value set and no condition
is needed.
15. Repeat these steps for the remaining value sets in your chart of accounts.
16. Click Save and Close.
17. Click Submit.
18. The last step is to run the deploy process by clicking the Deploy Flexfield button on the Manage Key Flexfields
page before security is enabled for the chart of accounts.
Related Topics
Flexfield Deployment: Explained
66
Chapter 5

The Oracle Fusion Financial Reporting Center provides functionality for reporting on Oracle Fusion General Ledger balances. It
provides secure, self-service access to reports that use real time account information.
You can design traditional financial report formats such as balance sheets, profit and loss statements, and cash flow reports.
You can also design nontraditional formats for financial or analytic data that include text and graphics.
Components
Financial Reporting Center is comprised of numerous components:
Financial Reporting: Financial users and analysts access live reports and books or published snapshot reports
and books from previously scheduled batches in a variety of formats. Other functionality includes the following
capabilities:
Refresh report data using runtime points of view or parameters

Drill through from parents to other parents
Drill down to detail balances, journal lines, and subledger transactions
Oracle Hyperion Smart View: Financial analysts view, import, manipulate, distribute, and share data from your
Oracle Fusion General Ledger balances in Microsoft Excel.
Account Monitor and Account Inspector: Financial analysts monitor and track key account balances in real time
at every level of your dimensions and hierarchies. These tools provide multidimensional account analysis and drill
down capability.
67
Chapter 5
Workspace: Reporting administrators:
Create, open, save, and delete folders
Store report objects, reports, and snapshot reports
Oracle Hyperion Financial Reporting Studio: Report authors use an object-oriented graphical report layout with
report objects, such as text boxes, grids, images, and charts, to design reports.
Related Topics
Setting Up Your Financial Reporting Center: Critical Choices
Define Financial Reporting Center

Oracle Fusion Financial Reporting Center is a powerful tool for accessing, designing, and presenting financial reports and
analytic data.
Configure Financial Reporting Center

You have access to the reports through the folder structure in the Financial Reporting Center and Workspace installed with
Oracle Fusion Financials. Your Oracle Fusion Business Intelligence (BI) administrator defines the folder structure in Workspace
taking into consideration your company's security requirements for folders and reports, as well as report distribution
requirements for financial reporting batches.
Security can be set on folders and reports from Workspace. BI Catalog stores both the Financial Reports and the BI Publisher
Reports. You are granted access to the folders and reports you need to view by your BI administrator.
Create and Secure Folder Structure

To create a folder or sub-folder:
1. Navigator > Financial Reporting Center.
2. From the Financial Reporting Center task panel, select Open Workspace for Financial Reporting.
3. From within Workspace select the Navigator > Applications > BI Catalog.
4. On the Oracle BI Catalog page, go to the desired location in the Folders panel.
68
Chapter 5
5. In the Oracle BI Catalog tool bar, click New and select Folder.
6. The New Folder dialog is displayed. Enter the folder name.
7. OK.
To assign permissions to a folder:
2. From the Financial Reporting Center task panel, select Launch Workspace.
3. From within Workspace select the Navigator menu > Applications > BI Catalog.
4. Search for the folder to which you want to assign permissions.
69
Chapter 5
5. Go to the Tasks panel and click Permissions. The Permission dialog is displayed.
6. Click the Add users/roles button.
70
Chapter 5
7. In the Add Application Roles, Catalog Groups and Users dialog box, query the roles and select those desired.
In this example, select General Ledger Functional Administration Duty and General Ledger and Profitability
Managerial Duty.
8. Click the Move button.

9. Set Permission to the level desired. In this example, select Full Control.
10. OK.
Configure Smart View Client for Users

Smart View is a multidimensional pivot analysis tool combined with full Excel functionality. Smart View enables you to
interactively analyze your balances and define report using a familiar spreadsheet environment.
Load Smart View, an Excel add-in, to each client computer. To download the installation files from Workspace:
1. Navigator > Financial Reporting Center > Open Workspace for Financial Reports.
2. In Workspace: Tools > Install > Smart View.
3. Alternatively, download Smart View from http://www.oracle.com/technetwork/middleware/epm/downloads/smartview-1112x-1594693.html.
71
Chapter 5
Note
Since Smart View is an add-in to Microsoft Office products, you can install Smart View only on a Windows
operating system.
Once Smart View is installed, it must be configured to connect to Oracle Fusion Applications. Use the Smart View Shared
Connections URL. You can derive the Shared Connections URL by following the following steps.
1. Open Workspace for Financial Reports from the Financial Reporting Center.
2. Edit the Workspace URL, for example, if the Workspace URL is https://fusionsystemtest-p-externalbi.us.oracle.com/workspace/index.jsp. Remove index.jsp and add SmartViewProviders at the end of the URL.
If the Workspace URL is https://efops-rel5st4-cdrm-external-bi.us.oracle.com:10622/workspace/index.jsp,
the Shared Connections URL is https://efops-rel5st4-cdrm-external-bi.us.oracle.com:10622/workspace/
SmartViewProviders.
3. Copy the URL.
4. Launch Excel.
5. Navigate to the Smart View menu >Options
6. Select the Advanced option.
7. Paste the URL in the Shared Connections URL field.

8. Click the OK button.
For more information on configuring the Smart View client for users, see Oracle Hyperion Smart View for Office User's Guide
for Oracle Hyperion Smart View.
To connect Oracle Fusion General Ledger Balances cubes in Smart View:
1. Open Smart View from your Start menu > Programs > Microsoft Office > Microsoft Excel 2007.
2. Go to the Smart View menu > Open, in the Start on the ribbon > click on Smart View Panel that appears in the
drop down box under the ribbon. This launches a task pane.
3. Click the Shared Connections button on the task pane.
72
Chapter 5
4. Sign in with your user name and password.
5. Click the Select Server list icon to proceed.
Note
If the Essbase Server is not there, then it has to be added. Use the following steps:
a. Click the Add Essbase Server link on the bottom of the spreadsheet.
b. Specify the Essbase Server login and password.
c. Expand the Essbase server and locate its cube.
6. Select Oracle Essbase from the list of shared connections.
7. Click the Expand to expand the list of cubes.
73
Chapter 5
8. Expand your cube that has the name of your chart of accounts.
9. Click db. A list of functions appears on the bottom of the panel.

10. Click the Ad hoc analysis.
Note
You must perform the steps above only once for a new server and database.
To set how the name and alias of the Essbase database appears:
1. Click the Options on the ribbon > select the Member Options > select Member Name Display.
2. Set one of these three options:
Distinct Member Name: Only shows the full Essbase distinct path.
Member Name and Alias: Shows both the member name and the alias.
Member Name Only: Shows only the member name.
Note
The Smart Slice feature is not supported in Oracle Fusion General Ledger. For all other documentation, refer to
the Oracle Hyperion Smart View for Office User's Guide.
Configure Financial Reporting Studio Client for Users

Oracle Hyperion Financial Reporting Studio is client-based software tool used for authoring financial reports. Prerequisites
needed for installing the Financial Reporting Studio are:
1. Financial Reporting Studio Client Certifications found at: http://www.oracle.com/technetwork/middleware/bifoundation/hyperion-supported-platforms-085957.html.
2. The end user's computer requires Microsoft Office installations.
74
Chapter 5
You connect to the Financial Reporting Studio by downloading the installation files to your computer from Workspace.
Follow this path:
1. Navigator > Financial Reporting Center > Open Workspace for Financial Reports.
2. In Workspace: Tools > Install > Financial Reporting Studio.
After performing the prerequisites and completing the installation, launch the Financial Reporting Studio. You must provide
your user ID, password, and the Server URL. Derive the Server URL information by following the steps:
1. Open Navigator > Financial Reporting Center > Open Workspace for Financial Reports.
2. Edit the Workspace URL and remove workspace/index.jsp.
3. Two examples of Server URLs are:
If the Workspace URL is https://fusionsystemtest-p-external-bi.us.oracle.com/workspace/index.jsp, the

Financial Reporting Server URL is https://fusionsystemtest-p-external-bi.us.oracle.com.
If the Workspace URL is https://fusionsystemtest-p-external-bi.us.oracle.com:10622/workspace/index.jsp, the

Financial Reporting Server URL is https://fusionsystemtest-p-external-bi.us.oracle.com:10622.
4. Copy the modified URL to the Server URL field.

Note
For end users installing the Oracle Fusion Financials Reporting Studio, the installer launches a separate console
window that continues to run for a brief time after the installation completes the setup tasks. The process is
normal, expected, and applies to Oracle Hyperion Reporting Studio installations in both the Oracle Fusion
Applications and Enterprise Performance Manager modes.
You must save a new report before attempting to preview it with Web Preview.
For more information, see:
Oracle Enterprise Performance Management System Installation and Configuration Guide.
Oracle Hyperion Enterprise Performance Management System EPM System Standard Deployment Guide.
Define Essbase Database Connections in Workspace

You need to create database connections from Workspace so you can access the cubes from Workspace and Financial
Reporting Studio.
Note
Ledger setup has to be completed before the database connection can be created. Oracle Fusion General Ledger
balances cubes are created as part of ledger setup. There is a separate cube for each combination of chart of
accounts and accounting calendar. A database connection is needed for each cube.
Steps to define a database connection are:
75
Chapter 5
2. From the Financial Reporting Center task panel, select Open Workspace for Financial Reporting.
3. From within Workspace select the Navigator menu > Applications > BI Catalog.
4. Tools menu > Database Connection Manager.
5. Click New.
6. Enter a user friendly name for the Database Connection Name.
7. Enter Essbase as the Type, your server, user name, and password.
8. Select Application (cube) and Database from the list of values.
9. Expand the Application name to see the related database, for example, db.
10. OK twice to save your selections.

11. Close to save your connection.
For more information on configuring Essbase database connections in Workspace see: Oracle Essbase Database
Administrator's Guide.
76
Chapter 5
Note
The database connection is available in both Workspace and Financial Reporting Studio. Optionally, the database
connection can be setup in Financial Reporting Studio while entering the grids on a report.
Create Financial Statements: Explained

In Oracle Hyperion Financial Reporting Studio, you can design traditional financial report formats such as balance sheets,
profit and loss statements, and cash flow reports. You can also design nontraditional reports for financial or analytic data that
include text and graphics. Use Financial Reporting Studio that is a client-based application and is launched from your desktop
to create your reports. Perform the following basic tasks to begin defining this report.
1. Access the Financial Reporting Studio on your desktop.
77
Chapter 5
Tip
The first time you sign in, you must set the Server URL in this format: https://<servername>-biext.us.oracle.com:port.
2. New Report (1st icon on the tool bar) or File menu > New > Report.
3. Use the Report Pallet page as the container to build your report.
4. New Grid. (First icon in second set on the tool bar.)
5. Press the left mouse button and drag the mouse to select a large area of the grid in which to create your report.
6. Click the Database Connection list.
7. Select your database. A unique cube exists for each combination of chart of accounts and accounting calendar.
8. OK.
Set the Row, Column, and Page Points of View

Set the point of view dimensions and accounts for the rows, columns, and page levels.
1. Use the Dimension Layout window that opens to arrange your dimensions.
2. Drag and drop:
Accounting Period to Columns.

Account to Rows.
Company to Pages.
Tip
Click the icon in front of the name to select the dimension to drag to the designed area.
78
Chapter 5
3. OK.
4. Double-click on Account to open the Select Members dialog box to select the data to use in your report.
5. Click the Account list item in the Selected box on the right.
6. Remove in the center to remove the default Account.
7. Expand for Account node.
8. Expand:
All Corporate Accounts
[Account]@[T]
95001
9. Select 95011 Revenue.
79
Chapter 5
10. Add.
11. OK.
12. File > Save As...
13. Select My Folders.
14. Enter the name for the report: XXInFusion Income Statement.
15. Save.
16. Select the last row in the grid. Click the row header (row with the account in it).
17. Insert > Row > Text to add a blank row.
18. Right-click the row header.
19. Insert Row > Data to add another blank row.
20. Add expense accounts by double-clicking on account 95011 in line 3.
21. Remove the Selected account 95011.
22. Expand: > All Corporate Accounts - V1 > [Account]@[T] > 95001 > 95021 - Expenses
23. Select all three accounts: 50000, 60000, and 70000.
24. Add.
80
Chapter 5
25. Check the Place selections into separate rows check box on the bottom right.
26. OK > Save. Leave the report open for the next activity.
Add a Formula
Add a formula to calculate total expenses.
1. Right click the row header of the row below row 5.
2. Insert > Row > Formula.
3. Click in the blank cell on row 6.
4. Click the Custom Heading option in the panel on the right hand side of the window.
5. Add a custom heading: Total Expenses.
6. Click the formula cell at row 6 and column A.
7. Sum(). The formula Sum() is entered into the Edit box.
8. Enter [3], [4], [5].
9. After entering the formula, validate the syntax by clicking the blue check mark.
81
Chapter 5
(I) Save. Leave the report open for the next activity.
Define Columns Using a Range Function

Define the columns using a range function to create a rolling 12 period column type report.
1. In the first column on the grid, double-click the AccountingPeriod cell.
2. Remove the default selection to assign a custom period selection.
3. Click the AccountingPeriod in the Selected window.
4. Click Remove.
5. Select Functions.
6. Click the Range list item.
7. Add.
8. OK.
9. Use the Edit Range Function window to add the range function start and end members or to select a hierarchy to
use to select your report data.
10. Select the StartMember row.
11. Click in the Value field.
82
Chapter 5
12. Select Lookup > Functions.

13. Click the RelativeMember list item.
14. Add.
15. Select the Member row.
16. Click in the Value field > Lookup
17. Click the Current Point of View list item.
18. Add > OK..
19. The Offset value determines periods to include from the current point of view. Since this is a rolling 12 month report,
enter -12.
20. OK twice.
21. Click the EndMember list item > Lookup
22. Click the Current Point of View list item.
23. Add.
24. OK three times until you return to your report.
25. Save. Leave the report open for the next activity.
Define User Points of View

Define the user points of view for the dimensions and specify values for those dimensions.
1. Select the Grid object (The intersection of rows and columns on the left margin.)
2. Right-click the Grid object.
83
Chapter 5
3. Grid Point of View. The points of view appear across the top of the window.
4. Ledger: User Point of View for Ledger.
5. Expand:
Ledger
All Ledgers
6. Highlight the Ledger item to include in the report: InFusion USA PL.
7. Select Scenario.
8. Expand Scenario.
9. Select Actual as the Scenario member to determine what should be included in the columns.
10. Select Balance Amount.
11. Expand the Balance Amount.
12. Select Period Activity as the balance amount to include in the report.
13. Select Currency.
14. Expand Currency.
15. Search for and select USD from the list.
16. Click the USD list item.
84
Chapter 5
17. OK.
18. Right-click the Grid object.

19. Click the Grid Point of View Setup.
20. Scroll down and click the Balance Amount list button.
21. Select the Nothing, Lock Member Selection option.
22. OK.
23. Double-click the Pages object.
24. Remove.
25. Select the Prompt for Company list item.
85
Chapter 5
26. Add.
27. OK.
28. Select Lookup.
29. Click the Default Member list icon.
30. Remove.
31. Expand.
Company.
All Company Values.
32. Select the required companies: 101-US 1 LE 1 BU 1 and 102-US 1 LE 2 BU 2.

33. Add.
34. OK.
35. Click the Member Labels in Prompt Selection Dialog list button.
86
Chapter 5
36. Select the Alias list item.
37. OK.
38. Open the Page Properties dialog box on the right side of the window. If it does not open, click View menu >
Property Sheet.
39. Double-click the Pages object.
40. Click the Alias: Default option.
87
Chapter 5
41. Click the first cell in Row 1.

42. Open the Heading Row Properties dialog box on the right hand side of the window.
43. Click the Alias: Default option.
44. Click the Grid object.

45. Open the Grid Properties dialog box.
46. Click the Suppression list item.
88
Chapter 5
47. Enter 0 in the Zero Values field.
48. Open the Heading Row Properties dialog box.

49. Click an entry in the row.
50. Click the Allow Expansion option.
51. Click the Grid object.
52. Open the Grid Properties dialog box.
53. Click the Drill Through option. (On the very bottom of the window.)
54. Save. Leave the report open for the next activity.
Add Company Logo and Title

Insert your company's logo and add a title to the report.
1. Click Image. (Third icon in the second set of icons on the tool bar.)
2. Find your company's logo in your file system.
3. Click Open.
4. Drag and drop the cursor over the report pallet to determine the length and width of the image.
89
Chapter 5
5. Save.
6. Click Text. (Second icon in the second set of icons on the tool bar).
7. Drag and drop the cursor over the report pallet to determine the length and width of the title.
8. Enter Rolling 12 Month Income Statement.
9. Format > Font.
10. Select Bold and 14 as the Font Size.
11. Center Text.
12. File > Page Setup option.
13. Click Landscape.
14. Click Workspace Size. If needed, you can adjust the Width and Height with the up and down arrows.
15. OK > Save.
Preview Report
Preview the report both in the Financial Reporting Studio and the Financial Reporting Center.
In Financial Reporting Studio
1. File > Print Preview.
2. Accept the default selections.
90
Chapter 5
3. OK.
4. Use the Next Page to see all the columns.

5. Edit the report definition as needed.
In Financial Reporting Center
1. Sign in the Oracle Fusion Applications.
2. Navigator > General Accounting: Financial Reporting Center > My Folders > XXInFusion Income
Statement.
3. View as HTML.
4. OK to the Respond to Prompts window to keep the default companies.
91
Chapter 5
5. Click the AccountingPeriod.
6. Expand:
a. AccountingPeriod
b. 2012
92
Chapter 5
c. Qtr2-12
7. Select 02-12.
93
Chapter 5
8. OK.
94
Chapter 6
Create Chart of Accounts, Ledger, Legal Entities, and

Business Units in Spreadsheets: Explained
Represent your enterprise structures in your chart of accounts, ledger, legal entities, and business unit configuration to track
and report on your financial objectives and meet your reporting requirements. These components are the underlying structure
for organizing financial information and reporting.
The chart of accounts within the ledger facilitates:
Aggregating data from different operations, from within an operation, and from different business flows
Consistent definitions to your stakeholders in compliance with legislative and corporate reporting standards and aids
in management decisions.
Rapid implementation is a way to configure the Oracle Fusion Financial Enterprise and Financial Reporting Structures quickly
using sheets in a workbook to upload lists of:
Companies (Legal Entities)
Ledgers by Country
Business Units
Chart of Account Values
Financial Sequences
Hierarchies
Once the sheets have been uploaded, the application creates your:
Chart of Accounts Structure and Instance
Key Accounts such as Retained Earnings and Account Payables.
Calendar
Ledgers by Country
Legal Entities and Their Locations
Business Units
Document and Journal Sequences
95
Chapter 6
The following graphic shows the relationship of these components.
Legal Entities: Identifies a recognized party with rights and responsibilities given by legislation, which has the right
to own property and the responsibility to account for themselves.
Chart of Accounts: Configures accounts consisting of components called segments that are used to record
balances and organize your financial information and reporting.
Segments: Contains a value set that provides formatting and validation of the set of values used with that segment.
When combined, several segments create an account for recording your transactions and journal entries.
Segment Labels: Identifies certain segments in your chart of accounts and assigns special functionality to those
segments. The three required segment labels are:
Balancing Segments: Ensures that all journals balance for each balancing segment value or combination of
multiple balancing segment values to use in financial processes and reporting. The three balancing segment
labels are: primary, second, and third balancing. The primary balancing segment label is required.
Natural Account: Facilities processes in the General Ledger application, such as retained earnings posting.
For each child value, you must assign an Account Type. You can select from one of the general choices to
mark the account value as an Asset, Liability, Owner's Equity, Revenue, or Expense account.
96
Chapter 6
If the account is used by the Rapid Implementation solution to provide accounts for setup objects, select the
appropriate Expanded Account Type for the child account. Examples of expanded account types required for
setup objects are:
Owner's Equity - Retained Earnings to setup General Ledger ledgers.
Liability - Accounts Payable to setup Payables common options.
Asset - Account Receivable to setup Receivables receipt methods.
For accounts that are tagged with these special account types, the Financial Category defaults. You can
override the defaults in the Financial Category or leave it out.
Cost Center: Facilitates grouping of natural accounts by functional cost types, accommodating tracking of
specific business expenses across natural accounts.
Ledger: Maintains the records and is a required component in your configuration. The Rapid implementation
process:
Creates your ledgers by combining your chart of accounts, calendar, and currency as well as other required
options defined in the sheets.
Assigns a default for the fourth component, the subledger accounting method, used to group subledger journal
entry rule sets together to define a consistent accounting treatment.
Creates a balances cube for each ledger with a unique chart of accounts and calendar. Each segment is
created as a dimension in the balances cube.
Business Units with Business Functions: Identifies where subledger transactions are posted and provides
access to perform subledger business processes. Business units are assigned to a primary ledger, as well as a
default legal entity, when configured and identify where subledger transactions are posted.
Subledgers: Captures detailed transactional information, such as supplier invoices, customer payments, and asset
acquisitions. Uses subledger accounting to transfer transactional balances to the ledger where they are posted.
97
Chapter 6
Note
Hierarchies: You can create more than one hierarchy for any of your chart of accounts segments. You can also
create additional hierarchies after the spreadsheet has been loaded once.
Document and Journal Sequences: You can create sequences for each legal entity or ledger based on the
predefined country defaults. Document Sequences are created for:
Payables Invoices
Payments
Receivables Invoices
Receivables Credit Memos
Receivables Adjustment Activities
Reporting and Accounting Journal Sequences are created for:
Subledger Journals
General Ledger Journals
Create Chart of Accounts, Ledger, Legal Entities,

and Business Units in Spreadsheets: How They Are
Processed
The Create Chart of Accounts, Ledger, Legal Entities, and Business Units rapid implementation process consists of four
steps.
1. Enter the data into the sheets.
2. Upload the XML files generated from the sheets.
3. Run the deployment process to finalize the chart of accounts configuration.
4. Upload the XML files generated from the sheets for the rest of the configuration.
Note
On the Instruction sheet is a link to a completed sample data workbook.
98
Chapter 6
Process Overview
Begin by downloading the Rapid Implementation for General Ledger workbook using the Create Chart of Accounts,
Ledger, Legal Entities, and Business Units in Spreadsheet task on the Setup and Maintenance work area.
99
Chapter 6
The following figure illustrates the Create Chart of Accounts, Ledger, Legal Entities, and Business Units process, what data is
entered into each sheet of the workbook, and the components that the process creates.
Process
Enter Data
The Create Chart of Accounts (COA), Ledger, Legal Entities, and Business Units workbook provides five sheets.
1. Instructions
2. COA, Calendar and Ledger
3. Business Units
4. Companies and Legal Entities
5. Natural Accounts
100
Chapter 6
6. Financial Sequences
You create sheets to enter other segment values and hierarchies for additional segments by entering the segments on the
COA, Calendar, and Ledger sheet and then clicking the Add Segment Sheets or Create Hierarchies Only button.
Instructions Sheet
Read the planning tips, loading process, best practices, and recommendations.
COA, Calendar and Ledger Sheet

Enter your data to create your ledger, chart of accounts, currency, and calendar, and to set the required ledger options.
Name: Enter the name of your primary ledgers. The name often appears in report titles, so enter a printable name.
Note
A primary ledger is created for each unique country entered in the Companies and Legal Entities sheet.
For example, if one of the legal entities is based in the United States and another in Canada, and the
ledger name is InFusion Ledger, then two primary ledgers, InFusion Ledger US and InFusion Ledger CA,
are created.
All the primary ledgers that are created use the same chart of accounts, account hierarchies, and
accounting calendar. Legal entities and their primary balancing segment values are assigned to the
primary ledger of their respective countries.
Currency: Enter the ledger currency in which most of your transactions are entered if you are not entering legal
entity data. If you are entering legal entities, leave the field blank. The currency is supplied by default based on the
country.
Period Frequency: Select the frequency for your calendar.
Adjusting Periods: Select the number of periods that are used to enter closing, auditing, or other adjustments in
the General Ledger at quarter or year end. The entries are tracked in the adjusting period and not in your monthly
activity.
Fiscal Year Start Date: Enter the beginning date of your calendar for the ledgers. The date cannot be changed
after the ledgers are saved.
101
Chapter 6
Important
Select a period before the first period in which you plan to load history or perform translations to enable
running translation. You cannot run translation in the first defined period of a ledger calendar.
Chart of Accounts region: Enter your segments, segment labels, short prompts, and display width data that is
used to create your chart of accounts. Plan this data carefully because you are defining the basic structure for your
accounting and reporting.
Segment: Enter the names of your segments.
Segment Label: Select which segment the application uses for certain processing, such as the Primary
Balancing, which is used to balance journal entries.
Note
If you select an intercompany segment label, you must complete at least one intercompany rule
and check the Enable Intercompany Balancing option in the Specify Ledger Options task for the
Balancing API to perform intercompany balancing.
Short Prompt: Enter a short name for the application to use.
Display Width: Enter the segment size. Select carefully and leave room for growth. For example, if you have
89 cost centers, enter 3 for the display length to allow for more than 100 cost centers in the future.
Add Segment Sheets button: Select to create sheets for additional segments. Only the Company and Natural
Account segment sheets are provided.
Step 1: Validate button: Select to validate your entered data. A Validation Report is generated if any errors occur.
Correct these errors before proceeding.
Step 2: Generate Chart of Accounts File: Select to create a file that is then uploaded to create the chart of
accounts structures, values, and hierarchies.
Step 3: Generate Ledger, LE, and BU File: Select to create a file that is then uploaded to create ledgers, legal
entities and their locations, business units, and document and journal sequences.
Create Hierarchies Only button: Select to create sheets to enter additional hierarchies after setup has been run
one time.
Business Units Sheet

Enter the name of your business units and related default legal entities.
102
Chapter 6
Note
You can enter more than one business unit per ledger. Business units are created with entered names. Based on
the default legal entity entered in the Business Units sheet, the respective country's primary ledger is supplied by
default for the business unit (BU). The first legal entity that is associated with the ledger is supplied by default for
all the BUs of that country.
Companies and Legal Entities Sheet

Enter a list of your legal entities with their addresses, registration number, reporting unit registration number, and assigned
parent or child value. You can create up to 9 levels of parent values to use to roll up your legal entities to meet corporate and
local reporting requirements.
103
Chapter 6
Natural Accounts Sheet

Enter your account values that are used to record the type of balance.
Parent Values, Child Values and Descriptions: Entered to build hierarchies. Hierarchies are used for chart of
accounts mappings, revaluations, data access sets, cross validation rules, and segment value security rules. The
balances cube and account hierarchies are also used for financial reporting, Smart View queries, and allocations.
Account Type: Enter to identify the type of account: Asset, Liability, Revenue, Expense, or Owner's Equity. Account
types are used in year-end close processes and to correctly categorize your account balances for reporting.
If the account is used by the Rapid Implementation solution to provide accounts for setup objects, select the
appropriate Expanded Account Type for the child account. Examples of expanded account types required for setup
objects are:
Owner's Equity - Retained Earnings to setup General Ledger ledgers.
Liability - Accounts Payable to setup Payables common options.
Asset - Account Receivable to setup Receivables receipt methods.
For accounts that are tagged with these special account types, the Financial Category defaults. You can override the
defaults in the Financial Category or leave it out.
Financial Category button: Enter to identify groups of accounts for reporting with Oracle Fusion Transactional
Business Intelligence.
Generate Additional Hierarchy button: To create more than one hierarchy for any of your COA segments, click the
Generate Additional Hierarchy button on the country's sheet. This creates a worksheet and populates it with the data
already entered for that segment. Change this data as required for the new hierarchy. For the Company Segment, adding
Legal Entity information is not supported on the new hierarchy's sheet.
104
Chapter 6
Note
When you create a new hierarchy sheet the name is derived by adding a counter to the sheet name.
Click the button on Companies and Legal Entities sheet to generate a new sheet named Companies and Legal
Entities1.
Click the button again then another sheet with the name Companies and Legal Entities2 is generated.
When you generate the upload files, each of these sheets are treated as a separate tree of the segment. You can
create new hierarchies only and not new versions of existing hierarchies.
Financial Sequences Sheet

Enable your document or journal sequences to assign unique numbers to your transactions to meet legal requirements.
The transactions the Document sequences are created for include:

Payables Invoices
Payments
Receivables Invoices
Receivables Credit Memos
Receivables Adjustment Activities
Reporting and Accounting Journal Sequences are created for:
Subledger Journals
General Ledger Journals
Complete the following steps on the Financial Sequences sheet:
1. Enabled: Set to yes to enable document or journal sequences for the transaction type.
105
Chapter 6
2. Restart: Set to restart the numbering based on one of the following criteria:
Annually: Restart sequence numbers once a year.
Monthly: Restart sequence numbers each month.
Never: Never restart sequences numbers. Continue with the same sequence.
3. Initial Value: The beginning number in the sequence.
Upload the Sheets and Run Deployment

Return to the COA, Calendar, and Ledger sheet after completing the other sheets to complete the following steps:
1. (B) Step 1: Validate: The process validates your data entry.
2. (B) Step 2: Generate Chart of Accounts File: The process generates an XML data file for the entered chart of
accounts and hierarchies setup data. Save the file to a network or local drive.
3. (B) Step 3: Generate Ledger, Legal Entity, and Business Units File: The program generates an XML data file
for the entered ledger, legal entities, and business unit setup data. Save the file to a network or local drive.
4. (N) Setup and Maintenance > Functional Setup Manager > Upload Chart of Accounts task: The Upload
Enterprise Structures process is launched.
5. (B) Upload File.
6. Leave the Upload Enterprise Structure radio button selected.
7. (B) Browse: Select the first file that you saved: ChartOfAccounts.xml.
8. (B) Submit.
9. Verify that the process was completed without errors or warnings.
106
Chapter 6
10. (N) Setup and Maintenance > Deploy Chart of Accounts task > (B) Deploy the Accounting Flexfield.
11. (I) Refresh until the green check mark appears and verifies that the deployment is successful.
12. (N) Setup and Maintenance > Upload Ledger, Legal Entities, and Business Units task. The Upload
Enterprise Structures process is launched.
13. (B) Upload File.
14. Leave the Upload Enterprise Structure radio button selected.
15. (B) Browse. Select the second file that you saved: FinancialsCommonEntities.xml.
16. (B) Submit.
17. Verify that the process was completed without errors or warnings.
Tip
You cannot change the chart of accounts, accounting calendar, or currency for your ledgers after the setup is
created. Assign the data role that was automatically generated for the ledgers to your users. Then open the first
accounting period to begin entering data.
Create Hierarchies in a Spreadsheet: Example

Use the Hierarchies Only sheet to create new hierarchies or new versions of existing hierarchies after enterprise structures
have been created using the Rapid Implementation spreadsheet.
Scenario
Plan your new hierarchies or new versions carefully, including the following requirements:
Compile the hierarchy in the specified format and save the file.
Use the Account Type attribute that is mandatory for the Natural Account segment.
Optionally, use the Financial Category attribute for the Natural Account segment.
Note
Only one Hierarchies Only sheet can be created at a time. After uploading a hierarchy, delete the data in the
sheet and add new hierarchy data.
107
Chapter 6
Use the following steps to create your hierarchy.

1. Click the Create Only Hierarchies button on the COA, Calendar and Ledger sheet to generate the Hierarchies
Only sheet.
2. Compile the hierarchy in this sheet in the format provided.
3. Click the Validate button. A Validation Report is generated if there are any errors. Correct these errors to
proceed.
4. Correct these errors and proceed.
5. Click the Generate Hierarchy File button. The process generates a zip file for the new hierarchy. Save this file.
6. From the Setup and Maintenance page in the Functional Setup Manager, search for and select the Upload
Chart of Accounts task.
7. Click on the Upload Hierarchy radio button.
8. Select Create New Hierarchy or Create New Version radio button
9. Under the Create New Hierarchy option, select the Value Set, enter the Tree Code and Start Date.
10. Click the Choose File button.
11. Select the file you saved.
12. Click Submit.
13. Under the Create New Version option, select the Value Set and Tree Code.
14. Enter the Tree Version Name and Start Date.
15. Click the Choose File button and select the file you saved.
16. Click Submit.
17. Navigate to the Scheduled Processes page.
18. Verify that the process completed without errors or warnings.
GL Cross-Validation Rules: Overview

In Oracle Fusion General Ledger, use cross-validation rules to determine valid account combinations that are created
dynamically as your users enter transactions or journal entries. Once enabled, a cross-validation rule determines whether
a selected value for a particular segment of the account combination can be combined with specific values in the other
segments to form a new account combination.
A cross-validation rule is defined in terms of a condition filter and a validation filter.
The condition filter describes the event under which the rule is evaluated. If the event specified in the condition filter
isn't applicable, then the rule isn't evaluated even if it is enabled.
When the event specified in the condition filter is applicable, the validation filter condition must be satisfied before
the account combination can be created. The rule is evaluated using the following logic: If condition is satisfied, then
perform specified validations.
For example, if your organization has determined that a certain company value, Operations, cannot use a specific cost center,
Marketing, define the following cross-validation rule to validate your accounts accordingly: If company is equal to Operations,
then validate that cost center is not equal to Marketing.
If account combinations already exist and violate the newly enabled cross-validation rules, these account combinations
continue to be valid. Before disabling any existing account combinations that violate your rules and you are no longer using,
move the balances in those accounts to the correct accounts. Then disable the account combinations manually to prevent
further posting.
108
Chapter 6
Note
Best practice is to define and enable cross-validation rules before:
Balances are loaded.
Transactions or journal entries are imported or entered.
Account combinations are created.
Tip
When you export or import cross-validation rules using an export or import project in the Functional Setup
Manager to a new instance, you must add the Manage Messages for General Ledger task before the
Manage Cross-Validation Rules task. You must also perform the export or import of the messages before
export or import of the cross validation rules.
Related Topics
Cross-Validation Rules: Explained
Cross-Validation Rules: Points to Consider
Creating a Cross-Validation Rule: Example

Create cross-validation rules to prevent specific combinations of segment values in your account combinations, for example,
preventing a particular cost center from being combined with a specific company value. Cross-validation rules only affect the
creation of new account combinations.
Scenario
Enter a new cross-validation rule to prevent your InFusion America Inc. company value 01 from being combined with your
marketing department value 300 in an account combination. Your company, InFusion America Inc. does not have a marketing
department.
1. Navigator > Setup and Maintenance > Manage Cross-Validation Rules > Go to Task.
2. Select your InFusion America chart of accounts.
3. Create.
4. Specify a unique rule Name, IFAM01, and an optional Description. Do not combine Marketing Department, 300
with InFusion America, company 01.
5. Enter an optional effective From Date of today. Check Enabled.
6. Click the Change filter condition on the Condition Filter. Enter Company equal to 01. The cross-validation rule
evaluates if Company 01 was entered and if it was entered, then the validation process continues to evaluate the
rule.
109
Chapter 6
Note
If you do not specify any statement in the condition filter, then the rule is always evaluated.
7. Click on the Change filter condition on the Validation Filter. Enter Cost Center is not equal to 300. When the
rule is evaluated, an account combination must contain a cost center other than 300 before it can be created.
8. Enter an Error Message: Cost Center 300 is not allowed with Company 01. The message displays in the relevant
user interfaces and processes when an account combination cannot be created because it violates the rule.
9. Save and Close.

Use Microsoft Excel templates to rapidly implement the following setup objects:
Banks
Bank Branches
Bank Accounts
Functional Setup Manager Tasks

The following are the Functional Setup Manager tasks that are required to be performed to rapidly create the setup objects
data:
Create Banks, Branches, and Accounts in Spreadsheet: Downloads the rapid implementation excel spreadsheet
template. Enter the bank, branch, and bank account data in this spreadsheet, and generate the data file to be
loaded.
Upload Banks, Branches, and Accounts: Launches the Upload Banks, Branches, and Accounts process with the
data file to be uploaded as the parameter. You must upload the data file generated from the previous task.
Preparing Data
Prepare your bank, branch, and account information to enter into the spreadsheet template.
Bank information requires the country, name, and number.
Branch information requires name, number, BIC code, and alternate name.
Account information requires name, number, currency, legal entity, type, and IBAN.
After you finish preparing the data in the spreadsheet, click the Generate Banks, Branches, and Accounts File button. Save
the generated XML file.
Loading Data
Use the following steps to load your data.
From Functional Setup Manager, search for and select Upload Banks, Branches, and Accounts task. This task
launches the Upload Banks, Branches, and Accounts process.
Select the XML file you have saved earlier and submit the process.
Verify in the process monitor that the process completed successfully.
Review the banks, branches, and accounts created.
110
Chapter 6
Best Practices
The following are recommended best practices:
Determine the Legal Entity for each bank account. The Legal Entity must be associated to a primary ledger.
Determine the use for each bank account: Payable, Receivable, or both.
Determine the Cash and Cash Clearing account for each bank account. Enter the entire account combination based
on your chart of accounts, for example 01-000-1110-0000-000.
Related Topics
Processing Electronic Bank Statements: Explained

Use the Tax Configuration Workbook to upload all common tax setups into Oracle Fusion Tax. For example, create standard
state, county, and city sales tax rates within the US using this workbook.
Tax Configuration Workbook Worksheets

The Tax Configuration Workbook is a Microsoft Excel spreadsheet template with five common tax setup worksheets:
Worksheet
Predefined Data Content
Setup Options
Manage Tax Regimes
Yes
Option 1: Use the tax regimes

that are already included for 28
countries. You can modify or delete
any of the predefined tax regimes
where needed.
Option 2: Use tax partner

content for the Tax Configuration
Workbook.
Manage Taxes
Yes
Option 1: Use the taxes that are

already included for 28 countries.
You can modify or delete any of the
predefined taxes where needed.

Workbook.
Manage Rates
No
Option 1: Prepare the tax rates.

Workbook.
111
Chapter 6
Worksheet
Predefined Data Content
Setup Options
Manage Tax Recovery Rates
No
Option 1: Prepare the tax recovery

rates.

Workbook.
Manage Tax Rules
No
Option 1: Prepare the tax rules.

Workbook.
Related Topics
Creating Tax Setup Using the Tax Configuration

Workbook: Worked Example
This example shows how to create standard state, county, and city sales tax rates within the US using the Tax Configuration
Workbook.
The following table summarizes key decisions for this scenario:
Decision to Consider
In This Example
What tax setup are you creating?
Tax Rates
Do you have exception rules for calculating US sales tax

on transactions?
No
Do you use tax partner content?
No
Creating Tax Setup

The steps to create tax rates in the Tax Configuration Workbook are:
1. On the Manage Tax Regimes page, click Download Tax Configuration Workbook in the Rapid Setup
Spreadsheets list in the Search Results table.
112
Chapter 6
2. Save the Tax Configuration Workbook in your local directory.

3. Review the detailed Tax Configuration Workbook instructions tab.
4. For the Manage Tax Regimes and Manage Taxes worksheets, use the predefined content for US sales tax. You can
modify or delete the predefined content where needed.
5. Using the instructions and the column help text, populate the required setups in the Manage Rates worksheet.
6. After completing the Tax Rates worksheet, click the Generate CSV File button in the Instructions tab.
7. A macro launches and saves all of the:
a. Applicable Tax Configuration Workbook worksheets in a comma separated values (CSV) file format.
b. Individual CSV files into a single zipped file attachment.
8. Save the zipped file attachment in your local directory.
9. On the Manage Tax Regimes page, click Upload Tax Configuration Workbook in the Rapid Setup Spreadsheets
list in the Search Results table.
10. Browse your local directory in which you saved the zipped file attachment and select the file.
11. Click Open and then click Upload.
12. Note the process ID and access the Monitor Upload and Download Processes tab.
13. Click the Refresh icon and ensure that the process ID completes with a Succeeded status.
If the status of the upload process is Succeeded, you can view your setups using the search criteria in this
page.
If the upload process failed with a status other than Succeeded, check the details in the corresponding error
log, correct any file errors, and upload the file again.
Related Topics
Budget Uploads
Budget Uploads: Overview
In Oracle Fusion General Ledger, you load budget data to perform variance reporting.
If you use a third-party budgeting system or if you don't use a budgeting system, there are three ways to load budgets into
the GL Balances Cube.
Importing Budget Data from a Flat File: Export budget data from your budgeting application to a comma
separated values (csv) file. A sample xls template is provided in the Oracle Enterprise Repository (OER) for Oracle
Fusion Applications. Use this template to prepare and generate flat files in a csv format. You can use Oracle
Application Development Framework (ADF) Desktop Integrator correction worksheets to correct validation errors,
delete rows with errors, and resubmit the corrected error rows.
Importing Budget Data from a Spreadsheet: You can access the budget load spreadsheet from General
Accounting Dashboard: Enter, load, and correct budget data in an ADF Desktop Integrator spreadsheet tool.
113
Chapter 6
Use this tool to prepare and load budget data for multiple ledgers and periods with a common chart of accounts
instance. The list of values and the web picker help you pick valid values. This simplified data entry reduces errors
and alerts you to errors as you enter the data in the spreadsheet. Error correction is done in the same spreadsheet.
Smart View: Enter and load budget data in a Smart View spreadsheet. Use this tool to enter data for an account
across multiple periods on a single row.
Caution
When the GL Balances Cube is rebuilt, the process retains the budget balances as well as the actual balances.
Only the budget balances loaded using the spreadsheet or flat file through the GL Budget Balances interface table
are retained.
You must reload Budget balances loaded with Smart View after the Refresh Balance process is run. Create
reports in Smart View or Financial Reporting to verify that the budget data was loaded correctly.
Importing Budget Data from a Spreadsheet: Explained

Use Oracle Application Development Framework (ADF) Desktop Integrator to enter, load, and correct budget data. This
functionality uses a new interface table called the GL_BUDGET_INTERFACE and requires the duty role, Budget Entry Duty.
114
Chapter 6
Budget Import
Budget Import Oracle ADF Desktop Integrator import functionality is similar to the journal import sheet in Oracle Fusion
General Ledger. You may use this tool to create and upload budget data. From the General Accounting Dashboard page,
download the import worksheet.
The budget import uses the Accounting Scenario value set for the budget being loaded. The Run Name is used as an
identifier for the imported data set. The Oracle ADF Desktop Integrator budget import functionality:
Supports multiple ledgers but a single chart of accounts instance
Allows multiple calendars and periods
Supports entered currencies in addition to the ledger currency
Contains user friendly lists of values
Performs most validations on the worksheet
Secures values by data access sets
115
Chapter 6
Note
The ADF Desktop Integrator spreadsheet contains a Record Status column that shows if the rows upload
successfully or with errors. Use the spreadsheet where the data was entered to enter the corrections.
Importing Budget Data from a Flat File: Explained

Use the Upload Budgets processes to integrate budget information from other budgeting application such as Oracle Hyperion
Planning, Fusion Edition. You can load your budget amounts to the General Ledger balances cube by populating the
GL_BUDGET_INTERFACE table and running the Validate and Upload Budgets process. You can load budgets for multiple
periods and for multiple ledgers with the same chart of accounts in a single load process. Note that the budget data is not
loaded to the GL_BALANCES table and only loaded to the balances cube for variance reporting purposes.
Note
You can load data to interface tables using predefined templates and the Load Interface File for Import scheduled
process, which are both part of the External Data Integration Services for Oracle Cloud feature. For more
information, see the Documentation tab for the Load Interface File for Import process in Oracle Enterprise
Repository for Oracle Fusion Applications.
Assigning Values for Columns in the GL_BUDGET_INTERFACE Table

You must enter values in all the columns of the interface table that require values, which includes all of the not null columns, in
order for the budget import to be successful.
Enter values in the following required columns of the interface table:
Column Name
Values
RUN_NAME
Enter a name to identify the budget data set being

imported.
STATUS
Enter the value NEW to indicate that you are bringing

new budget data.
LEDGER_ID
Enter the appropriate ledger ID value for the budget

amount. You can view the ledger ID for your ledgers
in the Manage Primary Ledgers page. The ledger ID
column is hidden by default, but you can display it from
the View > Columns menu. If you enter multiple ledgers
for the same run name, all of the ledgers need to share
the same chart of accounts.
BUDGET_NAME
Enter the appropriate budget name value for the budget

line. You define your budget names in the Accounting
Scenario value set.
116
Chapter 6
Column Name
Values
PERIOD_NAME
Enter the period name that you are loading the budget
data for. Note that you can load budget data to Never
Opened, Future Enterable, and Open periods only.
CURRENCY_CODE
Enter the currency code for your budget.
SEGMENT1 to SEGMENT30
Enter valid enabled account value for each segment in

your chart of accounts.
BUDGET_AMOUNT
Enter the amount in the ledger currency for account

types, expense and assets.
OBJECT_ VERSION_ NUMBER
For Oracle Cloud implementations, leave this field blank

as the application automatically populates this when you
load the data from the secure FTP server to the interface
table. For other implementations, you can default the
column with a value of 1.
The following columns should be left as null as the budget import process uses these columns for internal processing or does
not use them in the current release.
CHART_OF_ACCOUNTS_ID
CODE_COMBINATION_ID
ERROR_MESSAGE
CREATION_DATE
CREATED_BY
LAST_UPDATE_DATE
LAST_UPDATE_LOGIN
LAST_UPDATED_BY
REQUEST_ID
LOAD_REQUEST_ID
Related Topics
External Data Integration Services for Oracle Cloud: Overview
Loading Data to the Budget Interface Table: Explained

Load the budget amounts to the interface table by following the steps below.
1. Export budget data from your budgeting application to a comma separated values (csv) file. You can use the
sample csv file or xls file that is provided in Oracle Enterprise Repository (OER) for Oracle Fusion Applications as a
reference.
117
Chapter 6
2. Upload the comma separated values (csv) file to the secure FTP server.
3. Select the parameters:
Select the process: General Ledger Validate and Load Budgets
Enter the name of the zipped CSV data file.
4. After the data is loaded to the interface table, you can run the Validate and Load Budgets process to load the
budget amounts to the General Ledger balances cube.
5. Review the logs for validation errors. If there are validation errors, use an ADF Desktop Integrator (ADFdi) correction
worksheet to download and correct the rows with errors. Then resubmit the data using ADFdi.
118
Chapter 6
Related Topics
Budget Correction with Oracle ADF Desktop Integrator: Explained
119
Chapter 7
Integration with Financial External Systems: Points to

Consider
Oracle Fusion Applications provides:
Flexibility for external systems integration.
Many spreadsheets as an easy method for entering and loading key setup data into the system.
The following are some of the ways you might use external system integration.
Tax and conversion rates
Payroll processing
Bank statement reconciliation
Budget preparation
Tax and Conversion Rates

Tax rates may vary depending on the geographical location of the customer or supplier, the type of product, and other
factors.
If your tax rates do not change frequently:
Enter or copy a tax rate feed of new or updated tax rates into the spreadsheet loader.
Upload the spreadsheet.
Note
Similar processes are used for foreign exchange conversion rates, which can change daily.
Few foreign currency transactions: Use the spreadsheet loader.
Many foreign currency transactions: Use a supplier for a direct load into the Daily Rates open interface. The
application validates the rows in the interface table and then makes changes in the Daily Rates table.
Payroll Processing
If you are processing your payroll using an application other than Oracle Fusion Global Payroll:
Use a spreadsheet template to load the data and create a postable journal entry in the Oracle Fusion General
Ledger.
120
Chapter 7
Post the journal entry to reflect the payroll expense on your financial statements.
Set up the file from the payroll system to summarizes payments by cost center rather than detailed employee data.
Summarized balances data is the level of detail relevant for the financial reporting and provides the confidentiality required for
payroll information,
Note
Oracle Fusion Financials marks the spreadsheet with clear error messages on the problematic rows, for example,
a new cost center that must be setup, for ease of correction.
Bank Statement Reconciliation

Bank statements are often received daily and follow a fixed format. With Oracle Fusion Cash Management:
Establish a transfer of the statements from the bank to the open interface.
Run the automated process to load the bank statement file.
Run the reconciliation process.
Note
If there are any errors in the file, the reconciliation process stops. The load process indicates the errors so you can
follow up with the bank and receive a corrected file.
Budget Preparations
There are two approaches to preparing your budgets:
1. For simple budgeting:
Distribute the current actual results and prior budget numbers to the relevant finance professionals using
spreadsheets.
Collect and consolidate the spreadsheets.

Load the spreadsheets to the Essbase cube.
Compare actual results against budgets using all of the Oracle Fusion Financials reporting and analysis tools,
including Account Monitor, Account Inspector, Smart View, and Financial Reporting.
2. For more complex budgeting use Oracle Hyperion Planning on the Oracle Cloud, alongside Oracle Fusion
Financials. Advantages include:
Advanced tools to handle complex budgeting scenarios.

Direct flow of data between the two applications.
Simplified distribution and collection of budget data.
Note
For more information on external data integration see: Oracle Financials Cloud Implementing Common
Features guide: External Integration chapter: External Data Integration Services for Oracle Cloud.
121
Chapter 7
122
Glossary
Glossary
abstract role
A description of a person's function in the enterprise that is unrelated to the person's job (position), such as employee,
contingent worker, or line manager. A type of enterprise role.
action
The kind of access named in a security policy, such as view or edit.
chart of accounts
The account structure your organization uses to record transactions and maintain account balances.
condition
An XML filter or SQL predicate WHERE clause in a data security policy that specifies what portions of a database resource
are secured.
data dimension
A stripe of data accessed by a data role, such as the data controlled by a business unit.
data role
A role for a defined set of data describing the job a user does within that defined set of data. A data role inherits job or
abstract roles and grants entitlement to access data within a specific dimension of data based on data security policies. A
type of enterprise role.
data role template
A template used to generate data roles by specifying which base roles to combine with which dimension values for a set of
data security policies.
data security
The control of access to data. Data security controls what action a user can taken against which data.
data security policy
A grant of entitlement to a role on an object or attribute group for a given condition.
database resource
An applications data object at the instance, instance set, or global level, which is secured by data security policies.
123
Glossary
enterprise
An organization with one or more legal entities under common control.
enterprise role
Abstract, job, and data roles are shared across the enterprise. An enterprise role is an LDAP group. An enterprise role is
propagated and synchronized across Oracle Fusion Middleware, where it is considered to be an external role or role not
specifically defined within applications.
entitlement
Grant of access to functions and data. Oracle Fusion Middleware term for privilege.
financial reporting book
Comprised of reports and other documents such as text, PDF, PowerPoint, Excel and Word files. When run, the report data
is dynamically retrieved from the database; the snapshot data remains static.
function security
The control of access to a page or a specific widget or functionality within a page. Function security controls what a user can
do.
job role
A role for a specific job consisting of duties, such as an accounts payable manager or application implementation consultant.
A type of enterprise role.
journal
An element of a journal entry consisting of the name, accounting date, category, ledger, and currency for single currency
journal entries. Used to group journal lines.
journal category
A name used to group journal entries with similar characteristics, such as adjustments, accruals, or reclassifications.
journal source
A name that indicates the origin of journal entries, such as payables, receivables, or manual. Used as an attribute in automatic
posting and journal import processes.
legal entity
An entity identified and given rights and responsibilities under commercial law through the registration with country's
appropriate authority.
offering
A comprehensive grouping of business functions, such as Sales or Product Management, that is delivered as a unit to
support one or more business processes.
124
Glossary
point of view
User selected dimensions that are not included in the grids at the row, column or page levels for a particular report. Only
these dimensions can be overridden at run time, unless user also specifically defined Prompt for the dimensions on the grid.
primary balancing segment value
A segment value used to represent a legal entity in the chart of accounts and automatically balance all intercompany and
intracompany transactions and journal entries.
role
Controls access to application functions and data.
role provisioning
The automatic or manual allocation of a role to a user.
security reference implementation
Predefined function and data security in Oracle Fusion Applications, including role based access control, and policies that
protect functions, and data. The reference implementation supports identity management, access provisioning, and security
enforcement across the tools, data transformations, access methods, and the information life cycle of an enterprise.
SQL predicate
A type of condition using SQL to constrain the data secured by a data security policy.
trading partner
An external party, such as a supplier, in the Oracle B2B application for which electronic documents are sent or from which
documents are received. A trading partner in Oracle B2B corresponds to a supplier site.
XML filter
A type of condition using XML to constrain the data secured by a data security policy.
125

Oracle Fusion Financials Cloud Implementation Guide

Uploaded by

Document Information

Copyright

Available Formats

Share this document

Share or Embed Document

Sharing Options

Did you find this document useful?

Is this content inappropriate?

Copyright:

Available Formats

Oracle Fusion Financials Cloud Implementation Guide

Uploaded by

Copyright:

Available Formats

Oracle

Oracle Financials Cloud Getting Started with Your Implementation

Oracle Financials Cloud

Getting Started with Your Implementation

Introducing Oracle Financials Cloud

Introduction to Implementing Oracle Financials Cloud: Overview

Working with Your System Integrator: Overview

Getting Started with Oracle Cloud

Purchasing and Activating Oracle Cloud Application Services: Highlights .................................................................. 6

Other Financials Security Considerations: Explained

Oracle Cloud Application Services Security: Explained

Define Implementation Users Tasks: Points to Consider

Creating Data Roles for Implementation Users: Procedure

Oracle Financials Cloud

Getting Started with Your Implementation

Implementing Oracle Financials Cloud

Getting Started with an Implementation: Overview

Define Financials Configuration for Rapid Implementation: Overview ........................................................................ 25

Implementing Enterprise Structures: Procedure

Implementing Cash Management: Procedure

Implementing Payables and Payments: Procedure

Implementing Expenses: Procedure

Implementing Receivables and Payments: Procedure

Intercompany Balancing Rules: Explained

Intercompany Balancing Rules: Examples

Defining Financial Data Security

Data Access Set Security: Overview

Data Access Set Security: Examples

Segment Value Security: Examples

Enabling Security on a Chart of Accounts: Example

Configuring Financial Reporting

Configure Smart View Client for Users

Configure Financial Reporting Studio Client for Users

Define Essbase Database Connections in Workspace

Create Financial Statements: Explained

Oracle Financials Cloud

Getting Started with Your Implementation

Uploading Data for Oracle Financials Cloud

Creating a Cross-Validation Rule: Example

Cash Management Rapid Implementation: Overview

Introduction to External Data Integration

Integration with Financial External Systems: Points to Consider

Oracle Financials Cloud

Getting Started with Your Implementation

Oracle Applications Help

Oracle Applications Guides

Other Information Sources

Oracle Enterprise Repository for Oracle Fusion Applications

Comments and Suggestions

Oracle Financials Cloud

Getting Started with Your Implementation

Introducing Oracle Financials Cloud

Introducing Oracle Financials Cloud

Introduction to Implementing Oracle Financials

Oracle Financials Cloud: Overview

Oracle Financials Cloud

Getting Started with Your Implementation

Introducing Oracle Financials Cloud

Oracle Financials Cloud

Getting Started with Your Implementation

Introducing Oracle Financials Cloud

Access data through pages that contain:

Oracle Financials Cloud

Getting Started with Your Implementation