Search Results okl_frequency




Overview
Explore in AI Chat

Overview

OKL_PAYMENT_FREQUENCY_UV is an Oracle E-Business Suite view owned by the APPS schema. It exposes the set of enabled payment frequency lookup values used throughout Oracle Lease and Finance Management (OKL) and the broader E-Business Suite contracting and billing modules. The view is a presentation-layer object: rather than storing data of its own, it projects a filtered, ordered, and language-aware subset of Oracle Application Object Library (FND) lookup values into a simple three-column result set suitable for concurrent programs, Oracle Forms LOVs, Oracle Application Framework (OAF) pages, and external integrations.

Its central role is to provide a single, consistent definition of the valid values for the OKL_FREQUENCY lookup type, so that every caller resolves the same code, the same user-facing name, and the same descriptive text. This guards against divergent hard-coded lists and ensures that translations follow the session's language setting.

Underlying Base Objects

The view is defined exclusively over FND_LOOKUP_VALUES, referenced in the ETRM metadata through the synonym FND_LOOKUP_VALUES. The underlying table, FND_LOOKUP_VALUES, is a core EBS internal table that holds the individual values belonging to each lookup type defined in FND_LOOKUP_TYPES.

The following documented predicates are applied:

  • LANGUAGE = USERENV('LANG') — restricts rows to the language of the current database session, ensuring the returned MEANING and DESCRIPTION reflect the user's locale.
  • LOOKUP_TYPE = 'OKL_FREQUENCY' — limits the result set to the payment frequency lookup type.
  • ENABLED_FLAG = 'Y' — excludes disabled values.
  • NVL(START_DATE_ACTIVE,SYSDATE) <= SYSDATE and NVL(END_DATE_ACTIVE, SYSDATE + 1) > SYSDATE — applies effective-dating so that only values active as of the current date are returned.

The final ORDER BY MEANING clause presents values alphabetically by their user-facing name.

Key Columns

  • NAME — mapped from FND_LOOKUP_VALUES.MEANING. This is the translatable, user-facing label presented to end users in lists and forms.
  • CODE — mapped from FND_LOOKUP_VALUES.LOOKUP_CODE. This is the internal, non-translatable identifier that is stored on transactional records and referenced by application logic.
  • DESCRIPTION — mapped from FND_LOOKUP_VALUES.DESCRIPTION. Provides optional supplementary text explaining the frequency value.

Although only three columns are projected, the filtering relies on the standard FND columns LANGUAGE, LOOKUP_TYPE, ENABLED_FLAG, START_DATE_ACTIVE, and END_DATE_ACTIVE.

Common Use Cases and Queries

The view is typically used to populate selection lists, validate user input, or drive reports and interfaces where a payment frequency code must be resolved to a display name or description.

  • Populating LOVs in payment, billing, and lease screens.
  • Reporting on payment frequencies along with their descriptive text.
  • Validating inbound interface data against accepted frequency codes.
  • Resolving a stored CODE to its translated NAME for output and printing.

Representative queries include:

SELECT code, name, description FROM apps.okl_payment_frequency_uv;

SELECT name FROM apps.okl_payment_frequency_uv WHERE code = :p_code;

SELECT code, name FROM apps.okl_payment_frequency_uv ORDER BY name;

Because the view already enforces language, enabled status, and effective dates, callers do not need to repeat those predicates. Values configured or disabled in FND flow automatically into the view, so maintenance remains centralized.