A small example shall illustrate the necessity: When performing changes in a catalog's follow-up version it could be, for example that a project was split into two. If on customer side, just the new catalog version would be installed, related ERP numbers could not be assigned anymore, because the corresponding project is missing. However, if a mapping is created, this information is available during the installation and the ERP numbers can be correctly assigned to the new projects again.

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

To reduce the workload on the customer side, mapping information can be created in the SVN catalog status from V10 and included in the CIP file when publishing. This information is then processed automatically during installation. This means that the task of mapping is now taken over by the catalog modeling and no longer has to be carried out on the customer side with each update.

Note

For each new catalog release, the ERP mappings must be entered in PARTproject from the modeling. Publishing without this mapping information is not possible. As soon as the command Upload changed files in directories/projects to the server [Upload changed files in directories / projects to the server] is executed under Context menu command Version management [Versioning system], the dialog box Check ERP mapping [Check ERP-Mapping] opens automatically. Click on Search to load the published catalog versions, select the most recent one and click on Execute under Execute ERP mapping for the entire catalog [Execute ERP-Mapping for the whole catalog] or Execute ERP mapping for changed projects [Execute ERP-Mapping for changed projects]. (Alternatively, you can also use the context menu commands Add [Add ERP-Mapping...] ERP mapping... and Edit ERP mapping [Edit ERP-Mapping...]... can also be used) Details on this can be found in the following sections.

Precondition on customer side

On customer side, a version has to be installed for which mappings have been created.

Now the new method takes effect and manual editing is only necessary in exceptional cases, if an adjustment cannot be processed automatically.

Example:

The latest version of a catalog from the beginning of the year is still without mappings. A customer with V10 has exactly this catalog version.

A new version will now be published in the middle of the year. In this version, the modeling has already entered mappings for the last published version from the beginning of the year.

When the customer installs the latest status now, these mappings are automatically processed.