Keeping up with EPM Cloud

When working with Hyperion systems, Smart View is a key tool used for reporting, as well as inputting data. It provides a valuable link between Hyperion and Excel, which allows users to retrieve data from the database straight into Excel with ease. Smart View functions are available through the Smart View toolbar and can be used with Essbase, HFM, Planning or Cloud connections. Occasionally, it is necessary to perform Smart View functions behind the scenes using VBA code, rather than manually using the Smart View toolbar. For example, a spreadsheet which will refresh all the Essbase retrieval sheets on opening, so that users can view the most up to date data, without having to remember to refresh each of the retrieval sheets themselves. This blog will be cover how to retrieve data using a Smart View refresh function in VBA. For more information about Smart View Excel VBA functions, go to the Oracle Hyperion Smart View Developers Guide .  System Requirements ...

Import expressions can be added to an FDMEE import format to alter the data being imported from a file in several valuable ways. In this blog, I will focus on using the ‘Factor’ import expression, which allows you to multiply your data by any whole number or decimal factor. This means that you can scale the file data effortlessly by any numeric factor.  The syntax for this expression is Factor=Value, where the value is the user-defined whole or decimal number you wish to multiply your data by. The import expression should be entered in the 'Expression' field for the 'Amount' source column.  Listed below are a few things to consider when applying a factor to your data: Factors are only applied when the import format Data Type is set to one of the following   Delimited–Numeric data   Fixed–Numeric data   Multi-Column–Numeric Data   The factor will be applied to all data amounts in the file.   When importing a multi-column file with Accou...

Custom calculation scripts contain sections of code which can then be referenced several times within a Business Rule, or in multiple different Business Rules. They are created within Calculation Manager, in much the same way as Business Rules, and are listed below the relevant PBCS Plan Type, under the ‘Scripts’ heading, as below: Custom scripts are useful for times when a certain section of code is repeated throughout a Business Rule, or is contained in multiple Business Rules. Using scripts in this situation means that if the script needs to be altered, it only needs to be updated in one place, rather than having to be updated in multiple locations or Business Rules. This saves time and ensures all your Business Rules which contain this section of code are consistent. The syntax used to reference a script from within a Business Rule is: %Script(name:=" ScriptName ",application:=" AppName ",plantype:=" PlanType ") Where:   ScriptName...

For those of you familiar with Essbase, when creating an Essbase application there are two types available; BSO (Block storage) and ASO (Aggregate storage). Typically, BSO applications are used when the requirements involve complicated calculations, whereas ASO applications are used if the model contains large dimensions and does not require any complex calculations. One of the main problems with ASO databases in the past was finding a way to perform calculations such as a standard data copy from one member to another – a task that is extremely simple in a BSO application. You see, unlike in BSO applications, ASO applications don't give you the ability to write and execute calculation scripts. However, there is a way round this which uses MaxL along with an external calculation script and a little bit of MDX. Below illustrates a copy from scenario Actual to Forecast for months April to August. The MaxL Script is as follows: execute calculation on database MyApp.MyDB wit...