Search Results bill_from_to

Overview

APPS.OKS_BILLING_DTLS_V is a reporting view in Oracle Enterprise Business Suite (EBS) 12.1.1 and 12.2.2 that consolidates billing detail information generated by the Oracle Service Contracts (OKS) module. The view joins transaction, contract line, and sub-line records to present a flattened, denormalized picture of invoicing activity associated with service contract billing. It is commonly used for extracting billed amounts, tax amounts, invoice identifiers, and billing periods for contracts and their associated service lines.

Because the view exposes the billing period through the columns BILL_FROM_DATE and BILL_FROM_TO, it is frequently the object referenced by users and developers searching for "bill_from_to" — that is, the date range over which a billing instance or contract line was billed. This makes the view especially relevant for reconciliation, revenue recognition support, and audit reporting where the billed-through period must be identified.

Underlying Base Objects

The view is defined over four base objects, all documented as synonyms owned by APPS:

• OKS_BILL_TRANSACTIONS — header-level billing transaction records (invoice-level attributes such as TRX_NUMBER, TRX_DATE).
• OKS_BILL_TXN_LINES — line-level billing transaction records (line amounts, tax amounts, bill instance).
• OKS_BILL_CONT_LINES — contract billing lines, which supply the billed-from and billed-to dates.
• OKS_BILL_SUB_LINES — sub-line records tying a contract line to a service line (CLE_ID) and billing schedule (BCL_ID).

The joins established in the view text are: OKS_BILL_SUB_LINES.BCL_ID = OKS_BILL_CONT_LINES.ID, OKS_BILL_CONT_LINES.BTN_ID = OKS_BILL_TRANSACTIONS.ID, OKS_BILL_TRANSACTIONS.ID = OKS_BILL_TXN_LINES.BTN_ID, and OKS_BILL_TXN_LINES.BSL_ID = OKS_BILL_SUB_LINES.ID. This four-way join produces one row per billing transaction line matched to its contract line and sub-line.

Key Columns

• INVOICE_NUMBER — sourced from OKS_BILL_TRANSACTIONS.TRX_NUMBER; identifies the invoice or transaction.
• INVOICE_DATE — sourced from OKS_BILL_TRANSACTIONS.TRX_DATE; the transaction date.
• INVOICE_LINE_AMOUNT — sourced from OKS_BILL_TXN_LINES.TRX_LINE_AMOUNT; the billed line amount.
• INVOICE_LINE_TAX_AMOUNT — sourced from OKS_BILL_TXN_LINES.TRX_LINE_TAX_AMOUNT; tax on the billed line.
• BILL_INSTANCE_NUMBER — sourced from OKS_BILL_TXN_LINES.BILL_INSTANCE_NUMBER; indicates which billing instance produced the line.
• BILL_FROM_DATE — sourced from OKS_BILL_CONT_LINES.DATE_BILLED_FROM; start of the billed period.
• BILL_FROM_TO — sourced from OKS_BILL_CONT_LINES.DATE_BILLED_TO; the billed-through date, i.e., end of the billed period.
• CLE_ID — sourced from OKS_BILL_SUB_LINES.CLE_ID; identifies the contract line / service element.
• BCL_ID — sourced from OKS_BILL_SUB_LINES.BCL_ID; identifies the billing schedule line.

Common Use Cases and Queries

The view supports reconciliation of service contract invoices, verification of billed periods, and reporting on billed versus unbilled service. A representative query retrieving the billed period alongside invoice detail:

SELECT invoice_number,
       invoice_date,
       bill_instance_number,
       bill_from_date,
       bill_from_to,
       invoice_line_amount,
       invoice_line_tax_amount,
       cle_id,
       bcl_id
FROM   apps.oks_billing_dtls_v
WHERE  bill_from_to BETWEEN :start_date AND :end_date
ORDER  BY invoice_number, cle_id;

Because BILL_FROM_TO represents the billed-through date, filtering on it allows analysts to isolate all lines that cover a given period — a frequent requirement when validating accruals or identifying gaps in billing coverage. Joining CLE_ID back to the contract line tables further enables linkage to customer and contract attributes not exposed by this view. As with all views in the APPS schema, users should be assigned appropriate responsibility-level access before querying directly.