Release documentation - Life - Enhancements and requests

Problem:

Abend occurs after multiple uploading of the actual worksheet containing the entry code value to the New amount of worksheet.

Solution:

When Importing details of Technical Worksheet with 'New Amount' value, new worksheets to be created for the difference of value (“Amount”) of 'Previous Amount' and the 'New Amount', regardless of number of times of importing the same file. This should work in the same way as it works for manual worksheet creation with “Replacement values” option ON. The 'previous amount' of respective Entry codes should not be 'NULL' and should always be fetched and considered for calculating the difference (“Amount”). This applies to all Technical worksheet Import functions for product lines Life and P&C.

Problem:

Abend While doing Balance Pairing on Placement Business

Solution:

When there is no balance to pair the driving balance and the user clicks on OK then the system should not abend. It should do nothing and close the window.

Problem:
Unable to see a linked base company from a business partner detail tab
Solution:

When there is a business partner linked to the business partner, it should be possible to see the linked partner from the option Linked Base Company and Linked Business Partner from both the business partner and the base company

Problem:
Domain Restriction Business Structure creates an system crash on direct find of a business

Solution:

In both Life and P&C : When the domain restriction Business Structure is defined it should be possible to find business allowed as per the set domain restrictions.
It should not abend

Problem:

 'ACI Worksheet As At Date' objects not fetching data correctly in the reports.

Solution:

The joins should be modified like given below:

1.V_AMENDMENT_CLM_Derived.OBJECT_ID=LF_CLAIM_DETAIL_ACI.FK_AMENDMENT_CRE

2. Now AMENDMENT2 is joined with CESSION_DETAIL3, we need to remove that join and give join of AMENDMENT2 directly with the main table CD(CESSION_DETAIL).

CD.FK_CES_MUT_CRE=AMENDMENT2.OBJECT_ID

Problem: 

Missing Aggregate aware for payment partner related objects.

Solution:

Need to use the same structure as in PC Main Universe for both Payment partners & Responsible partners and update the object definitions with Aggregate aware.

Problem:

Object definitions has to be change for  Detail main, base and target conversion for detail objects.

Solution:

Detail Amount (Original) Dim object definition must change to coalesce(BOAC_LF_FACT.AMOUNT, 0.00)

The definitions for unsettled and settled objects are wrong. The correct definitions are in 'Detail Amount Unsettled (Orig)' and 'Detail Amount Settled (Orig)'. Copy these to the main, base, and target sections to get the right amounts.

Problem:

Missing functionality to create & updateNonProportionalLimitsConditionForLife for Working Cover

Solution:

It should be possible to update and create the updateNonProportionalLimitsConditionForLife for WorkingCover similar to Cat XL
The implementation of SE-28814 and SE-28912 should be extended to Working Cover Reinsurance Product

Problem

When PP is changed, Classifications are not refreshed or validated for mismatches

Solution:

Whenever a PP or an AB is updated on the RPO or RCPO then throw the warning message 'The classifications of all the protection programs included in the order should be a superset of the classifications of the Assumed Business. If not, all cessions may not be retroceded.'' This will be applicable for RPOs and RCPOs where there is one or more than one PP

Problem:
System Abends, when a cession is created with Reinsurance Program and Limits are not defined on the Agreement Level.

Solution:

 Do not validate the Limit condition on the Agreement level of the treaties within the reinsurance program if the limit condition has been defined on the section to which the cession is being linked.
If the section does not have the Limit condition created then thrwo the existing validation error message. The system should not abend

Problem:

Claim having Ceded O/S transaction and more than one -same transaction(Ceded Paid status) , the Created date and Reporting date of the latest transaction is updated from the 1st transaction

Solution:

When the claim transaction is created through the loader then always update the reporting date and the created date of the claim transaction from the value defined on the batch that created the transaction and the actual date on which the transaction was created through the batch

Problem:
 
On webservices, system throws wrong validation message on executing updateScopeOfCover operation with changed currency and updated limits conditions elements.
 

Solution:
 
Allow the user to update the currency on the Retention/ Underlying Top Limits or Autocover Limits and save the condition.
Update the existing error message as a warning message if the currencies in any one of the limits are not the same as the one you are updating

Similarly, when the currency is being changed on webservices, this warning message should be triggered in the background and be part of the response.

Problem:
RPO Abends when we have a backdated lapse transaction on a retroceded policy.

Solution:
When there is a linked retrocession cession to the inward cession but the date of the termination transaction on the inward cession does not fall within any of the effective periods of the retrocession cession but there are reversal transactions created on the inward cession (for transactions after the date of termination) then for all the corresponding effective periods that are available on the retrocession cession create the reversal transaction on the retrocession as soon as it is created on the inward- i.e even before the RPO is run

When the RPO is run then this inward cession will be considered inactive and not picked up
When the inward cession is reinstated then process the reinstatement and include the cession in the RPO as per existing functionality in later runs.
When the reinstated cession has to be retroceded, create the retrocession again as a new business transaction

Problem:

 ACI's are not calculating correctly on the Retrocession Placement Level of cession. in the 'linked environment'

Solution:

 The field Ceded Percentage is not applicable to the setup where the system parameter 'Retrocession basis- Sum at Risk Standalone Retrocessions Only' is not selected.

When the PM condition on the placements is inherited from the OCC, then always calculate the ACIs on the placement cessions applying the retrocessionaire definite share percentage to the retrocession level ACIs

If the PM condition on the placements is overridden, then use the rates defined on each placement's PM condition to calculate the premium ACIs and then the rest of the ACIs dependent on the premium.

The solution for SE-28979 should be applicable only when the system parameter 'Retrocession basis- Sum at Risk Standalone Retrocessions Only' AND ''Method of Retrocession- Sequentially in excess of Retention' is selected.

When either one of the system parameters is not selected then the existing functionality prior to SE-28979 should remain

Problem:
System abends while creating renewal transaction where benefit reinsurance start date is 27 feb of a leap year

Solution: 

When the benefit reinsurance start date is later than the reinsurance start date and within the next renewal effective date then when the renewal is created, the first transaction which would be a new business or old business should be created with a pro rata effective period with the start date = benefit reinsurance start date and end date = renewal effective date -1. The first renewal should start from the next renewal effective date

Problem:

 The Calculation Frequency Field is updated as Blank on Premium Condition through Webservices on defining Invalid value on the SOAP.

Solution:

 Fail the SOAP with the message 'The Calculation Timing field is required but has not been specified.' if there is an invalid Calculation Frequency field defined since the field is mandatory

Problem:

System allows to delete the business insured period on which Cession/claim batch is created.

Solution:

If there is a cession or a claim batch in any status or any standalone claims linked to the insured period of the business, then when deleting the business or the insured period throw the error message
BUS0058 The Insured Period has references to a cession batch. Deletion of the business/ insured period is not possible.

If there is a standalone claim linked to the insured period of the business in any status, then when deleting the business or the insured period throw the error message BS0320 : The Insured Period has Claims. Deletion not allowed when there is a claim linked to the business or the insured period. This is applicable to both prop and non prop business, inward and outward.

Problem:

 System Abends on renewing the Joint Life Cession

Solution:

When the retrocession is processed on a joint life cession benefit the selected values for Primary Life, First Death and any other values on the Joint Life tab should remain and not be delinked
When processing subsequent transactions on the cession benefit there should be no abend
This is irrespective of the Joint Life premium basis selected on the PM condition
 This is applicable to both 'Linked retrocessions' and 'Standalone Retrocessions' on the system parameter configuration

Problem:

On Cessions created on STP and QSR retrocessions ceded percentage is not updating in subsequent transactions.

Solution:

  The Original Sum Insured value and the ceded percentage and ceded factor should be updated for all the transactions when the retrocession is created through the STP or QSR retrocessions

Problem:

Find business Icon is not displaying in edit cession batch window.

Solution:
When the cession batch is edited and the business field is open for editing then display the Find business icon
On selecting this icon the user should be allowed to find and update the selected business
When a batch is in a closed or inactive status then it should not be possible to edit any fields including the business field
 

Problem:

On RPO the Filter functionality is not working when ran through scheduler.
 

Solution:

 When filters have been selected on the RCO or the RCPO and the orders are executed through the scheduler, the filters should be applied when running the orders.
This currently works when the order is executed online but the filters are ignored when run through the scheduler

Problem:

The walkback: GC overhead limit exceeded

Solution:

Optimize the performance of the RPO

Problem:

 On Webservices, system is not fetching any data on the domain retrival of the RPO/RCPO/RPGO.

Solution:

The system should not generate a walkback when executing the SOAP, and on feedback, the retrieval data of the Order should be fetched.

Problem:

 On Webservices, system is not fetching any data on the domain retrival of the Joint Life IO.

Solution:

 On executing the SOAP, the system should fetch the retrieval data of the joint life with all the details.

Problem:

Performance issue of running quarterly accounting order - mantis 8862 ( 3rd quarter from 1-7-2024 to 30-9-2024)

Solution:

Optimise the performance of the Retrocession Cession Order and Cession Order.

Problem:

 The RPO ID is not updating on the Scheduled JOB, created using Chained Operation through webservices.

Solution:

 When a chained operation is executed for creation of the RPO/RCPO/RPGO and subsequent creation of Scheduled Job for the same, system should create the JOB and update the references field on the JOB with the correct RPO/RCPO/RPGO ID, and on executing the RPO/RCPO/RPGO it should get executed as per existing functionality.

Problem:

PM Condition update on the Placement Level. Curently it is not able to update and it geneartes a walkback file due to some code error.

Solution:

 When the PM condition on a child section or a placement that is inherited is attempted to be updated through the SOAP = update the condition if the message 'This condition is inherited, do you want to create a local copy... is flagged as Y
If not, then fail the soap with the same message since it is considered as flagged as No and hence no overriding can take place
The system should not abend

Problem:
When we run the RCPO, Created date and Reporting date is not copied to the retroclaim

Solution: 

 Copy the Created Date and Reporting Date from each the inward claim status to the corresponding retroclaim and the placement claims when the retroclaim is created when the RCPO is run

Problem:
Incorrect retention and retrocession amounts when we reinstate an terminated cession and new retro is created

Solution: 

 When a cession is reinstated and then there is a subsequent transaction done after the reinstatement always calculate the SAR for retrocession/ SAR using the values on that specific transaction. Check for the remaining retention and capacity as on date of that transaction and process the retrocessions.

For a Reinstatement with Update transaction always use the values on the Reinstatement with Update transaction to calculate the SAR/ SAR for Retrocession and use the remaining retention and capacity as on date of that Reinstatement with Update transaction to process the retrocessions. Any subsequent transaction after the Reinstatement with update needs to be processed similar to any other transaction

Problem:
Issues with policy year and commissions 

Solution: 

 Update the policy year on a cession for every completed year.
When the cession has the ceded flag, then use the policy year to calculate the commissions using Basic Commission rate for policy year 1 and Renewal commission rates for policy year 2 onwards

Problem:

User not forced to make Full System Refresh when Access Code changed by another user via User Preferences rather than via Security

Solution :

Handle access code changes for another user consistently, regardless of whether the change is made via User Preferences or the Security module.

Problem:

Incorrect Deductions calculation on placement cessions when calculation rule is defined on Placement business PM condition.

Solution:

When the premium condition is overridden on the placements of the OCC the premium calculation should happen on placement level using the defined condition- this is similar to how the premiums will be calculated on the placements if they have been overridden without any calculation rule also.
All other ACIs that are defined on basis of premiums should then use this calculated premium on the placement cessions.

Problem:

System allows to create standalone claims on the business where mandatory conditions are not defined

Solution:

 Only check for the Admin condition when creating a standalone claim- both proportional and non proportional.
Throw a confirmation message when the claim is created and 'Accounts Administration Condition has not been specified on the business. Do you want to continue?
When the claim is created through the loader, answer this question a Yes by default
None of the other conditions need to be mandatory
 

Problem:

 On Webservices, system is not retrieving the SR and PM condition on the Prop and Non Prop business.

Solution:

 On Domain retrieval for the Business, system should retrieve the SR and PM codition of both Prop and Non Prop business same as other conditions.

Problem:

Premium is reversing on incorrect entry code when Lapse is created in New business effective period.

Solution:

 When there is a lapse transaction none of the fields should be allowed to be edited/ updated when created manually or through the loader. The ACIs that are calculated as reversal ACIs should have the same entry code as the source ACIs.
For each ACI that is being reversed, the corresponding reversal ACI should be created with the same entry code as the original ACI

Problem:

 System throws wrong Validation Message on updating the Profit Commission Condition.

Solution:

 When the Profit commission is Original then do not validate any other field on the PC condition

Problem:

 When we create/copy an RPO and attach More than one protection program with mismatch Base Company, no validation message raise by system.

Solution:

 When any one of the PPs linked to the RPO or RCPO do not have the same base company as the AB then throw the message *'Mismatch between program <PP ID> and assumed business <AB ID> cedent of the program is not same as the reinsurer of the assumed business.' should be thrown, similar to the RPO with one PP
This should be applicable irrespective of any system parameter under Retrocession Basis. So whenever one or more PPs linked to the RPO or RCPO have a base company that is not the same base company as the included Assumed Business then the error message should be thrown,
When the RPO or RCPO is created through webservices and a scheduled job then the error messages should never be thrown expecting user interaction and should fail the process in the background of the scheduled job and list the error

Problem:

Classification item unavailable on ceded cession when there is a parent dependency for the same.

Solution:

When the Ceded flag is selected on the cession and there are no child sections on the Assumed Business:
Always display ALL available reference data values on the cession benefit classifications for selection irrespective of any dependencies set.
Validate for Mandatory Classificcations defined for the base company of the assumed business, but do not validate any other values against the assumed business

When the Assumed Business has child sections :
Only display the classifications - both Mandatory and In Use- defined on the Assumed Business section on which the cession benefit is being created for selection.

Problem:

 System Abends on selecting the Reason as 'Duration Range' on the Extra Premium Tab on Premium Condition.

Solution:

 When the duration range is selected the system should not abend. It should allow the user to input values for the duration range applicable for the extra premiums as a From and To field. This should behave the same way as it does when Duration Range is selected as part of the Lookup Table creation

Aim of Function

Book ACIs of Proportional Standalone Claim through Accounting Order
 

Business value for customers

 Customers will now be able to book the ACIS of the Standalone Claim through the Cession and Retrocession Orders, similar to an individual claim

System Parameters Affected
None

Existing functionality affected

• Non Proportional Business can now be included in a Cession Order

• All business irrespective of the Premium Accounting Task can be included in a Cession Order

• A new flag is available to include Standalone Claims in the Cession Accounting Order. When this flag is selected all standalone claims will also be included in the cession order

Aim of Function

The aim of this enhancement is to be able to define Countries, Residence Countries and States as part of the Additional Classifications on a cession benefit.

Business value for customers

Customers will now be able to use Countries, Residence Countries and States to be part of the cession classifications and use these parameters in reports and for retroprocessing.
 

System Parameters Affected
A new system parameter 'Legal Area on Cession Benefit' is now available for selection under Cessions.

Existing functionality affected

When the system parameter 'Legal Area on Cession Benefit' is selected:

When this system parameter is selected the flag will be available for selection on the business level:

When the flag is selected on the business, then on all cession benefits where the ceded flag is selected, it will be possible to add the residence and legal areas on the cession benefit transaction:

The values from the inward cession will be copied for retroprocessing.

Note:

All values from the Locations will be available for selection.
The current implementation will only copy the values to the retrocessions, no validations will be done while running the RPO.
The legal area from the accounting costing items will not be included in the accounting.

Aim of Function

To be able to create a Conversion New Business transactionon a cession benefit on an existing cession through the loader and manually
 
To be able to update classifications on the Other transaction from the transaction effective date without changing the classifications on the previous transactions

Business value for customers

 When a policy has been processed with a Conversion Termination, it will now be possible to create the new transaction with the Conversion New Business transaction on the same cession as a new benefit both manually and through the loader.

When there are transactions on a cession where any of the additional classifications are changed from a specific date, then the change will be applicable only to the transactions from the transaction effective date, and the previous transactions will remain unchanged

System Parameters Affected
None

Existing functionality affected

Other transactions:

When the additional classifications are changed on an Other transaction, then only the transactions after this transaction will have the additional classifications. Previous transactions will not be impacted

Conversion New Business Transaction:

• It is possible to create a Conversion New Business Transaction on a Cession Benefit where there is a Conversion Termination
• This is possible both online and as a manual cession and through the cession orders
• It is possible to create a cession with the first benefit and the first transaction being Conversion New Business both manually and through the loader

Aim of Function

Apply filters on cession batch through webservices
 

Business value for customers

 It is possible to apply filters to the data that is loaded through the cession batch manually. Customers will now be able to apply the same filters through webservices also

System Parameters Affected
None

Existing functionality affected

Similar to online functionality, it is now possible to apply filters when processing the cession and claim batches through webservices

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

Customers will be able to update the Extra Premiums and Adjustments Tab in all the Life Business through webservices.
Customers will be able to select the Flag 'Standalone Claim' in in the Retrocession Claim Processing Order and include standalone retro claims processing through Webservices
 

System Parameters Affected

None

Existing functionality affected

The Extra Premium and Adjustments Tab on the PM condition is now available for creation and updating through webservices
The flag ' Proportional Standalone Claim' is now available on the Retrocession Claim Processing Order when it is created through webservices