Running Data Archival Processes

Select an existing archive ID.

Click to display all the tables to be included in the archive project.

Click to access the Archive Designer pages.

Select the archive process to run. Options are:

• Selection: Copy the data from the online tables to the history tables.

• Rollback: Copy the data from the history tables to the online tables.

• Delete: Remove the data from the online tables, but only when they have already been copied to the history tables.

• Remove from History: Delete the data from the history tables.

Select to enable the Commit After option, which specifies how many rows of data the system processes before issuing a database commit. Otherwise, the system issues a commit after each record has been processed.

If you have any custom PeopleSoft Application Engine programs that you want to run against the data, either before or after archiving, specify the appropriate program here. The available fields are:

• Pre AE: Select an existing Application Engine program to run before the archiving process.

• Post AE: Select an existing Application Engine program to run after the archiving process.

Select to indicate whether the table is processed at run time

Displays the tables containing the data to be archived.

Displays the tables where the system stores the archived data.

If your archive template contains runtime parameters (%PSPARMnn%), specify a value that the system substitutes in the SQL statement at run time.

Click to export the data to the flat files.

Select an existing archive ID.

Enter the path for the directory in which you want to store the resulting flat files. When you click Auto Fill Records, the directory is added as a prefix to each of the resulting file names.

Once you've selected an archive ID, click to display the table names associated with the archive. In addition, you must specify the path where the data will be exported.

Click to access the Archive Designer pages.

If you have any custom PeopleSoft Application Engine programs that you want to run against your data either before or after archiving, specify the appropriate program here. The available fields are:

• Pre AE: Select an existing Application Engine program to run before the archiving process.

• Post AE: Select an existing Application Engine program to run after the archiving process.

Select to specify whether to process this table.

Displays path and file names to which the data for each table will be written. If necessary, you can manually enter the file path so that a table has unique file name and location.

If the archive process contains the runtime parameter markers (%PSPARMnn%), specify a value that the system substitutes in the SQL statement at run time.

Click to export the data in the history table to the designated flat file.

Select an existing archive ID.

Enter the path for the directory in which to store the resulting flat files. When you click Auto Fill Records, the path is added as a prefix to each of the resulting the file names.

Click to display the table names. In addition, you must specify the path where the data is exported.

Displays the name of the table that is processed. This field is populated by clicking the Auto Fill Records button.

Displays the path and file names to which the data for each table is written. If necessary, you can manually enter the file path so that a table has a unique file name and location.

Click to import the data from the flat file into the designated staging table.

Enter the number of rows that the program processes before it issues a COMMIT.

Enter the path and the name of the file containing the flat file that you want to import into the database.

Enter the staging table name where the program inserts the data from the import file.