Hierarchy
SAP_BW (Software Component) SAP Business Warehouse⤷
BW-BEX-OT (Application Component) OLAP Technology⤷
RSEC (Package) BI AS Analysis Authorizations
Basic Data
| Data Element | RSECTEXTSTATUS |
| Short Description | Status of Authorizations |
Data Type
| Category of Dictionary Type | D | Domain |
| Type of Object Referenced | No Information | |
| Domain / Name of Reference Type | TEXT40 | |
| Data Type | CHAR | Character String |
| Length | 40 | |
| Decimal Places | 0 | |
| Output Length | 40 | |
| 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 | Status |
| Medium | 20 | Status of Auth. |
| Long | 40 | Status of Authorizations |
| Heading | 55 | Status of Authorizations |
Documentation
Definition
Version Status
Active: The last edited version has been activated.
Inactive: An edited version exists that has not yet been activated; this version differs from the current version.
Not Saved: The edited version has been changed on the user interface, but has not yet been saved.
Saved: The edited version has been saved.
Runtime Version
Status of the runtime version, that is, the version made available to reporting.
Independent of these settings, you can also deactivate a version for reporting, or specify that it is never to be activated.
Origin
The origin of an analytics security object indicates whether the object was created manually or generated automatically. You can make changes to generated authorizations. However, the next generation run may overwrite any changes made. The system therefore displays a message when you attempt to change this type of object.
Use
Dependencies
Example
History
| Last changed by/on | SAP | 20130604 |
| SAP Release Created in | 710 |
