Time Slicing tables ODF_SL_TOTAL% missing for custom slices

Products

• Clarity PPM SaaS
• Clarity PPM On Premise

Issue/Introduction

When trying to set up a custom slice request TSV on Resource Total Allocation Usage, Hard Allocation, ETC, etc. the Time Slicing job would fail and the slice request table is not available in the database

STEPS TO REPRODUCE:

1. Connect to Clarity Classic - Administration - Time Slices
2. Create a new custom Time Slice request as below:
3. For Item pick Resource::Resource Total Allocation
4. Save
5. Now check the table PRJ_BLB_SLICEREQUESTS - see the table for this slicerequests is ODF_SL_TOTAL_ALLOC_CURVE
6. Run Time Slicing job
7. Try selecting from ODF_SL_TOTAL_ALLOC_CURVE

Expected Results: To be able to query table ODF_SL_TOTAL_ALLOC_CURVE for the requests and the Time Slicing job to run well

Actual Results: ORA-00942: table or view does not exist, and the Time Slicing job fails with error:

Caused by: Error : 6550, Position : 0, Sql = BEGIN PRJ_BLB_SLICE_MERGE_SP(:1 ) ; END;, OriginalSql = {call PRJ_BLB_SLICE_MERGE_SP(?) }, Error Msg = ORA-06550: line 1, column 82:
PL/SQL: ORA-00942: table or view does not exist
ORA-06550: line 1, column 7:
PL/SQL: SQL Statement ignored
ORA-06550: line 1, column 324:
PL/SQL: ORA-00942: table or view does not exist
ORA-06550: line 1, column 249:
PL/SQL: SQL Statement ignored
ORA-06550: line 1, column 566:
PL/SQL: ORA-00942: table or view does not exist
ORA-06550: line 1, column 490:
PL/SQL: SQL Statement ignored
ORA-06550: line 1, column 949:
PL/SQL: ORA-00942: table or view does not exist
ORA-06550: line 1, column 920:
PL/SQL: SQL Statement ignored
ORA-06512: at "CLARITY1622.PRJ_BLB_SLICE_MERGE_SP", line 128
ORA-06512: at line 1
Using input: 
{tableName=ODF_SL_TOTAL_ALLOC_CURVE}

Missing tables:

• ODF_SL_OPLALC
• ODF_SL_OPLHALC
• ODF_SL_TOTAL_ACTUALS_CURVE
• ODF_SL_TOTAL_ALLOC_CURVE
• ODF_SL_TOTAL_ETC_CURVE
• ODF_SL_TOTAL_HARD_ALC_CURVE
• ODF_SL_TOTAL_USAGE_CURVE

Environment

Clarity 15.x,16.x

Resolution

This is DE94912, is a design limitation and will be addressed as a part of a future user story / enhancement

Workaround: Use a different time slice for your needs - engage Support if need advice