Uploaded by Pramodh Lakkur

HyperionAppsQuestionnaire

advertisement
Global Architecture & Design Team for
EPM Competency
Oracle EPM
Hyperion Apps
Capacity Planning Questionnaire
On-Premise & IaaS Cloud
This is Questionnaire should be used for capacity planning of Oracle Enterprise Performance Management products,
e.g. Hyperion, Essbase. Please contact the Oracle Solution Center at osc_epm _ww_grp@oracle.com for any
assistance during this process. After completion, the Questionnaire should be uploaded to OSC Services Request
System tool at "http://osc.oraclecorp.com". The configuration recommendation will be sent to the Oracle sales team
within one week. This form should be used for capacity planning of EPM products. Please, use the given input fields
to provide the needed capacity planning information as offered by the OSC architect team. Any other data format
cannot be accepted as this would not be inline with our developed algorithms. Thanks for understanding.
Oracle EPM questionnaire supports/includes the following application components:
An online analytical processing (OLAP) server that provides an environment for deploying prepackaged applications or developing custom
applications. Used in almost all Hyperion related usage scenarios.
1.
Oracle Hyperion Planning
A centralized, Excel and web-based planning, budgeting, and forecasting solution that integrates financial and operational planning
processes and improves business predictability. It is based on Oracle Essbase.
Crystal Ball (replaced by Predictive Planning)
Simplified User Interface (SUI)
Workforce Planning
Capital Expense Planning
Project Financial Planning
Offline Planning
2.
- Discontinued Part in 11.2
- Discontinued Part in 11.2
- Discontinued Part in 11.2
- Discontinued Part in 11.2
- Discontinued Part in 11.2
- Discontinued Part in 11.2
Oracle Hyperion Financial Management
A multidimensional online analytical processing server on RDBMS that provides an environment for web-based consolidation, tax
provision, QMR, JSK applications. The application enables global financial consolidation, reporting, and analysis in a single, highly
scalable software solution.
3.
Oracle Hyperion Financial Close Management
Oracle Hyperion Financial Close Management centralizes management of all period-end close activities, replacing traditional,
manually maintained checklists with dynamic dashboards that give users the ability to immediately view and act on information.
Supported close-cycle processes include ledger and sub-ledger close, data loading and mapping, financial consolidation, 10K/10Q
creation, reconciliations, tax/treasury–in fact, any task associated with the extended financial close.
4.
Oracle Hyperion Financial Data Quality Management
Oracle Hyperion Financial Data Quality Management, is a packaged solution for finance users that help develop standardized
financial data management processes with its Web-based guided workflow user interface. Its data preparation server can ease
integrating and validating financial data from any of your source systems. And to further reduce your data integration costs as well as
data mapping complexities, Hyperion Financial Data Quality Management includes optional prepackaged EPM Adapters for Hyperion
Financial Management, Hyperion Planning and Oracle Essbase.
5.
Oracle Hyperion Profitability and Cost Management
An application that provides actionable insights, by discovering drivers of cost and profitability, empowering users with visibility and
flexibility, and improving resource alignment.
6.
Oracle Hyperion Strategic Finance
Oracle Hyperion Strategic Finance is a feature rich financial forecasting and modeling solution with on-the-fly scenario analysis and
modeling capabilities. It helps users quickly model and evaluate financial scenarios, and offers out of the box treasury capabilities for
sophisticated debt and capital structure management. When used in conjunction with other Oracle Hyperion enterprise performance
management (EPM) applications and Oracle Essbase, it provides a compelling solution which can be used to set targets, perform
quick financial impact analysis, and present focused financial information for informed decision making.
7.
Hyperion Disclosure Management - Discontinued in 11.2
8.
Oracle Hyperion Tax Provision
A comprehensive global tax provision solution for multinational companies reporting under US GAAP or IFRS. The application
encompasses all the stages of the corporate tax provision process, including tax automation, data collection, tax provision calculation,
return-to-accrual automation, and tax reporting and analysis. The application is built using Oracle Hyperion Financial Management,
and it leverages all the functionality provided by Financial Management.
9.
Oracle Data Relationship Management (Windows only)
Oracle Data Relationship Management (DRM) is an enterprise change management solution for building and retaining consistency
within master data assets despite endless changes necessary to support underlying transactional and analytical systems.
https://www.oracle.com/middleware/technologies/epm-data-relationship-mgmt-downloads.html
Oracle Solution Center
Confidential - Oracle Restricted
2
Revised: August 2023
Attention:
The following generic Hyperion services are also no longer support (discontinued) starting with version 11.2 of Oracle Hyperion:
EPM Architect (EPMA) and EPM Mobile
Supported Platforms
See the Oracle Fusion Middleware 12c Certifications on the Oracle Fusion Middleware Supported System Configurations page on the Oracle
Technical Network at:
http://www.oracle.com/technetwork/middleware/ias/downloads/fusion-certification-100350.html.
Additional information about the Oracle EPM stack:
https://docs.oracle.com/en/applications/enterprise-performance-management/index.html
https://docs.oracle.com/en/applications/enterprise-performance-management/11.2/index.html
Oracle Solution Center
Confidential - Oracle Restricted
3
Revised: August 2023
Customer Information:
Customer Name:
City:
State:
Zip/Postal Code:
Country:
Central Bank of U.A.E
Dubai
United Arab Emirates
Customer Contact
Name:
Phone:
Email:
Desired Configuration:
Please give a high-level overview of the implementation: What are the business objectives and critical factors in the
decision to use Oracle EPM? Please provide details on customer-specific requirements be they unusual business
processes or other concerns. A short description of the customer's business (what markets they address etc.)
Dear Oracle Team,
Customer is planning to implement EPM 11.2.10 version for below mentioned components.
EPM Version: EPM 11.2.10 (Hyperion Planning Plus)
Applications:
1) Hyperion Planning
2) Hyperion Essbase
3) DRM (Data Relationship Management)
4) FDMEE (Financial Data Quality Management, Enterprise Edition)
5) Oracle ExaCC database
Additional Requirements:
1) High Availability for QA, Production and DR.
2) DR Setup (Seamless connectivity between Production and DR site)
Existing Customer Landscapes:
If this is a brownfield project with existing workloads on an Oracle or 3rd system landscape you have to ask for our
OSC data collection questionnaire for existing application & database landscapes.
Brownfield in this sense means, that the customer has already a running Oracle EPM environment in place and that
the related workload characteristics need to be used as basis for a mapping onto a new infrastructure setup.
Attention:
Customers EPM deployments are mainly Windows OS based related to the fact that the Essbase Core Services
and the DRM service are Windows only.
Oracle Solution Center
Confidential - Oracle Restricted
4
Revised: August 2023
1.Preferred server platform
Select AppS and DB separately:
Oracle Server X-series [ Provide Server Type: eg Server X8-2 ]
Exadata X8M-2 [ ]
Oracle Database Appliance X8 [ ]
Exadata X8M-8 [ ]
ExaC@C Gen 2 [Yes]
OnPrem
x86
Autonomous DB:
Oracle Private Cloud Appliance [ ] ADW [ ] ATP [ ]
CC@C Gen2 [ ]
Not yet available for most of the
Oracle AppS.
Need to be checked with the PM team
by the responsible Oracle account
team first.
Cloud
(OCI)
IaaS [ ]
Shape type to be used for AppS:
VM Intel [ ] VM AMD [ ] VM
Flex [ ]
Bare Metal [ ]
Shape type to be used for DB:
VM Intel [ ] VM AMD [ ] VM
Flex [ ] Bare Metal [ ]
PaaS:
DBaaS
Autonomous DB:
ADW [ ] ATP [ ]
ExaCS [ ]
MS Azure [ ]
Not yet available for most of the Oracle AppS. Need to
be checked with the PM team by the responsible Oracle
account team first.
Autonomous FAQ:
https://www.oracle.com/database/technologies/datawarehouse-bigdata/adb-faqs.html
Oracle Solution Center
Confidential - Oracle Restricted
5
Revised: August 2023
2.If you would like us to recommend additional capacity for future growth please indicate the estimated growth:
1.What will be the expected growth rate for the specified time frame.
(e.g., 15% increase in the next three years.) __________
Will be calculated on the basis if the initial given user or transaction related workload characteristics.
3.Preferred storage platform
Access Type
SAN [ ]
NAS [ ]
Storage Subsystem
Oracle ZFS Storage [Provide Storage Type eg : ZS7-2]
Data Protection
RAID-1 [ ]
RAID-10 [ ]
Internal Storage [ YES ] Other [ ]
RAID-5 [ ]
Oracle ASM
[ ]
4.High Availability (Yes [ Yes ] / No [ ])
Oracle Solution Center
Confidential - Oracle Restricted
6
Revised: August 2023
1. Hyperion Planning
Hyperion Essbase Planning includes the following logical application and database instances:
- Web Tier (Oracle HTTP Server)
- Foundation Service Tier
- Essbase Core Service Tier – Windows only (see appendix)
- Essbase Support Service Tier
- Essbase Reporting Service Tier
- DB Tier
User based sizing approach of the Hyperion Essbase Planning system:
Sizing element:
Users
Number of concurrent active users
10
Number of logged/in-active users*
50
* Attention: concurrent and logged/in-active users should clearly be separated in the input fields
Sizing element:
Essbase Cubes
Number of cubes to be used
3 BSO + 1 ASO
Size of a single cube
5 GB each
* Attention: The cube related input field is not mandatory and should only be used if qualified cube data is available.
2. Hyperion Financial Management:
HFM includes the following logical application and database instances:
- Web Tier (Oracle HTTP Server)
- Foundation Service Tier
- Financial Management Core Service Tier
- Financial Management Support Service Tier
- Financial Management Reporting Service Tier
- DB Tier
User based sizing approach of the Hyperion Financial Management system:
Sizing element:
Users
Number of concurrent active users
Number of logged/in-active users*
* Attention: concurrent and logged/in-active users should clearly be separated in the input fields
Oracle Solution Center
Confidential - Oracle Restricted
7
Revised: August 2023
3. Hyperion Financial Close Management
HFCM includes the following logical application and database instances:
- Web Tier (Oracle HTTP Server)
- Foundation (incl.Core components) Service Tier
- Financial Close Management SOA Service Tier
- DB Tier
User based sizing approach of the Hyperion Financial Close Management system:
Sizing element:
Users
Number of concurrent active users
Number of logged/in-active users*
* Attention: concurrent and logged/in-active users should clearly be separated in the input fields
4. Hyperion Profitability and Cost Management
HPCM includes the following logical application and database instances:
- Web Tier (Oracle HTTP Server)
- Foundation Service Tier
- Profitability and Cost Management Core Service Tier
- Profitability and Cost Management Support Service Tier
- DB Tier
- Essbase Service Tier - Windows only (see appendix)
User based sizing approach of the Profitability and Cost Management system:
Sizing element:
Users
Number of concurrent active users
Number of logged/in-active users*
* Attention: concurrent and logged/in-active users should clearly be separated in the input fields
Sizing element:
Essbase Cubes
Number of cubes to be used
Size of a single cube
1.5 GB (default value per cube)
* Attention: The cube related input field is not mandatory and should only be used if qualified cube data is available.
Oracle Solution Center
Confidential - Oracle Restricted
8
Revised: August 2023
5. Financial Data Quality Management (Budgetary)
HFDMEE includes the following logical application and database instances:
- Web Tier (Oracle HTTP Server)
- Foundation Service Tier
- Financial Management Enterprise Edition Core Service Tier
- DB Tier
User based sizing approach of the Hyperion FDMEE system:
Sizing element:
Users
Number of concurrent active users
5
Number of logged/in-active users*
10
* Attention: concurrent and logged/in-active users should clearly be separated in the input fields
Oracle Solution Center
Confidential - Oracle Restricted
9
Revised: August 2023
6. Hyperion Financial Management Enterprise Edition (Advanced/detailed)
HFDMEE includes the following logical application and database instances:
- Web Tier (Oracle HTTP Server)
- Foundation Service Tier
- Financial Management Enterprise Edition Core Service Tier
- DB Tier
Attention:
Please, read the related information in the appendix before using the advanced capacity planning approach. It
includes a detailed description for each input field/variable.
Sizing element: Batch Import Adaptor / pre-defined
Select only one out of the three options:
FDMEE Batch-Import – Adapter based /
Low = up to 500.000 rows
e.g. X
FDMEE Batch-Import – Adapter based /
Medium = up to 1.000.000 rows
FDMEE Batch-Import – Adapter based /
High = up to 2.500.000 rows
Nr of rows to be
imported from source
systems
Sizing element: Batch Import Adaptor / individual
Batch
time window
in Minutes
FDMEE Batch-Import – Adapter based
Default: 60 min
Sizing element: Single User - File Import / pre-defined
Concurrent active users only
FDMEE Single User – File Import / Low
/ reflects 1 day of financial data ~ 6000 rows of data
Default
FDMEE Single User – File Import / Medium
/ reflects 10 days of financial data ~ 60.000 rows of data
FDMEE Single User – File Import / High
/ reflects 1 month of financial data ~ 120.000 rows of data
Sizing element: Reporting / Online & Offline
Nr of reports to be generated in parallel
FDMEE Online Reporting – Low
= up to 10 pages per report
FDMEE Online Reporting – Medium
= up to 100 pages per report
FDMEE Online Reporting – High
= up to 1000 pages per report
FDMEE Offline Reporting – Low
= up to 10 pages per report
FDMEE Offline Reporting – Medium
= up to 100 pages per report
FDMEE Offline Reporting – High
= up to 1000 pages per report
Oracle Solution Center
Confidential - Oracle Restricted
10
Revised: August 2023
7. Oracle Hyperion Tax Provision
HTM includes the following logical application and database instances:
- Web Tier (Oracle HTTP Server)
- Foundation Service Tier
- Tax Management Core Service Tier
- Tax Management SOA Service Tier
- DB Tier
User based sizing approach of the Hyperion Tax Management system:
Sizing element:
Users
Number of concurrent active users
Number of logged/in-active users*
* Attention: concurrent and logged/in-active users should clearly be separated in the input fields
Oracle Solution Center
Confidential - Oracle Restricted
11
Revised: August 2023
8. Oracle Data Relationship Management (Windows or Linux only)
HTM includes the following logical application and database instances:
- Web Tier (Oracle HTTP Server EPM 11.2 only)
- Foundation Service Tier (local or on a dedicated Weblogic instance)
- DRM Core Service Tier (WL Managed Server)
- DB Tier
User based sizing approach of the DRM system:
Sizing element:
Users
Number of concurrent active users
5
Number of logged/in-active users*
10
* Attention: concurrent and logged/in-active users should clearly be separated in the input fields
Oracle Data Relationship Management functions as a hub where reporting structures are maintained, analyzed, and validated before moving
throughout the enterprise.
Data Relationship Management does the following:

Manages business entities, hierarchies, attributes, and mappings across multiple systems

Validates data relationships and calculates attribute values using business rules

Enforces referential integrity across all subscribing systems and hierarchies

Enables users to create and manage alternate views

Merges independent data sets from different sources and combines them into a master set

Maintains historical versions for comparative reporting and analysis

Tracks all hierarchy and attribute changes with a full-featured audit log

Can serve as the main point-of-entry to update subscribing systems or be used after the fact for reconciliation and analysis
DRM Certifications EPM 11.2+:
SQL Server 2012, 2014, 2019 (all SP levels included), Windows Server 2012 R2 (all SP levels included),
Windows Server 2019 (all SP levels included), FMW support for Windows Server 2012 (all SP levels included),
Windows Server 2019 (all SP levels included)
Oracle Solution Center
Confidential - Oracle Restricted
12
Revised: August 2023
9. In addition to Production, identify all other environments:
Number of
Environment
Development
Yes/No
Users
Instances
Tiers: two/three
Yes
5
5
three
Yes
50
10
three
Yes - DR
50
10
three
Test
Quality Assurance
Other
Two tier = AppS and DB on, e.g. the same physical server or VM shape
Three tier = AppS and DB on separated physical servers or VM shapes
10. Which deployment strategy should be used for the Non-PRD environment (e.g. DEV, TST, QAS)?
Physically separated on dedicated OnPrem Oracle Servers
[Y]
Separation through dedicated OCI Shapes
[ ]
Consolidation of all Non-PRD instances on a single Oracle Server
[ ]
Consolidation of all Non-PRD instances on a single OCI Shape
[ ]
Consolidation of all Non-PRD DB instances in a single Oracle Multi-Tenant DB instance
[ ]
Reference Oracle Multi-Tenant DB:
https://docs.oracle.com/database/121/CNCPT/cdbovrvw.htm#CNCPT89235
Oracle Solution Center
Confidential - Oracle Restricted
13
Revised: August 2023
Cloud Deployment:
Public Cloud
1. Oracle Cloud Infrastructure – Classic:
Compute Service [ ] Storage Service [ ] Container Service [ ]
2. Oracle Cloud Infrastructure:
Virtual Machine Instance [ ] Bare Metal Instance [ ]
Block Storage Service [ ] Object Storage Service [ ]
3. Oracle Cloud Infrastructure – Database Service on Bare Metal:
Dense I/O [ ]
4. Oracle Cloud Platform – Oracle Database Cloud Service:
Pay As You Go (PAYG) – Virtual Image [ ] Monthly Flex – Virtual Image [ ]
Standard Edition [ ] Enterprise Edition [ ] High Performance [ ] Extreme Performance [ ]
5. Oracle Cloud Platform – Oracle Database Exadata Cloud Service:
Pay As You Go (PAYG) [ ] Monthly Flex [ ]
6. Oracle Cloud Platform – Database Backup Cloud Service:
Cloud Storage [ ] Local + Cloud Storage [ ] Standby Database [ ]
7. Oracle Cloud Platform – Java Cloud Service:
Pay As You Go (PAYG) [ ] Monthly Flex [ ]
Standard Edition [ ] Enterprise Edition [ ] Suite Edition [ ]
Hybrid Cloud
Cloud@Customer:
Oracle Compute Cloud at Customer [ ] Exadata Database Cloud at Customer [ ]
Private Cloud
Engineered System for in-house Deployment:
Oracle Private Cloud Appliance [ ]
Are any application services sensitive to network or storage throughput requirements that must be met?
Oracle Solution Center
Confidential - Oracle Restricted
14
Revised: August 2023
Appendix
Typical Oracle EPM Deployment Architecture, e.g. OCI IaaS:
AD with Fault Domains
AD HA Deployment
Oracle Solution Center
Confidential - Oracle Restricted
15
Revised: August 2023
Difference between logged and active concurrent users
The overall number of users which are logged into a system like, e.g. EPM are called active logged users. These users do all consume memory
for their user context, out of this group only the users which are working with the system in parallel – the so called active concurrent users – will
consume CPU cycles. In this questionnaire the concurrent active user group is not part of the logged-in user group and vica versa.
Think time
Think time is the time that a real user waits between actions. Example: When a user receives data from a server, the user may wait several
seconds/minutes to review the data before responding / before starting his/her next interaction step with the system. Think time depends strongly
on the complexity of the data which need to be reviewed by the end user before moving on with the next processing step. Especially in the BI/EPM
space it can be expected that the think time is much higher than in comparison to a typical ERP application.
Budgetary vs. Detailed/Advanced Capacity Planning approach
The so called “Budgetary” approach should be used in the early stages of a project; when there are not yet that many hard facts and details about
the various transactions and the related user types available. It should just allow the customer to get an initial idea about the hardware resources
needed for a certain application deployment. The hardware results based on the budgetary CP method will include a higher headroom than the
ones for the Advanced CP approach. The Advanced method should then be used during a later stage of the project when there are more specific
details available about the application related usage scenarios and user types/behavior. This will allow us to provide a much more accurate
architecture&design output as in comparison to the initial phase. Therefore the hardware requirements calculated in phase II should normally be
lower than in phase I.
Essbase Core (Advanced/detailed CP approach)
The Essbase DB advanced capacity planning approach should only be used in cases where there is enough reliable input data available for the
various usage scenarios. When using the advanced approach you should keep in mind that Essbase is mainly be used in BI environments and
therefore the amount of parallel active user requests/sessions should not be that high in numbers. Especially when you work with estimates it
is recommend to follow the given concurrent active user limits in the following description:
Essbase ASO MDX user queries
The ASO or Aggregation Store Option/database is routinely loaded with detail-level data from a data warehouse, aggregated, and then made
available for query. Calculations are subsequently performed dynamically, at query execution time, by the calculation engine in MDX (the data
manipulation language for Oracle Essbase) generated by an application such as Oracle Business Intelligence Enterprise Edition. That means this
kind of user requests/session include the on-the-fly generation process for the aggregates/cubes to be used in a BI analysis. ASO is, for the
purposes of returning aggregated results, an in-memory database. Therefore this processing/request type is highly performance/hardware hungry.
The basis for the defined capacity planning method are so called complex aggregates which reflect the most common real-word usage scenarios
of Essbase.
Essbase ASO MDX user queries
– based on heavy pre-def MDX scripts / High User = 10 sec Think time
Typical OSC recommended concurrent active user load = 1-10 max
Essbase ASO MDX user queries
– based on heavy pre-def MDX scripts / Medium User = 30 sec Think time
Typical OSC recommended concurrent active user load = 1-10 max
Essbase ASO MDX user queries – based on heavy pre-def MDX scripts / Low User = 60 sec Think time (Default user type)
Typical OSC recommended concurrent active user load = 1-10 max
Essbase ASO MDX user queries – based on medium/small pre-def MDX scripts / High User = 10 sec Think time
Typical OSC recommended concurrent active user load = 1-20 max
Essbase ASO MDX user queries – based on medium/small pre-def MDX scripts / Medium User = 30 sec Think time
Typical OSC recommended concurrent active user load = 1-20 max
Essbase ASO MDX user queries – based on medium/small pre-def MDX scripts / Low User = 60 sec Think time (Default user type)
Typical OSC recommended concurrent active user load = 1-20 max
Oracle Solution Center
Confidential - Oracle Restricted
16
Revised: August 2023
Smart View provides a common Microsoft (MS) Office interface for Oracle Essbase, Oracle Hyperion Financial Management, Fusion Edition,
Oracle Hyperion Planning, Fusion Edition, Oracle Enterprise Performance Management Workspace, Fusion Edition, Oracle Business Intelligence
Suite Enterprise Edition, and Oracle's Hyperion Enterprise data. Using Smart View, you can view, import, manipulate, distribute, and share data
in MS Excel, MS Word, and MS PowerPoint.
Essbase ASO Smart-View user queries – MS-Excel ad-hoc reporting / High User = 10 sec Think time
Essbase ASO Smart-View user queries – MS-Excel ad-hoc reporting / Medium User = 30 sec Think time
Essbase ASO Smart-View user queries – MS-Excel ad-hoc reporting / Low User = 60 sec Think time
Essbase BSO user queries
BSO (Block Store/Storage Option) cubes typically contain fewer (and smaller) dimensions than aggregate storage (ASO) cubes and can perform
numerous and complex calculations on the smaller outlines. ASO cubes are designed to provide rapid aggregation capabilities for much larger
Essbase outlines, typically supporting many more (and larger) dimensions. ASO cannot support write-back but BSO can support that feature
(Write-Back = Input data directly back to Essbase Cube). For architecture of calculation, ASO use MDX script, BSO use Calc Script. BSO
applications are great for the manipulation and transformation of data, such as calculating healthcare costs for next year based on a rate, or
transforming data based on a series of exchange rates. Therefore BSO will also be used for Hyperion Planning, because of it’s future
oriented view. Data in BSO applications is manipulated using calculation scripts and business rules, which provide the math that Essbase needs
to perform.
Essbase BSO user queries – based on pre-calculated aggregates / High User = 10 sec Think time
Essbase BSO user queries – based on pre-calculated aggregates / Medium User = 30 sec Think time
Essbase BSO user queries – based on pre-calculated aggregates / Low User = 60 sec Think time
Essbase BSO Smart-View user queries – MS-Excel ad-hoc reporting / High User = 10 sec Think time
Essbase BSO Smart-View user queries – MS-Excel ad-hoc reporting / Medium User = 30 sec Think time
Essbase BSO Smart-View user queries – MS-Excel ad-hoc reporting / Low User = 60 sec Think time
Hyperion Planning is Oracle’s centralized financial and operational planning application. Part of the Oracle Enterprise Performance Management
(EPM) suite, Planning is primarily aimed at finance departments for enterprise budgeting and comprises a web application layer around a relational
metadata store and the OLAP data store and calculation engine Essbase.
Essbase BSO Planning user queries – Hyperion Planning only / High User = 10 sec Think time
Essbase BSO Planning user queries – Hyperion Planning only / Medium User = 30 sec Think time
Essbase BSO Planning user queries – Hyperion Planning only / Low User = 60 sec Think time
Essbase BSO+ASO user queries / Hybrid Essbase
BSO simply cannot aggregate the data quickly enough in typical Planning applications. The obvious solution would be a melding of BSO and ASO
to afford size, speed, and flexibility. That is exactly what Oracle have done with Hybrid Essbase. Hybrid’s storage engine uses BSO to store the
base data and on retrieval converts this data into the bitmap format needed for ASO’s fast aggregation engine. The result is a marriage of BSO
functionality and flexibility with ASOs’ performance – the best of both worlds of Essbase.
Essbase BSO+ASO user queries – Complex BSO+ASO combo calcs / High User = 10 sec Think time
Essbase BSO+ASO user queries – Complex BSO+ASO combo calcs / Medium User = 30 sec Think time
Essbase BSO+ASO user queries – Complex BSO+ASO combo calcs / Low User = 60 sec Think time
Oracle Solution Center
Confidential - Oracle Restricted
17
Revised: August 2023
Essbase components:
Hyperion Planning components:
Oracle Solution Center
Confidential - Oracle Restricted
18
Revised: August 2023
Hyperion Financial Management components:
Hyperion Profitability and Cost Management components:
Oracle Solution Center
Confidential - Oracle Restricted
19
Revised: August 2023
Oracle Hyperion Tax Provision components:
Oracle Hyperion Financial Data Quality Management FDMEE Components:
Oracle Solution Center
Confidential - Oracle Restricted
20
Revised: August 2023
Financial Close Management Components:
Oracle Solution Center
Confidential - Oracle Restricted
21
Revised: August 2023
Download