Guideline for suppliers to provide product data according to BMEcat Version 2005 Version 3.1 ETIM International Status 2015-11-13 This is the Guideline for suppliers to provide product data, created and coordinated on the level of ETIM International. Content 1. Providing product data 2. Supported transactions 3. Requirement for supplier catalogs a. File name b. General guidelines for catalog content 4. Specification of the BMEcat parts a. Instructions for header fields (HEADER) b. Transaction T_NEW_CATALOG c. Transaction T_UPDATE_PRODUCTS d. Transaction T_UPDATE_PRICES 5. Explanation a. Product description b. Keywords c. Classification and features d. Order e. Prices f. Pictures and other additional documents g. Deep linking h. Safety data sheet and ECCN-codes i. Examples of packing variants 6. Link compilation 7. ISO - International Organization for Standardization 8. Allowed order-, quantity- and packing units 9. Country specific regulations 10. Change log to previous versions Guideline for suppliers to provide product data / Version 3.1 Status: 2015-11-13 Page 2 Page 3 Page 5 Page 5 Page 5 Page 7 Page 7 Page 14 Page 35 Page 37 Page 38 Page 38 Page 40 Page 41 Page 44 Page 49 Page 51 Page 57 Page 58 Page 61 Page 75 Page 76 Page 77 Page 78 Page 87 - Page 1 of 88 - 1. Providing product data Due to the ever-increasing quantity of product data with constantly diminishing product lifecycles, the consideration and use of standards is an absolute necessity for providing and processing product information of high quality. With progressing globalization, there is a growing requirement from all the participants of the trade chain for quality of information. Especially the supplier will meet these requirements by using standards, because all product information concerning the product will be provided in a unique way and structured uniformly. This information will be used by all those participating in all levels of trade so that the exchange of information in both directions is always based on the same original data and can provide customers with high-quality product data via different media – in printed catalogs or brochures, on CD-ROMs, as well as in eProcurement solutions and online shops. To ensure that the standardized ETIM data is provided on a long term scale, members of ETIM International have created this guideline to provide electronic product data. For the integration of electronic product catalogs in the product master data the XML (Extensible Markup Language) based standard BMEcat ® Version 2005 is being used. Applied Standards: - BMEcat Version 2005 Website: http://www.bmecat.org ETIM Website: http://www.etim-international.com ETIM International E-Mail: [email protected] Guideline for suppliers to provide product data / Version 3.1 Status: 2015-11-13 - Page 2 of 88 - 2. Supported transactions Transactions determine which parts of a catalog will be transferred with the catalog document and how this data has to be processed in the target system. In BMEcat three transactions are at hand: • Transfer of a new catalog: T_NEW_CATALOG (which is supported by all data receivers). Normally a data supplier delivers an ETIM BMEcat with all products that are distributed by the data receiver. But if defined between the data supplier and the data receiver, it is also possible to deliver only a part of the respective product range, e.g. only the new products. All data of these (new) products has to be part of the BMEcat file, so it is also a T_NEW_CATALOG – only with a smaller number of products. Whether the following additional transactions are accepted must be defined between the data supplier and the data receiver: • Update of product data: T_UPDATE_PRODUCTS • Update of price data: T_UPDATE_PRICES The application of the update transactions permits the reduction of the volume of the documents to be transferred, since changes do not require the new transfer of the complete catalog. With the transaction T_UPDATE_PRODUCTS it is possible to inform the data receiver about new, changed and deleted products. The fields are identic to a new catalog, in the catalog there are only products which have been changed, the new ones and the deleted. Most important is that each update has to be transmitted from the data supplier and also has to be imported by the data receiver. If one update is missing the following catalog is invalid! In this case it is necessary to transmit a T_NEW_CATALOG. With the transaction T_UPDATE_PRICES it is possible to inform the data receiver about new prices. In this catalog there are only the fields for prices, but for all products which have been in the last transmitted catalog. In this file it is not possible to transmit any other changes. With this type it is also possible to transmit additional prices – for example “net_customer” price instead of transmitting this information by other means (e.g. by Excel file). Guideline for suppliers to provide product data / Version 3.1 Status: 2015-11-13 - Page 3 of 88 - The versioning is important: the first update-catalog has the text prev_version=”0”, the second one 1 and so on. This applies both for T_UPDATE_PRODUCTS and for T_UPDATE_PRICES. Important: Each data supplier (manufacturer) usually should inform the data receiver with each transfer of an ETIM BMEcat, why a new file is delivered (new prices, new pictures, new products ...). Guideline for suppliers to provide product data / Version 3.1 Status: 2015-11-13 - Page 4 of 88 - 3. Requirements for supplier catalogs a. File name The name of the BMEcat-XML-file must be as following: Short name of the supplier with generation date and file extension XML. Embodied spaces are to be replaced by underscoring. The date is to be specified in the format yyyy-mm-dd. The length of the file name should not exceed 40 characters. Especially for resellers it is necessary to add the name of the manufacturer or a trademark or “complete”; if there are updates it could be helpful to add “New” for a complete new catalog, “Update_Prices” or “Update_Products” at the end of the file name before the date. Example: Smith_Switches_New_2015-08-01.xml b. General guidelines for catalog content Criteria are listed as follows: Catalog data standard: BMEcat Version 2005 Classification standard: ETIM Language(s) of the catalog content: depending on the data receiver Currency: depending on the data receiver All fields of this Guideline should be filled when the necessary data is available (e.g.: product reference to follow up, accessory or other product) and only fields that are listed in this ETIM Guideline are allowed. Elements that are not part of this ETIM Guideline are not allowed in an ETIM BMEcat file! Separator in all numeric fields is a „.“ (dot). For example: 124.90 and not 124,90. To use thousands separators is not allowed (e.g. 1250.90 and not 1,250.90). Guidelines regarding text fields (e.g. on formatting, character set, spelling, etc.) will be detailed per country in the specific country sections of this Guideline. The content of update-catalogs is identic to a standard catalog, in price-update-catalogs only price information in transmitted – see marks in the following document. Header information is in all cases identic. Guideline for suppliers to provide product data / Version 3.1 Status: 2015-11-13 - Page 5 of 88 - A product update catalog includes only changed, new and deleted products. A price update catalog includes all products of the last catalog; no changes except the prices can be transmitted. If prices of some products are not changed it makes no difference. It is recommended to deliver URLs according to RFC1738, starting with http:// or https:// Important notice: In the specification BMEcat 2005 data fields are either “Mandatory” or “Optional”. In this ETIM Guideline, some optional fields of the original BMEcat specification BMEcat 2005 are mandatory. This will be marked as +Mandatory in this document (respectively +m in the corresponding Excel file <ETIM BMEcat Guideline V3-1 - Overview elements.xlsx>). Furthermore each optional element can be marked as mandatory on the level of an individual ETIM country. Guideline for suppliers to provide product data / Version 3.1 Status: 2015-11-13 - Page 6 of 88 - 4. Specification of the BMEcat parts a. Instructions for header fields (HEADER) In the catalog header (HEADER) the products themselves are not described, but information concerning the identification and the validity of the catalog, the catalog creator and receiver as well as the underlying framework agreement is transferred. Furthermore default values that are applicable for all contained products can be placed; e.g., language and currency. The catalog header is structured in the same way for all three transactions. HEADER (Mandatory, Single) Designation Generator information Element name GENERATOR_INFO Mandatory/ Optional Optional Single/ Multiple Explanation Data type Field length Lang. specific Single Information about the generator of the document, e.g. the used software or the name of a service provider. dtSTRING 250 - 3 - HEADER CATALOG (Mandatory, Single) Language LANGUAGE Mandatory Multiple Guideline for suppliers to provide product data / Version 3.1 Status: 2015-11-13 This element specifies the used languages (acc. ISO 639-2:1998), especially the default language of all language-dependent information. Single-lingual catalogs: contains the used language; if the default-attribute is set, then it is not necessary to name the language in all elements that contain languagedependent information; Multi-lingual catalogs: this element must be used to dtLANG - Page 7 of 88 - Designation Element name Mandatory/ Optional Single/ Multiple Default flag (attribute) default Optional Single Catalog ID CATALOG_ID Mandatory Single Catalog version CATALOG_VERSION Mandatory Single Catalog name CATALOG_NAME +Mandatory Single Guideline for suppliers to provide product data / Version 3.1 Status: 2015-11-13 Explanation specify each language that occurs in the document, therefore the element appears more than once. If the defaultattribute is set for the most frequently or always used language, then it is not necessary to name for all languagedependent information this language (default language); it is sufficient to mark information in other languages. This element determines the default language of all language-dependent information in the document. Unique catalog identification. This ID is usually assigned by the supplier when the catalog is generated and remains unchanged throughout the entire lifecycle of the catalog. Version number of the catalog. May only be reset on the target system in conjunction with a T_NEW_CATALOG transaction and not in the case of updates. Format: „MajorVersion“.“MinorVersion“, maximum however (xxx.yyy) (Example: 7.1 or 001.001) Any name that describes the catalog. Example: Fall/Winter Data type Field length Lang. specific dtBOOLEAN dtSTRING 20 - dtSTRING 7 - dtMLSTRING 100 - Page 8 of 88 - Yes Designation Mandatory/ Optional Element name Single/ Multiple Datetime DATETIME type=“generation_date” +Mandatory Single Territory TERRITORY Optional Multiple Currency CURRENCY Optional Single MIME root directory MIME_ROOT Optional Single Explanation 2005/2006 Time stamp, when the catalog document is generated. Used value: <Date> yyyy-mm-dd Example: 2015-07-01 Territory (i.e. country, state, region) coded according to ISO 3166. acc. ISO 4217:2001; Provides the currency that is default for all price information in the catalog. If the price of a product has a different currency, or this element is not used, the currency has to be specified in the PRICE_CURRENCY element for the respective product. Therefore, the currency must be specified in the catalog header or for each product separately. It is recommended to define a default currency. A relative directory can be entered here (and/or a URL), i.e. one to which the relative paths in MIME_SOURCE refer. Data type Field length dtDATETIME Lang. specific 10 - dtCOUNTRIES 6 - dtCURRENCIES 3 - dtMLSTRING 250 Yes dtSTRING 250 - HEADER BUYER (+Mandatory, Single) ID of the buying company BUYER_ID type=”buyer_specific” Optional Single Guideline for suppliers to provide product data / Version 3.1 Status: 2015-11-13 Unique number of the buying company - Page 9 of 88 - Designation Element name Mandatory/ Optional Single/ Multiple Explanation Data type Field length Lang. specific Name of the buyer BUYER_NAME Mandatory Single Name of the buying company or organization dtSTRING 50 - dtSTRING 250 - dtSTRING 250 - dtSTRING 50 - dtSTRING 20 - dtMLSTRING 50 Yes dtMLSTRING 50 Yes dtMLSTRING dtMLSTRING dtMLSTRING 20 50 50 Yes Yes Yes dtSTRING 50 - HEADER SUPPLIER (Mandatory, Single) Supplier ID SUPPLIER_ID type=“duns“ Optional Single Supplier ID SUPPLIER_ID type=“iln“ Optional Single Supplier name SUPPLIER_NAME Mandatory Single The D-U-N-S® number (Data Universal Numbering System http://www.dnb.com) is a 9digit numeric code to indicate companies all over the world clearly. It was developed and introduced by Dun & Bradstreet in 1962. The number has to be delivered without formatting. ILN (International-LocationNumber) of the supplier (respectively new designation is Global-Location-Number GLN) Name of the supplier HEADER SUPPLIER ADDRESS (Optional, Single) Address type ADDRESS type =”supplier” +Mandatory Single Contact name CONTACT Optional Single Street STREET Optional Single Zip code Town or city Country ZIP CITY COUNTRY Optional Optional Optional Single Single Single VAT-ID VAT_ID Optional Single Guideline for suppliers to provide product data / Version 3.1 Status: 2015-11-13 Contains the address type Contains the name of the contact person Street name and house number ZIP code of address Town or city of the company Country, e.g. France Value Added Tax Identification Number of the business partner - Page 10 of 88 - Designation Element name Mandatory/ Optional Single/ Multiple E-mail address EMAIL Mandatory Single Internet address URL Optional Single Explanation Data type Field length Lang. specific e-mail address URL of the web site, e.g., http://www.bmecat.org dtSTRING 255 - dtSTRING 255 - HEADER SUPPLIER MIME_INFO (Optional, Single) HEADER SUPPLIER MIME_INFO MIME (Mandatory, Multiple) Supplementary multimedia file with the logo of the supplier; MIME_TYPE MIME type +Mandatory MIME_SOURCE Source Mandatory MIME_DESCR Designation Optional MIME_ALT Alternative text Optional MIME_PURPOSE Purpose +Mandatory the sub element MIME_PURPOSE should contain the value “logo”. Single Same explanation as in the Subtree PRODUCT MIME_INFO Single Same explanation as in the Subtree PRODUCT MIME_INFO Single Same explanation as in the Subtree PRODUCT MIME_INFO Single Same explanation as in the Subtree PRODUCT MIME_INFO Single Same explanation as in the Subtree PRODUCT MIME_INFO HEADER USER_DEFINED_EXTENSIONS (Mandatory, Single) User-defined extensions version UDX.EDXF.VERSION +Mandatory Single Guideline for suppliers to provide product data / Version 3.1 Status: 2015-11-13 Version of the applied ETIM International BMEcat Guideline; EDXF = ETIM Data Exchange Format Field should be filled with “3.1” for this current version of the Guideline dtSTRING 20 - Page 11 of 88 - - Example for the Header <BMECAT version="2005"> <HEADER> <GENERATOR_INFO>Classification Software Master 1a</GENERATOR_INFO> <CATALOG> <LANGUAGE>dut</LANGUAGE> <CATALOG_ID>sample-7045839</CATALOG_ID> <CATALOG_VERSION>001.001</CATALOG_VERSION> <CATALOG_NAME>sample company-7045839</CATALOG_NAME> <DATETIME type="generation_date"> <DATE>2015-01-02</DATE> </DATETIME> <TERRITORY>NL</TERRITORY> <CURRENCY>EUR</CURRENCY> </CATALOG> <BUYER> <BUYER_ID type=”buyer_specific”>sample buyer</BUYER_ID> <BUYER_NAME>Sample buyer name</BUYER_NAME> </BUYER> <SUPPLIER> <SUPPLIER_ID type="duns">316011725</SUPPLIER_ID> <SUPPLIER_ID type=“iln“>4012345000001</SUPPLIER_ID> <SUPPLIER_NAME>Sample company ltd.</SUPPLIER_NAME> <ADDRESS type="supplier"> <NAME>Sample company ltd.</NAME> <STREET>Sample road</STREET> <CITY>Sample city</CITY> <COUNTRY>NL</COUNTRY> <EMAIL>[email protected]</EMAIL> <URL>http://www.sample-company.nl</URL> </ADDRESS> <MIME_INFO> <MIME> <MIME_TYPE>image/jpeg</MIME_TYPE> <MIME_SOURCE>sample company_logo.jpg</MIME_SOURCE> <MIME_DESCR>MD18</MIME_DESCR> <MIME_PURPOSE>logo</MIME_PURPOSE> Guideline for suppliers to provide product data / Version 3.1 Status: 2015-11-13 - Page 12 of 88 - </MIME> </MIME_INFO> </SUPPLIER> <USER_DEFINED_EXTENSIONS> <UDX.EDXF.VERSION>3.1</UDX.EDXF.VERSION> </USER_DEFINED_EXTENSIONS> </HEADER> Guideline for suppliers to provide product data / Version 3.1 Status: 2015-11-13 - Page 13 of 88 - b. Transaction T_NEW_CATALOG T_NEW_CATALOG (Mandatory, Single) Designation Element name Mandatory/ Optional Single/ Multiple Explanation Data type Field length Product PRODUCT in context T_NEW_CATALOG - mode +Mandatory Multiple PRODUCT mode=new; if none exists „new“ is assumed dtSTRING 20 Lang. specific - T_NEW_CATALOG PRODUCT (Mandatory, Multiple) The element PRODUCT contains the unique product number of the supplier and further sub elements for description, price, packing and multimedia supplementary information. Supplier's product ID SUPPLIER_PID Mandatory Single Contains the product number issued by the supplier. It is determining for ordering the product; it identifies the product in the supplier catalog. dtSTRING 32 - T_NEW_CATALOG PRODUCT PRODUCT_DETAILS (Mandatory, Single) Short description Long description International product number Alternative product number Product ID of the buying company Product ID of the manufacturer Short, concise product description (capitalization rules, see explanation 5a) Extensive and detailed product description (see explanation 5a) dtMLSTRING dtMLSTRING Multiple Indicates the “Global Trade Item Number” GTIN dtSTRING 100 - Optional Single Additional (internal) product identifier of the supplier if different to the SUPPLIER_PID dtSTRING 50 - BUYER_PID type=“buyer_specific” Optional Multiple Product number used by the buying company dtSTRING 50 - MANUFACTURER_PID Optional Single Product ID of the manufacturer dtSTRING 50 - DESCRIPTION_SHORT Mandatory Single DESCRIPTION_LONG Optional Single INTERNATIONAL_PID type=“GTIN” Optional SUPPLIER_ALT_PID Guideline for suppliers to provide product data / Version 3.1 Status: 2015-11-13 150 Yes 64000 Yes - Page 14 of 88 - Lang. specific Element name Mandatory/ Optional Single/ Multiple Explanation Data type Field length MANUFACTURER_NAME Optional Single Name of the manufacturer of the product dtSTRING 50 - MANUFACTURER_TYPE_DESC R Optional Single dtMLSTRING 50 Yes Special treatment class SPECIAL_TREATMENT_CLASS type=… Optional Multiple dtSTRING 20 - Keyword KEYWORD Optional Multiple 50 Yes Remark REMARKS type=”general” Optional Multiple 64000 Yes Special product status PRODUCT_STATUS type=… Optional Multiple 250 Yes Designation Name of manufacturer Manufacturer type description Guideline for suppliers to provide product data / Version 3.1 Status: 2015-11-13 A name for the product which may, in certain circumstances be more widelyknown than the correct product name. Supplementary classification of a product for dangerous goods, hazardous substances, drugs precursors, radioactive measurement devices etc. Labelling, if the product requires a safety data sheet or not. As well the code for ECCN is transmitted; the attribute “type” sets the special treatment regulation; the value sets the class within the order. Example: (Hazardous Goods Ordinance Road, heating oil) <SPECIAL_TREATMENT_CLASS type="GGVS">1201 </SPECIAL_TREATMENT_CLASS> (see explanation 5h) Keyword that makes it easier to find the product (see explanation 5b) Supplementary remarks of the supplier (e.g. “vertically stackable up to 8 units”) This element classifies a product in terms of its special characteristics. The status type is specified by the ‘type’ attribute. The value of the element reflects the text description of the special characteristics. If a product cannot be mapped to any of the predefined status types (listed below), „others“ must be used. This field is in connection with the field product expiration date (UDX.EDXF.EXPIRATION_DATE). dtMLSTRING dtMLSTRING dtMLSTRING - Page 15 of 88 - Designation Element name Bargain Core assortment Mandatory/ Optional Single/ Multiple type=“bargai n“ type=“core_p roduct” New type=“new“ New product type=“new_p roduct“ Old product type=“old_pr oduct“ Refurbished type=“refurbi shed“ Used type=“used“ Guideline for suppliers to provide product data / Version 3.1 Status: 2015-11-13 Explanation Data type Field length If a product is a discontinued line with expiration date, the value „others“ will be set for the element PRODUCT_STATUS. For the element UDX.EDXF.EXPIRATION_DATE the expiration date has to be indicated additionally. Among others, allowed combinations for ETIM are: <PRODUCT_STATUS type="others">discontinued</PRODUCT_ STATUS> <PRODUCT_STATUS type=" core_product">core_assortment</ PRODUCT_STATUS> (e.g. household appliances) A bargain is a product offered at a special low price for a limited period of time. A product which belongs to the core assortment for a particular customer. A new product is a product which has only just been manufactured (i.e. has not been used). The product has recently been added to the catalog. An old product is a product which can no longer be purchased but which is still displayed in the catalog, for example in order to refer to the follow-up product. A refurbished product is a used product that has been specially processed in order to restore it to a condition close to its original condition. A used product is a product which has already been in use. - Page 16 of 88 - Lang. specific Designation Element name Mandatory/ Optional Other status type=“others“ Single/ Multiple Explanation Data type Field length Lang. specific This status can be used if none of the predefined statuses adequately describe the product. T_NEW_CATALOG PRODUCT PRODUCT_FEATURES (+Mandatory, Multiple) The element PRODUCT_FEATURES contains elements for the classification of products. Classification system REFERENCE_FEATURE_SYST EM_NAME +Mandatory Single Group reference REFERENCE_FEATURE_GROU P_ID +Mandatory Single The indication is mandatory in case of ETIM; notation like “ETIM-6.0” Identification code of the ETIM class e.g. „EC001234“; if there is really no existing class in the used ETIM classification version, EC000000 is allowed exceptionally. But EC000000 is not part of the ETIM classification model! dtSTRING 80 - dtMLSTRING 60 Yes dtMLSTRING 60 Yes dtMLSTRING 60 Yes dtSTRING 20 - T_NEW_CATALOG PRODUCT PRODUCT_FEATURES FEATURE (+Mandatory, Multiple) Feature name FNAME Mandatory Single Feature value FVALUE Mandatory Multiple Feature Unit FUNIT Optional Single Guideline for suppliers to provide product data / Version 3.1 Status: 2015-11-13 Identification code of the ETIM feature e.g. „EF001234“ Defined feature values according to the ETIM classification: - Number value in case of numeric or range feature - Boolean value in case of logical feature (“true” or “false”) - Identification code of the ETIM value e.g. „EV001234“ in case of alphanumerical feature Unit of measurement of the feature; Standard measuring units should be used; When transferring ETIM classification, the specification of units is not necessary (and - Page 17 of 88 - Designation Supplementary details about the feature value Mandatory/ Optional Element name FVALUE_DETAILS Optional Single/ Multiple Single Explanation usually not desired), because it is already fixed within ETIM Usage a: Explanation of the feature characteristics. A manufacturer specific color can be transmitted here: (polar white, magenta, ash-grey, ..., see explanation 5c) Usage b: Explanation why a specific value will not be transmitted (see explanation 5c) Data type Field length Lang. specific dtMLSTRING 250 dtPUNIT 3 - dtPUNIT 3 - dtNUMBER - - dtNUMBER - - Yes T_NEW_CATALOG PRODUCT PRODUCT_ORDER_DETAILS (Mandatory, Single) Order unit ORDER_UNIT Mandatory Single Content of the unit CONTENT_UNIT Mandatory Single Packing quantity NO_CU_PER_OU Optional Single Price quantity PRICE_QUANTITY Optional Single Guideline for suppliers to provide product data / Version 3.1 Status: 2015-11-13 Unit in which the product can be ordered; it is only possible to order multiples of the product unit. For ETIM catalogs, the price also always refers to this unit (or to multiples of it). Example: Crate of mineral water with 6 bottles Order unit: "crate", content unit/unit of the article: "bottle" Packing quantity: "6" Unit of the product related to the order unit. Number of content units per order unit of the product. If order unit and content unit are identical, the value is always „1“ A multiple of the order unit indicating to which quantity all the specified prices refer to. The value is always integer for ETIM catalogs. General designation in the ETIM- - Page 18 of 88 - Designation Mandatory/ Optional Element name Single/ Multiple Minimum quantity QUANTITY_MIN Optional Single Quantity interval QUANTITY_INTERVAL Optional Single Explanation environment: ”price unit” (e.g. 1, 100, 1000) Minimum order quantity with respect to the order unit. The value should always be integer because of compatibility to the systems of the data receivers. This minimum order quantity (QUANTITY_MIN) is not the same to the minimum quantity in the sub tree of the packing units (UDX.EDXF.QUANTITY_MIN), even if the numerical value can be the same! Number indicating the quantity steps in which the product can be ordered, e.g. »5« The value should furthermore be integer because of compatibility to the systems of the data receivers. This information doesn’t have to be the same to the packing unit in the sub tree packing units, even if the numerical value can be the same! Data type Field length Lang. specific dtFLOAT - - dtFLOAT - - dtDATETIM E 10 - dtDATETIM E 10 - - - T_NEW_CATALOG PRODUCT PRODUCT_PRICE_DETAILS (Mandatory, Multiple) The element PRODUCT_PRICE_DETAILS and its sub elements specify the price data. Datetime (Valid start date) Datetime (Valid end date) Daily price DATETIME type=“valid_start_date” +Mandatory Single DATETIME type=“valid_end_date” Optional Single DAILY_PRICE Optional Single Guideline for suppliers to provide product data / Version 3.1 Status: 2015-11-13 Date for the beginning of the period of validity. Date for the end of the period of validity. Used value: <Date> yyyy-mm-dd Is used in the ETIM BMEcat to transmit, that a product has no fixed price (prices dtBOOLEAN - Page 19 of 88 - Designation Element name Mandatory/ Optional Single/ Multiple Explanation Data type Field length Lang. specific on request). In this case “true” has to be transmitted. If products have a fixed price this field is not required. See also 5e “Prices” T_NEW_CATALOG PRODUCT PRODUCT_PRICE_DETAILS PRODUCT_PRICE (Mandatory, Multiple) Price type PRODUCT_PRICE type=… Mandatory Single Nonbinding recommended price type= ”net_list” type= ”net_custom er” type= ”nrp” Price amount PRICE_AMOUNT Mandatory Single Currency PRICE_CURRENCY Optional Single Tax rate TAX Optional Single Price factor PRICE_FACTOR Optional Single Lower quantity limit LOWER_BOUND Optional Single Territory TERRITORY Optional Multiple List price Customer price Guideline for suppliers to provide product data / Version 3.1 Status: 2015-11-13 Attribute, which specifies the type of price, e.g. See also 5e “Prices” (Purchasing) list price excluding sales tax; discountable list(gross)price Customer-specific end price excluding sales tax; net purchase price without sales tax Nonbinding recommended (retail) price; suggested retail price incl. sales tax Amount of the price (0.00 is no valid price, except products without list price, see explanation 5e Currency of the price; If nothing is specified in this field, the currency defined in the document header (HEADER) in the element CURRENCY is used for all prices. Factor for tax applicable to this price »0.19« (is »19%«) The (discount) factor always multiplied by the price specified in this element in order to determine the end price. Lower quantity limit for graduated prices. The unit for the graduated price limit is the order unit (ORDER_UNIT), default value = 1. Territory in which the product price is val- dtSTRING 20 - dtNUMBER - - dtCURRENCIES 3 - dtNUMBER - - dtNUMBER - - dtNUMBER - - dtCOUN- 6 - - Page 20 of 88 - Designation Element name Mandatory/ Optional Single/ Multiple Explanation Data type id. If not specified, the value from the element TERRITORY of the HEADER is taken. TRIES Field length Lang. specific T_NEW_CATALOG PRODUCT MIME_INFO (Optional, Single) With the element MIME_INFO references to multimedia supplementary documents of a product can be specified. An infinite number of sub elements MIME can contain. The MIME element refers to a file that is transmitted on a separate way. T_NEW_CATALOG PRODUCT MIME_INFO MIME (Mandatory, Multiple) MIME type MIME_TYPE +Mandatory Single Source MIME_SOURCE Mandatory Single Designation MIME_DESCR Optional Single Alternative text MIME_ALT Optional Single Purpose MIME_PURPOSE +Mandatory Single Type of the supplementary document. The element is based on MIME types that are common on the internet (see explanation 5f). The relative path and the file name or URL address. The MIME_SOURCE string is combined with the base path (MIME_ROOT) in the HEADER (see explanation 5f). Describes the kind and usage of the MIME document with a code (see explanation 5f). Alternative text used if the file cannot be represented (e.g. by the browser) in the target system. Desired purpose of the MIME document on the target system. Guideline data receivers: if you deliver a MIME info at least one picture as MIME_PURPOSE = “normal” has to be delivered (see explanation 5f). dtSTRING 100 - dtMLSTRING 255 Yes dtMLSTRING 250 Yes dtMLSTRING 80 Yes dtSTRING 20 - T_NEW_CATALOG PRODUCT USER_DEFINED_EXTENSIONS (+Mandatory, Single) Guideline for suppliers to provide product data / Version 3.1 Status: 2015-11-13 - Page 21 of 88 - Designation Element name Single/ Multiple Explanation Data type Field length Optional Single Short name of the manufacturer dtSTRING 10 - Optional Single Very short description of a product e.g. for ERP systems or invoices/delivery notes. A brand name for a specific product, e.g. Supplier = “Master Company”, Manufacturer = “Miller”, Brand = “Brandy”. Tender text (a defined text for generating comparable competing offers from different bidders looking to obtain a business activity in works, supply, or service contracts). Date from when the product should become active. This is useful for central databases, where a supplier might submit the product in advance in order to allocate a branch product number. If the product is not tradable at the time of submission, this date indicates when the product is available for trade. Format: yyyy-mm-dd Is given when in the field PRODUCT_STATUS an expiration mark is delivered. Format : yyyy-mm-dd Example: 2015-10-24, which means, that this is the last day, the product can be ordered regular. dtMLSTRING 40 Yes dtSTRING 50 - Very short description UDX.EDXF.MANUFACTURER_A CRONYM UDX.EDXF.DESCRIPTION_VER Y_SHORT Brand name UDX.EDXF.BRAND_NAME Optional Single Tender text UDX.EDXF.TENDER_TEXT Optional Single Validation date product UDX.EDXF.VALID_FROM Optional Single Expiration date product UDX.EDXF.EXPIRATION_DATE Optional Single Short name Lang. specific Mandatory/ Optional dtMLSTRING 64000 Yes dtDATETIM E 10 - dtDATETIM E 10 - 20 - T_NEW_CATALOG PRODUCT USER_DEFINED_EXTENSIONS UDX.EDXF.DISCOUNT_GROUP (Optional, Single) Discount group of the manufacturer UDX.EDXF.DISCOUNT_GROUP _MANUFACTURER Optional Single Guideline for suppliers to provide product data / Version 3.1 Status: 2015-11-13 Discount group key of the manufacturer. At least one group of the manufacturer or the supplier has to be specified; also both discount groups can be given. dtSTRING - Page 22 of 88 - Designation Element name Mandatory/ Optional Single/ Multiple Discount group of the supplier UDX.EDXF.DISCOUNT_GROUP _SUPPLIER Optional Single Bonus group of the supplier UDX.EDXF.BONUS_GROUP_SU PPLIER Optional Single Code PKWiU 2008 UDX.EDXF.PKWIU Optional Single Declaration UDX.EDXF.DECLARATION type=… date=… Optional Multiple Guideline for suppliers to provide product data / Version 3.1 Status: 2015-11-13 Explanation (A list of all included discount groups with factors and possibly descriptions has to be agreed separately.) If there is no fixed discount group (e.g. all products have the same discount): “no_discount_group” If there is no discount group for this product (net price): „net_price“ Discount group key of the supplier. At least one group of the supplier or the manufacturer has to be specified; also both discount groups can be given. (A list of all included discount groups with factors and possibly descriptions has to be agreed separately.) If there is no fixed discount group (e.g. all products have the same discount): “no_discount_group” If there is no discount group for this product (net price): „net_price“ Bonus group key of the supplier. If there is no fixed bonus group the value “no_bonus_group” should be used. Code of the product according to the standard PKWiU 2008 (= Polska Klasyfikacja Wyrobów i Usług), in the format: PKWIU.number, for example: PKWIU.99.12.22.00 (relevant for Poland) Information about several declarations (types are recommended but the list is Lang. specific Data type Field length dtSTRING 20 - dtSTRING 20 - dtSTRING 50 - dtSTRING 50 - - Page 23 of 88 - Designation Element name Mandatory/ Optional Single/ Multiple Explanation Data type Field length Lang. specific open!). The element contains the type, the date and the filename of a media asset of type declaration. The reason for this element is higher flexibility in transfer of different PDFs containing declarations like shown in the type attribute list. For future requirements it is easy to enlarge the list. Date of issue of the document in format dtDATETIME yyyy-mm-dd; File name to be referenced because there is more than one media asset of type MIME_DESCR “MD36” (= “Declaration”). Remark: This may be an issue for systems needing a distinct selection; Example: <UDX.EDXF.DECLARATION type=”DOP” date=”2015-07-01”> myDOP_1526.pdf</UDX.EDXF.DECLAR ATION> RoHs DOP DOC CE Guarantee type= “RoHS” type= “DOP” type= “DOC_CE” RoHS declaration Declaration of performance Declaration of conformity CE Guarantee statement (A special guarantee statement in which the manufacturer assures, grants or limits the product guarantee.) type= “guarantee” T_NEW_CATALOG PRODUCT USER_DEFINED_EXTENSIONS UDX.EDXF.ADDITIONAL_FACTORS (Optional, Single) Additional factor UDX.EDXF.ADDITIONAL_PRICE _FACTOR +Mandatory Single Guideline for suppliers to provide product data / Version 3.1 Status: 2015-11-13 In many cases suppliers give more than one discount to their customers. dtNUMBER - Page 24 of 88 - - - Designation Element name Mandatory/ Optional Single/ Multiple Explanation Data type Field length Lang. specific e.g. 0.95; This element refers to the element “PRICE_FACTOR” in the subtree <T_NEW_CATALOG PRODUCT PRODUCT_PRICE_DETAILS PRODUCT_PRICE> UDX.EDXF.ADDITIONAL_ FACTOR_INFO Reason +Mandatory Single Stock information UDX.EDXF.PRODUCT_TO_STO CK Optional Single Product series UDX.EDXF.PRODUCT_SERIES Optional Multiple Product variation UDX.EDXF.PRODUCT_VARIATI ON Optional Multiple Reverse Charge (Austria) UDX.EDXF.AT.REVERSE_CHAR GE_INFO Optional Single Textual information about the price factor. Information if the product is defined as “produced to stock” from the manufacturer or “normally on stock” from a retailer – not the guarantee that the product is ever on stock. Indication to which product series, e.g. switch program(s) a product belongs (see explanation 5i). Subtype of the product within the product series; e.g. series = “Golf”, variation = “GTI” Element only for Austria: Information if this product is subject to “reverse charge”. This information is necessary for the Austrian wholesalers for the invoices they give to their customers. The statement here is legally binding! dtMLSTRING 150 dtBOOLEAN - Yes - dtMLSTRING 50 Yes dtMLSTRING 50 Yes dtBOOLEAN - - T_NEW_CATALOG PRODUCT USER_DEFINED_EXTENSIONS UDX.EDXF.COUNTRY_BRANCH_NUMBERS (Optional, Single) Branch number UDX.EDXF.COUNTRY_BRANCH _NUMBER type=… country=… +Mandatory Multiple Guideline for suppliers to provide product data / Version 3.1 Status: 2015-11-13 Country specific branch number. Many products are traded in several markets that have a central branch database. Some products could conceivably exist in several branch databases in a single market. This element allows the supplier to dtNUMBER - Page 25 of 88 - - - Designation Element name Mandatory/ Optional Single/ Multiple type +Mandatory Single country +Mandatory Single Explanation provide one or more branch- and country specific product numbers. NOTE: Only one branch number may be supplied for each country and branch. The industry to which the branch database number applies. Predefined values: - electrical - HVAC - building - shipbuilding The country for which the branch number is intended. Lang. specific Data type Field length dtSTRING 20 - - - dtCOUNTRIES T_NEW_CATALOG PRODUCT USER_DEFINED_EXTENSIONS UDX.EDXF.COUNTRY_BRANCH_SUPPLIER_IDS (Optional, Single) Supplier ID UDX.EDXF.COUNTRY_BRANCH _SUPPLIER_ID type=… country=… +Mandatory Multiple type +Mandatory Single country +Mandatory Single Country and branch specific Supplier ID. Used in conjunction with UDX.EDXF.COUNTRY_BRANCH_NUMB ER to transmit the branch specific supplier number. This number is issued by the central branch database. The industry to which the Supplier ID applies. Predefined values: - electrical - HVAC - building - shipbuilding The country for which the Supplier ID is intended. dtNUMBER dtSTRING dtCOUNTRIES T_NEW_CATALOG PRODUCT USER_DEFINED_EXTENSIONS UDX.EDXF.PACKING_UNITS (Optional, Single) Guideline for suppliers to provide product data / Version 3.1 Status: 2015-11-13 - Page 26 of 88 - - - 20 - - - Lang. specific Due to the fact that BMEcat® 2005 does not allow multiple appearances of sizes like volume, weight, length ... the sub tree is illustrated completely via UDX elements. The UDX sub tree PACKING_UNITS contains information about the different packing units. The sub element PACKING_UNIT can occur multiple. For each product at least the smallest regular PACKING_UNIT has to be indicated. The indication of all additional existing packing units is certainly important. Please be sure to observe the “Examples of packing variants” and the corresponding information in chapter 5i. T_NEW_CATALOG PRODUCT USER_DEFINED_EXTENSIONS UDX.EDXF.PACKING_UNITS UDX.EDXF.PACKING_UNIT (+Mandatory, Multiple) Minimum quantity with respect to the order unit (ORDER_UNIT), beginning Minimum UDX.EDXF.QUANTITY_MIN +Mandatory Single dtFLOAT - quantity with this order quantity, the respective packing unit is used. Maximum quantity with respect to the order unit (ORDER_UNIT), up to this Maximum UDX.EDXF.QUANTITY_MAX Optional Single dtFLOAT - quantity order quantity, the respective packing unit is used. Code for the packing unit; has to be seUDX.EDXF.PACKING_UNIT_CO Packing unit +Mandatory Single lected from the list of predefined values dtPUNIT 3 DE code (see chapter 8). Name of the packing unit. In Norway, the following names are valid: UDX.EDXF.PACKING_UNIT_NA Packing unit dtMLOptional Single f-pak, m-pak, d-pak,t-pak 20 Yes ME name STRING In Sweden, the following values are valid: Bas, Mellan, Topp Package A flag indicating whether a package may dtBOOLEUDX.EDXF.PACKAGE_BREAK Optional Single - break be broken. AN Volume of the packing unit in cubic meters UDX.EDXF.VOLUME Volume Optional Single dtNUMBER - (m³) Gross weight of the packing unit in kiloUDX.EDXF.WEIGHT Gross weight Optional Single dtNUMBER - gram (kg) UDX.EDXF.LENGTH Length Optional Single Length of the packing unit in meters (m) dtNUMBER - UDX.EDXF.WIDTH Width Optional Single Width of the packing unit in meters (m) dtNUMBER - UDX.EDXF.DEPTH Depth Optional Single Depth of the packing unit in meters (m) dtNUMBER - UDX.EDXF.DIAMETER Diameter Optional Single Diameter of the packing unit in meters (m) dtNUMBER - Designation Element name Mandatory/ Optional Single/ Multiple Guideline for suppliers to provide product data / Version 3.1 Status: 2015-11-13 Explanation Data type Field length - Page 27 of 88 - Lang. specific Designation Element name Mandatory/ Optional Single/ Multiple Explanation Data type Field length GTIN/EAN code UDX.EDXF.GTIN Optional Single GTIN (formerly EAN code) of packing unit dtSTRING 14 - Single GS1-128 is an application standard of the GS1 implementation using the Code 128 barcode specification. GS1-128 uses a series of Application Identifiers to include additional data such as best before dates, batch numbers, quantities, weights and many other attributes needed by the user. dtSTRING 48 - GS1_128 UDX.EDXF.GS1_128 Optional T_NEW_CATALOG PRODUCT USER_DEFINED_EXTENSIONS UDX.EDXF.PRODUCT_LOGISTIC_DETAILS (Optional, Single) Net weight UDX.EDXF.NETWEIGHT Optional Single Region of origin UDX.EDXF.REGION_OF_ORIGI N Optional Single Net weight of the product in kilograms in reference to one ORDER_UNIT, e.g. cable duct per 1 m. Description of the region according to >>ISO-3166-2<< (Country Subdivision Codes). Region codes must be written in capital letters. dtNUMBER - - 10 - dtDATETIM E 10 - dtSTRING 10 - dtSTRING T_NEW_CATALOG PRODUCT USER_DEFINED_EXTENSIONS UDX.EDXF.REACH (Optional, Single) Date UDX.EDXF.REACH.LISTDATE Optional Single REACH info UDX.EDXF.REACH.INFO +Mandatory Single Guideline for suppliers to provide product data / Version 3.1 Status: 2015-11-13 Date, on which the product was checked by the manufacturer for REACH Format: yyyy-mm-dd If “no data” is delivered in the following field UDX.EDXF.REACH.INFO the date of the catalog production has to be given here. Indication, if the product contains a “SVHC = substance of very high concern” in a concentration of more than 0.1 mass percentage (referring to the candidates/substances that were published by ECHA at the previous given date). Possible values: - Page 28 of 88 - Designation Element name Mandatory/ Optional Single/ Multiple Explanation Data type Field length Lang. specific - true contains substances > 0.1 mass percentage - false do not contain substances >0.1 mass percentage - no data if REACH info is not yet available for a certain product If “true” is given, a deep link at info is mandatory (see explanation 5g). The indication only refers to the check at the given date and says explicit nothing about products that were already delivered to the data receiver or about products that will be the delivered in the future (valid is always the indication on the delivery note) T_NEW_CATALOG PRODUCT USER_DEFINED_EXTENSIONS UDX.EDXF.SURCHARGE_LIST (Optional, Single) The sub element UDX.EDXF.SURCHARGE_LIST specifies the transmission of surcharge data of a product (e.g. primary materials like copper, brass, WEEE-charge etc.). The surcharge data can be given multiple if a product contains several metals. The information about surcharges is country specific and must be defined in detail between a data supplier and a data receiver. Based on these surcharge rules, the necessary elements of the ETIM BMEcat has to be selected, incl. their combination. Please note the additional examples and further explanations that are listed below. T_NEW_CATALOG PRODUCT USER_DEFINED_EXTENSIONS UDX.EDXF.SURCHARGE_LIST UDX.EDXF.SURCHARGE (+Mandatory, Multiple) As possible, the suggested English values for this element must be used. If there is no value for a required type of surcharge, Type of surUDX.EDXF.SURCHARGE_TYPE +Mandatory Single the data supplier is free to create an own dtSTRING 20 charge text. As possible, also in English. Suggested values for primary materials: - copper Guideline for suppliers to provide product data / Version 3.1 Status: 2015-11-13 - Page 29 of 88 - Designation Element name Mandatory/ Optional Single/ Multiple Manner of surcharge UDX.EDXF.SURCHARGE_MAN NER Optional Single Surcharge factor UDX.EDXF.SURCHARGE_PERC ENTAGE Optional Single Guideline for suppliers to provide product data / Version 3.1 Status: 2015-11-13 Explanation - MK copper (= processed copper) - aluminium - lead - silver - brass - gold - platinum Suggested values for other surcharges: - packaging - insurance - dearness - recycling - recycling WEEE - SLRS (recycling fee for luminaires, lamps etc.) - SENS (recycling fee for household appliances or similar) - SWICO (recycling fee for office equipment or similar) - INOBAT (battery recycling) - VOC (Volatile organic compounds) Manner of surcharge base / cumulated. Allowed values: „base“ or „cumulated“. „base“ is the value calculated by the PRODUCT_PRICE. “cumulated“ is suitable when an up- or down stroke is already made by an additional UDX.EDXF.SURCHARGE_LIST On the product price, a percentage surcharge is calculated. Example: 0.05 (corresponds to 5%) This must not be given if material weight is specified. If a step size is specified either the surcharge factor or the surcharge price Lang. specific Data type Field length dtSTRING 10 - - - dtNUMBER - Page 30 of 88 - Designation Element name Mandatory/ Optional Single/ Multiple Surcharge price amount UDX.EDXF.SURCHARGE_PRIC E_AMOUNT Optional Single Type of calculation UDX.EDXF.SURCHARGE_CALC ULATION Optional Single Material basis UDX.EDXF.MATERIAL_BASIS Optional Single Material weight UDX.EDXF.MATERIAL_BASIS_ WEIGHT Optional Single Guideline for suppliers to provide product data / Version 3.1 Status: 2015-11-13 Explanation amount must be indicated. On the product price, a surcharge price amount is calculated. Example: 0.02 (corresponds to 2 cents) This must not be given if material weight is specified. If a step size is specified either the surcharge price amount or the surcharge factor must be indicated. Describes if the surcharge that is indicated at UDX.EDXF.SURCHARGE_PERCENTAG E must be calculated on base of the gross list price (net_list) or the net price (net_customer respectively gross price ./. discount): 1 = gross price 2 = net price If no value is given, the gross price (1) will be assumed. This only has to be declared if UDX.EDXF.SURCHARGE_PERCENTAG E is given. Material basis must be specified for calculating primary material surcharges. This element is mandatory if a material basis is defined by the data supplier. An amount in €/100 kg, basic quotation of the primary material is already included in the price. Example: Flexible cable CU 150€/100kg Medium voltage power cable CU 000€/100kg (respectively another currency depending on the country) Material weight for the surcharge in gram/price reference quantity (PRICE_- Data type Field length Lang. specific dtNUMBER - - dtNUMBER - - dtNUMBER - - dtNUMBER - - - Page 31 of 88 - Designation Mandatory/ Optional Element name Single/ Multiple Step size UDX.EDXF.MATERIAL_BASIS_ SURCHARGE_THRESHOLD Optional Single Step triggering UDX.EDXF.MATERIAL_BASIS_ SURCHARGE_SHUTTER Optional Single Surcharge/credit UDX.EDXF.MATERIAL_BASIS_ SURCHARGE_CREDIT Optional Single Surcharge/table UDX.EDXF.MATERIAL_BASIS_ SURCHARGE_TABLE Optional Single Explanation QUANTITY). This must not be given if step size is specified. Step size as triggering moment for the calculation of the surcharge with surcharge factor or amount. This must not be given if material weight is specified. If this value is indicated, UDX.EDXF.SURCHARGE_PERCENTAGE or UDX.EDXF.SURCHARGE_PRICE_AMOUNT must be specified. Description at which point the step is triggered: 1 = per started 2 = per finished if no value is indicated, finished step (2) will be assumed Describes if only a surcharge or a surcharge/credit takes place: 1 = only surcharge 2 = surcharge/credit if no value is indicated, surcharge (1) will be assumed Information about the reference to a surcharge table of a product Data type Field length Lang. specific dtNUMBER - - dtNUMBER - - dtNUMBER - - dtMLSTRING 50 Yes dtSTRING 20 - - - T_NEW_CATALOG PRODUCT PRODUCT_REFERENCE (Optional, Multiple) Reference type PRODUCT_REFERENCE type=... +Mandatory Single Quantity PRODUCT_REFERENCE Optional Single Guideline for suppliers to provide product data / Version 3.1 Status: 2015-11-13 Describes the relationship between the two products. For the permitted values for the attribute of PRODUCT_REFERENCE see chapter 5f. Describes how many products are being dtINTEGER - Page 32 of 88 - Designation Mandatory/ Optional Element name Single/ Multiple quantity=… Reference product PROD_ID_TO +Mandatory Single Catalog ID CATALOG_ID Optional Single Catalog Version CATALOG_VERSION Optional Single Explanation referenced. Unique number of the product to which a reference is made. Unique catalog identification, if the referenced product is not listed in the same catalog. Version number of the referenced product catalog. Lang. specific Data type Field length dtSTRING 32 - dtSTRING 20 - dtSTRING 7 - 60 - dtNUMBER - - dtCOUNTRIES 2 - T_NEW_CATALOG PRODUCT PRODUCT_LOGISTIC_DETAILS (Optional, Single) T_NEW_CATALOG PRODUCT PRODUCT_LOGISTIC_DETAILS CUSTOMS_TARIFF_NUMBER (Optional, Multiple) Customs number CUSTOMS_NUMBER +Mandatory Single Statistics factor STATISTICS_FACTOR Optional Single Country of origin COUNTRY_OF_ORIGIN Optional Multiple Guideline for suppliers to provide product data / Version 3.1 Status: 2015-11-13 Product number for the index of goods of the foreign trade statistics. It matches with the first 8 digits of the code number of the customs tariff of the applicable trade item. Only current custom numbers are allowed (acc. to SOVA master file). Factor that transform the order unit into the unit of measurement that is necessary for the foreign trade statistics. In this example 3 m long pipes could be ordered (order unit = piece). The foreign trade statistics requires the unit meter; therefore, the factor is 3. On base of this factor and the order unit also calculation factors for different sales units can be derived. Country codes acc. to >>ISO-3166-1<< e.g.: >>DE<< (for Germany) >>NL<< (for Netherlands) dtSTRING - Page 33 of 88 - Designation Element name Mandatory/ Optional Single/ Multiple Explanation Data type Field length Ensure the usage of capital letters. The indication >>CE<< (European Union) is not allowed. Guideline for suppliers to provide product data / Version 3.1 Status: 2015-11-13 - Page 34 of 88 - Lang. specific c. Transaction T_UPDATE_PRODUCTS This transaction updates product data. The transferred products are either added to/deleted from the target system or the complete product data record is replaced by a new one. A product identification (see attribute "PRODUCT -->mode in context T_UPDATE_PRICES" in PRODUCT in context T_UPDATE_PRICES (in context T_UPDATE_PRODUCTS)) indicates whether the product should be added, deleted or modified. The product is always replaced completely; it is not possible to change individual data fields of a product. In this transaction, only the transfer of product data, but not of classification systems is possible. The transferred CATALOG_ID of the relevant supplier (SUPPLIER_NAME) and the CATALOG_VERSION to which it belongs must already be present in the target system. The attribute "T_UPDATE_PRODUCTS -->prev_version" must be set to 0 with the first transaction type after T_NEW_CATALOG (T_UPDATE_PRODUCTS, T_UPDATE_PRICES). Eventually, it is increased by 1 with each transaction of this sort. Elements T_UPDATE_PRODUCTS (Mandatory, Single) Designation Transaction Mandatory/ Optional Element name T_UPDATE_PRODUCTS – previous version Mandatory Field length Lang. specific Single/ Multiple Explanation Data type Single This attribute contains the number of previous updates or the number of the transferred updates (not the last version number). Counting begins at 0 after each T_NEW_CATALOG within the same version. - - - - - - T_UPDATE_PRODUCTS PRODUCT (Mandatory, Multiple) Product PRODUCT in context T_UPDATE_PRODUCTS - mode Mandatory Multiple Guideline for suppliers to provide product data / Version 3.1 Status: 2015-11-13 Information about a product. Determines how the transferred data should be processed by the target system. Permitted values: - delete (The product will be deleted in the target system. All other data transferred with the product will be ig- - Page 35 of 88 - Designation Element name Mandatory/ Optional Single/ Multiple Explanation - - Data type Field length Lang. specific nored.) new (The product does not exist in the target system and will be inserted.) update (The product already exists in the target system. The data fields will be completely replaced. Updating single data fields is not possible.) T_UPDATE_PRODUCTS PRODUCT PRODUCT_DETAILS (Mandatory, Single) T_UPDATE_PRODUCTS PRODUCT PRODUCT_FEATURES (Optional, Multiple) T_UPDATE_PRODUCTS PRODUCT PRODUCT_ORDER_DETAILS (Mandatory, Single) T_UPDATE_PRODUCTS PRODUCT PRODUCT_PRICE_DETAILS (Mandatory, Multiple) T_UPDATE_PRODUCTS PRODUCT MIME_INFO (Optional, Multiple) T_UPDATE_PRODUCTS PRODUCT USER_DEFINED_EXTENSIONS (Optional, Single) T_UPDATE_PRODUCTS PRODUCT PRODUCT_REFERENCE (Optional, Multiple) T_UPDATE_PRODUCTS PRODUCT PRODUCT_LOGISTIC_DETAILS (Optional, Single) If the transfer mode for the T_UPDATE_PRODUCTS transaction is set in a not allowed way, the following procedure is recommended: - Mode new: Product already exists in the target system Error, do not import, product remains unchanged in the target system - Mode update: Product does not exist in the target system Warning - Mode delete: Product does not exist in the target system Warning Guideline for suppliers to provide product data / Version 3.1 Status: 2015-11-13 - Page 36 of 88 - d. Transaction T_UPDATE_PRICES This transaction transfers new price information on products to the target system. All prices on the corresponding products already in the target system are deleted and replaced with the new prices. Essentially, the transaction consists of the SUPPLIER_PID and PRODUCT_PRICE_DETAILS elements. Elements T_UPDATE_PRICES (Mandatory, Single) Designation Transaction Mandatory/ Optional Element name T_UPDATE_PRICES – previous version Mandatory Field length Lang. specific Single/ Multiple Explanation Data type Single This attribute contains the number of previous updates or the number of the transferred updates (not the last version number). Counting begins at 0 after each T_NEW_CATALOG within the same version. - - - - - - T_UPDATE_PRICES PRODUCT (Mandatory, Multiple) Product PRODUCT in context T_UPDATE_PRICES - mode Mandatory Multiple Information about a product. Determines how the transferred data should be processed by the target system (insert, update, delete); In the transaction T_UPDATE_PRICES, determine the transfer mode is not necessary, otherwise it is always 'update'. T_UPDATE_PRICES PRODUCT PRODUCT_PRICE_DETAILS (Mandatory, Multiple) T_UPDATE_PRICES PRODUCT USER_DEFINED_EXTENSIONS (Optional, Single) Guideline for suppliers to provide product data / Version 3.1 Status: 2015-11-13 - Page 37 of 88 - 5. Explanation a. Product description The short description (DESCRIPTION_SHORT) describes the product short and concise to recognize in its kind and function among a large quantity of products - preferably unambiguous. It is not used to characterize it technically unique or highlight it among similar products. Unclear abbreviations or codes should be avoided. BMEcat® 2005 allows here 150 characters (versus max. 80 characters in BMEcat 1.2). If a data supplier wants to provide more than 80 characters, it should be noticed that the text can be automatically cut off by the data receiver after 80 characters (depending on the data receiver’s requirements of the target system also less than 80 characters are processed). Examples for desired short descriptions: Surge arrester 1-pole 180 V AC Junction box S-Color grey Feed-through terminal block 2.5 mm² blue Examples for undesired short descriptions: - Junct. box. gr. S-Color - Leakage-circuit breaker F374-25/0.03/400Hz - Normline HV150 The long description (DESCRIPTION_LONG) is used to present product features that are not presentable by the structured data. (DESCRIPTION_ SHORT, Type, ETIM). Here is also the possibility to communicate manufacturer specific benefits of a product. Example for a desired long description: Automatic luminaire with integrated movement sensor and 200° detection range, 360° creep-under protection for a gap free detection, weather-proof, painted surface, glass with semi-gloss optic, additional switching output for the connection of further luminaries, covered connection socket with large wiring space, double pipe-in lead for an easy and fast assembly, adjustment of the detection range by rotating lens and electronic calibration. Guideline for suppliers to provide product data / Version 3.1 Status: 2015-11-13 - Page 38 of 88 - For the text fields that are used in the ETIM BMEcat the given targets in no. 3b of this guideline (General guidelines for catalog content) must be strictly observed! Guideline for suppliers to provide product data / Version 3.1 Status: 2015-11-13 - Page 39 of 88 - b. Keywords Keywords (also search term or synonym) are alternative terms for the short description and are used to find products easier in electronic search systems. The data receivers expect here short and concise terms that are used by the customers customary to declare exactly the single product. They can be supplied in singular and/or plural form. It is not allowed to transmit the short description (DESCRIPTION_ SHORT) here again. Manufacturer specific terms that are well known on the market are permitted here. It is desired that several keywords (if possible) per product are supplied in separated tags. Punctuation marks should not be used in the tags. Keywords should consist of one word, sentence constructions are not allowed. It is not desired to transmit the ETIM class keywords here again as manufacturer specific product keywords. If individual ETIM class keywords match to the particular product, they can be used nevertheless in the BMEcat. Important is, that the keywords specified per product are suitable to the particular product (the keyword “Combination pliers” would be not correct for the product “Grip pliers”). Examples for desired keywords: Cross switch Bulb Dulux-Lamp Levelled pipe wrench Examples for undesired keywords: EIB, lamps EV-240 Aurora-Line Tongs for treating thick-walled corrugated steel conduit Guideline for suppliers to provide product data / Version 3.1 Status: 2015-11-13 - Page 40 of 88 - c. Classification und features Using the element PRODUCT_FEATURES a product is classified, i.e. assigned to a group in various classification or feature group systems (in our case e.g. ETIM version 6.0). Furthermore in the element PRODUCT_FEATURES features of a product are specified. Features are data objects that can be used to describe features of a product like color, nominal voltage, type of socket etc. These features are determined partially by so-called feature strips by the referenced classification and feature group system. In this case, the elements FEATURE is embedded in the corresponding element PRODUCT_FEATURES of the related classification and feature group system. In addition to the rules specified in the BMEcat ® Version 2005, the following tightening is made for the transmission of the ETIM product classification. ETIM Tightening/Explanation: If a product is assigned to an ETIM class, all attributed features of this class have to be transmitted in the BMEcat file. If a value cannot be assigned (e.g. diameter of a rectangular product), the minus sign “-“ must be delivered. If a minus sign “-“ is chosen, the data supplier has the opportunity to specify the reason in the element FVALUE_DETAILS as following: NA – Not applicable (this feature is not applicable in the context of a product in this class) MV – Missing value (an alphanumeric feature is relevant, but there is no correct value existing in this ETIM version) UN – Unknown (currently, the data supplier is not able to deliver a specific value; but basically it is possible) This applies to all feature types of the ETIM data model: A – Alphanumeric N – Numeric R – Range L – Logic Guideline for suppliers to provide product data / Version 3.1 Status: 2015-11-13 - Page 41 of 88 - Indication of manufacturer specific colors in the ETIM BMEcat: With the field FVALUE_DETAILS, more precise information to the color of a product defined in the ETIM model should be made if necessary and useful. Especially in the product ranges Domestic switching devices, Luminaries, Cable ducts or Small household appliances the indication is important and should be transmitted by the manufacturer in the ETIM BMEcat. So here are meant all alphanumeric features in ETIM that have the word “colour” (or “color”) in their names. e.g. Color of a Cover frame for domestic switching devices <FEATURE> <FNAME>EF000007</FNAME> <FVALUE>EV000080</FVALUE> <FVALUE_DETAILS>azure blue</FVALUE_DETAILS> </FEATURE> EF000007 = „Colour“ EV000080 = „Blue“ Guideline for suppliers to provide product data / Version 3.1 Status: 2015-11-13 - Page 42 of 88 - The indication of logical features can only be made by „true“ or „false“ (lowercase!), „yes“ and „no“ are not permitted. With range fields, two tags for the both values should be given in accordance to the BMEcat specification: <FVALUE>-15</FVALUE> <FVALUE>100</FVALUE>, the presentment <FVALUE>-15 to 100</FVALUE> or <FVALUE>-15 - 100</FVALUE> is incorrect. If both values are identical, they are also indicated in two separate tags. e.g. frequency 50 Hz fix: <FVALUE>50</FVALUE> <FVALUE>50</FVALUE> It is recommended to sort the 2 range values within the BMEcat file (if different). The lower value should be delivered first. The fields type „Alphanumeric“ defines a feature for which a value list exists in the ETIM model. Only the indication of codes that are part of this particular ETIM list are allowed (e.g. “EV000123”), the indication of free text is not possible here. Recommendation to set articles: For set articles consisting of a number of individual articles and therefore not clearly related to an ETIM-class, the set can be assigned to the class of the main article (reasonably the manufacturer of the set article takes this decision). Except for the classification according to ETIM, in principal other classifications can be transferred in a BMEcat in addition (e.g. eCl@ss, proficl@ss, UNSPSC, company specific classifications). Guideline for suppliers to provide product data / Version 3.1 Status: 2015-11-13 - Page 43 of 88 - d. Order The element PRODUCT_ORDER_DETAILS contains elements which indicate details of the order conditions and packing modalities. At the moment, order information in the BMEcat can only be transferred clearly and save by the fields ORDER_UNIT and PRICE_QUANTITY in the way described below. Examples Spray tin 200ml (billing per tin) <ORDER_UNIT>TN</ORDER_UNIT> <CONTENT_UNIT>MLT</CONTENT_UNIT> <NO_CU_PER_OU>200</NO_CU_PER_OU> <PRICE_QUANTITY>1</PRICE_QUANTITY> <QUANTITY_MIN>6</QUANTITY_MIN> <QUANTITY_INTERVAL>6</QUANTITY_INTERVAL> <PRICE_AMOUNT>1.90</PRICE_AMOUNT> Fitting screw (billing per unit) <ORDER_UNIT>C62</ORDER_UNIT> <CONTENT_UNIT>C62</CONTENT_UNIT> <NO_CU_PER_OU>1</NO_CU_PER_OU> <PRICE_QUANTITY>100</PRICE_QUANTITY> <QUANTITY_MIN>100</QUANTITY_MIN> <QUANTITY_INTERVAL>100</QUANTITY_INTERVAL> <PRICE_AMOUNT>5.80</PRICE_AMOUNT> Guideline for suppliers to provide product data / Version 3.1 Status: 2015-11-13 - Page 44 of 88 - Cable tray (billing per meter) <ORDER_UNIT>MTR</ORDER_UNIT> <CONTENT_UNIT>MTR</CONTENT_UNIT> <NO_CU_PER_OU>1</NO_CU_PER_OU> <PRICE_QUANTITY>1</PRICE_QUANTITY> <QUANTITY_MIN>3</QUANTITY_MIN> <QUANTITY_INTERVAL>3</QUANTITY_INTERVAL> <PRICE_AMOUNT>21.90</PRICE_AMOUNT> Miniature fuse (billing per unit) <ORDER_UNIT>C62</ORDER_UNIT> <CONTENT_UNIT>C62</CONTENT_UNIT> <NO_CU_PER_OU>1</NO_CU_PER_OU> <PRICE_QUANTITY>100</PRICE_QUANTITY> <QUANTITY_MIN>10</QUANTITY_MIN> <QUANTITY_INTERVAL>10</QUANTITY_INTERVAL> <PRICE_AMOUNT>18.40</PRICE_AMOUNT> Steel strip (billing per meter) <ORDER_UNIT>MTR</ORDER_UNIT> <CONTENT_UNIT>MTR</CONTENT_UNIT> <NO_CU_PER_OU>1</NO_CU_PER_OU> <PRICE_QUANTITY>1</PRICE_QUANTITY> <QUANTITY_MIN>25</QUANTITY_MIN> <QUANTITY_INTERVAL>25</QUANTITY_INTERVAL> <PRICE_AMOUNT>5.20</PRICE_AMOUNT> Guideline for suppliers to provide product data / Version 3.1 Status: 2015-11-13 - Page 45 of 88 - Mignon alkaline battery (billing per blister; the unit “blister” is not part of the ECE list and so cannot be used independently, for this reason, the unit PA = packet must be used) <ORDER_UNIT>PA</ORDER_UNIT> <CONTENT_UNIT>C62</CONTENT_UNIT> <NO_CU_PER_OU>4</NO_CU_PER_OU> <PRICE_QUANTITY>1</PRICE_QUANTITY> <QUANTITY_MIN>1</QUANTITY_MIN> <QUANTITY_INTERVAL>1</QUANTITY_INTERVAL> <PRICE_AMOUNT>2.24</PRICE_AMOUNT> Cable ties (billing per unit) <ORDER_UNIT>C62</ORDER_UNIT> <CONTENT_UNIT>C62</CONTENT_UNIT> <NO_CU_PER_OU>1</NO_CU_PER_OU> <PRICE_QUANTITY>100</PRICE_QUANTITY> <QUANTITY_MIN>100</QUANTITY_MIN> <QUANTITY_INTERVAL>100</QUANTITY_INTERVAL> <PRICE_AMOUNT>6.75</PRICE_AMOUNT> Installation duct (billing per meter) <ORDER_UNIT>MTR</ORDER_UNIT> <CONTENT_UNIT>MTR</CONTENT_UNIT> <NO_CU_PER_OU>1</NO_CU_PER_OU> <PRICE_QUANTITY>1</PRICE_QUANTITY> <QUANTITY_MIN>2</QUANTITY_MIN> <QUANTITY_INTERVAL>2</QUANTITY_INTERVAL> <PRICE_AMOUNT>5.60</PRICE_AMOUNT> Guideline for suppliers to provide product data / Version 3.1 Status: 2015-11-13 - Page 46 of 88 - Test badge (billing per packet) <ORDER_UNIT>PA</ORDER_UNIT> <CONTENT_UNIT>ST</CONTENT_UNIT> <NO_CU_PER_OU>10</NO_CU_PER_OU> <PRICE_QUANTITY>1</PRICE_QUANTITY> <QUANTITY_MIN>1</QUANTITY_MIN> <QUANTITY_INTERVAL>1</QUANTITY_INTERVAL> <PRICE_AMOUNT>26.56</PRICE_AMOUNT> Chipboard screw countersunk head (billing per box) <ORDER_UNIT>CS</ORDER_UNIT> <CONTENT_UNIT>C62</CONTENT_UNIT> <NO_CU_PER_OU>200</NO_CU_PER_OU> <PRICE_QUANTITY>1</PRICE_QUANTITY> <QUANTITY_MIN>1</QUANTITY_MIN> <QUANTITY_INTERVAL>1</QUANTITY_INTERVAL> <PRICE_AMOUNT>10.80</PRICE_AMOUNT> Speaker cable (billing per meter) <ORDER_UNIT>MTR</ORDER_UNIT> <CONTENT_UNIT>MTR</CONTENT_UNIT> <NO_CU_PER_OU>1</NO_CU_PER_OU> <PRICE_QUANTITY>100</PRICE_QUANTITY> <QUANTITY_MIN>100</QUANTITY_MIN> <QUANTITY_INTERVAL>100</QUANTITY_INTERVAL> <PRICE_AMOUNT>39.50</PRICE_AMOUNT> Guideline for suppliers to provide product data / Version 3.1 Status: 2015-11-13 - Page 47 of 88 - House wiring cable PVC insulated (100m ring, billing per 1,000 meter) <ORDER_UNIT>MTR</ORDER_UNIT> <CONTENT_UNIT>MTR</CONTENT_UNIT> <NO_CU_PER_OU>1</NO_CU_PER_OU> <PRICE_QUANTITY>1000</PRICE_QUANTITY> <QUANTITY_MIN>100</QUANTITY_MIN> <QUANTITY_INTERVAL>100</QUANTITY_INTERVAL> <PRICE_AMOUNT>490.00</PRICE_AMOUNT> Heat-shrink tubing (billing per unit) <ORDER_UNIT>C62</ORDER_UNIT> <CONTENT_UNIT>MTR</CONTENT_UNIT> <NO_CU_PER_OU>12</NO_CU_PER_OU> <PRICE_QUANTITY>1</PRICE_QUANTITY> <QUANTITY_MIN>1</QUANTITY_MIN> <QUANTITY_INTERVAL>1</QUANTITY_INTERVAL> <PRICE_AMOUNT>19.35</PRICE_AMOUNT> Guideline for suppliers to provide product data / Version 3.1 Status: 2015-11-13 - Page 48 of 88 - e. Prices With the element PRODUCT_PRICE_DETAILS price data of a product are specified. With the attribute “price_type” of the element PRODUCT_PRICE it is possible to indicate different prices for a product. Only one single price is permitted per PRODUCT_PRICE.price_type and LOWER_BOUND. The data receivers expect here the list(gross)price (attribute “net_list”, discountable) without sales tax and/or a customer specific special purchase price (attribute „net_customer“) for the data receiver without sales tax and/or the suggested retail price incl. sales tax (attribute „nrp“). A customer specific special purchase price can only be given if it differs from the calculated price „net_list less discount”. With the transaction T_UPDATE_PRICES it is as well possible to transmit customer specific prices. Example for the illustration of several prices <PRODUCT_PRICE_DETAILS> <DATETIME type="valid_start_date"> <DATE>2015-01-01</DATE> </DATETIME> <PRODUCT_PRICE price_type="net_list"> <PRICE_AMOUNT>61.1</PRICE_AMOUNT> <PRICE_CURRENCY>EUR</PRICE_CURRENCY> <TAX>0.19</TAX> <LOWER_BOUND>1</LOWER_BOUND> </PRODUCT_PRICE> <PRODUCT_PRICE price_type="net_list"> <PRICE_AMOUNT>53.8</PRICE_AMOUNT> <PRICE_CURRENCY>EUR</PRICE_CURRENCY> <TAX>0.19</TAX> <LOWER_BOUND>10</LOWER_BOUND> </PRODUCT_PRICE> <PRODUCT_PRICE price_type="net_customer"> <PRICE_AMOUNT>48.7</PRICE_AMOUNT> <PRICE_CURRENCY>EUR</PRICE_CURRENCY> <TAX>0.19</TAX> <LOWER_BOUND>1</LOWER_BOUND> </PRODUCT_PRICE> </PRODUCT_PRICE_DETAILS> Guideline for suppliers to provide product data / Version 3.1 Status: 2015-11-13 - Page 49 of 88 - Example for the transmission of products without prices If there are no list prices for some products (e.g. price on request), these products can be transmitted in the ETIM BMEcat anyway like described here: <PRODUCT_PRICE_DETAILS> <DATETIME type="valid_start_date"> <DATE>2015-07-01</DATE> </DATETIME> <DAILY_PRICE>true</DAILY_PRICE> <PRODUCT_PRICE price_type="net_list"> <PRICE_AMOUNT>0</PRICE_AMOUNT> <PRICE_CURRENCY>EUR</PRICE_CURRENCY> <TAX>0.19</TAX> <LOWER_BOUND>1</LOWER_BOUND> </PRODUCT_PRICE> </PRODUCT_PRICE_DETAILS> Greatest care has to be taken that the transmission in the ETIM BMEcat is exactly given as mentioned above. Especially important at this point is the element “DAILY_PRICE” (with the indication “true”) as a mark for a product without a current list price. Guideline for suppliers to provide product data / Version 3.1 Status: 2015-11-13 - Page 50 of 88 - f. Pictures and other additional documents With the element MIME_INFO references to additional multimedia documents of a product can be specified. This makes it possible, for example, to reference images and product data sheets of a product at a catalog data exchange. It is assumed that these supplementary data will be transmitted in addition (on a separate path) and can be found relative to the specified directory MIME_ROOT in the HEADER. The file names of the MIME objects may not be distinguishable only by the path statement. They also can not contain special characters. This also includes: „ “ / \ = ? * ‚ < > | ; : + The element MIME_INFO contains any number of MIME elements. Each of these elements represents exactly one reference to a supplementary document. The definition of the element MIME is inspired by the MIME format (Multipurpose Internet Mail Extensions). The MIME format is used to standardize data transfer over the internet. Predefined, suggested values for the element MIME_TYPE: Designation URL PDF document JPEG TIF GIF EPS PNG MP4 FLV Attribute value url application/pdf image/jpeg image/tif image/gif image/eps image/png video/mp4 video/flv URLvideo video/url HTML Text ldt text/html text/plain application/ldt Explanation Link to a resource on the internet (or intranet); this is not an official MIME type, but should still be used here (local) Acrobat PDF format (local) picture/graphic in the format JPEG (local) picture/graphic in the format TIF (local) picture/graphic in the format GIF (local) picture/graphic in the format EPS (but only as a supplementary picture) (local) picture/graphic in the format PNG (local) video in the format MP4 (local) video in the format FLV Link to a video resource on the internet (or intranet); this is not an official MIME type, but should still be used here (local) document in the format HTML (within the catalog file system) (local) unformatted text file EULUMDAT format for specification of photometric data When using URLs, a link to a product related single page is recommended. Guideline for suppliers to provide product data / Version 3.1 Status: 2015-11-13 - Page 51 of 88 - Suggested values for the element MIME_DESCR: Due to the fact that the predefined fields of the BMEcat do not provide enough MIME_PURPOSEs for the current requirements, the field MIME_DESCR has to deliver the more precise characterization of the document type. One of the following codes must be used. Code MIME_DESCR MD01 MD02 MD03 MD04 MD05 MD06 MD07 MD08 MD09 MD10 MD11 MD12 MD13 MD14 MD15 MD16 MD17 MD18 Designation Product picture Similar figure Safety data sheet Deep link product page Deep link REACH Energy label Product data sheet for energy label Calibration certificate Certificate Circuit diagram Construction Products Regulation Dimensioned drawing Environment label Instructions for use Light cone diagram Light Distribution Curve Logo 1c Logo 4c Code MIME_DESCR MD19 MD20 MD21 MD22 MD23 MD24 MD25 MD26 MD27 MD28 MD29 MD30 MD31 MD32 MD33 MD34 MD35 MD36 MD99 Designation Luminaire data Milieu picture Mounting instruction Product data sheet Product picture back view Product picture bottom view Product picture detailed view Product picture front view Product picture sloping Product picture top view Product picture view from the left side Product picture view from the right side Seal of approval Technical manual Test approval Wiring diagram Supplier´s declaration for products having preferential origin status Declaration Others The size of pictures: The best existing quality of a picture should be delivered. Absolutely minimum requirement: 300 pixels (only relevant for raster images, not for vector images). Notice: Pictures in the format .tif have to be delivered with the transparency path or masked! Guideline for suppliers to provide product data / Version 3.1 Status: 2015-11-13 - Page 52 of 88 - MIME_PURPOSE could be (acc. to BMEcat® 2005): Designation Screen view (normal view) Small view Print picture (enlarged view) Logo Others Product data sheet Symbol Safety data sheet Attribute value Description normal Normal picture (for usage on the internet and CD-ROM, 24-Bit, RGB, JPEG) thumbnail detail logo others data_sheet icon safety_data_sheet Preview picture small (24-Bit, RGB, JPEG) Enlarged picture (for print catalogs, 32-Bit, CMYK, TIF) Logo to a product or a supplier Other purpose. If no other value is suitable, others can be used. Product data sheet (e.g. a technical drawing) Small pictogram e.g. for description of fulfilled norms and standards Safety data sheet (e.g. for hazardous materials) The data receivers expect at least two pictures for each product according to the following specifications: Once the combination: MIME_DESCR = “MD01” (Product picture) or “MD02” (Similar figure) MIME_PURPOSE = “normal” MIME_TYPE=”image/jpeg” Exactly this combination represents the “standard picture” of a product and therefore may occur only once per product in the BMEcat. Once the combination: MIME_DESCR = “MD01” (Product picture) or “MD02” (Similar figure) MIME_PURPOSE = “detail” MIME_TYPE=”image/tif” It is important to ensure that the supplied picture fits to the product content wise. In exceptional cases, if product can only be represented by the picture of a related product, the MIME description “MD02” (Similar figure) can be used generally. Guideline for suppliers to provide product data / Version 3.1 Status: 2015-11-13 - Page 53 of 88 - Further pictures and documents can and should be delivered in addition, however, not with the indications used for the standard picture. If there is no picture available for a product, this part of the MIME part is to skip. Not permitted is the delivery of picture data that contains written or graphical information “Picture not available”. If safety data sheets are mandatory to certain products, they have to be delivered on this way. MIME_PURPOSE = safety_data_sheet MIME_DESCR = MD03 (i.e. “Safety data sheet”) The “Energy label” should be delivered in format jpg. A “product data sheet for energy label” must be supplied together with the label (Regulation EU 518/2014 of the European Commission). The necessary information depends on the product category. Guideline for suppliers to provide product data / Version 3.1 Status: 2015-11-13 - Page 54 of 88 - Permitted values for the attribute “type” of the element PRODUCT_REFERENCE (acc. to BMEcat® 2005): Attribute value Accessories accessories Base product base_prod uct Component part consists_of Designation Follow-up article followup Mandatory addi- mandatory tional product Similar product similar Selectable mandatory product Spare part select sparepart Other reference others type Explanation The reference product listed under PROD_ID_TO is an accessory product of the source product. An accessory product is considered to extend the functionality of the source product. The reference product listed under PROD_ID_TO is the base product of the source product, thus the base product is an abstract, packing-independent description of the source product The reference product listed under PROD_ID_TO is a component part of this source product. This type of reference can be used to build up parts lists. Reference is always made from the parent part to the parts it consists of. In order to reference the number of reference parts contained, the attribute "quantity" can be added. The reference product listed under PROD_ID_TO is the follow-up product to this source product. A follow-up product is defined as a product which has the same purpose and functions as the source product and can be considered a more advanced version of it. The reference product listed under PROD_ID_TO is a mandatory additional product which must always be ordered at the same time as the product article. The source product described cannot be ordered alone. If several products are marked "mandatory" they must all be ordered together with the source product. The reference product listed under PROD_ID_TO is similar to this source product. A similar product is defined as a product which is similar in purpose and functions to the source product and can possibly be used in its place. The reference product listed under PROD_ID_TO is a selectable additional product. The described reference product cannot be ordered alone. If several products are connected by "select" at least one of the additional products for the source product listed under PROD_ID_TO must be ordered. The reference product listed under PROD_ID_TO is a spare part for this source product. A spare part is defined as a part of the product that can be replaced separately in the course of maintenance and repair activities. This reference type can be used if none of the other reference types adequately describes the relationship between the reference product and the source product. Guideline for suppliers to provide product data / Version 3.1 Status: 2015-11-13 - Page 55 of 88 - Examples for some PRODUCT_REFERENCE’s: - base_product Source product = six pack of beer; base product = beer without any packing information - consists_of It must be specified that a table with the SUPPLIER_PID "Table 1" consists of one table top with the SUPPLIER_PID "Table top 5" and four table legs with the SUPPLIER_PID "Leg 7". other examples: - Cooker consists of Baking oven and Hob - Storage heater consists of Housing, Heating element and Stones - follow-up <PRODUCT_REFERENCE type="followup" <PROD_ID_TO>4711</PROD_ID_TO> </PRODUCT_REFERENCE> Guideline for suppliers to provide product data / Version 3.1 Status: 2015-11-13 - Page 56 of 88 - g. Deep linking Manufacturer specific, product related information should be available for direct access by „deep linking“ via a provided URL. Navigation elements are not allowed on the target page. A price orientation should be avoided. In the ETIM BMEcat there should be a reference via deep link to the homepage of the manufacturer about REACH „Registration, Evaluation und Authorization in the European Community (EC) used Chemicals“, i.e. not only to the general homepage, but directly to the REACH information (ideally directly to the REACH information of the single product). <UDX.EDXF.REACH> <UDX.EDXF.REACH.LISTDATE>2013-12-01</UDX.EDXF.REACH.LISTDATE> <UDX.EDXF.REACH.INFO>false</UDX.EDXF.REACH.INFO> </UDX.EDXF.REACH> A deep link is of course still be specified, to allow detailed information (in particular, what specific substances are in the product). This solution does not cover all aspects of the REACH regulation: - there is a current discussion at European level that REACH should also refer to relate on partial products - the candidate list is updated regularly, i.e. supplemented with further substances; the list will take effect immediately with publication - in different batches, a clear statement to the product is not possible - also the manufacturer has to rely on the statements of its suppliers Further information about REACH can be found on the websites of the ECHA (European Chemicals Agency) - http://echa.europa.eu Guideline for suppliers to provide product data / Version 3.1 Status: 2015-11-13 - Page 57 of 88 - h. Safety data sheet and ECCN codes Safety data sheet In the catalog, all products must be labelled, as determined in § 14 of the Hazardous Substances Act, a safety data sheet (Material Safety Data Sheet - MSDS) in accordance with Directive 91/155/EEC. In addition, all MSDS have to be deposited under the relevant product at other documents in the respective language as a PDF file (a link to the suppliers website is not allowed). Furthermore, all suppliers have to submit the MSDS to the applicable data receiver after any revision or modification, especially if a product is classified different due to a recipe modification or a statutory change. Thereby, the supplier’s product ID and the catalog have to be given for an unambiguously assignment of the MSDS. The transmitted MSDS have to be deposited as a PDF file with the next catalog update. The suppliers have to mark altered MSDS by the annual catalog update. This obligation can be fulfilled e.g. by attaching a list with all changed products. The new version of the MSDS must be annotated with the words “Reviewed: ... (date)“. The changes that were made in the revision of an MSDS have to be indicated. In addition, make sure that the description of the Multipurpose Internet Message Extension (MIME) for safety data sheets must be “MD03” (Safety data sheet). USA - Export Control Classification Number (ECCN) The ECCN is an alphanumeric product classification that is issued by the Bureau of Industry and Security (BIS), a division of the US Department of Commerce. The ECCN is used in the "Commerce Control List" to identify different products at the export control. Such a number is required by a company, if the U.S. importer re-exports the goods. The suitable ECCN for a specific product can be found in the Commerce Control List that in turn is located in the Export Administration Regulations. Alternatively you can inquire for the suitable ECCN at the following website: http://www.bis.doc.gov/Licensing Guideline for suppliers to provide product data / Version 3.1 Status: 2015-11-13 - Page 58 of 88 - Data transfer: The information on the MSDS and ECCN codes in the ETIM BMEcat are given as SPECIAL_TREATMENT_CLASS. The type for the relevance of an MSDS is the attribute “MSDS“ and the associated information „true“ or „false“. The safety data sheet is then passed as MIME. The type for the ECCN code is the attribute “ECCN” and the associated value is the ECCN. As the Guideline for suppliers declares the field SPECIAL_TREATMENT_CLASS as mandatory, always a value has to supplied. If a product is not subject to the labelling obligation, the fields mentioned in the example below have to be filled with the text „NOT_RELEVANT“ and „NONE“. Possible “Special Treatment classes” (not a complete listing): - MSDS - ECCN - AL - SIDAB Example safety data sheet MSDS, ECCN codes and Labelling obligation Export list number <PRODUCT> <SUPPLIER_PID>108014</SUPPLIER_PID> <PRODUCT_DETAILS> <DESCRIPTION_SHORT>Flat nose pliers short 160mm</DESCRIPTION_SHORT> <DESCRIPTION_LONG>Flat nose pliers short 160mm with two colored, ergonomic plastic shell. Good grip also when wet and dirty, isolating at extreme temperatures, electric hits and vibrations</DESCRIPTION_LONG> <INTERNATIONAL_PID type="GTIN">4012345108014</INTERNATIONAL_PID> <MANUFACTURER_PID>108014</MANUFACTURER_PID> <MANUFACTURER_NAME>Sample company ltd.</MANUFACTURER_NAME> <MANUFACTURER_TYPE_DESCR>108014</MANUFACTURER_TYPE_DESCR> <SPECIAL_TREATMENT_CLASS type="MSDS">true</SPECIAL_TREATMENT_CLASS> <SPECIAL_TREATMENT_CLASS type="ECCN">3A001</SPECIAL_TREATMENT_CLASS> <SPECIAL_TREATMENT_CLASS type="AL”>N</SPECIAL_TREATMENT_CLASS> </PRODUCT_DETAILS> Guideline for suppliers to provide product data / Version 3.1 Status: 2015-11-13 - Page 59 of 88 - That message here is that there is a safety data sheet, the Export Control Classification Number is 3A001 and a category of the export list does not exist. Example if a product is not subject to the labelling obligation <PRODUCT> <SUPPLIER_PID>108030</SUPPLIER_PID> <PRODUCT_DETAILS> <DESCRIPTION_SHORT>Screwdriver PZ 2</DESCRIPTION_SHORT> <DESCRIPTION_LONG> Screwdriver PZ 2 with plastic handle</DESCRIPTION_LONG> <INTERNATIONAL_PID type="GTIN">4012345108030</INTERNATIONAL_PID> <MANUFACTURER_PID>108030</MANUFACTURER_PID> <MANUFACTURER_NAME>Sample company ltd.</MANUFACTURER_NAME> <MANUFACTURER_TYPE_DESCR>108030</MANUFACTURER_TYPE_DESCR> <SPECIAL_TREATMENT_CLASS type="NOT_RELEVANT">NONE</SPECIAL_TREATMENT_CLASS> </PRODUCT_DETAILS> Important: If there is a statement “NOT_RELEVANT”, it is not allowed to define a SPECIAL_TREATMENT_CLASS in the next line of the BMEcat for this product (essentially clear, only for the avoidance of doubt). Exception for no statement according to the Special Treatment Class: If an ETIM BMEcat file is created e.g. based on a central product database and currently there is no information about a Special Treatment Class for some products, it is allowed (exceptionally!) to deliver the information “NO_DATA”: <SPECIAL_TREATMENT_CLASS type="NO_DATA">NO_DATA</SPECIAL_TREATMENT_CLASS> Guideline for suppliers to provide product data / Version 3.1 Status: 2015-11-13 - Page 60 of 88 - i. Examples of packing variants If possible, only actual packing units should be used for the packing variants, in other words, not piece (C62), meter (MTR), kilogram (KGM) or liter (LTR) for example. However, in the ETIM environment, the units piece, meter and kilogram play a role insofar as articles are delivered partially also in general unpacked by the manufacturer to the data receiver (however, piece, meter and kilogram are no packing units in the proper meaning of the word). That means, if a manufacturer delivers a single product (as a piece, meter goods or by kilogram) unpacked to the data receiver, the information about this smallest unpacked unit has to be transmitted. For one individual packing quantity (QUANTITY_MIN and QUANTITY_MAX) of a product, not more than one packing unit code (PACKING_UNIT_CODE) is allowed. Therefore, the following configurations are not allowed for an article: <USER_DEFINED_EXTENSIONS> <UDX.EDXF.PACKING_UNITS> <UDX.EDXF.PACKING_UNIT> <UDX.EDXF.QUANTITY_MIN>1<\UDX.EDXF.QUANTITY_MIN> <UDX.EDXF.QUANTITY_MAX>1<\UDX.EDXF.QUANTITY_MAX> <UDX.EDXF.PACKING_UNIT_CODE>C62<\UDX.EDXF.PACKING_UNIT_CODE> </UDX.EDXF.PACKING_UNIT> <UDX.EDXF.PACKING_UNIT> <UDX.EDXF.QUANTITY_MIN>1</UDX.EDXF.QUANTITY_MIN> <UDX.EDXF.QUANTITY_MAX>1</UDX.EDXF.QUANTITY_MAX> <UDX.EDXF.PACKING_UNIT_CODE>PA</UDX.EDXF.PACKING_UNIT_CODE> </UDX.EDXF.PACKING_UNIT> </UDX.EDXF.PACKING_UNITS> </USER_DEFINED_EXTENSIONS> The code of the packing unit (UDX.EDXF.PACKING_UNIT_CODE) of the different packing levels must be assigned the same for each product. So allowed would be e.g.: <USER_DEFINED_EXTENSIONS> <UDX.EDXF.PACKING_UNITS> <UDX.EDXF.PACKING_UNIT> <UDX.EDXF.QUANTITY_MIN>10<\UDX.EDXF.QUANTITY_MIN> <UDX.EDXF.QUANTITY_MAX>10<\UDX.EDXF.QUANTITY_MAX> Guideline for suppliers to provide product data / Version 3.1 Status: 2015-11-13 - Page 61 of 88 - <UDX.EDXF.PACKING_UNIT_CODE>PA<\UDX.EDXF.PACKING_UNIT_CODE> </UDX.EDXF.PACKING_UNIT> <UDX.EDXF.PACKING_UNIT> <UDX.EDXF.QUANTITY_MIN>100</UDX.EDXF.QUANTITY_MIN> <UDX.EDXF.QUANTITY_MAX>100</UDX.EDXF.QUANTITY_MAX> <UDX.EDXF.PACKING_UNIT_CODE>PA</UDX.EDXF.PACKING_UNIT_CODE> </UDX.EDXF.PACKING_UNIT> </UDX.EDXF.PACKING_UNITS> </USER_DEFINED_EXTENSIONS> Guideline for suppliers to provide product data / Version 3.1 Status: 2015-11-13 - Page 62 of 88 - But of course this is not allowed for the units piece, meter and kilogram: - packing unit 1 = 1 piece and - packing unit 2 = 10 pieces would not be allowed! The same refers to the units meter and kilogram Example for the correct indication of the packing units of a product: packing unit 1 = 1 unit in a packet (= PA) packing unit 2 = 10 units = carton (= CT) packing unit 3 = 40 units = 1 pallet (= PF) <USER_DEFINED_EXTENSIONS> <UDX.EDXF.PACKING_UNITS> <UDX.EDXF.PACKING_UNIT> <UDX.EDXF.QUANTITY_MIN>1<\UDX.EDXF.QUANTITY_MIN> <UDX.EDXF.QUANTITY_MAX>1<\UDX.EDXF.QUANTITY_MAX> <UDX.EDXF.PACKING_UNIT_CODE>PA<\UDX.EDXF.PACKING_UNIT_CODE> <UDX.EDXF.VOLUME>0.0323<\UDX.EDXF.VOLUME> <UDX.EDXF.WEIGHT>0.67<\UDX.EDXF.WEIGHT> <UDX.EDXF.LENGTH>0.38<\UDX.EDXF.LENGTH> <UDX.EDXF.WIDTH>0.10<\UDX.EDXF.WIDTH> <UDX.EDXF.DEPTH>0.85<\UDX.EDXF.DEPTH> <UDX.EDXF.GTIN>4012345678901<\UDX.EDXF.GTIN> </UDX.EDXF.PACKING_UNIT> <UDX.EDXF.PACKING_UNIT> <UDX.EDXF.QUANTITY_MIN>10</UDX.EDXF.QUANTITY_MIN> <UDX.EDXF.QUANTITY_MAX>10</UDX.EDXF.QUANTITY_MAX> <UDX.EDXF.PACKING_UNIT_CODE>CT</UDX.EDXF.PACKING_UNIT_CODE> <UDX.EDXF.VOLUME>0.425</UDX.EDXF.VOLUME> <UDX.EDXF.WEIGHT>6.7</UDX.EDXF.WEIGHT> <UDX.EDXF.LENGTH>1.0</UDX.EDXF.LENGTH> <UDX.EDXF.WIDTH>0.5</UDX.EDXF.WIDTH> <UDX.EDXF.DEPTH>0.85</UDX.EDXF.DEPTH> <UDX.EDXF.GTIN>4012345678002</UDX.EDXF.GTIN> </UDX.EDXF.PACKING_UNIT> <UDX.EDXF.PACKING_UNIT> <UDX.EDXF.QUANTITY_MIN>40</UDX.EDXF.QUANTITY_MIN> <UDX.EDXF.QUANTITY_MAX>40</UDX.EDXF.QUANTITY_MAX> Guideline for suppliers to provide product data / Version 3.1 Status: 2015-11-13 - Page 63 of 88 - <UDX.EDXF.PACKING_UNIT_CODE>PF</UDX.EDXF.PACKING_UNIT_CODE> <UDX.EDXF.VOLUME>0.96</UDX.EDXF.VOLUME> <UDX.EDXF.WEIGHT>28</UDX.EDXF.WEIGHT> <UDX.EDXF.LENGTH>1.2</UDX.EDXF.LENGTH> <UDX.EDXF.WIDTH>0.8</UDX.EDXF.WIDTH> <UDX.EDXF.DEPTH>1.0</UDX.EDXF.DEPTH> <UDX.EDXF.GTIN>4012345643901</UDX.EDXF.GTIN> </UDX.EDXF.PACKING_UNIT> </UDX.EDXF.PACKING_UNITS> </USER_DEFINED_EXTENSIONS> Explanation to the product 4012345678901 This is only one single product that is delivered in the packing unit packet (PA), so the QUANTITY_MIN and the QUANTITY_MAX is always 1. The packing dimensions of this single packed product are: volume 0.0323 m³ (the ETIM BMEcat requires m³) weight 0.67 kg (the ETIM BMEcat requires kg) length 0.38 m (the ETIM BMEcat requires m) width 0.1 m (the ETIM BMEcat requires m) depth 0.85 m (the ETIM BMEcat requires m) The GTIN (EAN code) of this product in this packing unit is 4012345678901. The fields, designations and units have been taken from the specification BMEcat ® 2005 to ensure a very high compatibility. Explanation to the product 4012345678002 This is a product that is delivered in the packing unit carton (CT). QUANTITY_MIN and QUANTITY_MAX are 10. That means, in one carton there are 10 products. The packing dimensions of this carton are: volume 0.425 m³ (the ETIM BMEcat requires m³) weight 6.7 kg (the ETIM BMEcat requires kg) length 1.0 m (the ETIM BMEcat requires m) width 0.5 m (the ETIM BMEcat requires m) depth 0.85 m (the ETIM BMEcat requires m) The GTIN (EAN code) of this product in this packing unit is 4012345678002. Guideline for suppliers to provide product data / Version 3.1 Status: 2015-11-13 - Page 64 of 88 - Explanation to the product 4012345643901 This is a product that is delivered in the packing unit pallet (PF = pallet). QUANTITY_MIN and QUANTITY_MAX are 40. That means, on one pallet there are 40 products. The packing dimensions of this pallet are: volume 0.96 m³ (the ETIM BMEcat requires m³) weight 28 kg (the ETIM BMEcat requires kg) length 1.2 m (the ETIM BMEcat requires m) width 0.8 m (the ETIM BMEcat requires m) depth 1.0 m (the ETIM BMEcat requires m) The GTIN (EAN code) of the product in this packing unit is 4012345643901 Product with the only packing unit pallet: Machines or similar products can have the pallet as the only packing unit. Therefore this would be then the smallest packing unit and has to be transmitted accordingly in the ETIM BMEcat also by this way. Excursus: The indication “MIN” and “MAX” result from the specification BMEcat ® 2005. At this point, it is for example possible for the product “lemonade” to declare, that at a maximum 12 bottles are always delivered in one crate. That means if 1 to 12 bottles are ordered always a crate will be delivered. The element QUANTITY_MIN would be 1 and the element QUANTITY_MAX will be 12. In the environment of ETIM this possibility usually does not play a role, which means the value QUANTITY_MIN and QUANTITY_MAX is for the packing unit of one product always identical. An exception to this rule is found at cables and wires. It could be possible that the values for QUANTITY_MIN and QUANTITY_MAX for one packing unit of a product are not identical (see explanation in chapter 9. d. b.). Guideline for suppliers to provide product data / Version 3.1 Status: 2015-11-13 - Page 65 of 88 - Further specific product examples explaining the packing units: Installation duct The installation duct is usually sold in a carton to 96 meters. If required, the article is also delivered separately, but then delivered unpacked. The single canal (length 2 m) is plastered at the front ends with foil to protect it from soiling and scratching but is not shrink-wrapped (thus no bag), that means, the first packing unit will be meter. <USER_DEFINED_EXTENSIONS> <UDX.EDXF.PACKING_UNITS> <UDX.EDXF.PACKING_UNIT> <UDX.EDXF.QUANTITY_MIN>2<\UDX.EDXF.QUANTITY_MIN> <UDX.EDXF.QUANTITY_MAX>2<\UDX.EDXF.QUANTITY_MAX> <UDX.EDXF.PACKING_UNIT_CODE>MTR<\UDX.EDXF.PACKING_UNIT_CODE> <UDX.EDXF.VOLUME>0.0004<\UDX.EDXF.VOLUME> <UDX.EDXF.WEIGHT>0.220<\UDX.EDXF.WEIGHT> <UDX.EDXF.LENGTH>2.000<\UDX.EDXF.LENGTH> <UDX.EDXF.WIDTH>0.020<\UDX.EDXF.WIDTH> <UDX.EDXF.DEPTH>0.010<\UDX.EDXF.DEPTH> <UDX.EDXF.GTIN>4012196097814<\UDX.EDXF.GTIN> </UDX.EDXF.PACKING_UNIT> <UDX.EDXF.PACKING_UNIT> <UDX.EDXF.QUANTITY_MIN>96</UDX.EDXF.QUANTITY_MIN> <UDX.EDXF.QUANTITY_MAX>96</UDX.EDXF.QUANTITY_MAX> <UDX.EDXF.PACKING_UNIT_CODE>CT</UDX.EDXF.PACKING_UNIT_CODE> <UDX.EDXF.VOLUME>0.0252</UDX.EDXF.VOLUME> <UDX.EDXF.WEIGHT>11.335</UDX.EDXF.WEIGHT> <UDX.EDXF.LENGTH>2.012</UDX.EDXF.LENGTH> <UDX.EDXF.WIDTH>0.146</UDX.EDXF.WIDTH> <UDX.EDXF.DEPTH>0.086</UDX.EDXF.DEPTH> <UDX.EDXF.GTIN>4012196097821</UDX.EDXF.GTIN> </UDX.EDXF.PACKING_UNIT> </UDX.EDXF.PACKING_UNITS> </USER_DEFINED_EXTENSIONS> Guideline for suppliers to provide product data / Version 3.1 Status: 2015-11-13 - Page 66 of 88 - Cable tray The cable tray is sold only unpacked and separately in the first packing stage with a length of 3 m. According to the size of the article (long property) the cost of the packing would exceed the effective benefit. In addition, a cable tray is made of steel and therefore relatively insensitive. The tray is marked by a lateral Inkjet printing. Likewise, a marking by a by an attached label would be conceivable. <USER_DEFINED_EXTENSIONS> <UDX.EDXF.PACKING_UNITS> <UDX.EDXF.PACKING_UNIT> <UDX.EDXF.QUANTITY_MIN>3<\UDX.EDXF.QUANTITY_MIN> <UDX.EDXF.QUANTITY_MAX>3<\UDX.EDXF.QUANTITY_MAX> <UDX.EDXF.PACKING_UNIT_CODE>MTR<\UDX.EDXF.PACKING_UNIT_CODE> <UDX.EDXF.VOLUME>0.0180<\UDX.EDXF.VOLUME> <UDX.EDXF.WEIGHT>4.95<\UDX.EDXF.WEIGHT> <UDX.EDXF.LENGTH>3.1<\UDX.EDXF.LENGTH> <UDX.EDXF.WIDTH>0.100<\UDX.EDXF.WIDTH> <UDX.EDXF.DEPTH>0.060<\UDX.EDXF.DEPTH> <UDX.EDXF.GTIN>4012195829553<\UDX.EDXF.GTIN> </UDX.EDXF.PACKING_UNIT> </UDX.EDXF.PACKING_UNITS> </USER_DEFINED_EXTENSIONS> Bend for mesh cable tray The formed component “bend” is only sold unpacked and separately as one piece. The cost of a packing would exceed the effective benefit. Concerning to the unusual format and size, a packing of such an article would be difficult to implement as well as too sophisticated. In addition, the bend is made of steel and therefore relatively insensitive. This article is marked with all required information by a label. <USER_DEFINED_EXTENSIONS> <UDX.EDXF.PACKING_UNITS> <UDX.EDXF.PACKING_UNIT> <UDX.EDXF.QUANTITY_MIN>1<\UDX.EDXF.QUANTITY_MIN> <UDX.EDXF.QUANTITY_MAX>1<\UDX.EDXF.QUANTITY_MAX> <UDX.EDXF.PACKING_UNIT_CODE>C62<\UDX.EDXF.PACKING_UNIT_CODE> <UDX.EDXF.VOLUME>0.0012<\UDX.EDXF.VOLUME> <UDX.EDXF.WEIGHT>0.627<\UDX.EDXF.WEIGHT> <UDX.EDXF.LENGTH>0.150<\UDX.EDXF.LENGTH> <UDX.EDXF.WIDTH>0.125<\UDX.EDXF.WIDTH> Guideline for suppliers to provide product data / Version 3.1 Status: 2015-11-13 - Page 67 of 88 - <UDX.EDXF.DEPTH>0.065<\UDX.EDXF.DEPTH> <UDX.EDXF.GTIN>4012196050482<\UDX.EDXF.GTIN> </UDX.EDXF.PACKING_UNIT> </UDX.EDXF.PACKING_UNITS> </USER_DEFINED_EXTENSIONS> Fire partitioning A fire partitioning is usually sold in a carton of 10 pieces. If required, the article is also delivered separately, but then delivered unpacked. The single article is marked by a lateral printing. <USER_DEFINED_EXTENSIONS> <UDX.EDXF.PACKING_UNITS> <UDX.EDXF.PACKING_UNIT> <UDX.EDXF.QUANTITY_MIN>1<\UDX.EDXF.QUANTITY_MIN> <UDX.EDXF.QUANTITY_MAX>1<\UDX.EDXF.QUANTITY_MAX> <UDX.EDXF.PACKING_UNIT_CODE>C62<\UDX.EDXF.PACKING_UNIT_CODE> <UDX.EDXF.VOLUME>0.0024<\UDX.EDXF.VOLUME> <UDX.EDXF.WEIGHT>0.66<\UDX.EDXF.WEIGHT> <UDX.EDXF.LENGTH>0.250<\UDX.EDXF.LENGTH> <UDX.EDXF.WIDTH>0.120<\UDX.EDXF.WIDTH> <UDX.EDXF.DEPTH>0.080<\UDX.EDXF.DEPTH> <UDX.EDXF.GTIN>4012195428213<\UDX.EDXF.GTIN> </UDX.EDXF.PACKING_UNIT> <UDX.EDXF.PACKING_UNIT> <UDX.EDXF.QUANTITY_MIN>10</UDX.EDXF.QUANTITY_MIN> <UDX.EDXF.QUANTITY_MAX>10</UDX.EDXF.QUANTITY_MAX> <UDX.EDXF.PACKING_UNIT_CODE>CT</UDX.EDXF.PACKING_UNIT_CODE> <UDX.EDXF.VOLUME>0.0419</UDX.EDXF.VOLUME> <UDX.EDXF.WEIGHT>7.25</UDX.EDXF.WEIGHT> <UDX.EDXF.LENGTH>0.471</UDX.EDXF.LENGTH> <UDX.EDXF.WIDTH>0.316</UDX.EDXF.WIDTH> <UDX.EDXF.DEPTH>0.282</UDX.EDXF.DEPTH> <UDX.EDXF.GTIN>4012195454359</UDX.EDXF.GTIN> </UDX.EDXF.PACKING_UNIT> </UDX.EDXF.PACKING_UNITS> </USER_DEFINED_EXTENSIONS> For each product at least the smallest regular PACKING_UNIT has to be indicated. The indication of all additional existing packing units is certainly also important, to enable the data receiver a useful disposition (also in the interest of the manufacturer). The predeGuideline for suppliers to provide product data / Version 3.1 Status: 2015-11-13 - Page 68 of 88 - fined units (cubic meter, kilogram, meter) must be strictly observed. An indication of another unit (e.g. liter, gram, millimeter) is not allowed. Please be sure to observe the “Examples of packing variants” and the corresponding information at 5i. The sub tree PACKING_UNITS is not used at the standard place for ETIM purpose because BMEcat ® 2005 do not allow multiple appearance of sizes like volume, weight, length etc. The whole sub tree is presented as a UDX element. Explanation to the field “Product series” <UDX.EDXF.PRODUCT_SERIES> If a product belongs to a program or a series, this of course should be transmitted also in the ETIM BMEcat. Especially in the sphere of switches this is important but today this is also important for Small Domestic Appliances or Luminaries. Furthermore the program name may appear in the long description additionally. Since it is possible that the description of a product series is country-related or language-specific, the data type dtMLSTRING is assigned to the field (according to the Specification BMEcat® 2005). The attribute “lang” need not be indicated, if the standard language for the element CATALOG was set to only one language. Example for monolingual indication of a product series (norm): <UDX.EDXF.PRODUCT_SERIES>Pentacolor<UDX.EDXF.PRODUCT_SERIES> Example for multilingual indication of a product series: <UDX.EDXF.PRODUCT_SERIES lang=”deu”>Flächenprogramm<UDX.EDXF.PRODUCT_SERIES> <UDX.EDXF.PRODUCT_SERIES lang=”eng”>Surface Program<UDX.EDXF.PRODUCT_SERIES> Guideline for suppliers to provide product data / Version 3.1 Status: 2015-11-13 - Page 69 of 88 - Examples of surcharge types Surcharge in percentage with step sizes (e.g. 5 %) Surcharge takes place, if the silver price rises by more than 50 € by comparison to the mentioned price in the material basis (finished step). This means, at a basis of 150 and 5% surcharge per finished step of 50.00 €: starting from 200 = 5% surcharge starting from 250 = 10% surcharge starting from 300 = 15% surcharge starting from 350 = 20% surcharge etc. <UDX.EDXF.SURCHARGE_LIST> <UDX.EDXF.SURCHARGE> <UDX.EDXF.SURCHARGE_TYPE>silver</UDX.EDXF.SURCHARGE_TYPE> <UDX.EDXF.SURCHARGE_MANNER>base</UDX.EDXF.SURCHARGE_MANNER> <UDX.EDXF.SURCHARGE_PERCENTAGE>0.05</UDX.EDXF.SURCHARGE_PERCENTAGE> <UDX.EDXF.SURCHARGE_CALCULATION>1</UDX.EDXF.SURCHARGE_CALCULATION> <UDX.EDXF.MATERIAL_BASIS>150</UDX.EDXF.MATERIAL_BASIS> <UDX.EDXF.MATERIAL_BASIS_SURCHARGE_THRESHOLD>50</UDX.EDXF.MATERIAL_BASIS_SURCHARGE_THRESHOLD> <UDX.EDXF.MATERIAL_BASIS_SURCHARGE_SHUTTER>2</UDX.EDXF.MATERIAL_BASIS_SURCHARGE_SHUTTER> <UDX.EDXF.MATERIAL_BASIS_SURCHARGE_CREDIT>1</UDX.EDXF.MATERIAL_BASIS_SURCHARGE_CREDIT> </UDX.EDXF.SURCHARGE> </UDX.EDXF.SURCHARGE_LIST> Surcharge weight with basis According to BMEcat® 2005 metal figures have to be indicated as “gram per PRICE_QUANTITY of the ORDER_UNIT”. That unusual size within the cable industry is a result of ELDANORM. Example for PRICE_QUANTITY = 1.000 (ORDER_UNIT = meter) <UDX.EDXF.SURCHARGE_LIST> <UDX.EDXF.SURCHARGE> <UDX.EDXF.SURCHARGE_TYPE>copper</UDX.EDXF.SURCHARGE_TYPE> <UDX.EDXF.SURCHARGE_MANNER>base</UDX.EDXF.SURCHARGE_MANNER> <UDX.EDXF.MATERIAL_BASIS>150</UDX.EDXF.MATERIAL_BASIS> <UDX.EDXF.MATERIAL_BASIS_WEIGHT>43000</UDX.EDXF.MATERIAL_BASIS_WEIGHT> Guideline for suppliers to provide product data / Version 3.1 Status: 2015-11-13 - Page 70 of 88 - </UDX.EDXF.SURCHARGE> </UDX.EDXF.SURCHARGE_LIST> Example for PRICE_QUANTITY = 100 (ORDER_UNIT = meter) <UDX.EDXF.SURCHARGE_LIST> <UDX.EDXF.SURCHARGE> <UDX.EDXF.SURCHARGE_TYPE>copper</UDX.EDXF.SURCHARGE_TYPE> <UDX.EDXF.SURCHARGE_MANNER>base</UDX.EDXF.SURCHARGE_MANNER> <UDX.EDXF.MATERIAL_BASIS>150</UDX.EDXF.MATERIAL_BASIS> <UDX.EDXF.MATERIAL_BASIS_WEIGHT>4300</UDX.EDXF.MATERIAL_BASIS_WEIGHT> </UDX.EDXF.SURCHARGE> </UDX.EDXF.SURCHARGE_LIST> Guideline for suppliers to provide product data / Version 3.1 Status: 2015-11-13 - Page 71 of 88 - Percentage surcharge to the list price net_list for packing (e.g. 1%) <UDX.EDXF.SURCHARGE_LIST> <UDX.EDXF.SURCHARGE> <UDX.EDXF.SURCHARGE_TYPE>packaging</UDX.EDXF.SURCHARGE_TYPE> <UDX.EDXF.SURCHARGE_MANNER>base</UDX.EDXF.SURCHARGE_MANNER> <UDX.EDXF.SURCHARGE_PERCENTAGE>0.01</UDX.EDXF.SURCHARGE_PERCENTAGE> </UDX.EDXF.SURCHARGE> </UDX.EDXF.SURCHARGE_LIST> Surcharge in percentage with step sizes and weight with basis Surcharge takes place, if the silver price rises by 1.00 € (started step) by comparison to the mentioned price in the material basis. If it declines 1.00 € below, a credit will be made. This means, at a basis of 150 and 5 % surcharge per started step of 50.00 €: starting from 151 = 5% surcharge starting from 201 = 10% surcharge starting from 251 = 15% surcharge starting from 301 = 20% surcharge etc. (credit corresponding) <UDX.EDXF.SURCHARGE_LIST> <UDX.EDXF.SURCHARGE> <UDX.EDXF.SURCHARGE_TYPE>silver</UDX.EDXF.SURCHARGE_TYPE> <UDX.EDXF.SURCHARGE_MANNER>base</UDX.EDXF.SURCHARGE_MANNER> <UDX.EDXF.SURCHARGE_PERCENTAGE>0.05</UDX.EDXF.SURCHARGE_PERCENTAGE> <UDX.EDXF.SURCHARGE_CALCULATION>1</UDX.EDXF.SURCHARGE_CALCULATION> <UDX.EDXF.MATERIAL_BASIS>150</UDX.EDXF.MATERIAL_BASIS> <UDX.EDXF.MATERIAL_BASIS_SURCHARGE_THRESHOLD>50</UDX.EDXF.MATERIAL_BASIS_SURCHARGE_THRESHOLD> <UDX.EDXF.MATERIAL_BASIS_SURCHARGE_SHUTTER>1</UDX.EDXF.MATERIAL_BASIS_SURCHARGE_SHUTTER> <UDX.EDXF.MATERIAL_BASIS_SURCHARGE_CREDIT>2</UDX.EDXF.MATERIAL_BASIS_SURCHARGE_CREDIT> </UDX.EDXF.SURCHARGE> <UDX.EDXF.SURCHARGE> <UDX.EDXF.SURCHARGE_TYPE>copper</UDX.EDXF.SURCHARGE_TYPE> <UDX.EDXF.SURCHARGE_MANNER>base</UDX.EDXF.SURCHARGE_MANNER> <UDX.EDXF.MATERIAL_BASIS>150</UDX.EDXF.MATERIAL_BASIS> Guideline for suppliers to provide product data / Version 3.1 Status: 2015-11-13 - Page 72 of 88 - <UDX.EDXF.MATERIAL_BASIS_WEIGHT>110</UDX.EDXF.MATERIAL_BASIS_WEIGHT> </UDX.EDXF.SURCHARGE> </UDX.EDXF.SURCHARGE_LIST> Transmission of information to WEEE (Waste Electrical and Electronic Equipment) <UDX.EDXF.SURCHARGE_LIST> <UDX.EDXF.SURCHARGE> <UDX.EDXF.SURCHARGE_TYPE>recycling WEEE</UDX.EDXF.SURCHARGE_TYPE> <UDX.EDXF.SURCHARGE_MANNER>base</UDX.EDXF.SURCHARGE_MANNER> <UDX.EDXF.SURCHARGE_PRICE_AMOUNT>0.28</UDX.EDXF.SURCHARGE_PRICE_AMOUNT> </UDX.EDXF.SURCHARGE> </UDX.EDXF.SURCHARGE_LIST> Guideline for suppliers to provide product data / Version 3.1 Status: 2015-11-13 - Page 73 of 88 - Graphical illustration of the metal surcharges and the relation between the elements Example for primary materials: copper, aluminium, lead, silver, brass, gold, platinum Material basis UDX.EDXF.MATERIAL_BASIS Step size UDX.EDXF.MATERIAL_BASIS_SURCHARGE_THRESHOLD Surcharge amount Surcharge factor Material basis weight UDX.EDXF.SURCHARGE_AMOUNT UDX.EDXF.SURCHARGE_PERCENTAGE UDX.EDXF.MATERIAL_BASIS_WEIGHT The diagram illustrates the dependency of the fields, but does not correspond to the order of the tags in BMEcat! Guideline for suppliers to provide product data / Version 3.1 Status: 2015-11-13 - Page 74 of 88 - 6. Link compilation - BMEcat® Version 2005 (http://www.bmecat.org), you will get the documentation after a free registration - ETIM International (http://www.etim-international.com) ETIM classification model version 6.0 (ixf) - UN/ECE Recommendation 20 (http://www.unece.org) Codes for Units of Measure Used in International Trade (PDF-Files) - D-U-N-S® Number (http://dnb.com), the Data Universal Numbering System is a 9-digit numeric code which was developed and regulated by Dun & Bradstreet in 1962 for identifying companies clearly worldwide. - Information on ECCN (http://www.trade.gov/) Guideline for suppliers to provide product data / Version 3.1 Status: 2015-11-13 - Page 75 of 88 - 7. ISO - International Organization for Standardization - ISO 3166-1:2007 http://www.iso.org Codes for the representation of names of countries and their subdivisions Part 1: Country codes - ISO 3166-2:2007 http://www.iso.org Codes for the representation of names of countries and their subdivisions Part 2: Country subdivision code - ISO 639-2:1998 http://www.loc.gov Codes for the representation of names of languages Part 2: Language Alpha-3 code (Terminology code) - ISO 4217:2008 http://www.currency-iso.org/ Codes for the representation of currencies and funds Note: The permitted currency codes of the specification BMEcat® 2005 are defined in the xsd file <bmecat_2005.xsd>. New codes that exist in the ISO do not exist in the BMEcat ® 2005 xsd and are therefore not allowed. As the best possible intermediate solution, in the ETIM BMEcat xsd the currency code “PLN” (New Polish Zloty) will be allowed, but please take care that it might be rejected in the certification acc. to the standard BMEcat ® 2005. Guideline for suppliers to provide product data / Version 3.1 Status: 2015-11-13 - Page 76 of 88 - 8. Allowed order-, quantity- and packing units A subset of the UN/ECE recommendation 20 is used: http://www.unece.org/ The following table shows, which units are used in the catalog system. For this reason, all units in the catalog have to be encoded according to the UN/ECE-codes or quantity units which are deposited in this table. Further definitions/specifications to the units are not given and are selected by the data supplier meaningful and consistent/uniform for equal products or product packing. Code BE BG BO BX C62 CA CL CMT CQ CR CS CT DR GRM KG KGM LTR MGM MLT Designation Bundle Bag Bottle Box One (unit) Can Coil Centimeter Cartridge Crate Case Carton Drum Gram Keg Kilogram Liter Milligram Milliliter Packing unit yes yes yes yes yes yes yes no yes yes yes yes yes no yes yes no no no Code MMT MTR PA PF PK PL PR PU RG RL RO SA SET ST TN TU Z2 Z3 Designation Millimeter Meter Packet Pallet (lift) Pack Pail Pair Tray / tray pack Ring Reel Roll Sack Set Sheet Tin Tube Chest Cask Guideline for suppliers to provide product data / Version 3.1 Status: 2015-11-13 Packing unit no yes yes yes yes yes yes yes yes yes yes yes yes no yes yes yes yes - Page 77 of 88 - 9. Country specific regulations In this chapter, each ETIM country organization can define specific regulations, relevant for data transfer in their market. General mandatory elements must be also mandatory in each country. But vice versa it could be possible to declare a general optional field as mandatory in a country. See annex Excel file <ETIM BMEcat Guideline V3-1 - Overview elements.xlsx> On www.etim-international.com you will find current contact information (e-mail) of each country. a. AT - Austria a) Text fields (identic to the German definition of text fields) i. For the Austrian market, the element “DESCRIPTION_LONG” is described as follows: “The aim of the element DESCRIPTION_LONG is a more detailed product description. ETIM features can be used but neither exclusively nor as a series of several ETIM features. Also not desired is a one-to-one copy of the DESCRIPTION_SHORT. Requested are formulated texts that should have a commercial and / or technical character. The long description should present features of a product – among others – that cannot be described with the structured data. Redundant information that is already submitted elsewhere in the BMEcat file should be avoided." ii. Text fields (“Short description”, “Long description”, “Keywords”, ...) may not contain font formatting (bold, italic (cursive), underline, ...). Allowed are all characters of the German character set, without semicolon, quotation marks, em dash/longer dash and apostrophe. Only the “Long description” may contain additional structures (e.g. bullets) but not HTML tags. HTML tags will be permitted if they are escaped. iii. The current spelling rules are generally observed. Particularly the use of capital letters/chapters generally should be avoided (e.g. JUNCTION BOX). Furthermore, sequences of blanks or information about the date of delivery are not allowed. The indication of a product number or a manufacturer name in the fields “Short description”, “Long description” and “Keyword” should also be avoided. b) BMEcat element “INTERNATIONAL_PID” If existing, this information is mandatory. Guideline for suppliers to provide product data / Version 3.1 Status: 2015-11-13 - Page 78 of 88 - b. BE – Belgium No country specific regulations for this version 3.1 of the ETIM Guidelines. c. CH - Switzerland No country specific regulations for this version 3.1 of the ETIM Guidelines. d. DE - Germany a) Text fields i. For the German market, the element “DESCRIPTION_LONG” is described as follows: “The aim of the element DESCRIPTION_LONG is a more detailed product description. ETIM features can be used but neither exclusively nor as a series of several ETIM features. Also not desired is a one-to-one copy of the DESCRIPTION_SHORT. Requested are formulated texts that should have a commercial and / or technical character. The long description should present features of a product – among others – that cannot be described with the structured data. Redundant information that is already submitted elsewhere in the BMEcat file should be avoided." ii. Text fields (“Short description”, “Long description”, “Keywords”, ...) may not contain font formatting (bold, italic (cursive), underline, ...). Allowed are all characters of the German character set, without semicolon, quotation marks, em dash/longer dash and apostrophe. Only the “Long description” may contain additional structures (bullets, paragraphs/line breaks) but not HTML tags. HTML tags will be permitted if they are escaped. iii. The current spelling rules are generally observed. Particularly the use of capital letters/chapters generally should be avoided (e.g. JUNCTION BOX). Furthermore, sequences of blanks or information about the date of delivery are not allowed. The indication of a product number or a manufacturer name in the fields “Short description”, “Long description” and “Keyword” should also be avoided. b) Specification for product group cables and wires in Germany Guideline for suppliers to provide product data / Version 3.1 Status: 2015-11-13 - Page 79 of 88 - NAYCWY 3x120 approx. 500 m returnable drum NAYCWY 3x120 cutting length Element: UDX.EDXF.PRODUCT_LOGISTIC_DETAILS Net weight (UDX.EDXF.NETWEIGHT) NYY-J 3x1.5 exact 3,000 m returnable drum Element: PRODUCT_PRICE Price type (PRICE_TYPE) Price currency (PRICE_CURRENCY) Price amount (PRICE_AMOUNT) Tax rate (TAX) Territory (TERRITORY) NYY-J 3x1.5 exact 500 m nonreturnable reel Element: PRODUCT_ORDER_DETAILS Order unit (ORDER_UNIT) Content unit (CONTENT_UNIT) Packing quantity (NO_CU_PER_OU) Price quantity (PRICE_QUANTITY) Quantity interval (QUANTITY_INTERVAL) NYM-J 3x1.5 100m ring Element: PRODUCT_DETAILS Short description (DESCRIPTION_SHORT) Long description (DESCRIPTION_LONG) INTERNATIONAL_PID type=”GTIN” (EAN code) Manufacturer type description (MANUFACTURER_TYPE_DESCRIPTION) see below see below see below see below see below see below see below see below see below see below n14 n14 n14 n14 n14 see below see below see below see below see below MTR MTR 1 1000 100 MTR MTR 1 1000 500 MTR MTR 1 1000 3000 MTR MTR 1 1000 500 MTR MTR 1 1000 1 net_list EUR 490.00 0.19 DE net_customer EUR 152.00 0.19 DE net_customer EUR 152.00 0.19 DE net_customer EUR 5300.00 0.19 DE net_customer EUR 5300.00 0.19 DE 110 110 176 2660 2660 Guideline for suppliers to provide product data / Version 3.1 Status: 2015-11-13 - Page 80 of 88 - NYY-J 3x1.5 exact 500 m nonreturnable reel NYY-J 3x1.5 exact 3,000 m returnable drum NAYCWY 3x120 approx. 500 m returnable drum NAYCWY 3x120 cutting length Element: UDX.EDXF.PACKING_UNITS (1 of n) Minimum quantity (UDX.EDXF.QUANTITY_MIN) Maximum quantity (UDX.EDXF.QUANTITY_MAX) NYM-J 3x1.5 100m ring Element: UDX.EDXF.SURCHARGE_LIST Surcharge type (UDX.EDXF.SURCHARGE_TYPE) Surcharge manner (UDX.EDXF.SURCHARGE_MANNER) Surcharge factor (UDX.EDXF.SURCHARGE_PERCENTAGE) Surcharge price amount (UDX.EDXF.SURCHARGE_PRICE_AMOUNT) Material basis (UDX.EDXF.SURCHARGE_MATERIAL_BASIS) Material basis weight (UDX.EDXF.SURCHARGE_MATERIAL_BASIS_WEIGHT) Quantity unit (UDX.EDXF.SURCHARGE_MATERIAL_BASIS_PRICE_UNIT) Surcharge type (UDX.EDXF.SURCHARGE_TYPE) Surcharge manner (UDX.EDXF.SURCHARGE_MANNER) Surcharge factor (UDX.EDXF.SURCHARGE_PERCENTAGE) Surcharge price amount (UDX.EDXF.SURCHARGE_PRICE_AMOUNT) Material basis (UDX.EDXF.SURCHARGE_MATERIAL_BASIS) Material basis weight (UDX.EDXF.SURCHARGE_MATERIAL_BASIS_WEIGHT) Quantity unit (UDX.EDXF.SURCHARGE_MATERIAL_BASIS_PRICE_UNIT) copper base copper base copper base aluminium base aluminium base 150 0 0 0 0 43000 43000 43000 1044000 1044000 MTR MTR MTR MTR MTR copper base copper base 0 0 800000 800000 MTR MTR 450 550 1 15 100 100 Guideline for suppliers to provide product data / Version 3.1 Status: 2015-11-13 500 500 3000 3000 - Page 81 of 88 - NYY-J 3x1.5 exact 3,000 m returnable drum NAYCWY 3x120 approx. 500 m returnable drum NAYCWY 3x120 cutting length DR RG 2000 2000 900 1100 16 1500 PF PF DR NYY-J 3x1.5 exact 500 m nonreturnable reel Element: UDX.EDXF.PACKING_UNITS (2 of n) Minimum quantity (UDX.EDXF.QUANTITY_MIN) Maximum quantity (UDX.EDXF.QUANTITY_MAX) Packing unit code (UDX.EDXF.PACKING_UNIT_CODE) DR NYM-J 3x1.5 100m ring Packing unit code (UDX.EDXF.PACKING_UNIT_CODE) RG CL 4800 4800 PF Explanation on the separate sample data: Element: PRODUCT_DETAILS Short description (DESCRIPTION_SHORT) max. 150 characters BMEcat® 2005 allows 150 characters (versus max. 80 characters in BMEcat 1.2). If a data supplier wants to provide more than 80 characters, it should be noticed that the text can be automatically cut off by the data receiver after 80 characters (depending on the data receiver’s requirements of the target system) Long description (DESCRIPTION_LONG) max. 64,000 characters In this field a textual description of the product is to enter. In catalogs it can be used as a headline of a product type. Examples: House wiring cable, PVC insulated Medium voltage power cable, VPE insulated with Cu conductor, longitudinal water blocking screen and PE sheath In this field a textual description of the application and the usage of the product is to enter. It can be related as an explaining text to a product type. Example: According to VDE 0298, part 3 – installation on top, on, in and under plaster in dry, humid and wet Guideline for suppliers to provide product data / Version 3.1 Status: 2015-11-13 - Page 82 of 88 - Element: PRODUCT_DETAILS rooms and also in brickwork and concrete, except for direct embedding in shaking-, vibratory or tamped concrete. As well suitable for outdoor usage if protected from direct sunlight, however not in the soil. Manufacturer type description (MANUFACTURER_TYPE_DESCR) max. 50 characters Element: PRODUCT_ORDER_DETAILS Quantity interval (QUANTITY_INTERVAL) Element: PRODUCT_PRICE Price type (PRICE_TYPE) Construction type, number of cores and nominal cross section should be filled in. Examples: J-Y(ST)Y 5x2x0.6 or NYM-J 3x1.5 or NAYCWY 3x120 Shows the interval in which the product can be ordered. For cutting length it is usually “1” (1 meter). For a stock length of e.g. 500 m with permitted length tolerance of maybe 450 m to 550 m it is “500” (500 meters). The length tolerances are specified by the maximum and minimum quantity. (UDX.EDXF.QUANTITY_MIN / UDX.EDXF.QUANTITY_MAX), see below net_list Discountable list(gross)price without sales tax. net_customer Net purchase price without sales tax. Surcharge data: UDX.EDXF.SURCHARGE_LIST (See also documentation ELDANORM 2000). Surcharge type Indication on the metal which is related to all further data: (UDX.EDXF.SURCHARGE_TYPE) aluminium copper lead silver Surcharge manner The surcharge data can be given multiple if a product has several metals (see example NAYCWY). In this field the value “base” has to be specified. Guideline for suppliers to provide product data / Version 3.1 Status: 2015-11-13 - Page 83 of 88 - Surcharge data: UDX.EDXF.SURCHARGE_LIST (See also documentation ELDANORM 2000). (UDX.EDXF.SURCHARGE_MANNER) Surcharge factor No value has to be entered. (UDX.EDXF.SURCHARGE_PERCENTAGE) Surcharge price amount No value has to be entered. (UDX.EDXF.SURCHARGE_PRICE_AMOUNT) Material basis The metal quotation that is already charged in the price has to be given, e.g.: (UDX.EDXF.MATERIAL_BASIS) - “000“ for hollow prices - “100“ for prices that include already the charge of the belonging metal with 100.00 €/100 kg - “150“ for prices that include already the charge of the belonging metal with 150.00 €/100 kg Notice: With so-called full prices, all data on metal surcharges can be omitted. Material basis weight Material weight (Individual metal number) has to be given in „grams per price reference quantity of (UDX.EDXF.MATERIAL_BASIS_WEIGHT) the order unit” (grams per PRICE_QUANTITY of the ORDER_UNIT) i.e. usually grams / 1,000 meter Quantity unit MTR Step size Usually no information is required for this field (UDX.EDXF.MATERIAL_BASIS_ SURCHARGE_THRESHOLD) Element: UDX.EDXF.PACKING_UNITS (1 of n) Minimum quantity / Maximum quantity (UDX.EDXF.QUANTITY_MIN / UDX.EDXF.QUANTITY_MAX) Packing unit code (UDX.EDXF.PACKING_UNIT_CODE) Depending on the different packing sizes the element can appear multiple, e.g. also to describe the content of a pallet (see example above „NYM-J 3x1.5 as 100 m ring“). (1) If “Minimum quantity” and “Maximum quantity” are equal, the product is invariably in its length (length fix). (2) If “Minimum quantity” and “Maximum quantity” are different, the product is variable in its length (length variable). Length variable products are in addition to cutting lengths also so-called stock lengths with approximately lengths. Example: a 500 m stock length – depending on the product – can vary between 450 and 550 m for manufacturing reasons. (3) Cutting lengths (length variable product) can be identified by the fact that the quantity interval is always filled in with the value “1” (meter). (4) For cutting lengths (length variable product) the largest specified “Maximum quantity” corresponds to the maximum production-technical admissible single length. The following definition is the base to avoid misinterpretation: Coil (CL): The coil is a light storage and transport container for cables and wires that generally can be used only once. Colloquially it is often also called “One-way coil”. A coil has no identification “trading unit number“ to identify the coil unambiguously. Guideline for suppliers to provide product data / Version 3.1 Status: 2015-11-13 - Page 84 of 88 - Drum (DR): The drum is a fix storage and transport container for cable and wires that generally can be used several times. This will also include returnable drums. Colloquially in Germany it is also often called “KTG drum - Cable drum organization”. A drum has an identification “trading unit / drum number” to identify the drum unambiguously. e. DK- Denmark No country specific regulations for this version 3.1 of the ETIM Guidelines. f. ES – Spain No country specific regulations for this version 3.1 of the ETIM Guidelines. g. FI – Finland No country specific regulations for this version 3.1 of the ETIM Guidelines. h. FR – France No country specific regulations for this version 3.1 of the ETIM Guidelines. i. NL – The Netherlands No country specific regulations for this version 3.1 of the ETIM Guidelines. j. NO – Norway No country specific regulations for this version 3.1 of the ETIM Guidelines. k. PL – Poland Guideline for suppliers to provide product data / Version 3.1 Status: 2015-11-13 - Page 85 of 88 - a) Text fields: For the Polish market, the elements: DESCRIPTION_SHORT, DESCRIPTION_LONG, KEYWORD should be delivered in Polish language and may not include formatting (bold, line breaks, bullet characters …). Allowed are all characters of the Polish character set (in UTF-8 encoding), without semicolon, quotation marks, dash and apostrophe. b) Additional elements There are 3 additional elements specific to the Polish market that are mandatory here: i. VAT-ID = element “VAT_ID” ii. Bonus group of the supplier = element “UDX.EDXF.BONUS_GROUP_SUPPLIER” iii. PKWIU = element “UDX.EDXF.PKWIU” l. SE - Sweden No country specific regulations for this version 3.1 of the ETIM Guidelines. Guideline for suppliers to provide product data / Version 3.1 Status: 2015-11-13 - Page 86 of 88 - 10. Change Log to previous version In this chapter, all relevant changes between versions of this guideline will be described. a. Changes between version 3.0 and 3.1 Subtree UDX.EDXF.SURCHARGE_LIST UDX.EDXF.SURCHARGE All elements of this subtree are now Optional, except UDX.EDXF.SURCHARGE_TYPE. The transfer of surcharge information is quite complicated and differs in each country. So the data supplier should know what information (that means what elements of the ETIM BMEcat) he must send to the data receiver. And in any case it must be possible, to validate the correctness of a statement Mandatory/Optional in the xsd file and the validation tool. The field length of the element MIME_TYPE is extended from 30 to 100 digits as MIME types exist already that are longer than 30 digits and that is not considered in the specification of BMEcat ® 2005. So this solution is not compliant to the specification of BMEcat ® 2005 and the ETIM BMEcat could therefore be rejected in the certification acc. to the standard BMEcat® 2005. In the specification of BMEcat® 2005 it is forbidden to use a slash “/” for the attributed value of the element MIME_TYPE. At the same time, the specification of BMEcat ® 2005 the attributed are defined with a slash “/”. So that is a mistake and we allow the slash “/” for the ETIM BMEcat. This solution is also not compliant to the specification of BMEcat ® 2005 and the ETIM BMEcat could therefore be rejected in the certification acc. to the standard BMEcat ® 2005. The correct name of the REACH subtree is UDX.EDXF.REACH (and not UDX.EDXF.REACH.PRODUCT). The name of the element UDX.EDXF.REACH.LIST_DATE was corrected to UDX.EDXF.REACH.LISTDATE The correct name of the element “Value Added Tax ID” is VAT_ID in ETIM BMEcat. The new element Brand name (UDX.EDXF.BRAND_NAME) was added. The field length of the element “UDX.EDXF.DISCOUNT_GROUP_MANUFACTURER” was changed from 10 to 20. The field length of the element “UDX.EDXF.DISCOUNT_GROUP_SUPPLIER” was changed from 10 to 20. Adjustment of the explanation of the element UDX.EDXF.NETWEIGHT Guideline for suppliers to provide product data / Version 3.1 Status: 2015-11-13 - Page 87 of 88 - The subtree T_NEW_CATALOG PRODUCT PRODUCT_LOGISTIC_DETAILS PRODUCT_DIMENSIONS was deleted because it described the data of a packed product. This information already exists in the subtree UDX.EDXF.PACKING_UNIT. Additional type for the element MIME_DESCR: MD99 “Others”. Recommendation for supplying URLs in chapter 3b. Updated the documentation for UDX.EDXF.COUNTRY_BRANCH_NUMBERS and UDX.EDXF.COUNTRY_BRANCH_SUPPLIER_IDS in order to identify the attributes used by the XSD file correctly. Guideline for suppliers to provide product data / Version 3.1 Status: 2015-11-13 - Page 88 of 88 -
© Copyright 2024 Paperzz