Hi All,
I am using TM1 9.5.2 with cognos 10 BI security
We have Premium Planning and HR Planning in the same DB
My users(finance heads) need access to view the transaction logs (they want to see the changes and inputs made by other Underwriting users)
I cannot make them as admin because we have HR data in application
So, is there a way that i can avail him the transactional data for only the cubes that he has rights
Thanks
Regards
Guru
Admin note: Moved from the enhancements forum.
Users require access to view transaction logs without admin
-
guru1988fortm1
- Posts: 42
- Joined: Mon Feb 06, 2012 5:52 pm
- OLAP Product: Cognos TM1
- Version: PA 2.0.3
- Excel Version: Micrsoft Excel 2010
- Location: Chennai, India
-
lotsaram
- MVP
- Posts: 3706
- Joined: Fri Mar 13, 2009 11:14 am
- OLAP Product: TableManager1
- Version: PA 2.0.x
- Excel Version: Office 365
- Location: Switzerland
Re: Users require access to view transaction logs without ad
This is not an enhancement. By the looks this is just a model not meeting requirements or new requirements emerging that require a change.
You could load the transaction log records into a relational table, making sure you filter out and only load records for the relevant cube(s). Then give the finance heads access to and a mechanism to query the table. That will solve your immediate requirement.
However really it sounds like a revisit of the model might be needed. Transactional budgeting is pretty rare in business but quite common in the government sector - you can design a planning model to capture deltas and submitter information in the cube itself but I rather doubt that this would be needed. The issue of which underwriting users have updated forecast for given business areas should be managed by security and responsibility area, this is fundamental to any planning model and workflow may come into play also. Then all that is really needed is a versioning dimension with timestamped snapshots of the forecast and calculated deltas between each snapshot and the current live version.
You could load the transaction log records into a relational table, making sure you filter out and only load records for the relevant cube(s). Then give the finance heads access to and a mechanism to query the table. That will solve your immediate requirement.
However really it sounds like a revisit of the model might be needed. Transactional budgeting is pretty rare in business but quite common in the government sector - you can design a planning model to capture deltas and submitter information in the cube itself but I rather doubt that this would be needed. The issue of which underwriting users have updated forecast for given business areas should be managed by security and responsibility area, this is fundamental to any planning model and workflow may come into play also. Then all that is really needed is a versioning dimension with timestamped snapshots of the forecast and calculated deltas between each snapshot and the current live version.