Search Results okl_process_trx_types_pvt




Overview
Explore in AI Chat

Overview

OKL_TRX_TYPES_PUB is the public application programming interface for maintaining transaction type definitions within the Oracle Enterprise Transaction Management (ETRM) module of Oracle E-Business Suite. Transaction types are the foundational configuration elements that classify and govern every lease or financing transaction processed in Oracle Lease Management, including new business bookings, assumptions, renewals, terminations, and asset-level adjustments. Because transaction types drive accounting rule generation, workflow routing, and validation logic throughout the lease lifecycle, the integrity of these definitions is critical to downstream processing.

This package exposes the supported, externally callable entry points for creating, modifying, locking, and removing transaction type records. As a PUB-classified API, it is intended to be invoked by other Oracle modules, by the ETRM application forms, and by customer extensions, rather than by end users directly. Internally it depends on OKC_API and OKL_API for standardized error handling and concurrent program context, on OKL_TRY_PVT for transaction type structure validation, and on the SQL STANDARD package. The package is itself referenced by OKL_PROCESS_TRX_TYPES_PVT, the private processing worker that the user search term identifies, as well as by OKL_TRX_TYPES_PUB_W.

Key Procedures and Functions

  • INSERT_TRX_TYPES — Creates a new transaction type record, populating the identifier, descriptive attributes, and the rules that control how transactions of that type behave.
  • UPDATE_TRX_TYPES — Modifies attributes of an existing transaction type, such as its name, description, or associated processing characteristics.
  • DELETE_TRX_TYPES — Removes a transaction type from the repository, subject to the referential constraints imposed by existing transaction data.
  • LOCK_TRX_TYPES — Obtains or releases the concurrency lock on a transaction type definition, preventing simultaneous conflicting maintenance operations.
  • VALIDATE_TRX_TYPES — Executes the business-rule validation logic for a transaction type, verifying required attributes and cross-field consistency before the record is committed.
  • ADD_LANGUAGE — Inserts translated (multi-language) rows for transaction type descriptive columns, supporting the Oracle EBS MLS translation model.

The package also contains a number of private helper routines that support the above public entry points. The documented metadata lists eleven procedures and functions in total, covering the public surface and their supporting private members. Parameter signatures are deliberately not restated here; callers should reference the package specification in the ETRM database for the authoritative argument lists.

Tables Accessed

The package operates on the ETRM transaction type repository through APPS synonyms. The documented table reference is PLITBLM, the transaction type base table that stores the core definition records and their translated columns. The INSERT, UPDATE, DELETE, and LOCK routines issue the corresponding DML against this table, while VALIDATE_TRX_TYPES reads it to confirm uniqueness and referential consistency. ADD_LANGUAGE writes the translation rows associated with PLITBLM. Because the package is a PUBLIC API, all direct table access is encapsulated here so that external callers never manipulate the underlying tables themselves.

Usage Notes

OKL_TRX_TYPES_PUB is typically invoked from three contexts. First, it is called by the ETRM setup forms when an administrator defines or edits transaction types in the Lease Management administrative responsibility. Second, it is invoked by concurrent programs and internal processing packages, most notably OKL_PROCESS_TRX_TYPES_PVT, which orchestrates bulk transaction type processing and relies on this package to perform individual record operations. Third, it is called from customer-written PL/SQL extensions and interface programs that need to load transaction type configuration during implementation or data migration.

Invocation in Oracle EBS 12.1.1 and 12.2.2 follows the standard API pattern: the APPLICATION_ID, ORG_ID, and user context must be initialized before the call, and the standard OKC_API/OKL_API return-status and message parameters should be inspected after execution. Custom code should always use these public entry points rather than writing directly to PLITBLM, because the API enforces validation, language row creation, and concurrency locking that direct DML would bypass.