CR 08-226 - Round 4 of the SA2 change request (note: this represents the final list of proprietary attributes submitted by SA2)

Adds attributes to the GDSN core item data model, or appropriate GDSN item data extension. Contained in this change request are attributes for specific product types, regulatory requirements, hazardous substance requirements and other generic trade item characteristics. The interim deployment of these attributes using the Fast Track AVP data extension was also requested.

CR 08-230, 08-245 & 08-249 - Validation rules for GDSN Item data.

This is the first round of additional GDSN validations to be perfomred on item data. Work continues within a sub-team to review further validations associated with the 3 change requests submitted by Sweden, Australia and the Netherlands. These validation rules may vary in complexity as to GSMP work effort but their implementation will be complex to Data Pools, Retailer, Suppliers & Solution Providers with programming required or new mapping etc.

CR 08-291 - Review and update section 9.2. (Appendix in the Trade Item BMS

Updates the definition and usage of “Common to all Levels of Hierarchy” and to review the “Common to All Levels of Hierarchy” classification of each attribute in the Trade Item. This chart will no longer be part of the BMS but will be added to the Trade Item Implementation Guidelines. GDSN Architecture Group Reviewed CR 08-291 to confirm if attributes have common values across an item hierarchy or not.

CR 09-038 -  Add a list of attributes to the GDSN External File Class of attributes.

Adds a number of new attributes to the external file class providing further information relating to digital assets contained at the URLs loaded in the item message. These attributes will allow for necessary information in retailer systems to be provided from the asset's source.

CR 09-042 - add an attribute for Community Visibility Date

Introduces Community Visibility Date, defined as "From this date, the neutral trade item information (i.e. not the private information, no relationship-dependent data and no price data) is available to all members of the target data pool, without restriction.  Until this date only the data recipients to whom the data source has explicitly published the data can have access to the data.  By setting this date a data source gives permission for wider publication of the generic item data." The date is optional and not repeatable.  It is a date, rather than a date/time stamp.
Note: This is different from endDateTimeOfExclusivity which refers to the physical supply of the trade item through the supply chain.  This date refers to the availability / visibility of data about the trade item, not the trade item itself.
Validation rule: For Target Markets Australia (AU) and New Zealand (NZ), the date is mutually exclusive with the attribute "partyReceivingPrivateData".

CR 09-049 - Price Synchronization validations

Changes to two Price related validation rules and adds one new business rule :
A. Changed Rule 409: A targeted condition must have a prior confirmation status of accept, synchronize or review except when a segment is first synchronized (as an Add). In this case, it may also be targeted in the same file without the requirement of a prior confirmation status.   409 Error Message Description: The Target Condition must be in the accept, synchronize, or review status except when the Target Condition is first synchronized (as an Add).
B. New Business Rule for the Price Sync BMS : Any rejection of a targeted price type would result in the rejection of the targeting price type. 
C. Changed Rule 415: A targeted price type must have a prior confirmation status of accept, synchronize or review except when a segment is first synchronized (as an Add). In this case, it may also be targeted in the same file without the requirement of a prior confirmation status. 415 Error Message Description: The Target Price type must be in the accept, synchronize, or review status except when the Target Price Type is first synchronized (as an Add).

CR 09-057 - Add an attribute for Heat of Combustion

Adds a new attri bb ute for the Heat of combustion. Definition:  "The amount of Heat generated by the item should it catch on fire, expressed for example as BTU’s (British Thermal Units) per Pound".  This field is used for storage decisions in the warehouse.  There is a need to know if the combustion of 1 item in storage could trigger the combustion of another stored nearby. What’s important here is the ‘amount of heat’.  Heat of combustion is … once the item does explode, how hot is the actual explosion? Expected Benefit: To identify if the trade item is heat combustible and reflected in for example BTUs. This facilitates identification of  trade items that are flammable under certain temperatures, e.g. hairspray and aerosol insect repellent.

CR 09-091 - Enable users to indicate information about the containment of built-in batteries in products.

Adds additional attributes relative to batteries required for specific trade items. Information needed is type of battery, number of batteries contained and the weight of each battery. 
- Quantity of Batteries Required 
- Type of Battery
- Is Battery BuiltIn
- Battery Weight

Note: these attributes may be combined with existing attributes currently contained in the Electronic Games extension to form a more robust class of attributes, and subsequently moved to core item for use by more types of products.