My Oracle Support Banner

AsFilePostInsertProcessPolicy Cannot Process A Policy If PolicyNumber Is Not Unique. (Doc ID 2406536.1)

Last updated on MARCH 13, 2019

Applies to:

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


On : version, General

AsFilePostInsertProcessPolicy cannot process a policy if PolicyNumber is not unique. When AsFile inserts a Policy where its PolicyNumber is not unique, and the AsFilePostInsertProcessPolicy functionality is called it will not process the newly added Policy. The system will try and process all activities on a policy that already exists in the system and not one AsFile just inserted.

AsFilePostInsertProcessPolicy will process activities on the newly created policy inserted by AsFile even if the PolicyNumber is not unique.

The issue can be reproduced at will with the following steps:
1) Create an AsFile that will insert a Policy and an Activity where you can specify the PolicyNumber
1a) Have this AsFile call AsFilePostInsertProcessPolicy
2) Call this AsFile such that it will insert the Policy and process the generated activity
3) Call the AsFile again and use the same PolicyNumber as in step 2
4) Notice the activity on the second Policy will not be processed.

The issue has the following business impact:
Due to this issue, Policy Numbers are not guaranteed to be unique and newly inserted policies will not be processed as expected.


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.