Results for “okl_txd_assets_pub”

50+ results




AI-generated from documented ETRM metadata — verify critical details on the linked pages.

Overview

OKL_TXD_ASSETS_PUB is a public PL/SQL package in the Oracle E-Business Suite (EBS) Applications (APPS) schema that provides the externally callable API layer for Oracle Lease and Finance Management (OKL) tax depreciation asset definitions. It belongs to the OKL_TXD (tax depreciation) product family and follows the standard EBS "PUB/PVT" pattern, where a public package exposes a stable, documented interface while delegating business logic and data manipulation to a private companion package (OKL_TXD_ASSETS_PVT).

The package is declared AUTHID CURRENT_USER, meaning it executes with the privileges of the calling user rather than the package owner, consistent with standard EBS API security conventions. Its declared constants and global variables (such as G_PKG_NAME, G_EXCEPTION_HALT_VALIDATION, and the OKC_API tokens used for message token substitution) confirm that the package participates in the common EBS API framework, propagating return status, message count, and message data through the OKC_API message stack. The dependency on OKC_API and the adpv_rec_type/adpv_tbl_type subtypes borrowed from OKL_TXD_ASSETS_PVT indicate the package supports both single-record and bulk (table-based) processing.

Key Procedures and Functions

The ETRM documentation records five public procedures within this package, with parameter lists defined in the source excerpt only for some.

  • CREATE_TXD_ASSET_DEF — Creates one or more tax depreciation asset definition records. Two overloaded signatures are documented: a single-record version accepting an adpv_rec input and returning the created record, and a bulk version accepting an adpv_tbl input and returning a corresponding output table.
  • UPDATE_TXD_ASSET_DEF — Modifies existing tax depreciation asset definition records, again offered in single-record and bulk overloaded forms.
  • DELETE_TXD_ASSET_DEF — Removes tax depreciation asset definition records maintained through this API.
  • LOCK_TXD_ASSET_DEF — Acquires a lock on a tax depreciation asset definition record. This is the procedure the user searched for under the term "lock_txd_asset_def". It exists to serialize concurrent access to the asset definition, ensuring that a record cannot be modified by another session while the current caller holds the lock. Typical usage is at the start of a transactional flow preceding an update or delete.
  • VALIDATE_TXD_ASSET_DEF — Performs validation of the supplied asset definition data without committing changes, allowing callers to check data integrity and business rules before invoking create or update.

All procedures follow the conventional EBS API signature pattern, returning x_return_status, x_msg_count, and x_msg_data.

Tables Accessed

The ETRM metadata lists a single referenced table via APPS synonyms: PLITBLM. The bulk-handling overloads and the record/table subtype definitions are consistent with the package inserting, updating, and deleting tax depreciation asset definition rows through its private package counterpart. Direct table access is encapsulated in OKL_TXD_ASSETS_PVT; the public package itself is a thin interface layer, which explains the limited table footprint documented at the public level.

Usage Notes

OKL_TXD_ASSETS_PUB is typically invoked from Oracle Forms within the Lease and Finance Management application, from concurrent programs that process tax depreciation in batch, and from custom code extending the OKL application. Because it is classified as a PUB API and is referenced by 18 other packages, it should be treated as a supported integration point; direct DML against underlying tax depreciation tables should be avoided.

Callers should initialize the message list, check x_return_status against the standard OKC_API constants, and drain messages through the OKC_API message stack. The LOCK_TXD_ASSET_DEF procedure should be called before update or delete operations where concurrency control is required. Bulk overloads should be used when processing multiple asset definitions to reduce round trips.