Administration: Cleaning Duplicated Mapping Objects

Administrators can clean up duplicated mapping objects generated by the coexistence tools.

Mapping objects are identified as duplicated when they share the same context name, and have the same attribute value for V_SourceIdentifier (unique identifier of the non-3DEXPERIENCE object) or V_TargetIdentifier (unique identifier of the 3DEXPERIENCE object).

When duplicated mapping objects are identified, coexistence tools stop. The cleaning operation indicates them as quarantined so that they are no longer taken into account.

The cleaning operation automatically quarantines the appropriate ones if possible, based on the duplication issues identified. The mapping objects that could not be automatically quarantined are listed in a separate cleaning report where you can choose the ones you want to clean up.

Required access role: Administrator.

Before you begin: Access the CoexistenceAdministration Batch with the Batch Monitor. For more information, see Select the CoexistenceAdministration Batch.
  1. From the Mapping Operation list, select Clean Duplicate Mappings.
  2. In the Context Name box, select the context in which you want to clean the duplicated mapping objects.
  3. In the Report Directory box, enter the report directory where you want to generate the global report and the cleaning reports, or click .
  4. Optional: Click Preview to test the operation.

    This option ensures that the operation complies with the mapping operation rules. Only the reports are generated and the duplicated mapping objects are not cleaned up.

  5. Enter the other information for the global report and run the batch. For more information, see Run the CoexistenceAdministration Batch.
    The batch generates the two following cleaning reports in the directory you specified:
    • AutoCleanDuplicates.xml: Lists the duplicated mapping objects found and those that have been cleaned up for each set of mapping objects (OperationReport Status="Quarantine Successful").
    • UserCleanDuplicates.xml: Lists the duplicated mapping objects that could not be automatically cleaned up. Each DuplicateSet contains the different mapping objects that are identified as duplicated (MappingEntry).
  6. In the UserCleanDuplicates.xml file, specify which duplicated mapping object must be quarantined for each DuplicateSet by changing <Quarantine>NO</Quarantine> to <Quarantine>YES</Quarantine> for the appropriate mapping object (MappingEntry).

    Important: Only keep one mapping object per DuplicateSet by changing its value to <Quarantine>NO</Quarantine>.
    The RecommendedSolution tag provides recommendations about the appropriate mapping object to keep in the DuplicateSet. The following table lists the recommendations tags available with their meaning:
    Recommendation ID DuplicateMappingType Recommendation Details
    Recommendation #1 Collaborative space difference Multiple mapping objects are found across two or more collaborative spaces. Analyze the 3DEXPERIENCE object from the provided information, and choose only one mapping object corresponding to it for future coexistence.

    Mapping objects corresponding to a collaborative space with Public access rights might be the appropriate mapping object to keep.

    Mapping objects with a 3DEXPERIENCE object in the Released state are good candidates to be quarantined, as these objects are generally not used for future modification.
    Recommendation #2 3DEXPERIENCE object deleted There are obsolete mapping objects in the system. Consider running the Delete operation with the Obsolete Mapping option. For more information, see Configure the Operations.
    Recommentation #3 3DEXPERIENCE type: design table Several 3DEXPERIENCE objects have been found for a same CATIA V5 object.

    The mapping objects have automatically been quarantined. Consider deleting all the 3DEXPERIENCE objects.
    Recommendation #4 3DEXPERIENCE type: instance/representation instance (3DEXPERIENCE object is different with the same V_Owner and V_Instance) Several 3DEXPERIENCE objects have been found for a same CATIA V5 object.

    Consider deleting the 3DEXPERIENCE object corresponding to the mapping object that has automatically been quarantined in the AutoCleanDuplicate report.
    Recommendation #5 3DEXPERIENCE: instance/representation instance (3DEXPERIENCE object is different) The duplicated mapping objects correspond to duplicated instances or representation instances.

    Open the structure to analyze the reference or representation reference value, comparing to V_InstanceOf and V_Owner value provided in the UserCleanDuplicate report.

    Consider deleting the instances or representation instances corresponding to the mapping objects you choose to quarantine.
    Recommendation #6 3DEXPERIENCE type: reference/representation (3DEXPERIENCE object is different) Different 3DEXPERIENCE objects are found for this DuplicateSet. Analyze the 3DEXPERIENCE object based on the information provided, and choose only one mapping object corresponding to it for future coexistence.

    First check if the 3DEXPERIENCE objects are part of the original coexistence scenario.

    If both objects are part of this scenario, manually delete one of them, and quarantine the corresponding mapping object.
    Recommendation #7 Mastership difference Different mastership values are found across duplicate mapping objects. The mapping object with V5 master might be the appropriate mapping object to keep.
    Recommendation #8 Non-3DEXPERIENCE object: reference/representation/instance Different non-3DEXPERIENCE objects are found for this DuplicateSet. Analyze the non-3DEXPERIENCE objects, and choose only one mapping object corresponding to it for future coexistence.

    First check if the non-3DEXPERIENCE objects are deleted or not. If an object is deleted, quarantine the corresponding mapping object.

    If none of the 3DEXPERIENCE object is deleted, keep the mapping object that is the most relevant for future coexistence, and quarantine the others.
    Recommendation #9 Mix of other configurations More than two DuplicateMappingType are identified for the DuplicateSet.

  7. Select the Apply user-defined cleaning option, and run the batch again.
    The duplicated mapping objects you specified are also quarantined.
  8. To update the policy where required, run the policychange.mql file that has been generated in the report directory.

    This file contains all the mapping objects that require the policy to be changed to VPLM_Replication.