Results for “xdp_oe_order_lines_u1”

AI-generated from documented ETRM metadata — verify critical details on the linked pages.

Overview

XDP.XDP_OE_ORDER_LINES is a standard Oracle E-Business Suite table owned by the XDP schema that stores all order line information for orders generated through the SFM (Service Fulfillment Manager) Order Entry interface. It is part of the Oracle Communications / ETRM (Enterprise Telecommunications Resource Management) data model, which is used extensively in telecommunications and subscription-based order fulfillment environments. Each row in this table represents a single line within an order, capturing the item being ordered, its version, its provisioning requirements, and the full lifecycle of fulfillment dates and statuses associated with that line.

From a Data Vault modeling perspective, the mined heuristic classification for this table is satellite-leaning. This suggests it primarily describes attributes and descriptive context of an underlying business key rather than acting as a pure hub or link. The business key is composed of ORDER_NUMBER, ORDER_VERSION, and LINE_NUMBER, which together uniquely identify a line within an order at a specific version. This structure aligns with a satellite attached to an order-line hub, where the composite key drives the descriptive payload.

Key Information Stored

The table contains 27 documented columns. The most significant of these are grouped below by function.

• Business key columns: ORDER_NUMBER (VARCHAR2 40), ORDER_VERSION (VARCHAR2 40), and LINE_NUMBER (NUMBER) form the unique index XDP_OE_ORDER_LINES_U1. These three columns together distinguish each line record and are the primary join keys to surrounding objects.
• Line item identification: LINE_ITEM_NAME, LINE_ITEM_VERSION, LINE_ITEM_TYPE, and LINE_ITEM_ACTION describe what is being ordered and what operation is being performed on it.
• Provisioning and fulfillment: PROVISIONING_REQUIRED_FLAG, IS_WORKITEM_FLAG, PROVISIONING_SEQUENCE, PRIORITY, and PROVISIONING_DATE control and sequence the fulfillment process.
• Status and dates: STATUS, DUE_DATE, CUSTOMER_REQUIRED_DATE, and COMPLETION_DATE provide the operational timeline and current state of the line.
• Bundling and jeopardy: BUNDLE_ID, BUNDLE_SEQUENCE, and JEOPARDY_ENABLED_FLAG support bundled order handling and risk monitoring.
• Number ranges: STARTING_NUMBER and ENDING_NUMBER are typically used for range-based or serialized provisioning.
• Standard WHO columns: CREATION_DATE, LAST_UPDATE_DATE, LAST_UPDATED_BY, CREATED_BY, LAST_UPDATE_LOGIN, and SECURITY_GROUP_ID support auditing and hosted-environment security.

There is no single surrogate primary key column; the unique index XDP_OE_ORDER_LINES_U1 acts as the business-key candidate. The foreign keys reference XDP_OE_ORDER_HEADERS via ORDER_NUMBER and FND_SECURITY_GROUPS via SECURITY_GROUP_ID.

Common Use Cases and Queries

Typical use cases include fulfillment tracking, provisioning workload reporting, jeopardy monitoring, and order-line detail extraction for downstream interfaces.

• Order line detail for a specific order: SELECT * FROM XDP.XDP_OE_ORDER_LINES WHERE ORDER_NUMBER = :p_order AND ORDER_VERSION = :p_version ORDER BY LINE_NUMBER;
• Lines requiring provisioning: SELECT ORDER_NUMBER, LINE_NUMBER, PROVISIONING_DATE, STATUS FROM XDP.XDP_OE_ORDER_LINES WHERE PROVISIONING_REQUIRED_FLAG = 'Y' AND STATUS <> 'COMPLETE';
• Jeopardy monitoring: SELECT ORDER_NUMBER, LINE_NUMBER, DUE_DATE, CUSTOMER_REQUIRED_DATE FROM XDP.XDP_OE_ORDER_LINES WHERE JEOPARDY_ENABLED_FLAG = 'Y' AND DUE_DATE < SYSDATE;
• Bundle-level aggregation: SELECT BUNDLE_ID, COUNT(*) FROM XDP.XDP_OE_ORDER_LINES GROUP BY BUNDLE_ID;
• Performance reporting on completion: compare COMPLETION_DATE against CUSTOMER_REQUIRED_DATE to measure fulfillment timeliness.

Because the table resides in the APPS_TS_ARCHIVE tablespace, queries often benefit from date-range predicates to limit scan volume in production reporting.

Related Objects

The following objects are most significant in relation to XDP_OE_ORDER_LINES:

• XDP_OE_ORDER_HEADERS — referenced via ORDER_NUMBER; the header record for each order.
• XDP_OE_ORDER_LINE_DETS — references XDP_OE_ORDER_LINES via ORDER_NUMBER and typically holds finer-grained line detail.
• FND_SECURITY_GROUPS — referenced via SECURITY_GROUP_ID for hosted-environment row-level security.
• SFM Order Entry interface objects — populate XDP_OE_ORDER_LINES during order import.
• Provisioning and fulfillment processing objects — consume PROVISIONING_SEQUENCE, PRIORITY, and DUE_DATE for downstream activation.

When the object is queried as xdp_oe_order_lines_u1, the reference points specifically to the unique index that enforces the composite business key, which is the recommended access path for single-line lookups.