Release documentation - Cede - Enhancements and requests

Problem:

In Lloyds Outward messages, while automatic referencing the insured period the system first check for OCC and then OIP (intermediary placement) and ORP. Whereas in case of manual referencing system prompts to assign OIP first.

The client expects to follow the same flow as in the case of manual referencing.

Solution:

LorsIPReferenceRule

The below sequence is followed while searching for correct insured period.

Unique Market Reference
Receiver Reference
Sender Business Partner Reference
Receiver Business Partner Reference
Former Business ID
Insured Period Former ID
Original Former ID

When searching on each reference, look for OIP first and then move to OCC or ORP.

Problem:

In the eMessaging search option there is a column for Service Provider Reference and the field captures the service provider reference from the message. It was working fine in 20.4 but not in 23.2 version. Please refer to the screen shot.

Solution:

For a Lloyds Outwards Signing TechAccount message having a message header ServiceProviderReference then that reference should be shown irrespective of there not actually being a ServiceProvider specified in the message.

Problem:

While processing LIMRIA messages, user is allowed to reject sub account items. While rejecting the items, system abends. This happening in current as well as old version.

Solution:

For messages of type LloydsOutwards the Reject Selected Item(s) should not be on the menu for Message or Subaccount items. This is for ACORD Settlement messages only.

Workaround:

Do not click on menu item for / try to Reject Selected Item(s) on the LORS messages.
Authorize / Object is performed by edit at message level.

Problem:
System Administrator's Guide does not specify, in detail, the process of making perils available for a given risk zone.

Solution:
Description has been added in the System Administration Guide, under Reference Data / Maintain Insurable Perils.

Problem: 

There is slow performance for exchange rate conversion in Cede universe.

Solution: 

1. The views V_BUS_EXCHANGE_RATE and V_ENTRY_CODES need to be altered as requested.

2. Also. in support class, there is a need to change the SQL of the two exchange rate objects i.e., Base Exchange rate and Target exchange rate.

3. The Cede Exchange rate parameters are defined wrongly and needs to be changed.

Problem:

Getting abend when clicking on the Generate Reporting Tables Scripts tab in SICS SysAdmin - MySQL

Solution:

 Need to fix it in the SICS java end to access the 'Generate Reporting Tables Scripts' tab.

Problem: 

Slow performance issue for exchange rate conversion in Cede universe.

Solution: 

1. The views V_BUS_EXCHANGE_RATE and V_ENTRY_CODES need to be altered as requested.

2. Also. in support class, there is a need to change the SQL of the two exchange rate objects i.e., Base Exchange rate and Target exchange rate.

3. The Cede Exchange rate parameters are defined wrongly and needs to be changed.

Problem:
The view V_ORP_DATES is being used by the two universes. However, depending on if it is a Cede or PC Main database the view is defined slightly differently.

Solution:
Need to change the query for the View with the latest one mentioned in the comment section for both databases.

Problem:

Policy Light Insurable Objects reporting via Cede Universe.

Solution:

Create an insurable class in Cede universe and add all the objects which are related to IO.

We need to add an IO table to the structure and this structure will cover most of the missing objects in the Cede universe in regard to the IO information.

Problem:

Description is not available for the objects of Class  'User Custom Objects' in SICS CEDE Universe

 Solution:

Add the following description to all of the objects in the user custom objects

Former Class: User Custom Objects

Former Name: Object1008 (this will obviously change for each object so it matches the current name)

Problem:

There are no development objects in the Cede universe which would allow us to make retrofit development into a customers universe allowing for the reports to smoothly upgrade when they upgrade to a new version of the universe.

Solution:

These types of objects in the PC Main universe so it would be good to add a number into the Cede universe as well.

Can you please add a number of them in to the Cede universe, and do not forget to add the description so it will be easy to identify when they are being used?

Problem:

The default arguments for stored procedure BO_DIM_DATE on an Oracle database cannot be used as it is giving error 'ORA-1483 (“not a valid month”) occurs when running “exec BO_DIM_DATE();”.'.

Solution:

Date values should never ever be provided as strings only without a format string. Type casting is required, e.g.: to date(‘01/01/1980’, ‘mm/dd/yyyy’).

Problem:

The name fields (e.g. DAY_NAME) in table DIMDATE are too small for non-english language settings like “Slovenian” in Oracle sqldeveloper. ORA-12899 (“value too large”) occurs in this case.

Solution:

Need to extend the size of all columns in this table so that they can hold data for all languages.

Problem

SICS abends when you click the Show More History button in the Scheduler History view.

Solution

SICS should not abend when you click the Show More History button in the Scheduler History view.

Problem:
It is not possible to flag e.g. a cedent as a fronting company when establishing or updating <BusinessPartnerRelationship> by web service.

Solution:
To be able to flag e.g. a cedent as a fronting company by web service, we need a new element <isFrontingCompany> Yes/No in <businessPartnerRelationship> and <updateBusinessPartnerRelationship>

Problem:

Event log participants for database update incorrectly excluded by default

Solution:

If a participant class is not present in the database, it should be included by default.

Workaround:

Manually edit the event log participant inclusions for database update in System Administration Utility -> System Administration -> Event Log -> Setup

Problem:

Light Policy shows Class of Business in square brackets

Solution:

Class of business should be shown without square bracket for Policy Light, it should be shown without - as it is for the other classification items

Root Cause:

SE-17413 / SICSR-25510

Problem:
When running the Cede Interface Order, all lines fail to be processed in the same run.

Solution:
Make sure all lines in the Cede Interface Order are processed in the same run.
Solution in SE-17277 - done in SICS 23.1 appears to be the source of the error.

Root Cause:
SE-17277

Problem:

Performance degradation in domain object hashCode method

Solution:

Remove the domain object hashCode override and use the native hashCode method instead.

Problem:

The Drag & Drop functionality to create desktop toolbar shortcuts incorrectly opens an empty edit window

Solution:

The Drag & Drop functionality should automatically save the new shortcut to the database without opening an empty edit window first.

Aim of function
Improve Source Claim Bookings View for recoveries run via Protection Program, i.e. more than one layer run in same order.
The list is accumulated per Inward Business, Claim, Currency and Accounting Classification
and is based on NONPROP_REC_DETAIL table.
It also shows the distribution at OCC Claim at accumulated level

Go to Protection Program XL part and select View Claims and View Protection Program figures, and this view is made available:

From here there is also a possibility to select to Export Source Claims for Protection Program. This creates a spreadsheet with inward claim details

Business value for customer
New improved view for recoveries run for Protection Program - available directly from Protection Program

System Parameters Affected
None

Existing functionality affected
Recovery Calculation for Protection Program