Search Results event_type_class_m

Overview

APPS.PA_EVENT_TYPE_CLASSES_V is a supplementary database view registered in the Oracle E-Business Suite Applications (APPS) schema. It is owned by APPS, carries the FND Design Data reference PA.PA_EVENT_TYPE_CLASSES_V, and holds VALID status in the Oracle ETRM 12.2.2 documentation. The view is classified as a "supplementary view used to simplify forms coding." As such, it exists primarily to support Oracle Projects forms and internal processing logic rather than to serve as a public data-access interface. Oracle explicitly warns that it does not recommend querying or altering data through this view, because its definition may change dramatically in subsequent minor or major releases.

The name of the view, together with the search term "event_type_class_m", indicates its function: it exposes the classification values and translated meanings (the "_M" or "meaning" values) associated with Oracle Projects event types. It presents a denormalized, forms-friendly projection of event type classification codes so that Oracle Forms-based components can display the classification and its user-facing meaning without performing an explicit lookup join at runtime.

Underlying Base Objects

Per the ETRM dependency metadata, APPS.PA_EVENT_TYPE_CLASSES_V references a single documented base object: APPS.PA_LOOKUPS, itself a view. PA_LOOKUPS is the Oracle Projects lookup view and is the mechanism through which the view derives the "_M" (meaning) column, EVENT_TYPE_CLASS_M. The lookup type underlying this mapping corresponds to the event type classification lookup, which is why the view exposes both the code (EVENT_TYPE_CLASSIFICATION) and its translated meaning. The view is in turn referenced by APPS.PA_RESOURCE_TXN_ATTRIBUTES_V, indicating that it participates in the resource transaction attribute code path within Oracle Projects. Because the dependency chain terminates at lookup infrastructure rather than at transactional base tables, the view is lightweight and read-only in nature; it carries no persistence of its own.

Key Columns

• EVENT_TYPE_CLASSIFICATION (VARCHAR2, 30) — The classification code assigned to an Oracle Projects event type. This is the stored lookup code value.
• EVENT_TYPE_CLASS_M (VARCHAR2, 80) — The translated meaning (display name) of the classification code, resolved through the PA_LOOKUPS view. The "_M" suffix follows the standard Oracle EBS convention for meaning columns used in forms list-of-values and descriptive display.
• START_DATE_ACTIVE (DATE) — The date from which the classification becomes active.
• END_DATE_ACTIVE (DATE) — The date on which the classification becomes inactive. A null value in this column conventionally indicates that the classification remains active with no scheduled expiration.

The active-date columns allow forms and validation logic to filter to classifications that are effective for a given transaction date, which is essential when historical event records must be interpreted against the classifications valid at the time of entry.

Common Use Cases and Queries

The principal use case is the display of event type classifications with their translated meanings in Oracle Projects forms and in dependent views such as PA_RESOURCE_TXN_ATTRIBUTES_V. Typical SQL retrieves only currently active classifications, ordering by the display meaning:

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

Because the view is documented as a forms-support construct, the recommended approach for a stable integration interface is to read the equivalent classification values directly from the Oracle Projects lookup definitions rather than binding custom code to this view. Where the view is queried for diagnostic or reporting purposes, it should be treated as read-only, and any dependency should be reviewed before applying Oracle Projects patches or upgrades, given Oracle's explicit caution that the view definition may change significantly between releases.