R12 Oracle HRMS Self Service Fundamentals

R12 Oracle HRMS Self Service Fundamentals Student Guide

D50093GC10

Edition 1.0

July 2007

D51827

Copyright © Oracle Corporation, 2007. All rights reserved.

This documentation contains proprietary information of Oracle Corporation. It is provided under a license agreement containing restrictions on use and disclosure and is also protected by copyright law. Reverse engineering of the software is prohibited. If this documentation is delivered to a U.S. Government Agency of the Department of Defense, then it is delivered with Restricted Rights and the following legend is applicable:

Restricted Rights Legend

Use, duplication or disclosure by the Government is subject to restrictions for commercial computer software and shall be deemed to be Restricted Rights software under Federal law, as set forth in subparagraph (c)(1)(ii) of DFARS 252.227-7013, Rights in Technical Data and Computer Software (October 1988).

This material or any portion of it may not be copied in any form or by any means without the express prior written permission of the Education Products group of Oracle Corporation. Any other copying is a violation of copyright law and may result in civil and/or criminal penalties.

If this documentation is delivered to a U.S. Government Agency not within the Department of Defense, then it is delivered with “Restricted Rights,” as defined in FAR 52.227-14, Rights in Data-General, including Alternate III (June 1987).

The information in this document is subject to change without notice. If you find any problems in the documentation, please report them in writing to Worldwide Education Services, Oracle Corporation, 500 Oracle Parkway, Box SB-6, Redwood Shores, CA 94065. Oracle Corporation does not warrant that this document is error-free.

Oracle and all references to Oracle Products are trademarks or registered trademarks of Oracle Corporation.

All other products or company names are used for identification purposes only, and may be trademarks of their respective owners.

Author

Kathryn O’Donoghue, Pragya Nair

Technical Contributors and Reviewers

Emma Haywood, Margaret Wong

This book was published using: oracletutor


R12 Oracle HRMS Self Service Fundamentals Table of Contents i

Table of Contents

R12 Oracle HRMS Self Service Fundamentals.............................................................................................1-1 R12 Oracle HRMS Self Service Fundamentals .............................................................................................1-2 Curriculum Outline........................................................................................................................................1-3 Introduction ...................................................................................................................................................1-4 Objectives ......................................................................................................................................................1-5

Introduction to SSHR......................................................................................................................................2-1 Introduction to SSHR ....................................................................................................................................2-2 Objectives ......................................................................................................................................................2-3

Overview of Self-Service Human Resources .................................................................................................3-1 Overview of Self-Service Human Resources (SSHR)...................................................................................3-2 What is a Web-based Application?................................................................................................................3-3

Guided Demonstration - Self-Service Interface.........................................................................................3-4 Professional User Interfaces versus Self-Service User Interfaces ................................................................3-5 Integration of SSHR and Professional User Interface ..................................................................................3-6 Why Use Self-Service?..................................................................................................................................3-7 Self-Service Functionality in HRMS.............................................................................................................3-8 Configuration Tools for SSHR ......................................................................................................................3-10 Highly Configurable Interface.......................................................................................................................3-11 Workflow-Enabled ........................................................................................................................................3-12 Useful Documentation...................................................................................................................................3-13 Related Guides...............................................................................................................................................3-14

Implementing SSHR........................................................................................................................................4-1 Implementing SSHR......................................................................................................................................4-2 Objectives ......................................................................................................................................................4-3

Self-Service Basics ...........................................................................................................................................5-1 Self-Service Basics ........................................................................................................................................5-2 e-Business Suite Architecture........................................................................................................................5-3 Operation of Web-Based Functions...............................................................................................................5-4 Personal Information: Functional Flow .........................................................................................................5-7

Guided Demonstration - Functional Flow .................................................................................................5-8 Storing Transaction Data ...............................................................................................................................5-14

User Access and Security ................................................................................................................................6-1 User Access and Security ..............................................................................................................................6-2 Security Mechanisms.....................................................................................................................................6-3 Defining User Access ....................................................................................................................................6-5 Responsibilities..............................................................................................................................................6-6 Functions, Menus, and Responsibilities ........................................................................................................6-8 Creating a Responsibility...............................................................................................................................6-9 Types of SSHR Users ....................................................................................................................................6-10 Comparing Employee/Worker and Manager Access.....................................................................................6-12 People versus Users .......................................................................................................................................6-13 Associating User with Person........................................................................................................................6-14 Creating Users - Information .........................................................................................................................6-15

Practice - Overview ...................................................................................................................................6-16 Practice - Creating Responsibilities ...........................................................................................................6-17 Solution – Creating Responsibilities..........................................................................................................6-20 Practice - Creating New Users...................................................................................................................6-23 Solution – Creating New Users .................................................................................................................6-26

Batch Creation of User Accounts ..................................................................................................................6-28 Creating User Hooks .....................................................................................................................................6-30


R12 Oracle HRMS Self Service Fundamentals Table of Contents ii

Access Roles for Self-Service Transactions ..................................................................................................6-31 User Access to People ......................................................................................................................................7-1

User Access to People ...................................................................................................................................7-2 Security Profiles (Non-Manager) ..................................................................................................................7-3 Security Profiles (Manager)...........................................................................................................................7-4 Assignment-Based Security...........................................................................................................................7-6 Interaction of Security Profiles ......................................................................................................................7-7 Releasing Information ...................................................................................................................................7-8 Hierarchy Page ..............................................................................................................................................7-9

Guided Demonstration - Hierarchy Page...................................................................................................7-10 Hierarchy .......................................................................................................................................................7-11 Search Page ...................................................................................................................................................7-12 Person Types .................................................................................................................................................7-13 My List ..........................................................................................................................................................7-14

Practice - Hierarchy, Search, and My List .................................................................................................7-15 Solution – Hierarchy, Search, and My List................................................................................................7-17

Manager Enter Process Pages........................................................................................................................7-18 Security Profiles - Considerations .................................................................................................................7-19

Practice - Using Security Profiles ..............................................................................................................7-20 Solution – Using Security Profiles.............................................................................................................7-22 Practice - Release Information Function....................................................................................................7-25 Solution – Release Information Function ..................................................................................................7-26 Practice - Change Manager Function and Hierarchy Page ........................................................................7-27 Solution – Change Manager Function and Hierarchy Page .......................................................................7-29

Implementation Steps......................................................................................................................................8-1 Implementation Steps ....................................................................................................................................8-2 Implementation Strategy................................................................................................................................8-3 Prepare Environment for SSHR.....................................................................................................................8-4 Configure HRMS Applications .....................................................................................................................8-6 User Access Setup .........................................................................................................................................8-7 Configure Workflow Processes and Page Layouts........................................................................................8-8 Migrate Configuration to Test and Production Environments.......................................................................8-10 Summary........................................................................................................................................................8-11

Configuring SSHR...........................................................................................................................................9-1 Configuring SSHR.........................................................................................................................................9-2 Objectives ......................................................................................................................................................9-3

Functions, Menus, and Responsibilities .........................................................................................................10-1 Functions, Menus and Responsibilities .........................................................................................................10-2 Functions, Menus, and Responsibilities - Overview .....................................................................................10-3 Functions, Menus, and Responsibilities ........................................................................................................10-4 Configuring Menus........................................................................................................................................10-5 Menu Types ...................................................................................................................................................10-6 Top-level Menus............................................................................................................................................10-7 Submenus ......................................................................................................................................................10-8 Designing Menus...........................................................................................................................................10-9 Hidden Submenus..........................................................................................................................................10-10 Data Security Menus .....................................................................................................................................10-12 Custom Menus 1............................................................................................................................................10-13 Custom Menus 2............................................................................................................................................10-14

Practice - Creating Menus .........................................................................................................................10-15 Solution – Creating Menus ........................................................................................................................10-17

Person Tree Navigation Paths........................................................................................................................10-20 Actions Menus...............................................................................................................................................10-21 Employee Actions Page.................................................................................................................................10-22

Practice - Actions Menus...........................................................................................................................10-23


R12 Oracle HRMS Self Service Fundamentals Table of Contents iii

Solution – Actions Menus .........................................................................................................................10-25 Configuring Functions ....................................................................................................................................11-1

Configuring Functions...................................................................................................................................11-2 Non-Manager versus Manager Functions......................................................................................................11-3 Considerations ...............................................................................................................................................11-4 Copying Delivered Functions ........................................................................................................................11-5

Practice - Configuring Functions...............................................................................................................11-7 Solution – Configuring Functions..............................................................................................................11-9

Adding Custom Functions to Menus .............................................................................................................11-12 Data Security Menus: Restricting Functions by Legislation Code ................................................................11-14 Adding Custom Functions .............................................................................................................................11-15 Data Security Menus .....................................................................................................................................11-16 Adding Custom Functions to Menus .............................................................................................................11-17

Practice - Adding Functions to Menus ......................................................................................................11-19 Solution – Adding Functions to Menus .....................................................................................................11-21

Changing the Manager Entry Pages...............................................................................................................11-24 Practice - Changing Manager Entry Page..................................................................................................11-25 Solution – Changing Manager Entry Page.................................................................................................11-27

Using the Workflow Builder ...........................................................................................................................12-1 Using the Workflow Builder .........................................................................................................................12-2 Workflow-Enabled SSHR Functions.............................................................................................................12-3 Workflow Builder..........................................................................................................................................12-4 Working with the Workflow Builder.............................................................................................................12-5 Working with Workflow Item Types.............................................................................................................12-6 Workflow Access Levels...............................................................................................................................12-7 Configurable and Locked Workflow Objects ................................................................................................12-8

Practice - Working with the Workflow Builder.........................................................................................12-9 Solution – Working with the Workflow Builder .......................................................................................12-10

Changing Workflow Objects .........................................................................................................................12-14 Practice - Changing a Process Flow ..........................................................................................................12-15 Solution – Changing a Process Flow .........................................................................................................12-17

Chaining Workflow Processes.......................................................................................................................12-23 Chaining Self-Service Activities ...................................................................................................................12-24 Manage Employment Events – Activities .....................................................................................................12-25 Sequencing Restrictions for Manage Employment Event Pages ...................................................................12-27 Applying a Patch ...........................................................................................................................................12-28

Configuring Web Page Layouts .....................................................................................................................13-1 Configuring Web Page Layouts.....................................................................................................................13-2 Configuring Self-Service Web Pages ............................................................................................................13-3 Oracle Applications Framework....................................................................................................................13-4 Personalization Levels ...................................................................................................................................13-5 Profile Options for Oracle Applications Framework....................................................................................13-6 Personalization - Buttons and Links ..............................................................................................................13-8 Configuration Options within the Oracle Applications Framework ..............................................................13-9

Practice - Configuring Web Page Layouts.................................................................................................13-10 Solution – Configuring Web Page Layouts ...............................................................................................13-12 Practice - Global Personalization Button...................................................................................................13-17 Solution – Global Personalization Button..................................................................................................13-18

Additional Options for Tabular Regions .......................................................................................................13-19 Adding User Instructions...............................................................................................................................13-20

Practice - Adding User Tips and Instructions ............................................................................................13-21 Solution – Adding User Tips and Instructions...........................................................................................13-23

Flexfields .......................................................................................................................................................13-28 Practice - Flexfields ...................................................................................................................................13-29 Solution - Flexfields ..................................................................................................................................13-31


R12 Oracle HRMS Self Service Fundamentals Table of Contents iv

Configuring the e-mail Address.....................................................................................................................13-33 Configuring the Global Button Bar ...............................................................................................................13-34 Logos .............................................................................................................................................................13-35

Guided Demonstration - Personalizing Logos...........................................................................................13-36 Configuring Effective Date Prompts .............................................................................................................13-38

Approvals .........................................................................................................................................................14-1 Approvals ......................................................................................................................................................14-2 Basic Approvals Loop ...................................................................................................................................14-3 Approvals ......................................................................................................................................................14-4 Enabling Dynamic Approvals........................................................................................................................14-5

Practice - Enabling Dynamic Approvals....................................................................................................14-6 Solution – Enabling Dynamic Approvals ..................................................................................................14-7

Configurable Approvals Options...................................................................................................................14-8 What is AME? ...............................................................................................................................................14-9 When Can I Use AME? .................................................................................................................................14-10 Business Requirements..................................................................................................................................14-11 Overview of AME Components ....................................................................................................................14-12 Approval Considerations ...............................................................................................................................14-13 Approvals Routing.........................................................................................................................................14-14

Practice - Working with Approvals ...........................................................................................................14-15 Solution – Working with Approvals ..........................................................................................................14-16 Practice - Creating an AME Rule ..............................................................................................................14-18 Solution – Creating an AME Rule.............................................................................................................14-20

Summary........................................................................................................................................................14-22 Using SSHR......................................................................................................................................................15-1

Using SSHR...................................................................................................................................................15-2 Objectives ......................................................................................................................................................15-3

Common SSHR Functions ..............................................................................................................................16-1 Common SSHR Functions.............................................................................................................................16-2 Common Functionality ..................................................................................................................................16-3 Review Page ..................................................................................................................................................16-4 Return for Correction.....................................................................................................................................16-5 Save for Later ................................................................................................................................................16-6 Managing Dates.............................................................................................................................................16-7 New User Registration...................................................................................................................................16-9 New Employee Registration Process.............................................................................................................16-10

Practice - Setting Up a Generic User ID for New User Registration.........................................................16-12 Solution: Setting Up a Generic ID for New Employee Registration .........................................................16-14

Document Manager .......................................................................................................................................16-19 Guided Demonstration - Using the Document Manager............................................................................16-21

FastFormula Options for Document Manager ...............................................................................................16-25 Self-Service Actions .........................................................................................................................................17-1

Self-Service Actions ......................................................................................................................................17-2 Overview – Self-Service Actions ..................................................................................................................17-3 Types of Self-Service Action.........................................................................................................................17-4 Life-Cycle of Self-Service Action .................................................................................................................17-5 Profile Options for Self-Service Actions .......................................................................................................17-6 Conflicting Actions........................................................................................................................................17-8 Conflicting Actions - Resolution ...................................................................................................................17-9 Approvals and Access Roles .........................................................................................................................17-10

Practice - Access Roles and Approvals .....................................................................................................17-11 Solution – Access Roles and Approvals ....................................................................................................17-13

Configuring Self-Service Actions..................................................................................................................17-15 Combining Activities for Self-Service Actions .............................................................................................17-16 What-If Analysis............................................................................................................................................17-17


R12 Oracle HRMS Self Service Fundamentals Table of Contents v

Eligibility Processing.....................................................................................................................................17-18 Summary........................................................................................................................................................17-19

Advanced Topics..............................................................................................................................................18-1 Advanced Topics ...........................................................................................................................................18-2 Objectives ......................................................................................................................................................18-3

Employee Directory.........................................................................................................................................19-1 Employee Directory.......................................................................................................................................19-2 Single Sign-On or Anonymous Log-In?........................................................................................................19-4 Enabling Single Sign-On ...............................................................................................................................19-5 Overrides .......................................................................................................................................................19-6 Customer Overrides for Employee Directory ................................................................................................19-7 Populating the Repository..............................................................................................................................19-8 Overrides for Populating the Repository .......................................................................................................19-9 Refresh Modes...............................................................................................................................................19-10

Guided Demonstration - Employee Directory and Single Sign-On...........................................................19-11 Summary........................................................................................................................................................19-18

Responsibility Ownership ...............................................................................................................................20-1 Responsibility Ownership..............................................................................................................................20-2 Additional Configuration Steps .....................................................................................................................20-4

Practice - Creating Data Grants for Responsibility Ownership .................................................................20-5 Solution - Creating Data Grants for Responsibility Ownership.................................................................20-6

Summary........................................................................................................................................................20-8


R12 Oracle HRMS Self Service Fundamentals Table of Contents vii

Preface

Profile

Before You Begin This Course

Before you begin this course, you should have the following qualifications:

• Thorough knowledge of navigating within Oracle Applications

• Working experience of Human Resources Management and of Oracle HRMS

Suggested Prerequisites

• R12 Implement Oracle Workflow - InClass (D49191GC10)

• R12 Oracle HRMS System Administration Fundamentals- Inclass (D49872GC10) or eClass (D49882GC10)

• R12 HRMS People Management Fundamentals – Inclass (D48423GC10) or eClass (D48425GC10)

How This Course Is Organized

This is an instructor-led course featuring lecture and hands-on exercises. Online demonstrations and written practice sessions reinforce the concepts and skills introduced.

Related Publications

Oracle Publications

Title Part Number

Oracle HRMS Configuring, Reporting, and System Administration Guide B31614-05

Oracle HRMS Implementation Guide B31617-02

Oracle HRMS FastFormula User Guide B31616-02

Oracle Self-Service Human Resources Deploy Self-Service Capability Guide B31648-03

Oracle Approvals Management Implementation Guide B31622-02

Additional Publications

• System release bulletins


R12 Oracle HRMS Self Service Fundamentals Table of Contents viii

• Installation and user’s guides

• read.me files

• Oracle Magazine


R12 Oracle HRMS Self Service Fundamentals Table of Contents ix

Typographic Conventions

Typographic Conventions in Text Convention Element Example Bold italic Glossary term (if

there is a glossary)

The algorithm inserts the new key.

Caps and lowercase

Buttons, check boxes, triggers, windows

Click the Executable button. Select the Can’t Delete Card check box. Assign a When-Validate-Item trigger to the ORD block. Open the Master Schedule window.

Courier new, case sensitive (default is lowercase)

Code output, directory names, filenames, passwords, pathnames, URLs, user input, usernames

Code output: debug.set (‘I”, 300); Directory: bin (DOS), $FMHOME (UNIX) Filename: Locate the init.ora file. Password: User tiger as your password. Pathname: Open c:\my_docs\projects URL: Go to http://www.oracle.com User input: Enter 300 Username: Log on as scott

Initial cap Graphics labels (unless the term is a proper noun)

Customer address (but Oracle Payables)

Italic Emphasized words and phrases, titles of books and courses, variables

Do not save changes to the database. For further information, see Oracle7 Server SQL Language Reference Manual. Enter [email protected], where user_id is the name of the user.

Quotation marks

Interface elements with long names that have only initial caps; lesson and chapter titles in cross-references

Select “Include a reusable module component” and click Finish. This subject is covered in Unit II, Lesson 3, “Working with Objects.”

Uppercase SQL column names, commands, functions, schemas, table names

Use the SELECT command to view information stored in the LAST_NAME column of the EMP table.

Arrow Menu paths Select File > Save. Brackets Key names Press [Enter]. Commas Key sequences Press and release keys one at a time:

[Alternate], [F], [D] Plus signs Key combinations Press and hold these keys simultaneously: [Ctrl]+[Alt]+[Del]


R12 Oracle HRMS Self Service Fundamentals Table of Contents x

Typographic Conventions in Code Convention Element Example Caps and lowercase

Oracle Forms triggers

When-Validate-Item

Lowercase Column names, table names

SELECT last_name FROM s_emp;

Passwords DROP USER scott IDENTIFIED BY tiger;

PL/SQL objects OG_ACTIVATE_LAYER (OG_GET_LAYER (‘prod_pie_layer’))

Lowercase italic

Syntax variables CREATE ROLE role

Uppercase SQL commands and functions

SELECT userid FROM emp;

Typographic Conventions in Navigation Paths

Typographic Conventions in Navigation Paths

This course uses simplified navigation paths, such as the following example, to direct you through Oracle Applications.

(N) People > Enter and Maintain > (M) Query-Find > (B) Assignment

This simplified path translates to the following:

1. (N) From the Navigator window, select People then Enter and Maintain.

2. (M) From the menu, select Query then Find “your employee”.

3. (B) Click the Assignment button.

Notations:

(N) = Navigator

(M) = Menu

(T) = Tab

(B) = Button

(I) = Icon

(H) = Hyperlink


R12 Oracle HRMS Self Service Fundamentals Table of Contents xi

Typographical Conventions in Help System Paths

This course uses a “navigation path” convention to represent actions you perform to find pertinent information in the Oracle Applications Help System.

The following help navigation path, for example—

Oracle HRMS > Total Compensation Elements Setup > Elements > How To > Define an Element

— represents the following sequence of actions:

1. In the navigation frame of the help system window, expand your local Oracle HRMS entry.

2. Under the Oracle HRMS entry, expand Total Compensation Elements Setup.

3. Under Total Compensation Elements Setup, expand Elements.

4. Under Elements, expand How To.

5. Under How To, select Define an Element.

This will display step-by-step instructions on how to complete the Element window.

Copyright © Oracle, 2007. All rights reserved.

R12 Oracle HRMS Self Service Fundamentals Chapter 1 - Page 1

R12 Oracle HRMS Self Service Fundamentals Chapter 1



R12 Oracle HRMS Self Service Fundamentals



Curriculum Outline



Introduction



Objectives


Introduction to SSHR Chapter 2 - Page 1

Introduction to SSHR Chapter 2



Introduction to SSHR



Objectives


Overview of Self-Service Human Resources Chapter 3 - Page 1

Overview of Self-Service Human Resources Chapter 3



Overview of Self-Service Human Resources (SSHR)



What is a Web-based Application?



Guided Demonstration - Self-Service Interface

Responsibility: Employee Self Service

1. Log in to SSHR as TBENNETT/welcome.

2. (M) Employee Self Service > Personal Information

The Overview Page appears.

3. Explain that users can use the Personalization Framework to configure instructions and field names, for example.

4. Click the Update button.

5. Click the Next button to continue to the next page.

The Basic Details page appears.

6. Change the value in the Marital Status field to Separated.

7. Click the Next button.

The Review page appears.

8. Explain that the Blue circle indicates a changed item.

9. Click the Cancel button.

10. Log out of the application.



Professional User Interfaces versus Self-Service User Interfaces



Integration of SSHR and Professional User Interface

Integration of SSHR and Professional User Interface

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



Why Use Self-Service?

Why Use Self-Service?

Provides secure, direct access to systems • Configurable security rules control access to employee records • Changes remain subject to manager or HR department approval as required • Uses responsibilities to control which self-service functions a user can access

User-friendly interface • Compresses cycle times • Reduces operating costs • Lowers staffing requirements for selected tasks • Allows personalization

Flexibility • Manages the process flow • Automated process • Ensures that correct approvals chain is used • Usually available when required (evenings/weekends, or for homeworkers)



Self-Service Functionality in HRMS

Self-Service Functionality in HRMS

HRMS provides many opportunities to take advantage of a self-service interface. Some examples are listed in this slide. Self-service functions are available in the following functional areas: Compensation, Benefits, and Payroll

• Compensation Workbench • Individual Compensation Distribution • Vehicle and Mileage Processing • Payroll

Time and Labor Talent Management

• Training Enrollment • Performance and Career • Management

Enterprise and Workforce Management



• Personal Information • Professional Information • Manage Employment Events • Views

Workforce Sourcing and Deployment • Recruitment



Configuration Tools for SSHR

Configuration Tools for Web-based Applications

The graphic shows which different configuration tools are used with Web-based applications: • Data flows between the web-based application and the forms interface. • The Workflow Builder controls the sequence of events and transactions. • The Oracle Application Framework defines the appearance of the web pages.

Note: Although the Meta Data Services Repository is mentioned above as a configuration tool, you should modify web pages using only the Personalization Framework so that any changes made are preserved during upgrades. Note: The Meta Data Services Repository is sometime referred to as the AK Dictionary or Web Applications Dictionary (historical names). Similarly, the Oracle Application Framework was previously known as the Personalization Framework or the Configuration Framework.



Highly Configurable Interface



Workflow-Enabled

Workflow-Enabled

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



Useful Documentation



Related Guides


Implementing SSHR Chapter 4 - Page 1

Implementing SSHR Chapter 4



Implementing SSHR



Objectives


Self-Service Basics Chapter 5 - Page 1

Self-Service Basics Chapter 5



Self-Service Basics



e-Business Suite Architecture

e-Business Suite Architecture

The slide illustrates the interaction of the highlighted client side, middle-tier, and server side components.

• Client/PC side - Browser (Internet Explorer or Netscape Navigator) - the user interface

• Middle Tier - Application Server, includes

-Web Listener (Apache) -various other components, including Servlet Engine, JSP and PL/SQL Gateway

• Server Side - Data Server, includes

-Applications data -Setup data (Menus, responsibilities, etc.) -Meta Data Services Repository (Web page region definitions) -Workflow (process flow definitions)



Operation of Web-Based Functions


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





The appearance of the page is determined by: • Process Definition (defined in Workflow Builder) • Region Definition (defined in Meta Data Service Repository) • Region Configurations (defined in Meta Data Service Repository using the Oracle

Application Framework)





Page content is determined by: • Selected Person

- The person associated with the current user (Employee functions), or - The person selected by the user (Manager functions)

• Security profile - Is the subject employee included in the Security Profile associated with the current

responsibility for this user? • Granted employees

- If the employee is not in the user’s security profile, has the employee granted information to the user?

- Does the user’s responsibility allow access to released information? • Data security

- Is this function permitted for the legislation code of the subject employee?



Personal Information: Functional Flow


1. The user chooses the Personal Information function from the user menu. 2. The HTML Call of this function

(OA.jsp?akRegionCode=HR_CREATE_PROCESS_TOP_SS&akRegionsApplicationId=800) causes the application to call the HR workflow service, while the Parameter field specifies the Personal Information workflow process (HR_PERSONAL_INFO_JSP_PRC) in the HR workflow item type (HRSSA).



Guided Demonstration - Functional Flow

Responsibility: Employee Self-Service

Use this demonstration to show the Personal Information function together with the Workflow Builder tool. Work through these steps in conjunction with the slides in the Self-Service Basics lesson. The titles of the corresponding slides are given below:

Personal Information: Functional Flow (AOL – Application Object Library)

1. Log on to SSHR as TBENNETT/welcome and display the Personal Information function.

• (N) SSHR > Employee Self-Service > Personal Information

Personal Information: Functional Flow (Workflow Builder)

2. Open the Workflow Builder.

3. Select the HR item type and expand the Processes node.

4. Select the Personal Information process and double click to open the Workflow Diagrammer.

5. Place your cursor on the Start icon. Explain that this is the starting point for the workflow process.

6. Move your cursor to the Personal Information Overview process. Right click to display the Properties for the process.

7. Point out the HR_WORKFLOW_SERVICE.BLOCK function name under the Function tab. This is a generic workflow function.

8. Point out the HR Activity Type Value attribute under the Node Attributes tab. This value corresponds to a region defined in the Meta Data Service repository.

Personal Information: Function Flow (Web Browser)

9. Return to the web browser.

10. Click Update in the Main Address region of the page.

The Workflow Builder runs the Process Main Address subprocess and queries whether the user is updating or creating an address.

11. Switch to the Workflow Builder and point out the Process Main Address process.

12. Return to the web browser.



13. Select the “Enter a new address if you have moved” option and continue to the next page.

The Main Address page is displayed.

14. Explain that the user would enter information here and submit the transaction. The Review page is displayed.

15. Switch to the Workflow Builder. Point out the Initialize Approval Item Attributes activity.

SSHR initiates the Approvals functionality. When approvals is complete, Oracle HRMS inserts the data into the HR tables.

16. Log out of SSHR and the Workflow Builder.





3. The HR workflow service creates an instance of the Personal Information (HR_PERSONAL_INFO_JSP_PRC) workflow process for the HRSSA item type.

Note: The FND data security checks to make sure that this function is permitted for the legislation code of the current employee’s business group. Personal Information is a global function that is available for all legislation codes.

4. Nested within this process is the subprocess Process Personal Information (HR_PROCESS_PERINFO_JSP_PRC), which Oracle Workflow runs, stopping on the first blocking activity called Personal Information Overview (HR_PERINFO_OVERVIEW_JSP_FCT).

5. The application calls the generic HR_WORKFLOW_SERVICE.BLOCK function, using the Meta Data Service Repository region HR_OVERVIEW_TOP_SS, specified in the HR Activity Type Value workflow attribute for this activity. The activity type is JSP.





6. A page is displayed based on the definition of the HR_OVERVIEW_TOP_SS region and its nested subregions. The page is influenced by any context-sensitive flexfields and the cumulative effect of any Oracle Application Framework configurations that relate to these regions. The definition for this page is stored in the Meta Data Service Repository. To change the definition you would use the Oracle Application Framework and configure the region to suit your requirements.

7. The user chooses the Update button in the Main Address page region. 8. Oracle Workflow runs the Process Main Address subprocess. If no past address changes

are awaiting approval or correction, or if no future-dated address changes exist, the Details page is displayed. The user specifies whether they want to correct an existing address or to enter an entirely new one. The button displayed to the user will be either Update/View Future Changes or View Pending Approval.





9. If the user chooses to enter a new address, the Entry page is displayed. The user enters the information. If required, the user can save the information and submit the transaction later. In this case, the changes entered so far are saved to the transaction tables without server-side validation. If the user chooses to correct an existing address, the existing Address information is displayed. The user corrects the information.

10. When the user has entered the information (or is ready to complete the transaction), they click the Next link at the bottom of the page. Any field-related errors (bad formatting, missing fields, and so on ) are flagged by a JavaScript procedure stored on the client and the user is asked to correct this information.

11. The web page data is sent from the client to the server and server-side validation is performed by HR Application Programming Interfaces (APIs).

12. If all fields are validated, the Review Page is displayed.





13. When the changes are complete, the user returns to the Review page and clicks the Submit Information link to save the changes.

14. If the Main Address part of the Personal Information function is configured for update without requiring approval , the new address data is inserted directly into the HR tables.

15. If the Main Address part of the Personal Information function is configured to required approval, the data is inserted into the HR transaction tables and the Approvals process begins for that item.

16. The workflow item is routed for approval according to the configuration of the Approvals process.

17. The approver can either approve or reject the transaction or return it to the user for correction. If the transaction is returned for correction, it is displayed for the user in the Actions Saved for Later table in the Actions page. The user can reopen the transaction. The previous values are reloaded from the transaction tables ready for the user to make the required changes and resubmit. When the approver approves or rejects the transaction, the user is notified of the transaction status and the transaction details are deleted from the transaction tables. If the transaction is approved, the data is loaded into the HR tables.



Storing Transaction Data


In the next few slides we consider how the attributes of a transaction are assembled and validated as the user steps through the pages of a web-based transaction. The example is a two-step transaction from Manage Employment Events. At Step 1 the user makes changes to Organization, Job, Position and/or Grade. The entered values are validated by executing the Assignment API in validate mode (the changes are not submitted to the database). If valid, the values are stored in the HR Transaction Tables.





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





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





Before submitting the transaction, you have the opportunity to add additional approvers and to specify additional people to be notified.





If the approval chain is complete, or if no approvals are required for this transaction, SSHR executes the following steps: For each step of the transaction, SSHR retrieves the values stored in the transaction tables and executes the corresponding API to commit the changes to the application tables.

• The transaction is cleared from transaction tables when either: - Transaction completes successfully and is committed to the applications tables, or - Transaction is cancelled by user before completion, or - Transaction is rejected by approver.

The administrator should run the HR Background Cleanup concurrent program periodically to clean out transactions that may be left in the transactions tables under other circumstances. For example, if a power cut occurs when a user is creating a transaction, or if a user closes a browser during a transaction.


User Access and Security Chapter 6 - Page 1

User Access and Security Chapter 6



User Access and Security



Security Mechanisms

Security Mechanisms

In the next few topics you learn how the various security mechanisms depicted in this slide combine to control user access to SSHR functions.

• You grant responsibilities to users. You can view a list of all owned responsibilities using the Responsibility Ownership functionality in SSHR. This functionality enables you to display a list of people with access to each of your owned responsibilities and revoke access to the responsibilities if appropriate.

• In general, each responsibility has a top menu (controlling navigation to functions) and a security profile (controlling access to people). Note that if you enable Security Groups, you assign security profiles are assigned at the user+responsibility level, not to the responsibility itself.

• Multiple responsibilities can share the same top menu. You can exclude individual functions for different responsibilities using Function Exclusions.

• Supervisor-based security is one type of security profile that is particularly suitable for self-service users. This type of security profile dynamically generates a list of available employees and workers based on either the supervisor hierarchy or the supervisor



assignment hierarchy. You can configure this view to use the position hierarchy by setting the profile option HR: Self-Service Display Position Hierarchy to Yes.

• The Data Security mechanism is used by SSHR in conjunction with legislation-specific menus to prevent legislation-specific functions from being used on people in another legislation.

• The Assignment-based Security mechanism enables you to restrict security access based on individual assignments. The security processes evaluate permissions on an assignment-by-assignment basis, rather than displaying all assignments if a manager has access to any assignment.

• If you use the Release Information function, then you can supplement the list of people who appear in a security profile. With this function, you can allow other users (who are outside of the security profile) to access their records. Similarly, managers can use the Release Information to allow another manager (who is outside of the security profile) to access the records for one of their employees.

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



Defining User Access

Defining User Access

This slide summarizes the steps involved in setting up users with appropriate access to the system. When setting up user access to SSHR, you must set the following profile options:

• HR: Self Service HR Licensed • HR:Cross Business Group • HR:Restrict Transactions across Business Groups in SSHR



Responsibilities

Responsibilities

The menu associated with a responsibility is the primary mechanism (along with functions, function exclusions, and menu exclusions) for defining what the user can do. You set up responsibilities to control who the user has access to by using them together with the following mechanisms:

• Security Profile (profile option) - If you enable security groups, you associate security with user + responsibility (not

just the responsibility). • Restrict Transactions across BG (profile option) • Allow Granted Access (attribute of security profile) • Search tab (menu configuration)

For additional information on user and security profiles, see the online user documentation. • Security Overview under Oracle HRMS Global Security.

The delivered SSHR responsibilities are as follows: • Employee Self-Service • Manager Self-Service



• HR User Self Service • HR Professional • Payroll Professional • New User Registration • Contingent Worker Self-Service • Responsibility Ownership • HR Web Administrator • Candidate Offers

HR Foundation responsibilities: • Employee Self Service Foundation • Manager Self Service Foundation

Self-Service Web Applications responsibilities: • Workflow User Web Applications • Preferences

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



Functions, Menus, and Responsibilities


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



Creating a Responsibility



Types of SSHR Users

Types of SSHR Users

SSHR implementers should identify the different groups of people who use SSHR. The following are examples of typical user groups: Primary users

• Employees/Contingent workers (individual users) • Line managers • HR professionals

Secondary users • Appraisal reviewers • Approvers • Recruiters/hiring managers

Administrators • HR Web administrators • HR specialists • System administrators



When SSHR implementers have identified these groups, they should consider: • What tasks they will be performing • Which user records do they need to access • How they access user records



Comparing Employee/Worker and Manager Access

Comparing Employee/Worker and Manager Access

Employees and workers can only view their own records. Managers and professional users can view their own records plus the records for certain employees and workers (defined by security profile). Usually managers have access to the records for the employees or workers they supervise.



People versus Users



Associating User with Person

Associating User with Person

It is actually the person_id of the corresponding person which is stored on the FND_USERS table.



Creating Users - Information

Creating Users - Information

You can create people and users using the following methods: • Manual:

- Create people using Enter and Maintain People form - Create users using Users form

• Automatic: - Create people using Create Employee API - Create users using User Acct API

• Self-Service: - New Employee Registration function - New Hire function

The next slides look at how to create users/people using an automated method.



Practice - Overview

Overview

• By the end of this series of practices, you will have created a custom SSHR responsibility complete with configured versions of selected functions. Your configurations will include changes to workflow processes, page layouts, and approvals.

• In these practices, you use four employees, one of whom is in a different business group from the other three. Initially, none of the employees has a defined manager.

Name Malcolm Aurora xx Mary Martin xx Helen Carr xx Carl Whiteside xx

Business Group

Vision Corporation Vision Corporation

Vision Industries Vision Corporation

(Note: xx represents a unique 2-digit identifier that the instructor assigns to each student in the class. Use the employees suffixed with the identifier assigned to you (for example Malcolm Aurora 12) throughout the practices to ensure that your configurations do not conflict with those of other participants.)

By the end of the practices, your employees are organized into a single management structure as shown below:

− Malcolm Aurora xx − Mary Martin xx

− Carl Whiteside xx − Helen Carr xx

The practices guide you through a number of intermediate stages, which provide opportunities to examine how a manager’s access to other employees is influenced by profile options, security profiles, and the Release Information function.



Practice - Creating Responsibilities

Overview

In these practices you learn how to control and define user access to self-service functionality. You use standard security functions in the forms interface to carry out the following tasks:

• Create self-service responsibilities for manager and non-manager users

• Create and test new self-service users

• Assign appropriate responsibilities to your new users

Assumptions

• You must have access to an Oracle Application Vision database or comparable training or test instance at your site on which to complete this practice.

• The names used throughout this practice are for the purpose of the practice and bear no resemblance to any particular organization or individuals.

• Prefix all names of responsibilities and users with your assigned unique group number or your initials.

• Unless otherwise indicated, use the System Administrator responsibility.

• The initial password for your users should be Oracle. You should then use Welcome as the active password.

• Unless otherwise indicated, use the Vision Corporation business group.

• To create a new record, select the New Record icon from the toolbar.

• When using a search function, you can use as a wildcard. For example, you can enter %Aur% to display all entries containing the string AUR.

Tasks


Within your enterprise, you have identified three distinct groups of SSHR users; two for managers and one for non-manager employees. You need to define a separate responsibility for each.

Log on as HRMS/welcome and create appropriate responsibilities based on the predefined self-service responsibilities (Manager Self-Service and Employee Self-Service).



Note: The two manager responsibilities are the same apart from their access to granted employees. This will be covered in the next practice, which looks at security profiles.

Create two copies of the Manager Self-Service responsibility using the following names (where xx is your group identifier):

• xxManager Self-Service Granted Access

• xxManager Self-Service No Granted Access

• The details of these responsibilities are shown below:

Responsibility Name xxManager Self-Service Granted Access

Application Human Resources

Responsibility Key xxMGR_SELF_SERVICE_GRANTED

Description xxManager Self-Service Granted Access

Responsibility Name xxManager Self-Service No Granted Access


Responsibility Key xxMGR_SELF_SERVICE_NO_GRANTED

Description xxManager Self-Service No Granted Access

The following information is identical for both responsibilities:

Available From Oracle Self-Service Web Applications

Menu Manager Self-Service

Data Group

Name Standard


Then create a copy of the delivered Employee Self-Service responsibility using the following information:

Responsibility Name xxEmployee Self-Service


Responsibility Key xxEMPLOYEE_SELF_SERVICE

Description xxEmployee Self-Service



Available From Oracle Self-Service Web Applications

Menu Employee Self-Service

Data Group

Name Standard




Solution – Creating Responsibilities


Responsibility = System Administrator

1. Log on to HRMS using HRMS/WELCOME and navigate to the Responsibilities window.

• (N) Security > Responsibility > Define

To create the Manager Self-Service Granted Access responsibility:

2. Initiate a query.

• (M) View > Query by Example > Enter

3. Enter the following string in the Responsibility Name field:

• Manager Self-Service

4. Execute the query.

• (M) View > Query by Example > Run

5. Choose New Record.

6. In the Responsibility Name field, enter xxManager Self-Service Granted Access.

Note: You may find it convenient to use the Shift+F5 key combination in some fields to duplicate the field value from the previous record and then make your changes rather than having to type the entire value.

7. In the Application field, enter Human Resources.

8. In the Responsibility Key field, enter xxMGR_SELF_SERVICE_GRANTED.

9. In the Available From region, select Oracle Self-Service Web Applications.

10. In the Menu field, select Manager Self Service.

11. Move to the Data Group region.

12. In the Name field, enter Standard.


14. Save your work.



To create the Manager Self-Service No Granted Access responsibility:




• Manager Self-Service




19. In the Responsibility Name field, enter xxManager Self-Service No Granted Access.


21. In the Responsibility Key field, enter xxMGR_SELF_SERVICE_NO_GRANTED.


23. In the Menu field, select Manager Self Service.




27. Save your work.

To create the Employee Self-Service responsibility:




• Employee Self-Service






32. In the Responsibility Name field, enter xxEmployee Self-Service.


34. In the Responsibility Key field, enter xxEMPLOYEE_SELF_SERVICE.


36. In the Menu field, select Employee Self Service.




40. Save your work.



Practice - Creating New Users

Overview

• This practice shows you how to create users for SSHR and how to assign the correct responsibilities to them.

Assumptions



• Prefix all names of responsibilities and users with your assigned unique group number or your initials.


• The initial password for your users should be Oracle. You should then use Welcome as the active password.


• To create a new record, select the New Record icon from the toolbar.


Tasks

Create New Users

You need to create users to enable your employees to use the self-service functionality. The employees have different roles within your enterprise so you must ensure that you assign the correct responsibilities are to each user. Since the number of users is small, you will create them manually rather then using the batch creation approach.

Remember to prefix each user name with your unique group number.

The initial password for your users is Oracle.

Log on as HRMS/welcome and create the following users. Link them to your employees as follows:



User Employee Business Group

xxuser1 Aurora, Malcolm xx Vision Corporation

xxuser2 Martin, Mary xx Vision Corporation

xxuser3 Whiteside, Carl xx Vision Corporation

xxuser4 Carr, Helen xx Vision Industries

Assign appropriate responsibilities to your new users to reflect their role within your enterprise. The following table shows suggested responsibilities:

User Responsibility Security Group

xxUSER1 US Super HRMS Manager System Administrator (not Administration) Application Developer Application Developer Common Modules Manager Self-Service xxManager Self-Service Granted Access xxManager Self-Service No Granted Access Employee Self-Service XxEmployee Self-Service Workflow User Web Applications Workflow Administrator Web Applications Functional Administrator Approvals Management Business Analyst

Standard for all responsibilities

xxUSER2 Manager Self-Service xxManager Self-Service Granted Access xxManager Self-Service No Granted Access Employee Self-Service XxEmployee Self-Service Workflow User Web Applications


xxUSER3 Employee Self-Service xxEmployee Self-Service Workflow User Web Applications


xxUSER4 Employee Self-Service XxEmployee Self-Service Workflow User Web Applications




Testing the Users

Make sure that you have assigned the correct responsibilities to your users by logging on to SSHR as one of your users, for example, xxUSER1. The initial password is Oracle. Enter Welcome as the new password.

Check that the responsibilities you defined in the last practice are correct for the user.

Choose the xxManager Self-Service Granted Access responsibility and check that the menu displayed is the same as for the predefined responsibility.

Note: Not all aspects of your custom responsibilities will function properly until additional configuration steps are performed in later practices.

Choose the xxEmployee Self-Service responsibility and check that the menu displayed is the same as for the predefined responsibility.

If required, repeat for xxUSER2, xxUSER3, and xxUSER4.



Solution – Creating New Users

Create New Users

Responsibility = System Administrator, Vision Corporation

1. Navigate to the Users window.

• (N) Security > User > Define

2. Enter the user name as specified in the practice, prefixed with your identifier.

• xxUSER1

3. Enter the password for your user. Use Oracle as the initial password (you will need to enter the password twice).

4. In the Person Field, select the first employee (Aurora, Malcolm xx).

5. Move to the Responsibilities region.

6. Enter the following responsibilities for your first user and choose standard as the Security Group for each responsibility.

− US HRMS Manager − System Administrator − Application Developer − Application Developer Common Modules − Manager Self-Service − xxManager Self-Service Granted Access − xxManager Self-Service No Granted Access − Employee Self-Service − xxEmployee Self-Service − Workflow User Web Applications − Workflow Administrator Web Applications − Functional Administrator − Approvals Management Business Analyst

7. Save your work.

8. Create a new record and repeat steps 2 thru 8 to create the remaining users and assign the responsibilities as follows:

User Employee Responsibilities

Xxuser2 Martin, Mary xx Manager Self-Service xxManager Self-Service Granted Access



xxManager Self-Service No Granted Access Employee Self-Service xxEmployee Self-Service Workflow User Web Applications

Xxuser3 Whiteside, Carl xx Employee Self-Service xxEmployee Self-Service Workflow User Web Applications

Xxuser4 Carr, Helen xx (Vision Industries)

Employee Self-Service xxEmployee Self-Service Workflow User Web Applications

9. Close the window.

Testing the Users

10. Exit Oracle HRMS and log on to SSHR as xxuser1.

11. Enter Oracle as the old password.

12. Enter Welcome in the two New Password fields.

13. Save your changes.

14. Check that the list of responsibilities corresponds to the responsibilities you assigned to the user in the previous practice.

15. Select the xxManager Self-Service Granted Access responsibility.

16. Check that the menu is the same as for the predefined Manager Self-Service responsibility.

17. If required, repeat this procedure to check the responsibilities and menus for your other users.



Batch Creation of User Accounts

Batch Creation of User Accounts

An administrator or implementor uses the following programs in batch creation of user accounts: User Account Employee Extract Process

• Parameters control which employees are included in the current batch Data Pump

• Executes hr_user_acct_api API for each person in the current batch to create / inactivate the person’s user record

• Custom PL/SQL in user hook enforces business rules for user name, responsibility and security profile

Data Pump Exceptions Report • Analyzes errors in the user hook

All these concurrent programs can be run from a Super HRMS Manager responsibility. For more information on these concurrent programs, see the related online documentation under:

• Oracle HRMS > Deploy Oracle Self-Service Human Resources > SSHR User Accounts. User Hooks:



• Create user (for new users) - before process hook (set user name, password (optional), responsibility and security

profile) - after process hook (if password not supplied in before hook, one will be generated

randomly and you will need to use the after hook to communicate this to the user • Update user

(for inactivating terminated users) - before process hook (optional additional validation before the user is inactivated) - after process hook (optional extra processing after the user is inactivated)



Creating User Hooks

Creating User Hooks

The slide above shows the sequence of steps involved in creating a user hook in Oracle HRMS. For more information on User Hooks, please see the online documentation under the following path:

• Applied Technology > Oracle Applications Developer’s Guide • Oracle HRMS Global > HR Information Systems > Deploy SSHR Capability > SSHR and

User Access If you are modifying user hooks, please note the following:

• Do not modify Oracle HRMS tables and data directly using custom code • Do not modify delivered API code • Any code isolated in user hooks is not overwritten during upgrades



Access Roles for Self-Service Transactions

Access Roles for Self-Service Transactions

You use access role to define a user’s access to workflow activities by defining whether a user can enter and approve transaction data routed for approval. You define new roles for your self-service transactions using the Maintain Roles window. Then assign the role to a user in a supervisor hierarchy or to a position in a position hierarchy. You create roles using delivered self-service role types:

• SSHR Update Allowed • SSHR Update Not Allowed

By default, all users can update self-service transactions. If this is correct for the majority of users, it makes sense to create a role with the type SSHR Update Not Allowed and to only assign this role to the users who do not have permission to update self-service transactions.


User Access to People Chapter 7 - Page 1

User Access to People Chapter 7



User Access to People



Security Profiles (Non-Manager)

Security Profiles (Non-Manager)

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



Security Profiles (Manager)

Security Profiles (Manager)

An SSHR implementer or administrator should take care when considering security profiles for manager responsibilities because of the potential for managers to search for and access employees and workers outside their supervisor hierarchy. Options include:

• User-based: list is dynamically generated when the user logs on, starting with the corresponding person record and traversing the supervisory hierarchy. A single security profile of this kind will serve most line managers. Avoid using this for senior employees in the enterprise because of the performance implications of generating a large list.

• Organization hierarchy-based: good for senior employees in the enterprise. Need a separate security profile for each starting point in the organization hierarchy.

• Position hierarchy-based: necessary for position-based enterprises (public sector). However, you need a separate security profile for each starting point in the position hierarchy.

• View all: You can avoid the need to set up multiple security profiles if you also remove the users’ access to the search capabilities. Users will then only have access to their reports via the people tree. However, they will not be able to get to granted information (Release Information).



• For most SSHR managers, the most appropriate security profile is a user-based profile with the Supervisor Hierarchy check box flagged.

For more information about Security Profiles, refer online help: Oracle HRMS Global > HR Information Systems > Security Rules > Security Profiles



Assignment-Based Security

Assignment-Based Security

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

• Provide supervisor assignment information. • Select the Restrict on Individual Assignments option in the Security Profile window. • Define how the supervisor hierarchy is displayed.



Interaction of Security Profiles

Interaction of Security Profiles

This slide describes can use the HR:Restrict Transactions across Business Groups in SSHR profile in conjunction with the HR:Cross Business Group (CBG) profile.

• If CBG is Yes and Restrict Transactions is No, SSHR displays persons from a different business group in the Person Tree but they are greyed out.

- Subordinates in the business group who are below the person in the different business group are displayed and their records can be processed.

• If CBG is No and Restrict Transaction is No, SSHR does not display persons from a different business group in the Person Tree.

Note that the system profile “HR:Restrict Transactions across Business Groups in SSHR” defaults to No at the site level, however, you can override this setting at the responsibility level.



Releasing Information

Releasing Information

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



Hierarchy Page

Hierarchy Page



Guided Demonstration - Hierarchy Page

Responsibility: Manager Self-Service

1. Log on to Oracle SSHR as TBENNETT/welcome.

2. Select the Manager Actions function from the Manager Self-Service responsibility:

• (N) Manager Self-Service > Manager Actions

3. The Hierarchy page appears and shows the direct reports for TBENNETT.

This hierarchy is supervisor based. Alternatively, you can also generate a position-based hierarchy if applicable to your business practices.

Note: To enable a position hierarchy, set the HR: Display Position Hierarchy profile to Yes.

4. Click My List. The display changes to only show those employees who TBENNETT has added to My List.

5. Click on the Action icon. You access available functions for the employee directly using this icon.

6. Select Back to return to My List.

7. Select the Details icon for someone in the list. This displays Person and Assignment information for the selected person.

8. Choose Home to exit the transaction.



Hierarchy

Hierarchy

The Person Tree is usually derived from the supervisor hierarchy (defined by the Restrict by Supervisor checkbox in the Security Profile window). Managers first see an Enter Process page that they can use to perform a basic search for any employee within the underlying security profile. Managers can process employees and workers in the resulting list directly or add them to My List for future reference. Note: You can extend the security profile for managers by enabling the Release Employee Information function. Some functions such as Online Payslip, Appraisals, and Tax Information (US only) enable managers and HR Professionals to search for ex-employees and terminated employees. Note: The Approvals processes are also driven off the supervisor hierarchy.



Search Page

Search Page

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



Person Types

Person Types

Some functions require managers and HR professionals to search for ex-employees and terminated employees. For example,a Payroll Professional may want to access an ex-employee’s payslip or a manager may want to view a terminated employee’s appraisal. The following functions enable you to search for ex-employees and terminated employees:

• Online Payslip • Appraisals • Tax Information (US only)



My List

My List

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



Practice - Hierarchy, Search, and My List

Overview

• When using SSHR, it is important to define how managers can access the information for other employees. In addition, an SSHR administrator or implementer must define security mechanisms to ensure that users cannot access information for unauthorized employees. In these practices, you learn how to enable managers to access the information for other employees and how to ensure that the correct employees are being accessed.

• In these next practices, you learn how a manager can search for employees and how to restrict which employees your managers can access.

Assumptions



• Prefix all names of security profiles with your assigned unique group number or your initials.


• Use the Vision Corporation business group unless otherwise indicated.

• Log on as xxuser1 unless otherwise indicated.

• To create a new record in the Professional Forms Interface, choose the New Record icon from the toolbar.

• To save your work, select either the Save button in SSHR or the Save icon from the toolbar in the Professional Forms Interface.


Tasks

Searching for Employees

Managers who use SSHR to carry out transactions on their employees need to be able to access the information on these employees. Some managers may be able to access the records for all employees in an enterprise whereas others may be restricted. In this first task, your manager has



access to all employees within your enterprise. Log on to SSHR as user1 and select the Manager Self-Service responsibility. Try and search for Helen Carr xx who is from a different business group.

Using My List

If you regularly carry out SSHR transactions on the same people, it is convenient to use the My List functionality to store these people in a list and avoid having to search for them each time.

Add Helen Carr xx to My List and then search for and add the following two employees:

• Mary Martin xx

• Carl Whiteside xx



Solution – Hierarchy, Search, and My List

Searching for Employees

Responsibility = Manager Self-Service

1. Log on to SSHR as xxuser1/welcome.

2. Select the Manager Self-Service responsibility.

3. Select the Manager Actions function.

Note: The People in Hierarchy table should only contain the record for Malcolm Aurora.

4. In the Name field, enter Carr% and choose the Go button.

The results table should include Helen Carr xx.

Using My List

5. Select the record for Helen Carr xx and click Add to My List.

The People in My List page is displayed.

6. Enter Martin% in the Name field at the top of the page and choose Go.

7. Select the record for Mary Martin xx and click Add to My List.

9. Enter Whiteside% in the Name field at the top of the page and choose Go.

10. Select the record for Carl Whiteside xx and click Add to My List.

11. Choose the Home link.



Manager Enter Process Pages



Security Profiles - Considerations

Security Profiles - Considerations

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



Practice - Using Security Profiles

Overview

In these practices you learn how to enable managers to access the information for other employees and how to ensure that the correct employees are being accessed. You use standard security functions in the forms interface to carry out the following tasks:

• Restrict user access to employees using a supervisor profile

• Create security profiles

• Assign security profiles to your users

Assumptions







• To create a new record in the forms interface, choose the New Record icon from the toolbar.


• When using a search function, you can use as a wildcard. For example, you can enter Aur% to display all entries starting with the string AUR.

Tasks

Restrict User Access by Supervisor Hierarchy

Your manager, Malcolm can currently access employees in any business group. However, it is usually the case that managers would only require access to those employees within their



supervisor hierarchy. To restrict access, create a security profile based on the predefined Vision Supervisor Profile and link it to your Manager Self-Service responsibility.

Name the security profile as follows:

• xxSupervisor Profile No Granted Access

Note: Make sure that the profile is supervisor-based and that there is no access to granted employees.

Now create another copy of the predefined Vision Supervisor Profile and rename it as follows:

• xxSupervisor Profile Granted Access

Make sure that this profile is supervisor-based and that is allows access to granted employees.

The business group for both custom security profiles should be Vision Corporation.

Assign the Supervisor Profile

You assign supervisor profiles using the HR: Security Profile using the System Administrator responsibility. Assign the security profiles as follows:

Responsibility HR: Security Profile

xxEmployee Self-Service Vision Corporation

xxManager Self-Service No Granted Access xxSupervisor Profile No Granted Access

xxManager Self-Service Granted Access xxSupervisor Profile Granted Access

Test the Supervisor Profile

In a previous practice, you searched for employees and added them to My List. This was possible because you were using a View All security profile with the Manager Self-Service responsibility.

Now log on as xxuser1 and select the xxManager Self-Service No Granted Access responsibility. Display My List. Try and search for the employees as before (Mary Martin, Helen Carr, and Carl Whiteside.



Solution – Using Security Profiles

Restrict User Access by Supervisor Hierarchy

Responsibility = US Super HRMS Manager

1. In Oracle HRMS, navigate to the Security Profiles window.

• (N) Security > Profile

2. Initiate the query:


3. Enter the following string in the Name field:

• Vision Supervisor Profile



5. Create a new record.

Defining a Supervisor Profile with No Granted Access

6. Name your copied profile as follows:

• xxSupervisor Profile No Granted Access

7. Enter Vision Corporation in the Business Group field.

8. Set the following fields to Restricted: − View Employees − View Contingent Workers − View Applicants − View Contacts

9. Set the following field to None: − View Candidates

10. Make sure that the Allow Granted Users box is not flagged.

11. Navigate to the Supervisor Security tabbed region.

12. Select the Restrict by Supervisor (person-based) box.

13. Save your new security profile.



Defining a Supervisor Profile with Granted Access


15. Name your copied profile as follows:

• xxSupervisor Profile Granted Access

16. Enter Vision Corporation in the Business Group field.

17. Set the following fields to Restricted: − View Employees − View Contingent Workers − View Applicants − View Contacts

18. Make sure that the Allow Granted Users box is flagged.

19. Navigate to the Supervisor Security tabbed region.

20. Select the Restrict by Supervisor (person-based) box.

21. Save your new security profile.

22. Close the form.

Assign the Security Profile


23. Switch your responsibility to the System Administrator responsibility:

• (M) File > Switch responsibility

24. Navigate to the System Profile window.

• (N) Profile > System

25. From the Find System Profile Values window, uncheck the Site checkbox.

Note: This is only a requirement in the classroom.

26. Enter xxManager Self-Service No Granted Access in the Responsibility field.

27. Enter HR: Security Profile in the Profile field.

28. Choose Find.

29. Enter the name of your custom supervisor profile in the Responsibility field.



• xxSupervisor Profile No Granted Access.


31. Choose the Find icon from the toolbar:

The Find System Profile Values window appears.

32. Change the value in the responsibility field to xxManager Self-Service Granted Access.

33. Choose Find.

34. Enter the name of your custom supervisor profile in the Responsibility field.

• xxSupervisor Profile Granted Access.


36. Exit Oracle Applications.

Test the Supervisor Profile

Responsibility = xxManager Self-Service No Granted Access


38. Navigate to the Manager Actions page:

• (M) Manager Actions

39. Click the My List link to display the People in My List page.

The list should be empty.

40. Enter Carr% in the Name field near the top of the page and choose Go.

No records should be returned. This is because the security profile restricts you to only accessing those records in your supervisor hierarchy and no hierarchy has been created yet.

41. Choose Home.



Practice - Release Information Function

Overview

In previous practices, you have restricted your manager’s access to person records based on a security profile. However, in particular situations, it may be necessary for a person to release their personal information to a manager who would not normally have access to the records. In this practice, you learn how to use the Release Information function.

Assumptions







• To create a new record in the forms interface, choose the New Record icon from the toolbar.



Tasks

Release Information Function

SSHR includes the function Release Information which enables users to release their personal information to a specified user, for example, a second manager. In order for this manager to be able to view this released information, he or she must have a supervisor profile which allows access to granted users.

Use the Release Information function as Helen Carr and release your personal information to Malcolm Aurora. Then log on as Malcolm (xxuser1) to see whether you can access Helen’s information.



Solution – Release Information Function

Release Information Function

Responsibility = Employee Self-Service

1. Log on to SSHR as xxuser4.

Note: If you have not already logged on as xxuser4, you will be asked for new passwords. Enter Welcome as the new password.

2. Navigate to the Release Information function:

• (M) Release Information

The Release Information page is displayed.

3. Click on the Search icon next to the Name field.

4. The Search and Select: Name page is displayed.

5. Enter Aurora%xx in the Name field.

6. Choose Go.

7. Choose the Quick Select icon for Aurora, Malcolm XX to return to the Release Information page.

8. Click on the Grant Access button.

The Release Information: Review page is displayed.

9. Check that the data is correct and choose Submit.

10. Choose the Log out link



13. Select the Manager Actions function.

14. Change the Search Criteria to Last Name.

15. Enter Carr% in the Last Name field and choose Go.

You can now select Helen Carr’s record.

16. Choose Home.



Practice - Change Manager Function and Hierarchy Page

Overview

In these practices you learn about the standard entry page for managers using SSHR: the Hierarchy or Person Tree.

If your organization uses supervisor or position hierarchies, you can use this view for your managers.

Assumptions



• Unless otherwise indicated, use the Manager Self-Service responsibility.



Tasks

Using the Change Manager Function to Create a Supervisor Hierarchy

You want to set up a supervisor hierarchy for your employees to ensure that managers can only access those employees for whom they are responsible. Log on as Malcolm and select the delivered Manager Self-Service responsibility. Use the Change Manager function to make Malcolm Aurora the manager of Mary Martin. Make Mary Martin the manager of Helen Carr and Carl Whiteside. The completed hierarchy should be as follows:

Malcolm Aurora

Mary Martin

Helen Carr

Carl Whiteside



Display the Supervisor Hierarchy

Log on to SSHR as xxuser1/welcome and select the xxManager Self-Service Granted Access responsibility. Select the Manager Actions function and check that the supervisor hierarchy is displayed in the People in Hierarchy page.



Solution – Change Manager Function and Hierarchy Page

Using the Change Manager Function

Responsibility = Manager Self-Service, Vision Corporation



3. Select the Change Manager function from the menu.

4. Click the My List link to display your list of people.

5. Select the Action icon for Mary Martin xx.

Select the “Changes should take effect on the effective date as entered below” option.

The Effective Date Options page is displayed.

6. Use today’s date as the Effective Date and choose the Continue button.

7. The Change Manager page appears.

8. Choose the Search icon next to the Manager Name field in the Assign a New Manager region.

Enter Aurora%XX in the Employee Name field. Choose the Go button

Select Aurora, Malcolm XX and choose the Select button

You return to the Change Manager page.

11. Navigate to the Assign New Direct Reports region.

12. Choose the Search icon next to the Worker Name field.

Enter Carr%XX in the Employee Name field. Choose the Go button.

13. Choose the Quick Select icon for Carr, Helen XX..


14. Choose the Add Another Row button to add an additional direct report.

15. Choose the Search icon next to the Worker Name field.

Enter Whiteside%XX in the Employee Name field. Choose the Go button



16. Choose the Quick Select icon for Whiteside, Carl XX.


17. Choose the Next button.

18. When the Review page appears, check that the information is correct.

Note: If there is no next approver, approval is met and the transaction is written to the HR tables. In this case, the user has no supervisor which means that approval is automatic.

19. Choose the Submit button.

20. From the Confirmation page, click the Logout link.

Display the Supervisor Hierarchy

Responsibility = xxManager Self-Service Granted Access


22. Navigate to the Manager Actions page:

• (M) Manager Actions

23. The People in Hierarchy page is displayed and you should be able to expand the hierarchy to see the expected supervisor hierarchy.



Implementation Steps Chapter 8 - Page 1

Implementation Steps Chapter 8



Implementation Steps



Implementation Strategy



Prepare Environment for SSHR

Prepare Environment for SSHR

The required steps are as follows: • Install Oracle Human Resources • Set up Apache Server • Apply latest SSHR patch • Complete install and setup of Oracle Applications Framework (OAF) • Set HR: Self Service HR Licensed system profile • Install Web Browser on every PC • Set up SSHR Background Cleanup Process • Install Workflow Builder as needed • Set access levels for predefined Workflow Item Type • Configure HRMS Applications • Check tools for SSHR Implementation

The above steps also represent the minimum steps that a user has to carry out to be able to run SSHR in a test environment. To be able to test SSHR effectively, implementers should also set



up a business group, set up at least 2 users (one of whom is a supervisor), and assign responsibilities to the users.



Configure HRMS Applications

Configure HRMS Applications

To set up work structures for Oracle HRMS, you carry out the following steps: • Adapt or Create Business Group • Define Organization Structures • Define Key Flexfields, Descriptive Flexfields, EITs, and SITs • Define Lookup Types and Values

- Lookups supply many of the lists of values in Oracle HRMS. They ensure that users enter only valid data into Oracle HRMS.

• Define Currencies For more information, see the Implementation Steps for Oracle HRMS.



User Access Setup

User Access Setup

• Identify target user groups • Set up access roles for Self-Service Actions (optional) • Create user menus • Create self-service responsibilities • Set up eligibility processing for Self-Service Actions (optional) • Configure Person Search • Set up security profiles – considerations

- Type of hierarchy? - Allow granted access?

• Link responsibilities to security profiles • Set the HR:Cross Business Group profile • Set the Allow Granted Access profile • Manually create user accounts • Configure batch creation of user accounts



Configure Workflow Processes and Page Layouts

Configure Workflow Processes and Approvals

When you configure your workflow process, it is advisable to do this for one target group of users. Configure the following:

• Display Enterprise Logo • Define Email Address • Configure Review Page (optional) • Configure Effective Date Options (optional) • Configure National Address Style • Identify and prioritize required Business Flows • Configure the Workflow Process • Configure the Approvals Process • Configure the Workflow Errors Processes • Link Workflow Item Types to Function • Add Sub Menus to Self-service User Menus • Add Functions to User Menus





Once you have configured the steps outlined in the previous slide, configure the following for the target group:

• Set Up User Profile Options • Test the Basic Flow • Configure the Pages for Your Functions and Notifications - When you create custom

functions, you must set the following parameters: - Item Type - Process Name - Called From - OA Func

• Configure Flexfields for the Regions • Create Messages for the Regions • Define the Name Format in Notifications (Optional) • Then repeat for other processes and groups of users.



Migrate Configuration to Test and Production Environments

Migrate Configuration to Test and Production Environments

Use the tools to migrate configuration between environments in the following ways: FNDLOAD

• Functions, Menus, Responsibilities AKLOAD

• Personalizations WFLOAD

• Workflow definitions



Summary


Configuring SSHR Chapter 9 - Page 1

Configuring SSHR Chapter 9



Configuring SSHR



Objectives


Functions, Menus, and Responsibilities Chapter 10 - Page 1

Functions, Menus, and Responsibilities Chapter 10



Functions, Menus and Responsibilities



Functions, Menus, and Responsibilities - Overview

Functions, Menus, and Responsibilities – Overview

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





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



Configuring Menus

Configuring Menus

The above slide shows a typical self-service menu. The Employee Self-Service menu is delivered as a standard menu. However, you may decide that you do not want to use all delivered functions. For example, as shown in the slide above, you may not require the Competence Profile function. In this case, you would either create your own menu in the Menus window or exclude the particular function using the Responsibilities window. You may also want to create your own menus for the following reasons:

• The delivered menus do not contain required functions • The menu sequence/structure is not appropriate for your business requirements • Menu prompts are not appropriate for your business requirements



Menu Types

Menu Types

SSHR uses four types of menu: top-level, submenu, hidden submenus, and data security menus.

• A top-level menu outlines the functions for a responsibility and is the starting point for navigation.

• A submenu with a prompt is visible to the user, and groups together related functions, for example, Professional Details.

• A submenu without a defined prompt is hidden from the user. Functions on these hidden submenus are available to the responsibility for function security without being directly navigable by the user. Hidden submenus determine which functions appear in the Actions pages.

• Data security menus define whether a function is global or legislation-specific. A function must be included in either a global or legislation-specific data security menu before it can be used and displayed. These menus are not displayed to the user.



Top-level Menus



Submenus



Designing Menus



Hidden Submenus

Hidden Submenus

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



Hidden Submenus

Hidden Submenus

This slide illustrates the two ways in SSHR in which hidden menus are referenced by the application:

• The Manager Actions page uses a profile option (set at site or responsibility level) to identify the menu which defines the functions to display on the page.

• The Enter Person Process page uses a region item to identify the menu which defines a hierarchy of tabbed regions (Employees, Hierarchy, My List, Search).

In either case, you must also attach the submenu to the responsibility’s top menu to satisfy function security.



Data Security Menus

Data Security Menus

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



Custom Menus 1

Custom Menus 1

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



Custom Menus 2

Custom Menus 2

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



Practice - Creating Menus

Overview

In these practices you learn how to create your own versions of the delivered self-service menus and functions. By creating your own versions of self-service menus and functions, you can personalize and configure them to suit your business requirements.

In this practice, you become familiar with the different types of menus used in SSHR and understand how to manipulate the menus so that the correct functions are displayed to the correct users. You use standard application development functions in the forms interface to carry out the following tasks:

• Create custom versions of delivered self-service menus

Assumptions



• Prefix all names of menus with your assigned unique group number or your initials.

• Unless otherwise indicated, use the Application Developer responsibility.

• Unless otherwise indicated, log on to Oracle HRMS and SSHR as xxuser1.


• To create a new record in the Professional User Interface, select the New Record icon from the toolbar.


Tasks

Create a Menu

You want to create a custom menu containing a set of functions for a specific group of self-service users. The menu may contain both predefined and custom functions (the custom functions will be defined in subsequent practices).

Create a copy of the Manager Self Service menu using the following attributes:



• Menu Name = xxHR_LINE_MANAGER_ACCESS_V4.0

• User Menu Name = xxManager Self Service

• Description = xxManager Self Service

and attach the following functions:

Seq Prompt Submenu Function or (User Function Name)

Function Name

10 Personal Information

Personal Information HR_PERINFO_SS

20 Personal Information Mgr

Personal Information Mgr

HR_PERINFO_MGR_SS

30 Change Manager

Change Manager Mgr HR_MANAGER_MGR_SS

Enable Search Functions

Although you have attached the Personal Information Mgr function to your new menu, this function will not work unless Search functions are also linked to the menu to enable you to perform transactions on other people. The Search, Person Tree, and My List functions are stored within the Manager Enter Process submenu.

• Add the required submenu to your menu:

Seq Prompt Submenu Menu Name

40 Enter Person Process HR_EPP_MENU

Link Menu to Responsibility

Then, enable the menu by attaching it to your xx Manager Self-Service Granted Access responsibility and xxManager Self-Service No Granted Access responsibility.

Test the Menus

After making these changes, you need to wait for the Apache server to be restarted before you can test your changes.

Then log on to SSHR and xxuser1 and select one of your custom manager responsibilities. Check that the only three available functions are the functions listed above. Also select the Personal Information function and check that the Person Tree is displayed.



Solution – Creating Menus

Creating Menus


1. Log on Oracle HRMS using xxuser1/welcome.

2. Navigate to the Menu window.

• (N) Application > Menu

3. Initiate a query to display the delivered Manager Self Service menu.


4. Enter the following string in the User Menu Name field:

• Manager Self Service




7. In the Menu Name field, enter xxHR_LINE_MANAGER_ACCESS_V4.0.


8. In the User Menu Name field, enter xxManager Self Service.

9. Navigate to the lower half of the screen.

10. Enter the function and submenu information as follows:

Seq Prompt Submenu Function or User

Function Name

10 Personal Information Personal Information

20 Personal Information Mgr Personal Information Mgr

30 Change Manager Mgr Change Manager Mgr



Enable Search Functions

11. Add the following submenu to your menu:

Seq Prompt Submenu Function or User Function Name

40 Manager Enter Process Menu

12. Save your work.


Link Menu to Responsibility

14. Navigate to the Responsibilities window.


15. Initiate a query:



• xxManager Self-Service No Granted Access%



18. Replace the predefined Manager Self Service menu with your custom xxManager Self Service menu in the Menu field.

19. Save your work.




• xxManager Self-Service Granted Access%





23. Replace the predefined Manager Self Service menu with your custom xxManager Self Service menu in the Menu field.

24. Save your work.


Note: you need to wait for the Apache server to be restarted before you can test your changes.

Test the Menus

Responsibility = xxManager Self-Service No Granted Access or xxManager Self-Service Granted Access


27. Check that the menu for your selected responsibility only displays the expected three functions.

28. Select the Personal Information Manager function.

29. Check that the Person Tree/Hierarchy is displayed.

30. Choose Home.



Person Tree Navigation Paths

Person Tree Navigation Paths

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



Actions Menus

Actions Page

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



Employee Actions Page

Employee Actions Page

The navigation path defines the contents of the Employee Actions page. • Navigation Path 1: The manager displays the Person Tree and then chooses a specific

function (by choosing the Manager Actions V4.0 function). The Employee Actions tab displays a context–sensitive list of the functions available for the selected employee. The hidden submenu defined for the HR:Manager Actions Menu profile option determines the contents of the list. The default menu for this profile option is the predefined Personal Actions Menu (HR_LINE_MANAGER_PERS_FUNCTIONS).

• Navigation Path 2: If a manager does not select a person in the Person Tree, the selection defaults to the manager’s own employee record. The list displayed is driven by the hidden submenu for the HR:Personal Actions Menu profile option. The default menu for this profile option is the predefined Manager Actions Menu (HR_LINE_MANAGER_FUNCTIONS).

• The information given above also applies to contingent workers when you use the Contingent Worker Personal Actions Menu function.



Practice - Actions Menus

Overview

This practice shows you how to set up special submenus to control which actions are available in the Manager Actions and Personal Actions pages, and how to add new custom functions to these submenus. The Manager Actions submenu defines the actions available in the Available Actions area of the Perform Action page that is displayed when a manager chooses the Manager Actions function and then selects an employee.

The Personal Actions submenu defines the actions available in the Available Actions area of the Perform Action page. This page is displayed when employees choose the Personal Actions function, or when a manager chooses the Manager Actions function and then selects their own record from the Person Tree.

In this practice, you become familiar with the actions menus used in SSHR and understand how to manipulate these menus so that the correct functions are displayed to the correct users. You use standard application development functions in the Professional User Interface to carry out the following tasks:

• Create custom versions of delivered self-service actions submenus

• Add your submenus to your top-level menu (xxManager Self Service)

• Set profile options for the Actions menus

Assumptions







• To create a new record in the Professional Forms Interface, select the New Record icon from the toolbar.




Tasks

Creating Actions Submenus

To enable the alternative navigation path offered by the Manager Actions and Personal Actions functions, you must create appropriate submenus for storing the Actions functions. As you intend to create your own functions shortly, create your own versions of the Manager Actions submenu and the Personal Actions submenu.

Add the following delivered functions to your menus as shown below:

Menu Functions Function Name

Manager Actions Personal Information HR_PERINFO_SS

Change Manager HR_MANAGER_SS

Personal Actions Personal Information HR_PERINFO_SS

Add Actions Submenus to Top-Level Menu

To enable the Actions functionality, attach your new actions menus to your custom top-level menus.

Also attach the two other functions required for full action functionality: Manager Actions Tree View and Suspended Actions Mgr.

Profile Options for Actions Menus

As you have created your own Actions menus, you need to change the system profiles for the actions menus. Change the values for the HR: Manager Actions Menu and HR: Personal Actions Menu profiles to point to your new Actions menus.

Testing Your Menu

After making these changes, you will need to wait for the Apache server to be restarted before you can test your changes.

When you have finished creating your custom menu, log on to SSHR and check that all required functions are listed in the menu.



Solution – Actions Menus

Creating Actions Menus






3. Enter the predefined Manager Actions Menu in the User Menu Name field.

4. Execute the query:



6. Choose Shift and F5 to copy the values from the previous record.

7. Rename the menu using your group identifier as the prefix.

• Menu Name = xxHR_LINE_MANAGER_FUNCTIONS

• User Menu Name = xxManager Actions Menu

8. Enter the following data:

Seq Prompt Submenu Function (or User

Function Name) Function Name

10 Personal Information Personal Information HR_PERINFO_SS 20 Change Manager Change Manager HR_MANAGER_SS




11. Enter the predefined Personal Actions Menu in the User Menu Name field.






14. Choose Shift and F5 to copy the values from the previous record.

15. Rename the menu using your group identifier as the prefix.

• Menu Name = xxHR_LINE_MANAGER_PERS_FUNC (you will have to shorten the menu name)

• User Menu Name = xxPersonal Actions Menu

16. Enter the following data:

Seq Prompt Submenu Function (or User

Function Name) Function

10 Personal Information Personal Information HR_PERINFO_SS

17. Save your work.

Add Actions Submenus to Top-Level Menu

18. Query your custom top-level menu so that you can link your Actions menus to this menu:


19. Enter your custom top-level menu in the User Menu Name field

• xxManager Self Service



21. Enter the following function information for the menu:

Seq Prompt Submenu Function

50 xxManager Actions Menu

60 xxPersonal Actions Menu

70 Manager Actions

Manager Actions Tree View

80 Suspended Actions

Suspended Actions Mgr



22. Save your work.


Profile Options for Actions Menus

24. Navigate to the System Profile Values window.


25. From the Find System Profile Values window, uncheck the Site checkbox

26. Enter xxManager Self-Service Granted Access in the Responsibility field.

27. Enter HR:% Actions Menu in the Profile field.

28. Choose the Find button.

29. In the column for your custom responsibility, change the value of the HR:Manager Actions Menu profile to xxManager Actions Menu.

30. In the column for your custom responsibility, change the value of the HR:Personal Actions Menu profile to xxPersonal Actions Menu.

Save your changes.

31. Choose the Find icon from the toolbar.

32. Change the value in the Responsibility field to xxManager Self-Service No Granted Access.

33. Enter HR:% Actions Menu in the Profile field.


35. In the column for your custom responsibility, change the value of the HR:Manager Actions Menu profile to xxManager Actions Menu.

36. In the column for your custom responsibility, change the value of the HR:Personal Actions Menu profile to xxPersonal Actions Menu.


38. Exit Oracle Applications.

Note: You may need to ask your instructor to restart the Apache server. When ready, test your changes.

Test the Menus





41. Select the Manager Actions function from the menu

41. Select the Action icon for Mary Martin.

42. Choose Continue.

43. Check that the Available Actions region contains the Personal Information and Change Manager functions.



Configuring Functions Chapter 11 - Page 1

Configuring Functions Chapter 11



Configuring Functions



Non-Manager versus Manager Functions

Non-Manager versus Manager Functions

Functions are available to employees/workers or managers, or both. In addition to manager functions, managers also have access to the Person Search capabilities so that they can search for the employee for whom the transaction is to be performed.



Considerations



Copying Delivered Functions


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





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



Practice - Configuring Functions

Overview

In these practices you learn how to create your own versions of the delivered self-service functions and add them to menus so that they are available for self-service users. You will use standard functionality in the forms interface to carry out the following tasks:

• Create custom versions of delivered self-service functions

Assumptions



• Prefix all names of functions with your assigned unique group number or your initials.




• To save your work in the Professional User Interface, select the Save icon from the toolbar.


Tasks

Copying Self-Service Functions

You want to modify a predefined function to suit your business requirements. You want to link a self-service function to a new workflow process (to be created in a subsequent practice). However, since any changes to delivered functions would be overwritten in an SSHR upgrade, it is necessary to create your own function.

Log on as xxuser1 and use the System Administrator responsibility to create copies of the Personal Information (HR_PERINFO_SS) and Personal Information Mgr (HR_PERINFO_MGR_SS) functions.



When you create copies of the Personal Information and Personal Information Mgr functions, change the following function parameters to point to your new functions and new workflow process (to be created in a subsequent practice):

Note: All other parameter values should remain the same.

Function Parameter Value

Personal Information Form > pCalledFrom New function code (xxHR_PERINFO_SS)

Form> pProcessName New process to be created in subsequent practice (xxHR_PERSONAL_INFO_JSP_PRC)

Form> pItemType New item type to be created in subsequent practice (xxHRSSA)

Web HTML > OAFunc New function code (xxHR_PERINFO_SS)

Personal Information Manager

pCalledFrom New function code (xxHR_PERINFO_SS)

HTML Call Copy values from delivered function (Shift and F5)



Solution – Configuring Functions

Copying Self-Service Functions

Responsibility = Application Developer

1. Log on to Oracle HRMS using xxuser1/welcome.

2. Navigate to the Form Functions window.:

• (N) Application > Function



4. Enter the following string in the Function field: − HR_PERINFO_SS



6. HR_PERINFO_SS corresponds to the Personal Information item on the Employee Self Service menu.


8. In the Function Name field, enter xxHR_PERINFO_SS.


9. In the User Function Name field, enter xxPersonal Information.

10. Display the Properties tabbed region.

11. In the Type field, select SSWA jsp function.

12. Display the Form tabbed region.

13. Click on the Parameter field and duplicate the value from the field above. (To duplicate a field, choose Shift and F5.)

14. Choose the Edit Field icon to display the value of the field.



15. Change the value of the pCalledFrom parameter from HR_PERINFO_SS to xxHR_PERINFO_SS.

16. Choose OK to close the window.

17. Choose the Web HTML tabbed region.

18. Click on the HTML Call field and duplicate the values from the field above (To duplicate a field, choose Shift and F5.).

19. Choose the Edit Field icon to display the value of the field.

20. Change the value of the OAFunc parameter from HR_PERINFO_SS to xxHR_PERINFO_SS.

21. Choose OK.

22. Save your work.

23. Return to the Description tab.

24. Initiate a query


26. Enter the following string in the Function field:

• HR_PERINFO_MGR_SS



30. Place your cursor on the record for HR_PERINFO_MGR_SS.

31. Create a new record and copy the field values from the record above. Prefix the values in the Function Name and User Function Name fields with your group identifier.

− xxHR_PERINFO_MGR_SS − xxPersonal Information Manager

32. Display the Properties tabbed region.

33. In the type field, select SSWA jsp function.

34. Display the Form tabbed region.

35. Click on the Parameter field and duplicate the value from the field above (To duplicate a field, choose Shift and F5.).

36. Edit the contents of the field.



37. Change the value of the pCalledFrom parameter from HR_PERINFO_SS to xxHR_PERINFO_SS.

38. Choose OK.

39. Display the Web HTML tabbed region.

40. Click on the HTML Call field and duplicate the values from the field above (To duplicate a field, choose Shift and F5.).

41. Save your work.

42. Close the form.



Adding Custom Functions to Menus


Copy the delivered top-level menu and Personal/Manager Actions submenus.





Add the function to your version of the top-level menu and the Personal/Manager Actions submenu.



Data Security Menus: Restricting Functions by Legislation Code

Data Security Menus: Restricting Functions by Legislation Code

In this example, menus include global functions plus functions for the US and Canada. The Actions menu contains all functions for all legislations (1 - 6). The global data security menu contains only the functions valid for all legislations: for example, Personal Information (1, 2, 3). The data security menus for the US and Canada contain only the functions valid for those legislations (4, 5 for the US and 6 for Canada). When a US SSHR displays the Actions page, the functions that appear are:

• All the global functions (defined by the global data security menu) • The US-specific functions (defined by the US data security menu)



Adding Custom Functions

Adding Custom Functions

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



Data Security Menus

Data Security Menus

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





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





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



Practice - Adding Functions to Menus

Overview

In these practices you learn how to add your custom functions to the correct menus so that they are available for self-service users. You will use standard functionality in the forms interface to carry out the following tasks using the Menus window:

• Add the functions to the top-level menus

• Add the functions to the data security menus

• Add the functions to the Actions menus

Assumptions



• Prefix all names of functions with your assigned unique group number or your initials.




• To save your work in the Professional User Interface, select the Save icon from the toolbar.

• When using a search function, you can use as a wildcard. For example, you can enter Aur% to display all entries containing the string AUR.

Tasks

Add Custom Functions to User Menus

To enable a self-service user to access your custom functions, you must add them to your top-level menus for SSHR. This means that your functions can be displayed in the self-service menu.



Add Custom Functions to Data Security Menus

SSHR uses several data security menus to determine whether a function is available globally or for specific legislations. In this case, the functions are global (in other words, not valid for a specific legislation) so add the functions to the global data security menu.

Add Custom Functions to Action Menus

To enable your SSHR users to use the Manager and Personal Actions functionality, you must add your function to the Manager Actions and Personal Actions menus.

Test Your Function

After carrying out the above steps, log on to SSHR and test your functions. Check that the menu contains the correct functions and then select the xxPersonal Information function.



Solution – Adding Functions to Menus

Add Custom Functions to User Menus



Initiate a query:



xxManager Self Service (where xx is your group identifier)



4. Enter the following functions by creating new records:

Seq Prompt Function

90 xxPersonal Information xxPersonal Information

100 xxPersonal Information Mgr xxPersonal Information Mgr

5. Save your work.

Add Custom Functions to Data Security Menus

6. Initiate a query to display the global data security menu:


7. Enter the following string in the Menu field:

• HR_GLOBAL_SS_FUNCTIONS_CUSTOM



9. Enter the functions as follows by creating new records in the function area:

Note: Since this is shared menu you should take care to use sequence numbers that are unique, for example, by prefixing them with your standard prefix.



Seq Prompt Function

xx1 xxPersonal Information

10. Save your work.

Add Custom Functions to Actions Menus

11. Initiate a query to display your custom Manager Actions Menu.



• xxManager Actions Menu



14. Enter the functions as follows by creating new records in the function area:

Prompt Function

xxPersonal Information V4.0 xxPersonal Information

15. Save your work.

16. Place your cursor on the Menu field.

17. Initiate a query to display your custom Personal Actions Menu.


Enter the following string in the User Menu Name field:

• xxPersonal Actions Menu

Execute the query.


Enter the functions as follows by creating new records in the function area:

Prompt Function

xxPersonal Information V4.0 xxPersonal Information



18. Save your work.


20. Ask your instructor to restart the Apache server. When ready, test your changes.

Optional Steps: Test Your Changes


22. Check that the menu contains your 2 custom functions: xxPersonal Information and xxPersonal Information Mgr.

23. Select the xxPersonal Information function from the menu.




Changing the Manager Entry Pages

Manager Enter Process Pages

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

• HR_PERSON_SEARCH_TOP_SS for Person Search • HR_MY_LIST_TOP_SS for My List

You can also extend the personalization options to enable users to personalize common pages in manager process flows, for example, the Effective Date page and the Hierarchy page. To enable this capability, you must change the OA Func parameter information for the manager function in the process flow to point to the corresponding manager function instead of the non-manager function, for example:

• Previous parameter information for Change Job Mgr function: OA Func = HR_CHANGE_JOB_SS

• New parameter information for Change Job Mgr function: OA Func = HR_CHANGE_JOB_MGR_SS



Practice - Changing Manager Entry Page

Overview

As standard, all manager functions use the Hierarchy or Tree View as the initial entry page. When a manager selects a function, the Hierarchy page appears and the manager can select the individual for the transaction.

However, it may be more appropriate for your managers to use the My List page or the Search page first, particularly if your organization does not use a supervisor hierarchy, for example.

In this practice, you learn how to change function parameters so that the initial page for one custom function is the My List page and for another is the Search page.

Assumptions









Tasks

Create a Function with Search as Initial Page

You want to create a version of the Personal Information Mgr function (HR_PERINFO_MGR_SS) for which the initial page for managers is the Search page.

Create a version of the Personal Information Mgr function (name it xxPersonal Information Mgr Search with the function name xxHR_PERINFO_MGR_SEARCH) and change the akRegionCode parameter in the Web HTML tab to HR_PERSON_SEARCH_TOP_SS.



Create a Function with My List as Initial Page

You want to create a version of the Personal Information Mgr function (HR_PERINFO_MGR_SS) for which the initial page for managers is the My List page.

Create a version of the Personal Information Mgr function (name it xxPersonal Information Mgr My List with the function name xxHR_PERINFO_MGR_LIST) and change the akRegionCode parameter in the Web HTML tab to HR_MY_LIST_TOP_SS.

Add Functions to Menus

Add your new functions to the following menus: − xxManager Self Service − Global Self Service Functions Custom (Global

HR_GLOBAL_SS_FUNCTIONS_CUSTOM)



Solution – Changing Manager Entry Page

Create a Function with Search as Initial Page



2. Navigate to the Form Functions window.


3. Initiate a query to display the delivered Personal Information Mgr function.







7. In the Function Name field, enter xx HR_PERINFO_MGR_SEARCH.

8. In the User Function Name field, enter xxPersonal Information Mgr Search.

9. Click the Properties tab.


11. Click the Form tab.

12. In the Parameters field, use Shift and F5 to copy the values from the delivered function.

13. Click the Web HTML tab.

14. In the HTML call field, use Shift and F5 to copy the values from the delivered function.

15. Choose Edit field from the toolbar.

16. Change the value for the akRegionCode parameter to HR_PERSON_SEARCH_TOP_SS.

17. Close the Editor window.

18. Save your work.



Create a Function with My List as Initial Page



20. Navigate to the Form Functions window.


21. Initiate a query to display the delivered Personal Information Mgr function.







25. In the Function Name field, enter xxHR_PERINFO_MGR_LIST.

26. In the User Function Name field, enter xxPersonal Information Mgr List.

27. Click the Properties tab.


29. Click the Form tab.

30. In the Parameters field, use Shift and F5 to copy the values from the delivered function.

31. Click the Web HTML tab.

32. In the HTML call field, use Shift and F5 to copy the values from the delivered function.

33. Choose Edit field from the toolbar.

34. Change the value for the akRegionCode parameter to HR_MY_LIST_TOP_SS.

35. Close the Editor window.

36. Save your work.



Add Functions to Menus

37. Navigate to the Menus window:


38. Query the following string in the User Menu Name field:

xxManager Self Service (where xx is your group identifier)

• (N) View > Query by Example > Enter


• (N) View > Query by Example > Run

40. Add the following new functions to your menu: 110 xxPersonal Information Mgr

Search xxPersonal Information Mgr Search

120 xxPersonal Information Mgr List

xxPersonal Information Mgr List

41. Save your work.

42. Query the following string in the User Menu Name field:

Global Self Service Functions Custom

• (N) View > Query by Example > Enter


• (N) View > Query by Example > Run

44. Add the following new functions to the menu: xx2 xxPersonal Information Search xxPersonal Information Mgr

Search

xx3 xxPersonal Information List xxPersonal Information Mgr List

45. Save your work.



Test the Changes



47. Check that the new functions are displayed in the menu.

48. Select the xxPersonal Information Mgr Search function and check that the Search page is displayed.

49. Select the xxPersonal Information Mgr List function and check that the My List page is displayed.


Using the Workflow Builder Chapter 12 - Page 1

Using the Workflow Builder Chapter 12



Using the Workflow Builder



Workflow-Enabled SSHR Functions

Workflow-Enabled SSHR Functions

Functions are generally workflow-enabled if they require approvals.



Workflow Builder

Workflow Builder

In Oracle Workflow, all processes are associated with an item type. An item type can include one or more processes and related objects, such as item attributes, functions, and messages. An item type is a way of grouping together related items. Oracle SSHR delivers a number of predefined workflow item types containing workflow processes that you can work with.

• HR (HRSSA) (displayed in the slide above) • HR Self-Service Benefits



Working with the Workflow Builder

Working with the Workflow Builder

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



Working with Workflow Item Types

Working with Workflow Item Types

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



Workflow Access Levels

Workflow Access Levels

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



Configurable and Locked Workflow Objects



Practice - Working with the Workflow Builder

Overview

In this practice, you learn how to use the Workflow Builder to copy a delivered item type and then use this item type for all subsequent tasks.

Note: In practice, you would make changes to the delivered item type. Access level features ensure that customizations are retained.

Assumptions



• Prefix all names of workflow processes and activities with your assigned unique group number or your initials.


• You will test the modified workflow process in a later practice in conjunction with creating a new function.


Tasks

Copy a Delivered Workflow Item Type

You need to make some changes to the delivered workflow processes to meet your business needs. Instead of changing the delivered workflow definition, make a copy of the process.

Open the Workflow Builder as directed by the instructor. Change your access level to 100 and uncheck the “Allow modifications of customized objects” box. Now load the HRMS Self-Service item up to the database and save it as a datastore to E:\Oracle\wf\Data\US\xxSSHR.wft.



Solution – Working with the Workflow Builder

Copy a Delivered Item Type

1. Open Workflow Builder using the information given to you by the instructor.

2. Select Help > About Oracle Workflow Builder 2.6 and set your access level to 100. Uncheck the box “Allow modifications of customized objects”.

3. Select File > Open.

4. Select Database.

5. Enter APPS in the User field.

6. Enter the password provided by your instructor in the Password field.

7. Enter the Connect string provided to you by the instructor.

8. Select the HR item type on the right of the Show Item Types window and click the << (Show) button.

9. Click OK to load the HR item type from the database into Workflow Builder. This step may take a few minutes.

10. To save the item type as a datastore, choose File > Save As.

11. Save your file to directory E:\xxSSHR.wft. This master item type will be a basis for all labs wherever possible.

Note: Some warnings will be displayed at this point.

12. Choose the Save button.

13. Click the + (expand) icon to expand the datastore. Expand the HR item type and then expand the Attributes and Processes nodes beneath. Note that a red bar appears across the lower right corner of the icons representing most attributes and all processes. The red bar indicates that you cannot make changes to these objects directly.

14. You can now create your own item type by copying from the predefined HR item type.

Note: In a real implementation, you would not need to copy the entire item type but would instead copy individual processes as needed. However, this approach does not work well I a classroom environment where many people are trying to save workflow definitions to the same item type at the same time. Instead, for the purposes of the class, each student will work on their own copy of the seeded item type.



15. Click the HR item type and copy and paste it back into the datastore xxSSHR.wft. The property sheet window will appear for the new item type.

16. Replace the Internal Name with xxHRSSA.

17. Replace the Display Name with xxHR.

18. Click OK to close this window.

Note: At this point, Workflow Builder will attempt to populate your new item type with copies of every object contained within the original HRSSA item type. This process will succeed for all objects except the Lookup Types, which must be unique across all item types in the datastore. For each lookup type in turn, Workflow Builder will prompt you to either provide a new unique name (in which case it will create a local copy of the new lookup type), or to cancel the copy (in which case, objects in the new item type will reference the original lookup type in the HRSSA item type). We do NOT want to have copies of the lookup types.

19. Click the Cancel button for each one of the Lookup Types.

20. To save your changes to the datastore, choose File > Save.

Note: Some warning messages will be displayed.

You have successfully created a master copy of the predefined item type. This copy will be used as a basis for subsequent practices wherever possible.

21. To close the datastore, choose File > Close Store.

To save your changes to the database:

22. To FTP files:

1. Launch psftp.exe

psftp: no hostname specified; use “open host.name” to connect

psftp>open esNNNN.us.oracle.com

login as:user1

[email protected]’s password: oracle

lcd e:\

New local directory is e:\

put xxSSHR.wft

local:xxSSHR.wft=>remote:/home/user1/xxSSHR.wft



2. Wait until the cursor returns with psftp>

Note: This may take about 5 minutes, depending on network traffic.

3. DO NOT close the psftp session.

23. To execute WFLOAD:

Launch putty.exe

In the Host Name field, enter esnnnn.oracle.com

Choose the Open button

Login as user0117/oracle or user0118/oracle

If you are asked about storing a key, choose Yes.

ls –1 (this is to make sure that .wft files are FTPed)

Verify that the size of the file is approximately 5027098+ for xxSSHR.wft and 5064014 for xxLAB.wft

Note: Repeat step 5 until the file size is constant.

WFLOAD apps/apps O Y UPGRADE workflow_file.wft

There will be GOOD error messages for item types WFSTD, HRSSA etc, these objects are protected and cannot be saved to the database.

• Uploaded 1 ITEM_TYPE record(s) to database

• Uploaded 0 LOOKUP_TYPE record(s) to database

• Uploaded 149 MESSAGE record(s) to database

• Uploaded 509 ACTIVITY record(s) to database

• Uploaded 0 ROLE record(s) to database

Close the putty session.

24. You are now ready to proceed to changing a process flow.

To Verify Workflow Definition




26. Select the Workflow Administrator Web Applications, Standard responsibility.

27. Choose Developer Studio link.

28. Choose your item type, xxHR, in the Workflow Type field.



Changing Workflow Objects

Changing Workflow Objects

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



Practice - Changing a Process Flow

Overview

In these practices you learn how to change workflow processes to suit the particular requirements of your enterprise.

Note: For the purpose of these practices, you work with a copy of the item type, however, you would usually work directly with the item type. Your changes are protected using access levels.

You need to collect additional information on your employees and decide to include a Special Information Type (SIT) page in your Personal Information process to gather this information.

Assumptions



• Prefix all names of workflow processes and activities with your assigned unique group number or your initials.


• You will test the modified workflow process in a later practice in conjunction with creating a new function.


Tasks

Copy a Process Flow

You want to modify the Personal Information V5 and Process Basic Details workflow objects so that you can add in an additional SIT page. First create copies of the following delivered processes:

• Personal Information (internal name is HR_PERSONAL_INFO_JSP_PRC)

• Process Personal Information V4.0 (internal name is HR_PROCESS_PERINFO_JSP_PRC)

• Process Basic Details (internal name is HR_PROCESS_BASIC_DET_JSP_PRC)



Then, replace the delivered processes with your copied processes. Make sure that you replace the transitions as in the original workflow objects.

Adding New Functions to a Process

You need to collect additional information on your employees and decide to include a Special Information Type (SIT) page in your Personal Information process to gather this information. Add the Special Information Type (SIT) page after the Basic Details page in the Process Personal Information process. Save your changes to the database.



Solution – Changing a Process Flow

Copy a Process Flow

1. Open Windows NT Explorer.

2. Copy E:\Oracle\Data\xxSSHR.wft into E:\Oracle\wf\Data\US\xxLAB.wft.

3. Open the Workflow Builder using information given to you by the instructor.

4. Select File > Open.

5. Choose Browse.

6. Search for E:\Oracle\wf\Data\US\xxLAB.wft.

7. Choose Open.

8. Click xxLAB to expand the datastore.

9. Click xxHR to expand the item type.

10. Click the Processes to expand them.

11. Use the left mouse button to drag the Personal Information process (with an internal name of HR_PERSONAL_INFO_JSP_PRC) to the Processes hierarchy. A window will open to let you modify the properties for the process.

12. Prefix the Internal Name, Display Name, and Description with your group identifier. − XxHR_PERSONAL_INFO_JSP_PRC − XxPersonal Information V5.0 − XxPersonal Information V5.0

13. Choose OK.

14. Use the left mouse button to drag the Process Personal Information process (with an internal name of HR_PERSONAL_INFO_JSP_PRC) to the Processes hierarchy. A window will open to let you modify the properties for the process.

15. Prefix the Internal Name, Display Name, and Description with your group identifier: − xxHR_PROCESS_PERINFO_JSP_PRC − xxProcess Personal Information V5.0 − xxProcess Personal Information V5.0

16. Choose OK.

17. Use the left mouse button to drag the Process Basic Details process to the Processes hierarchy. A window will open to let you modify the properties for the process.



18. Prefix the Internal Name, Display Name, and Description with your group identifier. − XxHR_PROCESS_BASIC_DET_JSP_PRC − XxProcess Basic Details V5.0 − XxProcess Basic Details V5.0

19. Choose OK to close the window.

20. Double-click xxPersonal InformationV5.0 process to open the Diagrammer window.

21. Drag your xxProcess Basic Details V5.0 process from the Navigator window to the Diagrammer and drop it near to the delivered Process Basic Details process.

22. Reproduce the transitions so that your xxProcess Basic Details V5.0 process replaces the original Process Basic Details process.

Note:To create a transition, place your cursor on the object representing the start of the transition. Click and hold the right mouse button to draw a line to the object representing the end of the transition.

23. Delete the delivered Process Basic Details process from within the xxPersonal Information process.

Note: To delete a process, place your cursor on the process and choose Delete Selection from the toolbar.

24. Your workflow diagram should appear as follows:



25. Double-click the xxProcess Basic Details V5.0 process to open up the process.

Adding New Functions to Workflow Process

26. Drag the following functions from the Navigator window to your xxProcess Basic Details process:

− SIT V4.0 − SIT Update V4.0

27. Link these functions as shown in the diagram below:



28. Place your cursor on the SIT V4.0 function.

29. Right click to display the function properties.

30. Display the Node Attributes tabbed region.

31. Place your cursor on the HR Activity Type Value attribute.

32. Check that the entry in the Constant Value field is HR_PERSON_SIT_TOP_SS.

33. Place your cursor on the HR Review Region Item attribute.

34. Check that the entry in the Constant Value field is HR_PERSON_SIT_TOP_SS.

Note: The attribute settings for the SIT functions may already be set correctly but the participants should still check the values.

35. Choose OK.

36. Save your changes to the datastore.

37. Save your changes to the database. Follow the steps listed in the previous task to ftp the wft file to the server and load using WFLOAD.



Changing the Function item type and process name parameters

38. Log on to Oracle HRMS as xxuser1/welcome

39. Navigate to the Form Function window using System Administrator responsibility:


40. Initiate a query


41. Enter the following string in the User Function Name field:

• - xxPersonal Information



43. Display the Form tabbed region

44. Choose the Edit Field icon to display the value of the Parameter field

45. Change the value of the pProcessName parameter from HR_PERSONAL_INFO_JSP_PRC to xxHR_PERSONAL_INFO_JSP_PRC

46. Change the calue of pItemType parameter from HRSSA to xxHRSSA.

47. Choose OK

48. Save your changes

49. Close the form

50. Exit Oracle Applications

51. Ask your instructor to restart the Apache server. When ready, test your changes.

Optional Steps: Testing Your Changes

52. Log on to Oracle SSHR as xxuser1.

53. Select the xxManager Self-Service Granted Access responsibility and then the xxPersonal Information function.

54. Choose the Update button in the Basic Details region

55. Choose ‘Correct or complete the current details’ radio button.



56. Choose the Next button

57. Enter a value in the Preferred Name field.

58. Choose the Next button

• The Special Information Type segments are displayed




Chaining Workflow Processes



Chaining Self-Service Activities

Chaining Self-Service Activities

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



Manage Employment Events – Activities



Manage Employment Events – Activities



Sequencing Restrictions for Manage Employment Event Pages



Applying a Patch

Applying a Patch

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


Configuring Web Page Layouts Chapter 13 - Page 1

Configuring Web Page Layouts Chapter 13



Configuring Web Page Layouts



Configuring Self-Service Web Pages

Configuring Self-Service Web Pages

This sample web page shows which elements an administrator can configure. Note: Configure the buttons such as Update and Add by selecting the Advanced Settings button in the Oracle Applications Framework (OAF).



Oracle Applications Framework

Oracle Applications Framework

You use the Oracle Applications Framework (OAF) to configure web pages for distinct audiences. For example, you can create one set of personalizations for a line manager and one set for an employee. Alternatively, you may personalize a self-service page differently for localizations, organizations, and sites. To enable this flexibility, the OA Framework provides two levels of personalization privileges:

• Administrator level - administrators can choose to create personalizations at a number of different levels, for example, at the responsibility, site, or function level. These levels are arranged in a hierarchy where lower level personalizations take precedence over higher level personalizations.

• End-user level - users can create personalizations for specific regions and items, for example, a user can hide or display particular columns in a table. A user can also personalize a portlet to hide or display particular information. User personalizations are only seen by the creating user.



Personalization Levels

Personalization Levels

The Oracle Applications Framework creates configurations to suit the requirements of different users. The Framework uses personalization levels which enable the implementation team to target the personalizations at specific users. For additional information, see the OA Customization Framework document on Metalink (Document ID 236618.1). Only administrators with the correct authorization can create administration-level configurations (administrators can assign authorization using a profile option at responsibility level). The Site level refers to an installation of Oracle HRMS. The Organization level refers to an organization or business group. Personalizations will affect all users within the organization. Personalizations made at lower levels (user and portlet level) always override configurations made at higher levels. User-level configurations can only be modified by the user who created them.



Profile Options for Oracle Applications Framework

Profile Options for Personalization Framework

Personalize Self-Service Defn (FND_CUSTOM_OA_DEFINITION) • Set to Yes or No at the user or responsibility level • Displays Personalize Page links on web pages • Default is No

FND: Personalization Region Link Enabled (FND_PERSONALIZATION_REGION_LINK_ENABLED)

• Set to Yes or No at Site, Application, Responsibility, User • Displays Personalize Region links in web page regions • Default is No

Disable Self-Service Personal (FND_DISABLE_OA_CUSTOMIZATIONS)

• Set to Yes or No at the site, application, or user level • If set to Yes, any configurations are suppressed regardless of level • Useful when debugging



• Default is No Note that prior to Framework version 5.6D, the profile options were

• Customize Self-Service Defn • Disable Self-Service Custom



Personalization - Buttons and Links

Personalize Region – Buttons and Links

If you set the Personalize Self-Service Defn profile option to Yes, the Personalize Page link is displayed in the global tool bar. If you also set the FND: Personalize Region Link Enabled profile option set to Yes, you also see a Personalize Region link in each region..

• Clicking on the Personalize Region in a specific region allows personalization of that region.

• Clicking on the global Personalize Page button allows the SSHR user or administrator to navigate to any of the regions included in the current page.



Configuration Options within the Oracle Applications Framework



Practice - Configuring Web Page Layouts

Overview

In these practices you learn how to use the Personalization Framework to change the layout of your SSHR web pages. You learn about the different levels of personalization and practice personalizing various elements on the web pages.

You use the Personalization Framework to carry out the following tasks:

• Change a page layout by changing field names and hiding fields

• Use the Global personalization button

• Add and modify user tips and instructions

Note: You enable the personalization functions using a profile option

Assumptions



• Prefix all names of messages and instructions with your assigned unique group number or your initials.

• Unless otherwise indicated, log on to SSHR and HRMS as user1.



Tasks

Enable Personalization

You discover that you need to make certain changes to the web pages used in SSHR. Before you can personalize the pages, you need to enable the Personalization Framework functionality using a profile option.

Use the System Administrator responsibility to set the following profile options so that Malcolm Aurora (xxuser1) can access the Personalization Framework:

− Personalize Self-Service Defn



− FND: Personalization Region Link Enabled

Change Field Labels and Hide Fields

The predefined Personal Information page includes the fields Employee Number and Social Security Number. At your enterprise, however, the Employee Number is known as the Badge Number and the Social Security Number is not required.

Log on to SSHR as xxuser1/welcome and make the following function-level personalizations for the xxPersonal Information function (select the xxPersonal Information function from the menu):

− Change the field label for the Employee Number to Badge Number. − Hide the Social Security field for the Basic Details region.

Then, to check whether the fields are used anywhere else, work through the Personal Information function as if you were changing the Basic Details. Make the same changes in any other region.



Solution – Configuring Web Page Layouts

Enable Personalization



2. Navigate to the System Profile Values window using the System Administrator responsibility.


3. Make sure that the User, and Profiles with No Values boxes are selected.

4. Enter xxuser1 in the User field.

5. Enter Personalize Self-Service Defn in the Profile field.


7. Enter Yes as the value in the User field.


9. Choose Find:

• (M) View > Find

10. Enter FND: Personalization Region Link Enabled in the Profile field.


12. Check that the value in the Site field is No.

13. Enter Yes as the value in the User field.



Change Field Labels and Hiding Fields


16. Switch to the xxManager Self-Service Granted Access responsibility:

• (M) File > Switch responsibility




18. Select one of your employees and click Action. The Personal Information page is displayed.

19. Click the Personalize Region link for the Basic Details Overview region.

20. Click Choose Context.

21. Check that the Scope field contains Region: Basic Details.

22. Check that the Function field contains the name of your function (xxPersonal Information).

23. Check that the Responsibility field contains the name of your responsibility (xxManager Self-Service Granted Access).

24. Choose Apply to continue to the next page.

The Personalize Region page appears.

To change a field label

25. Expand the Personalization Structure if necessary.

26. Navigate to the row containing Message Styled Text: Employee Number.

27. Click the Personalize icon (Pencil) to display the Personalization Properties page.

28. Find the Prompt row and change the value in the Function: xxPersonal Information column from Inherit to Badge Number.

29. Use the Tab button to move out of the field.

30. Choose Apply to submit the personalization.

To hide a field

31. Navigate to the row containing Message Styled Text: Social Security Number.


33. Find the Rendered row and change the value in the Function: xxPersonal Information column from Inherit to False.



The Personalization Structure page appears.

36. Click on the Return to Application link.



37. Check that the Social Security field is no longer displayed and that the Employee Number field has been renamed as Badge Number.

Check for Other Occurrences of Fields in Transaction

38. To check whether these fields are used anywhere else in the xxPersonal Information function, work through a transaction as if you were updating Basic Information.

Note: You should still be in the Basic Details region of the Personal Information function.

39. Choose the Update button in the Basic Details region to make a change to personal information.

40. With the “Enter new information because of a real change to the current details” option selected, choose the Next button.

The Basic Details: Update Information page appears. The Employee Number field also appears in the Other region of this page.

Select the Personalize Other link.


42. Check that the Scope field contains Region: Basic Detail Update Other Entry




The Personalization Region: Basic Detail Update Other Entry page appears.







The Personalization Region: Basic Detail Update Other Entry page appears.



Click the Return to Application link.

Check that the Employee Number field has been renamed to Badge Number.

53. Make any change, for example, change the Marital Status – this change will not be submitted to the database, it is simply for testing.

54. Click the Next button to continue to the Review page.

Check Review Page

Note that the Basic Details fields also appear on the Review page. You also need to make the changes here.

Note: The Employee Number field may not always appear.

55. Click the Personalize Summary Region link


57. Check that the Scope field contains Region: Summary Region.




The Personalization Region: Basic Details page appears.







67. Navigate to the row containing Message Styled Text: Social Security Number.


69. Find the Rendered row and change the value in the Function: xxPersonal Information column from Inherit to False.





72. The Personalize Region: Basic Details page appears.

73. Click the Return to Application link.

74. Check that the personalizations have been applied.

75. Cancel the transaction and confirm the cancellation when the warning appears.

76. Click the Home link.



Practice - Global Personalization Button

Overview

Some web page regions and fields may be difficult to access using the region-level Personalization Framework. As an alternative, you can use the global Personalization button and drill down to access required regions. This practice shows you how to use this alternative.

Assumptions







Tasks

Use the Global Personalization Button

Use the Personalize button located at the top of your web page to drill down and make the following changes at the function level (for xxPersonal Information):

− Change the Employee Number field label in the header to Badge Number (you cannot access the header using region-level personalizations).

− Make the Badge Number field read-only. − Rename the Emergency Contacts region to Contact Information.



Solution – Global Personalization Button

Use the Global Personalization Button





4. Select one of your employees and click Action. The personal information page is displayed.

5. Choose the Personalize Page link in the top right-hand corner of the page.


7. Check that the Scope field contains Page: Oracle Self-Service Human Resources : Personal Information.

8. Check that the Function field contains the name of yur function (xxPersonal Information).


The Personalize Page: Oracle Self-Service Human Resources: Personal Information page appears.

10. Click the Expand All link to expand the personalization structure.

11. As you scroll down the page, you can see all occurrences of the Employee Number field in the Personal Information page (note: the previous practice only covered the Basic Details part of the Personal Information module).

12. Change the remaining occurrences of Employee Number to Badge Number.

Hint: There are 2 remaining occurrences: both under Table Layout: Header Information. For a reminder of the procedure, see the previous practice entitled Configuring Web Page Layouts.




Additional Options for Tabular Regions

Additional Options for Tabular Regions

You can modify the number of columns and rows in tables. You can also change the column labels and change the sequence of columns.



Adding User Instructions

Adding User Instructions

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



Practice - Adding User Tips and Instructions

Overview

In this practice, you learn how to make the instructions and tips that appear on the Personal Information page more meaningful to your employees.

You use the forms interface and Personalization Framework to carry out the following tasks:

• Create message texts

• Add and modify user tips and instructions

Assumptions






• To create a new record using the Professional User Interface, select the New Record icon from the toolbar.

• To save your work, select either the Save icon from the toolbar in the Professional User Interface, or select the Save button in SSHR.

Tasks

Creating User Instructions and Tips

Note: First you need to define the text for these tips and instructions applications messages. Do not try to change the text of a delivered message. Instead, create a new message with the required text, and then personalize the tip or instruction item to use your new message.

Log on to Oracle HRMS as xxUSER1/welcome, and use the Application Developer responsibility to open the Messages window.

Create the following messages:



• xxPERINFO_OVERVIEW_INSTRUCTION

• xxPERINFO_PREFIX_LONGMESSAGE

• xxPERINFO_MIDDLENAME_SHORTTIP

Note: The following attributes apply to all three messages: − Application = Human Resources − Language = US − Type = Note − Number = Null

Adding User Instructions to Web Pages

When you have created your new messages, use the Personalization Framework to add the instructions, messages, and tips to the xxPersonal Information function. Check that the changes appear in the interface.

− Add a new instruction at the top of the Name region of the Basic Details Update page with the message that reads ‘xxRead the field-level tips carefully before making any changes to your basic details’ Note: Create a new item for the page with the item style Static Styled Text.

− Replace the existing tip on the Prefix field with the message that reads ‘xxUse this

field if your name has a prefix as in the examples van de Graaf and de Burgh’. Note: Replace the existing message for the Prefix field.

− Add a new tip to the Middle Name field with the advice ‘xxEnter only the initial(s) of any middle names’. Note: Enter the message name and select the tip type of Short Tip.



Solution – Adding User Tips and Instructions

Creating User Instructions and Tips

Responsibility = Application Developer, Vision Corporation

1. Log on to Oracle HRMS as xxuser1/welcome.

2. Navigate to the Messages window using the Application Developer responsibility.

• (N) Application > Messages

3. In the Name field, enter the following message name:

• xxPERINFO_INSTRUCTION (where xx is your group identifier)

4. In the Language field, select US.

5. In the Application field, select Human Resources.

6. In the Type field, select Note.

7. In the Current Message Text area, enter the following message:

• xxRead the field level tips carefully before making any changes to your basic details.

8. Save your work.

9. Repeat steps 3 through 8 to create the following messages: Field Value

Name xxPERINFO_PREFIX_LONGMESSAGE

Language US


Type Note

Current Message Text xxUse this field if your name has a prefix as in the examples van de Graaf and de Burgh.

Field Value

Name xxPERINFO_MIDDLENAME_SHORTTIP

Language US


Type Note



Current Message Text xxEnter only the initial(s) of any middle name(s)

10. Save your changes and close the window.

Add User Instructions to Web Pages

Add New Instruction




14. Select one of your employees and click Action. The Personal Information page is displayed.

15. To navigate to the page you wish to personalize, choose Update in the Basic Details region.

16. With the “Enter new information . . .” option selected, click on the Next button to continue to the Update Basic Details page.

17. You want to add a new message under the Name region heading so choose the Personalize Name link.


19. Check that the Scope field contains the value Region: Basic Detail Update Name Entry.




The Personalize Region: Basic Detail Update Name Entry page appears.

23. Find the Default Single Column: Basic Detail Update row (the first row in the personalization structure table).

24. Select the Create Item icon.

The Create Item page appears.

25. Check that the Level field contains your function.

26. In the Item Style field, select Static Styled Text.

27. In the Value column for the ID field, enter a value, for example, xxInstruction.



28. In the Value column for the Message Name, enter the name of the instruction (xxPERINFO_INSTRUCTION).

29. Use the Tab key to exit the field.

30. Click Apply to submit your changes.


31. Check that your new item appears in the personalization structure (probably the last row in the table). If this is the case, you may want to reorder the item so that it appears at the top of the Basic Details Update page.

32. Find the Default Single Column: Basic Detail Update row (the first row in the personalization structure table).

33. Select the Reorder icon.

The Reorder Contents of Default Single Column: Basic Detail Update page appears.

34. Locate your instruction (99Instruction) in the list of functions.

35. Move the item to the top of the list by selecting the appropriate arrow icon ( )





39. Check that your instruction is displayed at the top of the Name region.

Replace Existing Long Message

40. Choose the Personalize Name link.









46. Locate the Message Text Input: Prefix row and select the Personalize icon.

The Personalize Message Text Input: Prefix page appears.

47. Locate the Tip Message Name row and change the value in the field to xxPERINFO_PREFIX_LONGMESSAGE for the Function: xxPersonal Information column.


49. Choose Apply to submit your changes.

The Personalize Message Text Input: Prefix page appears.


51. Click the Information icon next to the Prefix field to display the long message.

52. Check that your message appears.

53. Click OK to close the long message window.

Add New Short Tip

54. Choose the Personalize Name link.







60. Locate the Message Text Input: Middle Name row and select the Personalize icon.

The Personalize Message Text Input: Middle Name page appears.

61. Locate the Tip Message Name row and change the value in the field to xxPERINFO_MIDDLENAME_SHORTTIP for the Function: xxPersonal Information column.


63. In the Tip Type field, select ShortTip.



64. Choose Apply to submit your changes.

65. The Personalize Message Text Input: Prefix page appears.


67. Check that your new short tip is displayed under the Middle Name field.




Flexfields

Flexfields

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



Practice - Flexfields

Overview

In these practices you learn how to use the Personalization Framework to modify delivered web pages to suit your business requirements. You learn about the different levels of personalization and practice personalizing various elements on the web pages.

You want to display some additional user-defined fields in the Other region within the Basic Details region of the Personal Information page. You know that the Additional Person Details descriptive flexfield is available in this region so you use the Personalization Framework to display specific segments.

Use the Personalization Framework to carry out the following tasks:

• Check the Additional Person Details and available segments in the forms interface.

• Add flexfield segments to an SSHR page

Assumptions






Tasks

Check Flexfields

Use the System Administrator responsibility to navigate to the Descriptive Flexfield Segments window. Query the Additional Personal Details descriptive flexfield belonging to the Human Resources application. Check the values for the Display flag, Reference field, and the segments of the EMP context field value.

Note: This practice assumes that the Display flag is Yes, the Reference field, is SYSTEM_PERSON_TYPE, and the EMP context includes the following segments:

− Drivers License Jurisdiction − Drivers License Number



Personalize Flexfields

Log on to SSHR as xxuser1 and use the xxManager Self-Service Granted Access responsibility to modify the Basic Details region of the xxPersonal Information function. Display the following segments of the Add Per Details flexfield in the Other region of the Basic Details Update page:

− Drivers License Jurisdiction. − Drivers License Number.

Note: Use the context EMP.

Hint: To display specific segments on a page use the Segment List field in the Personalization Framework and enter the fields that you want to display in the following format:

CONTEXT|SEGMENT1|SEGMENT2

When you have made your changes, return to xxPersonal Information and check that the segments appear.



Solution - Flexfields

Check Flexfields



2. Navigate to the Descriptive Flexfield Segments window:

• (N) Application > Flexfield > Descriptive > Segments



4. Enter the flexfield Additional Personal Details in the Title field:

• Additional Personal Details

5. Execute the query


6. Check the values for the Display flag and the segments of the EMP context field value. Make sure that the flexfield contains the following segments:

• Drivers License Jurisdiction

• Drivers License Number

Personalize Flexfields



8. Select your custom Personal Information function (xxPersonal Information) from the menu.

9. In the Basic Details region, choose the Update button.

10. With the “Enter new information because of a real change to the current details” option selected, choose the Next button.

11. In the Other region, note that initially none of the flexfield segments appear.

12. Click the Personalize Other link.




14. Check that the value in the Scope field is Region: Basic Details Update Other Entry.

15. Check that the value in the Function field is xxPersonal Information.

16. Check that the value in the Responsibility field is xxManager Self-Service Granted Access.


The Personalize Region: Basic Details Update Other Entry page appears.

18. Scroll down the page to locate the Flex: Add Per Details row.

19. Choose the Personalize icon for this row.

20. The Personalize Flex: Add Per Details Flex page appears.

21. Change the value in the Rendered row to True for the xxPersonal Information function.

22. In the Segment List field, specify which segments you want to display as shown below:

EMP|Drivers License Jurisdiction|Drivers License Number

23. Tab out of the field.


The Personalize Region: Basic Details Update Other Entry page appears.


26. Check that the Drivers License Jurisdiction and Drivers License Number segments are now displayed as fields in the Other region of the Basic Details Update page.

27. Click the Home link.



Configuring the e-mail Address

Configuring the e-mail Address

To configure the email addresses: 1. Open the Oracle Workflow Builder. 2. Open your configured HR item type (HRSSA). 3. Select Attributes. 4. Select the attribute HR Department Email ID and enter the appropriate email address in the

Default Value field. 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.

5. Save your work.



Configuring the Global Button Bar

Configuring the Global Button Bar

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



Logos



Guided Demonstration - Personalizing Logos

Responsibility: Manager Self-Service

1. Log on to Oracle SSHR as one of the users created in the training, for example 00user1/welcome.

2. Select the Manager Actions function from the Manager Self-Service responsibility.

• (N) > Manager Self-Service > Manager Actions

3. Select the Personalize Page link from the top of the page.

The Personalization Context page is displayed.

4. Click Apply to continue to the next page.

The Personalization Structure is displayed.

5. Expand the structure.

6. Expand the Corporate Branding row to display the row Image: (Corporate Branding).

7. Click the Pencil (Personalize) icon for the row

8. Point out the FNDSSCORP.gif file.

An administrator can replace this graphic with a corporate graphic, for example.

9. In the column for Function: Manager Actions Tree View, change the value in the Rendered field to False.

10. Apply the changes.

11. Select the Return to Application link and show the participants that the Oracle logo (Corporate logo) is no longer displayed.

12. Select the Personalize Page link from the top of the page.

The Personalization Context page is displayed.

13. Click Apply to continue to the next page.

The Personalization Structure is displayed.

14. Expand the structure.

15. Expand the Corporate Branding row to display the row Image: (Corporate Branding).



16. Click the Pencil (Personalize) icon for the row

17. In the column for Function: Manager Actions Tree View, change the value in the Rendered field to Inherit.

18. Apply the changes.

19. Select the Return to Application link and show the participants that the Oracle logo (Corporate logo) is displayed.

20. Select Home to exit the application.

Note: Explain to the participants that to make a site-level change to the corporate branding logo, they can also set the FND_CORPORATE_BRANDING_IMAGE profile to the URL for their corporate logo.



Configuring Effective Date Prompts

Configuring Effective Date Prompts

The effective date prompt appears at the top of most self-service web pages and indicates whether the current transaction is effective as of a specific date or whether the transaction is effective on approval. The two prompts are: •Effective Date: appears if you specify an effective date on the Effective Date Options page. •Effective as of Approval Date: appears if you specify on the Effective Date Options page that changes should take effect as soon as approval takes place


Approvals Chapter 14 - Page 1

Approvals Chapter 14



Approvals



Basic Approvals Loop

Basic Approvals Loop

The slide above shows the basic approvals loop. This loop represents the processing sequence which is executed behind the scenes in a self-service transaction. When the user submits a self-service transaction for approval, the approvals logic checks whether the approver is the Final Approver. If this is the case, the approvals loop ends. If the approver is not the final approver, the approvals logic fetches the next approver in the approval chain.



Approvals

Approvals

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



Enabling Dynamic Approvals

Enabling Dynamic Approvals

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



Practice - Enabling Dynamic Approvals

Overview

Some functions in SSHR are delivered without approvals enabled. In your organization, however, you may require that these transactions are approved. In this practice, you learn how to enable dynamic approvals for a function that is delivered with approvals disabled.

Assumptions







Tasks

Enable Dynamic Approvals

You want to change the Personal Information function so that all changes to Basic Details must be approved.

Use the Workflow Builder to configure the Review activity in your custom workflow process (xxHR_PROCESS_BASIC_DET_JSP_PRC) so that Dynamic Approvals are enabled.

Test the Changes

Log on to SSHR as xxuser2 and make a change to the Basic Details using your custom Personal Information function (xxPersonal Information). Check that the Approvals regions are now enabled.



Solution – Enabling Dynamic Approvals

1. Open the Workflow Builder using the procedure described in the Using the Workflow Builder lesson.

2. Expand the item type HR.

3. Expand the processes node.

4. Double click on the xxBasic Details process (xxHR_PROCESS_BASIC_DET_JSP_PRC).

5. Scroll across the screen to display the Review Page activity.

6. Click the right mouse button to display the properties for the Review function.

7. Display the Node Attributes tab.

8. Place your cursor on the HR_APPROVAL_REQ_FLAG attribute.

9. Change the value of the attribute to enable dynamic approvals (Yes – Dynamic Approvals).

10. Choose Apply then OK to close the Properties window.

11. Save your changes to the database using the procedure described in the Workflow Builder practice.

12. Choose Exit to close the Workflow Builder.

Test the Changes



14. Select your xxPersonal Information function.

15. Select Update in the Basic Details region.

16. Make sure the Enter new information … option is selected and click Next.

17. Make a change in the Basic Details page, for example, change the Marital Status to Married.

18. Click Next to continue to the next page.

19. Make sure that the Approvals regions are displayed in the Review page.

20. Choose Home.



Configurable Approvals Options

Configurable Approvals Options

The standard behaviour for SSHR functions is to use AME (Oracle Approvals Management). Your AME approval routing rules will override any settings defined in the workflow builder, for example, number of approval levels.



What is AME?

What Is AME?

Calling application refers to the application that is using AME components to define the approval process. Calling applications can be Oracle applications or any application that is uses PL/SQL code.



When Can I Use AME?



Business Requirements

Business Requirements: Example of approval loop using AME

The diagram above shows a basic business process using AME. 1. An employee creates their expense reports 2. An employee submits their expenses for approval. 3. These expenses go to the immediate manager (defined in the supervisor hierarchy) who

may have a sign off limit. 4. If the expenses cannot be approved by the immediate manager, they will then get passed to

the next manager in the chain. You can use AME, to define simple or complex rules which allow line level approval based on the sign off authority. For example, you may set up a substitution rule, which says that if an expense value is below $100, then manager 1 can approve the expenses and if the value is more than $100, then manager 2 needs to approve the transaction. If the default approvers fail to approve the transaction, and the transaction includes additional approvers, AME applies the substitution rule a second time on the additional approvers.

Note: AME processes substitution rules a second time at the end of the processing cycle only when the attribute REPEAT_SUBSTITUTION is set to true.

5. The expenses get paid.



Overview of AME Components

Overview of AME Components

Oracle SSHR provides standard AME attributes for self-service transactions. You can use these standard attributes to better define your approvals processes. For the complete list of attributes, see Oracle Approvals Management (AME) Configuration in the online help.



Approval Considerations



Approvals Routing



Practice - Working with Approvals

Overview

In these practices you learn about approvals. You also see how approvers receive notifications informing them of transactions.

Assumptions






Tasks

Using a Function that Requires Approval

When you set up this supervisor hierarchy, log on as Mary Martin and use the Change Pay to change the pay for Helen Carr from GBP 27.5 per hour to GBP 30. The Approvals mechanism should trigger an approval notification for Malcolm Aurora. You can access the notification as Malcolm by selecting either the All Actions Awaiting Your Attention function from the Manager Self-Service responsibility or by selecting the Worklist function from the Workflow User Web Applications responsibility.

When the Review page appears for transactions requiring approvals, you can add additional approvers or notification recipients. When the Review page appears for the Change Pay transaction, specify that Mary Martin should receive a notification of the transaction.

Display Workflow Notifications

Use the Workflow User Web Applications responsibility as Mary Martin to display the FYI Notification of the transaction. The log on as Malcolm Aurora (xxUSER1) to display the approval notification.



Solution – Working with Approvals

Using a Function that Requires Approval

1. Log on to SSHR as user2.


3. Select the Change Pay function.

The People in Hierarchy page appears.

4. Select the Action icon for Helen Carr.

The Change Pay: Perform Action page appears.

Check that the Change Pay action is in the Selected Actions table.

Select Start to initiate the transaction.

The Effective Date Options page appears.

5. Use today’s date as the effective date.

6. Click the Continue button.

The Pay Rate page appears.

7. Navigate to the Proposed Pay Rate region.

8. In the Description field, select Productivity.

9. In the Hourly Rate Annualised field, enter 2.5.

The remaining fields in the Proposed Pay Rate table are completed.

10. Choose the Next button.

The Review page appears.

Navigate to the Approvers region.

The Approvers table lists Malcolm Aurora as the approver.

11. Expand the Add Ad-hoc Approvers region.

12. In the Approver Type field, select HR People.

13. In the Approver field, enter Martin% and click the Search icon.



14. Select Mary Martin xx.

15. In the Category field, select For Your Information.

16. In the Insertion Point field, select Append to List.

17. Choose Submit to save the transaction.

18. Return to the homepage.

Display the Workflow Notification

Responsibility = Workflow User Web Applications responsibility.

19. Select the Notifications function.

20. The Worklist page is displayed.

21. Make sure that the worklist contains the notification for Helen Carr.

22. Click on the subject title to open the notification.

23. Choose the Logout link.


25. Select the Notifications function.

26. The Worklist page is displayed.

27. Make sure that the worklist contains the Change Pay notification.

28. Click on the subject title to display the information.

29. Click the Approve button to approve the transaction.

30. Choose the Logout link.



Practice - Creating an AME Rule

Overview

You can use Oracle Approvals Management (AME) to customize and configure your approvals processes to meet your specific requirements.

After creating your own custom workflow process, you decide that an additional approval level is required for SSHR transactions that use this workflow process.

In this practice you create the following list creation rule in AME:

• If the SSHR transaction calls your custom workflow process (xx_HR_PERSONAL_INFO_JSP_PRC) then the second immediate supervisor in the chain of authority as well as the immediate supervisor of the person submitting the transaction must approve the transaction.

To create this rule, you must also carry out the following tasks:

• Check the delivered Workflow Process attribute.

• Define a condition.

• Define the list creation rule.

Assumptions


• Prefix all names of rules, attributes and conditions with your assigned unique group number or your initials.

• Use the responsibility/user as offered by the trainer

Tasks

Define Condition

Define an ordinary header condition that references your workflow process. Use the WORKFLOW_PROCESS_NAME attribute.

Define Rule

Define a list creation rule, which will use the attributes, conditions and approval types mentioned above. Create a rule called xxWorkflow Process that uses the chains of authority based on



number of supervisory levels approval type. Use the WORKFLOW_PROCESS_NAME header attribute and your new condition.

Test Rule

Use the Test feature to create a test transaction. Change the header approver attributes so that the value of the TRANSACTION_REQUESTOR_PERSON_ID is Helen Carr xx and the WORKFLOW_PROCESS_NAME is xxHR_PERSONAL_INFO_JSP_PRC. Check that the required approvers are returned.



Solution – Creating an AME Rule

Define Condition

Responsibility = Approvals Management Business Analyst


2. Select the transaction type Oracle Self Service Human Resources and click the Conditions link.

3. Click Create.

4. Select the Ordinary for the condition type.

5. In the attribute field, select WORKFLOW_PROCESS_NAME from the list of values.

6. In the String Value field for the Workflow Process Name attribute, enter the internal name of your custom workflow process, for example, xxHR_PERSONAL_INFO_JSP_PRC.

7. Click Apply.

8. A confirmation message is displayed to confirm that the condition has been created.

9. Check that the condition is listed in the conditions list.

Define Rule

10. Click the Rules tab.

11. Click Create.

12. In the Name field, enter xxWorkflow Process.

13. In the Rule Type field, select List-creation.

14. Accept the default start and end dates.

15. Click Next to continue to the next step.

16. Click Add Condition

17. All possible conditions for the Workflow Process are listed in the Header Conditions region. Select your condition.

18. Click Continue to continue to the next step.

19. Select the Action “Require approvals up to the first two superiors” for the Supervisory Level action type.



20. Click Continue, review your rule, and select Finish.

Your rule has been created.

Test Rules

21. Click the Test Workbench tab.

22. Click Create.

23. Select Helen Carr XX as the test data for the TRANSACTION_REQUESTOR_PERSON_ID parameter.

24. Select your workflow process name as the test data for the WORKFLOW_PROCESS_NAME parameter, for example, xxHR_PERSONAL_INFO_JSP_PRC

25. Click Run Test Case.

26. AME will list any rule detected that match your test transaction – yours should be listed. The appropriate people to approve this transaction if initiated by Helen Carr are also listed: Mary Martin and Malcolm Aurora.



Summary


Using SSHR Chapter 15 - Page 1

Using SSHR Chapter 15



Using SSHR



Objectives


Common SSHR Functions Chapter 16 - Page 1

Common SSHR Functions Chapter 16



Common SSHR Functions



Common Functionality



Review Page

Review Page

The top region for the review page, HR_REVIEW_SS, contains multiple subregions, one for each of the modules that uses the review page, and shows only the subregion for current module, for example, HR_BASIC_DETAILS_REVIEW_SS for the Basic Details area of the Personal Information module. The Review Page for SSHR has the following characteristics:

• Included in most SSHR processes • Allows the user to check a transaction before submission • Displays approvals • Allows a user to add additional notification recipients and approvers • Displays before and after values in a tabular format, highlighting any fields which have

changed • Can configure field properties using the Personalization Framework • Can configure instructions and approval properties using Workflow Builder • Allows a user to attach documents



Return for Correction

Return for Correction

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



Save for Later

Save for Later

The slide illustrates how the Save for Later functionality is used within self-service transactions:

• A user can start a transaction and save it for completion at a later time • A user can select stored transactions from the Actions table



Managing Dates

Managing Dates

Effective dates: • The user can decide whether a transaction is valid on approval or on a specific date. • The application also checks the following dates when the user submits the transaction:

- hire_date: Checks that the effective date entered is later than the hire date. - termination_date: Checks that the effective date entered is earlier than the termination

date. - pending_workflow: Checks if there are changes pending in the workflow tables for

the selected person. - future_assignment: Checks if there are any future assignment changes with respect to

the effective date entered. - insert_mode: Issues a warning (alert) if the effective date of the assignment is less

than a future-dated change. Concurrent transactions:

• You control concurrent transaction using the following profile options: - HR:Allow Concurrent Self Service Actions to Yes.



- HR:Refresh Self Service Actions With Data From Intervening Actions - HR:Manage Self Service Actions When Future-Dated Changes Exist

• See: Self-Service Actions topic.



New User Registration

New User Registration

The New User Registration menu/responsibility provide the following functions: • Create User Name • New Employee Registration • Non-Employee Registration

The New Employee Registration function prompts the user to enter Personal, Assignment, and Benefits information. The Non-Employee Registration function prompts the user to enter information and this does not create an employee record. The Non-Employee Registration function is generally used by third parties, for example, Benefits provider. Participants or their dependents can log on to SSHR, for example, for COBRA registration. There are several advantages of using the New User Registration functionality. For example:

• Decentralized entry of user and personal information – reduced administration. • Particularly good if a large number of users need to be created. • Improved accuracy of personal information as user enters it themselves. • User can define their own password.



New Employee Registration Process

New Employee Registration Process

The generic user name and generic password provides access to SSHR. A default organization, payroll, and responsibility are assigned to the generic user name. A user who is given the generic user name and password will be able to log in, select the generic responsibility and, using the New Employee Registration function, create themselves a person record and corresponding personal user name and password. Oracle HRMS uses the default values for the generic user to build the new person record and user record. The process for New Employee Registration is as follows:

• Set up a responsibility with access to the function • Set up a generic user name and assign the responsibility to it • Define default values via profile options for the responsibility or generic user. The profile

options are: - OAB:User to Organization Link - OAB:User to Payroll Link - OAB:Self Registered User Default Responsibility



• Notify new employees or managers of the generic user id and password • Users log in as the generic user to create a new employee and corresponding new user • The new employee and user will combine personal information for the new employee with

default information defined for the generic user



Practice - Setting Up a Generic User ID for New User Registration

Overview

In this practice you learn how to set up a generic user ID for the New Employee Registration function. You can use this functionality as in the following example:

Your enterprise has recently hired a large number of employees. To save administration time, you decide to allow your new employees to use a generic user ID to log on and create their own employee records.

This practice takes you through the steps required to carry out this task:

• Define a default responsibility to attach to the generic user ID. This responsibility contains only the New Employee Registration function.

• Define a generic user ID (xxuserx) which your new employees can use to log on to SSHR. When they log on using this ID, they access the New Employee Registration function.

• Set the following profile options:

Profile Option Level Value

HR: Security Profile Responsibility (xxNew Employee Registration)

Vision Corporation

OAB:Self-Registered User Responsibility

User (xxuserx) Self Registered New User Default Responsibility

OAB:User to Organization Link

User (xxuserx) Vision Corporation

OAB:User to Payroll Link Responsibility (xxNew Employee Registration)

For example, Vision Monthly. If you do not select a payroll, the application uses the default payroll for the business group).

• Check that Oracle HRMS has created a new user record which is attached to a new person record for your user.

Assumptions





• Prefix all names of new objects with your assigned unique group number or your initials.



Tasks

Create a Generic Responsibility

You create a generic responsibility to include the New Employee Registration function. When your users log on to SSHR and use the generic user attached to this responsibility, they can use the New Employee function to register their own information. Create a responsibility with the name xxNew Employee Registration.

Create a Generic User

You can inform your new employees of a generic user ID which enables them to log on to SSHR. Create a generic user for this purpose and link it to the generic responsibility.

Set the Profile Options

Set the default profile options as specified above.

Use the Generic User and Responsibility

Log on as the generic user and enter your personal information and new user name/password.

Check the User Record

Log on to Oracle HRMS and use the Super HRMS manager responsibility to check that the application has created a new user and person record.



Solution: Setting Up a Generic ID for New Employee Registration

Creating a Generic Responsibility


1. Log on to Oracle HRMS as xxuser1 and navigate to the Responsibility window.


2. In the Responsibilities window, create a new responsibility with the following attributes: − Responsibility Name = xxNew Employee Registration − Application = Human Resources − Responsibility Key = xxNEW_EMP_REG − Available From = Oracle Self Service Web Applications − Data Group = Standard − Application = Human Resources − Menu = New User Registration

3. Define the following Menu Exclusions of type Function, so that only the New Employee Registration item will appear on the menu for user of your new responsibility.

− Self Service WorkFlow Enabled Create User Name1 − Self Service WorkFlow Enabled COBRA Registration

4. Save your work.


Creating the Generic User

Responsibility = System Administrator, Vision Corporation



7. In the User window, create a generic user and password (for example, xxUSERX with password ‘oracle’).

8. Add the xxNew Employee Registration responsibility to your generic user.

9. Save your work.




Set the Profile Options


11. Navigate to the System Profile Values window.


12. From the Find System Profile Values window, choose xxNew Employee Registration as the responsibility and xxUSERX as the User..

13. Make sure that the Responsibility, User, and Profiles with No Values options are selected.

14. Uncheck the Site option.

15. In the Profile field, enter HR: Security Profile.

16. Choose Find.

17. Change the security profile for your new responsibility to point to the View All security profile for your business group: Vision Corporation.

18. Save your work.

19. Choose Find.

20. Change the value in the Profile field to OAB:Self Registered User Responsibility.


22. In the User field, select US Benefits Manager as the default responsibility for the new employee registration. This list of values selects responsibilities owned by Application ID = 805, which is Advanced Benefits.

23. Save your work.


25. In the Profile field, enter OAB:User to Organization link.

26. Choose Find.

27. In the User field, select the organization to which you wish your new employees to belong, for example, Vision Corporation.

28. Save your work.


30. In the Profile field, enter OAB:User to Payroll link.



31. Choose Find.

32. In the Responsibility field, select the payroll for your new users, for example, Vision Monthly.

Note: If you do not select a payroll, OAB uses the default payroll for the business group to process benefits.

33. Save your work.

Using the Generic User and Responsibility

Responsibility = New User Registration, Vision Corporation

34. Log on to SSHR as xxuserx.

35. If required, in the Old Password field, enter Oracle.

36. In the two New Password fields, enter Welcome.

37. Choose the OK button.

38. Select the xxNew User Registration responsibility.

39. Select the New User Registration function.

The Introduction page appears.

40. Select the I Accept option to accept the terms displayed here. You can personalize this text as required.

41. Choose the Next button to move to the next page (Person Verification page)

42. In the First Name field, enter a name, for example, Martin.

43. In the Last Name field, enter a last name, for example, Test.

44. In the Date of Birth field, enter a date of birth, for example, 01-Jan-1960.

45. Choose the Next button to move to the next page (Basic Details page)

Here you would continue to enter your personal information.

46. In the Hire Date field, enter a date, for example, 01-Feb-2004.

47. In the Social Security Number field, enter a number, for example, 987-654-3xx.

48. In the Gender field, select the gender.

49. Choose the Next button to move to the next page (Main Address page)



50. In the Address Line 1 field, enter an address, for example, xx Main Street.

51. Select the Search icon next to the City field.

52. Search for a city, for example, Albany and select it.

53. Enter a zip code.

54. Choose the Next button to move to the next page (Phone Numbers page).

55. In the Number field, enter the phone number, for example, 044-9873xx.

56. Choose the Next button to move to the next page (Assignment page).

57. Check the data.

58. Choose the Next button to move to the next page (Family Member Coverage).

59. Select No Coverage.

60. Choose the Next button to move to the next page (Life Events page).

61. In the Current Event field, select SS Reg New Hire.

62. Choose the Next button to move to the next page (User Name page).

63. Enter your new user name, for example, MTESTxx.

64. Enter and confirm the password, for example, Oracle.

65. Choose the Next button to move to the next page (Review).

66. Check the data.

67. Choose the Submit button to submit your transaction to the database.


Checking the User Record


69. Log on to Oracle HRMS as xxuser1.

70. Navigate to the User window:


71. Query your new user (<username>xx) in the User field (to enter a query, choose (M) View > Query by Example > Enter).



72. Check that the default responsibility is entered in the Responsibility area of the window, and the user’s name appears in the Person field.


74. Log on to SSHR as your new user (<username>xx).

75. Select the New User Employee Self-Service responsibility.

76. Make sure that the Employee Self Service menu is available.




Document Manager

Document Manager

Create documents • PDF document - In a PDF editing application, add named form fields to contain data from

the action. The form field names are the tags you map to your action's attributes in Document Management.

• RTF document - When you use an RTF template, the application converts it to PDF format when you generate your document. You can also insert conditional programming statements available using RTF technology to display or hide fields based on the values of other fields. For example, you can display or hide data based on the department or e-mail address.

Configure Document Groups and Attribute Mappings • Use document groups to define a collection of documents and associate them with their

corresponding workflow process. To create the link between the document group and the workflow process, add the function parameter pGroupName=<documentgroupshortname> using a System Administrator responsibility.

• Add a document to a selected group. You can select from a list of documents in the database that are not yet part of a group, or you can add a new document.



• Define document and update Document Pages. If you use FastFormula to populate document tags with returned values from the database, or override tag values with literals, specify them as well.

• Map attributes to merge data from transaction data attributes to form fields. You can include both current and proposed values in a document, and also Header Information attributes containing details from the selected person's record. When you create the pdf document, it is helpful to know which attributes are available in the self-service function that will trigger the document generation. For example, the Change Manager page uses the following attributes:

- Current Manager Name - Employee Name - Manager Name

To create a document for the Change Manager function, you could, therefore, include those attributes in your pdf document as fields. For a list of the delivered attributes, see Document Manager in the online help for SSHR.

• Define Documents Properties to change the Document Type. Available types include Pre Approval, Post Approval, and Both.

• Generate pre-approval versions of documents while it is still in process. Generate post-approval versions on final approval. Initiators receive a notification containing a link to the Document Information page, containing post-approval versions of available documents.



Guided Demonstration - Using the Document Manager

Responsibility: US Super HRMS Manager responsibility

Creating a Document Group

1. Log on to SSHR as HRMS/welcome.

2. Navigate to the Document Manager page.

• (M) Other Definitions > Document Management

The Document Management page appears.

3. Click on the Create Group button to create a new document group.

4. The Define Group page appears.

5. In the Group Name field, enter xxPersonal Information, where xx is a prefix, for example, 99 or 00.

6. In the Short Name field, enter xxPerInfo, where xx is the same prefix as you used for the Group Name field.

7. Click the Apply button to save your changes.

You are returned to the Document Management window.

8. In the Group Name field, enter xx%.

9. Click the Go button to search for your group.

Your new group appears in the table.

10. Click the Plus (+) icon in the Add Document column.

The Map Documents page appears.

11. Click the Create Document button under the Results header.

The Define Document page appears.

Defining Your Document

12. In the Document Name field, enter xxStatusChange.

13. In the Short Name field, enter xxStatus.

14. In the Effective Date field, enter 01-Aug-2005.



15. In the File region, select the Upload a New File option.

16. Select the Browse button to search for your document.

17. Select the marital_status.pdf document that was supplied with the other courseware for this class.

18. Click the Continue button to display the next page.

The Define Document: Attribute Mapping page appears.

Note that your fields from the pdf are defined as attributes here.

Mapping Your Document Fields to SSHR Attributes

19. Select the Search icon next to the Marital Status field to display the Search page.

20. In the Attribute Name field, enter Marital%Status.

21. Click the Go button.

22. Select the Marital Status (Proposed) attribute.

23. Select the Search icon next to the Title field to display the Search page.

24. In the Attribute Name field, enter Title.


26. Select the Title (Current) attribute for the Personal Information process and click the Select button.

27. Select the Search icon next to the LastName field to display the Search page.

28. In the Attribute Name field, enter Last Name.


30. Select the Last Name (Current) attribute and click the Select button.

31. Select the Search icon next to the Date field to display the Search page.

32. In the Attribute Name field, enter Effective Date.


34. Select the Effective Date attribute (Current) and click the Select button.

35. Click the Finish button to continue to the next page.



A message confirms that you have created a new document.

36. In the Document Name field under the Search header, enter xx% to search for your new document.

The document appears in the table.

37. Select the document and click Continue to display the next page.

38. In the Type field, select Both.

39. Click Finish to continue to the next page.

A message confirms that your changes have been saved.

40. Return to the Homepage.

Setting the Function Parameter


41. Log on to Oracle HRMS as HRMS/welcome and navigate to the Form Functions window.

(N) Application > Form

42. Select the Search icon to find a custom function. For example, select 01Personal Information.

43. Select the Form tab.

44. Place your cursor on the Parameters field and select the Edit Field icon from the toolbar.

The function parameters are displayed.

45. Add the following parameter:

• pGroupName=<document group short name> (for example, 99PerInfo)

• Note: The function parameter is case-sensitive. Make sure that you enter parameter value exactly the same as the group name.

46. Save your work.

47. Close the form.

Generating Documents Automatically

Responsibility = xxManager Self-Service

48. Log on to Oracle SSHR as 99user2/welcome.




50. Select the xxPersonal Information function.

51. Click the Action icon for Mary Martin

52. Choose the Update button in the Basic Details region to update the personal information.

53. Select the “Enter new information … “ option and continue to the next page.

The Basic Details Update page is displayed.

54. Select the title for Mary Martin, for example, Mrs.

55. Make a change to the Marital Status, for example, set the status to Married.

56. Choose Next to display the Review page (or the SIT Update page).

57. From the Review page, you can display a printable page which includes any documents generated by the Document Manager.

58. Select the Printable Page link at the bottom of the page.

59. A dialog box appears to verify whether you want to open the file or save it to your computer. Open the file.

60. The generated pdf document is displayed.

61. Choose File > Close to close the document.

62. When the Review page is displayed again, choose Cancel to cancel the transaction.

63. Log out of SSHR.



FastFormula Options for Document Manager

Fast Formula Options for Document Manager

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


Self-Service Actions Chapter 17 - Page 1

Self-Service Actions Chapter 17



Self-Service Actions



Overview – Self-Service Actions



Types of Self-Service Action



Life-Cycle of Self-Service Action

Life-Cycle of Self-Service Action

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



Profile Options for Self-Service Actions

Profile Options for Self-Service Actions

• HR:Allow Approver updates to Self Service actions - Allows an approver to make updates to actions.

• HR:Allow concurrent Self Service actions - Allows multiple simultaneous self-service actions.

• HR:Manage Self Service actions when future-dated changes exist - If you set this profile option to Yes, you can control potential data conflicts when

future-dated changes exist. The default setting is Stop with an Error. This forces the user to choose an effective date subsequent to any future-dated change. Change this to Allow Approval (Notify HR Rep) to allow the user to select a date prior to any future-dated changes. After final approval the transaction is forwarded to an HR Representative for review and manual entry into the database.

Attention: If you set this profile option to Allow Approval, and you have enabled HR:Allow Approver Updates to Self Service Actions, Oracle recommends that you also enable HR:Refresh Self Service Actions with Data from Intervening Actions.

• HR:Refresh Self Service actions with data from intervening actions



- Allows you to control the effect of concurrent actions. If set to Yes, when a pending change is approved which affects the current transaction, the application displays a warning message with changed attributes and refreshes the data .If set to No (default), the application displays a warning message and the transaction fails. Oracle recommends that you set this profile option to Yes if HR: Allow Approver Updates to Self Service Actions is also Yes.

Note: Oracle recommends that you enable this option if you have set the system profile HR:Manage Self Service Actions When Future-Dated Changes Exist to Allow Approval (Notify HR Rep). Otherwise you should disable this option.

• HR:Display Position Hierarchy - If set to Yes, SSHR uses the position hierarchy will be used in the HGrid on the Enter

Process page. By default the HGrid uses supervisor hierarchy. • HR: Position Default Options for SSHR enables you to configure the application to

populate default information based on the position you select for an assignment. You can configure the user profile to populate Department, Job, Grade, Payroll, Supervisor, Probation Period, Bargaining Unit, Salary Basis, Work Hours, and Location. Implementers can choose whether to populate default data with no warning, display a warning, ask the user to decide, or turn off position defaulting.

• HR:Allow use of eligibility for Self Service actions - If set to yes, the Eligibility column appears on the Actions page and all eligible and

ineligible actions are displayed. The Eligibility column distinguishes between them. If set to No (default), only eligible actions are displayed and the Eligibility column is not displayed.

Note: Managers cannot process ineligible actions unless the profile option HR:Allow Processing of Ineligible Self Service Actions is also set to Yes.

• HR:Allow processing of ineligible Self Service actions - If set to Yes, managers can process ineligible self service actions. Note: This option depends on also enabling the profile option HR:Allow Use of

Eligibility for Self Service Actions in order to display ineligible actions in the first instance.

• HR:Run BENMNGLE when processing a Self Service action - In order to ensure that the list of eligible actions and sub-actions is up to date, you

must periodically run the Participation Batch Process (Run Benefits Manage Life Events Process) for that individual. This can run automatically every time a manager initiates an action by setting the profile option, HR:Run BENMNGLE When Processing a Self Service Action, to Yes.



Conflicting Actions



Conflicting Actions - Resolution

Conflicting Actions - Resolution

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



Approvals and Access Roles

Approvals and Access Roles

The above graphic illustrates how you can use an access role to restrict a user from updating SSHR transactions routed for approval. For example, in the above example, Approver 1 cannot update the transaction. Instead the transaction is routed directly to Approver 2.



Practice - Access Roles and Approvals

Overview

By default, all users can update self-service transactions. In this practice you assign an access role to a user to prevent the user from updating a transaction that has been routed for approval. You carry out the following tasks:

• Assign the access role

• Check that the access role functions correctly by logging on as different users and displaying the Actions table.

Assumptions






• To save your work, select the Save icon in the Professional User Interface, or select the Save button in SSHR.

Tasks

Assigning an Access Role

You decide to revise your approval policies and wish to restrict particular managers from being able to update SSHR transactions routed for approval.

Log on to Oracle HRMS as xxuser1 and use the local Super HRMS Manager responsibility to create a suitable role (xxSSHR No Update) using the SSHR Update Not Allowed role type and assign this role to Mary Martin (xxUSER2).

Testing Access Roles

If the SSHR Update Not Allowed role is assigned to a user, that user cannot update any transactions that have been routed for approval. To test this, log on to SSHR as xxuser4 and create a Leave of Absence record using the following data as an example:



• Absence type: Vacation

• Start date: Date of your choice, for example, 01-Feb-2006

• End date: Date of your choice, for example, 05-Feb-2006

Usually this transaction would go first to Mary Martin for approval and then to Malcolm Aurora. Create the absence record and then log on as Mary to see whether approval is required. Try and update the approval action.

Note: To display approval requests, use the All Actions Awaiting My Attention function.

Note: You may need to ask your instructor to restart the Apache server to ensure that the changes are applied.



Solution – Access Roles and Approvals

Assigning an Access Role

Responsibility = US Super HRMS Manager, Vision Corporation

1. Log on to Oracle HRMS as xxuser1 and navigate to the Roles window.

• (N) Transaction Maintenance > Roles

2. In the Role Name field, enter xxSSHR No Update.

3. In the Role Type field, select SSHR Update Not Allowed.


5. Place your cursor on the row for the xxSSHR No Update role and then select the Users tab.

6. Select the search icon next to the Person field and enter %Martin% in the resulting Find window.

7. Select Mary Martin xx.

8. Save your work and close the form.

Testing Access Roles

9. Log on to Oracle SSHR as xxuser4.

10. Select the Leave of Absence function from the Employee Self-Service responsibility.

(N) Employee Self-Service > Absence Management

The Summary of Absences page is displayed.

11. Choose Create Absence to create a new leave request.

The Create an Absence Request page is displayed.

12. Select Vacation as the Absence Type.

13. In the Start Date field, enter a date, for example, 01-Feb-2006.

14. In the End Date field, enter a date, for example, 05-Feb-2006.

15. Click the Calculate Duration button to populate the Days field.

16. Choose Next to display the Review page.



Mary Martin xx should be listed as an approver for the transaction.

17. Choose Submit to submit the transaction.

18. Choose Logout.

Testing Your Changes – Optional


20. Select All Actions Awaiting My Attention function from the Manager Self-Service responsibility.

• (N) Manager Self-Service > All Actions Awaiting Your Attention

21. The list of actions should include an approval request for Helen’s leave request.

22. Select the action to display the information.

23. Select the Update Action link.

24. You should not be able to update the action. An error message should be displayed. This is because the role prevents Mary from updating actions.

25. Log out of SSHR.



Configuring Self-Service Actions



Combining Activities for Self-Service Actions



What-If Analysis

What-If Analysis

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



Eligibility Processing

Eligibility Processing

There are 2 types of eligibility profile: Participant and Dependent You can define eligibility at all levels of the compensation object hierarchy: Program, Plan Type, plan, and options. The eligibility profile is not the only deciding factor whether a participant or dependent is eligible. You must also consider enrollment requirements and/or life events. Manage Employment Events and eligibility are discussed in greater depth in the People Management curriculum. Note: Manage Employment Events may sometimes be referred to as Self-Service Actions.



Summary


Advanced Topics Chapter 18 - Page 1

Advanced Topics Chapter 18



Advanced Topics



Objectives


Employee Directory Chapter 19 - Page 1

Employee Directory Chapter 19



Employee Directory



Employee Directory



Single Sign-On or Anonymous Log-In?

Single Sign-On or Anonymous Log-In?

The Employee Directory is read-only unless single sign-on is enabled.



Enabling Single Sign-On

Enabling Single Sign-On

The descriptive flexfield segment could be structured as follows: Descriptive Flexfields Segments window

• Code: Employee Directory • Name: Employee Directory User Name • Description: Employee Directory User Name

Segments Summary window • Name:Employee Directory User Name • Window Prompt: Employee Directory User Name • Attribute: ATTRIBUTE1 • Value Set: 30 characters

For information on the override procedure, see the next slide.



Overrides

Customer Overrides

To enable single sign-on for the Employee Directory, you use a customer override to add the FND_USERS column to the Employee Directory tables.



Customer Overrides for Employee Directory

Customer Overrides

IF p_srcSystem = 'PER' THEN per_empdir_ss.personTbl.person_key(p_rec_locator) := upper(per_empdir_ss.personTbl.attribute26(p_rec_locator)) ||' '||per_empdir_ss.personTbl.person_key(p_rec_locator) ||' '||substr(personTbl.work_telephone(p_rec_locator), length(personTbl.work_telephone(p_rec_locator))-4, 4); per_empdir_ss.personTbl.user_name(p_rec_locator) := upper(per_empdir_ss.personTbl.<<attributename>>(p_rec_locator)); END IF; The code assigns the user name to an available column in the repository. It also adds the user name to the person_key, which enables searches on the user name. It formats the work telephone number and adds it to the person_key, enabling searches on a preferred telephone format. You also use the overrider package to include a search field in an HTML form. For more information, see the online help under: Oracle HRMS > Deploy Oracle Self-Service Human Resources.



Populating the Repository

Populating the Repository

When you run the Refresh Employee Directory concurrent program, you can set the following parameters:

• Complete refresh – for initial population and intermittently in future • Incremental refresh – at regular intervals to ensure that data is up-to-date • Source system – PER • Process multiple assignments – processes primary or multiple assignments



Overrides for Populating the Repository

Overrides for Populating the Repository

You can use the delivered override packages to override values in the repository table columns.



Refresh Modes

Refresh Modes

When you run the Refresh Employee Directory process, you select a Refresh mode: either Complete or Incremental.



Guided Demonstration - Employee Directory and Single Sign-On

The Employee Directory is read only. To enable users to edit their personal information, or to add or edit their image, follow the procedures below to provide them with single sign on access to Self-Service:

• Define an FND user for each person that requires access to Self-Service, if they are not defined as FND users already.

• In the Descriptive Flexfield Segments window, configure a segment in the Additional Personal Details Descriptive flexfield to hold the FND_USER names, using any available attribute.

• Enter the employee’s user in the new flexfield segment which is accessible from the Enter and Maintain People form.

• Map the segment to the USER_NAME column in the PER_EMPDIR_PEOPLE repository table by editing the PER_EMPDIR_PEOPLE_OVERRIDE.

• Run the Refresh Employee Directory program to populate the Employee Directory.

• Demonstrate how a user can add a photo to the Employee Directory.

Define an FND User


1. Log on to Oracle HRMS as HRMS/welcome.

2. Select the System Administrator responsibility.



4. Initiate a query to check that your required users exist.


5. Enter the name of a user in the User Name field. For example, enter XXuser1

6. Run the query.


7. Check that your user already exists.



Configure a Flexfield Segment

Responsibility = Application Developer or System Administrator

8. Navigate to the Descriptive Flexfield Segments window.

• (N) Application > Flexfield > Descriptive > Segments



10. Enter the following text in the Title field:

• Additional Personal Details

11. Run the query.


The Context Field Values for the flexfield are displayed.

12. Make sure that the Freeze Flexfield Definition box is NOT selected.

13. Place your cursor on the Global Data Elements row.

14. Select the Segments button.

The Segments Summary (Additional Personal Details) – Global Data Elements window is displayed.

15. Enter the information for the new flexfield segment as follows: Number Name Window

Prompt Column Value Set Displayed Enabled

1 Employee Directory User Name

Employee Directory User Name

ATTRIBUTE15 FND_USER Yes Yes

16. Select the Open button to display the Segments window.

17. Check the displayed information.

18. Save your work.

19. Close all windows to return to the Descriptive Flexfield Segments window.

20. Select the Freeze Flexfield Definition checkbox and choose OK when the warning message is displayed.



21. When you save the changes, the Oracle HRMS automatically compiles the flexfield.

22. Close the form.

Add the User Name to the Flexfield

23. Responsibility = US Super HRMS Manager

24. Navigate to the People window:

• (N) People > Enter and Maintain

25. In the Find People window, enter the name of an employee, for example, Aurora%.

26. Select the Find button to run the query.

27. Place your cursor on the Flexfield field in the bottom right corner of the window.

The Additional Personal Details flexfield is displayed in a window.

The Employee Directory User Name field should be displayed (usually at the top of the window).

28. Enter the user name for the employee in the Employee Directory User Name field, for example, XXUSER1.

29. Click OK to close the window.

30. Click Correction to correct the existing information.

31. Save your work and close the window.

Edit the Package

32. Launch psftp.exe.

33. Enter psftp: no hostname specified; use “open host.name” to connect.

34. psftp > open esNNNN.us.oracle.com.

35. Log in as user1.

36. If the Store key in cache? message appears, choose Y.

37. The password for [email protected] is oracle.

38. Enter cd /esNNNN/appltop/115/per

39. cd 11.5.0



40. cd patch

41. cd 115

42. cd sql

43. lcd e:\temp

Note: e:\temp already exists in each PC.

44. get peredcor.pkb

45. Repeat the same procedure to get the other files:

• peredcor.pkb

• peredcor.pkh

• peredlor.pkb

• peredlor.pkh

• peredrcp.pkb

• peredrcp.pkh

Modifying the Package Body

46. Open file e:\temp\peredcor.pkb with Wordpad.

47. Modify the line in the PER_EMPDIR_PEOPLE_OVERRIDE package body:

From:

g_override_flg BOOLEAN:= FALSE;

To:

g_override_flg BOOLEAN:= TRUE;

Note: This change enables the override package.

48. Scroll down in the package to locate the section of sample code in the package:

Sample Code

/* IF p_srcSystem = 'PER' THEN

per_empdir_ss.personTbl.person_key(p_rec_locator) :=



upper(per_empdir_ss.personTbl.attribute26(p_rec_locator))

||'%'||per_empdir_ss.personTbl.person_key(p_rec_locator);

per_empdir_ss.personTbl.user_name(p_rec_locator) :=

upper(per_empdir_ss.personTbl.attribute26(p_rec_locator));

END IF; */

49. Remove the comment identifiers (/*) from the start and end of the section of sample code.

50. Instead of "attribute26", use the attribute name you used to configure the segment in the Additional Personal Details Descriptive flexfield (in this case, the attribute name is ATTRIBUTE15).

Note: The preceding code assigns the user name to an available column in the repository. In addition it adds the user name to the person_key, which enables searches on the user name.

Note: In practice you would then upload your changes to your database.

51. Copy the modified file from local e: drive to appltop/patch/115/sql directory.

52. Apply the file to the database, by running the following command:

• $> sqlplus apps/apps@esNNNN @peredcor.pkb

Note: hrssdvl here is a sample database instance name. apps/apps => login/password for the database instance.

Populate the Repository

Responsibility = US Super HRMS Manager

53. Log on to Oracle HRMS as hrms/welcome.

54. Navigate to the Submit Request window:

• (N) Processes and Reports > Submit Processes and Reports

55. Submit a single request.

56. In the Name field, enter Refresh Employee Directory.

The Parameters window is displayed.

57. In the Refresh Mode field, select COMPLETE.

58. Set the Refresh Date to today’s date.



59. Make sure that the value in the Source System field is PER.

60. For this demo, make sure that the value in the Process Multiple Assignments field is N.

61. Choose OK to close the Parameters window.

62. Choose Submit to submit the process.

63. Navigate to the Requests window:

• (M) View > Requests

The Find Requests window appears.

64. Make sure that the All My Requests radio button is selected.

65. Choose Find to display your requests.

66. Check that the process has completed.


Edit Personal Information

Responsibility = Employee Self-Service

68. Log on to SSHR as xxUSER1.

69. Select the Employee Directory function.

70. Enter Malcolm Aurora in the Search field and click Go.

71. The search results are displayed.

Note: If there are many people with the same name, try returning to the Personal Information function and entering a telephone number. This will help you to identify the correct person in the search results.

72. Select your own record (Malcolm Aurora) with your Work Phone number.

73. Check that the Edit My Information link is displayed in the left navigation bar under Short Cuts.

74. Note: If the link is not displayed, you need to personalize the page to display it. Use the following procedure:

1. Set the profile options to allow personalization (Personalize Self-Service Defn and FND: Personalization Region Link Enabled).

2. Choose Employee Self-Service responsibility.



3. Choose Employee Directory.

4. In the Search field, enter Malcolm Aurora, choose Go button.

5. Choose the Malcolm Aurora link with your own Work Phone number.

6. Click the Personalize Page link at the top of the page.

7. Accept all the defaults, Choose Apply

8. In the Personalization Structure, click Expand All to expand the hierarchy.

9. Scroll down to the bottom of the table to find the Header: Short Cuts row.

10. Click on the Personalize icon.

11. Change the value of the Rendered field to true under the Responsibility column.

12. Click Apply to submit the changes.

13. Choose Return to the Application link.

75. Click the Edit My Information link to display the Update Profile page.

76. Explain to the participants that they can upload a photograph if required.

Note: It is possible to add a link to the Personal Information function from this page, however, this is not yet documented.

77. Click Home.



Summary


Responsibility Ownership Chapter 20 - Page 1

Responsibility Ownership Chapter 20



Responsibility Ownership





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



Additional Configuration Steps

Additional Configuration Steps

Before you use the Responsibility Ownership function, you must additionally configure: • Create data security grants to link responsibilities to your users - data grants enable you to

control access to data in the data security system. When you create a data grant, you grant access to a database object to a user. In the case of the Responsibility Ownership function, you use data grants to grant responsibility ownership to a user.

• Create code to subscribe to the business event oracle.apps.per.selfservice.respowner.revoke_access. This triggers the fnd_user_resp_groups_api.update_assignment API to end date the responsibility assignment.



Practice - Creating Data Grants for Responsibility Ownership

Overview

In this practice, you learn how to create a data grant to enable users access to the Responsibility Ownership functionality.

Assumption

You must have access to an Oracle Application Vision database or comparable training or test instance at your site on which you want to complete this practice.

Task

Creating a Data Grant

You want to grant xxuser1 ownership of responsibilities. Using the Functional Administrator responsibility, create a data grant to enable xxuser1 access the Responsibility Ownership functionality.



Solution - Creating Data Grants for Responsibility Ownership

1. Log in to Oracle HRMS using hrms/welcome and use the Functional Administrator responsibility.

2. Click the Grants tab.

3. From the Grants page, click Create Grant to initiate the creation process and define the data grant.

4. In the Name field, enter a descriptive name for the grant xxGrant, where xx represents your unique identifier. You can also enter a description.

5. Enter the current date in the Effective From field.

6. Navigate to the Security Context region to define the context for applying the grant. In the Grantee Type field, select Specific User.

7. In the Grantee field, enter xxuser1, where xx represents your unique identifier.

8. Navigate to the Data Security region. In the Object field, search for and select the delivered object FND_USER_RESP_GROUPS.

Note: Oracle provides this object for use with the Responsibility Ownership functionality.

9. Click Next to continue.



10. For the purpose of the Responsibility Ownership function, you must create a data set that grants access to a specific instance in the object. Select the data context type Instance.

11. Click Next to define object parameters and select set.

12. The data set instance comprises three segments of information. Enter the following information:

Field Value

Responsibility ID 50101

Application ID 800

Security Group ID 0

13. In the Set field, enter the delivered set PRIMARY_OWNER.

Note: Oracle provides this function set for use with the Responsibility Ownership functionality.

14. Click Next to continue.

15. Click Finish to complete the data grant creation process.

xxuser1 can now log on to SSHR and use the Responsibility Ownership function to administer and control access to their responsibilities.



Summary