Results for “pa_next_allow_statuses”

AI-generated from documented ETRM metadata — verify critical details on the linked pages.

Overview

PA_NEXT_ALLOW_STATUSES is a reference configuration table in the Oracle Projects (PA) module of Oracle E-Business Suite. It defines the workflow of project status transitions by storing, for each defined project status, the set of statuses to which a project may legally move next. The table is key to enforcing the project lifecycle rules used throughout the Projects applications, including project setup, project management, and status-change processing.

The table operates in the PA schema and is classified as VALID across Oracle EBS 12.1.1 and 12.2.2. Under a heuristic Data Vault classification derived from its foreign-key structure, PA_NEXT_ALLOW_STATUSES is best modeled as a link table. It records relationships between pairs of statuses rather than holding descriptive attributes about a single business entity, which is characteristic of a link construct. This classification should be treated as a modeling suggestion, not an authoritative Oracle designation.

Key Information Stored

The table contains 24 documented columns, most of which are standard audit and descriptive flexfield attributes. The essential columns are:

• STATUS_CODE — the source or current status; a foreign key to PA_PROJECT_STATUSES.
• NEXT_ALLOWABLE_STATUS_CODE — the destination status that a project may transition into from STATUS_CODE; also a foreign key to PA_PROJECT_STATUSES.
• LAST_UPDATE_DATE, LAST_UPDATED_BY, CREATION_DATE, CREATED_BY, LAST_UPDATE_LOGIN — standard EBS who-column audit fields.
• ATTRIBUTE_CATEGORY and ATTRIBUTE1 through ATTRIBUTE15 — descriptive flexfield segments for extensible configuration.
• ZD_EDITION_NAME — the edition identifier used by the EBS 12.2 online patching architecture, enabling edition-specific rows during patching cycles.

No explicit surrogate primary key column is documented; the table functions with a composite business key. The unique index PA_NEXT_ALLOW_STATUSES_U1 spans (STATUS_CODE, NEXT_ALLOWABLE_STATUS_CODE, ZD_EDITION_NAME), making that triplet the business-key candidate and preventing duplicate transition definitions. Because the primary key is composite and both component columns are foreign keys, the row inherently links two status entries.

Common Use Cases and Queries

The primary use case is validating and rendering allowed project status transitions for user interfaces and APIs that change project status. Reporting on the transition graph supports lifecycle governance and audit reviews.

• List all allowable next statuses for a given status:

  SELECT next_allowable_status_code
  FROM   pa_next_allow_statuses
  WHERE  status_code = :status_code;
  

• Resolve the full transition matrix with descriptive status names:

  SELECT s.status_code, s.status_name, n.next_allowable_status_code
  FROM   pa_next_allow_statuses n,
         pa_project_statuses s
  WHERE  n.status_code = s.status_code;
  

• Identify terminal statuses (those with no outgoing transitions) to detect projects that can no longer change state.
• Validate a proposed status change before committing it, preventing invalid lifecycle jumps.

Because configuration drives behavior, the table is also consulted when examining why a status change was rejected in the Projects workflow.

Related Objects

The most significant dependencies are the status definitions with which this table joins. The documented foreign keys establish the following relationships:

• PA_PROJECT_STATUSES — referenced twice, via STATUS_CODE and NEXT_ALLOWABLE_STATUS_CODE; this is the primary companion table, supplying status names, descriptions, and system status flags.
• PA_PROJECTS — the projects whose lifecycle status changes are governed by these transition rules.
• PA_PROJECT_STATUSES (continued) — supports lookups that validate candidate transitions.
• Projects APIs and concurrent programs that perform status changes consult this table indirectly to enforce allowed movement.

Together these objects form the status-management component of the Oracle Projects data model, with PA_NEXT_ALLOW_STATUSES acting as the link that encodes permitted lifecycle paths between defined statuses.