Search Results event_type_classification




Overview
Explore in AI Chat

Overview

APPS.PA_EVENT_TYPES_RES_V is a reporting view in Oracle EBS Projects (Oracle Projects / ETRM) that exposes a filtered, resource-aware list of project event types. It is defined over the PA_EVENT_TYPES table and is restricted to event types whose EVENT_TYPE_CLASSIFICATION falls within the set AUTOMATIC, MANUAL, WRITE OFF, and WRITE ON. Because event types are central to revenue and billing generation, this view serves as the reference source for event type lookups used in revenue recognition, autoaccounting, and billing event processing.

The view is not a base table; it is a convenience layer that pre-applies the classification and date-effective filtering logic so that callers do not need to re-implement the same predicates. The suffix "_RES_V" signals a resource-oriented view, meaning the result set is constrained by the resource inclusion behavior driven by the PA_GET_RESOURCE package.

Underlying Base Objects

The view is defined over two documented referenced objects:

  • PA_EVENT_TYPES (SYNONYM) — the base table that stores event type definitions, including the classification, revenue category, description, and active date range columns selected by the view.
  • PA_GET_RESOURCE (PACKAGE) — referenced inside the WHERE clause to determine whether inactive resources should be included in the result set.

The relationship is one of projection and filtering: the view does not modify or aggregate base data; it returns a subset of PA_EVENT_TYPES rows with a fixed set of columns. The date-effective condition uses START_DATE_ACTIVE and END_DATE_ACTIVE. When PA_GET_RESOURCE.INCLUDE_INACTIVE_RESOURCES returns 'Y', the predicate compares START_DATE_ACTIVE against itself, effectively bypassing the current-date restriction and allowing inactive event types to appear. Otherwise, TRUNC(SYSDATE) is used, and only event types active as of the current date are returned.

Key Columns

  • EVENT_TYPE — the unique identifier/name of the event type, used as the primary lookup value in transaction and billing processing.
  • DESCRIPTION — the descriptive text associated with the event type.
  • EVENT_TYPE_CLASSIFICATION — the classification value that determines the behavior of the event type. The view restricts this column to AUTOMATIC, MANUAL, WRITE OFF, or WRITE ON. This is the column most directly relevant to searches for "event_type_classification."
  • REVENUE_CATEGORY_CODE — the revenue category associated with the event type, used to drive revenue accounting and reporting.
  • 'N', NULL, 'N' — three literal columns projected by the SELECT. These are constants rather than data columns, historically used to satisfy positional interfaces that expect a fixed column shape. Consumers should be aware they carry no real data.

Common Use Cases and Queries

Typical uses include validating which event types are active, driving LOV (list of values) queries in custom forms and reports, and joining event types to revenue or billing data. Because classification is a key filter, the view is commonly used to isolate write-off and write-on events for revenue adjustment analysis. A representative query:

  • SELECT event_type, description, event_type_classification, revenue_category_code FROM apps.pa_event_types_res_v WHERE event_type_classification = 'WRITE OFF';
  • SELECT event_type_classification, COUNT(*) FROM apps.pa_event_types_res_v GROUP BY event_type_classification;

Note that because the view invokes PA_GET_RESOURCE, its row count may vary depending on the session's resource inclusion setting, which makes it unsuitable as a stable source for full-table extracts. For complete event type inventories, query PA_EVENT_TYPES directly.