Search Results project_closed_date




Overview
Explore in AI Chat

Overview

APPS.PA_PURGE_PROJECTS_LOV_V is a supplementary Oracle EBS view owned by the APPS schema and registered under FND Design Data as PA.PA_PURGE_PROJECTS_LOV_V. Its status is VALID. Per the documented object details, this is a "supplementary view used to simplify forms coding," and Oracle explicitly warns that it does not recommend querying or altering data through it, because its definition may change dramatically in subsequent minor or major releases. It is therefore best understood as a forms-support construct rather than a stable, supported reporting interface.

Functionally, the view supplies the list of values presented by the Projects purge/cleanup form flow. It surfaces project identification, owning organization, status, project type, and — of direct relevance to users searching on "project_closed_date" — the PROJECT_CLOSED_DATE column. Because it is purge-oriented, the result set is filtered through PA_SECURITY and HR_SECURITY, meaning only projects visible to the current responsibility and organization hierarchy are returned. The view is not referenced by any other database object; it is a terminal, dependency-consuming object.

Underlying Base Objects

The documented dependencies of PA_PURGE_PROJECTS_LOV_V are as follows:

  • PA_PROJECTS (SYNONYM) — the primary project definition and header data.
  • PA_PROJECT_STATUSES (SYNONYM) — supplies the decoded PROJECT_STATUS value for a given PROJECT_STATUS_CODE.
  • PA_SECURITY (PACKAGE) — enforces project-level security, restricting rows to projects the current user may access.
  • HR_ORGANIZATION_UNITS (VIEW) — provides ORGANIZATION_NAME and ORGANIZATION_ID for the project's owning organization.
  • HR_GENERAL (PACKAGE) — resolves the current business group and related HR session context used by organization and security logic.
  • HR_SECURITY (PACKAGE) — applies organization-level (HR) security, complementing PA_SECURITY.

The combination of PA_SECURITY and HR_SECURITY means the view's row population is session-dependent, driven by FND_GLOBAL and HR session attributes rather than by a fixed predicate.

Key Columns

  • PROJECT_ID (NUMBER, 15) — unique project identifier; the key returned to the calling form.
  • PROJECT_NUMBER (VARCHAR2, 25) and PROJECT_NAME (VARCHAR2, 30) — the user-facing identifiers shown in the list of values.
  • ORGANIZATION_ID (NUMBER, 15) and ORGANIZATION_NAME (VARCHAR2, 240) — the owning/expenditure organization associated with the project.
  • PROJECT_STATUS_CODE (VARCHAR2, 30) — the stored status code on PA_PROJECTS.
  • PROJECT_STATUS (VARCHAR2, 80) — the decoded description from PA_PROJECT_STATUSES.
  • PROJECT_CLOSED_DATE (DATE) — the date the project was closed. This is the column most commonly used to qualify purge candidates, since purging is generally restricted to projects whose closure predates a cutoff.
  • PROJECT_TYPE (VARCHAR2, 20) — classifies the project (for example, contract, indirect, or capital).
  • ORG_ID (NUMBER, 15) — the operating unit (multi-org) identifier.

Common Use Cases and Queries

The principal use case is identifying closed projects eligible for purge, frequently filtered on PROJECT_CLOSED_DATE. A typical form-driven or diagnostic query is:

SELECT PROJECT_NUMBER, PROJECT_NAME, PROJECT_STATUS, PROJECT_CLOSED_DATE, ORGANIZATION_NAME
FROM APPS.PA_PURGE_PROJECTS_LOV_V
WHERE PROJECT_CLOSED_DATE < SYSDATE - 365
ORDER BY PROJECT_CLOSED_DATE;

A simpler lookup retrieves the project ID for a known number:

SELECT PROJECT_ID, PROJECT_NAME, PROJECT_STATUS_CODE, ORG_ID
FROM APPS.PA_PURGE_PROJECTS_LOV_V
WHERE PROJECT_NUMBER = :project_number;

Because PA_SECURITY and HR_SECURITY are applied, results depend on the connected responsibility, user, and operating unit. Queries executed as a privileged account or outside a properly initialized session may return no rows or an incomplete set. Given Oracle's documented warning that this view may change dramatically between releases, custom code should avoid hard-coded dependencies on it; for durable reporting, select directly from PA_PROJECTS joined to PA_PROJECT_STATUSES, HR_ORGANIZATION_UNITS, and the security packages, and apply the required ORG_ID context explicitly.