Release documentation - Cede - Enhancements and requests

Problem:
Performance problem when you create a new claim with automatic protection assignment due to incorrect incurred calculation.

Solution:
When running Recovery Calculation for Protection Program and selecting Pre-processing; the system checks light claims and regular claims (linked to Policy Ceded / assumed business) which does not have the Include in Recovery flag set; and the following process should be followed for Single Claims only (not linked to Headline loss):

• Calculation is done for single Light Claims / regular Claims only (not for claims linked to Headline loss; these are not considered for this automatic inclusion process).
• Calculate current Incurred amount by extracting Paid Claim, Paid Expenses, Outstanding Reserves and Outstanding Expenses as per run date (not considering Booking Year and Period extraction at Recovery Calculation order).
• Use As-of Date exchange rate for calculation of Paid claims and Current exchange rate for calculation of reserves
• Remove Incurred (and currency) column at Claim - Links/ Protection Allocation (for regular Claims). This field gives a performance issue when opening the tab and when doing manual protection allocation for these claims. As the incurred amount is available from the claim ledger tab, we find it unneccesarry to store it here as well.

After the calculation; the following will trigger the 'Include in Recovery' flag to be set to 'Yes' (according to the existing process):

• If the Incurred amount is above Excess of first layer in Program section
• If the Incurred amount is above the 'Claim Creation Limit' percentage of the 1st layer excess of the Program section
• If the Incurred amount is above 'Claim Advice limit' percentage given at 1st layer excess of the Program section (Claim Advice limit at OCC is used if global and OCC limit is different).

Workaround:

Root Cause:

SC-4039

Extent of Impact:

Impact on Existing Data

Recovery Method for Existing Data Affected

Problem:
Multi Claim Auto Protection order does not work when Light Claim protected by XLCA.

Solution:
When running Multi Claim Protection Assignment order and selecting 'Include XLCA of Outward' the system should validate if there are any XLCA protections which matches the Light Policy.
When you process the Multi Claim Auto Protection Order with the Include XL CA Of Outward selected, the system finds the Proportional OCC(s) protecting the scope of cover of the extracted claims, checks if it has common account protection (XLCA) and validates the XLCA protection against the claim. If the protection is found valid for the claim, the protection allocation percentage is set equal to the gross retroceded share of the proportional protection assignment protected by the respective XL CA Of Outward.

Validations must be the same as for regular light claim protection assignment and must work for both Light Policy, Policy Ceded.

Workaround:
Use 'Automatic Assignment to Outward Cedent’s Contract' and select XLCA ID from Light Claim

Root Cause:

Extent of Impact:

Impact on Existing Data

Recovery Method for Existing Data Affected

Problem: MTK Loader crashes when trying to write to loader files

Solution:

Workaround:

Root Cause:

Extent of Impact:

Impact on Existing Data

Recovery Method for Existing Data Affected

Problem:
When there is an existing Light claim to a Policy section (section A), and another section is created at the Policy (section B) (without Light Claim to Section relation), a new claim record from Cede Interface for section B will not be accepted; giving error message BUS0056.

Solution:
If there is an existing Policy section which an existing Light Claim (with a claim-to-soc relation to this Policy) - a new Light Claim record with the same Claim ID should get a claim-to-soc relation to the new Policy section - and bookings are done to same Light Claim - but to new section.

If there is an existing Policy section and a new Light Claim is to be created via Cede Interface, the Light Claim must be created to the existing Policy section if the section name is the same, and no new section version should be created. If the Light Claim DOL is outside the Insured Period of the Policy Light Insured Period, the new Claim is added to the latest amendment of current Insured Period. 

Workaround:
it finds/creates the correct section for light claim booking in these two occasions:
• if the Light Claim is already linked to the Policy section
• if the section is not created – it is automatically created via Cede Interface via Light claim record

Root Cause:
Probably caused by SE-7605 / SICSR-21529

Extent of Impact:

Impact on Existing Data

Recovery Method for Existing Data Affected

Problem:

Abend when running preliminary booking order protected by Prop Fac OCC when system parameter Book Future Due Items On RP is activated. Issue caused by SE-5737

Solution:

System Parameter 'Book Future Due Items On RP' applies to Proportional OCC- and Retrocessionaire Participation (RP) Treaty Businesses. This function should not be applied for Prop Fac OCC bookings via Preliminary Booking order.

Workaround:

None

Root Cause:

SE-5737

Extent of Impact:

Impact on Existing Data

Recovery Method for Existing Data Affected

Problem:

Error message when running Multi Business Automatic Protection Order 'Incorrect Syntax near 'RESULT' - when saving to business after having proposals in previous run.

Solution:

Fix incorrect syntax to avoid stop in the Multi Business Automatic Protection Order

Workaround:

None

Root Cause:

SC-32

Extent of Impact:

Impact on Existing Data

Recovery Method for Existing Data Affected

Aim of function
Insured Name field for Light Policy is increased to allow for 1000 characters when created via Cede Interface

System Parameters affected:
None

Existing functionality affected
Cede Interface Order

Aim of function
Claimant Name field for Light Policy is increased to allow for 1000 characters when created via Cede Interface

System Parameters affected:
None

Existing functionality affected
Cede Interface Order