Search Results create_asset_subsidy




Overview
Explore in AI Chat

Overview

OKL_ASSET_SUBSIDY_PVT_W is a private PL/SQL wrapper package in the Oracle Lease and Finance Management (OKL) module, part of the Oracle E-Business Suite. Its role is to expose the asset subsidy business logic implemented in the underlying package OKL_ASSET_SUBSIDY_PVT to external or generated callers through a standardized, weakly-typed interface. The asset subsidy feature supports the management of subsidies offered on leased assets, allowing transactions to record the value, source, and attributes of a subsidy associated with a specific asset. The package is declared with AUTHID CURRENT_USER and executes with the privileges of the invoking schema, which is typical of Oracle Application Object Library (AOL) private API patterns that sit alongside the public API layer.

The "_W" suffix indicates a wrapper that bridges the internal strongly-typed record structures used by the private package with the weakly-typed PL/SQL tables (JTF_NUMBER_TABLE, JTF_VARCHAR2_TABLE_* variants) consumed by the Java-based Rosetta integration layer in ETRM. The header reference OKLEASBS.pls 115.1 (dated 2003) confirms the package has been stable across the 12.1.1 and 12.2.2 releases without functional revision, consistent with an interface-stability contract.

Key Procedures and Functions

Although the extracted header fragment shows only the Rosetta copy procedures and the beginning of CREATE_ASSET_SUBSIDY, the documented metadata lists twelve procedures and functions associated with the package, including the following public surface:

  • ROSETTA_TABLE_COPY_IN_P1 — Converts Rosetta-delivered JTF weakly-typed table elements into the internal ASB_TBL_TYPE record table used by the private package, enabling inbound integration from Java or Web Services callers.
  • ROSETTA_TABLE_COPY_OUT_P1 — Performs the inverse conversion, marshalling the internal ASB_TBL_TYPE back into JTF table types for outbound integration responses.
  • CREATE_ASSET_SUBSIDY — Creates a new asset subsidy record, taking the standard API parameters (p_api_version, p_init_msg_list, x_return_status, x_msg_count, x_msg_data) plus the subsidy attribute columns exposed via the p5/p6 JTF parameter groups.
  • UPDATE_ASSET_SUBSIDY — Updates an existing subsidy row, applying changed subsidy attributes to the underlying OKL table.
  • DELETE_ASSET_SUBSIDY — Removes a subsidy record; this is the entry point corresponding to the searched term "delete_asset_subsidy" and is invoked when a user or process removes a subsidy from an asset.
  • VALIDATE_ASSET_SUBSIDY — Runs business validation rules against subsidy attributes prior to create or update.
  • CALCULATE_ASSET_SUBSIDY — Computes subsidy amounts or derived values using the lease and asset context.

Tables Accessed

The ETRM metadata documents a single physical table reference for this package: PLITBLM, accessed through an APPS synonym. PLITBLM is the migration/transition table used by the Oracle data-migration and error-logging infrastructure; its presence here indicates the wrapper participates in bulk data conversion or sees the subsidy rows as part of a broader migration context. No direct OKL_ASSET_SUBSIDY table is documented, because the underlying DML is delegated to the private package OKL_ASSET_SUBSIDY_PVT, which owns the OKL base tables for asset subsidy. The wrapper therefore reads and writes PLITBLM for staging purposes while invoking the private layer for actual subsidy persistence.

Usage Notes

OKL_ASSET_SUBSIDY_PVT_W is a private wrapper and is not intended for direct customer invocation. It is referenced by zero other packages in the ETRM metadata, meaning it is called exclusively from generated Rosetta integration stubs, from the OKL public API layer (OKL_ASSET_SUBSIDY_PUB), or from internal batch jobs. In Oracle EBS 12.1.1 and 12.2.2, the typical invocation path is through the Lease and Finance Management forms or the Asset Subsidy concurrent program, which ultimately delegate to the PUBLIC package, which in turn calls this wrapper for Rosetta-based middleware flows. Custom code should never call this package directly; developers should instead use the supported OKL_ASSET_SUBSIDY_PUB API for create, update, delete, validate, and calculate operations, and rely on the standard fnd_msg_pub message stack to interpret x_return_status, x_msg_count, and x_msg_data after each call.