Administración de la empresa > Implementación de Windchill ESI > Implementing Windchill ESI in an SAP Environment > Loading Release History
Loading Release History
Release history is a record of the information that is published from Windchill, identifying both the source Windchill PDMLinkdata and the distribution target. It may sometimes be necessary to load the release history for objects (such as parts and assemblies) that reside in the ERP system, but which were not published by Windchill ESI in the first place. Such a loading helps ensure that the two systems (Windchill PDMLinkand the ERP system) are in sync with each other, thereby allowing ESI to use those objects in subsequent publications.
Release Activity is now a typed object.
You can access the Release Activity from Site > Utilities > Type and Attribute Management. For more information on Type and Attribute Management, see Working with the Type and Attribute Management Utility.
You can add local and global attributes for Release Activity, but sub-types can not be created.
Loading release history is a common ERP Connector function. Release history may be loaded from an XML (Extensible Markup Language) or a CSV (comma-separated values) import file, having the following format:
Field
Description
LoadType
Required to drive the Windchill Data Loader. This value should be ESIReleaseActivity.
ObjectClass
The Windchill ESI class specification for the published object. For parts, this should be com.ptc.windchill.esi.Part. For BOM, this should be com.ptc.windchill.esi.BOMHeader.
ObjectNumber
The Windchill object number. For example, part number.
ObjectVersion
The Windchill version number of the object.
ObjectIteration
(Optional) If unspecified, the most recent iteration of the version is used. Otherwise, this is a specific Windchill iteration number.
ObjectView
(Optional) The Windchill view name. The view in which the iteration is defined.
* 
Views only apply to parts.
TargetNumber
The number attribute of the distribution target to use for creating the release history
PublishDate
The date on which the information was published to ERP. The format should be YYYY-MM-DD HH:MM:SS. The time portion is optional. If specified, the time should be represented as GMT. If unspecified, the time will default to midnight in the time zone configured within Windchill.
PublishAction
Should be create if the object was created as a result of publishing, or change if the object was changed.
For example:
Standalone
#BeginReleaseActivities
BeginReleaseActivities
#CreateReleaseActivity,releaseClass,objectClass,objectNumber,objectVersion,objectIteration,objectView,targetNumber,publishDate,publishAction,containerPath,publishMessage
CreateReleaseActivity,com.ptc.windchill.esi.Part,wt.part.WTPart,0000000072,A,1,Design,00000003,7/22/2021,create,,publish Part_0001
#EndReleaseActivities
EndReleaseActivities
Attributes
#BeginReleaseActivities
BeginReleaseActivities
#CreateReleaseActivity,releaseClass,objectClass,objectNumber,objectVersion,objectIteration,objectView,targetNumber,publishDate,publishAction,containerPath,publishMessage
CreateReleaseActivity,com.ptc.windchill.esi.Part,wt.part.WTPart,0000000072,A,1,Design,00000003,7/22/2021,create,,publish Part_0001
#LoadValue,name,refType,refAtt,value
LoadValue,MyString,,,DATA|java.lang.String|New_myString4
#IBAValue,definition,value1,value2,dependency_id
IBAValue,StringIBA,StringIBA_3,,
#EndReleaseActivity
EndReleaseActivity
#EndReleaseActivities
EndReleaseActivities
Each row in the import file represents a publishing event for a specific Windchill business object to a specific ERP organization.
¿Fue esto útil?