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 create a reference designator on a BOM (can't see it in Oracle Applications)
• Can’t change a BOM
• ESI Response Value for the Usage Element 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:
• BOM already exists in Oracle Applications
• Incorrect or invalid ESITarget organization(s) assigned to part
• User is looking in wrong ESITarget organization(s) in Oracle Applications
• Invalid component(s)
• Invalid substitute(s)
• Invalid reference designator(s)
• Invalid effectivity date(s) (cannot use dates in the past)
• Effectivity offset (middleware global variable) set incorrectly
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:
• BOM request flag for substitutes (middleware global variable) set incorrectly
• Part does not exist
• Invalid quantity
Can't create a reference designator on a BOM (can't see it in Oracle Applications)
The following can cause this problem:
• BOM request flag for reference designators (middleware global variable) set incorrectly
• Invalid reference designator
Can’t change a BOM
The following can cause this problem:
• The Oracle Applications BOM does not match the BOM in Windchill
• An Oracle Applications user directly modified attributes in Oracle Applications that are mastered by Windchill
• Did not assign ESITarget organization(s) to component(s), substitute(s), or reference designators in Windchill
• Invalid component
• Invalid substitute
• Invalid reference designator
• Invalid effectivity date(s) (cannot use dates in the past)
• Effectivity offset (middleware global variable) set incorrectly
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 Explorer, 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 attributes 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.
|
