TM1 Forum

Hello All

In our responsibility application, we have 3 cubes. 2 cubes have metro level (metrohierarchy) which is a approval dimension.
in cube 3, the city level hierarchy is being used along with metros (detail level hierarchy)

Issue:

When user submit for the node, User wont be able to take ownership in first 2 cube. This behaviour is normal. In 3rd cube, users are able to write which is also as expected but they are not able to submit their data at city level. it (cube 3) doesn't have approval dimension. We want user to do their forecast at city level all time eventhough the metro level submission is locked.

Does it have possible solution? What is it, if any?

What i tried:

As user couldn't able to submit or commit the data once they have submitted the data after we locked those from top node. I tried to reset the application and write a rule in cell security cube to make that cube read for most of the metro (not all) user. These action had made 2 cubes read only but in third cube what we write is not going to submit or commit eventhough option for same availble on above option panel


I am still looking in to it. If anyone has experienced it this or similar of this issue, it would help a lot with your directions.

Thanks

Dharav Patel

Is there an option to just have 2 applications (1 for each approval hierarchy)?

declanr wrote:Is there an option to just have 2 applications (1 for each approval hierarchy)?

we dont have that option. Even we recomanded same. Any work-around?

I want to know the logic behind below experienced i noticed:

In cube A, I write a cell security rule to make that cube read only for XYZ group. Cube A consist approval hierarchy.

In Cube B, We dont have approval dimension and there is no cell security rule. Users are able to input but can not commit the data or submit the data. When i removed the rule from Cube A than in Cube B users are able to commit or submit the data.

I would like to know the logic behind above situation and is there a way to alter this behavior in Cube B so users can commit the data while cell security "READ" rule applied in Cube A. (Cube A has approval dimension and Cube B doesn't have approval dimension.

Thanks

Thank You dclanr

I found the solution. I just had to go further one step and have to comment original rule and integrate it with my new rule. Now it works. Thank You so much again.

Dharav

Hello

I utilized the above cell security rule for the workflow hierarchy also to open the forecast for the user for only given N level element. All other element would still remain locked.

We just have to change the value of attributes where we want to make changes.

Thanks

Dharav

Hi everybody,
I have Some problem we TM1 applications. I have 2 applications("UPDATE" and "FIRST BUDGET") with same approval hierarchy(dim:"Company") based on the same Cube("Budget"). In one of dimension in this cube dim:"Versions" I have 2 elements ('version1','version2'). I want to submit each of these elements in the same hierarchy of acceptance. I want to submit "Version1" with FIRST BUDGET application with the same hierarchy as version2 but without locking this second app UPDATE.I want to have still Write permision on Version2 in UPDATE application. Now I can't becouse when I submit on one of appliactions then when I want to use this second I get "Dimension approval for the current application is no longer available". I don't know that it is clear what I mean. But if it is and any body can help me resolve this I will be very greatfull.
Best Regards
DK

http://www-01.ibm.com/support/docview.w ... wg21659476 would help.