Results for “okl_fund_checklists_uv”

AI-generated from documented ETRM metadata — verify critical details on the linked pages.

Overview

The view APPS.OKL_FUND_CHECKLISTS_UV is a user interface (UI) view within the Oracle Lease and Finance Management (OKL) module. Its documented purpose is to serve as the List of Values (LOV) source for funding checklists, enabling end users to select a valid funding checklist template when creating or managing funding-related transactions. The "_UV" suffix indicates a "User View," signifying that the object is intended for direct consumption by the application's user interface layer rather than for background processing or internal APIs.

In Oracle EBS 12.1.1 and 12.2.2, LOV views such as this one encapsulate the business rules that determine which records are eligible for selection. Rather than exposing an entire base table, the view applies filtering predicates so that only active, current, and correctly typed checklist templates appear to the user. This reduces the risk of invalid data entry and enforces referential and business consistency at the presentation layer.

Underlying Base Objects

The view is defined over the following documented base objects, all owned by the APPS schema and exposed through synonyms:

• OKL_CHECKLISTS — the primary checklist header table (aliased as CLH in both UNION ALL branches), supplying the majority of columns.
• OKL_CHECKLISTS_ALL — the multi-organization variant of the checklist header, referenced in the metadata as a dependent object.
• OKL_CHECKLIST_DTLS_ALL — the checklist detail (line) table, referenced via an EXISTS subquery (aliased as CLD) to ensure the template has at least one detail record.

The view is implemented as a UNION ALL of two nearly identical SELECT statements against OKL_CHECKLISTS. The first branch returns rows where CHECKLIST_TYPE = 'FUNDING', and the second branch returns rows where CHECKLIST_TYPE = 'NONE'. Both branches apply the same additional filters: the row must be currently in effect (TRUNC(NVL(END_DATE, SYSDATE)) >= TRUNC(SYSDATE)), carry a status of 'ACTIVE', represent a template rather than an instance (CKL_ID IS NULL and CHECKLIST_PURPOSE_CODE = 'CHECKLIST_TEMPLATE'), and have at least one matching detail record in OKL_CHECKLIST_DTLS_ALL.

Key Columns

The view projects the full standard column set of the checklist header, including:

• ID, OBJECT_VERSION_NUMBER — primary key and optimistic locking column.
• CHECKLIST_NUMBER, DESCRIPTION, SHORT_DESCRIPTION — identifiers and descriptive text presented in the LOV.
• CHECKLIST_TYPE — the discriminator driving the UNION ALL ('FUNDING' or 'NONE').
• START_DATE, END_DATE — effective dating; END_DATE drives the currency filter.
• STATUS_CODE — constrained to 'ACTIVE' by the view definition.
• ATTRIBUTE_CATEGORY and ATTRIBUTE1–15 — the standard DFF (Descriptive Flexfield) columns for extensible attributes.
• ORG_ID — the operating unit context, relevant for multi-org security.
• Audit columns — CREATED_BY, CREATION_DATE, LAST_UPDATED_BY, LAST_UPDATE_DATE, LAST_UPDATE_LOGIN, plus concurrent program columns (REQUEST_ID, PROGRAM_APPLICATION_ID, PROGRAM_ID, PROGRAM_UPDATE_DATE).

Common Use Cases and Queries

The principal use case is populating a funding checklist LOV, which maps to the search term checklist_template_group. The view surfaces only activatable templates grouped by type, allowing the UI to present valid funding checklist groups to the user. The following query retrieves all selectable templates:

SELECT id,
       checklist_number,
       description,
       checklist_type,
       start_date,
       end_date
  FROM apps.okl_fund_checklists_uv
 ORDER BY checklist_number;

To filter for funding templates with a defined end date:

SELECT checklist_number, description
  FROM apps.okl_fund_checklists_uv
 WHERE checklist_type = 'FUNDING'
   AND end_date IS NOT NULL;

When diagnosing why an expected template does not appear in the LOV, the underlying predicates should be validated against OKL_CHECKLISTS — specifically that the row is ACTIVE, its purpose code is CHECKLIST_TEMPLATE, its parent key (CKL_ID) is null, and that detail rows exist in OKL_CHECKLIST_DTLS_ALL. Because the view is a LOV-only construct, it is not intended for transactional updates; any modification to checklist templates must be performed against the base tables through the supported Oracle Lease and Finance Management application forms.