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 the ERP Connector.
ERP Connector lets you publish the co-produce object information that are created or changed within Windchill MPMLink to a distribution target. Only one distribution target can be assigned to a co-produce object as a co-produce object cannot be used across different plants.
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
MaterialGroup
StorageLocation
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
Type
Usage
Alternate
TargetID
Consumption
The following attributes of BOMHeader of the co-produce object are passed:
ObjectID
Class — com.ptc.windchill.esi.BOMHeader
LastChangedBy
Number
Version
Iteration
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
Was this helpful?