Release documentation - Cede - Enhancements and requests

Problem:

Previous Sliding Scale Commission Percent should be that one effectively used to calculate commissions (occasionally the provisional) and not always the percentage from the scale.

Solution:

Display the commission percent (provisional or from scale) applied in the calculation as previous.

Workaround:

update INSURED_PERIOD.PREV_SSC_PCT = SS_COMMISSION.PROV_COMM_PCT

Extent of Impact:

Special Stepped Sliding Scale Commission in use

Problem:

Special Sliding Scale Commission uses wrong percent

Solution:

The system should not add the percent of other types of deduction with the provisional commission percent when calculation the provisional phase of special stepped sliding scale commission by running retrocession calculation order. 

Extent of Impact:

Special Stepped Sliding Scale Commission in use

Problem:

When two scheduled orders (child Retrocession Calculation orders orders attached to the same Group order) is run in scheduler there is an abend caused by intervening update. The abend happens when the two scheduled child orders are run in two different schedulers, finishing at the exact same time, and try to update their parent order simultaneously.

Solution:

Make sure child orders linked to Retrocession Group Order can be run in different schedulers even when it is finished at the same time, handling any updates sequentially to avoid abend.

Workaround:

Run in same scheduler

Root Cause:

SC-3275 - fix not complete for all scenarios

Problem:

Commission is multiplied if other deduction exists

Solution:

The system should not use a different commission percentage than given by conditions (provisional or as per scale) when special deductions apply for a retrocessionaire. 

Problem:

Retrocession Calculation Order does not inherit condition from group order

Solution:

The selection of  'Override Sliding Calc. Freq.' of individual Retrocession Calculation Order should be inherit from the Retrocession Calculation Order Group. It should be done in both SICS Cede and SICS P&C.

Problem:

The Prev SSC% value is incorrectly updated after running retro calculations order when special stepped sliding scale commission

Solution:

After having run a retro calculation in variable phase the system should update the Prev SSC % on the ORP inured period tab to the value applied in the REAC calculation, using Loss Ratio and Sliding Scale. The Loss Ratio should be calculated as accumulated losses (including current quarter/account) / (current cumulative premium -current Additional premium)

If system is applying the provisional rate in the calculation, the prev SSC % should be updated to reflect that.

Root Cause:

GUI clean up

Problem:

System abends when running PB order and Entry codes in REAC entry code assignment (SysPar/Accounting/Entry Codes) has not defined values for calculations belonging to Special Stepped Sliding Scale Commission.

Solution:

PB order and Retrocession Calculation / Account order shold not require the following values defined in REAC, unless  'Calculate Special Stepped Sliding Scale Comm.' is selected in Insured Period Tab / Individual options at Prop OCC level:

Adjustable Variable Commission, Variable Commission Reserve, Variable Commission Reserve 2, Variable Commission Reserve 3, Variable Commission Reserve 4, Adjustable Variable Commission Reserve

Workaround:

To avoid the abend, a definition of these fields will make sure the PB order runs without abend until a fix is available.

Problem: 

Bookings do not transfer from Prop Fac ORP IGC to IAB IGC when Placement Completed flag is set prior to Preliminary Booking order run.

Solution: 

The bookings should be transferred to the Intra group contract from the Fac OCC placement regardless when placement complete is set on the OCC, regardless of whether this happens prior to the the prelimniary order run, or after.

Problem:

The system fails to reverse cumulative premium reserve if booking is zero. 

Solution:

When Special Sliding Scale functionality is in use the system should automatically reverse the previous month's cumulative premium reserve balance

Problem: 

The loss ratio is incorrectly calculated when special stepped sliding scale commission.

The calculation is using accumulated losses correctly, but the premium is not considering the reversals of cumulative premium made in current worksheet.

Solution:

The system must include the premium and premium reversal bookings made in current worksheet when calculating the loss ratio.

Problem: 

System crashes when running Preliminary booking order and a claim reserve is booked at Policy Light where a Prop Fac Protection is protecting the Light Policy.

Solution:

When running PB Order and there is a OCC Prop Fac Protection, the system must retrocede to the Prop Fac Protection. As Booking/As Account bookings must be done at OCC and ORP level according to existing functionaliy.

Workaround:

Remove placement complete flag at OCC Fac Retrocessionaire before running PB order. This creates open WS. When setting placement complete and closing the WS, the system creates bookings correctly at OCC and ORP level.

Problem: 

The sliding scale commission entry code is removed when Retrocession Calculation order is run with closed worksheets

Solution:

The entry code must be present also on the closed worksheet

Problem

Only provisional rate is being applied in the calculation of sliding scale although scale should be used

Solution

When account is within the frequency of the calculation or this has been overridden on the order, the system should apply the commission from the scale, determined by the loss ratio

Problem:

In PostgreSql, SICS Scheduler cannot execute Stored Procedures when they contain a COMMIT statement.

Solution:

Remove Commit from BOAC scripts for Postgresql DB.

Problem:

In P&C & CEDE universe we have these two objects:

• Booking Period Start Date
• Booking Period End Date 

Both List of values return an odd looking date

20120101

20120701

20121001

20121201

etc. 

Solution:

To get the requested format, need to change the object definition at the universe level. Attaching the snapshots for your reference.

Problem:
Missing space between first name and last name Business Partner Created By, Business Partner Updated By.
Solution:
We need to adjust the SQL to something like this instead so that we have a concat(concat( …., ‘ ‘), …) statement
concat(concat(CNU_UpdatedBy.FIRSTNAME,' '),CNU_UpdatedBy.LASTNAME)

Problem: 

In the Cede universe we have not implemented the BOAC_JT_ECG table which is not allowing for extraction of entry code groups defined in entry code groups

Solution: 
The BOAC_JT_ECG table should be implemented in the Cede universe

Problem:
The Container managed database connection doesn't work with Postgresql.
Solution:
Improve the Source code to eliminate the conditional checks for each DBMS platforms to ensure the new platforms are handled correctly.
 

Problem:

Specified element methods not generated on .NET Core clients.

Solution:

Generate specified element methods on the .NET Core clients.

Problem:

Bookings from Ceded Premium Order are not picked up in Retrocession Calculation order, although figures are booked at As Original and Transformation Terms are created at Prop OCC.

Solution:

Retrocession Calculation order must pick up Ceded Premium bookings booked at As Original ledger. The Ceded Premium informational bookings must be considering Transformation Terms and As Booking amounts must be booked at OCC. Distribution to Retrocessionaires according to existing functionality

Workaround:

None

Problem:

Write locks when you run PB orders in parallel schedulers due that the same policy is included in 2 different jobs.

Solution:

 Remove version field update of Light:Policy when you run PB and PBC order.

Updates of accounting classifications etc. when orders are ending and consequentially tried updated at the same time - must be done sequentially.

Problem:

Solr client used in Operational Reporting and SICS Search does not automatically trust the certificates in the trust store

Solution:

The Solr client used in SICS Workstation and SICS Servers should while using Operational Reporting and/or SICS Search must automatically trust the pre-configured trust store.

Workaround:

Set the Java system property -Dsolr.http1=true when launching SICS Workstation/SysAdmin and/or SICS Servers.

Problem:

Customer is facing issue while trying to upload ADH document (xml) with Process on Load option (System Parameter > eMessaging > Processing Option > Process On Load). Getting the attached error.

Index 0 out of bounds for length 0

Solution:

The system should abend when importing a message via ADH with the DiscardDuplicateUniversalUniqueIdendifierValidationRule active and the Process on Load flag active.

Aim of function
Our goal is to enhance functionality by implementing Policy Light User Interface adjustments. These adjustments involve removing group boxes, improving field alignments, and enhancing the navigation bar. By doing so, we aim to create a more streamlined and user-friendly interface for our customers.

Business value for customers
1. Eliminating group boxes can make forms look cleaner and more streamlined, this can make forms easier to scan and understand, which can lead to fewer errors and a better user experience.
2. Improving field alignments can make forms look more professional and polished. This can create a more positive impression on customers, which can lead to increased trust and loyalty.
3. Improving navigation bars can make it easier for customers to find what they are looking for. This can lead to shorter customer journeys and improved customer satisfaction.

System Parameters Affected
n/a

Existing functionality affected
n/a

Aim of function
Improve Source Claim Bookings View – showing accumulated inward source bookings included for the current OCC Claim Booking As-of-Date
The list is accumulated per Inward Business, Claim, Currency and Accounting Classification (picture1)
and is based on NONPROP_REC_DETAIL table.
It also shows the distribution at OCC Claim at accumulated level (picture2).
The information is available for Non-Prop Treaty OCC, Non-Prop Fac OCC and US Quota Share

Business value for customer
New improved view available directly from OCC Claim list – showing inward source claims at an accumulated level

System Parameters Affected
None

Existing functionality affected
Recovery Calculation for Protection Program
Recovery Calculation for single OCC
Recovery Calculation for US Quota Share