What does the Rate Matrix Extraction job do and how is it used?
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.
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.
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).
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 ensue 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 as per the details described in the following technical article: TEC528729 : Configuring and Scheduling Some of the Main Jobs
Also, refer to the following articles for more configuration details on this job.
Reference TEC439203 : On the 'Rate Matrix Extraction' job page, what does the parameter 'Extract Cost and Rate Information for the Scheduler' do?
Reference TEC439334 : On the 'Rate Matrix Extraction' job page, what do the parameters 'Prepare Rate Matrix Data' and 'Update Rate Matrix Data' do?
Reference TEC551863 : Clarity: How Should I Use The New Incremental Only Option For The Rate Matrix Extraction Job?
Reference TEC510858 : How often should I run the Investment Allocation Job?
Reference TEC521284 : Baseline a project populates baseline cost based on $1.00 when the project and ETC starts before the rate matrix actually starts