Results for “event_type_classification”

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

Overview

PA_EVENT_TYPE_CLASSES_V is a read-only view owned by the APPS schema in Oracle E-Business Suite, residing in the Projects (PA) product family. Its ETRM documentation classifies it with the description "10SC Only," indicating the object is relevant specifically to the 10SC (Project Manufacturing / Projects) reporting context rather than forming part of the core transactional data model. The view presents a controlled lookup list of event type classifications — the categorization values that group project events for cost, billing, and revenue processing.

Functionally, PA_EVENT_TYPE_CLASSES_V is a thin, filtered projection over the PA_LOOKUPS view. It exposes the subset of lookup rows whose LOOKUP_TYPE equals "EVENT TYPE CLASSIFICATION." Rather than surfacing the full lookup table, the view isolates the classification vocabulary used to associate event types with processing behavior. In EBS reporting and integration layers, such views serve as convenience access points: they allow forms, concurrent programs, and custom reports to retrieve valid event type classifications without replicating the LOOKUP_TYPE filter in every query.

Underlying Base Objects

The view is defined over a single documented base object: PA_LOOKUPS, itself a view in the APPS schema. The view text is straightforward:

• SELECT L.LOOKUP_CODE, L.MEANING, L.START_DATE_ACTIVE, L.END_DATE_ACTIVE
• FROM PA_LOOKUPS L
• WHERE L.LOOKUP_TYPE = 'EVENT TYPE CLASSIFICATION'

Because PA_LOOKUPS is a view rather than a physical table, the effective data source is the underlying lookup storage that PA_LOOKUPS projects. The view inherits no joins, aggregations, or additional filters beyond the lookup type restriction. This means PA_EVENT_TYPE_CLASSES_V is effectively a named, reusable WHERE-clause predicate — a lightweight semantic layer over the standardized Projects lookup mechanism.

Key Columns

• EVENT_TYPE_CLASSIFICATION (LOOKUP_CODE): The internal code value identifying a specific event type classification. This is the value typically stored as a foreign key reference on event type definitions.
• EVENT_TYPE_CLASS_M (MEANING): The user-facing, translatable description of the classification, displayed in LOVs and reports.
• START_DATE_ACTIVE: The date from which the classification becomes available for selection.
• END_DATE_ACTIVE: The date on which the classification is retired. A null value indicates the classification remains active.

The presence of active date columns is significant for reporting: queries that do not constrain on these dates may return historical classifications that are no longer valid for new event type assignments.

Common Use Cases and Queries

Typical uses include building value lists for event type setup forms, validating imported event type definitions, and driving conditional logic in cost or revenue event processing reports.

To list all classifications regardless of status:

• SELECT event_type_classification, event_type_class_m FROM pa_event_type_classes_v;

To restrict to currently active classifications at a point in time:

• SELECT event_type_classification, event_type_class_m FROM pa_event_type_classes_v WHERE TRUNC(SYSDATE) BETWEEN NVL(start_date_active, TRUNC(SYSDATE)) AND NVL(end_date_active, TRUNC(SYSDATE));

Because the view performs no joins, performance is governed entirely by PA_LOOKUPS and the selectivity of LOOKUP_TYPE. Custom code should treat these rows as reference data and cache them where appropriate rather than querying per transaction.