Difference between revisions of "Business partner/legal form/technical key"
Business partner/legal form/technical key
Jump to navigation
Jump to search
Line 1: | Line 1: | ||
− | {{Data model concept | + | {{Data model concept |
|name=Legal Form Technical Key | |name=Legal Form Technical Key | ||
|description=The unique key (Entity Legal Form Code) of a [[Business partner/legal form]] in the [[Product feature/Legal Form Metadata|CDQ legal form metadata]] | |description=The unique key (Entity Legal Form Code) of a [[Business partner/legal form]] in the [[Product feature/Legal Form Metadata|CDQ legal form metadata]] | ||
− | |data | + | |data source=Data source/CDQ |
|technical key=LEGAL_FORM_TECHNICAL_KEY | |technical key=LEGAL_FORM_TECHNICAL_KEY | ||
|parent concept=Business partner/legal form | |parent concept=Business partner/legal form |
Revision as of 19:26, 22 February 2021
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. | Legal Form Technical Key |
---|---|
Description Informal and comprehensive human-readable definition of a concept. | The unique key (Entity Legal Form Code) of a Legal Form (CDQ.POOL) in the CDQ legal form metadata |
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. | LEGAL_FORM_TECHNICAL_KEY
|
Parent concept Hierarchical relation between two concepts of a data model, e.g., the CDQ Data Model. | Legal Form (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 |
Path JSON Path to identify attributes in a data item. | businessPartner.legalForm.technicalKey
|
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/> | missing |
Mapping |