Release documentation - Cede - Enhancements and requests

Problem:
The Retrocession Calculation order abends when including the calculation of the Loss Participation and the field 'Max Pct of Premium' is empty

Solution:
The calculation of the Loss Participation requires a percentage in the field 'Max Pct of Premium' in Deductible conditions/Type Loss Participation.
System must issue an error message when no percentage is given in this field.

Workaround:
Enter a percentage 0,00 - 100,00 in field 'Max Pct of Premium' on Deductible Conditions, Type = Loss Participation to avoid the abend.

Root Cause:

Extent of Impact:

Impact on Existing Data

Recovery Method for Existing Data Affected

Problem:
SICS abends when trying to open Profit Commission Conditions either in an Assumed Business or OCC.

Solution:
When the Profit Commission conditions are created the system shall still be able to do that even if there are no Entry Code Groups within the Entry Code Group Category 'Premium Basis for Management Expenses'. In this situation the Profit Commission conditions can be created and when the user select Percent in the Management Expenses area the drop down for Premium Basis will just be empty.

Workaround:
Make at least one EC Group within the Entry Code Group Category 'Premium Basis for Management Expenses'. It does not make much sense to have PC defined without the possibility to define Management Expenses.

Root Cause:

Extent of Impact:

Impact on Existing Data

Recovery Method for Existing Data Affected

Problem:
The CEDE User Guide does not include eMessaging documentation

Solution:
Include eMessaging in CEDE User Guide

Workaround:

Root Cause:

Extent of Impact:

Impact on Existing Data

Recovery Method for Existing Data Affected

Problem:
Report with acccounting and claim info loose non claim bookings

Solution:

Change structure to extract accountung data linked to policy.

Workaround:

Root Cause:

Extent of Impact:

Impact on Existing Data

Recovery Method for Existing Data Affected

Problem:
System does not consider 'Registration Complete' flag for an OCC Fac Protection correctly when running PB order.

Solution:
When system parameter 'Require Complete Registration' is selected and a Prop Fac OCC without Registration Complete protecting a Policy Light the system should not retrocede booked figures via PB order.

Workaround:
When having set SysPar 'Require Complete Registration' = Yes, make sure all Outward Cedent's contracts (including Prop Fac OCC) has the 'Registration Complete' flag set before making any bookings

Root Cause:

Extent of Impact:

Impact on Existing Data

Recovery Method for Existing Data Affected

Problem:
Abend when running Loss Recovery when Light Claims handled as Risks Attaching with Interlocking Clause

Solution:
When Protection Program / OCC is Risks Attaching with Interlocking Clause selected the system must handle calculation of total inward claim and share against each OCC Insured Period correctly; i.e. according to valid FGU inward claim details which matches the OCC classification.

Workaround:
None

Root Cause:

Extent of Impact:

Impact on Existing Data

Recovery Method for Existing Data Affected

Problem:
SICS does not save parameter (link to Multi Claim Protection Assignment Order) added to a Job Scheduler Step

Solution:
When creating an Actual Job in Scheduler for Multi Claim Protection Assignment Order, this must be saved to the database to enable scheduled run of the order/s.
When running the scheduled order it must run through all steps correctly giving the desired results and giving error message if something goes wrong.

Workaround:
Run order online

Root Cause:

Extent of Impact:

Impact on Existing Data

Recovery Method for Existing Data Affected

Problem:
Settings in Reference Data Order for Sysem Defined items lost when upgrading,
Change Reinstatement Condition page order in reference data - Business Wizard Page (01008) from 110 to 29 - see first screen below.
Reopen SICS Workstation and go to Reference Data and check the ordering in Business Wizard Page (01008). Order of pages is re-set and Reinstatement Condition is again with value 110 (instead of 29)

Solution:
Order kept similar to changed name is kep-

Workaround:
Make a note of any changes to the Order of System Defined Reference Data items and manually re-set after Update Reference Data is run,

Root Cause:

Extent of Impact:

Impact on Existing Data

Recovery Method for Existing Data Affected

Problem:
Abend when running Multi Claim Protection Assignment

Solution:
When running Multi Claim Protection Assignment order with Calculate PA On Claim, the system must display proposed protection in the menu list.

Workaround:
Manual claim assignment

Root Cause:

Problem:
Even when a RUG Id is unique the system triggers error message 'BS0229 - Identifier is not unique' when attempting to edit the RUG.

Solution:
When editing a Risk Unit Group, BS0229 should not be triggered when an actual duplicate Id does not exist.
Should be working as in 21.2.

Workaround:

Root Cause: