powered by CADENAS



6.10.  Add ERP-Mapping... / Edit ERP-Mapping...

Up to 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.[51]

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] 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 the 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.


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.

However, if the customer has an installed status from 10/01/2014 then therefor no mappings exist and if he installs the status from 06/01/2015 then he has to do the mapping himself (for this last time). However, parts which have not been changed between 10/01/2014 and 01/01/2015 can automatically be mapped.

[51] Hereto the Update manager is used. Call up via PARTlinkManager -> Extras menu -> Update manager. Details on this can be found under Section 4.16.3, “ Catalog update with ERP integration - Fix mapping problems with the Update manager ” in PARTsolutions / PARTcommunity4Enterprise - Administration Manual.