Exporting the BMEcat 2005.1 format involves supplying header data and catalog / product data via the parameters displayed on the Select Format step and during the Map Data step. Some information is required, as is indicated on the Map Data step.
Note: While it is possible to initiate the export process even in the absence of mandatory fields, it's important to note that the background process (BGP) will fail.
Format Availability
BMEcat 2005.1 XML can be exported from:
-
Export Manager - refer to Creating a Data Export
-
OIEP - refer to Creating an Outbound Integration Endpoint
Mapping
This format requires creating a data map between STEP and the data being processed, and may also include data transformations. For further details on mapping, refer to Data Mapping.
Selecting the BMEcat 2005.1 Export format will automatically generate the data within the <PRODUCT_FEATURES></PRODUCT_FEATURES> Tag with the in STEP available ECLASS Advanced content. The extension plug-in will produce the needed information for the output.
Standard BMEcat fields can be mapped with the usual mapping process. For more information on mapping, refer to the Outbound Map Data Options topic in the Data Exchange documentation.
To map for ECLASS Advanced, the STEP ID of the SKU / Product must be mapped to the mandatory field 'SKU ID.'
Should other relevant fields need to be mapped, they can be mapped as needed.
Configuring BMEcat Exporter
The technical starting point for the Exporter is always the SKU / Product. Therefore, the user should trigger the exporter from either the SKU / Product or a relevant ECLASS Advanced Classification node from the top ECLASS Advanced level downwards.
Note: Only mapped languages are determined for output.
-
In workbench, initiate the export for the product(s) you intend to export. For information on how to initiate an export refer to the Creating a Data Export topic in the Data Exchange documentation.
Important: When exporting from a Classification node, in the Export dropdown select 'Product.'
-
On the Select Format step of the Export Manager, fill out the following Outbound Parameters.
Outbound Parameters
The parameters that are available to fill out are controlled by the XML template that is uploaded. The fields listed below are displayed for all users.
-
Sample: An XML template file is loaded automatically but can be modified as required. This defines the format of the XML file to be exported.
Note: For more information on Generic XML instructions, refer to the Generic XML Outbound Processing Instructions topic in the Data Exchange documentation.
-
Allow empty tags: Selecting Yes indicates that export tags with empty values are included in the output. If set to No, tags containing empty values are not included in the export.
-
ECLASS ADVANCED Version: This field is mandatory. If no version is selected, then there will be no SKU / Products exported. This field specifies the root classification node of the version that should be exported. To select the relevant ECLASS Advanced Version, click the eclipses button, and navigate to the relevant version in the ECLASS Advanced structure.
-
Validate XML: Selecting Yes indicates that the BMEcat 2005.1 export file is validated against an XSD included in STEP. When validation fails, the background process also fails, and the problem is reported in the BGP execution report. If set to No, the validation is skipped and the BGP does not fail due to differences found when comparing to the XSD.
-
Export data for selected contexts: This allows for the output values for language dependent attributes, for example, the ETIM Short Description, Long Description, Keyword, and Remark values, and others. Select Yes in the dropdown to display the Select Contexts link. Click the link, select the required contexts for the export from the Select Contexts dialog, and click the Select button. The selected contexts are listed in a text box.
The chosen contexts will be presented as <LANGUAGE> elements within the <HEADER> section of the exported XML file. If the system contains the specified context-dependent attribute values, they will be incorporated into the <PRODUCT_DETAILS> segment.
Important: When using an OIEP for BMECat format export, ensure consistency between the contexts specified in the 'Export data for selected contexts' parameter and OIEP > Configuration tab > Configuration flipper > Contexts parameter. A mismatch may lead to contexts being presented differently in the exported file: those added in OIEP > Configuration tab > Configuration flipper > Contexts parameter will appear in the <PRODUCT_DETAILS> element, and those in 'Export data for selected contexts' parameter will be in the <HEADER> element.
Select default context: This shows the default context that is selected for the output. The parameter only displays contexts that were selected in the Export data for selected contexts parameter, and automatically selects the first context from the list. However, this can be changed by clicking the dropdown menu and selecting a different option.
-
FID Selection Policy: The FID in STEP remains in contrast to the new FID values generated on export. The options are:
-
Auto enumerate blocks: When selected, the FID of product blocks stored in STEP will be output with a continuous enumeration starting at "0."
-
Warn and skip element and hierarchy: When selected, product blocks, where meta-data attributes have no value, will not be part of the output. All other directly related Product Blocks will consequently also not be part of the output. All other Product Blocks will be output with the FID from STEP. The execution report will list the 'leading' product block with missing FID values.
-
Warn and auto enumerate block: When selected, product blocks, were meta-data attributes have no value, will appear in the output with an auto FID as described. All other product blocks will be output with the FID from STEP. The execution report will list the product blocks with missing FID values.
-
ECLASS ADVANCED Debug: When selected, the output will show the respective STEP ID of the 'Features' in the 'StepID' tag. The StepID tag is intended for easier internal output debug investigation
For an explanation of the remaining parameters, search the web. No validation is performed on the text entered or the selections made, but if Validate XML = Yes, errors will be reported in the execution report, as defined above.
Export Manager
OIEP
Note: When using an OIEP for BMECat format export, there is a subtle distinction in how contexts are filled in the <HEADER> and <PRODUCT_DETAILS> elements. Specifically, for the context-dependent attribute values populated in the <PRODUCT_DETAILS> element, the values set in OIEP > Configuration tab > Configuration flipper > Contexts parameter take precedence and are populated accordingly. However, the contexts presented as <LANGUAGE> elements within the <HEADER> section are determined by the settings made in the above mentioned 'Export data for selected contexts' parameter itself.