Search Results xdp_interfaces_pub




Overview
Explore in AI Chat

Overview

XDP_INTERFACES_PUB is the public PL/SQL interface package for the Oracle E-Business Suite order orchestration and fulfillment engine (formerly known as the Oracle Order Capture / Distributed Order Processing framework and now positioned within the Order Management fulfillment stack). It resides in the APPS schema and is classified as a PUB (public) API, indicating that it is designed for supported, external invocation by other application modules and custom code rather than for internal use only.

The package exposes a stable, versioned entry point through which calling programs submit, query, and cancel orders processed by the XDP engine. It abstracts the underlying XDP_ENGINE processing logic, presenting a controlled facade that shields callers from internal engine complexity. The dependency metadata confirms that XDP_INTERFACES_PUB depends on FND_API (for the standard EBS API error-handling and message framework), XDP_ENGINE, and XDP_TYPES, and that it is itself referenced by several packages including XDPCORE_OM, XDP_CANCEL_ORDER, XDP_INTERFACES_PUB_W, and XDP_PERF_BM_PKG.

Key Procedures and Functions

The ETRM metadata documents nine procedures and functions within this package. The principal public entry points include:

  • PROCESS_ORDER — Submits an order to the XDP engine for processing. This is the primary interface used by external callers to hand an order into the orchestration and fulfillment pipeline.
  • CANCEL_ORDER — Requests cancellation of an order already submitted to the engine, allowing callers to reverse or halt fulfillment activity.
  • GET_ORDER_PARAMETER_LIST — Retrieves the list of parameters defined for a given order, enabling callers to enumerate the configurable inputs associated with an order.
  • GET_ORDER_PARAMETER_VALUE — Returns the value of a specific order-level parameter, supporting targeted lookups without retrieving the full parameter set.
  • GET_LINE_PARAMETER_VALUE — Returns the value of a parameter at the order-line level, enabling line-specific configuration to be inspected.
  • GET_ORDER_DETAILS — Retrieves detailed information about an order processed by the engine, serving as the primary read-back function for order state and content.
  • GET_ORDER_STATUS — Returns the current processing status of an order, allowing callers to poll or verify the outcome of submission.

The remaining documented procedures follow the same pattern of parameter retrieval and order interrogation. Because the metadata does not disclose individual parameter signatures, callers should consult the package specification directly for exact argument lists and return types.

Tables Accessed

The documented table reference for this package is PLITBLM, accessed through an APPS synonym. PLITBLM is an internal engine table used by the order processing framework for staging and tracking order data during orchestration. The package primarily operates against the logical structures defined in XDP_TYPES and delegates most persistent read/write activity to XDP_ENGINE, meaning direct table access from this interface layer is deliberately limited. This design isolates callers from the underlying schema and preserves the integrity of engine-managed data.

Usage Notes

XDP_INTERFACES_PUB is typically invoked from Order Management forms, concurrent programs, and custom integration code that needs to submit or interrogate orders in the XDP engine. Because it is a PUB API, it should be called directly rather than through the wrapper packages (XDP_INTERFACES_PUB_W, XDPCORE_OM) that themselves depend on it. Callers should observe the standard EBS API conventions — checking the return status and inspecting the FND_API message stack for errors — before proceeding. The GET_* functions are appropriate for confirmations and status polling, while PROCESS_ORDER and CANCEL_ORDER constitute the mutating operations.