Oracleâ Project Resource Management

Implementation and Administration Guide

Release 11i

September, 2002
Part No. B10049-01
Oracle Project Resource Management Implementation and Administration Guide, Release 11i

Part No. B10049-01

Copyright © 2000, 2002 Oracle Corporation. All rights reserved.

Primary Author: Juli Anne Tolley

Contributing Authors: Angela Chen, Nalin Chouhan, Rupal Fadia, Guriqpal Gill, Jason Hardy-Smith, John D.
May, Hamid Mirlohi, Matt Ness, Vijay Ranganathan, Johanna Rusly, Emma Selby, Selva Sivaramakrishnan,
Abhishek Uppal

Contributors: Janet Buchbinder, Neeraj Garg, Danielle Hafdal, Dinakar Hituvalli, Shreekar Inamdar, Sanjay
Kumar Kannojia, Ramesh Krishnamurthy, Jeanne Lowell, Johnson Paulraj, Mark Rowe, Mary Sun, Tianyi Wang

The Programs (which include both the software and documentation) contain proprietary information of Oracle
Corporation; they are provided under a license agreement containing restrictions on use and disclosure and are also
protected by copyright, patent, and other intellectual and industrial property laws. Reverse engineering,
disassembly, or decompilation of the Programs is prohibited.

The information contained in this document is subject to change without notice. If you find any problems in the
documentation, please report them to us in writing. Oracle Corporation does not warrant that this document is error
free. Except as may be expressly permitted in your license agreement for these Programs, no part of these Programs
may be reproduced or transmitted in any form or by any means, electronic or mechanical, for any purpose, without
the express written permission of Oracle Corporation.

If the Programs are delivered to the U.S. Government or anyone licensing or using the programs on behalf of the
U.S. Government, the following notice is applicable:

Restricted Rights Notice Programs delivered subject to the DOD FAR Supplement are "commercial computer
software" and use, duplication, and disclosure of the Programs, including documentation, shall be subject to the
licensing restrictions set forth in the applicable Oracle license agreement. Otherwise, Programs delivered subject to
the Federal Acquisition Regulations are "restricted computer software" and use, duplication, and disclosure of the
Programs shall be subject to the restrictions in FAR 52.227-19, Commercial Computer Software - Restricted Rights
(June, 1987). Oracle Corporation, 500 Oracle Parkway, Redwood City, CA 94065.

The Programs are not intended for use in any nuclear, aviation, mass transit, medical, or other inherently dangerous
applications. It shall be the licensee's responsibility to take all appropriate fail-safe, backup, redundancy, and other
measures to ensure the safe use of such applications if the Programs are used for such purposes, and Oracle
Corporation disclaims liability for any damages caused by such use of the Programs.

Oracle is a registered trademark, and Oracle Financials, Oracle Discoverer, and OracleMetaLink are trademarks or
registered trademarks of Oracle Corporation. Other names may be trademarks of their respective owners.
 Contents

Send Us Your Comments .................................................................................................................. xv

Preface......................................................................................................................................................... xvii

1 Introduction
Key Features......................................................................................................................................... 1-2
Required Technology Stack .............................................................................................................. 1-3
Implementation Planning ................................................................................................................. 1-4
Determining the Deployment Method........................................................................................... 1-5

2 User Process Flows and Concepts

Defining a Project Team .................................................................................................................... 2-2
Standard Task Flows .......................................................................................................................... 2-3
Application Process Flows ................................................................................................................ 2-5
Creating Requirements ................................................................................................................ 2-5
Performing a Resource Search .................................................................................................... 2-5
Filling Requirements .................................................................................................................... 2-5
Adding Assignments to Projects ................................................................................................ 2-6
Creating Administrative Assignments...................................................................................... 2-6

3 Establishing Your Enterprise Structure

Setting Up Your Business Group Model........................................................................................ 3-2
Defining Organizations..................................................................................................................... 3-3
Understanding the Resource Operating Unit........................................................................... 3-3

iii
 Defining Organizational Hierarchies ............................................................................................. 3-4
Defining Jobs and Job Mapping...................................................................................................... 3-5
Defining Job Relationships .......................................................................................................... 3-6
Specifying the Job Levels for Searches....................................................................................... 3-6

4 Defining Your People

Understanding Resource Pool Benefits .......................................................................................... 4-2
Performing Searches on Your Resource Pool ........................................................................... 4-2
Defining Employees and Employee Assignments ....................................................................... 4-5
Defining Employees ..................................................................................................................... 4-5
Defining Employee Assignments ............................................................................................... 4-6
Defining Locations........................................................................................................................ 4-6
Setting Up Competencies .................................................................................................................. 4-7
Defining Your Competence Structure ....................................................................................... 4-7
Assigning Competencies ............................................................................................................. 4-9
Assigning Job Competencies ............................................................................................... 4-9
Assigning Project Role Competencies ................................................................................ 4-9
Assigning Requirement Competencies ............................................................................ 4-10
Assigning Resource Competencies ................................................................................... 4-10
Matching Resource and Requirement Competencies .................................................... 4-11
Assigning Global and Local Competencies ..................................................................... 4-11
Acquiring Your Resources From Oracle HRMS.......................................................................... 4-13
Qualifying Criteria for the Resource Pull................................................................................ 4-13
Running the PRC: Maintain Project Resources Process ........................................................ 4-14
Migrating Resource Data From Other Systems...................................................................... 4-15
Migrating Data for a New Instance................................................................................. 4-15
Migrating Data for an Existing Instance ........................................................................ 4-16

5 Configuring Your Organization Security

Defining Your Security Strategy ...................................................................................................... 5-2
Understanding Responsibility-Based Security............................................................................. 5-3
Defining Additional User Level Security .................................................................................. 5-3
Authority at the Organization Level .................................................................................. 5-3
User with View All Projects Access .................................................................................... 5-3
User with Update All Projects Access ............................................................................... 5-4

iv
 User with View All Resources Access................................................................................ 5-4
Understanding Role-Based Security ............................................................................................... 5-5
Levels of Role-Based Security ..................................................................................................... 5-5
Predefined Roles ........................................................................................................................... 5-5
Project Manager ..................................................................................................................... 5-6
Project Staffing Owner.......................................................................................................... 5-6
Project Authority ................................................................................................................... 5-6
Resource Authority ............................................................................................................... 5-6
Utilization Authority ............................................................................................................ 5-6
Forecast Authority................................................................................................................. 5-6
Predefined Responsibilities......................................................................................................... 5-6
Overview of Predefined Responsibility Function and Menu Access ................................... 5-8
Detailed Predefined Function Access by Responsibility ...................................................... 5-10
Predefined Function Access by Menu ..................................................................................... 5-14
Defining Organizational Authority .............................................................................................. 5-21
Defining a Primary Contact ...................................................................................................... 5-21
Assigning Organizational Authority ....................................................................................... 5-22
Demonstrating a Security Check ................................................................................................... 5-23
Setting Up Security for Viewing Financial Amounts................................................................ 5-25

6 Defining Project Roles

Definition of a Project Role .............................................................................................................. 6-2
How Project Roles are Used........................................................................................................ 6-2
Overview of Predefined Role Controls .......................................................................................... 6-3
Defining Role Lists............................................................................................................................. 6-4
Defining Project Roles....................................................................................................................... 6-5

7 Setting Up Staffing Capabilities

Overview of Predefined Statuses and Status Controls ............................................................... 7-2
Defining Requirement Statuses and Profile Options ................................................................. 7-3
Predefined Requirement Statuses and Status Controls .......................................................... 7-3
Requirement Status Profile Options .......................................................................................... 7-3
PA: Starting Requirement Status......................................................................................... 7-3
PA: Default Filled Requirement Status .............................................................................. 7-4
PA: Default Cancelled Requirement Status....................................................................... 7-4

v
 Defining Staffing Priorities for Team Roles .............................................................................. 7-4
Defining the Team Role Descriptive Flexfield.......................................................................... 7-4
Setting Up Candidate Processing .................................................................................................... 7-5
Defining Candidate Statuses and Profile Options ................................................................... 7-5
Predefined Candidate Statuses and Status Controls ........................................................ 7-5
Candidate Status Profile Options........................................................................................ 7-6
PA: Default Starting Candidate Status........................................................................ 7-6
PA: Cancelled Requirement's Candidate Status ........................................................ 7-7
PA: Invalid Resource Candidate Status ...................................................................... 7-7
Understanding the Candidate Score and the Automated Nomination Process.................. 7-7
Candidate Score Weightings................................................................................................ 7-7
Automated Search and Nomination Process..................................................................... 7-8
Submitting the PRC: Automated Candidate Search Process .......................................... 7-9
Submitting the Process for a Single Project ................................................................ 7-9
Submitting the Process for Multiple Projects ............................................................. 7-9
Defining and Setting Up Advertisement Rules.......................................................................... 7-10
Overview of Advertisement Rules........................................................................................... 7-10
Advertisement Rule Actions.............................................................................................. 7-10
Advertisement Rule Action Conditions ........................................................................... 7-11
Advertisement Rule Statuses ............................................................................................. 7-12
Project Staffing Owner........................................................................................................ 7-12
Advertisement Rule Processes.................................................................................................. 7-13
Obtaining a Default Advertisement Rule ........................................................................ 7-13
Processing Advertisement Actions ................................................................................... 7-13
Reversing Advertisement Rule Actions ........................................................................... 7-14
Replacing an Advertisement Rule .................................................................................... 7-15
Auditing Advertisement Rule Activities ......................................................................... 7-15
Implementing Advertisement Rule Functionality ................................................................. 7-15
Defining Advertisement Rules .......................................................................................... 7-16
Specifying the Default Advertisement Rule .................................................................... 7-16
Submitting the PRC: Perform Action Rules Process ...................................................... 7-16
Defining Assignments Statuses and Profile Options................................................................ 7-17
Predefined Assignment Schedule Statuses and Status Controls ......................................... 7-17
Predefined Assignment Approval Statuses ............................................................................ 7-17
Assignment Status Profile Options .......................................................................................... 7-18

vi
 PA: Starting Assignment Status ........................................................................................ 7-18
PA: Default Cancelled Assignment Status ...................................................................... 7-18

8 Defining Calendars and Schedules

Setting Up Calendars ......................................................................................................................... 8-2
Creating Calendars and Defining Calendar Attributes .......................................................... 8-2
Defining Calendar Types ..................................................................................................... 8-2
Defining Shift and Shift Patterns......................................................................................... 8-3
Creating Calendar Exceptions ............................................................................................. 8-4
Creating a Calendar .............................................................................................................. 8-4
Assigning Shifts and Exceptions to Calendar ................................................................... 8-4
Changing the Calendar ................................................................................................. 8-4
Establishing Default Calendars .................................................................................................. 8-5
Defining the Default Calendar for the Site ........................................................................ 8-5
Defining Default Calendars for Organizations ................................................................. 8-5
Assigning Calendars .................................................................................................................... 8-5
Assigning Calendars to Projects.......................................................................................... 8-5
Assigning Calendars to Resources...................................................................................... 8-5
Establishing the Availability and Overcommitment Calculations........................................... 8-7
Overview of the Availability Calculation ................................................................................. 8-7
Setup Requirements for the Availability Calculation ...................................................... 8-7
Defining GL Periods and PA Periods for Availability Purposes ............................ 8-7
Defining Forecast Options for Scheduling Purposes ................................................ 8-8
Overview of the Overcommitment Calculation....................................................................... 8-8
Defining Availability and Overcommitment Profile Options ............................................... 8-9

9 Defining the Project Environment

Creating Project Attributes ............................................................................................................... 9-2
Establishing Probability Information............................................................................................. 9-3
Setting Up the Predefined Project Status Controls...................................................................... 9-3
Setting Up Your Self-Service Environment ................................................................................... 9-5
Self-Service Web Applications Profile Options........................................................................ 9-5
Configuring the Project Home Page .......................................................................................... 9-6
Specifying the Project Header Section................................................................................ 9-7
Enabling Project Shortcut Links ................................................................................................. 9-7

vii
 Predefined Shortcut Links.................................................................................................... 9-8
Project Shortcut Links .................................................................................................... 9-8
Resource Shortcut Links................................................................................................ 9-8
Reporting Shortcut Links .............................................................................................. 9-8
Configuring Table Views............................................................................................................. 9-9

10 Implementing Financial Forecasting

Overview of the Financial Forecast Process and Calculations................................................. 10-2
Financial Forecast Process ......................................................................................................... 10-2
Forecast Calculations.................................................................................................................. 10-3
Calculating Revenue ........................................................................................................... 10-3
Revenue Calculation for Projects Using Work-Based Distribution Rule ............. 10-4
Revenue Calculation for Projects Using Cost-Based Distribution Rule ............... 10-4
Revenue Calculation for Projects Using Event-Based Distribution Rule............. 10-5
Generating Forecast Information.............................................................................................. 10-5
Implementing the Forecast Functionality .................................................................................... 10-6
Defining a Job-Based Cost Rate Schedule ............................................................................... 10-6
Defining Bill Rate Schedules ..................................................................................................... 10-7
Updating Project Types with Employee and Job-Based Bill Rate Schedules..................... 10-7
Defining Forecast-Related Profile Option ............................................................................... 10-7
Defining Periods ......................................................................................................................... 10-7
Defining Unassigned Time Tracking ....................................................................................... 10-8
Defining Forecasting Options ................................................................................................... 10-9
Implementation Options .................................................................................................. 10-10
Unassigned Time Options ................................................................................................ 10-12
Establishing Security on Forecast Functionality....................................................................... 10-13
Granting Cost Viewing Access to Roles ................................................................................ 10-13
Granting Forecast Authority ................................................................................................... 10-13
Granting Forecast Function Access ........................................................................................ 10-14

11 Implementing Resource Utilization

Defining Your Utilization Strategy ............................................................................................... 11-2
Utilization Time Periods ............................................................................................................ 11-3
Understanding the Utilization Views ...................................................................................... 11-3
Choosing a Utilization Calculation Method ........................................................................... 11-4

viii
 Using the Capacity Calculation Method.......................................................................... 11-4
Using the Total Worked Hours Calculation Method..................................................... 11-4
Understanding the Utilization Reporting ............................................................................... 11-5
Reviewing the Organization Utilization Page ................................................................ 11-6
Employees and Others (Summary) ........................................................................... 11-6
Employees and Others (Sub-Organization Details) ................................................ 11-6
Actual Capacity (same as Forecast Capacity) .......................................................... 11-6
Actual Worked.............................................................................................................. 11-6
Weighted Actual........................................................................................................... 11-6
Actual Utilization (%) .................................................................................................. 11-7
Forecast Work ............................................................................................................... 11-7
Weighted Forecast........................................................................................................ 11-7
Forecast Utilization (%) ............................................................................................... 11-7
Reviewing the Resource Utilization by Organization Manager Page ......................... 11-7
Employees and Others (Summary) ........................................................................... 11-7
Person Details ............................................................................................................... 11-8
Reviewing the Resource Utilization by Resource Manager Page ................................ 11-8
Employees and Others ................................................................................................ 11-8
Actual Capacity (same as Forecast Capacity) .......................................................... 11-8
Actual Worked.............................................................................................................. 11-8
Weighted Actual........................................................................................................... 11-9
Actual Utilization (%) .................................................................................................. 11-9
Forecast Work ............................................................................................................... 11-9
Weighted Forecast........................................................................................................ 11-9
Forecast Utilization (%) ............................................................................................... 11-9
Reviewing the Personal Utilization Page......................................................................... 11-9
Capacity Amount ......................................................................................................... 11-9
Capacity Hours........................................................................................................... 11-10
Worked Hours ............................................................................................................ 11-10
Utilization.................................................................................................................... 11-10
(Forecast) Provisional Hours .................................................................................... 11-10
(Forecast) Confirmed Hours..................................................................................... 11-10
(Forecast) Utilization ................................................................................................. 11-10
Correlation of Utilization Totals ..................................................................................... 11-10
Implementing Your Utilization Strategy.................................................................................... 11-12

ix
 Determining Utilization Jobs .................................................................................................. 11-12
Establishing Utilization Categories and Work Types ......................................................... 11-13
Defining Utilization Categories....................................................................................... 11-13
Creating Utilization Categories................................................................................ 11-13
Using Utilization Categories..................................................................................... 11-13
Defining Work Types........................................................................................................ 11-14
Creating Work Types................................................................................................. 11-14
Using Work Types...................................................................................................... 11-15
Implementing Utilization Forecasting Functionality .......................................................... 11-16
Establishing Unassigned Time Tracking............................................................................... 11-16
Choosing Your Reporting Time Period ................................................................................. 11-16
Granting Utilization Authority............................................................................................... 11-17
Review of Responsibilities ............................................................................................... 11-17
Granting Organization Utilization Authority ............................................................... 11-18
Defining the Utilization Profile Options ................................................................................... 11-19

12 Setting Up for Reporting Capabilities

Oracle Discoverer 4i Postinstallation Tasks................................................................................. 12-2
Oracle Discoverer 3i Postinstallation Tasks................................................................................. 12-3
Oracle Discoverer Postinstallation Tasks Checklist............................................................... 12-3
Create the End User Layer ................................................................................................. 12-4
Creating the Database User ........................................................................................ 12-4
Creating the Applications Mode EUL ....................................................................... 12-4
Modify the Indexes of the End User Layer Owner......................................................... 12-6
Copy Files to Discoverer Administration Tier ................................................................ 12-6
Connect to Discoverer Administration Edition .............................................................. 12-7
Import the End User Layer EEX File ................................................................................ 12-7
Set Up Access to Business Areas and End User Discoverer Edition............................ 12-8
Refresh Business Areas ....................................................................................................... 12-9
Connect to Discoverer User Edition ................................................................................. 12-9
Install the Project Resource Management Reporting Workbooks for Discoverer ... 12-10
Set Up Access to the Reporting Workbooks .................................................................. 12-11
Test Your Installation and Set Up ................................................................................................ 12-11
Overview of the Business Areas and Business Views............................................................. 12-12
List of Business Areas............................................................................................................... 12-12

x
 Staffing Business Area ...................................................................................................... 12-12
Financial Business Area.................................................................................................... 12-14
List of Staffing Business Area Folders ................................................................................... 12-15
Staffing Organization Rollup Groups ............................................................................ 12-15
Resource Managers ........................................................................................................... 12-16
Fiscal Years ......................................................................................................................... 12-16
Fiscal Quarter Numbers ................................................................................................... 12-16
Calendar Years................................................................................................................... 12-16
Calendar Months ............................................................................................................... 12-17
Work Types ........................................................................................................................ 12-17
Required Project Hours by GL Period............................................................................ 12-17
Required Project Hours by GL Period: Team Role Detail ........................................... 12-18
Required Project Hours by PA Period............................................................................ 12-18
Required Project Hours by PA Period: Team Role Detail ........................................... 12-19
Required Project Hours by Global Week ....................................................................... 12-20
Required Project Hours by Global Week: Team Role Detail ...................................... 12-20
Resource Capacity by GL Period .................................................................................... 12-21
Resource Capacity by PA Period .................................................................................... 12-22
Resource Capacity by Global Week................................................................................ 12-22
Resource Schedule by GL Period .................................................................................... 12-23
Resource Schedule by GL Period: Team Role Detail.................................................... 12-24
Resource Schedule by PA Period .................................................................................... 12-25
Resource Schedule by PA Period: Team Role Detail.................................................... 12-26
Resource Schedule by Global Week ............................................................................... 12-27
Resource Schedule by Global Week: Team Role Detail ............................................... 12-28
Resource Schedule and Capacity by Global Week ....................................................... 12-29
Available Resource Hours by Global Week .................................................................. 12-30
Resource Overcommitment by Global Week ................................................................ 12-31
List of Financial Business Area Folders................................................................................. 12-32
Financial Organization Rollup Groups .......................................................................... 12-32
Project Managers ............................................................................................................... 12-32
Fiscal Years ......................................................................................................................... 12-33
Fiscal Quarter Numbers ................................................................................................... 12-33
Project Role Types ............................................................................................................. 12-33
Project Members ................................................................................................................ 12-33

xi
 Sales Pipeline by GL Period ............................................................................................. 12-33
Sales Pipeline by PA Period ............................................................................................. 12-35
Lookup for Class Categories ............................................................................................ 12-36
List of Competence Business Area Folders........................................................................... 12-36
Organization Competence Summary ............................................................................. 12-36
Resource Listing for Organization and Competence ................................................... 12-37
Resource Competence Details ......................................................................................... 12-37
Organization Resource Competencies............................................................................ 12-38
Project Resource Competencies....................................................................................... 12-38
Resource Projects ............................................................................................................... 12-39
Competence Organization Rollup Groups .................................................................... 12-39
Competencies ..................................................................................................................... 12-40
Include Sub Organizations............................................................................................... 12-40
Billable Job Only ................................................................................................................ 12-40
Resources ............................................................................................................................ 12-40
All Resource Managers ..................................................................................................... 12-41
Jobs....................................................................................................................................... 12-41
Job Levels ............................................................................................................................ 12-41
List of Business Views.............................................................................................................. 12-42
Security Overview .......................................................................................................................... 12-44
Discoverer Workbooks................................................................................................................... 12-44
Required Project Hours (PAREQPRJ).................................................................................... 12-45
Required Project Hours by GL Period............................................................................ 12-46
Required Project Hours by PA Period............................................................................ 12-47
Required Project Hours by Global Week ....................................................................... 12-49
Scheduled Resource Hours (PASCHRES)............................................................................. 12-51
Scheduled Resource Hours by GL Period...................................................................... 12-51
Scheduled Resource Hours by PA Period...................................................................... 12-54
Scheduled Resource Hours by Global Week ................................................................. 12-56
Available Resource Hours (PAAVLRES) .............................................................................. 12-58
Available Resource Hours by GL Period ....................................................................... 12-59
Available Resource Hours by PA Period ....................................................................... 12-61
Available Resource Hours by Global Week .................................................................. 12-63
Overcommitted Resource Hours (PAOVCRES)................................................................... 12-65
Overcommitted Resource Hours by GL Period ............................................................ 12-65

xii
 Overcommitted Resource Hours by PA Period............................................................ 12-67
Overcommitted Resource Hours by Global Week ....................................................... 12-70
Project Pipeline Workbook (PASALPIP)............................................................................... 12-72
Project Pipeline by Fiscal Year......................................................................................... 12-73
Project Pipeline by Fiscal Quarter.................................................................................. 12-75
Project Pipeline by GL Period.......................................................................................... 12-77
Project Pipeline by PA Period.......................................................................................... 12-79
Organization Competence Summary Workbook (PA_PRM_ORG_COMP_SUM) ........ 12-81
Organization Competence Summary Worksheet......................................................... 12-81
Resource Listing for Organization and Competence Worksheet............................... 12-83
Resource Competencies Workbook (PA_PRM_RES_COMP)............................................ 12-84
Organizaton Resource Competencies ............................................................................ 12-84
Project Resource Competencies....................................................................................... 12-86
Resource Competence Details ......................................................................................... 12-87
Discoverer Query Tips ................................................................................................................... 12-89

13 Maintaining Your Data

Understanding Data Processing..................................................................................................... 13-2
Understanding the Impact of Changes to HRMS-Based Information ................................... 13-3
Changing Job Information......................................................................................................... 13-3
Job Levels.............................................................................................................................. 13-3
Job Billability ........................................................................................................................ 13-4
Utilization Calculation........................................................................................................ 13-4
Changing Organization Information ....................................................................................... 13-4
Changing Organizational Hierarchy Information ................................................................. 13-4
Changing Resource Information .............................................................................................. 13-5
Changing an Assignment .......................................................................................................... 13-5
Maintaining Schedules.................................................................................................................... 13-6
Updating Schedules with Calendar Changes......................................................................... 13-6
Updating Schedules and Timelines to Reflect a New Calendar.......................................... 13-7
Maintaining Utilization Values ..................................................................................................... 13-8
Maintaining Forecast Information ................................................................................................ 13-9
Running a List of Forecast Exceptions..................................................................................... 13-9
Reprocess Forecast Exceptions ............................................................................................... 13-10

xiii
14 Overview of the Predefined Workflows
Initiating Deferred Workflow Processes ...................................................................................... 14-2
Available Item Types ................................................................................................................. 14-2
Recommended Process Scheduling Parameters..................................................................... 14-3
Assignment Approval Workflow Process .................................................................................... 14-4
Assignment Approval Workflow Item Type and Processes ................................................ 14-5
Assignment Approval Workflow Notification Messages..................................................... 14-6
Assignment Schedule Statuses ................................................................................................. 14-7
Assignment Approval Workflow Extensions......................................................................... 14-8
Assignment Approval Changes Extension ...................................................................... 14-8
Assignment Approval Notification Extensions .............................................................. 14-9
Candidate Workflow Processes .................................................................................................... 14-13
Candidate Notification Workflow Extension ....................................................................... 14-13

A Implementation Steps Checklist

Overview of the Implementation Environment ........................................................................... A-2
Oracle Applications Implementation Wizard .......................................................................... A-2
Setting Up Underlying Oracle Applications Technology ....................................................... A-2
Implementation Considerations ...................................................................................................... A-3
Overview of the Oracle Projects Implementation Checklists.................................................... A-4
Oracle Projects Implementation Checklist .................................................................................... A-5
Oracle Applications Implementation Checklist for Oracle Projects Integration................. A-27

Glossary

Index

xiv
 Send Us Your Comments
Oracle Project Resource Management Implementation and Administration Guide, Release 11i
Part No. B10049-01

Oracle Corporation welcomes your comments and suggestions on the quality and usefulness of this
document. Your input is an important part of the information used for revision.
■ Did you find any errors?
■ Is the information clearly presented?
■ Do you need more information? If so, where?
■ Are the examples correct? Do you need more examples?
■ What features did you like most?

If you find any errors or have any other suggestions for improvement, please indicate the document
title and part number, and the chapter, section, and page number (if available). You can send com-
ments to us in the following ways:
■ FAX: (650) 506-7862 Attn: Oracle Financial Applications Documentation
■ Postal service:
Oracle Corporation
Financial Applications Documentation, Oracle Project Resource Management
500 Oracle Parkway, M/S 3op11
Redwood Shores, CA 94065
USA
If you would like a reply, please give your name, address, telephone number, and (optionally) elec-
tronic mail address.

If you have problems with the software, please contact your local Oracle Support Services.

xv
xvi
 Preface

This guide provides you with information on how to implement Oracle Resource
Management, Release 11i, Oracle Projects Family Pack J (11i.PF_PJ.J). This preface
describes the organization of this guide.

Intended Audience
The intended audience for the material presented in this guide is system
administrators and persons responsible for performing the duties of implementing,
configuring, and administrating the Oracle Project Resource Management
application.

Structure
The organization of this guide is as follows:
Chapter 1, "Introduction" describes the purpose and key features of the product. It
also covers the required technology stack and implementation considerations.
Chapter 2, "User Process Flows and Concepts" discusses the various user and
process flows within Oracle Project Resource Management.
Chapter 3, "Establishing Your Enterprise Structure" covers how to set up your
organization and its various components such as business groups and
organizational hierarchies.
Chapter 4, "Defining Your People" discusses how to define the various resource
attributes and how to establish your resource pool.
Chapter 5, "Configuring Your Organization Security" describes responsibility-based
security and how to establish a security structure for your organization.

xvii
 Chapter 6, "Defining Project Roles" discusses how to define roles and role attributes.
Chapter 7, "Setting Up Staffing Capabilities" describes how to define staffing-related
attributes, profile options, and statuses.
Chapter 8, "Defining Calendars and Schedules" describes calendars and schedules,
and covers how to define the associated attributes. It also describes how to maintain
the calendars and schedules so they stay current.
Chapter 9, "Defining the Project Environment" describes the attributes associated
with projects, setting up probability, establishing the status and workflow
structures, and setting up the self-service environment.
Chapter 10, "Implementing Financial Forecasting" describes how to set up
forecasting functions so you can perform forecasting on your project resources.
Chapter 11, "Implementing Resource Utilization" describes how to set up utilization
functions for tracking your resource utilization.
Chapter 12, "Setting Up for Reporting Capabilities" covers how to set up reporting
functions in order for you to perform reporting on your projects and resources. This
chapter also describes the predefined reports.
Chapter 13, "Maintaining Your Data" discusses the various processes you must run
in order to maintain accuracy in your data.
Chapter 14, "Overview of the Predefined Workflows" explains predefined
workflows and the extensions that you can customize.
Appendix A, "Implementation Steps Checklist" provides a step-by-step checklist for
implementing the Oracle Project Resource Management application.
This guide also includes a Glossary and an Index.

Related Documents
The chapters of this guide provide basic and product-related information for setting
up, configuring, and maintaining information such as your enterprise structure,
resources, calendars, and schedules. For additional information, you are referred to
other sources of information as appropriate for the topic. Depending upon which
application you are using to perform the set up, your reference source may differ.
These sources include:
■ Oracle Applications User Guide
■ Oracle Alert User Guide

xviii
 ■ Oracle Applications Implementation Wizard User Guide
■ Oracle Applications Developer’s Guide
■ Oracle Applications User Interface Standards
■ Oracle Self-Service Web Applications Implementation Guide
■ Managing People Using Oracle HRMS
■ Oracle Applications Concepts
■ Installing Oracle Applications
■ Upgrading Oracle Applications
■ Oracle Applications Product Update Notes
■ Oracle Applications System Administrator’s Guide
■ Oracle Workflow Guide
■ Oracle Applications Flexfields Guide
■ The OA Framework - Release Notes & Configuration for the Phase 5.5 Release
■ Oracle Projects User Guide
■ Implementing Oracle HRMS
■ Oracle Projects 11i Release 11.5.3/Mini Pack B User Guide Supplement
■ Documentation Update for Patch Numbers 1383905 and 1377992 - Global
Competencies
■ Oracle Applications System Administrator’s Guide
■ Oracle Applications Developer’s Guide

Documentation Accessibility
Our goal is to make Oracle products, services, and supporting documentation
accessible, with good usability, to the disabled community. To that end, our
documentation includes features that make information available to users of
assistive technology. This documentation is available in HTML format, and contains
markup to facilitate access by the disabled community. Standards will continue to
evolve over time, and Oracle Corporation is actively engaged with other
market-leading technology vendors to address technical obstacles so that our
documentation can be accessible to all of our customers. For additional information,

xix
 visit the Oracle Accessibility Program Web site at
http://www.oracle.com/accessibility/.

Accessibility of Links to External Web Sites in Documentation

This documentation may contain links to Web sites of other companies or
organizations that Oracle Corporation does not own or control. Oracle Corporation
neither evaluates nor makes any representations regarding the accessibility of these
Web sites.

xx
Conventions
The following conventions are used in this guide:

Convention Meaning
. Vertical ellipsis points in an example mean that information not
. directly related to the example has been omitted.
.
... Horizontal ellipsis points in statements or commands mean that
parts of the statement or command not directly related to the
example have been omitted
boldface text Boldface type in text indicates a term defined in the text, the glossary,
or in both locations.
<> Angle brackets enclose user-supplied names.

[] Brackets enclose optional clauses from which you can choose one or
none.

Since Oracle Project Resource Management is a self-service application, references

to a page within the application are specific to a self-service Web page. Any
references to forms refers to forms within the Oracle Projects, Oracle Human
Resources Management System (HRMS), or Oracle CRM applications.

xxi
xxii
 1
Introduction

Oracle Project Resource Management is a self-service application to manage the

deployment and capacity of your resources in a global environment. You use this
application to manage your project resource needs, project profitability, and
organization utilization, by locating and deploying qualified and available
resources to your projects across your global, extended enterprise.
Using this application, project managers, resource managers, and staffing managers
throughout your enterprise can manage their resources and more effectively
communicate their needs to one another.
This chapter discusses the key features of the Oracle Project Resource Management
application and considerations to review in your implementation process through
the following topics:
■ Key Features
■ Required Technology Stack
■ Implementation Planning
■ Determining the Deployment Method

Introduction 1-1
Key Features

Key Features
The Oracle Project Resource Management application includes features such as:
■ Role-based security
■ Detailed requirement definition
■ Search functions for:
■ matching qualified resources to open requirements
■ locating requirements for which resources may nominate themselves
■ Tracking candidates for filling requirements
■ Automated approval processing
■ Detailed schedule management of your project team, including timeline views
■ Utilization reporting on your resource assignments from the individual
resource level to the organization level
■ Capabilities for performing analysis and financial forecasts on your projects
■ Simple Web interface for easy access by all project stakeholders
■ Complete project and customer sales history access through the integration
with Oracle Sales Online

1-2 Oracle Project Resource Management Implementation and Administration Guide

 Required Technology Stack

Required Technology Stack

Prior to installing the Oracle Project Resource Management application, you must
install other software components that build a base. This base provides the structure
for the Oracle Project Resource Management application.
The required base installation for Oracle Project Resource Management is Oracle
Applications, Release 11i.
You must upgrade your Oracle Applications Web Tier environment to include the
Self-Service Framework technology stack. The instructions for upgrading your
Oracle Applications Environment to use the Oracle Applications Self-Service
Framework are included with the framework patch in
README-Config-FAQ-Apps-HTTPServer.html located under the top level patch
directory. Please complete all steps in those instructions before proceeding with the
installation of Oracle Project Resource Management.
For additional information on installing these products and patches, you can refer
to the following sources:
■ Installing Oracle Applications, Release 11i
■ Associated readme files for each patch

Introduction 1-3
Implementation Planning

Implementation Planning
Since Oracle Project Resource Management is integrated with applications such as
Oracle Projects, Oracle Human Resources Management System (HRMS), and Oracle
CRM, many interdependencies exist. Careful planning is required because of these
interdependencies. A large portion of the information you must enter for your
implementation is actually loaded through these applications. Therefore, you
should create an implementation plan. Use the checklist provided in Appendix A as
a starting point for this plan because it identifies all the required and optional steps
for your implementation.

Shared Data
All organization and employee data is stored in Oracle HRMS tables. As most of
these tables are shared, you can enter this information using Oracle HRMS and
access the information through other Oracle applications such as Oracle Projects.
However, if your business does not currently use Oracle HRMS, you can define the
resource data through Oracle Projects. For more information, refer to Chapter 17,
"Oracle Projects Setup and Implementation," in the Oracle Projects User Guide,
Volume 3.

1-4 Oracle Project Resource Management Implementation and Administration Guide

 Determining the Deployment Method

Determining the Deployment Method

Prior to implementing Oracle Project Resource Management, you must determine
how you want to handle project staffing. You have three possible approaches in
addressing who manages the task of project staffing:
■ Centralized
The centralized approach uses staffing analysts (resource analysts.) These
analysts are responsible for managing requirements and assignments for all the
projects of an organization.
■ Decentralized
The decentralized approach uses project managers, or project assistants, who
work with resource managers to fill project requirements.
■ Combination
The combination approach is used by companies who have all these roles
interacting in the effort to fill project requirements and to obtain the highest
utilization of the available resources.
The method you choose effects how you roll out the implementation of the
application, how you establish training plans, and determines your security
strategy.

Introduction 1-5
Determining the Deployment Method

1-6 Oracle Project Resource Management Implementation and Administration Guide

 2
User Process Flows and Concepts

The Oracle Project Resource Management application provides functionality to meet the
needs of several key user scenarios, each with its own set of responsibilities and related task
flows. You can adapt these scenarios into your environment, or modify them accordingly.
Understanding the process flows and user concepts of the application provides you with the
appropriate knowledge for making key decisions for your implementation.
This chapter covers the following topics:
■ Defining a Project Team
■ Standard Task Flows
■ Application Process Flows

User Process Flows and Concepts 2-1

Defining a Project Team

Defining a Project Team

A project team has two layers: the delivery team and the extended team. The delivery team
consists of all the key members who perform the project tasks. These members are
scheduled and tracked within the organization that owns the project. The extended team
consists of team players outside of the project team such as individuals within the
organization performing administrative duties and client participants. These players interact
with the team members, but are not managed within the organization owning the project.
The following diagram demonstrates how the delivery team and extended team own
requirements and assignments.

Administrative assignments are not included in the domain of the delivery team as these
assignments are typically tracked on an indirect/administrative project. Therefore, to
distinguish these assignments from delivery assignments, they are shown outside the
framework of the project team. Administrative projects can have project managers who
manage these assignments, but having a project manager is not a requirement.

2-2 Oracle Project Resource Management Implementation and Administration Guide

 Standard Task Flows

Standard Task Flows

You can divide the overall process flow of Oracle Project Resource Management into three
segments: Demand, Supply, and Financial Management. The borders dividing these
segments are not definite. In fact, many of the tasks are shared between segments.
The segments demonstrate how Oracle Project Resource Management addresses the
different, but related, tasks and viewpoints needing access to project staffing data.
Different needs coming together to use the same data.
The following diagram illustrates how the different needs of the users can use the
same data through process flows. It also provides the segment division of task flows
and the various user roles that might use these segments.

The objectives of the role a user is playing on a project drives the tasks the user
must perform. The implementation of Oracle Project Resource Management
provides predefined roles to which you can add your own to suit your business

User Process Flows and Concepts 2-3

Standard Task Flows

needs. In the above diagram, typical user roles are associated with the applicable
process segments. For example, a Financial Analyst performs tasks related to
financial management, and a Project Manager concentrates on tasks relating to
project staffing from the demand side.
In general, you have the following typical user roles to address the issues of project
staffing:
■ Project Manager
A project manager initiates the creation of the project and requirements. In
order to fill the requirements, the project manager must perform searches from
which candidates can be identified. Once a candidate is selected, a provisional
assignment is created for the resource. The provisional assignment is forwarded
to the resource manager or primary contact for approval. If the project manager
wants specific persons to fill requirements, the search step can be bypassed and
direct provisional assignments can be made.
■ Staffing Manager
Staffing managers generally fill the supply side of the task flows as they have
the access to all the resource data and manage the schedules and utilization of
the resources. Therefore, these persons know the availability of their own
resources. Staffing managers can approve assignments given the proper
authority, as well as, search for resources, nominate candidates, and fill open
requirements.
■ Resource Manager
Resource managers confirm or deny resource assignments, and manage the
schedules and utilization of their direct reports (resources.)
■ Team Member
Team members are the resources. They can manage their own competence
profiles and work information through the shared professional model of
Self-Service Human Resources. Team members can also view their schedule of
project assignments and search for requirements to nominate themselves as
candidates.

2-4 Oracle Project Resource Management Implementation and Administration Guide

 Application Process Flows

Application Process Flows

The process flows of the Oracle Project Resource Management application entail
activities such as creating a requirement, electing a person as a candidate, and
creating assignments. Based on the responsibility of the user, these process flows
may vary. This section describes some of the basic process flows of the application.

Creating Requirements
Through Oracle Project Resource Management, you have the ability to define the
requirements for a given project. The purpose of these requirements is to provide a
representation of the resources that are needed to complete the project.
For example, you have a project to install a product at a customer site. This project
may require two DBAs and two Implementation Consultants skilled in the product
to be installed. Without knowing the specific individuals that will fill these required
roles, you can identify information such as what level of experience is necessary,
where the work will be carried out, and approximately how long each position is
required. You define this information for each requirement which simplifies the
process of identifying potential resources to fill these roles.

Performing a Resource Search

When performing a resource search for a requirement, the dates of the requirement
are compared with the availability of the resource. If these time periods match, the
resource is considered a candidate for the requirement given the other search
criteria for the requirement also matches.

Filling Requirements
Filling a requirement involves either directly identifying a known resource, or
searching the resource repository to find suitable resources.
When a requirement is filled, an assignment is created. The assignment identifies
the period of time a specific resource will fill a specific role. If the person assigning
the resource to the requirement has authority over the resource, the assignment is
considered a confirmed assignment. Otherwise, the assignment must go through an
approval process, either manual or workflow-enabled depending upon how you
have implemented your installation. These assignments are provisional until
confirmed.
Confirmed assignments appear on the schedules of the assigned resource and the
project. This assignment to the resource reduces the availability of the resource.

User Process Flows and Concepts 2-5

Application Process Flows

Adding Assignments to Projects

An assignment is a filled work position on a project associated with a specific
resource for a designated period of time. An assignment can have various statuses
as required such as proposed, provisional, and confirmed.
Upon selecting the team role for the assignment, default values are provided for the
assignment name and job levels. Values for the assignment location and calendar
are retrieved from the associated project. You can change any of these defaults as
necessary.
After you have entered all the desired assignments, click Save and Submit to submit
the assignments for approval. This process prompts you for the approvers of the
assignment and then, forwards the assignment through the approval process.

Creating Administrative Assignments

An administrative assignment represents a non-work activity and is tracked against
an administrative project. You can use such assignments to block off time on your
resource schedules. The following examples demonstrate the functionality of
administrative assignments:
■ vacation time
■ internal training
■ project management duties
■ personal holiday
■ sick time
■ jury duty
You may want to track such assignments because they consume the work hours of
your resources, and therefore, affect availability, financial forecasting, and resource
utilization.

2-6 Oracle Project Resource Management Implementation and Administration Guide

 3
Establishing Your Enterprise Structure

The structure of your enterprise determines how to define your business groups,
organizations, hierarchies, jobs, and job groups. You must establish these key pieces
of information prior to implementing Oracle Project Resource Management.
If you have already set up some of these features in a previous implementation of
Oracle Projects or Oracle Human Resources, you can skip the respective sections of
this chapter. However, you may want to review the information to ensure it
corresponds to the data you want to use with Oracle Project Resource Management.
This chapter covers the following topics:
■ Setting Up Your Business Group Model
■ Defining Organizations
■ Defining Organizational Hierarchies
■ Defining Jobs and Job Mapping

Establishing Your Enterprise Structure 3-1

Setting Up Your Business Group Model

Setting Up Your Business Group Model

A Business Group is a special class of organization. Every business group can have
its own set of default values, with its own internal organizations, grades, jobs,
positions, payrolls, employees, applicants, compensations, competence structures,
and benefits.
In setting up your enterprise structure, you can establish one business group or
divide it into multiple business groups. If you set up more than one business group,
the associated data, such as organizations and employees, is partitioned
accordingly. Establishing an organization as a business group is not reversible,
therefore, you should plan your business group setup carefully.

For more information on business groups and structuring your enterprise, see
"Adapting or Creating a New Business Group," in Using Oracle HRMS – The
Fundamentals.

Prerequisites
Your enterprise structure strategy plan outlines your business groups. Prior to
actually setting up your business groups, you must complete the following tasks:
■ Set the HR: Cross Business Group Profile as described in the Oracle Projects 11i
Release 11.5.3/Mini Pack B User Guide Supplement.
■ Define the six key flexfield structures outlined in "Implementation Steps" in
Documentation Update for Patch Numbers 1383905 and 1377992 - Global
Competencies.

3-2 Oracle Project Resource Management Implementation and Administration Guide

 Defining Organizations

Defining Organizations
Organizations are the basic work structure of any enterprise. They represent the
functional, management, or reporting groups for individual business groups or
globally for your entire enterprise.
You can choose any organization, but typically, you use expenditure organizations
to track project resource-related expenses. Expenditure/Event organizations can
own project events, incur expenditures, and hold budgets for projects. To enable
these capabilities in the organization, you must perform the following tasks when
defining an organization:
■ Enable the Project Expenditure/Event organization classification.
■ Define a default operating unit for the organization in the Additional
Information section. This step causes all resources belonging to this
organization to inherit the specified operating unit and calendar as their default
operating unit and calendar.
■ Enable the HR Organization classification. This task is necessary in order to
have the ability to assign resources (people) to the organization.
■ Attach the organization to the Expenditure hierarchy assigned to the operating
unit using the Setup Implementation Options form.
For instructions on performing these tasks, refer to the following sources:
■ "Creating an Organization" in Using Oracle HRMS – The Fundamentals.
■ "Entering Organization Classifications" in Using Oracle HRMS – The
Fundamentals
■ "Entering Additional Information" in Using Oracle HRMS – The Fundamentals

Understanding the Resource Operating Unit

Every resource, employees and contractors alike, is associated with an operating
unit for security and forecasting reasons. This operating unit is derived from the
organization operating unit. The operating unit of the resource is active for the
duration of an assignment. It drives forecasting based on the transfer price defined
for the operating unit if the resource is assigned on a project under a different
operating unit, in other words, a borrowed resource.
Each time the employee assignment changes or if the default operating unit
originally set up for the employee changes, the Project Resource Management
application updates the resource operating unit. A history is maintained for

Establishing Your Enterprise Structure 3-3

Defining Organizational Hierarchies

record-keeping purposes and allows date-specific operating unit defaults for the
resource.

Defining Organizational Hierarchies

An organization hierarchy provides the structure of the relationships between your
organizations. Depending on your business needs, you can define one hierarchy or
multiple hierarchies for the following purposes:
■ project-owning organizations
■ expenditures
■ reporting
■ project burdening hierarchies for each business group
For more information on organization hierarchies, refer to the following sources:
■ "Organization Hierarchy" in the Oracle Projects User Guide
■ "Define Global Organization Hierarchies" in the Oracle Projects 11i Release
11.5.3/Mini Pack B User Guide Supplement)
■ "Creating Organization Hierarchies" in Using Oracle HRMS - The Fundamentals

3-4 Oracle Project Resource Management Implementation and Administration Guide

 Defining Jobs and Job Mapping

Defining Jobs and Job Mapping

Each person in Oracle HRMS can have only one primary job assignment. However,
HR jobs are often too granular for the purposes of project jobs. For example, you
may have an HR job defined as Consultant - Level 2, but for the purposes of making
project assignments, you want to only see Consultant. Oracle Projects provides you
with the ability to map the HR-defined jobs to the project-related jobs.
The following table provides the tasks to complete categorized by the Oracle
applications.

Application Task
In Oracle HRMS ... ■ Define Job Groups in Oracle HRMS. Job groups enable you
to classify certain types of work.
■ Define Jobs in Oracle HRMS. Jobs are the precise
assignment the employee fills.
Note: If you have shared HR, you can access these forms in
Oracle Projects.
In Oracle Projects ... ■ Define Job Mapping in Oracle Projects. Job mapping enables
you to link similar jobs in different job groups.
■ Select Job Groups for Resource Lists in Oracle Projects.
■ Select Job Groups for Project Templates in Oracle Projects.
You can assign a Billing Job Group to contract projects and
project templates.
■ Specify the job group to use for searches.

You can enter this information directly through Project Resource Management using
the Project Super User responsibility, if you do not have Oracle HRMS or Oracle
Projects.
For more information and instructions for setting up these job-related attributes,
refer to the following sources:
■ Implementing Oracle HRMS
■ Oracle Projects User Guide
■ the Oracle Projects 11i Release 11.5.3/Mini Pack B User Guide Supplement

Establishing Your Enterprise Structure 3-5

Defining Jobs and Job Mapping

Defining Job Relationships

Every job has an associated level and job code. The level is a numeric value that
indicates the skill level. The job code is an alphanumeric identifier used for
reporting and utilization.
You assign your jobs to job groups. These groups categorize the jobs into lines of
business, such as Consulting, Accounting, Engineering, and Support. These job
groups are also useful for reporting and utilization purposes. However, you might
have similar jobs in various job groups. In order to align these similar jobs for
reporting, you map each job code to a master job group. The master job groups
categorize jobs for your entire enterprise.
For example, you may have analyst positions in several job groups such as a
Technical Analyst in Engineering, a Support Analyst in Support, and a Research
Analyst in Consulting. You can map these three positions to a single master job
group called Analysts. If you have several levels of analysts, then you can map
these jobs to separate master job groups as appropriate to suit your business
reporting needs.
For further explanations and examples of job mapping, refer to the Oracle Projects
11i Release 11.5.3/Mini Pack B User Guide Supplement. However, take not that the job
code is a new feature as of this release, and job mapping is no longer dependent
upon the sequence or job grade in HR.

Specifying the Job Levels for Searches

Each project requirement has defined minimum and maximum job levels for the
purpose of resource searching. During a search, the job levels of the resources are
compared to the minimum and maximum job levels of the requirement. If the job
level of a resource falls between the minimum and maximum job levels of the
requirement, the resource is considered a possible match for the requirement given
other search criteria are met.
The Minimum and Maximum Job Level fields default from the levels defined on the
requirement, but you can modify them on the Modify Search Criteria page.
Modifying these values on this page does not change the original definition on the
requirement. The original definition of the requirement is available on the
Requirement Details page.
The minimum and maximum job levels are based on the job levels associated with
the job group specified as the value for the profile option PA: Project Resource Job
Group. For this profile option, you enter the name of the job group you want used

3-6 Oracle Project Resource Management Implementation and Administration Guide

 Defining Jobs and Job Mapping

as the collection of jobs included in searches. This profile option is set at the site
level only.
You can use the master job group as the value of this profile option, but remember
that it includes every job. If you have jobs that you do not want included in job
searches such as accounts payable jobs, administrative jobs, and human resource
jobs that are not related to staffing projects, then you can set up a separate job group
specifically for searching. This job group should include all jobs that you want
included in searches.

Establishing Your Enterprise Structure 3-7

Defining Jobs and Job Mapping

3-8 Oracle Project Resource Management Implementation and Administration Guide

 4
Defining Your People

A single collection of your resources, their skill sets, and their availability enables
you to utilize and manage your resources both effectively and efficiently. To
establish such a resource pool, you must understand your enterprise structure, the
job groupings, and the required and desired competencies of the resources.
The structure of your enterprise determines how your resources are distributed,
how competencies are shared and tracked, and how calendars and schedules are
created and maintained. Prior to entering or acquiring resources, you must establish
this structure in your system before you set up your resources. For more
information, refer to Chapter 3, "Establishing Your Enterprise Structure".
This chapter provides information and instructions on establishing your resource
pool through the following topics:
■ Understanding Resource Pool Benefits
■ Defining Employees and Employee Assignments
■ Setting Up Competencies
■ Acquiring Your Resources From Oracle HRMS

Defining Your People 4-1

Understanding Resource Pool Benefits

Understanding Resource Pool Benefits

The resource pool is the collection of all your valid resources into a single group.
Each individual within your resource pool has various attributes defined such as
personal information, work patterns, location, and competencies. Through entering
this information as accurately as possible, you gain the following benefits:
■ resources with consistent information from which to search
■ secured single-source access to information such as personal information,
resume, and competencies
■ precise requirement matching capabilities
■ forecasting based on resource needs
■ resource utilization manageability

Performing Searches on Your Resource Pool

Only valid resources (including future-date employees) are considered in resource
search queries. In order for a person to be considered a qualified resource within
Project Resource Management, certain criteria must be met. For a complete list of
the criteria, refer to Chapter 13, "Maintaining Your Data".

Note: Future-dated employees can qualify as a match for a

requirement only if their start date is on or after the start date of the
requirement.

When searching your resource pool for potential matches to requirements, you
specify certain criteria to limit the search. These criteria include the following:
■ Organizational Hierarchy
This field identifies the project expenditure/event organization hierarchy in
which to conduct the search for resources. The default hierarchy value is the
hierarchy assigned to the operating unit for the current responsibility as defined
in Implementation Options. You can change this value to any project
expenditure/event organization hierarchy in the database. This field is required
for performing a resource search.
■ Starting Organization
This field identifies the starting organization from which to start the search
within the specified project expenditure/event organization hierarchy. All

4-2 Oracle Project Resource Management Implementation and Administration Guide

 Understanding Resource Pool Benefits

project expenditure/event organizations below the specified starting

organization in the organizational hierarchy are considered in the search as
well. This field is required for performing a resource search.
■ Country
This field identifies the country for which to conduct the search for resources.
This country is compared to the primary address of the resource as of their
primary HR assignment start date.

Note: If a resource does not have a country defined for their

primary address, but matches all other search criteria, that resource
will be included in the search results.

■ Availability
The Minimum Availability field identifies the minimum availability required
for the resource to be considered a match for the requirement. Availability is the
available number of hours in schedule of a resource. It is equal to the capacity of
the resource minus the number of hours on confirmed assignments. Any
assignment with a provisional system status does not reduce the availability of
the resource.
The availability of a resource is considered from the current system date and
does not reflect any past dates. For example, you have a requirement that spans
four weeks with the start date that began last week. If a resource is found to
have the next three weeks 100% available, then that resource is considered as a
100% match without any regard to the availability of the resource for the first
week of the requirement. A resource search will never return any results when
the requirement is completely in the past (when the end date of the requirement
is prior to the current date.)
In order for a resource to qualify for the search results, the resource must have
availability records for at least a portion of the assignment duration. An
availability record represents each day a resource has availability. These records
are generated for a specific time period in the future for every resource. The
specific time period is determined by the profile option PA: Availability
Duration. For example, you have a requirement with a time length of two years
but a resource has availability records for only the next year with availability
(meaning these records are not used for other confirmed assignments), the
resource will still be delivered in the search results as a potential match.

Defining Your People 4-3

Understanding Resource Pool Benefits

You can view the availability of a resource on the timeline on the Resource
Details page. The displayed availability may not be correct if the resource does
not have an assigned calendar for the duration of the requirement or the
calendar schedules have not been generated or updated for the period.
For more information on the calculation of availability, refer to "Establishing the
Availability and Overcommitment Calculations" in Chapter 8, "Defining
Calendars and Schedules".
■ Job Level Match
For an explanation on how the job levels affect searches on your resource pool,
refer to "Specifying the Job Levels for Searches" in Chapter 3, "Establishing Your
Enterprise Structure".
■ Competencies
For an explanation on how competencies affect your search results, refer to
"Matching Resource and Requirement Competencies" and "Assigning Global
and Local Competencies" later in this chapter.

4-4 Oracle Project Resource Management Implementation and Administration Guide

 Defining Employees and Employee Assignments

Defining Employees and Employee Assignments

After establishing your enterprise structure, you can add your employees and their
respective primary assignments.
You can enter employee information through the Enter and Maintain People form
using either the Project Resource Management Super User, US HR Manager or the
Human Resources responsibilities.

Note: In Oracle HRMS, contractors are set up as employees

(system person type) and are created under the user person type of
Contractor.

Resources are assigned to organizations by creating assignments. You can use these
date-specific assignments to define future assignments.

Defining Employees
Oracle Project Resource Management requires the following employee information:
■ Last Name
■ First Name
■ Employee Number
■ Start Date
■ Organization (Expenditure/Event organizations only)
■ Job (HR job)
■ Supervisor (for workflow approval processes)
■ Location (Address)
■ Primary Address
■ Calendar
You can enter your employee information manually, or most of the information in a
bulkload through the use of an Application Programming Interface (API).
For more information on jobs, refer to "Defining Jobs and Job Mapping" in
Chapter 3, "Establishing Your Enterprise Structure".

Defining Your People 4-5

Defining Employees and Employee Assignments

For technical information about using the HRMS APIs, refer to "Technical Essays" in
Implementing Oracle HRMS. For instructions on entering employee information,
refer to Managing People Using Oracle HRMS.
For instructions on assigning a calendar to a resource, refer to "Assigning
Calendars" in Chapter 8, "Defining Calendars and Schedules".

Note: Each employee must have a defined primary address. This

address is used by the search functions within Oracle Project
Resource Management. If the address information is missing, the
employee cannot be created as a resource within this application.

Defining Employee Assignments

Employee assignments, also called primary assignments, describe the role of the
person within your organization. This organization must be in the project
expenditure organization hierarchy. Every employee, including contractors, must
have a primary assignment. For instructions on creating and assigning employee
assignments, refer to Managing People Using Oracle HRMS.

Defining Locations
The Locations table is populated as you add the employee locations, or any
locations, in the free text fields through the Project Resource Management
application. Users can reuse previous entries or create new locations. For example,
if you enter the following as a new location:
City: San Francisco
State: California
Country: United States

Any user can access this location information when prompted for location
anywhere in the application. However, you can add only city and states, not
countries.

4-6 Oracle Project Resource Management Implementation and Administration Guide

 Setting Up Competencies

Setting Up Competencies
Competence management encompasses a full cycle of events, from designing your
competence structure to performing project resource matching. Once established,
you can use your competencies for various activities such as determining the
competence profiles of your resources, staffing projects using skill matching, and
searching your staff for specific skills.

Defining Your Competence Structure

In defining your competence structure and competencies, you must first decide if
you want to share the competencies across business groups. This decision
determines if you will setup global competencies, local competencies for each
business group, or both.
Oracle Project Resource Management recognizes all competencies regardless of
whether they are flagged as global or local. However, you can only establish global
competencies if the HR: Cross Business Group profile option is set to Yes. If you are
not in cross-business group mode, you can only view the local competencies for
your business group. This exclusion eliminates viewing any competencies that
belong exclusively to other business groups.

Note: You must make a decision on your competence structure in

the planning stage because once you set up the competencies, you
cannot change the structure.

Your competence structure can reflect skills or measurable behaviors broken down
into multiple levels. The number of levels you want to set up determines how you
should set up your key flexfield structures.
The following table provides an example of how a competence of language
expertise can be broken down into multiple levels:

Competence - Level 1 Level 2 Level 3 Level 4

Language Indo-Iranian Indic ■ Assamese
■ Bengali
■ Sindhi
■ Hindi
■ Urdu

Defining Your People 4-7

Setting Up Competencies

Competence - Level 1 Level 2 Level 3 Level 4

Language Indo-Iranian Iranian ■ Persian
■ Kurdish
Language Germanic West Germanic ■ English
■ Dutch
■ German
Language Germanic North Germanic ■ Icelandic
■ Norwegian
■ Swedish
■ Danish

Unless your business is very specific about linguistics, you most likely would not
categorize the languages into such detail. However, the example does demonstrate
how you might use the various levels of competencies to categorize the skills.
Using a different example, you may have a competence such as knowledge of the
Oracle Projects applications. As your business may have many software skills you
want to track, you might want to set up a higher competence level labeled
"Knowledge of Software Applications". The following table provides an overview of
how you might breakdown the competence levels:

Competence - Level 1 Level 2 Level 3 Level 4

Knowledge of Software Oracle Projects Projects Costing ■ Implementing
Applications Product
■ Using Product
Knowledge of Software Oracle Projects Projects Billing ■ Implementing
Applications Product
■ Using Product

For more information on setting up competencies, refer to the following sources:

■ Documentation Update for Patch Numbers 1383905 and 1377992 - Global
Competencies
■ "Career and Succession Management" in Implementing Oracle HRMS
■ "Creating a Competence" in Managing People Using Oracle HRMS

4-8 Oracle Project Resource Management Implementation and Administration Guide

 Setting Up Competencies

■ "Planning Your Descriptive Flexfields" in the Oracle Applications Descriptive

Flexfields Guide
■ "Defining Descriptive Flexfields" in the Oracle Applications Descriptive Flexfields
Guide

Note: When creating your competencies, you must define

proficiency levels in order for the competencies to be recognized in
resource requirement searches. The Oracle HRMS application does
not require you to complete this information.

Assigning Competencies
The following objects can have assigned competencies:
■ Resources (people)
■ Jobs
■ Roles
■ Requirements
If all of these objects have defined competencies, a structure exists in which your
users can perform competence matching to find potential candidates for
requirements.

Assigning Job Competencies

You define jobs through the Oracle HRMS application. For each job, you can assign
required and desired competencies. For more information on defining jobs, see
Implementing Oracle HRMS.

Assigning Project Role Competencies

When users define requirements, they must associate project roles to the
requirements. The project role determines the default competencies of the
requirement that are used for performing searches to fill the requirement.
You define project roles using the Define Project Roles window in Oracle Projects.
For each project role, you define a default job. All job-associated competencies are
automatically copied over to the project role. You can add, modify, or delete

Defining Your People 4-9

Setting Up Competencies

competencies and their associated proficiency levels to the project roles as suits
your needs. For information on creating project roles, see Chapter 6, "Defining
Project Roles".

Note: You can assign only global competencies to a project role.

Assigning Requirement Competencies

Your users define project requirements using the Requirement Detail page. The
system copies the competencies of the project role to the requirement to which they
can add, modify, or delete as meets their needs. Each competence determined to be
mandatory for the requirement must have the required range of proficiency
specified in that skill. This range is used for comparison during a resource search.

Note: Your users can assign global competencies to a requirement,

as well as local competencies belonging to the business group of the
requirement.

Assigning Resource Competencies

Users with resource authority can define the competence profile and other
professional details of a resource using the Self-Service Human Resources (SSHR)
Professional Details module. This module is a component of the shared foundation
of Oracle HRMS that is integrated with Project Resource Management. Resources
can maintain their own competencies through SSHR. Changes to competence
profiles initiate a workflow approval process to the resource manager.
The SSHR responsibilities are as follows:

Oracle HRMS Installation SSHR Foundation Only

Employee Self-Service V4.0 Employee Self-Service Foundation
Manager Self-Service V4.0 Manager Self-Service Foundation

For more information, see the following sources available on Oracle MetaLink:
■ Implementing Oracle Self-Service Human Resources 4.0
■ Oracle Self-Service Human Resources 4.1 - Supplement

4-10 Oracle Project Resource Management Implementation and Administration Guide

 Setting Up Competencies

These competencies, in addition to other pertinent information, are compared to the

competencies of a requirement when performing resource searches. For more
information on the search comparison, see the following section "Matching
Resource and Requirement Competencies".

Matching Resource and Requirement Competencies

When a user performs a resource search to fill a requirement, all the mandatory and
optional competencies of the requirement are compared to those of the resource. All
resources with the mandatory competencies and desired competence levels are
potential matches given the other search criteria is met. Each resource produced
from the search must have these mandatory competencies at a level that is within
the specified competence levels for the requirement. If a competence associated to a
resource or a requirement has no proficiency level then it is considered to be at the
lowest proficiency level.
For each matching resource, the matches between the optional competencies of the
requirement and the competencies of the resource display in the following format:
0/2. The first number indicates the number of matches, and the second number
refers to the actual number of optional competencies of the requirement. For
example, 4/5 means that the resource has four of the five optional competencies at
the specified proficiency level for the requirement.
The competencies in the Modify Search Criteria page will default from the
competencies defined for the requirement, but you can also modify them, their
associated proficiency levels, as well as their mandatory flag on the Modify Search
Criteria page as well. Note that by modifying them on this page, you are not
changing the original definition on the requirement.

Assigning Global and Local Competencies

Local competencies are competencies defined for a particular business group.
Global competencies span across all business groups.
You can assign both global and local competencies to a resource. However, to assign
a local competence to the resource, the local competence must belong to the same
business group as the resource.
For a requirement, the competence list is based on the selected role. You can modify
this list through the Requirement Details page, defining both mandatory and
optional competencies.

Defining Your People 4-11

Setting Up Competencies

You can assign both global and local competencies to a requirement. If you flag local
competencies as mandatory on a requirement, ensure that these competencies all
belong to the same business group. Assigning mandatory local competencies from
different business groups will prevent the search functionality from producing any
results. A resource can have assigned local competencies only within their own
business group. Therefore, you should make such local competencies optional for
the requirement, or only select global competencies.

4-12 Oracle Project Resource Management Implementation and Administration Guide

 Acquiring Your Resources From Oracle HRMS

Acquiring Your Resources From Oracle HRMS

A concurrent process called PRC: Maintain Project Resources copies your resources
and their associated attributes from the Oracle HRMS tables to Oracle Project
Resource Management data tables. It identifies valid employees and project-related
information that are set up in the Oracle HRMS People definition windows and
adds them as resources in Project Resource Management.
You must run this process during your implementation to acquire your resource
pool. Thereafter, a background workflow process maintains the resource data. For
more information, see:
■ "Understanding the Impact of Changes to HRMS-Based Information" in
Chapter 13, "Maintaining Your Data"
■ "Initiating Deferred Workflow Processes" in Chapter 14, "Overview of the
Predefined Workflows"

Note: You may need to run this process if you encounter

workflow processing errors related to resource information.

Qualifying Criteria for the Resource Pull

The PRC: Maintain Project Resources process checks the qualifying criteria for each
resource to ensure that the resource has the necessary information to be an active
resource pool member. The qualifying criteria is as follows:
■ The resource must have an active and current primary assignment.
■ The resource must have a person type of Employee, or a person type that maps
to the system type of Employee.
■ The end date of the primary assignment should be later than the current
(system) date.
■ The primary assignment must have a defined job. This job must be mapped to
to a master job group with an associated job level. This master job group or an
associated other job group must be classified as the Project Resource Job Group.
For more information, see "Defining Jobs and Job Mapping" in Chapter 3,
"Establishing Your Enterprise Structure".
■ The primary assignment organization must:
– have a default operating unit; this operating unit must implement Oracle
Projects

Defining Your People 4-13

Acquiring Your Resources From Oracle HRMS

– have a specified default calendar or, the profile option PA: Default Calendar
must have a defined value
– have the classification of Project Expenditure/Event Organization
– belong to the project expenditure hierarchy
■ The operating unit of the resource must have Forecasting Options definitions.
■ GL Periods and PA Periods must be defined for one year prior to the current
system date, as well as, for a minimum of the time period defined for the
PA: Availability Duration profile option. For more information, refer to
"Overview of the Availability Calculation" in Chapter 8, "Defining Calendars
and Schedules".

Note: Since one of the qualifying criteria is that the resource has a
valid calendar, run the PRC: Generate Calendar Schedules process
before running this process to ensure all qualified resources are
copied.

Running the PRC: Maintain Project Resources Process

To run this process, complete the following steps:
1. Navigate to the Submit Request screen.
2. Choose Submit > PRC: Maintain Project Resources.
3. Enter the range of employee numbers, or leave the fields blank to retrieve all
employees.
4. Select Yes or No for the Update Existing Resource Information field.
The value of Yes indicates to copy all resource information from the HR tables
to the Project Resource Management tables. Therefore, existing resource
information in Project Resource Management will be updated.
If you select No, only new employees are copied to Project Resource
Management, therefore, existing resource information is not updated.
5. Enter the desired organization, or leave blank to run the process for all
organizations.
6. Click Submit.
You can view the exceptions report generated from this process to see any
employees that did not qualify for the resource pool and the reason why.

4-14 Oracle Project Resource Management Implementation and Administration Guide

 Acquiring Your Resources From Oracle HRMS

Migrating Resource Data From Other Systems

Project Resource Management relies on the primary assignment of a resource for a
number of internal processes. The primary assignment of the resource and the
resource information is established in the Oracle HRMS data tables. Resources are
created in Project Resource Management from these tables through one of the
following methods:
■ Running the concurrent process PRC: Maintain Project Resources. You run this
process only during the implementation of Project Resource Management.
■ A deferred workflow process called HR Related Update Workflow. This
scheduled process synchronizes the HR tables with the Project Resource
Management tables in order to maintain current resource data. This workflow
process is launched when any update is made to the HR tables.
If you are using a different database instance or a different system from Oracle
HRMS to maintain your employee data, you must migrate that data into the HR
tables within the same database instance that the Project Resource Management
application is running in. Oracle HRMS has several API programs you can use to
achieve this task.
These API programs queue up the deferred workflow processes. If the workflow
queue becomes too large, you may encounter process failures and errors. To avoid
this situation, use the following recommended procedures for migrating your
employee data for either a new instance or an existing instance.

Migrating Data for a New Instance

If you are implementing Project Resource Management for the first time and have a
large amount of employee data to migrate from Oracle HRMS, use the following
steps to avoid overloading the workflow queue during data migration:
1. Disable workflow triggers (using the script par1th02.sql).
2. Migrate your employee data.
3. Run the PRC: Maintain Project Resources process. It is recommended to run this
process multiple times with each process using different parameters. Avoid
overlapping the parameters so that the same person is not accessed by multiple
processes.
4. Enable workflow triggers (using the script par1th03.sql).

Defining Your People 4-15

Acquiring Your Resources From Oracle HRMS

Migrating Data for an Existing Instance

If you have implemented Project Resource Management and you migrate employee
data into Oracle HRMS on a periodic basis, use the following the guidelines.
■ Small Implementation
Use the Oracle HRMS API programs to migrate data without disabling the
triggers. You do not have to run the PRC: Maintain Project Resources process
because the deferred workflow process activated from updates in HR tables will
synchronize the data into Project Resource Management tables. However, make
sure that the workflow background process is running.
■ Larger Implementation
To prevent the workflow process queue from becoming too large, separate the
migration of new and existing employees. For new employees, complete the
steps provided in the previous section "Migrating Data for a New Instance".
For migrating updates to existing employee information, use the Oracle HRMS
API programs. The deferred workflow process will update the Project Resource
Management tables. If you encounter problems with the workflow queue,
perform the data migration more frequently.

4-16 Oracle Project Resource Management Implementation and Administration Guide

 5
Configuring Your Organization Security

The Oracle HRMS and Oracle Projects applications provide the setup for the core
security of your enterprise structure. You define this responsibility-based security
structure based on your organization structure and user responsibilities.
With Oracle Project Resource Management, you have an extended project security
structure based on project roles. Role-based security enables users to have multiple
levels of function access depending upon the assigned roles they have for each
given project. For more information on role-based security, see Chapter 6, "Defining
Project Roles".
This chapter discusses the project security models through the following topics:
■ Defining Your Security Strategy
■ Understanding Responsibility-Based Security
■ Understanding Role-Based Security
■ Defining Organizational Authority
■ Demonstrating a Security Check
■ Setting Up Security for Viewing Financial Amounts

Configuring Your Organization Security 5-1

Defining Your Security Strategy

Defining Your Security Strategy

Your security structure depends heavily on how you manage your projects, and
what type of access you want to provide your users. You should determine this
information prior to setting up any of the security features. The following table
describes some of the basic differences between the responsibility-based and
role-based security models:

Basic Responsibility-Based Role-Based Security Model

Function Security Model
Project List The project list The project list displays all projects for the given
displays all projects for operating unit where the user is an active member
the given operating of has project authority over the project
unit. organization.
View Project The user can view ■ If the project member on a project has been
Information project information assigned to roles with function security
except for labor costs enabled, then the member can view the project
for any of the projects attributes as allowed by the roles. For users
appearing on the with project authority on a project
project list. A user can organization, the user can view all attributes
view the labor costs for as allowed by the project authority menu. If
a project if this the member has been assigned to a role with
function has been function security disabled, then the member
assigned to the can view the project attributes as allowed by
responsibility of the the responsibility level function security.
user.
■ The projects that a user can view are limited
the by the project list of the user.
Update Active key members or ■ If the project member on a project has been
Project users with profile PA: assigned to roles with function security
Attributes Cross Project enabled, then the member can update the
responsibility enabled project attributes as allowed by the roles. For
(at the responsibility users with project authority on a project
level) can update the organization, the user can update all attributes
project attributes as as allowed by the project authority menu. If
allowed by the the member has been assigned to a role with
responsibility level function security disabled, then the member
function security. can update the project attributes as allowed by
the responsibility level function security.
■ The projects that a user can view are limited
the by the project list of the user.

Each of these models has its own benefits and is described in further detail in the
sections to follow.

5-2 Oracle Project Resource Management Implementation and Administration Guide

 Understanding Responsibility-Based Security

Understanding Responsibility-Based Security

Within the responsibility-based security structure, users have viewing access to the
projects for the operating unit associated to their respective responsibilities. Only
project members and cross-project users can update project information or view
labor costs (given the appropriate authority.)
You associate functions to menus and the menus to responsibilities. Therefore, the
responsibility of a user determines what functions the user can perform.
For further information and instruction, refer to the following sources:
■ Implementing Oracle HRMS
■ the Security chapter in Customizing, Reporting and System Administration in
Oracle HRMS
■ User Guide Supplement for Oracle Projects Minipack B (Release 11i Mandatory Patch)
■ "Project and Labor Cost Security" in Chapter 15, "Advanced Topics and Essays,"
in the Oracle Projects User Guide.

Defining Additional User Level Security

In addition to responsibility based security, you can also define user level security.
User level security is determined based on the role the user plays on a project, or by
additional security profile options set for the responsibility of the user. For more
information on role-based security, see "Understanding Role-Based Security" later in
this chapter.
You can define user level security on top of responsibility specific responsibilities
assigned to the users at the following levels:

Authority at the Organization Level

You can designate a user to have project, resource, utilization, or forecast authority
for a given organization. This specific role defined at the organization level provides
access to all projects created under the organization. See "Defining Organizational
Authority" in this chapter.

User with View All Projects Access

Cross-project users with view access can view all projects across multiple operating
units whether or not they are defined as a project member or have project authority.
You can provide view access by setting the profile option called PA: Cross-Project
User - View to Yes.

Configuring Your Organization Security 5-3

Understanding Responsibility-Based Security

You can set this profile option at the following levels:

■ site
■ responsibility
■ user
The default value for this profile option is Yes. However, for responsibilities of
Project Resource Management, you may want to consider setting this profile option
to No so that only relevant projects (projects within the operating unit) is available
for viewing. For either setting, you want to set this profile option consistently across
responsibilities.

User with Update All Projects Access

Cross-project users with update access can update any project provided no other
restrictions have been applied. However, users can only update information on the
project if the project belongs to the same operating unit as the responsibility the user
has used to log in.
You can provide update access through the profile option called PA: Cross-Project
User - Update. Setting this profile option to Yes provides your users this ability. You
can set it at the responsibility and user levels. The default value for this profile
option is No.

Note: This profile option is generally reserved for your power

users that need cross-project and cross-organization access.

User with View All Resources Access

Users with view all resources access can view the resource information for all
resources across multiple operating units whether or not they are the resource
manager of the resource or have organization resource authority. You can provide
view access by setting the profile option PA: View All Project Resources to Yes. You
can set this profile option at the responsibility level. The default value for this
profile option is set to Yes for the Project Super User responsibility.
Setting this profile to Yes provides your users the ability to view all resources in
Project Resource Management and have the security to confirm any assignments for
the resources.

5-4 Oracle Project Resource Management Implementation and Administration Guide

 Understanding Role-Based Security

Understanding Role-Based Security

Role-based security provides a means of controlling user access based upon the role
the user is currently playing on a project team. Every project member is assigned a
role. The access levels of that role are bestowed upon the user for the duration of the
role assignment. A user can play different roles on different project teams. For
example, you may assign a user a project lead role for a particular project in the first
half of the year and then, a consultant role on another project for the second half of
the year. These roles have completely different project security access and controls.
Responsibilities allow access to the overall application and determine the menus
and functions to which a user has access.
With role-based security, you assign the menus to roles. This level of assignment
offers more flexibility than the responsibility-based security structure.

Note: You define project roles for your entire enterprise. They are
not specific to any operating group or business group.

Levels of Role-Based Security

Role-based security offers multiple levels of control. You determine how detailed
you want your security levels. The available levels are as follows:
■ Roles
You assign menus to roles to determine the menu and function access for each
role.
■ Menus
You assign functions to menus, roles, and responsibilities.
■ Functions
You can attach the desired functions (access to pages or actions) to the
individual menus.

Predefined Roles
Oracle Project Resource Management provides the following predefined roles. For
more information on the individual authorities, refer to "Defining Organizational
Authority".

Configuring Your Organization Security 5-5

Understanding Role-Based Security

Project Manager
The Project Manager role provides access to all security access functions for the
project.

Project Staffing Owner

The Project Staffing Owner is the primary contact for the advertised requirements
on the project and is listed on the notifications and e-mails sent out for
advertisements. The Project Staffing Owner is different from a staffing manager.
Staffing Manager is the primary staffing contact for an entire organization, but a
project staffing owner is the primary person for staffing requirements for a specific
project.

Project Authority
Project Authority is an internal role at the organization level. A user with project
authority on an organization can view all projects in that organization. The Staffing
Analyst menu is assigned to this role as predefined data. Therefore, a user with
project authority is by default a staffing analyst for all projects within the
organization of the user.

Resource Authority
Resource Authority is an internal role at the organization level. A user with
Resource Authority can manage all of the resources for that organization. This role
provides access to all resource information within the given organization including
any project-related information for that resource.

Utilization Authority
Utilization Authority is an internal role at the organization level. A user with
Utilization Authority can calculate and view utilization for an organization.

Forecast Authority
Forecast Authority is an internal role at the organization level. A user with Forecast
Authority can generate and view forecast information for all projects in an
organization.

Predefined Responsibilities
You have the following classes of users who typically need access to project
resourcing information:

5-6 Oracle Project Resource Management Implementation and Administration Guide

 Understanding Role-Based Security

■ Organization Manager (Business Manager)

■ Project Manager
■ Resource Manager
■ Staffing Manager
■ Team Member (Resource)
■ Project Resource Management Super User
The implementation of Oracle Project Resource Management provides these user
classes as predefined responsibilities on the home page of Oracle Project Resource
Management. These responsibilities have the following associated default functions:

Organization Manager (Business Manager)

■ Project reviews
■ Team reviews
■ Forecast generation and review
■ Resource utilization generation and review

Project Manager
■ Project creation and maintenance
■ Project schedule creation and maintenance for own projects
■ Resource searching
■ View resource details
■ Requirement searching
■ Setup of project subteam
■ Access notifications

Resource Manager
■ Perform a requirement search
■ View the schedules of resources for which they are responsible
■ Enter administrative assignments for resources for which they are responsible
■ View and update resource details for resources for which they are responsible
■ Access notifications

Configuring Your Organization Security 5-7

Understanding Role-Based Security

Staffing Manager
■ Project schedule creation and maintenance for own resources on own projects
■ Resource searching
■ View resource details
■ Requirement searching
■ Resource schedule creation and maintenance for own resources (on own
projects)
■ Access notifications

Team Member (Resource)

■ View their own schedule
■ Enter their own administrative assignments
■ Requirement searching
■ View and update their own resource details
■ Access notifications

Project Resource Management Super User

The Project Resource Management Super User can access (view and edit)
everything on all projects and everything related to all resources.

Overview of Predefined Responsibility Function and Menu Access

The following table highlights whether or not certain function access is enabled for
each predefined responsibility:

Note: The functions listed below are only a subset of the functions
associated with each responsibility.

Project Resource Staffing Project Super

Predefined Function Manager Manager Manager Resource User
Create Project Yes No No No Yes
Project List Yes No Yes Yes Yes
My Details (Schedule) No No No Yes No

5-8 Oracle Project Resource Management Implementation and Administration Guide

 Understanding Role-Based Security

Project Resource Staffing Project Super

Predefined Function Manager Manager Manager Resource User
Requirement Search Yes Yes Yes Yes Yes
Define Team Template No No No No Yes
Workflow Notifications Yes Yes Yes Yes Yes
Staffing Home No Yes Yes No No
Utilization No Yes Yes Yes Yes
Reports Yes Yes Yes No Yes

The following table indicates whether or not the menu access is enabled for each
predefined responsibility:

Project Resource Staffing Project Super

Predefined Menu Manager Manager Manager Resource User
Project Manager Yes No No No No
Project Authority No No No No Yes
Resource Authority No Yes No No Yes
Resource No No No Yes No
Resource Pool Yes Yes Yes No Yes

Configuring Your Organization Security 5-9

Understanding Role-Based Security

Detailed Predefined Function Access by Responsibility

This section provides predefined function access grouped by responsibility as well
as the menus associated to each responsibility. A list of the predefined menus and
their respective functions are provided in the section titled "Predefined Function
Access by Menu" later in this chapter.

Organization Manager Responsibility

The predefined functions that are displayed to the user upon login with this
responsibility are:
■ Organization Utilization
■ Project Pipeline Workbook
The following menu is associated with this responsibility:
■ Resource Pool
■ Utilization Authority

Project Manager Responsibility

The predefined functions that are displayed to the user upon login with this
responsibility are:
■ Create Project
■ Page Layouts*
■ Project List
■ Project Templates**
■ Required Project Hours Workbook
■ Requirement Search
■ Workflow Notifications
The following menus are associated with this responsibility:
■ Balance by Project, Cost Center: Project View**
■ Balance by Project: Project View**
■ Project Manager Role
■ Resource Pool Role

5-10 Oracle Project Resource Management Implementation and Administration Guide

 Understanding Role-Based Security

■ Transaction Details for Project: Project View**

Note: For more information on the predefined function marked

with an (*), please refer to the Oracle Projects 11i.PJ_PFI Family
Pack Documentation Supplement (document #283837) available on
Metalink.
For more information on the predefined function and menus
marked with an (**), refer to the About Oracle Projects Family Pack
J (11i. PJ_PFJ document # 204637.1) available on Metalink.

Resource Manager Responsibility

The predefined functions that are displayed to the user upon login with this
responsibility are:
■ Resource List
■ Requirement Search
■ Resource Utilization
■ Staffing Home
■ Workflow Notifications
■ Available Resource Hours Workbook
■ Organization Competence Summary Workbook
■ Overcommitted Resource Hours Workbook
■ Resource Competencies Workbook
■ Scheduled Resource Hours Workbook
Predefined portlets available to the user are:
■ Resource Manager View of Available Resources
■ Resource Manager View of Available Resources Timeline
■ Resource Manager View of Overcommitted Resources
■ Resource Manager View of Overcommitted Resources Timeline
The following menu is associated with this responsibility:
■ Resource Pool Role

Configuring Your Organization Security 5-11

Understanding Role-Based Security

Staffing Manager Responsibility

The predefined functions that are displayed to the user upon login with this
responsibility are:
■ My Resources
■ Open Requirements
■ Project List
■ Requirement Search
■ Resource Utilization
■ Staffing Home
■ Workflow Notifications
■ Available Resource Hours Workbook
■ Organization Competence Summary Workbook
■ Overcommitted Resource Hours Workbook
■ Resource Competencies Workbook
■ Required Project Hours Workbook
■ Scheduled Resource Hours Workbook
Predefined portlets available to the user are:
■ Staffing Manager View of Available Resources
■ Staffing Manager View of Available Resources Timeline
■ Staffing Manager View of Overcommitted Resources
■ Staffing Manager View of Overcommitted Resources Timeline
The following menu is associated with this responsibility:
■ Resource Pool Role

Team Member Responsibility (Resource)

The predefined functions that are displayed to the user upon login with this
responsibility are:
■ Own Resource Details (Schedule)
■ Personal Utilization

5-12 Oracle Project Resource Management Implementation and Administration Guide

 Understanding Role-Based Security

■ Project List
■ Requirement Search
■ Workflow Notification
The following menu is associated with this responsibility:
■ Team Member Role

Project Resource Management Super User Responsibility

The predefined functions that are displayed to the user upon login with this
responsibility are:
■ Advertisement Rule
■ Create Project
■ My Projects
■ My Resources
■ Open Requirements
■ Organization Roles**
■ Organization Utilization
■ Page Layouts*
■ Page Layout Setup*
■ Project Templates**
■ Requirement Search
■ Team Templates
■ Workflow Notifications
■ Available Resource Hours Workbook
■ Organization Competence Summary Workbook
■ Overcommitted Resource Hours Workbook
■ Project Pipeline Workbook
■ Required Project Hours Workbook
■ Resource Competencies Workbook
■ Scheduled Resource Hours Workbook

Configuring Your Organization Security 5-13

Understanding Role-Based Security

The predefined security functions are:

■ Edit Page Layouts
■ Edit Project Status Reports
■ Remove Conflicts
■ View Project Status Reports
The following menus are associated with this responsibility:
■ Project Administrator Responsibility**
■ Project Authority
■ Resource Authority
■ Resource Pool Role

Note: For more information on the predefined functions marked

with an (*), please refer to the Oracle Projects 11i.PJ_PFI Family
Pack Documentation Supplement (document #283837) available on
Metalink.
For more information on the predefined functions and menu
marked with an (**), please refer to the About Oracle Projects
Family Pack J (11i. PJ_PFJ document # 204637.1) available on
Metalink.

Predefined Function Access by Menu

The predefined menus are as follows:
■ Project Manager
■ Project Staffing Owner
■ Resource
■ Resource Pool
■ Project Authority
■ Resource Authority
■ Utilization Authority
■ Forecast Authority

5-14 Oracle Project Resource Management Implementation and Administration Guide

 Understanding Role-Based Security

This section provides a list of the predefined functions for each menu in
alphabetical order.

Project Manager
The predefined functions for this menu are:
■ Projects > Apply Team Template
■ Projects > Candidates
■ Create
■ Review Log
■ View
■ Projects > Identification > Resource Search
■ Projects > Forecast
■ Generate
■ View
■ Projects > Options > Project
■ View and Edit Additional Information
■ View and Edit Classifications
■ View and Edit Customers and Contacts
■ View and Edit General Information
■ View and Edit Key Members
■ View and Edit Organization
■ View and Edit Page Layouts
■ View and Edit Pipeline
■ View and Edit Project Access Setup
■ View and Edit Team Member List
■ Projects > Options > Resource
■ View and Edit Additional Staffing Information
■ View and Edit Candidate Score and Search Settings
■ View and Edit Subteens

Configuring Your Organization Security 5-15

Understanding Role-Based Security

■ Projects > Page Layouts > View

■ Projects > Projects List > View Summarization Columns
■ Projects > Requirement/Assignment
■ Create and Delete
■ Edit Advertisement
■ Edit Schedule
■ View and Edit General Information
■ View and Edit Forecast Information
■ Projects > Resources > View
■ Projects > Setup
■ Projects > Status
■ Approved Statuses
■ Change Project Status
■ Closed Statuses
■ Pending Close Statuses
■ Submitted Statuses
■ Unapproved Statuses
■ Project Status Reports
■ View
■ Edit

Project Staffing Owner

■ Projects > Assignment
■ Create and Delete
■ Edit Advertisement
■ Edit Schedule
■ Remove Conflicts
■ View and Edit General Information

5-16 Oracle Project Resource Management Implementation and Administration Guide

 Understanding Role-Based Security

■ View and Edit Forecasting Information

■ Projects > Candidates
■ Create
■ Review Log
■ View
■ Projects > Identification > Resource Search
■ Projects > Options > Project
■ View and Edit Additional Information
■ View and Edit Classifications
■ View and Edit Customers and Contacts
■ View and Edit General Information
■ View and Edit Key Members
■ View and Edit Organizations
■ View and Edit Page Layouts
■ View and Edit Pipeline
■ View and Edit Project Access Setup
■ View and Edit Team Members
■ Projects > Options >Resource Setup
■ View and Edit Additional Staffing Information
■ View and Edit Candidate Score and Search
■ View and Edit Subteams
■ Projects > Project Home
■ Projects > Project Setup
■ Projects > Resources Schedule
■ View

Resource
The predefined functions for this menu are:

Configuring Your Organization Security 5-17

Understanding Role-Based Security

■ Projects > Administrative Assignment

■ Create and Delete
■ Edit Basic Information
■ Edit Schedule
■ View Basic Information
■ Projects > Assignment > View Basic Information
■ Projects > Identification
■ Requirement Search
■ Projects > Requirement Search
■ Nominate Self
■ Projects > Resource Candidacy
■ View
■ Withdraw Self
■ Projects > Resource Pool
■ View Work Information

Resource Pool
The predefined functions for this menu are:
■ Projects > Administrative Assignment
■ View Basic Information
■ Projects > Resource Pool
■ View Competencies
■ View Resume
■ View Schedule
■ View Work Information

Project Authority
This menu has the same predefined functions as the Project Manager menu.

5-18 Oracle Project Resource Management Implementation and Administration Guide

 Understanding Role-Based Security

Resource Authority
The predefined functions for this menu are:
■ Projects > Administrative Assignment
■ Confirm
■ Create and Delete
■ Edit Schedule
■ View and Edit Forecast Information
■ View and Edit General Information
■ Projects > Assignment > Confirm
■ Projects > Requirement Search
■ Nominate
■ Projects > Resource Candidacy
■ View
■ Withdraw
■ Projects > Resource Pool
■ View Competencies
■ View Resume
■ View Schedule
■ View Work Information
■ Resource Utilization

Utilization Authority
The predefined functions for this menu are:
■ Projects > Personal Utilization
■ Projects > Resource Utilization
■ Projects > Organization Utilization

Forecast Authority
The predefined functions for this menu are:

Configuring Your Organization Security 5-19

Understanding Role-Based Security

■ Projects > Assignment > View Basic Information

■ Projects > Forecast View

5-20 Oracle Project Resource Management Implementation and Administration Guide

 Defining Organizational Authority

Defining Organizational Authority

Establishing organizational authority enables you to specify the authority for a
resource at an organizational level. The key benefit is you do not have to assign
roles for people with organizational authority because it provides access to all
projects, resources, forecasting, and utilization information for the specified
organization.
However, you must specify each organization that a user should have authority
over. This authority does not acknowledge organizational hierarchies. For example,
if you have resource authority over a top organization, you do not automatically
have resource authority for all subordinate organization. You have to individually
specify each organization to which you want resource authority. This division
provides greater flexibility, especially in the case of a reorganization or change in
the organizational hierarchy.
You have four levels of organizational authority providing different access:
■ Project Authority
This authority level enables a user to perform staffing functions on a project.
The difference between this authority and the Project Manager role is the Project
Manager role only applies to assigned projects. A user with project authority
can perform staffing functions on all projects within the organization.
■ Resource Authority
This authority level provides a user security access similar to the access you
would require as a resource manager. You have the ability to perform tasks,
such as confirm assignments, for resources for the entire organization.
■ Utilization Authority
This authority level enables a user to calculate and view utilization for the
specified organization.
■ Forecast Authority
This authority level enables a user to generate and view forecast information for
projects within the specified organization.

Defining a Primary Contact

For Resource Authority and Forecast Authority, you can specify a primary contact
to handle cases where you have more than one person who has authority for an

Configuring Your Organization Security 5-21

Defining Organizational Authority

organization. Specifying the primary contact determines to whom to route

workflow approvals for assignments or forecasts.

Note: You can only assign one primary contact per organization.

Assigning Organizational Authority

To establish organizational authority for your users:
1. Select the following menu path: Setup > Human Resources > Organizational
Authority
2. Click Add Organizations.
You can search for organizations based on the following three fields:
■ Resource Name
Select the resource for which you want to establish organizational authority.
■ Hierarchy
Select the hierarchy in order to establish a list of resource organizations. This
field defaults to the expenditure hierarchy of the operating unit of the resource.
■ Start Organization
Select the organization to use as the start organization in order to provide a list
of subordinate organizations.
You must at least select the name of the resource to perform a search. After you
make your entries, click Find Organizations. The search produces all organizations
for which the specified resource has organizational authority.
If you selected a hierarchy or organization as criteria for the search, the results
display all qualifying organizations. Any organization for which the resource has
authority displays with a checkmark. To grant authority over the organization to
this resource, click the checkbox next to the desired organization and click Save. You
can assign one or more of the following authorities to a resource for each
organizations:
■ Project Authority
■ Resource Authority
■ Utilization Authority
■ Forecasting Authority

5-22 Oracle Project Resource Management Implementation and Administration Guide

 Demonstrating a Security Check

Demonstrating a Security Check

When a user initiates an action by attempting to perform a function in Oracle
Project Resource Management, a security check process is invoked. This process
searches for the appropriate permissions to allow the user to perform the requested
action. The logic of the security checks is as follows:
Check to see if the selected function is for a project.
■ If the answer is no, check if the user has the appropriate function security under
the assigned responsibility.
■ If the answer is no, end the process.
■ If the answer is yes, perform the action.
■ If the answer is yes, check if the user has any secured roles on the project that
would allow the user to perform this function.
■ If the answer is yes, perform the action.
■ If the answer is no, check if the user has only secured roles on the project.
– If the answer is yes, end the process. The process ends here because it
has been determined that the user does not have access to this functions
through any of the assigned secured roles.
– If the answer is no, check the client extension called PA_
SECURITY.ALLOW_UPDATE. If the client extension is set to No, end
the process. If it is set to Yes, check if the user has the appropriate
function security under the assigned responsibility.
–If the answer is no, end the process.
–If the answer is yes, perform the action.

Note: A secured role is a role with defined function security.

When the system performs a check for secured roles, it also
performs a check on whether or not the user has project authority. If
this check returns a true value, then the whole check is considered
true.

Figure 5–1, "Security Check Process Flow" demonstrates this process flow.

Configuring Your Organization Security 5-23

Demonstrating a Security Check

Figure 5–1 Security Check Process Flow

5-24 Oracle Project Resource Management Implementation and Administration Guide

 Setting Up Security for Viewing Financial Amounts

Setting Up Security for Viewing Financial Amounts

You can configure the Project List table to display a variety of summarized
project-level financial numbers. These numbers are derived from the Project Status
Inquiry (PSI) window. The titles of the financial amount columns on the Project List
page are exactly the same as those in the PSI window.

Note: All financial amounts are displayed in the functional

currency defined for the project. You cannot see an indication of the
functional currency (such as USD for US dollars, for example) on
this page.

The system secures the financial amounts that display in these columns with the
Project List: View Summarization Columns function, which is associated to the
Project Manager Role Menu by default. The Project Manager Role Menu is attached
to the Project Manager role. Therefore, you can use the Project List: View
Summarization Columns function to enforce role-based security for the financial
amounts that can appear on the Project List page. For example, you can use the
function to ensure that only project managers (for example) see financial amounts
on the Project List page.

Note: All team members have access to projects they have worked
on until their security access to those projects is changed.

To give users access to financial amounts on the Project List page:

1. Determine which roles you want to have the ability to view financial amounts
for projects, and associate those roles to the appropriate employees.
2. Create a new menu.
3. Attach all the functions you need to this menu.
4. Attach the security function Project List: View Summarization Columns to this
menu.
5. Create the project role using the Project Roles window in Oracle Projects.
6. Specify the menu you just created as the default menu for the role.
7. Assign the people to the project as key members with the project role you just
created.

Configuring Your Organization Security 5-25

Setting Up Security for Viewing Financial Amounts

8. When these key members come to the Project List page, they can see
project-level financial amounts and create views that include or exclude those
columns as necessary.

5-26 Oracle Project Resource Management Implementation and Administration Guide

 6
Defining Project Roles

Project roles are the templates for your team roles. This chapter covers defining
project roles through the following topics:
■ Definition of a Project Role
■ Overview of Predefined Role Controls
■ Defining Role Lists
■ Defining Project Roles

Defining Project Roles 6-1

Definition of a Project Role

Definition of a Project Role

A project role is a collection of default information about a team member role on a
project, such as competencies, job information, and security. You create project roles
to represent the typical team member roles needed for projects within your
organization.

How Project Roles are Used

A team role represents either a requirement or an assignment on a project. You use
the project role as a template for your team roles. When you create a team role, you
specify the project role from which to obtain all the default information. The default
information is copied from the project role to the team role. Thereafter, you can
modify the information on the team role as appropriate for that role on that
particular project. Any changes you make to the team role are exclusive and do not
affect the definition of the project role.
For example, you have a project role called DBA. You create a team role on a project
called Lead DBA based on the DBA project role. All the defined competencies, job
information, and security information is copied from the DBA project role to this
new Lead DBA team role. You decide to add more competencies to the Lead DBA
team role and to change the job level. These changes are only reflected on this
particular team role.
Each project role has a security structure determining the features users can access
and the functions they can perform. This security structure is referred to as
role-based security. Though role-based security is optional, it offers you more
flexibility than responsibility-based security because the role of a user can change
from project to project. Therefore, the function access a user may require can change
from project to project. For more information on security, see Chapter 5,
"Configuring Your Organization Security".
In the application, the team role is the value displayed on most pages. The project
role is only available on the assignment and requirement details pages.

6-2 Oracle Project Resource Management Implementation and Administration Guide

 Overview of Predefined Role Controls

Overview of Predefined Role Controls

You use role controls to define an additional dimension of security layering. These
controls determine how you (or other users) can use the role. The following
predefined controls are available:
■ Allow as Scheduled Member
■ Allow as Task Member
■ Allow as Project Member
■ Allow as Contract Member
■ Allow View Labor Costs
You can assign as many of these controls to roles as necessary. For example, the
control Allow as Scheduled Member indicates that you can schedule any person
assigned to the role as their availability permits. You want to assign this control to
any role that should be available for scheduling resources on projects. Since role
assignments occur at the project level, you must, at a minimum, assign the role
control Allow as Project Member to each role.

Note: The role controls Allow as Task Member and Allow as

Contract Member are not currently enabled.

Defining Project Roles 6-3

Defining Role Lists

Defining Role Lists

You use role lists to categorize your roles into logical groupings. For example, you
may have a role list called Consulting to which all roles relating to consulting are
assigned.

Note: A role list can not be deleted once it has been associated
with a project.

To add, modify, or delete role lists, use the Role Lists form under Setup. In this form,
you can specify the name, description, and effective dates for a role list. After you
define these parameters, you can select the roles you want assigned to this role list.

6-4 Oracle Project Resource Management Implementation and Administration Guide

 Defining Project Roles

Defining Project Roles

Prior to defining your project roles, establish the following items:
■ Competencies
■ Jobs
■ Role Lists
You can define the project roles in Oracle Projects through the Define Roles form
under Setup. The following table lists the information you must define for each
project role:

Prompt Description
Role Lists Identify the role lists to which you want the role assigned.
Access Menu Identify a security menu that the role can perform on a given
project.
Default Competencies Identify all default competencies required for the role. These
competencies are used for requirement definition.
Default Job and Job Identify the default job and job group for the role.
Group
Calculations for costing, billing, and transfer pricing use the
default job to forecast project resource requirements. This
default job can be overridden by a Project Cost Job, Project
Billing, and Project Transfer Price Job. You can use job mapping
logic to map the default job of the role to the master job if they
are in different job groups.
Default Minimum and Determine the minimum and maximum job levels for this role.
Maximum Job Levels
The job levels of a requirement are compared to these levels
when performing candidate (resource) searches.
Effective Dates Identify the date range the specified role is effective.
In some cases, you may not know the ending effective date
because it has not been determined. Therefore, only a start date
is required.

You can also assign the appropriate role controls to each project role. At a minimum,
you must assign the role control Allow as a Project Member.

Defining Project Roles 6-5

Defining Project Roles

6-6 Oracle Project Resource Management Implementation and Administration Guide

 7
Setting Up Staffing Capabilities

The staffing life cycle begins with the creation of requirements on your projects, and
ends with assigning resources directly or, through nominating, reviewing, and
selecting candidates. The team roles and staffing processes have some required and
optional predefined behavior. You can define this default behavior through profile
options, statuses, and other attributes.
This chapter describes this setup through the following topics:
■ Overview of Predefined Statuses and Status Controls
■ Defining Requirement Statuses and Profile Options
■ Setting Up Candidate Processing
■ Defining and Setting Up Advertisement Rules
■ Defining Assignments Statuses and Profile Options

Setting Up Staffing Capabilities 7-1

Overview of Predefined Statuses and Status Controls

Overview of Predefined Statuses and Status Controls

A status is the state of an object. Objects can only have one status at a time. With
your implementation of Oracle Project Resource Management, you are provided
with basic predefined statuses for the following objects:
■ projects
■ requirements
■ assignments
■ candidates
■ assignment approval
You can create new user statuses based on the available system statuses to meet
your business needs and create process flows that support those needs. You can also
modify the default status controls for each user status.
For each existing user status, you must define the next allowable statuses. Defining
the next allowable statuses determines the process flow for your objects. For
example, you can specify that a requirement with the user status of Open can have
its status changed to the user statuses of either only Filled or Cancelled. This
example shows that you have just determined two possible process flows of a
requirement:
■ Open -> Filled
■ Open -> Cancelled
For more information on statuses, status controls, and how workflow processes use
the statuses, see the following sources:
■ "Setting Up the Predefined Project Status Controls" in Chapter 9, "Defining the
Project Environment"
■ Oracle Projects 11i Release 11.5.3/Mini Pack B User Guide Supplement
■ Oracle Projects User Guide
■ Chapter 14, "Overview of the Predefined Workflows"

Note: Statuses are available for your entire enterprise, and are not
specific to any business group or operating unit.

7-2 Oracle Project Resource Management Implementation and Administration Guide

 Defining Requirement Statuses and Profile Options

Defining Requirement Statuses and Profile Options

The requirement status that indicates the state or condition of the requirement in the
staffing life cycle. This section describes the predefined values for requirement
statuses and status controls. It also describes the related profile options that you
must define. Set up of these statuses and profile options is required.

Predefined Requirement Statuses and Status Controls

The following table provides list of the predefined requirement statuses and
suggested next allowable statuses.

Suggested Next
System Status User Status Description Allowable Statuses
Open Open The requirement is available for ■ Filled
resource assignments.
■ Cancelled
Filled Filled The requirement has an assigned ■ Cancelled
resource.
Cancelled Cancelled The requirement was cancelled. None

Three status controls exist for the requirement statuses:

■ Include in Project Forecasts
■ Visible in Requirement Searches
■ Assign Resources to the Requirement
Use these status controls to restrict allowable actions on requirements based on
status.

Requirement Status Profile Options

You must define the following profile options to set the status defaults for
requirements. Each profile option is set at the site level only.

PA: Starting Requirement Status

This profile option defines the default status of newly created requirements.

Setting Up Staffing Capabilities 7-3

Defining Requirement Statuses and Profile Options

PA: Default Filled Requirement Status

This profile option defines the requirement status when the requirement is filled
and becomes an assignment.

PA: Default Cancelled Requirement Status

This profile option defines the status of a requirement when it is canceled.

Defining Staffing Priorities for Team Roles

Staffing priorities provide your users a means of identifying requirements that
should receive more attention in staffing efforts than others. You can define values
for the Staffing Priorities using the Project Resource Management Super User
responsibility and the following navigation path:
Setup > Staffing > Staffing Priorities
Your users can select staffing priorities when they are adding or updating
requirements. An assignment retains the staffing priority allocated to the original
requirement before it became an assignment (filled requirement).
You define the staffing priorities as lookup values. However, the setup of the
staffing priorities is optional. For more information on lookup types, see "Lookups"
in the Oracle Applications Developer’s Guide.

Defining the Team Role Descriptive Flexfield

A descriptive flexfield is available in Project Resource Management for defining
additional information on your team roles. The following table provides the name
and lists the pages on which your users can view this descriptive flexfield:

Descriptive Flexfield Pages Containing Descriptive Flexfield

Team Role Requirement Details
Assignment Details
Team Schedule

For both the Requirement Details and Assignment Details pages, this flexfield
automatically appears. In order to view this flexfield on the Team Schedule page,
you must personalize the page using the Personalize button. When a requirement or
assignment is copied, any descriptive flexfield values on the original requirement or

7-4 Oracle Project Resource Management Implementation and Administration Guide

 Setting Up Candidate Processing

assignment are also copied to the new requirement or assignment. When a

requirement is filled, this flexfield is copied to the assignment.
For more information on descriptive flexfields, see:
■ Appendix D, "Descriptive Flexfields" in the Oracle Projects User Guide
■ Oracle Applications Flexfields Guide

Setting Up Candidate Processing

Candidates are the nominated resources for open requirements. The setup for
nominating and processing candidates includes setting up required statuses and
profile options and defining default values for the candidate score and automated
search process. This section describes these setup features.

Defining Candidate Statuses and Profile Options

Each candidate has a status that indicates the state of consideration in the
nomination process on a given requirement. This section describes the predefined
values for candidate statuses and status controls. It also describes the related profile
options that you must define. Setup of these statuses and profile options is required.

Predefined Candidate Statuses and Status Controls

The following table provides a list of the predefined candidate statuses with
suggested next allowable statuses:

Suggested Next
System Status User Status Description Allowable Statuses
Pending Pending The candidate is nominated for the ■ Suitable
Review Review requirement and is ready for
■ Under Review
review.
■ Declined
■ Withdrawn
■ Assigned

Setting Up Staffing Capabilities 7-5

Setting Up Candidate Processing

Suggested Next
System Status User Status Description Allowable Statuses
System System The candidate was nominated by ■ Suitable
Nomination Nomination the automated candidate search
■ Under Review
and nomination process.
■ Declined
You cannot modify the attributes
of this status nor create user ■ Withdrawn
statuses for it.
■ Assigned
Under Review Under The candidate is currently in the ■ Suitable
Review review process.
■ Declined
■ Withdrawn
■ Assigned
Suitable Suitable The candidate is a suitable match ■ Under Review
for the requirement.
■ Declined
■ Withdrawn
■ Assigned
Declined Declined The candidate is unsuitable for the ■ Under Review
requirement. The default status
■ Suitable
control "Requires Change Reason"
requires the user declining the
candidate to enter a reason.
Withdrawn Withdrawn The candidate has withdrawn from ■ Under Review
consideration for the requirement.
Assigned Assigned The candidate is assigned to fill the None
requirement. This status is used
only by the workflow process once
the candidate has been assigned to
fill the requirement.

You can define your own user statuses based on these system statuses, except for
the Assigned system status. This system status is reserved for internal processes.
Only one status control exists for the candidate statuses:
■ Requires Change Reason
Use this status control to require the user to enter a reason for changing the status of
a candidate.

7-6 Oracle Project Resource Management Implementation and Administration Guide

 Setting Up Candidate Processing

Candidate Status Profile Options

You must define the following profile options to enable candidate processing. These
profile options are set at the site level only.

PA: Default Starting Candidate Status This profile option defines the default status of all
newly nominated candidates, except for system-nominated candidates.

PA: Cancelled Requirement's Candidate Status This profile option defines the candidate
status when a candidate nomination is declined due to requirement cancellation.

PA: Invalid Resource Candidate Status This profile option defines the candidate status
when a candidate nomination is declined due to a person ceasing to be a valid
resource in the Project Resource Management application.

Understanding the Candidate Score and the Automated Nomination Process

To assist your users in staffing requirements, you can set up an automated search
and nomination process to identify and nominate resources as candidates for open
requirements automatically. The setup includes definitions for both calculating the
candidate score and performing automated searches for candidates. This section
describes the candidate score calculations, the automated search and nomination
process. Setup of these features is required only if you choose to use this
functionality.

Candidate Score Weightings

Candidate scores enable you to define the level of importance of the availability,
competencies, and job level of the resource when matched to the specifications of a
requirement. These weightings are used to calculate a score for each resource
identified by a resource search and for every candidate on your requirements. This
score helps you identify the stronger candidates based on the weightings that you
have specified. A high score indicates a better match.
The formula for calculating the scoring percentage is as follows:
[Competence Match)(Competence Match Weighting) + (Availability
Match)(Availability Match Weighting) + (Job Level Match)(Job Level Match
Weighting)]
divided by:
[Competence Match Weighting + Availability Match Weighting + Job Level
Match Weighting]

Setting Up Staffing Capabilities 7-7

Setting Up Candidate Processing

Users define these weighting values at the requirement level. Default values will
appear for the requirement if they have been defined for the project or project
template. Users can change these values at any of these levels. The user can also
temporarily change these values when performing a resource search.

Automated Search and Nomination Process

This automated search process identifies resources that meet the specified criteria
for the requirement, including a minimum candidate score, and nominates those
resources as candidates on the requirement. This search is an optional process that
you can set up to run on a regular frequency, such as, daily or weekly through the
concurrent manager.
All of the requirements for a project are included in the search process if the
Enabled Automated Candidate Nomination Requirements check box is selected on
the Candidate Score and Search Settings page of the project. However, users can
also select or de-select this check box for individual requirements to include or
exclude them from being considered in the automated nomination process. If the
check box at the project level is not selected, then none of the requirements on that
project are included in the automated search process.
Resources are matched against the search criteria defined in the Automated Search
and Nomination fields of the requirement. These fields are:
■ minimum availability
■ organization hierarchy
■ starting organization
■ country
■ minimum candidate score
Then, the resources are matched against the following criteria retrieved from the
requirement:
■ minimum and maximum job levels
■ requirement dates matched to availability dates
■ competencies
All matching resources are nominated as candidates for the requirement and
assigned a candidate status of System Nominated. If the user does not change this
status, the candidate is re-evaluated to determine if a match still exists for the
requirement the next time the automated search process is run. The user can
prevent a candidate from being reconsidered by the automated search process by

7-8 Oracle Project Resource Management Implementation and Administration Guide

 Setting Up Candidate Processing

changing the candidate status to any other candidate status. For more information
on candidate statuses, refer to the following discussions in this guide:
■ "Defining Candidate Statuses and Profile Options" in this chapter
■ "Candidate Notification Workflow Extension" in Chapter 13, "Maintaining Your
Data"
If you do not enable the automated search process for a project or requirement, or if
a requirement is excluded from the automated search, the search process still uses
the Automated Search and Nomination values to identify qualified requirements for
resources. Resources can nominate themselves as candidates from their Candicacy
Lists for these requirements.

Submitting the PRC: Automated Candidate Search Process

You can set up this process to run on a scheduled basis using the Concurrent
Manager. You can also set up multiple instances of this process to run in parallel. In
either case, to benefit the most from this process, you want to run this process
frequently to accommodate the addition of new projects and requirements and the
fluctuation in resource availability.

Submitting the Process for a Single Project To run this process for a single project,
complete the following steps:
1. Navigate to the Submit Request screen.
2. Choose Submit > PRC: Automated Candidate Search for a Single Project.
3. Select the project.
4. Specify the number of days to look forward for newly starting requirements, or
leave blank to include all requirements.
5. Click Submit.

Submitting the Process for Multiple Projects To run this process for a range of projects,
complete the following steps:
1. Navigate to the Submit Request screen.
2. Choose Submit > PRC: Automated Candidate Search for a Range of Projects.
3. Enter the project number range, or leave blank to include all projects.
4. Specify the number of days to look forward for newly starting projects, or leave
blank to include all projects.

Setting Up Staffing Capabilities 7-9

Setting Up Candidate Processing

5. Specify the number of days for newly starting requirements, or leave blank to
include all requirements.
6. Enter a specific project status, or leave blank to include projects of all statuses.
7. Click Submit.

7-10 Oracle Project Resource Management Implementation and Administration Guide

 Defining and Setting Up Advertisement Rules

Defining and Setting Up Advertisement Rules

An advertisement rule is an automated method of controlling the visibility of a
requirement to resources and managers of an organization over a period of time. It
is a list of actions that are performed when the condition associated with each action
is met.
With the advertisement rule functionality, users can perform the following tasks:
■ Create and maintain advertisement rules
■ Define default advertisement rules at various levels
■ Define and maintain advertisement actions on a requirement
■ View audit history and current status of an advertisement rule on a requirement
■ Replace advertisement rule on a requirement
■ Start, pause, or resume an advertisement rule on a requirement
■ Reverse advertisement actions on a requirement
This section describes advertisement rules, associated processes, and how to
implement this functionality. Setup of the advertisement rules is required only if
you choose to use this functionality.

Overview of Advertisement Rules

Advertisement rules enable users to control the staffing, visibility, and escalation of
requirements based on actions. For example, users can define actions to specify
when and which staffing managers and organizations can view the open
requirement and who should be notified if the requirement is not staffed within a
specified time.

Advertisement Rule Actions

The action choices are as follows:
■ Publish to All: Make advertisement visible to all resources, across all
organizations on the Staffing Home, Requirement List, and Requirement Search
Result pages.
■ Publish to Project Authority: Make requirement visible to resources with
project authority within a specified organization on the Staffing Home,
Requirement List, and Requirement Search Result pages.

Setting Up Staffing Capabilities 7-11

Defining and Setting Up Advertisement Rules

■ Publish to Organizations: Make requirement visible to all resources in a

specified organization hierarchy on the Staffing Home, Requirement List, and
Requirement Search Result pages.
■ Escalate to Next Level: Make the requirement visible to everyone in the next
level in the organization hierarchy. This action is only valid if one of the
previously defined actions is Publish to Organizations.
■ Send Email: Send an e-mail to a specific e-mail address. You can use any
external e-mail address. You can also enter multiple e-mail addresses separated
by a comma.
■ Send Notification to Person: Send a notification to a specified person regarding
the open requirement.
■ Send Notification to Project Role: Send a notification to a specified role on the
requirement-owning project.
■ Update Staffing Priority: Update the staffing priority of the requirement to the
selected value.
■ Cancel Advertisement: Remove visibilities of requirement in all pages and
searches.

Advertisement Rule Action Conditions

Each advertisement rule action has an associated condition. The possible conditions
of the advertisement rule actions are:
■ Number of days since the advertisement rule has been started for a
requirement, or
■ Number of days remaining before start of the requirement, or
■ Combination of above two conditions
The user can indicate to either begin the advertisement rule automatically upon the
requirement creation, or activate the rule later for each requirement. Oracle Project
Resource Management evaluates the open requirements that have an advertisement
rule with a status of "Started" or "Resumed" and performs all of the actions where
the conditions are met. You must schedule this evaluation process using a
concurrent process.

7-12 Oracle Project Resource Management Implementation and Administration Guide

 Defining and Setting Up Advertisement Rules

Advertisement Rule Statuses

Each advertisement rule on a requirement has a status. Possible statuses are
provided in the following table:

Advertisement Rule Status Possible Actions

Not Started ■ Start the advertisement rule on the requirement
■ Assign a resource to fill the requirement
Started ■ Pause the advertisement rule on the requirement
■ Assign a resource to fill the requirement
Paused ■ Resume the advertisement rule on the requirement
■ Assign a resource to fill the requirement
Resumed ■ Pause the advertisement rule on the requirement
■ Assign a resource to fill the requirement
Closed None

The default advertisement rule status on the requirement can be either "Not Started"
or "Started". When the requirement is staffed, the advertisement rule status becomes
"Closed". Users can change the status by performing different actions such as start,
pause, or resume the advertisement rule on the requirement. All actions are
recorded in the audit history.

Project Staffing Owner

A predefined role call Project Staffing Owner exists to identify the primary contact
for advertisements of the requirements of a given project. This role has predefined
security functions and is an optional assignment for every project.
This role differs from the Staffing Manager role because a staffing manager is
responsible for staffing requirements on projects across organizations. For more
information, see Chapter 5, "Configuring Your Organization Security"

Setting Up Staffing Capabilities 7-13

Defining and Setting Up Advertisement Rules

Advertisement Rule Processes

This section describes the various process flows of the advertisement rules.

Obtaining a Default Advertisement Rule

Users can set advertisement rules at various levels. The value defined at each level
becomes the default value for the next subsequent level. The levels and the default
sequence is as follows:
1. Implementation Options
2. Project Template
3. Project
4. Requirement
You set the overall default advertisement rule in the Implementation Options. When
a user creates a project template, the project template retrieves the advertisement
rule from the Implementation Options. When a user creates a project, the project
advertisement rule is copied from either the project template or from the original
project from which the new project is being copied. Any new requirements added to
the project also adopt the project advertisement rule.
The user can override the default advertisement rule at any of the levels from the
project template to the requirement. In addition, the user can modify the actions of
the advertisement rule on individual requirements without affecting the original
default advertisement rule.

Processing Advertisement Actions

An advertisement rule action on a requirement is performed only if the associated
condition is met and the advertisement rule status is "Started" or "Resumed". The
associated condition for advertisement actions is validated in the following three
methods:
■ Concurrent Process
The concurrent process, PRC: Perform Action Rules, set at regular frequency
performs the advertisement actions of the open requirements that have met the
associated condition.
■ Online update
The associated conditions of the actions on a requirement are re-evaluated
online if the start date of the requirement is changed or, if the advertisement

7-14 Oracle Project Resource Management Implementation and Administration Guide

 Defining and Setting Up Advertisement Rules

rule on the requirement is updated. The qualified actions are performed if the
advertisement rule status is "Started" or "Resumed".
■ Advertisement Rule is Started or Resumed
When a requirement advertisement rule is first activated or resumed, the
system validates the advertisement actions to check if they meet the associated
condition. The qualifying actions are performed.

Reversing Advertisement Rule Actions

Advertisement rule actions that have been already completed for a requirement can
be reversed by one of the following methods:
■ deleting the individual advertisement action from a requirement
■ using the Cancel Advertisement Rule action to cancel all advertisement rule
actions of the requirement
■ replacing the entire advertisement rule on a requirement with a new
advertisement rule
The following table describes the result of reversing each action.

Action Result of Action Reversal

Publish to All Resources of all organizations can no longer view the
requirement
Publish to Project Users with project authority of the organization can no longer
Authority view the requirement
Publish to Organizations Resources of the organizations can no longer view the
requirement
Escalate to Next Level Resources of the organizations can no longer view the
requirement
Update Staffing Priority This action cannot be reversed
Send Email An email is sent to the individuals and distribution lists
informing them that the requirement is no longer available
Send Notification to A notification is sent to the individuals informing them that the
Person requirement is no longer available.
Send Notification to A notification is sent to the project roles informing them that the
Project Role requirement is no longer available.

Setting Up Staffing Capabilities 7-15

Defining and Setting Up Advertisement Rules

Action Result of Action Reversal

Cancel Advertisement All previous actions that had been cancelled because of this
action are re-evaluated and are performed if the associated
condition is met

Replacing an Advertisement Rule

Users can replace an advertisement rule on an open requirement by selecting a
different rule. All the previously performed actions on the requirement are reversed
and the actions on the new rule are performed if the associated conditions are met.
All changes are recorded in the advertisement audit history for the requirement.

Auditing Advertisement Rule Activities

As the system performs advertisement actions for a requirement, the details and the
date of the actions are recorded in an audit history. This report lists all of the
advertisement activities and the related details on the requirement. For example,
when an action is activated, an audit record is created. This record provides a list of
the names of staffing managers, organization names and email addresses to whom
the requirement has been advertised and the date when the requirement was made
visible.

Implementing Advertisement Rule Functionality

One predefined advertisement rule called "Publish to Everyone" comes with your
installation of Oracle Project Resource Management. This system default rule
contains one action, Publish to All, and cannot be modified or deleted. This rule
publishes the requirements to everyone beginning on the creation date of the
requirement. If you do not want to use the advertisement rule functionality, you do
not have to set up or change anything. In this case, users should leave the Start
Advertisement Rule check box selected for each requirement. If a user de-selects
this check box, then the requirement will not be visible in any requirement searches
or Requirement List pages.
If you want to implement and utilize the advertisement functionality, you must
define your own rules and set them up accordingly. This section describes the
required setup steps in more detail.

7-16 Oracle Project Resource Management Implementation and Administration Guide

 Defining and Setting Up Advertisement Rules

Defining Advertisement Rules

To create advertisement rules, complete the following steps:
1. Using the Project Super User authority, select Advertisement Rules from the
main portal page.
2. Click Create Advertisement Rule.
3. Enter the name, description, and effective dates and click Add Action.
4. Enter action and condition information and click Apply. After you enter and
save the action, the Create Advertisement Rule page appears with the updated
information.
5. Repeat step #4 for each action you want to define for this advertisement rule.
6. When you are finished entering all actions, click Apply on the Create
Advertisement Rule page to save the entire advertisement rule.

Specifying the Default Advertisement Rule

After you define your advertisement rules, you can specify the default rule on the
Staffing tab in system Implementation Options window. For information on the full
defaulting process, see "Obtaining a Default Advertisement Rule" in this chapter.

Submitting the PRC: Perform Action Rules Process

The PRC: Perform Action Rules process evaluates the action conditions for each
action on a scheduled basis. If a condition is valid, then the process activates the
related action.
This process applies to all types of action rules. However, you can specify to run this
process for only advertisement rule actions. Only advertisement rule actions for
open requirements with an advertisement rule status of "Started" or "Resumed" are
processed.
To schedule this process, navigate to the Submit Request screen, select whether to
run this process for a single project or a range of projects, and complete the
parameters.

Setting Up Staffing Capabilities 7-17

Defining Assignments Statuses and Profile Options

Defining Assignments Statuses and Profile Options

Each assignment has a status that indicates the state of the assignment in the
staffing life cycle. This section describes the predefined values for assignment
statuses and status controls. It also describes the related profile options that you
must define. Setup of these statuses and profile options is required.

Predefined Assignment Schedule Statuses and Status Controls

The assignment schedule status is the daily assignment status. Therefore, each day
of the assignment has its own schedule status. The following table provides a list of
predefined assignment schedule system statuses with suggested next allowable
statuses:

Suggested Next
System Status User Status Description Allowable Statuses
Provisional Provisional A resource is assigned to the ■ Confirmed
assignment on a provisional
■ Cancelled
basis.
Confirmed Confirmed The resource is confirmed and ■ Cancelled
scheduled for the assignment.
Cancelled Cancelled The assignment was cancelled. None

Only one status control exists for the assignment statuses:

■ Include in Project Forecasts
Use this status control to include assignments in project forecasts based on the
status.

Predefined Assignment Approval Statuses

Assignment approval statuses are used by workflow processes. This status
represents the approval status for the entire assignment. You cannot add, modify, or
delete these statuses. In addition, users cannot manually change these statuses. The
status is applied to an assignment based on the action being undertaken.
The following table provides a list of the predefined assignment approval statuses
with their associated next allowable status:

7-18 Oracle Project Resource Management Implementation and Administration Guide

 Defining Assignments Statuses and Profile Options

Next Allowable
System Status Description Statuses
Working The assignment is new and has not yet been ■ Submitted
submitted, or the assignment has been changed and
is waiting to be resubmitted for approval.
Submitted The assignment is submitted for approval. Approval ■ Approved
can be sought either manually or through an
■ Rejected
automated workflow process.
Approved The assignment is approved and the resource is ■ Requires
confirmed. Resubmission
Cancelled The assignment is cancelled. None
Rejected The assignment is rejected. The user can choose to ■ Requires
modify the assignment and resubmit it for approval. Resubmission
Requires The assignment has been changed and requires a ■ Submitted
Resubmission resubmission for approval.

Assignment Status Profile Options

You must define the following profile options to set the status defaults for the
assignments. Each profile option is set at the site level only.

PA: Starting Assignment Status

This profile option defines the default status of newly created assignments.

PA: Default Cancelled Assignment Status

This profile option defines the status of cancelled assignments.

Setting Up Staffing Capabilities 7-19

Defining Assignments Statuses and Profile Options

7-20 Oracle Project Resource Management Implementation and Administration Guide

 8
Defining Calendars and Schedules

Defined calendars are the basis of all schedules fro resources, requirements, and
assignments. You establish resource schedules based on the calendar assigned to the
resource. You can assign a calendar to a resource, or accept the default calendar
from the site, organization, or project.
This chapter provides information creating calendars and maintaining schedules
through the following topics:
■ Setting Up Calendars
■ Establishing the Availability and Overcommitment Calculations

Defining Calendars and Schedules 8-1

Setting Up Calendars

Setting Up Calendars
A calendar provides basic information such as working days, non-working days,
and holidays. When a resource is assigned to a specific calendar, that calendar
represents the capacity of the resource. Assignments using these calendars provide
information such as the scheduled days for the assignment, and determine the
availability of the resource.
You can set up an unlimited number of calendars to meet your various scheduling
challenges. For example, you may have certain people that work specific days of the
week. Therefore, you would create a calendar for each unique work pattern
arrangement.

Creating Calendars and Defining Calendar Attributes

You must create a calendar in order to establish the schedule work patterns of your
resources. These work patterns determine the availability of a resource for project
assignments and scheduling. You can create an unlimited number of calendars to
define the work patterns, but you must define at least one.
In order to create a complete calendar, you must first define the following calendar
attributes:
■ calendar types
■ shifts and shift patterns
■ calendar exceptions
After defining these attributes, you can create calendars.

Defining Calendar Types

Calendar types enable you to classify your calendars. For example, you may have a
calendar type of "Part Time" to which you assign to all calendars that are defined
with part time shifts.
To create a calendar type, complete the following steps:
1. Select Setup > Schedule Management > Scheduling Calendar > Define
Calendar.
2. Select the Define Calendar Type tab.
3. Enter a code for the calendar type in the New Code field.
4. Enter a meaningful description in the Description field.

8-2 Oracle Project Resource Management Implementation and Administration Guide

 Setting Up Calendars

5. Enter dates in the From Effective Date and To Effective Date fields, if applicable.
You can now use this new calendar type to create a calendar.

Defining Shift and Shift Patterns

Shifts define the daily work hours in a week and are defined for a given range of
dates. The effective dates of the shift or shift pattern override any other preset
effective dates when used on a schedule.
For example, if a shift or shift pattern is not effective for the period or part of the
period for which requirement or assignment schedules are created, then the
schedule is not created for that period.
To create shifts and shift patterns, complete the following steps:
1. Select Setup > Schedule Management > Scheduling Calendar > Define
Calendar.
2. Select the Define Shifts tab.
3. Enter the name of the shift.
4. Enter the shift description.
5. Enter the effective dates of the shift.

To create shift patterns:

1. Select the desired weekdays.
2. Enter the From and To time range.
3. Enter the effective dates.

Only the total hours for the day are considered for Oracle Project Resource
Management. The specific time values do not have any effect.

Note: A day with zero hours specified in the shift is considered a

non-working day.

Defining Calendars and Schedules 8-3

Setting Up Calendars

Creating Calendar Exceptions

Exceptions define holidays and are considered non-working days.
To create calendar exceptions, complete the following steps:
1. Select Setup > Schedule Management > Scheduling Calendar > Define
Calendar.
2. Select the Calendar Exceptions tab.
3. Complete the fields as necessary for the specific calendar exception.
You must create calendar exceptions for public holidays and general holidays for
every year that they occur. For all other types of exceptions, make administrative
assignments. As described for shifts, only the total number of hours are considered
for Oracle Project Resource Management, not the actual time segments.

Creating a Calendar
To create a calendar, complete the following steps:
1. Select Setup > Schedule Management > Scheduling Calendar > Define
Calendar.
2. Select the Define Calendar tab.
3. Complete the required information for the calendar.

Assigning Shifts and Exceptions to Calendar

To assign shifts and exceptions to a calendar, complete the following steps:
1. Select Setup > Schedule Management > Scheduling Calendar > Define Calendar
> Calendar Shift/Exceptions.
2. Select the desired calendar.
3. Use the Shifts Tab to assign Shifts to the calendar.
4. Use the Exceptions Tab to assign Exceptions to the calendar.

Changing the Calendar Any changes to the calendar are applied to the schedule work
patterns by a periodic process. The changes to calendar will affect the future
schedule creations and updates. For more information, see "Updating Schedules
with Calendar Changes" in Chapter 13, "Maintaining Your Data".

8-4 Oracle Project Resource Management Implementation and Administration Guide

 Setting Up Calendars

Establishing Default Calendars

You can set up default calendars at two levels:
■ the site level
■ the organization level

Defining the Default Calendar for the Site

You can select any defined calendar as the default calendar at the site level using the
PA: Default Calendar profile option in Oracle Project Resource Management.
This profile option indicates the default calendar for projects, project assignments,
and resources in the Oracle Project Resource Management application. You can only
update this profile option at the site level.

Defining Default Calendars for Organizations

The calendar assignment at the organization level overrides the calendar
assignment at the system site level. You can set up a calendar for a project
organization using the Define Organization form in the Additional Information
section for the project Expenditure/Event organization classification. This calendar
becomes the default calendar for all resources within the organization.

Assigning Calendars
The default calendars you specify for the site and organizations carry down to the
projects and resources. You can override these defaults by assigning a calendar
directly to the project or resource.

Assigning Calendars to Projects

Assigning a calendar to a project overrides the default calendar retrieved from the
project organization or site. To modify the default calendar on a project, use the
Project Details page.

Assigning Calendars to Resources

Every resource must have an associated calendar for scheduling purposes. The
calendar determines the capacity of the resource. During implementation, you use a
process called PRC: Maintain Project Resources to pull the resources from HR tables
into Oracle Project Resource Management. This process assigns all resources a
default calendar. For more information on this process, see "Maintaining Schedules"
in Chapter 13, "Maintaining Your Data".

Defining Calendars and Schedules 8-5

Setting Up Calendars

The default calendar for the resource can come from various sources depending
upon how you have set up your system. Oracle Project Resource Management uses
the calendar defined for a resource in CRM. If the resource does not have a defined
calendar in CRM, the calendar for the resource defaults from the organization. If
you do not define a default calendar for the organization, then the calendar for the
resource defaults to the entry in the Calendar profile for the site. You can override
all these defaults at any time and assign a specific calendar to a resource.
To assign a default calendar to the resource, complete the following steps:
1. Select Setup > Schedule Management > Scheduling Calendar > Define
Calendar.
2. Select the Assign Resources tab.
3. Complete the required information on the screen.

8-6 Oracle Project Resource Management Implementation and Administration Guide

 Establishing the Availability and Overcommitment Calculations

Establishing the Availability and Overcommitment Calculations

Availability is the unassigned time of a resource within the capacity boundaries of
the resource. Overcommitment occurs when the confirmed and scheduled hours of
a resource exceed the capacity of that resource.
This section describes the calculations and profile options used to determine the
availability and overcommitment for the resource schedules.

Overview of the Availability Calculation

You determine availability of a resource by subtracting the confirmed scheduled
hours of the resource from the capacity hours of the resource. The calendar to which
the resource is assigned determines the capacity hours of the resource.
Oracle Project Resource Management calculates future resource availability based
on a predefined number of years. You set the number of years for the availability
calculation in a profile option called PA: Availability Duration. Availability records
are created from today’s date through to the end of the time period you specify
using this profile option. For example, if you enter 2 as the value of this profile
option, the availability of your resources is calculated from today to the end of two
years. The PA: Availability Calculation Period profile option determines whether
the availability hours for each resource is built daily or weekly. For more
information, refer to "Defining Availability and Overcommitment Profile Options".
Resource availability is recalculated every time a new assignment for a resource is
made. Therefore, using the above example, if you make an assignment on a resource
until the end of April, the availability is recalculated to move out for two years from
the end of April.
If you create an assignment for a resource outside of the availability period, such as
10 years in the future, the availability is not recalculated because it is outside of the
range defined in the above profile option. If this is a real assignment, then you must
break it up into segments of two years or change the profile option to be set to 10
years or greater.

Setup Requirements for the Availability Calculation

The availability calculation looks for defined GL Periods and PA Periods, as well as
defined Forecasting Options.

Defining GL Periods and PA Periods for Availability Purposes In order for the availability
of a resource to be calculated, you must have both GL Periods and PA Periods
defined for the availability duration. Since the availability of a resource is

Defining Calendars and Schedules 8-7

Establishing the Availability and Overcommitment Calculations

recalculated every time an assignment is added, this can be a moving target.

Therefore, a suggested formula for determining how far in advance to set up these
periods is to double the value you have entered for the PA: Availability Duration
profile option. For example, if you have defined this profile option with a value of 2
(for 2 years), then define GL and PA Periods for 4 years out.
The first time you run the PRC: Maintain Project Resources process to pull in your
resources, if you have resources that have a start date prior to the system date, the
resource availability will be calculated one year prior to the current system date.
This availability is used solely for timeline displays for the prior year. These
displays are useful if you are converting and tracking assignments that started in
the previous year. GL Periods and PA Periods must be established for this prior
year. If these periods are not defined, then any resource with an HR assignment
start date earlier than the current system date will not be considered a valid
resource in Project Resource Management.

Defining Forecast Options for Scheduling Purposes The forecast options must be defined
for each operating unit. These forecast options define your preferences on handling
resource utilization and financial forecasting. Some of this information is also used
for calculating resource availability. For more information, refer to "Defining
Forecasting Options" in Chapter 10, "Implementing Financial Forecasting".

Overview of the Overcommitment Calculation

A resource is considered overcommitted based on how the overcommitment is
calculated. Two profile options affect this calculation:
■ PA: Overcommitment Percentage
■ PA: Availability/Overcommitment Calculation Period
The PA: Overcommitment Percentage specifies the maximum tolerance of
overcommitment. Therefore, if you set this profile option to 10, then you are
indicating that resources will not be considered overcommitted until their
confirmed scheduled and confirmed assignment hours exceed their capacity hours
by 10% or more. For example, you set this profile option to 10. If a resource has a
capacity of 40 hours per week, then the overcommitment tolerance is 4 hours (40
hours X 10% = 4 hours). Any overcommitment beyond this number of hours
qualifies the resource to be flagged as an overcommitted resource. Therefore, the
resource will be considered overcommitted if the scheduled confirmed hours for
this resource exceeds 44 hours for any one week.
The PA: Availability/Overcommitment Calculation Period determines whether the
overcommitment is calculated on a daily basis or a weekly basis. For example, if

8-8 Oracle Project Resource Management Implementation and Administration Guide

 Establishing the Availability and Overcommitment Calculations

you set this profile option to Daily, then the number of confirmed hours and the
number of capacity hours are compared for each day for each resource. If the
number of confirmed hours for the day exceed the number of capacity hours for the
day by more than the tolerated percentage, then the resource is marked as
overcommitted for that day.
If you set this profile option to Weekly, the calculation will perform this comparison
to identify any overcommitment on a weekly basis. However, using the Weekly
setting, a resource can still have overcommitment on a daily basis and not get
marked as overcommitted as long as the resource is not overcommitted for the
entire week. For example, if the capacity for a resource is 40 hours and the resource
has 30 confirmed hours dispersed over 2 days for a given week, this resource is
marked as overcommitted using the daily basis, but not for the weekly basis.
The overcommitment calculation uses the start date of the assignment to evaluate
overcommitment. Therefore, even though the resource has 40 hours of capacity for a
given week and an assignment is scheduled for that week for 40 hours, the
distribution of those hours can still cause an overcommitment. For example, an
assignment begins on Tuesday and has a work pattern in the first week as
illustrated in the following table:

- Sun Mon. Tues Wed Thur Fri Sat

Availability 0 8 8 8 8 8 0
Assignment 0 0 8 8 8 8 8

The capacity hours of the resource for the week are calculated from the assignment
start date. In this example, the capacity hours begin from Tuesday and end on
Friday equaling 32 hours. Since the assignment has 40 hours distributed for this
week, the resource is considered overcommitted. This overcommitment can be
corrected either by changing the assignment start date to the Monday, or
redistributing the extra 8 hours to another week with availability.
As each resource is evaluated, any assignment causing an overcommitment is
flagged. Users with the appropriate authority can remove or change conflicting
assignments.

Defining Availability and Overcommitment Profile Options

Define the following profile options to establish how availability is calculated and
how both availability and overcommitment will appear on your resource timelines:

Defining Calendars and Schedules 8-9

Establishing the Availability and Overcommitment Calculations

■ PA: Availability/Overcommitment Calculation Period

This profile option enables you to determine the time period segment to use in
calculating the availability. Valid choices are Daily or Weekly, and the default
value is Weekly.
■ PA: Availability Duration
This profile option determines the length of time (in years) for which the
application should create timeline availability records. The availability for a
resource is recalculated every time a new assignment is created for the resource.
The default value for this profile option is 2.
■ PA: Percentage of Resource’s Capacity
This profile option specifies the lowest percentage threshold in determining
availability. The default value is 100.
■ PA: Overcommitment Percentage
This profile option specifies the minimum percentage to exceed capacity before
considered overcommitted. Default value is 0.

8-10 Oracle Project Resource Management Implementation and Administration Guide

 9
Defining the Project Environment

The definition of your project environment includes the setup of all the attributes
used for creating projects, tracking pipeline projects, and staffing project roles. It
also includes the implementation of your approval and notification processes
defined through automated Oracle Workflow processes. You define these features
using Oracle Projects, Oracle Project Resource Management, and Oracle Workflow.
This chapter elaborates on the definition and usage of these attributes through the
following sections:
■ Creating Project Attributes
■ Establishing Probability Information
■ Setting Up the Predefined Project Status Controls
■ Setting Up Your Self-Service Environment

Defining the Project Environment 9-1

Creating Project Attributes

Creating Project Attributes

In creating a project, your users will use a variety of attributes to define the
behavior and future processing of the project. To define the following attributes,
you use the Oracle Projects windows:
■ work types
■ class categories
■ class codes
■ project statuses
■ project types
■ project templates
■ service types
■ customer contact types
■ customer relationship codes
■ customers and customer addresses
■ billing schedules
■ pipeline information
This list is a subset of the required project attributes. For a complete list, refer to
Appendix A, "Implementation Steps Checklist". For information on defining work
types, refer to Chapter 11, "Implementing Resource Utilization".
For information on defining the remaining attributes, refer to "Project Definition" in
Chapter 17, "Oracle Projects Setup and Implementation," in the Oracle Projects User
Guide and the Oracle Projects 11i Release 11.5.3/Mini Pack B User Guide Supplement.

Note: You must set up customers in Oracle Projects (or in Oracle

Accounts Receivables) in order to assign them to projects.

9-2 Oracle Project Resource Management Implementation and Administration Guide

 Setting Up the Predefined Project Status Controls

Establishing Probability Information

When defining a potential project, you can enter pipeline information such as the
probability percentage of winning the project, the project value, and the expected
approval date. This information is used for calculations such as determining the
weighted (discounted) value of all projects in your pipeline. If a project has no
defined probability percentage, then it is assumed to be 100% for all calculations
performed on the project.
You have control over how percentage values are used on a project through the
creation of Probability Lists. The probability list is a list of percentages with
descriptions. For example, you create a list called "Quarters" with the following
percentages:
■ 25% Talks Initiated
■ 50% Negotiation
■ 75% Contract Proposed
■ 100% Approved
You can attach this list to any project type. When you create a project and using a
particular project type, these are the values available for selection in the Probability
field.
For more information and setup instructions, see the Oracle Projects 11i Release
11.5.3/Mini Pack B User Guide Supplement.

Setting Up the Predefined Project Status Controls

The predefined project statuses are:
■ Unapproved
■ Submitted
■ Approved
■ Pending Close
■ Closed
These project statuses are described in detail in the Oracle Projects User Guide.

Defining the Project Environment 9-3

Setting Up the Predefined Project Status Controls

The Oracle Project Resource Management application introduces the following

status controls for these statuses:
■ Change Project Probability
You can change the probability of the project when this status control is
enabled.
■ Allow Provisional Assignments
You can create provisional assignments on a project when this status control is
enabled.
■ Allow Confirmed Assignments
You can create confirmed assignments on a project when this status control is
enabled.
The project status controls enable you to define specific restrictions or allow certain
actions to occur when a status is applied to a project. The following table lists these
controls and indicates whether or not the status control is enabled for each status.
You can change these defaults to meet your business needs.

Status Control Unapproved Submitted Approved Pending Close Closed

Change Project Y Y Y N N
Probability
Allow Provisional Y Y Y N N
Assignment
Allow Confirmed Y Y Y N N
Assignments

For more information on project status values and status setup instructions, refer to
the Oracle Projects User Guide and the Oracle Projects 11i Release 11.5.3/Mini Pack B
User Guide Supplement. For more information on how the workflow processes use
the statuses, refer to Chapter 14, "Overview of the Predefined Workflows".

Note: Statuses are available for your entire enterprise, and are not
specific to any business group or operating unit.

9-4 Oracle Project Resource Management Implementation and Administration Guide

 Setting Up Your Self-Service Environment

Setting Up Your Self-Service Environment

You can set up your self-service environment to accommodate your business needs
and the needs of your users. For complete instructions, refer to the Oracle
Self-Service Web Applications Implementation Manual.
This section discusses the following topics:
■ Self-Service Web Applications Profile Options
■ Configuring the Project Home Page
■ Enabling Project Shortcut Links
■ Configuring Table Views

Self-Service Web Applications Profile Options

The following table lists the required Self-Service Web Applications profile options
for the home page setup:

Profile Option Description Value Example Value

Applications Web Identifies the location of the http://your_web_server: http://ap242sun.us.oracle.c
Agent Web agent port/<plsql cartridge om: 8000/bis115/plsql/
virtual path>/
ICX: Language Determines the default Language American English
language
ICX: Date language Determines the default Language American English
language in which dates are
displayed.
ICX: Date format Determines the date format Date Format Mask The American English
mask mask to use default is DD-MON-YYYY;
for example, 12-NOV-1997
ICX: Numeric Determines the characters to ., .,
characters use to delimit numbers
ICX: Territory Geographical area Geographical area America
ICX: Discoverer Identifies the Discoverer http://your_discover_ http://AP4811PC.us.oracle.
Launcher Server that runs reports and server:port/webdis/html/ com/webdis/html/english
produces HTML output english/welcome.htm? /
Connect=[AP PS_SECURE] welcome.htm?Connect=[AP
PS_SECURE]

Defining the Project Environment 9-5

Setting Up Your Self-Service Environment

Profile Option Description Value Example Value

ICX: Discoverer This profile option, in EUL EUL
End User Layer combination with the
Schema Prefix Language Code, comprises
the identifier of the EUL
Owner at runtime.
For example:
If your EUL owner is EUL_
US, then your ICX_
DEFAULT_EU L profile
should be EUL
(The language code to derive
the complete EUL owner is
automatically added).
PA: Home Page Determines how many The default value is set to 2 2
Highlights: weeks of team activities to meaning 2 weeks.
Number of Weeks display in the Team
Highlights table on the
Project Home page. This
profile option is set at the
site level only.

Configuring the Project Home Page

You can configure the layout of the Project Home page to display specific
information in a specified order. This functionality enables your project managers to
provide a higher level of direction and focus to their team members. The team
members see only the information they need, organized in order of importance.
Sections of information compose the home page. You can choose the sections you
want to appear and the order in which they should display. The home page layouts
also include shortcut links to useful pages within the application for the specific
project. You can specify project shortcut links you want on your project home page
layouts. For more information, see "Enabling Project Shortcut Links" in this chapter.
To create a project home page layout:
1. From the Project Super User responsibility, click Page Layout Setup menu
option.
2. Select Project Home in the Create Page Layout selection list and click Go.

9-6 Oracle Project Resource Management Implementation and Administration Guide

 Setting Up Your Self-Service Environment

3. On the Create Page Layout page, enter the information for your new layout.
4. Click Update Sections List to add the desired sections for both the right and left
sections of the page.
5. Click Apply.
You can create multiple configurations of the Project Home page, however, you can
only use one configuration per project.

Specifying the Project Header Section

The project header section is the basic information that appears on the various
project pages. Two predefined header sections are available:
■ Default Project Header: Displays the organization, project manager, project
type, status, start date, and completion date
■ Project Header with Customer and Project Value: Displays all information in
Default Project Header and the customer and project value
For each project, the project manager can select the header information for the
project pages and the project home page layout through the Page Layout page
available under the Project tab > Setup subtab.

Enabling Project Shortcut Links

Using standard menu functionary in the System Administrator responsibility, you
can define a variety of shortcut menus using the Menus window. By tying together
submenus, you can create a hierarchical shortcut menu with a maximum of three
levels. The lowest level menu is always the shortcut link.

Note: For detailed information about the operation of the Menus

window, see the Oracle Applications System Administrator’s Guide.

Shortcut links are composed of user functions, and therefore, the links are subject to
role-based security enabling you to control link access based on defined role of a
user on any given project. For example, you can make the Add Team Members link
visible only to project managers and other users whose role includes the ability to
perform this function. In addition, certain links are subject to product licensing and
are not available to organizations that have not licensed Oracle Project Resource
Management.

Defining the Project Environment 9-7

Setting Up Your Self-Service Environment

Predefined Shortcut Links

Oracle Projects includes eight link options from which you can select to include in
the shortcut menu. Six of these are included in the default project shortcuts menu.

Project Shortcut Links The following tables lists the predefined project shortcut links
and related information:

Included Project
in Default Resource
User Function Shortcut Management
Shortcut Link Page Name Name Menu Only
Add Team Members Add Team Projects: Options: Yes No
Members Key Members
View Classifications Classifications Projects: Options: Yes No
Classifications
View Customers Customer Projects: Options: Yes No
Details Customers and
Contacts

Resource Shortcut Links The following tables lists the predefined resource shortcut
links and related information:

Included Project
in Default Resource
User Function Shortcut Management
Shortcut Link Page Name Name Menu Only
Add Requirements Add Add Yes Yes
Requirements Requirements
Add Assignments Add Add Yes Yes
Assignments Assignments
View Staffing Staffing Projects: Options: No No
Information Information Staffing
Information
Apply Team Template Apply Team Apply Team No Yes
Template Template

Reporting Shortcut Links The following tables lists the predefined reporting shortcut
link and related information:

9-8 Oracle Project Resource Management Implementation and Administration Guide

 Setting Up Your Self-Service Environment

Included Project
in Default Resource
User Function Shortcut Management
Shortcut Link Page Name Name Menu Only
Maintain Status Maintain Status Projects: Project Yes No
Reports Reports Status Reports:
Edit

Configuring Table Views

The Oracle Applications Personalization Framework is available for all applications
built using the Oracle Applications Framework technology. The Personalization
Framework enables administrators and users to configure regions of the user
interface through a self-service tool without making any changes to underlying
code. Therefore, these changes do not impact your ability to upgrade to future
versions of the application.

Note: A restart of the JVM is not required for configurations to

take effect.

The Personalization Framework provides several levels of configuration. A defined

administrative user can configure the application Web pages as applicable to Project
Resource Management at the following levels:
■ Localization
■ Site
■ Organization
■ Responsibility
Most tables have one or more views predefined in the initial implementation.
Individual users can copy these views and use them as their default views. Users
can also create their own views. Such views are only available to their own
respective login sessions, and cannot be viewed by other users.

For more information on Oracle Applications Personalization Framework, refer to

OA Customization Framework, CR: 282233 available under ERP Oracle Applications
Technology Stack on Oracle MetaLink.

Defining the Project Environment 9-9

Setting Up Your Self-Service Environment

9-10 Oracle Project Resource Management Implementation and Administration Guide

 10
Implementing Financial Forecasting

Oracle Project Resource Management can produce financial forecasts for your
projects based on existing staffing plans. This self-service financial forecast
functionality enables you to:
■ perform forecasts based on single or multiple projects
■ drill down to find out the distribution of the forecast totals
■ regenerate forecasts on adjusted staffing plans
This chapter describes how to set up the required elements for performing
forecasting activities through the following topics:
■ Overview of the Financial Forecast Process and Calculations
■ Implementing the Forecast Functionality
■ Establishing Security on Forecast Functionality

Implementing Financial Forecasting 10-1

Overview of the Financial Forecast Process and Calculations

Overview of the Financial Forecast Process and Calculations

Oracle Project Resource Management provides a financial forecast process that
performs calculations based on your predefined bill and cost rates. These rates are
evaluated within the time frame of the assignments and requirements and the
scheduled work patterns to provide you forecast totals. Predefined bill rates can be
overridden by the user for individual requirements and assignments. This section
describes the process and calculations used to generate these forecast totals.

Financial Forecast Process

When you invoke the action to generate a forecast, the process evaluates for the
project the daily hours of the staffed labor (assignments) and open requirements.
The daily hours of the assignments and requirements are summarized based on the
time period (GL Period or PA Period) for the life of the project.
These totals are used to derive your total estimated cost, revenue, margin, and
margin percentage for the project. For requirements, the forecast cost and bill rates
are obtained from the job assigned to the role in Project Resource Management. For
assignments, this information is obtained directly from the assigned employee.
Employee and job level bill rates can be overridden by bill rates defined for the
requirement or assignment.
After the forecast generation completes, a notification is sent to the user who
invoked the process. This notification indicates whether or not the forecast totals
were generated successfully. On the Project Forecast page, an indicator appears next
to the role or project for which errors on forecast items occurred. A link to the
forecast error page is provided on the Project Forecast page. This page provides an
explanation of the errors encountered for each assignment or requirement for the
project. The user can regenerate the forecast after the errors have been corrected.

Note: The generation of forecast totals is handled through

deferred Oracle Workflow processes. As the volume of the forecast
items can be large, these processes can require a substantial amount
of time to complete the processing of forecast items. You can
increase the processing performance by creating additional
background process dedicated only to processing the forecast items.
For more information, see"Understanding Data Processing" in
Chapter 13, "Maintaining Your Data".

10-2 Oracle Project Resource Management Implementation and Administration Guide

 Overview of the Financial Forecast Process and Calculations

Forecast Calculations
Each forecast page provides totals for labor hours, cost, revenue, margin, and
margin percentage. These totals can vary depending upon how you implement the
forecast options. Therefore, it is helpful to review the calculations for each of these
totals to assist you with making your implementation decisions.
The calculations used to derive the forecast totals are as follows:
■ Hours = The number of hours for each requirement or assignment in the Project
Resource Management staffing plan, by role and period.
■ Cost = The labor raw cost represents for each role the cost of the requirements
and assignments.
The cost rates for assignments are based on the employee cost rates. The cost
rates for requirements are based on the cost rate of the job associated with the
role of the requirement.
The burden schedule for the project is applied to the raw cost rates to provide
the burdened costs that are reflected in the forecast. The formula to derive the
cost rate is as follows:
■ Average Cost Rate = Total Burdened Cost / Total Hours
This amount appears in the Average Rate column when you select Cost as
the Show Amount.
■ Margin = Revenue - Cost
Margin is calculated at the same level as Revenue for each project.
■ Margin % =[ (Revenue - Cost) / Revenue ] * 100%
Margin % is calculated at the same level as Revenue for each project.

Calculating Revenue
Revenue is calculated differently based on the revenue distribution rule assigned to
your projects. Using the work-based distribution rule, the revenue for time and
material projects is calculated by role. Using the cost and event-based distribution
rules, the revenue for fixed-price projects appears as one line for the entire project.
The formulas for generating the displayed totals are provided below grouped by
the distribution rules.
The following sections describe the calculations for each revenue distribution rule.
For more information regarding revenue distribution rules, see the Oracle Projects
User Guide.

Implementing Financial Forecasting 10-3

Overview of the Financial Forecast Process and Calculations

Revenue Calculation for Projects Using Work-Based Distribution Rule For projects with a
work-based distribution rule, the revenue is calculated as follows:
■ Revenue = Hours * Bill Rate
You can enter a bill rate for requirements and assignments individually on the
Requirements and Assignments Details pages. Otherwise, the bill rate is derived
from any project-level bill rate overrides. If no overrides exist, then depending on
how you define your project, the bill rate is derived from one of the following
schedules:
■ Rate Schedules
The rate schedules for both assignments and requirements are retrieved from
the associated job. For assignments, the rate schedule is overridden if the
assigned employee has a rate in the defined employee-based rate schedule.
■ Burden Schedules
If you associate a burden schedule with the project, then it is used to determine
the revenue by marking up the cost.
After the bill rate is determined, any defined project-level discount percentages are
applied. You can set a project-level discount to any project using the following
navigation path from the individual project:
Project Options > Bill Rates and Overrides > Standard Billing Schedules
The rates and discount percentages displayed in forecast pages are derived using
the following calculations:
■ Standard Rate = Job-based bill rate schedule (as of the start of the assignment)
■ Average Rate = Total Revenue / Total Hours
■ Effective Discount % = [ (Standard Rate - Average Rate) / Standard rate ] *
100%

Revenue Calculation for Projects Using Cost-Based Distribution Rule For projects with a
cost-based distribution rule, the revenue is calculated as follows:
■ Revenue (For period X) = [ (A / B) * C ] - D
Where:
X = Current Period
A = Inception to Period X Total Cost
B = Total Project Cost
C = Total Project Value

10-4 Oracle Project Resource Management Implementation and Administration Guide

 Overview of the Financial Forecast Process and Calculations

D = Inception to Prior Period End (X-1) Revenue

Revenue Calculation for Projects Using Event-Based Distribution Rule For projects with an
event-based distribution rule, the revenue is calculated as follows:
■ Revenue = Total Project Value
This total appears in the last period of the project. All other periods of the
project reflect a zero dollar value. If the project does not have an end date, then
the system uses the last period with an assignment or requirement.

Generating Forecast Information

You can generate forecasts by clicking the Generate Forecast button in the Financial
Forecast screen, or by submitting the concurrent process PRC: Generate Project
Forecasts.
When you submit the concurrent process, you can generate forecasts for:
■ a single project
■ a range of projects
■ all projects in an organization
To run the concurrent process, complete the following steps:
1. Navigate to the Submit Request screen.
2. Choose Submit > PRC: Generate Project Forecasts.
3. Select the desired project range by specifying From Project and To Project
parameters. To select a single project, specify the project for both the From
Project and To Project parameters. To run the process for all projects in an
organization, leave these parameters blank.
4. Enter the desired organization.
5. Click Submit.

Implementing Financial Forecasting 10-5

Implementing the Forecast Functionality

Implementing the Forecast Functionality

In order to generate forecasts totals, you have to define specific information on
which the forecasts are based. This section provides details for the following
implementation steps to establish the forecast feature:
■ Defining a Job-Based Cost Rate Schedule
■ Defining Bill Rate Schedules
■ Updating Project Types with Employee and Job-Based Bill Rate Schedules
■ Defining Forecast-Related Profile Option
■ Defining Periods
■ Defining Unassigned Time Tracking
■ Defining Forecasting Options
As the forecast totals for requirements depend upon the job bill and cost rates of the
requirement, each role within Project Resource Management must have a job
associated with it.
For more information on defining roles, see "Defining Project Roles" in Chapter 6,
"Defining Project Roles". See "Defining Jobs and Job Mapping" in Chapter 3,
"Establishing Your Enterprise Structure" for more information regarding jobs.

Defining a Job-Based Cost Rate Schedule

Define a job-based cost rate schedule to enable the generation of forecasts on the
cost of staffing requirements. To define this schedule, complete the following steps:
1. Navigate to the Rate Schedules form using the following menu path:
Setup > Expenditures > Rate Schedules
2. Enter a schedule name and a description of the schedule.
3. Select the organization that uses the schedule.
You can enter any organization from your hierarchy regardless of classification
or start and end dates.
4. Select the Job tab.
5. Select the appropriate jobs and enter their rates.

10-6 Oracle Project Resource Management Implementation and Administration Guide

 Implementing the Forecast Functionality

6. Save your work.

Note: Forecasts must be regenerated to reflect retroactively

changed cost rates.

Defining Bill Rate Schedules

Create a job-based bill rate schedule in Oracle Projects to enable the forecast
generation of revenue from staffing requirements. You can include bill rate
overrides in your forecasts. If you plan to utilize bill rate overrides, you will
establish them as they are needed.
For more information on bill rate overrides, see the Oracle Projects User Guide.

Updating Project Types with Employee and Job-Based Bill Rate Schedules
For any new project types, manually enter the appropriate job-based bill rate
schedule in the remaining field (either Job or employee-based) for each project type.

Defining Forecast-Related Profile Option

Define the profile option PA: Forecasting Period Type as either GL Period or PA
Period as applicable to your business using the following menu path through the
System Administrator responsibility:
Profile > System
This profile option is set only at the site level and determines the period type for
which you will generate forecast totals and the number of periods to display on the
forecast screens:
■ 13 periods for PA Period
■ 6 for GL Period
If you ever change the forecasting period type after you create forecasts, you must
regenerate all existing forecasts.

Defining Periods
In order to create forecast totals for the life of a project, you must define an
appropriate number of periods that span the life of your projects. These periods are
also necessary to create assignments for time periods in the future. You create these

Implementing Financial Forecasting 10-7

Implementing the Forecast Functionality

periods through Oracle General Ledger tables and migrate them to Oracle Projects
tables.
For more information on defining the time periods, refer to the Oracle General Ledger
User Guide or the Oracle Projects User Guide.

Defining Unassigned Time Tracking

Oracle Project Resource Management automatically generates totals for unassigned
time for all utilization jobs. The calculation for unassigned time subtracts both
provisional and confirmed assignment hours from the total capacity for each
available day. Any remaining hours generated from this calculation are assigned to
projects specifically implemented for the purpose of tracking unassigned hours.
To define unassigned time tracking projects, complete the following steps:
1. Login as Project Resource Management Super User.
2. Navigate to the Project Type form:
Setup > Projects > Project Types
3. Create a project type using the indirect project type class.
4. In the Details window, select the following options:
■ Administrative
■ Unassigned Time
5. Create a project template using the unassigned project type using the following
path:
Setup > Projects > Project Templates
6. Create a project using the unassigned project template.
Projects > Find Projects
Optionally, you can create two unassigned projects: one for billable jobs and one
for non-billable jobs.
7. Complete the options on the Unassigned Time Options tab. For more
information, refer to "Unassigned Time Options".
This type of project is used solely for tracking unassigned time for utilization and
forecasting calculations. Therefore, users cannot manually add any scheduled roles
to this project and the Add Requirement and Add Assignment options are not
available for this project.

10-8 Oracle Project Resource Management Implementation and Administration Guide

 Implementing the Forecast Functionality

Defining Forecasting Options

The Forecast Implementation Options provide implementation settings used for
resource scheduling, resource utilization, and financial forecasting at the operating
unit level. You can access these options using the following menu path:
Setup > Forecasting > Options
You have a choice of two tabs: Options and Unassigned Time Options. Complete the
options as follows:
1. In the Options tab, select the following options:
a. Check Include Admin Projects.
b. Enter a value in Max Historical Versions (suggested starting value: 5).
c. Enter the desired Utilization Calculation Method (suggested starting entry:
By Resource Capacity Hours).
d. Select at least one period type.
e. Enter the defaults for the Team Role Forecasting Options.
2. Select the Unassigned Time Options tab.
3. In the Billable People region, check Include in Forecast if you want to
summarize billable unassigned time in the financial forecasting reports. If you
select this option, enter values for the related fields (Unassigned Time Project,
Expenditure Type Class, and Expenditure Type.)
4. In the Non-Billable People region, check Include in Forecast if you want to
summarize non-billable unassigned time in the financial forecasting reports. If
you select this option, enter values for the related fields (Unassigned Time
Project, Expenditure Type Class, and Expenditure Type.)
The following sections provide details on the individual options.

Note: All forecast and unassigned time options must be defined

for each operating unit.

Implementing Financial Forecasting 10-9

Implementing the Forecast Functionality

Implementation Options
The following graphic depicts the Options tab:

Some of the fields are not currently in use, but have been provided for features
scheduled for future releases. The following table provides a list of fields and their
descriptions in the order they appear on the tab:

Field Description
Include Admin Projects Check to indicate that you want to include administrative
projects in project forecast totals. This field is scheduled for
future use in the forecasting functionality.
Note: Although this option is for future functionality, you
must enable this option for this release in order to avoid
errors because the application cannot yet exclude
administrative projects.

10-10 Oracle Project Resource Management Implementation and Administration Guide

 Implementing the Forecast Functionality

Field Description
Max Historical Versions Enter the maximum number of historical forecast versions that
you want to store. This field is scheduled for future use in the
forecasting functionality.
Note: At minimum, you must enter a value of 1.
Utilization Calculation Enter the desired method of calculating your resource
Method utilization. This field is scheduled for future use in the
forecasting functionality only and does not have any affect
utilization summarization or reporting.
Note: Although this option is for future functionality, a
selection is required. Capacity is the recommended
selection.
Period Type Check the desired period type (GL Period or PA Period) that the
forecasting process should use to generate the forecast totals.
This field is scheduled for future use in the forecasting
functionality.
Expenditure Type Class Select the Expenditure Type Class to classify the forecast items.
Expenditure Type Select the desired Expenditure Type to apply to all generated
forecast items.
Transfer Price Amount For future use in forecasting functionality
Type
Project Role Enter the role to display as the project owner. This value is
displayed in the Project Forecast List page.
Note: Defining this value is optional. If you leave this field
blank, the Project Owner column is hidden in the Project
Forecast List page.
Job-Based Cost Rate Select the job-based cost rate schedule to use for assignments.
Schedule
Classification Select the classification for which you want to generate forecast
totals. You can only select a classification where only one value
is allowed. The corresponding class code for each project is
displayed in the Project Forecast List page. Only those
classifications which are defined as mandatory in the project
template appear as choices for this field.
Note: Defining this value is optional. If you leave this field
blank, the Classification column is hidden in the Project
Forecast List page.

Implementing Financial Forecasting 10-11

Implementing the Forecast Functionality

For more information on expenditure types and project classifications, see Chapter
17, "Oracle Projects Setup and Implementation," in the Oracle Project User Guide.

Unassigned Time Options

The following graphic depicts the Unassigned Time Options tab:

This tab has two regions pertaining to the setup of billable people and non-billable
people respectively. The fields are the same for both regions. The following table
provides a list of the fields and their descriptions in the order they appear within a
region:

Field Description
Include in Forecast Check to indicate that you want to summarize unassigned time
in the project financial forecast totals.
Unassigned Time Project Enter the name of the project to which unassigned time should
be reported.
Expenditure Type Class Enter the expenditure type class with which unassigned time
should be associated.

10-12 Oracle Project Resource Management Implementation and Administration Guide

 Establishing Security on Forecast Functionality

Field Description
Expenditure Type Enter the expenditure type with which the unassigned time
should be associated.

You must enter values for these fields as applicable to billable and non-billable
unassigned time.

Establishing Security on Forecast Functionality

Users can view forecast hour and revenue totals for any project on which they are
active key members. You can provide viewing access to other users as well. Key
members and other users with the appropriate authority or security access can also
view project cost, margin, and margin percentage totals and generate project
forecast totals.
You can establish security for these features and functionality through granting
roles cost viewing access, granting forecast authority, and providing functions and
menu access.

Granting Cost Viewing Access to Roles

To grant a specific role the ability to view cost, margin, and margin percentage
totals, you can check the View Labor Cost checkbox on the Role Types form. To
access this form, use the Project Super User responsibility and follow this menu
path:
Setup > Project > Role Types

Granting Forecast Authority

You can grant a user forecast authority. This authority provides users the ability to
view all projects in an organization through the Multiple Project Forecast List. Users
can drill down on a project to view all amounts for hours, cost, revenue, margin and
margin percentage. Labor cost authority is assumed for users assigned this
authority. You can grant this authority using the following menu path:
Setup > Human Resources > Organization Authority
Business managers are likely candidates for these authority levels. You may grant
users these authorities at the organization level.

Implementing Financial Forecasting 10-13

Establishing Security on Forecast Functionality

Granting Forecast Function Access

You can add functions to menus associated with user roles to provide access to
forecast functionality. The forecast-related functions are:
■ Project Level View Forecast Security
This function provides users the ability to view existing project forecasts.
■ Project Level Edit Forecast Security
This function provides users the ability to generate project forecasts.
Typical users of the functionality that these security levels provide are project
managers or sales directors. For more information on how to edit menu and
function access, see "Understanding Role-Based Security" in Chapter 5,
"Configuring Your Organization Security".

10-14 Oracle Project Resource Management Implementation and Administration Guide

 11
Implementing Resource Utilization

The utilization functionality of Oracle Projects and Oracle Project Resource

Management enables you to generate actual and forecast totals of your resource
utilization. In addition, you can classify your resource hours to calculate utilization
percentages for:
■ Actual hours based on time card expenditures
■ Forecast hours based on schedule assignments
Oracle Project Resource Management generates forecasts for both provisional and
confirmed assignments enabling you to distinguish between real work hours and
potential work hours. This chapter discusses the business considerations and setup
requirements for resource utilization through the following topics:
■ Defining Your Utilization Strategy
■ Implementing Your Utilization Strategy
■ Defining the Utilization Profile Options

Note: Implementing Oracle Project Resource Management in

standalone mode enables you to generate and report the forecast
utilization totals. However, if you want to generate actual
utilization totals, you must also implement Oracle Projects Costing.
For more information on implementing Oracle Projects Costing, see
the Oracle Projects User Guide.

Implementing Resource Utilization 11-1

Defining Your Utilization Strategy

Defining Your Utilization Strategy

Prior to implementing utilization for your enterprise, you should understand how
the Oracle Project Resource Management application generates the utilization totals
and evaluate what you want these totals to represent. Through these considerations,
you must decide:
■ which resources should be included for reporting utilization
■ what reporting time periods you want to use
■ who will have access to the utilization totals
■ how resource hours are summarized for reporting purposes
The actual utilization totals are generated for all hours reported through employee
timecards. Forecast utilization totals are generated based on provisional and
confirmed assignments entered through Oracle Project Resource Management.
The utilization functionality classifies actual and forecast hours by work types
which enables you to:
■ identify each work type as Billable/Capitalizable or
Non-Billable/Non-Capitalizable
■ determine if specific non-billable/capitalizable work types will reduce capacity
■ define a weighting percentage for each Work Type for all capacity work types
.

Note: Work types defined as Non-Capacity always carry a 0%

weighting percentage.

The weighting percentage is applied to resource hours when summarizing those

hours for the utilization percentage calculation. Two utilization percentages are
calculated for both resource utilization categories and organization utilization
categories. The calculation for generating these percentages is as follows:
■ Capacity Method = sum of weighted hours / sum of unweighted capacity
hours
■ Total Worked Hours = sum of weighted hours /total weighted hours
Capacity hours are the total number of hours for the specified time period based on
the resource calendar. Actual calendar capacity is modified by subtracting any
recorded hours against the project tasks with non-capacity work types. Forecast

11-2 Oracle Project Resource Management Implementation and Administration Guide

 Defining Your Utilization Strategy

capacity is modified by any forecast hours from assignments with non-capacity

work types.

Utilization Time Periods

The utilization totals are provided for one or more of the following time periods:
■ Global Start Week
■ PA Period
■ GL Period
■ Quarter
■ Year

Understanding the Utilization Views

Resource hours are summarized into two distinct groups of utilization reporting
categories. These category groupings are used to create the following two utilization
views:
■ Resource Utilization View
This view summarizes actual and forecast utilization hours by Resource
Utilization Categories. The resource utilization percentage is calculated by
dividing the weighted resource utilization category hours by the specified
utilization method.
■ Organization Utilization View
This view summarizes actual and forecast hours by Organization Resource
Categories. The organization utilization percentage is calculated by dividing the
weighted organization utilization category hours by the specified utilization
method.
These utilization views provide you with two distinct managerial views of the work
that resources and their organizations have performed or will perform.

Implementing Resource Utilization 11-3

Defining Your Utilization Strategy

Choosing a Utilization Calculation Method

The calculation method you select determines the denominator for the utilization
percentage calculation. You have two methods from which to choose: capacity or
total worked hours. These calculation methods provide different percentages for the
utilization views.

Using the Capacity Calculation Method

This method uses the capacity hours as the denominator for the utilization
percentage calculation. The following table describes the calculation of the
utilization percentages for each utilization view using this calculation method.

Numerator Denominator Percentage

Utilization
View (Sum of A) (Sum of B) (Sum of A)/(Sum of B) * 100
Resource Sum of Resource Sum of Capacity Resource View Percentage
Utilization from for all Resources
Category Weighted
Hours for all Resources
Organization Sum of Organization Sum of Capacity Organization View
Utilization from for all Resources Percentage
Category Weighted
Hours for all Resources

Using the Total Worked Hours Calculation Method

This method uses the total number of hours recorded by time cards or scheduled on
assignments as the denominator. For actual utilization totals, the total number of
hours is calculated from reported timecard hours. For forecast utilization totals, the
total number of hours is calculated from scheduled confirmed assignments. Unlike
the capacity method, this method includes non-capacity work type hours.
The following table describes the calculation of the utilization percentages for each
utilization view using this calculation method.

Numerator Denominator Percentage

Utilization
View (Sum of A) (Sum of B) (Sum of A)/(Sum of B) * 100
Resource Resource Utilization Total worked Resource View Percentage by
Utilization Category Weighted hours for a Resource
View for a Hours by Resource resource
Resource

11-4 Oracle Project Resource Management Implementation and Administration Guide

 Defining Your Utilization Strategy

Numerator Denominator Percentage

Utilization
View (Sum of A) (Sum of B) (Sum of A)/(Sum of B) * 100
Organization Organization Total worked Organization View
Utilization Utilization Category hours for a Percentage by Resource
View for a Weighted Hours by resource
Resource Resource
Organization Sum of resource Sum of total Resource View by
Utilization utilization category worked hours Organization
View for an weighted hours for all for all resources
Organization resources

Understanding the Utilization Reporting

Utilization totals are reported to the following organization roles:
■ Organization Manager
Organization utilization reports for all resource hours for the selected time
period a resource is assigned to the specific organization.The organization
manager can view utilization for the entire organization as well as drill down to
the utilization of individual resources.
■ Resource Manager
Resource utilization reports for all resource hours for the selected time period
where the resource is currently assigned to the resource manager regardless of
organization assignment.
■ Individual Resource
Resources can monitor their personal performances through viewing all their
reported and assigned hours for a selected time period.
You can view utilization totals through the following pages:
■ Organization Utilization
■ Resource Utilization by Organization Manager
■ Resource Utilization by Resource Manager
■ Personal Utilization
Each page is described in the following sections.

Implementing Resource Utilization 11-5

Defining Your Utilization Strategy

Reviewing the Organization Utilization Page

This page provides utilization totals for an organization based on a specified time
period. The calculations for the totals on this page are defined below.

Employees and Others (Summary) The employee headcount includes a count of all
utilizable employees (employees with an assigned job that qualifies for utilization
calculations) and resource managers assigned to the organization as of the first day
in the selected time period (Year, Quarter, PA Period, GL Period, Global Week).
Other headcount includes all utilizable non-employees assigned to the organization
as of the first day in the selected time period (Year, Quarter, PA Period, GL Period,
Global Week).
For the period types of PA Period, GL Period, and Global Week, the number of
employees included in the utilization related numbers is the count of employees
assigned to the organization for the period.
For the period types of Year and Quarter, the number of employees included in the
utilization related numbers is the total as of the beginning of the period plus any
new headcount addition.

Employees and Others (Sub-Organization Details) The employee headcount includes a

count of all utilizable employees and resource managers assigned to the
organization as of the first day in the selected time period (Year, Quarter, PA Period,
GL Period, Global Week). Other headcount includes all utilizable non-employees
assigned to the organization as of the first day in the selected time period (Year,
Quarter, PA Period, GL Period, Global Week).

Actual Capacity (same as Forecast Capacity) This value represents the net available
hours for the organization, which is the total available hours minus reduced
capacity hours.
The total available hours is derived from the schedule of each resource. This value
can be correlated to the values shown in the Staffing Home for each of the resources
within the organization.
The reduced capacity hours are summarized from transactions that are logged
against a work type which reduces capacity, such as unpaid leave.

Actual Worked This value is a sum of the hours from the reported timecards of all
resources within the organization for the specified time period.

Weighted Actual This value represents the sum total of weighted actual hours for the
organization. It is calculated by multiplying the total from each timecard with the

11-6 Oracle Project Resource Management Implementation and Administration Guide

 Defining Your Utilization Strategy

weighting percentage of the organization before summing them all up. The
weighting percentage is taken from the organization utilization category as defined
for the work type associated with each job.

Actual Utilization (%) This value represents the Weighted Actual Hours as a gross
percentage of Actual Capacity or Actual Worked (depending upon the selected filter
on the page.) It is calculated by dividing the actual weighted hours by utilization
calculation method (capacity or total worked hours) for the organization and
specified time period.

Forecast Work This value represents the sum total of scheduled hours for the
organization for the specified time period.

Weighted Forecast This value represents the sum total of weighted forecast hours for
the organization. It is calculated by multiplying the total hours for each forecast
item with the weighting percentage of the organization before summing them all
up. The weighting percentage is taken from the organization utilization category as
defined for the work type associated with each job.

Forecast Utilization (%) This value represents the Weighted Forecast Hours as a gross
percentage of Forecast Capacity or Forecast Work (depending upon the selected
filter for the page.) It is calculated by dividing the total forecast weighted hours by
the utilization calculation method (capacity or total worked hours) for the
organization and specified time period.

Reviewing the Resource Utilization by Organization Manager Page

This page provides utilization totals for all resources under a particular
organization manager based on a specified time period. The calculations for the
totals on this page are defined below.

Employees and Others (Summary) The employee headcount summary includes a count
of all utilizable employees and resource managers assigned to the organization as of
the first day in the selected time period (PA Period, GL Period, and Global Week).
For the period types of Year and Quarter, the employee headcount summary
includes a count of all utilizable employees and resource managers assigned to the
organization as of the beginning of the period plus any headcount addition on the
first day of each primary period (GL Period).
Other headcount summary includes all utilizable non-employees assigned to the
organization as of the first day in the selected time period (PA Period, GL Period,

Implementing Resource Utilization 11-7

Defining Your Utilization Strategy

and Global Week). For the period types of Year and Quarter, other headcount
summary includes all utilizable non-employees assigned to the organization as of
the beginning of the period plus any headcount addition on the first day of each
primary period (GL Period).

Person Details This link lists all utilizable employees and managers assigned to the
organization as of the first day in the selected time period (PA Period, GL Period,
and Global Week). For the period types of Year and Quarter, the list includes a count
of all utilizable employees and resource managers assigned to the organization as of
the beginning of the period plus any headcount addition on the first day of each
primary period (GL Period).
Other headcount summary includes all utilizable non-employees assigned to the
organization as of the first day in the selected time period (PA Period, GL Period,
and Global Week). For the period types of Year and Quarter, other headcount
summary includes all utilizable non-employees assigned to the as of the beginning
of the period plus any headcount addition on the first day of each primary period
(GL Period).

Reviewing the Resource Utilization by Resource Manager Page

This page provides utilization totals for all resources under a particular resource
manager. The calculations for the totals on this page are defined below.

Employees and Others This value is a headcount of all utilizable employees reporting
to the manager as of the current system date, including future-date employees.
Other headcount summary includes all utilizable non-employees assigned to the
manager as of the current system date, including future-dated non-employees.

Actual Capacity (same as Forecast Capacity) This value represents the net available
hours for the resource (the total available hours minus reduced capacity hours.)
The total available hours is derived from the schedule of each resource. This value
can be correlated to the values shown in the Staffing Home for each of the resource
within the organization.
The reduced capacity hours are summarized from confirmed assignments that are
logged against a work type which reduces capacity, such as unassigned time.

Actual Worked This value represents the sum total of actual worked hours for the
resource as reported on submitted timecards.

11-8 Oracle Project Resource Management Implementation and Administration Guide

 Defining Your Utilization Strategy

Weighted Actual This value represents the sum total of weighted actual hours for the
resource. It is calculated by multiplying the total hours of each timecard with the
weighting percentage of the resource before summing them all up. The weighting
percentage is taken from the resource utilization category as defined for the work
type of the assigned job.

Actual Utilization (%) This value represents the Weighted Hours as a percentage of
Actual Capacity or Actual Worked Hours. It is calculated by dividing the Weighted
Actual Hours by the utilization calculation method (capacity or total worked
hours).

Forecast Work This value is the total number of hours of the forecast items for the
resource.

Weighted Forecast This value represents the sum total of weighted forecast hours for
the resource. It is calculated by multiplying the total hours for each forecast item by
the weighting percentage for the resource before summing them all up. The
weighting percentage is taken from the resource utilization category as defined for
the work type of the assigned job.

Forecast Utilization (%) This value represents the weighted hours as a percentage of
Forecast Capacity or Forecast Work (depending upon the selected filter for the
page.) It is calculated by dividing the Weighted Forecast Hours by the utilization
calculation method (capacity or total worked hours).

Reviewing the Personal Utilization Page

This page provides utilization totals for a single resource. The calculations for the
totals on this page are defined below.

Capacity Amount Capacity amount represents the total resource available hours
minus any assignment hours with a reduced capacity work type, such as
unassigned time. The original resource available hours can also be viewed in the
Staffing Home page. The actual and forecast worked hours displayed are normal
unweighted hours. However, the utilization total is calculated based on the
Resource Weighted Hours.
You can specify the default resource utilization calculation method (by total worked
hours or capacity) using the profile option: PA: Resource Utilization Calculation
Method.

Implementing Resource Utilization 11-9

Defining Your Utilization Strategy

The default resource utilization period type is specified in the profile option: PA:
Resource Utilization Period Type.

Capacity Hours This value represents the net available hours for the resource, (the
total available hours minus reduced capacity hours.) The total available hours is
derived from the schedule of each resource. This value can be correlated to the
values shown in the Staffing Home for each resource within the organization.
The reduced capacity hours are summarized from transactions that are logged
against a work type which reduces capacity, such as unassigned time.

Worked Hours This value represents the sum total of worked hours for the resource
obtained from submitted timecards.

Utilization This value represents the Weighted Hours for the resource as a percentage
of Actual Capacity or Actual Worked (depending upon the selected filter for the
page.)

(Forecast) Provisional Hours This value represents the sum total of forecast hours for
the resource. It is calculated by summing the totals of all forecast items for the
resource which have been marked as provisional.

(Forecast) Confirmed Hours This value represents the difference between the Forecast
Work Hours and the Provisional Hours (Forecast Work Hours – Provisional Hours.)

(Forecast) Utilization This value represents the Confirmed Weighted Hours for the resource
as a percentage of Actual Capacity or Actual Worked (depending upon the selected filter on
the page.)

Correlation of Utilization Totals

You can correlate the utilization total in the Resource Utilization by Organization
Manager page with the Personal Utilization page by selecting the following filter
parameters:
■ Utilization view: Resource
■ Include only: Confirmed Assignment
Ensure that the selected values for Period Type and Utilization Calculation
Method/Show Percentage By parameters are similar to the default profile values for
the Personal Utilization page.

11-10 Oracle Project Resource Management Implementation and Administration Guide

 Defining Your Utilization Strategy

You can also correlate the utilization total in the Resource Utilization by
Organization Manager page with the total shown in the Resource Utilization by
Resource Manager page by selecting the following filter parameter:
■ Select Manager = <Manager Name>
Selecting this filter returns the same resources, provided that the resource manager
is managing resources in the same organization authorized to the organization
manager. The actual and forecast worked hours are the same if the resource works
in the same organization during the specified period of time. The number may be
different if the resource also works in different organizations during the specified
period of time. This difference is because of the following page definitions:
■ Resource Utilization by Organization Manager displays utilization for resources
with a specific resource manager, period, and organization.
■ Resource Utilization by Resource Manager displays utilization for resources
with a resource manager who is managing the resources for a specific period.

Implementing Resource Utilization 11-11

Implementing Your Utilization Strategy

Implementing Your Utilization Strategy

Implementation options and functions are available for you to tailor the utilization
calculations to your business needs as well as provide viewing ability to your users.
These options include:
■ Determining Utilization Jobs
■ Establishing Utilization Categories and Work Types
■ Implementing Utilization Forecasting Functionality
■ Establishing Unassigned Time Tracking
■ Choosing Your Reporting Time Period
■ Granting Utilization Authority

Determining Utilization Jobs

All HR jobs have a flag which indicates whether or not the job is tracked for
utilization. As resources are assigned to these jobs, you can track their hours in the
utilization reports.
To include jobs in utilization, complete the following steps:
1. Login as the Project Resource Management Super User.
2. Navigate to the Jobs form:
Setup > Human Resources > Jobs
3. Select the desired HR Job Group
4. For each job, select Others, then Extra Information.
5. In the Job Category Details window, select Yes or No for Include in Utilization.

Note: The Billable choice is used only for financial forecast

reporting. See Chapter 10, "Implementing Financial Forecasting" for
implementation and usage information.

11-12 Oracle Project Resource Management Implementation and Administration Guide

 Implementing Your Utilization Strategy

Establishing Utilization Categories and Work Types

In order to use the utilization functionality, you must define work types and
utilization categories. These attributes provide a means of classifying and sorting
the work into logical and meaningful utilization reports.

Defining Utilization Categories

Utilization categories are classifications of work types for reporting purposes. Work
types are summarized into utilization categories and can carry different weighting
percentages to provide two distinct Utilization Views:
■ Resource Utilization View - to provide a utilization view for resources and their
managers
■ Organization Utilization View - to provide business managers a utilization
view for their organizations and related resources
These utilization views enable you to create two distinct managerial views of the
work that resources and their organizations have performed or will perform. You
can use each utilization category for one or both utilization views.

Creating Utilization Categories To create your utilization categories, use the following
menu path:
Projects Menu > Setup > Utilization > Utilization Categories
When you define a utilization category, you assign a code, a meaning, and
description, as well as the attributes as applicable to the category listed in the
following table:

Attribute Description
Description Enter a long description for the utilization category. This field is
optional.
Reporting Order Determine the display order for the categories on the screens
and reports.
Effective Dates Enter the beginning and ending date for which the utilization
category is effective.

Using Utilization Categories The effectiveness of utilization categories is best

illustrated through an example. In the following example, a resource has performed
warranty work which is not billable. The challenge is how to reflect that in your
utilization reporting so that it does not inflate your revenue-generating utilization.

Implementing Resource Utilization 11-13

Implementing Your Utilization Strategy

A resource is assigned to complete some rework (warranty) work on an existing

project. The enterprise (project organization) will not receive any revenue for
the extra work performed. The assignment has been allocated a work type
called "Warranty" which automatically classifies the timecard entries entered by
the resource.
As the project organization is responsible for the overall performance of the
project, it should not consider rework as receiving utilization credit. Otherwise,
the utilization reports provide a false representation of the total number of
hours being effectively utilized by the resources of the organization. This
company set up the utilization view for the organization to handle this
situation. It filters out work hours associated with the Warranty work type by
placing a 0% weighting on the organization categories of the work type.
However, the company does not want the contract-related work to negatively
affect the personal utilization percentage of the resource. So, the weighting for
the resource categories of the Warranty work type was set at 80%. Doing so,
ensures the resource receives a discounted credit of the performed effort.

Defining Work Types

Work types are classifications of work. As an example, a professional software
services enterprise typically needs work types for the following areas:
■ Analysis, Design, Implementation, Support [Billable/Productive work]
■ Rework [Non-Billable/Productive work]
■ Internal IT Support, Internal Reproduction [Internal Billable/Productive work]
■ Bid & Proposal, Marketing [Non-Billable/Selling]
■ Sick Pay, Holiday, Jury Duty [Non-Capacity/Non-Productive]

Creating Work Types To create your work types, use the following menu path:
Projects Menu > Setup > Utilization > Work Types
When you define a work type, you assign a name and a description. The following
table provides a list of attributes you can define for the work type:

Attribute Description
Billable/Capitalizable Check to identify a work type as being eligible for use
on a billable capitalizable task.

11-14 Oracle Project Resource Management Implementation and Administration Guide

 Implementing Your Utilization Strategy

Attribute Description
Non-Capacity Check to calculate capacity summarization by
subtracting the work type hours from the total capacity
and total work hours. Only Non-Billable/Capitalizable
work types may select this option If this attribute is
enabled, you cannot enter weighting values for the
work type.
Resource Utilization Category Select the utilization category in which the work type
should be considered for resource utilization
calculations.
Resource Weighting Percentage Enter a value between 0 and 100. The utilization
functionality uses this value to define utilization
calculations. The default value is 100% if the work type
is billable or capitalizable, otherwise, it defaults to 0.
Organization Utilization Select the utilization category in which the work type
Category should be considered for organization utilization
calculations.
Organization Weighting Enter a value between 0 and 100. The utilization
Percentage functionality uses this value to define utilization
calculations. The default value is 100% if the work type
is billable or capitalizable, otherwise, it defaults to 0.
Standard Effective Dates Enter the date range for which the work type is
effective.

Using Work Types You assign work types to project types, projects, tasks, and
assignments. The implementation process initially assigns default work types to
existing project types. You can modify these defaults as appropriate for your
business needs. Work types assigned to project types default to associated projects
and templates, and eventually, to the tasks and assignments of the project. You can
override a work type at the project, assignment, and task levels. However, an
override does not carry down to existing child tasks or assignments. You must
update each existing task and assignment individually.
To assign work types for forecast items on assignments, navigate to the Add
Assignment page.
To assign work types to tasks for actual items, navigate to:
Project > Task > Options > Task Detail

Implementing Resource Utilization 11-15

Implementing Your Utilization Strategy

Note: You can assign Billable/Capitalizable work types only to

billable tasks (tasks which have the Billable flag checked.)

Implementing Utilization Forecasting Functionality

Oracle Project Resource Management creates the forecast utilization totals for both
both provisional and confirmed assignments. These totals are based on forecast
items. Forecast items are generated for each day of an assignment or requirement.
The implementation options determine how forecast items are generated and their
default attributes. For more information on the Forecast Implementation Options,
see "Defining Forecasting Options" in Chapter 10, "Implementing Financial
Forecasting".

Establishing Unassigned Time Tracking

Oracle Project Resource Management automatically generates totals for forecast
unassigned time for all utilizable resources. The calculation for forecast unassigned
time subtracts both forecast provisional and forecast confirmed assignment hours
from the forecast total capacity for each available day of the resource. Any
remaining hours generated from this calculation are assigned to projects specifically
implemented for the purpose of tracking unassigned hours.
For more instructions on how to establish unassigned time tracking, see "Defining
Unassigned Time Tracking" in Chapter 10, "Implementing Financial Forecasting".

Choosing Your Reporting Time Period

The reporting time period has a direct impact on how your utilization totals are
calculated. Therefore, you have a choice on which periods you want to summarize
your enterprise and organization utilization totals. Once this choice is made and
you have run the utilization summarization program, you cannot change it.
You have three reporting periods on which you can perform utilization reporting:
GL Period, PA Period, and Global Week.The GL Period option summarizes the
utilization totals into financial general ledger period totals. The PA Period option
summarizes the utilization totals in periods distinctly different from your GL
Period. The Global Week option summarizes utilization totals by weeks (7 day
periods). This particular option is useful for calculation totals across the

11-16 Oracle Project Resource Management Implementation and Administration Guide

 Implementing Your Utilization Strategy

organization which have different financial calendar periods. It helps provide an

accurate picture of the totals on a enterprise basis.
To define your utilization time periods, complete the following steps:
1. Login as Project Resource Management Super User.
2. Navigate to the Utilization Options form.
3. Select at least one of the following options:
■ PA period
■ GL Period
■ Global Week

Granting Utilization Authority

You can provide your users the ability to view resource or organization utilization
totals through:
■ assigning specific responsibilities
■ assigning HR supervisors to employee assignments
■ granting Organization Utilization Authority

Review of Responsibilities
The following predefined responsibilities allow different levels of access to the
utilization information:
■ Organization Manager Responsibility
This responsibility provides access to the Organization Utilization page. This
page displays utilization totals for the organizations for which the business
manager oversees. It also provides the ability to drill-down to individual
summary amounts for resources assigned to the organization or
suborganization.
■ Resource Manager Responsibility
This responsibility provides access to the Resource Utilization page. This page
displays utilization totals for all resources reporting to the manager. These
resources include any person who has the Resource Manager currently assigned

Implementing Resource Utilization 11-17

Implementing Your Utilization Strategy

as their supervisor in their HR assignment. It also provides the ability to

drill-down to resources who are subordinates to direct reports.
■ Team Member Responsibility
This responsibility provides access to the Personal Utilization page to view
personal utilization totals.

Granting Organization Utilization Authority

The Organization Utilization Authority enables a user to view the utilization
amounts for an organization, all direct resources of the organization, all the
suborganizations, and the resources of those suborganizations.
To grant this authority to individual users, navigate to:
Projects menu > Human Resources > Organization Authority
For more information on this authority, see "Assigning Organizational Authority" in
Chapter 5, "Configuring Your Organization Security".

11-18 Oracle Project Resource Management Implementation and Administration Guide

 Defining the Utilization Profile Options

Defining the Utilization Profile Options

You have control over how utilization totals are processed through the following
profile options:
■ PA: Global Week Start Day
■ PA: Organization Utilization Default Period Type
■ PA: Organization Utilization Default Calculation Method
■ PA: Resource Utilization Period Type
■ PA: Resource Utilization Calculation Method
■ PA: Utilization Calculation Begin Date
Each profile option provides a different control on how your utilization totals are
calculated and processed. All utilization profile options are set at the site level.

PA: Global Week Start Day

This profile option specifies the weekday that you want recognized as the beginning
of the week. Set this profile option at the site level. Valid values are 1 through 7
representing the days of the week. The definition of the numeric values are:
1 = Sunday
2 = Monday
3 = Tuesday
4 = Wednesday
5 = Thursday
6 = Friday
7 = Saturday

Note: Global weeks use the date of the first day of the defined
week as the name of the period. For example, if you define Monday
as your week start day, then the name of each week period will be
the date of each Monday.

PA: Organization Utilization Default Period Type

This profile option determines the default period type used when initially entering
an organization or resource utilization reporting screen. Your choices are: PA

Implementing Resource Utilization 11-19

Defining the Utilization Profile Options

Period, GL Period, Global Week, Quarter, and Year. You must use one of the period
types selected in Utilization Options.

PA: Organization Utilization Default Calculation Method

This profile option determines the default utilization percentage to show when
initially entering an organization utilization reporting screen. Your choices are
Capacity or Total Worked Hours.

PA: Resource Utilization Period Type

This profile option determines the default period type used when initially entering
a resource utilization reporting screen. Your choices are PA Period, GL Period, and
Global Week. You must use one of the period types selected in Utilization Options.

PA: Resource Utilization Calculation Method

This profile option determines the default period type used when initially entering
a resource utilization reporting screen for an individual. Your choices are Capacity
or Total Worked Hours.

PA: Utilization Calculation Begin Date

This profile option determines the date to begin calculating the utilization hours for
both actuals and forecast amounts. No resource hours prior to this date will be
included in any of the generated totals.
After setting this particular profile option, you must run a concurrent process called
PRC: Identify Transactions for Actuals Utilization to flag all transactions that should
be excluded from the summarization of actual utilization hours. When this process
is run, any transaction with a date prior to the date specified in this profile option
will be flagged as a non-utilization transaction. Therefore, these transactions are
ignored when the utilization totals are generated.
This process is an optional one-time implementation step and does not have to be
repeated unless you change the date in the PA: Utilization Calculation Begin Date
profile option.

Note: Setting this profile option and running the related

concurrent process is optional. Only use this profile option and
process if you want to exclude a major portion of existing data from
the utilization totals.

11-20 Oracle Project Resource Management Implementation and Administration Guide

 12
Setting Up for Reporting Capabilities

Oracle Project Resource Management transactional reporting is supported by a

web-based Oracle Discoverer solution. The predefined workbooks, worksheets and
End User Layer (EUL) provide you and your users the ability to query and
manipulate transactional data to proactively measure and analyze corporate
performance.
After you implement the reporting solution, users can access the predefined Oracle
Discoverer reports from the self-service Project Resource Management menu
structure.
This chapter covers the setup and usage of the reporting solution through the
following topics:
■ Oracle Discoverer 4i Postinstallation Tasks
■ Oracle Discoverer 3i Postinstallation Tasks
■ Test Your Installation and Set Up
■ Overview of the Business Areas and Business Views
■ Security Overview
■ Discoverer Workbooks

Recommendation: To get the maximum benefit of the reporting

solution of PJR we recommend that you use Discoverer 4i.

Note: To use the enhanced functionality of Discoverer set the pro-

file option ICX_DISCOVERER_USE_VIEWER to Yes when setting
up the Discoverer.

Setting Up for Reporting Capabilities 12-1

Oracle Discoverer 4i Postinstallation Tasks

Oracle Discoverer 4i Postinstallation Tasks

For installation instructions for Discoverer 4i, refer to the Discoverer 4i with Oracle
Applications 11i document #139516.1on Metalink.
In the above document, in the sections called "Step 5 5.6 Import using adupdeul.sh
mode=complete" and "Appendix A.1 Import using adupdeul.sh mode=driver", you
can use the following two different parameters to import all shipped Project
Resource Management executable files:
■ use mode=complete
■ use mode= driver and driver=pasb020.drv,pasb018.drv,pasb010.drv,pasb017.drv
If you are currently using Discoverer 4i, please refer to the instructions in Discoverer
4i Maintenance for Oracle Applications 11i document #182106.1 on Metalink.

12-2 Oracle Project Resource Management Implementation and Administration Guide

 Oracle Discoverer 3i Postinstallation Tasks

Oracle Discoverer 3i Postinstallation Tasks

This section describes the Oracle Discoverer install and setup tasks for integration
with Oracle Project Resource Management. To set up the reporting solution, you
must use the Administrator Edition or client/server version of Discoverer. To set up
the User Edition, you must use the Web Discoverer version, with a few exceptions,
which are noted accordingly.
Before you start, you must complete the following activities:
1. Install Oracle Discoverer Administration Edition.
To access the Discoverer workbooks provided with Oracle Project Resource
Management, install Oracle Discoverer.
2. Install Oracle Web Discoverer.
For installation instructions, refer to the Oracle Discoverer 3.1 Installation and
Administration Guide.

Oracle Discoverer Postinstallation Tasks Checklist

The following tasks are covered in this section:
1. Create the End User Layer.
2. Modify the End User Layer Owner’s Indexes.
3. Copy files to Discoverer Administration Tier.
4. Connect to Discoverer Administration Edition.
5. Import the End User Layer EEX File.
6. Set up access to Business Areas and End User Discoverer Edition.
7. Refresh Business Areas.
8. Connect to Discoverer User Edition.
9. Install the Reporting workbooks.
When you have completed these steps, verify that:
■ The EUL owner (database user) id has a suffix corresponding to the end user
language, for example:
EUL_US

■ The EUL owner has necessary privileges to FND objects.

Setting Up for Reporting Capabilities 12-3

Oracle Discoverer 3i Postinstallation Tasks

Refer to the Oracle Discoverer 3.1 Administration Guide for details.

■ An application mode EUL owner exists. When creating the EUL the /APPS_
MODE parameter was added to the command line.
■ The ICX profiles in Oracle Applications are correct, for example: ICX_
DISCOVERER_LAUNCHER, ICX_DEFAULT_EUL, ICX_DEFAULT_
WORKBOOK_OWN, and SESSION_COOKIE_NAME.
These profile options are part of the set up of Oracle Discoverer and the
self-service environment for Oracle Project Resource Management. For more
information on these and other required ICX profile options, refer to Oracle
Discoverer 3.1 Administration Guide and the "Setting Up Your Self-Service
Environment" in Chapter 9, "Defining the Project Environment" within this
guide.

Create the End User Layer

Complete the following steps to create the End User Layer.
1. Create a database user that you want to designate as the End User Layer owner
and grant database access to it.
2. Create the application mode EUL.

Creating the Database User Set the name of the end user layer owner (database user)
to EUL_<language>, for example: EUL_US. Use the following script to perform this
task:
create user eul_us
identified by eul
default tablespace user_data
temporary tablespace temp;

Creating the Applications Mode EUL

1. Issue a set of grants to allow the EUL owner select access to certain
Applications Object Library tables. This step is necessary in order for
Discoverer to support the structure of Applications user IDs and
responsibilities. To do this, connect to the database using the account specified
in the FNDNAM environment variable (typically “APPS”) and execute the
following statements.
connect system/manager@<database>
grant connect, resource to &EULOWNER

12-4 Oracle Project Resource Management Implementation and Administration Guide

 Oracle Discoverer 3i Postinstallation Tasks

connect apps/apps@<database>
grant select on FND_USER to &EULOWNER
grant select on FND_APPLICATION to &EULOWNER
grant select on FND_USER_RESP_GROUPS to &EULOWNER
grant select on FND_RESPONSIBILITY_VL to &EULOWNER
grant select on FND_ORACLE_USERID to &EULOWNER
grant select on FND_DATA_GROUP_UNITS to &EULOWNER
grant select on FND_PRODUCT_INSTALLATIONS to &EULOWNER
grant select on FND_SECURITY_GROUPS_VL to &EULOWNER
grant execute on FND_CLIENT_INFO to &EULOWNER

2. Create an Applications mode from the Discoverer Administration Edition.

An Applications mode EUL is one that can be administered using the Oracle
Applications security model in place of the database security model. There are
two ways of doing this, both invoking the Administration edition from the
command line:
DIS31ADM.exe /APPS_MODE

Starts the Administration Edition in Applications mode. Any EULs created will
by default be Applications mode EULs.
DIS31ADM.exe /APPS_MODE /CREATE_EUL /CONNECT eul_owner/password@database

This command creates an Applications mode EUL from the command line in
batch mode.
3. Note that the EUL owner must be an Oracle database userid, not an Oracle
Applications userid. The easiest way to create an EUL with a new database
userid as the owner is to log onto the Discoverer Administration edition as the
SYSTEM user, and in step two of the Create EUL Wizard choose “Create a new
user.” It is recommended that you create the EUL in a separate schema from the
APPS schema that contains the Oracle Applications tables and views. The
primary reason for this is that by creating the EUL in a separate schema it is
easier to migrate the EUL from test environment to production environment
using database import/export.
4. Next you need to ensure that the EUL owner has select access to the
appropriate Applications tables and views where the data is stored. If you are
interested in creating Discoverer folders that span multiple tables you may
want to grant select any table privilege to the EUL owner. Otherwise, grant
select access to just the tables you wish to create Discoverer folders on.

Setting Up for Reporting Capabilities 12-5

Oracle Discoverer 3i Postinstallation Tasks

Modify the Indexes of the End User Layer Owner

Complete the following steps from the R11 Admin tier to modify the maximum
extents of the indexes in the End User Layer.
1. Connect to your database server using SQL/Plus as the End User Layer (for
example, EUL_US) owner.
2. At the SQL prompt, enter
$BIS_TOP/admin/sql/BISALTIN.sql

Copy Files to Discoverer Administration Tier

In order to access Discoverer-related files through the Discoverer Administration
and End User Editions, they must be copied to the Discoverer Administration Tier.
The file PAPRMEUL.eex is created in the $AU_TOP/discover/<language>/
directory when you install the Oracle Project Resource Management Reporting
product.
1. Copy the file PAPRMEUL.eex from the $AU_TOP/discover/<language>/
directory to an appropriate directory from where it can be imported into the
Discoverer Administration Edition.
2. Copy the sql script BISEULBA.sql from the $BIS_TOP/admin/sql/ directory
into the same temporary directory you used in step 1. Optionally, mount the
$AU_TOP/discover/<language> directory on to the Discovery Administration
Tier.
3. Copy the Discoverer Workbooks from the $AU_TOP/discover/<language>/
directory to a new directory where they can be saved to the database using the
Discoverer User Edition. The workbooks installed are:
■ PASCHRES.dis
■ PAAVLRES.dis
■ PAOVCRES.dis
■ PASALPIP.dis
■ PAREQPRJ.dis

12-6 Oracle Project Resource Management Implementation and Administration Guide

 Oracle Discoverer 3i Postinstallation Tasks

Connect to Discoverer Administration Edition

1. Log in to the Discoverer Administration Edition in application mode, for
example:
D:\orant\DISCVR31\DIS31ADM.EXE /APPS_MODE

2. Connect to the database, for example:

eul_us/eul@cus115

3. Select File > Set Default EUL.

Import the End User Layer EEX File

The Project Resource Management EEX file must be imported into the Discoverer
End User Layer. Select the EUL for which you want the EEX file to be imported, for
example, EUL_US.

Note: Before beginning the import process, increase the size of the
Rollback Segments to a minimum of 10 megabytes. After the import
has been completed, reset the Rollback Segments to their original
sizes.

To import the EEX file, complete the following steps:

1. Open an MS-DOS command window and navigate to the directory in which the
EEX file is located. Enter the following commands at the command prompt:
start /wait <ORACLE_HOME>\discvr31\dis31adm /APPS_MODE
/CONNECT <EUL_Owner>/EUL_Owner_password>@<Connect_string>
/IMPORT paprmeul.eex /eul<EUL_Owner_in_uppercase> /log eulimport.log

Where:
■ <ORACLE_HOME> is the top directory for Oracle products installed on the
NT server
■ <EUL Owner> is the database user created above
■ <EUL Owner password> is the database owner password
■ <Connect_string> is SQL*Net database connect string

Setting Up for Reporting Capabilities 12-7

Oracle Discoverer 3i Postinstallation Tasks

■ <EUL_Owner_in_uppercase>

.
Note: Enter the EUL owner schema in uppercase after the
key/EUL when invoking the second command. For example:
start /wait d:\orant\discvr31\dis31amd /APPS_MODE
/CONNECT eul_us/eul@apps /IMPORT PAPRMEUL.eex /eul EUL_US
/log eulimport.log

2. Check on the progress of the import process by pointing to the Discoverer icon
in the right lower corner of your toolbar.
Inspect the eulimport.log file to ensure that the Project Resource Management
EEX file was imported into the End User Layer successfully.
Alternatively, you can log in to the Discoverer Administration Edition and select
File > Import. Specify the location of the PAPRMEUL.eex file to complete the
import.

Set Up Access to Business Areas and End User Discoverer Edition

You must grant users access to the Discoverer Administrator and User Editions in
order for the users to open these applications. However, the users also need user
and responsibility access to the Business Areas in order to perform any reporting
activities on the Project Resource Management data.
To grant user access to Oracle Discover Administration and User Editions:
1. Log in to the Discoverer Administration Edition in application mode, for
example:
D:\orant\DISCVR31\DIS31ADM.EXE/APPS_MODE

2. Select Tools > Privileges.

3. Select the user/responsibility (role) to which you need to grant access, for
example, Project Resource Management Super User.
4. Grant the responsibility either the User Edition or the Administration Edition
access.

Reminder: If this responsibility is not a Self-Service responsibility,

it cannot be accessed through the Self-Service logon.

12-8 Oracle Project Resource Management Implementation and Administration Guide

 Oracle Discoverer 3i Postinstallation Tasks

To grant user/responsibilities access to Business Areas:

1. Log in to the Discoverer Administration Edition in application mode, for
example:
D:\orant\DISCVR31\DIS31ADM.EXE/APPS_MODE

2. Select Tools > Security.

3. Select the user/responsibility (role) to which you need to grant access, for
example, Project Resource Management Super User.
4. Select the business areas to which you want to grant this user/responsibility
access.
5. Check the Allow Administration checkbox for the business areas if this
responsibility needs administration access for tasks such as Refresh from the
database.

Refresh Business Areas

The following steps synchronize the information in the Discoverer End User Layer
and the underlying Oracle Applications data model.
1. Connect to Discoverer Administration Edition by invoking from the command
line D:\orant\DISCVR31\DIS31ADM.EXE /APPS_MODE
2. Connect to the database as an application user, for example:
SERVICES:Project Resource Management Super User:Standard/welcome@cus115

3. Set Default EUL.

4. Select all your business areas.
5. Select File > Refresh
6. Verify that the folders refresh is successful.

Connect to Discoverer User Edition

To invoke Discoverer User Edition:
1. Log in to the Discoverer User Edition in application mode, for example:
\orant\DISCVR31\DIS31USR.EXE

Setting Up for Reporting Capabilities 12-9

Oracle Discoverer 3i Postinstallation Tasks

2. Connect to the database, for example:

SERVICES:Project Resource Management Super User:Standard/welcome@cus115

3. Select Tools > Options.

4. Select the EUL tab and check the default EUL, for example, EUL_US.

Install the Project Resource Management Reporting Workbooks for Discoverer

The following steps explain how to save the workbooks to your database so that
users can access the workbooks through Oracle Web Discoverer.
1. Log in to the Discoverer User Edition in application mode, for example:
D:\orant\DISCVR31\DIS31USR.EXE

When asked for the login information, select Cancel.

2. While in Discoverer 3.1 User Edition, select Tools > Options and ensure that the
checkbox labeled “Display warning when opening workbook saved in a
different database account” is checked.
3. Exit from the Discoverer User Edition.
4. To save the Discoverer workbooks from the temporary staging area into the
database, open an MS-DOS window and change directories to the staging area
where the workbooks were saved. Refer to the section “To copy files to the
Discoverer Administration Tier” for more information.
5. Execute the following command from the command prompt:
start /wait for %%f in (*.dis) do
<ORACLE_HOM>\discvr31\dis31usr /connect
"<EUL_Owner>"/EUL_Owner_password>@<Connect_string>
/savedb %%f /batch
For example:
start /wait for %%f in (*dis) do
c:\orant\discvr31\dis31usr /connect
"SERVICES:Project Resource Management Super User:Standard”/welcome@apps
/savedb %%f /batch

Important: Use quotation marks when you enter the EUL_Owner

parameter in the command string.

12-10 Oracle Project Resource Management Implementation and Administration Guide

 Test Your Installation and Set Up

Alternatively, log in to the Discoverer User Edition and select File > Open > My
computer. Specify the location of the workbook file. After the workbook opens,
select File > Save As > Database to save the workbook in the database. You must
repeat this step for all workbooks.
Once the workbooks are saved in the database, change the EUL Owner (eul_us) End
User Layer (eul) password from the default password to a new, secure password.

Set Up Access to the Reporting Workbooks

The following steps instruct you on how to set up access to Discoverer workbooks
through the Discoverer User Edition.
1. Log in to the Discoverer User Edition in application mode, for example:
D:\orant\DISCVR31\DIS31USR.EXE

2. Open the workbook to which you need to grant other users/responsibilities

access.
3. Select File > Manage Workbooks > Sharing.
4. Select User > Workbook tab.
5. Select the user/responsibility to grant access.
6. Select the workbooks you need to grant access to and move them to the Shared
section of the Share workbook dialog box.

Test Your Installation and Set Up

Once you have finished installing the Oracle Project Resource Management
Reporting and performing all the postinstallation tasks, you want to verify that the
installation was successful. Check to see that you can access Discoverer Workbooks
by selecting any workbook from the Self-Service Applications menu.
If you have any problems, review the installation steps to ensure that you have
completed all of them correctly.

Setting Up for Reporting Capabilities 12-11

Overview of the Business Areas and Business Views

Overview of the Business Areas and Business Views

This section provides details on the Business Areas and Folders contained within
the Oracle Project Resource Management Discoverer reporting solution in the
following sections
■ List of Business Areas
■ List of Staffing Business Area Folders
■ List of Financial Business Area Folders
■ List of Competence Business Area Folders

List of Business Areas

The predefined business areas are:
■ Staffing
■ Financial
■ Competence

Staffing Business Area

The staffing business area provides general staffing information about resources,
projects, and organizations. From a supply perspective, you can identify
information regarding resource/organization capacity, availability,
over-commitment and overall schedule through these folders. From a demand
perspective, you can identify information regarding project/organization
requirements.
Folders available within the Staffing business area are:
■ Staffing Organization Rollup Groups
■ Resource Managers
■ Fiscal Years
■ Fiscal Quarter Numbers
■ Calendar Years
■ Calendar Months
■ Work Types
■ Required Project Hours by GL Period

12-12 Oracle Project Resource Management Implementation and Administration Guide

 Overview of the Business Areas and Business Views

■ Required Project Hours by GL Period: Team Role Detail

■ Required Project Hours by PA Period
■ Required Project Hours by PA Period: Team Role Detail
■ Required Project Hours by Global Week
■ Required Project Hours by Global Week: Team Role Detail
■ Resource Capacity by GL Period
■ Resource Capacity by PA Period
■ Resource Capacity by Global Week
■ Resource Schedule by GL Period
■ Resource Schedule by GL Period: Team Role Detail
■ Resource Schedule by PA Period
■ Resource Schedule by PA Period: Team Role Detail
■ Resource Schedule by Global Week
■ Resource Schedule by Global Week: Team Role Detail
■ Resource Schedule and Capacity by Global Week
■ Available Resource Hours by Global Week
■ Resource Overcommitment by Global Week

Note: The Team Role Detail folders are not used by the predefined
workbooks. They are extra folders provided for your convenience.

Reports by global week display the end date of the week. Therefore, if the global
week is defined to start on Monday, then the date for Sunday (the end of the week)
is used as the week label.
If you are generating a global week report for a specific month, the totals for the
weeks will only include the days for the specified month. For example, if the global
week is defined to start on Monday and the month of November 2001 begins on
Thursday, then the report will only include activity for Thursday through Sunday
for the first week of November.

Setting Up for Reporting Capabilities 12-13

Overview of the Business Areas and Business Views

Financial Business Area

The financial business area provides information about the project pipeline. Folders
available within the Financial business area are:
■ Lookup for Class Categories
■ Financial Organization Rollup Groups
■ Project Managers
■ Fiscal Years
■ Fiscal Quarter Numbers
■ Project Pipeline by GL Period
■ Project Pipeline by PA Period
■ Project Role Types
■ Project Members
Competence Business Area
The Competence business area provides information about the competence of the
resources. Folders available within the Competence business area are:
■ Organization Competence Summary
■ Resource Listing for Organization and Competence
■ Resource Competence Details
■ Organization Competence Details
■ Project Resource Competencies
■ Resource Projects
■ Competence Organization Rollup Groups
■ Competencies
■ Include Sub Organizations
■ Billable Job only
■ Resources
■ All Resource Managers
■ Jobs

12-14 Oracle Project Resource Management Implementation and Administration Guide

 Overview of the Business Areas and Business Views

■ Job Levels

List of Staffing Business Area Folders

This section provides descriptions for each of the folders within the Staffing
business area.

Staffing Organization Rollup Groups

This folder provides a simplified view of the reporting hierarchy (the hierarchy
specified as the default reporting hierarchy). The organizations are secured by
operating unit.
Although the hierarchy may be n level, this folder flattens the hierarchy out into
two levels. For example, if the original hierarchy is as follows:
Organization 1
Organization 2
Organization 4
Organization 3
Organization 5
it will be represented in this folder as follows:
Organization 1
Organization 2
Organization 3
Organization 4
Organization 5
This folder includes the items listed in the following table:

Item Description
Rollup Organization The name of the rollup organization
Suborganization The name of the suborganization

Setting Up for Reporting Capabilities 12-15

Overview of the Business Areas and Business Views

Resource Managers
This folder provides all of the managers of people over whom the user has
authority. In other words, a user can see all the managers that report to them
(directly and indirectly) and, if they have resource authority over an organization,
all the managers of people within that organization.
This folder includes the item listed in the following table:

Item Description
Resource Manager The full name of the resource manager

Fiscal Years
This folder provides the Fiscal Years in the format YYYY ranging from five Fiscal
Years in the past to five Fiscal Years in the future.
It includes the item listed in the following table:

Item Description
Fiscal Year The fiscal year

Fiscal Quarter Numbers

This folder provides the Fiscal Quarter numbers.
It includes the item listed in the following table:

Item Description
Fiscal Quarter The fiscal quarter

Calendar Years
This folder provides the calendar years in the format YYYY ranging from five years
in the past to five years in the future.
It includes the item listed in the following table:

Item Description
Calendar Year The calendar year

12-16 Oracle Project Resource Management Implementation and Administration Guide

 Overview of the Business Areas and Business Views

Calendar Months
This folder provides the calendar month name and number for the twelve months
of the year.
It includes the items listed in the following table:

Item Description
Calendar Month Name The name of the calendar month
Calendar Month The number of the calendar month
Numbers

Work Types
This folder provides information on work types used in the system.
It includes the items listed in the following table:

Item Description
Name User defined name of work type that uniquely identifies it.

Required Project Hours by GL Period

For each GL period, this folder contains the total number of hours that remain
unfilled on requirements within Project Resource Management. Hours scheduled in
a cancelled status are not included.
This folder includes the items listed in the following table:

Item Description
Fiscal Year The fiscal year
Fiscal Quarter The fiscal quarter
GL Period The GL Period for which the requirement hours are calculated
Project Manager The project manager as of the current date
Project Name (Number) The project of the requirement
Team Role The team role name of the requirement
Required Hours The total schedule, in hours, for the GL Period of the
requirement

Setting Up for Reporting Capabilities 12-17

Overview of the Business Areas and Business Views

Required Project Hours by GL Period: Team Role Detail

For each GL period, this folder contains the total number of hours that remain
unfilled on requirements within Project Resource Management. This folder contains
more detailed team role information. Hours scheduled in a cancelled status are not
included.
This folder includes the items listed in the following table:

Item Description
Fiscal Year The fiscal year
Fiscal Quarter The fiscal quarter
GL Period The GL Period for which the requirement hours are calculated
Project Manager The project manager as of the current date
Project Name (Number) The project of the requirement
Team Role The team role name of the requirement
Probability The probability of the project
Start Date The start date of the requirement
End Date The end date of the requirement
Minimum Job Level The minimum job level of the requirement
Maximum Job Level The maximum job level of the requirement
Required Hours The total schedule, in hours, for the GL Period of the
requirement

Required Project Hours by PA Period

For each PA period, this folder contains the total number of hours that remain
unfilled on requirements within Project Resource Management. Hours scheduled in
a cancelled status are not included.
This folder includes the items listed in the following table:

Item Description
Fiscal Year The fiscal year
Fiscal Quarter The fiscal quarter
PA Period The PA Period for which the requirement hours are calculated

12-18 Oracle Project Resource Management Implementation and Administration Guide

 Overview of the Business Areas and Business Views

Item Description
Project Manager The project manager as of the current date
Project Name (Number) The project of the requirement
Team Role The team role name of the requirement
Required Hours The total schedule, in hours, for the PA Period of the
requirement

Required Project Hours by PA Period: Team Role Detail

For each PA period, this folder contains the total number of hours that remain
unfilled on requirements within Project Resource Management. This folder contains
more detailed team role information. Hours scheduled in a cancelled status are not
included.
This folder includes the items listed in the following table:

Item Description
Fiscal Year The fiscal year
Fiscal Quarter The fiscal quarter
PA Period The PA Period for which the requirement hours are calculated
Project Manager The project manager as of the current date
Project Name (Number) The project of the requirement
Team Role The team role name of the requirement
Probability The probability of the project
Start Date The start date of the requirement
End Date The end date of the requirement
Minimum Job Level The minimum job level of the requirement
Maximum Job Level The maximum job level of the requirement
Required Hours The total schedule, in hours, for the GL Period of the
requirement

Setting Up for Reporting Capabilities 12-19

Overview of the Business Areas and Business Views

Required Project Hours by Global Week

For each Global Week, this folder contains the total number of hours that remain
unfilled on requirements within Project Resource Management. Hours scheduled in
a cancelled status are not included.
This folder includes the items listed in the following table:

Item Description
Calendar Year The calendar year
Calendar Month The calendar month
Global Week End Date The Global Week for which the hours of the requirement are
calculated (identified the end date of the requirement
Day of Week The name of the day for which the hours of the requirement are
calculated
Date The date for which the of the requirement are calculated
Project Manager The project manager as of the current date
Project Name (Number) The project of the requirement
Team Role The team role name of the requirement
Required Hours The total schedule, in hours, for the Global Week of the
requirement

Required Project Hours by Global Week: Team Role Detail

For each Global Week, this folder contains the total number of hours that remain
unfilled on requirements within Project Resource Management. This folder contains
more detailed team role information. Hours scheduled in a cancelled status are not
included.
This folder includes the items listed in the following table:

Item Description
Calendar Year The calendar year
Calendar Month The calendar month
Global Week End Date The Global Week for which the hours of the requirement are
calculated (identified the end date of the requirement
Day of Week The name of the day for which the hours of the requirement are
calculated

12-20 Oracle Project Resource Management Implementation and Administration Guide

 Overview of the Business Areas and Business Views

Item Description
Date The date for which the of the requirement are calculated
Project Manager The project manager as of the current date
Project Name (Number) The project of the requirement
Team Role The team role name of the requirement
Probability The probability of the project
Start Date The start date of the requirement
End Date The end date of the requirement
Minimum Job Level The minimum job level of the requirement
Maximum Job Level The maximum job level of the requirement
Required Hours The total schedule, in hours, for the Global Week of the
requirement

Resource Capacity by GL Period

For each GL period, this folder contains the total capacity, in hours, of each person.
The capacity of a person is derived from their capacity calendar assignments. It is
therefore calculated as, within each GL period, the number of potential working
hours attributable to the persons calendar work pattern minus any hours
attributable to public holidays.
The resource information in the folder is derived for the GL period specified.
This folder includes the items listed in the following table:

Item Description
Resource Manager The resource manager of the person
Resource The name of the person
Job Name The job title of the person
Job Level The job level of the person
Fiscal Year The fiscal year in which the GL Period exists
Fiscal Quarter The fiscal quarter in which the GL Period exists
GL Period The GL Period for which the hours of the person are calculated
Capacity Hours The capacity of the person, in hours, for the GL Period

Setting Up for Reporting Capabilities 12-21

Overview of the Business Areas and Business Views

Resource Capacity by PA Period

For each PA Period, this folder contains the total capacity, in hours, of each person.
A persons capacity is derived from their capacity calendar assignments. It is
therefore calculated as, within each PA Period, the number of potential working
hours attributable to the persons calendar work pattern minus any hours
attributable to public holidays.
The resource information in the folder is derived for the PA period specified.
This folder includes the items listed in the following table:

Item Description
Resource Manager The resource manager of the person
Resource The name of the person
Job Name The job title of the person
Job Level The job level of the person
Fiscal Year The fiscal year in which the PA Period exists
Fiscal Quarter The fiscal quarter in which the PA Period exists
PA Period The PA Period for which the hours of the person are calculated
Capacity Hours The capacity of the person, in hours, for the PA Period

Resource Capacity by Global Week

For each Global Week, this folder contains the total capacity, in hours, of each
person. A persons capacity is derived from their capacity calendar assignments. It is
therefore calculated as, within each Global Week, the number of potential working
hours attributable to the persons calendar work pattern minus any hours
attributable to public holidays.
The resource information in the folder is derived for the Global Week specified.
This folder includes the items listed in the following table:

Item Description
Resource Manager The resource manager of the person
Resource The name of the person
Job Name The job title of the person

12-22 Oracle Project Resource Management Implementation and Administration Guide

 Overview of the Business Areas and Business Views

Item Description
Job Level The job level of the person
Calendar Year The calendar year in which the Global Week exists
Calendar Month The calendar month in which the Global Week exists
Global Week End Date The Global Week for which the hours of the person are
calculated
Day of Week The name of the day for which the hours of the person are
calculated
Date The date for which the hours of the person are calculated
Capacity Hours The capacity of the person, in hours, for the Global Week

Resource Schedule by GL Period

For each GL period, this folder contains the total number of hours each person is
scheduled within Project Resource Management. No details of the actual
assignments on which the people are scheduled are available in this folder - the
lowest level of data is scheduled hours by person by GL period.
Hours scheduled on either delivery assignments and administrative assignments
are included in these totals. Hours scheduled in a provisional status and hours
scheduled in a confirmed status are totaled separately (hours scheduled in a
cancelled status are not included).
Data is only available for people who have a current and valid employment record
in Oracle Human Resources.
Historical data is available for either the previous two Fiscal Quarters or for the
whole of the current Fiscal Year (whichever provides more data).
Future data is available from the current date until the end of the forecasting
duration defined in the site level profile option PA: Availability Duration (the
default duration is two years).
This folder includes the items listed in the following table:

Item Description
GL Period The GL Period for which the assignment hours are calculated
Total Hours The total schedule hours of the person, including both
provisional and confirmed, for the GL Period

Setting Up for Reporting Capabilities 12-23

Overview of the Business Areas and Business Views

Item Description
Confirmed Hours The confirmed schedule hours of the person for the GL Period
Provisional Hours The provisional schedule hours of the person for the GL Period

Resource Schedule by GL Period: Team Role Detail

For each GL period, this folder contains the total number of hours each person is
scheduled on each of their assignments within Project Resource Management. To
view details of the actual assignments making up a persons schedule the user
should query this folder - the lowest level of data is scheduled hours by assignment
by GL period.
The scheduled hours of both delivery assignments and administrative assignments
can be viewed. Hours scheduled in a provisional status and hours scheduled in a
confirmed status are totaled separately (hours scheduled in a cancelled status are
not included).
Data is only available for people who have a current and valid employment record
in Oracle Human Resources.
Historical data is available for either the previous two Fiscal Quarters or for the
whole of the current Fiscal Year (whichever provides more data).
Future data is available from the current date until the end of the forecasting
duration defined in the site level profile option PA: Availability Duration (the
default duration is two years).
This folder includes the items listed in the following table:

Item Description
GL Period The GL Period for which the assignment hours are calculated
Project Name The project to which the assignment belongs
Project Manager The project manager as of the current date
Probability The probability of the project
Team Role The team role name of the assignment
Start Date The start date of the assignment
End Date The end date of the assignment
Total Hours The total schedule hours of the person, including both
provisional and confirmed, for the GL Period

12-24 Oracle Project Resource Management Implementation and Administration Guide

 Overview of the Business Areas and Business Views

Item Description
Confirmed Hours The confirmed schedule hours of the person for the GL Period
Provisional Hours The provisional schedule hours of the person for the GL Period
Assignment Work Type The work type of the assignment
Resource Name The name of the person
Project Type The project type of the project to which the assignment belongs
Project Number The project number to which the assignment belongs

Resource Schedule by PA Period

For each PA period, this folder contains the total number of hours each person is
scheduled within Project Resource Management. No details of the actual
assignments on which the people are scheduled are available in this folder - the
lowest level of data is scheduled hours by person by PA period.
Hours scheduled on either delivery assignments and administrative assignments
are included in these totals. Hours scheduled in a provisional status and hours
scheduled in a confirmed status are totaled separately (hours scheduled in a
cancelled status are not included).
Data is only available for people who have a current and valid employment record
in Oracle Human Resources.
Historical data is available for either the previous two Fiscal Quarters or for the
whole of the current Fiscal Year (whichever provides more data).
Future data is available from the current date until the end of the forecasting
duration defined in the site level profile option PA: Availability Duration (the
default duration is two years).
This folder includes the items listed in the following table:

Item Description
PA Period The GL Period for which the assignment hours are calculated
Total Hours The total schedule hours of the person, including both
provisional and confirmed, for the PA Period
Confirmed Hours The confirmed schedule hours of the person for the PA Period
Provisional Hours The provisional schedule hours of the person for the PA Period

Setting Up for Reporting Capabilities 12-25

Overview of the Business Areas and Business Views

Resource Schedule by PA Period: Team Role Detail

For each PA period, this folder contains the total number of hours each person is
scheduled on each of their assignments within Project Resource Management. To
view details of the actual assignments making up a persons schedule the user
should query this folder - the lowest level of data is scheduled hours by assignment
by PA period.
The scheduled hours of both delivery assignments and administrative assignments
can be viewed. Hours scheduled in a provisional status and hours scheduled in a
confirmed status are totaled separately (hours scheduled in a cancelled status are
not included).
Data is only available for people who have a current and valid employment record
in Oracle Human Resources.
Historical data is available for either the previous two Fiscal Quarters or for the
whole of the current Fiscal Year (whichever provides more data).
Future data is available from the current date until the end of the forecasting
duration defined in the site level profile option PA: Availability Duration (the
default duration is two years).
This folder includes the items listed in the following table:

Item Description
PA Period The PA Period for which the assignment hours are calculated
Project Name The project to which the assignment belongs
Project Manager The project manager as of the current date
Probability The probability of the project
Team Role The team role name of the assignment
Start Date The start date of the assignment
End Date The end date of the assignment
Total Hours The total schedule hours of the person, including both
provisional and confirmed, for the PA Period
Confirmed Hours The confirmed schedule hours of the person for the PA Period
Provisional Hours The provisional schedule hours of the person for the PA Period
Assignment Work Type The work type of the assignment

12-26 Oracle Project Resource Management Implementation and Administration Guide

 Overview of the Business Areas and Business Views

Item Description
PA Period Name The PA period name for which the assignment hours are
calculated
PA Period Start Date The PA Period start date
Resource Name The name of the person
Project Type The project type of the project to which the assignment belongs
Project Number The project number to which the assignment belongs

Resource Schedule by Global Week

For each Global Week, this folder contains the total number of hours each person is
scheduled within Project Resource Management. No details of the actual
assignments on which the people are scheduled are available in this folder - the
lowest level of data is scheduled hours by person by GL period.
Hours scheduled on either delivery assignments and administrative assignments
are included in these totals. Hours scheduled in a provisional status and hours
scheduled in a confirmed status are totaled separately (hours scheduled in a
cancelled status are not included).
Data is only available for people who have a current and valid employment record
in Oracle Human Resources.
Historical data is available for either the previous two Fiscal Quarters or for the
whole of the current Fiscal Year (whichever provides more data).
Future data is available from the current date until the end of the forecasting
duration defined in the site level profile option PA: Availability Duration (the
default duration is two years).
This folder includes the items listed in the following table:

Item Description
Calendar Year The calendar year in which the Global Week exists
Calendar Month The calendar month in which the Global Week exists
Global Week End Date The end date of the Global Week for which the hours of the
person are calculated
Global Week End Day The week day name of the end date of the Global Week
Date The date for which the hours of the person are calculated

Setting Up for Reporting Capabilities 12-27

Overview of the Business Areas and Business Views

Item Description
Total Hours The total schedule hours of the person, including both
provisional and confirmed, for the Global Week
Confirmed Hours The confirmed schedule hours of the person for the Global
Week
Provisional Hours The provisional schedule hours of the person for the Global
Week

Resource Schedule by Global Week: Team Role Detail

For each Global Week, this folder contains the total number of hours each person is
scheduled on each of their assignments within Project Resource Management. To
view details of the actual assignments making up a persons schedule the user
should query this folder - the lowest level of data is scheduled hours by assignment
by GL period.
The scheduled hours of both delivery assignments and administrative assignments
can be viewed. Hours scheduled in a provisional status and hours scheduled in a
confirmed status are totaled separately (hours scheduled in a cancelled status are
not included).
Data is only available for people who have a current and valid employment record
in Oracle Human Resources.
Historical data is available for either the previous two Fiscal Quarters or for the
whole of the current Fiscal Year (whichever provides more data).
Future data is available from the current date until the end of the forecasting
duration defined in the site level profile option PA: Availability Duration (the
default duration is two years).
This folder includes the items listed in the following table:

Item Description
Calendar Year The calendar year in which the Global Week exists
Calendar Month The calendar month in which the Global Week exists
Global Week End Date The end date of the Global Week for which the hours of the
person are calculated
Global Week End Day The week day name of the end date of the Global Week
Date The date for which the hours of the person are calculated

12-28 Oracle Project Resource Management Implementation and Administration Guide

 Overview of the Business Areas and Business Views

Item Description
Project Name The project to which the assignment belongs
Project Manager The project manager as of the current date
Probability The probability of the project
Team Role The team role name of the assignment
Start Date The start date of the assignment
End Date The end date of the assignment
Total Hours The total schedule hours of the person, including both
provisional and confirmed, for the Global Week
Confirmed Hours The confirmed schedule hours of the person for the Global
Week
Provisional Hours The provisional schedule hours of the person for the Global
Week
Assignment Work Type The work type of the assignment
Resource Name The name of the person
Project Type The project type of the project to which the assignment belongs
Project Number The project number to which the assignment belongs

Resource Schedule and Capacity by Global Week

For each Global Week, this folder contains the total number of hours each person is
scheduled within Project Resource Management.
The resource information in the folder is derived for the Global Week specified.
Hours scheduled on either delivery assignments or adminstrative assignments are
included in these totals. Hours scheduled in a provisional status and hours
scheduled in a confirmed status are available separately. Hours scheduled in a
cancelled status are not included.

Item Description
Resource Manager The resource manager of the person
Resource Name The name of the person
Job Name The job title of the person
Resource Job Level The job level of the person

Setting Up for Reporting Capabilities 12-29

Overview of the Business Areas and Business Views

Item Description
Year The fiscal year in which the Global week exists
Month The fiscal month in which the Global Week exists
Global Week End Date The end date of Global Week for which the scheduled hours of
the person are calculated
Day of Week The name of the day for which the scheduled hours of the
person are calculated
Date of Week The date of the week for which the scheduled hours of the day
are calculated
Total Hours The total schedule hours of the person, including both
provisional and confirmed, for the Global Week.
Confirmed Hours The confirmed schedule hours of the person for the Global
Week.
Provisional Hours The provisional scheduled hours of the person for the Global
Week.

Available Resource Hours by Global Week

For each Global Week, this folder contains the available hours, of each resource. A
persons capacity is derived from their calendar.
The resource information in the folder is derived for the Global Week specified.
This folder includes the items listed in the following table:

Item Description
Resource Manager The resource manager of the person
Resource Name The name of the person
Job Name The job title of the person
Resource Job Level The global job level of the person
Year The fiscal year in which the Global week exists
Month The fiscal month in which the Global Week exists
Global Week End Date The end date of Global Week for which the available hours of the
person are calculated
Day of Week The name of the day for which the available hours of the person
are calculated

12-30 Oracle Project Resource Management Implementation and Administration Guide

 Overview of the Business Areas and Business Views

Item Description
Date of Week The date of the week for which the available hours of the day are
calculated
Capacity Hours The capacity of the person, in hours, for the Global Week.
Definite Available Hours The definite available hours for the person, in hours, for the
Global Week. It is equal to Capacity Hours - Confirmed Hours.
Provisional Hours The provisional scheduled hours of the person for the Global
Week.

Resource Overcommitment by Global Week

This folder provides overcommited resources information.The resource information
in the folder is derived for the Global Week specified.
This folder includes the items listed in the following table:

Item Description
Resource Manager The resource manager of the person
Resource Name The name of the person
Job Name The job title of the person
Resource Job Level The job level of the person
Year The fiscal year in which the Global week exists
Month The fiscal month in which the Global Week exists
Global Week End Date The end date of Global Week for which the overcommitted
hours of the person are calculated
Day of Week The name of the day for which the overcommitted hours of the
person are calculated
Date of Week The date of the week for which the overcommitted hours of the
day are calculated
Capacity Hours The capacity of the person, in hours, for the Global Week.
Overcommited Hours The overcommited hours of the person for the Global Week
Confirmed Hours The confirmed schedule hours of the resource for the Global
Week

Setting Up for Reporting Capabilities 12-31

Overview of the Business Areas and Business Views

List of Financial Business Area Folders

This section provides descriptions for each of the folders within the Financial
business area.

Financial Organization Rollup Groups

Shows a simplified view of the reporting hierarchy (the hierarchy specified as the
default reporting hierarchy). The organizations are secured by operating unit and
forecasting authority.
Although the hierarchy may be n level, this folder flattens the hierarchy out into just
two levels. For example, if the original hierarchy is as follows:
Organization 1
Organization 2
Organization 4
Organization 3
Organization 5
and the user does not have forecasting authority over organization 2 or 5, this folder
will represent the following:
Organization 1
Organization 3
Organization 4
This folder includes the items listed in the following table:

Item Description
Rollup Organization The name of the rollup organization
Suborganization The name of the suborganization

Project Managers
This folder provides all people who have or have had the role of a project manager.
It includes the item listed in the following table:

Item Description
Project Manager The full name of the project manager

12-32 Oracle Project Resource Management Implementation and Administration Guide

 Overview of the Business Areas and Business Views

Fiscal Years
This folder provides the Fiscal Years in the format YYYY ranging from five Fiscal
Years in the past to five Fiscal Years in the future. It includes the item listed in the
following table:

Item Description
Fiscal Year The fiscal year

Fiscal Quarter Numbers

This folder provides the Fiscal Quarter numbers. It includes the item listed in the
following table:

Item Description
Fiscal Quarter Number The number of the fiscal quarter

Project Role Types

This folder provides the list of all Project Role Types.

Item Description
Project Role Type The name of the role on the project

Project Members
This folder provides a list of all resources that have a role on a project.

Item Description
Project Name The project name on which the resource (project member) is
assigned
Member Name The name of the project member

Sales Pipeline by GL Period

For each GL Period, this folder lists projects that are expecting approval and the
values associated with them. Both total project value and discounted amount (total
project value times project probability) are given.

Setting Up for Reporting Capabilities 12-33

Overview of the Business Areas and Business Views

Only projects with a status of unapproved or submitted and a probability of less

than 100 are included in this folder.
This folder lists projects by classification category. Therefore, if a project is classified
in two categories, it will appear twice in this folder. Therefore, to avoid double
counting project values, it is recommended that queries on this folder should be
performed for one classification category at a time.
Historical data is available for either the previous two Fiscal Quarters or for the
whole of the current Fiscal Year (whichever provides more data).
Future data is available from the current date until the end of the forecasting
duration defined in the site level profile option PA: Availability Duration (the
default duration is two years).
This folder includes the items listed in the following table:

Item Description
Classification Category The category by which the project is classified
Classification Code The code by which the project is classified
Project The name of the project
Class Code Percentage Percentage value of a classification code
Project Role Type The name of a role on a project
Probability The probability of the project
Type The type of the project
Status The status of the project
Expected Approval Date The expected approval date of the project
Fiscal Year The Fiscal Year in which the GL Period exists
Fiscal Quarter The Fiscal Quarter in which the GL Period exists
GL Period The GL Period in which the project is expecting approval
Total Project Value The total value of the project
Discounted Amount The total project value multiplied by the probability of the
project
Project Number The number of the project

12-34 Oracle Project Resource Management Implementation and Administration Guide

 Overview of the Business Areas and Business Views

Sales Pipeline by PA Period

For each PA Period, this folder lists projects that are expecting approval and the
values associated with them. Both total project value and discounted amount (total
project value times project probability) are given.
Only projects with a status of unapproved or submitted and a probability of less
than 100 are included in this folder.
This folder lists projects by classification category. Therefore, if a project is classified
in two categories, it will appear twice in this folder. Therefore, to avoid double
counting project values, it is recommended that queries on this folder should be
performed for one classification category at a time.
Historical data is available for either the previous two Fiscal Quarters or for the
whole of the current Fiscal Year (whichever provides more data).
Future data is available from the current date until the end of the forecasting
duration defined in the site level profile option PA: Availability Duration (the
default duration is two years).
This folder includes the items listed in the following table:

Item Description
Classification Category The category by which the project is classified
Classification Code The code by which the project is classified
Project The name of the project
Class Code Percentage Percentage value of a classification code
Project Role Type The name of a role on a project
Probability The probability of the project
Type The type of the project
Status The status of the project
Expected Approval Date The expected approval date of the project
Fiscal Year The Fiscal Year in which the PA Period exists
Fiscal Quarter The Fiscal Quarter in which the PA Period exists
PA Period The PA Period in which the project is expecting approval
Total Project Value The total value of the project

Setting Up for Reporting Capabilities 12-35

Overview of the Business Areas and Business Views

Item Description
Discounted Amount The total project value multiplied by the probability of the
project
Project Number The number of the project

Lookup for Class Categories

This folder provides all class categories currently available within the system. It
includes the item listed in the following table:

Item Description
Classification Category The name of the classification category

List of Competence Business Area Folders

This section provides descriptions for each of the folders within the Competence
business area.

Organization Competence Summary

This folder provides summary of competencies and number of resources per
organization that have a particular competence.
It includes the items listed in the following table:

Item Description
Organization Name The name of the organization
Competence Name The name of the competence
Competence Alias The short name of the competence
Competence Description The description of the competence
Resource Count The number of resources who have the competence.
View Resources The link to view list of resources
Business Group The business group name of the competence
Segment 1-30 Key FlexField segments of the competence

12-36 Oracle Project Resource Management Implementation and Administration Guide

 Overview of the Business Areas and Business Views

Resource Listing for Organization and Competence

This folder provides detail of the people per organization and their competence
profile.
It includes the items listed in the following table.

Item Description
Organization Name The name of the organization
Competence Name The name of the competence
Person Name The name of the resource
Proficiency Level The proficiency level of the competence
Manager Name The manager of the resource
Job Name The job name of the resource
Project Job Level The job level of the resource
Project Job Code The job code of the resource
Location The primary location of the resource
View Competence Details The link to view competence profile of the resource

Resource Competence Details

This folder provides detailed competence information of a resource.
It includes the items listed in the following table.

Item Description
Resource Name The name of the person
Competence Name The name of the competence of the resource
Competence Alias The short name of the competence
Business Group Name The business group name of the competence
Proficiency Level The proficiency level of the competence
Last Updated Date The last date the competence was updated
Segment 1- 30 Key Flexfield segments of the competence

Setting Up for Reporting Capabilities 12-37

Overview of the Business Areas and Business Views

Organization Resource Competencies

This folder provides competence information about all resources for an
organization.
It includes the items listed in the following table.

Item Description
Organization Name The name of the organization
Resource Name the name of the person
Resource Competencies A listing of all the competence aliases of the resource, prefixed
by the proficiency level of the competence. If the competence
does not have a alias the the competence name is used.
Resource Competence The number of competencies of the resource
Count
Last Updated The last date the competence profile was updated. This is the
latest date when any one of the resource competence was
updated.
Manager Name The name of the manager of the resource
Job Name The job name of the resource
Job Level The job level of the resource
Job Code The job code of the resource
View Competence The link to view competence profile of the resource
Details
Billable Flag The flag indicating if the job of the resource is billable

Project Resource Competencies

This folder provides information about all resources for a project, and their
competencies and proficiency levels.
It includes the items listed in the following table.

Item Description
Project Name The name of the project that has the resource assignment
Project Number The project number of the project that has the resource
assignment
Resource Name The name of the person

12-38 Oracle Project Resource Management Implementation and Administration Guide

 Overview of the Business Areas and Business Views

Item Description
Resource Competencies A listing of all the competence alias of the resource, prefixed by
the proficiency level of the competence. If the competence does
not have a alias the the competence name is used.
Resource Competence The number of competencies of the resource
Count
Last Updated The last date the competence profile was updated. This is the
latest date when any one of the resource competence was
updated.
Manager Name The name of the manager of the resource
Job Name The job name of the resource
Job Level The job level of the resource
Job Code The job code of the resource
View Competence The link to view competence profile of the resource
Details
Billable Flag The flag indicating if the job of the resource is billable

Resource Projects
This folder provides information about all projects that have a resource assigned to
it.
It includes the items listed in the following table.

Item Description
Id System Identification number of the project
Name Number The project name and project number that has resource
assignment
Name The name of the project
Number The number of the project

Competence Organization Rollup Groups

This folder provides information about all organizations in the reporting
organization hierarchy.

Setting Up for Reporting Capabilities 12-39

Overview of the Business Areas and Business Views

It includes the items listed in the following table.

Item Description
Parent Organization Name The name of the parent organization
Child Organization Name The name of the child organization
Include Sub Organization Yes/No: Select whether to include sub-organizations of the
selected organization in the result.

Competencies
This folder provides information about all competence names.
It includes the items listed in the following fields.

item Description
Competence Name The name of the competence

Include Sub Organizations

The folder provides information whether to include or exclude sub organization.
It includes the items listed in the following table.

Item Description
Meaning Yes/No: Used for selecting the sub organization in the list of
values

Billable Job Only

The folder provides information whether the job is a billable job or not.
It includes the items listed in the following table.

Item Description
Meaning Yes/No: Used for selecting whether the job is billable or not.

Resources
The folder shows information about all current and future resources with their
resource manager.

12-40 Oracle Project Resource Management Implementation and Administration Guide

 Overview of the Business Areas and Business Views

It includes the items listed in the following table.

Item Description
Resource Name The name of the person

All Resource Managers

The folder shows information about all current and future resource managers.
It includes the items listed in the following table.

Item Description
Name The name of the resource manager

Jobs
The folder shows information about all job names across business groups.
It includes the items listed in the following table.

Item Description
Name The name of the job

Job Levels
The folder shows information about all job levels across business groups.
It includes the items listed in the following table.

Item Description
Name The name of the job level

Setting Up for Reporting Capabilities 12-41

Overview of the Business Areas and Business Views

List of Business Views

Each folder within the EUL maps to a business view on the database. If you need
direct access to these views, the following table provides view and folder mapping:

View Name Folder Name

pa_rep_proj_reQhrs_gl_v Required Project Hours by GL Period
pa_rep_proj_reQhrs_gld_v Required Project Hours by GL Period: Team Role Detail
pa_rep_proj_reQhrs_pa_v Required Project Hours by PA Period
pa_rep_proj_reQhrs_pad_v Required Project Hours by PA Period: Team Role Detail
pa_rep_proj_reQhrs_wk_v Required Project Hours by Global Week
pa_rep_proj_reQhrs_wkd_v Required Project Hours by Global Week: Team Role Detail
pa_rep_res_cap_gl_v Resource Capacity by GL Period
pa_rep_res_cap_pa_v Resource Capacity by PA Period
pa_rep_res_cap_wkd_v Resource Capacity by Global Week
pa_rep_res_schhrs_gl_v Resource Schedule by GL Period
pa_rep_res_schhrs_gld_v Resource Schedule by GL Period: Team Role Detail
pa_rep_res_schhrs_pa_v Resource Schedule by PA Period
pa_rep_res_schhrs_pad_v Resource Schedule by PA Period: Team Role Detail
pa_rep__res_schhrs_wk_v Resource Schedule by Global Week
pa_rep_res_schhrs_wkd_v Resource Schedule by Global Week: Team Role Detail
pa_rep_proj_sp_gl_v Project Pipeline by GL Period
pa_rep_proj_sp_pa_v Project Pipeline by PA Period
pa_rep_all_rep_org_v Staffing Organization Rollup Groups
pa_rep_forecast_org_v Financial Organization Rollup Groups
pa_proj_manager_v Project Managers
pa_rep_all_mgr_v Resource Managers
pa_rep_year_gl_v Fiscal Years
pa_rep_quarter_gl_v Fiscal Quarter Numbers
pa_rep_year_cal_v Calendar Years
pa_rep_month_v Calendar Months

12-42 Oracle Project Resource Management Implementation and Administration Guide

 Overview of the Business Areas and Business Views

View Name Folder Name

pa_rep_proj_sp_cc_v Lookup for Class Categories
pa_rep_org_comp_sum_v Organization Competence Summary
pa_rep_org_comp_res_lst_v Resource Listing for Organization and Competence
pa_rep_res_comp_dts_v Resource Competence Details
pa_rep_org_res_comp_v Organization Resource Competencies
pa_rep_proj_res_comp_v Project Resource Competencies
pa_rep_res_projects_v Resource Projects
pa_rep_comp_rep_org_v Competence Organization Rollup Groups
pa_rep_all_comp_v Competencies
pa_rep_yes_no_v Include Sub-Organizations
pa_rep_resources_v Resources
pa_rep_managers_v All Resource Managers
pa_rep_all_jobs_v Jobs
pa_setup_job_levels_v Job Levels
pa_rep_proj_sts_v Project Statuses
pa_project_role_types_vl Project Role Types
pa_proj_members_view Project Members
pa_rep_res_cap_wkd_v Resource Schedule and Capacity by Global Week
pa_rep_res_ovc_wk_v Resource Overcommitment by Global Week
pa_rep_res_avl_wk_v Available Resource Hours by Global Week
pa_work_types_vl Work Types
pa_rep_proj_sp_gl_v Sales Pipeline by GL Period
pa_rep_proj_sp_pa_v Sales Pipeline by PA Period

Setting Up for Reporting Capabilities 12-43

Security Overview

Security Overview
Security is handled using the standard Oracle Applications security model meaning
that security is tied to the Applications responsibility that the user selects at login.
The user can then only view data and run reports as designated by the profile
options, reports, menus, and organizations the responsibility has assigned to it.

Organization Security
A user will only be able to run financial workbooks for organizations that they have
forecast authority over.

Resource Manager Security

A user will only be able to run staffing workbooks for resource managers that either
report to them or manage people that they have resource authority over.

Discoverer Workbooks
This chapter contains descriptive information for the following predefined
Discoverer workbooks included in the Project Resource Management reporting
solution:
■ Required Project Hours (PAREQPRJ)
■ Scheduled Resource Hours (PASCHRES)
■ Available Resource Hours (PAAVLRES)
■ Overcommitted Resource Hours (PAOVCRES)
■ Project Pipeline Workbook (PASALPIP)
■ Organization Competence Summary Workbook (PA_PRM_ORG_COMP_SUM)
■ Resource Competencies Workbook (PA_PRM_RES_COMP)

Note: The first five workbooks can be run on both Discoverer 3i

and 4i. The last two workbooks can be run only on Discoverer 4i.

12-44 Oracle Project Resource Management Implementation and Administration Guide

 Discoverer Workbooks

You may find references to the following Discoverer features:

■ Null Data Display
Discoverer displays a blank in a dropdown selection box when the field on
which the selection is made contains null values. To select a null value, click on
the blank in the same way that you select other, non-null values.
■ Optional Parameters
As is noted below, worksheet parameters can be switched on or off by the user
at runtime. For example, to run a report that has a resource manager parameter
for all resource managers, the resource manager parameter can be switched off.

Note: While using such parameters is common practice, you

should note that your system may experience a decrease in
performance when certain parameters are removed from a
worksheet.

Global Week Reports

Reports by global week display the end date of the week. Therefore, if the global
week is defined to start on Monday, then the date for Sunday (the end of the week)
is used as the week label.
If you are generating a global week report for a specific month, the totals for the
weeks will only include the days for the specified month. For example, if the global
week is defined to start on Monday and the month of November 2001 begins on
Thursday, then the report will only include activity for Thursday through Sunday
for the first week of November.

Required Project Hours (PAREQPRJ)

The required project hours workbook allows you to evaluate the number of hours
currently required within Project Resource Management by project. You can view
this information by Organization and Project Manager.
Worksheets included in this workbook are:
■ Required Project Hours by GL Period
■ Required Project Hours by PA Period
■ Required Project Hours by Global Week

Setting Up for Reporting Capabilities 12-45

Discoverer Workbooks

Security
When selecting an organization, the user will be restricted to those within the
reporting hierarchy of the operating unit associated with their responsibility.
When selecting a project manager, the user will be restricted to people who are
currently managing projects within Project Resource Management.

Required Project Hours by GL Period

Some of the business questions answered by this worksheet are:
■ What is the total number of hours of work that I need to find resources to fill in
my organization by GL period?
■ What does the spread of required hours per GL period look like over time?
■ What does the spread of required hours per GL period look like over
organizations?
The Required Project Hours by GL Period worksheet helps you answer these
questions by letting you analyze and manipulate scheduling information by
Organization and Project Manager. Additionally, you can roll the data up to Fiscal
Quarter and year.

Parameter Page
Parameters are predefined conditions that you can leave on or switch off by
selecting the Conditions dialogue under the Tools menu.
■ Organization - You can choose only one organization but the worksheet will
then run for the organization chosen and any below it in the reporting
hierarchy.
■ Project Manager - You can choose one or more Project Managers for whom you
want to view data.
■ Fiscal Year - You can choose only one year.
■ Fiscal Quarter Number - You can choose only one quarter number for the year
you have specified.

Conditions
Conditions are filters in the worksheet that you can turn on or off.
There are no conditions (other than those defined for the parameters listed above)
predefined on this worksheet.

12-46 Oracle Project Resource Management Implementation and Administration Guide

 Discoverer Workbooks

Column Dimensions
■ Fiscal Year - the name of a Fiscal Year
■ Fiscal Quarter - the name of a Fiscal Quarter
■ GL Period - the name of a GL period
■ Required Hours - number of hours required

Row Dimensions
■ Organization - the name of an organization.
■ Project - the name of a project.
■ Team Role - the team role name of the requirement.

Additional Information
If the worksheet returns a value that requires further investigation the user should
create a more detailed worksheet based on the folder Required Project Hours by GL
Period: Team Role Detail. Using this folder more detailed information about the
requirement can be found. The data you can view includes:
■ Probability - the probability of the project.
■ Start Date - the start date of the assignment.
■ End Date - the end date of the assignment.
■ Minimum Job Level - the minimum job level of the requirement.
■ Maximum Job Level - the maximum job level of the requirement.

Required Project Hours by PA Period

Some of the business questions answered by this worksheet are:
■ What is the total number of hours of work that I need to find resources to fill in
my organization by PA period?
■ What does the spread of required hours per PA period look like over time?
■ What does the spread of required hours per PA period look like over
organizations?
The Required Project Hours by PA Period worksheet helps you answer these
questions by letting you analyze and manipulate scheduling information by

Setting Up for Reporting Capabilities 12-47

Discoverer Workbooks

Organization and Project Manager. Additionally, you can roll the data up to Fiscal
Quarter and year.

Parameter Page
Parameters are predefined conditions that you can leave on or switch off by
selecting the Conditions dialogue under the Tools menu.
■ Organization - You can choose only one organization but the worksheet will
then run for the organization chosen and any below it in the reporting
hierarchy.
■ Project Manager - You can choose one or more Project Managers for whom you
want to view data.
■ Fiscal Year - You can choose only one year.
■ Fiscal Quarter Number - You can choose only one quarter number for the year
you have specified.

Conditions
Conditions are filters in the worksheet that you can turn on or off.
There are no conditions (other than those defined for the parameters listed above)
predefined on this worksheet.

Column Dimensions
■ Fiscal Year - the name of a Fiscal Year
■ Fiscal Quarter - the name of a Fiscal Quarter
■ PA Period - the name of a PA period
■ Required Hours - number of hours required

Row Dimensions
■ Organization - the name of an organization.
■ Project - the name of a project.
■ Team Role - the team role name of the requirement.

Additional Information
If the worksheet returns a value that requires further investigation the user should
create a more detailed worksheet based on the folder Required Project Hours by PA

12-48 Oracle Project Resource Management Implementation and Administration Guide

 Discoverer Workbooks

Period: Team Role Detail. Using this folder more detailed information about the
requirement can be found. The data you can view includes:
■ Probability - the probability of the project.
■ Start Date - the start date of the assignment.
■ End Date - the end date of the assignment.
■ Minimum Job Level - the minimum job level of the requirement.
■ Maximum Job Level - the maximum job level of the requirement.

Required Project Hours by Global Week

Some of the business questions answered by this worksheet are:
■ What is the total number of hours of work that I need to find resources to fill in
my organization by Global Week?
■ What does the spread of required hours per Global Week look like over time?
■ What does the spread of required hours per Global Week period look like over
organizations?
The Required Project Hours by Global Week worksheet helps you answer these
questions by letting you analyze and manipulate scheduling information by
Organization and Project Manager.

Parameter Page
Parameters are predefined conditions that you can leave on or switch off by
selecting the Conditions dialogue under the Tools menu.
■ Organization - You can choose only one organization but the worksheet will
then run for the organization chosen and any below it in the reporting
hierarchy.
■ Project Manager - You can choose one or more Project Managers for whom you
want to view data.
■ Calendar Year - You can choose only one year.
■ Calendar Month - You can choose only one calendar month for the year you
have specified.

Setting Up for Reporting Capabilities 12-49

Discoverer Workbooks

Conditions
Conditions are filters in the worksheet that you can turn on or off. There are no
conditions (other than those defined for the parameters listed above) predefined on
this worksheet.

Column Dimensions
■ Calendar Year - the name of a calendar year
■ Calendar Month - the name of a calendar month
■ Global Week - the name of a global week
■ Day - the name of a day
■ Required Hours - number of hours required

Row Dimensions
■ Organization - the name of an organization.
■ Project - the name of a project.
■ Team Role - the team role name of the requirement.

Additional Information
If the worksheet returns a value that requires further investigation the user should
create a more detailed worksheet based on the folder Required Project Hours by
Global Week: Team Role Detail. Using this folder, you can find more detailed
information about the requirement. The data you can view includes:
■ Probability - the probability of the project.
■ Start Date - the start date of the assignment.
■ End Date - the end date of the assignment.
■ Minimum Job Level - the minimum job level of the requirement.
■ Maximum Job Level - the maximum job level of the requirement.

12-50 Oracle Project Resource Management Implementation and Administration Guide

 Discoverer Workbooks

Scheduled Resource Hours (PASCHRES)

The scheduled resource hours workbook allows you to evaluate the number of
hours currently scheduled within Project Resource Management by person. You can
view this information by Organization and Resource Manager.
Worksheets included in this workbook are:
■ Scheduled Resource Hours by GL Period
■ Scheduled Resource Hours by PA Period
■ Scheduled Resource Hours by Global Week

Restrictions
■ When selecting an organization, the user is restricted to those within the
reporting hierarchy of the operating unit associated with their responsibility.
■ When selecting a resource manager, the user is restricted to those individuals
that report to them or manage people they have resource authority over.

Scheduled Resource Hours by GL Period

This worksheet addresses business questions such as:
■ What is the total number of hours scheduled for the people in my organization
per GL period?
■ What are the total number of hours scheduled for individuals in my
organization per GL period?
■ What does the spread of scheduled hours per GL period look like over time?
■ If there is an issue with a persons scheduled hours, what projects are they
assigned to?
The Scheduled Resource Hours by GL Period worksheet helps you answer these
questions by letting you analyze and manipulate scheduling information by
Organization, Resource Manager and Person. Additionally, you can roll the data up
to Fiscal Quarter and year.

Parameter Page
Parameters are predefined conditions that you can leave on or switch off by
selecting the Conditions dialogue under the Tools menu.

Setting Up for Reporting Capabilities 12-51

Discoverer Workbooks

■ Organization - You can choose only one organization but the worksheet will
then run for the organization chosen and any below it in the reporting
hierarchy.
■ Resource Manager - You can choose one or more Resource Managers for whom
you want to view data.
■ Fiscal Year - You can choose only one year.
■ Fiscal Quarter Number - You can choose only one quarter number for the year
you have specified.

Conditions
Conditions are filters in the worksheet that you can turn on or off.
There are no conditions (other than those defined for the parameters listed above)
predefined on this worksheet.

Column Dimensions
■ Fiscal Year - the name of a Fiscal Year
■ Fiscal Quarter - the name of a Fiscal Quarter
■ GL Period - the name of a GL period
■ Capacity Hours - number of hours available to work
■ Total Hours - number of hours scheduled in either a provisional or confirmed
status for all work types.
■ Provisional Hours - number of hours scheduled in a provisional status

Row Dimensions
■ Organization - the name of an organization.
■ Resource Manager - the name of a resource manager.
■ Person - the name of a person.
■ Job Name - the title of the job of the person.
■ Job Level - the global job level of the person.

12-52 Oracle Project Resource Management Implementation and Administration Guide

 Discoverer Workbooks

Additional Information
The following table lists items that can be added to the Scheduled Resource Hours
by GL Period worksheet:

Business Area Folder Item

Staffing Resource Schedule by GL Confirmed Hours
Period

Suggestion: A useful addition to this worksheet is a user-defined

exception highlighting people whose percentage overcommitment
is over a certain threshold.

It is common practice for the cells of data points meeting the exception criteria to be
shown in red.
If the worksheet returns a value that requires further investigation, you should
create a more detailed worksheet based on the folder Resource Schedule by GL
Period: Team Role Detail. Using this folder, the actual assignments on which a given
person is scheduled can be examined and manipulated. the data you can view
includes:
■ Project - the name of a project
■ Project Manager - the name of the current project manager
■ Probability - the probability of the project
■ Team Role - the team role name of the assignment
■ Start Date - the start date of the assignment
■ End Date - the end date of the assignment
■ Capacity Hours - number of hours available to work
■ Total Hours - number of hours scheduled in either a provisional or confirmed
status
■ Provisional Hours - number of hours scheduled in a provisional status

Setting Up for Reporting Capabilities 12-53

Discoverer Workbooks

Scheduled Resource Hours by PA Period

This worksheet addresses business questions such as:
■ What is the total number of hours scheduled for the people in my organization
per PA period?
■ What are the total number of hours scheduled for individuals in my
organization per PA period?
■ What does the spread of scheduled hours per PA period look like over time?
■ If there is an issue with a persons scheduled hours, what projects are they
assigned to?
The Scheduled Resource Hours by PA Period worksheet helps you answer these
questions by letting you analyze and manipulate scheduling information by
Organization, Resource Manager and Person. Additionally, you can roll the data up
to Fiscal Quarter and year.

Parameter Page
Parameters are predefined conditions that you can leave on or switch off by
selecting the Conditions dialogue under the Tools menu.
■ Organization - You can choose only one organization but the worksheet will
then run for the organization chosen and any below it in the reporting
hierarchy.
■ Resource Manager - You can choose one or more Resource Managers for whom
you want to view data.
■ Fiscal Year - You can choose only one year.
■ Fiscal Quarter Number - You can choose only one quarter number for the year
you have specified.

Conditions
Conditions are filters in the worksheet that you can turn on or off.
There are no conditions (other than those defined for the parameters listed above)
predefined on this worksheet.

Column Dimensions
■ Fiscal Year - the name of a Fiscal Year
■ Fiscal Quarter - the name of a Fiscal Quarter

12-54 Oracle Project Resource Management Implementation and Administration Guide

 Discoverer Workbooks

■ PA Period - the name of a PA period

■ Capacity Hours - number of hours available to work
■ Total Hours - number of hours scheduled in either a provisional or confirmed
status for all work types.
■ Provisional Hours - number of hours scheduled in a provisional status

Row Dimensions
■ Organization - the name of an organization.
■ Resource Manager - the name of a resource manager.
■ Person - the name of a person.
■ Job Name - the title of the job of the person.
■ Job Level - the global job level of the person.

Additional Information
The following table lists items that can be added to the Scheduled Resource Hours
by PA Period worksheet:

Business Area Folder Item

Staffing Resource Schedule by PA Confirmed Hours
Period

Suggestion: A useful addition to this worksheet is a user-defined

exception highlighting people whose percentage over-commitment
is over a certain threshold.

It is common practice for the cells of data points meeting the exception criteria to be
shown in red.
If the worksheet returns a value that requires further investigation, you should
create a more detailed worksheet based on the folder Resource Schedule by PA
Period: Team Role Detail. Using this folder, the actual assignments on which a given
person is scheduled can be examined and manipulated. The data you can view
includes:
■ Project - the name of a project.

Setting Up for Reporting Capabilities 12-55

Discoverer Workbooks

■ Project Manager - the name of the current project manager.

■ Probability - the probability of the project.
■ Team Role - the team role name of the assignment.
■ Start Date - the start date of the assignment.
■ End Date - the end date of the assignment.
■ Capacity Hours - number of hours available to work
■ Total Hours - number of hours scheduled in either a provisional or confirmed
status
■ Provisional Hours - number of hours scheduled in a provisional status

Scheduled Resource Hours by Global Week

This worksheet addresses business questions such as:
■ What is the total number of hours scheduled for the people in my organization
per Global Week?
■ What are the total number of hours scheduled for individuals in my
organization per Global Week?
■ What does the spread of scheduled hours per Global Week look like over time?
■ If there is an issue with a persons scheduled hours, what projects are they
assigned to?
The Scheduled Resource Hours by Global Week worksheet helps you answer these
questions by letting you analyze and manipulate scheduling information by
Organization, Resource Manager and Person. Additionally, you can drill down to
view the data by day (to view the hours per day).

Parameter Page
Parameters are predefined conditions that you can leave on or switch off by
selecting the Conditions dialogue under the Tools menu.
■ Organization - You can choose only one organization but the worksheet will
then run for the organization chosen and any below it in the reporting
hierarchy.
■ Resource Manager - You can choose one or more Resource Managers for whom
you want to view data.
■ Calendar Year - You can choose only one year.

12-56 Oracle Project Resource Management Implementation and Administration Guide

 Discoverer Workbooks

■ Calendar Month - You can choose only one calendar month for the year you
have specified.

Conditions
Conditions are filters in the worksheet that you can turn on or off.
There are no conditions (other than those defined for the parameters listed above)
predefined on this worksheet.

Column Dimensions
■ Calendar Year - the name of a calendar year
■ Calendar Month - the name of a calendar month
■ Global Week - the name of a global week
■ Day - the name of a day
■ Capacity Hours - number of hours available to work
■ Total Hours - number of hours scheduled in either a provisional or confirmed
status for all work types.
■ Provisional Hours - number of hours scheduled in a provisional status

Row Dimensions
■ Organization - the name of an organization.
■ Resource Manager - the name of a resource manager.
■ Person - the name of a person.
■ Job Name - the title of the job of the person.
■ Job Level - the global job level of the person.

Additional Information
The following table lists items that can be added to the Scheduled Resource Hours
by Global Week worksheet:

Business Area Folder Item

Staffing Resource Schedule and Confirmed Hours
Capacity by Global Week

Setting Up for Reporting Capabilities 12-57

Discoverer Workbooks

Suggestion: A useful addition to this worksheet is a user-defined

exception highlighting people whose percentage overcommitment
is over a certain threshold.

It is common practice for the cells of data points meeting the exception criteria to be
shown in red.
If the worksheet returns a value that requires further investigation, you should
create a more detailed worksheet based on the folder Resource Schedule by Global
Week: Team Role Detail. Using this folder, the actual assignments on which a given
person is scheduled can be examined and manipulated. The data you can view
includes:
■ Project - the name of a project
■ Project Manager - the name of the current project manager
■ Probability - the probability of the project
■ Team Role - the team role name of the assignment
■ Start Date - the start date of the assignment
■ End Date - the end date of the assignment
■ Capacity Hours - number of hours available to work
■ Total Hours - number of hours scheduled in either a provisional or confirmed
status for all work types.
■ Provisional Hours - number of hours scheduled in a provisional status

Available Resource Hours (PAAVLRES)

The Available Resource Hours workbook allows you to evaluate the number of
capacity hours that are currently not scheduled within Project Resource
Management. You can view this information by Organization and/or Resource
Manager.
Worksheets included in this workbook are:
■ Available Resource Hours by GL Period
■ Available Resource Hours by PA Period
■ Available Resource Hours by Global Week

12-58 Oracle Project Resource Management Implementation and Administration Guide

 Discoverer Workbooks

Restrictions
■ When selecting an organization, the user will be restricted to those within the
reporting hierarchy of the operating unit associated with their responsibility.
■ When selecting a resource manager, the user will be restricted to those that
report to them or manage people they have resource authority over.

Available Resource Hours by GL Period

This worksheet addresses business questions such as:
■ What is the total number of hours, per GL period, that people in my
organization are available to work but are not scheduled?
■ What are the total number of hours, per GL period, that people who report to
me are available to work but are not scheduled?
■ What does the spread of availability look like over time?
The Available Resource Hours by GL Period worksheet helps you answer these
questions by letting you analyze and manipulate availability information by
Organization, Resource Manager and Person. Additionally, you can roll the data up
to Fiscal Quarter and year.

Parameter Page
Parameters are predefined conditions that you can leave on or switch off by
selecting the Conditions dialogue under the Tools menu.
■ Organization - You can choose only one organization but the worksheet will
then run for the organization chosen and any below it in the reporting
hierarchy.
■ Resource Manager - You can choose one or more Resource Managers for whom
you want to view data.
■ Fiscal Year - You can choose only one year.
■ Fiscal Quarter Number - You can choose only one quarter number for the year
you have specified.

Conditions
Conditions are filters in the worksheet that you can turn on or off.
There are no conditions (other than those defined for the parameters listed above)
predefined on this worksheet.

Setting Up for Reporting Capabilities 12-59

Discoverer Workbooks

Column Dimensions
■ Fiscal Year - the name of a Fiscal Year
■ Fiscal Quarter - the name of a Fiscal Quarter
■ GL Period - the name of a GL period
■ Available Hours (Potential) - the number of hours unscheduled. It is equal to
(Capacity Hours- Confirmed Hours- Provisional Hours).
■ Available Hours (Definite) - the number of hours unscheduled or scheduled in a
provisional status. It is equal to (Capacity Hours- Confirmed Hours).
■ Availability % (Potential) - the number of hours unscheduled divided by the
capacity. It is equal to (Capacity Hours- Confirmed Hours- Provisional
Hours)/Capacity*100.
■ Availability % (Definite) - the number of hours unscheduled or schedules in a
provisional status divided by the capacity. It is equal to (Capacity
Hours-Confirmed Hours)/Capacity*100.

Row Dimensions
■ Organization - the name of an organization.
■ Resource Manager - the name of a resource manager.
■ Person - the name of a person.
■ Job Name - the title of the job of the person.
■ Job Level - the global job level of the person.

Additional Information
The following table lists items that can be added to the Available Resource Hours by
GL Period worksheet:

Business Area Folder Item

Staffing Resource Schedule by GL Confirmed Hours
Period
Staffing Resource Schedule by GL Provisional Hours
Period
Staffing Resource Schedule by GL Total Hours
Period

12-60 Oracle Project Resource Management Implementation and Administration Guide

 Discoverer Workbooks

Business Area Folder Item

Staffing Resource Capacity by GL Capacity Hours
Period

Available Resource Hours by PA Period

This worksheet addresses business questions such as:
■ What is the total number of hours, per PA period, that people in my
organization are available to work but are not scheduled?
■ What are the total number of hours, per PA period, that people who report to
me are available to work but are not scheduled?
■ What does the spread of availability look like over time?
The Available Resource Hours by PA Period worksheet helps you answer these
questions by letting you analyze and manipulate availability information by
Organization, Resource Manager and Person. Additionally, you can roll the data up
to Fiscal Quarter and year.

Parameter Page
Parameters are predefined conditions that you can leave on or switch off by
selecting the Conditions dialogue under the Tools menu.
■ Organization - You can choose only one organization but the worksheet will
then run for the organization chosen and any below it in the reporting
hierarchy.
■ Resource Manager - You can choose one or more Resource Managers for whom
you want to view data.
■ Fiscal Year - You can choose only one year.
■ Fiscal Quarter Number - You can choose only one quarter number for the year
you have specified.

Conditions
Conditions are filters in the worksheet that you can turn on or off.
There are no conditions (other than those defined for the parameters listed above)
predefined on this worksheet.

Setting Up for Reporting Capabilities 12-61

Discoverer Workbooks

Column Dimensions
■ Fiscal Year - the name of a Fiscal Year
■ Fiscal Quarter - the name of a Fiscal Quarter
■ PA Period - the name of a PA period
■ Available Hours (Potential) - the number of hours unscheduled. It is equal to
(Capacity Hours- Confirmed Hours- Provisional Hours).
■ Available Hours (Definite) - the number of hours unscheduled or scheduled in a
provisional status. It is equal to (Capacity Hours- Confirmed Hours).
■ Availability % (Potential) - the number of hours unscheduled divided by the
capacity. It is equal to (Capacity Hours- Confirmed Hours- Provisional
Hours)/Capacity*100.
■ Availability % (Definite) - the number of hours unscheduled or schedules in a
provisional status divided by the capacity. It is equal to (Capacity
Hours-Confirmed Hours)/Capacity*100.

Row Dimensions
■ Organization - the name of an organization.
■ Resource Manager - the name of a resource manager.
■ Person - the name of a person.
■ Job Name - the title of the job of the person.
■ Job Level - the global job level of the person.

Additional Information
The following table lists items that can be added to the Available Resource Hours by
PA Period worksheet:

Business Area Folder Item

Staffing Resource Schedule by PA Confirmed Hours
Period
Staffing Resource Schedule by PA Provisional Hours
Period
Staffing Resource Schedule by PA Total Hours
Period

12-62 Oracle Project Resource Management Implementation and Administration Guide

 Discoverer Workbooks

Business Area Folder Item

Staffing Resource Capacity by PA Capacity Hours
Period

Available Resource Hours by Global Week

Some of the business questions answered by this worksheet are:
■ What is the total number of hours, per Global Week, that people in my
organization are available to work but are not scheduled?
■ What are the total number of hours, per Global Week, that people who report to
me are available to work but are not scheduled?
■ What does the spread of availability look like over time?
The Available Resource Hours by Global Week worksheet helps you answer these
questions by letting you analyze and manipulate availability information by
Organization, Resource Manager and Person. Additionally, you can drill down to
view availability by day.

Parameter Page
Parameters are predefined conditions that you can leave on or switch off by
selecting the Conditions dialogue under the Tools menu.
■ Organization - You can choose only one organization but the worksheet will
then run for the organization chosen and any below it in the reporting
hierarchy.
■ Resource Manager - You can choose one or more Resource Managers for whom
you want to view data.
■ Calendar Year - You can choose only one year.
■ Calendar Month - You can choose only one month for the year you have
specified.

Conditions
Conditions are filters in the worksheet that you can turn on or off.
There are no conditions (other than those defined for the parameters listed above)
predefined on this worksheet.

Setting Up for Reporting Capabilities 12-63

Discoverer Workbooks

Column Dimensions
■ Calendar Year - the name of a calendar year
■ Calendar Month - the name of a Fiscal Quarter
■ Global Week - the name of a Global Week
■ Day - the name of a day
■ Available Hours (Potential) - the number of hours unscheduled. It is equal to
(Capacity Hours- Confirmed Hours- Provisional Hours).
■ Available Hours (Definite) - the number of hours unscheduled or scheduled in a
provisional status. It is equal to (Capacity Hours- Confirmed Hours).
■ Availability % (Potential) - the number of hours unscheduled divided by the
capacity. It is equal to (Capacity Hours- Confirmed Hours- Provisional
Hours)/Capacity*100.
■ Availability % (Definite) - the number of hours unscheduled or schedules in a
provisional status divided by the capacity. It is equal to (Capacity
Hours-Confirmed Hours)/Capacity*100.

Row Dimensions
■ Organization - the name of an organization
■ Resource Manager - the name of a resource manager
■ Person - the name of a person
■ Job Name - the title of the job of the person
■ Job Level - the global job level of the person

Additional Information
The following table lists items that can be added to the Available Resource Hours by
Global Week worksheet in the Staffing business area:

Business Area Folder Item

Staffing Resource Schedule by Global Week Confirmed Hours
Staffing Resource Schedule by Global Week Provisional Hours
Staffing Resource Schedule by Global Week Total Hours
Staffing Resource Capacity by Global Week Capacity Hours

12-64 Oracle Project Resource Management Implementation and Administration Guide

 Discoverer Workbooks

Overcommitted Resource Hours (PAOVCRES)

The overcommitted resource hours workbook allows you to evaluate the number of
hours people are currently scheduled over their capacity. You can view this
information by Organization and Resource Manager.
Worksheets included in this workbook are:
■ Overcommitted Resource Hours by GL Period
■ Overcommitted Resource Hours by PA Period
■ Overcommitted Resource Hours by Global Week

Restrictions
■ When selecting an organization, the user will be restricted to those within the
reporting hierarchy of the operating unit associated with their responsibility.
■ When selecting a resource manager, the user will be restricted to those that
report to them or manage people they have resource authority over.

Overcommitted Resource Hours by GL Period

This worksheet addresses business questions such as:
■ What is the total number of overcommitted hours for the people in my
organization per GL period?
■ What are the total number of overcommitted hours for individuals in my
organization per GL period?
■ What does the spread of overcommitted hours per GL period look like over
time?
■ If a person is overcommitted, what assignments have caused this?
The Overcommitted Resource Hours by GL Period worksheet helps you answer
these questions by letting you analyze and manipulate capacity and
overcommitment information by Organization, Resource Manager and Person.
Additionally, you can roll the data up to Fiscal Quarter and year.

Parameter Page
Parameters are predefined conditions that you can leave on or switch off by
selecting the Conditions dialogue under the Tools menu.

Setting Up for Reporting Capabilities 12-65

Discoverer Workbooks

■ Organization - You can choose only one organization but the worksheet will
then run for the organization chosen and any below it in the reporting
hierarchy.
■ Resource Manager - You can choose one or more Resource Managers for whom
you want to view data.
■ Fiscal Year - You can choose only one year.
■ Fiscal Quarter Number - You can choose only one quarter number for the year
you have specified.

Conditions
Conditions are filters in the worksheet that you can turn on or off.
There are no conditions (other than those defined for the parameters listed above)
predefined on this worksheet.

Column Dimensions
■ Fiscal Year - the name of a Fiscal Year
■ Fiscal Quarter - the name of a Fiscal Quarter
■ GL Period - the name of a GL period
■ Capacity Hours - number of hours available to work
■ Confirmed Hours - number of hours scheduled with a confirmed status
■ Overcommitted Hours - number of hours scheduled with a confirmed status
minus capacity
■ Overcommitted percentage - number of over-committed hours divided by
capacity

Row Dimensions
■ Organization - the name of an organization.
■ Resource Manager - the name of a resource manager.
■ Person - the name of a person.
■ Job Name - the title of the job of the person.
■ Job Level - the global job level of the person.

12-66 Oracle Project Resource Management Implementation and Administration Guide

 Discoverer Workbooks

Additional Information
The table that follows lists items that can be added to the Scheduled Resource
Hours by GL Period worksheet in the Staffing business area:

Business Area Folder Item

Staffing Resource Schedule by GL Period Total Hours
Staffing Resource Schedule by GL Period Provisional Hours

Suggestion: A useful addition to this worksheet is a user-defined

exception highlighting people whose percentage overcommitment
is over a certain threshold.

It is common practice for the cells of data points meeting the exception criteria to be
shown in red.
If the worksheet returns a value that requires further investigation, you should
create a more detailed worksheet based on the folder Resource Schedule by GL
Period: Team Role Detail. Using this folder, the actual assignments on which a given
person is scheduled can be examined and manipulated. The data you can view
includes:
■ Project - the name of a project.
■ Project Manager - the name of the current project manager
■ Probability - the probability of the project
■ Team Role - the team role name of the assignment
■ Start Date - the start date of the assignment
■ End Date - the end date of the assignment
■ Confirmed Hours - number of hours scheduled in a confirmed status

Overcommitted Resource Hours by PA Period

This worksheet addresses business questions such as:
■ What is the total number of overcommitted hours for the people in my
organization per PA period?

Setting Up for Reporting Capabilities 12-67

Discoverer Workbooks

■ What are the total number of overcommitted hours for individuals in my

organization per PA period?
■ What does the spread of overcommitted hours per PA period look like over
time?
■ If a person is overcommitted, what assignments have caused this?
The Resource Hours by PA Period worksheet helps you answer these questions by
letting you analyze and manipulate capacity and overcommitment information by
Organization, Resource Manager and Person. Additionally, you can roll the data up
to Fiscal Quarter and year.

Parameter Page
Parameters are predefined conditions that you can leave on or switch off by
selecting the Conditions dialogue under the Tools menu.
■ Organization - You can choose only one organization but the worksheet will
then run for the organization chosen and any below it in the reporting
hierarchy.
■ Resource Manager - You can choose one or more Resource Managers for whom
you want to view data.
■ Fiscal Year - You can choose only one year.
■ Fiscal Quarter Number - You can choose only one quarter number for the year
you have specified.

Conditions
Conditions are filters in the worksheet that you can turn on or off. There are no
conditions (other than those defined for the parameters listed above) predefined on
this worksheet.

Column Dimensions
■ Fiscal Year - the name of a Fiscal Year
■ Fiscal Quarter - the name of a Fiscal Quarter
■ PA Period - the name of a PA period
■ Capacity Hours - number of hours available to work
■ Confirmed Hours - number of hours scheduled with a confirmed status

12-68 Oracle Project Resource Management Implementation and Administration Guide

 Discoverer Workbooks

■ Overcommitted Hours - number of hours scheduled with a confirmed status

minus capacity
■ Overcommitted percentage - number of overcommitted hours divided by
capacity

Row Dimensions
■ Organization - the name of an organization
■ Resource Manager - the name of a resource manager
■ Person - the name of a person
■ Job Name - the title of the job of the person
■ Job Level - the global job level of the person

Additional Information
The following table lists items that can be added to the Overcommitted Resource
Hours by PA Period worksheet in the Staffing business area:

Business Area Folder Item

Staffing Resource Schedule by GL Period Total Hours
Staffing Resource Schedule by GL Period Provisional Hours

Suggestion: A useful addition to this worksheet is a user-defined

exception highlighting people whose percentage over-commitment
is over a certain threshold.

It is common practice for the cells of data points meeting the exception criteria to be
shown in red.
If the worksheet returns a value that requires further investigation, you should
create a more detailed worksheet based on the folder Resource Schedule by PA
Period: Team Role Detail. Using this folder, the actual assignments on which a given
person is scheduled can be examined and manipulated. The data you can view
includes:
■ Project - the name of a project
■ Project Manager - the name of the current project manager

Setting Up for Reporting Capabilities 12-69

Discoverer Workbooks

■ Probability - the probability of the project

■ Team Role - the team role name of the assignment
■ Start Date - the start date of the assignment
■ End Date - the end date of the assignment
■ Confirmed Hours - number of hours scheduled in a confirmed status

Overcommitted Resource Hours by Global Week

This worksheet addresses business questions such as:
■ What is the total number of overcommitted hours for the people in my
organization per Global Week or Day?
■ What are the total number of overcommitted hours for individuals in my
organization per Global Week or Day?
■ What does the spread of overcommitted hours per Global Week or Day look
like over time?
■ If a person is overcommitted, what assignments have caused this?
The Overcommitted Resource Hours by Global Week worksheet helps you answer
these questions by letting you analyze and manipulate capacity and
overcommitment information by Organization, Resource Manager and Person.
Additionally, you can drill down to view the data by day (to view the hours per
day).

Parameter Page
Parameters are predefined conditions that you can leave on or switch off by
selecting the Conditions dialogue under the Tools menu.
■ Organization - You can choose only one organization but the worksheet will
then run for the organization chosen and any below it in the reporting
hierarchy.
■ Resource Manager - You can choose one or more Resource Managers for whom
you want to view data.
■ Calendar Year - You can choose only one year.
■ Calendar Month - You can choose only one calendar month for the year you
have specified.

12-70 Oracle Project Resource Management Implementation and Administration Guide

 Discoverer Workbooks

Conditions
Conditions are filters in the worksheet that you can turn on or off.
There are no conditions (other than those defined for the parameters listed above)
predefined on this worksheet.

Column Dimensions
■ Calendar Year - the name of a calendar year
■ Calendar Month - the name of a calendar month
■ Global Week - the name of a global week
■ Day - the name of a day
■ Capacity Hours - number of hours available to work
■ Confirmed Hours - number of hours scheduled with a confirmed status
■ Overcommitted Hours - number of hours scheduled with a confirmed status
minus capacity
■ Overcommitted percentage - number of over-committed hours divided by
capacity

Row Dimensions
■ Organization - the name of an organization.
■ Resource Manager - the name of a resource manager.
■ Person - the name of a person.
■ Job Name - the title of the job of the person.
■ Job Level - the global job level of the person.

Additional Information
The following table lists items that you can add to the Overcommitted Resource
Hours by Global Week worksheet in the Staffing business area:

Business Area Folder Item

Staffing Resource Schedule by GL Period Total Hours
Staffing Resource Schedule by GL Period Provisional Hours

Setting Up for Reporting Capabilities 12-71

Discoverer Workbooks

Suggestion: A useful addition to this worksheet is a user-defined

exception highlighting people whose percentage over-commitment
is over a certain threshold.

It is common practice for the cells of data points meeting the exception criteria to be
shown in red.
If the worksheet returns a value that requires further investigation, you should
create a more detailed spreadsheet based on the folder Resource Schedule by Global
Week: Team Role Detail. Using this folder, the actual assignments on which a given
person is scheduled can be examined and manipulated. The data you can view
includes:
■ Project - the name of a project
■ Project Manager - the name of the current project manager
■ Probability - the probability of the project
■ Team Role - the team role name of the assignment
■ Start Date - the start date of the assignment
■ End Date - the end date of the assignment
■ Confirmed Hours - number of hours scheduled in a confirmed status

Project Pipeline Workbook (PASALPIP)

The Project Pipeline workbook allows you to view the value of projects currently
within your pipeline. You can view this information by Organization and/or
Resource Manager. Thus, you can now track potential revenue attributable to
different classification codes with varying percentages.
You can run the report to view all projects that have a selected project role. The
report shows projects that have one or more classification category defined with a
single or multiple class codes. If the project has classification category with
percentage values for each class code then the various values in the report re-split
according to the specified percentage.
Worksheets included in this workbook are:
■ Project Pipeline by Fiscal Year
■ Project Pipeline by Fiscal Quarter

12-72 Oracle Project Resource Management Implementation and Administration Guide

 Discoverer Workbooks

■ Project Pipeline by GL Period

■ Project Pipeline by PA Period
In all worksheets, null values are displayed as 0.
Restrictions
■ When selecting an organization, the user is restricted to those they have
forecasting authority over and that are also within the reporting hierarchy of
the operating unit associated with their responsibility.

Project Pipeline by Fiscal Year

This worksheet addresses business questions such as:
■ What is my organization’s total/discounted Project Pipeline up to and
including a particular Fiscal Year?
■ What is the total/discounted project pipeline of project’s I will manage up to
and including a particular Fiscal Year?
■ How is the project pipeline spread across all industries up to and including a
particular Fiscal Year?
The Project Pipeline by Fiscal Year worksheet helps you answer these questions by
letting you analyze and manipulate project value and probability information by
Class Category, Organization and/or Project Manager.

Parameter Page
Parameters are predefined conditions that you can leave on or switch off by
selecting the Conditions dialogue under the Tools menu.
■ Organization - You can choose only one organization but the worksheet will
then run for the organization chosen and any below it in the reporting
hierarchy.
■ Classification Category - You can choose only one classification category. Your
project pipeline will then be displayed by the classification codes within the
category chosen. The list of Class Categories parameter shows all categories and
not just the categories with one class code defined.
■ Fiscal Year - You can choose only one year but the worksheet will also include
any projects still in the pipeline that have expected approval dates prior to the
year specified.

Setting Up for Reporting Capabilities 12-73

Discoverer Workbooks

■ Project Manager - You can choose one or more project managers. Project
Pipeline will only be shown for projects managed by the project managers
selected.
■ Include Values Over - a currency value that the total project pipeline figure
must be greater than in order for the project to be displayed.
■ Project Role: You can choose a project role to view the pipeline projects that
have the specified project role.
■ Project Member: You can choose a resource to view the pipeline projects that
have the resource.
■ Project Status: You can choose the project status parameter to include the
projects with all project statuses. By default, the value of Project Status
parameter is Unapproved.

Note: The Project Status parameter is available when using

Discoverer 4i only.

Conditions
Conditions are filters in the worksheet that you can turn on or off.
■ Include Probabilities Under - a numeric value that the project probability must
be less than in order for the project to be displayed. Defaults to 100.

Column Dimensions
■ Fiscal Year - the name of the Fiscal Year
■ Total Value - the total project value
■ Discounted Value - the total project value multiplied by the probability of the
project.
■ Class Code: the class code defined for the classification category.

Row Dimensions
■ Organization - the name of an organization.
■ Classification Code - the classification code within the classification category.
■ Project - the name of a project.
■ Primary Customer Name- the name of the primary customer.

12-74 Oracle Project Resource Management Implementation and Administration Guide

 Discoverer Workbooks

■ Project Probability - the current project probability.

■ Type - the name of the project type on which the project is based.
■ Status - the status of the project
■ Expected Approval Date - the date on which the project approval is expected

Project Pipeline by Fiscal Quarter

This worksheet addresses business questions such as:
■ What is my organization’s total/discounted Project Pipeline up to and
including a particular Fiscal Quarter?
■ What is the total/discounted Project Pipeline of project’s I will up to and
including a particular Fiscal Quarter?
■ How is the project pipeline spread across all industries up to and including a
particular Fiscal Quarter?
The Project Pipeline by Fiscal Quarter worksheet helps you answer these questions
by letting you analyze and manipulate project value and probability information by
Class Category, Organization and/or Project Manager.

Parameter Page
Parameters are predefined conditions that you can leave on or switch off by
selecting the Conditions dialogue under the Tools menu.
■ Organization - You can choose only one organization but the worksheet will
then run for the organization chosen and any below it in the reporting
hierarchy.
■ Classification Category - You can choose only one classification category. Your
project pipeline will then be displayed by the classification codes within the
category chosen. The list of Class Categories parameter shows all categories and
not just the categories with one class code defined.
■ Fiscal Year - You can choose only one year but the worksheet will also include
any projects still in the pipeline that have expected approval dates prior to the
year specified.
■ Fiscal Quarter Number - You can choose only one quarter number but the
worksheet will also include any projects still in the pipeline that have expected
approval dates prior to the quarter specified.

Setting Up for Reporting Capabilities 12-75

Discoverer Workbooks

■ Project Manager - You can choose one or more project managers. Project
pipeline will only be shown for projects managed by the project managers
selected.
■ Include Values Over - a currency value that the total project pipeline figure
must be greater than in order for the project to be displayed.
■ Project Role: You can choose a project role to view the pipeline projects that
have the specified project role.
■ Project Member: You can choose a resource to view the pipeline projects that
have the resource.
■ Project Status: You can choose the project status parameter to include the
projects with all project statuses.You can choose the project status parameter to
include the projects with all project statuses. By default, the value of Project
Status parameter is Unapproved.

Note: The Project Status parameter is available when using

Discoverer 4i only.

Conditions
Conditions are filters in the worksheet that you can turn on or off.
■ Include Probabilities Under - a numeric value that the project probability must
be less than in order for the project to be displayed. Defaults to 100.

Column Dimensions
■ Fiscal Year - the name of the Fiscal Year
■ Fiscal Quarter - the name of the Fiscal Quarter
■ Total Value - the total project value
■ Discounted Value - the total project value multiplied by the probability of the
project.
■ Class Code: the class code defined for the classification category.

Row Dimensions
■ Organization - the name of an organization.
■ Classification Code - the classification code within the classification category.
■ Project - the name of a project.

12-76 Oracle Project Resource Management Implementation and Administration Guide

 Discoverer Workbooks

■ Primary Customer Name- the name of the primary customer.

■ Project Probability - the current project probability.
■ Type - the name of the project type on which the project is based.
■ Status - the status of the project

Project Pipeline by GL Period

This worksheet addresses business questions such as:
■ What is my organization’s total/discounted Project Pipeline up to and
including a particular GL period?
■ What is the total/discounted Project Pipeline of project’s I will manage up to
and including a particular GL period?
■ How is the project pipeline spread across all industries up to and including a
particular GL period?
The Project Pipeline by GL period worksheet helps you answer these questions by
letting you analyze and manipulate project value and probability information by
Class Category, Organization and/or Project Manager.

Parameter Page
Parameters are predefined conditions that you can leave on or switch off by
selecting the Conditions dialogue under the Tools menu.
■ Organization - You can choose only one organization but the worksheet will
then run for the organization chosen and any below it in the reporting
hierarchy.
■ Classification Category - You can choose only one classification category. Your
project pipeline will then be displayed by the classification codes within the
category chosen. The list of Class Categories parameter shows all categories and
not just the categories with one class code defined.
■ Fiscal Year - You can choose only one year but the worksheet will also include
any projects still in the pipeline that have expected approval dates prior to the
year specified.
■ Fiscal Quarter Number - You can choose only one quarter number but the
worksheet will also include any projects still in the pipeline that have expected
approval dates prior to the quarter specified.

Setting Up for Reporting Capabilities 12-77

Discoverer Workbooks

■ Project Manager - You can choose one or more project managers. Project
pipeline will only be shown for projects managed by the project managers
selected.
■ Include Values Over - a currency value that the total project pipeline figure
must be greater than in order for the project to be displayed.
■ Project Role: You can choose a project role to view the pipeline projects that
have the specified project role.
■ Project Member: You can choose a resource to view the pipeline projects that
have the resource.
■ Project Status: You can choose the project status parameter to include the
projects with all project statuses. By default, the value of Project Status
parameter is Unapproved.

Note: The Project Status parameter is available when using

Discoverer 4i only.

Conditions
Conditions are filters in the worksheet that you can turn on or off.
■ Include Probabilities Under - a numeric value that the project probability must
be less than in order for the project to be displayed. Defaults to 100.

Column Dimensions
■ Fiscal Year - the name of the Fiscal Year
■ Fiscal Quarter - the name of the Fiscal Quarter
■ GL Period - the name of the GL period
■ Total Value - the total project value
■ Discounted Value - the total project value multiplied by the probability of the
project.
■ Class Code: the class code defined for the classification category.

Row Dimensions
■ Organization - the name of an organization.
■ Classification Code - the classification code within the classification category.

12-78 Oracle Project Resource Management Implementation and Administration Guide

 Discoverer Workbooks

■ Project - the name of a project.

■ Primary Customer- the name of the primary customer.
■ Project Probability - the current project probability.
■ Type - the name of the project type on which the project is based.
■ Status - the status of the project

Project Pipeline by PA Period

This worksheet addresses business questions such as:
■ What is my organization’s total/discounted Project Pipeline up to and
including a particular PA period?
■ What is the total/discounted Project Pipeline of project’s I will manage up to
and including a particular PA period?
■ How is the project pipeline spread across all industries up to and including a
particular PA period?
The Project Pipeline by PA period worksheet helps you answer these questions by
letting you analyze and manipulate project value and probability information by
Class Category, Organization and Project Manager.

Parameter Page
Parameters are predefined conditions that you can leave on or switch off by
selecting the Conditions dialog under the Tools menu.
■ Organization - You can choose only one organization but the worksheet will
then run for the organization chosen and any below it in the reporting
hierarchy.
■ Classification Category - You can choose only one classification category. Your
project pipeline will then be displayed by the classification codes within the
category chosen.The list of Class Categories parameter shows all categories and
not just the categories with one class code defined.
■ Fiscal Year - You can choose only one year but the worksheet will also include
any projects still in the pipeline that have expected approval dates prior to the
year specified.
■ Fiscal Quarter Number - You can choose only one quarter number but the
worksheet will also include any projects still in the pipeline that have expected
approval dates prior to the quarter specified.

Setting Up for Reporting Capabilities 12-79

Discoverer Workbooks

■ Project Manager - You can choose one or more project managers. Project
pipeline will only be shown for projects managed by the project managers
selected.
■ Include Values Over - a currency value that the total project pipeline figure
must be greater than in order for the project to be displayed.
■ Project Role: You can choose a project role to view the pipeline projects that
have the specified project role.
■ Project Member: You can choose a resource to view the pipeline projects that
have the resource.
■ Project Status: You can choose the project status parameter to include the
projects with all project statuses.By default, the value of Project Status
parameter is Unapproved.

Note: The Project Status parameter is available when using

Discoverer 4i only.

Conditions
Conditions are filters in the worksheet that you can turn on or off.
■ Include Probabilities Under - a numeric value that the project probability must
be less than in order for the project to be displayed. Defaults to 100.

Column Dimensions
■ Fiscal Year - the name of the Fiscal Year
■ Fiscal Quarter - the name of the Fiscal Quarter
■ PA Period - the name of the PA period
■ Total Value - the total project value
■ Discounted Value - the total project value multiplied by the probability of the
project.
■ Class Code: the class code defined for the classification category.

Row Dimensions
■ Organization - the name of an organization
■ Classification Code - the classification code within the classification category

12-80 Oracle Project Resource Management Implementation and Administration Guide

 Discoverer Workbooks

■ Project - the name of a project

■ Primary Customer- the name of the primary customer.
■ Project Probability - the current project probability
■ Type - the name of the project type on which the project is based
■ Status - the status of the project
■ Expected Approval Date - the date on which the project approval is expected

Organization Competence Summary Workbook (PA_PRM_ORG_COMP_SUM)

The organization competence summary workbook enables you to view a summary
of your resources’ competencies in your organization.

Note: .This workbook is built on Discoverer 4i only

Worksheets included in this workbook are:

■ Organization Competence Summary
■ Resource Listing for Organization and Competence
In all worksheets, null values are displayed as 0.
Restrictions
You can view the resources that you have organization authority or are a Resource
Manager.

Organization Competence Summary Worksheet

This worksheet addresses business questions such as:
■ What is the spread of competencies across the resources in my organization?
■ Where am I low in resources having certain competencies?
■ What resource skills need to be improved?
The Organization Competence Summary worksheet helps you answer these
questions by letting you review and analyze the competencies of your resources
within your organization and enable you to drill down to another report for further
information.

Setting Up for Reporting Capabilities 12-81

Discoverer Workbooks

The worksheet displays only resources who have current or future assignments that
belong to the selected organization.

Parameter Page
Parameters are enabled predefined conditions that you can disable by selecting the
Conditions dialogue under the Tools menu.
■ Organization - You can select an organization that the resource belongs to.
■ Include Sub-Organizations- You can choose to include sub-organizations within
the organization hierarchy. The hierarchy used for sub-organizations is the
Reporting Hierarchy from the starting organization selected above.
■ Competence Name- You can select to view resources with a particular
competence across all business groups.

Conditions
Conditions are filters in the worksheet that you enable or disable.
No conditions, other than those defined for the parameters listed above, exist for
this worksheet.

Column Dimensions
■ Alias- a short name for the competence
■ Description- the description of the competence
■ Resource Count- the total number of resources who have the competence
■ View Resources- the link to the list of resources who have the competence

Row Dimensions
■ Organization - Organization of the resource
■ Competence Name- the name of the competence

Additional Information
The following table lists items that can be added to the Organization Competence
Summary Worksheet in the Staffing business area:

Business Area Folder Items

Competencies Organization Competence Summary Segments 1...20, Business Group

12-82 Oracle Project Resource Management Implementation and Administration Guide

 Discoverer Workbooks

Resource Listing for Organization and Competence Worksheet

This worksheet addresses business questions such as:
■ Who are the resources that have a particular competence?
■ Which resource skills need to be updated?
The Resource Listing for Organization and Competence worksheet helps you
answer these questions by showing you details of all resources within an
organization who have a particular competence and their respective proficieny
level.

Parameter Page
Parameters are enabled predefined conditions that you can disable by selecting the
Conditions dialogue under the Tools menu.
■ Organization - You can select an organization. The worksheet shows the
organization chosen and any below it in the reporting hierarchy.
■ Competence Name- You can select a particular competence across all business
groups.

Conditions
Conditions are filters in the worksheet that you enable or disable.
No conditions, other than those defined for the parameters listed above, exist for
this worksheet.

Column Dimensions
■ Proficiency Level- the proficiency level of the competence of the resource
■ Manager- the name of the manager of the resource
■ Job Name- the job of the resource
■ Project Job Level- the global job level of the resource
■ Project Job Code- the project code of the job
■ Location- the primary address of the resource
■ View Competence Details- the link to the competence details of the resource.

Row Dimensions
■ Person- the full name of the resource

Setting Up for Reporting Capabilities 12-83

Discoverer Workbooks

Resource Competencies Workbook (PA_PRM_RES_COMP)

The Resource Competencies workbook enables you to view a complete listing of the
competencies for all the resources, by organization. For each resource, you can drill
down to the Resource Competencies Details page to view the competencies of the
resource.

Note: .This workbook is built on Discoverer 4i only

Worksheets included in this workbook are:

■ Organization Resource Competencies
■ Project Resource Competencies
■ Resource Competence Details
Restrictions
You can view the resources that you have organization authority for or are a
Resource Manager.

Organizaton Resource Competencies

This worksheet addresses business questions such as:
■ What competencies do resources in my organization have?
■ What is the proficiency level of the competencies?
The Organization Resource Competencies worksheet helps you answer these
questions by showing you all resources for an organization or group of
organizatons, the competencies of each resource and the proficency level of those
competencies. You can also view the competence spread by jobs and job levels.

Parameter Page
Parameters are enabled predefined conditions that you can disable by selecting the
Conditions dialogue under the Tools menu.
■ Organization - You can select an organization.
■ Include Sub-Organizations- You can choose to include sub-organizations within
the organization hierarchy. The hierarchy used for sub-organizations is the
Reporting Hierarchy from the starting organization selected above.

12-84 Oracle Project Resource Management Implementation and Administration Guide

 Discoverer Workbooks

■ Manager- You can choose a Resource Manager to limit the resources in the
report to the ones who report to the selected Resource Manager.
■ Resource- You can choose only one resource name.
■ Job- You can choose the job name of the resource. All jobs across business
groups are shown.
■ Job Level- You can choose the global job level of the resource. All levels across
business groups are shown.
■ Billable Job Only- You can choose to include only resources that have a billable
job.

Conditions
Conditions are filters in the worksheet that you enable or disable.
No conditions, other than those defined for the parameters listed above, exist for
this worksheet.

Column Dimensions
■ Competencies - a listing of all the competence aliases of the resource, prefixed
by the proficiency level of the competence. If the competence does not have a
alias than the competence name is used.
■ Competence Count- the total number of competencies of the resource
■ Manager- the name of the manager of the resource
■ Last Updated- the latest date the competence profile of resource was updated
■ Job- the job of the resource
■ Project Job Level- the global job level of the resource
■ Job Code- the job code of the resource
■ View Competencies Details- the link to view the detail competencies of the
resource

Row Dimensions
■ Organization - The organization of the resource
■ Person- the name of the resource

Setting Up for Reporting Capabilities 12-85

Discoverer Workbooks

Project Resource Competencies

This worksheet addresses business questions such as:
■ What competencies do my project’s resources have?
■ What is the proficiency of the competencies?
The Project Resource Competencies worksheet helps you answer these questions by
showing you all resources in each project, the competencies for each resource and
the proficiency level of those competencies.

Parameter Page
Parameters are enabled predefined conditions that you can disable by selecting the
Conditions dialogue under the Tools menu.
■ Project Name- You can choose the name of the project that has resource
assignments.
■ Manager- You can choose a Resource Manager to limit the resources in the
report to the ones who report to the selected Resource Manager.
■ Resource- You can choose a resource name.
■ Job- You can choose the job name of the resource. All jobs across business
groups are shown
■ Job Level- You can choose the global job level of the resource. All levels across
business groups are shown.
■ Billable Job Only- You can choose to include only resources that have a billable
job.

Conditions
Conditions are filters in the worksheet that you enable or disable.
No conditions, other than those defined for the parameters listed above, exist for
this worksheet.

Column Dimensions
■ Competencies - a listing of all the competence aliases of the resource, prefixed
by the proficiency level of the competence. If the competence does not have a
alias than the competence name is used.
■ Competence Count- the total number of competencies of the resource
■ Manager- the name of the resource manager

12-86 Oracle Project Resource Management Implementation and Administration Guide

 Discoverer Workbooks

■ Last Updated- the latest date the competence was updated

■ Job- the job of the resource
■ Project Job Level- the global job level of the resource
■ Job Code- the job code of the resource
■ View Competencies Details- the link to view the detail competencies of the
resource

Row Dimensions
■ Project Name- the name of the project that has the resource assignment
■ Project Number- the number of the project that has the resource assignment
■ Person- the name of the resource

Resource Competence Details

This worksheet addresses business questions such as:
■ What is each individual’s competence?
■ What business group do they belong to?
■ What is the proficiency level of their competencies?
■ When were their competencies last updated?
The Resource Competence Details worksheet helps you answer these questions by
showing you details of each resource competence and the proficiency level of the
competencies.

Parameter Page
Parameters are enabled predefined conditions that you can disable by selecting the
Conditions dialogue under the Tools menu.
■ Resource- You can choose any resource who has a current or future assignment
that belongs to an organization in the reporting organization hierarchy.

Conditions
Conditions are filters in the worksheet that you enable or disable.
No conditions, other than those defined for the parameters listed above, exist for
this worksheet.

Setting Up for Reporting Capabilities 12-87

Discoverer Workbooks

Column Dimensions
■ Competence Alias- the short name for the competence
■ Business Group Name- the name of business group to which the resource
belongs
■ Proficiency Level- the proficiency level of the competence of the resource
■ Last Updated - the latest date the competence profile of resource was updated.

Row Dimensions
■ Competence Name- the name of the competence of the resource

Additional Information
The following table lists items that can be added to the Resource Competence
Details Worksheet in the Staffing business area.

Business Area Folders Items

Competencies Resource Competence Details Segments 1...20

12-88 Oracle Project Resource Management Implementation and Administration Guide

 Discoverer Query Tips

Discoverer Query Tips

The following suggestions provide you with guidance while you are performing
reporting activities.

Avoid Blind Queries

A blind query is a query that selects most or all of the items from a business view
folder without specifying any conditions.

Why avoid Blind Queries? Since no condition is specified in a blind query, the
query is not able to efficiently use the indexes created for the underlying tables. You
may encounter poor query performance if your database contains a large amount of
data.

Capacity, Schedule and Project Pipeline Views

When you create a workbook using any of the folders listed below, we suggest that
you create the conditions outlined below. In particular, by restricting the time
period for which the workbook is run it’s performance will be improved.

Project Pipeline Folders

■ Always join to the Classification Categories folder and specify one particular
category
■ Always specify a period of time (such as a quarter, period, or month)

Resource Schedule Folders

■ Always specify a period of time (such as a quarter, period, or month)
Use the OR statement in your condition rather than the IN statement. For
example, you should use:
Period Name = Feb-99 OR Period Name = Mar-99

instead of:
Period Name IN (Feb-99, Mar-99)

Setting Up for Reporting Capabilities 12-89

Discoverer Query Tips

12-90 Oracle Project Resource Management Implementation and Administration Guide

 13
Maintaining Your Data

As your data increases and changes to meet the demands of your projects,
maintaining data integrity becomes more imperative. In order to ensure the
accuracy of your data as changes are made, you should understand how additions
and changes affect the overall structure of your data.

Note: If you make changes to information through Oracle forms

that you want reflected in a poplist, you must stop and restart the
Web server.

This chapter discusses the impact of specific data modifications. It also describes the
built-in administrative processes that when run ensure that these changes are
reflected throughout the application. In order to run any of the processes described
in this chapter, you must have Project Super User responsibility.
The covered topics are:
■ Understanding Data Processing
■ Understanding the Impact of Changes to HRMS-Based Information
■ Maintaining Schedules
■ Maintaining Utilization Values
■ Maintaining Forecast Information

Maintaining Your Data 13-1

Understanding Data Processing

Understanding Data Processing

Oracle Project Resource Management uses deferred workflow processes and
administrative processes to manage changes to your data. You must configure and
manage the engines for both types of processes in order to handle the volume of
changes happening within your system. For more information on these
technologies, refer to:
■ Oracle Workflow Guide
■ Oracle Application Object Library User Guide
Most of the changes you make to your data automatically update related
information within the application. These changes occur without any intervention
on your part. However, some changes require the use of administrative processes to
ensure that the change is reflected accurately. In particular, two situations require
this level of maintenance:
■ If the automatic processes encounter errors due to missing or invalid setup
information, or due to technical failures
In this case, an administrative user is notified of the problem, and advised to
run an administrative process to complete the changes.
■ If the changed information is not expected to be done frequently enough to
warrant an automatic process
For example, if a change is made to a calendar, you must run the Create
Calendar Schedules process to reflect the calendar change throughout the
system.

Note: Assign at least one user to the seeded application user

Projects Application Administrator. This user receives notifications
regarding any encountered workflow processing errors. This user
should also have the appropriate authority to run the
administrative processes which assist in the correction of some of
the errors.

13-2 Oracle Project Resource Management Implementation and Administration Guide

 Understanding the Impact of Changes to HRMS-Based Information

Understanding the Impact of Changes to HRMS-Based Information

You will modify various setup and transaction data during the course of using the
Oracle Project Resource Management application. Other changes may also occur to
your employee data in Oracle HRMS. The system records the changes discussed in
this section in a holding place until the deferred workflow process item type called
HR Related Updates Workflow is run. This deferred workflow process synchronizes
the HRMS data with the Projects data.

Note: The changes against the HR tables are recorded only if:
■ the profile option PA: Licensed to Use Project Resource
management is set to Yes, or
■ actual utilization is implemented for at least one of the
operating units

For more information on the deferred workflow processes, see "Initiating Deferred
Workflow Processes" in Chapter 14, "Overview of the Predefined Workflows".

Changing Job Information

Changing job information such as job levels, billability, or utilization can have a
direct impact on utilization reporting and forecast results.

Job Levels
Job levels determine the experience level of a particular job. For example, you can
have three engineers with varying levels of experience and skill. You can change job
levels by:
■ changing the sequence (level) associated with the grade
■ assigning a new grade to a job
■ mapping a job to a new master job with a higher sequence
As you have the ability to search for resources by job levels, the job levels must be
reflected accurately on the resources. Therefore, the system migrates any changes
you make to the job levels to the job levels assigned to the resources.

Maintaining Your Data 13-3

Understanding the Impact of Changes to HRMS-Based Information

Job Billability
Oracle Project Resource Management uses the HR jobs entities to indicate whether
or not jobs are billable. This billable status also determines the billability of
resources based on their assignments. Therefore, project forecasting is affected by
changes to the billability status of a job.

Utilization Calculation
You can indicate whether or not to include a resource during the calculation of
utilization by selecting a check box called Include in Utilization during the job
setup. If you change the value of this check box, the utilization totals will reflect
your change the next time the utilization totals are recalculated.

Changing Organization Information

The default operating unit (OU) and the default calendar are stored at the
organization level. All resources, as well as their assignments, inherit these defaults.
Therefore, if the default operating unit of the organization changes during the active
period of an assignment, the assignment inherits the new operating unit for the
entire assignment period.

Note: Only resources belonging to organizations identified as

Expenditure organizations inherit the default operating unit from
the organization.

Changing Organizational Hierarchy Information

Oracle Project Resource Management stores organizations in the reporting
hierarchy to facilitate searching for resources by organizations. Therefore, changes
to the organization hierarchy impact resource searches. An end date is entered on a
resource if the organization to which the resource belongs is removed from the
expenditure hierarchy. As a result, the resource is neither accessible for searches nor
accessible for viewing through the Resource List page.

13-4 Oracle Project Resource Management Implementation and Administration Guide

 Understanding the Impact of Changes to HRMS-Based Information

Changing Resource Information

Oracle Project Resource Management acquires information from the HRMS people
tables for resources assigned to Project Expenditure organizations and all people
acting as team members on a project. This acquisition occurs automatically
whenever changes are made to the resource name or address. It also occurs when a
person that exists in the HRMS system is not yet established as a resource and this
person is being added as a project member on a project within Project Resource
Management.

Changing an Assignment
Oracle Project Resource Management stores only the HR primary assignment
information. Information changes on this assignment, such as the effective dates,
organization, job, or supervisor changes, trigger the deferred workflow process to
synchronize the Oracle HRMS data with the Oracle Project Resource Management
data.

Maintaining Your Data 13-5

Maintaining Schedules

Maintaining Schedules
Every resource, requirement, and assignment has a schedule. The schedules are
comprised of work patterns that include working hours and exceptions, such as
vacation days. Each schedule is based on the calendar for the organization or an
individually assigned calendar.
Changes to these calendars impact the schedules of the resources, requirements, and
assignments differently. Oracle Project Resource Management provides the
following two administrative processes to help manage these changes and to
maintain consistent schedule information throughout the application:
■ PRC: Generate Calendar Schedules
■ PRC: Rebuild Resource Timeline
These processes update the schedules and timelines tables with changes to the
calendars. For more information on setting up calendars and schedules, see
Chapter 8, "Defining Calendars and Schedules".

Updating Schedules with Calendar Changes

Changes to the calendar appear on the schedules and timelines of the resources,
new requirements, and new assignments only after you run a process called PRC:
Generate Calendar Schedules.
Existing requirements and scheduled assignments on resource calendars are not
impacted by changes. For example, if you add a holiday to the organization
calendar and run the PRC: Generate Calendar Schedules process, you will not see
this new holiday reflected on any existing requirements or assignment schedules.
However, the availability of a person is reduced by the number of hours in the
holiday period because availability is regenerated every time the process is run.
You can run the PRC: Generate Calendar Schedules process for a single calendar or
a range of calendars. You should run this process each time one or more of the
following events occur:
■ a new calendar is created
■ the work pattern for an existing calendar has changed, such as different
working days or hours
■ new exceptions have been applied to an existing calendar, such as the addition
or deletion of a public holiday
To run this process, complete the following steps:

13-6 Oracle Project Resource Management Implementation and Administration Guide

 Maintaining Schedules

1. Navigate to the Submit Request screen.

2. Choose Submit and select either PRC: Generate Calendar Schedule for a Single
Calendar or PRC: Generate Calendar Schedule for a Range of Calendars.
3. Enter the calendar name. If you are running the process for a range of calendars,
enter the starting and ending calendar names, or leave blank to process all
calendars.
4. Click Submit.

Updating Schedules and Timelines to Reflect a New Calendar

Availability data is transformed schedule data. This schedule data is used for
displaying graphical schedule timelines. It is also used for searches, calculating
utilization, and viewing non-graphical availability and overcommitment
information.
When the calendar for a resource changes, you need to run two processes to update
the availability data. You must first run the PRC: Generate Calendar Schedules
administrative process in order to reflect the new calendar in the schedules of the
resources, requirements, and assignments as is appropriate. Then, you can run a
process called PRC: Rebuild Resource Timeline to reflect the change in calendar and
resource availability in the timeline. This process rebuilds the availability data of
one or more resources incorporating changes made to the calendar or schedule.
To run this process, complete the following steps:
1. Navigate to the Submit Request screen.
2. Choose Submit and select either PRC: Rebuild Resource Timeline for a Single
Resource or PRC: Rebuild Timeline for a Range of Resources.
3. Enter the resource name. If you want to run the process for a range of resources,
enter the starting and ending resource names, or leave the fields blank to run
the process for all resources.
4. Click Submit.

Maintaining Your Data 13-7

Maintaining Utilization Values

Maintaining Utilization Values

The utilization screens provide totals on your resource utilization hours. In order to
view updated totals, you must run a batch process called PRC: Generate Utilization
on a regular basis. This request contains processes which create summary amounts
for both forecast and actual utilization. The forecast totals are derived from the
resource schedules. The actual totals are derived from actual submitted timecards.
To run this process, complete the following steps:
1. Navigate to the Submit Request screen.
2. Choose Submit > Request Set > PRC: Generate Utilization.
3. Enter the desired Actuals date range.
A default value for the Actuals From Date is entered. This default value is the
start date of the first period of the year in which the system date belongs. You
can change this date as appropriate for your needs.
4. Enter the desired Forecast date range.
A default value for the Forecast From Date is entered. This default value is the
start date of the first period of the year in which the system date belongs. You
can change this date as appropriate for your needs.
5. Enter the desired summary method for your organization.
The summary method offers two choices: Incremental or Refresh. The
Incremental method updates existing totals. The Refresh method deletes the
organization summary totals and re-calculates the new organization summary
totals. Incremental is the default value.

Note: If you have made any changes to the default reporting

organization hierarchy, you should select Refresh.

6. Click Submit.

13-8 Oracle Project Resource Management Implementation and Administration Guide

 Maintaining Forecast Information

Maintaining Forecast Information

Oracle Project Resource Management creates forecast information based on
assignments and requirements every time the schedule is created. Each day of an
assignment is treated as a potential forecast transaction and is considered for
forecast calculation based on the defined calculation period such as GL Period or PA
Period. An error is generated for each assignment that does not have a defined
calculation period.
These transactions are excluded from the project forecast values during the forecast
generation process. You can review and correct these forecast exceptions through
the following two processes:
■ PRC: List Forecast Exceptions
■ PRC: Process Forecast Exceptions

Running a List of Forecast Exceptions

The PRC: List Forecast Exceptions process produces a report listing all requirement
and assignment forecast items that are excluded from the project forecast. The
requirement and assignment forecast items appearing on this report have either
experienced a processing error or determined not to be valid items for the project
forecast.
To run this process, complete the following steps:
1. Navigate to the Submit Request screen.
2. Choose Submit > PRC: List Forecast Exceptions.
3. Enter the desired organization.
4. Enter the desired forecast date range.
5. Click Submit.

Maintaining Your Data 13-9

Maintaining Forecast Information

Reprocess Forecast Exceptions

After you run your list of exceptions and make the appropriate corrections, you
want to update your forecast amounts to include the corrected transactions. A
process called PRC: Process Forecast Exceptions evaluates eligible forecast items
and recreates the item for inclusion in the project forecast. Eligibility criteria for
forecast items are as follows:
■ forecast item date is between the specified forecast from and to date parameters
If the forecast item is not included in the current project forecast, a new forecast
item is created for that period. If the forecast item has been previously summarized,
the item is reversed and the rate is recalculated.
To run this process, complete the following steps:
1. Navigate to the Submit Request screen.
2. Choose Submit > PRC: Process Forecast Exceptions.
3. Enter the desired organization.
4. Enter the desired forecast date range.
5. Click Submit.

13-10 Oracle Project Resource Management Implementation and Administration Guide

 14
Overview of the Predefined Workflows

With Oracle Workflow, you can set up automated approval and notification
processes. The workflow processes depend on actions, such as a status change to
trigger the steps of the process. You can customize the messages and approval
system using the Oracle Workflow Builder.
The implementation of Oracle Project Resource Management includes default
workflow processes. Most of these workflow processes are used for updating
information and are invisible to your users. Others are specifically for providing
communication among your users, and you can modify them as appropriate for
your business.
This chapter explains the following workflow processes:
■ Initiating Deferred Workflow Processes
■ Assignment Approval Workflow Process
■ Candidate Workflow Processes
For more information on defining and modifying workflow processes and
modifying client extensions, refer to the following sources:
■ Chapter 13, "Integration with Other Oracle Applications," in the Oracle Projects
User Guide
■ Chapter 19, "Client Extensions," in the Oracle Projects User Guide
■ Oracle Workflow Guide, Release 2.5.2

Overview of the Predefined Workflows 14-1

Initiating Deferred Workflow Processes

Initiating Deferred Workflow Processes

Deferred workflow processes handle time-consuming tasks that can be automated
and placed in the background so that users can continue working in the application
without waiting for the requested task to complete online. For example, applying
the requirements of a team template to a project uses a deferred workflow process
and when the task is completed, a notification is sent to the user who initiated the
action.
These deferred workflow processes need at least one background engine to monitor
background activities in order to ensure consistent processing. Therefore, you must
submit a request to enable a concurrent program for workflow background
processing. Only a user with system administrator responsibilities can run the
Workflow Background Process.

Available Item Types

The following item types exist in the Workflow Background Process for Project
Resource Management:
■ PA Project Assignment: This process controls the routing of project assignment
approvals.
■ PA Apply Team Template: This process handles the task of applying a team
template to a project.
■ PA Candidate Notification Process: This process notifies candidates when they
are nominated or withdrawn.
■ PA Mass Assignment Transaction Workflow: This process handles the creation
of assignments when a mass assignment request is submitted.
■ PA Overcommitment Notification Processes: This process notifies users when
assignments cause overcommitments.
■ PA Project Forecasting Workflow: This process generates the forecast for a
project.
■ PA HR Related Updates Workflow: This process synchronizes Oracle HRMS
data with Project Resource Management data.
■ PA Mass Assignment Approval: This process handles the routing of approvals
for mass assignments.
■ PA Advertisements Workflow: This process sends out the advertisement
notifications and e-mails.

14-2 Oracle Project Resource Management Implementation and Administration Guide

 Initiating Deferred Workflow Processes

Recommended Process Scheduling Parameters

You can schedule concurrent processes either for all item types included in the
Workflow Background Process in a single request submission, or schedule each item
type in individual requests. For a single request submission, leave the Item Type
parameter blank. However, if you leave this parameter blank, the Workflow
Background Process will run for all item types across all Oracle applications and
may affect performance of the process.
The following table lists the recommended configuration for scheduling the
Workflow Background Process for the Project Resource Management item types:

Parameters Request 1 Request 2 Request 3

Repeat Every 10 minutes 24 hours 3 days
Minimum Threshold Leave blank Leave blank Leave blank
Maximum Threshold Leave blank Leave blank Leave blank
Process Deferred Yes No No
Process Timeout No Yes No
Process Stuck No No Yes
Apply the Interval From the From the From the
completion of completion of completion of
the prior run the prior run the prior run
Increment Date Leave blank Leave blank Leave blank

This configuration demonstrates three concurrently scheduled requests of the

Workflow Background Process.
To submit a request, complete the following steps:
1. Navigate to the Submit Requests form.
2. Submit the Workflow Background Process concurrent program as a request.
3. Specify the item type and other parameters as appropriate.
4. Schedule the process to repeat itself at appropriate intervals.
For more information on submitting and scheduling the workflow processes, see:
■ "Submitting a Request" in the Oracle Applications Users Guide
■ "Setting Up Oracle Workflow" in the Oracle Workflow Guide

Overview of the Predefined Workflows 14-3

Assignment Approval Workflow Process

Assignment Approval Workflow Process

This workflow process begins when an assignment is created for a resource and is
submitted for approval by a person that does not have the authority to approve the
resource assignment. This workflow process progresses as the status of the
assignment changes. The approvers for this process can include the staffing
manager and the resource manager. Upon approval or rejection, FYI notifications
are sent to the resource, the resource manager, staffing manager, and the project
manager.
The predefined status flows for assignment approval are:
■ Working -> Submitted -> Approved
■ Working -> Submitted -> Rejected -> Requires Resubmission -> Submitted ->
Approved
Actions invoke changes in the assignment approval status. The following table
describes how the default assignment approval workflow changes the status based
on actions:

Action Status Change

Assignment is created Working
Assignment is submitted for approval Submitted
Assignment is approved Approved
Assignment is cancelled Cancelled
Assignment is rejected Rejected
Assignment is changed Working
Assignment is resubmitted and the changes do not require Approved
approval
Assignment is resubmitted and the changes require approval Submitted
Rejected assignment is changed Requires
Resubmission

The following changes on an assignment require an approval:

■ a change in duration because it affects the schedule and availability of the
resource, such as any extension, shortening or moving the start dates forward
■ a change in work type because it affects billability or utilization percentage

14-4 Oracle Project Resource Management Implementation and Administration Guide

 Assignment Approval Workflow Process

You can change the order of the status flow for your business using these
predefined statuses and creating your own processes. For more information, see
"Assignment Approval Workflow Item Type and Processes" later in this chapter.
The automated Oracle Workflow-based approval process is enabled if the
assignment approval status Submitted has been workflow-enabled. Oracle
Workflow FYI notifications for Approved and Rejected statuses are enabled if
Workflow is enabled for the assignment approval status of Approved or Rejected.
If you do not enable the workflow-based approval process, assignments retain the
Submitted status until a user with authority over the resources manually logs in and
approves or rejects each assignment. Due to the enforcement of project security, the
person logging in should also have authority over the project in order to approve or
reject a given assignment. The approver can only be the primary contact or the
resource manager.

Assignment Approval Workflow Item Type and Processes

The assignment approval workflow process includes one predefined workflow item
type: PA: Project Assignments. This item type includes the following workflow
processes:
■ PA: Project Assignment Approval - main approval process
■ PA: Assignment Approval Notification - approval notification process
■ PA: Assignment Rejection Notification - rejected notification process
■ PA: Assignment Cancellation Notification - cancelled notification process
These processes activate based on the status of the assignment. The following table
provides the default workflow setup of these statuses:

Workflow Workflow
Enable Success Failure
Status Workflow Workflow Process Status Status
Working N None None None
Submitted Y PA: Project Assignment Approved Rejected
Approval
Approved Y PA: Assignment Approval None None
Notification
Cancelled Y PA: Assignment None None
Cancellation Notification

Overview of the Predefined Workflows 14-5

Assignment Approval Workflow Process

Workflow Workflow
Enable Success Failure
Status Workflow Workflow Process Status Status
Rejected Y PA: Assignment Rejection None None
Notification
Requires N None None None
Resubmission

You can view or modify these statuses through the Define Statuses form. You can
create your own workflow processes to override these default processes or modify
the workflow setup. If you choose to create your own workflow processes, you
must specify the item type and process name against the appropriate predefined
assignment approval statuses provided in the table above.

Assignment Approval Workflow Notification Messages

The following table displays the notification messages used by the workflow
processes. You can modify these messages as appropriate for your business
approval processes.

Message Description Type Recipients Comments

Notify Notifies the Response All chosen None
Approval recipient to required approvers
required approve the
approval request
with links to the
assignment details
and the schedule of
the resource
Notification Notifies the FYI only ■ Resource Any comments by the
of recipient that the approvers are suppressed
■ Resource
assignment approval request in the notification to the
Manager
approval has been approved resource.
■ Staffing
Manager
■ Project
Manager

14-6 Oracle Project Resource Management Implementation and Administration Guide

 Assignment Approval Workflow Process

Message Description Type Recipients Comments

Notification Notifies the FYI only ■ Resource All comments by the
of recipient that the approvers are suppressed
■ Resource
assignment approval request in the notification to the
Manager
rejection has been rejected resource.
■ Staffing
Manager
■ Project
Manager

For more information on defining notification messages, refer to the Oracle Workflow
Guide.

Assignment Schedule Statuses

Requirement and assignment statuses are referred to as assignment schedule
statuses because they reflect the status of the schedule for particular days. The
following table provides the default settings for these statuses:

User Status System Status Success Status Failure Status

Proposed Provisional Confirmed Rejected
Provisional Provisional Confirmed Rejected
Confirmed Confirmed None None
Cancelled Cancelled None None
Rejected Cancelled None None

Using the default settings, when a provisional assignment is approved, the status on
the assignment is changed to Confirmed. If the provisional assignment is rejected,
then the status of the assignment is changed to Rejected.
Assignment schedule statuses do not launch the approval workflow and you cannot
enable workflow processes on these statuses. However, you can change the default
workflow success and failure statuses for each provisional assignment schedule
status.

Overview of the Predefined Workflows 14-7

Assignment Approval Workflow Process

Note: You cannot define these settings for any cancelled system
statuses.

The schedules and timelines reflect all Confirmed and Provisional assignments.
Therefore, the provisional assignment schedule status must be set to a confirmed
status upon the completion of an approval process whether manual or automated
through Oracle Workflow. Since all assignment schedule statuses are user-defined,
you must specify the success and failure statuses for each user-defined Provisional
status.

Assignment Approval Workflow Extensions

Client extensions relating to the approval of assignments are as follows:
■ Assignment Approval Changes Extension
■ Assignment Approval Notification Extensions
This section covers each extension providing detail on the package and related
functions and procedures. For more information on client extensions, see Chapter
19, "Client Extensions," in the Oracle Projects User Guide.

Assignment Approval Changes Extension

This client extension enforces the following conditions to determine whether or not
an approval is required for an assignment:
■ Change in Duration
Any extension, shortening, or changing the dates of an assignment requires
approval as it effects the schedule and availability of the resource.
■ Change in Work Type
Any change in the work type on an assignment can have an effect on the
billability and utilization percentage of the resource and therefore, requires
approval.
Oracle Project Resource Management provides a template package called PA_
CLIENT_EXTN_ASGNMT_APPRVL. If you choose to write your own extensions,
print out the following files first. These files are located in the Oracle Project
Resource Management admin/sql directory:
■ PARAAPCB.pls

14-8 Oracle Project Resource Management Implementation and Administration Guide

 Assignment Approval Workflow Process

This file contains the procedures that you can modify to implement the
extension.
■ PARAAPCS.pls
This file contains the specifications of the extension package. If you create
procedures outside of the predefined procedure within the PA_CLIENT_EXTN_
ASGNMT_APPRVL package, you must also modify this file to include those
new procedures.
This package has a function called IS_ASGMT_APPR_ITEMS_CHANGED. This
function can return a VARCHAR2 value of either Y or N. The description of the data
type for this function are listed in the following table:

Parameter Name Data Type Description Mandatory

P_ASSIGNMENT_ID NUMBER The identifier of the assignment Yes

Assignment Approval Notification Extensions

The circulation of notifications is controlled by the predefined workflow processes.
These processes use workflow extensions to provide the lists of contacts for each
notification. The client extensions obtain the list of default contacts (recipients) from
the workflow process and makes any modifications to the list that the user may
have specified through the Oracle Project Resource Management application. The
end result is a customized list of recipients for the notification or approval request
which the workflow process uses.
Oracle Project Resource Management provides a template package called PA_
CLIENT_EXTN_ASGNMT_WF. If you choose to write your own extensions, print
out the following files first. The files are located in the Oracle Project Resource
Management admin/sql directory:
■ PARAWFCB.pls
This file contains the procedures that you can modify to implement the
extension.
■ PARAWFCS.pls
This file contains the specifications of the extension package. If you create
procedures outside of the predefined procedure within the PA_CLIENT_EXTN_
ASGNMT_WF package, you must also modify this file to include those new
procedures.

Overview of the Predefined Workflows 14-9

Assignment Approval Workflow Process

The description of the USERS_LIST_TBLTYP parameters for this package are listed
in the following table:

Parameter Name Data Type Description Mandatory

USER_NAME VARCHAR2 The workflow user Yes
name of the approver
PERSON_ID NUMBER The person ID of the Yes
approver
TYPE VARCHAR2 The type of user, such as Yes
RESOURCE_
MANAGER or
PRIMARY_CONTACT
ROUTING_ORDER NUMBER The order in which the No
approvals should be
For FYI notification
submitted
recipients, this value is
ignored since such
notifications are sent
to all recipients at the
same time.

You can modify the following package procedures as appropriate for your business
approval processes:
■ Generate_Assignment_Approvers
This procedure generates a list of approvers for the assignment. Oracle Project
Resource Management sends the list of default approvers to this procedure. The
procedure then makes any user-requested changes and provides a modified list
accordingly. If no user-requested changes exist, then the default list of
approvers is used by the workflow process.
Approvers added through this process are not visible on the Assignment
Approver page. However, users can see the name of the current approver on the
Assignment Details page.
The following table provides a list of the parameters for this procedure and the
details for each parameter:

Parameter Name Type Data Type Description

P_ASSIGNMENT_ID IN NUMBER The unique identifier of
the assignment

14-10 Oracle Project Resource Management Implementation and Administration Guide

 Assignment Approval Workflow Process

Parameter Name Type Data Type Description

P_PROJECT_ID IN NUMBER The unique identifier of
the project
P_IN_LIST_OF_RECIPIENTS IN References the Input list of notification
USERS_LIST_ recipients
TBLTYP
X_OUT_LIST _OF_ OUT References the Output list of
RECIPIENTS USERS_LIST_ notification recipients
TBLTYP
X_NUMBER_OF_RECIPIENTS OUT NUMBER Number of recipients

■ Generate_NF_Recipients
This client extension procedure generates a list of recipients for the various
notifications. Oracle Project Resource Management sends the list of default
approvers to this procedure. The procedure then makes any user-requested
changes and provides a modified list accordingly. If no user-requested changes
exist, then the default list of recipients is used by the workflow process. This
client extension procedure is used by the following FYI notifications:
– Assignment Approval Notification
– Assignment Rejection Notification
– Assignment Cancellation Notification
The following table provides a list of the parameters for this procedure and the
details for each parameter:

Parameter Name Type Data Type Description

P_ASSIGNMENT_ID IN NUMBER The unique identifier of
the assignment
P_PROJECT_ID IN NUMBER The unique identifier of
the project
P_NOTIFICATION_TYPE IN VARCHAR2 Type of notification;
valid values are:
■ APPROVAL_FYI
■ REJECTION_FYI

Overview of the Predefined Workflows 14-11

Assignment Approval Workflow Process

Parameter Name Type Data Type Description

P_IN_LIST_OF_RECIPIENTS IN References the Input list of notification
USERS_LIST_ recipients
TBLTYP
X_OUT_LIST _OF_ OUT References the Output list of
RECIPIENTS USERS_LIST_ notification recipients
TBLTYP
X_NUMBER_OF_RECIPIENTS OUT NUMBER Number of recipients

■ Set_Timeout_And_Reminders
This client extension procedure provides the reminder parameters, such as the
waiting period between reminders and the number of reminders before the
workflow process is cancelled.
The following table provides a list of the parameters for this procedure and the
details for each parameter:

Parameter Name Type Data Type Description

P_ASSIGNMENT_ID IN NUMBER The unique identifier of
the assignment
P_PROJECT_ID IN NUMBER The unique identifier of
the project
X_WAITING_TIMES OUT NUMBER The maximum amount
of time to wait before
sending a reminder
X_NUMBER_OF_REMINDERS OUT NUMBER The maximum number
of reminders to send
before aborting the
process

14-12 Oracle Project Resource Management Implementation and Administration Guide

 Candidate Workflow Processes

Candidate Workflow Processes

Oracle Project Resource Management has two predefined notification workflow
processes relating to a status change on candidates. These optional processes are:
■ New Candidate
As a candidate is nominated for a requirement, the candidate is initially given a
status of Pending Review. This status invokes a notification process. This
process notifies the resource, the manager of the resource, and their staffing
manager of the nomination. The person that nominated the candidate does not
receive a notification. Therefore, if the nomination was made by the resource,
resource manager, or staffing manager, then that person is excluded from the
notification process.
■ Candidate Declined
When a resource is declined as a candidate on a project, the status of the
candidate is changed to any user status with a system status of Declined. This
status initiates a notification process. This process notifies the candidate, the
manager of the resource, and their staffing manager of the change in status.
However, a notification is not sent to the person who declined the candidate, if
that person is one of these individuals.
An active candidate nomination of a resource on a requirement is automatically
declined and the candidate status is set to a Declined status if either one of the
following scenarios occurs:
■ A requirement is cancelled.
■ If the resource is no longer a valid Projects resource due to reasons such as
HR termination, transfer to a non-expenditure project organization, or the
resource’s organization is no longer a valid project expenditure
organization.
If the workflow PA: HR Related Updates Workflow is enabled, a notification is
sent to the resource and the resource manager informing them about the
declined candidate nomination.

Candidate Notification Workflow Extension

The candidate workflow processes use a template package called PA_CLIENT_
EXTN_CAND_WF. If you choose to write your own extensions, print out the
following files first. The files are located in the Oracle Project Resource Management
admin/sql directory:

Overview of the Predefined Workflows 14-13

Candidate Workflow Processes

■ PARCWFCB.pls
This file contains the procedures that you can modify to implement the
extension.
■ PARCWFCS.pls
This file contains the specifications of the extension package. If you create
procedures outside of the predefined procedure within the PA_CLIENT_EXTN_
CAND_WF package, you must also modify this file to include those new
procedures.

The description of the USERS_LIST_TBLTYP parameters for this package are listed
in the following table:

Parameter Name Data Type Description Mandatory

USER_NAME VARCHAR2 The workflow user name of the Yes
approver
PERSON_ID NUMBER The person ID of the approver Yes
TYPE VARCHAR2 The type of user, such as Yes
RESOURCE_MANAGER or
PRIMARY_CONTACT
ROUTING_ORDER NUMBER The order in which the No
approvals should be submitted For FYI notification
recipients, this
value is ignored
since such
notifications are
sent to all recipients
at the same time.

This package contains one procedure. You can modify the following package
procedure as appropriate for your business notification processes:
■ Generate_NF_Recipients
This client extension procedure generates a list of recipients for the various
notifications. Oracle Project Resource Management sends the list of default
approvers to this procedure. The procedure then makes any user-requested
changes and provides a modified list accordingly. If no user-requested changes
exist, then the default list of recipients is used by the workflow process. This
client extension procedure is used by the following FYI notifications:
– Candidate Nominated Notification

14-14 Oracle Project Resource Management Implementation and Administration Guide

 Candidate Workflow Processes

– Candidate Declined Notification

The following table provides a list of the parameters for this procedure and the
details for each parameter:

Parameter Name Type Data Type Description

P_PROJECT_ID IN NUMBER The unique identifier of
the project
P_ASSIGNMENT_ID IN NUMBER The unique identifier of
the assignment
P_CANDIDATE_NUMBER IN NUMBER The unique identifier of
the candidate
P_NOTIFICATION_TYPE IN VARCHAR2 Type of notification;
valid values are:
■ PENDING_
REVIEW_FYI
■ DECLINED_FYI
P_IN_LIST_OF_RECIPIENTS IN References the Input list of notification
USERS_LIST_ recipients
TBLTYP
X_OUT_LIST _OF_ OUT References the Output list of
RECIPIENTS USERS_LIST_ notification recipients
TBLTYP
X_NUMBER_OF_RECIPIENTS OUT NUMBER Number of recipients

Overview of the Predefined Workflows 14-15

Candidate Workflow Processes

14-16 Oracle Project Resource Management Implementation and Administration Guide

 A
Implementation Steps Checklist

The Oracle Projects products include Oracle Projects Costing, Oracle Projects
Billing, and Oracle Project Resource Management. Each of these products require a
set of implementation steps, some of which are optional. Since these products share
functionality and data, this appendix provides checklists that include all the tasks to
complete the implementation of all three products.
This appendix covers the following topics:
■ Overview of the Implementation Environment
■ Implementation Considerations
■ Overview of the Oracle Projects Implementation Checklists
■ Oracle Projects Implementation Checklist
■ Oracle Applications Implementation Checklist for Oracle Projects Integration

Implementation Steps Checklist A-1

Overview of the Implementation Environment

Overview of the Implementation Environment

Prior to beginning the implementation process, you should define Oracle
Applications responsibilities and users for the implementation. Oracle Projects
provides a predefined super user responsibility for each of the three related
applications as follows:
■ Projects Costing Super User
■ Projects Billing Super User
■ Project Resource Management Super User
You can assign this responsibility to users as appropriate for your implementation
needs. For more information, see "Defining a Responsibility" in the Oracle
Applications System Administrator’s Guide.

Oracle Applications Implementation Wizard

If you are implementing more than one Oracle Applications product, you can use
the Oracle Applications Implementation Wizard to coordinate your setup activities.
the Implementation Wizard guides you through the setup steps for the applications
you have installed, suggesting a logical sequence that satisfies cross-product
implementation dependencies and reduces redundant setup steps. The wizard also
identifies steps that can be completed independently, by several teams working in
parallel, to help you manage your implementation process most efficiently.
You can use the implementation wizard as a resource center to see a graphical
overview of setup steps, read online help for a setup activity, and to open the
appropriate setup window. You can also document your implementation for future
reference or review using the wizard to record your comments for each step.
For more information, refer to the Oracle Applications Implementation Wizard
User’s Guide.

Setting Up Underlying Oracle Applications Technology

The setup steps in the Oracle Projects Implementation Checklist guide you through
implementing the parts of Oracle Applications specific to the Oracle Projects
products. The Oracle Applications Implementation Wizard guides you through the
entire Oracle Applications setup, including system administration. However, if you
do not use the Wizard, you must complete several other setup steps, including:
■ performing system-wide setup tasks such as configuring concurrent managers
and printers

A-2 Oracle Project Resource Management Implementation and Administration Guide

 Implementation Considerations

■ managing data security, which includes setting up responsibilities to allow

access to a specific set of business data and complete a specific set of
transactions, and assigning individual users to one or more of these
responsibilities
For more information, see Oracle Applications System Administrator’s Guide
Also, if your implementation uses Oracle Workflow to manage data changes, you
must set up Oracle Workflow processes. For more information, refer to the Oracle
Workflow User’s Guide. For information relating to the deferred or approval
processes in Project Resource Management, refer to Chapter 8, "Defining the Project
Environment".

Implementation Considerations
As you determine your implementation data, you should consider the
AutoAccounting feature if you are implementing Oracle Project Costing or Oracle
Project Billing. The AutoAccounting feature in Oracle Projects derives values for
account combinations based on project information for all accounting transactions
in Oracle Projects. Consequently, the way you organize your chart of accounts
affects your implementation data. For example, if you charge several expense
accounts for varied expenditures such as meals, travel and lodging, and airfare,
then you need to implement an expenditure type that corresponds to each expense
account. You can use most of the implementation data that you define for Oracle
Projects as inputs to the Auto Accounting rules that you define.
After you complete most implementation steps, you can submit reports to review
your work and confirm that you have successfully completed the step. For example,
after you complete entering Agreement types, you can submit the Agreement Types
Listing. See "Implementation Listings" in the Oracle Projects User Guide for more
information.
To aid you with your implementation of either Projects Costing or Projects Billing,
you can refer to "About Fremont Corporation: An Example of Setting Up Oracle
Projects" in Chapter 17 of the Oracle Project User Guide.

Note: Fremont Corporation may not have implemented all the

features available in the current release of Oracle Projects.

Implementation Steps Checklist A-3

Overview of the Oracle Projects Implementation Checklists

Overview of the Oracle Projects Implementation Checklists

Two checklists are provided for your implementation:
■ Oracle Projects Implementation Checklist
■ Oracle Applications Implementation Checklist for Oracle Projects Integration
Each checklist indicates, for each step, whether it is required, optional, or
conditional. Required indicates that the step is necessary for the implementation of
the product to be successful. Optional indicates that you can determine whether or
not the step applies to your particular implementation. Conditional indicates that
the step is required to use a feature of the product, and the related feature is
provided in the step description.
The implementation checklists summarize the steps for implementing products in
the Oracle Projects suite. You can implement any of the Projects products
individually. However, the following products are dependent on Oracle Projects
Costing:
■ Oracle Projects Billing
■ Oracle Activity Management Gateway
■ Oracle Project Connect
The checklists include setup steps for data that may be shared with other Oracle
Applications, but are required by the Oracle Projects products. If you have already
defined this information when setting up other Oracle Applications, you can skip
those steps. This shared data includes:
■ Set of Books
■ Employees and Organizations
■ Customers
Since some implementation steps build upon information you define in other
implementation steps, you should perform the steps in the order listed.

A-4 Oracle Project Resource Management Implementation and Administration Guide

 Oracle Projects Implementation Checklist

Oracle Projects Implementation Checklist

The following table provides the Oracle Projects implementation checklist:

Project
Step Project Project Resource
Number Step Description Costing Billing Management
Licensing
1. Set the profile option PA: Licensed to Use Project n/a Required n/a
Billing. See: PA: Licensed to Use Project Billing
(Oracle Projects User Guide)
2. Set the profile option PA: Licensed to Use Project n/a n/a Required
Resource Management.
3. Specify additional profile option values. See: Optional Optional Optional
Profile Options (in Chapter 17 of the Oracle Projects
User Guide)
Set of Books and Currencies
4. Define your set of books. See Oracle Applications Required Required Required
Set of Books (Oracle General Ledger User Guide)
5. Enable additional currencies that you plan to use. Conditional Conditional Conditional
See Currencies Window (Oracle General Ledger User
Guide)
Required to use multiple currencies.
Human Resources – Work Structures
6. Set the profile option HR: Cross Business Group. Conditional Conditional Conditional
See: HR: Cross Business Group (in Appendix B of
the Oracle Projects User Guide)
Required to use Cross Business Group Access.
7. Define locations. See Locations (in Chapter 17 of the Required Required Required
Oracle Projects User Guide)
8. Define organizations. See: Organizations (in Required Required Required
Chapter 17 of the Oracle Projects User Guide)
9. Define default operating unit for the project and Conditional Conditional Required
expenditure organizations. See Chapter 3,
"Establishing Your Enterprise Structure".

Implementation Steps Checklist A-5

Oracle Projects Implementation Checklist

10. Define organization hierarchies and global Required Required Required

organization hierarchies. See: Organization
Hierarchies (in Chapter 17 of the Oracle Projects User
Guide).
11. Specify a project burdening hierarchy for each Conditional Conditional Conditional
business group. See: Specifying Project Burdening
Hierarchies (in Chapter 17 of the Oracle Projects User
Guide).
12. Define job groups. See: "Define Job Groups" (Oracle Conditional Conditional Required
Projects 11i Release 11.5.3/Mini Pack B User Guide
Supplement) and "Define Job Groups" in Implementing
Oracle HRMS.
Required to process labor.
13. Define jobs. See: "Define Jobs" (in Chapter 17 of the Conditional Conditional Required
Oracle Projects User Guide) and "Define Jobs" in the
Implementing Oracle HRMS.
Required to process labor.
14. Define job levels. See "Defining Job Levels" n/a n/a Required
(Implementing Oracle HRMS).
15. Define job mapping. See: Job Mapping (in Chapter Conditional Conditional Required
17 of the Oracle Projects User Guide).
Required to use project jobs.
16. Define competencies. See: Competencies (Oracle n/a n/a Required
Human Resources Documentation Update for Patch
Numbers 1383905 and 1377992 Global
Competencies).
17. Define rating scales. See: "Define Rating Scales" n/a n/a Required
(Implementing Oracle HRMS).
18. Assign competencies to resources. See: "Assigning n/a n/a Required
Competencies" in Chapter 4, "Defining Your People".
Calendars for Schedule and Capacity Management
19. Define calendar types. See: "Defining Calendar Conditional Conditional Required
Types" in Chapter 8, "Defining Calendars and
Schedules".
20. Define calendar shift and shift patterns. See: Conditional Conditional Required
"Defining Shift and Shift Patterns" in Chapter 8,
"Defining Calendars and Schedules".

A-6 Oracle Project Resource Management Implementation and Administration Guide

 Oracle Projects Implementation Checklist

21. Define calendar exceptions. See: "Creating Calendar Conditional Conditional Required
Exceptions" in Chapter 8, "Defining Calendars and
Schedules".
22. Define calendars. See: "Creating a Calendar" in Conditional Conditional Required
Chapter 8, "Defining Calendars and Schedules".
23. Assign calendar shifts. See: "Assigning Shifts and Conditional Conditional Required
Exceptions to Calendar" in Chapter 8, "Defining
Calendars and Schedules".
24. Set the following profile options: Conditional Conditional Required
■ PA: Default Calendar
■ PA: Global Week Start Day
■ PA: Availability Calculation Period
■ PA: Percentage of Resource’s Capacity
■ PA: Availability Duration
See: Chapter 8, "Defining Calendars and Schedules".
25. Run calendar generation process PRC: Generate Conditional Conditional Required
Calendar Schedule for a Range of Calendars. See
Chapter 8, "Defining Calendars and Schedules".
26. Define default calendar for the project and Conditional Conditional Required
expenditure organizations. See Chapter 3,
"Establishing Your Enterprise Structure".
Employees
27. Define employees, including address, assignment, Required Required Required
job, and supervisor. See: Chapter 4, "Defining Your
People" and "Employees" and "Employee
Assignments" (in Chapter 17 of the Oracle Projects
User Guide)
28. Run project resource process PRC: Maintain Conditional Conditional Required
Project Resources. See: Chapter 4, "Defining Your
People" and "Understanding the Candidate Score
and the Automated Nomination Process" in
Chapter 7, "Setting Up Staffing Capabilities".
29. Initiate deferred workflow processes. See: Conditional Conditional Required
Chapter 13, "Maintaining Your Data".
The HR related updates performed by the workflow
processes are required for Actual Utilization.

Implementation Steps Checklist A-7

Oracle Projects Implementation Checklist

Implementation Options and Accounting Periods

30. Set the profile option PA: Enable Enhanced Period Conditional Conditional Conditional
Processing. See: Enhanced Period Processing Setup
and Implementation (Oracle Projects 11i Family Pack I
(Release 11i.PJ_PF.I) Documentation Supplement).
31. Define implementation options. See: Required Required Required
Implementation Options (Oracle Projects User Guide)
and Enhanced Period Processing Setup and
Implementation (Oracle Projects 11i Family Pack I
(Release 11i.PJ_PF.I) Documentation Supplement).
32. Define PA periods. See: PA Periods (Oracle Projects Required Required Required
User Guide).
33. Set the status of GL periods. See: Enhanced Period Conditional Conditional Conditional
Processing Setup and Implementation (Oracle
Projects 11i Family Pack I (Release 11i.PJ_PF.I)
Documentation Supplement).
Expenditure Setup
34. Set the profile option PA: AP Discount Interface Conditional Conditional n/a
Start Date. See: AP Discount Interface Enhancement
Setup and Implementation (Oracle Projects 11i Family
Pack I (Release 11i.PJ_PF.I) Documentation Supplement).
35. Define expenditure categories. See: Expenditure Required Required Conditional
Categories (Oracle Projects User Guide).
Required if you use financial forecasting.
36. Define revenue categories. See: Revenue Categories Required Required Conditional
(Oracle Projects User Guide).
Required to use financial forecasting.
37. Define units. See: Units (Oracle Projects User Guide.) Required Required n/a
38. Define expenditure types. See: Expenditure Types Required Required Conditional
(Oracle Projects User Guide).
Required to use financial forecasting.
39. Define non-labor resources. See: Non-Labor Conditional Conditional n/a
Resources (Oracle Projects User Guide).
Required to use Usages.
40. Define transaction sources. See: Transaction Sources Conditional Conditional n/a
(Oracle Projects User Guide).
Required to use Transaction Import.

A-8 Oracle Project Resource Management Implementation and Administration Guide

 Oracle Projects Implementation Checklist

41. Implement transaction control extension. See: Optional Optional n/a

Transaction Control Extensions (Oracle Projects User
Guide).
42. Implement AutoApproval extension. See: Optional Optional n/a
AutoApproval Extension (Oracle Projects User Guide).
Non-Labor Costing Setup
43. Define cost rates for expenditure types. See: Cost Conditional Conditional n/a
Rates for Expenditure Types (Oracle Projects User
Guide).
44. Define usage cost rate overrides. See: Usage Cost Optional Optional n/a
Rate Overrides (Oracle Projects User Guide).
Labor Costing Setup
45. Define compensation rules. See: Compensation Conditional Conditional Conditional
Rules (Oracle Projects User Guide).
Required to process labor.
46. Define employee cost rates. See: Employee Cost Conditional Conditional Conditional
Rates (Oracle Projects User Guide).
Required to process labor.
47. Define labor cost multipliers. See: Labor Cost Optional Optional n/a
Multipliers (Oracle Projects User Guide).
48. Implement labor costing extension (advanced Optional Optional Optional
implementation step). See: Labor Costing Extensions
(Oracle Projects User Guide).
49. Implement labor transaction extension (advanced Optional Optional n/a
implementation step). See: Labor Transaction
Extensions (Oracle Projects User Guide).
50. Implement overtime processing (advanced Optional Optional n/a
implementation step). See: Overview of
Implementing Overtime (Oracle Projects User Guide).
51. Implement the overtime calculation extension. See: Optional Optional n/a
Overtime Calculation Extension (Oracle Projects User
Guide).
Budget Setup
52. Define additional budget types. See: Budget Types Conditional Conditional n/a
(Oracle Projects User Guide).
Required to use budgeting.

Implementation Steps Checklist A-9

Oracle Projects Implementation Checklist

53. Define budget entry methods. See: Budget Entry Conditional Conditional n/a
Methods (Oracle Projects User Guide).
Required to use budgeting.
54. Define budget change reasons. See: Budget Change Optional Optional n/a
Reasons (Oracle Projects User Guide).
55. Define resource lists. See: Resources and Resource Conditional Conditional n/a
Lists (Oracle Projects User Guide).
Required to use budgeting.
56. Implement budget calculation extension. See: Optional Optional n/a
Budget Calculation Extensions (Oracle Projects User
Guide).
57. Implement budget verification extension. See: Optional Optional n/a
Budget Verification Extension (Oracle Projects User
Guide).
58. Implement budget workflow extension. See: Optional Optional n/a
Budget Workflow Extension (Oracle Projects User
Guide).
Burden Costing Setup
59. Define cost bases and cost base types. See: Cost Conditional Conditional Conditional
Bases and Cost Base Amount Types (Oracle Projects
User Guide).
Required to use burdening.
60. Define burden cost codes. See: Burden Cost Codes Conditional Conditional Conditional
(Oracle Projects User Guide).
Required to use burdening.
61. Define burden structures. See: Burden Structures Conditional Conditional Conditional
(Oracle Projects User Guide).
Required to use burdening.
62. Define burden schedules. See: Burden Schedules Conditional Conditional Conditional
(Oracle Projects User Guide).
Required to use burdening.
63. Implement the Burden Costing extension. See: Optional Optional Optional
Burden Costing Extension (Oracle Projects User
Guide).
Project Billing Setup

A-10 Oracle Project Resource Management Implementation and Administration Guide

 Oracle Projects Implementation Checklist

64. Specify Receivables System Options. See: Optional Required Optional

Specifying System Options (Oracle Projects User
Guide).
65. Set up output tax codes for customer invoices. See: n/a Required n/a
Setting Up Invoice Line Tax Codes (Oracle Projects
User Guide).
66. Define billing cycles. See: Billing Cycles (Oracle n/a Required n/a
Projects User Guide).
67. Implement billing cycle extension (advanced n/a Optional n/a
implementation step). See: Billing Cycle Extension
(Oracle Projects User Guide).
68. Define payment terms. See: Payment Terms (Oracle n/a Required n/a
Projects User Guide).
69. Define agreement types. See: Agreement Types n/a Required n/a
(Oracle Projects User Guide).
70. Define bill rate schedules. See: Bill Rate Schedules Conditional Conditional Conditional
(Oracle Projects User Guide).
Required if your Transfer Price Schedules or Project
Billing setup are based on Rates.
71. Define invoice formats. See: Invoice Formats (Oracle n/a Required n/a
Projects User Guide).
72. Define credit types. See: Transfer Pricing (Oracle n/a Required n/a
Projects User Guide).
73. Define event types. See: Event Types (Oracle Projects n/a Conditional n/a
User Guide).
74. Assign event types for cost-to-cost revenue. See: n/a Conditional n/a
Assigning Event Types for Cost-to-Cost Revenue
(Oracle Projects User Guide).
75. Define customers. See: Customers (Oracle Projects Optional Required Optional
user Guide).
76. Implement Percent Complete Revenue Accrual and n/a Conditional n/a
Invoicing. See: Setup Requirements for Percent
Complete Revenue and Invoicing (Oracle Projects
User Guide).
77. Implement labor billing extension. See: Labor n/a Optional Optional
Billing Extensions (Oracle Projects User Guide).
78. Implement billing extensions. See: Billing n/a Optional n/a
Extensions (Oracle Projects User Guide).

Implementation Steps Checklist A-11

Oracle Projects Implementation Checklist

79. Implement automatic invoice approve/release n/a Optional n/a

extension. See: Automatic Invoice Approve/Release
Extension (Oracle Projects User Guide).
80. Implement AR transaction type extension. See: AR n/a Optional n/a
Transaction Type Extension (Oracle Projects User
Guide.)
81. Implement the output tax extension. See: Output n/a Optional n/a
Tax Extension (Oracle Projects User Guide).
82. Implement Revenue-Based Cost Accrual extension. n/a Optional n/a
See: Revenue-Based Cost Accrual (Oracle Projects
User Guide).
83. Implement cost accrual billing extension. See: Cost n/a Optional n/a
Accrual Billing Extension (Oracle Projects User
Guide).
84. Implement customer invoice printing strategy. See: n/a Optional n/a
Determining Your Invoice Printing Method (Oracle
Projects User Guide).
Role Setup
85. Define role lists. See: Chapter 6, "Defining Project Optional Optional Required
Roles".
86. Define roles and role types. See: Chapter 6, Optional Optional Required
"Defining Project Roles" and "Project Roles" in the
Oracle Projects User Guide.
87. Define project roles for organizations. See: Project Optional Optional Optional
Organization Roles (Oracle Projects Documentation
Update Notes, Family Pack J (11i.PJ_PF.J)).
Project Staffing
88. Define requirement, candidate, assignment n/a n/a Required
approval, and assignment scheduling statuses. See:
"Setting Up Staffing Capabilities".

A-12 Oracle Project Resource Management Implementation and Administration Guide

 Oracle Projects Implementation Checklist

89. Set the following profile options: n/a n/a Required

■ PA: Starting Requirement Status
■ PA: Starting Assignment Status
■ PA: Default Filled Requirement Status
■ PA: Default Starting Candidate Status
■ PA: Cancelled Requirement's Candidate Status
■ PA: Invalid Resource Candidate Status
See: Chapter 7, "Setting Up Staffing Capabilities".
90. Define advertisement rules and run the PRC: n/a n/a Optional
Perform Action Rules concurrent process. See:
Chapter 7, "Setting Up Staffing Capabilities".
91. Run the PRC: Automated Candidate Search n/a n/a Optional
process for automated candidate nomination. See:
Chapter 13, "Maintaining Your Data".
92. Setup Discoverer reporting. See: Chapter 12, n/a n/a Optional
"Setting Up for Reporting Capabilities".
93. Define team templates. See: "Creating and n/a n/a Optional
Applying Team Templates" in Oracle Project
Resource Management online help.
94. Define staffing priority codes. n/a n/a Optional
Project Setup
95. Define project statuses. See: "Setting Up the Optional Optional Optional
Predefined Project Status Controls" in Chapter 9,
"Defining the Project Environment" and "Statuses" in
the Oracle Projects User Guide.
96. Define additional class categories and class codes. Optional Optional Optional
See: Project Classifications (Oracle Projects User
Guide).
97. Define service types. See: Service Types (Oracle Required Required Required
Projects User Guide).
98. Define project customer relationships. See: Project Optional Required Optional
Customer Relationships (Oracle Projects User Guide).
99. Define contact types. See: Contact Types (Oracle Optional Optional Optional
Projects User Guide).

Implementation Steps Checklist A-13

Oracle Projects Implementation Checklist

100. Define probability lists. See: "Establishing Optional Optional Optional

Probability Information" in Chapter 9, "Defining the
Project Environment" and "Probability Lists" in the
Oracle Projects User Guide.
101. Define project types. See: Project Types (Oracle Required Required Required
Projects User Guide).
102. Define project templates. See: Project Templates Required Required Required
(Oracle Projects User Guide).
103. Create project list views. See: Customizable Project n/a n/a Optional
List (Oracle Projects 11i Family Pack I (Release 11i.PJ_
PF.I) Documentation Supplement).
104. Implement project verification extension. See: Optional Optional Optional
Project Verification Extension (Oracle Projects User
Guide).
105. Implement project workflow extension. See: Project Optional Optional Optional
Workflow Extension (Oracle Projects User Guide).
106. Implement verify organization change extension. Optional Optional Optional
See: Verify Organization Change Extension (Oracle
Projects User Guide).
107. Configure a project home page. See: Configurable n/a n/a Optional
Project Home (Oracle Projects 11i Family Pack I
(Release 11i.PJ_PF.I) Documentation Supplement).
This step includes defining a shortcut menu,
creating a project home page layout, and associating
the project home page layout with a project. This
step is optional because a default shortcut menu and
layout are provided.
Project and Organizational Security
108. Define security profiles and global security Conditional Conditional Conditional
profiles. See: Define Security Profiles (Oracle Projects
11i Release 11.5.3/Mini-Pack B User Guide Supplement)
and Define Security Profiles (Implementing Oracle
HRMS). See also: Chapter 5, "Configuring Your
Organization Security".
Required to restrict organization, responsibility and
role access.
109. Define organization-based security. See: Conditional Conditional Optional
"Understanding Responsibility-Based Security" in
Chapter 5, "Configuring Your Organization
Security".

A-14 Oracle Project Resource Management Implementation and Administration Guide

 Oracle Projects Implementation Checklist

110. Define role-based security. See: "Understanding n/a n/a Optional

Role-Based Security" in Chapter 5, "Configuring
Your Organization Security".
111. Implement project and labor cost security Optional Optional Optional
extension. (advanced implementation step) See:
Project Security Extension (Oracle Projects User
Guide).
Inter-Project Billing: Global Setup
112. In Oracle Payables, define suppliers for the n/a Conditional n/a
provider operating units.
113. Define expenditure types for inter-project n/a Conditional n/a
Payables invoices. See Setup for Inter-Project Billing
(Oracle Projects User Guide).
Optional if you have completed project costing
setup.
114. Define customers in Oracle Receivables for the n/a Conditional n/a
receiver operating units. See Oracle Receivables User
Guide.
Required to use inter-project billing.
115. Define inter-project agreement types. See: Setup for n/a Optional n/a
Inter-Project Billing (Oracle Projects User Guide).
Optional if you have completed project billing setup.
116. Define inter-project billing cycles. See: Billing n/a Optional n/a
Cycles (Oracle Projects User Guide).
Optional if you have completed project billing setup.
117. Define inter-project invoice formats. See: Invoice n/a Optional n/a
Formats (Oracle Projects User Guide).
Optional if you have completed project billing setup.
118. Customize the Payables Open Interface Workflow n/a Optional n/a
so that you can override the default attributes for
currency conversion. See: Customizing the Payables
Open Interface Workflow (Oracle Projects User
Guide).
119. Define inter-project supplier types. See: Setup for n/a Optional n/a
Inter-Project Billing (Oracle Projects User Guide).
Inter-Project Billing: Operating Unit Setup

Implementation Steps Checklist A-15

Oracle Projects Implementation Checklist

120. Define internal billing implementation options. n/a Conditional Optional

See: Setup for Inter-Project Billing (Oracle Projects
User Guide).
Required to use inter-project billing.
121. Define supplier sites for internal suppliers. See: n/a Conditional n/a
Setup for Inter-Project Billing (Oracle Projects User
Guide).
Required for each receiver operating unit, if you are
using inter-project billing.
122. Define customer bill and ship sites for internal n/a Conditional n/a
customers. See: Defining Customer Bill and Ship
Sites for Internal Customers (Oracle Projects User
Guide).
Required for each receiver operating unit, if you are
using inter-project billing.
123. Define provider and receiver controls. See: Setup n/a Conditional n/a
for Inter-Project Billing (Oracle Projects User Guide).
Required to use inter-project billing.
124. In Oracle Receivables, define tax account codes for n/a Conditional n/a
the tax amounts on internal Receivables invoices.
See: Defining Automatic Accounting in Oracle
Receivables (Oracle Projects User Guide).
Required for each receiver operating unit, if you are
using inter-project billing.
125. Define tax codes for internal Payables invoices. n/a Conditional n/a
See: Setup for Inter-Project Billing (Oracle Projects
User Guide).
Required for each receiver operating unit, if you are
using inter-project billing.
126. Verify that Receivables and Payables share the n/a Conditional n/a
same tax codes. See: Setup for Inter-Project Billing
(Oracle Projects User Guide).
Required for each provider and receiver operating
unit pair, if you are using inter-project billing.
127. Modify the Supplier Invoice Charge Account n/a Conditional n/a
process. See: Setup for Inter-Project Billing (Oracle
Projects User Guide).
Required for each receiver operating unit, if you are
using inter-project billing.

A-16 Oracle Project Resource Management Implementation and Administration Guide

 Oracle Projects Implementation Checklist

128. Define receiver projects. See: Setup for Inter-Project n/a Conditional n/a
Billing (Oracle Projects User Guide).
Required to use inter-project billing.
129. Define provider projects. See: Setup for n/a Conditional n/a
Inter-Project Billing (Oracle Projects User Guide).
Required to use inter-project billing.
Cross Charge - Borrowed and Lent
130. Define transfer price rules. See: Defining Transfer Conditional Conditional n/a
Price Rules (Oracle Projects User Guide).
Required to use borrowed and lent processing.
131. Define transfer price schedules. See: Defining Conditional Conditional n/a
Transfer Price Schedules (Oracle Projects User Guide).
Required to use borrowed and lent processing.
132. Define cross charge implementation options for all Conditional Conditional n/a
operating units using borrowed and lent
processing. See: Defining Cross Charge
Implementation Options (Oracle Projects User Guide).
133. Define additional expenditure types for borrowed Optional Optional n/a
and lent processing. See: Expenditure Types (Oracle
Projects User Guide).
134. Define transaction sources for borrowed and lent Optional Optional n/a
processing. See: Defining Transaction Sources for
Cross Charge Processing (Oracle Projects User Guide).
135. Define provider and receiver controls. See: Conditional Conditional n/a
Defining Provider and Receiver Controls (Oracle
Projects User Guide).
136. Implement the cross charge client extensions. See: Optional Optional n/a
Cross Charge Client Extensions (Oracle Projects User
Guide).
Cross Charge - Intercompany Billing
137. Define transfer price rules. See: Defining Transfer Conditional Conditional n/a
Price Rules (Oracle Projects User Guide).
Required to use cross charge processing.
138. Define transfer price schedules. See: Defining Conditional Conditional n/a
Transfer Price Schedules (Oracle Projects User Guide).
Required to use cross charge processing.

Implementation Steps Checklist A-17

Oracle Projects Implementation Checklist

139. Define inter-company supplier types. See: Defining n/a Optional n/a
Cross Charge Implementation Options (Oracle
Projects User Guide).
140. In Oracle Payables, define suppliers for the n/a Conditional n/a
provider operating units.
Required to use intercompany billing,
141. Define supplier sites for internal suppliers. See: n/a Conditional n/a
Defining Supplier Sites for Internal Suppliers (Oracle
Projects User Guide).
142. Define customers in Oracle Receivables for the n/a Conditional n/a
receiver operating units. See: Oracle Receivables User
Guide.
143. Define customer bill and ship sites for internal n/a Conditional n/a
customers. See: Defining Customer Bill and Ship
Sites for Internal Customers (Oracle Projects User
Guide).
Required for each receiver operating unit, if you are
using intercompany billing.
144. Define intercompany billing expenditure types. n/a Optional n/a
See: Defining Expenditure Types for Cross Charge
Processing (Oracle Projects User Guide).
Optional if you have completed project billing setup.
145. Define intercompany billing invoice formats. See: n/a Optional n/a
Invoice Formats and About Invoice Formats for
Intercompany Billing (Oracle Projects User Guide).
Optional if you have completed project billing setup.
146. Define intercompany billing cycles. See: Billing n/a Optional n/a
Cycles (Oracle Projects User Guide).
Optional if you have completed project billing setup.
147. Define agreement types for cross charge n/a Optional n/a
processing. See: Defining Agreement Types for
Cross Charge Processing (Oracle Projects User Guide).
Optional if you have completed project billing setup.
148. Define internal transaction sources. See: Defining n/a Optional n/a
Transaction Sources for Cross Charge Processing
(Oracle Projects User Guide).
149. Customize the Payables Open Interface Workflow. Conditional Conditional Conditional
See: Customizing the Payables Open Interface
Workflow (Oracle Projects User Guide).

A-18 Oracle Project Resource Management Implementation and Administration Guide

 Oracle Projects Implementation Checklist

150. Implement the cross charge client extensions. See: n/a Optional n/a
Cross Charge Client Extensions (Oracle Projects User
Guide).

Cross Charge - Intercompany Billing: Operating Unit Setup

151. Define internal billing implementation options. n/a Conditional n/a
See: Defining Internal billing Implementation
Options (Oracle Projects User Guide).
Required to use intercompany billing.
152. Define a project type for intercompany billing n/a Conditional n/a
projects. See: Defining a Project Type for
Intercompany Billing Projects (Oracle Projects User
Guide).
Required for each provider operating unit, if you are
using intercompany billing.
153. Define project templates for intercompany billing n/a Conditional n/a
projects. See: Defining Project Templates for
Intercompany Billing Projects (Oracle Projects User
Guide).
154. Define intercompany billing projects. See: Defining n/a Conditional n/a
Intercompany Billing Projects (Oracle Projects User
Guide).
Required for each provider operating unit, if you are
using intercompany billing.
155. Define agreements for intercompany billing n/a Conditional n/a
projects. See: Defining Agreements for
Intercompany Billing Projects (Oracle Projects User
Guide).
Required for each provider operating unit, if you are
using intercompany billing.
156. Define provider and receiver controls. See: n/a Conditional n/a
Defining Provider and Receiver Controls (Oracle
Projects User Guide).
Required to use intercompany billing.
157. Define tax account codes for internal Receivables n/a Conditional n/a
invoices. See: Defining Tax Codes for Internal
Receivables Invoices (Oracle Projects User Guide).
Required for each provider operating unit, if you are
using intercompany billing.

Implementation Steps Checklist A-19

Oracle Projects Implementation Checklist

158. Define Payables tax codes to apply separate tax n/a Conditional n/a
distributions on internal Payables invoices. See:
Defining Tax Codes for Internal Payables Invoices
(Oracle Projects User Guide).
Required for each provider operating unit, if you are
using intercompany billing.
159. Verify that Receivables and Payables share the n/a Conditional n/a
same tax codes for internal invoices. See: Verify the
Receivables and Payables Share the Same Tax Codes
(Oracle Projects User Guide).
Required for each provider operating unit, if you are
using intercompany billing.
160. Modify the Supplier Invoice Charge Account n/a Conditional n/a
process. See: Modifying the Supplier Invoice Charge
Account Process (Oracle Projects User Guide).
Required for each provider operating unit, if you are
using intercompany billing.
161. Define cross charge setup information for projects n/a Conditional n/a
and tasks. See: Defining Cross Charge Setup (Oracle
Projects User Guide).
Allocations Setup
162. Define allocation rules. See: Defining Allocation Conditional Conditional n/a
Rules (Oracle Projects User Guide).
Required to use allocations.
AutoAllocations Setup
163. Create AutoAllocation sets. See: Creating Conditional Conditional n/a
AutoAllocation Sets (Oracle Projects User Guide).
Required to use AutoAllocations.
164. Set up Workflow for Allocations. See: Setting Up Conditional Conditional n/a
Workflow for Step-Down AutoAllocations (Oracle
Projects User Guide).
Required to use AutoAllocations.
165. Implement the Allocation Extensions. See: Optional Optional n/a
Allocation Extensions (Oracle Projects User Guide).
Utilization
166. Classify jobs with "Utilizable" flag. See Chapter 11, Required Required Required
"Implementing Resource Utilization".

A-20 Oracle Project Resource Management Implementation and Administration Guide

 Oracle Projects Implementation Checklist

167. Define utilization categories. See Chapter 11, Required Required Required
"Implementing Resource Utilization".
168. Define work types. See Chapter 11, "Implementing Required Required Required
Resource Utilization".
169. Define utilization options and choose your Required Required Required
reporting period. See Chapter 11, "Implementing
Resource Utilization".
170. Grant utilization and resource authority. See Required Required Required
Chapter 11, "Implementing Resource Utilization".
171. Set the profile options for utilization: Required Required Required
■ PA: Utilization Records Per Set
■ PA: Utilization Manager Default Period Type
■ PA: Utilization Manager Default Calculation
Method
■ PA: Resource Utilization Period Type
■ PA: Resource Utilization Calculation Method
■ PA: Utilization Calculation Begin Date
See: Chapter 11, "Implementing Resource
Utilization".
172. Associate application users with predefined Required Required Required
responsibilities. See Chapter 5, "Configuring Your
Organization Security".
173. Run the concurrent report set PRC: Generate Required Required Required
Utilization. See Chapter 13, "Maintaining Your
Data".
Financial Forecasting
174. Define forecasting options. See: Chapter 10, Conditional Conditional Optional
"Implementing Financial Forecasting".
Required to use financial forecasting.
175. Define expenditure categories. See: Expenditure Conditional Conditional Optional
Categories (Oracle Projects User Guide).
Optional if you have already defined expenditure
categories.
176. Define revenue categories. See: Revenue Categories Conditional Conditional Optional
(Oracle Projects User Guide).
Required to use financial forecasting.

Implementation Steps Checklist A-21

Oracle Projects Implementation Checklist

177. Define expenditure types. See: Expenditure Types Conditional Conditional Optional
(Oracle Projects User Guide).
Required to use financial forecasting.
178. Define compensation rules. See: Compensation Conditional Conditional Optional
Rules (Oracle Projects User Guide).
Required to use financial forecasting.
179. Define employee cost rates. See: Employee Cost Conditional Conditional Optional
Rates (Oracle Projects User Guide).
Required to use financial forecasting.
180. Implement labor costing extension. See: Labor Optional Optional Optional
Costing Extensions (Oracle Projects User Guide).
181. Define cost bases and cost base types. See: Cost Optional Optional Optional
Bases and Cost Base Amount Types (Oracle Projects
User Guide).
182. Define burden cost codes. See: Burden Cost Codes Optional Optional Optional
(Oracle Projects User Guide).
183. Define burden structures. See: Burden Structures Optional Optional Optional
(Oracle Projects User Guide).
184. Define burden schedules. See: Burden Schedules Optional Optional Optional
(Oracle Projects User Guide).
185. Define rate schedules. See: Bill Rate Schedules Conditional Conditional Conditional
(Oracle Projects User Guide)
Required to use financial forecasting.
Project Status Inquiry Setup
186. Define derived columns. See: Derived Columns for Optional Optional n/a
Project Status Inquiry (Oracle Projects User Guide).
187. Define displayed columns. See: Non-Default Optional Optional n/a
Configuration for Project Status Inquiry (Oracle
Projects User Guide).
188. Implement commitments from external systems. Optional Optional n/a
See Implementing Commitments from External
Systems (Oracle Projects User Guide).
189. Implement custom reporting strategy. See Custom Optional Optional n/a
Reporting Using Project Summary Accounts (Oracle
Projects User Guide).

A-22 Oracle Project Resource Management Implementation and Administration Guide

 Oracle Projects Implementation Checklist

190. Implement the commitment changes extension. See Optional Optional n/a
Commitment Changes Extension (Oracle Projects
User Guide).
191. Implement the project status inquiry extension. Optional Optional n/a
See Project Status Inquiry Extension (Oracle Projects
User Guide).
Capital Projects Extensions
192. Implement the Asset Assignment Extension. See: Optional n/a n/a
Asset Assignment Extension (Oracle Projects User
Guide).
193. Implement the CIP Grouping Extension. See: CIP Optional n/a n/a
Grouping Extension (Oracle Projects User Guide).
Additional Setup
194. Define descriptive flexfields. See: Descriptive Optional Optional Optional
Flexfields (Oracle Projects User Guide).
195. Define request groups for report and process Optional Optional Optional
security. See: Oracle Applications System
Administrator’s Guide.
196. Define additional users. See: Oracle Applications Optional Optional Optional
System Administrator’s Guide.
197. Define responsibilities for functional users. See: Optional Optional Optional
Security Profiles (Oracle Projects User Guide).
198. Assign Self-Service HR responsibility to users and Optional Optional Required
roles. See: Chapter 4, "Defining Your People".
199. Define frequently-used folders. See: Customizing Optional Optional Optional
the Presentation of Data (Oracle Applications User’s
Guide) and Administering Folders (Oracle
Applications System Administrator’s Guide). To see
which windows are folder-enabled, see Oracle
Projects Navigation Paths (Oracle Projects User
Guide).
AutoAccounting for Costs
ATTENTION: If you have a multiple organization installation, you must repeat these steps for each operating
unit.
200. Set up accounting for labor costs. See: Accounting Conditional Conditional n/a
for Labor Costs (Oracle Projects User Guide).

Implementation Steps Checklist A-23

Oracle Projects Implementation Checklist

201. Set up accounting for expense report costs. See: Conditional Conditional n/a
Accounting for Expense Report Costs (Oracle Projects
User Guide).
202. Set up accounting for usage costs. See: Accounting Conditional Conditional n/a
for Usage Costs (Oracle Projects User Guide).
203. Set up accounting for miscellaneous costs. See: Conditional Conditional n/a
Expenditure Type Classes (Oracle Projects User
Guide).
204. Set up accounting for burden transactions. See: Conditional Conditional n/a
Expenditure Type Classes (Oracle Projects User
Guide).
205. Set up accounting for WIP and Inventory costs, if Conditional Conditional n/a
you are using these expenditure type classes for
costs other than those originating in Oracle
Manufacturing and Oracle Inventory. See:
Expenditure Type Classes (Oracle Projects User
Guide).
206. Set up accounting for supplier invoice adjustment Conditional Conditional n/a
costs. See: Accounting for Supplier Invoice
Adjustment Costs (Oracle Projects User Guide).
207. Set up accounting for total burdened costs. See: Conditional Conditional n/a
Accounting for Burdened Costs (Oracle Projects User
Guide).
AutoAccounting for Revenue and Billing
ATTENTION: If you have a multiple organization installation, you must repeat these steps for each operating
unit.
208. Define AutoAccounting for cross charge n/a Conditional n/a
transactions processed for intercompany billing.
See: Defining AutoAccounting for Cross Charge
Transactions Processed for Intercompany Billing
(Oracle Projects User Guide).
209. Define AutoAccounting for provider cost n/a Optional n/a
reclassifications. See: Define AutoAccounting for
Provider Cost Reclassifications (Oracle Projects User
Guide).
210. Define AutoAccounting for borrowed and lent Conditional Conditional n/a
transactions. See: Defining AutoAccounting for
Borrowed and Lent Transactions (Oracle Projects User
Guide).

A-24 Oracle Project Resource Management Implementation and Administration Guide

 Oracle Projects Implementation Checklist

211. Set up accounting for labor revenue. See: n/a Conditional n/a
Accounting for Labor Revenue (Oracle Projects User
Guide.)
212. Set up accounting for expense report revenue. See: n/a Conditional n/a
Accounting for Expense Report Revenue (Oracle
Projects User Guide).
213. Set up accounting for usage revenue. See: n/a Conditional n/a
Accounting for Usage Revenue (Oracle Projects User
Guide).
214. Set up accounting for miscellaneous revenue. See: n/a Conditional n/a
Expenditure Type Classes (Oracle Projects User
Guide).
215. Set up accounting for burden transactions revenue. n/a Conditional n/a
See: Expenditure Type Classes (Oracle Projects User
Guide).
216. Set up accounting for inventory revenue. See: n/a Conditional n/a
Expenditure Type Classes (Oracle Projects User
Guide).
217. Set up accounting for work in process revenue. See: n/a Conditional n/a
Expenditure Type Classes (Oracle Projects User
Guide).
218. Set up accounting for supplier invoice revenue. n/a Conditional n/a
See: Accounting for Supplier Invoices Revenue
(Oracle Projects User Guide).
219. Set up accounting for event revenue. See: n/a Conditional n/a
Accounting for Event Revenue (Oracle Projects User
Guide).
220. Set up accounting for unbilled receivables, n/a Conditional n/a
unearned revenue, and receivables. See:
Accounting for Revenue and Invoices (Oracle Projects
User Guide.)
221. Define Invoice Rounding account. See: Invoice n/a Conditional n/a
Rounding (Oracle Projects User Guide).
222. Set up accounting for invoice write-offs. See: n/a Conditional n/a
Accounting for Revenue and Invoices (Oracle Projects
User Guide).

Implementation Steps Checklist A-25

Oracle Projects Implementation Checklist

Opportunity to Project Integration

223. Map organization roles. See: Mapping Organization Optional Optional Optional
Roles (Oracle Projects Documentation Update Notes,
Family Pack J (11i.PJ_PF.J)).
224. Map person roles. See: Mapping Person Roles Optional Optional Optional
(Oracle Projects Documentation Update Notes, Family
Pack J (11i.PJ_PF.J)).
225. Map probability values. See: Mapping Probability Optional Optional Optional
Values (Oracle Projects Documentation Update Notes,
Family Pack J (11i.PJ_PF.J)).
226. Set up opportunity classifications. See: Setting up Optional Optional Optional
Opportunity Classifications (Oracle Projects
Documentation Update Notes, Family Pack J (11i.PJ_
PF.J)).
227. Drill from Projects to Sales Online. See: Drilling Optional Optional Optional
from Projects to Sales Online (Oracle Projects
Documentation Update Notes, Family Pack J (11i.PJ_
PF.J)).

A-26 Oracle Project Resource Management Implementation and Administration Guide

 Oracle Applications Implementation Checklist for Oracle Projects Integration

Oracle Applications Implementation Checklist for Oracle Projects

Integration
The following checklist includes the setup steps for other Oracle Applications that
affect the integration of Oracle Projects with those applications. You should
understand the implications of integration with Oracle Projects as you perform
these setup steps for other Oracle Applications.
Refer to the Setup chapter in each product’s User Guide for comprehensive
implementation information for the product. You only need to complete the steps
for the applications that you are implementing with Oracle Projects.
The following table provides the Oracle Projects integration checklist:

Project
Step Project Project Resource
Number Step Description Costing Billing Management
Oracle Payables
1. Install and implement Oracle Payables. See: Oracle Conditional Conditional n/a
Payables User Guide
2. Define your Payables Options for expense reports. Conditional Conditional n/a
See: Payables Options (Oracle Projects User Guide).
3. Specify profile options for project-related invoice Conditional Conditional n/a
entry. See: Updating Profile Options for Integration
with Other Products (Oracle Projects User Guide).
4. Set up the Account Generator to generate the Conditional Conditional n/a
supplier invoice account. See: The Account
Generator in Oracle Projects (Oracle Projects User
Guide).
5. Define project-related distribution sets. See: Project Optional Optional n/a
Related Distribution Sets (Oracle Projects User Guide).
6. Implement the descriptive flexfield mapping Optional Optional n/a
extension. See: Descriptive Flexfield Mapping
(Oracle Projects User Guide).
Oracle Purchasing
7. Install and implement Oracle Purchasing. See: Conditional Conditional n/a
Oracle Purchasing User Guide

Implementation Steps Checklist A-27

Oracle Applications Implementation Checklist for Oracle Projects Integration

8. Specify profile options for project-related Conditional Conditional n/a

document entry. See: Updating Profile Options for
Integration with Other Products (Oracle Projects User
Guide).
9. Set up the Account Generator to generate the Conditional Conditional n/a
project-related accounts in Oracle Purchasing. See:
The Account Generator in Oracle Projects (Oracle
Projects User Guide).
Oracle Receivables
10. Install and implement Oracle Receivables. See: Conditional Conditional n/a
Oracle Receivables User Guide.
11. Specify system options for project invoice n/a Conditional n/a
processing. See: Specifying System Options (Oracle
Projects User Guide).
12. Define transaction types. See: Transaction Types for n/a Conditional n/a
Invoice Processing (Oracle Projects User Guide).
13. Specify profile options for project invoices. See: n/a Conditional n/a
Updating Profile Options for Integration with Other
Products (Oracle Projects User Guide).
14. Define Automatic Accounting in Receivables. See: n/a Conditional n/a
Automatic Accounting in Oracle Receivables (Oracle
Projects User Guide).
15. Define salespersons for sales credit. See: n/a Optional n/a
Salespersons and Credit Types (Oracle Projects User
Guide).
16. Set up tax codes for project invoices. See: Applying n/a Conditional n/a
Tax to Project Invoices (Oracle Projects User Guide).
17. Implement the Receivables installation override n/a Optional n/a
extension. See: Receivables Installation Override
(Oracle Projects User Guide).
Oracle Inventory
18. Install and implement Oracle Inventory. See: Conditional Conditional n/a
Oracle Inventory User Guide.
19. Define project-related transaction types in Oracle Conditional Conditional n/a
Inventory. See: Oracle Inventory User’s Guide.
Oracle Project Manufacturing

A-28 Oracle Project Resource Management Implementation and Administration Guide

 Oracle Applications Implementation Checklist for Oracle Projects Integration

20. Install and implement Oracle Project Conditional Conditional n/a

Manufacturing. See: Oracle Project Manufacturing
User’s Guide.
Oracle Workflow
21. Install and implement Oracle Workflow. See: Conditional Conditional Conditional
Oracle Workflow Guide.
22. Implement Project Workflow. See: Implementing Conditional Conditional Conditional
Project Workflow (Oracle Projects User Guide).
23. Implement Budget Workflow. See: Implementing Conditional Conditional n/a
Budget Workflow (Oracle Projects User Guide).
24. Implement Project Assignment Workflow. See: n/a n/a Required
Oracle Workflow Guide.
25. Implement project workflow extension. See: Optional Optional Optional
Project Workflow Extension (Oracle Projects User
Guide).
26. Implement budget workflow extension. See: Optional Optional n/a
Budget Workflow Extension (Oracle Projects User
Guide).
27. Implement Project Assignment Workflow n/a n/a Optional
extension. See:Chapter 14, "Overview of the
Predefined Workflows".
28. Implement Candidate Notification Workflow n/a n/a Optional
extension. See: Chapter 14, "Overview of the
Predefined Workflows".
Oracle Activity Management Gateway
29. Specify profile option for product licensing. See: Conditional Conditional n/a
Updating Profile Options for Integration with Other
Products (Oracle Projects User Guide).
30. Set up controls over imported data. See: Control Conditional Conditional n/a
Actions Window (Oracle Projects User Guide).
31. Set up source products. See: Source Products Conditional Conditional n/a
Window (Oracle Projects User Guide).
Oracle Internet Time
32. Install and implement Oracle Internet Time. See: Conditional Conditional n/a
Oracle Self-Service Time Implementation Guide.

Implementation Steps Checklist A-29

Oracle Applications Implementation Checklist for Oracle Projects Integration

33. Implement the pre-import and post-import Optional Optional n/a

extensions for Internet Time. See: Pre-Import Client
Extension for Internet Time and Post-Import Client
Extension for Internet Time (Oracle Projects User
Guide).
Oracle Cash Management
34. Install and implement Oracle Cash Management. Conditional Conditional n/a
See: Oracle Cash Management User Guide.
35. Implement Oracle Projects integration with Oracle Conditional Conditional n/a
Cash Forecasting. See: Integrating with Cash
Management (Oracle Projects User Guide).

A-30 Oracle Project Resource Management Implementation and Administration Guide

 Glossary

administrative assignment
Activity on an administrative project such as personal holiday, sick day, or jury
duty. Administrative assignments can also represent administrative work such as
duties on an internal project. Such assignments are charged to the administrative
project which is determined by the administration flag on the project type.

Analysis Workbook
A display of enterprise information in a graphical and tabular format. The Analysis
Workbook uses Discoverer to allow the user to modify the selection criteria, drill
into dimension hierarchies or link to other data elements.

assignment forecast item

The assignment forecast item is the smallest unit of forecasting information for the
assignment. In this entity, the smallest time unit is a day. Forecast items are created
for each day of every provisional and confirmed assignment for every billable
resource.

availability
The percentage of the availability of a resource to work on an assignment based on
the calendar of the resource, as well as any scheduled assignments for that resource.

billable resource
A resource that has a current billable job assignment. Billable jobs are defined in the
job definition screen where the Job Billability Flag is equal to Y.

Glossary-1
 Business View
Component of the application database that sorts underlying applications data into
an understandable and consolidated set of information. By masking the complexity
of the database tables, Business Views provide a standard set of interfaces to any
tool or application that retrieves and presents data to the user.

calendar
Working capacity defined by work patterns and calendar exceptions.

capacity
Capacity is based on a amount of schedulable hours from the calendar of a resource.
In the case of Labor, capacity is defined in work hours. The capacity of an
Organization is the sum total of the capacity of assigned resources.

competence
A technical skill or personal ability such as JAVA programming, ability to speak
another language, and project billing.

competence match
A numerical comparison of the competence of a resource to the mandatory and
optional competencies of a requirement

Cross Business Group Access (CBGA)

The ability to view data in operating units that are not associated with the current
operating unit’s business group.

Cross Business Group Access mode (CBGA mode)

An installation that has selected CBGA in the profile options is operating in CBGA
mode.

delivery assignment
Filled work position on a project.

dimension
Dimensions are used to calculate and monitor performance measures. Some of the
dimensions are organization and time.

Glossary-2
Discoverer
An Oracle Tool that allows users to retrieve data from a database. Discoverer
provides a user friendly method for creating database queries and displaying
information.

duration
The total number of days between the start date and end date of a team role.

effort
The total number of hours of a team role.

End User Layer

Component of discoverer that translates business view column names into industry
standard terminology and provides links between related data tables. Discoverer
accesses information through the End User Layer (EUL).

global hierarchy
An organization hierarchy that includes one or more business groups. A global
hierarchy can be used by installations that are in CBGA mode.

global security profile

An HR security profiles that is not associated with a business group. A global
security profile can secure organizations and people throughout a global (cross
business group) organization hierarchy.

HR job
In HRMS, the HR job for a resource (person) is the job linked to the primary
assignment of the person.

job group
A collection of jobs defined for a specific purpose. Jobs in a job group have the same
key flexfield structure.

Logical Data Model

A representation of the End User Layer. Available in a readable format, the Logical
Data Model gives the relationship between folders, allowing a Discoverer user to
determine the data elements needed for a specific analysis.

Glossary-3
 master job group
The job group that is used as an intermediate mapping group between other job
groups.

master job
A job in a master job group.

non-capacity work type

Work types assigned to forecast assignment items or actual expenditure items
reduce the total capacity of a given resource for the specified time period.

requirement
Unfilled work position on a project.

responsibility
A security feature of Oracle applications that groups forms and procedures under
the user application.

schedule
The working hours defined by the calendar and schedule exceptions.

Single Business Group Access mode (SBGA mode)

An installation that has selected No for the profile option HR: Cross Business
Group is operating in SBGA mode.

team role
Specific position on a project representing either requirements or assignments as
appropriate for the context in which it is used within the application.

utilization
A measure of how effectively a resource was used or is projected to be used.

utilization method
Capacity Utilization Method compares the actual (productive) work performed and
forecasted (productive) work to be performed by the resource to the capacity of a
resource.
Worked Hours Utilization Method compares the actual (productive) work performed
and forecasted (productive) work to be performed by the resource to the total
number of hours recorded (actuals) or assigned (forecasted) of a resource.

Glossary-4
utilization category
An implementation-defined category used for utilization reporting. This reporting
grouping combines one or more work types for organization and resource
utilization views.

utilization view
Utilization views enables you to measure a resource or organization utilization
percentage based on different groupings of work types.

work type
Work types are an implementation-defined classification of work performed. Work
types are used to classify both actual and forecast amounts. They differ from
expenditure types which are a classification of cost expended. Work types are also
grouped together by Utilization Categories.

worksheet
A specific grouping of information within an Analysis Workbook. A workbook is
composed of one or more worksheets, each with its own set of data and graphs.
Conceptually this is similar to the “sheets” and “workbook” concept within a
spreadsheet application.

unassigned time
The net amount of hours for a given period for which a resource does not have any
scheduled assignments (capacity hours minus scheduled hours.)

Glossary-5
Glossary-6
 Index
A attributes
calendar, 8-2
administrative assignment project, 9-2
creating an, 2-6
authority
administrative assignments
forecast, granting, 10-13
ownership, 2-2 organization, 5-3
administrative processes, 13-2
organizational level, 5-21
application
utilization, 11-17
process flows AutoAccounting feature, A-3
administrative assignment, creating an, 2-6
availability, 8-7
assignment, adding an, 2-6
Available Resource Hours (PAAVLRES)
requirement, creating a, 2-5 workbook, 12-58
requirement, filling a, 2-5
resource searching, 2-5
assigning B
competencies, 4-9 bill rate schedule
organizational authority, 5-22 job-based, 10-7
project calendars, 8-5 billable status, 13-4
resource calendars, 8-5 business group
shifts and exceptions to calendars, 8-4 definition, 3-2
assignment business views, list of, 12-42
adding an, 2-6
administrative
creating an, 2-6 C
changes requiring approval, 14-4 calendar
primary, for employee, 4-6 assigning a project, 8-5
assignment approval assigning a resource, 8-5
notification messages, 14-6 assigning shifts and exceptions, 8-4
workflow process, 14-4 attributes, 8-2
assignment approval statuses, 7-17 availability, 8-7
assignment schedule statuses, 14-7 changing, 13-6
assignments creating a, 8-4
administrative defaults, 8-5
ownership, 2-2 definition of, 8-2

Index-1
 timeline options, 8-9 creating
types, 8-2 administrative assignments, 2-6
calendar exceptions, 8-4 assignments, 2-6
Calendar Months folder, 12-17 calendars, 8-4
Calendar Years folder, 12-16 job structure, 3-5
calendar, changes to a, 8-4 requirements, 2-5
candidate
notification processes, 14-13
D
candidate statuses, seeded, 7-5
centralized deployment, 1-5 data security, managing, A-3
changing decentralized deployment, 1-5
calendars, 13-6 default operating unit, changing, 13-4
default operating unit, 13-4 default status controls, 7-2
job billable status, 13-4 deferred workflow processes, 13-2, 14-2
job levels, 13-3 deferred workflow processes, initiating, 14-2
job utilization, 13-4 defining
master calendar, 13-6 calendar exceptions, 8-4
organization hierarchy, 13-4 calendar types, 8-2
primary assignment, 13-5 competencies, 4-7
checklist, implementation, A-5 job groups, 3-5
checklist, integration implementation, A-27 job mapping, 3-5
checklists job-based bill rate schedule, 10-7
Discoverer postinstallation tasks, 12-3 job-based cost rate schedule, 10-6
Oracle Projects implementation, A-4 jobs, 3-5
classification locations, 4-6
Expenditure/Event organization, 3-3 organization default calendar, 8-5
HR organization, 3-3 organization hierarchies, 3-4
client extension organizational authority, 5-21
Assignment Approval Changes Extension, 14-8 primary assignment, 4-6
Assignment Approval Notification primary contact, 5-21
Extension, 14-9 project roles, 6-1
combination deployment, 1-5 project team, 2-2
competence structure, 4-7 role controls, 6-3
competencies role lists, 6-4
assigning, 4-9 role-based security, 5-5
defining, 4-7 roles, 6-5
examples of levels, 4-7 security strategy, 5-2
job-assigned, 4-9 shifts and shift patterns, 8-3
matching, 4-11 site default calendar, 8-5
requirement, 4-10 time periods, 10-8
role-assigned, 4-9 timeline options, 8-9
contractors, 4-5 unassigned time, 10-8
cost-based distribution rule, 10-4 utilization categories, 11-13
cost-rate schedule utilization strategy, 11-2
job-based, 10-6 work types, 11-14

Index-2
delivery team, 2-2 calculating revenue, 10-3
deployment method calculations, 10-3
centralized, 1-5 cost-based distribution rule, 10-4
combination, 1-5 event-based distribution rule, 10-5
decentralized, 1-5 implementation steps, 10-6
diagram maintaining, 13-9
project team, 2-2 process, 10-2
security check process flow, 5-24 profile option, 10-7
task flows, 2-3 security, 10-13
distribution rule unassigned time, 10-8
cost-based, 10-4 work-based distribution rule, 10-4
event-based, 10-5 financial forecast functionality, description of, 10-1
work-based, 10-4 Financial Organization Rollup Groups
folder, 12-32
Fiscal Quarter Numbers folder, 12-16, 12-33
E
Fiscal Years folder, 12-16, 12-33
employee folder
home address, 4-6 Calendar Months, 12-17
required information, 4-5 Calendar Years, 12-16
enterprise structure Financial Organization Rollup Groups, 12-32
business groups in the, 3-2 Fiscal Quarter Numbers, 12-16, 12-33
determining, 3-1 Fiscal Years, 12-16
organizations in the, 3-3 Lookup for Class Categories, 12-36
error causes Project Managers, 12-33
missing or invalid setup information, 13-2 Project Managers folder, 12-32
event-based distribution rule, 10-5 Required Project Hours by GL Period, 12-17
example Required Project Hours by GL Period: Team Role
competence levels, 4-7 Detail, 12-18
example of implementation, A-3 Required Project Hours by Global Week, 12-20
Expenditure/Event classification, 3-3 Required Project Hours by Global Week: Team
extended team, 2-2 Role Detail, 12-20
Required Project Hours by PA Period, 12-18
F Required Project Hours by PA Period: Team Role
Detail, 12-19
file Resource Capacity by GL Period, 12-21, 12-22
PARAAPCB.pls, 14-8 Resource Managers, 12-16
PARAAPCS.pls, 14-9 Resource Schedule by GL Period, 12-23
PARAWFCB.pls, 14-9 Resource Schedule by GL Period: Team Role
PARAWFCS.pls, 14-9 Detail, 12-24
PARCWFCB.pls, 14-14 Resource Schedule by Global Week, 12-27
PARCWFCS.pls, 14-14 Resource Schedule by Global Week: Team Role
filling Detail, 12-28
requirements, 2-5 Resource Schedule by PA Period, 12-25
financial business area, 12-14 Resource Schedule by PA Period: Team Role
financial forecast Detail, 12-26

Index-3
 Sales Pipeline by GL Period, 12-33 creating a, 3-5
Sales Pipeline by PA Period, 12-35 job-based bill rate schedule, 10-7
Staffing Organization Rollup Groups, 12-15 job-based cost rate schedule, defining, 10-6
forecast authority jobs, 3-5
menu, 5-19 billable status, 13-4
forecast authority, granting, 10-13 including in utilization calculations, 11-12
forecast exceptions, correcting, 13-10
forecast exceptions, list of, 13-9
K
forecast implementation options, 10-9
functions key features, application, 1-2
access by responsibility, 5-10
L
H levels of role-based security, 5-5
hierarchy list
organizational, 3-4 forecast exceptions, 13-9
HR locations, defining employee, 4-6
Cross Business Group profile option, 4-7 Lookup for Class Categories folder, 12-36
HR organization, 3-3
M
I maintaining resources, 13-5
implementation managing
checklist for Oracle Projects, A-4 data security, A-3
deployment method, 1-5 resource pool, 4-1
planning, 1-4 master calendar changes, 13-6
implementation checklist, integration with Oracle menus
Projects, A-27 forecast authority, 5-19
implementation checklist, Oracle Projects, A-5 project authority, 5-18
implementation example, A-3 project manager, 5-15
implementation wizard, A-2 resource, 5-17
installation base, 1-3 resource authority, 5-19
invalid setup information, 13-2 resource pool, 5-18
item type utilization authority, 5-19
PA: Project Assignments, 14-5 menus, seeded, 5-14
missing setup information, 13-2
J
O
job
groups, 3-5 operating unit
primary assignment, 3-5 default, 3-3
job competencies, 4-9 resource, 3-3
job levels, changing, 13-3 Oracle Discoverer
job mapping, 3-5 tasks checklist, 12-3
job structure Oracle Discoverer, install and setup tasks, 12-3

Index-4
Oracle forms changes, 13-1 option, 8-8, 8-10
Oracle HRMS tables, 1-4 PA: Project Assignments item type, 14-5
organization PA: Resource Utilization Calculation Method profile
authority level, 5-3 option, 11-20
default calendar, 8-5 PA: Resource Utilization Period Type profile
definition of, 3-3 option, 11-20
hierarchy, 3-4 PA: Starting Assignment Status profile option, 7-18
hierarchy, changing, 13-4 PA: Starting Requirement Status profile option, 7-3
HR, 3-3 PA: Utilization Calculation Begin Date profile
operating unit, default, 3-3 option, 11-20
Project Expenditure/Event, 3-3 PA: Utilization Manager Default Period Type profile
resource assignment, 4-5 option, 11-19
utilization view, 11-3 PARAAPCB.pls file, 14-8
organization manager responsibility, seeded PARAAPCS.pls file, 14-9
functions, 5-10 PARAWFCB.pls file, 14-9
organizational authority, 5-21 PARAWFCS.pls file, 14-9
assigning, 5-22 PARCWFCB.pls file, 14-14
levels of, 5-21 PARCWFCS.pls file, 14-14
organizational hierarchy, 3-4 percentage of probability, 9-3
Overcommitted Resource Hours (PAOVCRES) pipeline information, 9-3
workbook, 12-65 planning
overviews implementation, 1-4
setting up Oracle Projects, A-2 poplist changes, 13-1
PRC: Generate Calendar Schedules process, 13-6
PRC: Generate Utilization process, 13-8
P
PRC: Process Forecast Exceptions, 13-9
PA: Availability Calculation Period profile PRC: Rebuild Resource Timeline, 13-6
option, 8-8, 8-10 PRC: Rebuild Resource Timeline process, 13-6
PA: Availability Duration profile option, 8-10 predefined status flows, for assignment
PA: Cross-Project User - Update profile option, 5-4 approval, 14-4
PA: Cross-Project User - View profile option, 5-3 primary assignment
PA: Default Calendar profile option, 8-5 employee, 4-6
PA: Default Cancelled Assignment Status profile primary assignment, changing, 13-5
option, 7-18 primary contact, defining, 5-21
PA: Default Cancelled Requirement Status profile primary job, 3-5
option, 7-4 probability list, 9-3
PA: Default Filled Requirement Status profile process, 13-6
option, 7-4 PRC: Generate Calendar Schedules, 13-6
PA: Default Starting Candidate Status profile PRC: Generate Utilization, 13-8
option, 7-6 PRC: Process Forecast Exceptions, 13-9
PA: Forecasting Period Type profile option, 10-7 security check, 5-23
PA: Global Week Start Day profile option, 11-19 process flow
PA: Organization Utilization Default Calculation application, 2-5
Method profile option, 11-20 profile option
PA: Percentage of Resource Capacity profile HR: Cross Business Group, 4-7

Index-5
 PA: Availability Calculation Period, 8-8, 8-10 delivery, 2-2
PA: Availability Duration, 8-10 diagram, 2-2
PA: Cross-Project User - Update, 5-4 extended, 2-2
PA: Cross-Project User - View, 5-3 Projects Billing Super User, A-2
PA: Default Calendar, 8-5 Projects Costing Super User, A-2
PA: Default Cancelled Assignment Status, 7-18
PA: Default Cancelled Requirement Status, 7-4
R
PA: Default Filled Requirement Status, 7-4
PA: Default Starting Candidate Status, 7-6 reference sources, iv-xviii
PA: Forecasting Period Type, 10-7 reporting
PA: Global Week Start Day, 11-19 Available Resource Hours (PAAVLRES)
PA: Organization Utilization Default Calculation workbook, 12-58
Method, 11-20 business views, 12-42
PA: Percentage of Resource Capacity, 8-8, 8-10 Calendar Months folder, 12-17
PA: Resource Utilization Calculation Calendar Years folder, 12-16
Method, 11-20 financial business area, 12-14
PA: Resource Utilization Period Type, 11-20 Financial Organization Rollup Groups
PA: Starting Assignment Status, 7-18 folder, 12-32
PA: Starting Requirement Status, 7-3 Fiscal Quarter Numbers folder, 12-16, 12-33
PA: Utilization Calculation Begin Date, 11-20 Fiscal Years folder, 12-16
PA: Utilization Manager Default Period Lookup for Class Categories folder, 12-36
Type, 11-19 Overcommitted Resource Hours (PAOVCRES)
self-service environment options, 9-5 workbook, 12-65
profile options Project Managers folder, 12-32, 12-33
utilization, 11-19 Required Project Hours (PAREQPRJ)
project workbook, 12-45
attributes, 9-2 Required Project Hours by GL Period
project authority folder, 12-17
menu, 5-18 Required Project Hours by GL Period: Team Role
project environment, 9-1 Detail folder, 12-18
project manager, 5-7 Required Project Hours by Global Week
menu, 5-15 folder, 12-20
project manager responsibility, seeded Required Project Hours by Global Week: Team
functions, 5-10 Role Detail folder, 12-20
project manager role, 2-4 Required Project Hours by PA Period
Project Managers folder, 12-32 folder, 12-18
Project Resource Management Super User, A-2 Required Project Hours by PA Period: Team Role
Project Resource Management super user, 5-8 Detail folder, 12-19
Project Resource Management super user Resource Capacity by GL Period folder, 12-21,
responsibility, seeded functions, 5-13 12-22
project roles, defining, 6-1 Resource Managers folder, 12-16
project security structure, 5-1 Resource Schedule by GL Period folder, 12-23
project statuses, 9-3 Resource Schedule by GL Period: Team Role
project team Detail folder, 12-24
defining a, 2-2 Resource Schedule by Global Week

Index-6
 folder, 12-27 required information, 4-5
Resource Schedule by Global Week: Team Role searching, 2-5
Detail folder, 12-28 utilization view, 11-3
Resource Schedule by PA Period folder, 12-25 resource authority
Resource Schedule by PA Period: Team Role menu, 5-19
Detail folder, 12-26 Resource Capacity by GL Period folder, 12-21
Sales Pipeline by GL Period folder, 12-33 Resource Capacity by Global Week folder, 12-22
Sales Pipeline by PA Period folder, 12-35 Resource Capacity by PA Period folder, 12-22
Sales Pipeline Workbook (PASALPIP) resource manager, 5-7
workbook, 12-72 resource manager responsibility, seeded
Scheduled Resource Hours (PASCHRES) functions, 5-11
workbook, 12-51 resource manager role, 2-4
security, 12-44 Resource Managers folder, 12-16
staffing business area, 12-12 resource operating unit, 3-3
Staffing Organization Rollup Groups resource pool
folder, 12-15 benefits of, 4-2
reporting solution, 12-1 managing, 4-1
reporting time period, 11-16 menu, 5-18
Required Project Hours (PAREQPRJ) Resource Schedule by GL Period folder, 12-23
workbook, 12-45 Resource Schedule by GL Period: Team Role Detail
Required Project Hours by GL Period folder, 12-17 folder, 12-24
Required Project Hours by GL Period: Team Role Resource Schedule by Global Week folder, 12-27
Detail folder, 12-18 Resource Schedule by Global Week: Team Role
Required Project Hours by Global Week Detail folder, 12-28
folder, 12-20 Resource Schedule by PA Period folder, 12-25
Required Project Hours by Global Week: Team Role Resource Schedule by PA Period: Team Role Detail
Detail folder, 12-20 folder, 12-26
Required Project Hours by PA Period folder, 12-18 resource search
Required Project Hours by PA Period: Team Role job level-based, 3-6
Detail folder, 12-19 resources
requirement maintaining, 13-5
creating a, 2-5 responsibilities
filling a, 2-5 Oracle Applications, A-2
requirement statuses, seeded, 7-3 organization manager
requirements seeded functions, 5-10
competencies, 4-10 project manager, 5-7
resource seeded functions, 5-10
availability, 8-7 Project Resource Management super user, 5-8
changing primary assignment, 13-5 seeded functions, 5-13
contractor setup, 4-5 resource, 5-8
default functions, 5-8 resource manager, 5-7
home address, 4-6 seeded functions, 5-11
menu, 5-17 seeded, 5-6
missing information, 4-6 seeded function and menu access, 5-8
organization assignment, 4-5 staffing manager, 5-8

Index-7
 seeded functions, 5-12 candidate statuses, 7-5
team member menu and function access, 5-8
seeded functions, 5-12 menus, 5-14
responsibility function access, 5-10 organization manager responsibility
responsibility-based security, 5-3 functions, 5-10
role project manager responsibility functions, 5-10
controls, 6-3 Project Resource Management super user
defining a, 6-5 responsibility functions, 5-13
lists, 6-4 requirement statuses, 7-3
project manager, 2-4 resource manager responsibility functions, 5-11
resource manager, 2-4 responsibilities, 5-6
staffing manager, 2-4 responsibility function access, 5-10
team member, 2-4 roles, 5-5
role competencies, 4-9 staffing manager responsibility functions, 5-12
role-based security, 5-5 super user responsibility, A-2
levels, 5-5 team member responsibility functions, 5-12
roles self-service environment, defining, 9-5
enterprise, 5-5 shared data, implementation, A-4
seeded, 5-5 shift patterns, defining, 8-3
shifts and exceptions, assigning to calendars, 8-4
shifts, defining, 8-3
S
site default calendar, 8-5
Sales Pipeline by GL Period folder, 12-33 sources
Sales Pipeline by PA Period folder, 12-35 of reference, iv-xviii
Sales Pipeline Workbook (PASALPIP) staffing business area, 12-12
workbook, 12-72 staffing manager, 5-8
Scheduled Resource Hours (PASCHRES) staffing manager responsibility, seeded
workbook, 12-51 functions, 5-12
searching staffing manager role, 2-4
competence match, 4-11 Staffing Organization Rollup Groups folder, 12-15
job level-based, 3-6 standalone mode
resource, 2-5 utilization results, 11-1
security status controls, 7-2
diagram of, check process flow, 5-24 statuses
financial forecast, 10-13 assignment approval, 7-17
model comparison, 5-2 assignment schedule, 14-7
process, check, 5-23 candidate, 7-5
project role-based, 5-1 Change Project Probability status, 9-4
reporting, 12-44 profile options for, 7-3, 7-6, 7-18
responsibility-based, 5-1, 5-3 requirement, 7-3
role-based levels, 5-5 seeded project, 9-3
strategy, 5-2 statuses, definition of, 7-2
structure, 5-2 structure
seeded competence, 4-7
assignment approval statuses, 7-17 enterprise, 3-1

Index-8
 job, 3-5 Total Worked Hours, 11-2
of implementation guide, iv-xvii unassigned time tracking, 11-16
super user responsibility, seeded, A-2 work types, 11-14
system administration, A-2 utilization authority
menu, 5-19
T
tables V
Oracle HRMS, 1-4 version
Oracle Projects, 1-4 Self-Service Framework, 1-3
task flow diagram, 2-3
team member responsibility, seeded
W
functions, 5-12
team member role, 2-4 weighting percentage, 11-2
technology stack, 1-3 work-based distribution rule, 10-4
time periods, defining, 10-8 workbook
timeline, updating, 13-7 Available Resource Hours (PAAVLRES), 12-58
transactional reporting, 12-1 Overcommitted Resource Hours
(PAOVCRES), 12-65
Required Project Hours (PAREQPRJ), 12-45
U Sales Pipeline Workbook (PASALPIP), 12-72
unassigned time, tracking, 10-8, 11-16 Scheduled Resource Hours (PASCHRES), 12-51
updating schedules with calendar changes, 13-6 workflow process
user role assignment approval notification
project manager, 2-4 messages, 14-6
resource manager, 2-4 assignment approval, seeded processes, 14-5
staffing manager, 2-4 candidate declined, 14-13
team member, 2-4 candidate notification processes, 14-13
utilization Generate_Assignment_Approvers
Capacity Method, 11-2 procedure, 14-10
categories, 11-13 Generate_NF_Recipients procedure, 14-11,
changing job, 13-4 14-14
defining strategy, 11-2 new candidate, 14-13
forecast functionality, 11-16 seeded assignment approval, 14-4
functionality description, 11-1 Set_Timeout_And_Reminders procedure, 14-12
generating, 13-8 workflow processes, default, 14-1
granting, authority, 11-17 workflow processes, deferred, 14-2
method, 11-4
organization view, 11-3
profile options, 11-19
reporting, 11-5
reporting time period, 11-16
resource view, 11-3
specifying, jobs, 11-12
time periods, 11-3

Index-9
Index-10