Search Results pa_status_lists_v




Overview
Explore in AI Chat

Overview

The Oracle EBS view PA_STATUS_LISTS_V is a reporting and integration object owned by the APPS schema in the Projects (PA) module. It presents the definitional attributes of a project status list — the configurable container that groups the statuses a project status may progress through — and exposes those attributes in a denormalized, read-only form suited to inquiry screens, concurrent extracts, and interface programs. The view is documented as VALID in ETRM for Oracle EBS 12.1.1 and 12.2.2. Functionally, a status list defines an ordered set of statuses together with the starting status assigned when a project enters the lifecycle, and the view surfaces both the header attributes and the audit columns that Oracle EBS uses to track record-level change history. Since the underlying table is date-effectivity aware (START_DATE_ACTIVE, END_DATE_ACTIVE), the view supports reports that must distinguish currently active status lists from historical or retired definitions.

Underlying Base Objects

Per the documented metadata, PA_STATUS_LISTS_V is defined by a single SELECT over PA_STATUS_LISTS, which appears in the view definition as an APPS synonym resolving to the base table. No joins, unions, or aggregations are present in the view text; it is a straight column projection of the base table. Consequently, the view inherits the base table's date-effectivity behavior, its audit triggers, and its primary key on STATUS_LIST_ID, and it is subject to the same Multi-Org and security authorization that governs direct access to PA_STATUS_LISTS. Any row count or filter applied to the view is therefore identical to the corresponding query against the base table.

Key Columns

  • STATUS_LIST_ID — Primary key and unique identifier of the project status list.
  • STATUS_TYPE — Classifies the purpose of the status list (for example, the business process area to which the statuses belong), and is a primary selection and grouping attribute.
  • NAME — User-defined name of the status list as presented in the Projects setup and query screens.
  • DESCRIPTION — Free-text explanatory description of the list's intended use.
  • DEFAULT_STARTING_STATUS_CODE — The status code assigned by default when a project or project template is first associated with the list.
  • START_DATE_ACTIVE / END_DATE_ACTIVE — Effective date range within which the definition applies; a NULL end date indicates an open-ended, currently valid definition.
  • RECORD_VERSION_NUMBER — Optimistic locking and version indicator used by EBS concurrent processing and the Projects APIs to detect stale updates.
  • CREATION_DATE, CREATED_BY, LAST_UPDATE_DATE, LAST_UPDATED_BY, LAST_UPDATE_LOGIN — Standard Oracle EBS audit columns identifying who created and last modified the row, when, and through which login session.

Common Use Cases and Queries

The view is typically used to resolve a STATUS_LIST_ID to its name and default starting status, to drive LOV (list of values) queries in custom reports, and to feed integration extracts that populate external project governance or workflow systems. A representative lookup of currently active status lists is shown below.

  • Validation report of active status lists: SELECT status_list_id, status_type, name, default_starting_status_code, start_date_active FROM pa_status_lists_v WHERE TRUNC(SYSDATE) BETWEEN NVL(start_date_active, TRUNC(SYSDATE)) AND NVL(end_date_active, TRUNC(SYSDATE)) ORDER BY status_type, name;
  • Name and default status resolution for a known list: SELECT name, default_starting_status_code FROM pa_status_lists_v WHERE status_list_id = :p_status_list_id;
  • Audit extract for changed definitions: SELECT status_list_id, name, last_updated_by, last_update_date FROM pa_status_lists_v WHERE last_update_date >= :p_since_date;
  • Version check during interface processing: SELECT record_version_number FROM pa_status_lists_v WHERE status_list_id = :p_status_list_id;

Because the view exposes no status-line detail, queries that require the individual statuses within a list must join to the related status definition objects rather than relying on this view alone.