Search Results okl_todo_items




Overview
Explore in AI Chat

Overview

APPS.OKL_CHECKLIST_TODO_UV is a lightweight lookup-based view in the Oracle E-Business Suite (EBS) Enterprise Contracts (formerly Oracle Lease and Finance Management, OKL) schema. It exposes the set of valid "to-do item" codes used by contract checklists and to-do tracking functionality. Rather than storing business data in a dedicated transactional table, the view derives its rows from the Oracle Applications common lookup facility, filtering the generic FND_LOOKUPS view by the lookup type OKL_TODO_ITEMS. This design means the list of available to-do items is administered as application reference data (through the Lookups form or concurrent loaders) rather than through seeded or user-entered transactional records.

In the context of EBS 12.1.1 and 12.2.2, the "UV" suffix conventionally denotes a user view intended for read-only consumption, typically for reports, integrations, and extensions. It presents a denormalized, presentation-friendly shape of the underlying lookup rows, so consumers do not need to know the lookup type code or apply date logic themselves.

Underlying Base Objects

The view is defined over a single documented base object: the view FND_LOOKUPS. FND_LOOKUPS is the standard Oracle Applications view over the lookup type and lookup code tables (FND_LOOKUP_TYPES and FND_LOOKUP_VALUES in the base schema), and it surfaces the lookup codes, their meanings, descriptions, and active date ranges.

OKL_CHECKLIST_TODO_UV applies a WHERE clause restricting rows to LOOKUP_TYPE = 'OKL_TODO_ITEMS'. The documented metadata also references FND_GLOBAL (PACKAGE), which is the standard EBS server-side package providing session context such as user ID, responsibility, and application. Its listing typically reflects a dependency introduced by EBS view compilation or by the surrounding reporting framework rather than a direct join in the view body; the view SQL itself does not select from FND_GLOBAL. In practice the view sits purely on top of the lookup data model, with no OKL transaction tables involved.

Key Columns

The view projects five columns, each derived from the matching FND_LOOKUPS row:

  • TODO_ITEM_CODE — the lookup code (LOOKUP_CODE); the technical identifier for a to-do item.
  • TODO_ITEM_MEANING — the display meaning (MEANING) shown to users, suitable for report labels.
  • DESCRIPTION — the longer descriptive text (DESCRIPTION) for the to-do item.
  • EFFECTIVE_FROM — NVL of START_DATE_ACTIVE; defaults to SYSDATE when no start date is defined.
  • EFFECTIVE_TO — NVL of END_DATE_ACTIVE; defaults to SYSDATE+3650 when no end date is defined, effectively treating an open-ended lookup as valid for roughly ten years.

Note that the view does not itself filter on the effective dates; consumers requiring only currently active to-do items must apply their own date predicates against EFFECTIVE_FROM and EFFECTIVE_TO.

Common Use Cases and Queries

Typical uses include validating to-do item codes entered on checklist or contract interfaces, populating LOV-style lists in custom forms, and joining checklist or task records back to human-readable meanings and descriptions. A basic query listing all defined to-do items is:

  • SELECT todo_item_code, todo_item_meaning, description, effective_from, effective_to FROM apps.okl_checklist_todo_uv ORDER BY todo_item_meaning;

To restrict to to-do items that are currently effective, add date predicates on the derived columns:

  • SELECT todo_item_code, todo_item_meaning FROM apps.okl_checklist_todo_uv WHERE SYSDATE BETWEEN effective_from AND effective_to ORDER BY todo_item_code;

A validation check for a single code can be written as a simple existence test:

  • SELECT todo_item_meaning FROM apps.okl_checklist_todo_uv WHERE todo_item_code = :p_todo_item_code;

Because the view is read-only and driven entirely by lookup configuration, adding or retiring to-do items requires changes to the OKL_TODO_ITEMS lookup values, not to the view definition.