Search Results g_commit

Overview

OKL_BLK_AST_UPD_PUB is a public PL/SQL package in the Oracle E-Business Suite (EBS) applications schema (APPS) that belongs to the Oracle Lease and Finance Management (OKL) module. Its primary business function is to provide a published, reusable API for updating the location information associated with leased assets. In the leasing lifecycle, asset location data frequently changes as equipment is relocated, returned, or redeployed. This package exposes a controlled, business-rule–compliant interface for maintaining that location data rather than allowing direct table manipulation.

The package is classified as a PUB (public) API, meaning its procedures are intended for invocation by external callers, including other packages, forms, concurrent programs, and custom code. The header comment ($Header: OKLPBAUS.pls 120.1 ...) and the OKL naming convention confirm it as a standard Oracle-delivered interface for the Lease Management application.

Key Procedures and Functions

The documented interface exposes a single logical operation, UPDATE_LOCATION, implemented through two overloaded procedure signatures. Both share the same underlying business purpose — updating asset location records — but differ in whether they process a single record or a collection of records.

• UPDATE_LOCATION (single-record overload) — Accepts a single location record parameter (p_loc_rec) of type blk_rec_type, along with the standard API control parameters (p_api_version, p_init_msg_list). It returns the standard OUT parameters x_return_status, x_msg_count, and x_msg_data. This overload is used when a caller needs to update one location at a time.
• UPDATE_LOCATION (table/collection overload) — Accepts a collection parameter (p_loc_tbl) of type blk_tbl_type, enabling bulk updates of multiple location records in a single call. It uses the same API control and OUT parameters as the single-record version.

The subtype declarations blk_rec_type and blk_tbl_type are anchored to the private package okl_blk_ast_upd_pvt, indicating that the record and table structures are defined in the corresponding private implementation package, keeping the public package as a thin wrapper.

Tables Accessed

The provided ETRM metadata does not enumerate specific tables referenced through APPS synonyms. Based on the OKL schema and the procedure name, the package logically operates against the OKL asset/location tables (for example, the location history or asset location detail tables within the OKL data model). Updates are channeled through the private implementation package okl_blk_ast_upd_pvt, which performs the actual DML against the underlying tables. The metadata does confirm that the package is referenced by one other package, reflecting its role as a dependent API within the OKL call graph.

Usage Notes

This API is typically invoked from Lease Management forms, other OKL public APIs, or custom extensions when asset location information must be changed through supported business logic rather than direct SQL. Because it is a public API, callers should respect standard Oracle API conventions: pass a valid p_api_version, honor the p_init_msg_list flag, and always inspect x_return_status and the message stack before proceeding.

Regarding the search term g_commit: the package specification declares the global constant G_COMMIT CONSTANT VARCHAR2(1) := FND_API.G_TRUE. This constant signals that the API is designed to perform a database commit internally upon success, rather than leaving transaction control to the caller. Callers should therefore not wrap these API calls within an outer transaction expecting to roll back, and they should be aware that a successful call may already have committed changes to the asset location data.