Hierarchy

⤷

⤷

Basic Data
Data Element | /BOBF/OBM_AUTH_OBJECT |
Short Description | Authorization object for a BO |
Data Type
Category of Dictionary Type | D | Domain |
Type of Object Referenced | No Information | |
Domain / Name of Reference Type | XUOBJECT | |
Data Type | CHAR | Character String |
Length | 10 | |
Decimal Places | 0 | |
Output Length | 10 | |
Value Table | TOBJ |
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.obj. |
Medium | 15 | Auth. object |
Long | 20 | Auth. object for BO |
Heading | 40 | Authorization object for a BO |
Documentation
Definition
Element of the authorization system.
Use
An authorization object combines up to 10 authorization fields that are checked using the AND connective.
An authorization object used for a BOPF business object must follow a specific authorization field pattern regarding the first 2 fields. The first field must be ACTVT (activity) and the second field must be BO_SERVICE (service name, e.g. name of a BOPF action). Beginning with the third field, application-specific fields can be configured. In transaction BOBF only the application-specific authorization fields can be used for mapping to data fields.
Dependencies
Authorizations are checked against objects in the system. Authorization objects enable complex checks (linked to several conditions) of an authorization. For the authorization check to be successful, the user must pass the check for each field contained in the object.
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 |