Mapping Artificial Timescale to Built-in Timescale


Hello, I have a Client that will need to use a 13-period timescale for their audit adjustments in their P&L but will budget and forecast using Anaplan's built-in timescale. Is there any way to map the artificial timescale using a list with 13 periods to the built-in timescale? Best, Chase Cantwell


Best Answers

  • peter_mcanena
    Yes, but exactly how you go about it depends on how your client needs the mapping to work. Assuming the built-in timescale is a standard setup, you can do it like this:
    1. Create a new list called Include, with just one member, also called Include. This list shouldn't have a top level
    2. Create a new module called Timescale Mapping, dimensioned by both timescales, with a line item called Include. This line item should return Include.Include where the timescales intersect, and blank otherwise
    3. To get data from a module "Artificial Data" dimensioned by the artificial timescale into a module dimensioned by the built-in timescale, create a line item called Mapped Data, dimensioned by the built-in timescale and the Include list. This line item should have the formula
    Artificial Data.Source Lineitem[SUM: Timescale Mapping.Include]
    4. Now add a second line item in the same module, dimensioned by the built-in timescale only, with the formula
    Mapped Data[SELECT: Include.Include]
  • harish_bk
    Answer ✓
    Hi Chase other way would be:

    1) Create a dummy time list with 13 periods
    2) Create a module with This list and one line item called time mapping
    3) Time mapping line item should be list fomatted with anaplan time (as selected list)
    4) Map the dummy time with anaplan time (Selecting required periods in drop down)

    1 - Jan 16
    12 -  Dec 16
    13 - Dec 16 so on

    5) Create a module using all required dimensions and the dummy time and load data
    6) Load data in the above model
    7) Create a module similar to above module and replace the same with anaplan time
    8) Link the models in step 5 and step 7 with lookup from the module created in step 2