Hierarchy

⤷

⤷

Basic Data
Data Element | /BOBF/OBM_NODE_AUTH_CHECK_REL |
Short Description | Node has own authorization checks |
Data Type
Category of Dictionary Type | D | Domain |
Type of Object Referenced | No Information | |
Domain / Name of Reference Type | BOOLE | |
Data Type | CHAR | Character String |
Length | 1 | |
Decimal Places | 0 | |
Output Length | 1 | |
Value Table |
Further Characteristics
Search Help: Name | ||
Search Help: Parameters | ||
Parameter ID | ||
Default Component name | ||
Change document | ||
No Input History | ||
Basic direction is set to LTR | ||
No BIDI Filtering |
Field Label
Length | Field Label | |
Short | 10 | Auth.check |
Medium | 15 | Auth. checks |
Long | 20 | Has authoriz. checks |
Heading | 40 | Node has own authorization checks |
Documentation
Definition
This flag indicates wether or not the node supports own authorization checks.
Use
To configure authorization checks on this node, mark the flag.
Not every node is relevant for authorization checks. Moreover, a node inherits authorization checks along the composition tree. If, for example, authorization checks are configured for the ROOT node, a RETRIEVE core service that is called on the ITEM node level not only must pass the authorization checks on this level, but must also pass the authorization checks that are configured for the corresponding ROOT node instances.
Specify a check class if you mark the flag. This may be the library class /BOBF/CL_LIB_AUTHORITY_CHECK.
Dependencies
The flag on the BO level is the main flag for switching off authorization checks: If it is not marked, it overrides the authorization check flags on the node level, which may be marked, and no authorization is checked.
Example
For more information about the BOPF authorization concept, see the class documentation of the library class /BOBF/CL_LIB_AUTHORITY_CHECK.
History
Last changed by/on | SAP | 20130604 |
SAP Release Created in | 747 |