Search Results validate_source_id

Overview

OKL_ECH_PVT is a private (PVT-classified) PL/SQL package that forms part of the Oracle Lease and Finance Management (OKL) application programming interface layer within Oracle E-Business Suite. The package body carries a header revision of 120.1 dated 2005/10/30, indicating it is a long-standing component of the OKL infrastructure that has been carried forward through release 12.1.1 and 12.2.2. Its principal business function is to provide the low-level data manipulation and concurrency handling for the OKL_FE_CRITERIA_SET entity, which stores criteria set definitions used in contract and lease origination and evaluation logic. As a "PVT" package, it is not intended for direct customer invocation; rather, it is consumed internally by other OKL packages that require controlled insert, update, delete, and row-lock operations against the criteria set table while preserving the object version number used for optimistic locking.

The package defines a standard set of API constants drawn from OKL_API, including success, error, and unexpected-error return statuses, the OKL_DB_ERROR token, and the missing-value sentinels g_miss_char, g_miss_num, and g_miss_date. These constants ensure that callers receive consistent return codes and that unset attributes are propagated uniformly across the OKL API stack.

Key Procedures and Functions

• API_COPY — A stub procedure for copying API records. Its body contains only a NULL statement, meaning it acts as a placeholder. The effect on the context of the user's search for "validate_source_id" is that API_COPY does not validate a source identifier; no source-id validation logic is implemented here.
• CHANGE_VERSION — Also a NULL-bodied stub. It is reserved for version-change semantics but performs no operation, so it cannot be relied upon to validate or mutate a source id.
• LOCK_ROW — The only procedure in the excerpt with substantive code. It accepts a record of type OKL_ECH_REC along with the standard initialization message list and return-status output parameters. It opens a locking cursor against OKL_FE_CRITERIA_SET, selecting OBJECT_VERSION_NUMBER for the matching CRITERIA_SET_ID and OBJECT_VERSION_NUMBER using FOR UPDATE OF OBJECT_VERSION_NUMBER NOWAIT. A second cursor, LCHK_CSR, is declared for existence checking. The e_resource_busy exception (ORA-00054) is initialized so that a concurrent lock attempt is surfaced as a friendly error rather than an unhandled database error.
• INSERT_ROW, UPDATE_ROW, DELETE_ROW — Documented procedures that provide the standard DML operations against the criteria set table, following the OKL API conventions for message-list initialization and return-status reporting.

Note that no procedure named for source-id validation appears in the documented procedure list. A search for "validate_source_id" within this package body would not resolve to a named procedure or function; the package simply does not expose that operation.

Tables Accessed

• OKL_FE_CRITERIA_SET — The primary subject table. It is read (via LOCK_ROW's cursors) to verify existence and object-version consistency, and it is the target of the INSERT_ROW, UPDATE_ROW, and DELETE_ROW procedures. The OBJECT_VERSION_NUMBER column is the optimistic-locking column.
• PLITBLM — Accessed through an APPS synonym. This is the standard Oracle EBS message-handling table used by the message-list API to store and retrieve error and warning messages accumulated during API execution.

Usage Notes

OKL_ECH_PVT is referenced by 15 other packages, which is consistent with its role as a shared private utility for criteria set persistence. It is not designed for direct invocation from Oracle Forms or concurrent programs; instead, it is called by higher-level OKL public APIs and internal packages that need to lock, insert, update, or delete criteria set rows while maintaining object-version integrity. Custom code that attempts to call OKL_ECH_PVT directly should treat it as an unstable private interface and should instead use the associated public API layer. Regarding the user's search term "validate_source_id": this package contains no such validation procedure. Source-identifier validation, if it exists in the OKL module, would reside elsewhere — possibly in a criteria evaluation package or a public API that delegates to OKL_ECH_PVT for the actual row operations. The presence of only stub implementations for API_COPY and CHANGE_VERSION further limits the routine's surface area to DML and locking on OKL_FE_CRITERIA_SET.