Dear All,
Found this information on support web for query related errors / issues.
When we select a PDQ, it gives the expected result set (provided the criteria are correct). Next, when we refine the query (ALT + R), a message is thrown as:
---------------------------
Siebel
---------------------------
Current search specification is too complex to be refined.
Please start a new query or refine one that is less complex.(SBL-DAT-00487)
---------------------------
OK
---------------------------
Solution:
The “OR” operator in the query expression should be converted to equivalent expression without the “OR” i.e.,
(Expression A) OR (Expression B)
Can be converted as
NOT (NOT (Expression A) AND NOT (Expression B))
| PRE-QUERY AND SBL-DAT-00487 [ID 956294.1] | | ||
| | |||
| | Modified 21-OCT-2009 Type HOWTO Status MODERATED | | |
In this Document
Goal
Solution
| 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. |
Applies to:
Siebel Tools - Version: 7.5.3.15 SIA [16279] - Release: V7
Information in this document applies to any platform.
Comments
--------
1. How can we resolve the message ( "Current search specification is too complex to be refined. Please start a new query or refine one that is less complex. (SBL-DAT-00487)") and let the user be able to refine their query?
For the issue with error, "Current search specification is too complex to be refined. Please start a new query or refine one that is less complex. (SBL-DAT-00487)", we have done some research on it. This issue often shows when a compound query contains any "OR" operator. The workaround is: The logic expression containing "OR" operator can be always converted to other equivalence expression without "OR" operator. For example, there’s a compound logic expression made from two simple logic expression:
(Expression A) OR (Expression B)
It can always be converted to equivalence:
NOT (NOT (Expression A) AND NOT (Expression B))
By converting to equivalence, the “OR” operator no longer stays in the query expression and the error message will be prevented.
There are a few existing Change Requests have been logged to address the product enhancement request:
CR 12-1H4W95G (Unable to refine Opportunity queries containing OR)
CR 12-1LTGWED (Allow the possibility to use the OR operator between two text fields in a PDQ)
The status for the above CRs is “Active Open”.
We hope the above information helps.
Thank you,
Oracle Tech Support
Thanks and regards,
Rama, K
This message contains information that may be privileged or confidential and is the property of the Capgemini Group. It is intended only for the person to whom it is addressed. If you are not the intended recipient, you are not authorized to read, print, retain, copy, disseminate, distribute, or use this message or any part thereof. If you receive this message in error, please notify the sender immediately and delete all copies of this message.
