企业管理 > 实施 Windchill ESI > Implementing Windchill ESI in an ORACLE Applications Environment > Loading Release History > Load Release History
  
Load Release History
The following steps describe how to load ESI ReleaseActivity objects:
1. Create a XML file for the data to be loaded in the format described before and save it as releaseactivity.xml to any location.
2. For example:
Standalone Parts:
<csvCreateReleaseActivity handler="com.ptc.windchill.esi.load.LoadESI.createReleaseActivity">
<csvreleaseClass>com.ptc.windchill.esi.Part</csvreleaseClass>
<csvobjectClass>wt.part.WTPart</csvobjectClass>
<csvobjectNumber>000000101</csvobjectNumber>
<csvobjectVersion>A</csvobjectVersion>
<csvobjectIteration>1</csvobjectIteration>
<csvobjectView>Design</csvobjectView>
<csvtargetNumber>00000003</csvtargetNumber>
<csvpublishDate>2015-07-05</csvpublishDate>
<csvpublishAction>create</csvpublishAction>
<csvpublishMessage>Loader Part</csvpublishMessage>
/<csvCreateReleaseActivity>
Assembly:
<csvCreateReleaseActivity handler="com.ptc.windchill.esi.load.LoadESI.createReleaseActivity">
<csvreleaseClass>com.ptc.windchill.esi.Part</csvreleaseClass>
<csvobjectClass>wt.part.WTPart</csvobjectClass>
<csvobjectNumber>0000000202</csvobjectNumber>
<csvobjectVersion>A</csvobjectVersion>
<csvobjectIteration>1</csvobjectIteration>
<csvobjectView>Design</csvobjectView>
<csvtargetNumber>00000003</csvtargetNumber>
<csvpublishDate>2015-07-05</csvpublishDate>
<csvpublishAction>create</csvpublishAction>
<csvpublishMessage>Loader Part</csvpublishMessage>
</csvCreateReleaseActivity>
* 
Since object 0000000202 is an assembly, it has two entries one for the part itself and one for the BOMheader.
3. Run the following command from Windchill shell:
windchill wt.load.LoadFromFile -d <path>\releaseactivity.xml
* 
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.