Results for “pa_event_id”

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

Overview

OKE_K_BILLING_EVENTS_V is an APPS-owned database view in the Oracle E-Business Suite (EBS) 12.1.1 and 12.2.2 releases, delivered as part of the OKE – Project Contracts (Oracle Knowledge/Contracts) module. The view presents deliverable-based billing events, exposing the transactional detail required to translate contract deliverables into billable events that flow into Oracle Projects and Oracle Receivables. Because it consolidates billing event metadata—project, task, organization, currency, quantity, price, and revenue amount—into a single queryable interface, it serves as a reporting and integration layer rather than a transactional entry point. The status is VALID, and the view is defined in the APPS schema, ensuring that it can be queried with standard EBS security and MOAC (Multi-Org Access Control) profiles.

Underlying Base Objects

The documented metadata indicates that OKE_K_BILLING_EVENTS_V is defined over a single referenced base object, OKE_K_BILLING_EVENTS (accessed via a SYNONYM). The view text confirms this: it is a simple projection selecting all named columns from the table aliased as B, plus B.ROWID, and the FROM clause references only OKE_K_BILLING_EVENTS. No joins, unions, or aggregations are applied. Consequently, the view exposes the same row population as the base table, with the additional ROWID column retained for row identification. There is no evidence of a WHERE predicate filtering rows, so the view is a straight pass-through of the underlying deliverable-based billing event records.

Key Columns

• BILLING_EVENT_ID – Primary identifier for the billing event record.
• PA_EVENT_ID – Reference to the associated Oracle Projects event.
• K_HEADER_ID / K_LINE_ID – Linkage to the OKE contract header and line.
• DELIVERABLE_ID – The contract deliverable that triggered the billing event.
• BILL_EVENT_TYPE / BILL_EVENT_DATE – Event classification and its effective date.
• BILL_ITEM_ID / BILL_LINE_ID / BILL_CHG_REQ_ID – Receivables-side item, line, and change request references.
• BILL_PROJECT_ID – The project against which the event is billed; this is the column typically targeted by users searching for "bill_project_id" (note the physical column is named BILL_PROJECT_ID, not BILL_PROJECT_ID with a leading B).
• BILL_TASK_ID / BILL_ORGANIZATION_ID – Task and organization assignment for the billing event.
• BILL_FUND_REF1-3, BILL_BILL_OF_LADING, BILL_SERIAL_NUM – Descriptive funding and shipping references.
• BILL_CURRENCY_CODE, BILL_RATE_TYPE, BILL_RATE_DATE, BILL_EXCHANGE_RATE – Currency and exchange rate attributes.
• BILL_QUANTITY, BILL_UNIT_PRICE, REVENUE_AMOUNT – Billing amounts and derived revenue.
• ATTRIBUTE1-15, ATTRIBUTE_CATEGORY – Descriptive flexfield segments.
• CREATED_BY, CREATION_DATE, LAST_UPDATED_BY, LAST_UPDATE_LOGIN, LAST_UPDATE_DATE – Standard WHO audit columns.
• INITIATED_FLAG – Indicates whether the event has been initiated.

Common Use Cases and Queries

Typical scenarios include reporting deliverable billing events by project, reconciling OKE events to Oracle Projects (PA) events, and extracting billing detail for downstream interfaces. A representative query filtering on the project is:

• SELECT billing_event_id, pa_event_id, k_header_id, k_line_id, deliverable_id, bill_event_type, bill_event_date, bill_project_id, bill_task_id, bill_currency_code, bill_quantity, bill_unit_price, revenue_amount FROM apps.oke_k_billing_events_v WHERE bill_project_id = :p_project_id ORDER BY bill_event_date;
• Filtering non-initiated events: SELECT billing_event_id, bill_project_id, initiated_flag FROM apps.oke_k_billing_events_v WHERE initiated_flag = 'N';
• Aggregating revenue by project: SELECT bill_project_id, SUM(revenue_amount) FROM apps.oke_k_billing_events_v GROUP BY bill_project_id;

Because the view is a direct projection of OKE_K_BILLING_EVENTS, performance mirrors that of the base table; index usage on BILLING_EVENT_ID, BILL_PROJECT_ID, and DELIVERABLE_ID is advised for large-volume extraction. The view is read-only and should not be used for DML.