D60563GC10 SG

THESE eKIT MATERIALS ARE FOR YOUR USE IN THIS CLASSROOM ONLY.
COPYING eKIT MATERIALS FROM THIS COMPUTER IS STRICTLY PROHIBITED
D65029
May 2010
Edition 1.0
D60563GC10
Student Guide
Service Fundamentals
R12.x Oracle HRMS Self
Oracle University and Zinger Solutions Limited use only

THESE eKIT MATERIALS ARE FOR YOUR USE IN THIS CLASSROOM ONLY. COPYING eKIT MATERIALS FROM THIS COMPUTER IS STRICTLY PROHIBITED
Copyright © 2007, 2010 Oracle. All rights reserved.

Disclaimer
This document contains proprietary information and is protected by copyright and other intellectual property laws. You may copy and
print this document solely for your own use in an Oracle training course. The document may not be modified or altered in any way.
Except where your use constitutes "fair use" under copyright law, you may not use, share, download, upload, copy, print, display,
perform, reproduce, publish, license, post, transmit, or distribute this document in whole or in part without the express authorization
of Oracle.
The information contained in this document is subject to change without notice. If you find any problems in the document, please
report them in writing to: Oracle University, 500 Oracle Parkway, Redwood Shores, California 94065 USA. This document is not
warranted to be error-free.
Restricted Rights Notice
If this documentation is delivered to the United States Government or anyone using the documentation on behalf of the United

States Government, the following notice is applicable:
U.S. GOVERNMENT RIGHTS

The U.S. Government’s rights to use, modify, reproduce, release, perform, display, or disclose these training materials are restricted
by the terms of the applicable Oracle license agreement and/or the applicable U.S. Government contract.
Trademark Notice
Oracle is a registered trademark of Oracle Corporation and/or its affiliates. Other names may be trademarks of their respective
owners.
Author
Gowri Arur
Technical Contributors and Reviewers
Andrea Auld
This book was published using: Oracle Tutor

Table of Contents
R12.x Oracle HRMS Self Service Fundamentals..........................................................................................1-1

R12.x Oracle HRMS Self Service Fundamentals ..........................................................................................1-3
Course Outline...............................................................................................................................................1-4
Introduction ...................................................................................................................................................1-5
Objectives ......................................................................................................................................................1-6
Introduction to SSHR......................................................................................................................................2-1
Introduction to SSHR ....................................................................................................................................2-3
Objectives ......................................................................................................................................................2-4

Overview of Self-Service Human Resources .................................................................................................3-1
Overview of Self-Service Human Resources (SSHR)...................................................................................3-3
What is a Web-based Application?................................................................................................................3-4
Professional User Interfaces versus Self-Service User Interfaces ................................................................3-5
Integration of SSHR and Professional User Interface ..................................................................................3-6
Why Use Self-Service?..................................................................................................................................3-7
Self-Service Functionality in HRMS.............................................................................................................3-8
Integration of SSHR with a Third-Party Application ....................................................................................3-10
Configuration Tools for SSHR ......................................................................................................................3-11
Highly Configurable Interface.......................................................................................................................3-12
Workflow-Enabled ........................................................................................................................................3-13
Useful Documentation...................................................................................................................................3-14
Related Guides...............................................................................................................................................3-15
Quiz ...............................................................................................................................................................3-16
Implementing SSHR........................................................................................................................................4-1
Implementing SSHR......................................................................................................................................4-3
Objectives ......................................................................................................................................................4-4
Self-Service Basics ...........................................................................................................................................5-1
Self-Service Basics ........................................................................................................................................5-3
e-Business Suite Architecture........................................................................................................................5-4
Operation of Web-Based Functions...............................................................................................................5-5
Personal Information: Functional Flow .........................................................................................................5-8
Storing Transaction Data ...............................................................................................................................5-13
Quiz ...............................................................................................................................................................5-18
Summary........................................................................................................................................................5-20
User Access and Security ................................................................................................................................6-1
User Access and Security ..............................................................................................................................6-3
Security Mechanisms.....................................................................................................................................6-4
Defining User Access ....................................................................................................................................6-6
Responsibilities..............................................................................................................................................6-7
Functions, Menus, and Responsibilities ........................................................................................................6-9
Creating a Responsibility...............................................................................................................................6-10
Types of SSHR Users ....................................................................................................................................6-11
Comparing Employee/Worker and Manager Access.....................................................................................6-13
People versus Users .......................................................................................................................................6-14
Associating User with Person........................................................................................................................6-15
Creating Users - Information .........................................................................................................................6-16
Batch Creation of User Accounts ..................................................................................................................6-17
Creating User Hooks .....................................................................................................................................6-19
Access Roles for Self-Service Transactions ..................................................................................................6-20
Restrict Access to Workflow Transactions....................................................................................................6-21
Quiz ...............................................................................................................................................................6-22
Copyright © Oracle 2010. All rights reserved.
R12.x Oracle HRMS Self Service Fundamentals Table of Contents

i
Summary........................................................................................................................................................6-24
User Access to People ......................................................................................................................................7-1
User Access to People ...................................................................................................................................7-3
Security Profiles (Non-Manager) ..................................................................................................................7-4
Security Profiles (Manager)...........................................................................................................................7-5
Assignment-Based Security...........................................................................................................................7-7
Interaction of System Profiles .......................................................................................................................7-8
Releasing Information ...................................................................................................................................7-9
Hierarchy Page ..............................................................................................................................................7-10
Searching for People......................................................................................................................................7-11
Search Page ...................................................................................................................................................7-12
Person Types .................................................................................................................................................7-13

My List ..........................................................................................................................................................7-14
Manager Enter Process Pages........................................................................................................................7-15
Security Profiles - Considerations .................................................................................................................7-16
Quiz ...............................................................................................................................................................7-17
Summary........................................................................................................................................................7-19
Implementation Steps......................................................................................................................................8-1
Implementation Steps ....................................................................................................................................8-3
Implementation Strategy................................................................................................................................8-4
Prepare Environment for SSHR.....................................................................................................................8-5
Configure HRMS Applications .....................................................................................................................8-6
User Access Setup .........................................................................................................................................8-7
Configure Workflow Processes and Page Layouts........................................................................................8-8
Migrate Configuration to Test and Production Environments.......................................................................8-10
Summary........................................................................................................................................................8-11
Configuring SSHR...........................................................................................................................................9-1
Configuring SSHR.........................................................................................................................................9-3
Objectives ......................................................................................................................................................9-4
Functions, Menus, and Responsibilities.........................................................................................................10-1
Functions, Menus and Responsibilities .........................................................................................................10-3
Functions, Menus, and Responsibilities - Overview .....................................................................................10-4
Functions, Menus, and Responsibilities ........................................................................................................10-5
Configuring Menus........................................................................................................................................10-6
Menu Types ...................................................................................................................................................10-7
Top-level Menus............................................................................................................................................10-8
Submenus ......................................................................................................................................................10-9
Designing Menus...........................................................................................................................................10-10
Hidden Submenus..........................................................................................................................................10-11
Data Security Menus .....................................................................................................................................10-13
Custom Menus 1............................................................................................................................................10-14
Custom Menus 2............................................................................................................................................10-15
Person Tree Navigation Paths........................................................................................................................10-16
Actions Menus...............................................................................................................................................10-17
Employee Actions Page.................................................................................................................................10-18
Quiz ...............................................................................................................................................................10-19
Summary........................................................................................................................................................10-21
Configuring Functions ....................................................................................................................................11-1
Configuring Functions...................................................................................................................................11-3
Non-Manager versus Manager Functions......................................................................................................11-4
Considerations ...............................................................................................................................................11-5
Copying Delivered Functions ........................................................................................................................11-6
Adding Custom Functions to Menus .............................................................................................................11-8
Data Security Menus: Restricting Functions by Legislation Code ................................................................11-10

ii
Adding Custom Functions .............................................................................................................................11-11

Data Security Menus .....................................................................................................................................11-12
Adding Custom Functions to Menus .............................................................................................................11-13
Changing the Manager Entry Pages...............................................................................................................11-15
Quiz ...............................................................................................................................................................11-16
Summary........................................................................................................................................................11-18
Using the Workflow Builder ...........................................................................................................................12-1
Using the Workflow Builder .........................................................................................................................12-3
Workflow-Enabled SSHR Functions.............................................................................................................12-4
Workflow Builder..........................................................................................................................................12-5
Working with the Workflow Builder.............................................................................................................12-6
Working with Workflow Item Types.............................................................................................................12-7

Workflow Access Levels...............................................................................................................................12-8
Configurable and Locked Workflow Objects ................................................................................................12-9
Changing Workflow Objects .........................................................................................................................12-10
Chaining Workflow Processes.......................................................................................................................12-11
Chaining Self-Service Activities ...................................................................................................................12-12
Manage Employment Events – Activities Some Delivered Processes ..........................................................12-13
Sequencing Restrictions for Manage Employment Event Pages ...................................................................12-14
Applying a Patch ...........................................................................................................................................12-15
Quiz ...............................................................................................................................................................12-16
Summary........................................................................................................................................................12-18
Configuring Web Page Layouts .....................................................................................................................13-1
Configuring Web Page Layouts.....................................................................................................................13-3
Configuring Self-Service Web Pages ............................................................................................................13-4
Oracle Applications Framework....................................................................................................................13-5
Personalization Levels...................................................................................................................................13-6
Profile Options for Oracle Applications Framework....................................................................................13-9
Personalization - Buttons and Links ..............................................................................................................13-10
Configuration Options within the Oracle Applications Framework ..............................................................13-11
Additional Options for Tabular Regions .......................................................................................................13-12
Adding User Instructions...............................................................................................................................13-13
Flexfields .......................................................................................................................................................13-14
Configuring the e-mail Address.....................................................................................................................13-15
Configuring the Global Button Bar ...............................................................................................................13-16
Logos .............................................................................................................................................................13-17
Quiz ...............................................................................................................................................................13-18
Summary........................................................................................................................................................13-20
Approvals .........................................................................................................................................................14-1
Approvals ......................................................................................................................................................14-3
Basic Approvals Loop ...................................................................................................................................14-4
Approvals ......................................................................................................................................................14-5
Enabling Dynamic Approvals........................................................................................................................14-6
Configurable Approvals Options...................................................................................................................14-7
What is AME? ...............................................................................................................................................14-8
When Can I Use AME? .................................................................................................................................14-9
Business Requirements..................................................................................................................................14-10
Overview of AME Components ....................................................................................................................14-11
Approval Considerations ...............................................................................................................................14-12
Approvals Routing.........................................................................................................................................14-13
Quiz ...............................................................................................................................................................14-14
Summary........................................................................................................................................................14-16
Using SSHR......................................................................................................................................................15-1
Using SSHR...................................................................................................................................................15-3
Objectives ......................................................................................................................................................15-4

iii
Common SSHR Functions ..............................................................................................................................16-1

Common SSHR Functions.............................................................................................................................16-3
Common Functionality ..................................................................................................................................16-4
Review Page ..................................................................................................................................................16-5
Return for Correction.....................................................................................................................................16-6
Save for Later ................................................................................................................................................16-7
New User Registration...................................................................................................................................16-8
New Employee Registration Process.............................................................................................................16-9
Document Manager .......................................................................................................................................16-11
FastFormula Options for Document Manager ...............................................................................................16-13
Quiz ...............................................................................................................................................................16-14
Summary........................................................................................................................................................16-16

Self-Service Actions .........................................................................................................................................17-1
Self-Service Actions ......................................................................................................................................17-3
Overview – Self-Service Actions ..................................................................................................................17-4
Types of Self-Service Action.........................................................................................................................17-5
Life-Cycle of Self-Service Action .................................................................................................................17-6
Profile Options for Self-Service Actions .......................................................................................................17-7
Managing Dates.............................................................................................................................................17-11
Conflicting Actions........................................................................................................................................17-12
Conflicting Actions - Resolution ...................................................................................................................17-13
Configuring Self-Service Actions..................................................................................................................17-14
Combining Activities for Self-Service Actions .............................................................................................17-15
What-If Analysis............................................................................................................................................17-16
Eligibility Processing.....................................................................................................................................17-17
Quiz ...............................................................................................................................................................17-18
Summary........................................................................................................................................................17-20
Integrating SSHR with Third-Party Information Providers .......................................................................18-1
Integrating SSHR with Third-Party Information Providers...........................................................................18-3
Integrating SSHR with Third-Party Information Provider ............................................................................18-4
Accessing Third-Party Information from the Self -Service Pages.................................................................18-5
Info Online – Enables Integration with Third-Party Information Providers..................................................18-6
Enabling the Info Online Functionality .........................................................................................................18-7
Setting up Links Between Oracle Self-Service HR and Enwisen..................................................................18-9
Display Info Online Content Container on Self-Service Pages .....................................................................18-10
Summary........................................................................................................................................................18-12
Advanced Topics..............................................................................................................................................19-1
Advanced Topics ...........................................................................................................................................19-3
Objectives ......................................................................................................................................................19-4
Employee Directory.......................................................................................................................................19-5
Single Sign-On or Anonymous Log-In? ........................................................................................................19-6
Responsibility Ownership..............................................................................................................................19-7
Additional Configuration Steps .....................................................................................................................19-8
Quiz ...............................................................................................................................................................19-9
Summary........................................................................................................................................................19-11

iv
Preface
Profile
Before You Begin This Course
Before you begin this course, you should have the following qualifications:
• Thorough knowledge of Oracle Applications

• Working experience with procurement
Prerequisites
• Oracle Applications Foundations
How This Course Is Organized
R12.x Oracle HRMS Self Service Fundamentals Ed 1 is an instructor-led course featuring lecture
and hands-on exercises. Online demonstrations and written practice sessions reinforce the
concepts and skills introduced.

v
Related Publications
Oracle Publications
Title Part Number
Oracle Workforce Sourcing, Deployment, and Talent Management E13515-02
Guide
Oracle HRMS Enterprise and Workforce Management Guide E13511-02
Oracle Self-Service Human Resources Deploy Self-Service E13507-02

Capability Guide
Oracle HRMS Systems Configuring, Reporting, and System E13509-02
Administration Guide
Oracle HRMS Approvals Management Implementation Guide E13516-02
Additional Publications
• System release bulletins
• Installation and user’s guides
• Read-me files
• International Oracle User’s Group (IOUG) articles
• Oracle Magazine

vi
Typographic Conventions
Typographic Conventions in Text
Convention Element Example
Bold italic Glossary term (if The algorithm inserts the new key.
there is a glossary)
Caps and Buttons, Click the Executable button.
lowercase check boxes, Select the Can’t Delete Card check box.
triggers, Assign a When-Validate-Item trigger to the ORD block.

windows Open the Master Schedule window.
Courier new, Code output, Code output: debug.set (‘I”, 300);
case sensitive directory names, Directory: bin (DOS), $FMHOME (UNIX)
(default is filenames, Filename: Locate the init.ora file.
lowercase) passwords, Password: User tiger as your password.
pathnames, Pathname: Open c:\my_docs\projects
URLs, URL: Go to http://www.oracle.com
user input,
User input: Enter 300
usernames
Username: Log on as scott
Initial cap Graphics labels Customer address (but Oracle Payables)
(unless the term is a
proper noun)
Italic Emphasized words Do not save changes to the database.
and phrases, For further information, see Oracle7 Server SQL Language
titles of books and Reference Manual.
courses, Enter user_id@us.oracle.com, where user_id is the
variables name of the user.
Quotation Interface elements Select “Include a reusable module component” and click Finish.
marks with long names
that have only This subject is covered in Unit II, Lesson 3, “Working with
initial caps; Objects.”
lesson and chapter
titles in cross-
references
Uppercase SQL column Use the SELECT command to view information stored in the
names, commands, LAST_NAME
functions, schemas, column of the EMP table.
table names
Arrow Menu paths Select File > Save.
Brackets Key names Press [Enter].
Commas Key sequences Press and release keys one at a time:
[Alternate], [F], [D]
Plus signs Key combinations Press and hold these keys simultaneously: [Ctrl]+[Alt]+[Del]

vii
Typographic Conventions in Code

Convention Element Example
Caps and Oracle Forms When-Validate-Item
lowercase triggers
Lowercase Column names, SELECT last_name
table names FROM s_emp;
Passwords DROP USER scott

IDENTIFIED BY tiger;
PL/SQL objects OG_ACTIVATE_LAYER

(OG_GET_LAYER (‘prod_pie_layer’))
Lowercase Syntax variables CREATE ROLE role

italic
Uppercase SQL commands and SELECT userid
functions FROM emp;
Typographic Conventions in Oracle Application Navigation Paths

This course uses simplified navigation paths, such as the following example, to direct you
through Oracle Applications.
(N) Invoice > Entry > Invoice Batches Summary (M) Query > Find (B) Approve
This simplified path translates to the following:
1. (N) From the Navigator window, select Invoice then Entry then Invoice Batches
Summary.
2. (M) From the menu, select Query then Find.
3. (B) Click the Approve button.
Notations:
(N) = Navigator
(M) = Menu
(T) = Tab
(B) = Button
(I) = Icon
(H) = Hyperlink
(ST) = Sub Tab

viii
Typographical Conventions in Oracle Application Help System Paths

This course uses a “navigation path” convention to represent actions you perform to find
pertinent information in the Oracle Applications Help System.
The following help navigation path, for example—
(Help) General Ledger > Journals > Enter Journals
—represents the following sequence of actions:

1. In the navigation frame of the help system window, expand the General Ledger entry.
2. Under the General Ledger entry, expand Journals.
3. Under Journals, select Enter Journals.
4. Review the Enter Journals topic that appears in the document frame of the help system
window.

ix
x
R12.x Oracle HRMS Self Service Fundamentals

Chapter 1 - Page 1
Chapter 1
Copyright © Oracle, 2010. All rights reserved.

Service Fundamentals
R12.x Oracle HRMS Self


Chapter 1 - Page 2

Chapter 1 - Page 3

Course Outline

Chapter 1 - Page 4
Introduction

Chapter 1 - Page 5
Objectives

Chapter 1 - Page 6
Introduction to SSHR
Chapter 2 - Page 1
Chapter 2


Chapter 2 - Page 2
Chapter 2 - Page 3
Objectives
Chapter 2 - Page 4
Overview of Self-Service Human Resources

Chapter 3 - Page 1
Chapter 3

Human Resources
Overview of Self-Service


Chapter 3 - Page 2

Chapter 3 - Page 3
Overview of Self-Service Human Resources (SSHR)


What is a Web-based Application?
Chapter 3 - Page 4
Professional User Interfaces versus Self-Service User Interfaces

Professional User Interfaces versus Self-Service User Interfaces
The slide shows the differences between the Professional User Interface (PUI) for HR
Applications and Oracle SSHR. Ask the participants if they can think of any other differences.

Chapter 3 - Page 5
Integration of SSHR and Professional User Interface

Integration of SSHR and Professional User Interface
Professional users have access to general purpose forms, like Define Person and
Assignment, which allow entry of complex transactions.
The self-service interface guides users through specific transactions, such as change
address, which may need approval before the application commits a transaction to the
database.
The system records changes made using either user interface in the same database tables.
This change takes place after validation using business rules in a common set of application
programming interfaces (APIs).
Note: Transaction tables are covered in Fundamentals Module 1 – Implementing SSHR.

Chapter 3 - Page 6
Why Use Self-Service?

Why Use Self-Service?
Provides secure, direct access to systems
• Configurable security rules control access to employee records
• Changes remain subject to manager or HR department approval as required
• Uses responsibilities to control which self-service functions a user can access
User-friendly interface
• Compresses cycle times
• Reduces operating costs
• Lowers staffing requirements for selected tasks
• Allows personalization
Flexibility
• Manages the process flow
• Automated process
• Ensures that correct approvals chain is used
• Usually available when required (evenings/weekends, or for homeworkers)

Chapter 3 - Page 7
Self-Service Functionality in HRMS

Self-Service Functionality in HRMS
HRMS provides many opportunities to take advantage of a self-service interface. Some
examples are listed in this slide. Self-service functions are available in the following functional
areas:
Compensation, Benefits, and Payroll
• Compensation Workbench
• Individual Compensation Distribution
• Vehicle and Mileage Processing
• Payroll
Time and Labor
Talent Management
• Training Enrollment
• Performance and Career
• Management
Enterprise and Workforce Management
• Personal Information

Chapter 3 - Page 8
• Professional Information
• Manage Employment Events
• Views
Workforce Sourcing and Deployment
• Recruitment

Chapter 3 - Page 9
Integration of SSHR with a Third-Party Application

Integration of SSHR with a Third-Party Application
Third-party information sites use a common knowledge repository to manage and
communicate HR and benefits information.
Configure access between Oracle SSHR and a third-party information provider to enable end
users to access personal and absence information.
This feature reduces phone calls and meetings to the HR team as you can source the
required information from the third-party application.
You can ensure that workforce decisions are in compliance with company policy and
legislative compliance by performing constant checks easily on personal and absence
information on the third-party website.

Chapter 3 - Page 10
Configuration Tools for SSHR

Configuration Tools for Web-based Applications
The graphic shows which different configuration tools are used with Web-based applications:
• Data flows between the web-based application and the forms interface.
• The Workflow Builder controls the sequence of events and transactions.
• The Oracle Application Framework defines the appearance of the web pages.
Note: Although the Meta Data Services Repository is mentioned above as a configuration tool,
you should modify web pages using only the Personalization Framework so that any changes
made are preserved during upgrades.
Note: The Meta Data Services Repository is sometime referred to as the AK Dictionary or
Web Applications Dictionary (historical names). Similarly, the Oracle Application Framework
was previously known as the Personalization Framework or the Configuration Framework.

Chapter 3 - Page 11

Highly Configurable Interface
Chapter 3 - Page 12
Workflow-Enabled

Workflow-Enabled
Workflow-enabled functions are those functions with a defined workflow process, usually with
an approvals activity. For example, the Education and Qualifications module and the Change
Supervisor modules are workflow-enabled. Modules that are not workflow-enabled include
Online Payslip and Resume.

Chapter 3 - Page 13
Useful Documentation

Chapter 3 - Page 14
Related Guides

Please refer to the additional guide for labs and/or demos for this lesson.

Chapter 3 - Page 15
Quiz
Answer: b

Chapter 3 - Page 16
Quiz
Answer: a

Chapter 3 - Page 17

Chapter 3 - Page 18
Implementing SSHR
Chapter 4 - Page 1
Chapter 4

Implementing SSHR

Implementing SSHR
Chapter 4 - Page 2
Implementing SSHR
Implementing SSHR
Chapter 4 - Page 3
Objectives
Implementing SSHR
Chapter 4 - Page 4
Self-Service Basics
Chapter 5 - Page 1
Chapter 5

Self-Service Basics

Self-Service Basics
Chapter 5 - Page 2
Self-Service Basics
Self-Service Basics
Chapter 5 - Page 3
e-Business Suite Architecture

e-Business Suite Architecture
The slide illustrates the interaction of the highlighted client side, middle-tier, and server side
components.
• Client/PC side
- Browser (Internet Explorer or Netscape Navigator)
- the user interface
• Middle Tier
- Application Server, includes
Web Listener (Apache)
various other components, including Servlet Engine, JSP and
PL/SQL Gateway
• Server Side
- Data Server, includes
Applications data
Setup data (Menus, responsibilities, etc.)
Meta Data Services Repository (Web page region definitions)
Workflow (process flow definitions)
Self-Service Basics
Chapter 5 - Page 4
Operation of Web-Based Functions

By selecting an option from the menu, you execute an Application Object Library function
(AOL function) which brings up a dynamic HTML page.
In the next few slides we’ll review the architectural components that influence the appearance
and content of the displayed page.
Self-Service Basics
Chapter 5 - Page 5

The appearance of the page is determined by:
• Process Definition (defined in Workflow Builder)
• Region Definition (defined in Meta Data Service Repository)
• Region Configurations (defined in Meta Data Service Repository using the Oracle
Application Framework)
Self-Service Basics
Chapter 5 - Page 6

Page content is determined by:
• Selected Person
- The person associated with the current user (Employee functions), or
- The person selected by the user (Manager functions)
• Security profile
- Is the subject employee included in the Security Profile associated with the current
responsibility for this user?
• Granted employees
- If the employee is not in the user’s security profile, has the employee granted
information to the user?
- Does the user’s responsibility allow access to released information?
• Data security
- Is this function permitted for the legislation code of the subject employee?
Self-Service Basics
Chapter 5 - Page 7
Personal Information: Functional Flow

1. The user chooses the Personal Information function from the user menu.
2. The HTML Call of this function
(OA.jsp?akRegionCode=HR_CREATE_PROCESS_TOP_SS&akRegionsApplicationId=80
0) causes the application to call the HR workflow service, while the Parameter field
specifies the Personal Information workflow process (HR_PERSONAL_INFO_JSP_PRC)
in the HR workflow item type (HRSSA).
Self-Service Basics
Chapter 5 - Page 8

3. The HR workflow service creates an instance of the Personal Information
(HR_PERSONAL_INFO_JSP_PRC) workflow process for the HRSSA item type.
• Note: The FND data security checks to make sure that this function is permitted for the
legislation code of the current employee’s business group. Personal Information is a
global function that is available for all legislation codes.
4. Nested within this process is the subprocess Process Personal Information
(HR_PROCESS_PERINFO_JSP_PRC), which Oracle Workflow runs, stopping on the first
blocking activity called Personal Information Overview
(HR_PERINFO_OVERVIEW_JSP_FCT).
5. The application calls the generic HR_WORKFLOW_SERVICE.BLOCK function, using the
Meta Data Service Repository region HR_OVERVIEW_TOP_SS, specified in the HR
Activity Type Value workflow attribute for this activity. The activity type is JSP.
Self-Service Basics
Chapter 5 - Page 9

6. A page is displayed based on the definition of the HR_OVERVIEW_TOP_SS region and
its nested subregions. The page is influenced by any context-sensitive flexfields and the
cumulative effect of any Oracle Application Framework configurations that relate to these
regions. The definition for this page is stored in the Meta Data Service Repository. To
change the definition you would use the Oracle Application Framework and configure the
region to suit your requirements.
7. The user chooses the Update button in the Main Address page region.
8. Oracle Workflow runs the Process Main Address subprocess. If no past address changes
are awaiting approval or correction, or if no future-dated address changes exist, the
Details page is displayed. The user specifies whether they want to correct an existing
address or to enter an entirely new one. The button displayed to the user will be either
Update/View Future Changes or View Pending Approval.
Self-Service Basics
Chapter 5 - Page 10

9. If the user chooses to enter a new address, the Entry page is displayed. The user enters
the information.
If required, the user can save the information and submit the transaction later. In this case,
the changes entered so far are saved to the transaction tables without server-side
validation.
If the user chooses to correct an existing address, the existing Address information is
displayed. The user corrects the information.
10. When the user has entered the information (or is ready to complete the transaction), they
click the Next link at the bottom of the page. Any field-related errors (bad formatting,
missing fields, and so on ) are flagged by a JavaScript procedure stored on the client and
the user is asked to correct this information.
11. The web page data is sent from the client to the server and server-side validation is
performed by HR Application Programming Interfaces (APIs).
12. If all fields are validated, the Review Page is displayed.
Self-Service Basics
Chapter 5 - Page 11

13. When the changes are complete, the user returns to the Review page and clicks the
Submit Information link to save the changes.
14. If the Main Address part of the Personal Information function is configured for update
without requiring approval , the new address data is inserted directly into the HR tables.
15. If the Main Address part of the Personal Information function is configured to required
approval, the data is inserted into the HR transaction tables and the Approvals process
begins for that item.
16. The workflow item is routed for approval according to the configuration of the Approvals
process.
17. The approver can either approve or reject the transaction or return it to the user for
correction. If the transaction is returned for correction, it is displayed for the user in the
Actions Saved for Later table in the Actions page. The user can reopen the transaction.
The previous values are reloaded from the transaction tables ready for the user to make
the required changes and resubmit. When the approver approves or rejects the
transaction, the user is notified of the transaction status and the transaction details are
deleted from the transaction tables. If the transaction is approved, the data is loaded into
the HR tables.
Self-Service Basics
Chapter 5 - Page 12
Storing Transaction Data

In the next few slides we consider how the attributes of a transaction are assembled and
validated as the user steps through the pages of a web-based transaction. The example is a
two-step transaction from Manage Employment Events. At Step 1 the user makes changes to
Organization, Job, Position and/or Grade.
The entered values are validated by executing the Assignment API in validate mode (the
changes are not submitted to the database). If valid, the values are stored in the HR
Transaction Tables.
Transaction data is stored in the following tables: HR_API_TRANSACTIONS,
• HR_API_TRANSACTION_STEPS , and HR_API_TRANSACTION_VALUES
List of transaction history tables:
• PQH_SS_TRANSACTION_HISTORY
• PQH_SS_STEP_HISTORY
• PQH_SS_VALUE_HISTORY
• PQH_SS_APPROVAL_HISTORY
See: Oracle HRMS Global > Oracle Self-Service Human Resources (SSHR) > Deploy SSHR
Capability > Extending SSHR > Transaction History
Self-Service Basics
Chapter 5 - Page 13

The user moves on to step 2 to make a change to Pay Rate, but does not have enough
information to complete the transaction so clicks on the Save for Later button.
The values entered so far are stored in the Transaction Tables without validation.
Self-Service Basics
Chapter 5 - Page 14

Later, the user retrieves the transaction (using the All Actions Saved for Later function) and
enters the remaining required values and proceeds to the Review page.
You validate the values by executing the Salary API in Validate mode.
Self-Service Basics
Chapter 5 - Page 15

Before submitting the transaction, you have the opportunity to add additional approvers and to
specify additional people to be notified.
Self-Service Basics
Chapter 5 - Page 16

If the approval chain is complete, or if no approvals are required for this transaction, SSHR
executes the following steps:
For each step of the transaction, SSHR retrieves the values stored in the transaction tables
and executes the corresponding API to commit the changes to the application tables.
• The transaction is cleared from transaction tables when either:
- Transaction completes successfully and is committed to the applications tables, or
- Transaction is cancelled by user before completion, or
- Transaction is rejected by approver.
The administrator should run the HR Background Cleanup concurrent program periodically to
clean out transactions that may be left in the transactions tables under other circumstances.
For example, if a power cut occurs when a user is creating a transaction, or if a user closes a
browser during a transaction. Note: Run the HR Background Cleanup concurrent program
within a request set. 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. For more
information, refer to the Running the Workflow Cleanup Process in the Oracle Self-Service
Human Resources Deploy Self-Service Capability Guide
Self-Service Basics
Chapter 5 - Page 17
Quiz
Answer: a
Self-Service Basics
Chapter 5 - Page 18
Quiz
Answer: a
Self-Service Basics
Chapter 5 - Page 19
Summary
Self-Service Basics
Chapter 5 - Page 20

User Access and Security

Chapter 6 - Page 1
Chapter 6



Chapter 6 - Page 2

Chapter 6 - Page 3
Security Mechanisms

Security Mechanisms
In the next few topics you learn how the various security mechanisms depicted in this slide
combine to control user access to SSHR functions.
• You grant responsibilities to users. You can view a list of all owned responsibilities using
the Responsibility Ownership functionality in SSHR. This functionality enables you to
display a list of people with access to each of your owned responsibilities and revoke
access to the responsibilities if appropriate.
• In general, each responsibility has a top menu (controlling navigation to functions) and a
security profile (controlling access to people). Note that if you enable Security Groups,
you assign security profiles are assigned at the user+responsibility level, not to the
responsibility itself.
• Multiple responsibilities can share the same top menu. You can exclude individual
functions for different responsibilities using Function Exclusions.
• Supervisor-based security is one type of security profile that is particularly suitable for
self-service users. This type of security profile dynamically generates a list of available
employees and workers based on either the supervisor hierarchy or the supervisor
assignment hierarchy. You can configure this view to use the position hierarchy by
setting the profile option HR: Self-Service Display Position Hierarchy to Yes.

Chapter 6 - Page 4
• The Data Security mechanism is used by SSHR in conjunction with legislation-specific

menus to prevent legislation-specific functions from being used on people in another
legislation.
• The Assignment-based Security mechanism enables you to restrict security access
based on individual assignments. The security processes evaluate permissions on an
assignment-by-assignment basis, rather than displaying all assignments if a manager
has access to any assignment.
• If you use the Release Information function, then you can supplement the list of people
who appear in a security profile. With this function, you can allow other users (who are
outside of the security profile) to access their records. Similarly, managers can use the
Release Information to allow another manager (who is outside of the security profile) to

access the records for one of their employees.
• You can use Person Search to enable managers to use the Enter Process page to
perform a basic search for any employee within the underlying security profile. Managers
can process employees and workers in the resulting list directly or add them to My List
for future reference. By default, some functions enable managers and HR Professionals
to search for ex-employees and terminated employees.

Chapter 6 - Page 5
Defining User Access

Defining User Access
This slide summarizes the steps involved in setting up users with appropriate access to the
system.
When setting up user access to SSHR, you must set the following profile options:
• HR: Self Service HR Licensed
• HR:Cross Business Group
• HR:Restrict Transactions across Business Groups in SSHR
Distinctly different groups may have different requirements and need different responsibilities,
menus, function configurations, for example.

Chapter 6 - Page 6
Responsibilities

Responsibilities
The menu associated with a responsibility is the primary mechanism (along with functions,
function exclusions, and menu exclusions) for defining what the user can do.
You set up responsibilities to control who the user has access to by using them together with
the following mechanisms:
• Security Profile (profile option)
- If you enable security groups, you associate security with user + responsibility (not
just the responsibility).
• Restrict Transactions across BG (profile option)
• Allow Granted Access (attribute of security profile)
• Search tab (menu configuration)
For additional information on user and security profiles, see the online user documentation.
• Security Overview under Oracle HRMS Global Æ Security.
The delivered SSHR responsibilities are as follows:
• Employee Self-Service
• Manager Self-Service
• HR User Self Service

Chapter 6 - Page 7
• HR Professional
• Payroll Professional
• New User Registration
• Contingent Worker Self-Service
• Responsibility Ownership
• HR Web Administrator
• Candidate Offers
HR Foundation responsibilities:
• Employee Self Service Foundation
• Manager Self Service Foundation

Self-Service Web Applications responsibilities:
• Workflow User Web Applications
• Preferences
The predefined responsibilities provide logical groupings of the delivered functions. They are
provided as a starting point for testing and configuration.
It is unlikely that any of the predefined responsibilities would exactly match the needs of an
actual user, so you should expect to create your own menus and responsibilities for your user
communities.
Note: Extra functionality has been added to the HR Professional responsibility with the latest
releases of SSHR. This responsibility now enables users of this responsibility to access the
Appraisals, questionnaire setup, and Suitability Matching functionality as well as the HR Views
functions which were previously accessed using this responsibility.
The Pay Professional responsibility is also new and enables payroll professionals to view the
payslips for employees.
Also, note that implementers will also need to use additional PUI responsibilities such as:
System Administrator, Application Developer, US HRMS Manager or equivalent for other
localization(s)

Chapter 6 - Page 8
Functions, Menus, and Responsibilities

You can define functions and assign them to multiple menus and responsibilities.
• The Payroll Payments function is an example employee-only function.
• The Personal Information function is used by employees and managers.
• The Termination function is an example manager-only function.

Chapter 6 - Page 9

Creating a Responsibility
Chapter 6 - Page 10
Types of SSHR Users

Types of SSHR Users
SSHR implementers should identify the different groups of people who use SSHR. The
following are examples of typical user groups:
Primary users
• Employees/Contingent workers (individual users)
• Line managers
• HR professionals
Secondary users
• Appraisal reviewers
• Approvers
• Recruiters/hiring managers
Administrators
• HR Web administrators
• HR specialists
• System administrators
When SSHR implementers have identified these groups, they should consider:

Chapter 6 - Page 11
• What tasks they will be performing

• Which user records do they need to access
• How they access user records

Chapter 6 - Page 12
Comparing Employee/Worker and Manager Access

Comparing Employee/Worker and Manager Access
Employees and workers can only view their own records.
Managers and professional users can view their own records plus the records for certain
employees and workers (defined by security profile). Usually managers have access to the
records for the employees or workers they supervise.
There are difference between manager and non-manager parameters. For example,
parameter information for Change Job Mgr function (for managers) is OA Func =
HR_CHANGE_JOB_MGR_SS, whereas the same parameter information for non-managers is
OA Func = HR_CHANGE_JOB_SS

Chapter 6 - Page 13

People versus Users
Chapter 6 - Page 14
Associating User with Person

Associating User with Person
It is actually the person_id of the corresponding person which is stored on the FND_USERS
table.

Chapter 6 - Page 15
Creating Users - Information

Creating Users - Information
You can create people and users using the following methods:
• Manual:
- Create people using Enter and Maintain People form
- Create users using Users form
• Automatic:
- Create people using Create Employee API
- Create users using User Acct API
• Self-Service:
- New Employee Registration function
- New Hire function
The next slides look at how to create users/people using an automated method.
It is advisable to create an SSHR user (or several users as in the practice) so that you can
work with these users in subsequent demonstrations.

Chapter 6 - Page 16
Batch Creation of User Accounts

Batch Creation of User Accounts
An administrator or implementer uses the following programs in batch creation of user
accounts:
User Account Employee Extract Process
• Parameters control which employees are included in the current batch
Data Pump
• Executes hr_user_acct_api API for each person in the current batch to create / inactivate
the person’s user record
• Custom PL/SQL in user hook enforces business rules for user name, responsibility and
security profile
Data Pump Exceptions Report
• Analyzes errors in the user hook
All these concurrent programs can be run from a Super HRMS Manager responsibility. For
more information on these concurrent programs, see the related online documentation under:
• HRMS Applications > Oracle Self-Service Human Resources (SSHR) > Deploy SSHR
Capability > SSHR User Accounts.
User Hooks:

Chapter 6 - Page 17
• Create user (for new users)

- before process hook (set user name, password (optional), responsibility and
security profile)
- after process hook (if password not supplied in before hook, one will be generated
randomly and you will need to use the after hook to communicate this to the user
• Update user
(for inactivating terminated users)
- before process hook (optional additional validation before the user is inactivated)
- after process hook (optional extra processing after the user is inactivated)
• See: Batch Creation of User Accounts in the Deploy SSHR Capability Guide or on the

online help (HRMS Applications > Oracle Self-Service Human Resources (SSHR) >
Deploy SSHR Capability > SSHR and User Access > SSHR User Accounts > Batch
Creation of User Accounts)

Chapter 6 - Page 18
Creating User Hooks

Creating User Hooks
The slide above shows the sequence of steps involved in creating a user hook in Oracle
HRMS. For more information on User Hooks, please see the online help under the following
path:
• Applied Technology > Oracle Applications Developer’s Guide
• HRMS Applications > Oracle Self-Service Human Resources (SSHR) > Deploy SSHR
Capability > SSHR and User Access
If you are modifying user hooks, please note the following:
• Do not modify Oracle HRMS tables and data directly using custom code
• Do not modify delivered API code
• Any code isolated in user hooks is not overwritten during upgrades

Chapter 6 - Page 19
Access Roles for Self-Service Transactions

Access Roles for Self-Service Transactions
You use access role to define a user’s access to workflow activities by defining whether a user
can enter and approve transaction data routed for approval. You define new roles for your
self-service transactions using the Maintain Roles window. Then assign the role to a user in a
supervisor hierarchy or to a position in a position hierarchy.
You create roles using delivered self-service role types:
• SSHR Update Allowed
• SSHR Update Not Allowed
By default, all users can update self-service transactions. If this is correct for the majority of
users, it makes sense to create a role with the type SSHR Update Not Allowed and to only
assign this role to the users who do not have permission to update self-service transactions.
Access roles are also covered in the Self-Service Actions topic.

Chapter 6 - Page 20
Restrict Access to Workflow Transactions

Restrict Access to Workflow Transactions
Workflow administrators can monitor all workflow transactions across the business areas in an
enterprise. Now, depending on your business requirements, you can restrict a workflow
administrator's access to specific workflow transactions using the HR Self Service Selected
Person ID Instance Set. This object instance set uses security profiles to identify the data that
workflow administrators can access. For example, you can use this feature to restrict an
administrator's access to workflow transactions in a specific organization hierarchy or a
business group. Similarly, you can restrict a human resources manager to view only HR
transactions and a payroll executive to view only payroll transactions.
Refer Online Help to restrict access to workflow transactions:
HRMS Applications > Oracle Self-Service Human Resources (SSHR) > Deploy SSHR
Capability > SSHR and User Access > Restricting Access to Workflow Transactions

Chapter 6 - Page 21
Quiz
Answer: a

Chapter 6 - Page 22
Quiz
Answer: a

Chapter 6 - Page 23
Summary

Chapter 6 - Page 24

User Access to People

Chapter 7 - Page 1
Chapter 7



Chapter 7 - Page 2

Chapter 7 - Page 3
Security Profiles (Non-Manager)

Security Profiles (Non-Manager)
It is usually acceptable to use the default View All security profile for each business group for
all non–manager (employee or contingent worker) responsibilities because these functions
restrict the user to accessing only their own record. In other words, the search functions are
not available.

Chapter 7 - Page 4
Security Profiles (Manager)

Security Profiles (Manager)
An SSHR implementer or administrator should take care when considering security profiles for
manager responsibilities because of the potential for managers to search for and access
employees and workers outside their supervisor hierarchy. Options include:
• User-based: list is dynamically generated when the user logs on, starting with the
corresponding person record and traversing the supervisory hierarchy. A single security
profile of this kind will serve most line managers. Avoid using this for senior employees
in the enterprise because of the performance implications of generating a large list.
• Organization hierarchy-based: good for senior employees in the enterprise. Need a
separate security profile for each starting point in the organization hierarchy.
• Position hierarchy-based: necessary for position-based enterprises (public sector).
However, you need a separate security profile for each starting point in the position
hierarchy.
• View all: You can avoid the need to set up multiple security profiles if you also remove
the users’ access to the search capabilities. Users will then only have access to their
reports via the people tree. However, they will not be able to get to granted information
(Release Information).

Chapter 7 - Page 5
• For most SSHR managers, the most appropriate security profile is a user-based profile
with the Supervisor Hierarchy check box flagged.
For more information about Security Profiles, refer online help:
HRMS Applications > Oracle HRMS Global > HR Information Systems > Security Rules >
Security Profiles

Chapter 7 - Page 6
Assignment-Based Security

Assignment-Based Security
Assignment-based security offers an alternative to the traditional supervisor hierarchy. In this
case, the application builds the hierarchies using the supervisor assignment information in the
Assignment window. Sometimes an employee can have two or more assignments with two or
more supervisors. In this case you can use assignment-level security to determine whether or
not supervisors have access to all assignments for an employee or worker, or whether they
only have access to those assignments for which they are the supervisors. If you do not use
assignment-level security, Sally can see Bob’s Assignment 1 (if she can see one assignment,
she can see them all). If you use assignment-level security, Sally can only see the
assignments for which she is the supervisor, in this case, Bob’s Assignment 2.
To enable assignment-level security, there are four required procedures:
• Provide supervisor assignment information.
• Select the Restrict on Individual Assignments option in the Security Profile window.
• Define how the supervisor hierarchy is displayed.

Chapter 7 - Page 7
Interaction of System Profiles

Interaction of System Profiles
This slide describes how to use the HR:Restrict Transactions across Business Groups in
SSHR profile in conjunction with the HR:Cross Business Group (CBG) profile.
• If CBG is Yes and Restrict Transactions is No, SSHR displays persons from a different
business group.
- Subordinates in the business group who are below the person in the different
business group are displayed and their records can be processed.
• If CBG is No and Restrict Transaction is No, SSHR does not display persons from a
different business group.
Note that the system profile “HR:Restrict Transactions across Business Groups in SSHR”
defaults to No at the site level, however, you can override this setting at the responsibility
level.

Chapter 7 - Page 8
Releasing Information

Releasing Information
The Release Information function enables you to extend the number of people in a security
profile. In the above example, Manager 1 has been granted access to the records of another
person who is outside of the security profile (Employee 2). Access can be granted by the other
person (Employee 2) or his manager (Manager 2). For example, a manager can release the
records of a direct report if required, however, the Release Information function is not
delivered on the seeded Manager Self Service menu. To enable the function for a manager,
add the function to the relevant menu.
Note: For Manager 2 to have access, they must have appropriate manager function and must
be assigned to a security profile for which the Allow Granted Access check box is flagged.

Chapter 7 - Page 9

Hierarchy Page
Chapter 7 - Page 10
Searching for People

Searching for People
Managers first see an Enter Process page that they can use to perform a basic search for any
employee within the underlying security profile. Managers can process employees and
workers in the resulting list directly or add them to My List for future reference.
Note: You can extend the security profile for managers by enabling the Release Employee
Information function.
Some functions such as Online Payslip, Appraisals, and Tax Information (US only) enable
managers and HR Professionals to search for ex-employees and terminated employees.
Note: The Approvals processes are also driven off the supervisor hierarchy.
The security profiles discussed in the previous topic (HR: Restrict Transactions Across
Business Groups for SSHR and HR:Cross Business Groups determine which persons can be
accessed by the manager and whether transactions can be carried out on these persons.

Chapter 7 - Page 11
Search Page

Search Page
You can use the Oracle Applications Framework to modify the search functions by hiding or
enabling particular search fields. For example, you could hide the first name field so that users
cannot search using this field.

Chapter 7 - Page 12
Person Types

Person Types
Some functions require managers and HR professionals to search for ex-employees and
terminated employees. For example,a Payroll Professional may want to access an ex-
employee’s payslip or a manager may want to view a terminated employee’s appraisal. The
following functions enable you to search for ex-employees and terminated employees:
• Online Payslip
• Appraisals
• Tax Information (US only)

Chapter 7 - Page 13
My List

My List
This view contains a user-defined list of people for quick reference.
Note: If you set the profile option HR:Expand Role of Contingent Worker to Yes, then
contingent workers will be able to manage other employees.

Chapter 7 - Page 14
Manager Enter Process Pages

The graphic shows the default process flow in solid lines. You can change the entry point to
give the sequence shown in dotted lines. This procedure is illustrated with a practice in the
Configuring Functions topic.

Chapter 7 - Page 15
Security Profiles - Considerations

Security Profiles - Considerations
The security profile that controls access to person records for the Search, should be similar to
the hierarchy display.
For example, if you use a supervisor hierarchy display, the manager can see all people in that
hierarchy and add them to My List. However, if the manager uses a responsibility with an
organization-based profile, for example, the manager can also search for people in that
organization and add them to My List. This reduces the security for SSHR.

Chapter 7 - Page 16
Quiz
Answer: a, b, c

Chapter 7 - Page 17
Quiz
Answer: b

Chapter 7 - Page 18
Summary

Chapter 7 - Page 19


Chapter 7 - Page 20
Implementation Steps
Chapter 8 - Page 1
Chapter 8


Chapter 8 - Page 2
Chapter 8 - Page 3
Implementation Strategy
Chapter 8 - Page 4
Prepare Environment for SSHR

Prepare Environment for SSHR
The required steps are as follows:
• Install Oracle Human Resources
• Set up Apache Server
• Apply latest SSHR patch
• Complete install and setup of Oracle Applications Framework (OAF)
• Set HR: Self Service HR Licensed system profile
• Install Web Browser on every PC
• Set up SSHR Background Cleanup Process
• Install Workflow Builder as needed
• Set access levels for predefined Workflow Item Type
• Configure HRMS Applications
• Check tools for SSHR Implementation
The above steps also represent the minimum steps that a user has to carry out to be able to
run SSHR in a test environment. To be able to test SSHR effectively, implementers should
also set up a business group, set up at least 2 users (one of whom is a supervisor), and
assign responsibilities to the users.
Chapter 8 - Page 5
Configure HRMS Applications

Configure HRMS Applications
To set up work structures for Oracle HRMS, you carry out the following steps:
• Adapt or Create Business Group
• Define Organization Structures
• Define Key Flexfields, Descriptive Flexfields, EITs, and SITs
• Define Lookup Types and Values
- Lookups supply many of the lists of values in Oracle HRMS. They ensure that
users enter only valid data into Oracle HRMS.
• Define Currencies
For more information, see online help:
Capability > Implementation > Implementation Steps for Self-Service HR (SSHR)
Chapter 8 - Page 6
User Access Setup

User Access Setup
• Identify target user groups
• Set up access roles for Self-Service Actions (optional)
• Create user menus
• Create self-service responsibilities
• Set up eligibility processing for Self-Service Actions (optional)
• Configure Person Search
• Set up security profiles – considerations
- Type of hierarchy?
- Allow granted access?
• Link responsibilities to security profiles
• Set the HR:Cross Business Group profile
• Set the Allow Granted Access profile
• Manually create user accounts
• Configure batch creation of user accounts
Chapter 8 - Page 7
Configure Workflow Processes and Page Layouts

Configure Workflow Processes and Approvals
When you configure your workflow process, it is advisable to do this for one target group of
users. Configure the following:
• Display Enterprise Logo
• Define Email Address
• Configure Review Page (optional)
• Configure Effective Date Options (optional)
• Configure National Address Style
• Identify and prioritize required Business Flows
• Configure the Workflow Process
• Configure the Approvals Process
• Configure the Workflow Errors Processes
• Link Workflow Item Types to Function
• Restrict Access to Workflow Transactions
• Add Sub Menus to Self-service User Menus
• Add Functions to User Menus
Chapter 8 - Page 8

Once you have configured the steps outlined in the previous slide, configure the following for
the target group:
• Set Up User Profile Options
• Test the Basic Flow
• Configure the Pages for Your Functions and Notifications - When you create custom
functions, you must set the following parameters:
- Item Type
- Process Name
- Called From
- OA Func
• Configure Flexfields for the Regions
• Create Messages for the Regions
• Define the Name Format in Notifications (Optional)
• Then repeat for other processes and groups of users.
The function parameters are covered in the Configuring Functions lesson.
Chapter 8 - Page 9
Migrate Configuration to Test and Production Environments

Migrate Configuration to Test and Production Environments
Use the tools to migrate configuration between environments in the following ways:
FNDLOAD
• Functions, Menus, Responsibilities
AKLOAD
• Personalizations
WFLOAD
• Workflow definitions
Chapter 8 - Page 10
Summary
Chapter 8 - Page 11
Chapter 8 - Page 12
Configuring SSHR
Chapter 9 - Page 1
Chapter 9

Configuring SSHR

Configuring SSHR
Chapter 9 - Page 2
Configuring SSHR
Configuring SSHR
Chapter 9 - Page 3
Configuring SSHR
Objectives
Chapter 9 - Page 4

Chapter 10 - Page 1
Chapter 10

Responsibilities
Functions, Menus, and


Chapter 10 - Page 2

Functions, Menus and Responsibilities
Chapter 10 - Page 3
Functions, Menus, and Responsibilities - Overview

Functions, Menus, and Responsibilities – Overview
The slide above shows how the different elements discussed in this chapter are linked and
which windows you use to configure them. For example, you link a function to a menu using
the Menu window and link a menu to a responsibility using the Responsibility window.

Chapter 10 - Page 4

This slide illustrates how functions are the building blocks of SSHR. By configuring the
predefined functions and assigning them to a menu, you can define the processes that users
can carry out.

Chapter 10 - Page 5
Configuring Menus

Configuring Menus
The above slide shows a typical self-service menu. The Employee Self-Service menu is
delivered as a standard menu. However, you may decide that you do not want to use all
delivered functions. For example, as shown in the slide above, you may not require the
Competence Profile function. In this case, you would either create your own menu in the
Menus window or exclude the particular function using the Responsibilities window.
You may also want to create your own menus for the following reasons:
• The delivered menus do not contain required functions
• The menu sequence/structure is not appropriate for your business requirements
• Menu prompts are not appropriate for your business requirements
For more information on menu function parameters, see online help:
Capability > Extending SSHR > Menu Function Parameters

Chapter 10 - Page 6
Menu Types

Menu Types
SSHR uses four types of menu: top-level, submenu, hidden submenus, and data security
menus.
• A top-level menu outlines the functions for a responsibility and is the starting point for
navigation.
• A submenu with a prompt is visible to the user, and groups together related functions, for
example, Professional Details.
• A submenu without a defined prompt is hidden from the user. Functions on these
hidden submenus are available to the responsibility for function security without being
directly navigable by the user. Hidden submenus determine which functions appear in
the Actions pages.
• Data security menus define whether a function is global or legislation-specific. A function
must be included in either a global or legislation-specific data security menu before it can
be used and displayed. These menus are not displayed to the user.

Chapter 10 - Page 7
Top-level Menus

Chapter 10 - Page 8
Submenus

Chapter 10 - Page 9
Designing Menus

Chapter 10 - Page 10
Hidden Submenus

Hidden Submenus
To restrict functions available in the Actions menus, remove them from the submenu.

Hidden Submenus

Hidden Submenus
This slide illustrates the two ways in SSHR in which hidden menus are referenced by the
application:
• The Manager Actions page uses a profile option (set at site or responsibility level) to
identify the menu which defines the functions to display on the page.
• The Enter Person Process page uses a region item to identify the menu which defines a
hierarchy of tabbed regions (Employees, Hierarchy, My List, Search).
In either case, you must also attach the submenu to the responsibility’s top menu to satisfy
function security.

Data Security Menus

Data Security Menus
Data security menus relate to the responsibility through security grants.
SSHR uses the data security menus to determine which functions are global and which apply
to specific legislations.

Custom Menus 1

Custom Menus 1
In the above example, the administrator has copied a delivered menu. The next step is to
assign this new menu to the responsibility in the Responsibilities window.
Note: You should always work with copies of the delivered menus.
Reason: The delivered menus are updated when a new patch is installed. This would give
your users immediate access to all the functions in the menu. It is safer to create a copy of the
delivered menu and then include the functions as required.

Custom Menus 2

Custom Menus 2
In the above example, the administrator has copied a delivered menu and excludes selected
functions from the copied (custom) menu by creating function exclusions.
Note: You define function exclusions at the responsibility level without specifying a menu, so
the users of this responsibility will not have access to the excluded functions regardless of
how many submenus they appear on.

Person Tree Navigation Paths

Person Tree Navigation Paths
Navigation Path 1: The manager selects a specific module and then selects the person for
processing. When the manager selects a person from the Person Tree, the manager is taken
directly to the module specified by the function name passed in the pCalledFrom parameter
for the manager function.
Navigation Path 2: The manager first selects the Manager Actions function from the menu and
then selects the required person from the person tree. The available modules, or actions, for
the selected person are displayed in a context–sensitive list. You set the function parameter
pDestination to HR_ACTIONS_SS (instead of setting it to a specific function) to ensure that
the page includes all actions.

Actions Menus

Actions Page
The traditional navigation path for SSHR users is to select a function directly from the user
menu. SSHR continues to support this approach but also introduces a new navigation path
using Actions pages. Instead of selecting the function from the menu, the user selects Actions
(Personal or Manager Actions). SSHR displays a context-sensitive list of available functions.
Note: The default settings for the profile options are Manager Actions Menus and Personal
Actions Menu (at the responsibility level). If you copy a responsibility, you must set the profile
options for your new responsibility.
For more information on profile options, see online help:
Oracle HRMS > Oracle HRMS Global > HR Information Systems > Security Rules > User
Profiles.
There are also corresponding functions and profile options for contingent workers. The
function is Contingent Worker Personal Actions Menu and the profile options are
HR:Contingent Worker Manager Actions Menu and HR:Contingent Worker Personal Actions
Menu.

Employee Actions Page

Employee Actions Page
The navigation path defines the contents of the Employee Actions page.
• Navigation Path 1: The manager displays the Person Tree and then chooses a specific
function (by choosing the Manager Actions V4.0 function). The Employee Actions tab
displays a context–sensitive list of the functions available for the selected employee. The
hidden submenu defined for the HR:Manager Actions Menu profile option determines the
contents of the list. The default menu for this profile option is the predefined Personal
Actions Menu (HR_LINE_MANAGER_PERS_FUNCTIONS).
• Navigation Path 2: If a manager does not select a person in the Person Tree, the
selection defaults to the manager’s own employee record. The list displayed is driven by
the hidden submenu for the HR:Personal Actions Menu profile option. The default menu
for this profile option is the predefined Manager Actions Menu
(HR_LINE_MANAGER_FUNCTIONS).
• The information given above also applies to contingent workers when you use the
Contingent Worker Personal Actions Menu function.

Quiz
Answer: a

Quiz
Answer: a

Summary



Configuring Functions
Chapter 11 - Page 1
Chapter 11


Chapter 11 - Page 2
Chapter 11 - Page 3
Non-Manager versus Manager Functions

Non-Manager versus Manager Functions
Functions are available to employees/workers or managers, or both. In addition to manager
functions, managers also have access to the Person Search capabilities so that they can
search for the employee for whom the transaction is to be performed.
The manager function names are of the format HR_xxxxx_xx_MGR_SS. For example, the
name of the Change Job function is HR_CHANGE_JOB_SS for employees, and
HR_CHANGE_JOB_MGR_SS for managers.
Chapter 11 - Page 4
Considerations
Chapter 11 - Page 5
Copying Delivered Functions

If you change a workflow process, you also need to change the function parameters to point to
the new workflow process.
You can modify the delivered workflow process if you are modifying “customizable” attributes
such as item-level attributes or approval levels. Workflow access levels protect the changes
(discussed in later topic).
You must copy the delivered workflow process and then modify the copy if you are changing
“read-only” objects such as processes, notifications, or messages.
Then log on to Oracle HRMS with the System Administrator responsibility and access the
Form Functions window to copy and configure the functions.
Chapter 11 - Page 6

Administrators can define how users access functions by attaching the function to different
menus. If you want SSHR users to access the function from the Personal or Manager Actions
page, for example, you add the function to the respective submenu (Personal/Manager
Actions).
If you want SSHR users to access the function from the Manager menus using the People
Search function, you need to create a corresponding manager function and add it to the
Manager menu. You base their manager function on the corresponding delivered manager
function.
The data security menus are “hidden”. To enable a function, you must add the function to
either a global or legislation-specific data security menu.
Chapter 11 - Page 7
Adding Custom Functions to Menus

Copy the delivered top-level menu and Personal/Manager Actions submenus.
Chapter 11 - Page 8

Add the function to your version of the top-level menu and the Personal/Manager Actions
submenu.
Chapter 11 - Page 9
Data Security Menus: Restricting Functions by Legislation Code

Data Security Menus: Restricting Functions by Legislation Code
In this example, menus include global functions plus functions for the US and Canada.
The Actions menu contains all functions for all legislations (1 - 6).
The global data security menu contains only the functions valid for all legislations: for
example, Personal Information (1, 2, 3).
The data security menus for the US and Canada contain only the functions valid for those
legislations (4, 5 for the US and 6 for Canada).
When a US SSHR displays the Actions page, the functions that appear are:
• All the global functions (defined by the global data security menu)
• The US-specific functions (defined by the US data security menu)
Adding Custom Functions

Adding Custom Functions
In this example, menus include custom copies of functions, as well as legislative-specific
functions.
You add custom functions to the appropriate data security menu to define which legislation a
custom function is available for. The Actions menu then appears with only the functions that
are available to the specific user.
Note: The custom functions are those shown with broken lines.
Data Security Menus

Data Security Menus
Data security menus relate to the responsibility using security grants.
SSHR uses the data security menus to determine which functions are global and which are for
specific legislations.

You must also add your custom functions to the respective data security menu (global or
legislation-specific).

Finally, you must assign the custom menus to the correct responsibility and also link the data
security menus to the responsibility.
Changing the Manager Entry Pages

By default, the Manager functions call the Hierarchy Page first. This sequence is determined
by the function parameter akRegionCode (under Web HTML tab of Form Functions window).
The default value is HR_PERSON_TREE_TOP.
You can change the value of this parameter to point to the My List page or the Search page
by setting the value as follows:
• HR_PERSON_SEARCH_TOP_SS for Person Search
• HR_MY_LIST_TOP_SS for My List
Quiz
Answer: a
Quiz
Answer: b
Summary

Using the Workflow Builder

Chapter 12 - Page 1
Chapter 12



Chapter 12 - Page 2

Chapter 12 - Page 3
Workflow-Enabled SSHR Functions

Workflow-Enabled SSHR Functions
Functions are generally workflow-enabled if they require approvals.

Chapter 12 - Page 4
Workflow Builder

Workflow Builder
In Oracle Workflow, all processes are associated with an item type. An item type can include
one or more processes and related objects, such as item attributes, functions, and messages.
An item type is a way of grouping together related items.
Oracle SSHR delivers a number of predefined workflow item types containing workflow
processes that you can work with.
• HR (HRSSA) (displayed in the slide above)
• HR Self-Service Benefits

Chapter 12 - Page 5
Working with the Workflow Builder

Working with the Workflow Builder
If a user leaves workflow processes running after a system crash or if an administrator
disables or removes a user ID, you can run a clean-up process to clear temporary tables. The
process cleans up temporary tables by removing redundant transaction information.
The concurrent program for cleaning up workflow transaction tables is: ‘Purge Obsolete
Workflow Runtime Data’. Administrators can run this program from the Submit Requests
window.

Chapter 12 - Page 6
Working with Workflow Item Types

Working with Workflow Item Types
This procedure is different from the previous HR Development advice which recommended
that customers make their changes to a copy of the delivered item type.
Note: We recommend that you do not change the item type directly in the database. Instead,
download the item type to a .wft file which you then source control. Make the changes to this
file and then upload it to the server.
For more information on Workflow Objects and Item Types, refer:
Capability > SSHR and Workflow > Workflow Objects and Item Types

Chapter 12 - Page 7
Workflow Access Levels

Workflow Access Levels
The access protection levels ensure that your customizations are preserved during an
upgrade. As long as you set your own access level to 100 or (higher) while working on
changes, the access protection ensures that when an upgrade takes place, the "read-only"
objects are updated and that customizations made to the "customizable" objects are
preserved.
You can change objects if your access level is less than or equal to the object's protection
level and greater than or equal to the object's customization level.

Chapter 12 - Page 8

Chapter 12 - Page 9
Configurable and Locked Workflow Objects

Changing Workflow Objects

Changing Workflow Objects
You change the workflow objects in the Workflow Builder and then change the function
parameters for your custom self-service functions to point to your changed workflow process.

Chaining Workflow Processes

Chaining Workflow Processes
Oracle Workflow enables you to combine different Manage Employment Events modules into
one workflow process. Such processes are known as chained processes. SSHR includes a
number of predefined chained processes that appear as functions on the user menus.
The following slide includes a graphic of chained modules.

Chaining Self-Service Activities

Chaining Self-Service Activities
The Worker Status Change chained process consists of the above modules. However, by
chaining the modules for employment events, you can create your own chained processes or
modify copies of the delivered processes.
Note: Manage Employment Events modules are covered in more detail in the People
Management curriculum.

Processes

Manage Employment Events – Activities Some Delivered

Sequencing Restrictions for Manage Employment Event Pages

Sequencing Restrictions for Manage Employment Event Pages
The order of workflow processes must be carefully designed to ensure business rules are
maintained and implemented. If you choose to create your own chained processes and
functionality, you must consider certain rules when designing the sequence of functions.
You can configure your own processes in any number of ways but they must comply with the
restrictions listed above. For example, you could configure a process that follows this
sequence:
• Step 1: Assignment
• Step 2: Location
• Step 5: Work Schedule
But, you cannot configure a process in this order, as you will break business rules:
• Step 2: Location
• Step 1: Assignment
• Step 5: Work Schedule
As long as you maintain the order of steps you can configure whichever workflow processes
your enterprise needs.

Applying a Patch

Applying a Patch
Readme files are usually included in the .zip file delivered with the patch.

Quiz
Answer: b

Quiz
Answer: a

Summary


Configuring Web Page Layouts

Chapter 13 - Page 1
Chapter 13
Layouts

Configuring Web Page


Chapter 13 - Page 2

Chapter 13 - Page 3
Configuring Self-Service Web Pages

Configuring Self-Service Web Pages
This sample web page shows which elements an administrator can configure.
Note: Configure the buttons such as Update and Add by selecting the Advanced Settings
button in the Oracle Applications Framework (OAF).
Refer to: Oracle Self-Service Human Resources (SSHR) > Deploy SSHR Capability >
Workforce Sourcing and Deployment > Employee Demographics > Basic Details

Chapter 13 - Page 4
Oracle Applications Framework

Oracle Applications Framework
You use the Oracle Applications Framework (OAF) to configure web pages for distinct
audiences. For example, you can create one set of personalizations for a line manager and
one set for an employee. Alternatively, you may personalize a self-service page differently for
localizations, organizations, and sites. To enable this flexibility, the OA Framework provides
two levels of personalization privileges:
• Administrator level - administrators can choose to create personalizations at a number of
different levels, for example, at the responsibility, site, or function level. These levels are
arranged in a hierarchy where lower level personalizations take precedence over higher
level personalizations.
• End-user level - users can create personalizations for specific regions and items, for
example, a user can hide or display particular columns in a table. A user can also
personalize a portlet to hide or display particular information. User personalizations are
only seen by the creating user.

Chapter 13 - Page 5
Personalization Levels

The Oracle Applications Framework creates configurations to suit the requirements of different
users. The Framework uses personalization levels which enable the implementation team to
target the personalizations at specific users.
Only administrators with the correct authorization can create administration-level
configurations (administrators can assign authorization using a profile option at responsibility
level).
Function Level: A function in the Oracle E-Business Suite is a token that is registered under a
unique name for the purpose of assigning it to, or excluding it from, a responsibility. You can
create personalizations for a region at the Function level, such that the personalizations are
visible only when you display the region while the specific function is in context.
Industry Level: The customer administrator can use the delivered set of predefined industry
categories to define personalizations according to vertical market.
Localization Level: Suppose you need to distribute your applications to a particular locale of
users, where certain fields or buttons are hidden and labels need to be changed to
accommodate that locale. You can do that by creating Localization level personalizations in
the relevant regions before delivering your applications. All end-users for the specific locale
will see the applied localization personalizations. For example, Oracle's localization teams
would make country-specific localization-level personalizations in HR applications before

Chapter 13 - Page 6
delivering the applications to customers in a given country. In the Personalization Context,

location refers to the legislation or country-specific personalization.
Site Level: A site refers to an installation of Oracle Framework-based applications.
Personalizations that you make at the site level affect all users of the current installation.

Chapter 13 - Page 7

Organization Level: Personalization at organization level refers to configuration for HR
organizations with Business Group classification. For example, you might make a
personalization at the Org level to hide certain fields because they are not pertinent to the
context of a particular Org.
Responsibility Level: A responsibility represents a specific level of authority within an
application. Each responsibility lets you access specific functions or a set of product pages,
menus, reports and data to fulfill your role in an application.
User-level or portlet-level personalizations, on the other hand, can be made only to certain
tables in query regions or portlets. User or portlet-level personalizations can be made directly
by an end-user and are visible only to that end-user, hence they are collectively referred to as
end user-level personalizations.
Examples of User Level Personalizations :
Portlet: Personalize the portlet to display news headlines.
User: Create personalized views for tables.
For more information on Personalization Levels, refer to the Oracle Application Framework
Personalization Guide

Chapter 13 - Page 8
Profile Options for Oracle Applications Framework

Profile Options for Personalization Framework
Personalize Self-Service Defn (FND_CUSTOM_OA_DEFINITION)
• Set to Yes or No at the user or responsibility level
• Displays Personalize Page links on web pages
• Default is No
FND: Personalization Region Link Enabled
(FND_PERSONALIZATION_REGION_LINK_ENABLED)
• Set to Yes or No at Site, Application, Responsibility, User
• Displays Personalize Region links in web page regions
• Default is No
Disable Self-Service Personal
(FND_DISABLE_OA_CUSTOMIZATIONS)
• Set to Yes or No at the site, application, or user level
• If set to Yes, any configurations are suppressed regardless of level
• Useful when debugging
• Default is No

Chapter 13 - Page 9
Personalization - Buttons and Links

Personalize Region – Buttons and Links
If you set the Personalize Self-Service Defn profile option to Yes, the Personalize Page link is
displayed in the global tool bar. If you also set the FND: Personalize Region Link Enabled
profile option set to Yes, you also see a Personalize Region link in each region..
• Clicking the Personalize Region in a specific region allows personalization of that region.
• Clicking the global Personalize Page button allows the SSHR user or administrator to
navigate to any of the regions included in the current page.


Configuration Options within the Oracle Applications Framework

Additional Options for Tabular Regions

Additional Options for Tabular Regions
You can modify the number of columns and rows in tables. You can also change the column
labels and change the sequence of columns.

Adding User Instructions

Adding User Instructions
To create new messages, log on with the Application Developer responsibility and choose
Application > Messages. Create a new message and save it. Then go to the Regions window
and insert your new message in the Message column for your region.

Flexfields

Flexfields
Key flexfields uniquely identify a record, for example, the Job Key flexfield.
Descriptive flexfields, for example, Additional Assignment Details, add attributes to existing
object.

Configuring the e-mail Address

Configuring the e-mail Address
To configure the email addresses:
1. Open the Oracle Workflow Builder.
2. Open your configured HR item type (HRSSA).
3. Select Attributes.
4. Select the attribute HR Department Email ID and enter the appropriate email address in
the Default Value field
5. Save your work.

Configuring the Global Button Bar

Configuring the Global Button Bar
This slide gives the possible functions that are available in the Global Button Bar. To hide a
function, for example, the Preferences button, use the Menus window and open the given
menu. You can also hide the entire bar using the Personalization Framework.

Logos

Quiz
Answer: a

Quiz
Answer: a

Summary


Approvals
Chapter 14 - Page 1
Chapter 14

Approvals

Approvals
Chapter 14 - Page 2
Approvals
Approvals
Chapter 14 - Page 3
Basic Approvals Loop

Basic Approvals Loop
The slide above shows the basic approvals loop. This loop represents the processing
sequence which is executed behind the scenes in a self-service transaction. When the user
submits a self-service transaction for approval, the approvals logic checks whether the
approver is the Final Approver. If this is the case, the approvals loop ends. If the approver is
not the final approver, the approvals logic fetches the next approver in the approval chain.
See online help: HRMS Applications > Oracle Self-Service Human Resources (SSHR) >
Deploy SSHR Capability > Approvals > Approvals in SSHR
Approvals
Chapter 14 - Page 4
Approvals

Approvals
Either Oracle Approvals Management or a customizable PL/SQL package determines the list
of approvers in the Review page. Although both approaches are available, only AME is fully
supported by Oracle in current SSHR releases.
If you enable Dynamic Approvals using the Workflow Builder, the SSHR user can add
additional approvers/notifications recipients in the Review Page. If you do not enable Dynamic
Approvals and standard approvals is used, the SSHR user cannot add additional approvers or
notification recipients in the Review Page.
AME is covered later in the topic.
Approvals
Chapter 14 - Page 5
Enabling Dynamic Approvals

Enabling Dynamic Approvals
The above graphic shows which workflow attribute you use to enable dynamic approvals. You
select the Node Attributes for the Review Page module within the workflow process. To
enable Dynamic Approvals, select the attribute value Yes – Dynamic Approvals. To enable
Standard Approvals, select the attribute value Yes. Alternatively, select No to disable the
approval functionality.
Approvals
Chapter 14 - Page 6
Configurable Approvals Options

Configurable Approvals Options
The standard behaviour for SSHR functions is to use AME (Oracle Approvals Management).
Your AME approval routing rules will override any settings defined in the workflow builder, for
example, number of approval levels.
For more information, see online help: HRMS Applications > Oracle Self-Service Human
Resources (SSHR) > Deploy SSHR Capability > Approvals > Oracle Approvals Management
(AME) Configuration > Standard AME Attributes for SSHR
Approvals
Chapter 14 - Page 7
What is AME?

What Is AME?
Calling application refers to the application that is using AME components to define the
approval process. Calling applications can be Oracle applications or any application that is
uses PL/SQL code.
Approvals
Chapter 14 - Page 8
Approvals
When Can I Use AME?
Chapter 14 - Page 9
Business Requirements

Business Requirements: Example of approval loop using AME
The diagram above shows a basic business process using AME.
1. An employee creates their expense reports
2. An employee submits their expenses for approval.
3. These expenses go to the immediate manager (defined in the supervisor hierarchy) who
may have a sign off limit.
4. If the expenses cannot be approved by the immediate manager, they will then get
passed to the next manager in the chain.
You can use AME, to define simple or complex rules which allow line level approval
based on the sign off authority. For example, you may set up a substitution rule, which
says that if an expense value is below $100, then manager 1 can approve the expenses
and if the value is more than $100, then manager 2 needs to approve the transaction. If
the default approvers fail to approve the transaction, and the transaction includes
additional approvers, AME applies the substitution rule a second time on the additional
approvers.
Note: AME processes substitution rules a second time at the end of the processing
cycle only when the attribute REPEAT_SUBSTITUTION is set to true.
5. The expenses get paid.
Approvals
Overview of AME Components

Overview of AME Components
Oracle SSHR provides standard AME attributes for self-service transactions. You can use
these standard attributes to better define your approvals processes. For the complete list of
attributes, see Oracle Approvals Management (AME) Configuration in the online help.
Approvals
Approvals
Approval Considerations
Approvals
Approvals Routing
Quiz
Approvals
Answer: a
Quiz
Approvals
Answer: a
Approvals
Summary

Using SSHR
Chapter 15 - Page 1
Chapter 15

Using SSHR

Using SSHR
Chapter 15 - Page 2
Using SSHR
Using SSHR
Chapter 15 - Page 3
Using SSHR
Objectives
Chapter 15 - Page 4
Common SSHR Functions

Chapter 16 - Page 1
Chapter 16



Chapter 16 - Page 2

Chapter 16 - Page 3
Common Functionality

Common Functionality
These functions are grouped together as “common functions” because they do not belong to
any specific functional area or they are common to all SSHR functions.

Chapter 16 - Page 4
Review Page

Review Page
The top region for the review page, HR_REVIEW_SS, contains multiple subregions, one for
each of the modules that uses the review page, and shows only the subregion for current
module, for example, HR_BASIC_DETAILS_REVIEW_SS for the Basic Details area of the
Personal Information module.
The Review Page for SSHR has the following characteristics:
• Included in most SSHR processes
• Allows the user to check a transaction before submission
• Displays approvals
• Allows a user to add additional notification recipients and approvers
• Displays before and after values in a tabular format, highlighting any fields which have
changed
• Can configure field properties using the Personalization Framework
• Can configure instructions and approval properties using Workflow Builder
• Allows a user to attach documents

Chapter 16 - Page 5
Return for Correction

Return for Correction
The Return for Correction page enables an approver to return a transaction to the previous
approver or initiator of the transaction for correction of information. When the approver or
initiator receives the Return for Correction notification, he or she can correct the information
and continue the transaction. In this case, the transaction is stored in the table on the Actions
page for the user until the user provides the required information or corrects the submitted
information.

Chapter 16 - Page 6
Save for Later

Save for Later
The slide illustrates how the Save for Later functionality is used within self-service
transactions:
• A user can start a transaction and save it for completion at a later time
• A user can select stored transactions from the Actions table

Chapter 16 - Page 7
New User Registration

New User Registration
The New User Registration menu/responsibility provide the following functions:
• Create User Name
• New Employee Registration
• Non-Employee Registration
The New Employee Registration function prompts the user to enter Personal, Assignment,
and Benefits information. The Non-Employee Registration function prompts the user to enter
information and this does not create an employee record. The Non-Employee Registration
function is generally used by third parties, for example, Benefits provider. Participants or their
dependents can log on to SSHR, for example, for COBRA registration.
There are several advantages of using the New User Registration functionality. For example:
• Decentralized entry of user and personal information – reduced administration.
• Particularly good if a large number of users need to be created.
• Improved accuracy of personal information as user enters it themselves.
• User can define their own password.

Chapter 16 - Page 8
New Employee Registration Process

New Employee Registration Process
The generic user name and generic password provides access to SSHR. A default
organization, payroll, and responsibility are assigned to the generic user name.
A user who is given the generic user name and password will be able to log in, select the
generic responsibility and, using the New Employee Registration function, create themselves
a person record and corresponding personal user name and password.
Oracle HRMS uses the default values for the generic user to build the new person record and
user record. The process for New Employee Registration is as follows:
• Set up a responsibility with access to the function
• Set up a generic user name and assign the responsibility to it
• Define default values via profile options for the responsibility or generic user. The profile
options are:
- OAB:User to Organization Link
- OAB:User to Payroll Link
- OAB:Self Registered User Default Responsibility
• Notify new employees or managers of the generic user id and password
• Users log in as the generic user to create a new employee and corresponding new user

Chapter 16 - Page 9
• The new employee and user will combine personal information for the new employee
with default information defined for the generic user.

Document Manager

Document Manager
Create documents
• PDF document - In a PDF editing application, add named form fields to contain data
from the action. The form field names are the tags you map to your action's attributes in
Document Management.
• RTF document - When you use an RTF template, the application converts it to PDF
format when you generate your document. You can also insert conditional programming
statements available using RTF technology to display or hide fields based on the values
of other fields. For example, you can display or hide data based on the department or e-
mail address.
Configure Document Groups and Attribute Mappings
• Use document groups to define a collection of documents and associate them with their
corresponding workflow process. To create the link between the document group and
the workflow process, add the function parameter
pGroupName=<documentgroupshortname> using a System Administrator responsibility.
• Add a document to a selected group. You can select from a list of documents in the
database that are not yet part of a group, or you can add a new document.

• Define document and update Document Pages. If you use FastFormula to populate
document tags with returned values from the database, or override tag values with
literals, specify them as well.
• Map attributes to merge data from transaction data attributes to form fields. You can
include both current and proposed values in a document, and also Header Information
attributes containing details from the selected person's record. When you create the pdf
document, it is helpful to know which attributes are available in the self-service function
that will trigger the document generation. For example, the Change Manager page uses
the following attributes:
- Current Manager Name
- Employee Name

- Manager Name
To create a document for the Change Manager function, you could, therefore, include those
attributes in your pdf document as fields.
For a list of the delivered attributes, see Document Manager in the online help for SSHR.
• Define Documents Properties to change the Document Type. Available types include
Pre Approval, Post Approval, and Both.
• Generate pre-approval versions of documents while it is still in process. Generate post-
approval versions on final approval. Initiators receive a notification containing a link to
the Document Information page, containing post-approval versions of available
documents.
Refer to : HRMS Applications > Oracle Self-Service Human Resources (SSHR) > Deploy
SSHR Capability > Common SSHR Modules > Document Management

FastFormula Options for Document Manager

Fast Formula Options for Document Manager
For more detailed information on the FastFormula options for the Document Manager, see the
online help under:
Oracle HRMS > Deploy Oracle Self-Service Human Resources > Common SSHR Functions

Quiz
Answer: a

Quiz
Answer: a

Summary


Self-Service Actions
Chapter 17 - Page 1
Chapter 17


Chapter 17 - Page 2
Chapter 17 - Page 3
Overview – Self-Service Actions
Chapter 17 - Page 4
Types of Self-Service Action
Chapter 17 - Page 5
Life-Cycle of Self-Service Action

Life-Cycle of Self-Service Action
Before you initiate a self-service action, you use the search functions to select the correct
person. The People List and Action pages confirm whether a person is eligible for the selected
action on the specified effective date. The Actions page also informs you of saved and
pending actions.
Self-service actions use Oracle's standard workflow and approvals management tools to
generate a list of approvers and route your action automatically.
Note: The life-cycle of a self-service action is greatly influenced by profile options and
effective dates. For example, you can use profile options to define the behavior if a manager
creates intervening actions or future-dated transactions.
For more information on profile options, see the following slide.
Online Help:
Capability > Common SSHR Modules > Self-Service Actions
Chapter 17 - Page 6
Profile Options for Self-Service Actions

• HR:Allow Approver updates to Self Service actions
- Allows an approver to make updates to actions.
• HR:Allow concurrent Self Service actions
- Allows multiple simultaneous self-service actions.
• HR:Manage Self Service actions when future-dated changes exist
- If you set this profile option to Yes, you can control potential data conflicts when
future-dated changes exist. The default setting is Stop with an Error. This forces
the user to choose an effective date subsequent to any future-dated change.
Change this to Allow Approval (Notify HR Rep) to allow the user to select a date
prior to any future-dated changes. After final approval the transaction is forwarded
to an HR Representative for review and manual entry into the database.
- Attention: If you set this profile option to Allow Approval, and you have enabled
HR:Allow Approver Updates to Self Service Actions, Oracle recommends that you
also enable HR:Refresh Self Service Actions with Data from Intervening Actions.
• HR:Refresh Self Service actions with data from intervening actions
- Allows you to control the effect of concurrent actions. If set to Yes, when a pending
change is approved which affects the current transaction, the application displays a
Chapter 17 - Page 7
warning message with changed attributes and refreshes the data .If set to No
(default), the application displays a warning message and the transaction fails.
Oracle recommends that you set this profile option to Yes if HR: Allow Approver
Updates to Self Service Actions is also Yes.
- Note: Oracle recommends that you enable this option if you have set the system
profile HR:Manage Self Service Actions When Future-Dated Changes Exist to
Allow Approval (Notify HR Rep). Otherwise you should disable this option.
• HR:Display Position Hierarchy
- If set to Yes, SSHR uses the position hierarchy will be used in the HGrid on the
Enter Process page. By default the HGrid uses supervisor hierarchy.
Chapter 17 - Page 8

• HR: Position Default Options for SSHR enables you to configure the application to
populate default information based on the position you select for an assignment. You
can configure the user profile to populate Department, Job, Grade, Payroll, Supervisor,
Probation Period, Bargaining Unit, Salary Basis, Work Hours, and Location.
Implementers can choose whether to populate default data with no warning, display a
warning, ask the user to decide, or turn off position defaulting.
• HR:Allow use of eligibility for Self Service actions
- If set to yes, the Eligibility column appears on the Actions page and all eligible and
ineligible actions are displayed. The Eligibility column distinguishes between them.
If set to No (default), only eligible actions are displayed and the Eligibility column is
not displayed.
- Note: Managers cannot process ineligible actions unless the profile option
HR:Allow Processing of Ineligible Self Service Actions is also set to Yes.
• HR:Allow processing of ineligible Self Service actions
- If set to Yes, managers can process ineligible self service actions.
Chapter 17 - Page 9
- Note: This option depends on also enabling the profile option HR:Allow Use of
Eligibility for Self Service Actions in order to display ineligible actions in the first
instance.
• HR:Run BENMNGLE when processing a Self Service action
- In order to ensure that the list of eligible actions and sub-actions is up to date, you
must periodically run the Participation Batch Process (Run Benefits Manage Life
Events Process) for that individual. This can run automatically every time a
manager initiates an action by setting the profile option, HR:Run BENMNGLE
When Processing a Self Service Action, to Yes.
Managing Dates

Managing Dates
Effective dates:
• The user can decide whether a transaction is valid on approval or on a specific date.
• The application also checks the following dates when the user submits the transaction:
- hire_date: Checks that the effective date entered is later than the hire date.
- termination_date: Checks that the effective date entered is earlier than the
termination date.
- pending_workflow: Checks if there are changes pending in the workflow tables for
the selected person.
- future_assignment: Checks if there are any future assignment changes with
respect to the effective date entered.
- insert_mode: Issues a warning (alert) if the effective date of the assignment is less
than a future-dated change.
Concurrent transactions: You control concurrent transaction using the following profile options:
- HR:Allow Concurrent Self Service Actions to Yes.
- HR:Refresh Self Service Actions With Data From Intervening Actions
- HR:Manage Self Service Actions When Future-Dated Changes Exist.
Conflicting Actions
Conflicting Actions - Resolution

Conflicting Actions - Resolution
Initiation date: when you submit your action for approval (usually the system date)
Effective date: when approved action takes effect (not necessarily the approval date)
Approval date: when you save your action to the database
Concurrent Actions: The application processes multiple actions on a selected person at the
same time. On final approval, each action takes effect on its own effective date, superseding
any actions with a previous effective date.
Intervening Actions: After your action is in process, the application encounters an approved
action on the same person with an effective date that falls between your initiation date and
effective date. Your setup can help you manage which information prevails, and (as
appropriate) replace values in your action.
Future-Dated and Retroactive Actions: After your action is in process, the application
encounters an approved action on the same person with a later effective date. Your setup can
allow you to route your action to a Human Resources representative on final approval, for
manual entry of all appropriate changes.
Configuring Self-Service Actions
Combining Activities for Self-Service Actions

What-If Analysis

What-If Analysis
What-If Analysis enables you to see the impact of your proposed action on the selected
person's entitlements to compensation and benefits. For example, you could use What-If
Analysis to see how a life insurance premium would be affected by different pay increases.
Note: To use What-If Analysis, you must run Oracle Advanced Benefits.
Eligibility Processing

Eligibility Processing
There are 2 types of eligibility profile: Participant and Dependent
You can define eligibility at all levels of the compensation object hierarchy: Program, Plan
Type, plan, and options. The eligibility profile is not the only deciding factor whether a
participant or dependent is eligible. You must also consider enrollment requirements and/or
life events.
Manage Employment Events and eligibility are discussed in greater depth in the People
Management curriculum.
Note: Manage Employment Events may sometimes be referred to as Self-Service Actions.
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. You refine the criteria that make a person eligible by defining eligibility profiles and
linking them to the sub action. You can link each form function to multiple actions and sub
actions, but you can determine eligibility only for sub actions.
Online Help;
Capability > Common SSHR Modules > Set Up Eligibility Processing
Quiz
Answer: a
Quiz
Answer: a
Summary

Integrating SSHR with Third-
Party Information Providers
Chapter 18
Integrating SSHR with Third-Party Information Providers

Chapter 18 - Page 1

Chapter 18 - Page 2

Chapter 18 - Page 3

Integrating SSHR with Third-Party Information Provider

Integrating SSHR with a Third-Party Information Provider
Third-party information sites use a common knowledge repository to manage and
communicate HR and benefits information.
Using Info Online, a generic framework to integrate Oracle Applications with partner
applications, you can configure access between Oracle HRMS products and third-party
information providers. Once the links are enabled, users can access an information provider
web site directly from a button or link on an Oracle HRMS window or self-service web page.
You can configure access between Oracle Self-Service HR (Oracle SSHR) and Enwisen, a
third-party information provider to enable end users to access company specific information or
any other relevant information hosted on the Enwisen web site. Managers, employees, and
contingent workers can use this feature to access third party content sites that host company
specific policies or information directly from the self-service pages.
Note: The information that your workforce can access on the information provider web site
depends on the agreement with the information provider.

Chapter 18 - Page 4
Accessing Third-Party Information from the Self -Service Pages

Accessing Third-Party Information from the Self-Service Pages
Accessing Handbook link on Enwisen from the Personal Information Page
Employees can access company policies on the Enwisen web site from the Handbook link on
the Personal Information page. The Info Online content container that displays the Handbook
link is hidden by default.
Accessing Enwisen from the Absence Management Page
The Absence Management page available from the Manager and Employee Self-Service
responsibilities contains the Info Online content container, which is hidden by default.This
content container displays the Time Off Policy link (default link) to access, for example,
company's absence policies on the Enwisen web site.

Chapter 18 - Page 5
Info Online – Enables Integration with Third-Party Information

Providers

Info Online – Enables Integration with Third-Party Information Providers
Info Online is a generic framework to integrate Oracle Applications with partner applications.
• Enables users to access information from third-party providers and integrations.
• Users access information provider web sites from the self-service web pages either
through links on Benefits pages or through the Info Online content container.
• Info Online content container:
- An ancillary region that appears on self-service web pages.
- Topics and providers appear as an alphabetical list of links in the content
container.
If your enterprise has an agreement with any third-party information, then you must complete
the basic implementation steps that are required to configure links between Oracle HRMS
products and the information provider using the Info Online functionality.
Then, you can configure additional implementation steps required for individual information
providers, such as Enwisen.

Chapter 18 - Page 6
Enabling the Info Online Functionality

Enabling the Info Online Functionality
• Set the following profile options to set up links between Oracle HRMS and any
information provider web sites:
- HR: KI Framework Version
- HR: Extension Agent Enabled
- HR: Extension Agent Client Timeout
• Setting the following additional profile options is optional if you are setting up links
between Oracle HRMS and any information provider web sites:
- HR: Extension Agent
- HR: Info Online: Open in New Window
- HR: Info Online: Toolbar Icon
- HR: KI Maximum Topics and Integrations
- HR: Servlet Timeout
- HR: KI Providers Enabled
- HR: KI Topics Enabled
- HR: KI User Options Enabled

Chapter 18 - Page 7
• Configure links to information providers: After you configure Info Online, you can access
configured partners in self service through the Info Online content container
• Display the Info Online content container, if hidden by default.

Chapter 18 - Page 8
Setting up Links Between Oracle Self-Service HR and Enwisen

Setting up Links Between Oracle Self-Service HR and Enwisen
If your enterprise has an agreement with Enwisen, a third-party information provider to enable
your workforce access company specific information or any other relevant information hosted
on the Enwisen web site, then you can configure links to Enwisen.
Note: The company information that your workforce can access on Enwisen depends on your
agreement with Enwisen.
See Online Help:
• HRMS Applications > Oracle HRMS > Oracle HRMS Global > HR Information Systems
> Info Online Links to Information Provider Websites
• HRMS Applications > Oracle HRMS > Oracle HRMS Global > HR Information Systems
> Info Online Links to Enwisen

Chapter 18 - Page 9
Display Info Online Content Container on Self-Service Pages

Display Info Online Content Container on Self-Service Pages
Personal Information Page
The Personal Information page available from the Employee Self-Service responsibility
contains the Info Online content container, which is hidden by default. This content container
displays the Handbook link (default link) to access, for example, company policies on the
Enwisen web site.
To enable users to access Enwisen, complete the following steps. Using the Personalization
Framework function:
• Display the Info Online content container.
• Display the default Handbook link or configure links to Enwisen according to your
Absence Management Page
The Absence Management page available from the Manager and Employee Self-Service
responsibilities contains the Info Online content container, which is hidden by default. This
content container displays the Time Off Policy link (default link) to access, for example,
company's absence policies on the Enwisen web site.
To enable users to access Enwisen, complete the following steps. Using the Personalization
Framework function:

• Display the Info Online content container.

• Display the default Time Off Policy link or configure links to Enwisen according to your

Summary

Advanced Topics
Chapter 19 - Page 1
Chapter 19

Advanced Topics

Advanced Topics
Chapter 19 - Page 2
Advanced Topics
Advanced Topics
Chapter 19 - Page 3
Advanced Topics
Objectives
Chapter 19 - Page 4
Employee Directory

Employee Directory
The Employee Directory has been given its own topic here as there are several set-up steps
which are necessary before the function can be used. It has been included in the Common
Modules section here because it does not belong to one specific functional area.
The Employee Directory provides an easily accessible, highly configurable lookup of people
within your enterprise. Users can search for a specific person against a range of data, and
navigate through the organization to view details of a person's manager or direct reports. You
can set up the Employee Directory to search for people from a single business group or from
multiple business groups as required.
Advanced Topics
Chapter 19 - Page 5
Single Sign-On or Anonymous Log-In?

Single Sign-On or Anonymous Log-In?
The Employee Directory is read-only unless single sign-on is enabled.
For information on how to set up the Employee Directory function, see online help:
Capability > Workforce Sourcing and Deployment > The Employee Directory Module
Advanced Topics
Chapter 19 - Page 6
Responsibility Ownership

Responsibility Ownership
As an administrator or implementer, you can associate ownership to responsibilities and
display a list of owned responsibilities. You can expand the list of responsibilities to display the
menus and functions attached to each responsibility. From the list of responsibilities, you can
see the number of people with access to each responsibility both within the organization
(within your HR security access environment) and outside of the organization (outside of your
HR security access environment). This provides additional security as you can review and
restrict the number of people outside of your organization with access to particular
responsibilities.
You can display the user ID and other information for each user with access to the
responsibility and if required, revoke access directly in the self-service page. If you choose to
revoke access to a responsibility, the affected user receives notification of the change.
Advanced Topics
Chapter 19 - Page 7
Additional Configuration Steps

Additional Configuration Steps
Before you use the Responsibility Ownership function, you must additionally configure:
• Create data security grants to link responsibilities to your users - data grants enable you
to control access to data in the data security system. When you create a data grant, you
grant access to a database object to a user. In the case of the Responsibility Ownership
function, you use data grants to grant responsibility ownership to a user.
• Create code to subscribe to the business event
oracle.apps.per.selfservice.respowner.revoke_access. This triggers the
fnd_user_resp_groups_api.update_assignment API to end date the responsibility
assignment.
Advanced Topics
Chapter 19 - Page 8
Quiz
Answer: a
Advanced Topics
Chapter 19 - Page 9
Quiz
Answer: a
Advanced Topics
Summary
Advanced Topics
Advanced Topics

D60563GC10 SG

Uploaded by

Document Information

Original Description:

Original Title

Copyright

Available Formats

Share this document

Share or Embed Document

Sharing Options

Did you find this document useful?

Is this content inappropriate?

Copyright:

Available Formats

D60563GC10 SG

Uploaded by

Copyright:

Available Formats

THESE eKIT MATERIALS ARE FOR YOUR USE IN THIS CLASSROOM ONLY.

COPYING eKIT MATERIALS FROM THIS COMPUTER IS STRICTLY PROHIBITED

Oracle University and Zinger Solutions Limited use only

Copyright © 2007, 2010 Oracle. All rights reserved.

Restricted Rights Notice

Oracle University and Zinger Solutions Limited use only

U.S. GOVERNMENT RIGHTS

Technical Contributors and Reviewers

This book was published using: Oracle Tutor

R12.x Oracle HRMS Self Service Fundamentals..........................................................................................1-1

Oracle University and Zinger Solutions Limited use only

Copyright © Oracle 2010. All rights reserved.

R12.x Oracle HRMS Self Service Fundamentals Table of Contents

Oracle University and Zinger Solutions Limited use only

Copyright © Oracle 2010. All rights reserved.

R12.x Oracle HRMS Self Service Fundamentals Table of Contents

Adding Custom Functions .............................................................................................................................11-11

Oracle University and Zinger Solutions Limited use only

Copyright © Oracle 2010. All rights reserved.

R12.x Oracle HRMS Self Service Fundamentals Table of Contents

Common SSHR Functions ..............................................................................................................................16-1

Oracle University and Zinger Solutions Limited use only

Copyright © Oracle 2010. All rights reserved.

R12.x Oracle HRMS Self Service Fundamentals Table of Contents

• Thorough knowledge of Oracle Applications

Oracle University and Zinger Solutions Limited use only

• Oracle Applications Foundations

How This Course Is Organized

Copyright © Oracle 2010. All rights reserved.

R12.x Oracle HRMS Self Service Fundamentals Table of Contents

Oracle University and Zinger Solutions Limited use only

• System release bulletins

• Installation and user’s guides

• International Oracle User’s Group (IOUG) articles

Copyright © Oracle 2010. All rights reserved.

R12.x Oracle HRMS Self Service Fundamentals Table of Contents

Oracle University and Zinger Solutions Limited use only

Copyright © Oracle 2010. All rights reserved.

R12.x Oracle HRMS Self Service Fundamentals Table of Contents

Typographic Conventions in Code

Passwords DROP USER scott

Oracle University and Zinger Solutions Limited use only

Lowercase Syntax variables CREATE ROLE role

Typographic Conventions in Oracle Application Navigation Paths

This simplified path translates to the following:

2. (M) From the menu, select Query then Find.

3. (B) Click the Approve button.

(ST) = Sub Tab

Copyright © Oracle 2010. All rights reserved.

R12.x Oracle HRMS Self Service Fundamentals Table of Contents

Typographical Conventions in Oracle Application Help System Paths

The following help navigation path, for example—

(Help) General Ledger > Journals > Enter Journals

—represents the following sequence of actions:

Oracle University and Zinger Solutions Limited use only

2. Under the General Ledger entry, expand Journals.

3. Under Journals, select Enter Journals.

Copyright © Oracle 2010. All rights reserved.

R12.x Oracle HRMS Self Service Fundamentals Table of Contents

R12.x Oracle HRMS Self Service Fundamentals

Copyright © Oracle, 2010. All rights reserved.

Oracle University and Zinger Solutions Limited use only