Prerequisites for Purging Projects (Oracle Project Foundation)

All projects in a purge batch must meet certain prerequisites for the batch to be purged or archived and purged.

Prerequisites for All Projects in a Purge Batch

All projects in a purge batch must meet the conditions shown in the following table before the batch can be purged or archived and purged. The conditions vary by project type class (indirect, contract, or capital):

Indirect Project	Contract Project	Capital Project	Condition
yes	yes	yes	All related records in transaction interface tables must be interfaced to Oracle Projects. See: Transaction Import.
yes	yes	yes	All related supplier invoices must be interfaced from Payables to Oracle Projects. See: Interface Supplier Costs.
yes	yes	yes	The project must not have pending commitments. See: Commitments from External Systems, Oracle Projects Implementation Guide
yes	yes	yes	Expenditure item costs must be distributed. See: Distribution Processes.
yes	yes	yes	Accounting for costs must be successfully created in Oracle Subledger Accounting. See: Generate Cost Accounting Events and Create Accounting.
	yes		Events having completion dates must be processed. See: Events.
	yes		Accounting for revenue must be successfully created in Oracle Subledger Accounting. See: Generate Revenue Accounting Events and Create Accounting.
	yes		Draft invoices must be interfaced to and accepted in Oracle Receivables. See: Interface Invoices to Receivables.
	yes		Unbilled receivables and unearned revenue for the project must be zero. See: Reviewing Revenue.
	yes		Project-related Receivables invoices must have a zero balance (that is, the invoice must be paid). Contract projects with invoices that have a balance due amount cannot be purged. See: Oracle Receivables Reference Guide.
		yes	If you have chosen Purge Capital Data in the Purge Batch Details window, all asset lines must be generated and successfully interfaced to Oracle Assets. Also, all project-related assets must be posted in Oracle Assets. See: Generate Asset Lines and Interface Assets.
yes	yes	yes	AP discount lines must be interfaced to Oracle Projects. See: Interface Supplier Costs.
yes	yes	yes	All allocation runs must be in either the Release Success status or the Reversed status for any task of a project that is purged.
yes	yes	yes	All project-related supplier invoices in Oracle Payables must be fully paid.
yes			Project-related records in Oracle Time & Labor must be interfaced to Oracle Projects.
yes			The project must not be an Organization Forecast project. See: Organization Forecasting.
yes	yes	yes	Receipt accrual amounts for project-related purchase items must be interfaced to Oracle Projects. See: Revenue Accruals.
	yes		All retentions must be billed and the retention balance must be zero. See: Customer Billing Retention.
yes	yes	yes	Project transactions must not be referenced in Oracle Project Contracts, Oracle Property Manager, or Oracle Commitment Administration.

yes

All related records in transaction interface tables must be interfaced to Oracle Projects. See: Transaction Import.

yes

All related supplier invoices must be interfaced from Payables to Oracle Projects. See: Interface Supplier Costs.

yes

The project must not have pending commitments. See: Commitments from External Systems, Oracle Projects Implementation Guide

yes

Expenditure item costs must be distributed. See: Distribution Processes.

yes

Accounting for costs must be successfully created in Oracle Subledger Accounting. See: Generate Cost Accounting Events and Create Accounting.

yes

Events having completion dates must be processed. See: Events.

yes

Accounting for revenue must be successfully created in Oracle Subledger Accounting. See: Generate Revenue Accounting Events and Create Accounting.

yes

Draft invoices must be interfaced to and accepted in Oracle Receivables. See: Interface Invoices to Receivables.

yes

Unbilled receivables and unearned revenue for the project must be zero. See: Reviewing Revenue.

yes

Project-related Receivables invoices must have a zero balance (that is, the invoice must be paid). Contract projects with invoices that have a balance due amount cannot be purged. See: Oracle Receivables Reference Guide.

yes

If you have chosen Purge Capital Data in the Purge Batch Details window, all asset lines must be generated and successfully interfaced to Oracle Assets. Also, all project-related assets must be posted in Oracle Assets. See: Generate Asset Lines and Interface Assets.

yes

AP discount lines must be interfaced to Oracle Projects. See: Interface Supplier Costs.

yes

All allocation runs must be in either the Release Success status or the Reversed status for any task of a project that is purged.

yes

All project-related supplier invoices in Oracle Payables must be fully paid.

yes

Project-related records in Oracle Time & Labor must be interfaced to Oracle Projects.

yes

The project must not be an Organization Forecast project. See: Organization Forecasting.

yes

Receipt accrual amounts for project-related purchase items must be interfaced to Oracle Projects. See: Revenue Accruals.

yes

All retentions must be billed and the retention balance must be zero. See: Customer Billing Retention.

yes

Project transactions must not be referenced in Oracle Project Contracts, Oracle Property Manager, or Oracle Commitment Administration.

Note: The summarization and burden cost distribution checks can be part of client extensions. The creation of a summarized burden component can be part of a client extension.

Prerequisites for Cross Charge Transactions in a Purge Batch

Cross charge transactions must meet the conditions shown in the following table before they can be purged or archived and purged.

Indirect Project	Contract Project	Capital Project	Condition
yes	yes	yes	Accounting for borrowed and lent transactions must be successfully created in Oracle Subledger Accounting. See: Generate Cross Charge Accounting Events and Create Accounting.
yes	yes		Cross charge projects can be purged after intercompany invoices are interfaced to Receivables and tied back to Projects.
	yes		Intercompany billing projects cannot be purged.
	yes		If the Reclassify Costs for Cross Charged Transactions option on the Internal Billing tab in Implementation Options is set to either Raw Cost or Burden Cost, then accounting for cross-charged transactions must be successfully created in Oracle Subledger Accounting. See: Generate Cross Charge Accounting Events and Create Accounting.
	yes		For inter-project billing, the provider project must be purged before purging any receiver project.
	yes		For inter-project billing, the provider project can be purged after draft invoices belonging to the provider project are interfaced to Receivables and transferred to Payables as supplier invoice costs for the receiver project.
yes	yes		For inter-project billing, if the receiver project is an indirect project, then it can be purged multiple times in a time phased manner.

yes

Accounting for borrowed and lent transactions must be successfully created in Oracle Subledger Accounting. See: Generate Cross Charge Accounting Events and Create Accounting.

yes

Cross charge projects can be purged after intercompany invoices are interfaced to Receivables and tied back to Projects.

yes

Intercompany billing projects cannot be purged.

yes

If the Reclassify Costs for Cross Charged Transactions option on the Internal Billing tab in Implementation Options is set to either Raw Cost or Burden Cost, then accounting for cross-charged transactions must be successfully created in Oracle Subledger Accounting. See: Generate Cross Charge Accounting Events and Create Accounting.

yes

For inter-project billing, the provider project must be purged before purging any receiver project.

yes

For inter-project billing, the provider project can be purged after draft invoices belonging to the provider project are interfaced to Receivables and transferred to Payables as supplier invoice costs for the receiver project.

yes

For inter-project billing, if the receiver project is an indirect project, then it can be purged multiple times in a time phased manner.

Prerequisites for Staffing Transactions in a Purge Batch

Staffing transactions must meet the conditions shown in the following table before they can be purged or archived and purged.

Indirect Project	Contract Project	Capital Project	Condition
yes			For open projects, requirements are not purged if an open requirement exists on the project with an end date earlier than the purge through date.
yes	yes	yes	For closed projects, the entire project is not purged if an assignment exists on the project with an end date later than the project close date.

yes

For open projects, requirements are not purged if an open requirement exists on the project with an end date earlier than the purge through date.

yes

For closed projects, the entire project is not purged if an assignment exists on the project with an end date later than the project close date.

Extend Archiving and Purging Requirements

In addition to the default prerequisites listed in the Data That You Can Purge table, you can create additional prerequisites for purging and archiving project data. See: Archive Purge Validation Extension, Oracle Projects APIs, Client Extensions, and Open Interfaces Reference.