Search Results okl_txl_quote_lines_pub




Overview
Explore in AI Chat

Overview

The APPS.OKL_TXL_QUOTE_LINES_PUB package body is a public (PUB-classified) PL/SQL API within Oracle E-Business Suite's Enterprise Taxation and Regulatory Management (ETRM) module, historically branded as Oracle Lease and Finance Management (OKL). It exposes the transactional interface through which quote lines associated with tax and lease transactions are created, maintained, validated, and removed. In the EBS 12.1.1 and 12.2.2 releases, this package functions as the outermost public layer of a three-tier API architecture: the public wrapper (_PUB) delegates business logic to the private package OKL_TQL_PVT, which in turn relies on the shared infrastructure packages OKC_API, OKL_API, and FND_API for contract-layer integration, error handling, and message resolution respectively. Its principal business purpose is to allow callers to manipulate tax-relevant quote line records in a controlled, validated manner, ensuring that tax determination and regulatory data captured during the quoting cycle remain consistent before conversion to a lease or contract.

Key Procedures and Functions

The documented metadata identifies ten procedures and functions in the package, with the following five exposed as the core public operations:

  • INSERT_TXL_QUOTE_LINES — Creates new tax quote line records, accepting the header and line attributes supplied by the calling application and persisting them through the private layer.
  • LOCK_TXL_QUOTE_LINES — Acquires a pessimistic lock on an existing quote line record, preventing concurrent modification during multi-step transactions or user edit sessions.
  • UPDATE_TXL_QUOTE_LINES — Modifies attributes of an existing tax quote line, typically after recalculation or user adjustment of taxable amounts.
  • DELETE_TXL_QUOTE_LINES — Removes a tax quote line record, subject to the validation rules enforced by the underlying private package.
  • VALIDATE_TXL_QUOTE_LINES — Performs pre-write validation of quote line data, checking required attributes, referential integrity, and tax-specific business rules before insert or update processing.

The remaining five documented routines follow the same procedural naming convention and support auxiliary operations within the same transactional domain. Consistent with EBS API standards, all operations are expected to signal outcomes through the FND_API return-status conventions (FND_API.G_RET_STS_SUCCESS, ERROR, UNEXPECTED_ERROR) and to accumulate messages in the FND_MSG_PUB stack rather than raising unhandled exceptions. Parameter lists are not reproduced here because they are not part of the documented metadata.

Tables Accessed

The ETRM dependency documentation lists only PLITBLM as a directly referenced table via APPS synonyms. PLITBLM is the standard EBS PL/SQL index-by table (associative array) package, typically used by API implementations to pass multi-row collections of records into and out of the private layer. The substantive tax quote line data is stored in the OKL transaction tables managed by OKL_TQL_PVT; the public package does not manipulate these base tables directly, which preserves the encapsulation required by Oracle's API design standards.

Usage Notes

OKL_TXL_QUOTE_LINES_PUB is not referenced by any database object, confirming that it is an entry-point API rather than a dependency of other schema objects. The documented metadata additionally indicates it is referenced by eleven other packages in the ETRM schema, reflecting a supporting role in the broader OKL quote and tax pipeline. Typical invocation scenarios include:

  • Oracle Forms-based quote entry and maintenance screens in the Lease and Finance Management module, which call the public API for line-level DML.
  • Concurrent programs that batch-process tax quote lines for recalculation, migration, or end-of-period reconciliation.
  • Custom PL/SQL extensions and integrations that must respect the same validation and messaging semantics as the seeded application.

Callers should initialize the FND_MSG_PUB message stack before invocation and inspect the returned status code afterward; the API is designed for composition with FND_API transaction control, so savepoints and commits remain the responsibility of the calling program.