Oracler Self–Service Human Resources (SSHR 4.

2)
Implementation Guide Release 11i
May 2003

i

Oracle Self–Service Human Resources Implementation Guide, Release 11i Copyright E 1988, 2003, Oracle Corporation. All rights reserved. Copyright E 1996, 2002, 2003 Oracle Corporation. All rights reserved.

Major Contributors: Kathryn O’Donoghue, Mark Rowe, Alison Crabbe, Satishkumar Ramasamy, Bob Eagles. Contributors: Phil Snowball, Jo Turner.
The Programs (which include both the software and documentation) contain proprietary information of Oracle Corporation; they are provided under a license agreement containing restrictions on use and disclosure and are also protected by copyright, patent and other intellectual property law. Reverse engineering, disassembly or decompilation of the Programs, except to the extent required to obtain interoperability with other independently created software or as specified by law, is prohibited. Program Documentation is licensed for use solely to support the deployment of the Programs and not for any other purpose. The information contained in this document is subject to change without notice. If you find any problems in the documentation, please report them to us in writing. Oracle Corporation does not warrant that this document is error free. Except as may be expressly permitted in your license agreement for these Programs, no part of these Programs may be reproduced or transmitted in any form or by any means, electronic or mechanical, for any purpose, without the express written permission of Oracle Corporation. If the Programs are delivered to the US Government or anyone licensing or using the Programs on behalf of the US Government, the following notice is applicable: RESTRICTED RIGHTS NOTICE Programs delivered subject to the DOD FAR Supplement are ”commercial computer software” and use, duplication and disclosure of the Programs, including documentation, shall be subject to the licensing restrictions set forth in the applicable Oracle license agreement. Otherwise, Programs delivered subject to the Federal Acquisition Regulations are ”restricted computer software” and use, duplication, and disclosure of the Programs shall be subject to the restrictions in FAR 52.227–19, Commercial Computer Software – Restricted Rights (June, 1987). Oracle Corporation, 500 Oracle Parkway, Redwood City, CA 94065. The Programs are not intended for use in any nuclear, aviation, mass transit, medical, or other inherently dangerous applications. It shall be licensee’s responsibility to take all appropriate fail–safe, back up, redundancy and other measures to ensure the safe use of such applications if the Programs are used for such purposes, and Oracle disclaims liability for any damages caused by such use of the Programs. The Programs may provide links to Web sites and access to content, products, and services from third parties. Oracle is not responsible for the availability of, or any content provided on, third–party Web sites. You bear all risks associated with the use of such content. If you choose to purchase any products or services from a third party, the relationship is directly between you and the third party. Oracle is not responsible for: (a) the quality of third–party products or services; or (b) fulfilling any of the terms of the agreement with the third party, including delivery of products or services and warranty obligation related to purchased products or services. Oracle is not responsible for any loss or damage of any sort that you may incur from dealing with any third party. Oracle is a registered trademark and ConText, Enabling the Information Age, Oracle7, Oracle8, Oracle8i, Oracle Access, Oracle Application Object Library, Oracle HRMS, Oracle Discoverer, Oracle Web Customers, Oracle Web Employees, Oracle Workflow, Oracle Work in Progress, PL/SQL, Pro*C, SmartClient, SQL*, SQL*Forms, SQL*Loader, SQL*Menu, SQL*Net, SQL*Plus, and SQL*Reports are trademarks or registered trademarks of Oracle Corporation. Other names may be trademarks of their respective owners.

ii

OracleR Self–Service Human Resources (SSHR 4.2) Implementation Guide

Contents

Chapter 1

Overview of Self–Service Human Resources . . . . . . . . . . . . . . . Overview . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . What is SSHR 4.0? . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Key Concepts in Self–Service Human Resources (SSHR) . . . . . . . Definitions . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Self–Service Modules . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Summary of SSHR Modules . . . . . . . . . . . . . . . . . . . . . . . . . . . Absences . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Benefits . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Career and Performance Management . . . . . . . . . . . . . . . . . . Common Modules . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Compensation . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Manage Employee Events (MEE) . . . . . . . . . . . . . . . . . . . . . . . Organization Management . . . . . . . . . . . . . . . . . . . . . . . . . . . . Payroll . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Personal Information . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Professional Details . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Recruitment . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Training . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Views . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . SSHR Licences . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Predefined Self–Service Responsibilities and User Menus . . . . . User Menus . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Navigation Options for Functions . . . . . . . . . . . . . . . . . . . . . . Legislation–specific Menus . . . . . . . . . . . . . . . . . . . . . . . . . . . .

1–1 1–2 1–2 1–5 1–5 1–7 1–7 1–11 1–11 1–12 1–13 1–15 1–15 1–17 1–17 1–18 1–19 1–20 1–20 1–20 1–22 1–23 1–23 1–24 1–24

Contents

iii

Chapter 2

Getting Started with SSHR . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Overview . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Notes on Migrating from SSHR Version 3 . . . . . . . . . . . . . . . . Minimum Requirements for an SSHR System . . . . . . . . . . . . Running the HRMS Profile Options Report . . . . . . . . . . . . . . . . . .

2–1 2–2 2–2 2–3 2–5

Chapter 3

Understanding How SSHR Functions Work . . . . . . . . . . . . . . . . Understanding a Typical SSHR Function . . . . . . . . . . . . . . . . . . . . How an SSHR Function Works in SSHR 4.2 . . . . . . . . . . . . . . A Typical SSHR Web Page . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Managing Dates in SSHR . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Effective Dates . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Future–Dated Changes . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Save For Later . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

3–1 3–2 3–3 3–7 3–9 3–9 3–9 3–11

Chapter 4

Configuring SSHR . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Configuration Overview . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Guidelines for Configuring SSHR Functions . . . . . . . . . . . . . User Access . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Process Flows . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Approvals . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Page Layouts . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Module–specific Configuration Options . . . . . . . . . . . . . . . . .

4–1 4–2 4–2 4–2 4–3 4–3 4–3 4–4

Chapter 5

Managing User Access . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . User Access and Security . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Responsibilities . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . User Access to People . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Security Profiles . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . User Access to Functions . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Legislation–specific Functions . . . . . . . . . . . . . . . . . . . . . . . . . . Users and Responsibilities . . . . . . . . . . . . . . . . . . . . . . . . . . . . . User Access to Functions . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Self–Service Menus and User Access . . . . . . . . . . . . . . . . . . . . . . . . Types of Menus . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Menus for Employees (Non–Managers) . . . . . . . . . . . . . . . . . Menus for Managers . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Defining Menus for SSHR . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Defining User Access to Self–Service Functions . . . . . . . . . . .

5–1 5–2 5–2 5–2 5–3 5–5 5–7 5–7 5–8 5–9 5–9 5–10 5–11 5–12 5–13

iv

Oracle SSHR 4.2 Implementation Guide

Defining Functions for SSHR . . . . . . . . . . . . . . . . . . . . . . . . . . . 5–15 Batch Creation of User Accounts . . . . . . . . . . . . . . . . . . . . . . . . . . . 5–18 Features of the Create Batch Users Process . . . . . . . . . . . . . . . 5–18 Creating Batch User Accounts with Concurrent Programs . 5–20 User Account Employee Extract Process . . . . . . . . . . . . . . . . . 5–20 Data Pump Engine . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5–23 Employee Data Pump Exceptions Report . . . . . . . . . . . . . . . . 5–24 Writing User Hooks for the Batch Creation of User Accounts . . . . . . . 5–25 Tables Updated in the Batch Process . . . . . . . . . . . . . . . . . . . . 5–26

Chapter 6

Configuring Process Flows . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Self–Service Workflows . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Approvals Processes . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Workflow Objects and Item Types . . . . . . . . . . . . . . . . . . . . . . Workflow Access Levels: . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Configuring Workflow Objects . . . . . . . . . . . . . . . . . . . . . . . . . Copying Workflow Processes . . . . . . . . . . . . . . . . . . . . . . . . . . Configuring Workflow Attribute Values . . . . . . . . . . . . . . . . . Configuring Workflow Error Processes . . . . . . . . . . . . . . . . . . Defining Your Enterprise’s Email Addresses . . . . . . . . . . . . . Running the Workflow Cleanup Process . . . . . . . . . . . . . . . . . . . .

6–1 6–2 6–2 6–3 6–3 6–5 6–6 6–7 6–8 6–9 6–10

Chapter 7

Configuring Page Layouts . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . The Personalization Framework . . . . . . . . . . . . . . . . . . . . . . . . . . . Personalization Framework Hierarchy . . . . . . . . . . . . . . . . . . Configurable Profile Options . . . . . . . . . . . . . . . . . . . . . . . . . . Configuring Web Pages . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Configuring Flexfields . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Configuring Tabbed Regions . . . . . . . . . . . . . . . . . . . . . . . . . . . Adding Instructions to Web Pages . . . . . . . . . . . . . . . . . . . . . . Configuring the Global Button Bar . . . . . . . . . . . . . . . . . . . . . . Replacing the Default Oracle Logo . . . . . . . . . . . . . . . . . . . . . .

7–1 7–2 7–2 7–3 7–5 7–6 7–7 7–9 7–10 7–11

Chapter 8

Approvals . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Overview of Approvals . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Approvals Process . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Approvals Mechanisms in SSHR . . . . . . . . . . . . . . . . . . . . . . . Oracle Approvals Management (AME) . . . . . . . . . . . . . . . . . .

8–1 8–2 8–2 8–4 8–5

Contents

v

Default Use of OAM Configuration in SSHR . . . . . . . . . . . . . 8–5 Configuring SSHR Approval Levels in AME . . . . . . . . . . . . . 8–6 Dynamic Approvals . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 8–7 Menu and Function Names . . . . . . . . . . . . . . . . . . . . . . . . . . . . 8–7 Workflow . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 8–7 Configurable Tips and Instructions . . . . . . . . . . . . . . . . . . . . . 8–7 Configurable Flexfields . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 8–7 Configurable Profile Options . . . . . . . . . . . . . . . . . . . . . . . . . . 8–7 Configuring Approvals in the Workflow Builder . . . . . . . . . 8–8 Customizing Approvals Using PL/SQL . . . . . . . . . . . . . . . . . 8–9 Configuring SSHR Functions to Use Oracle Approvals Management (AME) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 8–11

Chapter 9

Common Modules . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Overview of Common SSHR Modules . . . . . . . . . . . . . . . . . . . . . . Person Tree . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Employees Tab . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Employee Actions Tab . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Multiple Assignments . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Transactions Across Business Groups . . . . . . . . . . . . . . . . . . . Menu and Function Names . . . . . . . . . . . . . . . . . . . . . . . . . . . . Workflow . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Configurable Tips and Instructions . . . . . . . . . . . . . . . . . . . . . Configurable Flexfields . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Configurable Profile Options . . . . . . . . . . . . . . . . . . . . . . . . . . Additional Configuration Steps . . . . . . . . . . . . . . . . . . . . . . . . Actions Page . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Menu and Function Names . . . . . . . . . . . . . . . . . . . . . . . . . . . . Workflow . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Configurable Tips and Instructions . . . . . . . . . . . . . . . . . . . . . Configurable FlexFields: . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Configurable Profile Options . . . . . . . . . . . . . . . . . . . . . . . . . . Multiple Assignments . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Menu and Function Names . . . . . . . . . . . . . . . . . . . . . . . . . . . . Workflow . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Configurable Tips and Instructions . . . . . . . . . . . . . . . . . . . . . Configurable FlexFields . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Configurable Profile Options . . . . . . . . . . . . . . . . . . . . . . . . . . Release Employee Information . . . . . . . . . . . . . . . . . . . . . . . . . Menu and Function Names . . . . . . . . . . . . . . . . . . . . . . . . . . . . Workflow . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

9–1 9–2 9–3 9–4 9–4 9–5 9–5 9–5 9–5 9–5 9–6 9–6 9–7 9–8 9–8 9–8 9–9 9–10 9–10 9–11 9–11 9–11 9–11 9–11 9–11 9–13 9–13 9–13

vi

Oracle SSHR 4.2 Implementation Guide

Configurable Tips and Instructions . . . . . . . . . . . . . . . . . . . . . 9–13 Configurable Flexfields . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 9–14 Configurable Profile Options . . . . . . . . . . . . . . . . . . . . . . . . . . 9–14 Additional Configuration Steps . . . . . . . . . . . . . . . . . . . . . . . . 9–14 Review and Confirm . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 9–15 Menu and Function Names . . . . . . . . . . . . . . . . . . . . . . . . . . . . 9–15 Workflow . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 9–15 Configurable Tips and Instructions . . . . . . . . . . . . . . . . . . . . . 9–17 Configurable Flexfields . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 9–17 Configurable Profile Options . . . . . . . . . . . . . . . . . . . . . . . . . . 9–17 New User Registration . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 9–18 Benefits Registration . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 9–18 Generic Users and Responsibilities . . . . . . . . . . . . . . . . . . . . . 9–19 Setting Up a Generic User ID For New User Registration . . 9–20 Setting Up Generic User IDs in Multiple Business Groups . 9–23 Configuring the New Employee and Non–Employee Registration Processes . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 9–26 Using Workflow Builder . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 9–28 Using the Personalization Framework . . . . . . . . . . . . . . . . . . . 9–28 Setting Up Life Events (Advanced Benefits only) . . . . . . . . . 9–29 Configuring the Create User Name Process . . . . . . . . . . . . . . 9–31 Generating Self–Service User Names and Passwords . . . . . . 9–34 New Employee Registration and Non–employee Registration . . . . . . 9–35 Menu and Function Names . . . . . . . . . . . . . . . . . . . . . . . . . . . . 9–35 Workflow . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 9–35 Configurable Tips and Instructions . . . . . . . . . . . . . . . . . . . . . 9–35 Configurable Flexfields . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 9–36 Configurable Profile Options . . . . . . . . . . . . . . . . . . . . . . . . . . 9–36 Create User Name . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 9–37 Menu and Function Names . . . . . . . . . . . . . . . . . . . . . . . . . . . . 9–37 Workflow . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 9–37 Configurable Tips and Instructions . . . . . . . . . . . . . . . . . . . . . 9–37 Configurable Flexfields . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 9–37 Configurable Profile Options . . . . . . . . . . . . . . . . . . . . . . . . . . 9–38

Chapter 10

Employee Demographics . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Personal Information Modules . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Menu and Function Names . . . . . . . . . . . . . . . . . . . . . . . . . . . . Workflow . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Configurable Tips and Instructions . . . . . . . . . . . . . . . . . . . . .

10–1 10–2 10–2 10–2 10–2

Contents

vii

Configurable Flexfields . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Configurable Profile Options . . . . . . . . . . . . . . . . . . . . . . . . . . Basic Details . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Menu and Function Names . . . . . . . . . . . . . . . . . . . . . . . . . . . . Workflow . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Configurable Tips and Instructions . . . . . . . . . . . . . . . . . . . . . Configurable Flexfields . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Configurable Profile Options . . . . . . . . . . . . . . . . . . . . . . . . . . Main Address . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Menu and Function Names . . . . . . . . . . . . . . . . . . . . . . . . . . . . Workflow . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Configurable Tips and Instructions . . . . . . . . . . . . . . . . . . . . . Configurable Flexfields . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Configurable Profile Options . . . . . . . . . . . . . . . . . . . . . . . . . . Secondary Address . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Menu and Function Names . . . . . . . . . . . . . . . . . . . . . . . . . . . . Workflow . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Configurable Tips and Instructions . . . . . . . . . . . . . . . . . . . . . Configurable Flexfields . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Configurable Profile Options . . . . . . . . . . . . . . . . . . . . . . . . . . Phone Numbers . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Menu and Function Names . . . . . . . . . . . . . . . . . . . . . . . . . . . . Workflow . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Configurable Tips and Instructions . . . . . . . . . . . . . . . . . . . . . Configurable Flexfields . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Configurable Profile Options . . . . . . . . . . . . . . . . . . . . . . . . . . Dependents and Beneficiaries . . . . . . . . . . . . . . . . . . . . . . . . . . Menu and Function Names . . . . . . . . . . . . . . . . . . . . . . . . . . . . Workflow . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Configurable Tips and Instructions . . . . . . . . . . . . . . . . . . . . . Configurable Flexfields . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Configurable Profile Options . . . . . . . . . . . . . . . . . . . . . . . . . . Emergency Contacts . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Menu and Function Names . . . . . . . . . . . . . . . . . . . . . . . . . . . . Workflow . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Configurable Tips and Instructions . . . . . . . . . . . . . . . . . . . . . Configurable Flexfields . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Configurable Profile Options . . . . . . . . . . . . . . . . . . . . . . . . . . Professional Details Modules . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Education and Qualifications . . . . . . . . . . . . . . . . . . . . . . . . . . Menu and Function Names . . . . . . . . . . . . . . . . . . . . . . . . . . . . Workflow . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

10–2 10–2 10–3 10–3 10–3 10–3 10–4 10–4 10–5 10–5 10–5 10–5 10–6 10–6 10–7 10–7 10–7 10–7 10–8 10–8 10–9 10–9 10–9 10–9 10–10 10–10 10–11 10–11 10–11 10–11 10–12 10–12 10–13 10–13 10–13 10–13 10–14 10–14 10–15 10–16 10–16 10–16

viii

Oracle SSHR 4.2 Implementation Guide

Configurable Tips and Instructions . . . . . . . . . . . . . . . . . . . . . Configurable Flexfields . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Configurable Profile Options . . . . . . . . . . . . . . . . . . . . . . . . . . Other Professional Awards . . . . . . . . . . . . . . . . . . . . . . . . . . . . Menu and Function Names . . . . . . . . . . . . . . . . . . . . . . . . . . . . Workflow . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Configurable Tips and Instructions . . . . . . . . . . . . . . . . . . . . . Configurable Flexfields . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Configurable Profile Options . . . . . . . . . . . . . . . . . . . . . . . . . . Competence Profile . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Menu and Function Names . . . . . . . . . . . . . . . . . . . . . . . . . . . . Workflow . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Configurable Tips and Instructions . . . . . . . . . . . . . . . . . . . . . Configurable Flexfields . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Configurable Profile Options . . . . . . . . . . . . . . . . . . . . . . . . . . Work Preferences . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Menu and Function Names . . . . . . . . . . . . . . . . . . . . . . . . . . . . Workflow . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Configurable Tips and Instructions . . . . . . . . . . . . . . . . . . . . . Configurable FlexFields . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Configurable Profile Options . . . . . . . . . . . . . . . . . . . . . . . . . . Resume . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Menu and Function Names . . . . . . . . . . . . . . . . . . . . . . . . . . . . Workflow . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Configurable Tips and Instructions . . . . . . . . . . . . . . . . . . . . . Configurable FlexFields . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Configurable Profile Options . . . . . . . . . . . . . . . . . . . . . . . . . . Tenure Status (US) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Menu and Function Names . . . . . . . . . . . . . . . . . . . . . . . . . . . . Workflow . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Configurable Tips and Instructions . . . . . . . . . . . . . . . . . . . . . Configurable Flexfields . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Configurable Profile Options . . . . . . . . . . . . . . . . . . . . . . . . . . Academic Rank (US) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Menu and Function Names . . . . . . . . . . . . . . . . . . . . . . . . . . . . Workflow . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Configurable Tips and Instructions . . . . . . . . . . . . . . . . . . . . . Configurable Flexfields . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Configurable Profile Options . . . . . . . . . . . . . . . . . . . . . . . . . .

10–17 10–18 10–18 10–19 10–19 10–19 10–19 10–20 10–20 10–21 10–22 10–22 10–22 10–23 10–23 10–24 10–24 10–24 10–24 10–24 10–24 10–25 10–25 10–25 10–25 10–25 10–25 10–26 10–26 10–26 10–26 10–27 10–27 10–28 10–28 10–28 10–28 10–28 10–29

Contents

ix

Chapter 11

Career and Performance Management . . . . . . . . . . . . . . . . . . . . . Events and Bookings . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Menu and Function Names . . . . . . . . . . . . . . . . . . . . . . . . . . . . Workflow . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Configurable Tips and Instructions . . . . . . . . . . . . . . . . . . . . . Configurable Flexfields . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Configurable Profile Options . . . . . . . . . . . . . . . . . . . . . . . . . . Employee Reviews . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Menu and Function Names . . . . . . . . . . . . . . . . . . . . . . . . . . . . Workflow . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Configurable Tips and Instructions . . . . . . . . . . . . . . . . . . . . . Configurable Flexfields . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Configurable Profile Options . . . . . . . . . . . . . . . . . . . . . . . . . .

11–1 11–2 11–2 11–2 11–2 11–3 11–3 11–4 11–4 11–4 11–4 11–4 11–4

Chapter 12

Manage Employee Events (MEE) . . . . . . . . . . . . . . . . . . . . . . . . . . MEE Modules and Workflow . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Chained MEE Processes . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Ordering MEE Workflow Processes . . . . . . . . . . . . . . . . . . . . . Assignment . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Assigning a Salary Basis . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Multiple Assignments . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Menu and Function Names . . . . . . . . . . . . . . . . . . . . . . . . . . . . Workflow . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Configurable Tips and Instructions . . . . . . . . . . . . . . . . . . . . . Configurable Flexfields . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Configurable Profile Options . . . . . . . . . . . . . . . . . . . . . . . . . . Termination . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Menu and Function Names . . . . . . . . . . . . . . . . . . . . . . . . . . . . Workflow . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Configurable Tips and Instructions . . . . . . . . . . . . . . . . . . . . . Configurable Flexfields . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Configurable Profile Options . . . . . . . . . . . . . . . . . . . . . . . . . . Work Schedule . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Menu and Function Names . . . . . . . . . . . . . . . . . . . . . . . . . . . . Workflow . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Configurable Tips and Instructions . . . . . . . . . . . . . . . . . . . . . Configurable FlexFields . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Configurable Profile Options . . . . . . . . . . . . . . . . . . . . . . . . . . Location . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Menu and Function Names . . . . . . . . . . . . . . . . . . . . . . . . . . . . Workflow . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

12–1 12–2 12–2 12–3 12–5 12–5 12–5 12–5 12–5 12–7 12–8 12–8 12–10 12–10 12–10 12–11 12–11 12–11 12–12 12–12 12–12 12–12 12–12 12–13 12–14 12–14 12–14

x

Oracle SSHR 4.2 Implementation Guide

. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Configurable FlexFields . . . . . . . . . . . . . . . . Configurable Tips and Instructions . Configurable Profile Options . . . . . . . . . Configurable Profile Options . . . . . . . . . . . . . . . . . . . . . Configurable FlexFields . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Configurable Tips and Instructions . . . . . . . . Workflow . . . . . . . . . . . Configurable Profile Options . . . . . . . . . . . . . Configurable Profile Options . . . . . . . . . . . . . . . Configurable Tips and Instructions . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Configurable FlexFields . . . . . . . . . . . . . . . . . . . . . . Menu and Function Names . . . . . . . . . . . . . . . . . . . . . . . . . . Other Employment Information . . . . . . Menu and Function Names . . . . . . . . . . . . . . . . . . . . . . . Configurable FlexFields . . . . . . . Workflow . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Pay Rate . . . . . . . . . . . . . . Extra Information Types (EITs) . . . . . . . . . . . . . . . . . . . Change Manager . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Configurable FlexFields . Menu and Function Names . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Individual Compensation Distributions (ICD) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 12–15 12–15 12–16 12–17 12–17 12–17 12–17 12–18 12–18 12–19 12–20 12–20 12–20 12–20 12–21 12–21 12–21 12–23 12–23 12–23 12–23 12–23 12–23 12–24 12–24 12–24 12–24 12–24 12–26 12–26 12–26 12–27 12–27 12–27 12–28 12–28 12–28 12–28 12–29 12–29 Contents xi . . . . . . . . . . . Configurable Tips and Instructions . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Menu and Function Names . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Special Information Types (SITs) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Configurable FlexFields . . . . . . . . . . . . . . . . . . . . . . . . . Menu and Function Names . . . . . . . . Workflow . . . . . . . . Additional Configuration Steps: . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Workflow . . . . . . . . . . . . . . . . . . . . . . . Workflow . . . . . . . . . . . . . . . . . . .Configurable Tips and Instructions . . . . . . . . . . . . . . Configurable Tips and Instructions . . . . . . . . . . . . Menu and Function Names . . . . . . Workflow . . . . . . . . . . . . . . . . . . . . . . . Configurable Tips and Instructions . . . Configurable Profile Options . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Configurable Profile Options . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Configurable FlexFields . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Additional Configuration Steps . . . . .

. . . . . . . . . . . . . . Menu and Function Names . . . . . . . . . . . . . . . . . . . . . Workflow . . . . . . . Workflow . . . 14–1 14–2 14–2 14–2 14–3 14–3 14–4 14–4 Chapter 15 Absence Management . . . . . . . . . . . Configurable Profile Options . . . . . Menu and Function Names . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . New Hire and Applicant Hire Processes . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Organization Manager . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Workflow . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Configurable FlexFields . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .Chapter 13 Recruitment . . . 16–1 16–2 16–3 16–3 16–3 16–3 16–4 16–4 16–5 16–5 16–5 16–5 xii Oracle SSHR 4. . . . . . . . . . . . . . . . . . . . . . . . . Applicant Search . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Configurable Tips and Instructions . . . . . . . . . . . . . . . . . . . . Configurable Profile Options . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Configurable Tips and Instructions . . . . . Workflow . . . . . . . . . . 13–1 13–2 13–3 13–3 13–3 13–4 13–4 13–4 13–5 Chapter 14 Organization Management . . . . . . . . . . . . . . . . . . . . . . Configurable Tips and Instructions . Configurable FlexFields . Assignment Details View . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Menu and Function Names . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Configurable Tips and Instructions . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Overview . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Configurable Tips and Instructions . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Duplicate Person Checking . . . . . . . . . . Configurable Profile Options . . . . . . . . . . . . Menu and Function Names . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Configurable Profile Options . . . . . . . . . Configurable FlexFields . . . Workflow . . Configurable FlexFields . . . . . . . . . . . . . . . . . . . Additional Configuration Steps . . . . . 15–1 15–2 15–2 15–2 15–2 15–3 15–4 Chapter 16 Views . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Menu and Function Names . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .2 Implementation Guide . . . . . . . . . . . . . . . . . . Absences . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Employee Information View . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Compensation Activity View . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 17–28 Removing the Benefits Enrollment Overview Web Page (Standard Benefits) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 17–10 Configurable FlexFields . . . . . . . . . . . . . . . . . . . . . . 17–22 Enabling Self–Service Benefits Enrollment Notifications . Configurable Profile Options . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 17–12 Configurable FlexFields . . . . . . . . . . . . . . 17–10 Menu and Function Names . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 17–3 Hidden Fields in Self–Service Benefits . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Menu and Function Names . . . . . . . . . . . . . . 17–10 Configurable Pages and Shared Regions . . . . . . . Workflow . . Configurable Profile Options . . . . . . . . . . . . . . . . . . . . . . . . . . . . Configurable Tips and Instructions .Configurable FlexFields . . . . . . . . . . . . . . . . . . . . . . . Configurable Tips and Instructions . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Workflow . . 17–3 Displaying Descriptive Flexfields . . . . Termination History View . . . . Configurable Profile Options . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Menu and Function Names . . . . . . . . . . . . . . . . . . . . Search Functions for HR Views . . . . . . . . . . . . Configurable FlexFields . . . . . . . . . . . . . . . . . . . . . . . . . 17–1 Self–Service Benefit Enrollments . . . . . 17–24 Setting Up User Access to Self–Service Benefits . . . . . . . . . . . . . . . . . . 16–5 16–6 16–7 16–7 16–7 16–7 16–7 16–8 16–9 16–9 16–9 16–9 16–9 16–10 16–11 16–11 16–11 16–11 16–11 16–12 Chapter 17 Benefits . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Configurable FlexFields . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 17–30 Defining Self–Service Instruction Text . . . . . . . . . . . . . . 17–19 Setting Up Self–Service Benefits Enrollments . . . . . . . . . Menu and Function Names . . . . . . . . . . . . . . . . . . . . 17–31 Contents xiii . . . . . . . . 17–4 Plan Design Considerations for Self–Service Benefits . . . . . . . . 17–5 Benefits Enrollments . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 17–25 Setting the Effective Date of a Scheduled Enrollment in Self–Service Benefits . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 17–2 Self–Service Benefits Enrollment Functionality . . . . . . . . . . . 17–2 Enrollment Change Workflow Notifications . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Configurable Profile Options . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Workflow . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Configurable FlexFields . . . . . . . . . . . . . . . . . . . . . . . . . . . Configurable Tips and Instructions . . . . . . . . . . . . . . . .

. . . . . . . . . 18–6 Change in Family Status . . . . . . 18–3 Enrollment Management . . . . . . . . . . . . . 18–25 Running the Populate FEHB Program and Design Plan Process .US Federal . . . . . . . . . . . . . . . . . . . 18–32 Defining Additional Enrollment Action Types (Advanced Benefits) . . . 18–39 xiv Oracle SSHR 4. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .Defining Additional Enrollment Action Types (Advanced Benefits) . . . . . . . . . . . . . . . . . . . . . . 18–21 Enabling Self–Service Benefits Enrollment Notifications . . . 18–28 Compiling FEHB Fast Formulas . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 18–3 Manual Changes . . . . . . . . . . . . . . . . 18–31 Defining Self–Service Instruction Text . . . . . . . . . . . . . . . . . . . . .2 Implementation Guide . . . . . . . . . . . . . . . 18–18 Setting Up User Access to Self–Service Benefits . 18–3 Plan Eligibility . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 18–2 Administering FEHB . 17–37 Setting up an XML–Enabled Primary Care Provider Search 17–37 Setting Up a Primary Care Provider Search without XML Formatting . . . . . . . . . . . . . . . . . 18–6 Pre–Tax and After–Tax Plan Options . . . . . . 18–9 Menu and Function Names . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 18–38 Setting up an XML–Enabled Primary Care Provider Search 18–38 Setting Up a Primary Care Provider Search without XML Formatting . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 18–35 Configuring the Primary Care Provider Search Facility . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 18–7 Retroactive Actions . . . . . . . . 18–8 Cancellations and Corrections . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 18–9 Configurable FlexFields . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 18–34 Maintaining Primary Care Providers for a Plan . 17–38 Chapter 18 Benefits . . . . . . . . . . . . . . . . . . 17–34 Configuring the Primary Care Provider Search Facility . . . . . . . . . . . . . . . . . . . 18–27 Setting up FEHB . . . 18–24 Setting the Effective Date of a Scheduled Enrollment in Self–Service Benefits . . . . . . . . . . . . . . . . . . . 18–5 Effective Dates Life Event Occurred On Date . . . . . . . 18–29 FYI Notifications for FEHB . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 18–8 Benefits Enrollments . . . . . . . . . . . . . . . . . . . 18–9 Configurable Pages and Shared Regions . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 18–1 Federal Employee Health Benefits Overview . 18–30 Removing the Benefits Enrollment Overview Web Page (Standard Benefits) . . . . . . 17–33 Maintaining Primary Care Providers for a Plan . . . 18–11 Configurable FlexFields . . .

. . . . . . . . . 19–2 Chapter 20 Payroll . . . Additional Configuration Options . . . . . . . . . Configurable Profile Options . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Workflow . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Online Payslip (Canada) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Online Payslip (US) . . . . . . . . . . . . . . Additional Configuration Options . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 20–1 20–2 20–3 20–3 20–4 20–5 20–8 20–10 20–10 20–10 20–10 20–11 20–11 20–11 20–11 20–12 20–12 20–12 20–12 20–12 20–12 20–13 20–14 20–14 20–14 20–14 20–14 20–14 20–15 20–16 20–16 20–16 20–16 20–16 20–16 20–17 Contents xv . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Configurable Tips and Instructions . . . . . . . . . . . . . . . . . . . . . . . . . . Configurable FlexFields . . . . . . . . . . . Online Payslip (Generic) . . . . . Overview of Payroll Functions . . . . Configurable Tips and Instructions . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Payment Methods . . . . . . . . . Menu and Function Names . . . Configurable FlexFields . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Online Payslip (UK) . 19–1 Self–Service Individual Compensation Distributions (ICD) . . . . . . . . . . . . . . . . . . . . . . . . . . Configurable Profile Options . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Configurable Profile Options . . . . . . . . . . . . . . . . . . . . . . Configurable Tips and Instructions . . . Configurable FlexFields . . . . . . . . . . . . . . . . . . . . . . . . . Additional Configuration Steps: . . . . . . . . . . . . . Workflow . . . . . . . . . . . . . . . . . . . . . . . . . Additional Configuration Options . . . . . Menu and Function Names . . . . . . . . . 19–2 Setting Up Individual Compensation Distribution Plans for Self– Service Human Resources . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Menu and Function Names . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Workflow . . . . Configurable Profile Options . . . Configurable Tips and Instructions . Workflow . . . . . . . . . . . . . . . . Menu and Function Names . . . . . . . . . . . . . . . . . . . . . . . . . . . Configurable Definitions for Web Applications Dictionary: Configurable Profile Options . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Configurable FlexFields . . . . . . . . . . . . . . . . . . . . . . . . . . . .Chapter 19 Individual Compensation Distributions . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Workflow . . . . Menu and Function Names . . Viewing Online Payslips in Oracle HRMS . .

. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 20–21 Configurable FlexFields . . . . . . . . . . . . . . . . . . . . . . 20–24 Configurable FlexFields . . . . . . . . . . . . . . . . . . . . . . . . 20–27 Menu and Function Names . . . . . . . . . . . . . . . . . . . 20–24 Configurable Tips and Instructions . . . . . . . 20–28 Additional Configuration Steps: . .2 Implementation Guide . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . External Training (Self–Service) . . . . . . . . Korea. . . . . . . . . . . . . . . . 21–1 21–2 21–2 21–2 21–3 21–3 21–4 21–5 21–5 21–5 21–6 xvi Oracle SSHR 4. . . . . . . . . . . 20–19 Workflow . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Hong Kong. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 20–19 Configurable Tips and Instructions . . 20–28 Configurable Profile Options . . . . . . . . . . . . . . . . Menu and Function Names . . . . . . . . . . 20–21 Configurable Tips and Instructions . . Configurable Profile Options . . . . . . . . . . . 20–25 Configurable Profile Options . . . . . . . . . . . 20–22 Tax Withholdings Form (W–4) (US) . . . . . . . 20–30 Chapter 21 Training . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Workflow . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Configurable Tips and Instructions . . . . . . . . . Singapore. . . . . . . . . . . . . . . . . . . . 20–21 Menu and Function Names . . . . . . . . . . . . . . . . . . . . . . . .Online Payslip (Australia. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 20–19 Additional Configuration Options . . . . . . . . . . . . . . . . . . . . . . . . . . 20–25 Tax Information Form (W–2) (US) . . . . 20–21 Workflow . . 20–22 Additional Configuration Options . . Training (Self–Service) . . . . . . . . 20–19 Configurable FlexFields . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 20–27 Configurable Tips and Instructions . . . . . . . . . . . . . . 20–24 Workflow . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Workflow . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 20–27 Workflow . . . . . . 20–20 Online Payslip (South Africa) . . . . . Menu and Function Names . . . . . . . . . 20–24 Menu and Function Names . . . . . . . . . . 20–29 Voluntary Deductions . . . . . . . . . . . 20–19 Configurable Profile Options . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Configurable Flexfields . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 20–28 Configurable FlexFields . . . . . . . . . . . . . . . . . . . 20–22 Configurable Profile Options . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 20–19 Menu and Function Names . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Configurable Tips and Instructions . . . . . . . . . . . . . . . . . New Zealand) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

. 22–8 Budget and Worksheet Rounding . 22–7 Configurable Profile Options . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 22–9 Budget and Allocation Matrix . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 22–6 Does Compensation Workbench handle approving allocations. . . . . . . . . . . . . . . . . . . . . . . . . . 22–7 Menu and Function Names . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Configurable Profile Options . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 22–6 Can I Budget and Allocate Compensation Based on Salary Components? . . . . . . . . . . . . . 22–7 Configurable Tips and Instructions . . . . . . . . . . . . . . . . 22–5 Can other managers fill in for me if I am unavailable? . . . . . . . . . . . . . . . 22–7 Configurable FlexFields . . 22–2 Worksheets . . . . . 22–6 Can managers promote and rate or assess employees at the same time as allocating salaries? .Configurable Flexfields . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 22–12 Compensation Workbench Promotions . . . . . . . . . . . . . . . . . . . . . 22–14 Contents xvii . . . . . . . . . . . . . . . . . . . . . . . . . promotions. . . . . . . . . 22–7 Workflow . 22–9 Compensation Workbench Allocations . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Configurable Tips and Instructions . . . . . . . Menu and Function Names . . . . . . . . . . . . . . . . . 22–5 Can managers view employee details from Compensation Workbench? . . . . . . . . . . . . . . . . . . . . . . . . . . . 22–8 Budget Issuance . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Configurable Profile Options . . . . . . . . . . . . . . . . . 22–2 Approvals . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 22–11 Compensation Workbench Itemization . . . . . . . . . . . . . . . . . . . . . . . . 22–5 How are budgets prepared? . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 22–1 Compensation Workbench Overview . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 22–5 Can managers assign employees to their own worksheets? . . . . . . . . . . . . . . . . . . . . . . . 22–13 Processing the Promotion . . . . . . . . . . . . . . . . . . . 22–2 Budgets . . . . . . . . . . 21–6 21–6 21–7 21–7 21–8 21–9 21–10 21–10 Chapter 22 Compensation Workbench . . . . . . . . . . . . . . . . . . . . . . . Configurable FlexFields . . . . . . . . . . . . . . . . . . . . . . . . . Workflow . . . . . . . . . . . . . . 22–3 Copying the Seeded Menu . . . . 22–7 Compensation Workbench Budget Preparation . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 22–4 Compensation Workbench . . . . . . . . . and employee performance ranking? . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 22–6 Compensation Workbench . . . . . . . . . . . . . . . . . . . . . . . . External Linking (Self–Service Training) . . . . . . . . . 22–5 How are compensation allocations awarded? . . . . . . . .

. . . . . . . . . . . . . . . . . . . . . . . 22–56 Running the Compensation Workbench Back–out Life Events Process . . . 22–18 View and Update Employee Eligibility . . . . . . . . 22–29 Reporting in Compensation Workbench . . 22–21 Compensation Workbench Approvals and Notifications . . . . . . . . . . . . . . . 22–29 Budget Status . A – 2 xviii Oracle SSHR 4. . 22–29 Worksheet Status . . . . . . . . . . 22–59 Running the Compensation Workbench Progress Report . . . . . . . . . . 22–43 Defining a Reporting Group . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 22–57 Running the Compensation Workbench Close Enrollment Process . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 22–41 Defining Enrollment Requirements for Compensation Workbench Plans . . . . . 22–50 Using the Person Life Events Window for Compensation Workbench . . . . . . . . . . . . . . . 22–39 Defining a Compensation Workbench Plan . . . . . . . . . . . . . . . . . . . . 22–54 Updating Amounts for an Employee . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .2 Implementation Guide . 22–30 Setting Up Compensation Workbench Plans . . . . . . 22–14 Modifying an Existing Plan . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 22–48 Running the Participation Process: Compensation . . . 22–30 Total Compensation Progress Report . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 22–62 Appendix A Implementation Steps . . . . . . . . 22–16 Employee Eligibility for Compensation Workbench . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 22–22 Standard Activity Rates for Compensation Workbench . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 22–23 Compensation Workbench Statuses . . . . . . . . . . . . . . . . . . . 22–54 Moving an Employee to Another Manager’s Workbench . . . A – 1 Implementation Steps for Self–Service HR (SSHR) . . . . . . . . . . . . . . . . 22–21 Switch Manager Search Page . . . . . . . . . . 22–18 Employee Reassignment for Compensation Workbench . . . 22–19 Reassigning an Employee . . 22–32 Personalizing a Plan for Compensation Workbench . . . . . . . . . . . . . . . . 22–19 Switch Manager . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 22–61 Running the Eligibility and Enrollment List Report . . . . . . 22–29 Budget/Worksheet Access . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .Compensation Plan Design . . . . . . . . . . . . . . . . . . . . . 22–55 Running the Compensation Workbench Post Process . . 22–14 Compensation Workbench Employee Performance Rating . . 22–47 Compensation Workbench Processing . 22–23 Standard Rate Activity Types . . . . . . . . . . . . . . . . . . . . . . . 22–53 Updating an Employee’s Eligibility . . . . . . . . . . 22–52 Issuing a Budget to a High Level Manager . . . . . . . . .

. . . . . . C – 10 Transfer V4. . . . . . . . . . . . . . . . . . . . . . . C – 4 Change Cost Center V4.0 (HR_NEWHIRE_SS) . C – 2 Change Job V4. . . . . . . . . . . . .To Prepare the Environment for SSHR: . C–9 Employee Terms of Employment Change 4. . C – 13 New Hire V4. . . . . . . . . . . . . . . . . . . . . . . Configuring Workflow Processes and Page Layouts (SSHR) Implementation Flowcharts (SSHR 4. . . . . . . . . B – 2 Using the After User Hook . . . . . . . . . . . . . . . . . .0 (HR_EMP_TERMS_CHG_SS) . . . . . . .0 (HR_CHANGE_JOB_TERMS_SS) . . . . . . . . . . . . . B – 3 Appendix C Function–level Personalizations .2) . . . . . . . . . . . .0 (HR_TERMINATION_SS) . . . . C – 13 Termination V4. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .0 (HR_TERMINATION_COMP_SS) . . . . . . . . . . . . . . . . . C – 11 Termination with Compensation V4. . . . . . . . . C – 2 Change Job and Employment Terms V4. . . . . . . . . . . User Access and Workflow Set Up (SSHR) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .0 (HR_CHG_COST_TRM_LOC_SUP_SS) . . . . . . . . C – 1 Function–level Personalizations . B – 1 User Hooks To Generate User Names For New User Registration . . . . . . . . . . . . . . . .0 (HR_EMP_STATUS_CHG_SS) . . . . . . . . . . . . . . .0 (HR_CHANGE_JOB_SS) .0 (HR_TRANSFER_SS) . . . . . . . . . . . . . . . . . . . .0 (HR_CHG_COST_LOC_SUP_SS) C – 5 Change Cost Center and Employment Terms V4. . . . . . . . . . . . . . . . . . . . . . . . A–2 A–3 A–5 A–8 Appendix B User Hook for New User Registration . . . . . . . . C – 7 Employee Status Change V4. C – 13 Index Contents xix . . . . . . . . . . . . . . . B–2 Using the Before User Hook .

2 Implementation Guide .xx Oracle SSHR 4.

Preface Preface xxi .

we suggest you attend one of the training classes available through Oracle University. Chapter 3 illustrates how a typical SSHR function works using the Personal Information functions as an example.Audience for This Guide This Implementation Guide has been written to help implementation teams set up and configure Oracle SSHR.2 Implementation Guide . xxii Oracle SSHR 4. Chapter 7 looks at configuring page layouts using the OA Personalization Framework. • • • Chapter 1 introduces SSHR and its features Chapter 2 outlines the minimum steps you need to carry out to be able to run SSHR in a test environment. OracleR HRMS Oracle Workflow Oracle Self–Service Web Applications Oracle HRMS System Administration Oracle HRMS Applications If you have not yet been introduced to these applications. Chapter 5 looks at user access and security. This guide assumes you have a working knowledge of the following: • • • • • • The principles and customary practices of your business area. • • • • Chapter 4 introduces the configuration tools used to configure SSHR and provides a generic configuration procedure. How To Use This Guide This guide contains the information you need to understand and use Oracle SSHR. Chapter 6 looks at configuring process flows using the Workflow Builder. The next five chapters explain the tools and general techniques you use to configure SSHR. See Other Information Sources for more information about Oracle Applications product information.

Chapter 11 covers Career and Performance Management. our documentation includes features that make information available to users of assistive technology. Chapter 22 covers the Compensation Workbench.• Chapter 8 looks at configuring approvals using the Workflow Builder. Chapter 14 covers Organization Management. Appendix B gives a sample user hook for generating the user names for New User Registration. Chapter 16 covers Views. The remaining chapters cover in detail the specific configuration options available in each functional area. Chapter 17 covers Benefits. and Oracle Approvals Management. Appendix C provides a list of function–level personalizations. To that end. Conventions Documentation Accessibility Our goal is to make Oracle products. Chapter 15 covers Absences. PL/SQL. • • • Appendix A is a checklist of the implementation and configuration steps for SSHR. Standards will continue to Preface xxiii . and supporting documentation accessible. Chapter 10 covers Employee Demographics. Chapter 20 covers Payroll. to the disabled community. and contains markup to facilitate access by the disabled community. Chapter 12 covers Manage Employee Events (MEE). • • • • • • • • • • • • • • Chapter 9 covers common SSHR functionality. Chapter 21 covers Training. This documentation is available in HTML format. with good usability. Chapter 13 covers Recruitment. services. Chapter 18 covers US Federal Benefits Chapter 19 covers Individual Compensation Distributions (ICD).

Online help patches are available on Metalink. Other Information Sources You can choose from many sources of information. Online Documentation All Oracle Applications documentation is available online (HTML and PDF).evolve over time. a Windows screen reader. training.2 Implementation Guide .com/accessibility/. JAWS may not always read a line of text that consists solely of a bracket or brace. Accessibility of Links to External Web Sites in Documentation This documentation may contain links to web sites of other companies or organizations that Oracle Corporation does not own or control. however. • Online Help – The new features section in the HTML help describes new features in 11i. The conventions for writing code require that closing braces should appear on an otherwise empty line. 11i Features Matrix – This document lists new features available by patch and identifies any associated new documentation. Oracle Corporation neither evaluates nor makes any representations regarding the accessibility of these web sites. For example. use only the Release 11i versions of those guides. The new features matrix document is available on Metalink. to increase your knowledge and understanding of OracleR HRMS. • xxiv Oracle SSHR 4. The new features section also includes information about any features that were not yet available when this guide was printed. and support services. For additional information.oracle. Accessibility of Code Examples in Documentation JAWS. This information is updated for each new release of Oracle HRMS. and Oracle Corporation is actively engaged with other market–leading technology vendors to address technical obstacles so that our documentation can be accessible to all of our customers. including online documentation. if your administrator has installed software from a mini–pack as an upgrade. If this guide refers you to other Oracle Applications documentation. may not always correctly read the code examples in this document. this document describes the new features. visit the Oracle Accessibility Program web site at http://www.

It describes the Oracle Application Object Library components needed to implement the Oracle Applications user interface described in the Oracle Applications User Interface Standards for Forms–Based Products. You can access this user’s guide online by choosing ”Getting started with Oracle Applications” from any Oracle Applications help file. Therefore. by reading from the Oracle Applications Document Library CD included in your media pack. as well as running and reviewing reports and concurrent processes.com.oracle. and navigate using the graphical user interface (GUI) available with this release of Oracle HRMS (and any other Oracle Applications products).• Readme File– Refer to the readme file for patches that you have installed to learn about new documentation or documentation patches that you can download. If you require printed guides. query. Oracle Applications Developer’s Guide This guide contains the coding standards followed by the Oracle Applications development staff. Guides Related to All Products Oracle Applications User’s Guide This guide explains how to enter data. or by using a Web browser with a URL that your system administrator provides. You can read the guides online by choosing Library from the expandable menu on your HTML help window. you can purchase them from the Oracle store at http://oraclestore. Oracle Alert User’s Guide This guide explains how to define periodic and event alerts to monitor the status of your Oracle Applications data. This guide also includes information on setting user profiles. you may want to refer to other user guides when you set up and use OracleR HRMS. run reports. Related User’s Guides OracleR HRMS shares business and setup information with other Oracle Applications products. It also provides information Preface xxv .

and other processes. Running Your Payroll Using Oracle HRMS This user guide provides information about wage attachments. and also how to manage your costs. recording details about jobs and positions within your enterprise. and also defining and managing budgets. the payroll run. This includes how to represent your workforce on your application.2 Implementation Guide . You also use this guide to complete the setup steps necessary for any Oracle Applications product that includes workflow–enabled processes.6 Framework technologies. Oracle Workflow Guide This guide explains how to define new workflow business processes as well as customize existing Oracle Applications–embedded workflow processes. Managing Your Workforce Using Oracle HRMS Use this guide to learn about all aspects of managing your workforce. It describes the UI for the Oracle Applications products and how to apply this UI to the design of an application built by using Oracle Forms. Oracle Applications User Interface Standards for Forms–Based Products This guide contains the user interface (UI) standards followed by the Oracle Applications development staff. This includes setting up your organization hierarchy. xxvi Oracle SSHR 4. recruiting new employees and developing their careers. taxes and social insurance. Guides Related to This Product OA Personalization Framework and OA Extensibility Framework Use this guide to learn about the capabilities of the 5.to help you build your custom Oracle Forms Developer 6i forms so that they integrate with Oracle Applications. defining a payroll. Using Oracle HRMS – The Fundamentals Use this guide to learn about representing your enterprise on your application.

auditing. and letter generation.Managing Total Compensation Using Oracle HRMS Use this guide to learn about setting up the application to store and process information on your total compensation package. Using Oracle Training Administration (OTA) This guide provides information about how to set up and use Oracle Training Administration to facilitate your training and certification business. deductions. Using Application Data Exchange This guide provides information about using Application Data Exchange to view HRMS data with desktop tools. other earnings. Implementing Oracle Self–Service Human Resources (SSHR) This guide provides information about setting up the self–service human resources management functions for managers and employees. including salary administration. Implementing Oracle HRMS This guide explains the setup procedures you need to carry out in order to successfully implement Oracle HRMS in your enterprise. Oracle Self–service Web Applications This guide provides information on self–service applications in general. managing security. benefits. information access. Preface xxvii . and upload revised data to your application. Managers and employees can then use an intranet and Web browser to have easy and intuitive access to personal information and career management functionality. absence management and PTO accrual plans. Reporting and System Administration in Oracle HRMS This guide provides information about extending and configuring Oracle HRMS. Configuring.

7 or Release 11. In Release 11i. Using Oracle Time Management This guide provides information about capturing work patterns such as shift hours so that this information can be used by other applications such as General Ledger. and the Oracle8i Server technology stack by automating many of the required steps. technology stack. and Self–Service Web Applications. architecture. BIS User Guide 11i This guide is provided as online help only from the BIS application and includes information about intelligence reports. Installation and System Administration Oracle Applications Concepts This guide provides an introduction to the concepts. It provides a useful first book to read before an installation of Oracle Applications. features. languages and character sets. and terminology for Oracle Applications Release 11i.Oracle Business Intelligence System Implementation Guide This guide provides information about implementing Oracle Business Intelligence (BIS) in your environment. This guide contains instructions for using Oracle Rapid Install and lists the tasks you need to perform to finish your installation. Upgrading Oracle Applications Refer to this guide if you are upgrading your Oracle Applications Release 10. This guide describes the upgrade process and lists database and product–specific xxviii Oracle SSHR 4. Installing Oracle Applications This guide provides instructions for managing the installation of Oracle Applications products. You should use this guide in conjunction with individual product user’s guides and implementation guides. Discoverer workbooks. and the Performance Management Framework. This guide also introduces the concepts behind Applications–wide features such as Business Intelligence (BIS).2 Implementation Guide . which minimizes the time to install Oracle Applications and the Oracle8 technology stack. much of the installation process is handled using Oracle Rapid Install.0 products to Release 11i.

use this manual before implementing Oracle HRMS.7. You cannot upgrade to Release 11i directly from releases prior to 10. AD Controller. screenshots. to upgrade to Release 11i. It provides a history of the changes to individual Oracle Applications products between Release 11. and seed data for this interval.upgrade tasks. Other Implementation Documentation Oracle Applications Product Update Notes Use this guide as a reference for upgrading an installation of Oracle Applications. It includes new features. enhancements. profile options. This manual details additional steps and setup considerations for implementing Oracle HRMS with this feature. and other information that you need to run the AD utilities. You must be either at Release 10. It contains information on how to define security. It contains how–to steps. Oracle Applications System Administrator’s Guide This guide provides planning and reference information for the Oracle Applications System Administrator. such as AutoUpgrade.7 (NCA.0 and Release 11i.0. Maintaining Oracle Applications Use this guide to help you run the various AD utilities. this guide describes all you need to know about setting up and using Oracle HRMS with this feature. SmartClient. AD Relink. License Manager. customize menus and online help. and manage concurrent processing. Multiple Reporting Currencies in Oracle Applications If you use the Multiple Reporting Currencies feature to record transactions in more than one currency. and changes made to database objects. or character mode) or Release 11. AutoPatch. and others. Preface xxix . This guide also provides information on maintaining the applications file system and database. AD Administration. Multiple Organizations in Oracle Applications If you use the Oracle Applications Multiple Organization Support feature to use multiple sets of books for one Oracle HRMS installation.

This documentation includes open interfaces found in Oracle Manufacturing. This manual also provides information on creating custom reports on flexfields data. Oracle Technical Reference Manuals The technical reference guides are now available in electronic format only. Using Oracle FastFormula This guide provides information about writing. and reference information for the OracleR HRMS implementation team. Using Oracle SSP/SMP This guide provides information about setting up and using Oracle SSP/SMP to meet your statutory sick pay and statutory maternity pay obligations. Oracle Manufacturing and Distribution Open Interfaces Manual This manual contains up–to–date information about integrating with other Oracle Manufacturing applications and with your other systems. Oracle FastFormula provides a simple way to write formulas using English words and basic mathematical functions. You can now access technical reference manuals for any Oracle Applications product you have licensed. Oracle FastFormula enables you to specify elements in payroll runs or create rules for PTO and accrual plans. This manual is available in HTML format on the documentation CD–ROM for Release 11i.Oracle Applications Flexfields Guide This guide provides flexfields planning. Oracle Applications Message Reference Manual This manual describes all Oracle Applications messages. For example. editing. xxx Oracle SSHR 4. setup.2 Implementation Guide . and using formulas to configure your system. as well as for users responsible for the ongoing maintenance of Oracle Applications product data.

Do Not Use Database Tools to Modify Oracle Applications Data Oracle STRONGLY RECOMMENDS that you never use SQL*Plus. Oracle University’s online education utility. you can arrange for our trainers to teach at your facility. any change you make using an Oracle Applications form can update many tables at once. terminology. or any other tool to modify Oracle Applications data unless otherwise instructed. database triggers. Oracle Training professionals can tailor standard courses or develop custom courses to meet your needs. Support From on–site support to central support. managing an Oracle8i server. For example. and maintain information in an Oracle database. But if you use Oracle tools such as SQL*Plus to modify Oracle Applications data. store. retrieve. In addition. These courses are organized into functional learning paths. you risk destroying the integrity of your data and you lose the ability to audit changes to your data. and data as examples in a customized training session delivered at your own facility. our team of experienced professionals provides the help and information you need to keep OracleR HRMS working for you. Because Oracle Applications tables are interrelated. Oracle Data Browser. You have a choice of educational environments. You can attend courses offered by Oracle University at any one of our many Education Centers. But when you modify Oracle Applications data using anything Preface xxxi . and Oracle’s large staff of consultants and support specialists with expertise in your business area. Account Manager. Oracle provides powerful tools you can use to create. or you can use Oracle Learning Network. so you take only those courses appropriate to your job or area of responsibility. and your hardware and software environment.Training and Support Training Oracle offers a complete set of training courses to help you and your staff master Oracle HRMS and reach full productivity quickly. This team includes your Technical Representative. you may want to use your organization structure. change.

About Oracle Oracle Corporation develops and markets an integrated line of software products for database management.other than Oracle Applications. You also lose the ability to track who has changed your information because SQL*Plus and other database tools do not keep a record of changes. Oracle offers its database. unified computing and information resource. xxxii Oracle SSHR 4. Oracle products are available for mainframes. applications development. you may change a row in one table without making corresponding changes in related tables. manufacturing. If your tables get out of synchronization with each other.2 Implementation Guide . and the world’s second largest software company. and application products. Oracle Applications automatically checks that your changes are valid. into a single. you risk retrieving erroneous information and you risk unpredictable results throughout Oracle Applications. different networks. and even different database management systems. you may store invalid information. supply chain management. an integrated suite of more than 160 software modules for financial management. Oracle Applications also keeps track of who changes information. education and support services. network computers and personal digital assistants. allowing organizations to integrate different computers. human resources and customer relationship management. project systems. When you use Oracle Applications to modify your data. along with related consulting. as well as Oracle Applications. personal computers. tools. If you enter information into database tables using database tools. decision support and office automation. different operating systems. in over 145 countries around the world. Oracle is the world’s leading supplier of software for information management. minicomputers.

CHAPTER 1 Overview of Self–Service Human Resources Overview of Self–Service Human Resources 1–1 .

views.2 offers secure self–service business transactions and easy–to–use functionality driven by Oracle’s proven web and workflow technologies. thus providing seamless integration between Oracle HRMS and Self–Service HRMS. Using a standard web browser. What is SSHR 4. validation routines. for example. to 1–2 Oracle SSHR 4. such as updating personal and educational details. for example during an annual benefit enrollment period opportunities to configure and extend the application to meet enterprise needs system accessibility for people who are not Human Resource specialists ability to configure SSHR web pages to suit user requirements.Overview Oracle Self–Service Human Resources (SSHR) extends the functionality of standard Oracle HRMS by enabling both employees and managers to participate in Human Resources management via a web browser.0? The following sections answer common questions on SSHR and give an overview of the functionality. stored procedures. • • • What are the advantages to the HR Department? Potential self–service activities in an HR department range from simple data entry tasks. registering a change of address. the user accesses HR data and performs a specific task.2 Implementation Guide . By transferring the responsibility for the task to the originator of the task. How do self–service applications differ from traditional HR systems? The key elements that distinguish self–service applications from other systems are: • • • • easy–to–use user interfaces easy access to functions via web browsers complex processes reduced to simple steps reliability and scalability enabling many people to experience good response times. and APIs used in the standard Oracle Applications to be shared. SSHR 4. These technologies enable the data. What does self–service mean? Self–service means that the originator of a task is also the person responsible for that task. data accuracy is increased and administration costs are reduced.

0) are collections of functions intended for distinct audiences. and security profiles – used in standard Oracle applications also apply to self–service users. Another key advantage to the HR department is the accuracy of employee–maintained information. the manager functions allow the user to select an employee from a list of available employees and carry out the required function. How can the HR Department control the self–service activities available to each user? The security controls – responsibilities. HR management can now be so easily accessible that a virtual HR manager is always at hand. With SSHR. although they are not intended for production use. and legislation advice to all employees. you could use data on the skills of your employees to create a report showing how these skills could be better deployed throughout the enterprise. SSHR enables HR managers to publish information on job opportunities. A new dialog can be created between management and employees which results in increased employee applications for jobs or training and increased accuracy of personal information stored on employees. the person making an inquiry or wanting to change their personal details can find and manage this information themselves at little administrative cost to the HR department.more complex tasks. for example. Managers can also search for people with the right skills if they have an unfilled vacancy. For example. non–productive vacancies. or find new work for an employee. and minimize the number of unfilled. a manager can now make HR decisions even quicker. This can help reduce the number of rejected offers caused by delays in the recruitment process. customers can configure their own variations of these menus and responsibilities. The seeded SSHR responsibilities corresponding to each of these menus are useful for exploring the functionality delivered with the product. Overview of Self–Service Human Resources 1–3 . combined with appropriate security profiles. and quick decisions. menus. to restrict different groups of users to specific functions and employee groups. The seeded SSHR menus (Employee Self Service V4. The employee functions are constrained to operate only on the current self–service user’s record. to ensure that their pay check is mailed to the correct address. Employees have a vested interest in ensuring their information is accurate. Instead. such as informing employees of their current vacation allowance and providing policy advice. Accurate and timely data is also vital for HR reports.0 and Manager Self Service V4. company policies. Non–HR managers often have direct contact with employees and customers and can make informed. Using SSHR. expert.

1–4 Oracle SSHR 4.The Personalization Framework and Workflow Builder tools offer considerable flexibility in controlling the user’s access to specific functions and require that users’ transactions are approved before they are committed to the database. Although SSHR uses the design standards that are common to all Oracle applications. If you want to highlight procedures that are specific to your enterprise. Benefits eligibility profiles and enrollment requirements can determine which benefits an employee can select from within the Benefits Enrollment function. You can also control the user’s access by configuring the base products. For example. On some pages. you can customize the instructions that provide online help for users. How can SSHR meet my enterprise’s unique business processes? SSHR is highly configurable: you can configure web pages and predefined business transactions. you can change the appearance of the web pages by adding your own logos and by changing field and radio button names.2 Implementation Guide . You can also create your own business processes. you can choose which sections are displayed.

See: The Pesonalization Framework: page 7–2 Oracle Applications (OA) Framework The OA Framework is the technical foundation for the Oracle Self–Service Applications (OSSWA). They can be subdivided into sub–processes. Your configurations are stored in the MDS Repository and are preserved during upgrades. or business objectives. Customers can configure changes to the definitions held in the MDS Repository using the Personalization Framework. for example. The region is defined in terms of elements such as fields and buttons. critical success factors. They support the organization’s objectives. Region A region in the MDS Repository defines a section in a page in Oracle Self–Service Web Applications. Personalization Framework The Personalization Framework allows you to configure the display of Oracle Self–Service Web Applications (OSSWA) without having to make any changes to the underlying code. Definitions AOL function An AOL function is an item that can be added to a menu.Key Concepts in Self–Service Human Resources (SSHR) This section defines some important terms used throughout this Implementation Guide. See: The Personalization Framework: page 7–2 MDS (Meta Data Services) Repository An active repository that stores information on the appearance and behavior of self–service pages. The item can call a screen or web page or be a hidden function. the Change Hours workflow process consists of the Work Schedule and Pay Rate subprocesses. See also: Self–Service Function Business Process Produces the products and services that are recognized outside the business area. Self–Service Function Overview of Self–Service Human Resources 1–5 .

For example. such as changes to salary. See: Self–Service Workflows: page 6–2 Workflow Function A workflow activity which is defined as a function and which maps to a PL/SQL procedure that is executed by the Workflow Engine when it encounters this activity in the workflow process. locations. stored procedures). You use workflow to control who and how these participants take part in HR processes by modifying the underlying process definitions.2 Implementation Guide . but all the components of a transaction must be handled as a unit to be either approved or rejected. the employee. Transaction A transaction is a logical unit of work such as a promotion or an assignment change. It may consist of several components. and Assignment. or a subprocess.Self–service functions appear as menu options to the SSHR user. Self–Service Module A set of dynamic web pages and related components (for example. Examples include Personal Information. the manager. the same self–service module is used for Personal Information from both the manager and employee menus but the function determines whether the module is called in Employee or Manager mode. Competencies. and the applicant. See: Self–Service Workflows: page 6–2 Workflow Process A workflow process is a series of activities linked by transitions. The function determines how the self–service modules are called. Each activity can be a function. 1–6 Oracle SSHR 4. and grade. workflow process and definitions stored in the MDS Repository. Workflow Builder Oracle Workflow is embedded within SSHR and manages the flow of information between the HR professional. a notification.

4) Both Both Both Both Manager Manager No/Yes No/Yes No/Yes No/No No/No No/No Global Global Global Global Global Global Overview of Self–Service Human Resources 1–7 . Summary of SSHR Modules Note: In the tables below the Manager/Employee column refers to the type of activities that the responsibility would do. see the individual sections on each module. rather than a function that would specifically appear on a Manager or Employee menu.4) Succession Planning (3.4) Apply for a Job (3.4) Employee Reviews Events and Bookings Suitability Matching (3. For available functions within each module. Absence Modules Module Name Manager/Employee Workflow chainable/Approvals Localization Absences Both No/Yes Global Benefits Module Name Manager/Employee Workflow chainable/Approvals Localization Benefits Enrollment Benefits Enrollment Both Employee No/No No/No Global Federal Career and Performance Management Module Name Manager/Employee Workflow chainable/Approvals Localization Appraisals (3.Self–Service Modules This section provides a brief description of the delivered SSHR modules.

Common Modules Module Name Manager/Employee Workflow chainable/Approvals Localization Enter Person Process Manager Actions New User Registration Review and Confirm Release Employee Information Personal Actions Save for Later Manager Manager Both N/A Both Employee Both No/No No/No Yes/Yes Yes/Yes No/Yes No/No No/No Global Global Global Global Global Global Global Compensation Module Name Manager/Employee Workflow chainable/Approvals Localization Compensation Workbench Individual Compensation Distributions (ICD) Manager Manager No/Yes Yes/Yes Global Global Manage Employee Events Module Name Manager/Employee Workflow chainable/Approval Localization Assignment Change Location Change Manager Other Employment Information Pay Rate Extra Information Types (EITs) Manager Manager Manager Manager Manager Both Yes/Yes Yes/Yes Yes/Yes Yes/Yes Yes/Yes Yes/Yes Global Global Global Global Global Global 1–8 Oracle SSHR 4.2 Implementation Guide .

Hong Kong. UK. Korea New Zealand. Canada.Module Name Manager/Employee Workflow chainable/Approval Localization Special Information Types (SITs) Termination Work Schedule Both Manager Manager Yes/Yes Yes/Yes Yes/Yes Global Global Global Organization Management Module Name Manager/Employee Workflow chainable/Approval Localization Organization Manager Manager Yes/Yes Global Payroll Module Name Manager/Employee Workflow chainable/Approval Localization Online Payslip Both No/No Australia. Singapore. South Africa Global Personal Payment Methods (Direct Deposit) Online Tax Form (W–4) Online W–2 Form Both No/Yes Both Employee No/No No/No US US Personal Information Module Name Manager/Employee Workflow chainable/Approval Localization Basic Details Main Address Both Both Yes/Yes Yes/Yes Global Global Overview of Self–Service Human Resources 1–9 . US.

4) New Hire Manager Manager Manager No/Yes No/Yes No/Yes Global Global Global 1–10 Oracle SSHR 4.Module Name Manager/Employee Workflow chainable/Approval Localization Other Address Phone Number Emergency Contacts Dependents and Beneficiaries Both Both Both Both Yes/Yes Yes/Yes Yes/No Yes/No Global Global Global Global Professional Details Module Name Manager/Employee Workflow chainable/Approval Localization Academic Rank Competence Profiles Education and Qualifications Resume Other Professional Awards Tenure Status Work Preferences Both Both Both Both Both Both Both No/Yes No/Yes No/Yes No/No No/Yes No/Yes No/No US Global Global Global Global US Global Recruitment Module Name Manager/Employee Workflow chainable/Approval Localization Applicant Hire Candidate Offers (3.2 Implementation Guide .

update. See: Absences: page 15–2 Benefits Benefits Enrollment Benefit Enrollments enables an employee to: • • • • • Review their current benefit enrollments Select benefits Add.Global ured) No/No (can be config. Users can submit and update absence requests. confirmed. or remove dependents Add.4) HR Views Both HR Professional No/No No/No Global Global Absences Absences The Absences module enables employees or managers to enter absence–related information using a self–service interface. and updated requests are then submitted for approval. or remove beneficiaries Search for and select primary care providers See: Self–Service Benefits Enrollments: page 17–2 Overview of Self–Service Human Resources 1–11 .Training Module Name Manager/Employee Workflow chainable/Approval Localization External Training V4. update.0 Training V4.0 Both Both No/No (can be config. Planned.Global ured) Views Module Name Manager/Employee Workflow chainable/Approval Localization Employee/Manager Views (3.

see: Implementing Oracle Self–Service Human Resources 3. Apply for a Job (3.0 function is available to both managers and employees. see: Federal Health Employee Benefits Overview: page 18–2 Career and Performance Management Appraisals (3.4) The Appraisals module enables a manager and employee to evaluate employee performance and competencies and to set objectives and actions.0 module enables employees and managers to create or update reviews. See: Events and Bookings: page 11–2 Suitability Matching (3. presentations. manage their resume. enabling managers to book their subordinates onto events.For information on US federal self–service benefits. For information on Apply for a Job.4) The Apply for a Job module enables employees to search for and apply for jobs.4 (available on Metalink).4 (available on Metalink). For information on Suitability Matching. Employees can create their own reviews and managers can create reviews for their employees. See: Employee Review: page 11–4 Events and Bookings The Events and Bookings V4.2 Implementation Guide . 1–12 Oracle SSHR 4.0 module enables self–service users to create their own events such as meetings. view job details. For information on Appraisals.4 (available on Metalink). The Events and Bookings V4. see: Implementing Oracle Self–Service Human Resources 3. Both managers and employees can invite reviewers to attend the review. Employee Reviews The Employee Review V4.4) The Suitability Matching module compares and matches a person’s competences against a job or position. and prepare applications. see: Implementing Oracle Self–Service Human Resources 3. or training days or to book themselves on existing events.

Succession Planning (3. to be performed.4 (available on Metalink). see: Implementing Oracle Self–Service Human Resources 3. a manager can search for a person or persons who meet particular criteria. See: Oracle Approvals Management (AME): page 8–5 Manager Actions The Manager Actions module enables the user to first select a person and then the function. You can search on personal.4) The Succession Planning module enables a manager to prepare an employee for a position and to plan a successor for the position. The existing method of defining customizable PL/SQL packages for approvals is still supported in this release as an alternative to AME. assignment or skills criteria. a context–sensitive list of available actions is displayed and the user can choose the required action from the list. or action. Overview of Self–Service Human Resources 1–13 . low–level functionality that is reused in many of the higher–level functions. see: Implementing Oracle Approvals Management (available on Metalink). When the user selects the person.1 uses the Oracle Approvals Management (AME) application to define and manage approval logic. Enter Person Process The Enter Person process enables the user to: • • • Select an employee from a searchable list of people Select an employee from their supervisor hierarchy Add and remove employees from their personal list of employees A Simple Search enables to search for an employee by name. With an Advanced Search. For information on Succession Planning. Common Modules The following generic modules provide common. See: Navigation Paths: page 5–5 See: Actions Page: page 9–8 Multiple Assignments The multiple assignment functionality enables managers to view and update multiple assignments for an employee. Integration with Oracle Approvals Management SSHR 4. For more information on AME.

See: New User Registration: page 9–18 Personal Actions The Personal Actions module is the employee equivalent of Manager Actions. The user can review the information displayed to ensure that all the details are correct before the changes are finally submitted to the database.This functionality is available in all MEE modules with the exception of Termination. the user can return to the previous screen to change incorrect information.2 Implementation Guide . The employee is presented with a context–sensitive list of actions that they can perform on themselves. an employee may have requested a transfer to another group and the manager of the group may want to review the employee’s employment information before making a decision. If necessary. who would not normally have access to these records. See: Review and Confirm: page 9–15 Save for Later The Save for Later functionality enables a user to interrupt a transaction before the data is submitted. often a manager. See: Release Employee Information: page 9–13 Review and Confirm The Review and Confirm module shows details of transactions that a user has updated or details about pending transactions that require approval. See: Multiple Assignments: page 9–11 See: User Access to People: page 5–2 New User Registration New User Registration enables users to register their own details for SSHR and for benefits providers. See: Navigation Paths: page 5–5 See: Actions Page: page 9–8 Release Employee Information The Release Employee Information module enables an SSHR user to share information about themselves with another employee. The transaction is saved in a 1–14 Oracle SSHR 4. An employee can revoke access to their information at any time – unless the application has been configured differently. For example. You set up a generic name and password and you can either enable users to create their own user name or you can use user hooks to create the user name automatically.

See: Save for Later: page 3–11 Compensation Compensation Workbench The Compensation Workbench enables managers to determine and allocate compensation awards such as salary increases. prepare budgets. and stock options using a self–service interface. See: Assignment: page 12–5 Overview of Self–Service Human Resources 1–15 . ICD is available to users of both Standard and Advanced Benefits. You can also set up ICD for non–manager employees if your enterprise offers discretionary contribution plans. Managers can also view details on their direct reports. or which were partially saved at the time of a system failure or timeout. See: Compensation Workbench: page 22–2 Individual Compensation Distributions (ICD) ICD enables managers to assign one–time or recurring awards. you can display and change any assignment. and generate reports. bonuses. bonuses.transaction table from which it can be retrieved and continued at a later time. See: Individual Compensation Distributions: page 19–2 Manage Employee Events (MEE) The Manage Employee Events (MEE) functionality consists of a set of low–level. such as a charitable contribution or savings bond plan. The MEE components are as follows: Assignment The Assignment module enables a manager to change an employee’s assignment information. You define ICD plans using the same application windows that you use to define employee Benefits plans. If the employee has multiple assignments. and allowances to qualified employees and individuals. workflow–enabled components which can be chained together in various combinations to match your enterprise’s business processes. from the Actions Saved for Later list in the Actions page. Users can select those transactions which they have explicitly saved for later. Some chained processes are predefined for you but you can use the Workflow Builder to configure others if you need to.

You can also use the Change Supervisor workflow process to reassign a terminated supervisor’s reports. See: Extra Information Types (EITs): page 12–20 Other Employment Information The Other Employment Information module enables you to update and retrieve assignment and employment information in assignment descriptive flexfields and localization–enabled flexfields. 1–16 Oracle SSHR 4.2 Implementation Guide . move the direct reports of one supervisor to another supervisor and to assemble a new set of direct reports to a new supervisor.Change Location The Change Location module enables a manager to change an employee’s work location. See: Other Employment Info: page 12–23 Pay Rate The Pay Rate module enables a manager to change an employee’s overall pay rate or update an individual component of the pay rate. See: Special Information Types (SITs): page 12–17 Termination The Termination module enables a manager to end an employee’s relationship with their employer. See: Change Manager: page 12–26 Extra Information Types (EITs) Extra Information Types for SSHR enable you to store additional person and assignment information. You can combine the Termination module with the ICD module to create a severance pay process if required. Note: You cannot reverse a termination in SSHR. See: Location: page 12–14 Change Manager The Change Manager module enables a manager to transfer an employee to another supervisor. See: Pay Rate: page 12–24 Special Information Types (SITs) Special Information Types enable you to store additional information that is not currently captured by the system.

Note: Organization manager relationships can only be initially created in the Professional Forms Interface. The form is used for information purposes only as it contains no updateable fields and cannot be submitted in place of the paper version of the form. See: Tax Information Form (W–2) (US): page 20–27 Tax Withholdings Form (W–4) The Online Tax Form module enables an employee to submit US Tax Withholdings forms (W–4 tax forms) using a Web browser. A defined contact person will then receive notification of the changed information. Payslips are available for all assignments for which payroll has been completed. See: Organization Manager: page 14–2 Payroll Online Payslip The Online Payslip module enables an employee to view their payslip using a Web browser when the required payroll processes have been run. See: Online Payslip: page 20–10 Tax Information Form (W–2) The Tax Information form gives summary tax information for tax years from 2001 onwards. See: Work Schedule: page 12–12 Organization Management Organization Manager The Organization Manager module enables a manager to maintain organization manager relationships. Employees can display payslips for the most recent payroll period or for previous payroll periods. The employee can use the form to update withholding information.See: Termination: page 12–10 Work Schedule The Work Schedule module enables a manager to change an employee’s work schedule. Overview of Self–Service Human Resources 1–17 .

1–18 Oracle SSHR 4. deposit. See: Individual Compensation Distributions: page 19–2 Personal Information The Personal Information module enables users to update and maintain their personal records. You define ICD plans using the same application windows that you use to define employee Benefits plans. such as a charitable contribution or savings bond plan. check. The Personal Information module covers the following areas: • Basic employee details See: Basic Details: page 10–3 • Address See: Main Address: page 10–5 • Other addresses See: Other Address: page 10–7 • Phone number See: Phone Numbers: page 10–9 • Employee dependents and beneficiaries See: Dependents and Beneficiaries: page 10–11 • Emergency contacts See: Emergency Contacts: page 10–13 The Personal Information module can also be chained with Special Information Types (SITs). or a combination.2 Implementation Guide . See: Personal Payment Methods: page 20–3 Voluntary Deductions You can use the Individual Compensation Distributions (ICD) module if your enterprise uses voluntary deduction plans. ICD is available to users of both Standard and Advanced Benefits.See: Tax Withholdings Form (W–4) (US): page 20–24 Personal Payment Methods The Personal Payment Methods module enables an employee to determine how they are paid. The available payment methods are cash.

See: Competence Profiles: page 10–21 Work preferences The Work Preferences module enables employees and managers to store information such as relocation preferences and travel preferences. The Professional Details menu contains the following functions: Education. certain functions can be restricted for manager access only. Overview of Self–Service Human Resources 1–19 . See: Tenure Status: page 10–26 Academic Rank (US) The Academic Rank module enables managers to store information on the academic rank for employees within Higher Education. They can be used by both employees and their managers. See: Other Awards: page 10–19 Competence profiles The Competence Profile module enables employees and managers to store information on skills and competences.See: Personal Information: page 10–2 Professional Details The Professional Details modules enable users to maintain professional details. however. See: Resume: page 10–25 Tenure Status (US) The Tenure Status module enables managers to store information on an employee’s tenure (completion of professional criteria and extended probationary period). qualifications The Educations and Qualifications module enables employees and managers to store details on their academic qualifications. See: Work Preferences: page 10–24 Resume The Resume module enables employees and managers to store a resume. See: Education and Qualifications: page 10–16 Other professional awards The Other Professional Awards module enables employees and managers to store details on professional qualifications.

The External Training V4. Views Employee/Manager Views (3. see: Implementing Oracle Self–Service Human Resources 3.4) The Candidate Offers module is used by managers to seek approval for a job offer. and track the applicant’s response.0 module enables employees and managers to enter and update attendance in courses not registered as events in Oracle Training Administration.4 (available on Metalink).4 functions Enroll in a Class and Cancel Enrollment.4) 1–20 Oracle SSHR 4.4. See: New Hire and Applicant Hire Processes: page 13–2 Candidate Offers (3. The Training V4. See: New Hire and Applicant Hire Processes: page 13–2 Training Training The Training V4.2 Implementation Guide .0 module replaces the Training History function available in SSHR 3.See: Academic Rank: page 10–28 Recruitment Applicant Hire The Applicant Hire process is used by managers to hire applicants who have an applicant assignment with a status of Accepted. send it to an applicant.0 module enables employees to enroll in a class and cancel the enrollment. Managers can enroll their subordinates in training classes and cancel the enrollment if appropriate. New Hire The New Hire process is used by managers to enter details about new employees and hire them into their enterprise. For information on Candidate Offers.0 module replaces the SSHR 3. See: Training: page 21–2 External Training The External Training V4.

Assignment Details. for example. Compensation Activity. employment history. and Termination History. This module is used by the HR Professional. see: Implementing Oracle Self–Service Human Resources 3. For information on Employee and Manager Views. HR Views The HR Views module offers a summarized view of specific employee information: Personal Information.The Employee and Manager views offer the user access to specific information. and salary history. See: HR Views: page 16–2 Overview of Self–Service Human Resources 1–21 . Employees can view their own personal records and managers can view the records for the people they manage. absence history.4 (available on Metalink).

If you have licenced SSHR you have access to all SSHR HRMS functionality with the following exceptions: • Oracle Advanced Benefits (OAB). life event restrictions in the Advanced Benefits model allow you to use Self–Service Benefits at any time during the year. Note: For Standard Benefits customers. • • Oracle Training Administration – You must purchase a separate licence to be able to use the self–service training function. For example. additional functionality is available if you purchase OAB. 1–22 Oracle SSHR 4. Although the self–service Benefits functions are available with Standard Benefits which is included in the HRMS licence. SSHR delivers particular functionality according to your base product licence.2 Implementation Guide . you should consider taking your enrollment web pages off–line during periods where you do not want benefits participants to make changes to their elections. contact your Oracle sales representative.SSHR Licences To enable SSHR. In other words. Payroll – You must purchase a separate licence to be able to use the self–service payroll functions. you must first purchase the appropriate licence from Oracle. it is recommended the Benefits Election function be available only during the annual enrollment period. For information on licences.

the Personal Details function. The Manager Self–Service menu contains the same functions as the employee menu plus additional functions that the manager can carry out for the employees for whom they are responsible. You should create your own responsibilities and menus using the predefined SSHR responsibilities and menus as examples. the predefined responsibilities are: • • • • • Employee Self–Service V4. The HR Professional menu is available for HR professionals who wish to view summarized information on employees.0 Manager Self Service 4. each with a corresponding top level menu.0 HR User Self Service New User Registration HR Professional V4.0 The Employee Self–Service menu contains the functions that employees can perform on their own records. Overview of Self–Service Human Resources 1–23 . Otherwise. your changes may be lost during an upgrade. See: User Access and Security: page 5–2 See: Oracle Self–Service Web Applications User Guide User Menus SSHR includes several predefined top–level menus: • • • Employee Self Service 4.0 Manager Self–Service V4.0 HR Professional V4. for example.0 HR Foundation The predefined responsibility for the HR Foundation application is: • The additional responsibilities provided by OSSWA (Oracle Self–Service Web Applications are: • • Workflow User Web Applications Preferences Note: These responsibilities are provided as a starting point only. In this version of SSHR.Predefined Self–Service Responsibilities and User Menus SSHR modules are accessible from predefined responsibilities.

2 Implementation Guide . See: Self–Service Menus: page 5–9 1–24 Oracle SSHR 4. Legislation–specific Menus SSHR provides legislation–specific menus to give users access to the functions that are specific to a country. They can either use the above menus and select the function using the corresponding menu option or they can display the Actions page and select the required function from the list of available actions.You can also use the following menu for administration purposes: • HR Web Administrator See: Self–Service Menus: page 5–9 Navigation Options for Functions Both employees and managers can access functions in one of two ways.

CHAPTER 2 Getting Started with SSHR Getting Started with SSHR 2–1 .

See: Self–Service Workflows: page 6–2 Note: Some 3.x and SSHR 3.x components are still supported You can have both SSHR 4. See: Minimum Requirements for an SSHR System: page 2–3 For a list of all implementation steps. • When ready. if required.2 Implementation Guide .x functions when they become available. you would compare the new and old workflow processes and reapply workflow changes as required. 2–2 Oracle SSHR 4.x functions on the same menu You can set up equivalent 4. simply migrate your users to the 4. In doing this.x may be installed in the same instance as SSHR 3.x as they have been replaced by the Personalization Framework functionality.x workflow attributes are obsolete in SSHR 4.x: • • • • SSHR 4. see Implementation Steps for SSHR: page A – 2 Notes on Migrating from SSHR Version 3 The following notes provide you with information that is useful if you are upgrading your SSHR installation from 3.x to 4.x functions.x functions one at a time.x SSHR 3.Overview This section gives you a brief overview of the minimum tasks you need to complete to set up SSHR. You can switch over to 4.

Reporting. See: Self–Service Responsibilities and User Menus: page 1–23 See: Responsibilities (Configuring. Set up the Apache server as specified in the Oracle Self–Service Web Applications Implementation Manual (available on Metalink). Add the Manager Self Service and Employee Self Service responsibilities to your users (use either new or existing users).1) 6. 4. Ensure that at least one business group has been set up in Oracle HRMS with at least two employee records (one record should be defined as the supervisor for the other). See: Configuring and Troubleshooting Oracle HTTP Server with Oracle Applications (available on Metalink – technical note number: 139863. 7. Apply the patch for SSHR 4. Ensure that Oracle Human Resources 11i is installed with the most up–to–date patch according to the readme file for SSHR at the time of installation. set the following profile option to ”Yes” at the site level.x and make sure that all prerequisites are met. • 2. Ensure that the Apache server and Apache JSERV are installed. and System Administration in Oracle HRMS) If you have not licensed SSHR. 5. including those for the OSSWA Framework. which lists the implementation steps. and System Administration in Oracle HRMS) 3. please contact your Oracle sales representative for information on purchasing a licence. Reporting. For information on running SSHR in a production environment. Reporting. To set up an SSHR system: 1. and System Administration in Oracle HRMS) Getting Started with SSHR 2–3 . If you have licensed SSHR. HR: Self Service HR Licensed See: User Profiles (Configuring.Minimum Requirements for an SSHR System The following procedure gives you the basic implementation steps that are required to enable you to run SSHR in a test environment. Complete the install and set–up of the OSSWA Framework. please see the detailed chapters in this Implementation Guide and also the Appendix. See: Adapting and Creating a New Business Group (Configuring.

8. please see: Understanding a Typical SSHR Function: page 3–2 2–4 Oracle SSHR 4. and System Administration in Oracle HRMS) For information on a typical SSHR function.2 Implementation Guide . See: Defining User Access and Menus: page 5–12 See: Users Window (Configuring. Link the users to (new or existing) employee records in HRMS. Reporting.

Getting Started with SSHR 2–5 .5. 5. Choose View Report. If any profile options have not been set. you can select the System Administrator responsibility in this field. acts as a trouble–shooting aid. they are displayed in red. This application is delivered free to customers with Oracle HRMS 11. 3. the HRMS Profile Options Report does not apply this restriction. Note: The responsibility selected usually defines which diagnostic tests you can run based on the associated application. consequently. the report will end with the status Failed. The report also identifies which profile options have not been set for your installation and.1. For more information. The report lists the profile options and settings for your application. Enter your application user ID and password. 2. see MetaLink note 167000.Running the HRMS Profile Options Report The HRMS Profile Options Report lists the values of the profile options set for your HRMS installation.4 or above. Select a responsibility ID. therefore. However. Choose Run Test. Select the application for which you want to run the report. 4. If the report has identified missing profile option settings. " To run the HRMS Profile Options Report: 1. You run the HRMS Profile Options Report using the Oracle Diagnostic Framework.

2 Implementation Guide .2–6 Oracle SSHR 4.

CHAPTER 3 Understanding How SSHR Functions Work Understanding How SSHR Functions Work 33–1 .

Personal Information. 3–2 Oracle SSHR 4. The chapter includes an example of a typical SSHR Web page to illustrate the different elements that you can configure. how the page layout is controlled by the definitions held in the MDS Repository and the Personalization Framework. and introduces the underlying concepts. The configuration steps for SSHR functions and their web pages are discussed in detail in the subsequent chapters of the Implementation Guide.Understanding a Typical SSHR Function This chapter examines a typical SSHR function. The general principles described here can be applied to any other SSHR function. By following the functional flow of the Personal Information function. how Workflow is used by SSHR. and how the approvals process operates.2 Implementation Guide . you should understand how information is passed from the web browser to Oracle Applications.

Understanding How SSHR Functions Work 33–3 .How an SSHR Function Works in SSHR 4.2 The following flowchart and accompanying text describe the functional flows that occur when a user changes a main address using the Personal Information function.

Personal Information is a global function that is available for all legislation codes. 3–4 Oracle SSHR 4. A page is displayed based on the definition of the OverviewPG document in the MDS Repository. Oracle Workflow runs the Maintain Personal Information activity (HR_PERINFO_OVERVIEW_JSP_FCT) within the Personal Information subprocess (HR_PROCESS_PERINFO_JSP_PRC) within the Personal Information workflow process (HR_PERSONAL_INFO_JSP_PRC). The HR Activity Type Value workflow attribute for this process activity is set to HR_OVERVIEW_TOP_SS with the Activity Type as JSP.1.BLOCK function. 4.2 Implementation Guide . The application calls the HR workflow service (OA.jsp?akRegionCode=HR_CREATE_PROCESS_TOP_ SS&akRegionApplicationId=800) with a parameter specifying the Personal Information workflow process for the workflow item type (HR_MAINT_PERSONAL_DETAILS_PRC). the Entry page is displayed. 8.jspsOA. 7. 6. The button displayed to the user will be either Update/View Future Changes or View Pending Approval. If the user chooses to enter a new address. See: User Access and Security: page 5–2 3. The user enters the information. the Details page is displayed. 2. or if no future–dated address changes exist. The page is influenced by any context–sensitive flexfields and the cumulative effect of any Personalization Framework configurations that relate to this document. The application calls the generic HR_WORKFLOW_SERVICE. See: Self–Service Workflows: page 6–2 The HR workflow service creates an instance of the Personal Information workflow process for the item type. See: The Pesonalization Framework: page 7–2 If no past address changes are awaiting approval or correction. The user chooses the Personal Information function from the user menu. The FND data security is checked to make sure that this function is permitted for the legislation code of the current employee’s business group. The user specifies whether they want to correct an existing address or enter an entirely new one. 5.

the data is inserted into HR transaction tables and the Approvals process begins for that item. If the Main Address part of the Personal Information function is configured for update without requiring approval. Web page data is sent from the client to the server and server–side validation is performed by HR Application Programming Interfaces (APIs). missing fields. The workflow item is routed for approval according to the configuration of the Approvals process. See: Save for Later: page 3–11 If the user chooses to correct an existing address. The approver can either approve or reject the transaction or return it to the user for correction. they click the Continue link at the bottom of the page.) 15. they can choose the Back button to return to the update page to make changes. If the Main Address part of the Personal Information function is configured to require approval. If the transaction is returned for correction. See: Review and Confirm: page 9–15 11. The Understanding How SSHR Functions Work 33–5 . When the user has entered the information (or is ready to complete the transaction). it is displayed for the user in the Actions Saved for Later table in the Actions page. 13. The number of approval levels and approvers is determined by the configuration of Dynamic Approvals. the user returns to the Review page and clicks the Submit Information link to save the changes. 17. If all fields are validated. If applicable.If required. See: Dynamic Approvals: page 8–2 14. the Review page is displayed. 16. The Review page displays the information that the user has entered. 12. the changes entered so far are saved to the transaction tables without server–side validation. the user can save the information and submit the transaction later. In this case. The user corrects the information. Any field–related errors (bad formatting. 9. the existing Address information is displayed. When the changes are complete. (This step is the same process as step 18 for changes requiring an approval. the user can insert additional approvers and/or notification recipients. 10. and so on) are flagged by a JavaScript procedure stored on the client and the user is asked to correct this information. the new address data is inserted directly into the HR tables. If the user now wants to modify the address information.

2 Implementation Guide . 3–6 Oracle SSHR 4. the user is notified of the transaction status and the transaction details are deleted from the transaction tables. See: Save for Later: page 3–11 When the approver approves or rejects the transaction.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. If the transaction is approved. the data is loaded into the HR tables.

2. Add or remove links to enable personalization configuration Change the sequence of fields Add or remove buttons to control user’s ability to update fields Rename region items Configure table views Understanding How SSHR Functions Work 33–7 . Figure 3 – 1 Sample Web Page The graphic above shows the following elements which you can configure using the Personalization Framework: 1. 4. 3.A Typical SSHR Web Page The following diagram shows a simplified sample web page for the Personal Information function. The different elements that you can configure in the Personalization Framework are listed below. 5.

2 Implementation Guide .See: The Personalization Framework: page 7–2 3–8 Oracle SSHR 4.

The following checks are then carried out in a chained process: • hire_date Checks if the effective date entered is earlier than the hire date termination_date Checks if the effective date entered is earlier than the termination date • • future_assignment Checks if there are any future assignment changes with respect to the effective date entered • pending_workflow Checks if there are changes pending in the workflow tables for the selected person • correction_mode Issues a warning (alert) only if the latest effective date of the primary assignment is less than the SYSDATE Future–Dated Changes It is possible that an SSHR user may try and update information when a future–dated change is pending.Managing Dates in SSHR Effective Dates If a user is prompted to enter an effective date. the application validates the entry to make sure the data is correct using specific criteria. If a future–dated change has been entered. the day after the change date is used. The system date is the default date unless a future–dated assignment change has already been entered into the system. This action triggers the following process: • • • The application sends the user a message instructing them to contact their support representative The user is prevented from making any changes The workflow error process sends a message and description to the Sysadmin ID informing them that an attempt was made by a user to update information with a future–dated change pending Understanding How SSHR Functions Work 33–9 .

you can send a notification explaining that the update will be made at some point in the future. Note: A system administrator or other implementor of Self–Service Benefits can access the Change Session Date menu option for testing future dated enrollments. 3–10 Oracle SSHR 4. To remove the Change Session Date item from the menu.2 Implementation Guide . You should remove this menu item in your production environment so that benefits participants do not alter their enrollment date. implement the requested change to information. Alternatively. you could cancel the future–dated change.You then decide how to manage the update requested by the user. query the BEN_SELF_SERVICE_BENEFITS menu option in the Menus window and delete the Change Session Date menu entry. For example. and then implement the future–dated change again.

In this case.Save For Later The Save for Later functionality enables a user to interrupt transactions before they are complete and save them so that they can be completed at a later point. and resubmit it for approval. If the user submits the Understanding How SSHR Functions Work 33–11 . Both suspended transactions and returned transactions are displayed in the Actions Saved for Later table on the Actions page. Figure 3 – 2 Save for Later Functionality The graphic above shows the two different ways in which transactions can be saved for later. they can either submit the transaction for approval immediately or save the transaction for subsequent processing. approvers can return transactions to the initiator for correction. Users can also access their saved functions using the All Actions Saved for Later menu option on the employee and manager menus. The approvers can include informational notes to clarify the reason for returning the transaction. the initiator can reopen the transaction. correct the information. Route 1: When a user initiates a self–service transaction. In addition.

or a system failure. Note: If a transaction is interrupted due to user inactivity. a timeout. If the approver returns the transaction for correction. the approver can either approve the transaction. it is suspended and the user can restart it or delete it from the Actions Saved for Later table in the Actions page.2 Implementation Guide . the interrupted transaction is also stored as a suspended transaction. Route 2: When a user has submitted a transaction for approval. the transaction is subject to the usual approval processes.transaction immediately. the initiator can subsequently restart or delete it from the Actions Saved for Later table in the Actions page of the initiator. 3–12 Oracle SSHR 4. If the user chooses to save the transaction for later. reject the transaction. or return it for correction.

CHAPTER 4 Configuring SSHR Configuring SSHR 4–1 .

you might choose to implement one version of the Personal Information module for all employees. you can configure multiple variations of the same module to suit different groups of users. Although the SSHR modules are delivered with predefined settings which meet the HRMS requirements of the majority of enterprises with little or no configuration.2 Implementation Guide . and then repeat the steps for the other functions. see the following chapters: • • • • Managing User Access – Chapter 5 Configuring Process Flows – Chapter 6 Configuring Page Layouts – Chapter 7 Approvals – Chapter 8 Guidelines for Configuring SSHR Functions The best approach to take when configuring SSHR is to first configure a sample function. and another version for a second set of managers. are built on the Oracle Applications (OA) Framework to enable maximum flexibility. if required. For detailed information on the configuration steps. test it until you are satisfied with the results. there are many configuration options available to ensure that all your enterprise requirements are met. Note: If function–level personalizations have been delivered by Oracle for a function you wish to copy.Configuration Overview All Oracle Self–Service Applications. including the SSHR modules. another version for one set of managers. be aware that you will lose these personalizations if you create a custom version of the function. It is important to consider both the module and the intended audience at the same time because. This chapter provides an overview of the different configuration steps for SSHR and introduces a common configuration method that you can apply to any SSHR module in conjunction with the function–specific configuration steps. Start your configuration process by configuring a module for a particular group of users. See: Function–level Personalizations: page 7–3 User Access You make your new version of the SSHR module available to your target group of users by creating an AOL function and attaching it to a 4–2 Oracle SSHR 4. For example.

See: Approvals: page 8–2 Page Layouts In most cases. However. You also need to consider whether to allow users to access people in other business groups and whether users can access additional people who may grant them access to their records using the Release Employee Information function. See: Self–Service Workflows: page 6–2 Approvals You must decide whether changes that users make using your modified function are subject to approval and who the approvers are. or Oracle Approvals Management to control transaction approvals. You specify whether the AOL function is restricted to the employee’s own records or whether a manager can use the function to select from a list of employees. Configuring SSHR 4–3 . PL/SQL. display selected flexfield segments. you could change the field prompts to match terminology used by your enterprise. For each responsibility (or combination of responsibility and user). the predefined page layouts contain all the fields that users need to perform a transaction. You modify page layouts using the Personalization Framework. A typical subset would be all employees in a specific organization or all employees reporting to the current user. and hide fields or sections of web pages. a subset of a business group. For example. you may decide that some changes are required. You can also add more detailed instructions to the web pages.menu. You can either use the Workflow Builder. The menu is attached to a responsibility which you assign to your users. See: User Access and Security: page 5–2 Process Flows If the SSHR modules are workflow–enabled (see: Summary of SSHR Modules table: page 1–7). For example. you need to define a security profile to restrict the user to an appropriate business group and. you can chain two modules together (where permitted) or introduce additional branching logic. you can choose to modify the predefined process flow if required. if required.

tip.2 Implementation Guide .See: The Personalization Framework: page 7–2 Module–specific Configuration Options Detailed information on the configuration options for each module is given in the corresponding sections. Each section contains the following information: • • • • menu and function names workflow process names and attributes region. and instruction names profile options 4–4 Oracle SSHR 4.

CHAPTER 5 Managing User Access Managing User Access 5–1 .

which information they can access. Reporting and System Administration in Oracle HRMS) See: Oracle Applications System Administrator’s User Guide User Access to People The primary users of SSHR can be divided into two main groups: managers and employees (non–managers).User Access and Security SSHR uses the same security mechanisms as Oracle HRMS applications.2 Implementation Guide . Reporting. By defining user profiles. 5–2 Oracle SSHR 4. and how they access it. make sure they are available from Oracle Self–Service Web Applications. responsibilities. See: Responsibilities (Configuring. You define responsibilities in the same way as you define responsibilities for Oracle HRMS applications. Note: When you define your responsibilities. Managers Managers can process the records for other employees after selecting them from the People Search page. you can control who uses SSHR. and System Administration in Oracle HRMS) The purpose of this chapter is to identify the key concepts relating to SSHR user access and security and to provide information on how to apply these concepts to address the needs of your enterprise. See: Security Overview (Configuring. Person Search The Person Search page contains several tabs which are defined by the Employee’s Menu menu. Employees (non–managers) Employees can only access their own employee records. and menu structures. Responsibilities A responsibility combines low–level elements of user access configuration to control which functions the user can access (User Access to Functions) and on whom they can perform these actions (see User Access to People). security profiles.

For example. Note: You can extend the security profile for managers by enabling the Release Employee Information function. you can hide the Person Search function so that managers can only process the records for the employees displayed in their hierarchy.Hierarchy This page presents a hierarchical view of the employees reporting to the current user. The view is based on the supervisor hierarchy. See: Security Profiles (Configuring. you can apply the Cross Business Group profile option to enable managers to search for employees across business groups. Managing User Access 5–3 . My List This page contains a user–defined list of people for quick reference. For example. Reporting and System Administration in Oracle HRMS) Security Profiles SSHR uses security profiles to control a user’s access to employee records. Configuration Options You can control user access to the People Search functions by excluding certain functions if required. See: User Profiles (Configuring. See: Release Employee Information: page 9–13 The manager can process employees in the list directly or add them to My List for future reference. Search (Basic and Advanced Search) This page enables a manager to search for any employee within the underlying security profile. for example. Reporting and System Administration in Oracle HRMS) Employees (non–managers) You can use the default View All security profile for the corresponding business group for the employee (non–manager) responsibilities because the employee functions restrict the user to accessing only their own record. a security profile can give a manager access to the records for all the employees in the department. See: Defining User Access and Menus: page 5–12 You can also control how managers search for employees by assigning profile options.

you must create suitable security profiles.2 Implementation Guide . be restricted by HRMS security 5–4 Oracle SSHR 4. you can choose to disable the Search functions for an SSHR manager responsibility. and non–primary supervisors to perform any task on any employee’s assignment. imagine that an employee wants to transfer to another organization. this manager may be outside the employee’s current business group and would therefore. If you are using supervisor–based security profile. flag the Restrict by Supervisor check box in the Security Profile window. With this function. To activate supervisor–based security.Managers If you allow your managers to access the Search functions. Release Employee Information You can supplement the list of people who appear in a security profile by enabling the Release Employee Information function. If the HR: Allow Selection of Assignments security profile is set to Yes. The new manager may need to review the employee’s absence history before the transfer can take place. However. managers can only view and update primary assignments. the most appropriate security profile is a user–based profile with the Supervisor Hierarchy check box flagged. Note: You can also use the Primary Assignments Only checkbox to restrict managers to viewing and updating primary assignment information only. you can use the HR: Allow Selection of Assignments system profile to control whether a manager can view and update multiple assignments for an employee. See: Defining a Security Profile (Configuring. For most SSHR managers. Similarly. Supervisor–based security allows you to set up a single security profile and use it for multiple users. This security profile dynamically generates the list of available employees based on the supervisor hierarchy (starting with the current user). In this case. If the HR: Allow Selection of Assignments security profile is set to No. You can use the supervisor based security with the HR: Allow Selection of Assignments to limit primary supervisors to perform any task on an employee’s primary assignment. To illustrate a typical use of this function. users can allow other users (who are outside of the security profile) to access their records. managers can view and update multiple assignments for an employee. Reporting and System Administration in Oracle HRMS) Alternatively. managers can use the Release Employee Information to allow a second manager (who is outside of the security profile) to access the records for one of their employees. you can assign the View All security profile to the users.

Navigation paths The traditional navigation path for SSHR users is to select a function. To do this. Personal Information or Change Manager. See: Release Employee Information: page 9–13 User Access to Functions You control user access to specific functions using function security. However. This enables the manager to view the employee’s absence history. With the Release Employee Information function. disable the ”Allow Granted Access” check box for the main security profile and enable the check box for a separate security profile with a reduced set of functions. The manager cannot access the employee’s data from a Person Search because of the defined security profiles. the employee granting access can search for the manager’s name across all organizations and business groups and grant access to that person. for example. directly from a user menu. SSHR displays a context–sensitive list of available functions. Manager Views is associated with a security profile which has the ”Allow Granted Access” check box flagged. Functions are attached to menus which are then attached to responsibilities. Personal Actions Managing User Access 5–5 . Alternatively. you can simply enable the ”Allow Granted Access” option on the security profile they use with their main Manager Self Service responsibility. SSHR 4. Accessing functions from the Actions pages: Instead of selecting a specific function from the menu.access. you must ensure that the manager has a responsibility that satisfies the following conditions: • • includes appropriate manager functions. If you want managers in your enterprise to have the same privileges for granted employees as for other employees who work for them. For example. for example.2 continues to support this approach but also introduces a new navigation path which uses the Actions pages. the user selects either the Personal Actions function (for employees) or the Manager Actions function (for managers). you may restrict managers to selected views and not allow them to use functions such as Termination. you may choose to limit managers’ capabilities with respect to granted employees.

Note: Data security is checked after the user has selected a function. they are taken directly to the corresponding web page for the function. an error message is displayed. they are first presented with the Person Search page.The Personal Actions page consists of several tabs which are defined by the Employee Enter Process hidden submenu. If the function is specific to a legislation other than the legislation to which the selected employee belongs. See: SSHR Menus: page 5–9 See: Actions Page: page 9–8 The My Actions tab displays a list of available functions for the employee. Note: If the manager first selected their own record.2 Implementation Guide . Other Employees When a user selects an employee function directly from the menu. they can select an employee for processing. Manager Actions The Manager Actions page consists of several tabs which are defined by the Manager Enter Process hidden submenu. From this page. See:SSHR Menus: page 5–9 See: Actions Page: page 9–8 The Employee Actions tab displays a list of functions available for the employee selected in the Employees tab. If the function is specific to a legislation other than the 5–6 Oracle SSHR 4. SSHR derives the list of functions by taking the submenu defined in the HR:Manager Actions Menu profile option and excluding any legislation–specific functions that do not match the legislation code of the selected employee’s business group. Accessing functions directly from a menu: Managers When a user selects a manager function directly from the menu. Note: Data security starts after the user has selected an employee. SSHR takes the submenu defined in the HR:Personal Actions Menu profile option and excludes any legislation–specific functions that do match the legislation code of the user’s business group. the submenu is derived using the HR:Personal Actions Menu profile option. To generate this context–sensitive list. The user is then taken to the corresponding web page for the function.

For example. In addition to the data security menus that are available for predefined functions. The data security grants are already in place. Legislation–specific Functions Most SSHR functions are global and can be used on employees in any legislation.legislation to which the user belongs. the correct employee records would only be displayed in SSHR if the user’s name is entered in the Person field. See: Users Window (Oracle Applications System Administration Guide) However. See: Responsibilities (Oracle HRMS Applications User Guide) Managing User Access 5–7 . an error message is displayed. Data security grants have been predefined associating each data security menu with the appropriate legislation code (or with all legislation codes in the case of the global menu). there is a similar set of data security menus to which you can attach your custom functions. There is one data security menu for global functions and one for each legislation code. The predefined functions are associated with either the global data security menu or with one or more of the country–specific data security menus as appropriate. It ensures that the user name is linked to the correct employee records. See: Data Security Menus: page 5–10 Users and Responsibilities You define SSHR users in the same way as you define users for Oracle HRMS applications. some functions are legislation–specific and must be restricted to employees in the corresponding legislation. For example. The effect of each grant is to enable the functions attached to the corresponding data security menu for people in business groups having the corresponding legislation code. if you were to create a user and assign an SSHR responsibility to this user. However. the Person field of the Users window is particularly important for SSHR as it acts as the link between the professional forms interface and SSHR. SSHR uses FND Data Security to enforce this restriction. a function on the global data security menu may be used with any employee but a function that is only on the US data security menu may be used only with employees in a US business group. A data security object has been defined on the combination of person and legislation and data security menus have been created for predefined functions.

You can enable the New User Registration functions for both employees and non–employees. you could restrict employee access to the Termination function by only including it in the Manager menu. application level. The non–employee registration form is usually used in conjunction with Advanced Benefits. For example. You can set profile options at site level. See: User Profiles (Configuring. The individual profile options are specified in the sections on each module. Reporting and System Administration in Oracle HRMS) User Access to Functions Manager and Employee Functions You can control which functions employees and managers can access by adding or removing functions from the user menus.New User Registration The New User Registration functions enable new users to register their own details and create their own users for SSHR. See: New User Registration: page 9–18 User Profiles You apply user profiles to control how the SSHR application runs. responsibility level. and user level. See: Defining User Access and Menus: page 5–12 5–8 Oracle SSHR 4. You can also add a user hook which generates the user name when the user clicks a button on the web page.2 Implementation Guide .

the Professional Details functions are grouped together in the Manager Professional Details submenu.0 menu. hidden submenus. The predefined menus are overwritten whenever an SSHR patch is applied so any changes you have made to the menus are lost. Note: You can avoid having to configure several similar menus by adding all employee and manager functions to each of your menus and then defining menu exclusions against the responsibility to exclude specific functions from groups of users. The following section looks at each of these menus in detail. For this reason. The following hidden submenus are predefined for SSHR: • • Manager Enter Process Manager Actions Menu Managing User Access 5–9 . See: Defining User Access and Menus: page 5–12 Submenus Submenus group together functions in a logical group on the top–level menu. For example. you can assign functions to the responsibility but hide them from the user. See: Defining Menus for SSHR: page 5–12 Types of Menus Top–level Menus The top–level menus define the choices that the user sees on their menu when they log in to SSHR. you should create at least one top–level menu for employees and at least one for managers. the top–level menu for the Employee Self–Service responsibility is the Employee Self Service V4. This means that the user cannot select these functions directly.Self–Service Menus and User Access SSHR uses four types of menu: top–level menus. The predefined submenus for SSHR include: • • Manager Professional Details Benefits Self–Service Hidden Submenus By attaching a submenu to the top–level menu without defining a prompt. for example. and data security menus. submenus.

This menu also controls which functions are available from the Actions page when the manager selects their own record.• Personal Actions Menu SSHR uses these submenus to determine the availability of functions in other places. Data Security Menus SSHR uses the data security menus to determine which functions are global and which are for specific legislations. For example. you need to add the following submenus to your new menu: • • Employee Enter Process Menu (or your configured copy of this menu) Personal Actions Menu (or your configured copy of this menu) Personal Actions V4.0 (or your configured copy of this menu) You must also add the following functions to your new menu: • 5–10 Oracle SSHR 4. The Personal Actions menu controls which functions are available to a user on the Personal Actions page. the Manager Enter Process submenu controls the tabbed regions appearing on the Manager Enter Process page. The data security menus for SSHR are: • HR_GLOBAL_SS_FUNCTIONS_SEED Contains all the functions that are accessible across legislations (global functions) • HR_cc_SS_FUNCTIONS_SEED (where cc is legislation code) Contains all the functions that are specific to a legislation HR_GLOBAL_SS_FUNCTIONS_CUSTOM Contains customer functions that are accessible across legislations • • HR_cc_SS_FUNCTIONS_CUSTOM (where cc is the legislation code) Contains customer functions that are specific to a legislation See: Legislation–specific Functions: page 5–7 Menus for Employees (Non–Managers) If you create a new Employee menu and want to use the Personal Actions functionality. The Manager Actions menu controls which functions are available on the Actions page for a manager to perform on other employees.2 Implementation Guide .

0 You must also make sure that the value for the HR:Personal Actions Menu profile option for any responsibilities that use the new employee menu to match the names of the personal actions submenus you selected above.0 You must also make sure that the values for the HR:Manager Actions Menu and HR:Personal Actions Menu profile options for any responsibilities that use the new manager menu to match the names of the manager actions and personal actions submenus you selected above. Menus for Managers If you create a new Manager menu and want to use the Manager Actions functions.• Suspended Actions V4.0 (or your configured copy of the function) Suspended Actions Mgr V4. Managing User Access 5–11 . you need to add the following submenus to your new menu: • • • Manager Enter Process Menu (or your configured copy of this menu) Personal Actions Menu (or your configured copy of this menu) Manager Actions Menu (or your configured copy of this menu) You must also add the following functions to your new menu: • • Manager Actions Tree View V4.

Create your own menu based on the predefined menus. Make sure that all the functions you require are listed in the Function column of your menu.Defining Menus for SSHR The predefined self–service responsibilities are linked to a menu that contains a number of functions. You configure menus in the Menus window. Make sure that the following functions are attached to your custom menu: • • • Personal Actions V4. See: Self–Service Responsibilities and User Menus: page 1–23 See: User’s Menu (Oracle Applications System Administrator’s Guide) 2. add or remove functions so that the menus accurately reflect your organization’s structures and business processes. 5–12 Oracle SSHR 4. We recommend that you create a menu based on the predefined menus and. Make sure the following submenus are attached to your custom menu: • • • Employee Enter Process menu – for employee and manager menus Personal Actions menu – for employee and manager menus Manager Actions menu – for manager menus 5.0 (or a configured copy) – for manager menus Suspended Actions – for employee and manager menus 6.0 (or a configured copy) – for employee menus Manager Actions V4. You can base your configuration on the sample menus provided although you should not change the predefined menus directly. Save your work. Decide which functions you want to include in your user menus. 4.2 Implementation Guide . if necessary. " To set up menus for self–service: 1. Review the sample functions in the Employee Self–Service User Menu and the Manager Self–Service User Menu. 3.

" To define a responsibility for a self–service application: 1. 3.Defining User Access to Self–Service Functions To define user access to self–service functions. The following process takes you through the separate procedures. We recommend that you create a different responsibility for each target group of users. Define your responsibilities to be available from Oracle Self–Service Web Applications. and assign a menu to the responsibility. If Security Groups are not enabled. use the System Profile Values window to link your responsibility to a security profile in the appropriate Business Group. Set the system profiles for security groups. 2. See: Defining a Responsibility (Oracle Applications System Administration Guide) 2. Follow the standard procedure for creating a responsibility. assign profile values. you need to define a user. • • • HR: Security Profile HR:Cross Business Group (if you want users to be able to select employees from different business groups in lists of values) HR:Restrict Transactions across Business Groups in SSHR (if you want to stop your users from performing transactions on employees from different business groups. This profile option works together with the HR:Cross Business Group profile option). Note: Self–Service Benefits users: If you do not link your responsibility to your business group using the HR:Security Profile. assign a responsibility. Set any additional required profiles. any benefits participants who attempt to enroll will receive an error message indicating that they cannot enroll. Consider whether you should create menu or function exclusions to restrict the employee menus. you can set the security profile at the user level using the Assign Security Profiles window. If Security Groups are enabled. HR:Personal Actions Menu (for SSHR) • Managing User Access 5–13 . " To set your system profiles: 1.

" To define a user: 1. Define the people you would like to access Self–Service. you can set up concurrent programs to automate this manual process.• HR: Manager Actions Menu (for SSHR) Note: You need to restart the Apache listener after changing profile options. There are two ways to do this.2 Implementation Guide . See: Users Window (Oracle Applications System Administrator’s Guide) Alternatively. You can follow the typical steps for defining a new user and then assign each individual user to a responsibility that enables access to self–service benefits. See: Creating Batch User Accounts with Concurrent Programs: page 5–20 5–14 Oracle SSHR 4.

4.jsp?akRegionCode=HR_CREATE_PROCESS_TOP_SS&akRegio nApplicationId=800&OAFunc=HR_PERINFO_SS. for example. See: Self–Service Workflows: page 6–2 5. In the Parameter field. whether it is available from the Actions pages or from the People Search pages. Leave this value unchanged but change the pProcessName parameter from HR_PERSONAL_INFO_JSP_PRC to the name of your configured process. see Configuring Workflow Objects: page 6–5 You create the function in the Form Functions window using the system administrator responsibility. " To create a function based on a predefined SSHR function: 1. If you are using Oracle Approvals Management (OAM) for your function. press Shift and F5 to duplicate the field value from the record above.0 (HR_PERINFO_SS). You can then configure how the function is accessed. Query the function on which you want to base your function. In each field. Note: The Function Name and User Function Name fields must be unique so insert your standard prefix in front of the value duplicated from the previous record. note that the pItemType parameter value is ’HRSSA’ (the internal name for the predefined HR workflow item type). for example. For information on modifying the related workflow processes. Move from field to field in the new record using the tab key. Change the OAFunc parameter to your configured function name. Managing User Access 5–15 . Insert a new record beneath it in the table. you can create your own SSHR functions using the predefined functions as a basis. 3.Defining Functions for SSHR If required. 2. Personal Information V4. add the following parameters: • • pAMETranType=SSHRMS pAMEAppId=800 See: Configuring SSHR Functions to Use Oracle Approvals Management (OAM): page 8–11 6. Note that the HTML call field is OA.

If this function is appropriate for employees to perform on themselves. Note: You do not need to enter a prompt for the function. If this function is appropriate for managers to perform on other employees. Insert a new record beneath it. 2. Model your matching function on the corresponding predefined manager function.0 menu.2 Implementation Guide . Otherwise. Personal Information Manager V4. Add the function to the top–level menus and/or submenus as appropriate. Use the system administration responsibility to display the Menus window. Save your work. 2. 2. 1." To make the function available globally or for specific legislations: 1. you may want to add the function to your configured copy of the Employee Self–Service V4. make sure that the Granted check box is unchecked. Query the predefined manager function on which you want to base your function. add it to the HR_GLOBAL_SS_FUNCTIONS_CUSTOM data security menu. add it to your configured copy of the Personal Actions menu. you need to create a matching function. 2. 5–16 Oracle SSHR 4. You create your matching function in the Form Functions window. See: Defining Menus for SSHR: page 5–12 " To make a function available from the Actions pages: 1. add it to your configured copy of the Manager Actions menu. add it to the appropriate HR_cc_SS_FUNCTIONS_CUSTOM data security menu.0 (HR_PERINFO_MGR_SS). If this function is for a specific legislation. Note: You only add the employee version of the function to the Manager Actions menu. For example. " To add the function to an employee menu in the Menus window: 1. " To make a function available from the Manager menus via the People Search page: To make this function available to managers directly from the menu via the People Search page. for example. Also.

Managing User Access 5–17 . change the pCalledFrom parameter to match the name of your original custom function (as created in the above procedure) The HTML call field is OA. Move from field to field in the new record using the tab key. When the user selects a person from this page. Note: There is no need to add this type of function to the data security menus or to the actions menus. In each field. 5. appending the selected person_id to the pPersonID parameter specified for that function. 4.jsp?akRegionCode=HR_PERSON_TREE_TOP_SS&akRegionA pplicationId=800. Add the function to the top–level menus and/or submenus as required. Insert your standard prefix where required. Save your work. SSHR calls the AOL function specified by the pCalledFrom parameter. In the Parameter field. This corresponds to the Person Search page.3. press Shift and F5 to duplicate the field value from the record above. 6.

email ID JSMITH associated with the Manager Self Service responsibility could be JSMITH_MSS. If you create a template responsibility. for managing new hire user accounts. The creation or deletion of these user accounts can often be time consuming. if you create a security profile. you can code a new responsibility created by the 5–18 Oracle SSHR 4. A naming convention you might use is email ID with a responsibility name. you can assign the security profile to a new responsibility that is created for a user in the batch process. or for managing accounts for terminated employees. A set of concurrent programs have been created for Oracle HRMS applications to automate the creation and management of large groups of user accounts. the SEC_PF security profile could be JSMITH_MSS_SEC_PF. you must write custom logic to reflect your enterprise’s unique business rules. or use the predefined Manager Self Service responsibility. This is for Oracle HRMS Applications only. password and responsibility. These programs are particularly useful if you have to create a large number of user accounts at initial installation. You can find sample user hook code in the following package: • $PER_TOP/patch/115/sql/hrhksmpl. in Oracle HRMS. For example. You can create a template responsibility for the batch process.pkb Features of the Create Batch Users Process The create batch users process only creates new responsibilities or profile option values for the new responsibility you create in the batch. However. a responsibility and a security profile. particularly if you are restricting a user’s access with a responsibility associated with a security profile and a menu. If you have set up security profiles for managers in Oracle HRMS you can associate the security profile name to a user. A user hook in the hr_user_acct_api is provided for you to do this.2 Implementation Guide . The batch process does not create security profiles either. The batch process does not create security attributes for a responsibility or a user. For example. The concurrent programs are: • • • User Account Employee Extract Process Data Pump Engine Data Pump Batch Exceptions Report Before you can use the concurrent programs however.Batch Creation of User Accounts Every Oracle HRMS user needs to be registered with a user name.

by setting values in the communication area. You can then overwrite the template responsibilities attributes. Managing User Access 5–19 .user hook to inherit the template responsibilities attributes. hr_user_acct_utility. of the API.

See: Data Pump Engine 3. Run Data Pump Engine This program uses the batch from the employee extract process and calls the HR API to create or deactivate user accounts. The extracted employee records are written to the HR_PUMP_BATCH_LINES table.Creating Batch User Accounts with Concurrent Programs To create batches of users you must first write user hooks with your own custom logic.2 Implementation Guide . See: User Account Employee Extract Process 2. you can run a set of concurrent programs to manage the batch creation of users on an ongoing basis. You run the concurrent programs from the Submit Requests window. The Data Pump Engine calls the hr_user_acct_api to create or deactivate user accounts. the Data Pump generates a view on the HR_PUMP_BATCH_LINES table to reflect the parameters of the API. Run the User Account Employee Extract Process This program extracts employee records and creates a batch file of user accounts to be created or deactivated. The specific views tailored for the hr_user_acct_api are: • hrdpv_create_user_acct Records for creating new user accounts can be mapped to this database view 5–20 Oracle SSHR 4. When you have created user hooks. The batch line table has defined generic attributes but for each API. Submit Data Pump Batch Exceptions Report This program reports errors in the Data Pump Engine. The batch name is written to the HR_PUMP_BATCH_HEADERS table. See: Data Pump Batch Exceptions Report User Account Employee Extract Process This extract process produces output records which are used by the Data Pump Engine. See: Writing User Hooks to Create Batch User Accounts: page 5–25. " To create batch user accounts with concurrent programs: 1.

Enter the following organization input parameters: • Organization this parameter comprises a list of all the business group organizations that the responsibility is associated with. This parameter sets the start date from which employee records are extracted • End Date defaults to SYSDATE. These parameters always take precedence and replace the values entered in the organization parameter and work together as a set. they are superceded by any values you enter in the Organization Hierarchy. and Parent Organization parameters. Access the User Account Employee Extract Process concurrent program. Note: If you enter values in the Organization parameter. • Organization Hierarchy organization hierarchy name for the responsibility’s business group. • Organization Hierarchy Version Managing User Access 5–21 .• hrdpv_update_user_acct Records for terminated employees whose user accounts are to be inactivated can be mapped to this database view Note: You must use a meaningful batch name. Enter a batch name to identify the batch. 2. For example. " To run the user account employee extract process: 1. Organization Hierarchy Version. 3. If you select an organization from the list of values. the program only extracts records from the selected organization. Enter the following date input parameters: • Start Date defaults to SYSDATE. The batch name is the only way you can identify which batch to select in the Employee Data Pump process and the Data Pump Batch Exceptions Report processes. This parameter is used in conjunction with the start date parameter to set a date range for the extraction of employee records 4. run type and date range or another parameter. This parameter contains an list of all the organizations hierarchies in the business group.

The second query selects all employees terminated between the start date and end date within the organization or organization hierarchy. • Create and Inactivate User Accounts runs two queries.2 Implementation Guide . • Create User Accounts for All Employees selects all employees as of the end date. The start date parameter will be ignored and employees terminated before the end date will not be selected either. Enter the Run Type input parameters by selecting a processing option from the list of values. within the organization or organization hierarchy. Once selected. • Parent Organization parent organization within the hierarchy. This run type is used on an ongoing basis. Selecting the parent organization will extract records from this organization and any organizations below the parent organization. 5–22 Oracle SSHR 4. the terminated employee’s user account is end dated. This parameter contains an list of the organization hierarchy versions selected in the organization hierarchy parameter.organization hierarchy version for the responsibility’s business group. This run type is used on an ongoing basis to end date terminated employee accounts within the date range. The first query selects all employees hired between the start date and end date within the organization or organization hierarchy. The processing options are: • Create User Account for New Hires selects all employees hired between the start date and end date within the organization or organization hierarchy. • Inactivate User Account for Terminated Employees selects all employees terminated between the start date and end date parameter within the organization or organization hierarchy. This run type is used on an ongoing basis. See: Concurrent Programs. This run type is used on the initial implementation and is usually used once. (Oracle Application’s System Administration Guide) 5.

A NO value will commit the data to the database if there are no errors. 2. You can access these views because the API column name is used to identify the record rather than the generic names used in the hr_pump_batch_lines table. and change them before any are committed to the database. The hrdpv_create_user_acct view has been defined to map create user accounts to the hr_pump_batch_line table. " To run the Data Pump Engine concurrent program: 1. The Data Pump Engine depends on the batch id the User Account Employee Extract process creates. Data Pump Engine The Data Pump Engine will call the hr_user_acct_api to perform data validation and loading operations. Note: You must run the User Account Employee Extract Process before you run the Data Pump Engine process. If there are errors the data will not be committed to the database and you can fix the errors and rerun the batch. Managing User Access 5–23 . Enter the following parameters: • Batch Name you must enter the same batch name as you did in the Employee Extract Process. YES or NO. The Batch Name is the only information you have to identify which batch to run • Validation Mode you can set two values. The hrdpv_update_user_acct view has been defined to map inactivate user accounts to the hr_pump_batch_line table. or related records in a batch. Access the Data Pump Engine concurrent program.Note: Each employee extracted from the database is recorded in the hr_pump_batch_line table. A YES value enables you to review errors in the batch. The employee data is recorded in the hr_pump_batch_lines table.

Oracle HRMS Data Pump (Implementing Oracle HRMS) 5–24 Oracle SSHR 4. See: Running Concurrent Processes. Oracle HRMS Data Pump (Implementing Oracle HRMS) Employee Data Pump Exceptions Report Each employee record is recorded in an individual batch line. " To run the Data Pump Batch Exceptions report: 1.DataPump will set the Line Status to one of the following values: – E – Error – C – Completed – U – Unprocessed – V – Valid See: Concurrent Programs. (Oracle Application’s System Administration Guide) See: Oracle HRMS Data Pump. You can identify which person record is in error from the person id in the exception report. Note: You must run the User Account Employee Extract Process before you run the Data Pump Engine and Data Pump Batch Exception Report processes.2 Implementation Guide . Note: You can run the Data Pump Engine and Data Pump Batch Exception Report processes in sequence. Access the Data Pump Process Exceptions Report concurrent program. The Data Pump Engine and Data Pump Batch Exception Report processes depend on the batch id the User Account Employee Extract process creates. The data pump exceptions report will show whether the error is from the batch header or batch line. (System Administrator’s Guide) See: Oracle HRMS Data Pump.

using your naming standard. Use the Define System Profile Option Value in System Administrator responsibility to set a security profile at Site or Application level. When you have defined a standard and created any security profiles or security groups you need. you can code a new responsibility created by the user hook to inherit the template responsibilities attributes. run the Security List Maintenance concurrent process. Implement security groups to manage security profiles with the Enable Security Groups profile option. This is necessary because security profile option values can be set at Responsibility or User level with the batch process. You can create a template responsibility for the batch process. If you create a template responsibility or use the predefined Manager Self–Service responsibility. Note: Before you write user hooks. or plan to create a new responsibility for use in Oracle Self–Service Web Applications.pkb To set up the prerequisites for writing user hooks: 1. This must be in the format <username/password>. you can associate more than one security profile to a single responsibility. You can find sample user hook code in the following package: • " $PER_TOP/patch/115/sql/hrhksmpl. associate the security profile and responsibility to a new user in your user hook code. You can then overwrite the template responsibility’s attributes by setting values in the communication area of the API. 3. This ensures that the security profiles work. hr_user_acct_utility. you can begin to write your user hook. You can obtain and verify the guest user account with your Database Administrator. By implementing security groups. responsibility. Note: If you plan to use security groups in a responsibility defined for use in Oracle Self–Service Web Applications. 2. Set up a guest user account in Oracle Applications by setting the GUEST USER PASSWORD profile option. Managing User Access 5–25 . you must review your employee population and create a standard user name format. and security profile for your enterprise. 4. set the Enable Security Groups profile option at the application level: Oracle Self Service Web Applications. Create a security profile in Oracle HRMS and.Writing User Hooks for the Batch Creation of User Accounts Before you write your user hook.

See: API User Hooks. Oracle HRMS Data Pump (Implementing Oracle HRMS) Tables Updated in the Batch Process The batch process inserts records into the following FND tables: • • FND_USER FND_USER_RESP_GROUPS to enable a new user to use a designated responsibility • FND_RESPONSIBILITY if new responsibilities are created in the custom user hook module for the new user • FND_RESPONSIBILITY_TL stores the translated value of responsibility name • FND_RESP_FUNCTIONS if the new responsibility has function exclusion rules • FND_PROFILE_OPTION_VALUES to set profile option values for any newly created responsibility for the user.Note: The sample user hook is called hrhksmpl. The batch process automates the functionality of the Define User Form and inserts records into the following FND tables: • • FND_USER FND_RESP_GROUPS Note: Security attributes for a user cannot be created in the batch process The batch process automates the functionality of the Define Responsibility Form and inserts records into the following FND tables: • FND_USER_RESP_GROUPS 5–26 Oracle SSHR 4. You can also find a copy of the sample in the following directory $PER_TOP/patch/115/sql. APIs in Oracle HRMS (Implementing Oracle HRMS) See: Sample Code.pkb and each code block is documented. • PER_SEC_PROFILE_ASSIGNMENTS if security groups are enabled.2 Implementation Guide .

To create batches of users you need to write PL/SQL programs in the user hooks of the following API: • hr_user_acct_api hr_user_acct_api. password. Note: You can supply passwords for the new user account or leave the API to generate a random string. The program enters these values into the global variables or record structures in hr_user_acct_utility. There are two user hook points in the create user procedure: • hr_user_acct_bk1.update_user_acct used to inactivate user accounts.create_user_acct used to create a new user hr_user_acct_api. 2. The program must save the password of the new user account to a file that can be accessed by a Managing User Access 5–27 . and profile to use when it creates a new user account for the employee in the process.create_user_acct_b before–process hook point hr_user_acct_bk1. responsibility. Write a PL/SQL program to communicate to the API the user name. Write a PL/SQL program for the after–process hook if you leave the API to generate a password. for example on termination of an employee This API contains two procedures: • • " To set up the Create User API procedure: 1.create_user_acct_a after–process hook point • Use the before–process hook for the PL/SQL program. The string will be in an 8 character alphanumeric format.• FND_RESPONSIBILITY_TL Note: Security attributes for a responsibility cannot be created in the batch process The batch process automates the functionality of the Profile Option Value Form and inserts records into the following FND table: • " FND_PROFILE_OPTION_VALUES To write batch user hooks with your own custom business logic: 1.

update_user_acct_b before process hook point hr_user_acct_bk2. See: API User Hooks (Implementing Oracle HRMS) A sample script to register and link your custom package and procedures is provided below. The API will not pick up any values from your user hook. There are two user hook points in the update user procedure: • hr_user_acct_bk2. This is necessary because the password created by the API is encrypted when it is saved to the FND_USER table in the database. Sample code DECLARE ln_api_hook_call_id NUMBER. Compile the custom package you have created after you have written your user hooks. Register and link your custom package procedures to the appropriate API user hooks when you have compiled the package. you may not need to write a user hook for this after–process hook point. 2. ln_api_hook_id NUMBER. The after process user hook point executes any extra logic after the main API validation and processing logic has successfully completed and the update process is finished.system administrator. ln_object_version_number NUMBER. " To set up the Update User API procedure: The update user API procedure is used to inactivate employees. • " To carry out the remaining steps: 1. The API end dates the employees record in the FND_USER and FND_USER_RESP_GROUPS tables and is not meant for general purpose update. You must capture the password before it is encrypted so that you can notify employees of their initial password.2 Implementation Guide . 5–28 Oracle SSHR 4.update_user_acct_a after process hook point The before process user hook point is used for your extra validation. Note: If you supply a password.

–– insert a row into HR_API_HOOK_CALLS for before process user hook custom package procedure hr_api_hook_call_api.hook_package = ’HR_USER_ACCT_BK1’ AND ahk. –– get api_hook_id for the seeded after process user hook package procedure SELECT ahk.module_name = ’CREATE_USER_ACCT’ AND ahm.api_module_id. –– your custom package name p_call_procedure => ’CREATE_USER_ACCT_B’.create_api_hook_call( p_effective_date => to_date(’02/02/2000’. p_sequence => 1.BEGIN –– get api_hook_id for the seeded before process user hook package procedure SELECT ahk.api_module_type = ’BP’ AND ahk.module_name = ’CREATE_USER_ACCT’ AND ahm. –– insert a row in HR_API_HOOK_CALLS for after process user hook custom package procedure Managing User Access 5–29 .api_module_id = ahm.hr_api_modules ahm WHERE ahm.api_hook_type = ’AP’ AND ahk.hook_package = ’HR_USER_ACCT_BK1’ AND ahk.hook_procedure = ’CREATE_USER_ACCT_A’ AND ahk. ’DD/MM/YYYY’). –– your custom package procedure name p_api_hook_call_id => ln_api_hook_call_id.hook_procedure = ’CREATE_USER_ACCT_B’ AND ahk.api_hook_type = ’BP’ AND ahk.api_hook_id INTO ln_api_hook_id FROM hr_api_hooks ahk .api_module_type = ’BP’ AND ahk. p_api_hook_call_type => ’PP’. p_object_version_number => ln_object_version_number ). p_api_hook_id => ln_api_hook_id.api_module_id. p_enabled_flag => ’Y’.hr_api_modules ahm WHERE ahm.api_hook_id INTO ln_api_hook_id FROM hr_api_hooks ahk .api_module_id = ahm. p_call_package => ’MY_USER_ACCT’.

Execute User Hook Pre–Processor When you have registered and linked your custom package procedure to the API you should execute the user hook pre–processor program.put_line(’Error in seeding user hook procedures: ’ || sqlerrm). you will need to run hrahkone.2 Implementation Guide . p_api_hook_id => ln_api_hook_id. exit. Once for the api_module_id for CREATE_USER_ACCT hook call and second for the UPDATE_USER_ACCT hook call.sql twice. You should see results similar to those below: API_MODULE_ID API_MODULE_TYPE MODULE_NAME –––––––––––––––––––––––––––––––––––––––––––––––––––––––– 383 BP CREATE_USER_ACCT 384 BP UPDATE_USER_ACCT Note: Your api_module_id will be different from the one above.sql. p_call_procedure => ’CREATE_USER_ACCT_A’. / commit. p_object_version_number => ln_object_version_number ). p_call_package => ’MY_USER_ACCT’. p_sequence => 1. However. Use your own API module id when executing hrahkone. EXCEPTION when others then dbms_output. ’DD/MM/YYYY’). p_api_hook_call_id => ln_api_hook_call_id. 5–30 Oracle SSHR 4.create_api_hook_call( p_effective_date => to_date(’02/02/2000’.api_module_type . To find the internal api_module_id you should run the script below: SELECT api_module_id . END. p_enabled_flag => ’Y’. If you have a customer package for UPDATE_USER_ACCT hook point.sql found in $PER_TOP/patch/115/sql directory to do this.module_name FROM hr_api_modules WHERE module_package = ’HR_USER_ACCT_API’. p_api_hook_call_type => ’PP’. Run the hrahkone. you’ll need to know the internal api_module_id for the HR_USER_ACCT_API before running the script.hr_api_hook_call_api.

and fnd_user_resp_groups 4. These parameter control aspects of the Data Pump Engine process. Set the Data Pump error parameters. the engine will stop processing after 20 errors. The default value for the parameter is 20 or the chunk size. Note: You must set the MAX_ERRORS_ALLOWED parameter to see all the errors logged during the run. run the User Account Employee Extract concurrent program to create batches of extracted employees. If necessary. 7. Test the custom packages by running the following programs:. Note: You can use the Pipemon utility to help you debug your code. you can rerun the batch after fixing any errors. Run the Data Pump Engine concurrent program to process your batch. Ensure you have set the application level correctly if you use security groups to manage security profiles. If you do not set this parameter value. 5.3. Make sure that the Enable Security Groups profile option is Yes. in SSHR you must set the application level to Oracle Self Service Web Applications. To test. See: Oracle HRMS Data Pump (Implementing Oracle HRMS). This updates the following tables: per_sec_ profile_ assignments. Set the security profile option to the application level if you need to associate the responsibility with another HRMS application. This parameter controls how many errors are issued before the engine stops processing. Enter any new message text for the messages that you issue in your custom package when you have run the pre–processor program. See: Creating Batches of Users with Concurrent Programs: page 5–20 Managing User Access 5–31 . For example. and run the Data Pump Batch Exceptions • • • User Account Employee Extract concurrent program – to create batches of extracted employees Data Pump Engine concurrent program – to process your batch Data Pump Batch Exceptions concurrent program – to report any errors. Use an Application Developer responsibility in Oracle Applications to create your message text. 6.

2 Implementation Guide .5–32 Oracle SSHR 4.

CHAPTER 6 Configuring Process Flows Configuring Process Flows 6–1 .

an HR professional. you can include or hide the function in your user menus. see: Approvals: page 8–2 6–2 Oracle SSHR 4. See: Defining Functions for SSHR: page 5–15 This chapter describes how to use the Workflow Builder to review the delivered process flows and to configure alternative flows if desired. the employee. and to control the transaction flow between the initiating user and other users such as a manager. For more information. or an applicant. and the applicant. See: Oracle Workflow Guide (available on Metalink) SSHR uses workflow processes to combine related functions into a single transaction (for example. If necessary. The Workflows are embedded within SSHR and control the flow of information between the HR professional. the manager. you can configure different versions of the workflow processes to suit your business processes. When you have linked the workflow process to the function.2 Implementation Guide .Self–Service Workflows Oracle Self–Service Web Applications utilize the capabilities of Oracle Workflow to manage transaction flows. Approvals Processes You also use the Workflow Builder to configure your approvals processes. to add Special Information Types to Change Assignment or to Personal Information). You use the Workflow Builder to look at the delivered processes which have been designed to support typical business processes. You link a workflow process to one or more functions using the Form Functions window.

Note: We recommend that you do not change the item type directly in the database. however. the copied objects are displayed without a red tag on the icon. The absence of the red tag indicates that you can customize the objects.4 only) Previous versions of this implementation guide advised customers to make their configuration change to a copy of the delivered item type. An item type can include one or more processes and related objects. Instead. As long as you set your own access level to 100 or (higher) while working on changes.4 only) HR Standard (HRSTAND) (for SSHR 3. Make the changes to this file and then upload it to the server. Workflow processes that have been implemented using this approach will still be supported. and messages. download the item type to a . you should make your changes to the delivered item type using the approach described below. the access protection ensures that when an upgrade takes place. See: Opening and Saving Item Types (Oracle Workflow Guide Release 2. The original objects have a red tag. Configuring Process Flows 6–3 . You update the workflow item type in the Workflow Builder. Note: If you copy workflow objects and change the access level to 100. such as item attributes. Oracle SSHR delivers a number of predefined workflow item types containing workflow processes that you can work with.Workflow Objects and Item Types In Oracle Workflow. functions.wft file which you then source control.6. for new configurations.1) Workflow Access Levels: The access protection levels ensure that your customizations are preserved during an upgrade. all processes are associated with an item type. the ”read–only” objects are updated and that customizations made to the ”customizable” objects are preserved. • • • • HR (HRSSA) HR Self–Service Benefits HR Offer Letter (HR_OFFER) (for SSHR 3. The new approach utilizes Oracle Workflow’s access level features for preserving customizations. 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.

2 Implementation Guide . The customization level of a customizable object is set to the user’s access level at the time when the user customized the object.The following table shows typical settings for workflow objects within the HRSSA item type. Most Objects (Default) Customizable Objects (as delivered) Customizable Objects (after changes) Protection level Lock at this level Customization level Preserve customizations 20 Yes 20 No 1000 No 20 Yes 1000 No 100 Yes See: Overview of Workflow Access Protection (Oracle Applications Workflow Guide) 6–4 Oracle SSHR 4.

Open WorkFlow Builder. are ”read–only”. Select and display the Human Resources Self–Service Applications item type or the HR Self–Service Benefits item type. See: Copying Workflow Processes 5. 3. 3. See: Workflow Objects and Item Types: page 6–3 5.Configuring Workflow Objects " Before you make changes to workflow objects: 1. create copies of the read–only objects. change any configurable item attributes. Save your work. 2. Configuring Process Flows 6–5 . Open WorkFlow Builder. 6. Note: We recommend that you maintain source control for the . You can change the ”customizable” attributes directly in the workflow process. Set the Access Level to 100. Save it to a local file for backup. and lookup types. See: Defining Your Enterprise’s Email Addresses: page 6–9 See: Configuring Approvals with the Workflow Builder: page 8–8 4. messages. 2.wft files so that you can track changes to the original objects. If required. " To modify delivered workflow objects: 1. and revert to previous versions if necessary. In SSHR item types. move definitions to other database instances using the Workflow Loader. such as processes. Select and display the Human Resources Self–Service Applications item type. Deselect the Allow Modifications of Customized Objects check box. Note: Some item attributes can be customized and other objects. 4. On the File Menu select Help/About Workflow Builder. the only directly configurable objects are item–level attributes (including enterprise e–mail addresses) and dynamic approval levels. Ensure that you are using a version of Workflow Builder that is compatible with the version of Oracle Workflow installed on your server. notifications. If required.

See: Defining Functions for SSHR: page 5–15 3. you will have to insert your copy of the subprocess into your copy of the higher level process in place of the original subprocess. Create at least one function to point to the new process. 4. " After applying a patch: During the application of an SSHR patch. Refer to the patch readme file for instructions. 5. for example. This upload overwrites any ”read–only” objects but preserves any customizations that have been made to ”customizable” objects. If you have copied (and modified) a subprocess. Note: Prefix your copies with a consistent code. you need to apply the same changes to your copied objects. Save your work. the workflow loader utility ensures that your server has the latest versions of any delivered workflow objects. Copy the object and rename it. 6–6 Oracle SSHR 4. a consistent numeral or a four–letter acronym for the company. If a patch includes new features or bug fixes for delivered objects that you have copied. you would have to copy the overall process (Personal Information) and the subprocesses (Process Basic Details and Process Personal Information). You may have to copy multiple levels of the process. For example.Copying Workflow Processes " To copy a workflow process: 1. Make sure the new process has the same item type as the original process. You may have to compare your copied object with the original read–only object. you can copy the FYI Notification Process (FYI_NOTIFICATION_PRC) for use with Self–Service Benefits Enrollments.2 Implementation Guide . 2. to make changes to the Basic Details subprocess within the Personal Information process. for example.

7. For information on the attributes that are relevant for each process. 8. first make a copy of the process. Click OK and save your work. Open the Human Resources Self–Service Applications Item Type or the HR Self–Service Benefits Item Type depending on which Item Type you want to modify.Configuring Workflow Attribute Values Workflow attribute values are the values for item types. Double–click an activity in the Process window to open the Control Properties window. They are variables that can be set by the application that maintains the item. create a copy of the workflow process you want to modify. Double–click the process you want to modify. See: Workflow Objects and Item Types: page 6–3 4. see the function–specific documentation. Configuring Process Flows 6–7 . 6. You configure workflow attributes in the Workflow Builder. 5. This opens the Process window. Open Workflow Builder. See: Self–Service Workflows: page 6–2 " To configure workflow attributes: 1. Choose the Node Attributes Tab and select a value name. 3. If you want to modify a predefined process. Edit any values defined in a procedure in the Value drop down list. 2. If necessary.

" To configure a workflow error process: 1. Change the text of the error message by editing the Self–Service HR System Error Message: • HR_SYSTEM_ERROR_MSG 3. 6–8 Oracle SSHR 4. The process sends a notification and a description to the System Administrator’s ID. The process runs when a system error occurs. Save your work.Configuring Workflow Error Processes Every workflow–enabled function has an error process. Edit the workflow error process: • HR_STANDARD_ERROR_PRC 2.2 Implementation Guide .

" To change email addresses: 1. Open the Oracle Workflow Builder. 5. You set up the email addresses for your enterprise in the Workflow Builder.Defining Your Enterprise’s Email Addresses Email addresses of key people in your enterprise may be displayed n various pages or error messages throughout SSHR. 4. 2. Select the following attribute and enter the appropriate email address in the Default Value field: • HR Department E–mail ID Note: You configure the Training Administrator ID (if using Enroll in a Class or Cancel Enrollment) and the Recruitment Supervisor ID (if using Candidate Offers) in the Professional Forms Interface. Configuring Process Flows 6–9 . Save your work. Select Attributes. 3. Open your configured HR item type (HRSSA).

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. 2. Note: From SSHR 4. If you previously scheduled this concurrent process to run when still registered under Oracle Self–Service Web Applications. Select the item type for which you want to remove obsolete workflow runtime data. Before you run the cleanup process. 5. you must cancel the process and resubmit it using the new Complete Defunct HR Workflow Processes registered under Oracle Human Resources. Place your cursor on the Parameters field in the row for the Purge Obsolete Workflow Runtime Data process to open the Parameters window. 6. 4. if you want to purge obsolete data for the last 7 days.2 Implementation Guide . Select the persistence type of the data to be purged (Temporary or Permanent). If you leave the field blank. 8. For example. enter an item key. the process will purge obsolete data for all item types.Running the Workflow Cleanup Process The workflow cleanup process enables you to remove workflow processes that are left running if a system crashes or a user ID is disabled or removed. You run the cleanup process by running the concurrent program Complete Defunct HR Workflow Processes from the Submit Request Set window. See: Overview of Concurrent Programs and Requests (Oracle Applications System Administrator’s Guide) " To run the request set: 1. 3. enter 7. If applicable. Choose OK to close the Parameters window. Enter the number of days for which you want to run the process. 7. The process cleans up temporary tables by removing redundant transaction information. enter the name of your request set. In the Request Set field. the Complete Defunct Workflow Processes concurrent process is registered under Oracle Human Resources instead of Oracle Self–Service Web Applications. 6–10 Oracle SSHR 4.1. Place your cursor on the Parameters field in the row for the Complete Defunct HR Workflow Processes process to open the Parameters window.

9. if you want to run the cleanup process for the last 7 days. enter 7. Select the item type to be included in the process. 11. For example. 10. Choose the Submit button. Configuring Process Flows 6–11 . Enter the number of days for which you want to run the process.

2 Implementation Guide .6–12 Oracle SSHR 4.

CHAPTER 7 Configuring Page Layouts Configuring Page Layouts 7–1 .

The user then logs on to the self–service application and selects a responsibility. function. a component of the Oracle Applications (OA) Framework technology. for iRecruitment. To enable administration–level personalizations (at the localization.2 Implementation Guide . Note: Not all personalization levels may be available for your self–service application. If the profile options have been set correctly. site. organization. enables you to modify many aspects of the appearance and behavior of self–service web pages which are defined in the MDS Repository. See: Oracle Self–Service Framework Documentation (available on Metalink) Personalization Framework Hierarchy The Personalization Framework enables you to configure web pages at different levels: function. responsibility. For example. take precedence over the higher level personalizations. they will affect all users within the organization or site. The Personalization Framework provides a user–friendly interface for making changes to the definitions held in the MDS Repository. localization. organization. For example. The lower level personalizations. and responsibility levels). use only site and responsibility levels. If you make personalizations at the organization or site level. Typical administration–level personalizations include: • • • • • Creating views Changing column labels Hiding/Displaying columns Configuring tables Filtering and sorting data 7–2 Oracle SSHR 4. By clicking on these links. the system administrator must set the personalization profile options for the user in question. the user will see Personalize Region links on the web page. and user. site–level personalizations. portlet. the user can customize the page to the level defined by the system administrator.The Personalization Framework The Personalization Framework. for example. for example. user–level personalizations. site. you may want to include a particular logo in a web page for all users within a site.

0 New Hire/Applicant Hire V4.0 Change Job and Employment Terms V4. Application. Currently. For more information.0 Termination V4. Function–level personalizations Some delivered SSHR functions include function–level customizations which you cannot update or delete. you can either make the personalizations at the site or responsibility level or you can create a copy of the function and make your own personalizations accordingly. User Site. User Yes/No Yes/No No No Configuring Page Layouts 7–3 .0 Change Job V4.0 See: OA Personalization Framework and OA Extensibility Framework (available on Oracle Metalink) If you wish to modify the personalizations for one of the above functions. see the Oracle Self–Service Framework documentation which is available on Metalink.The system administrator decides whether to enable the Personalization Framework at the different levels.0 Employee Status Change V4. if you prefer to work with your own custom functions rather than the delivered functions.0 Change Cost Center and Employment Terms V4. However. the following functions include function–level personalizations: • • • • • • • • • • Change Cost Center V4.0 Transfer V4.0 Termination with Compensation V4. you should be aware that you will lose any delivered function–level personalizations See: Defining Functions for SSHR: page 5–15 See: Function–level Personalizations: page C – 2 Configurable Profile Options Profile Configurable Levels Values Default Personalize Self–Service Defn (FND_CUSTOM_OA_DEFINITION) Disable Self–Service Personal (FND_DISABLE_OA_CUSTOMIZATI ONS) Responsibility.0 Employee Terms of Employment Change V4.

Only the original definition of each self–service page will be displayed. regardless of the level at which you make the configurations. Disable Self–Service Personal If this system profile option is set to Yes.Personalize Self–Service Defn This profile option enables or disables the global Personalize URL link that appears on each self–service web application page for Admin–level customizations. the configurations you make will not be applied.2 Implementation Guide . 7–4 Oracle SSHR 4.

If required. See: Configuring Flexfields: page 7–6 6.2. 4. You configure your web pages using the Personalization Framework.2B (available on Metalink) 1.Configuring Web Pages It may sometimes be necessary to modify the predefined web page regions to suit your business requirements. Configuring Page Layouts 7–5 . 2. Make your configuration changes. you do not need to enter a customization value. 5. Navigate to the web page you want to configure. you must specify which responsibility or function is affected. If you are configuring at the responsibility or functional level. Make sure that you are using a responsibility with administration–level customization access. The Create View page is displayed. See: Oracle Self–Service Framework Version 5. Save your work. Choose the global Personalize link for the web page or the Personalize Region link for a specific region. Note: If you want to configure the page at site level. you can hide or display flexfield segments. 3.

3.2 Implementation Guide . you must manually specify the segments in the Flex Segment List. You modify and add flexfields to regions of your web pages using the Personalization Framework. Key flexfields are used to uniquely identify a record. See: Oracle Applications Flexfields (Oracle Applied Technology Guide) If the self–service function you are using has flexfields enabled. Note: It may be the case that flexfields available in the Professional User Interface are not available in SSHR. Global Data Element|New Employer|Address||US|Zip Code 4. each with its own validation rules. 7–6 Oracle SSHR 4. Descriptive flexfields add attributes to an existing object. Configure the region by choosing the Personalize Region. Leave the Flex Segment List field blank if you want to display all the segments in the flexfield. Select the region. 2. If you only want to display some of the segments. " To modify the flexfields displayed in a region: 1. although you can choose to hide the flexfields using the Personalization Framework. For a list of the available flexfields for each self–service function.Configuring Flexfields Flexfields are user–defined data structures which are provided with many of the applications database tables. However. Choose Save. You enter the segments to be displayed as follows: context1|segment1|segment||context2|segment 1 For example. please see the corresponding functional description in this Implementation Guide. they are visible to users of self–service applications by default. not all self–service functions use flexfields. Each flexfield can consist of multiple flexfield segments.

0) Which contains the following tabbed regions: • HR Views (HR_VIEWS_MENU) – Search function – HR Views Submenu (HR_VIEWS) – Employee Information View – Assignment Information View – Compensation Activity View – Termination History View • • Search function Benefits Self Service (BEN_SELF_SERVICE_BENEFITS) Which contains the following tabbed regions: • • Benefits Enrollments function Current Benefits function See also: Setting Up Self–Service Benefits Web Pages: page 17–22 Some tabbed regions include a subset of buttons. and Search buttons. Configuring Page Layouts 7–7 . For example. the Employees menu includes the Hierarchy. The following submenus contain tabbed regions: • Employee Enter Process Menu (HR_EMP_ENTERPROCESS_MENU) Which contains the following tabbed region: • Personal Actions function • Manager Enter Process Menu (HR_MGR_ENTERPROCESS_MENU) Which contains the following tabbed regions: • Employees (HR_EMPLOYEES_MENU) – Hierarchy – My List – Search • • Manager Actions function HR Professional V4. for example. The self–service Benefits functions also use tabbed regions. the Manager Actions page includes the Employees and Employee Actions tabs.Configuring Tabbed Regions Tabbed regions appear on several SSHR web pages. My List.0 Menu (HR_PROF_SELF_SERVICE_V4.

query the self–service manager responsibility.To remove buttons from display. 3. Select the function you wish to exclude in the Name column. see also: Person Tree (Hierarchy): page 9–7 7–8 Oracle SSHR 4. In the Menu Exclusions tabbed region. you exclude the functions (buttons) at responsibility level.2 Implementation Guide . In the Responsibility window. " To remove a tabbed region or button from display: You can use the following method to remove a tabbed region or button from display: Set a function exclusion at the responsibility level: 1. 4. create an exclusion with the type Function. Note: If you wish to remove the Person Tree page. 2. Save your work.

4. Configuring Page Layouts 7–9 . 4. " To create a new message text: 1. Short tips are also attached to a field. the message is displayed in a separate window. 6. 2. Save your work. Select Note as the message type. Enter the name for your message. Note: To enable configuration. • You create texts in the Messages window and add them to your region in the Personalization Framework.Adding Instructions to Web Pages You can change the predefined instructions. Save your work. Navigate to the self–service page for which you want to change the text. You can create the following texts: • • Instructions appear at the top of a region and generally give advice applicable to the whole region or page. Log on to a self–service application using a responsibility that allows configuration. search for your new instruction. Log on to the database using an Application Developer responsibility. 5. Navigate to the Messages window. however. 5. or tip. leave the Tip Type field blank. In the Tip Message Name column for the corresponding region. Long messages are attached to a field. " To add a text to a region: 1. Choose the Advanced Settings button. messages. 6. 2. 3. they are displayed underneath the field in blue. 3. select either Long Message or Short Tip. and tips attached to your Web pages to provide additional information for your users. the Personalize Self–Service profile option (FND_CUSTOM_OA_DEFINITION) must be set to Yes at the responsibility level. 7. If you are adding an instruction. When the user clicks the Information next to a field. message. Enter the application and the message text. Otherwise. Choose the Personalize Region link for the region.

Hide the Global Button bar. of the buttons from a user’s web page. Delete the functions you don’t want users to access.Configuring the Global Button Bar The Global Button Bar comprises the following buttons by default: • • • • • Return to Portal Log Off Select Preferences Email Self–Service Help Selecting a button enables a user to access the button’s function.2. See: Oracle Self–Service Framework Version 5. 4. " To configure a button on the global button bar: 1. You edit the contents of the Global Button bar in the Menus window. 2. 2.2B (available on Metalink) 7–10 Oracle SSHR 4. See: User’s Menu (Oracle Applications System Administrator’s Guide) " To remove the global button bar display: 1.2 Implementation Guide . You can configure the Global Button bar by removing any. Choose Personalize. or all. You can also rearrange the order of the buttons or use a button bar that you create. 3. Save your work. When you remove a button from display a user can no longer access the button’s functionality. Query the following Menu in the Menus window: • ICX_GLOBAL_MENU Consider which of the following functions you want your users to access with the Global Button Bar: • • • • • Return to Portal Log Off Select Preferences Email Self–Service Help 3. Navigate to the web page you want to configure.

Release 11) Configuring Page Layouts 7–11 . 3. Place the gif in the $OA_MEDIA/<Language> directory. you can overwrite the default logo with a logo of the same name or you can replace the default logo with one of your own. Save and name the logo: • • • • FNDSSCORP. Save your work.gif (log–in logo) 3.gif logo. Place the gif in the $OA_MEDIA/<Language> directory.gif (Human Resources logo) IRCBRAND. you must also copy this file to the other language locations. you must also copy this file to the other language locations. which appears in the upper left corner of the Web pages. You can do this in one of two ways. Note: If you have a multilingual install. " To overwrite the default logo with your own logo: 1. Create a logo.gif (iRecruitment logo) LOGO. 4. Overwrite the Image File Name column entry with the name of your Logo. Create a . 5. See: Web Application Dictionary (Oracle Self–Service Web Applications Implementation Manual. 2.Replacing the Default Oracle Logo You can replace the default Oracle logo. 2. Note: If you have a multilingual install. " To replace the default logo with your own logo: 1. Query each of the Web Page Regions.gif (Oracle logo) PERBRAND. with your own logo.

2 Implementation Guide .7–12 Oracle SSHR 4.

CHAPTER 8 Approvals Approvals 8–1 .

2 Implementation Guide .0 is the default behavior for modules in SSHR 4. the application fetches the next approver who then receives the approval notification. The logic checks whether the current approver is the final approver in the hierarchy. Within the approvals process. All approvals mechanisms used in SSHR follow the basic approvals loop shown below. or return the transaction for correction.0 and above. The next approver can either reject the transaction. Alternatively. If the current approver is not the final approver. you can configure the workflow processes so that the Address part of Personal Information requires approval but the Phone Numbers part does not. Approvals Process Figure 8 – 1 The Basic Approvals Loop Approvals with Correction V4.Overview of Approvals Approvals processes enable you to decide whether transactions carried out by SSHR users need approval before they are submitted to the HR tables. You can define different approval requirements for different transactions and vary the approval requirements as required. you can vary the Approvals requirements by responsibility so that records changed by employees would need approval but records changed by managers would not. the application uses 8–2 Oracle SSHR 4. For example. approve the transaction.

This is either Oracle Approvals Management (AME) or a customizable PL/SQL package.rules to generate a list of approvers for the SSHR transaction. The transaction is saved automatically when the Workflow Background Process runs. When you run the Workflow Background Process you need to set the following parameters: • • • • Item Type = HR Process Deferred = Yes Process Timeout = No Process Stuck = No See Submitting a Request in Oracle Application User’s Guide. See: Configuring Approvals: page 8–8 As part of the approvals process. Approvals 8–3 . the system profile HR:Defer Update After Approval should be set to No at User/Responsibility/Application/Site level. See: Review and Confirm: page 9–15 Defer Update After Approval By default. One part is the self–service user interface which enables the initiating manager to add additional approvers and/or notification recipients. You can also display the approvers and limit the number of approval levels. This is to prevent any delay between the final approver clicking the approve button and moving on to the next notification. If you need to modify the default behavior so that transactions are saved immediately after final approval. you can choose to enable dynamic approvals by configuring the Review activity for the workflow process in question. The second part is an application which generates the default approvers. The system administrator needs to schedule this process to run periodically as needed. the save of the SSHR transaction to the database is deferred after the final approval. The dynamic approval workflow process then sends notifications to approvers and/or notification recipients based on the approver list. The way in which the list is generated depends on the approvals mechanism you are using (see Approvals Mechanisms in SSHR). The dynamic approvals functionality works in two parts. The default approvals process also includes dynamic approvals as standard.

the customizable PL/SQL package for approvals. Reporting and System Administration in Oracle HRMS. you can choose to continue to use the customizable PL/SQL package for new functions. see: Customizing Approvals Using PL/SQL: page 8–9. even if they are modeled on SSHR version 4 functions. See: Oracle Approvals Management: page 8–5 Note: If you are an existing SSHR customer.See User Profiles in Configuring. 8–4 Oracle SSHR 4. Approvals Mechanisms in SSHR SSHR 4. or Suitability Matching. See: Configuring SSHR Functions to Use Oracle Approvals Management (AME): page 8–11 Alternatively. is still supported in this release as an alternative to AME. Succession Planning. see: Implementing Oracle Approvals Management (available on Metalink). If required. to AME. you can also link any existing custom functions that you may have based on earlier version 4 functions to OAM.2.2. Apply for a Job.2 Implementation Guide . For information on configuring and customizing the PL/SQL package and workflow activity for SSHR 4. The procedures for configuring and customizing the PL/SQL package have not changed with release 4. For more information on AME.1 uses the Oracle Approvals Management (AME) application to define and manage approval logic. Note: You cannot link SSHR version 3 functions such as Appraisals. See: Customizing Approvals Using PL/SQL: page 8–9 All delivered SSHR version 4 functions are now linked to AME. which was the default approvals mechanism in previous releases of SSHR.

• • Attribute – this is a business variable. • • For more information on the components used in AME. With AME. Approval type and approval specifications – these components define the type of approver list that is generated. If the salary is greater than a specified value. to generate a supervisor–based approver list with 5 levels. The default AME configuration consists of: • • • a single AME transaction type ’SSHRMS’ with a single condition WORKFLOW_PROCESS_NAME a single rule which requires approvals to the top of the approval hierarchy or to 10 levels above the initiator. whichever comes first. you use the following components to define your approvals processes. a particular approver list is created. or workflow process name. – this is based on the standard AME approval type ’chains of authority based on number of supervisory levels’ Approvals 8–5 . For example. For example. for example. They are associated with a transaction type for a particular application. Rules – a rule links the other components together by associating one or more conditions with the approval type and approval rule. a salary amount. a condition could look at a salary amount. you use the ’supervisory level’ approval type with the ’requires approval up to the first 5 approvers’ approval specification.Oracle Approvals Management (AME) Oracle Approvals Management (AME) is a web–based application which is integrated with Oracle Workflow and which enables you to define business rules to control your approvals processes. Default Use of OAM Configuration in SSHR Oracle SSHR delivers an AME configuration which has been designed to emulate functionality delivered in the PL/SQL package. see: Implementing Oracle Approvals Management (available on Metalink). Condition – a condition compares an attribute value with a set of allowed attribute values. user ID. The default behavior is to use a supervisor–based approvals hierarchy which is now delivered using AME rules.

or you can define a custom transaction type. see: Implementing Oracle Approvals Management (available on Metalink). Alternatively. To define a different approval level for all SSHR workflow processes: • For example. for example. ’2 approvers in supervisor chain’. For more information on the configuration options offered by AME. for example.2 Implementation Guide . to specify two approval levels: The approval level is currently defined in the rule ’SSHR Rule for at most 10 approvers in Supervisor chain’. First you create a new condition with the attribute WORKFLOW_PROCESS_NAME and enter the workflow processes which will have the different approval level as the attribute values. conditions. a manager. you could create a new rule. You would edit this default rule and change the approval level for the supervisory level approval type to ’requires approval up to the first two superiors at most’. It is relatively easy to make minor changes to the delivered AME configuration and some examples are provided below. you may add additional rules. You would add this list modification condition to your rules so that the approval chain would stop at this specified approver. To define a particular user as the final approver. or attributes within the delivered SSHRMS transaction type. conditions. or final authority (even if they are not the last person in the approval chain): • You create a List Modification Condition and specify a user. see: Implementing Oracle Approvals Management (available on Metalink). and attributes. 8–6 Oracle SSHR 4. Then you create a new rule. add the approval type for final approver and add the WORKFLOW_PROCESS_NAME condition so that this final approver rule would apply to selected processes. For more information on configuring AME rules. – Use the ’supervisory level’ approval type with the ’requires approval up to the first two superiors at most’ approval – Finally. as the final approver. attach your new condition to the rule.Configuring SSHR Approval Levels in AME To meet your business needs. ’requires approval up to the first 15 superiors at most’) in the ’supervisory level’ approval type. To define a different approval level for a specific workflow process: • • To define a new approval level (if the delivered approvals do not meet your requirements): • You create a new approval (for example.

The dynamic approvals is default behavior for SSHR functions. The manager initiating the SSHR transaction can add additional approvers to the approval chain and nominate additional notification recipients (reviewers). See: Review and Confirm: page 9–15 Menu and Function Names Not applicable Workflow The workflow details for this module are listed below: Workflow Process Display Name: Approvals Process with Correction V4. however.0 Configurable Workflow Attributes: Not applicable Configurable Tips and Instructions Not applicable Configurable Flexfields Not applicable Configurable Profile Options See: Review and Confirm: page 9–15 Approvals 8–7 .Dynamic Approvals The self–service user interface for dynamic approvals has two sections: the Approvals and Notification Recipient sections. you can disable the insert approvers/add notification recipients functionality if required by configuring the Review activity for the workflow process. The notifications would then be sent to these persons on submission and/or on approval. The SSHR user can see the path of the transaction by displaying all default approvers who will participate in the approval process.

8–8 Oracle SSHR 4. Navigate to the process you want to modify and double click to open the workflow diagram. Open the Review Page V4. you would have to copy the Process Personal Information V4. A value of 1 for example will pass the approval one level up the supervisor chain. This activates approval for your process/subprocess. if you are modifying the approvals for the Process Personal Information V4. See: Updating Workflow Objects: page 6–3 5.0 activity for your workflow process.0 process. Open the workflow item type.Configuring Approvals in the Workflow Builder If required. in other words. how many levels of approval are required. Note: The default value varies for different modules. Select the Review Page V4. meaning that the number of levels is unlimited. " To configure approvals in the Workflow Builder: 1.0 activity for your process/subprocess and set the Approval Required workflow attribute (HR_APPROVAL_REQ_FLAG) to YES.2 Implementation Guide . and the related subprocesses. Set the approval level using the Approval Level attribute (HR_DYNAMIC_APPROVAL_LEVEL). Decide how a process should pass through the entire approval chain. Note: You may have to drill down through several subprocesses until you reach the correct Review Page V4. 3. 2. 4. for example. Save your work. See: Review and Confirm: page 9–15 6. you can configure the predefined approvals processes in the Workflow Builder. You set up the approvals process using workflow attributes.0 activity. For example. 7. Note: The default number of level is 0. the Process Basic Details subprocess.0 process. Add an approval level value to the Default Value field. Make a copy of the process and any affected subprocesses.

you can customize the code to use different approvals routings or to stop at a different grade level. These functions are within the HR_APPROVAL_CUSTOM package. –– begin –– loop through each row.person_id%type . if p_forward_to_person_id = l_person_id then return(’Y’).person_id%type) return varchar2 is –– cursor csr_pa(l_effective_date in date) is select paf. else return(’N’). exception when others then return(’E’). –– l_person_id per_people_f.effective_start_date and paf.supervisor_id = paf.primary_flag = ’Y’ and l_effective_date between paf.person_id%type := null. –– function check_final_approver Approvals 8–9 . --Check_final_approver (p_forward_to_person_id in per_people_f.p_person_id in per_people_f. end loop. Make sure that your returned values are of the correct data type. end if.person_id from per_all_assignments_f paf start with paf.Customizing Approvals Using PL/SQL If necessary.person_id = p_person_id and paf.effective_start_date and paf.person_id.person_id and paf. the rows are returned in an order which makes –– the last row selected the top most node of the chain.effective_end_date. The following code shows the logic for the approval functions.primary_flag = ’Y’ and l_effective_date between paf. you can review the logic in the check_final_approver and get_next_approver functions and modify them as required. for csr in csr_pa(trunc(sysdate)) loop –– set the l_person_id variable to the row fetched l_person_id := csr.effective_end_date connect by prior paf. If required.

supervisor_id and ppf. end if. –– begin –– [CUSTOMIZE] –– open the candidate select cursor open csr_pa(trunc(sysdate). if csr_pa%notfound then –– if the cursor does not return a row then we must set the out –– parameter to null l_out_person_id := null.person_id from per_all_assignments_f paf .person_id%type) is select ppf.effective_end_date and ppf. return(l_out_person_id).primary_flag = ’Y’ and l_effective_date between paf.person_id%type) return per_people_f. end get_next_approver. –– fetch the candidate details fetch csr_pa into l_out_person_id.2 Implementation Guide . p_person_id).effective_end_date. () -Get_next_approver function get_next_approver (p_person_id in per_people_f.effective_start_date and paf.end check_final_approver.person_id%type is –– cursor csr_pa(l_effective_date in date .person_id = paf.l_in_person_id in per_people_f.person_id = l_in_person_id and paf.effective_start_date and ppf. () 8–10 Oracle SSHR 4. –– close the cursor close csr_pa.person_id%type default null.current_employee_flag = ’Y’ and l_effective_date between ppf. –– l_out_person_id per_people_f.per_people_f ppf where paf.

you should set up processes that currently do not require approval as follows: • • Set the Approvals Required workflow attribute to Yes Configure AME so that no approvers are returned Note: If you subsequently need to add approvals to your process. Query your function.1 will use the customizable PL/SQL package as the default approvals mechanism. the process completes without requiring approval. you can modify any custom SSHR 4. To add your custom workflow process to the list of values for the condition attribute for the SSHRMS AME transaction type (required if using the delivered SSHR transaction type): 1. " To link your function to AME in the Form Functions window (required): 1. " Save your work. As a general set–up recommendation. Log on to Oracle Approvals Management. You define the additional parameters in the Form Functions window. for example. If the Approvals Required workflow attribute is set to Yes for a workflow process but AME does not return any approvers. The AME rules and conditions always override any other workflow attribute settings that apply to approvals. Navigate to the Form tabbed region. 3. However. 2. the attribute settings for the Review activity.Configuring SSHR Functions to Use Oracle Approvals Management (AME) Any custom functions you created prior to release 4.0 functions to point to AME by adding two new function parameters. Note: You need to use one of the following AME responsibilities: – AME Application Administrator Approvals 8–11 . You should also check the workflow attributes for your workflow process using the Workflow Builder. you can simply use a different AME condition. Add the following parameter information to the Parameters field for your function: • • pAMETranType=SSHRMS pAMEAppId=800 4.

Note: To display the Additional Approvers/Notification Recipients page. you must select the Yes – Dynamic Approvals value. Set the Approvals Required attribute to Yes or Yes – Dynamic Approvals. Choose the Add Text Value button and enter the name of your new workflow process as an attribute value. Display the attributes for the Review function. 3. 4. 8–12 Oracle SSHR 4. Save your work. " Select the SSHRMS transaction type.2 Implementation Guide . Save your work. 5. 4. To set the Approvals Required attribute in the Workflow Builder: 1. Select the Conditions tab and click on the WORKFLOW_PROCESS_NAME condition. 3. 2. Display your function in the Workflow Builder.– AME General Business User – AME Limited Business User 2.

CHAPTER 9 Common Modules Common Modules 9–1 .

The common modules are: • • • • • • Person Tree Actions Page Multiple Assignments Release Employee Information Review and Confirm New User Registration 9–2 Oracle SSHR 4. low–level functionality used in many of the higher–level functions described in later chapters.Overview of Common SSHR Modules This chapter contains information on how to configure modules that provide common.2 Implementation Guide .

It enables managers to select an employee record for processing in SSHR.0 menu In this case. See: Navigation Paths: page 5–5 See:Defining Functions for SSHR: page 5–15 The Person Tree page consists of several tabbed regions which are defined by the Manager Enter Process hidden submenu (HR_MGR_ENTERPROCESS_MENU).Person Tree The Person Tree. When the manager selects a person from the Person Tree. the manager first selects the person from the person tree and then selects the SSHR module. • From a specific manager self–service menu item In this case. See: Menus for Managers: page 5–11 Common Modules 9–3 . The Person Tree page consists of the following nested components which are explained in detail below: • Employees region – Hierarchy nested region – My List nested region – Search nested region • Employee Actions region The format of the Person Tree page depends on the navigation path that the manager has taken. The submenu currently contains the following tabbed regions: • • Employees Employee Actions Note: You must attach the Manager Enter Process submenu to the top–level menus for all manager responsibilities. they are taken directly to the module specified by the function name passed in the pCalledFrom parameter for the manager function. There are two possible paths: • From the generic Manager Actions V4. or actions. You set the parameter pDestination to HR_ACTIONS_SS (instead of setting it to a specific function) to ensure that the page includes all actions. or hierarchy. for the selected person are displayed in a context–sensitive list. is the starting point for all manager self–service functions. the manager selects a specific module and then selects the person for processing. The modules.

If a manager has displayed the Person Tree before choosing a specific function (by choosing the Manager Actions V4. See: Data Security Menus: page 5–10 If the manager selects a specific function first and then selects a person from the Person Tree. the selection defaults to the manager’s own employee record. If a manager does not select a person in the Person Tree. If the function is not available. In this case. The list is driven by the hidden submenu defined for the HR:Manager Actions Menu profile option. The contents of the Employee Actions tab is defined by the navigation path taken by the user. if legislation restrictions apply.2 Implementation Guide . the Employee Actions tab displays a context–sensitive list of the functions available for the selected employee.Employees Tab You define which regions appear on the Employees tab by modifying the Employees Menu hidden submenu (HR_EMPLOYEES_MENU). See: Actions Page: page 9–8 9–4 Oracle SSHR 4.0 function). the Employee Actions tab only displays the preselected function. the list displayed is driven by the hidden submenu for the HR:Personal Actions Menu profile option. or hierarchy My List Person Search Note: You must attach the Employees Menu hidden submenu to the top–level menus for all manager responsibilities. for example. The Employees tab currently includes the following regions: • • • Person Tree. If required. The list of functions displayed in the Employee Actions tab is also defined by the person’s legislation code. an error message is displayed. you can hide the My List and Search tabs from responsibilities using function exclusions. The default menu for this profile option is the predefined Manager Actions Menu (HR_LINE_MANAGER_FUNCTIONS). The default menu for this profile option is the predefined Personal Actions Menu (HR_LINE_MANAGER_PERS_FUNCTIONS). See: Menus for Managers: page 5–11 Employee Actions Tab The Employee Actions tab is displayed when a manager either chooses the Manager Actions V4.0 function and selects a person or chooses a function and then selects a person.

Transactions Across Business Groups You can choose to enable your managers to see the names of employees in other business groups but to prevent them from performing any transactions on them.0 Manager Actions Tree View V4. To do this. you use the HR:Restrict Transactions Across Busienss Groups in SSHR profile option in conjunction with the existing HR:Cross Busienss Group profile. managers can see the names of employees in other business groups and perform transactions on them. the names of the employees in other business groups are disabled. If you set the HR:Cross Business Group profile to Yes. Menu and Function Names User Menu Name Function Name Manager Self Service V4. If you then set the HR:Restrict Transactions Across Business Groups in SSHR profile to Yes.0 and all manager functions See: Defining User Access and Menus: page 5–12 Workflow Not applicable Configurable Tips and Instructions Hierarchy Page Region Tip Type Message Name Person Tree Container Instruction HR_INST_HIERARCHY_TREE Common Modules 9–5 . Note: To enable multiple assignments. the profile option HR: Allow Selection of Assignments must be set to yes at the required level. you must select the relevant assignment before you carry out the employee action.Multiple Assignments If an employee has more than one assignment.

Reporting.My List Region Tip Type Message Name Enter Person My List Header Enter Person My List Header Instruction Instruction HR_INST_MY_LIST HR_INST_MY_LIST_SEARCH Person Search Page Region Tip Type Message Name Person Search Switch Basic Person Search Criteria Advanced Search Business Group Advanced Search Person Type Instruction Instruction Instruction Instruction HR_PERSON_SEARCH_GENERIC_INST HR_BASIC_SEARCH_INST_SS HR_ADV_SRCH_BUSGRP_INST_SS HR_ADV_SRCH_PERTYP_INST_SS See: Adding Instructions to Web Pages: page 7–9 Configurable Flexfields Not applicable Configurable Profile Options Profile Configurable Levels Values Default HR:Cross Business Group HR:Restrict Transactions Across Business Groups in SSHR All All Yes/No Yes/No No No See: User Profiles (Configuring.2 Implementation Guide . and System Administration in SSHR) 9–6 Oracle SSHR 4.

Common Modules 9–7 . and System Administration in Oracle HRMS) Search Page 1. 1. In the Form Functions window. hide the corresponding region in the Personalization Framework or use function exclusions to exclude the Person Search function at the responsibility level. You can configure the search criteria for the Basic and Advanced Searches. This may be necessary of you use a position–based hierarchy rather than a supervisor–based hierarchy. delete search criteria. See: Adding Lookup Types and Values (Customizing. The field contents should now be: OA. 2. 3. if necessary.Additional Configuration Steps Hierarchy Page (Person Tree) If necessary you can change the start page for manager functions from the Person Tree page to the Search page. Reporting. query a manager function (those functions ending in _MGR_SS). To prevent your users from using the Basic or Advanced Search. You can rearrange the sequence of the criteria and. change the values of the lookup type HR_HIRE_DATE.jsp?akRegionCode=HR_PERSON_TREE_TOP_SS&akRegionA pplicationId=800 My List Page 1. See: Configuring Web Pages: page 7–5 2. To configure the range of dates that users can see. Edit the field contents for the HTML call field so that the region code parameter points to the Search function instead of the Person Tree function. Display the Web HTML tabbed region.jsp?akRegionCode=HR_PERSON_SEARCH_TOP_SS&akRegio nApplicationId=800 instead of: OA.

0 Employee Self Service V4. for example.0 Manager Actions V4.0 See: Defining User Access and Menus: page 5–12 Workflow Not applicable 9–8 Oracle SSHR 4.Actions Page The Actions page displays a context–sensitive list of actions that can be performed for a selected person and suspended actions. Suspended actions can include actions that a user has saved for later submission or actions that have been returned to the initiator by an approver.0 Manager Self Service V4.0 Employee Self Service V4. See: Navigation Paths: page 5–5 The Actions page can be accessed in one of the following ways: • Managers can select an employee using one of the employee selection methods and then choose the Actions tab to display the actions relevant to the employee Managers can select the Actions tab from the Hierarchy page and display their own personal actions Employees can select the Personal Actions menu option from the Employee menu and display their personal actions • • Menu and Function Names This module can be accessed from the following menus and functions: User Menu Name Function Name Manager Self Service V4.0 Personal Actions V4.0 Suspended Actions Mgr V4.0 Suspended Actions V4.2 Implementation Guide . to be corrected.

Configurable Tips and Instructions Process People Top Page Region Tip Type Message Name Perform Employee Action SSHR Process Selected Action Region SSHR Process Selected Action Region SSHR Process List Instruction Instruction HR_INST_ACTIONS HR_INST_ACTIONS_SINGLE_SUS Instruction HR_INST_ACTIONS_SINGLE Instruction HR_INST_ACTIONS_DUAL Personal Process Top Page Region Tip Type Message Name Process People Nested Region SSHR Process Selected Action Region SSHR Process Selected Action Region SSHR Process List SSHR Process List SSHR Process List SSHR Process Suspended List SSHR Process Suspended List SSHR Process Selected Action Region Instruction Instruction HR_INST_ACTIONS HR_INST_ACTIONS_SINGLE_SUS Instruction HR_INST_ACTIONS_SINGLE Instruction Instruction Instruction Instruction Instruction Instruction HR_INST_ACTIONS_DUAL HR_INST_ACTIONS_SHOW HR_INST_ACTIONS_DUAL_NO_EFF HR_INST_ACTIONS_ON_HOLD HR_INST_ACTIONS_EDA_ON_HOLD HR_INST_ACTIONS_SINGLE_SUS See: Adding Instructions to Web Pages: page 7–9 Common Modules 9–9 .

All Validation Post Selection Manager Actions Menu Personal Actions Menu All Actions Checked See: User Profiles (Configuring. Preselected Action Checked. and System Administration in Oracle HRMS) 9–10 Oracle SSHR 4.Configurable FlexFields: Not applicable Configurable Profile Options Profile Configurable Levels Values Default HR:Manager Actions Menu HR:Personal Actions Menu HR: Actions – Validation All All All All Manager Actions menus All Personal Actions menus All Actions Checked. Reporting.2 Implementation Guide .

When the multiple assignment functionality is enabled. the person tree includes employees who report to the manager through a secondary assignment. User Yes. Menu and Function Names Not applicable Workflow Not applicable Configurable Tips and Instructions SSHR Process People Top Page Region Tip Type Message Name SSHR Asg Selection Instruction HR_INST_ASG_SELECTION See: Adding Instructions to Web Pages: page 7–9 Configurable FlexFields Not applicable Configurable Profile Options Profile Configurable Levels Values Default HR: Enable Multiple Assignments in SSHR Site. Responsibility.Multiple Assignments The multiple assignment functionality enables managers to view and update both primary and secondary assignments for an employee. No No HR: Enable Multiple Assignments in SSHR The HR: Enable Multiple Assignments in SSHR system profile enables you to control whether a manager can view and update multiple Common Modules 9–11 . You enable the functionality by setting the HR: Enable Multiple Assignments in SSHR profile to Yes. Application.

assignments for an employee. You can use the supervisor–based security profile with the HR: Enable Multiple Assignments in SSHR system profile to limit primary supervisors to perform any task on an employee’s primary assignment.2 Implementation Guide . and non–primary supervisors to perform any task on any employee’s assignment. Note: You can also use the Primary Assignments Only checkbox to restrict managers to viewing and updating primary assignment information only. managers can view and update primary and secondary assignments for an employee. 9–12 Oracle SSHR 4. managers can only view and update primary assignments. If the HR: Enable Multiple Assignments in SSHR security profile is set to Yes. If the HR: Enable Multiple Assignments in SSHR security profile is set to No.

0 See: Defining User Access and Menus: page 5–12 Workflow The workflow details for this module are listed below: Workflow Process Display Name: Release Employee Information V4.0 Release Employee Information Mgr 4.Release Employee Information The Release Employee Information function enables an employee to share information about themselves with another employee. who would not usually have access to their records. Menu and Function Names This module can be accessed from the following menus and functions: User Menu Name Function Name Manager Self Service 4. Similarly.0 Release Employee Information 4. often a manager. and System Administration in Oracle HRMS) The Release Employee Information function is available under predefined Manager and Employee responsibilities. Configuration options enable you to set up approvals processes for granting access.0 Employee Self Service V4.0 Configurable Workflow Attributes: Not applicable Configurable Tips and Instructions CAED Page Region Tip Type Message Name CAED: Grant Access to CAED Granted Employee Header Region Instruction Instruction HR_INST_CAED_GRANT_ACCESS HR_INST_CAED_EXISTING_GRANTS Common Modules 9–13 . See: Security Profiles (Configuring. Reporting. a manager can use this function to share information about one of their employees with a second manager.

Region

Tip Type

Message Name

CAED Pending Employee Header CAED Control Access To Employee Data

Instruction Instruction

HR_INST_CAED_PENDING_GRANTS HR_INST_CAED_TOP_TEXT

See: Adding Instructions to Web Pages: page 7–9

Configurable Flexfields
Not applicable

Configurable Profile Options
Not applicable
Profile Configurable Levels Values Default

HR:CROSS_BUSINE Site SS_GROUP

Yes/No

No

The Cross Business Group profile option determines whether employees from other business groups are retrieved in the employee search. See: User Profiles (Configuring, Reporting, and System Administration in Oracle HRMS)

Additional Configuration Steps
1. Configure the predefined user menus to include the Release Employee Information function. See: Defining User Access and Menus: page 5–12 2. If you want your managers to have access to employee data, ensure that the Allow Granted Access check box is flagged for the security profile assigned to the manager. This enables the manager to review the employee’s data. See: Security Profiles (Configuring, Reporting, and System Administration in Oracle HRMS)

9–14

Oracle SSHR 4.2 Implementation Guide

Review and Confirm
Most functions display the Review and Confirm pages. The Review page displays a corresponding region for each Web page section that you have updated as part of the preceding transaction. Inside each region is a list of current database and proposed transaction data. If you have configured approvals, you can enter approvals comments in this page. If you have enabled the Dynamic Approvals function, the user can see the default approval chain and add further approvers and notification recipients. When the user chooses the Submit button from the Review page, the transaction is committed to the Human Resources system or sent for approval. The Confirm page is then displayed. The Confirm page contains a confirmation message describing the status of the transaction. The user can print a copy of the submitted transaction for their records if required. You can set up the approval properties for a process by changing the activity level attributes for the Review workflow functions.

Menu and Function Names
Not applicable

Workflow
The workflow details for this module are listed below:

Workflow Process Display Name:
Common functionality which is used by all processes.

Configurable Workflow Attributes:
Process Display Name Function Activity Display Name Function Activity Attribute Display Name

Review Page V4.0 Review Page V4.0 Review Page V4.0 Review Page V4.0 Review Page V4.0

HR_DYNAMIC_APPROVAL_LEVEL HR_APPROVAL_REQUIRED_FLAG Confirm Instruction Application Short Name Confirm Save Instruction Name Confirm Send for Approval Instruction Name

Common Modules

9–15

HR_DYNAMIC_APPROVAL_LEVEL: This attribute is used to specify the number of levels to which this transaction needs to be forwarded for approval in the approval hierarchy. For example, if the value is 1, the transaction is submitted for approval to one level higher than the initiating person. When the transaction has been approved, it is committed to the HRMS application. By default, this attribute reads the approval level from the APPROVAL_LEVEL (Approval Level) item level attribute. If you specify a value for the item level attribute, you can control the approval level for all the processes. If you specify a value for the HR_DYNAMIC_APPROVAL_LEVEL attribute, it overrides the item level attribute for the process for which you have specified the value. HR_APPROVAL_REQUIRED_FLAG: This attribute is used to specify whether the current transaction requires an approval. The valid values are:
• •

No: the process does not require approval Yes: the process requires approval but the dynamic approval user interface will not be shown in the review page. This means that the initiator cannot add additional approvers or notifiers. Yes – Dynamic Approval: the process requires approval and the dynamic approval user interface will be shown in the review page. The initiator can add additional approvers and notifiers.

Confirm Instruction Application Short Name: In addition to the standard confirmation message shown in the confirmation page, you can also configure messages that are specific to the process. You can specify one for a scenario for which approval is required and one for a scenario for which no approval is required. Processes can be set to either Approval Required or Approval Not Required, but not both, using the HR_APPROVAL_REQUIRED_FLAG. For example, you can define a message for Confirm Save Instruction Name and Confirm Send for Approval Instruction Name. You register this message under your custom application. Confirm Send for Approval Instruction Name: The text associated with this message name is displayed in the confirmation page immediately after the standard confirmation message. This text is only displayed when the process does not require approval. The text associated with this message name is displayed in the confirmation page immediately after the standard confirmation

9–16

Oracle SSHR 4.2 Implementation Guide

message. This text is only displayed when the process requires approval. Note: You must copy the delivered processes and make changes to the copy. If you make changes to the delivered processes, they will be overwritten when new patches are applied to your system. See: Configuring Workflow Attribute Values: page 6–7

Configurable Tips and Instructions
Not applicable

Configurable Flexfields
Not applicable

Configurable Profile Options
Not applicable

Common Modules

9–17

New User Registration
Self–service registration for new users helps to reduce the workload and costs of HR administration. HR professionals can use this feature to add new employees to the Oracle HRMS database. The self–service approach reduces the rollout effort for large companies where the HR department is not centrally located. You can add or edit user–friendly tips and text messages in the user interface to reduce the need for end user training. You can also use self–service registration to help shift the workload from the HR department onto the hiring line manager or even the individual employees by allowing them to register their own employee details. Using the New Employee Registration function, employees log on with a generic company user name and supplied password or they access the function directly with a “guest login”, which is invisible to users. They complete online registration, giving details such as name, address, employment details, and family members. They can create their own self–service user names and passwords (or you can choose to generate these automatically). Alternatively, HR administrators or line managers can create the employee records and self–service user names for their new hires. Using the Non–employee Registration function, other people can log on to create non–employee records in Oracle HRMS. This is most commonly used by US third party benefits providers using Oracle Advanced Benefits. It enables benefits participants or their dependents who become COBRA qualified due to a life event (such as divorce or termination) to register so they can elect their COBRA coverage through self–service. Using the Create User Name function, people who already have an HR record in the database can create their own self–service user names and passwords. This function provides an alternative to the existing methods of creating users, which are using the Users window or creating self–service users in a batch.

Benefits Registration
If you have implemented Standard Benefits or Oracle Advanced Benefits, benefits participants can register directly with you through the World Wide Web or over a corporate intranet. If you are a third party benefits administrator or provider, this means that employees’ HR departments are no longer responsible for transferring HR information to your database.

9–18

Oracle SSHR 4.2 Implementation Guide

Once a person completes the registration, they can navigate directly to the Self–Service Benefits functions, which process detected life events that enable benefits elections or unrestricted program elections.

Generic Users and Responsibilities
You give a generic user name and password to people, enabling them to access self–service initially to register. You can choose how many generic user names you create. For example, a third party benefits provider is likely to create one generic user name for each subscriber organization. Employers might create one user name for the entire business group, or different names based on the organization hierarchy structure. Default Organization Each user name is associated with an organization using the profile option OAB:User to Organization Link. This defaults the organization for a new employee assignment, but the user can select another organization from the business group during registration. You can set this profile option at the responsibility level––to link each generic user name with a separate organization––or at the site, or application levels. Default Payroll Similarly, for each generic user name you can select the default payroll to be assigned, by setting the profile option OAB:User to Payroll Link at the responsibility level. You can also set this profile option at the site, or application levels. Default Responsibility By default, all newly registered users are assigned the seeded Self Registered Employee Default responsibility. This responsibility gives them access to a subset of self–service functions, such as Self–Service Benefits enrollment, person name, address, and contact information. You can create your own responsibilities and assign them to responsibilities, or the whole site by setting the OAB: Self Registered User Responsibility profile option at the appropriate level.

Common Modules

9–19

Setting Up a Generic User ID For New User Registration
Follow these steps to create the generic user name and password that will enable new employees, managers, and other users to access self–service to register themselves in your database. These steps are required if you are using any of the following processes:
• • •

New Employee Registration Non–employee Registration Create User Name

If you are implementing new user registration in more than one business group, see: Setting Up Generic User IDs in Multiple Business Groups: page 9–23. If you are implementing new user registration within a single business group, use the following procedure. If you are only implementing the Create User Name process (that is, you are using self–service to create new users but not to create HRMS records), you can omit steps 7 and 8.
"

To set up self–service registration in a single business group: 1. If you are a third party benefits provider, create an organization to represent each subscriber organization or company in which you are providing benefits. If you are not a third party benefits provider, you create your HR organization hierarchy as required within your business group. Skip the next step since it applies to third parties who administer multiple companies within a single business group. See: Creating an Organization, Using Oracle HRMS – The Fundamentals See: Adapting and Creating a New Business Group, Using Oracle HRMS – The Fundamentals 2. Third party benefits providers using Oracle Advanced Benefits only: Establish a link between your organizations and the relevant benefits program. For example, link each subscriber organization to the subscriber’s benefit program. Use the Organizations tabbed region of the Programs window. This link enables the Participation process to select the appropriate benefit programs for a particular organization when processing people within that organization. This enhances system performance by limiting the retrieval of records to the person’s organization. The process selects the programs pertaining to that organization and then examines the person’s eligibility restrictions.

9–20

Oracle SSHR 4.2 Implementation Guide

Note: Set the system profile Limit By Persons Organization to Yes to enable this feature for the Benefit Service Center window. Set the Limit to Organization parameter to limit the Participation batch process. See: Defining a Benefits Program, Managing Total Compensation Using Oracle HRMS See: Associating an Organization with a Benefits Program, Managing Total Compensation Using Oracle HRMS 3. Review the predefined New User Registration responsibility and New User Registration menu, which gives access to the New Employee Registration, Non–employee Registration and Create User Name functions in self–service. If you only need one generic user name for the business group, you can use the predefined New User Registration responsibility. Otherwise, create a copy of the New User Registration responsibility for each organization for which you will create a separate generic user name. You might want more than one responsibility for each organization. For example, you might give new employees a responsibility that gives them access to the New Employee Registration function only. You could create a second responsibility for people who already exist in the database but need to create a self–service user name and password. This would reduce errors by giving each person access to one function only. 4. Create a generic user name and password for the business group or for each organization, so that new people can log on to the Registration page. If users will log in with a guest login, create the guest user instead. For further information on guest users, see: Configuring the Create User Name Process: page 9–31. See: Users Window, Oracle Applications System Administrator’s Guide 5. Add the New User Registration responsibility (or the responsibilities you created in step 3) to the generic user name for each organization. Update the system profile HR:Business Group at the appropriate level so that the generic user name points to the business group in which the person registering belongs. Update the OAB:User to Organization Link system profile at the responsibility level to link the New User Registration responsibility (or your copies) to the organization in which the person belongs. Attention: Check to ensure that the organization you select is correct. The list of values contains all the organizations in the database. You must select an organization defined in the business group associated with the user name.

6.

7.

Common Modules

9–21

See: System Profile Values Window, Oracle Applications System Administrator’s Guide 8. Update the profile OAB User to Payroll Link at the responsibility level for the New User Registration responsibility (or your copies) to provide a default employee payroll. If this profile is blank and the employee is not assigned to a payroll, OAB processes use the benefits default payroll selected for the business group in which the person will be registered. Attention: Check to ensure that the payroll you select is correct. The list of values contains all the payrolls in the database. You must select a payroll defined in the business group associated with the user name.

Note: Oracle delivers the system profile OAB: Self Registered User Responsibility with the seeded value of Self Registered Employee Default Responsibility predefined at the site level. 9. add it to the profile OAB: Self Registered User Responsibility at the responsibility level for the New User Registration responsibility (or your copies). After entering it. The application assigns the responsibility set in the OAB:Self Registered User Responsibility profile (step 10) to the new user name. create any new self–service responsibilities you require. you gain access by using the password you created in step 4. Note: The application assigns this responsibility to users when they complete their registration.2 Implementation Guide . Log into Self–Service with the user name and password you created. change the profile OAB: Self Registered User Responsibility at the site level to point to your new responsibility. As the system administrator. The self–service menu for this seeded responsibility gives access to only a subset of employee self–service transactions. If it is not. Check whether the predefined Self Registered Employee Default responsibility is appropriate for all your organizations. This responsibility contains the New Employee Default Menu that the participant uses to access the self–service web pages after the initial registration. 9–22 Oracle SSHR 4. the first time you log into self–service. 10. If you created a different responsibility for each organization. 11. Use the New Employee Registration function to create a new person and a user name for that person. you must change the password to a generic password you want the new people to use when accessing self–service initially to register. If you created just one new responsibility in the previous step. 12.

See: Users Window. In each business group. see: Configuring the Create User Name Process: page 9–31. See: Creating an Organization. 3. which gives access to the New Employee Registration. This would reduce errors by giving each person access to one function only. You may want to create separate user names for the organizational hierarchies within each business group. Third party benefits providers: Create a business group to represent each subscriber organization or company in which you are providing benefits. You might want more than one responsibility for each business group. Add your copy of the New User Registration responsibility to the generic user name for each organization. For further information on guest users. Using Oracle HRMS – The Fundamentals See: Adapting and Creating a New Business Group. For example. Review the predefined New User Registration responsibility and New User Registration menu. Create a generic user name and password for each organization so that new people can log on to the Registration page.Setting Up Generic User IDs in Multiple Business Groups This procedure is appropriate for third party benefit providers who are creating a separate business group for each company or subscriber organization. Non–employee Registration and Create User Name functions in self–service. You could create a second responsibility for people who already exist in the database but need to create a self–service user name and password. Create a copy of the New User Registration responsibility for each business group. you might give new employees a responsibility that gives them access to the New Employee Registration function only. Using Oracle HRMS – The Fundamentals 2. Oracle Applications System Administrator’s Guide 4. create an HR organization for the subscriber. It is also appropriate for employers or third party administrators who have multiple business groups on a single database. You will need at least one generic user name for each business group. If users will log in with a guest login. " To set up self–service registration in multiple business groups: 1. Employers: Decide how many generic user names you want to create. Common Modules 9–23 . create the guest user instead.

Attention: Check to ensure that the organization you select is correct. 6. Update the system profile HR:Business Group at the appropriate level so that the generic user name points to the business group in which the person registering belongs.5. You must select an organization defined in the business group associated with the user name. The list of values contains all the organizations in the database. Update the OAB:User to Organization Link system profile at the user or responsibility level to link the New User Registration responsibility (or your copies) to the organization in which the person belongs. .

See: System Profile Values Window. If this profile is blank and the employee is not assigned to a payroll. Attention: Check to ensure that the payroll you select is correct. 7. . Oracle Applications System Administrator’s Guide Update the profile OAB User to Payroll Link at the responsibility level for the New User Registration responsibility (or your copies) to provide a default employee payroll. You must select a payroll defined in the business group associated with the user name. OAB processes use the benefits default payroll selected for the business group in which the person will be registered. The list of values contains all the payrolls in the database.

Note: The application assigns this responsibility to users when they complete their registration. Update the system profile HR:Business Group at the responsibility level to point to the correct business group. create any new self–service responsibilities you require. 9. Update the system profile OAB: Self Registered User Responsibility at the responsibility level with the name of the responsibility to use for that organization (created in step 8). 9–24 Oracle SSHR 4.2 Implementation Guide . create a copy for each organization. This responsibility contains the New Employee Default Menu that the participant uses to access the self–service web pages after the initial registration. If it is not. • • Check whether the predefined Self Registered Employee Default responsibility is appropriate for all your organizations. If it is. Note: Oracle delivers the system profile OAB: Self Registered User Responsibility with the seeded value of Self Registered Employee Default Responsibility predefined at the site level. 8.

After entering it. 10. Log into Self–Service with the user name and password you created. 11. the first time you log into self–service. The application assigns the responsibility set in the OAB:Self Registered User Responsibility profile (step 9) to the new user name. As the system administrator. you gain access by using the password you created in step 3. Use the New Employee Registration function to create a new person and a user name for that person. Common Modules 9–25 .The self–service menu for this seeded responsibility gives access to only a subset of employee self–service transactions. you must change the password to the generic password you want new people to use when accessing self–service initially to register.

and additional employment information. Users enter marital status. job. people group. for New Employee process (not in non– employee process) 9–26 Oracle SSHR 4. and a legal agreement that users must agree to before proceeding. the following pages: Page Introduction Required? No Purpose This page includes a checklist of information that new users must have when entering their registration. The New Employee Registration process displays the pages for new employees to create HR records and self–service user names for themselves. position. These processes include. This page has the user enter minimal information about themselves. by default. payroll. The Non–employee Registration process creates person records in the HRMS system for people who are not employees. Employees can fill in information about their organization. Users can enter the phone numbers they require.2 Implementation Guide . Verification No Basic Details Main Address Phone Numbers Assignment Yes Yes No Yes. Users can enter a primary address and two other addresses. This process is used by US benefit providers who have licensed Oracle Advanced Benefits to display pages for participants or dependents to register on the system to elect COBRA coverage. and other personal data. assignment status. This way the system can check for their existence on the database before they attempt to register their data.Configuring the New Employee and Non–Employee Registration Processes These processes are part of the Human Resources Self–Service item type. grade.

the Add Family Members page appears. NOTE: Employers must remove this page from the process. phone numbers. addresses. This page summarizes all the information in the database about the new user. If the user clicks Submit. the data is saved and the Confirmation page displays. Add Family Members No Life Events No User Name No Review Yes Confirmation No Note: It is not currently possible to route the information entered by the user for approval by workflow. A user hook is provided so that you can write the PL/SQL to generate the user names and passwords as you require. To configure the Registration processes. you can display the Enroll Now button on this page. You can set up Alerts to notify the HR administrator that a new person record has been created. Common Modules 9–27 . Users can select the life event that has made them eligible for a benefits program. This creates a potential life event for the person. Alternatively you can generate user names and passwords. If they confirm that they do. Relevant to US Third Party Benefits providers only. On this page. you make some changes using Workflow Builder and others using the Personalization Framework.Page Family Member Coverage Required? No Purpose This page simply asks users whether they wish to enter details of other family members. and additional personal information for as many contacts as they require. users can create their own user id and password. If you want to enable users to enroll themselves in benefits. Users can enter names.

There are no life event restriction capabilities in Standard Benefits. Decide which pages you want to use in the process. The only pages that can come before Personal Details are Introduction and Verification. If you use rates. 2. You must include Personal Details. In non–US countries. ensure you are including all the fields that capture information required to assess benefits eligibility. and––for the New Employee Registration process only––Employment Details (to identify the correct organization). The Introduction page normally appears first. To delete pages. you must require a birth date. the life event page must be before the Personal Details page. and therefore need a Payroll. Decide in what sequence you want pages to appear. Main Address. Gender and Hire Date fields.Using Workflow Builder " To configure the New Employee and Non–employee Registration workflows: 1. Review. On the Personal Information page: • • • • You must display the Last Name. For the Non–employee Registration workflow. See: Configuring Workflow Objects: page 6–5 Using the Personalization Framework For each region.2 Implementation Guide . Cancel. If you have implemented Standard Benefits or Oracle Advanced Benefits. decide which region items you want to display. delete the corresponding activities from the workflow process. Oracle Advanced Benefits customers can use life event triggers in the database to determine benefit enrollment opportunities. edit the workflow process diagram. you should hide the field Covered Under Medicare. Employers must delete the Life Event page from the registration process. Make the Employee Number field enterable if you do not generate employee numbers in your business group. followed by Personal Details. 9–28 Oracle SSHR 4. To change the sequence of pages.

see: New Employee Registration and Non–employee Registration: page 9–35. The code choices are: • • • • All––meaning that the life event can be selected in all self–service processes that use the Life Events page. Social Security Number. You can add birth date. and email address. the application displays a tables of the duplicates so the user can choose one. See also: Configuring Web Pages: page 7–5 Setting Up Life Events (Advanced Benefits only) This section is relevant only to third party benefits providers who are including the Life Events page in the process flows. such as national identifier (for example. social security number). employee number. and FND username. • For a list of configurable regions. employee number. If the information entered on the Verification page matches more than one person. On the Verification page: • You can add fields to assist the search. Basic Registration––meaning that the life event can be selected in the New Employee Registration process COBRA Registration––meaning that the life event can be selected in the Non–employee Registration process Basic and COBRA Registration––meaning that the life event can be selected in both the New Employee and the Non–employee Registration processes Common Modules 9–29 . person descriptive flexfields. In localizations that use GRE. person descriptive flexfields. you should display the GRE field. Employers who use Oracle Advanced Benefits should rely on life event triggers to determine the necessary processing instead of using this page. you must display the Payroll field. You determine which life events appear on the Life Events page by the Selectable for Self–Service code you enter when you define the life event in the professional user interface. If you use rates or element entries.On the Employment Information page (New Employee Registration only): • • • You must display the Organization field. Decide what information to include in this table.

2 Implementation Guide . the person may have other life events detected due to life event triggers in the business group. This is the approach that employers should use to determine data changes that may give the person an opportunity to make benefit election changes. Ensure that your life event collapsing and collision logic leaves a user with just one “winning” potential life event during the Participation Process. the process will insert the event as a potential life event for the person. By completing the rest of the registration process.Colliding Life Events When a person selects a life event from this page. during setup of collapsing life events. Turning off automatic triggering of life events Removing Life Event page from workflow and configuring life event triggers in the business group to be detected based on data entered by the person during the registration process. you could choose which event should win if there is more than one overriding event. You could do this by one of the following approaches: • Ensuring that all life events that can be selected in Registration have the Override check box selected (and other life events that might be triggered do not). Then. • • 9–30 Oracle SSHR 4.

A user hook is provided so that you can write the PL/SQL to generate the user names and passwords as you require. Alternatively you can generate user names and passwords. or shared with the new employee registration process.Configuring the Create User Name Process The Create User Name Process workflow within the Human Resources Self–Service item type displays the pages for people who already have a record on the HR database to create their own self–service user names and passwords. This page summarizes all the information in the database about the new user. the following pages: Page Verification Required? Yes Purpose This page has the user enter minimal information about themselves. If you want to enable users to enroll themselves in benefits. users can create their own user id and password. Decide whether users should log on to use this process with a generic company ID or with a guest ID (which would happen automatically and be invisible to the user). This process includes. the data is saved and the Confirmation page displays. If you decide to use a company ID for extra security: • 2. or is taken straight to the Create User Name process. This page must find one and only one person matching the information entered so that the User is connected to the correct HR record On this page. Common Modules 9–31 . User Name Yes Review Yes Confirmation No " To configure the Create User Name process: 1. you can display the Enroll Now button on this page. This determines whether the user sees a menu of processes after logging on. Decide whether to create an ID specific to this process. by default. If the user clicks Submit.

see the Note above) If the user name is passed in. (For example. Log on using this user to change the password. By default. Decide what information a user must enter on the Verification page of the system to identify the existing HR person record.home directly passing a user name/password if desired. there are three approaches you can use. Log on using this user to change the password to WELCOME.home?userid=<your user name>&password=<your password>).login?i_1=USERNA ME&i_2=PASSWORD&rmode=2 • In the Users window. oraclehomepage. Do one of the following: • In the Users window.2 Implementation Guide . If you decide to use a guest ID. On the Verification page: • • 9–32 Oracle SSHR 4. the password must be too. One approach––if you have licensed Oracle Advanced Benefits––is to create a new communication type and use the Determine Communications batch process. • Call oraclehomepage. By default this information is: first name. It passes the user name and unencrypted password into the call to oraclehomepage. employee number.home(). organization. and birth date. address. This approach will only work for people currently in the database. and person flexfields. create the guest user with any name and password. 3. The procedure passes the user name and unencrypted password into the call to oraclehomepage. passing a user name and unencrypted password. Call the supplied pl/sql procedure ben_guest_user_api without passing a user name and password. Call the supplied pl/sql procedure ben_guest_user_api. Decide what to display if the information entered on the Verification page matches more than one person. You can add the following fields: national identifier (such as social security number). You can grant this user the predefined New User Registration responsibility or your copy of it. supervisor. email address. 4.• Decide how to communicate the company IDs to your users.home(). location. the application displays an error. Note: Call ben_guest_user_api from a URL in this way: [APPS_WEB_AGENT]ben_guest_user_api. create the guest user with the user name GUESTOAB and the password GUESTOAB. or the procedure returns an error. last name. (For the format of the call. The procedure uses user name GUESTOAB and the password WELCOME.

By default the application issues an error directing the user to retry or Cancel to the menu and contact their administrator. Common Modules 9–33 . see: Create User Name: page 9–37. Decide what should happen if users try to create a user name when they do not have an existing HR record. all new users are granted the responsibility set in the OAB:Self Registered User Responsibility profile option. For example.For a list of configurable regions. To do this. By default. Determine which responsibility to assign to the new users. you can create different generic IDs (and responsibilities) for different groups of users and change the OAB:Self Registered User Responsibility profile option at responsibility level. 6. the Cancel button could take them straight to the New Employee Registration process. You can configure the message text and the URL associated with the Cancel button. You may wish to configure this to vary the responsibility by the person type (especially employee versus non–employee). 5. rather than to the menu.

rather than have them create their own. Optionally. 3. 2. Consider how you will inform users of their user name. edit the instruction text on the User ID page. using the user hooks. you can choose to generate their self–service user name and password. 9–34 Oracle SSHR 4.Generating Self–Service User Names and Passwords When a person has registered themselves in the HR database. You can implement this using user hooks. and change the button label from Next to Generate.2 Implementation Guide . Another approach is to generate the user names in a standard and predictable way from users’ names or national identifiers. One approach––for Oracle Advanced Benefits customers––is to use a user hook to call your own code that populates the communication tables. and use this information to alert your users. Write the PL/SQL to generate the user names and passwords as you require. hide the user name and password fields. See: User Hooks To Generate User Names for New User Registration (appendix): page B – 2. " To generate user names and passwords: 1.

users log on with a generic user name to create their own employee records in Oracle HRMS. They can be used as part of employee self–service or manager self–service.New Employee Registration and Non–employee Registration These modules are available under the predefined New User Registration Responsibility. Using Non–employee Registration. and their own self–service user name and password. Using New Employee Registration. Menu and Function Names User Menu Name Function Name New User Registration New User Registration New Employee Registration Non–employee Registration Workflow The workflow details for this module are listed below: Workflow Process Display Names: New Employee Registration Process and COBRA Registration Process See: Oracle Workflow Guide (available on Metalink) Note: Approval is not supported by these processes. other people can log on to create non–employee records in your Oracle HRMS. Configurable Workflow Attributes: Not applicable Configurable Tips and Instructions Region Tip Type Message Name Ben Life Event Cobra Ben Life Event Cobra Ben Life Event Current Message Message Message BEN_COBRA_LIFE_EVENT_DATE BEN_LIFE_EVENT_COBRA BEN_LIFE_EVENT_DATE Common Modules 9–35 .

2 Implementation Guide . Reporting. and System Administration in Oracle HRMS) 9–36 Oracle SSHR 4.Region Tip Type Message Name Ben Life Event Current Registration user Main Content Verification Content Message Short Tip DATE_FORMAT BEN_LIFE_EVENT_CURRENT HR_INCORRECT_PASSWORD_LENGTH See: Adding Instructions to Web Pages: page 7–9 Configurable Flexfields Region Flex Name Flex Code Verification Content Extra Information Type Update Additional Personal Details Flex Extra Person Information PER_PEOPLE Person Developer DDF See: Configuring Flexfields: page 7–6 Configurable Profile Options Profile Configurable Levels Values Default OAB: User to Organization Link OAB User to Payroll Link OAB: Self Registered User Responsibility HR: Business Group HR: Self Service HR Licensed All All All Organizations Payrolls Responsibilities Null Null Self Registered Employee Default Responsibility Set at Responsibility level Site––set to Yes Business groups Yes/No No See: User Profiles (Configuring.

Using Create User Name. people who already have an HR record in Oracle HRMS can create their own self–service user names and passwords. Configurable Workflow Attributes: Not applicable Configurable Tips and Instructions Region Tip Type Message Name New User Creation Verification Content Registration User Main Content DATE_FORMAT Short Tip HR_INCORRECT_PASSWORD_LENGTH See: Adding Instructions to Web Pages: page 7–9 Configurable Flexfields Region Flex Name Flex Code New User Creation Verification Content Additional Personal Details PER_PEOPLE Common Modules 9–37 . Menu and Function Names User Menu Name Function Name New User Registration Create User Name Workflow The workflow details for this module are listed below: Workflow Process Display Names: Create User Name Process See: Oracle Workflow Guide (available on Metalink) Note: Approval is not supported by these processes.Create User Name This module is available under the predefined New User Registration Responsibility. It can be used as part of employee self–service.

See: Configuring Flexfields: page 7–6 Configurable Profile Options Profile Configurable Levels Values Default OAB: Self Registered User Responsibility HR: Business Group HR: Self Service HR Licensed All Responsibilities Self Registered Employee Default Responsibility Set at Responsibility level Site––set to Yes Business groups Yes/No No See: User Profiles (Oracle HRMS Applications User Guide) 9–38 Oracle SSHR 4.2 Implementation Guide .

CHAPTER 10 Employee Demographics Employee Demographics 10–1 .

Menu and Function Names This module can be accessed from the following menus and functions: User Menu Name Function Name Manager Self Service V4. Title. and Dependents and Beneficiaries. The Personal Information function can be used to update basic details such as Marital Status. You can also design an approval process for any changes made by employees or managers. First and Last Name.2 Implementation Guide .0 Personal Information V4.0 Personal Information V4. By using Oracle Workflow and the Personalization Framework.Personal Information Modules The Personal Information function enables employees to enter and update their own personal records.0 Employee Self Service V4.0 See: Defining User Access and Menus: page 5–12 Workflow The workflow details for this module are listed below: Workflow Process Display Name: Personal Information V4. This function is integrated within Oracle Workflow. Addresses. Emergency Contacts. you can design a process to control which personal details an employee can change or display.0 Configurable Workflow Attributes: Not applicable Configurable Tips and Instructions Not applicable Configurable Flexfields Not applicable Configurable Profile Options Not applicable 10–2 Oracle SSHR 4.

0 Employee Self Service V4. Menu and Function Names This module can be accessed from the following menus and functions: User Menu Name Function Name Manager Self Service V4.0 See: Oracle Workflow Guide (available on Metalink) Configurable Workflow Attributes: Not applicable Configurable Tips and Instructions Basic Details Page Region Tip Type Message Name Basic Detail Update Name Entry Basic Detail Update Name Entry Basic Detail Update Name Entry Basic Detail Update Name Entry Long Message Long Message Long Message Long Message HR_TIP_EFFECTIVE_DATE HR_TIP_PREFIX HR_TIP_SUFFIX HR_TIP_PREFERRED_NAME Employee Demographics 10–3 .0 Personal Information V4.Basic Details The Basic Details module records information such as the employee’s name and marital status.0 Personal Information V4.0 See: Defining User Access and Menus: page 5–12 Workflow The workflow details for this module are listed below: Workflow Process Display Name: Process Basic Details V4.

2 Implementation Guide .Region Tip Type Message Name Basic Detail Update Name Entry Basic Detail Update Name Entry Basic Details Update Entry Long Message Instruction Instruction HR_TIP_PREVIOUS_LASTNAME HR_INST_BASIC_DETAILS_FORM HR_PERINFO_FUTURE_CHANGES Basic Details Action Page Region Tip Type Message Name Basic Details Action Type Instruction HR_INST_BASIC_DETAILS_TOC See: Adding Instructions to Web Pages: page 7–9 Configurable Flexfields Basic Details Page Region Flex Name Flex Code Basic Detail Update Other Entry Basic Detail Update Other Entry Further Person Information Additional Personal Details Person Developer DF PER_PEOPLE See: Configuring Flexfields: page 7–6 Configurable Profile Options Not applicable 10–4 Oracle SSHR 4.

0 Personal Information V4.Main Address The Main Address module stores the employee’s primary address. Menu and Function Names This module can be accessed from the following menus and functions: User Menu Name Function Name Manager Self Service V4.0 Personal Information V4.0 Employee Self Service V4.0 Configurable Workflow Attributes: Not applicable Configurable Tips and Instructions Main Address Page Region Tip Type Message Name Main Address Update Main Adderss Update Main Address Update Main Address Update Main Address Update Long Message Long Message Instruction Instruction Instruction HR_TIP_MADDR_EFFECTIVE_DATE HR_TIP_MADDR_ADDRESS_TYPE HR_INST_MAIN_CORRECT_ADDRESS HR_INST_MAIN_NEW_CHG_ADDRESS HR_INST_VIEW_FUTURE_CHANGES Employee Demographics 10–5 .0 See: Defining User Access and Menus: page 5–12 Workflow The workflow details for this module are listed below: Workflow Process Display Name: Process Main Address V4.

2 Implementation Guide .Main Address Action Page Region Tip Type Message Name Main Address Action Type Instruction HR_INST_MAIN_ADDRESS_TOC See: Adding Instructions to Web Pages: page 7–9 Configurable Flexfields Main Address Page Region Flex Name Flex Code Main Address Update Main Address Update Personal Address Details Additional Address Details Address Structure PER_ADDRESSES See: Configuring Flexfields: page 7–6 Configurable Profile Options Not applicable 10–6 Oracle SSHR 4.

0 Configurable Workflow Attributes: Not applicable Configurable Tips and Instructions Other Address Page Region Tip Type Message Name Second Address Update Second Address Update Second Address Update Second Address Update Second Address Update Instruction Instruction Instruction Instruction Instruction HR_TIP_SADDR_EFFECTIVE_DATE HR_TIP_SADDR_ADDRESS_TYPE HR_INST_SCND_CORRECT_CHANGES HR_INST_SCND_NEW_CHG_ADDRESS HR_INST_VIEW_FUTURE_ADDRESS Employee Demographics 10–7 . Menu and Function Names This module can be accessed from the following menus and functions: User Menu Name Function Name Manager Self Service V4.0 Employee Self Service V4.Secondary Address The Secondary Address module stores additional addresses for an employee.0 Personal Information V4.0 Personal Information V4.0 See: Defining User Access and Menus: page 5–12 Workflow The workflow details for this module are listed below: Workflow Process Display Name: Process Secondary Address V4.

Other Address Action Page Region Tip Type Message Name Secondary Address Action Instruction HR_INST_SECONDARY_ADDRESS_TOC See: Adding Instructions to Web Pages: page 7–9 Configurable Flexfields Other Address Page Region Flex Name Flex Code Secondary Address Update Secondary Address Update Personal Address Information Additional Address Details Address Structure PER ADDRESSES See: Configuring Flexfields: page 7–6 Configurable Profile Options Not applicable 10–8 Oracle SSHR 4.2 Implementation Guide .

Phone Numbers The Phone Numbers module stores the telephone information for an employee.0 Employee Self Service V4. Menu and Function Names This module can be accessed from the following menus and functions: User Menu Name Function Name Manager Self Service V4.0 Personal Information V4.0 See: Defining User Access and Menus: page 5–12 Workflow The workflow details for this module are listed below: Workflow Process Display Name: Process Phone Numbers V4.0 Personal Information V4.0 Configurable Workflow Attributes: Not applicable Configurable Tips and Instructions Personal Information Overview Page Region Tip Type Message Name Phone Numbers Overview Phone Numbers Update Instruction Instruction HR_PERINFO_PHONES_ABOVE_LIMIT HR_INST_PHONES_FORM Other Addresses Page Region Tip Type Message Name Second Address Update Second Address Update Instruction Instruction HR_INST_SCND_NEW_CHG_ADDRESS HR_INST_VIEW_FUTURE_CHANGES Employee Demographics 10–9 .

2 Implementation Guide .See: Adding Instructions to Web Pages: page 7–9 Configurable Flexfields Phone Numbers Details Page Region Flex Name Flex Code Phone Number Details Additional Telephone Number Details PER_PHONES Phone Details Review Page Region Flex Name Flex Code Details Review Additional Telephone Number Details PER_PHONES Configurable Profile Options Not applicable 10–10 Oracle SSHR 4.

Dependents and Beneficiaries The Dependents and Beneficiaries module stores the names and contact information for an employee’s dependents and beneficiaries. Menu and Function Names This module can be accessed from the following menus and functions: User Menu Name Function Name Manager Self Service V4.0 Employee Self Service V4.0 Personal Information V4.0 See: Defining User Access and Menus: page 5–12 Workflow Not applicable Configurable Tips and Instructions Contacts Page Region Tip Type Message Name Contacts Main Table Region Contacts Main Table Region Contacts Main Table Region Contacts Main Table Region Contacts Main Table Region Contact Phone Numbers Contact Address Contacts Main Table Region Instruction Long Message Long Message Long Message Long Message Instruction Instruction Instruction HR_289383_CONT_EMRG_MAIN_MSG HR_TIP_SUFFIX HR_TIP_PREFIX HR_289372_EMRG_CONT_FLAG_TIP HR_289373_PRMRY_REL_MAIN_TIP HR_INT_PHONES_FORM HR_INST_MAIN_CORRECT_ADDRESS HR_289371_DEP_BNF_FLAG_TIP Employee Demographics 10–11 .0 Personal Information V4.

See: Adding Instructions to Web Pages: page 7–9 Configurable Flexfields Not applicable Configurable Profile Options Not applicable 10–12 Oracle SSHR 4.2 Implementation Guide .

Emergency Contacts The Emergency Contacts module stores the contact information for the employee’s emergency contacts. Menu and Function Names This module can be accessed from the following menus and functions: User Menu Name Function Name Manager Self Service V4.0 See: Oracle Workflow Guide (available on Metalink) Configurable Workflow Attributes: Not applicable Configurable Tips and Instructions Contacts Page Region Tip Type Message Name Contacts Main Table Region Contacts Main Table Region Contacts Main Table Region Instruction Long Message Long Message HR_289383_CONT_EMRG_MAIN_MSG HR_TIP_SUFFIX HR_TIP_PREFIX Employee Demographics 10–13 .0 Employee Self Service V4.0 Personal Information V4.0 See: Defining User Access and Menus: page 5–12 Workflow The workflow details for this module are listed below: Workflow Process Display Name: Process Contacts V4.0 Personal Information V4. Employees can add and delete people from the list of emergency contacts as required.

2 Implementation Guide .Region Tip Type Message Name Contacts Main Table Region Contacts Main Table Region Contact Phone Numbers Contact Address Long Message Long Message Instruction Instruction HR_289371_DEP_BNF_FLAG_TIP HR_289373_PRMRY_REL_MAIN_TIP HR_INT_PHONES_FORM HR_INST_MAIN_CORRECT_ADDRESS See: Adding Instructions to Web Pages: page 7–9 Configurable Flexfields Not applicable Configurable Profile Options Not applicable 10–14 Oracle SSHR 4.

Other Professional Awards. In addition. Education and Qualifications. Employees can maintain their own details or managers can maintain the details for their direct reports.Professional Details Modules There are five modules within Professional Details: Competence Profiles. and Resume. there are two modules for the US localization (Tenure Tracking and Academic Rank). Employee Demographics 10–15 . Work Preferences.

0 See: Oracle Workflow Guide (available on Metalink) Configurable Workflow Attributes: Not applicable 10–16 Oracle SSHR 4. the user cannot edit the qualification until it has been approved or rejected by the approver.0 Employee Self Service V4.Education and Qualifications This module allows users to add qualifications to an existing list of qualifications or to create a new list of qualifications.2 Implementation Guide . The Education and Qualifications overview page shows the list of approved education qualifications for a person and also those qualifications that are pending approval. If the transaction is awaiting approval. Menu and Function Names This module can be accessed from the following menus and functions: User Menu Name Function Name Manager Self Service V4. the workflow submits the transaction for approval.0 See: Defining User Access and Menus: page 5–12 Workflow The workflow details for this module are listed below: Workflow Process Display Name: Education and Qualifications V4. and delete the major subjects for the qualifications.0 Education and Qualifications V4. When the user has created or edited a qualification.0 Education and Qualifications Mgr V4. The user can also add. edit.

Configurable Tips and Instructions Education and Qualifications Overview Page Region Tip Type Message Name Qualification Approved Header Qualification Overview Page Qualification Approved Header Instruction Instruction Instruction HR_INST_NO_QUALIFICATION_FOUND HR_INST_ADD_QUALIFICATION HR_INST_QUALIFICATION_FOUND Add Qualifications Page Region Tip Type Message Name Qualification Add Main Page Qualification Add Main Page Add Qualification Add School Instruction Instruction HR_INST_NEW_QUALIFICATION HR_INST_EDIT_QUALIFICATION HR_INST_SCHOOL_NAME Add Subject Page Region Tip Type Message Name Qualification Add Subject Main Page Qualification Add Subject Main Page Qualification Add Subject Main Page Qualification Add Subject Main Page Instruction Instruction Instruction Instruction HR_INST_AWARD_ADD_SUBJECT HR_INST_AWARD_EDIT_SUBJECT HR_INST_QUA_ADD_SUBJECT HR_INST_QUA_EDIT_SUBJECT See: Adding Instructions to Web Pages: page 7–9 Employee Demographics 10–17 .

Configurable Flexfields Add Qualifications Page Region Flex Name Flex Code Qualification Add Qualification Qualification Add Qualification Add Qualification Add School Additional Qualification Details Further Qualification Information Additional Establishment Attendance Details PER_QUALIFICATIONS Qualification Developer DF PER_ESTABLISHMENT_ATTENDANCES Add Subject Page Region Flex Name Flex Code Add Subject Add Subject Additional Subjects Taken Details Further Subject Information PER_SUBJECTS_TAKEN Subject Developer DF Configurable Profile Options Not applicable 10–18 Oracle SSHR 4.2 Implementation Guide .

Academic awards are entered in the Education and Qualifications page.0 Other Professional Awards Mgr V4.0 See: Defining User Access and Menus: page 5–12 Workflow The workflow details for this module are listed below: Workflow Process Display Name: Other Professional Awards V4. When the user has created or edited an award. the user cannot edit the qualification until it has been approved or rejected by the approver. If the transaction is awaiting approval. the workflow submits the transaction for approval.0 Employee Self Service V4.0 Other Professional Awards V4. Menu and Function Names This module can be accessed from the following menus and functions: User Menu Name Function Name Manager Self Service V4.Other Professional Awards This module allows users to add additional professional awards to an existing list of awards or to create a new list of professional awards.0 See: Oracle Workflow Guide (available on Metalink) Configurable Workflow Attributes: Not applicable Configurable Tips and Instructions Awards Page Region Tip Type Message Name Awards Add Main Page Awards Add Main Page Instruction Instruction HR_INST_NEW_AWARD HR_INST_EDIT_AWARD Employee Demographics 10–19 .

Other Professional Awards Overview Page Region Tip Type Message Name Award Approved Header Award Approved Header Award Overview Page Instruction Instruction Instruction HR_INST_NO_AWARD_FOUND HR_INST_AWARD_FOUND HR_INST_ADD_AWARD See: Adding Instructions to Web Pages: page 7–9 Configurable Flexfields Awards Page Region Flex Name Flex Code Awards Add Qualification Awards Add Qualification Additional Qualification Details Further Qualification Information PER_QUALIFICATIONS Qualification Developer DF Add Subject Page Region Flex Name Flex Code Add Subject Add Subject Additional Subjects Taken Details Further Subject Information PER_SUBJECTS_TAKEN Subject Developer DF Configurable Profile Options Not applicable 10–20 Oracle SSHR 4.2 Implementation Guide .

Access to the competencies function may be restricted to specific users. the line manager. you can • All pages allow you to validate the changes made. The proficiency levels must be displayed dynamically depending on the selected competence. skills. Typically. There is the need for a security mechanism to define who can maintain competences for which employees. a person may have a continuous series of records for a given competence showing progression from one level to the next. and personal or professional attributes. for example. Employee Demographics 10–21 . The levels for a given competence can fluctuate over time. A competence definition associated with a competence profile typically ’ends’ when a new level of the competence is attained. Competences include knowledge. A given competence can also become obsolete within a person’s competence profile. and its behavioral indicators wherever a competence and scale is displayed. you can: • • • In the New Levels Attained page. its associated levels. The Competence Profile Overview page has three sections: • • • Current competencies Current session changes Competences pending approval View the Competence Profile History Add additional competences Update competence levels Correct existing competences Correct or delete session changes Search for competences to add to your profile Create default profiles Add additional information on competences Enter information on the competence level attained In the Competence Profile Overview page. you can: • • • • • In the Add Competence page.Competence Profile The Competence Profile enables the user to record a set of competences for an individual. Proficiency scales can vary with each competence so it is essential that the user has access to the descriptions for the competence. A person’s competencies are only valid in the context of the proficiency level at which they demonstrate each competence.

Menu and Function Names This module can be accessed from the following menus and functions: User Menu Name Function Name Manager Self Service V4.The user can copy the competences defined for the job or position related to a person’s assignment across to their competence profile using the Default Competences button in the Add Competence page.0 See: Defining User Access and Menus: page 5–12 Workflow The workflow details for this module are listed below: Workflow Process Display Name: Competence Profile V4.2 Implementation Guide . the user must update the proficiency level manually as this is not copied across.0 See: Oracle Workflow Guide (available on Metalink) Configurable Workflow Attributes: Not applicable Configurable Tips and Instructions Correction Page Region Tip Type Message Name Correction Main Page Instruction HR_COMP_CORRECTION_SS Current Changes Page Region Tip Type Message Name Current Changes Main Page Instruction HR_COMP_CORRECTION_SS 10–22 Oracle SSHR 4. However.0 Competence Profile V4.0 Employee Self Service V4.0 Competence Profile Mgr V4.

See: Adding Instructions to a Web Page: page 7–9 Configurable Flexfields Not applicable Configurable Profile Options Not applicable Employee Demographics 10–23 .

2 Implementation Guide .0 Work Preferences Mgr V4. Employees can enter the information for themselves and managers can enter the information for their direct reports.0 Employee Self Service V4.0 Work Preferences V4. Menu and Function Names This module can be accessed from the following menus and functions: User Menu Name Function Name Manager Self Service V4.Work Preferences The Work Preferences function enables users to store information about their preferred work location and their relocation and travel preferences.0 See: Defining User Access and Menus: page 5–12 Workflow The workflow details for this module are listed below: Workflow Process Display Name: Configurable Workflow Attributes: Not applicable Configurable Tips and Instructions Region Name Tip Type Message Name Work Preferences Instruction HR_INST_WORK_PREFERENCES See: Adding Instructions to Web Pages: page 7–9 Configurable FlexFields Not applicable Configurable Profile Options Not applicable 10–24 Oracle SSHR 4.

0 Employee Self Service V4.Resume The Resume module enables an employee to store and update their own resume.0 Resume V4. A manager can store a resume for an employee or update the resume with new information.0 Resume Mgr V4.0 See: Defining User Access and Menus: page 5–12 Workflow The workflow details for this module are listed below: Workflow Process Display Name: Not applicable Configurable Workflow Attributes: Not applicable Configurable Tips and Instructions Region Name Tip Type Message Name Resume Instruction HR_INST_TEXT_RESUME See: Adding Instructions to Web Pages: page 7–9 Configurable FlexFields Not applicable Configurable Profile Options Not applicable Employee Demographics 10–25 . Menu and Function Names This module can be accessed from the following menus and functions: User Menu Name Function Name Manager Self Service V4.

2 Implementation Guide .0 See: Defining Menus for SSHR: page 5–12 Workflow The workflow details for this module are listed below: Workflow Process Display Name: Tenure Status V4.0 Manager Self Service V4. This results in a person attaining permanent employment with the institution.0 Professional Details V4. The Tenure Status module captures the following information: • • • • • • Tenure status Date determined Projected tenure date Adjusted tenure date Reason for adjustment Subject to tenure quota? Menu and Function Names This module can be accessed from the following menus and functions: User Menu Name Function Name Manager Professional Details V4.0 Employee Self Service V4.0 Configurable Workflow Attributes: Not applicable Configurable Tips and Instructions Not applicable 10–26 Oracle SSHR 4.0 Tenure Status V4.Tenure Status (US) Tenure is a unique term in the ”Education Industry” that means the completion of professional criteria and an extended probationary period.0 Tenure Status Overview Tenure Status V4.0 Tenure Status Mgr V4.

Configurable Flexfields Region Attribute Name FlexField Name Tenure Status Flex Descriptive Flexfield Extra Person Info DDF See: Configuring Flexfields: page 7–6 Configurable Profile Options Not applicable Employee Demographics 10–27 .

The Academic Rank module captures the following information: • • • • Academic rank Start date and end date Next academic rank Projected date Menu and Function Names This module can be accessed from the following menus and functions: User Menu Name Function Name Employee Self Service V4.Academic Rank (US) The Academic Rank module is a method for promotional progression within Higher Education.0 Configurable Workflow Attributes: Not applicable Configurable Tips and Instructions Not applicable Configurable Flexfields Region Attribute Name FlexField Name Academic Rank Flex Descriptive Flexfield Extra Person Info DDF 10–28 Oracle SSHR 4.0 Academic Rank V4.0 See: Defining User Access and Menus: page 5–12 Workflow The workflow details for this module are listed below: Workflow Process Display Name: Academic Rank V4.2 Implementation Guide .0 Academic Rank V4.0 Manager Self Service V4.

See: Configuring Flexfields: page 7–6 Configurable Profile Options Not applicable Employee Demographics 10–29 .

10–30 Oracle SSHR 4.2 Implementation Guide .

CHAPTER 11 Career and Performance Management Career and Performance Management 11–1 .

Events and Bookings The Events and Bookings V4. enabling managers to book their subordinates onto events.2 Implementation Guide . presentations.0 Events and Bookings V4. If a manager books a subordinate onto an event.0 function is available to both managers and employees. See also: Event and Attendance Administration (Managing Your Workforce Using Oracle HRMS) Menu and Function Names This module can be accessed from the following menus and functions: User Menu Name Function Name Employee Self Service V4. The Events and Bookings V4.0 Workflow The workflow details for this module are listed below: Workflow Process Display Name: Not applicable Configurable Workflow Attributes: Not applicable Configurable Tips and Instructions Region Name Tip Type Message Name Events Search Criteria Events Create Button Events Search And Result Header Instruction Instruction Instruction PQH_EVENT_SEARCH PQH_EVENT_ADDORCANCEL PQH_EVENT_BOOK 11–2 Oracle SSHR 4. the subordinate employee receives notification of the booking.0 function enables self–service users to create their own events such as meetings.0 Manager Self Service V4. or training days or to book themselves on existing events.0 Events and Bookings V4.

Region Name Tip Type Message Name Manager Events Search And Result Header Events Create Button Instruction PQH_EVENT_MGR_SEARCH Instruction PQH_EVENT_ADDORCANCEL See: Adding Instructions to Web Pages: page 7–9 Configurable Flexfields Not applicable Configurable Profile Options Not applicable Career and Performance Management 11–3 .

See: Event and Attendance Administration (Managing Your Workforce Using Oracle HRMS) Menu and Function Names This module can be accessed from the following menus and functions: User Menu Name Function Name Employee Self Service V4.0 Employee Review V4. Both managers and employees can invite reviewers to attend the review.0 Manager Self Service V4. When reviewers are invited to a review or removed from a review.Employee Reviews The Employee Review V4.0 Workflow The workflow details for this module are listed below: Workflow Process Display Name: Employee Review V4.2 Implementation Guide .0 Configurable Workflow Attributes: Not applicable Configurable Tips and Instructions Not applicable Configurable Flexfields Not applicable Configurable Profile Options Not applicable 11–4 Oracle SSHR 4. Employees can create their own reviews and managers can create reviews for their employees.0 function enables employees and managers to create or update reviews.0 Employee Review V4. they receive a notification. They can also remove these reviewers if necessary.

CHAPTER 12 Manage Employee Events (MEE) Manage Employee Events (MEE) 12–1 .

Location V4. The basic MEE modules are: Assignment.0 Change Hours V4. Change Manager V4. Employment Terms. Work Schedule.0 Assignment V4.0 Assignment V4.0 Assignment V4. Special Information Types. Other Employment Info V4.0. Location V4.0 12–2 Oracle SSHR 4.0. Pay Rate V4.0. Pay Rate. and/or Manager V4. Work Schedule V4.0.0 Change Job V4.0 Assignment V4. if required.0 Change Manager V4. EIT Update V4. The functions available enable you to control an employee from hire through to termination.0 Change Conditions V4. and/or Manager V4. Other Employment Info V4.0 Change Cost Center.0 Work Schedule V4. The following table gives a list of the delivered chained processes. Change Manager V4. Location V4.0 Location V4. Location. Location.MEE Modules and Workflow The Manage Employee Events module groups together workflow processes that relate to changes in an employee’s assignment.0 EIT V4.0 Change Manager V4.0. Location.0 Change Location V4.0 Pay Rate V4. Change Manager. Individual Compensation Distributions.0. and Other Employment Information. Note: You can also include the Individual Compensation Distributions (ICD) module in chained processes.0. Such processes are known as chained processes.0. You can build and configure these workflow processes to suit the requirements of your enterprise. Chained MEE Processes Oracle Workflow enables you to combine different MEE modules into one workflow process.0 Assignment V4.0 Change Job and Employment Terms V4. Termination.2 Implementation Guide .0 Change Extra Information Types V4.0.0 Change Cost Center. MEE Chained Processes: MEE Chained Process Contains the following MEE modules: Change Base Salary V4. SSHR includes a number of predefined chained processes that appear as functions on the user menus.0.

Change Manager V4.0. Work Schedule V4.0.0 Termination Page V4. Pay Rate V4. Work Schedule V4.0 Termination Page V4. Organization Manager Detail V4. Other Compensation V4.0.0 Transfer V4.0. you must consider the following rules when designing the sequence of functions: Function Restriction Assignment Change Manager Extra Information Types Individual Compensation Distributions Location If the Assignment module is present in a chained process. Organization Manager Detail V4.0 Termination Page V4.0. Location V4.0 Employee Terms of Employment Change V4.0 Assignment V4.0.0.0 Deploy Person V4. Pay Rate V4.0.0. it must appear first.0 Assignment V4. Pay Rate V4.0.0.0 Assignment V4.0. SIT Update V4.0 Termination V4. SIT V4.0. Change Manager V4.0 SIT V4. Change Manager V4.0.0. Change Manager V4.0.0 Termination with Compensation V4.0. Change Manager V4. Work Schedule V4.0 Assignment V4.0 Change Special Information Types V4.0.0.0 Employee Status Change V4.0 Change Supervisor Process V4. it should follow Termination Can appear anywhere in the chain Can appear anywhere in the chain Can appear anywhere in the chain Manage Employee Events (MEE) 12–3 .MEE Chained Process Contains the following MEE modules: Change Pay Rate Process V4.0 Pay Rate V4.0.0. Change Manager V4. Location V4. If used in a chain with Termination. Other Employment Info V4. Change Manager V4.0. Location V4. Location V4.0.0 ICD and Termination Integration V4.0. Work Schedule V4. If you choose to create your own chained processes and functionality.0 Ordering MEE Workflow Processes The order of workflow processes must be carefully designed to ensure business rules are maintained and implemented.0 Change Supervisor V4.

2 Implementation Guide . 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. you could configure a process that follows this sequence: • • • Step 1: Assignment Step 2: Location Step 5: Work Schedule But.Function Restriction Other Employment Information Pay Rate Special Information Types Termination Can appear anywhere in the chain Can appear anywhere in the chain Can appear anywhere in the chain If used in a chain with Supervisor. 12–4 Oracle SSHR 4. you cannot configure a process in this order. For example. it should precede Supervisor You can configure your own processes in any number of ways but they must comply with the restrictions listed above.

the Employee Status Change chained process. This notification is only sent for changes to salary basis and not for new hires or the first assignment of a salary basis to an existing employee. The payroll contact can accept or reject the change. Note: To enable a manager to select an assignment. the application sends a notification to a payroll contact as part of the approval process. If you want to enable self–service users to assign a salary basis. for example. Menu and Function Names Not applicable Workflow The workflow details for this module are listed below: Manage Employee Events (MEE) 12–5 . you must select the relevant assignment before you carry out the employee action. If they change the salary basis mid–way through a payroll period. Also. you must enable the Salary Information region item in the HR_ASSIGNMENT_SS and HR_ASSIGNMENT_REVIEW_SS regions. or change the salary basis of an existing employee. Note: This notification is sent only for employees assigned to a payroll. or return it to the originator requesting a change to the effective date (normally setting it to the first day of the next payroll period). users can assign newly hired employees to a salary basis. This may not be desirable for payroll calculations. Assigning a Salary Basis If you enable the Salary Information region. therefore if a user changes the salary basis of an employee assigned to a payroll on any effective date other than the first day of the employee’s payroll period. this notification is sent to your payroll contact only if you have enabled approvals for this transaction.0). the profile option HR: Enable Multiple Assignments in SSHR must be set to yes at the required level. You must also set up the payroll contact using a workflow item attribute (Payroll Contact User Name V4. Multiple Assignments If an employee has more than one assignment.Assignment The Assignment module is used in some delivered Manage Employee Events (MEE) menu functions. the application ends the existing salary element entry. It can be added in any of your own business processes that you model in the Workflow Builder.

0 The Assignment V4.0 Change Job V4.Workflow Process Display Name: Assignment V4.2 Implementation Guide .0 Transfer V4. HR Element Warning Controls whether hr element changes are displayed as a warning or an error.0 See: Configuring Workflow Attribute Values: page 6–7 Use Grade Points Defines whether the ceiling point can be displayed.0 Configurable Workflow Attributes: Function Activity Display Name Function Activity Attribute Display Name Assignment V4. Set Grade Ceiling Defines whether the ceiling point can be updated. Use Step/Grade No Update Defines whether the grade can be changed if grade steps exist.0 module is used in several example chained processes including: • • • Employee Status Change V4.0 Use Grade Points Set Grade Ceiling Use Step/Grade No Update Display Job Attachment Display Position Attachment HR Element Warning Asg Change Reason Lookup Codes HR Use Default Location Item Level Attributes Item Attribute Display Name Payroll Contact User Name V4. 12–6 Oracle SSHR 4.

Configurable Tips and Instructions Assignment Page Region Tip Type Message Name Assignment Job Position GRE Payroll Location Location Instruction Instruction Instruction Instruction Instruction Long Message Long Message HR_INST_TOP_COMMON_TEXT HR_INST_ASG_JOB_SS HR_INST_ASG_POSITION_SS HR_INST_ASG_GRE_SS HR_INST_ASG_PAYROLL_SS HR_INST_CHANGE_LOCATION HR_INST_WORK_AT_HOME_LOC Manage Employee Events (MEE) 12–7 . HR Use Default Location The location can be changed to the default organization or position locations. If there are comments for the job. If there are comments for the position. If the organization/position is then changed for a user. You enter the codes as follows: • Reason1|Reason21|. Payroll Contact User Name V4. no attachments are displayed. no attachments are displayed. the user’s location will be the default location for the organization/position.0 The Applications user name of the payroll representative who should be notified when a user changes an employee’s salary basis in the middle of a payroll period..Asg Change Reason Lookup Codes Allows system administrator to specify which change reason lookup codes should be displayed (subset of change reason lookup codes). This attribute is mandatory if you use the Salary Basis functionality.. Display Position Attachment Whether attachments are displayed for the position when there are no position comments. Display Job Attachment Whether attachments are displayed for the job when there are no job comments.

The list of values for the Grade field is determined by the entry in the Organization. 12–8 Oracle SSHR 4. Configurable Flexfields Assignment Page Region Flex Name Flex Code Specific Job Information Extra Position Information Department Working Conditions People Group Other Assignment Information Statutory Information HrFlex1 HrFlex1 HrFlex1 People Group Key Flex Additional Assignment Details Work Sched Key Flex Job Developer DF Extra Position Info DDF Org Developer DF GRP PER_ASSIGNMENTS GRES_AND_OTHER_DATA See: Configuring Flexfields: page 7–6 Configurable Profile Options Profile Configurable Levels Values Default HR:Use Grade Defaults HR:Override Grade Defaults Site. Responsibility. or position. User Site. or Position field.* These instructions are delivered as hidden. Application. job. User Yes/No Yes/No Yes No The following profile options control a user’s ability to use grade defaults. HR:Use Grade Defaults If this profile value is Yes. Responsibility. although they can be displayed and personalized. If this profile value is No.2 Implementation Guide . the user can select any grade for the organization. or position. Application. the user can only select a valid grade for a parent organization. job. Job.

Manage Employee Events (MEE) 12–9 . If this profile value is No.HR:Override Grade Defaults If this profile value is Yes (and the HR:Use Grade Defaults profile is also Yes). position. the user can select a different (non–default) grade for an organization. or job. the user cannot override the default grade.

For example.0 Termination Reason Lookup Codes Termination Reason Lookup Codes This attribute allows users to configure which Termination Reason lookup Codes to display. In the event of the employee also being a manager to an organization.0 Termination Page V4. if your enterprise does not want a manager to select the Termination Reason lookup code of ”Involuntary Termination”. If the terminated employee has direct subordinates.2 Implementation Guide . Note: If you create your own version of the Termination process.Termination The Termination page enables a manager to end an employee’s employment relationship. You configure the reasons in the workflow activity attribute configuration. This depends on how your security profile is set up. 12–10 Oracle SSHR 4. For more information see: Organization Manager: page 14–2 Menu and Function Names Not applicable Workflow The workflow details for this module are listed below: Workflow Process Display Name: Termination Process V4.0 Configurable Workflow Attributes: Process Display Name Function Activity Display Name Function Activity Attribute Display Name Termination Process V4. You can configure which Termination Reasons are displayed to the user in the Termination page. the system will automatically display the Change Manager page to reassign the terminated supervisor’s subordinates to another supervisor. This is because you do not differentiate between assignments when you terminate an employee. the Update Organization Manager page may appear for you to assign a new manager. you should remove the Assignment Selection page from the workflow process. you can exclude it by omitting this lookup code in workflow.

The Lookup Code. Separate each lookup code with the ”|”. in other words. See: Configuring Workflow Attribute Values: page 6–7 Configurable Tips and Instructions Termination Page Region Tip Type Message Name Termination Details Long Message HR_INST_TERMINATION See: Adding Instructions to Web Pages (Implementing Oracle Human Resources 4. the codes entered here will be included for display.Note: The list entered in this attribute is in the format of ”lookup_code1|lookup_code2|.. or enter ”All” or ”ALL”. The list entered in this attribute is the inclusion list.”. is used and no embedded blanks are allowed. you can either leave this attribute empty. If all the lookup codes are to be displayed..0) Configurable Flexfields Termination Page Region Flex Name Flex Code Termination Details Termination Details Additional Period of Service Details Additional Period of Service Information PER_PERIODS_OF_SERVICE PER_PDS_DEVELOPER_DF See: Configuring Flexfields: page 7–6 Configurable Profile Options Not applicable Manage Employee Events (MEE) 12–11 . not the meaning.

2 Implementation Guide . The employment category defines the type of employment.0 Configurable Workflow Attributes: Not applicable Configurable Tips and Instructions Region Name Tip Type Message Name Work Schedule Work Schedule Work Schedule Long Message Short Tip Short Tip HR_INST_WORK_SCHED_MAIN HR_TIP_WORK_START_TIME HR_TIP_WORK_END_TIME See: Adding Instructions to Web Pages: page 7–9 Configurable FlexFields Region Name Flex Name Flex Code Work Schedule Work Schedule Soft coded KeyFlexfield Additional Assignment Details SCL PER_ASSIGNMENTS 12–12 Oracle SSHR 4. Note: Part of the Work Schedule page information is displayed from the Soft Coded Key Flexfield. full and part–time employment. for example. See Configuring Flexfields: page 7–6 Menu and Function Names Not applicable Workflow The workflow details for this module are listed below: Workflow Process Display Name: Change Work Schedule V4.Work Schedule The Work Schedule workflow process enables a manager to change an employee’s work schedule and employment category. A work schedule is the number of days and hours worked and the start and end times for the employee.

See: Configuring Flexfields: page 7–6 Configurable Profile Options Not applicable Manage Employee Events (MEE) 12–13 .

US users: If you select the Home Worker check box for an employee. for tax purposes.0 Configurable Workflow Attributes: Process Display Name Function Activity Display Name Function Activity Attribute Display Name Location V4. the employee is assumed.0 Location V4. This check box is available for all localizations.2 Implementation Guide . For more information on the tax implications of the Home Worker check box for US users. although it is delivered as hidden.0 Location V4. If required. you can set up approvals processes for the Location V4.Location The Location V4. see Managing Your Payroll Using Oracle HRMS (US).0 Hr Null Allowed HR Location Required Hr Use Defaults Hr Override Defaults HR Element Warning HR Null Allowed: 12–14 Oracle SSHR 4.0 Location V4.0 function.0 Location V4.0 Location V4. The Location region includes the Home Worker check box.0 Location V4. Menu and Function Names Not applicable Workflow The workflow details for this module are listed below: Workflow Process Display Name: Location V4.0 Location V4.0 function is available under the predefined Manager responsibility.0 Location V4. to work 100% from their primary address (or tax override address if there is one) for this assignment.0 Location V4.0 function enables a manager to change an employee’s work location. The Location V4.

See: Configuring Workflow Attribute Values: page 6–7 Configurable Tips and Instructions Location Page Region Tip Type Message Name Change Location Change Location Instruction Long Message HR_INST_TOP_COMMON_TEXT HR_TIP_LOCATION_CODE See: Adding Instructions to Web Pages: page 7–9 Configurable FlexFields Location Page Region Flex Name Flex Code Location Location Location Address Additional Assignment Details Address Location PER_ASSIGNMENTS See: Configuring Flexfields: page 7–6 Manage Employee Events (MEE) 12–15 . This is enforced by displaying the locations in a poplist.Allows null location for an employee. The locations are displayed in a list of values if this attribute is called. HR Override Defaults: The location can be changed to any global location or any location in the user’s business group. HR Use Defaults: The location can be changed to the default locations which are the user’s Organization Location or Position Location. HR Location Required: Defines whether the location is required for an employee. HR Element Warning: Defines whether or not to display the HR element warning.

Configurable Profile Options Not applicable 12–16 Oracle SSHR 4.2 Implementation Guide .

Special Information Types (SITs)
Special Information Types (SITs) enable you to store additional information that is not currently captured by the system. The additional information is stored in categories. See: Additional Configuration Steps: page 12–19 See: Special Information Types (Managing Your Workforce Using Oracle HRMS)

Menu and Function Names
Special Information Types V4.0

Workflow
The workflow details for this module are listed below:

Workflow Process Display Name:
Change Special Information Types V4.0

Configurable Workflow Attributes:
Not applicable

Configurable Tips and Instructions
Special Information Page
Region Tip Type Message Name

Special Information Type Main Page

Instruction

HR_INST_SIT_OVERVIEW

Special Information Type Update Top Page
Region Tip Type Message Name

Special Information Type Update Page

Instruction

HR_SIT_UPDATE_INSTRUC_TEXT_SS

See: Adding Instructions to Web Pages: page 7–9

Manage Employee Events (MEE)

12–17

Configurable FlexFields
Special Information Page
Region Flex Name Flex Code

Special Person Information Type Details

Personal Analysis Flexfield

PEA

Special Information Type Update Top Page
Region Flex Name Flex Code

Special Person Information Type Review Special Information Type Update Page

Personal Analysis Flexfield Additional Person Analysis Details

PEA PER_PERSON_ANALYSES

Review Page
Region Flex Name Flex Code

Special Information Type Review Special Information Type Review

Additional Person Analysis Details Person Analysis Flexfield

PER_PERSON_ANALYSES PEA

See: Configuring Flexfields : page 7–6

Configurable Profile Options
Not applicable

12–18

Oracle SSHR 4.2 Implementation Guide

Additional Configuration Steps:
1. Decide how you want to use your SIT modules:
• • •

standalone – as an Employee or Manager menu chained – as part of a Manage Employee Events (MEE) flow chained – as part of a Personal Information flow See: MEE Functions and Workflow: page 12–2

2.

Enable your SITs using the Special Information Types form. You must enable them for each business group and select at least the Enabled and Other check boxes. See: Enabling Special Information Types (Managing Your Workforce Using Oracle HRMS)

3. 4.

Check the title of the SIT type. This title appears as the region header above the data in the self–service module. Use the Personalization Framework to restrict the SIT types that are displayed. By default, all SIT types that are enabled using the above procedure are displayed in the self–service SIT module (defined by the selected person’s business group), however, you can use the Personalization Framework to display only specific types. To display only certain special information types, personalize the HR_PERSON_SIT_DETAILS_SS region at the appropriate level (for example, responsibility or function) and in the Flex Settings box for HrSitKeyFlex, list the key flexfield structure codes of only the types you wish to appear. After each structure code, list the names of the segments you wish to appear for that special information type. Separate multiple segments with single pipe symbols (|) and separate multiple structures with double pipe symbols (||). Note: If you list a structure code with no segment names, the special information type will not be displayed. If you choose to only display certain SITs, you should also personalize the HR_PERSON_SIT_UPDATE_SS region and the HR_PERSON_SIT_REVIEW_SS region to correspond to the HR_PERSON_SIT_DETAILS_SS region. See: Configuring Flexfields: page 7–6

Manage Employee Events (MEE)

12–19

Extra Information Types (EITs)
Extra Information Types (EITs) are a type of flexfield that allows you to set up unlimited amounts of extra information. See: Extra Information Types (Configuring, Reporting, and System Administration in Oracle HRMS)

Menu and Function Names
Extra Information Types V4.0

Workflow
The workflow details for this module are listed below:

Workflow Process Display Name:
Change Extra Information Types V4.0

Configurable Workflow Attributes:
Process Display Name Function Activity Display Name Function Activity Attribute Display Name

Change Extra Information Types V4.0

EIT V4.0

HR EIT TYPE

HR EIT TYPE This attribute value defines whether the EIT is a Person or Assignment EIT. The possible values are PERSON or ASSIGNMENT, and the default value is PERSON. See: Configuring Workflow Attribute Values: page 6–7

Configurable Tips and Instructions
Extra Information Type Page
Region Tip Type Message Name

Extra Information Type Main Page

Instruction

HR_EIT_INSTRUCTION_TEXT_SS

12–20

Oracle SSHR 4.2 Implementation Guide

Extra Information Type Update Page
Region Tip Type Message Name

Extra Information Type Update

Instruction

HR_EIT_UPDATE_INSTRUC_TEXT_SS

See: Adding Instructions to Web Pages: page 7–9

Configurable FlexFields
Extra Information Type Page
Region Flex Name Flex Code

Extra Information Type Update

Extra Person Information

Extra Person Info DDF

Extra Information Type Update Page
Region Flex Name Flex Code

Extra Information Type Update Extra Information Update Page

Extra Person Information Extra Person Info Details

Extra Person InfoDDF PER_PEOPLE_EXTRA_INFO

Review Page
Region Flex Name Flex Code

Extra Information Update Page

Extra Person Info Details

PER_PEOPLE_EXTRA_INFO

See: Configuring Flexfields: page 7–6

Configurable Profile Options
Not applicable

Additional Configuration Steps
Note: Although EITs and SITs are similar in appearance, there are several different configuration steps due to underlying structural differences.

Manage Employee Events (MEE)

12–21

1.

Decide how you want to use your EIT modules:
• • •

standalone – as an Employee or Manager menu chained – as part of a Manage Employee Events (MEE) flow chained – as part of a Personal Information flow People Assignment

2.

You can currently set up EITs for the following HR entities:
• •

Before you can add the EIT V4.0 function to an SSHR process, you must enable the EITs for your responsibilities. You enable the EITs in the Information Types Security window. See: Setting Up Extra Information Types Against a Responsibility (Configuring, Reporting, and System Administration in Oracle HRMS) If your responsibility only covers one business group, you can select the required EITs directly in the Information Types region of the form. The available EITs are already associated with the business group for your responsibility. If your responsibility covers multiple business groups, you need to carry out the following procedure to access the EITs for the other business groups for your responsibility: 2.1 Copy the EITs for the delivered Manager Self–Service V4.0 or Employee Self–Service V4.0 responsibility to a custom responsibility. The delivered responsibilities are associated with all EITs for all business groups, in other words, there is no legislation restriction. 2.2 Delete the EITs that are not required for your responsibility. 2.3 Save your work. 3. The Context Description for the descriptive flexfield context value for the EIT appears as the region header in the self–service module. You configure the Context Description in the Descriptive Flexfield Segments window. All EIT that are enabled using the above steps are displayed in self–service EIT module, although they are restricted by the user’s responsibility and legislation code for the person’s business group. Note: We do not currently provide personalization options for EITs in self–service. The general advice on configuring flexfields does not apply to the EIT module.

4.

12–22

Oracle SSHR 4.2 Implementation Guide

Other Employment Information
The Other Employment Information module enables you to store assignment and employment information in descriptive flexfields and Developer Descriptive Flexfields (DDFs).

Menu and Function Names
Not applicable

Workflow
The workflow details for this module are listed below:

Workflow Process Display Name:
Change Other Employment Info V4.0

Configurable Workflow Attributes:
Not applicable

Configurable Tips and Instructions
Region Tip Type Message Name

Other Employment Info

Long Message

HR_INST_TOP_COMMON_TEXT

See: Adding Instructions to Web Pages: page 7–9

Configurable FlexFields
Region Flex Name Flex Code

CAGR Assignment Info Assignment Info

CAGR Flexfield Additional Assignment Details Soft Coded KeyFlexField

CAGR PER_ASSIGNMENTS SCL

See: Configuring Flexfields: page 7–6

Configurable Profile Options
Not applicable

Manage Employee Events (MEE)

12–23

Pay Rate
You use the Pay Rate module to enable a manager to change an employee’s overall pay rate directly (Single Pay Rate) or to create component increases to the previous rate (Multiple Pay Rate). You can change pay rates independently of assignment changes or as part of an assignment change. You can also insert a salary proposal for an employee.

Menu and Function Names
Not applicable

Workflow
The workflow details for this module are listed below:

Workflow Process Display Name:
Change Pay Rate V4.0

Configurable Workflow Attributes:
Process Display Name Function Activity Display Name Function Activity Attribute Display Name

Change Pay Rate V4.0

HR_P_RATE_JSP_PRC

Pay Rate V4.0

See: Configuring Workflow Attributes: page 6–7

Configurable Tips and Instructions
Region Tip Type Message Name

PayRate Main

Instruction

HR_INST_TOP_COMMON_TEXT

See: Adding Instructions to Web Pages: page 7–9

Configurable FlexFields
Region Flex Name Flex Code

Pay Rate Salary Admin Flex Add’l Salary Admin Details Cell Pay Rate Multiple Table Proposal Component Addl Info

PER_PAY_PROPOSALS PER_PAY_PROPOSAL_COMPONENTS

12–24

Oracle SSHR 4.2 Implementation Guide

See: Configuring Flexfields: page 7–6

Manage Employee Events (MEE)

12–25

Change Manager
The Change Manager function enables a user to perform the following operations on a selected employee and assignment:
• • •

specify which other employees report to the selected employee reassign the selected employee to report to a different manager reassign the selected employee’s subordinates to one or more managers

In a manager–subordinate relationship, the manager’s ID is stored against the subordinate’s assignment. If the profile HR: Enable Multiple Assignments in SSHR is set to No, only primary assignments are displayed. If the profile HR: Enable Multiple Assignments in SSHR is set to Yes, other assignments will also be displayed. In situations where a subordinate employee has more than one assignment, it is important to select which of the employee’s assignments is to report to the manager. In practice, this means that you may have to select between multiple assignments when you select the employee for whom you are using the Change Manager function and when you select the direct reports for the selected employee. In these cases, the lists of values will contain several fields (including Primary, Job, Department, and Business Group) to help you select the correct assignment. However, when you reassign the selected employee, or the selected employee’s subordinates, to a different manager, it is not necessary to specify a particular assignment for the manager.

Menu and Function Names
Not applicable

Workflow
The workflow details for this module are listed below:

Workflow Process Display Name:
Change Manager V4.0

Configurable Workflow Attributes:
Process Display Name Function Activity Display Name Function Activity Attribute Display Name

Change Manager V4.0

Change Manager V4.0

HR_MANAGER_REQUIRED_INDICATOR

12–26

Oracle SSHR 4.2 Implementation Guide

the supervisor_id field of the per_all_assignments_f record can remain blank.0) Configurable FlexFields Not applicable Configurable Profile Options Not applicable Manage Employee Events (MEE) 12–27 .HR_MANAGER_REQUIRED_INDICATOR If this attribute has a value of ”Y”. the employee must have a manager. See: Configuring Workflow Attribute Values: page 6–7 Configurable Tips and Instructions Region Tip Type Message Name New Manager Direct Reports of Selected Employee New Direct Reports Manager Update Direct Reports New Direct Reports Instruction Instruction Instruction Instruction Long Message Long Message HR_INST_SUPERVISOR_MAIN HR_INST_SUPERVISOR_DIRECT HR_INST_SUPERVISOR_NEW_DIRECT HR_INST_TOP_COMMON_TEXT HR_TIP_SUPERVISOR_DR_DATE HR_TIP_SUPERVISOR_NDR_DATE See: Adding Instructions to Web Pages (Implementing Oracle Human Resources 4. If this attribute has a value of ”N”.

2 Implementation Guide . such as a charitable contribution or savings bond plan. Use ICD for both one–time and recurring awards. You can also set up ICD for non–manager employees if your enterprise offers discretionary contribution plans. See: Self–Service Individual Compensation Distributions: page 19–2 Menu and Function Names This module can be accessed from the following menus and functions: User Menu Name Function Name Manager Self Service Individual Compensation Distributions See: Defining User Access and Menus: page 5–12 Workflow The workflow details for this module are listed below: Workflow Process Display Name: Compensation Distribution Configurable Workflow Attributes: Not applicable Configurable Tips and Instructions Region Tip Type Message Name Comp Plan Selection Compensation Update Mode Selection Content Benefits Communication Type Long Message CPS.PLAN_SELECTION_CONTENT BEN_92737_COMP_UPD_MD_INSTR 12–28 Oracle SSHR 4.Individual Compensation Distributions (ICD) The Individual Compensation Distributions (ICD) module enables managers to assign compensation distributions to employees. such as bonuses or allowances to employees. The Benefits or Compensation administrator needs to define the individual compensation distribution plans using Oracle Advanced Benefits or Oracle Standard Benefits.

Region Tip Type Message Name Compensation Details Content Compensation Review Content Benefits Communication Type Benefits Communication Type CPD.COMP_CONFIRM_CONTENT (Confirmation Page): CPR. COMP_DETAILS_CONTENT (Review Page): CPC.COMP_REVIEW_CONTENT See: Adding Instructions to Web Pages: page 7–9 Configurable FlexFields Not applicable Configurable Profile Options Not applicable Manage Employee Events (MEE) 12–29 .

2 Implementation Guide .12–30 Oracle SSHR 4.

CHAPTER 13 Recruitment Recruitment 13–1 .

0 French Applicant Hire V4. Pay Rate V4.0 French New Hire V4.0 Personal Information V4. Other Employment Information V4.0. Pay Rate V4. Assignment EIT.0.0 Personal Information V4.New Hire and Applicant Hire Processes The New Hire and Applicant Hire processes delivered with SSHR enable you to enter information about new employees. followed by the Personal Information page. address. Assignment V4. however should you want to change them to fit your particular business needs you can chain any of the following modules into the New Hire workflow process: • • • • • • • • Personal Information (including basic details. Following this. Work Schedule V4.0. Work Schedule V4.0 Personal Information V4. Assignment EIT. Assignment V4.0. the Hire Details and Applicant Search page must be the first page. Then you can add the Person EIT. Assignment V4. and phone numbers) Assignment Pay Rate Change Manager SIT EIT Work Schedule Other Employment Information When creating a chained process.0 Personal Information V4.0. or the Assignment pages.0. Pay Rate V4. any of the remaining pages can be included.0. Assignment V4.0 13–2 Oracle SSHR 4. Other Employment Information V4. and also hire those people for whom you already have applicant assignments with a status of Accepted.0.0.0. These processes provide you with the ability to hire employees into your enterprise.2 Implementation Guide . Recruitment Chained Processes: Chained Process Contains the following modules: New Hire V4. The following table gives a list of the delivered chained processes and what modules are included in them.0. Assignment EIT. Pay Rate V4.0.0 Applicant Hire V4.

Duplicate Person Checking When entering a new person. Menu and Function Names These processes can be accessed from the following menus and functions: User Menu Name Function Name Manager Self Service V4. then the application does a check to see if the person you are entering already has an existing record. You can do one of the following: • If a potential duplicate exists in outside of the current business group you can create a link between the two records by selecting it. People in a Global Enterprise. if you have the HR: Cross Business Group profile option set to Yes.0 Manager Self Service V4. then a list of the possible matches is displayed in the Potential Duplicate People page.0 Applicant Hire V4. the results displayed in the Search Applicant page are restricted according to your security profile. any applicant who is also a current or future employee in your enterprise is also excluded from the SSHR Search Applicant page. then when you click on the existing record an error is displayed as you cannot have two record for the same person in one business group. Managing your Workforce using Oracle HRMS. If this is a new person select No Match to indicate that the new record is not connected to any other records and continue entering information.Note: These processes are delivered with function level personalizations. • • For more information see. In addition.0 Recruitment 13–3 . This indicates that they are the same person. See: Function–level Personalizations: page C – 2 Applicant Search When hiring an applicant. If the potential duplicate exists in the same business group.0 New Hire V4. If you make a copy either of them in order to make your own changes you will lose these delivered personalizations. If an existing record is found.

0 Configurable Workflow Attributes: Refer to the individual topics on each of the modules included in your process for information on what configurable workflow attributes are available.0 French New Hire V4. Configurable Tips and Instructions Search Hire Applicant Page Region Tip Type Message Name Configurable FlexFields 13–4 Oracle SSHR 4.0 French Applicant Hire V4.User Menu Name Function Name Manager Self Service V4.2 Implementation Guide ÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁ Á Á ÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁ Á Á Á Á Á Á Á Á Á Á Á Á Á Á Á Á Á ÁÁÁÁÁÁÁ ÁÁÁÁÁÁÁÁ ÁÁÁÁÁÁÁÁ Á Á Á ÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁ Á Á Á Á Á Á Á Á Á Á Á Á Á Á Á Á Á ÁÁÁÁÁÁÁ ÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁ Á ÁÁÁÁÁÁÁÁÁÁÁÁ Á Á ÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁ Á Á ÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁ Á Á ÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁ Á Á ÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁ Á Á ÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁ ÁÁÁÁÁÁÁÁÁÁÁ ÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁ Á Á Á ÁÁÁÁÁÁÁÁÁÁÁÁ Á Á ÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁ ÁÁÁÁÁÁÁÁÁÁÁ Á Applicant List Long Message Instruction Instruction Instruction HR_GENERIC_PENDING_INST_SS Applicant Entry Applicant Entry Applicant Entry HR_INST_SEARCH_HIRE_APPLICANT HR_INST_SEARCH_APPLICANT HR_INST_APPLICANT_HIRE See: Adding Instructions to Web Pages: page 7–9 Region Flex Name Flex Code Basic Detail Update Name Entry Basic Detail Update Other Entry hrpersondevdfflex hrpersondevdfflex Person Developer DF Person Developer DF .0 See: Defining User Access and Menus: page 5–12 Workflow The workflow details for this module are listed below: Workflow Process Display Name: New Hire V4.0 Manager Self Service V4.0 French New Hire V4.

Person Record Synchronization. for example if a person has local records in two different countries If you want changes made in one business group to be propagated throughout all business groups. HR:Self Service New Hire Default Values Specifies whether values for the new person record should be defaulted or not. Application. Responsibility. then set this profile option to Yes. User Yes/No Yes/No Yes/No No No Yes HR:Cross Business Group Specifies whether people from business groups other than your own can be retrieved in the Search Applicant page. Managing your Workforce using Oracle HRMS. For more information see. Note: You can only propagate changes to business groups in which your security profile allows you to make updates. of the person logged in: Recruitment 13–5 . For the New Hire function. as of the system date. if the profile is set to Yes then the following values are defaulted based on the primary assignment.Region Flex Name Flex Code Configurable Profile Options ÁÁÁÁÁÁÁÁ Á Á Á Á Á Á Á Á Á Á Á Á Á Á Á Á Á ÁÁÁÁÁÁÁ Á Á Á Á Á Á Á Á Á Á Á Á Á Á Á Á Á ÁÁÁÁÁÁÁ Á Á Á Á Á Á Á Á Á Á Á Á Á Á Á Á Á ÁÁÁÁÁÁÁ Á Á Á Á Á Á Á Á ÁÁÁÁÁÁÁ ÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁ Á Á Á ÁÁÁÁÁÁÁÁ Á Á Á Á Á Á Á Á Á Á Á Á Á Á Á Á Á ÁÁÁÁÁÁÁ ÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁ Á Basic Detail Update Other Entry NewHire Main Address NewHire Main Address Add Per Details Flexfield hraddressflex PER_PEOPLE Address Structure hraddtladdressflex PER_ADDRESSES Profile Configurable Levels Values Default HR: Cross Business Group HR: Propagate Data Changes HR:Self Service New Hire Default Values Site. Responsibility Site Site. HR:Propagate Data Changes You use this profile option to control the synchronization of your person records where you have multiple records for one person.

For both New Hire and Applicant Hire. then this person type is defaulted. Configuring. If the profile is set to Yes and there is only one person type available. If there is more than one available then the field remains blank and you can select a value. User Profiles. Reporting and System Administration in Oracle HRMS 13–6 Oracle SSHR 4. • If the profile is set to No and there is only one person type available. this profile also controls which person type is defaulted. • For more information see. If there is more than one available then the field displays the person type set as the default for the system person type of Employee.• • • • Organization GRE (if US) Payroll Salary Basis The supervisor for the new person defaults to the person logged in. then this person type is defaulted.2 Implementation Guide .

CHAPTER 14 Organization Management Organization Management 14–1 .

If you terminate an employee who is also the manager of one or many organizations. the Update Organization Manager page does not appear. Menu and Function Names This Module can be accessed from the following menus and functions: User Menu Name Function Name Manager Self Service V4. • • If you have supervisor security enabled. If you have organization hierarchy security set up and the employee is the manager of multiple organizations. However.0 Organization Manager V4.2 Implementation Guide . If you do not have access to any records.Organization Manager The Organization Manager function enables you to maintain organization manager relationships. one of the following will occur: • The Update Organization Manager page displays for you to assign new managers to the organizations for which the terminated person was the manager. you can view and update organization managers according to your security profile in SSHR.0 Workflow Details of Workflow for this module are listed below: Workflow Process Display Name: Organization Manager V4. Note: There can only be one organization manager relationship at any single point in time.0 14–2 Oracle SSHR 4. the Update Organization Manager page displays only the records to which you have access and can update. A manager can only be initially assigned to an organization in the professional forms interface. the Organization Manager Actions Section on the Overview page will automatically display with any records that have been end dated and require you to assign a new manager.

You can find the organization classification code for a classification from the ORG_CLASS Lookup Type. Configurable Tips and Instructions Manager Overview Top Page Region Tip Type Message Name Organization Manager Actions Section Organization Manager Overview Form Organization Manager Search Section Organization Manager Actions Section Instruction Instruction HR_CCMGR_ACTIONS_SS HR_CCMGR_OVERVIEW_INSTR_SS Long Message Long Message HR_CCMGR_DIRECT_REPORTS_TIP HR_PENDING_INSTR_SS Manager Update Top Page Region Tip Type Message Name Organization Manaher Update Form Instruction HR_CCMGR_UPD_PAGE_INSTR_SS See: Adding Instructions to Web Pages (Implementing Oracle Human Resources 4.0 module to one organization classification by entering an organization classification code into the attribute.0 Organization Manager Overview V4.Configurable Workflow Attributes: Process Display Name Function Activity Display Name Function Activity Attribute Display Name Organization Manager V4. For example the code for HR Organization is HR_ORG.0) Configurable FlexFields Not applicable Organization Management 14–3 .0 Restrict Organization Classification Description of Attributes You can restrict the Organization Manager V4.

Configurable Profile Options Not applicable Additional Configuration Steps Not applicable 14–4 Oracle SSHR 4.2 Implementation Guide .

CHAPTER 15 Absence Management Absence Management 15–1 .

2 Implementation Guide . Users can request multiple absences and view them in a summary format. confirmed.Absences The Absences module enables employees or managers to enter absence–related information in SSHR.0 Configurable Workflow Attributes: Not applicable Configurable Tips and Instructions Leave of Absence Summary Top Page Region Tip Type Message Name Absence Summary Instruction HR_INST_LOA_SUMMARY 15–2 Oracle SSHR 4.0 Workflow The workflow details for this module are listed below: Workflow Process Display Name: Leave of Absence V4. and updated requests can be submitted for approval. For more information on Absence Management. They can submit a planned absence request (before the absence is taken) or a confirmed request (either after the absence is completed or when dates have been finalized before the absence begins). Menu and Function Names This module can be accessed from the following menus and functions: User Menu Name Function Name Leave of Absence V4. see: Absence Management and PTO Accruals (Managing Total Compensation Using Oracle HRMS). Absence requests can be updated by employees or managers to change the absence dates or confirm the absence.0 Leave of Absence V4. Users cannot update requests when they are pending approval. Planned. They can also view a history of absences they have taken.

Create Leave of Absence Page Region Tip Type Message Name Create Leave Of Absence Main Absence Details Instruction Instruction HR_INST_LOA_CREATE HR_INST_LOA_CREATE_DETAILS Update Leave of Absence Page Region Tip Type Message Name Update Main Update Details Instruction Instruction HR_INST_LOA_UPDATE HR_INST_LOA_UPDATE_DETAILS Confirm Dates Top Page Region Tip Type Message Name Confirm Dates Main Confirm Dates Details Instruction Instruction HR_INST_LOA_RETURN HR_INST_LOA_RETURN_DETAILS See: Configuring Tips and Messages: page 7–9 Configurable FlexFields Create Leave of Absence Page Region Flex Name Flex Code Additional Absence Details Further Absence Details Additional Absence Details Additional Absence Detail Information PER_ABSENCE_ATTENDA NCES PER_ABS_DEVELOPER_D F Absence Management 15–3 .

View Leave of Absence Page Region Flex Name Flex Code View Descriptive Flexfield View Developer Additional Absence Details Additional Absence Detail Information PER_ABSENCE_ATTENDA NCES PER_ABS_DEVELOPER_D F Update Leave of Absence Page Region Flex Name Flex Code Additional Absence Details Further Absence Details Additional Absence Details Additional Absence Detail Information PER_ABSENCE_ATTENDA NCES PER_ABS_DEVELOPER_D F Confirm Dates Top Page Region Flex Name Flex Code Additional Absence Details Further Absence Details Additional Absence Details Additional Absence Detail Information PER_ABSENCE_ATTENDA NCES PER_ABS_DEVELOPER_D F See: Configuring Flexfields: page 7–6 Configurable Profile Options Not applicable 15–4 Oracle SSHR 4.2 Implementation Guide .

CHAPTER 16 Views Views 16–1 .

see: Configuring Tabbed Regions: page 7–7. Each area of information is displayed on separate pages. Employee access using HR Views is controlled by the HRMS security access associated with the current user. and Termination History. The following chapter outlines the technical information for the separate HR Views pages. 16–2 Oracle SSHR 4. the user would have to log on with the Manager Self Service V4. The Views functions are displayed on tabbed regions. the user can simply click a button and display different information. To modify the information displayed.2 Implementation Guide .0 responsibility. Assignment Details. All information displayed in the HR Views is for viewing only. For information on configuring tabbed regions.Overview The HR Views module is intended to be used by HR Professionals. Compensation Activity. It offers a summarized view of different aspects of employee information: Personal Information. From each page. The HR Views functionality is reached using the HR User Self Service responsibility and the HR Views function. Note: HR Views show information that is more appropriate for HR professional users hence it is delivered under the HR Professional V4.0 responsibility.

Note: If the employee has been rehired. This information need not relate to their job or employment contract. All the information in the Employee Information view relates to the current record for the employee and no history is displayed.Employee Information View The Employee Information view displays the details relevant to an employee. the national identifier or visa information. for example. the SSHR application displays the last termination date. Menu and Function Names This module can be accessed from the following menus and functions: User Menu Name Function Name HR Views HR Views See: Defining User Access and Menus: page 5–12 Workflow The workflow details for this module are listed below: Workflow Process Display Name: Not applicable Configurable Workflow Attributes: Not applicable Configurable Tips and Instructions Not applicable Views 16–3 . The Employee Information page displays any specific fields which you have defined as flexfields and can also display a country–specific section which will display localization fields.

2 Implementation Guide .Configurable FlexFields Region Flex Name Flex Code EPI Address Detail Region EPI Additional Person Details EPI Further Person Information Personal Address Information Additional Personal Details Further Person Information Address Structure PER_PEOPLE Person Developer DF See: Configuring Flexfields: page 7–6 Configurable Profile Options Not applicable 16–4 Oracle SSHR 4.

the primary assignment information is displayed.Assignment Details View The Assignment Details view displays the assignment information for a particular employee. If multiple assignments are not enabled. the HR Professional can select which assignment information to display. If multiple assignments are enabled. See: Multiple Assignments: page 9–11 Menu and Function Names This module can be accessed from the following menus and functions: User Menu Name Function Name HR Views View Employee Assignment Details See: Defining User Access and Menus: page 5–12 Workflow The workflow details for this module are listed below: Workflow Process Display Name: Not applicable Configurable Workflow Attributes: Not applicable Configurable Tips and Instructions Not applicable Configurable FlexFields Region Flex Name Flex Code AD Current Assignment Region AD Current Assignment Region Job Flexfield Position Flexfield JOB POS Views 16–5 .

Region Flex Name Flex Code AD Current Assignment Region Grade Flexfield GRD PER_ASSIGNMENTS AD Additional AsAdditional Assignment Designment Details Desc tails Flex Region AD Assignment History Detail Region AD Assignment History Detail Region AD Assignment History Detail Region AD Assignment Statutory Info Job Flexfield Position Flexfield Grade Flexfield Soft Coded Key Flex JOB POS GRD SCL See: Configuring Flexfields: page 7–6 Configurable Profile Options Not applicable 16–6 Oracle SSHR 4.2 Implementation Guide .

only the rates are displayed. therefore. the HR Professional can select the required assignment. See: Multiple Assignments: page 9–11 Note: The self–service Manager views also contain a Salary Information view although this view does not contain information on the employee’s benefits. The Compensation Activity view displays all the elements for an employee unless they are linked to benefit plans and. If this is the case. Menu and Function Names This module can be accessed from the following menus and functions: User Menu Name Function Name HR Views View Employee Compensation Activity See: Defining User Access and Menus: page 5–12 Workflow The workflow details for this module are listed below: Workflow Process Display Name: Not applicable Configurable Workflow Attributes: Not applicable Configurable Tips and Instructions Not applicable Configurable FlexFields Region Flex Name Flex Code CA Work Detail Region CA Work Detail Region Job Flexfield Position Flexfield JOB POS Views 16–7 . have rates defined. If multiple assignments are enabled.Compensation Activity View The Compensation activity view displays the salary and benefits information for an employee.

2 Implementation Guide .Region Flex Name Flex Code CA Work Detail Region CA Additional Salary Details Desc Flex Region Grade Flexfield Add’l Salary Admin Details GRD PER_PAY_PROPOSALS See: Configuring Flexfields: page 7–6 Configurable Profile Options Not applicable 16–8 Oracle SSHR 4.

the application updates the information displayed in the view so that the employee is not displayed as Terminated.Termination History View The Termination History view displays any termination history for an employee. if they have been rehired more than once. Menu and Function Names This module can be accessed from the following menus and functions: User Menu Name Function Name HR Views View Employee Termination History See: Defining User Access and Menus: page 5–12 Workflow The workflow details for this module are listed below: Workflow Process Display Name: Not applicable Configurable Workflow Attributes: Not applicable Configurable Tips and Instructions Not applicable Configurable FlexFields Region Flex Name Flex Code TH Work Detail Region TH Work Detail Region Job Flexfield Position Flexfield JOB POS Views 16–9 . If an employee’s contract is terminated and the employee is subsequently rehired. for example. The employee’s record may contain more that one termination.

Region Flex Name Flex Code TH Work Detail Region TH Additional Periods of Service Desc Flex Region TH Additional Periods of Service Information Desc Flex Region Grade Flexfield Add’l Period of Service Det’s Add’l Periods of Service Information GRD PER_PERIODS_OF_SERVICE PER_PDS_DEVELOPER_DF See: Configuring Flex Segments: page 7–6 Configurable Profile Options Not applicable 16–10 Oracle SSHR 4.2 Implementation Guide .

Search Functions for HR Views The first Search function for HR Views is displayed when an HR Professional selects the HR Views option from the self–service menu (when using the HR User Self Service responsibility). At this point. The second Search function for HR Views is displayed when the HR Professional has searched for an employee. the user can only search for an employee.0) HR Views Menu (HR_VIEWS_MENU) HR Views Person Search Initial Screen HR Views Person Search See: Defining User Access and Menus: page 5–12 Workflow The workflow details for this module are listed below: Workflow Process Display Name: Not applicable Configurable Workflow Attributes: Not applicable Configurable Tips and Instructions Not applicable Configurable FlexFields Not applicable Views 16–11 . Menu and Function Names These modules can be accessed from the following menus and functions: User Menu Name Function Name HR User Self Service (HR_USER_SELF_SERVICE_V4. At this point. the user can either view data for the selected employee or search for another employee.

Configurable Profile Options Not applicable 16–12 Oracle SSHR 4.2 Implementation Guide .

CHAPTER 17 Benefits Benefits 17–1 .

or remove dependents Note: Self–Service requires dependents and beneficiaries to have the personal relationship check box checked on the Contacts window. and other information in Self–Service Benefits web pages are derived from Oracle Applications database tables using the rules of your plan design. update. update. or 401(k) plans. within the last two years Select benefits Distribute excess flex credits (Advanced Benefits) Add. price tags. • Search for and select primary care providers 17–2 Oracle SSHR 4. update.2 Implementation Guide . unrestricted. and life event enrollments for one or more flex or non–flex programs. Self–Service Benefits supports enrollment for plans and options in a program. or review family member information Note: Family member information entered through the self–service interface and personal contact data entered through the professional forms interface share the same table. including open. The enrollment choices. Employee Stock Purchase Plans (ESPP). Use Oracle’s professional forms interface or the self–service Individual Compensation Distribution web pages to enroll participants in all plans not in a program such as savings plans. and future program benefits enrollments. and up to ten past enrollments. Updated information is stored in the Oracle Applications database tables using standard Application Programmable Interfaces (APIs). • Add. and selected the May Designate Organization as Beneficiary check box in the plan enrollment requirements. Self–Service Benefits Enrollment Functionality Self–Service Benefits offers an employee the opportunity to: • • • • Review current. Any data entered or updated in Self–Service HRMS or the professional forms interface is reflected in both interfaces. or remove beneficiaries Employees can select organizational beneficiaries provided that the administrator has entered the Beneficiary Organization using the professional forms interface. • Add.Self–Service Benefit Enrollments Self–Service Benefits supports a variety of enrollment types.

on the Primary Care Provider Search page Full name See: Benefits Enrollments: page 17–10 for further details of these hidden fields and the regions where you can display them. The notification contains the following information and provides direct access to the Confirmation page for the participant.• Print a temporary participant identification card Enrollment Change Workflow Notifications You can configure the Workflow Builder to send a notification to an HR professional whenever a participant updates a Self–Service Benefits Enrollment web page. 3 (taxable). Benefits 17–3 . If the participant closes the browser window prior to reaching the Confirmation page. excluding the Primary Care Provider page. You can choose to display them. but is not linked to any Workflow approval process: • • • • • • Name of Employee Social Security Number or National Identifier Life Event Name Enrollment Period Selected Benefit Plans and Options List of Covered Dependents Oracle Workflow sends a notification to a worklist or group that you maintain after the participant completes the enrollment update. They include: • • • • Coverage start and end dates for specific enrollments Cost 2 (after tax). You can manually override the enrollment or contact the participant to correct and resubmit the election if necessary. and 4 (miscellaneous) columns for displaying multiple rates for a vertical display plan type Physician group and hospital. Oracle Workflow sends a notification within one hour of the first enrollment change. See: Self–Service Workflows Hidden Fields in Self–Service Benefits There are a number of fields that are delivered hidden by default on the self–service pages.

you must define a context for the flexfield based on BG_ID_PL_TYP_ID. • Add’l Contact R’ship Det’s (PER_CONTACTS) You enter this flexfield data in the Miscellaneous region of the Family Member Add page. To display the flexfield differentially by compensation object. Plan Type Context You may want to display the Additional Ben Prtt Enrt Rslt F Details flexfield only for enrollment in specific compensation objects. or segments defined for the selected plan type. it will contain all the contexts for the flexfield (even those for other business groups) unless you restrict them by a value set defined for the context. The Additional Ben Prtt Enrt Rslt F Details flexfield appears automatically if you define and freeze this flexfield. You must bounce the Apache server after freezing or unfreezing the flexfield to ensure that your changes are displayed. You can also view or enter the flexfield data in the Personal Information module of SSHR. you can choose to display some or all of the segments in self–service using the Personalization Framework. If there are frozen segments for the descriptive flexfield but no global segments defined and no segments defined for the selected plan type. See: Configuring Flexfields: page 7–6. On the Descriptive Flexfield Segments window. while hiding commission information used to calculate group life insurance rates. If you have set up the Further Person Information or Additional Contact Relationship Details flexfields. you may want to display prior years commission information to participants for a supplemental life insurance plan. For example.2 Implementation Guide . Notice that if you display this list. which appears after the Benefits Selection page if the flexfield has been set up and there are global segments. uncheck the Displayed check box for the context if you do not want to show the context poplist to the user. the Benefits Information page appears in the enrollment chain but the 17–4 Oracle SSHR 4.Displaying Descriptive Flexfields The following descriptive flexfields can be entered in self–service Benefits: • Additional Ben Prtt Enrt Rslt F Details (BEN_PRTT_ENRT_RSLT_F) You enter this flexfield data on the Benefits Information page. • Further Person Information (Person Developer DF) You enter this flexfield data in the Name and Relationship region of the Family Member Add page.

Integration with Authoria HR (US and UK) The third party product Authoria HR provides a common knowledge repository to manage and communicate HR and benefits information. Benefits 17–5 . The following topics look at the points you should consider when designing your plan for the self–service environment.region pertaining to this plan type does not display. you may want to hide the list of States from the address fields. Plan Design Considerations for Self–Service Benefits Before eligible participants can enroll in self–service benefits using the self–service interface. Note: The address style and country used by Self–Service Benefits is inherited from the primary benefits participant. you can edit field labels to fit your legislative requirements and you can also hide and unhide fields. consider hiding the after tax columns on the tables contained in the following web pages: • • • • Benefits Enrollment Overview Current Benefits Overview Benefits Selection Confirmation See: Setting Up Self–Service Benefits Web Pages: page 17–22 See: Benefits Enrollments: page 17–10 for a list of the configurable user interface elements in each delivered web page. If your legislation or benefit plan design does not allow for after tax contributions. For example. Legislative Configurations Self–Service Benefits is delivered with US–style formatting for the following fields: • • • • Address Social Security Number Pre Tax Cost After Tax Cost For non–US self–service implementations. Existing data set up in the flexfield is not affected by any new contexts you define for self–service. you must design your benefit plan using Oracle’s professional forms interface.

if you • 17–6 Oracle SSHR 4. You can configure the following self–service enrollment windows for use with Authoria HR: • • • • Benefits Enrollment Overview page Current Benefits page Confirmation page Benefits Selection page See Configuring. the column headings in self–service are Cost 1. However. you can select any activity type and tax type. and related costs such as fringe benefit taxes and administrative fees. and Cost 4.After a self–service implementer defines a total compensation plan in the Oracle HRMS professional user interface. either based on the coverage or the amount in Cost 1. Benefits Selection. if applicable. Cost 2. you must check the Display on Enrollment check box (Processing Information tab) and you must specify the Self Service Display Order number (1 to 4). Multiple Rates You can display up to four standard rates for each compensation object to enable employees to see employee and employer paid premiums. Reporting and System Administration in Oracle HRMS. When you display multiple rates. and Confirmation pages. However. Annual Value can only be entered in Cost 1.2 Implementation Guide . licensees of Authoria HR can configure links between Oracle HRMS and Authoria HR. Multiple rates are displayed on the Overview. End users can click on links in the applicable self–service web pages to display context–sensitive Authoria HR documentation. Otherwise. do not select the Enter Annual Value check box on the Calculation Method tab. 3. For example. When defining your standard rate. Costs 2. You can change the column headings using the Personalization Framework. a single rate displays as either Pretax or Aftertax. horizontal display Plan Types cannot display multiple rates. When you define standard rates for self–service. and 4 can be used to calculate additional amounts. Only vertical display Plan Types are able to be custom formatted in self–service to display multiple rates for a single compensation object. consider the following: • For Costs 2. Current Benefits. 3. and 4 you can select the Display on Enrollment check box (Processing Information tab of Standard Rates window) or the Enter Value at Enrollment check box (Calculation Method tab). Due to display and sizing constraints. Cost 3.

Unused Flex Credits (rollovers) displayed are not impacted by the use of multiple rates.02 * coverage. For example. you may not want them all deducted from flex credits. you link options for both selecting and declining coverage. Within this plan type. in this example) Benefits Pools (Advanced Benefits) If you are displaying multiple rates. All rates selected on this tab are included in the Flex Credit Used Total. Alternatively. Then. Flexible Spending Accounts (US) To ensure that your qualifying participants can enroll in Flexible Spending Account (FSA) plans using Self–Service Benefits. You also define a decline coverage plan which is linked to each plan type. check the Enter Value at Enrollment field in the Calculation Method region of the Standard Rates window.02 * coverage. you must set up your plans using one of the following two methods: The preferred method is to use the Plan Types window to define one plan type for each FSA plan. Use the Application tab on the Benefits Pool window to determine which standard rate to deduct. Indicate that values for this plan are entered at enrollment. • • Benefits 17–7 . in this example) Cost 3 = Total Cost––Select Multiple of Coverage as the Calculation Method (1.charge a 2% administration fee for a spending account. Select Set Annual Rate Equal to Coverage as the calculation method In the Coverages window. you define one plan type for Dependent Care FSA plans and a second plan type for Health Care FSA plans. For each plan type. you define the coverage plan or plans into which participants and their dependents can enroll. define the minimum and maximum contribution amounts for the FSA plan. you can set up one FSA plan type that covers both dependent care and health care plans. you would set up the rates as follows: Coverage––Check the Enter Value at Enrollment box Cost 1 = Contribution––Select Same as Coverage as the Calculation Method Cost 2 = Administration Fee––Select Multiple of Coverage as the Calculation Method (0. you define plans for both dependent care and health care. Other items for consideration: • When you define the activity rate for the FSA plan. within these plans.

Set the processing type of the corresponding element to Recurring. or other benefit treatment before the participant receives the official membership card from the provider. you indicate the number of flex credits associated with a compensation object by entering the value in the Flat Amount field in the Calculation Method region of the Flex Credits window. select the same periodicity for the activity reference period (the time period in which the system expresses activity rates) and the enrollment rate frequency (the activity rate that is communicated to participants). This plan records the total flex credits for the program. Using Self–Service Benefits. a participant can print one card for each elected plan that allows for temporary identification cards. You must set up a flex credits placeholder plan and link this plan to the flex program. • • Temporary Participant Identification Cards A temporary identification card allows a participant to obtain medical. The participant can also print a card for each covered dependent. Other items for consideration: • Unless your flex credits are determined using the result of a calculation.Flexible Benefits Programs (Advanced Benefits) With Flexible Benefits Programs. Define a rate for this plan by entering zero in the Flat Amount field of the Calculation Method region of the Standard Rates window. The application generates a temporary ID card upon: • • • • Enrollment Re–enrollment Change in Enrollment Participant Request (due to loss) The identification card includes information such as: • • • • Employee Name and Social Security Number Member Name and Social Security Number (for dependents) Employer Name Plan Name 17–8 Oracle SSHR 4. you can offer flex credits to eligible participants to offset the cost of benefits. dental. This ensures that the price tags for selecting benefits and the flex credits available to participants are expressed for the same time period.2 Implementation Guide . When you defining a benefit program in the Programs window.

If a plan type contains multiple plans. If a plan type has only one plan. you create a decline coverage plan in the Plans window (in addition to the regular plans) and indicate that the plan is of the specified plan type. Note: If your plan design requires that a participant select at least one option from a group of options or at least one plan from a group of plans. Benefits 17–9 .You indicate that a plan allows for the printing of temporary ID cards by checking the Allow Temporary Identification field on the Plans window. Declining Coverage Depending on your plan design. you must set up either a decline coverage plan or option that allows a participant to waive an enrollment opportunity for which they are otherwise eligible. do not define a decline coverage plan or option. This ensures that participants can either select or decline benefit coverage. you define a decline coverage option and link it to the plan.

plan type. and Family Members and Others Detail Page The Family Members and Others page enables a participant to view a record of their family members and other persons enrolled as dependents or beneficiaries of their benefits. First Middle Suffix’.0 Self–Service Benefits Enrollment – Employee Self–Service Benefits Enrollment – Federal Configurable Pages and Shared Regions The following definitions can be configured using the Personalization Framework: Family Members and Others. plan. 17–10 Oracle SSHR 4. Benefits participants can add another person to the Family Members and Others table by choosing the Add Another Person button. For instruction text.2 Implementation Guide . Menu and Function Names This module can be accessed from the following menus and functions: User Menu Name Function Name Employee Self–Service v4.) You can add the Full Name field to a web page and remove the delivered Name field. For example. See: Defining Self–Service Instruction Text: page 17–31 Hidden Fields: This topic also lists––by web page region––all fields the application delivers as hidden which you can display using the Personalization Framework. or life event. which opens the Family Members and Others Details page. by default all person name fields in Self–Service Benefits display names in the format ’First Last Suffix’ (without commas between the parts of the name. In the US. the Full Name field uses the format ’Prefix Last.Benefits Enrollments This topic provides reference information you need to configure your Self–Service Benefits web pages using the Personalization Framework. the tables below list––by web page region––the communication short name and the valid communication usages that are required when you define a communication type to display instruction text for a particular program.0 Employee Self–Service v4.

you cannot use communication usages to restrict the display of instruction text to a compensation object or a life event for the Family Members page.’ you can trigger a life event when a person enters a contact on the Self–Service Human Resources Contacts page and selects a relationship start reason. Life Event Benefits 17–11 . Life Event TENT FML. Hidden Field: Use the BEN_FAMILY_MBRS_TABLE region to add the hidden Full Name field to the page and to remove the Name field if necessary. the application opens the Current Benefits page. Life Event Family Members and Others Detail Page Region Tip Type Message Name Required Communication Short Name Valid Communication Usages Add or Update Family Members Name and Relationship Address Instruction Instruction Instruction FML. If you define a life event reason of the type ’Personal.FAMILY_MBRS_CONTENT Valid Communication Usages Members Content Family Members Content Instruction Help Tip Program.FAM_ADD_NA ME FML.Program.FAM_ADD_CON. Life Event Program. The seeded life event reason of Added During Enrollment prevents a life event from occurring when you create a family member or update a family member’s details.FAM_ADD_ADDRESS Program.This page only displays when a person has either: • • • An enrollment opportunity Eligibility for an unrestricted program A detected or unprocessed potential life event as of the system date If one of these conditions does not exist. Note: It is recommended that you provide instruction text indicating that eligibility for benefits may be based on family members. Family Members and Others Region Tip Type Message Name Required Communication Short Name FML. However.

Life Event Second Medical Cover. • BEN_OVW_SELECTIONS_TABLE • BEN_OVW_CVRD_DEPS_TABLE 17–12 Oracle SSHR 4. Hidden Fields: You can use the following regions to add the hidden Full Name field to the page and to remove the Name field if necessary. Life Event ER FML.FAM_ADD_OTH.Instruction age Address Name and Relationship Address Miscellaneous Information Miscellaneous Information Help Tip Hint (Suffix) Hint (Postal Code) Hint (National Identifier) Hint (Date of Birth) Message (Required Field Missing) Message (Invalid Birth Date) 92638 92639 92640 92637 92601 92598 __ __ __ __ __ __ __ __ __ __ __ __ Configurable FlexFields Family Members and Others Page Region Flex Name Flex Code Add or Update Family Members Miscellaneous Information Further Person Information Additional Contact Relationship Details hrpersondevdfflex Add Cont Details D Flexfield See: Configuring Flexfields: page 7–6 Benefits Enrollment Overview Page The Benefits Enrollment Overview web page enables a participant to view a record of their current benefits and to enroll into a new set of benefits.FAM_ADD_SECOND_MEDICAL Program.2 Implementation Guide .Region Tip Type Message Name Required Communication Short Name Valid Communication Usages Miscellaneous Information Instruction FML.Program.

These columns show the coverage start and end dates for each election. Life Event Program. Detail Message) –– 92571 –– –– Current Benefits Overview Page The Current Benefits Overview web page enables a participant to see a record of their current benefits. Life Event Program. Life Event Program.FLEX_CREDIT_ROLLOVERS BEO.FLEX_CREDITS BEO. Brief Message) Message (No Enrollment Opportunity. Life Event Program. Life Event Program. you can also display the Cost 2 (After Tax Cost) and Cost 4 (Miscellaneous) columns to show the rates you have defined with 2 and 4 in the Self Service Display Order field. If you are displaying multiple rates. Life Event Program. This column corresponds to a standard rate with an activity type of Self–Service Display.OVERVIEW_FC_SUMMARY BEO.OVERVIEW_CVRD_DEPS BEO.ENRL_OVERVIEW_BENEF BEO. Life Event Program. or––if you are displaying multiple rates for the compensation object––to the rate you have defined with 3 in the Self Service Display Order field.• BEN_OVW_BENEF_TABLE • BEN_OVW_PCP_TABLE You can use the BEN_OVW_SELECTIONS_TABLE region to display a column for the taxable cost of a benefit. Life Event Message (No Enrollment Opportunity.ENRL_OVERVIEW_CONTENT BEO. Benefits 17–13 . Benefits Enrollment Overview Page Region Tip Type Message Name Required Communication Short Name BEO. You can also use the BEN_OVW_SELECTIONS_TABLE region to display Coverage Start and End Date columns.OVERVIEW_SELECTIONS BEO.ENRL_OVERVIEW_PCP 92570 –– Valid Communication Usages Enrollment Overview Content Flex Credits Flex Credit Summary Flex Credit Rollovers Benefit Selections Covered Dependents Beneficiary Enrollment Overview Primary Care Providers Enrollment Overview Enrollment Overview Content Enrollment Overview Content Instruction Instruction Instruction Instruction Instruction Instruction Instruction Instruction Program.

OVERVIEW_CVRD_DEPS CBO. These columns show the coverage start and end dates for each election.OVERVIEW_PCP 92572 __ Valid Communication Usages Current Benefits Overview Content Flex Credits Flex Credit Summary Flex Credit Rollovers Benefit Selections Covered Dependents Beneficiary Overview Primary Care Providers Overview Current Benefits Overview Content Current Benefits Overview Content Instruction Program Instruction Instruction Instruction Instruction Instruction Instruction Instruction Message (No Current Enrollment. Brief Message) Message (No Current Enrollment.Hidden Fields: You can use the following regions to add the hidden Full Name field to the page and to remove the Name field if necessary. 17–14 Oracle SSHR 4.OVERVIEW_FC_SUMMARY CBO.ENRL_OVERVIEW_BENEF CBO. Detail Message) Program Program Program Program Program Program Program __ 92573 __ __ Benefits Selection Page The Benefits Selection page enables a participant to select one or more plans in which to enroll.OVERVIEW_SELECTIONS CBO. • BEN_OVW_CVRD_DEPS_TABLE • BEN_OVW_BENEF_TABLE • BEN_OVW_PCP_TABLE You can also use the BEN_OVW_SELECTIONS_TABLE region to display Coverage Start and End Date columns.2 Implementation Guide .CURRENT_OVERVIEW_CONTENT CBO. Current Benefits Overview Page Region Tip Type Message Name Required Communication Short Name CBO.FLEX_CREDITS CBO.FLEX_CREDIT_ROLLOVERS CBO.

Life Event Program.ENRT_SELECTION_CR_TOP BNS. Long Tip) Message (Enter Rate.ENRT_SELECTION_SELECT_AREA Valid Communication Usages Enrollment Selection Content Top Flex Credit Region Bottom Flex Credit Region Selection Area Selection Area Selection Area Instruction Instruction Instruction Instruction Help Tip (Certification Legend) Help Tip (Enter Annual Rate Input Box. Long Tip) Help Tip (Enter Rate Input Box.Region Tip Type Message Name Required Communication Short Name BNS. Plan Type. Note: For Advanced Benefits customers: if participant dependents are not displaying in this page. verify that you have linked the appropriate life events to the program or plan enrollment requirements in the Dependent Change of Life Event window. Benefits 17–15 . Life Event Selection Area Selection Area Selection Area Selection Area Selection Area Selection Area Selection Area Dependents Selection Page The Dependents Selection page enables a participant to add their dependents to a plan. Long Tip) Message (Enter Annual Rate. Long Tip) Help Tip (Enter Benefit Amount Input Box. Life Event Program. Life Event Program. Hidden Field: Use the BEN_ENRL_DEPEN_SELECTION_TABLE region to add the hidden Full Name field to the page and to remove the Name field if necessary. Long Tip) Message (Enter Benefit Amount Tip) Message (Tokens for above messages) Message (Tokens for above messages) BEN_ENRT_ANN_RT VAL_TIP BEN_ENRT_BNFTAM T_TIP BEN_ENRT_RTVAL_T IP BEN_ENRT_SLECT_TI P_ANY_AMOUNT BEN_ENRT_SLECT_TI P_ANY_VALUE Program.ENRT_SELECTION_CONTENT BNS.ENRT_SELECTION_CR_BOTTOM BNS.

BENEFICIARY_CONTENT_ORGS Valid Communication Usages Beneficiary Selection Beneficiary Selection Family Members and Others Organizations Beneficiary Totals Table Beneficiary Selection Instruction (Page) Instruction (Plan Level Table) Instruction Program. If your enterprise partners with a third party supplier of primary care provider information. Life Event Dependents Selection Hint (Dependent Table) Message (Can’t Designate) Program. Life Event Instruction Hint Message (Can’t Designate) 92587 __ __ Primary Care Provider Page The Primary Care Provider page enables a participant to select a care provider.ENRL_DEPENDENTS_CONTENT DPS. you can configure this page to allow web–based searches of a database of provider information. Plan.ENRL_DEPENDENTS_CONTENT_PL 92588 __ Valid Communication Usages Dependents Selection Dependents Selection Instruction Instruction –– Program. Plan Type. Plan Type.2 Implementation Guide .BENEFICIARY_CONTENT BFS. Life Event Program. Plan Type. Plan Type. Life Event Program. Hidden Field: Use the BEN_BENEF_SELECTION_TABLE region to add the hidden Full Name field to the page and to remove the Name field if necessary. Region Tip Type Message Name Required Communication Short Name BFS. Plan. 17–16 Oracle SSHR 4.BENEFICIARY_CONTENT_FAMILY BFS. Life Event __ Dependents Selection Beneficiary Selection Page The Beneficiary Selection page enables a participant to add their beneficiaries to a plan.BENEFICIARY_CONTENT_PLAN BFS.Dependents Selection Page Region Tip Type Message Name Required Communication Short Name –– DPS. Life Event Program. Plan. Plan.

Life Event Program. and Degree are reserved for future use. Language. Life Event Benefits 17–17 . Plan. you can use the BEN_PCP_SEARCH_CRITERIA region to add the hidden fields of Physician Group and Hospital. For the Physician Group. The hidden fields of Location. Plan Type. Plan. Hospital. you must load the available data as provided by GeoAccess into the corresponding Lookup Codes using the Application Utilities Lookups window in the Professional User Interface.PCP_SEARCH PCS.PcpSelectContentPageLevel PCP.PcpSelectContentPlanLevel __ 92567 __ Valid Communication Usages Primary Care Provider Selection Content Primary Care Provider Selection Content Primary Care Provider Selection Content Primary Care Provider Selection Content Instruction Instruction Hint Message (Can’t Designate) Instruction Instruction Program. • • • • Region Tip Type BEN_PCP_MED_GRP BEN_PCP_HOSPITAL BEN_PCP_LANGUAGE BEN_PCP_SPCLTY Message Name Required Communication Short Name PCS.See: Configuring the Primary Care Provider Search Facility: page 17–38 Region Tip Type Message Name Required Communication Short Name PCP. Life Event __ __ Primary Care Provider Summary and Search Pages Hidden Fields: You can use the following regions to add the hidden Full Name field to the page and to remove the Name field if necessary. and Specialty fields. Plan Type. Life Event Program.PCP_SEARCH_C RITERIA Valid Communication Usages Primary Care Provider Search Search Instruction Instruction Program. • BEN_PCP_SEARCH_TABLE • BEN_PCP_SELECT_TABLE On the Primary Care Provider Search page. Plan. School. Plan Type.

you can also display the Cost 2 (After Tax Cost) and Cost 4 (Miscellaneous) columns to show the rates you have defined with 2 and 4 in the Self Service Display Order field.2 Implementation Guide . Hidden Fields: You can use the following regions to add the hidden Full Name field to the page and to remove the Name field if necessary.PCP_SEARCH_R ESULT Valid Communication Usages PCP Result Table Ben PCP XML Request Params Ben PCP XML Request Params Instruction Tip Message (No PCPs found) Program. Use this region if you require a participant’s signature as part of a benefits enrollment.Region Tip Type Message Name Required Communication Short Name PCS. • BEN_OVW_BENEF_TABLE • BEN_OVW_CVR_DEPS_TABLE • BEN_OVW_PCP_TABLE You can use the BEN_OVW_SELECTIONS_TABLE region to display a column for the taxable cost of a benefit. This column corresponds to a standard rate with an activity type of Self–Service Display. These columns show the coverage start and end dates for each election. You can personalize the BEN_ENRL_CONF_CONTENT region to display the signature field. Plan Type. You can also use the BEN_OVW_SELECTIONS_TABLE region to display Coverage Start and End Date columns. or––if you are displaying multiple rates for the compensation object––to the rate you have defined with 3 in the Self Service Display Order field. If you are displaying multiple rates. Life Event Confirmation Page The Confirmation page enables a participant to see a summary of their choices and a warning of any oversights or miscalculations they may have made. 17–18 Oracle SSHR 4. Note: You can also use the Confirmation page to display a signature region for participants to print from their web browser. Plan.

FLEX_CREDIT_ROLLOVERS BEC. Life Event Program. Life Event Program. Benefits 17–19 .Region t Tip Type Message Name Required Communication Short Name Valid Communication Usages Ben Enrollment Confirmation Content Flex Credits Flex Credit Summary Flex Credit Rollovers Benefit Selections Covered Dependents Beneficiaries Enrollment Confirmation Primary Care Providers Enrollment Confirmation BEN_ENRL_CONF_W ARNINGS BEN_ENRL_CONF_W ARNINGS Instruction Instruction Instruction Instruction Instruction Instruction Instruction Instruction BEC.ENRL_CONF_PC P 92605 92606 __ __ Program. Life Event NTENT BEC. Life Event Program.FLEX_CREDITS BEC.ENRL_CONF_CO Program. Life Event Program. Life Event Program. Life Event Message (Confirmation Success) Message (Action Item Warning) __ __ Configurable FlexFields Confirmation Page Region Flex Name Flex Code Benefit Selections Additional Ben Prtt Enrt Rslt F Details N/A Unused Flex Credits Page The Unused Flex Credits page provides a summary of the flex credits left unspent by a participant.OVERVIEW_CVRD_DEPS BEC.OVERVIEW_FC_SUMMARY BEC.OVERVIEW_SELECTIONS BEC.ENRL_CONF_BE NEFICIARIES BEC. Life Event Program.

2 Implementation Guide . For example.Region Tip Type Message Name Required Communication Short Name FLX. or other benefit treatment before the participant receives the official membership card from the provider.UNUSED_FLEX_CREDIT_NONE Valid Communication Usages Unused Flex Credits Content Unused Flex Credits Content Unused Flex Credits Content Unused Flex Credits Content Instruction Program. you may want to perform system testing before the start of an open enrollment period. Life Event Message (No Unused Flex Credits) Message 92633 92632 __ __ __ __ Change Session Date Page The Change Session Date page lets you test future–dated elections. dental.UNUSED_FLEX_CREDIT_CONTENT FLX. This page should be removed in your production environment so that benefits participants do not alter their enrollment date. Life Event Instruction Program. See: Setting the Effective Date of a Scheduled Enrollment in Self–Service Benefits: page 17–28 Region Session Date Content Session Date Content Tip Type Instruction Tip (Effective Date) Message Name 92604 92637 Temporary ID Card Page The Temporary ID Card page lets a participant print an ID card which the participant can use to obtain medical. 17–20 Oracle SSHR 4.

Plan. Life Event Program. Plan. Plan Type.ENRL_TEMP_ID _CARD Valid Communication Usages Oracle Self–Service Human Resources Identification Card Ben Temporary ID Card Content Temporary ID Card Instruction Program.ENRL_TEMP_ID _PAGE TMP. Life Event See: Configuring Web Pages: page 7–5 Benefits 17–21 . Plan Type. Life Event Instruction Instruction Program.Region Tip Type Message Name Required Communication Short Name TMP.ENRL_TEMP_ID _PLAN TMP.

If you license Advanced Benefits. If you use Standard Benefits.Setting Up Self–Service Benefits Enrollments You must complete your plan design in the professional forms interface before you can view a self–service benefits enrollments web page. " To set up self–service benefits enrollments: 1. 17–22 Oracle SSHR 4. You do this by defining a communication type and associating the instruction text with a web page Region.com” target=_newWindow”>Vision Medical web site </a> for more information. Managing Total Compensation Using Oracle HRMS You can include a link in your instruction text to another web site using HTML syntax. You could create a link to reference information contained in a summary plan description. or if you are an Advanced Benefits customers using the unrestricted enrollment method. you can run the Participation Batch Process from the Concurrent Manager to create electable choices for eligible participants. You can configure the following elements using the Personalization Framework: • • • • • • Section titles Table Layout Hints Tips Fields (you can choose to display fields that are hidden by default) Field labels See: Configuring Web Pages: page 7–5 2.visionmedical. Review the sample benefits web pages.2 Implementation Guide . See: Defining Communication Types. The application creates the self–service enrollment page when the person logs into Self–Service Benefits. the application opens the web page in a new browser window. Define instruction text for each web page region. In this example. For example: See the <a href=”http://www. you can begin to allow participant enrollments after you create your plan design.

See: Defining a Benefits Program. Managing Total Compensation Using Oracle HRMS 7. You can vary the instruction displayed according to: • • • • Program Plan Type Plan Life Event (Advanced Benefits) See: Defining When to Use a Benefits Communication: page NO TAG 4.3. or––for Programs––the Overview page. To create a hypertext link. use one or more of the following windows: • • • • Programs (for a program) Plan and Plan Type window (for a plan or a plan type in program) Plans window (for a plan) Maintain Plan Options window (for an option in a plan) The link appears in the Benefits Selection web page. Managing Total Compensation Using Oracle HRMS 5. See: Maintaining Primary Care Providers for a Plan: page 17–35 8. See: Configuring the Primary Care Provider Search Facility: page 17–38 Benefits 17–23 . or option in plan. The application displays Action Item messages at the end of the enrollment process on the Confirmation page. Configure whether benefits participants have the option to select a Primary Care Provider (PCP) for a benefits plan. plan. Define when you want the instruction text displayed. plan type in program. See: ”Enrollment Action Types” in Enrollment Requirements. Review Messages and change any that do not meet your requirements. 6. plan in program. Configure whether you want benefits participants to have access to the Primary Care Provider Search facility. Configure Action Item messages (Advanced Benefits) to meet your requirements. Create a hypertext link from a compensation object to a web page which describes that program.

Query the function that you want to update. Note: If you do not see this string. In the Parameters field. Choose the Form tab. See: Enrollment Change Workflow Notifications: page 17–3 " To enable Self–Service Benefits Enrollment Notifications: 1. 17–24 Oracle SSHR 4. To enable workflow notifications. Replace the wfProcessName=FYI_NOTIFICATION_PRC portion of the parameter with your custom process name.Enabling Self–Service Benefits Enrollment Notifications You can configure Self–Service Benefits Enrollments so that an enrollment update generates a notification to an HR professional. Save your work. replace sendFYINotification=N with sendFYINotification=Y.2 Implementation Guide . To enable enrollment notifications. you update one of the seeded functions in the Form Functions window using the system administrator responsibility. 6. Choose one of the following: • • Employee Self–Service (BEN_SS_BNFT_ENRT) Manager Self–Service (BEN_SS_MGR_ENRT) 2. you must manually enter the parameter. 4. 3. 5. verify that the following parameter appears: displayDate=N&allowEnrt=Y&sessionDate=&sendFYINotification =N&wfProcessName=FYI_NOTIFICATION_PRC.

Log on to Oracle HRMS with the System Administrator responsibility. If you create a new submenu. Benefits 17–25 . you should copy and edit all delivered menus you want to update. your changes will be overwritten the next time you apply a patch to the application. 6.Setting Up User Access to Self–Service Benefits Self–Service Benefits functions are attached to the Benefits Self–Service menu. Save your work and close the Menus window. " To set up user access to self–service benefits: 1. Query the Benefits Submenu in the Menu field: BEN_SELF_SERVICE_BENEFITS. The following Self–Service User Menu Name displays to users: • Employee Self–Service V4. Query the Self–Service Menu in the Menu field: HR_EMPLOYEE_DIRECT_ACCESS_WEB. Otherwise. You can change menu names and function names. 5. 4. you must update the AK regions which point to the submenu. The Benefits Self Service submenu has the following prompts. you must update the AK regions which point to the submenu. 3. As a standard practice. or remove menus and functions if required. The following Benefits Submenu User Name displays: • Benefits Self Service Because the Benefits Self Service submenu is not linked to a top level menu (it has no prompt) the submenu is hidden.0 You can change the menu name if required. See: Configuring Tabbed Regions: page 7–7 See: User’s Menu (Oracle Applications System Administrator’s Guide) for more information on configuring menus. If you create a new submenu. 2. Open the Menus window. • • Benefits Enrollment Current Benefits These prompts function as the labels on the tabs of the self–service web page.

13. 16. or proceed to step 8 if you do not intend to create any new submenus.Complete steps 2 to 7 to update the region items. Repeat for each region listed in step 9. select the Application Menu entry. Save your work and close the Region Items window. Using an AK Developer responsibility. You can use the Form Functions window to customize the seeded functions––BEN_SS_BNFT_ENRT and BEN_SS_MNGR_ENRT. 12. 11. 9. Open the Regions window. Query one of the following regions in the Region ID field: • • • • • • • • • • • BEN_BENEFICIARY_PAGE BEN_CURR_OVW_PAGE BEN_ENRL_CONF_PAGE BEN_ENRL_DEPENDENTS_PAGE BEN_ENRL_OVERVIEW_PAGE BEN_ENRT_SELECTION_PAGE BEN_FAMILY_MBRS_PAGE BEN_FAM_ADD_PAGE BEN_PCP_SEARCH_PAGE BEN_PCP_SELECT_PAGE BEN_UNUSED_FLEX_CREDIT_PAGE 10. In the Attribute Name column. Choose the Region Items button to open the Region Items window. See: Configuring Tabbed Regions: page 7–7 7.2 Implementation Guide . Scroll to the Menu Name column and update the field with the new menu as entered in the Menu field of the Menus window. Use the Form Functions window to create your own Self–Service Benefit functions from the sample functions supplied. log on to the application. 14. 8. The sample User Function Names are: • • Self Service View Current Benefits Self Service Benefits Enrollment BEN_SS_CURR_BNFT BEN_SS_BNFT_ENRT The Function Names are: • • 17–26 Oracle SSHR 4. 15.

See: Users Window (Oracle Applications System Administrator’s Guide). Define the people you would like to access Self–Service Benefits. you can set up concurrent programs to automate this manual process. any benefits participants who attempt to enroll will receive an error message indicating they cannot enroll. See: Form Functions Window (Oracle Applications System Administrator’s Guide) 17. Or. one at a time. Set the HR: Business Group Profile. The Business Group Profile is: • HR: Business Group 19. Set Security Profiles. Use the System Profile Values window to link the responsibility you have created to a Security Profile and your Business Group. available from MetaLink. You can follow the typical steps for defining a new user and assign each user a responsibility that enables access to Self–Service Benefits. Use the System Profile Values window to link the responsibility you have created to your Business Group. There are two ways to do this. The Security Profile is: • HR: Security Profile Note: If you fail to link your Responsibility to your Business group with the HR: Security Profile. See: User Profiles (Oracle Applications User’s Guide and Oracle Applications System Administrator’s Guide) 18.If you update the seeded functions. Note: It is a good practice to check the Readme for each Self–Service Benefits patch you apply to see if the parameters and HTML Calls for the seeded functions have changed. See the White Paper titled: Batch Creation of User Accounts. Benefits 17–27 . you must update your custom function to use the seeded parameters and HTML Calls.

you can set the session date to record all enrollments as of January 1st of the following year. For example. Self–Service Benefits processes dates based on the date codes you select in your plan design. Choose from: • • BEN_SS_BNFT_ENRT (Employee Self–Service Benefits) BEN_SS_MGR_ENRT (Manager Self–Service Benefits) 4. 17–28 Oracle SSHR 4. 5. In the following example. 3. " To set the session date in Self–Service Benefits: 1. Note: You can use both features simultaneously. if you schedule your open enrollment period for the first two weeks in November. Log in to Oracle HRMS using a System Administrator responsibility and open the Form Functions window. but the date the user enters in the Change Session Date web page overrides the session date parameter for the current session. 2. Choose the Form tab. Query the Function Name for which you want to set the session date. such as for an upcoming open enrollment period. setting displayDate=Y displays the Change Session Date web page. Setting &sessionDate=12/31 sets the session date to December 31st for the BEN_SS_MGR_ENRT function. Update the seeded parameter to display the Change Session Date page or to set the effective date to a date you choose. Use the Change Session Date menu parameter if you use Oracle Standard Benefits and you want to record the life event occurred date of an enrollment for a date that is not equal to the system date. Note: If you do not set the session date. Choose the Description tab.Setting the Effective Date of a Scheduled Enrollment in Self–Service Benefits Self–Service Benefits provides different ways of controlling the date on which the application records a participant election: • • • The Change Session Date web page (for testing environments in both Standard and Advanced Benefits) The Change Session Date menu parameter (Standard Benefits) Normal date processing based on the session date (Advanced Benefits) The Change Session Date web page lets you test future–dated elections.2 Implementation Guide .

displayDate=Y&sessionDate=12/31&pFromPersonSearch=Y&pFor mFunction=BEN_SS_MGR_SRCH You enter the session date in mm/dd format. so you should not include a year in the session date parameter. Do not include the year. the application sets the session date to the current year. Note: You should remove this web page from your production environment by setting displayDate=N so that benefits participants cannot alter their enrollment date. Deriving the Year of the Session Date The application derives the year to use for the session date. If you enter a session date that is later than the system day and month. If you enter a session day and month that is prior to or equal to the system day and month. the application uses the following year. Benefits 17–29 .

When you remove the Benefits Enrollment Overview page. 17–30 Oracle SSHR 4. or if you use Advanced Benefits and process unrestricted program enrollments. For example: • • BEN_SS_BNFT_ENRT (Self–Service Benefits Enrollment – Employee) BEN_SS_MGR_ENRT (Self–Service Benefits Enrollment – Internal Use) 4.2 Implementation Guide . Choose the Form tab. 3. participants can still view their past. Update the seeded parameter to disallow enrollments by setting allowEnrt=N. it is recommended that you remove the Benefits Enrollment Overview web page from your Self–Service Benefits implementation during those periods when you do not want participants to enter or update benefits elections. " To remove user access to the Benefits Enrollment Overview page: 1. Log in to Oracle HRMS using a System Administrator responsibility and open the Form Functions window. Choose the Description tab. 6. 5. 2. Query the Function Name for which you want to set the session date. current.Removing the Benefits Enrollment Overview Web Page (Standard Benefits) If you use Standard Benefits. Save your work. and any future elections using the Current Benefits Overview web page.

9. 4. Choose the Usages button. Select a To Be Sent code of Not Applicable. See: Benefits Enrollments: page 17–10 for a list of the required short names for each web page region. 3. Exclude the BEN prefix from the regionname portion of the short name. 7. such as the presence of a life event or enrollment in a particular compensation object. " To define a communication type: 1. 2. 6. You can vary the instruction text that displays in a region based on different criteria. Enter a Short Name for this communication type.Defining Self–Service Instruction Text Use the Communication Types window in the Professional User Interface to define regional instruction text for Self–Service Benefits Enrollments and Individual Compensation Distributions.REGIONNAME. Save your work. Enter instruction text in the Self Service Instruction Text field that corresponds to the region of the self–service web page that you are configuring. Select a Usage Rule if your criteria for determining the conditions under which instruction text is generated cannot be fully accommodated by the usage criteria on this window. 5. Select a value for one or more of the following parameters to limit the conditions under which instruction text is displayed. You must enter the short name in the following format: BEN. Note: Self–Service uses the short name to link the instruction text you write to a specific region in a Self–Service Benefits web page. • • • • • • Life Event Program Plan Plan Type Enrollment Period Action 8. Select a Usage type of Self Service Instruction Text to indicate you are configuring a self–service web page. Enter a Name for the communication type you are defining. Benefits 17–31 .

Save your work.2 Implementation Guide .10. 17–32 Oracle SSHR 4.

Select an enrollment action type in the Type field to specify a generic action a person must resolve in order to enroll in a compensation object. You then link the action type to a program or a plan as part of your enrollment requirements. You also use this window to edit messages for incomplete action items for Oracle Self–Service Human Resources benefits enrollments. 4. Note: The description text appears as a message when a self–service user is required to complete an action item before an enrollment is valid. Enter a description of the enrollment action type in the Description field. 2. " To define additional enrollment action types: 1. Save your work. Enter a name for the enrollment action type you are defining in the Name field. Benefits 17–33 . 3.Defining Additional Enrollment Action Types (Advanced Benefits) You use the Enrollment Action Types window to rename an action type delivered with the system.

17–34 Oracle SSHR 4.2 Implementation Guide .

For primary care provider searches. " To maintain primary care providers for a plan: 1. Select a Designation Code to indicate if a participant who enrolls in this plan is required to select a PCP. Select the Name of the plan for which you are maintaining primary care provider data. you must link an organization to this plan (using the Maintain Plan Related Details window) which has an Organization Role Type of Primary Care Provider Locator. or be required. Select a Start Date Code that indicates when the selected provider becomes the participant’s primary care provider. 5. You use the Maintain Plan Primary Care Providers window to define restrictions for the selection of a primary care provider. Note: If you do not check the From Repository field. The participant must enter the PCP ID number or name in a free form text field. or if PCP selection is optional.Maintaining Primary Care Providers for a Plan Based on your plan design. Select a Dependent Designation Code to indicate if a participant who enrolls in this plan is required to select a PCP for each dependent covered by the plan. to select a Primary Care Provider (PCP) when electing a benefit plan. benefits participants may have the option. 9. Check the From Repository field if you are using Oracle Self–Service Benefits and the benefits participant selects a primary care provider through a searchable database of providers. 3. Note: The Can Keep Provider field is reserved for future use. Check the Radius warning field to issue a warning message to the participant indicating that the selected PCP is outside the range 6. 2. 7. Note: As a prerequisite. select the maximum Radius in miles which the PCP database should consider when returning the results of a search query. 8. Enter the number of times a participant is permitted to change primary care providers per month in the Number of Changes Allowed field. or if PCP selection is optional. You also use this window to set high level configuration options for web–based PCP database searches that are performed through Oracle Self–Service Benefits. a participant cannot select a PCP from a list of valid PCPs. Benefits 17–35 . 4.

Choose the Plan Restrictions button if the requirements for designating a primary care provider for this plan vary based on the primary care provider type (such as Gynecology or Pediatric Medicine) and the age or gender of the benefits participant. Save your work and close the Plan Primary Care Provider Restrictions window. a participant cannot select a PCP outside the radius. 12. 14. you would need to specify designation restrictions at the option level. or if PCP selection is optional. 13. Note: This warning only occurs in the professional forms user interface. if a participant who elects participant only coverage is not required to select a PCP. but a participant who elects employee plus spouse coverage is required to select a PCP for dependent coverage. 16. Checking this field lets a participant override the warning and select a PCP outside the prescribed range. instead of the plan level. 17–36 Oracle SSHR 4. Note: If you do not check this field. Select a Designation Code to indicate if a participant who enrolls in this option is required to select a PCP.2 Implementation Guide . 10. Note: The Plan Restrictions button is only activated if you check the From Repository field. not in Self–Service Benefits. Select the option for which you are specifying PCP designation requirements in the Options field. Save your work. Select a primary care provider type for which you are specifying PCP designation requirements based on the age or gender of the benefits participant. You maintain primary care provider types using the Lookup Type BEN_PCP_SPCLTY if your primary care providers are stored in an external repository. Select a Dependent Designation Code to indicate if a participant who enrolls in this option is required to select a PCP for each dependent covered by the plan.allowed by the plan. Note: For example. Choose the Option Restrictions button to open the Plan Primary Care Provider Restrictions window if the requirements for designating a primary care provider differ between the options in the plan. 15. or if PCP selection is optional. 17. 11. Use the Lookup Type BEN_PRMRY_CARE_PRVDR_TYP if your PCPs are not stored in a repository.

Benefits 17–37 . such as female for a gynecology provider. Select a Gender Allowed Code of Female or Male to restrict the selection of this provider type to one gender. Enter a Minimum Age if the participant must be of a minimum age or older to select this provider type.18. Enter a Maximum Age if the participant must be of a maximum age or younger to select this provider type. such as a pediatric care provider. such as a geriatric care provider. 19. 20.

you use the Regions window to configure information such as the URL of the information provider and the Document Type Definition (DTD) used by the search. select the Ben PCP Server Proxy Set attribute and enter true in the Long Label field. 2.0 or 3.2 Implementation Guide . Self–Service Benefits also supports free form text entry of primary care providers without validation when a repository of PCP data is not used. Select the Ben PCP XML DTD attribute and enter the URL of the XML Document Type Definition in the Long Label field. 17–38 Oracle SSHR 4. the XML transaction must conform to version 2. Select the Ben PCP Info Provider Client ID attribute and enter the Client ID given by the information provider in the Long Label field. Setting up an XML–Enabled Primary Care Provider Search If the search criteria entered by a benefits participant is formatted as an XML search request for use with a database of primary care providers (maintained by your enterprise or a third party). 6. Note: Enter the URL as you would in the Address or Location field of your web browser. Follow the instructions below based on the search type configured by your enterprise. a benefits participant can select a primary care provider (PCP) for a benefit plan. • If you do not use a proxy server. Do not enclose the URL in quotations. 3.Configuring the Primary Care Provider Search Facility As part of a self–service enrollment. The DTD version you use should correspond to your Client ID. Click the Region Items button. " To set up an XML–enabled primary care provider search: 1. If you use a proxy server to access an external web site. you can configure Self–Service Benefits so that a participant can select a primary care provider through a web–based search of a PCP database. enter false. Select the Ben PCP Provider Information attribute and enter the URL of the information provider in the Long Label field. Note: Currently. As a system administrator. 5. 4.0 of the GeoAccess DTD . Query the Region ID BEN_PCP_XML_REQUEST_PARAMS.

Query the Region ID BEN_PCP_SELECT_SEARCH_TABLE. select the Ben PCP Proxy Host attribute and enter the URL of the proxy server in the Long Label field. 10. Setting Up a Primary Care Provider Search without XML Formatting Customers who create a search page which does not format the PCP query in XML can follow these guidelines for a creating a PCP search that is compatible with Self–Service Benefits. If you use a proxy server. Open the Regions window. such as 1. it is recommended that the maximum number of records be set to 100 or less.0 8. Benefits 17–39 . A system administrator or application developer creates a search page that performs the query and accepts the following page–context variables: • • • 5. 4. Click the Region Items button. " To set up a primary care provider search without XML formatting: 1. Select the Ben PCP XML Version attribute and enter the version of XML you are using in the Long Label field. PcpPersonId = (Person ID of the person for whom you are searching for a primary care provider ) PcpPlId = (Plan ID defined for the plan in the database) PcpPlTypId = (Plan Type ID defined in the database) Note: You do not need to use these variables if they are not required for your search or validations. select the Ben PCP Server Proxy Port attribute and enter the port number (typically 80) in the Long Label field. 11. Select the ICX_IMAGE_FILE_1 attribute and enter the URL in the URL field that is accessed when a participant clicks the Search button on your custom Search web page. If you use a proxy server.7. 2. 3. 9. Note: For best performance. Select the Ben PCP Max Records attribute and enter the maximum number of records to be returned by the query in the Long Label field. Select the Ben PCP Request Method attribute and enter the HTTP request method expected by the information provider (such as GET or POST) in the Long Label field.

2 Implementation Guide . the following URL must be used to return to the search page: • /OA_HTML/OA. If the search is successful.6. MD (doctorsName) Internal Medicine. Pediatrics (specialty) 905 (planId) PcpPersonId Number 928374655 (personId) PcpTypCd Number 23 (pcpTypCd) The URL returned by the search should look like this: • /OA_HTML/OA.jsp?akRegionCode=BEN_PCP_SELECT_PAGE &akRegionApplicationId=805&pcpSearchCancel=1. If the search is canceled without a selection of a PCP. 7. Name of the primary care provider Specialties of the primary care provider The plan ID that corresponds to the plan name The person ID passed to the database as part of the query The code of the first primary care provider specialty that is returned by the query Value Number String String Number Example 10154244 (id) Sue Jones. Note: Replace the directory OA_HTML with the base HTML directory of your installation. the URL accessed by the query must return the following information (properly formatted) with the following parameter names and data types as shown in the table below: PCP Parameters and Data Types Parameter Name ExtIdent PcpName PcpSpecialty PcpPlId Data ID of the primary care provider per the plan.jsp?akRegionCode=BEN_PCP_SELECT_PAGE &akRegionApplicationId=805&ExtIdent=id&PcpName=doctors Name&PcpSpecialty=specialty&PcpPlId=planId&PcpPersonId= personId&PcpTypCd=pcpTypCd Note: Replace the directory OA_HTML with the base HTML directory of your installation and replace the variables in the URL with the actual values. 17–40 Oracle SSHR 4.

US Federal Benefits .US Federal 18–1 .CHAPTER 18 Benefits .

refer to Setting up FEHB: page 18–29 18–2 Oracle SSHR 4. federal employees can change their benefits selection only when a valid life event change occurs. contact the employee to correct and resubmit the elections. you no longer enter FEHB information when processing the RPA (the RPA health benefit extra information is disabled). Now. Similarly. Previously. the HR professional can initiate a life event for the employee. such as the addition of a dependent or change in primary address. Other life events result from the employee entering or changing his or her personal details. refer to Administering FEHB. If the employee does not have access to a computer. With the exception of employees who waive the pre–tax deductions. the personnelist captured the employee’s enrollment information through the RPA health benefits extra information or through manual updates to the health benefits elements. the personnelist can transfer the data from the employee’s SF–2809. The Office of Personnel Management defines 13 life events that permit benefits enrollment or changes to benefit elections.2 Implementation Guide . such as when a family member loses coverage due to discontinuance of a FEHB plan. you no longer manually update the FEHB elements (Health Benefits and Health Benefits Pre–Tax). the application sends an FYI notification to the Personnel Office (POI) groupbox.Federal Employee Health Benefits Overview Federal government employees can elect.: page 18–3 For information about setting up the programs and plans used by federal health benefits. In these cases. The information entered in self–service is the same information needed to complete the SF–2809 (Health Benefits Election Form for Federal Employees). For further information about administering Federal Employee Benefits. As a consequence of this new functionality. change. The application simplifies the process of determining health benefit eligibility through life events. Some life events are not automated. The personnelist can review the linked confirmation page and. if necessary. When an employee enrolls or changes his or her health benefits. Some life events result from RPA updates such as an Appointment action or Change in Duty Station personnel action. employees and HR professionals enroll and manage their FEHB benefits using self–service or the Standard Benefits professional user interface. or cancel Federal Employee Health Benefits (FEHB). or consult with the employee and then make the necessary elections through the professional user interface.

Live events are triggered through: Benefits . Conversely. See: Overriding Eligibility Participation Information for a Person in a Program or Plan: page NO TAG Enrollment Management Electable benefit choices occur as a result of one of the OPM defined permissible life events. you could waive the person’s participation in the plan so that he or she could enroll in another plan. Employees may elect a plan that is specific to their state or county of residence. The only exception occurs for in–state moves. you can waive an eligible person’s participation in a plan. you must manually initiate a potential life event. Employees participating in Federal Employee Health Benefits may elect one of the predefined plans and options installed during the initial set up of FEHB.Administering FEHB You administer the US Federal Health Benefits and manage enrollment using Standard Benefits. If this occurs. For in–state moves. or a plan specific to their work location. In that case. such as a Change of Duty Station or Change in Primary Address. See: Manually Creating a Potential Life Event for a Person: page NO TAG.) If the employee’s primary residence or duty station changes.US Federal 18–3 . (Overseas employees are only eligible for nationwide plans. For example. so you would grant an exception. you can grant an exception so that an ineligible person can enroll in a plan or option. Enrollment management is the process of registering your employees and their dependents FEHB plans and options. the employee may become ineligible for FEHB. the application detects the change and triggers a life event that permits the employee to change his or her benefit elections. Note: For the application to detect a change in primary address. the employee could neither select nor remain with the plan. Plan Eligibility An employee’s plan enrollment eligibility is based on work or residence location. For example. it is necessary to override eligibility results. if you extend an employee’s Leave Without Pay (LWOP) beyond 365 days. enter all employee addresses using the US or US global address style. Viewing a Person’s Life Event Information: page NO TAG In some cases. if the OPM dropped a plan from a FEHB program.

713. or HR Manual RPA (NOACs 500–599) and HR Manual 1D RPA (NOACs 781.148. 108. 101.150–171) The NTE Date must be greater than 365 days. 108. or HR Manual Manual Manual or HR Manual RPA or Manual RPA (NOACs 100. • • The following table lists the life event triggers for the predefined OPM life events. only through the professional interface. Note: You cannot initiate these events through self: service. 115.• RPA update: Request for Personnel action has been updated to the database. 115. Life Event Code Life Event Life Event Triggers 1A Initial Opportunity to Enroll RPA (NOACs 100. 107. 107. or in the Non–Flex enrollment window HR Manual: The personnelist initiates a potential life event through the professional user interface. 703. 741) 18–4 Oracle SSHR 4. 150–171) The NTE Date must be greater than 365 days. Address window. 500–599. 721. 782. Manual changes: The employee initiates a change in self–service health benefits. or a personnelist changes data in either the Person window. 101. 702. 740. 148. or HR Manual HR Manual 1B 1C 1D 1D Open Season Change in Family Status Change in Employment Status Re–employment after a break in service of more than three days 1D Return to pay status following loss of coverage due to expiration of 365 days of LWOP status of termination of coverage during LWOP Return to pay sufficient to make withholdings after termination of coverage during a period of insufficient pay Restoration to civilian position after servicing in uniformed services Change from temporary appointment to appointment that entitles employee receipt of government contributions Change to or from part–time career employment 1D HR Manual 1D 1D RPA (NOACs 100–199) and LAC is QAK.2 Implementation Guide .

Section 8906a) Salary of temporary employee insufficient to make withholdings for plan in which enrolled HR Manual 1F RPA (NOACs 792. 703.US Federal 18–5 . 741) HR Manual 1G 1H Open Season or HR Manual 1I HR Manual 1J HR Manual 1K 1L HR Manual HR Manual 1M HR Manual Manual Changes Employees use benefits self–service to manually enroll and make changes to their benefits.C. 702. A personnelist can manually initiate life events (HR Manual) for an employee. of a FEHB plan Loss of coverage under a Federal group health plan because an employee moves out of the commuting area to accept another position and the employee’s non–federally employed spouse terminates employment to accompany the employee Employee or covered family member in a Health Maintenance Organization moves or becomes employed outside the geographic area from which the carrier accepts enrollments. in whole or part. 713. moves or becomes employed further from this area On becoming eligible for Medicare Temporary completes one year continuous service under (5 U. 740. HR Manual intervention is often required when: Benefits .Life Event Code Life Event Life Event Triggers 1E Separation from Federal employment–employee or employee’s spouse pregnant Transfer from a post of duty within the US to a post of duty outside the US or reverse Employee or eligible family member loses coverage under FEHB or another group plan Employee or eligible family member loses coverage due to the discontinuance. 721. as well as enroll the employee or make changes to that person’s benefit selections. or if already outside the area.S. 500–599.

when you Cancel an Appointment and have to back out potential life events created for that person. such as an employee or eligible family member losing coverage under FEHB or another group plan. and the Non–Flex Enrollment window to enroll and administer benefits for participants. back out or void life events. See: Enrolling a Person in a Non–Flex Program: page NO TAG. or a change in your home address. A Cancellation or Correction action requires that you back out a life event. such as a change in marital status From Date of the primary address RPA’s effective date or the Occurred DAte that the personnelist entered when the personnelist created the potential life event Change in Family Status A Change in Family Status can occur for many reasons. The following table lists the source of the information used for the occurred on date. update. the application generates a Change in Family Status. divorce. such as a marriage. or delete a contact. 18–6 Oracle SSHR 4. legal separation. • Two different windows enable you to make these changes. As a result. You use the Potential Life Event window to manually initiate. the birth or death of a family member. the Change in Family Status encompasses several sub–events: • Change in Dependents: when you add. Occurred On Source Date Used RPA action Person window Address window Self–Service benefits RPA’s effective date Effective date of the data change. Manually Creating a Potential Life Event for a Person: page NO TAG Effective Dates Life Event Occurred On Date The application determines the date on which a life event occurs based on the effective date or the user–entered date.2 Implementation Guide . for example.• • An employee does not have access to a computer The life event is not one that is automatically detected. Viewing a Person’s Life Event Information: page NO TAG.

Pre–Tax and After–Tax Plan Options The employee has the option upon initial enrollment to choose a plan with a pre–tax or after tax option. The employee can then update his or her current benefit elections. The reasons that you might make a change in dependents is to record a birth or death of a family member. he or she can contact the personnelist who can then process a potential life event (After Tax Deductions). no life event is required for the employee to: • • • Terminate health benefits by declining coverage (pre–tax employees can only terminate coverage with a valid life event) Change to a lower option. such as Open Season or a Change in Dependents. the application generates a Change in Family Status life event Change in Primary Address: when an employee changes the state designation in the primary address or the personnelist makes the change through the professional user interface. If an employee later wants to change from a pre–tax to an after tax option. Similarly. the application generates a Change in Family Status life event.US Federal 18–7 . Marital Status. Change in Family Status) in the Potential Life Events window. The personnelist can then make the necessary benefit changes in the Non–Flex Enrollment window or have the employee make the necessary changes in self–service. or a High to Low option Change to Pre–Tax Benefits .Note: You cannot delete a contact until you end–date that contact information in the Contact window. the application generates a corresponding Change in Family Status life event. • Each time an employee makes a change in self–service that initiates one of these sub–events (Change in Dependents. a personnelist manually initiates a potential life event for one of the sub–events by initiating the parent life event. the employee must wait until a valid life event occurs. or Primary Address). • Change in Marital Status: when the employee changes his or her marital status in self–service or the personnelist changes the marital status in the professional user interface. If the employee does not want to wait. for example change from Family to Self. For employees on after–tax deductions.

for example a Change in Duty Station.2 Implementation Guide . or if the life events have closed.After the personnelist initiates an After Tax Deductions life event. you would void the life event. if you Cancelled an updated Appointment action. See: Viewing a Person’s Life Event Information: page NO TAG. Manually Creating a Potential Life Event for a Person: page NO TAG.the personnelist must change the end date. back out the life events and if appropriate. Viewing Electable Choices for a Person Based on a Life Event: page NO TAG. As another example. you must void the life events if they are still open. For example. if you Corrected an action. the employee can choose to keep the current option level or change to a lower option. Manually Creating a Potential Life Event for a Person: page NO TAG. To extend the election period. and then back it out. the employee cannot make the changes through self–service. If you process a retroactive action in which the end date for election period has expired. you would close the life event if it was still open. Viewing Electable Choices for a Person Based on a Life Event: page NO TAG Cancellations and Corrections If you process a Cancellation or Correction action for an employee and the original RPA triggered potential life events. Retroactive Actions The application automatically enters the start and end dates for the election period based on the amount of time authorized by the OPM for each life event. process new life events. and the Initial Opportunity to Enroll life event was subsequently detected. or close the event and initiate a new life event from the Life Events window. See: Viewing a Person’s Life Event Information: page NO TAG. Manually Voiding a Potential Life Event for a Person: page NO TAG 18–8 Oracle SSHR 4.

See: Defining Self–Service Instruction Text: page 17–31 Hidden Fields: This topic also lists––by web page region––all fields the application delivers as hidden which you can display using the Personalization Framework. plan type. the Full Name field uses the format ’Prefix Last. by default all person name fields in Self–Service Benefits display names in the format ’First Last Suffix’ (without commas between the parts of the name. plan.Benefits Enrollments This topic provides reference information you need to configure your Self–Service Benefits web pages using the Personalization Framework. Benefits . In the US. or life event. the tables below list––by web page region––the communication short name and the valid communication usages that are required when you define a communication type to display instruction text for a particular program. For instruction text. Benefits participants can add another person to the Family Members and Others table by choosing the Add Another Person button.0 Self–Service Benefits Enrollment – Employee Self–Service Benefits Enrollment – Federal Configurable Pages and Shared Regions The following definitions can be configured using the Personalization Framework: Family Members and Others. Menu and Function Names This module can be accessed from the following menus and functions: User Menu Name Function Name Employee Self–Service v4.US Federal 18–9 .0 Employee Self–Service v4. and Family Members and Others Detail Page The Family Members and Others page enables a participant to view a record of their family members and other persons enrolled as dependents or beneficiaries of their benefits. For example.) You can add the Full Name field to a web page and remove the delivered Name field. First Middle Suffix’. which opens the Family Members and Others Details page.

the application opens the Current Benefits page. Life Event Program. However.FAM_ADD_ADDRESS Program. Note: It is recommended that you provide instruction text indicating that eligibility for benefits may be based on family members.Program. Life Event Family Members and Others Detail Page Region Tip Type Message Name Required Communication Short Name Valid Communication Usages Add or Update Family Members Name and Relationship Address Instruction Instruction Instruction FML.FAMILY_MBRS_CONTENT Valid Communication Usages Members Content Family Members Content Instruction Help Tip Program.2 Implementation Guide . If you define a life event reason of the type ’Personal. Hidden Field: Use the BEN_FAMILY_MBRS_TABLE region to add the hidden Full Name field to the page and to remove the Name field if necessary. Life Event TENT FML.This page only displays when a person has either: • • • An enrollment opportunity Eligibility for an unrestricted program A detected or unprocessed potential life event as of the system date If one of these conditions does not exist.’ you can trigger a life event when a person enters a contact on the Self–Service Human Resources Contacts page and selects a relationship start reason.FAM_ADD_CON. The seeded life event reason of Added During Enrollment prevents a life event from occurring when you create a family member or update a family member’s details. Life Event 18–10 Oracle SSHR 4. you cannot use communication usages to restrict the display of instruction text to a compensation object or a life event for the Family Members page. Family Members and Others Region Tip Type Message Name Required Communication Short Name FML.FAM_ADD_NA ME FML.

FAM_ADD_SECOND_MEDICAL Program. Life Event Second Medical Cover.US Federal 18–11 .Region Tip Type Message Name Required Communication Short Name Valid Communication Usages Miscellaneous Information Instruction FML.FAM_ADD_OTH. Life Event ER FML.Program. Hidden Fields: You can use the following regions to add the hidden Full Name field to the page and to remove the Name field if necessary.Instruction age Address Name and Relationship Address Miscellaneous Information Miscellaneous Information Help Tip Hint (Suffix) Hint (Postal Code) Hint (National Identifier) Hint (Date of Birth) Message (Required Field Missing) Message (Invalid Birth Date) 92638 92639 92640 92637 92601 92598 __ __ __ __ __ __ __ __ __ __ __ __ Configurable FlexFields Family Members and Others Page Region Flex Name Flex Code Add or Update Family Members Miscellaneous Information Further Person Information Additional Contact Relationship Details hrpersondevdfflex Add Cont Details D Flexfield See: Configuring Flexfields: page 7–6 Benefits Enrollment Overview Page The Benefits Enrollment Overview web page enables a participant to view a record of their current benefits and to enroll into a new set of benefits. • BEN_OVW_SELECTIONS_TABLE • BEN_OVW_CVRD_DEPS_TABLE Benefits .

OVERVIEW_CVRD_DEPS BEO. Life Event Program. Life Event Program. Life Event Program. Life Event Program.FLEX_CREDITS BEO.ENRL_OVERVIEW_PCP 92570 –– Valid Communication Usages Enrollment Overview Content Flex Credits Flex Credit Summary Flex Credit Rollovers Benefit Selections Covered Dependents Beneficiary Enrollment Overview Primary Care Providers Enrollment Overview Enrollment Overview Content Enrollment Overview Content Instruction Instruction Instruction Instruction Instruction Instruction Instruction Instruction Program. Life Event Program.OVERVIEW_SELECTIONS BEO. Benefits Enrollment Overview Page Region Tip Type Message Name Required Communication Short Name BEO. or––if you are displaying multiple rates for the compensation object––to the rate you have defined with 3 in the Self Service Display Order field.2 Implementation Guide . Life Event Program. If you are displaying multiple rates. 18–12 Oracle SSHR 4. Life Event Message (No Enrollment Opportunity.• BEN_OVW_BENEF_TABLE • BEN_OVW_PCP_TABLE You can use the BEN_OVW_SELECTIONS_TABLE region to display a column for the taxable cost of a benefit. you can also display the Cost 2 (After Tax Cost) and Cost 4 (Miscellaneous) columns to show the rates you have defined with 2 and 4 in the Self Service Display Order field. Brief Message) Message (No Enrollment Opportunity. Life Event Program.OVERVIEW_FC_SUMMARY BEO. These columns show the coverage start and end dates for each election. This column corresponds to a standard rate with an activity type of Self–Service Display. Detail Message) –– 92571 –– –– Current Benefits Overview Page The Current Benefits Overview web page enables a participant to see a record of their current benefits.FLEX_CREDIT_ROLLOVERS BEO.ENRL_OVERVIEW_CONTENT BEO. You can also use the BEN_OVW_SELECTIONS_TABLE region to display Coverage Start and End Date columns.ENRL_OVERVIEW_BENEF BEO.

Brief Message) Message (No Current Enrollment.FLEX_CREDIT_ROLLOVERS CBO. Benefits .CURRENT_OVERVIEW_CONTENT CBO. Detail Message) Program Program Program Program Program Program Program __ 92573 __ __ Benefits Selection Page The Benefits Selection page enables a participant to select one or more plans in which to enroll. These columns show the coverage start and end dates for each election. Current Benefits Overview Page Region Tip Type Message Name Required Communication Short Name CBO.FLEX_CREDITS CBO.OVERVIEW_PCP 92572 __ Valid Communication Usages Current Benefits Overview Content Flex Credits Flex Credit Summary Flex Credit Rollovers Benefit Selections Covered Dependents Beneficiary Overview Primary Care Providers Overview Current Benefits Overview Content Current Benefits Overview Content Instruction Program Instruction Instruction Instruction Instruction Instruction Instruction Instruction Message (No Current Enrollment.OVERVIEW_SELECTIONS CBO.US Federal 18–13 .ENRL_OVERVIEW_BENEF CBO.Hidden Fields: You can use the following regions to add the hidden Full Name field to the page and to remove the Name field if necessary.OVERVIEW_CVRD_DEPS CBO.OVERVIEW_FC_SUMMARY CBO. • BEN_OVW_CVRD_DEPS_TABLE • BEN_OVW_BENEF_TABLE • BEN_OVW_PCP_TABLE You can also use the BEN_OVW_SELECTIONS_TABLE region to display Coverage Start and End Date columns.

verify that you have linked the appropriate life events to the program or plan enrollment requirements in the Dependent Change of Life Event window. Long Tip) Help Tip (Enter Benefit Amount Input Box. Life Event Program. Plan Type.ENRT_SELECTION_SELECT_AREA Valid Communication Usages Enrollment Selection Content Top Flex Credit Region Bottom Flex Credit Region Selection Area Selection Area Selection Area Instruction Instruction Instruction Instruction Help Tip (Certification Legend) Help Tip (Enter Annual Rate Input Box. Long Tip) Message (Enter Rate. Life Event Program.2 Implementation Guide . Long Tip) Message (Enter Annual Rate.ENRT_SELECTION_CR_BOTTOM BNS. 18–14 Oracle SSHR 4. Life Event Program.ENRT_SELECTION_CR_TOP BNS.Region Tip Type Message Name Required Communication Short Name BNS. Life Event Selection Area Selection Area Selection Area Selection Area Selection Area Selection Area Selection Area Dependents Selection Page The Dependents Selection page enables a participant to add their dependents to a plan. Note: For Advanced Benefits customers: if participant dependents are not displaying in this page. Hidden Field: Use the BEN_ENRL_DEPEN_SELECTION_TABLE region to add the hidden Full Name field to the page and to remove the Name field if necessary.ENRT_SELECTION_CONTENT BNS. Long Tip) Message (Enter Benefit Amount Tip) Message (Tokens for above messages) Message (Tokens for above messages) BEN_ENRT_ANN_RT VAL_TIP BEN_ENRT_BNFTAM T_TIP BEN_ENRT_RTVAL_T IP BEN_ENRT_SLECT_TI P_ANY_AMOUNT BEN_ENRT_SLECT_TI P_ANY_VALUE Program. Long Tip) Help Tip (Enter Rate Input Box.

ENRL_DEPENDENTS_CONTENT_PL 92588 __ Valid Communication Usages Dependents Selection Dependents Selection Instruction Instruction –– Program. Benefits . you can configure this page to allow web–based searches of a database of provider information. Region Tip Type Message Name Required Communication Short Name BFS. Plan Type. Life Event Dependents Selection Hint (Dependent Table) Message (Can’t Designate) Program. Plan.BENEFICIARY_CONTENT BFS.BENEFICIARY_CONTENT_PLAN BFS. Hidden Field: Use the BEN_BENEF_SELECTION_TABLE region to add the hidden Full Name field to the page and to remove the Name field if necessary. Plan Type. Life Event Program. Plan Type.BENEFICIARY_CONTENT_ORGS Valid Communication Usages Beneficiary Selection Beneficiary Selection Family Members and Others Organizations Beneficiary Totals Table Beneficiary Selection Instruction (Page) Instruction (Plan Level Table) Instruction Program.US Federal 18–15 . Life Event Instruction Hint Message (Can’t Designate) 92587 __ __ Primary Care Provider Page The Primary Care Provider page enables a participant to select a care provider.BENEFICIARY_CONTENT_FAMILY BFS.Dependents Selection Page Region Tip Type Message Name Required Communication Short Name –– DPS. Life Event Program. Plan. Plan. Plan Type. Plan. Life Event __ Dependents Selection Beneficiary Selection Page The Beneficiary Selection page enables a participant to add their beneficiaries to a plan. If your enterprise partners with a third party supplier of primary care provider information.ENRL_DEPENDENTS_CONTENT DPS. Life Event Program.

Plan. and Specialty fields. you must load the available data as provided by GeoAccess into the corresponding Lookup Codes using the Application Utilities Lookups window in the Professional User Interface. Hospital. • BEN_PCP_SEARCH_TABLE • BEN_PCP_SELECT_TABLE On the Primary Care Provider Search page. Plan. School.PcpSelectContentPageLevel PCP. For the Physician Group. The hidden fields of Location. Life Event 18–16 Oracle SSHR 4. and Degree are reserved for future use. Plan Type. Life Event __ __ Primary Care Provider Summary and Search Pages Hidden Fields: You can use the following regions to add the hidden Full Name field to the page and to remove the Name field if necessary.See: Configuring the Primary Care Provider Search Facility: page 17–38 Region Tip Type Message Name Required Communication Short Name PCP.PcpSelectContentPlanLevel __ 92567 __ Valid Communication Usages Primary Care Provider Selection Content Primary Care Provider Selection Content Primary Care Provider Selection Content Primary Care Provider Selection Content Instruction Instruction Hint Message (Can’t Designate) Instruction Instruction Program. Language. Plan. you can use the BEN_PCP_SEARCH_CRITERIA region to add the hidden fields of Physician Group and Hospital. • • • • Region Tip Type BEN_PCP_MED_GRP BEN_PCP_HOSPITAL BEN_PCP_LANGUAGE BEN_PCP_SPCLTY Message Name Required Communication Short Name PCS. Life Event Program.PCP_SEARCH_C RITERIA Valid Communication Usages Primary Care Provider Search Search Instruction Instruction Program. Plan Type. Life Event Program.PCP_SEARCH PCS. Plan Type.2 Implementation Guide .

Note: You can also use the Confirmation page to display a signature region for participants to print from their web browser. you can also display the Cost 2 (After Tax Cost) and Cost 4 (Miscellaneous) columns to show the rates you have defined with 2 and 4 in the Self Service Display Order field. • BEN_OVW_BENEF_TABLE • BEN_OVW_CVR_DEPS_TABLE • BEN_OVW_PCP_TABLE You can use the BEN_OVW_SELECTIONS_TABLE region to display a column for the taxable cost of a benefit. These columns show the coverage start and end dates for each election. or––if you are displaying multiple rates for the compensation object––to the rate you have defined with 3 in the Self Service Display Order field.PCP_SEARCH_R ESULT Valid Communication Usages PCP Result Table Ben PCP XML Request Params Ben PCP XML Request Params Instruction Tip Message (No PCPs found) Program. You can also use the BEN_OVW_SELECTIONS_TABLE region to display Coverage Start and End Date columns. You can personalize the BEN_ENRL_CONF_CONTENT region to display the signature field. Plan.Region Tip Type Message Name Required Communication Short Name PCS. This column corresponds to a standard rate with an activity type of Self–Service Display. Benefits . Plan Type. If you are displaying multiple rates.US Federal 18–17 . Use this region if you require a participant’s signature as part of a benefits enrollment. Hidden Fields: You can use the following regions to add the hidden Full Name field to the page and to remove the Name field if necessary. Life Event Confirmation Page The Confirmation page enables a participant to see a summary of their choices and a warning of any oversights or miscalculations they may have made.

OVERVIEW_CVRD_DEPS BEC.2 Implementation Guide . Life Event Program.FLEX_CREDIT_ROLLOVERS BEC.ENRL_CONF_CO Program. Life Event Program.OVERVIEW_SELECTIONS BEC.FLEX_CREDITS BEC.ENRL_CONF_PC P 92605 92606 __ __ Program. Life Event NTENT BEC. Life Event Message (Confirmation Success) Message (Action Item Warning) __ __ Configurable FlexFields Confirmation Page Region Flex Name Flex Code Benefit Selections Additional Ben Prtt Enrt Rslt F Details N/A Unused Flex Credits Page The Unused Flex Credits page provides a summary of the flex credits left unspent by a participant. 18–18 Oracle SSHR 4.ENRL_CONF_BE NEFICIARIES BEC.Region t Tip Type Message Name Required Communication Short Name Valid Communication Usages Ben Enrollment Confirmation Content Flex Credits Flex Credit Summary Flex Credit Rollovers Benefit Selections Covered Dependents Beneficiaries Enrollment Confirmation Primary Care Providers Enrollment Confirmation BEN_ENRL_CONF_W ARNINGS BEN_ENRL_CONF_W ARNINGS Instruction Instruction Instruction Instruction Instruction Instruction Instruction Instruction BEC. Life Event Program. Life Event Program. Life Event Program.OVERVIEW_FC_SUMMARY BEC. Life Event Program.

UNUSED_FLEX_CREDIT_CONTENT FLX. dental. you may want to perform system testing before the start of an open enrollment period.UNUSED_FLEX_CREDIT_NONE Valid Communication Usages Unused Flex Credits Content Unused Flex Credits Content Unused Flex Credits Content Unused Flex Credits Content Instruction Program. Life Event Instruction Program. See: Setting the Effective Date of a Scheduled Enrollment in Self–Service Benefits: page 17–28 Region Session Date Content Session Date Content Tip Type Instruction Tip (Effective Date) Message Name 92604 92637 Temporary ID Card Page The Temporary ID Card page lets a participant print an ID card which the participant can use to obtain medical.US Federal 18–19 . For example. This page should be removed in your production environment so that benefits participants do not alter their enrollment date.Region Tip Type Message Name Required Communication Short Name FLX. or other benefit treatment before the participant receives the official membership card from the provider. Life Event Message (No Unused Flex Credits) Message 92633 92632 __ __ __ __ Change Session Date Page The Change Session Date page lets you test future–dated elections. Benefits .

Plan. Life Event See: Configuring Web Pages: page 7–5 18–20 Oracle SSHR 4. Plan Type. Plan.ENRL_TEMP_ID _PAGE TMP.Region Tip Type Message Name Required Communication Short Name TMP. Life Event Program.ENRL_TEMP_ID _PLAN TMP.ENRL_TEMP_ID _CARD Valid Communication Usages Oracle Self–Service Human Resources Identification Card Ben Temporary ID Card Content Temporary ID Card Instruction Program.2 Implementation Guide . Life Event Instruction Instruction Program. Plan Type.

0 Self Service Benefits Enrollment –Employee menu. Deselect the Grants button to exclude this menu. 10. See: Configuring Tabbed Regions: page 7–7 See: User’s Menu (Oracle Applications System Administrator’s Guide) for more information on configuring menus. You can use the Personalization Framework to configure the appearance of the self–service web pages.US Federal 18–21 . Query the Self–Service Menu in the Menu field: HR_EMPLOYEE_DIRECT_ACCESS_V4. You can change menu names and function names. Its two prompts (Benefits Enrollment and Current Benefits) function as the labels on the tabs for the self–service web page. 8. 7. As a standard practice. Confirm that the Grants button is selected for the Benefits Self Service submenu. Log on to Oracle HRMS with the System Administrator responsibility. such as US Federal HR Benefits.Setting Up User Access to Self–Service Benefits Self–Service Benefits functions are attached to the Benefits Self–Service menu. " To set up user access to self–service benefits: 1. 9. Choose the Self–Service Benefits Enrollment – Federal function. 3. Add a new row for the US Federal benefits function. 2. The federal application uses this sub–menu.0. Benefits .0 You can change the menu name if required. 4. 5. Save your work and close the Menus window. The following Self–Service User Menu Name displays to users: • Employee Self–Service V4. or remove menus and functions if required. your changes will be overwritten the next time you apply a patch to the application. Open the Menus window. Enter a sequence number. Otherwise. Scroll through the list of functions and locate the Benefits v4. you should copy and edit all delivered menus you want to update. (GHR_SS_BNFT_ENRT). Enter a prompt. Note: The Benefits Self Service submenu is not linked to a top level menu. 6. 11.

See: Form Functions Window (Oracle Applications System Administrator’s Guide) 14. 13. Set the HR: Business Group Profile. Note: It is a good practice to check the Readme for each Self–Service Benefits patch you apply to see if the parameters and HTML Calls for the seeded functions have changed. You can use the Form Functions window to customize the predefined functions––GHR_SS_BNFT_ENRT. you can set up concurrent programs to automate this manual process. Use the System Profile Values window to link the responsibility you have created to your Business Group. Or. See: Users Window (Oracle Applications System Administrator’s Guide).2 Implementation Guide . Use the Form Functions window to create your own Self–Service Benefit functions from the sample functions supplied. The sample User Function Names are: • • Self Service View Current Benefits Self Service Benefits Enrollment BEN_SS_CURR_BNFT GHR_SS_BNFT_ENRT The Function Names are: • • If you update the seeded functions. Note: If you fail to link your Responsibility to your business group. one at a time. The Business Group Profile is: • HR: Business Group 16. you must update your custom function to use the seeded parameters and HTML Calls. benefits participants who attempt to enroll receive an error message indicating they cannot enroll. See: User Profiles (Oracle Applications User’s Guide and Oracle Applications System Administrator’s Guide) 15. There are two ways to do this.See: Personalization Framework: page 7–2. 12. Define the people you would like to access Self–Service Benefits. 18–22 Oracle SSHR 4. Link the responsibility you have created to a Security Profile and your Business Group. You can follow the typical steps for defining a new user and assign each user a responsibility that enables access to Self–Service Benefits.

US Federal 18–23 . available from MetaLink.See the White Paper titled: Batch Creation of User Accounts. Benefits .

To enable enrollment notifications. Note: If you do not see this string.Enabling Self–Service Benefits Enrollment Notifications You can configure Self–Service Benefits Enrollments so that an enrollment update generates a notification to an HR professional. Choose the Form tab. Query the function that you want to update. Replace the wfProcessName=FYI_NOTIFICATION_PRC portion of the parameter with your custom process name. 4. you must manually enter the parameter. 3. verify that the following parameter appears: displayDate=N&allowEnrt=Y&sessionDate=&sendFYINotification =N&wfProcessName=FYI_NOTIFICATION_PRC. In the Parameters field. Save your work. 6. Choose one of the following: • • Employee Self–Service (BEN_SS_BNFT_ENRT) Manager Self–Service (BEN_SS_MGR_ENRT) 2.2 Implementation Guide . To enable workflow notifications. you update one of the seeded functions in the Form Functions window using the system administrator responsibility. See: Enrollment Change Workflow Notifications: page 17–3 " To enable Self–Service Benefits Enrollment Notifications: 1. replace sendFYINotification=N with sendFYINotification=Y. 18–24 Oracle SSHR 4. 5.

you can set the session date to record all enrollments as of January 1st of the following year. Choose the Form tab. if you schedule your open enrollment period for the first two weeks in November. setting displayDate=Y displays the Change Session Date web page. Choose the Description tab. In the following example. 5. such as for an upcoming open enrollment period. 3. Update the seeded parameter to display the Change Session Date page or to set the effective date to a date you choose. Benefits . Query the Function Name for which you want to set the session date. Self–Service Benefits processes dates based on the date codes you select in your plan design. For example. Use the Change Session Date menu parameter if you use Oracle Standard Benefits and you want to record the life event occurred date of an enrollment for a date that is not equal to the system date.US Federal 18–25 . Setting &sessionDate=12/31 sets the session date to December 31st for the BEN_SS_MGR_ENRT function. " To set the session date in Self–Service Benefits: 1. Choose from: • • BEN_SS_BNFT_ENRT (Employee Self–Service Benefits) BEN_SS_MGR_ENRT (Manager Self–Service Benefits) 4. Note: You can use both features simultaneously. Log in to Oracle HRMS using a System Administrator responsibility and open the Form Functions window. but the date the user enters in the Change Session Date web page overrides the session date parameter for the current session. Note: If you do not set the session date.Setting the Effective Date of a Scheduled Enrollment in Self–Service Benefits Self–Service Benefits provides different ways of controlling the date on which the application records a participant election: • • • The Change Session Date web page (for testing environments in both Standard and Advanced Benefits) The Change Session Date menu parameter (Standard Benefits) Normal date processing based on the session date (Advanced Benefits) The Change Session Date web page lets you test future–dated elections. 2.

Note: You should remove this web page from your production environment by setting displayDate=N so that benefits participants cannot alter their enrollment date. so you should not include a year in the session date parameter. If you enter a session date that is later than the system day and month.2 Implementation Guide . Do not include the year. 18–26 Oracle SSHR 4. the application sets the session date to the current year.displayDate=Y&sessionDate=12/31&pFromPersonSearch=Y&pFor mFunction=BEN_SS_MGR_SRCH You enter the session date in mm/dd format. If you enter a session day and month that is prior to or equal to the system day and month. the application uses the following year. Deriving the Year of the Session Date The application derives the year to use for the session date.

Use the Submit Processes and Reports window.Running the Populate FEHB Program and Design Plan Process Before you can access the predefined programs and plans for Federal Employee Health Benefits. 4. 2. Choose the Submit button. Benefits . you must run a concurrent manager process that installs this data. 3. Choose the Business Group Name from the list of values. In the Name field. Click in the Parameters field to open the Parameters window. Repeat these steps for each business group that you have set up. choose Populate FEHB Program and Design Plan from the list of values. " To run the Populate FEHB Program and Design Plan Process: 1.US Federal 18–27 .

Setting up FEHB Before the employees or human resource personnel can access self–service benefits through the self–service user interface or the professional forms interface. Run the Populate FEHB Program and Plan Design concurrent manager program for each business group. See: Set Up User Access to Self–Service Benefits: page 18–21 When an employee has selected their benefits. If you do not want the POI groupbox to receive these notifications. you can deselect this option as explained in FYI Notifications for FEHB: page 18–33. Note: Do not add or update life events associated to the predefined FEHB program and plan enrollment requirements. See: Compiling FEHB Fast Formulas: page 18–31 3. Compile the FEHB fast formulas for each business group. the application notifies the Personnel Office groupbox. Set up user access. See: Running the Populate FEHB Program and Plan Design Process: page 18–27 2. " To set up US Federal Employee Health Benefits: 1. Benefits .US Federal 18–29 . you must set up FEHB.

In the Parameters window. choose Compile Formula. Choose the Submit button.FEHB_PLAN_ELIGIBILITY ity Benefits . substituting the following parameter information for the remaining fast formulas. Repeat these steps. Formula Name Formula Type Person Change Causes Life Event Person Change Causes Life Event Person Changes Causes Life Event GHR_CONT_LER_TRIGGER GHR_ADDRESS_LER_TRIGGER GHR_MARI_STATUS_LER_TRIGGER Participation and Rate Eligibil. " To compile individual formulas: 1. 4.US Federal 18–31 . you must compile the fast formulas for the same business groups. • • Formal Type: Extra Input Formula Names: FEHB_GET_PLAN_OPTION_SHORT_CODE 3. choose the formula type and formula name. See: Running the Populate FEHB Program and Design Plan Process: page 18–27 Use the Submit Requests and Processes window.Compiling FEHB Fast Formulas After you populate the Federal Employee Health Benefit plans and programs for each business group. 2. In the Name field.

the personnelist may then contact the participant to correct and resubmit the elections or manually override the changes in the professional user interface. 3.FYI Notifications for FEHB As a general practice. 2. If your agency’s policies do not include this review or approval process. Query the function GHR_SS_BNFT_ENRT Navigate to the Parameters field and change the send Notification parameter from Y to N. you can prevent the receipt of the FYI notification by changing the function parameters. most federal personnel offices approve a participant’s benefits elections. Click the Forms tab. Use the Function window and the System Administrator responsibility to change the FYI notification setting. " To not have the POI groupbox receive the FEHB fyi notification: 1. After reviewing the elections. Oracle workflow sends a notification to the POI groupbox. The entire parameter should read: displayDate=N&allowEnrt=Y&sessionDate=&sendFYINotification= N&wfProcessName=GHR_FYI_Notification_PRC 4. After an employee completes the enrollment or updates to their benefit elections. Benefits . The notification contains a link to the employee’s confirmation page.US Federal 18–33 . Save the form function.

Log in to Oracle HRMS using a System Administrator responsibility and open the Form Functions window. Query the Function Name for which you want to set the session date. Save your work. Update the seeded parameter to disallow enrollments by setting allowEnrt=N. current. Choose the Form tab. For example: • • BEN_SS_BNFT_ENRT (Self–Service Benefits Enrollment – Employee) BEN_SS_MGR_ENRT (Self–Service Benefits Enrollment – Internal Use) 4. When you remove the Benefits Enrollment Overview page.2 Implementation Guide . or if you use Advanced Benefits and process unrestricted program enrollments. participants can still view their past. 18–34 Oracle SSHR 4. it is recommended that you remove the Benefits Enrollment Overview web page from your Self–Service Benefits implementation during those periods when you do not want participants to enter or update benefits elections. and any future elections using the Current Benefits Overview web page.Removing the Benefits Enrollment Overview Web Page (Standard Benefits) If you use Standard Benefits. 2. 6. Choose the Description tab. " To remove user access to the Benefits Enrollment Overview page: 1. 5. 3.

Enter a Name for the communication type you are defining. Exclude the BEN prefix from the regionname portion of the short name. Save your work. Select a Usage Rule if your criteria for determining the conditions under which instruction text is generated cannot be fully accommodated by the usage criteria on this window. Enter a Short Name for this communication type. Note: Self–Service uses the short name to link the instruction text you write to a specific region in a Self–Service Benefits web page. Select a Usage type of Self Service Instruction Text to indicate you are configuring a self–service web page. " To define a communication type: 1. Select a value for one or more of the following parameters to limit the conditions under which instruction text is displayed. 5. You can vary the instruction text that displays in a region based on different criteria. 2. such as the presence of a life event or enrollment in a particular compensation object. Choose the Usages button. See: Benefits Enrollments: page 17–10 for a list of the required short names for each web page region. You must enter the short name in the following format: BEN. 3. 9. 4. Enter instruction text in the Self Service Instruction Text field that corresponds to the region of the self–service web page that you are configuring. • • • • • • Life Event Program Plan Plan Type Enrollment Period Action 8. Benefits . 7. 6. Select a To Be Sent code of Not Applicable.US Federal 18–35 .Defining Self–Service Instruction Text Use the Communication Types window in the Professional User Interface to define regional instruction text for Self–Service Benefits Enrollments and Individual Compensation Distributions.REGIONNAME.

18–36 Oracle SSHR 4.10.2 Implementation Guide . Save your work.

Enter a description of the enrollment action type in the Description field. Save your work.Defining Additional Enrollment Action Types (Advanced Benefits) You use the Enrollment Action Types window to rename an action type delivered with the system. 3. 4. Benefits . " To define additional enrollment action types: 1. Enter a name for the enrollment action type you are defining in the Name field. You then link the action type to a program or a plan as part of your enrollment requirements. Note: The description text appears as a message when a self–service user is required to complete an action item before an enrollment is valid. Select an enrollment action type in the Type field to specify a generic action a person must resolve in order to enroll in a compensation object.US Federal 18–37 . 2. You also use this window to edit messages for incomplete action items for Oracle Self–Service Human Resources benefits enrollments.

18–38 Oracle SSHR 4.2 Implementation Guide .

Select the Name of the plan for which you are maintaining primary care provider data. Note: As a prerequisite. Benefits . a participant cannot select a PCP from a list of valid PCPs.Maintaining Primary Care Providers for a Plan Based on your plan design. benefits participants may have the option. 9. 7. you must link an organization to this plan (using the Maintain Plan Related Details window) which has an Organization Role Type of Primary Care Provider Locator. Select a Dependent Designation Code to indicate if a participant who enrolls in this plan is required to select a PCP for each dependent covered by the plan. Note: If you do not check the From Repository field.US Federal 18–39 . to select a Primary Care Provider (PCP) when electing a benefit plan. or be required. 8. You use the Maintain Plan Primary Care Providers window to define restrictions for the selection of a primary care provider. or if PCP selection is optional. 3. or if PCP selection is optional. Note: The Can Keep Provider field is reserved for future use. Enter the number of times a participant is permitted to change primary care providers per month in the Number of Changes Allowed field. Select a Start Date Code that indicates when the selected provider becomes the participant’s primary care provider. select the maximum Radius in miles which the PCP database should consider when returning the results of a search query. Select a Designation Code to indicate if a participant who enrolls in this plan is required to select a PCP. For primary care provider searches. 5. 2. The participant must enter the PCP ID number or name in a free form text field. You also use this window to set high level configuration options for web–based PCP database searches that are performed through Oracle Self–Service Benefits. Check the From Repository field if you are using Oracle Self–Service Benefits and the benefits participant selects a primary care provider through a searchable database of providers. Check the Radius warning field to issue a warning message to the participant indicating that the selected PCP is outside the range 6. 4. " To maintain primary care providers for a plan: 1.

You maintain primary care provider types using the Lookup Type BEN_PCP_SPCLTY if your primary care providers are stored in an external repository. you would need to specify designation restrictions at the option level. 18–40 Oracle SSHR 4. Select a Designation Code to indicate if a participant who enrolls in this option is required to select a PCP. Note: For example.allowed by the plan. 10. not in Self–Service Benefits. Select a primary care provider type for which you are specifying PCP designation requirements based on the age or gender of the benefits participant.2 Implementation Guide . or if PCP selection is optional. Save your work. 17. Note: This warning only occurs in the professional forms user interface. Choose the Plan Restrictions button if the requirements for designating a primary care provider for this plan vary based on the primary care provider type (such as Gynecology or Pediatric Medicine) and the age or gender of the benefits participant. but a participant who elects employee plus spouse coverage is required to select a PCP for dependent coverage. Note: If you do not check this field. Note: The Plan Restrictions button is only activated if you check the From Repository field. Select the option for which you are specifying PCP designation requirements in the Options field. Save your work and close the Plan Primary Care Provider Restrictions window. Checking this field lets a participant override the warning and select a PCP outside the prescribed range. a participant cannot select a PCP outside the radius. 14. 13. 15. or if PCP selection is optional. 12. instead of the plan level. 11. Choose the Option Restrictions button to open the Plan Primary Care Provider Restrictions window if the requirements for designating a primary care provider differ between the options in the plan. Use the Lookup Type BEN_PRMRY_CARE_PRVDR_TYP if your PCPs are not stored in a repository. if a participant who elects participant only coverage is not required to select a PCP. 16. Select a Dependent Designation Code to indicate if a participant who enrolls in this option is required to select a PCP for each dependent covered by the plan.

20. Enter a Minimum Age if the participant must be of a minimum age or older to select this provider type. such as female for a gynecology provider. Select a Gender Allowed Code of Female or Male to restrict the selection of this provider type to one gender.US Federal 18–41 . such as a pediatric care provider. such as a geriatric care provider. Enter a Maximum Age if the participant must be of a maximum age or younger to select this provider type. Benefits .18. 19.

" To set up an XML–enabled primary care provider search: 1. Click the Region Items button. Self–Service Benefits also supports free form text entry of primary care providers without validation when a repository of PCP data is not used. Note: Currently.Configuring the Primary Care Provider Search Facility As part of a self–service enrollment. 3. enter false. • If you do not use a proxy server.2 Implementation Guide . If you use a proxy server to access an external web site. Do not enclose the URL in quotations.0 or 3. a benefits participant can select a primary care provider (PCP) for a benefit plan. 2. select the Ben PCP Server Proxy Set attribute and enter true in the Long Label field. Select the Ben PCP XML DTD attribute and enter the URL of the XML Document Type Definition in the Long Label field. Setting up an XML–Enabled Primary Care Provider Search If the search criteria entered by a benefits participant is formatted as an XML search request for use with a database of primary care providers (maintained by your enterprise or a third party). you can configure Self–Service Benefits so that a participant can select a primary care provider through a web–based search of a PCP database. The DTD version you use should correspond to your Client ID.0 of the GeoAccess DTD . Select the Ben PCP Provider Information attribute and enter the URL of the information provider in the Long Label field. 18–42 Oracle SSHR 4. the XML transaction must conform to version 2. Note: Enter the URL as you would in the Address or Location field of your web browser. Follow the instructions below based on the search type configured by your enterprise. 5. Select the Ben PCP Info Provider Client ID attribute and enter the Client ID given by the information provider in the Long Label field. you use the Regions window to configure information such as the URL of the information provider and the Document Type Definition (DTD) used by the search. As a system administrator. Query the Region ID BEN_PCP_XML_REQUEST_PARAMS. 6. 4.

0 8. PcpPersonId = (Person ID of the person for whom you are searching for a primary care provider ) PcpPlId = (Plan ID defined for the plan in the database) PcpPlTypId = (Plan Type ID defined in the database) Note: You do not need to use these variables if they are not required for your search or validations. Query the Region ID BEN_PCP_SELECT_SEARCH_TABLE. it is recommended that the maximum number of records be set to 100 or less. Select the Ben PCP XML Version attribute and enter the version of XML you are using in the Long Label field. 11. Select the Ben PCP Max Records attribute and enter the maximum number of records to be returned by the query in the Long Label field. Select the Ben PCP Request Method attribute and enter the HTTP request method expected by the information provider (such as GET or POST) in the Long Label field. Open the Regions window. A system administrator or application developer creates a search page that performs the query and accepts the following page–context variables: • • • 5.US Federal 18–43 . Select the ICX_IMAGE_FILE_1 attribute and enter the URL in the URL field that is accessed when a participant clicks the Search button on your custom Search web page. 4. 10. Note: For best performance. select the Ben PCP Server Proxy Port attribute and enter the port number (typically 80) in the Long Label field. 2. If you use a proxy server. 3. Benefits . 9. " To set up a primary care provider search without XML formatting: 1. Setting Up a Primary Care Provider Search without XML Formatting Customers who create a search page which does not format the PCP query in XML can follow these guidelines for a creating a PCP search that is compatible with Self–Service Benefits. Click the Region Items button. select the Ben PCP Proxy Host attribute and enter the URL of the proxy server in the Long Label field.7. If you use a proxy server. such as 1.

Pediatrics (specialty) 905 (planId) PcpPersonId Number 928374655 (personId) PcpTypCd Number 23 (pcpTypCd) The URL returned by the search should look like this: • /OA_HTML/OA. Note: Replace the directory OA_HTML with the base HTML directory of your installation.6.2 Implementation Guide . If the search is canceled without a selection of a PCP. Name of the primary care provider Specialties of the primary care provider The plan ID that corresponds to the plan name The person ID passed to the database as part of the query The code of the first primary care provider specialty that is returned by the query Value Number String String Number Example 10154244 (id) Sue Jones.jsp?akRegionCode=BEN_PCP_SELECT_PAGE &akRegionApplicationId=805&pcpSearchCancel=1. If the search is successful. 18–44 Oracle SSHR 4. MD (doctorsName) Internal Medicine. 7. the following URL must be used to return to the search page: • /OA_HTML/OA.jsp?akRegionCode=BEN_PCP_SELECT_PAGE &akRegionApplicationId=805&ExtIdent=id&PcpName=doctors Name&PcpSpecialty=specialty&PcpPlId=planId&PcpPersonId= personId&PcpTypCd=pcpTypCd Note: Replace the directory OA_HTML with the base HTML directory of your installation and replace the variables in the URL with the actual values. the URL accessed by the query must return the following information (properly formatted) with the following parameter names and data types as shown in the table below: PCP Parameters and Data Types Parameter Name ExtIdent PcpName PcpSpecialty PcpPlId Data ID of the primary care provider per the plan.

CHAPTER 19 Individual Compensation Distributions Individual Compensation Distributions 19–1 .

or. For example. Setting Up Individual Compensation Distribution Plans for Self–Service Human Resources Follow these process steps to set up a variety of individual compensation distribution plans. Using elements. You can also configure employee self–service ICD for use by non–manager employees. enforce the total maximum distribution you allow in a period. such as: • • • • • Periodic or spot bonuses Sponsored allowances Resettlement compensation Severance Payments Other periodic or recurring awards 19–2 Oracle SSHR 4. such as assignment data. you can process the distributions through Oracle Payroll. and allowances to qualified employees and other individuals using Oracle Self–Service Human Resources. Security features in Oracle HRMS ensure that managers can assign a distribution only to employees and contractors within their security group. you set up individual compensation distribution plans to define the components of an award or allowance. Participant eligibility profiles offer a further way to limit distributions to eligible employees based on a range of criteria. you can define the distribution end date.2 Implementation Guide . The manager’s supervisor can either approve or reject the distribution. if your enterprise offers a charitable contribution plan or a savings bond plan to which employees contribute at their own discretion. As a compensation manager. Oracle Self–Service HR seeds a workflow approval process that automatically sends a notification to the supervisor of the manager who distributes the award. using FastFormula. you can give managers throughout your enterprise the authority and ability to assign one–time or recurring awards. For recurring distributions. you can enable the contribution through the self–service interface. bonuses.Self–Service Individual Compensation Distributions (ICD) Using Oracle HRMS. The line manager uses the self–service interface to assign the award––setting the start and end date of the distribution––while the back–office maintains control of the plan’s administration.

" Setting up self–service individual compensation distribution plans 1. If you do not define a participant eligibility profile. the application finds all employees and contractors reporting to the manager eligible for the distribution. you define an individual compensation distribution plan using the features of Oracle Standard Benefits or Oracle Advanced Benefits. Define the Plan Year start and end dates for the compensation plan. See: Defining an Eligibility Profile. you can define participant eligibility profiles to limit the participants who are eligible for the plan or option. Set up several plan years to account for future plan years. If necessary. Note: Set the participant eligibility profile status to active if you define a profile. Set up one or more Plan Types to group the compensation plans you administer. Optional: define a participant eligibility profile to control eligibility for the compensation plan. See: Defining a Program or Plan Year Period. a line manager issues the compensation distribution to the employee through Oracle Self Service Human Resources. (Managing Total Compensation Using Oracle HRMS) 2. Individual Compensation Distributions 19–3 . (Managing Total Compensation Using Oracle HRMS) 3. • Required: select an Option Type of Individual Compensation Distribution to enable a manager to distribute the award through the self–service interface. Once you define the compensation plan. See the following topics for more information on setting up ICD: • • • • • • Define the Individual Distribution Compensation Plan: page 19–3 Define Enrollment Requirements for the Plan: page 19–5 Set Up Activity Rates and Coverages for the Plan: page 19–6 Configuring ICD Web pages: page 19–9 Entering People for Test Purposes: page 19–9 Setting Up Employee Self–Service Access to ICD: page 19–10 Define the Individual Distribution Compensation Plan You set up an individual compensation distribution plan by defining the characteristics of the plan and any electable options in the plan.As a compensation and benefits administrator.

For recurring awards. Set the plan status to active. you can select any activity reference period. or you can define multiple plan types for groupings of plans (Bonus. and allowances. Enter a sequence number that indicates the order in which the plan displays in the self service web page relative to other plans in the plan type. $100 per period. Optional: define the options in the compensation plan. You can update the status to inactive if you need to temporarily disable the plan. In the Not in Program tabbed region: • • • For non recurring awards. and Ford. • • • • Enter a user friendly plan name to display in the self service web page. such as a car allowance plan with options of BMW. • • Enter a user friendly option name to display in the self service web page. such as cars. Severance. 19–4 Oracle SSHR 4. and others). See: Defining Options. For bonus plans. You can choose to set up a single plan type for all your compensation plans. Allowance. Define the individual distribution compensation plan. (Managing Total Compensation Using Oracle HRMS) 4. the activity reference period is the period the manager sees when distributing the award. set up each compensation type as a separate plan.• Optional: select a Compensation Category of Compensation for reporting purposes or for system extracts. severances. Select the plan type of the plan. Note: Use options when there is a logical grouping of choices within a plan. for example. Select the corresponding plan type of each option.2 Implementation Guide . Select the Activity Reference Period of the plan. Select a Plan Usage code of May Not Be In a Program. See: Defining Plan Types. Select the currency of the plan for monetary distributions. You do not enter a currency for non monetary allowances. Honda. (Managing Total Compensation Using Oracle HRMS) 5. Note: You should base the number of plan types you define on your reporting requirements.

Select an enrollment method of Explicit. choose Event. for non–recurring allowances. select a Coverage Start Date code of Enterable if you want to let the manager enter the coverage start date. • Set the status for each option to active. (Managing Total Compensation Using Oracle HRMS) 7. Link the Plan Years to the plan that you defined in Step 1. (Managing Total Compensation Using Oracle HRMS) 8. Select a Coverage Start Date code of Event to set the start date to the system date when the manager enters the self service web page. " To define plan enrollment requirements: 1. • • • • Query the plan you defined in step 5 above. The application distributes the award to Payroll following the date. Use this code for non–recurring awards. Required: select a Coverage End Date code that corresponds to your Coverage Start Date code. If you define coverages. You can update the status to inactive if you need to temporarily disable an option.See: Defining a Benefits Plan. Define Enrollment Requirements for the Plan You use the Plan Enrollment Requirements window to control the enrollment method for an individual compensation distribution plan. If you defined options in Step 4. See: Associating Options with a Plan. See: Maintaining Plan Related Details. Activity Rate Start and End Date codes function similarly to coverage codes. Define enrollment requirements for the plan. The application distributes the award to Payroll in the following payroll period. You can also set up required certifications that the individual must provide before Oracle Payroll distributes the award. select any other coverage state date code. If you do not want the manager to enter the start date. Check the Allows Unrestricted Enrollment check box. link the options to the plan. • • • Individual Compensation Distributions 19–5 . Link a participant eligibility profile to the plan if you limit eligibility for the plan. Choose Enterable for recurring allowances. (Managing Total Compensation Using Oracle HRMS) 6.

You offer a monetary award and you want to distribute the amount of the award to payroll. You can then merge the data from the text file into the body of the participant communication. however. Optional: for Advanced Benefits. Optional: for Advanced Benefits users. (Managing Total Compensation Using Oracle HRMS) Set Up Activity Rates and Coverages for the Plan You set up activity rates to define the amount of a distribution (for fixed rate distributions) or to indicate that the manager enters the distribution amount when the award is assigned in the self–service web page. See: Defining Communication Types. (Managing Total Compensation Using Oracle HRMS) 3.2 Implementation Guide . You set up a system extract to write the applicable information from the communication type to a text file. Optional: set up an activity rate for an individual compensation distribution plan or option in the following cases: • • You do not use coverages. Note: You can set up multiple activity rates for an ICD plan. you can define communication types that the application generates to inform the participant of a suspended distribution. (Managing Total Compensation Using Oracle HRMS) See: Defining an Action Item Due Date (Advanced Benefits). Oracle HRMS seeds the certification types available with the application. (Managing Total Compensation Using Oracle HRMS) 2. See: Defining Certifications for Enrollment in a Plan. link one or more certifications to the plan if you request or require certification from the participant before you make the distribution. 19–6 Oracle SSHR 4. " To set up activity rates for a plan: 1. the application suspends the payroll distribution of the award until the participant returns the certification. you can choose only one rate to display on enrollment to the self–service user. A message displays to the issuing manager indicating that the distribution is suspended. Note: If you require a certification.See: Defining Enrollment Requirements for Not in Program Plans.

• See: Defining Activity Rates for a Standard Contribution/Distribution. Select a Usage code of Standard Contribution/Distribution. Select any Activity Type code. You can also use variable rate profiles to minimum and maximum distributions. For recurring awards. If the award is not a flat amount. Note: If the Unit of Measure is monetary. • • If the award is a flat amount. You award a non monetary gift (defined as a coverage) and you need to keep records of the taxable benefit. increments. check the Enter Value at Enrollment check box. (Managing Total Compensation Using Oracle HRMS) Individual Compensation Distributions 19–7 . Note: In order to control the maximum distribution amount. You want to control the maximum amount that can be distributed for a recurring element. Define the calculation method for the activity rate. Optional: define a variable rate profile if the activity rate varies according to one or more factors. the value the manager enters at enrollment is per the activity reference period defined for the plan. you must configure Oracle Payroll using FastFormula. See: Defining General Information for a Variable Rate Profile. • Select a rate certification type if you want to suspend the rate until the appropriate certification is received and approved. do not select any unit of measure. enter the value of the award. (Managing Total Compensation Using Oracle HRMS) 2. such as the assignment of the person to whom the manager distributes the award. Check the Assign on Enrollment and Display on Enrollment check boxes. Follow these guidelines when setting up the activity rate: • • • • • Set the activity rate status to active. and default rates.• • • You create element entries for the award. Select a Unit of Measure if the award is non monetary. Indicate if the activity rate applies to a plan or to an option in a plan.

Note: You may have to define your coverage first before saving this rate. Select a Rounding Code of Round to Nearest Hundredth. Select a Coverage Operator of Multiply by. with the following exceptions: • • • • • • • Leave the Unit of Measure field blank. Uncheck the Enter Value at Enrollment field. Optional: create a taxable benefit rate for use with non monetary coverages. with the following exceptions: • • • Select an Activity Type of Total Distribution Limit. On the Calculation Method Tab. Uncheck the Display on Enrollment check box.3. Leave the Recurring field blank. The award is a non monetary gift (which is defined as a coverage) and you need to keep records of the taxable benefit.2 Implementation Guide . Leave the Unit of Measure field blank. Select a coverage type. The award is non monetary and you do not want element entries created for the non monetary award. 4. 5. You do not define standard activity rates. Optional: define coverages for the plan if: • • • See: Defining a Coverage Calculation. Select a Unit of Measure if the Type is not Coverage. Select a Calculation Method of Multiple of Coverage. (Managing Total Compensation Using Oracle HRMS) Follow these guidelines when you set up a coverage definition: • • • • Enter a name for the coverage. Optional: create a Maximum Distribution Rate to accompany the standard rate. You set up a taxable benefit rate for non monetary coverages like you define a standard activity rate. select a Calculation Method of Flat Amount. Define a multiplier where the number represents the value of one non monetary award. You set up a Maximum Distribution Rate like you define a standard activity rate. 19–8 Oracle SSHR 4.

Select the manager’s GRE in the GRE tabbed region. Otherwise. See: Individual Compensation Distributions (ICD): page 12–28 Entering People for Test Purposes You can enter sample people into the Oracle HRMS database to test your Individual Compensation Distribution plan. and certain workflow attributes. Select the employee’s GRE in the GRE tabbed region. Using the People window. social security number. 4. and address. Select the test manager you created as the employee’s supervisor on the Supervisor tabbed region. Define a Manager: 1. 2. Note: You should set up no more than one coverage per compensation plan or option. Using the People window. • For recurring distributions. 4. define an employee with a date of birth. Check the Manager check box located in the Miscellaneous tabbed region. the coverage amount is per the activity reference period defined in the plan. and address. Note: If you use eligibility profiles. Enter an Assignment for the manager. social security number. open the User Types window to define a user name and password for the manager you created. 3.Note: If you want the user to enter the value during the enrollment check the Enter Value at Enrollment check box. tips. 3. and messages that display in an ICD web page. 1. function names. hints. enter the amount. You can also configure menu names. Configuring ICD Web pages You use the Application Dictionary to configure the field labels. 1. 2. As a system administrator. make sure the test employee meets your eligibility requirements. Define an Employee: Create a User Name and Password for the Test Manager: Individual Compensation Distributions 19–9 . define a manager with a date of birth. Enter an Assignment for the employee.

4. 7. Choose the Individual Compensation menu item. Choose the Web HTML tab. 2. Assign an Individual Compensation Distribution to the Employee: 1. 6. However. or service recognition plans where you allow the employee to select from one or more awards. Select SSWA JSP Function as the function Type.2. Optional: enter a Description of the function. 3. 5. 19–10 Oracle SSHR 4. 4. Enter the following parameter. substituting the function name you entered in Step 3 and your plan type IDs where indicated: • pProcessName=HR_INDIVIDUAL_COMP_PRC&pItemType=H RSSA&pCalledFrom=<your new function code>&OAFunc=<your new function code>&PLANTYPE=<your plan type IDs separated by commas> 9. log on to Oracle Self Service HR. 3. 2. Using the manager’s user name and password. Find the Employee you created. Save your work and close the window. Choose the Description tab. Choose the Form tab. " To set up employee self–service access to ICD: 1. Note: You set up employee self–service plans as you would other plans. 8. using the professional user interface. Enter a User Function Name for this function. Link the Manager Self Service responsibility to the user name. Log in to Oracle HRMS using a System Administrator responsibility and open the Form Functions window.2 Implementation Guide . Use this feature if your enterprise administers charitable contribution plans. Setting Up Employee Self–Service Access to ICD You can configure ICD for employee self–service access. savings bond plans. 3. Assign the individual an award. so that participants cannot view plans only available to managers. Enter a new function name––without spaces––in the Function field. you should include employee self–service plans in their own plan type.

10. Individual Compensation Distributions 19–11 . 14. Save your work. Close the Form Functions window and open the Menus window. 13. Add the function you just created to the Employee Self–Service Menu.jsp?akRegionCode=HR_CREATE_PROCESS_TOP_SS&akRe gionApplicationId=800 11. Enter the following string in the HTML Call field: • OA. 12. Save your work.

2 Implementation Guide .19–12 Oracle SSHR 4.

CHAPTER 20 Payroll Payroll 20–1 .

however. that these functions are generally localized and you should see the relevant documentation for your localization for additional implementation and configuration information.Overview of Payroll Functions SSHR currently includes the following payroll functions: • • • • Online Payslip Personal Payment Methods Online Tax Form Voluntary Deductions The following section gives technical information on configuring the generic versions of these functions. You should note.2 Implementation Guide . 20–2 Oracle SSHR 4.

0 See: Defining Menus for SSHR: page 5–12 Payroll 20–3 . Each payment is of a particular type (cash. or a combination) how the payment amounts are defined (percentage of net pay or a monetary amount) the maximum number of payments an employee can set up which organization payment methods are used If you configure Payment Methods so that employees can edit their payments. The employee can subsequently change the amount paid into the savings account if required.Payment Methods The Payroll Payments module enables employees to specify how they wish their salary to be paid by dividing an employee’s net pay into one or more payments. SSHR always uses the lowest priority payment to pay any net pay remaining after all the other payments have been made.0 Manage Payroll Payments V4. A typical use of this function occurs if an employee wants to split the net pay so that $100 is paid into a savings account and the rest is paid into a current account. deposit) and has an associated amount and a priority. deposit. You can apply configuration options to determine: • • • • • • whether employees can use the module for multiple payments whether payment information is for viewing only which types of payments the employee can select (cash. It is also possible that low priority payments may not receive all (or any) or their allotted funds because of the amounts used to process higher priority payments. The payments are made in order of priority. check. they can carry out the following steps: • • • • create new payments update existing payments delete payments change the priorities for payments Menu and Function Names This module can be accessed from the following menus and functions: User Menu Name Function Name Employee Self Service V4. check.

check. 20–4 Oracle SSHR 4.0 Process Payroll Payments V4.0 Process Payroll Payments V4.0 Manage Payroll Payments V4.0 Manage Payroll Payments V4.0 Note: The Process Payroll Payments module does not support approvals.0 Manage Payroll Payments V4.0 View Only Permitted Payment Types Maximum Payment Methods Permitted Amount Types Deposit Payments List Cash Payments List Cash Payments List View Only Specifies whether the employee can edit the payments information.0 Process Payroll Payments V4. The default value is 5. Maximum Payment Methods Specifies the maximum number of payments that an employee can create (up to 10).0 Manage Payroll Payments V4. Configurable Workflow Attributes: Process Display Name Function Activity Display Name Function Activity Attribute Display Name Process Payroll Payments V4. The default value allows the employee to create any of the three payment types.0 Process Payroll Payments V4. Permitted Payment Types Specifies which types of payment methods an employee can create.0 Manage Payroll Payments V4.0 Manage Payroll Payments V4.Workflow The workflow details for this module are listed below: Workflow Process Display Name: Process Payroll Payments V4.0 Process Payroll Payments V4.0 Manage Payroll Payments V4.2 Implementation Guide .0 Process Payroll Payments V4. The available payment types are cash. The default value enables editing. and deposit.

Deposit Payments List This attribute is only used if you have enabled deposit payments. The payment amount can be a monetary amount or a percentage of net pay. Cash Payments List This is used in the same way as the Deposit Payments Checklist but for cash payments. See: Configuring Workflow Attribute Values: page 6–7 Configurable Definitions for Web Applications Dictionary: The following definitions can be configured in the Web Applications Dictionary: Regions Summary and Edit Pages Region Code Region Name PAY_PAYMENTS_TOP_SS PAY_PAYMENTS_EDIT_SS PAY_PAYMENTS_SUMMARY_SS PAY_PAYMENTS_LABELS_SS Payroll Payments Top Payroll Payments Edit Payroll Payments Summary Payroll Payments Labels Payroll 20–5 . The module uses the first match to a deposit OPM name (for the employee’s payroll) when new deposit payments are created. Note: The administrator must set at least one of Deposit Payments List. Check Payments List This is used in the same way as the Deposit Payments Checklist but for check payments. The OPM names are separated by a vertical bar (|). Cash Payments List. For example. East_Coast_NACHA|West_Coast_NACHA.Permitted Amount Types Specifies the amount types for payments. or Check Payments List. This attribute stores a list of Organizational Payment Method (OPM) names that can be used to create a deposit payment. The default value enables both amount types.

2 Implementation Guide .Review Page Region Code Region Name PAY_PAYMENTS_REVIEW_SS Payroll Payments Review Tips and Instructions Region ID Region Name Attribute Name Tip Type Message Name PAY_PAYMENTS _EDIT_INS1_SS PAY_PAYMENTS _EDIT_INS1_SS PAY_PAYMENTS _EDIT_INS1_SS PAY_PAYMENTS _EDIT_INS1_SS Payroll Payments Edit Create Mode Instructions Payroll Payments Edit Create Mode Instructions Payroll Payments Edit Create Mode Instructions Payroll Payments Edit Create Mode Instructions Payroll Payments Edit Create Mode Instructions Pay Instruction 1 Pay Instruction 2 Pay Instruction 3 Pay Instruction 4 PAY_PSSV4_ADD _CASH_OVERVIEW PAY_PSSV4_ADD _CHECK_OVERVIEW PAY_PSSV4_ADD _CHEQUE_OVERVIEW PAY_PSSV4_ADD _DEPOSIT_OVERVIEW PAY_PSSV4_ADD _REMAINING_PAY PAY_PSSV4_UPDATE_CASH_OV ERVIEW PAY_PSSV4_UPDATE_CHECK_O VERVIEW PAY_PSSV4_UPDATE_CHEQUE_ OVERVIEW PAY_PSSV4_UPDATE_DEPOSIT_OVERVIEW PAY_PSS_REMAINING_PAY PAY_PAYMENTS _EDIT_INS1_SS PAY_PAYMENTS _EDIT_INS2_SS PAY_PAYMENTS _EDIT_INS2_SS PAY_PAYMENTS _EDIT_INS2_SS PAY_PAYMENTS _EDIT_INS2_SS Pay Instruction 5 Payroll Payments Pay Instruction Edit Update 1 Mode Instructions Payroll Payments Pay Instruction Edit Update 2 Mode Instructions Payroll Payments Pay Instruction Edit Update 3 Mode Instructions Payroll Payments Pay Instruction Edit Update 4 Mode Instructions Payroll Payments Pay Instruction Edit Update 5 Mode Instructions PAY_PAYMENTS _EDIT_INS2_SS 20–6 Oracle SSHR 4.

Region ID Region Name Attribute Name Tip Type Message Name PAY_PAYMENTS _EDIT_INS3_SS PAY_PAYMENTS _EDIT_INS3_SS PAY_PAYMENTS _EDIT_INS3_SS PAY_PAYMENTS _EDIT_INS3_SS PAY_PAYMENTS _EDIT_INS3_SS PAY_PAYMENTS _SUMMARY_INS 1_SS PAY_PAYMENTS _SUMMARY_INS 1_SS PAY_PAYMENTS _SUMMARY_INS 1_SS PAY_PAYMENTS _SUMMARY_INS 1_SS PAY_PAYMENTS _SUMMARY_INS 1_SS PAY_PAYMENTS _SUMMARY_INS 2_SS PAY_PAYMENTS _SUMMARY_INS 2_SS Payroll Payments Pay Instruction Edit View–only 1 Mode Instructions Payroll Payments Pay Instruction Edit View–only 2 Mode Instructions Payroll Payments Pay Instruction Edit View–only 3 Mode Instructions Payroll Payments Pay Instruction Edit View–only 4 Mode Instructions Payroll Payments Pay Instruction Edit View–only 5 Mode Instructions Payroll Payments Pay Instruction Summary Edit 1 Mode Instructions Payroll Payments Pay Instruction Summary Edit 2 Mode Instructions Payroll Payments Pay Instruction Summary Edit 3 Mode Instructions Payroll Payments Pay Instruction Summary Edit 4 Mode Instructions Payroll Payments Pay Instruction Summary Edit 5 Mode Instructions Payroll Payments Summary View– only Mode Instructions Payroll Payments Summary View– only Mode Instructions Pay Instruction 1 PAY_PSSV4_DETAILS_OVERVIEW PAY_PSSV4_DETAILS_OVERVIEW PAY_PSSV4_DETAILS_OVERVIEW PAY_PSSV4_DETAILS_OVERVIEW PAY_PSS_REMAINING_PAY PAY_PSSV4_SUMMARY_EDIT_OVERVIEW PAY_PSS_EDIT_D FLT_MANDATORY_ PAY PAY_PSS_EDIT_D FLT_CASH PAY_PSS_EDIT_D FLT_CHECK PAY_PSS_EDIT_D FLT_CHEQUE PAY_PSSV4_SUMMARY_VIEW_OVERVIEW PAY_PSS_MANDATORY_PAY Pay Instruction 2 Payroll 20–7 .

Region ID Region Name Attribute Name Tip Type Message Name PAY_PAYMENTS _SUMMARY_INS 2_SS PAY_PAYMENTS _SUMMARY_INS 2_SS PAY_PAYMENTS _SUMMARY_INS 2_SS Payroll Payments Summary View– only Mode Instructions Payroll Payments Summary View– only Mode Instructions Payroll Payments Summary View– only Mode Instructions Pay Instruction 3 PAY_PSS_CASH_S ALARY Pay Instruction 4 PAY_PSS_CHECK _SALARY Pay Instruction 5 PAY_PSS_CHEQU E_SALARY See: Adding Instructions to Web Pages: page 7–9 FlexFields: Region ID Region Name Attribute Name FlexField Name PAY_PAYMENTS_E MPLOYEE_TABLE_ SS PAY_PAYMENTS_E DIT_DETAILS_SS PAY_PAYMENTS_R EVIEW_SS Payroll Payments Employee Table Payroll Payments Edit Details Payroll Payments Review PAY_BANK_KEY _FLEX PAY_BANK_KEY _FLEX PAY_BANK_KEY _FLEX BANK Bank Details Key Flexfield BANK Bank Details Key Flexfield BANK Bank Details Key Flexfield See: Configuring Flexfields: page 7–6 Configurable Profile Options Profile Configurable Levels Values Default HR:Payroll Payments Self–Service Enable Multiple Assignments Site Yes/No No 20–8 Oracle SSHR 4.2 Implementation Guide .

HR:Payroll Payments Self–Service Enable Multiple Assignments Specifies whether the employee can use the function to define payments for multiple assignments. The default value only permits payments for the primary assignment. See: User Profiles (Oracle HRMS Applications User Guide) Payroll 20–9 .

0 See: Defining Menus for SSHR: page 5–12 Viewing Online Payslips in Oracle HRMS Using the HR Professional V4. or by clicking on the Next or Back button. Note: All columns and fields in the Online Payslip function are display only.0 responsibility you can select the Payslip Details link and search for a person. The Payslip is generated from the employee’s assignments. the online payslip will show the combined totals for all assignments. their payslip will be displayed. You can also save a person in My List for future access. Employees can select what pay period to view from a list of values showing the Pay Dates. When you select a person from the list.2 Implementation Guide . the employee will see an electronic version of their payslip based on their selected assignment and the last pay period that has been processed. you have the option of combining the checks for multiple assignments into one pay check.0 Payslip V4. the employee can select the required assignment. In this case.Online Payslip (Generic) The Payslip module enables employees to view an electronic payslip for a pay period. Workflow The workflow details for this module are listed below: Workflow Process Display Name: Not applicable 20–10 Oracle SSHR 4. See: Creating a Payroll (Using Oracle HRMS – The Fundamentals) Menu and Function Names This module can be accessed from the following menus and functions: User Menu Name Function Name Employee Self Service V4. If there are multiple paid assignments for an employee. Once the employee has logged into the application and clicks on the View Payslip option. If Multiple Assignment Payments functionality has been enabled for your localization. so you don’t have to search for that person again.

see: • • • • • Online Payslip (Canada): page 20–16 Online Payslip (ZA): page 20–21 Online Payslip (UK): page 20–14 Online Payslip (US): page 20–12 Online Payslip (Australia. New Zealand): page 20–19 Payroll 20–11 . an error message is displayed when the employee attempts to view the online payslip.Configurable Workflow Attributes: Not applicable Configurable Tips and Instructions Not applicable Configurable FlexFields Not applicable Configurable Profile Options Profile Configurable Level Values Default HR:View Payslip From Date for WEB (MM/DD/YYYY) User specification Date 01/01/1997 HR:View Payslip From Date for WEB This profile option determines how many payroll periods an employee can view in the online payslip. Singapore. and System Administration in Oracle HRMS) Additional Configuration Steps: For legislation–specific configuration steps. If the profile option is not set. Korea. Reporting. See: User Profiles (Configuring. Hong Kong.

Menu and Function Names This module can be accessed from the following menus and functions: User Menu Name Function Name Employee Self–Service Payslip V4.0 See: Defining Menus for SSHR: page 5–12 Workflow The workflow details for this module are listed below: Workflow Process Display Name: Not applicable Configurable Workflow Attributes: Not applicable Configurable Tips and Instructions Not applicable Configurable FlexFields Not applicable Configurable Profile Options Profile Configurable Level Values Default HR:View Payslip From Date for WEB (MM/DD/YYYY) User specification Date 01/01/1997 20–12 Oracle SSHR 4.Online Payslip (US) The Online Payslip for the US is a localized version of the generic payslip and has been designed to meet local requirements. For information on the generic payslip functionality. see Online Payslip: page 20–10.2 Implementation Guide .

5. messages. See: Running the Prepayments Process. Oracle HRMS – The Fundamentals 3. Run the payment processes (for example. See: User Profiles (Configuring. and System Administration in Oracle HRMS) Additional Configuration Options 1. Reporting. See: Entering Self–Service Preference Information Oracle HRMS – The Fundamentals See: Person Extra Information Types. Run the External Process Archive process to enable SSHR users to view their payslip. If the profile option is not set. an error message is displayed when the employee attempts to view the online payslip. the Check Writer process). See: Entering Payslip Information Running Your Payroll Using Oracle HRMS 2. Managing Your Workforce Using Oracle HRMS See: Location Extra Information Types. Run the Prepayments process. You can set this information at the HR organization or business group level using the Self–Service Preferences additional organization information. You can display elements. and balances. Optionally define additional information to be displayed in the Other Information section of the payslip using the Payslip Information additional organization information. or alternatively at the person or location level using an extra information type. Running Your Payroll Using Oracle HRMS 4. Running Your Payroll Using Oracle HRMS Payroll 20–13 . See: Running the External Process Archive Process.HR:View Payslip From Date for WEB This profile option determines how many payroll periods an employee can view in the online payslip. Set the document viewing and printing preferences.

2 Implementation Guide . Menu and Function Names This module can be accessed from the following menus and functions: User Menu Name Function Name Employee Self–Service Payslip V4. For information on the generic payslip functionality.Online Payslip (UK) The Online Payslip for the UK is a localized version of the generic payslip and has been designed to meet local requirements. see Online Payslip: page 20–10.0 See: Defining Menus for SSHR: page 5–12 Workflow The workflow details for this module are listed below: Workflow Process Display Name: Not applicable Configurable Workflow Attributes: Not applicable Configurable Tips and Instructions Not applicable Configurable FlexFields Not applicable Configurable Profile Options Profile Configurable Level Values Default HR:View Payslip From Date for WEB (MM/DD/YYYY) User specification Date 01/01/1997 20–14 Oracle SSHR 4.

Running Your Payroll Using Oracle HRMS 4. Run the payment processes (for example. See: User Profiles (Configuring. Running Your Payroll Using Oracle HRMS – Payslip Elements See: Entering Payroll Elements. See: Generating the Payslip. – Payslip Balances See: Entering Payroll Balances. Run the Payslip Generation Self–Service process to enable SSHR users to view their payslip. Set the document viewing and printing preferences using the Self Service Preferences additional organization information. See: Running the Prepayments Process. Reporting. See: Entering Self–Service Preference Information Oracle HRMS – The Fundamentals 3. If the profile option is not set. Run the Prepayments process. Running Your Payroll Using Oracle HRMS Payroll 20–15 . the Chequewriter process).HR:View Payslip From Date for WEB This profile option determines how many payroll periods an employee can view in the online payslip. and System Administration in Oracle HRMS) Additional Configuration Options 1. an error message is displayed when the employee attempts to view the online payslip. 5. Optionally define additional information to be displayed in the Other Information section of the payslip using the Payslip Balances and Payslip Elements additional organization information. Running Your Payroll Using Oracle HRMS 2.

see Online Payslip: page 20–10.2 Implementation Guide .Online Payslip (Canada) The Online Payslip for Canada is a localized version of the generic payslip and has been designed to meet local requirements. For information on the generic payslip functionality. Menu and Function Names This module can be accessed from the following menus and functions: User Menu Name Function Name Employee Self–Service Payslip V4.0 See: Defining Menus for SSHR: page 5–12 Workflow The workflow details for this module are listed below: Workflow Process Display Name: Not applicable Configurable Workflow Attributes: Not applicable Configurable Tips and Instructions Not applicable Configurable FlexFields Not applicable Configurable Profile Options Profile Configurable Level Values Default HR:View Payslip From Date for WEB (MM/DD/YYYY) User specification Date 01/01/1997 20–16 Oracle SSHR 4.

Elements. Running Your Payroll Using Oracle HRMS 4. 5. you can either specify the message text or the message name. If you enter the message text.HR:View Payslip From Date for WEB This profile option determines how many payroll periods an employee can view in the online payslip. Reporting. You can set this information at the HR organization or business group level using the Self–Service Preferences additional organization information. See: Entering Payslip Information Running Your Payroll Using Oracle HRMS 2. See: Person Extra Information Types. the Chequewriter process). If you are entering a message. Run the Canadian Payroll Archiver process to enable SSHR users to view their payslip. Oracle HRMS – The Fundamentals See: Entering Self–Service Preference Information Oracle HRMS – The Fundamentals 3. and System Administration in Oracle HRMS) Additional Configuration Options 1. Payroll 20–17 . the Canadian Payroll Archiver subsequently retrieves the message from fnd_new_messages and archives it. See: User Profiles (Configuring. Run the Prepayments process. and Message types in the Payslip Information additional organization information. Optionally define additional information to be displayed in the Other Information section of the payslip using the Balances. Set the document viewing and printing preferences. Managing Your Workforce Using Oracle HRMS See: Location Extra Information Types. If the profile option is not set. If you specify the message name. See: Running the Prepayments Process. Run the payment processes (for example. the Canadian Payroll Archiver archives the message text entered at the organization or business group level. an error message is displayed when the employee attempts to view the online payslip. or alternatively at the person or location level using an extra information type.

See: Running the Canadian Payroll Archiver available in the online help for Canada. 20–18 Oracle SSHR 4.2 Implementation Guide .

New Zealand) The Online Payslips for the above localizations are localized versions of the generic payslip and have been designed to meet local requirements.0 See: Defining Menus for SSHR: page 5–12 Workflow The workflow details for this module are listed below: Workflow Process Display Name: Not applicable Configurable Workflow Attributes: Not applicable Configurable Tips and Instructions Not applicable Configurable FlexFields Not applicable Configurable Profile Options Profile Configurable Level Values Default HR:View Payslip From Date for WEB (MM/DD/YYYY) User specification Date 01/01/1997 Payroll 20–19 . Hong Kong. For information on the generic payslip functionality. see Online Payslip: page 20–10.Online Payslip (Australia. Menu and Function Names This module can be accessed from the following menus and functions: User Menu Name Function Name Employee Self–Service Payslip V4. Singapore. Korea.

Run the payment processes (for example. an error message is displayed when the employee attempts to view the online payslip. Reporting. Running Your Payroll Using Oracle HRMS – Payslip Elements See: Entering Payroll Elements. Running Your Payroll Using Oracle HRMS 4. Run the Prepayments process. Optionally define additional information to be displayed in the Other Information section of the payslip using the Payslip Balances and Payslip Elements additional organization information.HR:View Payslip From Date for WEB This profile option determines how many payroll periods an employee can view in the online payslip. and System Administration in Oracle HRMS) Additional Configuration Options 1. – Payslip Balances See: Entering Payroll Balances. If the profile option is not set. the Chequewriter process). See: Entering Self–Service Preference Information Oracle HRMS – The Fundamentals 3. See: User Profiles (Configuring. Run the Payslip Archive process for the appropriate legislation to enable SSHR users to view their payslip.2 Implementation Guide . See: Running the Prepayments Process. 20–20 Oracle SSHR 4. Running Your Payroll Using Oracle HRMS 2. 5. Set the document viewing and printing preferences using the Self Service Preferences additional organization information.

If there are multiple paid assignments for an employee. or by clicking on the Next or Back button. The Payslip is generated from the employee’s assignments. you have the option of combining the checks for multiple assignments into one pay check. the employee can select the required assignment.0 See: Defining Menus for SSHR: page 5–12 Workflow The workflow details for this module are listed below: Workflow Process Display Name: Not applicable Configurable Workflow Attributes: Not applicable Configurable Tips and Instructions Not applicable Payroll 20–21 . In this case. Note: All columns and fields in the Online Payslip function are display only. See: Creating a Payroll (Using Oracle HRMS – The Fundamentals) Menu and Function Names This module can be accessed from the following menus and functions: User Menu Name Function Name Employee Self–Service Payslip V4. If Multiple Assignment Payments functionality has been enabled for your localization.Online Payslip (South Africa) The Payslip module enables employees to view an electronic payslip for a pay period. Once the employee has logged into the application and clicks on the View Payslip option. Employees can select what pay period to view from a list of values showing the Pay Dates. the online payslip will show the combined totals for all assignments. the employee will see an electronic version of their payslip based on their selected assignment and the last pay period that has been processed.

If the profile option is not set. See: Entering Self–Service Preference Information Oracle HRMS – The Fundamentals 20–22 Oracle SSHR 4. See: User Profiles (Configuring. Running Your Payroll Using Oracle HRMS – ZA Payslip Elements See: Entering ZA Payslip Elements.2 Implementation Guide . and System Administration in Oracle HRMS) HR:Mask Characters You can use this profile option to set the number of characters or digits to display in numbers such as bank account or credit card numbers. Optionally define additional information to be displayed in the Other Information section of the payslip using the ZA Payslip Balances and ZA Payslip Elements additional organization information types. and System Administration in Oracle HRMS) Additional Configuration Options 1. Reporting. Reporting.Configurable FlexFields Not applicable Configurable Profile Options Profile Configurable Level Values Default HR:View Payslip From Date for WEB (MM/DD/YYYY) User specification Date 01/01/1997 HR:View Payslip From Date for WEB This profile option determines how many payroll periods an employee can view in the online payslip. See: User Profiles (Configuring. Running Your Payroll Using Oracle HRMS 2. Set the document viewing and printing preferences using the Self Service Preferences additional organization information. an error message is displayed when the employee attempts to view the online payslip. – ZA Payslip Balances See: Entering ZA Payslip Balances.

Run the Prepayments process. the Chequewriter process). 5. Running Your Payroll Using Oracle HRMS Payroll 20–23 . See: Running the Pay Advice Generation – Self Service (South Africa). Run the payment processes (for example. Run the Pay Advice Generation – Self Service (South Africa) process to enable SSHR users to view their payslip.3. See: Running the Prepayments Process. Running Your Payroll Using Oracle HRMS 4.

all the states that follow the Federal information are also updated. number of allowances. unless the filing status.0 See: Defining Menus for SSHR: page 5–12 Workflow The workflow details for this module are listed below: Workflow Process Display Name: Change W4 Information JSP PRC Configurable Workflow Attributes: Not applicable Configurable Tips and Instructions Region Tip Type Message Name W4 Overview Header W4 Update Filing Detail W4 Update Exempt Instruction Instruction Instruction PAY_W4_OVERVIEW_MSG PAYSSW4_UPDATE_HEADER_INFO PAY_US_OTF_W4_EXEMPTSTAT_TXT 20–24 Oracle SSHR 4. When an employee makes changes to the Federal information.Tax Withholdings Form (W–4) (US) The Tax Withholdings Form module enables employees to make changes to their tax information. Menu and Function Names This module can be accessed from the following menus and functions: User Menu Name Function Name Employee Self Service Online Tax Forms V4.2 Implementation Guide . or exempt status are different. the HR/Payroll representative receives a notification and can review the data. If an employee claims tax exemption or has allowances that exceed the state limit.

if the profile value is Primary. Further Payroll Information Further Payroll Information See: User Profiles (Configuring. only the tax information for the primary assignment is updated when a user changes tax information using the Online Tax Form. Reporting. This profile option defines how the contact person is determined. GRE Contact Information. Primary Primary Site Custom PL/SQL. For example. Payroll 20–25 . The possible values are as follows: • Further Payroll Information: You must enter a payroll representative in the Further Payroll Information flexfield of the Payroll window.Region Tip Type Message Name W4 Update Agreement W4 Update Filing Detail W4 Update Filing Detail Instruction Long Message Long Message PAYSSW4_UPDATE_AGREEMENT_INFO PAY_US_OTF_W4_ALLOWANCES_TXT PAY_US_OTF_W4_ADDLAMOUNT_TXT See: Adding Instructions to a Web Page: page 7–9 Configurable FlexFields Not applicable Configurable Profile Options Profile Configurable Level Values Default HR: Online Tax Forms Update Method HR: HR/Payroll Representative Source Site All. a notification is sent to a designated contact person informing them of the change. None. and System Administration in Oracle HRMS) HR: Online Tax Forms Update Method This profile option determines which assignments can be updated. HR: HR/Payroll Representative Source If a user makes a change to their tax information using the online tax form.

• 20–26 Oracle SSHR 4.• GRE Contact Information: You must enter a payroll representative in the Contact Information additional organization information window.2 Implementation Guide . Custom PL/SQL: You need to modify the Get_Next_Payroll_Notifier function in the PL/SQL package hr_approval_custom.

the employee can request a reprint of the W–2 information on paper.irs. If required. the payroll contact receives a notification of the reprint request. It should not be printed and attached to tax returns. a message is displayed. no online W–2 information is available for any assignments in the GRE. only the assignments that have been archived successfully will be available for online viewing.gov). If there is no W–2 information or if the self–service preferences have not been configured to enable online access. A message giving this information is also displayed at the bottom of the online form. If the Year End Pre–Process has ended with an error status. If the Year End Pre–Process has finished successfully but some assignments are in error. The online W–2 information will not be available for assignments with errors until the errors have been resolved and the assignments have been successfully archived.0 function. The payroll contact is defined using the HR:HR/Payroll Representative Source profile option. Menu and Function Names This module can be accessed from the following menus and functions: User Menu Name Function Name Employee Self Service Employee W–2 V4. W–2 information for the year 2001 and onward will be available for viewing online.0 Workflow The workflow details for this module are listed below: Workflow Process Display Name: Pay Employee W2 Process Payroll 20–27 . In this case. When an employee selects the Employee W–2 V4. The W–2 form can only be viewed after the Year End Pre–Process has been run. the most recent W–2 information is displayed.Tax Information Form (W–2) (US) The Tax Information Form enables employees to view their W–2 Tax Statement information on the web. A consent form from the employee is not required to place this W–2 information online because the employer must still issue a paper copy of Form W–2 (see publication 15–A for further details – available at www. Note: Currently the online Employee W–2 form is for informational purposes only.

Payroll Further Payroll Information. GRE Contact Information: You must enter a payroll representative in the Contact Information additional organization information window. Custom PL/ SQL Further Payroll Information See: User Profiles (Oracle HRMS Applications User Guide) HR: HR/Payroll Representative Source If a user requests a reprint of the paper Form W–2. • 20–28 Oracle SSHR 4. The possible values are as follows: • Further Payroll Information: You must enter a payroll representative in the Further Payroll Information flexfield of the Payroll window. This profile option defines how the contact person is determined.0) Configurable FlexFields Not applicable Configurable Profile Options Profile Configurable Level Values Default HR: HR/Payroll Representative Source Site. a notification is sent to a designated contact person informing them of the request.Configurable Workflow Attributes: Not applicable Configurable Tips and Instructions Region Name Tip Type Message Name Pay W2 Details Instruction Instruction Instruction PAY_W2_PRINT_WARNING_MESG PAY_NO_W2_TO_VIEW_WEB PAY_NO_SS_PREF_W2_WEB See: Adding Instructions to Web Pages (Implementing Oracle Human Resources 4.2 Implementation Guide . GRE Contact Information.

at the person or location level using an extra information type. You can define this information at the HR organization or business group level using additional organization information. or alternatively.• Custom PL/SQL: You need to modify the Get_Next_Payroll_Notifier function in the PL/SQL package hr_approval_custom. See: Entering Self–Service Preference Information (for HR organization or business group level) (Using Oracle HRMS – The Fundamentals) See: Person Extra Information Types (Managing Your Workforce Using Oracle HRMS) (for person level) See: Location Extra Information Types (Using Oracle HRMS – The Fundamentals) (for location level) Payroll 20–29 . Additional Configuration Steps: Set the document viewing and printing preferences using Self Service Preferences.

such as charitable contributions or savings bond plans. such as a charitable contribution or savings bond plan. and allowances to qualified employees and individuals. ICD enables managers to assign one–time or recurring awards. You can also set up ICD for non–manager employees if your enterprise offers discretionary contribution plans.Voluntary Deductions Using the Total Compensation data model. a compensation or benefits administrator can enable voluntary deductions for employees by setting up Individual Compensation Distribution plans. See: Individual Compensation Distributions (ICD): page 12–28 20–30 Oracle SSHR 4. bonuses.2 Implementation Guide .

CHAPTER 21 Training Training 21–1 .

In other words.0 Training V4. enable approvals by configuring the Approval Required attribute for the Review Page and Additional Enrollment Details activities within the Enroll in Training workflow process. See: Overview of Approvals: page 8–2 See: Overview of Approvals. Implementing Oracle Self–Service Human Resources To integrate self–service training with a full installation of Oracle Training Administration. No unique workflow attributes are used.0 function uses self–approval. Menu and Function Names You can access this module from the following menus and functions: User Menu Name Function Name Employee Self–Service V4. Note: To obtain the self–service External Training module.4.0 module replaces the Enroll in a Class and Cancel Enrollment functions available in SSHR 3. You can now enroll in a training class and cancel enrollment using the same self–service interface. you may have already set some of the configurable profile options listed below.Training (Self–Service) The Training V4.2 Implementation Guide . The default Training V4. however. 21–2 Oracle SSHR 4. you must apply OTA Minipack G or later. You can. employees can enroll themselves in classes without requiring approval from their manager or supervisor.0 Manager Self–Service V4. You do not need to reset them for SSHR. see Implementing Oracle Training Administration Note: If you have already implemented OTA.0 Workflow The Training module uses a Workflow Process Display Name of Enroll in Training.0 Training V4.

Configurable Tips and Instructions
Region Tip Type Message Name

Training Top Training Top OTA Advanced Search Top OTA Advanced Search Top OTA Advanced Search Top OTA Training Center Search Top OTA Training Center Search Top OTA Competence Search Top OTA Competence Search Top

Instruction Instruction Instruction Instruction Instruction Instruction Instruction Instruction Instruction

OTA_SS_INST_SELECT_VIEW_TIP OTA_SS_INST_ENR_DETAILS_TIP OTA_SS_SIMPLE_SEARCH_TIP OTA_SS_ADVANCED_SEARCH_TIP OTA_SS_SEARCH_RESULT_TIP OTA_SS_TRN_CENTER_SEARCH_TIP OTA_SS_SIMPLE_SEARCH_TIP OTA_SS_COMP_SEARCH_TIP OTA_SS_SIMPLE_SEARCH_TIP

See: Adding Instructions to Web Pages: page 7–9

Configurable Flexfields
Region Flexfield Code Flexfield Name

OTA Additional Enrollment Details Top Top Course Details Page Top Course Details Page Top Course Details Page

OTA_DELEGATE_BOOKINGS OTA_ACTIVITY_VERSIONS OTA_EVENTS Address Location

Additional Delegate Booking Information Additional Activity Version Information Additional Event Information Location Address Additional Non OTA Training History Information

Other Non OTA Train- OTA_NOTRNG_HISing Details TORIES

See: Configuring Flexfields: page 7–6

Training

21–3

Configurable Profile Options
If you have previously implemented Oracle Training Administration, you may have already set some of the profiles below. You do not need to reset them for Self–Service Training.
Profile Configurable Level Values (default value in boldface) Yes, No Value Required?

OTA: Activate Automatic Waitlist Enrollments OTA: Automatic Finance Header Approval OTA: Automatic Waitlist Enrollment Default Booking Status OTA: Automatic Waitlist Enrollments: Hours Prior To Event OTA: Waitlist Sorting Criteria OTA: SS Automatic Creation of Finance Headers and Lines OTA: SS Default Training Administrator OTA: SS Automatic Transfer to GL OTA: SS Minimum Hours to Cancel for Free OTA: SS Read–only Enrollment Message

All

Yes, at Site level

Responsibility, Site

Yes, No

Yes

All

Placed, <value based on Placed>, <null> <numeric> (0)

Yes

All

Yes, at Site level

All Site

Booking Priority, Date Placed Yes, No

Yes, at Site level Yes

Responsibility

<Person name>, <null> Yes, No <numeric value>, 0

Yes

Responsibility, Site Site

Yes Yes

User

<Message text>, <null>

No

For further definitions of the OTA profile options, see Profile Options, Using Oracle Training Administration For general information about profile options, see: User Profiles, Configuring, Reporting, and System Administration in Oracle HRMS.

21–4

Oracle SSHR 4.2 Implementation Guide

External Training (Self–Service)
The External Training V4.0 module replaces the Training History functions available in SSHR 3.4. You can now enter and update external training (courses not originating as events within OTA) using the self–service interface. Note: To obtain the self–service External Training module, you must apply OTA Minipack G or later. The default External Training V4.0 function uses self–approval. In other words, employees can record their attendance without requiring approval from their manager or supervisor. You can, however, enable approvals by configuring the Approval Required attribute for the Additional Training Entry and the Review Page activities within the External Training workflow process. See: Overview of Approvals, Implementing Oracle Self–Service Human Resources See: Overview of Approvals: page 8–2 See: Overview of Approvals: page 8–2 To integrate self–service training with a full installation of Oracle Training Administration, see Implementing Oracle Training Administration

Menu and Function Names
You can access this module from the following menus and functions:
User Menu Name Function Name

Employee Self–Service V4.0 Manager Self–Service V4.0

External Training V4.0 External Training V4.0

Workflow
The Training module uses a Workflow Process Display Name of External Training. No unique workflow attributes are used.

Training

21–5

Configurable Tips and Instructions
Region Name Tip Type Message Name

Additional Training Overview Top Additional Training Yes No Top Additional Training Entry Top Additional Training Entry Top

Instruction Instruction Instruction Instruction

OTA_13962_ADD_TRNG_OVIEW_TIP OTA_13961_ADD_TRNG_DEL_CNFR_SS OTA_13963_ADD_TRNG_ENTRY_TIP OTA_13964_ADD_TRNG_UPD_TIP

See: Adding Instructions to Web Pages: page 7–9

Configurable Flexfields
Region Name Flexfield Code Flexfield Name

Additional Training Entry Top

OTA_NOTRNG_HIST ORIES

Additional Non OTA Training History Information

See: Configuring Flexfields: page 7–6

Configurable Profile Options
The External Training module includes no applicable profiles. For further definitions of the OTA profile options, see Profile Options, Using Oracle Training Administration For general information about profile options, see: User Profiles (Configuring, Reporting, and System Administration in Oracle HRMS)

21–6

Oracle SSHR 4.2 Implementation Guide

External Linking (Self–Service Training)
The External Linking V4.0 module for self–service Oracle Training Administration generates hyperlinks to courses and events that training administrators can copy and paste into emails and Web pages. Clicking these hyperlinks enables employees to view, search for, and enroll in training events. To generate hyperlinks, training administrators access the Training Link Generation V4.0 function from their Training Administrator Self Service menu. You first search for the course or event, then the application generates a hyperlink in two forms, one a simple text hyperlink that bears the URL (Web address) of the course or event, the other a block of HTML code that you can copy and paste into a Web page or HTML mail. To copy the standard hyperlink, you generally right–click on the link, choose Copy Shortcut or equivalent from the contextual pop–up menu, then paste into the email or Web page (the specific procedures vary among browsers and platforms). Note that you may have to take an extra step to generate a hyperlink from the URL, depending upon the target application. In either form, these links give employees direct access to the self–service application. If the hyperlink refers to a course, they can search for events based on the course, then enroll in the selected event; if the hyperlink refers to an event, they can enroll directly in the event. The links enforce security by prompting employees for their self–service login before they can view and enroll in courses and events. Note that employees with multiple responsibilities or security profiles accessing this functionality cannot use the hyperlinks to enroll in events. These employees must use their standard self–service login procedure to view or enroll in courses or events. Note also that employees cannot enroll in courses outside their business group.

Menu and Function Names

ÁÁÁÁÁÁÁÁÁÁ Á Á Á Á Á Á Á Á Á Á Á ÁÁÁÁÁÁÁÁÁÁÁÁ Á Á Á Á Á Á Á Á Á Á Á ÁÁÁÁÁÁÁÁÁÁÁÁ Á Á Á Á Á Á Á Á Á Á Á ÁÁÁÁÁÁÁÁÁÁÁÁ Á Á Á Á Á Á Á Á Á Á Á ÁÁÁÁÁÁÁÁÁÁÁÁ Á Á Á Á Á Á Á Á Á Á Á ÁÁÁÁÁÁÁÁÁÁÁÁ Á Á Á Á Á Á Á Á Á Á Á ÁÁÁÁÁÁÁÁÁÁÁÁ Á Á Á Á Á Á Á Á Á Á Á ÁÁÁÁÁÁÁÁÁÁÁÁ ÁÁÁÁÁÁÁÁÁÁÁÁÁ
User Menu Name Training Administrator Self Service Global Self Service Functions Seed Employee Self Service V4.0 Function Name Training Link Generation V4.0 Training Link Access V4.0 Training Link Access V4.0 Training Link Access and Global Self Service Functions Seed are included on the Employee Self Service menu but are invisible to Employee Self Service users. The Training Administrator can access these functions for setup and error checking, but they work mainly in the background.
Training 21–7

To change menu structures or function names, or to modify workflow processes, you may wish to create your own versions of the Training Link Access and Training Link Generation functions. To copy and modify the supplied functions, you must change the parameter and HTML call values below. You can retain the other values. Training Link Access V4.0

Workflow

21–8

Oracle SSHR 4.2 Implementation Guide

ÁÁÁÁÁÁÁÁÁ Á Á Á Á Á Á Á Á Á Á ÁÁÁÁÁÁÁÁÁÁÁÁÁ ÁÁÁÁÁÁÁÁÁÁÁÁÁÁ Á Á Á Á Á Á Á Á Á ÁÁÁÁÁÁÁÁÁÁÁÁÁ Á Á Á Á Á Á Á Á Á Á ÁÁÁÁÁÁÁÁÁÁÁÁÁ Á ÁÁÁÁÁÁÁÁÁ Á Á Á Á Á Á Á Á Á Á ÁÁÁÁÁÁÁÁÁÁÁÁÁ ÁÁÁÁÁÁÁÁÁÁÁÁÁÁ ÁÁÁÁÁÁÁÁÁ Á ÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁ Á ÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁ Á Á Á Á Á Á Á Á Á Á ÁÁÁÁÁÁÁÁÁÁÁÁÁ Á Á Á Á Á Á Á Á Á Á ÁÁÁÁÁÁÁÁÁÁÁÁÁ ÁÁÁÁÁÁÁÁÁÁÁÁÁÁ ÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁ Á ÁÁÁÁÁÁÁÁÁ Á ÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁ Á Á Á Á Á Á Á Á Á Á ÁÁÁÁÁÁÁÁÁÁÁÁÁ Á Á Á Á Á Á Á Á Á Á ÁÁÁÁÁÁÁÁÁÁÁÁÁ ÁÁÁÁÁÁÁÁÁÁÁÁÁÁ ÁÁÁÁÁÁÁÁÁ Á ÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁ Á Á Á Á Á Á Á Á Á Á ÁÁÁÁÁÁÁÁÁÁÁÁÁ ÁÁÁÁÁÁÁÁÁÁÁÁÁÁ ÁÁÁÁÁÁÁÁÁ Á ÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁ ÁÁÁÁÁÁÁÁÁÁÁÁÁÁ Á Á Á Á Á Á Á Á Á ÁÁÁÁÁÁÁÁÁÁÁÁÁ Á Á Á Á Á Á Á Á Á Á ÁÁÁÁÁÁÁÁÁÁÁÁÁ Á Á Á Á Á Á Á Á Á Á ÁÁÁÁÁÁÁÁÁÁÁÁÁ Á ÁÁÁÁÁÁÁÁÁ Á ÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁ Á ÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁ Á Á Á Á Á Á Á Á Á Á ÁÁÁÁÁÁÁÁÁÁÁÁÁ Á Á Á Á Á Á Á Á Á Á ÁÁÁÁÁÁÁÁÁÁÁÁÁ ÁÁÁÁÁÁÁÁÁÁÁÁÁÁ
Parameter and Value &pProcessName=OTA_EXT_LINK_JSP_PRC &pCalledFrom=OTA_EXTERNAL_LINKING_SS &pOATrngFunc=OTA_ENROLL_SS &pTrngProcessName=OTA_ENROLL_IN_TRAINING_JSP_PRC Refers To Training Link Access Workflow process name Training Link Access function name Training V4.0 function name Training V4.0 Workflow process name Refers To Training Link Access function name Refers To Training Link Generation function name Training Link Access function name Refers To Training Link Generation function name HTML Call and Value &OAFunc=OTA_EXTERNAL_LINKING_SS Training Link Generation V4.0 Parameter and Value pCalledFrom=OTA_EXTERNAL_LINKING_URL_SS &pExternalLinkingFunc=OTA_EXTERNAL_LINKING_SS HTML Call and Value &OAFunc=OTA_EXTERNAL_LINKING_URL_SS Workflow Process Display Name: Training Link Access Configurable Workflow Attributes:

ÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁ Á Á Á ÁÁÁÁÁÁÁÁÁ Á Á ÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁ Á Á Á Á Á Á Á Á Á Á Á Á Á Á Á Á Á ÁÁÁÁÁÁÁ Á ÁÁÁÁÁ Á Á Á Á Á Á Á Á Á Á Á Á Á Á Á Á ÁÁÁÁÁÁÁ ÁÁÁÁÁÁÁÁ ÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁ Á Á Á ÁÁÁÁÁÁÁÁÁ Á Á ÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁ Á Á Á Á Á Á Á Á Á Á Á Á Á Á Á Á Á ÁÁÁÁÁÁÁ Á Á Á Á Á Á Á Á Á Á Á Á Á Á Á Á Á ÁÁÁÁÁÁÁ Á Á Á Á Á Á Á ÁÁÁÁÁÁÁ Á
Process Display Name Training Link Access Training Link Access Training Link Access Function Activity Display Name Cost Center Review Page V4.0 Review Page V4.0 Function Activity Attribute Display Name HR_APPROVAL_REQ_F LAG HR_APPROVAL_REQ_F LAG HR_DYNAMIC_APPROVAL_LEVEL

ÁÁÁÁÁÁÁÁÁÁÁÁÁ Á Á Á ÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁ Á Á Á ÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁ ÁÁÁÁÁÁÁÁÁ ÁÁÁÁÁÁÁÁÁÁÁÁÁ Á Á Á Á ÁÁÁÁÁ ÁÁÁÁÁÁÁÁÁÁÁÁÁ Á Á Á Á ÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁ ÁÁÁÁÁÁÁÁÁÁ Á ÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁ Á Á ÁÁÁÁÁÁÁÁÁÁÁÁÁ Á Á Á Á ÁÁÁÁÁ ÁÁÁÁÁÁÁÁÁÁÁÁÁ Á Á Á Á ÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁ Á Á Á ÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁ Á ÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁ ÁÁÁÁÁÁÁÁÁÁ Á ÁÁÁÁÁÁÁÁÁÁÁÁÁ Á Á Á Á ÁÁÁÁÁ ÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁ Á Á Á Á ÁÁÁÁÁÁÁÁÁÁÁÁÁ Á Á Á ÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁ Á ÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁ ÁÁÁÁÁÁÁÁÁÁ Á ÁÁÁÁÁÁÁÁÁÁÁÁÁ Á Á Á Á ÁÁÁÁÁ ÁÁÁÁÁÁÁÁÁÁÁÁÁ Á Á Á Á ÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁ ÁÁÁÁÁÁÁÁÁÁ Á ÁÁÁÁÁÁÁÁÁÁÁÁÁ Á Á Á Á ÁÁÁÁÁ ÁÁÁÁÁÁÁÁÁÁÁÁÁ Á Á Á Á ÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁ ÁÁÁÁÁÁÁÁÁÁ Á ÁÁÁÁÁÁÁÁÁÁÁÁÁ Á Á Á Á ÁÁÁÁÁ ÁÁÁÁÁÁÁÁÁÁÁÁÁ Á Á Á Á ÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁ ÁÁÁÁÁÁÁÁÁÁ Á ÁÁÁÁÁÁÁÁÁÁÁÁÁ Á Á Á Á ÁÁÁÁÁ ÁÁÁÁÁÁÁÁÁÁÁÁÁ Á Á Á Á ÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁ Á Á ÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁ ÁÁÁÁÁÁÁÁÁÁ Á ÁÁÁÁÁÁÁÁÁÁÁÁÁ Á Á Á Á ÁÁÁÁÁ ÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁ Á Á Á Á Á ÁÁÁÁÁÁÁÁÁÁÁÁÁ Á Á Á ÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁ ÁÁÁÁÁÁÁÁÁ ÁÁÁÁÁÁÁÁÁÁÁÁÁ Á Á Á Á ÁÁÁÁÁ ÁÁÁÁÁÁÁÁÁÁÁÁÁ Á Á Á Á Á ÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁ Á Á ÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁ Á Á Á ÁÁÁÁÁÁÁÁÁÁÁÁÁ Á Á Á Á ÁÁÁÁÁ Á Á ÁÁÁÁÁÁÁÁÁÁÁÁÁ Á Á Á Á ÁÁÁÁÁ ÁÁÁÁÁÁÁÁÁ Á ÁÁÁÁÁÁÁÁÁÁÁÁÁ Á Á Á Á ÁÁÁÁÁ ÁÁÁÁÁÁÁÁÁÁÁÁÁ Á Á Á ÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁ Á Á ÁÁÁÁÁÁÁÁÁÁÁÁÁ Á Á Á Á ÁÁÁÁÁ ÁÁÁÁÁÁÁÁÁÁ Á
Configurable Tips and Instructions
Attribute Name OTA EL Adv Help Tip 2 Srch Criteria OTA EL Adv Help Tip 2 Srch Search Results OTA EL Help Tip Center Search Criteria OTA EL Help Tip 2 Center Search Results OTA EL Help Tip Course Header OTA EL Help Tip Course Header OTA ELU Help Tip 1 URL Main OTA Help Tip 1 ExtLinking URL Act Search Criteria OTA Help Tip 2 ExtLinking URL Act Search Results OTA ELU Help Tip Center Search Criteria OTA ELU Help Tip 2 Center Search Results Region OTA_SS_TRN_CENTER_SEARCH_TIP OTA_SS_SIMPLE_SEARCH_TIP OTA_13970_ELU_ACT_RSLT_TIP OTA_SS_ADVANCED_SEARCH_TIP OTA_13987_ELU_HYPERLINK_TIP OTA_13975_EL_ACT_TIP OTA_13975_EL_ACT_TIP OTA_SS_TRN_CENTER_SEARCH_TIP OTA_SS_SIMPLE_SEARCH_TIP OTA_SS_SEARCH_RESULT_TIP OTA_13971_EL_EVT_SRCH_TIP Message Name

Training

21–9

ÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁ Á Á Á ÁÁÁÁÁÁÁÁÁÁ Á ÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁ ÁÁÁÁÁÁÁÁ Á ÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁ ÁÁÁÁÁÁ ÁÁÁÁÁÁÁÁÁÁ Á Á Á ÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁ ÁÁÁÁÁÁÁÁ Á ÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁ ÁÁÁÁÁÁ ÁÁÁÁÁÁÁÁÁÁ Á Á Á Á ÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁ ÁÁÁÁÁÁÁÁÁÁÁÁÁ Á ÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁ ÁÁÁÁÁÁÁÁÁÁ Á Á Á Á ÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁ Á Á ÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁ Á Á ÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁ Á Á ÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁ Á ÁÁÁÁÁÁ Á ÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁ ÁÁÁÁÁÁ ÁÁÁÁÁÁÁÁÁÁ Á Á Á ÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁ ÁÁÁÁÁÁÁÁÁÁÁÁÁ Á ÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁ ÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁ Á Á Á Á ÁÁÁÁÁÁÁÁÁÁ Á Á ÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁ ÁÁÁÁÁÁÁÁ Á ÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁ ÁÁÁÁÁÁ ÁÁÁÁÁÁÁÁÁÁ Á Á Á ÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁ Á Á ÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁ Á Á ÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁ Á Á ÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁ ÁÁÁÁÁÁÁÁÁÁÁÁÁ Á
Region OTA EL Activity Details DFF Region OTA EL Activity Desc Flex Region OTA EL Main Event Details Page OTA EL Event Location OTA ELU Activity Desc Flex Region OTA ELU Main Event Details Page OTA ELU Event Location OTA EL Additional Enrollment Details Region 2 Descriptive Flexfield Descriptive Flexfield Descriptive Flexfield Descriptive Flexfield Descriptive Flexfield Descriptive Flexfield Descriptive Flexfield Attribute Name Descriptive Flexfield OTA_DELEGATE_BOOKINGS Address Location OTA_EVENTS OTA_ACTIVITY_VERSIONS Address Location OTA_EVENTS OTA_ACTIVITY_VERSIONS Flexfield Name OTA_ACTIVITY_VERSIONS

ÁÁÁÁÁÁÁÁÁÁÁÁÁ Á Á ÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁ Á Á ÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁ ÁÁÁÁÁÁÁÁÁÁ Á ÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁ ÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁ Á Á Á Á ÁÁÁÁÁÁÁÁÁÁÁÁÁ Á Á Á ÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁ Á ÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁ Á Á ÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁ ÁÁÁÁÁÁÁÁÁÁ Á
OTA ExtLinking URL Evt Search Criteria OTA ExtLinking URL Evt Search Results Help Tip 2 Help Tip 1 OTA_13972_ELU_EVT_RSLT_TIP OTA_13971_EL_EVT_SRCH_TIP

Configurable Profile Options

Configurable FlexFields

21–10

Oracle SSHR 4.2 Implementation Guide

This module contains no configurable profile options.

CHAPTER

22

Compensation Workbench

Compensation Workbench

22–1

Compensation Workbench Overview
Line managers and other employees responsible for distributing compensation use Compensation Workbench to issue budgets to reporting managers responsible for budgeting and to allocate compensation awards to individual employees, promote employees, and rate employee performance. Using the Oracle HRMS professional user interface, a compensation manager or system administrator defines Compensation Workbench plans based on the Total Compensation data model.

Budgets
High–level managers set distribution budgets for all of the subordinate managers in their organizations. The budget provides a variety of information to a manager, such as the available amount to budget, the amount used, and any amount reserved for future use that is not issued to reporting managers. You can define budgets as monetary amounts or as a percentage of eligible salary. There is an Allocations Wizard that can help high–level managers create a budget, if they do not want to manually set the budget. Reporting managers receive Workflow notifications automatically when a higher–level manager issues a budget, and the budget appears in the manager’s Allocation Worksheet. See: Compensation Workbench Budget Preparation: page 22–8

Worksheets
Compensation Workbench uses Worksheet Groups within the worksheet as the collection point of information for managers to use when evaluating eligible employees. Worksheet groups allows managers to make discreet changes to employees. Compensation Workbench includes the following worksheets in the worksheet group:

Allocations Worksheet Groups After the budget has been set by a high–level manager, reporting managers can determine how to allocate compensation or awards to employees within their organizations. Like the high–level manager, they can use the Allocation Wizard to help set allocations automatically.

22–2

Oracle SSHR 4.2 Implementation Guide

or grade for any eligible employee in their reporting structure. position. Oracle’s Personalization feature is expanded for Compensation Workbench to allow for Plan–level Personalization. Employees with the appropriate security access can also rate employees using the Switch Manager. they send it for approval using Oracle Workflow. The following notifications are available: • • • • Your manager has issued you a budget A higher–level manager has changed the due date or access level of your worksheet or budget Your manager has Approved or Rejected your worksheet A reporting manager has submitted their worksheet for your approval Higher–level managers can approve.Note: Managers cannot allocate themselves an award. you can personalize the Worksheet Groups by plan. Note: The workflow process requires approval at the highest level of your organization hierarchy. managers can change data related to a job. modify. Additionally. which routes a notification to each approver through a configurable notification hierarchy. Compensation Workbench 22–3 . or return a submitted worksheet to any reporting manager below them in the hierarchy. • Performance Worksheet Group Employee Performance Rating allows managers to rate and rank the performance of any eligible employee in their reporting structure. Personalization allows you to modify the data that line managers see and are able to update in each worksheet group for a compensation plan. Employees with an appropriate security access can also record promotions using the Switch Manager. See: Employee Performance Rating: page 22–16 See: Promotions: page 22–13 See: Allocations: page 22–11 See: Switch Manager: page 22–21 See: Personalizing a Plan for Compensation Workbench: page 22–39 Approvals When managers complete their worksheet. • Promotions Worksheet Group Using the Self–Service interface.

you need to include the appropriate Compensation Workbench function and submenus in your new menu. If the worksheet is approved. You cannot approve some changes and not others. This controls the various tabs that display in Compensation Workbench. Add the Compensation Workbench Main Menu submenu. be sure to add the following functions and submenus: • • • Add the Compensation Workbench Home for Administrators functionto the menu and give the function a Prompt. This adds menu functions specific to Compensation Workbench to the Self–Service Global menu. then all the changes proposed in the worksheet are approved. The system maintains the changes in a temporary state––until approved––and the worksheet is visible only in the managers’ Self Service view from Compensation Workbench. In your new menu. Upon approval. See: Compensation Workbench Approvals and Notifications: page 22–22 Copying the Seeded Menu If you create your own menu based on the seeded HR Professional V4.2 Implementation Guide .An approver must approve the worksheet groups within a worksheet as a whole. Add the Compensation Workbench Global Menu submenu. See: Configuring the Global Button Bar : page 7–10 22–4 Oracle SSHR 4. you run a post–process that updates all HRMS data regarding these changes.0 menu.

including the following: • • • Salary increases Bonuses Stock Options You can also use Compensation Workbench to perform Promotions and Performance rankings. Can other managers fill in for me if I am unavailable? Using the Switch Manager.Compensation Workbench Using Compensation Workbench. managers can view employee details for their direct reports and any employee further down in the reporting hierarchy. Compensation Workbench 22–5 . You can issue monetary amounts or percentages of eligible salaries. you can determine and allocate compensation and awards for your enterprise. deployed on your intranet. A high–level manager in the hierarchy issues budgets to managers who have direct reports –– and these direct reports can be managers as well. You can update certain employee information in Compensation Workbench. Additionally. you can act as another manager within your security profile. How are budgets prepared? You can define a budget at the top–level of an organization hierarchy. How are compensation allocations awarded? A line manager uses the Allocation Worksheet to award compensation to any employee at a lower level in the reporting hierarchy. so you do not have to change functions while you are working in your compensation cycle. Can managers view employee details from Compensation Workbench? Yes. you can auto–issue a predefined budget (typically as a flat percentage of eligible salaries) to all allocating managers. Line managers cannot allocate their own compensation. and view or make updates to another manager’s worksheet. You can also use the Allocation wizard to help you calculate the amount/percentages to issue.

Can I Budget and Allocate Compensation Based on Salary Components? If you itemize a compensation plan into two or more components––for example. The employee reassignment is valid for the selected compensation plan and enrollment period and does not affect the current supervisor relationship. or stock award. position. Can managers promote and rate or assess employees at the same time as allocating salaries? Yes. Self–service Compensation Workbench uses the same jobs. and employee performance ranking? Oracle HRMS routes a completed worksheet for approval based on position or supervisor–hierarchy as specified in the enrollment requirements for the compensation plan. promotions.” Does Compensation Workbench handle approving allocations. You can link compensation components to Oracle HRMS salary components.2 Implementation Guide . bonus.Can managers assign employees to their own worksheets? The Employee Reassignment feature provides managers a facility to add an employee to their own worksheets as well as to assign employees to other managers’ worksheets. using the Promotion and Performance features. you can process a promotion or complete a performance rating and ranking in conjunction with processing a pay increase. Cost of Living and Performance––you can budget and allocate for each component. 22–6 Oracle SSHR 4. There is a single approval for the entire worksheet. and grades as the compensation professionals use in the “back office.

Compensation Workbench For a full functional description of the Compensation Workbench. Compensation Workbench 22–7 . see: Compensation Workbench: page 22–2.0 Compensation Workbench Workflow Not applicable Configurable Tips and Instructions Not applicable. Configurable Profile Options Not applicable. Menu and Function Names This module can be accessed from the following menus and functions: User Menu Name Function Name Manager Self–Service V4. Configurable FlexFields Not applicable.

22–8 Oracle SSHR 4. • Auto–issuing budgets gives the compensation professional control over the amount a manager can allocate to reporting employees and creates a uniform compensation distribution across the enterprise. The budget provides a variety of information. Budget Issuance To begin the budgeting process. You can set up variable rate profiles to vary the available percent based on a variety of eligibility criteria. You can define a budget using monetary amounts or percentages of eligible salaries. Managing Total Compensation Using Oracle HRMS The Allocation Wizard The Allocation Wizard provides a variety of calculation types that automatically calculate the budget for one or more selected managers. Typically. See: Defining Enrollment Requirements for Compensation Workbench Plans. you base auto–issued budgets on a flat percentage. A manager can determine a reporting manager’s budget manually or by using the Allocation Wizard. the amount used. such as the available amount to budget. a compensation manager does one of the following: • Uses the Person Life Events window––located in the professional user interface––to issue a budget to a high–level manager who issues budgets to other managers. You can choose to maintain fixed amounts or to recalculate the budget based on a percentage. you determine how changes to a lower–level manager’s list of employees affect a budget.Compensation Workbench Budget Preparation You can define a budget at the top level of an organization hierarchy.2 Implementation Guide . Sets up the compensation plan so that a predefined budget is auto–issued to the Worksheet for all managers when you run the Participation Process: Compensation. and any amount reserved for future use that is not issued to reporting managers. Reporting managers receive Workflow notifications automatically when a higher–level manager issues a budget. A high–level manager issues distribution budgets to managers who have direct reports who are also managers. During plan design. Helpful tips located in Compensation Workbench self–service interface explain the features of each calculation type.

Here you can enter the percentage of eligible salary and choose the recalculate button to view the updated totals from this matrix. Compensation Workbench 22–9 . This will show two numbers under each cell: number of employees and total eligible salaries for the number of employees. you select criteria only for “Row Criteria. Here you can enter a percentage of eligible salary for each row and column. You may also choose to save a Matrix definition for a later use. Eligible Salary. and legend. Percentage of Eligible Salary. the page displays a two–dimensional table with all the unique values for the selected criteria as row and column headers for the selected employees. After you click Apply. If you enter the percent of eligible salary. Selecting this distribution method displays the Matrix page. the page displays a single dimensional table with all the unique values of the selected criteria as row headers for the selected employees. A Legend displays on top of the table describing each cell. The matrix displays the Number of Employees. Here. of the new salary. and Total as the column headers. You may also choose to Show Details. To hide the details. The application recalculates the percent and new salary after obtaining the rounded amount.Budget and Worksheet Rounding You can enter an amount or percent without it being automatically rounded. Budget and Allocation Matrix The Allocation Wizard includes an additional distribution method–– Distribute Based on Criteria––for calculating budget or worksheet amounts. Managers can set criteria for one of two types of matrices. you can choose the Recalculate button to view the updated totals. The professional user can also omit the rounding codes for rates so amounts are always rounded using the same rounding rules as the plan currency.” After you click Apply on the Allocations page. a line manager can set or revise the budget or worksheet allocations based on common employee criteria. and Two Dimensional (Two Criteria). choose Hide Details. For a single–dimensional matrix. you select criteria for Rows and Columns. and not the percent. For a two–dimensional matrix. Rounding codes you enter on the worksheet and budget sheet apply to the amount. Single Dimensional (One Criteria).

2 Implementation Guide . and Create New Criteria Matrix. Click the “Revert Matrix Criteria” button to display two regions.Save the Matrix by entering a name in the Matrix Name field. The named matrix is available in the Recall Saved Criteria Matrix list of values. or create a new matrix with varying row and column criteria. Recall Saved Criteria Matrix. You can choose to recall a previously saved matrix. 22–10 Oracle SSHR 4.

a line manager can use the allocation wizard to help determine compensation awards.Compensation Workbench Allocations A line manager uses the Allocations tab on the worksheet to allocate compensation to any eligible employee at a lower level in the reporting hierarchy. As with budgets. The data in the detail region shows the manager detailed information about the employee. See: Employee Eligibility for Compensation Workbench: page 22–18 Compensation Workbench 22–11 . The worksheet displays a variety of information about an employee that a manager can view to help determine an allocation. Note: Line managers cannot allocate their own compensation. work information. You may choose to select the Show icon on the Allocations Table to display the detail region. such as personal information. and recent compensation awards. You can define a plan so that a manager can view historical information about compensation awarded to an employee.

Compensation Workbench Itemization
You can itemize a compensation plan into components so that your line managers budget and allocate compensation for discrete factors, such as Merit or Cost of Living. Itemization provides for a focused approach to adminstering salary increases and awards. You can link a compensation component to a salary component. At the end of a salary review cycle, you run the Compensation Workbench Post Process to update salary components with the new values stored by the compensation components. A component is equivalent to an option in the Total Compensation data model. After you set up your components using the Options window, you link the options to the compensation plan. Here are some guidelines to consider if you itemize your plan:
• • •

You should attach two or more components to the plan. If you budget, you must budget for at least one component, but you are not required to budget for each component in the plan. Coordinate your activity rates so that you record rates for the component, rather than the plan.

22–12

Oracle SSHR 4.2 Implementation Guide

Compensation Workbench Promotions
Depending on your company’s business needs, compensation plans may be designed to allow managers to change an eligible employee’s job or promote the employee during the same cycle that salary, bonus, or stock is awarded — or a separate promotions plan may be created to enable managers to change an employee’s job or promote as a separate and distinct action. Compensation Workbench Promotions provides managers with a complete list of eligible employees to promote (and to award compensation) that will help them select the best people to promote and to maintain equity and fairness within the manager’s organization. Using Self–Service, managers can assign a new job, position, or grade, or change the Assignment Descriptive Flexfield or soft–coded Legislative Flexfield for any employee in their reporting structure. Employees with an appropriate security access can also record promotions using the Switch Manager. Managers can also change some employee details directly, depending on which fields are available to them. You can configure the Worksheet Group using Personalization and select the columns that managers may view and update. For instance, if you use Personalization, you may allow managers to update the Job, but not the Position, then the self–service page will display Old Job and New Job, but not Old Position, New Position. The Old value will always show data as of the effective date. New data will show only if it has been changed. You can make the following available using Personalization for update using Compensation Workbench:

Assignment Change Reason Note: This indicates the reason that a promotion or job change has occurred.

• • •

New Job New Position New Grade Employee Name Employee Full Name Old Job Old Position Old Grade

You can view the following information while Promoting an employee:
• • • • •

Compensation Workbench

22–13

See: Switch Manager: page 22–21 See: Employee Eligibility for Compensation Workbench: page 22–18

Processing the Promotion
Once you complete the worksheet, you route it for approval. The application maintains the changes in a temporary state––until approved––and the changes are visible only in the managers’ self–service view of Compensation Workbench. If the higher–level manager approves the worksheet, then all the changes are approved. You cannot approve some changes and not others. Upon approval, you run a post–process that updates all new or changed HRMS data. Once the worksheet is approved, you run a post process, which updates the employee’s assignment record to reflect the approved job changes and/or promotion.

Compensation Plan Design
There are different ways to design your Compensation Plan to take advantage of Compensation Workbench features, each with its own benefits. You can:

Create a plan that allows managers to make job changes and promotions at the same time that compensation is awarded. This plan speeds up the annual review process because all changes that affect a person’s compensation can be submitted, reviewed, and approved at once. This helps managers award compensation to employees in the position, job, or grade equitably, and reduces the amount of plan design setup required.

Create a plan that only allows managers to process job changes and promotions. This allows you to schedule a compensation period after all job changes / promotions are given. This is helpful when compensation limits or recommendations are based on an employee’s assignment information.

Modifying an Existing Plan
You can modify an existing compensation plan to allow for jobs changes and / or promotions.

22–14

Oracle SSHR 4.2 Implementation Guide

If you add the Job Change/Promotions Worksheet group to an existing plan, and the allocations have been approved and the Post Process has run, and you only select the Job Changes/Promotions worksheet to display, then managers will only be able to see the Job Changes/Promotions worksheet group. The previously made allocations will be stored, though hidden from view. If you add the Job Changes/Promotions worksheet group to an existing plan and allocations have not yet been approved or submitted, and managers are allowed to allocate compensation, then both the Job Changes/Promotions and Compensation Worksheet groups should be added to the Plan Definition window. Note: Changing the worksheet groups after the Participation Process runs does not require rerunning the Participation Process.

Compensation Workbench

22–15

Compensation Workbench Employee Performance Rating
Employee Performance Rating allows managers to rate and rank any eligible employee in their reporting structure. Employees with the appropriate security access can also rate employees using the Switch Manager. Compensation Workbench allows managers to see all of their employees in a single view. Because managers can see each employee in relationship to others, the process of rating employee performance should be more fair and objective. Managers can view their employees’ last performance ranking and then assign them a new one. You can complete your employee ratings and ranking before or during a promotions or compensation cycle, depending on how your business operates, and this will dictate your plan design and setup. You can configure the Worksheet Group using Personalization and select the columns that managers may view and update. Depending upon Personalization, managers can view and update information regarding the employee, as follows:
• •

Rank Rating

Additionally, you can view the following information while ranking an employee for performance:
• • • •

Employee’s Name Employee’s Full Name Number of Years Employed Total Ranked Note: This is the total ranked by the current manager. Other’s Rank Note: This is the rank of the employee given by the line manager, and only displayed to the manager approving the worksheet.

Rating Type Note: Rating is a List of Values can can be updated at your site.

Previous Rating Date

The worksheet has to be approved as a whole.

22–16

Oracle SSHR 4.2 Implementation Guide

Once a manager completes the worksheet, it is sent for approval. The system maintains the changes in a temporary state–– until approved–– and changes are visible only in the managers’ Self Service view from Compensation Workbench. If the worksheet is approved, then all the changes are approved. You cannot approve some changes and not others. Upon approval, you run a post process that updates all HRMS data regarding these changes.

Compensation Workbench

22–17

Employee Eligibility for Compensation Workbench
A manager can view employee details for his or her direct report––and any eligible employee farther down in the reporting hierarchy––in Compensation Workbench. When you set up your Compensation Workbench plan in Oracle HRMS, you can define participant eligibility profiles to determine if an employee is eligible to receive an award, a promotion, or even a performance evaluation. A compensation administrator can override eligibility results in the professional user interface. Additionally, a compensation administrator can move an employee from one manager’s worksheet to another manager’s worksheet. See: Employee Reassignment for Compensation Workbench: page 22–19

View and Update Employee Eligibility
Managers can update employee eligibility when they have “update access” to their own worksheet. Managers can update employee eligibility for all direct report employees and employees assigned to their worksheet for the selected compensation plan. To give a manager update access to their worksheets, select Updateable in the Worksheet Access field on the Person Life Events window for each manager. The employee eligibility page displays the ineligibility reason for employees ineligible for the plan. In addition, if eligibility has been overridden in the past, the person who did the override and the date of action displays. However, updates to an employee’s eligibility may not be made after the worksheet has been submitted for approval, or if another manager has submitted an eligibility change. Managers without update access may only view employee eligibility for all direct report employees and employees assigned to their worksheet for the selected compensation plan. Managers can view eligibility when the session date is within the availability period defined for the plan and enrollment period, and there is at least one eligible employee in the manager’s worksheet for the plan.

22–18

Oracle SSHR 4.2 Implementation Guide

Employee Reassignment for Compensation Workbench
Employee Reassignment provides managers a facility to add employees to their worksheets as well as assign employees to other managers’ worksheets. The employee reassignment is valid for the selected compensation plan and enrollment period, and does not affect the current supervisor relationship. Employee Reassignment enables managers to award a bonus or other type of compensation to an employee who does not report to them, but who may have performed some task for the manager that warrants compensation. Employee Reassignment also enables managers to cover for one another when absent during a compensation award period. Employee Reassignment uses supervisor or position hierarchy to determine required approvals and the subsequent approver in the approval chain. The approver may approve or reject the employee reassignment. Compensation Workbench includes two default approval and notification workflows.

Reassigning an Employee
You navigate to the Select Employees to Reassign page by choosing Employee Reassignment under the Worksheet tab. You can search for a Worksheet Manager, or an Employee Name. The search results display in the lower region of the page, listing the Employee Name, Employee Number, Job, Worksheet Manager, and Supervisor. Here, you can choose those employees you wish to reassign, or view pending details. The employee’s earlier assignment is in pending status if a clock icon displays next to an employee’s name. You cannot reassign an employee who is in a pending status. However, you can view the pending details for the employee by clicking the icon, which displays the Pending Details page for the employee. This page shows the Pending Worksheet Manager name, the Requestor Name, Requested Date, and the name of the Next Approver. If you click the Reassign button, a page displays where you can enter the new manager’s name. Click Next to review the employees to be reassigned. On the Review page, you can enter comments for the current and or proposed worksheet managers. After you review the employees you wish to reassign and enter any comments, you can submit your request. A page displays to confirm your request. Changes on the manager’s worksheet may require approval before they appear on the new manager’s worksheet. The approval process and notifications use Workflow/AME. There are three terms used for each approval process:

Compensation Workbench

22–19

• • •

Party 1 is the manager whose worksheet is losing the employee Party 2 is the manager whose worksheet gains the employee Requestor is the person who requests the reassignment. The requestor may or may not be one of the two parties.

The three delivered approvals are:
• • •

Approval 1: Party 1 is a single approver in which the approver is Party 1. Party 1 can Approve or Reject the request. Approval 2: Party 2 is a single approver in which the approver is Party 2. Party 2 can Approve or Reject the request. Approval 3: Party 3 is No approver necessary.

Party 1 and Party 2 receive notifications to inform them about a change of worksheet manager if approval is not required. Party 1 and Party 2 receive notifications to inform them that a reassignment request has been submitted for approval if approval is required. Party 1, Party 2, and the requestor receive approval notifications. Rejection notifications are only sent to the requestor. When you receive the notification of pending employee reassignment, you can view all the details, and either approve, reject, or reassign. This will initiate the approval and notification process again.

22–20

Oracle SSHR 4.2 Implementation Guide

Switch Manager
You access Switch Manager from the Compensation Workbench Bench home page. You can search for a specific manager, switch to a recently selected manager, or switch back to your original identity. The Switch Manager allows users to switch their identity to any of the worksheet managers available under their security view. Using this feature, you can quickly act as another manager within your security profile, and view or make updates to another manager’s worksheet without drilling down within the worksheet. Compensation professionals use Switch Manager to act as a Super–User. Compensation Workbench is delivered with Switch Manager enabled for the HR Professional V4.0 responsibility. A system administrator can disable Switch Manager, if necessary. To disable Switch Manager, open the Form Functions window and query Compensation Workbench Home for Administrators in the User Function Name field. Choose the Web HTML tab to display the following HTML Call: OA.jsp?akRegionCode=BEN_CWB_HOME_PAGE&akRegionApplication Id=805&displayDate=N&displaySwitchManager=Y Change displaySwitchManger=Y to displaySwitchManger=N to prevent anyone using a responsibility with this menu and function from having access to the Switch Manager on the Compensation Workbench home page.

Switch Manager Search Page
If a manager does not appear in your poplist, you can search for a manager using the Switch Manager Search page. This allows you to search for managers based on various search options such as:
• • •

Employee Name Employee Number Email Address

The Results region of the search page returns all managers that meet the search criteria entered. You click on the manager’s name to initiate the Switch Manager functionality.

Compensation Workbench

22–21

the date the mail was sent. complete details about the mail. the manager submits the worksheet and Oracle HRMS routes it for approval based on position or supervisor hierarchy (as defined in the enrollment requirements for the compensation plan). the manager’s full name. If you choose the subject of any notification. If the manager logging into Compensation Workbench has the Switch Manager ability and switches to a different manager. All job changes and promotions must be approved or rejected together. See: Switch Manager: page 22–21 22–22 Oracle SSHR 4. Notifications on the Home Page Managers can see a snapshot of their five most recent. the Self–Service workflow process assigns a submitted worksheet a status of Pending Approval and routes a notification to each approver through a configurable notification hierarchy. the other manager’s notifications are not displayed. choose the Close button within the Response region. If more than five notifications exist. You can view the complete details of any of the five notifications by clicking on the subject. open Compensation Workbench notifications on their Compensation Workbench home page. you can choose to view the full list of open notifications by choosing Full List. Managers are able to close notifications from this page. All information is considered part of one worksheet once a manager submits the worksheet for approval. the approving manager can drill down to a lower level manager’s worksheet and make changes to it before approving the worksheet and sending it to the next level for approval. If you require worksheet approval. and a response section indicating if a response is required. To close a notification.Compensation Workbench Approvals and Notifications When done. removing the notifications from the notifications list. plus room for a response. However.2 Implementation Guide . the details page displays where you can view the subject of the email notification.

Compensation Workbench 22–23 . you attach an element and input value to this standard rate to pass the allocation to payroll. Standard Rate Activity Types CWB Worksheet Amount This activity type stores a manager’s worksheet allocations for an employee in money or shares. The rates can allow input from a manager––to complete a distribution––or provide guidance for a manager’s decision–making. do not attach an element to this rate. define the Distribution Budget rate so that it is equal to the Worksheet Budget rate. The activity type you select when you define a standard rate determines how and where Compensation Workbench uses the rate.Standard Activity Rates for Compensation Workbench You can define standard rates to meet a variety of business needs for a Compensation Workbench plan. Leave the Enter Value at Enrollment and Enter Annual Value fields unchecked. See below for a description of activity types that have specific functions for Compensation Workbench. You can also base a rate on a multiple of compensation that uses a derived compensation factor you have defined. This is an employee’s award amount. Most rates display fixed or enterable amounts that appear as columns in the self–service interface. Enter the auto–issue percent or amount in the Flat Amount field. If you auto–issue budgets. For salary updates. Check the Assign on Enrollment field so that the Compensation Workbench Post Process can write the element entry (for bonus and stock plans) or update the person’s salary amount (for salary plans) and salary element. For bonuses and stock options. Required? Maximum Defined Per Plan or Option Assign on Enrollment Recommendation Enter Value at Enrollment Recommendation Override Recommendation Unit of Measure Recommendation Attach elements? Required One Checked Checked Checked Blank or Shares Yes CWB Distribution Budget This activity type stores the budget amount or percent of eligible salaries issued by a high–level manager to another manager.

Leave the Enter Value at Enrollment and Enter Annual Value fields unchecked. Required? Maximum Defined Per Plan or Option Assign on Enrollment Recommendation Enter Value at Enrollment Recommendation Override Recommendation Unit of Measure Recommendation Attach elements? Required if budgeting One Unchecked Checked (Unchecked for auto–issued budgets) Checked Shares of Blank if monetary No CWB Worksheet Budget The total monetary or share amount available to a manager to distribute to employees. Enter the auto–issue percent or amount in the Flat Amount field. you must define reserve rates at the same level. Required if budgeting One Unchecked Checked (Unchecked for auto–issued budgets) Checked Shares or Blank if monetary No Required? Maximum Defined Per Plan or Option Never required One 22–24 Oracle SSHR 4. If you define distribution rates for components (options in plan).2 Implementation Guide . Required? Maximum Defined Per Plan or Option Assign on Enrollment Recommendation Enter Value at Enrollment Recommendation Override Recommendation Unit of Measure Recommendation Attach elements? CWB Reserve A reserve enables a manager to retain a certain amount of money or shares in a budget for distribution at a later time. If you auto–issue budgets. If you auto–issue budgets. define the Worksheet Budget rate equal to the Distribution Budget rate.Use the Preserve Budget Column field on the Plan Enrollment Requirements window to set whether the application stores budgets as amounts or percents. you should not define a reserve rate since managers will not have access to the Budget sheet to reserve any portion of their budget.

and recommended for bonus and salary plans if you budget by amount. Unlike eligible salary. you cannot prorate stated salary. Required? Maximum Defined Per Plan or Option Assign on Enrollment Recommendation Enter Value at Enrollment Recommendation Override Recommendation Unit of Measure Recommendation Attach elements? Never required One Unchecked Unchecked Checked Blank No Required if distributing budgets by percentage One Unchecked Unchecked Checked Blank No Compensation Workbench 22–25 . Required? Maximum Defined Per Plan or Option Assign on Enrollment Recommendation Enter Value at Enrollment Recommendation Override Recommendation Unit of Measure Recommendation Attach elements? CWB Stated Salary Use for salaries that can be converted to a different frequency than the one set in a person’s pay basis. you must define Eligible Salary rates at the same level.Assign on Enrollment Recommendation Enter Value at Enrollment Recommendation Override Recommendation Unit of Measure Recommendation Attach elements? CWB Eligible Salary Unchecked Checked Checked Blank or Shares No This activity type is required if you distribute budgets by percentage. You can prorate an employee’s salary based on length of service using a FastFormula rule to determine their eligible salary. If you define Worksheet Amount rates for components (options in plan). Use stated salary if you want an amount other than eligible salary. The Eligible Salary rate uses a derived compensation factor to determine an employee’s eligible salary. The stated salary is stated as of a specific date and is usually a multiple of a compensation factor.

vacation hours. you must define Recommended Amount rates at the same level. Required? Maximum Defined Per Plan or Option Assign on Enrollment Recommendation Enter Value at Enrollment Recommendation Override Recommendation Unit of Measure Recommendation Attach elements? Never required One Unchecked Unchecked Unchecked Blank No CWB Misc Rate 1. 2. A manager can distribute a recommended amount using the Allocation Wizard. and 3 You can define miscellaneous standard rates to use for storing any numeric value in Compensation Workbench. Required? Maximum Defined Per Plan or Option Assign on Enrollment Recommendation Enter Value at Enrollment Recommendation Override Recommendation Unit of Measure Recommendation Attach elements? Never required One of each Unchecked Unchecked Unchecked Blank if monetary. for example. Miscellaneous rates often require a FastFormula rule to derive a value. If you define Worksheet Amount rates for components (options in plan).2 Implementation Guide . Often. or length of service. You can rename these columns in the self–service interface. or use any value––this has no impact on processing No CWB Recommended Amount Displays minimum and maximum recommended compensation increases or awards on the worksheet. performance ratings. Required? Maximum Defined Per Plan or Option Never required One 22–26 Oracle SSHR 4. recommended rates use variable rate profiles––based on a percentage of a multiple of compensation––to derive the recommend increase based on an employee’s compensation.CWB Other Salary Used when eligible and stated salary are not sufficient to display the result of a calculated derived factor in Compensation Workbench.

As an estimate. You can display the grant price on the Worksheet History page and through reports. You enter the grant price as a parameter when you run the Compensation Workbench Post Process. The Post Process overrides this value with the value you enter when you run the process.Assign on Enrollment Recommendation Enter Value at Enrollment Recommendation Override Recommendation Unit of Measure Recommendation Attach elements? Unchecked Unchecked Checked Blank or Shares No CWB Total Compensation The total of a person’s compensation stated as a monetary amount. You must define a derived factor that provides the total through a balance or a FastFormula rule. Note: Define the CWB Grant Price activity rate even if you do not know the grant price. you can enter the grant price in Compensation Workbench. Required? Maximum Defined Per Plan Assign on Enrollment Recommendation Enter Value at Enrollment Recommendation Override Recommendation Unit of Measure Recommendation Attach elements? Never required One Checked Unchecked Checked Blank No Never required One Unchecked Unchecked Checked Blank No Compensation Workbench 22–27 . Required? Maximum Defined Per Plan Assign on Enrollment Recommendation Enter Value at Enrollment Recommendation Override Recommendation Unit of Measure Recommendation Attach elements? CWB Grant Price Records a stock option grant price if you maintain a grant price in Oracle HRMS. Attach this derived factor to the rate that uses this activity type.

for example). you could link the elements used to record the signing bonus to a Compensation Workbench bonus plan. For example.2 Implementation Guide . Assign this standard rate a status of inactive to prevent the Participation Process: Compensation from processing the rate.CWB Additional Element History Displays element entry history for compensation elements distributed outside of Compensation Workbench. you should link this activity type to only one standard rate for any plan of that plan type. Required? Maximum Defined Per Plan Assign on Enrollment Recommendation Enter Value at Enrollment Recommendation Override Recommendation Unit of Measure Recommendation Attach elements? Never required No maximum Unchecked Unchecked Unchecked Blank No 22–28 Oracle SSHR 4. The element will appear in the compensation history table corresponding to that plan type in Compensation Workbench. If you administer multiple plans of the same plan type (bonus. if your enterprise offers a signing bonus to executives.

Approved: The user’s manager has approved the worksheet. Compensation Workbench 22–29 . Budget/Worksheet Access Read Only: The manager cannot perform any allocations or distributions. Worksheet Status Not Started: The manager has not started to allocate Budgeted amounts to employees. In Progress: The manager has started to allocate the Budget but has elected Save and has not yet submitted the worksheet for approval. Updateable: The manager can update the budget or worksheet to perform distributions or allocations. but has not submitted the worksheet for approval. Award amounts are final.Compensation Workbench Statuses Budget Status Not Started: The manager has not started to allocate the Distribution Budget to the reporting managers. Issued: The manager has issued a budget to at least one reporting manager. In Progress: The manager has started to allocate the Distribution Budget but has elected Save and has not yet started to issue budgets (making the budgets available). and––where applicable––sent to payroll. Processed: The Compensation Workbench Post Process has run. Complete: A high level manager has completed his or her own worksheet. Pending Approval: The manager has submitted the worksheet for approval. Not Available: The user cannot view the Budget or Worksheet.

Administrators can run the Report from the Submit Request window at any time. or after running the Compensation Workbench Post Process. and a table describing the different rates with the total amount and total issued amount. or 1 to 5 levels down in the organization hierarchy. direct reports. including grant price. Total Compensation Progress Report The Total Compensation Progress Report checks the progress of the compensation cycle for a specific availability period and plan. The compensation cycle for the salary plan may be June 1 to August 1. the progress report summarizes the number of employees who may or may not be 22–30 Oracle SSHR 4. This is the time when the manager can do salary reviews for their eligible employees. After running the Participation Process batch job. For example. the number of employees who may or may not be electable. you can select any manager within your hierarchy. beginning salary. For example. such as after running the Participation Process: Compensation. eligible salary. The administrator can run the report at any time to produce different results based on the timing in the compensation cycle. • After running the Post process batch job. during the allocation period. such as all employees.2 Implementation Guide . the number of employees who may or may not be eligible. your salary review period is September 1. and value Salary Detail: Employee information such as name. the progress report includes the number of employees whose status is started and processed. This produces a report for the defined manager and that manager’s direct reports. This reports all monetary amounts stored in the system as of the date you run the report. Access to the reports is always available. and one level down. bonuses.Reporting in Compensation Workbench Compensation Workbench delivers the following online reports for use by line managers: • • • • Bonus Detail: Employee information for bonus plan distribution Stock Detail: Employee stock allocation information. number of shares. and stock option grants for each employee for a selected year Managers run the reports from the Self–Service interface for various levels in the organization hierarchy. and new salary Total Compensation: Salary increases.

This does not include Salary plans. • Payroll summary includes a table with all the elements and the total amount for each element attached to the specified plan for bonus and stock plans. and a table for each group of employees containing all the rates with the total amounts. Managing Total Compensation Using Oracle HRMS Compensation Workbench 22–31 .suspended. See: Running the Total Compensation Progress Report.

Optional: define compensation components (options) and link the components to the plan. 13. 8. Follow this process to set up plans for Compensation Workbench. Plan Years You use the Program/Plan Years window to set up plan years that define the year––or period within a year––during which an employee 22–32 Oracle SSHR 4.2 Implementation Guide . Optional: define a reporting group to include multiple Compensation Workbench plans. 12. Optional: define elements if you want to transfer activity rates to Oracle Payroll or to third party applications. Define plan years for the Compensation Workbench plan. Define the Compensation Workbench plan. 4. 3. Define a plan type. Link the elements.Setting Up Compensation Workbench Plans You set up Compensation Workbench plans using the Total Compensation data model. 11. Refer to the cross–references for further details. see: Compensation Workbench Processing: page 22–48 " To set up a compensation workbench plan: 1. 10. Define plan enrollment requirements. Optional: define participant eligibility profiles to limit the employees who are eligible for a Compensation Workbench plan. 6. 2. For information about administering Compensation Workbench plans that you have defined. 7. The windows you use to define a Compensation Workbench plan are a subset of those windows that you use to implement and administer Standard and Advanced Benefits. 9. Optional: define variable rate profiles if an activity rate can vary according to one or more factors. selecting a compensation category. Define standard activity rates. Optional: define GL Daily Rates if you enable managers to view amounts in the budget or the worksheet in a currency that differs from the plan’s currency. Optional: define a derived compensation factor if compensation awards are based on a stored or system calculated value. Define one life event reason for each plan. 5. such as eligible or stated salary.

• Enter a life event reason Name that corresponds to your plan. On the Submit Requests window. Note: The application requires year periods for life event processing. Note: To avoid life event collisions. For compensation types that you award more than once per year (such as bonus plans)––or for which the employee earning period is less than a full year––enter a Within Year Period. You can use this amount. you select Participation Process: Compensation to assign the life event to a person. set up one life event reason per Compensation Workbench plan. Managing Total Compensation Using Oracle HRMS Compensation Life Event You set up a life event reason for your Compensation Workbench plan so that when you process participant eligibility and electability. See: Defining a Program or Plan Year Period. Note: Standard Benefit users may only create life event reasons with the Types of Compensation or Absence. the batch process assigns the compensation life event to employees and schedules the availability period for budget and worksheet entry in Compensation Workbench. for example. A naming convention helps you to identify the life event in other application windows. Provide a life event name that identifies the compensation type. Managing Total Compensation Using Oracle HRMS Compensation Workbench 22–33 .earned their compensation. Select the Unit of Measure that best represents your period. if. • See: Defining General Characteristics of Life Events. Compensation Workbench life events require no additional set up. This is the year in which the employee earned the compensation. Do not define person changes for Compensation Workbench life events. select Semi–Year for compensation plans administered twice yearly. The life event occurred on date is the Assigned Life Event that you define for the plan in the Plan Enrollment Requirements window. and––if you operate globally––the legislation of the plan. you award a bonus based on a percentage of compensation earned during the period. • • Enter the plan year start and end dates. For example. Select a life event reason Type of Compensation.

• • Select Compensation Workbench as the Option Type.Derived Factors Compensation awards are typically based on a derived compensation factor. benefits balances. the application finds all employees and ex–employees eligible for your plan. Managing Total Compensation Using Oracle HRMS Compensation Plan Types Your plan requires a compensation plan type. See: Defining an Eligibility Profile. prorated balances. If you do not define an eligibility profile. See: Defining Plan Types. Note: Use the derived factor to convert various pay bases to one pay basis for all employees. • In the Applies To field.2 Implementation Guide . Derived compensation factors can use stated salary. or a FastFormula rule that you define. historical balances. defined balances. Managing Total Compensation Using Oracle HRMS 22–34 Oracle SSHR 4. Select one of the following Compensation Categories: • • • • Comp – Bonus Comp – Stock Options Comp – Other (for promotion and performance plans) Comp – Salary Comp – Salary identifies compensation plans that alter the amount displayed on the Salary Administration window for a person after you process a compensation distribution. See: Derived Factors. You can also use a derived factor as a component in a distribution calculation based on a percentage of the derived amount. select Benefits Profile for Compensation Workbench plans. salary as of a defined date. such as eligible salary or stated salary. Managing Total Compensation Using Oracle HRMS Eligibility You can define participant eligibility profiles to limit the employees who are eligible for a Compensation Workbench plan. You link the derived factor to the standard rate or variable rate to determine the amount that is used in Compensation Workbench for display purposes to help a manager make a more informed decision about an award.

Typical compensation plans include salary increases linked to a yearly focal review period. You should attach two or more components to an itemized compensation plan. You can also define plans for promotions/job changes and performance ratings. Managing Total Compensation Using Oracle HRMS Plan Enrollment Requirements Set up plan enrollment requirements to determine the availability period of Compensation Workbench in Self–Service for a plan. you can define components to represent each item (Cost of Living or Merit. Managing Total Compensation Using Oracle HRMS Compensation Components If you itemize your compensation plan. You also use plan enrollment requirements to enter items such as the: • • • • • • • Assigned life event date Plan year or within year period for the compensation plan Close enrollment date Enrollment coverage and activity rate start and end dates Budget and worksheet characteristics and availability periods Supervisor or position hierarchy to use for budgets Dates on which performance ratings or job changes become effective See: Defining Enrollment Requirements for Compensation Workbench Plans. Run the Compensation Workbench Post Process to update salary component values for an employee who received an award or compensation increase.Compensation Workbench Plans You define a compensation workbench plan for each unique compensation offering or promotions or performance plan that you administer within Oracle HRMS for a business group. You can link a salary increase component to a salary administration component. and stock option grants. For each option. scheduled bonuses. Managing Total Compensation Using Oracle HRMS Compensation Workbench 22–35 . for example). You define components as Total Compensation options. See: Defining Options. select a plan type you defined with an Option Type of Compensation Workbench. See: Defining a Compensation Workbench Plan.

See: Defining a Reporting Group. This enables a line manager to use a single signon to review and allocate compensation for employees in different business groups. select an element type of Information See: Defining an Element. Managing Total Compensation Using Oracle HRMS Element Links You set up element links for Compensation Workbench plans as you would for Standard and Advanced Benefits. See: Defining an Element Link. for bonuses A Processing Type of Non–Recurring An Input Value of Pay Value in Units of Money For Stock Option plans with a unit of measure of Shares.2 Implementation Guide . a typical element setup includes: • • • • A Primary Classification of Supplemental Earnings. Defining a reporting group places a plan switcher on your Self–Service web pages that allows you to switch between available compensation plans.Reporting Groups For Compensation Workbench. Managing Compensation and Benefits Using Oracle HRMS 22–36 Oracle SSHR 4. For compensation workbench. You must have eligible employees below you in the hierarchy to see more than one plan. you can use that element without defining a new one. The name of the reporting group appears on the Home Page in Compensation Workbench. If you have previously defined an element that you now want to use for a Compensation Workbench plan. Managing Total Compensation Using Oracle HRMS Elements Use elements to transfer activity rates to Oracle Payroll or to third party applications. The application automatically updates the employee’s salary basis on the Salary Administration window. you can create a reporting group as a container to hold multiple plans. Note: You do not need to define elements for salary plans. Create a global reporting group to include plans from more than one business group. only for bonus and stock option plans. Elements record items such as the compensation that a line manager distributes to an employee.

you must set up activity rates for the option in plan rather than for the plan. Managing Total Compensation Using Oracle HRMS Standard Rates You set up standard activity rates to record a variety of compensation amounts.Variable Rate Profiles Variable rate profiles are optional for Compensation Workbench plans. See: Defining General Information for a Variable Rate Profile. If you have multiple components. such as: • • • • Distribution budgets Worksheet budgets Budget reserves Eligible or Stated Salary Each standard rate uses an activity type to control many of the columns that display in Compensation Workbench. A line manager can override the recommended amount within the guidelines of a minimum and maximum compensation range that you define. Variable rate profiles are also useful if you auto–issue a fixed budget to all managers and you want to vary the issued amount based on a manager’s demographics. See: Defining Activity Rates for a Standard Contribution/Distribution. You can use a variable rate profile. you must budget for at least one component. for example. If you budget or allocate for a component. or. and you check the Uses Budget check box on the Plan Enrollment Requirements window. Managing Total Compensation Using Oracle HRMS GL Daily Rates Setting up GL Daily Rates enables your managers to use Compensation Workbench to enter and view budget and worksheet distributions in a currency that differs from the currency set for the profile option BEN: Benefits Preferred Currency. for the currency defined for the business group. Compensation Workbench 22–37 . You set up different activity rates––with different activity types––depending on the kinds of values you want to record in Compensation Workbench. if you do not set this profile option. if you provide an initial recommended amount for a compensation distribution. You could vary this amount based on a manager’s demographics. Managing Total Compensation Using Oracle HRMS See: Compensation Workbench Activity Types.

Note: Conversions are for display purposes only and do not affect actual paid amounts.2 Implementation Guide . • You must use a GL Daily Rate Conversion Type of Corporate for each currency you want to use with Compensation Workbench.Line managers can select their preferred currency––you should only enable those currencies for which you have conversion rates. Oracle General Ledger Users’ Guide 22–38 Oracle SSHR 4. See: Entering Daily Rates.

the worksheet. 2. and Select Compensation Workbench. Note: The left side displays all Available Columns you can choose to display in the worksheet group for the selected plan. select the plan. In the Find field. and then the worksheet group you want to personalize. Change the No to Yes for either Site– or Responsibility–level. For instance. Navigate to Profile > System. . you can configure worksheet groups so managers can: • • • • • view compensation history view job information view previous employee performance ratings perform employee evaluations award allocations You can use personalization to move columns into a more meaningful arrangement. 4. located at the bottom of the Worksheet Group page. You can use personalization to have multiple and different views of the same information available in the worksheet groups. Select the link. You enable self–service personalization through the Professional User Interface using the System Administrator responsibility. choose to display or not display items. 3. and rename columns to match your business terminology. In the Define System Values Profile window. Search for the Personalize Self Service Defn Profile. 1. select either the Site or the Responsibility check box to enable personalization at the appropriate level. On the Home page. 7. 6. Personalize This Region for Benefits Plan Design. Note: The following steps are performed in the Self–Service Interface. as appropriate. 5.Personalizing a Plan for Compensation Workbench Plan–level personalization allows the professional user to configure the worksheet groups and the information that managers are able to view and update. Log into the Manager Self–Service responsibility. Attention: The system Administrator will need to “bounce” the Apache server before personalization is enabled in Self–Service.

Compensation Workbench 22–39 .

8.2 Implementation Guide . choose the Rename button.the right side lists the Columns Displayed in the worksheet group for the selected plan. Select items you want to add or remove by highlighting them in either column and using the appropriate left or right arrow on the slider. To change the name of a column. Additionally. 9. You can select the Apply button to save your changes to the worksheet group. 10. you can reorder the sequence of columns displayed by using the up and down arrows on the slider. Select the item you want to rename and change the name. or you can select the Delete button to cancel your changes. 11. Note: You can select the Delete Customization button to return to the original design of the worksheet group after changes have been applied. Save your work. 22–40 Oracle SSHR 4.

10. 4. 1. Select the Plan Type you created for this plan. 7. Note: If you select Hourly as the Activity Reference Period. Note: You can also use the Plans window to define employee benefits plans.Defining a Compensation Workbench Plan Use the Plans window to define a compensation workbench plan. 3. Change the status to inactive to make the plan unavailable in Compensation Workbench. Choose the Details button to open the Maintain Plan Related Details window. This defaults to 2080. select May not be in Program. 2. you can reuse the plan over multiple award periods. and the amount in which salary increases are entered. Leave the Enrollment Rate/Frequency field blank. 11. Enter the Sequence number of this plan if you want compensation plans to display in a particular order in Self–Service. Compensation plans use only a subset of the features available on the Plans window. 9. Compensation Workbench 22–41 . This determines the period for which the base salary is displayed. Choose the Eligibility Rates tab. Choose the Not in Program tab. 6. 5. Note: By using a generic plan name (one that does not include a particular year period). meaning that there are assumed to be 2080 hours in a year (8 hours * 5 days * 52 weeks). Check the Track Ineligible Person field to enable eligibility overrides without having to rerun the Participation Process: Compensation to determine eligibility or rates. Select an Activity Reference Period that matches your most common pay basis. Enter the plan Name. Select the Currency of your plan. Select a Status of Active. In the Plan Usage field. You must create a separate plan for each plan with a unique currency. 12. 8. ensure you have defined a value for the BEN:BEN HOURLY ANNUALIZATION FACTOR user profile option.

Attach the plan years you defined to the plan. Select a Status of Active. 26. 30. Choose the Eligibility button. 27. Attach any applicable participant eligibility profiles that you created. Close the Maintain Plan Related Details window. 15. 14. Note: If you do not attach any worksheet groups. 17. Enter the sequence number of the first component. Self–Service defaults to show the Compensation Worksheet Group. Existing Compensation Plans do not require modification.2 Implementation Guide . 31. 23. Give your worksheet group a unique name –– this name will appear on the tab in the Self–Service interface. Close both the Eligibility window and the Maintain Plan Eligibility window. 21. Choose the Plan Periods tab. Select the component in the Option field. Check the Track Ineligible Person field to enable eligibility overrides without having to rerun the Participation Process: Compensation.13. 16. 22–42 Oracle SSHR 4. Choose the Plan Eligibility button if you want to link a participant eligibility profile to the plan. 28. 24. 22. You can attach any combination of the same or different worksheet groups. Attach any applicable participant eligibility profiles that you created. 29. Check the Hidden check box if you want to hide this component from a manager’s budget and worksheet. 18. Choose the Eligibility tab. and enter a sequence number for the first worksheet group you are adding. 19. Choose the Compensation Workbench tab. Repeat steps 23 to 29 for each component in the plan. Choose the Options button if you itemize this compensation plan. 20. Save your work. 25.

Select Explicit as the enrollment Method. Required: select 1 Prior or Event as the Enrollment Coverage End Date. 2. select Elections as the Enrollment Coverage Start Date. 1. Compensation Workbench 22–43 . This starts the employee’s coverage as of the effective date of the Compensation Workbench Post Process. In most instances. Choose the Timing tab and then the Scheduled tab. 3. 9. Query the plan for which you are defining enrollment requirements in the Plan field. You can only select this Enrollment Type if the option type of the plan type you attached to this plan is Compensation Workbench. Select Current. Required: select 1 Prior or Event as the Rate End Date. Can Choose as the Enrollment Code. Note: By setting coverage and activity rate start and end dates at the plan level you will not have to update these codes for each availability period. Note: You can also use the Plan Enrollment Requirements window to define electability requirements for employee benefits plans. Compensation Workbench plans use only a subset of the features available on this window. 5. 11. This ends the employee’s coverage one day prior to the start of any subsequent coverage. 12. Select Compensation as the Enrollment Type. 10. select Elections as the Rate Start Date. choose the Enrollment tabbed region. 8. 6. Can Keep or Choose. This starts the employee’s rate––and element entry––as of the effective date of the Compensation Workbench Post Process. With the General tab and the Plan tab selected. 4. New. Choose the Rates tabbed region. In most instances. 7.Defining Enrollment Requirements for Compensation Workbench Plans Use the Plan Enrollment Requirements window to define the scheduled availability period for a Compensation Workbench plan and to establish certain budget and worksheet properties. Choose the Coverage tabbed region.

17. In the No further processing is allowed after field.2 Implementation Guide . Enter the effective date of the compensation life event in the Assigned Life Event Date field. 14. enter the date range for which Compensation Workbench is available in Self–Service for this plan. Select a Within Year Period if this plan uses a period of less than a year to determine available compensation. Note: You can only have one life event per plan. and each employee’s worksheet manager. Availability periods for the same plan cannot overlap. Select the Year Period of this plan. you cannot change the availability period unless you back out the life event. For promotion and performance plans.13. 15. Attention: Once you run the Participation Process: Compensation. 19. Select a previously defined compensation life event reason for this plan in the Life Event field. In the Enrollment or Availability Period Start and End fields. enter the last date on which you can make changes in the professional user interface to this compensation plan. Enter a Close Enrollment Date to use code that determines the date when the life event status is changed from started to processed: • • Processing End Date (Closed by the Close Compensation Enrollments Process on the No further processing date) When Elections Are Made (Recommended––Closed by the Compensation Workbench Post Process on the effective date of the process) When Enrollment Period Ends (Closed by the Close Compensation Enrollments Process as of the Availability Period end date) • 18. 22–44 Oracle SSHR 4. 16. Subsequent runs of the process must be after the previous life event has been closed for all individuals and the previous availability period has ended. activity rates. you must leave the budget tabbed region blank. Budget Characteristics Note: Because Budgets are not used for Promotion and Performance Plans. skip to step 25. The assigned life event date sets the date on which the Compensation Participation Process evaluates your plan design to determine eligibility.

Using Self–Service. a higher level manager can set the default worksheet access for lower level managers within their hierarchy. You can change the date range for the budget at any time without having to re–run Participation Process: Compensation for the change to take effect. 22. Choose the Miscellaneous tabbed region. Select the Uses Budget check box to enable higher level managers to issue budgets to lower level managers. Select the Default Worksheet Access for all managers: • • • Not Available Read Only Updateable You can override the default worksheet access for a manager using the Person Life Events window. Optionally. You must check this field to enable the use of budgets at any level in the application. 27.20. Hierarchy and Performance Ratings 28. the application automatically recalculates a manager’s distribution budget and worksheet budget if an employee becomes eligible or ineligible or is reassigned from one manager’s worksheet to another’s. Worksheet Characteristics 25. 23. Compensation Workbench 22–45 . Enter the date range for which a manager can access and update the Budget in the Self Service Budget Update Period block. Select whether to store budgets as percents or amounts in the Preserve Budget Column field. You can change the date range for the worksheet at any time without having to re–run Participation Process: Compensation for the change to take effect. If you select percent (recommended). Choose the Budget tabbed region. select the Automatically Allocate Defined Budgets check box to update the allocation worksheet for all managers with a predefined budget amount after you run the Compensation Pre–Process. Choose the Worksheet tabbed region. 26. Enter the date range for which a manager can access and update the Worksheet in the Self Service Worksheet Update Period block. 21. 24.

This supervisor can be in a different business group. enter the date in the New Ratings Become Effective field. 31. select the Performance Rating Type to use for this plan. If you use position hierarchies––and you want an employee to report to a supervisor in a different business group for budget purposes––create a placeholder position above that employee in the hierarchy and do not assign a person to the position.2 Implementation Guide . Select whether you administer Compensation Workbench plans based on a manager’s supervisor hierarchy or a position hierarchy. enter the date in the Assignment Changes Become Effective field. 30. 32. Note: For Promotion Plans. 22–46 Oracle SSHR 4. Save your work. and you want to display those rating in Compensation Workbench. The application checks for a manager’s supervisor if it cannot find a position in the hierarchy above the manager’s current level. If you maintain employee performance ratings in Oracle HRMS. Select a position hierarchy if you administer this plan based on positions. Note: For Performance Plans. You can only display one performance rating type at a time for a compensation plan in Compensation Workbench.29.

3. Select the first Program Name if the reporting group is to consist of one or more programs. 6. indicating that you can define regulatory bodies for. 2. select the first Plan Name in the reporting group. 5. you could do so by choosing a Program Name for one record. Compensation Workbench 22–47 . Any row (record) in this table can include a Program Name or a Plan Name. You can also define which regulatory bodies and regulations govern the reporting group. Note: Create a global reporting group if you implement a Compensation Workbench plan and you enable a manager to review or allocate compensation for employees in different business groups. Save your work. Select a purpose of Compensation Plan Groupings for Compensation Workbench. Select the Global check box to include plans in the reporting group from any business group. Enter a unique Name for the reporting group.Defining a Reporting Group You use the Reporting Groups window to define a reporting group and to associate programs and plans with the reporting group. that plan. Enter a Description of the reporting group. While it is unlikely that you would want to use the same reporting group to report at the program and plan levels. but not both simultaneously. Select the Purpose of the reports that will be generated for this reporting group. and then choosing a Plan Name for each subsequent record in the reporting group. " To define a reporting group: 1. 4. Alternatively. Note: When a plan is selected. the Regulatory Bodies and Regulations button is enabled. and associate regulations with.

If necessary. The process assigns the compensation life event to a person and determines eligibility and rates. See: Issuing the Budget to the Highest Level Manager: page 22–53 3. for salary plans. For information about implementing Compensation Workbench plans. If you auto–issue budgets. The process displays its results on the Person Life Events window. The highest level manager can then use Compensation Workbench to issue budgets to lower level managers. use the Enrollment Override window to override an amount for a person after you run the Compensation Workbench Post Process. 4. issue the highest level budget. Note: Values you enter in this window update element entries for bonus and stock option plans. Run this process prior to the availability period of Compensation Workbench to prepare the Self–Service interface for data entry by your line managers. See: Running the Compensation Workbench Post Process: page 22–56 5. However.Compensation Workbench Processing Use the following process to administer your Compensation Workbench plans after you define them in Oracle HRMS using the Total Compensation data model. perform enrollment overrides. 22–48 Oracle SSHR 4. the process updates the allocation worksheet for all managers with a predefined budget amount that cannot be updated. Run the Participation Process: Compensation. Run this process after all worksheet allocations have been approved to write the distribution totals to enrollment results. See: Running the Participation Process: Compensation: page 22–50 2. Run the Compensation Workbench Post Process. see: Setting Up a Compensation Workbench Plan 1. You issue a budget to the highest level manager in your organization hierarchy using the Person Life Events window in the professional user interface. Optionally. If you do not auto–issue budgets.2 Implementation Guide . Line managers use Compensation Workbench to enter compensation awards.

you run the Post Process for salary and stock option plans. You do not need to run the Close process if you set up the Compensation Workbench Post Process to close the compensation life event. See: Overriding Enrollment Results for a Plan. you run this process for a bonus plan if you set the Close Enrollment Date code to Processing End Date. Run the Close Compensation Enrollments Process. Managing Total Compensation Using Oracle HRMS 6. This process closes the compensation life event for one or more persons as selected by the batch process parameters. future–dated enrollments always require you to run the Close Compensation Enrollments Process.overrides you enter on this window do not update the Salary Administration window. Typically. However.’ Typically. You can run the Compensation Workbench Post Process to close the compensation life event if you set up the processing end date as ’When elections are made. See: Running the Close Compensation Enrollments Process: page 22–59 Compensation Workbench 22–49 .

5. You run Processes from the Submit Requests window. To further limit the persons evaluated by the process. Select Participation Process: Compensation in the Name field. and assigns the compensation life event to each eligible person. " To run the Participation Process: Compensation: 1. you use the Person Life Events window to enter a budget for the highest level manager in your enterprise responsible for distributing budgets in Compensation Workbench. 4. 6. 2. select from one or more of the following parameters. Select the compensation plan in the Plan Name field. If you do not auto–issue budgets. • • • • • • Organization Benefits Group Location Postal Zip Range Legal Entity Payroll 22–50 Oracle SSHR 4.Running the Participation Process: Compensation You run the Participation Process: Compensation before the availability period of a compensation plan. 3. If you auto–issue budgets. Select a year Period. Select a Person Type if you want to run the process for a specific person type (such as employee) for this compensation plan. Select Commit or Rollback in the Validate field. Set the effective date of the process to a date on or after the assigned life event date. 9. It is easier to correct errors before you commit results. Select a Person Selection Rule if you want to run the process for persons who match the criteria of your rule. The process determines eligibility. 8. calculates rates. Enter the Parameters field to open the Parameters window.2 Implementation Guide . the process updates the allocation worksheet for all managers with a predefined budget amount. Select Rollback to check your results before committing them to the database. 7.

10. Select Yes in the Audit Log to create a file that lists the eligibility results for each person evaluated by the process. 12. 11. Complete the batch process request and choose Submit. Choose the OK button. If you select Yes. Compensation Workbench 22–51 . you should periodically run the Participation Audit Activity Purge process to purge the audit log tables.

See: Moving an Employee to Another Manager’s Worksheet: page 22–54 Note: You can use the Person Life Events window to back out a life event for a single person. The Population field displays the level at which the high level manager issues budgets. If you auto–issue budgets. it is recommended that you use the Back–out Life Events Process to back out the entire life event. a compensation manager uses the Person Life Events window to issue a budget to a high level manager or managers in the organization responsible for issuing budgets.2 Implementation Guide .Using the Person Life Events Window for Compensation Workbench After you set up your Compensation Workbench plan. You can also enter the Due date by which you want a manager to complete the budget or worksheet. and does not affect budget or worksheet processing. Note: Do not use this window to close a person’s compensation life event. the pre–process updates the allocation worksheet for all managers with a predefined budget amount If you do not auto–issue budgets. High level managers in a hierarchy use Compensation Workbench to issue budgets to lower level managers. you run Participation Process: Compensation on the Submit Requests window to determine a person’s eligibility and the availability period of a Compensation Workbench plan. The move is effective only for the selected plan and period. • Direct Reports: The high level manager issues a budget to his or her direct reports. you can also use the Person Life Events window to override any employee’s eligibility or their award amount. See: Issuing a Budget to a High Level Manager: page 22–53 As a compensation manager. or to change a budget amount issued to a manager in Compensation Workbench. This is considered information only. However. See: Updating an Employee’s Eligibility: page 22–54 See: Updating an Employee’s Budget or Worksheet Amount: page 22–55 You can move an employee from one manager’s worksheet to another manager’s worksheet. Use the Close Compensation Enrollments Process. The manager selects this value in Compensation Workbench. 22–52 Oracle SSHR 4.

Select the CWB Distribution Budget rate in the Rate Name field. 8. Select a budget or worksheet Access level for this manager. 7. 6. 2. Compensation Workbench 22–53 . Note: If the Issued Amount field appears disabled. Issuing a Budget to a High Level Manager " To issue a budget to a high level manager: 1. Select the started compensation life event that corresponds to your compensation plan. Choose the Rates button to open the Rates window. 10. Query the Name of the high level manager to whom you are issuing the budget. For example. 3. Enter the budget amount you are issuing to the high level manager in the Amount and Issued Amount fields. Choose the Amount tabbed region. • • • Read Only Updateable Not Available Select Updateable when issuing a budget to your highest level manager. Choose the Enrollment Opportunities button to open the Enrollment Opportunities window. 4. The high level manager can now log in to Compensation Workbench to begin issuing budgets to lower level budgeting managers. Choose the Electable Choices button to open the Electable Choices window. 5. Choose the Compensation tabbed region. enter 10 for ten percent. Enter a percent (without the percent symbol) if you are budgeting based on a percentage of eligible salaries. 9.• All Managers: The high level manager issues a budget to each direct report and to all the budgeting managers beneath the direct reports. Select the compensation plan in the Program or Plan field. make sure that the standard rate allows overrides. 11.

2. Note: If you change an employee’s supervisor on the Assignment window after you run the Participation Process: Compensation. " To move an employee to another manager’s worksheet: 1. Note: If the worksheet manager field is blank. Choose the Electable Choices button to open the Electable Choices window. querying the employee whose eligibility you want to change. Select the new manager in the Worksheet Manager field. 5. 4. the application routes a worksheet submitted for approval to each person with a Role Type of Compensation Administrator. If applicable. Choose the Enrollment Opportunities button to open the Enrollment Opportunities window. 22–54 Oracle SSHR 4. Query the Name of the employee whose worksheet manager you want to change. Select the started compensation life event that corresponds to your compensation plan.Updating an Employee’s Eligibility " To update an employee’s eligibility: 1. the process restores the person to the original manager’s worksheet. You can override a employee’s eligibility for this plan in the Eligibility field. Moving an Employee to Another Manager’s Workbench Moving a person from one manager’s worksheet to another manager’s worksheet does not affect your actual organization hierarchy. 3.2 Implementation Guide . If you rerun the Participation Process: Compensation. select the Ineligibility Reason for this person. 2. Choose the Compensation tab. The move only affects the selected plan for the current year period or within year period. • The application displays the override date and the person who committed the override in the Overridden On and Overridden By fields. you must update the employee’s worksheet manager if you want the employee to appear on the new manager’s worksheet. 3. 4. Repeat steps 1 to 5 above.

3. Select the compensation life event that corresponds to your compensation plan. 7. worksheet. or grant price. 5. 8. Line managers can view and update these comments. In the Rate Name field. Choose the Enrollment Opportunities button to open the Enrollment Opportunities window. For a worksheet. Enter a value in the Amount field. Updating Amounts for an Employee You can use the Person Life Events window to update any Compensation Workbench amount for an employee––such as budget. eligible salary. Save your work. 2. 9. Managing Your Workforce Using Oracle HRMS 5. 6. 4. Choose the Rates button to open the Rates window. budget reserve. Choose the Amount tabbed region. Choose the Electable Choices button to open the Electable Choices window. Query the Name of the employee for whom you are issuing a budget or worksheet amount. Compensation Workbench 22–55 .See: Defining Workflow Roles for Transactions. select the rate for which you are entering an amount. enter any Comments you want to display about an employee in Compensation Workbench. Enter a percent (without the percent symbol) if you are basing the rate on a percentage of eligible salaries. " To update amounts for an employee: 1.

10. you should periodically run the Participation Audit Activity Purge process to purge the audit log tables. 4. 2. Enter the effective date of the process. Select Yes in the Audit Log to create a file that lists the results for each person evaluated by the process. You run processes from the Submit Requests window. Select the name of a specific person in the Person Name field if you want to run the process for one person. 11.Running the Compensation Workbench Post Process You run the Compensation Workbench Post Process after line managers have approved all budget and worksheet entries. Select the compensation plan in the Plan Name field. 9. Select Rollback to check your results before committing them to the database. Select Commit or Rollback in the Validate field. Note: You must define a standard activity rate with an activity type of CWB Grant Price to record a grant price prior to running the Participation Process: Compensation. Select Compensation Workbench Post Process in the Name field. Complete the batch process request and choose Submit. The process writes the allocated amounts to an employee’s salary and element entry––for salary changes––or to element entries for other activity rates (such as bonuses) if you attach an element to the applicable rate when you define the rate. Note: The effective date is the date of the election if you set the Rate Start Date code to Elections. 7. Select an Enrollment Period. It is easier to correct errors before you commit results.2 Implementation Guide . 22–56 Oracle SSHR 4. 5. Enter a Grant Price if this is a Stock Option plan and you want to record the grant price for each person who received a grant. " To run the Compensation Workbench Post Process: 1. 8. Choose the OK button. If you select Yes. 3. For example. Enter the Parameters field to open the Parameters window. 6. set the effective date to September 1st if a bonus or salary increase is effective as of that date.

• • • • Organization Location Person Benefit Group Legal Entity Compensation Workbench 22–57 . select one or more of the following parameters. " To run the Compensation Workbench Back–out Life Events Process: 1. You run processes from the Submit Requests window. Enter the effective date of the process. Select Compensation Workbench Back–out Life Events Process in the Name field. Typically. To further limit the persons evaluated by the process. or an award distributed to the person by another manager. Enter the Parameters field to open the Parameters window. this is the same as the To Occurred Date in step 6. you run this process before you run the Compensation Workbench Post Process if you need to back out a compensation life event. Note: Use caution if you run this process. Typically. you can run the process any time before a payroll run has processed your results. 4. 7. use the Enrollment Override window to override an activity rate result for a person. or use the Person Life Events window to override eligibility or to change worksheet managers. However. As an alternative to backing–out the compensation life event. Enter the date range for which you want to back out results in the From Occurred Date and To Occurred Date fields. Persons selected by the process lose all rates assigned during the selected period––including amounts they entered on a budget or worksheet. Select the compensation Life Event to back out. Select Commit or Rollback in the Validate field. 6.Running the Compensation Workbench Back–out Life Events Process You run this process to remove the results of the Participation Process: Compensation for a compensation life event in the case of errors or changes in plan design. 2. Select Rollback to check your results before committing them to the database. 5. 3.

Choose the OK button. Complete the batch process request and choose Submit. 22–58 Oracle SSHR 4.2 Implementation Guide .• Person Selection Rule 8. Select a Resulting Status of Voided for the backed out life event. 9. 10.

10. 8. Select an Assigned Life Event Date to close a life event that was assigned on a particular date. 2. Select Compensation Workbench Close Enrollment Process in the Name field. If you set the Close Enrollment Date code for a plan to When Elections are Made (such as for a salary or stock option plan). 4. Compensation Workbench 22–59 .Running the Compensation Workbench Close Enrollment Process This process closes the compensation life event for the selected persons when the following conditions exist: • • The availability period for the compensation plan is passed The final processing date for the plan is passed Typically. Enter the effective date of the process. You run processes from the Submit Requests window. 5. 7. 9. 6. you do not need to run this process. Select Rollback to check your results before committing them to the database. Select the compensation plan in the Plan Name field. 3. Select a Person Selection Rule to run the process for persons who match the criteria of your rule. you must periodically run the Participation Audit Activity Purge process to purge the audit log tables. 11. Select Commit or Rollback in the Validate field. Select a Location to close the compensation life event for persons who work in a specific location. Select Yes in the Audit Log to create a file that lists the results for each person evaluated by the process. Run the Compensation Workbench Post Process to close the life event. you run this process for a bonus plan if you set the Close Enrollment Date code to Processing End Date. " To run the Compensation Workbench Close Enrollment Process: 1. Select the name of a specific person in the Person Name field to run the process for one person. Select the compensation Life Event to close. Enter the Parameters field to open the Parameters window. If you select Yes.

13.12. 22–60 Oracle SSHR 4.2 Implementation Guide . Choose the OK button. • • Force Close always closes the life event. Complete the batch process request and choose Submit. Select a Close Mode. 14. Normal Close closes the life event based on the close enrollment date.

After running the Compensation Workbench Post Process batch job. and a table describing the different rates with the total amount and total issued amount. 5. Select the Availability Period. ensure the date is within the element entry start and end dates. the progress report summarizes the number of employees who are or are not suspended. the progress report includes the number of employees whose status is started and processed.Running the Compensation Workbench Progress Report The Compensation Workbench Progress Report checks the progress of the compensation cycle for a specific availability period and plan. Select Compensation Workbench Progress Report in the Name field. Choose OK and choose Submit. 4. 6. Payroll summary includes a table with all the elements and the total amount for each element attached to the specified plan for bonus and stock plans. Enter the Effective Date for the process run. These are filtered by the previously selected plan. You run processes from the Submit Requests window. In order to see element entry values on the report. the number of employees who are or are not electable. Select the Plan Name you wish to review. The report produces different results based on the timing in the compensation cycle. and a table for each group of employees containing all the rates with the total amounts. Salary plans are not reflected here. " To run the Compensation Workbench Progress Report: 1. Enter the Parameters field to open the Parameters window. the number of eligible and ineligible employees. You can run the report at any time: • • • After running the Participation Process: Compensation During the allocation period After running the Compensation Workbench Post Process. 22–62 Oracle SSHR 4. This is the compensation cycle for a particular time period. 2.2 Implementation Guide . After running the Participation Process: Compensation batch job. 3.

enter the eligibility start and end dates. enter the Reporting Start Date and the Reporting End Date to limit the eligibility and enrollment list to this period. Note: You must select either the Plan Type or the Plan. Or. Select Eligibility and Enrollment List in the Name field. enter coverage start and end dates for enrollment results. Recently ineligible persons are those people found ineligible in a compensation object for which they were previously eligible. To view eligibility results.Running the Eligibility and Enrollment List Report Run the Eligibility and Enrollment List to display the total number of eligible and enrolled participants in plans used for Standard and Advanced Benefits. This report enables you to: • • • • • Reconcile total participant counts with third–party providers Determine the effectiveness of a plan by comparing the number of eligible people to the actual number of enrolled participants Monitor trends in changes to the volume of currently enrolled participants Analyze the impact of potential changes to plan offerings on participants Generate a mailing list of currently enrolled participants You run reports from the Submit Requests window. and Compensation Workbench. Plan: limits the report to the selected plan type or the plan. 3. Individual Compensation Distribution. The report also lists recently ineligible and de–enrolled participants. You can also select other criteria to limit the results of the report: • • • Person. Plan Not in Program Option • • • Enrollment Method (select a value of Generated for enrollments processed through data conversion or IVR transaction) Compensation Workbench 22–63 . In the Parameters window. 2. Person Type Program Plan Type. " To run the Eligibility and Enrollment List: 1.

Newly De–enrolled. Display All Enrolled Plans by Participant: lists all plans in which the selected participant is enrolled. Display Enrolled Participants by Plan: lists people enrolled for the selected plan. Display Date of Birth: displays participant date of birth in the Enrolled Plans by Participant Section. Choose the Submit button. 22–64 Oracle SSHR 4. • Display Eligibility and Enrollment Summary: lists people who are Eligible. Indicate if you want to view report results such as: Note: The default value for the following is Yes: 4. In the Submit Request window. Display Email Address: displays participant email addresses in the Enrolled Plans by Participant Section. and Newly Ineligible. 6. Enrolled by each Enrollment Method Type. • • • • • • 5. Display Mailing Address: displays participant address details in the Enrolled Plans by Participant Section.2 Implementation Guide . verify the parameters you selected. Display Gender: displays participant gender in the Enrolled Plans by Participant Section.• • • • • • • • Person Selection Rule Organization Location Benefits Group Reporting Group Payroll Person Identifier: the report displays the selected identifier. Currently Enrolled. Choose OK. 7. Sort Order 1 to Sort Order 3: sorts the report based on your selection. set the schedule and the options for running the report.

APPENDIX A Implementation Steps Implementation Steps A–1 .

and Suitability Matching have not yet been migrated to the new technology framework for SSHR version 4. Set up the Apache server as specified in the Oracle Self–Service Web Applications Implementation Manual (available on Metalink). set the following profile option to ”Yes” at the site level. please see Implementing Self–Service Human Resources (SSHR) 3. Apply the patch for SSHR 4. 6.2) which is available on Metalink.x and make sure that all prerequisites are met. please contact Oracle for information on purchasing a licence. Create an SSHR Background Workflow Cleanup Process 7. A–2 Oracle SSHR 4.08 or Microsoft Internet Explorer version 4 or 5. although you must configure this data and functionality for your own implementation of SSHR. To Prepare the Environment for SSHR: 1. See: Configuring and Troubleshooting Oracle HTTP Server with Oracle Applications (available on Metalink – technical note number: 139863. Check that you have the correct Internet browser. Note: If you try to configure functionality before you are familiar with Oracle HRMS and Oracle Workflow. You can use Netscape Navigator 4. Note: It is your responsibility to populate data fields.2 Implementation Guide . HR: Self Service HR Licensed If you have not licensed SSHR.Implementation Steps for Self–Service HR (SSHR) SSHR is supplied with predefined data and functionality. Before you complete any step. If you have licensed SSHR. Complete the install and set–up of the OSSWA Framework. 3. • 2. Candidate Offers. Functions in the areas of Appraisals.4 (11i.0. 4. Ensure that Oracle Human Resources 11i is installed with the most up–to–date patch according to the readme file for SSHR at the time of installation. you may make mistakes. Ensure that the Apache server and Apache JSERV are installed.1) 5. read the referenced topic information. For information on these functions. including those for the OSSWA Framework.

See: Creating a Workflow Cleanup Process: 8.You should remove transaction information from the temporary tables for processes that support Web transactions. See: Updating Workflow Objects: page 6–3 See: Overview of Oracle Workflow Access Protection (Oracle Workflow Guide – available on Metalink) 10. Identify the Target User Groups Before starting your implementation. Install the Workflow Builder on Selected Workstations Members of your Implementation team who will be making changes to workflow process definitions need to have the Workflow Builder installed on their workstations or available from a file server. descriptive flexfields. Set the Access Levels for the Predefined Workflow Item Type The predefined workflow item type is used as the basis for all future upgrades. Configure the HRMS applications Define work structures. Reporting. To do this. and System Administration in Oracle HRMS 11. Provided the access and protection levels are set correctly. 9. include the Remove Transaction activity in the workflow process. key flexfield. it is important to identify any groups of users in your enterprise who may have different requirements. You should have now installed the following tools: • • • • Oracle Workflow Oracle Applications SSHR OSSWA Framework See: Getting Started with SSHR: page 2–2 User Access and Workflow Set Up (SSHR) 12. Most enterprises will differentiate between managers Implementation Steps A–3 . you can work with the delivered item type and your configurations will not be overwritten. See: Configuring. lists of values. Check that you now have the required tools for implementing SSHR.

and other employees. use the Menu window. Create the User Menus User menus group together a number of functions. but we recommend that you create your own user menus using the seeded menus as a basis. managers. Assign a menu to them in the Responsibilities window.2 Implementation Guide . we recommend that you create your own responsibilities based on the seeded responsibilities. See: Person Tree: page 9–3 16. Set Up the System Profiles You set up the security profiles to control access to information. you may identify further distinct groups such as HR professionals. (Oracle Applications System Administrators Guide) See: Defining User Access and Menus: page 5–12 14. You can choose whether to display all these tabs or whether to hide one or more tabs from the user. Configure the Person Search Screens Three tabs are displayed on the Person Search page. and system administrators. To create user menus. Create Self–Service Responsibilities SSHR is supplied with predefined responsibilities. You remove a tab from display in the Menu Exclusions Region of the Responsibilities window. A–4 Oracle SSHR 4. also set the HR: Cross Business Group responsibility. See: User Access and Security: page 5–2 17. Link the Responsibilities to Your Security Profiles Use the System Profile Values window to link the responsibilities you have created to your security profile. 13. SSHR includes predefined menus for employees. Set the HR: Cross Business Group Profile If you want your managers to be able to access data for employees in other business groups. however. or senior managers. See: Menus Window. In your enterprise. managers in a particular department. See: Responsibilities Window (Oracle Applications System Administrator’s Guide) See: Self–Service Responsibilities and User Access: page 1–23 15. 18.

you must first write API user hooks. and profile options you want to associate with a user. Place the logo in the $OA_MEDIA/<Language> directory. Configure Batch Creation of User Accounts To create and manage the batch creation of user accounts. You can replace this logo with your own. See: Writing User Hooks to Create Batch User Accounts: page 5–20 See: Setting Up Batch Creation of User Accounts: page 5–25 Configuring Workflow Processes and Page Layouts (SSHR) 22. also set the Allow Granted Access profile option to Yes for the responsibility.0 functions.See: User Profiles (Oracle Applications User’s Guide) and (Oracle Applications System Administrator’s Guide). you may choose to create all your user accounts manually and skip the next step. Display Your Enterprise Logo SSHR is delivered with a default Oracle logo in the upper left hand corner of the application. The logos are named FNDLWAPP. You use the user account hooks for example. Set the Allow Granted Access Profile If you want managers to be able to access data for employees outside their security profile whose information has been released to them using the Release Employee Information function.2 and later.gif for SSHR version 3. See: Release Employee Information: page 9–13 20. For a small enterprise. responsibilities. See: Displaying a New Logo: page 7–11 23. See: User Profiles (Oracle Applications User’s Guide) and (Oracle Applications System Administrator’s Guide). User hooks enable you to extend the predefined business rules to reflect your enterprise’s business rules. See: Defining User Access and Menus: page 5–12 21. to set up your customary user name and password format. 19. Manually Create User Accounts Create at least one user account manually to test the responsibilities and menus. and FNDLOGHR for SSHR 2. Define your Email Address Implementation Steps A–5 .

repeat steps 15 thru 26. See: Self–Service Workflows: page 6–2 27. Identify and Prioritize Required Business Flows SSHR is delivered with a number of business flows incorporating workflow–enabled functions. Detailed information is available in the relevant chapters as indicated. Configure the Workflow Process Review the underlying workflow process in the Workflow Builder. configure changes in the Workflow Builder. Consider the information flows and approval processes within your enterprise. See: Approvals Processes: page 8–2 28.Set up the email addresses for your enterprise. first copy the process so that you can make changes to the copy. First identify which business flows you need to implement for your enterprise. Set up the following addresses using the Attributes Value tab in the Workflow Builder: • • • HR email address Training administrator email address Recruitment supervisor email address See: Defining Your Enterprise’s Email Addresses: page 6–9 24. See Descriptive Flexfields and Address Styles (Oracle Applications User Guide) 25. The default address style is determined by the legislation of the business group. if necessary. select one of the predefined address styles.2 Implementation Guide . If you wish to make changes. Configure the Approvals Process Review the seeded approvals processes and. Details of the configuration options are available for each SSHR module. use the Descriptive Flexfield Segments window. To select an address style. Configure Your National Address Style To ensure that the correct address style for your country is used in the application. For each business flow. The error process sends a notification A–6 Oracle SSHR 4. Configure the Workflow Error Processes Each workflow–enabled function has an error process that runs when a system error occurs. 26.

Set Up User Profile Options User profiles control how users access information and how the information is displayed. See: Testing a Workflow Definition (Oracle Workflow Guide) 33. You configure the error processes in the Workflow Builder. Link the Workflow Item Type to the Function Use the Form Functions Window and the Parameters field to link the workflow item type to functions. See: Configuring Flexfields: page 7–6 35. Configure the Pages for Your Functions Use the Personalization Framework. See: Form Functions Window. then enable selected segments in the appropriate pages using the Personalization Framework. See: Configuring Workflow Error Processes: page 6–8 29. The Parameters field is displayed when you select the Form tab. (Oracle Applications System Administrators Guide) 30. See: Configuring Page Layouts 34. See: User Profiles (Oracle HRMS Applications User Guide) 32. Create Messages for the Regions You can add predefined messages to your regions or you can create your own messages if required. You define the profiles at either the user or responsibility level in the System Profile Values window. See: Defining User Access and Menus: page 5–12 31. Configure Flexfields for the Regions You can configure the flexfield structures in the Application Developer responsibility.and a description of the error to the sysadmin ID. Test the Basic Flow Test the workflow process to make sure that it is correct. Add the Functions to the User Menu Make sure that your configured functions are available in your user menus. See: Adding Instructions to Web Pages: page 7–9 Implementation Steps A–7 .

The steps where you can use data supplied with the system are marked as seeded. approach to configuration lets you focus on those processes you want to use. Decision making is an important part of any configuration process. Steps that are required for all implementations are marked as required. A–8 Oracle SSHR 4. you must decide how you want to use it alongside your other Oracle HRMS applications.2) The flowcharts provide you with a summary of the logical sequence you might follow in any implementation of SSHR. Adopting a staged. Before you begin to customize SSHR. It is not the only sequence you could follow but one we recommend. The functional areas of the system you configure to your specific business needs. or incremental.Implementation Flowcharts (SSHR 4.2 Implementation Guide . Some functions have been seeded with default data.

0. part 1 Implementation Steps A–9 .Figure 22 – 1 Implementation Flowchart for SSHR 4.

part 2 A – 10 Oracle SSHR 4.2 Implementation Guide .0.Figure 22 – 2 Implementation Flowchart for SSHR 4.

APPENDIX B User Hook for New User Registration User Hook for New User Registration B–1 .

password_accesses_left.g_fnd_user_record. If you do not set the responsibility and security information using globals.CREATE_USER_DETAILS_A (which we will call the “After user hook” because it runs after the user name is created) • They are called in the user api BEN_PROCESS_USER_SS_API. use G_FND_RESP_RECORD. password_date.2 Implementation Guide . you can implement some additional code so that the user name and password are generated by the application when the user clicks a button on this page. ben_process_user_utility. You can implement this using user hooks. end_date. Minimum Setup The minimum you need to do to create a user with today’s date as the start date is to put the following two lines in the Before user hook.g_fnd_user_record. the New User Registration processes (Create New User.User Hooks To Generate User Names For New User Registration As supplied. B–2 Oracle SSHR 4. These globals are defined in the package BEN_PROCESS_USER_UTILITY. There are two user hooks: • BEN_PROCESS_USER_SS_BK1. Alternatively. The usage notes within this package explain how to use the globals. password_lifespan_accesses. You can also set up globals for start_date. The user hooks communicate with this caller api through a set of globals. use G_FND_USER_RECORD. the application uses the responsibility from the OAB:Self Registered Employee Responsibility profile option. New Employee Registration.password := ’testpassword’. last_logon_date. To associate responsibility and security group/security profile information with the user.CREATE_USER_DETAILS_B (which we will call the “Before user hook” because it runs before the user name is created) BEN_PROCESS_USER_SS_BK1.user_name := ’testuser’. ben_process_user_utility. To set the globals with user information. Using the Before User Hook Use the Before user hook to set globals with user and responsibility information. and Non–employee Registration) include a User ID page where users can enter a user name and password for logging on to self service.

fax. . email_address.password_lifespan_days. description. customer_id. and supplier_id.

but it does not handle multiple responsibilities. If you do so. menu. you can then pass in the global for employee id. the Before user hook enables you to pass in information about a responsibility. You could pass no information about responsibility in the Before user hook and instead call the appropriate ”fnd” api(s) in the After hook to take care of the responsibility. Attention: Never set the employee_id global within the New User Registration processes. Another use for the After hook might be to write code to populate some tables––such as communication or extract tables––from where you can extract the information later. For example. the global overwrites the employee id created during the process and so the user will not be associated with the correct employee id. User Hook for New User Registration B–3 . If you want to use the user wrapper api outside of the page for creating user name and password. Using the After User Hook Use the After user hook to accomplish something that needs to be done after a user is created. or any profile value that you want to associate with the user.

B–4 Oracle SSHR 4.2 Implementation Guide .

APPENDIX C Function–level Personalizations Function–level Personalizations C–1 .

Any region item not included in this table behaves in the default way. the function–level personalizations are not copied.0 (HR_CHANGE_JOB_SS) Assignment Attributes Displayed (Y/N) HRInstruction Department Position Grade People Group Assignment Status Other Assignment Information Statutory Information Payroll Salary Information Location N N N N N N N N N N N C–2 Oracle SSHR 4.Function–level Personalizations A number of the processes delivered with SSHR have function–level personalizations enabled. which is normally displayed in the Assignment page. See: Function–level Personalizations: page 7–3 Change Job V4. If you take a copy of one of these processes to create your own version. The tables show where a region item for a particular process behaves differently than it would in the standard module. for the Change Job process we can see that the Department item. is hidden. For example.2 Implementation Guide . so you can replicate them if you desire. The following tables show what personalizations are included in the delivered processes.

Assignment Review Attributes Displayed (Y/N) Change Reason Assignment Flex Assignment Status Ceiling Point Ceiling Step Department Name Employee Category Employment Category Establishment Name Frequency Grade Name Location Normal End Time Normal Start Time People Group Key Flex Performance Review Period Performance Review Frequency Position Name Salary Basis Salary Review Frequency Salary Review Period Work Hours Additional Information Payroll Name N N N N N N N N N N N N N N N N N N N N N N N N Function–level Personalizations C–3 .

0 (HR_CHANGE_JOB_TERMS_SS) Assignment Attributes Displayed (Y/N) Department Position Grade People Group Assignment Status Other Assignment Information Statutory Information Payroll Salary Information Location N N N N N N N N N N Assignment Review Attributes Displayed (Y/N) Change Reason Assignment Flex Assignment Status Ceiling Point Ceiling Step Department Name Employee Category Employment Category Establishment Name Frequency Grade Name Location N N N N N N N N N N N N C–4 Oracle SSHR 4.Change Job and Employment Terms V4.2 Implementation Guide .

Attributes Displayed (Y/N) Normal End Time Normal Start Time People Group Key Flex Performance Review Period Performance Review Frequency Position Name Salary Basis Salary Review Frequency Salary Review Period Work Hours Additional Information Payroll Name N N N N N N N N N N N N Change Cost Center V4.0 (HR_CHG_COST_LOC_SUP_SS) Assignment Attributes Displayed (Y/N) HRInstruction Job Position Grade People Group Assignment Status Other Assignment Information Statutory Information Payroll N N N N N N N N N Function–level Personalizations C–5 .

2 Implementation Guide .Attributes Displayed (Y/N) Salary Information Location N N Assignment Review Attributes Displayed (Y/N) Change Reason Assignment Flex Assignment Status Ceiling Point Ceiling Step Employee Category Employment Category Establishment Name Frequency Grade Name Job Title Location Employee is a Manager Normal End Time Normal Start Time People Group Key Flex Performance Review Period Performance Review Frequency Position Name Salary Basis Salary Review Frequency Salary Review Period N N N N N N N N N N N N N N N N N N N N N N C–6 Oracle SSHR 4.

0 (HR_CHG_COST_TRM_LOC_SUP_SS) Assignment Attributes Displayed (Y/N) N Job Position Grade People Group Assignment Status Other Assignment Information Statutory Information Payroll Salary Information Location N N N N N N N N N N Assignment Review Attributes Displayed (Y/N) Change Reason Assignment Flex Assignment Status Ceiling Point N N N N Function–level Personalizations C–7 .Attributes Displayed (Y/N) Work Hours Additional Information Payroll Name N N N Change Cost Center and Employment Terms V4.

Attributes Displayed (Y/N) Ceiling Step Employee Category Employment Category Establishment Name Frequency Grade Name Job Title Location Employee is a Manager Normal End Time Normal Start Time People Group Key Flex Performance Review Period Performance Review Frequency Position Name Salary Basis Salary Review Frequency Salary Review Period Work Hours Additional Information Payroll Name N N N N N N N N N N N N N N N N N N N N N C–8 Oracle SSHR 4.2 Implementation Guide .

Employee Status Change V4.0 (HR_EMP_STATUS_CHG_SS) Assignment Attributes Displayed (Y/N) N Position Grade Assignment Status Other Assignment Information Statutory Information Payroll Location N N N N N N N Assignment Review Attributes Displayed (Y/N) Change Reason Assignment Flex Assignment Status Ceiling Point Ceiling Step Employee Category Employment Category Establishment Name Frequency Grade Name Location Normal End Time Normal Start Time Position Name N N N N N N N N N N N N N N Function–level Personalizations C–9 .

2 Implementation Guide .0 (HR_EMP_TERMS_CHG_SS) Assignment Attributes Displayed (Y/N) N Position Grade Other Assignment Information Statutory Information Payroll Salary Information Location N N N N N N N Assignment Review Attributes Displayed (Y/N) Change Reason Assignment Flex Assignment Status Ceiling Point Ceiling Step Employee Category Employment Category Establishment Name N N N N N N N N C – 10 Oracle SSHR 4.Attributes Displayed (Y/N) Work Hours Additional Information Payroll Name N N N Employee Terms of Employment Change 4.

0 (HR_TRANSFER_SS) Assignment Attributes Displayed (Y/N) N Position Grade Other Assignment Information Statutory Information Payroll Salary Information Location N N N N N N N Function–level Personalizations C – 11 .Attributes Displayed (Y/N) Frequency Grade Name Location Normal End Time Normal Start Time People Group Key Flex Position Name Work Hours Additional Information Payroll Name N N N N N N N N N N Transfer V4.

2 Implementation Guide .Assignment Review Attributes Displayed (Y/N) Change Reason Assignment Flex Assignment Status Ceiling Point Ceiling Step Employee Category Employment Category Establishment Name Frequency Grade Name Location Normal End Time Normal Start Time Performance Review Period Performance Review Frequency Position Name Salary Basis Salary Review Frequency Salary Review Period Work Hours Additional Information Payroll Name N N N N N N N N N N N N N N N N N N N N N N C – 12 Oracle SSHR 4.

0 (HR_TERMINATION_SS) SSHR Process People Attributes Displayed (Y/N) PerInfo Header Assignment Selection N N New Hire V4.Termination with Compensation V4.0 (HR_TERMINATION_COMP_SS) SSHR Process People Attributes Displayed (Y/N) PerInfo Header Assignment Selection N N Termination V4.0 (HR_NEWHIRE_SS) Assignment Attributes Displayed (Y/N) Position Grade Assignment Status N N N Assignment Review Attributes Displayed (Y/N) Change Reason Assignment Flex Assignment Status Ceiling Point N N N N Function–level Personalizations C – 13 .

Attributes Displayed (Y/N) Ceiling Step Employee Category Establishment Name Grade Name Position Name N N N N N Basic Details Review Attributes Displayed (Y/N) Hire Date Effective Date Employee Number Gender Person Type Disability Code Full Name Effective Date Full Name Hire Date Gender Y N N Y Y N N N N Y Y Employment Type Attributes Displayed (Y/N) Date of Last Change N C – 14 Oracle SSHR 4.2 Implementation Guide .

Main Address Update Attributes Displayed (Y/N) Effective Date N Main Address Review Attributes Displayed (Y/N) Effective Date N Other Assignment Information Attributes Displayed (Y/N) Assignment Flex Employee Category N N Other Employment Information Attributes Displayed (Y/N) Configurable Pay Info N PayRate Misc Fields Table Attributes Displayed (Y/N) Changed On Last Pay Change N N Function–level Personalizations C – 15 .

C – 16 Oracle SSHR 4.2 Implementation Guide .

22–16 B Basic Details. 3–11 Actions page. 22–41 defining enrollment requirements. 1–8. 22–59 defining a plan. 12–5 multiple assignments. 1–20. 16–5 and user hooks. 12–14 Change Manager. 18–11 configuring. 12–5 salary basis. 22–18 employee reassignment. 22–43. 5–20 Index – 1 . 1–8. 5–25 Benefits Enrollment. 6–2. 1–19. 8–2 configuring in Workflow Builder. 1–7. 1–15 activity rates. 1–20 Change Location. 1–15. 10–28 Access levels. 1–11. 16–7 Compensation Workbench. 1–12 Appraisals. 22–52 itemization. 1–10. 22–12 moving an employee. 1–18 Applicant Hire. 1–8. 1–10. 8–5 Review and Confirm. 6–3 Action items and self–service messages. 17–22 removing Benefits Enrollment page. 22–52 backing–out life events. 1–18. 10–3 Batch user accounts. 17–33. 1–11. 1–10. 9–15 Assignment. 22–11 approvals. 17–33. 1–16. 1–12 Approvals. 22–22 auto–issuing a budget. 3–11. 22–57 budgets. 1–7. 12–26 Compensation Activity view. 8–9 dynamic approvals. 22–47 C Candidate Offers. Save for Later. 1–7. 5–18 and concurrent programs. 22–2 Participation Process: Compensation. 8–8 customizing using PL/SQL. 22–8 Close Enrollment Process. 8–7 Oracle Approvals Management (OAM). 22–52 overview. 1–16.Index A Absences. 12–5 Assignment Details view. 22–19 issuing a budget. 1–7. 1–9. 15–2 Academic Rank. 18–39 defining. 5–5 Address. 22–23 allocations. 17–10. 22–43 employee eligibility. 1–8. 18–36 Benefits reporting group. 13–2 Apply for a Job. defining. 18–39 Actions. 17–30. 22–50 performance ratings.

1–20 Extra Information Types (EITs). 13–2 HR views. 1–7. configuring. 5–20 Configuration See also Personalization Framework guidelines. New User Registration. 7–2 Emergency Contacts. 18–29 Flexfields. 1–19. 18–5 Setting up. 22–62 promotions. 22–30 setting up. 1–18. 17–28. 7–10 E Education and Qualifications. 1–8. 1–19. 5–5 defining. 3–9 Eligibility and Enrollment List. 10–13 Employee Information. 18–5 Overview. 11–2 External Training. 18–31 Federal Health Employee Benefits. 1–7. 5–15 legislation–specific. 1–12. 1–11. 22–56 processing. 4–2 overview. 3–9 schedule enrollments in Benefits. 1–18. 18–3 FEHB Administering. 5–7 Future–dated changes. 16–3 Employee Reviews. 1–10. 4–2 Configuration Framework See also Personalization Framework hierarchy. 7–3 Functions and OAM.2 Implementation Guide . 22–63 Email address. 11–4 Employee/Manager Views. 1–16. 7–6 Function–level personalizations. 1–13 Error processes. 1–11. 1–5 Dependents and Beneficiaries. 22–48 Progress Report. 1–8. 22–47 reports. See Views HRMS Profile Options report. 8–7 G Generic users. 10–11 Disable Self–Service Personal profile option. 6–8 Events and Bookings. 1–10. 2–5 Index – 2 Oracle SSHR 4. 1–12. 1–10. 10–21 Concurrent programs for batch user creation. 22–52 updating employee eligibility. 22–29 switch manager. 22–39 Post Process. 6–9 H Hiring. 12–20 F Federal Employee Health Benefits Administering. 22–13 reporting groups. 18–27 Definitions. 8–11 and user access. 7–4 Dynamic approvals. 3–9 D Dates effective. 22–21 updating amounts. Overview. 18–3 Populate program design. 1–20 Enter Person Process. 10–16 Effective dates.personalizing. 9–20 Global button bar. 22–52 Competence Profile. 1–10. 22–32 status. 3–9 future–dated changes.

6–3 O Oracle Approvals Management (OAM). 1–10. 1–20. B – 2 user names and passwords. 20–14. 1–15. 20–3 Payroll. 8–11 Oracle Self–Service Human Resources. 9–29 user hook. 12–23 Other Professional Awards. 20–2 to 20–30 Payslip. 10–2 to 10–20 Personalization Framework. 10–19 L Legislation–specific functions. 19–2 Instructions. 1–9. 10–15 to 10–52 Profile options. 1–17 Canada. 12–24 Payment Methods. 1–17. 1–19. 9–37 generic users. 5–12 types of. 12–5 N New Hire. 1–22 Logos. 9–34 Pay Rate. 7–9 function–level personalizations. 1–13. 9–8 MEE modules. 1–10. 1–9. 20–21 Person search. 9–11. 1–2 Organization Manager. 20–19 US. 1–16. 17–35. 10–9 Primary care providers. 1–18 Other Employment Information. 7–2. 2–2 Multiple assignments. 1–14. 7–11 P Passwords. A – 2 Individual Compensation Distributions (ICD). defining restrictions for selecting. 13–2 New User Registration. 18–41 Primary care search provider facility. 1–8. 9–8 Personal Information modules. 1–18. 5–2 Person Tree. 9–34 Index – 3 . 12–2 to 12–39 chained processes. 2–5 Disable Self–Service Personal. 7–4 M Main Address. 3–7. 12–3 Menus defining. from SSHR 3. See MEE modules Manager Actions. 1–14. 9–3 Personal Actions. 9–20 Life events. 1–8. 17–38. 7–6. 1–9. 18–44 Professional Details modules. 7–9 Item type. 1–9. 1–10. 5–9 user access. 1–8. 8–5 configuring functions. 7–9 Migration. 7–3 Personalize Self–Service Defn profile option. 1–18. 1–16. 1–8. 1–8. 20–12 ZA. 9–26 Create User Name process. 12–28. 12–10 Other Address. New User Registration. 7–5. 1–8. 7–4 Phone Number. 14–2 and Termination. 20–16 generic. 12–2 sequence. 5–7 Licences. 20–10 UK. 10–5 Manage Employee Events modules. 9–18 configuring. 9–31. 1–10.I Implementation steps. 5–9 Messages.

9–37 HR:Cross Business Group. 12–10 and Organization Manager. 1–9. 1–13 Suitability Matching. user access. 9–11 HR: HR/Payroll Representative Source. 22–63 Responsibilities. for persons. 1–19. 9–35. 7–4 Search. 1–10. defining instruction text. migrating from. 18–37 Self–service Benefits Individual Compensation Distributions (ICD). 9–35. 12–10 Termination History view. 5–18 User hooks for batch user creation. 9–5 HR:HR/Payroll Representative Source. 20–27 Tax Form (W–4). 3–2. 9–35. 20–16. 1–7. configuring. 1–14. 1–9. 20–19 HRMS Profile Options report. 1–11. 12–5 Save for Later. 5–2 Secondary Address. 18–27 user access to. 12–5 HR:Payroll Payments Self–Service Enable Multiple Assignments. 10–26 Termination. 5–3 Self–Service. 1–16. 1–17. 5–2 User accounts. 3–11 Index – 4 Oracle SSHR 4. 9–37 HR:Business Group. 1–16 SSHR 3. 9–35 Personalize Self–Service Defn. 1–17. 1–23 Resume. 5–2 security profiles. 1–7. Eligibility and Enrollment List. 10–25 Review and Confirm. 5–5 to people. 20–10. 5–2 Security profiles. 20–12. 5–9 responsibilities. 9–13. 12–5 HR:View Payslip From Date for WEB (MM/DD/YYYY). 9–8 HR:Restrict Transactions Across Business Groups in SSHR. 9–3. 13–2 HR: Self Service HR Licensed. 9–8 HR:Override Grade Defaults. 5–25 S Salary basis. 9–35 OAB: User to Payroll Link. 20–24 HR: Propagate Data Changes. 1–19. 17–28. 2–3 T Tabbed regions. 12–17 Special Information Types (SITs). 9–37 OAB: User to Organization Link. 18–23 Special Information Types (SIT). 1–8. batch creation of. 1–12 System requirements. 5–4. 9–15 U User access defining. 7–7 Tax Form (W–2). 5–2 security. 10–7 Security.HR: Cross Business Group.2 Implementation Guide . 20–24 Tenure Status. 1–10. 17–31. 2–5 OAB: Self Registered User Responsibility. 13–2 HR: Enable Multiple Assignments in SSHR. 9–5 HR:Self Service New Hire Default Values. 1–14. 12–28. 9–13 Reports. 1–8. 1–9. 1–14. 16–9 Training. 5–13 menus. 20–24 HR:Manager Actions Menu. 5–3 to functions. 3–3 Succession Planning. 17–25. 2–2 SSHR functions. 1–9. 20–14. 19–2 scheduled enrollment dates. 1–8. 13–2 HR:Use Grade Defaults. 1–20 R Release Employee Information. 20–27 HR: Online Tax Forms Update Method. 20–3 HR:Personal Actions Menu.

6–7 Workflow cleanup process. 7–9 removing Benefits Enrollment page. 17–30. 18–37 Enrollment Action Types. 18–36 Windows Communication Types. 7–9 messages. 16–5 Compensation Activity. 17–35. 6–8 item types. 8–8 attribute values. 9–34 V Views. 6–3 approvals. 1–11. 17–31. configuring. 6–10 Workflow error processes. 6–3 Workflow attribute values. 1–21 Assignment Details. 6–3 Index – 5 . configuring. 1–9. 18–41 Work Preferences. 1–17. 1–19.for new user registration. 6–5 error processes. 18–39 Maintain Plan Primary Care Providers. 1–23 User names. 6–10 configuring objects. 6–7 cleanup process. 7–5 instructions. 6–3 objects. New User Registration. copying. 16–9 W Web pages configuring. 10–24 Work Schedule. B – 2 User menus. 6–5 copying. 16–7 Employee Information. 16–3 search function. 3–7. 6–2 access levels. 1–10. 6–8 Workflow item type. 6–3 Workflow objects configuring. 17–33. 12–12 Workflow. 16–11 Termination History.