Appendix A: Setting Parent/Variants
Adding of Free fields (features/attributes):
In Profit you open the General -> Management tool. Next you open the function group Item.
In this screen you find the already defined fields on the item. As here displayed on the image:
In this menu at least 3 extra free fields must be added. One field to indicate whether a product is a configurable product and one field to indicate to which configurable product the item belongs to. The third (and fourth, fifth, etcetera) free field is an attribute to which the product is variable. For example, the colour of a shirt, or the size of a shoe.
The first field must be a Yes / No field and the second field must be an association with a fixed Table, namely Items. The third field does not have specific requirements, other than that this must be at least one. A configurable product without attributes is not possible.
When these are added this will look something like this:
Filling attributes per product:
With configurable products you have 2 types of products for the creation of products creating products. You have the physical product, for example, the red T-shirt in size 38. And the (what we call) the display product, this display T-shirt does not really exist as a physical product but is actually a container for all colors and sizes of this model . This display T-shirt also has no stock, but for a integration it is essential as an existing product.
The two types must be completed in the same way as the example below. Of course there are many types of configurable products, but the essence is always the same, you have 1 container item and 1 physical item. In the image below you first see the container article with the checkmark "Conf.Artikel" (is product configurable) checked.
And with the second article you will see the reference to the container in the field "Hoofdartikel" (reference to main product). And the second article also contains a value for the third free field, in this case ‘Kleur’ (colour). Notice also, that the features are only filled out in the main product, since these values are the same for all variants.
This is also how AFAS should be set up to support Configurable products.
Configuring in ApiCenter
When the AFAS environment has been fully populated with data described above, it is time to set ApiCenter to the correct configuration, to load in variant products and their parents.
First; you will need to specify which attribute is mapped to which attribute in the secondary application. Remember, an attribute is what makes a product unique, like size and colour for example. Do not include features in this mapping table.
Secondly; you need to define the features of a product. Remember a feature is what all variants of a model share, like the material the product was made from, or the country of manufacture for example.