Multipack¶
The multipack schema contains information regarding the multipacks that are used to create loads. These are created from a number of either identical or different complete packages from the complete packaging schema.
Note: The multipack portion is optional (only applies to multipacks). If the complete packaging or component is not in a multipack, all of the fields below are optional.
Table¶
Column | Status |
Format | Notes |
---|---|---|---|
identifier | required |
String | A globally unique identifier. See identifiers section for information on how to construct this identifier |
name | recommended |
String | The name of this multipack. |
description | recommended |
String | A brief description of this multipack. |
externalIdentifiers | recommended |
Dictionary | A dictionary of identifiers that might be used to identify the multipack in other systems. For example: manufacturer’s own internal identifier, bar codes or global trade item number (gtin). To provide external identifiers please follow this format. {'externalIdentifierName1': 'identifier1', 'externalIdentifierName2': 'identifier2'} |
multipackConstituentsIdentifiers | required |
List | The information regarding the consituents that are combined to create this multipack. The entries should be from the Multipack Constituents Relationship List identifier. |
tier | recommended |
Integer | The tier associated with the multipack. The inner most tier denoted as 1, and the outermost tier is the biggest number. |
identicalQuantity | required |
Numeric | Number of identical units for the unique complete packaging item or a component this row corresponds to. |
updateDate | required |
String | The date that the multipack was provided/last updated. Use the format dd/mm/yyyy . |
releaseDate | recommended |
String | The date that the component will be available to use. Use the format dd/mm/yyyy . |
discontinueDate | recommended |
String | The date that the component will no longer be available to use. Use the format dd/mm/yyyy . |
Diagram¶
erDiagram
COMPONENTS }o..o{ MULTIPACK : within
COMPONENTS }o..o{ COMPLETE_PACKAGING : within
COMPLETE_PACKAGING }o..o{ MULTIPACK : within
MULTIPACK {
identifier String
name String
description String
externalIdentifiers Dictionary
multipackConstituentsIdentifiers List
tier String
identicalQuantity Numeric
updateDate String
releaseDate String
discontinueDate String
}
MULTIPACK }o--o{ RELATIONSHIP_LISTS : attributes
COMPLETE_PACKAGING }o..o{ LOAD_CATALOGUE : within
MULTIPACK }o..o{ LOAD_CATALOGUE : within
COMPONENTS }o--o{ LOAD_CATALOGUE : within
RELATIONSHIP_LISTS {
multipackConstituentsIdentifier required
}
Template¶
Multipack should be provided as a separate csv file. The specification of this csv file is as follows:
Example¶
1 2 3 4 5 6 7 8 9 10 11 12 13 14 15 |
|