Problem:
SICS - Issue on hard stop for booking of premium deposit

Solution:
When the user press Apply or Change Status on a Technical worksheet that contains Premium Deposit Retained, the system process the Accuracy Validation Rules for Premium Deposit Retained. To validate that the given Premium Deposit Retained is correct or not the system sums up the basis for this calculation.

If the basis is Premium and the conditions says deposit regulation Quarters and release in Next Account, then we must make sure the system only use the Premium booked on the current worksheet and use this as basis for the deposit retained, both when the user makes automatic booking of deposit retained and when the system performs the accuracy validation.

If the basis is Premium and the conditions says deposit regulation Quarters and release in Same Account in Next Accounting Year, then we must make sure the system only use the Premium booked on the current worksheet and use this as basis for the deposit retained, both when the user makes automatic booking of deposit retained and when the system performs the accuracy validation.

If the basis is Original Premium Reserve and the conditions says deposit regulation Years and released in Same Account in Next Accounting Year, then we must make sure the system sums up all Original Premium Reserves booked within the actual Accounting Year for all Accounting Periods since last Release, and use this as basis for the deposit retained, both when the user makes automatic booking of deposit retained and when the system performs the accuracy validation.

Workaround:

Root Cause:

Extent of Impact:

Impact on Existing Data

Recovery Method for Existing Data Affected

Problem:
Stop loss recovery not produced as expected when having two Stop loss for one Insured Period (with different classifications). This happens both when the OCCs are in one Protection Program and in two separate programs.

Solution:
When there are more than one Stop loss for an Insured Period, the Recovery Calculation for Stop loss must consider this correctly.

Workaround:
None

Root Cause:

Extent of Impact:

Impact on Existing Data

Recovery Method for Existing Data Affected

Problem:
Mass pairing does not work when matching is based on London Reference (lmm ref)

Solution:
1. First of all we need to change the logic for including the remittances in the query. If the Match On Unique Reference is selected and also the London Reference is selected on the order, then the system shall include all remittances where either the Partner's Reference exists on the remittance AND/OR the London Market Reference exists on the remittance.

2a. When running the Mass Pairing order with the London Reference ticked under Match On Unique Reference, and the London Market Reference is present on the remittance, then the system should use this field on the balances, both on the technical and the remittance balance, to find match and to perform the balance pairing if match is found. In the database this field is known as LMM_REF. 

2b. When running the Mass Pairing order with the London Reference NOT ticked under Match On Unique Reference, or the London Market Reference is blank on the remittance, then the system should use the Partner's Reference field on the remittance balances, to find match with technical balances on any of the nine reference fields selected on the order except for London Reference and to perform the balance pairing if match is found. 

This works currently fine for Partner's Reference and should also work for London Market Reference.

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:
Not possible to include Remittances in balance pairing when “When Pairing, always Use Remittances as the Driving Balances” is ON

Solution:
1) Make a new system parameter on the Accounting, Balance Pairing page below the existing parameter 'When Pairing, always use Remittances as the driving Balance' and becomes enabled when that parameter is selected. The new parameter should be named e.g. 'Allow all types of balances included”. It should be disabled if the above existing parameter is not selected.
2) When the new parameter 'Allow all types of balances included” is selected and the user is manually doing a balance pairing, and the pairing contains both technical/claim balances AND ordinary remittance balances then the system will accept this.
But if the new system parameter is NOT selected, then AC0823 will appear according to existing functionality, i.e. when both the parameters 'When Pairing, always use Remittances as the driving Balance' and 'Balance Pairing Group in use' are selected.

Workaround:

Root Cause:

Extent of Impact:

Impact on Existing Data

Recovery Method for Existing Data Affected

Problem:
PRB100005315 Update of Bank account fails due to DB error in Production

Solution:
When an existing business partner's or base company's bank account is edited, whatever information the user updates on this bank account, we must make sure the system is able to store these changes without abending. This must be independent of the Status of the Bank Account and independent of the information that is changed.

Workaround:

Root Cause:

Extent of Impact:

Impact on Existing Data

Recovery Method for Existing Data Affected

Problem:
SICS_Hard Stop error_Discrepancy Amt base currrency CHF

Solution:
When the user opens the Accuracy Validation Log message window the system must calculate the value in the column Discrepancy Amount in Base Currency XXX (where XXX is the base currency) by deducting the Booked Amount value from the Computed Amount value, both in booking currency, and convert this difference into the base currency shown in the header of this column (same as the base currency in the accuracy validation rule).

Workaround:

Root Cause:

Extent of Impact:

Impact on Existing Data

Recovery Method for Existing Data Affected

Problem:
AC0425 message misleading when filter criteria is applied - gives wrong number of balances found

Solution:
When the user press Find Now on the Account Balances tab on the Business Ledger, the system presents the message AC0425, telling you how many balances found and will be listed. The system shall display the correct number of balances independent which filter criteria selected on the Balance Criteria window.

Workaround:

Root Cause:

Extent of Impact:

Impact on Existing Data

Recovery Method for Existing Data Affected

Problem:
Import TW via xls option ignores Accounting period value 'None' or 'Yearly' provided in the input file when accounts have been generated on the contract

Solution:
When a Technical Worksheet is created by the function Import Technical Worksheet from Spreadsheet and the AccPeriod column in the spreadsheet contains of the value Yearly or <None>, the system must set these values on the worksheet as given in the spreadsheet, independent of system parameter settings. These two values shall be valid both when the worksheet is created online and from spreadsheet, for ALL type of businesses.

Workaround:
Manually enter the correct AccPeriod on the worksheet

Root Cause:

Extent of Impact:

Impact on Existing Data

Recovery Method for Existing Data Affected

Problem:
When technical worksheet is uploaded from spreadsheet with many details linked to Headline Loss it is not user friendly that warning message AC0497 appear per detail.

Solution:
Make a new system parameter below the existing parameter Only Warning Message when Linked Headline Loss is outside IP on the Accounting, P&C Miscellaneous page. The new parameter can be named Do not validate if Linked Headline Loss is outside IP. The new parameter shall only be enabled if Only Warning Message when Linked Headline Loss is outside IP parameter is select.
If the new Do not validate if Linked Headline Loss is outside IP parameter is selected, the system will not present any warning messages regarding linked Headline Losses at all when the worksheet is validated.

Workaround:
By setting the Claim Basis and the Loss Portfolio conditions on the business this will also prevent the warning message

Root Cause:

Extent of Impact:

Impact on Existing Data

Recovery Method for Existing Data Affected

Problem:
GOV TAX - Change of Accounting Period is not validated

Solution:

When a technical or claim worksheet is created and applied and the system sets a Government Tax error message on the Trigger detail and/or the Target detail, the system must remove this Government Tax Category/Comment from the actual details if the user change the Accounting Classification on the actual detail, in the same way as this information is removed if the Insured Period or Section on the actual detail is changed.
If both trigger and target details are booked with a linkage and a GT error is set because the target detail amount is wrong according to the rule, and the user change IP, Section, AC or Accounting Period To-date on the TRIGGER detail, then the system shall also remove the GT Category/Comment on the target detail (found through the linkage).
The system must also remove the Government Tax Category/Comment from the actual details if the Accounting Period To-date is changed and the triggered GT rule has the Tax % Calculation Basis set to Acct Period End Date.
The system must also remove the Government Tax Category/Comment from the actual details on the worksheet if the Booking Date is changed for the worksheet and where the triggered GT rule has the Tax % Calculation Basis set to Booking Date.

The Accounting Period To-date can also be changed by changing the AccYear/AccPeriod on the worksheet and therefore the GT Category and Comment shall also be changed in this scenario.

Workaround:

Root Cause:

Extent of Impact:

Impact on Existing Data

Recovery Method for Existing Data Affected

Problem:
Technical Worksheet System Abend after deleting Attachment

Solution:
When an attachment has been created on a Technical worksheet and this is deleted by the user followed by selecting Apply, the system must be able to handle this and just apply the worksheet to the database with the attachment deleted and not abend. This is working fine when the attachment is deleted from the worksheet closing window, so we need to solve this in the same way on the worksheet details window.

Workaround:
It is possible to navigate to the Worksheet Closing window and from there delete the attachment from the worksheet. If further update is necessary the user can also navigate back to the worksheet for these updates and then click Apply

Root Cause:

Extent of Impact:

Impact on Existing Data

Recovery Method for Existing Data Affected

Problem:

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

Solution:

When the user on the worksheet manually book both a government tax trigger AND target entry code with the amount of ZERO and then select the option Change Status or press the button Apply so that the validation of the government tax target detail takes place, then the system must present the error message AC0837 for the user and inform that the entered zero amount is wrong compared with the computed amount, and NOT replace the zero amount with the computed amount. This is correct if the target amount is different from zero (and different from the computed amount), but not if the target amount is zero.

It also works fine if the target detail of zero amount has already been validated and linked to the GT tax rule, then the system correctly use the zero amount in the validation and keeps the zero amount on the detail. The zero amount must be kept if the details are linked or not and both when the Automatic Booking is selected on the rule or not.

Workaround:

Root Cause:

Extent of Impact:

Impact on Existing Data

Recovery Method for Existing Data Affected

Problem:
AUTO SBG - After Loading and Refresh SICS, the Settlement amounts goes to Exchange Diff.

Solution:
When a new Settlement Balance Group is created by the function Automatic Search for SBG and the user selects the option Import Excel/Delimited Record File from the menu, the system must commit this balance group to the database so that it remains correct also after a refresh.

Workaround:

Root Cause:

Extent of Impact:

Impact on Existing Data

Recovery Method for Existing Data Affected

Problem:
Checkbox 'Auto booking on OCC/ORP' shown in Prop Treaty OCC now is invisible in screen.

Solution:

When opening the Business, Accounting Info tab on the business overview, either in view mode or in edit mode we must make sure the Automatic Booking on OCC ORP tick box is visible.

Workaround:

Root Cause:

Extent of Impact:

Impact on Existing Data

Recovery Method for Existing Data Affected

Problem:

Development Received Date defaults to Due Date in TW does not work when selecting Auto Calc of Deposits or Loss Participation Clause

Solution:

When the system parameter 'Set Due date from Received date on Technical Worksheet' is ON and the user selects the option Automatic Booking of Premium Deposit or Loss Participation, the system must set the Due Date equal the Due Date on the basis premium detail.
Also when the user from the worksheet selects the menu option Release Bookings (Cash Claims, Premium Due Later, Deposits, Non-Liquid Deposits), and this is the FIRST detail on the worksheet, then the system shall set the Due Date equal the Received Date.

Workaround:

Root Cause:

Extent of Impact:

Impact on Existing Data

Recovery Method for Existing Data Affected

Problem:

When a definite URB is replaced by a technical worksheet, a new pairing ID is not given.

Solution:

When an Unallocated Remittance Balance is replaced in the balance pairing by another balance, e.g. a technical balance, the system must set a NEW Pairing ID for this new pairing. This should be the case both when the URB is replaced manually by the option Replace Selected URB in Pairing from the business ledger or when the a worksheet is closed with a matching balance so that message AC0441 appears. In both these situation, the system must generate a new Pairing ID for the pairing with the new balance that replaces the URB in the pairing.

Workaround:

Root Cause:

Extent of Impact:

Impact on Existing Data

Recovery Method for Existing Data Affected

Problem:

When Retrocession Calculation Order is run on multiple Insured Periods, the Account As Of Date (in Administration Conditions) on the last Insured Period is used to populate Accounting Period To Date on details for all Insured Periods. Furthermore, the Accounting Period From Date is populated based on the Insured Period Start Date on the latest Insured Period. 

Solution:

Make sure Account As Of Date on each Insured Period is used to populate Accounting Period To Date on the same Insured Periods. In addition, the Accounting Period From Date should be populated based on the Insured Period Start Date on each Insured Period.

Workaround:

Root Cause:

Old implementation

Extent of Impact:

Impact on Existing Data

None

Recovery Method for Existing Data Affected

N/A

Problem:
Error createworksheet and createclaimworksheet SicsServer

Solution:
When executing either createWorksheet or createClaimWorksheet, with chained operation with closeWorksheet or not, and the soap contains the element
<accountingClassificationByReferenceData>, then the system will use the given AC element values to find existing AC on the business. If no matching AC is found on the business, but the element values are found on the Classification tab on the business, insured period, section, then we must make sure the system creates a NEW Accounting Classification with the given elements.

Workaround:
Create the necessary Accounting Classification in advanced on the business.
By selecting the system parameter 'Automatic Creation Of Accounting Classification' and 'Renew AC on Renewal' (found on the page Accounting Classification), the system will automatically generate all possible Accounting Classification on the business/IP

Root Cause:

Extent of Impact:

Impact on Existing Data

Recovery Method for Existing Data Affected

Problem:
SICS does not refer Orig Book Year/Orig Book Per to calculate FC amount when SICS Reverse/Reverse and Replace bookings.

Solution:
When the System Parameter, Accounting, Retrocession, General, 'Keep Booking Year/Period from Source Business' is selected, then the system shall not only set the Booking Year/Period from the source booking in the Orig Booking Year/Period, but also do the FC Calculation based on the Orig Booking Year/Period, also for the Replacement booking details on the worksheet.
The above should apply for the following processes:
Reverse Balance, Worksheet or Detail
Reverse and Replace Balance, Worksheet or Detail
Split balance into details
Balance split in the balance pairing process

The above functionality should NOT be affected by the system parameter Reverse with Re-Calculation

Workaround:

Root Cause:
SICSR-11541

Extent of Impact:

Impact on Existing Data

Recovery Method for Existing Data Affected

Problem:
FC amount becomes zero when I do the 'Reverse and Replace Worksheet' twice. It maybe part of SICSR-23640.

Solution:

When the function Reverse and Replace is executed on a worksheet that is created by Reverse and Replace, we must make sure ALL details are correctly set with Functional Currency amount.

Workaround:

Root Cause:

Extent of Impact:

Impact on Existing Data

Recovery Method for Existing Data Affected

Problem:
Retrocession Account Order sometimes does not create bookings

Occurs when Accounting Year on the As Booking balances are higher than the Accounting Year on the Order. This is again caused by incorrect setting of Accounting year by the Retrocession Calculation Order, in situations where the UWY is higher than the Insured Period Start Year. 

Solution:

Make sure the Retrocession Calculation Order sets the Accounting Year on the bookings equal to the Accounting Year on the Order

Workaround:

Root Cause:

SE-1734

Extent of Impact:

Impact on Existing Data

Recovery Method for Existing Data Affected

Problem:

Booking Terms for Base Company not used on worksheet

Solution:

When creating the first booking detail row on a worksheet, both Technical and Claim, the system must read the Booking Terms for the Base Company on the business/insured period. From here the system shall pick the Default Booking Year/Period. The drop down shall contain all open Booking Year/Periods for these Booking Terms.

If no special Booking Terms are defined for the actual Base Company, then the <Default Settings> shall be used.

Workaround:

Root Cause:

Extent of Impact:

Impact on Existing Data

Recovery Method for Existing Data Affected

Problem:
Failed to find preliminary bookings in 'worksheet exclusion' of retrocession calculation order. 

Caused by the fact that possible UWY extract in the window is taken from bookings on protected assumed businesses, but the query in the window selects UWY from the Preliminary bookings on the OCC. 

Solution:

When you press Find Now in the Worksheet Exclusion window, the system should look for Preliminary bookings which has a source inward booking with an UWY selected in the Worksheet Exclusion window. 

Workaround:

Root Cause:

Original implementation of SE-276

Extent of Impact:

Impact on Existing Data

Recovery Method for Existing Data Affected

Problem:
GOV TAX - TA/CL - SICS 22.1 - TECSNT02: Override Comment on Trigger EC removed by validation

Solution:
When you have booked a government tax trigger entry code on a worksheet without a relevant target entry code, and you have given a government tax category and comment, make sure this category and comment is kept both when the user select the Change Status on the worksheet. It is correctly kept if no further GT error messages appears, but not if new error messages appears.
The government tax category and comment must also be kept when the user opens the Government Tax Validation Error details window and then select Cancel to close that window.

Workaround:

Root Cause:

Extent of Impact:

Impact on Existing Data

Recovery Method for Existing Data Affected

Problem:
Wrong As Original Amount is booked when I edit the retroceded %.

Solution:

In the proportional protection (PP) on an IAB, if the user first remove an OCC and later add the same OCC, the system will in both of these operations make a retroactive correction booking on this OCC. First it will reverse the as Original bookings already made on the OCC coming from the IAB, then the system will rebook to this OCC according to the new retroceded share given to this OCC. In the latter operation the system must take into consideration both the original bookings that came from the IAB AND the reversal bookings that took place when this OCC was removed from the protection assignment.

Workaround:

Only change the retroceded share in one operation, i.e. do not first remove the OCC and then add the same OCC again.

Root Cause:

Extent of Impact:

Impact on Existing Data

Recovery Method for Existing Data Affected

Problem:
As Account Deposit Release Functional Currency Amount is incorrect when system parameter 'FC Deposit Released equal FC Deposit Retained' is selected. 

Solution:

Make sure that when system parameter 'FC Deposit Released equal FC Deposit Retained' is selected, the Functional Currency amount of the Deposit Released amount in Account Currency is set equal to the Functional Currency amount of the corresponding Deposit Retained amount. 

Workaround:

None

Root Cause:

SICSR-17659

Extent of Impact:

Impact on Existing Data

Recovery Method for Existing Data Affected

Problem:
Validation error in Accounting Classification

Solution:
When a non-prop treaty OCC is renewed and the global system parameter 'Renew AC on Renewal ' is selected, the system must copy ALL ACs from the source IP to the new IP, including the AC Split % assigned. This means that it must include both Reporting Unit and Type of Participation (Method) and have all the ACs with the various RU and ToP copied over. It must be similar for a non-prop treaty OCC as it is for a prop treaty OCC or an AB where the ACs are copied over correctly.

Workaround:

Root Cause:

Extent of Impact:

Impact on Existing Data

Recovery Method for Existing Data Affected

Problem:
After auto amend system gives Error message regarding booked premium Instalments asking to reverse on OCC

Solution:
When the user wants to edit the Share conditions on an assumed business with amendments defined and on this business there are booked instalments, then the system shall not present validation error message BR0165, but instead allow the user to edit the share conditions.

Workaround:

Root Cause:
SICSR-18026 in 21.4 - a correction that should only affect non-prop treaty OCC/ORP and not AB

Extent of Impact:

Impact on Existing Data

Recovery Method for Existing Data Affected

Problem:

The system does not allow update business Insured Period To date when business has unsettled bookings/estimates 

Solution:

When the system parameter 'Change of IP/UW Year not allowed if Unsettled Booking exists' is selected and the user change the Insured Period From date or the Underwriting Year AND if the Business has actual bookings or estimates that do not sums up to zero for this insured period the system correctly gives an error message (BS0436) saying 'Change of IP/UW Year not allowed because actual bookings or estimates exist and does not sum up to zero. These must be reversed before the change can be made' so that the changes cannot be saved.
The same validation takes place also when the user change the Insured Period To date. This is not correct and we must make sure the system allows modification of the IP To date even with the above system parameter selected and bookings exist.

Workaround:

Root Cause:

Extent of Impact:

Impact on Existing Data

None

Recovery Method for Existing Data Affected

N/A

Problem:
CededCeded - 2 booking periods open - Wrong booking period for the As Original booking

Solution:
When protection assignment is changed on an Assumed Business by either adding a new prop treaty OCC or changing the Share of an existing OCC, so that existing bookings on the Assumed Business result is retroactive correction bookings on the As Original ledger on the OCC, the system must keep the Booking Year and Period on these correction booking on the OCC, even if these periods are currently closed for the actual Base Company's Booking Terms. ONLY if the system parameter Override Booking Period on As Original Correction Bookings is ON, then the system shall overrule and change the Booking Year and Period to the first Open period.

Workaround:

Root Cause:
SICSR-20192 implemented in 21.2

Extent of Impact:

Impact on Existing Data

Recovery Method for Existing Data Affected

Problem:

When copying an Unearned Premium Reserve Order, not all selections on the source Order are copied to the new Order. 

Selections for 'Use Insured Period as Earning Period' and 'Calculate Reserves with 1/8 method' are not copied to the new Order

Solution:

When copying an Unearned Premium Reserve Order, make sure all selections on the source Order are copied to the new Order

Declination Reason:

Workaround:

Root Cause:

Extent of Impact:

Impact on Existing Data

Recovery Method for Existing Data Affected

Problem:
I am running Recovery Calculation for Protection Program where an OCC has child section with calculated figures, and none at Main section.
Two issues:

• When deselecting Accumulated at Protection Program List, instead of figures at main section - it shows an error code: com.csc.sics.framework.lang.attributes.PropertyAccessException
• When selecting Close WS at Protection Program list - the system abends with the following message: Exception occured: Cannot invoke 'java.util.List.isEmpty() ...

Solution:
Even though there are no figures at Main section, the display must be correct both in Accumulated and non-accumulated View at Recovery order, and it must be possible to close Worksheets and get bookings at child section level of the OCC.

Workaround:

Root Cause:

Extent of Impact:

Impact on Existing Data

Recovery Method for Existing Data Affected

Problem:
unexpected Abend on TA message due to government tax validation

Solution:
When a Tech Account message is opened and the Swap to Worksheet takes place, the system must also handle a null value in the Accounting Period To date and not perform the Government Tax calculation.

Workaround:

Root Cause:
SICSR-23385 done in 22.2 and in 22.1_SSP1

Extent of Impact:

Impact on Existing Data

Recovery Method for Existing Data Affected

Problem:
Incorrect calculation for Loss Deposit Retained ACC Validation calculation

Solution:
When the system validates the Premium and Loss Deposit Retained on a worksheet, we must make sure the system aggregates also the previous booked retained deposits within the same aggregation level. The computed value in message AC0770 must reflect this aggregated value of the basis multiplied with the deposit Percentage less the already retained deposit.

Workaround:

Root Cause:

Extent of Impact:

Impact on Existing Data

Recovery Method for Existing Data Affected

Problem:
GOV TAX - Change of Accounting Period is not validated

Solution:
1. When a technical or claim worksheet is created and applied the system performs the Government Tax validation based on a matching GT Rule. To find the matching GT Rule the system also checks the Tax % Applicable valid From and To date of the rule. If the Tax % Calculation Basis is Acct Period End Date, it means that the system checks the Accounting Period To date on the actual details. Among the other matching criteria the Accounting Period To date must be within the Tax % Applicable valid From and To date in the rule.
So if the system has set a Government Tax error message, e.g. AC0837, on the Target detail based on a Government Tax rule according to above, and the user again applies the worksheet, then the system must perform the Government Tax validation again for the actual details in case the user has changed the Accounting Period To date on the actual detail.
2. If the Tax % Calculation Basis is Booking Date, and the user has changed the Booking Date on the worksheet, then the system must also perform the Government Tax Validation again for this worksheet when the user applies to be sure the correct rule is used.
The system correctly performs a new validation when the link between the trigger and the target detail have been removed, so the solution should be to remove this link between the trigger and target detail when the user change the Accounting Period To date on a detail where the actual rule is based on Acct Period End Date or when the user change the Booking Date and any of the actual rules used on the worksheet is based on the Booking Date.
This correctly takes place, both when the Tax % Calculation Basis is Booking Date or Acct Period End Date, if only a Trigger detail is booked on the worksheet and error message AC0834 appears. If the user now change the Accounting Period To date for this detail or the Booking Date and applies the worksheet then the system again validates this detail and uses the correct rule matching the valid date in the rule.

Workaround:

Root Cause:

Extent of Impact:

Impact on Existing Data

Recovery Method for Existing Data Affected

Problem:
Incorrect Premium Deposit Validation for Scenario 1

Solution:
When the Calculation Method on the Premium Deposit is  Pct Of Premium Reserve and on the Loss Deposit is Pct Of Loss Reserve, then the system must aggregate all reserves, both on current worksheet and from the ledger, within the current Accounting Year. The sum of the Reserve (Reserve Balance for the current Accounting Year) is multiplied with the Percentage on the deposit conditions.

Workaround:

Root Cause:

Extent of Impact:

Impact on Existing Data

Recovery Method for Existing Data Affected

Problem:
SICS abend when create new Business Partner.

Solution:

Ensure that Party Wizard Type (01234) have at least one child (“Properties”) from Reference Data 01233 (Party Wizard Page)

Workaround:
In the reference data Type 'Party Wizard Type', for value New Business Partner, select Child Wizard Page 'Properties'.
Do the same for Bank, Third Party and Person.

Root Cause:

Extent of Impact:

Impact on Existing Data

Recovery Method for Existing Data Affected

Problem:

When renewing a single treaty protection, and the Type of Participation method was changed on the protected assumed business new insured period, the type of participation method of the single treaty protection's new period is also changed or is missing. 

Solution:

When renewing a Single Treaty Protection, the Type of Participation Method should be copied from the Type of Participation Method of the Single Treaty Protection's own previous insured period. 

Workaround:

Root Cause:

Extent of Impact:

Impact on Existing Data

Recovery Method for Existing Data Affected

Problem:
Abend when trying to update Bank account status.

Solution:
When an existing business partner's or base company's bank account is edited, whatever information the user updates on this bank account, we must make sure the system is able to store these changes without abending. This must be independent of the Status of the Bank Account and independent of the information that is changed and independent if it is referred to from the AC_LEDGER_BALANCE table (if it as been used on a Remittance balance) or not.

Workaround:

Root Cause:

Extent of Impact:

Impact on Existing Data

Recovery Method for Existing Data Affected

Problem:

Saved Provisional Commission for Sliding Scale Commission is removed on cancellation.

Solution:

When 'Sliding Scale Commission' or 'Stepped Sliding Scale Commission' is opened in Edit mode and then the operation is cancelled, all original values, including Provisional Commission percent, should be kept in View screen (and in the database) of 'Sliding Scale Commission' or 'Stepped Sliding Scale Commission'.

Workaround:
Manually re-enter missing Provisional Commission percent.

Root Cause:
SC-3487

Extent of Impact:

Impact on Existing Data

Recovery Method for Existing Data Affected

Problem: 
The system stops calculating deposits after the 99th retention.

Solution:
Increase the Last Regulation column in the database so that SICS allows up to 3 digits (maximum 999) in the field Last Regulation, both in the Premium Deposit and in the Loss Deposit window.

Workaround:

Root Cause:

Extent of Impact:

Impact on Existing Data

Recovery Method for Existing Data Affected

Problem:
The system abends after deletion of the non-proportional protection assignment or the proportional protection assignment on a Sub-Section.

Solution:
When deleting the Non-Proportional Protection Assignment or Proportional Protection Assignment on a Sub Section or on Main Section, the system should not abend. Instead, the protection should be removed on the desired section.
In case the process is started from the Main Section, the inheritance from Main Section to any sub section should be deleted as well, if the user decides so.

Workaround:

Root Cause:
SE-7907

Extent of Impact:

Impact on Existing Data

Recovery Method for Existing Data Affected

Problem:
The Approved status is not available for the creator of a Bank Account which was previously updated by a different user.

Solution:
When the Bank Account properties for a business partner is opened in view mode and the user clicks the Edit button next to the Account Status, where the status is currently Provisional, make sure the value Approved is enabled and can be selected by this user. The value Approve should be enabled also if the bank account was Created by this user.

There is only one exception to this; if the user is the same as the user that last Updated this bank account, then the value Approved should be hidden.

Workaround:

Root Cause:

Extent of Impact:

Impact on Existing Data

Recovery Method for Existing Data Affected

Problem:    
View available tags in document production abends.

Solution:

SICS must not abend when selecting pop-up option 'View Available Tags' for any given Document Type under Document Production Template Maintenance facility. The system should open the expected window just fine.

Workaround:

Root Cause:

Extent of Impact:

Impact on Existing Data

Recovery Method for Existing Data Affected

Problem:
If there are many claims (above 100) in Claim list; performance is bad.
If there are more than 100 claims for an Insured Period 'Retrieve Claim Totals' is automatically deselected and claim totals not shown in the container. When selecting it, the performance is extremely bad.

Solution:
Improvements to be done for:
1) read details in EC subcategory level
2) include only Loss/Loss reserve/aadPaid/aadReserve
3) read 'Other' details when asked - not up front

View all Claims (all Insured Periods) must also be considered in this respect.
Implement for assumed business, Outward Cedent's Contract and Policy Ceded

Workaround:
None

Root Cause:

Extent of Impact:

Impact on Existing Data

Recovery Method for Existing Data Affected

Problem:

createClaim API fails if ClaimClassificationList elements is included.

Solution:

Claim should be created with the Claim classifications included in API

++Workaround:

Root Cause:

Extent of Impact:

Impact on Existing Data

Recovery Method for Existing Data Affected

Problem:

Abend when selecting Automatic Reinstatement Booking from within a worksheet which does not have any details, or has an undefined entry code line.

Solution:

The system must validate that worksheet entry is 'complete' - at least one detail, and no undefined entry codes before attempting calculation of reinstatement.

Workaround:

Ensure the worksheet has at least one detail, and not undefined entry codes.

Root Cause:

Extent of Impact:

Impact on Existing Data

Recovery Method for Existing Data Affected

Problem:

The system abends when selecting Auotmatic Reinstatement booking in  the worksheet created by having selected Automatic Reinstatement Booking from claim list

Solution:

As the worksheet already contains all reinstatement bookings, there is no need to calculate and book again. The option should be disabled in the worksheet itself.

Workaround:

Do not select Automatic Reinstatement Calculation in the worksheet, as this worksheet already contains all necessary bookings.

Root Cause:

Extent of Impact:

Impact on Existing Data

Recovery Method for Existing Data Affected

Problem:

When viewing Find Claims in a resolution of 150% the business/claim options of query specifications is not displayed

Solution:

The system should display all options also when viewing in a resolution > 100%

Workaround:

View in 100% mode

Root Cause:

Extent of Impact:

Impact on Existing Data

Recovery Method for Existing Data Affected

Problem:

Find Claim view details - section information limits is incorrect. This should display the limit of that section.

Solution:

When claim is linked to more than one section of the same business, Find Claims should display each section limit when Business Identifier is the selected Query Sepcification, and View Details has been selected.

Workaround:

Root Cause:

SE-1884

Extent of Impact:

Impact on Existing Data

Recovery Method for Existing Data Affected

Problem:

Abend when deleting all bookings/entries in a worksheet

Solution:

When deleting a row in a claim worksheet, the system should remove all details for that row

Workaround

Inactivate worksheet

Root Cause

SE-5232

Extent of Impact:

Impact on Existing Data

Recovery Method for Existing Data Affected

Problem:

The Headline Loss Notice does not support all of the tags supported in the Large Loss Notice.

Solution:

Ensure that all tags supported by Large Loss Notice is supported in the Headline Loss Notice

Workaround:

Root Cause:

Extent of Impact:

Impact on Existing Data

Recovery Method for Existing Data Affected

Problem:

Signature Notes which are unlocked can still be viewed

Solution:

When Data Protection applies, the signature notes should be protected, whether they are locked or unlocked

Workaround:

Root Cause:

Extent of Impact:

Impact on Existing Data

Recovery Method for Existing Data Affected

Problem:

The system abends when user enters an Event Group name which exceeds the maximum of 50 characters

Solution:

Either prevent entry beyond 50 characters, or raise warning

Workaround:

Ensure that name does not exceed the maximum field length

Root Cause:

Extent of Impact:

Impact on Existing Data

Recovery Method for Existing Data Affected

Problem:

The system abends when deleting a claim reference due to log activity set up

Solution:

The system activity log must be able to handle the soc to claim rel and reference type and id being set from a value to NIL. 

Workaround:

In Log Activity, Claim References, disable triggering of types scopeOfCoverToClaimRelation and variousClaimDetailsRelation

Root Cause:

Extent of Impact:

Impact on Existing Data

Recovery Method for Existing Data Affected

Problem:

Error in updateClaim rule for cause of loss when the existing cause of loss is invalid for the insured period's main class of business, but no update of the cause of loss is expected.

Solution:

The updateClaim rule should only update and validate the Cause of Loss on the claim if it has not yet been defined. If a value has been defined, although invalid for the MainClass of Business, the system should neither update nor validate.

 Workaround:

Root Cause:

Extent of Impact:

Impact on Existing Data

Recovery Method for Existing Data Affected

Problem:

In the Claim Disposition History folder the Select statement is missing the *H .  Without this change the claim Disposition history doe not work as it only brings in the most recent disposition.*

Solution:

 The query for 'Claim disposition' needs to be updated.

Problem:
We are looking to use the RejectByMessageFunctionValidationRule , but when we try to add the message function to the rule in the partner ruleset, we get an abend.

Solution:
It should be possible to add a new configuration for the rule without problem.

Workaround:

Root Cause:

Extent of Impact:

Impact on Existing Data

Recovery Method for Existing Data Affected

Problem:
We have already assigned the DuplicateMessageMappingRule to the ruleset eMessaging document type: ACORD TechAccount - eMessaging Message Function: ADH, and created a simple duplicate message table (with just one test in it, for Sender Ref). However we fear there may be a problem here, because when we validated eMessaging UUId = 1400598d-2c16-45af-8d1c-78d0dde95e8c (which includes the new rule) we got an abend.

It is not possible to delete a Duplicate Message Mapping Set.

Solution:
There should be validation that a message type is assigned to a Mapping set.
It should be possible to delete a Duplicate Message mapping set.

Workaround:

Root Cause:

Extent of Impact:

Impact on Existing Data

Recovery Method for Existing Data Affected

Problem:

Error when we turned on the SICS 21.2.7 Conduit scheduler

Unexpeced error occured while tranferring messages from SICS to WebConnectivity processing aborted! com.csc.sics.emessaging.gateway.integration.SicsEMessagingIntegrationCriticalException: Failed getting message from SICS:

and

Unexpected error occurred while running class com.csc.sics.emessaging.gateway.integration.SicsEMessagingGatewayRouter : com.csc.sics.emessaging.gateway.integration.SicsEMessagingIntegrationFatallException: Unexpeced error occured while tranferring messages from SICS to WebConnectivity processing aborted!

Solution:
Message should be correctly read and sent by the SicsAcordClient

Workaround:

Root Cause:

Extent of Impact:

Impact on Existing Data

Recovery Method for Existing Data Affected

Problem:
DuplicateMessageMappingRule abends checking referenced insured period

Solution:
Referenced insured period should have an affect on DuplicateMessageMappingRule

Workaround:

Root Cause:

Extent of Impact:

Impact on Existing Data

Recovery Method for Existing Data Affected

Problem:

SICS Documentation: Installment Premium Order

Solution:

Reported that some fields on the Instalment order are not described in the user's guide and one field that is described but not shown on the window.

This discrepancy need to be updated in the user's guide.

Workaround:

Root Cause:

Extent of Impact:

Impact on Existing Data

Recovery Method for Existing Data Affected

Problem:
Business ID of OIP business missing.

Solution:

2 new objects.
OIP Business ID
OIP Current Share

Workaround:

Root Cause:

Extent of Impact:

Impact on Existing Data

Recovery Method for Existing Data Affected

Problem: Flag field, 'Affects Liquid Balance,' has no equivalent reporting object in the 21.3 BI REF_DATA reporting universe.

Solution:   Flag field, 'Affects Liquid Balance,' object should be added in the 21.3 reporting universe.

Workaround:

Root Cause:

Extent of Impact:

Impact on Existing Data

Recovery Method for Existing Data Affected

Problem:
Extract on estimation items do not check estimation type.
Solution:
New object for estimation type

Workaround:

Root Cause:

Extent of Impact:

Impact on Existing Data

Recovery Method for Existing Data Affected

Problem:
UE Estimation Amount for Base and Main

Solution:

SQL linked to objects changed,

Workaround:

Root Cause:

Extent of Impact:

Impact on Existing Data

Recovery Method for Existing Data Affected

Problem:

User Defined Fields in SICS for ORP as SICS does not inherit the values from OCC down to ORP level

Solution:

Add this view (VIEW V_UDD_Business_L2) to the database

Workaround:

Root Cause:

Extent of Impact:

Impact on Existing Data

Recovery Method for Existing Data Affected

Problem:

If selecting a Reporting Unit in a Hierarchy and selecting Edit from the pop up menu to add a Base Company, the “Updated By” does not get saved and the Edit is lost after a full Refresh.

Solution:

The system should save the same updates on a Reporting Unit Leaf, opened from the bottom of a hierarchy, in the same way as it currently correctly does if the user updates directly on the Left (opened outside the hierarchy from the reporting unit list at the bottom): 

If doing an update on a Reporting Unit Leaf, opened inside a hierarchy, for example assigning a Base Company, the Last Updated User and Last Updated At should be shown both immediately and after full refresh.

If assigning a new Base Company to a Reporting Unit, this base company should be shown also after full refresh, both in the hierarchy and on a Leaf when opened directly outside the hierarchy.

Workaround:

Root Cause:

Extent of Impact:

Impact on Existing Data

Recovery Method for Existing Data Affected

Problem:
Joins for Base Company adress incorrect
Solution:

Joins corrected.

Workaround:

Root Cause:

Extent of Impact:

Impact on Existing Data

Recovery Method for Existing Data Affected

Problem:
XL adjustment premium incorrect for ORP
Solution:
Check on LoB before premium is calculated.

Workaround:

Root Cause:

Extent of Impact:

Impact on Existing Data

Recovery Method for Existing Data Affected

Problem:

In the Reference data universe the object 'Notes' are not available

Solution:

Need to add that object 'Notes' in the universe

Workaround:

Root Cause:

Extent of Impact:

Impact on Existing Data

Recovery Method for Existing Data Affected

Problem:

Missing outer joins for some of the reporting unit tables

Solution:

Need to add outer joints for reporting unit tables

Workaround:

Root Cause:

Extent of Impact:

Impact on Existing Data

Recovery Method for Existing Data Affected

Problem:

Because of the wrong definition in the objects, it is generating unnecessary joints while generating a report

Solution:

We need to change the definition of the object under the Gap estimates folder 'Period Est Currency (code)' in both SPC&OPC main SICS 22.2

Workaround:

Root Cause:

Extent of Impact:

Impact on Existing Data

Recovery Method for Existing Data Affected

Problem:
When the Automatic VAT Calculation is in use and in addition the system parameters 'VAT Calculation based on EC Groups' and 'Additional VAT Calculation' are selected, it is possible to exempt VAT calculation on an insured period. This is possible in on-line SICS, but the same possibility is no available in Web Services

Solution:
In on-line SICS, when automatic VAT calculation is in use, it is possible to exempt an insured period from the calculation. This possibility is missing in web service. We therefore need to, in web services, <insuredPeriod> section, include a new element <VATexemption>, values Yes(True) / No (False).

Problem:

createClaim API fails if sectionSpecificClassificationList element is included 

Solution:

The createClaimAPI must support the sectionSpecificClassificationList

Workaround:

Remove element sectionSpecificClassificationList

Root Cause:

SE-8778

Extent of Impact:

Impact on Existing Data

Recovery Method for Existing Data Affected

Problem:

The field in which additional mandatory claim classification item can be defined is no longer available/visible

Solution:

Rearrange window so that selection of the field is available again

Workaround:

Root Cause:

SE-10536

Extent of Impact:

Impact on Existing Data

Recovery Method for Existing Data Affected

Problem:

Mass Renewal by Web Service does not set Placement Complete even if reply indicated in the web service message.

Solution:

When mass renewing an outward cedent's contract by Web Service: 

• If an answer to the BS00225 question is included in in the Web Service message and the answer is Yes, then the system the system should set the Placement Complete flag to Selected.  
• If an answer to the BS00225 question is included in in the Web Service message and the answer is No, then the system should not set the Placement Complete flag to Selected.  
• If an answer to the BS00225 question has not been included in in the Web Service message, the system should stop the user and return the message BS0225' Total Signed Share is 100.0000000000, which is considered to be 100 percent. (The tolerance range is 99,9999999950 - 100,0000000049). Do you want to set Placement Complete to Yes?' 

Workaround:

Root Cause:

Extent of Impact:

Impact on Existing Data

Recovery Method for Existing Data Affected

Problem:
When creating Placement via Webservice, Former Id and Title are not updated. However, CreatePlacementForOccRequest soap XML processes successfully without error.

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

Workaround:
User could manually update missing information from Placement using SICS Workstation.

Root Cause:

Extent of Impact:

Impact on Existing Data

Recovery Method for Existing Data Affected

Problem:
Sometimes, differences are reported when there are no differences.
Sometimes, existing differences are not reported.
Sometimes, the mapping comparison abends due to IndexOutOfBoundsException.

Solution:
Improve the mapping comparison logic.

Workaround:
None

Impact on Existing Data
None

Problem:

Abend Creating DMSI Index Properties for ORP WS

Solution:

When clicking the Attachment icon on the worksheet closing window the system must be able to open the attachment, without falling over, even on an ORP.

Workaround:

Root Cause:

Extent of Impact:

Impact on Existing Data

Recovery Method for Existing Data Affected

Problem:
BUG 1017899 - Missing Web Service Elements for Invoice No, GT Ref No & Invoice Date

Solution:
The balance fields; Government Tax 'Invoice No', 'Government Invoice Ref No' and 'Invoice Date' must be possible to update through the following SICS web services;

createWorksheet, createClaimWorksheet and updateWorksheetBalanceInformation.

In the createWorksheet or createClaimWorksheet, if the service creates multiple balances and if any of these new balance fields are given, it means that each balance will be set with the values belonging to that balance on the worksheet.

Workaround:

Root Cause:

Extent of Impact:

Impact on Existing Data

Recovery Method for Existing Data Affected

Problem:
Missing validation of duplicate exchange rate.
Solution:

Validation reimplemented

Workaround:

Root Cause:

Extent of Impact:

Impact on Existing Data

Recovery Method for Existing Data Affected

Problem:
Directory for Loader emp file

Solution:

Appended load filrd dpes not work.

Workaround:

Root Cause:

Extent of Impact:

Impact on Existing Data

Recovery Method for Existing Data Affected

Problem:
Proportional facultative business with adjustment premium schedule abends when retrieved by web service

Solution:
A proportional business cannot have a Loading Factor. Therefore, when retrieving a business by web service, and this business has a Premium Adjustment schedule, the system should NOT check for a Loading Factor when looking at the Adjustment Premium Rate, IF the Type of Business is something else than Non-Proportional Facultative and Non-Proportional Treaty.  For proportional business, the system should just skip Loading Factor.   

Workaround:

Root Cause:

Extent of Impact:

Impact on Existing Data

Recovery Method for Existing Data Affected

Aim of function-

To be able to update the Accounting Classification name and/or Accounting Classification Split % through a Web Service both for SICS P&C and SICS Life. It can be used for updating the Accounting Classification name and Accounting Classification Split % for one or multiple Accounting Classifications.

All the validations and interactive messages applicable to this functionality for Workstation are applicable to this new Web Service also.
The name of the new web service is updateAccountingClassifications and is found in SicsWsBusinessEntryPoint.

System Parameters Affected-

No System Parameter is affected.

Existing functionality affected-

Update Accounting Classification Name.
Update Accounting Classification Split %.
Web Services within SicsWsBusinessEntryPoint.

Aim of function

When creating worksheets through createWorksheet or createClaimWorksheet web services, a new interactive warning message is needed so that the user can reply Yes on this message, while the web service is stopped by Government Tax validation error. In the above two web services the various GT error messages that appear online should be replaced by the new warning message so that the worksheets can be created in open status.

System Parameters Affected

No System Parameter is affected.

Existing functionality affected

System now creates a new interactive warning message in the web services createWorksheet and createClaimWorksheet instead of error message. When replied Yes on the new warning message, the worksheet can be created in Open status even if a Government Tax validation error would have stopped this worksheet from being applied to the database in an online process. At the same time, the reason for the validation error is also logged for this detail in the DB to allow identification of the failed detail record(s) later. In the above two web services, the new warning message replaces the Government Tax error messages that are triggered online. When these worksheets later are closed the system will trigger the online Government Tax validations and the user must take actions accordingly (existing functionality).

Aim of the function:

The aim is to ensure that there are no paid remittance with classification Cash Payment left unsettled in the system. To achieve this objective, an error message will appear if a new Paid remittance with Rem Class 1 equal Cash Payment is created and left Unsettled. Further more, if a remittance is generated from an existing Technical or Claim balance it will be set to Cash Payment and immediately/automatically paired and set to Settled.
Reversal of a Received remittance will also generate a Paid remittance with Cash Payment and these two remittances will be paired and set to Settled automatically.

System Parameter/Reference Data Affected:

New system parameter 'Independent creation of Cash Paid remittance not allowed' under Accounting, Balance Pairing

New system defined value in Reference table 415 (Rem Class 1) named 'Cash Payment'

Also existing parameters affects this functionality:
'Mandatory - Rem Class 1' under Accounting, Remittance
'Automatic Balance Pairing when change of Remittance Status' under Accounting, Balance Pairing.

Existing functionality Affected:

Manually creation of Paid Remittance balances, in any status, and leave them Unsettled

Reverse Received Remittance balances and create reversal Paid Remittances

Generate Remittance balances from payable individual balances or balance groups

Aim of the function:

The aim is to ensure that during the Pairing process, any remittance balance(s) involved should never be left as Partially settled and in such a case, the pairing process must be stopped by the system.

System Parameter Affected:

New system parameter: Suppress creation of Partially settled remittance balance

Existing functionality Affected:

Currently there is no system parameter/functionality to stop the User from creating a ‘Partially Settled’ Remittance Balance during the pairing process. However, there are certain scenarios based on a specific system set-up where the system provides an alternative to the User to decide whether to leave the Technical or the Remittance balance as partially settled; and the User can select the option to leave the Remittance Balance as partially settled

Aim of function

Client wants to give exception of  mixing technical and remittance balances as included balances in the balance pairing when they are not both in Pending status. So we introduce new system parameter 'Exclude Definite Pairings from the above restriction' to control. If checked, be able to replace an Unallocated Remittance Balance with a regular Remittance Balance in a Balance Pairing when there exists other Technical/Claim Balances in this pairing that are Definite, or vice versa. 

System Parameters Affected

Balance Pairing Group in use
When Pairing, always use Remittances as the driving Balance
Exclude Definite Pairings from the above restriction 

Existing functionality affected

Replace Selected URB in Pairing

Aim of Function

In SICS, the current Outward Cedent’s Contract placing process allows loading of retrocessionaires from external excel files. Earlier, only Signed Share could be uploaded. This enhancement makes it possible to upload both Signed Share and Written Share values.

In addition, it is now possible to upload files to update share values (signed share and written share) on existing retrocessionaires.

System Parameters Affected

Business / P&C Miscellaneous/ Default Status of Upload of Placements

Existing functionality affected

Create New Business
Place Business 
Maintain Share Condition
Change Life Cycle Status

Aim of function

To reduce clutter in the user experience of SICS, the security facility now hides the condition buttons if they have no content (empty) and the user do not have an Update or Create right for these conditions.

When the user has no Update or Create right for certain conditions, their buttons are not be visible anywhere if they do not have any content. For example:
-Toolbar
-Structure Overview
-Cedent’s Program Contract Overview

Condition buttons are visible and accessible if they have contents (condition buttons are yellow).

System parameters affected
None

Existing functionality affected
Maintain Share Conditions
Maintain Premium and Limit Main Conditions
Maintain Deduction Conditions
Maintain Reinstatement Conditions
Maintain Claim Conditions
Maintain Rebate Conditions
Maintain Deductibles Conditions
Maintain Profit Commission Conditions
Maintain Cancellation Conditions
Maintain Index Clause Conditions
Maintain Clauses Conditions
Maintain Reserve Conditions
Maintain Deposit Conditions
Maintain Portfolio Conditions 
Maintain Calculation Rules Condition
Maintain Performance Management Data Return Condition
Maintain  Additional Scope
Maintain Administration Life
Maintain Agreement Clause Life
Maintain Cancellation Provisions Life
Maintain Claim Life
Maintain Deposit of Reserves Life
Maintain Experience Adjustment Life
Maintain Limit Life
Maintain Non-Contract Administration Life
Maintain Portfolio Transfer Life
Maintain Premium Life
Maintain Profit Commission Life
Maintain Sum at Risk Life
Manage Security
Maintain Section Overview
Maintain Cedent's Program Contract Overview
 

Aim of Function

An excess of loss treaty may have special covers like Clash Cover and Cost Cover. For these, SICS has separate validations, e.g. regular covers cannot overlap, clash covers cannot overlap, clash cover can overlap with regular cover and vice versa. 

Earlier, if using web services to capture Treaty Type of Cover, it could be captured only when creating treaty outlines on a reinsurance program.  Now, it is possible to capture Treaty Type of Cover also when creating a new assumed non-proportional treaty or updating an existing one by using web services.

The new element <treatyTypeOfCover> has been added to the <insuredPeriod> part of relevant Web Services.

System Parameters Affected
None

Existing Functionality Affected
Create Business by Web Service
Update Insured Period by Web Service

Aim of function

Display lists in SICS have an initial setting called the Factory Settings. The lists can however be customized by an organization and even by individual users, depending on security permissions.

When a user is allowed to save column settings (User Preferences / Misc. Preferences: “Allow Saving of Container Changes (Column Changes)” is selected), additional options are available in the standard pop-up menu of the display lists. These options were earlier missing from the display lists of Protection Program and Reinsurance Program treaty parts: Prop., XL, AX and SL. These have now been made available.

System Parameters Affected

 None

Existing functionality affected

Organise Display Lists
View Protection Program Outlines
View Reinsurance Program Outlines

Aim of function

Earlier, the create new business partner wizard allowed for some details to be set up to appear as additional pages.  All items listed under the Details tab of an existing business partner were available, however, out of these, only 2 pages could appear simultaneously. Now, this has been improved to allow all pages to be included in the wizard simultaneously. In addition, the User Defined Page can also be included here. 

These improvements apply to Business Partner, Bank, Third Party and Person.

System Parameters Affected

None

Existing functionality affected

Create Business Partner
Create Bank
Create Person
Create Third Party
Maintain User Defined Pages
Maintain Reference Data

Aim of function:

Make Headline Loss link mandatory for Main Class of Business/Base Company combination

System Parameters affected:

New Base Company Specific Setting parameter enabling activation, and listing of Main Classes of Business

Existing functionality affected:

Create New Claim

Link Claim to Headline Loss

Create Worksheet

Change Claim Status

Aim of function

New API which allows user to create a link between a single claim worksheet and one or more eMessages.

System Parameters Affected

None

Existing functionality affected

Aim of function

 When either reporting unit or combination of Base Company and Main Class of Business indicates that link to Headline Loss is mandatory, user cannot close a claim worksheet unless this link is defined.

System Parameters Affected

New parameter 'Link to a Headline Loss is Mandatory when Closing Claim Worksheet' 

Existing functionality affected

Close Claim Worksheet

Aim of function

New rule applicable for claim movement messages which do not have the FGU Indicator activated. When rule is included the messsage creation date will be used as the as of date in the worksheet, instead of the message' as of date.

The rule should be implemented on message layer

System Parameters affected:

None

Existing functionality affected

Process Claim Movement message

Swap to Claim Worksheet

Aim of function
The aim is to make it possible to automatically validate messages after they have been imported, without fully processing the messages.
Two changes:

1. Added a new system parameter 'Validate on load' in eMessaging -> Processing Options
When selected, messages are automatically validated once they are loaded.

2. Added a new Job Step Type 'eMessaging Import and Validate' in Scheduler.
When used, messages are automatically validated after they have been imported.

System parameters affected
eMessaging Processing Options parameter 'Process on load'

Existing functionality affected
Import eMessaging messages from the workstation
Import eMessaging messages from Scheduler

Aim of function
Made various improvements on the creation of outbound messages in eMessaging

• Made it possible to specify an ACORD Schema version for a specific recipient. This is done in eMessaging Information on the business partner. If a partner has a specific ACORD Schema selected then this is used to generate message for that recipient, otherwise if non is set then the Global ACORD Schema is used.
• Added Support for a commission calculation account, including supporting document for calculation description.
• On Outbound messages, made it possible to switch the sign of the amount in the case that the Entry Code and ACORD code normally positive flags do not correspond
• On Claim Movement messages, made it possible to include FGU Advisory info when FGU Indicator is activated,
• On Claim Movement messages, added previous amounts when applicable, so that messages with booked adjustments can be validated against the previous movements.
• On Claim Movement messages, when a message has a booking of a Multiple Account Group Item for current payment, all other items in the group are also included. Same when a message has a booking of a Multiple Account Group for Outstanding Loss, all other items in the group are also included.
• On Claim Movement messages and TechAccount Claim Signings: When a message has a booking of an item having a current and previous item for loss / loss expense, the total loss incurred / loss expense incurred is also included in the message

System parameters affected
N/A

Existing functionality affected
Create outbound TechAccount and Claim Movement messages

Aim of function

When FGU Advisory is created by an eMessage the system should default the entry codes using mapping table for the message amtItems for the initial message, but for subsequent messages entry codes should be defaulted using mapping table for message amtItems, and default the entry codes defined on latest advisory for non-message FGU amounts (Client IBNR, Client IBNR LAE, ACR, ACR LAE

 System Parameters Affected

None

Existing functionality affected

Validate and process subsequent ClaimMovement message using FGU booking rule

Aim of function

You can now generate or execute one or multiple BOAC Scripts in a single click in the from System Administration Desktop (SICS Admin –> Database Setup -> Manage Tables -> BO Reporting Tab).
User can also Create or Execute one or Multiple support scripts in single click in the System Administration Desktop.

BOAC Scripts : 

Support Script : 

System Parameters Affected

Not Applicable

Existing functionality affected

1. Creation of BOAC Scripts from SICS admin & Execution of BOAC scripts on Database from SICS Admin

2. Creation of Support Scripts from SICS admin  & Execution of Support Script  on Database from SICS Admin

Aim of function
Provide a means of issuing system level announcements to a specific SICS environment that will be shown on login and desktop refresh.
The announcement is edited in System Parameters and includes a from/to dates:

When the user logs into a SICS Environment or refreshes the desktop, the announcement will be shown if the from/to dates indicate it is active.

An API is provided for programmatically setting/unsetting the announcement.

System Parameters Affected
New system parameter section and settings:
Desktop Administration/Banner Announcement

Existing functionality affected
Login/Refresh

Aim of function

Fully support unicode mode on SQL Server on all text columns. In prior releases, some columns were not correctly created as NVARCHAR columns when unicode mode was enabled.

System Parameters Affected
In the sics-databasesource.xml file

 <unicodeMode>true</unicodeMode> 

Existing functionality affected

Create tables

Aim of function

Enable the import of Excel files (workbooks) where one or more sheets contain cells with a formula that refers to another, pivot table sheet, using the PIVOT function. SICS uses a 3rd party library, POI, to read Excel data. This library does not support the PIVOT function. The solution is to utilize the pre-calculated value of the cell formula. This value was stored during the last save of the Excel workbook, and was made available in a recent upgrade of POI. There should be no need to re-calculate the formula during import to ADH.

System Parameters Affected

None.

Existing functionality affected

ADH import of Excel spreadsheets as XML data.