SAP ABAP Data Element OBLROLCARD (Role Cardinality)
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
⤷ BC-SRV-GBT-OBL (Application Component) General Object Relations
⤷ SOBL (Package) Generic Relation Service for Business Objects
Basic Data
Data Element | OBLROLCARD |
Short Description | Role Cardinality |
Data Type
Category of Dictionary Type | D | Domain |
Type of Object Referenced | No Information | |
Domain / Name of Reference Type | OBLROCARD | |
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 | Role Card. |
Medium | 18 | Role Cardinality |
Long | 20 | Role Cardinality |
Heading | 18 | Role Cardinality |
Documentation
Definition
Specifies how many object instances in in this role can be related to object instances in the related role.
Use
Dependencies
The cardinality when creating relationships is not checked as standard. If they are to be checked, you have to set the the IP_CHECK_CARDINALITY parameter when calling the CREATE_LINK method.
Example
A transit flight can have any number of connecting flights. The other way around, a connecting flight of the connection can be for any number of transit flights. The cardinalities were therefore M:N for the relationship type flight connections.
Any number of replies can be written to an e-mail. The other way around, however, a reply only refers to one e-mail. For relationship type replies, the cardinality is therefore 1:N.
History
Last changed by/on | SAP | 20010220 |
SAP Release Created in | 50A |