Release documentation - P&C Enhancements and requests

Problem:
Incorrect Portfolio Entry Calculation for OCC with Claim Basis “Losses Occurring” 

Solution:
When calculating 'Portfolio - Losses Occurring' through Retrocession Calculation Order, If OCC is renewed to the next Insured Period or if an OCC business-id is entered in the field 'Transfer Pt/Entry to Business', the system should make a Portfolio Entry booking to the OCC for the next Insured Period. 

Problem:
While creating a Settlement Balance Group, when we transfer balances to SBG, only the first balance from which the 'create SBG' option opted is displayed in the group but the other balances which are transferred later are not displayed in the Balance Group container, though SBG Total balance added properly. However, once the SBG saved and reopened then all the individual balances are displayed correctly.

Solution:
While creating a Settlement Balance Group, when we transfer balances to SBG, the transferred balances details also to be displayed in the Balance Group container, even before saving. Need to make sure that the balance total is being added up with the transferred balances in SBG Total balance field as it is working currently.

Problem:
Stop pairing between remittance and Informational claim worksheet (not transferred to ledger).

The system pairs the Claim Worksheet balance and Remittance Worksheet via webservice, even though the Claim worksheet has Transfer to Ledger flag as 'NO'.

Solution:
When pairing request sent through 'createBalancePairing' webservice, the pairing should not be allowed for Claims Worksheet which has 'Transfer to Ledger' flag as 'NO' (as currently working fine for online) with a failure response message like 'Claim balance not transferred to ledger. Pairing not allowed'.

Problem:
Wrong assumed business linkage by createTechncialWorksheet Web Service

Solution:
When creating Worksheet through webservice, system should correctly assign the Source Business to the balance details that has been set up the <linkInsuredPeriodToProtectedBusiness> element. For the balance details that has not been set up the <linkInsuredPeriodToProtectedBusiness> should not be assigned the Source Business.{}

Problem:
Improve Validation message description - Headline Loss Split - eMessaging.

In 'Hl Movement (adjusted)' window, When duplicate rows identified, then the error message EM0137 states - Detail Duplicated or Existed:OSLS.

When the split amount not equal to the original amount of any EC, then the error message EM0138 states - Excess Data Found:OSLS.

Solution:
The error messages should be properly displayed as follows :

When duplicate rows identified, then the error EM0137 should be triggered with message like 'Duplicate details found i.e., Entry code, HL, ORP,..etc' mentioning the exact duplication items.

When the split amount not equal to the original amount of any EC, then the error M0138 should be triggered with message like 'Split amounts not equal to the original amount of EC', mentioning relevant the Entry codes.

Problem:
Business Partner Financial Ledger: Behavior when Used with Third Party BP

Solution:
The 'Business Partner Financial Ledger' should be disabled for 'Third Parties'. However, when the Third party is transformed to a Business Partner, this option to be enabled and should work as it is working for Business Partners.

Problem:
When the exchange rate is overruled by the Functional Currency Maintenance functionality, the system leads the user to worksheet edit window if the worksheet is opened through Find: Accounting Worksheet window.

Solution:
When the exchange rate is overruled by the Functional Currency Maintenance functionality, the system should always lead the user to worksheet closing window when it is being opened through the Find: Accounting Worksheet window, as it works currently when it is being opened through the Technical Worksheet window at business level.

Problem:
Reset Functional Currencies' in the closed worksheet unexpectedly sets the functional amount to zero

Solution:
'Reset Functional Currencies' option should be disabled in the close worksheet window for worksheets with 'Closed' status regardless of whether the system parameter 'Reverse with Re-Calculation' is selected or not. However, as system works currently, this option should still be enabled for reversal worksheets with other than closed statuses, if the system parameter 'Reverse with Re-Calculation' is selected.

Problem:
Unexpected BS00478 because SICS takes allocated URB as open worksheets during Cease Accounting.

Solution:
When the user select the option to Commute a Business or its Insured Period, the system checks if there are open worksheets, or more correct it checks the value in AC_LEDGER_BALANCE.FRK_WORKSH_STATUS. If any balance in this check has the value 'NONE', 'AUTH', 'CORRECT', 'O', 'REJECT', 'R', 'SUSP' and 'UNFI', then the system correctly presents the error message BS00478 - There are open worksheets on this Business. Cease Accounting not allowed. All these worksheet statuses are correct and shall stop the user from commuting the business, but an additional condition must be checked for balances with FRK_WORKSH_STATUS = R.
FRK_WORKSH_STATUS = R is set on Unallocated Remittance balances. But not all Unallocated Remittance balances shall trigger this message.
If FRK_WORKSH_STATUS = R then the system must also check the AC_LEDGER_BALANCE.FRK_SETLMNT_IND for this/these balances. If any of the balances has the FRK_SETLMNT_IND = S then this will also trigger BS00478.
The value S in FRK_SETLMNT_IND means that the Unallocated Remittance balance is still Unallocated, i.e. has an active pairing. But when the FRK_SETLMNT_IND = U, then it means that it has been Allocated, i.e. it has been annulled from the pairing and replaced by a technical balance. In such a case BS00478 should not be triggered and cease accounting can be performed as it is working in case of Commute Business Operation. 

Problem:
Link Claim on Technical Worksheet does not transfer claim ID

Solution:
There are two columns 'Claim' & 'Claim ID' observed in the attributes of column view of TW. The column 'Claim' should be removed for both inward and outward businesses.

The 'Claim ID' column should behave in the same way as it is working currently as below :

For inward Business : If the parameter 'Allow to link claim from TW on Assumed Business' is selected in the System parameter, then the column 'Claim ID' should only be available on the TW and under the attributes of column view either. If this system parameter is not selected, it should not be available on the TW and under the attributes of column view.

For Outward Business : Regardless of this system parameter 'Allow to link claim from TW on Assumed Business', always, the column 'Claim ID' should only be available on the TW and under the attributes of column view either.

Problem:
SEC003 Message popped-up as many times as number of worksheets present when closing worksheets through Open Worksheet Mass Update order.

Solution:
When a user without the 'Create' access right for 'Accounting Balance Pairing', closes worksheets (Reversal worksheets) through Open Worksheet Mass Update order, where auto-pairing is a part of this operation, then the message SEC003 should appear only once at the beginning, even though multiple worksheets are present for closure in the order.

Problem:
Pairing ID is not displayed in Annul pairing

Solution:
When annulling any Pairing, regardless of the pairing type, the same pairing ID of the original pairing to be updated for the annulled row as well.

Problem:
API retrieveObject not extracting 'Functional Currency' related Information.

Solution:
Entrypoint : SicsWsDomainRetrievalEntryPoint
Operation : retrieveObject

When calling retrieveObject with XSD: SicsLedgerBalance and SicsLedgerDetail, the response message should include 'Functional currency' information such as functionalCurrency, functinalCurreny2, functionalAmount, functinalAmount2, fcRate1 and fcRate2.

Problem:
Walkback in production SicsLedgerDetailPreviousAmountCacheKeyHelper

When selecting option Show All Bookings - Walback is generated

[Technical description: Cannot invoke "com.csc.sics.business.domain.SicsAbstractBusinessScopeOfCover.objectId()" because the return value of "com.csc.sics.accounting.previousamount.domain.SicsLedgerDetailPreviousAmountCacheKeyHelper.section()" is null - Caused by: java.lang.reflect.InvocationTargetException]

Solution:
On Create worksheet window, when selecting option 'Show All Bookings', the system should not abend, instead system should automatically show all Reserve Entry Codes allowed for Replacement Values as it is working in the previous versions as below :

Show All Bookings: 

• Select the Show All Bookings check box in the Balance Control Information box. System displays all Entry Codes allowed for Replacement Values within the Entry Code Category Reserves. Only Entry Codes with a total amount different from zero are shown. System shows the status per Entry Code allowed for Replacement Values in the columns Previous Amount and New Amount. (Aggregation level is according to the rule defined for the Entry Code/Cession Basis)

• Enter the booking details in the column Amount and the system will automatically update the New Amount or enter the New Amount (the Current Status) and the system will calculate the difference between the New- and Previous amount and displays the difference (the adjustment) in the Amount column.

• System shows all reserve entry codes allowed for Replacement Values for the selected currency. When accessing another currency on the Technical Worksheet, system shows all reserve bookings also for this currency.

• If manual booking are entered with an Entry Code allowed for Replacement Value before the selection of Show All Bookings, this will be taken into consideration when system displays all bookings.

• When selecting one of the options ‘Change Status’, ‘UNFI’ or ‘Apply and UNFI’ from the menu on Technical Worksheet, user need to confirm if users want/not want the system to generate bookings for the Entry Codes with no Adjustments. If users select ‘Yes’, the system makes zero bookings for all booking lines displayed by the system. If you select ‘No’, the s ystem deletes all lines without any adjustments.

The following Replacement Rules are supported when selecting Show All Bookings:

• Per IP, AC
• Per IP, Occ Year, AC
• Per IP, Occ Year, Section, AC
• Per IP, Occ Year, Section, AC, HLL
• Per IP, Occ Year, Section, AC, HLL, CLM
• Per IP, Orig UW Year, AC
• Per IP, Orig UW Year, Section, AC
• Per IP, Orig UW Year, Section, AC, HLL
• Per IP, Orig UW Year, Section, AC, HLL, CLM
• Per IP, Section, AC
• Per IP, Section, AC, HLL
• Per IP, Section, AC, HLL, CLM
• Per IP, AC, HLL
• Per IP, OCC Year, AC, HLL
• Per IP, Orig UW Year, AC, HLL

(IP = Insured Period, AC = Accounting Classification, Occ Year = Occurrence Year, Orig UW Year = Original Underwriting Year, HLL = Headline Loss, CLM = Claim ID)

The Cession Basis on the Business decides what replacement rule to be used. These rules also take the Currency, Entry Code and Estimate Indicator into consideration.

If no rules can be found then the default system defined rule (Per IP, Section, AC) is used.

Note! For Entry Codes having a rule not including Section, the system displays the Target Scope of Cover (SOC) of the Accounting Classification (AC). (Target SOC is the SOC where an AC is created).

Problem:
System is stopping to add a new booking on Claim worksheet which is part of SBG.

Solution:
When the new parameter implemented in SE-10707 — 'Allow Balances in Authorized Status in Settlement Balance Group' — is set to ON, the following restrictions apply:

• Users will be prevented from updating any information on a detail (or its balance) if it belongs to a balance that is part of a Settlement Balance Group (SBG) and is linked to a worksheet with Authorized status. This restriction applies even if the detail update does not change the balance amount.
• These restrictions must be implemented on both Technical and Claim Worksheets.
  Deleting details or adding new details to balances in Authorized worksheets is also restricted if the balance is part of an SBG, regardless of whether the change affects the balance amount.
• However, adding a new currency record that belongs to a different balance (i.e., one not included in the SBG) does not affect the SBG balance amount. In this case, the validation error 'ACBP034' should not appear, and the system should allow booking the other currency in Authorized status without error.

Problem:
Abend case. Mass pairing of technical/claim

Solution:
System parameters
• Validate BYRP in Balance Pairing is selected.
• Driving Balance String for Mass Pairing of TW/CW = Reversal

When Mass Pairing of Technical/Claim balances is initiated, the system must enforce the AC0504 rule ('Validate BYRP' in Balance Pairing). Specifically, if the system encounters a balance with a Booking Year/Period (BYRP) that is not equal to default BYRP setting defined in the Balance Pairing rules for the relevant Base Company, the system must not perform the pairing for that balance.

Additionally, when the user clicks on Run to start the mass pairing of Technical/Claim balances, the system must ensure that no abend occurs. Instead, the pairing attempt for that balance needs to be skipped, allowing the mass pairing process to continue uninterrupted with the remaining eligible balances. Note that balances skipped during this process will not have their notes updated.

Problem:
Abend case when BP is blank on Mass pairing of technical/claim.

Solution:
System parameters
• Validate BYRP in Balance Pairing is selected.
• Driving Balance String for Mass Pairing of TW/CW = Reversal

When the OK button clicked on the mass pairing of Technical/Claim balances screen leaving the 'Business Partner(s)' field empty, the system must ensure that no abend occurs. Instead, it should save the details to enable for order run. Picking up the details for pairing should work as it works in versions prior to 25.2 (as it works in 25.1) also considering the changes made in between if any.

Problem:
Due Dates are not as per Payment Cedent date on Administration condition

Solution:
When Book Future Due Items on RP is selected and Keep Due Date as Original is unselected, the Due Date of each balance should be set according to the Payment Cedent date of the Accounting Period. The Accounting Period is set set by comparing the original Due Date with the Acc. As of Dates defined in the Administration Condition.

If Due Dates of the bookings <= date in the field ‘Acct as of’ of the ordered account, the bookings are allocated the Accounting Year and -Period from the ordered account.

If Due Dates of the bookings > date in the field ‘Acct as of’ of the ordered account, the date in the filed ‘Acct as of’ of the next account number is checked. If Due Date <= this date, the corresponding Accounting Year and -Period is allocated to the bookings.

We also need to clarify the corresponding User Guide for the Due Date overriding logic in the System Administration Guide for system parameter Book Future Due Items on RP .

Problem:
The AC_LEDGER_DETAIL.DTL_UNR_AMT are wrong

Solution:
When booking instalments/Adjustment, regardless of the facts whether deduction conditions present are not and whether booking happening manually or through instalment order, the column DTL_UNR_AMT in table AC_LEDGER_DETAIL should be updated with correct values even for worksheets in closed status. (currently working fine for the worksheets with open status).

Problem:
Null Pairing ID when mass pairing with SBG

Solution:
When utilizing the Mass Pairing function to create balance pairings, if a single remittance balance acts as the driving balance for multiple included balances, when those included balances belong to the same Balance Group (SBG or ABG), then the system must use the same Pairing ID for all resulting pairings that share this driving remittance balance.

Problem:
Closing ORP worksheet in SICS loaded from CSV using batch booking results in Actual balances transferred to IGC immediately. Retro Account order also transfers the same actuals to IGC.

• Create CSV file for import into SICS via Batch Booking Utility.
• Worksheet status = Open. We need to allow SICS to create Estimate balances on IGC.
• After closing worksheet in SICS, we find that SICS has created both actual balances as well as estimate balances on IGC.
• Run Retro Account order, SICS create balances in As Account as well as IGC again.
• This results in duplication on IGC.

Solution:
When uploaded PT ORP booking using 'Ceded batch booking' with open status and closed the worksheets online, the 'As booking' details should not be transferred to IGC IAB directly which should be transferred by Retrocession account order. However, for estimate booking, if system parameter 'Book Estimate to IGC' is selected, then the estimate booking should be transferred to IGC IAB directly, or else it should not be transferred.

Problem:
Wrong Functional Currency 1 and FC2 on as originals generated (reversals) when change retroceded percent to Proportional Outward Cedent's Contract protection of Non Prop OCC.

Solution:
When reduce the retroceded share of proportional protection from Non-Proportional Outward Cedent's Contract (OCC) to Proportional OCC, and only when system parameter 'Proportional Protection Assignment on Non-prop OCC in use ' is selected but 'Keep Sign from Non-prop OCC' is unselected, system should correctly calculate the Functional Currency amounts (including FC1 and FC2) of the adjustment balances in Original Currency. The sign of the Functional Currency Rate1 and Rate 2 using for calculating FC1 and FC2 Amounts should be positive.

Problem:
When investigating the issue for Mass Pairing we remarked that some Settlement Balance Groups have Legal Reporting Units while other does not have.

Example of SBGs without Legal RUs is SBG35086. All included balances have the same Legal RU but the SBG itself is without. This is stopping our Mass Pairing

How it makes that some SBGs have RUs while others does not have?

Solution:
When creating a Settlement Balance through eMessaging ensure that the Legal Reporting Unit is set from the first balance added (presuming this has a Legal Reporting Unit set)

Workaround:
Root Cause:

Extent of Impact:
Impact on Existing Data

Recovery Method for Existing Data Affected
 

Problem:
Wrong functionality: 'View They Bill Cession Order' in version 25.2

Solution:
The options View They Bill Cession Order and Create They Bill Cession Order that appear on the menu of the technical worksheets should be hidden in the P&C system.

Problem:
Business Partner Balance Mass Update - wrong number of details to be processed.

Solution:
When Mass update option selected under 'Business Partner Mass Update on Balances' form any of the tabs such as 'Expected BP update', 'Expected BP Replace', 'Responsible BP update' and 'Responsible BP Replace', only the total number of included objects to be correctly displayed in the message 'BS00267' and only the included objects to be mass updated.

Problem:
Source business FC rates not applied on Prop Retro when closing instalments manually.

Solution:
When system parameter 'Use FC Rate from Source Business' is selected, and there is protection between Non-Prop Treaty Assumed Business and Prop-Treaty Outward Cedent's Contract (OCC), system should use the same exchange rate for calculating Functional Currency 1 and Functional Currency 2 of the source Assumed Business to calculate the Functional Currencies of the balances and balance details of the OCC. It covers all possible methods of create and close the source Assumed Business worksheets, for example, create the worksheets through the Installment Condition and close the worksheet from the Technical Worksheet condition.

Problem:
Spacing is missing in the field businesspartner(s) on the mass paring order window.

Solution:
Periodic function < Mass Pairing - in Mass Pairing Order window the label 'businesspartner(s)' should be correctly placed with space as 'business partner(s)'.

Problem:
API retrieveObject not extracting 'createOrUpdateCollateral' and 'createOrUpdateCollateraldetails' related Information.

Solution:
Entrypoint - SicsWsDomainRetrievalEntryPoint
Operation - retrieveObject
XSD: SicsBusinessPartnerReference

When this XSD being used to retrieve business partner details, then the relevant collateral details as defined under the heading of 'Collateral' under the respective business partner should also be fetched and shown in the respective response.

Problem:
Premium Installment dates with Payment Date prior to the Insured Period is not allowed even though the system parameter 'Prohibit premium installment dates prior to Insured Period' is cleared.

Solution:
Premium Instalment Schedule:
When the System Parameter ‘Prohibit premium installment dates prior to Insured Period’ is cleared, the system should allow setting the Payment Date of  an Instalment to be prior to the Insured Period From Date.

Problem:
The system abends when trying to revoke a To Be Commuted status by mass update, when the included business has no administration conditions.

Solution:
When in the Business Mass Commutation having listed businesses eligible for Revoke and selecting Mass Update, the system should not abend, even if an included business has an empty Administration Conditions and a To be Commuted status. Instead, it should revoke the To be Commuted status of this business.

Workaround:
Consider doing the follwing:
-Open the outward cedent' contract of thee retrocessionaires to be revoked
-Open the administration Condition (A button)
-Select Requirements tab and here, select Payment Method 'unspecified'
-Select save
-Answer No to the question
-It should now be possible to revoke 'to be commuted' for the Retrocessionaires of this OCC.

Problem:
Placing a proportional facultative Outward Cedent's Contract gives additional premium instalments on the retrocessionaires.

Solution:
When creating a placement (retrocessionaire or intermediary placement) on a proportional facultative Outward Cedent's Contract and the Outward Cedent's Contract has calculated premium instalment(s), the placements should not get double the number of instalments. Instead, the placements should get the same number of instalment(s) as the Outward Cedent's Contract.

Problem:
Edit of Business Partner Identifier which is set as Legal Identifier via Details tab / Identifiers leads to abend when the identifier is identical to a Legal Identifier for another partner. 

Solution:
A Business Partner Identifier, which has been set up as Legal Identifier, should be possible to enter or change via the Details tab / Identifiers without any abend. If the entered identifiers is a duplicate of another, the system should give a message, unless the system parameter 'Legal ID Duplication allowed  for' has a country. If duplication is allowed for the country or it's not a duplicate, the system should accept it.
 

Problem:
When the system parameters: 'Business Partner Name' is on, the system abends when placing an intermediary to multiple retrocessionaires. 

Solution:
System parameters / Business / Business View / Parameter 'Business Partner Name' is Selected or Cleared
Outward Cedent's Contract / Placement list
Placing an intermediary to multiple retrocessionaires in one go, the system should not abend, but open the Place/Add Multiple Placements window. 

Workaround:
From the desktop, select System Administration
Select System Parameter Maintenance
Select Business
Select Business View
Set the System Parameter 'Business Partner Name' to Cleared 

Problem:
The word 'Available' appears between the two columns when editing the Business Partner Main Class of Business.

Solution:
Business Partner / Details / Main Class of Business:
When selecting edit from the pop up menu, remove the word 'Available' between the columns from the presented window.

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

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

Problem:
The SICS server abends when retrieving details for the claim worksheet using xsi claimWorksheet

Solution:
As we are retrieving the AC_WORKSHEET table information, separate xsis for different worksheet types is not required, and should be removed.  This is only valid for domainRetrieval. This must be confirmed by system/acct team.

Problem:
Incorrect error displays when booking claims adjustments

Solution:
The system should not raise null pointer errors when changing Accounting classification in the worksheet.

Problem:
The system fails to display converted limits (cover, excess, aggregate, aggregate deductible, liability) in other currency, when the currency has been recorded without a fixed rate on limit condition.

Solution:
On a multi currency contract, the claim list should display limits and claim bookings, and calculate remaining amounts, in selected curremcy.

If a rate has been defined on limit condition, this should be used.

If no rate has been defined, the latest rates should be used.

Problem:
When a new claim worksheet is created, the Accounting Period from and To Fields are empty system and system throws an error message.

'Failed to save cell value, due to: 'java.lang.NullPointerException: Cannot invoke 'com.csc.cnu.timeduration.CnuDateSpan.endingDate()' because the return value of 'com.csc.sics.accounting.domain.SicsLedgerDetail.accountingPeriod()' is null' please inform a developer'

Solution:
System must validate that all required information is entered at the time when selecting to apply/change status, as previous information may have changed.

Aim of function:
The FGU indicator should not be enabled/set when Business Administration type is LPC, despite matching Base Company and Type of Participation, as these claims on these businesses do not use FGU accounting. 

Benefit for customers:
Claim is created with correct settings

System parameters affected:
New Base Company Specific Claim Specific parameter - selecting the Additional Business Classification table and table value.

Problem:
FGU distribution towards AAD is incorrect when Client IBNR and ACR 

Solution:
The system should distribute towards AAD in this sequence Paid, Res, CIBNR, ACR, before distributing towards layer. The total distribution towards AAD must not exceed the remaining for AAD group (ie AAD Paid, or AAD Res), and the overall distribution for the claim towards AAD and layer must not exceed the cover amount.

Problem:
When clearing the FGU indicator with updateClaim API, the system fails to create an automatic FGU record setting all entries back to zero.

Solution:
The system should trigger the automatic FGU record creation, as it is happening online.

Problem:
Missing indexes on FK_NOTE

Solution:
Add indexes on FK_NOTE column

Problem:
The SOAP for Create HL Event IBNR Group doesn't have Reporting Unit fields

Solution:
The Reporting Unit fields should be supported on the SOAP for entrypoint /operation : SicsWsPcClaimEntryPoint/createHeadlineLossEventGroup.
The SOAP should allow linking of multiple RUs.
Sample SOAP without Reporting Unit field: createHeadlineLossEventGroup.txt

Problem:
Abend when saving a notifier created from worksheet closing window

Solution:
The system should save the notifier

Problem:
VAT Calculation are not performed when the System Parameter Calculate Loss VAT and Reinstatement VAT On Net (Claim Accounting) and VAT Calculation based on EC groups (Accounting> P&C Misc) are Turned Off. Also, the automatic Reinstatement Calculation yields incorrect figures.

Solution:
Reinstatement Calculations should be correctly performed even when the VAT Calculations Based on EC Group is Turned OFF.
VAT Calculations should be performed Automatically if the  Is Automatic VAT Calculation is in Use (Accounting>P&C Misc) has been selected and the Business IP has a defined VAT% and flag is checked.
VAT Calculation should be in accordance with the System Parameter: Calculate Loss VAT and Reinstatement/Reinstatement VAT on Net (Claim Accounting).

Problem:
When copying a worksheet with a single currency detail, the system highlights the correct currency, but selects the other currency.

Solution:
When copying a worksheet booked in single currency on a multi currency business (ledger currencies in more than one currency), the system should highlight/select the currency of the worksheet being copied. If copying a worksheet in multi currencies, all currencies with details should be highlighted and one selected.

Workaround:
Select the requested currency.

Problem:
Incorrect FGU bookings and distribution when booking claim on an OCC 

Solution:
 The system must distribute FGU amounts correctly, create worksheets correctly also for OCC claims.

Assumed claims FGU display figures as 'positives', worksheet as negative (sign of entry code and amount determines), and claim ledger as positive (bookings are negated).

This results in an incorrect distribution and calculation on OCC claims.

Also; do not raise warnings concerning positive reserves if level of business is OCC (that is expected).

Workaround:
Create bookings manually from claim ledger.

Problem:
SICS Server throws a validation error when creating a Claim program via API and bdx parameter is activated.

Solution:
The system must be able to create Claim program, as is possible online.

Indicator should be set on CP when set on claim condition of the source.

If no claim condition on source (and therefore no bdx) do not set bdx on CP.

All included treaties/businesses must have same bdx.

Problem:
System abends on Claim Creation wizard without Loss Date when Recovery Calculation is included and the Claim Trigger is NONE

Solution:
System should display a validation CM0199 

Problem:
Missing limits warning CM0391 is not raised when claim worksheet is created from Business worksheet icon.

Solution:
When claim worksheet is created from business worksheet icon, the warning must be raised when adding a claim which is linked to a section without limits.

Problem:
Many instances of Claim worksheets created with origin 'E-messaging' have FC1 and FC2 calculated to 0. This has cascading impact on ceded accounts and staging reconciliation issues.

Solution:
When processing ClaimMovement Replacement bookings and automatically linking a detail as reversed then ensure that the functional currency and amounts are set at that point as they would be when manually reversing a claim booking.

Root Cause:
Version 25.1 SE-32969 - eMessaging - Claims - Automatically pair reversal CM messages if they are booked

Problem:
When creating a Claim Worksheet from FGU it is not picking up the correct booking period default.

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:
On the attached reversal message, the message highlights show a different IAB than what the linked/created worksheet shows. User did link the message manually to a different IAB. However, when the reversal was processed it picked up IAB from the original booking (which is correct) but did not update the message highlights accordingly. We have now the message showing incorrect / inaccurate IAB. Furthermore the reversal user is shown as the original user but should really show the user which triggered the booking.

Solution:
When the system is reversing the booking of an original message then first check that the referenced Section / Insured Period of the reversal message matches the Section / Insured Period of the the original. If it does not then raise a problem and prevent booking.

Problem:
The Claim Manager does not appear to be set as expected when we create claims through eMessaging. Relevant System Parameter is active:

Manual case - works as expected:

Solution:
Claim Manager should be set when creating a new claim when Processing an eMessage according to the same rules as when creating a claim manually.

Problem:
Attached eMessage was mapped to a business that was set to inactive during the process while it was already mapped to it.

We could not change the mapping to the proper active business, as the system was crashing while editing.

Discarding the message did not help.

Solution:
When a TechAccount message is linked to an Insured Period with a non-Definite Life Cycle then regardless of any (Default) Processing Option do not attempt to locate a Specific Section.

Workaround:
Edit / Create eMessaging Information on the Insured Period and set the Processing Option to Process as Default / Main Section

Extent of Impact:
Insured Period set as Informational or Inactive etc.

Problem:
CM previous message referencing is recognized a message and applying the Insured Period, Section, Accounting Classification of the previous message as expected:
 
However, it does not consider/apply the claim id as per the previous message as expected. Previous message referencing should apply all referencing items as per the previous message.

In this example the message was not referenced most probably because of a mismatch of Date of Loss:

Solution:
As per TechAccount Claim Referencing from Previous Message, if section of previous and current message is set and the same and the Claim cannot be referenced by other methods then set the claim section of the current message by that of the Previous Message

Problem:
We have observed below errors for Emessage Server in our Tomcat logs. The Emessage server restarts each time after the error. Attached here is the stack trace of the logs.

Request your assistance in identifying the root cause for this error and recommendation for resolution.

Solution:
eMessaging Server should explicitly set the Reprocessing Related Messages flag based on the System Parameter setting and if this is false then there should be no Confirm Message as this is only applicable for Attended Mode or the API Server (where Confirm messages can be handled).

Workaround:
System Parameters -> eMessaging -> Processing Options
Automatically Reprocess Related Messages -> Checked

Root Cause:
Unhandled Confirm Message for Reprocessing Related Messages in eMessaging Server

Extent of Impact:
eMessaging Server when System Parameters -> eMessaging -> Processing Options
Automatically Reprocess Related Messages -> Unchecked
A message going to a final processing state which has a related message that can be reprocessed.

Problem:
Preconditions:
Insured Period lasts 15 Months
P/L Main Tab bears Annual Expected Premium amount and Expected Premium (Insured) Period
Message has Premium for whole Insured Period

Problem:
Although the Premium on the Message is the same like the Expected Premium for the (Insured) Period, the system triggers an Error that the Premium is not matching. The system considers the Annual Expected Premium instead of the Expected Premium for the whole Insured Period for the validation, which does not make sense and is wrong. - INCORRECT BEHAVIOR

Solution:
The contract premium used should be the Insured Period amount

 Problem:
'eMessaging Message Discard and Restore' use case access rights not working on eMessaging Find window.

Solution:
Since the user role doesn't have access right for accessing 'Discard/reject/restore' window, system should throw warning popup.

 Problem:
AssureRe Abend- when opening Rule set allocation Edit window and in Remove Rule option in Default Rulesets.

Solution:
System didn't get abend on SICS workstation.

Problem:
My SQL was not completely removed from installation documentation.

Answer:
References to MySQL was present in the SICS documentation, specifically in the sections related to the DXC SICS API Server, DXC SICS Batch Server, and the DXC SICS Installation Guide is removed now. No more traces of MySQL are present now.

Problem:
Image not displayed in SICS P&C User Guide - Mass pairing

Solution:
The missing images and font issues as highlighted should be corrected.

Problem:
 Performance issue for pairing and revaluation report.

Solution:
We identified that the V_BOAC_STL_PAIRING_BAL1 view contains unused columns that are slowing down performance. Removing these columns will significantly improve report execution time.

V_BOAC_STL_PAIRING_BAL1_MODIFIED_FINAL.sql
 
 

Problem:                                                                                                                                                                   
Performance issue while selecting all year performance is still bad, it needs around 40-45 minutes (in some older version this worked faster). For one year time is around 20-25 minutes (which is not the best).

Solution:                                                                                                                                                                             
Needs to alter SQL for the view V_UW_EST & V_UW_EST_LATEST with the latest attached script. So that it will fix the Underwriter's estimate objects the performance problem.

Problem:                                                                                                                                                                         
The BOAC004_REVALUATION procedure is having performance issue as it is included all balances, causing a performance issue.

Solution: 

• The two BO views V_BOAC_FC_REVAL_BAL_BYRP and V_BOAC_FC_REVAL_DTL_BYRP needs to be adjusted.
• The new procedure BOAC008_REVAL needs to be created which will replace the BOAC004_REVALUATION Procedure.

Problem:
Problems with Detail Liquid Ageing objects in SICS 25.1, because numbers are wrong in some cases.

Solution:
Needs to alter SQL in view V_DTL_LIQUID_UNSETTLED in SICS - java

V_DTL_LIQUID_UNSETTLED1.sql

Problem:
Additional objects have to be included in the default PC Main Universe.

Solution:
We need to create alias tables, derived tables and update the object definitions for two objects: MAX Incurred and Max Incurred (Base). Additionally, we need to create 49 new objects in the default universe.

The attached document contains a complete list of objects, alias tables, derived tables and  a sample universe for reference.

Achmea Customized.xlsx

Problem:
Select SQL for the Objects Description Of Account & Accounting Classification Name are not defined correctly.

Solution:
1.Need to alter the view V_BOAC_PC_FACT to add new columns ACC_CLASSIFIC_NAME,DESCRIPTION_OF_ACCOUNT&DESCRIPTION_OF_ACCOUNT_CODE  

2.Adjust the SELECT SQL of the objects Description of Account & Accounting Classification Name in PC Main Universe on top of newly added columns.

Object: Description of Account

Adjusted SQL: @Aggregate_aware(V_BOAC_PC_FACT.DESCRIPTION_OF_ACCOUNT,REF_AC_PR_CL.NAME)

Object: Accounting Classification Name

SQL: V_BOAC_PC_FACT.ACC_CLASSIFIC_NAME

Problem:
 Polish Re are testing the 25.2 SISC and BO. They noticed that not everything is working as expected in BO in terms of pairing.They checked a remittance that was paired with technical worksheet and then unpaired.In the current (adjusted) version 23.2 they can see both pared and unpaired rows. However, in version 25.2 they can see only the unpaired ones. We saw something similar during the last upgrade to version 23.2 and if I remember correctly, it was linked with the annulment date on the actual annulment record while the other date was NULL.

Solution:
'REF_BookingPer ' table was not joined properly. Need to adjust the join like below in PC Main universe.

REF_BookingPer.CODE=V_BOAC_STL_PAIR_FOLLOWER.FRK_BOOKING_PERIOD AND REF_BookingPer.SUBCLASS=10

Problem:
Missing values for Minimum and Deposit Premiums in universe even though exist in SICS

Solution:

• Need to alter the views V_BOAC_PREM, V_BOAC_PREM_CURR, V_BOAC_PREM_CURR_MAIN

SICSR-33397- CREATE OR ALTER VIEW V_BOAC_PREM-V_BOAC_PREM_CURR-V_BOAC_PREM_CURR_MAIN.sql

• Need do structure changes in PC Main universe by altering joins between the Premium tables.

Problem:
Missing Premium on Multi Year contracts in BO Reports.

Solution:
The necessary changes must be applied to the views V_BOAC_PREM, V_BOAC_PREM_CURR, and V_BOAC_PREM_CURR_MAIN.
LATEST - ALTER SCRIPTs for TABLES, VIEWS and PROCEDURE BOBU001.txt

The required changes need to be made to the joins between the tables BO_PREM_CURR_HEADER, TOT_PREMIUM_CURR_ORIG, and SJ_LPC_PRM_TOTPREM_ORIG.

Problem:                                                                                                                                                                            
In 25.2 BO universe the 'Commission Pct' object from Business Information/Deduction Conditions/Commission Deductions is in Dimension it should be changed to measure.

Solution:
The objects Commission Pct & Commission Amount from Commission Deductions folder and Brokerage Pct & Brokerage Amount from Brokerage Deductions folder and Other Pct & Other Amount from Other Deductions folder is also in dimension. So, these objects should be changed from dimension to measure.

Problem:
Detail Amount Unsettled (Base) not working for estimates.

Solution:
Modify the existing SQL definition of the objects Detail Amount Unsettled (Base) & Detail Amount Settled (Base) as per the definitions provided below.

Detail Amount Unsettled (Base)

SUM(CASE WHEN V_BOAC_PC_FACT.IS_ESTIMATE = 'Y' THEN V_BOAC_PC_FACT.AMOUNT WHEN V_BOAC_PC_FACT.IS_LIQUID = 'N' THEN V_BOAC_PC_FACT.AMOUNT ELSE V_DETAIL_BOAC_STL_PAIR.UNSETTLED_AMT1 * V_BOAC_PC_FACT.AMOUNT / CASE WHEN V_DETAIL_BALANCE.LEDGER_BAL_ORG_AMT = 0.00 THEN 1 ELSE V_DETAIL_BALANCE.LEDGER_BAL_ORG_AMT END END  * @Select(Entry Codes/Base))

Detail Amount Settled (Base)

SUM(CASE WHEN V_BOAC_PC_FACT.IS_ESTIMATE = 'Y' THEN 0.00 WHEN V_BOAC_PC_FACT.IS_LIQUID = 'N' THEN 0.00 ELSE ( V_DETAIL_BALANCE.LEDGER_BAL_ORG_AMT - V_DETAIL_BOAC_STL_PAIR.UNSETTLED_AMT1) * V_BOAC_PC_FACT.AMOUNT / CASE WHEN V_DETAIL_BALANCE.LEDGER_BAL_ORG_AMT = 0.00 THEN 1 ELSE V_DETAIL_BALANCE.LEDGER_BAL_ORG_AMT END END * @Select(Entry Codes/Base))

Add two objects for Detail Amount Unsettled (Target) & Detail Amount Settled (Target) under the folder 'Accounting information> Detail> Detail (Target)' as per the SQL definitions provided below.

Detail Amount Unsettled (Target):
SUM(CASE WHEN V_BOAC_PC_FACT.IS_ESTIMATE = 'Y' THEN V_BOAC_PC_FACT.AMOUNT WHEN V_BOAC_PC_FACT.IS_LIQUID = 'N' THEN V_BOAC_PC_FACT.AMOUNT ELSE V_DETAIL_BOAC_STL_PAIR.UNSETTLED_AMT1 * V_BOAC_PC_FACT.AMOUNT / CASE WHEN V_DETAIL_BALANCE.LEDGER_BAL_ORG_AMT = 0.00 THEN 1 ELSE V_DETAIL_BALANCE.LEDGER_BAL_ORG_AMT END END * @Select(Support/Exchange Rates/Entry Codes/Target))

Detail Amount Settled (Target):
SUM(CASE WHEN V_BOAC_PC_FACT.IS_ESTIMATE = 'Y' THEN 0.00 WHEN V_BOAC_PC_FACT.IS_LIQUID = 'N' THEN 0.00 ELSE ( V_DETAIL_BALANCE.LEDGER_BAL_ORG_AMT - V_DETAIL_BOAC_STL_PAIR.UNSETTLED_AMT1) * V_BOAC_PC_FACT.AMOUNT / CASE WHEN V_DETAIL_BALANCE.LEDGER_BAL_ORG_AMT = 0.00 THEN 1 ELSE V_DETAIL_BALANCE.LEDGER_BAL_ORG_AMT END END * @Select(Support/Exchange Rates/Entry Codes/Target))

Problem:
BOAC script and support views for Entry Code - V_BOAC_DIM_ENTRY_CODE2 - related to database optimization issues.

Solution:
Modify BOAC004 and add rtrim() before all codes and entry codes related objects in all the views and the tables to remove the right trailing space in codes.

Problem:
Performance issue with LOV of the object Booking Year Quarter-Local in PC Main Universe.

Solution:
Need to adjust the LOV SQL of the object as suggested below to get LOV from table instead of view to improve performance.

New LOV SQL: Booking Year Quarter-Local

SELECT DISTINCT
  BOAC_DIM_TIME.BOOKING_YEAR_Q
FROM
BOAC_DIM_TIME
ORDER BY
  1   DESC

Problem:
Objects for user-defined fields 6 to 10 (date and string types) are missing, along with an object in the partner universe.

Solution:
The following objects need to be added: 'T3 Business String 06' to 'T3 Business String 10' and 'T3 Business Date 06' to 'T3 Business Date 10.' Additionally, the 'Partner Integer 09' object is missing in the Partner universe.

Problem:
LOV is facing slow performance for Accounting Year and Period object.

Solution:
Accounting year and period object.

SELECT DISTINCT
  BOAC_DIM_TIME.ACC_YEAR_PERIOD FROM
BOAC_DIM_TIME
ORDER BY
  1   DESC

Problem:
The objects settled payable Amount (Original) and settled receivable amt (Original) having issue data was not populating correctly in report level.

Solution:
Need to alter the view V_BOAC_STL_BP_BASE_BUILD with the latest attached script. So that data will be populated correctly into the objects in report level.

Problem:
LOV for Accounting Year and Quarter is not correct.

Solution:
Need to adjust LOV SQL of the object Accounting Year and Quarter to get correct LOV with prefix 'A' included.

Problem:
PC Main universe Issue related to cash flow reporting.

Solution:
To enable reporting of unsettled positions at the start and end of a period, along with all movements in between, the following universe changes have been implemented

Outer Joins Added
Applied outer joins to the derived tables: V_BOAC_STL_PAIR_START and V_BOAC_STL_PAIR_END.

SQL Adjustment in Derived Tables
Modified the WHERE clause to include only WHERE STL.MINBOOKDATE <= @Prompt('Pairing History Booking Year Period Date From','D','Reference Data/Pairing BYRP Date To',mono,free)

Textbox Update.
Updated the universe textbox to reflect the above changes for clarity and consistency.

These changes ensure accurate tracking of unsettled positions and movements across the selected period.

Problem:
Issue with Detail objects- Getting wrong data in Reports.

Solution:
Need to alter the Select statement of the objects Detail Amount Settled (Orig) & Detail Amount Settled(Base) to get correct data in Report.

Problem:
SBOP BI Platform Servers 4.3 SP05 Patch 200 is not available at the DXC e-Delivery portal for clients to download the latest patch.

Solution:
To make sure that the SBOP BI Platform Servers 4.3 SP05 Patch 200 is uploaded to the DXC e-Delivery portal so that it will be available to SICS clients for download. 

Problem:
The 'Log Activity' interface for outbound settings is currently not reportable.

Solution:
Object name and definitions
Interface Main Type=IF_SELECTED_ATTRIBS.FRK_MAIN_TYPE
Class Name = IF_SELECTED_ATTRIBS.CLASS_NAME
Name=IF_SELECTED_ATTRIBS.ATTRIBUTE_NAME

Trigger: Derived table. Result

Create a derived table and give a join to the IF_SELECTD_ATTRIBS table.

Join: IF_SELECTD_ATTRIBS.IS_REQUIRED_OUT=Derived Table.RESULT

Derived table:

SELECT DISTINCT
    CASE 
        WHEN EXISTS (
            SELECT 1 
            FROM IF_SELECTD_ATTRIBS 
            WHERE CLASS_NAME = 'CnuMessageDetails' 
              AND ATTRIBUTE_NAME = 'captureWalkBack'
        ) 
        THEN 'YES' 
        ELSE 'NO' 
    END AS result from IF_SELECTD_ATTRIBS;

LOOKUP & Update:

IF_SELECTD_ATTRIBS.IS_REQUIRED_OUT

We need to create a join for the Reference data and the IF_SELECTD table.

IF_SELECTD_ATTRIBS. FSK_MAIN_TYPE=IF_SELECTD_REFERENCE. SUBCLASS and IF_SELECTD_ATTRIBS. FRK_MAIN_TYPE=IF_SELECTD_REFERENCE.CODE

Problem:
Issue with LOV of the object Responsible Person Full Name ,there are still missing space between First and Last name.

Solution:
Need to adjust LOV SQL of the object Responsible Person Full Name.

LOV SQL:

SELECT DISTINCT
  concat(concat(CNU_USER.FIRSTNAME,' '),CNU_USER.LASTNAME)
FROM
  CNU_USER
ORDER BY
  1

Problem:
TRSI-1640 - SUPP005 some days fails in production.

Solution:
Need to replace the TRUNCATE statement with that of DELETE statement in SUPP05.

Replace 

TRUNCATE TABLE 'SICS4PC'.BOAC_WK1_PARTY;

TRUNCATE TABLE 'SICS4PC'.BOAC_WK2_PARTY;

with 

DELETE FROM  'SICS4PC'.BOAC_WK1_PARTY;

DELETE FROM   'SICS4PC'.BOAC_WK2_PARTY;

Problem:
Fields were wrongly added as user custom objects instead of development objects,risking upgrade issues.

Solution:
 To align with best practices and ensure future compatibility and ease of upgrades, Move these fields from user custom objects to development objects that are intended for internal use and can be safely retrofitted across client environments.

Please use Dev Objects 512-519.

Problem:
25.3 PC Main universe - Universe Set Up Definition - Like the Prefix object but for the System Dates.

Solution:
Need to adjust the chapter in SICS System Admin Guidebook to point out the prefix object a bit more and as well add in instruction about the system dates here how the date objects should be adjusted dependent on which database it is supposed to be reported against.

Problem:
Unnecessary joins and tables no longer needed in the universe.

Solution:
Remove the two obsolete tables and delete the redundant FRK join, as the existing FSK–FRK join is sufficient.

Problem:
Joins and tables that needs renaming and adjustments in SQL in PC Main universe.

Solution:
Need to make changes in the joins mentioned and delete the derived table as it is not needed as per the excel attachment below.
25.3 PC Main Universe Joins.xlsx

Problem:
Add TRUNCATE for BOAC revaluation tables in BO001 script across all Databases.

Solution:
To reset BOAC revaluation tables during BO001 execution, please add the following TRUNCATE statements across all Databases.

TRUNCATE TABLE BOAC_FC_REVAL_BAL_BYRP;
TRUNCATE TABLE BOAC_FC_REVAL_DTL_BYRP

Problem:
BOAC_WK3_FACT table is showing closing status for all worksheets, although they are in open state.
Solution:

• Remove alter statement from creation part of BOAC_WK3_FACT table
• Alter procedure BOAC006- Add FRK_STATUS in INSERT INTO BOAC_WK3_FACT part (in step 8A).
• Add below statement before step 8B -
      IF PINCLUDE_OPEN_WORKSHEET = 0 THEN
      DELETE
      FROM 'sics_pc'.BOAC_WK3_FACT
      WHERE FRK_STATUS <> 'C';
      END IF ;

Problem:
Getting the same data when using 'Premium Currency (Code)' and 'Limit Currency (Code)' in the report. To avoid confusion, please hide 'Premium Currency (Code)' and 'Premium Currency' from the report

Solution: 

• Set the SQL to be the same for both objects: 'Premium Currency (Code)' and 'Premium Currency', similar to how it's set for 'Limit Currency' and 'Limit Currency (Code)'.
• Hide the new objects for premium currency as they are not needed as well as add in the description of these two that they are duplicates and therefore hidden.

• Rename the limit currency to have the same name as in 25.2, meaning changing it from “Limit Currency (Code)” so that it will have the old name “Limit/Premium Currency (Code)

Problem:
Wrong object definition for Premium, which is coming from the 'All Premiums (Original)' folder class.

Solution:
Need to update the object definition for the premium object.

REF_PM_MOPF3.NAME

Problem:
Milli Re: BOAC005_PAIRING - performance issue.

Solution:
Need to alter the BOAC005_PAIRING script as per the script attached to resolves the performance issue.

BOAC005_PAIRING_34003.txt

.

Problem:
The 'ORP As Booking' and 'ORP As Account' values under Currency Transformation Terms are incorrect in the BO report.

Solution:
The current joins are using 'ATOP', which is incorrect and causing inaccurate data to be displayed in the report. Update the join conditions to use 'BTOA' instead of 'ATOP'.

SQL:

ORP_ACCT_CUR_TERM_DTL.FRK_TRANSF_TYPE = 'BTOA'

ORP_PAY_ACCT_CUR_TERM_DTL.FRK_TRANSF_TYPE = 'BTOA'

Problem:
Performance issue in the BOAC procedures.

Solution:
We need to apply condition to choose between DELETE and TRUNCATE based on the target database type (Oracle vs SQL Server).

Changes need to be made in below procedures

BOAC004

BOAC005_PAIRING

BOAC005

BOAC006

BOAC007

Problem:
The join expression is wrong between the Reporting_table and BUS_COND_LOG2.

Solution:
Need to modify the join expression.

BUS_COND_LOG2.FK_ROOT_OBJECT=REPORTING_TABLE.FK_SOC

Problem:
Missing documentation in the SICS SYS Admin Guide for the related BO Table and view definitions update.

Solution:
Need to create a new chapter in SICS SYS Admin Guide just after the SICS patch running chapter so that it will not be forgotten during a database upgrade.

Problem:
Users are not able to see proper data under 'Ded. Inherited' column in BO reports. It is showing 'Yes' against all entries.

Solution:
To correct this issue, we have to create 2 alias tables PA_DED_INHERITED & OP_DEDUCTION_COND and we need update the definition of 'Ded.Inherited' object. Then in the reports we can see 'Yes' against inherited ORPs and 'No' for non-inherited ORPs.

Problem:
Some custom objects still not available as default objects in PC Main Universe SICS 24.2

Solution:
To retrieve the LOV for Payment partner type (CODE), enable the associate Lov option in the BLX layer for this object.

For Level of business (Code) under triangulation limit the Lov using the below given SQL for the Lov.
SELECT DISTINCT
  REFERENCE_DATA.CODE,
  REFERENCE_DATA.NAME
FROM
  REFERENCE_DATA
WHERE
  ( REFERENCE_DATA.IS_ACTIVE='Y'  )
  AND  
  REFERENCE_DATA.SUBCLASS  =  45
ORDER BY
  1

For the object Type of Participation (All) typing error no longer exists, also it is using development objects now and not user custom objects anymore. So, nothing needs to be changed for the third point.

Problem:
In existing PC Main universe, the naming for the Balance objects is not correct and which will cause confusion for developers and users.

Solution:
Need to change the names of the Balance objects to make the naming more uniform and consistent with other objects.

Problem:
Triangulation Scope of Cover main class of business and class of business picking up all the reference data in report.

Solution:
Add 4 joins in universe level to limit the data as mentioned in the screenshot below.

Problem:
Balance Revaluation Amount (Func) Aggregates (Paired).

Solution:
Associate Lov for the object Balance Revaluation Date (Paired) in universe level to get Lovs in report.

Modify the SQL definition of the object Balance Revaluation Booking Year Period.
New SQL:
BOAC_FC_REVAL_BAL_BYRP2.BOOKING_YEAR_PERIOD

Problem:
The objects settled payable Amount (Original) and settled receivable amt (Original) having issue data was not populating correctly in report level.

Solution:
Need to alter the view V_BOAC_STL_PAIRING_BAL2 with the latest attached script. So that data will be populated correctly into the objects in report level.

Problem:
While executing the PDM Procedure UPDATE_PDM_TABLES facing issue.

Solution:
Need to resolve the issue in the procedure to accept null values in PK field, after dropping fk constraints.

Problem:
Filters option is not checked for all sub objects under Insured Period folder in PC Main universe.

Solution:
Need to check filters option for all the sub objects under Insured Period Start & Insured Period End to be able to add them to Query filters.

Problem:
Multiple user records exist with the same USER_ID, differing only by case (e.g., yhsiao and YHsiao). This causes the incorrect display of the Last Logged In information on the screen.

Solution:
The system should perform a case-insensitive lookup for USER_ID so that users are matched even when the USER_ID differs by letter case. The database query should compare USER_ID values in lowercase.

Problem:
Subclass for Security Domain Restriction 'Business Update After Registration Complete' changed in SICS 25.2 (and later) from 45 to 58

Solution:
Restore the subclass for “Business Update After Registration Complete” to 45 and assign a new subclass value (58) to “Accounting Worksheet Risk Code Manipulation” to ensure both restrictions function independently, as class loading is alphabetical and earlier versions always treated “Business Update After Registration Complete” as 45, as shown in the screenshots. Since this change can affect behavior in versions 25.2 and 25.3, the fix needs to be included in both 25.2 and 25.3 SSPs.

Problem:
When updating multiple ratings within the same Web Service (UpdateBusinessPartner), the system gives a message about Specified Business Partner Rating does not exist, even if the ratings exist.
  
Solution:
When adding multiple Ratings to a Business Partner by Web Service (updateBusinessPartner), the system should not give a message about Specified Business Partner Rating not existing when the ratings do exist. Instead, it should update the partner with all ratings, like it currently correctly does if updating only one Rating by web service.

Problem:
The system abends when searching for business periods by Underwriting Year From and/or Underwriting Year To by Web Service.

Solution:
Entry Point: SicsWsDomainSearchEntryPoint:
Web Service: ExcuteBusinessSearch:
When by Web Service searching for business(es) including Underwriting Year From and/or Underwriting Year To as search criteria, the system should not abend. Instead, the system should return the business(es) matching search criteria.

Problem:
System Parameter 'Restrict Invalid Accounting Classification when bookings exist' is invisible while searching by key words.

Solution:
When searching by key words, all topics having that key words to be displayed in the search results.

In this case, 'Restrict Invalid Accounting Classification when bookings exist' though it exists under Accounting > Accounting Classifications, 'Accounting Classification' topic is not displayed in the search results.

SICS implemented code makes it impossible to log performance for SICS API
Method processMessageContext in SicsWsAbstractEntryPoint the boolean always return true and no performance can be logged

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

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

Problem:
++

In 'Add Correction: Input Fields Replacement Values' there is no validation for input value's format for Replacement Value

Solution:
Validation of Input Values is done when mappings starts validation.
In 'Add Correction: Input Fields Replacement Values' window allows to enter data without validation, just like data received from xml or excel file.

So, to fix this issue, The Mapping can be updated to do validation on input data before starting transformation.
Also add data format details on input pattern filed to make sure, data is entered in correct format

Root Cause:
Working as per functionality

Impact on Existing Data

'XIS LIMRIA2' Mapping need to be updated with added checks in validation.

Problem:
executeClaimSearch results in an abend when searching for a claim with a Business Partner - message 'argument type mismatch'.

Solution:
SICS server should return the matching claim.

Workaround:
Execute the search with claim ID only.

Problem:
The system abends when creating a new country without a flag and when touching this country afterwards.
 
Solution:
When creating a new country without a flag, the system should not abend. Instead, it should create the country and show the flag grey with a question mark. When opening this country afterwards, the system should also not abend, but show the country information. **  

Problem:
Abend when trying to Open 'Currency and Exchange Rates' when SysParameters for 'Base Company Segregation' ticked (activated).

Solution:
The 'Currency and Exchange Rates' should be able to be opened even when System Parameter for 'Base Company Segregation' is ticked (activated), without any abend.

Problem:
The setting <caseSensitiveCnuUserNames> is documented in the user guide but it not referenced in the settings file where the setting should be defined.

Context:
The <caseSensitiveCnuUserNames> tag in the datasource definition controls how the retrieval of the SICS user from the database table handles case. The default value is false, which means that SICS presumes that the user id stored in SICS is in uppercase and it will convert the authentication user id into uppercase in order to retrieve it.
In a situation where the authentication user id and the SICS user id are in lowercase or mixed case, then you must set the value to true <caseSensitiveCnuUserNames>true</caseSensitiveCnuUserNames>

Solution:
Added the setting to the shipped sics-database-sources.xml files

Problem:
New SICS User role can't use API properly.

“Final status can only be set by another user' validation happening even if the changeStatusRemittanceBalance operation request sent with a different user ID.

Solution:
System Parameter:
Accounting >>Remittance>> Remittance validation >> Final status requires different signature - selected

When the changeStatusRemittanceBalance operation webservice request sent with a different user ID, then the “Final status can only be set by another user' validation should not happen, instead the remittance status should be changed and the respective response should be received.

Description:
Scripts longer than 255 characters created in older versions (e.g., 21.3) show alien characters when opened in 25.3 and later. This happens because the parsing logic incorrectly checks patterns, leading to corrupted script content.

Solution:
The parsing logic will be updated to correctly handle long scripts created in older versions. This ensures that scripts from earlier versions open properly in 25.3 and subsequent versions.

Additional Comments:

Crash on” Trying to decrement transaction counter, but it is 0 already.” when running a simple 1-liner insert SQL script via SICS batch

Problem:
There are some classes wrongly named having 1 at the end example DeleteAccountingClassificationInput1.

Solution:
This is due to the same classname but having different name space there it is applicable, but at some places i have figured out it is by default generating classname having 1 at the end which is wrong, and this is fixed after generating the .cs file from svc-util tool with the help of a .sh script we are using. it is fixed for the current version and for the all the upcoming Service packs(SSP).

 
Reported By Customer: 

Each time we integrate a new sicsSever.cs into Merlin we have to switch certain class names from <name>1 to <name> or <name> to <name>1  for the re-compiliation to work

“You never really know from one time to the next which classes it uses. Take the latest case, for example, where you had to change to using the class called Input1() — it’s inconsistent, sometimes it uses Input as the class name and sometimes it doesn’t.”

Problem:
Inconsistent and unclear handling of database table naming standards and actions.

Solution:
Delete the table V_CLAIM_DISPOSITION_der. Rename the tables V_RESP_UNDERWRITER_x and V_refSectionLevels so that their names are in all uppercase.

Note: I observed some of the tables are also in lowercase.

AB_Insured_REL (BUSINESS_PRTNR_REL)

ACC_Ex_Rate_Basis (BUS_EX_RATE_BASIS)
ACCT_CurrDtl (ACCT_CUR_TERM_DTL)
ACCT_CurrTerm (ACCT_CUR_TERM)
ACLB_Reinsurer_Alert_Reason (REFERENCE_DATA)

ALL_CNU_CURR_LimInc (CNU_CURRENCY)
ALL_CNU_CURR_LimPay (CNU_CURRENCY)
ALL_CNU_LimCond (CNU_USER)
ALL_CNU_ShareCond (CNU_USER)
AMD_Booking (AMENDMENT)
BAL_AccountPeriod (REFERENCE_DATA)

BAL_BookingPeriod (REFERENCE_DATA)
BAL_GRP_BaseComp (PARTY)
BAL_GRP_PayPar (PARTY)
BAL_OrderStatus (REFERENCE_DATA)

BANK_ACC_RemBP (BANK_ACCOUNT)
BANK_ACC_RemBP_SRC (BANK_ACCOUNT)
BANK_ACC_RemIntern (BANK_ACCOUNT)
BANK_ACC_RemIntern_SRC (BANK_ACCOUNT)
BASE_AUDIT_Bus (BASE_AUDIT)
BASE_AUDIT_business (BASE_AUDIT)

BaseCommCURR (CNU_CURRENCY)

I have found this table name appearing in both uppercase and lowercase formats.

Aim of function:
To provide import function through spreadsheet for “Balance Signature Note” of Balances (claims and technical) on “Balance Properties” window.

Business value for customers:
This functionality will support user to import Signature Notes of balances through a Spreadsheet.

System Parameters affected:
N/A

Existing functionality affected:
'Balance Properties' window for Balances.

Aim of function:
Retrocession Calculation order and Retrocession Account order are created via the SICS API. So that add new XSD Type RetrocessionCalculationOrder and RetrocessionAccountOrder of Element createAccountingOrderInput on createAccountingOrder operation of SicsWsBatchProcessEntryPoint entrypoint.

Business value for customers:
Retrocession Calculation order and Retrocession Account order are created via the SICS API. This can help users reduce the manual creation process.

System Parameters affected:
None

Existing functionality affected:
SicsWsBatchProcessEntryPoint 

Aim of function:
Introduce new columns in the search results container on the “Find : Mass Paring Order” window named 'Base company(s)', 'Business partner(s)' and 'Matching routine'. The values for these new columns will be brought from Mass Paring Order as defined in it.

Business value for customers:
To enhance the identification of Mass Pairing Orders for accounting, both the base company and its business partners—alongside the matching routine in the 'Find Mass Pairing Order' window—will deliver richer, more actionable details. This provides:
 
Enhanced order visibility: Users can now quickly identify the base company, involved business partners, and the matching routine used — directly from the search results. 
 
Improved accuracy in selection: With additional context available upfront, there's less risk of selecting the wrong Mass Pairing Order for accounting processes. 
 
Streamlined workflows: The richer detail supports faster decision-making and simplifies financial reconciliation. 

System Parameters affected:
N/A

Existing functionality affected:
Find :Mass Pairing Order

Aim of function:
To create 2 new columns in the below mentioned database tables representing Booking year period start date and end date so that reports generated will have these dates :

FC_REVAL,
AC_LEDGER_BALANCE,
AC_STL_PAIRING,
AC_DETAIL_LIGHT,
BUS_PERIOD_EST,
PERIOD_SNL_EST,
GL_T_ALL,
GL_T_NEW,
GL_R_ALL,
GL_R_NEW,
GL_P_ALL,
GL_P_NEW

Business value for customers:
Reports generated for customers will have these dates and will be more informative.

System Parameters affected:
None

Existing functionality affected:
None

Aim of function:
When renewing a contract, most terms and conditions remain the same for the new insured period, so the system copies them to the new period. Earlier the system also copied the shares. As shares often vary, it is now possible to renew a business without copying the shares. This is customizable so that, if set up to not copy, the new period will get no shares. If the new period gets a definite status however, the system adds a share page to the renewal wizard so that the user can enter the new share.

Business value for customers:
Ensures accuracy
Improves usability

System Parameters Affected:
None

Existing functionality affected:
Renew Business
Mass Renew Business
Automatically Renew Business
Maintain Share Conditions
Maintain Limit and Premium Conditions
Manage Agreement Life Cycle Status
Maintain System Parameters
Renew Business by Web Service

Aim of function:
The FGU indicator should not be enabled/set when Business Administration type is LPC, despite matching Base Company and Type of Participation, as these claims on these businesses do not use FGU accounting.

Benefit for customers:
Claim is created with correct settings

System parameters affected:
New Base Company Specific Claim Specific parameter - selecting the Additional Business Classification table and table value.

Existing functionality affected
Create Claim
Create Claim Program
Process new claim emessage

Aim of function:
To introduce a new eMessaging modifier rule “ModifyIPReferencingRuleToAllowToleranceOnFromDate” to allow date tolerance for message contract start date.

Business value for customers:

• User can set Tolerance limit in the new rule “ModifyIPReferencingRuleToAllowToleranceOnFromDate” 

• System now links message to the insured period even if the message start date is not exactly matching, if it is within the defined tolerance.

System Parameters affected:
N/A

Existing functionality affected:
eMessage Processing.

Aim of function:
To create new Use cases in Access security manager window,

• eMessaging Message Discard with Acceptance acknowledgement.
• eMessaging Message Reject with acknowledgement.
• eMessaging Message Discard Without acknowledgement.

Business value for customers:

• Prevents users from discarding/ rejecting the messages without acknowledgement.
• Able to assign each use cases to appropriate user roles as required.

System Parameters affected:
N/A

Existing functionality affected:
eMessaging Discard& Reject functionality.

Aim of function:
To introduce a new rule 'CheckForMandatoryHeadlineLoss' for eMessaging claims to enable applying mandatory headline loss for LOB/RU validations.

Business value for customers:
User get notified with warnings/error on eMessage when the headline loss is defined as mandatory for LOB/RU.

System Parameters affected:

• From base-company specific settings, Claim Headline Loss Assignment – Mandatory headline loss link for MCOB flag with MCOB.

• Headline Loss link mandatory for reporting units.

• Link to a Headline Loss is Mandatory When Closing Claim Worksheet.

Existing functionality affected:
eMessage processing.

Aim of function:
Currently Insurable objects store and display the GPS coordinates using the older notation of Direction, Degrees, Minutes, Seconds. ie: (N 59° 55' 01'', E 10° 43' 39'').

This enhancement moves instead to use the simpler decimal degrees format (59.91715, 10.72764) for display and storage.
5 decimal places is accurate to about 1-2 meters. https://en.wikipedia.org/wiki/Decimal_degrees

Business value for clients:
The decimal degrees format is widely used by analytics tools such as SAP BI, Microsoft PowerBI & Excel, AWS QuickSight which allows extracts to be used to create geographic representations of SICS data.
Additionally, it is simpler to enter 2 decimal numbers in the UX and the data storage format is smaller and speeds up SQL queries.

System Parameters affected:
None

Existing functionality affected:
Insurable Objects General Information & BI Universe

Aim of function:
Assess and identify the suitable methodology for automatically loading only changed data into PDM tables, ensuring efficiency, accuracy, and scalability.

Business value for customers:
Ensures selection of the most efficient and reliable incremental loading approach for timely, accurate PDM updates.

System Parameters affected:
N/A

Existing functionality affected:
N/A

Aim of function:
Utilize PDM table structures to develop interactive Power BI reports, supporting business analysis through accurate data modeling and visualization.
The repots include -

• 44 Statistics Entities Triangular
• 44 STROS COUNTED between dates with Orig_UD
• 48 Technical account balance situation from the date.
• 54 Technical_Financial_Account_All_Cias_Retro_Robot.
• 63 Remittances and Pairings Report

Business value for customers:
With the newly developed Public Data Model (PDM) database views and tables, BI developers now have a standardized and structured data foundation to build reports and dashboards. These can be developed using BI tools such as Power BI, enabling consistent and efficient data visualization and analysis.

System Parameters affected:
N/A

Existing functionality affected:
N/A

Aim of function:
Implement enhancements to SICS Life Business Objects universes to incorporate new business requirements, improve performance, and ensure accurate, comprehensive reporting

• Identify the tables, Objects, Joins need to be added or modified.
• Modify or add objects, classes, and measures to reflect updated business logic.
• Optimize universe structure for query performance and usability.

Business value for customers:

• Improves reporting accuracy and provides enriched insights to support decision-making.
• Enhances universe usability and performance, reducing report generation time and errors.

System Parameters affected:
N/A

Existing functionality affected:
N/A

Aim of function:
Prevent user roles that have been allocated to users and therefore part of the security setup from being deleted. This preserves the audit trail of security rights. The role can only be inactivated.
User roles that have not been allocated to users can be deleted.

Business value for customers:
This ensures previous security settings are preserved and can be tracked in audit trails.

System Parameters affected:
Security Administration

Existing functionality affected: 
Delete Security Role

Aim of function: 
To introduce all the following new variables in the Multi GAAP and Underwriter estimates Calculation editor from Stepped Sliding Scale and Sliding Scale commission window.  

• Provisional Commission
• Minimum Sliding Commission
• Maximum Sliding Commission 
• Minimum Loss ratio
• Maximum Loss Ratio
• Slope Ratio 
• Loss Ratio

Business value for customers: 
To retrieve values from Stepped Sliding Scale and Sliding Scale commission conditions. Provisional Commission and (Stepped) Sliding Scale Commission can now be booked using different entry codes. Booked (stepped) sliding scale commission that represents the differentiation between the Provisional Commission and the SSC.

System Parameters affected:
All of the calculation variables specified above will be added to the Multi GAAP and Underwriters Calculation Editor.

Existing functionality affected:
Multi GAAP and Underwriter Calculation Editor. 

Aim of function:

• Create new PDM database objects (e.g., tables, indexes, views) from within the SICS System Admin tool, ensuring centralized control over database structures.
• Enable creation and management of foreign key (FK) constraints directly from SICS System Admin to enforce referential integrity between related tables.
• Verify and maintain data quality within PDM tables by identifying inconsistencies or missing relationships and allowing corrective actions to be taken efficiently.
• Automate script generation for the creation, modification, or deletion of PDM objects and FK constraints, ensuring consistent deployment across environments (Development, Test, Production).
• This functionality aims to streamline database management, reduce manual dependency, and strengthen data integrity and traceability across the SICS and PDM systems

Business value for customers:

• Create new PDM database objects (e.g., tables, indexes, views) from within the SICS System Admin tool, ensuring centralized control over database structures.
• Enable creation and management of foreign key (FK) constraints directly from SICS System Admin to enforce referential integrity between related tables.
• Verify and maintain data quality within PDM tables by identifying inconsistencies or missing relationships and allowing corrective actions to be taken efficiently.
• Automate script generation for the creation, modification, or deletion of PDM objects and FK constraints, ensuring consistent deployment across environments (Development, Test, Production).

System Parameters affected:
N/A

Existing functionality affected:
N/A: