Difference between revisions of "Data source/US-FL.BER/data model/corporation/corporationStatus"

From CDQ
Data source/US-FL.BER/data model/corporation/corporationStatus
Jump to navigation Jump to search
(Spreadsheet import)
(Template parameters updated.)
 
Line 1: Line 1:
 
{{Data model concept
 
{{Data model concept
|name=COR_STATUS
+
| name = COR_STATUS
|description=The status of filing: active, inactive "A" (active), "I" (inactive).
+
| description = The status of filing: active, inactive "A" (active), "I" (inactive).
|example=A
+
| example = A
|data source=Data source/US-FL.BER
+
| data source = Data source/US-FL.BER
|technical key=corporationStatus
+
| technical key = corporationStatus
|parent concept=Data source/US-FL.BER/data model/corporation
+
| parent concept = Data source/US-FL.BER/data model/corporation
|cardinality=ZERO_OR_ONE
+
| cardinality = ZERO_OR_ONE
|data type=STRING
+
| data type = STRING
|path=corporationStatus
+
| path = COR_STATUS
|concept role=LEAF
+
| concept role = LEAF
 
}}
 
}}

Latest revision as of 12:14, 31 May 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. COR_STATUS
Description Informal and comprehensive human-readable definition of a concept. The status of filing: active, inactive "A" (active), "I" (inactive).
Example A simple example supporting the understanding of a concept, business rule, etc. A
Part of Hierarchical relation between two concepts of the CDQ Data Model. Data source US-FL.BER
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. corporationStatus
Parent concept Hierarchical relation between two concepts of a data model, e.g., the CDQ Data Model. corporation (US-FL.BER)
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. COR_STATUS
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: US-FL.BER corporationStatusBUSINESS_PARTNER_STATUS_TYPE


Values