My Oracle Support Banner

The MultiSuspense STOP Attribute Does Not Limit The Number Of Suspense Item (Doc ID 2762044.1)

Last updated on MARCH 22, 2021

Applies to:

Oracle Insurance Policy Administration J2EE - Version 10.2.0.34 and later
Information in this document applies to any platform.

Symptoms

On : 10.2.0.34 version, General

ACTUAL BEHAVIOR
---------------
The lack of a limit allows users to add more Suspense items than are configured for in the Math, resulting in Suspense items that do not have proper Accounting.
The XML guide no longer lists these as available attributes of the MultiSuspense tag, but the palette still shows them.
This appears to not be supported any more or there is a bug, because we have users entering > 5 suspense items and creating problems.


EXPECTED BEHAVIOR
-----------------------
In v8 when client configured MultiSuspense with start and stop attributes that limited how many suspense items could be entered.
Eg : SuspenseToUse
This is important because the way client's accounting is set up depends on specific math variables for each one so having an upper limit ensures our accounting works.


STEPS
-----------------------
The issue can be reproduced at will with the following steps:
1. Configure an activity ex: SuspenseRefund with MultiSuspense tag: GrossDistribution
2. Add the activity and go to the Suspense tab. This brings up suspense entry table.
3. You can click on the + to add additional suspense.
4. By the config, after the STOP limit is reached, it should not display the + anymore however it still allows the user to add as many suspense items as user wants.



Cause

To view full details, sign in with your My Oracle Support account.

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


In this Document
Symptoms
Cause
Solution
References


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