BOMPKMUD And BOMFDMCO (Mass Changes) Using Old Values Instead of Null
(Doc ID 1950337.1)
Last updated on FEBRUARY 28, 2019
Applies to:Oracle Bills of Material - Version 12.0.6 to 12.2.4 [Release 12 to 12.2]
Information in this document applies to any platform.
As per Oracle's own documentation, "If you do not wish to replace the values for the Supply Type, Supply Subinventory, and Supply Locator fields, you must enter the current value when executing a mass change. If you leave the Supply Type, Supply Subinventory, and Supply Locator fields blank when entering component changes, their values will be replaced by the blank (null) value when the mass change is executed."
THIS IS NOT WORKING. If you leave these values blank (NULL), it does NOT replace the old values with NULL, it tries to use the old values and BOMPKMUD errors out (if the 'New' item is not assigned the same Item Subinventory/Locator as the 'Update' item).
Expect to be able to leave the values for Supply Type, Supply Subinventory, and Supply Locator fields Null in the mass change and have the values set to NULL as per the documentation.
Steps to Reproduce
- Create a Mass Change
- Leave the values for Supply Type, Supply Subinventory, and Supply Locator null
- The mass change process errors as it is trying to use the old values.
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