Planual Explained - Day 31

Highlighted
Master Anaplanner/Community Boss

Planual Explained - Day 31

"Rule 1.01-04": Article 1, Chapter 1, and Rule 4” Consider All Periods. Consider the use of All Periods.This is effectively the Top Level for time and whilst increasing the model cell count very slightly it does allow for flexibility in modelling.It goes against PERFORMANCE elements of PLANS if you wish to go against this rule

Use Case: Ability to see the lifetime Sales for each Region

Here is how it was done in Pre Planual Era. We used to use TIMESUM to aggregate the values from a module dimensioned by Time to a module which is without Time dimension.

Source Module:

Misbah_0-1599211909109.png

Target Module:

Misbah_1-1599211918367.png

What is wrong with this method? TIMESUM is a single threaded function and takes a heavy toll on performance. Hence should be avoided as much as possible

Here is how it should be done in Planual Way:

Go to Time Page of your model and activate the “Total of All Periods” Option. It does increase the cell count marginally but it gives you the performance benefits in return.

Misbah_2-1599211966946.png

Use Select Function on All Periods and pull the values

Misbah_3-1599211975676.png

 

1 REPLY 1
Highlighted
Master Anaplanner/Community Boss

Re: Planual Explained - Day 31

@Misbah 

TIMESUM is a killer, as @rob_marshall has reminded me at least six times. Never hurts to hear it again, especially if that function can be avoided.


Jared Dolich