Search Results pa_purge_validate




Overview
Explore in AI Chat

Overview

PA_PURGE_VALIDATE is an Oracle E-Business Suite PL/SQL package owned by the APPS schema that supports the Project Purge process, one of the most sensitive administrative operations in Oracle Projects. Project purge physically removes project-related data from the transactional tables after the project has been closed, and the operation is governed by a batch-driven framework that verifies a project is eligible for deletion before any rows are removed. PA_PURGE_VALIDATE supplies that eligibility layer. It validates candidate projects against purge rules, records validation failures in a purge error repository, and works alongside the batch that identifies and stages projects for removal.

The package is classified in the ETRM metadata as a non-API ("OTHER") program unit. It is not published as a public integration interface; rather it is an internal component consumed by the Oracle Projects purge infrastructure. It maintains dependencies only on the SYS.STANDARD package and the APPS synonyms of the purge and project tables, confirming that its logic is restricted to validation and error logging rather than data manipulation on transactional tables.

Key Procedures and Functions

Two procedures are documented for this package.

  • BATCHVAL — Performs validation for a purge batch. It evaluates the projects associated with a given batch against the rules that determine whether a project may be purged, and it identifies the projects that fail those checks. Results are routed to the error-recording logic so that failures can be reviewed and reported. No parameter list is documented; specific arguments should be confirmed against the deployed package specification.
  • INSERT_ERRORS — Persists validation failures by inserting rows into the purge project error table. This procedure gives the batch a durable audit trail: rather than aborting silently, PA_PURGE_VALIDATE records which project failed, together with the associated batch context, so users can correct the condition and re-run the purge.

Tables Accessed

The documented table references are consistent with a validation-only role.

  • PA_PURGE_BATCHES — the header table for a purge batch; supplies batch context and status used to determine which projects are in scope for validation.
  • PA_PURGE_PROJECTS — the list of projects staged within a batch for purging; the primary subject of the validation checks.
  • PA_PURGE_PROJECT_ERRORS — written by INSERT_ERRORS to record failed validations and their causes.
  • PA_PROJECTS / PA_PROJECTS_ALL — the project definition and its multi-organization (operating unit) view, read to confirm the project exists in the required context.
  • PA_PROJECT_TYPES / PA_PROJECT_TYPES_ALL — project type classification, used to evaluate whether a given project type is eligible for purge.

Usage Notes

PA_PURGE_VALIDATE is normally invoked indirectly. The ETRM dependency list shows it is referenced by PA_PAXARPVD_XMLP_PKG, the structure underpinning the purge validation report concurrent program, and by the implementation packages PA_PROJECT_UTILS2, PA_PURGE_VALIDATE_CAPITAL, and other purge-related units. In practice, a batch is created for the purge, the validation step runs to populate PA_PURGE_PROJECT_ERRORS, and the report is reviewed to correct blocking conditions before the purge is committed.

Because this package is not documented as an API, custom code should not bind directly to it. Organizations requiring purge validation should drive the standard purge batch and report concurrent programs and inspect PA_PURGE_PROJECT_ERRORS for outcomes. Any direct call would depend on an undocumented signature and could break on upgrade between 12.1.1 and 12.2.2.