Oracle HRMS provides a range of inquiry and reporting mechanisms to meet the needs of different users:
Predefined Discoverer Workbooks that you can use directly, or edit to meet your own reporting requirements.
Discoverer End User Layer folders that you can use to create your own Discoverer Workbooks.
Inquiry windows (including folders)
Predefined reports that can be scheduled and grouped for periodic processing
QuickPaint, to create your own online inquiries and reports about people and assignments
Multilingual reporting for some reports
Use of desktop tools for reporting or editing HRMS data. For example, you can use Application Data Exchange (ADE) to download information to a spreadsheet, and then upload the modified data to HRMS.
Oracle Discoverer is a data query and analytical tool that enables you to perform detailed analysis of the human resources issues that interest you. Discoverer uses an End User Layer (EUL), which is based on a series of business views, to build worksheets and workbooks that report on the data from the underlying HRMS application. There are a number of predefined workbooks, which you can refine by specifying worksheet parameters; you can also build your own workbooks.
Use the following responsibility to access the predefined Discoverer workbooks:
HRMS Ad-Hoc Reporting – Administrator
This responsibility provides access to the HRMS Ad-Hoc Reporting – Administrator menu, which has the following structure:
HRMS Ad-Hoc Reporting – Administrator
Human Resources
Recruitment
Training
The menu structure reflects the functional areas you need to install in order to retrieve data from the workbooks.
HRMS contains a predefined End User Layer (EUL) where the data in the underlying database tables is organized in Discoverer as folders. The folders are organized into business areas. You can use this EUL to create your own Discoverer Workbooks.
Use the HRMS Ad-Hoc Reporting – Administrator responsibility to access the following Discoverer business areas:
HRMS – Administration – Oracle Human Resources
HRMS – Administration – Oracle Human Resources (Lists of Values)
HRMS – Administration – Oracle Training Management
HRMS – Administration – iRecruitment
HRMS – Compensation and Benefits
HRMS – General Employment Practices
HRMS – Training Management
HRMS – Implementation and Data Set-Up
HRMS – Workforce Budgeting
HRMS – Workforce Composition and Activity
HRMS – Workforce Development and Performance
HRMS – Workforce Recruitment
HRMS – Workforce Separation
HRMS – Workforce Utilization and Productivity
HRMS – Workforce Costing
For descriptions of these Discoverer business areas, see: Discoverer End User Layer Business Area Descriptions
Oracle HRMS includes some inquiry windows to meet the most common online reporting requirements. In these windows, you typically enter selection criteria in the first block then choose the Find button to view a list of people, assignments, or other entities that match your criteria. Some of these windows use folders to display the information retrieved by your criteria.
Folders are online views that you can configure. By default, the folder block in an inquiry window displays all records matching your inquiry and all fields available within the folder. However, you can create your own folders to display a subset of these records and fields. You can also choose the field labels, their size and order, and the sort sequence of the retrieved records.
For example, in the Assignment Folder window, you could create a folder called Sales Employees by Grade. This folder has the query criteria Organization = "Sales", and it is sorted by grade.
There are a number of predefined reports that you can use immediately without any further set up. They have a predefined format but you can choose which records to view by entering a set of parameters when you submit the report.
You can also create your own reports using Oracle Reports or SQL*Plus or another tool of your choice. You can register them with Application Object Library. This means you can run them from the standard Submit Requests window, and you can schedule them in report sets with other reports and processes.
Oracle HRMS enables you to print reports in the language of your choice.
You can select in which language the following reports are printed:
Full Person Details
Full Applicant Details
Full Assignment Details
Full Work Details
See: Submitting a Request, Oracle Applications User's Guide
Payroll reports are usually submitted in the language of your Business Group, for example the US Check writer can only be printed in American English and the GB Deposit Advice can only be printed in English. However, you may be able to print payroll reports in multiple languages if your localization team has created legislation specific reports for you to use.
Note: The default HRMS payrolls for the US and UK can only be run in English.
You can use Oracle Application Data Exchange (ADE) to download information from the HRMS database to a spreadsheet for analysis and manipulation. For example, you can download data on current and proposed salaries for a group of employees. You can adjust the salary proposals in the spreadsheet, or enter new ones, and upload the revised data to the database. The ADE upload process reports any errors and ensures that only valid data is saved in the database.
To download information from a form to a spreadsheet using ADE, your system administrator needs to create a style in ADE. The style defines the form it is used for, the responsibilities that can use it, and the columns (or fields) to be downloaded. You determine which records are downloaded by running a query in the form before launching ADE.
A style for downloading salary proposals is predefined.
See Using Application Data Exchange.
QuickPaint is a powerful and flexible tool to design reports about assignments in the format you require. You can include the following sorts of information in a QuickPaint report:
Personal information
Contact information
Assignment information
Application information
Compensation and benefit information
Descriptive flexfield information
Once you have designed a QuickPaint report, you and other users can run the report online for any assignment or set of assignments. You can view the results online or print them.
Using the standard QuickPaint Report window, you can run the report for an assignment or an assignment set. The assignments can be held by current employees or applicants.
Your system administrator can create configured versions of this window to restrict the reports you can run and the people you can report on. A configured version might be subject to one or more of the following restrictions:
Report on one person type only (employees OR applicants).
Run one report only.
Report on single assignments only, or report on assignment sets only.
If the window is subject to the third type of restriction, it will look different to the standard version since it will contain either the assignment region or the assignment set region, but not both.
You can add attachments to a large number of HRMS records. Examples of attachments are word processed documents, Web pages or video images.
Oracle HRMS provides a range of inquiry and reporting mechanisms to meet the needs of different users.
The information held in Oracle HRMS is an extremely valuable resource for your enterprise. You can use the same information in a variety of different ways depending on your business purpose. For example, you can use Oracle HRMS information in support of each of the following business activities:
Performing a full range of HR functions on a day-to-day basis
Reporting on HR activities
Performing what-if exercises to determine the viability of alternatives scenarios
Performing strategic planning with the Business Intelligence System
You can extract details about a single employee or a group of employees. Particular examples are:
Selecting an employee or a set of employees for HR processing
Extracting HRMS information to produce standard letters
Viewing organization hierarchies and position hierarchies
Viewing a historical record of previous changes
When you are reporting on activities using HRMS you may want to use each of the following reporting options depending on your business purpose:
Define a report using parameters that you supply
Run a predefined report
Specify the intervals at which a report should run
Combine several reports into a set so that they can be run at the same time
Run a predefined Discoverer workbook.
Create a Discoverer workbook based on the predefined End User Layer.
Yes, you can run HRMS in more than one language on a single database. This means that you can enter and report on information using more than one language. For example, your base, or source, language could be French, but you could also install German and English. You would then be able to enter and produce reports in German and English.
HRMS uses Oracle Discoverer to create workbooks containing worksheet reports and graphs. You can amend these workbooks to meet your enterprise's specific requirements. You can also use Discoverer User to create your own workbooks, based on the supplied Discoverer End User Layer (EUL).
You can find full instructions on developing the Discoverer EUL and creating and maintaining Discoverer workbooks in the Oracle Discoverer Plus User's Guide and the Oracle Discoverer Plus Administrator's Guide
Each workbook holds a set of related worksheets. A worksheet is simply a report that returns data from a SQL query. The workbook may contain calculations and conditions that can restrict the report in various ways.
You can access Discoverer workbooks from the Self-Service menu. You can use parameters to specify the data range you want in your report. The worksheets are displayed in Discoverer Viewer.
The end user layer (EUL) comprises a set of business areas, containing folders. The folders contain items that map to table columns. The folders can map to one or more database table. The folders present that data in a structure that is suitable for reporting.
There are two types of business areas: administrative and functional. The administrative business areas contain all folders. The purpose of the administrative areas is to give report developers access to all the folders to enable them to create ad hoc reports.
The functional business areas contain folders that support reporting for a specific business function, such as iRecruitment. Folders can exist in one or more functional business area. Workbooks are typically based on folders from one functional business area. You can grant users access to one or more functional business area, depending on which reports they require.
The HRMS Discoverer End User Layer provides folders that access the data from the HRMS transactional tables. You can use these folders to create your own Discoverer reports. The End User Layer organizes the folders into two types of business areas: Administrative, and Functional.
Use the Administration business area to produce detailed ad hoc reports specific to the needs of your enterprise.
The HRMS – Administration – Oracle Human Resources business area is a composite set of Discoverer folders focusing on different entities of the Oracle Human Resources system, such as salaries, benefits, jobs, grades and assignments. The related Lists of Values folders are in a separate business area.
Use the HRMS – Administration – Oracle Human Resources business area to produce detailed ad-hoc reports specific to your human resources needs.
The HRMS – Administration – Oracle Human Resources (Lists of Values) business area contains all the Lists of Values folders relating to the Oracle Human Resources system. The folders in this business area do not appear anywhere else.
This business area is for internal use only.
The HRMS – Administration – Oracle Training Administration business area is a composite set of Discoverer folders focusing on different entities of the Oracle Training Administration system, such as training events, training activities, student enrollments and event resources.
Use the HRMS – Administration – Oracle Training Administration business area to produce detailed ad-hoc reports specific to your training administration needs.
The HRMS – Administration - Oracle iRecruitment business area focuses on the vacancy and job posting details, recruitment activities, candidate details and applicant information within your enterprise.
The HRMS – Administration - Oracle iRecruitment (List of Values) business area contains all the Lists of Values folders relating to the Oracle iRecruitment. The folders in this business area do not appear anywhere else.
This business area is for internal use only.
The HRMS - Administration - Oracle Payroll (Core) business area contains folders to enable you to produce ad-hoc reports on action parameters, balance attributes, element classifications, payroll actions and so on.
This business area also contains a generic folder that can be used by any legislation to create and use complex sub folders.
The HRMS - Administration - Oracle Payroll (List of Values) (Core) business areas contains the list of values for elements, input values, organization payment methods and so on.
The HRMS - Administration - Oracle Payroll (US) business area contains folders to enable you to produce ad-hoc reports for US payroll processing, for example, on costing, RetroPay and so on.
The HRMS - Administration - Oracle Payroll (IN) business area contains a folder that enables you to produce payroll run results and other ad hoc reports.
These business areas are grouped by function. They enable you to restrict users to a functional area in which they can develop or access workbooks specific to their functional role.
The HRMS – Compensation and Benefits folders focus on entities specific to employee remuneration. From these folders you can produce ad-hoc reports summarizing and detailing such information as salary against grades and jobs.
The HRMS – Employee Pay Detail folders contain information about employee payment history and the composition of employee payments.
The HRMS – General Employment Practices folders focus on entities specific to employment practices. Using this functional business area you can produce ad-hoc reports covering such issues as equal opportunities, minority employment, disability accommodations, work related injuries, health and safety, disciplinary actions, grievances and interpersonal conflicts.
The HRMS – Implementation and Data Set-up folders provide information on system setup and data.
The HRMS – Payroll Configuration folders contain information about payroll setup and configuration. You can use this information to produce ad-hoc reports on the defining characteristics of a payroll, or to compare the setup of several payrolls.
The HRMS – Payroll Process Result folders contain information about the results of each payroll process that you run. You can use this information to produce ad-hoc reports identifying completed and pending processes.
The Payroll Actions With Run Results and Net Pay Detail folder contains the payroll run results. You can use this information to reconcile your payrolls, verify correctness of your payroll runs, and produce other standard reports.
The Payroll Run Results With Net Pay folder contains the payroll run results. You can use this information to reconcile your payrolls, verify correctness of your payroll runs, and produce other standard reports.
The HRMS - Person Information - Human Resources folder contains Person, Assignment and Organization related information.
The HRMS - Organization Information - Human Resources folder contains information that is linked to folders in HRMS Administration - Oracle Human Resources (IN). You can use this information for creating organization-based reports. All the folders in this business area are grouped into a single functional area.
The HRMS - Reports Information - Oracle Payroll folder contains information on payslips. All the folders in this business area are grouped into a single functional area.
The HRMS Training Management folders relate to the management of training, where the enterprise is a training provider.
The HRMS – Workforce Budgeting functional business area covers all aspects relating to creating budgets. The folders contain budget information together with assignment, job, location, organization assignment, and supervisor information.
The HRMS – Workforce Composition and Activity folders show how employees are spread throughout various areas such as jobs, geography, minority groups, and business groups. Activity information is concerned with changes in the workforce (for example, organization transfers).
The HRMS – Workforce Costing business folders focus on costs associated with the workforce, such as the cost of training, direct payments to employees, and assignment costings.
The HRMS – Workforce Development and Performance folders focus on issues such as competency information, internal training and success.
The HRMS – Workforce Recruitment folders provide information on workforce recruits, such as competencies, employment history, education, and qualifications. It also provides analysis of employee movement within and between organizations.
The HRMS – Workforce Separation folders provide information on staff turnover, including categorizing the reasons people leave or move within an organization.
The HRMS – Workforce Utilization and Productivity folders focus on issues such as how well the workforce is utilized (working hours, absence) and how productive they are.
The HRMS - Pay Period Archived Data - Oracle Payroll (US) folders provide information on federal, state and local tax archives.
Many Workforce Intelligence 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 pre-defined concurrent programs, as described below.
For information on concurrent programs, see: Overview of Concurrent Processing, Oracle Applications Developer's Guide
This program creates the organization hierarchies on which HTML reports are based. When you run this program, it collects organization hierarchy structures into the HRI_ORG_PARAMS and HRI_ORG_PARAM_LIST tables to improve reporting performance.
Prior to running the concurrent program, ensure you have one hierarchy marked as the primary hierarchy. If no hierarchy is nominated as the primary hierarchy, BIS Load Organization Hierarchy Summary Table will not pick up your hierarchies.
Add the BIS Load Organization Hierarchy Summary Table concurrent program to a request group using the Request Group window. The request group must be used by the responsibility that runs the concurrent program.
Schedule and run the request group using the Submit Request window.
Important: After running each BIS Load Organization Hierarchy Summary Table request you are advised to run the system administrator request Gather Schema Statistics for the HRI schema. This will ensure that you gather statistics from the BIS Load Organization Hierarchies request.
There are no parameters for this program.
You must also run this program when there are changes to organization hierarchies and you want to reflect them in your reports. Reports will not display accurate information if you do not run this program periodically to update the summary tables.
You should therefore ensure that the concurrent program is run at regular intervals, for example, every day or every week in order to collect any changed data.
If a system failure occurs, you must restart the program.
This concurrent program collects your organization hierarchy structures into the HRI_ORG_HRCHY_SUMMARY table to improve reporting performance. It will perform a full refresh of all the data.
There are no parameters for this program.
Run the HRI Load All Organization Hierarchy Versions concurrent program at implementation.
You must also run this program when there are changes to organization hierarchies and you want to reflect those changes in your reports. Reports will not display accurate information if you do not run this program periodically to update the summary tables.
You should therefore ensure that the concurrent program is run at regular intervals, for example, every day or every week in order to collect any changed data.
If a system failure occurs, you must restart the program
The HRI Load All Supervisor Hierarchies concurrent program populates the Supervisor Hierarchy Summary Table with current and historic supervisor hierarchy data
Note: The program only collects the relationships between primary assignments in order to structure the supervisor hierarchy.
HRI Load All Supervisor Hierarchies concurrent program has the following parameters:
Full Refresh – Yes / No
If you set Full Refresh to Yes, the program will delete all information previously held in the summary table, and will recalculate the supervisor hierarchy history for the entire collection date range specified (see the Collect From Date / Collect To Date parameters).
If you set Full Refresh to No, the program will delete none of the existing table information. It will update the summary table incrementally with any supervisor hierarchy changes that occurred within the collection date range specified (see the Collect From Date / Collect To Date parameters).
The program runs faster if you set the Full Refresh to No.
The default value of this parameter is Yes the first time the program is run, and No thereafter.
Collect From Date / Collect To Date
These parameters define the start and end dates of the collection range. The program will store any supervisor changes occurring (date effectively) between these dates in the summary table.
This date range initially defaults to be the last five years. Thereafter the Collect From Date defaults to the last Collect To Date and the Collect To Date defaults to the current date
At implementation, run the concurrent request, HRI Load All Supervisor Hierarchies, with the following parameter values:
| Parameter | Implementation Value |
|---|---|
| Collect From Date | The earliest date required for supervisor information (default is five years previous) |
| Collect To Date | The current date (default) |
| Full Refresh | Yes (default) |
After implementation, run the HRI Load All Supervisor Hierarchies concurrent program infrequently in full refresh mode, and frequently in incremental mode to capture and report on supervisor hierarchy changes in your enterprise (see the discussion on Full Refresh, above).
If a system failure occurs, you must restart the program
Loops in the supervisor hierarchy will cause the program to print an error message in the concurrent program log. A loop will occur if, for example, A supervises B, B supervises C, and C supervises A. In this case, the program will enter the person-IDs of the supervisors in the loop in the log.
Corrupt data may also produce error messages in the concurrent program log, for example, where an assignment has two date-tracked records that overlap, as shown in the table below:
| Assignment Number | Start Date | End Date | Organization |
|---|---|---|---|
| 10 | 1 Jan 2000 | 24 Apr 2000 | Organization 1 |
| 10 | 1 Apr 2000 | 31 Dec 2000 | Organization 2 |
In this example, the assignment records overlap on 1st to 24th April. To correct this situation, you should find the correct date of the organization transfer, and update the assignment record. If, for example, the transfer occurred on the 25th April, the data should be corrected to:
| Assignment Number | Start Date | End Date | Organization |
|---|---|---|---|
| 10 | 1 Jan 2000 | 24 Apr 2000 | Organization 1 |
| 10 | 25 Apr 2000 | 31 Dec 2000 | Organization 2 |
Many reports use Workforce Measurement Values (WMVs), for example, Workforce Losses, Workforce Gains, and Workforce Count. WMVs include headcount and full-time equivalent (FTE) assignment budget values. Calculation and collection of this data could involve repeatedly running FastFormula for each assignment every time a report is run, which is expensive and increases the time taken to display the report.
To reduce the number of times the FastFormula is run, a summary table exists which holds a history of the FTE and headcount WMVs for all assignments over the collection date range. The table ensures you are getting the best possible performance from your reports.
You need to populate the summary table with the WMVs used by your reports. To populate the table, you need to run the concurrent program HRI Load Workforce Measurement Value History.
The HRI Load Workforce Measurement Value History request is not used by all reports; some reports still calculate WMV at the time of running.
The concurrent program HRI Load Workforce Measurement History uses the following parameters:
Full Refresh – Yes / No
If you set Full Refresh to Yes, the program will delete all information previously held in the summary table, and will recalculate the WMV history for all assignments over the entire collection date range specified (see the Collect From Date / Collect To Date parameters). Use this mode the first time you run the program.
If you set Full Refresh to No, the program will delete none of the existing table information. It will update the summary table incrementally with any WMV changes that occurred within the collection date range specified (see the Collect From Date / Collect To Date parameters).
The program will run faster if you set the Full Refresh to No.
The following constraints apply:
If WMVs are updated in the forms interface, the summary table will not reflect this change until you re-run the program, and only if you include the effective date of the correction (not the actual date the correction was made).
The summary table will not reflect historical changes if you run the program in incremental mode.
For example, if the collection date range includes today but does not include last year, the program will not pick up changes made today that update WMVs date-effectively last year.
The program will only transfer corrections to WMV data (as opposed to updates, where historical data is retained) to the summary table when you run the program in full refresh mode.
Due to these constraints you should run the full refresh program weekly or monthly to ensure that the WMV history table is correct. If there are no corrections, deletions, or historical/backdated changes, (for example, if you implement WMVs by a FastFormula only, and do not directly store values for an assignment using the forms interface) running the incremental update at consecutive time periods will keep the table up to date.
The default value of this parameter is Yes the first time you run the program, and No thereafter.
Collect From Date / Collect To Date
This parameter defines the start and end dates of the collection range. The program stores any WMV changes occurring (date effectively) between these dates in the WMV summary table.
This date range initially defaults to be the previous year. Thereafter the Collect From Date defaults to the last Collect To Date and the Collect To Date defaults to the current date.
Collect FTE (Yes / No)
This parameter defines whether or not you wish to collect or update the WMV summary table with Full Time Equivalent values.
The default value for Collect FTE is Yes.
Collect Headcount (Yes/No)
This parameter defines whether or not you wish to collect or update the WMV summary table with Headcount values.
The default value for Collect Headcount is Yes.
On implementation, run the concurrent request HRI Load Workforce Measurement Value History with the following parameters:
| Parameter | Implementation Value |
|---|---|
| Collect From Date | The earliest date required for WMV information. |
| Collect To Date | The current date (default) |
| Full Refresh | Yes (default) |
| Collect FTE | Yes (if FTE is used in reporting) |
| Collect Headcount | Yes (if Headcount is used in reporting) |
Thereafter, Oracle recommends that you run the HRI Load Workforce Measurement Value History concurrent program monthly or weekly to capture and report on workforce measurement value changes in your enterprise (see discussion on Full Refresh below).
If a system failure occurs, you must restart the program.
Some US specific Discoverer workbooks use a 'Vets, EEO, AAP, OSHA, Multi Work Sites' hierarchy. They require information about the current generic hierarchy.
The concurrent program HRI Load All Generic Hierarchy Versions calculates the required data and stores it in the Generic Hierarchy Summary table ready for use by the workbooks. These workbooks will only work if you have set up these generic hierarchies and run this concurrent program.
For further information on HRMS Generic Hierarchies see EEO-1 and VETS-100 Reporting in Oracle HRMS, available on My Oracle Support (formerly MetaLink).
The HRI Load All Generic Hierarchy Versions program collects all generic hierarchies of type “Vets, EEO, AAP, OSHA, Multi Work Sites” (system code FEDREP) across all your business groups. The program stores the data in the Generic Hierarchy Summary table.
The HRI Load All Generic Hierarchy Versions concurrent program has no parameters.
Run the HRI Load All Generic Hierarchy Versions concurrent program at implementation.
You must also run this process when there are changes to the generic hierarchies and you want to reflect those changes in your reports. Reports will not display accurate information if you do not run this process periodically to update the summary tables.
You should therefore run the concurrent program at regular intervals, for example, every day or every week in order to collect any changed data.
If a system failure occurs, you must restart the process.
Workforce is one of the key areas of your enterprise you can investigate using the Workforce Intelligence reports.
Workforce is not necessarily a count of the number of employees within your enterprise. Instead, it is a count based on employee assignments and budget measurement type.
You can set budget measurement types and assignment measurement values for each employee assignment within Oracle Human Resources. When the report or performance measure runs, the workforce is calculated using this budget value.
If you have not entered a default budget measurement type and an assignment budget value, and a Business Group default does not exist, then the reports count workforce using Oracle FastFormula.
HRMSi provides two predefined formulas that reports use to calculate workforce if you do not enter assignment budget values for assignments. They are described below.
If you want to customize how workforce is counted, use Oracle FastFormula to copy and amend the predefined formulas. Reports will then use your customized version instead of the predefined formula. See: Customizing Workforce Calculations using Oracle FastFormula
Note: Reports only use Oracle FastFormula to calculate workforce if you do not have an assignment budget value entered for an assignment. Oracle recommends setting up an assignment budget value for each employee assignment.
HRMS provides two predefined workforce formulas:
TEMPLATE_HEAD
TEMPLATE_FTE
The TEMPLATE_HEAD formula calculates the headcount value as follows:
If the assignment is a primary assignment, a default value of 1 is used. Otherwise, the assignment is ignored.
The TEMPLATE_FTE formula uses the employment category to calculate the Full Time Equivalent value as follows:
If the employment category is Full Time, the value is taken as 1.
If the employment category is Part Time, the formula uses the standard working hours for the assignment and compares them to those on either the position, organization, or business group to determine the value for the full–time equivalent.
If the employment category is not set up, the assignment is ignored.
The TEMPLATE_FTE formula uses the predefined meanings set up for the Lookup types EMP_CAT and FREQUENCY.
The following table lists the lookup codes and meanings for EMP_CAT (Employment Category).
| Lookup Code | Lookup Meaning |
|---|---|
| FR | Full-time-Regular |
| FT | Full-time-Temporary |
| PR | Part-time-Regular |
| PT | Part-time-Temporary |
The following table lists the lookup codes and meanings for FREQUENCY.
| Lookup Code | Lookup Meaning |
|---|---|
| D | Day |
| HO | Hour |
| W | Week |
If you update a lookup meaning, you must copy and amend the predefined TEMPLATE_FTE formula.
For example, the predefined TEMPLATE_FTE has the following lines, which reference two of the Lookup meanings for EMP_CAT:
/* If assignment is Full Time then FTE=1 */
IF hri_asg_employment_category_code = 'FR'
OR hri_asg_employment_category_code = 'FT' THEN
fte = 1
However, you should consider performance before customizing the TEMPLATE_HEAD formula. The TEMPLATE_HEAD FastFormula calculates the Headcount value based on whether the assignment is primary or not (1 if primary, 0 otherwise). In some cases, a report can determine this value directly, and so does not need to use the formula. This can improve report performance considerably where a large number of FastFormula calculations would be required.
This bypass is not available if you are using a customized version of the TEMPLATE_HEAD FastFormula as the logic may vary.
Typically you set up an assignment budget value for each employee assignment, and reports use this value to calculate workforce numbers. However, if you do not enter an assignment budget value for an assignment, reports use a formula to calculate workforce.
By default reports use the TEMPLATE_FTE and TEMPLATE_HEAD formulas. Copy and amend these formula templates to change the way you calculate workforce, or to report on other budget measurement types.
Important: If you are using the default template formulas, this does not need to be copied to other business groups.
Workforce Calculation Formulas for DBI for HRMS
Depending on the requirements of your enterprise, to calculate workforce, you can use a formula for each business group or a global formula for the entire enterprise.
You can create:
A BUDGET_HEAD or BUDGET_FTE formula for each business group in your enterprise.
A GLOBAL_BUDGET_HEAD or GLOBAL_BUDGET_FTE formula for the entire enterprise. DBI for HRMS uses the global formula if business group formulas do not exist. If you have not defined a global formula either, DBI for HRMS then uses the Budget Measurement Type values. You must define the global formula in the delivered Setup Business group.
Important: Global formulas affect the workforce calculation in all HRMS intelligence reports.
Base the formulas on the existing TEMPLATE_HEAD and TEMPLATE_FTE formulas.
To configure workforce calculations
Use the Formula window.
Select either the TEMPLATE_HEAD or TEMPLATE_FTE formula.
Click on Edit and copy the formula body.
Create a new formula as appropriate:
BUDGET_HEAD or BUDGET_FTE for each business group.
GLOBAL_BUDGET_HEAD or GLOBAL_BUDGET_FTE for the entire enterprise.
Click on Edit and paste in the contents of the template you have copied.
Edit the formula code as required.
For further information on naming and amending these formulas, see: Workforce Calculation
Compile the new formula.
Repeat the above steps for each business group within your enterprise.
Many Workforce Intelligence reports display financial information, such as salaries. To enable the reports to convert salaries into your selected currency, you need to enter a Conversion Rate Type.
Set the Conversion Rate Type to whatever rate you have set for the profile option BIS: Primary Rate Type.
To enter a conversion rate type
Query EXCHANGE_RATE_TYPES in the Table field.
Enter BIS in the Exact field.
Enter the conversion type you want HRMS reports to use in the Value field, such as spot type. This must match the rate used by the BIS: Primary Rate Type profile option.
Save the conversion rate type.
Workforce Intelligence now uses the conversion rates set up in the General Ledger Daily Rates window for the conversion rate type you have selected.
To ensure that reports and workbooks calculate the correct hours for your training events you can customize the predefined formula.
To amend the default training hours
Copy the predefined template formula TEMPLATE_BIS_TRAINING_CONVERT_DURATION.
Name the new formula BIS_ TRAINING_CONVERT_DURATION.
If you do not name the formula correctly, the reports and workbooks cannot use it.
Replace the number of hours a training event runs in a day.
For example, if you record the duration of a training event in days, and within your training organization a day is 10 hours:
In the predefined formula the number of hours are set as follows:
hours_per_day = 8
To set the number of hours to 10, change the code to:
hours_per_day = 10
Compile the new formula.
If you have defined your own time periods using the FREQUENCY Lookup you must copy and amend the predefined formula. If you do not add your additional time periods to the formula the hours for these events will not be included in the report and workbooks.
Use the Formula window.
To Add Training Time Periods
Copy the predefined template formula TEMPLATE_BIS_TRAINING_CONVERT_DURATION.
Name the new formula BIS_ TRAINING_CONVERT_DURATION.
If you do not name the formula correctly, reports and workbooks cannot use it.
Update the formula to add the code.
For example, if you set up a time period called Fortnight using the Lookup code of F (Fortnight), you need to amend the formula as follows:
/* Main Body of Formula */
hours_per_day = 8
hours_per_week = hours_per_day * 5
hours_per_fortnight = hours_per_week * 2
hours_per_month = hours_per_week * 4.225
hours_per_year = hours_per_month * 12
/* Calculate Duration in Hours */
IF (from_duration_units = 'Y') THEN
hours = from_duration * hours_per_year
ELSE IF (from_duration_units = 'M') THEN
hours = from_duration * hours_per_month
ELSE IF (from_duration_units = 'F') THEN
hours = from_duration * hours_per_fortnight
ELSE IF (from_duration_units = 'W') THEN
hours = from_duration * hours_per_week
ELSE IF (from_duration_units = 'D') THEN
hours = from_duration * hours_per_day
ELSE IF (from_duration_units = 'H') THEN
hours = from_duration
ELSE
hours = 0
/* Calculate Duration in desired units */
IF (to_duration_units = 'H') THEN
to_duration = hours
ELSE IF (to_duration_units = 'D') THEN
to_duration = hours / hours_per_day
ELSE IF (to_duration_units = 'W') THEN
to_duration = hours / hours_per_week
ELSE IF (to_duration_units = 'F') THEN
to_duration = hours / hours_per_fortnight
ELSE IF (to_duration_units = 'M') THEN
to_duration = hours / hours_per_month
ELSE IF (to_duration_units = 'Y') THEN
to_duration = hours / hours_per_year
ELSE
to_duration = 0
RETURN to_duration
Compile the new formula.
The SYSADMIN user and users with a valid HRMS responsibility automatically have access to all HRMS Discoverer business areas.
You can grant access to specific business areas for users or responsibilities. This enables users to create or view workbooks only in the business areas they have access to.
Typically, you provide the majority of report users with read-only access to specific business areas, thereby enabling them to only view workbooks in those business areas.
Grant access to business areas for users or responsibilities.
For a detailed explanation of how to grant access to business areas, see: Set Privileges for the Current EUL in Oracle Discoverer Administrator Administration Guide.
The vacancy reports only count vacancies as closed if they have the system vacancy status of CLOSED. However, if your system was installed prior to 11.5.9, you may have two vacancy status options that users can use to close a vacancy: Closed, and Closed (1). The Closed option has a system vacancy status of C, whereas the Closed (1) option has a system vacancy status of CLOSED.
To ensure the vacancy reports return accurate results, you need to obsolete the old vacancy status option of Closed that returns the status of C. You can also update the name of the Closed (1) option.
If you want reports to include previously closed vacancies, you may also need to update their system vacancy status from C to CLOSED.
Use the Application Utilities Lookups window.
To update the Vacancy Status Options
In Enter Query mode, enter VACANCY_STATUS in the Type field, and execute a query.
Both Closed and Closed (1) may appear in the list of vacancy status options.
If both options appear, insert an end date of the current date against the Closed option that has a code of C.
This will remove that Closed option from the list of vacancy status options, and prevent C being used as a system vacancy status.
In the Meaning field, rename the Closed option to something else, for example, Closed_old.
In the Meaning field, rename the Closed (1) option to Closed. Ensure is has the code of CLOSED.
If necessary, update the system vacancy status of previously closed vacancies from C to CLOSED.
Reports that use organization hierarchy retrieve your organization structure from the HRI_ORG_HRCHY_SUMMARY table. Use the HRI Load All Organization Hierarchy Versions concurrent program to collect your organization hierarchy structures into the summary table. The process will perform a full refresh of all the data.
Use the Submit Requests window.
To populate the Organization Hierarchy Summary table
Select Single Request in the Submit a New Request window.
In the Name field, select HRI Load All Organization Hierarchy Versions and submit your request.
Define when you want to run this process using the schedule options.
For full information on this concurrent program, see HRI Load All Organization Hierarchy Versions
All reports that use supervisor hierarchy retrieve your current and historic supervisor hierarchy data from the Supervisor Hierarchy Summary table. Use the HRI Load All Supervisor Hierarchies concurrent program to collect your organization hierarchy structures into the summary table.
Use the Submit Requests window.
To populate the Supervisor Hierarchy History table
Select Single Request in the Submit a New Request window.
In the Name field, select HRI Load All Supervisor Hierarchies.
At implementation, set Full Refresh to Yes in the Parameters window.
Submit your request.
Define when you want to run this process using the schedule options.
For full information on this concurrent program, see HRI Load All Supervisor Hierarchies
Many reports use Workforce Measurement Values (WMVs), for example, Workforce Losses, Workforce Gains, and Workforce Count. WMVs include headcount and full-time equivalent (FTE) assignment budget values.
Populate the Workforce Measurement Value History table with the WMVs used by your reports. To populate the table, you need to run the concurrent program HRI Load Workforce Measurement Value History.
Use the Submit Requests window.
To populate the Workforce Measurement Value History table
Select Single Request in the Submit a New Request window.
In the Name field, select HRI Load Workforce Measurement Value History.
At implementation, use the following parameter values:
| Parameter | Implementation Value |
|---|---|
| Collect From Date | The earliest date required for WMV information. |
| Collect To Date | The current date (default) |
| Full Refresh | Yes |
| Collect FTE | Yes (if FTE is used in reporting) |
| Collect Headcount | Yes (if Headcount is used in reporting) |
Submit your request.
Define when you want to run this process using the schedule options.
For full information on this concurrent program, see HRI Load Workforce Measurement Value History
Some US specific Discoverer workbooks use a 'Vets, EEO, AAP, OSHA, Multi Work Sites' hierarchy. They require information about the current generic hierarchy.
Run the concurrent program HRI Load All Generic Hierarchy Versions to calculate the required data and store it in the Generic Hierarchy Summary table ready for use by the workbooks. These workbooks will only work if you have set up these generic hierarchies and run this concurrent program.
Use the Submit Requests window.
To populate the Generic Hierarchy Summary table
Select Single Request in the Submit a New Request window.
In the Name field, select HRI Load All Generic Hierarchy Versions.
Submit your request.
For a full discussion of the HRI Load All Generic Hierarchy Versions concurrent program, see HRI Load All Generic Hierarchy Versions
The BIS Load Organization Hierarchy Summary Table concurrent program creates the organization hierarchies on which the Discoverer End User Layer folder Organization Rollup – Current is based. If you create any reports based on the Organization Rollup – Current folder, you need to run this program to collect organization hierarchy structures into the HRI_ORG_PARAMS and HRI_ORG_PARAM_LIST tables.
Prior to running the concurrent program, ensure you have at least one organization hierarchy marked as the primary hierarchy. If no hierarchy is nominated as the primary hierarchy, BIS Load Organization Hierarchy Summary Table will not pick up your hierarchies.
See: Creating Organization Hierarchies, Oracle HRMS Enterprise and Workforce Management Guide
Add the BIS Load Organization Hierarchy Summary Table concurrent program to a request group.
See: Adding BIS Load Organization Hierarchy Summary Table to a Request Group
Schedule and run your request set that contains the BIS Load Organization Hierarchy Summary Table concurrent program using the Submit Request Set window.
If you have created reports based on the Organization Rollup – Current folder in the Discoverer End User Layer, you must run the BIS Load Organization Hierarchy Summary Table concurrent program to populate organization hierarchy summary tables.
See: Populate the Organization Hierarchy Tables
Prior to running this program you must add it to a request group. The request group should be used by the responsibility that runs the concurrent program.
Use the Request Groups window.
To add BIS Load Organization Hierarchy Summary Table to a request group
Enter the name of the group to which you want to add the program.
Enter Oracle Human Resources in the Application field.
Select Program as the Request Type.
In the Name field, select BIS Load Organization Hierarchy Summary Table
Save the change to the request group.
If you have created reports based on the Organization Rollup – Current folder in the Discoverer End User Layer, you must populate organization hierarchy summary tables. Use the BIS Load Organization Hierarchy Summary Table concurrent program to populate the tables.
Prior to running the concurrent program, ensure you have at least one hierarchy marked as the primary hierarchy. See: Creating Organization Hierarchies, Oracle HRMS Enterprise and Workforce Management Guide
Prior to running this program you must also add it to a request group. See: Adding BIS Load Organization Hierarchy Summary Table to a Request Group
Use the Submit Request Set window.
To populate the Organization Hierarchy tables
Select Request Set in the Submit a New Request window.
In the Request Set field, select the name of your request set that includes BIS Load Organization Hierarchy Summary Table and submit your request.
Define when you want to run this request set using the schedule options.
For further information on the BIS Load Organization Hierarchy Summary Table concurrent program, see BIS Load Organization Hierarchy Summary Table
You can attach short comments, word processed documents, images, video, OLE objects, or Web pages to many records in Oracle HRMS. For example, you could attach a resume to an applicant record, a vacancy announcement to a Request for Personnel Action, and a position description to a position record.
Each record can have one or more attachments, and you can copy attachments from one record to another. You can store the attachments in the database or in your file system.
To view attachments or add new attachments:
Click the Attachments icon. By default, clicking the attachments icon displays a Comments window where you can enter text up to 2000 characters. This is the Comments facility available in earlier releases of Oracle HRMS. If you want to replace this facility with the ability to attach multiple items, ask your system administrator to set your user profile option HR:Use Standard Attachments to Yes.
The Federal HR entities that support attachments are:
Absence
Absence Type
Address
Application
Assignment
Balance (Oracle Payroll)
Batch Header
Booking
Budgets
Budget Version
Calendar
Career Path
Collective Agreements
Consolidation Set (Oracle Payroll)
Contact Relationship
Contracts
Customization
Element
Element Entry
Element Link
Element Set
Event
Grade
Grade Rate
Job
Job Evaluation
Job Requirement
Letter Type
Monetary Unit (Oracle Payroll)
Organization
Organization Payment Method
Organization Hierarchy
Pay Scale
Payroll Process (Oracle Payroll)
Period of Service
Person
Person Analysis/Special Information
Personal Payment Method
Position
Position Description
Position Hierarchy
Recruitment Activity
Request for Personnel Action
Requisition
Salary Basis
Salary Proposal
Salary Proposal Component
Secondary Assignment Status
Special Information Type
Status Processing Rules (Oracle Payroll)
Vacancy
Valid Grade
You can define public folders, which all users can view, as well as private folders for your own use.
| Inquiry Window | Information Provided |
|---|---|
| Assignments Folder | Lists of assignments in a folder |
| Breakdown Folder | AA/EEO Breakdown report |
| People Folder | Lists of people in a folder |
| Salary Management Folder | List of assignments with their current approved salary and proposed new salary |
| Position Occupancy Folder | Lists of people who have held a selected position, or are applying for it, and the dates of their occupancy |
| List Assignments | Assignments that match the assignment components you specify for current applicants, employees, or both |
| List People by Assignment | People whose assignments match the assignment components you specify for current or former applicants, employees, or both |
| List Employees by Organization | All employees assigned to one organization and, optionally, to all organizations below it in a specified hierarchy |
| Assignment History | The dates of assignments and periods of service for an employee who has had more than one assignment NOTE: use DateTrack History on the Assignment window to see historical changes to one assignment |
| List Employees by Position | All employees assigned to a specified position or organization and job |
| List Employees by Position Hierarchy | Current holders of positions at and below a specified position in a position hierarchy |
| View Employee Grade Comparatio | The amount employees receive for a specified element as a percentage of the mid-value of their grade rate range |
| List Employees by Absence Type | All absences of a particular absence type or category within, optionally, a specified time period |
| View Employee Absence History | Periods of absence for a specified employee |
| List People by Special Information | All people for whom you have entered details about a specified special information type |
| List Employees by Element | All employee assignments receiving a specified compensation element within a given time period |
| View Element Entry History for Employee | The history of entries of one or more elements for an employee assignment |
| List Position Budget Variance | Variances between the number of actual position holders and the values entered in a specified budget for positions below a chosen position in a hierarchy |
| List Budget Variance by Organization | Variances between the number of actual position holders and the values entered in a specified budget for all positions in organizations at and below a chosen organization in a hierarchy |
| View Employee Benefits | View benefit plans on which an employee is enrolled and the coverage level and contributions for each plan |
| View Vacancies | Vacancies matching assignment components and other criteria you select |
There are a number of predefined reports that you can use immediately without any further set up. They have a predefined format but you can choose which records to view by entering a set of parameters when you submit the report.
These reports run in batch mode: you submit them for processing in the Submit Requests window and can view their progress using the View Requests window. The requests are handled by a concurrent manager so you can continue working online while your request is processed.
You can schedule the reports to run regularly and you can group them with other reports and processes to run as a set. You can also control access to the reports and control their printing. For example, the system administrator might want to ensure that users in one location always print their reports on a local printer.
| Report Name | Information Provided |
|---|---|
| AA/EEO Breakdown | Government required ethnicity and gender breakdown report by Occupational Category or Pay Plan |
| EEOC Form 462 | Government required summary of EEO complaints |
| Absences | Absence details for an employee or organization, for some or all absence types |
| Assignment Status | All employees, applicants, or both assigned to selected work structures |
| Batch Print Notification of Personnel Action | Prints SF-50s in batch mode |
| CPDF Dynamics Report | Record of the personnel data changes that occurred for the employee during a reporting period |
| CPDF Organization Component Tracking Report | Record of the organizational codes, titles, and hierarchical relationships for organizations within an agency as of the last day of the quarterly reporting period |
| CPDF Status Report | Record of each employee's personnel data as of the ending date of a fiscal quarter |
| EEOC Form 462 | Government required summary of EEO complaints |
| SF-113A-Federal Civilian Employment Report | Summary of federal civilian employment, payroll, and turnover |
| Current and Projected Progression Point Values | The expected results of running the Increment Progression Points process, that is, the projected point and value changes for a group of employees |
| Duty Station Conversion | Moves employees from an old to a new Location, updates the employes' Assignment records, updates Position records, both occupied and vacant, updates Organization Location information |
| Element Link Details | The eligibility criteria for an element or a group of elements |
| Employee Increment Results | The actual results of running the Increment Progression Points process, that is, progression point and value changes for a group of employees |
| Employee Organization Movements | New hires, terminations, transfers in and transfer out of a selected organization, or organization hierarchy |
| Employee Payroll Movements | New hires, terminations, transfers in and transfer out of a selected payroll |
| Employee Summary | Addresses, contacts, period of service, assignments, special information, personal payment methods, and element entries for a selected employee |
| Full Applicant Details | Applications and applicant interviews for one applicant |
| Full Assignment Details | Assignment information including periods of service, payment methods, and element entries for one employee |
| Full Personal Details Report Set | Person details, applicant details, assignment details, and work details for one employee |
| Full Person Details | Addresses and information entered in the Person window, such as name, date of birth, nationality, and work telephone number for one employee |
| Full Work Details | Miscellaneous work information, including special information, absences, recruitment activities, and contacts for one employee |
| Job and Position Skills Matching | Lists of employees, applicants, or both that meet some or all skill requirements of a job or position |
| Location Occupancy Report | Lists employees who currently or have at one time been assigned to a Location |
| Mass Realignment De-selection | Lists employees deselected in a criteria for realignment |
| Mass Realignment PA Listing for All | Notification of Personnel Action in list form for employees selected for a salary adjustment |
| Mass Realignment Listing for Employee | Notification of Personnel Action in list form for an individual employee selected for a salary adjustment |
| Mass Realignment Preview | Lists employees selected in a criteria for a salary adjustment |
| Mass Salary De-selection | Lists employees deselected in a criteria for a salary adjustment |
| Mass Salary PA Listing for All | Notification of Personnel Action in list form for employees selected for a salary adjustment |
| Mass Salary Listing for Employee | Notification of Personnel Action in list form for an individual employee selected for a salary adjustment |
| Mass Salary Preview | Lists employees selected in a criteria for a salary adjustment |
| Mass Transfer In De-selection | Lists employees deselected in a criteria for a Transfer In action |
| Mass Transfer In PA Listing for All | Notification of Personnel Action in list form for employees selected for a Transfer In action |
| Mass Transfer In Listing for Employee | Notification of Personnel Action in list form for an individual employee selected for a Transfer In action |
| Mass Transfer In Preview | Lists employees selected in a criteria for a Transfer In action |
| Mass Transfer Out De-selection | Lists employees deselected in a criteria for a Transfer Out action |
| Mass Transfer Out PA Listing for All | Notification of Personnel Action in list form for employees selected for a Transfer Out action |
| Mass Transfer Out Listing for Employee | Notification of Personnel Action in list form for an individual employee selected for a Transfer Out action |
| Mass Transfer Out Preview | Lists employees selected in a criteria for a Transfer Out action |
| Notification of Personnel Action (SF50) | Prints the standard Notification of Personnel Action for an approved Request for Personnel Action |
| Position Description | Lists the details of an approved position classification |
| Position Hierarchy | The positions (and optionally their holders) below a selected position in a particular hierarchy |
| Reduction in Force Retention Register | Lists selected employees |
| Request for Personnel Action (SF-52) | Prints the contents of the employee's Request for Personnel Action |
| Requisition Summary | Applicants and their interview schedules for a selection of vacancies |
| Salary Review | Current, past, and proposed salaries for a selected list of employees |
| SF-113A-Federal Civilian Employment Report | Summary of federal civilian employment, payroll, and turnover |
| Staffing Budget Details | Actual staffing level with budgeted levels over a specified period |
You can create your own reports using Oracle Reports or SQL*Plus or another tool of your choice. You can register them with Application Object Library. This means you can run them from the standard Submit Requests window, and you can schedule them in report sets with other reports and processes.
You can design QuickPaint reports in the Define QuickPaint Report window.
In the Report Definition area, you can enter free text to introduce the report and to label the information that the report extracts from the database. You can also select database items, which are tags representing the information to be extracted from the database. When you run the report, the database item names are replaced by the appropriate data for the assignment or set of assignments for which the report is run.
You must be careful how you position the database items so that QuickPaint interprets them correctly and formats the report in the layout you require.
To define a QuickPaint Report
Enter a name, and optionally a description, of the report.
The Protected field is display only; some reports provided by localization teams are protected against edits.
In the Report Definition area, enter free text exactly as you want it to appear on the report.
To select database items, choose the Show Items button and run a query to display a list of database items, then select and copy items to the Report Definition area.
Notice that the database item name must begin with an ampersand (&). Names without an ampersand are treated as free text.
Save the report definition.
If you want to add free text immediately after a database item, you must separate it from the database item with at least one space. Otherwise QuickPaint reads the database item as free text.
Both free text and database items appear in the report results on the line on which you painted them in the Report Definition area. They also generally appear in the column in which you painted them. However, it might be that the data replacing a database item name is long enough to push later items on the same line to the right.
For example, if you paint database items and free text like this:
&ASG_JOB in &ASG_ORG
the report results print like this:
Technician in Biochemistry
Scientific Officer in Biochemistry
Notice that, in the second result, the free text 'in' is pushed to the right and one space is entered before it.
If you know the number of the column in which you want text or a database item to appear, you can enter it like this:
&ASG_JOB &32in &ASG_ORG
However, the text 'in' will still be pushed to the right if the preceding database item (&ASG_JOB) extends beyond column 32. If you would prefer the preceding database item to be truncated, paint the line as follows:
&ASG_JOB &&32in &ASG_ORG
The report results will look like this:
Technician in Biochemistry
Scientific Off in Biochemistry
If you want one space between two database items or between a database item and text, then paint them separated by a single space. The single space is always preserved. For example, this definition:
&EMP_FIRST_NAME &EMP_LAST_NAME
gives the following report results:
Alice Hollister
Ray Garcia
When you save a report definition, QuickPaint generates a formula to extract the information required by the report. You can view this formula in the Formulas window. To query the formula, enter the name of your QuickPaint report.
Formulas generated from QuickPaint definitions do not contain conditional logic or mathematical computations. If you need these features, query the formula in the Formulas window and copy it. Edit the copy to add the logic you require.
Important: You should not edit the original QuickPaint formula. Always edit a copy. Any edits of the original formula are overwritten if you change the report definition in the QuickPaint Report window.
You run QuickPaint reports from the Run QuickPaint Report window. You can run a report for one assignment or for a group of assignments.
To run a report for one assignment
Select the type Assignment.
In the Assignment region, select the assignment for which you want to run the report.
In the Report field, select the report you want to run.
Choose the Run Report button.
The message line tells you when the report is complete.
Choose the View Report button to see the report results.
When you run a QuickPaint report, the system runs the formula associated with the report. The first time you run a report, the system may take several seconds to identify all of the related data and bring it back to the screen. All subsequent inquiries for other employees or applicants will run very quickly.
To run a report for an assignment set
Select the type Assignment Set.
In the Assignment Set region, select the assignment set for which you want to run the report.
In the Report field, select the report you want to run.
Choose the Run Report button.
The message line tells you when the report is complete.
Choose the View Report button to see the report results.
The Custom Reports function provides a generic reporting capability that makes use of a single report to print out a custom definition. This report is called PERGENRP.
The report is registered as a concurrent process and prints, in landscape format, the contents of the temporary table PER_GENERIC_OUTPUT_REPORT.
This table contains the individual components of a custom report and is populated by the PL/SQL package PERGENRP.pkb, stored in $PER_TOP/admin/sql. This package is executed when you select the Generate Report button on the Custom Reports window.
To submit a Custom Report
Navigate to the Custom Reports window.
Select the report by name.
Enter any parameters for this report.
Important: Parameter values are not validated until you choose the Generate Report button.
Choose the Generate Report button
The default for the report is to print the output automatically. It is a System Administrator task to set default printers for all users, or to reset this option on the Concurrent Program window.
A special feature of Custom Reports is that you do not need to create multiple reports. You modify the generic package (PERGENRP.pkb) and report to provide additional formats and parameters.
Three sample report formats are provided, each with a different set of parameters:
PERCS001 - Custom Report 1
There is one parameter: Vacancy. The format in PERGENRP is Full Name of Applicant and Gender.
PERCS002 - Custom Report 2
Parameters are Vacancy and Gender. The format in PERGENRP is Full Name of Applicant in uppercase.
PERCS003 Custom Report 3
Parameters are Vacancy, Gender and Marital Status. The format in PERGENRP is Full Name of Applicant, Gender and then Full Name in uppercase.
You can edit the generic package to change:
Report Title Page
Header
Footer
Body Text
After you have modified the package, you need to register a new custom report, with the parameter set for that report. This is a task for the System Administrator.
To register a new Custom Report with parameters
Navigate to the Concurrent Programs window.
Enter the name of the Custom Report as the Program.
Enter a short name for the Custom Report.
Important: You must start the short name with PERCS. This will limit the list of values available to users in the Custom Report window.