Hierarchy
SAP_BW (Software Component) SAP Business Warehouse⤷
BW-BEX-OT (Application Component) OLAP Technology⤷
RSECLOPD (Package) Special Revision Requirements
Basic Data
| Data Element | RSECLOPD_ID |
| Short Description | LOPD: InfoObject Group ID |
Data Type
| Category of Dictionary Type | Direct Type Entry | |
| Type of Object Referenced | No Information | |
| Domain / Name of Reference Type | ||
| Data Type | CHAR | Character String |
| Length | 10 | |
| Decimal Places | 0 | |
| Output Length | 10 | |
| 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 ID |
| Medium | 20 | LOPD ID |
| Long | 40 | LOPD: InfoObject Group ID |
| Heading | 40 | LOPD: InfoObject Group ID |
Documentation
Definition
An LOPD group describes a set of InfoObjects that allow access to personal data critical for data protection.
Use
The InfoObjects in an LOPD group either identify an individual (type 'P') or include sensitive information about a person (type 'S'). For a data request (in a BEX query for example) to be recognized as relevant in terms of the Spanish data protection law LOPD, all InfoObjects of type 'P' and at least one InfoObject of type 'S' have to be included in the request.
Dependencies
All InfoObjects of type P or S must be highlighted as authorization relevant according to the BW authorization concept.
Example
Example 1: Persons can be identified by their employee number. Sensitive information about employees can be found in InfoObjects 0NUMSICK (number of sick days) and 0RELIGION (religious affiliation). The LOPD group can be defined by the InfoObjects:
0EMPLOYEE (type 'P')
0NUMSICK (type 'S')
0RELIGION (type 'S')
If either of these combinations (0EMPLOYEE, 0NUMSICK) and (0EMPLOYEE, 0RELIGION) occurs within a data request (BEx query for example), the system identifies the request as an LOPD-relevant event.
Example 2: Persons can be identified using a combination of their surname and date of birth. Sensitive personal information can be found in InfoObjects 0NUMSICK (number of sick days) and 0RELIGION (religious affiliation). The LOPD group can be defined by the InfoObjects:
0DATEOFBIRTH (type 'P')
0LASTNAME (type 'P')
0NUMSICK (type 'S')
0RELIGION (type 'S')
The following combinations of InfoObjects are LOPD-relevant:
(0DATEOFBIRTH , 0LASTNAME , 0NUMSICK)
(0DATEOFBIRTH , 0LASTNAME , 0RELIGION)
The following combinations are not LOPD-relevant:
(0DATEOFBIRTH , 0RELIGION, 0NUMSICK) --> information is not sufficient to identify an individual
(0DATEOFBIRTH , 0LASTNAME) --> information requested does not include sensitive data
History
| Last changed by/on | SAP | 20130604 |
| SAP Release Created in | 700 |
