Search Results checkist_results




Overview
Explore in AI Chat

Overview

APPS.OKL_FUNDING_CHECKLISTS_UV is a supplementary view in the Oracle E-Business Suite Lease and Finance Management (OKL/ETRM) module. It presents funding checklist data—the enumerated to-do items, validation outcomes, and approval states that must be satisfied before a lease or loan contract can be funded. The view is classified as a "supplementary view used to simplify forms coding," meaning it is intended primarily as a forms-layer convenience object rather than as a public reporting interface. Oracle explicitly warns that querying or altering data through this view is not recommended because its definition may change dramatically across minor or major releases.

In the 12.1.1 and 12.2.2 releases the object remains VALID under the APPS schema and is registered in FND Design Data as OKL.OKL_FUNDING_CHECKLISTS_UV. The view joins checklist rows to lookup meanings and status descriptions, so downstream consumers receive decoded values alongside raw codes. The final column, CHECKIST_RESULTS (note the Oracle-preserved misspelling), carries the checklist outcome flag and is frequently the column users search for, often as "checkist_results".

Underlying Base Objects

The documented dependencies for OKL_FUNDING_CHECKLISTS_UV are:

The view therefore does not persist data; it is a read-only projection over rule, status, lookup, and function metadata entities that together describe checklist execution against a contract header (KHR_ID) and funding request (FUND_REQ_ID).

Key Columns

  • ID – Unique identifier for the funding checklist line.
  • RGP_ID / KHR_ID – Foreign keys to the rule group and contract header respectively, providing the context in which the checklist item applies.
  • FUND_REQ_ID – Identifier of the funding request the checklist governs.
  • TODO_ITEM_CODE / TODO_ITEM_MEANING – The checklist action and its decoded description.
  • MANDATORY_FLAG / _MEANING – Indicates whether the item must be completed before funding.
  • CHECK_OFF / _MEANING / CHECK_OFF_RESULTS – Completion indicator, decoded value, and any result returned by the check.
  • STATUS / STATUS_MEANING – Workflow or rule status derived from OKC_STATUSES_V.
  • APPROVERYN – Approval flag used to drive authorization routing.
  • FUNCTION_* and FUNCTION_VALIDATE_* – Validation function identity, source, and its outcome and message.
  • CHECKLIST_TYPE / _MEANING – Classification of the checklist (for example, funding versus delivery).
  • CHECKIST_RESULTS – The aggregated or per-item checklist result flag; retain the spelling exactly as documented.
  • NOTE / ADMIN_NOTE – User and administrative annotations.

Common Use Cases and Queries

Typical scenarios include verifying outstanding funding prerequisites for a contract, auditing failed validation functions, and driving custom funding dashboards. Because the view is marked non-recommended for direct access, production integrations should prefer the underlying OKC tables or supported APIs; the view remains valuable for ad hoc diagnostics and forms-style reporting.

Sample query returning unresolved mandatory items for a contract:

  • SELECT ID, TODO_ITEM_MEANING, MANDATORY_FLAG_MEANING, CHECK_OFF_MEANING, STATUS_MEANING, CHECKIST_RESULTS FROM APPS.OKL_FUNDING_CHECKLISTS_UV WHERE KHR_ID = :p_khr_id AND MANDATORY_FLAG = 'Y' AND NVL(CHECK_OFF,'N') = 'N';
  • SELECT FUNCTION_NAME, FUNCTION_VALIDATE_RSTS, FUNCTION_VALIDATE_MSG FROM APPS.OKL_FUNDING_CHECKLISTS_UV WHERE FUNCTION_VALIDATE_RSTS IS NOT NULL ORDER BY KHR_ID, ID;
  • SELECT CHECKLIST_TYPE_MEANING, CHECKIST_RESULTS, COUNT(*) FROM APPS.OKL_FUNDING_CHECKLISTS_UV GROUP BY CHECKLIST_TYPE_MEANING, CHECKIST_RESULTS;