Keeping up with EPM Cloud

Recently I have been attempting to map null entries to be ignored when importing data into FDMEE. This may sound like an easy thing to do, but if you have experimented much with FDMEE mappings, you’ll know that this isn’t as simple as just creating a mapping from ‘Null’ to ‘Ignore’. However, there is a way around this using a custom SQL mapping script to define your own mappings a nd this blog is here to show you how! Firstly, to access the ability to input a custom SQL mapping script, go to the ‘Between’, ‘In’ or ‘Like’ mappings tab (SQL mapping scripts are not available for Explicit or Multi-dimension mapping types).  Add a new mapping and enter the Source Value and Rule Name . Then for the Target Value , enter either:    #SQL to enable the SQL mapping script functionality    #SCRIPT to enable the Jython mapping script functionality   In the example below I have used a Like mapping on the Products dimension ( d ata t able c olu m n UD2) and set the Source Value t

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

About EPM Automate EPM Automate is a utility which enables service administrators to remotely perform a selection of routine tasks on their PBCS system. The EPM Automate commands are referenced in batch scripts, meaning repeatable tasks can be automated easily. This is particularly useful when the automated task cannot be set up as a scheduled job from within the PBCS interface. The following tasks can be performed remotely using EPM Automate commands: Import and export metadata and data Refresh the application Run business rules on data Copy data from one database to another Upload files into service instances, list files, and delete files from the service Run a Data Management batch rule Export and import application and artefact snapshots Import and export Data Management mappings Generate Data Management reports Installing EPM Automate Before you can use EPM Automate, it must be downloaded and installed to your local computer or server. To install t