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

Manual

Top Links

Manual

6.10.2.  Check ERP-Mapping (Add ERP-Mapping... and Edit ERP-Mapping...)
6.10.2.5. ERP mapping: Questions -> Answers
Prev   Next

6.10.2.5. ERP mapping: Questions -> Answers

Q: Why ERP mapping has to be performed at all?
Q: On which versions the mapping is based?
Q: May an ERP mapping be performed during LIVE publishing?
Q: When an ERP mapping has to be added for partial publishing (context menu command Add ERP mapping for partial publication....)?
Q: Modeler has just confirmed the mappings without actually performing it - how this can be fixed?
Q: What happens when a variable used for ERP mapping gets deleted?
Q: What to keep in mind with regard to links?
Q: Which catalogs require an ERP mapping?
Q: Performing Edit ERP-Mapping...: is this a reliable method to check another person's ERP mapping (also as part of QA checks)?
Q: Some of problems with ERP mapping are difficult to reproduce - what's the best way to report them?
Q: Which role do files uploaded into the SVN trunk (Upload changed files in directories / projects to the server) play for QA publication?
Q: Where the mapping is saved?
Q: Can the file mapping.json be edited by several users at the same time?
Q: How can conflicts be avoided?
Q:

Why ERP mapping has to be performed at all?
A:

A small example shall illustrate the necessity: When performing changes in a catalog's follow-up version it could be, for example that a project was split into two. If on customer side, just the new catalog version would be installed, related ERP numbers could not be assigned anymore, because the corresponding project is missing. However, if a mapping is created, this information is available during the installation and the ERP numbers can be correctly assigned to the new projects again.
Q:

On which versions the mapping is based?
A:

  • Source version: The version selected in the dialog Add ERP mapping

    • SVN: The files are downloaded from the server (branch)

    • CIP: The CIP file is unpacked to the $CADENAS_DATA/ciptmp folder

  • Target version: Your local working copy in $CADENAS_DATA/23d-libs/catalogname
Q:

May an ERP mapping be performed during LIVE publishing?
A:

No. A new mapping is always created in relation to the last LIVE publication, however, this is not yet available.
Q:

When an ERP mapping has to be added for partial publishing (context menu command Add ERP mapping for partial publication....)?
A:

For a QA publication which only contains the locally modified files of the selected subfolder.

All other files are used from the last successful QA publication. In this way it is possible just to publish a subset of the locally modified files.

By running multiple partial publications before running a live publication you can ‚build‘ a certain desired live version. For example user1 partial publishes subfolder1, user2 partial publishes subfolder2 … etc.
Q:

Modeler has just confirmed the mappings without actually performing it - how this can be fixed?
A:

This can lead to problems during the installation of a catalog update.

  • The LIVE publication will work fine, because mapping exists

  • However, when the customer installs the update, possibly ERP numbers are mapped to wrong parts.

  • Solution: Create a new LIVE publication and for this two mappings:

    1. Create a mapping as usually (source version corresponds to the last available LIVE version)

    2. Delete the wrongly verified mapping from the mapping file (context menu command Cleanup previous ERP mappings...).

    3. Create a second mapping to the second last LIVE version.
Q:

What happens when a variable used for ERP mapping gets deleted?
A:

Mapping is based on a whole row. So not much happens... The user has to verify the mapping suggestion.
Q:

What to keep in mind with regard to links?
A:

Nothing, as links do not occur in the mapping. A link points to a real project. However, if the real project gets modified, this needs a mapping. So then also for the link project everything is ok.
Q:

Which catalogs require an ERP mapping?
A:

Only catalogs for which a CIP is created during the LIVE publication (checkbox in dialog). Catalogs without CIP do not have ERP numbers.

In PARTcommunity or 3dfind.it projects are simply modified. There are no ERP numbers - the only reason for ERP mapping.
Q:

Performing Edit ERP-Mapping...: is this a reliable method to check another person's ERP mapping (also as part of QA checks)?
A:

Yes, but following has to be considered:

ERP-Mapping is created using the local working copy of the catalog. So you should make sure that the local version of the catalog is the same (watch out for locally modified files / outdated files etc.)
Q:

Some of problems with ERP mapping are difficult to reproduce - what's the best way to report them?
A:

  • mapping.json

  • If possible do not keep on changing files (else it will be harder to check the problem)

  • What kind of changes were applied which lead to the problem with the mapping?

  • Do not use any workarounds when the publications fails (e.g. publishing without CIP to make the publishing work. Publishing without CIP will destroy the server data.
Q:

Which role do files uploaded into the SVN trunk (Upload changed files in directories / projects to the server) play for QA publication?
A:

Actually none, because the files of the local working copy are used.

(If it makes sense to check in the local files is another question.)
Q:

Where the mapping is saved?
A:

In the file mapping.json.
Q:

Can the file mapping.json be edited by several users at the same time?
A:

Yes, the file is not locked. To have status as current as possible, update your local file.
Q:

How can conflicts be avoided?
A:

  • Always download the latest version of the mapping.json file.

  • At best you should always perform mappings when checking in files, included the mapping.json file. In this way mappings should always be up-to-date and then a publication be possible without problems.

  • Check in changes in a timely manner (+ perform mapping for it). If e.g. a big change shall be performed, it could make sense, to process it in several little steps and to check in the changes after each partial step (+ create mapping and check in).
Prev  Up  Next
6.10.2.4.22. Renamed fixed variables  Home  6.10.3. Publication mark