Page 1 of 1
Number Consolidation based on security settings
Posted: Thu Mar 16, 2017 5:01 pm
by cdhodge2002
Looking for a little clarification on a security item that was brought to my attention by a user.
If I am a user and I have access to 3 children that roll up to a parent. The parent has a total of 6 children. If I grant security access to that parent and I go to report data off that parent will that aggregation be an aggregation of the 3 children I have access to or the 6 total children of the parent.
I heard this might be an enhancement in newer versions of TM1 but I am not totally sure. The version of TM1 I am working with is a couple of versions behind and consolidations sum the total of the children.
Re: Number Consolidation based on security settings
Posted: Thu Mar 16, 2017 5:36 pm
by Wim Gielis
It's the sum of 6 children, not 3.
I haven't heard of changes in this respect.
It's been always like still and will most probably remain like this.
Re: Number Consolidation based on security settings
Posted: Thu Mar 16, 2017 5:55 pm
by tomok
TM1 does not alter the results of a consolidated calculation to reflect only those cells beneath which a specific user has security access and likely never will. Doing so would totally blow out of the water the concept of cached results since now it would have to be by user.
Re: Number Consolidation based on security settings
Posted: Thu Mar 16, 2017 6:38 pm
by Edward Stuart
Reporting consistent numbers would become a nightmare so I'd be surprised if this was implemented
Re: Number Consolidation based on security settings
Posted: Thu Mar 16, 2017 9:17 pm
by lotsaram
cdhodge2002 wrote:If I am a user and I have access to 3 children that roll up to a parent. The parent has a total of 6 children. If I grant security access to that parent and I go to report data off that parent will that aggregation be an aggregation of the 3 children I have access to or the 6 total children of the parent.
I heard this might be an enhancement in newer versions of TM1 but I am not totally sure. The version of TM1 I am working with is a couple of versions behind and consolidations sum the total of the children.
That would be anything but an "enhancement". It would be a nightmare.
"Alternate facts" might be in vogue in politics but in finance and analytics the sum of a consolidation has an objectively correct value which is not influenced by users' ability to see all of the components underneath or not.
Re: Number Consolidation based on security settings
Posted: Fri Mar 17, 2017 12:41 pm
by Steve Rowe
Interesting problem though...
If you have a parent with 4 children and you have access to the parent and 3 of the children only then the security breaks.
Answers on a postcard.
Re: Number Consolidation based on security settings
Posted: Fri Mar 17, 2017 3:52 pm
by mvaspal
just an argument from the other other side: this worked in Cognos Planning, and many times proved to be a great feature; just search this forum for people looking for CP's access tables and then the non-perfect workarounds that TM1 gives you...
there are use cases when accumulating only those elements that you have access to is very useful; i.e. I do not think custom consolidations will be supported in CAFE/PAw, and building a User Group based hierarchy may not be the perfect solution
So I don't think this is a black/white topic
Re: Number Consolidation based on security settings
Posted: Fri Mar 17, 2017 4:42 pm
by Duncan P
Even in Cognos Planning the access tables did not affect the way in which the consolidation was done. If there data was there it was aggregated, even if it was invisible to the user. We had arguments internally about the problem Steve highlights but there was never any question of doing the aggregation any other way.
The other aspect was that as you moved up the organisation hierarchy (what we used to call the eList - you know, late 90s, e-Everything) you got the union of the access below.