Usage Eligibility Criteria Not Evaluating Integers Correctly (Doc ID 2464890.1)

Last updated on SEPTEMBER 27, 2022

Applies to:

Symptoms

On : 2.2.0.2.0 version, Environment

ACTUAL BEHAVIOR
---------------
Usage Eligibility Criteria not working for number data types

Usage Rule Criteria Field Algorithm (D1-SP-URCF) which returns an element value (data type is number). The comparison operator is not working when the data type is number

EXPECTED BEHAVIOR
-----------------------
The comparison operator is expected to work when the data type is number

STEPS
-----------------------
The issue can be reproduced at will with the following steps:
1. Set up Usage Rule with Eligibility criteria using a number as the data type of the criteria to be evaluated e.g if a certain element is >50 then execute the rule.
2. Calculate a UT such that it calls the eligibility criteria.  Make sure element (from the SP for example ) is populated such that it is larger than the number being evaluaged, e.g. 150.
3. Notice the wrong path is taken because the evaluation results are incorrect by seeing that the Usage Rule is not executed when it should be.

BUSINESS IMPACT
-----------------------
The issue has the following business impact:
The logic that is set up to determine if certain rules should be executed is not working at all in this case with numbers. The impact of this issue is that rules are being executed when they should not be and rules that should be executed are skipped. This results in incorrect Usage Transaction calculation which directly affects billing.

Changes

Cause

My Oracle Support provides customers with access to over a million knowledge articles and a vibrant support community of peers and Oracle experts.