Business Partner Classification Value (CDQ.POOL)

From CDQ
Business partner/partner profile/classification/value
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 Classification Value
Description Informal and comprehensive human-readable definition of a concept. A textual description of the classification
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_CLASSIFICATION_VALUE
Parent concept Hierarchical relation between two concepts of a data model, e.g., the CDQ Data Model. Business Partner Classification (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_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. businessPartner.profile.classifications[0].value
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: nomenclatureActivitePrincipaleEtablissement (FR.RC), mapping: FR.RC etablissementValue_nomenclatureActivitePrincipaleEtablissementBUSINESS_PARTNER_CLASSIFICATION_VALUE
mapping source: sbiCodeDescription (NL.BR), mapping: NL.BR sbiCodeDescriptionBUSINESS_PARTNER_CLASSIFICATION_VALUE
mapping source: classificationDescription (NZ.CR), mapping: NZ.CR entity_industryClassifications_classificationDescriptionBUSINESS_PARTNER_CLASSIFICATION_VALUE
mapping source: sourceRegister (NZ.CR), mapping: NZ.CR entity_sourceRegisterBUSINESS_PARTNER_CLASSIFICATION_VALUE
mapping source: primary_ssic_description (SG.BR), mapping: SG.BR primary_ssic_descriptionBUSINESS_PARTNER_CLASSIFICATION_VALUE
mapping source: secondary_ssic_description (SG.BR), mapping: SG.BR secondary_ssic_descriptionBUSINESS_PARTNER_CLASSIFICATION_VALUE
mapping source: PRIMARY NAICS DESCRIPTION (US-LA.BER), mapping: US-LA.BER PRIMARY_NAICS_DESCRIPTIONBUSINESS_PARTNER_CLASSIFICATION_VALUE
mapping source: LIC Code Description (US-SF.BER), mapping: US-SF.BER LIC_Code_DescriptionBUSINESS_PARTNER_CLASSIFICATION_VALUE
mapping source: NAICS Code Description (US-SF.BER), mapping: US-SF.BER NAICS_Code_DescriptionBUSINESS_PARTNER_CLASSIFICATION_VALUE
mapping source: PURPOSE (US-WY.BER), mapping: US-WY.BER PURPOSEBUSINESS_PARTNER_CLASSIFICATION_VALUE
mapping source: NAICS_DESC (US.EDU), mapping: US.EDU NAICS_DESCBUSINESS_PARTNER_CLASSIFICATION_VALUE

Data quality rules