Results for “update_trx_status”
50+ results
AI-generated from documented ETRM metadata — verify critical details on the linked pages.
Overview
OKL_TRANSACTION_PUB_W is a public PL/SQL package in the APPS schema that forms part of the Oracle Lease and Finance Management (OKL) module within Oracle E-Business Suite. It acts as a transactional API layer for lease and finance contracts, exposing the core operations needed to create contract transactions, update their status, and manage contract revisions. The package is classified as an OTHER API in the ETRM repository, meaning it is a documented public interface rather than a private internal helper. Its status is VALID in both 12.1.1 and 12.2.2, indicating it remains a supported and stable entry point across these releases.
In business terms, this package supports the contract lifecycle within the leasing application. Transactions represent the financial and non-financial events recorded against a lease or loan contract, such as bookings, adjustments, terminations, and revision-driven changes. By centralizing the creation and status management of these transactions in a public package, OKL provides a controlled programmatic interface that avoids direct manipulation of underlying OKL tables.
Key Procedures and Functions
The documented interface exposes the following callable units. Parameter lists are intentionally excluded, as the ETRM metadata does not publish them.
- CREATE_TRANSACTION — Creates a new transaction record within the lease or finance contract context. This is the primary entry point for introducing a transactional event into the OKL data model, and it is the routine most commonly invoked by integration and extension code.
- UPDATE_TRX_STATUS — Modifies the status of an existing transaction. Status transitions govern whether a transaction is active, processed, or otherwise finalized, and this procedure is the sanctioned way to drive those state changes without bypassing application logic.
- ABANDON_REVISIONS — Discards or cancels pending revisions associated with a contract. Revisions capture proposed changes to contract terms, and this procedure is used when those proposed changes should not be applied.
Tables Accessed
The ETRM metadata lists no explicit base tables referenced through APPS synonyms. The recorded dependency section shows the package references the APPS schema, the JTF_NUMBER_TABLE collection type, and SYS.STANDARD. The dependency on JTF_NUMBER_TABLE indicates that at least one routine accepts or internally uses a numeric ID collection, a common pattern in OKL public APIs for passing arrays of identifiers. Because no tables are documented in the extracted metadata, table access is described here at a functional level only: the package reads and writes the OKL transaction and revision tables that back lease contract processing, together with the supporting lookup and reference tables that those operations require. Consultants requiring an authoritative table list should inspect the package body and its runtime dependency view rather than relying on the summary metadata.
Usage Notes
OKL_TRANSACTION_PUB_W is normally invoked from three sources. First, Oracle Lease and Finance Management forms call the package when a user performs contract actions that result in a transaction being created or restated. Second, concurrent programs and workflow activities that process contract revisions or status updates may invoke it in batch. Third, and most relevant to technical consultants, it serves as the supported integration point for custom PL/SQL, interfaces, and external systems that must record transactions or change transaction status without writing directly to OKL tables.
The ETRM metadata records zero packages referencing this package as a dependency, so it functions as a leaf-level public API rather than a shared internal library. When extending OKL, calls should be made through this public wrapper in preference to lower-level internal packages, since the public layer encapsulates validation and status logic that direct DML would bypass. Testing in a non-production environment is advisable before promoting any custom code that invokes these routines.