Time Slicing Sync runs for 35 minutes due to timesheets > 7 years old with null curves

Products

• Clarity PPM On Premise
• Clarity PPM SaaS

Issue/Introduction

When the system has many thousands of old timesheets with null curves over 7 years old, the Time Slicing Sync will fetch them to process them in batches, and then not actually process them due to date capped at 84 months. Time Slicing Sync will run for 30-35 minutes every time without any changes

 

STEPS TO REPRODUCE:

1. On a system with many old timesheets with null actual curves (Use the attached System)
2. Run the query:
   • SELECT COUNT(*)
   • FROM PRTIMESHEET
   • WHERE PRACTCURVE IS NULL
   •    OR ODF_NK_PRACTCURVE IS NULL;
3. Now run Time Slicing Sync job with default parameters (24 months)
4. Note it takes 35 minutes
5. Run Time Slicing Sync job, again it takes 35 minutes

In logs we can see:

• TimesheetActuals 13m 39s
• TimeSliceSyncTimesheetActualsSlicer 21m 45s

Expected Results: The Time Slicing Sync job to run within a reasonable time

Actual Results: Time Slicing Sync is very slow on TimeSliceSyncTimesheetActualsSlicer

Environment

Clarity 16.4.1

Cause

DE197101

Resolution

In review with Engineering

Workaround:

1. Run one instance of Time Slicing Sync with 84 months for Number of Prior Months for Limiting Timesheet Data
2. This will process all records 7 years back
3. If you still have a lot of old timesheets with null actual curve you may consider disabling feature DE181694_TIMESHEET_ACTUALS_SLICER
   Note this will disable the aggregation of PRTIMEENTRY daily hours into PRTIMESHEET.PRACTCURVE on the Timesheet record