This article provides detailed steps for troubleshooting aggregate-related issues and using Resource Diagnostics to identify data anomalies.

1.How to proceed when the schedule is updated, but the aggregate tables do not reflect hours?

Scenario-1:

In Resource Management, schedules are cached to improve the performance, please clear the cache when there is a change in the schedule and then update the capacity.

Scenario-2:

Dates on the schedule are not completely covering the duration of capacity you are looking for. Review the dates on the schedule - The date value on ‘Start date time’ field is the start date of the schedule and ‘Repeat until’ field is the end date of schedule.

2.What to do when capacity is not reduced after defining a holiday in the schedule?

Scenario-1:

If holiday is added in Schedule Entry, then record type must be Excluded.

Scenario-2:

If holidays are in Child schedule, then Child schedule type must be Include.

3.How to resolve the issue of capacity splitting between days?

Check the Time zone field on schedule.

The Time zone field value on the schedule must be Floating. If the value is not Floating,the Time zone field value must be same as that of the Time zone field value of the user record for which the schedule is attached, or for the user who updates the aggregates.

4.How to allocate resources only up to user’s capacity?

If you do not want to over-allocate a user, always use Resource Finder for confirming / allocating the resource plans. This is because resource finder restricts the confirmation / allocation only up to the scheduled hours whereas form or workbench confirmation / allocation will attempt to allocate up to 24 hours.

5.How to avoid the situation of having left-over capacities when users schedules are in decimal?

Resource allocations use the calendar event duration (‘com.snc.resource_management.allocation_interval_minutes’) property to create allocations with a decimal value.

If the value of this property is set to 60 minutes, the allocation is given to the 60-minute block.

If the value of this property is set to 30 minutes, and 1 hour needs to be allocated to the user, the allocation is divided into the two 30-minute blocks when the user is available.

If User’s Scheduled Hours, ends with	Calendar Event Duration, value should be set to
0.5	30
0.25/0.5/0.75	15
0.2/0.4/0.6/0.8	12
0.1,0.2….	6

NOTE: It is recommended to set this property to 60. If your organisation is keen in tracking time in minutes, it can be set to a lower value.

If the scheduled hours are not divisible by the calendar event property, then there will be a loss of few hours for each day.

Example: User’s per day scheduled hours are 8.5 and if the calendar event property value is 60.

In this case the maximum allocated hours for each day will be 8, resulting in a loss of 0.5 hours per day.

6.How to proceed when there is over or under allocation after allocating for the FTE or Person Days plan?

The ’Average Daily FTE Hours’ field value on the User or Group record should be same as the scheduled hours for a day. If the values are not same, then the resources might get over or under allocated when resource plan of FTE or Person days type is allocated.

The*Average Daily FTE Hours* (‘com.snc.resource_management.average_daily_fte’ )property value is used as the full-time equivalent if no value is specified in the ‘Average Daily FTE Hours’ field on the user or group record.

Resource Diagnostics:

Resource Diagnostics can be run by users with the ‘pps_admin’ role to detect corrupt aggregates and daily allocation data.

Following are resource management diagnostics:

-Identifies project-related resource allocation dailies without a top task.

• Duplicate aggregates for users

-Identifies ‘project_allocated’ or ‘project_confirmed’ category entries in all resource aggregate tables with empty task.

• Aggregate issues with demand to project conversion (Available from ‘Quebec’ release onwards)

-Identifies all resource allocation daily and all resource aggregate table entries that are still pointing to demand after project conversion.

• Top task on allocations is no longer a top task (Available from ‘Quebec’ release onwards)

-Identifies all resource allocation daily entries that have top task pointing to previous top task after reparenting project.