Problem:
Incorrect distribution of reinstatement booking to retrocessionaires when Special Premium is selected at OCC level. Latest retrocessionaire in the placement list gets entire amount distributed when doing second and subsequent calculation of reinstatement.

Solution:
When Special Premium is selected at OCC, there is an option to create special premium conditions at ORP level. When calculating Reinstatement Premium these special conditions must be considered - using the correct premium for the reinstatement premium calculation at ORP level. Calculated Reinstatement Premium at ORP level is added together and reflected as a total amount at OCC level.
When having booked 1st reinstatement premium for a Claim, and the second is due - the system must consider already booked figures at ORP level - and book the difference. This must be done both for paid reinstatement and reinstatement reserve.

Workaround:
None

Root Cause:

Extent of Impact:

Impact on Existing Data

Recovery Method for Existing Data Affected

Problem:
Description of Account not kept as original when running REAC

Solution:
When system parameter 'Keep Description of Account As Original' and one or more descriptions are selected, the Description of Account on the As Original details should be kept on the As Booking details, also when the Retrocession Calculation Order is run with Balance Split Option 'Split By Description Of Account' is cleared

Workaround:

Root Cause:

Extent of Impact:

Impact on Existing Data

Recovery Method for Existing Data Affected

Problem:
Please change the SICSR-17982 solution as follows;

Solution:
When using the function 'Revoke' through the Business Mass Commutation order (Periodic Functions) only businesses with Commutation Status 'In Progress' or 'Revoked and In Progress'(Partners tab) must be updated

Workaround:
Business Mass Commutation order, Function 'Revoke';
Exclude business Insured Periods with Commutation Status different from 'In Progress' from the Business Mass Commutation Order before pressing the 'Mass Update' button

Root Cause:

Extent of Impact:

Impact on Existing Data

Recovery Method for Existing Data Affected

Problem:
Hard Stop not recognized (Charges and Sliding Scale commission)

Solution:
When the operation take place to navigate directly to the worksheet closing window from Find Worksheet window or from Select Open Worksheet window, the system must perform the accuracy validation in the 'background' and raise a new error message if any of the accuracy validations fails, telling the user that this worksheet cannot be closed directly but have to be opened in edit mode to check the accuracy validation errors.

Workaround:

Root Cause:

Extent of Impact:

Impact on Existing Data

Recovery Method for Existing Data Affected

Problem:
Performance problem - UE Recalculation Order

Solution:

Batch reading process changed.

Added Progress log on Underwriters Estimation Calculation Order

Workaround:

Root Cause:

Extent of Impact:

Impact on Existing Data

Recovery Method for Existing Data Affected

Problem:
SICS_No PBR generated for bookings done (05.03.2021)_PID 8220997

Solution:
When the PBR for Change of Loss Incurred is executed and the actual rule to be used is identified, then the system check the Closed Date on the checked worksheet against the Cut-off dates in this rule. If the Closed Date is found to be the same as a Cut-off date, then we must make sure the system check all worksheets with a Closed Date in a range of 1 day higher than the previous Cut-off date up to and including the matching Cut-off date.
Example:
If the Cut-off dates are like this
1: 01.01.2020
2: 31.03.2020
3: 30.06.2020
4: 30.09.2020
5: 31.12.2020
then the system will find the following time span for the worksheet to be checked with a Closed Date 30.09.2020: The worksheets to be included to find if Loss Incurred is booked must have a Closed Date > 30.06.2020 and <= 30.09.2020.

This is working fine in Oracle, and this must also be corrected to work in SQL Server databases.

Workaround:
Add one day to the Cut-off days in the PBR rules

Root Cause:

Extent of Impact:

Impact on Existing Data

Recovery Method for Existing Data Affected

Problem:

After importing ESPID table, generated Accounting Classification (AC) – this is resulting in duplicate row having M & D premium % as 0.00 against each accounting classification.

Solution:
When an ESPID table is attached and ACs are generated from that on the M&D conditions, the system must prevent making duplicate AC rows with zero split percentages. Only real rows from the ESPID table shall be generated as AC rows on the AC Spit % tab.

Workaround:
Delete the unwanted duplicates manually, one by one.

Root Cause:

Extent of Impact:

Impact on Existing Data

Recovery Method for Existing Data Affected

Problem:
CL WS System triggered auto book of Gov. Tax not working if previous amount for Trigger EC is available

Solution:
On Technical Worksheet or Claim Worksheet, when the user applies the worksheet to the database, e.g. by Apply or Change Status, and the system check if any Government Tax Rules with Automatic Booking selected is triggered, then the system must perform this automatic booking of the target Government Tax detail 1) if the target Government Tax detail is NOT present on the worksheet (existing functionality) or 2) if the target Government Tax detail IS present, but the adjustment Amount is blank or zero (new functionality).
One exception to the 2) above; if the target Government Tax detail is present with the Amount as zero AND it is linked to the trigger detail, then the automatic booking shall still not be performed.

Workaround:
Delete the target Government Tax detail before Apply/Change Status

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 a target Government Tax details has been linked to the trigger detail on a worksheet (technical or claim), and a deviation error is found when the worksheet is applied to the database (Validation error AC0843 appears), and the user recalculates the Government Tax detail with the option Automatic Booking of Government Tax, we must make sure the system also recalculates the balance this Government Tax belongs to.
This is correct when there is no target Government Tax on the worksheet from before, when the Automatic Booking of Government Tax is done, then the balance is correctly updated with this new detail.

Workaround:
1. either tick and untick the Balance Split option for Government Tax
2. or delete the wrong target Government Tax detail before the Automatic Booking of Government Tax is selected again

Root Cause:

Extent of Impact:

Impact on Existing Data

Recovery Method for Existing Data Affected

Problem:
Find Accounting Worksheet - Remittance with status In Execution in combination with a From and/or To Date does not work

Solution:
On the Find Accounting Worksheet window, if the user search for balance Type: Remittance, and with Status: In Execution, Planned or Rejected, the system is able to fine these remittances. By searching for Status: In Execution, Planned or Rejected, the system also changes the label for the related From/To date field on the Advanced tab to be In Execution Date, Planned Date and Rejected Date respectively.
But if the user combine this extraction criteria with a From and/or To date in these date fields on the Advanced tab we must make sure the system is able to find also these remittances by using the date when these remittances were changed to these statuses.

Workaround:

Root Cause:

Extent of Impact:

Impact on Existing Data

Recovery Method for Existing Data Affected

Problem:
System Message 'Unable to edit cell' when entering 'TAX Type BY AC' on WS

Solution:
When a Technical Worksheet is opened make sure the column Tax type by AC is hidden in the P&C environment. The Tax type by AC column is a Life specific column and related to Life specific functions.

Workaround:
On the Technical Worksheet, use the Column View to hide the column Tax type by AC, to prevent the user from navigating to this column

Root Cause:
SE-807 in 4.8.6

Extent of Impact:

Impact on Existing Data

Recovery Method for Existing Data Affected

Problem:
Not calculate reversed commission correctly when cut PP assignment to Fac OCC with ECTT defined

Solution:
In the process of changing retroceded share for a Fac OCC on the protection assignment page on the Assumed Business, both when the share is changed or when the Fac OCC is removed from the list, the system will do automatic correction bookings on the actual Fac OCC.
When the system sums up their amounts to be the new amount of the correction booking of this ledger detail the system also use entry code to do the filter, but only pairings of the same entry code as the ledger detail are included.
So additional to existing functionality we must also include pairing where the details have different entry codes, if they are found in the Entry Code Transformation Terms on the Fac OCC.

Workaround:

Root Cause:

Extent of Impact:

Impact on Existing Data

Recovery Method for Existing Data Affected

Problem:
Business Ledger 'Generic find in …..' does not present expected results as empty values included

Solution:
For container tables a null value should not be selected unless the search is for empty.

Workaround:

Root Cause:

Extent of Impact:
SQL Server, Generic Find in

Impact on Existing Data

Recovery Method for Existing Data Affected

Problem:
ABEND when I create a new 'Open Worksheet Mass Update' with Additional Classification.

Solution:
It should be possible to select a value from all Additional Classification types in the Open Worksheet Mass Update order.

Workaround:

Root Cause:

Extent of Impact:

Impact on Existing Data

Recovery Method for Existing Data Affected

Problem:

Validation error BC0056 - mandatory information is missing - is incorrectly given in Internal Premium Reserve Condition on Outward Cedent's Contract.

When Calculation Method = Pro Rata Temporis is selected for Original Premium Reserve, the message is given even if all information is entered.

Solution:

Make sure no validation error is given when all mandatory information is entered

Declination Reason:

Workaround:

Root Cause:

Extent of Impact:

Impact on Existing Data

Recovery Method for Existing Data Affected

Problem:
Periodic Function “Mass Pairing Of Paid Remittances” abends when parameter 'Validate BYRP in Balance Pairing' is ON and BYrPer of paired Balance is outside allowed period of <Default Settings>

Solution:
When the user performs the Mass Pairing Of Paid Remittances and the system is trying to do a pairing where the included balance has a Booking Year/Period higher than the Default settings for Remittances for the actual Base Company, then this pairing cannot be performed and must therefore be skipped so that the process can continue with the remaining available pairings.

Workaround:

Root Cause:

Extent of Impact:

Impact on Existing Data

Recovery Method for Existing Data Affected

Problem:
Revaluation behavior is different between v4.6 and SICS20.

Solution:
Change the effect of the system parameter 'Exclude Partially Released Deposit from FC Revaluation' so that if this is selected in combination with the system parameter 'Include Realized Gain/Loss In FC Revaluation' NOT selected, then the system shall revaluate also Released Deposit details in Unsettled Balances.

Workaround:

Root Cause:
Caused by SICSR-12440 corrected in version 4.9.1 where we introduced revaluation of partially released deposit (and also changed the logic for released deposit so that it was no longer revaluated in Unsettled balances).
The new system parameter 'Exclude Partially Released Deposit from FC Revaluation' was introduced in 20.2 by SICSR-18654 to solve the problem with bad performance when we introduced partially released deposits in the revaluation order.

Extent of Impact:

Impact on Existing Data

Recovery Method for Existing Data Affected

Problem:
Revaluation Order Long Execution Time

Solution:
Improve the execution time when running the FC Revaluation order in Oracle databases.

Workaround:

Root Cause:

Extent of Impact:

Impact on Existing Data

Recovery Method for Existing Data Affected

Problem:

Abend running Revised EPI Mass Update Order

Solution:

Remove abend

Workaround:

Root Cause:

Extent of Impact:

Impact on Existing Data

Recovery Method for Existing Data Affected

Problem:
Reinstatement premium incorrectly done to 0% placement when Special premium is selected.

Solution:
When running Outward Reinstatement order and OCC has Special Premium flag activated, the system must comply with a 0% placement correctly; i.e. no reinstatement paid and reserve should be calculated. This must function both when running the first reinstatement order and the subsequent ones.

Workaround:
None

Root Cause:

Extent of Impact:

Impact on Existing Data

Recovery Method for Existing Data Affected

Problem:
The system does not generate preliminary bookings when bulk import more than 250 IAB from OCC side

Solution:
When the Import Assumed Businesses from the Assumed Business list on an OCC, and the file contains of more than 250 Assumed Businesses, we must make sure the system is able to generate preliminary bookings on the OCC for ALL involved Assumed Businesses.

Workaround:
Limit the number of Assumed Businesses the uploading file to less than 250

Root Cause:

Extent of Impact:

Impact on Existing Data

Recovery Method for Existing Data Affected

Problem:
LMM Reference is not populated on worksheets created using fastCreate API although provided in SOAP.

Solution:
The element 'lmmReference' can be removed from all create worksheet services (fastCreateTechnicalWorksheet, fastCreateClaimWorksheet, createWorksheet and createClaimWorksheet), since it is not supported in these services.
The element 'londonMarketReference must be made available in the create technical worksheet services (fastCreateTechnicalWorksheet and createWorksheet), within the XSD Type 'FastAccountingBusinessDetailBalanceEntry'

Workaround:

Root Cause:
Initial development seems as if LMMReference is not covered - see SRZ90493/4 - technical doc

Extent of Impact:

Impact on Existing Data

Recovery Method for Existing Data Affected

Problem:
GOV TAX - Cover Area Excluded with wrong error message

Solution:
Error 1;
Change the text of error message AC0849 to read this:
'Government Taxes to be checked by the user - Cover Area is not specified on Business/Section' when triggered on a technical worksheet
'Government Taxes to be checked by the user - Cover Area is not specified on Claim Location' when triggered on a claim worksheet
Error 2;
In case the rule is defined with Cover Area Excluded and the Classification on the business/IP ONLY contains countries different than the excluded countries in the rule, then the message AC0834 appears correctly if the target EC is not present, but if the Classification on the business contains countries both mentioned in the rule and not mentioned then the message AC0849 should appear telling the user to check the government taxes.

Workaround:

Root Cause:

Extent of Impact:

Impact on Existing Data

Recovery Method for Existing Data Affected

Problem:
AC0403 blocks URB allocation

Solution:
When a Remittance balance replaces the Unallocated Remittance balance (URB) in a balance pairing process, so that the URB becomes Allocated (which means it is 'used'), and the user later annul the Remittance balance from the balance pairing again, then the system replaces the Remittance with the URB in the pairing. The URB becomes Unallocated again and we must make sure the system is able to Start Balance Pairing from this URB as long as the system parameter 'When Pairing, always use Remittances as the driving Balance' is selected.

Workaround:

Root Cause:

Extent of Impact:

Impact on Existing Data

Recovery Method for Existing Data Affected

Problem:
Recon Fact Cash Records - No Wks ID created by Account Balances

Solution:
When an Account Balance Group (ABG) is created from eMessaging, TechAccount, because the worksheet created by the TechAccount contains of more than one balance so that the ABG match the balance in the FA message, we must make sure the ABG gets a balance Identifier take from the system parameters, Accounting, Worksheet, in the same way as when ABGs are created manually.

Workaround:

Root Cause:

Extent of Impact:

Impact on Existing Data

Recovery Method for Existing Data Affected

Problem:
GOV TAX - 'Cover Area Included not working correctly with multiple countries in Cover

Solution:
When a Government Tax Rule is defined with a Country in the Cover Area Included, and this Country contains of States, e.g. United States, and on the business or the claim only a State within this Country, e.g. Alaska, is defined as location, then the system must be able to trigger this rule.

Workaround:
By defining both the Country and the State as location on the business and on the claim, then the system is able to trigger the correct rule.

Root Cause:

Extent of Impact:

Impact on Existing Data

Recovery Method for Existing Data Affected

Problem:
'Revoke Business to be commuted' is displayed even businesses are commuted.

Solution:

Declination Reason:

Workaround:

Root Cause:

Extent of Impact:

Impact on Existing Data

Recovery Method for Existing Data Affected

Problem:
Sub sub section of assumed business can not be found by name when uploading from outward cedent's contract side

Solution:
Outward Cedent's Contract
AB (Assumed Business) button:

When using the ‘Import Assumed Business’ function to upload the Assumed Businesses to a given OCC, if the protection assignment is created between the sub-sub sections (i.e. 2nd.3rd…level child sections) of Assumed Business and OCC section, the system should allow the uploading taking into consideration all current validations.
It should not give the message ‘the section name can not be found’.
Instead, it should establish the protection on sub-sub section of Assumed Business in the same way it currently does when Main Section or Child Section beneath Main Section of Assumed Business are protected.

Furthermore, the established protection must be copied to all child Sections (if any) of the Section that is going to be protected, just like when creating the protection from the Assumed Business.
Currently this works when protecting Main Section of Assumed Business, but does not work when protecting Child Section - e.g. protections are not copied to lower Sections.

Declination Reason:

Workaround:
Manually create the protection starting from the Assumed Business

Root Cause:
SE-3190

Extent of Impact:

Impact on Existing Data

Recovery Method for Existing Data Affected

Problem:

Solution:

Declination Reason:

Workaround:

Root Cause:

Extent of Impact:

Impact on Existing Data

Recovery Method for Existing Data Affected

Problem:
The flag IS_LEAF section is not correctly set on Retrocessionaire Participations when sections are deleted from the Outward Cedent's Contract.

Solution:
When deleting a section on an Outward Cedent's Contract with corresponding deletion of this section on its Retrocessionaire Participations, the 'Is Leaf' flag should be set to Y on the section being parent of the deleted section, both on the OCC (which is currently working correctly) and on the Retrocessionaire Participations.

Workaround:

Root Cause:

Extent of Impact:

Impact on Existing Data

Recovery Method for Existing Data Affected

Problem:
The system abends when summing up a limit amount from a sub section to a parent section, and the sub sections included in the sum have different main currencies.

Solution:
When a limit on a sub section has the Sum Up flag set to Yes, and then selecting Sum Up to Parent and the sections included in the sum have different main currencies, the system should not abend. It should instead convert and summarize the amounts to the main currency of the parent.

Workaround:

Root Cause:

Extent of Impact:

Impact on Existing Data

Recovery Method for Existing Data Affected

Problem:

Underwriters Estimates condition on child section is inherited from the Main Section, causing incorrect estimates on child section

Solution:

Underwriters Estimates condition should never be inherited. Make sure that it is not possible to created an inheritance of this condition

Workaround:

Root Cause:

Extent of Impact:

Impact on Existing Data

Recovery Method for Existing Data Affected

Problem:
When renew Assumed Business via renewBusiness with active <isCeaseAccounting> the SICS Server returns abend instead of renewing the Assumed Business

Solution:
When renewing Assumed Business or Outward Business via web service renewBusiness the system must not abend, but should complete the operation OK even when tag <isCeaseAccounting> is included into the web service call no matter if it is empty or not.

Declination Reason:

Workaround:
Do not use tag <isCeaseAccounting> when renewing Assumed Business via web service renewBusiness

Root Cause:

Extent of Impact:

Impact on Existing Data

Recovery Method for Existing Data Affected

Problem:
Domain retrieval fails

Solution:
Fixed for incomplete PC conditions.

Workaround:

Root Cause:

Extent of Impact:

Impact on Existing Data

Recovery Method for Existing Data Affected

Problem:
Rate On Line on Highlights tab is changed after a full system refresh in case EPI is not calculated based on SUPI*Premium Rate, but is set equal to Minimum Premium

Solution:
Type of Business: Non-Proportional Treaty
Assumed Business, Outward Cedent's Contract, Retrocessionaire Participation

Business Highlights;
'Rate On Line' shown on Highlights tab should always show correct values.
This should be the case when business is opened for the first or any next time or after full system refresh.
Even when EPI is based not on SUPI*Premium Rate, but is set equal to Minimum Premium.
Just like the 'Rate On Line' is correct each time opening the Limit and Premium Condition.

Declination Reason:

Workaround:

Root Cause:

Extent of Impact:

Impact on Existing Data

Recovery Method for Existing Data Affected

Problem:
Claim Document production does not allow to pull a claim reference for a specific type only.

Solution:
Introduce support to pull claim reference for a specified type only. The types should be those defined in Claim Reference Type table,

Workaround:

Root Cause:

Extent of Impact:

Impact on Existing Data

Recovery Method for Existing Data Affected

Problem:
When renewing Claim Program the existing program periods are listed, and the new period is derived from the last in list + 1 year, irrespective of whether this is the latest or not.

Solution:
When renewing a claim program, choose the latest period, and not the last listed.

Workaround:

Root Cause:

Extent of Impact:

Impact on Existing Data

Recovery Method for Existing Data Affected

Problem:
System returns incorrect validation error AC0399 (expects corresponding business condition), when combined aggregate limit, and reinstatement condition is defined on main section level.

Solution:
When Combined Aggregate Limit, the system must consider the reinstatement condition on Main Section.

Workaround:

Root Cause:

Extent of Impact:

Impact on Existing Data

Recovery Method for Existing Data Affected

Problem:
The system abends when booking reinstatement on a technical worksheet an section is either PER LOSS and no reinstatements created, or Per Insured Period but No Calculation.

Solution:
The system should not abend, but raise errors:
1. When booking on a technical section with calculation per loss, the system should not abend, but raise the Compare Worksheet Type error, if the rule is included. If the rule is NOT included, no errors will be raised.
2. When booking on a technical worksheet and a section which has NO calculation, the system should not validate reinstatement at all.

Workaround:

Root Cause:

Extent of Impact:

Impact on Existing Data

Recovery Method for Existing Data Affected

Problem:
When duplicate technical worksheet is reversed, it is reversed with the same booking period as it was created with - provided this is still open, and not updated to reflect a changed booking period on the claim worksheet

Solution:
The reversal technical worksheet must reflect the booking period of the CLOSED claim worksheet, provided this is still open.

Workaround:
SE--2567

Root Cause:

Extent of Impact:

Impact on Existing Data

Recovery Method for Existing Data Affected

Problem:
Abend when selecting 'Select Accounting Classification' from Claim worksheet

Solution:
The system should open the list of Accounting Classifications

Workaround:

Root Cause:

Extent of Impact:

Impact on Existing Data

Recovery Method for Existing Data Affected

Problem:
Claim list figures is not populated

Solution:
Expect that figures are displayed for all claims in the columns, both for Assumed and Outward claims

Workaround:
None

Root Cause:

Extent of Impact:

Impact on Existing Data

Recovery Method for Existing Data Affected

Problem:
Container save settings and save as system wide settings is not enabled for FGU advisory figures container if system parameter 'Additional Case Reserves in FGU' is not selected.

Solution:
The container save settings and save as system wide settings option should be available for FGU Figures container although 'Additional Case Reserves in FGU' parameter is not selected.

Workaround:

Root Cause:

Extent of Impact:

Impact on Existing Data

Recovery Method for Existing Data Affected

Problem:
eMessaging generates Accounting Year prior to Insured Period start date when the First Account As Of Date is in a later year to the IP start date.

Solution:
When a First Account As Of Date is provided then that should be used as the basis for the start date for the calculation of accounts (as per on-line generation) as it may be in a year after the Insured Period Start Date

Workaround:

Root Cause:
Incorrect start date used for account generation by eMessaging

Extent of Impact:
Prop Fac contracts with eMessaging generating an account schedule in order to set Accounting period etc.

Impact on Existing Data

Recovery Method for Existing Data Affected

Problem:
TA message UUid = AMM test share M1 T1 270721
Message has reinsurer share percentage of 25%
Message is linked to business id 1322913. The business has a signed line of 15%.
The rule TestReceiverShareAgainstSignedShare is in force, but has not set an error.
Why?

Note: the business has the processing option 'split', and accordingly there is no link to section or AC. Compare with TA UUid = AMM test share M1 T2 270721, linked to 1322930, where the processing option is specific. Here the TestReceiverShareAgainstSignedShare rule has set an error.

Solution:
As per other rules the share rules should take account of no section being referenced in the case of Processing Option To per AC split

Workaround:

Root Cause:

Extent of Impact:
Following Rules when no Section referenced due to AC split option.
TestBrokerOrderPercentage
TestReceiverShareAgainsteMessagingInfo
TestReceiverShareAgainstEstimatedShare
TestReceiverShareAgainstSignedShare
TestReceiverShareAgainstWrittenShare

Impact on Existing Data

Recovery Method for Existing Data Affected

Problem:
Reading the use case for the IP referencing rule I find this in test 7 (Former Business Id):
Check the role of the message receiver – e.g.. <JV-Ins-Reinsurance><TechAccount @Receiver>
If the message contains <Contract><roleReference> (where ‘role’ is the role found above e.g. if the role is ‘reinsurer’ look for <ReinsurerReference> ) use the contents of the element to search for a former business id.

In this case, the receiver role is 'reinsurer', but there is no reinsurerReference in the <Contract> element of the message. This doesn't appear to stop the rule from looking for a former business id with space as the value.

We are faced with senders who do not complete the message correctly (and we don't always set it in ADH either!) , so we need a better solution in the rule. We would like the rule to omit any search if the message value is empty/spaces/null/missing. This applies to any reference look-up in the IP reference rule, not just test 7.

Solution:
As per other references the Receiver contract reference should not result in a look-up if it is empty/spaces/null/missing.

Workaround:

Root Cause:

Extent of Impact:

Impact on Existing Data

Recovery Method for Existing Data Affected

Problem:
When a ClaimMovement has not created a new adjustment as it is matched as already booked via CheckForExistingBooking rule then a subsequent similar message fails with error on ClaimAdjustmentCMReferenceRule with Previous adjustment not closed. The previous adjustment is closed.

Solution:
When a message is set not to not create a new claim adjustment by the CheckForExistingBooking rule then upon apply worksheet the message should be set to Informational.

If such a message is referenced by a subsequent message then its previous adjustment should be correctly identified and referenced as if that message had created a new claim adjustment..

Workaround:

Root Cause:

Extent of Impact:

Impact on Existing Data

Recovery Method for Existing Data Affected

Problem:
System abends when processing CM.
Performing Swap to Claim then CM0038 error on Date of Loss is raised

Solution:
Ensure that functionality for CheckForExpectedClaimMovement is not performed when a new claim is being created by process of eMessage

Workaround:
Use Swap to Claim to create a new Claim

Root Cause:
Old incorrect functionality now activated by setting of default rules in rule set for Claim Section.

Extent of Impact:

Impact on Existing Data

Recovery Method for Existing Data Affected

Problem:
Periodic Account Treaty Statement has cash_loss as transaction - should only be for advance request
Reversal of advance request should also get cash_loss

The amounts should be unsigned for both (non-reversal) bookings and amount should correctly reflect the booked amount (with message amount as normally positive or negative).

Solution:
Booking of cash loss request / advance using entry code for cash loss that is flagged as positive on outwards should get cash_loss as transaction type (otherwise if a refund / regulation then this is normal treaty statement account).

The items for cash loss are both unsigned and thus the message amounts should reflect this while still getting the correct balance amount.

Workaround:

Root Cause:

Extent of Impact:

Impact on Existing Data

Recovery Method for Existing Data Affected

Problem:
Message has unique references UUID and cedentReference - cedent ref is too long and not unique

Solution:
Ensure that cedentReference is set on the referred message item after uuid
Ensure that the cedentReference is short enough and unique
Set as
Worksheet ID, Currency, Receiver SICS id, Generated message type and sequence - a hash value for detail on worksheet used as base message generation (e.g. case where multiple sections booked etc.)

Workaround:

Root Cause:

Extent of Impact:

Impact on Existing Data

Recovery Method for Existing Data Affected

Problem:
The rule compareReceivedReinstatement to expected is triggered although AutoBookReinstatement rule is not included in ruleset

Solution:
The compare rule should only be triggered if both t he auto book and the compare rules are included in the ruleset

Workaround:
Override

Root Cause:

Extent of Impact:

Impact on Existing Data

Recovery Method for Existing Data Affected

Problem:
The rule checkTotalDeductions is not skipped for message function reinstatement although usage indicates it should be

Solution:
When usage Skip total deductions test is defined for a message function, the rule CheckTotalDeduction rule should not be triggered for messages with this function

Workaround:
Override or remove rule

Root Cause:

Extent of Impact:

Impact on Existing Data

Recovery Method for Existing Data Affected

Problem:

The outer join between tables V_GOV_TAX_LINKAGE and BOAC_PC_FACT is in wrong direction.

Solution:

It should be for BOAC_PC_FACT  *table in SPC Main SICS 21.3.*

Declination Reason:

Problem:
RETRO_PAIRING - Outer joins wrongly defined
Solution:

Joins corrected.

Workaround:

Root Cause:

Extent of Impact:

Impact on Existing Data

Recovery Method for Existing Data Affected

Problem:
BOAC_STL_PAIRING - Outer Joins

Solution:

Corrected

Workaround:

Root Cause:

Extent of Impact:

Impact on Existing Data

Recovery Method for Existing Data Affected

Problem:
Wrong join for Cedants-Program

Solution:

Join corrected.

Workaround:

Root Cause:

Extent of Impact:

Impact on Existing Data

Recovery Method for Existing Data Affected

Problem:
Join wring in SPC

Solution:

CLAIM_COND join corrected.

Workaround:

Root Cause:

Extent of Impact:

Impact on Existing Data

Recovery Method for Existing Data Affected

Problem:
UDD_BUSINESS_L1 wrong join

Solution:

Join corrected

Workaround:

Root Cause:

Extent of Impact:

Impact on Existing Data

Recovery Method for Existing Data Affected

Problem:
Wrong join

Solution:

Join corrected.

Workaround:

Root Cause:

Extent of Impact:

Impact on Existing Data

Recovery Method for Existing Data Affected

Problem:
If a user without security rights to update or create accounting conditions still tries to do so, the system abends.

Solution:
If a user tries to create or update Deposit Conditions, Reserve Conditions, Portfolio Conditions or Internal Premium Reserve Condition without having the security rights to do so, the system should stop the user with the standard security message.

Workaround:

Root Cause:

Extent of Impact:

Impact on Existing Data

Recovery Method for Existing Data Affected

Problem:
Domain Restriction Accounting Worksheet Claim Details for Threshold Amount does not work correctly when the entry code is defined as a positive, or when DR is defined with a negative amount.

Solution:
The system must validate that the amount defined is not exceeded for bookings present in the technical worksheet. When DR is set up with a 'negative' amount, this must be interpreted as the corresponding positive amount in the worksheet. If the DR is set up as an amount, this must be interpreted as the corresponding negative/regular booking.
error must be raised when booking in worksheet exceeds the defined amount.

If DR is set as -10 - the validation is that wk amount cannot be a positive amount MORE than +10. (this means that all negative bookings are accepted and also postive bookings up to 10)
If DR is set as 10, the validation is that wk amount cannot be negative amount more than -10.This means that ALL positive bookings are allowed, and negative up to -10.

Workaround:
None

Root Cause:

Extent of Impact:

Impact on Existing Data

Recovery Method for Existing Data Affected

Problem:
Domain Retrieval for Accounting worksheet doesn't work with Dotnet client.

Solution:

Correct the XSD elements 'pairingBookingYear' and 'pairingBookingPeriod' elements in Complex type 'AbstractLedgerBalance'

Declination Reason:

Workaround:

Root Cause:

Extent of Impact:

Impact on Existing Data

Recovery Method for Existing Data Affected

Problem:
retrieveObject service does not return result when retrieveAll is false

Solution:

Corrected to return what has been rquested.

Workaround:

retrieveAll is set to true.

Root Cause:

Extent of Impact:

Impact on Existing Data

Recovery Method for Existing Data Affected

Problem:

Solution:

Declination Reason:

Workaround:

Root Cause:

Extent of Impact:

Impact on Existing Data

Recovery Method for Existing Data Affected

Problem:

Solution:
Declination Reason:

Workaround:

Root Cause:

Extent of Impact:

Impact on Existing Data

Recovery Method for Existing Data Affected

Problem:
When the user tries to change an existing/defaulted date on a technical worksheet, e.g. Due Date, Payment Date or Accounting Period dates by use of the Calendar, the system does not store the selected date(s)

Solution:
When the user tries to change and existing date by use of the Calendar, the system should show and store the selected date.

Root Cause:

Code error

Extent of Impact:

Impact on Existing Data

Recovery Method for Existing Data Affected

Problem:
MTK does not inherit conditions from Assumed Business to Single Treaty Protection

Solution:
When Proportional Treaty Single Treaty Protection is imported via Migration Tool Kit, the system must inherit all inheritable conditions from protected inward treaty business no matter if the Assumed Business is proportional or non-proportional.
Just like system is doing when Proportional Treaty Single Treaty Protection is created online.
In addition, the system must not abend on opening any condition (inherited or automatically created) on Proportional Treaty Single Treaty Protection

Declination Reason:

Workaround:

Root Cause:

Extent of Impact:

Impact on Existing Data

Recovery Method for Existing Data Affected

Problem:
The Web Service classification update with replacement List for Classification lists allows one set of items to be replaced with another item(s) but it is not possible to completely remove all entries using a List element

Solution:
As well as replacing the items with other(s) it should be possible to remove all items for an element via an empty replacement List element.

Workaround:
Use the full classification update service or clear out incorrectly added items using the workstation.

Root Cause:
SICS 4.8 - SICSE-2788 - Enhanced update classification web services

Extent of Impact:
Single classification updated elements for type ClassificationWithReplacementLists when wishing to clear out all.

Impact on Existing Data

Recovery Method for Existing Data Affected

Problem:
Web Service - Domain Retrieval:
When including <amendmentNumber> in domain retrieval of e.g. business or insured period, the response message returns information from the last amendment - independent of which amendment number is entered in the request message.

Solution:
Web Service: Domain Retrieval
When including <amendmentNumber> in domain retrieval (of e.g. business or insured period), the response message should return information from the correct amendment

Workaround:
None

Problem:

When adding a new group for first time in Details tab of a Business Partner, 'Last Updated' information (User name, date and time) is correct. However, for every subsequent changes, 'Last Updated' information does not update.

Solution:
When assigning a Business Partner to a group, the system should update the Last Updated by (User) and Last Updated at (Date and Time) also when assigning the partners to additional groups.

Workaround:

Root Cause:

Extent of Impact:

Impact on Existing Data

Recovery Method for Existing Data Affected

Problem:

When creating/updating Cancellation Condition <specialTerminationClause>, by use of web service createCancellationCondition or updateCancellationCondition, the details in the element </terminatingAgencyRatingList> is not updated in on-line SICS

Solution:
When creating/updating Cancellation Condition <specialTerminationClause> by use of web service createCancellationCondition or updateCancellationCondition,
all details in the message should up-date the correct details in on-line SICS.
This does also apply to the element </terminatingAgencyRatingList>. System should update the 'Rating Agency', 'Rate At' and 'Business At Stake' fields with the details entered in the message.

Workaround:
Manually update missing details in on-line SICS

Root Cause:

Extent of Impact:

Impact on Existing Data

Recovery Method for Existing Data Affected

Problem:
When creating Protection Program or Reinsurance Program by web service createBusiness, system abend if you include <insuredPeriodFormerId>xxx</insuredPeriodFormerId> and/or <originalFormerId>xxx</originalFormerId> in the message.

Solution:
When creating Protection Program or Reinsurance Program by web service createBusiness, and the elements <insuredPeriodFormerId>xxx</insuredPeriodFormerId> and/or <originalFormerId>xxx</originalFormerId> are included in the message, the system should not abend but simply ignore these elements.
System should behave in the same way as it does if you send updateInsuredPeriod message to update Reinsurance/Protection Program and the message includes the same elements

Workaround:
Disable elements <insuredPeriodFormerId>xxx</insuredPeriodFormerId> and/or <originalFormerId>xxx</originalFormerId> in the message.

Problem:
Missing Accounts in Administration Calculate Accounts function

Solution:
When the business insured period starts from another date than 01.01 and the user recalculates the accounts from e.g. Monthly to Quarterly/Half Yearly/Yearly and select a date in the second accounting year in the window 'Choose an account to start with recalculation', we must make sure the system KEEPS the accounts in the first accounting year as they are.

Workaround:

Root Cause:
This is a side-effect of the fix we did in 20.4 according to SICSR-20087

Extent of Impact:

Impact on Existing Data

Recovery Method for Existing Data Affected

Problem:
It is not possible to add a new rating on existing business partner by web service.

Solution:
The system should not abend when creating a new Rating on an existing Business Partner by Web Service. Instead it should record the rating with the selected rating system.

Workaround:

Root Cause:

Extent of Impact:

Impact on Existing Data

Recovery Method for Existing Data Affected

Problem:

Solution:

Declination Reason:

Workaround:

Root Cause:

Extent of Impact:

Impact on Existing Data

Recovery Method for Existing Data Affected

Problem:

Period Estimates on Outward Retrocessionaire's Placements (ORP) are normally calculated as the values on the Outward Cedent's Contract (OCC), multiplied with the Retrocessionaire's share. However, it is possible to execute the calculation rules directly on the ORP. This is activated by selecting 'Calculation on Retrocessionaire' in the relevant Period Estimation Rule in Multi GAAP system parameters. 

The Calculation on Retrocessionaire option only works when Multi GAAP General system parameter 'Period Estimation Calculation on Prop Outward Contracts' is selected. This is not correct. For Non-Proportional ORPs, it should not be dependent on this parameter

Solution:

On Non-Proportional ORPs, make sure Period Estimates calculation rules are executed directly on the ORP when option 'Calculation on Retrocessionaire' is selected, independent on whether or not parameter Period Estimation Calculation on Prop Outward Contracts' are selected. 

Workaround:

Root Cause:

Original implementation

Extent of Impact:

Impact on Existing Data

Recovery Method for Existing Data Affected

Problem:
If creating a new Person and selecting Finish without having entered the mandatory information, the system abends.

Solution:
If creating a new Person and selecting Finish without having entered the mandatory information, the system should not abend. Instead, it should give the full stop messages, telling what is missing.

Workaround:

Root Cause:

Extent of Impact:

Impact on Existing Data

Recovery Method for Existing Data Affected

Aim of function
Added periodic function 'Update Retro Pairing Table' as a job step in scheduler

System Parameters Affected
None 
Existing functionality affected
Update Retro Pairing Table
Create and run scheduled jobs

 Aim of function

The aim of this change is to be more precise when searching for balances in the function Automatic Search for SBG from the BP Ledger. Therefore a new option to the existing 'Import Record File...' is established named 'Import Excel/Delimited Record File...'
The new option uploads an electronic file with a title supports TXT, CSV, XLS, and XLSX files with titles. The column names must strictly follow the names given in the Template.

Create SBG from Automatic matching by use of the new file structure:
If the Currency column is the same as 'SBG Currency' column, the value in the Settlement Amount column in the electronic file will be ignored when the SBG is created (the Unsettled Amount of the matched balance is used). The Settlement Balance Group will use the SBG Currency as the Currency and it will sum up the Unsettled Part Amounts from the rows with the same Currency and the Settlement Amount from the rows with different Currency. If NO Settlement Amount given on a row with different Currency, Then the system will calculate the Settlement Amount by use of current exchange rate (existing functionality).

System Parameters Affected

N/A

Existing functionality affected

1. Automatic Search for Settlement Balance Group uploads files
2. Create Settlement Balance Group from Automatically Matched Balances

Aim of function

Some companies have other applications than SICS that work with complete versions after each amendment. To make the interface to these easier, SICS offers a facility that automatically links all existing conditions to an amendment upon creation of this amendment. Along with this, SICS offers also now a feature for updating the history, where the amendments already existed before activating the facility. This feature is the Mass Update Amendment Links. This mass update has however major impact on all contracts in the system, as all terms and conditions will then be linked to all contract amendments. Thorough analysis and considerations should therefore be taken in advance of taking such action.

 System Parameters Affected

Automatically Amend Contract Information

Existing functionality affected

Maintain Share Conditions
Maintain Premium and Limit Main Conditions
Maintain Deduction Conditions
Maintain Reinstatement Conditions
Maintain Claim Conditions
Maintain Rebate Conditions
Maintain Deductibles Conditions
Maintain Profit Commission Conditions
Maintain Cancellation Conditions
Maintain Index Clause Conditions
Maintain Clauses Conditions
Maintain Classifications
Handle Protection Assignment
Handle Business Amendments

Aim of function

Most companies need a contract amendment to be linked only to those terms and conditions that changed as part of the amendment. Some companies have however other applications that work with complete versions after each amendment. To make the interface to these easier, SICS offers now a function that automatically links all existing conditions to an amendment upon creation of this amendment.  Activating this function has however major impact on all contracts in the system as all terms and conditions will then be linked to all contract amendments. Thorough analysis and considerations should therefore be taken in advance of taking such action.

Amendable  terms and conditions are divided into 'Auto Amend Groups' and the system can be set up to automatically link existing conditions within these groups to new amendments.

The following Auto Amend Groups are available:

• Share, Limit and Premium Conditions (Share Condition, Premium and Limit Main Conditions, Deposit Premium Condition, Flat Premium Condition)
• Other Conditions (Commission Conditions, Brokerage Conditions, Other Deductions, Reinstatement Conditions, Claim Conditions, Rebate Conditions, Deductibles Conditions, Profit Commission Conditions, Cancellation Conditions, Index Clause Conditions, Clauses Conditions, Underlying Business)
• Business Classifications
• Administration Conditions
• User Defined Information
• Protection Assignment (Proportional and Non-Proportional Protection Assignment)

  System Parameters Affected

Automatically Amend Contract Information

Existing functionality affected

Maintain Share Conditions
Maintain Premium and Limit Main Conditions
Maintain Deduction Conditions
Maintain Reinstatement Conditions
Maintain Claim Conditions
Maintain Rebate Conditions
Maintain Deductibles Conditions
Maintain Profit Commission Conditions
Maintain Cancellation Conditions
Maintain Index Clause Conditions
Maintain Clauses Conditions
Maintain Classifications
Handle Protection Assignment
Handle Business Amendments

Aim of function

In order to control who can create a duplicate Technical worksheet from an open claim worksheet, a new security use case is implemented to control access to create such worksheets.

System parameters affected

None

Existing functionality affected

Define Security User Roles

Claim Accounting - Create Duplicate Technical Worksheet from Open Claim Worksheet

Aim of function

A claim action date is normally set automatically on all claims, regardless of reserve position. In order to avoid that claims without any reserves have an action date, there should be a validation against the accumulated reserves. The validation should be implemented for all reserve entry codes, and is made per currency, entry code level, and per accounting classification. If the claim has an action date, the action date should be removed if the accumulated reserves are zero. Otherwise the worksheet should result in an update of the action date.

Additionally, a new option is introduced to ensure that action date is always generated if a claim has a sub-disposition, regardless of reserves. 

System Parameters Affected

New Base Company Specific Parameter - Claim Specific:  Validate Against Reserves

New Base Company Specific Parameter - Claim Specific: Always Set Action Date for Sub dispositions  other than None 

Existing Functionality Affected:

Maintain Claim Sub-disposition

Create Claim Worksheet

Close Claim

Process Claim Movement

Aim of function:

Add a new rule on message layer to  calculate Reinstatement Reserves, and book these on the same worksheet as claim and reinstatement paid.

The new rule shall be a 'full' reinstatement calculation, but only book the reserve items. 

A new element shall be added to createClaimWK and createFGUClaimWK APIs - to book reinstatement accruals only.

A new option is added to the claim worksheet to create Reinstatement for Reserves only.

System Parameters:

New rule available for message layer.

Existing functionality affected:

Process ClaimMovement

createClaimWorksheet API

createFGUClaimWK API

Create Claim Worksheet

Aim of function:

The automatically reprocess related messages - which is invoked when a message is processed from within emessaging - should also be triggered when a worksheet is closed manually/through API.

System parameters affected:

Automatically Reprocess Related Messages must be activated

Existing functionality affected:

Close worksheet

CloseWorksheet API

Aim of function
When comparing the BalanceAmtItem in a TechAccount message with the net Instalment or Adjustment premium in the Limit and Premium condition in SICS, any TechAccountAmtItems or TaxAmtItems mapped to a Government Tax Target entry code are now deducted from the BalanceAmtItem before it is compared to the Net Instalment or Adjustment amount.

Government Tax Target entry codes in this respect are defined as entry codes included in an Entry Code Group within Entry Code Group Category ‘Government Tax Target’

System Parameters Affected

N/A

Existing functionality affected
The following validation rules are affected:

• CompareReceivedPremiumToNetInstalmentPremium
• CompareReceivedPremiiumToNetAdjustmentPremium
• CompareReceivedPremiumToNetInstalmentPremiumLM
• CompareReceivedPremiumToNetAdjustmentPremiumLM
• ValidateNetBookedAmountsOnInstalment

Aim of function
The aim of the function is to show more information on the TechAccount/eMessaging/Government Tax tab and to specify why the validation failed. The Gov. Tax Rule Type gives the following information in the new column Gov. Tax Rule Type depending on various scenarios;

• Booked Target EC without Gov. Tax Rule
• Gov. Tax Table Rule
• Gov. Tax Validation Indicator Rule

System Parameters Affected

Two existing Accounting system parameter must be activated/defined;

• 'Government Tax Framework in use' to activate the new Government Tax functionality.
• 'Government Tax Table' to define various rules for what to be booked and validated

Existing functionality affected

• eMessaging/TechAccount/Government Tax tab
• Validation of Government Tax Trigger/Target Entry Codes and amount