Business Partner Relation (CDQ.POOL)

From CDQ
Business partner/relation
Jump to navigation Jump to search
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 Relation
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 relation is separated from the Business Partner concept. The data about relationships between companies come from official, external data sources.

Relations based on the four foundational attributes:

  • StartNode - parent company in the relationship
  • EndNode - child company in the relationship
  • Type - what kind of relation is between to Business Partners
  • Class - From which classification does the hierarchy come?

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.

Example A simple example supporting the understanding of a concept, business rule, etc. no example available
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. BUSINESS_PARTNER_RELATION
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. ONE_OR_MORE
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
Concept type Complex data type of a data model concept, defined by another data model concept. Allows re-use of data type concepts, e.g. for several address types in a data model. SELF
Path JSON Path to identify attributes in a data item. businessPartner.relations[0]
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/> NODE
Mapping

Sub concepts

Data quality rules