Sum on Clone Day Period List

Highlighted
Community Boss

Sum on Clone Day Period List

Hi Team,

 

I have created a Clone Day Period list as I require to RANK data that is dimensionalised by Day but I cannot SUM the data into the Clone list when using the mapping

 

 Time(Day) with the Clone Day List as a property

IMG3.PNG

 

Source Data dimensionaled by Time(Day) 

IMG2.PNG

 

 Target module dimensionalised by Clone Day List and referencing the Source data

IMG1.PNG

 

Is there a restriction when using Time(Day)? I'm aware that you cannot use it as a Line Item property

 

Thanks

 

Mark

10 REPLIES 10
Highlighted
Frequent Contributor

Re: Sum on Clone Day Period List

Hi @MarkTurkenburg ,

 

In the source module "SMS Test Source", which dimesnion are you using TIME or Clone List ?

 

Thanks,

Naushad

Highlighted
Community Boss

Re: Sum on Clone Day Period List

Hi @naushad786 

 

The SMS Test Source module is dimensionalised by Time - Day

 

Thanks

Highlighted
Community Boss

Re: Sum on Clone Day Period List

it seems so...

 

I know when you have time as your dimension, if you SUM over a time mapping it won't get you anything just like here, without any warning, so it is possible that's a limitation.

Ill try to reproduce first amd get some feedback.


Nathan Rudman, Anaplan Model Builder
Highlighted
Super Contributor

Re: Sum on Clone Day Period List

Hi @MarkTurkenburg - Yes There are restriction on Time(Day).

 

if it is transaction list or any other list act as a dimension in your source module, then your formula works.

 

The reason you are not able to see the result in your target module is because,

                                                 when ever you are coming out of Time Dimension(Built in Dimension) then        an additional condition must also be mentioned in your formula.

 

Time - Built in Dimension in Anaplan

Clone Day List - is a List which you have created

 

The Term "Coming Out" in my previous sentence means - Source has Time as Dimension

                                                                                             Target has Custom Time List as Dimension,

so you don't have TIME dimension in Target.

 

in your Scenario - you should use TIMESUM function not SUM function.

 

Source Module : Time as Dimension

 

Capture1.JPGCapture2.JPG

 

Target Module : Clone Day as Dimension

 

Capture3.JPGCapture4.JPG

 

 

An Another Example

 

Source Module : Time as Dimension

 

My objective is "I want to Sum the values based out of Country(Line item: TEST)"

 

Capture1.JPGCapture2.JPG

 

 

Target Module : No Time(Build it Dimension) Dimension, but Country as Dimension.

 

 

Capture6.JPG

 

 

The Same output as we seen in your example.

So when ever you come out of Time Dimension, then Look for some Time functions in Anaplan.

 

 

 

 

Hope it make sense.

 

 

Thanks,

Sorna Raja Prabhu

Sorna Raja Prabhu
Highlighted
Community Boss

Re: Sum on Clone Day Period List

Thanks @Sorna Raja Prabhu 

 

Appreciate the detailed reply!

 

I'm going to use LOOKUP now that I can create a mapping table of Clone Day List to Date using @rob_marshall example below

 

Mark

Highlighted
Super Contributor

Re: Sum on Clone Day Period List

hi, you can use timesum to achieve this , and from period will be the mapping time to the list value by finditem

 

Kanishq17_0-1591185016202.png

here this is the custom day list in target

 

Kanishq17_1-1591185072492.png

source module with day timescale 

Highlighted
Master Anaplanner/Community Boss

Re: Sum on Clone Day Period List

@MarkTurkenburg ,

 

Don't use timesum as that will be a performance hinderance, but rather create a mapping module with Fake Time (or your Clone Days) to real time and do a lookup.

 

Rob

Highlighted
Super Contributor

Re: Sum on Clone Day Period List

hi @rob_marshall 

tried doing that but cant make mapping table as not possible to keep time period-day as format for line item

 

 

 

Highlighted
Master Anaplanner/Community Boss

Re: Sum on Clone Day Period List

@Kanishq17 ,

 

You can keep it as Date which will work.

 

2020-06-03_09-02-39.png

 

2020-06-03_09-02-59.png

 

Rob