The information in this chapter applies only to block storage databases and is not relevant to aggregate storage databases.

Also see:

If the outline includes a dimension tagged as accounts, you can use the @PTD function to calculate period-to-date values.

The example in this topic uses the Inventory branch of the Measures dimension from the Sample.Basic database, as shown:

Inventory (~) (Label Only) Opening Inventory (+) (TB First) (Expense Reporting) IF(NOT @ISMBR(Jan)) Additions (~) (Expense Reporting) Ending Inventory (~) (TB Last) (Expense Reporting)

To calculate period-to-date values for the year and for the current quarter, add two members to the Year dimension: QTD for quarter-to-date and YTD for year-to-date. For example:

Assuming that the current month is May, you would add this formula to the QTD member:

@PTD(Apr:May);

And you would add this formula on the YTD member:

@PTD(Jan:May);

Essbase sums the values for the range of months, as appropriate. Opening Inventory, however, has a time balance tag, First, and Ending Inventory has a time balance tag, Last. Essbase takes these values and treats them accordingly. See Calculating First, Last, and Average Values.

The following table provides an example of the calculation results for the members in the Inventory branch and for the Sales member:

The values for Sales and Additions have been summed.

Opening Inventory has a First tag. For QTD, Essbase takes the first value in the current quarter, which is Apr. For YTD, Essbase takes the first value in the year, which is Jan.

Ending Inventory has a Last tag. For QTD, Essbase takes the last value in the current quarter, which is May. For YTD, Essbase takes the last value in the year, which is also May.

Note:

You can also use Dynamic Time Series members to calculate period-to-date values. See Calculating Time Series Data.

You can use the @AVGRANGE function to calculate rolling averages and the @ACCUM function to calculate rolling year-to-date values.

For example, assume that a database contains monthly Sales data values and that the database outline includes the members AVG_Sales and YTD_Sales.

You would add this formula to the AVG_Sales member:

@AVGRANGE(SKIPNONE, Sales, @CURRMBRRANGE(Year, LEV, 0, , 0));

And you would add this formula on the YTD_Sales member:

@ACCUM(Sales);

Essbase calculates the average Sales values across the months in the dimension tagged as time. The SKIPNONE parameter means that all values are included, even #MISSING values. Essbase places the results in AVG_Sales. See Consolidating #MISSING Values.

The following table shows the results when Essbase calculates the cumulative Sales values and places the results in YTD_Sales:

The values for AVG_Sales are averages of the months-to-date. For example, AVG_Sales -> Mar is an average of Sales for Jan, Feb, and Mar.

The values for YTD_Sales are the cumulative values up to the current month. So YTD_Sales -> Feb is the sum of Sales -> Jan and Sales -> Feb.

You can use the @PRIOR function to calculate values based on a previous month’s value.

For example, assume that a database contains assets data values that are stored on a month-by-month basis. You can calculate the difference between the assets values of successive months (the asset movement) by subtracting the previous month’s value from the present month’s value.

Assume these three members manage the asset values for the database:

For Jan, the Asset_MVNT value is calculated by subtracting the Opening_Balance value from the Jan value.

You would add this formula on the Asset_MVNT member:

IF(@ISMBR(Jan)) Asset_MVNT = Assets - Opening_Balance; ELSE Asset_MVNT = Assets - @PRIOR(Assets); ENDIF;

This table shows the results when Essbase calculates the difference between the values of assets in successive months:

Essbase cycles through the months, performing these calculations:

The IF statement and @ISMBR function check whether the current member on the Year dimension is Jan. This check is necessary because the Asset_MVNT value for Jan cannot be calculated by subtracting the previous month’s value.

If the current member on the Year dimension is Jan, Essbase subtracts the Opening_Balance from the Jan -> Assets value and places the result in Jan -> Asset_MVNT.

If the current member on the Year dimension is not Jan, the @PRIOR function obtains the value for the previous month’s assets. Essbase subtracts the previous month’s assets from the current month’s assets. It places the result in the current month’s Asset_MVNT value.

You can test for #MISSING values in a database. See Consolidating #MISSING Values.

Assume that a database outline contains a member called Commission. Commission is paid at 10% of sales when the Sales value for the current member combination is not #MISSING. When applied to a Commission member in the database outline, the following formula calculates Commission:

IF(Sales <> #MISSING) Commission = Sales * .1; ELSE Commission = #MISSING; ENDIF;

If you place the formula in a calculation script, you must associate it with the Commission member as shown:

Commission(IF(Sales <> #MISSING) Commission = Sales * .1; ELSE Commission = #MISSING; ENDIF;);

Essbase cycles through the database, performing the following calculations:

You can perform specific calculations on attribute-dimension members in a database. See Calculating Attribute Data.

For example, to calculate profitability by ounce for products sized in ounces, you can use the @ATTRIBUTEVAL function in a calculation formula. In the Sample.Basic database, the Ratios branch of the Measures dimension contains a member called Profit per Ounce. The formula on this member:

Profit/@ATTRIBUTEVAL(@NAME(Ounces));

Essbase cycles through the Products dimension, performing the following calculations:

See Using Attributes in Calculation Formulas. For more information about the @ATTRIBUTEVAL function, see the Oracle Essbase Technical Reference.