Results for “date_billed_from”

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

Overview

OKI_BILL_HIST_V is a reporting view owned by the APPS schema in Oracle E-Business Suite, delivered as part of the OKI – Contracts Intelligence product family. It exposes the billing history for service contracts, presenting each billed contract line alongside its associated receivable transaction details. The view is defined in the ETRM repository as a VIEW object with VALID status and is available in both Oracle EBS 12.1.1 and 12.2.2 environments. Because Contracts Intelligence is a reporting and analytics module, this view serves as a denormalized read layer that joins service contract line information to billing and transaction records, sparing report developers and integrators from reconstructing the three-way relationship themselves. Systems and reports that reference this object can retrieve invoice-level and line-level billing detail in a single query, which supports both operational reporting and downstream data extraction. The view is read-only in practice: no DML should be issued against it, and consumers should rely on the underlying Contracts and Service modules to maintain the source data. A user searching for "bill_action" will find that this column is one of the fourteen exposed by the view and represents the billing action performed against the contract line, making OKI_BILL_HIST_V a natural starting point for any query that filters or groups contract billing history by action type.

Underlying Base Objects

The view text documents three base tables joined together. OKI_SOLD_ITM_LINES (aliased SIL) supplies the contract dimension, including the contract header identifier, contract line identifier, contract number and modifier, and line number. OKS_BILL_CONT_LINES (aliased BCL) supplies the billing line detail, including the billed amount, billing period boundaries, and the bill action. OKS_BILL_TRANSACTIONS (aliased BTN) supplies the invoice-level transaction attributes, including transaction date, transaction number, transaction amount, currency, and transaction class. The join conditions are explicit: BTN.ID equals BCL.BTN_ID links each billing line to its parent transaction, and BCL.CLE_ID equals SIL.CLE_ID links each billing line back to the sold item line, which carries the contract and line identifiers. This chain means every row represents one billed contract line tied to one invoice transaction. Note that the documented ETRM metadata lists no referenced base objects separately, so the relationship must be read from the view text itself; the three tables above are the authoritative sources.

Key Columns

• CONTRACT_ID – Contract header identifier from OKI_SOLD_ITM_LINES (CHR_ID).
• CONTRACT_LINE_ID – Contract line identifier (CLE_ID), the principal link to sold item lines.
• CONTRACT_NUMBER / CONTRACT_NUMBER_MODIFIER – Human-readable contract identifier and its version modifier.
• LINE_NUMBER – Line number within the contract.
• INVOICE_DATE / INVOICE_NUMBER – Transaction date and number from OKS_BILL_TRANSACTIONS.
• INVOICE_AMOUNT / CURRENCY_CODE / INVOICE_CLASS – Invoice total, currency, and transaction class.
• LINE_AMOUNT – Amount billed for the specific contract line.
• DATE_BILLED_FROM / DATE_BILLED_TO – The billing period covered by the line.
• BILL_ACTION – The billing action applied to the line, the column of primary interest to users searching on this term.

Common Use Cases and Queries

Typical uses include reconciling service contract billings to receivables transactions, auditing billing periods for a contract, and reporting revenue by contract line. A simple filtered query illustrates the pattern, including a BILL_ACTION predicate:

SELECT CONTRACT_NUMBER, LINE_NUMBER, INVOICE_NUMBER, INVOICE_DATE, LINE_AMOUNT, BILL_ACTION FROM APPS.OKI_BILL_HIST_V WHERE CONTRACT_NUMBER = :contract_number AND BILL_ACTION = :bill_action ORDER BY INVOICE_DATE, LINE_NUMBER;

Aggregate reporting by action type is equally straightforward:

SELECT BILL_ACTION, CURRENCY_CODE, COUNT(*) line_count, SUM(LINE_AMOUNT) total_billed FROM APPS.OKI_BILL_HIST_V GROUP BY BILL_ACTION, CURRENCY_CODE;

Because the view performs no filtering, all billed activity for the joined contracts is returned, and calling applications should bound results by contract, date range, or action as appropriate.