Best Of

@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"

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.

You can have a module dimensioned by "CC Flat"

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.

@MirBorishkevich Went through a similar build requirement recently, and found the following discussion from a few years back to be very helpful.

@rob_marshall thanks, I think I've figured this out.

There was one column in the source file that had a blank column header. If I delete that column in the file then I get the normal time mapping window.