Topic
  • 8 replies
  • Latest Post - ‏2012-09-13T07:05:20Z by Richard Allan
Richard Allan
Richard Allan
12 Posts

Pinned topic TM1 Planner / Contributor

‏2012-09-06T14:11:30Z |
Hi

Is there anyway of turning off the ability in TM1 Planner / Contributor to input data on a consolidated level? It automatically writes data to the leaves and this could scupper the budgeting process ie. users input figures against leaf level nodes and then the reviewer at a consolidated level writes to the consolidated value and over-writes the leaf level values.

Cheers
Richard
Updated on 2012-09-13T07:05:20Z at 2012-09-13T07:05:20Z by Richard Allan
  • Rizwan.Kaif
    Rizwan.Kaif
    197 Posts

    Re: TM1 Planner / Contributor

    ‏2012-09-06T15:33:45Z  
    In short to-date there is no way to disable the entry at the consolidation level in the TM1Web or Contributor.

    By default it will do spreading to the children if data is entered at the consolidation level.

    Cheers!
    Rizwan Kaif
  • kielmc
    kielmc
    8 Posts

    Re: TM1 Planner / Contributor

    ‏2012-09-06T15:38:52Z  
    Simply implement element level security on your approval dimension, allowing only READ access to consolidated elements, and this should prevent the default spreading behavior.
  • Richard Allan
    Richard Allan
    12 Posts

    Re: TM1 Planner / Contributor

    ‏2012-09-07T07:09:09Z  
    In short to-date there is no way to disable the entry at the consolidation level in the TM1Web or Contributor.

    By default it will do spreading to the children if data is entered at the consolidation level.

    Cheers!
    Rizwan Kaif
    Thank you for the quick replies - I'll try the element security although I suspect the writing to leaf values from the consolidation spread will still work.
  • Richard Allan
    Richard Allan
    12 Posts

    Re: TM1 Planner / Contributor

    ‏2012-09-07T07:23:16Z  
    • kielmc
    • ‏2012-09-06T15:38:52Z
    Simply implement element level security on your approval dimension, allowing only READ access to consolidated elements, and this should prevent the default spreading behavior.
    Yup - setting read only on the consolidated node worked a treat - thank you!
    Of course everytime the plan gets redeployed, I'll have to edit the security manually but at least it worked.
  • Rizwan.Kaif
    Rizwan.Kaif
    197 Posts

    Re: TM1 Planner / Contributor

    ‏2012-09-07T14:00:48Z  
    Yup - setting read only on the consolidated node worked a treat - thank you!
    Of course everytime the plan gets redeployed, I'll have to edit the security manually but at least it worked.
    Instead of manually updating the security you can write a TI which will change the Security rights the consolidate nodes. Doing it through the TI will automate it and will not be prone to human errors.
    Cheers!
    Rizwan Kaif
  • Richard Allan
    Richard Allan
    12 Posts

    Re: TM1 Planner / Contributor

    ‏2012-09-11T09:01:31Z  
    Instead of manually updating the security you can write a TI which will change the Security rights the consolidate nodes. Doing it through the TI will automate it and will not be prone to human errors.
    Cheers!
    Rizwan Kaif
    Hi Rizwan

    Could you give me a flavour of what the TI process would look like please - sounds like a good idea.

    Cheers
    Richard
  • Rizwan.Kaif
    Rizwan.Kaif
    197 Posts

    Re: TM1 Planner / Contributor

    ‏2012-09-11T14:28:29Z  
    Hi Rizwan

    Could you give me a flavour of what the TI process would look like please - sounds like a good idea.

    Cheers
    Richard
    You can do it through TI or Rules.

    1) If using TI then use the Approval Dimension as the Data source to loop through the Dimension elements. In the Data Tab you can do something like:
    
    #Check 
    
    if it is a consolidated node and change the security IF (DTYPE(dim , vElem) @= 
    'C' ); ELEMENTSECURITYPUT(
    'READ', dim , vElem , vGroupName); ENDIF;
    


    2) If using Rules then write the following rule for the }ElementSecurity_DimensionName cube:
    
    SKIPCHECK; FEEDSTRINGS;   [
    'GroupName'] = S: IF( ELLEV(
    'ApprovalDim' , !ApprovalDim) = 0 , 
    'WRITE' , 
    'READ' );   FEEDEERS;
    


    Also make sure you do SecurityRefresh to see the results after making these changes.

    Hope that helps!
    Rizwan Kaif
  • Richard Allan
    Richard Allan
    12 Posts

    Re: TM1 Planner / Contributor

    ‏2012-09-13T07:05:20Z  
    You can do it through TI or Rules.

    1) If using TI then use the Approval Dimension as the Data source to loop through the Dimension elements. In the Data Tab you can do something like:
    <pre class="jive-pre"> #Check if it is a consolidated node and change the security IF (DTYPE(dim , vElem) @= 'C' ); ELEMENTSECURITYPUT( 'READ', dim , vElem , vGroupName); ENDIF; </pre>

    2) If using Rules then write the following rule for the }ElementSecurity_DimensionName cube:
    <pre class="jive-pre"> SKIPCHECK; FEEDSTRINGS; [ 'GroupName'] = S: IF( ELLEV( 'ApprovalDim' , !ApprovalDim) = 0 , 'WRITE' , 'READ' ); FEEDEERS; </pre>

    Also make sure you do SecurityRefresh to see the results after making these changes.

    Hope that helps!
    Rizwan Kaif
    Hi Rizwan

    Thank you for that - a function I wasn't aware of.

    Cheers
    Richard