Enterprise Administration > Windchill Export and Import > PTC Windchill PLM Connector - Creo Packages Administrator's and User's Guide > Creo Packages > Importing Packages > Importing a Package > Importing a Package Example
Importing a Package Example
The target PLM system design partner or supplier has received a package from the source PLM system design partner containing Creo Parametric data of a complete bike assembly.
Review the Package Details Report on the Target PLM System
Before importing the package to the target PLM system, the design partner or supplier for the target PLM system creates a package details report to review the package contents and to obtain the owner PLM system ID needed for the target PLM system mapping file.
WPCView -g c:\ptc\ilink03_siteA\bin\1102_1800_01 -t c:\ptc\bear203d_
siteB\temp
The following table contains essential arguments for this example WPCView command:
Command Name
Argument
Description
WPCView
-g
Use to specify the package name and path.
-t
Use to specify the target location for the package Details Report.
This sample Package Details Report contains detailed package and PDM object set information about the exported package from the source PLM system design partner.
+++++++++++++++++++++++++++++++++++++++++++++++++
Package Details
I Package Information
Description
Package creation date: June 10 18:00:50 EDT 2009
Source system ID: 6107333525-1190288955171-32960257-204-89-253
-132@alink03.ptcnet.ptc.com
Source system description:
Source system version: 9.1
Product version: 9.1
Package type: regular
II PDM Object set
i. Set of Masters
ii.Set of Versions
1 PMDPackageVersion
Name: crank_asm_1800.prt
Owner system ID: Same as source ID
Revision: A(position 1)
Iteration: 4(position 4)
Exported time: June 10 18:00:50 EDT 2009
Location: /ptc/Product/Hill Climber//M1800
Lifecycle: Basic
Lifecycle state: INWORK
Content:
Name: crank_asm_1800.prt
Authoring application: PROE
+++++++++++++++++++++++++++++++++++++++++++++++++
The owner PLM system ID needed for the target PLM system mapping file is contained in the package information PDM Object Set section of the report.
For example:
6107333525-1190288955171-32960257-204-89-253-132@alink03.ptcnet.ptc.com
Prepare the Package for Import to the Target PLM System
The mapping file (*.mapping) must be updated to include the owner PLM system ID number and appropriate mapping information for the package being received from the source PLM system. This file can be updated in any text editor. For example:
Site -id 610733525-1190288955171-32960257-204-89-253-132@ilink03.
ptcnet.ptc.com -alias "ilink03_server"
rule -iteration_rule Position -revision_rule Position

begin

location "/ptc/Library/mig_test//Part/Basic/pub_geo"="/ptc/
Library/mig_test//Assembly/Design"
location "/ptc/Library/mig_test//Part/Basic/mig_geo"="/ptc/
Library/mig_test//Assembly/Phase"

lifecyclestate "Basic::INWORK"="Basic::INWORK"
lifecyclestate "Basic::RELEASED"="Basic::RELEASED"
lifecyclestate "Basic::CANCELLED"="Basic::CANCELLED"

rule -iteration_rule Position -revision_rule Position

end
The mapping file can contain mapping information for location, life cycle state, and revision scheme.
Validate the Package to Be Imported in the Target PLM System
The WPCImport command can be used without attempting import on the target PLM system when using the -package and -validate arguments to check for conflicts.
For example, to validate a package for the package name and path C:\ptc\ilink03SiteA\bin\1101-05, the following is entered at the command line:
WPCImport -u jadams -p ptc -g C:\ptc\ilink03SiteA\bin\1101-05 -v C:\ptc
The following table contains essential arguments for this example WPCImport command:
Command Name
Argument
Description
WPCImport
-u
Use to specify the username.
-p
Use to specify the password. For increased security, you can choose to not include the password. The system prompts you for the password and mask the password characters that you enter.
-g
Use to specify the package name and location.
-v
Use to validate the package against the target PLM system without attempting import and is used with the -package (-g) argument.
Import the Package to the Target PLM System
After successful validation, the package is ready to be imported into the target PLM system using the Creo Packages WPCImport command and arguments.
For example, to import a package using mapping files for the package name and path C:\ptc\ilink03SiteA\bin\1101-05, the following is entered at the command line:
WPCImport -u jadams -p ptc -g C:\ptc\ilink03SiteA\bin\1101-05 -m C:\ptc
The following table contains essential arguments for this example WPCImport command:
Command Name
Argument
Description
WPCImport
-u
Use to specify the username.
-p
Use to specify the password. For increased security, you can choose to not include the password. The system prompts you for the password and mask the password characters that you enter.
-g
Use to specify the package name.
-m
Use to specify the directory where mapping files are located.
Review the Import Post Report
The Import Post Report for the imported data contains the Creo Parametric assemblies and components with various actions and revision values. The report may contain information concerning file names, revisions, iterations, life cycle, life cycle state, and locations for owner and target system.
For example:

IMPORT POST REPORT
General report
Imported as new(3 objects)
FILE NAME
ACTIONS
LOCAL REVISION
LOCAL ITERATION
LOCAL LIFE CYCLE STATE
LOCAL LOCATION
block2.
prt
Create
New
1
Basic
INWORK
/ptc/Library/mig_test//From_PDML/test1
square_
pat_asm.
asm
Create
New
1
Basic
INWORK
/ptc/Library/mig_test//From_PDML/test1
square_
pat_part
.prt
Create
New
1
Basic
INWORK
/ptc/Library/mig_test//From_PDML/test1
(continuation of remaining columns of the Import post report)
OWNER REVISION
OWNER ITERATION
OWNER LIFECYCLE
OWNER LIFECYCLE STATE
OWNER LOCATION
A
1
Basic
INWORK
/ptc/Library/mig_test//test2
A
1
Basic
INWORK
/ptc/Library/mig_test//test2
A
1
Basic
INWORK
/ptc/Library/mig_test//test2
Was this helpful?