Configure Resource Allocation Management page settings
The Resource Allocation Management page of a resource pool enables the pool manager to assess and manage resources and resource requests for a single resource pool. Administrators can configure the display settings for the Resource Allocation Management page and specify the calendar for calculating resource effort in the FTE unit.
Configure display settings
Administrators can use the following parameters to control the display settings of the Resource Allocation Management page such as:
- The maximum number of rows displayed on a single page
- The number of staffing profile positions displayed on a single page
- The units displayed in the Display Options dialog for measurements.
- The default unit displayed in the Display Options dialog for groupings and measurements
- The maximum number of resources for which the Projected Resource Pool Utilization summary is calculated
The following table lists the parameters that control the settings of the Resource Allocation Management page:
Parameter |
Description |
---|---|
ENABLE_PROMISE_RESOURCE_ALLOCATION |
Enable or disable the allocation of promised resources. Promised resources or allocations are resource allocations who are not specifically named or identified. They can be used when a resource is allocated but the resource is not defined in PPM (for example, a subcontractor) or to commit a resource and then assign a specific resource at a later time. If enabled but the user does not have the Resource Mgmt: Promise Unspecified Resources access grant, promised allocations are view-only. If enabled or disabled, promised allocations are used in all calculations (such as current demand and remaining capacity). Promised allocations may exist when this parameter is disabled if values were entered before the parameter was disabled. That is, the parameter was enabled, promised allocations were entered, and then the parameter was disabled. If disabled, any existing promised allocations are view-only. Default: false (disabled) |
RAMP_MAX_RA_PER_PAGE |
The maximum number of rows of data to display on a single page. Default: 200. Note: This parameter is specific to the Table view of the Resource Allocation Management page. |
RAMP_PAGE_SIZE |
The maximum number of staffing profile positions to display on a single page. Default: 20. Note: This parameter is specific to the Table view of the Resource Allocation Management page. |
RM_ALLOWED_EFFORT_TYPES |
The effort types from which the resource pool manager can select for the |
RM_DEFAULT_EFFORT_TYPE |
The default effort type. The resource pool manager can change the effort type by modifying the |
RM_DEFAULT_PERIOD_TYPE |
The default time period section. The resource pool manager can change the time period section by modifying the |
RM_MAX_RESOURCE_IN_POOL |
The maximum number of resources in a resource pool for which the Projected Resource Pool Utilization summary will be calculated. If the number of resources in a resource pool exceeds this number, you cannot load or view the Projected Resource Pool Utilization summary data. Default: 250. Note: This parameter is specific to the Table view of the Resource Allocation Management page. |
Specify the calendar for calculating effort in FTE units
Use the Use Regional Calendar When Converting Resource Effort feature toggle to control the calendar used when calculating resource effort in the FTE unit.
When this feature toggle is turned on, when calculating a resource effort in the FTE unit, the resource's regional calendar is used. When the feature toggle is turned off, the resource calendar is used.
This is a Beta feature and is available only in the Gantt view of the Resource Allocation Management page and the New UI of a staffing profile.
Note: Using this feature requires extra steps to update the database. If you want to enable this feature, contact support for details.
Every time you turn on or off this feature toggle, you need to stop the PPM server and run the following SQL against the PPM DB schema in order for the effort to be calculated using the current settings.
UPDATE RSC_RESOURCE_ASSIGNMENTS
SET SIMPLE_ASK_READY = 'N'
WHERE RESOURCE_ASSIGNMENT_ID IN (SELECT DISTINCT ASSIGNMENT_ID
FROM RSC_SIMPLE_ASK_ALLOCATIONS);
COMMIT;
We recommend that you save a copy of the RSC_RESOURCE_ASSIGNMENTS
table before you run the SQL above.