4.16.3.  Catalog update with ERP integration - Fix mapping problems with the Update manager
4.16.3.2. Catalog update (Tutorial) - Example 2
Prev  Next

4.16.3.2. Catalog update (Tutorial) - Example 2

4.16.3.2.1. Preparations
4.16.3.2.2. Catalog update - Download
4.16.3.2.3. Assignment / release – Overview on the best approaches
4.16.3.2.4. PARTadmin - Check | Compare | Install
4.16.3.2.5. PARTlinkManager
4.16.3.2.6. Update manager - Project assignment to LinkDB datasets
4.16.3.2.6.1. Update manager - Projects with simple process of assignment
4.16.3.2.6.1.1. Assign project.prj (Standard name adjusted)
4.16.3.2.6.1.2. Assign project2.prj (Adjusted directory)
4.16.3.2.6.1.3. Assign project4.prj (directory relocated and Standard name adjusted)
4.16.3.2.6.2. Update manager - Projects with more complex process of assignment
4.16.3.2.6.2.1. Assign project3.prj (project and Standard number renamed)
4.16.3.2.6.2.2. Assign project5.prj
4.16.3.2.6.2.3. Assign project6.prj
4.16.3.2.6.2.4. Assign project7.prj
4.16.3.2.6.3. Final check

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 (because of changes).

[Note]Note

This example 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) adjustedAutomatic mapping is possible (see Section 4.16.3.2.6.1, “ Update manager - Projects with simple process of assignment”)
project2.prj Directory relocatedAutomatic mapping is possible (see Section 4.16.3.2.6.1, “ Update manager - Projects with simple process of assignment”)
project3.prj Project and Standard number (NN) renamedAutomatic mapping is possible (see Section 4.16.3.2.6.2, “ Update manager - Projects with more complex process of assignment”)
project4.prj Directory relocated and Standard name (NB) adjusted

Automatic mapping is possible (see Section 4.16.3.2.6.1, “ Update manager - Projects with simple process of assignment”)

project5.prj Project and Standard number (NN) renamed and Standard name adjustedAutomatic mapping is possible (see Section 4.16.3.2.6.2, “ Update manager - Projects with more complex process of assignment”)
project6.prj Project and Standard number (NN) renamed and directory relocatedAutomatic mapping is possible (see Section 4.16.3.2.6.2, “ Update manager - Projects with more complex process of assignment”)
project7.prj Project and Standard number (NN) renamed, directory relocated and Standard name adjustedAutomatic mapping is possible (see Section 4.16.3.2.6.2, “ Update manager - Projects with more complex process of assignment”)

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 4.16.3.2.1, “Preparations”.

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

Prev Up Next
4.16.3.1.3. Editing in Update manager  Home 4.16.3.2.1. Preparations