Search Results okl_time_units_v




Overview
Explore in AI Chat

Overview

OKL_TIME_UNITS_V is a reporting and integration view owned by the APPS schema in Oracle E-Business Suite Release 12.1.1 and 12.2.2. It belongs to the OKL product, Oracle Lease and Finance Management. The view exposes the complete set of frequency time units available to Lease Management, presenting each unit as a discrete, user-facing value with an associated descriptive meaning. Rather than maintaining its own persistent data, the view derives its content dynamically from Oracle Application Object Library lookup values, specifically the lookup type OKL_FREQUENCY.

The view serves two distinct purposes. First, it acts as a read-only reference for reporting and querying against the allowed frequency units used in lease transactions and contract terms. Second, and more significantly for the application architecture, it is registered as the object source for the JTF object OKL_TUOM. That registration means the view underpins the object-level definition used by the JTF (Java Technology Framework) layer, enabling standard object metadata, validation, and LOV (list of values) behavior for time units throughout the Lease Management module. Changes to the underlying lookup values therefore propagate directly into the object definition without any separate synchronization step.

Underlying Base Objects

The ETRM documentation records a single referenced base object for this view: FND_LOOKUP_VALUES, accessed through a synonym. FND_LOOKUP_VALUES is the core lookup table in Oracle EBS, storing lookup codes, meanings, descriptions, language-specific values, and effective date ranges. The view definition filters this table on two conditions: the session language must match the user environment language via USERENV('LANG'), and the lookup type must equal OKL_FREQUENCY.

Because the view reads directly from FND_LOOKUP_VALUES and applies no aggregation or joining, its cardinality equals the number of active and inactive OKL_FREQUENCY lookup rows for the current language. There is no OKL-specific base table behind the view; all data originates in the common lookup infrastructure. This design ensures that Lease Management frequency units remain consistent with the standard EBS lookup maintenance model and can be extended or translated using the standard Application Developer responsibility.

Key Columns

  • NAME — Mapped from LOOKUP_MEANING. The translated, user-facing label for the time unit, such as monthly, quarterly, or annual.
  • DESCRIPTION — Mapped from DESCRIPTION on the lookup value, providing optional supplementary context.
  • START_DATE_ACTIVE — The date from which the time unit becomes effective.
  • END_DATE_ACTIVE — The date after which the time unit is no longer effective.
  • STATUS — A derived column. A DECODE expression compares the truncated system date against the start and end dates and returns 'A' for active or 'I' for inactive. Null start or end dates default to the current date, so a unit with no date bounds evaluates as active.
  • ENABLED_FLAG — The enabled flag from the lookup value, indicating whether the unit is available for selection independent of its date range.
  • PRIMARY_UOM_CODE — Always NULL in the view definition. It exists to satisfy the object source contract required by JTF object OKL_TUOM and carries no business data.

Two internal columns, ID1 and ID2, are also selected. ID1 holds the lookup code and ID2 is a literal '#'. These support the JTF object key structure rather than end-user reporting.

Common Use Cases and Queries

Typical use cases include populating list of values components for lease frequency selection, validating incoming integration payloads against permitted time units, and producing reference listings for configuration review or audit. Because STATUS is computed at query time, reports that must show historical or effective-dated behavior should filter on the date columns directly rather than relying solely on STATUS.

The following query lists currently active and enabled time units:

  • SELECT name, description, status, enabled_flag FROM okl_time_units_v WHERE status = 'A' AND enabled_flag = 'Y' ORDER BY name;

To retrieve the raw lookup code used in integration or object binding, query ID1 alongside the descriptive columns:

  • SELECT id1 lookup_code, name, start_date_active, end_date_active FROM okl_time_units_v ORDER BY name;

For auditing effective dates across all configured units, including inactive ones:

  • SELECT name, start_date_active, end_date_active, status FROM okl_time_units_v ORDER BY start_date_active;

Adding or changing frequency units should be performed through the standard lookup maintenance forms for lookup type OKL_FREQUENCY; no direct DML against the view is supported.