Where Clause Issues In A Get Category Item Step Type (Doc ID 2262964.1)

Last updated on MAY 12, 2017

Applies to:

Oracle Insurance Insbridge Rating and Underwriting - Version 5.0.1 and later
Information in this document applies to any platform.

Symptoms

On : Insbridge 5.0.1 version, RateManager

ACTUAL BEHAVIOR
---------------
Where Clause Issues in a Get Category Item step type

While debugging a test case against Windows and Java engine it was noticed that there were 3 issues with trying to use a Where Clause in a Get Category Item step type. The following summarizes the 3 issues:
Issue #1:
It appears you cannot use a Calculated Variable in the Term 2 slot of a Where Clause. Doing so does not throw an error but the engine will never find a match even if there is one. You can see this by looking at Algorithm called aPT Wtd Avg NHC Overall Rtng Steps 1 - 2. Note the “a” character in front of name.
See attached screen shots labeled:
1a_Get_Item_with_Where_Clause_definition
1b_Get_Item_with_Where_Clause_debug
Once I adjust the Algorithm to use a “Results of Step” variable in the Term 2 slot of the Where Clause, the engine finds a match. You can see this by looking at Algorithm called bPT Wtd Avg NHC Overall Rtng Steps 1 - 2. Note the “b” character in front of name.
See attached screen shots labeled:
2a_Get_Item_with_Where_Clause_definition
2b_Get_Item_with_Where_Clause_debug

Issue #2:
When the Where Clause does not find a match, the Where Clause info is not shown in the debug report. This does not match what happens when using Where Clause on a Sum Across step type and no matches are found. The debug report should show the Where Clause info even if there is no match found.
See attached screen shots labeled:
1b_Get_Item_with_Where_Clause_debug
2b_Get_Item_with_Where_Clause_debug

Issue #3:
When the Where Clause does not find a match, the result of that step indicates NULL. However, in the very next step in Algorithm, that same result variable is checked and it shows a value. Not sure where the value came from but it is incorrect and should have been NULL or 0.
See attached screen shots labeled:
1b_Get_Item_with_Where_Clause_debug
2b_Get_Item_with_Where_Clause_debug
 

BUSINESS IMPACT
-----------------------
The issue has the following business impact:
Due to this issue, where clauses are erroneous in the Debug report.

Cause

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