Hierarchy
⤷ BC-SEC (Application Component) Security
⤷ SLDW (Package) Generic Whitelist Administration
Basic Data
Data Element | SLDW_NAME |
Short Description | Name of a Generic Whitelist |
Data Type
Category of Dictionary Type | D | Domain |
Type of Object Referenced | No Information | |
Domain / Name of Reference Type | SLDW_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 | Whitelist Name |
Long | 40 | Name of a Whitelist |
Heading | 40 | Name of a Generic Whitelist |
Documentation
Definition
A whitelist (also known as a positive list) is a collected of trusted elements of a type.
For generic whitelists in SAP applications, the whitelist name is the key attribute for the properties (header attributes, element list) of a whitelist.
The whitelist definition is a Workbench development object (transport object SLDD) and supports the partner namespace. A whitelist is defined by header information (whitelist status, SAL recording mode, optional error messages, and an explanatory documentation reference), and a list of whitelist elements with assigned check status.
Use
To be able to use the whitelist productively, in addition to the whitelist definition, there must be an active whitelist with the same name.
The generic whitelist check with the method CL_SLDW=> CHECK_WHITE_LIST( ) is performed only on the active version.
You can maintain whitelists using transaction SLDW.
Dependencies
The check is always performed on the active version of the whitelist.
Example
Use the example program SLDW_TEST_AND_DEMO as a possible implementation example.
History
Last changed by/on | SAP | 20141013 |
SAP Release Created in | 740 |