Release documentation - P&C Enhancements and requests

Problem:
Not possible to remove business classification when there is an open worksheet, even if this classification is not present on the open worksheet

Solution:
When a classification value is removed from the Classification tab on a business and the system check if open worksheets exist, and present message BS00276 if open worksheets exist, we must make this check more specific and see if the actual value the user is suppose to remove is PRESENT on any of the open worksheets. If the value to be removed is not present on any of the open worksheets, then the message BS00276 shall not appear.

Workaround:
Close the open worksheet before the classification value is removed

Root Cause:

Extent of Impact:

Impact on Existing Data

Recovery Method for Existing Data Affected

Problem:
When AC split percentage on AC Split % tab on the P/L conditions are defined with negative sign, the amounts become wrong.

Solution:
When booking Adjustment Premium from the P/L conditions with AC Split % defined on the P/L conditions, make sure the system can handle also negative AC percentages and distribute the negative amounts correct on each of the ACs with negative percentages.

Workaround:

Root Cause:

Extent of Impact:

Impact on Existing Data

Recovery Method for Existing Data Affected

Problem:
When the field 'Tax Applicable' in the Government Tax Table has the value 'No' all remaining fields in the table are mandatory to define/fill in, but should not have been.

Solution:
When the field 'Tax Applicable' in the Government Tax Table has the value 'No' some fields must be optional to define and some other fields must not be possible to defined

Workaround:

Root Cause:

Extent of Impact:

Impact on Existing Data

Recovery Method for Existing Data Affected

Problem:
The ‘Closed Balances Mass Update’ order does not include balances where the Payment Task is assigned to a Broker.

Solution:
On the Closed Balance Mass Update order, the Balance Owner field is pointing to the Responsible Business Partner on the balances. So if a partner is given here and this partner act as the Responsible Business Partner on the Balance, then this balance shall be listed (if it fulfills the other filter criteria), independent if it has a different Payment Business Partner, e.g. a Broker, on the balances.

Workaround:

Root Cause:

Extent of Impact:

Impact on Existing Data

Recovery Method for Existing Data Affected

Problem:
Doesn't recalculate VAT for other deduction when change placement share

Solution:
When Signed Share (Placement Share) is changed for a Retrocessionaire Participation (ORP) on a Fac OCC, and the system is suppose to make correction bookings on the ORP because of this, then we must make sure the system also calculate and book VAT for all the correction bookings made for the deductions.

Workaround:

Root Cause:

Extent of Impact:

Impact on Existing Data

Recovery Method for Existing Data Affected

Problem:
Group Remittance function is not functioning properly when own bank account is mandatory in the system parameters

Solution:
When trying to create balance pairing between a Settlement Balance (containing balances from different Base Companies) and a Group Remittance, by selecting the option Automatic Balance Pairing from the Group Wire, we must make sure the system is able to perform the balance pairings when each of the Group Internal remittances perfectly match the technical balance(s) in the SBG for the actual Base Company. Only in case such a match does not happen, then the message AC0379 should appear.
In case there is no discrepancy in the Functional Currency among the group remittance members created, then the system should not present the message AC0522 about this.

Workaround:

Root Cause:

Extent of Impact:

Impact on Existing Data

Recovery Method for Existing Data Affected

Problem:
Classification data - Type of Risk - cannot be used in fastCreateTechWks soap

Solution:
All valid classification types should be available for Web Service as per on-line, also including the classification type with sub class 525, reference data Type of Risk.

Workaround:

Root Cause:

Extent of Impact:

Impact on Existing Data

Recovery Method for Existing Data Affected

Problem:
Can't create TW on main section if business all sub-sections are inactive if tick system parameter 'Do not allow create TW for non-leaf sections'

Solution:
When the system parameter 'Do not allow create TW for non-leaf sections' is ON and the user is trying to book on a business with sub-sections but all sub-sections are Inactivated, we must make sure the Main Sections becomes available on the worksheet, in the same way as if the business only contains on a Main Section.. The requirement to book on leaf sections only shall only take effect if at leased ONE ACTIVE sub-section exists.

Workaround:

Root Cause:

Extent of Impact:

Impact on Existing Data

Recovery Method for Existing Data Affected

Problem:
PBR_Claims paid without reserves maintained is raised even if there are loss reserves on previous booking dates.

Solution:
When the PBR 'Claim Paid Without Reserves Maintained' is executed the system will trigger a report if there are no existing loss reserves (or the sum of loss reserves becomes zero) with a Booking Date prior to the Booking Date on the worksheet to be checked. But the report should not be triggered if there exist loss reserves with a Booking Date prior to the Booking Date on the worksheet to be checked and the sum of these reserves are different from zero, even if the Loss Reserve sums up to zero for one or more currencies, as long as it is NOT zero for at least ONE currency.

Workaround:

Root Cause:

Extent of Impact:

Impact on Existing Data

Recovery Method for Existing Data Affected

Problem:
Copy Worksheet for ORP/OCC not validating the carrier on the Insured Period (Cedent)

Solution:
When a balance is copied either on an OCC or an ORP we must make sure the Base Company on the source balance is checked against the Base Companies (Cedents) on the actual Insured Period. 1) If one Cedent is marked as Main Base Company, then set this as the Base Company on the new balance. 2) If no Cedent is marked as Main Base Company, then check if the Base Company is among the Cedents on the actual Insured Period and if it is, 2a) keep the Base Company from the source balance, else 2b) reset the Base Company on the new balance to the first Cedent on the Insured Period.
This shall not affect the Reversal process, where the Base Company shall be kept from the Source.

Workaround:
Mark the new Cedent as Main Base Company. This will force the system to pick this Cedent as Base Company also on a copied balance.

Root Cause:

Extent of Impact:

Impact on Existing Data

Recovery Method for Existing Data Affected

Problem:
No validation error when running Recovery Calculation order for Protection Program without Registration Complete set for included OCCs.

Solution:
Implement Validation error BS0718 'Registration of Contract is not yet complete' for all Recovery and Reinstatement orders.
When running orders for Protection Program, all OCCs must be validated, and a message with a list about which OCCs and IPs that are missing Registration Complete must be given.

Workaround:
Set Registration Complete for all included OCCs - and run the order again to get worksheets created.

Root Cause:

Extent of Impact:

Impact on Existing Data

Recovery Method for Existing Data Affected

Problem:

When user selects multiple rows in a table by holding SHIFT key , SWT Table Scrolls to Far Right.

Solution:

Ensure that Scrollbar doesn't move when user selects multiple rows in a table by holding SHIFT key or CTRL key.

Workaround:

Root Cause:

Extent of Impact:

Impact on Existing Data

Recovery Method for Existing Data Affected

Problem:
Doesn't show all merger members if selected active BP belong to a merger group

Solution:
When the BP Ledger opens from the Business Partner properties and this partner has Merged Companies, make sure all Merged Companies are also included in the partner list on the BP Ledger, also partners that are not Active. This must be the case both when the Business Partner you open the BP Ledger from is an Active partner or not.

Workaround:

Root Cause:

Extent of Impact:

Impact on Existing Data

Recovery Method for Existing Data Affected

Problem:
The system does not generate preliminary bookings when importing IAB from OCC side.

Solution:
When the user selects the function Import Assumed Business on the AB list page on an OCC, which is enabled independent of the system parameter Remove or Add Assumed Businesses on OCC not allowed', we must make sure that the import facility also takes care of the preliminary bookings independent if the above parameter is selected or not.

Workaround:
Add the protection manually on the PA page on each of the actual Assumed Businesses.

Root Cause:

Extent of Impact:

Impact on Existing Data

Recovery Method for Existing Data Affected

Problem:
I select 'Automatic Booking of Government Tax' -> trying to apply / change status etc. the system crashes.

Solution:
On a Claim worksheet when booking the Government Tax calculation the bookings should be correctly populated and not cause abends

Workaround:
Workaround for problem no 2 above is to delete the Target EC and calculate the government tax

Root Cause:

Extent of Impact:

Impact on Existing Data

Recovery Method for Existing Data Affected

Problem:
SICS abend when click on button 'Worksheet' on worksheet closing screen

Solution:
When executing the closeWorksheet web service with the <notes> element enabled but without giving any value in the field, make sure the system sets the Notes field on the worksheet to blank (as if no notes exists), so that it is possible to navigate from this worksheet closing window to the worksheet by pressing the Worksheet button, without abending.

Workaround:
Make sure that if the <notes> element is enabled in the closeWorksheet service that a value is also given in this field. This will solve the problem no 2 above.

Root Cause:

Extent of Impact:

Impact on Existing Data

Recovery Method for Existing Data Affected

Problem:
Automatic Gov. Tax Booking doesn't work if partial Target EC is already booked (TA WS)

Solution:
When booking a trigger entry code with an amount and the target entry code is already present on the technical worksheet, and the user do the automatic calculation of Government Tax on this worksheet, then the system must recalculate new target Government Tax amount for this trigger detail.

Workaround:
Before the recalculation of the government tax is performed, delete the target detail

Root Cause:

Extent of Impact:

Impact on Existing Data

Recovery Method for Existing Data Affected

Problem:
GOV. TAX - TA&CL - SICS 21.1 - TECTAP01 - Government Tax Log Messages option not greyed out if no error

Solution:
When a Balance or Details is highlighted on the Business Ledger and the popup menu is opened and the option Government Tax Log Messages is selected, w must make sure the sub menu options Balance and Detail become disabled if the Balance or Detail do not have such a log message linked.

Workaround:
When the option is selected you will see that there are no log message linked. This problem will not affect reporting.

Root Cause:

Extent of Impact:

Impact on Existing Data

Recovery Method for Existing Data Affected

Problem:
Government tax is displayed twice due to similar rule

Solution:
On a worksheet, both technical and claim worksheet, when the user select the Automatic Booking of Government Tax and the system finds that ONE Trigger Entry Code hits TWO different Government Tax Rules, both with the SAME Target Entry Code, then we must make sure the system splits the Government Tax target details in two details so that each detail is assigned to the correct GT Rule Reference. This can be done by using the 'governmentTaxRuleRef' as a new attribute to separate details.
NB! For Claim Worksheets it is recommended to use DIFFERENT entry code for the two GT rules else it will not be possible to close the worksheet - it is not allowed with same entry code on different details on a claim worksheet.

Workaround:

Root Cause:

Extent of Impact:

Impact on Existing Data

Recovery Method for Existing Data Affected

Problem:
1.
I have booked two different Trigger ECs, for which Tax is applicable with same Target EC:
Trigger EC 3021 -> Target EC 302B
Trigger EC 3023 -> Target EC 302B
I haven't entered any Target EC.
I select 'Automatic Booking of Government Tax' -> the system crashes.
2.
I have booked both a Trigger EC and a Target EC (manually added or automatically appearing because it has been booked on the claim before) and I select 'Automatic Booking of Government Tax -> the Target EC is not recalculated

Solution:
On a Claim worksheet when booking a trigger entry code for the Government Tax calculation we need to make a solution for the following problem that occurs when the user select the function Automatic Calculation of Government Tax:
1) When booking two trigger entry codes, both with amounts and with the same target entry code and the user selects the calculation of Government Tax, then the system must calculate one target detail of government tax for the sum of the two trigger details without abending.
2) When booking a trigger entry code with an amount and the target entry code is already present on the worksheet, either because it is automatically shown on the worksheet or if it has been manually added or calculated, and the user do the automatic calculation of Government Tax on this worksheet, then the system must recalculate new GT amount for this target detail.

Workaround:
Workaround for problem no 2 above is to delete the Target EC and calculate the government tax

Root Cause:

Extent of Impact:

Impact on Existing Data

Recovery Method for Existing Data Affected

Problem:
GOV TAX - TA WS Refresh problem with Gov Tax Split option

Solution:
1. When the Balance Split Option for Government Tax is selected/deselected, we must make sure the system split/merge balances accordingly. It is working fine when the balance contains of both trigger codes and target government tax codes and you select the split option, then the system correctly split in two balances one with the normal entry codes and one balance with the government tax codes.
But when the split option is deselected nothing happens and here we must make sure the system merge the balance again and include both the normal codes and the government tax codes.
2. When a new detail is created on the worksheet where an existing Government Tax detail exists and the Balance Split option for Government Tax is already selected so that a special balance for this Government Tax detail exists (with Notes field given) then we must make sure the new detail creates a new balance without copying the Notes so that it can be merged with the none-Government Tax balance (if possible).

Workaround:

Root Cause:

Extent of Impact:

Impact on Existing Data

Recovery Method for Existing Data Affected

Problem:
GOV TAX - Tax Prct Calculation Basis Booking Date not working as expected

Solution:
When Automatic Booking of Government Taxes takes place on the worksheet and a Government Tax rule is found to be used, and this rule is defined with Tax % Calculation Basis is Booking Date, then we must make sure the automatic booking of the Government Tax is performed if the current date is equal or higher than the Tax % Applicable valid From and is equal or less that the Tax % Applicable valid To, and this must be independent of the trigger detail's Accounting Period From - To.

Workaround:

Root Cause:

Extent of Impact:

Impact on Existing Data

Recovery Method for Existing Data Affected

Problem:
When uploading IAB from OCC side, if the protection assignment is created between IAB main section and OCC main section, but the bookings exist on IAB sub-sub section, the system does not generate preliminary bookings after import

Solution:
When the function Import Assumed Businesses is selected from the Assumed Businesses list on a prop treaty OCC, and the imported ABs already have bookings on the ledger, the system will generate preliminary bookings on the As Original ledger of these bookings on the ABs. We must also make sure if the existing bookings on the AB are on any sub section level, that these bookings are also included in this process to generate preliminary bookings on the OCC.

Workaround:

Root Cause:

Extent of Impact:

Impact on Existing Data

Recovery Method for Existing Data Affected

Problem:
SICS abend when close TW on NPTTY with PROP STP protection that is not realized

Solution:
When booking on an Assumed Business with a Single Treaty Protection that is NOT yet Realized, then the system should give an error message to the user about this and prevent the user from closing the worksheet on the Assumed Business.

Workaround:
Make sure the STP is realized before starting booking on the AB

Root Cause:

Extent of Impact:

Impact on Existing Data

Recovery Method for Existing Data Affected

Problem:
The Claim Movement must be excluded from Government Tax Validation

Solution:
The Claim Movement must be excluded from Government Tax Validation

Workaround:

Root Cause:

Extent of Impact:

Impact on Existing Data

Recovery Method for Existing Data Affected

Problem:
When booking a Target Entry Code on a worksheet, without a corresponding Trigger Entry Code and there is no respective rule in the Governement Tax table, system does not stop the user from closing the user.

Solution:
When trying to close a worksheet including a Target Entry Code only and no Government Tax rule exists;
System must issue an error message telling that no respective Government Tax Rule exists.
User may either delete the Target EC to be able to close the worksheet or update the Gov Tax Category and Gov Tax Comment field to override this error. Upon 'Change Status' system must issue an error message telling that 'The Gov Tax Trigger EC/Target EC booking link is missing for at lease one Gov Tax Target ECs'. User must not be allowed to close the worksheet until a link between a Trigger/Target Entry Code is made.

Workaround:

Root Cause:

Extent of Impact:

Impact on Existing Data

Recovery Method for Existing Data Affected

Problem:
No validation that reinstatement and brokerage has correct sign, as long as amount is correct

Solution:
The accuracy validation for brokerage and reinstatement premium must also check that the sign is correct, and raise an error if not.

Workaround:

Root Cause:

Extent of Impact:

Impact on Existing Data

Recovery Method for Existing Data Affected

Problem:
Default BYRP is taken on balance pairing when 'BYRP according to technical balance' is checked

Solution:
When the system parameter 'BYRP according to technical balance' is selected and there is no special default booking year/period defined for Balance Pairing for the actual Base Company in the system parameters for Base Company Specific Settings, Booking Terms, then the system shall still use the Booking Year/Period from the balance on the Technical/Claim worksheet as the Pairing Booking Year/Period if this is equal to or higher than the general Default Booking Year/Period and is within the open periods for this Base Company.
The above is working fine when special default booking year/period IS defined for Balance Pairing for the actual Base Company.

Workaround:

Root Cause:

Extent of Impact:

Impact on Existing Data

Recovery Method for Existing Data Affected

Problem:
Abend when right mouse click on selected Remittance from Find Accounting Worksheet screen

Solution:
On the Find Worksheet window, when the user has highlighted a Remittance Balance and press the right click button, we must make sure the system displays the popup menu without abend.

Workaround:

Root Cause:

Extent of Impact:

Impact on Existing Data

Recovery Method for Existing Data Affected

Problem:
Error like messages in BPL for SBG in columns Pairing BYR and Pairing BP. Walkback when clicking on Settlement Balance Group from Business Partner Ledger or from Find Accounting Worksheet

Solution:
When balances that are Settled in balance pairing, are listed on the BP Ledger, the new column Pairing BYR and Pairing BP shows the Booking Year and Period from the pairing object. But for some balances that are Settled without any pairing like Settlement Balance Group, Account Balance Group or Expected Payment, we must make sure the Pairing BYR and Pairing BP columns are blank.
The walkback will be solved through an additional correction of SICSR-21365, already fixed in main stream but needs to be ported to 20.4_SSP1_ALL2

Workaround:

Root Cause:

Extent of Impact:

Impact on Existing Data

Recovery Method for Existing Data Affected

Problem:
The abend happens when there is a detail to a child PP section which is not fully covered will be read in by its parent PP section. When the underlying program section is a risk and the parent is a cat protection we will get this abend.
Observation:
In 21.2, this example does not abend because of the fix made for SC-3721 where we added null check. It appears that this fix did not include these details in ac table because of different risk indicators. This will in some cases cause details to be stopped from being considered for recovery at the next level in the hierarchy.

Solution:
When underlying program section has a Risk OCC and parent section has a Cat OCC, the system must make sure details from one Program section is sent to the next level via ITB conditions. It must also be sent via the automatic functionality which ensures details not fully recovered in child program section is read by its parent PP section and considered for recovery.

Workaround:
None

Root Cause:
SC-2729 / SC-3721

Extent of Impact:

Impact on Existing Data

Recovery Method for Existing Data Affected

Problem:
SICS abend when delete IAB booking

Solution:
It must be possible to Delete a detail row on Technical Worksheet even if it is not linked to an Insured Period or Section yet. This is a problem when the Government Tax framework is in use.

Workaround:

Root Cause:

Extent of Impact:

Impact on Existing Data

Recovery Method for Existing Data Affected

Problem:
When creating a new contract from a program with several reinsurers, this contracts receives all reinsurers.

Solution:
When the system parameter 'Joint Underwriting Agreement in Use' is Cleared, only one Reinsurer should be allowed at any one time for an assumed business. If an assumed business is created from a Cedent's Program with more than one reinsurer and the user does not deselect on in the creation process, the system should stop the user.

Workaround:
Remove the extra Reinsurers

Root Cause:

Extent of Impact:

Impact on Existing Data

Recovery Method for Existing Data Affected

Problem:
Re-establishing Inheritance of Deduction Impacts Non-Intended Retrocessionaire Participations

Solution:
Level Of Business - Outward Cedent's Contract
Type Of Business - Proportional Treaty or Non-Proportional Treaty or Proportional Facultative or Non-Proportional Facultative

When Outward Cedent's Contract is placed through Broker and through direct Placements AND Deduction Condition on direct Placement (without a Broker) is deleted to restore inheritance - SICS must only re-establish the inheritance of Deduction Condition on the updated Retrocessionaire Participation, without changing Deduction Condition on any other Retrocessionaire Participation which is not changed by user, no matter if those Placements are direct or via Broker

Workaround:
1. Edit Deduction condition of one Placement through Broker in order to brake the inheritance
2. Save the Deduction condition without making any change
3. Delete the Deduction condition from the broker-placed ORP
4. See that the Deduction condition will still be inherited, but this time it will come from the Intermediary Placement, instead of from the Outward Cedent's Contract

Root Cause:

Extent of Impact:

Impact on Existing Data

Recovery Method for Existing Data Affected

Problem:
System abends when deleting the Premium and Limit Conditions 'P/L Main' tab, when the P/L Main tab is defined, but without any currency

Solution:
When one or more of the Premium Conditions is defined, the P/L Main condition must contain the minimum information, i.e. Currency and Premium Type (the same information that is automatically defined on the P/L Main tab when first creating P/L condition, but enter no details on the P/L Main tab)
When selecting to Delete the P/L Main tab condition, and any other premium information exists you should be stopped by an validation error message.

Workaround:
As long as Deposit Premium, instalments or any other premium information exists on the section, the P/L Main tab should not be deleted. Make sure that the P/L Main condition is defined with minimum information such as Currency and Premium Type - the same information that is automatically defined when first creating Premium and Limit Conditions, but no additional input is made on the P/L Main tab.
If you however end up with a defined P/L Main tab with no currency, you must delete the Deposit Premium Condition first, and you can then delete the P/L Main tab condition

Root Cause:

Extent of Impact:

Impact on Existing Data

Recovery Method for Existing Data Affected

Problem:
Milli Re are now testing version 20.3 in preparation for an upgrade. The users have found that Other Costs is still appearing as 4.9.5, but not the other two deductions, Brokerage and Overriding Commission, they now appear as positive in the Business Highlights screen in 20.3 but were negative in 4.9.5. A copy of the Milli Re Prod DB is on the Oslo server.

Solution:
On a prop treaty OCC, when the user opens the Highlights and the system displays the Deduction Types and Percentages for these, then we must make sure the system is using the Entry Code Properties for the Entry Codes found under the Accounting Function REAC - Retrocession Accounting Proportional Treaty to find out if the percentages should be presented as a positive or negative amount (negative percentage only when the entry code is defined opposite of the normal, i.e. positive on assumed business)
On a prop treaty OCC, when the user edit the estimated premium on the Main tab on the Premium and Limit conditions, then we must make sure the system is using the Entry Code Properties for the Entry Codes found under the Accounting Function REAC - Retrocession Accounting Proportional Treaty to find out if the deduction should be deducted or added to the Premium when the Net Premium is to be calculated (added only when the entry code is defined opposite of the normal, i.e. positive on assumed business)
On a prop treaty OCC when the user make a manual booking and performs the function Automatic Booking of Deductions, we must make sure the system is using the Entry Codes found under the Accounting Function REAC - Retrocession Accounting Proportional Treaty to find the entry codes to be used for the deductions to be booked.

Workaround:

Root Cause:

Extent of Impact:

Impact on Existing Data

Recovery Method for Existing Data Affected

Problem:

When having changed base company for a contract, the system still keeps classifications not in use by the new base company.

Solution:

When a classification for a Base Company is not in use, as per system parameter Base Company Settings / Classification Rule 2, and a business is renewed to a new base company, the system should not copy unused classifications from the previous insured period to the next insured period. Also if  changing the Base Company for an insured period of a contract, the system should drop any unused classification by the new Base Company.

Workaround:

Root Cause:

Extent of Impact:

Impact on Existing Data

Recovery Method for Existing Data Affected

Problem:
The date information of the premium instalment schedule (due date, account date, payment date) are outside its insured period.

Solution:
Type of Business:

• Non-Proportional Treaty
• Proportional Facultative
• Non-Proportional Facultative
• Proportional Direct
• Non-Proportional Direct

When there are manually created Instalments on the latest insured period and Instalment Condition is not empty (it is colored), but the field “Number of Instalments” is empty, while the Days etc. exist (see screen below) – during business renewal, even if user answers “No” to message for Proportional Split of Instalments, the system should calculate the instalments dates (Due Date, Accounting Period From - To, Payment Date, Extended Payment Date) for the new insured period the same way as it currently correctly does if the whole Instalment Condition sub-tab is empty (greyed out)

Workaround:
Manually correct Dates on Instalments on new Insured Period OR confirm message for Instalment Recalculation in the renewal wizard.

Root Cause:

Extent of Impact:

Impact on Existing Data

Recovery Method for Existing Data Affected

Problem:

When a declaration, (being a special acceptance or not special acceptance) has its own Limits and Premiums Conditions and then trying to delete this declaration, the system abends.  

Solution:

When having overridden Limits and Premiums Conditions for a sub section, an insured object cession or a declaration, and then trying to delete this sub section, cession or declaration, the system should not abend.  Instead it should delete this section, cession or declaration.

Workaround:

Close the business and reopen the business again before deleting the Declaration.

Root Cause:

Extent of Impact:

Impact on Existing Data

Recovery Method for Existing Data Affected

Problem:
Abend when edit and save Classifications on Programs (Reinsurance, Protection) or Own Retention without changing the values.

Solution:
Level of Business:
-Reinsurance Program
-Protection Program
-Own Retention

SICS must not abend when Business Classifications are opened in Edit mode on above Level of Businesses and then saved without any changes. In this case the system should save the Classifications and not abend.

Workaround:
Press Cancel instead of OK and abend does not happen; OR record a new value for business Classification and then save

Root Cause:
SE-1072

Extent of Impact:

Impact on Existing Data

Recovery Method for Existing Data Affected

Problem:
Deposit Premium condition - system overwrites percentage with change of release pattern

Solution:
On the Deposit Conditions, Premium tab, when the user switch the 'Release in' radio button between 'Next Account' and 'Same Account In Next Accounting Year' we must make sure the system keeps the value in the Percentage field and NOT resets the number to 0.00000. This works correct on the Loss tab.
The Percentage field shall only be reset to 0.00000 when the user change the Calculation Method, which is correct both on Premium and Loss tab.

Workaround:
Re-enter the percentage manually

Root Cause:

Extent of Impact:

Impact on Existing Data

Recovery Method for Existing Data Affected

Problem:

Main Base Company indicator is not correctly removed in the DB when unticking Main Base Company after OCC has been copied with a Main Base Company flag. This is causing incorrect Headline Loss Filter.

Solution:

When removing Main Base Company indicator, the DB must reflect the removal correctly.

Workaround:

Create from start without Main Base Company flag, or copy from an OCC without Main Base Company.

Root Cause:

Extent of Impact:

Impact on Existing Data

Recovery Method for Existing Data Affected

Problem:
Replace Reinsurer creates duplicate Reinsurer when multiple Insured Periods are present

Solution:
Level of Business:

• Assumed Business
• Reinsurance Program
• Cedent’s Program
• Portfolio Program
• Master Agreement
• Retrocessionaire Participation

When business has multiple Insured Periods AND Reinsurer is changed via pop-up option “Replace Reinsurer” on all Insured Periods (message BS00287 is answered “Yes”) AND ‘old’ Reinsurer is NOT converted to Original Reinsurer (message BS00286 is answered “No”), then the ‘old’ Reinsurer must be removed from the business and only the ‘new’ Reinsurer should be displayed on Partners tab on all Insured Periods, even after a full system refresh is performed and business is reopened once again afterwards.

Workaround:
Manually remove the 'old' Reinsurer from all Insured Periods after the full refresh OR use 'Replace Reinsurer' separately on each Insured Period of the contract (e.g. answer 'No' to message BS00287)

Root Cause:

Extent of Impact:

Impact on Existing Data

Recovery Method for Existing Data Affected

Problem:

Find business does not transfer inactive business partner back from 'Find: business partner'

Solution:
When

• System Parameter 'Include merged companies and merger parent at search by business partner' (Find->Partners) is SELECTED
• Business Partner is Inactive and not included in Merger Group

On 'Find Business' screen – when one presses magnifying glass on 'Bus. Partner' (or 'Bus. Partner 2') to go to 'Find: Business Partner' screen where searches for Partner which is inactivated and not included in Merger Group -> this selected Partner must be transferred via double click or pop-up option ‘Transfer’ to screen “Find Business” in container 'Bus. Partner' (or 'Bus. Partner 2').
Just like the system correctly does when the inactivated Business Partner is included in Merger Group OR when System Parameter 'Include merged companies and merger parent at search by business partner' (Find->Partners) is CLEARED.
 

Workaround:
Enter directly the inactivated Business Partner in 'Bus. Partner' (or 'Bus. Partner 2') on 'Find Business' screen via type ahead or by entering the Partner ID, without using the magnifying glass to go to 'Find: Business Partner' screen.

Root Cause:

Extent of Impact:

Impact on Existing Data

Recovery Method for Existing Data Affected

Problem:

When the Limit and Premium condition is amended from Inception and thus there are 2 amendments but only one effective period, the calculation of Minimum and Deposit Premium in Underwriter's Estimates accumulates the premium for both amendments. This relates to calculations using the following calculation variables
In Underwriters estimates:
%depositPremiumAmountOurShare

%depositPremiumAmountOurSharePerCurr

%minimumPremiumAmountOurShare

%minimumPremiumAmountOurSharePerCurr

Solution:

When the Limit and Premium condition is amended from Inception, only the premium from the last amendment should be used in the calculations in Underwriter's Estimates 

Workaround:

Root Cause:

Extent of Impact:

Impact on Existing Data

Recovery Method for Existing Data Affected

Problem:

Bad performance when opening Claim List on Policy with a large number of Claim (above 10.000)

Solution:

Simplify the method for displaying all Claims in a claims list in the online view - to ensure the system can handle a large number of claims with better performance.

Workaround:
None

Root Cause:

Extent of Impact:

Impact on Existing Data

Recovery Method for Existing Data Affected

Problem:
An error is raised when attempting to extend the insured period when there are linked claims although claims are valid for new extended period.

Solution:
An extension of insured period should be allowed although claims have been linked, and booked, provided they are valid for the extended period. Insured Period on existing bookings remains as they are.
Workaround:

Root Cause:

Extent of Impact:

Impact on Existing Data

Recovery Method for Existing Data Affected

Problem:
Claims are displayed multiple times per claim group.

Solution:
Each claim section should only be listed once per booking currency on the linked claim group.

Workaround:

Root Cause:

Extent of Impact:

Impact on Existing Data

Recovery Method for Existing Data Affected

Problem:
When entering a NEW amount which is identical to the previous amount, the adjustment column is blank, instead of 0. When the parameter Remove entry codes without adjustments, this results in no booking towards the entry code.

Solution:
When the new amount in the claim worksheet is identical to the previous amount, the system should calculate an adjustment of 0

Workaround:

Root Cause:

Extent of Impact:

Impact on Existing Data

Recovery Method for Existing Data Affected

Problem:
Validation error AC0399 for reinstatement brokerage appears when booking premium

Solution:
Reinstatement brokerage validation should not be triggered when worksheet contains only PREMIUM related entry codes (which may include brokerage)

Workaround:

Root Cause:
SE-3510

Extent of Impact:

Impact on Existing Data

Recovery Method for Existing Data Affected

Problem:
1. Abend when reinstatement validation rules are included in template but not relevant for business
2. Abend when booking installments when reinstatement validation rules are included in template, but not present in worksheet

Solution:
1. The accuracy rules for reinstatement (compare worksheet type, reinstatement, and brokerage) must consider condition. If condition is not available, the rules must be ignored.
2. the reinstatement validation rules should not be triggered when booking installments, adjustments.

Workaround:

Root Cause:

Extent of Impact:

Impact on Existing Data

Recovery Method for Existing Data Affected

Problem:
Find Claim Program does not support multiple partners in BP field

Solution:
Find Claim Program should support multiple partners as criteria for one partner type; eg Broker, and retrieve all which has either and matches any other search criteria.
 
Workaround:

Root Cause:

Extent of Impact:

Impact on Existing Data

Recovery Method for Existing Data Affected

Problem:
Possible to reverse or reverse/replace a technical wk with linked claim wk prior to claim wk closing

Solution:
disable the options if the technical worksheet has a linked claim worksheet

Workaround:

Root Cause:
SE-2567

Extent of Impact:

Impact on Existing Data

Recovery Method for Existing Data Affected

Problem:
Refresh issue in claim accuracy validation

Solution:
Hard stop error should appear immediately when Aggregate Limit is exceeded

Workaround:
apply worksheet prior to change status

Root Cause:
SE-3512

Extent of Impact:

Impact on Existing Data

Recovery Method for Existing Data Affected

Problem:
When booking reinstatement on technical worksheet and business has brokerage defined on deduction condition, and possibly also on reinstatement condition, and accuracy template contains rules for both deduction brokerage and reinstatement brokerage, the system raises error for deduction brokerage

Solution:
When booking reinstatement and validating brokerage, the system should not raise rule for brokerage- deduction condition; but only brokerage -reinstatement condition.

Workaround:

Root Cause:

Extent of Impact:

Impact on Existing Data

Recovery Method for Existing Data Affected

Problem:
An entry which has been defined as default in claim worksheet - is appearing in the worksheet although restricted for user

Solution:
When an entry code is restricted for user, it should not appear as default

Workaround:

Root Cause:

Extent of Impact:
None - validation error appears when applying/closing

Impact on Existing Data

Recovery Method for Existing Data Affected

Problem:
User cannot create a claim on proportional treaty when claim basis is not defined and date of loss is after Insured Period End date.

Solution:
When no claim basis is recorded and claim trigger code is None, (and there is no Clean Cut or Portfolio to consider) the system should check if date of loss is within Insured Period.
If it is not, check if it is within OPP and OPP start is within Insured Period.

Workaround:
Define claim basis Risks Attaching

Root Cause:

Extent of Impact:

Impact on Existing Data

Recovery Method for Existing Data Affected

Problem:
A number of unexpected issues for SOC Limit validation when claim has different limits for paid and incurred, and allocation towards Annual Aggregate Deductible

Solution:
SOC limit validation should refer to errors AC0191,192,193,194 - and not to AC0057
Validation computed and detail amounts must be expressed in our share.
Validation must apply correct limit in computed amount - this is incurred limit when validating incurred amount, and payment limit when validating paid amount.
Detail amount must include all relevant bookings for claim section including any bookings towards AAD

Workaround:

Root Cause:

Extent of Impact:

Impact on Existing Data

Recovery Method for Existing Data Affected

Problem:
Reinstatement booking is validated also when calculation rule is 'No Automatic Calculation'.

Solution:
When reinstatement calculation rule is No automatic Calculation, neither reinstatement nor reinstatement brokerage should be validated

Workaround:

Root Cause:

Extent of Impact:

Impact on Existing Data

Recovery Method for Existing Data Affected

Problem:
Missing validation of date of loss and original policy period start date for Facultative and Direct business with Claim Basis = Risks Attaching

Solution:
The system must validate that the Date of Loss is within the Original Policy Period and that the Original Policy Period Start date is within Insured Period.

Workaround:

Root Cause:

Extent of Impact:

Impact on Existing Data

Recovery Method for Existing Data Affected

Problem:
Technical Worksheet Accuracy rules for reinstatement is performed although calculation rule is No Automatic Calculation.

Solution:
Technical Worksheet Accuracy rules for reinstatement should not be performed when calculation rule is No Automatic Calculation.

Workaround:

Root Cause:

Extent of Impact:

Impact on Existing Data

Recovery Method for Existing Data Affected

Problem:
When validating combined AAL the system uses an incorrect query - and load every single claim, balance and detail on a contract one at a time

Solution:
Rewrite as per existing validations to use query sum, not load up every single claim, balance and detail on a contract one at a time.

Workaround:

Root Cause:
SE-3512

Extent of Impact:

Impact on Existing Data

Recovery Method for Existing Data Affected

Problem:
The reinstatement accuracy computed amount does not consider accounting period to dates.

Solution:
When the reinstatement premium calculation per insured period considers the accounting period dates, the accuracy computed amount must do the same. The computed amount should be the same as the result of the automatic calculation.

Workaround:

Root Cause:
SE-3510

Extent of Impact:

Impact on Existing Data

Recovery Method for Existing Data Affected

Problem:
Abend when validating worksheet entries when having booked reinstatement brokerage and brokerage deduction basis has not been defined on deduction condition.

Solution:
When deduction condition does not have deduction basis defined for brokerage, and reinstatement condition has defined brokerage, the system cannot calculate the brokerage. When validating the entries through accuracy (and reinstatement brokerage rule is included), the rule must set an error - computed amount is zero.

Workaround:
Define brokerage deduction basis; for example 'Gross Premium'.

Root Cause:

Extent of Impact:

Impact on Existing Data

Recovery Method for Existing Data Affected

Problem:
Duplicate technical worksheets can be created more than once for multi balance worksheets

Solution:
Prevent creation of duplicate worksheets if one already has been created, also for multi balances worksheets

Workaround:

Root Cause:

Extent of Impact:

Impact on Existing Data

Recovery Method for Existing Data Affected

Problem:
Reinstatement premium amount rule computed value considers booked reinstatement on other section

Solution:
When claim and premium is booked on child section, the reinstatement premium amount rule must only consider amounts on the section on which premium is calculated, as is the result of the automatic reinstatement calculation.

Workaround:

Root Cause:
SE-3510

Extent of Impact:

Impact on Existing Data

Recovery Method for Existing Data Affected

Problem:
Missing date of loss validation on facultative business (proportional and non-proportional) when claim basis is risks attaching and Administration condition is recorded and system parameter Do Not Validate OPP for Losses Occurring is cleared

Solution:
The system must validate that the loss date is within the Original Policy Period, and the OPP start is within the Insured Period.

Workaround:

Root Cause:

Extent of Impact:

Impact on Existing Data

Recovery Method for Existing Data Affected

Problem:
When booking premium and no brokerage, the system raises validation errors for both brokerage-deduction, and brokerage-reinstatement.

Solution:
When booking regular premium/adjustment (and no reinstatement entry codes are present in the worksheet), only the brokerage-deduction rule should be raised, when booking reinstatement premium (and no premium entry codes are present in the worksheet), only the reinstatement-brokerage rule should be raised.

Workaround:

Root Cause:
SE-6709

Extent of Impact:

Impact on Existing Data

Recovery Method for Existing Data Affected

Problem:
Duplicate Technical Worksheets are created as Claim Balances instead of Tecnical Balances, and cannot be found using Find Worksheet using type 'Technical'

Solution:
Duplicate technical worksheets must be created as technical balances.
Workaround:

Root Cause:
SE-2567

Extent of Impact:

Impact on Existing Data

Recovery Method for Existing Data Affected

Problem:
New adjustment flag on message is set to false when there is a previous message on same as of date, which is a subset of current message

Suggested Solution:
UC 5.1.20 and 5.2.111 specify that the new adjustment flag is set to true if new message contains additional amtItems.

Workaround:
If the message is not Processed automatically then you can manually de-link the prior adjustment booking. If no prior booking is linked then having an override on the ClaimAdjustmentCMReferenceRule allows worksheet generation.

Root Cause:
Incorrect match test in CheckForExistingBooking and ClaimAdjustmentCMReferenceRule.

Extent of Impact:
CM with 'previous booking' on same as-of-date with that previous booking being a matching sub-set of the new CM bookings.
The additional bookings on the new CM are not booked.

Impact on Existing Data

Recovery Method for Existing Data Affected

Problem:
If a ClaimMovement message has claim_no_amounts indicarot then a Worksheet may still be created via Swap to Worksheet and left open.
If the message is subsequently Processed it goes stright through to Processed without a) Waiting Aprroval if set to do so and/or b) Does not Close the Claim Worksheet.
This results in a Claim Worksheet being left open and upon trying to Close stops with the Message that a linked eMessage is Waiting Apporval (although it is in Processed state)

Solution:
If a Claim Movement Message has claim_no_amounts it should Require Aprroval and go into Waiting Approval status regardless of it making any booking.

Workaround:

Root Cause:

Extent of Impact:
Waisting Apporval functionality in use and
ClaimMovement messages with claim_no_amounts indicator set but actually having amounts and using Swap to Worksheet. to crreate an open worksheet

Impact on Existing Data
Impossible to Close a Claim Worksheet linked to an eMessage that is Waiting Aprroval but in Processed status.

Recovery Method for Existing Data Affected

Problem:
eMessaging accuracy fails to consider claim limits created by message when validating SOC limit

Solution:
The claim accuracy must consider the claim limit created by message when validating SOC limit

Workaround:

Root Cause:

Extent of Impact:

Impact on Existing Data

Recovery Method for Existing Data Affected

Problem:
Invalid message element included in XIS messages - non 100% <BrokerSharePercentage> when amounts expressed as 100% of Cede

Solution:
SICS should ignore the invalid broker share supplied and treat as 100%

Workaround:

Root Cause:

Extent of Impact:

Impact on Existing Data

Recovery Method for Existing Data Affected

Problem:
System applies ratio to reserve adjustment instead of reserve balance when calculating loss and annuity reserve on follower

Solution:
The system should apply the ratios to the distributed reserve NEW amount (balance) for the layer; and calculate the new amount based on this, and the adjustment amount as calculated new less previous.

Workaround:

Root Cause:

Extent of Impact:

Impact on Existing Data

Recovery Method for Existing Data Affected

Problem:
Validating a TechAccount message abends on a query in the InsuredPeriodReferenceRule due to a # character in a lookup value

Solution:
The query should be correctly perfomed without abend regardless of the value content

Workaround:

Root Cause:
Custom Join queries perfoming a query on a value that contains a # character.

Extent of Impact:
Mostly a few eMessaging queries on Insured Period References and Claim References

Impact on Existing Data

Recovery Method for Existing Data Affected

Problem:
When processing an eMessaging TechAccount and system finds an error due to Government Tax, an error message is presented on Problems tab and Override can incorrectly be done on Problems tab.

Solution:
Must not be possible to override Government Tax error messages from the Problems tab, override must only be allowed on the Government Tax tab.

Workaround:

1. Validate the TechAccount
2. Swap to Worksheet
3. Check the Gov Tax Details/Make Gov Tax Details
4. Change Status - system will issue error message(s) due to Government Tax if error(s) is(are) found
5. Select 'UNFI'
6. Check the Government Tax tab on TechAccount which is updated with error message(s) due to Government Tax
7. Override on Government Tax tab
8. Swap to Worksheet
9. Change Status to Close Worksheet

Root Cause:

Extent of Impact:

Impact on Existing Data

Recovery Method for Existing Data Affected

Problem:
The system does not seem to consider the Government Tax Bookings for the liquid balance on the worksheet

Solution:
When the flag 'Automatic Booking' in the Government Tax table is NOT selected for these Gov Tax rules and 'Automatic Booking of Government Tax' is performed or details manually added then the bookings should be added to the existing eMessage balance and not split out into another balance.

Workaround:

Root Cause:

Extent of Impact:

Impact on Existing Data

Recovery Method for Existing Data Affected

Problem:
TA invoice message finds incorrect claim via Loss Date where there is another Claim with the same Sender / Cedent Claim Reference. Either it should have referenced via Linked by Sender Claim Reference or raised error on multiple loss date match.

As there is a Referred Message CedentReference and a Claim Reference both are being identified as a Cedent Claim Reference and thus not populated on the message data for the Sender/Cedent as Sender Claim Reference.

Solution:
Ensure that a Unique to message Sender when Cedent ClaimReference is populated on the message data table i.e. only Extract SenderReference from a Claim record. This allows reference to claim via Sender as Cedent Claim Reference.

When performing the query for Claims via Loss date do not ignore any that have a UCR. The London Market UCR test is only for the case when the query returns just one match, not multiple.

Workaround:
Progrss the CM to at least create a worksheet at which point the TA would link via the CM links.
Remove (claim references from inactive claims.

Root Cause:
Incorrect extraction / non-population of message data for Participant when sender is Cedent for Claim Reference (when there is also a <ReferredClaimMovement>CedentReference ) as the system thinks the claim reference is not a singleton.

Query on Loss Date incorrectly excluded claims that had a UCR. This should just be a post query test when only one match returned. UCR is a London Market Service Provider Field and should not be populated on a B2B claim.

Extent of Impact:
The TA may link to the wrong claim or not at all when it could.

Impact on Existing Data

Recovery Method for Existing Data Affected

Problem:
Claim Creation rule abends if Insured Period is referenced but no Section and Check for Contract Registration Complete is required.

Solution:
Ensure that the rule functions correctly if there is Insured Period but no Section Referenced.

Workaround:
Validate the message so it can be manually referenced.

Root Cause:
Requirement for Registration Complete on Insured Period

Extent of Impact:
ClaimMovement message with Check for Contract Registration Complete on Insured Period and Insured Period Referenced but no Section due to inability to reference to a specific Section when multiple child sections available (i.e. not Default).

Impact on Existing Data

Recovery Method for Existing Data Affected

Problem:
If a ClaimMovement message has claim_no_amounts indicarot then a Worksheet may still be created via Swap to Worksheet and left open.
If the message is subsequently Processed it goes stright through to Processed without a) Waiting Aprroval if set to do so and/or b) Does not Close the Claim Worksheet.
This results in a Claim Worksheet being left open and upon trying to Close stops with the Message that a linked eMessage is Waiting Apporval (although it is in Processed state)

Solution:
If a Claim Movement Message has claim_no_amounts it should Require Aprroval and go into Waiting Approval status regardless of it making any booking. Approval may be grated without the need for any worksheet to be created manually.

Workaround:

Root Cause:

Extent of Impact:
Waisting Apporval functionality in use and
ClaimMovement messages with claim_no_amounts indicator set but actually having amounts and using Swap to Worksheet. to crreate an open worksheet

Impact on Existing Data
Impossible to Close a Claim Worksheet linked to an eMessage that is Waiting Aprroval but in Processed status.

Recovery Method for Existing Data Affected

Problem:
Checking if tax bookings should be excluded from hash validation even if they are mapped – for the case when they are not originating from an eMessage is incorrect which results in them being included when they should not be (i.e. also when they are not actually flagged).

Solution:
Detail bookings should never be included in the summed value to compare with the control amount if they are not flagged on the EC mapping.
If there is a Gov Tax rule that is set not to book automatically then irrespective of EC mapping, a detail should not be included.

Workaround:
Override the Rule on the message.

Root Cause:

Extent of Impact:

Impact on Existing Data

Recovery Method for Existing Data Affected

Problem:
Existing CM with previous amounts abends on CheckPreviouslyPaidAmountOnSicsClaim if no Claim Section is referenced

Solution:
If no Claim Section is referenced then the CheckPreviouslyPaidAmountOnSicsClaim rule should simply exit.

Workaround:
Set ClaimReferenceRule to Halt Processing on Error
or on case by case basis, ensure message will automatically reference to Claim Section.

Root Cause:
Existing CM that contains previous amounts for validation but is not automatically referencing to a claim section.

Extent of Impact:

Impact on Existing Data

Recovery Method for Existing Data Affected

Problem:
claim_no_amounts messages are considered in the search for previous CM in LinkCMtoCMReferenceRule which results in 'Previous adjustment not closed' (when no booking was made).

Solution:
In the B2B, ILU and Lloyds (non-sequencing) Link step, skip over claim_no_amounts message(s) - irrespective of any manual adjustment created - to ensure that any message linked has / will create an adjustment.

Workaround:
Do not process messages that will do nothing but rather identify and set to Information state.

Root Cause:
Processing a message that is claim_no_amounts

Extent of Impact:

Impact on Existing Data

Recovery Method for Existing Data Affected

Problem:
Lloyds TA Treaty statement with claim payment does not locate CM via ReferRelatedMessagesBySigningReferenceRule

Solution:
The rule is to link a TA to a CM. It does not apply for CM to CM and should function as specified in UC 5.1.10

Workaround:
Once the CM has created a booking it may automatically link via that on validation, otherwise manually link to a claim adjustment (from the CM)

Root Cause:

Extent of Impact:
Lloyds TA with claim payments (more of an issue on Treaty Statements with not claim link as link must be made to a CM or the booking of CM).

Impact on Existing Data

Recovery Method for Existing Data Affected

Problem:

GL_BALANCE. BYRPP wrong in GL Universe

Solution:

Object corrected.

Workaround:

Root Cause:

Extent of Impact:

Impact on Existing Data

Recovery Method for Existing Data Affected

Problem:

Solution:

Workaround:

Root Cause:

Extent of Impact:

Impact on Existing Data

Recovery Method for Existing Data Affected

Problem:
Max Loss Ratio object for Stepped Sliding Scale not correct in SPC and missing in OPC

Solution:
Object corrected in SPC and added to OPC

Workaround:

Root Cause:

Extent of Impact:

Impact on Existing Data

Recovery Method for Existing Data Affected

Problem:
Latest FGU Information
Solution:

Made sure that FGU advices done on same date are sorted,

Workaround:

Root Cause:

Extent of Impact:

Impact on Existing Data

Recovery Method for Existing Data Affected

Problem:
Extract on claim status together with accounting data

Solution:

New object for latest claim status

Workaround:

Root Cause:

Extent of Impact:

Impact on Existing Data

Recovery Method for Existing Data Affected

Problem:

Claim FGI As Of date object returns the date

Solution:

Changes to return atimestamp

Workaround:

Root Cause:

Extent of Impact:

Impact on Existing Data

Recovery Method for Existing Data Affected

Problem:
Remittance settle 2 or more balances. Settled amount will show only one of the balances for functional currency.

Solution:

Object corrected to show the total settled amount including all balances,

Workaround:

Root Cause:

Extent of Impact:

Impact on Existing Data

Recovery Method for Existing Data Affected

Problem:
Balance Report and BOAC_SETT_WITHOUT_PAIR is to be compatible.
Causing Cartesian product error.

Solution:

Table set to be NOT compatible with Balance Report.

Workaround:

Root Cause:

Extent of Impact:

Impact on Existing Data

Recovery Method for Existing Data Affected

Problem:
SICS Version field too small
Solution:

*Increase the version field

Workaround:

Root Cause:

Extent of Impact:

Impact on Existing Data

Recovery Method for Existing Data Affected

Problem:
OCC ID in reports where you extract OIP and/or ORP

Solution:

Get real ID instead of assumed ID based on ORP id.

Workaround:

Root Cause:

Extent of Impact:

Impact on Existing Data

Recovery Method for Existing Data Affected

Problem:
Base Company ID according to LOB from reporting table

Solution:

Corresponsing solution as for base company name
Workaround:

Root Cause:

Extent of Impact:

Impact on Existing Data

Recovery Method for Existing Data Affected

Problem:
Cede Universe tuning

Solution:
Naming of objects made consistent.

Workaround:

Root Cause:

Extent of Impact:

Impact on Existing Data

Recovery Method for Existing Data Affected

Problem:

When a user tries on a Cedent's Program to Mass Renewal multiple participating assumed businesses, the system does not stop the user even though the security settings for the user do not allow renewal. 

Solution:

When a user tries to mass renewal businesses in a cedent's program, and the security domain restrictions do not allow renewal, the system should stop the user.

Workaround:

Root Cause:

Extent of Impact:

Impact on Existing Data

Recovery Method for Existing Data Affected

Problem:
Possible to enter too long name of security role.

Solution:
When entering “Name” on a new (screen ‘Create User Role’) or existing (screen ‘Edit User Role Details’) User Role, the system should allow recording only 30 characters as per designed. In case user tries to enter more than 30 characters, then the “Name” field must become red and system must not allow the user to continue recording 31st character.

Workaround:
Save the User Role once it is created with its Name only and without entering any other Role details like assigning Use Cases, Domain Restrictions or Members. Then open the new Role in edit mode and continue entering its Details (Use Cases, Domain Restrictions or Members).

Root Cause:

Extent of Impact:

Impact on Existing Data

Recovery Method for Existing Data Affected

Problem:
Executing a large createFastTechnicalWorksheet request (~150MB SOAP message) takes a long time.

Solution:

Optimize the createFastTechnicalWorksheet web service by reducing the number of SQL statements, and by implementing caching of resolved SICS objects in the resolver part of the de-serialization phase of the soap request message-processing.

What is characteristic with this web service is that it is a repetitive in nature, in some cases reading the same SICS object many times in the de-serialization phase. For example, a single business or entry code might be referred by many details in the soap request.

Workaround:

None

Root Cause:

None

Extent of Impact:

None

Impact on Existing Data

None

Recovery Method for Existing Data Affected

None

Problem:
Logged exception after creation of claim worksheet in SICS Server. As Sics Server silently logs ingored exceptions, the size of the file increases over a period of time and that is impacting performance of SICS Server.

Solution:
There should not be an exception after creating a claim worksheet in SICS Server.

Workaround:
Turn off the logging of IgnoredExceptions

SICS Sever log4j2.xml
<!-- Logging of exceptions that are caught and ignored -->
<Logger name='IgnoredExceptions' level='off' />

Root Cause:
Trapped exception logged by SICS Server.

Extent of Impact:

Impact on Existing Data

Recovery Method for Existing Data Affected

Problem:
Poor performance when adding a new claim to an existing risk claim.

Solution:

Improve technical approach for processing of Recovery bookings of Outward Claims

Workaround:

None

Root Cause:

Extent of Impact:

Impact on Existing Data

Recovery Method for Existing Data Affected

Problem:
Incorrect calculation of Premium in Underwriters Estimates on child sections when premium type = Flat Premium

Occurs when the main Premium & Limit condition is inherited, but the Instalment premium condition is not inherited. 

Relates to calculation variable %premiumIncomeAmount and calculation function ( #FUNC getPremiumAmountForOptionCode: 'GROSS_PREM'   'Total Gross Premium'  )

Solution:
Make sure the above mentioned variable and function captures the Flat Premium amount from the correct section. 

Workaround:

Break inheritance on the main Premium and Limit condition

Root Cause:

Extent of Impact:

Impact on Existing Data

Recovery Method for Existing Data Affected

Problem:
Cannot remove business Classifications via web service due to message BS0830

Solution:
Message BS0830 must not be raised when executing web service updateBusiness which is removing business Classifications.
Instead, the changes should be checked and accepted by the system when they are meeting the system settings , just like the system does when the operation is executed online.

Workaround:
Update business Classifications via SICS online

Root Cause:
SE-3029

Extent of Impact:

Impact on Existing Data

Recovery Method for Existing Data Affected

Problem:
MTK- Abend while migrating Single Treaty Protection

Solution:
It should be possible to load Single Treaty Protection Outward Cedent's Contract via Migration Tool Kit without any abend

Workaround:

Root Cause:

Extent of Impact:

Impact on Existing Data

Recovery Method for Existing Data Affected

Problem:
When the ADH setting 'Process on Load' is selected, importing multiple documents sometimes fails.
This is related to documents that use a mapping which contains a 'Claim Ledger Figures - Domain Data' block.

Solution:
The 'Claim Ledger Figures - Domain Data' block reuse the Claim - Claim Ledger online accounting statistics logic. The purpose is to extract the claim ledger figures for use in the DD block. However, the online logic contains async refresh logic that may cause issues with concurrent modification when multiple documents are imported in ADH. The solution is to avoid the [unnecessary] UI refresh logic when data is retrieved by ADH.

Workaround:
Unselect 'Process on Load' and transform imported documents manually.

Root Cause:

Extent of Impact:

Impact on Existing Data

Recovery Method for Existing Data Affected

Problem:
SICS works slow for Multi GAAP Recalculation Order with large data volume

Solution:
Improve the performance of Multi GAAP Recalculation Order.

Workaround:

Root Cause:

Extent of Impact:

Impact on Existing Data

Recovery Method for Existing Data Affected

Problem:
When importing an Excel spreadsheet into ADH, numbers are formatted according to the cell's number format and the computer's locale. There are scenarios where this does not work correctly. For example, assume the number format is set to use thousand separator and no decimals, and the locale is US. In this case, the number 123456 will be formatted as 123,456 which ADH thinks means 123 plus 0.456

Solution:
Import numbers without applying formatting.

Workaround:
None

Root Cause:

Extent of Impact:

Impact on Existing Data

Recovery Method for Existing Data Affected

Problem:
ADH mapping export does not include the 'sub document' setting and a few others. This means that when importing such an xml export file, the resulting mapping will not be identical to the original one.

Solution:
Make sure to include all attributes/settings when exporting a mapping. This used to work.

Workaround:

Root Cause:

Extent of Impact:

Impact on Existing Data

Recovery Method for Existing Data Affected

Problem:
ADH mappings - When 'sub document' is defined on a mapping, input data augmenting by way of indexing a Domain Data block does not work correctly. Instead of N input positions we get N*N.

Solution:
We should get N input positions, as we do when the mapping does not use 'sub documents'.

Workaround:
Do not use 'sub documents'.

Root Cause:

Extent of Impact:

Impact on Existing Data

Recovery Method for Existing Data Affected

Problem:

Abend in Underwriters Estimation Calculation Order when the Exclude option is selected in the business list container, but no business is selected

Solution:

Make sure the Exclude option is disabled when no business is selected.

Workaround:

Select one or several businesses before you select the Exclude option

Root Cause:

Extent of Impact:

Impact on Existing Data

Recovery Method for Existing Data Affected

Problem:

Multi GAAP calculation variable %claimBasis gives error when used on Facultative and Direct business

Solution:

Make sure the variable also works for Facultative and Direct business

Workaround:

None

Root Cause:

Extent of Impact:

Impact on Existing Data

Recovery Method for Existing Data Affected

Aim of function

Accounting Reviewer wants to verify if the data input is correct, that is to verify the information of Section and Accounting Classification.

For the technical worksheet or claim worksheet in pending status, system now offers showing available Sections and Accounting Classifications in new window for the selected balance detail. Modification of Sections and Accounting Classifications in the new window will not change the actual values of Section and Accounting Classification on the highlighted detail. 

System Parameters Affected

N/A

Existing functionality affected

View balance details

Aim of function

When changing the Insured Period Start Date or Underwriting Year on the Insured Period tab on a business, when the below new system parameter is checked, and if the Assumed Business or Outward Cedent's Contract has actual bookings or estimates that do not sums up to zero for the actual Insured Period, an error message is raised:
'Change of IP/UW Year not allowed because actual bookings or estimates exist and does not sum up to zero. These must be reversed before the change can be made' so that the changes cannot be saved.

The zero check is performed by aggregating details linked to the actual Insured Period with same Currency, Entry Code, Section, Accounting Classification and Actual/Estimate flag.

System Parameters Affected

A new system parameter Change of IP/UW Year not allowed if Unsettled Bookings exists is added and if this system parameter is checked the system will check if bookings on this insured period does not sum up to zero, both Actual bookings and Estimates. 
This system parameter is unselected as default.

Existing functionality affected

• Assumed Business  Edit Insured period
• Outward Cedent's Contract  Edit Insured period

Aim of function
The aim of the function is to be able to aggregate booking details produced by the Retrocession Calculation Order, the Retrocession Account Order and the Retrocession Estimation Calculation Order according to the sign of the details so that the Functional Currency Amount always is shown with the same sign as its original amount.

System Parameters Affected

A new Accounting/Retrocession/General system parameter is introduced;

• 'Aggregate by sign in REAC'.

Existing functionality affected

• Retrocession Calculation Order
• Retrocession Account Order
• Retrocession Estimation Calculation Order

Aim of function

Added new element called Entrycode term in entry point SicsWsBusinessEntryPoint and select either the service operations createAccountsCommonConditions or updateAccountsCommonConditions.

Now user can create and update the Entry Code Transformation Term' field on administration condition via web service interface.

By executing these soaps the “createAccountsCommonConditions” or the “UpdateAccountsCommonConditions” with the new element the system will validate the existence of the given term and set it in the Entry Code Transformation Term if it exists. It will overwrite the already given term on the conditions. This information will only be used and set on businesses where it is relevant, i.e. where the Entry Code Transformation Term field exists and can be given manual.

System Parameters Affected

None

Existing functionality affected

Currently, SICS can not update the 'Entry Code Transformation Term' field on the administration condition->Currencies page via web service interface. There is no field for entryCodeTerm in complex type 'AccountsCommonCondition'.

Aim of function

To speed up the facultative protection placing process, it is advantageous to be able to create multiple protections simultaneously.  SICS therefore now offers an option of creating multiple non-proportional facultative protections in one go, in a similar way as it earlier did only for proportional facultative protections. 

 
System Parameters Affected

None

Existing functionality affected

Protect Business
Create Business
Maintain Share Conditions
Assign Business Partner Role
Assign Account Groups
Protect Business by Web Service

Aim of function

Most companies need a contract amendment to be linked only to those terms and conditions that changed as part of this amendment. Some companies have however other applications than SICS that work with complete versions after each contract amendment. To interface, the task for these could be easier if in SICS, all existing conditions were automatically linked upon creation of an amendment.

SICS will therefore offer an optional automatic amendment facility. For the current release however, only the set-up feature is available.  This is for activating the automatic amend contract information and for selecting which groups of information should be auto amended and which should not. 

System Parameters Affected

None

Existing functionality affected

None

Aim of function

When mass renewing businesses and the Security Domain Restriction ‘Business Structure’ is set up to restrict renewal, the system now checks the Domain Restriction Filters towards the businesses being renewed, (e.g. Assumed Business or Retrocessionaire’s Participations) and not towards the parent business (e.g. Program or Outwards Cedent’s Contract).

System Parameters Affected

None

Existing functionality affected

Mass Renew Assumed Businesses in Reinsurance Program
Mass Renew Assumed Businesses in Cedent's Program
Mass Renew Assumed Businesses in Master Agreement 
Mass Renew Assumed Businesses in Insured's Contract
Mass Renew Retrocessionaires in Outward Cedent's Contract
Mass Renew Intermediaries in Outward Cedent's Contract
Mass Renew of Outwards Cedent's Contracts in Protection Program

Aim of function

A new Security Use Case specific to Deductibles Conditions has been implemented, as this was missing.  All Business Conditions now have their own specific Security Use Case. 

When a Security User Role has this use case set up with access right Update = N and Create = N for example, and a user assigned to this role tries to create or edit Deductibles Conditions, the system stops the user.  

System Parameters Affected

None

Existing functionality affected

Manage Security 
Maintain Deductibles Conditions
Update Business 
Maintain Conditions from Section Overview
Maintain Cedent's Program Contract Overview
Update Deductibles Conditions by Web Service

Aim of function

In order to clearly see which Base company the claim relates to, a new column shall be added to the Find Claims result container, displaying the Base Company identifier. The identifier is only displayed when search option is Business identifier.

System Parameters affected:

None

Existing functionality affected:

Find Claims

Aim of function

The As of Date on the FGU advisory should default to message creation date, instead of the message As of Date. The current default creates inefficiency because there could be other FGU activity already booked before the message is received so the Own Incurred might not match the message

System Parameters affected

 New emessaging rule on Message Layer; ModifyClaimFGUAsOfDate rule.

Existing functionality

Validate and process Claim Movement message

Aim of function
From the Find: eMessaging Messages window you can export message information into a csv file.

For export of ACORD Claim Movement messages, we have added 6 new elements that can be included. All elements relate to Claim Movement Amount Items

System Parameters affected

None

Existing functionality

Export eMessaging Message data to a csv file

Aim of function

Support MySQL 5.7+ and compatible platforms including AWS Aurora MySQL, MariaDB 10.2+

The additional DBMS platform support increases our Cloud deployment options and lowers the total cost of ownership.

System parameters affected
None.

Existing functionality affected
All DBMS configuration related functions

Aim of function

When setting up calculation rules in Multi GAAP system parameters, the system has given an error message if you create a rule which will cause circularity in the calculation chain. However, in some situations the error is given also when there is actually no circularity, e.g. if you refer to the same estimation item as being calculated for a previous period. Also, there has been no information as to what causes the circularity.

We have changed the error message to a warning, and added some information on which reference and which rule is creating the potential circularity. The rule may be a different rule than the one you try to save, if this refers to an estimation with a rule which already has a potential circularity, as in the example shown below.

System Parameters Affected

None

Existing functionality affected

Create and modify Multi GAAP Calculation Rules

Aim of function

To be able to use webservice to create Multi GAAP Accounting Order in both SICS Life and SICS P&C.__

System Parameters Affected

None

Existing functionality affected

SicsWsBatchProcessEntryPoint：

      Add new Service: createAccountingOrder

Aim of function:
In Underwriters Estimates calculation rules, added the following new functions:

Date functions:

• The day of a date - retrieving the day in the month of a given date
• The month of a date - retrieving the month number from a given date
• The Year of a date - retieving the year from a given date

Number function:

• Modulo - Retrieving remainder when one value is divided by another value

In Multi GAAP calculation rules, the above date functions have been made available to select from the Date functions folder. Previously they had to be manually written into the calculation rule.

System parameters affected

New functions available in Underwriter estimates and Multi GAAP calculation rules as described above

Existing functionality affected:
Define calculation rules in for Underwriters Estimates and Multi GAAP
Calculate Underwriters Estimates