Hierarchy Hell

[ADW]

I have a problem. Trying to get our HR guys on board with TM1. They have a HR structure in our accounting system (SAP) called org unit. Here is my problem:

Consolidated items contain their own values that need to be added to the consolidation, as below.

CEO (1)
---- PERS (20)
---- IS (25)
---- FIN (30)

Should be:

CEO (76) (Note: the 1 added in)
---- PERS (20)
---- IS (25)
---- FIN (30)

TI won't post to C level. So I created a flat hierarchy dimension and cube which I can post the numbers to. How can I then trick the system into doing the roll up I want?

[Michel Zijlema]

Hi,

You indeed can't store data on a consolidated level. A typical way to get this working in TM1 would be to build the hierarchy like:

Total CEO (76)
---- CEO (1)
---- PERS (20)
---- IS (25)
---- FIN (30)

IMO this is also a more transparant way of showing where the numbers are located.

Michel

[Christopher Kernahan]

If they insist on having this method then you could store it as a String element against each level of the heirachy.

But, really. Fight this as strongly as possible.

[ADW]

Hi Michael,

Thank you for your reply. I have implemeted this and it seems to work of (just need to adjust the TI to remove 'Total' group names with only one child). Certainly produces the numbers I need.

Christopher,

Appologies but I don't really understand your comment.

Cheers,

Adam

[Wim Gielis]

Christopher,

Appologies but I don't really understand your comment.

Cheers,

Adam

Leave it the way you have it now, that is the preferred approach.
Christopher only commented in case HR still wanted to write values to consolidations. Try to avoid it as much as possible.

[Alan Kirk]

Christopher,

Appologies but I don't really understand your comment.

Cheers,

Adam

Leave it the way you have it now, that is the preferred approach.
Christopher only commented in case HR still wanted to write values to consolidations. Try to avoid it as much as possible.

I agree with Wim but just to answer ADW's question for future reference; level 0 data in TM1 comes in two flavours, N elements and S elements. N type stores (Numeric) values, S types (which can only appear in the last dimension of a cube) store "strings" (or text, for the non-technical).

You can never write values directly to a numeric consolidation, but you can to a string consolidation. But, of course, if you store a value as a string you can't effectively calculate with it. (Slight oversimplification, but go with it.)

It's a way of working around your problem but as has already been stated you definitely shouldn't do it if you can avoid it.

[ADW]

Thanks all for your excellent replies