Results for “billing_event_id”

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

Overview

OKE_K_BILLING_EVENTS is a transactional table in the OKE (Project Contracts) module of Oracle E-Business Suite, available in releases 12.1.1 and 12.2.2. It stores deliverable-based billing events that arise from contract terms negotiated and authored within Oracle Project Contracts. Where a contract deliverable is associated with a billable milestone, quantity, or rate, this table records the resulting billing event together with its financial attributes, the project and task to be billed, and the currency and exchange-rate conventions that govern the transaction. Its records therefore act as the bridge between contract authoring in OKE and downstream billing and revenue recognition activity in Oracle Projects and Oracle Receivables.

From a Data Vault modeling perspective, the FK structure of this table is heuristic-classified as a link. This is a reasonable classification: the table resolves relationships between contracts (OKE_K_HEADERS, OKE_K_LINES), deliverables (OKE_K_DELIVERABLES_B), projects and tasks (PA_PROJECTS_ALL, PA_TASKS), and change requests (OKE_CHG_REQUESTS). Because it also carries descriptive and financial attributes such as quantity, unit price, and revenue amount, the table functions in practice as a link with satellite-like attributes attached.

Key Information Stored

The table is owned by the OKE schema and contains 48 documented columns. The surrogate primary key is BILLING_EVENT_ID, enforced by OKE_K_BILLING_EVENTS_PK and also uniquely constrained by the index OKE_K_BILLING_EVENTS_U1. The most significant columns include:

• BILLING_EVENT_ID — system-generated primary key for the billing event.
• K_HEADER_ID and K_LINE_ID — identify the parent contract and contract line that originate the event.
• DELIVERABLE_ID — the specific deliverable that triggers billing, linking to OKE_K_DELIVERABLES_B.
• BILL_EVENT_DATE and BILL_EVENT_TYPE — when the event occurred and its project-billing event type (PA_EVENT_TYPES).
• BILL_PROJECT_ID and BILL_TASK_ID — the project and task to which the billing event is charged.
• BILL_LINE_ID and BILL_CHG_REQ_ID — the contract line and change request associated with the billable amount.
• BILL_ORGANIZATION_ID — the organization unit (HR_ALL_ORGANIZATION_UNITS) responsible for or receiving the event.
• BILL_CURRENCY_CODE, BILL_RATE_TYPE, BILL_RATE_DATE, BILL_EXCHANGE_RATE — currency and conversion attributes governing the transaction.
• BILL_QUANTITY, BILL_UNIT_PRICE, REVENUE_AMOUNT — the quantity, price, and computed revenue for the event.
• BILL_DESCRIPTION — free-text description of the billing event.
• INITIATED_FLAG — indicates whether the event has been initiated or processed.
• ATTRIBUTE_CATEGORY through ATTRIBUTE15 — the standard EBS descriptive flexfield columns.
• WHO columns (CREATION_DATE, CREATED_BY, LAST_UPDATE_DATE, LAST_UPDATED_BY, LAST_UPDATE_LOGIN) — standard audit trail.

Common Use Cases and Queries

Reporting on OKE_K_BILLING_EVENTS is typically performed to reconcile contract deliverables against billable amounts, to trace revenue back to a specific contract line or change request, and to review currency exposure on foreign-currency billing events. A typical join pattern connects the event to its contract header and deliverable:

SELECT be.billing_event_id, be.bill_event_date, be.bill_quantity, be.bill_unit_price, be.revenue_amount, be.bill_currency_code, kh.contract_number
FROM oke_k_billing_events be, oke_k_headers kh
WHERE be.k_header_id = kh.k_header_id
AND be.bill_project_id = :project_id;

Because BILL_PROJECT_ID and BILL_TASK_ID point into Oracle Projects, the table is also frequently joined to PA_PROJECTS_ALL and PA_TASKS to summarize billing events by project or task, and to PA_EVENT_TYPES to classify events by type. Analysts commonly aggregate BILL_QUANTITY and REVENUE_AMOUNT by BILL_EVENT_TYPE, BILL_CURRENCY_CODE, or BILL_ORGANIZATION_ID to support revenue forecasting and currency reporting. The INITIATED_FLAG is used to separate pending events from those already passed to downstream billing processes.

Related Objects

The table participates in a dense foreign-key network within the OKE and Projects schemas:

• OKE_K_HEADERS — joined on K_HEADER_ID; the parent contract header.
• OKE_K_LINES — joined on K_LINE_ID and BILL_LINE_ID; contract lines that carry the billing event.
• OKE_K_DELIVERABLES_B — joined on DELIVERABLE_ID; the deliverable that triggers billing. This table also holds a foreign key back to OKE_K_BILLING_EVENTS.BILLING_EVENT_ID, as does its history counterpart OKE_K_DELIVERABLES_BH.
• PA_PROJECTS_ALL and PA_TASKS — joined on BILL_PROJECT_ID and BILL_TASK_ID for project billing context.
• PA_EVENT_TYPES — joined on BILL_EVENT_TYPE to classify the event.
• OKE_CHG_REQUESTS — joined on BILL_CHG_REQ_ID for change-order driven billing.
• HR_ALL_ORGANIZATION_UNITS — joined on BILL_ORGANIZATION_ID.
• FND_CURRENCIES and GL_DAILY_CONVERSION_TYPES — joined on BILL_CURRENCY_CODE and BILL_RATE_TYPE for currency and rate validation.

The bidirectional relationship with OKE_K_DELIVERABLES_B makes OKE_K_BILLING_EVENTS a central reference point for deliverable billing, and interface logic should account for that dependency when purging or archiving contract data.