Hierarchy
SAP_BASIS (Software Component) SAP Basis Component⤷
BC-SRV-GBT-OBL (Application Component) General Object Relations⤷
SOBL (Package) Generic Relation Service for Business Objects
Basic Data
| Data Element | OBLPERS |
| Short Description | Role Records Are Not Written |
Data Type
| Category of Dictionary Type | D | Domain |
| Type of Object Referenced | No Information | |
| Domain / Name of Reference Type | OBLROLPERS | |
| 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 | NoRl.Rcrds |
| Medium | 20 | No Role Records |
| Long | 35 | Role Records Are Not Written |
| Heading | 35 | Role Records Are Not Written |
Documentation
Definition
Use
If this indicator is set, the role instances are not written to a separate table. The disadvantage of this is that performance problems can occur when relationships are accessed generically (without giving the relationship type). Therefore, only set this indicator when relationships in which this role occurs are not to be accessed generically.
If this indicator is not set, the role instances are written in a separate table. This has the disadvantage that the table, which can get very large, contains redundant information. On the other hand, performance problems when accessing the relationships generically can be avoided.
Dependencies
Examples
The existence of role records is a prerequisite for reading document flows and for the display of relationships using generic object services.
Relationships with notes or attachments do not need persistent roles because the relationship type is given when the relationships are read.
History
| Last changed by/on | SAP | 20010130 |
| SAP Release Created in | 50A |
