Release documentation - Cede - Enhancements and requests

Problem:
Preliminary Bookings order abends in Faculative Prop when Fronting Fee is defined as an amount and premium bookings from Light Policy is proportionally retroceded in Preliminary booking order

Solution:
When running a Preliminary Booking order, and the Premium booked on the Policy Light is retroceded to a Proportional Fac OCC with Premium Basis = Proportional Based or Cash Based - and with Fronting Fee defined as an amount instead of percentage, the fronting fee should be correctly calculated and booked according to the condition.

Workaround:
If the client actually has a Flat premium for the Prop Fac OCC, and change the Premium basis accordingly, there will be no abend when running PB order.

Problem:
Proportional retrocession of Light policies in Sql Server DB does not use 10 decimals places for the calculation causing incorrect retrocession details and figures in AC_RETRO_DTL_PAIR

Solution:
Calculation logic for Proportional Retrocession of Light policies must use 10 decimal places also in Sql Server DB - to ensure correct distribution to Proportional OCC and ORP. The functionality must work the same as for Oracle.

Workaround:
None

Problem:
Abend when searching for business partners in Add and Realize OCC Fac Protection (Non Proportional)

Solution:
When selecting Non Proportional and Proportional Protection Assignment from a Policy Ceded, and thereafter selecting Add and Realize OCC Fac Protection, the system requires you to first fill in some fields for OCC level. When all required fields are filled in, and no error messages appear, the system requires you to fill in information in the container to create corresponding retrocessionaire participations.
When entering a business partner ID code in the business partner field - the system should search for the corresponding business partner. If not found, the field should be left empty, not giving any search result.

Workaround:
Fill in the correct Business Partner ID

Problem:

Cede Universe - Join issue.

Solution:

1. Modify the join between AC_RETO_PAIRNG & V_ORP_DATES. Instead of V_ORP_DATES, it should have a join with V_ACLB_B2.

The updated join structure should look like this:

2. The objects associated with V_ORP_DATES should be adjusted so that they reference to V_ACLB_B2, instead of V_ORP_DATES.

Problem:

Replace two views into a new view which will also replace the table AC_DETAIL_LIGHT.

Solution:

1.Need to create a new view V_AC_DETAIL_LIGHT that will replace 2 views V_AC_DETAIL_LIGHT_TIME and V_ENTRY_DATES to get bit better performance.

2. Once the new view is created need to take it in the universe structure and give the joins by replacing table and old views as required.

3. Once the joins are done need to adjust all the object definitions for all the associated objects of the table AC_DETAIL_LIGHT and views V_AC_DETAIL_LIGHT_TIME and V_ENTRY_DATES instead to come from the new view V_AC_DETAIL_LIGHT.

Problem:
Object retrieval for Policy Light repeats list of all protections at each and every Policy Light section. (For example: Section A lists protection assignment for both Section A and Section B and also Section B lists protection assignment for both Section A and Section B)

Solution:
When doing Object retrieval for a Policy Light, the result should be given per section, based upon information for:

• Section Name (Section A)
• Section Version
• Classification information
• Proportional and Non Proportional Protection for current section (Section A)

If further sections (for example Section B), only information for current section is given (Section B)

Problem:

25.1 PC Main/Cede/Life upgrade queries to UNX universe - working around a cartesian product by moving it to the view V_TRIG_YEAR

Solution:

1. Creation of database view V_TRIG_YEAR

2. Once the database view is existing on the database, we need to adjust the universe structure and replace the TRIG_YEAR table with the database view V_TRIG_YEAR

3. Once this view is introduced the following objects needs to be altered in the UNX universe, the TRIG_YEAR table needs to be exchanged with V_TRIG_YEAR database view in the select statement.

When all this is done then a triangulation query can easily be upgraded from UNV to UNX universe.

The SQL of the object triangulation query will be like this and the cartesian product is gone.

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:
The isoAlpha2 code is not retrieved when accessing any domain object or country via reference data retrieval.

Solution:
Include the isoAlpha2 code in the country object during the country data retrieval process to ensure it is part of the retrieved information.

Verification:

• Step 1: Retrieve any business and check the list of included countries to confirm that the isoAlpha2 code is present.

• Step 2: Check the domain retrieval of countries from the reference entry point to ensure that the isoAlpha2 code is correctly included in the retrieved data.

Problem:
While creating Ceded Premium order for extration of Policy Light bookings, the Booking Year and Period extraction at order is not defaulted from Base Company given in Base Company

Solution:
In Cede Premium order, when selecting level of business = Policy Light, the following default must be implemented:

When selecting one specific Base Company in the container, and the Base company has a specific Booking Term in Booking Terms Maintenance, this booking term should be basis for available Booking Year and Periods From - To at the top of the Ceded Premium order.

Current default is to use Booking Term default settings when Policy Light is selected. Default Booking Terms should still be used in these cases:

When Policy Light and two or more Base Companies is selected
When Policy Light and no specific booking term defined for selected base company
When Policy Ceded is selected - booking terms maintenance are dependent on listed business in the container
When both Policy Ceded and Policy Light is selected - and no specific Base company

Workaround:
None

Problem:
When a Policy Light has multiple amendments and a single Preliminary booking order is run, then the Assistance Coverage Premium calculation is incorrect. It is summing up all the Attachment period's premium and adjusting it multiple times.

Solution:
When running Preliminary Booking order calculating Assistance Cover Premium, system should calculate premium respective to its attachment period. It should adjust respective attachment period's Premium only once
The rule for Assistance Cover Premium in Preliminary Booking order is:
Premium is calculated considering the attachment period of policy light, and is booked to OCC As Original for the protected period. If the premium is for the entire insured period (i.e. the attachment period from - to of the policy light is the entire year), the full premium (multiplied with number of insured objects) is booked. If the attachment period is half a year, approximately ½ of the premium (counting days) is booked to OCC As Original. If the policy is amended, the new period/assistance key/number of objects will be considered for the amended period, and the corresponding reduction will be done for the corresponding period before amendment.

Workaround:
None

Problem:
System abends when trying to move a light claim that is already retroceded. 

Solution:
When selecting to move an already retroceded light claim to another section and the source and target section has different proportional protections, the system should not abend but stop you with the validation error message CM0523 ' The claim cannot be moved since the Proportional Protection assignment is not identical for the old and new section'. 

Aim of function
Refine response by including missing values for Protection Plan:

• OCC Section Name, Cedents (if multiple at OCC), OCC Claim Basis, OCC Placement: Definite Placed Share, OCC Placement: Pending Placed Share
• Cedents (could be multiple at OCC)
• OCC Claim Basis
• OCC Placement: Definite Placed Share, Pending Placed Share

1) Connect to the SICS Server and open XML Tree view.

2) Generate 'New Skeleton' and Select Entry Point as 'SicsWsBusinessEntryPoint' and Select 'getProtectionAssignmentForPolicyLightNotRecorded' or 'getProtectionAssignmentForLfPolicyLightNotRecorded'

3) New Soap is available to generate protection for Light Policy not recorded.

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

Aim of function
The Cede Excel loader function allows validation of records at an early stage of the process. This will improve the quality of the data before running it in the Cede Interface order

• Ensure mandatory columns are identified regardless of the order of the columns.
• Ensure mandatory columns with missing data are validated.

Note:
Any non-existent column (not part of cede interface record) will not be validated and might cause loss of data when running in Cede Interface Order

Cede Excel Loader P&C, Cede Excel Loader Life
Example of error messages when importing a file:

Once the errors are corrected and file is uploaded it gets successfully processed and ready to import.
The records are now available in Cede Interface monitor under pending records, ready to be included in a Cede Interface Order.

Business value for customers
A more correct and streamlined handling of records in Excel Loader with validations at an earlier stage of the process. This will improve the quality of the data before running it in the Cede Interface order

System Parameters Affected
None

Existing functionality affected
Cede Excel Loader P&C
Cede Excel Loader Life