Search Results okl_trq_pvt




Overview
Explore in AI Chat

Overview

OKL_TRQ_PVT is a private PL/SQL package in the APPS schema belonging to the Oracle Lease and Finance Management (OKL) module of Oracle E-Business Suite. The "PVT" suffix designates it an internal, private API — its procedures are not intended for direct invocation by external integrations, but rather are consumed by other packages within the OKL transaction request framework. Its central responsibility is the maintenance and validation of transaction request records: the structured requests that drive lease lifecycle events such as renewals, payoffs, asset updates, billing adjustments, and stream processing.

The package operates as a supporting private layer beneath the public transaction request APIs. It provides row-level DML operations, concurrency control, and business validation for the OKL_TRX_REQUESTS table, and it is tightly coupled to the workflow and processing packages that submit and route transaction requests across the lease management suite. Its dependency on FND_API and OKL_API confirms that it adheres to the standard EBS API conventions: error handling through FND_MSG_PUB, standard savepoint and initialization patterns, and consistent return-status conventions.

Key Procedures and Functions

  • QC — A quality-control / consistency check routine, likely used to validate that the package's state and the underlying transaction request data conform to expected invariants before processing proceeds.
  • CHANGE_VERSION — Manages version tracking for transaction request rows, supporting optimistic concurrency so that concurrent updates do not silently overwrite one another.
  • API_COPY — Copies transaction request definition data, typically used when duplicating or propagating a request structure from one context to another (for example, across contract versions or processing runs).
  • INSERT_ROW — Inserts a new transaction request row into OKL_TRX_REQUESTS, applying the package's standard defaults and validation.
  • LOCK_ROW — Acquires a row-level lock on an existing transaction request, protecting it from conflicting concurrent modification during workflow processing.
  • UPDATE_ROW — Updates an existing transaction request record, enforcing validation and version control.
  • DELETE_ROW — Removes a transaction request row, subject to the package's referential and business-rule checks.
  • VALIDATE_ROW — Performs business-rule validation on a transaction request row without persisting changes, allowing callers to pre-validate before commit.

The documented metadata lists 18 procedures and functions in total; the eight above are the published core, with the remainder being internal helper routines supporting these operations.

Tables Accessed

  • OKL_TRX_REQUESTS — The primary transaction request table. All INSERT, UPDATE, DELETE, LOCK, and VALIDATE operations target this table. It stores the requests that initiate downstream lease processing.
  • OKL_TRQ_SEQ — A sequence object supplying unique transaction request identifiers for newly inserted rows.
  • DUAL — The standard Oracle single-row utility table, used for sequence retrieval and expression evaluation.
  • PLITBLM — A PL/SQL-indexed table type relied upon internally for bulk or collection-based processing within the package.

Access is performed through APPS synonyms, consistent with standard EBS development conventions.

Usage Notes

OKL_TRQ_PVT is invoked indirectly. The ETRM metadata shows it is referenced by eleven packages, including OKL_TRX_REQUESTS_PUB (the public wrapper), OKL_CS_WF, OKL_SSC_WF, OKL_BILLING_REF_WF, OKL_CONVERT_INT_TYPE_WF, OKL_PROCESS_STREAMS_PVT, OKL_AMORT_SCHED_REQ_PVT, OKL_BLK_AST_UPD_PVT, OKL_LA_SALES_TAX_PVT, OKL_CS_LEASE_RENEWAL_PVT, and OKL_CS_PRINCIPAL_PAYDOWN_PVT. This dependency pattern confirms that it is a private DML and validation engine shared across lease workflow, billing, tax, amortization, and contract-service processes.

Custom code should never call OKL_TRQ_PVT directly; instead, use the documented public API OKL_TRX_REQUESTS_PUB or the relevant workflow package. Because the PKG is private and its procedures carry no public parameter contract, direct invocation risks breakage on patching or upgrade. Oracle EBS 12.1.1 and 12.2.2 both ship this package in valid status, and 12.2.2's online patching model means any custom dependency on internals should be reviewed before each upgrade cycle.