Results for “pabv_events”

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

Overview

PABV_EVENTS is an APPS-owned, VALID database view registered against the PA – Projects product in Oracle E-Business Suite 12.1.1 and 12.2.2. Its name follows the convention for Oracle Project Billing/Project Accounting "BV" (business view) objects, and the ETRM metadata records it with the terse description "- Retrofitted," indicating that the object was carried forward and re-registered against the current ETRM release rather than newly authored. The view presents project event data — billable and revenue-bearing events recorded against a project and, optionally, a task — in a single flattened row combined with selected project and task attributes.

Functionally, PABV_EVENTS serves as a reporting and integration surface over PA_EVENTS. It exposes identifying columns, descriptive text, revenue and billing amounts, and a set of audit columns that capture budget type context. The view is declared WITH READ ONLY, meaning consumers cannot perform DML through it; it is intended strictly for query, extract, and integration purposes. Because it joins to PA_PROJECTS_ALL, it also carries the operating unit (ORG_ID) and is subject to the '_SEC:PPA.ORG_ID' security predicate, which restricts returned rows to projects visible within the current operating unit context.

Underlying Base Objects

The view is defined over three documented base objects, all referenced through synonyms in the APPS schema: PA_EVENTS, PA_PROJECTS_ALL, and PA_TASKS. The driving table is PA_EVENTS (aliased PE), representing the project event transaction. PA_PROJECTS_ALL (aliased PPA) is joined on PE.PROJECT_ID = PPA.PROJECT_ID using an inner join, so an event is returned only when a matching project row exists. PA_TASKS (aliased PT) is joined on PE.TASK_ID = PT.TASK_ID(+) using an outer join, meaning events without an associated task are still returned, with TASK_ID null.

The security predicate "'_SEC:PPA.ORG_ID' IS NOT NULL" applies row-level operating unit filtering based on the organization of the project row. The WITH READ ONLY clause further enforces the view's read-only nature. Together these characteristics make PABV_EVENTS a secured, non-updatable projection rather than a maintenance view.

Key Columns

• EVENT_ID and EVENT_NUM — surrogate and user-visible identifiers for the project event.
• TASK_ID and PROJECT_ID — foreign keys to the task and project; TASK_ID may be null due to the outer join.
• DESCRIPTION — free-text description of the event.
• REVENUE_AMOUNT and BILL_AMOUNT — the revenue and billing monetary values associated with the event.
• COMPLETION_DATE — the date the event was completed.
• EVENT_TYPE — the classification of the event.
• AUDIT_REV_BUDGET_TYPE_CODE — the revenue budget type code captured for audit purposes; this is the column that surfaced in the user's search and identifies which revenue budget type was in effect for the event.
• AUDIT_COST_BUDGET_TYPE_CODE — the corresponding cost budget type code retained for audit.
• AUDIT_AMOUNT1 through AUDIT_AMOUNT10 — generic audit amount slots.
• ORGANIZATION_ID — operating unit context derived from the project.
• DESCRIPTIVE FLEX columns — the view returns placeholder tokens for descriptive flexfield and value-set lookups, including "_DF:PA:PA_EVENTS_DESC_FLEX:PE" for the events descriptive flexfield and lookup tokens such as BILL_HOLD_FLAG and REVENUE_DISTRIBUTED_FLAG mapped to FND_LOOKUPS YES_NO meanings.
• Audit trail columns — LAST_UPDATE_DATE, LAST_UPDATED_BY, CREATION_DATE, and CREATED_BY.

Common Use Cases and Queries

PABV_EVENTS is typically used to report project event activity, to reconcile revenue and billing amounts, and to extract audit information about the budget types applied. A representative query filtering on the audit revenue budget type code is:

SELECT event_id, event_num, project_id, task_id, revenue_amount, bill_amount, audit_rev_budget_type_code FROM apps.pabv_events WHERE audit_rev_budget_type_code = :budget_type_code;

Because the view is secured by ORG_ID, this query returns only events belonging to projects in the caller's operating unit. Analysts also use the view to list events without tasks (WHERE task_id IS NULL) or to trace descriptive flexfield content on the underlying event. All access should be treated as read-only.