Search Results bill_from




Overview
Explore in AI Chat

Overview

APPS.OKS_BILLING_HIST_LINES_V is a reporting view in Oracle E-Business Suite (12.1.1 and 12.2.2) that exposes billing history detail at the contract line level. It is part of the Service Contracts (OKS) and Contracts Core (OKC) schema family, joining contract line definitions to their subordinate billing sub-lines and the calculated billing results. The view presents the billed-from and billed-to dates, the billing amount, the billing level, and the computed result for each billing sub-line, giving users a flattened, query-friendly picture of how a contract line has been billed over time. Because it consolidates contract, line-style, sub-line, and sub-line-detail information into a single SELECT, it is commonly used in service contract billing audits, revenue and deferred-revenue analysis, invoice reconciliation, and custom reporting or integration extracts. The alias BILL_FROM in the view definition corresponds to the underlying DATE_BILLED_FROM column, which is the value users typically search for when reconciling billing periods.

Underlying Base Objects

The view is defined over four documented objects. Two are other APPS views: OKC_K_LINES_V (aliased KLE), which supplies contract line information including the line name and the line style identifier, and OKC_LINE_STYLES_V (aliased LST), which supplies the line style name used as the billing level. Two are SYNONYM references to OKS base tables: OKS_BILL_SUB_LINES (aliased BSL), which holds the billing sub-lines including the billed-from, billed-to, amount, and the foreign keys to the contract line and sub-line detail, and OKS_BILL_SUB_LINE_DTLS (aliased BSD), which holds the calculated billing result.

Joins are constructed as follows: KLE.LSE_ID = LST.ID links each contract line to its line style; KLE.ID = BSL.CLE_ID links contract lines to their billing sub-lines; and BSL.ID = BSD.BSL_ID links each sub-line to its detail result. The view is therefore a strict inner-join chain, so only contract lines that have billing sub-lines with associated details appear in the result set.

Key Columns

  • ROW_ID — the ROWID of the OKS_BILL_SUB_LINES row, useful as a unique identifier for updates or de-duplication.
  • ID — the billing sub-line identifier (BSL.ID).
  • BCL_ID — the parent billing contract line identifier.
  • BILL_LEVEL — the line style name (LST.NAME), indicating the level at which billing occurs.
  • NAME — the contract line name (KLE.NAME).
  • BILL_FROM — the billed-from date (BSL.DATE_BILLED_FROM), the start of the billing period.
  • BILL_TO — the billed-to date (BSL.DATE_BILLED_TO), the end of the billing period.
  • AMOUNT — the billed amount for the sub-line.
  • RESULT — the billing result value from the sub-line detail record (BSD.RESULT).

The BILL_FROM and BILL_TO columns are the primary temporal anchors for period-based analysis, while AMOUNT and RESULT drive financial aggregation.

Common Use Cases and Queries

Typical scenarios include auditing all billing periods for a given contract line, summarizing billed amounts by level, and extracting billing history for a date range. The following query retrieves billing history for lines billed from a specific date:

  • SELECT name, bill_level, bill_from, bill_to, amount, result FROM apps.oks_billing_hist_lines_v WHERE bill_from >= :p_from_date ORDER BY bill_from;
  • SELECT bill_level, SUM(amount) total_billed FROM apps.oks_billing_hist_lines_v GROUP BY bill_level;
  • SELECT name, bill_from, bill_to, amount FROM apps.oks_billing_hist_lines_v WHERE id = :p_bsl_id;

Because the view performs inner joins across contract line, line style, sub-line, and detail objects, queries should filter on BILL_FROM or BILL_TO to constrain volume. No filtering is applied by the view itself, so row-level security and operating unit context must be applied by the calling report or integration.