Results for “pafv_events_obsolete”

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

Overview

PAFV_EVENTS_OBSOLETE is a Projects (PA) business view in Oracle EBS 12.1.1 and 12.2.2 that exposes information about project events — the revenue and invoice generation events associated with projects. The view is explicitly flagged as obsolete by its name and by the ETRM implementation metadata, which records "Not implemented in this database." As a result, it should be treated as a historical or legacy artifact rather than an active reporting object in a current instance.

The view was designed to support revenue and billing event reporting, presenting event-level amounts, project/organization context, and descriptive attributes such as event type description. In that role it would have served reporting and integration scenarios requiring event-to-project, event-to-organization, and event-to-event-type relationships. Because it is documented as obsolete, developers and analysts should generally reference the supported replacement views (for example, current PA events views) rather than this object.

Underlying Base Objects

The ETRM metadata lists no documented referenced base objects for the 12.2.2 documented view metadata ("Referenced base objects: none documented"). However, the embedded view text defines the underlying tables explicitly. The view joins:

• PA_EVENTS PE — the primary event table, aliased PE, supplying event ID, number, description, revenue amount, bill amount, completion date, audit amounts, event type, and audit trail columns.
• PA_TASKS PT — joined on PE.TASK_ID = PT.TASK_ID (+) as an outer join, supplying TASK_ID.
• PA_PROJECTS_ALL PPA — joined on PE.PROJECT_ID = PPA.PROJECT_ID, supplying ORG_ID, PROJECT_ID, NAME, and SEGMENT1.
• PA_EVENT_TYPES PET — joined on PE.EVENT_TYPE = PET.EVENT_TYPE, supplying the event type description (PET.DESCRIPTION aliased as EVENT_TYPE_DESCRIPTION).
• PER_ALL_ORGANIZATION_UNITS POU — joined on PE.ORGANIZATION_ID = POU.ORGANIZATION_ID, supplying the organization name.
• PA_BUDGET_TYPES BUT1 and BUT2 — outer-joined to PE.AUDIT_COST_BUDGET_TYPE_CODE and PE.AUDIT_REV_BUDGET_TYPE_CODE respectively to resolve budget type descriptions.

The view applies the security predicate '_SEC:PPA.ORG_ID' IS NOT NULL and is defined WITH READ ONLY, indicating it is intended strictly for query access and is subject to organization-level security.

Key Columns

The view exposes identifiers, monetary amounts, descriptive fields, and audit columns. Notable columns include:

• EVENT_ID, EVENT_NUM, EVENT_NUM_REVERSED — unique event identifier and the event number, including any reversal reference.
• REVENUE_AMOUNT, BILL_AMOUNT — the revenue and billing values associated with the event.
• EVENT_TYPE, EVENT_TYPE_DESCRIPTION — the event type code and its corresponding description from PA_EVENT_TYPES, resolving the user search term "event_type_description."
• COMPLETION_DATE, DESCRIPTION — event completion date and free-text description.
• AUDIT_AMOUNT1 through AUDIT_AMOUNT10 — a set of audit amount buckets associated with the event.
• AUDIT_COST_BUDGET_TYPE_CODE / AUDIT_COST_BUDGET_TYPE and AUDIT_REV_BUDGET_TYPE_CODE / AUDIT_REV_BUDGET_TYPE — cost and revenue budget type codes and descriptions.
• PROJECT_ID, PROJECT_NAME, PROJECT_NUMBER, ORG_ID, ORGANIZATION_ID, ORGANIZATION_NAME — project and organization context.
• LAST_UPDATE_DATE, LAST_UPDATED_BY, CREATION_DATE, CREATED_BY — standard audit trail columns.
• _DF and _LA descriptors — Flexfield and lookup attributes carried in the view text (for example, PA_EVENTS_DESC_FLEX, and YES_NO lookup meanings for BILL_HOLD_FLAG and REVENUE_DISTRIBUTED_FLAG).

Common Use Cases and Queries

Because the view is marked obsolete and not implemented, its practical use is limited to legacy migrations, historical references, or review of prior EBS versions. Where it remains available, typical usage mirrors event reporting: retrieving revenue and billing amounts per project, resolving event type descriptions, and validating organization security.

A representative query follows:

• SELECT event_id, event_num, project_number, event_type, event_type_description, revenue_amount, bill_amount, completion_date FROM pafv_events_obsolete WHERE project_number = 'PRJ-100';
• SELECT event_type, event_type_description, SUM(revenue_amount), SUM(bill_amount) FROM pafv_events_obsolete GROUP BY event_type, event_type_description;
• SELECT ORG_ID, ORGANIZATION_NAME, COUNT(*) FROM pafv_events_obsolete GROUP BY ORG_ID, ORGANIZATION_NAME;

For production reporting on 12.1.1 or 12.2.2, the supported PA event views should be used instead, as PAFV_EVENTS_OBSOLETE is retained only as a deprecated reference.