Search Results okl_asd_pvt




Overview
Explore in AI Chat

Overview

OKL_ASD_PVT is a private PL/SQL package body in the APPS schema within Oracle E-Business Suite, belonging to the Oracle Lease and Finance Management (OKL) module of the ETRM (Enterprise Trade and Risk Management) product family. The package name embeds the module prefix OKL and the object mnemonic ASD, which in the OKL data model refers to asset depreciation and the underlying asset master records stored in the OKL_TXD_ASSETS tables. The package therefore supports the maintenance and lifecycle management of lease assets, including their descriptive attributes, depreciation method assignments, book controls, and translated descriptions. Because the package is classified as a private (PVT) API rather than a public (PUB) API, it is intended for internal consumption by other OKL packages and is not part of the supported external integration surface. The package body is documented as VALID and is referenced by 31 other database objects, indicating a central role in the asset-side processing performed by the Lease Management application.

Key Procedures and Functions

The package exposes fourteen documented procedures and functions. Their names follow the standard Oracle Application Object Library (AOL) table-handler and API conventions:

  • QC — A quality-control or consistency check routine, typically used to verify the internal state of the package or the asset data before further processing.
  • CHANGE_VERSION — Manages concurrency-version stamping, supporting optimistic locking on asset rows between concurrent sessions.
  • API_COPY — Provides programmatic copying of asset records, used when duplicating an asset definition or creating a derivative record.
  • ADD_LANGUAGE — Inserts translated (TL) rows for asset descriptions, supporting multi-language installations.
  • INSERT_ROW — The core create routine for new asset rows, propagating inserts to the base and translation tables.
  • LOCK_ROW — Acquires a row-level lock on a specific asset record prior to modification.
  • UPDATE_ROW — Modifies existing asset records and their translated attributes.
  • DELETE_ROW — Removes asset records and their dependent translation rows.
  • VALIDATE_ROW — Performs the business-rule validation that must pass before an insert or update is committed.

No parameter lists are published in the ETRM metadata; callers must follow the internal conventions established by OKC_API, OKL_API and FND_API, which this package invokes.

Tables Accessed

The package reads and writes the following documented tables through APPS synonyms:

  • OKL_TXD_ASSETS_B and OKL_TXD_ASSETS_TL — The base and translated tables for lease asset definitions; these are the primary subject of the row-level DML and validation logic.
  • OKL_TXL_ASSETS_V — A view over asset lines, used for read access during validation and copying.
  • FND_LANGUAGES — Provides installed language information for ADD_LANGUAGE and translation handling.
  • GL_CURRENCIES and GL_DAILY_CONVERSION_TYPES — Supply currency codes and conversion type definitions used in asset financial attribute processing.
  • OKC_K_HEADERS_ALL_B and OKC_K_LINES_B — The contract headers and lines tables from Oracle Contracts, linking assets to their governing lease contracts.
  • OKL_TXL_ASSETS_B and DUAL — Supporting structures and single-row queries, with PLITBLM used for PL/SQL index-by-table bulk processing.

Additional dependencies include OKL_ACCOUNTING_UTIL, OKC_P_UTIL, FND_GLOBAL and APP_EXCEPTIONS, reflecting the package's integration with accounting, contract utilities and the standard exception-handling framework.

Usage Notes

OKL_ASD_PVT is invoked internally by the OKL asset maintenance flows rather than directly by end users. In Oracle EBS 12.1.1 and 12.2.2 it is typically called from the Lease Management asset entry forms, from concurrent programs that mass-maintain or migrate asset records, and from other OKL packages that need to create, copy, lock, update or delete asset definitions. Because it is a private package, customizations should call the corresponding public API (for example OKL_ASSET_PUB) where one exists, and treat OKL_ASD_PVT as an implementation detail that Oracle may change without notice. The dependency on FND_API and the standard validate-then-insert/update pattern means callers must respect the returned API status and message codes, and must not bypass the VALIDATE_ROW and CHANGE_VERSION routines when writing asset data directly.