Search Results rgp_labill_lapmth_id




Overview
Explore in AI Chat

Overview

The OKL_OR_ASSET_BILLING_SETUP_UV view is a user-facing (UV) database object in the APPS schema belonging to the OKL – Lease and Finance Management product family. In ETRM 12.1.1 and 12.2.2 it is primarily consumed as a data source for Oracle Reports and Oracle Bills of Material (BOM) report layouts. The view exposes billing setup information associated with lease contract lines — the contract line description, the leased asset description, the bill-to site and customer account site, and a set of placeholder columns reserved for Originations (OR) billing-related flexfields and identifiers.

The view is a read-only construct: it contains no DML logic and no procedural code. Its columns are either sourced directly from the underlying OKC and HZ objects, or are literal TO_CHAR(NULL) placeholders, indicating that the columns are defined in the report/layout metadata so that a reporting template can bind to them even when no underlying value exists. This is a common ETRM reporting pattern used to stabilise column lists for Oracle Reports (RDF) or XML Publisher output.

Underlying Base Objects

The documented base objects referenced by the view are:

  • OKC_K_LINES_B (SYNONYM) – the base (B) table holding contract line identifiers. In the view it is aliased as CLEB_FIN.
  • OKC_K_LINES_TL (SYNONYM) – the translated (TL) table holding contract line name and description. In the view it is aliased as CLET.
  • HZ_CUST_SITE_USES_ALL (SYNONYM) – the customer site-uses table from the Trading Community Architecture (TCA) model. In the view it is aliased as CSU.

The join structure is straightforward. OKC_K_LINES_B.ID is equated to OKC_K_LINES_TL.ID, giving the descriptive text of each contract line. The TCA customer site is outer-joined (CSU.SITE_USE_ID(+) = CLEB_FIN.BILL_TO_SITE_USE_ID) so that contract lines without an associated bill-to site still return a row.

Key Columns

Because the RGP_*, RUL_* and RGP_ID columns resolve to NULL in the view definition, any query that filters on them will return the full rowset regardless of the filter value. Their purpose is structural — they exist so that report templates referencing <RUL_LAPMTH_ID> or similar tokens compile and run without modification.

Common Use Cases and Queries

The view is most commonly queried when diagnosing why an asset-billing report displays blank payment-method, bank-account or invoice-detail fields, and when tracing the contract line that drives a billing setup row.

Typical simple query:

  • SELECT id, name, item_description, bill_to_site_name, rul_lapmth_id FROM apps.okl_or_asset_billing_setup_uv; – to enumerate all contract lines and their bill-to sites.
  • SELECT id, rul_lapmth_id, rul_labacc_name FROM apps.okl_or_asset_billing_setup_uv WHERE id = :line_id; – to inspect the placeholder columns for a specific contract line.
  • SELECT name, dnz_chr_id, cust_acct_site_id FROM apps.okl_or_asset_billing_setup_uv WHERE dnz_chr_id = :contract_id; – to list all lines belonging to one contract.

Because the join to HZ_CUST_SITE_USES_ALL is an outer join, rows with no bill-to site return NULL for BILL_TO_SITE_NAME, BILL_TO_SITE_USE_ID and CUST_ACCT_SITE_ID. Support engineers should be aware that NULLs returned from the RUL_* columns are by design in the base view and cannot be used to determine whether a billing rule was actually configured; the underlying OKL rule tables must be queried for that purpose.