Hierarchy
SAP_BS_FND (Software Component) SAP Business Suite Foundation⤷
AP-RC-BOF-CFN (Application Component) Business Object Processing Framework Configuration⤷
/BOBF/CONFIGURATION (Package) Business Object Processing Configuration
Basic Data
| Data Element | /BOBF/OBM_AUTH_FIELD |
| Short Description | Authorization field for a BO |
Data Type
| Category of Dictionary Type | D | Domain |
| Type of Object Referenced | No Information | |
| Domain / Name of Reference Type | XUFIELD | |
| Data Type | CHAR | Character String |
| Length | 10 | |
| Decimal Places | 0 | |
| Output Length | 10 | |
| 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.field |
| Medium | 15 | Auth. field |
| Long | 20 | Auth. field for BO |
| Heading | 40 | Authorization field for a BO |
Documentation
Definition
Element in the authorization concept, e.g. activity, company code, or material group.
Use
Authorization objects and authorization checks contain fields for quantities that are checked to verify user authorizations.
Dependencies
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.
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 |
