Results for “okl_fee_types”

40 results




AI-generated from documented ETRM metadata — verify critical details on the linked pages.

Overview

APPS.OKL_PYMTS_FEE_INSTS_UV is a supplementary Oracle E-Business Suite view owned by the APPS schema, defined within the FND Design Data for the OKL (Oracle Lease and Finance Management) application. Consistent with its documented classification, the view is intended solely to simplify forms coding; Oracle explicitly warns that querying or altering data through it is not recommended, as its definition may change substantially between minor and major releases. The view presents fee-instance information associated with payment streams, combining contract line data with lookup-driven fee type descriptions. For users and integrators, its principal value lies in surfacing the FEE_TYPE_MEANING column — the human-readable label for a fee type — alongside the underlying FEE_TYPE_CODE, thereby removing the need to resolve FND_LOOKUPS independently. The object is recorded with VALID status and is referenced by the OKL_LA_PAYMENTS_PVT package, confirming its role as a supporting data source for lease-payment processing logic.

Underlying Base Objects

The view is defined over a set of contract-core and lease-management objects accessed through APPS synonyms: OKC_K_ITEMS, OKC_K_LINES_B, OKC_LINE_STYLES_B, OKC_STATUSES_B, OKL_K_LINES, the view OKL_STRMTYP_SOURCE_V, the FND_LOOKUPS view, and the FND_GLOBAL package. The OKC_* objects belong to Oracle Contracts Core and supply contract header and line structures, styles, and statuses. OKL_K_LINES and OKL_STRMTYP_SOURCE_V contribute lease-specific line and stream-type derivation data, while FND_LOOKUPS provides the lookup values from which FEE_TYPE_MEANING and FEE_TYPE_CODE are resolved. FND_GLOBAL is typically invoked to supply session context such as the current user, responsibility, or language, ensuring lookup meanings are returned in the appropriate locale. Because the view is a form-support construct rather than a base table, the joins among these objects are internalized and not exposed through the documented column list.

Key Columns

  • LINE_ID (NUMBER) — Identifier for the contract or payment line row exposed by the view.
  • KHR_ID (NUMBER) — Documented as a foreign key to the view OKL_K_HEADERS_V, linking each row back to the lease contract header.
  • LSE_ID (NUMBER) — Lease identifier associating the fee instance with a specific lease.
  • SERVICE_INST_NAME (VARCHAR2, 150) — Name of the service instance to which the fee applies.
  • SERVICE_INST_DESC (VARCHAR2, 1995) — Descriptive text for the service instance.
  • FEE_TYPE_MEANING (VARCHAR2, 80) — The fee type meaning; the descriptive lookup value most users search for when the requirement is expressed as "fee_type_meaning."
  • FEE_TYPE_CODE (VARCHAR2, 30) — The fee type code, the stored lookup value that FEE_TYPE_MEANING translates.

The pairing of FEE_TYPE_CODE and FEE_TYPE_MEANING is the central feature of the view: code provides a stable key for joins and filters, while meaning provides readable output for reports and forms.

Common Use Cases and Queries

Typical use cases include reconciling payment-level fee instances to lease contracts, displaying fee descriptions in custom forms or reports, and validating that fee codes map correctly to lookup meanings. The following query retrieves all fee instances with their descriptive fee type:

SELECT line_id, khr_id, lse_id, service_inst_name, fee_type_code, fee_type_meaning FROM apps.okl_pymts_fee_insts_uv;

A filtered query by fee type code supports targeted analysis. Because FEE_TYPE_MEANING derives from FND_LOOKUPS via FND_GLOBAL context, results reflect the language and lookup configuration of the querying session, which must be considered when comparing output across environments. Where a stable, supported integration path is required, the documented base objects — particularly OKL_K_LINES and FND_LOOKUPS — should be queried directly rather than this forms-support view.