Difference between revisions of "Address/function"
Address/function
Jump to navigation
Jump to search
(Spreadsheet import) |
(Spreadsheet import) |
||
| Line 1: | Line 1: | ||
| − | {{Data model concept | + | {{Data model concept |
|name=Address Function | |name=Address Function | ||
|description=Documents the way an address is used e.g. at different CDL member companies. For example, a [[business partner]]'s [[address]] may be a [[Address/function/ship to]] for one of its [[business partner]]s but a [[Address/function/bill to]] for another CDL member. There is no direct use of this information in the CDL but may be used in future for data analysis and data validation purposes. | |description=Documents the way an address is used e.g. at different CDL member companies. For example, a [[business partner]]'s [[address]] may be a [[Address/function/ship to]] for one of its [[business partner]]s but a [[Address/function/bill to]] for another CDL member. There is no direct use of this information in the CDL but may be used in future for data analysis and data validation purposes. | ||
| − | |data | + | |data source=Data source/CDQ |
|technical key=ADDRESS_FUNCTION | |technical key=ADDRESS_FUNCTION | ||
|parent concept=Address | |parent concept=Address | ||
|cardinality=ZERO_OR_MORE | |cardinality=ZERO_OR_MORE | ||
|path=address.function | |path=address.function | ||
| + | |concept role=LEAF | ||
}} | }} | ||
Revision as of 07:45, 30 November 2020
| 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. | Address Function |
|---|---|
| Description Informal and comprehensive human-readable definition of a concept. | Documents the way an address is used e.g. at different CDL member companies. For example, a business partner's address may be a Ship To Address (CDQ.POOL) for one of its business partners but a Bill To Address (CDQ.POOL) for another CDL member. There is no direct use of this information in the CDL but may be used in future for data analysis and data validation purposes. |
| 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. | ADDRESS_FUNCTION
|
| Parent concept Hierarchical relation between two concepts of a data model, e.g., the CDQ Data Model. | Address (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_MORE
|
| 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. | address.function
|
| 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 |
Values