Understanding Report Summarization
The Report Summarization process summarizes rows in the Project Transaction table (PROJ_RESOURCE) into a smaller Project Transaction Reporting table (PC_RPO) for enhanced performance. Creating reports by using report summarization is a three-step process:
Create a Report Summarization group that contains the distinct fields that you want to summarize from the Project Transaction table.
Run the Report Summarization process to populate the Project Transaction Reporting table.
Use PSQuery, BI Publisher, or nVision to create the report.
You can restrict the level of data that users can access by first enabling Allow Multiple Report Summary and then enabling project-level security. When enabled, the Allow Multiple Report Summary option populates the Project Transaction Reporting table with the operator ID of the individual making the request.
Delivered PeopleSoft Project Costing reports use data from the Project Transaction Reporting table instead of the Project Transaction table.
This topic discusses:
Date options.
Project-level security in Report Summarization.
The Report Summarization process uses the calendar that is specified in the Reporting Roll Up Calendars group box on the Installation Options - Project Costing page. Additionally, it uses the 01/01/1900 date as a wildcard value. For example, if you use a date option of Accounting Date, the transaction date in the Project Transaction table is irrelevant. Therefore, the system assigns the wildcard value of 01/01/1900 to the field.
This table shows an example of the rules that the Report Summarization process uses to assign accounting and transaction dates. Assume that the accounting date and transaction date are 09/10/2005:
|
Date Option |
Reporting Interval |
Transaction Date in PC_RPO |
Accounting Date in PC_RPO |
|---|---|---|---|
|
Accounting Date |
Daily |
01/01/1900 |
09/10/2005 |
|
Accounting Date |
Monthly |
01/01/1900 |
09/30/2005 |
|
Accounting Date |
Quarterly |
01/01/1900 |
10/31/2005 |
|
Accounting Date |
Yearly |
01/01/1900 |
12/31/2005 |
|
Transaction Date |
Daily |
09/10/2005 |
01/01/1900 |
|
Transaction Date |
Monthly |
09/30/2005 |
01/01/1900 |
|
Transaction Date |
Quarterly |
10/31/2005 |
01/01/1900 |
|
Transaction Date |
Yearly |
12/31/2005 |
01/01/1900 |
|
All |
Inception |
01/01/1900 |
01/01/1900 |
The Report Summarization process enforces team, user, or permission list security for projects if you activate project-level security on the Security Options page and activate the Allow Multiple Report Summary option on the Installation Options - Project Costing page.
This table lists security options that you can establish for the Report Summarization process:
|
Project-level Security |
Allow Multiple Report Summary |
Report Summarization Process Functionality |
|---|---|---|
|
Activated |
Activated |
The process refreshes the Project Transaction Reporting table based on the row-level security of the user who is running the process or, in other words, based on permission lists or on individual users. The Report Summarization process selects only those rows for which the user has security access. The process refreshes summary rows only for the user who is running the process. Summary rows that other users create remain unchanged in the Project Transaction Reporting table. |
|
Not activated |
Activated |
The process uses all rows in the Project Transaction table to refresh the Project Transaction Reporting table for the user who is running the process. Summary rows that other users create remain unchanged in the Project Transaction Reporting table. |
|
Activated |
Not activated |
The process refreshes the entire Project Transaction Reporting table each time the Report Summarization process runs. The process is not subject to project-level security. |
|
Not activated |
Not activated |
Same as above. |