Search Results function_validate_msg




Overview

OKL_CREDIT_CHECKLISTS_UV is an APPS-owned database view in the Oracle E-Business Suite Lease and Finance Management (OKL) module. It serves as the user-interface view for the lease credit line checklist, presenting configuration rows stored generically in the OKC rules engine in a fully decoded, presentation-ready format. The view filters the underlying rules table to rows whose RULE_INFORMATION_CATEGORY equals 'LACCLD', decodes each of the ten RULE_INFORMATION attributes through FND_LOOKUPS, and enriches them with function and status information. Because of this layered decoding, it is the standard source for both OA Framework UI pages and custom reporting or integration queries that need to display checklist items, their mandatory flags, results, and associated validation functions in human-readable form.

Underlying Base Objects

The view is defined over a join of several documented base objects:

  • OKC_RULES_B (referenced via synonym RULT) — the rules engine table holding the raw checklist definition rows in category 'LACCLD'. Each RULE_INFORMATIONn column stores a coded value.
  • FND_LOOKUPS (referenced six times as LK1 through LK6) — supplies the meaning text for each coded attribute, using lookup types OKL_TODO_ITEMS, YES_NO, OKL_FUN_VALIDATE_RSTS, OKL_CHECKLIST_TYPE, and OKL_VALIDATE_RESULTS.
  • OKC_STATUSES_V (STATUS) — resolves the checklist status code into its meaning.
  • OKL_DATA_SRC_FNCTNS_B (FUN) — provides the function name and source for the client-side validation function referenced by the checklist item.
  • FND_PROFILE (package) — retrieves the OKL_CREDIT_LINE_APPROVER profile option to produce the APPROVERYN column.
  • FND_GLOBAL (package) — included among documented dependencies to supply runtime context (user, responsibility, application) during view access.

The view therefore does not store data; it is a pure projection and decoding layer over rules-engine metadata.

Key Columns

Common Use Cases and Queries

The view supports reporting on checklist configuration and completion, troubleshooting validation outcomes, and integration with external approval systems.

  • List all checklist items for a contract: SELECT todo_item_code, todo_item_meaning, mandatory_flag_meaning, status_meaning FROM okl_credit_checklists_uv WHERE rgp_id = :p_rgp_id;
  • Identify mandatory items not yet checked off: SELECT id, todo_item_code FROM okl_credit_checklists_uv WHERE mandatory_flag = 'Y' AND check_off = 'N';
  • Inspect validation function outcomes: SELECT todo_item_code, function_validate_rsts, func_val_rsts_meaning, function_name FROM okl_credit_checklists_uv WHERE function_validate_rsts = 'FAILED';
  • Report by checklist type: SELECT checklist_type_meaning, COUNT(*) FROM okl_credit_checklists_uv GROUP BY checklist_type_meaning;

Because the view performs the lookup joins and DECODE logic, custom reports should query it directly rather than re-deriving meanings from OKC_RULES_B, ensuring consistency with the standard lease credit line UI pages.