Parts
Windchill ESI allows you to publish parts created and changed within Windchill PDMLink to a distribution target such as Oracle Applications. You can configure the Windchill PDMLink system to publish particular attributes of the parts. The Windchill PDMLink part information is used to create a part in the distribution target.
Windchill ESI passes the following part-associated attributes from Windchill PDMLink to the EAI software components:
• 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
• Extended Data
• Department Data
Once the part data has been sent from Windchill PDMLink, the EAI software components map the Windchill PDMLink part attributes to Oracle Applications object attributes. The following table shows the mapping of Windchill PDMLink part attributes to Oracle Applications object attributes:
|
Windchill Part Attribute
|
Oracle Applications Object Attribute
|
|---|---|
|
Number
|
Item Number
|
|
Default Unit
|
Primary Unit of Measure
|
|
Part Type
|
User Item Type using Template
|
|
Date Effectivity
|
Item’s Revision Effectivity Date
|
|
Name
|
Item Description
|
|
Version
|
Revision Level
|
|
Source
|
General planning Make or Buy
|
|
Distribution Target
|
Organization
|
The Windchill PDMLink part iteration is passed to the EAI software components; however, the attribute is not sent to the distribution target. If the distribution target is capable of handling Windchill PDMLink part iterations, the EAI software components can be extended to pass the information to the distribution target; however, the out-of-the-box Oracle Applications system does not currently have an attribute that can handle iteration information.
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. The EAI software components use this information to communicate with the correct distribution target and pass organization information to it.
Some attributes that are passed from Windchill PDMLink are passed to the distribution target from the EAI software components without transformation; however, there are a few attributes that contain values that are either modified or cross referenced by the EAI software components.
Windchill PDMLink passes the Start Effectivity Date in the format YYYY-MM-DD HH:MM:SS. Windchill ESI assumes that the time zone is configured across Windchill PDMLink, TIBCO, and Oracle Applications.
The attributes Default Unit, Part Type, and Source are cross referenced in the EAI software components. The following tables show the possible available Windchill PDMLink part values and the corresponding Oracle Applications item values that are passed from the EAI software components to Oracle Applications.
|
Windchill Part Default Unit Value (Database Value)
|
Oracle Applications Base Unit of Measure Value (Database Value)
|
|---|---|
|
As Needed (as_needed)
|
As Needed (AN)
|
|
Each (ea)
|
Each (Ea)
|
|
Kilogram (kg)
|
Kilogram (KG)
|
|
Liter (l)
|
Liter (L)
|
|
Meter (m)
|
Meter (M)
|
|
Windchill PDMLink Part Type Value (Database Value)
|
Oracle Applications Item Type Value (Database Value)
|
|---|---|
|
Separable (separable)
|
Subassembly (SA)This is the mapping for the API field ITEM_TYPE. The mapping for the API field TEMPLATE_ID is Subassembly (5), and the mapping for the API field TEMPLATE_NAME is Subassembly (@Subassembly).
|
|
Inseparable (inseparable)
|
Subassembly (SA)
This is the mapping for the API field ITEM_TYPE. The mapping for the API field TEMPLATE_ID is Subassembly (5), and the mapping for the API field TEMPLATE_NAME is Subassembly (@Subassembly).
|
|
Component (component)
|
Purchased Item (P)
This is the mapping for the API field ITEM_TYPE. The mapping for the API field TEMPLATE_ID is Purchased Item (2), and the mapping for the API field TEMPLATE_NAME is Purchased Item (@Purchased Item)
|
|
Windchill PDMLink Part Source Value (Database Value)
|
Oracle Applications General Planning Make or Buy Value
|
|---|---|
|
Make (make)
|
Make (1)
|
|
Buy (buy)
|
Buy (2)
|
There are some attributes that Oracle Applications requires to create or change item records that are not provided by Windchill PDMLink. In these instances, Windchill ESI defaults the values in the EAI software components prior to passing the data to Oracle Applications. The following table lists the Oracle Applications item attributes that are defaulted in Windchill ESI and their default values.
|
Oracle Applications Item Attribute
|
Default Value
|
|---|---|
|
Summary Flag
|
No (N)
|
|
Effectivity Control
|
1 for Date or 2 for Unit
|
|
Serial Number Generation Code
|
2 for Predefined
|
|
Starting Prefix
|
X
|
|
Starting Number
|
1
|
Windchill ESI also leverages Subassembly and Purchased Item templates in Oracle Applications, which automatically provide default data values for many other Item fields. See the Oracle Inventory User's Guide supplied with your Oracle Applications software for further details on Item templates.
Windchill PDMLink also supports publishing alternates related to parts; however, because the concept of alternate parts, as it exists in Windchill PDMLink, does not exist in Oracle Applications, the EAI software components portion of Windchill ESI does not support publishing alternate parts to Oracle Applications. If the Oracle Applications distribution target is capable of handling Windchill PDMLink alternates, the EAI software components portion of Windchill ESI can be extended to pass the information to Oracle Applications, however, by default, alternates are not supported.
Publishing an Enterprise Version of a Manufacturing Part
Every downstream part is manufactured based on the specification of the upstream part. For a particular part, the Enterprise Version attribute displays the linked upstream part version. For more information, see Enterprise Version.
When publishing a manufacturing part, the ESI response contains the information of the Enterprise version (upstream version) along with the manufacturing part information.
For example, when you publish the manufacturing part (version A.1), the ESI response includes the upstream design part (version B.1) information, along with the manufacturing part (version A.1) information. Refer to the image below.
This feature is useful when you want to track the part revision using the engineering revision (in this case, the design part) in the downstream ERP system.
Follow these steps to enable this preference:
1. Open the Preference Management utility. Click > > .
2. Select > > .
3. Set the preference Publish Enterprise Version of manufacturing part as Yes.
The Enterprise Version is consumed in the Oracle ERP system for material and BOM.
Plant Specific Attributes for Parts
Plant-specific attributes for a part can be published using the view-specific capabilities of Windchill MPMLink. To publish plant-specific attributes:
• Ensure that the Publish Plant Data Information preference from the > > category is set to Yes.
• Define a specific view corresponding to each of your plants in Windchill MPMLink.
• Define your plant-specific attributes in the corresponding view attributes tab.
• Use Windchill ESI to publish your part.
Windchill ESI then retrieves the plant-specific attributes for the part from Windchill MPMLink and sends that information to the relevant plant in the distribution target.
 | • These attributes must have their mapping defined in the ESI response meta information file. Also, the EAI software components should be extended to map these attributes to SAP as appropriate. • While publishing department data or plant data for parts or resources using Send to Distribution Target action, Send Material to Distribution Target action, Change Notice, Promotion Request, Set State, or Saved Filter is used from: ◦ BOM Settings on distribution target when publishing part or BOM. ◦ Resource Settings on distribution target when publishing resource or resource structure. ◦ Process Plan Settings on distribution target when publishing process plan structure. ◦ Change Notice Settings on distribution target when publishing using change notice. |
Department Attributes for Parts
Department attributes for a part can be published using the plant specific capabilities of Windchill MPMLink. To publish department attributes:
• Ensure that the Publish Plant Data Information preference from the > > category is set to Yes.
• Define a specific view corresponding to each of your plants in Windchill MPMLink.
• Define your department attributes in the corresponding view attributes tab.
• Use Windchill ESI to publish your part.
Windchill ESI then retrieves the department attributes for the part from Windchill MPMLink and sends that information to the relevant organization in the distribution target.
| | • These attributes must have their mappings defined in the ESI response meta information file. Also, the EAI software components should be extended to map these attributes to Oracle Applications as appropriate. • While publishing department or plant data for parts or resources using Send To Distribution Target action, Send Material To Distribution Target action, Change Notice, Promotion Request, or Set State, Saved Filter is used from: ◦ BOM Settings on distribution target when publishing part or BOM. ◦ Resource Settings on distribution target when publishing resource or resource structure. ◦ Process Plan Settings on distribution target when publishing process plan structure. ◦ Change Notice Settings on distribution target when publishing using change notice. |
Publish Extended Data
Extended data is a versioned, workable object in Windchill that is used to store data that needs to be published to an ERP system. The extended data can be published in the ESI response to a distribution target using the ERP connector.
To publish the extended data, enable the preference Publish Enterprise Data Information by setting it to Yes.
To know more about extended data, see the topic Extended Data.
| | • If you want to publish the version information from the part or extended 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 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. |
Department Data
The department data attributes are published along with the part or resource attributes in the ESI response from all the relevant department data objects associated with the plant data.
For more information, see the topic Department Data Overview.
Ensure that the Publish Plant Data Information preference from the > > category is set to Yes.
For more information about the department data, refer to Department Data Overview.
Configuring Data to Publish Automatically with Life Cycle State Change
The extended data or department data can be configured to get published automatically in the ESI response if the life cycle state of the plant data is changed. You can configure this by enabling the preference Extended 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. If the preference value is empty, the Part (material) will not be published automatically when life cycle state of enterprise data or plant data is changed.
After enabling this preference, when enterprise data or plant data life cycle state is changed as specified in the preference, ESI will render the relevant part iteration and the department 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 plant data is released, the plant data and the enterprise data will get published. Whereas, if the enterprise data is released, then the relevant plant data is published. |
The extended data and department data can be published in separate buckets in the ESI response. This can be done by customizing the ESI response. Refer to the applicable ERP Connector Customizer's Guide on Document Reference Site to know more about customizing the buckets in the ESI response.