Problem:
Remittance Worksheet - Business Partner not found when ID is provided
Solution:
It should be possible to default the business partner in any find window by entering the business partner id or when the first few characters of the name are entered, the possible matches should be listed for selection

Declination Reason:

Workaround:

Root Cause:

Extent of Impact:

Impact on Existing Data

Recovery Method for Existing Data Affected

Problem:

Full surrender transaction got 0 ACI after Other transaction

Solution:

Any termination transaction should have the ACIs calculated for return premiums based on the Unearned Premium option selected in the AC condition

Declination Reason:

Workaround:

Root Cause:

Extent of Impact:

Impact on Existing Data

Recovery Method for Existing Data Affected

Problem:

SICS abends when running renewal orders

Solution:

When the Age calculation basis is Original no age recalculation should be done during renewals of the cession benefit or the retrocession cession benefit
The renewals of the cession through the cession renewal order or the retrocession cession through the RPO should happen without abend and without attempting to calculate the age

Declination Reason:

Workaround:

Root Cause:

Extent of Impact:

Impact on Existing Data

Recovery Method for Existing Data Affected

Problem:
Unable to add classification due to Dependency errors in the NB wizard

Solution:

When there is a parent or child dependency defined on the additional classification, this dependency should be validated at the time of creating the classifications on the business or at the time of editing classifications on an existing business.

If the selected classification value has the valid parent classifications and values available in the business Method and Coverage, it should be possible to add this classification to the business that is being created/ edited.

Declination Reason:
None

Workaround:
Remove the dependency defined on the additional classification value

Root Cause:

Extent of Impact:

Problem:

Cancellation not allowed on a business that has no cessions attached but termination has been registered

Solution:

When termination has been registered on an assumed business and there are no cessions linked to the insured period:

On selecting the option 'Edit' in the Insured Period tab the flag 'Termination registered' in the Additional tab should be editable.
On deselecting this flag then the insured period should be considered as it was before the termination was registered

When termination has been registered on an OCC and there are no cessions linked to the insured period

On selecting the option 'Edit Termination Details' in the Insured Period tab the flag 'Termination registered' in the Additional tab should be editable.
On deselecting this flag then the insured period should be considered as it was before the termination was registered

When there are cessions linked to the assumed business or OCC then the existing functionality should remain

Declination Reason:

Workaround:

Root Cause:

Extent of Impact:

Impact on Existing Data

Recovery Method for Existing Data Affected

Problem:
We have several missing objects int the P&C and Life Universe.

Please see the attached
Solution:

To create objects:

Unsettl Amt at Start of Prd (Func), Unsettl Amt at End of Prd (Func) and Movement Btw Start and End (Func)

Declination Reason:

Problem:

Extra Premiums are not calculated for joint life cessions

Solution:

When the Joint Life option uses any premium method other than when the statement option 'Separate Premiums'- Any loading should be calculated and created using the first life entry code for extra premiums
eg: In SICS4LIFE : When the premium is BAPR, the extra premium should be calculated using the BAPR and created with the entry code EMMP

When the statement option is 'Separate Premiums' and the premium ACIs are calculated with separate entry codes for the first and second live (eg BRPA and BRP2), then any extra premium should be calculated using the loading factor on the specific life and be created using the respective entry code
eg: When the basic premium is BRPA for Life 1, then if there is a loading on life 1 all extra premiums and extra commissions should be calculated and created using the Life 1 entry codes
When the loading os on life 2 that has the basic premium calculated with eg BRP2, then the extra premiums when applicable for life 2 should use EMM2

Declination Reason:

Workaround:

Root Cause:

Extent of Impact:

Impact on Existing Data

Recovery Method for Existing Data Affected

Problem:
Transaction number of adjustment reversal is not corrrect

Solution:

When the adjustment reversal transaction has a transaction number, this transaction on the cession benefit should be reversed and the same transaction number should be updated on the created adjustment reversal transaction

If the transaction number does not exist then the record should fail with the existing error messages

Declination Reason:

Workaround:

Root Cause:

Extent of Impact:

Impact on Existing Data

Recovery Method for Existing Data Affected

Problem:

No ACIs generated for reinstatement transaction when RPO is run

Solution:

After any termination transaction when a reinstatement is created on the retrocession the ACIs of the termination transaction should be created on the reinstatement transaction with the opposite sign

Any other transactions after the reinstatement should continue to have the ACIs calculated as per the calculation rules for any active transaction

Declination Reason:

Workaround:

Root Cause:

Extent of Impact:

Impact on Existing Data

Recovery Method for Existing Data Affected

Problem:
Benefit Term not getting updated for 2nd Benefit when created through loader

Solution:

When a new cession benefit is being created as a new business transaction on an existing cession as part of the same batch load or as part of a separate batch load, all details as mapped on the input record sould be updated on the created cession benefit that is created

Declination Reason:

Workaround:

Root Cause:

Extent of Impact:

Impact on Existing Data

Recovery Method for Existing Data Affected

Problem:
Preferred classification is not updating for individual life benefit when there are joint life and individual life benefits on the same cession
Solution:

All values as per the mapping should be updated on each cession benefit that is created on a cession

Declination Reason:

Workaround:

Root Cause:

Extent of Impact:

Impact on Existing Data

Recovery Method for Existing Data Affected

Problem:

GroupScheme number of lives is not updating through the cession loader

Solution:

ntroduce a new Cession Output Pattern 'Group Scheme Number of Lives'
This field should reference to the field Group Scheme Number of Lives' field on the 'Group Information' tab of the cession benefit for both individual and joint life benefit

The field Group Scheme Number of Lives should be removed from the Joint Life Other tab. The Group Scheme number of lives should be available only on the Group information tab for both single and joint life cessions and any referencing for calculations should be done using the value in this field

Any value that is mapped to the field NUMBER_OF_LIVES should update the field Number of Lives on the cession benefit (override the defaulted values if mapped) that is available on the Other tab for both individual and joint lives

The value that is mapped to the field NUMBER_OF_LIVES should not reference to the Group Scheme Number of Lives field irrespective of whether the GS ID is mapped or not

Declination Reason:

Workaround:

Root Cause:

Extent of Impact:

Impact on Existing Data

Recovery Method for Existing Data Affected

Problem:
Abend when we Inactivate Output pattern and Cancel
Solution:
Clicking on Cancel should cancel the process and the output pattern should remain active without an abend

Declination Reason:

Workaround:

Root Cause:

Extent of Impact:

Impact on Existing Data

Recovery Method for Existing Data Affected

Problem:

Validation of Business Covered in Non Proportional Business during Protection Assignment

Solution:

ONLY FOR NON PROPORTIONAL BUSINESS:
When creating a proportional protection assignment or a non proportional protection assignment on a non proportional business (PP condition or NP condition) do not validate the 'Business Covered' field while attaching the OCC

Declination Reason:

Workaround:

Root Cause:

Extent of Impact:

Impact on Existing Data

Recovery Method for Existing Data Affected

Problem:
SICS abends when Title of IO not available in DB but mapped in Loader

Solution:

Any change in Title. Full Name, First Name, Last Name, Middle Name in subsequent transactions should be updated on the same IO that is referenced as Alternate names

Declination Reason:

Workaround:
In the mapping create a rule to make the title always null or default it to Mr if Gender = Male and Ms if Gender = Female

Root Cause:

Extent of Impact:

Impact on Existing Data

Recovery Method for Existing Data Affected

Problem:

SICS abends while calculating ACIs for JointLife

Solution:

Always calculate the ACIs for each cession benefit within the cession using the respective values from each cession benefit as per the linked lookup table parameters.

Declination Reason:

Workaround:

Root Cause:

Extent of Impact:

Impact on Existing Data

Recovery Method for Existing Data Affected

Problem:

Retros are not created when the RPO ran after Lapse transaction date for NB and Renewal

Solution:

The RPO should pick up ALL cession transactions that do not have the Retroceded date set
It should then process each inward cession benefit transaction to create the corresponding retrocession transactions

Declination Reason:

Workaround:

Root Cause:

Extent of Impact:

Impact on Existing Data

Recovery Method for Existing Data Affected

Problem:

Above Participation limit flag on claim details tab is selected by default when claim is created through loader

Solution:

The above participation limit flag should be selected by default on a claim ONLY when the benefit sum reinsured value is above the value 'Participation Limit' defined on the RL condition of the business

The above participation limit and above notification limit flag should be selected ONLY when the benefit sum reinsured value is above the Notification limit defined on the RL condition of the business

When the RL condition does not have the values defined or any other option is selected then the flags should remain unselected

Declination Reason:

Workaround:

Root Cause:

Extent of Impact:

Impact on Existing Data

Recovery Method for Existing Data Affected

Problem:
The fields ‘Above Notification limit’ and ‘Above Participation limit’ should be added in the claims output pattern

Solution:
Two new output fields in the claim output pattern to be available

'Above Participation Limit' and 'Above Notification Limit' of type boolean

These fields will be defaulted based on the values defined in the RL condition of the business and the benefit sum reinsured

The fields will be editable- and if edited, any confirmation message that is given should be answered as Yes when the batch is processed.
No confirmation message that requires user intervention should be thrown when the batch is run

Declination Reason:

Workaround:

Root Cause:

Extent of Impact:

Impact on Existing Data

Recovery Method for Existing Data Affected

Problem:

System abend when updating the claim status to paid through loader

Solution:

When a new claim status on an existing claim is processed through the cession loader, if the status is one that is allowed i,e Paid status on a Valid claim, In Payment Status on a Valid claim with the cession being income benefit per frequency. Update Claim Reserve status on an In Payment Claim etc
then the new status should be updated on the claim

If the status is not an allowable status i,e one more Valid status on a Valid claim, Paid status directly, In Payment status on a claim where the cession is Capital Lumpsum etc, then the message <Status> is not a valid status should appear

Declination Reason:

Workaround:

Root Cause:

Extent of Impact:

Impact on Existing Data

Recovery Method for Existing Data Affected

Aim of function

To be able to process cessions by uploading a database

System Parameters Affected

None

Existing functionality affected

It is now possible to select JDBC Data Connection as part of one of the Datasource types when loading a cession or claim batch and processing the data from the database to create cessions in SICS

Aim of function: 

The aim of the function is to indicate that in a business, if estimation is set to complete
in the ES condition then no further projections are created through Projection Calculation Order

Existing functionality affected:

1.Life/ES condition/Projections tab
2.Projections will not be created through Projection calculation order after Selecting the
   Estimation Complete flag in the ES condition

Projection Basis-->Ultimate:

Projection Basis-->Yearly:

Aim of function

The aim of this enhancement is to use the value defined on the field 'Policy Year' in the cession benefit to calculate the commission and other deductions on the retrocession cessions that are linked to the inward cessions.

System Parameters Affected

None

Existing functionality affected

Retrocession cessions- Only when the Ceded flag is selected:

When an inward cession transaction is retroceded and the retrocession transaction it could happen that the retrocession transaction is a new business since the sum at risk on the inward cession has exceeded the retention only at a later stage in the life cycle of the cession.
When such a new business transaction is created on the retrocession, the deductions will be calculated using the value in the policy year on the inward transaction to identify whether the commission and other deductions would be applicable for the first year or subsequent years

Aim of function

1. To be able to apply percentage defined on the PC condition to the profit/ loss amount calculated as per the profit commission calculation rule selected
2. To be able to calculate and book a deficit under an informational entry code and carry forward this amount for the number of years as defined in the 'Deficit Carried Forward' field on the PC condition

System Parameters Affected

New entry code for automatic booking- Loss Carried Forward

Existing functionality affected

Profit Commission Calculation:

When the profit commission basis is defined as a Profit Commission Calculation rule from the system parameters, then SICS will calculate profit/ loss based on the calculation rule and then apply the percentage defined in the PC condition to calculate the profit commission when the profit commission order is run

Loss Carried Forward:

A new informational entry code 'Deficit Carried Forward' is available for selection and can be defined on the system parameter

When there is a deficit that is calculated by the profit commission calculation order, then this loss amount is booked as an informational amount with the entry code as defined

This amount will be considered in subsequent calculations of the profit commission for the number of years defined under the 'Deficit Carried Forward' field on the profit commission condition

Aim of function

The aim of this enhancement is to add a new type of transaction called 'Informational transaction' on a cession benefit

System Parameters Affected

None

Existing functionality affected

Cessions and Retrocessions:

Only when the Ceded flag is selected:

It will be possible to create a transaction 'Informational Transaction' on a cession benefit.
All details from the previous transaction will be copied to this transaction
All retrocession data from the previous transaction will be copied to this transaction
Informational Transactions will not be picked up during retroprocessing by the RPO
It will be possible to create an Informational transaction after a termination transaction. However, any further actual transactions after a termination will require the reinstatement to be processed as per existing functionality.