Search Results pl_to_sql13




Overview
Explore in AI Chat

Overview

DPP_BPEL_GETPODATA is a PL/SQL package body owned by the APPS schema in Oracle E-Business Suite. It forms part of the Oracle Advanced Pricing and Procurement pricing infrastructure, specifically the component that bridges BPEL (Business Process Execution Language) web service invocations with the underlying purchase order and purchase price data structures. Its name indicates its role: retrieving purchase order data for consumption by BPEL-based integration flows, most commonly in the context of Oracle Supplier Network and punchout/direct procurement integrations.

The package has no public declaration of an independent specification in the documented metadata; it is classified as an OTHER API and is marked VALID in the ETRM repository for 12.2.2. Its most significant characteristic is that it is not referenced by any other database object, meaning it operates purely as an entry point invoked from outside the database — typically by SOA Suite/BPEL processes or through the Advanced Pricing integration layer.

Key Procedures and Functions

The package exposes eleven documented procedures and functions. These fall into two functional groups:

  • PL_TO_SQL11, PL_TO_SQL12, PL_TO_SQL13, PL_TO_SQL14, PL_TO_SQL15 — a series of conversion routines that translate PL/SQL collection structures into SQL-accessible data sets. The numeric suffixes correspond to internal revision or interface variants, reflecting successive versions of the pricing and procurement integration contract.
  • SQL_TO_PL11, SQL_TO_PL12, SQL_TO_PL13, SQL_TO_PL14, SQL_TO_PL15 — the inverse routines, marshalling SQL query results back into PL/SQL collections for processing within the package or by the calling BPEL flow.
  • DPP_PURCHASEPRICE_PVT$NOTIFY_ — a notification routine associated with the DPP_PURCHASEPRICE_PVT pricing private API, used to signal events or status changes back to the pricing engine after purchase order data retrieval.

The paired PL_TO_SQL and SQL_TO_PL naming convention indicates a bidirectional data marshalling layer designed to move bulk purchase order records between the PL/SQL runtime and SQL statements executed on behalf of external callers.

Tables Accessed

The only documented table referenced through APPS synonyms is PLITBLM, a standard Oracle EBS table used for storing large object (LOB) and interface data. This confirms that the package handles bulk data transfer, likely staging purchase order or pricing payloads for BPEL consumption. All remaining data access is delegated to the dependent pricing packages rather than performed directly.

Usage Notes

DPP_BPEL_GETPODATA depends on APPS.DPP_PURCHASEPRICE_PVT and its generated variants (DPP_PURCHASEPRICE_PVT_DPP_P11, DPP_PURCHASEPRICE_PVT_DPP_P13, DPP_PURCHASEPRICE_PVT_DPP_PO10, DPP_PURCHASEPRICE_PVT_DPP_PO_), as well as DPP_PURCHASEPRICEPVTDPPP11_DPP. These dependencies confirm that the package is a thin retrieval facade over the purchase price private API.

Typical invocation occurs from BPEL/SOA composites exposed through the Oracle EBS Integrated SOA Gateway, or from concurrent programs and custom code that need to fetch purchase order data formatted for external pricing workflows. Because it is referenced by no other database object, it should be treated as a callable integration endpoint. In 12.1.1 and 12.2.2, the package is delivered as part of the Advanced Pricing patch family; it should not be modified directly, and any customization should wrap rather than alter its logic.