Release documentation - P&C Enhancements and requests

Problem:
Rounding in reversal not working

Solution:
When instalments/adjustments are booked on a non-prop OCC and there are split percentages defined on the Accounting Classifications and this OCC is placed to more than one ORP, then the system will check the sum of all details booked on the ORPs, and if the sum does not match exact the premium on the OCC, then the difference is adjusted on the last ORP and the last AC detail. This is working fine when the instalments and adjustments are booked.

Make sure the same takes place when instalments and adjustments are reversed, i.e. the same sum up must take place so that the rounding of the last detail on the last ORP also takes place for reversal of instalments and adjustments when that is necessary.

Workaround:

Root Cause:

Extent of Impact:

Impact on Existing Data

Recovery Method for Existing Data Affected

Problem:
SICS loading of Business Partner Ledger Balances scrolling performance retest failed

Solution:
When balances are listed on the Business Partner Ledger and the user scroll down/up among the balances we must make sure the performance is improved. This is done by ignoring the FK_ORIG_RP on the details in the balances if the system parameter 'Trace Original Responsible Partner from Outward Bookings' is NOT selected.

Workaround:

Root Cause:

Extent of Impact:

Impact on Existing Data

Recovery Method for Existing Data Affected

Problem:

Entry Code Transformation Term defined for asOriginal bookings.

Error when ceded percentage change trigger recalculation.

Solution:

EC Transformation Tern to be supported

Workaround:

Root Cause:

Extent of Impact:

Impact on Existing Data

Recovery Method for Existing Data Affected

Problem:
Taking a long time to close the worksheet on AB when system parameter “Automatically Create Retrocession Calculation order” is ON

Solution:
Preconditions: The system parameter “Automatically Create Retrocession Calculation order” is ON
Make the query to check if new retrocession calculation order shall be created or if an existing open order already exists more effective by removing the 'not exists' clause. This will hopefully improve the performance.

Workaround:

Root Cause:

Extent of Impact:

Impact on Existing Data

Recovery Method for Existing Data Affected

Problem:
Reversal/Replacement Automatic Booking applies wrong amounts

Solution:
When a worksheet that contains Government Tax details is highlighted and the option Reverse and Replace is selected, the system creates a worksheet with both reversed details and copied details from the source worksheet. Each GT reversal detail has a link to Government Tax Rule Ref while the GT copied details do not have this link. When Automatic Booking of Government Tax is selected on this worksheet to have the GT recalculated the system must do this ONLY for the copied details and keep the reversal details unchanged.

When a worksheet that contains Government Tax details is highlighted and the option Reverse is selected, the system creates a worksheet with reversed details from the source worksheet. Each GT reversal detail has a link to Government Tax Rule Ref. When Automatic Booking of Government Tax is selected on this worksheet the system must keep the reversal details unchanged. Reversed details must be protected also from the GT calculation.

When a worksheet that contains Government Tax details is highlighted and the option Copy is selected, the system creates a worksheet with copied details from the source worksheet. The GT copied details does not have a link to Government Tax Rule Ref. When Automatic Booking of Government Tax is selected on this worksheet the system must calculate the GT details from all source details on the worksheet where this is applicable and overrule the existing amounts and set the Government Tax Rule Ref accordingly. The system must calculate each source/target detail separately in case the there are several target details with the same entry code, i.e. they must be treated separately as when they are calculated the first time.

Workaround:

Root Cause:

Extent of Impact:

Impact on Existing Data

Recovery Method for Existing Data Affected

Problem:
Not considered scenario where in previous Q is no retained, however validation in current Q expects release.

Solution:
Preconditions:
Business with Quarterly accounts
Deposit based on Premium Reserve
Regulation Years
Release in 'Same Account in Next Accounting Year' or 'Next Account'

With the above preconditions the system shall accept booking of Premium Deposit Retained in last account each Accounting year. If premium deposit retained in booked in other than last account, then an error message shall appear.
It shall also accept booking of Premium Deposit Released in last account each Accounting year of the retained booked in previous Accounting year, unless there is no premium deposit retained found in the last account in previous accounting year, in this case an error message must appear (AC0400). If the release of the premium deposit is done in any other accounts than the last account, then an error message shall also appear.

The above is the case also for loss deposit when it is based on Loss Reserve.

Workaround:

Root Cause:

Extent of Impact:

Impact on Existing Data

Recovery Method for Existing Data Affected

Problem:
SICS Hardstop error in Reinstatement booking for 'other Costs' Deduction

Solution:
When booking an entry code within the Entry Code Sub Category 'Reinstatement Premium' on a technical worksheet this shall not trigger any validation of deductions other than validation rules where Attribute on Condition is Brokerage On Reinstatement - Reinstatement Conditions, i.e. if Attribute on Condition is any of those from the Deduction Conditions then these validation rules shall NOT be triggered for the detail with entry code in the EC Sub Category 'Reinstatement Premium'.

The above should be independent if there are deductions defined in Entry Code Usage in the Accounting Function 'Reinstatement Premium, non-Proportional AB' in the system parameters.

Workaround:

Root Cause:

Extent of Impact:

Impact on Existing Data

Recovery Method for Existing Data Affected

Problem:
Deposits - Validation AC0395 wrongly triggered for quarterly regulation and release in next quarter

Solution:
Preconditions:
Deposit based on Premium or Paid Loss
Quarterly Accounts and also Regulation Quarterly
Release in Next Account

When retained deposit, booked in 1st quarter, have been manually released in 2nd quarter (not used the Release Bookings...Deposits from the worksheet) and therefore still shown as Unreleased and when the user now make a booking of deposit retained in 3rd quarter we must make sure the system does NOT raise message AC0395 saying that a corresponding deposit release detail is expected.
This error message is correctly raised if the user book a deposit retained in 2nd quarter and the deposit retained for the 1st quarter is still 'Unreleased'

Workaround:

Root Cause:

Extent of Impact:

Impact on Existing Data

Recovery Method for Existing Data Affected

Problem:
Inconsistent display of balance search result in SBG’s edit

Solution:
When a Settlement Balance Group is opened from a Settlement message in eMessaging by using the option Swap to Settlement Balance, and the user opens the SBG in Edit mode and search for balances in the upper balance container, the system must retrieve ALL found balances in one go and not display only a portion at the time.
This will then be consistent with the same operation when the user highlight the same Settlement Balance Group directly from the BP Ledger, open it in Edit mode and the search for balances. In this operation ALL balances are listed in one go when the user press Find Now.

Workaround:

Root Cause:

Extent of Impact:

Impact on Existing Data

Recovery Method for Existing Data Affected

Problem: 
ESPID - System abends when the user try to book instalments from P/L condition through the option 'Book and close selected instalments' or 'Create booking order'

Solution:
Preconditions: System parameter Government Tax in use is ON
From the premium and limit conditions, when there are defined AC Split % including split by Base Company, and the user selects the option Book and Close Selected Instalment, the system shall be able to do this and create the necessary details according to the AC Split percentages without abending.

Workaround:

Root Cause:
SICSR-22902 in 22.3

Extent of Impact:

Impact on Existing Data

Recovery Method for Existing Data Affected

Problem:
Partner's Bank Account not updated in updateRemittance web service

Solution:
When running the web service updateRemittance the system must also be able to update the Partner's Bank Account from the element
<partnersBankAccount>
<accountNumber>123456789</accountNumber>
</partnersBankAccount>
The element correctly appears in the web service, but the Partner's Bank Account is not updated on the remittance balance. It must be updated in the same way as the Bank Account for the Base Company.

Workaround:

Root Cause:

Extent of Impact:

Impact on Existing Data

Recovery Method for Existing Data Affected

Problem:
Old worksheets created by installment premium order without link to proportional ceded transactions.
Protection added later and accounting order preliminary booking is run to create ceded transactions.
ABEND

Solution:
Corrected to support bookings linked to installments and adjustments,

Workaround:
Use Periodic Function Preliminary Bookings

Root Cause:

Extent of Impact:

Impact on Existing Data

Recovery Method for Existing Data Affected

Problem:
'Use RU from OCC/ORP in AC' is incorrectly referred to as Base Company specific in Recovery Calculation code for SE-15189

Solution:
Use correct coding for reference to 'Use RU from OCC/ORP in AC' in Recovery Calculation solution for SE-15189

Workaround:
None

Root Cause:
SE-15189

Extent of Impact:

Impact on Existing Data

Recovery Method for Existing Data Affected

Problem:
eMessaging - CWS go to a status of waiting - Same functionality for TWS

Solution:
When the system parameter 'Prevent Manual update of technical worksheets' is selected, the check box labelled ‘In Review’ shall appear in the Technical Worksheet also when the worksheet is created by TechAccount eMessaging. Both when the user selects Process on the message and when the user selects Swap to Worksheet. The Technical Worksheet shall not be possible to change to Closed immediately but have to be stored as ‘In Review’.
This must work in the same way as if the worksheet is created manually.

Workaround:

Root Cause:

Extent of Impact:

Impact on Existing Data

Recovery Method for Existing Data Affected

Problem:
RU ignored in AC matching when AC is created manually by function Add.

Solution:
On a Non-Prop Treaty OCC and Non-Prop Fac OCC, when Accounting Classification is Added, make sure the system validates the new AC also by using all Reporting Units. This means that Reporting Unit must also be part of the comparison when finding out if new AC is unique or not.

Workaround:

Root Cause:

Extent of Impact:

Impact on Existing Data

Recovery Method for Existing Data Affected

Problem:
not yet implemented for non-proportional assumed business

Solution:
Make sure the ECTT is enabled on the Fac ORP also when it protects a non-prop AB, both Facultative and Direct.
Make also sure that the ECTT function work in the same way as for a Fac ORP protecting a prop AB.

Workaround:

Root Cause:
Missing from the implementation of SE-2375 in 22.3

Extent of Impact:

Impact on Existing Data

Recovery Method for Existing Data Affected

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

Solution:
When the system parameter 'Override Booking Period on As Original Correction Bookings' and the user makes changes to the Retroceded Share on the Proportional Protection assignment window on the Assumed Business, so that retroactive correction bookings take place on the As Original ledger of the OCCs, the system must always use the Booking Year/Periods from the source bookings on the Assumed Business, even if these are closed according to the Closure Booking Terms for the Base Company settings.

This must be the case both when Reporting Unit is part of the classification on the details coming from the AB or not.

Workaround:

Root Cause:
The correction in SICSR-24541 did not solve the business case where the Reporting Unit is part of the classification of the details.

Extent of Impact:

Impact on Existing Data

Recovery Method for Existing Data Affected

Problem:
The latest Entry Code Transformation Term (ECTT) is always effective even when the ECTT is amended.

Solution:
When the Entry Code Transformation Term is changed as part of Amendment on a Fac ORP, we must make sure the system reads the amendment number on the detail and if there are Entry Code Transformation Term on the actual amendment, then the system shall use these term.

Workaround:

Root Cause:

Extent of Impact:

Impact on Existing Data

Recovery Method for Existing Data Affected

Problem:
When PA is updated, retroactive bookings are not correctly EC-transformed (SE-2375)

Solution:
When an assumed business is protected by single Fac ORP and this ORP has Entry Code Transformation Terms (ECTT), and the retroceded share is changed for this Fac ORP so that correction bookings takes place on the ORP ledger, then the system must also book correct amount for the detail with the entry code that has been transformed.

When an assumed business is protected by Fac OCC and this is placed to ORP with ECTT, and the placement share is changed for this ORP and/or a new ORP is added, so that correction bookings takes place on the ORP ledger, then the system must also transform the entry code according to the ECTT and book correct amount for the detail with the entry code that has been transformed. For this part of the reported issue we have created a new case, SICSR-25549, and will fix it in 23.1.

Workaround:

Root Cause:

Extent of Impact:

Impact on Existing Data

Recovery Method for Existing Data Affected

Problem:
Wrong label on a field on Functional Currency Revaluation order

Solution:
Remove the wrongly pasted text behind the label Remove Previous Revaluation Rows in the Functional Currency Revaluation Order

Workaround:

Root Cause:
SE-5231 in 21.1

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:
When renewing a business to new insured period and the current insured period has manually created instalment(s), instalments on the new insured period should have dates reflecting the new insured period (e.g. Due Date, Accounting Period From - To, Payment Date, Extended Payment Date)

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

Problem:

Find Business result list shows the wrong column header for Sub Class of Business. It uses the Fixed name and not display name.

Solution:

In the result list, the column header should not show the name from the Reference Data Type's 'Fixed Name'.  It should instead take it from the 'Display Name'.  

Workaround:

Root Cause:

Extent of Impact:

Impact on Existing Data

Recovery Method for Existing Data Affected

Problem:
The system abends when creating or changing the selection criteria on a document template

Solution:
System Administration / Document Production Template Maintenance:
Creating or editing selection criteria of a template, the system should not abend. It should instead save the criteria as entered.

Workaround:

Root Cause:

Extent of Impact:

Impact on Existing Data

Recovery Method for Existing Data Affected

Problem:
Create Business Partner with User defined field Monetary Amount by Web Service different from online.

Solution:

The system should create Business Partner with User Defined field Monetary Amount by Web Service as it does correctly on-line.  

Workaround:

Root Cause:

Extent of Impact:

Impact on Existing Data

Recovery Method for Existing Data Affected

Problem:

When claim ID series contains year (and possibly also prefix), the system can create multiple ID series for same year if SICS is started from two instances, where the series do not yet exist for a year, and then new claim is created for that year is created from both instances.

Solution:

There should only be one ID series for a year.

Workaround:

Root Cause:

Extent of Impact:

Impact on Existing Data

Recovery Method for Existing Data Affected

Problem:

Abend when closing a claim worksheet on an assumed business which has a proportional facultative OCC placement with linked intragroup business and a claim and claim booking is created directly on the intragroup business.

Solution:

When IGC is party of a proportional fac arrangement:

Warning message if user is creating claim directly on IGC contract: You are creating claim directly on an Intra Group contract, The claim must be linked to corresponding Assumed Claim before booking.'

Error message if user is creating booking on IGC claim which is not linked to Assumed Claim: The claim is not linked to an Assumed Claim. Booking is not allowed.'

 Workaround

Root Cause:

Extent of Impact:

Impact on Existing Data

Recovery Method for Existing Data Affected

Problem:

Accuracy error raised for reinstatement on a Stop Loss treaty despite business not having condition available

Solution:

Accuracy errors for reinstatement and brokerage-reinstatement should not be raised for businesses which do not have the condition available

Workaround:

Root Cause:

Extent of Impact:

Impact on Existing Data

Recovery Method for Existing Data Affected

Problem:
Automatic Booking of Reinstatement Premium Calculation on Claim Worksheets abend

Solution:
Preconditions:
System Parameter 'Split entry Codes With Special FC1 Calculation Rule In Separate Balance' is selected.

When the function Automatic Booking of Reinstatement Premium Calculation is selected on a Claim Worksheets the system shall not abend, but must use the functionality from the above system parameter and set the FK_AC_FC_RULE on the details if special Functional Currency Exchange Rules exists for the Entry Codes in these details. Based on these values the system shall group the details in necessary balances. If the Entry Codes in the details do not have special exchange rules then no special action for these details is needed.

Workaround:

Root Cause:
Enhancement case SE-12648 in 22.3

Extent of Impact:

Impact on Existing Data

Recovery Method for Existing Data Affected

Problem:

When retroactive date is defined on claim condition, the original policy period from date defaults to this date and could result in an error message if prior to insured period from date. Furthermore the warning that the OPP dates are prior to insured period needs to be overridden every time

Solution:

When claim trigger code (other than none) and claim trigger date is recorded, the system should not raise an error for Original Policy Period Dates.

When Retroactive date is defined, do not raise warning either.

Workaround:

Root Cause:

Extent of Impact:

Impact on Existing Data

Recovery Method for Existing Data Affected

Problem:

The date of loss end date is automatically populated when entering a Claims Made Date

Solution:

The system should not populate the date of loss to date

Workaround:

Root Cause:

Extent of Impact:

Impact on Existing Data

Recovery Method for Existing Data Affected

Problem:
Validation of ACORD code mapped to Reference Data None value when compared to corresponding contract None value results in a mismatch error being raised.

Solution:
Ensure Reference Data None values added in mappings are set to be of the correct Reference Data Type

Workaround:
Enter Mappings to None values as required and then execute script.

SELECT DISTINCT m.*, m1.FSK_SICS_REF_DATA, (SELECT MAX(m2.FSK_SICS_REF_DATA) FROM EMES_MAPPING m2
WHERE m2.subclass = m.subclass and m2.FRK_SICS_REF_DATA <> 'NONE')
FROM EMES_MAPPING m
JOIN EMES_MAPPING m1 on m1.subclass = m.subclass and m1.FRK_SICS_REF_DATA <> 'NONE'
WHERE m.FRK_SICS_REF_DATA = 'NONE' AND m.FSK_SICS_REF_DATA <> (SELECT MAX(m1.FSK_SICS_REF_DATA) FROM EMES_MAPPING m1
WHERE m1.subclass = m.subclass and m1.FRK_SICS_REF_DATA <> 'NONE');

UPDATE EMES_MAPPING SET FSK_SICS_REF_DATA = (SELECT MAX(m1.FSK_SICS_REF_DATA) FROM EMES_MAPPING m1
WHERE m1.subclass = EMES_MAPPING.subclass and m1.FRK_SICS_REF_DATA <> 'NONE')
WHERE EMES_MAPPING.FRK_SICS_REF_DATA = 'NONE' AND EMES_MAPPING.FSK_SICS_REF_DATA <> (SELECT MAX(m2.FSK_SICS_REF_DATA) FROM EMES_MAPPING m2
WHERE m2.subclass = EMES_MAPPING.subclass and m2.FRK_SICS_REF_DATA <> 'NONE');

Root Cause:
Wrong Reference Data Types for None being used in System Parameter mappings.

Extent of Impact:

Impact on Existing Data

Recovery Method for Existing Data Affected

Problem:
eMessages were loaded several times by mistake one day and for all Settlements, the ValidateFAINotInAnotherSettlement validation rule failed, the users had to manually override the error to process the message. ValidateFAINotInAnotherSettlement should not consider the discarded messages

Solution:
ValidateFAINotInAnotherSettlement should not consider discarded messages.

Workaround:

Root Cause:

Extent of Impact:

Impact on Existing Data

Recovery Method for Existing Data Affected

Problem:
When Rejecting an eMessage then the Message History Tab is missing the link / reference to the Acknowledgement.

Solution:
The Rejection Acknowledgement should be shown on the message history tab as when the message is acknowledged

Workaround:

Root Cause:

Extent of Impact:

Impact on Existing Data

Recovery Method for Existing Data Affected

Problem:
When Rejecting an eMessage then the Acknowledgement is missing the mandatory attribute for ErrorIndicator

Solution:
When generating an Ack with rejected status then add attribute ErrorIndicator with the value 'error_free_format' given that the ResponseDescription text gives the reasoning for rejection.

Workaround:

Root Cause:

Extent of Impact:

Impact on Existing Data

Recovery Method for Existing Data Affected

Problem:
eMessaging Export Data abends.
View Related Messages on Insured Period eMessaging does not show any eMessages linked to the Insured Period

Solution:
Export Data and view Related Messages on Insured Period should work as expected.

Workaround:

Root Cause:
Changes to Query for Assure Re.

Extent of Impact:

Impact on Existing Data

Recovery Method for Existing Data Affected

Problem:
Messages set to Informational have no acknowledgement created

Solution:
When a message is set to Informational it should still be considered to be Complete / Accepted and if applicable create an Acknowledgement message.

Workaround:

Root Cause:

Extent of Impact:

Impact on Existing Data

Recovery Method for Existing Data Affected

Problem:
There is an issue with the SE-5946 New ModifyClaimFGUAsofDate rule which was not grouping FGU messages correctly.

Solution:
The ModifyClaimFGUAsofDate rule should correctly group messages together in the same method as if the rule were not in place. It should only affect what AsOfDate is set, not grouping of messages.

Workaround:

Root Cause:

Extent of Impact:

Impact on Existing Data

Recovery Method for Existing Data Affected

Problem:  support scripts performance issues, Problem with a query in script SUPP005.

Solution:  Have to verify the latest  suppoo5 script and check whether the script is matching with Triglav or not. If the changes are not matching please update the changes suggested By Triglav

Attaching the doc of Triglav.

SICSR-19194 - BOAC Support scripts performance andor function.xlsx

Problem:
Mass Pairing abend when Remittance is included in Settlement Balance

Solution:
When running the Mass Pairing order and the system find a match between a Remittance balance and a Settlement Balance Group containing other Remittance balances, then the system shall still perform the pairing between the driving Remittance balance and all the balances included in the SBG, including Remittance balances, without abend.

Workaround:

Root Cause:

Extent of Impact:

Impact on Existing Data

Recovery Method for Existing Data Affected

Problem:
Using in reports the universe objects Unsettled Amount Start of Period & End etc. gives users an automated Prompt to enter a date as to when they want to see the unsettled balances (1/1/2018, 4/1/2020 etc.)

However a number of clients have complained that this will not due because they can't keep track of closing dates as they are not always the end of month. For example if a client closed the month of January of February 6th they would have to remember that is the date to run the report (Feb 6)

They are requesting the booking year Period be used instead of a date to more accurately reflect their numbers.

Africa Re (and all other clients like Samsung Fire and Marine, Labuan, Achmea, ACIM, Triglav Re, EMC Re have all expressed this to be altered.

See the attached screenshot for review and advise what can be done
Solution: 

The object 'Booking year period' should be added to the universe.

Problem:

Payment Partner details

Solution:

Joins corrected.

Root Cause:

Extent of Impact:

Impact on Existing Data

Recovery Method for Existing Data Affected

Problem: BOAC scripts - XML file generation.

Solution: The SQL should be updated and the extra signs should be removed at SICS level, as it does not exist in the script generated in the database level.

Problem:
SICS Server Domain Retrieval for Business does not retrieve 'Other Deductions' business conditions.
The issue is due to refactorings in the XSD, when the new complex type 'PcScopeOfCover' was introduced. This was introduced by development of the Business entrypoint for Life.

Solution:
The mappings file 'Business.map' need to get updated with mappings for the new XSD type 'PcSCopeOfCover' (copy of the existing mapping for XSD type 'ScopeOfCover').

Workaround:

Root Cause:

Extent of Impact:

Impact on Existing Data

Recovery Method for Existing Data Affected

Problem:
-When exporting Business Partner data using SICS Data Export Function, exported file does not display %BP RELATION which has information of linked business partners.
-When migrating a Business Partner via MTK loader, migration is successful but linked Business Partners are not created.

Solution:
-The Data Export function should export all information of a Base Company, including the link to Business Partners (LBP) and the link to Insureds (LIN) in %BP RELATION.
-Migration Tool Kit-Loader function should create new Base Company including the link to Business Partners and the Link to Insureds.

Workaround:

Root Cause:

Extent of Impact:

Impact on Existing Data

Recovery Method for Existing Data Affected

Problem:

Multi GAAP calculation variables %depositPremiumAmount and %premiumEPIAmount does not calculate correctly on Outward Retrocessionaires Participations. 

When option 'Calculation on Retrocessionaire' is selected in the Period Estimation Rule, the system incorrectly retrieves the 100% values from the OCC instead of the participant's share

Solution:

When option 'Calculation on Retrocessionaire' is selected in the Period Estimation Rule, the variables %depositPremiumAmount and %premiumEPIAmount must retrieve the premium for the retrocessionaire's share

Workaround

Root Cause:

Extent of Impact:

Impact on Existing Data

Recovery Method for Existing Data Affected

Problem:

Additional Classifications 20-29 are not considered in Multi GAAP Period Estimation Rules

Values for the classifications can be selected in Period Estimation Rules, but they are not considered when matching the business classification. Also not considered when checking for duplicate Period Estimation rules upon saving of the rule. 

Solution:

Make sure Additional Classifications 20-29 are considered in Multi GAAP Period Estimation Rules, in line with other additional classifications

Workaround:

Root Cause:

Extent of Impact:

Impact on Existing Data

Recovery Method for Existing Data Affected

Problem:

Event Log - Missing classes

Solution:

Classes made available

Workaround:

Root Cause:

Extent of Impact:

Impact on Existing Data

Recovery Method for Existing Data Affected

Problem:
Creating a Retrocessionaire Placement on an Outward Cedent's Contract by use of Web Services, the Former ID information is not recorded on the Retrocessionaire Placement when the placement is placed through an intermediary.

Solution:
When creating a Retrocessionaire Placement via a Broker using Web service, all information entered in the SOAP message, including Former Id (<formerIdentifier>), should be correctly recorded on the Retrocessionaire Placement.

Problem:
When using webservice to update Treaty Type of Cover on an assumed non-proportional treaty linked to a reinsurance program, Treaty Type of Cover is not updated accordingly on the XL Treaty Part of the reinsurance program

Solution:
When using web services to update Treaty Type of Cover on an assumed business linked to a Reinsurance Program, the updated Treaty Type of Cover value should be reflected also on the Reinsurance Program. In the same way it is correctly updated in on-line SICS

Problem:
There is no example entry in the shipped sics-database-sources.xml file

Solution:
Add example entry.

Workaround:
Manually add entry based on:
<!-- Example for PostgreSQL -->
<source name='PostgreSQL'>
<driver>org.postgresql.Driver</driver>
<accessor>com.csc.troll.accessor.JDBCDatabaseAccessor</accessor>
<interface>com.csc.troll.accessor.PostgresDatabaseInterface</interface>
<dataSource>jdbc:postgresql://hostname/</dataSource>
<caseSensitiveUserNames>true</caseSensitiveUserNames>
<optimizedMode>true</optimizedMode>
<useParameterizedSql>true</useParameterizedSql>
<statementCacheSize>100</statementCacheSize>
</source>

Root Cause:

Extent of Impact:

Impact on Existing Data

Recovery Method for Existing Data Affected

Aim of Function

When we run the Open Worksheet mass update order to close the selected/listed worksheets and one or more worksheets becomes closed then the existing message that appears must be modified so that the following information is added as dynamic message text:

• The numbers of closed worksheets
• Run Date
• Run by Whom

System Parameters Affected

 None

Existing functionality affected

Open Worksheet Mass update Order- When we close the selected listed worksheets through mass update order, the existing message is modified with the new information.

Aim of Function

The Aim of this function is to set status Authorized in the Change to field on the worksheet closing window, while selecting the check box change status on both technical and claims worksheet, then the system shall be display default the status Authorized in the change to field.

System Parameters Affected

A new system parameter named ' Default Authorized When Change Status '  can be found under Accounting-> Worksheet, above the parameter “Advanced use of Worksheet Status” . The new parameter gets enabled when “Advanced use of Worksheet Status” is CHECKED.

Existing functionality affected

When a worksheet closing window is accessed and the user manually want to change the status of the worksheet, both Technical and Claim worksheet.

Aim of function:

• When Cease Accounting is set on Business or Insured Period level, then the system should raise a warning message if estimates, reserves or deposits are not down to zero.
• Warning message - BS0865 - There are either reserves, deposits or estimates on this Insured Period/Business and these should be set to zero before Cease Accounting is set.
• The system will still allow us to set Cease Accounting even if the ledger is not cleaned up.

System Parameters affected:

None

Existing functionality
 Cease Accounting.

Aim of function:

To store information about Letter of Credit, Trust and Funds Held on a partner level and to have all this information reportable in Business Object.  
Historical values of increase/decrease amounts including withdrawal of all 3 collateral values shall also be visible on business partner level.

System Parameters affected:

None

Existing functionality
View and Edit Business Partner Properties

Aim of function
Added calculation of an additional premium deposits when running Retrocession Calculation Order. In addition, some change to deposit regulation, and calculation of Interest and Tax.

• Monthly deposit regulations when Order is run monthly, even if account frequency is quarterly
• Monthly Interest calculation
• Tax on Interest calculated on Final Accounts only, i.e. only once each quarter when account frequency is quarterly.

The new functionality is triggered by a new flag on the Outward Cedent's Contract.

Additional Premium tab in Deposit Conditions:

New calculations in Entry Code Usage:

New Entry Code Sub Category within Entry Code Category = Deposits:

New Functionality triggered by new parameter in Insured Period tab on Outward Cedent's Contract:

System Parameters Affected

The new Additional Premium tab in Deposit Condition is only available when system parameter parameter 'Additional Premium added to the Deposit Conditions on Outward Cedent Contract' is selected. This system parameter is found in Accounting/Retrocession/P&C Miscellaneous parameters.

Existing functionality affected

Retrocession Calculation Order

Aim of Function

Currently it is possible to remove Proportional or Non-Proportional Protection assignment from a protected assumed business, even when bookings exists on OCC and Placements.  This is probably causing problems for some client due to potential missing source business link.

So we introduce this enhancement to make sure it should not be possible to remove the OCC completely from the assumed business PP and NP conditions if failed validation. During validation SICS will consider bookings on OCC coming from the assumed business and bookings recorded directly on OCC that have this particular assumed business used as Source Business. In case not all closed bookings on OCC or Placements coming from this source business are not reversed to zero 0 or having any bookings which not in ('Closed', 'Inactive') status,  error message must be raised to prevent the removal of OCC from PP and NP condition of assumed business.

• Aggregation should per Currency, Insured Period, Section, Accounting Classification, Occurrence Year, Entry Code and Claim no (fk_claim_to_soc).
• If the protection is on assumed business sub section and try to remove it, for preliminary bookings only those coming from this section of the assume business will be included in validation, while all bookings directly booked on OCC with linkage to the insured period of the assumed business will always be considered. If the sum of all these bookings per aggregation level are all zero, then OCC protection can be removed.
• If the protection is on the Main section and there are bookings on several sub sections, then bookings coming from assumed business main section and all sub sections are all considered.
• Actual booking and estimate bookings should be aggregated separately.
• Not need to consider manual bookings on placements and linked to assumed business

New functionality should apply to both P&C and LIFE.

System Parameters Affected
Not Allowed to Remove Protection Assignment If Its Bookings Are not Reversed under System parameter maintenance>>Accounting>>Retrocession>>General

 
Existing functionality affected
'Remove Selected' from Assumed Business 'PP' and 'NP' condition 

Aim of Function

Include a new element named periodAndYear in the updatePeriodEstimates webservice to specify the Periods in the Period Estimates tab of Underwriters Estimates Condition with the format Periods/Year (e.g., 1/2021, 2/2021, etc.).

System Parameters Affected
N/A

Existing functionality affected
Webservice Entry Point: SicsWsBusinessEntryPoint/updatePeriodEstimates

Aim of function

Introduced a new flag under Accounting info in Business tab on Outward Cedent's Contract as shown below.

On Selecting, System will Split details with entry codes marked as “premium related” and details with entry codes marked as “loss related” into separate balances for Retrocession Calculation Order and Retrocession Account Order. A new split will be created in addition to any other splits already applicable.

System Parameters Affected

NA

Existing functionality affected

Retrocession Calculation order, Retrocession Account order.

Aim of function

Possible to give the position (New Amount) for an entry code when it is imported to a worksheet also when using the function ‘Import Technical Worksheet from Column Spreadsheet’.

System Parameters Affected

NA

Existing functionality affected

Import Technical Worksheet from Column Spreadsheet

Aim of function
Added 7 new calculations for Special Stepped Sliding Scale Commission, each with own premium basis and Entry Code
Following the same principles as existing Stepped Sliding Scale Commission, but with some major changes, e.g.:

• Special Stepped Sliding Scale Commission is calculated each month, even if account frequency is quarterly
• It is possible to override 'First calculation after' which is set on Stepped Sliding Scale Condition
• Reversal of previous premium basis and commission each month (assumption is that new figures coming in are always accumulated from inception to date)

New calculations added:

Possible to override 'First calculation after' on condition:

Special Stepped Sliding Scale Commission functionality is triggered by a flag on the Insured Period tab on the Outward Cedent's Contract:

System Parameters Affected

N/A

Existing functionality affected

Retrocession Calculation Order

Aim of function

To complete the new functionality started on in 22.3 based on SE- 12648.
To give users an option to split the balances of a Technical or Claim Worksheet on the basis of Special Functional Currency 1 Exchange rules, to ensure that all details within the same balance follow the same exchange rule when calculating the Functional Currency 1 amounts. This split of balances is additional to the other balance split options that take place on a worksheet. Entry codes that are part of any special Functional Currency 1 Exchange rule will be part of their respective separate balances whereas Entry Codes with no Special Functional Currency 1 Exchange Rules will remain in the normal balance. 

System Parameters Affected

A new system parameter named “Split Entry Codes with special FC1 Calculation Rule in Separate Balance” can be found under Accounting-> Currency-> General, below the parameter “Include Realized Gain/Loss In FC Revaluation” . The new parameter gets enabled when “Include Realized Gain/Loss In FC Revaluation” is CHECKED.

Existing functionality affected

• In ALL business processes when the Functional Currency Amounts are calculated on details and the system is reading the Functional Currency Exchange Rules in the system parameters to figure out which exchange rate to be used for the calculation. Regrouping of balances must take placed based on the FC exchange rules for the different entry codes on the details in the balance. Additional to the processes mentioned in SE-12648 we also need to do this for worksheets created by eMessaging, all accounting orders (reserve orders and Multi GAAP)
• When running Retrocession Calculation order and Retrocession Account order we also need to get the balances split according to the above rules, i.e. keep the balances for the details with entry codes with the same FC exchange rules.

Aim of function

 New service for Live desktop OpenBusinessIP

System Parameters Affected

None

Existing functionality affected

Aim of function

A reinsurance company assumes contract from cedents all over the world. In addition, some of these contracts are part of programs.  To help identifying an assumed business searched for, the Find Business display list now also shows the country of the cedent and the identifier of the reinsurance program the business is part of, if any.

System Parameters Affected

None

Existing Functionality Affected

Find Business 

Aim of function

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

Some of these base companies might however have intercompany procedures at a common place. The system now offers some support for this. The user may be set up to have access to his/her current base company's group.  

For functions where the the base company is manually selectable, the system defaults the user's current base company as before, however he/she can now also include more base companies from his/her base company group. Examples of such functions are are:

• Find Business, Find Claims and Find Accounting Worksheets
• Create New Business, Create New Claim and Create New Remittance
• Create Intra Group Contract
• Maintain and update Business Partner Roles 

For functions, where the base company is not manually selectable, the system gives access based only on the current base company, e.g. for Find Insurable Objects. For a few frequently used functions however, the system does offers a direct access based on the ‘user’s group’, even if the base company is not manually selectable, e.g. for Find Business Groups.

System Parameters Affected

System Parameter / Database and Systems:  Extend Base Company Segregation
System Parameter / Database and Systems:  Hide Insureds
System Parameter / Database and Systems:  Hide Business Partners 
System Parameter / Database and Systems:  Hide Base Companies 

Existing functionality affected

Find Business
Create New Business
Change Life Cycle Status of Business
Renew Business
Maintain Business Partner Roles
Mass update of Business Partner Roles
Protect Business Manually
Assign Protected Assumed Business
Create Intra Group Contract
Find Business Groups
Mange Business in Business Group
Perform Accumulation Control of Insured Object
Perform Accumulation Control of Insured Peril Risk Zone
Mass Update Business with Commutation Information
Find Claims
Create New Claim
Find Claim Programs
Create New Claim Program
Find Linked Business and Claims in Claim Program
Find Accounting Worksheets
Create Remittance Worksheet
View Pending Remittances
Find Accounting Data on Business Partner Ledger
Find Retrocession Calculation Order
Run Retrocession Accounting Due Orders

Aim of function
Your organizations may have activated the extend base company segregation facility, which makes your users see information only relevant to his/her base company. As this company may be part of a group with intercompany processes, this facility now offers base company segregation, based on such a group.

To give a user access to a group of Base Companies, the user's Current Base Company must belong to an Owner Group. The intersection of the base companies in this Owner Group and the user's Allowed Base Companies constitutes the group of base companies the user has access to.

When the system in this case is set up to hide company information of other base companies than ones own, it will show only the base companies in this group. 

When the system is set up to hide the company information of the Business Partners belonging to other base companies than ones own, it will show only business partners linked to this group.

When the system is set up to hide the company information of Insureds (Third Parties) belonging to other base companies, it will show only insureds linked to the this group.

System Parameters Affected

System Parameter / Database and Systems:  Extend Base Company Segregation
System Parameter / Database and Systems:  Hide Insureds
System Parameter / Database and Systems:  Hide Business Partners 
System Parameter / Database and Systems:  Hide Base Companies 

Existing functionality affected

Maintain Business Partners
Maintain Insureds
Maintain Business Partner groups
Maintain Owner groups

Aim of function

Enable upload of Claim FGU figures based on an xls spreadsheet.

The upload file should be validated and contain columns for creation of regular and zero worksheets, as well as reinstatement bookings.  The upload does not support multi currency, or multiple adjustments of the same claim in one upload.

Open worksheets will be created.

Parameters affected

None

Existing functionality affected

Create Claim FGU figures

Generate Worksheets from FGU

Generate Reinstatement bookings

Aim of Function

Introduce a new reinstatement premium order for assumed business which can be run across the portfolio, and not be limited to a single Business only. The order should also support calculation of reinstatement premium reserves only. This order should be possible to schedule.

System Parameters affected

None

Existing functionality affected

Create Reinstatement Order for Assumed Business

Period Closing

Aim of Function

In Headline Loss claim list add new filter criteria for Claim ID. The Headline Loss Claim figures as well as all other tabs of the claim list should be updated according to this filter. On Linked Proportional Retrocession, the retro figures should also provide a breakdown per claim

System Parameters Affected

None

Existing Functionality Affected

View Claims linked to Headline Loss

Aim of function

When claim ID series contains year (and possibly also prefix), the system can create multiple ID series for same year if SICS is started from two instances, where the series do not yet exist for a year, and then new claim is created for that year is created from both instances.

System Parameters Affected

Claim Identifier series

Aim of function

When rejecting an eMessage the Acknowledgement is missing the mandatory attribute for Error Indicator.

L4 Acknowledgement Reject message is generated with an Error Indicator with the value 'error_free_format' with Response Description text, that gives the reason for rejection in the rejected eMessage both in SICS and Webservice.

System Parameters Affected

None

Existing functionality affected

Process eMessaging messages

Aim of function

Configure the scheduler to process/ validate messages based on the eMessaging source. eMessaging source will be defined by a Receiver’s Agency. Previously, the system allowed STP for TA/FA/CM process separately, however, it did not have the feature to validate/process messages per eMessage Source (Receiver’s Agency). With the new enhancement, we have introduced the Agency field in the job step parameter, by selecting the dropdown options from the Agency field, the user can perform the process/validation of the existing messages for the selected agency specifically.

System Parameters Affected

N/A

Existing functionality affected

New field Agency added to the Job step parameters: eMessage import and process / eMessage import and validate.

Aim of function

Human set block indicator not to be overridden by message

System Parameters Affected

NA

Existing functionality affected

Claim updates done by eMessaging.

Aim of function

Provide integration with ADEPT (ACORD Data Exchange Platform & Translator)^TM, enabling rapid data exchange, translation, and transformation.
The new integration plugin builds upon the sophisticated SICS eMessaging foundation to provides a next-generation market capability to increase the timeliness, accuracy, and security of business data exchange.

System Parameters Affected
Configuration of a new eMessaging ADEPT gateway plugin.

Existing functionality affected
eMessaging

Aim of function
The EDI component of SICS will be hidden in 23.1 and higher.
The EDI component will continue to be support in older versions for as long as they are contractually supported.

It will not be supported in DXC Assure Reinsurance.

System Parameters Affected
N/A

Existing functionality affected
N/A

Aim of function:

All Views required for the SAP BI Reporting universe are now managed from the System Admin desktop.

System Parameters affected:

N/A

Existing functionality

N/A

Aim of function:

The BOAC Stored Procedures have historically been manually written for each DBMS platform. This has lead to discrepancies in how the procedures work across platforms and duplicate work required when making fixes and improvements.

In this feature we have built a stored procedure generation engine that from one definition can generate the Stored Procedure SQL code for any of the supported DBMS platforms. This will reduce the work required to maintain and develop the BOAC stored procedures going forward and eliminate some manual errors.

System Parameters Affected:

None

Existing functionality affected:

The reporting tab in the Database Maintenance window that generates the BOAC stored Procedures.

Aim of function

The aim of this epic is 

• To Improve the UX of the P&C Share Condition
• To Improve the UX of the Business Partner/Bank/Third Party window.
• Make User Defined fields condition visible only when it is configured for Business

System Parameters Affected

N/A

Existing functionality affected

N/A

Aim of function

To have one set of universes that and connect to and report off of the any of the supported database platforms: Oracle 19c, Microsoft SQL Server 2014+, PostgresSQL 11+
Reports developed in the new universes will not have to be modified to work on each platform.
Existing reports will need minor modification to work on the new Universes.

System Parameters Affected
N/A

Existing functionality affected

N/A

Aim of Function
Update the default countries and currencies shipped with SICS that are used when setting up a brand new database with default settings.

Updated countries and currencies are based on:

• https://www.iso.org/iso-3166-country-codes.html
• https://www.iso.org/iso-4217-currency-codes.html

System Parameters Affected
None

Existing Functionality
Create Base Data function in the system admin workstation.
Note that existing databases are not affected. Only when a new database is created from scratch and the shipped values are loaded into the new database.

Aim of function

The aim of this epic is 

• Improved Business Partner Ledge window.
• Improved the UX of System Parameter screen for Accounting >> Currency >> General.

System Parameters Affected

N/A

Existing functionality affected

N/A

Aim of function

The aim of this epic is 

• To Improve the UX of the P&C Claims - Estimates window.
• To Improve the UX of the P&C Headlineloss window.

System Parameters Affected

N/A

Existing functionality affected

N/A

Aim of function:

Remove violations of the XSD strict enforcement, partially to support the new .NET Core client and partially to just be correct.
Example: SicsWsAdministrationEntryPoint.isAvailable

The modifications to the schema are detailed in the XSD Changes section of the system documentation.

https://www.w3.org/TR/xmlschema11-1/#cos-element-consistent

If the {particles} property contains, either directly, indirectly (that is, within the {particles} property of a contained model group, recursively), or ·implicitly·, two or more element declarations with the same expanded name, then all their type definitions must be the same top-level definition, that is, all of the following must be true:
1 All their declared {type definition}s have a ·non-absent· {name}.
2 All their declared {type definition}s have the same {name}.
3 All their declared {type definition}s have the same {target namespace}.
4 All their {type table}s are either all ·absent· or else all are present and ·equivalent·.

System Parameters Affected:

N/A

Existing functionality affected:

SICS API Server