Search Results okl_spp_pvt




Overview
Explore in AI Chat

Overview

OKL_SPP_PVT is the private API package body for the Supplier Price Program (SPP) subsystem within Oracle Enterprise Asset Management and Oracle Lease and Finance Management (OLFM), shipped under the ETRM (Enterprise Transaction and Reference Model) module family. The package encapsulates the low-level persistence and validation logic that governs supplier price parameter records stored in the OKL_SIF_PRICE_PARMS table. As a PVT-classified package, OKL_SPP_PVT is not intended for direct customer invocation; it is the internal implementation layer behind the public supplier price interfaces and is consumed exclusively by other OLFM packages that require controlled read/write access to price program setups.

The package adheres to the standard Oracle Applications API architecture, relying on FND_API for message handling, FND_GLOBAL for session context, and OKL_API/OKC_API for common lease and contract utilities. Its dependency footprint confirms it operates within the core leasing transaction flow rather than as a standalone utility.

Key Procedures and Functions

The ETRM metadata documents thirteen procedures and functions within this package body. The core data-manipulation routines follow the conventional EBS API naming pattern:

  • INSERT_ROW — Creates a new supplier price parameter record, populating the OKL_SIF_PRICE_PARMS columns and setting standard WHO audit columns via FND_GLOBAL.
  • UPDATE_ROW — Modifies an existing price parameter row, applying change control semantics before committing values.
  • DELETE_ROW — Removes a supplier price parameter record, typically performing logical or validated deletion consistent with lease setup integrity rules.
  • LOCK_ROW — Acquires a row-level lock to serialize concurrent updates against the same price parameter record.
  • VALIDATE_ROW — Executes business-rule validation against a candidate record before insertion or update, raising API errors through FND_API where constraints are violated.
  • API_COPY — Duplicates an existing price parameter set, supporting versioning and template-style reuse of supplier pricing definitions.
  • CHANGE_VERSION — Manages version transitions for price parameter records, preserving historical pricing configurations.
  • QC — A quality-control or consistency-check routine used to verify the integrity of supplier price data prior to downstream processing.

The remaining documented procedures support these operations internally. Parameter lists are defined in the ETRM reference and are not reproduced here.

Tables Accessed

Two tables are documented as accessed through APPS synonyms. OKL_SIF_PRICE_PARMS is the primary transactional table holding supplier price program parameters, and it is the target of the INSERT_ROW, UPDATE_ROW, DELETE_ROW, and LOCK_ROW operations. A companion view, OKL_SIF_PRICE_PARMS_V, provides the read-side projection used during validation and query operations. The PLITBLM table is accessed as an Oracle-supplied PL/SQL table type used for in-memory collections, typically to buffer rows during bulk validation or copy processing. No other persistent tables are documented as direct dependencies.

Usage Notes

OKL_SPP_PVT is not referenced by any database object and is not intended for direct external calls. It is invoked by six other packages within the OLFM/EBS stack, which act as the public-facing entry points for supplier price program maintenance. In practice, this package is triggered during:

  • Supplier price parameter setup and maintenance screens within Oracle Lease Management, where the form calls a public wrapper that delegates to these row-level routines.
  • Concurrent programs that load or refresh supplier price schedules, using INSERT_ROW and VALIDATE_ROW to stage and verify bulk data.
  • Version management and copy operations initiated when reusing pricing setups across contracts or program revisions, via CHANGE_VERSION and API_COPY.
  • Custom extensions, which should call the public wrapping APIs rather than OKL_SPP_PVT directly, since private API signatures are subject to change across patch levels and are not covered by Oracle's public API support policy.

Because the package is VALID in the APPS schema, it is available in both 12.1.1 and 12.2.2 environments, though routine differences between those releases may exist in dependent code.