Why ERP mapping has to be performed at all?

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. ^[65]

In order to relieve the customer side, as of V10, mapping information is created in the SVN catalog status and during publishing integrated in the CIP file so that it can be processed during the installation. That means, mapping tasks are now done by the catalog modeller and don't have to be conducted on the customer side at each update.

Note

For each new catalog release ERP mappings have to be created by the modeling in PARTproject. Publishing without this mapping information is not possible. Once under context menu command Versioning system, executing the command Upload changed files in directories / projects to the server, automatically the dialog box Check ERP-Mapping is opened. Click on Search to load published catalog versions, select one and under Execute ERP-Mapping for the whole catalog or Execute ERP-Mapping for changed projects, click on Execute. Just as well under context menu command Publication, you can use the commands Add ERP-Mapping... and Edit ERP-Mapping.... 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:

At catalog xy the latest status is from 01/01/2015 and still without mappings. A customer with V10 has exactly this catalog status.

Now a new version is released on 06/01/2015. In this, the modeling has already added the mapping information, namely at the last released status from 01/01/2015.

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