Results for “tld_new”

4 results




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

Overview

The Oracle E-Business Suite view APPS.OKL_AM_RMK_BILLING_UV belongs to the Oracle Lease and Finance Management (OKL) module. It is a read-only reporting view (the _UV suffix designates a user view) that consolidates asset return information with billing, invoicing, and address data for leased assets. Its principal purpose is to expose a denormalized, query-friendly projection that links returned lease assets to their associated order lines, contracts, items, billing transactions, and bill-to addresses. The view is defined over eleven base objects and is intended for use in report generation, integration extracts, and analytical queries where users require a single flattened row per returned asset/invoice combination rather than navigating the underlying normalized lease, order, and receivables schemas.

Underlying Base Objects

The view draws from a set of documented APPS objects, joined on their respective keys. The driver of the query is OKL_ASSET_RETURNS_ALL_B, aliased ART. It joins to OKL_K_LINES_FULL_V (KLE) on the line ID, and to OKC_K_HEADERS_B (KHR) through the line's contract header ID. Order data is supplied by OE_ORDER_HEADERS_ALL (ORH) and OE_ORDER_LINES_ALL (ORL), joined on HEADER_ID and linked to the returned asset via INVENTORY_ITEM_ID. Item master attributes come from MTL_SYSTEM_ITEMS_B_KFV (MSI).

Billing and invoice details are provided by OKL_BPD_TLD_AR_LINES_V (TLD_NEW), a view sourced from billing transaction-line data linked to the aggregate transaction lines. Receivables data is joined via AR_PAYMENT_SCHEDULES_ALL (PLS), which supplies the outstanding line-item amount. Bill-to address components are assembled from HZ_CUST_ACCT_SITES_ALL (CAS), HZ_PARTY_SITES (PST), and HZ_LOCATIONS (LOC), with the formatted address rendered through the ARP_ADDR_LABEL_PKG package. The view's logic is also associated with the OKL_BILLING_UTIL_PVT package. Note that the documented view text is a partial excerpt ending mid-join on TLD_NEW.ISL_ID.

Key Columns

Common Use Cases and Queries

Typical scenarios include lease return reporting, invoice reconciliation, and asset-level revenue analysis. A representative query selecting key billing attributes:

SELECT asset_number,
       contract_number,
       invoice_number,
       total_invoice_amount,
       outstanding_invoice_amount,
       bill_date
  FROM apps.okl_am_rmk_billing_uv
 WHERE contract_number = :p_contract_number
 ORDER BY bill_date DESC;

For outstanding balance analysis by item:

SELECT item_number,
       SUM(outstanding_invoice_amount) outstanding
  FROM apps.okl_am_rmk_billing_uv
 GROUP BY item_number
HAVING SUM(outstanding_invoice_amount) > 0;

Because the view joins many tables, filtering on indexed identifiers, such as KLE_ID, CONTRACT_NUMBER, or INVOICE_NUMBER, yields the best performance.