Custom Reporting Summarization Views
Oracle Projects provides two sets of views for custom reporting on summarization summary amounts:
- Work Breakdown or WBS summarization views
- Resource summarization views
Both sets of views contain project and task-level summary amounts. The WBS summarization views have summary level amounts for projects and tasks. The resource summarization views have summary amounts by project and resource as well as task and resource.
Each set of views contains views with prior-period, period-to-date, year-to-date, inception-to-date, and project summary amounts for the following:
Work Breakdown Summarization Views
The WBS summarization views are as follows:
WBS Summarization Actuals View: This view contains summary amounts of actual costs and revenue by project and task.
WBS Summarization Revenue Budget View: This view contains summary amounts of revenue budgets by project and task.
WBS Summarization Cost Budget View: This view contains summary amounts of cost budgets by project and task.
WBS Summarization Commitments View: This view contains summary amounts of commitments by project and task.
These views also contain limited task information, such as project number and name, indented task numbers and names, task start and completion dates, and task manager name.
You can refer to the Oracle Projects Revenue, Costs, Budgets by Work Breakdown Structure Report as an example of how to use these views for reporting. See: Revenue, Costs, Budgets by Work Breakdown Structure.
Resource Summarization Views
The resource summarization views are as follows:
Resource Summarization Actuals View: This view contains summary amounts of actual costs and revenue by project and resource and task and resource.
Resource Summarization Revenue Budget View: This view contains summary amounts of revenue budgets by project and resource and task and resource.
Resource Summarization Cost Budget View: This view contains summary amounts of cost budgets by project and resource and task and resource.
Resource Summarization Commitments View: This view contains summary amounts of commitments by project and resource and task and resource.
You can refer to the following Oracle Projects reports for examples of how to use these views for reporting:
Custom Reporting Strategies with WBS and Resource Reporting Summarization Views
The following custom reporting strategies pertain to both sets of reporting summarization views.
Since both sets of views contain project and task-level summary amounts, you must be careful to select the appropriate rows:
- For project-level rows, the task_id is zero
- For task-level rows, the task_id is greater than zero
When designing the data model in Oracle Reports, you will need to consider the following information:
- Unless you create a higher-level view for one or more of the reporting summarization views, Oracle Projects requires separate query groups for each view used in a report.
Because of performance implications, higher-level views are not recommended.
- It will be necessary to drive the views off a table, such as the PA_TASKS table, for a WBS report or a resource list for a resource report.
- With respect to the budget views, there can be one or more budget rows for a given project, task, or resource
You may need to either join on the 'budget_type_code' or filter on it in a query group.
To report multiple budget types for each project or task, you must create a query group for each budget type
- If you design your data model to report by budget type and resource list, you can assume that only one resource list is assigned to each budget type
To facilitate resource list-driven reporting, Oracle Projects provides the view, 'pa_resource_list_members_v'. This provides the following functionality:
- A resource list with indented second-level resources within each respective resource group
- Columns to facilitate the ordering of resource groups and their related second-level resources
To use this view in your custom reports, you can add the following to the resource-list query:
- Use the 'alias' view column to automatically display an indented resource list
- Include an order-by clause, such as the following, to ensure the proper ordering of resource groups and related second-level resources:
order by parent_sort_order, sort_order
