Search Results checklist_template_group




Overview
Explore in AI Chat

Overview

APPS.OKL_CRD_CHECKLISTS_UV is a union-based reporting and integration view within the Oracle E-Business Suite Enterprise Contracts (formerly Oracle Lease and Finance Management / OKL) module. It exposes active checklist header records that function as templates — either standalone checklist templates or checklist template groups — used to drive structured task execution during contract and lease activation workflows. The view applies a fixed filter set so that only current, in-force template definitions are surfaced: the checklist type must be either ACTIVATION or NONE, the end date (or system date when null) must be on or after the current date, the status code must be ACTIVE, the parent checklist identifier (CKL_ID) must be null (confirming the record is a template, not an instance spawned from one), and the checklist purpose code must be CHECKLIST_TEMPLATE or CHECKLIST_TEMPLATE_GROUP. Because of its filtered nature and union structure, the view supports lookups, validation logic, and downstream reporting without requiring callers to re-implement these business rules.

Underlying Base Objects

The view is defined over three documented base objects:

  • OKL_CHECKLISTS — the primary source table for checklist header rows, aliased as CLH in both branches of the union.
  • OKL_CHECKLISTS_ALL — referenced as part of the template-group membership logic (the second branch excludes group headers lacking detail rows via a NOT EXISTS clause).
  • OKL_CHECKLIST_DTLS_ALL — the checklist detail lines table, used in the EXISTS predicate of the first branch to require that a template has at least one detail line before it is exposed.

The two union branches differ only in the checklist type and purpose code combination: the first branch returns ACTIVATION checklists whose purpose code is CHECKLIST_TEMPLATE and which possess at least one detail record; the second returns NONE checklists whose purpose code is CHECKLIST_TEMPLATE_GROUP. Both branches exclude rows that already have a parent CKL_ID.

Key Columns

Common Use Cases and Queries

The view is typically queried to populate LOVs for checklist template selection, to validate that a chosen template is active and in date range, and to report on available template groups. A representative query follows:

SELECT id,
       checklist_number,
       description,
       checklist_type,
       start_date,
       end_date
  FROM apps.okl_crd_checklists_uv
 WHERE checklist_type = 'ACTIVATION'
   AND org_id = :p_org_id
 ORDER BY checklist_number;

To retrieve group-level templates only:

SELECT id, checklist_number, description
  FROM apps.okl_crd_checklists_uv
 WHERE checklist_type = 'NONE';

Because the view already enforces status, date-range, purpose-code, and parent-null conditions, integrators generally should not re-apply these predicates; doing so risks redundant or inconsistent filtering. Joins to OKL_CHECKLIST_DTLS_ALL on ID = CKL_ID are the standard pattern for expanding a selected template into its constituent detail lines.