Hierarchy
SAP_BASIS (Software Component) SAP Basis Component⤷
BC-SEC (Application Component) Security⤷
SECU_ABAP (Package) Security and Protection of ABAP Programs
Basic Data
| Data Element | SCEN_NAME |
| Short Description | Scenario Name for Switchable Authorization Check |
Data Type
| Category of Dictionary Type | D | Domain |
| Type of Object Referenced | No Information | |
| Domain / Name of Reference Type | SCEN_NAME | |
| 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 | Name |
| Medium | 15 | Scenario Name |
| Long | 0 | |
| Heading | 0 |
Documentation
Definition
A thematically-linked set of switchable authorization checks is combined into a scenario. The rules of this set are only taken into account during an authorization check using the method CL_SACF=>AUTH_CHECK_SPEC.
The scenario definition is a Workbench development object (transport SUCD) and supports the partner namespace.
A scenario is defined by its header information (scenario status, Security Audit Log recording mode, and an explanatory SAP Note), and a list of authorization objects with assigned check mode.
Use
Dependencies
To be able to use the scenario productively, In addition to the scenario definition there must be an active scenario with the same name. The check of the method CL_SACF=>AUTH_CHECK_SPEC is only performed on the active scenario. Active scenario are defined as cross-client Customizing are are distributed with the transport object SUCC.
Example
Use the example program SACF_TEST_CASE as a possible implementation example.
History
| Last changed by/on | SAP | 20141013 |
| SAP Release Created in | 740 |
