Search Results gen_projects




Overview
Explore in AI Chat

Overview

PA_PURGE_PROJECTS_GEN_PKG is an Oracle Projects (PA) PL/SQL package owned by the APPS schema. It supports the Project Purge functional area within Oracle E-Business Suite 12.1.1 and 12.2.2, providing the programmatic engine behind the purging of project-related data. Purging is an administrative housekeeping activity that permanently removes obsolete, archived project records and their associated summary, budgetary, capital, and actual transaction balances from the operational tables, freeing storage and improving system performance.

The package is classified under the ETRM API classification "OTHER," meaning it is treated as an internal implementation package rather than a published, externally callable public API. The header comment ($Header: PAXPRGNS.pls 120.1 2005/08/19) shows the source file has been relatively stable since the 11i era, which is consistent with the mature nature of the Project Purge feature set. The package contains no membership in a public API family and is referenced by no other packages, confirming its role as a leaf-level processing unit invoked directly by the purge concurrent program or its driver logic.

Key Procedures and Functions

The ETRM metadata documents two procedures within this package:

  • GEN_PROJECTS — The primary worker procedure. It performs the generation and selection of project records eligible for purge based on the caller-supplied purge criteria, including the purge batch identifier, the active/closed project flag, the closed-through date, organization identifier, project type, project status code, and transaction-to-date date. It accepts a set of purge and archive flag pairs governing summary, budget, capital, and actual balances, plus an administrative-project flag and the next project/project-status code to be applied during the purge lifecycle. It returns the number of records processed through the x_no_recs OUT parameter. The procedure is declared with NOCOPY for the OUT parameter, a performance optimization noted against bug 4440895.
  • GET_PURGE_OPTIONS — A helper procedure that derives and returns the effective purge options for a given project. Given a project identifier and the active/closed flag, it returns the transaction-to-date date and the purge/archive indicator flags for actuals, budgets, capital, and summary balances. This allows the purge process to determine the applicable purge configuration rather than requiring the caller to supply every flag explicitly.

Tables Accessed

Referenced tables (via APPS synonyms) include:

  • PA_PROJECTS_ALL — The primary project master table, read and updated to identify and mark projects for purge, including application of the next project status code.
  • PA_PROJECT_TYPES — Read to resolve and validate the project type criterion used in the purge selection logic.
  • PA_PURGE_PROJECTS — The purge staging/tracking table that records projects submitted for purge and their batch association, central to the purge workflow.
  • DBMS_SQL — The Oracle-supplied dynamic SQL package, used where dynamic statement construction is required for flexible purge criteria.
  • DUAL — Used for single-row evaluations and utility queries.

Usage Notes

This package is not intended for direct invocation by end users or general custom code. It is typically called from the Project Purge concurrent program or from a thin driver procedure that gathers purge criteria, invokes GEN_PROJECTS to process eligible projects, and then relies on GET_PURGE_OPTIONS to resolve per-project purge and archive flags. Because the package is an internal implementation unit with no dependent packages, customizations should avoid calling it directly; instead, customers should use the supported Project Purge concurrent program or the documented Oracle Projects purge interface. Any direct use is at the customer's own risk, since the signature and behavior are not governed by Oracle's public API policy.