English
Deutsch
Español
Français
Hrvatski
Italiano
Polski
Türkçe
Русский
中文
日本語
한국어
Legal notice
powered by CADENAS

Manual

Top Links

Manual

6.10.2.1. Workflow
6.10.2.1.1.  Check ERP-Mapping (Add ERP-Mapping... and Edit ERP-Mapping...) [catalog modeling]
Prev   Next
6.10.2.1.1.  Check ERP-Mapping (Add ERP-Mapping... and Edit ERP-Mapping...) [catalog modeling]
[Note] Note

When performing an ERP mapping it's always about to create 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] 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 dialog Check ERP-Mapping is automatically opened if a new mapping is required (see below).

    • E.g.: Removed row, removed variable, changed variable

    • Acts as help / reminder to create / update a mapping (can be skipped)

    • Perform the function and verify the mapping in the dialog Edit ERP mapping for source catalog from .... (Mappings showing an icon have to be verified, mappings without not.)

    • Upload 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 dialog Update table versions is opened.

    Normally you should confirm with Yes.

  • The mapping.json file is not locked so that several users may modify the file. When uploading on the server different entries (related to different projects) are merged. So different users can work on the catalog at the same time and also update the mapping.

In the following the standard mapping workflow is described.

  1. Upload changed files in directories / projects to the server: In the course of uploading files the necessity of mapping (or updating the table version with the mapping) is checked.

    -> The dialog box Send changes to the server is opened where all changed files are listed.

    Dialog "Send changes to the server"

    Dialog "Send changes to the server"

  2. Enter a comment and confirm with OK.

    -> The dialog Check ERP-Mapping is opened.

  3. Either select the option Search for a published catalog version or Load CIP file.

    • 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 catalog status as of November 2014 are valid, older ones are hidden. In that case use the variant Load CIP file.

      Click on Search.

      -> All published catalog versions are listed.

      Select the most current version.

      [Note] Note

      Normally you should always use the most current version. Selecting older mappings makes only sense for research purposes.

      • Other catalog:

        • This option is especially used for Standard catalogs. Use case: Standards is published, however, the mapping has been created for DIN. So under Other catalog select Standards and under Directory select DIN.

        • 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.

    • Use order numbers to create mappings: See below.

    [Note] Note

    At larger catalogs or bad network connectivity the mapping may last a little bit longer (about 1-2 hours).

  4. Now you have different options:

    • Execute ERP-Mapping for the whole catalog -> Click on Execute.

    • Execute ERP-Mapping for projects which are modified and selected for check-in -> Click on Execute.

    • Proceed without executing 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 will be uploaded -> Click on Cancel.

    When clicking Execute the dialog box Create ERP-mapping is opened and then without any further interaction immediately afterwards the dialog box Edit ERP mapping for the source catalog from ....

    What happens in the background after clicking on Execute?

    The software attempts to map the source projects (of selected 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. When executing the command anew the existing release mapping is updated. If the mapping has already been verified (in the dialog Edit ERP mapping for source catalog from ...) and the table version is unchanged, the mapping is kept. Not verified mappings will be overwritten. Mappings with new changes are added.

    [Note] Note

    ERP mappings consider everything, even if the Remove publication mark is set or if projects are hidden.

    Dialog "Create ERP-mapping" with protocol

    Dialog "Create ERP-mapping" with protocol

    Edit ERP mapping for the source catalog from ...

    Edit ERP mapping for the source catalog from ...

  5. Edit (verify) all assignment which are not unique.

    Index tree:

    [Note] 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

    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] Note

      Projects without icon do not have to be verified!

      Verified folder containing projects with and without 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] 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] Note

    Publishing with not confirmed assignments (invalid mappings) is not allowed.

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

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


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

[67] 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