Release documentation - Cede - Enhancements and requests

Problem:

Details created by the Unearned Premium Reserve Order are not correctly split by Base Company and Original Base Company, when Calculation Option is 'Linear over Extended Accounting Period'

Solution:

Make sure Unearned Premium Reserve details are split on the same Base Company and Original Base Company as the source premium

Workaround:

Root Cause:

Incomplete implemention of SE-3281

Extent of Impact:

Impact on Existing Data

Recovery Method for Existing Data Affected

Problem:

Incorrect or missing Original Base Company on details created by the Unearned Premium Reserve Order. Occurs when there are both negative and positive premium bookings on the same business.

Solution:

Make sure the Unearned Premium details always have the same Original Base Company as the source premium

Workaround:

Root Cause:

Incorrect side effect of SE-3281

Extent of Impact:

Impact on Existing Data

Recovery Method for Existing Data Affected

Problem:

Not all Program sections are included when selecting List Business for Recovery Calculation Group order after having previously listed for a different selection criteria.

Solution:

When defining Main Class of Business to include Programs in Recovery Group Order, the system must add all program sections which meets the conditions. This must happen both when doing this when creating the order first time, and also when adding a new Main Class of Business after having and selecting List Business again.
The same functionality must be present for other extraction criterias.

Workaround:

Add the program section manually

Root Cause:

Extent of Impact:

Impact on Existing Data

Recovery Method for Existing Data Affected

Problem:
More than 2000 Light Life Policies in Multi Business PA order cause abend

Solution:
No limit on number of policies.

Workaround:

Root Cause:

Extent of Impact:

Impact on Existing Data

Recovery Method for Existing Data Affected

Problem:
When transforming a light policy to a policy, the system adds MAIN LIMIT to premium section, although this has not been defined so in in reference tables.

Suggested Solution:
the system should create the transformed policy with limits and premiums from light policy and otherwise as defined in reference tables,

Workaround:
Delete the Main limit from premium section

Root Cause:

Extent of Impact:

Impact on Existing Data

Recovery Method for Existing Data Affected

Problem:
Abend when opening sub section properties of policy ceded, as the system fails when populating business partner 'candidates' in the 'Other Broker' field.

Solution:
When the Policy Ceded 'Insured' business partner is just a text field and does not have a link to an actual business partner, the system should not include Insured in the list of business partner candidates for 'Other Broker' field. The list of candidates should be all business partners with business partner link.

Workaround:
None

Root Cause:

Extent of Impact:

Impact on Existing Data

Recovery Method for Existing Data Affected

Problem:
Different indexing for TW and CW
Solution:

Indexing made equal.

Workaround:

Root Cause:

Extent of Impact:

Impact on Existing Data

Recovery Method for Existing Data Affected

Problem:
Poor performance when editing claim location when list of available locations is substantial

Solution:

Workaround:

Root Cause:

Extent of Impact:

Impact on Existing Data

Recovery Method for Existing Data Affected

Problem:
UDF Layout for Light Policy does not work as expected when you use access codes.
Common Layout for Policy Ceded and Light Policy

Solution:

If access code is a selection criteria for a UDF layout it shall match access code of policy.

Workaround:

Root Cause:

Extent of Impact:

Impact on Existing Data

Recovery Method for Existing Data Affected

Problem:
Manual amendment of Light Policy, not possible to register Reporting Unit

Solution:
When creating a Policy Light and the base company is set up with Base Reporting Unit as mandatory in Classification Rules 1 the system must allow for manual update of Reporting Unit when doing an amendment.

Workaround:

Root Cause:

Extent of Impact:

Impact on Existing Data

Recovery Method for Existing Data Affected

Problem:
Abend while copying a Policy Ceded to new business, due to the source Policy Ceded being created with Insured business partner without link to business partner object. When copying or renewing the Policy Ceded at a later stage, the system abends.

Solution:
A policy Ceded could have an Insured which is just text, without a business partner link. When transforming a Policy Light to a Policy Ceded, Insured is created with name (and ID) if given at Policy Light. When copying / renewing the transformed Policy Ceded, the Insured must be copied accordingly; as a name and ID without link to BP.

Current functionality for copy/renew Policy Ceded is expecting a link to business partner, and this logic should be kept as-is if the Policy Ceded has an Insured with a business partner link.

Workaround:
Copy a Policy Ceded which is not transformed from a Policy Light, or create the Policy Ceded from scratch without using copy function.

Root Cause:

Extent of Impact:

Impact on Existing Data

Recovery Method for Existing Data Affected

Problem:

When opening a Retrocession Worksheet there is an abend on field Control Amount and AccYR/Period

Solution:

Disable possibility to edit Control amount and AccYR/Period for a Retrocession Worksheet.

Workaround:

Root Cause:

Extent of Impact:

Impact on Existing Data

Recovery Method for Existing Data Affected

Problem:
 When having a Life Light record created in Cede Interface Order with Life Insurable Object status = empty, the system abends second time a record is created with empty value - as it will try to update the Life IO status, and does not handle update when there is not a valid value.

Solution:
System must accept empty value in Life Insurable Object Status in Cede Interface record, as the field is not mandatory.
1) System accepts change from 'empty' to 'empty'
2) System accepts change from 'empty' to a valid status
3) System accepts change from valid to 'empty' status

Workaround:
Update current Life Insurable Object status to a valid value (f.ex. ALIVE, DISABLED), and use a valid value also in the Cede Interface record.

Root Cause:
SE-2074 implemented in 4.9.5

Extent of Impact:

Impact on Existing Data

Recovery Method for Existing Data Affected

Problem:
DTL_PLT_AMT on old bookings have strange values causing order to abend.

Solution:
Correct that new booking get correct value set. DTL_PLT_AMT = DTL_AMT
Correct old data.

Workaround:
Runa a script on old AC_LEDGER_DETAIL rows where update DTL_PLT_AMT = DTL_AMT.

Root Cause:

Extent of Impact:

Impact on Existing Data

Recovery Method for Existing Data Affected

Problem:

Walkback when trying to create New Light detail from Life policy light if no policy title

Solution:

The system should allow creation of a new life policy light booking online even though the Life Policy Light does not have a Policy Title.

Workaround:

Root Cause:

Extent of Impact:

Impact on Existing Data

Recovery Method for Existing Data Affected