Release documentation - P&C Enhancements and requests

Problem:
Able to Book and close installment without Placement complete for Proportional Facultative

Solution:
Preconditions:
The system parameter Require Complete Registration must be OFF.
When selecting Book and Close Selected Instalment on the Premium Accounting window, on a Facultative OCC with the Placement Completed NOT set, the system must prevent the user from doing this operation.

Workaround:
Activate the system parameter Require Complete Registration under Business, Conditions, Miscellaneous.
With this parameter ON, it is not possible to book instalment before Registration Complete is set on the business, and to set this you must first set Placement Complete. So it is a workaround to activate the registration complete parameter to avoid this problem.

Problem:
Abend on TW and CW after selecting 'view blance changes' without any bookings

Solution:
The View Balance Changes option shall only be enabled when at least ONE balance exists on the worksheet. Keep the option disabled as long as there are no balances to display on the view worksheet closing window. Both for TW and CW.

Workaround:
Instead of using View Balance Changes it is also possible to select the option Change Status to open the worksheet closing window to inspect the balances, and from there go back to the worksheet in edit mode to continue the bookings.

Problem:

The Booking Year/Period of the Portfolio Entry in Account Currency is not the same as that of the source balance in Booking Currency.

Solution:

The Booking Year/Period of portfolio entries in Account Currency should be the same as the Booking Year/Period in Booking Currency when the Same as Booking is selected in the Retrocession Account Order, which should not be affected by the Booking Terms in the base company specific setting.

Problem:

Execution of Recovery calculation order is taking too long time compared to previous SICS version (SICS 4.8.5).

Solution:

Improve the performance of recovery calculation order by enhancing the database view AC_DETAIL_BALANCE 

Problem:

When Database is common and System parameter “Enable Summary Account on Technical Worksheet” is enable in Life area, SICS behave incorrect for SICS P&C environment. 

Solution:

When System Parameter “Enable Summary Account on Technical Worksheet” is activated via SICS Life then SICS functionality should not impact both (P&C and Life) environment. This system parameter should only applicable for Life area (even If it is Common Database). 
It should reset accounting Year/Period according to Admin condition as per existing functionality in both area. (P&C and Life)

Workaround:
Turn OFF the System Parameter from the Life Database then SICS will behave as expected OR manually enter the Accounting Year/Period on the details of booking. 

Problem:
Not able to do bookings from Premium and Limits tab if Reporting Unit inactive

Solution:
Preconditions:
Booking on Accounting Classification with inactivated Reporting Unit
When the user from Instalment or Adjustment conditions selects the option Book Selected..../Book and Closed Selected...., then the system must allow this operation and not present message BS0030. The system must behave consistent since it is allowed to book on an inactivated Reporting Unit if you book manually or if you book through Instalment or Adjustment orders.

Problem:
Entry Code Transformation doesn't work correctly when removing/attaching an OCC to an IAB

Solution:
Precondition:
You have a Fac OCC protecting an Assumed Business and this Fac OCC has an Entry Code Transformation Term saying that an entry code shall be suppressed and not booked on the Fac OCC when it comes from the AB.
When you have made bookings on the AB with this entry code it is correctly not booked on the Fac OCC.
But if you remove this Fac OCC from the Proportional Protection on the AB, and later add this Fac OCC back on the PP on the AB, so that retroactive correction bookings take place on the Fac OCC, we must make sure the system also in this proecess suppress this entry code so that it is not booked on the Fac OCC.

In this version, 23.3, we have only fixed the problem when the Fac OCC is removed from the PP on the AB. In 23.4 we will also fix the problem when the Fac OCC is added on the PP on the AB.

In SICS Cede, the same should be the case when Proportional Protection is changed on a Policy Cede.

NB! The Entry Code Transformation Term shall not be defined on the Assumed Business itself. Booking on an Assumed Business with ECTT may be affected by this ECTT on the bookings are retroceded to Facultative OCC, but that is wrong and will be corrected in a separate case in a future release. The ECTT must be defined on the Facultative OCC itself if it shall affect when the bookings are retroceded to the Fac OCC.

Problem:
Expected Payment remains after mass pairing of technical/claim balances (AC0013)

Solution:
Preconditions:
System Parameter 'Always keep Expected Payment Balance after Pairing' is NOT selected
When mass pairing or the mass pairing of Tech/Claim balances is executed and pairing takes place between two balances of same currency and the balances have Expected Payment balances in different currency than the pairing currency (the driving balance currency), then the system shall complete the pairing as it does currently, but the system must also delete the Expected Payment balances for the actual involved balances. This is the same as if you reply Yes to the message AC0013 when trying to do the same pairing manually.
If the above parameter is SELECTED, then the system shall always keep the Expected Payment balances both for manual pairing and mass pairing.

Problem:
TAWV - AC0399 instead of AC0839 triggered when booking Reinstatement Premium on TW where RIP condition is not active

Solution:
When booking Reinstatement Premium on an Insured Period with Technical Validation Indicator that contains a validation template with a validation rule for Reinstatement Premium and with Attribute on Conditions 'Compare Worksheet Type with RIP Calculation', then the rule correctly trigger validation error message AC0839 (Compare Worksheet error) if the Reinstatement Condition is defined as Specific and the Calculation Rule is empty, is defined as NONE or the defined as Per Loss.
But the error message must also be triggered if the Reinstatement Condition is NOT defined at all.

Workaround:
None

Root Cause:
Validation rule implemented in version 21.1 according to enhancement case SE-4446

Problem:

Performance issue when running Recovery Calculation for Protection Program

Solution:

Improve the performance of recovery calculation order by enhancing the database view AC_DETAIL_BALANCE

Problem:

The Reporting Unit filter on the open worksheet mass update order not looking at the exact RU of the UWY of the authorized worksheets.

Solution:

In the Open Worksheet Mass Update order, when the user have some extraction criteria e.g. Reporting Unit, and selects the option List Open Worksheets, then the system must check all Insured Periods, not only the last IP, and list all worksheets with a link to any Insured Period if at least one IP matching the extraction criteria.

Root Cause:

The List Open Worksheet option on the Open Worksheet Mass Update order has always only looked at the LATEST Insured Period to find match according to the extraction criteria given on the order.

Problem:
TAWV- Automatic booking functionality for Deductions generates Tax on Premium deduction for RIP booking

Solution:
When the user selects the option Automatic Booking of Deduction on Technical Worksheet and there are details with entry codes in the Entry Code Sub Category 'Reinstatement Premium' on the worksheet which are also included in the Entry Code Group used as basis for the calculation of these deductions, the system shall still exclude all details with entry codes in that EC Sub Category in the calculation of deductions.

Problem:
UGLOE split when different FX details

Solution:
When a general Functional Currency Exchange Rule is defined for a Worksheet Type and Exchange Rate Category, it is also possible to define a specific rule including Type of Business and Entry Code. If such a specific rule is defined it must be mandadory to define both one Type of Business and one or more Entry Codes.

Problem:
Reason is shown instead of Pairing ID on notes field after Mass Pairing for TW/CW is done successfully

Solution:
When running the Mass Pairing of Technical/Claim Balances order and balance pairing takes place between two balances, the system shall write a new Notes text below the existing text found in the Notes in the following way (example):
Date and time: 2022-09-13-10:39:20
Order ID: AO4000
Status : Paired
Matches: TW/2022/1227912
Pairing ID: GP'2022'100002

Root Cause:
Wrong implementation of how to set Notes in enhancement case SE-9765 in 23.1

Problem:
Cannot add attachements on SICS from Techincal workheet properties window

Solution:
When a Technical or Claim Worksheet is created and applied to the database, there is a menu button option named Attachments. By selecting this the system opens the Attachments window where the user can view and add new attachments. When selecting the option New from file... or New from DMS..., the system must allow to do so and not present the message 'SICS0008-Only One Edit Window Allowed'

Workaround:
From the worksheet closing window, even on open worksheets, you can add attachments

Problem:
The 'Authorized' status claim worksheets registered in SBG can update to 'Inactive' status.

Solution:
1. When the user selects the option Inactive from the Menu button on the Worksheet details window and this worksheet contains a balance that is part of a Settlement Balance Group, the system must also raise the message ACBP034 and prevent the user from doing this in the same way as if the user change status to Inactive on the worksheet closing window. Both on Technical and Claim worksheet.
2. When the user from the Open Worksheet Mass Update order selects the option Inactive or Inactive Selected and one or more of the worksheets contain balance(s) that are part of Settlement Balance Group(s), the system must also here raise the message ACBP034 and stop the process. In case some worksheets allowed to be Inactived, have been inactivated, shall remain Inactive. Both for Technical and Claim worksheets.

Root Cause:
SE-10707 in 23.1

Problem:
Inactivated worksheet types are still shown and selectable in worksheet closing window if current status is Authorized

Solution:
When worksheet statuses Rejected and/or Suspended are inactivated in the reference table 168 Worksheet Status, and the system parameter Advanced use of Worksheet Status is selected, then the system must disable/hide these two statuses on the worksheet closing window in the Change to drop down field, even if the current status is Authorized. This must be the case both on Technical and Claim worksheet.

The above is limited to these two statuses, i.e. the system will always show Closed, Inactivated and Authorized, even if they are inactivated.

Problem:
Incorrect calculation of common account XLCA premium to Proportional retrocessionaires when special premium is selected

Solution:
The amounts to be distributed to the Prop Retrocessionaires must consider booked figures for XL ORPs when special premium - not retroceding figures premium booked at OCC level.
Example: 100% booked at XLCA: 63.500, while total booked on two ORPs is 64.450, considering special premium. 100% basis for retrocession must then be 64.450.

Make sure that Instalment Premium, Adjustment Premium and Reinstatement Premium Order is correctly handled when special premium

Workaround:
None

Problem:
SE9765#10 Some Booking data of inactive BP is paired even though checked 'Exclude inactive business Partners'

Solution:
When the 'Exclude Inactive Business Partners ' is checked while running Mass Pairing of Technical/Claim Balances order the system must check ALL the involved balances, both Driving and Included balance, and if any of the two balances to be paired is marked Inactive (the Active flag is unticked) the system must exclude these two balances to be paired. In other words, the system shall only pair balances if the Business Partner on BOTH balances are set as Active.

Root Cause:
Missing from the implementation of enhancement SE-19018 in 23.2

Problem:
IGC Accounting registered with wrong Access Code

Solution:
Precondition:
The system parameter Segregate Data by Access Code is activated.
When Intra Group Contract bookings takes place on an IAB, coming from a prop or non-prop ORP, then the Access Code on the source booking on the ORP shall NOT be copied over to the IGC IAB, but instead the Access Code shall be taken from the Base Company (Reinsurer) on the IGC IAB itself. This should be the case for all places where the access code is set on the booking; AC_WORKSHEET.FRK_ACCESS_CODE, AC_LEDGER_BALANCE.FRK_ACCESS_CODE and AC_LEDGER_DETAIL.FRK_ACCESS_CODE.

If the above system parameter is NOT selected then the Access Code shall not be set on the IGC IAB booking (same as on the ORP booking).

Problem:

System administration / System Parameter & Maintenance / Database & System:
Base Company Segregation: selected

With the above parameter is set, and the User is assigned few base companies, the user is still able to find worksheets which do not belong to assigned base companies.

Solution:

When the parameter Base Company Segregation is set to Selected, on Find Accounting Worksheets, when the user wants to change or add more base companies and from here open the Find Business Partner, the system:

• Should find the Owner Group of the Current Base Company. Then it should use the intersection of this Owner Group and my Allowed Base Companies.  
• If my the Current Base Company is not part of any owner group, the user can only select his/her own Current Base Company.

Problem:

Performance issue shows a very long runtime AGAIN of running UW estimates, Recalculation and Accounting Orders. We need assistance looking into asap.

Identified issue: Batch reading that was added on estimation item and single estimates are causing performance issues on estimation orders.

Solution:

The Batch reading needs to be implemented more efficiently.

For this case, remove batch reading from SicsBusinessPeriodEstimatesConditionClass.addRelationshipMapping(ClassBasedTableDescriptorBuilder).

Problem:

Not generate new item in IGC IAB 'AC' condition during intercompany Transfer

Solution:

In case the Base Company on both the IGC IAB and the IGC ORP has mandatory reference data, e.g. Sub Class of Business or Origin of Business, and the AC in the booking from the ORP contains a SCoB or OoB value that do not exist on the IAB, then the system shall still use the value from the source AC and set the AC Invalid on the AB.

The above is independent if the booking takes place on the Main Section or Sub Section on the IGC ORP/IGC IAB, and also independent if the system parameter Make Valid AC from AB on Intra Group Contract bookings is selected or not.

Currently it is correct if the booking takes place on the Main Section, but not on Sub Sections.

Problem:
When booking a Premium without any expected deduction and an Accounting validation / accuracy error is raised (on missing bookings) it is no longer possible to override on the Premium booking as any override and comment is not considered and the error is still raised.

Solution:
When overriding a base detail for Accounting Accuracy Validation this should work as before and not raise the validation error.

Workaround:
Add 0 bookings for missing details and add an override on those.

Problem:
Bug 1550210: GOV TAX - SICS 23.1 SP4 - TECSNT02: Automatic Booking Gov Tax not consistent if Target EC switch sign checked

Solution:
When Automatic Booking of Government Tax is selected on a Worksheet and the GT Rule has the Switch Sign selected for the GT Target Entry Code, then the system correctly switch the sign to be opposite of the sign in the EC properties. But if you again select the Automatic Booking of Government Tax the system must also use the Switch Sign flag in the rule when the GT Target amount is calculated.

Workaround:
The GT Target detail must be deleted before the Automatic Booking of Government Tax is selected for the second time.

Root Cause:
The Switch Sign functionality in the GT Rule were implemented in 23.1 by SE-15373

Problem:

As Original on outward Cedent's Contract gets lower WS ID number than source booking

Solution:

When booking of Installments or Adjustments takes place on an Assumed Business, from the Premium and Limit conditions with the option Book and Close Selected, then the system should follow the same logic for how to allocate Worksheet IDs as when bookings are done manually on the Assumed Business; First give Worksheet ID to the worksheet on the Assumed Business, then give Worksheet ID to the worksheets on the outward business, e.g. Treaty OCC. The Worksheet IDs series number on the Assumed Business must be before the series number on the OCC.

Workaround:

Just ignore the strange settings of the series numbers on the worksheets

Root Cause:

Always been like this since we implemented the the Book and Close Selected on installment conditions.

Extent of Impact:

No known impact since the series numbers of the worksheets have no special effect other than that it look a bit strange.

Recovery Method for Existing Data Affected

Not needed.

Problem:
Error message on Classification tab for IGC1028510 - 2020

Solution:
Preconditions:
The system parameter 'Allow only One Type of Participation', is switched OFF.
On an IGC IAB business, when the user changes the Classification, and the user is trying to add more than one Type of Participation (method), this must be allowed and the message BR0128 shall not appear when the ToPs matches the ToPs on the source ORP business. The message BR0128 shall appear only when the added ToP does NOT match the ToPs on the source ORP business.

Problem:
Open TWS screen - unable to navigate to Worksheet - Validation error

Solution:
Preconditions:
System parameter Advanced Use of Worksheet Status is ON
When a worksheet in status Authorized is to be opened by the user the system will navigate directly to the worksheet closing window. In this case the system shall raise AC0850 - 'The worksheet cannot be closed directly but have to be opened in edit mode to check the accuracy validation errors.' only if there are Accuracy Validation Errors on the worksheet that has not been overuled by the user. If no such validation errors exists on the worksheet, then the system shall not raise AC0850.

Problem:
The balance with the expected payment balance is missing from the BPL when the balance pairing group is annulled.

Solution:
When the system parameter Always keep Expected Payment Balance after Pairingthis is selected the Expected payment shall be kept even if the driving balance in the pairing is in different currency than the Expected Payment. If this parameter is not selected, then the Expected Payment balance shall be deleted if the driving balance is in a different currency than the Expected Payment. But shall always be kept after balance pairing if the driving balance is in same currency as the Expected Payment.
When balance pairing takes place between a driving balance and an included balance with an Expected Payment, is that the Settlement Indicator on the original balance and the Expected Payment balance shall always be in sync, i.e. if the balance is Settled then the linked Expected Payment balance shall also be Settled, etc.
The above shall be followed independent of how the pairing takes place; i.e. if it is a normal manual pairing, pairing group or any mass pairing.

Problem:
Abend on OCC Business Ledger when trying to 'Calculate' Account Balances Summary for 'As Informational' bookings

Solution:
When opening the ledger on a prop/non-prop treaty OCC or ORP, and select As Informational view on the Account Balances Summary tab and click one of the Calculate button, the system shall not abend but only shows the sums for the As Informational bookings if there are some, else show nothing.

Problem:
Open Worksheets on OCC retroceded to ORP when running the Retro Calculation order

Solution:
When the Import Technical Worksheet from Column Spreadsheet function is executed and the Select Import Worksheet window is opened, these worksheets are already committed to the database. Therefore, the system must do some special arrangements if there are details and balances to be booked on Prop Treaty OCCs. For bookings to be done on Prop Treaty OCCs the following values must be set on 3 column on the Balances (ac_ledger_balance);
the ac_ledger_balance.is_in_orig_curr must be set to True (Y)
the ac_ledger_balance.is_in_book_curr and ac_ledger_balance.is_in_acct_curr must be set to False (N).

By doing the above the user will see these bookings on the As Original ledger for the OCC and these bookings will only be included in the Retrocession Calculation order after the worksheets for these bookings are Closed.

Workaround:
Open each of the worksheets that are uploaded from the spreadsheet to have the As Original flag set correctly and do not run the retrocession calculation order before this is done.

Problem:
PA change on the amendment wrongly triggers SYN0029 (Sompo: RE0099)

Solution:
When Protection Assignment is changed on an Assumed Business so that retroactive correction bookings are to be created on the involved outward businesses, e.g. on a Proportional Treaty OCC, then the system shall set the Booking Date equal the current date on all the correction bookings. This will prevent the syntax error SYN0029 to stop the booking.

Problem:

Estimate Settlement Indicator Mass Update order for 2022 updates flag on balances for 2023

Solution:

'Estimate Settlement Indicator Mass Update' order should execute the process those businesses matches the described classification criteria in the order. If any of the criteria doesn't match with the listed business, Order should not update the settlement Indicator.  

Problem:

Abend while Running Estimate and Accruals Order

Solution:

Accrual Accounting Order should not abend when any of the listed business have Cease accounting flag selected.  If Business already added in the Order list and then 'Cease Accounting' Flag is selected in the business and User execute the Order. Order should not create any worksheet those have 'Cease Accounting' Flag selected. 

 Workaround:

Exclude those business where 'Cease Accounting Flag' has been selected. 

Problem:
Manage the ESPID tables at sub section level

Solution:
When booking Instalments/Adjustments on a non-prop with Instalments/Adjustment registered on sub sections with AC Split defined from ESPID table, the system shall book and split according the AC Split percentages on the actual section and NOT use the split percentages accross the sections. The sections must be treated separately.

Workaround:
Keep all classifications on main section, create the total instalments on the main section and make the ESPID table including all the Accounting Classifications.

Problem:

Performance issue shows a very long runtime AGAIN of running UW estimates, Recalculation and Accounting Orders. We need assistance looking into asap.

Identified issue: Batch reading that was added on estimation item and single estimates are causing performance issues on estimation orders.

Solution:

The Batch reading needs to be implemented more efficiently.

For this case, remove batch reading from SicsBusinessPeriodEstimatesConditionClass.addRelationshipMapping(ClassBasedTableDescriptorBuilder).

Problem:
This is the side effect of SE-10707 implemented in SICS23.1.
1) When the claim is created in Authorized status and add to a SBG, system allows to remove the claim id on the worksheet without error and the SBG amount after removing the claim id is not getting adjusted.

2) No error(ACBP034) triggered when changing AC on CW with Authorized status included in SBG.

Solution:

1) When the system parameter ' Allow Balances in Authorized Status in Settlement Balance Group' is ON and a Settlement balance group is created for the Authorized claim worksheets, then system should not allow to remove a claim which is a part of SBG. 
When user tried to 'Remove Claim' then system must raise the message ACBP034.

2) When the system parameter 'Allow Balances in Authorized Status in Settlement Balance Group' is ON and 'Display Bookings and Entry Codes per Accounting Classification' is Selected, and a Claim Worksheet is created with one AC in Authorized status and included in SBG then system should not allow to change the AC on the claim worksheet and should trigger ACBP034 error.

Problem:
Able to update the expected payment amount for the worksheet which is included in SBG and in authorized status.

Solution:
SICS should raise a validation message AC0256 when modifying expected Payment amount of Expected Payment Balance which is part of Settlement Balance group, in the same way SICS correctly validates for when modifying expected Payment currency

Problem:

System is throwing an abend when trying to Switch currency on Technical Worksheet with Authorized which is a part of SBG.

Solution:

When the system parameter ' Allow Balances in Authorized Status in Settlement Balance Group' is ON and a Settlement balance group is created for the Authorized Technical worksheet, and now user tries to 'Switch currency on all details' on worksheet then system should not allow to switch currency and Validation Error ACBP034 should be triggered and there should not be any abend.

For Claim worksheet it is working correctly, TW should also work similarly.

Problem:
Incorrect Deduction Amount Using Automatic Gross Up of Premium & Deduction Booking

Solution:
When the option 'Automatic Gross-up of Premium and Booking of Deduction' is selected on a Technical Worksheet, and the worksheet contains two premium details that are basis for the calculation of deduction, the system must make sure the two premium details are handled separated and that the calculated deductions. If the Deduction details can be merged together this must take place after they have been separately calculated.

We must also make sure the system does not abend if the same worksheet is reopened and the user performs again the 'Automatic Gross-up of Premium and Booking of Deduction' .

Problem:

System is stopping to 'Add Business' on worksheet with Authorized status which is part of SBG and also restricting from 'Add a New Entry Code' on the business which is not part of SBG, triggering and error ACBP034.

Solution: 

When the system parameter ' Allow Balances in Authorized Status in Settlement Balance Group' is ON and a Settlement balance group is created for the Authorized Worksheet, and now user tries to 'Add Business' system should allow to add a new business and also should allow to add a new Entry Code on the Business which is not part of SBG (as the new balance will not be part of SBG).

Problem:

The expected payment is deleted from the balance during balance pairing group when driving balance currency is different from expected payment currency even if system parameter Always keep Expected Payment Balance after Pairing is selected.

Solution:

Make same solution as in SICSR-27234 also for Balance Pairing Group:

When the system parameter Always keep Expected Payment Balance after Pairing is selected the Expected payment shall be kept even if the driving balances in the Balance Pairing Group is in different currency than the Expected Payment.

If this parameter is not selected, then the Expected Payment balance shall be deleted if the driving balance is in a different currency than the Expected Payment. But shall always be kept after Balance Pairing Group if the driving balances is in same currency as the Expected Payment.

When Balance Pairing Group takes place between multiple driving balance and included balances with an Expected Payment, then make sure the Settlement Indicator on the original balance and the Expected Payment balance shall always be in sync, i.e. if the balance is Settled then the linked Expected Payment balance shall also be Settled, etc.

Problem:
System is stopping to 'Add New Booking' on Claim worksheet which is part of SBG.

Solution:
When the system parameter ' Allow Balances in Authorized Status in Settlement Balance Group' is ON and a Settlement balance group is created for the Authorized Claim worksheet, and now user tries to 'Add New Booking' system should allow to add a new balance as the new balance will not be part of SBG.

Problem:
System is stopping to 'Add New Booking' on Claim worksheet which is part of SBG and when trying to delete the booking, system abends.

Solution:
When the system parameter ' Allow Balances in Authorized Status in Settlement Balance Group' is ON and a Settlement balance group is created for the Authorized Claim worksheet, and now user tries to 'Add New Booking' system should allow to add a new balance as the new balance will not be part of SBG and when trying to delete the new booking which is not part of SBG, system should not abend and should allow to delete the booking.

Problem:

When user Annulled Pairing ID in the Mass Pairing of Technical/Claim Balances and Pair the same balances again, then Log is not updated correctly with the latest Pairing ID.

Solution:

When the system parameter ' Balance Pairing Group in use ' is ON and the Balances are paired using the order 'Mass Pairing of Technical/Claim Balances'. Now Annulled this Pairing ID and when user tries to Pair the same balances using the order 'Mass Pairing of Technical/Claim Balances', the Pairing Log should also be updated with the latest Pairing ID same as the Balance Pairing Properties.

Problem:
System is allowing to 'Delete Expected Payment' on Authorized worksheet which is a part of SBG.

Solution:
When the system parameter ' Allow Balances in Authorized Status in Settlement Balance Group' is ON
and a Settlement balance group is created for the Authorized Worksheet, and now user tries to Delete/Modify the Expected Payment Currency/ Expected Payment Amount then system should restrict this by raising a validation message AC0256 - 'This Expected Payment Balance is used in a Settlement or Account Group Balance and cannot be changed. The balance must first be removed from the group.'

Problem:
IN328701 - Walkback on an UNFI worksheet, automatic booking - Automatic Gross-up

Solution:
When you open up a pending worksheet (status Open or Unfi doesn't matter) and then select the option Automatic Gross Up of Premium and Booking of Deductions, then the system must calculate the deductions in the same way as if this calculation takes place on a brand new worksheet, without falling over.

Problem:
ECTT on IAB/OCC work incorrectly when IAB is protected by PF OCC

Solution:
When booking takes place on an Assumed Business, protected by Fac OCC or directly by a Fac ORP, there shall be no effect of Entry Code Transformation Terms defined on the Assumed Business when the bookings are done on the Fac OCC/Fac ORP. The system shall only make use of ECTT if it is defined on the Fac OCC or the Fac ORP itself. We must make sure the ECTT on the Assumed Business is NOT used on the outward bookings at all.

Problem:

When the items Aggregate Limit, Cover or Excess have been set up to be colored as mandatory and they on the contract contain a value, when selecting the item and then Delete, the system gives the message ‘DB0005: Database Session Error The current unit-of-work in the database session is not the expected unit-of-work.’. If selecting OK on this, the system abends.

Solution:

When selecting an items defined to be colored as mandatory and it contains a value, and the user selects Delete, the system should not give the message ‘DB0005: Database Session Error The current unit-of-work in the database session is not the expected unit-of-work.’ And pressing ok to this should not abend. Instead, the delete choice should be disabled, as it currently correctly is when this item does not have a value in it. 

Problem:

Underwriters cannot create or link Inward Intra Group Contract when Current Base Company is not set up as part of any owner group.

Solution:

It should be possible to create an Inward Intra Group Contract even if the Current Base Company is not part of any base company owner group.

Workaround:

A System Administrator, who does not have any Allowed Base Companies assigned in the Security Management, will be allowed to create Intra Group Contracts on any business. 

Problem:
When transforming a Business Partner into a Third Party or a Third party into a Business Partner, and the partner is linked to a base company, the Business Partner/Third Party is only linked to the base company as the partner type it was originally created.

Solution:
When transforming a Business Partner to a Third party or a Third Party to a Business Partner, and the transformed partner is linked to a Base Company either as Linked Business Partner or Linked Insured, the partner should after having been transformed, be shown both in Linked Business Partners and Linked Insured on the Base Company.

Workaround
A system administrator can link the user's Base Company to the Third Party (transformed from a Business Partner). When linked, the Third Party will be visible to the user.

Problem:
'Status' filter is missing from Find Bank.

Solution:
The filters for Status should be available on the Find Banks screen similar to how it is available on the Find Partners and Find Persons screen

Problem:
Instalment Premium calculated wrong first time after removal

Solution:
When the popup menu option Proportional Split Instalments is selected on the Instalment conditions, it must always be based on the Deposit Premium Our Share, also after the instalments have been booked, reversed and removed from the Instalment container. If the Deposit Premium is changed and the user selects Proportional Split Instalments, then it must also be based on the current Deposit Premium Our Share.

Workaround:
Recalculate a second time will create correct instalments

Problem:
No validation of Retroceded Percent of Facultative Retrocessionaire Participation against Intermediary percent

Solution:
When system parameter 'Protection assignment 100% is mandatory' is selected and users book on an Assumed Business protected by Facultative Retrocessionaires the system shall raise the error message AC0075 (booking not allowed, possible reason: not correctly protected) if the sum of retroceded share to OCC, Own Retention and Facultative Retrocessionaire's Participation, does not add up to 100%. In this validation the system must ignore Intermediary Placements.

Workaround:
If an Assumed Business is protected by Intermediary Placement, make sure this placement is assigned 100% Retrocessionaire's Participations before booking takes place on the Assumed Business

Problem:
On an Outward Cedent's Contract's protected assumed businesses list (AB button), the system does not show some businesses, despite them being with base companies in the same owner group as my current base company.

Solution:
On an Outward Cedent's Contract, the system should not hide the protected businesses with base companies in the same owner group as my current base company. Instead, when the Reinsurer is a base company in my Owner Group, these should be shown.

Workaround:
Not really a workaround, but a possibility:
Open the not shown Assumed Business (if the ID is known) from the Find Business. Then open its Protection Assignment (PP). The assigned OCCs are listed.

Problem:
Abend when the expected payment is created on a claim worksheet

Solution:
When opening the Balance Properties for a Balance on a Claim Worksheet and in Edit mode selects the option Create/Edit Expected Payment, and finally save the balance with a new Expected Payment balance, the system must be able to store this, and not abend, in the same way as when this is done for a Balance on a Technical Worksheet.
This must work properly both when there are defined percentages in the Exchange Difference Warning/Error Limit or if these fields are blank

Problem:

Walkback when migrating a claim worksheet

Solution:

ensure that the BusinessObject Id is set correctly so that the claim worksheet is migrated to the correct SocToClaimRel

Problem:

System does not default claim worksheet entry codes as expected

Solution:

When an entry code is flagged to default in a claim worksheet it should automatically appear when creating the first worksheet on the claim.

Workaround:

Add the entry codes manually

Problem

When you have the business stats screen with criteria selection open, and you are viewing the claim ledger, you select and unselect between our share and 100% however the figures do not change.

Solution

The system should recalculate the Claim Ledger figures regardless of whether the Online Statistics Criteria selection window is open or not.
 
Workaround

Close the Criteria Selection window.

Problem:

Claim Accuracy Error AC395 (missing reinstatement) appears when it is not expected. 

Solution:

Accuracy error for reinstatement should not be raised if worksheet does not contain Paid Loss (and possibly Paid Loss Expense) entry codes, nor when booking zero payments, nor when condition is not defined, defined as none or no auto calculation, free, or not available - although adjustments to already booked reinstatement is due.

Problem:

The system does not split ACR to ACR AAD and ACR when total AAD is exhausted

Solution:

The system must allocate towards AAD only as much as is remaining in AAD. The balance must be allocated to the layer, provided the limit is not yet breached.

Problem:

London Market TA Reversal without Due Date results in a reversal booking missing a Due Date which cannot be manually added.

Solution:

For a reversal message missing a due date the due date should be set as the current date with the exception of a Lloyds Delinked reversal which should take the due date from the original booking being reversed.

For any other cases of a missing Due Date the field on the balance is editable and should be set as desired.

Problem:

Issue is with the rule “TestSumOfLiquidDetailsAgainstClaimedSubAccountBalanceValidationRule”

The rule (error) does not prevent processing messages by Swap To Worksheet even if we set 'Halt Processing = Y' in the rule property.
By processing the message by Swap To Worksheet, the booked amount and the amount we acknowledge may not match.

Factory setting of the rule has “Allow Swap To WS = Y”, So it is understandable that Swap To WS is possible on the message. However, by closing the swapped worksheet the message is processed. That causes sending L4 acknowledgement confirming an amount not matching with the booked balance.

The message should not be processed with the error set by this rule.

Correction in SICS 4.9.1
SICSR-14199 - Strange not understandable validation when swap to worksheet

The control amount for CheckLiquidBalanceControlTotal should be set from the message balance amount on all eMessage generated balances. The affects liquid entry codes will be summed across all eMessage generated balances and compared to (one of the identical) control amount.

However even if there is a validation problem with the control amount if UNFI on an Instalment Booking you are prompted to set the message to processed even though the current message is making the booking itself and the worksheet is still open.

Solution:

When UNFI on an Instalment booking worksheet there should be no prompt to set the message to Processed.

Problem:
System Admin cannot close worksheets due to EM0106/security domain restriction issue

Solution:
Preconditions:
System parameter 'Prevent Manual update of technical worksheet' is selected.

For a TechAccount message, when the user has Validated the message and select the Process option, then make sure the message goes directly to Waiting status in the same way as it does when a claim message is processed and the 'Prevent Mandual update of claim worksheet' parameter is selected.

Problem:

CM messages that are Discarded with an Acknowledgement message being sent to the Broker do not meet ACORD standards.

XML:
Problem: Claim/ReinsurerReference not present in XML

In this Story’s scenario, we want a Business Validation ACK going back to the Broker - but we may or may not have a Claim to link the message to. We need the ability to Discard the message from SICS (as it is invalid or we do not wish to process it) and close the messaging loop with the Broker.

Solution:

For Claim/ReinsurerReference or Claim/InsurerReference then
If there is no linked Claim ID (after Validate has been run) - then use the (Re)InsuranceReference from the message.

Problem:

CM closing notice processed, claim not auto-closed when CWS was closed.

Solution:

If a Claim is Pending Closure and eMessaging closes a worksheet via Process or Swap to Worksheet then if the Claim can be closed it should be.

Problem:

InsuredPeriodFromDateValidationRule tolerance does not work if message date is prior to insured period date

Solution:

Date tolerances with lower and upper values should function if the base date is prior or after the reference date using the lower or upper tolerance respestively.

Problem:

ValidateMessageSequence triggered incorrectly.

The validation rule – ValidateMessageSequence – is supposed to outline instances where the current message is prior to the linked adjustment, it compared as of data and if they are equal the creation date. However, if creation date is equal (can likely happen on Lloyds batches) it raises this error which is wrong.

The problem message text states 'Message as of date equals SICS as of date with prior CreationDate'

Solution:

For messages with the same As of Date and CreationDate the ValidateMessageSequence rule should not raise an error.

Problem:

We checked out Conduit scheduler and the 3 Pending delivery messages aren't being picked up. Also, they are displayed as <None> in the external system info. Messages are all Discarded with acknowledged status.

Solution:

When discarding with Acceptance acknowledgement the external system should be set from the original message as per other cases.

Workaround:

 UPDATE EMES_MSG SET FSK_EXT_SYSTEM = 1239, FRK_EXT_SYSTEM = 'GATEWAY' WHERE FRK_EXT_SYSTEM IS NULL; 

Problem:

SICS eMessaging Sample client not working SICS 23.1 and 23.2

Solution:

Axis2 upgrade should be completed fully included in the eMessaging Acord Client executable version.

Workaround:

Requires upgraded axis2 lib to be used by acord-client.
axis2-adb-1.8.2.jar to sample client/lib folder. Then in acord-client.bat add this lib lib/axis2-adb-1.8.2.jar; .

Root Cause:

Upgrade to Axis2

Problem:

For the ACORD version 2015 Settlement message with multiple FAI items, rejected the few of the pending items and processed the message. once processed system has created rejection acknowledgement with no error indicator.System is only generating the error indicator for the acord version 2016-10 messages but not for the other ones.

Solution:

Add ErrorIndicator for ACORD schema 2010 an onwards as per 2016-10 for Settlement FAI Rejections and TA/CM rejections.

Problem:

Abend and/or missing AsOdDate on Claim Worksheet when making a booking from a message that does not include an AsOfDate.

Solution:

Ensure that if no AsOfDate is provided in a message then the CreationDate of the message is used to set the AsOfDate.

Problem:
The original message is booked in M04. M04 is then closed.
A Reversal message arrives and sets booking period to M04 when the message is processed or if the user swaps to worksheet to Process.
The user does not have access to closed periods and the user is not warned. The booking is made in the closed period.
If the user reverses the worksheet from the business ledger M04 is the booking period but when the user tries to close the worksheet the user receives warning AC0181. The booking cannot be made in the closed period.

It is critical that messages are not booked into closed periods when the user does not have access to book to closed periods.

Solution:
Unless the current user is allowed to make Claim and Technical Bookings Ignoring Specific Closure Terms
booking on closed period validation should be applied to claim and technical bookings irrespective of worksheet origin with the exception of Prop Treaty OCC Original Currency bookings when the system parameter is set for Accounting - Retrocession - General - Miscellaneous - Override Booking Period on As Original Correction Bookings

Extent of Impact:
Restriction of the general open booking periods - Technical/Claim WS

Validation on Closed Periods for non-Manual origin worksheets will not take place unless the system parameter
'Accounting - Retrocession - General - Miscellaneous - Override Booking Period on As Original Correction Bookings' is set.

Problem:

If there is a balance split defined (triggered by Task definition on Business/Partner Tab), only the Balance including the Claim Paid booking is overwritten with the BP Ref. of the Claim Signing Message once the Claim Worksheet is closed. We would expect that all balance splits are updated with the correct BP Ref. from the Claim Signing Message.

Solution:

If one or multiple (item level) balances are linked, given each linked previous adjustment balance:
look on that worksheet for any additional balances with the same message, currency and claim section and update the references on those balances, if any, in addition to the one linked.

Root Cause:

Update on references only applied to the actual balance(s) linked to the message which does not account for additional balances made by the same booking due to a balance split being applied.

Extent of Impact:

TA updating Claim balances where balances have been split.

Problem:

On the attached new claim message the claims trigger date does not appear to be populated automatically when the claim is set-up. Hence the Claim Update rule can not create a claim automatically and fails. When swapping to claim the claims trigger date appears to be empty and requires manual input (= DOL). Note that we have definite an extended reporting period on this business/insured period.

Solution:

eMessaging should default Claims Trigger and Date for Claims on Prop Treaty when Claims Made or Awards Made

Problem:

We have been doing some more 'investigation' on this abends/crashes and it turns out that this relates to the new rule: SetClaimDispositionToInformationalForProportionalQSTreaty. If this rule is disabled, no abends/crash occur anymore.

Solution:

If there is no section referenced on the message then the rule SetClaimDispositionToInformationalForProportionalQSTreaty should exit (until such a time that the reference is made).

Problem:

Every post placement message is crashing due to a problem linked to the mappedSicsCoverageBasis rule

Solution:

If there is no mapping for a Contract Coverage Basis then skip the Check test until the mapping is made - the Reference rule for Contract Coverage Basis will raise an error.

Workaround:

Change the setting for rule ReferenceContractCoverageBasis to Halt Processing
There is a problem with a missing Acord to SICS mapping for CoverageBasis.

Root Cause:

The subsequent check rule CheckContractCoverageBasis is failing on the missing mapping but this should be trapped to ignore the check until the reference is correctly made. This means you do not get to see the Referencing problem.

Problem:

The CheckDeductionsForAutoBookingValidationRule does not consider deductions captured on section level.
Messages can be referenced to sections and the main section can have no deduction condition set-up but rather the child sections.

This rule needs to look for the deduction condition on main section if the values are inherited to the child sections and if there is a deduction condition set-up on child section that needs to be used/referenced to.

Solution:

The rule should check the deductions on the referenced section and not simply the main section.

Problem:
It is possible to protect an assumed business by an outward cedent contract that has a cedent different from the reinsurer of the business it protects. The system gives only an overridable warning message. The User Guide says that these base companies must match.

Solution:
The user guide should be updated to reflect the correct behavior.

Problem:

ACIM is about to start their UAT and this will become a problem as they will run retro calc / account orders and want to see this in the reports – and since we cannot use and schedule the “Update Retro Pairing Table” job to get the data needed available for reporting.

This period function is not updating the information after the retrocession account order have been run. It does not include any new data. The only time it works is the first time it is run. Any subsequent updates are not included into the AC_RETRO_PAIRING table.

Solution:

If we change this script to include a truncation of the AC_RETRO_PAIRING table then data will become available and the reports start to produce the correct numbers.

 TRUNCATE TABLE AC_RETRO_PAIRING 

 TRUNCATE TABLE AC_RETRO_WORK 

 INSERT INTO AC_RETRO_WORK… 

Is there any chance that this periodic function can be updated with the truncation of the AC_RETRO_PAIRING Table in the beginning or that the scripts can be reviewed to workout why the information in the AC_RETRO_WORK is not populating the AC_RETRO_PAIRING table with the new latest data so that the whole AC_RETRO_PAIRING table does not have to be completely reloaded each time.

Problem:

For  Premium Deposit scenario 4, detail value is not computed correctly.

Showing warning AC0770:The Validation rule detected a discrepancy between computed value and detail value.

Solution:

On the Deposit conditions the Calculation Method is Percent of Premium/Percent of Loss
When booking Premium or Loss Deposit Retained on SAME Accounting Year/Period as an already booked and closed worksheet with a Premium or Loss Deposit Retained in it, the system shall NOT look at these previous bookings but only validate the deposit retained booking on current worksheet against the basis also on the current worksheet.
 

Problem:

BO report does not list worksheet where business partner has changed on business

Solution:

The tables BOAC_PC_FACT & BOAC_WK1_FACT needs to be updated as mentioned by the client in the attachment provided.

Problem:
When the user renews a business, the premium figure for the old underwriting year is copied to the new year.  Then the user creates sections.  The business object report shows however the old premium in the sub sections even after having adjusting the premium on the main section and it was inherited to the sub sections. 

Solution:
Type of Business: Non-Proportional Facultative:
When renewing a business with premium amounts, the system should for the new period, make sure it sets the premium amount on the database (the one used for Business Highlights, Structure tab and Reporting) based on the Limits and Premium Conditions of the same insured period. This should happen also for sub sections.

Problem: 

In Reference Data Unified Universe there are no objects to retrieve emails and phone numbers which is present in SICS 

Solution:

To create objects in Ref Data Universe under Security class for retrieving emails and phone numbers from SICS, create a alias table of ELECTRONIC_ADDRESS such as WEBSITE_ADDRESS, EMAIL_ADDRESS, PHONE_NUMBER, MOBILE_NUMBER, and FAX_NUMBER and then give joins between those alias tables and CNU_USER

Problem: 

Object Business Partner Admin Task filter out data where there is no admin task assigned. In simple report it don't return Reinsurer role with empty admin task, because in this case no admin task is assigned to reinsurer.

Solution:

Outer joins need to be added for the highlighted table so that After adding outer joins, we will Partner details that does not have any value for Business Partner Admin Task.

Problem:

BOAC004 and BOAC_JT_ECG not showing all possible entry code groups.

Solution:

In the oracle version of BOAC004 and in the part that is looking at BOAC_JT_EGC and ECG2 this whole part needs to be updated as it works fine in 22.2.

Problem:

The Pairing objects report does not show some pairings even though they are clearly paired in SICS.

Solution: 

To create a view V_BOAC_STL_PAIRING_FOLLOWER.

Add view V_BOAC_STL_PAIRING_FOLLOWER into the universe structure and provide required joins with respective tables.

Later, modify the definition of objects related to Aggregate pairing balance, Driver balance and cash flow in the universe.

Problem:

Worksheet doesn't flow to BO even after many reinitializations of BO.

Solution:

If possible then we should set up or adjust BOAC004 so that both method A and B will use the same criteria’s on how the worksheets are loaded and what it is doing with BOAC_DUP_WORKSHEET table.

Problem:
The outer join is on the wrong side and needs to be adjusted.
Solution:
The join between the tables 'AC_STL_PAIRING' and 'AC_LEDGER_BALANCE' needs to be adjusted in regard to the outer join direction.

Problem:

To add some objects directly to view V_BOAC_STL_PAIRING, to easily report the settlement indicator for balance 2 (the follower balance in a pairing) as well as getting the full text of settlement indicator for balance 1 for which we currently only have as code in the BOAC_STL_PAIRING/AC_STL_PAIRING table.

Solution:

The view V_BOAC_STL_PAIRING needs to be altered as given so that we can see the settlement indicator for balance 2 (the follower balance in a pairing) as well as get the full text of settlement indicator for balance 1 for which we currently only have as code in the BOAC_STL_PAIRING/AC_STL_PAIRING table.

Problem: 

 The following views to need some changes/adjustments in order to work better and faster:

Solution:

All the views are coming from AC_LEDGER_BALANCE table .

V_BALANCE_DATES is using additional tables .SOC_TO_CLAIM,CLAIM,AC_WORKSHEET, and  V_ORP_DATES,V_AFTERPAIRING_DATES,V_BANK_DATES can be combined with V_BALANCE_DATES view. 

Some additional columns should be added in this view which are available in above three views.

Problem:

In the Cede universe few objects name are mis-spelling such as Orignial  (Code), Acounting, Accociated, Reocvery, Expences

Solution:

Some objects which are mis-spelled in Cede universe should be corrected.

Problem:

Duplicate data is generating due to view V_INS_PERIL_RZ.

Solution: 

The script of view V_INS_PERIL_RZ should be updated for getting correct results.

Problem:

The object Inward paired Amount (Original) Dim it is coming from the V_RETRO_DTL_PAIR_CLMTOOCC_SRC table. and V_INWARD_OUTWARD_DATES is joined to BOAC_PC_FACT table that it should not.

Solution:

To create a alias for V_INWARD_OUTWARD_DATES and should be joined to CLMTOOCC_SRC_DTL table

Problem: 

The object OCC paired Amount (Original) Dim it is coming from the V_RETRO_DTL_PAIR_CLMTOOCC_TGT table. And V_INWARD_OUTWARD_DATES is joined to BOAC_PC_FACT table that it should not. It should be joined with CLMTOOCC_TARGET_DTL table.

Solution: 

To create a alias for V_INWARD_OUTWARD_DATES and should be joined to CLMTOOCC_TARGET_DTL table.

Problem:

The object Detail Amount Unsettled (Main) is missing in the universes under Detail (Main) class.

Solution:

To add object Detail Amount Unsettled (Main), to make its data available on reports according to its Main Currency selected.

Problem:

Booking year period start date and end date was earlier in character format but we need them in date format as the client requested.

Solution:

Altering the views V_BOAC_STL_PAIRING, V_FCREVAL_BAL_BYRP, V_FC_REVAL_DTL_BYRP and V_BOAC_STL_PAIRING_FOLLOWER in all the databases so that we get the dates in proper date format as they were earlier in character format.

Problem:

When the Domain Restriction 'Business Structure' is used for filtering the Use Case 'Business Administration', the system does not stop the user from updating existing conditions.  

Solution:

When the Domain Restriction 'Business Structure' is used for filtering the Use Case 'Business Administration', the system should stop the user from updating also existing conditions. 

Problem:

When the Domain Restriction 'Business Structure' is used for filtering the Use Case 'Business Administration', the system does not stop the user from creating new conditions, if the user opens this condition from another existing condition.  

Solution:

When the Domain Restriction 'Business Structure' is used for 'Business Administration' (Update), the system should stop the user from updating an existing condition and creating a new condition. This should work regardless of from where this condition is opened. For example, opening the Premium and Limit Conditions from the Business Highlights or from another condition (like Clauses) should be restricted by this security. 

Problem:

SICS Server crashes when receiving multiple parallel calls if MaxQueueLength is 0.

Solution:

Made some cleanup/fixes in earlier SICS Server versions that fixed this. This works fine now.

Problem:
You receive an error message when using web service editClassification to change business classifications on a sub section

Solution:
Using web service editClassification to e.g. add classification item(s) on a sub section, the system should execute relevant checks that classification item(s) is valid and then add the item. This should work in the same way it correctly works on main section

Workaround:
Wrong SOAP message is used
To change existing business classifications, you should use service updateScopeOfCover

Problem:

executeBusinessSearch behaves inconsistently in SICS 22.4

Solution:

executeBusinessSearch operation should return list as per the startIndex specified in request and should behave as like in SICS 20.4

Problem:

createClaimGroup API fails to raise an error if the Claim Group name is not unique within the category.

Solution:

SICS Server should raise the same error as online - CM022.

Problem:

When selecting to calculateReinstatement as part of createFGUWorksheet API the system fails to add the reinstatements to the worksheet.

Solution:

Reinstatement bookings - if any are due - should be added to the FGU worksheet.

Problem:

When using the Axis2 client libraries connected to an API server connected to a non-Oracle database, the serialization of Strings with empty values results in a runtime exception: 'Input values do not follow defined XSD restrictions'.

Solution:
Ensure empty strings are treated as nil values to comply with XSD

Root Cause:
Oracle treats empty strings as NULL when storing/retrieving the values.
All other supported DBMS platforms store/retrieve empty strings.

Extent of Impact:
Axis2 API client libraries throw a runtime exception when being used against any database other than Oracle.

Impact on Existing Data
None

Problem:

Serialization Error on CreateBusiness webservice with Axis2 Client for creating a business with deduction commission and without specifying increaseCommissionBy.

Solution:

Make XSD element increaseCommissionBy as optional as it is not a mandatory element.

Problem:
Incompatible function concat_ws on SQL Server 2016 or prior

Solution:
The SQL Server 2016 or prior needs to make changes to the view definition as shown:

LEGAL_AREA.ISO_ALPHA_3+', 'RTRIM(RISK_ZONE.CODE)', '+INS_PERIL.FRK_PERIL_TYPE as RZ_SICS_DISPLAY

Problem:
The system parameter 'Global Credit Terms for Instalments on Assumed Business' input field and belonging unit of time drop down are not completely visible.

Solution:
System Parameters/ Business / Limit and Premium Conditions: Global Credit Terms for Instalments on Assumed Business':
The input field of this parameter and the belonging Unit of Time drop-down (days, months, etc.) must be bigger so that the input values are completely visible both in edit and view mode.

Problem:

When viewing a mapping that has several revisions, navigating between the revisions does not update the fingerprint.

Solution:

Recalculate the fingerprint when selection of revision changes.

Workaround:

In System Parameters, look up the mapping. Open the context menu (the other mouse button) and select 'Show Revisions'. Double-click the desired revision in order to view the fingerprint of that specific revision.

Problem:
Migrating a business, details in User Defined Fields are not copied to the migrated business partner

Solution:
Using Migration Toolkit to migrate a business partner, all details in the input file, should be included in the migration. This does also apply to any User Defined Fields details

Problem:

If selecting to transfer/attach a sub section of a business to a portfolio program and its main section is already linked to this program, the system stops the user.

Solution:

When the main section of an assumed business is already linked to a Portfolio Program and 'Is Period Estimate Sum up Section' is cleared and the users tries to link a sub section of the same business to the same program, the system should NOT stop the user with error message BR0098. Instead, it should attach this sub section.

The behavior when linking Assumed Business should be the same for all pop up menu options, regardless of the user starting from Main OR Sub section or for all. The system should only give this validation message when ' Is Period Estimate Sum Up Section' is selected and the Main Section is already linked to the Portfolio Program, and then the User tries to add the sub section to the program.

Problem:
On PostgreSQL the login ID and the SICS User ID may be in different cases.
In this scenario it is impossible to login to the database and to SICS.

Solution:
Add an option for case insensitivity in the handling of the SICS User ID to the SICS datasource xml file schema
<caseSensitiveCnuUserNames>false</caseSensitiveCnuUserNames>

The default value (false) ignores the case of the login ID when retrieving the SICS ID.

Problem:

Can't link Assumed Business to Portfolio Program with 2 Reinsurers despite Assumed Reinsurer has one of them 

Solution:

When Business Partner from the Assumed is matched with the Portfolio Program, SICS should allow to attach the same even the IAB partner contains First OR second Partner of the portfolio program. SICS007 - SICS Message should only be display when Business Partner does not matched, it means does not exist in Portfolio Program.   

Problem:
API - accountingValidationIndicator and claimValidationIndicator values missing in retrieveObject for type SicsInsuredPeriodReference

Solution:
When running the retrieveObject web service with SicsInsuredPeriodReference as reference object, we should get the data for accountingValidationIndicator and claimValidationIndicator instead of null when we have data added on the Business.

Problem:
Changes regarding Excess of Loss Protection for Common Account assignment to a proportional Outward Cedent's Contract are logged even when no bookings exist and despite the parameter for logging before bookings is off.

Solution:
System Administration / Outbound Interfaces / General Interface Outbound / Set Up / Log Activity Settings: Log Activities: Selected
Log Business conditions before booking: Cleared

Log View started from XL Protection for CA of an Outward Cedent's Contract should not list any logs when 'Log Business conditions before booking is cleared and the protected OCC does not have bookings.

Problem:

Database patch re_2592 incorrectly named re_2590

Solution:

Correct the name of patch re_2592.

Problem:
Copy Live Desktop URL to Clipboard function not available for Remittance worksheet

Solution:
When opening a Remittance worksheet, either in a pending status or in status Final, make sure the option 'Copy SICS Live Desktop URL to clipbord' becomes enabled under the Bookmarks menu option.

Problem:
The sequence in which the available base companies under User Preferences for Extended Base Company Segregation are listed, is not in alphabetical order.

Solution:
On the User Preferences, for selection of the Current Base Company, the system should show the available companies sorted alphabetically.

Problem:

System Use Cases are missing description.

Solution:

Update the label(name) and note fields in the use case definitions where blank.

Problem:

Changes to the domain object hashCode method cause performance degradation.

Solution:

Improve the domain object hashCode method so that it does not cause performance degradation.

Problem:

The angular-chart.js module is bundled with an old version of chart.js, this version of chart.js is not used by SICS Operational Reporting, but it shows up in security scans of the application.

Solution:

Remove the bundled version of chart.js from the packaged angular-chart.js module

Aim of function

Improve the usability of the Multi-GAAP calculation editor in system parameters.
We introduced a searchable hierarchy of calculation functions and operators to make it easy to find the value you need faster when editing a calculation.

Business value for customers

Customers can now have a modified user interface with all available items in searchable tree widget form to insert into calculation rule.

System Parameters Affected

Multi GAAP --> Calculation rule

Existing functionality affected

There is no impact to functionality. This will only improve the usability of calculation editor in Multi GAAP & underwriter estimates system parameter window.

Edit Calculation window - Multi GAAP:

Edit Calculation window - Underwriters Estimates:

Aim of function

To Make it possible for all the users to maintain the Booking Terms for Base Companies outside System Parameter Maintenance. According to the Use Case assigned to the user, the access will be provided for maintaining the Booking Terms Maintenance.
Making the Base Company Segregation waterproof so that the user assigned to specific BCs can see and maintain the Booking Terms only for this/these Base Companies.

Business value for customers

Beneficial for all customers as the maintenance of the Booking Terms will be quicker and more user friendly. Possibility to prevent users (with only the new Use Case) from accessing system parameter settings for other Base Companies than those they are assigned to.

System Parameters Affected

• Extend Base company segregation.
• Hide Base Companies

Existing functionality affected

The new provision will allow users to access Booking terms maintenance of base company from System Administration in SICS Desktop screen instead of from System parameters. 

If Extend Base Company Segregation is activated with the parameter Hide Base Companies selected, and a user assigned to a few Base Company in the User Preferences with the new security Use case assigned then user can have access to create, view, edit, delete and assign booking definition to a base company as per access rights defined. 

Aim of function

Often organizations have several (re)insurance companies sharing the same SICS installation. These are legal entities and might not wish to have knowledge of each other, neither each other’s existence, nor each other’s business administration.  

Some of these base companies might however have intercompany procedures at a common place. The system offers some support for this, by the user being set up to have access to his/her current base company's group. The system offers now also support for handling some of these, even if the current base company is not part of such a group. For example, by system set up, the user can now create an intra group contract on behalf of another company, even if it is not linked to the user's own company.

In addition, finding accounting items according to base company segregation has improved, both for companies set up in an owner group and for companies not within a group.

System Parameters Affected

System Parameter / Database and Systems:  Extend Base Company Segregation
System Parameter / Database and Systems:  Hide Insureds
System Parameter / Database and Systems:  Hide Business Partners 
System Parameter / Database and Systems:  Hide Base Companies 
System Parameter / Database and Systems: Create Intra Group Contract for Ungrouped Companies

Existing functionality affected

Find Business
Create New Business
Renew Business
Maintain Business Partner Roles
Maintain Intra Group Contracts
Maintain System Parameters
Find Accounting Worksheets
Find Accounting Data on Business Partner Ledger

Aim of function
Enable the AdjustmentReferenceRule functionality for the non-prop direct business type.

Business value for customers
Making it possible for the system to extend the functionality of the AdjustmentReferenceRule to
non-prop direct businesses in the same way it is working for non-prop treaty.

System Parameters Affected
N/A

Existing functionality affected
eMessage processing

Aim of function
All eMessages regardless of type shall book into default period only, including the Lloyds CON reversal messages.

Business value for customers
All eMessages, especially “CON reversal eMessages” are expected to close in the default period, regardless the worksheet closed/open in previous month or earlier. When applying a default booking year, the system will check the booking rule for the local bookings:

• If there is no booking rule for the worksheet type of the message, then the system will apply the default period from the open booking year.
• If there is a booking rule for the worksheet type of the message, then the system will apply the year and period that is mentioned in the booking rule by overruling the default period from the open booking terms.

System Parameters Affected
N/A

Existing functionality affected

CON Reversal Messages
eMessage processing

Aim of function
A positive claim response message shall look for the waiting Claim Movement message and trigger its processing (same as when a user is overwriting the CheckForManualClaimResponse manually and re-processes the message.

Business value for customers
Automatic processing of messages ; all related messages will be re-processed (go to waiting) and once the associated worksheet is closed, messages closes (processed).

System Parameters Affected
N/A

Existing functionality affected
eMessage processing

Aim of function

To set and validate the Lloyd's Catastrophe code LcoCatastropheReference value automatically as a Claim Reference on claims via a Lloyd's London Market Service Provider ACORD eMessage.

https://www.lloyds.com/resources-and-services/claims-for-market-participants/catastrophe-portal/catastrophe-codes

Business value for customers

• User can have the LcoCatastropheReference from Lloyd's eMessage set as a claim reference on claims automatically.
• User can validate a LcoCatastropheReference on claims matches an eMessage automatically via an eMessaging rule.

System Parameters Affected

N/A

Existing functionality affected

eMessage processing

Aim of function

Now also supporting:

• respond; allows a techAccount or claim sender to respond to a query previously raised for a related techAccount or claim for the query specified in techAccount.id.
• hold; allows a techAccount or claim sender to send a hold response to a query previously raised for a related techAccount or claim for the query specified in techAccount.id, providing information regarding actions being taken to resolve the query but where further time is required to provide a response.
• chase; allows a techAccount or claim receiver to send a chaser response to a query previously raised for a related techAccount or claim for the query specified in techAccount.id. This can also be used by the sender to send a chaser response to a query response that has been provided for the query specified in techAccount.id.
• attachments; allows a techAccount or claim sender to respond to a query previously raised for a related techAccount or claim for the query specified in techAccount.id.

via the already supported integration with ADEPT (ACORD Data Exchange Platform & Translator). The new integration plugin builds upon the sophisticated SICS eMessaging foundation to provide a next-generation market capability to increase the timeliness, accuracy, and security of business data exchange.

Business value for customers

Enabling rapid data exchange, translation, and transformation via ADEPT, the ACORD Data Exchange Platform & Translator.

System Parameters Affected

Configuration of a new eMessaging ADEPT gateway plugin.

Existing functionality affected

eMessaging
 

Aim of function

To implement support for creation of actual job for the remaining orders (Group Orders).
The orders listed below can now a Activate Scheduled job from the workstation from the Group order window itself for all child orders.

• Account Group Order (Retrocession Account Order Group)

• Calculation Group Order (Retrocession Calculation Order Group)

• Recovery Calculation Group Order

Business value for customers

Once Schedule job is created with request status, the Job, however, will not be run before its activation through Accounting Orders Monitor. With this enhancement, users can Activate Schedule job from the workstation (from the Group order window itself) for all child orders.

System Parameters Affected

None

Existing functionality affected

Accounting Orders (Scheduled Job activation)

Note: The current implementation is limited to showing the menu option, but doesn't trigger activation of child orders in 23.3 release. The Activation of child orders will be implemented in SICS 23.4 release.

Aim of function

Add configurable links that will appear in SICS as a menu item in the Help Menu.
The primary purpose is for Helpdesk links e.g. 'Contact Helpdesk' -> https://mycompany.com/helpdesk/sics
However links to any system are allowed.

Business value for customers

Easy access to specific support services from within the application itself.

System Parameters Affected

New system parameter page under Desktop Administration where multiple URL links can be added in a list.

Existing functionality affected

Help Menu bar

Aim of function

Generate the SOAP API documentation from code to ensure it is always up to date and complete.
In these release we are generating the list of APIs by entry point with a description and references to their input and output types.
Future releases will build on this to provide schema browsing and more detailed descriptions.

Business value for customers

Provide easily accessible, up to date generated documentation for SOAP webservices for SICS API Server.

System Parameters Affected

None

Existing functionality affected

None