MaintainSuspense Accounting Is Not Working As It Did in V7
(Doc ID 2269873.1)
Last updated on MAY 24, 2017
Applies to:Oracle Insurance Policy Administration J2EE - Version 10.2.0.0 and later
Information in this document applies to any platform.
A SuspenseAddReverse transaction is used to reverse a SuspenseAdd transaction and in certain cases,
to shadow a single suspense ticket to generate the appropriate reverse suspense accounting.
MaintainSuspense Business Rule is attached to the SuspenseAddReverse transaction.
MaintainSuspense allows for in the Attribute/Element Table, but does not work in V10 as is did in V7
In the <SuspenseArrays> section, the <CopyToSuspenseFields> works as expected.
The does not work as expected. It generates forward Suspense accounting, thereby replicating the accounting records.
User requires reversed entries. When the transaction is reversed, the accounting is not reversed.
Each time the transaction is recycled, an additional set of entries is produced.
Is this a defect, configuration or an enhancement?
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