My Oracle Support Banner

Disabling A Component On A Bom Does Not Propagate Change To All Orgs To Which Bom Is Common (Doc ID 1936285.1)

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.

Symptoms

Actual Behavior
Find manually disabling a component on a bom doesn't propagate change to all Orgs for which the BOM is common.

Expected Behavior
Expect that when a component is disabled the change should be propagated to all common BOMs

Steps
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

Business Impact
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.

Cause

To view full details, sign in with your My Oracle Support account.

Don't have a My Oracle Support account? Click to get started!


In this Document
Symptoms
Cause
Solution
References


This document is being delivered to you via Oracle Support's Rapid Visibility (RaV) process and therefore has not been subject to an independent technical review.
My Oracle Support provides customers with access to over a million knowledge articles and a vibrant support community of peers and Oracle experts.