Subject:Understanding and Using Checklist Items in People Management

  Doc ID:744150.1 Type:WHITE PAPER

  Modified Date :17-NOV-2008 Status:PUBLISHED

In this Document
  Abstract
  Document History
  Understanding and Using Checklist Items in People Management
     Introduction
     Define Lookups
     Checklist Window in Enter and Maintain Person Form
     Checklist Tab in People Management
     Background Processing
     Checklist API

Applies to:

Oracle Human Resources - Version: 11.5.10 to 11.5.10.2

Information in this document applies to any platform.

Abstract

This document provides a technical and functional appreciation of the Checklist Item functionality. It is to be
differentiated from the Life Event Checklists available from R12 of Oracle HRMS (see Note 740618.1). It
includes a step by step approach to the setup, and particularly how to set up a tab page in a People
Management template.

Document History

Author : Steve Cooper

Create Date 20-Oct-2008 
Update Date 20-Oct-2008
Expire Date

Understanding and Using Checklist Items in People Management

Introduction

 Prior to the introduction of Life Event Checklists in R12 (See Note 740618.1), checklists were more limited
in scope. Using this method, items can be defined against the lookup_code CHECKLIST_ITEM, which are
then assigned to a person using the Enter and Maintain Person form, or configured to display automatically
on a tab in People Management. They are effectively a list of sign-off items or tasks that can be used for a
variety of functions. For example, during the recruitment process, or an employee's probationary period. The
user can maintain the items with a target date, a completion date, a status and some free text.

This functionality continues to run in parallel with the Life Event Checklists and is an alternative if Oracle
Advanced Benefits hasn't been installed.
Define Lookups

There are lookup_codes seeded against the lookup_type, CHECKLIST_ITEM. Users can add their own
lookup_codes in the Application Utilities Lookups form. They can also add their own statuses against the
lookup_type, CHECKLIST_STATUS.

Other Definitions -> Application Utilities Lookups

Checklist Window in Enter and Maintain Person Form

A checklist window is available for use in Taskflows. In the Taskflow Definitions form add the seeded
CHECKLIST node to your taskflow definition if not already inserted, then include it under the NPERSON
node, for example, so that it can be accessed from the Person window in the Enter and Maintain Person
Form.

It is also available for use as a Fastpath option on the menu. Function name is WSCHK_PERWSCHK.

The window is not configurable, and allows the user to choose any checklist item that has been defined. A
descriptive flexfield, Additional Checklist Item Details, is available to allow the user to capture additional
user-definable information as required.

Checklist Tab in People Management

In People Management you can create a specific Tab Page for Checklist Items, and configure it in such a
way that it only displays the checklist items that you want to see. The following example shows a tab page
entitled Mentor Program with a list of signoff items. You can define one page in the Summary section and
one in the Maintenance Section. A maximum of 10 items can be displayed on each page.
Setup steps on how to create the above Tab page

Navigate to Forms Configurator from Security submenu, pick the template to be modified, and click on Edit
button. Expand template which will give you Windows and Items nodes.

Create Tab Page

1. Expand Windows, and expand the window where the tab page will be created (Summary or
Maintenance), then Expand Tab Pages node.
2. Click on insert icon to create new Tab Page if Checklist not already listed.
3. Enter properties as follows:

            Tab Page Name: Checklist
             Visible: Yes
               Label: <Name of Tab>
Navigation Direction: Left to Right

Create Tab Items

Properties now need to be defined for the Items. As previously mentioned up to 10 Checklist Items can be
arranged on a tab page. They are defined in Forms Configurator as

Checklist n Item Code (Summary)
Checklist n Status (Summary)
Checklist n Date Due (Summary)
Checklist n Date Done (Summary)
Checklist n Notes (Summary)

where n is a number 1 to 10. For a Tab on Maintenance page, Summary would read Maintain.

1.  Expand Items
2. Find Checklist 1 Item Code (Summary) or Checklist 1 Item Code (Maintain) depending on where
you are creating the checklist tab. If the item doesn't exist then add by clicking on insert icon.
3. Enter Properties as follows. Note the Default Value property entered against Item Name, Checklist
1 Item Code (Summary).This is the Meaning of the Lookup_Code defined against the Lookup_Type,
CHECKLIST_ITEM. Insert and Update Allowed is set to No, which prevents users entering other
checklist items in this field. In other words it permanently fixes the position.

Item Name: Checklist 1 Item Code (Summary)
Window Name: Summary Window
Tab Page Name: Checklist
Visible: Yes
Height: 0.25
Width: 1.6
X Position: 0
Y Position: 0.5
Enabled: Yes
Insert Allowed: No
Update Allowed: No
Prompt Text: Checklist Item
Prompt Display Style: First Record
Prompt Text Alignment: Start
Prompt Edge: Top
Prompt Edge Alignment: Start
Prompt Edge Offset: 0.5
Tooltip Text: Checklist Item
Default Value: Induction

Enter Properties for the 4 remaining item fields on the line as follows:

Item Name: Checklist 1 Status (Summary)
Window Name: Summary Window
Tab Page Name: Checklist
Visible: Yes
Height: 0.25
Width: 1.1
X Position: 1.6
Y Position: 0.5
Enabled: Yes
Insert Allowed: Yes
Update Allowed: Yes
Prompt Text: Status
Prompt Display Style: First Record
Prompt Text Alignment: Start
Prompt Edge: Top
Prompt Edge Alignment: Start
Prompt Edge Offset: 0.5
Tooltip Text: Status

Item Name: Checklist 1 Date Due (Summary)
Window Name: Summary Window
Tab Page Name: Checklist
Visible: Yes
Height: 0.25
Width: 1
X Position: 2.7
Y Position: 0.5
Enabled: Yes
Insert Allowed: Yes
Update Allowed: Yes
Prompt Text: Target Date
Prompt Display Style: First Record
Prompt Text Alignment: Start
Prompt Edge: Top
Prompt Edge Alignment: Start
Prompt Edge Offset: 0.5
Tooltip Text: Target Date
Item Name: Checklist 1 Date Done (Summary)
Window Name: Summary Window
Tab Page Name: Checklist
Visible: Yes
Height: 0.25
Width: 1
X Position: 3.7
Y Position: 0.5
Enabled: Yes
Insert Allowed: Yes
Update Allowed: Yes
Prompt Text: Completed
Prompt Display Style: First Record
Prompt Text Alignment: Start
Prompt Edge: Top
Prompt Edge Alignment: Start
Prompt Edge Offset: 0.5
Tooltip Text: Completed

Item Name: Checklist 1 Notes (Summary)
Window Name: Summary Window
Tab Page Name: Checklist
Visible: Yes
Height: 0.25
Width: 1.2
X Position: 4.7
Y Position: 0.5
Enabled: Yes
Insert Allowed: Yes
Update Allowed: Yes
Prompt Text: Notes
Prompt Display Style: First Record
Prompt Text Alignment: Start
Prompt Edge: Top
Prompt Edge Alignment: Start
Prompt Edge Offset: 0.5
Tooltip Text: Notes

Repeat for checklist items 2 thru 10. Note that Y Position should increment by 0.25 for each line. Prompt
properties should be left as null. Default value on Item Code should be set to the meaning of the
lookup_code for the Checklist Item to be displayed.

For more information on People Management Configuration Options, see Extending Oracle HRMS section in
the Oracle HRMS Configuring, Reporting, and System Administration Guide.

Background Processing

There is one main table which holds the allocated checklist rows maintained by the Enter and Maintain
Person window and People Management. This is PER_CHECKLIST_ITEMS. This is an example query from
the table:

set linesize 180

col item_code format a20

col notes format a30
select checklist_item_id,
          item_code,
         date_due,
         date_done,
          notes
  from per_checklist_items
where person_id=99999;

CHECKLIST_ITEM_ID ITEM_CODE            DATE_DUE    DATE_DONE       NOTES
----------------- -------------------- ----------  --------------- --------------
             7041 INDUCTION            27-OCT-08   28-OCT-08       Room 21a
             8042 ENGLISH              20-OCT-08
             8043 PRODTRAIN            25-OCT-08
             8041 SHADOWING            01-DEC-08                   With Sam Smith
             8044 TECHTRAIN            01-DEC-08
             8045 TOOLS                01-DEC-08
             8046 US_CHK_VISA
             8047 US_CHK_VISIT_HIST

8 rows selected.

Checklist API

There is a public API which can be used to add Checklist Items to a person. It's called
per_checklist_items_api ( pechkapi.pkb) and has a create, update and delete procedure. Here is an
example of a call to create a Checklist Item against a person.

set serverout on;

declare
l_person_id number := 99999;
l_object_version_number number;
l_checklist_item_id number;

begin
per_checklist_items_api.create_checklist_items
(p_validate   => FALSE
,p_effective_date  => to_date('01-Nov-2008','DD-MON-YYYY')
,p_person_id  => l_person_id
,p_item_code  => 'INDUCTION'
,p_date_due   => to_date('01-Dec-2008','DD-MON-YYYY')
,p_status   => 'GLB_PENDING'
,p_checklist_item_id  => l_checklist_item_id
,p_object_version_number => l_object_version_number);

dbms_output.put_line ('Person ID: ' || to_char(l_person_id));
end;
/

If running the api gives the following error, it's because it can't find the LOOKUP_CODE you are passing to
p_item_code.

ERROR at line 1:
ORA-20001: HR_52778_CHK_INVALID_ITEM:
ORA-06512: at "APPS.PER_CHECKLIST_ITEMS_API", line 276
ORA-06512: at line 7
If the lookup_code is present, the error may be occurring because it was created in a security group other
than standard. If so, it wll be necessary to initialize the APPS environment before running the api. e.g. by
executing fnd_global.apps_initialize with the appropriate parameters.