Search Results cleb_fin

Overview

APPS.OKL_OR_ASSET_BILLING_SETUP_UV is a reporting and integration view in the Oracle E-Business Suite (EBS) 12.1.1 / 12.2.2 environment. It is an "OR" (Oracle Receivables) oriented view belonging to the OKL (Oracle Lease and Finance Management / ETRM) module. The view projects billing setup information for lease and finance contract lines, surfacing the relationship between a contract line (identified in OKC_K_LINES_B / OKC_K_LINES_TL) and its associated bill-to customer site (from HZ_CUST_SITE_USES_ALL). It is intended to provide downstream consumers, extensions, and reports with a single, denormalized source for asset billing configuration.

In the context of the user's search for "cleb_fin", the "fin" component refers to finance contract lines — the underlying OKC_K_LINES_B alias CLEB_FIN. The view name and its column set suggest it is designed to feed billing-related processing or reporting that requires the bill-to site, line description, and a large set of placeholder columns for billing parameters (payment terms, account, invoice, and invoice profile references).

Underlying Base Objects

The view is defined over three documented base objects (all exposed as SYNONYMs to the APPS schema):

• HZ_CUST_SITE_USES_ALL (alias CSU) — the customer site usages table, providing bill-to site location and account site information. Joined with an outer join ((+)) on SITE_USE_ID.
• OKC_K_LINES_B (alias CLEB_FIN) — the base line entity for contract lines, holding the line ID, contract header ID (DNZ_CHR_ID), and the bill-to site use reference.
• OKC_K_LINES_TL (alias CLET) — the translated line table, providing the line name and item description.

The join conditions are CLEB_FIN.ID = CLET.ID and CSU.SITE_USE_ID(+) = CLEB_FIN.BILL_TO_SITE_USE_ID. The outer join on the bill-to site means rows are still returned when no matching customer site usage exists, with the bill-to site columns returned as NULL.

Key Columns

• NAME / ITEM_DESCRIPTION — line name and item description from OKC_K_LINES_TL.
• ID, DNZ_CHR_ID, BILL_TO_SITE_USE_ID — the line ID, contract header ID, and bill-to site reference from OKC_K_LINES_B.
• BILL_TO_SITE_NAME, CUST_ACCT_SITE_ID — bill-to site location and customer account site ID from HZ_CUST_SITE_USES_ALL.
• RGP_* and RUL_* columns — a series of placeholders (returned as TO_CHAR(NULL)). These include RGP_LABILL_LAPMTH_ID, RGP_LABILL_LABACC_ID, RGP_LABILL_LAINVD_ID, RGP_LABILL_LAINPR_ID, RUL_LAPMTH_ID, RUL_LABACC_ID, RUL_LAINVD_ID, RUL_LAINPR_ID, RUL_LAPMTH_OBJECT1_ID1/ID2, RUL_LAPMTH_NAME, RUL_LABACC_OBJECT1_ID1/ID2, RUL_LABACC_NAME, RUL_LABACC_BANK_NAME, and RGP_ID. These are reserved for payment-term, account, invoice, and invoice-profile lookups (e.g., "LAPMTH" = payment method, "LABACC" = bank account, "LAINVD" = invoice, "LAINPR" = invoice profile) and are hardcoded NULL in this view definition, presumably to be populated by extension layers or a different view variant.

Common Use Cases and Queries

This view is typically used to report on the billing configuration of lease/finance contract lines, to identify lines missing a valid bill-to site (via the outer join), or to feed external systems that require contract line and customer site details. A typical query is:

• SELECT ID, DNZ_CHR_ID, BILL_TO_SITE_NAME, NAME, ITEM_DESCRIPTION FROM APPS.OKL_OR_ASSET_BILLING_SETUP_UV WHERE DNZ_CHR_ID = :contract_id;
• To find lines with no bill-to site: SELECT ID, NAME FROM APPS.OKL_OR_ASSET_BILLING_SETUP_UV WHERE BILL_TO_SITE_USE_ID IS NULL;

Because the RGP_ and RUL_ columns are NULL placeholders, consumers should not rely on them for billing parameter values in this view; they are reserved for the RGP/RUL identifier structure and may be populated in related views or by customer extensions.