Search Results cleb_fee

Overview

APPS.OKL_LA_FEE_LINES_UV is a reporting view within the Oracle E-Business Suite (EBS) Lease and Finance Management (OKL) module, also referred to as the enterprise contract and lease management (ETRM) stack. It consolidates lease and loan fee line information by joining fee definitions held on lease contract line items with their associated Origination, Contract, and Party role records, and it exposes a flattened result set suitable for reporting, extraction, and integration rather than for transactional update. The view presents fee-level detail including fee type, fee amount, fee purpose, funding and date ranges, origination identifiers, party (vendor or investor) attribution, and rule-based frequency information. Because the view is defined in the APPS schema, it is intended to be queried by reporting tools and interface programs operating under standard EBS responsibility security rather than being modified directly.

Underlying Base Objects

The view is defined over a set of documented base objects that span contract, party, lookup, and rules data. The OKC_K_ITEMS and OKC_K_LINES_B synonyms supply contract line context, while OKC_K_PARTY_ROLES_B provides the party role assignments that the view resolves into vendor or investor names. OKL_K_LINES and OKL_STRM_TYPE_TL supply lease line and stream type information, and OKL_TIME_UNITS_V supports the frequency unit of measure through the TUOM alias and FREQUENCY_NAME column. Rule frequency detail is drawn through OKC_RULES_B and OKC_RULE_GROUPS_B, referenced by the RUL_LAFEXP and RUL_LAFREQ aliases. FND_LOOKUPS is joined to resolve the fee type meaning via the LKP_FEE_TYPE alias, and FND_GLOBAL is referenced to supply session context values such as the current user and login. OKX_PARTIES_V and PO_VENDORS are joined to derive party names for investor and vendor role codes respectively, and OKC_RULES_B also underpins the rule information returned for each fee line.

Key Columns

• CLEB_FEE_ID, DNZ_CHR_ID, ORIG_SYSTEM_ID1 — Identifiers for the lease fee record, the owning contract/header, and the originating system reference.
• FEE_TYPE, FEE_TYPE_NAME — The fee type code from OKL_K_LINES and its decoded meaning resolved from FND_LOOKUPS.
• AMOUNT, INITIAL_DIRECT_COST, FUNDING_DATE — The fee amount, its initial direct cost value, and the date the fee was funded.
• FEE_PURPOSE_CODE — Classifies the purpose of the fee line.
• START_DATE, END_DATE — Validity window for the fee line.
• CPLB_FEE_ID, CPLB_FEE_VENDOR_NAME, CPLB_FEE_RLE_CODE — Party role record and the resolved vendor or investor name, chosen via a DECODE on the role code.
• CIM_FEE_ID, CIM_FEE_STY_NAME, CIM_FEE_OBJECT1_CODE — Related contract line item context and its stream type name.
• QTE_ID — The quote identifier associated with the fee.
• RUL_LAFREQ_ID, FREQUENCY_NAME, RULE_INFORMATION1 — Rule frequency identifiers, the resolved frequency unit of measure, and rule information text.
• ATTRIBUTE_CATEGORY, ATTRIBUTE1 … ATTRIBUTE15 — Descriptive flexfield context and segment values carried from the fee definition.

Common Use Cases and Queries

The view is typically used to produce fee schedules, fee accrual extracts, investor/vendor fee reconciliations, and integration feeds into downstream financial systems. A common pattern filters by contract header and date range and projects the fee and party columns:

SELECT cleb_fee_id, dnz_chr_id, fee_type_name, amount, initial_direct_cost,
      start_date, end_date, cplb_fee_vendor_name, funding_date
  FROM apps.okl_la_fee_lines_uv
 WHERE dnz_chr_id = :p_chr_id
   AND start_date >= :p_from_date
   AND (end_date IS NULL OR end_date <= :p_to_date)
 ORDER BY start_date, fee_type_name;

For frequency-based fee analysis, join conditions on RUL_LAFREQ_ID and FREQUENCY_NAME support grouping of recurring charges, while RULE_INFORMATION1 exposes the rule detail. Integration queries generally select the ORIG_SYSTEM_ID1, QTE_ID, and attribute segment columns to map lease fee lines into external accounting or treasury applications. Because the view reads only and contains no bind parameters, it can be safely embedded in Oracle Reports, BI Publisher data templates, and SQL-based interface programs in both 12.1.1 and 12.2.2 environments.