Search Results all_except_closed




Overview

PA_PROJ_STATUSES_V is a predefined Oracle E-Business Suite view owned by the APPS schema within the Projects (PA) product family. As documented in the ETRM metadata, it "provides the project statuses" available to the application. The view delivers a consolidated, query-friendly list of project statuses that can be assigned to projects, along with their associated system status codes, workflow configuration, and lifecycle attributes. Because it is a view rather than a base table, it presents a read-optimized projection and does not itself store data.

A key characteristic of the view is that it is a UNION ALL construct. It combines project-level statuses defined in the underlying statuses entity (filtered by STATUS_TYPE = 'PROJECT') with two special lookup-based pseudo-statuses drawn from the PROJECT STATUS lookup type. This design allows reporting and integration logic to treat the standard statuses and the special selection entries ('ALL' and 'ALL_EXCEPT_CLOSED') through a single consistent interface.

Underlying Base Objects

The ETRM metadata documents two referenced base objects: PA_LOOKUPS (VIEW) and PA_PROJECT_STATUSES (SYNONYM). The view text confirms these dependencies through its two UNION ALL branches.

  • PA_PROJECT_STATUSES supplies the primary set of rows, restricted by STATUS_TYPE = 'PROJECT'. This branch contributes all standard project statuses, including workflow-related columns that are meaningful only for genuine statuses.
  • PA_LOOKUPS supplies supplemental rows where LOOKUP_TYPE = 'PROJECT STATUS' and LOOKUP_CODE is 'ALL' or 'ALL_EXCEPT_CLOSED'. These rows reuse lookup columns (LOOKUP_CODE, MEANING, DESCRIPTION) in place of the status columns and are hard-coded with neutral values such as STATUS_TYPE = 'PROJECT', PREDEFINED_FLAG from the lookup, and 'N' for STARTING_STATUS_FLAG and ENABLE_WF_FLAG.

Because PA_PROJECT_STATUSES appears as a synonym, the view resolves through the APPS synonym layer at runtime.

Key Columns

Common Use Cases and Queries

Typical scenarios include populating status-of-value lists in reports or integrations, identifying which statuses are Oracle-seeded versus customer-defined, and driving workflow-aware status transitions.

Listing predefined project statuses:

  • SELECT PROJECT_STATUS_CODE, PROJECT_STATUS_NAME FROM PA_PROJ_STATUSES_V WHERE PREDEFINED_FLAG = 'Y';

Listing statuses valid as a starting status:

  • SELECT PROJECT_STATUS_CODE, PROJECT_STATUS_NAME FROM PA_PROJ_STATUSES_V WHERE STARTING_STATUS_FLAG = 'Y';

Retrieving workflow-enabled statuses:

  • SELECT PROJECT_STATUS_CODE, WORKFLOW_ITEM_TYPE, WORKFLOW_PROCESS FROM PA_PROJ_STATUSES_V WHERE ENABLE_WF_FLAG = 'Y';

Because the view unions standard statuses with the 'ALL' and 'ALL_EXCEPT_CLOSED' lookup entries, queries should apply appropriate filters when only genuine project statuses are required.