Release documentation - Cede - Enhancements and requests

Problem:
When the system parameter on the Find, Partners page, named 'Include merged companies and merger parent at search by business partner' is NOT selected and the BP Ledger is opened from a Merger Parent, the system bring all merged companies in as well

Solution:
When you open the BP ledger from a business partner that has Merged Companies, i.e. it is a Merger Parent to the merged companies, then the system will also bring all the Merged Companies to the list of Business Partners and highlight these on the ledger. This is correct when the system parameter 'Include merged companies and merger parent at search by business partner' is selected.

But if this parameter is NOT selected, then we must make sure the system only bring the actual business partner, i.e. the Merger Partner, and leave the Merged Companies behind.

It is also correct when you start from one of the Merged Companies, i.e. only his partner shall be shown in the list of partners on the ledger, this is independent of the above mentioned system parameter.

Workaround:

Root Cause:

Extent of Impact:

Impact on Existing Data

Recovery Method for Existing Data Affected

Problem:
Generate Payment Request - Settlement Balance vs Technical

Solution:
When a Remittance balance is created from a balance group (Settlement Balance Group or Account Balance Group) belonging to a Business Partner with only ONE bank account in the same currency as the balance currency, make sure the system sets this bank account on the created remittance, independent if the Intermediary Account is selected on the bank account and independent if the system parameter Partner's Bank Account Currency same as Payment Currency for Paid Remittances. The rules for how to default the partner bank account shall follow the function Generate Payment Request when this is selected from a technical balance.

Workaround:

Root Cause:

Extent of Impact:

Impact on Existing Data

Recovery Method for Existing Data Affected

Problem:
Settled Instalments not displayed correctly on P/L Instalments

Solution:
When the Paid and Paid % columns are updated on the OCC after instalments are booked and distributed to the ORP and these instalment balances are Settled on the ORP ledgers, we must make sure these columns are updated correctly according to the portion of the instalments that are paid.

Example:
If an instalment is booked on a non-prop OCC and it is distributed to two ORPs with share of 40 and 60 percent, and the instalment on the ORP with 40% becomes Settled, then this instalment on the OCC should be shown as Partially with 40% in the Paid % column. When both of the ORP's instalments are Settled then it should show Yes with 100% in the Paid % column.

Workaround:

Root Cause:

Extent of Impact:

Impact on Existing Data

Recovery Method for Existing Data Affected

Problem:

Job Template without priority allowed

Solution:

Make the Priority field in Job Templates mandatory. 

Allow any value upto 10 digits. 

Workaround:

Root Cause:

Extent of Impact:

Impact on Existing Data

Recovery Method for Existing Data Affected

Problem:

SOAP Server doesn't save 'fundType' information when a BusinessPartner is created/updated by SAOP message.

Solution:
Fix classes
com/csc/sics/businesspartner/bp/SicsBusinessPartnerCreateBp.java
com/csc/sics/businesspartner/bp/SicsBusinessPartnerMainInfoEditBp.java
to manage 'fundType'

Workaround:
No Workaround

Root Cause:
Code bug. Fund type not handled.

Problem:
Abend when selecting 'Populate interface tables' under Light Interface Test Generator

Solution:
The Light Policy must be copied the number of times indicated

Workaround:
Create new Policy Light via Cede Interface / Web Service / Online

Root Cause:

Extent of Impact:

Solution:

Workaround:

Root Cause:

Extent of Impact:

Problem:
System Abend's when opening Light Claim properties which is linked in View Recovery Claim overview

Solution:
When opening Light Claim proporties from View Recovery Claim, selecting Claim list and open up proporties of one of the listed Light Claims - the system should show properties of the Light Claim selected.

Workaround:
Open the Light Claim directly

Root Cause:

Extent of Impact:

Impact on Existing Data

Recovery Method for Existing Data Affected