Last updated on MARCH 08, 2017
Applies to:Oracle Bills of Material - Version 12.1.3 and later
Information in this document applies to any platform.
Find manually disabling a component on a bom doesn't propagate change to all Orgs for which the BOM is common.
Expect that when a component is disabled the change should be propagated to all common BOMs
The issue can be reproduced at will with the following steps:
1. Disable a component on a Bill of Material
2. Find that the change is not reflected in all common BOMS
The issue has the following business impact:
BOM data is being corrupted in our production instance, causing discrete jobs to go out to the shop floor with incorrect material requirements.
Sign In with your My Oracle Support account
Don't have a My Oracle Support account? Click to get started
Million Knowledge Articles and hundreds of Community platforms