Search Results pa_status_lists




Overview
Explore in AI Chat

Overview

PA_STATUS_LISTS is a Projects (PA) module table that stores the attributes of a project status list. In Oracle EBS 12.1.1 and 12.2.2, project status lists define the ordered set of statuses a project, task, or other project-related entity may pass through during its lifecycle. The table acts as the controlling header that groups individual status entries and binds them to a status type, a unique name, and a validity window.

From a data-modeling perspective, the metadata's heuristic Data Vault classification is hub-leaning. This is a modeling suggestion: PA_STATUS_LISTS behaves as a hub because it carries a surrogate primary key (STATUS_LIST_ID) whose business identity is reflected in the unique index PA_STATUS_LISTS_U2 (STATUS_TYPE, NAME, ZD_EDITION_NAME). Dependent attributes such as dates and the default starting status code would conventionally be modeled as satellite data around that hub in a Data Vault design.

Key Information Stored

The documented physical schema contains 14 columns. The most significant are summarized below.

  • STATUS_LIST_ID — the surrogate primary key (PST_PK), uniquely identifying each status list. This is the column referenced by all foreign-key relationships.
  • STATUS_TYPE — the entity type the list applies to (for example, a project or a task), functioning as the category discriminator for the list.
  • NAME — the business name of the status list. Together with STATUS_TYPE, it forms the business-key candidate defined by the unique index PA_STATUS_LISTS_U2.
  • RECORD_VERSION_NUMBER — the optimistic locking / version column used to detect concurrent updates.
  • START_DATE_ACTIVE and END_DATE_ACTIVE — the effective date range during which the status list is active. Records outside this window are treated as inactive.
  • DEFAULT_STARTING_STATUS_CODE — the status code assigned by default when a new entity is created under this list.
  • DESCRIPTION — free-text description of the list's purpose.
  • ZD_EDITION_NAME — the editioning column introduced with the EBS 12.2 online patching (editions) architecture; it participates in both unique indexes.
  • Audit columns — CREATION_DATE, CREATED_BY, LAST_UPDATE_DATE, LAST_UPDATED_BY, and LAST_UPDATE_LOGIN capture who created and last modified each row.

A second unique index, PA_STATUS_LISTS_U1 (STATUS_LIST_ID, ZD_EDITION_NAME), reinforces the primary key within the editioning framework.

Common Use Cases and Queries

Typical scenarios include validating which statuses are permitted for a project, reporting on the default starting status by status type, and auditing the active configuration of status lists. A basic lookup by name and type takes the following form:

  • SELECT status_list_id, name, status_type, default_starting_status_code FROM pa_status_lists WHERE status_type = :p_type AND name = :p_name AND SYSDATE BETWEEN start_date_active AND NVL(end_date_active, SYSDATE + 1);
  • Listing the individual statuses within a list by joining the detail table: SELECT i.* FROM pa_status_list_items i, pa_status_lists l WHERE i.pst_status_list_id = l.status_list_id AND l.name = :p_name;
  • Identifying all lists assigned to an entity via PA_OBJ_STATUS_LISTS: SELECT o.* FROM pa_obj_status_lists o, pa_status_lists l WHERE o.status_list_id = l.status_list_id;
  • Audit reporting on creation and last update activity using CREATED_BY, CREATION_DATE, LAST_UPDATED_BY, and LAST_UPDATE_DATE.

Related Objects

The following objects reference or depend on PA_STATUS_LISTS through the documented foreign-key relationships.

  • PA_STATUS_LIST_ITEMS — the primary dependent child, joined on PA_STATUS_LIST_ITEMS.PST_STATUS_LIST_ID = PA_STATUS_LISTS.STATUS_LIST_ID; it holds the individual statuses belonging to each list.
  • PA_OBJ_STATUS_LISTS — associates status lists with project objects, joined on PA_OBJ_STATUS_LISTS.STATUS_LIST_ID = PA_STATUS_LISTS.STATUS_LIST_ID.
  • PA_STATUS_LIST_ITEMS (STATUS_LIST_ID) — a second documented foreign-key path from the same child table, reinforcing the header-to-detail dependency.

These relationships confirm that PA_STATUS_LISTS functions as the parent hub from which status list items and object-to-list assignments derive their identity.