Legal Form Name (CDQ.POOL)
| 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 Name |
|---|---|
| Description Informal and comprehensive human-readable definition of a concept. | n/a |
| 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_NAME
|
| 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. | 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 |
| Path JSON Path to identify attributes in a data item. | legalForm.name
|
| 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 target: Legal Form (), mapping: CDQ.POOL LEGAL_FORM_NAME ↣ mapping target: BP_LEGALFORM (SAP), mapping: CDQ.POOL LEGAL_FORM_NAME ↣ BP_LEGALFORM
mapping source: JuridicalForm (BE.CCD), mapping: BE.CCD |