Business Partner Status (CDQ.POOL)

From CDQ
Business partner/status
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 Status
Description Informal and comprehensive human-readable definition of a concept. Describes the status of a business partner with respect to its level of activity (e.g. out of business) or legally relevant conditions (e.g. in liquidation)
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_STATUS
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. ZERO_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.status
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

mapping source: סטטוס חברה (IL.CR), mapping: IL.CR companyStatusBUSINESS_PARTNER_STATUS
mapping source: entityStatusDescription (NZ.CR), mapping: NZ.CR entity_entityStatusDescriptionBUSINESS_PARTNER_STATUS
mapping source: entity_status_description (SG.BR), mapping: SG.BR entity_status_descriptionBUSINESS_PARTNER_STATUS
mapping source: entitytype (US-CO.BER), mapping: US-CO.BER entitytypeBUSINESS_PARTNER_STATUS
mapping source: STATUS (US-WY.BER), mapping: US-WY.BER STATUSBUSINESS_PARTNER_STATUS

Sub concepts

Data quality rules