SAP ABAP Data Element SLDW_SAL_MODE (Recording Mode for Security Audit Log)
Hierarchy
☛
SAP_BASIS (Software Component) SAP Basis Component
⤷ BC-SEC (Application Component) Security
⤷ SLDW (Package) Generic Whitelist Administration
⤷ BC-SEC (Application Component) Security
⤷ SLDW (Package) Generic Whitelist Administration
Basic Data
Data Element | SLDW_SAL_MODE |
Short Description | Recording Mode for Security Audit Log |
Data Type
Category of Dictionary Type | D | Domain |
Type of Object Referenced | No Information | |
Domain / Name of Reference Type | SLDW_SAL_MODE | |
Data Type | CHAR | Character String |
Length | 1 | |
Decimal Places | 0 | |
Output Length | 1 | |
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 | SAL |
Medium | 15 | SAL Mode |
Long | 40 | Security Audit Log Recording Mode |
Heading | 41 | Recording Mode for Security Audit Log |
Documentation
Definition
You have the option to log checks for generic whitelists in the Security Audit Log (SAL). You can choose between the following options:
- N - No recording in the Security Audit Log (default setting)
- E - Record failed checks in the Security Audit Log (for critical processes)
- A - Record all checks in the Security Audit Log (exceptional setting for troubleshooting)
The following SAL messages are used for the logging:
- DUL - Check on &A in whitelist &B was successful
- DUM - Check on &A in whitelist &B failed
If an active whitelist is changed, the event DUN is triggered, regardless of this parameter.
Use
Dependencies
SAL messages are only written if the Security Audit Log is active and the current filter settings contain the messages listed above.
You can check this with transaction SM19.
Example
History
Last changed by/on | SAP | 20141013 |
SAP Release Created in | 740 |