Search Results oks_billing_hist_lines_v




Overview
Explore in AI Chat

Overview

OKS_BILLING_HIST_LINES_V is an APPS-owned database view in the Oracle E-Business Suite Service Contracts (OKS) module. It exposes the billing history detail for service contract lines, joining contract line definitions, line styles, billing sub-lines, and billing sub-line details into a single flattened result set. The view carries a VALID status and is available in both 12.1.1 and 12.2.2 releases. Its primary role is to support reporting and integration scenarios that require visibility into how a service contract line was billed over a given billing period — specifically the from/to billing dates, the billed amount, and the processing result returned by the billing engine.

For users and developers searching on bill_to, the view is directly relevant because one of its exposed columns is literally named BILL_TO. This column represents the end date of the billing interval for a given billing sub-line, complementing BILL_FROM (the interval start date). Together these columns describe the billing period covered by each historical billing record.

Underlying Base Objects

The view is defined over four referenced objects, two of which are views and two of which are synonyms resolving to Service Contracts billing tables:

  • OKC_K_LINES_V (VIEW) – aliased as KLE in the view text. Supplies the contract line context, including the line NAME shown in the output. It is joined on KLE.ID = BSL.CLE_ID, linking each billing sub-line back to its originating contract line.
  • OKC_LINE_STYLES_V (VIEW) – aliased as LST. Supplies the BILL_LEVEL description, joined via KLE.LSE_ID = LST.ID, which maps the line to its line style and hence its billing level.
  • OKS_BILL_SUB_LINES (SYNONYM) – aliased as BSL. The core billing sub-line table, providing the billing period dates, the billed amount, and the ROWID/ID/BCL_ID identifiers.
  • OKS_BILL_SUB_LINE_DTLS (SYNONYM) – aliased as BSD. Provides the processing RESULT for each billing sub-line, joined on BSL.ID = BSD.BSL_ID.

The join path is therefore: contract line → line style → billing sub-line → billing sub-line detail, producing one row per billing sub-line/detail combination.

Key Columns

  • ROW_ID – the ROWID of the underlying OKS_BILL_SUB_LINES row; useful for direct row addressing.
  • ID – the billing sub-line identifier (BSL.ID).
  • BCL_ID – the parent billing contract line identifier, linking the sub-line to its billing line header.
  • BILL_LEVEL – the name of the line style, indicating the billing level at which the line is billed.
  • NAME – the contract line name from OKC_K_LINES_V.
  • BILL_FROM – start date of the billed period (BSL.DATE_BILLED_FROM).
  • BILL_TO – end date of the billed period (BSL.DATE_BILLED_TO). This is the column most commonly targeted by bill_to searches.
  • AMOUNT – the billed amount for the sub-line.
  • RESULT – the billing processing result from the detail table, indicating outcome status.

Common Use Cases and Queries

Typical uses include billing history reporting for a contract line, reconciliation of billed amounts against billing periods, and integration extracts feeding downstream revenue or invoicing systems. The following sample retrieves billing history for a given contract line identifier, filtering on the bill-to date range:

  • SELECT id, bcl_id, bill_level, name, bill_from, bill_to, amount, result FROM apps.oks_billing_hist_lines_v WHERE bill_to >= :p_start_date AND bill_from <= :p_end_date ORDER BY name, bill_from;
  • SELECT name, SUM(amount) total_billed FROM apps.oks_billing_hist_lines_v WHERE bill_to BETWEEN :p_from AND :p_to GROUP BY name;
  • SELECT id, bill_from, bill_to, result FROM apps.oks_billing_hist_lines_v WHERE result IS NOT NULL AND name = :p_line_name;

Because the view joins multiple OKC and OKS objects, query performance benefits from filtering on indexed identifiers such as ID or BCL_ID, and from constraining the BILL_TO range where period-specific reporting is required.