TB.One > Import & Export > Master Data Import via TB.Cat/XML > TB.Cat - XML Structure > TBCATALOG > PRODUCTDATA > PRODUCT > ARTICLEDATA / ARTICLE > A_COMPONENTDATA
Components on article level (see also P_COMPONENTDATA) are different for each article but do not create variants. If you provide article components, each article must contain a value.
EXAMPLE: |
ATTENTION: In that case, the value you provide for A_COMPONENTDATA would be interpreted as the "long text" of the variant dimension (the corresponding field can be seen in the UI by opening the tab "Article properties" in the article detail menu). However, the standard procedure is to only transmit a brief description (= variant value). Therefore, you should avoid referencing the same component twice. |

NODE |
REQUIRED |
DESCRIPTION |
|
|---|---|---|---|
A_COMPONENTDATA |
Y |
XML |
Article components |
A_COMPONENT |
N |
CHAR(255) |
Definition of each article component |
A_COMPONENT[identifier] |
N |
ENUM |
Indicator for referencing (key or name) |
A_COMPONENT[key] |
N |
CHAR(50) |
Value stored in the identifier assignment statement |
A_COMPONENT[name] |
Y |
CHAR(100) |
Value stored in the identifier assignment statement |
VALUE |
Y |
TEXT |
Contains the component value in the indicated language (see below) |
VALUE[xml:lang="Sprache"] |
Y |
ISO language code/"x-default" |
Defines the component value's language. "x-default" references the default language configured in TB.One |
EXAMPLE:
or
|
For further information, see also:
▪Master data import via XML - overview
▪XML structure overview - TB.Cat 1.4
▪XML structure overview - TB.Cat 1.2/1.3
▪Examples: XML for TB.Cat 1.4 or TB.Cat 1.2/1.3