1. Administrator's Guide
  2. Getting Started with Planning
  3. Setting Application and System Properties
  4. Setting Threshold Limits for Applications

Setting Threshold Limits for Applications

You can set threshold limits for applications—warning thresholds and error thresholds—that, if exceeded, will issue warnings in application monitor so artifacts can be modified or deny system requests at runtime.

You can set the application threshold limits by adding the application properties described in this section.

To set threshold limits for applications:

  1. Select Administration, then Application, and then Properties.
  2. Select Application Properties to set properties and values for a Oracle Hyperion Planning application.
  3. Add the property by clicking Add, entering the property in the blank row, and then entering a value in Property Value:

    Table 2-4 Threshold Property Names and Descriptions

    PROPERTY_NAME Column Description

    Thresholds for the number of cells in a data entry form:

    WARNING_THRESHOLD_NUM_OF_CELLS

    ERROR_THRESHOLD_NUM_OF_CELLS

    A warning is issued and the artifact is shown in yellow in the application monitor if the number of cells in a form exceeds the warning threshold value.

    If the number of cells in a form exceeds the error threshold value, the form will not open.

    Tip:

    Consider redesigning the form to reduce the number of cells by reducing the number of segments and/or members. Use of suppression options may temporarily reduce the total cells retrieved, but the total cells may exceed the threshold as data increases.

    Thresholds for the number of planning units in a planning unit hierarchy:

    WARNING_THRESHOLD_NUM_OF_PUS

    ERROR_THRESHOLD_NUM_OF_PUS

    A warning is issued and the artifact is shown in yellow in the application monitor if the number of planning units in a planning unit hierarchy exceeds the warning threshold value.

    If the number of planning units in a planning unit hierarchy exceeds the error threshold value, you will not be able to save the planning unit hierarchy.

    Tip:

    Consider redesigning the planning unit hierarchy to reduce the number of planning units by reducing the selected primary and secondary members.

    Thresholds for the number of dimensions in the application:

    WARNING_THRESHOLD_FOR_NUM_DIMS

    ERROR_THRESHOLD_FOR_NUM_DIMS

    A warning or error is issued and the artifact is shown in yellow or red in the application monitor if the number of dimensions exceeds the warning or error threshold value, respectively.

    Tip:

    Try reducing the number of dimensions.

    Thresholds for the number of members in each dimension:

    WARNING_THRESHOLD_FOR_NUM_ACCOUNTS

    WARNING_THRESHOLD_FOR_NUM_ENTITIES

    WARNING_THRESHOLD_FOR_NUM_VERSIONS

    WARNING_THRESHOLD_FOR_NUM_SCENARIOS

    WARNING_THRESHOLD_FOR_NUM_YEARS

    WARNING_THRESHOLD_FOR_NUM_CURRENCIES

    WARNING_THRESHOLD_FOR_NUM_PERIODS

    WARNING_THRESHOLD_FOR_NUM_CUSTOM_DIM_MBRS

    A warning is issued and the artifact is shown in yellow in the application monitor if the number of members in a dimension (accounts, entities, versions, scenarios, and so on) exceeds the warning threshold value.

    Tip:

    To optimize calculation performance and data storage, try reducing the number of members in this dimension. Consider purging historical data (along with the corresponding members).

    Thresholds for business rules run in the context of a form:

    WARNING_SYNC_THRESHOLD_FOR_NUM_BLOCKS

    ERROR_SYNC_THRESHOLD_FOR_NUM_BLOCKS

    Thresholds for long running business rules run stand alone:

    WARNING_ASYNC_THRESHOLD_FOR_NUM_BLOCKS

    ERROR_ASYNC_THRESHOLD_FOR_NUM_BLOCKS

    A warning or error is issued and the artifact is shown in yellow or red in the application monitor if the number of blocks processed in a rule exceeds the warning or error threshold value, respectively.

    Tip:

    Consider adding additional scoping to the business rule to reduce the number of blocks processed.

    Thresholds for business rules run in the context of a form:

    WARNING_SYNC_THRESHOLD_FOR_NUM_PASSES

    ERROR_SYNC_THRESHOLD_FOR_NUM_PASSES

    Thresholds for long running business rules run stand alone:

    WARNING_ASYNC_THRESHOLD_FOR_NUM_PASSES

    ERROR_ASYNC_THRESHOLD_FOR_NUM_PASSES

    A warning or error is issued and the artifact is shown in yellow or red in the application monitor if the number of passes made through the database in a rule exceeds the warning or error threshold value, respectively.

    Tip:

    Consider grouping dimensions wherever possible when you calculate a series of dimensions. Avoid using parentheses unnecessarily when you calculate a series of formulas. You may also reconsider the usage for CALCMODE and CREATENONMISSINGBLK options in the calculation script.

    Thresholds for data export from a source during Reporting Mappings execution:

    WARNING_THRESHOLD_FOR_CUBE_LINK_NUM_BLOCKS

    ERROR_THRESHOLD_FOR_CUBE_LINK_NUM_BLOCKS

    A warning is issued and the artifact is shown in yellow in the application monitor if the number of blocks from which the data is being exported exceeds the warning threshold value.

    If the number of blocks from which the data is being exported exceeds the error threshold value, Reporting Mappings will not execute at runtime.

    Tip:

    Consider adding additional scope to the mapping to reduce the number of blocks processed.
  4. Click Save and confirm your changes.