Search Results func_val_rsts_meaning




Overview
Explore in AI Chat

Overview

The OKL_FUNDING_CHECKLISTS_UV view is a user interface (UI) view in the Oracle E-Business Suite OKL – Lease and Finance Management module. It belongs to the APPS schema and holds a status of VALID in both Oracle EBS 12.1.1 and 12.2.2. The view presents the lease funding checklist — the set of to-do items, validation rules, and administrative notes that must be addressed before a lease funding request can be approved and disbursed. Because it is a "UV" (User View) object, it is designed specifically as a presentation-layer query rather than as a normalized data store; the OA Framework or Forms-based UI layers query it directly to render the funding checklist pages for the lease funding request workflow.

The view does not store data itself. Instead, it denormalizes funding-checklist rule rows held in OKC_RULES_B and enriches them with human-readable lookup meanings, status descriptions, profile-option values, and registered data-source function metadata. This design means a single query returns everything needed to render a checklist row: the to-do item code and its meaning, whether the item is mandatory, whether it has been checked off, the validation result and message, the owning function, and the checklist type.

Underlying Base Objects

The view is defined over the following documented base objects:

  • OKC_RULES_B (synonym) — the primary driver table. Checklist rows are stored here under the rule information category LAFCLD, which identifies Lease and Finance checklist data. Positional columns RULE_INFORMATION1 through RULE_INFORMATION10 carry the checklist attributes.
  • FND_LOOKUPS (view) — joined six times (aliases LK1–LK6) to translate coded values into display meanings for to-do items, yes/no flags, validation results, checklist types, and check-off results.
  • OKC_STATUSES_V (view) — supplies the status code description joined on the rule's status value (defaulting to NEW).
  • OKL_DATA_SRC_FNCTNS_B (synonym) — provides the registered data-source function NAME and SOURCE for the function that validates the checklist item.
  • FND_PROFILE (package) — used via FND_PROFILE.VALUE('OKL_FUNDING_REQUEST_APPROVER') to expose the APPROVERYN column.
  • FND_GLOBAL (package) — referenced for session/user context (e.g., USER_ID, RESP_ID), though not shown explicitly in the excerpt.

Key Columns

Common Use Cases and Queries

The view is queried when displaying or diagnosing funding checklist behavior for a specific funding request, and when investigating validation messages produced by checklist functions.

SELECT fund_req_id, todo_item_code, todo_item_meaning,
       mandatory_flag_meaning, status_meaning,
       function_name, function_validate_rsts, function_validate_msg
FROM   apps.okl_funding_checklists_uv
WHERE  fund_req_id = :p_fund_req_id
AND    check_off = 'N'
ORDER BY mandatory_flag DESC, todo_item_code;

To isolate rows whose validating function returned a message (the typical goal when searching for function_validate_msg):

SELECT fund_req_id, todo_item_code, function_name,
       function_validate_rsts, function_validate_msg
FROM   apps.okl_funding_checklists_uv
WHERE  function_validate_msg IS NOT NULL;

Because the view joins lookup values and profile options, it is also useful for reporting on completed vs. outstanding checklist items per funding request, or for auditing which data-source function governs each to-do item.