The HRMSi strategic reports rely on collected data, stored in summary tables, in order to run efficiently. You need to collect data from your transaction tables regularly so that the information in your reports is up to date. You collect the data by running the following pre-defined concurrent programs:
For information on concurrent programs, see: Overview of Concurrent Processing
All Analytics business areas and workbooks that use the competence level hierarchy gather information from the Competence Level Summary table. Use the HRI Load All Competence Level Hierarchy concurrent program to populate this summary table with your competence level hierarchy data.
The program collects pre-calculated data and stores it in the Competence Level Summary (HRI_CS_CMPTNC_LVL_CT) table ready for use by the workbooks.
The HRI Load All Competence Level Hierarchy concurrent program uses the following parameters:
Collect From Date
The earliest date required for competence level hierarchy information. The default is five years previous the first time you run this program, thereafter the value defaults to the previous Collect To Date.
Collect To Date
The latest date required for competence level hierarchy information. The default is the current date.
Full Refresh
If you set Full Refresh to Yes, the concurrent program deletes all information previously held in the summary table, and recalculates the competence level hierarchy for the entire collection date range specified (see the Collect From Date and Collect To Date parameters).
If you set Full Refresh to No, the concurrent program deletes none of the existing table information. The concurrent program incrementally updates the summary table with any competence level hierarchy changes that occurred within the collection date range specified (see the Collect From Date and Collect To Date parameters).
Run this concurrent program infrequently in full refresh mode, and frequently in incremental mode (Full Refresh = No) to capture and report on competence level hierarchy changes in your enterprise.
If a system failure occurs, you must restart the process.
All Analytics business areas and workbooks that use the job competence requirements gather information from the Competence Requirement Fact Summary table. Use the HRI Load All Competence Requirement Fact concurrent program to populate this summary table with your job competence requirement data.
The program collects pre-calculated data and stores it in the Competence Requirement Fact Summary (HRI_MB_CMPTNC_RQRMNT_CT) table ready for use by the workbooks.
The HRI Load All Competence Requirement Fact concurrent program uses the following parameters:
Collect From Date
The earliest date required for competence requirement information. The default is five years previous the first time you run this program, thereafter the value defaults to the previous Collect To Date.
Collect To Date
The latest date required for competence requirement information. The default is the current date.
Full Refresh
If you set Full Refresh to Yes, the concurrent program deletes all information previously held in the summary table, and collects competence fact information for the entire collection date range specified (see the Collect From Date and Collect To Date parameters).
If you set Full Refresh to No, the concurrent program deletes none of the existing table information. The concurrent program incrementally updates the summary table with any competence fact changes that occurred within the collection date range specified (see the Collect From Date and Collect To Date parameters).
Run this concurrent program infrequently in full refresh mode, and frequently in incremental mode (Full Refresh = No) to capture and report on competence level hierarchy changes in your enterprise.
If a system failure occurs, you must restart the process.
This program populates the time dimension folders in the Developer HRMSi - Administration - Analytic Dimensions business area with time information. So, for example, it populates the Time Year - (Dimension Level) folder with a list of years, and the Time Month - (Dimension Level) folder with a list of months.
Update Gregorian Hierarchy in the Time Dimension concurrent program has the following parameters:
Date From
Set this to the earliest date you need to see in your reports.
Date To
Set this to the latest date you need to see in your reports.
Do not use an unnecessarily wide date range, as this will impede performance.
Run this program when you need to collect future dates.
Run the HRI Load All Geography Category Structures concurrent program in order to populate the geography dimension with values. This concurrent program populates the location information stored in the HR_LOCATIONS_ALL table into a separate summary table.
The HRI Load All Geography Category Structures concurrent program has the following parameters:
Collect From Date
The earliest date required for geography information. The default is one month previous the first time you run this program, thereafter the value defaults to the previous Collect To Date.
Collect To Date
The latest date required for geography information. The default is the current date.
Full Refresh
If you set Full Refresh to Yes, the collection program purges previously inserted records and populates the dimension again for the entire collection date range specified (see the Collect From Date and Collect To Date parameters).
If you set Full Refresh to No, the program collects data in the incremental mode and that means it inserts new records without purging the table.
Oracle recommends that you run the HRI Load All Geography Category Structures concurrent program infrequently in full refresh mode, and frequently in incremental mode to reflect changes in the geography hierarchy in your enterprise.
If a system failure occurs, you must restart the process.
This concurrent program collects formula definitions for voluntary and involuntary separation reasons into a table to improve reporting performance.
This concurrent program has no parameters.
At implementation you need to run the HRI Load Separation Reasons Table concurrent program in order to initially populate the Separation Reasons table.
Thereafter, Oracle recommends that you run the HRI Load Separation Reasons Table concurrent program only after changes to the HR_MOVE_TYPE formula.
Note: If you have EDW implemented then it is recommended that you never schedule the HRI Load Separation Reasons Table process to run regularly. It should only be run on an ad-hoc basis when the full implications on the Workforce Separation fact re-collection are understood and accepted.