Release documentation - Cede - Enhancements and requests

Problem:
Limit when using BP Mass Update on Balances

Solution:
On the Business Partner Balance Mass Update is executed, i.e. the Find Now is selected, then the system will find a number of balances matching the criteria given on the order. The system must list ALL found balances and not limit the list to 30 balances.

Problem:
LORS LIMRIA message when processed, the sub accounts finds the correct retrocessionaire and its balance automatically. If there is a mismatch system throws a valdation error 'LOSubaccountToBalanceReferenceRule' but allows user to change the retrocessionaire and the balance details. On saving the details, system allows to authorize the transaction.

When processed, system again throws validation error for 'LorsTransactionCreationApplyRule' for retrocessionaire mismatch. The system although changed the balance details but retrocessionaire details remains as is means the new retrocessionaire is not reflecting.

Solution:
LOSubaccountToRetrocessionaireReferenceRule should not automatically re-reference once a reference is already made.

Root Cause:
LOSubaccountToRetrocessionaireReferenceRule always re-referencing even if already done.

Problem:
The installation documentation does not clearly articulate some of the platform differences and the implications to SAP BI Reports of making the switch to an optimized schema.

Solution:
Updated the documentation accordingly.

Problem:
Booking Year Period Start Date & Booking Year Period End Date are not actually defined as Dates.

Solution:
View V_AC_DETAIL_LIGHT_TIME needs to be created and then need to  adjust all the Timeline Objects to come from this new view to get the correct data.

Problem:
View V_AC_DETAIL_LIGHT_TIME is not present and SQL for the objects needs to be adjusted and create few objects for Triangulation and sum objects for Policy Retro.

Solution:
1. View V_AC_DETAIL_LIGHT_TIME needs to be created and also alias for the table V_CLMS_HL_DER_LIGHT_TRIG needs to be created.

2. Needs to have joins for the above created alias and the view.

3. Need to Adjust SQL for the objects under Timeline folder and then objects under Timeline needs to have sub folders as Accounting Period Timeline and Booking Period Timeline and move the objects to subfolders also few objects needs to be created.

4. Need to adjust SQL for the objects under Triangulation objects, Support, Policy Retro folders. Also need to created few Dimension objects under Policy Retro folder as per the Requirement.

5. Need to adjust the structure by deleting the tables that are no longer needed in CEDE Universe.

Problem:
Need to change the definition for Legal Area object and add a new object Legal Area(Code)in the universe.

Solution:
The definition needs to be change as below mentioned:
Object name: Legal Area 
Object SQL :  LA_Light_SocClass.NAME

A new object has to be created:

New Object:    Legal Area (code)
New SQL  :      COALESCE(LA_Light_SocClass.CODE,LA_Light_SocClass.SHORT_NAME)

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:
XML message for policy creation throws error, due to the fact that the XSD type for 'childScopeOfCover' element in the SOAP request is wrongly used. This should have a type 'PcScopeOfCover'.

Solution:
Update documentation to reflect the changes made in XML message.

Problem:
Not possible to 'Add and Realize Fac OCC Protection' via web services

Solution:
Create a new web service called 'Add and Realize Fac OCC Protection', which must be available from assumed fac and direct business, and also from Policy Light. The web services should mirror the online functionality

Workaround:
Use web service Add Fac Protection which is dependent on the Prop Fac OCC already existing

Problem:
UDF_TXT4 in CEDE_INTERFACE is smaller size then other UDF_TXT attributes in CEDE_INTERFACE table

Solution:
Policy Light UDF text fields must have same size and be documented accordingly

Increase UDF4 Text Field length from 30 to 256, which should be same as other UDF Text fields (1 to 6)

Problem:
Recycling very slow with large number of records with errors takes too long time

Solution:
The recycling process should move the records from having status run in order (with or without error) back to Pending. This process should just keep the records as-is - and should not take long time per record.

Workaround:
The recommended workaround is to correct the records (according to error message in Cede Interface monitor) in spreadsheet / SQL and run again.

Problem:
Creating a new Life Policy Light ( Type 3 or 4), the system creates a new Insurable Object (Person) every time.

Solution:
When using the Cede Interface to create a new Life Light Policy (Type 3 or 4), the system should not create a new insurable object, but instead add the new policy to the Light Policy List of the Insurable Object included in the record.

Aim of function:
Improvement of Domain Retrieval for Policy Light and Light Claim.

Business value for customers
Access to an overview of structure, classification and protections for the light object via domain retrieval for web services: SicsPolicyLightBusinessReference and
SicsLightClaimReference.

System Parameters Affected:
N/A

Aim of function
Create Web Service for Add and Realize Fac OCC Protection
Functional and Technical specifiation

Business value for customer
Prop Fac OCC could be defined and created via Web Service - in addition to existing online functionality

System Parameters affected
None

Existing Functionality affected
Add and Realize Fac OCC Protection online - from Policy Light, assumed Fac and Direct business

Aim of function
Implement a simple out of the box integration solution for DXC Assure Commercial & Specialty on Microsoft SQL Server

Business value for customers
OOTB Integrated solutions