Show TOC

Settings for Hierarchy AuthorizationsLocate this document in the navigation structure

Type of Authorization

You can define the authorization starting from a node of the hierarchy in different ways:

  • 0 for the node
  • 1 for a subtree below the node
  • 2 for a subtree below the node up to and including a level (absolute)

    You must define a level for this type. A typical example of an absolute level is data protection with regard to the degree of detail of the data (works council ruling: no reports at employee level only at more summarized levels).

  • 3 for the entire hierarchy
  • 4 for a subtree below the node up to and including a level (relative)

    You must specify a level that is defined relative to the node for this type. It makes sense to specify a relative distance if an employee may only expand the hierarchy to a certain depth below his or her initial node, but this node moves to another level when the hierarchy is restructured.

Hierarchy Levels

For types 2 and 4 you can specify, in Hierarchy Level, the level to which the user can expand the hierarchy.

  • With authorization type 2 (up to and including a level, absolute), the level refers to the absolute number of the level in the hierarchy where the top-most node of the hierarchy is level 1.
  • With authorization type 4 (up to and including a level, relative) the level number refers to the number of levels starting from the selected node itself which is level 1.

Validity Area

In the Validity Area you specify in exactly which ways a hierarchy authorization has to match a selected display hierarchy for it to be included in the authorization check.

  • Type 0 (very strict check): Name and version of the hierarchy upon which the hierarchy authorization is based have to agree with the selected display hierarchy. Your key date (the upper validity limit) has to be greater than or equal to the key date (the upper validity limit) of the selected display hierarchy.
  • Type 1: The name and version of the hierarchy upon which the hierarchy authorization is based have to agree with the selected display hierarchy.
  • Type
    2
    : The name of the hierarchy on which the hierarchy authorization is based has to agree with the display hierarchy.
  • Type 3 (least strict check): None of the three properties have to match.
    Caution

    Note that in some circumstances, setting a check level that is too low may lead to more nodes being selected using hierarchy node variables that are filled from authorizations, than actually exist in the display hierarchy for the query. This can cause an error message.

    Note that hierarchy authorizations can calculate single values that are the end nodes (leaves) of non-displayed hierarchy, but that in this case, the strictest check type, which is 0, is valid.

    Note

    As a general rule, make the check as strict as possible. The default is type 0.