What does the Rate Matrix Extraction job do and how is it used?
Release: All Supported Clarity releases
The Rate Matrix Extraction (RME) job takes the resources who are assigned to projects and tasks on those projects, and finds out what the applicable rates and costs are for the duration of their assignment. Since that information is coming from financial rate matrices, you need to run this job if the matrix has changed. The data populated by this job is primarily used by Baselines, the Post Timesheets job and the Update Earned Value Costs Totals job (or 'Update Costs Totals' actions within a project). You also need to run this job if you have created or updated project dates, team members and task assignments.
Description of RME Job Parameters and different combinations of them for different use cases:
Full RME with TEAM RATES ONLY
Incremental (with and without Scheduler Cost and Rates:
Incremental with Team Rates Only
As a rule of thumb, we recommend that you run this job at least once a week prior to posting timesheets, but no more than once a day. For a system size with a large dataset, you should expect the job to take a fair amount of time and consume database resources. We recommend scheduling it every few days to run at night when there is not a whole lot of use activity going on. Running the job during business hours can make the system slow for all connected users.
Example: Split up the job with different combinations of options to prepare the data and update the data just in time for posting timesheets or working with project baselines.
The 'Datamart Extraction' job utilizes some of the data that the 'Rate Matrix Extraction' job creates. Therefore, it is recommended that the 'Rate Matrix Extraction' job is executed successfully prior to the execution of the 'Datamart Extraction' job and prior to execution of the 'Post Timesheets' job and prior to the execution of the 'Update Earned Value Costs Totals' job.
Regarding the "Extract Cost and Rate Information for the Scheduler " check box in the Job page, it will impact performance of the job. If the flag is checked then the rates for the resources who are assigned to a project are calculated for beyond project start and end date. These calculations add time to the processing for the Rate Matrix job. The additional data beyond the project start and end date is used by the scheduler (OWB & MSP where the user can shift the project start and end dates).
HOW ARE RATES DERIVED?
After the Rate Matrix Extraction job runs, the NBI_PROJ_RES_RATES_AND_COSTS populates with various rows based on resource/project/task details.
For all the Earned Value metrics (baseline values, acwp, etc cost) the row that is used is the -1 row. This row comes from the team settings.NOTE: If the rates are not updated before posting timesheets or creating baselines, the costs may not be what is desired. If the data in the extraction table does not exist for a date range used in a baseline or timesheet posting, the application will use a $1 rate. Alternatively, if you have modified rates and modified projects and the extraction table is not updated, an incorrect rate could be used for the baseline or timesheet posting.
To ensure there is no conflict between the Rate Matrix Extraction job and other jobs in the application, it is recommended to update the job definition for 'Incompatible Jobs' is updated