Release documentation - Life - Enhancements and requests

Problem:

When selecting Cease Accounting, the Cease Description shows None

Solution:

In SICS LIFE the Reference Data 001076 should be available, similar to P&C. This is applicable to standalone and combined DB

FOR BOTH LIFE AND P&C

When the Cease Accounting flag on the business insured period is selected and the defaulted value of none is overridden with a free text field, the overridden value should remain for each insured period's cease accounting description

When the Cease Accounting is set on the Business level and a value from ref data 001076 is selected this value should only be applicable to the Business Cease Accounting and the values that were defined on the insured period description should remain

Existing behaviour when the insured period or all insured periods are commuted should remain

Problem:

Add Reinsurance Program from assumed business not possible from proportional treaty and proportional facultative

Solution:

It must be possible to link all Proportional Assumed Business Life Type Of Businesses to Reinsurance Program starting the process from the inward side when the process is initiated from the Life Cycle tab

The option Add Reinsurance Program should be enabled and once selected it should create and link the Reinsurance Program to the Assumed Business
If an AB is already linked to a reinsurance program then the option should be disabled

Should work in the same was as it currently works for NP Auto and NP Fac businesses

Problem:
Combined Quota Share/Surplus cannot be linked to reinsurance program due to message BR0038

Solution:

Both Manually and through Webservices it should be possible to link Assumed Business with Reinsurance Product 'Combined Quota Share/Surplus' to the PT part of Reinsurance Program in the same way it is currently possible to link Surplus or Quota Share businesses.
When the cession batch is loaded against a reinsurance program where the AB is a Combined QS/ Surplus the batch should be loaded and the cessions validated as per the manual functionality against the limits

Problem:
SICS Documentation for SICS 24.4 - enhancements and bug fixes page is empty

Solution:

Update the documentation for bugs and enhancements and ship an updated SICS Docs in a 24.4 SSP

Problem:

Additional Classification (Code) objects - List of values are not in proper sequence for Life Universe.

Solution:

Need to fix the SQL of LOVs of few Additional Classification code objects like Additional Classification 2(code), Additional Classification 5(code) etc which are not in correct sequence.

Note: The correct sequence should be ‘Code’ comes before ‘Name’.

Problem:

Access Code message SICS0026 when changing user roles (even for Edit and Assign/revoke user role).

Solution:

The Message 'SICS0026' should not be popped-up when the operations Assign/ revoke User Roles performed. This message should only be triggered when Access Code is actually changed.

Problem:

Web Service retrieveObject generating walkback in SICS Life

Solution:

The retrieveObject web service should retrieve all the relevant objects as per the soap and should not abend

Problem:

 On Webservices, Missing elements to define the 'Accounting Options' fields and Reinsurance Brokerage fields on the createLfbusiness/UpdateScopeofCover.

Solution:

Elements to Add Accounting Options and Reinsurance Brokerage when the Business Partner of type Broker is attached should be available in the Create LfBusiness/ UpdateScopeofCover webservices for Life
All elements should be as per the fields currently available in the online function

Problem:

System abends on updating the Deduction condition of Non Prop Business.
 

Solution:

The non Prop Deduction condition has to be updated manually or through webservices without any abend
 

Problem:

Performance issue with Retrocession Cession Order

Solution:

Update the query to reduce the lag in performance of the RCO

Problem:

Cession batch fails with 'Validation with Error' when batch is created with Reinsurance Program.
 

Solution:

 When the SAR Calculation Frequency is Original then always create the cessions through one or more of the ABs when the batch is loaded against a Reinsurance Program

Do not attempt to calculate the SAR on each cession transaction and use the SAR as mapped as it is when creating the cession benefit transactions

Problem:

Limit condition is saved without defining Premium definition where Priority basis is premium

Solution: 

When the priority type on the Stop Loss type of business is defined as permille or percent, permillion then while creating the condition itself the Premium Defintion options should be displayed. The radio button Gross and the Accounted Status should be defaulted to Accounted and be selected by default and the user should be allowed to change it to any other selection. The same selection that has been made for Priority should always default to Capacity or vice versa

Problem:

Failed to upload transaction 'Reinstatement with Update' transaction

Solution:

 The reinstatement with update transaction should be allowed when the effective date of the transaction is equal to or later than the date of termination

If the date is later than the date of termination there should be a termination period from the date of termination till the date of reinstatement created on the cession benefit and an active effective period from the date of reinstatement to the end of the next effective period (based on the calculation frequency of the cession benefit)

Problem:

Trans_date of 'Adjustment Reversal' does not follow the value in upload file

Solution:

For all inward cession transactions when the transaction is loaded through the cession loader update the Original Transaction Date with the mapped value. Only when there is no mapped value the original transaction date should be defaulted to the transaction effective date.

The Original Transaction Date on the retro transactions should always be copied from the inward cession transactions. This is applicable to all amendment and termination transactions

Problem:

Trans_date is NULL for auto reverse transactions

Solution:

For all automatically reversed cession transactions the original transaction date should be defaulted to the transaction effective date of the source transaction. If a value is mapped, then use this value.

The Original Transaction Date on the retro transactions should always be copied from the inward cession transactions. This is applicable to all amendment and termination transactions

Problem:

System is not creating automatic renewal on running the RPO.
 

Solution:

Similar to a manual retroprocessing the automatic renewals including informational renewals for future renewal dates should be created on the cession benefits once the first transaction has been retroceded when the RPO is run. This will be applicable when 1)The data calculation period on the NC conditions has been defined as a value other than 'Original', 2) The Calculation responsibility is Reinsurer 3) The PPremium Accounting Task is with the reinsurer / base company business partner.

Problem:

The SAR Decreement Value is not calculating on the Cession when the Benefit Term is in Years and Days
 

Solution:

When the SR condition on a business section is saved with the decrement basis as Table of Reserves throw a warning message 'SAR Reserves will be applied on the cession benefits only when the benefit term on the cession benefits is defined in whole years.'
This will be just a warning message and the condition should be saved once the user clicks on OK.
 

Problem:
Claim ACI status on Placement level getting changed to Suspended post running RCPO.

Solution:

  All ACIs on the placement claims for all statuses should be released when they are created when the RCPO is run

Problem:

When merging insurable object fk_primary_life column of lf_cession table becomes null

Solution:

When one or more IOs are merged and a new IO is created out of the merged IO then do not set the primary life value to null on any of the cessions that were linked to the source IOs that are now linked to the merged IO. The values for the primary life and all the other lives on the joint life cessions should follow the new identifier that has been created

Problem:

Cession batch abends when Limits are defined with 'zero' amount on quota share business.

Solution:

When the limit condition on the Quota Share OCC or Assumed Business is defined without at least one row of limits (there should always be a limit defined) or the values are entered for the limits are 0 in both the Cedent's retention and the Quota Share Amount field (which will result in Our Reinsurance and Available Reinsurance also being 0) then throw an error message 'The Cedent Retention and the Quota Share Amount fields both cannot be 0' This is applicable to all limits defined in different currencies if applicable

When the Quota Share Limit is defined as a Lookup Table, then at the time of defining the table if there are 0 values for both % or amount throw an error message 'Value cannot be 0 for both fields'
 

Problem:

While creating RPO system pop up LCH227 validation error and not allowed to process further.

Solution:
Do not validate the type of business on the OCC and AB when running the RPO
Do not validate the type of business classification of the AB, OCC or PP when running the RPO
The RPO should always be created and saved

When picking up the cessions only use the cession benefit classifications to be validated against the PP classifications. Do not validate the type of business of the AB linked to the cessions against the type of business of the OCCs on the PP

Problem:

System abends while creating Proportional Standalone Claim with Valid status in the Linked Retro env.

Solution:
Irrespective of the system parameter settings of the Retrocession Basis it should be possible to create a proportional standalone claim
The effective date and timestamp of the claim statuses should be the date on which the status is created. This is applicable to all statuses.
For a claim with more than one status the order of the statuses should follow the sequence in which they were created as per the effective date and time

Problem:

System Abends while creating Non Proportional Claim.

Solution:

Do not check for insurable object when creating a non proportional claim. The system should not abend. Ceded Paid and Ceded Outstanding claim should not be applicable to a non proportional claim

Problem:

On cession batch created by using Reinsurance Program the Agreement details are updating incorrectly

Solution:
Always use the insured period of the Reinsurance Program while adding the linked Assumed Business to the cession batch when the batch is created for a reinsured program.

If there is no assumed business on the reinsurance program for the corresponding insured period then throw a validation error message 'No valid Assumed Business for the selected Insured Period of the Reinsurance Program

Problem:

System fails to replace the business partner through webservices with updatedinsuredperiod operation.

 Solution:
The <replacebusinesspartner> element should replace the existing business partner on a business
The message BS00238 If you are about to change the Business Partner to this agreement, the terms already registered may no longer be valid. Do you want to continue? should be part of the confirmation messages and if answered yes the partner should be replaced
Where the business partner cannot be replaced because worksheets exist then throw the error message BS00201 A worksheet exists for this business. You are no longer
allowed to change the business partner.

All existing online functions should be supported in webservices
 

Problem:

On Webservices missing element to exclude the classification on the RPO and RCPO.

Solution:

In both the webservices to create the RCPO and RPO, under the Classification complex elements, a new element <excludeRefData> should be available to filter the classification. It should be repeatable so that it will be possible to exclude classification values for more than one classification items, same a the online functionality.

Example, it should be possible to exclude one or more values for the Benefit Covered, Insurance Product, Additional Classifications etc within the same order.

This will be applicable to the RPO and RCPO where one PP is included. If more than one PP is included then this element should not have any impact irrespective of what has been included/ excluded

Problem:

Issues with Adjustment Reversal Transactions on Claims

Solution:

 Only when the system parameter 'Allow Transaction number on cession and claim transaction' is selected the option Adjustment Reversals should be available for claims and cessions.

The ACIs for Transaction reversals and Adjustment Reversals on the OCC and Placement levels should be in Released status and the ACIs should be included in the accounting process

Problem:

 System fails to exclude the classfication from business, when classification are defined on <excludeRefData> element on updateScopeofCover operation.

 Solution:

 On executing a SOAP for updateScopeOfCover with Classfications elements as <excludeRefData>, system should exclude the defined classification from the business, and should throw the relevant validation if classification cannot be excluded due to multiple child section or Cession created on the business.

Problem:
ACI's are calculating incorrect on the cession when amendment is done on the business (OCC)

Solution:

When the Amendment option for Existing Business is 'From next premium calculation' the Retrocession ACIs that will be calculated as part of the amendment should be calculated with the amended values for the renewal transaction that falls on or after the amendment date for any existing Retrocession when the RPO is run

When the system parameter 'Use Reinsurance Start Date for retroprocessing' is selected use the reinsurance start date of the cession to only validatate if the reinsurance start date falls within the treaty effective period
For all amendments use the transaction effective date to validate the terms and conditions

This is similar to existing inward cession functionality

Problem:

ACI's are not calculating on placement cessions when created with Single treaty protection.

Solution:

 When the retro is created through a Single treaty protection or a QSR linked to the AB on the PP (proportional protection) condition of the Assumed Business, the ACIs on the placement cessions should be calculated in the retrocessionaire percentage defined on the linked OCC / STP using the ACIs that have been calculated on the OCC retrocession level cession

This is similar to any other type of ACI calculation on the placements where retrocession cession calculation when the retros are created through the RPO (or on a manual standalone retrocession)

Problem:

Incorrect retention and retrocession calculation when SAR decreased to below the retention.

Solution:

 When there is no change in the SAR or SAR for retrocession on a cession benefit then do not recalculate the SAR for Retrocession and the Retro SAR, Net Sum Retained. Copy the values from the previous transaction to the current transaction and use the same amounts to calculate the remaining Capacity and retention

Problem:

Abend on running a Retrocession Processing Order when on Premium condition 'Rate /Amt from cession benefit transaction' check box is selected

Solution:

When the checkbox 'Rate /Amt from cession benefit transaction' is selected on the PM condition of the OCC or the placement then this selection should be ignored if there is no valid rule selected
If the option is selected and there is no valid premium calculation rule, then use the rate / amount defined on the PM condition to calculate the premium. If there is no rate or amount and there is no valid rule and no premium rate on the retrocession cession, then do not calculate the ACIs, but the retrocession cession should be created and there should be no abend

This is similar to the functionality when the checkbox is selected on an inward cession

Problem:

 Cession Batch is not checking the Confirmation message flags defined on the batch and fails with 'Updated with Error', when created through webservices and executed by Job Scheduler.

 Solution:

  All confirmation messages taht have been selected on the cession batch should be answered as per the selection when the batches are run through scheduled jobs

This is similar to how the messages are handled online when run manually and when the batch is run through webservices

Problem:
Hide option - Per Life, Per SAR Accumulation Category in P/L condition in Inward/Outward Treaty/PP when system parameter Insurance Product included in SAR Accumulation category is not selected

Solution: 

When the system parameter Branded Products--> 'Insurance Product included in SAR Accumulation category' is not selected then hide the option 'Per life, Per SAR Accumulation category' under the PL condition Limit Expressed option on the AB, OCC and PP

Problem:
 
On webservices, system throws wrong validation message on createLfbusiness when min/Max expiry age is defined for AS Condition (<generalbasesCondition>)
 
Solution:

 System should update the Min and Max Expiry Age field as defined on SOAP, and should create the condition with given values on the new business. 
If there is any missing mandatory data in the SOAP, system should throw the respective Validation Message. 

Problem:
RCPO is not picking Standalone claim

Solution: 

The RCPO should pick up the standalone claims and use the classifications on the claims to process the retroclaims through the PP that is part of the RCPO and use the ceded % defined on the claims to process and calculate the retro claims

When there is an inward business on the RPO check for claims that are linked to all the sections of the AB. When the classifications on the claims are part of the linked PP's classifications pick up all the claims and process them

Link the processed retro claims to the respective sections of the PP's OCC based on the classifications of the inward claim

Problem:

Incorrect ACI's calculated on retrocession when in PM condition rate/value option is selected as Retro share of original.

Solution:
When the PM condition has the premium basis as Retro Share of Original defined on the OCC, then when an inward cession is picked up by the RPO the ACIs on the retrocession cession should be calculated using the ceded percentage and apply this ceded percentage to all the inward cession ACIs

This should be applicable to both ceded and non ceded cessions

When the Premium basis is defined on the OCC as Retro Share of Original and a manual standalone retrocession is created then the calculation should be considered similar to Premium Basis as Original i.e no premium should be automatically calculated even if a value is entered in the Ceded Percentage field

Apply the ceded percentage to the inward cession ACIs only when the retrocessions are created through the RPO and there is a link established between the inward cession and the retrocession cession

The solution as per SE-8186 will not be fully applicable anymore since both Ceded and non-Ceded will behave the same way going forward.
 

Problem:

Change Label of 'Ceded Percentage' under Placement

Solution:

Label name 'Ceded Percentage' under Placement has to be changed to 'Ceded Share'.

Problem:

Hide the RCPO option on Linked Retrocessions environment

Solution:

When the system parameter Retrocession Basis- Sum at Risk Standalone Retrocession only is NOT selected then hide the option Reinsurance Claim Processing Order from the Orders
This is not applicable to the 'linked environment'
 

Problem:

System Abends on deleting the deduction Condition when all the tabs are defined.

 Solution:

 When there is a rate table on the deduction condition - any tab- Basic, Extra or Other Deductions- then delete the condition along with the rate tables. Delete the link between the business / business section and the lookup table

If there is a cession linked to the section the deduction condition should behave the same way as the PM condition. The rates should not be editable and the condition should not be deleteable

Aim of function

The aim of the function is to streamline the Life Business Webservices so that the non mandatory tabs can also be created and updated through webservices.
 
Business value for customers

All the tabs in all the Life Business conditions will now be available to be created and updated through webservices.
 

System Parameters Affected

None

Existing functionality affected

Webservices for the following have been extended

Update the Rates Guarantees and Cash Surrender Tab of the Prop Premium Condition
Joint Life tab of the Premium condition
Update Additional Scope Condition
Domain Retrieval for Non Prop Business Conditions
Cession Deductions and Common Accounts Tab of the Deduction Condition
Modification Condition and Cut Off Lower Limts on the Limits Condition on Proportional Surplus Business

Aim of Function

The aim of this enhancement is to be able to book ACIs on a standalone claim.

Business value for customers

Customers will now be able to book the claim ACIs on a technical worksheet directly from a standalone claim or include the claim ACIs on the technical worksheet directly

System Parameters Affected
None

Existing functionality affected

From a standalone claim it will be possible to create a technical worksheet that will book all the claim ACIs using the TW icon on the claim

It will also be possible to create a technical worksheet and include more than one claim and its ACIs in the worksheet.

Aim of Function

The aim of this enhancement is to be able to create standalone claims on all types of business

Business value for customers

Customers will now be able to create standalone claims without a cession on both proportional and non proportional businesses

System Parameters Affected
None

Existing functionality affected

A standalone claim without a link to a cession can now be created on any type of business, both proportional and non proportional.
The standalone claim can also be loaded through the batch management on both proportional and non proportional businesses

Aim of Function

The aim of this enhancement is to be able to define new claim liability basis on a Proportional treaties and update claim liability basis on standalone proportional claim.

Business value for customers

Customers will be able to update the claim condition on the Assumed Business.
 
System Parameters Affected
None

Existing functionality affected

On the proportional business also it will be possible to update the Claim Basis on the Claim Condition
The basis Losses Occuring and Risk Attaching will be available for selection and when selected this will be used to validate the claims that are linked to the treaty insured periods.
For any other basis selected there will be no validation done when the claims are attached.

Aim of Function

To be able to assign ‘Premium Accounting’ task to the Reinsurer independent of the AS condition.

 
Business value for customers
 
For customers who use the Bulk Accounting on Assumed business, it will still be possible to assign the Premium Accounting task to the Reinsurer. This will open up the Cession Order to create accounting for such business in the future

System Parameters Affected
None

Existing functionality affected

Irrespective of the responsible partner defined in the AS condition and the Account Administration basis, the Premium Accounting task can be assigned to the Reinsurer.
This way, the ACIs on the standalone claims can be included in accounting through the existing Cession Order functionality (Note: It is currently not yet possible to include standalone claims in a cession order).

Aim of function

Create a specification for 'Use Commission Rate from the cession level and not the D condition'.

Existing functionality affected

A new option will be made available on the Deduction condition and when selected the commission rate entered on the cession benefit transaction will be used to calculate the commissions for that transaction

When the premium basis is Original and a commission rate is entered in either the Deduction condition or the Cession Benefit transaction, this rate will be applied to the premium that has been entered on Original basis on the cession transaction and the commissions will be calculated on the premium amount that has been input on the cession benefit transaction

Aim of Function
The aim of this enhancement is to be able default the type of claim that will be listed in the Find Claim window

 Business value for customers

 It will be easier for the customer to define the default search options on the Find Claim window rather than always select the option they need or commonly use.

System Parameters Affected

None

Existing functionality affected

Based on the Default value selected in the Reference Data, the type of Claim selected as default in the Find Window can be customised.

Aim of Function

The aim of this enhancement is to optimise the performance of the RPO.
 
Business value for customers

Better performance of the RPO

System Parameters Affected
None

Existing functionality affected

The RPO performance has been improved

Aim of Function
The aim of this enhancement is to be able to increase the field size of the Insurable Object Identifier from 50 to 100 characters

Business value for customers

Since the Insurable Object identifier is sometimes generated by concatenating other fields like name, date of birth and gender to create a unique identifier, the existing field size of 50 was insufficient. It is now possible to create an identifier with up to 100 characters

System Parameters Affected
None

Existing functionality affected

Insurable object identifier field size is now increased to 100 characters

Aim of Function

The aim of this enhancement is to be able to view the list of claims from a busines
 
Business value for customers

 It will be easier for the customer to view all the claims linked to a business insured period from the business

System Parameters Affected

None

Existing functionality affected

A new icon to display claims is now available
When selected the list of claims linked to the insured period of the business based on the Claim Basis is listed

When the Claim Basis is 'Risks Attaching' then the claims will be listed on the insured period based on the Reinsurance Start Date
When the Claim Basis is 'Losses Occurring During' then the claims will be listed on the insured period where the Claim Event Date falls in

All other Claim Basis options are informational and will behave similar to Risks Attaching

Aim of Function

The aim of this enhancement is to create batch auto test for RPO

Business value for customers

 This will ensure that existing functionality for any RPO has not been affected by any new enhancement

System Parameters Affected
None

Existing functionality affected
N/A