My Oracle Support Banner

Translation On Plan Name For New Policy (Doc ID 2793316.1)

Last updated on JULY 22, 2021

Applies to:

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

Symptoms

On : 11.2.0.13 version, General

ACTUAL BEHAVIOR
---------------
OIPA is looking at the translated output of the select plan name in AsPlan instead of the real name value. If an AsTranslation exist for a particular AsPlan name, then OIPA will automatically show the translated plan name value on the Plan Name field, but will use this translated value to look for available plan names in AsPlan to be able to create the policy instead of just checking the original non translated value.
 

EXPECTED BEHAVIOR
-----------------------
Whatever the translations associated to the PlanName (translationkey) the new Policy screen shouldn't look through AsPlan with the TranslationValue for available plans.
 

STEPS
-----------------------
The issue can be reproduced at will with the following steps:
1. Create a plan with a Plan Name.
2. Create a translation where the TranslationKey is the Plan Name but the TranslationValue is something else (and that is not another Plan Name).
3. Go to Create Policy.
4. Whatever the Plan date, OIPA will show an error message stating "No effective plans for the plan date mm/dd/yyyy" although it will still show in Plan field the desired translated plan name but won't allow to save the policy.

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.