Search Results multiple_status_text




Overview
Explore in AI Chat

Overview

APPS.PA_REP_ASMT_SCH_STATUS_V is a reporting view in Oracle EBS Projects (PA) that consolidates project status and assignment status values used by the Project Status Inquiry and related reporting and integration components. Its purpose is to present a single, denormalized list of status codes and their display names that can appear on project assignment schedules, including both standard project statuses defined in PA_PROJECT_STATUSES and the special "MULTIPLE" status used when an assignment carries more than one concurrent status.

The view is defined as a UNION ALL of two queries. Because the object name contains the prefix PA_REP_ (reporting) and the suffix _V (view), it is intended for read-only consumption by reports, concurrent programs, OAF pages, and external integrations rather than for transactional DML. The view is owned by APPS and is therefore typically granted to reporting responsibilities and read-only integration schemas.

Underlying Base Objects

The documented base objects referenced by this view are:

The first branch of the UNION ALL joins PS.PROJECT_STATUS_CODE to ASMT.STATUS_CODE for assignments whose ASSIGNMENT_TYPE is not 'OPEN_ASSIGNMENT', returning the code and name from PA_PROJECT_STATUSES. The second branch joins PA_PROJECT_ASSIGNMENTS to PA_LOOKUPS where MULTIPLE_STATUS_FLAG = 'Y', producing the status code and the lookup meaning. Both branches apply a ROWNUM = 1 filter, which prevents duplicate rows and ensures a single representative row per status value.

Key Columns

  • PROJECT_STATUS_CODE / STATUS_CODE — the status identifier joined against PA_PROJECT_ASSIGNMENTS.STATUS_CODE. In the first branch it is PS.PROJECT_STATUS_CODE; in the second it is ASMT.STATUS_CODE (the MULTIPLE code).
  • PROJECT_STATUS_NAME / MEANING — the display text for the status. Standard statuses use PS.PROJECT_STATUS_NAME; the multiple-assignment case uses PL.MEANING from PA_LOOKUPS.

Although the UNION ALL columns are named differently in each branch, the first column of each SELECT supplies the status code and the second supplies its name; consumers should reference them positionally or via a column alias applied at the outer query.

Common Use Cases and Queries

Typical uses include populating status list-of-values on project assignment pages, resolving the display text for a status code returned by assignment queries, and validating that the MULTIPLE status lookup is present. A common query lists available statuses:

  • SELECT status_code, status_name FROM (SELECT PROJECT_STATUS_CODE status_code, PROJECT_STATUS_NAME status_name FROM APPS.PA_REP_ASMT_SCH_STATUS_V) ORDER BY 1;

To find the display text for a specific assignment's status:

  • SELECT a.status_code, v.status_name FROM APPS.PA_PROJECT_ASSIGNMENTS a, APPS.PA_REP_ASMT_SCH_STATUS_V v WHERE a.status_code = v.status_code AND a.assignment_type <> 'OPEN_ASSIGNMENT';

To locate the MULTIPLE status entry specifically, filter on the code returned by the second branch, which is driven by the MULTIPLE_STATUS_TEXT lookup. The ROWNUM = 1 predicates in both branches mean the view is not a full listing of all distinct statuses; it returns one row per qualifying status. Reports requiring complete assignment-status coverage should join to PA_PROJECT_STATUSES directly, using this view as the display-name convenience layer for the MULTIPLE case.