Release documentation - Cede - Enhancements and requests

Problem:
Abend when running recovery calculation with Risk Name - and RiskEvent indicator is Event.

Solution:
1) Recovery Calculation must in the process of creating missing outward claims disregard the Claim Risk Event Indicator when there is a Risk name.
Risk claims with the same Risk Name is grouped together as one Dummy Headline loss according to existing functionality; and recovery calculation create an outward claim; including both Risk and Event inward claims.
2) In the process of checking the valid classifications of the inward details for the OCC claim; recovery calculation check the assumed claim risk event indicator against the Type of participation of the Outward Cedent's Contract.
a) If the Type of participation is Risk (Parent Data Type of the Type of Participation has Per Event Per Risk Indicator = Per Risk), the recovery calculation will include ONLY details with Claim Per Risk Indicator = Risk in the recovery calculation.
In some cases this will mean that no Outward Claim will be created (depending on the Claim Creation limit settings as well).
b) If the Type of participation is Event (Parent Data Type of the Type of Participation has Per Event Per Risk Indicator different from Per Risk) - recovery calculation will include all details.

Observations:
This works fine when the inward claim is of type assumed claim (fixed by SICSR-417)

Workaround:
If the Claim Risk Event indicator for a Light Claim with Risk Name is changed to Event; the abend is avoided

Problem:
Performance issue with Non-Prop Recovery Order when executed for a specific Protection Program (PP18) and year.
 
Solution:

• Changes needed in various methods to reduce process time. This includes createBookingDetailHelpersFromLightDetailsFor, getBookingDetails and some other methods.
• In SE-8179 used method for object id list-chuncking must be changed to streamline the type of code

Problem:
Functional Currency 2 balance amount <> 0 for balance with Original Amount = 0

Solution:
Pre-condition :

The following system parameters should be enabled:

• Functional Currency 1 in use - with any functional Currency

• Functional Currency 2 in use - with any functional Currency

• Allow override Functional Currency in Business

• Manually change Functional Currency

• Allow override FC Calc rule in Business

When any booking has Zero balance, the functional amount for the defined functional currencies should also be zero without any decimal values at More Balance information window, regardless of the fact whether the the exchange rates are from system or manually entered rate at Functional currency maintenance screen.

Problem:
When the Headline loss ID is created using lower case letters in Cede Interface Order, the system creates them as capital letters in the system (headline becomes HEADLINE). Next time this lower case letters are used in a record for the same Headline loss ID - the system does not recognize the previous Headline loss as the same, since it is comparing a lower case one to the created capital letters Headline loss ID. Thereby duplicate Headline loss IDs with the same name are created.

Solution:
The Headline loss ID is expected to have capital letters, and when creating them online all lowercase letters are converted to capital letters. This works fine also in Cede Interface the first time, a Headline ID with capital letters is created. The issue appears when creating a new record with the same lowercase Headline loss ID. The system does not recognize the previous Headline loss as the same, since it is comparing a lower case one to the created capital letters Headline loss ID.
Preferred solution: When converting a Headline loss ID from lower case letters - it should check if there are any existing Headline losses which 'converted' are called exactly the same. The current light claim / light claim booking should then be linked to this one - not creating a new one.

Workaround:
We expect creation of a Headline loss ID to be done with capital letters. This is reflected also in the online creation of a Headline loss ID, where lower case letters are automatically converted to capital letters.
By doing this - this issue in Cede Interface order will not occur.

Problem:
Wrong Sign For Realized Gain/Loss (RGLOE)

When negative balance included in Received Remittance for pairing and after the pairing completed, the FC revaluation happening with Positive figures. As a result the Mvt Realized Gain/Loss 1 & Mvt Realized Gain/Loss 2 for FC1 & FC2 showing wrong sign. (Instead of Loss it shows as Gain).

Solution:

• When Negative Technical balance included in Driving Negative Remittance for pairing and after the pairing completed, the FC revaluation should consider the Current and Previous amount in - figures. Based on these negative figures only, the Mvt Realized Gain/Loss 1 & Mvt Realized Gain/Loss 2 for FC1 & FC2 to be calculated and shown. For Positive included balances it should work as it is working currently.
• When Positive Technical balance included in Driving Positive Remittance for pairing and after the pairing completed, the FC revaluation should consider the Current and Previous amount in + figures. Based on these positive figures only, the Mvt Realized Gain/Loss 1 & Mvt Realized Gain/Loss 2 for FC1 & FC2 to be calculated and shown. For Negative included balances it should work as it is working currently.
• When Negative Remittance balance included in Driving  Negative Technical Balance for pairing and after the pairing completed, the FC revaluation should consider the Current and Previous amount in + figures. Based on these negative figures only, the Mvt Realized Gain/Loss 1 & Mvt Realized Gain/Loss 2 for FC1 & FC2 to be calculated and shown. For Positive included balances it should work as it is working currently.
• When Positive Remittance ** balance included in Driving Positive Technical Balance for pairing and after the pairing completed, the FC revaluation should consider the Current and Previous amount in - figures. Based on these positive figures only, the Mvt Realized Gain/Loss 1 & Mvt Realized Gain/Loss 2 for FC1 & FC2 to be calculated and shown. For Negative included balances it should work as it is working currently.
• Further the signs should be compared with 'Unsettled balances' before pairing instead of main 'Balances' to cope up with Single TW with multiple RW and Single RW with multiple TW pairings. The logic should be :

           If Driving balance is RW then

          if TW Unsettled Balance + and RW Unsettled Balance - then FV+
          if TW Unsettled Balance - and RW Unsettled Balance - then FV-
          if TW Unsettled Balance - and RW Unsettled Balance + then FV-
          if TW Unsettled Balance + and RW Unsettled Balance+ then FV+

          If Driving balance is TW then

          if TW Unsettled Balance + and RW Unsettled Balance - then FV+
          if TW Unsettled Balance - and RW Unsettled Balance - then FV+
          if TW Unsettled Balance - and RW Unsettled Balance + then FV-
          if TW Unsettled Balance + and RW Unsettled Balance+ then FV-

Pre-conditions :

System Parameter : Currency > General > Functional Currency Options > Include Realized Gain/Loss in FC Revaluation is ON  **  

Base Currency (Booking Currency) : USD

FC1 : USD

FC2 : EUR

Example for Single RW being paired with multiple TWs. 

Example for scenario 1 :

Received Remittance RW1 : Driving balance USD - 100 (Exchange Rate : 0.8900 = Euro - 89 )

TW1 : Included balance USD + 200 (Exchange Rate : 0.8600 =  Euro 172 )

TW2 : Included Balance USD - 100 (Exchange Rate : 0.8600 = Euro - 86)

When checking the FC Revaluation after Pairing 

TW1 :

FC1 Mvt Realized Gain/Loss = 0

FC2 Current Amount +178, Previous Amount +172, Mvt Realized Gain/Loss : Current Amount - Previous Amount = 178 - 172 = 6 (Gain)

TW2 :

FC1 Mvt Realized Gain/Loss = 0

FC2 Current Amount -89, Previous Amount -86, Mvt Realized Gain/Loss : Current Amount - Previous Amount = -89 - (-86) = - 3 (Loss)

Example for scenario 2 :

Paid Remittance RW1 : Driving balance USD 100 (Exchange Rate : 0.8900 = Euro 89 )

TW1 : Included balance USD - 200 (Exchange Rate : 0.8600 =  Euro -172 )

TW2 : Included Balance USD + 100 (Exchange Rate : 0.8600 = Euro 86)

When checking the FC Revaluation after Pairing 

TW1 :

FC1 Gain/Loss = 0

FC2 Current Amount -178, Previous Amount -172, Mvt Realized Gain/Loss : Current Amount - Previous Amount = -178 - (-172) = - 6 (Loss)

TW2 :

FC1 Gain/Loss = 0

FC2 Current Amount + 89, Previous Amount  +86, Mvt Realized Gain/Loss : Current Amount - Previous Amount = 89 - 86 = 3 (Gain)

Problem:
Zero total not shown per Entry Code in Online Statistics when Ladder View is activated

Solution:
In Online statistics screen, even with 'Ladder View' option, the entry code-wise total should be shown, even it is '0' as it is being correctly shown without the option Ladder view.

Problem:
Error message 'column ac_detail_light of relation ac_detail_light does not exist' when running Ceded Premium Order in PostgrSQL database is stopping the premium calculation. Calculation works fine for Oracle DB.

Solution:
Implement solution for calculation of CededPremiumOrder which works for all databases.
Changes are needed in sqlUpdateIsIncludedInCPOrder method of SicsAccountingCededPremiumRunOrderBp.
The query needs to be rewritten to support SQL server, MySQL, Oracle and Postgres.

Workaround:
None

Problem:
Due to rounding problem Automatic Protection Assignment sometimes assigns Own Retention even when Total retroceded is perceived as 100%.
Causing BR0026: The Total Retroceded Share cannot exceed 100%

Solution:
The system should not assign Own Retention when Total retroceded is already 100%.

Workaround:
Remove the Own Retention assignment from the Single Business Auto Protection proposal before save.

Root Cause:
Extent of Impact:

Impact on Existing Data

Recovery Method for Existing Data Affected

Problem:
Missing table reference in the object definition.

Solution:
Add the missing tables to the object definitions.

Note: A couple of object definitions in the universes are missing table references. Ensure all missing tables are included in the object definitions.

Problem:
No Confirmation Message raised when deleting a Domain Restriction assigned to user role.

Solution:
Raise confirmation message when user selected the 'Delete' menu option on Domain restrictions tab. When selected No, the delete process should be rolled back.

Solution:
Eliminate redundant code from the PC module such as createClaimWorksheetRequest , CloseWorksheetRequest and other similar requests, retaining only the shared functionality in the Common module, and ensure the Common module manages all logic while simplifying the PC module to reference this shared functionality, followed by thorough testing to ensure consistent functionality across modules.

Problem:
Cede Interface order abends when two failing Claim records is supposed to create a new section to an existing Policy Light

Solution:
When running a claim record which has Date of loss outside an existing Headline loss which it is linking to, the system should not abend.
In Cede Interface this must result in an error message that the DOL is not within the Headline loss date span.
In Cede Excel Loader a similar error message must be given.

Note that Epic SE-35799 is fixing the other issues found in this respect.

Workaround:
For the following scenarios, you could correct the claim records and run Cede Interface Order again after correction:
Fill in section name, Claim status - and make sure the Claim DOL is within the Headline loss from - to period (if you are linking to an existing Headline). The error might be checked by running one of the records separately to see what is failing.

Problem:
When running Ceded Premium Order some worksheets are closed incorrectly at order, business ledger and find worksheet view

Following issues are found when running Ceded Premium Order.
1. In case of Policy Light Level of Business - 'Run Now' still enabled, even after successful order run & worksheets generated.
2.  In case of Policy Light Level of Business - After running order, Worksheets are generated, but 'Worksheets' option from the pop-up menu, is still disabled. 
3. In case of Policy Light Level of Business - Unable to view the generated informational booking worksheets via Accounting> Worksheet>Find Worksheet window
4. In case of Policy Ceded Level of Business - In Business ledger, for the informational bookings, the 'Closed date' column in ledger appears blank.

Solution:
When Ceded Premium Order is run for Policy Light or Policy Ceded; the following corrections must be done:

• For Policy Ceded when creating Ceded Premium results, these newly created worksheets must have Closed status at the Policy Ceded business ledger.
• For Policy Light when successfully running the order, policy light details are created instead of worksheets. The run must check if these light bookings are created. If at least one is created, the order must be closed for further run by disabling “Run now” and closing the order. Note that bookings are as before possible to inspect at the Policy light ledger where the worksheet ID starts with the current order ID (for example AO1234/1).

Workaround:
View the Policy Light>Ledger details, for the worksheet generated via Ceded Premium Order.

Problem:
When running Multi Business Protection Assignment order and the system parameter 'Retrocede to Own Retention' is selected, save protections on business gives a double allocation to Own Retention and is also removing/reducing the Prop Treaty allocation incorrectly down to zero %.

Solution:
When running Multi Business Protection Assignment order and the system parameter 'Retrocede to Own Retention' is selected, save protections on business gives a double allocation to Own Retention and is also removing/reducing the Prop Treaty allocation incorrectly. To avoid this, the system must remove the 'cached' earlier result for Own Retention in the Multi Order process and only do the calculation once.
 
When running Multi Business Protection Assignment order and the system parameter 'Retrocede to Own Retention' is selected, save protections on business gives a double allocation to Own Retention which is due to cache and also as it holds already one own retention and it matches with the current one so system kept the own retention completely and making the other protections percentage to zero incorrectly. To avoid this, the system must remove the 'cached' earlier result for Own Retention in the Multi Order process and only do the calculation once.

Workaround:
Manual update of the incorrect allocation

Problem:
RetrieveObject does not retrieve all information related to Policy Light for the existing Declarations and Declaration protection assignments. The name of the declaration and the Insurable Object Object ID is present in the response (should show IO Name). Currently it is also missing declaration main limit if overridden and declaration protection assignment if overridden.
Declaration Classification is inherited from Policy Light section, and is found at the section level.

Solution:
When retrieving information for a Policy Light it has to include information for Declarations (if any):

• Insurable Object Name
• Declaration Main limit - if overridden
• Declaration protection assignment - if overridden

Problem:
System abends when adding Policy Light on Create New Cede Interface Rule when using Quick Find option on Find Business window. 

Solution:
System should open the Policy Light when searching for and transferring Policy Light using Quick Find just like it does when searching for Policy Light using Find Now button.

Workaround:
Use Find Now option on Find Business window to search for Policy Light.

Aim of function:
New Headline loss filter displaying a Date of Loss list for current Headline loss when opened.

• As for other filters, there is an option to exclude one or more Date/s of Loss, leaving the included claims in the claim list
• Calculation of accumulated Headline loss amounts is for included Claims only
• Implemented for assumed and light claims

Business value for customers:
More granular overview of Headline loss.
The implementation is done as preparation for Recovery Calculation with Automatic Hours Clause

System Parameters Affected:
N/A

Existing functionality affected:
Headline loss view