Search Results xdp_proc_ctl




Overview
Explore in AI Chat

Overview

XDP_PROC_CTL is an APPS-owned PL/SQL package body within the Oracle E-Business Suite communications infrastructure maintained by the ETRM (E-Business Suite Technology Reference Model) layer. In Oracle EBS 12.1.1 and 12.2.2, the package functions as a process control and message handling utility for outbound and inbound integration traffic. Rather than implementing a business transaction such as order entry or invoicing, XDP_PROC_CTL provides the internal machinery used by the XDP adapter and engine stack to construct, parameterize, dispatch, transmit, and audit messages exchanged between EBS and external systems, including HTTP-based endpoints.

The package is documented with a status of VALID and is classified as OTHER in the ETRM metadata. It does not reference business entity tables directly; instead it relies on configuration and audit tables within the XDP schema family, along with several Oracle-supplied PL/SQL packages. The package body is not referenced by any database object, which confirms it serves as a top-level driver invoked at runtime rather than a reusable library consumed by other PL/SQL units.

Key Procedures and Functions

The documented 30 procedures and functions cluster around parameter resolution, message generation, transport, and audit. Representative members include:

Tables Accessed

XDP_PROC_CTL reads and writes several documented configuration and audit tables through APPS synonyms:

It also depends on Oracle-supplied packages including DBMS_LOB, DBMS_PIPE, DBMS_SQL, UTL_HTTP, FND_MESSAGE, FND_PROFILE, FND_GLOBAL, CSI_LOOKUPS, and the XDP_ADAPTER and XDP_ENGINE families.

Usage Notes

XDP_PROC_CTL is invoked at runtime by the XDP engine and adapter layer when outgoing messages must be built and transmitted, or when responses must be awaited and audited. It is typically reached indirectly through concurrent programs, forms-driven integrations, or adapter configuration rather than being called directly by end users. Custom development should avoid direct calls; instead, integration should flow through XDP_ADAPTER and XDP_ENGINE, which manage the parameter, channel, and audit context that XDP_PROC_CTL expects. As with all APPS-owned packages, modifications are unsupported and should be limited to configuration changes in the underlying XDP tables.