Search Results insert_msg




Overview
Explore in AI Chat

Overview

The APPS.QP_OA_DELAYED_REQUESTS_PVT package body supports the Oracle Advanced Pricing (QP) module's delayed request infrastructure used within the Oracle E-Business Suite 12.1.1 and 12.2.2 environments. Its principal business purpose is to capture and stage pricing-related requests that cannot be processed immediately, persisting them into a holding table so that they may be dequeued and executed at a later point in time. This deferred-processing pattern is common in Advanced Pricing where high concurrency, external integrations, or asynchronous workflows would otherwise block synchronous execution. The package is classified as a private (PVT) API, meaning it is an internal implementation artifact intended for use by other QP components and not as a public integration surface. It is documented in ETRM with a single exposed procedure, EXECUTE, though the supplied source excerpt additionally reveals the internal helper insert_msg.

Key Procedures and Functions

  • EXECUTE — The sole documented procedure. It processes a collection of delayed pricing requests passed in as a table of request records. It reports failure context through output parameters that identify the offending request type and entity identifier. This procedure forms the primary entry point used by callers that wish to drain or replay the pool of staged requests.
  • insert_msg — An internal helper procedure, visible in the source but not listed among the ETRM-documented procedures. It inserts a single delayed request record into the staging table and returns a status string. Notably, it is declared with PRAGMA AUTONOMOUS_TRANSACTION, allowing its INSERT and COMMIT to persist independently of the caller's transactional context. This design ensures that a staged request survives even if the surrounding transaction is rolled back.

No parameter lists are reproduced here, as the ETRM metadata documents only EXECUTE by name.

Tables Accessed

  • QP_FWK_DELAYED_REQUESTS — The central staging table for delayed requests. It stores the request type, entity identifiers, status, five generic request-unique keys, twenty-five generic parameters, and one long parameter. insert_msg writes to this table; EXECUTE reads from it to retrieve and process pending requests.
  • PLITBLM — An EBS standard table referenced by the package, typically used in the context of storing or retrieving large text bodies associated with request payloads.

Usage Notes

This private package is normally invoked internally by Oracle Advanced Pricing rather than called directly from custom code. Typical invocation paths include asynchronous pricing flows, integration adapters, and scheduled retry or replay logic where requests are first queued via insert_msg and later drained through EXECUTE. The autonomous-transaction pragma on insert_msg means that staged rows are committed immediately upon insertion, so callers must treat the staging table as an independent, durable queue rather than part of a single unit of work. Because the package is classified PVT and is referenced by zero other packages per the ETRM metadata, its interfaces are not guaranteed stable across releases; developers extending or debugging deferred-pricing behavior should treat QP_FWK_DELAYED_REQUESTS as the reliable inspection point while considering any direct calls to EXECUTE as unsupported.