Browser version script Skip Headers

Oracle® Fusion Accounting Hub Implementation Guide
11g Release 1 (11.1.3)
Part Number E20374-03
Go to contents  page
Contents
Go to Previous  page
Previous
Go to previous page
Next

1 Fusion Accounting Hub Overview

This chapter contains the following:

Oracle Fusion Accounting Hub Features: Overview

Oracle Fusion Accounting Hub: How It Works

Accounting Configuration: Overview

Implementation Options for Oracle Fusion Accounting Hub: Overview

Manage Application Implementation

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

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:

There are several documentation resources 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.