Forum Discussion

Marcello's avatar
Marcello
Contributor
3 years ago

prevent users to work on wrong periods

Hi, is there an easy way to prevent users to work on wrong periods? It seems that all periods in Onestream are open for data load.   This request is mostly related to statutory consolidation....
Cube Security
Metadata
Methodology
Time
  • PeterFu's avatar
    PeterFu
    3 years ago

    Hi Marcello,

     

    OneStream is by default open for all periods, no need of opening periods like HFM. I assume Historical data will be locked once completed. You can lock future years and reopen the periods when you get there (can be done in a batch job, not doing one-by-one).

     

    In addition, you can set the End-year under Application properties to just 1 - 2 years ahead (depending on your Planning and Forecast processes). Then you do not need to lock that many periods. See print screen below.

     

     

    Peter

  • TonyToniTone's avatar
    TonyToniTone
    3 years ago

    A couple of ways you can do it.  

    1.  Like Peter mentioned, you can batch lock all Workflows.  You would have to do it by year.  Then unlock the period each month that you would like to load

    2.  The second option would be to control data loading and data processing by Scenario Type through the "Enforce Global POV" option in Application Properties

    This way, the Admin can control what period users can process for any Scenario assigned the Actual Scenario Type.  In addition, you can align the Import step to the Global POV.  This can be done by setting up the Time and Scenario Dimensions in the Data Source to use Global Datakey Time and Global Datakey Scenario.  Another step to help ensure that Global POV drives the control needed.  

     

TonyToniTone's avatar
TonyToniTone
Contributor II
3 years ago

A couple of ways you can do it.  

1.  Like Peter mentioned, you can batch lock all Workflows.  You would have to do it by year.  Then unlock the period each month that you would like to load

2.  The second option would be to control data loading and data processing by Scenario Type through the "Enforce Global POV" option in Application Properties

This way, the Admin can control what period users can process for any Scenario assigned the Actual Scenario Type.  In addition, you can align the Import step to the Global POV.  This can be done by setting up the Time and Scenario Dimensions in the Data Source to use Global Datakey Time and Global Datakey Scenario.  Another step to help ensure that Global POV drives the control needed.