Search Results update_executiondetails

Overview

DPP_EXECUTIONDETAILS_PVT is a private PL/SQL package in the APPS schema within Oracle E-Business Suite. Its name derives from the Oracle Advanced Pricing (formerly E-Business Suite Advanced Pricing) module, whose internal schema prefix is "DPP". The package forms part of the pricing engine's runtime infrastructure, specifically the layer that records and maintains execution details for pricing transactions. In Oracle EBS, every pricing request — whether a list price lookup, purchase price derivation, item cost determination, or customer claim calculation — is executed against an "execution" context. The DPP_EXECUTIONDETAILS_PVT package persists the outcome and metadata of those execution contexts, providing the audit and traceability backbone used for debugging, retry, and integration reconciliation.

The object resides in the APPS schema and is classified as a Private (PVT) package, meaning it is intended for internal use by other pricing packages and is not exposed directly to users or external APIs. It is marked VALID and is documented against ETRM 12.2.2, with applicability to 12.1.1 and 12.2.2 releases. In the ETRM dependency listing, DPP_EXECUTIONDETAILS_PVT references APPS.FND_API and the SYS.STANDARD package, confirming reliance on the Oracle Applications API framework (for error handling and message conventions) and standard PL/SQL runtime constructs.

Because the package is private, it is not documented for direct customer invocation. Its role is instead to support the higher-level pricing service packages, several of which — DPP_BPEL_UPDATEEXECDTLS, DPP_ERROR_PVT, DPP_ITEMCOST_PVT, DPP_LISTPRICE_PVT, and DPP_PURCHASEPRICE_PVT — call into it. The reverse dependency on DPP_EXECUTIONDETAILS_PVT itself (self-referenced in the ETRM listing) indicates internal recursive calls, typically when a single logical execution updates multiple detail rows or re-enters to append a related record.

Key Procedures and Functions

The documented public interface consists of two procedures, both concerned with maintaining the execution detail record after or during a pricing run:

• UPDATE_EXECUTIONDETAILS — Persists or updates the execution details associated with a pricing execution. This is the primary maintenance routine invoked by the calling pricing packages when an execution completes, changes state, or must have its summary attributes reflected in the DPP_EXECUTION_DETAILS repository.
• UPDATE_ESB_INSTANCEID — Records the Enterprise Service Bus (ESB) instance identifier against the execution detail record. This links the Oracle EBS pricing execution to the corresponding integration message handled by the SOA/ESB middleware layer, enabling end-to-end tracing between the EBS pricing engine and external service orchestration.

No parameter lists are documented in the available metadata, and none should be assumed. Both routines are implementation-level and are called exclusively by other DPP packages and the BPEL update wrapper DPP_BPEL_UPDATEEXECDTLS.

Tables Accessed

Through APPS synonyms, the package touches the following objects:

• DPP_EXECUTION_DETAILS — The central execution detail table; the primary target of both procedures.
• DPP_CUSTOMER_CLAIMS_ALL — Supports customer claim pricing executions, allowing claims data to be reflected in the execution record.
• DPP_TRANSACTION_LINES_ALL — Provides pricing transaction line context, so execution details can be tied to specific pricing request lines.
• PLITBLM — A PL/SQL index-by table type used internally for bulk processing.
• XMLTYPE — Utilized for storing or parsing XML payload structures, consistent with the ESB integration identifier handling.

Usage Notes

DPP_EXECUTIONDETAILS_PVT is not invoked directly from Oracle Forms, concurrent programs, or user-facing workflows. It is a subordinate utility package called by the pricing engine's higher-level private packages and by DPP_BPEL_UPDATEEXECDTLS, which is the BPEL/ESB integration entry point. Customizations should not call it directly; supported extension points are the public pricing APIs. When troubleshooting pricing executions, review DPP_EXECUTION_DETAILS rows updated via these procedures and correlate the ESB instance identifier for integrated flows.