Problem:
Performance issue - Recovery Calculation for Protection Program

Solution:
Duplicate of SICSR-18588

Workaround:

Root Cause:

Extent of Impact:

Impact on Existing Data

Recovery Method for Existing Data Affected

Problem:
GOV TAX - Balance split for automatic Target EC bookings via PL

Solution:
When Instalment/Adjustment/Special Acceptance Premium is present on a Technical Worksheet, i.e. premium and deductions booked from premium & limit conditions, and Government Tax details have been automatically calculated and added on the worksheet, then the system must do the following:
1. When the worksheet is set to Closed by the user on the Worksheet Closing window, or the worksheet is automatically set to Closed, or the instalment is reversed, then the system must read the Balance Split option Government Taxes on the Worksheet (must also make sure that this is automatically ticked if the Government Tax Accounting task is given to a partner on the actual insured period) and if this is NOT selected, the system must add together all balances linked to the same instalment in an Account Balance Group. The Payment Partner, Base Company, Due Date, Accounting Year/Period and BP Reference for this ABG shall be taken from the instalment balance.

2. If the Government Tax Accounting task is given to a partner and therefore the Balance Split option for Government Tax IS automatically selected  on the worksheet (or if it is manually set by the user), then the system will keep the instalment/adjustment details as separate balances, create separate balances for the GT details defined in the entry code group GOVTAX (within the EC Group Category 'Business Partner Ledger Balance Split'), and set the Notes on ALL these GT balances to Government Tax and create separate balance for the other GT details (not defined in the above group). When the worksheet is closed the system will group the instalment/adjustment balance and the GT balance without the above Notes, in an Account Balance Group so that it appears financially on the BP Ledger as one balance and can be easily paired with the remittance. The GT balances with the above Notes will be kept outside the Account Balance Group.

Workaround:

Root Cause:

Extent of Impact:

Impact on Existing Data

Recovery Method for Existing Data Affected

Problem:
Reporting Unit which is not valid is included in recovery bookings when creating claim worksheet via Recovery Order. This is due to the fact that we do not validate against reporting unit when running recovery calculation order. We accept all reporting units, which means that when it is booked at a RU which does not exist at the OCC, the AC will be Invalid for OCC.
Reporting units reflect how the business is divided internally according to reporting structure, and is therefore not meant to be a part of the validation if a claim is recoverable under an OCC or not.
However, there is an issue when the SysPar 'Use RU from OCC/ORP in AC' is NOT selected (as in your DB set-up). The current solution does not split per Reporting Unit in AC, it just use one of the existing ones.

Solution:
When Reporting Unit is mandatory for base company (both for business and AC), and SysPar 'Use RU from OCC/ORP in AC' is NOT selected, the following solution should be implemented:

Use Reporting Unit as split criteria, and book at all ACs (including RU) from inward, which the claim details are split between. Note that this split will also be used for Reinstatement for Reinstatement Premium for this Outward Claim.

Note: Recoveries should still not be validated against Reporting Unit; this means that we will split according to inward even though the Accounting Classification becomes invalid at OCC.
Reporting units reflect how the business is divided internally according to reporting structure, and is therefore not meant to be a part of the validation if a claim is recoverable under an OCC or not.

Workaround:
None

Root Cause:
SICSR-23617 and SC-4210

Extent of Impact:

Impact on Existing Data

Recovery Method for Existing Data Affected

Problem:
Document Production Billing statement for selected Balances does not display instalments in sorted order

Solution:
When balances are listed in the document Billing Statement for selected Balances, the system should use the Due Date of the balances as part of the sorting criteria.

Workaround:

Root Cause:

Extent of Impact:

Impact on Existing Data

Recovery Method for Existing Data Affected

Problem:
Billing statement for selected Balances does not display net instalment - Issue No:2

Solution:
Installment section in template is coming with only Gross Premium output but it would also be needed to see the Net Premium per instalment and new tags are needed for this.

Workaround:

Root Cause:

Extent of Impact:

Impact on Existing Data

Recovery Method for Existing Data Affected

Problem:
Split Balances into Details issue

Solution:
1) Create a new system parameter named 'Affects Split of Balances into Details and Proportional Split as well'. It should be placed below the existing parameter 'Revers balance not allowed if Base Company on Business is changed' and must be enabled only if this existing parameter is selected.

2a) When the new system parameter is NOT selected, existing functionality will apply, i.e. the system will present message AC0404 and the text should be changed to 'You are not allowed to perform this operation because the Base Company on the balance is not the same as on the Business', only when the user performs the manual reversal of a balance.

2b) When the new system parameter IS selected, and the user performs the operation Split Balance into Details or the system is doing Proportional Split of a balance when the user performs a partial settled balance pairing, then the system will also present message AC0404 and prevent the user from completing the process if the Base Company on the actual balance is not the current Base Company on the business.

Workaround:

Root Cause:

Extent of Impact:

Impact on Existing Data

Recovery Method for Existing Data Affected

Problem:
GOV TAX - CL - SICS PROD - Gov Tax Comment Field not available & not possible to link Trigger/Target EC

Solution:
If a claim is linked to several businesses, e.g. an Assumed Business and an OCC, but only one of the businesses have activated the Government Tax Validation, we must make sure the Government Tax Category and Government Tax Comment columns are visible on the Claim Worksheet when booking on the business where the Government Tax Validation is activated.

Workaround:

Root Cause:

Extent of Impact:

Impact on Existing Data

Recovery Method for Existing Data Affected

Problem:
When creating a worksheet via web service that includes replacement value bookings with a new amount that has a rule including Claim then the previous amount is not located as the Claim is not set on the detail until after the amount to book is calculated.

Solution:
As per Headline Loss and other values included in replacement value rules, make sure that the values are populated on the new detail created by the web service before any calculation of previous amounts takes place,

Workaround:
If an open worksheet is created then open the worksheet which will trigger a recalculation of the amount which will now consider also the Claim.

Root Cause:
New replacement value rules to include Claim.

Extent of Impact:

Impact on Existing Data

Recovery Method for Existing Data Affected

Problem:
when Change Status/UNFI/process Message AFTER a 1st UNFI, system does not perform Gov. Tax Validation anymore: no error is triggered! This issue occurred in both scenarios (with correct Gov. Tax Error (SP1) and incorrect Gov. Tax Error (SP2)

User swaps to worksheet to create the link. He presses UNFI, goes back to the message and processes the message. Expectation: System to trigger Errors for Trigger EC without Target EC and Target EC without corresponding Gov. Tax Rule. Message processed without triggering the expected errors - INCORRECT

Solution:
If a TechAccount message is booking a new balance on an existing Claim Worksheet created by eMessageing (including FGU) then ensure that that balance is identified to have the eMessaging Gov Tax validation performed on its details.

Workaround:

Root Cause:

Extent of Impact:

Impact on Existing Data

Recovery Method for Existing Data Affected

Problem:
Not considered scenario where in previous Q is no retained, however validation in current Q expects release.

Solution:
Preconditions: Premium Deposit Conditions with Quarterly regulation

When applying a worksheet with only Paid Loss, i.e. no details with basis for premium deposit retained, we must make sure the system does NOT raise message AC0395 for validation rule Premium deposit retained, i.e. that the system expects corresponding detail in worksheet.
The same if worksheet only contains of Premium, i.e. no details with basis for loss deposit retained.

Workaround:

Root Cause:

Extent of Impact:

Impact on Existing Data

Recovery Method for Existing Data Affected

Problem:
Please find an other issue for Loss Deposit Scenario 2 which was found in SICS 22.1 SSP2
SwissRe ID: 1083060

Example: 1102760,UY2021

Loss Deposit Validation - Scenario 2
Validation AC0401 was not triggered and with release there was not calculated amount 0.

Solution:
When the basis is percent of loss deposit and a release is booked without a basis entry then the release amount should still be calculated and raise an error.

Workaround:

Root Cause:

Extent of Impact:

Impact on Existing Data

Recovery Method for Existing Data Affected

Problem:
Incorrect Loss Deposit Validation

Solution:
When the deposit regulation is Years, and the user book on 4th Quarter of an accounting year without booking a basis detail for the Loss Deposit Retained, e.g. Loss Reserve, the system shall still look for previously booked Loss Reserve and present error message AC0395 for the missing and required Loss Deposit Retained. This must also be the case for the Premium deposit.

Workaround:

Root Cause:

Extent of Impact:

Impact on Existing Data

Recovery Method for Existing Data Affected

Problem:
Government Tax details not created when instalments are booked via instalment order

Solution:
When running instalment or adjustment orders the system must also calculate Government Tax details if applicable. This should take place independent if the Automatic Booking flag is selected or not in the GT Rule.

When the Instalment or adjustment order runs, if it is with the Close worksheet selected or not, the system shall perform the GT calculations for all trigger entry codes.

Workaround:

Root Cause:

Extent of Impact:

Impact on Existing Data

Recovery Method for Existing Data Affected

Problem:
GOV TAX - CL - SICS 21.3 SP3 Hotfix2 - TECSNT02: Zero Target EC amount overwritten by automatic booking

Solution:
When both a Trigger GT entry code detail and a Target GT entry code detail exists on the worksheet and the user press Apply or select Change Status, the system shall NOT automatically re-calculated the target GT detail amount even if the details are Linked and the GT Rule has the Automatic Booking box selected. The system shall always trigger the AC0837 error message if the target GT amount is wrong according to the rule even if the amount is zero and the rule has the Automatic Booking box selected.

Workaround:

Root Cause:

Extent of Impact:

Impact on Existing Data

Recovery Method for Existing Data Affected

Problem:
Parameter ‘Partner Bank account optional for pending paid remittance ‘is not working when we try to generate payment request in different currency than main account bank currency

Solution:
When the system parameter 'Partner Bank Account optional for pending paid remittance' is NOT selected, i.e. Partner's Bank Account IS mandatory, and the user generates a Paid Remittance from a single technical or claim balance, the system must validate this remittance and give an error message if both the Partner's Bank Account and Intermediary Account is missing. It should only accept to save a pending paid remittance if either the Partner's Bank Account OR Intermediary Account is given. Should work in the same way as when you create a remittance manually or if you generate it from a Settlement Balance Group.

Workaround:

Root Cause:

Extent of Impact:

Impact on Existing Data

Recovery Method for Existing Data Affected

Problem:
GOV TAX - Hard Stop Category and Comment not emptied

Solution:
When a Government Tax Rule is triggered on a Technical or Claim Worksheet because only a Trigger GT entry code is given and the Target GT entry code is missing, and the user has given a Government Tax Category and Government Tax Comment on the Trigger GT entry code, we must make sure both the GT Category and GT Comment must be removed from the Trigger GT detail when the user enter a new detail with the missing Target GT entry code defined on the relevant GT rule and Apply the worksheet (or select any option that applies the worksheet to the database) so that the trigger and target details are linked.

Workaround:

Root Cause:
This issue has reoccurred because of the fix we did in SICSR-23712, in 22.2 and ported to 22.1_SSP2

Extent of Impact:

Impact on Existing Data

Recovery Method for Existing Data Affected

Problem:

Walkback running Multi GAAP Accounting Order

java.lang.NullPointerException: Cannot invoke 'com.csc.sics.business.insuredperiod.domain.SicsInsuredPeriod.isCeaseAccounting()' because the return value of 'com.csc.sics.accounting.domain.SicsInwardInstalmentPremiumBookingObject.insuredPeriod()' is null

Solution:

Remove abend

Workaround:

Root Cause:

Extent of Impact:

Impact on Existing Data

Recovery Method for Existing Data Affected

Problem:
“Replace Selected URB in Pairing” cancels the RM-URB pairing

Solution:
When users have selected the option 'Replace Selected URB in pairing' from the Business ledger so that the balance pairing window appears with the actual URB annulled from the pairing, and are in the process of committing the pairing, then the system must check if there are replacements of the annulled URB in the pairing. Only if there are new pairings, not yet committed in the pairing, that match the annulled URB, then the system shall accept this. But if there is a mismatch between the annulled URB and the new included balances (replacements), then a new error message shall prevent the user from committing the pairing. In this case the user must either include other replacement balances or press Cancel to interrupt.
One exception to the above test; if all balances in the pairing becomes fully Settled, then the system shall also accept this, even if there is a mismatch.

New error message should read: The selected Unallocated Remittance must be fully replaced before you can continue the pairing process.

Workaround:

Root Cause:

Extent of Impact:

Impact on Existing Data

Recovery Method for Existing Data Affected

Problem:
Instalment Order for Non-prop OCC does not calculate functional amounts ; AC_LEDGER_DETAIL.EXCH_AMT is zero

Solution:
When running Instalment or Adjustment order with Close Worksheet box selected, make sure the system calculates the FC Amounts on the AC_LEDGER_DETAIL and sets the FC Currency on the AC_LEDGER_BALANCE

Workaround:

Root Cause:

Extent of Impact:

Impact on Existing Data

Recovery Method for Existing Data Affected

Problem:

Unable to run Retrocession Calculation Order when registration is not completed for the following Insured Period.

Solution: 

Make sure it is possible to create and run a Retrocession Order on an Insured Period even if the Registration Complete flag is not set on a later Insured Period.

Root Cause:

Extent of Impact:

Impact on Existing Data

Recovery Method for Existing Data Affected

Problem:
No retroceded Bookings created when adding new ORP with copy to selected retrocessionaiere's option

Solution:
When a Fac ORP is created on the PP conditions by use of the option Copy Selected to Retrocessionaire, and the user replies Yes to the message AC0258 so that the changes are committed and correction bookings will take place on the changed retrocessionaries, we must make sure the correction bookings also take place on the new ORPs. In the same way as when the user selects the option Add and Realize Retrocessionaire.

Workaround:

Root Cause:

Extent of Impact:

Impact on Existing Data

Recovery Method for Existing Data Affected

Problem:
Unexpected AC0395 triggered for EC1000 and EC3000 and 3500 - Loss Deposit scenario 2 (ISSUE 23)

Solution:
When the deposit retained is based on reserves (loss or premium), and the deposit regulation is Quarters and Release in Same Account Next Accounting Year, then the system shall only use the adjustment of the reserve for the current Quarter as basis for the deposit retained each Quarter.

Workaround:

Root Cause:

Extent of Impact:

Impact on Existing Data

Recovery Method for Existing Data Affected

Problem:
Deposits - Validation AC0400 system is not able to find right retained deposit to the release - Loss Deposit scenario 13a (ISSUE 27)

Solution:
When the deposit retained is based on reserves (loss or premium), and the deposit regulation is Years and Release in Same Account Next Accounting Year, then the system shall use the adjustment of the reserve for all Quarters (in current Accounting Year and PREVIOUS Accounting Year) as basis for the deposit retained each Quarter and use this as the computed value in error message AC0770 if the deposit retained is not according to this computed value.

Workaround:

Root Cause:

Extent of Impact:

Impact on Existing Data

Recovery Method for Existing Data Affected

Problem:
Deposits - Validation AC0395 triggered in Q1 and incorrect AC770 - Loss Deposit scenario 13a (ISSUE 29)

Solution:
When Deposit Regulation is Years and the user has correctly booked Loss Reserve during the 1st Accounting Year and Loss Deposit Retained in the 4th Quarter in 1st Accounting Year and when booking a Loss Reserve in the 1st Quarter in 2nd Accounting Year, it is not expected any loss deposit retained in this quarter, then the system shall not accept a Loss Deposit Retained in this 1st Quarter. Loss Deposit Retained is expected only in the 4th Quarter each Accounting Year, and shall pass the validation in this quarter if the retained is based on the aggregated Loss Reserve for current and previous Accounting Years.
If Loss Deposit Retained is booked in other than last quarter of the accounting year, the message AC0770 shall appear telling that the computed value is zero and that this is not matching the detail amount in the worksheet.

Workaround:

Root Cause:

Extent of Impact:

Impact on Existing Data

Recovery Method for Existing Data Affected

Problem:
Deposits - Validation AC0395 for deposit retained by TOA 3000 - Loss scenario 1 (ISSUE 44)

Solution:
Even if the deposit is based on reserves, either Premium or Loss Reserves, and previous booked reserves within the current Accounting Year shall be aggregated to find the correct basis for the new Premium/Loss Deposit Retained, we must make sure that this aggregation only takes place if the current worksheet has adjustment of the reserve balance, i.e. there is either a Premium Reserve or Loss Reserve adjustment in this Accounting Year on the current worksheet.

Workaround:

Root Cause:

Extent of Impact:

Impact on Existing Data

Recovery Method for Existing Data Affected

Problem:

Selecting Placement Complete, when not having filled the Intermediary share up to 100%, the system does not accept the same interval for small deviations as the current check for Total Share for the entire outward cedent’s contract.

Declination Reason:

Development

Workaround:

1. Select Full Refresh to see the 'real' total signed share (99.999999%) 

2. When the signed share of broker is 100% then placement share through broker must be 100% rather than 99.9999999%. Therefore please add 0.0000001% to a Retrocessionaire 'Share of 100' to make it 100%.

3. Select the Placement Complete flag.

Root Cause:

Extent of Impact:

Impact on Existing Data

Recovery Method for Existing Data Affected

Problem:
Pre-renewal show strange values on different columns related to claims e.g. Paid Loss Amount

Solution:
New implementation

Workaround:
Create the package in a schema where its found.

Root Cause:

Extent of Impact:

Impact on Existing Data

Recovery Method for Existing Data Affected

Problem:
Document Production
Producing a new document from the attached template (Treaty Extract/ Test 2) the system no longer find the business details such as e.g. Business Identifier, Effective Date or Treaty Inception

Solution:
Document Production
Producing a document, e.g. Treaty Extract /'Test 2', the created document should not fail with message 'The selector 'business' is not defined for the interface SICSLifeCyclePhaseExternalInterface', but create a document with details existing on the business and defined in the document template, in the same way it correctly did in earlier versions, e.g. 4.8.6.
Make sure that, for example, the following details are displayed on the document produced:

• Treaty ID(s)
• Effective Date:
• Treaty Inception

Problem:

Able to create Bank, even when Defined User Role has only Read Access.

Solution:

Should not be able to create Bank when Defined User Role has only Read Access for Partners Banks Administration.

Workaround:

Root Cause:

Extent of Impact:

Impact on Existing Data

Recovery Method for Existing Data Affected

Problem:

Able to create business partner even when Defined User Role has only Read Access.

Solution:

Should not be able to create business partner when Defined User Role has only Read Access for Partners Business Partners Administration.

Workaround:

Root Cause:

Extent of Impact:

Impact on Existing Data

Recovery Method for Existing Data Affected

Problem:

Able to create Insured / Third Party even when Defined User Role has only Read Access.

Solution:

Should not be able to create business partner when Defined User Role has only Read Access for Partners Insureds Administration.

Workaround:

Root Cause:

Extent of Impact:

Impact on Existing Data

Recovery Method for Existing Data Affected

Problem:

Able to create new Person, even when Defined User Role has only Read Access

Solution:

Should not be able to create new Person when Defined User Role has only Read Access for Partners Persons Administration

Workaround:

Root Cause:

Extent of Impact:

Impact on Existing Data

Recovery Method for Existing Data Affected

Problem:
The frame around the insured period information (i.e. the From / To dates, Underwriting Year, Insured Period Duration) is not anymore present. It is now not clear to the user what the 'From' and 'To' dates/time stamps refer to.

Solution:
There should be a frame around the insured period information (i.e. the From /To dates, Underwriting Year, Insured Period Duration) for all levels of business that have an Insured Period Information.
This frame should be labelled 'Insured Period'.

Workaround:

Root Cause:

Extent of Impact:

Impact on Existing Data

Recovery Method for Existing Data Affected

Problem:

The system does not accept <None> for mandatory additional claim classification

Solution:

The system should validate that value is not null, but allow any value apart from that (otherwise available), including None

Workaround:

Root Cause:

Extent of Impact:

Impact on Existing Data

Recovery Method for Existing Data Affected

Problem:
Reinstatement Validation raises an error on missing (Limit Premium) Condition when the condition is correctly present but having Unlimited Cover.

Solution:
The test for a valid Limit Premium condition should include a test that the Cover can be unlimited

Workaround:

Root Cause:

Extent of Impact:
LPC having Unlimited Cover

Impact on Existing Data

Recovery Method for Existing Data Affected

Problem:

When Data Protection is activated for Claimant, Find Claims should never display the Claimant (always display Protected Data if anything is recorded), regardless of User Access right.

Solution:

Disregard User Data Protection Access Right in Find Claims. 

Claimant if recorded should be displayed as Protected Data, otherwise column should be empty

Workaround:

Root Cause:

Extent of Impact:

Impact on Existing Data

Recovery Method for Existing Data Affected

Problem:

The computed event limit amount is incorrect when converted into booking currency resulting in accuracy error being incorrectly raised.

Solution:

The system should compare the booking amount with the correct calculation of the computed amount limit.

Workaround:

Root Cause:

Extent of Impact:

Impact on Existing Data

Recovery Method for Existing Data Affected

Problem:

Claim worksheet fail to display entry codes with previous bookings when entry code restriction apply for user

Solution:

The worksheet should display entry codes with previous bookings provided they are included in the user's entry code restriction group

Change message/add new message   for the User EC restriction; 'Selected entry code (xxx) is not allowed according to your User Preferences'

The entry code must be deleted from the worksheet prior to applying/changing status

Workaround:

Root Cause:

SE-6863

Extent of Impact:

Impact on Existing Data

Recovery Method for Existing Data Affected

Problem:

When selecting to add a Headline to a Headline Loss Group, the system opens the find HL window, and the user can select existing HL, or create New HL.  When creating new HL and after having saved the new HL info, but not selecting/transferring this back to the group - the Headline is not created. 

If user does not close the Find Headline Loss window, further edit windows cannot be opened.

Solution:

1. When pressing Save on subedit create Headline Loss the system should create and commit the Headline Loss. This should not depend on Headline being selected/transferred
2. Find Headline Loss window should not be an edit window - that should be the create New Headline window only

Workaround:

Root Cause:

Extent of Impact:

Impact on Existing Data

Recovery Method for Existing Data Affected

Problem:

Distribution towards AAD is incorrect when Client IBNR and ACR 

Solution:

The system should distribute towards AAD in this sequence Paid, Res, CIBNR, ACR, before distributing towards layer. The total distribution towards AAD must not exceed the remaining for AAD group (ie AAD Paid, or AAD Res), and the overall distribution for the claim towards AAD and layer must not exceed the cover amount.

Workaround:

Root Cause:

Extent of Impact:

Impact on Existing Data

Recovery Method for Existing Data Affected

Problem:

Previous amounts in FGU distribution does not reflect client ibnr bookings made when the worksheet is still in open status

Solution:

 Previous figures should include open worksheets also for Client IBNR

Workaround:

Root Cause:

Extent of Impact:

Impact on Existing Data

Recovery Method for Existing Data Affected

Problem:

When Data Protection is in use and activated for Claimant, Find Claims 'Claimant' column is always displayed as empty, instead of Protected data

Solution:

If the system parameter for Claim Data Protection in use is ticked and the Claimant Name on Claims checkbox is also ticked then the column for Claimant Name (whatever it may contain) should display as 'Protected Data' on the Find Claims List. It should not attempt to read any data for this column.

Workaround:

Root Cause:

Extent of Impact:

Impact on Existing Data

Recovery Method for Existing Data Affected

Problem:

TestReceiverShareAgainstSignedShare abends when the message contains an invalid BrokerSharePercentage of zero.

Solution:
To take care of invalid messages a zero percentage BrokerSharePercent should be taken as being 100 (as if it were set as 100 or not provided at all).

Workaround:

Root Cause:

Extent of Impact:

Impact on Existing Data

Recovery Method for Existing Data Affected

Problem:
Lloyds Instalment messages (Contra, Correction) attaching to the wrong instalment.
While the message has referenced to an instalment, as it is a reversal of a referred original message, then the instalment booked on by the original message takes precedence.

Solution:
ReferRelatedMessagesByUUidReferenceRule (including by ServiceProviderReference) should try to match messages using (if present) Item Due Date, Lloyds Risk Code and InstalmentNbr.

If for some reason this should match against more than one original message then no reference should be made (to avoid matching to a wrong one). Processing without an original message will take place in this case (even if an original is present but cannot be automatically matched.) For Instalment messages the referred instalment on the current message will be booked on (rather than the instalment of the original message when that is referenced.

Workaround:

Root Cause:
ReferRelatedMessagesByUUidReferenceRule
Referred Message look-up check for messages with the same ServiceProviderReference plus additional checks on RiskCode and DueDate. Messages that have a ReferredTechAccount reference that does not uniquely identify a single message-

Extent of Impact:
Grouped Instalment messages that all have the same identical message ServiceProviderReference and reversal messages that only contain the referred TA with the SP ref. i.e. they do not contain uuid or uniquely reference a single message.
Where there are messages with DueDates but multiple Instalments due on the same date then the original message is randomly assigned to one of the matching messages.

Impact on Existing Data

Recovery Method for Existing Data Affected

Problem:
Unexpected - SYN0002 - The Amount field is required but has not been specified - error
when booking informational adjustments from new previous amount calcuations in SE-6908

Per IP, Occ Year, Section, AC, HLL, CLM
Per IP, Orig UW Year, Section, AC, HLL, CLM
Per IP, Section, AC, HLL, CLM

Solution:
Ensure that the new calculations of previous amounts also work for eMessaging

Workaround:

Root Cause:

Extent of Impact:

Impact on Existing Data

Recovery Method for Existing Data Affected

Problem:
FA Item linked automatically to No Transfer to Ledger worksheet SICS eMessaging Settlement message

Solution:
If a balance with Not Transfer to Ledger is automatically selected (not possible manually) then it should not be linked to the FAI but rather an error stating that a balance has Not Transfer to Ledger has been identified.

Workaround:

Root Cause:
Automatic linking of a claim balance to FAI not testing for Transfer to Ledger

Extent of Impact:

Impact on Existing Data

Recovery Method for Existing Data Affected

Problem:
A couple of parameters have now disappeared from the standard edit window for processing options in eMessaging.

Solution:
Resize edit window for processing options in eMessaging so that all fields show as default.

Workaround:
Resize window and save as system wide settings.

Root Cause:

Extent of Impact:

Impact on Existing Data

Recovery Method for Existing Data Affected

Problem:
If the label of the tax column is Tax % as instructed in the user guide, then the next columns, e.g. Notes are not correctly set on the worksheet.

Solution:
Update the user guide, both P&C and Cede, in the Find Worksheet chapter, Import Worksheet Details section with the below:
The column name for Tax % must be changed to Tax%.
In the same chapter about the Is Estimate column the description must be changed to this:
If the column 'Is Estimate' is set to Yes, the bookings are made on the Estimates tab, if it is set to No or left blank, the bookings are made on the Actual tab of the Worksheet.

Workaround:

Root Cause:

Extent of Impact:

Impact on Existing Data

Recovery Method for Existing Data Affected

Problem:

Currently the Report Unit Name can only be unique and cannot be duplicate. On the opposite way, The Reporting Uni Code is not unique and can be duplicated. To be consistent, both items should be unique and it should not be possible to duplicate them

Declination Reason:
Enhancement

Workaround:

Root Cause:

Extent of Impact:

Impact on Existing Data

Recovery Method for Existing Data Affected

Problem:   Do not have any years beyond 2020 generated in the TIRG_YEAR table.

Solution:  In order for triangulation reports to work properly there need to be a few more years added. In new SSP through database batches, we can provide the code to insert values in the TRIG_YEAR table. (2021-2035)

Workaround:

Root Cause:

Extent of Impact:

Impact on Existing Data

Recovery Method for Existing Data Affected

Problem:

Joins incorrect in partner universe for bank accounts,

Solution:

Universe corrected.

Workaround:

Root Cause:

Extent of Impact:

Impact on Existing Data

Recovery Method for Existing Data Affected

Problem:  BOAC005 performance issues

Solution: Need to generate a new BOAC005 Script.

Workaround:

Root Cause:

Extent of Impact:

Impact on Existing Data

Recovery Method for Existing Data Affected

Problem:
Balance pairing does not take place when remittance is reversed

Solution:
When the following system parameters are selected:
'Independent creation of Cash Paid remittance not allowed' under Accounting, Balance Pairing
'Mandatory - Rem Class 1' under Accounting, Remittance
'Automatic Balance Pairing when change of Remittance Status' under Accounting, Balance Pairing,

and the user reverse an Unsettled Received Remittance balance in status Final and also sets the status of the new remittance to Final,

the system shall perform a full balance pairing between the source and the target remittance and make both of them Settled.

Workaround:

Root Cause:

Extent of Impact:

Impact on Existing Data

Recovery Method for Existing Data Affected

Problem: Facing issue while generating Boac scripts

Solution: In Script Directory, give the location of the folder where the user wants to save the scripts, Select the scripts that you want to generate. Select Create radio button and then Click on the ‘Generate Script’ button.

Problem:
Generated Oracle BOAC scripts are missing commit statements

Solution:
Add commit statements into the generated BOAC scripts.

Declination Reason:

Workaround:

Root Cause:

Extent of Impact:

Impact on Existing Data

Recovery Method for Existing Data Affected

Problem:  Data is getting duplicated in BOAC_JT_ECG

Solution:  Remove the code from BOAC which was causing the duplication of data. 

Declination Reason:

Workaround:

Root Cause:

Extent of Impact:

Impact on Existing Data

Recovery Method for Existing Data Affected

Problem:

Payment Partner details

Solution:

Joins corrected.

Root Cause:

Extent of Impact:

Impact on Existing Data

Recovery Method for Existing Data Affected

Problem: Lost the ability to select a date and retrieve the latest adjustment back in time, or nearest to the date selected.

Solution: Need to change the views in DB and make some joint changes at the universe level.

Workaround:

Root Cause:

Extent of Impact:

Impact on Existing Data

Recovery Method for Existing Data Affected

Problem:

HL - Cause of Loss

Solution:

Corrected implementation

Workaround:

Root Cause:

Extent of Impact:

Impact on Existing Data

Recovery Method for Existing Data Affected

Problem:

New object for related business

Solution:

New view implemented to get related business.

Workaround:

Root Cause:

Extent of Impact:

Impact on Existing Data

Recovery Method for Existing Data Affected

Problem:

System abends when user is attempting to open a claim which is restricted by user's domain restriction.

Solution:

When user is attempting to open a claim which is restricted by Domain Restriction, the system should not abend but raise standard security message (“You do not have access rights to perform this function”).

Workaround:

Root Cause:

SE-6535

Extent of Impact:

Impact on Existing Data

Recovery Method for Existing Data Affected

Problem:

Able to update P&C System Parameters despite relevant Use case is not assigned to the User Profile.

Solution:

Should not be able to update P&C System Parameters when the use case System Parameter Administration P&C is not assigned to the User Profile.

Workaround:

Root Cause:

Extent of Impact:

Impact on Existing Data

Recovery Method for Existing Data Affected

Problem:

Not all protected businesses retrieved

Solution

Web service should return all the protected businesses, not just the first 50.

 Workaround:

Root Cause:

Extent of Impact:

Impact on Existing Data

Recovery Method for Existing Data Affected

Problem:
Possible to define two different FC Exchange Rules with same Entry Code

Solution:
1. When a specific Functional Currency Exchange Rule is created/edited and saved to the database, the system must check that it does not contain same Entry Code as in other rules with same Worksheet Type and Type of Business.
New error message: Same Entry Code found in another Functional Currency Exchange Rule. This is not allowed.

2. When a specific Functional Currency Exchange Rule is created/edited and saved to the database, the system must check that it is unique, i.e. that the same combination of Worksheet Type, Type of Business and Exchange Rate Category does not exist from before.
New error message: Combination of Worksheet Type, Type of Business and Exchange Rate Category is found in another Functional Currency Exchange Rule. This is not allowed.

Allowed:
Technical Account, Booked Date - Daily Rate, Proportional Treaty, 10 Written Premium
Technical Account, Inception Rate - Daily Rate, Proportional Treaty, 83 Loss Reserve, 81 Premium Reserve

Not Allowed:
Technical Account, Booked Date - Daily Rate, Proportional Treaty, 10 Written Premium
Technical Account, Inception Rate - Daily Rate, Proportional Treaty, 10 Written Premium

Technical Account, Inception Rate - Daily Rate, Proportional Treaty, 83 Loss Reserve
Technical Account, Inception Rate - Daily Rate, Proportional Treaty, 81 Premium Reserve

The above is both for Functional Currency 1 and Functional Currency 2.

Workaround:

Root Cause:

Extent of Impact:

Impact on Existing Data

Recovery Method for Existing Data Affected

Problem:

The SICS Search functionality was found to be vulnerable to Cross-Site Scripting (XSS) attacks.
When using the functionality, the provided search term will be interpreted as code. This is shown
in the Figure below, where the term <img src=x onerror=alert(1)> was used.
As this results in an attack which can only target the user executing it, it is not considered severe.
However, there are multiple methods of generating an XSS attack which will affect any user of
the Search functionality.

First, the Figure below shows the result of HTML code and JavaScript injected into multiple
order titles.

Secondly, the Figure below shows HTML code being interpreted after being injected into a business
title. Such a payload can be created both through SICS and the UW Portal.

Do note that the injected code will only be executed if the search function does not highlight
it. As such, if the payload is within the title and the search function highlights the title, the payload
will not execute. This behavior is shown in the Figure below, where previously successful
payloads do not function.

Solution:

Prevent Cross site scripting (XSS) by using HTML encoding on all output variables in the Freemarker template that produce the output HTML page in SICS Search.

Declination Reason:

Workaround:

Root Cause:

Extent of Impact:

Impact on Existing Data

Recovery Method for Existing Data Affected

Problem:

The system abends when renewing an Unplaced Share business by Web Service.

Solution:

When an Outward Cedent’s Contracts has more than one extra insured period, as compared to its placements, (because it has been renewed multiple times before renewing belonging  placements), then when renewing its Unplaced Share business by Web Service, the system should not abend.  It should instead renew it as normal.

Workaround:

Renew the Unplaced Share business manually by opening its Life Cycle tab and selecting Renewal from the menu button. 

Root Cause:

Extent of Impact:

Impact on Existing Data

Recovery Method for Existing Data Affected

Problem:

Log function Write a walkback trace does not work.

Solution:

The error is arising because of the incompatible type of the  'main class of business'. Might be resolved by changing the main class of business from casualty to something compatible with the classification type.

Problem:
Not possible to give Former ID and Business Title at Intermediary Placement, Placement via Broker or Unplaced Share of outward cedent's contract by web service.

Solution:
When creating Intermediary Placement, Placement via Broker or Unplaced Share via Web service, all information including Business Title (<title>) and Former Id (<formerIdentifier>) which is submitted in CreatePlacementForOccRequest soap request, should completely and correctly update on those businesses (respectively Intermediary Placement, Placement via Broker or Unplaced Share). Just like the system does when creating same businesses via SICS online and Business Title and Former Id can be entered on last page ('Business Identifier & Accounting Info') of the wizard

Workaround:
Update Former ID and Business Title at Intermediary Placement, Placement via Broker or Unplaced Share via SICS online system

Root Cause:
Code error

Extent of Impact:

Impact on Existing Data

Recovery Method for Existing Data Affected

Aim of function:

We have the Entry code Transformation Term selected on ORP (Admin condition->Currency) then the EC defined on assumed business should be transformed to EC on ORP(for both As booking and As Account)

When a user create Proportional Facultative business and directly places to ORP than as per the terms defined under the admin conditions<Currencies Tab <EC transformation, booking made with entry code in assumed business will be transformed to another entry code for ORP. This enhancement is done to transform the booking when ORP is directly placed to Proportional facultative business.

System Parameters affected:

None

Existing functionality
Entry Code Transformation when booking takes place on Assumed Business protected by Fac ORP

Aim of function

To give users an option to split the balances of a Technical or Claim Worksheet on the basis of Special Functional Currency 1 Exchange rules, to ensure that all details within the same balance follow the same exchange rule when calculating the Functional Currency 1 amounts. This split of balances is additional to the other balance split options that take place on a worksheet. Entry codes that are part of any special Functional Currency 1 Exchange rule will be part of their respective separate balances whereas Entry Codes with no Special Functional Currency 1 Exchange Rules will remain in the normal balance. 

System Parameters Affected

A new system parameter named “Split Entry Codes with special FC1 Calculation Rule in Separate Balance” can be found under Accounting-> Currency-> General, below the parameter “Include Realized Gain/Loss In FC Revaluation” . The new parameter gets enabled when “Include Realized Gain/Loss In FC Revaluation” is CHECKED.

Existing functionality affected

• Manual creation of Technical and Claim Worksheet.
• Reverse worksheet for Technical and Claim Worksheet
• Reverse and Replace for Technical and Claim Worksheet.
• Copy for Technical and Claim Worksheet.
• Import Technical Worksheet through Spreadsheet.
• Installment Order & Adjustment Order.
• Automatic booking of Installments and Adjustments.

Aim of function

For all types of Business, when the user adds the first Booking row to the Worksheet, when the Due Date is defaulted on a technical worksheet and it is earlier than the Booking Date, then the system shall set the Due Date equal the Booking Date. When the Due Date is defaulted on a technical worksheet and it is equal or higher than the Booking Date, then the system shall keep the defaulted Due Date. This should also be the case for details created by the functions Copy, Reverse and Reverse and Replace.

System Parameters Affected

A new system parameter named Do not default Due Date before Booking Date, is found under Accounting, Worksheet page 

Existing functionality affected

The system shall compare the defaulted Due Date with the Booking Date, and set it equal the Booking Date if it is less than/before the Booking Date. This should be the case for all types of businesses independent of how the booking details are created on the worksheet, manually, reversal, automatic instalment bookings etc. If the user change the Due Date manually after it has been defaulted, then it will not be changed even if the Booking Date is changed. New details created manually on the worksheet will get the Due Date from the previous detail.
Excluded from this would be booking created by Retrocession Calculation and Account orders, and all booking of Estimates, manually or through orders.
 

Aim of function

Add New Calculation Variable in Underwriters Estimates/Multi Gaap Calculation rules. 

It will allow to setup calculation rules based on the Installment booked and not booked, If the ‘Total Amount Not Booked’ is Zero system follows the old approach and other than zero follows the new approach.  

System Parameters Affected

Added new calculation variable i.e. 'Total Amount Not Booked' with Two sub variable 'Gross' & 'Net'.

Aim of Function

The Aim of this function is to trigger a additional confirmation message on the closing screen, while the status  is changed to closed, on both Technical and Claim worksheet, each time bookings are made in different currency than the main currency defined on the business.

System Parameters Affected

A new system parameter named 'Confirmation Message While Closing Worksheet When Currency is not Main', is found under Accounting, Miscellaneous page

Existing functionality affected

Worksheet Closing Window - when status is set to Closed

Aim of Function
When booking on an Assumed Business, either manually or automatically from Premium & Limit conditions, e.g. Instalment, and Deduction details are calculated from the Deduction Conditions, then the system will check the 'Paid To' field for all deductions to be calculated. If there is no partner assigned in the 'Paid To' field no special action to be taken, i.e. existing functionality will apply. If there IS a partner assigned in the 'Paid To' field for the actual deduction to be calculated, then the system shall add this detail in a new balance or add it to an existing balance where the same partner is the Business Partner.

System Parameters Affected
A new system parameter named Activate the 'Paid To' column in deduction condition under System parameter maintenance>>Accounting>>Miscellaneous.

 
Existing functionality affected
Manually booking with automatic deduction calculation.
Automatic booking.
Installment/Adjustment order.

Aim of Function

Added a new system parameter named Period Number According to Calendar Time under the system parameter: MultiGAAP/General/Estimation Frequency/Depend On Each Business. When the new system parameter is selected:

1. The period numbers in Administration Condition follow calendar time.
2. The period number in Period Estimates is the same as the period number in Administration Condition.
3. AccYr and AccPeriod in Technical worksheet and Estimate worksheet are the information configured in Administration Condition.

System Parameters Affected

MultiGAAP/General/Estimation Basis/Accounting Year 

MultiGAAP/General/Estimation Frequency/Depend On Each Business

Existing functionality affected

Business/Administration Condition

Business/Underwriters Estimate/Period Estimates

Technical Worksheet

MultiGAAP Accounting Order

Retrocession Estimation Calculation Order

MultiGAAP Retrocession Order

Aim of Function

When a contract is fully placed, you flag the contract as placement complete. The Placement Completed flag can only be set when the sum of signed shares for all the definite retrocessionaires is 100%.  The system allows here for a deviation of +/-0,0000000049. 

Also, when setting this flag, the system checks that the total of retrocessionaires' signed shares placed through each intermediary with a definite status is equal to the intermediary's signed share.  Earlier, this check did not allow for any deviation between the intermediary's share and total share of retrocessionaires accepted through this intermediary. Now, SICS will also accept the same deviation of +/- 0,0000000049 for retrocessionaires placed through an intermediary, as it did earlier only for the total check. 

System Parameters Affected
Allow Proportional OCC Placement above 100%

Existing Functionality Affected

Maintain Share Conditions
Edit Placement Completed
Check for Placement Completed
Place intermediary

Aim of function
To reduce clutter in the user experience of the system, the security facility hides the condition buttons if they have no content (empty) and the user do not have an Update or Create right for these conditions. This has now been implemented also for conditions consisting of sub parts, like deduction conditions and premium and limit conditions.

System parameters affected
None

Existing functionality affected
Maintain Premium and Limit Main Conditions
Maintain Deduction Conditions
Manage Security
Maintain Section Overview
Maintain Cedent's Program Contract Overview

Aim of function

Reporting units reflect how the business is divided internally according to a reporting structure. The Reporting Units are identified by a unique name and a code.

SICS now offers the possibility to set up the system so that the Reporting Unit Code also must have a unique value.  

 System Parameters Affected

Reporting Unit Code must be unique

Existing Functionality Affected: 

Maintain Reporting Unit

Aim of function

Enable process/validate the eMessages per message type​.  Previously, the system did not have the feature to process/ validate the selected message types through the scheduler. With the new enhancement, we have introduced the Message Type field in the job step parameter, by selecting the options from the Message Type field, the user can perform the process/validation of the existing messages accordingly.​

System parameters affected

NA

Existing functionality affected

New field Message Type added to the Job step parameters: eMessage import and process and eMessage import and validate

Aim of function

Contract with sections for the receiver are often handled with multiple contracts by the sender or broker. The system now shows a list of all eMessaging Reference types that have category Unique Market Reference from all the sections of a contract. This list is shown on the Insured Period tab. 

System Parameters Affected

In the default settings of the eMessaging system parameter, introduced a new table Unique Market Reference.

Existing functionality affected

Maintain Sections
Update Business
Show Unique Market Reference Information

Aim of function

When processing an Accord Claims (CM) eMessage, any extension to the claim attributes, the claims fields were populated manually. However, with this new enhancement, the system will allow the sender to include extensions, which have no restrictions in terms of formatting and content, and it will allow the sender to define which extensions are to be used and considered for 'claim creation' in the wizard and when creating the claim automatically. Basically, when there are mappings from message fields to Claim attributes, which contain valid values (internal or external codes) the claims attributes are automatically populated.

System Parameters Affected

Added a new field under the Mapping  'eMessage extension' and mapped eMessaging Message Field to SICS Attribute.

Existing functionality affected

N/A.

Aim of function

Generate new P&C and Life API Server .NET Core Clients using the Windows Communication Foundation (WCF) dotnet-svcutil tool.

Deliver the new clients as NuGet packages.

https://learn.microsoft.com/en-us/dotnet/core/additional-tools/dotnet-svcutil-guide?tabs=dotnetsvcutil2x

https://www.nuget.org

System Parameters Affected

None

Existing functionality affected

None

Aim of function

The aim of this epic is 

• Improve the UI alignments of various Business Consitions of SICS P&C Workstation.
• Make sure screens are properly visible in different screen display resolutions.

System Parameters Affected

N/A

Existing functionality affected

N/A

Aim of function

The aim of this epic is 

• Improve the UI alignments of Claims related functions of SICS P&C Workstation.
• Make sure screens are properly visible in different screen display resolutions.

System Parameters Affected

N/A

Existing functionality affected

N/A

Aim of function
Automatically refresh SICS Servers if there are changes to system parameters, security, etc.
When a change is made to system parameters, etc and an automatic refresh is requested, the server components will automatically refresh before processing a new request or job.

System Parameters Affected

None

Existing functionality affected

SICS SOAP Server

SICS Batch Server

SICS REST Server

SICS eMessaging Server

SICS ADH Server

Aim of function

Support for Apple Mac OS is still preliminary and not production ready, however as part of our continued work on in this area we have added native support for Apple Silicon with the inclusion of the appropriate SWT libraries. It requires a native Apple Silicon Java Runtime in order to work.

System Parameters Affected

None

Existing functionality affected

None

Aim of function
Find windows in 22.2 and lower would use an open cursor to support the 'More' button. This added load to the database server by having an open SQL statement waiting to provide more records that may never be asked for.
We have replaced the open cursor with new paged SQL statements that are opened when Find Now is pressed and closed immediately the first page of records is returned. Pressing More issues a new SQL statement asking for the next page of results.
This reduces the load on the server.

System Parameters Affected
None

Existing functionality affected
UIs with a More button!

Aim of function
Oracle 12c extended support ended in July 2022. We have now removed support for Oracle 12c from our supported platform list.
As of September 2022, the only long term release version of Oracle is 19c with an extended support EOL date of April 2027.

Microsoft SQL Server 2012 extended support ended in July 2022. We have now removed support for Microsoft SQL Server 2012 from our supported platform list.

System Parameters Affected
None

Existing functionality affected
None

--------------------------------------------------

References to Vendor EOL support terms:

• https://docs.microsoft.com/en-us/lifecycle/products/microsoft-sql-server-2012
• https://www.oracle.com/us/support/library/lsp-tech-chart-069290.pdf

Aim of function

The aim of this epic is 

• Improved the UX of the Life Cession tool bars.
• Added support to hi resolution displays to show a larger splash screens.
• Fix the UI/UX for Underwriting Estimates window.

System Parameters Affected

N/A

Existing functionality affected

N/A

Aim of function
Support PostgreSQL 11+ in the SICS application.

Included:

• System Admin and SICS Desktop app
• Creating the database
• Running DB patches in future releases
• All SICS server components

Not Included:

• SAP BI Support
• Create BOAC scripts & related functions
• Any DB conversion tools from other DBMS platforms. There are many 3rd party options available.

SAP BI will be supported in a future release.

System parameters affected
None.

Existing functionality affected
All DBMS configuration related functions

Aim of function

Need to create Views (In SQL and ORACLE) to resolve few object level and join level issues in the unified universes like CEDE, Life, GL_Interface & PC Main  .

Creating views to resolve date calculation, date format and measure calculations.

System Parameters Affected

These changes will not effect any existing system parameters.

Existing functionality affected

As we are creating new views , it won't disturb the existing functionality.

Aim of function

To have one universe to develop and maintain and this ONE universe can then connect to the different supported database platforms.

System Parameters Affected

NA

Existing functionality affected

There will be a new universe which is the unified universe, in this universe there will be no RTRIM() functions and dates will be extracted as datetime stamp without any conversions as they have today. There will also be a new exchange rate function which is similar for all database platforms.

Aim of Function
The SQL Log Analyzer has been improved with the following:

• An information tab with basic details about the log
• A report of duplicate SQL in a separate tab with a count of the number of instances. These are completely identical SQL statements issued within the SQL log being analyzed
• A tab with a list of the number & type of statements issued each minute
• A tab with a chart of the number & type of statements issued each minute

Existing Functions Affected
The SQL Log Analyzer available on the System Information > Logging tab.

System Parameters Affected
None

Aim of function

1. Ultimate Loss Ratio Import and UW Estimates Supporting Figures Import, previously found in the Inbound Interfaces folder in the System Administration Utility, has been moved to the Periodic Functions folder on the SICS Desktop

2. Typical Mass Update functions, previously found in the Periodic Functions folder, has been moved to a new Mass Update Functions folder on the SICS Desktop

3. Separate the Mass Update functions from the Periodic Functions by creating a new Mass Update folder and moving all mass update functions to that folder

System Parameters Affected

None

Existing functionality affected
Ultimate Loss Ratio Import (P&C only)
UW Estimates Supporting Figures Import
Periodic Functions and Mass Updates

Aim of function

To add database views, procedures, and functions so that the BO functionalities will be supported for Postgresql database as they are supported for Oracle and SQL Server database

System Parameters Affected

None

Existing functionality affected

None