Search Results pa_event_types_res_v




Overview
Explore in AI Chat

Overview

PA_EVENT_TYPES_RES_V is an Oracle Applications (APPS) view in the Projects (PA) module that exposes a filtered, resource-aware list of project event types. According to the ETRM metadata, the object is a VIEW owned by the APPS schema with VALID status, and its documentation describes it as "10Sc Only," indicating it was introduced for or aligned with Release 10SC functionality and retained for backward compatibility. In Oracle EBS 12.1.1 and 12.2.2 the view remains a lightweight presentation layer over the PA_EVENT_TYPES table, providing a restricted set of event types and a normalized column layout suited to reporting and integration.

The view's principal role is to present only event types whose classification falls within the Automatic, Manual, Write Off, or Write On categories, and to honor the resource inclusion profile established by the PA_GET_RESOURCE package. This makes it useful wherever a report or interface must treat inactive event types differently based on user or site-level preferences.

Underlying Base Objects

The documented base objects referenced by the view are PA_EVENT_TYPES (exposed through a synonym) and the PA_GET_RESOURCE package. The view text selects from PA_EVENT_TYPES and applies two filters:

  • A classification filter restricting rows to EVENT_TYPE_CLASSIFICATION values of 'AUTOMATIC', 'MANUAL', 'WRITE OFF', or 'WRITE ON'.
  • A date-effectiveness filter using DECODE on PA_GET_RESOURCE.INCLUDE_INACTIVE_RESOURCES. When the profile option is 'Y', the comparison uses START_DATE_ACTIVE; otherwise it uses TRUNC(SYSDATE), and the value must fall between START_DATE_ACTIVE and NVL(END_DATE_ACTIVE, TRUNC(SYSDATE)).

The dependency on PA_GET_RESOURCE means the view effectively joins to resource-level configuration at query time rather than materializing those rules.

Key Columns

The view exposes seven columns. Four are drawn directly from PA_EVENT_TYPES:

  • EVENT_TYPE — the identifier of the event type.
  • DESCRIPTION — the descriptive name of the event type.
  • EVENT_TYPE_CLASSIFICATION — the category (Automatic, Manual, Write Off, Write On).
  • REVENUE_CATEGORY_CODE — the associated revenue category.

The remaining three columns are literals: TRACK_AS_LABOR_FLAG is hard-coded to 'N', UNIT_OF_MEASURE is NULL, and ROLLUP_QUANTITY_FLAG is hard-coded to 'N'. These constants preserve a consistent column shape for consumers that expect the full resource event-type interface, while signaling that labor tracking and quantity rollup are not applicable in this context.

Common Use Cases and Queries

The view is typically used in reporting, LOV definitions, and integration extracts where only active, revenue-relevant event types are required. A basic query is:

  • SELECT event_type, description, event_type_classification, revenue_category_code FROM apps.pa_event_types_res_v ORDER BY event_type;

A more targeted query filters by classification:

  • SELECT event_type, description FROM apps.pa_event_types_res_v WHERE event_type_classification = 'MANUAL';

Because the effectiveness filter depends on PA_GET_RESOURCE, results vary with the INCLUDE_INACTIVE_RESOURCES profile setting, and administrators should confirm that behavior when reconciling counts against PA_EVENT_TYPES directly.