AnsweredAssumed Answered

Slice data Budget, Benefit, Forecast not updating when zero is entered

Question asked by MikeGillespie on Aug 1, 2011
Latest reply on Jul 2, 2012 by Connie_Fu
In 12.1 sp1 I have noticed the following:

When updating a budget, forecast, or benefit the respective
odf_ssl_***_dtl_cost slice tables are not updated when a zero value is
entered into the plan. All other values update the slice tables.

Running a SQLtrace reveals these statements are run when updating the plan -
one delete and one insert for the new value. However, when a zero value is
entered into the plan the delete and insert is not performed.

Could this be by design or a bug?

Does anyone know another way to get this tyep of data for portlets?


PMD:STATEMENT-SET: blobcrack.batchDelete_set in blobcrackPMD.xml
NDE:PSTM@2b742b74: Non-SQL Time: 0

DELETE FROM ODF_SSL_CST_DTL_COST WHERE SLICE_REQUEST_ID = ? AND PRJ_OBJECT_ID
IN (5235786)


NDE:CONN@4d194d19: prepareStatement(string)
NDE:PSTM@2b742b74: setInt(): 1, 5000073
NDE:PSTM@2b742b74: execute(): ExecuteTime: 1
NDE:PSTM@2b742b74: close(): Open Time: 1
PMD:STATEMENT-SET: blobcrack.insertSegmentSlice_set in blobcrackPMD.xml
NDE:PSTM@1d6c1d6c: Non-SQL Time: 0

INSERT INTO ODF_SSL_CST_DTL_COST
( SLICE_REQUEST_ID, PRJ_OBJECT_ID, START_DATE, FINISH_DATE,
SLICE, CREATED_DATE
)
VALUES (?, ?, ?, ?, ?, ? )


NDE:CONN@4d194d19: prepareStatement(string)
NDE:PSTM@1d6c1d6c: setInt(): 1, 5000073
NDE:PSTM@1d6c1d6c: setInt(): 2, 5235786
NDE:PSTM@1d6c1d6c: setObject(): 3, 2011-12-31 00:00:00.0
NDE:PSTM@1d6c1d6c: setObject(): 4, 2012-01-28 00:00:00.0
NDE:PSTM@1d6c1d6c: setObject(): 5, 0.0014285714285714286
NDE:PSTM@1d6c1d6c: setObject(): 6, 2011-08-01 08:58:32.807
NDE:PSTM@1d6c1d6c: executeUpdate(): ExecuteTime: 1
NDE:PSTM@1d6c1d6c: close(): Open Time: 1
NDE:CONN@4d194d19: commit()
NDE:CONN@4d194d19: close()
EndAction: npt.gridUpdate TotalTime: 297 msecs

Outcomes