Business Partner Type (CDQ.POOL)

From CDQ
Business partner/type
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 Type
Description Informal and comprehensive human-readable definition of a concept. A distinct type a business partner is assigned to. It determines the business context a business partner is involved in. In the Corporate Data League, most business partners are legal entities.
Example A simple example supporting the understanding of a concept, business rule, etc. A business partner can possess the business partner type "legal entity" that indicates that the business partner is capable of holding rights.
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_TYPE
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. EXACTLY_ONE
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. types
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/> LEAF
Mapping

mapping source: IDENTIFICADOR MATRIZ (BR.RF), mapping: BR.RF IDENTIFICADOR_MATRIZBUSINESS_PARTNER_TYPE
mapping source: tipo (BR.SINRF), mapping: BR.SINRF tipoBUSINESS_PARTNER_TYPE
mapping source: legalForm (CH.UIDR), mapping: CH.UIDR legalFormBUSINESS_PARTNER_TYPE
mapping source: etablissementSiege (FR.RC), mapping: FR.RC etablissementValue_etablissementSiegeBUSINESS_PARTNER_TYPE
mapping source: form_kodas (LT.CR), mapping: LT.CR form_kodasBUSINESS_PARTNER_TYPE
mapping source: Data source/NO.RBE/data model/record/organisasjonsform/kode, mapping: NO.RBE organisasjonsform_kodeBUSINESS_PARTNER_TYPE
mapping source: Data source/PL.NOBR/data model/businessEntity/typ, mapping: PL.NOBR BUSINESS_PARTNER_TYPE
mapping source: 組織別名稱 (TW.CR), mapping: TW.CR legalFormBUSINESS_PARTNER_TYPE


Values