Search Results okl_crd_checklists_uv




Overview
Explore in AI Chat

Overview

OKL_CRD_CHECKLISTS_UV is a user interface (UI) view owned by the APPS schema in Oracle E-Business Suite, belonging to the OKL - Lease and Finance Management product (Oracle Lease Management). Its documented purpose is to serve as the source for the credit checklist List of Values (LOV) presented on the credit origination and credit review user interface. Rather than exposing the full set of checklists that may exist in the underlying checklist tables, the view applies a defined set of business filters that restrict the query result to the subset of checklist template records that are meaningful for credit processing.

The view is defined as a UNION ALL of two result sets drawn from the OKL_CHECKLISTS table, differing only in the CHECKLIST_TYPE predicate. Because it is a simple, non-current-accounting view over checklists (not a balances or transactions view), it does not aggregate or summarize amounts; it exposes descriptive and control attributes only. It is intended primarily for LOV lookup and UI binding rather than for financial reporting, though it can be used in integration and validation queries to confirm which checklist templates are currently selectable for credit processing on a given date.

Underlying Base Objects

The view is defined over OKL_CHECKLISTS (exposed through the OKL_CHECKLISTS and OKL_CHECKLISTS_ALL synonyms in the APPS layer) with a correlated EXISTS subquery against OKL_CHECKLIST_DTLS_ALL. Two distinct row sources are combined:

  • The first branch selects checklists where CHECKLIST_TYPE = 'ACTIVATION', CHECKLIST_PURPOSE_CODE = 'CHECKLIST_TEMPLATE', CKL_ID IS NULL (indicating a top-level template rather than a child checklist), STATUS_CODE = 'ACTIVE', and an effective end date (or the current system date when END_DATE is null) on or after the current date. It further requires that at least one detail row exists in OKL_CHECKLIST_DTLS_ALL, ensuring the template is not empty.
  • The second branch selects checklists where CHECKLIST_TYPE = 'NONE' that are also active and within their effective date range.

Rows from the two branches are returned as a single result set via UNION ALL, with no de-duplication. All date comparisons are performed with TRUNC on both the stored date and SYSDATE, which makes the view date-sensitive: a template whose END_DATE has passed will silently disappear from the LOV.

Key Columns

All columns of OKL_CHECKLISTS are projected without transformation, including the standard EBS who-columns and descriptive flexfield attributes. The most operationally significant columns include:

Common Use Cases and Queries

The primary use case is the credit checklist LOV on the lease credit origination and credit review screens: the form binds to this view and lets the user pick an eligible checklist template. Related uses include validation queries confirming whether a given template is currently selectable, and integration extracts that need the same filtered set of templates.

  • Listing all currently selectable credit checklist templates: SELECT id, checklist_number, description FROM okl_crd_checklists_uv ORDER BY checklist_number;
  • Confirming that a specific template is active and within its effective dates: SELECT id, status_code, start_date, end_date FROM okl_crd_checklists_uv WHERE checklist_number = :p_number;
  • Filtering by type to isolate activation versus unrestricted templates: SELECT id, checklist_number FROM okl_crd_checklists_uv WHERE checklist_type = 'ACTIVATION';
  • Joining to the detail table to count expected checklist lines for a selected template: SELECT u.id, u.checklist_number, COUNT(d.id) FROM okl_crd_checklists_uv u JOIN okl_checklist_dtls_all d ON d.ckl_id = u.id GROUP BY u.id, u.checklist_number;

Because the view enforces status, date, purpose, and detail-existence criteria, queries against it automatically exclude inactive, expired, and empty templates, which makes it a reliable filter for both UI LOV behavior and programmatic validation.