Exception Query Using AMONG Does Not Save Correctly And Returns Wrong Results

(Doc ID 2031762.1)

Last updated on JUNE 28, 2017

Applies to:

Oracle Advanced Supply Chain Planning - Version 12.2.3 to 12.2.4 [Release 12.2]
Information in this document applies to any platform.


12.2.3 and 12.2.4 in Production and Test

Exception query using AMONG condition does not save properly and executes wrong query

Create exception query with AMONG - like Org - AMONG - TST:M1, TST:M2
Save - and see status bar show the records are save
Then click again in the FROM field and find it empty - org are missing
If you execute the query then you see same number of records returned as in the Exception summary (i.e. all records) instead of reduced record set

query works as defined

cannot use these queries.
Users cannot do normal daily routines


Sign In with your My Oracle Support account

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

My Oracle Support provides customers with access to over a
Million Knowledge Articles and hundreds of Community platforms