Business Partner Relationship (CDQ.POOL)
|Name Name of a concept, e.g. a data model concept. In contrast to terms, the name does not depend on a given context, e.g. a country-specific language.||Business Partner Relationship|
|Description Informal and comprehensive human-readable definition of a concept.||Also known as business partner hierarchy, or any other kind of relation between two business partner entities.
The relationship is separated from the Business Partner concept. The data about relationship between companies come from official, external data sources.
Relationships based on the three foundational attributes:
Additionally, there are also start and end dates of the relationship, which provided information about when the relationship was established and when it was ended.
|Part of Hierarchical relation between two concepts of the CDQ Data Model.||Data source CDQ.POOL|
|Technical key Defines a unique key by which e.g. data model concepts can be referenced in a technical integration context. These keys are unique in the CDL context.|
|Parent concept Hierarchical relation between two concepts of a data model, e.g., the CDQ Data Model.||Business Partner (CDQ.POOL)|
|Cardinality Cardinality of data model concepts.<br/><code>ZERO_OR_ONE</code>: Optional, but max. 1 instance related to its parent.<br/><code>EXACTLY_ONE</code>: Exactly 1 instance related to its parent.<br/><code>ZERO_OR_MORE</code>: Optional, multiple instances related to its parent may exist.<br/><code>ONE_OR_MORE</code>: Mandatory, multiple instances related to its parent may exist.|
|Data type Data type of a data model concept, i.e., <code>ARRAY</code>, <code>BOOLEAN</code>, <code>DATE</code>, <code>ENUM</code>, <code>INTEGER</code>, <code>OBJECT</code>, or <code>STRING</code>.||n/a|
|Path JSON Path to identify attributes in a data item.|
|Concept role The role of a Category:Data model concept in the tree structure of a data model.<br/><code>ROOT</code>: Root concept in a data model, i.e., no parent concepts.<br/><code>NODE</code>: Structure concepts in a data model, i.e., parent and child concepts.<br/><code>LEAF</code>: Leaf concept in a data model, i.e., no child concepts, provides the effective data values.<br/>|
|Mapping||not mapped to anything|
Data quality rules