Difference between revisions of "Business partner/legal form"
Line 6: | Line 6: | ||
|parent concept=Business partner | |parent concept=Business partner | ||
|cardinality=ZERO_OR_ONE | |cardinality=ZERO_OR_ONE | ||
− | |path= | + | |path=legalForm |
|concept role=NODE | |concept role=NODE | ||
}} | }} |
Latest revision as of 21:42, 26 June 2023
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 |
---|---|
Description Informal and comprehensive human-readable definition of a concept. | The legal form of a business partner/type/legal entity is the form it takes in the eyes of the law governing it. The legal form of a company is the general type it may legally use to identify itself according to the local, regional, national, or international law governing it. This is normally reflected in the ending abbreviation after the company's name (e.g. AG, Inc., LLC, S.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
|
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_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
|
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: tipo_societario (AR.NRC), mapping: AR.NRC |
Sub concepts
Values