Search Results okl_name_required




Overview
Explore in AI Chat

Overview

OKL_PROCESS_TRX_TYPES_PVT is a private PL/SQL package body in the Oracle E-Business Suite Lease Management (OKL) module, part of the Enterprise Transaction Management (ETRM) product family. It acts as the private implementation layer that participates in the standard Oracle API architecture pattern, where a public (PUB) package exposes the supported interface to callers and a private (PVT) package contains the validation and orchestration logic that supports it.

The package maintains transaction type definitions used by Lease Management contracts. Transaction types drive how contract-related financial events—such as billings, accruals, terminations, and asset transactions—are classified and processed by the lease engine. The body defines three exception variables declared explicitly as documentation of error-handling intent: G_EXCEPTION_UNEXPECTED_ERROR and G_EXCEPTION_ERROR. These, together with the return status constants G_RET_STS_SUCCESS, G_RET_STS_UNEXP_ERROR, and G_RET_STS_ERROR (mapped from OKL_API), form the standard error-handling scaffolding that callers search for when tracing unexpected failures in Lease Management API calls.

Key Procedures and Functions

The package body documents three public-private procedures, each wrapping the corresponding entry point in OKL_TRX_TYPES_PUB:

  • INSERT_TRX_TYPES — Creates a new transaction type record. It initializes the API, starts an activity context through Okl_Api.START_ACTIVITY, and applies local validation. A notable inline check verifies that the transaction type name is populated and not equal to OKC_API.G_MISS_CHAR; when validation fails, it raises the message OKL_NAME_REQUIRED and raises G_EXCEPTION_ERROR. After local validation it delegates the actual insert to the public package.
  • UPDATE_TRX_TYPES — Modifies an existing transaction type definition, following the same initiation, validation, delegation, and exception-propagation pattern as the insert procedure.
  • DELETE_TRX_TYPES — Removes a transaction type record, again wrapping the public procedure with consistent error and message handling.

Across all three procedures the code checks the return status from the delegated call; an unexpected error causes G_EXCEPTION_UNEXPECTED_ERROR to be raised, while a normal API error raises G_EXCEPTION_ERROR. This ensures the caller always receives a meaningful x_return_status, message count, and message data.

Tables Accessed

The documented table referenced through APPS synonyms is PLITBLM. This is the standard Oracle message repository table queried by OKC_API.SET_MESSAGE and the message-handling utilities to populate x_msg_count and x_msg_data when a validation or API error occurs. The transaction type data itself is persisted by the public OKL_TRX_TYPES_PUB procedures; this private body primarily reads message metadata rather than manipulating contract data directly.

Usage Notes

The package is invoked indirectly. Oracle Forms in Lease Management, concurrent programs, and custom extensions call OKL_TRX_TYPES_PUB (or higher-level lease APIs), and the public procedures in turn delegate to this private body. It is referenced by at least two other packages in the ETRM schema, confirming its role as an internal building block.

Developers diagnosing the search term "g_exception_error" should note that this exception is raised in the private layer and propagated outward; the message detail needed to resolve the problem is stored via OKC_API.SET_MESSAGE and retrievable through x_msg_data. Custom code should not call the PVT procedures directly—doing so bypasses the supported public interface and can break upgrade compatibility between 12.1.1 and 12.2.2.