Release documentation - Life - Enhancements and requests

Problem:
MultiGAAP Accounting Order does not correctly create estimation worksheets according to Administration Condition (for the situation with discontinuous Account Numbers) and Period Estimates when changing Multi GAAP system parameter Estimation Frequency from Quarterly to Depend on Each Business and select Period Number According to the Calendar Time. 

Solution:
Multi GAAP Accounting Order should create correct estimation worksheet, according to Administration Condition and what is shown in Period Estimates. This should be correct also when you have changed Estimation Frequency in Multi GAAP system parameters from Quarterly to Depend on Each Business, and when Period Number According to the Calendar Time in system parameters is selected. 

Workaround:

Root Cause:

Extent of Impact:

Impact on Existing Data

Recovery Method for Existing Data Affected

Problem:
Abend in Life when adding rows in technical worksheet

Solution:
When there is no insured period selected on the technicial worksheet then do not check whether the flag Original Accounting Year and Period is selected on the business insured period when adding the first row and more than one row on the worksheet

Irrespective of whether the system parameter ''Original accounting period set on order' is selected or not or whether the flag 'Original Accounting Year and Period' is set on the business it should be possible to add several rows of booking on a technical worksheet for a closed ended or open ended business without an abend even when the insured period field is not selected

This is applicable to all levels of business

Declination Reason:

Workaround:

Root Cause:

Extent of Impact:

Impact on Existing Data

Recovery Method for Existing Data Affected

Problem:
Abend while creating cession when change the limit of the quota share is a table in the Pending Life Cycle and an Amount in the Definite Life Cycle status

Solution:
Always validate the limits on the cession based on the Definite Life Cycle status. Do not reference to the limits on the pending life cycle status for any kind of validation

When there is more than one amendment in the definite life cycle status always reference to the limits on the amendment within which the reinsurance start date of the cession falls under.

The system should not abend

Workaround:

Root Cause:

Extent of Impact:

Impact on Existing Data

Recovery Method for Existing Data Affected

Problem:
System abend while navigating section tab After classification added through amendment

Solution:
While navigating through the amendments either by clicking on the amendment icons or the effective period arrows on the structure tab or classifications only the values/ structure pertaining to that amendment should be displayed

I should be able to open any condition and the condition should reflect the values as per the selected amendment / effective period from which it is opened

Declination Reason:

Workaround:

Root Cause:

Extent of Impact:

Impact on Existing Data

Recovery Method for Existing Data Affected

Problem:
Total sum retroceded is calculating incorrectly on subsequent transactions when sequence number is same on multiple cessions

Solution :
When the system parameter ' Sequencing based on Sequence number' is selected and there are multiple cession transactions with the same sequence number then do the sequencing based on the cession identifier if there is a change in the SAR

When there is no change in SAR on subsequent transactions, the net sum retained and total sum retroceded should be copied from new business transaction

Declination Reason:

Workaround:

Root Cause:

Extent of Impact:

Impact on Existing Data

Recovery Method for Existing Data Affected

Problem:
On Retro claims Ceded percentage field and all other fields are calculating with incorrect values, When historical claim Flag is selected

Solution:
ACIs and all values on Retro Claims should be calculated using the value from the Ceded Percentage defined on the claim. If there is no value in the Ceded Percentage field, then the ceded factor/ percentage from the linked cession should be used. This is applicable for both claims with and without the historical claim flag

When there is more than one OCC on the cession then apply the ceded factor of each OCC to the ceded percentage and process the retro claims in that percentage for each retrocession

When the ceded percentage on the claim is overridden and not defaulted from the ceded percentage on the respective effective period of the cession then the following calculation should be done to proportionally allocate the claim liability

Calculate the proportional factor based on the retroceded percentage per retrocession cession as on the claim event date (or for historical claims, on the last active effective period on the cession)
The retrocession cession factor will be calculated as the retrocession cession SAR/ total retro SAR
When the claim is calculated, apply the ceded percentage entered on the claim to the claim liability (and all other values on the claim). This will be the total retro claim amount
To this total retro claim amount, apply the retrocession cession factor as calculated for each retroclaim per OCC

The RCPO should not pick up any claims that have a payment due date that is later than the period end date defined on the RCPO

The system should not abend

Declination Reason:

Workaround:

Root Cause:

Extent of Impact:

Impact on Existing Data

Recovery Method for Existing Data Affected

Problem: 
Need Unique IDs for all types of Lifes.

Solution: 
Need to add the FK Primary Life object and preferred Life Classification object in their respective folders 

Declination Reason:

Workaround:

Root Cause:

Extent of Impact:

Impact on Existing Data

Recovery Method for Existing Data Affected

Problem:
Walkback on running RPO/RCPO using SICS API server

Solution:
Do not trigger a full refresh when the RCPO or RPO is run through the APIs

Declination Reason:

Workaround:

Root Cause:

Extent of Impact:

Impact on Existing Data

Recovery Method for Existing Data Affected

Problem:
Options available in Reference data class dropdown are not in Alphabetical order in cession output pattern in automatic document handling  

Solution:
 When selecting the Reference Data class in the output pattern for cessions or claims the reference data values should be listed in alphabetical order.
On pressing a certain letter the option should default to the first value that starts with that letter and allow te user to scroll through all the other values that start with that letter

Declination Reason:

Workaround:

Root Cause:

Extent of Impact:

Impact on Existing Data

Recovery Method for Existing Data Affected

Problem:
System crash when trying to book on a Life Business in which previous IP do not have single accounts defined

Solution:
All accounting information related to the accounting year and period on the technical worksheet should default from the insured period that is selected on the technical worksheet

If there are no single accounts on the business the values should default to None and the values selected from the dropdown should be accepted on the created worksheet booking detail

The system should not abend

Declination Reason:

Workaround:
Define single accounts in all the insured periods

Root Cause:

Extent of Impact:

Impact on Existing Data

Recovery Method for Existing Data Affected

Problem:
System abends while creating Decrease transaction on cession having Unplaced amount.

Solution:
The decrease transaction should get the corresponding retrocession transaction when the RPO is run. Any change in the net sum retained/ retroceded/ unplaced should be updated in the decrease transaction using the inward cession sum at risk and the limits of the OCC similar to any other transaction and the system should not abend
 
Declination Reason:

Workaround:

Root Cause:

Extent of Impact:

Impact on Existing Data

Recovery Method for Existing Data Affected

Problem:
Residence Legal area is populated for Inward business in Ceded Cession

Solution:
Do not validate the residence country, residence country group, country or country group defined on the inward business while creating a cession with a ceded flag

The value that is mapped to the output pattern field Residence Country should be updated on the cession

On a manual cession it should be possible to select any country from the dropdown list without any validation against the AB classifications

Declination Reason:

Workaround:

Root Cause:

Extent of Impact:

Impact on Existing Data

Recovery Method for Existing Data Affected

Problem:
Ceded percentage defined on cession benefit is overridden after running RPO with surplus OCC

Solution: 
If the ceded percentage on the cession has been defined before the RPO is run, then do not update the value as per the ceded factor that is calculated after the RPO is processed.

The value input on the cession benefit should remain and this should be copied to the claim ceded percentage

Where the ceded percentage field is not available on the cession benefit, then the calculated value after the RPO is processed should be updated on the cession benefit

Declination Reason:

Workaround:

Root Cause:

Extent of Impact:

Impact on Existing Data

Recovery Method for Existing Data Affected

Problem:
Issues with Decrease and increase transaction created on Inward cession having unplaced amount.

Solution:
 Any retroprocessing should be done only after the RPO is run for any kind of transaction (except Reinstatement). This will include Increase and Decrease transactions also

When a cession transaction is created and whether there is an unplaced amount without a fac retrocession then the RPO should process the retrocessions for the transactions and update the linked retrocessions

When there is an unplaced amount that was retroceded with a Fac OCC, then only the Fac retrocession should be automatically updated with the corresponding transaction.
The existing treaty retrocessions should only be processed when the RPO is run

There will be no change to the value in the Unplaced Amount field if there is no change in the SAR
If there is a change in the SAR the unplaced amount and the net sum retained, retroceded will be updated, but this will not impact the existing fac retro

When the RPO is run the calculation of net sum retained/ retroceded should be calculated based on the retention and limits of the OCC for all transactions including increase/ decrease

Any existing fac retrocessions should not impact these figures

If there is no change in the retro sum at risk of the retrocessions, then the transaction will be created but no ACI to be calculated (similar to manual transactions where there is no increase in SAR)

Declination Reason:

Workaround:

Root Cause:

Extent of Impact:

Impact on Existing Data

Recovery Method for Existing Data Affected

Problem:
Unable to edit the ceded percentage on a non-historical claim

Solution:
Allow the overriding of the value ceded percentage on any type of claim
This should be possible through the loader and manually
The ACIs and other figures on the retro claim should be calculated based on the value in the ceded percentage field on the inward claim
If there is no value in the ceded percentage field on the inward claim then use the ceded factor from the cession benefit to calculate the retroclaim ACIs

Declination Reason:

Workaround:

Root Cause:

Extent of Impact:

Impact on Existing Data

Recovery Method for Existing Data Affected

Problem:
Several issues with Multiple Premium Tables- Premium is not calculating correctly when a prem rate or value table and rule is defined on PM condition

Solution:
When the LUT on the calculation rule and the LUT on the premium condition are not matched the error message 'One or more Lookup Tables defined on the PM condition do not match the Lookup Tables defined in the calculation rules' should be thrown

This is applicable to single LUT and Multiple LUT

The premium should not be calculated

When this happens on the cession loader- the cession should be created in provisional status (as per existing functionality where the premium and any ACI is not calculated)
When this happens on the RPO then the retrocession should be created without the premium ACI (as per existing functionality)

There should be no user intervention required when the cession loader or RPO throws this error message

If all the tables are matched then the premium should be calculated as per existing functionality

When the premium basis is Premium Rate or Value table AND there is a premium calculation rule- then always use the tables (there can be more than one table) within the premium calculation rule to arrive at the rate to be applied. Based on the rate that is defined on the table (percent permille fixed amount) and apply that rate to the SAR or RSAR (or any other parameter within the rule) on the cession to calculate the ACIs

When the Calculation rule includes any of the functions from 'Calculated Amounts' then do not apply the above logic- existing functionality should remain

Current Calculated Amounts are Premium Rate from Cession Benefit, Premium Amount from Cession Benefit and Split by Sum Insured Range. There can be more such calculated amounts, so any Calculated Amount should follow the rules as per the respective amount only.  

If there is no rule (None) then existing calculation logic should apply

Declination Reason:

Workaround:

Root Cause:

Extent of Impact:

Impact on Existing Data

Recovery Method for Existing Data Affected

Problem:
Retro claim not created when RCPO is run and the classifications related to country do not exist on the claim

Solution:
If the country that is defined on the claim is part of the country group that is defined on the PP, then the claim should be considered eligible as part of the RCPO

When the PP has both country and country group defined, then first check if the country on the claim is a subset of the country classifications, if not available, then check if it is part of the countries within the country group and if there is a match, then process the claim through the RCPO

If there is no country defined on the claim, then ignore this as a criteria while picking up the claim for processing through the RCPO

Declination Reason:

Workaround:

Root Cause:

Extent of Impact:

Impact on Existing Data

Recovery Method for Existing Data Affected

Problem:
System abends when creating historical claim through loader

Solution:
When the historical claim flag is selected on the loader the claim should be created without abend.
The claim event date should not be validated and it can be a date that is prior to the linked cession benefit start date
The ceded percentage field will accept an input and if it is not specified then the ceded percentage from the cession benefit's latest transaction will be copied to the claim

Declination Reason:

Workaround:

Root Cause:

Extent of Impact:

Impact on Existing Data

Recovery Method for Existing Data Affected

Problem:
System abends while running a Running RPO for SAR= 0 and Origin of Business = Coinsurance

Solution:
 When the Origin of business is Coinsurance and the SAR on the cession is 0 then copy the ceded percentage value to the all the retrocession cession created

In this scenario, since there is no Retro SAR calculation, there will never be a scenario where the retrocessions are done across more than one OCC
So the solution implemented on SE-16412 will never be applicable for any retrocession calculation.

Declination Reason:

Workaround:

Root Cause:

Extent of Impact:

Impact on Existing Data

Recovery Method for Existing Data Affected

Problem:
System showing wrong Validation Error message when trying to do a renewal transaction on a non-ceded cession.

Solution: 
For both ceded and non ceded cessions always through a confirmation message only when the effective date that is input is not the same as the defaulted renewal date for any renewal transaction

In the cession loader this message should be answered as yes by default and the cession should be created with the same date as input

The error message as per SE-11541 should remain- it should not be possible to renew a non ceded cession if the termination option is NOT existing business runs off and the cession is attempted for renewal after the termination/ cancellation date on the business

Background:
It was originally an error message for non-ceded cessions and this was removed as part of SICSC-7381. SE-14762 reintroduced the same error message for non-ceded cessions, but since this is now impacting clients who have used the flexible renewal dates for their existing policies (using the exact date as the renewal date instead of the next month irrespective of the number of days in the month)

Declination Reason:

Workaround:

Root Cause:

Extent of Impact:

Impact on Existing Data

Recovery Method for Existing Data Affected

Problem:
On Inward cession with classification as Coinsurance, ceded percentage is not updating for renewal transactions.

Solution:
On an inward cession with classification type = coinsurance, the ceded percentage will be input on the cession benefit.
If there is no input in the cession benefit then copy the ceded percentage value from the previous transaction
This value should be used to calculate the retro ACIs
The ceded factor that is calculated based on the retroSAR/inward SAR should never be used here since it may be 0 when the SAR = 0

 Declination Reason:

Workaround:

Root Cause:

Extent of Impact:

Impact on Existing Data

Recovery Method for Existing Data Affected

Problem:
Gross Sum Reinsured is not updating correctly on cession, when Sum At Risk our Share flag is unchecked.

Solution: 
On the Main tab of the manual cession wizard when the value on the field Gross Sum Reinsured is manually updated and there is no change manually done to the value in the field sum at risk- always default the value from the Gross Sum Reinsured to the Sum at risk
When the value in the field Sum at Risk is manually entered or overridden to be a value different from the Gross Sum Reinsured, then retain this value in the field

Declination Reason:

Workaround:

Root Cause:

Extent of Impact:

Impact on Existing Data

Recovery Method for Existing Data Affected

Problem:
Wallback generated to process claim reversal on a claim that does not exist

Solution:
When any status is loaded and the claim that is being referenced does not exist the system should not abend, the record should fail with the error message <claim reference number> not found

Declination Reason: 

Workaround:

Root Cause:

Extent of Impact:

Impact on Existing Data

Recovery Method for Existing Data Affected

Problem:
Premium tab condition – Min & Dep Premium is not displaying for both ‘Our share’ values and ‘100%’ values

Solution:
When the radio button Our Share is selected then the amount that is entered in the Minimum and Deposit Premium field should be displayed in the Min Premium Share and Dep Premium Share fields as it has been entered, without converting to the share percentage

When the offered, signed and written share are available on the business and there is only one life cycle status on the business, which is Signed- then only populate the value to the Signed%

If there is an offered and written share only and there is only one life cycle status, then only populate the value to the Written share

If there is more than one life cycle status then copy the value from the offered and written share from previous life cycle statuses to the next status until the status is offer accepted and the share is signed

Declination Reason:

Workaround:

Root Cause:

Extent of Impact:

Impact on Existing Data

Recovery Method for Existing Data Affected

Problem:
Failed Assignment window of RPO is listing all cessions that have a reinsurance start date outside the PP start date

Solution:
When the system parameter 'Use Reinsurance Start Date for Retrocession Processing' is selected

First check if the reinsurance start date of the cession falls within the insured period of the protection program

If the reinsurance start date falls within the IP of the PP, then process the cession benefit transactions through the PP irrespective of the transaction effective date

If the reinsurance start date is outside the insured period of the PP, then the cession and any of the benefits on the cession should not be picked up by the PP for processing even if the transaction effective period falls within the PP's active insured period.

Declination Reason:  

Workaround:

Root Cause:

Extent of Impact:

Impact on Existing Data

Recovery Method for Existing Data Affected

Problem:
UI/UX Unable to Expand Protection Program container when we click on Add more than one PP while creating RPO

Solution:
When the flag 'Add more than one PP ' is selected the PP container in the RPO should be visible and on right click you should be allowed to add more than one PP

Declination Reason: 

Workaround:

Root Cause:

Extent of Impact:

Impact on Existing Data

Recovery Method for Existing Data Affected

Problem:
 Abend when there are no countries in the country group and the RPO is Run'

Solution:
If there is no country as part of a country group on the OCC/ PP/ AB then treat the group as equal to Worldwide and validate any country that is part of the cession to be included in the PP/ OCC/ AB classifications. This is applicable to both RPO and RCPO

Declination Reason:

Workaround:

Root Cause:

Extent of Impact:

Impact on Existing Data

Recovery Method for Existing Data Affected

Problem:
System abends when creating subsequent transactions on cession without transaction code and issues with the display of the transaction code

Solution:
When the transaction date and a transaction code is mapped, then the mapped values should always be updated on the cession transaction that is created.

eg: When the date is 28- Feb -2011 and the mapped subsequent transaction has a transaction code and a transaction date of 28-Feb -2012, irrespective of the type of year, the created transaction should have the effective period 28-Feb-2012 with the mapped transaction code

When a batch for a subsequent transaction is loaded without a transaction code, and only a transaction date, then the subsequent transaction should be created by defaulting the transaction code as Renewal if the transaction date is the next defaulted renewal date and Other if it is any date other than the defaulted renewal date

Declination Reason:

Workaround:

Root Cause:

Extent of Impact:

Impact on Existing Data

Recovery Method for Existing Data Affected

Problem:
When we have migrated ACI's as '0' on the retrocession of an old business transaction then 'Lapse' and 'Other' transactions does not calculate correct ACI's.

Solution:
When the flag 'Old Business transactions as New Business' is selected on the PM condition of the OCC and the New Business transaction on the retrocession has 0 as the ACI

• Perform a calculation on the premium and related ACIs for the new business transaction using the rates/ rate tables/ amounts on the OCC
• Use this calculated amount to calculate the pro rata ACIs for the lapse or Other transaction that falls within the New Business transaction period

Declination Reason: 

Workaround:

Root Cause:

Extent of Impact:

Impact on Existing Data

Recovery Method for Existing Data Affected

Problem:
Find Business Partner window do not have the field for Identifiers

Solution:
In SICS Life similar to P&C: The Id type field should be made visible in the Find Business Partner window from wherever a business partner is accessed which includes the Partners module, Business Partner Ledger, Create Remittance, Assign Business Partner functions

Declination Reason:

Workaround:

Root Cause:

Extent of Impact:

Impact on Existing Data

Recovery Method for Existing Data Affected

Problem:
RCPO listing all the Claims in Failed Assignments tab which are created outside of PP effective period 

Solution:
When the system parameter 'Use Reinsurance Start Date while processing retrocessions' is selected :

Do not pick up any claim that is linked to a cession benefit that is part of a cession where the reinsurance start date is outside the effective period of the PP

Declination Reason: 

Workaround:

Root Cause:

Extent of Impact:

Impact on Existing Data

Recovery Method for Existing Data Affected

Problem:
Enhance Webservice to create Claim with status Ceded Paid. 

Solution:
The payment due date element should be made available in the create claim webservices similar to what is available on the Edit Claim webservices

When the payment due date value is entered for a claim that is not Ceded Paid or Ceded Outstanding, it should be ignored
When there is a value available on the webservice for the statuses 'Ceded Paid' or Ceded Outstanding then the claim should be created successfully with the payment due date updated on the created claim
All other fields such as Claim Liability, Accounted Liability etc will be defaulted from the cession benefit on the claim as per online functionality and there should not be considered mandatory

Declination Reason:  

Workaround:

Root Cause:

Extent of Impact:

Impact on Existing Data

Recovery Method for Existing Data Affected

Problem:
Adjustment transaction on the retro level is not correct for a supplementary transaction

Solution:
The adjustment ACIs created on the supplementary transaction of the retrocession should be (previous ACI * (1/previous number of lives))) with the opposite sign of the previous ACI

Declination Reason:

Workaround:

Root Cause:

Extent of Impact:

Impact on Existing Data

Recovery Method for Existing Data Affected

Problem:
 Incorrect calculation of Equivalent values on a QSR Limits table

Solution:
When there is a Quota Share Limits table attached to the L condition irrespective of the currency on the table the equivalent rate values should be calculated using the system currency when validating the cession autocover limits

This happens correctly for a Surplus Limits table

Declination Reason:

Workaround:

Root Cause:

Extent of Impact:

Impact on Existing Data

Recovery Method for Existing Data Affected

Problem:
Claim loading rejected by SICS when Claim Event date falls on the Policy Termination date

Solution:
Consider the start time of the claim event date while validating it against the policy termination date and the end time of the termination date. When the start time is < the end time of the termination date, then the claim should be created even if the date of claim event is equal to the date of termination

Declination Reason:

Workaround:

Root Cause:

Extent of Impact:

Impact on Existing Data

Recovery Method for Existing Data Affected

Problem:
While running batch through loader using submit job option then the sub batches created after execution of batch are having the duplicate identifiers 

Solution:
The sub batches for any failed records and the respective reject files for each sub batch should be created when the batch loader is run through the scheduler. Each sub batch and the reject file should have the respective identifiers based on the sub batch similar to what happens online

Declination Reason:

Workaround:

Root Cause:

Extent of Impact:

Impact on Existing Data

Recovery Method for Existing Data Affected

Problem:
On the Retro Claims, All the fields are updating as '0' even when Inward Claim has amount (The Inward Claim is created on a Cession with SAR=0)

Solution:
Always use the Ceded Percentage on the claim to calculate the claim ACIs and any other value when the RCPO is run. When there is no value in the Ceded Percentage field, then use the ceded factor on the linked cession benefit

Declination Reason:

Workaround:

Root Cause:

Extent of Impact:

Impact on Existing Data

Recovery Method for Existing Data Affected

Problem:
No Validation Popup's while saving RPO without attaching an AB in linked environment

Solution:
When the system parameter 'Sum at Risk Standalone Retrocessions only' is NOT selected:
Similar to when the system parameter is selected, always force the user to attach an Assumed business in the RPO
If the user saves the RPO without an assumed business throw an error message 'At least one assumed business is mandatory'

Declination Reason:

Workaround:

Root Cause:

Extent of Impact:

Impact on Existing Data

Recovery Method for Existing Data Affected

Problem:
Limits are not updating when amendment is created on share condition which makes incorrect validation on cessions

Solution:
 1. When the share condition alone is amended:
Recalculate all the values in the Limit condition (ceded share, our share of original) Available Reinsurance and Our Reinsurance using the amended share condition values even if the Limits are not specifically amended

2. When the Limits condition alone is amended:
Recalculate the amended limits using the existing share as on date of the amendmend

3. When both the Limits and Share are amended:
Use the amended share and the amended limits to calculate all the values in the Limits

Cession validations:
Always use the value that is available in Our Reinsurance (calculated based on the Quota Share Amount/ Available Reinsurance amount and our share of original/ ceded share as on the reinsurance start date of the cession to validate the autocover limits/ available reinsurance

Declination Reason:

Workaround:

Root Cause:

Extent of Impact:

Impact on Existing Data

Recovery Method for Existing Data Affected

Problem: 
ACI's calculated incorrectly for OTHER transaction when Retro SAR is Zero 

Solution:
Always calculate the pro rata adjustment ACIs when the Other transaction results in the Retro SAR becoming 0 based on the transaction effective period within which the Other transaction falls in using the elapsed duration of the premium and other ACIs already earned and the remaining duration within the effective period

When the SAR/ Retro SAR = 0 and the effective period is equal to the premium calculation frequency period, then calculate the ACIs as 0 where the ACIs are based on the sum reinsured/ retro SAR
Do not calculate any ACI that is defined as a flat amount/ flat extra/ fixed premium etc

This will be applicable for any prorata adjustment transaction that happens in the middle of an existing effective period where there are existing ACIs (eg Other, Increase, Decrease

For any transaction where there are no existing ACIs that need to be adjusted and the Retro Sum at Risk is 0, then no ACIs will be calculated.

For any cession where the Origin of business = Coinsurance and the SAR = 0, then force the user to manually enter the ACIs as per existing functionality

Declination Reason:

Workaround:

Root Cause:

Extent of Impact:

Impact on Existing Data

Recovery Method for Existing Data Affected

Problem:
Abend in Life on createWorksheet on combined DB when parameter 'Create Duplicate Technical Worksheet from Open Claim Worsheet' selected

Solution:
The system parameter ' 'Create Duplicate Technical Worksheet from Open Claim Worksheet' should be disregarded and bypassed in the Life environment on a Combined Database. It is not applicable to Life
When a Technical Worksheet is created through Webservices (on any level of business) in the Life environment in a combined database the worksheet should be created without an abend irrespective of whether the above system parameter is selected or not

Declination Reason:

Workaround:

Root Cause:

Extent of Impact:

Impact on Existing Data

Recovery Method for Existing Data Affected

Problem:
Values for the Claim is not copied to the retro claim

Solution:
Always copy the values for Smoker Status, Occupation Class, Occupation Code and Residence Country from the Personal Details tab of the inward claim to the retro claim and placement claims when the RCPO is run 

Declination Reason:

Workaround:

Root Cause:

Extent of Impact:

Impact on Existing Data

Recovery Method for Existing Data Affected

Problem:
Option Create facultative retrocession is available on retrocession window in Linked environment.

Solution:
The option Create Facultative Retrocession should never be available on the retrocession window when the system parameter 'Sum at Risk Standalone Retrocessions only' is NOT selected

Declination Reason:

Workaround:

Root Cause:

Extent of Impact:

Impact on Existing Data

Recovery Method for Existing Data Affected

Problem:
Limits are not recalculating when we amend Share condition on Child section of Assumed Business.

Solution:
When the share condition is amended on the child section then throw a warning message 'Please override the Proportional Limits condition and link it to the same amendment as the amended Share condition in order to recalculate the limits as per the amended share. Failure to do so may result in incorrect validations of the limits at the time of cession handling' 

This is applicable to QS, CQS and Surplus business

Declination Reason:

Workaround:
Amend the Limit condition also, without any change whenever the share condition is only amended 

Root Cause:

Extent of Impact:

Impact on Existing Data

Recovery Method for Existing Data Affected

Problem:
Cessions are validating with incorrect ACL, when Share condition is amended on Child section on CQS Assumed business

Solution:
 When the share on the child sections of the business are amended then the amended share should be applied to the respective limits condition of the child section

This is similar to the amendments on the agreement level

This is applicable to QS, CQS and Surplus business

Declination Reason:

Workaround:

Root Cause:

Extent of Impact:

Impact on Existing Data

Recovery Method for Existing Data Affected

Problem:
System is calculating incorrect Benefit expiry date on Retrocession cession when Expiry Age is given as 0 on inward Cession

Solution:
When the Expiry Age is set as 0 either through manual entry, tabbing or loading a 0 value, this should be ignored and considered as blank- field reset to blank and the expiry age and therefore the expiry date should never be calculated on the retrocession cessions 

Declination Reason:

Workaround:

Root Cause:

Extent of Impact:

Impact on Existing Data

Recovery Method for Existing Data Affected

Problem:
ACI's are not calculating for the Year which fall outside the defined value of Table of Reserve on SAR Decrement

Solution: 
Do not allow the transaction to be saved when there is no parameter as per the SAR reserve table

The the user should be forced to terminate the process. After the error message that the SAR cannot be calculated appears then when the user clicks on Save- with or without attempting to calculate the ACIs give a confirmation message 

'Sum at Risk cannot be calculated as per the defined decrement basis. ACIs will also not be calculated. Do you want to continue' 

The user can click yes- the transaction will be saved without the SAR being calculated and the ACIs that are dependent on the SAR

User can click No- the user will be forced to terminate the transaction

Cession Loader: Always answer this message as No- and reject the record

Declination Reason:

Workaround:

Root Cause:

Extent of Impact:

Impact on Existing Data

Recovery Method for Existing Data Affected

Problem:
'CANCEL FROM INCEPTION' transaction retrocession cession - the policy number and status does not change 

Solution:
When the status of the cession is Cancelled from Inception, Ceded in Error or Setup in Error, the corresponding full recapture should be effected on the retrocession cessions and placements if any and the policy number of the retrocession cessions and placements should also be updated as per the linked inward cession

Declination Reason:

Workaround:

Root Cause:

Extent of Impact:

Impact on Existing Data

Recovery Method for Existing Data Affected

Problem:
System Abends when attaching a LUT with Benefit Covered/Insurance product in Table of Reserve in SR condition decrement Basis. 

Solution: 
All parameters that are part of the SAR Reserve Factor Lookup Table should be considered when applying the decrement factor. The system should not abend

This is applicable for manual inward and outward cessions and also retrocessions created through the RPO

The rules for applying the parameters should be similar to a prop premium LUT

for example if the LUT has parameters such as benefit covered, insurance product, age, gender, occupation class etc (any valid LUT allowable column) and these values are available on the cession benefit- then the reserve factor corresponding to the combination of the columns should be applied

If any of the parameters are not available on the cession then the SAR calculation should fail with the message 'No value found for <parameter where the value is missing> as per existing functionality for any other type of table with missing values

If the SAR Reserve Factor Table has an insurance product or a benefit covered that is not part of the business classifications then at the time of attaching the LUT itself the message ' Invalid Insurance Product' should be thrown (for reference check attaching a prop premium or deduction table with  insurance products that are not part of the business classification)

Declination Reason:

Workaround:

Root Cause:

Extent of Impact:

Impact on Existing Data

Recovery Method for Existing Data Affected

Problem:
SICS abends when RCPO is ran after setting up and using Claim Liability Calculation Rule in OCC SR condition

Solution:
Fail the claims with the message Unable to apply Claim Liability Sum at Risk calculation rule if the calculation rule entered does not provide any result and the system should not abend

Declination Reason: 

Workaround:

Root Cause:

Extent of Impact:

Impact on Existing Data

Recovery Method for Existing Data Affected

Problem:
Validation message for Last name when IO created through loader is edited 

Solution:
Do not throw an error message asking for the last name as a mandatory field if there is a value in the field Full Name

This is applicable to both manual and loader created IOs

Declination Reason:

Workaround:
Manually add the last name while editing the IO

Root Cause:

Extent of Impact:

Impact on Existing Data

Recovery Method for Existing Data Affected

Problem:
System is sequencing joint life IO name randomly in a joint life cession 

Solution:
Always use the life that is mapped to the LIFE1_ID as the first life while creating the joint life insurable object for the first time. When the individual insurable object is listed in the joint life IO they should be listed in the order of creation and the name of the joint life IO should always have the name of the life mapped to LIFE1_ID first

While referencing this IO on later cessions, both (or all) lives within the joint life IO should be considered and should not be duplicated if the order of mapping is different in other cessions

Declination Reason:  

Workaround:

Root Cause:

Extent of Impact:

Impact on Existing Data

Recovery Method for Existing Data Affected

Problem:
Ceded Percentage Field is not visible for the Non Ceded Policy.

Solution: 
Extend the Ceded Percentage field to the non-ceded cessions also

The Ceded Percentage should be an input that is available and if there is no input in this field the value should be populated with the ceded factor once the RPO has been run

This is applicable to both manual and loader cessions
 
Declination Reason:

Workaround:

Root Cause:

Extent of Impact:

Impact on Existing Data

Recovery Method for Existing Data Affected

Problem:
On Inward cession ceded percentage field is not updating correctly, if we attach Fac retrocessions

Solution:
Update the total ceded percentage including the Fac Retrocessions on the field Ceded Percentage on the inward cession

Declination Reason:

Workaround:

Root Cause:

Extent of Impact:

Impact on Existing Data

Recovery Method for Existing Data Affected

Problem:
Deduction ACI's is not calculating for subsequent year if LUT table having policy year is attached on PM and deduction condition

Solution:
On an inward cession if the transaction is not New Business AND the Ceded flag is selected:

When there is a policy year on the cession that >1 

Create all premium ACIs with the entry code related to subsequent year premiums (existing functionality)

Create all deductions on the calculated premiums with an entry code related to subsequent year deductions using the LUT that is attached

When the Ceded flag is not selected:

Use the values from the LUT to calculate the deductions without validating the actual policy year

Declination Reason:

Workaround:

Root Cause:

Extent of Impact:

Impact on Existing Data

Recovery Method for Existing Data Affected

Aim of function

Allow to create estimation worksheets of Retrocessionaire’s Participation (ORP) according to the Account Number and Acc.As of Dates in the Administration Condition when the system parameter According to The Calendar Time is selected. 

Business value for customers

It is possible to create estimation worksheets of ORP directly use the information configured in the Administration Condition of each business  

System Parameters Affected

MultiGAAP/General/Estimation Frequency/Depend on Each Business/Period According To The Calendar Time.

MultiGAAP/Calculation Rules:

#FUNC getBookedAmountsForAccountingPeriodForEntryCodeGroup:  

 #FUNC getBookedEstimateAmountsForAccountingPeriodForEntryCodeGroup

Existing functionality affected

Administration Condition

Underwriters Estimates/Period Estimates

MultiGAAP Retrocession Order

Aim of function

The Aim of the function is to provide the option to create a new version of the existing standard ADH output patterns which can be then automatically updated on the existing transformation mappings

Business value for customers

When new fields are introduced or updated on an existing output pattern that is being used by existing transformation mappings, then when the new output patterns are generated as a new revision, then this revision may be automatically applied to all existing transformation mappings without any manual intervention

System Parameters Affected

ADH Document Handling

Existing functionality affected

When the new output pattern is generated via the 'Update Automated Document Handling Data', then if there had been updates to the previous standard output pattern, the user will be provided the option to create the new output pattern as a revision to the existing standard output pattern

If the option to create a new revision on the standard output pattern was selected, then the existing standard output pattern will get a new revision created

All existing Transformation Mappings can then be updated to this revision

Aim of function

The aim of the function is to be able to create all levels of business in SICS Life through webservices

Business value for customers

It will now be possible to create business through webservices without the branded products being the parent classification 

System Parameters Affected

None

Existing functionality affected

The existing create business webservices in SICS only supported the configuration where the parent classification was the branded product and all other classifications such as benefit covered and insurance product were defaulted based on the branded product classifications. 

With this enhancement it is now possible to create all levels of business in SICS Life through the create business webservice where the mandatory classifications under coverage are only Benefit Covered and Insurance Product and no branded products are in use

Aim of function

The aim of this enhancement is to extend the existing webservice retrieveAllAssumedBusinessesLinkedToPlacement to SICS Life

Business value for customers

This enhancement enables the user to Retrieve all the Assumed Business which are linked to the Outward Business through webservices.

System Parameters Affected

None

Existing functionality affected

The webservice retrieveAllAssumedBusinessesLinkedToPlacement that was currently only applicable to P&C is now available in SICS Life

This webservice will list all Assumed Business that are linked to the Outward Businesses 

Aim of function

Improve UX of SICS Life Screens in Cession and Claim areas.

Business value for customers

Improved Look & feel of SICS Life application.

System Parameters Affected

N/A

Existing functionality affected

N/A

Aim of function

The aim of this enhancement is to be able to default an additional classification based on the Reinsurance Method Indicator on the retrocession cession

Business value for customers

When an inward cession is retroceded through a protection program where there are two types of OCCs, Treaty and Facultative, then the additional classification that needs to be defaulted as part of the accounting classifications is now defaulted based on the type of treaty to which the cession is linked 

System Parameters Affected

None

Existing functionality affected

When a child dependency to an additional classification is defined on the reference data 'Reinsurance Method Indicator' then the child value will be automatically defaulted on the retrocession cession that is created on running the RPO

For example:

On an OCC of type 'P Auto' the defaulted Reinsurance Method Indicator will be Automatic

When a child value of an additional classification eg 'Treaty/ Fac Indicator' eg, Treaty is defined for this Reinsurance Method Indicator then when the Reinsurance Method Indicator on the retrocession cession is defaulted to Automatic the Additional Classification value of 'Treaty' is automatically updated even if the inward cession had any other value

Aim of function

The aim of the function is to allow a fixed ceded percentage to be applicable to retrocessions processed throughout the life cycle status of the cession

Business value for customers

For some customers, the ceded percentage set at the time of new business will be applicable throughout the life cycle of the cession irrespective of the change in the sum at risk. This enhancement will support this type of retrocession processing

System Parameters Affected

None

Existing functionality affected

When the system parameter 'Method of Retrocession is Reinsured Proportionally in Excess of Retention' is selected:

On the PL condition of the OCC a new flag 'Fixed Ceded Percentage throughout the lifecycle of the retrocession cession' is available for selection.

When this flag is selected the ceded percentage that is set at the time of new business status when the RPO is run will be applicable to calculate the retro sum at risk of all the subsequent retrocession transactions 

In this scenario, even when the sum at risk falls below the retention of a surplus OCC, the ceded percentage will continue to be applied and the sum at risk on the inward cession will be continue to be reinsured using the same ceded percentage

Aim of function

The aim of the function is to extend the handling of Facultative  Retrocessions that are linked to inward cessions

Business value for customers

This enhancement enables the users to link one or more Facultative retrocessions to the inward cession where the RPO has been run and an unplaced amount has been generated. 

It also allows more than one Facultative OCC to be attached to the RCPO whereby the claim recoveries for all the Facultative retrocessions linked to each OCC will be done

System Parameters Affected

None

Existing functionality affected

Cession :

Only when the SAR Decrement basis on the OCC is Top Triangle, then the Retro Sum at Risk on the Facultative Retrocessions will be reduced on Top Triangle basis when the Sum at Risk on the Inward Cession is decreased

On the inward cession, on the Retrocession Information tab a new field 'Remaining Unplaced Amount' is available

This field will display the value Unplaced Amount - Fac Total Sum Retroceded 

Retrocession Claims Processing Order:

On the Retrocession Claims Processing Order it is now possible to add more than one Facultative OCC
Running the RCPO will process the claim recoveries for all the facultative retrocessions that are linked to the listed OCCs

Aim of function

The aim of the function is to
a) Be able to perform automatic calculations of the Retro Sum at Risk using various SAR Decrement methods.

b) Include Lookup Tables in the Sum at Risk calculation rules

Business value for customers

This enhancement offers the flexibility to calculate the Sum at Risk to be considered for retrocession by using various calculation rules and Lookup tables

System Parameters Affected

In the Sum at Risk Calculation Rules, it is now possible to include Lookup Tables in the formula

Existing functionality affected

It is now possible to add a SAR Reserve Table or a Cash Surrender Value Table to the Sum at Risk Calculation Rules and include these tables as part of the SAR calculation when the Sum to be considered for retrocession is not equal to the value in the Sum at Risk field of the inward cession

When the Sum to be considered for retrocession is recalculated based on the SAR calculation rule, this value will be updated on the field Sum at Risk on the inward cession

Aim of function

To create a New Life Claim where the Claim ID and Cedent Reference number will accept the values up to 100 characters.

Business value for customers

To view the Claim Details with exact identifier. Moreover to find the claims with Cedent Reference Number and Claim ID with the identifier as defined and stored in the client databases. This functionality will help the client to update the claim records without compromising on their available formats.

System Parameters Affected

None

Existing functionality affected

Claim reference fields (CLAIM_ID and CEDENTS_REF) of Life Claim - Output Pattern will have the String Size increased from 20 to 100.
  

Aim of function

The aim of the function is to be able to Mass Close technical worksheets through the batch process from the Mass Update functions

Business value for customers

When there are several technical worksheets that have been created in an open status then it is possible to list and close all worksheets through a batch process

System Parameters Affected

None

Existing functionality affected

In the Mass Update sub module a new option  'Open Worksheets' is available

This will list all open worksheets that are linked to the businesses that are listed as per the selection criteria

The Listed worksheets can then be closed through the same update function

Aim of function

The aim of the function is to allow the policy Year and Deductible as Lookup Table Allowable Columns

Business value for customers

Customers will now be able to add the Policy Year and Deductible as lookup table allowable columns and use these fields within any type of lookup table which would use the values from the cession and retrocession cessions to calculate the ACIs or perform any other calculations 

System Parameters Affected

None

Existing functionality affected

Two new Lookup Table Allowable columns are available :

Policy Year- This will reference the field Policy Year on the cession benefit transaction

Deductible Range- This will reference the field 'Deductible' on the cession benefit transaction