Reviewing the Package to be Imported
To review a package and its contents, open a command prompt, go to the Creo Packages installation directory, and type the following command:
WPCView -p <package name with full path>
This command generates an HTML package details report in your current working directory and provides the following information:
• Package source ID
• Comments, if any
• List of included objects
• List of included metadata
Using the Information From the Package
Reviewing the package using the HTML package details report enables you to determine the following information:
• Source PLM system for the package
You can import packages from multiple source PLM systems. However, it is important to know the source PLM system from where you have obtained a particular package. Use the site ID label in the package to identify the source PLM system. This site ID is unique for each source PLM system and can be used in a mapping file. For more information on mapping files, see
Mapping the Target PLM System.
• Type of package and changes made in the source PLM system
If the package to be imported is an incremental package, you must ensure its preceding full package is imported before importing the incremental package.
• Type of metadata included in the package
The package includes information about whether objects in the package are expected or packaged. Objects imported into the target PLM system for the first time are marked as packaged.
Objects marked as expected must be present in the target PLM system from an earlier import. The package to be imported contains the metadata (and possibly) that has changed since the preceding import.
Besides the information contained in the HTML package details report, you can acquire the following information from the package:
• Whether or not you want to create a new folder (or folders) in the target PLM system into which you want to import the package.
• Whether or not you want the object properties in the package and the target PLM system to be the same. If the object properties are different, map them before importing the package to avoid conflicts.