Release documentation - Life - Enhancements and requests

Problem:
Original Accounting Year and Period - Issues with Copy, Reversal, Add Booking
Solution:

When the flag 'Original Accounting Year and Period' is selected on the Insured Period Tab of the AB or OCC, the following should be applicable to manually created technical worksheets and technical worksheets created through the orders where the copy, reverse function is applicable

1. The Original Accounting Year and Period values from the previous booking detail should be copied to all the booking details created on the TW when selecting Add Booking

2. When the worksheet/ balance/ detail is copied - copy the values in the field Original Acc Year and Period from the source bookings

3. When the worksheet/ balance/ detail is reversed- copy the values in the field Original Acc Year and Period from the source bookings and keep the field editable (similar to the booking year and period field)

4. When the worksheet/ balance/ detail is reversed and replaced- copy the values in the field Original Acc Year and Period from the source bookings and keep the field editable (similar to the booking year and period field)

Declination Reason:

Workaround:

Root Cause:

Extent of Impact:

Impact on Existing Data

Recovery Method for Existing Data Affected

Problem:

Abend when create TW in Life on Assumed Business protected by Prop OCC or STP

Solution:

When the account admin basis on the AB is Bulk and there is any protection attached on the Proportional Protection (PP condition) whether it is aSTP or a QS OCC and a technical booking is made on the assumed business the system should not abend- the bookings should be booked on the OCC in the retrocedd percentage as 'As Original' bookings

When there is a non Prop Protection (NP condition) - TW should be closed on the inward business without abend, there will be no bookings flowing to the non prop STP or OCC

Problem:

Mortality Factor with Reason for Loading = 'Above Free Cover Limit' does not flow to the Retrocession Cession from Inward

Solution:

The Loadings from the inward cession should be copied to the retrocession cession and placements
When the PM condition on the OCC is not Original, then the copied loadings should be used to calculate the extra premiums on the retrocession and placement cessions

When the reason for loading is 'Above Free Cover Limt' the same calculation as per the inward cession should be applicable on the retrocession cessions and the Extra Premium should be calculated on the retrocessions

Declination Reason:

Workaround:*

Root Cause:

Extent of Impact:

Impact on Existing Data

Recovery Method for Existing Data Affected

Problem:

Underwriters Estimates calculations using calculation variables for Basic Multiple Extra Commission or Flat or Per Mille Extra Commission give an error message when the flag 'Same As For Basic Premium' is selected in the Deductions condition/Extra Premium Commission tab

Solution:

Calculate zero in the above situation, without giving any error message.

Note: The calculation variables do NOT retrieve values from the Basic Premium. Such functionality is not supported, and will not be implemented in this case. 

Workaround:

Define the extra premium exactly as per the definition on the Basic Premium Tab

Root Cause:

Extent of Impact:

Impact on Existing Data

Recovery Method for Existing Data Affected

Problem:
When change SICS login password, including special characters is not allowed.

Declination Reason:
This is just standard Oracle functionality. If any specific functionality were required then this would be an enhancement.

If the password is not enclosed in quotes then it can include any letter, any digit, '_', '#' or '$' characters. Only a letter can be used in the first character, the other characters can be used after that. If on the other hand you enclose the password in quotes then you can use any character in any position.

Workaround:

Root Cause:

Extent of Impact:
Changing password on Oracle DB

Impact on Existing Data

Recovery Method for Existing Data Affected

Problem:
Premium calculation wrong with short-term premium rate table
Solution:
Use the short term range while calculating the premium based on the number of days in the premium paying term

Declination Reason:

Workaround:

Root Cause:

Extent of Impact:

Impact on Existing Data

Recovery Method for Existing Data Affected

Problem:

Abends while generating DD Record Def.

Verification Steps ( How to recreate the error):

 SICS4LIFE@CSCDBSOSL003V - b4211ga

• Open Life System Admin Desktop.

• Goto Inbound Interfaces -> Migration Toolkit -> CSV File Utilities
• In Generate Files Tab -> Go to DD Record Def.
• Enter CSV file path and click on Generate [*ABEND*]

java.lang.IndexOutOfBoundsException: Index 0 out of bounds for length 0java.lang.IndexOutOfBoundsException: Index 0 out of bounds for length 0  . . .  com.csc.sics.lf.migration.roledefinition.SicsLfMigrationAbstractRole.getLastRootChainForSequence(SicsLfMigrationAbstractRole.java:522) at com.csc.sics.lf.migration.roledefinition.SicsLfMigrationAbstractRole.isExtractedBefore(SicsLfMigrationAbstractRole.java:576) . . .

Solution:

System should not give abend and should work as per existing functionality.

Workaround:

The client could use this now, not in one year when correction released

Root Cause:

In case SE-3437, %BusinessSteppedSlidingScaleElementManagementExpense was added as leaf without any owner/root, due to typing mistake.
As a result default migration sequence i.e. 0 was assigned to it.

When we click on generate 'DD Record Def.', it starts sorting. all SicsLfMigrationDefinition elements
While sorting system tries to get owner/root from empty list of owners of %BusinessSteppedSlidingScaleElementManagementExpense.
Which causes 'Index 0 out of bounds for length 0'

Extent of Impact:

Impact on Existing Data

Recovery Method for Existing Data Affected

+Problem:

Add Business option on Life Cession Related Orders

Solution:
Add Business option to be made available on the following orders

Cession Renewal Order
Cancel Cessions Order
Renewal Order for Fac Standalone Retrocessions
Replace Informational Renewals
Terminate Cessions
REtrocession Processing Order - ONLY WHEN THE SYSTEM PARAMETER 'STANDALONE RETROCESSIONS ONLY IS NOT SELECTED'

Workaround:

Root Cause:

Extent of Impact:

Impact on Existing Data

Recovery Method for Existing Data Affected

Problem:
An error message when runing RPO if PM condition has calculation rule

Solution:

The premium should be calculated as per the calculation rule defined on the respective levels of business. No error message should be thrown when the Premium calculation is being done on the outward business and the inward business calculation rules should not be validated by the RPO

Declination Reason:

Workaround:

Root Cause:

Extent of Impact:

Impact on Existing Data

Recovery Method for Existing Data Affected

+Problem:

When creating a new Cession Renewal Order through Copy Order option SICS automatically change Renewal year as latest year after a full refresh

Solution:
SICS should pick the detail as it is from the original order which is copied including the year and month. The year should not be automatically updated to the current year after a refresh on a cession renewal orjder

Declination Reason:

Workaround:

Root Cause:

Extent of Impact:

Impact on Existing Data

Recovery Method for Existing Data Affected

Problem:
Group Scheme No of Lives, Male expiry age and Female expiry age data size error.
Solution:

Group Scheme Number of Lives field should accept up to 10 digits
The output pattern field on the cession loader should be increased to default to accept up to 10 digits

Male Expiry Age and Female Expiry Age should accept up to the age 999 similar to the Expiry Age on the main cession

Declination Reason:

Workaround:

Root Cause:

Extent of Impact:

Impact on Existing Data

Recovery Method for Existing Data Affected

Problem:
Free Cover Limit Extra Premium not calculated correctly when SI-FCL> Auto Cover Limit

Solution:
Rule:
When (Sum Insured – FCL) > Auto Cover Limit, then ‘Auto Cover Limit’ is to be considered down the line for calculation of Extra Mortality Premium

Declination Reason:

Workaround:

Root Cause:

Extent of Impact:

Impact on Existing Data

Recovery Method for Existing Data Affected

Problem:

Solution:

Declination Reason:

Workaround:

Root Cause:

Extent of Impact:

Impact on Existing Data

Recovery Method for Existing Data Affected

Problem:
System is throwing error for Joint Life Name allowable size

Solution:

Increase the size of the Joint Life Insurable object to 300 characters from 80 i.e to accommodate the maximum number of characters for two individual lives with a first name last name and middle name of 50 characters each

When the size exceeds 300 characters in case of more than two lives with 150 char names each, reject the IO name similar to what happens online
Declination Reason:

Workaround:

Root Cause:

Extent of Impact:

Impact on Existing Data

Recovery Method for Existing Data Affected

Problem:

Multi GAAP Recalculation Order does not create Period Estimates on Retrocessionaire's Placements in SICS Life

Solution:

When Multi GAAP Recalculation Order is run on Level of Business = Outward Cedent's Contract and Retrocessionaire's Placements, the Order should add the Period Estimate Currency both on the Outward Cedent's Contract and the corresponding Retrocessionaire's Placements

++Workaround:

Root Cause:

Extent of Impact:

Impact on Existing Data

Recovery Method for Existing Data Affected

Problem:

System Abend when click on Main,SAR & ACIs button if AB & Cession both have not update calculation frequency for Premium

Solution:

When there is no Renewal Frequency defined on the cession and the user presses the Main OR SAR button OR the ACI button and saves the cession benefit, the validation error message 'Renewal Frequency is required' should be thrown 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:
System incorrectly creating duplicate benefits on the same cession through loader

Solution:
When there are identical / duplicate i.e when the policy number, cedent cession id, all the life ids, all benefits covered and insurance product is the same then the records should be rejected with the error message LCH018

In case the batch has both identical and non-identical records, then the non-identical records should get loaded and these identical records should get rejected through batch. And they should appear in the sub batch.

If there are two different insurable objects on the policy record and the mapping has been done to create a joint life insurable object, then the cession should be created with the joint life IO and the benefits should be created on the same cession against the respective individual IOs as per existing functionality

Declination Reason:

Workaround:

Root Cause:

Extent of Impact:

Impact on Existing Data

Recovery Method for Existing Data Affected

Problem:

Multi GAAP calculation functions 'Booked amounts for Original Accounting Period' does not retrieve bookings correctly when Estimation Basis is set to Booking Year in Multi GAAP/General system parameter

Solution:

Make sure the functions retrieve bookings from the Business Ledger with an Original AccYr and Original AccPeriod equal to the accounting period in the Period Estimates

Workaround:

None

Root Cause:

Extent of Impact:

Impact on Existing Data

Recovery Method for Existing Data Affected

Problem:

Unable to add more than one PP in the RPO

Solution:

When the Allow more than one PP option is selected the option Add Business should be enabled after adding one PP
Selecting this option should allow the user to add PPs from the Find Business window

Declination Reason:

Workaround:

Root Cause:

Extent of Impact:

Impact on Existing Data

Recovery Method for Existing Data Affected

Problem:
The cession details on worksheet are not aggregating based on the entry codes

Solution:

When the cession or retrocession cession order is run, the balance details should be aggregated within each section/ insured period/ accounting year and period/ original accounting year and period- on the basis of the entry code
When the balance details are viewed from the open cession worksheet or from the view balance details on the close worksheet window or on the details container of the business ledger, the details should be aggregated per entry code
On right click -> View cessions the list of all cession benefits comprising of this aggregated balance should be listed

Declination Reason:

Workaround:

Root Cause:

Extent of Impact:

Impact on Existing Data

Recovery Method for Existing Data Affected

Problem:

When a Period Estimate currency is added to an Outward Cedent's Contract, the Period Estimates are not automatically added to the placements

Solution:

When a Period Estimate currency is added to an Outward Cedent's Contract, I should be given an option to add the same Period Estimate currency on all placements.

Workaround:

Add the Period Estimate currency manually on each placement

Root Cause:

Missing in original implementation

Extent of Impact:

Impact on Existing Data

Recovery Method for Existing Data Affected

Problem:

When system parameter 'Create Retro Link Of Source Business' is selected, and a Source Assumed Business is selected on the Assumed Businesses window of an Outward Cedent's Contract, the system should automatically create a link to the selected assumed business when running Multi GAAP Retrocession Order and when creating a manual technical worksheet on the OCC. 

This does not work for manual technical worksheets if the OCC has multiple Insured Periods. Instead, AC0551 is given, asking the user to link the booking details to an insured period on the protected business. 

Solution:

Make sure the system automatically make a link to the Source Business defined for each insured period on the OCC

Workaround:

Root Cause:

SE-1661

Extent of Impact:

Impact on Existing Data

Recovery Method for Existing Data Affected

Problem:
Calculation of SAR on Cession Transaction New Business to be reviewed

Solution:

When the Benefit Term is less than the duration of the renewal frequency period (i.e if the renewal frequency = Yearly and the benefit term is less than 365 days or if the renewal frequency is Quarterly and the benefit term is less than 90 days etc), do not attempt to recalculate the Sum at Risk when the SAR button on the cession benefit is applied
The ACIs will be calculated for the Sum at Risk as entered/ available on the Sum at Risk field on the cession benefit

Declination Reason:

Workaround:

Root Cause:

Extent of Impact:

Impact on Existing Data

Recovery Method for Existing Data Affected

Problem:
Loader Should Allow 'Cede Paid' status Claim to be Uploaded with Empty Correspondence Date and Notification Date

Solution:

Do not validate the Correspondence Date and Notification Date or Claim Cause of Loss and Claim Cause of Loss Group on a claim that has the status of Ceded Paid
The fields should not be mandatory both manually or through the loader
If there is a Correspondence Date or/and Notification Date entered- do not validate them against each other or the claim event date

Declination Reason:

Workaround:

Root Cause:

Extent of Impact:

Impact on Existing Data

Recovery Method for Existing Data Affected

Problem:
Increase the maximum UDF fields (DATE and STRING data type) on SICS Claim and Cessions

Solution:
Increase the number of UDF fields for String and Date on cession, and Claim from the existing 5 to 10

This should be applicable to manual cessions, and claims - both inward and outward- OCC level and placement level
New output pattern fields in the claim and cession output pattern
The objects should be part of the BO Universe
The fields should be part of the MTK objects

Declination Reason:

Workaround:

Root Cause:

Extent of Impact:

Impact on Existing Data

Recovery Method for Existing Data Affected

Problem:
Abend when the ID type, ID IO of second life is blank in the loader file

Solution:

If any one or more fields in addition to the LIFE_ID_TYPE are mapped in a joint life block then the joint life block will be considered as expected to create a joint life insurable object and will need to be validated for the following mandatory fields

LIFE_ID
LIFE_FULL_NAME or LIFE_FIRST_NAME or LIFE_LAST_NAME or LIFE_MIDDLE_NAME
LIFE_GENDER
LIFE_DATE_OF_BIRTH

If any one of these fields is not available then the record should fail with the message 'Missing Mandatory field <Missing field name> in the Joint Life Block'

If only the LIFE_ID_TYPE is mapped and there is no other data mapped to the joint life block, then the joint life block should be ignored. If there is no other Joint Life block, then the cession will be created as an individual insurable object. If there are other joint life blocks with all the mandatory information, then the joint life IO and cession should be created using those values and the block with only the LIFE_ID_TYPE will be ignored

Declination Reason:

Workaround:

Root Cause:

Extent of Impact:

Impact on Existing Data

Recovery Method for Existing Data Affected

Problem:

The Last Projection Year defined on an Outward Cedent's Contract is not reflected on the Retrocessionaire's placements

Solution:

Last Projection year on the Retrocessionaire's placements should always be copied from the Outward Cedent's contract and should not be possible to overwrite on the placement

Workaround:

Root Cause:

Extent of Impact:

Impact on Existing Data

Recovery Method for Existing Data Affected

Problem:
The flag ‘Allow Partial Processing of Cession Batch’ is not getting displayed on the batch, for both open and closed ended business.

Solution:

The flag 'Allow Partial Processing of Cession Batch' should be copied from the selection on the Business tab of the business insured period that is selected on the cession batch.

Declination Reason:

Workaround:

Root Cause:

Extent of Impact:

Impact on Existing Data

Recovery Method for Existing Data Affected

Problem:

Adjustment Reversals are not generated on Cession via Loader

Solution:
When the system parameter Cession- >Allow Transaction Number on Cessions is selected
When there is a transaction 'Adjustment Reversal' with the corresponding transaction number loaded as part of a cession batch the adjustment reversal should be created on the relevant transaction
The linked Retro and the placements should be automatically reversed with a corresponding 'Adjustment Reversal' transaction and the all the ACIs should be reversed on this reversal transaction

Declination Reason:

Workaround:

Root Cause:

Extent of Impact:

Impact on Existing Data

Recovery Method for Existing Data Affected

Problem:
Retrocession are not generated for Maturity transaction

Solution:

When the Ceded flag is selected- for any termination transaction on the inward cession a full recapture should be generated on the outward cession

Declination Reason:

Workaround:

Root Cause:

Extent of Impact:

Impact on Existing Data

Recovery Method for Existing Data Affected

Problem:
Amendment not picked up correctly by RPO

Solution:
The RPO should process the retrocession cessions based on the amendment effective period to which the cession benefit transaction is linked to.
If the amendment is set to affect existing cessions, then the existing cession transaction date should be used to refer to the relevant amendment on the OCC

Declination Reason:

Workaround:

Root Cause:

Extent of Impact:

Impact on Existing Data

Recovery Method for Existing Data Affected

Problem:

Premium Paying Term incorrect on inward cession transactions and on retros

Solution:

When the Premium Paying Term is explicitly mapped/ input, this value should not be updated based on the benefit term- this is applicable for both NB and Other and Extended Term

The PPT should be copied from the inward cession to the outward cessions and the placements- This is applicable for both Linked Retros and Standalone Retros (with and without the ceded flag)

Declination Reason:

Workaround:

Root Cause:

Extent of Impact:

Impact on Existing Data

Recovery Method for Existing Data Affected

Problem:
Abend when processing an Adjustment Reversal on a New Business Transaction

Solution:

When an Adjustment Reversal transaction is created (both manual and through loader)

If the transaction being reversed has a transaction code of 'New Business' or 'Old Business' then the adjustment reversal transaction should not be allowed
SICS should stop the transaction with a message 'Adjustment Reversal transactions cannot be processed on the first transaction of the cession benefit. Please terminate the cession benefit with a Ceded In Error/ Setup In Error transaction'

Declination Reason:

Workaround:

Root Cause:

Extent of Impact:

Impact on Existing Data

Recovery Method for Existing Data Affected

Problem:
Decimals incorrectly calculated when SAR is 'Our Share' resulting in incorrect retros

Solution:

When the system parameter Cession Sum at Risk amounts in decimals is NOT selected:
The Sum at Risk should be rounded off to 0 decimals irrespective of whether it is calculated in Our Share figures or not
This rounded off sum at risk should be use to calculate the Retention and Sum to be retroceded

Declination Reason:

Workaround:

Root Cause:

Extent of Impact:

Impact on Existing Data

Recovery Method for Existing Data Affected

Aim of function

The aim of this enhancement is for the cession loader to handle blank column headers or duplicate column headers during the import process and allow the user to import the input file with blank column headers or duplicate column headers and allow the user to create mappings

This epic has covered the detailed specification of the requirement

System Parameters Affected

None

Existing functionality affected

None

Aim of function

The aim of this enhancement is to be support calculating and accumulating the Sum at Risk amounts to up to 6 decimals and processing the retrocession cessions and applying the ceded ratio on the sum at risk figures that have 6 decimals

System Parameters Affected

New system parameter where the user is allowed to define the number of decimals that can be accepted on any of the Sum at Risk fields is available. You can define a value to accept up to 6 decimals

Existing functionality affected

Depending on the number of decimals that have been selected on the system parameters, the following values on a cession benefit will accept upto and round off the entered amount to that many decimals.

The accumulated Sum at Risk will be calculated in decimals and the retroceded sum at risk will be calculated using this SAR amount

Aim of function

Summary:
A New Claim Recovery Calculation Rule for Wavier of Premium Rider Policy

Description:
Currently, the client only has one claim recovery calculation rule, and this rule is applied to all insurance policies.

Since the claim ACI figure for the wavier of premium rider (WPR) policies are calculated differently from other policies in client's old system (LA), and as a result, the existing claim recovery calculation rule cannot produce the expected result for WPR claims.

Hence, client needs a different calculation rule for WPR claims. Client expects SICS to be able to apply different calculation rules based on the following two new fields they will provide to SICS.

Two new fields client will pass into SICS:
No. Name Expected Value from the Client
1 Claim Percentage 0% ~ 100%, and most of the time will be 100%
2 Claim Type 'T' for regular claim (use the existing claim calculation rule),
'P' for WPR claim (use the new WPR claim calculation rule).

The calculation rule for WPR claims (with the Claim Type of 'P'):
WPR Claim Recovery = Retroceded SAR * Claim Percentage (the new field stated above)

System Parameters Affected

N/A

Existing functionality affected

N/A

Aim of function

The aim of this enhancement is to be able to use the Original Transaction Date on the cession benefit transaction as the first criteria for sequencing the cessions through the Retrocession Processing Order

System Parameters Affected

A new system parameter 'Sequencing Based on Original Transaction Date' is available when the system parameter
'Method of Retrocession is Reinsured Sequentialy in Excess of Maximum Retention' is selected.

This system parameter may be selected in addition to the system parameter 'Include Policy Number in Sequencing' or independently.

Existing functionality affected

When the above mentioned system parameter is selected, on each cession benefit transaction a new field 'Original Transaction Date' is available.

This field will be defaulted to the effective period start date and can be overridden while manually creating each transaction or when creating the cession benefit transaction through the cession loader

When the RPO is run, the cessions will be sequenced based on the Original Transaction Date rather than the Reinsurance Start date or the Transaction Effective Date of each transaction.

Aim of function

The aim of this enhancement is to be able to include Reinsurance Program in a Cession Renewal Order so that all the cessions that are linked to all the Assumed Businesses under the Reinsurance Program are renewed

System Parameters Affected

None

Existing functionality affected

The Cession Renewal Order will now have the option to select a Reinsurance Program
When selected all the Assumed Businesses that are part of the Reinsurance Program are listed
When a Reinsurance Program is selected it will not be possible to list or add Assumed Businesses that are not linked to a Reinsurance Program

On running the Cession Renewal Order all the eligible cessions linked to all the Assumed Businesses that are part of the Reinsurance Program will be renewed for the month and year specified in the order

Aim of function

When the premium paying term or the benefit term is entered in days up to a maximum of 365 days (366 for a leap year), they value should remain as entered and this value should be used to calculate the ACIs when the tables that are used for calculation use the term in days as one of the parameters.

This epic addressed the specification part of the requirement

System Parameters Affected

None

Existing functionality affected

None

Aim of function

The aim of this enhancement is to be able to create a reject file when a cession batch is partially rejected. This reject file should be created in the same format as the original input file and it should be reusable as is, once the errors are resolved

System Parameters Affected

None

Existing functionality affected

When a cession batch has been partially closed and a child batch is created for the error records, a reject file having the some name as the originally imported inforce file will be created and saved in the same location as the original import file. This file will be in the same format as the original file and will have the same name with a suffix _ rejected records.
This reject file can be imported again as it is once the underlying errors are resolved and it will match to the same mapping/s as the original import file did.

Aim of function

The aim of this enhancement is to be able to handle subsequent amendment and termination transactions on cessions linked to a Reinsurance Program when created through the cession loader

System Parameters Affected

None

Existing functionality affected

When a cession benefit transaction such as a renewal, other, or a termination such as a lapse pertaining to a cession that is linked to a more than one layer (assumed business) on a reinsurance program is processed through the cession loader, then this transaction will be updated on all the cession benefits. Each transaction will use the terms and conditions as defined on the respective assumed business sections to which the cession benefit is linked

Aim of function

The aim of this enhancement is to be able to create an Adjustment Reversal transaction on a Ceded Paid Claim and reverse any Retrocession Claim that was recovered
This epic has covered the detailed specification of the requirement

System Parameters Affected

None

Existing functionality affected

None

Aim of function

For clients who use both 'Ultimate' and 'Yearly' Projection Bases for estimates, it may be required to use Projection Basis as an extract criteria for Estimation Complete Mass Update and Multi GAAP Stop Calculation Mass Update. We have therefore added Projection Basis as an extract criteria for these two Mass Updates

System Parameters Affected

None

Existing functionality affected

Create and run Estimation Complete Mass Update
Create and run Multi GAAP Stop Calculation Mass Update