Results for “project_system_status_code”

50+ results




Overview
Explore in AI Chat

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

Overview

PA_PROJECT_STATUSES_V is a reporting view owned by the APPS schema within the Oracle E-Business Suite Projects (PA) module. Its documented purpose is to present the set of "control item statuses" available to Oracle Projects. In Oracle Projects, a project progresses through a series of statuses (for example, Submitted, Approved, Rejected, On Hold, Closed). These statuses are classified internally by a discriminator column, STATUS_TYPE, which distinguishes control item statuses from other status categories. PA_PROJECT_STATUSES_V is defined as a restricted projection over the base table PA_PROJECT_STATUSES filtered by the predicate STATUS_TYPE = 'CONTROL_ITEM'.

Because the view eliminates all non-control-item rows at the definition level, it acts as a stable, read-only interface for reports, concurrent programs, custom forms, and integration interfaces that require only control item statuses. It is classified as VALID in the data dictionary, indicating that the underlying definition is compiled and available in both Oracle EBS 12.1.1 and 12.2.2 environments. Users searching on "status_type" encounter this view precisely because the STATUS_TYPE column is the defining filter of the view and is also exposed as a selectable column in its projection.

Underlying Base Objects

The documented base object for this view is PA_PROJECT_STATUSES, referenced through the APPS-owned synonym. The relationship is one of projection and restriction: the view selects a fixed list of columns from the base table and applies a single WHERE predicate on STATUS_TYPE. No joins, aggregations, or set operators are documented, so the view carries no additional performance cost relative to a direct query against the base table with the equivalent filter.

Adding the STATUS_TYPE predicate offers two important consequences. First, it enforces semantic scoping — consumers can never inadvertently retrieve non-control-item statuses. Second, it reduces the number of rows returned, which benefits report queries and List of Values definitions that target control item workflows. Because the view is a simple projection, DML against it is not intended; the base table should be treated as the maintenance point for status definitions.

Key Columns

Common Use Cases and Queries

The view is most commonly used to populate status List of Values, to constrain status-driven workflow logic in reports, and to drive conditional formatting based on PROJECT_STATUS_WEIGHT or STATUS_ICON_IND. Typical consumers include custom Oracle Reports, BI Publisher data templates, and OAF or Forms-based extensions in the Projects module.

Retrieve all active control item statuses ordered by weight:

SELECT project_status_code, project_status_name, project_system_status_code, project_status_weight
FROM apps.pa_project_statuses_v
WHERE (start_date_active IS NULL OR start_date_active <= SYSDATE)
AND (end_date_active IS NULL OR end_date_active >= SYSDATE)
ORDER BY project_status_weight;

Identify predefined versus user-defined statuses:

SELECT project_status_code, project_status_name, predefined_flag
FROM apps.pa_project_statuses_v
WHERE predefined_flag = 'Y';

Check workflow-enabled statuses and their success transitions:

SELECT project_status_code, workflow_item_type, workflow_process,
      wf_success_status_code, wf_failure_status_code
FROM apps.pa_project_statuses_v
WHERE enable_wf_flag = 'Y';

Because the view restricts rows by STATUS_TYPE = 'CONTROL_ITEM', queries against it are naturally scoped and require no additional status-type predicate, although including one explicitly supports self-documenting SQL.