When a non-zero value is saved in cost plan flat view via Edit Mode, the value is reflected in the Aggregate View; when a zero is entered to replace the non-zero value previously saved in Flat View, the 0 value is not reflected in the Aggregate View which still shows the non-zero value previously saved.
This is caused by slices, storing the financial plan TSV data, not being deleted upon saving 0 values. This also affects benefit plans that do not have the Aggregated View.
This affects any type of detailed financial plan. The steps below use the 'Cost Plan' as one example.
Steps to Reproduce:
Expected Result: Zero (0) units is shown for this year (or month)
Actual Result: 123 units still show for this year (or month); ODF_SSL_CST_DTL_COST table still hold a record representing this value.
The application should delete the slice record when a zero value is entered into the TSV cell. The application only stores non-zero slice records in the database table by design. Therefore if you follow the steps below, the non-zero slice record will be deleted and the aggregation totals will be reflected correctly.
Through the application interface, navigate to the financial plan details view
Select / checkmark the affected row or rows
Click 'Delete' button
Add the row(s) back into the plan either individually or using the populate feature
Resolved in Clarity 12.1.1 Generic Patch. Reference TEC553491.
Resolved in Clarity 12.1.2 Generic Patch. Reference TEC572267.
Resolved in Clarity 12.1.3
Resolved in Clarity 13.0.1
Resolved in Clarity 13.1.0
For additional information, reference TEC568588: Updating a Submitted Budget Plan Cost to Zero Is Not Reflected in 'ODF_SSL_CST_DTL_COST' Table
Keywords: CLARITYKB, CLRT-64765, clarity12resolved, clarity1213resolved, clarity13resolved, clarity1301resolved, clarity1310resolved, revmgr.
Release: ESPCLA99000-12.1-Clarity-Extended Support Plus