Search Results xdp_oe_order




Overview
Explore in AI Chat

Overview

XDP_OE_ORDER is a PL/SQL package owned by the APPS schema in Oracle E-Business Suite 12.1.1 and 12.2.2. It belongs to the Oracle Advanced Supply Chain Planning / Demand Planning family of utilities (the XDP prefix), and its function is to create and manage staged Oracle Order Management sales order records that originate from planning or demand-planning output rather than from standard order entry. In practice, the package provides a supported programmatic bridge between a planning-generated staging structure and the Order Management transactional tables, allowing planned supply or demand to be materialised as firm order headers and lines.

The package is classified as OTHER under the ETRM API classification scheme, meaning it is not a formally published public API and carries no documented interface contract or compatibility guarantee. Its metadata records it as VALID with an associated package body, and its dependency list confirms that it references the APPS.XDP_TYPES package specification. This dependency is the direct answer to the search term "xdp_types": XDP_TYPES supplies the shared PL/SQL record and collection type definitions used for passing order and line data into XDP_OE_ORDER. Because XDP_TYPES is compiled independently, XDP_OE_ORDER depends on it being valid and present in the APPS schema, and a compilation failure in XDP_TYPES will invalidate the dependent package.

Key Procedures and Functions

  • INSERT_OE_ORDER — Inserts the order header-level data into the staging structure, establishing the order identity used by subsequently inserted lines.
  • OE_ORDER_EXISTS — A check routine that determines whether a given order already exists in the staging or target structure, allowing callers to avoid duplicate inserts.
  • INSERT_OE_ORDER_LINE — Inserts order line detail rows associated with a previously created order, including the line-level attributes held in the staging tables.
  • SUBMIT_OE_ORDER — The final processing step that submits the staged order for processing, effectively handing the assembled header and line data to the order processing flow.

The four documented routines form a natural sequence: existence check, header insert, line insert, and submission. No parameter signatures are documented in the ETRM record and none are reproduced here.

Tables Accessed

The package operates against a set of dedicated staging tables accessed through APPS synonyms. XDP_OE_ORDER_HEADERS holds the order header records written by INSERT_OE_ORDER. XDP_OE_ORDER_LINES holds the corresponding order line records written by INSERT_OE_ORDER_LINE. XDP_OE_ORDER_LINE_DETS stores further line-level detail or attribute rows. XDP_OE_ORDER_PARAMETERS supplies control and configuration values that govern how the staging and submission logic behaves. DUAL is used for standard singleton SQL evaluation, and PLITBLM is the standard Oracle-supplied index-by table used for PL/SQL table-to-SQL passthrough. No other tables are documented as referenced.

Usage Notes

Because XDP_OE_ORDER is classified as OTHER and is not a published API, it is not intended for direct invocation by end users or by general custom development. It is normally called by the XDP planning components that own and populate the XDP_OE_ORDER_* staging tables, with those components supplying record structures typed by XDP_TYPES. The associated flow is typically driven from a planning or demand-planning responsibility rather than from the Order Management responsibility.

Given that ETRM records zero referencing packages, the package is effectively a terminal node reached from planning-side code or from a concurrent program that does not register as a package-level dependency. Custom development should not call these routines directly; the documented behavior may change without notice, and the staging tables are internal implementation artefacts. Any dependency on XDP_TYPES must be validated after patching, since that specification controls the data structures passed through this package.