Search Results delete_credit_chklst

Overview

OKL_CREDIT_CHECKLIST_PVT is a private PL/SQL package in the Oracle Lease and Finance Management (OKL) module of Oracle E-Business Suite, declared with AUTHID CURRENT_USER and executed under the privileges of the calling session. Its name, carrying the _PVT suffix and the internal constant G_API_TYPE := '_PVT', identifies it as an implementation-layer package that performs the actual validation and persistence work behind the public TCA/OKC-style API wrappers. Functionally it manages credit checklists and checklist templates: the structured questionnaires used to capture, review, document, and approve a lessee's creditworthiness before a lease or funding request is authorized. The package encapsulates the full lifecycle of a credit checklist record — creation, maintenance, approval, and removal — for both individual transaction-level checklists and reusable funding checklist templates. Two other packages reference it, and because it is classified as PVT, customers and integrators are expected to call the corresponding public APIs or user interfaces rather than invoke it directly.

Key Procedures and Functions

The documented entry points group into three functional clusters:

• Credit checklist maintenance: CREATE_CREDIT_CHKLST, UPDATE_CREDIT_CHKLST, DELETE_CREDIT_CHKLST, and APPROVE_CREDIT_CHKLST. These provide the CRUD and workflow operations for a credit checklist instance, including the specific record-removal routine the user searched for as delete_credit_chklst. DELETE_CREDIT_CHKLST removes a checklist or its associated lines/rules from the underlying credit rules structures.
• Template maintenance: CREATE_FUNDING_CHKLST_TPL, UPDATE_FUNDING_CHKLST_TPL, DELETE_FUNDING_CHKLST_TPL, and APPROVE_FUNDING_CHKLST_TPL. These manage the reusable funding checklist templates from which transaction checklists are instantiated.
• Template header updates: UPDATE_FUND_CHKLST_TPL_HDR refreshes header-level attributes of a funding checklist template.

All procedures follow the standard EBS API convention, returning a status code using the package constants G_RET_STS_SUCCESS, G_RET_STS_ERROR, and G_RET_STS_UNEXP_ERROR, and routing unexpected failures through G_EXCEPTION_UNEXPECTED_ERROR with the message tokens OKL_UNEXPECTED_ERROR, OKL_SQLERRM, and OKL_SQLCODE. Validation failures such as OKL_REQUIRED_VALUE, OKL_LLA_NOT_UNIQUE, OKL_LLA_INVALID_DATE_FORMAT, and OKL_LLA_RANGE_CHECK are raised through the error-handling framework.

Tables Accessed

Access to base tables occurs through APPS synonyms and OKC rule structures:

• OKC_K_HEADERS_B: stores the contract/lease header that anchors each credit checklist; the package reads it to associate checklist records with the correct header and to inherit header context.
• OKC_RULES_B and OKC_RULE_GROUPS_B: hold the rule and rule-group definitions that represent individual checklist questions, answers, and logical groupings. These are the primary targets of create, update, and delete operations.
• PLITBLM: the standard EBS multi-lingual/interfacing table used for column-name and message token handling in the API error framework.

The local record type rulv_rec_type mirrors the OKC_RULES_V column definitions, confirming that checklist rows are manipulated as credit-rule records.

Usage Notes

Because OKL_CREDIT_CHECKLIST_PVT is a private package, it is normally invoked indirectly — from the Oracle Lease Management credit checklist setup and credit request forms, from the public credit checklist APIs that wrap it, or from concurrent programs and custom extensions that call the public layer. Developers searching for "delete_credit_chklst" should note that the package's procedure is named DELETE_CREDIT_CHKLST and that calling it directly bypasses the supported public interface; removal of a checklist should generally be performed through the application UI or the corresponding public API so that validation, error handling, and canonical processing are preserved. The recorded header timestamp (OKLRCLCS.pls 120.1, 2005) indicates a long-stable interface that is compatible with both Oracle EBS 12.1.1 and 12.2.2.