Results for “sel_id”

50+ results




Overview
Explore in AI Chat

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

Overview

OKL_RCPT_ARINV_BALANCES_UV is an APPS-owned database view within the Oracle E-Business Suite Release 12.1.1 and 12.2.2 environment, delivered as part of the OKL (Leasing and Finance Management) product family. The view consolidates Oracle Receivables invoice data with Oracle Leasing contract and transaction-detail data, producing a unified projection of open and original receivable balances tied to lease contracts. Its primary role is to support receipt application, balance inquiry, and reconciliation reporting across the Leasing and Receivables modules without requiring callers to join the underlying transaction, customer, and contract tables directly. Because it is a view rather than a table, it stores no data of its own; all values are derived at runtime from the base objects listed below.

Underlying Base Objects

The ETRM metadata documentation identifies the following referenced base objects, all accessed through APPS synonyms:

Joins are driven by CUSTOMER_TRX_ID, CUSTOMER_TRX_LINE_ID, BILL_TO_CUSTOMER_ID to CUST_ACCOUNT_ID, PARTY_ID, and ID to the OKL transaction-detail record. Rows are restricted to CUST_TRX_LINES.LINE_TYPE = 'LINE' and INTERFACE_LINE_ATTRIBUTE1 IS NULL, excluding interface-staged lines.

Key Columns

The view exposes identifiers, descriptive attributes, and financial measures. Identifying columns include INVOICE_NUMBER, AR_INVOICE_ID, INVOICE_LINE_ID, LINE_IDENTIFIER, ORG_ID, and BILL_TO_SITE_USE_ID. Customer context is provided by CUSTOMER_NAME, CUSTOMER_NUMBER, CUSTOMER_ACCT_ID, and CUSTOMER_ACCOUNT_NUMBER. Lease context is supplied through CONTRACT_NUMBER, START_DATE, KHR_ID, KLE_ID, SEL_ID, STY_ID, plus ASSET_NUMBER (INTERFACE_LINE_ATTRIBUTE7) and STREAM_TYPE (INTERFACE_LINE_ATTRIBUTE9). Financial columns include INVOICE_CURRENCY_CODE, AMOUNT_DUE_ORIGINAL (line extended amount plus linked tax extended amounts), AMOUNT_DUE_REMAINING (line plus linked tax remaining amounts), and INVOICE_DUE_DATE and STATUS from the payment schedule.

Common Use Cases and Queries

Typical uses include aging analysis of lease-related receivables, reconciliation of contract streams to invoice balances, and inquiry screens showing outstanding amounts per lease. A representative query retrieves open balances by contract:

  • SELECT CONTRACT_NUMBER, INVOICE_NUMBER, CUSTOMER_NAME, AMOUNT_DUE_REMAINING FROM OKL_RCPT_ARINV_BALANCES_UV WHERE AMOUNT_DUE_REMAINING > 0 ORDER BY INVOICE_DUE_DATE;
  • SELECT CONTRACT_NUMBER, SUM(AMOUNT_DUE_ORIGINAL) ORIGINAL_TOTAL, SUM(AMOUNT_DUE_REMAINING) OPEN_TOTAL FROM OKL_RCPT_ARINV_BALANCES_UV GROUP BY CONTRACT_NUMBER;
  • SELECT INVOICE_NUMBER, ASSET_NUMBER, STREAM_TYPE, AMOUNT_DUE_REMAINING FROM OKL_RCPT_ARINV_BALANCES_UV WHERE ORG_ID = :p_org_id AND STATUS = 'OP';

Because the view joins Receivables with OKL transaction details, it should be used for read-only reporting and integration extracts rather than as a base for DML.