ETIM BMEcat Export App based on BMEcat 2005 - Baseline Structure

Prev Next

The below illustration helps you understand the schematic representation of Root element and Transaction types based on the ETIM BMEcat XSD:
ETIM-BMEcat-XSDStruc

BMEcat 2005

For the integration of product catalogs with master data, the XML based BMEcat 2005 guideline is used in the PIM system as a baseline.

With this guideline, it follows certain criteria such as:

  • Catalog data standards
  • Classification standards
  • Language(s) of the catalog content
  • Product References to follow up
  • Elements that need to be part of the xml file
  • Recommendations on character set
  • Guidelines regarding the text fields
Note:

For more information on the guidelines, see ETIM BMECAT Guideline V5-0 document.

Supported ETIM BMEcat Elements Based on XSD in Export App

The Export App is aligned with the above schema for the XML being generated. The attributes or elements associated with the entity (Part) based on the ETIM BMEcat solution are structured as below for XML export:

The Header element is a mandatory section and contains:

Elements Description Sample XML Structure (After Export)
CATALOG This element contains the attributes such as default language, catalog ID, generation date, territory, currency and so on. Header_1
BUYER This element contains the Buyer details such as Buyer name and ID. Header_2
SUPPLIER This element contains the Supplier details such as Supplier name, ID, and address. Header_3

Normally a data supplier delivers ETIM BMEcat attributes 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. For example, only the new products. All data of these (new) products must be part of the BMEcat file.

The following are the supported data transactions:

(You can decide the required transaction type for the data transfer)

Transaction Type Description Sample XML Structure
T_NEW_CATALOG With this transaction type, the exported XML file contains the attributes of the following groups:
  • Product Core Details
  • Product Details
  • Product Order Details
  • Product Price Details
  • Product Logistic Details
  • Classification Details
  • ETIM 8.0 Attributes, ETIM 9.0 Attributes, or ETIM 10.0 Attributes
  • User Defined Extensions
Notes:
  • For more information on the attribute groups, you must refer the data models.
  • The ETIM attributes exported are based on the selected ETIM versions. For example, if you select ETIM 10.0 version in the app, the ETIM 10.0 attributes are available in the catalog.
  • ETIM_T_NEW_CATALOG
    T_NEW_PRODUCTDATA With this transaction subsets of product data can be delivered in an easy and fast way PRODUCT in context T_NEW_PRODUCTDATA. The exported XML file contains the attribute of the following groups:
    • Product Core Details
    • Product Details
    • Product Logistic Details
    • Classification Details
    • ETIM 8.0 Attributes, ETIM 9.0 Attributes, or ETIM 10.0 Attributes
    Notes:
  • For more information on the attribute groups, you must refer the data models.
  • The ETIM attributes exported are based on the selected ETIM versions. For example, if you select ETIM 10.0 version in the app, the ETIM 10.0 attributes are available in the product data.
  • Here is the sample XML structure with a product in T_NEW_PRODUCTDATA
    T_New_Prodct