Browser version scriptSkip Headers

Oracle® Fusion Accounting Hub Implementation Guide
11g Release 7 (11.1.7)
Part Number E20374-07
Go to Documentation Home
Home
Go to contents  page
Contents
Book<br />List
Book
List
Go to Feedback page
Contact
Us

Go to previous page
Previous
Go to previous page
Next
PDF

1 Fusion Accounting Hub Overview

This chapter contains the following:

Define Fusion Accounting Hub Configuration for Rapid Implementation: Overview

Oracle Fusion Accounting Hub Features: Overview

Oracle Fusion Accounting Hub: How It Works

Accounting Configuration Offerings: Overview

Implementation Options for Oracle Fusion Accounting Hub: Overview

Setup Data Import and Export for Oracle Fusion Accounting Hub: Explained

Manage Application Implementation

Define Fusion Accounting Hub Configuration for Rapid Implementation: Overview

Use the Define Fusion Accounting Hub 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 Accounting Hub applications.

The rapid implementation task list includes tasks that are:

To create an implementation project that includes the Define Fusion Accounting Hub 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 Fusion Accounting Hub offering task lists and tasks to your rapid implementation project to change and update your setup.

Task Lists

The Define Fusion Accounting Hub Configuration for Rapid Implementation task list contains the following task lists:


Task List

Description

Define Enterprise Structures Configuration for Rapid Implementation

Define the enterprise structures configuration for Oracle Fusion Accounting Hub rapid implementation that includes financial and enterprise structures.

Define Accounting Entry Configuration for Rapid Implementation

Define the accounting entry configuration for Oracle Fusion Accounting Hub rapid implementation that includes accounting transformation rules for transactions sourced from external systems.

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 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 Fusion Accounting Hub Configuration for Rapid Implementation task list.

Creating an Oracle Fusion Accounting Hub Rapid Implementation Project: Worked Example

This example shows how to create an implementation project for the Oracle Fusion Accounting Hub 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:

  • General Ledger

  • Subledger Accounting

  • Financial Reporting Center

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. On the Setup and Maintenance work area, click the Manage Implementation Projects link.
  2. Click Create.
  3. Enter Implementation Project-FAH_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. Click Add in the Task Lists and Tasks table.
  7. On the Select and Add: Task Lists and Task dialog window enter %Rapid Implementation% in the Name field. Use wild card characters if you do not know the exact name of the task list or task.
  8. Click the Search button.
  9. Select the Define Fusion Accounting Hub Configuration for Rapid Implementation row.
  10. Click the Done button.
  11. Click Expand to expand the task list to see the task lists and tasks associated with your implementation project.
  12. Click the Done button.

Oracle Fusion Accounting Hub Features: Overview

Oracle Fusion Accounting Hub (FAH) provides a complete set of accounting tools and unparalleled access to financial data.

It includes:

Oracle Fusion Accounting Hub: How It Works

The Oracle Fusion Accounting Hub process can begin by using financial data from any or all of the following:

The Accounting Hub process ends with complete reporting and analysis solutions.

The Oracle Fusion Accounting Hub Components

The Accounting Hub contains the following components:

This figure shows the flow of transactions
from non-Oracle external applications and Oracle Fusion Subledgers,
through the Oracle Fusion Subledger Accounting (SLA) engine and repository.
And then, the SLA journal entries are transferred to the Oracle Fusion
General Ledger and into the balances cube and tables. The figure also
shows other integration features of the Oracle Fusion Accounting Hub,
which are described in the text below.

Oracle Fusion Subledger Accounting for External Systems

The Oracle Fusion Accounting Hub allows you to use Subledger Accounting to perform accounting transformations on external, non-Oracle system data. Subledger Accounting is also used to flexibly create accounting for Oracle subledgers such as Oracle Payables and Receivables. Subledger Accounting includes:

Oracle Fusion General Ledger

The Oracle Fusion General Ledger combines traditional general ledger functionality with embedded Oracle Hyperion Essbase functionality. The General Ledger functionality includes:

Financial Reporting Center

The Oracle Fusion General Ledger provides a Financial Reporting Center with robust financial reporting and analysis using data from your balances cubes. The dimensions contained in your chart of account segments become the direct source of multidimensional analysis. Direct links are maintained to your transactional data permitting comprehensive drill down from journals to transaction details. Use the following tools for your reporting and analysis:

The Oracle Fusion Accounting Hub fits into Oracle's broader enterprise performance management framework via integration with Oracle Hyperion Planning, Fusion Edition and Oracle Hyperion Financial Management, Fusion Edition, You can perform:

Integration with Hyperion Data Management

Oracle Fusion Accounting Hub is integrated with Oracle Hyperion Data Relationship Management, Fusion Edition, which is a master data management solution for creating and maintaining hierarchies across your enterprise. This integration allows you to maintain your charts of accounts values and hierarchies in one central location, and then to synchronize your hierarchies in Oracle Fusion and E-Business Suite General Ledgers. With licensing and integration of Data Relationship Management, you can:

Integration with E-Business Suite and PeopleSoft General Ledgers

Integration between the Oracle E-Business Suite, Oracle PeopleSoft, and Oracle Fusion General Ledgers can be used to support an applications coexistence strategy. This strategy permits you to continue to use your E-Business Suite or PeopleSoft applications while also using the Oracle Fusion Accounting Hub. Application coexistence provides the ability to:

Accounting Configuration Offerings: Overview

The Setup and Maintenance work area in the Oracle Fusion Applications is used to manage the configuration of legal entities, ledgers, and reporting currencies that comprise your accounting configuration. To create a new legal entity or ledger, your implementation consultant or system administrator must create an implementation project. This implementation project can be populated by either adding a financials related offering or one or more task lists.

Note

Setup tasks that are not related to the ledger or legal entity specific setup tasks can be invoked from either an implementation project or launched directly from the Setup and Maintenance work area.

There are two offerings predefined for financial implementations.

When adding an offering to an implementation project, implementation consultants can customize the tasks displayed by adding additional tasks to the implementation project.

Implementation Options for Oracle Fusion Accounting Hub: Overview

The Oracle Fusion Accounting Hub has three possible implementation scenarios that can be used separately or in conjunction with each other. These three scenarios are:

This figure shows the flow of transactions
from non-Oracle external applications and Oracle Fusion Subledgers,
through the Oracle Fusion Subledger Accounting (SLA) engine and repository.
And then, the SLA journal entries are transferred to the Oracle Fusion
General Ledger and into the balances cube and tables. The figure also
shows other integration features of the Oracle Fusion Accounting Hub,
which are described in the text below.

Coexistence with E-Business Suite and PeopleSoft

Oracle Fusion Accounting Hub provides embedded integration with the Oracle E-Business Suite and Oracle PeopleSoft General Ledgers. The integration has three main components:

See the following guides for details on implementing this scenario:

Accounting for Diverse Transactions

The Oracle Fusion Accounting Hub provides accounting for diverse business system events and transactions using configurable and auditable rule based accounting transformations. The Accounting Hub process begins with transactions and data from your non-Oracle, industry specific subledgers and other general ledgers. Subledger and general ledger applications that generate accounting events invoke the Create Accounting process to create journals that can be posted to the Oracle Fusion General Ledger. The process ends with complete reporting and analysis solutions.

See the following for details on implementing this scenario: Define Accounting Transformation Configuration chapter in the Oracle Fusion Accounting Hub Implementation Guide.

Expansion of Financial Reporting

Oracle Fusion Accounting Hub enables creation of multidimensional, self service reporting and analytics with real time accounting information from a single source with flexible formatting options. The Financial Reporting Center includes predefined financial reports, the ability to create new reports, and flexible options for dissemination of such reports. The Financial Reporting Center also includes the Account Monitor and Inspector, providing drill down and pivot views of your balances. Oracle Hyperion Smart View provides spreadsheet analytics and Oracle Transaction Business Intelligence, Oracle Business Intelligence Analytics, and Oracle Business Intelligence Publisher provide key performance indicators (KPI), dashboards, and flexible reporting.

See the following guides for details on implementing this scenario:

Setup Data Import and Export for Oracle Fusion Accounting Hub: Explained

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 Accounting Hub offering.


Section

Description

Setup tasks performed before export

You must perform these tasks prior to initiating export processes for the Fusion Accounting Hub offering.

Setup tasks performed before import

You must perform these tasks prior to initiating import processes for the Fusion Accounting Hub 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.

Refer to the Oracle Fusion Functional Setup Manager User's Guide for the steps to perform setup data export and import processes.

Setup Tasks Performed Before Export

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.

Setup Tasks Performed Before Import

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 Fusion Accounting Hub

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 Tasks Performed After Import

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

  • Manage Document Sequences

Define Document Sequences

Manage Document Sequences

Define Approval Management for Financials

  • Manage Task Configurations for Financials

  • Manage Approval Groups for Financials

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 Accounting Transformation Configuration

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.

Define Financial Reporting

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:

  • Oracle Fusion Accounting Hub Implementation Guide, Define Financial Reporting

  • Oracle Enterprise Performance Management System Installation and Configuration Guide for Oracle Enterprise Performance Management, Installing Smart View and other topics

  • Oracle Hyperion Smart View for Office User's Guide for Oracle Hyperion Smart View

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:

  • Installing Financial Reporting Studio and Financial Reporting Print Server

  • Configuring the Financial Reporting Print Server

  • Administrative Information for Financial Reporting

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.

  1. Navigator > General Accounting: Financial Reporting Center > select link: Open Workspace for Financial Reports.

  2. Navigate to Applications > BI Catalog.

  3. Navigate to File > Export.

  4. Save the file to the local desktop.

Import the file into Workspace in the target environment.

  1. Navigator > General Accounting: Financial Reporting Center > select link: Open Workspace for Financial Reports.

  2. Navigate to Application > BI Catalog.

  3. Navigate to File > Import.

  4. Select the file you had saved during the export.

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.

  1. Navigator > General Accounting: Journals > select link: Create Allocation Rules.

  2. Navigate to File > Export.

  3. Save the file to the local desktop.

Import the file into Calculation Manager in the target environment.

  1. Navigator > General Accounting: Journals > select link: Create Allocation Rules.

  2. Select the specific application in which to import the rules.

  3. Navigate to File > Import.

  4. Select the file you saved during the export.

Define Applications Coexistence Configuration for E-Business Suite

Manage Calendar Mappings for E-Business Suite

The import process does not include the calendar mappings of source Oracle E-Business Suite accounting calendars to target Oracle Fusion accounting calendars. If you use a calendar mapping, you must create it manually in your production Oracle E-Business Suite instance.

For more information, see Oracle Fusion Accounting Hub Implementation Guide, Define Applications Coexistence Configuration.

Define Applications Coexistence Configuration for E-Business Suite

Manage Ledger Mappings for E-Business Suite

The import process does not include the mappings of source Oracle E-Business Suite ledgers to target Oracle Fusion ledgers. You must create the ledger mappings manually in your production Oracle E-Business Suite instance.

For more information, see Oracle Fusion Accounting Hub Implementation Guide, Define Applications Coexistence Configuration.

Define Applications Coexistence Configuration for E-Business Suite

Register Applications Coexistence Instances for E-Business Suite

The import process does not include the registration of source Oracle E-Business Suite instances. You must manually register your source Oracle E-Business Suite instance or instances in the Oracle Fusion target instance.

For more information, see Oracle Fusion Accounting Hub Implementation Guide. Define Applications Coexistence Configuration.

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.

Manage Application Implementation

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:

With Oracle Fusion Functional Setup Manager you can:

The following documentation resources are available for learning how to configure Oracle Fusion Applications.

Implementation Projects: Explained

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.

Maintaining Setup Data

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

Exporting and Importing

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.

Selecting Offerings

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: Explained

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.

Implementation Task Lists

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.

Enabling Offerings

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.

Provisioning Offerings

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.

Options: Explained

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.

Feature Choices: Explained

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:

Yes or No

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.

Single Select

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.

Multi-Select

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.