Search Results okl_debug_level

Overview

OKL_CURE_WF is a PL/SQL package owned by the APPS schema in Oracle E-Business Oracle Lease Management (OKL). Its name reflects its role as the workflow integration layer for the "cure" process — the set of corrective actions a lessor must undertake when a lease contract falls into delinquency or default. When cure reports are submitted and reviewed, the workflow must move the associated activity through approval or rejection, and the results must be written back against the cure report record. OKL_CURE_WF encapsulates that orchestration logic so that Oracle Workflow function activities can call a stable, package-based API rather than embedding business rules directly in workflow definitions.

The package is declared with AUTHID CURRENT_USER, so its unqualified references resolve against the privileges of the calling session, and it depends on OKC_API constants and message conventions for error handling and API versioning. It is referenced by one other package in the ETRM schema, indicating a narrow, well-contained dependency footprint. The header comments date the source to 2003, and the object remains shipped under the 12.1.1 and 12.2.2 code lines.

Key Procedures and Functions

• APPROVE_CURE_REPORTS — The primary programmatic entry point. It follows the standard EBS API pattern, exposing API version, initialization of the message list, a commit flag, and an input report identifier, with standard return status, message count, and message data outputs. It applies the approval outcome to the specified cure report.
• SET_APPROVAL_STATUS — A workflow-callback procedure with the canonical Workflow signature (itemtype, itemkey, actid, funcmode, result). It is invoked by an approval activity to mark the cure report as approved and set the activity result.
• SET_REJECT_STATUS — The counterpart callback for a rejection activity, using the same Workflow signature. It records the rejection outcome and returns the appropriate result to the workflow engine.

The two status procedures are the flexible-routing hooks that allow a single cure workflow to branch cleanly on the reviewer's decision.

Tables Accessed

• OKL_CURE_REPORTS — The principal business table; the package updates the cure report record with its approval or rejection status. This is the core write performed by the package.
• FND_USER — Used to resolve the acting user, most likely to stamp the approval or rejection with the responsible person and to support message personalization.
• FND_NEW_MESSAGES — Referenced for Oracle Alert or notification-style messaging related to the cure decision.
• OKL_WF_ITEM_S — The workflow item store, read to resolve item type, item key, and activity context within the callbacks.
• WF_PARAMETER_LIST_T — The Workflow parameter list type, used to read activity attributes passed from the workflow definition.
• PLITBLM — The standard EBS message-list table used to accumulate and return API messages.
• DUAL — Used for scalar evaluation, including profile-option lookups.

Usage Notes

OKL_CURE_WF is not ordinarily invoked from an Oracle Forms window directly. Its documented consumers are Oracle Workflow function activities that drive cure report approval and rejection, plus the one dependent package noted in the metadata, which likely calls APPROVE_CURE_REPORTS to process a batch or programmatic approval. Customizations that need to approve cure reports outside the standard workflow should call APPROVE_CURE_REPORTS rather than updating OKL_CURE_REPORTS directly, so that messages and status semantics remain consistent.

The package declares a debug-level global initialized from the FND profile option OKL_DEBUG_LEVEL, defaulting to 20 when the profile is unset. This is the only diagnostic control present, and it corresponds directly to the search term okl_debug_level: raising the profile value increases logging verbosity during workflow callbacks and API calls, which is the standard technique for troubleshooting cure workflow routing. Confirm the profile is set at the correct level and site before enabling higher verbosity, since debug output in a workflow context can be extensive.