Search Results okl_payment_frequency_uv




Overview
Explore in AI Chat

Overview

The OKL_PAYMENT_FREQUENCY_UV view is a UI-support database object owned by the APPS schema within the Oracle E-Business Suite (EBS) Leasing and Finance Management (OKL) module. Its documented purpose is to serve as the "Securitization - Payment frequency UI view." The view presents a filtered, presentation-ready list of payment frequency values that the ETRM (Enterprise Transaction and Reporting Management / Leasing) application surfaces to end users across securitization and contract-related user interfaces.

Rather than storing transactional data, the object is a lightweight reference view. It exposes the set of valid, active payment frequency codes and their descriptive meanings so that forms, list-of-values (LOVs), and dependent UI components can populate selection lists consistently. In the context of reporting and integration, the view functions as a lookup abstraction layer: downstream queries, concurrent programs, or external interfaces that need the canonical list of payment frequencies can select from this view instead of writing bespoke predicates against the underlying lookup table.

Underlying Base Objects

The view is defined over a single documented base object, FND_LOOKUP_VALUES (accessed via synonym), which is the standard EBS repository of lookup codes maintained in Oracle Application Object Library. The view text applies a fixed set of filters to that table:

  • LANGUAGE = USERENV('LANG') — restricts rows to the language of the current session, ensuring the displayed meaning matches the user's locale.
  • LOOKUP_TYPE = 'OKL_FREQUENCY' — isolates only the payment frequency lookup set defined for the Leasing product.
  • ENABLED_FLAG = 'Y' — excludes disabled lookup values.
  • Date-range predicates on START_DATE_ACTIVE and END_DATE_ACTIVE — returns only frequencies that are currently in effect as of the query execution date.

Because the view depends entirely on FND_LOOKUP_VALUES, its content is governed by the Lookup Types setup in the application. Setting up or deactivating an OKL_FREQUENCY lookup value directly changes the rows returned by this view.

Key Columns

The view exposes three columns, each mapped from a corresponding field in FND_LOOKUP_VALUES:

  • NAME — the translated MEANING of the lookup value; the user-facing label shown in payment frequency selections.
  • CODE — the LOOKUP_CODE, the internal, language-independent identifier stored on leasing transactions and used by application logic.
  • DESCRIPTION — the optional descriptive text associated with the frequency, providing additional context to end users.

The rows returned are ordered by NAME (meaning), giving a stable, alphabetically presented list for UI rendering.

Common Use Cases and Queries

This view is typically referenced when building or troubleshooting payment frequency selection lists, validating that a given frequency code is currently active, and reconciling UI selections against reference data. A typical query is:

  • List all active frequencies for a UI/LOV: SELECT NAME, CODE, DESCRIPTION FROM APPS.OKL_PAYMENT_FREQUENCY_UV ORDER BY NAME;
  • Validate a specific frequency code: SELECT CODE, NAME FROM APPS.OKL_PAYMENT_FREQUENCY_UV WHERE CODE = :p_code;
  • Diagnose a "missing" frequency: when a value expected in the UI does not appear, DBA and support teams compare this view's output against FND_LOOKUP_VALUES for LOOKUP_TYPE = 'OKL_FREQUENCY' to detect disabled flags or expired date ranges.
  • Integration mapping: external interfaces join NAME to source system frequency descriptions while transmitting CODE as the persistent key.

Because it is a simple, single-source lookup view, OKL_PAYMENT_FREQUENCY_UV performs efficiently and imposes no direct storage overhead; its correctness depends solely on the integrity of the OKL_FREQUENCY lookup configuration in the EBS environment.