Search Results xdp_order_sync




Overview
Explore in AI Chat

Overview

XDP_ORDER_SYNC is a PL/SQL package owned by the APPS schema that forms part of the Oracle E-Business Suite fulfillment and order orchestration infrastructure. It belongs to the XDP (fulfillment/order processing) module family and is classified under the ETRM API classification of "OTHER," indicating that it is an internal utility package rather than a formally published public API. The package is primarily responsible for synchronizing order-related data across the fulfillment engine, coordinating order headers and line items with workitems, worklists, and fulfillment actions. In practice, XDP_ORDER_SYNC acts as a bridge between the order capture structures (XDP_ORDER_HEADERS and XDP_ORDER_LINE_ITEMS) and the runtime fulfillment tables that drive downstream processing, such as XDP_FULFILL_WORKLIST, XDP_WORKITEMS, and XDP_FULFILL_ACTIONS. The package is validated and present in both Oracle EBS 12.1.1 and 12.2.2 environments, where the underlying data model is largely consistent. Its single documented entry point, EXECUTE_ORDER_SYNC, provides a controlled mechanism for propagating order state changes through the fulfillment pipeline.

Key Procedures and Functions

The ETRM metadata documents one procedure within this package:

  • EXECUTE_ORDER_SYNC — the sole documented program unit. This procedure serves as the main driver for the order synchronization process. Its purpose is to reconcile order records with the fulfillment runtime structures, moving or updating data across the order header, line item, workitem, worklist, and fulfillment action tables so that the fulfillment engine reflects the current state of the order. Because the ETRM documentation does not enumerate a parameter list, the specific arguments are not reproduced here; callers should treat it as the primary invocation point of the package.

Tables Accessed

The package reads from and writes to a set of XDP tables accessed through APPS synonyms. The documented tables and their roles are as follows:

  • XDP_ORDER_HEADERS / XDP_ORDER_LINE_ITEMS — the order source structures supplying header and line data to be synchronized.
  • XDP_FULFILL_WORKLIST / XDP_WORKITEMS — the fulfillment worklist and workitem queues that receive synchronized order activity.
  • XDP_FULFILL_ACTIONS — records the fulfillment actions generated or updated by the synchronization process.
  • XDP_ADAPTER_REG / XDP_FA_RUNTIME_LIST / XDP_FA_FULFILLMENT_PROC — adapter registration and runtime fulfillment process definitions used to route work to the correct handler.
  • XDP_FE_SW_GEN_LOOKUP — the lookup table supplying fulfillment engine software generation/configuration values.
  • XDP_WI_FA_MAPPING — the mapping between workitems and fulfillment actions used to resolve processing relationships.
  • DUAL — used for single-row computations and control checks.

Usage Notes

XDP_ORDER_SYNC is an internal package and is not intended for direct invocation by end users. It is typically called from within the XDP_ORDER and XDP_ORDER_SYNC package family itself (the package body references and is referenced by these units) as part of order and fulfillment processing flows. In the context of EBS fulfillment, such synchronization logic is commonly triggered when fulfillment actions are created, when workitems are released, or when orders progress through their lifecycle stages. Because no concurrent program or form is documented as a direct caller in the ETRM metadata, the most reliable integration point for custom code is an indirect one: developers should generally invoke the higher-level XDP_ORDER package or the fulfillment engine's own APIs rather than calling EXECUTE_ORDER_SYNC directly. Where direct calls are necessary, they should be made within the same transaction context as the order change that necessitates synchronization, and the calling transaction should be committed only after the synchronization completes successfully to preserve data consistency across the order and fulfillment tables.