Results for “til_id_reverses”

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

Overview

The OKL_TXL_AR_INV_LNS_UV view is a user-facing (UV) database object owned by the APPS schema within the OKL - Leasing and Finance Management product family. It exposes transaction-line data associated with Accounts Receivable invoice generation for leasing contracts. In Oracle EBS 12.1.1 and 12.2.2, the view presents a flattened, multi-language-aware projection of the contract receivable invoice line tables, joining the base transaction-line entity (OKL_TXL_AR_INV_LNS_B), its translation table (OKL_TXL_AR_INV_LNS_TL), and the contract line header (OKC_K_LINES_B).

Because the view carries a ROW_ID and the full audit and WHO columns, it behaves much like a queryable base table for reporting, integration, and concurrent-program data extraction. The user search term date_bill_period_end maps directly to the DATE_BILL_PERIOD_END column surfaced by this view, indicating the object is commonly queried to analyze or reconcile the billing periods for which receivable invoice lines are generated. The view is registered as VALID in the ETRM repository, confirming that its dependencies resolved correctly at the time of documentation.

Underlying Base Objects

The view is defined over three documented base objects, all referenced as synonyms in the APPS schema:

• OKL_TXL_AR_INV_LNS_B — the primary base table (TILB) holding the transaction invoice line records, including amounts, quantities, billing-period dates, and the KLE_ID foreign key.
• OKL_TXL_AR_INV_LNS_TL — the translation table (TILT) supplying the language-specific DESCRIPTION, restricted by TILT.LANGUAGE = USERENV('LANG').
• OKC_K_LINES_B — the contract line base table (KLE), joined via an outer join (KLE.ID(+)) to supply the contract line number.

The join between TILB and TILT is an inner join on ID; the join to KLE is an outer join, so records lacking a matching contract line are still returned. The view also derives a literal column, LINE_TYPE, hard-coded as 'ITEM', and surfaces CONTRACT_LINE_NUMBER from the contract line table.

Key Columns

• ID / ROW_ID — primary identity and physical row locator of the transaction line.
• KLE_ID / CONTRACT_LINE_NUMBER — linking key to the contract line and its human-readable number.
• DATE_BILL_PERIOD_START / DATE_BILL_PERIOD_END — the billing period boundaries for which the invoice line applies; these are the columns most relevant to the user's search for date_bill_period_end.
• AMOUNT / QUANTITY / AMOUNT_APPLIED — monetary and quantity measures of the invoice line.
• RECEIVABLES_INVOICE_ID — the AR invoice identifier to which the line is associated.
• STY_ID / TAI_ID / TPL_ID / ACN_ID_COST — references to stream type, transaction type, template, and cost accounting distribution.
• DESCRIPTION — language-specific description from the TL table.
• ATTRIBUTE1–15 / ATTRIBUTE_CATEGORY — flexfield descriptor columns for extensibility.
• ORG_ID — multi-org operating unit discriminator, enabling operating-unit-secured queries.
• WHO columns (CREATED_BY, CREATION_DATE, LAST_UPDATED_BY, LAST_UPDATE_DATE, LAST_UPDATE_LOGIN) and concurrent-program columns (REQUEST_ID, PROGRAM_ID, PROGRAM_APPLICATION_ID, PROGRAM_UPDATE_DATE).

Common Use Cases and Queries

The view is typically used for reconciliation reporting, invoice-line auditing, and integration extracts where the billing period end date drives downstream processing. A representative query filtered on the searched column:

SELECT kle_id, line_number, contract_line_number,
       date_bill_period_start, date_bill_period_end,
       amount, receivables_invoice_id
FROM   apps.okl_txl_ar_inv_lns_uv
WHERE  date_bill_period_end BETWEEN :p_start AND :p_end
AND    org_id = :p_org_id;

Other common patterns include joining to AR invoice headers via RECEIVABLES_INVOICE_ID, aggregating AMOUNT by contract line to analyze billed versus applied amounts, and extracting ATTRIBUTE flexfields for interfacing into external systems. Because the view respects USERENV('LANG'), queries executed under different language sessions return translated descriptions. Multi-org access must be enforced through ORG_ID, as the view does not itself apply organizational security.