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:

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:

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.

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.

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.

Plant-specific attributes for a part can be published using the view-specific capabilities of Windchill MPMLink. To publish plant-specific attributes:

Windchill ESI then retrieves the plant-specific attributes for the part from Windchill MPMLink and sends that information to the relevant organization in the distribution target.

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.

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.

For more information, see the topic Plant-specific Functional Data Overview.

Ensure that the Publish View Specific Enterprise Data Information preference from the ESI > Settings > Part category is set to Yes.

For more information about the plant specific functional data, refer to Plant-specific Functional Data Overview.

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 ESI > Setting > Part. 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 common enterprise data or view-specific enterprise data is changed.

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 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.