Search Results okl_trx_types_pub_w




Overview
Explore in AI Chat

Overview

The APPS.OKL_TRX_TYPES_PUB_W package is a public PL/SQL wrapper belonging to the Oracle Lease and Finance Management (OLFM/ETRM) module of Oracle E-Business Suite. It exposes the transaction type definition APIs used by the leasing application to create, maintain, and validate the transaction type records that drive lease-origination and contract-servicing flows. Within the ETRM architecture, transaction types classify the nature of a lease transaction (for example, new lease, renewal, assumption, or termination) and determine the downstream accounting, booking, and workflow rules applied to a contract. The _PUB_W suffix indicates that this is the published wrapper layer that marshals calls to the underlying business logic, providing a stable, supported entry point for internal EBS components and for extensions that must operate on transaction type setup data.

Key Procedures and Functions

ETRM documentation for this package lists the following procedures. They correspond to the standard DML lifecycle for transaction type records:

  • INSERT_TRX_TYPES — Creates new transaction type definitions, accepting the attribute values that characterize the transaction type and persisting them to the underlying ETRM tables.
  • LOCK_TRX_TYPES — Acquires a locking reference on a transaction type record, ensuring exclusive access during an update or validation operation within the same transaction scope.
  • UPDATE_TRX_TYPES — Modifies existing transaction type definitions, applying changed attributes to already-persisted records.
  • DELETE_TRX_TYPES — Removes transaction type definitions that are no longer required, subject to any referential constraints enforced by the application.
  • VALIDATE_TRX_TYPES — Performs the business-rule validation associated with a transaction type, verifying that the supplied or stored attribute set satisfies ETRM consistency requirements before commit.

Because the wrapper is documented as exposing ten procedures/functions in total, additional private or overloaded entry points may exist, but only the five above are enumerated in the ETRM metadata. No parameter lists are published in the metadata; callers must consult the package specification in the database for exact signatures.

Tables Accessed

The documented dependency list for OKL_TRX_TYPES_PUB_W shows references to FND_API, the Oracle Application Object Library API package used for the standard EBS API return-status and message-buffer protocol, and to the JTF collection types JTF_DATE_TABLE, JTF_NUMBER_TABLE, JTF_VARCHAR2_TABLE_100, JTF_VARCHAR2_TABLE_200, and JTF_VARCHAR2_TABLE_2000. The presence of these collection types indicates that the package follows the table-based (PL/SQL record array) API convention used widely in ETRM, in which multiple transaction type rows are passed in a single invocation. The metadata additionally lists STANDARD and no explicitly named business tables via APPS synonyms, which is consistent with the package delegating physical table access to an underlying private package while it serves purely as the published interface layer.

Usage Notes

OKL_TRX_TYPES_PUB_W is referenced by no other packaged PL/SQL unit according to the documentation, so it is not an internal dependency of the ETRM package hierarchy. It is therefore intended to be called directly — typically from ETRM setup forms, from concurrent programs that mass-maintain transaction type definitions, or from custom extension code that must maintain transaction types programmatically. Invocations should follow the standard EBS API pattern: initialize the FND_API.G_MISS_* sentinels for optional attributes, populate the JTF collection parameters, call the appropriate procedure, and then inspect the returned API status and message buffer. Callers should ensure that a locking call precedes any update, and that validation is performed before committing inserts or updates, in accordance with the transactional contract implied by the published procedure set. The package is valid in both Oracle EBS 12.1.1 and 12.2.2.