Manuals - 3Dfindit

6.10.2.1. Workflow

6.10.2.1.1. Check ERP mapping (Add ERP mapping... and Edit ERP mapping...) [Catalog modeling]

	Note
ERP mapping is always about creating a mapping between the local work status (potential LIVE status) and an already published status. Thus the first LIVE publishing does not require a mapping.

Note

ERP mapping is always about creating a mapping between the local work status (potential LIVE status) and an already published status.

Thus the first LIVE publishing does not require a mapping.

	Note
	Always add a mapping or update a mapping when uploading modified catalog data. Normally you should upload modified catalog data into the SVN, when a task is finished before starting a new task. The Check ERP mapping [Check ERP-Mapping] dialog opens automatically (see below) if a new mapping is required: E.g.: Removed row, removed variable, changed variable Acts as help / reminder to create / update a mapping (can be skipped) Execute the function and verify the mapping on the ERP mapping dialog page for the source catalog from ... edit. (Mappings with an icon must be verified, mappings without do not) Check in the files together with the updated mapping (`mapping.json`). -> In this way the mapping should always be up-to-date. If only a new table row has been added and the project is already part of a mapping, then the standard process for adding a mapping does not appear. However, because hereby the table version changed it has to be updated within the mapping, because otherwise the server won't accept the mapping for this table.. -> The Update table versions dialog opens. As a rule, you should confirm the dialog with Yes. The file `mapping.json` is not locked so that multiple users can modify the file. When uploading to the server, different entries (relating to different projects) are merged. Different users can therefore work on the catalog at the same time and also update the mapping.

In the following the standard mapping workflow is described.

Upload changed files in directories/projects to the server [Upload changed files in directories / projects to the server]: When uploading files, the necessity of mapping (or updating the table version in the mapping) is automatically checked.

-> The Changes to server [Send changes to the server] dialog box appears, where all changed files are listed.

Server changes [Send changes to the server] dialog
Enter an appropriate comment and confirm with OK.
-> The Check ERP mapping [Check ERP-Mapping] dialog opens.
Select either the Search published catalog status [Search for a published catalog version] option or the Load CIP file option.
- Search for published catalog status [Search for a published catalog version] (standard variant )
  Catalog modeling is based on SVN so that the standard variant is the one to prefer.
  However, only versions from November 2014 onwards are valid, older versions are hidden. In this case, use the Load CIP file variant.
  Click on Search.
  -> All published catalog versions are listed.
  Select the most current version.
  
  Note
  Normally you should always use the most current version. Selecting older mappings makes only sense for research purposes.
  - Other catalog:
    This option is mainly used for the standards catalogs. Use case: You publish Norm, but make the mapping for DIN. Select Norm under Other catalog and DIN under Directory.
    Other use case:
    If the supplier changed the catalog name for some reason (e.g. at first catalog modeled by standard, then Quick&Simple catalog)
    In this case for the first mapping another catalog name has been used.
- Load CIP file
  If the last catalog status is before November 2014, the mapping can be created with the help of a CIP file. At this variant the mapping is not verified during publishing.
- Carry out assignment via order number [Use order numbers to create mappings]: See below.
Note
Creating the mapping can take a little longer with larger catalogs and/or poor network connections (approx. 1-2 hours).
Now you have different options:
- Perform ERP mapping for the entire catalog [Execute ERP-Mapping for the whole catalog] -> Click on Perform [Execute].
- Perform ERP mapping for changed projects and projects selected for check-in [Execute ERP-Mapping for projects which are modified and selected for check-in] -> Click Perform [Execute].
- Continue without performing ERP mapping [Proceed without executing ERP-Mapping] -> Do not perform ERP mapping [Do not execute ERP-Mapping].
  (There already is a mapping or it will be performed later [see Section 6.10.2.1.3, “ Add ERP mapping... and Edit ERP mapping.. ”].)
- Cancel process. No files are uploaded [Cancel process. No files will be uploaded] -> Click Cancel.
After clicking on Execute, the Create ERP mapping [Create ERP-mapping] dialog box opens and the Edit ERP mapping for the source catalog from ... dialog box appears immediately afterwards without any further interaction.
What happens in the background after clicking on Execute?
The software attempts to map the source projects (of the selected published catalog version) to the target projects (of the local working copy). If a release mapping already exists and files have been changed since the last time, the mapping is created. If the mapping has already been verified (in the Edit ERP mapping for the source catalog from ... dialog) and the table version has not changed, the mapping is retained. Mappings that have not been verified are overwritten. Mappings with new changes are added.

Note
ERP mapping goes over everything, even if the Remove published flag [Remove publication mark] is set or if projects are hidden.

Create ERP mapping [Create ERP-mapping] dialog with protocol

Edit ERP mapping for the source catalog from ...

Edit (verify) all assignment which are not unique.

Index tree:

	Note
	All displayed directories and projects have been changed in some way. Unchanged projects (+tables) are not displayed.

Something in the project or in the table has changed which not necessarily means that there was a change relevant for the ERP mapping. For changes not relevant for the ERP mapping no icon is displayed.

Index tree with projects with and without icon

No icon:

A target project/row has been automatically found and the changes are quite minimal, so there is no need for the user to confirm the mapping. Possible reasons are:
- Renamed variable (with unchanged values)
- Changed project name (with unchanged values)
Value range: Mappings referring to a value range are always displayed (with or without icon).
- Without icon:
  At least for one row an exact accordance could be found. As the software cannot test all combinations of value range values (endless), it may be that values have still changed. That's why the value range has to be checked manually, nevertheless.
- With icon:
  If a relevant change of value range is found, an icon is displayed.

Note

Projects without an icon do not need to be verified! icon

Verified folder containing projects with and without icon

Always check value ranges carefully.

With icon:
- Exclamation mark : A possible target has been found, but the mapping cannot be confirmed automatically. That means, due to changes the modeler either has to verify the proposed mapping or to map another target. For example, here it could be that the NB differs due to a change of a variable value.
- X (and exclamation mark) : No target has been found. Here, the user has to interact as well and either confirm that the respective line does not exist anymore (meaning to verify) or assign something different.
- X and checkmark) : There is no target. Mapping has been verified by user (display only on line level). The project shows a checkmark.
- Checkmark : Mapping has been verified.
Icons signalize that there is at least one row where it applies to.
Also have a look on the respective tooltip. At mouseover a tooltip explaining the icon is displayed.
On row level the tooltips are still more detailed. For example, there they show that the NB has been changed (old and new are displayed). So it becomes clear why a specific icon is displayed.

Caution

There are seldom cases where an automatic assignment of ERP numbers is performed, which however, is not correct.

This can happen in the following cases:

At value range changes, in theory, an endless number of possibilities (step range) would have to be tried out, which is not practical. That's why only 3 possibilities are checked per value range: Starting value, middle value and maximal value. So an assigned ERP number could fall onto a wrong value.
Changes of units are not considered.

Once all assignments are confirmed, the catalog, directories, projects and project rows will show a green checkmark. (Projects without icon will be displayed without further on.)

Note

Publishing with unconfirmed assignments (invalid mappings) is not permitted.

The mappings have to be already available in the QA status! The generation is still processed, but when publishing an error message is displayed.

Once everything is assigned you can publish the catalog.^[67] All mapping information is included^[68] and will be processed at the catalog installation.

^[67]Detailed information on publishing can be found under Section 6.10, “ Publish catalog ”.

^[68]in the file "mapping.json"

Prev	Up	Next
6.10.2.1. Workflow	Home	6.10.2.1.2. Use order numbers to create mappings