MathStatement Throws Stack Trace When Used In ScreenMath And Environment Has Debug=ON (Doc ID 2910093.1)

Last updated on NOVEMBER 18, 2022

Applies to:

Symptoms

On : 11.3.1.1 version, General

ACTUAL BEHAVIOR
---------------
MathStatement throws stack trace when used in ScreenMath and environment has Debug=ON.

When creating a Transaction using a mathstatement within ScreenMath , the configuration functions locally in an Oracle environment when Debug-OFF but crashes in Development environment where Debug=ON.When using ActivityFunction to do Valuation via ScreenMath:

<MathStatement TYPE="ACTIVITYFUNCTION" FUNCTIONNAME="MathValuation">
<Parameters>
<Parameter NAME="ValuationDate" TYPE="INPUT">EffectiveDate</Parameter>
<Parameter NAME="PolicyValues" TYPE="INPUT">'Yes'</Parameter>
<Parameter NAME="NearestPrice" TYPE="INPUT">'No'</Parameter>
</Parameters>
</MathStatement>

EXPECTED BEHAVIOR
-----------------------
Mathstatement in ScreenMath should work within the environment using Dbeug=On/Off.

STEPS
-----------------------
The issue can be reproduced at will with the following steps:
1. Use the attached configuration to create Termination Transaction.
2. Attempt to select the Activity in the drop down and Activity will not load but report a stack trace.

Cause

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