Release documentation - Cede - Enhancements and requests

Problem:
Total Allocated Split % cache issue on Accounting Classification screen. 

Total Allocated Split % on Accounting classification screen is inconsistent and displaying wrong totals. 

Solution:
Total Allocated Split % on Accounting classification screen should be consistent with correct sum of valid/active AC percentages. For main section it should show total of valid AC percentages of all sections with label 'Total allocated split % (of all sections). And for each child section, it should show total of valid AC percentages of that particular section with label 'Total allocated split %,. However, as existing, the total should be arrived by summing up of the active/valid AC split percentages only regardless of the check box 'Display valid and active classification only'.

Problem:
Error on Special Sliding Scale Commission when there are multiple currencies in the Retrocession Calculation

Solution:
When there are multiple currencies in the Retrocession Calculation of Special Sliding Scale Commission, system should use the Loss Ratio considering the exchange rate between the source balance currency and the Main Currency of the Outward Cedent's Contract when there is no Currency Transformation Term set in the Administration Condition of the OCC. System should firstly convert the source balance amounts for both Loss and Premium into the Main Currency of the OCC through the Base currency of the Cedent Company. Then, system calculates the Loss Ratio using converted balance amount of Loss divided by the converted balance amount of Premium. This exchange rate calculation logic of Loss Ratio should apply to Adjustable Variable Commission, Adjustable Variable Commission Reserve, Variable Commission, Variable Commission Reserve, Variable Commission Reserve 2, Variable Commission Reserve 3, Variable Commission 4.

Problem:
System parameter 'Split Entry Codes with special FC1 Calculation Rule in Separate Balance' unexpectedly created one Balance per Detail on one ORP when Retrocession Calculation order was executed

Solution:

• When system parameter 'Split Entry Codes with special FC1 Calculation Rule in Separate Balance' is selected, and run the Retrocession Calculation Order, system should split the entry codes that have been set the special FC1 Calculation Rule. The balance details that have the entry codes set in the same special FC1 Calculation Rule should be grouped in the same balance.

• The entry codes that were not set the special FC1 Calculation Rule should not be grouped in the same balance with the entry codes that have been set the special FC1 Calculation Rule.

• This split of balances is additional to the other balance split options that take place on a Retrocession Worksheet.

• All ORPs should have the same balance split logic when doing the retrocession Calculation.

• The 'Split Entry Codes with special FC1 Calculation Rule in Separate Balance'  logic should also apply for the Retrocession Account Order, Retrocession Estimation Calculation

Problem:
Original Currency Recovery Abends while closing Worksheets via Recovery Order

SOLUTION:
When 'Original Currency Recovery' is selected at Non Prop OCC and we have Inward Assumed Claims, the system should perform recovery calculations in original currencies.
The Paid Recoveries are allocated to the original currency by using the exchange rate for the payment As of Date, while the Loss Reserve Recoveries are allocated to the original currency by using the most recent daily exchange rate stored in the system.

Workaround:
None

Problem:
When running Recovery calculation with Combined Aggregate Limit, the system doesn't create any Recoveries.

Solution:
Recovery Calculation for Combined Aggregate Limit must be calculating recoveries at the sub-sections and considering the combine aggregate limit at main section.

Workaround:
None

Problem:
FX strange amounts in production summed from balance amount with pairing (remittance) amount.

When Original Currency = Functional currency, the current amount is being wrongly calculated.

Solution:
When Original Currency EQUAL to Functional currency, then in FC revaluation, the current amount and the previous amount should be same for the particular Functional Currency using the exchange rate 1, hence the gain/loss (unrealized & Realized) should be '0'. All other implementation done through SICSR-33013 for the scenario of Original Currency NOT EQUAL to Functional currency, should remain unaltered.

Problem:
Zeros displayed where should be empty in Online Statistics.

Zeros are shown also for each booking period and entry code where there was no bookings.

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 (already fixed by SICSR-33265). However, for each booking period and entry code where there are no bookings, those should be shown as empty without Zero. ** 

Problem:
System parameter 'Split Entry Codes with special FC1 Calculation Rule in Separate Balance' unexpectedly created one Balance per Detail on OCC when Retrocession Calculation order was executed

Solution:
When system parameter 'Split Entry Codes with special FC1 Calculation Rule in Separate Balance' is selected, and run the Retrocession Calculation Order, or Retrocession Estimation Calculation, system should split balances of OCC follow the same logic as ORPs.

When system parameter 'Split Entry Codes with special FC1 Calculation Rule in Separate Balance' is selected, and run the Retrocession Account Order, system should split balances of ORP follows the same logic as the Retrocession Calculation Order and Retrocession Estimation Calculation Order.

Problem:

Few Objects are missing in the Cede Light Universe.

Solution:

 Need to create all the missing objects for User Defined Conditions in Cede Light Universe.

Objects: Strng06 to strng20 & Date06 to Date10 under both Policy and Claim folders.

Problem:
During penetration test of SICS Batch Server they discovered that SICS Batch server doesn't replace cookie after successful login which means that is vulnerable for session fixation. How they test this is visible on screnshoots.
They also said that issue is that SICS Batch server doesn't have logout option.
https://owasp.org/www-community/attacks/Session_fixation

Solution:
In class SicsBatchServerLoginHandler we will generate a new Session ID on successful login attempts. This will make sure Session Fixation attacks are remedied.

Problem:
API Light ledger details fails mapping to declaration

Solution:
Introduce an option in web service to link the booking detail to the correct declaration.
A new element- <declarationScopeOfCoverReference> must be added under the <createLedgerDetailLight> operation under SicsWsCommonAccountingEntryPoint, similar to the sub-elements already existing for lightScopeOfCoverReference.

Workaround:
Use Cede Interface

Problem:
The pairing type of 'ASSTOORIG' is not applicable to PROFAC.

Solution:
To ensure we retrieve both the proportional treaty and proportional facultative data within the same objects, we should use the following expression:
SQL
COALESCE(ASSOCIATED_ORP_ACLB.IDENTIFIER, ASSOCIATED_ORP_ACLB_PROP.IDENTIFIER)
This approach allows us to combine values from both sources seamlessly.

We need to apply similar COALESCE expressions to all relevant fields in the Associated ORP Detail Information objects to ensure consistent data coverage across both treaty types.

Problem:
A. In the Ceded Premium Order - Policy Light level of business, user is able to Edit the order and Request a Scheduled Job even when the Run Now option is disabled. 

B. Ceded Premium Order Abends when both Policy Light and Policy Ceded level of Business are selected while running the order.

Solution:
A. When a Ceded Premium Order for Policy light level of business is run and when Run Now option Disables, ensure the order should not be accessible foe editing or for the Request Schedule job.

B. During the run process of Ceded Premium Order, if user selects both level of business, the system should automatically identify the appropriate ledger detail class (light detail or assumed detail) and generate the corresponding Worksheets. 

Workaround:
None

Problem:
RetrieveObject does not retrieve all information related to Policy Light for the existing Declarations. The name of the declaration and the Insurable Object Object ID is available in the response under Scope of Cover of Section, however, not available under Declaration details. 

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

• Insurable Object Name 

With SE-39244, SicsWsBusinessEntryPointClass fix was done at ScopeofCoverList and need to retrieve Insurable Object Name as part of <declarationList>. 

Aim of function:
New Web Service Operations for creating and linking Non-proportional Protection Assignment under SicsWsBusinessEntryPoint

• addRealizeNonPropFacOccProtectionToLightPolicy

• addRealizeNonPropFacOccProtection

Business value for customer:
Possibility to define Non-proportional Protection Assignment using Web Service

System Parameters affected:
N/A

Existing Functionality affected:
Existing Web Service Operations renamed to separately identify from new Web Service Operations

• addRealizePropFacOccProtectionToLightPolicy
• addRealizePropFacOccProtection

Aim of function:
New web service for overriding Protection Assignment at declaration level of a Policy Light under SicsWsBusinessEntryPoint

• OverrideDeclarationProportionalProtectionOnLightPolicy
  

• OverrideDeclarationNonProportionalProtectionOnLightPolicy
  

Business value for customer:
Ability to override Policy Light Declaration Protection Assignment using web service.

System Parameters affected:
None

Existing Functionality affected:
Proportional and Non Proportional Protection assignment for a Policy light

Aim of function:
To enhance the SICS CEDE Universe by analyzing the existing data model and developing approximately 30 new derived tables, joins, and related objects to integrate and represent associated detailed information.
This will ensure that all necessary ORP data elements are efficiently modeled, linked, and available for reporting and analytics purposes within the BusinessObjects (BO) environment. Following derived tables rt be created in SICS CEDE Universe-

• OCC_RETRO_DTL_PAIR_PROP
• OCC_AS_BOOKING_ACLD_PROP
• ORP_RETRO_DTL_PAIR_PROP
• ASSOCIATED_ORP_ACLD_PROP 
• ASSOCIATED_ORP_ADD_CLASS06_ALL_PROP                                                                      
• ASSOCIATED_ORP_ADD_CLASS08_ALL_PROP
• ASSOCIATED_ORP_ADD_CLASS09_ALL_PROP
• ASSOCIATED_ORP_ADD_CLASS10_ALL_PROP
• ASSOCIATED_ORP_BSR_PROP
• ASSOCIATED_ORP_ACLB_PROP
• ASSOCIATED_ORP_EC_PROP
• ACC_CLASSIFIC2_PROP
• REF_LEVELOFBUS_PROP 
• REF_TYPEOFBUS_PROP  
• ASSOCIATED_ORP_SHARE_PROP
• ASSOCIATED_ORP_BROKER_PROP
• ASSOCIATED_ORP_BROKER_REL_PROP  
• ASSOCIATED_ORP_CEDENT_PROP
• ASSOCIATED_ORP_REINSURER_PROP 
• ASSOCIATED_ORP_REINSURER_COUNTRY_PROP
• ASSOCIATED_ORP_TOP_METHOD_PROP
• ASSOCIATED_ORP_COUNTRY_PROP  
• ASSOCIATED_ORP_MCOB_PROP  
• ASSOCIATED_ORP_COB_PROP
• ASSOCIATED_ORP_SCOB_PROP
• ASSOCIATED_ORP_BYRP_PROP
• ASSOCIATED_ORP_AYRP_PROP

Business value for customers:

• Enhanced Reporting Capability: Enables users to access a more complete and accurate view of ORP detail data directly through the SICS CEDE Universe without manual data merges.
• Improved Decision-Making: Provides richer, integrated datasets for analysis, helping business users make faster and data-driven operational decisions.
• Performance Optimization: Derived tables and well-defined joins improve query performance and reduce report generation time.
• Data Consistency and Accuracy: Ensures that all ORP-related metrics are standardized across reports, minimizing discrepancies and improving data reliability.
• Scalability for Future Enhancements: Establishes a flexible universe design that can accommodate future ORP and CEDE data expansions with minimal rework.

System Parameters affected:
N/A

Existing functionality affected:
N/A