Load Release History
The following steps describe how to load ESI ReleaseActivity objects:
1. Create a CSV file for the data to be loaded in the format described before and save it as releaseactivity.csv to any location.
2. For example:
Standalone Parts:
ESIReleaseActivity,com.ptc.windchill.esi.Part,0000000061,A,1,
Design,DV1_00001,2008-12-17,createESIReleaseActivity,com.
ptc.windchill.esi.Part,0000000062,A,1,
Design,DV1_00002,2008-12-17,createESIReleaseActivity,
com.ptc.windchill.esi.Part,0000000063,A,1,
Design,DV1_00001,2008-12-17,changeESIReleaseActivity,
com.ptc.windchill.esi.Part,0000000064,A,1,
Design,DV1_00002,2008-12-17,changeESIReleaseActivity,
com.ptc.windchill.esi.Part,0000000065,A,1,Design,DV1_00001,2008-12-17,change
Assembly:
ESIReleaseActivity,com.ptc.windchill.esi.BOMHeader,0000000202,A,2,Design,
DV1_00001,2008-12-17,create
ESIReleaseActivity,com.ptc.windchill.esi.Part,0000000202,A,2,Design,
DV1_00001,2008-12-17,create
ESIReleaseActivity,com.ptc.windchill.esi.Part,0000000201,A,1,Design,
DV1_00001,2008-12-17,create
|
|
Since object 0000000202 is an assembly, it has two entries one for the part itself and one for the BOMheader.
|
3. Ensure sure that the Windchill installation has the csvmapfile.txt file in the following location.
<wt_home>\codebase\com\ptc\windchill\esi\load
4. Run the following command from Windchill shell.
|
|
In the above command, <wt_home> and <path> should be replaced by actual values. The newly created Windchill ESI ReleaseActivity objects will not be associated with an ESITransaction object. Given that there is no transaction, the release history will not be viewable via the Transaction Management GUI.
|
