Search Results xdp_order




Overview
Explore in AI Chat

Overview

XDP_ORDER is an Oracle E-Business Suite PL/SQL package owned by the APPS schema that forms part of the Oracle Advanced Supply Chain Planning / Distributed Order Orchestration (DOO) fulfillment infrastructure. In release 12.1.1 and 12.2.2 it is classified as an "OTHER" API, meaning it is not a public, declaratively registered interface but an internal processing engine invoked by higher-level components. Its core responsibility is the manipulation and processing of fulfillment order data held in the XDP family of tables — the order headers, line items, line item details, and worklist records that drive order fulfillment within the orchestration model. The package bridges raw order capture data with the fulfillment worklist, applying business validation, parameter resolution, and item/customer defaulting derived from standard EBS master data. The ETRM metadata records the package as VALID in the APPS schema, confirming it is a supported, compiled object in the current instance.

Key Procedures and Functions

The documented package exposes a single program unit entry: PROCESS_ORDER. This procedure serves as the primary entry point for order-level processing. Based on its name and the package's dependency footprint, it is responsible for accepting order context, resolving fulfillment parameters, validating the order against customer and item master data, and writing or updating the corresponding fulfillment records. It is the orchestrating routine that other XDP components call when an order must be processed through the fulfillment pipeline. No parameter list is documented in the ETRM metadata; consultants should inspect the package specification in the database for the exact signature. The package as a whole depends on XDP_TYPES for its record and collection type definitions and on FND_API, indicating that PROCESS_ORDER follows Oracle's standard API error-handling and message-stack conventions (for example, returning a global success or failure status rather than raising uncontrolled exceptions).

Tables Accessed

The package reads and writes the XDP fulfillment schema tables plus several standard EBS master tables referenced through APPS synonyms:

Usage Notes

XDP_ORDER is not intended for direct invocation by end users or external custom code. It is referenced by the following packages: XDP_AQ_UTILITIES, XDP_INTERFACES, XDP_INTERFACES_PUB, and XNP_CORE (with XDP_ORDER also appearing as a self-reference, common for package-body internal calls). These callers are the inbound interface and advanced-queue processing layers that receive order messages and hand them to XDP_ORDER for fulfillment preparation. In practice the package is therefore triggered indirectly through the Distributed Order Orchestration / fulfillment concurrent programs and interface processing rather than from an Oracle Forms block or a standalone concurrent program. Custom developers integrating with this area should call the public wrapper XDP_INTERFACES_PUB rather than PROCESS_ORDER directly, to preserve supported upgrade paths. Because it relies on FND_API, callers should always check the returned API status, and debugging should focus on the XDP order tables and the fulfillment worklist, since these are the persistent artifacts produced by the package.