Search Results event_revenue_amount

Overview

APPS.GMS_EVENTS_V is an Oracle E-Business Suite view owned by the APPS schema and registered under the FND Design Data reference GMS.GMS_EVENTS_V. It is a supplementary view whose primary purpose is to simplify forms coding within the Grants Management (GMS) application family. The view presents event-related data used in the billing and revenue recognition lifecycle for awards and projects, combining governed event attributes with organization-level event information. The object carries a status of VALID across the documented EBS 12.1.1 and 12.2.2 environments.

Because it is a forms-support view rather than a public API, Oracle explicitly warns that it should not be queried or altered directly for transactional purposes, as its definition may change significantly in subsequent minor or major releases. It is therefore best treated as a read-only reporting and diagnostic surface, not as an integration contract. The event_revenue_amount term that leads users to this object corresponds to the EVENT_REVENUE_AMOUNT column exposed by the view.

Underlying Base Objects

The documented base objects underlying GMS_EVENTS_V are:

• PA_EVENTS (referenced via SYNONYM) — the core Projects event table holding billing and revenue events associated with tasks and projects.
• GMS_EVENT_ATTRIBUTE (referenced via SYNONYM) — the Grants event attribute table holding supplementary descriptive and audit columns.

The view joins these sources so that forms can retrieve a single denormalized row per event, including descriptive flexfield context, audit columns, and financial amounts. Because the base objects are referenced through synonyms, the view remains decoupled from fully qualified table names, a standard pattern in APPS-owned database objects.

Key Columns

The view exposes a broad set of columns across identity, financial, workflow, and descriptive categories:

• EVENT_ID, EVENT_NUM, TASK_ID, PROJECT_ID, ORGANIZATION_ID — primary identity and project/task association keys.
• EVENT_REVENUE_AMOUNT and REVENUE_AMOUNT — the revenue values associated with the event, the column of primary interest to users searching this object.
• EVENT_BILL_AMOUNT and BILL_AMOUNT — the corresponding billing amounts.
• WRITE_OFF_AMOUNT and REVENUE_ACCUMULATED — revenue write-off and accumulation indicators.
• REVENUE_DISTRIBUTED_FLAG, BILL_HOLD_FLAG, REV_DIST_REJECTION_CODE — workflow and distribution status controls that govern whether an event can be billed or revenue-distributed.
• COMPLETION_DATE, EVENT_TYPE, DESCRIPTION — descriptive event context.
• BILLING_ASSIGNMENT_ID, INSTALLMENT_ID, EVENT_NUM_REVERSED — billing assignment and reversal linkage.
• ATTRIBUTE_CATEGORY and ATTRIBUTE1 through ATTRIBUTE10 — descriptive flexfield columns supporting client-specific extensions.
• LAST_UPDATE_DATE, CREATION_DATE, CREATED_BY, LAST_UPDATED_BY, REQUEST_ID, PROGRAM_ID — standard audit and concurrent program tracing columns.
• AUDIT_AMOUNT1 through AUDIT_AMOUNT10 — audit amount placeholders used by the Grants forms.

Common Use Cases and Queries

The view is typically used in reporting to identify events awaiting revenue distribution or billing, and to reconcile event revenue against audit amounts. A representative query retrieving unconsumed revenue events is:

SELECT event_id, event_num, task_id, project_id, event_type, event_revenue_amount, revenue_amount, revenue_distributed_flag FROM apps.gms_events_v WHERE revenue_distributed_flag = 'N';

Another common pattern isolates events blocked from billing:

SELECT event_num, project_id, event_bill_amount, revenue_distributed_flag, bill_hold_flag FROM apps.gms_events_v WHERE bill_hold_flag = 'Y';

Because Oracle does not recommend direct querying of supplementary views, production integrations should prefer documented Grants/Projects public APIs, reserving this view for ad hoc reporting and diagnostics where release-to-release stability is not a requirement.