Search Results g_exception_unexpected_error

Overview

OKL_SETUP_TRXPARAMS_PUB is the public wrapper package for Oracle Lease and Finance Management (OKL) transaction parameter setup within Oracle E-Business Suite. It exposes the transaction parameter setup API to external callers such as Oracle Forms, concurrent programs, and custom integrations, shielding them from the internal private implementation held in OKL_SETUP_TRXPARAMS_PVT. The package operates on the OKL_SIF_TRX_PARMS_V entity, which stores the setup parameters that govern how lease and finance transactions are created and defaulted.

The package follows the standard Oracle Application Object Library (AOL) API architecture. Each public procedure invokes OKL_API.START_ACTIVITY to initialize the API context, validate the API version, and seed the global message stack. The return status from START_ACTIVITY is inspected, and on failure the code raises the standard exceptions G_EXCEPTION_ERROR or G_EXCEPTION_UNEXPECTED_ERROR. This design is the origin of the g_exception_unexpected_error reference, which surfaces when an unexpected (non-business) error occurs during API initialization or execution.

Key Procedures and Functions

• CREATE_TRX_PARM — Public wrapper that creates a new transaction parameter record through the OKL_SIF_TRX_PARMS_V interface. It accepts the standard API parameters (API version, initialization message list flag), a transaction parameter record, and returns the standard return status, message count, message data, and the created record. Internally it delegates to OKL_SETUP_TRXPARAMS_PVT.create_trx_parm.
• UPDATE_TRX_PARM — Updates an existing transaction parameter record, delegating to the corresponding private procedure in OKL_SETUP_TRXPARAMS_PVT.
• DELETE_TRX_PARM — Removes an existing transaction parameter record via the private delete procedure.
• CREATE_TRX_ASSET_PARM — Creates a transaction asset parameter record, associating asset-level setup values with a transaction parameter definition.
• UPDATE_TRX_ASSET_PARM — Updates an existing transaction asset parameter record.

The metadata documents ten procedures or functions in total; the five listed above are the principal public entry points. Each follows the same defensive pattern: initialize activity, trap unexpected and business errors, delegate to the private package, and re-inspect the return status before propagating it to the caller.

Tables Accessed

The documented table accessed via an APPS synonym is PLITBLM, a standard Oracle AOL message table used by the FND message dictionary to resolve message names into translated text. It is referenced indirectly as part of the message-handling infrastructure invoked by OKL_API.START_ACTIVITY and the message retrieval routines. The underlying transaction parameter data itself resides in the OKL_SIF_TRX_PARMS_V view and its base tables, which are manipulated by the private package rather than by this public wrapper.

Usage Notes

This package is typically invoked from Oracle Forms transaction parameter setup windows, from concurrent programs that load or migrate transaction parameter configuration, and from custom PL/SQL integrations that must create, update, or delete transaction parameters programmatically. Callers should always pass a valid p_api_version (the package expects version 1) and should preserve the standard p_init_msg_list, x_return_status, x_msg_count, and x_msg_data parameters to participate correctly in the message stack.

When a caller encounters G_EXCEPTION_UNEXPECTED_ERROR, it indicates an unexpected database or runtime failure rather than a validation failure; the accompanying message stack should be retrieved via FND_MSG_PUB to determine the cause. Because the package is classified as a public (PUB) API and is referenced by one other package, it is a supported integration point, and direct manipulation of the underlying private package should be avoided.