Search Results rev_dist_rejection_code




Overview
Explore in AI Chat

Overview

PA_EVENTS_AMG_V is an Oracle E-Business Suite view owned by the APPS schema and classified under the PA (Projects) product family. It is documented as VALID in ETRM for releases 12.1.1 and 12.2.2. The view is defined over the PA_EVENTS table and presents events assigned to a project task that generate revenue and/or billing activity which is not directly associated with the cost and revenue produced by expenditure items. In practice, this means it exposes "standalone" or "manual" events — such as milestone billings, progress payments, or ad hoc revenue accruals — that are decoupled from the standard expenditure-driven revenue and billing generation flows.

Its role in Oracle EBS reporting and integration is to provide a denormalized, read-friendly projection of the PA_EVENTS entity for inquiry, reconciliation, and downstream integration. Because event-based billing and revenue generation in Oracle Projects depends on discrete attributes such as hold flags, distribution flags, completion dates, and conversion amounts in multiple currencies, this view is commonly used as the source for custom reports, extracts, and interfaces that need visibility into event-level revenue and billing status without joining the full set of PA_EVENTS columns directly.

Underlying Base Objects

The documented referenced base object is PA_EVENTS (exposed to APPS as a synonym). The view text is a direct column projection from that table, including the primary and foreign key columns TASK_ID, EVENT_ID, PROJECT_ID, ORGANIZATION_ID, BILLING_ASSIGNMENT_ID, and the event sequence identifier EVENT_NUM, alongside audit columns such as LAST_UPDATE_DATE, LAST_UPDATED_BY, CREATION_DATE, CREATED_BY, and LAST_UPDATE_LOGIN.

Because PA_EVENTS sits at the intersection of task setup, billing assignments, and revenue distribution processing, PA_EVENTS_AMG_V inherits that positioning. Any row returned by the view corresponds to a single event record in PA_EVENTS and therefore participates in the same attribution, distribution, and accounting rules applied by Oracle Projects. No additional joins, filters, or aggregations are documented in the view text, which makes it a transparent pass-through over the base table's event data.

Key Columns

  • EVENT_ID / EVENT_NUM — Surrogate key and user-facing event number identifying the event.
  • TASK_ID / PROJECT_ID / ORGANIZATION_ID — The task, project, and organization to which the event is attributed.
  • EVENT_TYPE — Classifies the event (for example, milestone or other revenue/billing event type).
  • BILL_AMOUNT / REVENUE_AMOUNT — Transactional billing and revenue amounts held on the event in the project ledger context.
  • REVENUE_DISTRIBUTED_FLAG — Indicates whether the event's revenue has been distributed to the revenue subsystem. This is the column referenced by the user search and is central to identifying undistributed events.
  • BILL_HOLD_FLAG — Controls whether billing for the event is held (excluded from the next bill run).
  • BILLED_FLAG — Indicates whether the event has already been billed.
  • COMPLETION_DATE — Date on which the event is considered complete, relevant for milestone-based billing.
  • REV_DIST_REJECTION_CODE — Populated when revenue distribution fails, identifying the rejection reason.
  • BILLING_ASSIGNMENT_ID — Links the event to its billing assignment configuration.
  • Currency columns — PROJECT_*, PROJFUNC_*, BILL_TRANS_*, and FUNDING_* amount, currency code, rate type, rate date, and exchange rate columns provide converted values and rates across project, project functional, transaction, and funding currency contexts.
  • Descriptive and descriptive flexfield columns — DESCRIPTION, ATTRIBUTE_CATEGORY, ATTRIBUTE1 through ATTRIBUTE10, and REFERENCE1 through REFERENCE10.

Common Use Cases and Queries

The most frequent use case is identifying events whose revenue has not yet been distributed, which is exactly where REVENUE_DISTRIBUTED_FLAG is relevant. The following query lists undistributed events within a project:

  • SELECT event_id, event_num, task_id, project_id, event_type, revenue_amount, revenue_distributed_flag FROM apps.pa_events_amg_v WHERE project_id = :project_id AND NVL(revenue_distributed_flag,'N') = 'N';

Other practical scenarios include reconciliation of billed versus unbilled events, review of held billing events, and analysis of revenue distribution rejections. For example:

  • SELECT event_num, task_id, bill_amount, revenue_amount, billed_flag, bill_hold_flag FROM apps.pa_events_amg_v WHERE project_id = :project_id AND bill_hold_flag = 'Y';
  • SELECT event_num, rev_dist_rejection_code FROM apps.pa_events_amg_v WHERE rev_dist_rejection_code IS NOT NULL;
  • SELECT event_num, projfunc_revenue_amount, projfunc_currency_code FROM apps.pa_events_amg_v WHERE project_id = :project_id ORDER BY event_num;

These queries support revenue accounting review, billing cycle preparation, and custom reporting where event-level detail is required without the overhead of joining directly to the underlying PA_EVENTS table.