Policy Level Activity Wrongly Spawn Entry In AsClientActivity Table
(Doc ID 2963581.1)
Last updated on JULY 26, 2023
Applies to:
Oracle Insurance Policy Administration J2EE - Version 11.3.0.1 and laterInformation in this document applies to any platform.
Symptoms
On : 11.3.0.1 version, General
ACTUAL BEHAVIOR
---------------
When a Client level Activity spawns a Policy level Activity then spawned Activity wrongly has an entry in AsClientActivity table.
This causes issue in Client level Batch processing as those spawned Activities are considered by OIPA base code as Client level Activities when they are not.
As a workaround, the business can run following SQL every day before batch Cycle starts:
- Delete from asclientactivity Where activityguid in (select activityguid from asactivity where policyguid is not null)
EXPECTED BEHAVIOR
-----------------------
No Activity on AsClientActivity table.
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 |