Difference between revisions of "Data source/SAP.ODM/data model/businesspartner/organization/globalLocationNumber"
Data source/SAP.ODM/data model/businesspartner/organization/globalLocationNumber
Jump to navigation
Jump to search
(Spreadsheet import) |
(Template parameters updated.) |
||
Line 1: | Line 1: | ||
{{Data model concept | {{Data model concept | ||
− | |name=GlobalLocationNumber | + | | name = GlobalLocationNumber |
− | |description=The Global Location Number (GLN) - former Internal Location Number (ILN) - assigned by GS1 organizations identifies physical locations or legal entities uniquely. It consists of 13 digits, the last digit being the check digit. There are two categories of location numbers: Participants who only need an GLN to clearly and unmistakably identify themselves for communication with the business partner are given a category 1 GLN. This cannot be used to identify articles by means of EAN. Participants who wish to assign the location numbers for their own enterprise areas are given a category 2 GLN. For a category 2 GLN, digits 1-7, 1-8 or 1-9 are described as basis number. This is used as basis for the creation of article numbers (EAN). | + | | description = The Global Location Number (GLN) - former Internal Location Number (ILN) - assigned by GS1 organizations identifies physical locations or legal entities uniquely. It consists of 13 digits, the last digit being the check digit. There are two categories of location numbers: Participants who only need an GLN to clearly and unmistakably identify themselves for communication with the business partner are given a category 1 GLN. This cannot be used to identify articles by means of EAN. Participants who wish to assign the location numbers for their own enterprise areas are given a category 2 GLN. For a category 2 GLN, digits 1-7, 1-8 or 1-9 are described as basis number. This is used as basis for the creation of article numbers (EAN). |
− | |data source=Data source/SAP.ODM | + | | data source = Data source/SAP.ODM |
− | |technical key=globalLocationNumber | + | | technical key = globalLocationNumber |
− | |parent concept=Data source/SAP.ODM/data model/businesspartner/organization | + | | parent concept = Data source/SAP.ODM/data model/businesspartner/organization |
− | |cardinality=ZERO_OR_ONE | + | | cardinality = ZERO_OR_ONE |
− | |data type=STRING | + | | data type = STRING |
− | |path=businesspartner.organization.globalLocationNumber | + | | path = businesspartner.organization.globalLocationNumber |
− | |concept role=LEAF | + | | concept role = LEAF |
}} | }} |
Revision as of 16:15, 20 April 2022
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. | GlobalLocationNumber |
---|---|
Description Informal and comprehensive human-readable definition of a concept. | The Global Location Number (GLN) - former Internal Location Number (ILN) - assigned by GS1 organizations identifies physical locations or legal entities uniquely. It consists of 13 digits, the last digit being the check digit. There are two categories of location numbers: Participants who only need an GLN to clearly and unmistakably identify themselves for communication with the business partner are given a category 1 GLN. This cannot be used to identify articles by means of EAN. Participants who wish to assign the location numbers for their own enterprise areas are given a category 2 GLN. For a category 2 GLN, digits 1-7, 1-8 or 1-9 are described as basis number. This is used as basis for the creation of article numbers (EAN). |
Part of Hierarchical relation between two concepts of the CDQ Data Model. | Data source SAP.ODM |
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. | globalLocationNumber
|
Parent concept Hierarchical relation between two concepts of a data model, e.g., the CDQ Data Model. | OrganizationDetails (SAP.ODM) |
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. | businesspartner.organization.globalLocationNumber
|
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: IdentifierValue (CDQ.POOL), mapping: SAP.ODM globalLocationNumber ↣ identifierValue
|