An Oracle White Paper

March 2011
Project Performance Reporting
A Description of the Solution

PPR: A Description of the Solution
1
Executive Overview ........................................................................... 1
Introduction ....................................................................................... 1
Approach and Scope ..................................................................... 1
Scope ............................................................................................ 2
Other Resources ........................................................................... 2
Glossary of Terms ......................................................................... 3
Summarization Flow and Concurrent Requests ................................. 4
Summarization Programs Descriptions .......................................... 5
Project Performance Setup ................................................................ 8
Project Performance Setups .......................................................... 8
Current Reporting Period Page .................................................... 10
Data Flow ........................................................................................ 10
Solutions to Common Errors ............................................................ 12
Recommended Links ....................................................................... 16
PPR: A Description of the Solution
1
Executive Overview
This paper is intended to present the Project Performance Reporting (PPR) solution concepts and
common issues encountered and to describe basic techniques to resolve issues from a business
perspective.
Introduction
Using Project Performance Reporting
Oracle Project Management Project Performance Reporting features provides you with at-a-glance
comparison of actual and planned project results. You can view project performance in the areas of
effort, cost, profitability, earned value, billing and collections, or capital costs. PPR provides the ability
to report performance metrics for a project based on a user-configured resource hierarchy (resource
breakdown structure), as well as the financial structure of a project.
Reporting by Currency
You can view amounts in global, project, and project functional currencies. You have the option to
view project performance results in an additional currency by enabling a secondary global currency.
This means you can view critical project information in your local currency, business unit currency, and
your enterprise global currency.
Reporting by Period
You can view amounts based on the global calendar, project calendar, or a fiscal (GL) calendar. You
can view cost, profitability, and earned value amounts at the project level. This enables you to make
informed decisions to control project costs, generate revenue, and manage risks. Drill down to analyze
cost and profitability information by task, resource, and time. Identify the specific tasks and resources
that contribute to variances, and determine performance trends based on periodic (e.g., monthly)
amounts. You can view earned value information for tasks to understand how each task is performing
in terms of cost and schedule.
Approach and Scope
This whitepaper presents the process and steps you follow to summarize project performance data.
The Summarization Process flow outlines the concurrent requests you run to complete the process.
The use and purpose for each concurrent request are provided.
PPR: A Description of the Solution
2
The paper also includes a description of common issues encountered by customers using Project
Performance Reporting. This section helps you identify common problems you may encounter and
implement the appropriate solution.
Scope
This document covers Project Performance Reporting setup, basic summarization process flows, basic
Project Performance Reporting concepts and concludes with suggestions how to identify common
PPR issues.
Topics not covered in this document include:
Project performance measures and formulas (this information is available in Note 1166423.1;
comparative analysis for Project Status Inquiry (PSI) and Project Performance Reporting measures is
available in Note 828564.1)
Project Intelligence processes
Personalization
Data accumulation descriptions
Other Resources
This whitepaper is intended to supplement information provided in other Oracle documents:
Oracle Project Management User Guide provides details to setup and use PPR and project
performance management.
An Oracle White Paper, A Trouble Shooting Guide for Project Performance Reporting,
recommends setups and troubleshooting tips to help project managers use PPR to monitor projects.
Release 12.1.2 Transfer of Information Technical Overview: Support and Troubleshoot Project
Performance Reporting provides details of new features to help you streamline reporting data
creation, delete historical plans data and update project performance data.
Recommended Links
Links to helpful knowledge repository notes are listed in the final section

PPR: A Description of the Solution
3
Glossary of Terms
PHRASE ACRONYM MEANING
Work Breakdown Structure WBS The hierarchy of tasks used in the workplan structure
Financial Breakdown Structure FBS The hierarch of tasks used in financial plans, such as budgets and
forecasts
Resource Breakdown Structure RBS The hierarchy of resources used to report project results
Fully Shared Structure FSS The structure of WBS and FBS are identical and tasks carry both
workplan and financial information
Partially Shared Structure PSS Part or portion of the tasks and structure of the WBS are identified
as FBS tasks. Tasks that are shared carry both workplan and
financial information
Non-Shared No Mapping Structure NSNM The tasks and structure of WBS and FBS are completely different
and are not related in any manner
Non-Shared Task Based Mapping NSTBM The tasks and structure of WBS and FBS are completely different,
but tasks in the WBS are mapped to tasks in the FBS. Many
workplan tasks can be mapped to one financial task but not vice-
versa.
Split Structure One of the non-shared workplan structures (e.g., Non-Shared Not
Mapped or Non-Shared Task Based Mapping)
Inception To Date ITD Values are accumulated from the project start date to the reporting
date.
Period To Date PTD Values are accumulated from the first date of the project period to
the reporting date.
Summarization Data from actual project results (ie, costs and revenues) are
summarized for reporting and forecasting
Project Status Inquiry PSI A feature used to report project status and performance based on a
resource list (and not an RBS) and displayed in the project status
subtab
Unit Of Measurement UOM Defines the quantity used for an amount
Estimate to Completion ETC Planned Amount less Actual Amount with respect to the scheduled
project completion date
Physical Percent Complete PPC The percentage of completion for a task or project
Service Request SR A request registered with Oracle Support to get assistance with a
reported product issue
.
PPR: A Description of the Solution
4
Summarization Flow and Concurrent Requests
To summarize data for new projects, you must run the initial summarization concurrent processes. Then, through the project life, you run the
summarization update requests each period to collect actuals and progress. This Summarization Process flow describes the processes and the order
to run the concurrent request programs.
Summarization Process
Initial Summarization
Processes
Periodic Summarization
Processes
PRC: Load
Project and
Resource Base
Summaries
PRC: Load
Project
Performance Data
PRC: Update
Project
Performance Data
PRC: Launch
Project
Performance Data
PRC: Update
Project and
Resource Base
Summaries
PRC: Refresh
Project and
Resource Base
Summaries
PRC: Refresh
Project
Performance Data
PRC: Delete
Historical
Workplans and
Financial Plans
Performance
Problem?
Performance
Problem?
Problem with
Summarized
Data?
Problem with
Summarized
Data?
Summarization
Complete




PPR: A Description of the Solution
5
Summarization Programs Descriptions
CONCURRENT REQUEST WHEN TO USE THE CONCURRENT PROGRAM THE CONCURRENT PROGRAMS INTENDED PURPOSE
PRC: Load Project and
Resource Base
Summaries
Submit this program after you initially install or perform a
complete reinstall of either Oracle Projects PPR
This program extracts and summarizes actual cost and commitment amounts as well as revenue,
invoice, funding and backlog amounts to create a base summary of reporting data that is used by Oracle
Projects project performance reporting.
In order to improve performance, the process can be run for actuals or commitments only.
PRC: Load Project
Performance Data
Submit this program after you initially install or perform a
complete reinstall. You should also run the program if a
project has never been summarized in Performance
reporting before.
Submit after PRC: Load Project and Resource Base
Summaries
This program summarizes the data created by the PRC: Load Project and Resource Base Summaries
program. In addition, this program also performs the initial summarization of financial plan amounts for
reporting. Oracle Projects uses this information for project-level reporting on project performance
reporting, workplan, and financial plan pages. This program also summarizes the amounts that Oracle
Project Costing allocation programs use to distribute raw and burdened costs between and within
projects and tasks.
In order to improve performance, the process can be run for a particular operating unit and/or project
organization and/or project type as well as a range of projects.
PRC: Update Project and
Resource Base
Summaries
Submit this process periodically when you need to
summarize new transactions.
This program updates the base summary with changes in source transactions such as new time cards,
other new and modified costs, commitments, revenue, invoice, funding, effort and earned value.
In order to improve performance, the process can be run for actuals or commitments only.
PRC: Update Project
Performance Data
Submit this process periodically when you need to
summarize new transactions.
Run after PRC: Update Project and Resource Base
Summaries
This program uses the updated base summary data to further summarize new and incremental costs,
commitments and changes in the resource breakdown structure. Use this program to ensure that
project-level reporting is current and reflects changes in the source transactions and the resource
breakdown structure.
In order to improve performance, the process can be run for a particular operating unit and/or project
organization and/or project type as well as a range of projects.
PPR: A Description of the Solution
6
PRC: Launch Update
Project Performance
Data
Submit this process when there are a large number of
projects that need to be summarized in parallel.
This program divides and groups the projects into manageable batches before launching the update
program. It sends the batch name as a parameter to the PRC: Update Project Performance Data
(UPPD) program and launches the program automatically for each batch. The UPPD program
processes project performance data for only those projects that are part of the batch, thereby increasing
efficiency of daily processing.
In order to improve performance, the process can be run for a particular operating unit, number of
projects and number of batches. Additional parameters can be used to reduce system load while
performing incremental update of reporting data.
It is recommended to apply patch 8429101 or 9817761 depending upon your release version.

TROUBLESHOOTING SOLUTIONS
PRC: Refresh Project
and Resource Base
Summaries
Submit this program if you find inconsistencies in data for
one or more projects on project performance reporting,
workplan, and financial plan pages.
This program extracts and re-summarizes transaction data to replace the existing base summary data
for projects with duplicate, missing, or unreconciled amounts. This ensures that the base summary data
for specified projects correctly reflects the latest transaction amounts.
In order to improve performance, the process can be run for actuals or commitments only.
This process may take additional time to complete depending on the amount of project data to be
refreshed, so you should run it ONLY in case there are some data reconciliation issues. It should NOT
be run as a regular process.
PRC: Refresh Project
Performance Data
Submit this program for the same projects after the PRC:
Refresh Project and Resource Base Summaries program
completes successfully. To update plan summary amounts
with changes to the resource list for a project, run this
program without submitting the PRC: Refresh Project and
Resource Base Summaries program.
Run after PRC: Refresh Project and Resource Base
Summaries
This program re-summarizes the refreshed base summary data for specified projects to address data
inconsistencies such as duplicate, missing, or unreconciled summary amounts. In addition, this program
re-summarizes the base summary data for plan amounts to reflect changes in the resource list. If you
run this process for any project in a program, then this process automatically refreshes data for all
projects in the program hierarchy.
In order to improve performance, the process can be run for a particular operating unit, plan type,
transaction type and plan version.
This process may take additional time to complete depending on the amount of project data to be
refreshed, so you should run it ONLY in case there are some data reconciliation issues. It should NOT
be run as a regular process.
PPR: A Description of the Solution
7
PRC: Delete Historical
Workplans and Financial
Plans
Submit the process when you want to delete historical
published workplan and baselined financial plan versions
for which data is no longer needed.
The process will purge reporting data only and delete all the data for historical versions of workplans
and financial plans. Use this program to reduce data and improve summarization program performance.
This functionality is available through Patch 9038817. For more on this process please refer to Note
1174657.1

Using Summarization Programs
Parameters for summarization programs may be different in 11i and R12. The programs and process projects with the
pa_projects_all.pji_source_flag=Y. The summarization programs for projects using PSI (Project Status Inquiry) identify and process projects with a
null value for the pji_source_flag.
You do not have to run the summarization programs when publishing a workplan or base-lining a financial plan. When performing these tasks, the
summarization programs are initiated automatically. When the publishing or base-lining processes finish successfully, the summarized data is
available for the plan version.
When you add new tasks to a workplan, use the Process Update function from workplan tab shortcut menu or run the PRC: Process Project
Structure Updates concurrent request. The regular summarization update programs will summarize transactional data created for these new tasks.
The program PRC: Generate Asset Lines processes costs that have been summarized either through PSI or PPR routines which will impact
Capital Projects.
Program Summarization Requirements
In order for the program to have underlying projects amounts to roll up, the following conditions have to be met:
1. Program and projects share the same Resource Breakdown Structure.
2. Program and projects share the same Budget Type, there should be at least one baselined plan version at both program and subsequent
projects.
3. Plan type should be set up as Time Phased by PA or GL period. Time Phase=None plan types will not be rolled up to Program.

PPR: A Description of the Solution
8
Project Performance Setup
The amount of summarized data stored for a project grows over time. Once Project Performance
Setup options have been defined, only the setups for period options can be modified or changed.
Therefore, you should define PPR settings carefully and based on known best practices in order to
publish meaningful performance reports efficiently and avoid costly and time consuming
reconfiguration.
Project Performance Setups
Navigation path: SSWA Projects> Setup> Project Performance Setup
Planning Amount Allocation
When your fiscal (GL) calendar is monthly and your project (PA) calendar is based on weekly periods,
you can use the Daily Distribution method to allocate the monthly GL amounts evenly across the
weekly PA periods.
When you choose the Period Start Date method, Oracle Projects allocates the total monthly GL
amounts to the PA period in which the start date of the GL period lies. Similarly, by choosing the
Period End Date option, you can instruct the system to allocate the total monthly GL amounts to the
PA period in which the end date of the GL period lies.
Note: When you enable Daily Proration, the processes may create a large amount of data that could
impact processing time.
Currency
The following currency settings are based on a standard, common implementation.
VALUE SOURCE COMMENTS
Primary Global Currency BIS: Primary Currency Mandatory profile
Secondary Global Currency BIS: Secondary Currency Additional currency in which reporting will be performed
Transaction Currency Transaction in which currency
has been entered
Transaction Currency cannot be viewed on reporting
pages. Project Performance Reporting processes create
the data in reporting tables for this currency if enabled, but
there are no standard views for data in the transaction
currency.
Conversion Rate Date
By default, Oracle Projects converts planned amounts from one currency to another using the
exchange rate on the first day of the planning period. Alternatively, you can set up Oracle Projects to
convert amounts using the exchange rate on the last day of the planning period.
Current Reporting Periods
PPR: A Description of the Solution
9
You select a current reporting period option for the global (enterprise), project (PA), and fiscal (GL)
calendars for an operating unit. Based on your selection, Oracle Projects determines the current
reporting period to use for that calendar when reporting project performance. You can set the current
reporting period option for each calendar individually on the Project Performance Setup page.
CALENDAR TYPE AVAILABLE SETUP
Project (PA) Calendar Last Open Period
First Open Period
Last Closed Period
Prior Period
Current Period
Specific Period
Fiscal (GL) Calendar Last Open Period
First Open Period
Last Closed Period
Prior Period
Current Period
Specific Period
Global (Enterprise) Calendar Prior Period
Current Period
Specific Period
Data Processing Control
This setting controls the volume of data that is summarized.
DATA PROCESSING CONTROL SETUP WHAT THE SETUP ENABLES
Summarize data for defined time phase This checkbox allows to summarize data for the time phase that you define for
the workplan and financial plan version
Summarize data to view periodic analysis of
workplan
This checkbox allows to view summarized periodic workplan data in the Periodic
Analysis page
Control periodic summarized data creation for non-
current and non-original budgets during initial load
This checkbox allows to generate summarized periodic data only for current,
original budgets during the Initial Load summarization process

Data Processing Control enables you to:
Control the creation of PA or GL calendar types for a workplan when publishing the work plan.
Control the creation of Global, PA, or GL calendar types for financial plans during the baseline flow.
Control the creation of Global, PA, or GL calendar types for workplans and financial plans during
the summarization process.
Control the creation of summarized data when updating or refreshing project performance data by
primary global currency.
PPR: A Description of the Solution
10
Changing Setup for Project Performance Reporting Page
In order to change Project Performance Reporting setups, data must be purged from the system.
Therefore, you should modify PPR setups under the guidance of Oracle Support to avoid unnecessary
problems. Contact Oracle Support to obtain detailed instructions when you are required to change
setups.
Current Reporting Period Page
Navigation: SSWA Projects> Setup> Current Reporting Period
The Current Reporting Period setup page is only available for update when the Specific Period option
has been selected in Project Performance Setup page.
Predefined logic to derive current reporting period is based setup options chosen in the Project
Performance Setup page. For example, for calendar type GL, if setup option has been chosen as
CURRENT, then the current open GL period is current reporting period. If the setting is PRIOR,
then current reporting period is the period prior to the current open period. Current period will be
dependent on system date which is not recommended for change.
Note: You can manually define the current reporting period for your global, project, and fiscal
calendars only if you choose the Specific Period option for a calendar. If you choose any of the other
current reporting period options, or subsequently change to one of the other current reporting period
options after choosing the Specific Period option, then Oracle Projects uses the predefined system
logic for the selected option to derive the current reporting period. Oracle Projects ignores the period
you specify on the Set Current Reporting Period page.
Data Flow
This section describes the main tables required to process and transfer Project Performance Reporting
data.
MAIN PROJECT PERFORMANCE REPORTING TABLES
TABLE PROPERTIES
PJI_FP_TXN_ACCUM Permanently stores summarized data (for 3 calendars and 4 currencies) from cost and revenue
distribution tables
PJI_FP_TXN_ACCUM1 Permanently stores summarized data for commitments (for 3 calendars and 4 currencies)
PJI_FM_AGGR_FIN7 Stores incremental summarized data (3 calendars and 4 currencies) for cost and revenue distributions
tables and also commitments
PJI_FM_AGGR_ACT4 Stores summarized data (for 3 calendars and 4 currencies) from draft revenues, draft invoices, funding
and receivable amount due and paid
PJI_FP_XBS_ACCUM_F Stores complete (costs, commitments, revenue, workplan and financial plan) financial summarized data
(for 4 calendars, 5 currencies, WBS, RBS)
PJI_AC_XBS_ACCUM_F Stores complete (draft revenues, draft invoices, funding, receivable amount due and paid) activity
summarization data (for 4 calendars, 5 currencies and WBS)
PPR: A Description of the Solution
11
PJI_PJP_WBS_HEADER Stores WBS header information
Links each WBS version with its respective plan version
PJI_XBS_DENORM Stores de-normalized WBS structure
Stores the structure for each new WBS version.
PJI_PJP_RBS_HEADER Stores RBS header information
Links each RBS version with its respective plan version
PJI_RBS_DENORM Stores de-normalized RBS structure
Stores the structure for each new RBS version.

When you run Project Performance Reporting Summarization processes, data is selected from
Transaction Data tables, reorganized for calculations, and stored in Staging Data tables. Then staging
data is sliced to perform PPR calculations and the data is transferred to FACT tables to be processed
by the PRC: Delete Historical Workplans and Financial Plans concurrent programs.

PPR: A Description of the Solution
12
Solutions to Common Errors
Project Performance Reporting pages do not display complete data
When incorrect parameters are used to filter the data, Project Performance Reporting pages may not
display data. The following screenshot shows parameters that can be modified by users to change the
view of Project Performance data.
REPORTING OPTIONS AND PARAMETERS IN PERFORMANCE OVERVIEW PAGE:

Project Performance Reporting pages display partial data
When PPR processes are run partially or with incorrect parameters that cause the program to select an
incorrect set of data for summarization, pages may display only part of the data.

Current Reporting Period
(set for an organization)
Last time summarization was
performed for the project
Switch between
summarization
periods
Switch between Primary and
Secondary Reporting
Currency
PPR: A Description of the Solution
13
This screenshot displays an example of partial summarization in the Performance Overview page (Oracle Projects Release 12). Note that only
budgeting and forecasting data has been summarized. Costs and Revenue data has been left out.


PPR: A Description of the Solution
14



PPR: A Description of the Solution
15
If the page does not display all expected values insure that you have selected correct values in Details
and Parameters section, that source data for calculation exists, and that the summarization programs
have completed without error. If you determine that the issue is not caused by selecting incorrect
parameters, try following these troubleshooting steps in sequence:
Ensure that the initial load of Resource Base Summaries and Performance Data has been performed
as well as the incremental update
Run Refresh processes
Understanding Percent Complete values
Project Performance Reporting summarization processes calculate Percent Complete values based on
summarized data. In the Earned Value section of the reporting pages, the Physical %-Complete field is
the Financial Plan Physical %-Complete that is derived from the Financial Plan and is the same value
displayed in PSI.
When you setup your project with structures that share the same task structure (FS), the Physical %-
Complete value is the same for the workplan and financial plans. However when you setup other
structure types, such as Partially Shared (PSS), Non-Shared Task Based Mapping (NSTBM), and Non-
Shared No Mapping (NSNM), the workplan and financial plan may result in different &-Complete
values. In some cases, you may enter the %-Complete manually.
When you summarize data for projects that are included in programs:
Publishing a workplan initiates summarization so when publishing is finished, the workplan physical
%-Complete values are calculated.
If the workplan Physical %-Complete needs to be rolled to a Program, run PRC: Update Project
Performance Data process. This is the only program that summarizes the workplan Physical %-
Complete values.
Loading or Uploading Project Performance Data fails
If the programs PRC: Load Project Performance Data or PRC: Update Project Performance Data fail
with the error message: ORA-00054: resource busy and acquire with NOWAIT specified or timeout expired.
Refer to Note 1159004.1: When running Project Performance processes, there are table space issues.
Refer to Note 311745.1: This recommends details on parameters and how to perform initial load.
Please also note that the query in the above note will return estimated size. Query to calculate actual
table size taken by costs and revenue:
select segment_name, sum(bytes/1024/1024/1024)
from dba_extents
where owner='PA' and segment_type='TABLE' and
segment_name in ('PA_COST_DISTRIBUTION_LINES_ALL',
'PA_EXPENDITURE_ITEMS_ALL', 'PA_BUDGET_LINES',
'PA_PROJ_ELEMENT_VERSIONS', 'PA_CUST_REV_DIST_LINES_ALL',
'PA_CUST_EVENT_RDL_ALL')
PPR: A Description of the Solution
16
group by segment_name
Error: ORA-20000: index "PJI"."PJI_FP_AGGR_PJP1_N1"
When PRC: Load/Update Project Performance data fails with the error: ORA-20000: index
"PJI"."PJI_FP_AGGR_PJP1_N1" or partition of such index is in unusable state apply patch 9736946.
Error: A system error has occurred. Unable to locate: CURRENT PERIOD
When you are not using Maintain Common PA and GL periods (N: Projects Forms > Setup > System
> Implementation Options), the page will display the error: A system error has occurred. Unable to
locate: CURRENT PERIOD. Please contact your support representative. To fix this error, apply
Patch 9881954 (11i). At the time of publishing, the patch is only available on release 11i. Please raise a
SR with Oracle Support to obtain a patch for R12.
Note 1150063.1 Project Performance Current Reporting Period PA - Last Period Results In Error
Recommended Links
The following notes may be useful to help resolve common issues when using Project Performance
Reporting:
Note 1166423.1 Troubleshooting Guide for Project Performance Reporting
Note 1150063.1 Project Performance Current Reporting Period Pa - Last Period Results In Error
Note 1099603.1 How To Get Data In Performance Reporting For Linked Projects To Program?
Note 459875.1 What Happens If PJI Load Processes Are Executed More Than Once?
Note 1174657.1 New concurrent program PRC: Delete Historical Workplans and Financial Plans to
help managing Project Management data effectively
Note 311745.1 Temporary Tablespace Sizing And Profile Options For Initial Summarization Loads In
11i.PJ_PF.M
Note 356829.1 Troubleshooting Guide Oracle Project Management (Performance Reporting) -
Common errors in PPR processes
Note 375728.1 How Can You Change Project Performance Setup?
Note 1064449.1 Project Management New Feature: Streamline Reporting Data Creation











\

Mar 2011

Oracle Corporation
World Headquarters
500 Oracle Parkway
Redwood Shores, CA 94065
U.S.A.

Worldwide Inquiries:
Phone: +1.650.506.7000
Fax: +1.650.506.7200
oracle.com
Copyright 2011, Oracle and/or its affiliates. All rights reserved. This document is provided for information purposes only and the
contents hereof are subject to change without notice. This document is not warranted to be error-free, nor subject to any other
warranties or conditions, whether expressed orally or implied in law, including implied warranties and conditions of merchantability or
fitness for a particular purpose. We specifically disclaim any liability with respect to this document and no contractual obligations are
formed either directly or indirectly by this document. This document may not be reproduced or transmitted in any form or by any
means, electronic or mechanical, for any purpose, without our prior written permission.

Oracle and Java are registered trademarks of Oracle and/or its affiliates. Other names may be trademarks of their respective
owners.

AMD, Opteron, the AMD logo, and the AMD Opteron logo are trademarks or registered trademarks of Advanced Micro Devices. Intel
and Intel Xeon are trademarks or registered trademarks of Intel Corporation. All SPARC trademarks are used under license and are
trademarks or registered trademarks of SPARC International, Inc. UNIX is a registered trademark licensed through X/Open
Company, Ltd. 0410