powered by CADENAS


Manual  Add ERP-Mapping... and Edit ERP-Mapping... (catalog modeling)

Which steps are necessary beginning from the creation of a mapping and the catalog publishing with the included mapping information up to the installation at the customer?

  1. Initial situation: Finalized SVN status (ready for publishing, everything checked in)

    Finalized SVN status

    Finalized SVN status

  2. In PARTproject, on the catalog root directory, call the context menu. Under Publication, click on the Add ERP-Mapping... command.

    -> The dialog box Add ERP mapping is displayed.

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

    • Search for a published catalog version

      Catalog modeling is based on SVN so this is the standard approach. However, only catalog status as of November 2014 are valid, older ones are hidden. In that case use the variant Load CIP file.

      • Other catalog:

        This option is especially used for Standard catalogs. Use case: Standards is published, the mapping has been made for DIN. That's why the function can be called for the DIN folder. Select Standards under Other catalog and DIN as directory.

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

    This option only fits for catalogs which have an order number. Advantage: With an unique ID the mapping should automatically be created in any case.

    Finally click on OK.

    -> The mapping is created and the protocol displayed.

    [Note] Note

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

  4. In PARTproject, on the catalog root directory, call up the context menu. Under Publication, click on the command Edit ERP-Mapping....

    [Note] Note

    If you are not quite sure whether the existing mapping is up-to-date, then it makes sense to execute the command Add ERP-Mapping... again before executing the command Edit ERP-Mapping....

    -> If several mappings had been created, the dialog box Select source version opens. Here, select which mapping you want to edit.

    [Note] Note

    Releases not needed anymore can be removed from the current work status (saved in mapping.json) with the command Cleanup ERP mappings.

    Cleanup ERP mappings

    Cleanup ERP mappings

    Confirm with OK.

    -> The dialog box Edit ERP mapping opens.

    Edit ERP mapping

    Edit ERP mapping

  5. Edit all assignments which are not unique.

    At projects not showing icons, in the directory tree, the assignment has automatically been performed. No manual editing of the mapping is needed here. In the directory tree simply use the context menu command Verify all mappings for the respective directory level.

    At projects showing icons an ERP mapping has to be created, at projects without icon the mapping has automatically been created.

    At projects showing icons an ERP mapping has to be created, at projects without icon the mapping has automatically been created.

    [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 a green checkmark is displayed, at the catalog, at all directories, projects and project lines.

    [Note] Note

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

    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.[52] All mapping information is included[53] and will be processed at the catalog installation.

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

[53] in the file "mapping.json"