3.4.2.
Check ERP mapping
(Add ERP mapping... and Edit ERP mapping...)
3.4.2.2.
Deletion of projects
|  |
| Prev | Next |
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/en/3dfindit/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. This error can be corrected by replacing the duplicates with link projects. If a link project is not valid for all rows, filters can be used. See Section 5.8.2.1.3, “ New link ” (sub-items Table restriction [Restricted display] and Table restriction [Restricted display] in value ranges ). Before republishing, ERP mapping [Edit ERP-Mapping...] must be edited. [Edit ERP-Mapping...].. (see Section 6.10.2, “ Check ERP mapping (Add ERP mapping... and Edit ERP mapping...) ”..) must be carried out. ERP mapping checks whether a project still exists. If the Perform mapping via order number [Use order numbers to create mappings] option is activated, a new project is found and mapped without any problems.
Link projects do not play a role in ERP mapping, only physical ones. | |
Details on the end-of-life feature can be found under Section 5.9.2.12, “Menu item: Expiry date (End of Life) ”.
If a project has been deleted, see Section 6.10.2.4.5, “Deleted project”.