Discussions
Categories
- 17.9K All Categories
- 3.4K Industry Applications
- 3.4K Intelligent Advisor
- 75 Insurance
- 537.7K On-Premises Infrastructure
- 138.7K Analytics Software
- 38.6K Application Development Software
- 6.1K Cloud Platform
- 109.6K Database Software
- 17.6K Enterprise Manager
- 8.8K Hardware
- 71.3K Infrastructure Software
- 105.4K Integration
- 41.6K Security Software
How to reduce Essbase currency conversion process time

Hi All,
We are using Hyperion Essbase 11.1.2.3.508 version. Earlier, our Essbase currency conversion process used to take 40min to complete but these days it is taking approx.12 hrs to complete. Can you please let us know is there any way to improve the process? Below are the log screenshots for your reference.
Now:
20> },
21> (Descendants ([Consolidation Group], [Consolidation Group].Levels (0))
22> )))))))))))))))"
23> Amount "([GBP_RPT])"
24> Amountcontext "( [Periodic])"
25> Target "([GBP_REP_Curr])"
26> Range "{( [Periodic])}"
27> SPREAD;
OK/INFO - 1300006 - Essbase generated [83582] cells.
OK/INFO - 1013374 - The elapsed time of the allocation is [41327.2] seconds.
OK/INFO - 1241188 - ASO Allocation Completed on Database ['IFRS9REP'.'IFRS9REP'].
Earlier:
20> },
21> (Descendants ([Consolidation Group], [Consolidation Group].Levels (0))
22> )))))))))))))))"
23> Amount "([GBP_RPT])"
24> Amountcontext "( [Periodic])"
25> Target "([GBP_REP_Curr])"
26> Range "{( [Periodic])}"
27> SPREAD;
OK/INFO - 1300006 - Essbase generated [62104] cells.
OK/INFO - 1013374 - The elapsed time of the allocation is [2827.03] seconds.
OK/INFO - 1241188 - ASO Allocation Completed on Database ['IFRS9REP'.'IFRS9REP'].
Answers
-
The time it takes to process these calculations seems to increase exponentially when increasing the number of combinations in the POV. So I'm guessing that one or more of the member sets inside the POV has increased.
The first thing I'd try is splitting the statement up along some logical lines. For example, if you have a dimension in the POV where there are two members, create two nearly identical statements that contain just one of the members each. See what the performance is for that. You might be best off separating them on month -- so you'd have 12 nearly identical statements.
The good news is that Essbase 19c should be much faster for handling calculations like this.