Publishing Co-produce Objects
In a manufacturing plant, the same material can be used to produce different components of a product. Parts that are produced in a single production process can be put together as a co-produce object. One of these parts can be considered as primary, and the other parts as secondary. For more information, see Co-produce Object.
You can publish the co-produce object information in the Windchill Enterprise Systems Integration (ESI) response to a distribution target using Windchill ESI.
Windchill ESI lets you publish the co-produce object information that are created or changed within Windchill MPMLink to a distribution target. You can assign one or more distribution targets to a co-produce object through Associate Distribution Targets option from the Actions menu or using Windchill loader. For more information on assigning a distribution target, see Associating Distribution Targets with Objects and Using a Loader to Assign Distribution Targets.
Windchill ESI passes the following co-produce object information to the EAI software components.
The following attributes of the MadeFromObject are passed:
• ObjectID
• Class — com.ptc.windchill.esi.MadeFromObject
• LastChangedBy
• Number
• DefaultUnit
• Name
• PartType
• Source
• State
• View
• Version
• Iteration
• PreviousVersion
• AssociatedEffectivityID
• Type — Coproduce
• TargetID
The following attributes of BOMComponent of the co-produce object are passed
• ObjectID
• Class — com.ptc.windchill.esi.BOMComponent
• PartNumber
• AssemblyPartNumber
• AssemblyPartID
• Quantity
• Unit
• LineNumber
• FindNumber
• AlternateItemGroup
• ComponentID
• IsChildPhantom
• IsPartConfigurable
• IsPartCollapsible
• AssociatedEffectivityID
• IsRawMaterial
• Usage
• Alternate
• Type
• Category
• Consumption
• TargetID
The following attributes of BOMHeader of the co-produce object are passed:
• ObjectID
• Class — com.ptc.windchill.esi.BOMHeader
• LastChangedBy
• Number
• Version
• Iteration
• EnterpriseVersion
• PreviousVersion
• Usage
• Alternate
• IsCADPhantom
• IsCollapsible
• AssociatedEffectivityID
• Type
• TargetPlant
• Quantity
• Unit
• AssociatedMadeFromObjectID
• IsAllocatedAsResource
• TargetID
In the ESI response, the co-produce structure is published as an alternate BOM for its primary part.
When publishing a process plan associated with a co-produce object, the process plan associated with the co-produce object is published as a process plan for the primary part of the co-produce. The part to process plan link is sent with the primary part instead of the co-produce object.
The following information is also published in the ESI response:
• Enterprise Data
• Plant Data
• Department Data
• Documents associated with the co-produce object
You can publish co-produce information using the following methods:
• Set State
• Change Notice
• Send to Distribution Target
• Co-produce associated with BOM, process plan, and resource structure for its primary part
 |
• Co-produce is not supported in the Oracle applications.
• Its is recommended to assign line numbers to the components if a BOM or Made From Set or CoProduce object contains duplicate components. For example, if you have structure as shown below, you should assign line numbers to the components.
Car
└ Wheel (Line Number = 10) └ Wheel (Line Number = 20) └ Wheel (Line Number = 30) └ Wheel (Line Number = 40) └ Seat (Line Number = 50) • When you delete and add the same component (in a scenario where the component is not duplicated at the same level for the same parent), in the resulting ESI response will have this component as a changed component.
• When we have duplicate raw material links and one of them is deleted, and readded, then the response will contain the deleted link in deleted bucket and the added link in the added bucket.
|