Release documentation - P&C Enhancements and requests

Problem:
FC Revaluation Order- Details are getting revaluated for a settled balance when the parameter is ON

Solution:
Preconditions: System parameter Include realize gain/loss in FC Revaluation is Checked
When running the FC Revaluation Order the system correctly include Unsettled Balances in its revaluation. But we must also make sure only Unreleased Deposit details and Reserve details not sums up to zero are included in this revaluation. Other details shall NOT be revalued.

Problem:
FC Revaluation Error- After annulling and running FC Revaluation order, Previous amount is doubled of Original Amount

Solution:
When running the FC Revaluation order for a balance AFTER it has been annulled from a pairing with a remittance the system must set the Previous Amount for this revaluation row equal the Current Amount in the LAST row before the annulling.

Problem:
BUG - 1073670 - Issue with Webservice when testing SE-6908

Solution:
When running API createWorksheet with the element <newAmount> and <replacementValues>true</replacementValues> given together with the element <oneHundredPercentFigures>true</oneHundredPercentFigures> or <figuresFromShareConditions>true</figuresFromShareConditions>.
then the system must recalculate the given newAmount according to the Signed Share on the Share conditions.

Problem:

Adjustment Premium Order requires UWY to close worksheets

Solution:

1) Make both a U/W Year From and UpTo field on the Adjustment Premium Order, similar to the Instalment Premium Order. For existing orders with a year in the existing U/W Year field, a DB Patch is needed to set this year in the U/W Year UpTo field, i.e. UpTo year = From year.

2) When an Instalment or Adjustment order runs the From field and the UpTo field must be mandatory when the Close Worksheet box is selected.

3) When a new Adjustment Premium Order is created from Find Accounting Order window the U/W Year From and To shall be defaulted according to the same logic as the Instalment Premium Order, i.e. with the current year in the To field and with the past year in the From field. When both the Instalment and Adjustment Premium order is created from the P/L Conditions, then the U/W Year From and To shall be set equal the U/W Year the business.

4) When an Adjustment Premium Order runs, with both the U/W Year From and To given, or only the From year, then the system must follow the same logic as the instalment order and include Insured Periods from the businesses on the order that have U/W years matching the given U/W years on the order, i.e. include all U/W year equal or higher than the From year and less than or equal the UpTo year, if this is given else all higher years than the From year.

5) When an Instalment or Adjustment Order is created and the user give both a From and an UpTo Year, make sure the system validates this input so that the From Year is less than or equal the UpTo Year.

Workaround:

Select 'Close Remaining Open Worksheets' from the menu; Run a 'Open Worksheets Mass Update Order'

Problem:

New Amount column for Reserves on business ledger SR ADO 1876020

Solution:

Preconditions:
Booking on a technical worksheet with an entry code defined as 'Allows Entry of Replacement Values' but where the 'Calculate Based on As of Date' is NOT selected.

When a technical worksheet is created through the API interface with the New Amount given in the soap, e.g. createWorksheet, and this worksheet is automatically closed without opening the worksheet details in edit mode, then the system should set the New Amount column on the Ledger to Null.

Exception to the above:
If the 'Calculate Based on As of Date' IS selected on the above entry code, then the New Amount column on the ledger shall keep the New Amount given in the soap.

Problem:

Reserve and Deposit Detail Mass Update produce unexpected result

Solution:

Preconditions:
Open worksheets have been created on prop treaty ORP from the Reserve and Deposit Detail Mass Update order and all the balances on this worksheet have the As Account correctly set to True (IS_IN_ACCT_CURR = Y) and correctly set the As Booking set to False (IS_IN_BOOK_CURR = N).

When an existing Open worksheet, created on prop treaty ORPs by the above order, is to be manually closed, the system must check the As Account flag on any of the balances on the worksheet. If this flag is true (IS_IN_ACCT_CURR = Y), then the system shall NOT set/change the value of the As Booking flag but keep it false (IS_IN_BOOK_CURR = N).

Problem:

Incorrectly generated old pairing ID using 'Replace Selected URB in Pairing'

Solution:

When an Unallocated Remittance Balance (URB) is replaced by another balance, either automatically when a matching technical balance is booked on the actual business or manually when the option Replace Selected URB in Pairing is selected for the URB on the business ledger and the user manually include one or more balances to replace the URB, then the system shall give the SAME Pairing Id for the anulling of the URB as it does for the balance(s) that replaces it (and not copy the Pairing Id from the original pairing with the URB)

Problem:

SICS suddenly disappears when running BP Balance Mass Update

Solution:

Problem to solve:
In the Business Partner Balance Mass Update there are several criteria the user can give to find the actual balances to be updated. Among these criteria, there is also one that is found on the Details of the Balances, Insured Period Start Date From - To. The system will therefore find a number of Details, independent if this field is used or not, and then display the relevant Balances for these Details. The number of Details found when Find Now is selected is according to the Cursor Amount defined in the system parameters, e.g. 50. But when the system shows the number of Found Objects below the balance container it is the actual Balances found so it may often be less than the Cursor Amount, but it match the balances listed. As a consequence of this the user has to press the More button until it becomes disabled, to be sure that all wanted balances are listed.

Solution:
A new global system parameter will be introduced so that the users can decide if this Insured Period Start Date From - To shall be used as criteria or not. By switching ON this new parameter the Insured Period Start Date From - To becomes disabled and the system will only use the balance criteria on the mass update. The result of this is that the number of Found Objects will match the actual listed balances.
When the new system parameter is NOT selected, as per existing functionality Insured Period Start Date From To fields will be enabled in mass update window and the criteria will be on detail level, i.e. the system will first find and work with the number of details according to the Cursor Amount, e.g. 50 and then display the relevant balances for these details so the number of Found Objects can show less than the Cursor Amount defined in the system parameters.

So client has to decide if they need to extract balances based on the insured period or not and select the new system parameter accordingly. It will affect both the Expected BP Replace and Responsible BP Replace tabs on the Business Partner Balances Mass Update.
Name of new system parameter: 'Disable Detail Criteria on BP Balance Mass Update' and should be placed under Accounting, Miscellaneous tab.

Workaround:
If you want to use the Insured Period Start Date From - To, and keep the new system parameter not selected, then the number of Found Objects will not match the actual number of balances listed. The users just have to press the More button until it is disabled, even if the Found Objects show a number that is less than the Cursor Amount defined.

Problem:

Inheritance of Accounting Classification cause problem on Retrocessionaire Participation upon renewal

Solution:

When the user selects the option 'Copy selected to Placements' or the option 'Copy all to Placements' from the AC window on a prop or non-prop treaty OCC, the system shall also perform this operation even if there are ACs already present on the ORPs and REPLACE these, including AC split percentages, if possible. If it is not possible, e.g. if there are bookings on any of the ACs on any of the ORPs, on either Open or Closed Worksheets, then the system will raise an error message saying that this cannot be done for those ACs because booking exists and for the remaining ACs where no bookings exists the replacement should be done.

The message text shall be something like this: 'Operation interrupted for one or more Accounting Classifications on Placements where booking already exist, and can therefore not be replaced.'

Workaround:

When the system parameter Automatic Creation Of Accounting Classification under Accounting Classification page is selected, then the ACs will not be copied to the Placement when the Mass Renewal is selected on the OCC. So if you now use the option 'Copy selected to Placements' or the option 'Copy all to Placements' from the AC window on the OCC, then the system will copy the ACs from the OCC.

Problem:
Retroceded percentage shown on REAC order wrong 

Solution:

From the Retrocession Calculation Order, when the user selects the option View Worksheets Balances and that window opens, make sure that the Retroceded% column shows the correct percentage for the Retrocessionaire Participations, if the Balance contains of only one UwYR/Insured Period. If the balance belongs to a Retrocessionaire or the OCC itself, with more than one UwYR, it shall be blank.

Problem:

Loss Deposits: Wrong Calculation of Loss Deposits Retained Validation

Solution:

Deposit Condition Preconditions:

Calculation Method : Pct of Premium/Loss Reserves

When we are computing the Retained amount in the Validation, system should calculate the Deposit Retained amount as the result of (Accumulated Premium/Loss Reserves * Deposit Percentage) – (Total Deposits Retained of all closed WS + Total Deposits Released of all closed WS + Deposit Release on current WS).

And while computing the Deposit Release amount in the Validation, system should calculate the Computed Amount as only the Deposit Retained Amount in referred Account.

Problem:

System abend when trying to inactivate a technical worksheet having > 1000 balances

Solution:

When a spreadsheet with more than 1000 Details that also creates more than 1000 Balances on a Technical Worksheet, the system must be able to set the worksheet to Inactive when the user select this option. It must be possible to Apply the worksheet to the database and to change the status to Closed.

Problem:

Premium Posting pop up message in SICS 24.1 is missing

Solution:

When the user selects the Book Selected Instalment option to inspect the booking details before the worksheet is closed, and then navigate to the Worksheet Closing window to get the worksheet status set to Closed, then the system shall also present message AC0227 telling the user which worksheet id the worksheet has got. This message appears correctly when the user selects the option Book and Close Selected Instalment so that the system closes the worksheet automatically, in the same way the AC0227 must appear also when the worksheet is closed manually.

User must also be informed with the same message when booking of Adjustment premium and booking of Special Acceptance Premiums from the Premium and Limit conditions.

Caused by:

SICSR-25391 in version 23.2

Problem:

Unneccessary warnings when running reinstatement assumed order - when  order does not result in any bookings on a specific section of an included business, and question whether zero bookings should be made when no adjustments due.

These warnings also prevents the scheduler from running correctly.

Solution:

Remove these warnings. 

Do not create zero bookings 

Problem:

How can we avoid  AC0255 and make a booking on amendment 0 without changing the AC date?

Solution:

When a user select the UNFI option after clicking on the menu button on a Technical Worksheet window, the system must check if any detail on the worksheet is linked to an Insured Period with Amendment and if this is the case, then the system must present a new error message and inform the user to select Apply and UNFI to make sure the business validation and split by amendment takes place so that the system can present message AC0255 to inform the user that this split should be done.
The new error message should say something like this: 'At least one detail on this worksheet is linked to an insured period with amendments and you must select the option Apply and UNFI to get the necessary validation and split by amendment before it is stored to the database'.

Workaround:

Use the option Apply and UNFI instead of UNFI, so that the system performs the necessary business validations.

Problem:

Error received when trying to pair technical and remittance

Solution:

Preconditions:
System parameter 'When pairing, always use Remittance as the driving Balance' is selected, and 'Balance Pairing Group in Use' is selected

When the driving balance in a balance pairing is a Remittance balance and the included balances is a combination of technical/claim balance(s) and remittance balance(s), then system much check for the system parameters 'Pending Status for Balance Pairing' and 'Exclude Definite Pairings from the above restriction'. If either both these parameters are selected or unselected at the same time, then the error message AC0823 must appear, telling the user that this pairing must be interrupted because this combination is not allowed. If either of the parameter is not selected then there should be no error message displayed.

Problem:

No error(ACBP034) triggered when clicking on Create Remittance/Link to Remittance with Authorized status in the settlement balance group.

Solution:

Prerequisite: System parameter  'Allow Balances in Authorized Status in Settlement Balance Group' under Balance Pairing is ON.

When a Settlement Balance Group contains worksheets with the status Authorized and the user selects the option Link To Remittance or Create Remittance from SBG, an error message must be raised saying, 'This is not allowed since the balance is part of an SBG.' This SBG cannot be included in balance pairing, either manual pairing, mass pairing, or group pairing. 

Problem:

Booking with different (wrong) Access Code possible

Solution:

Preconditions: The system parameter Segregate Data by Access Code is activated.

1. if you change the Assigned Access Code for your own user, either in Security or in User Preferences, a new message should be presented for you; 'By changing the Assigned Access Code the system will automatically be refreshed. Do you want to continue? Yes/No. By answering Yes, the system automatically refresh the system for you. By answering No, the changes will not be done.
2. if you change the Assigned Access Code for another user, a message should be presented for you where you can reply Yes to force this user to refresh when trying edit anywhere or reply No to roll back your update.
3. if your Assigned Access Code has been changed by another user and you are trying to edit any object in the system, you should be told that a full refresh of the system must be done before the edit can be performed, with the option to answer Yes or No to do so.

Problem:
Walkback when running Retro Calculation order in Postgre SQL database

Solution:
When running the Retrocession Calculation order or Retrocession Account order in a Postgre SQL database the system must be able to execute this operation without falling over with a walkback in the same way as when running these orders in Oracle.

The problem is that the column AC_WORKSHEET.IS_FROM_COM_ORDER data type is Character (1) and this will not work. We need to change it to Varchar to support more than 1 character.

Problem:

BookInstallment web service is not applying and saving AC Split % when created worksheet is in Open status

Solution:

When executing the bookInstalment web service with the element <bookAndCloseSelectedItem> set to false, so that the worksheet becomes Open, then the system must do the split of the details according to the AC split percentages if the element <bookingsToBeSplitPerAccountingClassificationPercent> is set to true. The operation that must take place when the worksheet is created and applied to the database by the above web service, is the same as when the user selects the menu button option 'Apply Split' on a manual created worksheet.

Problem:

Remittance Worksheet | Incorrect direction of balance amount

Solution:

When a remittance is created and the user switches between the direction Received and Paid, the system must behave consistently so that all relevant amounts also switches the sign like the Hash Total on the two tabs in the bottom right corner and the Original Amount and the Functional Currency amounts. It work fine if you click on the Received to switch between Received and Paid, but it must also work if you click on the Paid to switch between Received and Paid.

Workaround:

Always click on the Received box to swithch between Paid and Received and between Received and Paid. This will update the totals and the functional currency amounts correctly.++

Problem:

In MG related orders the errors are not listed via Batch server

Solution:

Make sure Multi GAAP calculation variable %claimBasis reads the correct Claim basis for all type of Business,
If more than one Claim basis is given, take one random Claim Basi.
if Claim condition is not define then system should not have any kind of error message, it should reterive the value as per calculation rule define. 

Problem:

System is triggering unexpected AC0392 Premium Deposit Retained expects the worksheet to include a base detail for calculation.

Solution:

When we have a Premium and Loss Deposit condition defined on the business and when on a worksheet, booked only either Premium or Loss then system should not trigger AC0392 error for the other Deposit condition which is not booked.

Problem:

System is  triggering unexpected AC0400 Premium Deposit Released expects a corresponding Deposit Retained Detail.

Solution:

When we have a Premium and Loss Deposit condition defined on the business and when on a worksheet, only booked Deposit Release for the Deposit Retained from the previous referred account then system should not trigger AC0400 error but should accept the booking if the amount is correct else should trigger AC0770 comparing the computed value to the threshold limit defined on the rule.

Problem:
SICS Pairings without Pairing_ID in SICS 24.2 SSP01, if more than two balances are included in the pairing, only 2 pairings get the Pairing Id correctly stored in the database.

Solution:
When balance pairing takes place and the pairings are committed to the database, then the system must also commit and store the Pairing IDs correctly for ALL involved pairing objects.

Problem:
When using PreparedStatements, some queries were incorrectly using a '1/0' value for yes/no columns instead of the standard Y/N values SICS.
On SQL Server and Oracle this is a silent error. On PostgreSQL this produces a walkback error.
Below are the functionalities affected,

• Accounting Order -> Preliminary Bookings Order
• Accounting Order -> Commutation Multi Businesses
• Accounting Order -> Retrocession Account Order
• Accounting Order -> Retrocession Commutation Account Order
• Accounting Order -> Retrocession Calculation Order
• Accounting Order -> Retrocession Commutation Calculation Order
• Accounting Order -> Retrocession Calculation Order For Non Proportional
• Accounting Order -> Retrocession Estimation Calculation Order

Solution:
Correctly map boolean values to Y/N when setting prepared statement values.

Workaround:
Turn off PreparedStatements (Parameterized SQL) mode

Root Cause:

Extent of Impact:

Impact on Existing Data
There may be some columns with incorrect values.

Recovery Method for Existing Data Affected

Please execute the below queries in the respective databases if PreparedStatements (Parameterized SQL) mode is turned on

UPDATE AC_WORKSHEET SET IS_FROM_COM_ORDER = 'Y' WHERE IS_FROM_COM_ORDER = '1';
UPDATE AC_WORKSHEET SET IS_FROM_COM_ORDER = 'N' WHERE IS_FROM_COM_ORDER = '0';
UPDATE AC_PRE_ORD_HELP SET IS_RETROCEDED = 'Y' WHERE IS_RETROCEDED = '1';
UPDATE AC_PRE_ORD_HELP SET IS_RETROCEDED = 'N' WHERE IS_RETROCEDED = '0';

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:
System abends when click the 'import' button on 'Import remittance worksheet from spreadsheet' window.

Solution:
When the user imports the remittance worksheet through the function 'Import Remittance Worksheet From spreadsheet' window, instead of abend, system should save it and generated the remittance identifier.

Problem:

Multi GAAP calculation Rounding function not working as expected when its trigged from other estimation item. The fix under SICSR-29450 is working fine for the single layered calculation rules of period estimates. However, for interdependent multi layered calculation rules, it produces considerable difference in the period estimate amounts. 

Solution:

As the provided fix is having some side effects and currently there is no alternate solution possible, the fix under the case SICSR-29450 to be rolled back to avoid the impact.

Problem:
Renewal of a Single Treaty Protection, created from an assumed sub section, is not possible due to message 'BS00185 - Renewal is not possible on sub sections. Renewal must be performed from the Main section'.  This message is given even if the user is on the main section.

Solution:

If the user is on a proportional single treaty protection or a proportional facultative protection that, were created from an assumed sub section, and then tries to renew, the system should not give the message:  ‘BS00185 - Renewal is not possible on sub sections. Renewal must be performed from the Main section'. The user is already at the main section. Instead, the system should give a message saying ‘Renewal not supported for single treaty or facultative protections created from a sub section’. 

Problem:

Using the classifications of the contract to create several sub sections in one go is wrongly not possible when a classification is mapped to more than one parent classification.  The system suggests sections without these classification and therefore mandatory classifications will be missing. The system gives therefore the full stop message 'P0084 Validation Error - Creation not possible. A section will be missing mandatory classification: Sub Class of Business.'.

Solution:

Structure Tab:
Pop Up Menu: Create Child Sections
When creating sections per a Classification Type and one of its values are set up in the reference data with more than one parent, the system should, for the suggested section hierarchy, suggest also the classifications that have more than one parent.

Workaround:

For the sub sections that cannot be created by the option Create Child Sections, consider creating them one by one with the Add Child Section option. 

Problem:

The system abends when using ‘Add and Realize Retrocessionaire’ on a business with sub sections and classification method  'Agreement Type'.

Solution:

When selecting ‘Add and Realize Retrocessionaire’ on an assumed business that has sub section and has Agreement Type, the system should not abend. Instead, it should create the facultative Retrocessionaire Participation business.

Workaround:

Use instead the pop-up options ‘Add Retrocessionaire Fac Protection’ and ‘Realize Fac Protection…’ (in separate  steps), and add the Deductions manually on the created FAC Retrocessioniare Participation afterwards.

Problem:

The system abends when Place Selected to Retrocessionaire is executed right after an Intermediary Facultative Protection is created and realized without the proportional protection assignment being saved.

Solution:

Proportional Protection Assignment:
When on an assumed non-proportional facultative business using the option Place Selected to Retrocessionaire, the system should not abend when created via Intermediary Protection immediately after this Intermediary has been created and realized and the Proportional Protection Assignment is not yet saved. 

Workaround:

Save the proportional protection assignment after creating the intermediary participation, before placing this to retrocessionaires.

Problem:

Non-Proportional Facultative outward cedent's contract with special premium selected shows wrong limits for our share on section overview of retrocessionaires with overridden premium and limit conditions. 

Solution:

If having overridden the Premium and Limit Conditions on a Retrocessionaire Participation, which is only possible if Special Premium is selected,  the system should not show wrong limits on the Structure Tab.  Instead, the system should show the same Cover and Aggregate Limit amounts as are currently correctly shown on the Limit and Premium Conditions.

Problem:

When on the Life Cycle Tab, selecting the Previous sub tab, and there is no previous status to show, the system should not show the strange title: '!SicsBusinessStatusMainZNotbook......' in the middle of the window. 

Solution:

When selecting the Previous sub tab, and there is no previous status to show, the system should show the title: 'No Previous Status Available'.

Problem:

The Compliance Check List is showing duplicated items when Reinsurer is defined as Follower during the business creation.

Solution:

The Compliance Check List must not show duplicated items when Reinsurer Position is added during the business creation. The system should show each item only once, just like it currently correctly does when the Position of the Reinsurer is updated after the business has been created.

Problem:
Find Claims returns one row per claim reference type when using reference ID as search criteria; and therefore results in more than one row if reference ID is the same for different reference types. 

Solution:
Find claims should return a single row if claim is linked to only one business regardless of the claim reference.

Problem:

The system picks incorrect amendment when both Risks Attaching and Losses Occurring is defined as Claim Basis and Date of Loss is after insured period

Solution:

When the date of loss is after the insured period, the system should interpret this as a Risks Attaching, and use the Original Policy Period Start date to determine correct amendment.

Problem:
FGU distribution is incorrect when booked with negative figures

Solution:

Nothing should be allocated, if the own incurred is below retention

Only when either paid amount / 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:
When moving a Claim on a Claim Program, on to a the same Source treaty using the 'To another Treaty' Option , System abends.

Solution:
When the option 'To another Treaty' is used , the source CP business should not be displayed on the Business selection screen or the user should be restricted to proceed further by a Validation.

Problem:

Find claims does not return all results, and MORE button is not activated.

If number of selected base companies exceed 1000 the system abends.

Solution:

If the total number of claims or soc-to-claim-relations (depending on search option) for the defined search criteria exceed the number of records to be retrieved as specified in User Preference/System Parameter, the system should retrieve the number of records defined in User Preference/System Parameter and activate the MORE button, allow the user to retrieve the additional records.

The system should allow searching for more than 1000 base companies.

Problem:

The distribution towards layer is incorrect when incurred is zero, and own incurred > excess, and expected distribution is only towards AAD

Solution:

The system should allocate towards AAD  before allocating towards layer

Problem:
FGU distribution incurred amount is incorrect when the Automatic Index calculation flag is set and distributed incurred exceeds the nominal cover.

Solution:
The system should correctly display incurred amount

Problem:
Missing CM0633 (selected business has other locations not included in Claim Program) when adding business with greater location than CP

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:
Accuracy validation AC0770 error message always displays as 'greater than' although booked amount is within tolerance.

Solution:
The system should display greater than only if amount exceeds upper limit. 

If amount is less or or equal, but still raises an accuarcy error, the error should read 'less or equal to'

Problem:
Error message which is appearing when selecting to generate worksheet from FGU from an inactivated claim is not informative.

Solution:
Disable both worksheet options from an inactivated claim.

Workaround:
Activate the claim

Problem:

Incorrect validation error when adding a business to a Claim Program, and existing Claim Program location is a country group defined as exclusion (for example World wide excl US) , and new business has location defined as country group with that exclusion (for example World wide).

Solution:

The system should allow businesses to be added if the cover all of the Claim Program's locations. 

Problem:
BookReinstatementAccruals on multi-layer FGU booking is adding RIP Reserve bookings but also updating all balances with the current / Lead FGU message.v This leads to incorrect control balances.

Solution:
BookReinstatementAccruals must not trigger the updating of linking / references on any balances created.

Workaround:
If there is a CheckLiquidBalanceControlTotal raised problem then this must be overridden on the eMessage that is linked to the balance. This may be on multiple balances / eMessages and not just the one where the problem is raised.

Root Cause:
BookReinstatementAccruals processing

Problem:
Worksheet Validations Errors AC0392, AC0395, AC0399 cannot be overridden from eMessage (ISSUE 201)

Solution:
Applying an override on an eMessage Accounting Validation Rule should be applied to that rule and related bookings regardless of the specific warning. message

Workaround:
Swap to Worksheet and manually apply overrides

Root Cause:
Tolerance level on specified warnings other than amount

Extent of Impact:
Accuracy Validation rule Warnings other than AC0770 (Condition, Trigger Amount but with wrong Target Amount with Deviation above Threshold)

Problem:

Need to create a object which extract whole XML data at the report level.

Solution:

Create a object using below table and column detail to extract XML data.
XML_DOCUMENT.XML_DATA

Problem:
LPC Settlement Messages error with Message amount does not match SICS original balance amount and due to non-unique message references and are creating Account Grouping Balances with balances for multiple messages that are not linked to the FAI and thus cannot be easily located and edited.

Solution:
Do not create an AGB if it would be outside tolerance.
Do not group balances into an AGB that have differing eMessages or their UUid reference.
Do raise errors for LPC Settlements that do not locate a single balance or if a single balance is located outside of tolerance - in these cases the FAI will go to Automatically Accepted without linking to a balance.

Workaround:
Locate any Account Grouping Balance created and delete it or remove all but the desired item. Manually link the FAI.

Root Cause:
SICS 24.2 - SICSR-28652 - No Error Triggered for Responsible Partner in Alert Status

Extent of Impact:
LPC Settlement messages that have non-unique references in FAI.

Problem:  

 In System administration guide (SICS docs), In many chapters like chapter 16.8, 16.14 and 16.15 the images are missing.

Solution:

Add images in the above mentioned chapters in System administration guide.

Problem:

Solution:

Declination Reason:

Workaround:

Root Cause:

Extent of Impact:

Impact on Existing Data

Recovery Method for Existing Data Affected

Problem:

Adding partner alert objects under responsible partners, payment partners and as well as under reinsurer and cedant (business information>business partner) to reduce cost, run time and improve report efficiency.

Solution:

First add four alias table for REFERENCE_DATA i.e., BOAC_RP_Alert_Reason, ACLB_RP_Alert_Reason, BOAC_PP_Alert_Reason and ACLB_PP_Alert_Reason.

Next join the two new alias tables
BOAC_Alert_Reason.CODE=PTY_BOAC_RP.FRK_RSN_FOR_ALERT AND BOAC_Alert_Reason.SUBCLASS=PTY_BOAC_RP.FSK_RSN_FOR_ALERT

(Refer to the screenshots below)

ACLB_Alert_Reason.CODE=PTY_SecPayPartner.FRK_RSN_FOR_ALERT AND ACLB_Alert_Reason.SUBCLASS=PTY_SecPayPartner.FSK_RSN_FOR_ALERT

Thereafter create a new sub-class Alert status with two objects- Reason for Alert & Reason for Alert(code) for responsible partner, payment partner, cedant and reinsurer.

Reason For Alert:            @Aggregate_aware(BOAC_Alert_Reason.NAME,ACLB_Alert_Reason.NAME)

Reason For Alert (Code):         @Aggregate_aware(PTY_BOAC_RP.FRK_RSN_FOR_ALERT,PTY_SecPayPartner.FRK_RSN_FOR_ALERT)

Problem:

A few indexes are missing on SICS tables and BOAC tables for BOAC004, BOAC005 scripts.

Solution:

Add a few indexes for boac004 and boac005 on SICS tables and BOAC tables.

Remove begin / commit trans in BOAC004 for BO_DM_ACTIVITY_LOG, so that the client can follow progress directly from BO_DM_ACTIVITY_LOG.

Remove statistics scan for BOAC_STL_PAIRING(BOAC005).

Increment BM_BATCH_NO correctly for BOAC004, so that it eases building queries.

Refer to the attached document for the changes mentioned above - LF283 Client Error Report.doc

Problem - 

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.

• Even If the Main and Original currencies are the same, some associated values vary, like in Entry Code=83
• 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)).

Solution - 

Database view   V_ENTRYCODES_DATES needs to be altered to avoid the aggregation problem

Problem:

In Financial statement report amounts are doubling in the query when we use the object 'RC Claim Disposition'.

Solution:

Need to create a view V_RC_CLAIMS and provide the joins with respective tables. Update the join between CLAIM_DISP_RC and SOC_TO_CLM_RC to get latest dispositions.

Problem:

The value for the field AUTOM.BOOKED is not matching between SICS and BO for a few business ids.

Solution:

We need to add the column 'Autom.booked' directly into the view V_SJ_BC_INSTAL0_DER, as we need to get the data directly from the database view and not the SICS logic instead to resolve this issue.

Note: The SICS code for the field autom.booked is attached below for reference to fetch the table and column name.

SICSR-30293_AUTOM.BOOKED.docx

Problem:

The database view V_DTL_LIQUID_UNSETTLED is not producing intervals as it should because date minus another date does not work in SQL server database.

Solution:

The database view V_DTL_LIQUID_UNSETTLED needs to be altered as per the script given in the attachment below.

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:

Issue updating user-defined fields for intermediary participation in 24.1 universe

Solution:

Include the OIP (intermediary placement) level in all 10 views under Business Information-User-Defined Conditions.

Attaching the document of the  view V_UDD_BUSINESS_L1, which includes OIP as well

Like for other views, we can include OIP

 UDD 1.txt

Problem:

Need to make Premium Basis object reportable in PC Main universe.

Solution:

Add an object, Premium Basis Type under the folder Business Information>Limit & Premium conditions>Premium Information>SUPI.

Object definition:

LPC_LIM_PREM_COND.FRK_REF_PREM_TYPE

Problem:

 Merge the two booking year periods and the booking year period-local-latest in the PC Main Universe,merging a dimension and a measure is not possible.

Solution:

Need to change this Booking year period-local-latest object from Measure to a dimension as we need to merge the two booking year period and booking year period latest.

Problem:

Missing attachment objects for worksheet, claim and headline loss in PC Main Universe.

Solution:

For headline loss(attachments):

• View: In the view V_CLAIMS_HEADLINE_LOSS, add a column for attachments as per the code given below. (Fetched from Oracle server)
  SELECT 
      SUBSTR(INV.path_and_filename, 1, INSTR(INV.path_and_filename, '', -1, 1)) AS file_path,
      SUBSTR(INV.path_and_filename, INSTR(INV.path_and_filename, '', -1, 1) + 1) AS file_name, 
      inv.description AS TITLE
  FROM 
      SICS4PC.CLAIMS CL
  JOIN 
      SICS4PC.DOC_INVENTORY INV
      ON cl.object_id = INV.attachedtooid
  WHERE 
      cl.claim_identifier = 'HL9009'; 
• Once we have inserted the column for it in the view, we can add an object for headline loss - attachments under Claims Information>Headline loss to make it reportable.

For CLAIM- ATTACHMENTS

We need to follow the same steps as headline loss.

Select DOC_INVENTORY. * from DOC_INVENTORY JOIN SOC_TO_CLAIM_REL ON SOC_TO_CLAIM_REL.object_id=attachedtooid JOIN CLAIMS ON CLAIMS.object_ID=SOC_TO_CLAIM_REL.FK_CLAIM where claim_identifier ='0000002296'

NOTE: INV needs to be another alias something like DOC_INVENTORY INV_HL so that it will separate out form the DOC_INVENTORY INV which is going for the claim
***

Problem: Few objects are missing in the partner Universe.

Solution: Need to create all the missing objects in the partner universe.

For few objects we need to create alias tables and create objects.

{}> Need to create folders Bank Visit Address and Bank Any Address under Bank details{}->Bank same as in Person.

-->Need to create Business Unit under Address–>Bank

Object definition: BUSINESS UNIT-ADDRESS.BUS_UNIT_NAME

--> need to create Bank Former Name & Bank Former Short Name under Bank.

Bank Former Name-SJ_Bank_FON.NAME

Bank Former Short Name-SJ_Bank_FON.SHORT_NAME

-->Also need to create Attachment folder under Bank same as in Business partners.

-->In Business partners need to create Included in Billing statements, Business Partner Former Name, Business Partner Former Short Name, Business Partner Alternative Short Name.

IS INCLUDEDE FROM BILLING STATEMENT-PARTY.IS_INCL_FROM_BILLS

Business Partner Former Name-SJ_BP_FON.NAME

Business Partner Former Short Name-SJ_BP_FON.SHORT_NAME 

Business Partner Alternative Short Name-SJ_BP_AON.SHORT_NAME

--> Need to create folders Claim Detailed Check & Tax on interest under Business Partner

--> Need to create Bank Account Type, Bank Account Task, Currency Conversion Account , Intermediary Account under Bank Account–>Business Partner

Bank Account Task-PARTY.ACCOUNT_TASK 

BANK ACCOUNT TYPE-BANK ACCOUNT.BNK_ACC_TYP

Currency Conversion Account-BANK_ACCOUNT.IS_BCCA

Intermediary Account-BANK_ACCOUNT.IS_IMD

--> Retention Date under Third Party

--->Objects for Person Middle Name, Age, Contact Person For under Person

Person Middle Name-PTY_Person_Derived.PERSONNAME_MN

-->Partner Address Identifier under Address–>Person

Partner Address Identifier-ADDRESS.ADDRESS_IDENTIFIER

--> Also need to create objects IS Active/Is Main Address/ Is Visit Address/Is Postal under Person. Business Partners & Bank.

Problem:

Missing attachment objects for countries in Ref Data Universe.

Solution:

Add an object for attachment for countries in Ref Data universe.

As per the example I have recreated, the SQL query for it is:

select * from 
DOC_INVENTORY DI
JOIN LEGAL_AREA LA
ON LA.OBJECT_ID = DI.ATTACHEDTOOID
WHERE LA.NAME = 'Switzerland'

The table for DOC_INVENTORY is already added at database level.

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:

Presence of a strange character in the database views V_AC_LEDGER_BALANCE and V_BOAC_PC_FACT.

Solution:

• Remove space from line '(concat(AC_LEDGEconcatR_BALANCE.AC_YEAR,'A '),REF_ACCPeriod.NAME) AS ACCOUNTING_YEAR_PERIOD,' in the view V_AC_LEDGER_BALANCE, and retype it in eclipse.
• Remove space from the line 'CONCAT(CONCAT(BOAC_DIM_TIME.AC_YEAR,' '),BOAC_DIM_TIME.NAME_AC_REF_PERIOD) AS ACCOUNTING_YEAR_PERIOD,' in the view V_BOAC_PC_FACT and retype it in eclipse.
  It is a simple mistyping issue, can be resolved by editing the line in Eclipse IDE and typing it manually.
  CC: Genji Srinivasarao & Manikandan Venkatasen 

Problem: Parameter name change for the procedure and additional information to the documentation.

Solution:

• Need to change the parameter name for the procedure BO_REPUNIT from Log level to Reporting level Hierarchy depth to make it is easy for the customer to understand.
• Need to adjust the create statement for the view V_REPUNIT from create view to create or alter view to avoid any error while creating the views from SICS Admin when the view is already existed in the database.
• Need to update the documentation of the Reporting Units with all the latest information including Procedure BO_REP_UNIT.

Problem:

Parsing error with EXTENTED_PAYMENT_DATE_BAL - ORA-00911

Solution:

 The strange character NBSP can simply be removed by retyping the highlighted line in bold in the given SQL below. 

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:

LOV's in the partner universe are wrong and should be corrected.

Solution:

Need to change the LOV'S SQL for the below mentioned objects.

• Rating 

SELECT DISTINCT
  Rating.NAME
FROM REFERENCE_DATA  Rating
RIGHT OUTER JOIN BP_RATING ON
BP_RATING.FRK_RATING=Rating.CODE AND 
BP_RATING.FSK_RATING=Rating.SUBCLASS
ORDER BY
1

• Rating System

SELECT DISTINCT
  REF_RatingSystem.NAME
FROM
  REFERENCE_DATA  REF_RatingSystem
RIGHT OUTER JOIN BP_RATING ON
BP_RATING.FRK_RATING_SYSTEM=REF_RatingSystem.CODE AND 
BP_RATING.FSK_RATING_SYSTEM=REF_RatingSystem.SUBCLASS
ORDER BY
1

Problem:

Calculated issue for the object Current share, which is coming from V_Reporting_Table.

Solution:

Need to adjust the definition to the object Current_share.

SQL:coalesce(V_REPORTING_TABLE.CURRENT_SHARE,0.00)

Problem: Changes are required for the join conditions and object definitions in PC Main Universe.

Solution: 

1.Need to adjust the Join Conditions for few joins as suggested.

2.Need to adjust the view script of V_REPORTING_TABLE to get exchange rate joins parse with out any error.

3. Need to rename the derived table V_BOAC_STL_PAIRING1 to V_BOAC_STL_PAIRING

4. Need to update the object definition for few Pairing Timeline Objects & Support objects.

Problem: BOAC005_PAIRING XML script is missing in the SICS SYSADMIN.

Solution: Need to add XML File for the procedure BOAC005_PAIRING in the SQL Script manager and also need to update the documentation with the newly added procedure information in all the required places.

Problem:

Solution:

Declination Reason:

Workaround:

Root Cause:

Extent of Impact:

Impact on Existing Data

Recovery Method for Existing Data Affected

Problem:

Exchange rate join issue for B30 and T30 tables .

Solution:

 We need to do an adjustment to the database view V_REPORTING_TABLE for exchange rate conversations and join changes to the exchange rate Join B30 and T30.

Problem:
Wrong universe join in the PC Main Universe Related to Triangulation Objects.

Solution:
The Join for the Triangulation Objects in the PC Main Universe should be corrected as BOAC_DIM_TRIG_EC.CODE=V_BOAC_PC_FACT.ENTRY_CODE.

Problem:

Users do not like the development and functionality of viewing the numbers per booking year period.

Solution:

We simply need to include this in a text field. Clients, upgrade teams, and DXC consultants will find this useful in determining which section of the derived tables above to modify in response to user inquiries.

Problem:

Balance Type (Code) not working on Balance level in SICS 24.3 for PC Main Universe.

Solution:

*Need to adjust the definition for the object Balance Type (code)

@Aggregate_aware(V_BOAC_PC_FACT.FRK_BALANCE_TYPE,V_AC_LEDGER_BALANCE.FRK_BALANCE_TYPE)

Problem:

Origin of worksheet (code) object is now placed under the object balance object ID in PC Main universe.

Solution:

Drag and drop the object Origin of worksheet (Code) from Balance Object ID to Origin of Worksheet in PC Main universe.

Problem:

Missing joins in the PC Main Universe 24.3

Solution:

We need to add these missing joins in the PC Main Universe.

*REF_IBNR_MTD3.CODE=V_UW_EST.FRK_IBNR_MTD AND REF_IBNR_MTD3.SUBCLASS=V_UW_EST.FSK_IBNR_MTD
*REF_IBNR_MTD22.CODE=V_UW_EST.FRK_IBNR_MTD2 AND REF_IBNR_MTD22.SUBCLASS=V_UW_EST.FSK_IBNR_MTD2
*LD_PATTERN2.OBJECT_ID=V_UW_EST.FK_LD_PATTERN
*LD_PATTERN_Paid3.OBJECT_ID=V_UW_EST.FK_LD_PATTERN_PAID
*LD_PATTERN_Paid22.OBJECT_ID=V_UW_EST.FK_LD_PATTERN_PAID_2
*MODEL_SECT2.OBJECT_ID=V_UW_EST.FK_MODEL_SECT
*CNU_NOTE_UW_EST.OBJECT_ID=V_UW_EST.FK_ESTIMATE_NOTE
*REF_UW_Est_Type.SUBCLASS=V_UW_EST.FSK_ESTIMATE_TYPE and REF_UW_Est_Type.CODE=V_UW_EST.FRK_ESTIMATE_TYPE
*CNU_CURUWEst.ISO_ALPHA=V_UW_EST.FK_PER_CURR
*BUS_PER_SNL_EST_UW.FK_SNGL_EST=V_UW_EST.BUS_PERIOD_EST_OBJECT_ID

*V_UW_EST.FK_SOC=V_REPORTING_TABLE.FK_SOC

Problem:
Object definition of the objects Detail Amount Unsettled (Base), Detail Amount Settled (Base) are defined wrongly in PC Main Universe.

Solution:
Need to change the object definition for the objects Detail Amount Unsettled(Base) and Detail Amount Settled (Base) from DETAIL_BALANCE to instead come from V_DETAIL_BALANCE.

Problem:
Object 'OIP / ORP Current Share PCT' is not working as expected. It is creating a cartesian product.

Solution:
Need to alter the SQL of the object 'OIP/ORP Current Share PCT' in PC Main Universe.

Problem: 

Reports are not showing proper premium values for OCC businesses.

Solution:

In PC Main universe, we need to point existing tables joins to V_REPORTING_TABLE.FK_SOC to avoid multiple rows. ** 

Root Cause:

In BO_PREM_CURR table we are getting multiple FK_SOC values for business.

Problem:

Solution:

Declination Reason:

Workaround:

Root Cause:

Extent of Impact:

Impact on Existing Data

Recovery Method for Existing Data Affected

Problem:
The base companies listed in the drop down of Current Base Company are sorted in the same order as they were selected as allowed base companies.  

Solution:
Sorting of base companies in the drop down of Current Base Company should be sorted alphabetically. This should happen also the first time selecting a Current Base Company.

Problem:

The use case Claim User Defined fields is incorrectly displayed with name 'Accounting Automatic Premium Update' when inspecting the properties.

Solution:

The name of the use case should be displayed as 'Claim User Defined Fields Update'

Problem:

Solution:

Declination Reason:

Workaround:

Root Cause:

Extent of Impact:

Impact on Existing Data

Recovery Method for Existing Data Affected

Problem:
When by Web Service trying to retrieve the value of the following field 'Reinsurer to Assumed Other Reinsurer Shares' in the Cancelation Conditions / Special Termination Clause, the system does not show its recorded value.

Solution:
When by Web Service trying to retrieve the value of the following fields in the Cancelation Conditions / Special Termination Clause, the system should show their recorded value:
-Reinsurer to Assumed Other Reinsurer Share
-Return of Res and/IBNR
-Return of Unearned Premium
Each of these fields can have one out of the following 3 values: Yes, No, and Not Specified. The system should retrieve the recorded value.

Problem:   
At some places specified properties being generated as data member and some of them with suffix '1' ,

Solution: 
This will be fixed during the generation of the client, 

Problem:

General Ledger Balance Revaluation walkback

Solution:

When a General Ledger Balance Revaluation is started from the SICS Admin Utility under Outbound functionality, then system will check if for all the primary currencies the exchange rates have been defined or not for the Booking Year and Period. If they are defined, then system will fetch all the balances which were transferred to the GL according to the selection criteria given on the GL Balance revaluation and will insert these details to the GL_BALANCE table. If the exchange rates are not defined, then system will raise an error to first define the missing exchange rates for all the primary currencies.

Problem:

ADH is throwing NullPointerException, while transforming an input document.

java.lang.NullPointerException: Cannot invoke 'com.csc.sics.adh.transform.SicsADHXmlTransformer$SubDocument.subDocumentNumber()' because 'this.currentSubDocument' is null     at com.csc.sics.adh.transform.SicsADHXmlTransformer.subDocumentNumber(SicsADHXmlTransformer.java:785) ~[?:?]     at com.csc.sics.adh.transform.SicsADHXmlTransformer.hookEnrichProblemDetails(SicsADHXmlTransformer.java:791) ~[?:?]     at com.csc.sics.adh.transform.SicsADHAbstractTransformer.recordNewTransformationProblem(SicsADHAbstractTransformer.java:1074) ~[?:?]

Solution:

A null check should be added to avoid use of currentSubDocument variable, before it has been used.

Workaround:

Quick Fix:

In the input data there is typo error in an element i.e. it should be <_dateOfLoss>01/Oct/1992</_dateOfLoss> instead of <_dateOfLoss>O1/Oct/1992</_dateOfLoss>
That means it should be 0 (Zero) not O (O for Orange).
 
So, please do the changes in input document, after this change document transformation is processing ahead.

Root Cause:

ADH abends while displaying proper error message:

        Error evaluating block 'Time Format': Unparseable date: 'O1/Oct/1992' 

It is trying to call value for currentSubDocument variable, before it has been assigned, which causes NullPointerException.

Problem:  Issue with Period Estimates when an Estimate item is mapped to different calculation rules in OCC/ORP level.  The expected amounts are not fetched from ORP level when the period estimation rule is limited to ORP level only.

Solution:

There is one more add-on to the existing solution from SICSR-28262. We will make sure, SICS do the calculation as per the exiting solution and it should also work when single Estimatation Item name is used for both level of business i.e., OCC and ORP. only the changes is different calculation rule. Period Estimation rule will retrive the figures as per their selections.

Existing solution (SICSR-28262)

When Period Estimation rule having a selection of 'Calculation on Retrocessionaire', we make sure system should do the calculation on ORP level as per their 'our share amounts' for all type variable (example Deposit Premium, Minimum Premium, Premium amount and Flat premium)  and if it's not selected then value should retrieve from the OCC as per their ORP shares even though share within more than 2 decimal places. It should work from both the places (Manually and from the Recalculation Order).

Problem:
An abend occurred while importing files using the SQL Script Manager.

Solution:
Resolve the abend during the file import process and restore the functionality to its previous working state.

Verification:

Step1: Log in to the System Administration Utility.
Step2: Select SQL Script Manager and attempt to import the file.

Additional Information
We are installing SICS 24.3 (4.24.3.4243ia) on a new server for the customer Stonefort.

Database is SQL Server 2022 (Microsoft SQL Server 2022 (RTM) - 16.0.1000.6 (X64)  (Build 20348: ) (Hypervisor) and Operating system is Windows 2022 (Windows Server 2022 Standard 10.0 <X64>).

After having upgraded the DB and SICS from a previous version, I generated and executed the scripts for BO reporting (with method B)

and then generated the XML files for BOACs

But as soon as I try to import the XML from Import Script tab, SICS crash. Attached here you can find some walkback files generated.

I also tried to use a custom script used for Consistency Script (that works for other customers) but got the same result.

Can you, please, check what is the issue?

Regards

   Luigi

Problem:

Entry code context was not detected automatically.

Solution:

The join between BOAC_DIM_ENTRY_CODE and ENTRY_CODE has to be one to many, and the join expression also has to be modified.

BOAC_DIM_ENTRY_CODE.CODE=ENTRY_CODE.CODE

*After making these changes, the context will automatically detect.

Problem:

Editing Retroceded Percent to Outward Cedent's Contract by Web Service does not trigger correction bookings

Solution:

When an IAB is protected with multiple Outward Cedent Contracts and the share percent is updated through webserver for one or more OCCs after the bookings are made, then system should consider the AC0258 message for automatically creating the adjustment bookings according to the new share percentage as of how it is functioning from the SICS UI when the share % is changed.

Problem
When taking a screen shot using the 'Hardcopy' menu, the menu bar item selected is included in the screen shot which may be hiding something intended to be in the screen shot.

Solution
Introduce a slight delay to allow Windows to fade out the menu item before taking the screenshot.

Aim of function:

Must be possible to give the Final Year End Calculation Frequency information on the Stepped Sliding Scale Commission conditions for a business in Web Services createDeductionCondition and updateDeductionConditions.

Business value for customers:

When creating and updating Deduction Conditions via Web Services in SICS this enhancement will avoid the user to manually update the Final Year End Calculation Frequency information on the SSSC conditions afterwards.

System Parameters Affected:

N/A

Existing functionality affected:

Webservices :
createDeductionCondition,
updateDeductionCondition,
createProfitCommissionCondition,
updateProfitCommissionCondition,
retrieveObject

Aim of function

The aim of this enhancement is to have an option to indicate on the business/insured period that all TechAccount messages processed on this insured period shall be interrupted by a warning if it contains loss related details, if this option is selected.

Business value for customers

As it is now any eMessage which contains a loss movement and/or outstanding reserve related to a Proportional contract is stopped (message indicator is off for all proportional contracts). The value of this enhancement is to minimize the amount of insured periods we have the message indicator off, because there is no need to process a headline loss on every proportional insured period.

With this new option activated on the Insured Period tab on the Business the TechAccount messages processed on this IP shall never trigger the rule CheckTAHeadlineLossProcessing 
BUT
if the new option is activated the TechAccount messages processed on this IP shall trigger the above rule if the message contains Non-Zero Original Loss Reserves or Paid Loss entries. When the rule is triggered the system will check if the aggregated Original Loss Reserves or Paid Loss on the business ledger in the same currency is Zero or not, and if not it will raise an Error. The error can be overruled.

This will ensure that the users becomes aware of this and take the necessary actions related to Headline Loss split and allocation when this is necessary. 

System Parameters Affected
N/A

Existing functionality affected

The eMessaging Information page on the Insured Period tab on the business will have a new flag named e.g. Headline Loss Processing

When the flag is selected it will affect the processing of TechAccounts eMessages

Aim of function
To enhance the 'Use Selected Value to Populate' function on the Technical worksheet, which allows users to apply a selected value from one row to other rows in the same column. This functionality should be extended to the 'Entry Code' column as well.
 
Business value for customers
Makes it easier to copy the Entry Code from one row to another row. 
 
System Parameters Affected
None
 
Existing functionality affected
Automatic population of Values on Technical Worksheet.

Aim of Function:

Add Accounting Year/Period information in the ‘Balance Summary per Currency’ container within the Business Partner Ledger to enable the splitting of balances based on Accounting Year/Period.

Business value to customers:

Including Accounting Year/Period information in the ‘Balance Summary per Currency’ container allows users to better manage and control larger cedent accounts that settle across multiple accounting periods. This feature enhances visibility and precision in financial reporting, enabling users to quickly assess and manage credit controls. 

System Parameters Affected:

None
 
Existing functionality affected:

Balance Summary per Currency under Business Partner ledger.

Aim of Function
The column Estimated in the Balances container should also be shown in the Details container on the Business Ledger.

Business value to customers
When multiple balances are highlighted and selected in the Balance container, and these are both estimates and actual balances, then there will also be a combination of estimates and actual details in the Details container. By showing the Estimated flag also on these details will give additional information to the user.

System Parameters Affected

None

Existing functionality affected

View Business Ledger Details Container

Aim of Function
Add a Legal Reporting Unit column in the Balance Group Information tab and display the Legal Reporting Unit in the Create Settlement Balance Group and View Settlement Balance Group window, like how it is displayed for balances in the Business Partner Ledger. 

Business value to customers
By adding the Legal Reporting Unit column in the Balance Group Information tab and ensuring the Legal Reporting Unit is displayed when a Settlement Balance Group is created or inspected, users can quickly pinpoint errors and confirm that the correct Legal Reporting Units are used. This will reduce the time and effort spent on troubleshooting validation errors and improve the overall accuracy of financial reporting. 

System Parameters Affected

A system parameter named 'Balance Pairing “Balance Grouping across Base Company/ Legal reporting Units not allowed', is found under accounting>>Balance Pairing.

Existing functionality affected

Create and Edit Settlement Balance Groups

Aim of function:

To make it possible to auto update the Withdrawal of the Collateral categories Letter of Credit, Trust and Funds Held on the Business Partner properties, based on payment of losses by use of special Remittance type “Collateral Withdrawal”, and make it possible to report these changes.​

Business value to customers:

If there are any recoveries be needed from the non-admitted reinsurer, draws against the LOC balance for actual paid loss or paid LAE balances, they can be made by the ceding company, reducing the business partner-level balance of the LOC. 

System Parameters affected:

None

Existing functionality
View and Edit Business Partner Properties
Remittances 

Aim of function:
To enhance the calculation of Computed amount for Deposit Retained Validation such that no retained funds are overlooked, even if there were residual amounts from previous periods. 

Business value to customers:
This enhancement enables clients to efficiently monitor their Premium/Loss Deposits Retained by accurately accumulating and tracking these amounts, clients can ensure that no retained funds are overlooked, even if there were residual amounts from previous periods.  

System Parameters Affected:

N/A

Existing functionality affected:

The Computed Value for the Deposits Retained associated with the Accuracy Validation.

Aim of function

To ease the registration of insurable objects, it is now possible to upload them from an external file. The excel sheet must contain the Insurable Object Type (e.g. Building, Vessel) and Object Name. In addition, it can contain all items that the current online Create Multiple Objects can contain, (e.g. Object Country, Address, Latitude Degrees, Market Value). The objects are loaded to the current Create Multiple Objects feature and once uploaded here, the user can make further additions and modifications before saving. 

Business value for customers

The numbers of insurable objects a user must record is often high. The upload feature increases the efficiency in recording these and therefore reduces cost. Also, reducing entries of insurable object data by end users may increase the data quality.  

System Parameters Affected

None

Existing functionality affected

Handle Insurable Objects
Cover Insurable Object
Handle Insured Object Cessions

Aim of function
Support for Losses Discovered Claim basis, ensuring that the Loss Discovery date is within insured period and the date of loss is equal to or after the retroactive date.

Business value for customers
This enhancement will ensure that claims are validated correctly for Losses Discovered basis. Date of Loss reflecting the Incident Occurrence Date can be recorded after the Retroactive Date (made mandatory for Losses Discovered claim basis) and before the Claim Trigger date (date of Discovery of Loss).

System Parameters Affected
None

Existing functionality affected
Maintain Claim condition
Create Claims
Process New claim Claim Movement messages

Aim of function
Add support for indexation calculation method margin/franchise of payments and reserves.
Indexation will only take place when the retrieved index is exceeding the Contractual Base index + Margin% of Contractual Base Index.
The system will calculate separate index ratios for payments and for incurred, and the distribution will be determined using these indexed limits.

Business value for customers
This enhancement will further complete the automatic index functionality for Assumed Claims, and enable customers to use the automated calculation instead of external applications.

System Parameters Affected
None

Existing functionality affected
Claim FGU Handling

Aim of function
Default the Claim manager to the user defined as Claims Handler on the Insured Period, instead of the user who creates the claim

Business value for customers
Although the Claims Handler responsibility can be defined on the Business Insured Period, the Claims manager on the Claim is not defaulted. This enhancement shall ensure that the Claim Manager is in alignment with the Business insured period information as much as possible, and reduce the need for manual updates.

System Parameters Affected
New parameter introduced 'Default Claim Manager from Insured Period Claim Handler

Existing functionality affected
Create Claims
Process New claim Claim Movement messages

Aim of function
To introduce a new eMessaging rule 'AssignClaimToClaimsProgram' to link new claims to the appropriate claim program automatically and when using “Swap to” then display only the matching claim programs.

Business value for customers

• Automatic linking of new claims to claim program when all necessary data is available.
• Streamlining the process to eliminate manual identification of the claim program.

System Parameters affected
N/A

Existing functionality affected

• eMessage Processing
• Swap To Claim

Aim of function

To introduce a new field for claim Bureau Signing Reference in eMessaging find window.

Business value for customers

Can search for matching claim messages on Bureau Signing reference.

System Parameters Affected

N/A

Existing functionality affected

eMessaging find window - Claim Tab

Aim of function

To keep the link to the Insured period on discarded messages.

Business value for customers

• Business details are retained on discarded messages.
• Can know what business has caused the errors in the problems tab.

System Parameters Affected

N/A

Existing functionality affected

Insured period references

Aim of function

To enable a scroll-through option for related emessages on the insured period.

Business value for customers

Can navigate to other related messages of the insured period.

System Parameters Affected

N/A

Existing functionality affected

Insured period - Related messages - View eMessage

Aim of function

To introduce a new eMessaging rule ComparePartialPremiumToNetInstalmentPremium to check for partial amounts of an instalment and to book message amount.

Business value for customers

• Can be able to check for partial instalment amounts. 

• Can be able to book the message amounts for instalments. 

• Can be able to reverse the fully booked instalments. 

System Parameters Affected

N/A

Existing functionality affected

Booking of partial amounts by eMessage.

Fully booked(manual) instalments on P/L Condition.

Aim of function
Change request to enhance the view of instalments drop down menu within eMessage.

Business value for customers
Enrich the view to offer more information from SICS P/L Tab and thus make the choice of correct instalment easier for the user on eMessage.

System Parameters Affected
N/A

Existing functionality affected
eMessage Highlights edit window

Aim of function

We have copied the SOAP examples from the old Word documentation into SICS Docs as get closer to our goal of eliminating the Word documentation.

Business value for customers

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

System Parameters Affected

None

Existing functionality affected

None

Aim of function
Ensure all options for updating a database are included in the database maintenance launcher so we can headlessly update a DB via code.
Added in this release:

• -buildTables
• -buildViews
• -addDefinedIndexes
• -addForeignKeyIndexes
• -addConstraints
• -addComments
• -dropTables
• -dropViews
• -dropIndexes
• -dropConstraints

This is essential for a SaaS environment.

Business value for customers
Fully automated database maintenance operations

System Parameters Affected
N/A
Existing functionality affected
N/A