Resource Planning Workloads portlet warning "Time Periods do not exist"

Products

• Clarity PPM On Premise
• Clarity PPM SaaS

Issue/Introduction

When trying to set the Resource Planning workload portlet / report to show Planned and Actuals in Weeks as opposed to Months, the system is saying the time periods don't exist.

Cause

This is due to the time periods being outside the interanl time slice limits. 

Resolution

The out-of-the-box range available for weekly periods is as follows:

• 16 Weekly - 2 weeks in the past, the current week and 13 weeks in the future

Pre-approved internal timeslice range that can be used to extend weekly time slice dates:

(SaaS / GCP Customers please contact Broadcom support to request this extension)

• 45 Weekly - 4 weeks in the past, the current week and 40 weeks in the future

See: Warning: "The time periods requested do not exist" moving through periods on a TSV field for more details on limits for other period intervals. 

 

You can also use the Modern UX to see all time periods with no limitations.

In instances up to 15.9.2 you can use the Project Staff page to add per-period metrics for all your facts (ETC, ALC, AVL, ACT)

Starting with 15.9.3 you can also use the new Staffing Grid to show resources and investments with all the per-period metrics.

Refer to Staffing Enhancements under Clarity Release Notes for 15.9.3

 

 

Additional Information

To extend external slices found in Clarity->Administration->Time Slices See KB: Extend Weekly or other Period Type Time Slices

See also: 

• Time Scale Values Settings in Classic Clarity
• Warning: "The time periods requested do not exist.." and data exists in periods
• Warning: "The time periods requested do not exist" moving through periods on a TSV field

On Premise customers can run the below query to check what these internal slices are currently set to.  The From Date is the earliest date you can have on your TSV.

<D_AVL, W_AVL, M_AVL>

SELECT ID, field, REQUEST_NAME, FROM_DATE, NUM_PERIODS, TO_DATE, EXPIRATION_DATE next_rollover, 
TO_CHAR(REQUEST_COMPLETED_DATE, 'Dy DD-Mon-YYYY HH24:MI:SS') REQUEST_COMPLETED_DATE, 
LAST_UPDATED_DATE, LAST_UPDATED_BY, TABLE_NAME, is_active, is_synchronous 
from prj_blb_slicerequests 
where 1=1 
order by To_Date