Step 1: Check HR11i Installation Required Step

Ensure that Oracle Human Resources 11i is installed with the most up-to-date patch according to
the readme file for SSHR at the time of installation. SSHR Implementation Steps 12-3

Step 2: Check the Apache server Required Step

Ensure that the Apache server and Apache JSERV are installed. Set up the Apache server as
specified in the Oracle Self-Service Web Applications Implementation Manual (available on
Metalink).

Step 3: Apply the patch Required Step

Apply the patch for the latest version of SSHR and make sure that all prerequisites are met,
including those for the Oracle Applications Framework (OAF).

Step 4: Complete the install and set-up of the Oracle Applications Framework (OAF).
Required Step
See: Configuring and Troubleshooting the OA Framework 5.7 with Oracle Applications 11.5.8
or Prior Releases (available on Metalink - technical note number: 139863.1)

Step 5: Set the HR:Self Service HR Licensed profile option Required Step

If you have licensed SSHR, set the following profile option to "Yes" at the site level.

HR: Self Service HR Licensed

If you have not licensed SSHR, please contact Oracle for information on purchasing a
licence.
Step 6: Check you have the correct Internet browser Required Step

Check that you have the correct Internet browser. You can use Netscape Navigator 4.08 or
Microsoft Internet Explorer version 4 or 5 or above.

Step 7: Create an SSHR Background Workflow Cleanup Process Required Step

You should remove transaction information from the temporary tables for processes that support
Web transactions. To do this, include the Remove Transaction activity in the workflow process.

Running the Workflow Cleanup Process

The workflow cleanup process enables you to remove workflow processes that are left running if
a system crashes or a user ID is disabled or removed. The process cleans up temporary tables by
removing redundant transaction information. You can specify which transactions are queried by
the process by setting the Transaction Status parameter.

You run the cleanup process by running the concurrent program Complete Defunct HR
Workflow Processes from the Submit Request Set window.

Before you run the cleanup process, you must define a request set that runs the Purge Obsolete
Workflow Runtime Data (FNDWFPR) concurrent program before the Complete Defunct HR
Workflow Resources (HRWFDFCT) concurrent program.

Note: From SSHR 4.1, the Complete Defunct Workflow Processes concurrent process is
registered under Oracle Human Resources instead of Oracle Self-Service Web Applications. If
you previously scheduled this concurrent process to run when still registered under Oracle Self-
Service Web Applications, you must cancel the process and resubmit it using the new Complete
Defunct HR Workflow Processes registered under Oracle Human Resources.

See: Concurrent Programs Window, Oracle Applications Developer's Guide

See: Overview of Concurrent Programs and Requests, Oracle Applications

System Administrator's Guide

To run the request set:

1. In the Request Set field, enter the name of your request set.

2. Place your cursor on the Parameters field in the row for the Purge Obsolete Workflow
Runtime Data process to open the Parameters window.

3. Select the item type for which you want to remove obsolete workflow runtime data. If you
leave the field blank, the process will purge obsolete data for all item types.

4. If applicable, enter an item key.

5. Enter the number of days for which you want to run the process. For example, if you want to
purge obsolete data for the last 7 days, enter 7.

6. Select the persistence type of the data to be purged (Temporary or Permanent).

7. Choose OK to close the Parameters window.

8. Place your cursor on the Parameters field in the row for the Complete Defunct HR Workflow
Processes process to open the Parameters window.

9. Select the item type to be included in the process.

10. Enter the number of days for which you want to run the process. For example, if you want to
run the cleanup process for the last 7 days, enter 7.

11. Select the transaction statuses to be queried in the program. The permitted values for the
transaction status parameter are as follows:

Transaction Status Values

Parameter Value Description

ALL All transaction statuses are queried in the program.

C Transaction returned for correction (in modules with SSHR V4.x

and earlier)

RO Transactions returned to approver for correction

ROS Transactions returned to approver for correction and saved for later

RI Transactions returned to initiator for correction

RIS Transactions returned to initiator for correction and saved for later

D Deleted transactions

E Transactions with errors

N Transactions initiated but not submitted for approval

S Transactions saved for later

W Transactions in progress

12. Choose the Submit button.

Step 13: Set Up Access Roles for Self-Service Actions Optional Step

If you want to take advantage of security based on access roles when routing and approving self-
service actions, you must first activate the system profile option HR: Allow Approver updates to
Self Service actions. Optionally, create and assign roles that grant or deny privileges to update
actions. All users can update by default. Define and manage access roles in the Maintain Roles
window.
Step 16: Set Up Eligibility Processing for Self-Service Actions Optional Step

You can configure SSHR to automatically determine if a person is eligible for a self-service
action. To do this, you set up eligibility profiles, reporting groups (actions), and plans (sub
actions), using SSHR Compensation and Benefits functionality as a generic processing engine.

Step 19: Link the Responsibilities to Your Security Profiles Required Step

Use the System Profile Values window to link the responsibilities you have created to your
security profile.

Step 20: Set the HR: Cross Business Group Profile Required Step

If you want your managers to be able to access data for employees in other business groups, also
set the HR: Cross Business Group responsibility.

Step 21: Set the Allow Granted Access Profile Required Step

If you want managers to be able to access data for workers outside their security profile whose
information has been released to them using the Release Employee Information function, also set
the Allow Granted Access profile option to Yes for the responsibility.

Step 43: Set Up Document Management Optional Step

If you want to make formatted PDF documents available to users that contain merged data from
self-service actions, create PDF documents and link them to appropriate menu functions by
creating groups in Document Manager. See: Document Manager, page 7-19

Step 44: Populate the Employee Directory Required Step

You must load data from your database into the repository. At this time you can override any of
the supplied mappings with your own data. See: Populating the Repository, page 8-31

Populating the Repository

Use the following procedures to load HRMS data into the Employee Directory repository. Prior
to loading the data, you can optionally configure the data for your legislation and country
requirements.

1. Use the supplied override packages to override values in the repository table columns for
individual legislation teams and customers if required. The overrides are effective when you
refresh the repository in either Complete or Incremental refresh mode.

See: Setting up Legislation and Customer Overrides, page 8-33

2. In the Submit Request window, run the concurrent program Refresh Employee Directory. This
program populates the repository with data from HRMS tables.
See: Submitting a Request, Oracle Applications User's Guide

The Refresh Employee Directory concurrent program uses the following parameters:

Note: If you run the Refresh Employee Directory concurrent program in Complete Refresh mode
with Process Multiple Assignments set to Yes, subsequent runs in Incremental Refresh mode
with Process Multiple Assignments set to No will have no effect. Incremental Refresh mode does
not remove previously populated secondary assignments. Conversely, if you run this program in
Complete Refresh mode with Process Multiple Assignments set to No, then subsequently run in
Incremental Refresh mode with Process Multiple Assignments set to Yes, secondary assignments
will be populated.