23
Configuring Context Sensitive Extra Information Types (EITs) Using Oracle Self-Service Human Resources (R12.1.2) An Oracle White Paper November 2009 1

Whitepaper Context Sensitive EITs

Embed Size (px)

DESCRIPTION

Setting for EITd

Citation preview

Configuring Context Sensitive Extra Information Types (EITs) Using Oracle Self-Service Human Resources

(R12.1.2)

An Oracle White Paper November 2009

1

Table of Contents 1. Introduction.......................................................................................... 3 2. Release Level ........................................................................................ 3 3. References ............................................................................................. 3 4. Configuration for Context Sensitive EITs.................................. 3

4.1 Prerequisite ........................................................................................................ 3 4.2 Setup Steps in Oracle HRMS.......................................................................... 4 4.3 Setup Steps in Oracle Self-Service HR........................................................... 9 4.4 Real Time Execution....................................................................................... 11

5. Additional Setup in Oracle HRMS for using EITs in PUI along with the Self-Service HR setup............................................... 14

2

1. Introduction Flexfields provide the capability to capture unlimited amount of information based on an organization’s requirements. The flexfield segments can be auto-populated depending on other segments. The dependent flexfield segments can be driven based on other independent flexfield segments. For example, when information is entered in a segment of one flexfield, based on that information the context in dependent flexfield can be set. Extra Information Types (EITs) are Descriptive Flexfields used to capture extra information for Location, Organization, Job, Position, People and Assignments. The configuration steps documented in this whitepaper describe how to set up context sensitive extra information types in Oracle Self-Service Human Resources. The document also covers the steps to be performed to continue using EITs in professional forms along with context sensitive EITs in Self-Service HR. For illustration purpose, Extra Person Information EIT is used. The feature can be set up on any DFF which has a dependent flexfield.

2. Release Level Important: This document is meant for EBS HCM 12.1.2 and forward.

3. References Refer to the following PDF guides on the Oracle Applications Documentation site: http://www.oracle.com/technology/documentation/applications.html

• Oracle Self-Service Human Resources Deploy Self-Service Capability Guide • Oracle HRMS Implementation Guide

4. Configuration for Context Sensitive EITs Self-Service HR can be configured to support context sensitive EITs. This requires a set of steps to be performed in Oracle HRMS as well as in Oracle Self-Service HR, the details of which are given below.

4.1 Prerequisite

1. Access to System Administrator responsibility 2. Access to HRMS Manager responsibility (Professional Forms) 3. Access to Employee/Manager Self-Service responsibility ( Personalization set up)

3

4.2 Setup Steps in Oracle HRMS

4.2.1 Define context sensitive segments: Navigation: System Administrator responsibility Application Flexfield Descriptive Segments

1. Identify the independent flexfield ( For example, Extra Person Information) 2. Identify the context of the independent flexfield (For example,

PQH_ACADEMIC_RANK) to be referred by the dependent flexfield

3. Identify the segment of that context for which context sensitive segments of the dependent flexfield need to be defined. Note the column for that segment (PEI_INFORMATION1)

4

4. From the Segments Summary, navigate to Value Set Edit Information

5. Note the LOOKUP_TYPE ( PQH_ACADEMIC_RANK)

5

Navigation: Super HRMS Manager Responsibility People Other Definitions Lookup Tables

6. Query the LOOKUP_TYPE ( PQH_ACADEMIC_RANK)

7. Note the context codes (‘Code’) for the lookup values

8. Create corresponding codes in the dependent flexfield (Extra Person Info. Details)

9. The ‘Synchronize with Reference Field’ check box should be checked. The value of reference

field should be of format “:$PROFILES$.*<name>” (Name can be any character)

6

10. Define the dependent flexfield segments for the context codes – (Grade and Salary). These are the

context sensitive segments, which will be displayed when the user enters a value in the independent flexfield segment for the context.

7

11. Grade and Salary are the segments for the context code ‘03’ with the name ‘Instructor More Info’ corresponding to the context code ‘03’ for ‘Instructor’ in the Lookup table for the Independent flexfield segment (Refer Step #6)

12. Another example of segments defined for another context ‘N’ corresponding to the segment in independent flexfield

8

4.3 Setup Steps in Oracle Self-Service HR The next set of steps is to be done in Oracle Self-Service HR. Complete the following steps:. Navigation: Employee Self-Service Extra Information Add/Update Page Personalize Page

13. Click Add ( If EITs already exist, click the Update or Add button)

14. Click Personalize Page to create flexmaps for the context reference

9

15. Click Create Item for the property ‘Flex: Developer Descrip...’

16. Create flexmap items. Format of Reference Value is as ${oa.<independent_context>.<column_name>}

Refer Step #2 and Step #3 for context code and column name

10

18. Similarly, define flexmaps for other contexts as well. ‘Name’ should match the ‘name’ in the reference field value “:$PROFILES$.*<name>” defined in Step #9.

17. Three flexmaps are defined in this example.

4.4 Real Time Execution Steps #18 to #24 illustrate the end user interaction for the feature.

18. Employee navigates to the Extra Information function and enters a value of ‘Lecturer’ for

Academic Rank and tabs out of the field. Note that the Context value field is null.

11

19. The context value defaults to ‘Lecturer More Info’ and the context sensitive segments ‘Lecturer

Grade’ and ‘Lecturer Salary’ are displayed.

20. User enters another value ‘Instructor’ for Academic Rank and tabs out of the field.

21. Context value defaults to ‘Instructor More Info’ and the context sensitive segments ‘Instructor Grade’ and ‘Instructor Salary’ are displayed.

12

22. User selects ‘No’ for the ‘Subject to Tenure Quota’ field.

23. For the context reference ‘No’ the dependent flexfield segments ‘Reason for No’ and ‘Comments for No’ are displayed

13

24. Context sensitive segments are supported for free text input also. In the following example for Comments field user enters free text HR Role and the context value defaults to the context set for HR Role.

The above process enables context sensitive EITs in Self-Service HR.

5. Additional Setup in Oracle HRMS for using EITs in PUI along with the Self-Service HR setup

25. To continue using EITs in PUI (Professional forms) once the above setup for context sensitive EITs in Self-Service HR are completed, perform the following set of steps in Oracle HRMS. Personalize the EIT form as follows. Personalization can be done either at the Form level or at Function level. Personalization at the Form level is recommended.

26. Query a Person and navigate to the Extra Information form Navigation: People -> Enter and Maintain Query A Person Others Extra Information

14

27. From the Extra Information Form navigate to Help Diagnostics Custom Code

Personalize.

15

28. Personalize the form as given below

Seq 1

Description Set Profile Step 1

Level Form

Trigger Event WHEN-NEW-FORM-INSTANCE

16

29. Navigate to the Actions tab and enter the following

Seq 1

Type Builtin

Builtin Type Set Profile Value in Cache

Profile Name *<name> (*A in the example used above)

Profile Value leave the field blank

17

30. Save the record and go to the next Seq row. Continue the setup as shown below

Seq 2

Description Set Profile Step 2

Level Form

Trigger Event WHEN-NEW-RECORD-INSTANCE

Trigger Object PIT

18

31. Navigate to the Actions tab and enter the following information

Seq 1

Type Builtin

Builtin Type Set Profile Value in Cache

Profile Name *<name> (*A in the example used above)

Profile Value leave the field blank

19

32. Save the record and go to next Seq row.

Seq 3

Description Set Profile Step 3

Level Form

Trigger Event WHEN-NEW-ITEM-INSTANCE

Trigger Object PEI.DF

20

33. Go to Actions tab for Seq 3 and enter the following information.

Seq 1

Type Builtin

Builtin Type Set Profile Value in Cache

Profile Name *<name> (*A in the example used above)

Profile Value :Context Segment (:PEI_INFORMATION1 in the example used above)

21

34. Save the record. Close the Personalize form and the Extra Information form. Again navigate to the Extra Information page. Enter a value for example Lecturer for Academic Rank and the context sensitive segments are displayed.

22

Configuring Context Sensitive Extra Information Types using Oracle Self-Service HR November 2009 Author: Rosamma Sonia Varghese Contributing Authors: Gyanesh Purohit, Kalyan Tithy Oracle Corporation World Headquarters 500 Oracle Parkway Redwood Shores, CA 94065 U.S.A. Worldwide Inquiries: Phone: +1.650.506.7000 Fax: +1.650.506.7200 oracle.com Copyright © 2009, Oracle. All rights reserved. This document is provided for information purposes only and the contents hereof are subject to change without notice. This document is not warranted to be error-free, nor subject to any other warranties or conditions, whether expressed orally or implied in law, including implied warranties and conditions of merchantability or fitness for a particular purpose. We specifically disclaim any liability with respect to this document and no contractual obligations are formed either directly or indirectly by this document. This document may not be reproduced or transmitted in any form or by any means, electronic or mechanical, for any purpose, without our prior written permission. Oracle, JD Edwards, and PeopleSoft, are registered trademarks of Oracle Corporation and/or its affiliates. Other names may be trademarks of their respective owners.

23