Search Results oe_line_split_details_u1

Overview

The ONT.OE_LINE_SPLIT_DETAILS table is a transactional child table within the Oracle Order Management (ONT) schema. It stores audit and quantity information for every order line that participates in a line-splitting operation in Oracle E-Business Suite. When a user or concurrent program splits a model line or an ordered line, one row is written per resulting split segment, capturing the quantities, shipping organizations, request context, and change-reason metadata associated with that split. Oracle EBS 12.1.1 and 12.2.2 expose this table under the same ONT schema and FND design data object (ONT.OE_LINE_SPLIT_DETAILS), and it resides in the APPS_TS_TX_DATA tablespace.

From a Data Vault modeling perspective, the table is heuristically classified as standalone. It carries no foreign-key references outward, meaning it behaves less like a link or hub in a normalized vault model and more like a standalone satellite or event/audit record keyed by the business transaction it describes. Analysts building a Data Vault or dimensional model should treat it as a split-event satellite whose grain is one row per split segment per model line.

Key Information Stored

The documented physical schema contains eleven columns. The most significant are grouped below.

• LINE_ID and SPLIT_INDEX — quoted from the primary key in the metadata, together these form the unique key of a split segment. LINE_ID stores the top model line id of the model being split, while SPLIT_INDEX is the index of the line being split.
• REQUEST_ID — the concurrent request that performed the split.
• ORDERED_QUANTITY and ORDERED_QUANTITY2 — the ordered quantity and the secondary ordered quantity for the split line.
• SHIP_TO_ORG_ID and SHIP_FROM_ORG_ID — the receiving and shipping inventory organizations for the split segment.
• REQUEST_DATE — the date the split line was requested.
• SPLIT_BY — a VARCHAR2(30) code identifying the action or actor that performed the split.
• CHANGE_REASON_CODE and CHANGE_REASON_COMMENT — the reason code and free-text comment (up to 2000 characters) explaining the change.

The unique index OE_LINE_SPLIT_DETAILS_U1 on (LINE_ID, SPLIT_INDEX) is the primary business-key candidate and mirrors the modeled primary key, making the pair suitable as the natural key for lookups and deduplication. A secondary index named OE_LINE_SPLIT_DETAILS# also exists, referenced by ONT in the dependency data.

Common Use Cases and Queries

Typical scenarios include auditing split history for a model line, reconciling split quantities against ordered quantities, tracing splits back to a concurrent request, and reporting change-reason usage for governance purposes.

A standard lookup by top model line retrieves every split segment for that line:

• SELECT LINE_ID, SPLIT_INDEX, ORDERED_QUANTITY, ORDERED_QUANTITY2, SHIP_TO_ORG_ID, SHIP_FROM_ORG_ID FROM ONT.OE_LINE_SPLIT_DETAILS WHERE LINE_ID = :line_id ORDER BY SPLIT_INDEX;

To audit a specific concurrent request, filter on REQUEST_ID and REQUEST_DATE. To analyze split reasons, aggregate by CHANGE_REASON_CODE. Because the table is standalone with no outgoing foreign keys, joins to order headers or fulfillment tables must be inferred through LINE_ID against the appropriate order line tables rather than declared constraints.

Related Objects

The documented dependency metadata shows that ONT.OE_LINE_SPLIT_DETAILS does not reference any database object. It is referenced only by the internal synonym-like object ONT.OE_LINE_SPLIT_DETAILS#, which is the underlying base object in the dependency chain. Practically, reports join OE_LINE_SPLIT_DETAILS to OE_ORDER_LINES_ALL and OE_ORDER_HEADERS_ALL on LINE_ID/HEADER_ID to resolve order context, to FND_CONCURRENT_REQUESTS on REQUEST_ID to identify the submitting program, and to MTL_PARAMETERS on SHIP_TO_ORG_ID and SHIP_FROM_ORG_ID to resolve organization names. The change-reason columns align with the Order Management change-reason setup used elsewhere in the ONT schema.