Search Results quote_line_dtls




Overview

OKL_AM_TERMNT_QUOTE_PUB is the public PL/SQL API package for termination quoting within the Oracle E-Business Suite Lease and Finance Management (OKL) module, part of the Enterprise Taxation and Regulatory Management / Oracle Lease Management stack. In Release 12.1.1 and 12.2.2, this package encapsulates the business logic required to terminate an existing lease quote, submit quotes for internal approval, validate asset serial numbers, and maintain the individual line details that make up a quote. The package is classified as a PUB (public) API, meaning its procedures form the officially supported integration surface for external callers—Oracle Forms, concurrent programs, and customer-written extensions—rather than an internal implementation detail subject to change.

The header comment, $Header: OKLPTNQB.pls 120.4 2007/12/14 14:03:02 nikshah ship $, shows the file reaching production-ready status with version 120.4. The implementation makes extensive use of the FND_LOG diagnostic framework through OKL_DEBUG_PUB, exposing procedure-, exception-, and statement-level tracing controlled by module name okl.am.plsql.okl_am_termnt_quote_pub. This instrumentation allows DBAs and support engineers to enable targeted debugging without altering code.

Key Procedures and Functions

The package documents eleven procedures and functions, seven of which carry the strongest functional significance:

  • TERMINATE_QUOTE — Terminates an existing quote. The signature follows the standard EBS API convention (p_api_version, p_init_msg_list, x_return_status, x_msg_count, x_msg_data), supplemented by term_rec_type input/output records and an x_err_msg output. Bug #3921591 introduced the p_acceptance_source parameter to identify the acceptance source driving the termination. The procedure opens with SAVEPOINT trx_terminate_quote, enabling clean rollback on failure, and logs both entry and input parameters when statement-level debug is enabled.
  • SUBMIT_FOR_APPROVAL — Routes a completed quote into the approval workflow, moving it from draft to an approval-eligible state.
  • CHECK_ASSET_SNO — Validates an asset serial number, typically invoked during quote line entry to prevent invalid or duplicate asset references.
  • QUOTE_LINE_DTLS — Returns the detail rows of a quote line. This is the procedure most directly associated with the user search term quote_line_dtls; callers use it to retrieve line-level attributes for display, validation, or downstream processing.
  • CREATE_QUOTE_LINE — Inserts a new quote line, applying standard validation and defaulting logic.
  • UPDATE_QUOTE_LINE — Modifies an existing quote line, preserving the standard return-status and message-count contract.
  • DELETE_QUOTE_LINE — Removes a quote line, with corresponding integrity handling.

The remaining documented entries complete the set of eleven, supporting the create/read/update/delete lifecycle of quote lines and the quote termination and approval flow.

Tables Accessed

The metadata identifies two tables accessed via APPS synonyms:

  • OKL_K_LINES — The lease line table underlying quote line storage. All CREATE, UPDATE, DELETE, and QUOTE_LINE_DTLS operations resolve to this table, making it the central transactional target of the package.
  • PLITBLM — The standard Oracle Applications message table used by the FND message stack. The procedures read it indirectly to populate x_msg_count and x_msg_data when errors occur.

Usage Notes

OKL_AM_TERMNT_QUOTE_PUB is referenced by seven other packages, confirming its role as a shared service layer rather than a leaf module. It is typically invoked from the Lease Management quote and termination forms, from concurrent programs performing bulk quote maintenance or approval submission, and from custom PL/SQL code that must create, inspect, or retire quote lines programmatically. Callers should always initialize the message list, inspect x_return_status before consuming output parameters, and treat the API as the only sanctioned entry point to OKL_K_LINES quote-line data. Because FND_LOG tracing is built in, support personnel can enable debug output at procedure, exception, or statement granularity to diagnose termination and line-maintenance failures in production.