• Master data is considered to be that set of data that describes the specifications and structure of each item and party involved in the supply chain processes. The uniqueness of the data associated with a trade item is given only by the GTIN or an alternate item identification. This data is static, not dependent on a transaction.
• Transactional data is that set of data that can only be determined during a business transaction, i.e., plan, sell, buy, and deliver cycle. (E.g. actual amount of cases delivered).

• Master Data Alignment is the process of timely distribution of accurate Master Data from one partner to others and the correct use of this data. Such synchronization and use of Master Data leads to more accurate business transactions and therefore reinforces the efficiency of the supply chain operations.
• Successful Master Data Alignment is achieved via the use of EAN.UCC coding specifications throughout the supply chain, communication of all changes and new information between trading partners and use of the information exchanged in subsequent transactions.
• Master Data Alignment relies on EAN.UCC specifications concerning the Unique Identification of Items, GTIN or alternate item identification and Parties GLN or alternate party identification type as shown in the Party BRD, section 3.2

• An extension is an attribute that is relevant to one or more industries (not all EAN.UCC Industries)
• The definition of an extension attribute is common to all Industries who use the attribute
• Each Industry is responsible for determining the extension attributes that are relevant to their Industry
• New extension attributes may be submitted/requested for a specific Industry as necessary
• The conditions of extension attributes can vary by each industry.  E.g. Mandatory/Optional, Global/Local, Trading Partner Neutral/Relationship Dependent, and Common to all Hierarchy levels
• Industry user groups should be developed in concert with the EAN.UCC GSMP Process, to determine their relevant extension attributes and the conditions associated with those attributes
• Process user groups such as CPFR and local (target market) extensions

• The condition Trading Partner Neutral is applied to any attribute whose value is independent of a buyer and seller relationship. An attribute, which has the condition Trading Partner Neutral, can have only one set of values.
• The condition Trading Partner Dependent is applied to any attribute whose value is dependent on a buyer and seller relationship. An attribute, which has the condition Trading Partner Dependent, can have only one set of values per GLN of Party Receiving Data. These are attributes whose value is dependent on a specific point-to-point agreement between a buyer and a seller.
• An attribute which has the condition Trading Partner Neutral & Trading Partner Dependent, can have only one set of values for the Trading Partner Neutral value AND one set of values per GLN of Party Receiving Data

• The purpose of the target market country code is to organize master data to meet the requirements of specific geographies
• The purpose of this field is to explain where a manufacturer is intending to sell its product(s) to a buyer. It does not control where the buyer can resell the product (s) to the end consumer.
• It is the country, (the geopolitical area) where the product is to be sold and available for publication in an Item Catalog.
• Target Market Country Code in relationship to Master Data, can be Trading Partner Neutral only. A Target Market Country Code is not used to control Distribution or Consumer Market Area geographies. E.g. product available for shipment from a single Distribution Center

• A sub-country code level used to address/comply with a “law making” requirement associated with a country.
• The number of sub-country codes will vary by each country. These will match with the legislation requirements of each country. (Local bottle deposit tax laws, State and country taxes)
• Not all countries will have sub-country codes.
• A sub-country code must be associated with a Target Market Country Code.  It cannot stand-alone

• All attributes are impacted by their geo-political relevance. This condition can be used by information providers as they build data models. With this information, they can limit the attributes communicated to those relevant for that geography.
• A global attribute indicates that the attribute is relevant for business cases around the world, and can only have a single value throughout the world. (E.g. GTIN)
• A global/local attribute indicates that the field is relevant for business cases around the world, that its definition is the same around the world, but may have a different value depending on the geography. (E.g. VAT tax values, 1.00 in France, 1.05 in Belgium)
• A local attribute is only relevant in certain geographical areas, and the values may change based on where the product is offered for sale. (E.g. green dot – only relevant in certain European countries)

• An attribute, which has the condition ‘Global’, can have only one global value (except where there are multiple values allowed).
• An attribute which has the condition Global / Local can have one value per Target Market specified (except where there are multiple values allowed). A Global/Local attribute indicates that the field is relevant for business cases around the world, that its definition is the same around the world, but may have a different value depending on the geography. (E.g. the attribute - VAT tax values are relevant globally, but the actual value, 1.00 in France, 1.05 in Belgium varies by country)
• As long as the attribute values apply consistently to the GTIN, GLN, TM combination the values are repeatable

Example

GTINa + GLNa + TMa + b, = Ohio, Indiana.  Start availability date = January 1, 2003 
Target Market can be repeated where the values for the attribute are the same e.g. start availability date is the same for the GTIN + GLN + TM combination data set.
 
GTINa + GLNa + TMc = Kentucky.  Start availability date = January 15, 2003
 
Note: If GTIN and GLN are not used, alternate item identification and alternate party identification should be used.

• An attribute, which has the condition Local, can have only one value for the Target Market that is valid for (except where there are multiple values allowed).