Page 1 of 1

TM1 Contributor Ownership Concept

Posted: Thu Jul 28, 2016 6:47 pm
by dharav
Hello All,

Environment: 10.2.0

We have approval application has been placed.


Business Case:

Users are consolidating their branch data in to their excel sheet.
Few users are copying and pasting data from their excel sheet to TM1 contributor.
I created an excel sheet using DBSW formula to send data directly to TM1 system
through perspective. As we have deployed the TM1 Approval application, user need to take ownership
first before they can send data in to TM1 system. After taking ownership in contributor, they can send their
data to TM1 system. Now, they have to go back to contributor to submit the nodes.

Objective:

User should also able to take ownership in TM1 workflow using TI process from perspective when approval application
has been deployed. So i want to find out the values to be changed in respective control cubes to enable the users to write back data from perspective without taking ownership from contributor.

thoughts to bring solution:


Following thoughts came out:

=> }tp_application_state shows the state of each node. If we change the value of state than shouldn't it change the workflow state in contributor? When i change the state value to 0 for top parent node than workflow state got changed
in the TM1 Contributor workflow. When i changed state value to 0 for anyother elements in the approval hierarchy
dimension elements than i did not find any changes in the TM1 contributor workflow. Any thoughts or concept to learn?

=> SecurityOverlayGlobal_Cube: It restricts the access rights of the node. If we change the value of this cube from 1 to 0 through TI process than can't we write back data in to TM1 system without taking ownership from contributor. I tried but user can't write back till he takes ownership. (May be i am missing something conceptually on this topic.)

=> Now we another TI process would submit data: Here TI process will change the SecurityOverlayGlobal_Cube value to 1 and application state value to 4 for leaf level elements & to 3 if the element is consolidation element provided the parent of this consolidation element having state value 0.


Can anyone throw further lights on this? is it possible to achieve while having approval hierarchy?

Please feel free if you require further information.

Thank You

Dharavv

Re: TM1 Contributor Ownership Concept

Posted: Fri Jul 29, 2016 4:27 pm
by dharav
I got it!!

}tp_application_state control cube is the place where you can manipulate the logic. It works.


1) Zero Out data for required approval hierarchy elements in this cube
2) get the details of the user who runs the process
3) Insert data in to }tp_application_state cube (it would work like taking an ownership)
4) User data input
5) TI process to change the state value in }tp_application_state cube. Now assign value 1 in securityOerlayGlobal cube for each approval hierarchy element
where state value is 4.

Thanks for your time!!