Managing Risk for Structured Work

advertisement
NorCal OAUG 2010 Training Day
How to deploy Performance Reporting
within Oracle EBS Projects successfully
Suhail Maqsood
Chief Operating Officer, Rysigo Technologies Corp
Agenda






Oracle Projects Reporting Solutions
The Business Need
Project Performance Reporting – Overview
Exceptions Management - Overview
Architecture
Project Status Inquiry vs Project Performance
Reporting
 Implementation tips and techniques
 Implementation gotcha’s
 Project Performance Reporting Enhancements
Oracle Projects Reporting Solutions
Projects Intelligence
Project Analytics
12
+
Discoverer
Workbooks
Project Status
Inquiry
Concurrent
Reports
FORMS
Project Performance
Reporting
Reporting Pack
(BI Publisher)
12
+
Project List
Status
Reports
HTML
ORACLE PROJECTS
Project Performance Reporting – Business Need
Compressed Business Cycles
• Multiple fragmented systems
• Manual transformation,
cleansing and rollup of data
• Timeliness of information
Increased Accountability
• Incomplete data across business,
lifecycle
• Alignment with corporate objectives
• Visibility into key metrics
Reduced IT Budgets
• Reliance on technical staff for reports
• Expensive systems for generating
reports
• Ad-hoc process of collecting
information and generating reports
Operational Challenges
• Consistency and accuracy of
information across roles &
business units
• Security of information
• Supplier and customer access
Project Performance Reporting - Overview
Project
Visibility across all levels of a project
Multiple reporting sections
•
•
•
•
•
Work
Report Financial Info, Effort and Earned Value
Analysis by Tasks, Resources, Time
Drill down to underlying transactions
Configurability with Graphs
Report by Multiple currencies and calendars
Resources
Highly Configurable
More powerful than PSI
Drill down from Project Intelligence
Reporting by Project – Performance Overview
Project
X
Top
Task 1
Activity 1
Activity 2
Financial
Performance
Effort
Cost
Earned
Value
Revenue
Billability
Top
Task 2
Activity 1
Billing and
Collections
Example of the performance areas you can see on the
overview page layout for each project type.
Reporting by Task – Task Summary
Project
X
Top
Task 1
Activity 1
Activity 2
Top
Task 2
Activity 1
Financial Structure
Example of viewing financial information such as
actual cost and actual revenue at the task level of a
financial structure. These amounts are rolled up to
the project level.
Viewing Detailed Amounts
Project
Task
Lowest Task
Expenditure Items
Commitments
Events
Actuals
For example, drill down to view actuals and
commitment details for the lowest level tasks.
Reporting by Resource – Resource Summary
0 - RBS
Version
Standard Costs
Standard
Time
Contractor
Time
Profitability
Cost
Example of viewing cost and profitability from a
resource breakdown structure.
Periodic View
May 2008
Cost
Revenue Margin
June 2008
Cost
Revenue Margin
You can use the Periodic View page to create a side-byside comparison of project performance reporting
information for a specific calendar and currency across
several months, quarters, or years.
To-Date View
Example of the available to-date views in which you
can view financial information for a project through a
particular point in time.
Project Performance Reporting – Examples
Overview of Performance Exceptions Reporting
Visual status indicators that denote exceptions can
be tracked at the three levels shown above.
Adding Performance and Scoring Rules
Project
X
Top
Task 1
Activity 1
Top
Task 2
Activity 2
Activity 1
With proper authority, you can add and remove
performance rules and key performance area scoring
rules for a project.
Managing Exceptions
You can click the exception icon status to drill
down to the details of the exception.
Exceptions Management - Overview
 View Key Performance Area Statuses for a project
> Financial
> Schedule
> Execution
 Drilldown to individual exceptions for the project
Project
Dashboard
Exceptions
Exceptions Management “Rollup” - Overview
Single
Project
Status
Key
Performance
Areas
Exceptions
Overall Project Status
Financial
Schedule
Execution
Project Performance Reporting – Overview
1. Intuitive front end
2. Support for
a) 5 different currencies
b) Multiple calendars – PA, GL, Enterprise
c) Multiple structures – (Workplan, Financial)
d) Multiple Resource Breakdown Structures per project
3. Single reporting summarization model
PJI and Performance Reporting
4. Custom Measures
Project Performance Reporting: Setup
Setup Profile Options
Calendar
BIS: Enterprise Calendar
BIS: Period Type
Currency
BIS: Primary Currency
BIS: Primary Rate Type (mandatory)
BIS: Secondary Currency
BIS: Secondary Rate Type (optional)
Global Start Date
BIS: Global Start Date
Architecture
Forecast Items
Availability Facts
Budgets and
Financial Plans
Resource
Management Facts
Financial and
Planning Facts
Draft Revenues
Project Intelligence
Corresponding
Materialized Views
Activities Fact
Revenue Lines
Expenditures
Cost Lines
Invoices
Online Plan Data
Shared Extraction
Financial and
Planning Fact
Funding
Activities Fact
Commitments
Project Performance
Architecture – Concurrent Programs
** Concurrent Programs in green represent
the usual business flow
Project Intelligence
“PRC: Load Project Intelligence Data”
“PRC: Update Project Intelligence Data” **
“PRC: Refresh Project Intelligence Data”
“PRC: Delete Project Intelligence Data”
“PRC: Load Project and Resource Base
Summaries”
“PRC: Update Project and Resource Base
Summaries” **
“PRC: Refresh Project and Resource
Base Summaries”
“PRC: Delete Project Intelligence and
Performance Reporting Data”
Shared Extraction
“PRC: Load Project Performance Data”
“PRC: Update Project Performance Data” **
“PRC: Refresh Project Performance Data”
“PRC: Process Resource Breakdown
Structure Updates”
“PRC: Delete Project Performance Data”
Project Performance
Project Status Inquiry versus Project Performance Reporting
Feature
PSI
Project Performance
Calendars
One calendar (PA or GL)
PA, GL and Enterprise
Currency
Only functional
Upto five
Period types
Total, ITD, PTD, PP,YTD
Total, ITD, PTD, YTD, QTD
Periodic data
Only for current reporting period
All periods
Budgetary controls
Supported
Not Supported
Resource Views
Using resource list – only 2 levels
Using RBS – multi-level
Seeded Measures
40 (120)*
160 (418)
Display measures
30
all
Comparisons
Actual vs. Approved Budget vs.
Primary Forecast
Actuals vs. Budgets – 2 plan types vs
any approved forecasts
Drill-downs
Summary to transaction screens (e.g:
Exp. Enquiry)
Resource summary to transactions
Summary to day level transactions
No drill-down from resource summary
Custom measures
Up to 30 numeric (includes ITD,
YTD, PTD, PP, Total) and 3 text
SQL based formula– not flexible
Up to 60 numeric (excludes ITD,
PTD, Total)
SQL and PL/SQL based formula –
more flexible
Implementation Tips and Techniques
> Implementing PPR introduces additional technologies that
a customer needs to be able to understand and support:
• Tech Stack – PMV (Performance Management Viewer)
> The initial load programs may take a significant time and
system resources to complete (based on the data volume).
• Plan accordingly for this!
• Refer to the PJI Project Performance Sizing spreadsheet to
obtain an accurate prediction of tablespace sizes
Implementation Tips and Techniques
 PJI Project Performance Sizing Spreadsheet –
Available soon!
Implementation Tips and Techniques
> To reduce the time it takes to summarize the data and
the size of the database, consider:
• Purging Projects data prior to running summarization
processes using the Purge program
• Reducing the date data needs to be summarized from
• Clean up Projects data if possible (close projects etc)
DO NOT run the Delete or Truncate processes unless
instructed to do so by development when experiencing an
issue for which an SR is logged
Customization options
• There are 2 methods to define custom measures
– Stored custom measures
—
—
—
Defined by updating the package (PJISC01B.pls)
Calculated and stored during summarization process.
For further details on how to modify the package to create
the stored custom measure, please read the header of the
file.
– Computed custom measures
—
—
Defined using the user interface for custom measures
Calculated and displayed during the runtime.
Customization Options
Performance Tracking and Exceptions
• Customize icons
– The Implementation user can chose to define a different
icon by updating the same in the following lookup:
PA_PERF_INDICATORS
• Customize KPA
– The Implementation user can edit the KPA for name,
enabling 2 addl KPA through the following lookup:
PA_PERF_KEY_AREAS
Customization Options
Performance Tracking and Exceptions
• Performance Exception Status Client Extension
(PA_PERF_STATUS_CLIENT_EXTN)
– Returns the overall performance indicator for a project.
– $pa/patch/115/sql/PAPESCLS.pls (specification file)
– $pa/patch/115/sql/PAPESCLB.pls (package body file)
Implementation Gotchas
 Typical issues hit during an implementation:
Issue
Likely Cause
The load and update processes are Ensure you have the latest patches
taking too long to run
– refer to the Recommended patch
list on Oracle Support pages
Also, ensure your DBA has
gathered Schema Statistics for PA,
FII and PJI.
Implementation Gotchas
 Typical issues hit during an implementation:
Issue
Suggestion
How can I reduce the time it takes Reduce the amount of data that is
to run the summarization for a
being summarized by modifying
conference room pilot?
the “Global Start Date”
Implementation Gotchas
 Typical issues hit during an implementation:
Issue
Suggestion
When I drill-down from Project
Intelligence detail report to a
project the amounts don't match.
Why?
Either the project performance or
the project intelligence may show
the latest data if the programs
were run out of sync.
Statistics from an early adopter
FP.M Upgrade:
Shared Extraction (load):
Project Performance (load):
runtime: 3hr 23m
runtime: 8hr 20m gather statistics: 2hr 43m
runtime: 37hr 31m gather statistics: 8hr 50m
Data Distribution:
54,255 Projects
Work Breakdown Structure:
50M rows in PA_PROJ_ELEMENT_VERSIONS
109K work plan versions
600K financial plan versions
150K FIDs
21M CDLs
Hardware Configuration: 4 node RAC on 4 SUN 25K servers
CPU: Total 80 Dual-Core 1.2 Ghz UltraSparc IV processors
Memory: Total 320 GB of memory
Troubleshooting Recommendations
• Summarization takes unreasonably long to complete
– Statistics
– Trace files
• Environment issues: Unable to extend tablespace, etc.
– Auto-recovery!
• Overlapping Work
– Resolve the base issue (see output – next slide)
• Missing Calendar / Currency Setup
– Fix and resubmit (auto-recovery)
Troubleshooting Recommendations
Always check the output of the summarization program
The following entries correspond to incomplete runs of the
Project Performance summarization program. To complete any
of the incomplete runs, submit a new Project Performance
summarization run with identical parameters to the
incomplete run.
Incomplete Summarization Run
Run Mode
: Update Project Performance Data
Project Type
: <<no selection made>>
Project Organization
: <<no selection made>>
From Project
: Sum_Test_Forecast_FS_CB
To Project
: Sum_Test_Forecast_FS_CB
Troubleshooting Recommendations
Just about all PJI and PPM debugging starts in one place:
Information about existing summarization runs:
select
*
from
pji_system_parameters
order by name, value;
Information about what those runs are doing:
select
*
from
pji_system_prc_status
order by process_name, step_seq;
PJI_SYSTEM_PRC_STATUS sample output
PROCESS_NAME STEP_SEQUENCE STEP_STATUS STEP_NAME
------------ ------------- ----------- ----------------------PJI_EXTR1
10
C INIT_PROCESS
PJI_EXTR1
20
RUN_PROCESS
PJI_EXTR1
30
WRAPUP_PROCESS
PJI_EXTR1
40
C POPULATE_TIME_DIMENSION
PJI_EXTR1
50
C EXTRACT_BATCH_DREV
PJI_EXTR1
60
C MARK_EXTRACTED_DREV_PRE
Current
...
...
...
...
Point of
PJI_EXTR1
340
C ORG_EXTR_INFO_TABLE
Execution
PJI_EXTR1
350
C CURR_CONV_TABLE
PJI_EXTR1
360
C DANGLING_FIN_ROWS
PJI_EXTR1
370
DANGLING_ACT_ROWS
PJI_EXTR1
380
PURGE_DANGLING_FIN_ROWS
PJI_EXTR1
390
PURGE_DANGLING_ACT_ROWS
PJI_EXTR1
400
FIN_CMT_SUMMARY
...
...
...
...
•
If this table contains any rows, then incomplete runs exist.
Project Performance Reporting Enhancements
R12.1
Additional Measures
Year To Date, Quarter to Date and At Completion calculated
measures are now available.
Inter-project Revenue & Cost are included in the Provider
Project Revenue & Cost amounts
New concurrent audit process
AUD: Project Performance Reporting Setup
Generates a report that enables you to review setup information
for Oracle Projects Project Performance Reporting
New parameters for PRC: Refresh Project Performance Data
Project Performance Reporting Enhancements
Future enhancements to:
1.
2.
3.
4.
5.
6.
7.
Improve Performance and scalability
Reduce Volume Growth
Eliminate Data Inconsistency
Streamline patch delivery
Best Business Practices
Increase responsiveness
Recovery from failed processing
NorCal OAUG 2010 Training Day
Thank you
For further information, please contact
Suhail.Maqsood@Rysigo.com
Download