Professional Documents
Culture Documents
Product Hierarchy Common Values
Product Hierarchy Common Values
1.
1.1.
For an electrical product, it makes sense to provide maximumEnergyUsage at the Each level only. It does not need to be repeated for a Case. For any product, it makes sense to allow the Data Source to publish firstOrderDate at any level of the product hierarchy and the values might be different at each level. The published hierarchy might include an existing Each (already published in another hierarchy) contained in a new configuration of Case not made available before, where the Case has a different firstOrderDate from the Each.
1.2.
Pre-Requisites
The Data Source has analysed what data is to be published and has identified the attributes to be used. Its master data environment is capable of storing and making available for publication the relevant attributes at the appropriate levels of the product hierarchy. The Data Recipient has the capability to store different data at different levels of the product hierarchy. Its master data environment is capable of receiving, storing and using in its internal processes of the relevant attributes at the appropriate levels of the product hierarchy.
1.3.
which levels of the product hierarchy may typically be relevant for the attribute whether the data value for the attribute should be the same at all levels of the product hierarchy comments e.g. to explain why some levels are relevant
Dec-2010
Page 1 of 5
GDSN Trade Item Implementation Guide - Relevant Product Hierarchy Levels & Common Values
Note: The information is advisory. It is the responsibility and privilege of the Data Source to determine which data attributes will be published at which product hierarchy level. The XML Schema is capable of holding all attributes at all levels of the product hierarchy. Provided no formal GDSN Validation Rules (located on in the GS1 Knowledge Centre) are broken, the message should not be rejected on the basis of attributes being populated at a particular level.
1.4.
Dec-2010
Page 2 of 5
GDSN Trade Item Implementation Guide - Relevant Product Hierarchy Levels & Common Values
Column (5)
Description The common attribute value condition indicates whether the value for the attribute is advised to be the same value in all levels of a given hierarchy. This feature is optional to support for the data pools and trading partners but helps them to achieve consistent data handling in the hierarchy. Common Value Indicator = NO: Meaning: The attribute value is not common to all levels of the trade item hierarchy Example: grossWeight is not common to all levels of the trade item hierarchy, so the value can be different on the different hierarchy levels e.g. grossWeight of Each = 10 lbs / 4,5 kg grossWeight of Pallet = 100 lbs / 45 kg). Common Value Indicator = YES: Meaning: The attribute value is common to all levels of trade item hierarchy Example: shipFromLocationIdentification is common to all levels of the trade item hierarchy, so this value should be the same for each hierarchy level e.g. shipFromLocationIdentification = '1234567890128' for all levels published in the trade item hierarchy Note: The comment To allow for assortments has been added for some attributes which might normally be expected to have the same value at all levels. Some assortment items might require different values for each hierarchy level. For example: a manufacturer offers a Trade Item which is a Case of jam, with different flavours available at the Each level: - 4 x Strawberry - 4 x Raspberry - 4 x Blackcurrant If the manufacturer is using the Variant attribute to hold the flavour, the Each trade items will have the respective flavour in Variant, and the Case trade item may have a Variant of Mixed or Strawberry,Raspberry,Blackcurrant.
(6)
Comments
Additional information helpful for implementation. For example an additional comment may explain why the attribute might apply to more than one level of a trade item hierarchy, or to give examples.
1.5.
Implementation Considerations
Supporting the functionality:
This rule could be an additional validation for the GDSN data pools. Data pools MAY validate the master data of their data sources against this rule but CAN NOT enforce this validation on the data sources of other data pools (incoming CINs). Special rule for mixed hierarchies: the validation of common' condition CAN be ignored in case of parents with mixed children (and above that level) as they are implicitly not common at all levels of that hierarchy.
Dec-2010
Page 3 of 5
GDSN Trade Item Implementation Guide - Relevant Product Hierarchy Levels & Common Values
1.6.
Can the attribute be used in more than one hierarchy level? Will the supplier (manufacturer) provide the same value for every levels of the trade item hierarchy? Will a distributor or importer provide the same value for every levels of the trade item hierarchy (example different trade items from different suppliers in the same case)? If the answer is 'true' for every question above then the attribute can have its Common Value Indicator set to 'Yes'.
For each successive GDSN Release, the GS1 development team provides a list of suggested values for any new attributes in the release to the GDSN Trade Item Implementation Guide team who will review the suggested values, amend where necessary, and when satisfied the revised values will be submitted for Public Review. Once any comments arising from Public Review are resolved, a new issue of the advice will be published.
Dec-2010
Page 4 of 5
GDSN Trade Item Implementation Guide - Relevant Product Hierarchy Levels & Common Values
Dec-2010
Page 5 of 5