Identifying Problems with Bills of Material (BOMs)
This section describes common problems and possible causes that relate to BOMs. A bulleted list of common problems follows. You can use the links to go directly to the information for the problem you are experiencing. If you do not see the problem you are experiencing in the list, or the suggested course of action does not solve the problem, contact your system administrator.
• Can’t create a BOM
• Can’t create a component on a BOM
• Can’t create a substitute on a BOM
• Can’t change a BOM
• Reference designators do not appear on the BOM in SAP
• BOM revision does not appear in SAP
• The BOM create or change operation appeared to be successful but there are warning messages (40215, 40216)
• ESI response value for the usage Eelement is different than BOM Type value
• Component parts in an assembly are not published to certain distribution targets, although the targets are associated to those parts
Can’t create a BOM
The following can cause this problem:
• Incorrect or invalid ESITarget plant(s) assigned to part
• User is looking in wrong ESITarget plant(s) in SAP
• Invalid component(s)
• Invalid substitute(s)
• Phantom CAD subassembly publication is not supported
Can’t create a component on a BOM
The following can cause this problem:
• Part does not exist
• Invalid line number
• Invalid quantity
Can’t create a substitute on a BOM
The following can cause this problem:
• Part does not exist
• Invalid quantity
• Invalid line number
• Invalid alternate item group
• No alternate item group with the component for the substitute
Can’t change a BOM
The following can cause this problem:
• Did not assign ESITarget plant(s) to component(s) or substitute(s) in Windchill
• Invalid component
• Invalid substitute
Reference designators do not appear on the BOM in SAP
This is expected behavior. Windchill ESI does not support the sending of reference designators to SAP.
BOM revision does not appear in SAP
The following can cause this problem:
• Windchill ESI does not support the sending of BOM revisions without a CN
• Revision management is not enabled in SAP or the TIBCO BusinessWorks application
The BOM create or change operation appeared to be successful but there are warning messages (40215, 40216)
40215: SAP returned a warning while attempting to change a BOM
40216: SAP returned a warning while attempting to create a BOM
• SAP automatically returns a warning message when creating a group BOM; these messages can be safely ignored
• Windchill ESI attempted to delete an invalid component, substitute, or other data in SAP
• Windchill ESI attempted to change a BOM by adding a component that does not exist in SAP
ESI response value for the Usage Element is different than BOM Type value
The value sent with the ESI response for the Usage element for a certain assembly is different from the value specified for BOM Type for the assembly part from the Manufacturing Product Structure Browser, using the Update Alternate BOM Number option.
This can occur when the Windchill ESI preferences View To Distribution Target Mappings and View To BOM Type Mappings are set to override the BOM Type value specified on the assembly part iteration. For example, if these preferences are set to values “Design:001,Manufacturing:002” and “Design:Engineering,Manufacturing:Production” respectively, a value of Engineering will be sent for the Usage element when the assembly is published to the distribution target with number 001, thereby overriding the BOM Type value that may have been specified on the assembly part.
Component parts in an assembly are not published to certain distribution targets, although the targets are associated to those parts
This can be caused by any of the following:
• The distribution targets have their Status attribute set to Inactive.
• The distribution targets are not associated to the assembly part that holds the component parts; also, the targets belong in a different ERP instance as compared to those associated to the assembly part.
 |
In order for a component part in an assembly to be published to a distribution target that is not associated to the assembly part, the target must belong in the same ERP instance as any of the targets associated to the assembly part.
|