Search Results order_provisioning_date




Overview
Explore in AI Chat

Overview

APPS.XDP_OE_ORDER_DETAILS_V is a reporting and integration view in Oracle E-Business Suite that consolidates order header and order line information from the Oracle Communications / ETRM (Enterprise Telecommunications Resource Management) order capture schema. The view joins the header-level table XDP_OE_ORDER_HEADERS with the line-level table XDP_OE_ORDER_LINES, presenting a flattened, denormalized result set where each row represents a single order line enriched with its parent order attributes. Because the view is owned by APPS and defined over public synonyms, it is accessible to reporting tools, concurrent programs, and external integrations without requiring direct grants on the underlying XDP tables.

The view is particularly relevant to provisioning workflows. The user search term line_provisioning_date maps to the column LINE_PROVISIONING_DATE, which the view derives from XOEL.PROVISIONING_DATE (the line record in XDP_OE_ORDER_LINES). The corresponding order-level value is exposed as ORDER_PROVISIONING_DATE, sourced from XOEH.PROVISIONING_DATE. This separation allows consumers to distinguish when the order as a whole was provisioned from when the individual line item was provisioned — a critical distinction in telecommunications order fulfillment, where multi-line orders may be provisioned incrementally.

Underlying Base Objects

The ETRM documentation for release 12.2.2 identifies exactly two referenced base objects, both exposed as synonyms:

The join is performed on ORDER_NUMBER and, importantly, on a version-safe comparison: NVL(XOEH.ORDER_VERSION,'X') = NVL(XOEL.ORDER_VERSION,'X'). The NVL wrapping ensures that rows with a NULL order version on either side still match, which is essential in ETRM because versioned orders may carry NULL versions during certain lifecycle stages. The 12.1.1 and 12.2.2 column sets are consistent with this definition.

Key Columns

Common Use Cases and Queries

Typical scenarios include provisioning status dashboards, SLA monitoring, and integration extracts. A representative query for lines provisioned in a period:

  • SELECT order_number, line_number, line_provisioning_date, line_status FROM apps.xdp_oe_order_details_v WHERE line_provisioning_date >= :start_date AND org_id = :org_id;
  • Find lines with provisioning required but no provisioning date: SELECT order_number, line_number FROM apps.xdp_oe_order_details_v WHERE provisioning_required_flag = 'Y' AND line_provisioning_date IS NULL;
  • Compare order vs. line provisioning dates to detect incremental provisioning: SELECT order_number, order_provisioning_date, line_number, line_provisioning_date FROM apps.xdp_oe_order_details_v WHERE order_provisioning_date <> line_provisioning_date;

Because the view is read-only and built on version-aware joins, it is safe for concurrent reporting but should be filtered by ORG_ID in multi-org environments to respect data security.