Search Results okc_price_adj_assocs




Overview
Explore in AI Chat

Overview

The OKS_BILL_CONT_LINES table is a core transactional table within the Oracle E-Business Suite Service Contracts (OKS) module. Its primary function is to serve as the staging and tracking repository for contract line-level billing information before it is transmitted to Oracle Receivables (AR) for invoice generation. The table acts as a critical junction point in the order-to-cash cycle for service contracts, linking contract fulfillment activities to the financial invoicing process. Each record represents a billable line item from a service contract that has been identified for revenue recognition and customer billing.

Key Information Stored

While the provided metadata does not list specific columns, the table's foreign key relationships and description indicate it stores identifiers and attributes necessary for billing. The primary key column is ID. Crucially, the table holds foreign keys that link it to the originating contract line (CLE_ID referencing OKC_K_LINES_B) and its parent billing transaction header (BTN_ID referencing OKS_BILL_TRANSACTIONS). This structure allows the system to aggregate multiple billable contract lines under a single billing transaction. The table likely stores financial details such as the billable amount, revenue amount, accounting rule information, and status flags indicating the line's progression from creation to successful interface to AR.

Common Use Cases and Queries

This table is central to troubleshooting billing issues, auditing billed revenue, and generating custom billing reports. Common operational queries involve identifying billed lines for a specific contract or transaction and diagnosing lines that failed to interface to AR. A typical pattern is joining to contract headers and lines to analyze billed activity.

  • Sample Query for Billed Contract Lines:
    SELECT bcl.id, khr.contract_number, klb.line_number, bcl.amount
    FROM oks.oks_bill_cont_lines bcl,
    oks.oks_bill_transactions btn,
    okc.okc_k_lines_b klb,
    okc.okc_k_headers_b khr
    WHERE bcl.btn_id = btn.id
    AND bcl.cle_id = klb.id
    AND klb.dnz_chr_id = khr.id
    AND btn.status = 'PROCESSED';
  • Reporting Use Case: Reconciling total billed amounts from service contracts to the AR module by summarizing amounts from OKS_BILL_CONT_LINES for a given period and comparing them to imported AR invoice lines.

Related Objects

The metadata reveals a complex web of integrations. OKS_BILL_CONT_LINES is a hub table with dependencies from several key modules:

  • Parent: OKS_BILL_TRANSACTIONS (BTN_ID) is the header for the billing batch.
  • Source: OKC_K_LINES_B (CLE_ID) is the source service contract line.
  • Child Tables: OKS_BILL_SUB_LINES and OKS_BILL_TXN_LINES store more granular billing details.
  • Pricing Integration: OKC_PRICE_ADJUSTMENTS and related tables link price adjustments (discounts, surcharges) to the specific billable line.
  • Financials Integration: OKL_TXD_AR_LN_DTLS_B indicates a link to detailed accounting entries, underscoring the table's role in the financial flow.