Search Results okl_fees_v




Overview
Explore in AI Chat

Overview

OKL_FEES_V is a valid, APPS-owned database view within the Oracle Lease and Finance Management (OKL) module, available in Oracle E-Business Suite 12.1.1 and 12.2.2. It presents fee and charges information defined against lease and finance contracts and quotes. The view consolidates data from the two principal fees tables — OKL_FEES_B, which stores the base, language-independent fee attributes, and OKL_FEES_TL, which stores the translated, language-dependent descriptive columns. By joining these tables on the fee ID and the session language, OKL_FEES_V exposes a single, joined row per fee that includes both functional and descriptive attributes.

Because it is a database view rather than a form or a public API, it is intended primarily for reporting, extraction, and integration. It gives read access to the fee records that support pricing, upfront and periodic charges, and contract-level cost elements. Form development and internal processing generally read directly from the base tables, but the view provides a convenient join that application developers can use without replicating the base/translation join logic themselves.

Underlying Base Objects

According to the documented metadata, the view is defined over two referenced base objects: OKL_FEES_B and OKL_FEES_TL, both referenced as synonyms within the APPS schema. The view text confirms the relationship: rows from OKL_FEES_B (aliased FEE) are matched to rows from OKL_FEES_TL (aliased FEET) with the condition FEE.ID = FEET.ID, restricted further by FEET.LANGUAGE = USERENV('LANG').

Because the join filters on the language environment, the view returns only the translation row matching the logged-in user's language, ensuring descriptions appear in the appropriate language.

Key Columns

The view exposes a broad set of columns inherited from the base tables. Important columns include FEE.ID, the primary identifier; ROW_ID, the ROWID of the base row; and OBJECT_VERSION_NUMBER, used for optimistic locking. PARENT_OBJECT_CODE and PARENT_OBJECT_ID identify the owning business object (such as a lease or quote) to which the fee belongs. STREAM_TYPE_ID links the fee to a pricing stream, while FEE_TYPE classifies the fee.

Pricing-related columns include STRUCTURED_PRICING, RATE_TEMPLATE_ID, RATE_CARD_ID, LEASE_RATE_FACTOR, TARGET_ARREARS, and TARGET_AMOUNT, supporting rate and yield calculations. Financial columns include FEE_AMOUNT, INITIAL_DIRECT_COST, SUPPLIER_ID, PAYMENT_TYPE_ID, and TARGET_FREQUENCY. Effective dating is handled by EFFECTIVE_FROM and EFFECTIVE_TO, and ROLLOVER_QUOTE_ID and FEE_PURPOSE_CODE provide additional context. Descriptive columns SHORT_DESCRIPTION, DESCRIPTION, and COMMENTS come from the translation table.

Common Use Cases and Queries

Typical uses include reconciling fees on lease contracts, extracting contract cost components for reporting, and validating fee setup prior to downstream pricing. Because the view is read-only, it is safe for ad hoc queries and integration extracts.

  • List fees for a contract: SELECT id, fee_type, fee_amount, effective_from FROM okl_fees_v WHERE parent_object_id = :p_id;
  • Show fees with descriptions: SELECT id, short_description, fee_type, fee_amount FROM okl_fees_v;
  • Effective-dated pricing: SELECT id, lease_rate_factor, effective_from, effective_to FROM okl_fees_v WHERE sysdate BETWEEN effective_from AND NVL(effective_to, sysdate);

Queries should account for translated text by relying on the view's language filter rather than joining OKL_FEES_TL separately, which would risk returning duplicate or non-language rows.