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

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.

	Note
	For each new catalog release ERP mappings have to be created by the modeling in PARTproject. Publishing without these mapping information is not possible.

First catalog update with V10

At the first catalog update with V10 the updates still have to be manually performed (with the Update Manager), but from then on this will only be necessary in exceptional cases where an automatic assignment is not possible.

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.

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.

Add ERP-Mapping... and Edit ERP-Mapping...

UI of the dialog box Edit release mapping

Edit release mapping

The UI is subdivided in index tree on the left side and table with functions on the right side.

Icons in index tree

In the index tree you can see at a glance which projects have automatically been mapped (these do not show icons) and which projects have to be edited manually.

Bitmap	Meaning
	Changes existing These have to be edited and confirmed manually.
	Project deleted, but still not confirmed
	Confirmed (regardless of whether assigned or removed)

Icons in the table

Bitmap	Meaning
	Changes exist These have to be edited and confirmed manually.
	Line removed. The change has to be confirmed.
	This assignment has been confirmed by the modeler
	This line is expired. This was confirmed by the editor

Tooltips in the table

When moving the mouse over the icons tooltips are displayed.

Tooltip

Functions

Bitmap	Meaning
	Add target project or Add condition On this see ???.
	Generate algorithm matching the selected line and copy it to clipboard
	Under : Remove target project Under Table: Revoke the mapping to this project
	Function: Map this project to the currently selected line This function is only active if the assignment has been removed in the table via . Table: Currently mapped line
	Open project: When clicking on the icon the respective project is selected in PARTproject.
	Verify all mappings or Approve assignment Note Furthermore, in the index tree, you can find the context menu command Verify all mappings.

For complex mappings such as resolving value range variables (yellow fields) into fixed variables you can use algorithms based on Fortran code. On this see splitinto2.prj.

Examples

Note

The examples can be found in the SVN, in the catalog "training -> catalog_update_erp_mapping" or in your PARTsolutions installation under $CADENAS/training/catalog_update_erp_mapping. Locally install version2.cip and copy the root directory in a "test" SVN environment. Then under Publication -> Add ERP-Mapping... -> Load CIP file select version1.cip. folder1 -> addremovewb Remove value range variables and add new ones folder1 -> datowb Combine lines with the help of value range variables folder1 -> davarrenamed Rename fixed variables older1 -> lineswap Line swap (Line ID) folder1 -> precchanged Change precision of variables folder1 -> wbvarrenamed Rename value range variables folder2 -> torename/toremove Rename project folder3 -> splitinto2 Resolve value range variable into 2 projects with fixed variable. folder4 -> merge_a folder4 -> merge_b Combine 2 projects (tables) in one

Examples with manual assignment

	Note
	Projects to be edited are displayed in the index tree with meaningful icons.

Examples with automatic assignment

	Note
	At projects which do not show any icons in the index tree assignments have been automatically performed.