Release documentation - P&C Enhancements and requests

Problem:

Importing excel file leads to update on the file itself

Solution:

When importing xl spreadsheet to technical worksheet the system shall NOT update the source file with modification of date and size. This must be independent if the xl format is XLSX or XLS. The source file shall never be updated when it is used to uploade its content to a technical worksheet.

Problem:

Business Partner Ledger UI unintentional scrolls right

Solution:

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

Problem:
Abend occurs when mapping is created multiple times from the Worksheet menu

Solution:
When exist import function, refresh SICS to remove objects created in memory.

Problem:
Can't trigger retrocession calculation order for OCC auto booking

Solution:
If IAB is protected by OCC 1:1, when closing the bookings on the IAB, SICS will auto trigger retrocession calculation/account order to generate As bookings and As account bookings on OCC/ORP and linked IGC

Problem: duplicated bookings and commissions not calculated

Solution:

Special Stepped Sliding Scale Commission functionality should support to book on section level with parameter 'Automatically booked figures on section level' selected, without duplicate As booking generated and calculate commission correctly.

Problem:
Performance issue when adding multiple rows to Settlement Balance Group

Solution:
When creating a Settlement Balance Group or Account Balance Group with a large number of balances or include a large number of balances in an existing Settlement Balance Group or Account Balance Group, the system must be able to do this within a reasonable time. The business process to include these big number of balances into the group must be made more efficient.

Problem:

Mass Update of Open Worksheets does not consider the Validation errors and allows to close the worksheet.

Solution:

In the mass update order for open worksheets, when users extract open worksheets using the extraction criteria and attempt to close them, the system must verify if any worksheet contains a validation error message. If a validation error message is present, the system should stop the closing process and display a pop-up validation error message.

The system currently functions correctly in scenarios where worksheets are missing accounting classification, have a closed booking year and period, or do not have any validation message. However, it does not properly handle government tax and accuracy validation errors.

The open worksheet mass update order should display a pop-up error message if any worksheet has a validation error, preventing the closure of that worksheet.

Extent of Impact:

This issue has the potential to close incorrect worksheets that may contain validation errors requiring user intervention for correction.

Problem:
Missing Save Settings Functionality in some accounting windows

Solution:
In the Premium and Limit conditions when navigate to the Instalments tab, the Special Acceptance Premiums tab or the Adjustments tab they all contains containers with a possibility to modify the columns by use of the facility Column View. But in all of these containers it is not possible to Save Settings of these changes. We must make sure it is possible to to save these settings by adding this option in the pop-up menu in the container headings.

The same should be the case when opening the Premium Accounting window, on all the same 3 tabs.

In all the above we must make sure all the standard save, delete and retrieve settings are implemented in the pop-up menu options in the container headings.

Problem:
Abend when searching by Business Identifier from Create Unallocated Remittance Balance Pairings

Solution:
In the balance pairing process, when you select the option 'Create Unallocated Remittance Balance' you must enter all mandatory fields on the URB, including the Business Id. If you do not enter the Business Id, then the system correctly presents error message AC0323. If you now, immediately after you confirm OK on message AC0323, enter a valid Business Id and move out of the Business Id field, the system must not abend, but store the Business Id correctly on the URB.

Workaround :

i) when we do not give any Business ID in the Business field then we must hit the tab button instead of Enter button or click outside the field using mouse,
ii) user can actually close the 'Create Unallocated Remittance Balance' window and reopen it again to prevent the error.

Problem:

In Open worksheet mass update order, the selected filtering options are not being considered for the extraction of matching worksheets.

Solution:

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

Problem:

Bug 2172024: Pairings with missing Balance and Detail Link

When system parameter 'Suppress creation of partially settled Technical- and Claim-Balances' is ON and creating a paring between a RW (less amount than TW) and a TW, SICS will reverse the TW, and create two new worksheets with one equal to the RW and one TW for the remaining amount.

However, when the old pairing needs to be removed and new pairing created. Removal of old pairing will set the balance1 and balance2 to NULL and should delete the row. But actually it just insert one pairing without balance 1 and balance 2

Solution:

Precondition : System parameter 'Suppress creation of partially settled Technical- and Claim-Balances' is ON

While creating a paring between a RW (less amount than TW) and a TW (Partial-settlement) , SICS will reverse the TW, and create two new worksheets with one equal to the RW and one TW for the remaining amount.

However, in ac_stl_pairing table, when the old pairing need to be removed and new pairing to be created. Removal of old pairing should set the balance1 and balance2 to NULL and this old row to be deleted, without leaving a pairing with value 'Null' for balance 1 and balance 2 while inserting the new paring with balance values

Problem:
SICS Bug Report - AC_LEGDER_DETAIL - WKST_SEQ_NBR

Solution:
For each detail created on a worksheet, both Technical and Claim, the system shall set a uniqued number, from 1 and upwards, on each detail on the worksheet.

If a detail on a worksheet is deleted after it has got a number, this number will no longer be used on the worksheet, but new details added will get the next number after the detail with the highest number (this is also current functionality)

Problem:
Wrong Retro commission in case of Reversal on original booking

Solution:

The warning message BS00269 needs to be modified or a new warning message should be presented for the user when Deduction conditions are changed on a Non-Prop Treaty OCC or Fac OCC or it's placements and booking exists with this information:

'The Insured Period being modified has bookings. Future bookings done on this Insured Period, including reversal of existing bookings, will use the current deduction conditions. You should therefore consider to reverse the bookings before the deductions are changed. Do you want to continue'

Problem:

Import of Remittance not working properly.

If System Parameter - 'Own Bank Account is Mandatory for Remittances' is checked. when importing a remittance spreadsheet, in which the bank account is defined but the column 'Bank Currency' is empty.  The ERROR message 'The bank account field is required but has not been specified' triggered.

Solution:

If System Parameter - 'Own Bank Account is Mandatory for Remittances' is checked. when importing a remittance spreadsheet, in which the 'Bank Account' is defined but the column 'Bank Currency' is empty. The system should consider the Payment Currency as Bank Currency and should not show any error.

If System Parameter - 'Own Bank Account is Mandatory for Remittances' is NOT checked. when importing a remittance spreadsheet, in which the Bank Account and  'Bank Currency' columns are empty. Still the system should consider the Payment Currency as Bank Currency and should not show any error.

In above both scenarios, the import should work in the same way of Online functionality.

Problem:

Bug 2285946: SICS_split balance option is not working with gov tax EC

When 'Split balance into details' opted for Government tax EC, system abends.

Solution:

When 'Split balance into details' opted for Government tax EC, system should not abend, instead should trigger error message AC0832 'The Government Tax Trigger EC/Target EC booking link is missing for at least one Government Tax Target EC' as per the existing logic.

Problem:

Copy worksheet & Reverse and Replace functionality:

When the 'Received External date' is being changed for a new booking created by the 'Copy balance' & 'Reverse and Replace' functions, it is not updated in Balance properties screen when saved.

Further, when a 'Note' field of a balance row of the copied or reversed/replaced new worksheet on the close worksheets screen is being edited/changed, such edited note is being updated for the other balance rows as well.

Solution:

Copy worksheet & Reverse and Replace functionality:

When the 'Received External date' is being changed for a new booking created by the 'Copy balance' & 'Reverse and Replace' functions, the same should be updated in Balance properties screen as well, when saved.

Further, when a 'Note' field of a balance row of the copied or reversed/replaced new worksheet on the close worksheets screen is being edited/changed, such edited note should be updated and saved for that particular balance row only, without affecting the Notes of other balance rows.

Problem:

Abend on Mass Pairing Orders when Base Company Segregation and user assigned to base company

Solution:

If a user linked to a particular Base Company by Base Company segregation functionality, when the user clicks the 'Find Now' button on the Find Order screen of Mass Pairing orders (Periodic Functions - Mass Pairing, Mass Pairing of Paid Remittance and Mass Pairing of Technical/Claim balances orders), the abend should not happen. Instead, the system should list the orders relevant to the Base Company to which the user is linked to. If No matching order for the particular Base company, then No matching record message to be displayed. This should work as it is working for other orders.

Problem:

Bug 2299946: System abend when user tries to save Statistics as spreadsheet.

The system produces abend when trying to save the statistics as spreadsheet, when any of the statistics criteria ('Booking', 'Accounting', 'Orig. Accounting', 'Occurrence ', 'U/W' and 'Orig. U/W ') range either 'From' or 'Upto' field left as empty, even though the statistics produced on the Statistics screen for the given criteria.

Solution:

The system should not abend when trying to save the statistics as spreadsheet, even though any of the statistics criteria ('Booking', 'Accounting', 'Orig. Accounting', 'Occurrence ', 'U/W' and 'Orig. U/W ') range either 'From' or 'Upto' field left as empty. The system should save the statistics as spreadsheet, a front page to be created listing all the selection criteria defined for the Online Statistics. The figures on the spreadsheet will have exactly the same structure as the figures shown on the statistics window. This should work in the same way as when any of the criteria range not left as empty.

Problem:

SICSR-31290 - Forced System Refresh - Booking Terms Maintenance - Correction

The fix provided under ** SICSR-31290 ** considers booking terms of all Base companies assigned to the particular user for validation.

Solution:

System should check the booking term, that are being modified by a user, whether it is linked to any base company or not.

1) If linked to a base company/base companies then it will check which users have these base company/base companies as part of their Base Company segregation setup and the user who modifies this booking term will get message 'ADM0005' before saving the modifications.

When the Booking Terms have been modified, and the user doing this, replies Yes to message ADM0005, then this must affect only those users assigned to the Base Company(ies) using this Booking Terms (If any user assigned to more than one Base Company, then the booking term of the 'Current selected Base company' of that particular user should only be considered for validation) with forced refresh message ADM0003. Since one Booking Terms can be assigned to more than one Base Company we must be able to find the collection of users assigned to ANY of these Base Companies in the User Preferences in the field Extended Base Company Segregation.

2)If booking term not linked to any base company Or even if it is linked but this base company is not part of any user's BC segregation setup then it should raise ADM0004 to the user who is modifying the booking term before saving the modifications.

When the Booking Terms have been modified, and the user doing this, replies 'Yes' to message ADM0004, then this must affect whole users in the DB with forced refresh message ADM0003. 

Example:
User A is assigned to Base Company 1 with Booking Terms BT1
User B is assigned to Base Companies 1, 3 & 4 and the Current selected Base Company is 4 with Booking Terms BT2
User C is assigned to Base Company 3 also with Booking Terms BT1
User D is assigned to Base Company 4 with Booking Terms BT2
User E edits Booking Term BT3 which is Not linked to any Base Company or linked to Base company, but that base company not part of any user's BC segregation

When Booking Terms BT1 is changed and Yes is replied on ADM0005, then only user A and C must get ADM0003 to refresh to edit in the system.
When Booking Terms BT2 is changed and Yes is replied on ADM0005, then only user B and D must get ADM0003 to refresh to edit in the system.
When Booking Terms BT3 is changed and Yes is replied on ADM0004, then whole users in the DB must get ADM0003 to refresh to edit in the system.

The Highlighted items are the differences of the fix provided under SICSR-31290 which are to be incorporated.

Problem:
Enhance Retrocession Calculation Order that allows user to pick up some worksheets with as origin status exclude running into as booking status- Not working correctly

Solution:
The Worksheet Exclusion list accessed from the Retrocession Calculation Order should Include Manual Worksheets (made directly on the Outward Cedent's Contract). For the bookings transferred from Assumed Business, system should trace the UWY from the source Assumed Business to display the available balances in the worksheet exclusion list; for the bookings directly made on the OCC, system should display them based on the UWY of the Outward Cedent's Contact. 

Problem:
When Expenses are been set as part of liability and the system parameter- Distribution Of Recovery Reserves Based On Incurred Figures is SELECTED, the system gives an Abend.

Solution:
The system should not abend when running Recovery Calculation for single OCC / Protection Program when SysPar 'Distribution of Recovery Reserves Based On Incurred Figures' is SELECTED. It should calculate recoveries considering correct distribution for Incurred figures - and deduct Paid figures to calculate Recovery Reserves.

Workaround:
None

Problem:
Create Scheduled jobs for Orders is disabled when selecting Create Orders in the Retrocession Calculation Group Order.

Solution:
The option 'Create Scheduled Jobs for Orders' should be disabled when the Retrocession Calculation Group Order has not created any individual orders.

If the 'Create Orders' is selected and the Retrocession Calculation Group Order has created individual orders, the option 'Create Scheduled Jobs for Orders' should be disabled only when the created individual orders has linked to job. If the created individual orders has not linked to job, then the 'Create Scheduled Jobs for Orders' should be enabled.

Problem:

Unexpected AC0227 message raised while remittance status set to Rejected.

Solution:

When the status of existing Remittance changed from one to another, the message AC0227 should not be shown as the worksheet IDs have already been created and available. However, the new status should be updated to the relevant worksheet/s when saving without affecting any existing functionalities.

Problem:
SICS abend when calculating Deposit in Percent of Combination through Retrocession Calculation Order.

Solution:
When running the Retrocession Calculation Order with calculating Deposit in Percent of Combination, system should not abends after running the Order for several times.

Problem:
When creating Recovery Calculation order for Protection Program - it is not including (Include = Yes) any Program sections even though there are realized OCCs.

Solution:
When creating Recovery Calculation for Protection Program, the system should automatically include all Program sections for all Insured Periods where there are realized OCCs linked.

Workaround:
Include sections manually by changing each Program section to Include = Yes

Root Cause:
SE-34164

Problem:
Revaluation Order Long Execution Time

Solution:
Improve the execution time when running the FC Revaluation order in MS SQL Server 2019 databases by optimizing the Query, adding the base company filter.

When Multiple instances run the FC Revaluation Order at the same time, system should not abend.

Problem:

Bug 2406935: Fast  Create Worksheets not changing status to closed

Solution:

When FastCreateTechnicalWorksheet request through SicsWsMigrationEntryPoint, sent with worksheet status element value as 'Closed', then regardless of the value of the element replacementValues whether True or False, the worksheet/s should be generated with closed Status. However, the intended function (showing Previous and New values at worksheet) of 'replacementValues' based on the provided input value, should not be affected.

Problem:

Bug 2433217: TA - GOV TAX - Technical Worksheet Inconsistent behavior for Balance Split Option Government Taxes (ISSUE 309)

Solution:

When selecting 'Change Status' on worksheet window, the Balance detail which are not related to Government Tax shouldn't be taken as separate balance on close worksheet window. The balance Notes should not be as 'Government Tax' for non-Government Tax balances. Balance split should follow selected 'Balance split option'.

Workaround:

The Government tax detail to be given as last detail of the worksheet to overcome this issue.

Problem:

Bug 2467628: TA - GOV TAX - Technical Worksheet Inconsistent behavior for Balance Split Option Government Taxes (ISSUE 309) - Issue1

Solution:

When split option 'Government Tax' only selected while creating worksheets, while entering further balance details after the Government tax detail, the message 'AC0163' should not be shown as there is no actual background grouping happening.

Problem:

The system abends when renewing a business with Informational status and empty Share Conditions to a period also with informational status. 

Solution:

When renewing a business from a period with empty Share Conditions and with an existing Premium Instalment Schedule to a period also with empty Share Conditions, the system should not abend. Instead, it should renew the business as normal.

Workaround:

1. In the Share Conditions of the period to be renewed, please enter a 'Share from 100' value, for example 0.00.
2. Renew the business.
3. Open the renewed business and remove the Share Conditions again on both the new and the old insured period. 

Problem:
Searching for Master Treaty Groups, starting from a business, has a too long response time when Base Company segregation in use and user assigned to base company. It eventually ends in an abend.

Solution:
Development:
Searching for groups, starting from a business, should have a similar find facility as when starting the search from the groups side.

Problem:

When deleting Limit & Premium conditions of a Declaration which was created as part of an amendment, the system abends.  This occurs only when there is also another declaration on the business that was not created as part of amendment and which has inherited P&L Conditions.

Solution:

When a Declaration, created as part of an amendment, has overridden Premium  and Limits Conditions, the system should not abend  when  trying to remove its Premium and Limit Conditions. Instead it should restore P&L from the parent section. This should happen also when there is another Declaration on the business that was not created as part of amendment and that had inherited P&L conditions. 

Problem:

Share from Net of Gross in the share conditions is not recalculated when the user changes the Order in the placement group box.

Solution:

Type of Business: Non-Proportional Treaty

Share Conditions:
When having values in both the Net of Gross and the Order fields, when changing the Order value, the system should automatically recalculate 'From Net of Gross' accordingly. 

Problem:

It is not anymore possible to enter the Layer Number of an outward cedent's contract on the Life Cycle Tab.

Solution:

When selecting the Life Cycle tab of an outward cedent's contract, the system should show the field Layer No. and the belonging Edit button.  When selecting the Layer No. Edit button., the user should be able to enter a number.

Workaround:

In the Business wizards, e.g. Create New Business, the Layer No field is available on the Classification Page (at the bottom)  and can be entered.

For already existing Outward Cedent’s Contract, you can try the following:
-Enter the Layer Number in the Update Business Wizard:
-On the Life Cycle Tab, from the menu button in the bottom right corner, select the choice Update Business, press Next until you see the Business Classification page. Here, enter the Layer No.

If the Update Business choice is not enabled, or the classification page is missing from the Wizard, you need to first set up the wizard as follows:
-Select Reference Data Maintenance
-Find Type: Business Wizard Page (Code 01008)
-Double Click the value ‘Business Classification’
-Select ‘Parent Dependencies’
-Double click the value ‘Update Wizard’
-Select OK

Problem:
System abends when selecting premium and limit conditions after removing type of business covered 'non-proportional facultative'.

Solution:

For Types of Business Methods:

• Proportional Facultative
• Proportional Direct
• Proportional Treaty when the business has the Single Treaty Protection flag set to Selected (on the Business tab)

When having recorded Limit and Premium Conditions, and the user removes all Type of Business Covered that are non-proportional, e.g. non-proportional facultative, the system should stop the user with a warning. The same warning message should be given, as currently correctly given when Type of Participation Method is changed,: 'BS0602: Any existing limits will be lost. Do you want to continue Yes/No.' If answering Yes, the system should remove all limit items in the Premium and Limits Conditions. Only the items set up for the new Type of Business Covered should be available.  If replying no, the system should revert to the classification tab without changing the Type of Business Covered.

Workaround:

Please check the below for a workaround to avoid the abend in attachment called existing_OCC_walkback:
I assume that they removed the type of business covered ‘non-proportional facultative’ because this business does not cover non-prop. This business should therefore also not have any non-proportional limits.
-Open the problem business and select the Classification tab.
-In the Coverage table, from the pop-up menu, select Edit Classification
-Then from the pop up menu, select Type of Business.
-Move back the non-proportional facultative value (move from available to selected) and Save.
-Do a full refresh.
-Open the business again and select the Premium and Limit Condition.  
-Take note/screen shots of all limits and premiums on the Main tab, Original and Original Details tab.
-Then on the Main Tab, select Delete from the menu button, and select Yes.
-Select the Classification tab again.
-In the Coverage table, from the pop-up menu, select Edit Classification
-Then from the pop up menu, select Type of Business.
-Remove the non-proportional facultative value again and Save.
-Do a full refresh.
-You should now be able to open the Premium and Limit Conditions
-Enter again the limits and premiums. Save.

Problem:
On the Life Cycle tab a business, the system does not update the Last Updated name and date after changes of Wording status.

Solution:
On the Life Cycle tab a business, when updating the of Wording information, the system should update the Last Updated name and date, (the same way as it currently correctly does when changing other fields on the same tab).

Problem:

System parameter /Business / Business View /On Business Title Bar Show:

• Business Partner - SELECTED
• Business Partner Name - SELECTED

Business Partner Name and Business Partner Identifier are not shown in the Title Bar for Premium and Limit Conditions

Solution:

Business Partner Name and Business Partner Identifier should be shown in the Title bar for Premium and Limit Condition in the same way it is shown for other business condition. When refreshing the opened business condition window (by clicking the Insured Period field) the Business Partner Name and Business Partner Identifier should not disappear, but still be shown

Problem:

The system abends on protection programs, when outlines are overlapping and tabbing out of e.g. the Excess field on the 2nd facultative outline.

Solution:

When in a protection program creating multiple outlines, e.g. 2, and there is an overlap between the outlines, system should not abend when tabbing out of the 2nd outline's e.g. Excess field. The system should instead keep the values, like it currently correctly does if you click on the next field instead of tabbing.

Workaround:

Instead of tabbing out of e.g. the Excess field, the user can click on the next/wanted field. 

Problem:

The system gives an  'intervening object' message and then abends when adding sub section to a business after another user has just added a section on the same business.

Solution:

The system should not gives an  'intervening object' message when a user adds a sub section to a business after another user has just added a section on the same business. It should instead add the sub section to the business without any such message. 

Problem

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

Solution

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

Close the Criteria Selection window.

Problem: Signature notes objects under headline loss are not available in the universe.

Solution: Need to create signature notes objects in the PC Main universe under headline loss folder under claims.

Problem:
When we try to create a new claim manually on an IP which is Ceased, we get error BS00486 raised and no claim can be created:

However, eMessaging is creating the claim and only than raising the error, this requires a lot of manual work to fix/correct and to create the claim manually on the correct contract.

Error is raised. However, only when the claim is already created - this is too late, the check should be included in the 'create claim' rule so it is detected on time.

Solution:
Validation on Cease Accounting on Business or Insured Period should be applied upon Claim creation and raise problem / error preventing creation of Claim if set.

Problem:
System abends when user tries to create a new Various Claim Details on the Various claim through Webservices.

Solution:
Details for<variousClaimDetailList> with<variousClaimDetail> should be correctly assigned on to the Various Claim using UpdateClaim Entry point.

Problem:

The system generates the error message 'Business field required but has not been specified' when claim protection allocation (either automatic or manual) is performed for the protection program or outward cedant contract via an API.

Solution:

To protect the claim with a protection program or outward cedant contract, the business ID included in the SOAP file must be identified.

Problem:
When the Business has Reinstatement condition as Per Insured Period, and the Reinstatement has already booked, system abends when Automatic Reinstatement Calculation is attempted.

Solution:
System should generate a blank TW without any abend

Problem:
The 'Unlimited Cover' Boolean field for the Claim Limit is missing in DR for a Claim

Solution:
The Unlimited Cover Boolean field should be included in the DR for Payment and Incurred fields.

Problem:

The joint contract/Master Agreement/Insured's contract business, shows the FGU indicator as enabled, and the FGU recording option is accessible from the claim list, even though FGU is not available on these level of business

Solution:

FGU options should not be available on the Joint contract/Master Agreement/ Insured's Contract. FGU indicator on the claim should be disabled and the FGU recording on the claim list has to be excluded and not available for selection.

Problem:

Claims/Claim worksheets created on the Administrator business through an API, does not create claims/claim worksheets on the other placements on the Joint Contract

Solution:

Claims/Claim worksheets created on the Administrator business through an API, should automatically create claims/claim worksheets on the other placements on the Joint Contract

Problem:

Claim creation on the Master Agreement, through an API, generates walkback error

Solution:

To be able to create a claim on the Master Agreement level of business.

Problem:

When creating a claim on a Fac or Direct with a single claim basis the system defaults the Claim Trigger Code. Only required input is the Claim Trigger Date.

In SICS Server the system always requires both Code and Date. If not both are provided SICS Server always returns error 'Claims Trigger Date is required but has not been specified'.

Solution:

For Fac and Direct business, when Claim trigger code is defaulted, the system should only require Claim Trigger date in SOAP input.

For treaty business the system must still require both if either Code or Date has been provided.

Problem:

createClaim API requires Date of Loss within Insured Period when Claim Trigger is Manifestation.

Solution:

Validate that Claim Claim Trigger Date within Insured Period, and (optional) Date of Loss should be prior or equal to Claim Trigger Date.

Problem:

At the Insured Contract level, the booked amounts are not displayed in the upper part of the claim list.

Solution:

At the Insured Contract level, Claim list should display the booked amounts on the upper part as well

Problem:

Incorrect validation that Date of Loss is within Insured Period when Claim Trigger Code is Causation.

Solution:

Correct validation is that the Date of Loss must be equal or greater than the Claim Trigger Date; not necessarily within the Insured Period{}

Problem:

Additional Code and Additional Code Date fields are missing from Individual Claim Properties, and the wizards.

Solution:

The fields should be displayed in create/copy wizards and on properties.

Problem:

The Annual Aggregate Deductible Reserve displays double amount on the Claim List for Quota Share.

Solution:

Display the actual booked amount.

(Please note that AAD functionality is not supported for Quota Share treaties.)

Problem:

Joint Contract-Claim/CW created on the Administrator business through an API, does not automatically create Claim/CW on the other placements

Solution:

Claims/Claim worksheets created on the administrator business through an API, has to automatically create claims/claim worksheets on the remaining placements.

Problem:

Error message referring to 'Received Date' AC0723 when creating a multi business worksheet or changing any date (received date, booking date, due date, as of date) (TWK and CWK)

Solution:

Confirmation message text AC0723 should be changed to 'Should the new Date be applied to this Business only?'

The message should appear when changing any date in the Account Information section of the worksheet for a multi business claim or technical worksheet. 

The validations of these dates should remain unchanged.

Changing dates in the balance or detail section of the worksheet should not raise AC0723. Existing validations for these dates should also remain unchanged.

Problem:
The CM Lead message is responsible to invoke the FGU calculation and create through the FGU functionality the appropriate entries for all assigned claim sections.

Any follower CM message and the related TA messages are only validating consistency and ultimately updating the references on the related worksheet and balance.

The TA RIP messages which are part of the group are creating dedicated balances. However, if the worksheet related to the CM Lead message is not closed (status processed) the TA RIP messages are subject to create balances on the CM Lead message worksheet.

Bug:

Where is the as of date of September 15, 2020, coming from and why is that picked-up and used for the highlighted entries? Why are they not part of the Jun 30, 2024, as of date entry?

Solution:
A TA RIP booking on an existing Claim Worksheet from a CM should set the same dates regardless of booking on an Existing CW or on its own and not use a date from the previous balance referenced which is part of the ModifyClaimBookingBehaviourRule functionality and not to be used when that rule is not active.

Workaround:

Root Cause:
Incorrect application of part of LM Method of bookings Reserves from CM and Reverse and Rebook with TA (dates being set with incorrect method applied).

Extent of Impact:
Booking a TA RIP on an existing claim worksheet where the RIP is referenced to a previous balance having a different (prior) As Of Date.

Problem:
For the outgoing Remittances SICS should follow the logic 'Value/Due date=T+3', however seems that it is not followed for Processing eMessaging REM worksheets where the value/due date for eMess RM is equal to Document/Received date of B2B message and not +3 Dayes from Creation Date.

Solution:
Regardless of the method of Remittance Creation (Process or Swap-to), per the System Parameters and rule settings the Remittance should be set with either Settlement Date or the specified number of working days after the message CreationDate.

Workaround:

Root Cause:

Extent of Impact:
Creating a Remittance via Processing a Settlement message (rather than manually creating)

Problem:
If a message gets processed, either manually or by the scheduler, that is linking to a business that has multiple AC's and the Message Processing Option blank,

The system crashes.

While we're aware the setting is needed, we're not expecting SICS to crash.

Solution:
Ensure that in all cases if a value is not explicitly set then the Base Company, System Parameter default value should be used and not a null value.

Problem:
Abend calculating net booked instalment amount in adjustment calculation with deduction as amount but no current instalments.

Solution:
If the deduction is an amount then it is split over the number of instalments. If there are no instalments at this point then the amount is taken as-is.

Problem:
Checked and we were able to create Claim without HLL link although mandatory MCoB Prop Cat was set up. Do we miss something else?

Solution:
When UpdateClaim rule resets a partial / incomplete Date of Loss with an actual full date (specific one time only case) then ensure that the Claims Trigger Date is also set as would have occurred if the complete date were provided to begin with upon claim creation.

If a problem is raised on the Claim FX Date of Loss (when in use) then log this as a warning regardless of LogApplyWarningsAsErrorsForClaim

Root Cause:
Incorrect use of system turning off LogApplyWarningsAsErrorsForClaim

Extent of Impact:
Claim FX Date of Loss validation

Problem:
We have an abend when we run the scheduler caused by SicsAcordTechAccountMessageImpl.sectionToActOn()

Two kind of abends for the moment:

• SicsAbstractBusinessScopeOfCover.18()' because the return value of 'com.csc.sics.emessaging.domain.impl.SicsAcordTechAccountMessageImpl.sectionToActOn()' is null
   
• SicsAbstractBusinessScopeOfCover.accountingClassificationsAvailableActiveAndValidForMe()' because the return value of 'com.csc.sics.emessaging.domain.impl.SicsAcordTechAccountMessageImpl.sectionToActOn()' is null

Solution:
If there is no Section referenced then rule TestForOutstandingLossToReverseValidationRule should exit as it cannot run yet.

Workaround:
Override rule TestForOutstandingLossToReverseValidationRule or ensure that message can reference to a Section.

Problem:

CheckLiquidBalanceControlTotal - AC0543 - Liquid balance total -33’796.00 does not match the original original liquid balance control amount -16’898.00

Solution:
Split options should be defaulted and grouping of details on balances applied before eMessaging control amounts are set.

Problem:
System abends when Discarding a message indirectly being part of a group of messages where another is being discarded.

Solution:
When discarding messages that are part of a group then this should successfully discard all messages.

Workaround:
Turn off System Parameter eMessaging - Processing Options - Automatically Discard Related Messages

Root Cause:
SE-25003 - Discarded messages to keep the link to business insured period if mapped already

Extent of Impact:
Automatically Discard Related Messages

Problem:
AssignClaimToClaimsProgram for Existing Claims and for almost all the cases we tested error 'multiple matching claims programs found' was generated. Only in one case was this behaviour as expected - there were two claims programs which were matching fully both with the emessage and the existing claim. Other than this scenario we received this error message where it would not have been expected for the various scenarios.

Solution:
AssignClaimToClaimsProgram should not raise an error (Multiple matches in this case) when there is a single ClaimsProgram matching the Claim Section on the message.

Problem:
Abend when BookReinstatementAccruals is applied to a message that is not booking a Claim Worksheet,

Solution:
BookReinstatementAccruals rule is only applicable for messages booking on a Claim Worksheet with Reinstatements Per Loss and should have no effect at all on a message booking a Technical Worksheet.

Workaround:
Turn off the rule BookReinstatementAccruals from TechAccount Messages as default (Message Function None) and only turn it on for a Message Function(s) that will book a Claim Worksheet.
Alternatively for Tech Accounts, only add the rule to specific Claim Worksheet related rule sets / message functions e.g. Reinstatement

Root Cause:
Missing test on type of worksheet being booked by message when implementing BookReinstatementAccruals

Extent of Impact:
TechAccount messages for a contract with Reinstatements Per Loss that is not booking a Claim Worksheet.

Problem:
The CM & TA messages are linked with the new claim ID and are in status waiting. The reinstatement premium message is in error and no reinstatement premium has been booked. If we try to link the message with the business insured period and/or the new claim the system crashes.

Solution:
LinkTAReinstatementToCMReferenceRule should correctly match to an existing Claim Balance based on the type of booking being made (without abend).

Problem:

The client is facing issues while running  for BOAC005 and supp005 scripts.

Solution:

BOAC_STL_PAIRING  Table is  getting duplicate data when running the procedure with parameter B

that is creating performace issue due to exponetial growth of table every time 

fixing the issue will resolve redundatnt data as well as performance 

Problem:

OCC Placement Screen showing 'Ded.Inherited' yes or no not reportable as object does not exist.

Solution:

Need to create a below objects for field Ded.Inherited in Placement tab -
1) Deduction Type:-      Concat(Concat(PA_DED_ELM_Com.FRK_TYPE,PA_DED_ELM_Bkg.FRK_TYPE),PA_DED_ELM_Other.FRK_TYPE) 

2) Ded.Inherited :-
    Case when @Select(PA Deduction Conditions / Deduction Type) is not null then 'Yes'          ELSE 'No ' END

Problem:

The database table BUS_RETRO is not updating FK_SOC in all instances. It is giving NULL in few businesses which is wrong, and it should return some value.

Solution:

We need to modify the script given below as its is updating FK_SOC for one business only. In the updated script FK_SOC should be updated for all the businesses. 

SCSR-30296_SOLUTION SCRIPT.docx

Problem:    Work sheet are missing in BOAC_PC_FACT TABLE after running incremental load

Solution:   Need to add adjust the  BOAC004 procedure for incremental load

Problem:

Users want to see new option for Quarter while doing exchange rate calculation in detail amounts.

Solution:
Need to add BOOKING_YQ_LOCAL, BOOKING_YQ_LEGAL, BOOKING_YQ_GLOBAL columns in V_BOAC_PC_FACT view.
Change definition of objects under Support/Exchange Rates/Entry Codes folder from 'V_ENTRY_CODES_DATES' to V_BOAC_PC_FACT.
Add option to user for Quarter selection in these objects.

Problem:

In the current database view, we can only see the related state; it does not come out with the country.

Solution:

Need to modify the view V_CLAIM_LOCATION_JURISDICTION.CREATE OR ALTER VIEW V_CLAIM_LOCATION_JURISDICTION.sql

Problem:

Unique index IX_STL_BAL1 crashing the incremental load of BOAC005 script.

Solution:

Need to update the BOAC005 Script with suggested changes by adding the condition.

Problem:

Test Prefix Object By Parsing correction of SQL.

Solution:

Modify the object definition of Test Prefix Object by as per the following:

@Select(Support / Prefix_Object)get_exch_rate_and_euro(V_ACLB_B2.FK_CURR,

@Prompt('1. Enter Base Currency','a','Currency / Primary',mono,free),'NA',

@Prompt('2. Enter Base Exchange Rate Type','a','Exchange Rates / Category - Code',mono,free),

Case @Prompt('3. (Booking Base) Enter timeline according to base exchange type','a',

,mono,free)

when 'Today' then V_ACLB_B2.TODAY

when 'Date of Booking' then V_ACLB_B2.CHAR_DATE_OF_BOOKING

when 'Due Date' then V_ACLB_B2.CHAR_DUE_DATE

when 'Accounting Year' then V_ACLB_B2.ACC_YEAR

else @Prompt('3. (Booking Base) Enter timeline according to base exchange type','a',

,mono,free) end)

Problem:

Getting a lot of error messages regarding the view V_LIGHT_ACC_CLASSIF_ALL when parsing the Cede universe against a cede SQL Server database.

Solution:

Need to alter view V_LIGHT_ACC_CLASSIF_ALL for SQL Server.

Problem:

Stonefort - Special Currency Conversion Option.

Solution:

1. Adjust the views V_AC_LEDGER_BALANCE & V_BOAC_PC_FACT as per the script given below:

Stonefort - CREATE OR ALTER VIEW V_AC_LEDGER_BALANCE AND V_BOAC_PC_FACT.sql

2. Adjust the detail and balance objects in support folder so that it includes the new changes in the prompt part like given in an eg below for detail base conversion:

@Select(Support/Prefix_Object)get_exch_rate_and_euro(V_BOAC_PC_FACT.FK_CURR,

@Prompt('1. Enter Base Currency','a','Currency/Primary',mono,free),'NA',

@Prompt('2. Enter Base Exchange Rate Type','a','Exchange Rates/Category - Code',mono,free),

case @Prompt('3. (Booking Base) Enter timeline according to base exchange type','a',

,mono,free)

when 'Today' then V_BOAC_PC_FACT.TODAY

when 'Insured Period Start Date' then V_BOAC_PC_FACT.INSURED_PERIOD_START

when 'Inward Insured Period Start Date' then V_BOAC_PC_FACT.INWARD_INSURED_PERIOD_START

when 'Underwriting Year' then V_BOAC_PC_FACT.CHAR_UW_YEAR

when 'Last day of Month' Then V_BOAC_PC_FACT.CHAR_LAST_DAY_OF_MONTH

when 'Date of Booking' then V_BOAC_PC_FACT.CHAR_DATE_OF_BOOKING

These are the objects in universe which will need to be adjusted once the changes are done at view level.

Problem:

View V_REINSTATEMENT_ALL is having the old code that is using STUFF() Function.

Solution:

Need to update view as suggested to use STRING_AGG() function as it is better function to use in SQL Server to improve performance.

Problem: 

All limits values are not correct in the reports.

Solution:
Create a derived table 'EXCH_RATES_LIMITS_DER' in PC Main universe.
Change the definition of 3 objects Limit/Premium Currency (Code), Exchange Rate Limit, Exchange Rate Excess.

Root Cause:

To find out original limit value we are using Exchange rate limit value which is coming from premium table. Because of these limits and premiums in one query causing data duplication.

Problem:

In SICS SYS Admin guide under chapter 16.4 the description for BOAC004_REVALUATION procedure is missing and also there is XML script for BOAC004_REVALUATION.

Solution:
Need to add description for the procedure BOAC004_REVALUATION in all the places in SYS Admin guide.
Need to create a new XML script for BOAC004_REVALUATION procedure.

Problem:

Join issue in PC Main universe .

Solution:

This join needs to be changed to the ACLD instead of ACLB.

For changing this join we need to alter the view V_RETRO_DTL_PAIR_TO_INW_DTL.

CREATE OR ALTER VIEW V_RETRO_DTL_PAIR_TO_INW_DTL.txt

Problem:

Missing Joins for Collateral type objects.

Solution:

Need to add missing joins for the tables REF_BAL_Collateral_Type and BOAC_REF_BAL_Collateral_Type. Also, need to add missing join between the tables REMITTANCE_COLLATERAL and V_AC_LEDGER_BALANCE.

Problem:

There are some objects that exist in both version 24.4 and version 25.1, and even though their definitions are the same/or not, they are still highlighted in the documentation on the 25.1 PC Main side with different object id. This likely means that the highlighted objects in the 25.1 documentation have different object IDs compared to those in version 24.4.

Solution:

For each object where we are facing this issue, we need to delete the object from the 25.1 PC Main Universe and copy it from the 24.4 version into 25.1. This will ensure that the object ID remains the same in both versions—that is, the object ID from 24.4 will be retained in 25.1 as well.

Problem:

Naming of the universes we have delivered are wrong.

Solution:

Need to adjust the naming of the universe as mentioned like below.

The universe name should  be Cede Light SICS. Like that we need to change  for all the universes.

Problem:

User custom objects are not available in eMessaging universe.

Solution:

*Need to add custom objects in eMessaging universe.

*Development objects are already available in the universe.

• We need to create 50 custom objects in universe.

Problem:

Development objects are missing in the LOG Universe.

Solution:

Need to add development objects in the LOG Universe same as we have in PC Main Universe.

Problem:

In Reference Universe, the  bo_dm_activity_log table was not found.

Solution:

Convert the table to uppercase, and it will be located when parsing the universe structure.

Problem:

User Custom Objects and Development Objects are not available in the universe.

Solution:

*We need to add both development and custom objects in the universe.

*Task manager universe is a tiny one, we can add both development and user custom objects in a limited way.

Problem:

 Development Objects  are not hidden

Solution:

Need to hide the development objects and  support objects in PC main universe.

Problem:

Tables or views naming conventions do not match between the Universe and Database.

Solution:

The name of the tables should have the same conversion across the database platforms and the SICS BO Universe.

Problem:

The following objects have still wrong LOVs in eMessaging Universe in SICS 25.1:
LORS Transaction > Status
Rules > Message Function
LORS Transaction > Base Company (showing all partners names not just base companies)
Rules > Message Type
Accounting Validation Rules > Tolerance
Accounting Validation Rules > Error Type
LORS Transaction > Old Status
LORS Transaction > New Status

Solution:

We need to modifying lov sql in SQL Viewer for the all objects having issues

Problem:

MDP on placements showing everything as not booked, but on OCC is showing correct numbers.

Solution:

Modify the SQL definitions of the 4 objects namely,
Instalment Premium Amount:
case 
when @Select(Business Information
evel of Business (Code))= 'ORP'
then V_INSTALLMENTS_OCC_ORP.PREMIUM_AMT*V_REPORTING_TABLE.CURRENT_SHARE
Else
coalesce(V_INSTALLMENTS_OCC_ORP.PREMIUM_AMT, 0)
END
Instalment Net Premium Amt:
case
when @Select(Business Information
evel of Business (Code))= 'ORP'
then V_INSTALLMENTS_OCC_ORP.NET_PREMIUM*V_REPORTING_TABLE.CURRENT_SHARE
Else
V_INSTALLMENTS_OCC_ORP.NET_PREMIUM
END
Booked Premium Amt:
case
when @Select(Business Information
evel of Business (Code))= 'ORP'
then V_INSTALLMENTS_OCC_ORP.BOOKED_PRE_AMT*V_REPORTING_TABLE.CURRENT_SHARE
Else
V_INSTALLMENTS_OCC_ORP.BOOKED_PRE_AMT
END
Remain to Book Amt:
case
when @Select(Business Information
evel of Business (Code))= 'ORP'
then V_INSTALLMENTS_OCC_ORP.REMAINING_TO_BOOK*V_REPORTING_TABLE.CURRENT_SHARE
Else
V_INSTALLMENTS_OCC_ORP.REMAINING_TO_BOOK
END

After making these changes we are able to view data correctly in the reports which are in accordance with SICS data.

Problem:

Missing documentation for UNX universes. 

Solution:

Need to add document for steps to create new connection in IDT. This will again allow us to have ONE universe and dependent on the user/group it will then connect to different databases. Which is very good when it comes to implementation and testing.

Problem:

25.1 - UNX universes - Allow Cartesian Products.

Solution:

Untick the option 'Allow Cartesian Products' in the SQL options tab in data foundation layers for all the UNX format universes in IDT.

Problem:

1. When run Incremental load for BOAC004 procedure, Getting errors like Cannot insert duplicate key row in object with the tables BOAC_BOOK_PERIODS with unique index 'IX_BOOK_PERIODS and BOAC_ACCT_PERIODS with unique index 'IX_ACCT_PERIODS.

2. Got an issue When creating BOAC004_REVALUATION Procedure. The issue: 'STRING_AGG' is not a recognized built-in-function name

Solution:
Add truncate statements for the tables BOAC_BOOK_PERIODS, BOAC_ACCT_PERIODS in BOAC004 procedure.
BOAC004_REVALUATION_with_STUFF.create.sql This file has not contain STRING_AGG() in it.

Problem: 

Objects Detail Amount Settled (Func) and Detail Revaluation Amount Settled (Func) are not working properly.

Solution:

Need to change queries for Objects Detail Amount Settled (Func) and Detail Revaluation Amount Settled (Func). Alter view V_FC_REVAL_DTL_BYRP to get correct Accumulated realized data.

Problem:

Missing documentation for Tomcat upgrade, especially the Tomcat that is bundled with SAP BI.

Solution:

Need to create new document with the steps required for Tomcat upgrade and these steps are for Linux and windows. Also, these steps can used for updating Tomcat on SICS Server that is running API, Search, Live Desktop etc.

Problem:

Target 2 object is not parsing in the PC main universe from the support folder.

Solution:

Need to correct V_BOAC_PC_FACT.BOOKING_YP_GLOBALL

*It should be V BOAC_PC_FACT.BOOKING_YP_GLOBAL

Problem:

Missing documentation for how to upgrade from 4.x - 25.1 UNV format to UNX 25.1.

Solution:

Need to create new document with the steps required to upgrade from UNV to UNX. Because while upgrading universe the normal copy and paste is not working between UNV and UNX as the format. So, we need to follow the steps attached in the document.

Problem:

Missing documentation for the UNV to UNX Report Upgrade from SICS Sys Admin.

Solution:

Need to create new document with the steps required for UNV to UNX Report upgradation.

Problem:

Labuan - Today's Date and Yesterday's Date- forming cartesian product issue.

Solution:

1. Add the SQL definitions from V_DATE_LOV into the views V_AC_LEDGER_BALANCE & V_BOAC_PC_FACT as below:

CAST(CONVERT(VARCHAR,getdate(),102) AS DATETIME ) as TODAY_102,
cast(convert(char,getdate(),102) as datetime) + 0.99999 as LAST_SECOND,
convert(numeric,CONVERT(VARCHAR,DATEPART(QUARTER,getdate()))) as DATE_QUARTER,
convert(numeric,CONVERT(VARCHAR,DATEPART(YEAR,getdate()))) as DATE_YEAR,
convert(numeric,CONVERT(VARCHAR,DATEPART(YEAR,getdate()))) - 1 as LAST_YEAR,
convert(numeric,CONVERT(VARCHAR,DATEPART(MONTH,getdate()))) as DATE_MONTH,
CONVERT(VARCHAR,getdate(),112) AS TODAY

2. Add the below mentioned part in the script of the view V_REPORTING_TABLE to add Today column in the view.

CONVERT(VARCHAR,getdate(),112) AS TODAY

3. Change the SQL definition of the object Commuted Effective date as shown below:

case INSURED_PERIOD0.FRK_COMMUTATION
when 'NONE' then INSURED_PERIOD0.COMM_EF_DATE 
else coalesce(INSURED_PERIOD0.COMM_EF_DATE, V_REPORTING_TABLE.TODAY) end

Problem:

We have a slight problem with Underwriters Estimate in the PC Main universe

Solution:

Need to alter the view for V_US_EST_LATEST and need to adjust the join between V_UW_EST_LATEST and V_REPORTING_TABLE.

Note: Joins are missing for both V_UW_EST AND V_UW_EST_LATEST on the UDT side. We need to add the joins for both.

Problem:

Missing documentation for setting up SAP BI LDAP SSL/TLS.

Solution:

Need to create new document with the steps required for setting up SAP BI LDAP SSL/TLS.

Problem:

25.1 PC Main Universe (UNX) - Insured Period Position needs to change its data type.

Solution:

Need to change the data type of the object insured Period Position from 'Date' to 'string' so that we can fetch the report without any errors.

Problem:

New objects needs to be added  in Reference data universe 25.1

Solution:

We need to add the BO_DM_ACTIVITY_LOG_REVALUATION table in the universe structure and add the same objects which are in BO_DM_ACTIVITY_LOG

Here is the list of some new objects that need to be added in the universe.

• Country Group Alternate code
• Currencies objects in countries
• Market interest rates on countries.
• VAT Notes on countries
• Indexes on Countries
• Fund Type 
• Tax on interest
• Account Administration
• Risk Zone notes
• Risk Zone Tob/Mcob combination
• Entry code maintenance objects
• Entry code loss/Premium related, VAT code, cession basics, and restrictions and advanced setting objects are missings
• Reference data notes and search priority objects 
• Currency As form date
• Reporting unit notes
• MGAP Estimation and also underwriter estimates objects
• Security short name
• Security Active access code
• Security accounting setting objects
• Security Task Group.

Problem:

Issue with the view V_CLAIMS_HEADLINE_LOSS and also need to adjust the universe level joins and objects.

Solution:

The view V_CLAIMS_HEADLINE_LOSS needs to be modified and also the objects query needs to be adjusted.

Problem:

Business Count object is defined as char instead number

Solution:

Business Count object in IDT should be defined as number instead string. Also, need to take away the cast function from Object definition as it is not needed.

Problem:

Base Company ID & Base Company name from the accounting objects is causing bad performance.

Solution:

Modify the SQL definition of the objects Base Company ID & Base Company name under the class Accounting Information> Accounting Business Partners.

Base Company ID:

@Aggregate_Aware(BOAC_DIM_PARTY.BC_IDENTIFIER,V_AC_LEDGER_BALANCE.BASE_COMPANY_ID)

Base Company name:

@Aggregate_Aware(BOAC_DIM_PARTY.BC_CURR_NAME,V_AC_LEDGER_BALANCE.BASE_COMPANY_NAME)

Problem:

SQL in the ORDER BY part was not working as it should for the derived tables: V_BOAC_STL_PAIRING, V_BOAC_STL_PAIR_START, V_BOAC_STL_PAIR_END and V_BOAC_STL_PAIR_FOLLOWER

Solution:

Order by part in SQL of the derived tables needs to be adjusted.

Problem:

Reporting unit Name (All) and Reporting unit (Code) (All) objects

Solution:
Add a database view as per the script provided.
V_REPUNIT_ALL_VIEW_SCRIPT.txt
Add three objects at universe level for leaf name (all), leaf code(all) and category(all) after adding the new view in universe structure and joining it with V_REPORTING_TABLE as per the join below:
V_REPORTING_TABLE.FK_SOC=REP_UNIT_ALL.FK_SOC

Reporting Unit Leaf Name(all) : REP_UNIT_ALL.LEAF_NAME_ALL
Leaf(code)(All) : REP_UNIT_ALL.LEAF_CODE_ALL
Reporting Unit Category(All) : REP_UNIT_ALL.REP_CATEGORY_ALL

After making all these changes we can view the report in the way Report user requested.

Problem:

To make the triangulation reports to split their numbers on currency for the actuary review, there is no currency code object to the triangulation structure.

Solution:

It would be needed to have accounting currency in the triangulation allowing for merger in the report on currency. We need to add currency code object to the triangulation structure in the PC Main universe

Attaching screenshot for reference

Add alias of AC_LEDGER_BALANCE as AC_LEDGER_BALANCE_TRIG and then give join between AC_LEDGER_BALANCE_TRIG and TRIG_NO. 
AC_LEDGER_BALANCE_TRIG.OBJECT_ID=AC_LEDGER_BALANCE_TRIG.OBJECT_ID AND TRIG_NO.OBJECT_ID = TRIG_NO.OBJECT_ID

After that create subfolder Triangulation Account Currency and then add three new objects under this subfolder.
Original Currency (Code) : AC_LEDGER_BALANCE_TRIG.FK_CURR
Func Currency (Code) : AC_LEDGER_BALANCE_TRIG.FK_AC_FUNC_CCY
Func 2 Currency (Code) : AC_LEDGER_BALANCE_TRIG.FK_AC_FUNC_CCY2

Problem:

Descriptions are missing for the newly added user custom objects. 

Solution:

The description needs to be added for the user custom objects.

Need to add Former Class and Former Name in the description.

Problem:

The outer joins around CNU_USER_HL are inconsistent in PC Main 25.1 SSP01 Universe.

Solution:

The existing join should be removed and the join redefined appropriately.

Problem:

Partner Universe - on refreshing structure, the selected tables were not found error

Solution:
Rename the tables PTY_Person_Derived and PTY_Bank_Derived and change it to PTY_PERSON_DERIVED and PTY_BANK_DERIVED.
Modify the SQL definitions of both the derived table to upper case by typing it manually.
Then, on refreshing structure, table not found error will be resolved and we will also not get double quotes on the derived table name.

Problem:

Log Universe - on refreshing structure, the selected tables were not found error.

Solution:
Rename the tabe REPORTING_UNIT_derived and change it to REPORTING_UNIT_DERIVED.
Modify the SQL definition of the derived table to upper case by typing it manually.
SELECT OBJECT_ID,CODE,NAME,'ROOT' TYPE FROM REPORTING_UNIT
UNION
SELECT OBJECT_ID,CODE,NAME,'LEAF' TYPE FROM RU_LEAF
Then, on refreshing structure, table not found error will be resolved and we will also not get double quotes on the derived table name.++

Solution:

Ensure the system behaves as it did previously when updating user properties, preventing the ADM0005 message from appearing during property updates.

Solution:

Prevent the ADM0005 message from appearing twice when updating user roles, ensuring a smooth and consistent user experience.

Problem:
Abend when creating new Accuracy validation rule

Solution:
For Claim Creation limit - it should not be possible to set a negative percentage value, but it should be possible to set the value to 0,00 %. A validation error in system parameters should be given if the value is less than 0 or more than 100.
If the value is 0,00% (in case it was given before validation error was implemented) it should behave as if it was empty (not given) - and validation against Claim Creation limit for Recovery Calculation order should not be performed.
When setting up a new Accuracy Rule, the system should NOT check that Claim Creation limit set in System Parameter: Accounting / Retrocession / Non-Prop Retrocession is unequal zero. Claim Creation limit is not part of Accuracy feature - and must be removed from there.

Workaround:
Set a value above zero in Claim Creation limit in System parameter Accounting / Retrocession / Non-Prop Retrocession

Root Cause:
SICSR-31780 - Claim Creation Limit in System Parameters is not clearly marked as percentage and missing validations in 25.1

Extent of Impact:
Non-Proportional Retrocession
Claim Creation Limit% You can enter a percentage in this field. When calculating Recoveries the system will include claims not yet affecting the protection if the Incurred claim exceeds the amount which corresponds to this percentage of the Excess Amount.

Problem:

Log entries are shown duplicated for changes in deduction conditions expressed as amount.

Solution:

When changing an item with Deduction Method  ‘Amount’ from one value to another, the system should not log this twice and show it twice in the Log View window of Deduction Conditions.  It should show it only once.     

Problem:

Bookings on Outward Cedent's Contract not displayed on Underwriter's Estimates if coming from assumed business. 

Solution:

When bookings are made directly on OCC, the 'Incurred Loss Business Ledger' variable for Underwriter Estimate (Pricing and Adjusted Estimate) on OCC functions properly; however, when bookings are arriving from the associated IAB, it fails to retrieve the numbers. The system will ensure that even when bookings come from IAB, all of the corresponding 'incurred loss' variables should retrieve the numbers.

Problem:
Postgres requires that views that use a table column be dropped before the column can be modified.
Currently this manifests as an error while applying DB patches if the views have not already been dropped.

Workaround:
Drop views before running the DB patches as part of the upgrade process.

Problem:

Multi Gaap Recalculation Order correctly calculates figures on Outward Cedent's Contract and Retrocessionaire Participation with Special conditions, but after refresh wrong on one item

Solution:

When we manually create and update ES - Period Estimates on OCC/ORP, the figures are displayed accurately even after refreshing the system.

Issue only occurs when the user creates or runs the Multi GAAP recalculation order, and some of the estimation items on ORP retrieve the value from the Limit & Premium Condition when a particular Premium condition is established for the business. It correctly displays the figures on the corresponding item while we are finished with the execution, however after refreshing, the relevant amount changes to the previous stored value.
It appears that newly updated figures via Order are not stored; we will ensure that the system stores the most recent value and displays it appropriately regardless of whether we refresh the system or not.

Problem:

Offset period is not working as expected when we have entered -2 Value.

Solution:

When we switch the Estimation Scop from Monthly to Quarterly view, we have found that the offset period (Booking Term & System Parameter) does not display the figures accurately. We have also noticed that this issue only arises when we set the offset period to -2; otherwise, SICS displays the figures correctly in both view modes.

Even if the user chooses any value inside the offset period, we will ensure that SICS displays the figures accurately in Both view mode. (Monthly or Quarterly).

Workaround:

Root Cause:

Extent of Impact:

Impact on Existing Data

Recovery Method for Existing Data Affected

Problem:

Issue with period estimate rules on ORP's when calculation rule is inherited from Underwriters Estimate

Solution:

Mult GAAP Period Estimate Period does not work as planned due to their selection of the Period Estimation rule, i.e., 'Calculation on Retrocessionaires', and the calculation rule that retrieves the amount from the Underwriter Estimate Tab. 

When a Period Estimation Item contains a calculation rule that is based on Underwriter estimations (Pricing/Adjusted estimations), ORP estimation items produce inaccurate results that should be generated based on the Period Estimation Item selection.
If the 'Calculation on Retrocessionaires' option is selected on the Period Estimation Item, the figures should be computed directly at the ORP level; if such culation rule is not available on the ORP, the value should be zero and no error should be reported. 
If the 'Calculation on Retrocessionaires' option is not selected on the Period Estimation Item, data must be sent from OCC to ORP based on their share percentage.

Problem:
The SICS Language Translation Assistant is not supporting versions higher than Java 8.

Solution:
The SICS Language Translation Assistant needs to be upgraded to Java 17. During this upgrade, compile-time issues related to the deprecation and removal of javax.xml.ws.http.HTTPException and javax.xml.bind.DatatypeConverter must be addressed to ensure the application functions correctly, as the current version is running on Java 8.

Problem:

Out of Memory Error When Running The Retrocession Calculation Order

Solution:

When there is a large amount of worksheets in Original Currency to be included in the Retrocession Calculation, system should not abend because of the Out of Memory Error.

Problem:

Performance issue with MG Recalc Order

Solution:

We will try to reduce the performance issue; as determined by technical experts, several duplicated SQLs are executed multiple times (more than 10 times); we will ensure that only the necessary SQLs are executed, and the undesired ones will be removed.

Problem:

When using the function 'Copy including EC Group assignment' EC Code Groups are copied but not saved. These copied EC code groups disappeared after the system refresh.

Solution:

When using the function 'Copy including EC Group assignment' copied EC Code Groups should be saved.

Problem:

Walkback is generated after changing Entry Code Category and selecting Flags tab.

Abend happened when we left the 'Sub Category' field as empty when changing the Entry Code Category.

Solution:

Abend should not happen when we left the 'Sub Category' field as empty when changing the Entry Code Category. Instead system should stop the user with a Hard stop error message something like 'Entry code Sub Category is required, but not selected'.

Problem:

SICS does not transfer the value to ORP as per their Ratio %, When User define ES condition Manually on OCC and The Period Estimation item for which the 'default' (hard-coded) value is calculated and 'Caculation on Retrocessionaire' option is not selected on the same 'Period Estimation rule'. Then, when this Estimation item is in used for that Estimation item where 'Calculation on Retrocessionaire' option is selected.

Solution:

When we have a default value in the 'MG Calculation rule' for Outward business and the respective value intends to be applied to Retrocessionaires based on their ratio, we will ensure that the figures are transferred correctly to the linked Retrocessionaires when the 'Calculation on Retrocessionaire' option is not selected. 

Currently, when we run the MG Recalculation Order, it is correctly updated; however, the error occurs with the Manual process. We will make it work from all sides, whether manually or automatically. 

Problem:

The Accumulation Control of Insurable Object lists insured object cessions with Attachment Period not covered by the Calculation as Date.

Solution:

Accumulation control of Insurable Object should not list all insured object cessions with attachment period older than the Calculation at Date. Instead, it should list only the insured object cessions with Attachment Period covering the date in the Calculation at Date field.

Aim of function

To provide a new UPR calculation option “Linear Over Extended Accounting Period – Straight Line” with the UPR factor formula :

This option will be available under the IR conditions tab at Business level and would be taken into consideration while executing UPR order (with selection of “Use Calculation option from Business Internal Premium Reserve conditions”) to calculate UPR. 

Business value for customers
This option provides a Straight line simple calculation for Linear Over Extended Accounting Period method of UPR calculation unlike traditional assumption method. The UPR figures calculated on pro-rated basis by this method, would be more appropriate as there are no assumptions/projections involved.

System Parameters Affected

N/A

Existing functionality affected

• IR Conditions of Business
• UPR Order

Aim of Function
This feature is to extend the existing base company segregation functionality to the 'exchange rate type' under the “Currency and Exchange rates” window of Reference Items and to the “Functional Currency Revaluation Order” window for FC1 & FC2. It will ensure that users will only be able to view the exchange rate types associated with the 'Exchange Rate Category' defined for the base company they are assigned to.

Business value to customers
The implementation of Base company segregation for “Exchange Rate Category” ensures that users can only access information relevant to their assigned base company. This enhancement aligns with existing base company segregation functionality and making it more advanced and efficient.

System Parameters Affected:
 
N/A
 
Existing functionality affected:
 
Reference Items - Currency and Exchange rates

Functional Currency Revaluation Order

Aim of function

To introduce a new “Balance Signature Note” option for Balances (claims and technical) on “Balance Properties” window, in addition to the existing “Note” tab, which can be opened from the worksheet closing window, business ledger or business partner ledger by selecting menu 'More balance information'.

Business value for customers

This functionality would support user activities around chasing open balances and ensuring a history of user activities on a specific balance.

System Parameters Affected

N/A

Existing functionality affected

'Balance Properties' window for Balances.

Aim of function:
A contract’s business partner ledger provides a detailed overview of balances corresponding to the business partner. This window shows balance details for all insured periods.

In addition to existing functionality, to include the insured period title in business partner ledger to show the relevant insured period title of the balances, if available

Business value for customers:
More representative title for the insured period of a contract.
Easier identification of the insured period of a contract.

System Parameters Affected
N/A

Existing functionality affected
Business partner ledger container

Aim of function

The overall aim of this function/enhancement is to improve the headline loss processing on eMessages. To be able to support the user better and ensure that the system can leverage eMessages better/more when we have Headline Losses involved.

Business value for customers

Right now, any eMessage which contains a loss movement and/or outstanding reserve related to a Proportional contract is stopped (message indicator is off for all proportional contracts). The value of this enhancement is
a) to minimize the amount of insured periods we have the message indicator off, because after all not on every proportional insured period we have to process a headline loss and
b) instead of swap to worksheet and record the Headline Loss Movements manually we would get a screen which supports the user in efficiently process the headline loss movements directly there with more control and oversight than when you do a swap to worksheet. 

System Parameters Affected
N/A

Existing functionality affected

New tab on TechAccount messages to show Headline Loss information
New spreadsheet to upload Headline Loss information to the new tab on the TechAccount
Affects the processing of TechAccount messages

Aim of function

When a Retrocessionaire is assigned through a Broker and the Brokerage Payment task is assigned to the Broker, system could default split the Brokerage by Payment Partner when running the Retrocession Calculation Order/Retrocession Account Order.  

Business value for customers

When client want to see the Brokerage as a separate balance from the business ledger of Retrocessionaire in Booking Currency/ Account Currency, they could use this function to split Brokerage according to the assigned Payment Partner when running the Retrocession Calculation Order/Retrocession Account Order.  

System Parameters Affected

Add a new system paramater 'Default Split brokerage balance'  under the Business Tab of Outward Cedent‘s Contract       

Add a new balance split option 'Split by Brokerage' on the Retrocession Calculation Group Order/Retrocession Calculation Order/Retrocession Account Group Order/Retrocession Account Order.  

Existing functionality affected

Retrocession Calculation Order​

Retrocession Account  Order​

Retrocession Calculation Group Order

Retrocession Account  Group Order

Aim of function

A non-proportional treaty outward cedent’s contract may hold share information relating to the entire contract. This may be, for example, shares that express the portion a party has in the contract. This share information is also shown on each participant and the participant’s share may again be expressed of these, e.g. Share expressed of Order.  If the shares on the outward cedent's contract change, the system now also updates the equivalent shares on the belonging participations accordingly.  

Business value for customers

Increases information accuracy.
Improves clarity.

System Parameters Affected

N/A

Existing functionality affected

Maintain Share Conditions
Maintain Limit and Premium Conditions
Create Share Conditions by Web Service
Update Share Conditions by Web Service

Aim of function

A contract’s title can indicate, for example, its overall coverage. Earlier, only one common title was available for the entire contract. If this was changed, the system automatically changes it for all insured periods. It is however useful to also have a contract title specific to one insured period. It is therefore now possible to give a title applicable only to one insured period.  This can be set up to be shown in the  title bar of the contract, as well as can be searched on to find contracts.

Business value for customers

More representative title for the insured period of a contract.
Easier identification of the insured period of a contract.

System Parameters Affected

System Parameter / Business / Business View: On Business Bar show: Business Partner
System Parameter / Business / Business View: On Business Bar show: Business Partner Name

Existing functionality affected

Copy Business
Change Life Cycle Status
Renew Business
Place Business
Update Business
Change Life Cycle Status
Find Business
View Business
Maintain System Parameters
Update Insured Period by Web Service
Create Business by Web Service

Aim of function

When viewing a contract and wanting to assign a group, the system earlier showed all existing groups in a simple list. This list did not have any further search possibilities and had a long response time if it included a large number of groups. For all types of business groups, e.g., Master Treaty Group, this listing has been replaced by full search functions, similar to the ones offered when initiated from the Groups side.

 
Business value for customers
Faster response time, allowing users to find groups without a system hang, also when the list of groups is long and using the extended base company segregation facility.

System Parameters Affected
None

Existing functionality affected
Find Business Group from Business
Find Master  Treaty Group from Business
Find Merger Group from Business
Find Offer Group from Business
Find Bouquet Calculation Group from Business
Find Bifurcation Group from Business

Aim of function

To display the missing details of tax amount item in the eMessage highlights tab.

Business value for customers

Able to view the entry code, message function, and tax application details of tax amount item from eMessage highlights tab.

System Parameters Affected

N/A

Existing functionality affected

TA message highlights tab

Aim of function
To introduce a new eMessaging rule “ValidateNetBookedAmountOnAdjustmentRule” to validate message amount with net booked adjustment amount (not by message) for adjustment messages.

Business value for customers
System now validates message amount with net booked adjustment amount.

System Parameters Affected
NA

Existing functionality affected
eMessage Processing.

Aim of function

To introduce new fields “Indicator Description” and “Last Updated by” (includes username and timestamp) on Message Indicator in the eMessaging Info under Insured Period screen.

Business value for customers

Helps the user to know the Reason and Updated by information when Message indicator is turned on/off

System Parameters Affected

N/A

Existing functionality affected

Message Indicator field on the Insured Period.

Aim of function :  

The aim of this enhancement is to strengthen security administrative access control by introducing new domain restrictions within the existing System Administrator role. These restrictions will limit the ability to assign user roles and modify role definitions, particularly those related to Security Administration use cases and the System Administrator role.

Business value for customers

Enhanced security and access control through domain restrictions within the existing security manager.

System Parameters Affected : 

None

Existing functionality affected

Security Manager User Role's

Security Manager Use Cases

Security Manager Domain Restrictions

Security Manager Users

Aim of function
General improvements to the desktop UI

• Clean up the OK/Cancel button set to remove the Help button

In Assure Re mode:

• Add a background to the window title icons to make them clearly visible
• Adopt the ISB style guideline coloring
• Clean up the desktop functions so they have less visual noise

Business value for customers
Improved visual appearance and the preview and provide feedback on the new icons.

System Parameters Affected
User Preferences

Existing functionality affected
n/a

Aim of function
Microsoft SQL Server 2014 reached End of Life status on Jul 9, 2024
DXC no longer supports SQL Server 2014 as a platform for SICS.

https://learn.microsoft.com/en-us/lifecycle/products/sql-server-2014

System Parameters Affected
None

Existing functionality affected
None