Publishing Operations
Windchill ESI enables you to publish an operation (including a standard operation) based on its life cycle state without publishing the related process plan. However, for the first-time publishing of an operation, the relevant process plan and parent operation must be already published to the downstream ERP systems.
You can publish an operation using one of the following methods:
Set State
Change Notice
Promotion Request
Publishing of an operation is based on the life cycle state specified in the Operation Configuration Specification States preference. This preference defines the life cycle states at which the publication of an operation is triggered. By default, its value is empty or blank. You can set the preference value to one or more lifecycle states using a comma-separated list. The preference values are not case-sensitive. The preference is available for the Site and Organization contexts at Preference Management > ESI > Settings > Windchill MPMLink > Process Plan. For more information on setting a preference, see Preference Management.
The publication of an operation is triggered only if the following conditions are met:
The life cycle state matches the preference value,
The Launch ESI Workflow Automatically preference is set to Yes,
The operation is not associated with an implemented change notice.
Other than the conditions mentioned above, consider the following points when publishing an operation:
For the first-time publishing of an operation, the relevant process plan and parent operation must be already published to the downstream ERP systems.
The operation is published to the distribution targets associated with the process plan.
Consider the Distribution Target Attributes settings of the process plan when publishing an operation. For example, Number of Levels in an Assembly to Publish when Publishing a Change Notice and Number of Levels of Sub-Operations to be Published when Publishing a Change Notice.
Based on the distribution target attributes settings, the following information associated with the operation is published in the ESI response:
Relevant process plan and parent-operation information
Part allocation information (regular and operated-on part allocations)
Resource allocation information
Standard control characteristics
Documents
Work instructions
Options and variant expressions
* 
The ESI response includes associated process plan and parent-operation information to identify and have the operation persist in the downstream ERP systems. However, this information does not persist in the downstream ERP systems.
Publishing status of the operation is displayed in the related Distribution Target table on the Operation information page.
Was this helpful?