Als de browser instellingen niet veranderd, dan maak je gebruik van de cookies. Lees meer. Wij maken op deze website gebruik van cookies. Wij gebruiken cookies om het gebruik van onze site faciliteren, het inloggen te onthouden en t.
|Published (Last):||19 August 2016|
|PDF File Size:||7.10 Mb|
|ePub File Size:||9.53 Mb|
|Price:||Free* [*Free Regsitration Required]|
Als de browser instellingen niet veranderd, dan maak je gebruik van de cookies. Lees meer. Wij maken op deze website gebruik van cookies.
Wij gebruiken cookies om het gebruik van onze site faciliteren, het inloggen te onthouden en t. Daarnaast gebruiken wij anonieme gegevens voor het opbouwen van site statistieken zoals het aantal keer dat de sites bezocht worden, met welke browser etc. De 2BA site kan niet zonder cookies werken. For data suppliers who manage their product information on international level, the choice of a data exchange format is often the BMEcat We have tried to achieve as much similarity as possible between the BMEcat 4.
During the course of the first year since the initial release, some several small errors where identified in the documentation and the XSD file, that ETIM considered to be too much to ignore until the next major release. The supported exchange formats are mapped to the internal fields of the data model. Some internal fields may differ from the length or type as described in the guideline of the exchange formats. We create as much clarity as possible but there may be differences, which we mention in the mapping.
For example, in BMEcat the short description has a length of characters, in the data model only 70 characters.
The BMEcat 4. Corrections for the ETIM 4. Every country requires more fields then originally available in the BMEcat structure. A complete BMEcat files has to contain all active products.
A new complete file will overwrite all records in the database! Existing productrecords which are not present in the complete file will be set as "expired". Existing trade itemsrecords which are not present in the complete file will be deleted. Product information concerns data from the manufacturer about the manufactured product such as attachments and ETIM classification. The related trade item information contains all data indicating how to order the item such as gross price, order unit, minimum purchase amount and delivery time.
In many cases standard manufacturers , this information will be equal to each other, but a distinction can be made here for importers. The mapping is based on product status type, the value is informative except for expired products. The product status will be set at product and trade item level exept for expired products model code The mapping of product status types versus the data model is available here.
It is possible for a manufacturer or supplier to distribute more than one type of package for the same product. For trade items, the logistic information can be given for each unique trade item in the elements UDX. Measurements must be given in meters and weights must to be given in kilograms. If there are more than one trade items for the same product see chapter Multiple packing units for the same product. The mapping below applies to the packaging information for all trade items:.
The mapping of packing codes versus 2BA is available here. The country of origin is the country of shipment of the order. The country of production is the actual production location. Please use the country specific UDX.
For each trade item can be defined how the trade item can be ordered, on which unit the price is based and how the product can be used. The mapping of the order and price details in the import of BMEcat 4. Given the various purposes, different types of descriptions are possible to describe a trade item or product. There are three possibilities:. Wholesalers uses the structure of brand, serie, type as a filtering method and search engine optimisation SEO , for example on their webshop.
For this reason these fields are mandatory for each product record. For records which are only used as trade item data, these fields can be skipped see chapter: multiple packing units for the same product.
Some manufactures don't use serie and type grouping. More information click here. For example the United Nations number is a four digit number, ideally preceded by the letters "UN" for example, "UN". This number is not mentioned in the ETIM 4. If there are any attachments, the UDX. The DIN number is the German institute for standardisation number. In the format ETIM-x. If a value cannot be assigned, according to the ETIM guideline the data supplier has the opportunity to use a minus sign.
Values with a minus sign will be skipped by 2BA. According to the 4. Because of the different export formats the predefined values MD codes are mapped to the attachment type code list. The mapping of MD codes versus the data model is available here. The mapping of product references versus the data model is available here.
Door deze website te bezoeken maak je automatisch gebruik van cookies. Lees meer Sluiten. Wat is een Cookie Wij maken op deze website gebruik van cookies. Soort cookies Wij gebruiken cookies om het gebruik van onze site faciliteren, het inloggen te onthouden en t. Complete mapping of BMEcat 4. Exceptions There are a few exceptions in the current XSD filedate: According to the ETIM 4.
Country specific characteristics Every country requires more fields then originally available in the BMEcat structure. The use of language codes at the descriptions is highly recommended! Delivery of mutation files is also possible. Identification 2BA distinguishes two entities, the product information and related trade item information. Expired products model code can be specified via type "others" in combination with the value "expired".
Multiple packing units for the same product It is possible for a manufacturer or supplier to distribute more than one type of package for the same product. The structure with package information UDX. Logistic information For trade items, the logistic information can be given for each unique trade item in the elements UDX.
Order price details For each trade item can be defined how the trade item can be ordered, on which unit the price is based and how the product can be used. In case of piece, use code C TAX will be multiplied with Descriptions Given the various purposes, different types of descriptions are possible to describe a trade item or product. If the short description contains more characters the description will be cut to length of 70 characters. If the long description contains more characters, the description will be cut to specified length of 1.
Please use the Character Entity Reference Table to specify new lines, lists, special characters etc. The default language is Dutch and is mandatory. If no Dutch description is set, the English description will be adopted as Dutch description.
If neither a Dutch nor an English description is specified the specific record will blocked. The mapping of the language codes versus 2BA is available here Brand, serie and type Wholesalers uses the structure of brand, serie, type as a filtering method and search engine optimisation SEO , for example on their webshop. Brand; UDX. Only the value true or false is expected in this string field.
For 2BA this field is not mandatory. UN ; Unknown currently, the data supplier is not able to specifiy a value; but basically it is possible. If UDX. The minimum quality of a high resulution should be DPI for x pixels 15x15cm. If only a high resolution detail MD01 picture is specified, the import system will generate a low resolution picture.
This field is used in combination with UDX. Be careful not to use the same directory structure in both fields. The UDX. When the value starts with an URL, the import system will download the attachment.
MD47 thumbnail is not imported by 2BA. Reference items In the data model reference items will be mapped at product level, not on trade item level. BMEcat code "Base product" is used for hierarchy, see chapter 10 hierarchy. BMEcat code "Followup" can be used to refer to a successor at product level not for trade items. Files containing data from multiple data suppliers In case of catalogue messages containing products of more than one manufacturer, on every product the field the country specific UDX.
In case of a multi supplier catalogue, every trade item needs to be identified with the GLN of the supplier, the field the country specific UDX. When a multi catalogue message contains multiple suppliers of the same product, redundant product information should be avoided.
InstallData supports imports and exports in the BMEcat format. BMEcat is a German standard for distributing catalogue information. Technically it is a very comprehensive and extensible XML format. The format is mainly focused on sellable products from manufacturers. It pays less attention to the method of distinguishing manufacturer products from wholesalers trade items in comparison to GS1 on which InstallData is based. We will validate every import against this schema.
The current eCl ss-BMEcat 1. Older versions of this document can be found in the Version history of BMEcat 1. It contains how to exchange classification and properties including their values and it is designed for a national and international use. For version 1.