Search Results event_num_reversed




Overview
Explore in AI Chat

Overview

APPS.PAFV_EVENTS is a read-only reporting view in Oracle E-Business Suite (EBS) Release 12.1.1 and 12.2.2 that consolidates project revenue and billing event information from the Oracle Projects (PA) module. It presents a denormalized, security-enabled picture of project events, joining event detail to project, task, organization, event type, and budget type information in a single queryable object. Because the view is defined WITH READ ONLY, it cannot be used for DML and is intended strictly for reporting, extraction, and integration purposes.

The view is particularly relevant to users investigating the EVENT_NUM_REVERSED column, which exposes the event number associated with an event reversal. When an event is reversed or credited through Oracle Projects revenue and billing processing, the reversal event references the original event number in this column, allowing users to trace reversal relationships and reconcile revenue activity. The view also embeds descriptive flexfield and lookup references (for example, _DF:PA:PA_EVENTS_DESC_FLEX:PE and lookups for BILL_HOLD_FLAG and REVENUE_DISTRIBUTED_FLAG), which indicate it is designed for use with Oracle's standard reporting and integration frameworks.

Underlying Base Objects

The view is defined over the following documented base objects, all accessed through APPS synonyms:

  • PA_EVENTS (PE) — the driving table, supplying event identifiers, amounts, dates, and the reversal reference.
  • PA_TASKS (PT) — joined via an outer join (pe.task_id = pt.task_id(+)) to provide task context.
  • PA_PROJECTS_ALL (PPA) — joined on project_id to supply project name, number, and org_id; the org_id also drives the view's security predicate.
  • PA_EVENT_TYPES (PET) — joined on event_type to translate event type codes into descriptions.
  • HR_ALL_ORGANIZATION_UNITS (HOU) — joined on organization_id to supply the organization name.
  • PA_BUDGET_TYPES (BUT1, BUT2) — outer-joined twice to resolve the audit cost and audit revenue budget type codes into descriptions.

Each base object is referenced as a synonym under the APPS schema, consistent with standard EBS view architecture.

Key Columns

Common Use Cases and Queries

Typical uses include reconciling reversed revenue events, reporting billed versus unbilled events by project, and feeding downstream interfaces. To find all reversals and their originals:

  • SELECT event_id, event_num, event_num_reversed, revenue_amount, bill_amount, project_id FROM apps.pafv_events WHERE event_num_reversed IS NOT NULL;
  • SELECT event_id, event_num, revenue_amount FROM apps.pafv_events WHERE project_id = :project_id AND revenue_amount > 0;
  • SELECT project_id, event_type, SUM(bill_amount) FROM apps.pafv_events GROUP BY project_id, event_type;

Because the view enforces org-level security via the _SEC:ppa.org_id predicate, results are automatically restricted to the operating units accessible to the querying user. Analysts tracing reversal activity should always include EVENT_NUM_REVERSED to associate credit events with their originating event numbers.