Essbase data loss and data shifting due to IMPLIED_SHARE setting

Per the Oracle technical reference for IMPLIED_SHARE the following steps must be performed any time the IMPLIED_SHARE setting is changed in essbase.cfg: Add IMPLIED_SHARE FALSE to essbase.cfg. Restart Essbase Server. Create a new application and database, with the IMPLIED_SHARE setting in place. Rebuild the outline, with the IMPLIED_SHARE setting in place. Reload the data. Run aggregation or calculation scripts. Restart the application. However, the technical reference does not say what would happen if the above … Read More

Pass Planning Calc Manager variable run time prompt values to an Essbase Partition

I had a requirement to pass planning calc manager variable run time prompt values to an Essbase Partition to refresh a partition for a specific scenario and version. We know we can run a MaxL file from a planning business rule using CDF. Can we extend this further and pass on run time prompt values to the MaxL file as well so they can be used in a partition definition? Say for example that we … Read More

Using Planning Calc Manager Variables in Essbase Calculation script with SET RUNTIMESUBVARS command

On a recent project, I wanted to execute an Essbase Calc script with substitution variables set to accept values passed by Planning business rule run time prompts. In this specific case, I wanted a user to run a business rule in a planning application that would use the run time prompt values and pass on to a calculation script in a separate standalone Essbase database. I used a combination of CDF in business rule that … Read More

Maximum number of rows exceeded errror in Smartview

When using Smartview on Essbase, you may get a maximum number of rows exceeded error specifying a number for the rows exceeded. This number is the one specified in the Oracle Provider Services maximum number of rows setting. The default setting is 5000 rows. When the Smartview query result exceeds 5000 rows (or the number specified in the Provider Services settings) , you get an error which looks like: Essbase Error (1020011): Maximum number of … Read More

Essbase Substitution Variables in Essbase SQL Load Rules

Do you know that you can use Essbase Substitution Variables in Essbase SQL Load rules? For example, you can use the substitution variables in the where clause of a SQL query to fetch only a specific year or month corresponding to the value of the variables. This is a very good feature if you want your SQL data loads to be controlled using the Essbase Substitution variables. Read further to see how this can be … Read More


@MOVSUM and @MOVSUMX functions are handy functions that can used to calculate trailing or forward sums across dimensions. You can benefit from using these functions for calculating rolling sums. Details about @MOVSUMX function from the Oracle tech ref can be found here. Although the tech ref gives a lot of details, I thought it was worth sharing a practical use of this function and something worth noting regarding the time period range used in the … Read More

Essbase ASO dimension build limit & Outline Compaction

There is a maximum number of times you can add and delete dimensions in an ASO cube. Each dimension added is tagged with a dimension ID that increments and reaches the ASO dimension build limit. Once you reach this limit, you get errors. For e.g. ESSBASE ASO Error:  “1060190 Cannot Add Dimension – too many dimensions have been created and deleted”. EPMA-ASO Error: Error. Failed to deploy Essbase cube. Caused by: Cannot end stream build. … Read More