CUMULATE optimum use

Question

Hi All,

I'm trying to replace the use of CUMULATE to produce a running total in a module Dimensioned by 'fake time' - so I can't use PREVIOS, for example.

I am trying to establish if this is a worthwhile exercise - the relevant MAPS report shows 00.00% calculation effort against the CUMULATE formula and a relatively low cell count of 61k. We don't have BPI figures available currently.

I have heard CUMULATE should not be used in conjunction with 'fake time' (though I don't get why this is the case,  as the formulas are working fine)  - if so why not?

Also, I am having structuring a "WEEK CHAIN" structure without a substantial re-structure of the current module. Can some one point to a WEEK CHAIN case study i could reference please?

ChrisG532 · Answer

Thanks all for you inputs, which I sense, Rob says, "nailed it".

rob_marshall · Answer

@devrathahuja nope, nothing to add, you nailed it.

devrathahuja · Answer

@ChrisG532 - The main issue with cumulate is that it is single threaded and can be a cause of bottleneck. However, with a low cell count of 61k it does not seem like that should be a big issue.

However, if you still wanted to replace it, an easier way would be to map the data from your fake time to native time, use the previous set up in that case and remap it back to fake time. Again, for 61k cell count, this could instead end up taking more calc effort than the cumulate.

I think @rob_marshall can add a bit more to this :)