Windchill ESI allows you to publish Change Notices (CNs) created within Windchill ESI to a distribution target such as Oracle Applications. Publishing CNs from Windchill ESI also includes the publishing of all part, BOM, process plan and operation objects that are listed (the item process is used to maintain item attributes other than part revisions). By enabling this capability in Windchill ESI, users can also create and change parts, BOMs, process plans and operations when publishing the CN.

Windchill ESI creates all ECOs in Oracle Applications so that they have object revisions and BOM objects listed on them. When processing the ECO in Oracle Applications, Windchill ESI initially sets the status of each ECO to Scheduled in Oracle. An administrator should schedule the Automatic Engineering Change Order Implementation concurrent program to run at predetermined intervals for all ESI-related organizations. This program sets the status of all recently-created (Scheduled) ECOs to Implemented based on effectivity. This is a critical processing step, as it makes the ECOs effective. For more information, see the Windchill Enterprise Systems Integration Administration - Oracle Applications.

When you associate various attributes to a CN in Windchill PDMLink, Windchill ESI passes the attributes to the EAI software components. The following attributes are passed (the list consists of both attributes of the resulting objects and those of the CN itself):

Once the CN data has been published by Windchill ESI Services, the EAI software components map the Windchill CN attributes to Oracle Applications ECO attributes. The following table shows the mapping of Windchill CN attributes to Oracle Applications ECO attributes.

The attribute Distribution Target in Windchill PDMLink identifies the distribution target in which the CN should be created. The EAI software components use this information to communicate with the correct target data source 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 24HH:MM:SS. Windchill ESI assumes that the time zone is configured across Windchill PDMLink, TIBCO, and Oracle Applications.

The Action (relative to the CN) for CN Headers, Revised Objects (Parts), Revised Items (BOM Headers), and Process Plans is cross-referenced in the EAI software components. The table below shows the possible available Windchill PDMLink action values and the corresponding Oracle Applications values that are passed from the EAI software components to Oracle Applications.

The absolute Action for Revised Components, Reference Designators, Substitutes and Operations is cross-referenced in the EAI software components. The following table shows the possible available Windchill PDMLink action values and the corresponding Oracle Applications Add-Change-Delete (ACD) Type values that are passed from the EAI software components to Oracle Applications.

There are some attributes that are required within Oracle Applications to create or change ECOs 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 ECO attributes that are defaulted in Windchill ESI and their defaulted values.