Search Results cim_fee_object1_code

Overview

OKL_LA_FEE_LINES_UV is a view owned by the APPS schema within the OKL – Leasing and Finance Management module of Oracle E-Business Suite. The "_UV" suffix identifies it as a user-facing view intended to present fee line information in a business-friendly form, resolving the internal IDs and codes held on the underlying transaction tables into descriptive values. The view consolidates fee data that originates across three separate relational structures — lease fees, contract-line items, and rule-driven expense and frequency definitions — into a single flattened result set aligned to a lease contract identifier (DNZ_CHR_ID).

The object is central to reporting and integration scenarios in Oracle Leases (OLM/OKL), where users need to list the fees attached to a lease or quote, identify the fee type by its displayed meaning, review the vendor paying or receiving the fee, and inspect the scheduled amount and frequency. It is registered as VALID in the ETRM 12.2.2 metadata, with an equivalent footprint in 12.1.1.

Underlying Base Objects

The view is defined over a collection of synonyms and views spanning the OKC contracts infrastructure and the OKL leasing tables. Documented base objects include OKC_K_LINES_B (contract lines), OKC_K_ITEMS (line items), OKC_K_PARTY_ROLES_B (contract party roles), OKC_RULE_GROUPS_B and OKC_RULES_B (rule group and rule definitions), OKL_K_LINES (the leasing extension of contract lines), OKL_STRM_TYPE_TL (stream type translations), OKL_TIME_UNITS_V (time unit lookup), OKX_PARTIES_V (parties view), PO_VENDORS (supplier master), FND_LOOKUPS (lookup meanings), and the FND_GLOBAL package for session context.

The dominant join key is the contract/lease header ID, appearing as DNZ_CHR_ID from the contract line base (CLEB_FEE alias). Fee-rule and expense-rule records are joined via rule groups to bring back the frequency (RUL_LAFREQ) and the rule-name context (RGP_LAFEXP). Vendor information is drawn through PO_VENDORS, while FND_LOOKUPS supplies the translated lookup meaning.

Key Columns

• FEE_TYPE / FEE_TYPE_NAME — the internal fee type code and its translated lookup meaning. This is the column most frequently targeted when users search on "fee_type_name".
• CLEB_FEE_ID / DNZ_CHR_ID — the contract-line identifier and the lease/contract header identifier (character form).
• ORIG_SYSTEM_ID1 — the originating source identifier, useful for cross-referencing with feeder systems.
• AMOUNT — the value of the fee line as recorded on the fee rule.
• INITIAL_DIRECT_COST — the portion of the fee treated as a direct cost.
• CPLB_FEE_VENDOR_NAME — the supplier name associated with the payable fee party role.
• CPLB_FEE_RLE_CODE / CPLB_FEE_OBJECT1_ID1 / OBJECT1_ID2 — the party role code and identifying keys for the payable fee vendor.
• START_DATE / END_DATE — the effective period of the fee line.
• FUNDING_DATE / QTE_ID — funding reference and quote identifier.
• FREQUENCY_NAME — the billing or expense frequency in readable form (from OKL_TIME_UNITS_V).
• FEE_PURPOSE_CODE / SALES_TAX_FEE_YN — purpose classification and an indicator of tax treatment.
• ATTRIBUTE1 through ATTRIBUTE15 — the DFF flexfield values carried through from the fee rule table.

Common Use Cases and Queries

Analysts and integrators use this view to reconcile fee schedules per lease, to validate that a fee type is configured and translated correctly, and to drill from a quote or contract into vendor payables. A typical query filters by lease header and includes the translated fee type name:

SELECT DNZ_CHR_ID, FEE_TYPE, FEE_TYPE_NAME, AMOUNT, START_DATE, END_DATE, CPLB_FEE_VENDOR_NAME, FREQUENCY_NAME FROM APPS.OKL_LA_FEE_LINES_UV WHERE DNZ_CHR_ID = :p_chr_id ORDER BY FEE_TYPE_NAME, START_DATE;

A complementary query lists the distinct fee types currently in use, which helps users confirm the meaning behind a "fee_type_name" value they encountered in a report or on a lease form:

SELECT DISTINCT FEE_TYPE, FEE_TYPE_NAME FROM APPS.OKL_LA_FEE_LINES_UV ORDER BY FEE_TYPE_NAME;

Because the view joins contract, rule, party, and vendor structures, it is best consumed in read-only reporting contexts. Trace flag or debug-level logging should be enabled only when diagnosing performance issues on large lease portfolios.