Can I have a code in a list mapped to different parent between two time periods?

Options

I wonder if someone have come across of this use case:

Our reporting hierarchy is based on Cost Centres i.e. Cost Centres are mapped to Business Units (Parent/Child relationship). There was a request to move a Cost Centre between two Business Units in July going forward, meaning that history remains unchanged. When I change the parent, all data related to this code moves with it. As you can understand I need the CC to stay as is until July (under E&M Cross) and move everything only going forward (to E&M APAC). It seems it's not possible in Anaplan, but I wonder if there is a known workaround ?

Answers

  • We can try to use a System module with Time as dimension to segregate the Reporting, you will just need to update some formulas and the structure of the C3 Cost Center (to include the parent when creating the code), so you will have somewhat duplicate cost centers on different parents.

    List:

    System Module with Time:

    Please tell me if this helps.

    Spread the love and humanity

  • @DanielSvocak I have built something that is a slight variation to what @ramonito recommended. Implement 2 lists for cost centres:

    • one that belongs to a financial hierarchy (this is the one you currently have). Follow what ramonito recommended with respect to prefixing the code with the parent. In his example, cost centre is "D" and is either prefixed by the parent "EMEA" resulting in EMEA_D or "EASTASIA" resulting in EASTASIA_D. For purpose of this discussion let's call the list "CC Hierarchy"
    • one that is a flat list (only has D as code). For the purpose of this discussion let's call the list "CC Flat"
    • create a mapping module between the financial hierarchy cost centre and the flat list cost centre. For example, create module below and call it "CC Mapping"

    Item

    CC Flat Mapping

    EMEA_D

    D

    EASTASIA_D

    D

    The benefit of this is that you are able to report on cost centre D regardless of its parent while also being able to report on cost centre D specific to its parent.

    So if you have a module dimensioned by "CC Hierarchy" and Month with history below. Let's call this module "CC Hierarchy Cost" and line item is value.

    Jan

    Feb

    Mar

    Apr

    Jun

    EMEA_D

    10

    20

    30

    EASTASIA_D

    40

    50

    You can have a module dimensioned by "CC Flat"

    Jan

    Feb

    Mar

    Apr

    Jun

    D

    10

    20

    30

    40

    50

    You would just need use a sum function

    'CC Hierarchy Cost'.value[SUM: 'CC Mapping'.'CC Flat Mapping']

    There's a bit more work you will need to do from the current design state you have at the moment but should help provide flexibility in your model for future use cases. Hope this helps.

  • @DanielSvocak

    Love the idea of using flat lists as I use them all the time. They become very important when using numbered lists as you can use the flat list as the Display Name (list formatted). Also, you might want to take a look at this lesson on effective dating to see if it gives you any ideas.

    https://learning.anaplan.com/enrol/index.php?id=512