Results for “pa_event_types”

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

Overview

PA_EVENT_TYPES is the implementation-defined classification master for project events in Oracle Projects (PA). The table stores the valid event type codes that control how billing events, revenue-generating events, and resource-driven transactions are categorized, processed, and reported throughout the Projects suite. Because the repository classifies this object as a hub in a Data Vault style model, it functions as the central business-key reference point from which many dependent satellites, links, and transactional tables radiate. Its role is analogous to a lookup/validation table: before an event can be created, billed, accumulated, or applied against a retention rule, the event must be classified with a valid EVENT_TYPE defined in this table.

The object exists identically in Oracle EBS 12.1.1 and 12.2.2, owned by the PA schema. It is described in ETRM as containing "Implementation-defined classifications of events," confirming that the row content is created and maintained by the implementing organization rather than seeded entirely by Oracle.

Key Information Stored

The documented physical schema contains 28 columns. The most material columns are:

• EVENT_TYPE — the business-key identifier and column of unique index PA_EVENT_TYPES_U1; this is the value referenced by downstream transactional tables.
• EVENT_TYPE_ID — a second unique key column (index PA_EVENT_TYPES_U2), providing a surrogate identifier used internally and for cross-reference to external accounting event types.
• EVENT_TYPE_CLASSIFICATION — classifies the event type, driving how the event is treated in billing and revenue processing.
• REVENUE_CATEGORY_CODE — associates the event type with a revenue category for accounting and reporting.
• START_DATE_ACTIVE and END_DATE_ACTIVE — define the effective date range during which the event type is usable, enabling date-effective behavior.
• DESCRIPTION — the user-facing name or description presented in Oracle Projects forms.
• LAST_UPDATE_DATE, LAST_UPDATED_BY, CREATION_DATE, CREATED_BY, LAST_UPDATE_LOGIN — standard Oracle WHO columns providing audit and concurrency information.
• ATTRIBUTE_CATEGORY and ATTRIBUTE1 through ATTRIBUTE15 — the standard Oracle flexfield/descriptive attribute set for implementation-specific extensions.

The primary key is PA_EVENT_TYPES_PK, defined on EVENT_TYPE. The metadata also documents a foreign key from PA_EVENT_TYPES.EVENT_TYPE_ID to RCV_ACCOUNTING_EVENT_TYPES, linking project event types to receiving accounting event types.

Common Use Cases and Queries

Typical usage centers on validating and reporting billable event classifications, checking which event types are currently active, and tracing downstream transactions back to their classification.

• List all currently active event types: SELECT EVENT_TYPE, DESCRIPTION, EVENT_TYPE_CLASSIFICATION, REVENUE_CATEGORY_CODE FROM PA.PA_EVENT_TYPES WHERE TRUNC(SYSDATE) BETWEEN START_DATE_ACTIVE AND NVL(END_DATE_ACTIVE, SYSDATE);
• Identify billing-related event types by joining to PA_BILLING_EXTENSIONS on DEFAULT_EVENT_TYPE.
• Reconcile event volumes by classification: join PA_EVENTS.EVENT_TYPE to PA_EVENT_TYPES.EVENT_TYPE and group by classification.
• Determine which event types drive retention: join PA_PROJ_RETN_RULES.EVENT_TYPE to PA_EVENT_TYPES.EVENT_TYPE.
• Audit date-effectiveness and detect event types referenced by transactions but no longer active.

Related Objects

PA_EVENT_TYPES is referenced by numerous PA tables through the EVENT_TYPE column, confirming its hub role:

• PA_EVENTS — joins on EVENT_TYPE; stores the actual project events.
• PA_BILLING_EXTENSIONS — joins on DEFAULT_EVENT_TYPE; supplies default billing event types.
• PA_EVENT_TYPE_OUS_ALL — joins on EVENT_TYPE; maps event types to operating units.
• PA_PROJECT_EVENT_ACCUM — joins on EVENT_TYPE; holds accumulated event amounts.
• PA_PROJ_RETN_RULES — joins on EVENT_TYPE; defines retention rules per event type.
• PA_RESOURCE_ASSIGNMENTS, PA_RESOURCE_LIST_MEMBERS, PA_RESOURCE_MAPS, PA_RESOURCE_TXN_ATTRIBUTES — all join on EVENT_TYPE, tying resources and resource transactions to event classifications.
• OKE_K_BILLING_EVENTS — joins on BILL_EVENT_TYPE; links Oracle Purchasing/OKE billing events to project event types.
• PJI_FP_TXN_ACCUM_HEADER — joins on EVENT_TYPE for financial plan accumulation.
• RCV_ACCOUNTING_EVENT_TYPES — parent reference for EVENT_TYPE_ID.