Difference between revisions of "Product update"
(→Catalogue System V2 and later versions) |
|||
| Line 16: | Line 16: | ||
Updating a product may or may not cause a new product version to be created. | Updating a product may or may not cause a new product version to be created. | ||
| − | This will all depend on the | + | This will all depend on the Catalogue Import Configuration File settings. |
Effectively some fields have business impact, therefore it should not be possible to edit them without buyer approval | Effectively some fields have business impact, therefore it should not be possible to edit them without buyer approval | ||
On the other hand, some attributes do not need any approval so a change in those can overwrite previous data. | On the other hand, some attributes do not need any approval so a change in those can overwrite previous data. | ||
Latest revision as of 10:01, 28 April 2015
Catalogue System V1[edit]
On CAT V1 it is not possible to update products attributes. Only product prices can be updated : see Product Price Update All other product attributes cannot be updated In case you want to update a catalog, please apply the work-around below :
- Supplier should contact the buying company purchasing department so they can inactivate the existing catalogue. See Imported products
- Then supplier must import the modified catalogue, into a new catalogue, for ex with Vx+1 at the end of naming.
- Purchasing department will have to activate the products and assign all AOs again. See Imported products
Catalogue System V2 and later versions[edit]
Starting with V2 it will be possible to update a catalogue. By updating a catalogue is meant:
- Adding new products to an existing catalogue
- Updating existing products attributes
Updating a product may or may not cause a new product version to be created. This will all depend on the Catalogue Import Configuration File settings. Effectively some fields have business impact, therefore it should not be possible to edit them without buyer approval On the other hand, some attributes do not need any approval so a change in those can overwrite previous data. All this can be best summed up as below:
- If the existing product version is ACTIVE or PENDING, AND a change is made to at least one fields marked as "ChangeCauseNewVersion=Y" in configuration file
- => A new product version is created, it is inactive and will have to be activated (approved) by buyer. On activation the previous version is automatically inactivated
- In other cases : product is overwritten (change is somehow tracked in audit trail)
