Understanding the Data Archive Process

This topic lists a prerequisite and discusses the archive process flow.

Before you can archive data, you must run the Project Data Compression process to populate the Project Transaction History table and the Project Summary History table.

This diagram illustrates how the archive process follows the data compression process, which consists of nine steps.

 The project data compression process is followed by the archive process

The data compression, archiving, 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. Archive or copy rows from the Project Transaction History table to the Project Transaction Archive table, and from the Project Summary History table to the Project Archive History table.

  6. Delete archived rows in the Project Transaction History table and in the Project Summary History table.

  7. Roll back archived rows from the Project Transaction Archive table to the Project Transaction History table, and from the Project Archive History table to the Project Summary History table.

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

  9. Delete compressed rows in the Project Transaction table.

You must complete these steps to compress and archive data in PeopleSoft Project Costing:

  1. Run the Project Data Compression process to summarize transaction data into history tables.

    You must complete this recurring step before each occurrence of the archive process. The archive process relieves only the Project Transaction History table and Project Summary History table. Archiving data does not affect the Project Transaction table.

  2. Select the archive action to initiate the archive jobs that move summarized project data into the archive tables.

    For this recurring step, you select the archive action from the Project Compression Tracking page for the set of compressed data that you want to archive.

    By selecting the archive action, the archive jobs are automatically submitted in the background.

  3. (Optional) Roll back data from the archive tables to the history tables to recover deleted data as needed.

  4. (Optional) Restore data from the transaction history table to the project transaction table to recover detailed data as needed.

  5. (Optional) Purge data from the Project Transaction History table and Project Summary History table.

    You can delete data from the transaction history and summary tables without archiving the data by selecting the purge option from the Project Compression Tracking page. You should only select this option if you no longer need to retain historical transaction data. Consider carefully before you select this option.

  6. (Optional) Audit archive jobs.

    The Data Archive Manager retains information about each process that is executed, such as who ran the process, when they ran it, which archive ID and record were affected, and what SQL statement was executed.