Importing a Package on the Target PLM System
This section describes the necessary steps for partners or suppliers receiving packages from the source PLM system before they are imported to the target PLM system
Viewing the Package Details Report
A design partners or supplier who receives an exported package from the source PLM system begins by viewing the exported package details report. The package details report contains the owner PLM system ID needed for the target PLM mapping file.
Setting Import Preferences
Before importing the package to the target PLM System, the design partner or supplier receiving the exported package from the source PLM system, sets the import preferences in the wpc_preferences.txt file on the target PLM system machine. You can also create mapping files for the imported package.
If the user who exported the package does not have access to all of the CAD objects and their dependents and used the wpc.export.secured.version preference to create an incomplete package, you must enable the wpc.export.secured.version to successfully import the package. For more information, see Setting Import Preferences and Setting Export Preferences.
Validating the Package to be Imported
Before importing the package on the target PLM system, use the -validate argument with the WPCImport command to check for conflicts. If conflicts are found, Creo Packages generates a conflict report.
Importing the Package
After validation, you are ready to import the package to the target PLM system using the Creo Packages WPCImport command and arguments.
After the import, the model files and the associated metadata are available in the target system. This imported design data may be new to the target system, a new iteration of a previously shared design, or a new version of a previously shared design.
 |
You must not make changes to the imported data on the target PLM system.
You can do a private checkout operation on collaborated objects, irrespective of whether the ownership of the object is local or not. For more on information, see Object Ownership Transfer and Collaboration Using Creo Packages.
|