SAP ABAP Data Element XUFBLOCK1 (Price not relevant for function block read authorization)
Hierarchy
☛
SAP_BASIS (Software Component) SAP Basis Component
⤷ BC-SEC-USR-ADM (Application Component) User and Authorization Management
⤷ SUSR (Package) ABAP User Administration
⤷ BC-SEC-USR-ADM (Application Component) User and Authorization Management
⤷ SUSR (Package) ABAP User Administration
Basic Data
Data Element | XUFBLOCK1 |
Short Description | Price not relevant for function block read authorization |
Data Type
Category of Dictionary Type | D | Domain |
Type of Object Referenced | No Information | |
Domain / Name of Reference Type | XUFBLOCK | |
Data Type | CHAR | Character String |
Length | 8 | |
Decimal Places | 0 | |
Output Length | 8 | |
Value Table | TFBLK |
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 | F-Block |
Medium | 15 | Read auth. FB |
Long | 20 | Read auth. for FB |
Heading | 2 | FB |
Documentation
Definition
Function blocks, which are entered here, have read authorization for the current authorization object, without the user having to additionally be considered as an Addon-Infouser.
Example: Object XYZ is assigned to the function block SD.
MM and CO are entered in the fields 'readable for FB'.
When an MM or CO full user (user with authorization for objects which are assigned to MM or CO) has a reading access authorization for the object XYZ (value 03 in field ACTVT), this user is neither an SD user nor an Addon-Infouser.
If the user in this example is, for example, an FI full user, he or she is regarded as an Addon-Infouser.
If the user has a change authorization for this object he or she becomes an SD full user.
History
Last changed by/on | SAP | 20110908 |
SAP Release Created in |