powered by CADENAS

Manual

Manual

4.16.3.  Catalog update with ERP integration - Fix mapping problems with the Update manager

4.16.3.1. Catalog update (Tutorial) - Example 1
4.16.3.1.1. Preparation
4.16.3.1.2. Status after update installation to Bikecompany V2 and before editing with Update Manager
4.16.3.1.3. Editing in Update manager
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
4.16.3.3. Install update version
4.16.3.3.1. Update without connection to the LinkDB
4.16.3.3.2. Correct version numbers
4.16.3.3.3. Update structure table
4.16.3.4. User interface of Update Manager
4.16.3.4.1. Symbols in the Catalogs section
4.16.3.4.2. Symbols in the Line mapping section
4.16.3.5. Functions
4.16.3.5.1. Active State and Requested State
4.16.3.5.2. Changed standard name
4.16.3.5.3. Moved dataset
4.16.3.5.4. No correlation to the old dataset found
4.16.3.5.5. Conduct assignments across lines
4.16.3.6. Catalog update with ERP integration - Check LinkDB mapping problems BEFORE installation (table and 3D view)
4.16.3.7. Background information
4.16.3.8. Configuration file plinkupdatemgr.cfg
4.16.3.8.1. Block [WORKFLOW]
4.16.3.8.1.1. Key "CUSTOMUPDATESCRIPT"

[Note] Note

Up to now a customer administrator had to perform a mapping for LinkDB datasets at each catalog update with the Update manager, if projects or variables had been changed, which led to lots of effort on the customer side and less upgrades to latest catalogs.

In order to relieve the customer side, as of V10, mapping information is integrated directly into the catalog. That means these tasks are now done by the modeller of the catalog before it is published. Only in exceptional cases the mapping has to be performed on customer side.

On this please see under Section 6.10, “ Add ERP-Mapping... / Edit ERP-Mapping... ” in eCATALOGsolutions Manual.

For catalog status which are not yet prepared for automatic mapping, the Update manager is still used if assignment problems occur.

Why using the Update Manager?

When an ERP integration is used, every dataset in the link database is assigned to a specific project line (project path + LineID) in the characteristic attribute table.

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

Reasons for catalog changes may be:

  • Product changes

    • Products delisted

    • Products replaced

    • Replacement of product values

    • New products added

  • Maintenance

    • Error in modeling

    • Adjustments in label & name

    • Structural changes

    • Table values corrected

Update manager

Update manager

In the Update manager, you can see all projects, project lines, variables and values at a glance. Under Information -> Geometrical similarity you can recognize geometrical part changes.

On the left you can select individual projects and lines in the directory structure. On the right you can see the current mapping. With a click on the respective icon you can confirm or revoke assignments.

The status for ACTIVE_STATE and REQUESTED_STATE is automatically set anew and different functions enable quick editing of the questionable links.

With the help of two examples the editing procedure with the Update manager shall be illustrated.

  • Catalog update - Example 1

    Example 1 is a little bit more detailed in its explanations as example 2, but does not contain all possible change cases.

  • Catalog update - Example 2

    Example 2 is a "Worst case" scenario. It exemplifies only all possible change cases - no "normal, "good" projects.