Problem:
Even though there are Non Prop OCCs protected by a Proportional OCC it is not always shown in the Protected Assumed business list (which holds a combination of both inward assumed business and Non Proporitonal OCCs). Even though the list is short for Non Prop OCCs, all of them are not always shown because the list is including both assumed business and Non Prop OCCs.

Solution:
Non Prop OCC part of the protected business must fetch all protected Non Proportional OCCs even though the list is long.

Workaround:
Check the Non Prop OCC to see if it is protected by a Prop OCC

Problem:
When i navigate with the right or left buttons on the keyboard in Base company/Business partner in mass pairing order, the cursor jumps out of the field

Solution:
When the user navigates right or left curser in Base company field and Business partner field in mass pairing order, System should work accordingly i.e., it goes right or left as per the user give command (<,>). It does not select the view business partner button.

Problem:
Base Company specific RoE not working with Tolerance Limit of Balance Pairing

Solution:
When system detects that there is a special Exchange Rate Category defined for Day Rate on the Base Company Specific Settings for the actual Base Company on the driving balance, then the system shall get the Base Currency given on the Base Company and find the actual day rate in this special Exchange Rate Category defined instead of the Daily Rate category when calculating the exchange rate to check the tolerance limit of the exchange difference. This should be applicable in all places where the system uses the tolerance limit and checks the exchange rate, especially when the Base Company of the driving balance has a special Exchange Rate category defined under base company specific setting> Exchange rate category.
If no Base Currency is defined on the Base Company, the the system shall use the Default Base Currency in the system parameter under Business, Miscellaneous.

Root Cause:
Missed implementation of SE-1781 in version 20.3

Problem:

Read only 'Technical Worksheet' Access Right does not navigate the user to the worksheet closing screen [ Client: Sompo Japan]             

Solution:

There are two problems to be solved here:
1. From the Find Accounting Worksheet window the system behaves differently for Technical Worksheet and Claim Worksheet when the user double-click on a balance. When you do not have access to Update the worksheet, then you should open the worksheet Closing window when double-click on a worksheet balance. This is correctly done for a balance on a TW but for a CW the system raise SEC0003 saying that you need Accouning Claim Worksheet with U access. Instead the system should open the closing window also for a CW (as it does for TW).
When selecting the popup menu option Change Worksheet Status, then the worksheet Closing window opens correctly for both CW and TW. Same should be the case when user double-click.
2. From the worksheet Closing window, both for TW and CW, when the user selects the option More Balance Information, then the system shall also raise SEC0003, but saying that missing access right is U and not C as it does today. When the user have the Update access right it should be possible to update the More Balance information both for TW and CW.

Workaround:

Instead for double-click on the balance on the Find Accounting Worksheet window, you can select Change Worksheet Status from the popup menu, which will take you to the worksheet closing window.
It is misleading that the system require the Create access right when trying to open the More Balance window, but if you don't have neither of the Create nor the Update access rights, then you will still be stopped, but with wrong message only.

Problem:

Manual AC Creation receives AC0502 but SICS automatically creates the duplicate AC  through the IAB booking.           

Solution:

When Accounting Classification is automatically created when doing bookings on a Technical Worksheet, the system must validate that the name of the generated AC is unique by checking the existing ACs on the actual insured period/section, also invalid and inactive ACs. If the name of the new AC to be generated is not unique, then the system shall not generate this AC, but keep the field empty on the worksheet.

In the above situations the user must manually create the correct ACs to be used in the booking.

Workaround:

To avoid the above which is also how it should have been defined (workaround) is to select all of these parameters 'Include Method Classification in Accounting Classification name', 'Include Legal Area Code in Accounting Classification name' and 'Include Reporting Unit Code(s) in Accounting Classification name'. By doing that the user will not get into the prolem.

Problem:

Access Right (DR) Violation: Worksheet Closed by Non-Granted Users 

Solution:

On the Premium and Limit condition, on the Premium Accounting window, the user can select to Reverse already booked Instalments, Adjustments or special Acceptance Premiums. By selecting this option on any of the above 3 tabs, the system shall raise a new warning message telling the user that 'This action will immediately create CLOSED worksheets. Do you want to continue?' with the option to continue the operation (YES) or to interrupt this operation (NO). If YES is selected the system will act as today, i.e. book the reversal on Closed worksheets. If NO is selected the system will interrupt the process and not reverse any worksheets.

These are the operations affected by the new function:
On the Instalments tab
Popup menu options Auto Reverse Selected Instalments and Auto Reverse All Instalments on All Sections
On the Special Acceptance Premiums tab
Popup menu option Auto Reverse Selected Special Acceptance Premiums
On the Adjustments tab
Popup menu option Auto Reverse Selected Adjustments

Problem:

Remittance Creation ID missing on message AC0227

Solution:

When a balance is highlighted on the BP ledger and user selects the popup menu option Generate Payment Request, the remittance worksheet is opened. When this remittance is Applied to the database the system presents informational message AC0227 telling the user that booking where made on a new worksheet and should also show the Remittance Id given. This is missing. Must make sure that the new Remittance Id is also shown in message AC0227, in the same way as it is when the remittance is created from a Settlement Balance Group.

Problem:

Update ‘Level of Business Indicator’ on a ‘Final’ Remittance | Possible to update for Partially Settled remittance 

Solution:

Preconditions:
System parameters :  'Update of Level of Business Indicator when Remittance is Final' and 'Update of Final Remittances Allowed through Web Services' selected.

When open a Remittance Balance in Status Final in Edit mode and the above parameters are selected, the system should allow to update the Direction and OCC fields in the Level of Business Indicator frame, but ONLY if the Remittance Balance is Unsettled. Even with the above parameters selected it shall NOT be possible to edit these fields if the Remittance Balance is Settled or Partially Settled.

Problem:

Multi GAAP calculation Rounding function not working as expected when its trigged from other estimation item. 

Solution:

When we use Rounding function in the calculation, SICS should round the value as described in the calculation rule even if Calculation rule drive from other Estimation Items. 

Problem:

Cancel and Remove Instalments on All Sections is executed without any further warning

Solution:

When the user from the Structure tab on a business selects the popup menu option Instalments with sub option Cancel and Remove Instalments on all Sections then a new confirmation message shall be raised saying that 'Are you sure you want to Cancel and Remove the Instalments on all Sections? Yes/No'
When the user replies Yes to this message the system will perform as today's existing functionality and cancel and remove all instalments on all sections.
When the user replies No to this message the process is interrupted and all instalments are kept as they are.

Same message should appear when the user select the same option from the Premium Accounting window on the Premium and Limit conditions.

Problem:

Upload of Remittance spreadsheet | Attach file option does not work

Solution:

When using the function 'Import Remittance Worksheet From spreadsheet window' and select the tick box 'Include the spreadsheet as attachment' and finally click the Import button, then the system must attach the xl spreadsheet file to ALL teh created Remittance Balances. The result of this will be that if the user inspect any of the created Remittance Balances and selects the menu option Attachments, the system will show the file used to create ALL the remittances.

Problem:

When searching remittances the search result reflects nothing in the responsible business partner field although it has been captured on the remittance

Solution:

When searching for Remittance Balances in the Find Accounting Worksheet and found remittances are displayed in the result container, the system shall also show the Responsible Partner in the actual column if the found remittance has a Respnsible Partner given in the Responsible BP field on the remittance.

Problem:

Duplicates of Default Settings on Booking Terms Maintenance

Solution:

Even if new Booking Terms have been created, assigned to a Base Company, later deleted and finally created and assigned to the Base Company again, without any refresh of the system until now, the system shall NOT create any duplicate of the <Default Settings> terms. The system shall not allow to have duplicate names of booking terms including the name <Default Settings>.

Recovery Method for Existing Data Affected

We need to delete the duplicate <Default Settings> now created in the latest DB as we are not able to edit the Default settings because of validation 'Booking Term definition already exist'.

Problem:

Pairing - Wrong FX Diff Currency Stored in DB

Solution:

Precondition:
The system parameter 'Use Base Currency On Driving Balance Base Company In Exch Diff Calculation' under Accounting>Balance Pairing is selected
The Default Base Currency of the system (found under system parameter Business >Misc) is different than the Base Company Base Currency

When balance pairing takes place between a remittance in one currency and a technical balance in another currency and both becomes fully Settled with an Exchange Difference created, and this Exchange Difference is changed to a Write Off in the same Base Company Base Currency, and the user later opens the Pairing Properties for this pairing, the Diff. Curr column must also show the Base Company Base Currency and NOT the Default Base Currency in the system.

Problem:

Description Account of Commission function

Solution:

Preconditions:
The system parameters 'Keep Description Of Account As Original' and 'Keep Description Of Account For Commission' are both selected under Accounting, Retrocession on the General page.

When running the Retrocession Calculation or Retrocession Estimation Calculation orders, the system shall keep the Description of Account from the source As Original bookings on the OCC and use this on the As Booking details on both the OCC and ORP ledger. For additional calculated Deductions on the ORP ledger, the system shall also use the Description of Account from the source premium booking.

If the above system paramters are NOT selected, then the default Regular Account will be assigned in the field Description of Account for bookings made on the Business Ledger of the Outward Cedent’s Contract/Retrocessionaire Participation.

Problem:

Security / User Roles / Domain Restriction / Accounting Section on Worksheet Details not fully working for the Auto Reverse Selected Instalments function

Solution:

Preconditions:
Domain Restriction 'Accounting Section on Worksheet Detail' is assigned to the User Role of the actual User with a restriction to stop the user from closing the worksheet on certain businesses.

When the above user is booking on the business and trying to close the worksheet manually or via the Book and Close Selected Instalments, the system correctly raise the security error message AC0302, telling the user the reason why the worksheet cannot be closed.
But when the same user selects the operation Auto Reverse Selected Instalments on the same business the system must also in this situation raise the same message AC0302 and NOT allow the user to book and close the reversal worksheet.

Problem:

Update Received External Date does not update Received Internal Date

Solution:

Preconditions:
The system parameter 'Is Received Internal Date On Worksheet In Use' under Base Company Specific Settings is selected for the actual Base Company

When a Technical or Claim Worksheet is opened and the user changes the Received External date, the system automatically shall set the Received Internal date equal the new Received External date, both if the new Received External date is before or after the existing Received Internal date.

If the user wants to set the Received Internal date to a different date than the Received External date, this must be done afterwards, but the Received Internal date must be equal or higher than the Received External date (existing and correct functionality)

Problem:

Claim ID is not included in the accumulation key of revaluation order to set the Completion Flag=Yes.

Solution:

When running the Functional Currency Revaluation order and the system shall check if the Reserve details shall be revalued or if they accumulates to zero so that they shall instead be marked as Completed, the system must also use the Claim Id linked to the details to figure out if the Reserve details accumulates to zero.
If two Loss Reserve details accumulates to zero, but one is linked to a Claim Id and one is not, then the system shall not accumulate these details and shall not set the Completed flag on them.

Problem:
Incorrect Balance Split between partners on claim worksheet bookings when Entry Code groups are used to determine split, and Claim Payment task is assigned to 'agent', and brokerage payment is assigned to 'broker' and all other is assigned to 'cedent'. The reinstatement premium booking which should have been allocated to 'Cedent' is incorrectly assigned to the 'agent' which has claim payment task.

Solution:
The system should correctly split balances according to assigned payment tasks and the entry code groups.

Problem:

Technical Worksheet Attachment abend - abend when trying to retrieve saved attachment to a worksheet or create new attachments on the Worksheet Closing window for a Closed Worksheet.

Solution:

On the Worksheet Closing window, when the Worksheet Properties is selected for a Closed Worksheet, and the user click the Attachments button, then the system shall open the Attachment window where the user can either see already attached documents or create new attachments, and not abend.

This functionality works fine when the user does this operation when a new worksheet is created and the Worksheet Closing window is opened up for changing the status of the worksheet.

Problem:

Accounting Order Find: not able to retrieve any record

Solution:

Preconditions:
In reference table 168 - Worksheet Status, the code NONE is set Inactive or Active and the code AUTH is defined as Default.

When opening the Find Accounting Order with the above settings, the field Ws Status is blank. If the user now press Find Now the system must act in the same way as if the user first selects <None>, i.e. all 3 available statuses, Open, Closed and Inactivated, shall be included in the result. 

Workaround:

Before pressing Find Now the user should select wanted worksheet status in the field Ws Status or select <None> (this is available even if it is set as Inactivated in the reference table)

Problem:

Delete parameter ' Loss Reserve Booked As Booking'

Solution:

Removed from 'Premium Basis' of OCC as requirement SE-13374 raised QHR has been canceled.

Root Cause:

Because this parameter was added by the new requirement SE-3374 proposed by Qianhai Re customers at that time. However, during the development process, Qianhai Re customer feedback no longer used this requireation-related function, so SE-3374 was cancelled. At that time, the system parameters had been added and the code had been submitted, but the relevant calculation logic had not been developed. This part of the code was not rolled back later when SE-3374 was cancelled. So we need to delete the parameter ' Loss Reserve Booked As Booking'

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:
Booking period not increased by 1 

Solution:

The booking period of the reserve details/the portfolio entry details booked into the next open insured period are increased by one compared to the ordinary bookings. If the booking period of the ordinary bookings is the last booking period of the period set also the booking year will be increased by one.

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:

Problem with a Remittance Group

Solution:

When we annul the balance, the system should correctly remove the pairing link between the balances and update the unsettled amount and settlement indicator accurately. This should be same for any Balance pairing. This will allow the annulled balances to be used for further pairing.

Problem:

Total Booked Net amount wrong for partially booked instalments - if 1st part is booked on a Closed worksheet and rest is booked on an Open worksheet then the Net amount also takes the deductions on the Open worksheets into account.

Solution:

Precondition:
One Instalment is partially booked on a Closed worksheet
The last part of the above instalment is booked on an Open worksheet

When opening the Instalments tab on the Premium and Limit Conditions on a business the system will calculate the Total Amount Booked for Gross premium and for Net premium where deductions have been subtracted, by looking at Closed worksheet on the ledger. The system shall only look at Closed worksheet also when it calculates the Net premium and NOT include deductions from the open worksheets.

Problem:

When running the reinstatement premium order, the system also validates businesses which are excluded.

Solution:

When running the order the system should only validate included businesses.

Problem:

Bug 2046899: TA/CL - Deposits - SICS 24.1 SP2 TECSNT02: AC0777 - triggered with other than cash type of security triggered (ISSUE 197)

Solution:

On the business when a Deposit Condition is defined with 'Type of Securities' other than Cash and Mixed, and on a worksheet when only Base detail (Premium/Premium Reserves, Loss/Loss Reserves) is added, then system should accept with out any error. And for Cash or Mixed 'Type of Securities', System should raise AC0395 error for missing Target details.

For the 'Type of Securities' other than Cash and Mixed, when a target detail is added along with the Base detail then system should raise AC0777 error saying worksheet '<TWXXXX> does not expect the given entry code for type of security on deposit condition'. And for Cash or Mixed 'Type of Securities', System should compare the Target amount given on the worksheet with the Computed Value and if necessary should raise AC0770 accordingly to the Threshold Values defined on the Validation Rule.

Root Cause:

This is a side-effect of the accuracy validation refactoring we did in 24.2 and ported to 24.1 SSP2

Problem:

Premium/Loss Deposits: Inconsistent Triggering of Errors

Solution:

Deposit Condition Preconditions:

Calculation Method : Pct of Premium/Loss Reserves

When we are booking on a Quarter where it is expecting to release and there is previously booked Deposit Retained amount but the Release is not booked on the current worksheet, then system shall compare the previously Retained amount in the referred account, with the AC0395 Threshold value on the rule and should trigger a hard-stop error only when the Retained amount exceeds the Threshold Limit else it should Auto-Log the error and should be independent of the Retained amount booked on the current worksheet.

And in the same case when an expected Deposit Retained is missing on the worksheet, system should calculate the Deposit Retained for the current worksheet as result of Accumulated Premium/Loss Reserves – (Total Deposits Retained of all closed WS + Total Deposits Released of all closed WS + Deposit Release on current WS). If this calculated Deposit Retained amount exceeds the Threshold Limit then system should trigger an AC0395 Hard-Stop error, else just Auto-Log the error.

Problem:

Reverse / Copy / Reverse & Replace -> Worksheet is not available for imported worksheet. Only Balance option is active from Find Accounting Worksheet Window.

Solution:

When a worksheet contains of more than 1000 details the options to Copy, Reverse, Reverse and Replace Worksheet are disabled from Find Accounting Worksheet Window.

This was an intended limitation, but we have increased the Limitation from 1000 to 10000 for a current worksheet. This was implemented for Business Ledger and Business Partner Ledger and now we need to extend the same functionality for Find Accounting Worksheet Window as well.

Problem:

Premium Adjustment Booking Confirmation

Solution:

When the user selects Auto Reverse option on a Premium Adjustment from the Adjustments screen which was already booked and closed with the Adjustment amount, then system should reverse the Premium Adjustment bookings and display the worksheet id which is created for the reversal instead of displaying worksheet id as null.

Problem:
Strange message about accounting classifications saying No New AC were Added when changing Life Cycle Status to Offer Accepted

Solution:
System Parameter 'Automatic Creation Of Accounting Classification' - ON

When we have the parameter Selected and while changing the Lifecycle status to Definite, system will try to generate the Accounting Classification on the business. While generating if there is nothing to generate, then make system to suppress the message AC0130 to appear by setting shouldDisplayMessage as false only during Lifecycle status change.

Problem:

Change of Computed Amount when changing sign of Deposit Retained amount

Solution:

When we are displaying the amount for Deposit Retained Validation, the Computed amount for the Deposit Retained should remain the same regardless if the Deposit Retained booking on current worksheet has +ve or –ve amount. As of now, the computed amount for the Deposit Retained is displaying correctly when we have the same Booking currency and the rule currency. So it should be the same when we have the different currencies as well.

Problem:

When placing an outward cedent's contract to a retrocessionaire, after the user has added one premium instalment to the contract, the system does not copy this instalment to the retrocessionaires.

Solution:

When creating a retrocessionaire after the user has added One Instalment to the OCC, the system should copy this premium instalment to the retrocessionaire. It should copy this instalment also when there were other instalments present on the OCC before adding the one by the choice One Instalment.

Problem:

It is not possible to delete a Base Company even if the reference to the system parameters has been removed.

Solution:

When having created a Base Company with only minimum information (name, country, etc.), which allows deletion, one should not be stopped from deleting the base company after having linked it to the System Parameters / Base Company Specific Setting / Classification Rules 2, and then removed this link again. The system should remove this link entirely so that one can delete the base company.

Problem:

It is not possible to remove a single treaty protection indications, even if it has not yet realized into a business. 

Solution:

Proportional Protection Assignment (PP):
Non-Proportional Protection Assignment (NP):
When having selected an unrealized Single Treaty Protection and asked for the pop up menu, the choice Remove Selected should be enabled.  When having selected this choice and replied Yes, the system should remove the unrealized Single Treaty Protection.

Problem:
When an assumed business that is part of a portfolio program has been renewed to a non-definite Life Cycle Status e.g. pending status, and then changing the status to a definite one, the links from the earlier non-definite status to the portfolio program is not correct.

Solution:
If changing the life cycle status on a renewed business in a portfolio program to a definite one, the system should establish the link to the program in the same way as it correctly does when a definite period is linked to a portfolio program for the first time, when it has earlier non-definite statuses. When then de-linking this renewed definite period from the portfolio program, the system should remove the link to this insured period completely. After the de-link the system should:
-If navigating to the earlier pending status button and selecting the PT button, the system should not show the program it was just delinked from. Instead, it should show the place to find new programs.
-If transforming the de-linked period to a Multi Year Contract, and then opening one of the sub periods, right mouse clicking on the insured period navigation, the system should not show the original insured period and it should show each period only once.

Workaround:
For businesses that have NOT yet been delinked from the Portfolio Program:
1.On the Portfolio Program, find the assumed business period to be delinked
2.From the pop-up menu, select Delete
3.DO NOW NOT LEAVE THIS WINDOW.
4.You will see the same assumed business ID and period again. This is for the previous pending status.
5.Select this period and from the pop-up menu, select Delete.

For businesses that have already been linked to the program and transformed to a Multi Year Contract, consider doing the following:
For the incorrect insured period (e.g. 01.04.2024-31.03.2027 and the periods within this), remove all periods and sub periods by navigateing to the assumed business’ Insured Period tab. From the menu button here, select Delete Insured Period. Do this for all periods belonging to this insured period. Then renew this period again. Then start step 1 above of the workaround.

Problem:

When selecting a business partner contact person for assigning to a particular business, the available list is not sorted

Solution:

Partners tab:
When having selected a business partner on a business and from the pop-up menu selecting Contacts and then Edit, the system should show the Available List sorted alphabetically.  Also, it should offer the standard Column View functionality allowing for example to search for a person.

Problem:
The system abends when selecting next before the Registration Complete page in new business wizard.

Solution:

Security Domain Restriction: ‘Business Ensure different User Approval of Registration Complete Setting'

When selecting the Next button on the page before the page with the Registration Complete flag in the New Business Wizard, the system should not abend. Instead, it should let the user into the page with the Registration Complete flag so that the user can try to select it or leave it cleared. This should be the case also when the security domain requires a different user to select Registration Complete flag.

Workaround:

Shorten the business creation process, by clicking on Finish while it's available, instead of selecting Next.

Problem:

The period fields on the Insured Period tab of a business are not aligned. For example, the Underwriting Year is not aligned and the Insured Period Duration is missing a front border.

Solution:

Insured Period tab:
The fields Insured Period From, Insured Periods To, Underwriting Year, and Insured Period Duration (if Facultative Business) should all be aligned with each other.

Problem:

The system abends when deleting a Business Partner which has assigned partner group(s)

Solution:

When deleting a Business Partner, which has an assigned partner group(s), the system should not abend.  Instead, the system should stop the user with the message message SICS0007 'there are references to it'.

Problem:

Validation error CM0292 (mismatch classification/classifications when adding business to a claim program) is too general and does not indicate which element is a mismatch - and it could relate to the classification items and/or location.

Solution:

Raise CM0292 only when either of the  classification items MCOB /COB /SCOB is not matching. Do not include validation of location in this validation. Message text as existing.

Raise new message to validate the location element. (Cannot add business xxxx. The location does not cover the Claim Program's location

Problem:

Abend when createClaim API is executed with element isClaimComplex

Solution:

The API should support the element isClaimComplex, and set indicator as per request

Root Cause:

SE-3836 (original implementation)

Problem:

No errors/log created for brokerage if no reinstatement is due, but was booked without brokerage, when brokerage condition is defined.

The log is not always created when booking reinstatement less than expected amount.

Solution:

Whenever brokerage has been defined on condition, but only reinstatement has been booked, the system should raise AC0395. This is regardless of whether the booked reinstatement is correct or not.

The accuracy log should be raised on the reinstatement detail. No computed or discrepancy.

Accuracy log should be created also when booking a reinstatement or brokerage amount less than what is computed.

The log's validation error description should be displayed for both soft stop and hard stop

Root Cause:

SE-22256 

Problem:

Claim Accuracy log is incorrect when the worksheet is expecting reinstatement bookings, but none have been made.

Solution:

The accuracy log should include the validation error if there was a either a soft stop or hard stop

Root Cause:

SE-22256

Problem:
Accounting Period on Claim Worksheet is not derived from first open account on Administration condition for non-proportional business

Solution:
When parameters 'Default from As of date' and 'Do not default as of date' are cleared, and accounts have been defined, the system should default the first open account on claim worksheet also for non-proportional business

Problem:

The arrow navigation on FGU is incorrect - it opens on the latest (correct), but requires user to use right arrows too navigate to older advisories, instead of left arrows to older, and right arrow to newer.

Solution:

When navigating on FGU advisories, the left arrows should navigate to older advisories, and the right arrows should navigate to newer. The arrows should be enabled accordingly.

This should NOT impact the dropdown date selection.

Workaround

Use the 'opposite' arrows, or view and select advisory from drop down (right click on as of date field)

Problem:

Incorrect distribution towards ACR in AAD and CIBNR in AAD when own incurred is below retention - and sequence is date of loss, and later claims (with later date of loss) has been booked. The system then allocates towards AAD despite loss being below retention.

Solution:

Nothing should be allocated towards AAD if the own incurred is below retention

Only when either paid amounts / incurred amount / incurred + cibnr amounts / Own incurred are above retention, amounts should be allocated.

Maximum allocation whichever amount exceeds the retention, or remaining aad for group (group being paid, os, cibnr, acr - and this sequence)

Problem: 

Abend when opening FGU for specific claim - division undefined - when attempting to calculate CIBNR

Solution:

Change the method used whilst comparing a value with BigDecimalZero - using CompareTo() so that the system does not abend in these situations.

Problem:

Claim can be created and linked to a Claim Program with loss location that has been excluded for one of the businesses in the Claim Program*

Solution:

The system should validate that the claim location is valid for all businesses in the Claim Program at the time of claim creation.*

Root Cause:

SE-21793

Problem:

Abend when opening FGU recording window due to system is dividing a zero value with zero.

Solution:

Change the method used whilst comparing a value with BigDecimalZero - using CompareTo() so that the system does not abend in these situations.

Problem:

The FGU screen does not default to the Claim Worksheet setting and ignores the Restriction allow the CW to be closed in the wrong period. Details attached in Word doc.

Solution:

When generating a worksheet from FGU, the system must default period as defined in booking terms applicable, also considering the booking terms rules and closing definitions.

Problem:
Layout for the Jurisdiction field on Headline loss in incorrect, also in the edit mode. It gets covered by the location field.
Solution:
Layout has to be corrected for the Jurisdiction field to be visible.

The Headline Loss: The alignment of the Jurisdiction field is not correct. The location box covers the Jurisdiction field, and the Headline Loss window has to be resized to get the Jurisdiction field visible.
Same thing happens in the edit mode, the window has to be resized to view the Jurisdiction field.

Problem:
System abends when searching through Broker value as a Role/Role2 on the Find CP window.
Solution:
System should be able to display the List of CPs when a BP with Role/Role2 as a Broker is selected.

Problem:

Claim list total reserve does not include Client IBNR Reserve

Solution:

The total amount in upper column must include all relevant reserve, and be the total of the reserve column in the lower container

Problem:

Claim Signature notes cannot be added from menu option

Solution:

It should be possible to add new note by choosing this option from menu

Workaround:

Use '+' button on menu bar above signature notes container to add new note

Problem:

System fails to raise warning CM0633 when removing a location from Claim Program in the create wizard

Solution:

The system should validate the locations against all the linked businesses. If one or more contains additional locations, CM0633 should be raised. This should happen when creating or editing the Claim Program.

Problem:

SICS only supports indexation of payments; and reserves are distributed using the nominal amounts less the indexed adjusted paid excess less the distributed paid amount. 

Solution:

Add support for indexation of reserves for 'Standard' indexation.

When calculation is defined as either 'Reserves' or 'Both' the system will trigger indexation when claim is indexed. Separate index ratios is calculated for paid and reserves. Payments are indexed using each adjustment (as per existing functionality), whereas reserves are indexed using the accumulated reserves at calculation date (FGU settlement date).

The index adjusted incurred amount is the sum of the index adjusted paid amoount

Problem:

In the following document DXC SICS eMessaging Server.pdf which is shipped with SICS 24.1 is written that eMessaging url for sending requests is /servlet/AxisServlet. This url was used with shipped eMessaging client with SICS version 4.9.2, but eMessaging client which is shipped with SICS 24.1 has in acord.client.properties the following url /wsdl/MyAcordMsgService.wsdl.

We also have problem which is correct url for some custom implemented client. From traffic analyse with SICS eMessaging client we found that this is /services/AcordMsgSvcCall. If this is correct then this also be needed to add somewhere in documentation, because now it is written that url for other tools and platforms is /servlet/AxisServlet.

Please review all documentation regarding eMessaging urls.

Solution:

I have updated the document DXC SICS eMessaging Server.pdf with the correct url i.e /wsdl/MyAcordMsgService.wsdl.

Problem:

FA message: d9be06e8-e424-41a2-9f41-cc8bdafcfefd
Settlement amount - due by sender ( + ) [TOTAL OF SEGMENT]  12,939,214.39 USD

We rejected two items: -612.91 and -1,311.71
The expectation was to have an SBG for 12,941,166.01

The SBG was now created for 11,068,119.34 USD.
Which leaves a difference of 1,873,046.67.

We checked and there was an item for that amount which shows accepted but was not included in the SBG.

Turns out, it is because in the meantime it was reversed.

Presumably because that happened after the tws was mapped to the FA, it was not validated anymore and just stayed accepted.

On revalidation of the FA should it go through all mapped TWS and check whether they are still unsettled?

Solution:
Previously if there is only 1 Accepted FAI and this fails to add a balance to create a Settlement Balance then a Problem is raised. A problem should be raised and process halted if any Accepted FAI balance fails to be added to the Settlement Balance. The FAI must be reviewed and no Settlement Balance created until all Accepted FAI balances can be successfully added.

Workaround:

Root Cause:

Extent of Impact:
Accepted FAI failing to be added to a Settlement Balance.

Impact on Existing Data

Recovery Method for Existing Data Affected

Problem:
Message applied correct newly mapped Entry Code 2003 Brokerage on the Message Highlights and Worksheet correctly booked Entry Code 2003 Brokerage – CORRECT BEHAVIOR
The message went to 'Waiting' status which cannot be overridden. Why? – UNEXPECTED BEHAVIOR

Solution:
If for grouped messages the rule ReferRelatedMessagesReferenceRule is overridden then this should not prevent a worksheet from being closed (if not all messages are available / ready to be booked.) and thus it should not go into a Waiting (for other messages in group) status.

Workaround:

Root Cause:

Extent of Impact:

Impact on Existing Data

Recovery Method for Existing Data Affected

Problem:

As per the rule ”LorsTransactionAuthorizationApplyRule”, the system should allow splitting of balance when the SICS balance is higher than the LORS transaction balance. I have tested the scenario in both 20.4 and the latest SICS version and it is not working.

Since the message balance is less than the ledger balance, the system should do the following on processing LIMRIS (LIMRISSWRISSUE_8_2023)

The Original Technical Balance is reversed (and paired against the original balance)
Two new balances are created; one equal to the authorized balance in the SICS LORS Transaction and the net amount as another new balance. Both balances remain Unsettled in SICS at this stage.
The existing link (referencing link) of the Original Technical Balance to the SICS LORS Transaction is removed and a new referencing link is created to the matching balance.
An Account Balance Group is created including the original balance, the reversed balance and the newly created balances.
Instead system is throwing an error for balance mismatch. The error should be there when the ledger balance is lower than the message balance.

Solution:
Regardless of the balances being both positive or negative if the SICS balance is larger then the balance should be split.

Workaround:

Root Cause:

Extent of Impact:

Impact on Existing Data

Recovery Method for Existing Data Affected

Problem:

CM JvClassOfBusiness is not considered in the previous mapping rule for CM Messages. As they were no test for matching Acord code set

Solution:

System should consider the CM JvClassOfBusiness for CM messages in the previous message mapping rule. 

Problem:
Intervention action SwapTo is set on message history when viewing an already closed worksheet.

Solution:
SwapTo should only be set as the intervention action on a worksheet when it is creating a worksheet or editing an open worksheet - not an already closed worksheet opened in view mode.

Workaround:

Root Cause:

Extent of Impact:

Impact on Existing Data

Recovery Method for Existing Data Affected

Problem:
We noticed that Receiver (Role) is not shown properly in ClaimMovement eMessages (SICS Client 24.1.2). Seems that version 23.1.14 doesn’t have this issue.

What we see in 'Highlights' tab is different from 'Rendered View' Tab and XML view in 'Properties' tab.

Solution:
Ensure that for CM that the Receiver Role is shown correctly as per message (rather than being the same as the Sender Role).

Workaround:

Root Cause:

Extent of Impact:
Wrong display of Receiver Role shown on GUIs.

Impact on Existing Data

Recovery Method for Existing Data Affected

Problem:   The client is facing issues while running  for BOAC006 scripts.

Solution:    

Table is  getting dupicate data when running the procedure with parameter 

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

fixing the issue will resolve redundatnt data as well as performance 

Declination Reason:

(Delete as applicable one of above)

Workaround:

Root Cause:

Extent of Impact:

Impact on Existing Data

Recovery Method for Existing Data Affected

Problem:

PC Main universe does not allow reporting on multiple brokers.

Solution:

Need to make adjustment for the joins and objects and then set the aggregate aware.

Problem:  

SICS 24.1 R&D still forget to remove sentences regarding view V_ORP_DATES on several places in chapter 16.11 in System administration guide (SICS docs).

Solution:

Need to remove the sentence regarding view V_ORP_DATES in System administration guide.

Problem:

We want to get data for settled and unsettled balances faster as compared to now.

Solution:

Add a few new tables i.e., BOAC_STL_BP_BASE, V_ACCT_PERIODS, V_BOOK_PERIODS as mentioned in the attached script.

Also add the functions and alter views V_BOAC_STL_PAIRING_BAL1 and V_BOAC_STL_PAIRING_BAL2, so that they give same calculations.

Next add the views V_BOAC_STL_BP_BASE_BUILD, V_BOOK_PERIODS_BUILD and V_ACCT_PERIODS_BUILD.

Lastly, introduce a new procedure BOAC005_PAIRING after BOAC005 as given in the attached script.

These changes in return will make the results come faster for settled and unsettled balances.

The script is given only for sql, it needs to be converted for other dbs as well and changes needs to be made.

Workaround:

Root Cause:

Extent of Impact:

Impact on Existing Data

Recovery Method for Existing Data Affected

Problem:

The Lovs for a number of objects are picking up all the data from the reference and not just the required data from reference data table.

Solution:

Restrict the SQL of the Lovs of the mentioned objects i.e., JV Entry Code, Type code, Base company name, Responsible roles, User role notes, User Case description, accounting function and accounting calculations by adding a subclass, so that we get the correct data output for that particular subclass.

Like for eg, the SQL of Lovs for JV Entry Codes will be:

SELECT
  concat(concat(REF_EDI_RINET_QUAL.CODE,' '),REF_EDI_RINET_QUAL.NAME)

FROM
  REFERENCE_DATA  REF_EDI_RINET_QUAL
INNER JOIN EDI_RINET_CODES ON
REF_EDI_RINET_QUAL.CODE=EDI_RINET_CODES.FRK_AMOUNT_QUAL and 
REF_EDI_RINET_QUAL.SUBCLASS=EDI_RINET_CODES.FSK_AMOUNT_QUAL

ORDER BY
   1

After modifying the SQL of LOVs of all the objects mentioned above it should give the right data while fetching the Lovs as well.

Problem:

Missing Base Company Full Name Object and Wrong LOVs for various Partner Full Names objects in PC Main Universe.

Solution:

Need to add the missing object

Object Name: Base Company Full Name.

Sql definition :Base_CON.FULL_NAME

The Wrong Lov's needs to be corrected .

Base Company Full Name

Cedent Full Name

Broker Full Name

Orginal cedent full Name

Former Orginal cedent full Name

Former  cedent full Name

Former Broker Full Name

Producer Full Name

Reinsurer Full Name

Tax Authority Full Name

Former Reinsurer Full Name

Orig  Reinsurer Full Name etc..  we have to correct the Lov's for the highlighted Objects. 

For reference I'm mentioning one correct Lov SQL similarly we can do for all the objects.

ObjectName:Broker Full Name

LOV:SELECT DISTINCT
  SJ_Broker_CON.FULL_NAME
FROM
  ORGANISATION_NAME  SJ_Broker_CON
right outer join PARTY PTY_Broker ON
SJ_Broker_CON.FK_ORGANISATION=PTY_Broker.OBJECT_ID AND SJ_Broker_CON.SUBCLASS=3
ORDER BY
  1    

Object Name:Cedent Full Name
LOV:SELECT DISTINCT
  SJ_Cedent_CON.FULL_NAME
FROM
  ORGANISATION_NAME  SJ_Cedent_CON  
SJ_Cedent_CON.FK_ORGANISATION=PTY_Cedent.OBJECT_ID AND SJ_Cedent_CON.SUBCLASS=3

Hi,

We have recently upgraded to SICS and BO universe v23.3.

We have noticed that Detail Amount (Main) object returns some values that look wrong.

1. Even If the Main and Original currencies are the same, some associated values vary, like in Entry Code=83
2. Original Amount =0, but Main Amount <>0, like in Entry Code=88

The query used to generate this report is attached and an example of issues is shown in image below, the query on the left is incorrect (Detail Amount (Main)), the query on the right is correct (Detail Amount (Original)).

Can you advise how this can be fixed please?

Kind regards,

Niall

Problem:

Performance issue  for adapted SQL Server BOAC StoredProcedure SUPP001 based on version 23.3.

Solution:

Need to Modify the  BOAC SUPPOO1 script for better performance.

Problem:

Need to move some objects from one folder to another and has to create a missing object in the universe.

Solution:

Need to create one missing object and  move some objects from one folder to another folder and change the object type from detail to dimension.

*Coinsurance(Y/N).

*Single Treaty Protection(Y/N)

The above two objects needs to change from detail to dimension.

*Supporting Business(Y/N).

Missing object:

 object:CLAIM SECURITY

object sql: BUSINESS.WK_CLS_SC AS CLAIM_SECURITY.

Problem:

The objects under the folder Geographical positions are giving error in report for PC Main universe Issue in SAP BI 4.3.

Solution:

Need to 'Remove object format' for all the objects under Geographical positions (Business Information>Classification>Classification Insurable objects>General>Geographic positions), so that client (using SAP 4.3) no longer gets the error message although we are not getting any error message at our end.

Workaround:

Root Cause:

Extent of Impact:

Impact on Existing Data

Recovery Method for Existing Data Affected

Hi,

We have an issue with one of our reports whereby some figures are doubled, trebled etc

For example see below figures that are trebled:

The structure of the report is as follows:

Can you advise what is the cause please?

Please treat as high priority.

Kind regards,

Niall

Problem: we are getting NULL values for the columns AC_YEAR, FRK_AC_REF_PERIOD in the view V_BOAC_FACT as data is not populating correctly into BOAC_PC_FACT Table.

Solution: Need to adjust the BOAC004 Procedure in order to get the data populated correctly into BOAC_PC_FACT Table.

Problem:

Underwriting Year and Month object defintion contain space after the Month.

Solution:

Remove the space after the month for the object definition so that it will work better.

Problem:

Getting the test failures when running the Jenkins job sics-pc-bo-test-a

Solution:

Need to be identify the issues and that should be fixed either in the SICS Code or SICS DB scripts level.

Declination Reason:

(Delete as applicable one of above)    

Workaround:

Root Cause:

Extent of Impact:

Impact on Existing Data

Recovery Method for Existing Data Affected

Problem:

Getting the test failures when running the Jenkins job sics-pc-bo-test-b

Solution:

Need to be identify the issues and that should be fixed either in the SICS Code or SICS DB scripts level.

Declination Reason:

(Delete as applicable one of above)     

Workaround:

Root Cause:

Extent of Impact:

Impact on Existing Data

Recovery Method for Existing Data Affected

Problem:

Getting the test failures when running the Jenkins job sics-lf-bo-test-a

Solution:

Need to be identify the issues and that should be fixed either in the SICS Code or SICS DB scripts level.

Declination Reason:

(Delete as applicable one of above)     

Workaround:

Root Cause:

Extent of Impact:

Impact on Existing Data

Recovery Method for Existing Data Affected

Problem:

Getting the test failures when running the Jenkins job sics-bo-lf-test-b

Solution:

Need to be identify the issues and that should be fixed either in the SICS Code or SICS DB scripts level.

Declination Reason:

(Delete as applicable one of above)      

Workaround:

Root Cause:

Extent of Impact:

Impact on Existing Data

Recovery Method for Existing Data Affected

Problem:

The join between BO_PREM_CURR_HEADER & V_REPORTING TABLE needs to be adjusted for it to work faster.

Solution:

1. Alter the view V_REPORTING_TABLE and add the part 'CONCAT(REPORTING_TABLE.FK_PC_LIM_PREM,REPORTING_TABLE.FK_PC_PREM) AS PC_DP_FK_CONDITION,' as shown in the screenshot attached below.
2. Also adjust the join between BO_PREM_CURR_HEADER & V_REPORTING_TABLE as per the screenshot attached.

Workaround:

Root Cause:

Extent of Impact:

Impact on Existing Data

Recovery Method for Existing Data Affected

Problem:

Need to change the objections definitions and make some adjustment for the view.

Solution:

Need to adjusts  object definitions and V_Reporting_Table view for the reports to perform better.

Object Name: Insured_Period_Identifier

SQL:V_REPORTING_TABLE.INSURED_PERIOD_IDENTIFIER.

Object Name: Insured Period Former ID

SQL:V_REPORTING_TABLE.INSURED_PERIOD_FORMER_ID

View Adjustment:

 case REPORTING_TABLE.FRK_LEVEL_OF_BUS when 'CDP' then INSURED_PERIOD0.I_PERIOD_FORMER_ID else REPORTING_TABLE.IP_FORMER_ID end as INSURED_PERIOD_FORMER_ID,

  INSURED_PERIOD0.BUS_INS_PER_ID AS INSURED_PERIOD_IDENTIFIER,

   JOIN INSURED_PERIOD INSURED_PERIOD0 ON INSURED_PERIOD0.OBJECT_ID=REPORTING_TABLE.FK_INS_PERIOD

Problem:

The database view V_BOAC_PC_FACT needs to be altered for better performance.

Solution:

Replace the reference of V_BOOK_PERIODS & V_ACCT_PERIODS with BOAC_BOOK_PERIODS & BOAC_ACCT_PERIODS for the view V_BOAC_PC_FACT to enhance reporting performance.

Workaround:

Root Cause:

Extent of Impact:

Impact on Existing Data

Recovery Method for Existing Data Affected

Problem:  Bank sort code objection definition is incorrect.

Solution:  Need to change the object definition for the object.

Object Name: Bank Sort code

SQL:@Aggregate_aware(BASE_COMP_Sort.IDENTIFIER,BAL_BASE_COMP_Sort.IDENTIFIER)

Problem:

Need some changes in Universe structure for PC Main Universe.

Solution:

Need to change the structure, just like in the 4.3.1 version. I am attaching the screenshot for reference.

There is an addition to this case. Looked some more at the reports using this and for reserves, getting multiple rows. The reason for this is because of aggregated reserves which we need to take away

V_RETRO_DTL_PAIR_TO_INW_DTL.IAB_ACLB_OBJECT_ID=V_BOAC_PC_FACT_INW.OBJECT_ID AND V_BOAC_PC_FACT_INW.ORIGIN = 'O'
 

Problem:

The view V_RET_GROSS_HELPER is restricting the data.

Solution:

Alter the existing view according to the script provided below.

CREATE OR ALTER VIEW V_RET_GROSS_HELPER

AS

SELECT

  BR.OBJECT_ID AS BR_ID,

  BR.RETROCEDED_VALUE,

  --COUNT(BR.FK_INSURED_PERIOD) AS SPLIT_VALUE

  CASE WHEN COUNT(BR.FK_INSURED_PERIOD) = 0 THEN 1 ELSE COUNT(BR.FK_INSURED_PERIOD) END AS SPLIT_VALUE

FROM

  BUS_RETRO BR

   LEFT OUTER JOIN BUS_STRUCT_REP BSR_OP ON BSR_OP.FK_IP_OCC = BR.FK_INSURED_PERIOD

GROUP BY

  BR.OBJECT_ID,

  BR.RETROCEDED_VALUE

;

GO

Workaround:

Root Cause:

Extent of Impact:

Impact on Existing Data

Recovery Method for Existing Data Affected

Problem: BO_DIM_DATE procedure is not populating the data in a correct way

Solution:

1.Need to create a view V_DIMDATE

2.Alter the view V_REPORTING_TABLE 

3.Need to create alias tables V_DIMDATE2 & V_DIMDATE3

4. Adjust the joins and SQL query of the objects.

Problem:

 Extracting the correct percentage when it is changed through amendment, allowing for viewing 100% booking in the correct way.

Solution:

*Need to add a new view, V_AMENDMENT_SHARE and create joins as mentioned below.

 Need to adjust the object definition for the below objects.

Current Share Pct: @Aggregate_aware(BC_SHARE0.CUR_SHARE_PCT,V_AMENDMENT_SHARE.CUR_SHARE_PCT)
Current Share Pct A: @Aggregate_aware(SUM(BC_SHARE0.CUR_SHARE_PCT),SUM(V_AMENDMENT_SHARE.CUR_SHARE_PCT))
Written Share Pct: @Aggregate_aware(BC_SHARE0.WRITTEN_SHARE,V_AMENDMENT_SHARE.WRITTEN_SHARE)
Signed Share Pct: @Aggregate_aware(BC_SHARE0.SIGNED_SHARE,V_AMENDMENT_SHARE.SIGNED_SHARE)

*Add the aggregate aware of incompatibility.

Problem:

Unable to get a stable set of rows in the source tables in SICS 24.2

Solution:

Need to adjust the view V_BOAC_PREM_CURR at line 97 The script looks like this, as mentioned below.

LEFT JOIN lpc_dep_premium ON lpc_dep_premium.fk_condition = bus_struct_rep.fk_pc_prem

But it has to be like this:

LEFT JOIN lpc_dep_premium ON lpc_dep_premium.fk_condition = bus_struct_rep.fk_pc_prem and lpc_dep_premium.fk_currency = lcp.object_id

Problem:

Need to add Missing object  under Business Information/ Additional Business Information  in PC main universe.

Solution:

Object: Split REAC Flag:

Definition:

BUSINESS

IS_SPLT_REAC_BAL_BSD_ON_PL

Problem:

Need to add the Extended Payment Date  object in PC Main Universe.

Solution:

*For creating this object in the Universe we need to create derived table and  add joins  after then add the aggregate navigation to the universe. Attaching the document for reference .extended.xlsx

Object name: Extended Payment Date 

Definition: @AGGREGATE_AWARE(EXTENDED_PAYMENT_DATE_DETAIL.EXT_PAYMENT,EXTENDED_PAYMENT_DATE_BAL.EXT_PAYMENT)                                

Derived Table:

--EXTENDED_PAYMENT_DATE_BAL
SELECT
DISTINCT
BUSINESS.IDENTIFIER AS BUS_ID,
AC_LEDGER_BALANCE.OBJECT_ID AS ACLB_OBJECT_ID,
AC_LEDGER_BALANCE.IDENTIFIER AS ACLB_IDENTIFIER,
CASE WHEN EXTENDED_PAYMENT_DATE.EXT_PAYMENT IS NULL THEN EXTENDED_PAYMENT_DATE.PAYMENT_DATE ELSE EXTENDED_PAYMENT_DATE.EXT_PAYMENT END AS EXTENDED_OR_DUE_DATE,
AC_LEDGER_BALANCE.DUE_DATE AS DUE_DATE,
EXTENDED_PAYMENT_DATE.EXT_PAYMENT AS EXT_PAYMENT,
EXTENDED_PAYMENT_DATE.INST_NR AS INST_NR
FROM
BC_INSTAL EXTENDED_PAYMENT_DATE,
AC_LEDGER_DETAIL,
AC_LEDGER_BALANCE, 
BUSINESS
WHERE
AC_LEDGER_DETAIL.FK_SRCE_INSTALMENT = EXTENDED_PAYMENT_DATE.OBJECT_ID
AND AC_LEDGER_DETAIL.FK_BALANCE=AC_LEDGER_BALANCE.OBJECT_ID
AND AC_LEDGER_BALANCE.FK_BUSINESS=BUSINESS.OBJECT_ID.

Problem:

Payment and a responsible partner address are active in the PC Main Universe.

Solution:

Need to adjust the joins for both BOAC_PP and BOAC_SECPayPart.

BOAC_DIM_PARTY.BP_OBJECT_ID=BOAC_PP_Address.FK_PARTY AND BOAC_PP_Address.IS_ACTIVE='Y'

And

BOAC_DIM_PARTY.RP_OBJECT_ID=BOAC_SecPayPart_Address.FK_PARTY AND BOAC_SecPayPart_Address.IS_ACTIVE='Y

Problem:

Estimation worksheets are being left out when reporting on them for unsettled/settled balance and detail as well as revaluation for both balance and detail.

Solution:

Need to change the definitions for the below mentioned objects.

Estimated Balances.xlsx

Settled Balance (Original) Dim
Unsettled Balance (Orig) Dim

Detail Amount Unsettled (Orig)
Detail Amount Settled (Orig)
Detail Amount Unsettled (Func)
Detail Amount Settled (Func)
Detail Amount Unsettled (Func2)
Detail Amount Settled (Func2).

After changing the object definitions, we need to add an outer join to the table on balance level.

Problem:

LOV's in the PC universe should be corrected.

Solution:

LoVs for following objects to be corrected:

1. Limit Basis 
2. Responsible Partner Reason for Alert
3. Payment Partner Reason for Alert
4. Cedent Reason for Alert
5. Reinsurer Reason for Alert

Problem:

Estimation is not part of the AC_STL_PAIRING table  we have to make a small adjustment to cater for estimate worksheets.

Solution:

Need to modify the SQL for the object Detail Settlement Indicator.

CASE WHEN V_BOAC_PC_FACT.IS_ESTIMATE='Y' THEN REF_SettlFlag2.NAME ELSE V_DETAIL_BOAC_STL_PAIR.SETTLEMENT_IND1_NAME END

Problem:

Estimation is not part of the AC_STL_PAIRING/BOAC_STL_PAIRING table, meaning we have to make a small adjustment to cater for estimate worksheets.

Solution:

Need to adjust the sql for the object settlement indicator as at.

@Aggregate_aware(CASE WHEN V_AC_LEDGER_BALANCE.IS_ESTIMATE='Y' THEN 
REF_SettlementFlag.NAME ELSE V_BOAC_STL_PAIR2.SETTLEMENT_IND1_NAME END,CASE 
WHEN V_AC_LEDGER_BALANCE.IS_ESTIMATE='Y' THEN REF_SettlementFlag.NAME 
ELSE V_BOAC_STL_PAIR_FOLLOWER.SETTLEMENT_IND1_NAME END)

Problem:

LOV's for Policy Insurer Full Name in the CEDE universe is not restricted.

Solution:

LoVs for Policy Insurer Full Name in the CEDE universe should be corrected

Problem:

Possible to edit some system parameters  although only read rights - Claim Headline Loss, Additional Classifications 4 and Exchange Rate Category. claim headline loss assignment although only read rights

Solution:

User should be stopped when attempting to edit parameter with only read rights

Problem:
When running an update condition web service, the system is only overriding inherited sub section condition. It does not also change the values that were requested to be changed.

Solution:
When running a web service to update a condition, e.g. UpdateShareCondition, for a sub section that has inherited conditions, the systems must not only override this, but also change the values as requested in the service.

Workaround:
Run the UpdateShareCondition web service twice for the sub sections. (The first time it will override and the second time, it will change the share values to the wanted values.)

Problem:

The system abends when sending chained request containing both createClaim, and createWorksheet, as the code (detail.claimToSocRelation().objectId()) being compared in the Action Date functionality for the Amounts of Details on the worksheet, has the objectid() (being referenced to) which is still null (that is not yet saved in the database). Due to this an abend is being thrown. ** 

Solution:

The code must be changed  so that the first operation (createClaim) is considered in the detail.claimToSocRelation .

Root Cause:

SE-7057

Problem:

System Admin user (User without Data segregation and assigned Use Case 'System Administration Booking Terms' ) is not able to edit the 'Period Set' for Booking Terms.

The System Admin should have full control over booking term maintenance, including the editing of the 'Period Set'.

Period Set is greyed out (not editable) also for a System Admin

Solution:

Preconditions:
The system parameters Extend Base Company Segregation and Hide Base Company are both selected.

With the two above parameters selected the Booking Term Definition Name and Period Set fields becomes disabled. But if a user, e.g. a System Administrator, has no restriction of Base Companies in the security setup, these fields should still be enabled.

Workaround:

System Administrator can uncheck the Hide base company option temporarily and edit the field Period set and name of definition keeping extend base company segregation checked.

Problem:

System Parameters . Underwriter Estimates - Estimation Items: when trying to delete an Item in the list, the system returns an abend. Walkback attached

Solution:

When we try to delete any estimation Item from Multi GAAP/Estimation Item and Underwriters/estimation Item List, system should allow to delete the same and there should not be any abend while we delete the estimation item. 

Problem:

MG Function 'Accounting Period Interval' gives an error message.

Solution:

When we use Multi GAAP function 'Accounting Period Interval' in the MG calculation rule, there should not be an error message for null value, and it should calculate the figures as described in the calculation rule. 

Problem:

When running a Reinstatement Premium Order through scheduler, the system returns a validation error that entry code must be defined for Automatic Booking as it is checking for the reinstatement entry codes for Loss Recovery calculation, instead of those defined for Reinstatement Assumed Business.

Solution:

Remove check for entry codes in  Reinstatement Premium Non-Prop AB calculation.

Problem:

Newly introduced Offset Period expressed as Month is not working for Date Value and Date function.

Solution:

When Offset Period expressed as month is in use, System should make sure Date Value and Date Function must consider the same logic as It works for Offset Period Quarter. 
Respective variable where we are consider Current Period From & To criteria, Current Period must be start from IP Start range not before the Insured Period range even if Offset has been applied. 

Problem: - 

Error message appearing when trying to create or open Period estimates or UW estimate items.

Error message 'Cannot invoke 'String.equals(Object)' because 'attributeName' is null' appearing when trying to create or open Period estimates or UW estimate items. Please refer the attachment for details of the error.

Solution : - 

MG module should not trough any Error error message while we create, Open OR Edit ES conditon on any Business (Pricing, Adjusted Estimates & Period estimates), all respective Estimation item must calculate correctly as their calculation rules and reteirve the figures accorndingly. 

Aim of function:

On the Business Partner properties, it must be possible to store new information about Letter of Credit information on a partner level, including Trust and Funds Held. This information shall be possible to view and edit manually and to report all these fields in Business Object.  

To complete the functionality we need to implement an automatic withdrawal of the Letter of Credit balance based on the Remittance amount created with the new Collateral Type field given on the remittance. This part of the enhancement specifies in detail how this automatic update of the LoC will take place. The development for this specification will probably be done and delivered in the 25.1 release.

Business value for customers

This specification will detail functionality to simplify the processing of collateralized contracts to support Schedule F reporting

System Parameters affected:

None

Existing functionality affected
View and Edit Business Partner Properties
Remittances and Balance Pairing

Aim of function:

Most SICS conditions that can be viewed in the SICS GUI are included in the business XML when a business is retrieved via a 'retrieveObject' request. This is not the case for the insurancePremiumTaxCondition. To be able to read out values from this condition, it is needed to be able to obtain the condition as part of the 'retrieveObject' response.

Business value to customers:

This enables customers to retrieve Insurance Premium Tax conditions via the `retrieveObject` API, streamlining data integration and improving operational efficiency. This provides comprehensive data access and scalability, leading to seamless system integration and enhanced business outcomes.

System Parameters affected:

None

Existing functionality affected
View and retrieve the Insurance Premium Tax Condition

Aim of Function
Introduce a new column named “External identifier” in the Business Partner Ledger. This column is already available in Business Ledger and now needs to be added to the Business Partner Ledger.

Business value to customers
Adding the “External Identifier” column in Business Partner ledger will help to maintain data consistency across different ledgers so that similar data points are available across various ledgers and will also enhance data tracking capabilities. 

System Parameters Affected

None

Existing functionality affected

View Business Partner Ledger

Aim of Function
Adding a new column in the balance container on the Find Accounting Worksheet window named ‘BookingYear/Period.’ This new column is similar to the ‘AccYear/Period’ column and added next to the ‘Settlement Indicator’ column. 

Business value to customers
In order to improve worksheet identification, the BookingYear and Booking Period shown in the Find Accounting Worksheet window, will provide user with more details about the worksheets intended for accounting needs. 

System Parameters Affected

N/A

Existing functionality affected

The Find Accounting Worksheet function

Aim of Function
Make two new Payment Types on Remittance worksheet, equal to and with same functionality as the existing Check and Check 2, named e.g. Check 3 and Check 4.

Business value to customers
To be able to distinguish between Checks received/paid in P&C and Life, two new Check types to be used in Life is needed. 

System Parameters Affected

None

Existing functionality affected

None

Aim of function
Add support for indexation of reserves for calculation method 'standard'

Business value for customers
When a contract is subject to index clause there are typically 3 different methods:

1. Standard
2. Margin
3. Severe Inflation

It is normally expected that the indexation is triggered by both payments and reserves. The index ratio to be applied for payments and reserves are often different due to differences in how they are calculated. Until now SICS has only supported Standard indexation triggered by payments. This enhancement will introduce support for indexation of reserves for calculation method standard.

The additional indexation methods will be added in future releases.

System Parameters Affected
None

Existing functionality affected
Claim FGU Handling

Aim of function
Introduce a new column for a total settlement amount in the eMessaging search screen.

Business value for customers
Customer can view the total balance of a settlement messages from the eMessaging search window. The “Settlement Balance” column will display the total amount of a settlement message from the SICS eMessaging search screen.

System Parameters Affected
N/A

Existing functionality affected
Processing of eMessages.
 

Aim of function

To Display related Settlement messages in the TechAccount related messages tab.

Business value for customers

• Settlement messages link will be made available in the TechAccount related messages tab.
• It saves time for the user instead of searching.

System Parameters Affected
N/A

Existing functionality affected
eMessage Processing

Aim of function
To Introduce new Parameters in the existing 'eMessaging Import and Validate' & 'eMessaging Import and Process' Job steps. When used, messages are automatically validated/processed based on the user selected criteria.

Business value for customers
User can now have various selection parameters to automate the validation/Processing of eMessages.

System Parameters Affected
NA

Existing functionality affected
eMessaging Batch Scheduler
eMessaging Import and Validate
eMessaging Import and Process

Aim of function

Improve the SOAP API documentation by generating it from code including the entry point description, the operation descriptions and the from versions. The generated documentation is available in SICS Docs.
Only 2 P&C operations remain to be completed in 24.4 where we will also add an XSD schema browser to view the input and output schemas for the operations.

Business value for customers

Generating documentation from code means that the documentation is automatically updated as APIs are changed or new APIs are added. Once the generated documentation has achieved parity with the existing Word documents, we will no longer ship those documents.

System Parameters Affected

None

Existing functionality affected

SICS Docs

Aim of function
We support 4 DBMS platforms with varying authentication schemes.
This feature is to ensure that all platforms support native user IDs and passwords with the modern mixed case & special character requirements equally by encoding the credentials appropriately.

Business value for customers
Elimination of technical debt and support for modern security requirements.

System Parameters Affected
None

Existing functionality affected
Login screen