Oracle® Fusion Applications
Financials Implementation Guide 11g Release 7 (11.1.7) Part Number E20375-08 |
![]() Home |
![]() Contents |
![]() Book List |
![]() Contact Us |
![]() Previous |
![]() Next |
This chapter contains the following:
Common Implementation: Overview
Getting Started with an Implementation: Overview
Define Financials Configuration for Rapid Implementation: Overview
Creating an Oracle Fusion Financials Rapid Implementation Project: Worked Example
Setup Data Import and Export for Oracle Fusion Financials: Explained
Manage Application Implementation
Common implementation involves accessing tasks that are available in multiple offerings, or that apply to multiple products and product families. The Define Common Applications Configuration task list and other activities include these common setup and implementation tasks.
You can find other information in support of common implementation in the Oracle Fusion Applications Concepts Guide.
In addition, you can customize and extend applications using various tools. For more information, see the Oracle Fusion Applications Extensibility Guide.
Use the Define Common Applications Configuration task list to set up and administer an implementation of behaviors across offerings.
Most Oracle Fusion Applications offerings include the Define Common Applications Configuration task list for implementing what is common in multiple or all Oracle Fusion applications. The task lists and tasks within Define Common Applications Configuration can be present in all offerings, some, or just a single offering.
Common implementation includes such tasks as setting up security, defining enterprise structures, configuring Oracle Fusion Applications Help, and setting options. Many of the common implementation tasks involve configuring reference objects provided by Oracle Fusion Middleware Extensions for Applications (Applications Core), such as messages, flexfields, document sequences, and profile options. Some common implementation tasks involve configuring features provided by Oracle Application Toolkit (ATK), such as the Watchlist. Other common implementation tasks involve Oracle Fusion Applications products such as the Assign Balancing Segment Values to Ledger task in Oracle Fusion General Ledger.
Other setup and maintenance tasks exist in multiple offerings but not in the Define Common Applications Configuration task list. Use these other task lists to define an Oracle Fusion Transactional Business Intelligence configuration, and to define extensions such as custom Oracle Enterprise Scheduler jobs.
You can access common implementation tasks and task lists by starting in the Setup and Maintenance Overview page and searching for task lists by name. Setup and Maintenance is available from the Administration menu to users provisioned with appropriate roles. The Administration menu provides access to other tasks, such as for customization.
Using the Financials offering, your enterprise can configure how you manage financial flows, including assets, ledgers, cash cycle, invoices and payments, accounts receivable, collections, and setup of subledger accounting and tax configuration.
Before you begin, use the Getting Started page in the Setup and Maintenance work area to access reports for each offering, including full lists of setup tasks, descriptions of the options and features you can select when you configure the offering, and lists of business objects and enterprise applications associated with the offering.
The first implementation step is to configure the offerings in the Setup and Maintenance work area by selecting the offerings and options that you want to make available to implement. For the Financials offering, you can select the following options:
Payables
Expenses
Fixed Assets
Receivables
Collections
Intercompany
Intercompany Transaction Flows
Financial Business Intelligence Analytics
Profitability Business Intelligence Analytics
General Ledger Business Intelligence Analytics
Accounts Payable Business Intelligence Analytics
Employee Expenses Business Intelligence Analytics
Intrastat Reporting
Next, create one or more implementation projects for the offerings and options that you want to implement first, which generates task lists for each project. The application implementation manager can customize the task list and assign and track each task.
If you select all of the options, the generated task list for this offering contains the groups of tasks listed in the following table:
Task List |
Description |
---|---|
Define Common Applications Configuration |
Manage definitions used across offerings, typically applying to multiple products and product families. These definitions include enterprise structures, workforce profiles, security, and approval rules, and more. You can find other information that supports the common implementation tasks in the Oracle Fusion Applications Concepts Guide. |
Define Common Financials Configuration |
Create and maintain tax setup according to local and international tax requirements and to apply tax data to the transaction line. |
Define Invoicing and Payments Configuration |
Define and maintain prerequisite setup components for the payables configuration required for Oracle Fusion Procurement. |
Define Expenses Configuration |
Maintain corporate expense policies and rules, expense types, and expense report approval rules. Configure corporate card issuers, programs, and cards. |
Define Fixed Assets Configuration |
Define and maintain fixed assets configurations, which are required to manage fixed assets. |
Define Receivables Configuration |
Define the configuration for the Oracle Fusion Receivables environment. |
Define Collections |
Configure components specific to collections. Configure profile options, lookups, descriptive flexfields, and other common components. |
Define and Maintain Intercompany Processing Rules |
Define intercompany accounts and intercompany transaction processing rules to be used for intercompany balancing and intercompany transactions. |
Define Hyperion Financial Management Integration |
Define and manage options that are used to configure the integration with Hyperion Financial Management. |
Define Budget Configuration |
Define and manage options that are used for budgeting. |
Define Financial Reporting |
Define and manage configuration options for the Fusion Financial Reporting Center. |
Define Transactional Business Intelligence Configuration |
Configure Oracle Transactional Business Intelligence for ad hoc reporting, including managing the repository, connections, presentation catalog, and currency type display. |
Define Extensions for Financials |
Define extensions such as custom Oracle Enterprise Scheduler jobs. You can also customize and extend applications using other tools. For more information, see the Oracle Fusion Applications Extensibility Guide. |
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 Application Services implementations. Because Oracle Fusion Applications is secure as delivered, the process of enabling the necessary setup access for initial users requires several specialized steps when getting started with an implementation.
The following high level steps are required for starting an implementation.
If you are not starting an Oracle Cloud Application Services 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.
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 Application Services administrator user.
Select an offering to implement, and generate the setup tasks needed to implement the offering.
Perform the following security tasks:
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.
Create an IT security manager user by using the Create Implementation Users task.
Provision the IT security manager with the IT Security Manager role by using the Provision Roles to Implementation Users task.
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.
Create an implementation user by using the Create Implementation Users task.
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 Application Implementation Consultant job role inherits from all product-specific application administrators and entitles the necessary View All access to all secured object.
Optionally, create a data role for an implementation user who needs only the limited access of a product-specific 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.
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.
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. |
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.
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
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:
Decision to Consider |
In This Example |
---|---|
What Oracle Fusion applications are included in this implementation? |
The Oracle Fusion applications being implemented are:
|
Are the setup requirements unique to this organization? |
No |
Can the rapid implementation task lists and tasks be used for this implementation? |
Yes |
The following sections describe the manual tasks that you must complete as part of the setup data export and import processes for the Oracle Fusion Financials offering.
Section |
Description |
---|---|
Setup tasks performed before export |
You must perform these tasks prior to initiating export processes for the Financials offering. |
Setup tasks performed before import |
You must perform these tasks prior to initiating import processes for the Financials offering. |
Setup tasks performed after import |
Setup data for these tasks is not imported from the source instance. Review and perform the manual setups steps on the target instance as required. |
Setup tasks not requiring data import |
These setup tasks do not require data import. Perform these tasks on the target instance as required. |
Refer to the Oracle Fusion Functional Setup Manager User's Guide for the steps to perform setup data export and import processes.
Prior to initiating export processes from the source instance, you must verify and update setup for the following task. This is required to ensure that data is correctly imported into the target instance.
Activity Name |
Task Name |
Setup Steps |
---|---|---|
Define Chart of Accounts |
Manage Account Combinations |
Account combinations are not exported from the source instance. Before exporting, navigate to the Manage Chart of Accounts Instance page on the source instance and verify that dynamic insertion is enabled for your charts of accounts. As long as dynamic insertion is enabled, account combinations are created automatically as needed on the target instance. |
Prior to initiating import processes into the target instance, you must verify and update setup for the following task.
Activity Name |
Task Name |
Setup Steps |
---|---|---|
Define Common Applications Configuration for Financials |
Define Implementation Users |
The import process does not include implementation users and roles associated with them. For more information, see Oracle Fusion Middleware Enterprise Deployment Guide for Oracle Identity Management (Oracle Fusion Applications Edition). |
Setup data for the following tasks will not be imported. Review these tasks for relevance to your implementation. For relevant tasks, access the corresponding setup pages from your implementation project to create the setup on the target instance as needed.
Activity Name |
Task Name |
---|---|
Define General Ledger Options |
Manage Journal Approval Rules |
Define Approval Management for Financials |
|
Define Tax Geographies |
Manage Tax Geographies |
Define Payables |
|
Define Image Processing |
Configure Document Capture Parameters |
Define Expense Policies and Rules |
|
Define Customer Billing Configuration |
Manage Salesperson Account References |
Define Customer Payments |
Manage Receivables Specialist Assignment Rules |
Setup data for the following tasks will not be imported from the source instance. Review the steps in the following table to create the setup on the target instance as needed.
Activity Name |
Task Name |
Setup Steps |
---|---|---|
Define Credit Card Data |
Extend Employee Matching Rules |
Write custom PL/SQL code to extend the predefined criteria for automatically matching new corporate cards to employees to incorporate your company-specific criteria. If you use a custom matching rule, then the PL/SQL package is not imported to the target instance. You can create the package in the target instance or copy the package to the target instance and compile it. |
Define Customer |
Create Customer |
Manually create customers, using the Create Customer task in Functional Setup Manager, or import customer information by running the Trading Community Model Data Import program. |
Define Customer |
Manage Customers |
Manually maintain customer information using the Manage Customer task in Functional Setup Manager, or by running the Trading Community Model Data Import program. |
Configure Payment System Connectivity |
Manage BI Publisher Templates |
Manually import any new or updated Oracle Business Intelligence Publisher (Oracle BI Publisher) templates. Use the Oracle BI Publisher archiving feature, or alternatively perform the following steps:
|
Define Subledger Accounting Rules |
Import Supporting Reference Initial Balances |
This task allows upload of initial subledger balances for supporting references. These balances are not imported from the source instance, but can be loaded directly to the target instance. For more information, see Oracle Fusion Accounting Hub Implementation Guide, Define Accounting Transformation. |
Configure Payment System Connectivity |
Integrate External Payment Systems |
Setup entities resulting from this integration will be exported and imported through the Transmission Configuration service. However, any work performed outside of Oracle Fusion Applications to integrate with a payment system needs to be applied to the production environment manually. Examples include custom code, routers, or dedicated lines to facilitate communication. |
Define Payments Security |
Manage System Security Options |
This setup cannot be imported and must be set up again in a production instance. Use the steps documented in the Oracle Fusion Applications Post-Installation Guide. |
Manage Expense Report Audit Selection Rules |
Manage Expense Report Receipt and Notification Rules |
The import process indicates an error at this task. Use the Manage Expense Report Receipt and Notification Rules tasks to manually create Receipt and Notification Rules on the target instance as needed. |
Define Financial Reporting Center Configuration |
Configure Smart View Client for Users |
Manually reconfigure the Smart View client to point to the production instance. For more information about configuring the Smart View client for users, see:
|
Define Financial Reporting Center Configuration |
Define Essbase Database Connection in Workspace |
Manually reconfigure the Essbase database connection in Hyperion Workspace. For more information about configuring the Hyperion Workspace Database Connection, see Oracle Fusion Accounting Hub Implementation Guide, Define Financial Reporting, |
Define Financial Reporting Center Configuration |
Configure Financial Reporting Studio Client for Users |
Manually reconfigure the Financial Reporting Studio client to point to the production instance. For more information about configuring the Financial Reporting Studio client for users, see: Oracle Fusion Accounting Hub Implementation Guide, Define Financial Reporting. Oracle Enterprise Performance Management System Installation and Configuration Guide for Oracle Enterprise Performance Management. Refer to the following topics:
|
Define Financial Reporting |
Create Financial Statements |
Export the financial report definitions from Workspace in the source environment. When exporting, you can export a single report, multiple reports in a zip file, or an entire folder structure in a zip file.
Import the file into Workspace in the target environment.
If you import the folder structure, the entire structure from the source instance is imported into the existing structure on the target instance. This could result in some redundant folders. In this case, you can reorganize child folders in the structure on the target instance and delete any unneeded folders. |
Define Period Close Components |
Manage Allocations and Periodic Entries |
Export the allocation rules, rule sets, variables, and runtime prompt definitions from Calculation Manager in the source environment. When exporting, you can export at the application level or at a single rule or rule set level. Note You must export and import rules for each application on the Essbase server separately.
Import the file into Calculation Manager in the target environment.
|
Define Hyperion Financial Management Integration |
Define Hyperion Financial Management Configuration |
Manually import the rules using the Oracle Enterprise Performance Management Life Cycle Management tool. For more information, see the Oracle Hyperion Artifact Life Cycle Management Utility User's Guide. |
Define Hyperion Financial Management Integration |
Define ERP Integrator Configuration for Hyperion Financial Management |
Manually import the rules using the Oracle Enterprise Performance Management Life Cycle Management tool. For more information, see the Oracle Hyperion Artifact Life Cycle Management Utility User's Guide. |
Define Budget Configuration |
Define Budget Configuration in Hyperion Planning |
Manually import the rules using the Oracle Enterprise Performance Management Life Cycle Management tool. For more information, see the Oracle Hyperion Artifact Life Cycle Management Utility User's Guide. |
Define Budget Configuration |
Define ERP Integrator Configuration for Hyperion Planning |
Manually import the rules using the Oracle Enterprise Performance Management Life Cycle Management tool. For more information, see the Oracle Hyperion Artifact Life Cycle Management Utility User's Guide. |
The following tasks in the setup task list are available to support your overall implementation approach. These tasks do not require any data to be imported. You can perform these tasks on the target instance as required.
Activity Name |
Task Name |
---|---|
Define Occasional Tax Implementation Setups |
Run Tax Configuration Content Upload Program |
Verify Tax Configuration |
|
Define Fixed Assets Configuration |
Verify Data Role Generation for Asset Books |
Define Disbursements |
Grant Payment Function Access |
Configure Payment System Connectivity |
View Validations |
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
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
P6 EPPM Administrator's Guide for an Oracle Database
P6 EPPM Administrator's Guide for Microsoft SQL Server Database
An implementation project is the list of setup tasks you need to complete to implement selected offerings and options. You create a project by selecting the offerings and options you want to implement together. You manage the project as a unit throughout the implementation lifecycle. You can assign these tasks to users and track their completion using the included project management tools.
You can also create an implementation project to maintain the setup of specific business processes and activities. In this case, you select specific setup task lists and tasks
Implementation projects are also the foundation for setup export and import. You use them to identify which business objects, and consequently setup data, you will export or import and in which order.
When creating an implementation project you see the list of offerings and options that are configured for implementation. Implementation managers specify which of those offerings and options to include in an implementation project. There are no hard and fast rules for how many offerings you should include in one implementation project. The implementation manager should decide based on how they plan to manage their implementations. For example, if you will implement and deploy different offerings at different times, then having separate implementation projects will make it easier to manage the implementation life cycles. Furthermore, the more offerings you included in an implementation project, the bigger the generated task list will be. This is because the implementation task list includes all setup tasks needed to implement all included offerings. Alternatively, segmenting into multiple implementation projects makes the process easier to manage.
Offerings are application solution sets representing one or more business processes and activities that you typically provision and implement as a unit. They are, therefore, the primary drivers of functional setup of Oracle Fusion applications. Some of the examples of offerings are Financials, Procurement, Sales, Marketing, Order Orchestration, and Workforce Deployment. An offering may have one or more options or feature choices.
The configuration of the offerings will determine how the list of setup tasks is generated during the implementation phase. Only the setup tasks needed to implement the selected offerings, options and features will be included in the task list, giving you a targeted, clutter-free task list necessary to meet your implementation requirements.
Offerings and their options are presented in an expandable and collapsible hierarchy to facilitate progressive decision making when specifying whether or not an enterprise plans to implement them. An offering or its options can either be selected or not be selected for implementation. Implementation managers decide which offerings to enable.
The Provisioned column on the Configure Offerings page shows whether or not an offering is provisioned. While you are not prevented from configuring offerings that have not been provisioned, ultimately the users are not able to perform the tasks needed to enter setup data for those offerings until appropriate enterprise applications (Java EE applications) are provisioned and their location (end point URLs) is registered.
Each offering in general includes a set of standard functionality and a set of optional modules, which are called options. For example, in addition to standard Opportunity Management, the Sales offering includes optional functionality such as Sales Catalog, Sales Forecasting, Sales Prediction Engine, and Outlook Integration. These optional functions may not be relevant to all application implementations. Because these are subprocesses within an offering, you do not always implement options that are not core to the standard transactions of the offering.
Offerings include optional or alternative business rules or processes called feature choices. You make feature selections according to your business requirements to get the best fit with the offering. If the selected offerings and options have dependent features then those features are applicable when you implement the corresponding offering or option. In general, the features are set with a default configuration based on their typical usage in most implementations. However, you should always review the available feature choices for their selected offerings and options and configure them as appropriate for the implementation.
You can configure feature choices in three different ways:
If a feature can either be applicable or not be applicable to an implementation, a single checkbox is presented for selection. Check or uncheck to specify yes or no respectively.
If a feature has multiple choices but only one can be applicable to an implementation, multiple choices are presented as radio buttons. You can turn on only one of those choices.
If the feature has multiple choices but one or more can be applicable to an implementation then all choices are presented with a checkbox. Select all that apply by checking the appropriate choices.