Release documentation - Life - Enhancements and requests

Problem:
Remittance Classification Group (Life Functionality) Included in P&C incorrectly

Solution:
On a Remittace Worksheet the following options should not be displayed in P&C even in a disabled mode

Transform Classification Group
Create New Group Member
Delete All Group Members

Problem:
Ceded percentage is updated as ‘0’ for Inward Cession and Inward Claim, while it is updated correctly for Outward Cession and Outward Claim and the system abends when opening the retro claim

Solution:
Do not recalculate the ceded percentage on the retro claim- always use the value from the inward claim's ceded percentage field.

If the inward cession was lapsed and the claim event date falls in the lapsed period, then the ceded percentage on the inward claim will be previous active cession transaction's ceded percentage as per existing functionality

Problem:
Getting abend for the cession creation while using a business which have pending amendment on draft.

Solution:
 When there is an amendment on the business and the amendment is not set to definite, the amendment should never be considered while processing cessions, accounting or any other transaction

If the reinsurance start date of the cession falls in an effective period of an amendment that is not Definite then throw the validation error message LCH127 ' The agreement attached has an amendment that has not been set to Agreed.'

This is applicable to both manual and loader

Problem:
When System Parameters not select Allow transaction number on cession and claim transactions. when upload adjustment reversal without transaction number, system abend.

Solution:
 When the system parameter Allow transaction number on claim an cession transactions is selected and the transaction number is not entered / uploaded then the transaction number should default from 1 on the first transaction that is created and continue incrementing +1 for each transaction.

When the adjustment reversal transaction is created without entering a transaction number then consider the transaction number as 0 and throw the validation error LCH247 'Transaction number <0> with effective period <2027-06-15-00.00.10.000000> cannot be reversed. Later active transactions exist. Adjustment Reversal can be done from the latest active transaction only.'

The system should not abend

Solution:
Any Reversal transactions that happen on the inward cession benefit should be automatically reflected on the retrocession and placement cessions when the RPO is run

Problem:
Renewal occurred within the previous period, retro and PL can't generate the corresponding reverse transaction.

Problem:
The migration through MTK is resulting in an error.

Solution:
It should be possible to import a file to migrate an assumed business that has a Lookup Table attached to any section/ condition without abend or error if the LUT or LUT allowable column is valid. If the LUT is not valid, migrate the business and the condition, but without the LUT

Problem:
System throws validation message on the wrong screen, when the system parameter is Seq. Based on Policy No. is selected.
 

Solution:
 When the system parameter Retrocession Basis - Sequencing as per Policy Number is selected then the policy number will be mandatory on the manual cession and the error message should be thrown on the first screen of the create cession wizard if the policy number is not given. On the loader, irrespective of whether the field Policy Number is marked as mandatory, the error message should always be thrown and the batch should fail if the policy number is not part of the input

Problem:
Renewal for Fac standalone retrocession order is creating renewals on fac retrocessions which are linked to inward cessions.

Solution:
 The Facultative Standalone Retrocession renewal Order should only renew Fac Retrocessions that do not have a link to any inward cession

Problem:
SICS Batch Processing taking long time to process Cession File in SQLSERVER database.
 

Solution:
 Improve performance of the Cession Loader from Reference to Closed status in SQL SERVER

Problem:
Cession/Claim Batch loaded with errors with incorrect error message when a field is defined with characters more than it's maximum limit.

Solution:
The error message should be made more descriptive '<field name> exceeds the maximum allowable character limit' when the batch is failed due to one or more records exceeding the maximum allowable field size on a cession or a claim

Problem:
RPO calculate incorrect Premium when cession transaction date falls after the OCC amendment date.

Solution:
 When the Amendment is created with the option Existing Business- From Amendment Date, then all transactions on existing cessions tahat are processed after the amendment date should follow the amended terms.

Problem:
For manually create  joint life inward and retro and placement inconsistent

Solution:
The Retrocession cession and placement cessions should have the tabs and the fields copied from the inward joint life cession

Problem:
On Merged IO in Remarks, in the individual IO details system updates with life ID type as PIDN. Even the actual life ID is not the PIDN.

Solution:
 Update the Remarks on the Merged IDs with the SICS IO Id and the Alternate Identifier IDs to be more descriptive

This insurable object was created on <date of merging>, by merging the following objects ...
<Full Name> (Date of Birth: <Date of Borth>, <Id Type/s> : <id number/s> separated by a comma if there are more).

Problem:
System Validate Corresponding date, Notification date and Primary and secondary Cause while creating claim with non ceded status.

Solution:
Convert the error messages related to Correspondence Date, Notification Date, Primary Cause of Loss and Loss Group on non-ceded claims to a confirmation message from the existing error message. In the claim loader, this message will be answered as Yes by default and listed in the messages. The record should not fail

Problem:
Claim loaded directly with status 'Ceded Paid' | Claim Paid ACI is not created when there is an interest entry code mapped

Solution:
Irrespective of any other entry code belonging to other entry code groups like Interest, Taxation that is mapped, the value in the field claim Liability should be automatically created with the Loss Entry code as defined for the type of claim as per the calculation model if the claim status is Ceded Paid, and with the Entry code for Ceded Claim Reserve if the claim status is Ceded Outstanding.

Problem:
The Filters are not showing on the cession accumulation when the cessions are status was excluded and included back
 

Solution:
Reset the filters to what they were updated manually to when the cessions are listed with new As of Dates and list the cessions only as per the selected filters. Thre should be a consitency between the seleted filters and the cessions that are listed

Problem:
When creating IO with two same identifiers with different identifier number, system creates duplicate IO with the same unique identifier number.

Solution:
Only one Insurable Object should be created and listed irrespective of the number of alternate identifiers defined on the IO

Problem:
The system list Insurable Object (IO) details that contain at least one identifier type restricted by the user’s Domain Restriction (DR) settings.

Solution:
If even one identifier type is restricted as per the Domain Restriction then the Insurable Object should not be listed in Search for both single, joint life or group insurable objects
If there is a cession or claim linked to that IO then the cession and claim should be listed with the IO masked, but on trying to open the IO, the Domain Restriction message should appear and the user should not be allowed to view the IO details

Problem:
An abend occurs while migrating the assumed business by using MTK.

Solution:
All levels of business should be migrated without abend through MTK. If there are Lookup Tables to be migrated and the LUTs already exist then the conditions with the LUTs should be migrated. If the LUTs do not exist then the conditions should be migrated, but the tables will not be attached to the migrated business

Problem:
Multiple Claims are getting generated with different IO although IO details are same in Loader File.

Solution:
When the Cedent Reference number is different but all refer to the same IO then the IO should be referenced if it already exists or created the first time when the first claim is created.

Only one IO should be created and all the claims that reference this IO should be linked to the same IO
This is similar to cession benefits that are created with different policy number/ cedent ref number, but with the same IO details in the same batch

Problem:
System throws no validation message on the cession order & retrocession cession order, when the order title and business is missing.

Solution:
When the cession order or retrocession cession order is created the Title and the business is mandatory
If no title is defined system should give a Validation Message '“The Uppercase Order Title field is smaller than its minimum allowable size (1).” and when Business is not defined for Cession Order, system should give a Validation Message “The Assumed Business is required but has not been specified.” and for Retrocession Cession Order , system should give a Validation Message '“The Outward Cedent Contract is required but has not been specified.”

Problem:
Abend on saving any amount field with exponential value

Solution:
In any numeric field, do not allow more than 1 digit after the letter E is input. If this input results in a figure that exceeds the maximum allowable size of the field, then throw the validattion error as applicable to the field

Problem:
Walkback error in SICS -System calculates Total Sum retroceded Amount in negative when Other transaction has SAR less than previous transaction.

Solution:
When the system parameter Sum at Risk Standalone Retrocession Only is NOT selected:

When the OCC Decrement Basis is Top Triangle:

If the Sum at Risk is greater than the Retention Limit in the first transaction, Retroceded Amount = SAR – Retention Limit. Update the Gross Sum Retroceded and Total Sum Retroceded with this value

When SAR Changes:

If the new SAR is still above the Retention Limit but less than the previous SAR,
then the new Total Retroceded Amount = Current SAR – Retention Limit.
The Gross Sum Retroceded will remain the same as the initial transaction
The Total Sum Retroceded will be updated with the Current SAR- Retention Limit

The difference between the previous and new retroceded amounts (Retro SAR) will be reduced from the retrocession cession linked to the OCC that was used last to retrocede the cession. If there was only one OCC, it will be reduced from the retrocession cession linked to that OCC
This difference should be reduced from the retrocession cession linked to the most recently used OCC first and then from the retrocession cession linked to the earlier OCCs

If the new SAR is equal to or below the retention, then the Total Retroceded Amount = Current SAR- Retention Limit will be < or = 0
The Total Sum Retroceded will always need to be 0
The entire SAR will be considered Retained
The Retrocession cession/cessions will be set to Lapse and be made inactivating Data+*

Problem:
When inherited child sections have cession link, when update agreement PM condition ,related child section should not be editable

Solution:
When any of the conditions on the parent sections that impact cession calculations are inherited and the condition is edited on the parent section then throw an error message ' One or more child sections that inherit this condition have cessions attached. The condition cannot be updated on the parent section'

Conditions that are relevant here- all fields on the conditions that cannot be edited if cessions are linked:
PM
D
SR
AC

If the update is done on any other condition that does not impact cessions, then the change can be made on all the inherited sections

Problem:
On webservices, system generates walkback when the Other Info Field defined with the exceeding character limits on the SOAP

Solution:
 When the Character limits exceed on the Other Info. fields OR on the Group Information Tab- Other Group Info fields, on executing the SOAP system should throw the Validation message '< Field Name> Exceeds the maximum allowed characters <max. character count>

This is applicable for both String fields and Numeric Fields.

Problem:
System creates Lapse Transactions on Retrocessions, when multiple Other Transaction is created on a cession in linked Env.

Solution:
When the system parameter 'Sum at Risk standalone retrocessions only' is NOT selected:
The first transaction on the inward cession should always be retroceded in order to process subsequent transactions. The RPO should pick up only the first (and only) unretroceded transaction. This transaction can either be retroceded or fully retained to be considered retroceded.

After this, when there is one or more subsequent transactions created on the inward cession with the same date as the first transaction or several subsequent transactions with the same set of dates, each transaction should be independently retroceded without impacting the first transaction that was already considered retroceded.

Problem:
When order was filtered by date, the system abend.

Solution:
 All search criteria based on Date and User in the Advanced tab should work without abend irrespective of how the order was run- manually, through the scheduler with or without distributed process options selected

Problem:
System Abends on uploading a subsequent tranasction though loader which doesn't exists on the already created cession.

Solution:
When a subsequent transaction (with a transaction code or transaction effective date or both) mapped is being uploaded on an existing cession and referring to a benefit covered or insurance product that does not already exist on the cession, the rrecord should be rejected with the error message 'Attempting a <transaction type> on a cession that does not exist. The system should not abend.
If there is more than one benefit that is being attempted to be created on the same cession or more than one transaction on the same cession benefit attempting to be created, then if one record fails due to any error all transactions on the cession should fail as per existing functionality with the error message <main error message of the first transaction that has failed> and <Rejected due to errros on other cessions.> for the transactions on the other benefits/ other transactions on the same benefit

Problem:
 
On webservice, System shows a Validation on Updating or deleting the Reinstatement Condition.

Solution:
When the required elements are defined on the SOAP and user executes the SOAP, system should update or delete the existing reinstatemnet rows as per the value defined on the SOAP.

Problem:
System abends while attaching informational cessions on individual cession.

Solution:
When the cession is linked to an insurable object that has the Gender = Group and the flag 'Group Cession without Individual Member List' is selected, then the options to create new informational or group cession on the informational cessions icon and function should be disabled.
Only the Properties options should be enabled if an automatically created informational cession benefit is linked

Problem:
Reference status issue, when duplicated life1ID in database, then upload cession data with duplicated life1ID, it's show updated with errors instead of referenced with errors.

Solution:
 
When the batch fails due to duplicate insurable object ids being referenced the error message should be'More than one insurable object with the same unique identifier available' and the batch should be set to a Referenced with Errors status rather than Updated with Errors

Problem:
WRE | SICS 24.3_SSP03 | Warning Message: LCH283 is not defaulted with 'Yes' in the Claim Loader

Solution:
'Claim event date is a outside the latest active effective period of the cession benefit. Do you want to continue?'

This message should be selected by default as Yes when processed through the loader and the claim should be created

Problem:
On Webservices, System generates a walkback file, on executing createLfCessionBatch created with JDBC connection.

Solution:
 It should be possible to create a cession batch through webservices when the Data Source is a JDBC connection without an abend

Problem:
Multiple ACI gets generated when clicking on ACI button during reinstatement

Solution:
For any transaction the ACI should only be calculated once. Clicking the ACI button multiple times should not create new ACIs. It should only recalculate the ACIs and update the already calculated ACIs if any parameter that affects the ACIs has been changed

Problem:
System Abends on creating a cession through loader when the Coverage Indicator is not mapped.

Solution:
 
The Coverage Indicator is not mandatory. If it is not mapped it should be defaulted to None (or the default value defined in the Reference Data)

Aim of function:
The aim of this function is to be able define various calculation rules such as Premium Calculation Rules. SAR calculation Rules, Profit Commission Calculation Rules as part of a separate module and not within the system parameters.

Business value for customers:
Customers will be able to define and administer the Business Calculation Rules outside the System Parameters and users who are not System Administrators can be granted access rights to manage them.

System Parameters affected:
All Life Business Calculation Rules

Existing functionality affected:

• New Security Use Case to Manage Life Business Calculation Rules with the Read, Create, Update and Delete Access Rights

• The Life Business Calculation Rules that were earlier in the System Parameters - > Business option are now available as a separate module under System Administration and can be maintained by users that need not have System Administration rights

• The following Life Business Calculation Rules will now be available under this module:

Aim of function:
The aim of the function is to be able to create a partial batch and a reject file when the batch is loaded with errors.

Business value for customers:
Now when a cession or claim batch has partially incorrect records that would result in a loaded stage error, it is possible to generate these as a sub batch and continue to process the remaining correct records

System Parameters affected:
None

Existing functionality affected:
When the flag 'Allow Partial Processing of Cession Batch' is selected, then when there are records rejected at the Loading stage, they will now be created as a sub batch with a reject file and the remaining records will be processed to the next stage

Please note that due to technical limitations, the number of records that have been rejected will currently not be displayed in the sub batch, but the number of records will continue to be displayed in the sub batch that has been successfully processed.

Aim of Function:
The aim of this enhancement is to be able to create and update the Reinstatement Condition on a non proportional business. 

Business value for customers:
Life Customers will be able to create and update the Reinstatement conditions on the Non Proportional Treaty through webservices as an update in the current insured period or after renewals of the treaties.

System Parameters affected:
None

Existing functionality affected:
Create Reinstatement Condition:

Update Reinstatement Condition:

Aim of Function:
The aim of the function is to be able to have webservices to support Life Accounting Orders- Cession Order and Retrocession Cession Order
 

Business value for customers:
 Life Cession and Retrocession Cession Orders can now be created through Webservices

System Parameters affected:
None

Existing functionality affected:
Create Cession Order :

Create Retrocession Cession Order :