Search Results create_trx_asset_parm

Overview

OKL_SETUP_TRXPARAMS_PUB is a public PL/SQL API package in the Oracle E-Business Suite Contracts (OKL/OKC) module, specifically associated with Oracle Lease and Finance Management (OKL). Operating under AUTHID CURRENT_USER, it exposes the transactional parameter setup layer that governs how lease and contract transactions are configured at runtime. The package provides a standardized, concurrent-safe interface for maintaining transaction parameters and transaction asset parameters — the definable attributes that control behavior on lease and financing transactions, such as asset-level defaults, pricing and accounting controls, and processing options.

The package adheres to the EBS public API design standard. It declares the standard constants G_MISS_NUM, G_MISS_CHAR, and G_MISS_DATE for attribute-level omission, along with the customary return-status constants (G_RET_STS_SUCCESS, G_RET_STS_ERROR, G_RET_STS_UNEXP_ERROR) and the associated named exceptions. Each API returns a return status, message count, and message data so callers can handle errors consistently without parsing exception text. The header references OKL_API and OKC_API, confirming that it participates in the shared Contracts API framework rather than implementing private, package-local error handling.

Key Procedures and Functions

• CREATE_TRX_PARM — Creates a transaction parameter record for a lease or contract transaction. Accepts the standard API version and initialization arguments and returns the standard status and message outputs.
• UPDATE_TRX_PARM — Updates an existing transaction parameter record. This is the transaction-level counterpart to the asset-level update routine sought by the search term "update_trx_asset_parm."
• DELETE_TRX_PARM — Removes a transaction parameter record.
• CREATE_TRX_ASSET_PARM — Creates an asset-level transaction parameter record, associating parameter values with a specific asset on a transaction.
• UPDATE_TRX_ASSET_PARM — Updates an existing asset-level transaction parameter record. This is the routine directly relevant to the query "update_trx_asset_parm": it is the supported, public entry point for modifying asset-specific transaction parameter values without direct DML against the underlying tables.

The metadata documents ten procedures/functions in total; the five above are the documented core CRUD operations for transaction and asset parameters. The package also defines the sxpv_rec_type and sxpv_tbl_type subtypes by reference to OKL_SIF_TRX_PARMS_PUB, indicating that single-record and table (bulk) parameter structures are shared with the SIF transaction-parameters public API.

Tables Accessed

The documented table reference for this package is PLITBLM, accessed through an APPS synonym. Consistent with its role, OKL_SETUP_TRXPARAMS_PUB reads and writes the transaction parameter and transaction asset parameter storage used by the lease setup and transaction flows. The presence of G_MISS_NUM, G_MISS_CHAR, and G_MISS_DATE constants indicates the API performs attribute-level validation and null-handling before committing changes, ensuring that omitted columns are preserved on update and defaulted on create.

Usage Notes

This package is intended to be called rather than queried directly. Typical invocations occur from Oracle Forms setup and transaction windows, from concurrent programs that seed or migrate transaction parameters, and from custom PL/SQL that extends lease transaction configuration. Callers must pass a valid API version, honor the returned x_return_status, and inspect x_msg_count and x_msg_data for diagnostics. Because the API is AUTHID CURRENT_USER and classified as PUB, it is a supported extension point in both 12.1.1 and 12.2.2; direct inserts or updates against the underlying parameter tables should be avoided in favor of CREATE_TRX_PARM, UPDATE_TRX_PARM, CREATE_TRX_ASSET_PARM, and UPDATE_TRX_ASSET_PARM. It is referenced by one other package, and the shared record/table types with OKL_SIF_TRX_PARMS_PUB mean changes to parameter structure should be coordinated across both APIs.