Designing forms in EPM can be easy or challenging depending on the requirements. In general, forms should be easy to maintain by including substitution or user variables to allow usage across multiple scenarios, years, versions, and other dimensions. They also need to perform efficiently by limiting the number of rows and columns by using suppression … Continue reading Add Row to Form
Here's an easy way to use Groovy to retrieve variables when running business rules.
Here's a way for non-administrators to execute data maps, it's pretty Groovy.
Rules or Rules? The Answer is Artifact Labels
This script will replace all the zeros in the scenario Actual with #Missing, thus reducing the size of the database. After running script, must do a dense restructure. SET UpdateCalc Off; Actual = Actual / (Actual != 0);
Aggregation script to be used on forms, aggs the scenario selected on the form. SET AGGMISSG ON; SET CACHE HIGH; SET UPDATECALC OFF; SET LOCKBLOCK HIGH; SET EMPTYMEMBERSETS ON; /*Forecast Agg*/ Fix (@Remove({Scenario}, "OEP_Plan")) Fix ({Scenario} AND "OEP_Forecast")) /* cleaner way to use the Fix */ Fix ("OEP_Working", &OEP_FcstStartYr:&OEP_FcstEndYr) Agg ("DataSource", "Detail", "Entity", "Function", "Intercompany"); … Continue reading Agg w/ EMPTYMEMBERSETS
Random EPM Notes 