Search Results dpp_bpel_getipl




Overview
Explore in AI Chat

Overview

APPS.DPP_BPEL_GETIPL is a VALID PL/SQL package in the APPS schema that supports Oracle E-Business Suite Advanced Pricing and the Oracle BPEL (Business Process Execution Language) notification infrastructure. In EBS 12.1.1 and 12.2.2, DPP (Oracle Pricing) integrates with BPEL-based business events and process flows, particularly for price list and pricing notification activities. The package name suggests its primary role: translating between PL/SQL data structures and SQL-representable payloads exchanged with BPEL processes ("GETIPL" implying retrieval of pricing/price list data for external process consumption).

Functionally, DPP_BPEL_GETIPL acts as a conversion and integration utility layer, bridging the internal pricing engine (DPP_PRICING_PVT) and the notification mechanisms used to publish pricing events. It exposes conversion routines that transform between PL/SQL collections/records and SQL-queryable forms, which is characteristic of EBS packages designed to marshal data for BPEL web services or concurrent/notification consumers.

Key Procedures and Functions

The documented package exposes nine procedures/functions. Consistent with ETRM metadata, their purpose is described below without inventing parameter signatures:

  • PL_TO_SQL0, PL_TO_SQL1, PL_TO_SQL2, PL_TO_SQL3 — A family of conversion routines that translate PL/SQL data structures into SQL-accessible representations. The numeric suffixes denote overloaded or variant forms handling different data shapes or tiers of pricing payload.
  • SQL_TO_PL0, SQL_TO_PL1, SQL_TO_PL2, SQL_TO_PL3 — The inverse conversion family, moving SQL query results back into PL/SQL collections/records for internal pricing processing.
  • DPP_PRICING_PVT$NOTIFY_INBOUN — An inbound notification handler delegating to DPP_PRICING_PVT, used to process incoming pricing notifications routed through BPEL.

These routines form a symmetric marshalling layer, enabling the pricing engine to expose and consume data across SQL and PL/SQL boundaries typical of BPEL integration.

Tables Accessed

Per documented metadata, the package references a single table via APPS synonyms: PLITBLM. This table (a pricing-related interface/translation table) is used as the staging or mapping structure through which PL/SQL and SQL representations are correlated during conversion. It supports the PL_TO_SQL and SQL_TO_PL transformations by providing the row-based storage the SQL-facing routines require.

Usage Notes

DPP_BPEL_GETIPL is referenced by only itself in the documented dependency graph and is not referenced by other packages, indicating it is invoked as a leaf-level integration utility rather than a shared internal library. It depends on DPP_PRICING_PVT and its notification subprograms, tying it directly to the Oracle Pricing engine.

Typical invocation scenarios include: BPEL process callouts and inbound pricing notifications, pricing event publication flows, and custom extensions requiring conversion between PL/SQL pricing structures and SQL-queryable payloads. Because it manipulates pricing notification data, customizations should treat it as an integration boundary and avoid direct modification. In 12.2.2 it remains VALID and classified as OTHER, reflecting its role as supporting infrastructure rather than a public API. Developers should rely on documented procedures only and never assume parameter signatures beyond what ETRM exposes.