Search Results line_reference




Overview
Explore in AI Chat

Overview

OKS_BILLPRST_SRVSUBLINE_V is a reporting view owned by the APPS schema in Oracle E-Business Suite, defined within the Service Contracts (OKS) product family. Its name reflects its purpose: it presents billing presentation detail at the service sub-line level, exposing the relationship between contract service lines, their billing sub-lines, and the billing transaction instances generated against them. The view is a union of two structurally identical queries, one scoped to line style identifier 11 and the other to line style identifier 10, which distinguishes the supported service line categories processed during billing.

Because it resolves contract commercial attributes, billing period information, and customer context into a single flat structure, the view serves as a convenient source for operational reporting, reconciliation of billed versus negotiated amounts, and integration extracts that require service sub-line billing granularity and monetary totals such as the extended price for each billed service line.

Underlying Base Objects

The view is defined over a combination of contract core objects and billing transaction objects. The documented referenced base objects include OKC_K_HEADERS_B, OKC_K_ITEMS, OKC_K_LINES_V, OKC_LINE_STYLES_V, OKS_BILL_SUB_LINES, OKS_BILL_TXN_LINES, OKS_K_LINES_V, OKX_SYSTEMS_V, OKX_CUST_SITE_USES_V, OKX_CUSTOMER_ACCOUNTS_V, OKX_PARTIES_V, OKX_SYSTEM_ITEMS_V, CS_CUSTOMER_PRODUCTS, and the packages ARP_ADDR_LABEL_PKG and CSICUMPI_PUB.

The join logic links each billing transaction line in OKS_BILL_TXN_LINES to its billing sub-line in OKS_BILL_SUB_LINES, and both to the contract line exposed through OKC_K_LINES_V. The contract header in OKC_K_HEADERS_B supplies the contract number and currency, while OKC_LINE_STYLES_V supplies the style name and OKS_K_LINES_V supplies invoice text. Customer and installed-base context is resolved via the OKX views and CS_CUSTOMER_PRODUCTS.

Key Columns

  • NAME: The line style name, sourced from OKC_LINE_STYLES_V.
  • DESCRIPTION: Descriptive text for the system or service, from OKX_SYSTEMS_V or OKX_CUST_SITE_USES_V depending on the union branch.
  • LINE_REFERENCE: The contract line cognomen identifying the service line.
  • START_DATE / END_DATE: The effective coverage window of the contract line.
  • EXTENDED_PRICE: The negotiated price of the line, mapped directly from OKC_K_LINES_V.PRICE_NEGOTIATED. This is the column most frequently searched for when reconciling contract line pricing.
  • INVOICE_TEXT: Invoice narrative carried on the line.
  • DATE_BILLED_FROM / DATE_BILLED_TO: The billing period boundaries from OKS_BILL_SUB_LINES.
  • AMOUNT_BILLED: The amount billed for the sub-line period.
  • CURRENCY_CODE: Currency of the contract header.
  • CONTRACT_NUMBER / BILL_INSTANCE_NUMBER: Identifiers for the contract and the billing transaction instance.
  • ID, CLE_ID, BCL_ID, BSL_ID, DNZ_CHR_ID: Technical keys linking to contract lines, billing sub-lines, and header records.

Common Use Cases and Queries

Typical usage includes billing reconciliation, where AMOUNT_BILLED is compared against EXTENDED_PRICE for a given period, and integration extracts that feed downstream revenue or invoicing systems. The following query illustrates retrieving billed service sub-lines with their negotiated extended price for a specific contract:

  • SELECT contract_number, line_reference, extended_price, amount_billed, date_billed_from, date_billed_to FROM oks_billprst_srvsubline_v WHERE contract_number LIKE :contract_prefix ORDER BY date_billed_from;
  • SELECT currency_code, SUM(extended_price) negotiated_total, SUM(amount_billed) billed_total FROM oks_billprst_srvsubline_v GROUP BY currency_code;
  • SELECT bill_instance_number, line_reference, amount_billed FROM oks_billprst_srvsubline_v WHERE date_billed_from >= :from_date AND date_billed_to <= :to_date;

Because the view is read-only and assembled from numerous joins, queries should be filtered by contract number, line reference, or billing date range to minimize execution cost on large billing volumes.