Problem:

Assumed Business 'Working Cover' cannot be linked to Reinsurance Program due to message BR0033

Solution:

It should be possible to link all types of non proportional businesses with all types of Participation on the XL and SL sections of the Reinsurance Program
When the Assumed Business is added as a treaty outline and realised as part of the Reinsurance Program all the Types of Participation that are applicable to a non proportional treaty should be listed for selection
This is applicable to both online functionality and webservices

Problem:
Override Inheritance not activated on Proportional Protection Assignment on sub section in Life

Solution:
Allow override of inheritance on the PP section for QSR OCCs as long as there are no cessions attached to the section

If there has been any accounting that has already been processed and the inheritance is overridden then throw a warning message 'Bookings exist on the section and inherited sections that may need to be updated'

Problem:

Issue in Claim Batch when Life_ID is interchanged during 2nd Claim Transaction

Solution:

If the claim cannot be referenced due to a mismatch of the life id then fail the transaction with the error message 'Claim id <> not found or the status of the claim is not valid for the transaction'

The system should not abend

Problem:

When attempting to create a report at FWD, we observed a little issue were they requested to view the entry code group category in addition to the entry code group and its entry codes

Solution:

Need to adjust the below mentioned two joins in the universe.

V_BOAC_JT_ECG2.ECODE=ENTRY_CODE.CODE

ENT_CODE_GRP_Acc.OBJECT_ID=V_BOAC_JT_ECG2.GID.

Problem:

After running RCPO, SICS generated two amendments on claim

Solution:

 Only one amendment should be displayed on the retro claims when the same claim is referenced through the RCPO. This should be fixed both in the backend and in the UI display

Problem:

The FAC total sum retroceded is updated incorrect on the cession.

Solution:

When the system parameter 'Retrocession Basiss : Sequential in excess of retention' is selected and the calculation frequency of the OCC is Original

When the RPO is run

Always sequence the cession benefit transactions as per the sequence number, the lowest number should be processed first. When there are inconsistent values (numeric, alpha numeric or same sequence number then the existing random logic can remain)

For each cession benefit transaction

Process the Net Sum Retained, Retro SAR and the Unplaced Amount as per existing functionality
When there is a value in the field Fac Total Sum Retroceded on the transaction that the RPO has picked up, then calculate the Retro SAR as MIN( SAR- Fac Total Sum Retroceded, available capacity) (Here it will mean that there will never be an amount that is retained since there is a Fac Total Sum Retroceded)
When the Unplaced Amount - Fac Total Sum Retroceded > 0 then update the field Remaining Unplaced Amount as Unplaced Amount - Fac Total Sum Retroceded

Problem:

FK_PRIMARY_LIFE column of LF_CESSION table is not updated for placement cession

Solution:

The primary life detail of a joint life cession should be stored in the database on the cession, retrocession and placement levels. 

Problem:

Getting abend in loading a joint life batch through cession laoder

Solution:

Solution as per SE-26893 should be applied to joint life insurable object also: 

 If there is another transaction with the transaction code New Business or Old Business that is loaded on the same active cession benefit where the same BC-IP and policy number / cedent ref number and life id referenced - For both single life and joint life then the record should be rejected with the confirmation message LCH0018 'A cession is already covering a benefit with the same insurance product....' The cession benefit should not be renewed

Problem:

On Webservices, system is generating a walkback file on executing the Operation amendOtherLfStandaloneIndividualRetrocession.

Solution:

It should be possible to create an amendment or termination transaction on a standalone retrocession benefit through webservices without abend. This is irrespective of whether there is a linked inward cession or not

Problem:

Abend in subsequent transaction on Retention corridor 

Solution:

If the retention corridor has not been applied in the first transaction it should not be considered in any subsequent transactions. The system should not abend and the retros should continue to be created using the QS% and the capped retention as defined on the L condition

Problem:

System is creating RPO / RPCO without any Assumed Business or Protection Program through webservices.

Solution:

Similar to online functionality it should not be possible to create an RPO through webservices without a Protection Program and an Assumed Business. The same messages as per online functionality should be thrown when the PP or AB is missing on the RPO

Problem:

On Webservices, missing element to define the 'Business ID' on the Operation 'create Order' xsd:Retrocession Claim Procession Order

Solution:

Include the element to include Business ID in the claim processing order API. This should accept an assumed business id as per online functionality

Problem:

System is not updating the Retention Corridor, Modification Condition & Cut of Lower Limit Tab on the Limits Condition of business through webservices.

Solution:

 The update and create webservices for the Limit condition should update all the tabs and all the fields in the tabs on the L condition for Surplus, Quota Share and Capped Quota Share

Problem

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

Solution:

The classifications on the RPO should be updated based on the PP that is attached. When there is a PP that is replaced on the RPO either on a copied RPO or a RPO that is edited to change the PP while creating it the classifications should be updated as per the attached PP

When the PP classifications are not a subset of the AB classifications the message LCH225 -The classifications of the protection program should be a subset of the classifications of the Assumed Business'' This will be applicable for RPOs where there is one PP ++

Problem:

Outward Cedent's Contract realized from Protection Program abends when adding 'reinsurance premium method' from 'create child section' window

Solution:

When trying to add or create child sections on the OCC and there is no Reinsurance Premium method on the Agreement level then the process should be stopped with the error message BS0060 'Missing Mandatory Selection of Reinsurance Premium Method'
The user should be forced to select the Reinsurance Premium method on the Agreement section before adding or generating the child sections
On the generated or added child sections the reinsurance premium method should then be inherited from the agreement section as per existing functionality

Problem:

Can't delete leaf section from specific date as part of an amendment

Solution:

Even if placements are linked when the OCC is amended and the section is cancelled as part of an amendment, the section should be cancelled. The cancelled section should be reflected on all the linked placement businesses also

Problem:

Solution:

Declination Reason:

(Delete as applicable one of above)

Workaround:

Root Cause:

Extent of Impact:

Impact on Existing Data

Recovery Method for Existing Data Affected

Problem:
System Abends while running RPO with Parameter Use Transaction date for Retrocession Processing selected.

Solution:

When the system parameter Use Transaction date for Retrocession Processing is selected'

The RPO should pick up all cession benefit transactions that have an Original Transaction Date that fall within the Effective Date of the order

Any referencing to the linked OCC should be done based on the transaction effective date. The validation of the treaty limits, premium, deduction condition etc (all conditions and classifications) should be done based on the transaction effective date

When the system parameter is not selected: Always use the transaction effective date when picking up cessions benefit transactions that fall within the effective date and ignore the original transaction date. 

The original transaction date in this case will be used only to sequence the accumulation of cessions. So when there are several cession benefit transactions with the same transaction effective date, all will be picked up by the RPO if the transaction effective date falls within the effective date of the RPO. Here the original transaction date will not be considered for picking up the cession benefits. Then when the RPO sequences the cessions the cession with the earliest Original Transaction Date will be picked up first and the retention will be used by this cession and so on. 

Problem:
Incorrect ACI's are calculated on Placement cessions when Calculation rule is defined on the OCC and defined Multiple Placements.

Solution:

When the PM condition on the placement level is not overridden then the ACIs that are calculated on the retrocession cession level should be retroceded to the placements in the defined percentage (or the ACIs should be calculated on the placement level and summed up on the retrocession cession level - OE to check the sequence in the code)

When the PM condition is overridden on the placements, then the premium should be calculated on that particular placement independent of the definition on the OCC level

This will apply to any ACI that is calculated using the premium as a basis - eg deductions or any ACI that is defined as a separate value that is not dependent on the premiums - eg: Other Deduction as a fixed amount

Problem:
System abends while creating claim with event date falls in future date through loader.

Solution:

When the claim event date is a future date (greater than today) the batch should fail with the existing error message  'Event Date cannot be in future' (this will Applicable for ceded and for non ceded claims)

When the claim event date is a date that falls outside the active effective period of the cession benefit then when the claim is created on a non ceded  cession with a status of Valid or Outstanding then the error message 'Missing Renewals. Claim can only have a status Preliminary' should be thrown

When the claim event date is a date that falls outside the active effective period of the cession benefit then when the claim is created through loader on ceded cession then reject the claim record that is loaded with the existing warning message as LCH283 - 'Claim event date is a outside the latest active effective period of the cession benefit. Do you want to continue?' and in Loader is should always answer as NO.

Problem:

System is allowing to create RPO/ RCPO, when PP has linked OCC with PM condition Calculation Frequency other than Original through webservices 

Solution:

When the Create RPO/ RCPO webservices are run on an environment where the system parameter 'Method of Retrocessions Sequentially in excess of Retention' is selected, then when the included Protection Program has OCCs where one or more of the PM conditions have a Calculation frequency other than Original, then the same validation error as per online functionality ''LB0114 - One or more OCCs linked to the PP has a calculation frequency that is not As Original or the PM condition has not been defined'should be thrown and the user should not be able to create the RPO or RCPO

When the system parameter 'Method of retrocession is proportional in excess of retention' IS selected OR when the system parameter 'Sum at Risk Standalone Retrocessions only is NOT selected no validation of the calculation frequency should be done

Problem:

The Retrocessionaire Percentage is not updating correctly on the Retrocessionaire Cession/Placement Level of Cession.
 

Solution:

 The value in the field Retrocessionaire percentage should be calculated as Retro SAR of placement/ SAR For Retrocession of inward Cession.

The value should be calculated on each transaction and it will change when the Retro SAR is changed on the OCC level

The value should be rounded off to 6 decimals

Problem:
Rename System Parameter Use Transaction date for Retrocession Processing to 'Use Original Transaction date for RPO and RCO'

Solution:

Rename the system parameter 'Use Transaction date for Retrocession Processing' to 'Use Cession Benefit Original Transaction Date while processing the RPO and RCO'

The parameter should visible and available for selection only if in Base Company Specific Settings>>> Retrocession Basics, 'Sequencing based on Original transaction date' parameter is selected.

Problem:

Incorrect adjusted ACI calculation when we increase expiry date with 'Other' transaction on retrocession.

Solution:

When the expiry date is updated as per an Other transaction calculate the ACIs on pro rata basis for the other transaction from the previous expiry date till the the updated expiry date even if there is no change in any other parameters on the cession benefit

Problem:

Incorrect ACI calculation when expiry date is reduced with Extended term transaction on Retrocession

Solution:
For an extended term transaction the ACIs should be calculated for the extended period on pro rata basis as on the expiry date when the expiry date falls within the active effective period of the cession benefit

If the expiry date is outside the active effective date of the cession benefit then no ACIs will be calculated

Problem:
System abend while creating Proportional standalone claim through Loader.

Solution:

The standalone claim should never need to reference any cession. It should be loaded and processed through the batch loader without an abend

Problem:

Inward Cession created through Loader | Identifier for Individual Standalone Retrocession Placement is not correct

Solution:

Irrespective of the system parameter 'Cession Benefit Identifier Series in Use' is selected or not

The identifier series set on each type of cession in the system parameters should be used when the cession, retrocession and placement cession are created.

When the inward cession is created manually or through the loader and the cession identifier series is used (not the batch identifier) then the inward cession should get the defined identifier series and the retros and placements that are created through the RPO and linked to these cessions should get the same identifier series as defined in the system parameter for the respective retrocession types

When a standalone retrocession is created manually then the defined identifier series should be used for the standalone retrocession and placement cession

The Cession benefit identifier series will not be applicable to retrocession cessions and will also not be visible on the screen. This will only generate an identifier series in the back end for each cession benefit and use it for sequencing (has now been replaced with the sequence number) 

Problem:

SICS gets stuck, when we load the policy file with the First record having BENEFIT_SEQ_NO format: 'numberEnumber'

Solution:

The benefit sequence number can be of any format since it is a free text string field

Irrespective of the type of value in this field the policies should be loaded and processed to create the cession benefit transactions

When sequencing use the sequence the numbers as per numeric sequencing and then alpha numeric and then string (as per existing logic)

Problem:

Unable to process Fac placement with closed ended OCC

Solution:
When a cession benefit has already been placed to a closed ended fac OCC which has the termination option as Existing Business Runs off then any increases in subsequent transactions should continue to be placed to the same OCC even if the subsequent transaction effective date is outside the insured period of the Fac OCC

If the Fac OCC has been terminated with any other option other than existing business runs off then throw the message LCH185 The insured period of the business is terminated or cancelled.

If the cession benefit transacion is being placed for the first time to a Fac OCC then the transaction effective start date should fall within the insured period of the Fac OCC. If not the message No Matching Classification because one or more of the classifications or insured period of the OCC is invalid

Problem:
ACI's are incorrectly calculated for the transaction---extended term

Solution:

For an extended term transaction or an Other transaction where the expiry date is reduced, the ACIs should be calculated as per the updated expiry date on pro rata basis as on the expiry date, when the expiry date falls within the active effective period of the cession benefit based on the last active transaction on the cession benefit within the same effective period

Problem:
In RPO and RCPO in Protection Program field a Colon symbol displays and Make issue in referencing PP in for first time.

Solution:
The field on the RPO and RCPO where the user is expected to input the PP identifier should always be blank without any text or characters when the RPO or RCPO when the flag Classification as per PP is selected and the user should be able to input the PP identifier directly.
 

Problem:

 Under Cession Benefit Details, additional classifications of objects are not available in the life universe.

Solution:

In the Life Universe, under the Cession Information folder, we need to add additional classification objects under two folders.

*Retro cession.–> Main Retro ->Agreement and Benefits-Retro

*Benfit Details:-> Agreement section.

Problem:

Solution:

Declination Reason:

(Delete as applicable one of above)

Workaround:

Root Cause:

Extent of Impact:

Impact on Existing Data

Recovery Method for Existing Data Affected

Problem:

Abend while saving deduction condition on Assumed business

Solution:

It should be possible to save the deduction condition on all levels of business after edit or after creating the condition for the first time without abend
 

Problem:
Multiple Claim issue, in different clime status and in event date referencing and by using Historical claim flag.

Solution:

A transaction reversal status should always be created AFTER the active claim status that it has reversed and the amendment number of the transaction reversal should be greater than the source status. Once the transaction reversal is created the claim ACIs of the source status should be reversed. The Cancelled status should be the final status on the claim after the transaction reversal has happened.

The Transaction Reversal type of transaction should not reference the linked cession benefit or validate anything on the linked cession benefit. The Transaction Reversal should reverse the immediate previous active claim status and reverse the claim ACIs and set the claim to cancelled

When the Historical flag is selected the claim event date can be earlier than the first active effective period on the cession benefit

If the claim event date is within an active effective period or later than the active effective period then throw the warning message 'Claim Event Date is not prior to the reinsurance start date of the cession benefit. Historical Claim flag will be removed' and remove the flag in the claim wizard screen for the user to proceed with the claim as a non historical claim.

When this scenario is processed through the loader run this message in the background, list this message on the status and create the claim as a non-historical claim as per existing functionality with the existing validations of a non historical claim

When a batch is loaded with the claim event date that falls outside the active transaction effective period of the linked cession i.e the renewal effective period, then the claim record should fail with the message Claim event date is a outside the latest active effective period of the cession benefit. Do you want to continue?'

As per existing functionality this message should be answered as N and the record should not be processed

Problem:

Retroceded percentage isn't consistent between different transactions

Solution:

 When the flag 'Fixed Ceded Percentage throughout the life cycle of the cession' is selected :

The ceded percentage field should be calculated in the new business transaction and this should be applied throughout the life cycle of the cession benefit. The value in the field ceded percentage should be copied from the New Business transaction and not be updated on each transaction

The ceded percentage should be rounded off to 6 decimals when calculated

The same ceded percentage should be applied to the claims also

Problem:
Unable to create retro claims for cessions which are retroceded when assumed business is defined in the RCPO

Solution:

When there is no assumed business in the RCPO then all the valid claim transactions on cessions that have been retroceded through the linked PP/ PPs which have a payment due date that fall within the period end date of the RCPO should be picked up for processing

When no assumed business is part of the RCPO do not validate any classifications against any assumed business classifications

When there is an assumed business in the RCPO then using the same criteria as mentioned above, pick up the claims that are linked to that assumed business. No classifications should be validated

Problem:

 New views must be included in the Life universe.

Solution:

We can add the views listed below to the most recent version.

V_GRP_TRANSACTION_CODE

V_TRANSACTION_CODE

V_TRANSACTION_CODE_INWARD.

Problem:
System is not updating the Termination option, when a Reinsurance Program is created through Webservices.
 
Solution:
System is not updating the Termination option, when a Reinsurance Program is created through Webservices.
 

Problem:

 System is not poping up the Validation message on Renewal/Termination of Closed Ended Buisness, when the Existing Business Runs Off Flag is not checked and no Termination Option is selected.

Solution:

When the flag Existing Business Runs off is deselected then the Termination Options should always be defaulted and one of the options should always be available as selected. The dropdown should never be blank

This is applicable to both when the termination option is to be selected at the time of creating the treaty in the NB wizard, copying the business or selecting the option in the renewal wizard or at the time of registering the termination

This is applicable for both individual and bulk administered business 

This works as expected on an inward business and the termination option is always listed by default while registering the termination

Problem:
Incorrect commission calculation for outward cession with monthly frequency and monthly expiry date

Solution:

When the cession has the ceded flag selected calculate the annualised premium and then apply the calculation frequency value to each transaction for calculating the premiums as per existing functionality

When the first year commission is defined as divided across all periods in the first year then apply the commission rate to each transaction on the calculated premiums

When the first year commission is defined as All in Period One calculate the total commission for the premium paying term of the cession for the total premium that will be payable for the period and create the commission ACI in the first new business transaction

The above is applicable to both inward cessions, standalone retrocessions and retrocessions created through the loader

When the Extra premium commission is defined as per basic commission or independently the basis on which it has been defined should apply to all the extra commissions calculated

Problem:

 System is allowing to create RCPO, when OCC has PM condition Calculation Frequency other than the Original in Standalone Env.

Solution:

When the system parameter Method of Retrocession 'Sum at Risk Sequential in excess of retention' is selected and the Fac OCC that is added to the RCPO has a calculation frequency other than Original then throw the same message that appears when a PP with invalid OCCs are attached ''One or more OCCs has a calculation frequency that is not As Original or the PM condition has not been defined''
This is applicable to both online and webservices
 

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:

Show cede percentage in case SA > retention < minimum cession

Solution:

Introduce a new field 'Ceded Percentage - Retention Corridor'  to show the ceded percentage when the SAR is within the retention corridor and the SAR is retained even though it is above the defined retention. The Ceded Percentage  should be updated as SAR for Retrocession- Retention on the OCC / SAR for Retrocession

Problem:

'SAR for retrocession' amount with decimal places

Solution:

When the system parameter 'SAR in Decimals' is selected then the value in the field SAR for Retro cession should be displayed with the same number of decimals as defined in the system parameter similar to the other fields on the cession benefit

Problem:

Show cede percentage in case SA > retention < recapture limit

Solution:

Introduce a new field to show the ceded percentage when the SAR is within the retention corridor and the SAR is retained even though it is above the defined retention and below the recapture limit. The Ceded Percentage  should be updated as SAR for Retrocession- Net Sum Retained / SAR for Retrocession

Problem:

 On a closed ended STP OCC, system abends when the user unchecked the termination registered flag.

Solution:

It should be possible to register the termination on the STP OCC without abend and the termination option can be different from the termination option on the linked assumed business
The system should not abend when changing the termination option on the STP or updating the termination registered flag

Problem:

 When defining placements for a Prop OCC created through Single Treaty Protection on a Non-Prop Inward business, system abends.

Solution:

Placements on the STP on both the prop and non prop assumed business should be created without abend
 

Problem:

 Decrement Basis is not calculating on the Cession NB transaction when created through loader.

Solution:

Similar to manual online calculations, the decrement basis as defined on the SR condition should be applied to the cession benefit transactions when processed through the cession loader when the calculation responsibility is Reinsurer

Problem:
On renewal of Business, the new main currency is not updating if it is changed.

Solution:

 On a renewal period it should be possible to change and save the main currency of the business. When this is changed and there is a mismatch between the currency on the Limit condition or any other condition that has been copied from the previous insured period the existing warning message should be thrown and the user should be forced to update the currency on the relevant conditions

If the currency is already part of the additional allowed currencies then the existing error message that the currency is already on the additional currencies should be thrown

Problem:

Can't update CW booking date because of AC0797 Error message

Solution:

When the As of From Date on the order is within the Accounting period of the bookings created on the worksheets then the message AC0797 should not be thrown.
When the As of From Date on the order is outside the Accounting period on the bookings then throw the message AC0797 - 'As of From Date is outside the valid accounting period of the bookings'

Problem:

 The Retrocessionaire % Field is not updating when the retrocession are created by STP OCC.

Solution:

 Similar to retrocessions processed through the RPO, when the retrocessions are created through STP protections or QSR protections that are created on the PP condition of the Assumed business :

The value in the field Retrocessionaire percentage should be calculated as Retro SAR of placement/ SAR For Retrocession of inward Cession.

The value should be calculated on each transaction and it will change when the Retro SAR is changed on the OCC level

The value should be rounded off to 6 decimals

Problem:
Reinsurance premium can not generated when calculation rule use variable: %retroSumAtRiskOfRetrocessionaire

Solution:
When the variable %retroSumAtRiskOfRetrocessionaire (or any other retrocessionaire level variables) are part of the Premium Calculation Rule defined on the OCC, then calculate the premium on the placements using these variables on the placement level and sum them up on the OCC level

Aim of function

The aim of the function is to be able to include Fac OCCs in the Webservices for Retrocession Claim Processing Order.

Business value for customers

Customers will now be able to run their Retrocession Claim Processing Order webservices to include the facultative retrocessions also.

System Parameters Affected

None

Existing functionality affected

The Create Retrocession Claim Processing Order webservices will be able to include facultative OCCs for recovery

Aim of function

The aim of the function is to be able to see the child section on which the condition has been amended from the Amendment tab and also to be able to navigate to the respective effective periods and amendments on open ended businesses in Life

Business value for customers

When the treaties are structured based on insurance products the treaties could have several hundred child sections. When a specific condition on one or more of the the child section are amended it will now be easier for the user to know which section and condition was amended from the list of conditions in the amendment tab

System Parameters Affected

None

Existing functionality affected

A new column is available on the Amendments Tab- Amended Conditions. Whenever a condition or classification is amended on a child section or a child section is added or deleted as part of an amendment, the amended child section detail will be listed on this tab

A new sub tab on the Amendments Tab 'Amended Sections'. When any child section is either added or cancelled as part of an amendment the details will be listed on this tab

Aim of function

The aim of the function is to extend the Functional Currency Revaluation Order that is currently available in the P&C system to Life.

Business value for customers

Life customers will now be able to calculate the Functional Currency movements due to exchange rate differences by running the functional currency revaluation order and keep track of the gains and losses caused due to the exchange rate changes over specific periods
 

System Parameters Affected

The following system parameters are now available in Life Accounting- > Currency- > General

1. Allow Functional Currency Revaluation
2. Use Extraction Criteria in Functional Currency Revaluation Order
3. Include Realised Loss/ Gain in Functional Currency Revaluation

In the P&C system the P&C specific system parameters Accounting- > Currency- > General has been reordered as below

Existing functionality affected

Under Periodic Functions in Life the following Order will now be available

Functional Currency Revaluation Order

On running the order with the mandatory criteria, the Functional Currency will be revaluated and the Movement for Loss or Gain due to Exchange Rates will be calculated on the respective balances as selected

Aim of function

The aim of the function is to include 7 more 'Other Info' fields from the cession, retrocession and placement to be part of the Calculation Rules

Business value for customers

For more complex calculation rules where different conditions may need values from different fields of the cession benefit it is now possible to use more of the Other Info fields in the SAR calculation and Prop Premium Calculation rules

System Parameters Affected

Seven more 'Other Info' fields from the Cession, Retrocession and Placement Cessions Variables are now available under the calculation rules under Business SAR Calculation Rules and Prop Premium Calculation Rules

Existing functionality affected

Sum at Risk Calculation and Prop Premium Calculation rules can now be created to include Other Info fields Other Info 11 to Other Info 17

Example:

Aim of function

The aim of the function is to be able to renew the reinsurance program through web service API

Business value for customers

Customers will now be able to renew the reinsurance programs and the underlying treaties through web service API

System Parameters Affected

None

Existing functionality affected

It will be possible to include a reinsurance program for renewal in Renew Business web service API.
This is an improvement to the existing renewReinsuranceProgram operation on the SicsWsBusinessEntryPoint.

Aim of function

The aim of the function is to improve the performance of the UX when opening certain business conditions on treaties with several child sections and active cessions

Business value for customers

When business conditions like the PL condition or the SR or PM condition are inherited and the treaty has several child sections, opening the condition on child sections will be faster since the system will now not check all the other child sections that use the same inherited condition for active cessions

System Parameters Affected

None

Existing functionality affected

Opening the PL, SR and PM conditions on treaties with several sections is now significantly faster since active cessions on other child sections inherited from the same parent section are not checked each time the condition is opened on another inherited section

Aim of function

The aim of the function is to allow the users to decide how the confirmation messages are answered by the cession loader while processing the cessions

Business value for customers

All confirmation messages that are thrown while running the cession order were earlier answered as Yes by default to allow the cessions to be processed. Now it will be possible for the user to choose whether to answer some of the messages as Yes or No. This will provide more flexibility so that the processing can be done as per the specific business requirements and when the messages are answered as No, the transaction will fail and be available for further investigation by the end users. 

System Parameters Affected

A new system parameter option 'Cession Batch Confirmation Messages' is available on the System Parameters – > Cession

Existing functionality affected

On the system parameters - > Cessions- > Cession Batch Confirmation Messages is available. The list of confirmation messages that can be configured to be answered Yes or No is listed under this system parameter. All messages are by default answered as Yes

On the Assumed Business - NC condtion the same set of Confirmation Messages are available. The values are defaulted from the System Parameter Selection and can be overridden on the business level

The same set of confirmation messages selected/defaulted from the business condition will be available on the cession batch. These messages can further be overridden on specific batches before running them or updated on a failed batch before the batch is rerun

Aim of function

The aim of the function is to be able to renew all types of treaties through a web service API in SICS Life

Business value for customers

Customers will be able to renew closed ended prop and non prop treaties through webservices and also process terminations

System Parameters Affected

None

Existing functionality affected

New operation to renew closed ended treaties through webservices is available
This is a new operation on the SicsWsBusinessEntryPoint entry point: renewLfBusiness

Aim of function

The aim of the function is to be able to register termination on all types of closed ended treaties through webservices in SICS Life

Business value for customers

Customers will be able to process terminations on closed-ended treaties before processing the renewals

System Parameters Affected

None

Existing functionality affected

It is now possible to register a termination through a web service API on closed ended businesses before renewal.
This is a new operation on the SicsWsBusinessEntryPoint entry point: registerTermination