How does the initial provision of a product database work?

This document describes the initialization of a product database that is made available by an organization to underlying companies. A product database is a separate supply of product information, outside of the normal organization's products. Companies can subscribe to one or more product databases, provided they have sufficient licenses for them. Each product database requires a database CAL (Client Access License).

From company 2, Administration, Product databases, a new database can be created. A code can be specified when creating a new database. This code must correspond to the file import software.

Information can be given as a free text as an explanation of the database.

By marking the checkbox 'Headquarters database', preparation is made for importing a database at the organization level. Underlying companies cannot subscribe to such a database, it is simply read at the organization level and the products are automatically available to everyone.

With 'Purchase supplier mode', it can be indicated which supplier will ultimately be included in the purchase information of an imported product. The following choices are possible:

- Use supplier from product file: The supplier as mentioned in the product database file is transferred to the purchase information.

- Use supplier specified here: The supplier specified in this screen is transferred as the supplier in the purchase information from the product database file.

- Use both suppliers: Both the supplier mentioned in the product database file and the supplier specified here will be transferred to the purchasing information. This will always result in the existence of 2 purchasing data.

With 'Preferred supplier mode', it can be indicated how the determination of the preferred supplier for a product should take place. The following choices are possible:

Product data itself will only be updated if the change comes from the preferred supplier or if the 'Preferred supplier mode' setting leads to the supplier becoming preferred.

A provided sales price from a supplier that is not preferred or allowed to be preferred will not be updated. If the product has an active purchasing data from the DA Retail Group, it means that the product data is managed by the BOD set. In that case, product mutations are not transferred, except for the preferred supplier property.

- Apply default processing: RetailVista has a fairly extensive algorithm for determining the preferred supplier. This also depends on various settings and is described separately in QA xxx.

- Transfer supplier from product file: The preferred supplier of an imported product is adjusted to the supplier specified in the product database file for the purchasing information.

- Convert to specified supplier: The preferred supplier of an imported product is adjusted to the supplier specified in this screen.

The last input field 'Supplier' is the supplier that should be applied in the previous 2 choice fields. Depending on the above choices, this field may or may not be available.

Note: If a setting regarding supplier or preferred supplier is changed, it will not result in a mutation on the existing products. The settings will be applied to the next import processing.

Major changes such as a new source should always be tested in the designated test environment(s) beforehand.