Search Results xdp_utilities




Overview
Explore in AI Chat

Overview

XDP_UTILITIES is a foundational PL/SQL package body in the APPS schema that supports the Oracle E-Business Suite's provisioning and fulfillment infrastructure, commonly referred to as the XDP (eXtended Data Provisioning) family of objects. Within EBS 12.1.1 and 12.2.2, this package functions primarily as a dynamic PL/SQL execution and procedure-management utility layer. Rather than implementing a single business transaction, XDP_UTILITIES provides generic services—dynamic SQL execution, dynamic package construction, procedure introspection, and workflow invocation—that other XDP packages invoke at runtime. Its classification as OTHER reflects that it is an internal technical utility rather than a public, user-facing API.

The package is reported as VALID and is referenced by 21 other database objects, confirming its role as a shared dependency across the fulfillment engine and worklist processing modules. Its dependency footprint includes both XDP-specific objects (XDPCORE, XDP_TYPES, XDP_PROCEDURE_UTIL, XDP_PROCEDURE_BUILDER, XDP_FES) and standard EBS infrastructure (FND_FILE, FND_GLOBAL, FND_MESSAGE, FND_PROFILE, WF_CORE, WF_ENGINE, DBMS_SQL, DBMS_LOB).

Key Procedures and Functions

The ETRM documentation records 48 procedures and functions within this package body. Documented members include:

  • CALLWIPARAMEVALPROC, CALLFAPARAMEVALPROC, CALLFAEVALALLPROC — invoke parameter-evaluation and evaluation-all routines used when the fulfillment engine resolves configuration parameters for Workflow Item (WI) and Fulfillment Agent (FA) processing.
  • CALLFEROUTINGPROC, CALLFULFILLMENTPROC, CALLFAMAPPROC, CALLWIMAPPROC — dynamically call routing, fulfillment, and mapping procedures during fulfillment execution.
  • CALLWIWORKFLOWPROC, CALLDRCTASKRESULTPROC — dispatch Workflow process calls and Direct Task result handlers.
  • CALL_NECONNECTION_PROC — invokes a Network Element connection procedure.
  • CREATE_NEW_PROC_BODY, UPDATE_PROC_BODY, CREATE_PKG_SPEC, CREATE_PKG_BODY — construct and modify PL/SQL procedure bodies and package specifications/bodies dynamically, enabling the engine to generate executable code at runtime.
  • GET_CLOB_VALUE — retrieves CLOB content, leveraging DBMS_LOB for large object handling.
  • EXECUTE_GETID_QUERY — executes a dynamically constructed query to obtain an identifier value.
  • RUNPROC, DESCRIBEPROC, PRINTPARAMS — execute a named procedure dynamically, describe its signature, and print its parameters for diagnostic or metadata purposes.
  • DO_COMMIT — performs a database commit, used to persist results at controlled points in dynamic execution flows.

Tables Accessed

The package reads and writes several application tables, largely through APPS synonyms. Configuration and audit tables include XDP_FE_GENERIC_CONFIG, XDP_FE_SW_GEN_LOOKUP, and XDP_FE_CMD_AUD_TRAILS, which store fulfillment engine configuration, lookup values, and command audit trail records. Fulfillment and worklist tables include XDP_FA_FULFILLMENT_PROC, XDP_FULFILL_WORKLIST, XDP_ORDER_LINE_ITEMS, XDP_ORDER_LINEITEM_DETS, XDP_WORKITEMS, and XDP_WORKLIST_DETAILS. Workflow integration tables include XDP_WF_PROCESS_COORD, XDP_WF_COORDINATION_ID_S, and the WF_ITEM_ATTRIBUTE_VALUES view. XDP_PROC_BODY and XDP_FES support dynamically generated procedure storage and fulfillment engine state. FND_RESPONSIBILITY is referenced for responsibility context resolution. DUAL is used for scalar queries.

Usage Notes

XDP_UTILITIES is not intended for direct end-user invocation. It is called programmatically by the XDP fulfillment engine and associated worklist processes during runtime execution, and it is invoked when dynamic procedure construction or execution is required. Because the package relies on DBMS_SQL and dynamic code generation, it operates with the privileges of the calling APPS session and should be invoked only within supported fulfillment flows. Customizations extending the XDP framework may call the documented utility routines, but direct modification of this package is not supported and would be overwritten by patching. The package is reported as not referenced by any higher-level database object (beyond its PL/SQL callers), reinforcing its position as a low-level internal utility.