Oracle eBS R12 customers can co-exist with Fusion Accounting Hub

Existing Oracle eBS customers who are on R12 can leverage the features of Fusion General Ledger and extensive reporting capabilities of Oracle Fusion without re-implementing or upgrading the entire sub-ledger system to Fusion ecosystem through a co-existence configuration setup using Fusion Accounting Hub (FAH).
Oracle Fusion Accounting Hub, comes embedded with Essbase multidimensional cube that can be leveraged to derive business benefits through BI analytics, Smartview reporting, Financial Studio reporting, Account Monitor and Account Inspector and a very intuitive Allocation Manager for creating Allocation rules.
Using GoldenGate, a seamless integration between Oracle eBS and FAH has been provided. GL actual balances data can be transferred to FAH and drill-down back to eBS system is also possible.
The SaaS model of FAH deployment would provide faster time to deployment and lower TCO for customers as well while the existing eBS system can be an on-premise installation.

Fusion Applications Security

The Fusion security architecture in Fusion is quite different from EBS and relates to real world scenarios better. Fusion security is externalized from Applications and moved to standardized Fusion Middleware, OPSS and LDAP.

Management of enterprise users and roles in fusion applications is done via Oracle Identity Manager (OIM). OIM manages this data in a database and keeps it in sync with the LDAP directory.

Management of enterprise users and roles in fusion applications is done via Oracle Identity Manager (OIM). OIM manages this data in a database and keeps it in sync with the LDAP directory. OAM is authentication, authorization, and auditing solution that provides centralized security administration. This includes functionality for access control, single sign-on (separate from Oracle Single Sign-On), personalization, and user profile management in heterogeneous application environments across a variety of application servers, legacy applications, and databases. OAM provides key features for creating, managing, and enforcing access policies. In Fusion v1, the LDAP server will hold both the Identity Store and the Policy Store. Identity store holds users and external roles. Policy store holds Application roles, Function and Data security policies.

Fusion ships with a full pre-seeded set of Job Roles. Separation of Jobs and Duty allows access control to be customized to a company’s particular organization

   • You can add/change jobs and their duties

   • You can add/change duties and their privileges

Below is a comparison of EBS security with Fusion Apps.

Job Role -> Top Level Menu

Data Role -> Responsibility

Duty Role -> Sub Menu

Privilege -> Form Function

Permission -> Executable

However, at times you may need to create a new set of policies, duties and job roles. I will try to demonstrate the steps necessary to setup this using an example in another article.