Search Results okl_checklist_todo_uv




Overview
Explore in AI Chat

Overview

OKL_CHECKLIST_TODO_UV is a user interface (UI) view owned by the APPS schema in the Oracle E-Business Suite Lease and Finance Management (OKL) module. Its documented purpose is to support the funding checklist to-do page. In practical terms, it presents the list of configurable "to-do" items that a lease or funding professional can select when building a funding checklist, converting the underlying Oracle Application Object Library lookup rows into a clean, page-ready result set.

The view is primarily a presentation and validation layer rather than a transactional object. It exposes the seeded (and any customer-extended) values of the OKL_TODO_ITEMS lookup type so that the checklist UI can render a pick list of valid to-do items. Because the view conforms to standard EBS lookup semantics, it is equally suitable for use in BI Publisher reports, custom OAF or Forms-based pages, and integration extracts where a normalized list of checklist to-do item codes and their descriptions is required. The view is reported as VALID in the ETRM metadata for 12.1.1 and 12.2.2.

Underlying Base Objects

The view is defined over a single documented base object: FND_LOOKUPS, the Oracle Application Object Library lookup values view. FND_LOOKUPS exposes the rows stored in the FND_LOOKUP_VALUES table, which holds the lookup codes, meanings, descriptions, and effective date ranges for each lookup type. The view filters that source with a fixed predicate of WHERE FLK.LOOKUP_TYPE = 'OKL_TODO_ITEMS', ensuring only to-do item lookup values are returned.

ETRM metadata also lists FND_GLOBAL (PACKAGE) as a referenced base object. This is a reference to the standard Oracle Application Object Library package that supplies session context such as user, responsibility, application, and login information; it is not a table, and no columns from FND_GLOBAL are projected by the view. The join between the view and its lookup source is therefore a simple, single-table selection with a type filter, which keeps performance predictable and avoids complex joins.

Key Columns

  • TODO_ITEM_CODE — Derived from FLK.LOOKUP_CODE. The unique code that identifies a checklist to-do item within the OKL_TODO_ITEMS lookup type.
  • TODO_ITEM_MEANING — Derived from FLK.MEANING. The user-facing label or meaning of the to-do item, which is the value most commonly presented on the checklist page.
  • DESCRIPTION — Derived from FLK.DESCRIPTION. Free-text description providing additional context about the to-do item.
  • EFFECTIVE_FROM — Derived from NVL(FLK.START_DATE_ACTIVE, SYSDATE). Lower bound of the item's effective date range; defaults to the current date if no start date is configured.
  • EFFECTIVE_TO — Derived from NVL(FLK.END_DATE_ACTIVE, SYSDATE+3650). Upper bound of the item's effective date range; defaults to ten years past the current date if no end date is configured, effectively treating the item as open-ended.

Note that the view returns all enabled and expired lookup rows for the lookup type; it does not itself apply a SYSDATE filter. Consumers must apply their own date-range predicate when only currently active items are wanted. This is relevant to the search term "todo_item_meaning": the human-readable meaning is exposed through TODO_ITEM_MEANING, not TODO_ITEM_CODE.

Common Use Cases and Queries

The view supports reporting and validation of available funding checklist to-do items. Typical scenarios include BI Publisher reports that list candidate checklist items, custom pages that must validate a selected to-do code, and integration extracts that map legacy checklist values to the current OKL_TODO_ITEMS list.

To list all to-do items regardless of effective date:

SELECT TODO_ITEM_CODE, TODO_ITEM_MEANING, DESCRIPTION
FROM   APPS.OKL_CHECKLIST_TODO_UV
ORDER  BY TODO_ITEM_MEANING;

To restrict the list to items that are active as of the current date:

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_MEANING;

To resolve a meaning back to its code for validation or lookup purposes:

SELECT TODO_ITEM_CODE
FROM   APPS.OKL_CHECKLIST_TODO_UV
WHERE  TODO_ITEM_MEANING = :p_meaning;

Because the underlying lookup type is extensible, customers may add their own to-do items in the OKL_TODO_ITEMS lookup type, and these will appear automatically in the view. Any report or integration that depends on this view therefore reflects both Oracle-seeded and customer-defined checklist items without code changes.