Difference between revisions of "Data source/IE.CR/data model/company/companyStatusCode"

From CDQ
Data source/IE.CR/data model/company/companyStatusCode
Jump to navigation Jump to search
(Spreadsheet import)
(Template parameters updated.)
 
Line 1: Line 1:
 
{{Data model concept
 
{{Data model concept
|name=company_status_code
+
| name = companyStatusCode
|description=The CRO's primary key value corresponding to the company_status_desc.
+
| description = The CRO's primary key value corresponding to the 'companyStatusDesc'. Examples:
|example=1158
+
|data source=Data source/IE.CR
+
* 1151 - Normal
|technical key=companyStatusCode
+
* 1158 - Dissolved
|parent concept=Data source/IE.CR/data model/company
+
| example = 1158
|cardinality=ZERO_OR_ONE
+
| data source = Data source/IE.CR
|data type=INTEGER
+
| technical key = companyStatusCode
|path=companyStatusCode
+
| parent concept = Data source/IE.CR/data model/company
|concept role=LEAF
+
| cardinality = ZERO_OR_ONE
 +
| data type = STRING
 +
| path = companyStatusCode
 +
| concept role = LEAF
 
}}
 
}}

Latest revision as of 09:03, 22 June 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. companyStatusCode
Description Informal and comprehensive human-readable definition of a concept. The CRO's primary key value corresponding to the 'companyStatusDesc'. Examples:
  • 1151 - Normal
  • 1158 - Dissolved
Example A simple example supporting the understanding of a concept, business rule, etc. 1158
Part of Hierarchical relation between two concepts of the CDQ Data Model. Data source IE.CR
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. companyStatusCode
Parent concept Hierarchical relation between two concepts of a data model, e.g., the CDQ Data Model. Data source/IE.CR/data model/company
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>. STRING
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. companyStatusCode
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: Business Partner Status Type (CDQ.POOL), mapping: IE.CR companyStatusCode, company_status_codeBUSINESS_PARTNER_STATUS_TYPE


Values