Search Results okl_yes_no




Overview
Explore in AI Chat

Overview

OKL_INSTANCE_CHECKLIST_DTL_UV is an APPS-owned database view within the Oracle Lease and Finance Management (OKL) product family. It presents funding checklist instance details — the individual checklist line items attached to a lease or funding transaction, together with their validation outcomes and descriptive lookups. The "UV" suffix follows the Oracle E-Business Suite convention for a user-facing validation view, indicating that the object is intended for direct query by forms, concurrent programs, and reporting tools rather than being a private implementation detail.

The view's principal role is to translate the raw code values stored on checklist detail records into human-readable meanings. It resolves TODO_ITEM_CODE, mandatory and completion flags, validation statuses, and checklist types against FND_LOOKUPS, so that downstream consumers receive fully decoded rows without needing to join lookups themselves. The object is classified as VALID and is present in both Oracle EBS 12.1.1 and 12.2.2, making it a stable reference point across release upgrades.

Underlying Base Objects

The view is defined over the following documented base objects:

  • OKL_CHECKLIST_DETAILS (synonym) — the driving table, aliased CLD. It supplies the checklist line identity, checklist header reference, TODO item code, flags, validation results and messages, descriptive flexfield attributes, and the standard WHO columns. It is the table that actually stores the checklist instance data against a funding transaction.
  • FND_LOOKUPS (view) — joined six times under the aliases FLK, FLK2, FLK3, FLK4, FLK6 and FLK7 to decode lookup codes from the OKL_TODO_ITEMS, OKL_YES_NO and related lookup types into meanings and descriptions.
  • OKL_DATA_SRC_FNCTNS_B (synonym) — aliased FUN, providing the function name and source for the validation function referenced on the detail row.
  • FND_GLOBAL (package) — the standard EBS context package underlying org and user security behavior in OKL views.

All base tables are referenced through APPS synonyms, so querying the view requires no fully qualified schema prefix. Outer joins are implemented with NVL defaults rather than explicit (+) syntax for the flag columns, so a missing flag is presented as 'N' and a missing validation result as 'UNDETERMINED'.

Key Columns

Common Use Cases and Queries

The view is typically queried to report funding checklist status per transaction, to identify incomplete mandatory items before funding release, and to inspect validation failures. A representative query follows:

  • SELECT ckl_id, todo_item_meaning, mandatory_flag_meaning, user_complete_flag_meaning, function_validate_rsts, function_validate_msg FROM okl_instance_checklist_dtl_uv WHERE ckl_id = :p_ckl_id ORDER BY id;
  • SELECT ckl_id, COUNT(*) FROM okl_instance_checklist_dtl_uv WHERE mandatory_flag = 'Y' AND user_complete_flag = 'N' GROUP BY ckl_id;
  • SELECT todo_item_meaning, function_validate_rsts, function_validate_msg FROM okl_instance_checklist_dtl_uv WHERE function_validate_rsts = 'FAILED';

Because the user searched for okl_yes_no, it is worth noting that this lookup type underpins the MANDATORY_FLAG and USER_COMPLETE_FLAG decodes; the FK numbers FLK2 and FLK3 reference OKL_YES_NO, while FLK6 provides the completion meaning used inside CHECKIST_RESULTS. Integrations that extract checklist data should filter on ORG_ID and use OBJECT_VERSION_NUMBER when writing back.