Search Results generate_debug_req_seq

Overview

QP_COPY_DEBUG_PVT is a private PL/SQL package in the APPS schema that supports Oracle E-Business Suite's Oracle Advanced Pricing (QP) debugging infrastructure. Its business purpose is to capture, stage, and persist diagnostic information generated during pricing engine execution, copying debug records from transient processing structures into permanent debug repository tables. The package operates alongside the public QP_COPY_DEBUG_PUB and the QP_PREQ_GRP package that drives pricing request processing.

The object is classified as a PVT package within the ETRM repository, meaning it is intended for internal use by the Oracle Pricing application rather than as a supported customer-facing API. It is a dependency of several higher-level pricing packages and is documented against Oracle EBS 12.1.1 and 12.2.2. Its presence on the ETRM search index under the temporary table QP_NPREQ_LINES_TMP confirms its role in the pricing request debug pipeline, where line-level pricing request data is harvested before being written to permanent debug storage.

Key Procedures and Functions

• REQUEST_ID — Returns or resolves the identifier of the current debug request, providing the correlation key that ties captured debug rows back to the originating pricing request.
• SET_REQUEST_TO_NULL — Clears the request identifier, resetting package state after a debug copy cycle completes or when no active debug request exists.
• WRITE_TO_DEBUG_TABLES — The core driver that copies staged debug content into the permanent QP debug tables, moving data from temporary pricing request structures into the debug repository.
• INSERT_DEBUG_LINE — Inserts an individual debug line or record into the target debug tables, invoked for each row processed during the copy.
• GENERATE_DEBUG_REQ_SEQ — Generates the next sequence value used to assign unique identifiers to debug request records.

These five documented procedures collectively implement the state management, sequence generation, and row-level insertion logic required to persist debug output.

Tables Accessed

• QP_DEBUG_REQ, QP_DEBUG_REQ_LINES, QP_DEBUG_REQ_LINE_ATTRS, QP_DEBUG_REQ_LDETS, QP_DEBUG_REQ_RLTD_LINES, QP_DEBUG_REQ_S — the permanent debug repository tables to which records are written.
• QP_DEBUG_FORMULA_STEP_VALUES, QP_DEBUG_TEXT — debug tables capturing formula evaluation and free-text diagnostic content.
• QP_NPREQ_LINES_TMP, QP_NPREQ_LINE_ATTRS_TMP, QP_NPREQ_LDETS_TMP, QP_NPREQ_RLTD_LINES_TMP, QP_NFORMULA_STEP_VALUES_TMP — temporary pricing request structures from which debug data is read and copied.
• OE_ORDER_HEADERS_ALL, OE_ORDER_LINES_ALL — order headers and lines supplying context for the request being debugged.
• QP_LINE_ATTR_S, QP_PREQ_GRP, DUAL, PLITBLM — supporting objects used for line attribute lookup, request grouping, and control flow.

Usage Notes

The package is invoked indirectly through pricing request processing rather than being called directly by end users. It is referenced by QP_COPY_DEBUG_PVT itself, QP_PREQ_GRP, QP_PREQ_PUB, and QP_UTIL_PUB, indicating that the public pricing APIs and utility routines drive it during debug capture. Typical invocation occurs when Oracle Pricing debug mode is enabled and a pricing request is executed from the order management flow, either through the Sales Orders form, Order Management concurrent programs, or custom code that calls the public Pricing APIs. Because it is a private package with no documented public interface, customizations should avoid direct calls; instead, developers enable the standard debug profile options and allow QP_PREQ_GRP and related public APIs to trigger the copy routines. Debug requests should be purged periodically as the repository tables can accumulate significant row volumes.