Release documentation - P&C Enhancements and requests

Problem:
Remittance Group and Pairing - Bank Account not set on all Group Internal remittances

Solution:
When the user from a Settlement Balance Group selects the option Create Remittance and this results in a Group Remittance because the SBG contains of balances with different Base Companies and the system parameter 'Is Group Remittances In Use' is activated, then we must make sure the system populates the Base Company's Bank Account for each of the Group Internal remittances when this is possible. Only if it is not possible, i.e. because there are no valid bank accounts found, that the Bank Account field can be left empty.

Workaround:

Root Cause:

Extent of Impact:

Impact on Existing Data

Recovery Method for Existing Data Affected

Problem:
Creation of Accounting Classification not properly working on non-prop outward cedent's contract

Solution:
When the user selects the option Generate Accounting Classification on a Non-Prop Treaty OCC and on a Non-Prop Fac OCC, the system will generate one AC for each combination of classification elements available on the business that is part of the mandatory classification types for the given Base Company. In this process the system must also take the mandatory Reporting Units into account and include ALL values of the mandatory RUs on the business and not only the first one.

Workaround:

Root Cause:

Extent of Impact:

Impact on Existing Data

Recovery Method for Existing Data Affected

Problem:
Issue - Create Remittance worksheet webservices.

Solution:
When running the create Remittance web service and a Partner's Bank Account ( <partnersBankAccount>) is given, if there are MULTIPLE bank accounts with this account number, make sure the system picks the one matching the Bank Account Currency (<bankAccountCurrency>).
If only one bank account exists for this partner in this currency or if none of the bank accounts has this currency, then the existing logic shall apply.

When running the create Remittance web service and a Base Company's Bank Account ( <bankAccount>) is given, if there are MULTIPLE bank accounts with this account number, make sure the system picks the one matching the Bank Account Currency.

Workaround:

Root Cause:

Extent of Impact:

Impact on Existing Data

Recovery Method for Existing Data Affected

Problem:
Validation against System parameters

Solution:
On the Accounting Classification window for a business, when the user select the menu option Validate Against System Parameters, the system checks all elements in each AC against the setup for the actual Base Company, both in Classification Rules 1 and 2. When the system check the definition of the Reporting Unit in Classification Rules 1, the system must check ALL Reporting Unit Categories that are selected to be mandatory (and unticked the box 'Not Allowed For AC'), and compare these with the RU values in the actual Accounting Classification. The value Yes in the column 'Valid per Sys Params' must be set to No if there is a mismatch between the elements in the AC and the setup in the system parameters for this Base Company.

Workaround:

Root Cause:

Extent of Impact:

Impact on Existing Data

Recovery Method for Existing Data Affected

Problem:
Commutation - No Closed Date after order and worksheet has been closed

Solution:
When running the Commutation Calculation Order and the worksheets created by the order is set to Closed or Inactivated, we must make sure the Closed Date/Inactivated Date is correctly set for the worksheet.

Workaround:

Root Cause:

Extent of Impact:

Impact on Existing Data

Recovery Method for Existing Data Affected

Problem:
GOV TAX - Inconsistent Gov Tax Validation after Automatic Booking and Trigger EC

Solution:
On Claim worksheet, when the user has selected the Automatic Booking of Government Tax or applied the worksheet so that a Government Tax target details is created, and the trigger and target entry code is linked together, then the system must also disable the Entry Code field for these details so that the user cannot change the entry code. This is the case on a Technical worksheet, and we need to implement the same for Claim worksheet.
If the trigger entry code is wrong, the user must delete the detail and create a new detail. In this way the link to the target detail is also removed.

Workaround:
Instead of changing the Entry Code on the trigger details the whole detail can be deleted and create a new trigger detail.

Root Cause:

Extent of Impact:

Impact on Existing Data

Recovery Method for Existing Data Affected

Problem:
1. Insured Period can be update when the closed worksheets and inactivated worksheets sum up of 0.
2. Insured Period can be update when the closed worksheets and open worksheets sum up of 0.

Solution:
1. When checking for open worksheet we must check for ALL pending worksheets (all except for Closed and Inactive)
2. When checking for existing bookings if they are summed up to zero or not, we must ONLY check Closed worksheet (not pending worksheets and not inactivated worksheets)

Workaround:

Root Cause:

Extent of Impact:

Impact on Existing Data

Recovery Method for Existing Data Affected

Problem:
Option to Copy an order from Find screen - incorrect access rights error

Solution:
When the user do not have access right to Create in the Use Case 'Accounting Automatic Premium', make sure the option Copy to... from the accounting order itself triggers the security message and prevents the user from copying the order in the same way as when the option Copy... is selected from the Find Accounting Order.

Workaround:

Root Cause:

Extent of Impact:

Impact on Existing Data

Recovery Method for Existing Data Affected

Problem:
SICS abends for all Business which are affected by the GOV TAX Calculation

Solution:
When a Government Tax Rule is created/updated with the Active flag set and with a Trigger Entry Code Group given, SICS must also require a Target Entry Code defined for this rule before it can be saved.

Workaround:
Ensure that all Active Gov. Tax rules have a Entry Codes defined. Either add missing Entry Codes or Inactivate Rules without.

Root Cause:

Extent of Impact:

Impact on Existing Data

Recovery Method for Existing Data Affected

Problem:
TA document abends when you show cumulative reserves

Solution:

Make sure cumulative reserves is supported.

Workaround:

Root Cause:

Extent of Impact:

Impact on Existing Data

Recovery Method for Existing Data Affected

Problem:
GOV TAX - Gov Tax Validation not triggered if Trigger Target EC link is created

Solution:
When a worksheet, technical or claim, is applied to the database (Apply or Change Status options), and it contains both Government Tax Trigger and Target entry codes, SICS must perform the Government Tax validation even if Government Tax Link has been manually created between the trigger and target details. If the target detail's amount is not correct, then an error message must appear and the user cannot apply the worksheet unless the amount is corrected or a GT Category/Comment is added to overrule the error.

Workaround:

Root Cause:

Extent of Impact:

Impact on Existing Data

Recovery Method for Existing Data Affected

Problem:
Periodic function Generate Preliminary bookings does not create the asOriginal bookings.

Solution:

Make sure that create worksheets with bookings and pairings are created.

Workaround:
Accounting Order - Preliminary Bookings can be used,
Create Order i workstation and scheduled as an accounting order,

Root Cause:

Extent of Impact:

Impact on Existing Data

Recovery Method for Existing Data Affected

Problem:
The system abends when choosing a date in claim worksheets and in online statistics. 

Solution:
The system should allow the selection of the  date using the calendar widgets.

Workaround:
Enter the date directly, instead of using the calendar widget

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:
PRB100005406 - Autopairing is failing for remittance linked to Group Balances if different BCs involved

Solution:
When status is change to Final on a remittance linked to an Account Balance Group, or Settlement Balance Group, the system must fulfill this pairing process as long as the involved Base Companies are linked together in the Base Company Properties, under Linked Base Companies.

Workaround:

Root Cause:

Extent of Impact:

Impact on Existing Data

Recovery Method for Existing Data Affected

Problem:
Incorrect AC picked up on ORP level (NPTTY OCC) due to invalid RU

Solution:
When booking takes place on a non-prop treaty OCC or non-prop fac OCC, with Reporting Unit as a mandatory part of the Accounting Classification, then the Reporting Unit must also be part of the validation and comparison of the Accounting Classification used on the booking on the ORP placement. The SAME Reporting Unit must be used in the AC on the ORP as it is in the AC on the OCC.

Workaround:

Root Cause:

Extent of Impact:

Impact on Existing Data

Recovery Method for Existing Data Affected

Problem:
SICS abend when check 'show all booking' in TW edit screen.

Solution:
On a technical worksheet, when the user selects the Show All Bookings tick box, the system must show the previous values on ALL entry codes that allows replacement value without abending.

Workaround:

Root Cause:

Extent of Impact:

Impact on Existing Data

Recovery Method for Existing Data Affected

Problem:
When you import technical worksheet from spreadsheet with multiple businesses/currencies, and use the New Amount column, then the details on the business/currency not inspected by the user becomes zero, i.e. the Amount value is not calculated.

Solution:
When worksheet is created by the Import Technical Worksheet from Spreadsheet and the values are given in the New Amount column, then the system must correctly calculate and store the Amount for ALL details, also those details not inspected by the user.

Workaround:
If you open each page of the worksheet with details on, then all details will be updated correctly.

Root Cause:

Extent of Impact:

Impact on Existing Data

Recovery Method for Existing Data Affected

Problem:
Pairing with Write-Off causing an abend of SICS

Solution:
When a balance pairing takes place between a remittance with Functional Currency amounts present and a technical balance without the Functional Currency amounts present and the system has calculated a Write Off, the system must be able to complete the pairing by totally ignore the Functional Currency Revaluation function. As long as one of the balances in the pairing is missing the Functional Currency amounts no FC revaluation calculation shall take place, neither for Write Off nor for Exchange Difference

Workaround:

Root Cause:

Extent of Impact:

Impact on Existing Data

Recovery Method for Existing Data Affected

Problem:
SICS abends when running Revaluation Order for details on outward prop treaties

Solution:
When running the FC Revaluation order it is important that the system group details on outward by using the flags isInOrigCurr, isInBookCurr and isInAcctCurr, so that the bookings on the different ledgers are handled separately. All internal queries and temporary tables must take into account that the details can have different values in these 3 columns in the tables.

Workaround:

Root Cause:
Parts missing in the correction done in 21.1 according to the service case SICSR-20632

Extent of Impact:

Impact on Existing Data

Recovery Method for Existing Data Affected

Problem:
Enhancement SE-9026 - Due Date not working when Accounts defined on Administration conditions

Solution:
When the new system parameter 'Set Due Date from Received Date on Technical Worksheet' is selected then the system should override all the existing logic for how to set the Due Date, also if single accounts are defined on the Administration conditions, so that the Due Date is taken from the Received date on the worksheet (named Received External if the system parameter 'Is Received Internal Date On Worksheet In Use' is selected) also in this situation.

Workaround:

Root Cause:

Extent of Impact:

Impact on Existing Data

Recovery Method for Existing Data Affected

Problem:
The AC_LEDGER_DETAIL.DTL_UNR_AMT are wrong for all deductions created by instalment order

Solution:
When running an Instalment or Adjustment order, and the system sets the Unreleased Amount (DTL_UNR_AMT) for the calculated details (i.e. all deduction details), the system must set (initiate) this Unreleased Amount equal the original amount (DTL_AMT) it belongs to and NOT as a copy from the source premium amount. Most of the detail attributes for the calculated deduction details are copied from the source premium detail, but the DTL_UNR_AMT must be reset equal to the DTL_AMT for these deduction details.

Workaround:

Root Cause:

Extent of Impact:

Impact on Existing Data

Recovery Method for Existing Data Affected
Make an update script to reset the DTL_UNR_AMT equal the DTL_AMT on the detail it belongs to for all details created by instalment/adjustments

Problem:
When matching on payment partner, mass pairing seemed to assign the same pairing ID to all the pairings.

Solution:
When balance pairing takes place by use of the Mass Pairing the system must handle each driving remittance separately and create one Pairing Id for each of them and the pairings with all the included balances for each remittance. If the Mass Pairing finds match between 2 remittances and 2 other balances (individual balances or balance groups) and the pairing takes place between each of the remittances and the matching balances, then the system shall also create 2 Pairing Ids, one for each of the pairings created for the individual remittances.

Workaround:

Root Cause:

Extent of Impact:

Impact on Existing Data

Recovery Method for Existing Data Affected

Problem:
GOV TAX - Able to close CL WS without entering Gov. Tax Comment

Solution:
When a Government Tax Rule is triggered on a Claim Worksheet the system must require that BOTH a Government Tax Category AND a Government Tax Comment is given by the user before the worksheet can be closed. In the same way as it works for Technical Worksheet.

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:

Extent of Impact:

Impact on Existing Data

Recovery Method for Existing Data Affected

Problem:
Entries link to HL use wrong FX Rate

Solution:

When linked to HL - CW rules applu.

Workaround:

Root Cause:

Extent of Impact:

Impact on Existing Data

Recovery Method for Existing Data Affected

Problem:
System crashes when trying to book Instalment Premium including Deductions

Solution:
When booking manually or through instalments on a Treaty OCC or Fac OCC with placements, and with accounting classification split defined, and the user select the option to automatically calculate deductions for the given premium we must make sure the system does not set the temporary split identifier for the deduction, but sets this identifier only when the user selects the menu option Apply Split or selects the popup menu option Split Selected Booking per Accounting Classification. This temporary split identifier is necessary only when details are split by accounting classification.
When the worksheet is closed it is also important that only the details with this temporary split identifier set use this feature and that details without this identifier are treated without so that the system does not abend but are able to closed the worksheet both on the OCC and on the ORP

Workaround:

Root Cause:

Extent of Impact:

Impact on Existing Data

Recovery Method for Existing Data Affected

Problem:

Abend when selecting 'Find All Matching businesses' from the Assumed businesses window of a Portfolio Program

Solution:

Remove abend

Workaround:

Root Cause:

Extent of Impact:

Impact on Existing Data

Recovery Method for Existing Data Affected

Problem:

When for pending (e.g. Quoted) business with the Cedent business partner still in Provisional status changing the Life Cycle Status to Definite (Offer Accepted) and recording the Signed Share, the system first gives a message, but then abends. 

Solution:

The system should not abend if changing the Life Cycle Status of a business to definite when one of its partners have a Provisional Completenes status, even though this business does not have any earlier insured periods. This should be the case whether the Business Partner Assignment page has been set up in the reference data to be part of the Change Life Cycle Status Wizard or not.

Workaround:

Root Cause:

Extent of Impact:

Impact on Existing Data

Recovery Method for Existing Data Affected

Problem:

In the Create New Business Partner wizard, there are pages where in View mode it is possible to delete existing fields.  Afterwards, when trying to enter value in these fields, the system raises an error like message.

Solution:

Create New Business Partner wizard – pages:

• Addresses
• Alternative Names
• Brokerage Frame Agreement
• Detailed Claim Checks
• Former Names
• Key Figures

All values and rows added on any screen must not be open for edit directly from the wizard pages in view mode.
The fields should be editable only via pop-up option Edit, just like when recording or reviewing such information from the Details tab of Business Partner.

Workaround:

Root Cause:

Extent of Impact:

Impact on Existing Data

Recovery Method for Existing Data Affected

Problem:
SICS does not return results when searching for Business Partners based on partial Identifier

Solution:
Find Business Partner screen must return results as per given search criteria even when search is based on partial Identifier

Declination Reason:

Workaround:
Search for Business Partners by using full Identifier instead of partial one

Root Cause:
SE-5039 / SICSR-20446

Extent of Impact:

Impact on Existing Data

Recovery Method for Existing Data Affected

Problem:

eMessaging Membership fields does not work on Find:Business Partners.

Solution:

Make sure that 'Agency' combo have values and user is able to find information as per selected value.

Workaround:

Root Cause:

Extent of Impact:

Impact on Existing Data

Recovery Method for Existing Data Affected

Problem:
The system allows worksheet to be changed to status which should be restricted by Domain Restriction Account Section on Worksheet definition, and when attempting to view the worksheet properties (after closing) the system is abending.

Solution:
The system should have raised security message AC0294 preventing user to change status restricted by the domain restriction.
The system should allow user to inspect worksheet  properties.

Workaround:

Root Cause:

Extent of Impact:

Impact on Existing Data

Recovery Method for Existing Data Affected

Problem:

Domain Restriction Accounting Worksheet Claim Details For Threshold Amount' is not triggered when expected

Solution:

The Claim Threshold Domain Restriction should consider bookings made towards Loss Expenses and Loss Expense Reserves when condition is either not available (Prop fac business), or defined as None or Part of Liability.

Workaround:

Ensure that Claim Accounting parameter 'Remove Entry Codes without adjustments' is cleared, and always respond No to AC0167 when that appears

Root Cause:

Extent of Impact:

Impact on Existing Data

Recovery Method for Existing Data Affected

Problem: 

Domain Restriction Liquid and Non-liquid amount validates 'Incurred' amount, and only raises error for non-liquid amount although both have been defined. 

Solution:

The Domain Restriction must validate liquid and non liquid separately. If only liquid is activated,  and liquid balance exceeds the defined amount, the liquid error AC0292 should appear. None liquid amount is not relevant.

If only none-liquid is activated, and none liquid exceeds defined amount, the none -liquid error AC0293 should appear. The liquid amount is not relevant.

If both are defined, both must be validated, and both errors must be raised if relevant.

Workaround:

Root Cause:

Extent of Impact:

Impact on Existing Data

Recovery Method for Existing Data Affected

Problem:
Abend when creating a various loss detail and registering the detail's claim reference simultaneously.

Solution:
A various loss detail should be possible to create with all information, including claim references.

Workaround:

Root Cause:

Extent of Impact:

Impact on Existing Data

Recovery Method for Existing Data Affected

Problem:
No validation that Claim Date of Loss on a Risks Attaching Business is outside Original Policy Period when Administration condition has been defined/saved.

Solution:
When claim basis is Risks Attaching, the general rule is that the Date of Loss must be within Original Policy Period, and OPP Start date must be within Insured Period-

If Administration condition cession basis is defined as Clean Cut, the date of loss should be within Original Policy Period and Insured Period, and OPP start must be within Insured Period.

If Loss Portfolio is defined, the date of loss must be within Original Policy Period, but the OPP Start does not have to be within the Insured Period - also if business has a Clean Cut Provision.

If Administration clause is not available (parameter) this should be interpreted as not defined - and general rule apply.

The assumption for all of the above is that Claim Trigger on Claim remains NONE.

Workaround:
Delete the Administration Clause

Root Cause:
SE-9608

Extent of Impact:

Impact on Existing Data

Recovery Method for Existing Data Affected

Problem:
Informational Client IBNR is impacting inuring calculation.

Solution
When Client IBNR is informational, it should not impact the inuring calculation.

Workaround:
Enter the inuring amounts instead of calculating.

Root Cause:
SE-2395

Extent of Impact:

Impact on Existing Data

Recovery Method for Existing Data Affected

Problem:
Abend when using quick find to find a headline loss

Solution:
System should open the Headline Loss if match is found, otherwise raise error message SICS0011 No match is found if Headline cannot be found

Workaround:
Use Find Headline Loss

Root Cause:

Extent of Impact:

Impact on Existing Data

Recovery Method for Existing Data Affected

Problem:
Own Incurred is not set correctly on previous advisories when activating ACR in FGU

Solution:
Ensure that Own Incurred is set to same amount as Incurred when parameter is activated (if ACR, ACR LAE, Client IBNR and Client IBNR LAE entry codes are null) (Neither ACR nor Client IBNR included in FGU)

Own Incurred should be set to Incurred + ACR + ACR LAE (if Client IBNR and Client IBNR LAE entry codes are null) (ACR included in FGU, Client IBNR is not included)

Otherwise set Own Incurred to Incurred + ACR + ACR LAE + Client IBNR + Client IBNR LAE  (both ACR and Client IBNR included in FGU)

Workaround:
Create new advisory

Root Cause:

Extent of Impact:

Impact on Existing Data

Recovery Method for Existing Data Affected

Problem:
Change to claim worksheet payment partner is not saved if worksheet is left in 'open' status.

Solution:
The system should store the change also on open worksheets

Workaround:

Root Cause:

Extent of Impact:

Impact on Existing Data

Recovery Method for Existing Data Affected

Problem:
Abend when adding a third business to a manual claim worksheet although claim is linked to this when worksheet already has existing bookings

Solution:
The user should be allowed to add any or all of the linked businesses to the claim worksheet; all other validations remaining in place

Workaround:
Add all businesses before making any bookings/saving the worksheet
Create separate worksheet for each business

Root Cause:

Extent of Impact:

Impact on Existing Data

Recovery Method for Existing Data Affected

Problem:
ACORD 2016-10 – Willis - Outward Query – Message Structure Errors
Willis have picked us up on a technical rejection within our L4 Query message
Cedent Address issue
Willis are not expecting Cedent Address details to appear within our outward Query Message.

The EBOT Guide is not all that clear on this particular front – but they are probably right. Once they have the Name & DUNS – they need nothing else.

Solution:
Do not copy any Address for Cedent that is being set by the Broker

Workaround:

Root Cause:

Extent of Impact:

Impact on Existing Data

Recovery Method for Existing Data Affected

Problem:
When an FA message is processed a settlement balance group (SBG) is created for all 'accepted' balances. If an Accepted Balance is on a 'Disputed' claim it is omitted from the created SBG; client indicates that this is correct and as expected. However, they expect SICS to raise an error message when this occurs, and they're not receiving any error message.

Solution:
The FAI with the balance on the Disputed claim should be set to Rejected status with a description indicating the reason being the Balance is on a Disputed Claim.

Workaround:

Root Cause:

Extent of Impact:

Impact on Existing Data

Recovery Method for Existing Data Affected

Problem:
Incorrect error triggered 'previous message not closed where an eMessage was processed without creating a worksheet.

Solution:
There should be a test on the status of the eMessage, if it is Processed or Informational and did not create a closed worksheet then it never will. There should not be an error raised on worksheet status in this case. Only if the message were linked to a previous balance and that balance is on an open worksheet should a previous message not closed error be raised.

Workaround:

Root Cause:

Extent of Impact:

Impact on Existing Data

Recovery Method for Existing Data Affected

Problem:
Swap to Worksheet abends for a TA RIP booking on an existing (created via CM) worksheet for FGU with Annuities

Solution:
The system should correctly update and open the worksheet.

Workaround:
If the booking cannot be automatically added (via Process) to the existing Claim Worksheet then the only option is to Close the Claim Worksheet with the Claim Movement bookings only and have the TA RIP book on its own worksheet (which would allow Swap to Worksheet)

Root Cause:
FGU with Annuities parameter for FGU Claims.

Extent of Impact:

Impact on Existing Data

Recovery Method for Existing Data Affected

Problem:
eMessaging is reversing multiple message bookings for a single instalment when the original messages have the same i.e. non-unique sender (broker) and/or Service Provider Reference.

Solution:
While all message references should be unique, clearly they are not. A match should be made against bookings using the message Uuid only as the other references cannot be trusted.

Workaround:

Root Cause:
Non-unique message references (Sender / Service Provider).

Extent of Impact:

Impact on Existing Data

Recovery Method for Existing Data Affected

Problem:
Test Share Rules abend when the <BrokerSharePercentage> is zero,

Solution:
The system should calculate the share as zero and raise the appropriate error message for the rule.

Workaround:

Root Cause:
Invalid message content

Extent of Impact:
Invalid messages being sent from Broker with <BrokerSharePercentage> 0

Impact on Existing Data

Recovery Method for Existing Data Affected

Problem:
If a message contain wrong Tax Code and Amount Code (=not defined in ACORD), validate/process on the message causes Walkback.

Solution:
When a code set item is sent in a message that is not in the current system code set then, with the exception of a rule that should raise this as a problem, other rules should skip processing.

Workaround:
If there is a new ACORD code set which contains the code item in the message then the system code sets should be patched with the new code files for GeneralCodes.xml and AmountCodes.xml as detailed in the eMessaging Setup Document delivered with the eMessaging Server (Documentation).

Override Rule TestForNegativeLossReserves

Root Cause:
TestForNegativeLossReserves rule when an amount item code is not in the SICS code set

Extent of Impact:
TestForNegativeLossReserves rule when an amount item code is not in the SICS code set
This requires sender has No Claim Movement messages checked.

Impact on Existing Data

Recovery Method for Existing Data Affected

Problem:
When business is on Sanction watch list Instalment message is processing without any error message

Solution:
Make sure the message AC0851 only appears once per balance, i.e. if any of the details in a balance belongs to an Insured Period with the Sanction Watchlist is selected, then the message AC0851 should appear only once.

In eMessaging the message AC0851 must appear on the Error tab for all types of eMessages, so that the user must overrule this to be able to process the worksheet

Workaround:

Root Cause:

Extent of Impact:

Impact on Existing Data

Recovery Method for Existing Data Affected

Problem:
When Processing an eMessage on a Claim Worksheet that has correct but unlinked Government Tax Bookings then there is no automatic linkage taking place.
Also Apply on a Claim Worksheet is not available when Swap to Worksheet.

Solution:
When accessing (create or edit) a open worksheet (Technical or Claim) from an eMessage via Swap to Worksheet it should be possibly to Apply the worksheet. This will not Save the worksheet or any changes to the database but will Apply the automatic functionality (including validations) to the worksheet. To save any changes to the database the worksheet must be exited via another method than Cancel e.g. UNFI or Change Status and OK.

Workaround:
Open the worksheet from the Claim Ledger rather than Swap to Worksheet.
Make any corrections and then Apply. The message can now be Processed.

Root Cause:

Extent of Impact:

Impact on Existing Data

Recovery Method for Existing Data Affected

Problem:
Tracing from ORP to INW
Solution:
Objects changed from use of VIEW ril AC_RETRO_PAIRING
Workaround:

Root Cause:

Extent of Impact:

Impact on Existing Data

Recovery Method for Existing Data Affected

Problem: The level of business is coming from either the BUS_STURCT_REP (for detail) or from BUSINESS (for balance).

Solution: We need to adjust the balance so that it will not come from business but rather from AC_LEDGER_BALANCE table.

Workaround:

Root Cause:

Extent of Impact:

Impact on Existing Data

Recovery Method for Existing Data Affected

Problem:
Objects fro functional amount missing in net reporting

Solution:

New objects addes

Workaround:

Root Cause:

Extent of Impact:

Impact on Existing Data

Recovery Method for Existing Data Affected

Problem:
Missing objects for Functional Amount in XOL Net Reporting
Solution:

New objects for functional amount on INW and OCC

Workaround:

Root Cause:

Extent of Impact:

Impact on Existing Data

Recovery Method for Existing Data Affected

Problem:
UE to be extracted

Solution:

View to support OCC and ORP
Workaround:

Root Cause:

Extent of Impact:

Impact on Existing Data

Recovery Method for Existing Data Affected

Problem:

When in the Main universe a user highlights the Object Booking Year Period - Local and a tool tip appears that reads 'This object should not be used in a condition as the response time will be long. Instead should the year and the period object be used as a condition object.'

This should be removed as accounting reports around the world use the Booking Year Period - Local in condtions and there is no difference in perfomrace if using booking Year & Period.

As this is a VERY OLD tool tip suggest it to be removed in next release.

See attached screenshot

Solution: In the Object Booking Year Period - Local tip that reads 'This object should not be used in a condition as the response time will be long. Instead should the year and the period object be used as a condition object.' should be removed

Workaround:

Root Cause:

Extent of Impact:

Impact on Existing Data

Recovery Method for Existing Data Affected

Problem:
User when creating Inward business via Webservices is presented an error BS0371 - Domain Restriction Business Structure which prevents creating inward business even when user has user role supporting this action.

Solution:

Fix problem when 2 or more roles are assigned.

Workaround:

Root Cause:

Extent of Impact:

Impact on Existing Data

Recovery Method for Existing Data Affected

Problem:
System fails to apply rate to domain restriction limit when considering if booking exceeds threshold amount

Solution:
The booking must be converted into Domain Restriction currency (or Domain Restriction amount must be converted into booking currency) using latest rate of exchange when considering if threshold amount is exceeded

Workaround:

Root Cause:

Extent of Impact:

Impact on Existing Data

Recovery Method for Existing Data Affected

Problem:
The Claim Threshold Domain Restriction is not being raised correctly when a Technical Worksheet detail is being booked with an opposite sign than entry code definition.

Solution:
The system should validate that the details in the technical worksheet for the entry codes covered by the Domain Restriction is greater or smaller than the specified amount. (Allowed range is -amount to +amount)

Workaround:

Root Cause:

Extent of Impact:

Impact on Existing Data

Recovery Method for Existing Data Affected

Problem:
Assumed business could not be renewed by Web Service when it has an inactive business partner, even if has an active merger parent business partner.

Solution:
Renewal by Web Service should be able to replace the inactive business partner with its active merger parent on the new insured period.

Workaround:
Affected Business could be renewed online from SICS online workstation.

Root Cause:

Extent of Impact:

Impact on Existing Data

Recovery Method for Existing Data Affected

Problem:
SICS does not make bookings through SOAP when creating a Technical Worksheet on a Business with multiple Insured Periods if the element <amendmentNumber>0</amendmentNumber> is included in the accountingDetailBalanceEntry

Solution:
If it is required to specify an amendment number on a TW that is not the latest active (default) to book on then the element specified in the SOAP booking for amendmentNumber should be used to populate the booking detail AFTER the IP has been explicitly set from said SOAP. i.e. should have been booked along with setting of Section etc.

Workaround:
Do not include amendmentNumber in SOAP.

Root Cause:

Extent of Impact:

Impact on Existing Data

Recovery Method for Existing Data Affected

Problem:
Some system parameter labels are getting cut off, no matter what dimensions the parameter window is. See highlighted fields below; size of label needs to be enlarged (or adjusted for all Windows GUI standards).

GUI can be found in System Parameters > Claims > Claim Classifications.

Note: Have also noted this issue on other system parameter GUIs; e.g., System Parameters > Claims > Claim Accounting > Premium Must Come Before the Loss Amount on Facultative Business, where '...Business' is cut off. Suggest that all GUI fields in System Parameters be reviewed for cut off labels.

Solution:
Fix the Width and alignment of the mentioned fields in System parameter screens

Workaround:

Root Cause:

Extent of Impact:

Impact on Existing Data

Recovery Method for Existing Data Affected

Problem:
Migrating Facultative protections, which has renewed periods for each period of Inward, by Migration Tool Kit abends.

Solution:
It should be possible to load proportional facultative protections with several insured periods (renewed)  via Migration Tool Kit without any abend. 

Workaround:

Root Cause:

Extent of Impact:

Impact on Existing Data

Recovery Method for Existing Data Affected

Problem:
Insurable Object/ Person
General/ Aliases: Former name entered is not visible when saving - need refresh to be visible

Solution:
Insurable Object/ Person
When entering a Former name in General /Aliases, the system should display the former name entered once saving. The user should not have to refresh the window to be able to see the name

Workaround:
Refresh the window

Root Cause:

Extent of Impact:

Impact on Existing Data

Recovery Method for Existing Data Affected

Problem:
When making changes to the clauses conditions of a contract, the system does not show the log details of this in the log view.

Solution:
When the Log Activities has been activated, and the user updates Clauses Conditions on an existing contract, the system should log this and show it in the Log View window of these Clauses Conditions.  

Workaround:

Root Cause:

Extent of Impact:

Impact on Existing Data

Recovery Method for Existing Data Affected

Problem:
On Find: Business Partner window, when searching for Business Partner by entering both ID/Type and Business Partner Group. search results in abend.

Solution:
On Find Business Partner screen
SICS must not abend when searching for Business Partner using simultaneously Identifier and Business Partner Group. System must return correct results which match both of the defined search criteria.

Workaround:
Search can be performed using either of SICS Identifier or Business Partner Group. Among the list of search results, desired Business Partner can be located.

Root Cause:

Extent of Impact:

Impact on Existing Data

Recovery Method for Existing Data Affected

Problem:
Minor typo in SICS message SICS0007; should be 'specify', not 'speficy'. See Attachment.

Solution:
Fix the NLS Strings in com.csc.sics.migration.bp.SicsAbstractDataLoaderBp

Workaround:

Root Cause:

Extent of Impact:

Impact on Existing Data

Recovery Method for Existing Data Affected

Problem:
Save to Spreadsheet produces Files without extensions

https://bugs.eclipse.org/bugs/show_bug.cgi?id=576984

Since version 4.20 the FileDialog(shell, SWT.SAVE) doesn't add an extension to a file name displayed in the dialog.
This problem occurs only if the set file name does not have an extension. Till version 4.19 the extension of the chosen filter index has been added automatically.

Solution:
Third Party Library corrected and included in SICS 21.1
3plib/win64/org.eclipse.swt.win32.win32.x86_64-3.118.0.jar

Workaround:
Add extension in file name

Root Cause:

Extent of Impact:

Impact on Existing Data

Recovery Method for Existing Data Affected

Aim of function

• Enhance the Profit Commission conditions with Profit Carried Forward (Experience Account) information. 
• The new fields are applicable for both assumed and outward businesses and is pure informational fields without any functional impact. 
• This makes it possible to capture also the information about profit to be carried forward and for how long.  

System Parameters Affected

N/A

Existing functionality affected

Create and View Profit Commission Conditions online

Create and Update Profit Commission Conditions through web services createProfitCommission and updateProfitCommission 

Aim of function

Possibility to split MANUAL Estimate bookings into separate balances for Liquid and Non-Liquid details. The balances with Liquid details will then be set to Unsettled, and the balances with Non-Liquid details will be set automatically to Settled

System Parameters Affected

New system parameter; Split Estimate Balances on Liquid / Non Liquid for manual bookings

Existing functionality affected

When the new system parameter is selected and the user make a manual booking on the Estimates tab on the technical worksheet, the system will separate Liquid and Non-Liquid details in separate balances, additional to existing balance split options on the worksheet, and when the worksheet is applied to the database the system will set the Non-Liquid balance automatically to Settled, because the balance is zero.

 Aim of function

On the Find Accounting Worksheet window, on the Special tab, 4 new fields shall be visible and enabled if the Type of worksheet is either Claim or Technical (else disabled), named Type of Business, Level of Business, Accounting Year and Accounting Period. By those search criteria on the Find Accounting Worksheet it will be possible to narrow down the search result to easy the identifying of the wanted Worksheets/Balances

System Parameters Affected
 
N/A
 
Existing functionality affected

Four filters were added to Find Accounting Worksheet window
 

Aim of function

For Assumed Proportional Treaty and Assumed Proportional Facultative Business, for Technical Worksheet, when the user adds the first Booking row to the Worksheet, the (External) Receive Date given on the worksheet will populate the Due Date for this detail. This function should override the rules for how the Due Date is set for the first detail and it must be driven by a new system parameter.  

System Parameters Affected

A new system parameter named Set Due Date from Received Date on Technical Worksheet, is found under Accounting, Worksheet page 

Existing functionality affected

The system overrides the existing logic for how to set the Due Date so that the Due Date is taken from the Received date on the worksheet (named Received External if the system parameter 'Is Received Internal Date On Worksheet In Use' is selected). The given Due Date is still editable and can be overruled. For the subsequent details added on the worksheet the system will follow existing functionality and copy the Due Date from previous row.
It is only when the user creates the first row on the worksheet that the Due Date shall be taken from the Received Date, so if the Received Date is changed after the first row is created the defaulted/overruled Due Date will not be changed.

Aim of function

Some reinsurance contracts include a provision allowing the cedent or both the cedent and reinsurer to bring the reinsurance contract to an end prior to its natural expiry. By capturing special termination clauses, the parties are better equipped to assess the business risk of the agreement and to give proper notification in case such events occur.

SICS now offers the possibility to enter the Special Termination Clauses not only for treaty business, but also for the other Types of Business.  In addition, these clauses now also includes 2 more trigger types:

• Capital Reduction
• Obligation to Inform Client

Finally, the maximum for Number of Trigger Types Required has been increased to 6.

 System Parameters Affected

None

Existing functionality affected

Maintain Cancellation Condition Special Termination Clauses
Create New Business
Update Business
Change Business Life Cycle Status
Renew Business 
Manage Security
Create Cancellation Conditions by Web Service
Update Cancellation by Web Service

Aim of function

Regulations to protect access to personal data  and sensitive personal data is implemented in many jurisdictions, for example through European Union General Data Protection Regulation. In SICS however, the data in fields which may contain such information  has not been protected, but available to all. 

This enhancement introduces a possibility to protect data in maintained in 'Short Description', 'Signature Notes', and 'Claimant Name', and 'Insured Name'; and also in emessaging  Claim Movement 'Loss Description', 'Claimant', 'Insured'.

When functionality is in use, users can be granted access to view information in the otherwise protected fields, for specific jurisdictions (a new Data Protection Country Group) and if required the profit centre assigned to an Insured Period. 

System Parameters affected

New parameters in Claims - Claim Data Protection

Existing functionality affected

Security Handling

View Claims 

View Message Highlights

View Message Properties

View Message Rendered View

Aim of function:
Option to produce document from a Headline. The document supports some of the basic Headline Loss Properties, and also enables retrieval of claim bookings per currency, as a summary. There are no details of linked claims as such. 

System Parameters affected:
New document type

Existing functionality:
Headline Loss

Aim of function
Display the Base Company name in Find Claims when search option is selected as 'Business Identifier'

System Parameters affected:
None

Existing functionality affected
Find Claims

Aim of function

To change the default Remittance Type for B2B Remittances

System Parameters Affected

eMessaging- Processing Options - Default Remittance Type

Existing functionality affected

Previously the system was used to generate the default payment type for remittances

Now, using Default Remittance type parameter system will generate the selected option as the payment type 

Aim of function:
Claim figures on proportional treaty quota share are reported both in Claim Movement messages and in Statement. If the claim is created with the default claim disposition of 'Accepted' this may result in double booking. This enhancement will add a new rule which will default the claim disposition to 'Informational ' on new claims on Proportional Treaty Quota Share insured periods.

System Parameters affected:
New (pre-apply) rule on Message Type layer in eMessaging.

Existing functionality
Process ClaimMovement message New Claim

Aim of function

Added an option to Reject an eMessaging message.

Option to Save With Rejection Acknowledgement.

When selected, a L4 Acknowledgement Reject message is generated.

System Parameters Affected

None

Existing functionality affected

Process eMessaging messages

Aim of function
Added support for converting booked amounts to estimate currency using the Daily Rate valid at IP Creation Date,. Applicable to Underwriters Estimates calculation, Period Estimate calculation and Multi GAAP Accounting and Retrocession Orders.
Controlled by new system parameter 'Use IP Creation Date - Daily Rate in UPR/MG Calculation'. and dependent on IP Creation Date being set on Insured Period tab on business.

Also, if Functional Currency on bookings is equal to Estimate Currency, the Functional Currency amount is used to populate amount in Estimate Currency, instead of converting from Original Currency. Controlled by changed system parameter 'Use FC Rate From Source Premiium in UPR/MG Calculation'.

System Parameters Affected

Accounting/Currency/General system parameters:

• New Parameter: 'Use IP Creation Date - Daily Rate in UPR/MG Calculation'
• Existing parameter 'Use FC Rate From Source Premium in UPR Calculation' has changed label to 'Use FC Rate From Source Premium in UPR/MG Calculation'.

Existing functionality affected

• Calculate Pricing/Adjusted Estimates
• Calculate Period Estimates
• Run Multi GAAP Accounting Order
• Run Multi GAAP Retrocession Order