BMEcat 2005 ETIM Guidelines V5.0 import available

On June 30, ETIM International published a new version of the ETIM guideline on BMEcat 2005; the ETIM Guideline V5.0. We can inform you that our import routine now accepts this new version.

Implementation changes compared to version 4.0

There are some important changes regarding 2BA. For example, a few Dutch (NL) characteristics have been removed and moved to the regular product line, the price to order unit factor (PRICE_UNIT_FACTOR) has been added and new MD codes are available for attachments.

Element	Data model	Remarks
PRICE_UNIT_FACTOR	https://my.2ba.nl/Model/TradeItem/PriceToOrderUnitFactor	Was missing in 4.0
UDX.EDXF.MIME_ORDER	https://my.2ba.nl/Model/ProductAttachment/PresentationOrder	Was missing in 4.0
UDX.EDXF.PREDECESSOR_PID	https://my.2ba.nl/Model/Product/PredecessorProductcode	In 4.0 via PROD_ID_TO (product references)
UDX.EDXF.BATTERY_CONTAINED	https://my.2ba.nl/Model/Product/BatteriesIncluded	Was a NL Characteristic
UDX.EDXF.ROHS_INDICATOR	https://my.2ba.nl/Model/Product/ROHSIndicator	Was a NL Characteristic
UDX.EDXF.CE_MARKING	https://my.2ba.nl/Model/Product/CECertificate	Was a NL Characteristic
UDX.EDXF.UN_NUMBER	https://my.2ba.nl/Model/Product/UNCODE	In 4.0 via SPECIAL_TREATMENT_CLASS

In addition to the above changes, several fields related to hazardous substances have been added, these elements are currently not supported by 2BA. For a complete overview of the mapping to the 2BA model, we refer to the online documentation of the BMEcat 2005 ETIM Guideline V5.0.

Refurbished and used products

In 2020 we have informed you about communicating refurbished and re-usable products. We would like to draw your attention to the fact that this indicator can be specified via the PRODUCT_STATUS element.

Type	Data model
Product status type=“refurbished“	https://my.2ba.nl/Model/TradeItem/Refurbished	Is mapped to trade item
Product status type=“used“	https://my.2ba.nl/Model/TradeItem/Reused	Is mapped to trade item

Think twice before you start

If you have files according to previous ETIM guideline versions, we recommend that you upgrade to the latest version 5.0 as soon as possible. Point your software or ICT partner to the online documentation of 2BA. The rules are not imposed by 2BA, but Extensible Markup Language rules, a standard of the World Wide Web Consortium.

Developing an XML message based on an XSD and the associated rules is a task that requires XML specialization.

Common mistakes:

Incorrect specified headers
Missing mandatory elements
No closed elements (only but missing )
No open elementes (missing only )
Empty optional elements ()
Improperly defined NL Characteristics (e.g. wrong specified field types)
Failure to follow the order specified in the XSD
Not escaping symbols within strings such as an ampersand (&).

To avoid disappointment, we recommend that you use a specialized software party with sufficient XML knowledge. Of course, there are also various PIM software parties affiliated with 2BA that export a valid dataset via an efficient route so that you can easily deliver your valuable data to 2BA.

Do you have a validated BMEcat 2005 ETIM V5.0 file? Deliver it as soon as possible! If you have any further questions, please do not hesitate to contact your internal contact person at 2BA.

Follow 2BA on LinkedIn:

This is an automatically generated message, you cannot respond to it.