 |
Projects (that once have been a part of a published CIP for PARTsolutions) should never be deleted again. Of course projects can be officially rejected by the supplier at times, however, in this case the End-of-Life feature should be used and not the project be deleted.
![[Note]](https://webapi.partcommunity.com/service/help/latest/pages/cn/partwarehouse/doc/images/note.png) | Note |
|---|---|
If projects have been created as real duplicates several times in the past, TestMeta will show an error, because CNSORDERNO/CNSTYPCODE has to be mandatorily declared, however, is not unique. In order to correct this error, replace duplicates by link projects. If a link project shall not cover all rows, you can use filters. On this see Section 5.8.2.1.3, “ New link ” (subitem Restricted Display and Restricted Display in value ranges). Before publishing, please perform Edit ERP-Mapping... (see Section 6.10.2, “ Check ERP-Mapping (Add ERP-Mapping... and Edit ERP-Mapping...) ”). ERP mapping will check, if a project is still available. With activated option Use order numbers to create mappings, a new project will be found and mapped without problems.
Link projects doesn't matter for ERP mapping, only physical. | |
Details on End-of-Life feature can be found under Section 5.9.2.12, “Menu item Expiration date (End of Life) ”.
If a project has been deleted, see Section 6.10.2.4.5, “Deleted project”.