Search Results xdp_engine




Overview
Explore in AI Chat

Overview

XDP_ENGINE is the core runtime engine package body within the Oracle E-Business Suite fulfillment and order-management framework delivered by the XDP (eXtended Data Processing) product family. It resides in the APPS schema and holds a VALID status, indicating that it compiles and functions within the supported EBS 12.1.1 and 12.2.2 environments. The package orchestrates the execution of fulfillment actions, workitems, and order-level processing by resolving, storing, and retrieving runtime parameter values that drive configurable business logic. It acts as the central hub through which order headers, line items, fulfillment actions, and feature/attribute configurations are interrogated and manipulated at runtime. Because the package body is not referenced by any other database object, it is consumed internally by the XDP subsystem and by dependent packages rather than being exposed as a directly callable API surface for external callers.

Key Procedures and Functions

The package body exposes forty-seven documented procedures and functions, organized around several parameter-management families. The workitem parameter family includes GET_WORKITEM_PARAM_VALUE, GET_WORKITEM_PARAM_REF_VALUE, GET_WORKITEM_PARAM_LIST, and SET_WORKITEM_PARAM_VALUE, which read and write runtime values associated with fulfillment workitems. The provisioning-date functions GET_WORKITEM_PROV_DATE and SET_WORKITEM_PROV_DATE manage scheduled provisioning timestamps for workitems.

The fulfillment-action parameter family comprises GET_FA_PARAM_VALUE, GET_FA_PARAM_REF_VALUE, GET_FA_PARAM, GET_FA_PARAM_LIST, and SET_FA_PARAM_VALUE, providing getter and setter access to fulfillment action parameters. Order-level access is provided by GET_ORDER_PARAM_VALUE, GET_ORDER_PARAM_LIST, and SET_ORDER_PARAM_VALUE. Line-level access is handled by GET_LINE_PARAM_VALUE, GET_LINE_PARAM_REF_VALUE, ADD_LINE_PARAM, and SET_LINE_PARAM_VALUE. Finally, configuration and attribute retrieval are served by GET_FE_CONFIGINFO and GET_FE_ATTRIBUTEVAL, which expose feature/attribute configuration metadata and values.

Tables Accessed

XDP_ENGINE reads and writes through APPS synonyms against the XDP transaction and configuration tables. Order structure is maintained in XDP_ORDER_HEADERS, XDP_ORDER_LINE_ITEMS, and XDP_ORDER_LINEITEM_DETS, which anchor order and line parameter operations. Fulfillment execution data is stored in XDP_FULFILL_ACTIONS, XDP_FULFILL_WORKLIST, XDP_WORKITEMS, XDP_WORKLIST_DETAILS, and XDP_WI_PARAMETERS, supporting the workitem and fulfillment action procedures. Parameter definition and runtime resolution leverage XDP_FA_PARAMETERS, XDP_FA_RUNTIME_LIST, XDP_FA_DETAILS, and XDP_ORDER_PARAMETERS. Feature/attribute processing draws on XDP_FES, XDP_FE_ATTRIBUTE_DEF, XDP_FE_ATTRIBUTE_VAL, XDP_FE_CMD_AUD_TRAILS, XDP_FE_GENERIC_CONFIG, XDP_FE_SW_GEN_LOOKUP, and XDP_FE_TYPES. The package also depends on utility and infrastructure packages including FND_GLOBAL, FND_MESSAGE, APP_EXCEPTION, XDPCORE, XDPCORE_FA, XDPCORE_WI, XDP_CRYPT_TOOLS, XDP_ERRORS_PKG, XDP_TYPES, XDP_UTILITIES, XNP_TIMER_CORE, and XNP_WF_SYNC.

Usage Notes

XDP_ENGINE is typically invoked indirectly rather than through direct end-user calls. It is referenced by twenty-one other packages within the XDP framework, meaning its procedures are called during fulfillment processing flows, workitem state transitions, and attribute resolution triggered by forms, concurrent programs, or workflow activities. Customizations that need to read or set order, line, fulfillment action, or workitem parameter values should call the appropriate GET_* and SET_* procedures rather than accessing the underlying XDP tables directly, preserving encapsulation and audit behavior. Because the package relies on FND_GLOBAL for session context, it must be invoked within an initialized EBS application session. Developers extending the framework should account for its dependencies on XDPCORE and the XNP synchronization packages when diagnosing runtime errors.