Oracle EPB and OFA architecture comparison

Categories: Other
Financial Analyzer Enterprise Planning and Budgeting
Tiered Structure
The OFA Super Administrator can create Sub-Administrators with their own shared databases, which form a distributed hierarchy of multiple OFA shared databases. Structures are distributed down to Sub-Administrators and data is submitted back up. Sub-Administrators are free to create their own structures and create further Sub-Administrators.
Tiered Structure
There is no equivalent concept in EPB. Different Business Process Administrators can own different business processes and users’ access to dimensions can be scoped, but there is no concept of autonomous systems linked by a distributed hierarchy. All data and structures reside in a single Oracle Database.
Financial Data Items (FDIs)
OFA is data-centric: Administrators and end users need to know in which FDIs their data resides, together with the dimensionality of those FDIs.
Business Process Run Views (BPR Views)
EPB is business process-centric. Business Process Administrators create business processes that include the currency, data model, solve, tasks, and schedule of the business process. Based on the schedule, new runs of the business process are kicked off. Each run generally creates a new Business Process Run View, which is the logical view of the data.
The end users do not need to be aware of the physical model of the data storage. They access Views just as they access any other dimension.
Examples of business processes are: Actuals, Budget, Forecast.
Examples of BPR views are: Actuals, Budget 2006, Budget 2007, Forecast Q2 2005, Forecast Q3 2005.
Personal Databases
Each OFA user has a personal database. Administrators’ and Budget Workstations’ personal databases contain both data and documents. Analyst Workstations’ personal databases only contain documents. The data and structures are synchronized with the shared database through distribute, refresh, and submit options.
Personal Workspaces
Each EPB user has a personal workspace but all the workspaces reside in a single Oracle Database. In EPB the synchronization of the personal workspace with the shared workspace is handled automatically by the system. The personal workspace contains only data from those Views into which the user is entering worksheet data, and any personal dimension values the user has created.
Task Processor
This manages the updating of the OFA shared database. All changes to the shared database go through the Task Queue, managed by the Task Processor.
Concurrent Manager
All tasks created by EPB that are not actioned at runtime are managed by the E-Business Suite Concurrent Manager.
Windows and Java Clients
OFA has a Visual Basic client for Windows and a Java client for the web. The Windows client functionality is aimed at the power-user; the Java client functionality is aimed at a light data-entry clerk or analyst. Some features are only available in one of the clients.
HTML Client
EPB has an HTML client for the web with all the EPB functionality.
Disconnected Use
Administrators’ and Budget Workstations’ personal databases can be located on desktops and used when no connections are available to the shared database server as long as Oracle Personal Express is installed on the desktop.
Disconnected Use
There is no equivalent architecture for EPB. EPB’s thin client architecture requires that the user be always connected to the database.
« « Oracle Inventory (INV) key tables – mtl_category_sets_b, mtl_categories_b (3)                        Can you use Discoverer BIS views with Business Objects? » »

Comments are closed.