Search Results project_type_class_m




Overview
Explore in AI Chat

Overview

APPS.PA_PROJECT_TYPE_CLASSES_V is a supplementary database view owned by the APPS schema in Oracle E-Business Suite 12.1.1 and 12.2.2. It is registered under the FND Design Data name PA.PA_PROJECT_TYPE_CLASSES_V and is currently documented with a VALID status. The view is classified as a "supplementary view used to simplify forms coding," a designation that places it within the family of Oracle Forms support objects rather than the public, supported data model. The ETRM documentation carries an explicit warning: Oracle does not recommend that customers query or alter data using this view, and its definition may change dramatically in subsequent minor or major releases. This means the view should be treated as an internal implementation artifact, not as a stable integration contract.

Functionally, PA_PROJECT_TYPE_CLASSES_V exposes the set of project type classification codes and their translated (meaning) descriptions, along with the date range during which each classification is active. In the Oracle Projects (PA) module, project type classes drive the categorization applied to project types, and the associated lookup values are validated through PA_LOOKUPS. The suffix "_M" on the PROJECT_TYPE_CLASS_M column reflects the standard Oracle EBS convention for the "meaning" or display value associated with a lookup code.

The search term "project_type_class_m" corresponds directly to this view's second column, PROJECT_TYPE_CLASS_M, which is the human-readable description paired with the coded value in PROJECT_TYPE_CLASS_CODE. Users searching on that term are typically attempting to join a project type class code to its descriptive text.

Underlying Base Objects

Per the ETRM dependency information, APPS.PA_PROJECT_TYPE_CLASSES_V references two base objects:

  • PA_LOOKUPS (VIEW) — the Oracle Projects lookup view that supplies the lookup code and its meaning, filtered by the appropriate lookup type for project type classes. This is the primary source of the PROJECT_TYPE_CLASS_CODE and PROJECT_TYPE_CLASS_M values.
  • PA_INSTALL (PACKAGE) — a package referenced by the view's defining query, typically for installation or multi-organization context checks. Its inclusion suggests the view may be filtered or conditioned on installation-level settings.

The view is not referenced by any database object, meaning no other view, package, or synonym depends on it. It is a terminal, leaf-level object used only at runtime by Oracle Forms. This reinforces its status as a presentation-layer convenience rather than part of a shared data model. Because the definition is layered over PA_LOOKUPS, changes to project type class lookups in the PA module flow through automatically to this view.

Key Columns

  • PROJECT_TYPE_CLASS_CODE (VARCHAR2, 30) — the coded identifier for a project type classification, sourced from the lookup set. This is the value stored in transaction tables and used in joins.
  • PROJECT_TYPE_CLASS_M (VARCHAR2, 80) — the meaning or descriptive label associated with the code. This is the column most often sought when users search for "project_type_class_m," typically to display a friendly name in reports or LOVs.
  • START_DATE_ACTIVE (DATE) — the date from which the classification code becomes effective.
  • END_DATE_ACTIVE (DATE) — the date until which the classification code remains effective; a null value generally indicates no scheduled end.

None of the columns are marked mandatory in the metadata, though the source lookup normally populates the code and meaning.

Common Use Cases and Queries

The most common practical use is retrieving the descriptive meaning for a project type class code, or listing all active classification values. Because Oracle discourages direct querying, the recommended approach in production is to resolve these values through PA_LOOKUPS directly or through approved Projects APIs. Where the view is used for validation or troubleshooting, the canonical query is:

SELECT PROJECT_TYPE_CLASS_CODE, PROJECT_TYPE_CLASS_M, START_DATE_ACTIVE, END_DATE_ACTIVE FROM APPS.PA_PROJECT_TYPE_CLASSES_V;

A typical active-value filter adds a date predicate, for example: WHERE SYSDATE BETWEEN START_DATE_ACTIVE AND NVL(END_DATE_ACTIVE, SYSDATE). A common join pattern pairs the code against a project type assignment column to render the classification description in a report or concurrent program output. Given the documented warning about release volatility, any custom code depending on this view should be isolated behind a wrapper query so that a future definition change can be absorbed without widespread refactoring.