Search Results xdp_oe_order_parameters




Overview
Explore in AI Chat

Overview

The XDP_OE_ORDER_PARAMETERS table is a Provisioning (XDP) module data object in Oracle E-Business Suite 12.1.1 and 12.2.2. It stores the individual order parameters associated with an order that is generated through the SFM - Order Entry interface. In practical terms, this table functions as a child detail store that decomposes an order header into a set of named name/value pairs, allowing the provisioning process to persist flexible, order-level attributes without requiring a distinct column for every possible attribute.

The object resides in the XDP schema and is documented as VALID in ETRM. Its documented physical schema records ten columns. Based on the foreign-key structure mined from the metadata, the table is classified heuristically as satellite-leaning in Data Vault terms. This classification is a modeling suggestion: the table behaves as a descriptive satellite attached to an order header hub, rather than as an independent hub or a many-to-many link, because its grain is defined by the parent order identity plus a parameter name.

Key Information Stored

The table's uniqueness is enforced by the unique index XDP_OE_ORDER_PARAMETERS_U1 on the combination of ORDER_NUMBER, ORDER_VERSION, and PARAMETER_NAME. The same three columns form the documented primary key, XDP_OE_ORDER_PARAMETERS_UK. No separate surrogate key column is documented; the business-key candidate serves directly as the primary key.

  • ORDER_NUMBER — Identifies the order to which the parameter belongs. This column participates in the foreign key to XDP_OE_ORDER_HEADERS and is part of the primary key.
  • ORDER_VERSION — Distinguishes between versions of the same order number, enabling versioned parameter sets. It is part of the primary key and the foreign key to XDP_OE_ORDER_HEADERS.
  • PARAMETER_NAME — The name of the individual parameter. It completes the primary key, so each order version may hold at most one row per parameter name.
  • PARAMETER_VALUE — The value assigned to the named parameter for that order and version.
  • SECURITY_GROUP_ID — Supports security grouping and references FND_SECURITY_GROUPS.
  • CREATION_DATE — The date the parameter row was created.
  • CREATED_BY — The user who created the parameter row.
  • LAST_UPDATE_DATE — The date of the most recent change to the row.
  • LAST_UPDATED_BY — The user who last updated the row.
  • LAST_UPDATE_LOGIN — The login context associated with the last update.

Common Use Cases and Queries

The table is principally queried to retrieve the full parameter set for a given order and version, or to find orders that carry a specific parameter value. A typical retrieval joins the parameter table to the order header:

  • Retrieve all parameters for an order: SELECT parameter_name, parameter_value FROM xdp.xdp_oe_order_parameters WHERE order_number = :p_order AND order_version = :p_version;
  • Search by parameter value: SELECT order_number, order_version, parameter_value FROM xdp.xdp_oe_order_parameters WHERE parameter_name = :p_name AND parameter_value = :p_value;
  • Join to headers for context: SELECT h.order_number, p.parameter_name, p.parameter_value FROM xdp_oe_order_parameters p JOIN xdp_oe_order_headers h ON p.order_number = h.order_number AND p.order_version = h.order_version;
  • Reporting scenarios include auditing provisioned order attributes, comparing parameter values across order versions, and validating that required parameters were supplied by the SFM - Order Entry interface.

Related Objects

  • XDP_OE_ORDER_HEADERS — The parent order header table. Joined via ORDER_NUMBER and ORDER_VERSION; the documented foreign key links both columns.
  • FND_SECURITY_GROUPS — Referenced by SECURITY_GROUP_ID to enforce security group filtering.

The parameter table depends on XDP_OE_ORDER_HEADERS as its parent and is populated as part of the SFM - Order Entry interface flow, so downstream provisioning and order-entry components that consume order headers typically read parameters through this relationship rather than querying the table in isolation.