Search Results sql_to_pl4

Overview

DPP_BPEL_SELCUSTCLAIM is an Oracle E-Business Suite PL/SQL package body owned by the APPS schema that supports the Distributed Process Planning (DPP) customer claims flow within Oracle's Advanced Planning and Demand Planning product family. Its primary business function is to bridge the impedance mismatch between PL/SQL record structures defined in the DPP_CUSTOMERCLAIMS_PVT package and the equivalent SQL object types that Oracle's Business Process Execution Language (BPEL) engine or Java-based middleware expects when exchanging data. This serialization/deserialization role is critical in distributed planning scenarios where claim and transaction data must traverse process boundaries between the EBS application tier and external planning providers.

Key Procedures and Functions

The package exposes eleven documented program units, organized as paired conversion functions that map between the PL/SQL record type DPP_CUSTOMERCLAIMS_PVT.DPP_CUST_HDR_REC_TYPE and its SQL object counterpart DPP_CUSTOMERCLAIMS_PVT_DPP_CU.

• PL_TO_SQL0, PL_TO_SQL1, PL_TO_SQL2, PL_TO_SQL3, PL_TO_SQL4 — These functions accept a PL/SQL customer claim header record and return a SQL object instance. Each variant follows the pattern shown in PL_TO_SQL1: the target object is initialized with NULL values, then each attribute (TRANSACTION_HEADER_ID, EFFECTIVE_START_DATE, EFFECTIVE_END_DATE, ORG_ID, EXECUTION_DETAIL_ID, OUTPUT_XML, PROVIDER_PROCESS_ID, PROVIDER_PROCESS_INSTANCE_ID, LAST_UPDATED_BY, CURRENCY_CODE) is copied field-by-field before return. The numeric suffix variants accommodate differing record shapes or call-site contexts.
• SQL_TO_PL0, SQL_TO_PL1, SQL_TO_PL2, SQL_TO_PL3, SQL_TO_PL4 — The inverse direction, accepting a SQL object and returning a populated PL/SQL record. SQL_TO_PL0 mirrors PL_TO_SQL1 exactly in its attribute assignments.
• DPP_CUSTOMERCLAIMS_PVT$SELECT — A generated selector function associated with the object type, used by Oracle's object-relational infrastructure to instantiate typed objects from stored or streamed data.

The "4" suffix, which is what the search term "pl_to_sql4" targets, corresponds to a specific record variant in the family, typically representing the deepest or most complete attribute set used by the claims selection process.

Tables Accessed

The only table referenced via APPS synonyms is PLITBLM. In EBS DPP, PLITBLM is a materialized view used to stage pending item or transaction changes for incremental planning. The package reads from PLITBLM to resolve claim header data during the selection phase, converting retrieved rows into PL/SQL records and then re-emitting them as SQL objects for downstream BPEL consumption. No direct DML against customer claims base tables is performed by this body — mutation is delegated to DPP_CUSTOMERCLAIMS_PVT.

Usage Notes

This package is not intended for direct invocation by end users or forms. It is called programmatically by the DPP customer claims selection workflow, typically during the "Select Customer Claims" step of a distributed planning cycle. The conversion functions are invoked whenever data must cross from a PL/SQL procedural context into a SQL/Java/BPEL context — for example, when the application constructs the payload for an outbound provider-process invocation or interprets an inbound response. Because it is referenced by zero other packages in the documented dependency graph, its consumers are external (BPEL process definitions, Java adapters, or the DPP engine itself). Developers extending or debugging customer-claim selection should treat this body as a stable serialization utility; modifications should preserve the field ordering and NULL-initialization contract to avoid breaking external type mapping.