Search Results pa_class_categories_lov_v




Overview
Explore in AI Chat

Overview

PA_CLASS_CATEGORIES_LOV_V is an Oracle EBS database view owned by the APPS schema and registered against the PA (Projects) product family. It is classified as a VALID database object in both EBS 12.1.1 and 12.2.2. The view functions as a list-of-values (LOV) data source, exposing the implementation-defined combinations of class categories and class codes that are currently active within an Oracle Projects installation.

Its practical role is to supply valid, date-effective selection lists to Oracle Forms-based Project Accounting screens (for example, class code assignment and project classification entry), and to provide a convenient read-only query surface for reporting and integration. Because the view pre-applies the enabled/active date filter, consumers are not required to re-derive the effective-date logic themselves. The view is not a transactional table; it is a presentation layer over the underlying validation data, intended for lookups and descriptive reporting rather than for maintaining classification definitions.

Underlying Base Objects

The view is defined over a single base object, PA_CLASS_CODES, which is exposed to the APPS schema through a synonym. Its documented view text is:

SELECT CLASS_CATEGORY, CLASS_CODE, DESCRIPTION
FROM   PA_CLASS_CODES
WHERE  TRUNC(SYSDATE) BETWEEN START_DATE_ACTIVE
                        AND NVL(END_DATE_ACTIVE, TRUNC(SYSDATE))

PA_CLASS_CODES is the Projects table that stores the implementation-defined class codes and the class categories to which they belong, along with effective start and end dates. The view therefore inherits the key characteristics of that table while adding a system-date filter. Only rows whose active window covers the current date (TRUNC(SYSDATE)) are returned; rows with an END_DATE_ACTIVE of NULL are treated as open-ended and remain visible. Rows that have expired are automatically excluded. This makes the view a "currently effective" projection of PA_CLASS_CODES rather than a full listing of all historically defined values.

Key Columns

  • CLASS_CATEGORY — The implementation-defined class category that groups related class codes. It drives the LOV partitioning and is typically the first field a user selects.
  • CLASS_CODE — The individual class code defined within the category. In the view text this column is selected from CLASS_CODE; the documented column list refers to it as CODE, reflecting the column alias/name presented in some ETRM extracts.
  • DESCRIPTION — The descriptive text associated with the class code, providing the user-facing label in LOV and report output.

No date columns are exposed through the view; the effective-date logic is applied internally and is intentionally hidden from consumers. Only the three descriptive columns above are projected.

Common Use Cases and Queries

The view is most frequently used to populate class category and class code LOVs, to validate lookup values during data conversion, and to generate reference listings for classification reporting. The following queries illustrate typical usage:

-- List all currently effective class categories and codes
SELECT class_category, class_code, description
FROM   apps.pa_class_categories_lov_v
ORDER  BY class_category, class_code;

-- Restrict to a single class category
SELECT class_code, description
FROM   apps.pa_class_categories_lov_v
WHERE  class_category = :p_category;

-- Distinct category listing for LOV headers
SELECT DISTINCT class_category
FROM   apps.pa_class_categories_lov_v
ORDER  BY class_category;

Because the view returns only active rows, it is well suited as a validation source in inbound interfaces: a code that is absent from this view is either undefined or expired and should be rejected or flagged. For historical or full lifecycle analysis of classification definitions, query PA_CLASS_CODES directly, since the view deliberately omits inactive rows.