When The Capable To Promise Flag Is Checked On A Common Router It Will Not Populate On New Items, is this Normal?
(Doc ID 1572007.1)
Last updated on FEBRUARY 06, 2020
Applies to:Oracle Bills of Material - Version 220.127.116.11 and later
Information in this document applies to any platform.
When the Capable to Promise flag is checked on a common router it will not populate on new items, is this normal, expected functionality?
Support was able to replicate the issue at will in our instance 18.104.22.168 internal instance:
Query a routing: SB22679
capable to promise = checked
operations 10 and 20 assembly and packing, referenced checked
New routing for item ASO0027
tools > assign common routing SB22679
warning: you can only view common operations, saved
result: new routing created but Capable to promise flag NOT checked in new routing ASO0027 once common router SB22679 is
assigned and saved.
is this normal behavior or a bug?
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