By Ravi Shankar, PgMP

This is Part 2 of a 2-part blog series on Program Reporting in Oracle E-Business Suite Project Management (PJT). These blog articles and our May 4th Webinar will help you understand how to use Program Reporting in your organization.

Program Roll-up Metrics

The following metrics roll up at the Program level:

• • Financial Performance (Budgets, Forecast, Actuals for Cost, Revenue, Margin, etc.)
  • Effort
  • Cost
  • Revenue
  • Earned Value
  • Billability
  • Billing and Collection
  • Backlog

How the Process Works

To implement the Program level reporting, you need to do the following:

• Create Program project
• Create child project(s)
• Assign (staff) resources through Oracle Project Resource Management  (PJR). Fund the project(s)
• Generate Approved Budget (Budget & Forecast)
• Link the child project(s) to the lowest WBS of the Program project
• Enter transactions
• Run Costing, Revenue, and Invoicing processes
• Create cost & Revenue Accounting Events, interface to GL
• Generate Invoices and run streamlined processes to interface with AR
• Update PSI
• Run the Request Set: PRC: Update Project Reporting Base Summaries and Performance Data
• Review the Program information roll-up for the linked project(s) and the Program (if it has its activities) for Actuals, Budgets, and Progress
• Drill down to details of the child project(s)

Publishing Workplans of Projects and Program

Detailed information is provided in the User Guide that explains the Publishing processes and how the Application links the versions within the Program hierarchy. Therefore, please refer to that document.

Here is a summary of what needs to be done and the steps to be followed:

• Workplan of the Program and the linked project(s) can be published (and baselined) independently
• PRC: Process Structure Updates synchronize data across the Program Hierarchy
• Typically, update the work plan (s) of linked child projects and publish them. Launches the Update and synchronizes data
• Ensure Baseline versions of all linked projects are linked and rolled up with the Baseline version of the Program

Key Design Considerations

To be successful, you must consider the following.

First, you must evaluate your business needs between roll-up reporting for related projects and operational analysis using reporting Organization hierarchy. Then you must consider the work breakdown structure of linked projects and their interrelationship. Then it is time to carefully review the prerequisites to implement this PJT functionality. Only then are you ready to make an informed decision considering the implementation and use of the Program functionality detailed above.