You are on page 1of 7

Set Up a Currency Conversion Rate Type Required Steps

Step 3: Enter a Currency Conversion Rate Type Required Step Workforce


Intelligence uses the conversion rates set up in the GL Daily Rate window. You can
enter a specific conversion rate type for Workforce Intelligence, such as Corporate
or Spot. Use the Oracle Human Resources Table Values window. See: Entering a
Conversion Rate Type, Oracle HRMS Configuring, Reporting, and System
Administration Guide
Set Up and Configure Training Hours Optional Steps Within Oracle Training
Administration OTA you can record the duration of a training event using a time
period of your choice. For example, rather than recording an event in hours you
might record it in weeks or months. To enable the workbooks to display the number
of hours of a training event, a predefined Oracle FastFormula,
TEMPLATE_BIS_TRAINING_CONVERT_DURATION, converts your time periods into
hours. OTA is installed with four predefined time periods. If you record the duration
of events using these predefined time periods the formula automatically converts
them into the following hours: D (Day) = 8 Hours
W (Week) = 40 Hours
M (Month) = 169 Hours
Y (Year) = 2028 Hours
Note: You set up time periods in Oracle Training Administration using the Lookup
type FREQUENCY.
Step 4: Amend the Default Training Hours Optional Step Amend the FastFormula
TEMPLATE_BIS_TRAINING_CONVERT_DURATION if you have set up different time
periods using the Lookup type FREQUENCY. Use the Formula window. See: Amending
the Default Training Hours, Oracle HRMS Configuring, Reporting, and System
Administration Guide
Implementation Steps

3-111

Step 5: Add Additional Training Time Periods Optional Step Amend the FastFormula
TEMPLATE_BIS_TRAINING_CONVERT_DURATION if the number of hours per time
period does not match those of your enterprise. Use the Formula window. See:
Adding Additional Training Time Periods, Oracle HRMS Configuring, Reporting, and
System Administration Guide
Set up Cross Business Group Reporting Optional Steps If users are using a local
security profile they will only be able to see information in a specific business group.
The business group is defined in the security profile attached to the responsibility.
For Discoverer reports, you may want to enable users to see data that spans
business groups.

Step 6: Provide users with a global security profile Optional Step If you want to
enable cross business reporting, provide users with a global security profile. A global
security profile provides cross business group reporting because it does not specify
a business group. Use the Global Security Profile window. See: Defining a Security
Profile, Oracle HRMS Configuring, Reporting, and System Administration Guide
Identify the Reporting Organization Required Steps HRMS Discoverer workbooks will
not run unless the application can identify an organization to report on. If a
workbook cannot identify the reporting organization, it will fail to generate certain
report parameter lists and will produce the following error message when displaying
the report parameter page: "No values were found for the parameter Organization
whilst attempting to build the list of values. To run this report your system must
have the parameter Organization set up. Please contact your system administrator."
The application identifies an organization through a business group. You must
therefore ensure that you assign a business group correctly to report users. How
you assign the business group depends on which security model you implement and
whether you are using a local or global security profile. See the options below.
Step 7: Set the Profile Option HR: Security Optional Step If you have implemented
the standard HRMS security model, with a local security profile, you must set the
profile option HR: Security to the business group you want to report on. The reports
identify the business group through the profile option HR: Business Group.
3-112

Oracle Human Resources Management Systems Implementation Guide

The application automatically sets this profile option to the value in the HR: Security
profile option. Set up the business group in the profile option HR: Security. Use the
System Profile Values window. See: System Profile Values Window , Oracle EBusiness Suite System Administrator's Guide - Security
Step 8: Set the Profile Option HR: Business Group Optional Step If you have
implemented the standard HRMS security model, with a global security profile, the
HR: Business Group profile option is not set automatically. Set the profile option HR:
Business Group at responsibility level to the business group that you want to report
on. Use the System Profile Values window. See: Defining Preferences with User
Profile Options, Oracle E-Business Suite System Administrator's Guide - Security
Step 9: Associate a Business Group with a Security Profile Optional Step If you have
implemented the Security Groups Enabled security model, the HR: Business Group
profile option is not used. You associate a business group with a security profile. Use
the Assign Security Profile window. See: Assigning Security Profiles, Oracle HRMS
Configuring, Reporting, and System Administration Guide
Restrict Discoverer Workbook Access Required Steps

Step 10: Grant Access to Discoverer Business Areas Required Step Grant access
privileges to the Discoverer business area to determine which workbooks users can
create or view. Use Oracle Discoverer Administration Edition. See: Grant Business
Area Access, Oracle HRMS Configuring, Reporting, and System Administration Guide
Check the Vacancy Status Options Required Steps
Step 11: Check the Vacancy Status Options Required Step To ensure the reports
that cover vacancies return accurate results, you need to ensure that users close
vacancies by using the status of CLOSED. You may have to obsolete an old vacancy
status option that results in the status of C. Use the Application Utilities Lookups
window.
Implementation Steps

3-113

See: Check the Vacancy Status Options, Oracle HRMS Configuring, Reporting, and
System Administration Guide
Populate Summary Tables Required Steps To ensure your HRMS Discoverer
workbooks run correctly and efficiently, you need to run concurrent programs to
populate summary tables with your hierarchy data and workforce measurement
values. For a full discussion of these concurrent programs, and when you need to
run them, see: Programs for Populating Workforce Intelligence Discoverer Reports,
Oracle HRMS Configuring, Reporting, and System Administration Guide
Step 12: Populate the Organization Hierarchy Summary Table Required Step All
reports that use organization hierarchy gather information from the Organization
Hierarchy Summary table. Populate this summary table with your organization
hierarchy data. The table ensures that you are getting the best possible
performance from your reports. To populate the summary table, run the concurrent
program HRI Load All Organization Hierarchy Versions. Use the Submit Requests
window. See: Populating the Organization Hierarchy Summary Table, Oracle HRMS
Configuring, Reporting, and System Administration Guide
Step 13: Populate the Supervisor Hierarchy History Table Required Step All reports
that use supervisor hierarchy gather information from the Supervisor Hierarchy
Summary table. Populate this summary table with your supervisor hierarchy data.
The table ensures that you are getting the best possible performance from your
reports. To populate the summary table, run the concurrent program HRI Load All
Supervisor Hierarchies. Use the Submit Requests window. See: Populating the
Supervisor Hierarchy History Table, Oracle HRMS Configuring, Reporting, and
System Administration Guide
Step 14: Populate the Workforce Measurement Value History Table Required Step
Many reports use Workforce Measurement Values (WMVs). WMVs currently include
headcount and full-time equivalent (FTE) assignment budget values. Run the

concurrent program HRI Load Workforce Measurement Value History to populate the
Workforce Measurement Value History table with the WMVs used by your reports.
Use the Submit Requests window.
3-114

Oracle Human Resources Management Systems Implementation Guide

See: Populating the Workforce Measurement Value History Table, Oracle HRMS
Configuring, Reporting, and System Administration Guide
Step 15: Populate the Generic Hierarchy Summary Table Required Step 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 and collect
the required data. Use the Submit Requests window. See: Populating the Generic
Hierarchy Summary Table, Oracle HRMS Configuring, Reporting, and System
Administration Guide
Step 16: Collect Organization Hierarchy Structures Optional Step The Organization
Rollup Current folder in the Discoverer End User Layer uses organization
hierarchies held in the HRI_ORG_PARAMS and HRI_ORG_PARAM_LIST tables. If you
build Discoverer reports using the Organization Rollup Current folder, you must
populate these tables with your organization hierarchies. To populate the tables, run
the concurrent program BIS Load Organization Hierarchy Summary Table. See:
Collecting Organization Hierarchy Structures, Oracle HRMS Configuring, Reporting,
and System Administration GuideHR Information Systems
Reports
Step 1: Use Standard Reports or Write New Reports Optional Step A number of
standard reports are supplied with Oracle HRMS. These reports have been written
using Oracle Reports V.2 and registered as concurrent programs with the Standard
Requests Submission (SRS) feature of Oracle Applications. You can use these
Standard Reports or write your own reports and register these as additional reports
which users can request from the Submit a New Request window.
UK Payroll Implementation Only In the UK, P45 and Pay Advice reports supplied with
Oracle Payroll are designed for use with preprinted stationery. These reports use two
special printer drivers to control the print format. P45 - paygbp45.prt
Pay Advice -paygbsoe.prt
Implementation Steps

3-115

If your printer does not accept the same control characters as the DEC LN03 printer,
you may need to modify the special SRW driver files. When you install Oracle Payroll
the two sample files are stored in the $PAY_TOP/srw directory. You should copy the

files to $FND_TOP/$APPLREP and then register them using the Printer Drivers
window.
Step 2: Register Reports as Concurrent Programs Optional Step After you have
written your new reports and saved them in the correct subdirectory, you must
register the report as a concurrent program. You also register the parameters which
can be submitted with the report. For example, you may have written a report to
display personal details and you want to submit employee name to limit the output
to include one person at a time. Use the Concurrent Programs window. See:
Concurrent Programs Window, Oracle E-Business Suite System Administrator's
Guide - Security
Step 3: Define Report Sets Optional Step You can define sets of Reports: To
restrict user access to specific reports. A set of reports can be linked to a
Responsibility.
To simplify requesting a report You can run a report set in one request, rather than
a request for each report.
Use the Request Set window.
Standard Letter Generation You can use standard letters in HRMS to help you to
manage your enterprise's recruitment or enrollments, for example. You do this by
issuing standard letters to applicants or students, triggered by changes in
assignment or enrollment status. Oracle HRMS provides you with three different
methods to create standard letters: Method 1 Concurrent Processing using Word
Processors, page 3-115
Method 2: Concurrent Processing using Oracle Reports, page 3-117
Method 3: Create Mail Merge Letters using Web ADI, page 3-118
Method 1 - Concurrent Processing using Word Processors You can create standard
letters using Multimate, WordPerfect or Microsoft Word.
3-116

Oracle Human Resources Management Systems Implementation Guide

Step 4: Plan Standard Letter Requirements Optional Step You need to identify the
database information to include in the letters. See: Planning Standard Letter
Requirements, Oracle HRMS Configuring, Reporting, and System Administration
Guide
Step 5: Write a SQL*Plus Script Optional Step Oracle HRMS supplies you with
SQL*Plus scripts as templates for extracting database information for standard
letters. You can copy the SQL*Plus script templates and modify them to create the
standard letters you require. See: Writing a SQL*Plus Script for MultiMate or
WordPerfect, Oracle HRMS Configuring, Reporting, and System Administration Guide

See: Writing a SQL*Plus Script for Microsoft Word, Oracle HRMS Configuring,
Reporting, and System Administration Guide
Step 6: Register the SQL*Plus Script Optional Step Register your SQL*Plus program
with Oracle HRMS. You register your program so that you can run it as a concurrent
program. Name the file PERWP*** (or OTAWP***). You must use this prefix for the
system to recognize it as a type of letter. Use the Concurrent Programs window. See:
Registering the SQL*Plus Script, Oracle HRMS Configuring, Reporting, and System
Administration Guide
Step 7: Link the SQL*Plus Script to the Letter Optional Step Link your SQL*Plus
script with a letter and one or more statuses. In Oracle Human Resources, you can
link one or more applicant assignment statuses with each recruitment letter. A
request for the letter is then created automatically when an applicant is given an
associated assignment status. For example, you can link your standard recruitment
rejection letter to the status Rejected so that the letter is triggered when you set an
applicant's assignment status to Rejected Use the Letter window. See: Linking the
SQL*Plus Script with aLetter, Oracle HRMS Configuring, Reporting, and System
Administration Guide
Step 8: Writing a Skeleton Letter Optional Step Write a skeleton letter using your
word processor. Include the appropriate merge codes from the data source for the
word processor you are using. See: Writing a Skeleton Letter, Oracle HRMS
Configuring, Reporting, and System Administration Guide
Implementation Steps

3-117

Step 9: Requesting Letters Optional Step When you, or other users, set the status
for an applicant or enrollment that triggers your standard letters, Oracle HRMS
creates a letter request automatically, with the status of Pending. It also adds the
applicant's or student's name to the request. You can view the pending request and
names through the Request Letter window. Use the Request Letter window. See:
Requesting Letters/Running the Report, Oracle HRMS Configuring, Reporting, and
System Administration Guide
Step 10: Merging the Data Files Optional Step You now need to merge the data in
the Data File with your skeleton letters. See: Merging the Data File with the
Standard Letter, Oracle HRMS Configuring, Reporting, and System Administration
Guide
Method 2 - Concurrent Processing using Oracle Reports You can create a report for
each letter using Oracle Reports, or another tool of your choice. The report contains
the skeleton letter text and Select statements specifying the data to be extracted
from the Oracle database.

Step 11: Plan Standard Letter Requirements Optional Step You need to identify the
database information to include in the letters. See: Planning Standard Letter
Requirements, Oracle HRMS Configuring, Reporting, and System Administration
Guide
Step 12: Write and Register the Report Optional Step You now need to write and
register the report. See: Writing and Registering the Report, Oracle HRMS
Configuring, Reporting, and System Administration Guide
Step 13: Link the Report with a Letter Optional Step You need to link your report
with a letter and one or more statuses. In Oracle Human Resources, you can link
one or more applicant assignment statuses with each recruitment letter. A request
for the letter is then created automatically when an applicant is given an associated
assignment status. In Oracle Training Administration, you can link one or more
enrollment statuses with each enrollment letter. A request for the letter is then
created automatically when an enrollment is given an associated status. Use the
Letter window. See: Linking the Report With a Letter, Oracle HRMS Configuring,
Reporting, and System Administration Guide
3-118

Oracle Human Resources Management Systems Implementation Guide

Step 14: Run the Report Optional Step When you, or other users, set the status for
an applicant or enrollment that triggers your standard letters, Oracle HRMS creates
a letter request automatically, with the status of Pending. It also adds the
applicant's or student's name to the request. You can view the pending request and
names through the Request Letter window. Then, when you change the letter
request from Pending to Requested, Oracle HRMS runs the report that you created.
Use the Request Letter window. See: Registering Letters/Running the Report, Oracle
HRMS Configuring, Reporting, and System Administration Guide
Method 3 Create Mail Merge Letters Using Web ADI
Step 15: Create Mail Merge Letters Optional Step Define Web ADI integrators and
layouts and set up template letters. See Creating Mail Merge Letters Using Web ADI,
Oracle HRMS Configuring, Reporting, and System Administration Guide

You might also like