Release documentation - Life - Enhancements and requests

Problem:
Possible to close WS via 'Change Worksheet Status' although mandatory retro link is empty

Solution:
Preconditions: The system parameter 'Mandatory Retro Booking Details Link' is activated

When user is trying to change status to Closed on a worksheet created by an instalment order on a non-prop treaty OCC, and this worksheet contains details without retro link to an assumed business, then the system shall not allow the user to navigate from Find Accounting Worksheet window or from Select Open Worksheet window to the Worksheet Closing window. The message AC0553 must be raised and stop the user from reaching the Worksheet Closing window.

Problem:

Development Objects' Folder is not hidden in the Life Unified Universe.

Solution:

Development Objects' Folder needs to be hidden in the Universe so that it will not be visible to users after upgrading.

Problem:

Claim ACI Base conversions and some of the objects needs to be adjusted to make the conversion correct.

Solution:

SQL of the objects under Claim ACI & Base& Base2 needs to be adjusted  and new view and alias needs to be created to correct the currency Conversion.

Problem:

Outer join is not defined on the tables REF_TypeOfBusiness and REF_LevelofBus also the AMENDMENT Details is defined two times in LIFE Universe.

Solution:

Outer joins needs to be defined on the tables as suggested and create a alias of CNU_USER instead of REFERENCE_TABLE and join with AMD_Booking table. Object definition also needs to be modified.
 

Problem:

Flat or per mile Extra for reason 'Above Free Cover Limit' is not calculating correctly on the Retrocessions and Placements of Standalone Environment. 

Solution:

When the system parameter 'Sum at Risk Standalone Retrocessions Only is selected' - the system defined value 'Above Free Cover Limit' should not be available for selection on the cession benefit. If mapped, the value should be ignored.

Problem:

Error message when editClassificationForLife on a sub section classification by web service 

Solution:

For Life ONLY

When editing the classification through webservices remove all validations of parent dependencies including Included Ref Data of child SOC and Type of Business on child SOC.

Problem:

AC not generated on the ORP when IP is involved

Solution:

All classifications that are part of the accounting classifications should be used when the ACs are generated on the OCC and they should be inherited to the intermediary and retrocessionaire placements

Problem:

 When the Gross Sum Reinsured amount is increased on a Increase Transaction, system is not correctly retaining the amount on Running RPO with OCC having Calculation Rule.

Solution:

Always use the value in the field 'Sum at Risk for Retrocession' when there is a SAR calculation rule in the OCC to calculate the retrocessions for all transactions. 

When there is a change in any of the parameters that are part of the SAR calculation rule and this results in a change in the SAR for Retrocession in a subsequent transaction then use this value to recalculate the Net Sum Retained, Retro Sum at Risk and the Unplaced amounts

If there is an SAR calculation rule then the field Sum at Risk on the inward cession will never be considered for the retroprocessing

Problem:

Editing of Cession Worksheet Balance's properties window is controlled by Use Case: Accounting Claim Worksheet 'U'

Solution:

The Use Case Accounting Claim Worksheet should be specific to P&C only. Selection of any options on the Use Case and assigning/ unassigning the use case itself should have no impact on any Life functions

Problem:

Legal Reporting Unit not populated on the Balance of Cession Worksheets at random

Solution:

Always default the reporting unit that is available on the business SoC to which the cession benefit is linked when the cession order or retrocession cession order is run

If the SoC has more than one RU then force the user to select the RU when closing the cession worksheet

Once the worksheet is created all the details that are part of the balances should have the reporting unit available

This should be available on the details when viewed through the balance details of the worksheet,  business ledger, business partner ledger

When balance pairing the legal reporting unit should be validated based on the system parameters

Problem:

Linked Retrocession | Inward Claim with status 'Paid' created through Claim Loader | 'As of date' of the ACI on the placement claim is incorrect

Solution:

The As of Date of the retrocession claim and the placement claims should be equal to the the payment due date field of the retro claim and placement claim

When the environment is 'linked' and the system parameter 'Standalone retrocessions only' is not selected the retro claim and placement claim should be created automatically when the inward claim is created and therefore the As of Date of the retro claim and placement claims should be copied from the inward claim transaction

Problem:

System Abends on closing the cession batch, when Benefit Term Unit is not mapped on the Output Pattern.

Solution:

Fail the record with a missing benefit term unit message similar to what is presented online when there is a benefit term but no unit mapped. The system should not abend

Problem:

 System generates a Walkback file on executing the SOAP for creating a Cession Batch. 

Solution:

 When there is no input file found the webservice should fail with the message that the file is not found or available in the mapped path and should not abend

Problem:

System is throwing an Error message, 'There are unfortunately no details. Probably Sics/nt has disabled the process behind the service due to business rules' on executing SOAP for Standalone Individual Retrocession.

Solution:

The SOAP should create the standalone retrocession when the mandatory values are provided. when the entry point is create standalone retrocession

Problem:

System is throwing a SQL Error on Referencing a Batch in Linked Environment.

Solution:

Update the missing schema names on the tables

Problem:

'Attach OCC for Facultative Retrocession' option not active on Create Facultative Retrocession window

Solution:

The option 'Attach OCC for Facultative Retrocession' should be available when there is an amount in the Remaining Unplaced Amount field

When the retroceded flag or the retroceded date is not available then also the option should be available

Problem:

System abend when we map Unit of time constant on Premium Frequency in output pattern while creating cession through batch

Solution:

When an invalid value is mapped to the premium frequency the batch should not abend. The batch should fail with the error message 'Premium calculation frequency is mandatory' similar to how it fails when the value is not available 

Problem:

On Webservice, Sequence No. Element is not available on the cession and Standalone Individual Retrocession skeleton

Solution:

Sequence number element to be avaialble in the create cession and create standalone retrocession webservice. When the system parameter is selected as manatory, then the soap should fail when the value is not present in the sequence number field

Problem:

System is abending when clicking on more information tab while updating balance properties in a cession worksheet.

Solution:

The Use Case Accounting Claim Worksheet should be specific to P&C only. Selection of any options on the Use Case and assigning/ unassigning the use case itself should have no impact on any Life functions

So when the use case is selected or not, there should be no impact on ANY of the life functions. All options on the cession and retrocession cession worksheet and orders should work and be accessible to the user

Problem:

Retroceded date is not updating on inward cessions on which Retrocessions are created with single treaty Protection.

Solution:

Retroceded Date should be automatically updated with the transaction effective date of the inward cession transaction when the STP attaches to the inward cession to create the retros. The retrocessions attached flag should also be set

Problem:

System not allowing to create Underwriting Actual cession through Loader

Solution:

When the cession loader references an underwriting cession then when all the fields on the record match the underwriting cession fields it should convert the underwriting cession into an actual cession.

The transaction code if mapped should be ignored and the cession should be created as a new business always

When there is a calculation frequency mapped to the record and the premium calc frequency is Original on the PM condition then the mapped frequency should be updated on the converted cession

When the calc frequency on the PM condition is not Original then the frequency mapped should be ignored and the value from the business should be defaulted to the cession

If there is no calc frequency then the record should fail with an error message 'renewal frequency is not defined'

Problem:

Retrocession Claim Processing Order is not running in SQL Database

Solution:

Update the scripts so that the RCPO will run in the SQL database. The RCPO should pick up individual claims, proportional standalone claims and claims that need to be recovered from facultative retrocessions.

All filters applicable on the RCPO that currently work in Oracle database should also be applicable in SQL

Problem:

Fields under Escalation Indexation and original policy tab are not updating when an cession is created through loader

Solution:

When the cession has the ceded flag selected ALL values that are mapped to the Escalation Indexation and Original Policy tab should be updated as per the loaded values. Do not reference to the business conditions when updating the fields

Also, ALL the fields should be available for manual edit when the ceded flag is selected

Problem:

 When Historical Claim flag is selected on a non ceded claim, system is not allowing the event date prior to reinsurance start date.

Solution:

 Allow creating of claims with an event date prior to the benefit start date when the historical claim flag is selected. This is applicable to claims that are created with any status

Problem:

Premium is not calculating on retrocessions, when PM condition having Age rate Table and Age definition as original

Solution:

When the Age Definition is Original on the OCC and there is an Adjusted Age and therefore a transaction Age updated on the inward cession then use this transaction age to calculate the premium or any other ACI on the retrocession cession level when age is one of the parameters on the LUT when the RPO is run

Problem:

Reversal transaction is getting created when we use same details of existing cessions to create new cession

Solution:

When there is a record loaded with the same details as an existing cession benefit then the record should be rejected with the error message 'LCH018' since it is attempting to create a duplicate transaction.

If this record is loaded with the same details, but there is no transaction code mapped, then this should be created as an 'Other' transaction

 Problem:

On Webservices, system is not allowing to disable LookupTable element on the Create/Update Proportional Limit Condition Operation as it is non mandatory.

Solution:

Allow the element <Lookup Table> to be disabled in the 'createProportionalLimitsConditionForLife' API if not required. Once disabled all the dependent child elements should also be disabled

Problem:

On Webservices, 'Is Ceded' Flag element is not available on the CreateLfCession operation. 

Solution:

The Is Ceded element should be available for both Create cession and create standalone retrocession APIs

When this is selected it should be possible to add additional classifiactions to the cession on the soap

Add a repeatable element for Additional Classifiction in the SicsWsLfCessionEntryPoint' and Operations As 'createLfCession and createLfRetrocession

In this it should be possible to add different additional classifications

When the cession Is Ceded is marked as Yes then these additional classifications should be created on the cession and retrocessions

When the Is Ceded is not Yes then the additional classifications should be ignored and the cession should be created with only benefit covered and insurance product

When the additional classifications are marked as mandatory then the transaction should fail if the mandatory classifications are not part of the soap

Problem:

On Webservices, 'LookUpTable' element is not available on the Create/Update Propotional Limit operation under the Quota Share Retention Basis Element.

Solution:

The element Lookup Table should be available for Create Prop Limit and Update Prop Limit webservices for Quota Share Retention basis element

Problem:

Claim loader is creating claim on random benefit if benefit covered and insurance product is not mapped on the batch and cessions having two benefits.

Solution:

If there is more than one benefit on the cession - active or inactive - then the benefit covered is mandatory on the claim when loaded

If there is more than one benefit covered on the cession benefit then even if there is only one cession benefit on the cession then the benefit covered is mandatory on the claim when loaded

If there is no benefit covered mapped and there is more than one benefit covered or benefit that is trying to be referenced then the record should be rejected with a validation error 'More than one matching cession benefit found. Benefit covered is mandatory to reference the correct cession benefit'

If the referenced cession has only one benefit covered with only one benefit then the policy number match should be sufficient to find the correct cession benefit to create the claim on

Problem:

Expiry age is not updated on inward cession and retrocession cession for Extended term transaction

Solution:

When the expiry date is changed either on an extended term or any other transaction where  the expiry date is changed or the benefit term is changed

Recalculate the expiry age on the current transaction based on the updated expiry age

Use the calculation logic to calculate the expiry age similar to the calculation implemented for new business

Problem:

When renewal sum at risk=0, SICS should calculate the sum at risk = 0 rather than directly copy the previous transaction to calculate the retention and retro.

Solution:

Allow loading of SAR = 0 ONLY when the SAR decrement basis on the SR condition is defined as Unknown SAR Advised and no Increase is defined in the Increases tab

When the SR Decrement Basis is NOT 'Unknown SAR Advised' then existing logic to remain

Consider the SAR = 0 when processing the retros for this transaction thereby releasing the retention and capacity already used

Create the linked retrocession cession also with a 0 Retro SAR

The cession and retrocession should continue to be active

Problem:

Escalation Indexation and Original Policy tab is not available on Retrocessions and Placements

Solution:

Escalation Indexation and Original Policy tab should be available on standalone retrocessions and placements (all retrocessions, facultative, linked to an inward cession or standalone manual retrocessions)

When the retrocession is created through the RPO or linked as a Facultative Retrocession then all values should be copied from the linked inward cession without applying any ceded percentage to the values in the fields. When the retrocession is created manually then the tab should be copied to the placements without applying any ceded percentage

Problem:

Cannot create Underwriting Individual Cession due to SICS0007 - Missing qualifier

Solution:

When manually creating an inward cession, retrocession cession or underwriting cession the Qualifiers tab should be available for selection in the create cession wizard itself

When the Limits  (retention, UTL or Autocover limits or QS Limits, QS 100% Limits) are defined with a qualifier then the qualifier should be allowed for selection during the create cession process itself and when the qualifier is selected then the Limits should be validated based on the selected qualifier

When qualifiers are required since they are defined on the Limits condition for either retention or autocover limits then on the Agreement section the user should be forced to select a qualifier. If not selected then the existing message ''You must specify value for each column' should appear

This is applicable for both Actual and Underwriting cessions

Problem:

When a OCC is linked to the AB, on running the Retro Calc. Order on OCC, system is creating multiple Worksheet, on the 'As Booking' of OCC and Placements

Solution:

When a worksheet has already been picked up by the Retrocession Calculation Order it should never be picked up when the REAC orders are run again

Problem:

SicsWsBusinessEntryPoint. createLfDeductionCondition and SicsWsBusinessEntryPoint. updateLfDeductionCondition cannot link lookup table for basic premium commission, when I using 'TAB_RATE' as Commission structure.

Solution:

Any rate table added to the Deduction condition for basic commission,- initial and renewal commissions, extra commission - initial and renewal commissions or any Other deduction should be updated on the created condition when the table is part of the SOAP

Problem:

On Webservices, The Domain retrival is not showing all the Required data on the Server response, after executing the SOAP for SICSLfCessionBatch 

Solution:

All details from the cession batch should be retrieved as part of the domain retrieval webservice for Lf Cession batch

• Identifier
• Account Period
• Title
• Status
• Status Date
• Business 
• Partner
• Reporting Date
• Allow Partial Processing Flag
• Data Sources
• Status History

Problem:

When trans_code='TREINSWUP', reinstatement effective date =lapse effective date, the reinstatement premium will be an exact reversal of the lapse premium.

Solution:

When the transaction is a reinstatement with update and the transaction effective date of the reinstatement with update is equal to the date of termination then the reinstated premium should be equal to the reversal premium ACIS. The reinstatement premium should not be calculated on any pro rata basis

All other ACIs that were reversed including the commissions and other deductions from the termination transaction should also be reinstated

Problem:

System is allowing to take payment due date earlier than event date in proportional standalone claim

Solution:

For all claims: Payment due date should be greater than or equal to the claim event date. If the payment due date is earlier than the claim event date then the error message 'Payment due date cannot be earlier than the claim event date <claim event date>' should be thrown

Problem:

Can not override L condition and create a local copy for child section by API(SicsWsBusinessEntryPoint .createProportionalLimitsConditionForLife) when L condition of child section is inherited from parent section.

Solution:

Refer  to the Child Section name that has been defined on the SOAP under SOC element when referencing to the scope of cover that needs to be updated

When the validation message 'BS00167' has been defined to be answered as Yes then override the condition and update only the scope of cover that the update SOAP references to

Do not update the Agreement section or any other section

When the validation message 'BS00167' has not been activated in interactive messages or marked as No then fail the process with the message 'BS00167'

Problem:

On updating the retention limit condition as part of amendment through API, system creates another entry of retention instead of updating the existing one

Solution:

When the 'updateProportionalLimitsConditionForLifeInput' soap is run and the currency that is part of the update limit already exists on the business section then the system should update the existing retention value and do not create an additional entry for retention on executing the soap. 

If the currency does not exist and the currency is part of the additional allowable currencies then the limit in the update soap should be added

If the currency does not exist on the business classifiacations then the record should be rejected with the error message that currency does not exist

The above is applicable to any update action either as an edit or an amendment

Problem:

The retrocession is not created on the cession through loader when add a single treaty protection from the PP condition on the AB

Solution:

When the system parameter 'Sum at Risk Standalone Retrocessions Only' is selected.

When there is a single treaty protection or a QSR retrocession attached to the inward business the retrocession cessions should be created automatically when the inward cession is set to an active status either manually or through the loader

The retrocessions should be created for all subsequent transactions of the cession when the inward transaction is created

The retroceded date on the cession and retrocession should be set based on the transaction effective date

The RPO should not pick up these cessions 

There should be only one window open when the retrocession icon is clicked on the inward claim

Problem:

Ceded percentage is not calculating while creating cession when STP/QSR is attached on PP condition of AB

Solution:

The ceded percentage field on the cession benefit and retrocession and placemet enefit transation and the ceded factor field on the retrocession window should be calculated and updated as per the ceded percentage of the QSR/ STP OCC 

The same value should also be copied to the claim created on the cession

Problem:

Claim loader is not referencing Cessions converted from UW cessions.

Solution:

Once the underwriting cession is converted to an active actual cession (UR) either manually or through the loader  should be refrerenced for claims and subsequent transactions similar to an actual individual cession of type R

Problem:

Retrocession cession renewal point not copied from inward cession.

Solution:

Always copy the Renewal Point from the inward cession on the retrocession and placement cessions that is created through the RPO or the retrocessions that are linked through a Fac retrocession

When the renewal transaction is done on the inward cession then the retrocession cession and the placements should be renewed with the same dates as the inward cession

Problem:

Show details flag on worksheet is not available in the system parameter 

Solution:

Aim of function
 
The aim of the function is to be able to place the increased SAR to the same OCC on which the previous facultative amount was placed.

 
Business value for customers

When there is an increase in the SAR and there is an existing facultative retrocession linked to the cession, it will be possible to retrocede the increased SAR to the same retro partner on the same facultative agreement. 

System Parameters Affected

None

Existing functionality affected

When there is an increase in the SAR in a subsequent transaction and there is an existing Facultative Retrocession linked to the cession a new option 'Adjust SAR to Existing Facultative Retrocession' is available.
When this is selected the user will be allowed to add the increased SAR that is now unplaced and available for retrocession to the existing Facultative Retrocession as long as the ACIs are already not included.
The increased SAR that is unplaced can be allocated to the same Fac OCC as long as there is capacity available on the OCC.

Aim of function

The aim of this function is to be able to view the accumulation on the insurable object for the retrocessions and also retrieve the accumulation for the retrocessions through an API.

Business value for customers

This will enable the customers to have a snapshot of the accumulated retrocessions at any given date similar to the inward cessions. It will also allow the customers to retrieve the accumulated retro sum at risk through APIs which may be used during underwriting.

System Parameters Affected

None

Existing functionality affected

1. Insurable Object- Accumulation Control now has an a tab 'Standalone Retrocessions' 

This tab will display the Accumulated figures from the retrocession cessions

2. It is possible to retrieve the accumulation of a standalone retrocession through the RetrieveCessionsAndAccumulatedSARofIO webservice

Soap Message :

Response:

Aim of function

To be able to use more values from the cession in the SAR calculation rules including values in the 'Original policy' tab.
To be able to use the original policy frequency in a Lookup Table. 

Business value for customers

The Sum at Risk that will be considered for retrocession/ reinsurance can be calculated using the SAR calculation rules by applying additional parameters from the original policy when the RPO is run.

System Parameters Affected

Additional variables for the SAR calculation rules

Existing functionality affected

1. Escalation Indexation and Original Policy tab is now available for input for all cessions where the ceded flag is selected.
2. The values in this tab can be used in defining the SAR calculation rules and are available as variables
3. Original Policy Renewal Frequency is now a system-defined Lookup Table Allowable column and can be defined within any LUT. This will refer to the field 'Policy Renewal Frequency' in the Escalation Indexation and Original Policy tab of the cession or retrocession.

Aim of function

The aim of the function is to be able to update values on existing cessions through a batch process where the cessions have not yet been retroceded or included in accounting.

Business value for customers

It will now be possible to make corrections on already loaded batches or to update the classifications such as underwriting flag (additional classifications) and other details on a cession after the decision is made. 

It will also be possible to load cessions in a provisional status and update them once confirmed or approved.

 
System Parameters Affected

None

Existing functionality affected

A new flag is available on the cession batch loader in the Create New Batch option.

When this flag is selected and the imported records reference to an existing new business cession benefit transaction that is not yet retroceded or not included in accounting yet, then the details on the cession benefit will be updated as per the input file.

When the cession is in provisional status, and the input file contains ACIs then the referenced cession benefit will be set to active with the ACIs being created.

Aim of function

Attach to matching OCC within the PP based on the cession classifications. 

Business value for customers

For scenarios where the treaty covers a set of products and there is more than one Fac agreement with different reinsurers that cover a subset of the products on the treaty or, when the Facultative agreement pertains to a pure fac and the cession that is processed needs to be reinsured only through the Fac layer on the PP it will be possible for the cession to be reinsured through the respective layer within the same PP

System Parameters Affected

None

Existing functionality affected

When a Protection Program has more than one OCC and each OCC has different classifications or additional classifications, then the cession benefit will be retroceded to the OCC that has the matching classifications within the same PP.

Aim of function

The aim of this function is to move some functions that were implemented directly in the HA version SSP to head.

Business value for customers

New features as described in the Existing functionality affected section will be available.

System Parameters Affected

None

Existing functionality affected

1. Specific sections of the treaty can be updated using webservices.
2. It is possible to create amendments through webservices.