Enterprise Administration > Windchill Export and Import > PTC Windchill PLM Connector - Creo Packages Administrator's and User's Guide > Creo Packages > Importing Packages > Conflict Handling and Resolution > Conflict Resolution
Conflict Resolution
When there are conflicts between the source and the target PLM systems, Creo Packages generate reports. These conflicts can be divided in the following two types:
• Overridable—The conflicts that Creo Packages can resolve are called the overridable conflicts. When an overridable conflict occurs, Creo Packages generates a CSV file in the output folder. This file lists the conflicts that have occurred while validating the package and the corresponding resolution. You can use this file or the wpc_preferences.txt file to resolve the conflict.
To apply a resolution for a particular object, use the CSV file. For this, you need to use the resolution option with the WPCImport command to resolve the conflict. After resolving the conflict, import the package again.
To apply a common resolution for all the objects, you can use the wpc_preferences.txt file.
• Non-overridable—When a non-overridable conflict occurs, the conflict report is generated in the output directory that you specify on the command line with the -output option. Otherwise, the conflict report is generated in your current-working-directory.
Suggested Actions For Resolving Conflicts
 
Overridable
The following actions are suggested for overridable conflicts:
Label in the report
Type of Conflict Message
Resolution
Error code: OVERRIDE_MISSING_REF
The following references are expected to exist in the target PLM system, but they are missing in target PLM system.
Object-level
• IGNORE_MISSING_REF
Ignore if the expected object does not exist in the target PLM system.
• REUSE_OR_IGNORE_MISSING_REF
If the name and master ID of the model file in the package and target database match, reuse the file in the target PLM system. Otherwise, ignore the file.
Error code:
OVERRIDE_LATER_VERSION
Later versions of the following objects already exist in the target PLM system.
Object-level
Creo Parametric may not be able to regenerate the object.
LASTEST_VERSION_REUSEUSE
Use the object from the target PLM system.
Error code:
OVERRIDE_FOLDER_NOT_FOUND
The specified folder not found in the target PLM system.
A mapped folder does not exist in the target PLM system.
Definition-level
CREATE_TARGET_FOLDER
In this example, the resolution works only if the inherited release level scheme agrees the mapping.
Error code:
REVISE_INPDMLINK
The incoming object has a different revision.
The package contains objects with a different revision, and objects have already been PDM checked in.
Definition-level
REVISE_INPDMLINK
For example:
Conflict.OVERRIDE_NEW_REVISION=REVISE_IN_PDMLINK
Non-overridable
The following actions are suggested for non-overridable conflicts:
Label in the report
Type of Conflict Message
Suggested Action
The following objects with the same file name already exist in target.
Object-level
• Ignore the complete package.
• Rename the object either in the source PLM system or the target PLM system, depending on which PLM system owns the object.
Cannot rename bolt.prt to bolt1.prt as object with the same name exists.
Object-level
• Ignore the complete package.
• Rename the object either in the source PLM system or the target PLM system, depending on which PLM system owns the object.
You do not have authorization to modify the following objects.
Definition-level
While exporting do not include these objects in the package. While importing do not import this package.
The following objects are expected to exist in the target PLM system, but they do not exist in the target PLM system.
Object-level
Expected files available in the target PLM system with same Object ID.
The lifecycle state/ release level of the following objects could not be updated.
Object-level
Manually change the life cycle state of this object in the target PLM system to see the reason for the conflict and its resolution.
File Name could not be updated for the following objects.
Object-level
Rename this object in the target PLM system to see the reason for the conflict and its resolution.
The following missing dependents could not be resolved.
Object-level
You must create these objects in the target PLM system.
The following objects were saved using later version of Creo.
Object-level
Use a later version of Creo Parametric to perform the import.
• The following folders could not be created.
• Mapping file provides an invalid folder name.
• You have no authorization to create a particular folder.
Definition-level
• Create the folder manually in the target PLM system to see the reason for the conflict and its resolution.
• Review the folder mapping.
The following target locations have incompatible release scheme/lifecycle.
Definition-level
• Change the mapping to map to a valid release level or life cycle state.
• Create a valid definition for the release scheme or release state in the target PLM system.
The following target locations have incompatible release level/lifecycle state mapping.
Definition-level
• Change the mapping to a valid one.
• Create a valid definition in the target PLM system.
The following revisions do not exist in the target PLM system.
Definition-level
• Create a corresponding revision in the target PLM system, if it is allowed in your PLM system.
• Map the missing revision to an existing revision in the target PLM system.
The following revisions have been mapped from multiple source revisions.
Multiple revisions from a single revision scheme in the source PLM system are mapped to a single revision in the target PLM system.
Definition-level
Map a single version from a revision scheme to only one revision in the target PLM system.
Was this helpful?