Publishing Production Versions
You can use a routing plan as a production version. A routing plan determines which process plan should be used with which BOM for a specified quantity in a specific plant. There can be one or more production versions based on the effectivity such as date, lot, and serial number. For more information on routing plan, see Managing Routing Plans.
Windchill ESI allows you to publish production versions created or changed within Windchill PDMLink to a distribution target using one of the following methods:
• Set State
• Change Notice
• Promotion Request
• Send to Distribution Target
The following preferences control the publishing of production versions:
• Routing Plans to be Considered as Production Versions — Only the routing plan, or its subtypes, selected in this preference are considered as production version objects for publishing.
• Lifecycle States for Triggering Production Version Publishing — Specify the lifecycle states to automatically trigger the publication of production version objects. You can add one or more lifecycle states in a comma-separated list.
The above preferences are available for the Site and Organization contexts at > > > > .
You can assign one or more distribution targets to a production version using Associate Distribution Target action. The automatic distribution target assignment is also supported.
The following information associated with the production version is published in the ESI response file:
• Production version information including plant information.
• Production version assignment link between production version and process plan.
• Production version assignment link between production version and part.
• Effectivity associated with the production version such as date, lot, and serial number.
 |
Only the metadata of the part, process plan, and plant linked to the production version is published in the ESI response. It does not include the actual part, process plan, and plant objects.
|
The following production version attributes are published in the ESI response:
• ObjectID
• Class
• Number
• Name
• LotSize
• CycleTime
• RoutePosition
• LongDescription
• Description
• State
• Version
• Iteration
• LastChangedBy
• PreviousVersion
• RouteHolderRef
• PlantNumber
• PlantName
• PlantVersion
• PlantIteration
• AssociatedEffectivityID — Effectivity information is published as separate elements in the ESI response.
• TargetID
The following production version assignment link attributes are published in the ESI response:
• ObjectID
• ProductionVersionReference
• RoutableClass — This can be part or process plan class.
• RoutableNumber — This can be part or process plan number.
• RoutableVersion — This can be part or process plan version.
• Alternate — This can be alternate number for part or process plan.
• Usage — This can be part or process plan usage.
• View — This can be view on part or process plan.
• TargetID
The transaction status of a published production version is available in the Related ESI Transactions. For information on how to view ESI transactions, see Viewing Related ESI Transactions.
Currently, TIBCO business logic does not support publishing of production versions to SAP and Oracle Applications.