Identifying Problems with Parts
This section describes common problems and possible causes that relate to parts. A bullet list of common problems follows. If you do not see the problem you are experiencing in the list, or the suggested course of action does not completely solve the problem, contact your system administrator.
• Can’t create a part
• Can’t change a part
• Can’t see alternate parts
• Can’t see a part revision
• Changes to a part were applied across all Organizations
• A subtype attribute or its value is not rendered in the response file
• Business object attributes do not match between Windchill ESI and Publication System
• A distribution target is not assigned to a part during publication
• An error message appears when associating a certain distribution target to a part
• A part gets sent to a certain distribution target as a changed one in the ESI response, although the part was neither iterated nor revised
• A certain global attribute added to the type extended data does not get sent with the ESI response when the corresponding part is published
• A certain global attribute added to the type plant specific data does not get sent with the ESI response when the corresponding part is published
Can’t create a part
The following can cause this problem:
• Windchill release to manufacturing workflow has not started
• Part already exists in Oracle Applications
• Publishing status is incorrect in Windchill
• Oracle Applications user directly created part in Oracle Applications
• Incorrect or invalid ESITarget organization(s) assigned to part
• User is looking in wrong ESITarget organization(s) in Oracle Applications
• Invalid or missing part attributes
Can’t change a part
The following can cause this problem:
• Windchill release to manufacturing workflow has not started
• Part doesn’t exist in Oracle Applications in the ESITarget organization(s)
• Release status is incorrect in Windchill
• Oracle Applications user directly modified attributes in Oracle Applications that are mastered by Windchill
• Part is locked in Oracle
• Incorrect or invalid ESITarget organization(s) assigned to part
• User is looking in wrong ESITarget organization(s) in Oracle Applications
• Invalid or missing part attributes
Can’t see alternate parts
• Oracle Applications does not support alternates at the item level
Can’t see a part revision
The following can cause this problem:
• Windchill ESI completed processing the part attribute changes using the Open Item Interface, but did not subsequently create the part revision using the ECO Business Object Interface due to an error
• The Change Notice (CN) Management flag (middleware global variable) is set incorrectly
• Item revisioning is disabled in Oracle Applications
Changes to a part were applied across all Organizations
The Object Attribute Master Control flag (middleware global variable) is set incorrectly.
A subtype attribute or its value is not rendered in the response file
This problem could occur if:
• The mapping is incorrect.
• A unique identifier (internal name) is not defined for the subtype attribute.
• The internal name is not the source attribute name in the Map element defined for parts in the ESI response meta information map file.
Ensure that the mapping is correct. For example, if a subtype attribute has been defined on the wt.part.WTPart then;
• Attribute name: volume
• Unique identifier: org.ptc.volume
• Mapping: <esi:attributeMapping sourceAttribute="org.ptc.volume">Volume</esi:attributeMapping>
|
|
Add the above to the map element for parts in the ESI response meta information file.
|
Business object attributes do not match between Windchill ESI and Publication System
The following can cause this problem:
• Attribute is not mapped by ESI
• Oracle Applications user directly modified attributes in Oracle Applications
A distribution target is not assigned to a part during publication
A distribution target does not get automatically assigned to a part during publication, although the attribute Default for Context on the target is set to Yes and the target belongs to either the same context as the part, or to a higher level context
This can occur when the Windchill ESI preference View To Distribution Target Mappings is not set appropriately. For example, if the part in question is created in the Design view, the preference must be set to a value such as Design:001, in order for a distribution target with number 001 to be automatically assigned to the part when publishing the latter. Alternatively, the preference can have a value that makes no reference to the number of the target.
An error message appears when associating a certain distribution target to a part
This can be caused by any one of the following:
• The Windchill ESI preference View To Distribution Target Mappings is not set appropriately. For example, if the part in question is created in the Manufacturing view, the preference must be set to a value such as “Manufacturing:002”, in order for a distribution target with number 002 to be assignable to the part. Alternatively, the preference can have a value such as “Plant1:002” (where Plant1 is a child view of Manufacturing) or one that makes no reference to the number of the target.
• The distribution target is already assigned to the part.
A part gets sent to a certain distribution target as a changed one in the ESI response, although the part was neither iterated nor revised
This can be caused by any one of the following:
• Date effectivity was set for the part or was changed since the part was last successfully published.
• The lifecycle state on the part was changed since it was last successfully published.
• The Windchill ESI preference Publish Enterprise Data Information is set to Yes and the ERPMaterial object that represents the part was modified since the part was last successfully published.
• The Windchill ESI preference Publish Plant Data Information is set to Yes and the ERPPartSpecificPlantData object that represents plant specific data for the part and target was modified since the part was last successfully published.
A certain global attribute added to the type extended data does not get sent with the ESI response when the corresponding part is published
This can be caused by any one of the following:
• The Windchill ESI preference Publish Enterprise Data Information is set to No.
• No attributeMapping entry exists for the global attribute in the ESI response meta information file used for the publication.
• An entry exists for the global attribute in the ESI response meta information file, but the XML attribute erpMaterialAttribute for the entry is not set to true.
A certain global attribute added to the type plant specific data does not get sent with the ESI response when the corresponding part is published
This can be caused by any one of the following:
• The Windchill ESI preference Publish Plant Data Information is set to No.
• No attributeMapping entry exists for the global attribute in the ESI response meta information file used for the publication.
• An entry exists for the global attribute in the ESI response meta information file, but the XML attribute plantSpecificAttribute for the entry is not set to true.
