powered by CADENAS

Manual

Manual

5.15.2.  Catalog update with ERP integration - Update manager

5.15.2.1. Catalog update - Example 1
5.15.2.1.1. Preparations
5.15.2.1.2. Catalog update - Download
5.15.2.1.3. Assignment / release – Overview on the best approaches
5.15.2.1.4. PARTadmin - Check | Compare | Install
5.15.2.1.5. PARTlinkManager - Important notes on procedure
5.15.2.1.6. Update manager - Project assignment to LinkDB datasets
5.15.2.1.6.1. Update manager - Assign projects after mapping automatically processed before
5.15.2.1.6.1.1. Assign project.prj (Standard name adjusted)
5.15.2.1.6.1.2. Assign project2.prj (Adjusted directory)
5.15.2.1.6.1.3. Assign project4.prj (directory relocated and Standard name adjusted)
5.15.2.1.6.2. Update manager - Assign projects without preceding mapping
5.15.2.1.6.2.1. Assign project3.prj (project and Standard number renamed)
5.15.2.1.6.2.2. Assign project5.prj (project and Standard number renamed and Standard name adjusted)
5.15.2.1.6.2.3. Assign project6.prj and project7.prj
5.15.2.1.6.3. Final check
5.15.2.2. Catalog update - Example 2
5.15.2.2.1. Preparation
5.15.2.2.2. Status after update installation to Bikecompany V2 and before editing with Update Manager
5.15.2.2.3. Editing in Update manager
5.15.2.3. Install update version
5.15.2.3.1. Update without connection to the LinkDB
5.15.2.3.2. Correct version numbers
5.15.2.3.3. Update structure table
5.15.2.4. User interface of Update Manager
5.15.2.4.1. Symbols in the Catalogs section
5.15.2.4.2. Symbols in the Line mapping section
5.15.2.5. Functions
5.15.2.5.1. Active State and Requested State
5.15.2.5.2. Changed standard name
5.15.2.5.3. Moved dataset
5.15.2.5.4. No correlation to the old dataset found
5.15.2.5.5. Conduct assignments across lines
5.15.2.6. Background information

[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.9, “ Add ERP-Mapping... / Edit ERP-Mapping... ” in eCATALOGsolutions Manual.

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

At an PARTadmin Catalog update you are asked, whether you want the catalog to be checked before the installation for possible conflicts in the LinkDB. These can be solved by new assignment in the Update manager.

After click on the button Yes - Check Catalog the dialog box CIP Installation with the tabbed page Protocol is displayed. Here you will receive an overview how many datasets could be automatically updated successfully and how many would be to check and reassign and how many could not be automatically updated successfully.

On the tabbed pages ERP Status and PLM Status you get detailed information on project path and standard name.

Now you can decide, whether you want to install. If yes, click on the button Install selected catalogs.

After installation a note is displayed again, that you have to solve assignment conflicts in the Update manager.

In order to correct assignments, in PARTlinkManager, via Extras menu, call up the Update manager.

All variables, values and the table can be viewed at a glance.

The status for ACTIVE_STATE and REQUESTED_STATE is automatically adjusted and different functions allow quick editing of doubtful assignments.

Below are two examples:

  • Catalog update - Example 1

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

    [Tip] Tip

    If you like to learn the most important with minimal effort, then have a look on example 1; ideally reproduce it with the help of the enclosed sample catalogs.

  • Catalog update - Example 2

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

In the subsequent sections you can find all further details.