Parts
ERP Connector passes the following part-associated attributes from Windchill PDMLink to a distribution target:
• Number
• Whether the part is a phantom part or not
• Default Unit
• Control Characteristics
• Type
• Name
• Source
• Version
• Iteration
• Date Effectivity
• Last Changed By
• Distribution Targets
• Serial Effectivity
• Lot Effectivity
• Lifecycle State
• View
• Storage Location
• Previously Published Part Version
• Enterprise Data
• Plant Specific Functional Data
Publish Enterprise Data
Enterprise data is a versioned, workable object in Windchill that is used to store data that needs to be published to an ERP system. The Enterprise Data can be published in the ESI response to a distribution target using the ERP connector.
To publish the enterprise data, enable the preference Publish Common Enterprise Data Information by setting it to Yes.
To know more about Enterprise Data, see the topic
Enterprise Data.
|
|
• If you want to publish the version information from the part or enterprise data, set the property com.ptc.windchill.esi.useVersionInfofromPartOrED in the esi.properties file. For example, <Property default="PART" name="com.ptc.windchill.esi.useVersionInfofromPartOrED">. Other values can be PART or COMMON_ENTERPRISE_DATA
Otherwise OOTB, the common enterprise data will be published by default.
• The attribute Distribution Targets (in the elements Destination and TargetID that appear in the ESI response) identifies the distribution target in which the part should be created or changed.
• Windchill PDMLink passes the Part Date Effectivity in the format YYYY-MM-DD HH:MM:SS.
• When using the object-centric mode of publishing a part, with the distribution target attribute Publish Related Documents when Publishing a Part set to Yes, documents associated to the part are published as well.
|
Plant Specific Functional Data
The plant-specific functional data attributes are published along with the part or resource attributes in the ESI response from all the relevant plant-specific data objects associated with the view-specific enterprise data.
Ensure that the Publish View Specific Enterprise Data Information preference from the > > category is set to Yes.
For more information about the plant specific functional data, refer to
Plant-specific Functional Data Overview.
Configuring Data to Publish Automatically with Life Cycle State Change
The enterprise data or plant specific functional data can be configured to get published automatically in the ESI response if the life cycle state of the view-specific enterprise data is changed. You can configure this by enabling the preference Enterprise data life cycle states to trigger part publication automatically from > > . You can specify multiple life cycle states in a comma-separated list. The default value of the preference is empty.
After enabling this preference, when common enterprise data or view-specific enterprise data life cycle state is changed as specified in the preference, ESI will render the relevant part iteration and the plant-specific functional data as per the configuration specification or filter associated with the distribution target to publish the part in the ESI response.
|
|
• The publishing of a part is enabled only if the preference Launch ESI Workflow Automatically is set to Yes.
• If the view-specific enterprise data is released, the view-specific enterprise data and the common enterprise data will get published. Whereas, if the common enterprise data is released, then the relevant view-specific enterprise data is published.
|
The enterprise data and plant specific functional data can be published in separate buckets in the ESI response. This can be done by customizing the ESI response. Refer the ERP Connector Customizer's Guide on PTC.com to know more about customizing the buckets in the ESI response.
