Search Results is_debug_statement_on

Overview

OKL_AM_LOAN_TRMNT_PVT is a private PL/SQL package body in the Oracle E-Business Suite Lease Management (OKL) module, forming part of the Oracle Lease and Loan Management application. The package encapsulates the core termination logic for loan-type contracts within the Asset Management (AM) subsystem. As a PVT (private) classification package, it is intended for internal consumption by other APIs, packages, and concurrent processing logic rather than direct invocation by end users. The package header (OKLRLOTB.pls, version 120.6) reflects a modification date of December 2007, placing it within the code base that spans both EBS 12.1.1 and 12.2.2 releases. The package relies on the FND_LOG facility for diagnostic logging, declaring standard constants such as G_LEVEL_PROCEDURE, G_LEVEL_EXCEPTION, and G_LEVEL_STATEMENT, along with a module name prefix of 'okl.am.plsql.okl_am_loan_trmnt_pvt.' for trace identification. The presence of a constant such as G_LEVEL_STATEMENT is directly relevant to the "is_debug_statement_on" search that led to this documentation, since that construct governs whether statement-level debug messages are emitted during execution.

Key Procedures and Functions

The package body exposes two documented procedures:

• VALIDATE_LOAN — Validates the loan contract prior to termination. According to its header comments, it performs loan-specific validation and defers the majority of checks to the validate_contract routine located in OKL_AM_LEASE_LOAN_TRMNT_PVT. The procedure accepts a term record structure (term_rec_type) and returns standard API status and message parameters. In its current form the implementation initializes the return status to success and contains no additional logic, indicating validations are handled downstream.
• LOAN_TERMINATION — The main API responsible for executing loan termination. Its documentation emphasizes that the entire process is rolled back if a processing transaction fails, preserving information about the success or failure of constituent APIs. A rolled-back process is subsequently re-picked by the batch_process mechanism. The procedure's history log records several corrections, including a change from OR to AND in the transaction-exists check, removal of Process_Close_Streams (relocated to update_k_hdr_and_lines), and the addition of code to get and set TMG_RUN on OKL_TRX_MS.

Tables Accessed

The documented metadata lists DUAL as the sole referenced table via APPS synonyms. DUAL is the standard Oracle dummy table used for singleton SELECT statements and expression evaluation, and its presence here indicates lightweight internal queries rather than direct DML against business entities within the documented scope. The procedure history references OKL_TRX_MS for TMG_RUN retrieval and update, and OKL_TRX_MS-related processing, though the canonical metadata aligns references primarily through helper routines and upstream APIs.

Usage Notes

OKL_AM_LOAN_TRMNT_PVT is referenced by one other package, consistent with its private API classification. It is typically invoked through lease and loan termination flows, likely originating from OKL_AM_LEASE_LOAN_TRMNT_PVT, termination forms, or batch processing programs that handle contract terminations. Because the package uses FND_LOG-based debugging, administrators and developers diagnosing termination issues can enable statement-level logging through the standard FND profile options that control the "is_debug_statement_on" behavior, allowing the G_LEVEL_STATEMENT constant to drive trace output. Custom code should not call this package directly; instead, the public lease/loan termination APIs should be used to preserve transaction integrity and rollback semantics.