Manual

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

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 8.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

Update manager

In the Update manager you can see all projects, project lines, variables and values at a glance.

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 "Worst case" scenario. It exemplifies only all possible change cases - no "normal, "good" projects.

	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.

Prev	Up	Next
4.16.2. Standard check on problems with mapping LinkDB entries	Home	4.16.3.1. Catalog update (Tutorial) - Example 1

Manual

Login

Top Links

Manual

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