Understanding the Data Summary Process

In PeopleSoft Project Costing, you summarize data before you archive it. You use the Project Data Compression Application Engine process (PC_COMPRESS) to summarize project data into history tables. Then, you use the PeopleSoft Archive (PSARCHIVE) process to archive data from the history tables.

This topic discusses:

  • Summarization process flow.

  • Tables populated by the Project Data Compression process.

  • Summary transactions.

  • Project compression log.

PeopleSoft Project Costing keeps all life-to-date transactions for each project, resulting in a high volume of data to manage. To reduce storage needs and increase performance, you can summarize transaction data by using the Project Data Compression Application Engine process that retains project costs while deleting some detail and integration information.

The Compress Project Data (PC_COMPRESS) process compresses project transactions based on parameters from the run control. This process:

  1. Selects the transactions that are targeted for compression and saves them in history tables.

  2. Creates summary transactions and inserts them into the project transactions table.

  3. Deletes the original transactions from the project transaction table.

This diagram shows the Project Data Compression process, which consists of six steps.

 Project Data Compression process

The data compression and restoration process flow that the system performs is:

  1. Copy the detailed transaction rows based on the compression template and run control options from the Project Transaction table (PROJ_RESOURCE) to the Project Transaction History table (PROJ_RES_ARCH).

  2. Summarize detailed transaction rows in the Project Transaction History table and copy them to the Project Summary History table (PROJ_SUM_ARCH).

  3. Delete the original transactions from the Project Transaction table.

  4. Copy summarized transactions in the Project Summary History table to the Project Transaction table.

  5. Restore rows from the Project Transaction History table to the Project Transaction table as detailed rows.

  6. Delete compressed rows in the Project Transaction table.

See the product documentation for PeopleTools: Data Management

The Project Data Compression process stores data in transaction history and summary tables. The process updates these tables when you summarize data from the Project Transaction table:

  • Project Transaction History (PROJ_RES_ARCH)

  • Project Summary History (PROJ_SUM_ARCH)

  • Project Resource (PROJ_RESOURCE)

  • Project Compression Log (PC_COMPRESS_LOG)

The Project Data Compression process summarizes transaction data based on run control parameters, such as date, analysis group, contract, or customized SQL. The Project Data Compression process should be performed only on completed projects and activities. The system does not check the status of a project or activity before running the Project Data Compression process.

A compression template is used to define how project transactions are to be summarized during the process. The template enables users to choose the dates they want to roll up and the rollup calendar. Microsoft and Sybase database platforms have a limit of 32 fields of detail.

For example, a compression template is created using these parameters:

  • Date Roll up Level is Monthly.

  • Roll up Date to Use is Start of Period.

  • Calendar ID is 01 Monthly.

  • Dates Selected are Accounting Date and Transaction Date.

The 01 Monthly Calendar for year 2007 is set up:

  • Period 01: January 01, 2007 to January 31, 2007

  • Period 02: February 01, 2007 to February 28, 2007

  • And so on

Before the compression process runs, the detail rows in the PROJ_RESOURCE table are:

Business Unit

Project

Activity

Amount

Acct Date

Transaction Date

US004

ABC

001

100.00

01/01/2007

01/05/2007

US004

ABC

001

200.00

01/15/2007

01/15/2007

US004

ABC

001

500.00

02/02/2007

01/31/2007

US004

ABC

001

600.00

02/28/2007

02/28/2007

US004

ABC

001

100.00

02/28/2007

02/01/2007

After the compression process runs, the detail rows in PROJ_RESOURCE table are:

Business Unit

Project

Activity

Amount

Acct Date

Transaction Date

US004

ABC

001

300.00

01/01/2007

01/01/2007

US004

ABC

001

500.00

02/01/2007

01/01/2007

US004

ABC

001

700.00

02/01/2007

02/01/2007

The system logs each compression run in the PC_COMPRESS_LOG table. The log retains compression details such as run date, parameters used, and status. Additional details, such as date option, analysis group, contract, and SQL, are logged if used.

The compression log enables the user to perform actions such as viewing history or archiving, purging, restoring, and rolling back data.