Results for “invoice_class”

AI-generated from documented ETRM metadata — verify critical details on the linked pages.

Overview

OKS_INV_RVW_V is a reporting view owned by the APPS schema in Oracle E-Business Suite, delivered as part of the OKS – Service Contracts module. Its documented purpose is invoice reporting: it consolidates billing and invoice information generated by the Service Contracts billing engine into a single, denormalized result set suitable for reporting, integration extracts, and ad-hoc inquiry. The view is registered as VALID and is classified as a VIEW object in the ETRM repository for both 12.1.1 and 12.2.2.

The view is particularly relevant to users searching on the term bill_instance_number, since it explicitly exposes the BILL_INSTANCE_NUMBER column sourced from OKS_BILL_TXN_LINES. This column identifies the billing instance associated with a given invoice line, allowing report authors to trace an invoice back to the specific billing instance processed by the contracts billing engine.

Underlying Base Objects

The documented metadata lists the following referenced base objects: FND_GLOBAL (PACKAGE), FND_LOOKUPS (VIEW), OKS_BILL_CONT_LINES (SYNONYM), OKS_BILL_SUB_LINES (SYNONYM), OKS_BILL_TRANSACTIONS (SYNONYM), and OKS_BILL_TXN_LINES (SYNONYM). The synonyms resolve to the corresponding OKS tables in the APPS schema.

The view definition is a UNION ALL of two branches. In the first branch, OKS_BILL_TRANSACTIONS (BTR), OKS_BILL_TXN_LINES (BTL), and OKS_BILL_CONT_LINES (BCL) are joined on BTR.ID = BTL.BTN_ID and BCL.BTN_ID = BTR.ID, with BTL.BCL_ID = BCL.ID. The transaction type is resolved through FND_LOOKUPS using LOOKUP_TYPE = 'OKS_BILL_ACTIONS'. This branch is restricted to lines where BTL.BSL_ID IS NULL — that is, contract-level lines without a subordinate sub-line. The second branch adds OKS_BILL_SUB_LINES (BSL) and returns only lines where BTL.BSL_ID = BSL.ID, providing sub-line billing detail.

Key Columns

• BCL_ID / BCL_CLE_ID / BSL_CLE_ID — Identifiers for the contract line and, where applicable, the contract sub-line.
• INVOICE_NUMBER / INVOICE_CLASS — Derived via NVL from the transaction line or transaction header, representing the invoice document number and class.
• TRANSACTION_TYPE — The lookup meaning from FND_LOOKUPS describing the billing action.
• BTN_ID / BTL_ID — Foreign keys to the billing transaction header and its line.
• BILL_INSTANCE_NUMBER — The billing instance number from OKS_BILL_TXN_LINES, used to group and trace billed instances.
• INVOICE_DATE — The transaction date, taken from the line or header via NVL.
• BCL_BILL_FROM_DATE / BCL_BILL_TO_DATE / BSL_BILL_FROM_DATE / BSL_BILL_TO_DATE — Billing period boundaries at contract line and sub-line level. The sub-line columns resolve to NULL in the first UNION branch.
• CURRENCY_CODE — Taken from OKS_BILL_CONT_LINES.

Common Use Cases and Queries

Typical usage includes reconciliation of billed instances to invoices and analysis of billing periods by contract line. A representative query filtering on the billing instance number is:

SELECT invoice_number,
       invoice_class,
       transaction_type,
       bill_instance_number,
       invoice_date,
       bcl_bill_from_date,
       bcl_bill_to_date,
       currency_code
  FROM apps.oks_inv_rvw_v
 WHERE bill_instance_number = :p_bill_instance_number;

Reports aggregating invoice totals by transaction type or billing period may join the view to OKS contracts data using BCL_CLE_ID or BTN_ID. Because the view applies a UNION ALL, callers should anticipate that a single billing transaction may appear in both branches, and filters on BSL-specific columns are meaningful only for sub-line rows.