Search Results okl_checklists_uv




Overview
Explore in AI Chat

Overview

OKL_CHECKLISTS_UV is an APPS-owned view in the Oracle E-Business Suite Lease and Finance Management (OKL) module. Its documented purpose is to serve as the user interface view for the credit and funding checklists page, exposing checklist header data in a form suitable for display and for downstream reporting or integration. The view is VALID in both 12.1.1 and 12.2.2. Beyond its UI role, it is a convenient denormalized source because it resolves several lookup codes to their translated meanings within the query itself, which is directly relevant to users searching on the column STATUS_CODE_MEANING.

Because it is a view rather than a table, it holds no data of its own and cannot be written to. Querying it returns the same underlying rows as OKL_CHECKLISTS, filtered and joined to lookup values and to the _ALL synonym for the checklist identifier.

Underlying Base Objects

The documented ETRM metadata lists the referenced base objects as FND_GLOBAL (package), FND_LOOKUPS (view), OKL_CHECKLISTS (synonym), and OKL_CHECKLISTS_ALL (synonym). The view text joins OKL_CHECKLISTS (alias CKL) as the primary source, OKL_CHECKLISTS_ALL (alias CKL2) on CKL.ID = CKL2.CKL_ID with an outer join, and FND_LOOKUPS three times (aliases FLK, FLK2, FLK4) to resolve descriptive meanings for the checklist type, checklist purpose, and status code respectively.

The registered columns include PARENT_CHECKLIST_ID and PARENT_CHECKLIST_NUMBER, which in the view text are sourced from CKL2.CKL_ID and CKL2.CHECKLIST_NUMBER. The join to FND_LOOKUPS is filtered to specific lookup types, and the query restricts CHECKLIST_PURPOSE_CODE to the values CHECKLIST_TEMPLATE and CHECKLIST_TEMPLATE_GROUP, so the view returns template-oriented checklist rows rather than every checklist record.

Key Columns

Common Use Cases and Queries

Typical scenarios include reporting checklist statuses on the credit and funding pages, resolving lookup meanings without re-joining FND_LOOKUPS, and feeding integrations that require human-readable status values.

  • To obtain status meaning alongside the code for credit and funding templates:
SELECT checklist_number,
       checklist_type_meaning,
       status_code,
       status_code_meaning,
       start_date,
       end_date
FROM   apps.okl_checklists_uv
WHERE  checklist_purpose_code IN
       ('CHECKLIST_TEMPLATE','CHECKLIST_TEMPLATE_GROUP');
  • To filter a specific status, query STATUS_CODE_MEANING rather than the raw code, which avoids hard-coding lookup codes. Restrict by ORG_ID for multi-org environments and join ID to operational tables when a checklist must be linked back to its source object.