To archive and purge in Oracle Projects, you use the following processes:
The Validate Purge Batch process verifies that projects satisfy the default prerequisites and any additional business rules defined in the Validation Extension. See: Prerequisites for Purging Projects and Validation Extension, Oracle Projects APIs, Client Extensions, and Open Interfaces Reference.
Submit the ADM: Validate Purge Batch process from the Purge Batches window. See Release the Purge Batch.
You can also validate the batch by running the process in the Submit Requests window.
Batch Name. The name of the batch you want to validate.
Run Validation. The default value is Yes. Enter No to run the Purge Validation Report without running the validation.
Report Errors Only. The default value is No. Enter Yes to report only those projects that fail validation.
The following reports show the results of this process:
The Purge Validation Report lists all projects included in the purge batch.
The Purge Validation Exception Report lists the projects that failed the validation. The report includes a description of the error or warning message associated with each project.
This process purges and archives project information, as specified for each project in the batch. The Purge Extension allows you to purge custom tables. See: Archive Custom Tables Extension, Oracle Projects APIs, Client Extensions, and Open Interfaces Reference.
After the process runs, the system changes the purge batch status to Completed and changes the project status. For more information about project statuses, see: Project Statuses for Purged Projects.
Submit the ADM: Purge Project Data process from the Purge Batches window. See: Start the Purge Process.
You can also run the process in the Submit Requests window.
Batch Name. The name of the batch you want to purge.
Run Purge. The default value is No. Enter Yes to run the Purge Project Data Process. Enter No to run the Purge Process Report without running the purge itself.
Commit Size. This program processes a certain number of records at a time, depending on your commit size. The commit size indicates how many records the program processes and stores before it purges and/or archives the records.
For example, suppose that you have 4000 records to purge and your commit size is set to 1000. The program processes the first 1000 records and purges them, then processes the next 1000, and so on, until it processes and purges all 4000 records.
The commit size can help to optimize processing time. Your database administrator should identify what is the best commit size for your organization. This field can be set up to display a default value. For more information, see PA: Commit Size for Archive and Purge, Oracle Projects Implementation Guide.
Note: If you have historical (prior to Release 12) Multiple Reporting Currency transactions, then the commit size includes the increased number of secondary records you have for each reporting currency.
The following reports show the results of this process:
The Purge Process Report lists the projects that were purged. For each purged project, the report also shows the database tables that were purged, and the number of rows that were purged from each table.
This process purges the unassigned time for all resources. This unassigned time includes resource capacity, availability and overcommitment. The process purges the unassigned time through the Purge Till Date that you specify, assuming therefore that you no longer need to track resource capacity, availability or overcomitment through that past date.
Submit the ADM: Purge Resources Unassigned Time process from the Submit Requests window.
Purge Till Date. The date through which you want this process to purge data.
Archive. Select Yes to archive, or No to not archive data.
The following reports show the results of this process:
The Purge Resources Unassigned Time Process Report. This report lists the database tables that were purged and the number of rows that were purged from each table.
Use this concurrent program to purge obsolete project data for all projects without regard to project status.
Obsolete project data is data that has become irrelevant or invalid as a result of the creation of new or updated data. Obsolete project data includes additional data created during processing and data copied to Oracle Projects tables that is not automatically removed when the source data is purged from permanent tables.
Submit this program to purge the following types of data at the specified times:
Daily Forecast Information: Submit this program at any time to delete historical information about resource availability, project requirements, and project assignments.
Reporting Exceptions: Submit this program after the Purge Concurrent Request and/or Manager Data program is run to delete exception information displayed by the PRC: Maintain Project Resources concurrent program
Projects Workflow: Submit this program after the Purge Obsolete Workflow Runtime Data program is run to delete copies of the obsolete workflows stored in Oracle Projects.
Project Performance Log Data: Submit this program at any time to delete all the debug information stored by project performance summarization processes.
Terminated Organization Authority: Submit this program at any time to delete organization authority information for all terminated employees or contingent workers.
All: Submit this program at any time to delete all of the preceding types of project data.
Submit the ADM: Purge Obsolete Projects Data concurrent program from the Submit Requests window.
Purge Type: Select from the following purge data types:
Daily Forecast Information
Reporting Exceptions
Projects Workflow
All
Commit Size: This program obtains the commit size value from the PA: Commit Size for Archive and Purge profile option. For more information, see PA: Commit Size for Archive and Purge, Oracle Projects Implementation Guide.
No output report is generated. However, the program creates a log file that indicates the number of purged records.