SAP ABAP Data Element RSECLOPD_IOBJTYPE (Description Type for LOPD InfoObjects)
Hierarchy
☛
SAP_BW (Software Component) SAP Business Warehouse
⤷ BW-BEX-OT (Application Component) OLAP Technology
⤷ RSECLOPD (Package) Special Revision Requirements
⤷ BW-BEX-OT (Application Component) OLAP Technology
⤷ RSECLOPD (Package) Special Revision Requirements
Basic Data
Data Element | RSECLOPD_IOBJTYPE |
Short Description | Description Type for LOPD InfoObjects |
Data Type
Category of Dictionary Type | D | Domain |
Type of Object Referenced | No Information | |
Domain / Name of Reference Type | RSECLOPD_IOBJTYPE | |
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 | LOPD Type |
Medium | 20 | LOPD Type InfoObject |
Long | 40 | LOPD Type InfoObject |
Heading | 55 | LOPD Type InfoObject |
Documentation
Definition
To track access to data in accordance with the Spanish data protection law LOPD, InfoObjects in BW are highlighted as relevant for the purposes of LOPD. LOPD-relevant InfoObjects are InfoObjects that either identify a person (type P) or contain sensitive information about a person (type S).
Use
This setting records LOPD-relevant data requests (such as a BEx query) in BW.
Dependencies
All InfoObjects of type P or S must be highlighted as authorization relevant according to the BW authorization concept.
Example
Examples of possible identifying InfoObjects of type P: 0EMPLOYEE (employee number), 0CONTRACT (contract number).
Example of InfoObjects of type S that can potentially contain sensitive data: 0NUMSICK (number of sickness days), 0RELIGION (religious affiliation).
History
Last changed by/on | SAP | 20130604 |
SAP Release Created in | 700 |