Release documentation - Cede - Enhancements and requests

Problem:
It is possible to Delete Reinstatement Condition providing warning about existing bookings is disregarded. When deleting the Reinstatement Condition it appears to be deleted, however a disabled Calculation Rule field = None is kept, and is not editable. This means that it is not possible to create a new Reinstatement Condition for the user.

Solution:
Do not allow deletion of Reinstatement Condition (for assumed and Outward Cedent's Contract) if there are existing Reinstatement Premium bookings for current Insured Period. This ensures that the Calculation Rule remains the same.
User could still edit number of reinstatement or payment rule to obtain required change and even set reinstatements to None - if required. This should still remain possible.
The two different Reinstatement choices Per Loss / Per Insured Period are not changeable, as these are calculations done at a different level (per Claim or Per Insured Period). Furthermore it is done respectively on Claim Worksheet or Technical Worksheet.

SQL to correct condition:
We will provide an SQL to be able to update the incorrectly deleted Reinstatement Condition. Please note that the Calculation Rule must be scripted to the the same as before deletion, to make sure the calculation of reinstatement will continue to work.

Problem: When copying from a Job Template of type Calculation Group Order or Accounting Group Order from Accounting Order Monitor, the Actual job created has always activation = active regardless of the activation status of the template (e.g. On Call Only)

Solution: When executing Copy to Actual Job from Job Template for order type Account Group Order and Calculation Group Order, system should keep the same Activation of Pending Actual Job as the source Job Templates. The correction should work for the Copy to Actual Job from both System Administration/Scheduled Job and SICS workstation Desktop/Accounting Order Monitor.

Problem:
Recovery Calculation creates incorrect balance at business partner ledger, as it is showing one Claim ID when the details are actually split by more than one Claim ID.

Solution:
When running recovery calculation order bookings are created as Claim Worksheet at OCC level, and thereafter multiplied with placed share per retrocessionaire and booked as a technical worksheet.
When more than one OCC Claim, the balance at retrocessionaire level should not show one random OCC Claim ID for Retrocessionaire Placement, there must be one balance per OCC Claim

Workaround:
Balance could be split into details by using 'Split Balances into Details'

Problem: Chapter '13.15. Calculate Portfolio of Reserve' is present in SICS P&C user guide but not in SICS Cede's.

Solution:

Copy chapter 13.15 - Calculate Portfolio of Reserve from the P&C User's Guide into the Cede User's Guide between chapter 13.14 and 13.15, and renumbering to following chapter.

Problem:
Incorrect values in Cede User Guide Appendix for Recovery Calculation, 17. Recovery Calculation when Reinstatement Exhausted Drop

Solution:
Correct the values to be same as in P&C User Guide

Workaround:
Correct values in columns found in P&C User Guide, Appendix 19. Recovery Calculation when Reinstatement Exhausted Drop

Problem:
The list of vales for 'Policy Insurer ID' is fetching details for ALL the business partners like brokers, cedents, reinsurer etc. 

Solution:
The SQL for LOVs for 'policy insurer id' and 'policy insurer name' should be modified.

The modified SQL would look something like this:

'SELECT DISTINCT
  PartnerIDLOV.IDENTIFIER,
  PartnerNameLOV.NAME
FROM
  PARTY_IDENTIFIER  PartnerIDLOV 
INNER JOIN PARTY  PTY_PartnerLOV ON (PTY_PartnerLOV.OBJECT_ID=PartnerIDLOV.FK_PARTY)
INNER JOIN ORGANISATION_NAME  PartnerNameLOV ON (PTY_PartnerLOV.OBJECT_ID=PartnerNameLOV.FK_ORGANISATION)
INNER JOIN BUS_PARTNER_CAT BP_Category ON BP_Category.FK_PARTNER = PTY_PartnerLOV.OBJECT_ID  
WHERE
  ( PartnerNameLOV.SUBCLASS=3  )
  AND  ( PartnerIDLOV.FRK_PARTY_ID_TYPE='BPID'  )
  AND  ( PTY_PartnerLOV.IS_ACTIVE='Y'  )
  AND  ( PTY_PartnerLOV.IS_BUS_PARTNER = 'Y'  )
  AND  ( BP_CATEGORY.FRK_CATEGORY = 'I'  )
ORDER BY
  1'

For policy insurer name we should make the same changes so that it reflects only the insurer name and not all the partner details.

Similarly, the SQL for LOVs of 'policy insured id' and 'policy insured name' should be changed.

SELECT DISTINCT
  PartnerIDLOV.IDENTIFIER,
  PartnerNameLOV.NAME
FROM
  PARTY_IDENTIFIER  PartnerIDLOV 
INNER JOIN PARTY  PTY_PartnerLOV ON (PTY_PartnerLOV.OBJECT_ID=PartnerIDLOV.FK_PARTY)
INNER JOIN ORGANISATION_NAME  PartnerNameLOV ON (PTY_PartnerLOV.OBJECT_ID=PartnerNameLOV.FK_ORGANISATION)
INNER JOIN BUS_PARTNER_CAT BP_Category ON BP_Category.FK_PARTNER = PTY_PartnerLOV.OBJECT_ID  
WHERE
  ( PartnerNameLOV.SUBCLASS=3  )
  AND  ( PartnerIDLOV.FRK_PARTY_ID_TYPE='BPID'  )
  AND  ( PTY_PartnerLOV.IS_ACTIVE='Y'  )
  AND  ( PTY_PartnerLOV.IS_BUS_PARTNER = 'Y'  )
  AND  ( BP_CATEGORY.FRK_CATEGORY = 'IN'  )
ORDER BY
  1

Problem:
DISTINCTLIST should not appear in the list of Stored Functions.

Solution:

 Need to remove this DISTINCTLIST function from all databases in sics.

Problem: Few objects are not showing correct values, They are showing all the values under Reference Data Table.

Solution: Need to adjust LOV SQL for the objects to limit the LOV Values to show relevant reference data.

Problem:

Missing space between first name and last name in the Lovs for the objects Business Partner Created By, Business Partner Updated By at Universe level.

Solution:

Change the SQL of the Lovs for the objects Business Partner Created By and Business Partner Updated By.

Business Partner Created By:

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

Business Partner Updated By:

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

Problem:

Insurer Full name object is not present in Cede Light Universe.

Solution:

We need to add the Insurer Full name object in the Cede Light  Universe under Policy folder.

Object Name: Policy Insurer Full Name
sql: SJ_LightInsurer_CON.FULL_NAME

Problem:

Objects Legal Area(code) and Legal area(all) are missing under policy classification in CEDE Light universe.

Solution:

Modify the object definition of Legal Area under policy >policy properties>classification.

Next add the object Legal Area(code) like it is under the class accounting information.

After that add another object named legal Area(all) under policy >policy properties>classification(all).

Problem:

Changes to System Parameter 'Status Authorized not available for Write Off Remittance' is not stored.

Solution:

When updating the system parameter 'Status Authorized not available for Write Off Remittance', either by swithing it On or Off and save it to the database, then the system must be able to store the new value.

Root Cause:

In version 23.4 we split the system parameter Remittance (under Accounting) into two pages, Remittance Properties and Remittance Validation. During this split something went wrong with the above parameter

Problem:
System abends when Creation TS and Import TS is given in the Cede Excel Loader P&C.

Solution:
Generally, the Excel Loader solution should have a few required validations for the imported file, to avoid crash. This must be limited to the fields which are required for starting the loader and creating the Cede Interface record (see below for examples), and it should not include validations which are done on the business fields (like the classification items, Insured period, booking periods etc.)

The Import TS and the Creation TS field should not be necessary to fill in, as this will be done automatically by the system. If filled in incorrectly, it must be overwritten with current date and time.
This must be equally implemented for both P&C and Life Excel Loader

Workaround:
If you leave the Creation TS / Import TS fields empty - the field will be automatically updated, and no abend will occur.

Problem:
When removing Proportional Protection Assignment for a Light Policy, the deduction is duplicated at Prop Fac ORP

Solution:
When Light Policy is protected by a Prop Fac OCC, and protection assignment is removed, reversal of ORP figures must be as following:
Reversal of deductions must follow the original entry of deductions; i.e.

• if Entry Code Usage is defined for current deduction - the ORP reversal must be based on the same
• If Entry Code Usage is NOT defined for current ORP deduction - the ORP reversal must be based upon the ORP share of OCC deducdtion.

Workaround:
None

Problem:

System abends when searching for Policy from the SICS Desktop - when entering a Policy Light Identifier. When entering a Policy Ceded identifier - it opens the Policy Ceded correctly.

Solution:

Searching for Policy Light from the SICS desktop by selecting the Policy option, system should not abend but open the Policy Light. This should happen in the same way system opens the policy from Find Policy Light Business and Find Business.
It should still (as currently) open any Policy Ceded identifier which is searched for in the same field.

Problem:

When the Cede Interface Rule is set up with a value in 'Claim Incurred at least', all claim bookings (Type 2 and 4)  with negative sign (which is the 'normal' claim booking) are excluded from being processed

Solution:

When the Cede Interface Rule is set up with a value in 'Claim Incurred at least', the claim bookings on a new light claim must be validated against the value in 'Claim Incurred at least'. 

As the claim records are negative, the validation is against the negative amount. E.g. if the 'Claim Incurred at least' is 1.000, the system should validate that the incurred amount for the claim (for all included balances) is more than -1.000. This means it should be -1.000 or more, if it is f.ex. -900 it will not be processed.

Problem:

Cede Interface does not copy Additional Classification 12-18 values to new record

Solution:

When copying a record in Cede Interface all additonal classification, also 12-18 must be copied into the new record for Policy Light, Policy Claim, Policy Light Life and Policy Life Claim record.

Workaround:

Fill in the additional classification information in the copied record

Problem:
Abend when running Cede Interface Order via Distributed Processes if the order has already been run.

Solution:
Distributed Processes is not in use for Cede Interface anymore, and must therefore be removed as an option in the system.
Remove from reference data
Remove as a dropdown option.
Remove Cede Interface reference from System Administration Guide

Problem:

Policy Light assigned to Risk Unit Group is not listed as member

Solution:

When a Policy Light is assigned to a Risk Unit Group, the policy must be listed as Member in the group

Problem:

The system does Fac Netting at US Quota Share for each Policy Light (section) which is protected by the Non Prop Fac OCC, instead of doing it only for the first one.

Solution:

When Fac Netting for Policy Light, make sure the OCC Fac Protection is only netted once at US Quota Share per Non Prop Fac OCC. Depending on system parameter setting, the system should automatically generate informational bookings on the Policy, or directly on the US Quota Share only once per Non Prop Fac OCC / US Quota Share combination.

System parameter: Fac netting not booked on policy

Workaround:

None

Problem:

Missing Object in Cede Light SICS Universe 24.1.

Solution:

Need to add the missing object Policy Batch Name in the Cede universe 24.2.

Aim of function
Create Web Service for Add and Realize Proportional Fac OCC Protection for Policy Light, Assumed Fac, Direct Business and Policy Ceded

• Development; including XML
• Testing

Business value for customer
Prop Fac OCC could be defined and created via Web Service

System Parameters affected
N/A

Existing Functionality affected
Add and Realize Fac OCC Protection online

Aim of function:
Improvement of Domain Retrieval for Policy Light by including Reporting Units

Business value for customers
Access to the registered Reporting Unit for the light object via domain retrieval for web services: SicsPolicyLightBusinessReference

System Parameters Affected:
N/A
 
Existing functionality affected:
Domain Retrieval for Policy Light