Capacity/availability generation based on resource plan.

[Captain Gaming]

Hi team,

 the system is generating Capacity and Availability also for months prior to when the resource started working (e.g. we have someone starting in June 2025, a Resource Plan is created for a period June – December 2025, but the system is automatically also generating Capacity / Availability for the period January – May 2025).

The creation of availability and capacity records while creating a resource plan is handled via the following:
- Business Rule 'PopulateCapacityAndAvailability':
- Script Include 'RMMonthlyAggregate':
Consider checking the following functions from the above Script Include:
- updateCapacity
- this.populate()
- this._maxPopulatedDate()
As this is the OOTB Script include, If we make changes to this script include, what would be the impact - on tables/workbench and other functionalities?
Appreciate your support on the issue.

Regards,
Captain

[PaulaaO]

Hi - I assume this presents an issue in reporting or have there been occurrences where the resources was allocated prior to their joining the company? Maybe it's worth looking into Employee Profile and populate Start Date instead, to prevent that. 

I cannot speak of the exact impact on changing the script include, however looking at it and seeing how many functions it calls, seems to be one of those that need to be tested over and over again to make sure you won't break functionality. Capacity and resource aggregates in general are used widely in SPM (New PW, RMW, SPW) so I would be cautious.

I would consider the upgradeability impact - seems like an important component which means that you need to review it with every patch and upgrade to not miss out on new functionality if you plan to change it.

If past resource aggregates are not a deal breaker and you cannot use employee profiles I would leave it alone, but maybe other experts might have a different view on it 🙂