How to force re-slicing when slice data is not correct for instaslices
search cancel

How to force re-slicing when slice data is not correct for instaslices

book

Article ID: 435309

calendar_today

Updated On:

Products

Clarity PPM On Premise Clarity FedRAMP Clarity PPM SaaS

Issue/Introduction

We have identified that the slice table odf_ssl_cst_dtl_cost contains inaccurate slice values. Could you please assist us in re‑slicing and correcting these entries?

Environment

Clarity 16.3.3, 16.4.1, 16.4.2 

Resolution

To reset the slice below steps needs to be followed 

  • Pause the Time slice and Time slice Sync Job 
  • Back up the table prj_blb_slicerequests
  • Option 1: Reset Specific Slice Request (ID 5000020 for Segment Cost) 
    UPDATE prj_blb_slicerequests SET request_completed_date = NULL,    request_status = NULL, last_updated_date = SYSTIMESTAMP,last_updated_by  = 1 
    WHERE id = 5000020  AND request_name = 'costplandetail::cost::segment';
  • Commit and Verify the reset by running the query 
    SELECT id, request_name, table_name, request_completed_date, request_statusFROM prj_blb_slicerequests WHERE id = 5000020;
    
  • Option 2: Reset Both Default and Segment Requests 
    UPDATE prj_blb_slicerequests SET request_completed_date = NULL, request_status= NULL, last_updated_date = SYSTIMESTAMP, 
    last_updated_by = 1 WHERE id IN (5000019, 5000020)  AND request_name IN ('costplandetail::cost::default', 'costplandetail::cost::segment');
  • Commit and Verify the reset by running the query 
    SELECT s.slice_request_id, COUNT(*)  AS slice_count, MIN(s.start_date)   AS earliest_start,  MAX(s.finish_date)  AS latest_finish,  MIN(s.created_date) AS earliest_created,    MAX(s.created_date) AS latest_created FROM odf_ssl_cst_dtl_cost s GROUP BY s.slice_request_id;
  • Verify Slice Request Completion: Request_completed_date should now be populated with the run timestamp
    SELECT sr.id,  sr.request_name, sr.request_completed_date, sr.request_statusFROM prj_blb_slicerequests sr 
    WHERE sr.table_name IN ('ODF_SSL_CST_DTL_COST', 'ODF_SL_CST_DTL_COST');
  • Validate Slice Totals Match Source Totals: Ideally returns no rows (all slice totals match source) 
    SELECT d.id AS detail_id,  d.total_cost AS source_total_cost,SUM(s.slice) AS sum_of_slices, d.total_cost - COALESCE(SUM(s.slice), 0) AS difference 
    FROM fin_cost_plan_details d LEFT JOIN odf_ssl_cst_dtl_cost s ON s.prj_object_id = d.id GROUP BY d.id, d.total_cost HAVING ABS(d.total_cost - COALESCE(SUM(s.slice), 0)) > 0.01ORDER BY ABS(d.total_cost - COALESCE(SUM(s.slice), 0)) DESCFETCH FIRST 50 ROWS ONLY;
    

Additional Information

For SaaS customers please reach out to Broadcom Support