Here’s the Prophix Product Adoption Tip for November of 2020.
Check it out and let us know what you think!
To Model Manager Formula, or Not to Model Manager Formula?
A very common inquiry that pops up is when to leverage a calculated account or version in Model Manager vs. a template calculation.
To help you decide which one may be a better alternative, here is the main question you should ask before adding your next calculated account or version.
Is this calculated member going to be used across multiple data views and templates?
If yes, then it would make sense to add the member as part of the model manager structure. This will allow you to reference the member across data views and templates.
If no, then we would recommend creating the needed calculation logic as a template formula instead.
Why would a template formula be preferable to a calculated account in Model Manager?
If a calculated value is only needed in one or few reports (for example Balance Sheet ratios, or account values as percent of revenue) it may be better to leverage template-based calculations so the values are only generated where and when they are needed.
Setting up the calculation in the account dimension requires MDX. Increasing use of MDX can make model maintenance difficult and can lead to performance degradation.
Specifically, for versions, increasing the number of versions can negatively impact model performance so you want to minimize the number of versions in your model. Leveraging template calculations in place of versions to calculate variances is preferred.
We already classified our model manager formulas based on this logic. For example credit rate is a formula which for us is universal across all templates so we define it as a formula within the model manager.
I was using procedural calculations in Model Manager and had to change everything to template calculations because the procedural calculations did not work correctly for my standard users with limited security access. Template calculations are working much better for my end users.
As our models are very calculation heavy, we have used both types. In addition, we have moved a lot of calculations to the sql side, so the Prophix models can be more efficient.