powered by CADENAS

Manual

Manual

5.15.2.1. Catalog update - Example 1

When using an ERP integration datasets are assigned to a certain project line (project path + LineID) in the LinkDB.

At catalog updates it could happen, that not all LinkDB links are found for each product (just because of changes).

[Note] Note

The example in hand is a "Worst case" scenario. It exemplifies only all possible change cases - no "normal", "good" projects. It can be used as a tutorial to getting started with the subject "Catalog update".

You can find sample files in your installation under $CADENAS\training\update_manager\catalog_update_v1(and v2).cip.

The projects cover the following cases:

project.prj Standard name (NB) adjusted Automatic mapping is possible (see Section 5.15.2.1.6.1, “ Update manager - Assign projects after mapping automatically processed before”)
project2.prj Directory relocated Automatic mapping is possible (see Section 5.15.2.1.6.1, “ Update manager - Assign projects after mapping automatically processed before”)
project3.prj Project and Standard number (NN) renamed No automatic mapping is possible (see Section 5.15.2.1.6.2, “ Update manager - Assign projects without preceding mapping”)
project4.prj Directory relocated and Standard name (NB) adjusted

Automatic mapping is possible (see Section 5.15.2.1.6.1, “ Update manager - Assign projects after mapping automatically processed before”)

project5.prj Project and Standard number (NN) renamed and Standard name adjusted No automatic mapping is possible (see Section 5.15.2.1.6.2, “ Update manager - Assign projects without preceding mapping”)
project6.prj Project and Standard number (NN) renamed and directory relocated No automatic mapping is possible (see Section 5.15.2.1.6.2, “ Update manager - Assign projects without preceding mapping”)
project7.prj Project and Standard number (NN) renamed, directory relocated and Standard name adjusted No automatic mapping is possible (see Section 5.15.2.1.6.2, “ Update manager - Assign projects without preceding mapping”)

Reasons for catalog changes may be:

  • Product changes

    • Products delisted

    • Products replaced

    • Replacement of product values

    • New products added

  • Maintenance

    • Modeling errors

    • Adjustments of labels & names

    • Changes in structure

    • Adjustment of table values

In order to be able to optimally use the explanations in the sense of a tutorial, please install a base catalog first. On this see the following section Section 5.15.2.1.1, “Preparations”.

Under Section 5.15.2.1.3, “Assignment / release – Overview on the best approaches” you will get an overview.