Difference between revisions of "Data source/US-SF.BER/data model/entity/Location Id"
Jump to navigation
Jump to search
(Spreadsheet import) |
(Template parameters updated.) |
||
| Line 1: | Line 1: | ||
{{Data model concept | {{Data model concept | ||
| − | |name=Location Id | + | | name = Location Id |
| − | |description=Location Identification Number. Each DBA has a unique LIN for location specific tax filings | + | | description = Location Identification Number. Each DBA has a unique LIN for location specific tax filings |
| − | |example=0419041-02-001 | + | | example = 0419041-02-001 |
| − | |data source=Data source/US-SF.BER | + | | data source = Data source/US-SF.BER |
| − | |technical key=Location_Id | + | | technical key = Location_Id |
| − | |parent concept=Data source/US-SF.BER/data model/entity | + | | parent concept = Data source/US-SF.BER/data model/entity |
| − | |cardinality=ZERO_OR_ONE | + | | cardinality = ZERO_OR_ONE |
| − | |data type=STRING | + | | data type = STRING |
| − | |path=['Location Id'] | + | | path = ['Location Id'] |
| − | |concept role=LEAF | + | | concept role = LEAF |
}} | }} | ||
Latest revision as of 08:47, 23 April 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. | Location Id |
|---|---|
| Description Informal and comprehensive human-readable definition of a concept. | Location Identification Number. Each DBA has a unique LIN for location specific tax filings |
| Example A simple example supporting the understanding of a concept, business rule, etc. | 0419041-02-001 |
| Part of Hierarchical relation between two concepts of the CDQ Data Model. | Data source US-SF.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. | Location_Id
|
| Parent concept Hierarchical relation between two concepts of a data model, e.g., the CDQ Data Model. | entity (US-SF.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
|
| Path JSON Path to identify attributes in a data item. | ['Location Id']
|
| 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: CDQ Business Partner External ID (CDQ.POOL), mapping: US-SF.BER Location_Id ↣ CDQ_BUSINESS_PARTNER_EXTERNAL_IDmapping target: IdentifierValue (CDQ.POOL), mapping: US-SF.BER Location_Id ↣ IDENTIFIER_VALUE
|