Release documentation - Cede - Enhancements and requests

Problem:
Abend when editing Recovery Calculation Order for Protection Program when the removal of the old Program is not saved before selecting to add a new program.

Solution:
When editing a Recovery Calculation Order for Protection Program - it must be possible to remove and old Program ID and add a new Program ID without issues. This must be possible also when the new Program has a different base company; and when the Program goes from one to several base company and vice versa.

This functionality must be implemented for regular Recovery Calculation for Protection Program and also for Aggregate XL Recovery / Stop Loss Recovery for Protection Program.

Workaround:
Edit and remove the current Program and save without any Program, then as a next step; edit again and select to Add the new Program.

Problem:
Premium is not proportionally ceded in Preliminary Booking Order when Policy Light have bookings for same accounting classification which in total gives a zero amount.

Solution:
This must be resolved in Preliminary Booking Order by creating a zero balance for light bookings which accumulated are zero but comprises of a number of entries with same entry code and same accounting classification which has amounts with opposite signs which in total is zero.
Details which belong to this balance must be accumulated per sign, and the source details must be at Policy level.

Example where all details are the same Premium Entry Code and accounting classification (accumulation group level):
Policy Light 1: 100
Policy Light 2: 50
Policy Light 3: 75
Policy Light 3: -150
Policy Light 4: -75

This should be booked to As Original as:
Balance: 0,00
Detail1: 225
Detail2: -225

Detail1 will have source details: Policy Light 1: 100, Policy Light 2: 50, Policy Light 3: 75 (when selecting View source this is shown in View Associated Details GUI)
Detail2 will have source details: Policy Light 3: -150, Policy Light 4: -75 (when selecting View source this is shown in View Associated Details GUI).

When running REAC the same functionality as for Assumed business will be applied:
As Booking balance will be zero, As booking details will be zero.
No bookings will be done at ORP level

Workaround:
None

Problem:
When running Multi Business Protection Allocation order, and the 'Assign All Matching Protection Program Scopes of Cover for Claim PA Order' is selected, Light Claims are not assigned to business when selecting Save on Claim at order.
This is a mistake, as this system parameter should not have any affect on the Multi Business Protection Allocation Order. This was caused by SE-20510 solution in SICS 23.4.

Solution:
Make sure that the system parameter 'Assign All Matching Protection Program Scopes of Cover for Claim PA Order' does not have any effect on Multi Business Protection Allocation Order

Expected functionality for Multi Business Protection Allocation Order:
When selecting Save on Claim there should be a regular validation to find the correct Insured Period to assign to the Claim. The Protection Allocation should be assigned to the lowest matching protection in the Program hierarchy. Furthermore, the base company and classification of the Claim must be a sub-set of the Protection Program cedent / classification. For Claim basis: Losses Occurring = DOL inside / Risks Attaching = IP of Policy Light starting within OCC IP.

Workaround:
None

Root Cause:
SE-20510

Problem:
'Claim Advice Limit' and '% Excess Point' in Protection Program is not updated correctly.

Solution:
When creating Claim Advice Limit in Protection Program, XL Part, it must be handled the same way as it is at OCC level.
The percentage field must automatically update amount according to the existing Program retention at XL Part; i.e. - if the retention is 100.000 and the percentage is set to be 75%, the amount should be updated as 75.000 for the Protection Program. If there is no existing Program retention, no validation is possible.
If the Protection Program XL Part condition is inherited to the OCCs - the percentage should be used to show correct amount for the different OCCs (% multiplied with Excess for each of the OCCs).
If the inheritance is broken, the OCC condition should act independently, and according to existing functionality (no changes required).

Workaround: 
Make sure to only use overridden OCC conditions; i.e. not inherited from the Protection Program XL Part condition.

Problem:
Images not displayed in SICS Cede User Guide

Solution:
Correction of incorrect GUI links in two chapters of Cede User Guide

• Chapter 1.2.5 things to know before you begin: Headline 'Add an Object to the Bookmarks List' is missing the GUI related to Adding a folder
• Chapter 11.13 Mass Update Balances, Pairings and Worksheets: Headline: 'To change the responsibility of a Business Partner using the mass update function': invalid GUI reference - to be removed as it is redundant.

Workaround:
Available in SICS P&C User Guide

Problem:
Claim Creation Limit in System Parameters is not clearly marked as percentage and there is not validation that it cannot be more than 100%.

Solution:
Claim Creation Limit in System Parameters should be renamed to be: 'Claim Creation Limit %'
Validation to be implemented to not allow a percentage above 100%. This should give an error message: 'Percentage is not allowed above 100%'

Workaround: 
Use a percentage below 100.

Problem:
Recovery order for Protection Program does not finish calculating due to performance issues - resulting in a Java Heap Space error.

Solution:
When running Recovery Calculation order, add filter to the initial query to consider only those lightSocToClaim ids from protectionAllocation where lightSocToClaim id is not null

Workaround:
None

Problem:
When Processing addRealizeFacOccProtection via web service, a Facultative OCC gets created protecting Assumed Business or Policy Ceded Level of Business. The identifier of Fac OCC is not getting displayed in the Webservice response. 

Solution:
SICS Webservice should display the Fac OCC Identifier when processing the addRealizeFacOccProtection.

Workaround:
None

Problem:
When adding values to fields CLAIMANT and PC_INSURED_NAME to a Claim record in Cede Excel Loader P&C, the loaded records are appearing incorrectly in Pending; it is not populating the fields, and in some cases also missing the record Type.

Solution:
When loading Policy Light / Policy Light Life records via Cede Excel Loader P&C / Life all fields available for the different record types must be accepted and populating the records correctly - making a correct new pending booking record - ready to be run in Cede Interface Order.
CLAIMANT and PC_INSURED_NAME must be corrected, to ensure the values of the fields are included correctly.
In addition, we have to make sure that all other fields are making correct pending records to be included in a Cede Interface Order and thereby populating the Policy, Claim and light ledger correctly according to given input in all available fields.

Workaround:
None

Root Cause:
SE-11390 / SE-10710

Problem:
Multi Business Auto Protection Order is Not Processing All Records at Once

Solution:
System processes large amount of data in streams and tries to break it into batches to avoid performance issues and system crashing. During this process, if the system is not able to calculate this data in equal batches or the count of batches is not correct, system will not process all data.
We need to ensure that the system is including all data in this process.

Problem:
Preliminary Booking Order's Assistance Premium Calculation is not considering changes in Assistance Key and No of Insurable Objects as part of amendment correctly

Solution:
Make sure Preliminary Booking Order's calculation of Assistance Premium is considering reductions or additions in premium correctly when Assistance Key / No of Insurable Objects are changed during insured period.
Calculation of amendment:
the following reduction booking is done for the overlap period:
Premium * Protection Assignment % * (Attachment period from - to)/365/6 * number of insured objects; where
• Actual light premium amount booked is disregarded; and the Premium given in the LookUpTable is used instead
• Protection Assignment % is taken from the Proportional Protection Assignment on previous Policy light section version
• Attachment period from - to is taken from current Policy light section version (calculation of reduction)
• Number of insured objects are taken from previous Policy light section version

Workaround:
None

Root Cause:

Problem:
When creating Life Light records for Type 3 & 4 without 'Origin of Business' is causing abend when running the Cede Interface Order.

Solution:
We should be able to create Life Light records for Type 3 & 4 without abend the same way we are able to do it for P&C records Type 1 & 2.

Workaround: 
None

Problem:
System is allowing user to do bookings on wrong Base company for the Policy Light.

Solution:
Ensure it is not possible to make light bookings with wrong base company in Cede Interface Order and web service.

• Cede Interface order: Include a validation error when running order, which stops the booking: Validation error message: Incorrect Base company.
• Web services: Do not allow bookings with different base company to the Policy base company: Validation error message: Incorrect Base company.

Workaround:
Use the correct base company

Problem:
Issue with Cede Excel Loader P&C after release of SICSR-30840/SE-32961 where it was made mandatory to use the DXC provided template.

Solution:
When loading Policy Light / Policy Light Life records via Cede Excel Loader P&C / Life all fields available for the different record types must be accepted and populating the records correctly - making a correct new pending booking record - ready to be run in Cede Interface Order.

Add the six exclusions: INTEGER_ID, CREATION_TS, IMPORT_TS, RECORD_UNIQUE_ID, PID and STATUS Since these columns are also system-generated, user input is not required for them.

Previous solution in SICSR-30840 in current release must be partly rolled back to remove sequencing of the columns from the code so that the user is not forced to use that sequenced CEDE-defined template.

Workaround:
Use Excel Loader template

Root Cause:
SICSR-30840

Aim of function:
Policy Light /Policy Life Light creation including Batch Name
Preliminary Booking Order/Preliminary Bookings Correction Order creation including Batch Name
Policy / Claim Retrieval including Batch Name

• Select Entry Point as 'SicsWsBusinessEntryPoint' and Select Operation as below to Create/Update Policy Light or Policy Life Light Businesses.
• createLfPolicyLightBusiness/ createPolicyLightBusiness/ updateLfPolicyLightBusiness/ updatePolicyLightBusiness 

• Generate 'New Skeleton' and Select Entry Point as 'SicsWsBatchProcessEntryPoint' and Select Operation as 'createAccountingOrder' to Create PB/PBC Order.

• From XSD Type- select either PreliminaryBookings or PreliminaryBookingsCorrection
• New element- Batch Name is available for inclusion in the newly generated SOAP.

• Generate 'New Skeleton' and Select Entry Point as 'SicsWsDomainRetrievalEntryPoint' and Select Operation as 'retrieveObject'

• Batch Name is retrieved for both Policy and Claim.

Business value for customers:
Batch Name as part of Web Services functionality allows update without using the workstation.

System Parameters Affected:
N/A
 
Existing functionality affected:
Web Service

Aim of function

A. Enhance Policy Light ledger to include Base Company and section version

• On the Policy light ledger/Light Claim the below features are added:
  a) Base company (new column)
  b) Section version (added to section column)
  
• On Life Policy/Life light Claim a new column - Base Company is added
  

B. Ensure Policy Light items are handled with the same sequence in Cede Interface order

• When any type of Cede Interface record is created with a unique Batch name and run in Cede Interface order, In addition to existing filter system also sorts based on CREATION_TS with two elements, Date & Time
  a) First it sorts by date (oldest first)
  b) Secondly it sorts by time (if multiple records have same date). Oldest time stamp is sorted first
• Bookings at policy light ledger are displayed in the same sequence as they are sorted in Cede Interface order.

Business value for customers

• Better overview in Policy Light Ledger
• Consistent handling in Cede Interface order

System Parameters Affected
N/A

Existing functionality affected
Policy Light ledger view
Cede Interface Order

Aim of function:
New option in API for Recovery Calculation order to choose creation of either Open or Closed Worksheets

• A new field WS Open in Scheduled Job is added in the Recovery Calculation Order for Protection Program and Recovery Calculation Order for Single OCC.
• The order can be created either Online or via API, wherein the new element <isWSOpenInScJob> is added in the SicsWsBatchProcessEntryPoint, Operation- createAccountingOrder.

• If the new field is SELECTED- Order(s) when run via Job Scheduler creates Open Worksheet(s) and the Order status remains as Open.
• If the new field is NOT SELECTED- Order(s) when run via Job Scheduler creates Closed Worksheet(s) as per the existing functionality. The order status changes to Closed.
• User can close the remaining Open Worksheets via API. A new element is added in the SicsWsBatchProcessEntryPoint, Operation- closeRemainingOpenWS for the process.

Business value for customers:
Possibility to run Recovery Order via batch order without closing worksheet

System Parameters Affected:
N/A

Existing functionality affected:
API for recovery calculation order

Aim of function
API for retrieval of existing matching protection for a potential Policy Light / Life Light. The Policy Light will not be recorded in the system - just used as information for finding any existing protections.

The new API is available from SICSWsBusinessEntryPoint with the following services:

• getProtectionAssignmentForPolicyLightNotRecorded
• getProtectionAssignmentForLfPolicyLightNotRecorded

Missing response values (to be implemented in next version):

• OCC Section Name, Cedents (if multiple at OCC), OCC Claim Basis, OCC Placement: Definite Placed Share, OCC Placement: Pending Placed Share
• Non Proportional protection for Life Light Policy

Business value for customers
Possibility to check existing matching protections before creating the Policy in the system, to ensure the protection is in place and/or see if any further protections are required.

System Parameters Affected
N/A

Existing functionality affected
Web Service