Results for “project_status_code”

50+ results




Overview
Explore in AI Chat

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

Overview

PA_PROJECTS_V_PAXTRAPE is an APPS-owned database view in the Oracle E-Business Suite Projects (PA) module. It exists solely to support a specific functional requirement tracked under Bug 2556167, and is documented as being reserved for use as a record group definition within the PAXTRAPE concurrent program / form context. It is not a general-purpose reporting view and should not be treated as a supported public interface.

The view presents a consolidated, filtered list of projects suitable for expenditure inquiry processing. Each row exposes the project number, name, internal ID, type classification, status code, operating unit, and ledger organization ID. Its defining characteristic is that it applies security and status filtering logic at query time rather than relying on the caller to do so.

The basis of this filtering is twofold. First, it excludes project templates by testing TEMPLATE_FLAG <> 'Y'. Second, it invokes PA_PROJECT_STUS_UTILS.IS_PROJECT_IN_PURGE_STATUS to remove any project currently in a purge status. It also conditions the UNION ALL branches on the session mode returned by PA_EXPENDITURE_INQUIRY.GET_MODE, so that only the appropriate project population is returned for the current inquiry context.

Underlying Base Objects

The view text unions two pre-built views: PA_PROJECTS_BASIC_V (filtered for template exclusion) and PA_PROJECTS_ALL_BASIC_V. Both are themselves secured views over the PA_PROJECTS and PA_PROJECTS_ALL tables respectively, and inherit organization and security filtering from the PA security packages.

The documented referenced objects include the security and utility packages that underpin the runtime filtering: PA_SECURITY, PA_PROJECT_UTILS, PA_PROJECT_STUS_UTILS, PA_CROSS_BUSINESS_GRP, PA_EXPENDITURE_INQUIRY, and MO_GLOBAL. Multi-organization and HR security context is resolved through FND_PROFILE, HR_SECURITY, HR_GENERAL, HR_ORGANIZATION_INFORMATION, and PA_CC_ORG_RELATIONSHIPS. Configuration is read from PA_IMPLEMENTATIONS.

Key Columns

  • PROJECT_ID — Surrogate primary key from PA_PROJECTS_ALL; the join key to all project-related tables.
  • PROJECT_NUMBER — User-visible project identifier, typically concatenated with PROJECT_NAME in list-of-values displays.
  • PROJECT_NAME — Descriptive project name.
  • PROJECT_TYPE_CLASS_CODE — Classification of the project (for example, contract, indirect, or capital), used to drive behavior in expenditure inquiry.
  • PROJECT_STATUS_CODE — The current lifecycle status of the project. This is the column most relevant to the originating search: valid values mirror those defined in PA_PROJECT_STATUSES (for example, APPROVED, CLOSED, PENDING_CLOSE, REJECTED). The view excludes rows where this status evaluates to a purge state.
  • ORG_ID — Operating unit identifier, used for multi-org filtering.
  • OPERATING_UNIT — The name of the operating unit resolved from organization data.

Common Use Cases and Queries

The intended use is as a record group source for the PAXTRAPE expenditure inquiry flow, typically reached through Oracle Forms or a concurrent request rather than by direct user SQL. Because mode and security filtering are resolved at runtime, the query returns different results depending on profile values and the logged-in responsibility.

A representative query resembles the following:

  • SELECT project_number, project_name, project_status_code, operating_unit
  • FROM apps.pa_projects_v_paxtrape
  • WHERE project_status_code = 'APPROVED'
  • ORDER BY project_number;

This returns only approved projects visible to the current mode and organization context, excluding templates and purged projects. Analysts should note the view is not documented as a supported API and may change without notice across releases; direct dependency is discouraged outside its original Bug 2556167 scope.