My Oracle Support Banner

CreatePolicy Crashes When AllocationSet For Specified Typecode Is Not Present On Source Policy (Doc ID 2518278.1)

Last updated on DECEMBER 03, 2019

Applies to:

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


On : version, General

3 type codes for allocations on a policy. 02, 04 and 06. Want CreatePolicy to copy all source policy allocation sets over to the target policy. In the case where the allocationset does not exist for a specific TypeCode, the CreatePolicy BusinessRule crashes with attached stack trace. It happens that the source policy has 1 out of 3 allocation sets defined, or 2 out of 3 and sometimes has all 3 defined.

The rule does not allow to test that the allocation set exists, which would solve our issue.

CreatePolicy copies all source allocation sets from source policy to target policy, no matter how many allocation sets are defined

The issue can be reproduced at will with the following steps:
1. Use configuration to create new policy. Make sure that the source policy has 0,1 or 2 allocation sets defined.

The issue has the following business impact:
Unable to use create policy to copy source policy over to target.


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

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