Release documentation - P&C Enhancements and requests

Problem:
Incorrect BC for Worksheet Import on outward businesses

Solution:
The import functionality should work the same way as the online functionality. When a worksheet is imported to an OCC/ORP through a spreadsheet, the system should check the partners of the business. If a Base Company is defined as the Main BC, then the balance should be linked to that Base Company, and the detail should be linked to the Original Base Company as given in the spreadsheet. If no partner is defined as the Main BC, then link the first Base Company to the balance and the one given in the spreadsheet to the detail.

Problem:
Technical Worksheet created via Import TW facility is missing Payment Partner on some Balances

Solution:
When Technical Worksheets are created through the function Import Technical Worksheet from Spreadsheet, the value in the Payment Partner must ALWAYS be set. It must follow the same logic as when worksheets are created manually.

Workaround:
If you open up the View Balance Changes on the worksheet before manipulating the Balance Split Options, then you will get the Payment Partner set correctly on the Brokerage Balance.

Problem:
Incorrect Reinstatment Premium calculation for Protection Program is caused by the fact that the order is in wrong state the first time it is run, and calculation for Reinstatement for Assumed business is incorrectly triggered. This will cause incorrect reinstatement premium bookings in some cases, especially when having large recovery reversals. The incorrect bokings could be avoided by use of workaround (see below) until a fix is provided.

Solution:
While creating and running Reinstatement Premium order for Protection Program for the first time, the system must find the correct procedure for calculating reinstatement premium for OCCs linked to Protection Program. This must be done without having to do a refresh, as this order is always run for Outward Business only - not assumed business.

Workaround:
The issue can be avoided if you do the following steps when running the Reinstatement Order for Protection Program.

1. Create the new Reinstatement Premium Order for Protection Program
2. Run the Order with Open Worksheet (this might give wrong calculation)
3. Do a full refresh of the system
4. Open up the order again, and run it with Open WS / or directly on Closed WS --> the reinstatement premium is correctly booked.

Note that after refresh, when we open and run the order, it correctly determines that its purpose is to run for Reinstatement Premium for PP and gives correct results.

Problem:
Bug 1552811: TA - Deposits - SICS 23.1 SP4 TECSNT02: Premium scenario 2 - validation AC0395 expects 0 deposit retained booked (ISSUE 111)

Solution:
When the basis for the Premium Deposit Retained is zero and you book a retained detail amount of zero, then the system accept this without any validation error. But if you don't book a retained detail amount at all, then the system shall not raise the validation error message AC0395, but instead handle this situation as if the retained amount is zero. The logic must be changed so that if a retained detail is missing and the system currently raise AC0395 for this, then an additional check must be done before it is raised; a) if the computed amount for the missing detail is zero then the message AC0395 shall not be raised, but b) if the computed amount for the missing detail is NOT zero, then the message AC0395 shall still be raised.
Same logic must also be implemented for Loss Deposit.

Workaround:
When the basis for the Premium Deposit Retained is zero you can book a retained detail amount of zero, then the system accept this without any validation error. If the validation message appears because the Premium Deposit Retained is NOT booked, then just add the detail with zero amount.

Problem:
When no Main Base Company / Separate Balance is selected for a Base Company, Recovery Calculation will be booked according to inward claim base company split. When calculating reinstatement premium on that basis where there is for example recovery bookings for two base companies, the reinstatement premium is doubled - not considering the balance split correctly.

Solution:
Reinstatement Premium must follow the recovery base company split. This means that when there is more than one base company for an OCC, recoveries and also reinstatement premium will be split per base company according to the following rules: 

1. When one of the Base companies is marked as Main Base company and no Separate Balance is selected, the system will calculate recoveries and book to Main Base company only - and the Reinstatement Premium balance is booked at Main Base company as well.

2. When one of the Base companies is marked as Main Base company and Separate Balance is selected, the system calculates recoveries and is booking balances to Base company/ies with Separate Balance, and the rest will be booked to Main Base company. Reinstatement Premium is split accordingly.

3. When no Main Base Company / Separate Balance is selected, there will be a total split of recoveries based upon inward Claim details allocation to the Outward Cedent's Contract. The Base company split is applied to the recoveries, and the same split will be used for reinstatement premium balances.

In the case reported here there is no Main / Separate selected, which means that the recovery is split between involved base companies. The reinstatement split  must be according to the recovery split, creating one balance per base company. Total reinstatement premium must be split according to the recovery share of the base company.

For example; if reinstatement premium for a total loss is 10.000, and the recoveries are split BC1: 30% / BC2: 70% - the corresponding reinstatement premium will be BC1: 3.000 / BC2: 7.000.   

Problem:
Abend when calculating reinstatement premium and cover basis percent is empty

Solution:
If cover basis percentage has not been entered on limit condition, interpret this as 100% in the reinstatement premium calculation.

Workaround:
Define a percentage in cover basis field on limit condition.

Problem:
When Running Retrocession Account Order, system always checks the balances with Entry Codes of Deposits, Portfolio, Reserves in booking currency for the next insured period and include them in the Retrocession Account Calculation. However, system abends when we run this type of Retrocession Account Order.

Solution:
System should not get abend when running Retrocession Account Order if there are balances in booking currency that cover Entry Codes of Deposits, Portfolio, Reserves in the next Insured Periods and has not been booked in Account Currency.

Problem:
SICS updates Closed date and Booking Period on already closed retro worksheet.

Solution:
When a Retrocession Calculation Group order runs with Closed worksheet, we must make sure that the system ONLY close the OPEN worksheets on the individual order linked to the group order. The system shall NOT do anything with already Closed worksheets on the individual orders. So we must check the existing worksheets on the linked orders and make sure all Closed worksheets remains as they are both in respect of Booking Year/Period and Closed Date. This shall be independent if the Include Estimates on the group order is selected or not.

Problem:
Abend when running reverseTechnicalWorksheet SOAP for a particular detail.

Solution:
Make sure the reverseTechincalWorksheet SOAP works fine without abend also when a specific Detail is given in the soap in the same way as when it reversing a Worksheet and even for a specific Balance.

Problem 1:
Claim Worksheet is not automatically calculating the GT target details when a Claim Worksheet is already closed and on the new worksheet the ECs are already present. 

Solution 1:
When a Claim Worksheet is closed and on the new worksheet the target ECs are already present with previous details and Automatic Booking Flag is selected on the GT rule, then when only the trigger details are provided on the new worksheet, then system shall take the target EC's amount as NULL and automatically generate the correct amounts when user selects Apply/Change status. 

And when user enters any value(even Zero) manually on the target ECs then system should not automatically calculate the target amounts when Apply/Change Status is selected, instead it should only compare the amount entered with the computed value and throw an error if necessary. 

Problem 2:
On the TW/CW, when we manually enter the trigger EC and only one target EC with wrong amount and select Automatic booking on the worksheet, then System is only correcting the amount on the target EC added manually but does not generate the other target ECs which are missing.

Solution 2:
When on a TW/CW, user enters the trigger EC and only one/few target EC(s) manually and when user selects to calculate the GT through Automatic Booking on a worksheet, then system should calculate all the target details, that is; system should correct the amounts on the already existing target ECs on the worksheet if they are wrong and also add bookings for the missing target ECs. 

And when the Automatic Booking Flag is Selected on the GT rule, and user selects Apply/Change Status, system shall handle the two rules individually, i.e. if only one of the target details are given, but the amount is wrong, then the system shall validate the given target amount and raise an error message and for the target detail NOT entered, it shall automatically calculate and create a target detail according to the second GT rule.

Problem:
Possible to book premium Instalments from the Structure Tab on intermediary participation.

Solution:
When booking is not possible to do from the Instalment conditions on the P/L conditions, of any reason, e.g. because the instalments are inheritet from parent business, as it is for a Fac OIP, and therefore must be booked from the parent business, then the system must make the same validation and restriction if user is trying to book the same instalments from the Structure tab on the Business.

Problem:
Import TW from Column Spreadsheet - problem on Proportional ORP  Calculation order.

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

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

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

Problem:
Calendar gadget in Acct Period from/to field does not work.

Solution:
When clicking the calendar vidget in all date fields on TW, like Accounting Period From and To, make sure it works fine whichs mean that the system shall not abend and the selected date shall be set on the worksheet.

Workaround:
Enter the date in the Accounting Period From - To manually.

Problem:
Abend when trying Renewal of Proportional Fac ORP.  
Preconditions:
In the User Preferences, the radio button Scrollable is selected under Wizard Layout on the My Default Values page under Business Default Values.

Solution:
With the above setting and the user selects to Renew Fac Protection on the Proportional Protection Assignment page on an Assumed Business so that the renewal wizards opens, then the system must be able to renew the business correctly without any abend.

Workaround:
In the User Preferences, select the radio button Pages under Wizard Layout on the My Default Values page under Business Default Values.

Problem:
Validation check for broker when book EC for Brokerage on OCC.

Solution:
When booking of Brokerage on businesses, the system checks if a Broker exists or not on this business/insured period. If it does not exists the message AC0184 appears. It is just a warning and the user can overrule it ans still book the Brokerage. But this validation makes no sense on level of business OCC. Therefore, when the user is booking Brokerage on level of business OCC, both prop and non-prop, both treaty and fac, this validation shall not take place, and the message AC0184 shall not be raised.

Problem:
After the client changed the database of SICS from Sqlsever to Mysql, Sql erro occurred during the GL transfer of SICS.

Solution:
When selecting Run Now in the General Ledger Trasfer for any type of transfer, the system should be able to do the transfer, independent of the database, if it is SQL Server og MySql, without abend.

Problem:
TA Claim Signing (instead of going to status 'Waiting) goes to 'Error for rule 'CompareTechAccountTaxApplicationAmountAgainstAdjustmentAmount' with text 'Claim amount in message is different from amount on Worksheet' - INCORRECT No. 2 (Gov. Tax EC Target amount of autogenerated booking on Claim Worksheet matches the Gov. Tax amount on the TA Claim Signing Message on respective booking row. But the rule seems to consider also the separate booking row of the Reinstatement booking belonging to the TA RIP Message)
6. Claim can not be approved in external Workflow Tool (CREW) because of TA Claim Signing Message in 'Error' instead in 'Waiting'

Solution:
CompareTechAccountTaxApplicationAmountAgainstAdjustmentAmount must distinguish between bookings made by the ClaimMovement and the Reinstatement TA on the same worksheet.

Problem:
Booking Year Period Increased by 1 option for Reserves, creating multiple bookings on ORP when running REAC.

Solution:
When the System Parameter - Accounting - Retrocession - General - Booking Year and Period on Outward - 'Same as Inward' and 'Booking period for Reserves/Portfolio entries Increased by 1' are selected, when running the Retro Calculation order with option reserves & portfolio, in this case, while calculating reserves on ORP based on OCC AsBooking detail as base booking, the BYRP on OCC booking of reserve should also be incremented by one when it is booked on the ORP, to match with the ORP’s incremented BYRP. This will make two booking details with same BYRP but with opposite sign with the possibility to merge them together. Thereby showing only one booking line with incremented BYRP.

However, if the System Parameter - Accounting - Retrocession - P&C Miscellaneous - 'Aggregated by Sign in REAC' is also selected along with the above parameter, then all the 03 created booking will be shown on the details of the worksheet, however, all these three will have the same BYRP.

Problem:
The system abends on Non-Proportional protection assignment when an Outward Cedent's Contract is highlighted and selecting Remove Selected in the popup menu.

Solution:
When the user selects the popup menu option Remove Selected on the Non-Proportional protection assignment window when an OCC is selected, then the system should check if bookings exist on the OCC that are not reversed if the system parameter 'Not Allowed to Remove Protection Assignment If Its Bookings Are not Reversed' is selected. If this check is performed and the system is 'allowed' to remove the OCC, then the system will raise confirmation message BR0018 asking the user 'Do you want to remove relation to selected business?'. When answering Yes on this message, the system should remove the link to the selected OCC and remove it from the NP protection assignment window and not abend.

Workaround:
With the system parameter 'Log Business Conditions before Booking' activated on the General Interface Outbound Setup page under Outbound Interfaces in the System Administration Utility will solve this problem.

Problem:
When searching by something that will a result in finding above 2100 items, the system abends. This happens for example when searching for businesses by use of a Unique Market Identifier which is similar on 2100 businesses (or insured periods) or above.

Solution:
When searching for businesses by use of Unique Market Identifier, the generated sub query should be optimized so that it does not include the UMR Identifier several times in the request.

Workaround:
Provide more search criteria:
The user should make sure to use specific enough search criteria, like a bigger part of the UMR identifier.

Problem:
The assumed business list on anoutwardcedent'scontract only shows 50 businesses.

Solution:
When opening the protected Assumed Business list (AB) of an Outward Cedent's Contract, the system should show not only show the 50 first linked assumed businesses. It should show all.

Problem:
Facultative outward cedent's contract Section Overview/Structure tab shows wrong cover amount and aggregate limit.

Solution:
Facultative Outward Cedent's Contract structure tab should shows correct limits for our share. This should be the case also for Cover amount and Aggregate Limit.  These should show the same as the currently correctly shown 'Cover for Our Share' and 'Aggregate Limit for Our Share' on the Limits and Premium Conditions.

Problem:
The Protection Assignment overview of own retention is wrong when the business is protected by an Outward Cedent's Contract with an Unplaced Share where share is expressed in Units.

Solution:
Protection Assignment / Overview:
When an assumed business is protected with e.g. an Outward Cedents's Contract with share expressed in Units and which again is placed to an Unplaced Share, the Overview for the own retention should show correct percentages. I.e. the system must recalculate the unplaced share of the Outward Cedent's Contract to percent (not just take the number of Units and display it as if a percent).

Problem:
When changing the cedent's Main Base Company indicator on an Outward Cedent's Contract, this is not changed on belonging Intra Group Contracts.

Solution:
When creating an Intra Group Contract (Assumed) from a Retrocessionaire Participation where the Cedent has the Main Base Company Flag set to Selected, the system should NOT set the Main Base Complay flag to Selected on the database on the created Intra Group Contract (Assumed). Preferably, both the Main Base Company Flag and the Separate Balance Flag for the role Cedent shall be set to No (false) on Intra Group Contract Assumed Businesses created from a Retrocessionaire Participation. (For the following Levels of Business NO change should be made: Protection Program, Outward Cedent's Program and placements of the latter.)

Problem:
When creating a new business partner within the Create new Business wizard and then selecting to cancel the new business process, the new business partner is still partly created.

Solution:
When creating a new business partner in the Create New Business wizard and then selecting to cancel the create new business process, the new business partner must also be completely cancelled, i.e. all details entered on the new business partner must be rolled back.

Problem:
The system abends when a user selects to view Placement List on an Outward Cedent's Contract, when the user has been set up with security domain restrictions.

Solution:
Domain Restriction: Business Structure
When a user has security restrictions for viewing the Placement List, the system should not abend when opening the Placement list of an Outward Cedent's Contract. If the security was set up to stop this, the system should return a security message and if the security was set up to allow this, the system should open the Placement List.
The same applies to opening the list of protected business (AB button) of an outward cedent's contract.

Problem:
When on a treaty part of a program, e.g. Proportional Treaty Part (PT button), the user has changed something related the column Agreement Type (e.g. excluded it), and then has selected Apply and Save Settings, the system still shows the orginal setting after closing this window and then re-opened it.

Solution:
When changing the column view on a program treaty part display list, e.g. within the PT button, and saving these settings, the system should show this new view also after closing the window and re-opened it.  This should apply also to changes done to the column Agreent Type. It should always show the saved view as default until another view has been saved.

Problem:
On display lists, e.g. in Find Business, if the user changes the column view, e.g. excludes the column M. Yr.,  and saves the container settings, the desired settings are saved only temporarely. The changes are revoked as soon as the window is closed. 

Solution:
When the user preference Allow Saving of Container Changes is activate, and the user on a display list has reorganized the columns and then selected Save Settings, the system should show this view also after this window is closed and re-opened. 

Problem:
When from the Pre-renewal selecting to open an assumed business being an Intra Group Contract with Type of Business Method proportional treaty and Type of Business Covered non-proportional treaty, system abends.

Solution:
Pre-renewal
Opening an assumed business being an Intra Group Contract with Type of Business Method proportional treaty and Type of Business Covered non-proportional treaty (and therefore has non-prop limits), system should not abend but open the business - in the same way the business is opened from e.g. Find Business.

Problem:
Profit Commission condition is not fully displayed in edit mode, so to be able see Average Basis fields, window must be maximized.  

Solution:
All relevant fields should be visible in view and edit mode.
This also applies to the fields for 'Average Basis' in Profit Commission Condition. The 'Average Basis' fields should be displayed for all Types of Business in the same way as it correctly is when Type of Business is Proportional Treaty and Profit Commission Type is Percent.

Problem:
When renewing a business with renewal method non-continuous, and there is a gap between the old and the new insured period, the system returns the  warning message BS0175 about the gap multiple times.

Solution:
When renewing a business with renewal method non-continuous, and there is a gap between the old and the new insured period, system should return the  warning message BS0175 about the gap only once.

Problem:
If making several updates and changes on a Multi Year Contract, the contract becomes corrupted. 

Solution:
Working on a Multi Year Contract and making several updates/changes, the MYC should not make it corrupted and abend when opened. It should still be a MYC which can be accessed/ opened from the desktop.

Problem:
The system warns when the user enters a Cedent Signature Date that is prior to the commencement date, even if the time for such signature should be prior to the commencement date.

Solution:
When, on the Life Cycle Tab/Agreement Signature Dates Sub Tab, having entered a Cedent Signature Date, a Reinsurer Signature Date, or any other Partner Signature Date, the system should not check whether this date is prior to the insured period. Instead, the system should only validate that this is a date and if so just record the date.  

Problem:
Headline Loss - Loss Location validation does not accept States

Solution:
When validating whether claim is within HL location, the system must allow loss location defined as one or more states, if the HL is defined with country/ies. 

Problem:
Abend when retrieving Headline Loss claim list when one claim is linked to an Assumed Business with proportional protection.

Solution:
The claim list should be retrieved, and Headline Loss figures populated.

Problem:
Unable to create zero worksheet when paid is not greater than excess

Solution:
Create zero worksheet should be enabled.

1. If claim has no previous bookings: Incurred /Own incurred is greater or equal to excess AND current advisory does not result in any adjustments.. When calculating the Incurred/Own incurred the system must consider the cost/expense, and include these only when POL or None.

2. If claim has previous bookings, when current advisory does not result in any adjustments.

Workaround:
Create a manual worksheet with zero adjustments.

Problem:
The 'More' button is disabled when extracting on Headline Loss ID when one or more claims are linked to more than one business (ie multiple soc-to-claim links for same claim identifier) and default find is defined as a number which is less than the total number of soc-to-claims - and option is business identifier.

Solution:
The system must enable MORE button when the total number of soc-to-claim relations linked to the Headline Loss exceed the defined default.

Workaround:
Extract on Headline Loss in combination with selecting all base companies (i.e. move them to 'selected').

Problem:
System abends with a division by zero error when reserves are negative and inuring is calculated and costs are part of liability

Solution:
The calculation must be corrected, so that the division by zero error is not raised.

Problem:
Cannot register a negative 'Other Inuring' amounts.

Solution:
It should be possible to register 'other inuring' amounts with negative signs. Any such amounts should reduce the calculated inuring amount in step 4 of the calculation.

Root Cause:
SE-17208

Problem:
When claim is linked to business with multiple base companies, and none of them have been flagged as Main Base, the Base Company ID column in Find Claims only displays the ID for one.

Solution:
The ID column should display the ID of all the linked base companies, separated by comma.

Problem:
Client IBNR and ACR LAE not included in reserves on claim list although expenses are defined as part of liability.

Solution:
When expenses are part of liability, the reserves should also include expense reserves, acr lae, and client ibnr lae.

Problem:
Not all sub categories are listed on business claims list.

Solution:
It should be possible to select any sub category as 'other' on the business claims list.

Problem:
The option 'Add Business from Reinsurance Program' is available also for Fac Claim Programs.

Solution:
This option should not be enabled.

Problem:
Claim Accuracy errors not raised on all relevant details when both paid and incurred in AAD is exceeded.

Solution:
Accuracy error should be raised on all relevant details, and accuracy errors should be raised for both paid and incurred in AAD.

Problem:
Upload FGU worksheet title field only allows 15 character, whereas the online field accepts 30.

Solution:
The upload functionality must accept the same length as online

Workaround:
Complete title on the open worksheet.

Problem:
The FGU indicator is not set for the first claim when claim is created from an emessage.

Solution:
The system should set the FGU indicator as per Base Company Specific settings also for the first claim.

Problem:
When adding businesses to a claim program, the system behaves differently in create and edit.

Solution:
The system should raise errors and warnings as per expectations, regardless of whether the claim program is being edited, or created.

Root Cause:
SE-21793

Problem:
The Data Protection framework does not handle cessions or declarations, and results in abends when claim is linked to such.

Solution:
The Data Protection framework should handle cessions and declaration levels in the same way it handles section level.

Root Cause:
Original implementation failed to consider this.

Problem:
System fails to create open worksheet through upload in some situations.

Solution:
When import file indicates that worksheets should be created, the system should create an open worksheet with details as per FGU distribution.

Problem:
Claim Accuracy validation throws error for missing condition when liability is recorded as 'Unlimited' when validating SOC Limit.

Solution:
Unlimited must be considered as a condition, and AC0399 should not be raised.

Problem:
In our SICS 22.4.5 QA testing our users have identified that creating New Claim from EDI wizard is crashing.

Solution:
The Claim should be created without problem.

Workaround:
Manually create claim.

Extent of Impact:
Creating New Claim via EDI.

Problem:
We are facing the following challenge on the attached CM/TA messages which relate to each other.

The CM message reached status informational. The related TA message is raising a reference error that the related claim movement/adjustment is not found (which is surely the case but not of relevance for an informational CM):

Furthermore it raises the 'set zero value claim Ta's to informational' error pointing out that the CM is informational. This is all correct and the TA message is zero value – hence it should move to informational and move on.

Solution:
The test that the linked CM is 'Processed' should consider both Processed and Informational states as the same. Problem on not Processed should not occur if CM is Informational.

Problem:
Accounting Year is wrongly generated by TechAcct Message where there is unexpected decrement of year resulting in an Accounting Year prior to IP start resulting in error SYN0017 on worksheet if there are no admin conditions.

Solution:
When there is no Admin condition defined then eMessaging should start calculation per the default values of a new Admin Condition and not simply taking the duration as 1 month as this may result in starting on a prior year.

Workaround:
Add an Admin condition on the contract so that the correct values may be derived from that. Specifically have at least set the First Account As Of Date.

Root Cause:
When there is no Admin condition then the default duration for a new Admin Condition is 1 Quarter. eMessaging is setting the calculation start date using 1 month and not 1 quarter, thus depending on the IP start an incorrect year may be selected.

Problem:
When setting Claim Classification per a single match / mapped Class of Business then any Additional Classifications have all items included regardless of not having a relationship for the included class of business.

Solution:
When setting Claim Classification per a single match / mapped Class of Business then given there is a 1:1 mapping parent / child relationship for a Claim Additional Classification then those applicable items should be set on Claim Classification. Items applicable for different Class of Business should not be included. Items for different Main Class of Business and Class of Business are not included (presumption 1:1 relationships).

Problem:
The images named 'Tomcat_14.png', 'Tomcat_15.png' and 'Tomcat_17.png' are missing in the PDF version of SICS Docs document 'DXC SICS Batch Server.pdf'.

Solution:
The image is missing because the the image tag that gets generated is rendered as a code block with an image tag inside, instead of an image tag. Because of this the image does not get visualized.

Workaround:
The HTML version of the document renders the missing image in the PDF document correctly.

Problem:
SQL is different dependent on where it is generated from. Support(SUPP) XML script are not executed successfully at SICS admin.

Solution:
BOAC SUPP scripts generated from the same place as BOAC4,5 etc. and need to write a correct call procedure statement.

Problem:
During testing of 23.2 we see that when trying to include 'Pairing History Dates' from Accounting Information/Pairing/Pairing History Objects in 23.2, their values are different compared to previous version (4.8) because they now display months instead of full dates.

Is it possible to use current functionality (to pick exact dates not months) to calculate the cash flows?

Problem:
The client wants to do exchange rate conversion using latest life cycle change date, i.e., they want a customization that would enable them to convert the numbers using the latest life cycle date.

Solution:
1. Add the suggested (mentioned in the excel attachment) date option   'CONVERT (CHAR, LIFE_CYCLE_STATUS.CHANGE_DATE,112) AS CHANGE_OF_LIFE_CYCLE', into the view V_INSTALLMENTBALANCE_DATES.

2. Adjust the exchange rate SQL in the Base and Target objects in the universe as mentioned in the excel attachment below.

Problem:
In order to get Booking Year Period Month 13 and higher we need to make few changes to BOAC005 and few views. Also need to make few adjustments at Universe level for the Pairing related objects.

Solution:  
BOAC005 Script and few views mentioned needs to be adjusted in order to cope this with Booking Year Period Month 13 and higher. Few adjustments needs to be made for the objects related to Pairing to get the proper data.

Problem:
Showing two prompts for BOAC scripts Drop and Generation via SICS Admin.

Solution:
Need to adjust the two prompts in a single prompt saying it has either dropped or created the procedures successfully for the upcoming release.

Problem:
The client is facing issue regarding 'last year' object definition, join duplications and missing object 'admin note' under administration conditions in 23.4 version of Universe. 

Solution:
1. Missing object mentioned i.e., 'admin note' should be added so that the client can retrofit it into their universe as mentioned in the comments below.

2. Join correction needs to be done and single join should be taken away leaving everything else like it is now.

3. Add the object 'Last Year' into the view V_DATE_LOV (this means a change in the view for all the different database platforms). (Updated SQL for the view is attached in the comments). Also change the type to 'number' from 'character' of the object 'Last Year'.

Problem:
The client is facing parsing error in task manager universe specifically with the table TM_ADATA_OUTPUT.

Solution:
The Select statement of the table TM_ADATA_OUTPUT needs to be edited and a space should be added between SELECT and * so that the client does not face this parsing error anymore. 

The updated select statement for the table TM_ADATA_OUTPUT should be:

SELECT * FROM TM_ADATA_FIELD WHERE SUBCLASS = 2

Problem:
The list of values for 'CEDENT ID' while creating a report is fetching the details of all the third parties alongside cedent details like for e.g., broker details and reinsurer details. 

Solution:
Modify the SQL of the list of values of the 'CEDENT ID' and as well as of the 'BROKER ID' and 'REINSURER ID', so that it no longer fetches details of all the third parties.

Problem:
Missing possibility to generate BOAC007 XML script from System Admin.

Solution:
Need to update Generate Reporting Table Update script tab with BOAC007 XML file.

Problem:
Few objects and joins are missing in the partner universe.

Solution:
Need to implement the missing objects and joins into Partner Universe using Development objects.

Problem:
BOAC007 is truncating the data instead of doing delta load of data like it does in ' UPDATE RETRO PAIRING TABLE' under periodic function.

Solution:
Update the BOAC007 script and remove the part where it is truncating 'ac_retro_pairing' table so that it does delta load of data just like 'update retro pairing table' is doing now.

Problem:
Views V_BOAC_DIM_TIME & V_BALANCE_TIMELINE are causing error at report level for the objects Booking Period Stat Date & Booking Period End Date.

Solution:
Views V_BOAC_DIM_TIME & V_BALANCE_TIMELINE Needs to be adjusted to improve performance as well as to get correct data. Also the first column of V_BALANCE_TIMELINE should be object id instead of FK_BALANCE to make the view work faster in indexing point of view.

Problem:
ID NOTES object  is not present in the PC Main Universe.

Solution:
Need to create the object ID NOTES under Business Information folder in PC Main Universe.

Problem:
Some security use cases are missing name and/or description.

Solution:
Ensure that all use cases have a name and description.

Problem:
System abends when creating new Cession Limit Calculation Rule.

Solution:
System parameters/ Business/ Insurables/ Cession Limit Calculation Rules.

When creating a new or changing an existing calculation rule and adding an operator, system should not abend but add the selected operator so that a user can continue and the calculation rule can be created/updated. 

Problem:
When changing the Profit Commission Percent from one value to another, this is not always logged even though, its log Trigger value is Yes.  Likewise, the system sometimes logs this change, even though its log Trigger value is No. 

Solution:
When the Log Activities has been activated, and the user updates the profit commission percent on an existing contract, the system should log this and show it in the Log View window of the profit commission conditions if its log trigger value has been set to Yes.  If the log trigger value has been set to No, nothing should be logged for this change. 

Problem:
Support comma in section name.

Solution:
This Issue will be fixed once SE-20551 has been implemented. 

Aim of function for SE-20551 implementation:
The functions Ultimate Loss Ratio Import & UW Estimates Supporting Figures Import only support .CSV files, they should also support Excel and any other formats supported by the tabular framework.

Benefit to customers
Ease of uploading files using the Excel spreadsheets, including generating a template so user know what fields need to be entered.

Existing functionality related
Ultimate Loss Ratio Import & UW Estimates Supporting Figures Import.

Problem:
The Copy Live Desktop URL to Clipboard option the Headline Loss view gives you an incorrect URL to open a claim using the ID for the Headline Loss.

Solution:
Disable the Copy Live Desktop URL to Clipboard option from Headline Loss since Live Desktop does not have an openHeadlineLoss operation.

Problem:
Some eMessage Use Cases are missing description.

Solution:
Not all eMessage Use Cases have a description. The description should explain the function controlled and where it may be found.

Problem:
An image named 'ManageDatabaseTables.png' is missing in the PDF version of SICS Docs document 'DXC SICS Database Preparation for Oracle.pdf'.

Solution:
The image is missing because the the image tag that gets generated is rendered as a code block with an image tag inside, instead of an image tag. Because of this the image does not get visualized.

Workaround:
The HTML version of the document renders the missing image in the PDF document correctly.

Problem:
User Preference 'Do Not Display Hidden Estimation Items' should follow a logic

Solution:
We must make sure that 'Do Not Display Hidden Estimation Items' option in User Preference should be selected by default and can be unselect by the user, If a user instead wants to see all hidden items.

Problem:
In SICS login,  the user couldn't change the password, if there are special characters in the username or password. 

Solution:
When the username or password contains special characters, SICS encloses the username and password with double quotes(') before querying the database so that there is no error.

Problem:
Manual defined values on UE/MG rules with more than 9 size not working.

Solution:
Underwriter and Multi GAAP Estimates calculation rule should consider the direct manual calculation even if single entered value have more than 9 digit. UW/MG should process the correct calculation as per entered calculation.

Problem:
Underwriter's Estimation Calculation Order raise error 'Cannot invoke...'

Solution:
When Non-Prop business (Flat Premium type) having an amendment and PL (main) condition has been deleted with amendment 1. System gives a 'null pointer exception' error to calculate the Underwriter's Estimation Functions ( #FUNC getPremiumAmountForOptionCode).

We must make sure, if P/L condition has been amended and user deletes the P/L condition (Main tab) with amendment 1, system should not give the null pointer exception error and it should pick the value from Period our share amount.

Problem:
The username with special characters couldn't log into SICS.

Solution:
The special characters in the username is handled by SICS framework and the user will be able to login.

Problem:
API - bankAccount field - not being used to set the base company bank account.

Solution:
When a remittance is created via the API createRemittanceBalance, and an existing and valid bank account is given for the Base Company, then the system shall keep this bank account on this remittance in the same way as when a similar remittance is created manually. The system must follow the same logic for the validation of the bank accounts on the remittance when it is created via API as when it is created manually. This also includes the use of the relevant system parameters; Own Bank Account Mandatory for Remittances, Bank Currency same as Payment Currency for Paid Remittance and Own Bank Account Currency must match Bank Currency.

Problem:
DMSI index MASTERTREATYGROUP is not available in the index attributes.

Solution: 
System Parameter from Document Handling >> DMSI Interface for Attachments: SELECTED

Make sure to add index for MASTERTREATYGROUP when business is attached to Master Treaty Group. (same as in v4.9.3SHL1 version). When the user on a treaty, which  is linked to a master treaty group, selects the Attachment icon in the navigationbar, Mastertreatygroup should be shown on the list. 

Problem:
Renewal of linked assumed business section to Portfolio Program not working.

Solution:
When System parameter ‘Extended Renewal Functionality’ is selected, if Assumed Business linked to Portfolio Program gets renewed, the link to the program must be kept on the new period on all Sections of IAB where link was present, in case the Portfolio Program also has Insured Period which covers the IAB new Insured Period From date.

Problem:
The system  does not stops the user from setting registration to complete, even if some of the user defined  limits set up to be mandatory still are missing a value. It correctly stops if all of them are missing, but if one exists, it ignores that the rest are still missing. This error does not exist for the system-defined limits and premiums. 

Solution:
The system should stop the user from setting the registration to complete when user defined limits set up to be mandatory still are missing a value. This should apply even if some user defined limits have a value, when others are still missing.

Problem:
Cession benefit that finds more than one matching PP but fails on the OCCs within one PP is not retroceded through the valid PP when the RPO is run with multiple PP mode.

Solution:
When there is more than one PP that matches the cession benefit's classification, but only the OCCs within one of the PPs match the classification of the cession benefit, then if the cession fails being retroceded through the first PP (due to mismatch of OCC classifications) then it has to then be processed through the next PP with the same classifications, and if the OCCs within that PP match, then the cession should be retroceded through that PP.

Aim of function
Pairing ID should be set on all pairings independent if the system parameter “Balance Pairing Group in use” is selected or not. If there is an Identifier Series defined for Group Pairing (to be renamed), the system must create Identifiers both for normal pairings and for pairing groups. 

Additionally, the Pairing ID shall be shown in the FC Revaluation container open from the balance properties, when the row is created from the balance pairing.

Business value for clients
Even when the client does not want to activate and use the Balance Pairing Group they still want to use Pairing IDs. With this enhancement the Pairing Id will also be shown in the FC Revaluation table. 

System Parameters Affected
'Balance Pairing Group in use' will not affect the setting of Pairing ID in Balance Pairing and Balance Pairing Group.

Existing functionality affected
Balance Pairing
Balance Pairing Group
FC Revaluation table

Aim of function
Improve the Accuracy Validation so that minor deviations do not raise error messages by introducing more Threshold Limits for the validations.

1. Improve existing Validation for AC0399 Threshold Limit so that if the target amount is smaller or equal the threshold limit, SICS logs the situation with the same information as if the user has overruled AC0399 when the target amount is greater than the threshold limit.

2. Introduce a new threshold limit for AC0395 Threshold Limit so that the hard stop is triggered only when the target amount is missing, and booked base amount is greater than the defined threshold limit even though the business condition exist on it. SICS will record Accuracy Validation log message when the user has overruled AC0395. If target amount is missing, and the booked base amount is smaller or equal the defined threshold limit, SICS will only log and will not trigger hard stop.

3. Introduce a new threshold limit for AC0392 Threshold Limit so that the hard stop is triggered only when the base amount is missing, and the target amount is greater than the defined threshold limit even though the business condition exist on it. SICS will record Accuracy Validation log message when the user has overruled AC0392. If the base amount is missing, and the target amount is smaller or equal the defined threshold limit, SICS will only log and will not trigger hard stop.

4. Improve existing validation for AC0068 so that it is not triggered for Deduction validation if the Deduction Method on the condition is defined as “Original + Percentage” and it has no Percentage defined.

Business value for clients
Reduce number of hard stops that interrupt the booking process. Gain efficiency and promote lean processing.

System Parameters Affected
Accuracy Validation Rules

Accuracy Validation Template

Existing functionality affected
Accuracy Validation

Aim of function:
To keep the Settlement Balance Group even when a balance in the SBG is reversed and settled and therefore removed from the SBG, recalculating the SBG's balance.

Business value for clients:
This can enhance client efficiency and decrease administrative workload by eliminating the need for manual recreation of SBGs when balances are reversed and settled. Instead, the actual balance is removed from the Settlement Balance Group and recalculated automatically based on the remaining balance. This simplifies the process, improves user experience, and ultimately saves time and effort.

System Parameters Affected:
A new System Parameter named:   'Keep SBG When Balance Is Settled and Removed From SBG After Reversal' under Accounting>Balance Pairing

Existing functionality affected:

• The functionality of Reverse and Reverse and Replace balances.
• Maintain Settlement Balance Groups.

Aim of function
Implement a threshold amount for claim accuracy rules where either AC0399 or AC0395 may be raised. These errors which currently result in a hard-stop, should not be raised if booking is below defined threshold.

Business Benefit
The threshold amounts in Claim Accuracy rules reduces the number of hard-stops and promotes lean processing of claim worksheets.

System Parameters Affected
Claim - Claim Accuracy Rules

Existing functionality affected
Create Claim Worksheets
Create FGU Worksheets

Aim of function:
Display FGU Advisory creator and timestamp on each advisory.
Improve navigation between advisories by implementing date selection list, similar to the one which is present on Business Insured Period; allowing user to navigate directly to a specific Advisory.

Functionality:
FGU Administration

System Parameters:
None

Aim of function
To enable a new Modifier Rule “FAIBaseCompanyAllowLinkedReceiver” to consider message Receiver's Linked BC's as well when validating with FAI Base company.

Business value for customers
With the new Rule active, an FAI message should be possible to validate without error even if it contains different Base Company than the matching balance(s) if the involved Base Companies are linked.

System Parameters Affected
NA

Existing functionality affected

• Validate FAI Base Company Rule
• eMessage Processing

Aim of function
To bulk set the eMessages to “Examined” status by selecting the option “Mark as Examined” from the Find eMessaging window.

Business value for customers
The customer can set “”Examined” status on multiple messages simultaneously, from the eMessaging Find window.
This is applicable for all types of messages except for Acknowledgment messages. Making it possible for SICS to set the validated messages to Examined status in both the View message window and from the Find window. 

System Parameters Affected
N/A

Existing functionality affected
Processing of eMessages.

Aim of function
To extend ReferRelatedMessagesWorksheetReferenceRule to Techaccounts, so that messages of same group reference can be booked under a single Technical worksheet ID.​

For Example:​

In a group, we are receiving n no.of eMessages, when this rule ReferRelatedMessagesWorksheetReferenceRule is ON, all the TA messages that are part of group will make their bookings against a single worksheet ID.​

Business value for customers

• With this enhancement user can avoid the creation of multiple worksheets.​
• They can easily retrieve the results for data comparison.

Existing functionality affected
eMessaging Process

Aim of function
A new eMessaging rule CheckIfClaimDispositionIsInformational to check for the claim disposition on Claim Signing Account Messages.

When the rule is in force:

• This rule checks for Claim disposition on claims that are attached to non-zero payment TA claim signing messages, and if the claim disposition of the claims is Informational then this rule sets an error on eMessages.

When the rule is not in force:

• Then it work as it works now.

Business value for customers
The Claim signing accounts received against informational claims stop with an error meaning the balance of TA is not financially relevant balance. 

System Parameters Affected
N/A

Existing functionality affected
eMessage Processing

Aim of function
To Create a new Modifier rule ModifyPreventManualUpdateOfWorksheet which allows System to ignore the functionality of the parameter “Prevent Manual Update of Technical/ Claim Worksheets” when Worksheets are created through eMessaging.

Business value for customers
For specific type of message (specified by Message Type & Message Function) User wants not to apply Review/Authorization functionality so that the message/ worksheet will flow through the process.

System Parameters Affected

• Prevent Manual Update of Technical/ Claim Worksheets

Existing functionality affected
eMessage processing

Aim of function
Support of outbound messages to start receiving the Response Acknowledgements for ceded outbound CM, TA and Settlement messages from ADEPT to SICS.

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

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

Existing functionality affected
eMessaging

Aim of Function
A new security use case: Security Administration – Access Security.
The new use case will control if the user is allowed to update the Access Security.

Usage Description

• User A is assigned with both the security usecase Security Administration (E: Execute) and Security Administration - Access Security (U: Update). User A will be able to update the Access Security.

• User B is assigned with only the security usecase Security Administration (R: Read). User B will NOT be able to update the Access Security.

• User C is assigned with only the security usecase Security Administration - Access Security (U: Update). User C will NOT be able to update the Access Security because it does not have access to the Access Security Manager.

• User D is assigned with only the security usecase Security Administration (E: Execute). User D will NOT be able to update the Access Security.

• While upgrading to a new version of SICS from a version not having the new security usecase Security Administration - Access Security, all existing user roles having the usecase Security Administration (E: Execute) assigned will automatically be assigned the Security Administration - Access Security (E: Execute) security usecase.

Business value for customers
With this new feature, the client can assign dedicated users which already have assigned the Security Administration use case to only have access to update the Access Security instead of all users having the Security Administration usecase.

System Parameters Affected
None

Existing functionality affected
Security administration

Aim of function
Improve the usability of managing the assignment of business by adding a List icon next to Master Treaty Group, Merger Group and Bifurcation Group.

Business value for customers
Improved UX and usability.

System Parameters Affected
N/A

Existing functionality affected
View Merger Group from Business
View Master Treaty Group from Business
View Bifurcation Group from Business

Aim of function
Update the API descriptions in code to complete the generated documentation based on the current generation capability.
The descriptions for the Document Production and Domain Retrieval entry points to the generated documentation.

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

System Parameters Affected
None

Existing functionality affected
None