powered by CADENAS



3.4.2.  Add ERP-Mapping... / Edit ERP-Mapping...

[Note] Note

The topics and rules in this document don't have to be considered during the first catalog creation. But they become very important when the catalog has already been published and some users already have potentially integrated it into their ERP systems.

Background information

Several of the CADENAS catalogs are also used in connection with an ERP system. In this case the parts of the catalogs were linked to the existing datasets of the customer’s inventory control system. If this is performed the first time, this procedure is also called “ERP initial load”.

As resource for the initial load, usually the latest CIP catalog, released by supplier is used. This CIP catalog is delivered on DVD together with the software. Even more up to date they are also available via PARTadmin -> Catalog update -> Online (see Section, “ Catalog update Online ” in PARTsolutions / PARTcommunity4Enterprise - Administration Manual).

Once a catalog was installed into an ERP environment, numerous links and technical references were created. But often the catalog is extended at the same time, what means there were new products added, changed or removed by the decision of the supplier. Sometimes this affects only one size, but this also causes at least a table change. Also the supplier can change the whole folder structure because in the course of time new chapters and part families result and the structure must be adjusted e.g. to the Print catalog appearance.

At the end of all these changes the catalog will appear again as update on the above mentioned platforms and the end-user can install the new CIP catalog version on his environment. And he of course should do this, because also mistakes in the catalog data are resolved continuously.

In order not to lose the mentioned links and references during a catalog update in an already installed ERP system, several points have to be considered preventively by the catalog creator. These are explained in this section.

Since eCATALOGsolutions V10 SP2 it is required to perform an ERP mapping check each time before a catalog is generated. With this procedure we additionally ensure, that this guideline Is kept and we are able to provide information about changed, reorganized and removed projects during a CIP updated to the PART solutions end customer. You can find all details about it documented under Section 6.10, “ Add ERP-Mapping... / Edit ERP-Mapping... ”.