An error message "CostPlanDetail persistence failed" occurs when a cost plan is created using the 'New From Resource' button
Steps to Reproduce:
Expected Result: Cost Plan created
Actual Result: Error reported: "CostPlanDetail persistence failed"
When a SQL Trace is run, it will show that the total_billing_cost column is being set to a non-numeric value in FIN_COST_PLAN_DETAILS.
update FIN_COST_PLAN_DETAILS set billing_cost = ?, total_billing_cost= ?, last_updated_date = ?, last_updated_by = ? where id = ? NDE:[email protected]: prepareStatement(string) NDE:[email protected]: setBinaryStream(): 1, [email protected] NDE:[email protected]: setObject(): 2, NaN NDE:[email protected]: setObject(): 3, 2010-07-28 16:09:27.462 NDE:[email protected]: setInt(): 4, 5030402 NDE:[email protected]: setLong(): 5, 5427599 NDE:[email protected]: execute() NDE:[email protected]: FAIL: [CA Clarity][Oracle JDBC Driver][Oracle]ORA-01722: invalid number
When this condition occurs, this usually is attributed to time segments that have an allocation % set to infinity (ascii code 236). To find this:
The above needs to be repeated for each resource or role.
The infinity value is caused by allocation ending on a non-working date from the clarity calendar.
For more information on other symptoms of the infinity value in an allocation segment, refer to the following articles:
TEC530210: Clarity: Infinity data value on Allocation Segments - java internal processing exception : NumberFormatException.
TEC530418: Clarity: Booking Status Portlet Error when attempting to Export to Excel.
Resolved in Clarity 12.0.2.
Keywords: CLARITYKB, CLRT-27754, clarity12resolved, clarity1202resolved.
Release: ESPCLA99000-12.1-Clarity-Extended Support Plus