Search This Blog

Sunday, July 31, 2016

RunTimeSubVars in FDMEE

FDMEE Essbase/Planning Calculation Script Execution

We have a client that loads the same entities from two separate FDMEE locations.  Typically, it is recommend that we prevent this from happening, but in this case the complete data set originated from two different sources.  During the data load process in FDMEE each location impacts the other location.  To prevent data issues from occurring we leveraged the Target Application Calculation Script setup with RunTimeSubVars.  


The Planning Architect setup a specific Clear CalcScript to limit the impact on the secondary location. This script runs before the data load and is application specific.  Data Rule and Location Script Scopes would not work in this instance because we wanted to limit the number of scripts created in the Planning/Essbase. The second script is the Calc/Aggregation of the cube, which obviously runs after the data load. 

Now the fun part...

The Planning/Essbase Architect setup the CLEARFDM calc script.  As part of the setup we defaulted the rtsvFactility RunTimeSubVar.

In the FDMEE setup we set the script value through the the Data Rule Option 1, which we will leverage to send over the Essbase Calc Script language necessary for SALMON and SUN data load. 

The Data Load Rule Integration Options are available on the Custom Options tab with the Data Load Rule for each Location.  Notice that we passed Essbase Calc Language leveraging the Integration Option 1 into the ClearFDM calc for both Salmon and Sun locations. 

Salmon Custom Options:

Sun Custom Options:

When we load the data to Planning/Essbase we can see the results of the above Integration Options in the log files.

Salmon Log:

Sun Log:

Each process passes the correct Essbase Calc Language to the rtsvFactility RunTimeSubVar preventing each location from impacting each other. 

Below are a few items to note: 
  • We leveraged this because the Target Entities overlapped in each locations data
  • If you have a long Essbase Script Filter that you need to pass, you will need to stack the Script Parameters
    • Each Integration Options within the Data Load Rule only allows 100 characters (Spaces count). Even if you stack and leverage all four Integration Options your max characters is 400



1 comment:

  1. Thanks for posting this. I found it really useful. As a relative noob to FDMEE, what are the advantages of writing custom scripts to clear data from the target application, over using the 'replace data' option when executing a rule to export data?

    ReplyDelete