Results for “ordered_quantity”

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

Overview

OE_LINE_SPLIT_DETAILS is an Order Management (ONT) transactional table in the Oracle E-Business Suite 12.1.1 and 12.2.2 environments. It is owned by the ONT schema and holds information about every order line that is subject to a split operation. The table records the outcome of order line splitting activities, capturing which line was split, the resulting split sequence, the requested quantities, the source and destination organizations involved, and the reason the split was initiated.

Line splitting occurs when a single ordered line must be divided into multiple subordinate lines — for example, to satisfy availability from more than one shipping warehouse, to separate quantities by requested ship date, or to isolate backordered portions of a demand. OE_LINE_SPLIT_DETAILS preserves the audit trail of those operations and supports queries that reconstruct how an original line was decomposed. The table is populated during split processing, typically driven by concurrent request identifiers, and is referenced by Order Management forms and concurrent programs.

From a data-modeling perspective, the ETRM metadata classifies this object heuristically as standalone under a Data Vault classification scheme. No foreign-key dependencies were mined from the documented structure, meaning the table functions as an independent record of split events rather than a dependent child or a junction between persistent hubs. This should be treated as a modeling suggestion rather than a definitive Data Vault designation.

Key Information Stored

The table is documented with eleven physical columns. Its primary key, named TABLE1_PK, is a composite of LINE_ID and SPLIT_INDEX. A unique index, OE_LINE_SPLIT_DETAILS_U1, covers the same two columns, confirming the business-key combination of the line identifier and the split sequence number.

• LINE_ID — surrogate/foreign reference to the order line being split; part of the composite primary key and the business-key candidate.
• SPLIT_INDEX — sequence number identifying each resulting split of the line; part of the composite primary key and the business-key candidate.
• REQUEST_ID — the concurrent request that executed the split, enabling traceability to the program run.
• ORDERED_QUANTITY — the primary quantity associated with the split line.
• ORDERED_QUANTITY2 — the secondary ordered quantity, used where dual-unit-of-measure tracking applies.
• REQUEST_DATE — the date the split was requested, used for chronological reporting.
• SHIP_TO_ORG_ID — the ship-to organization assigned to the split line.
• SHIP_FROM_ORG_ID — the ship-from (warehouse) organization supplying the split quantity.
• SPLIT_BY — indicates the criterion or mechanism by which the split was performed.
• CHANGE_REASON_CODE — the code describing the reason recorded for the split.
• CHANGE_REASON_COMMENT — free-text comment accompanying the change reason.

Common Use Cases and Queries

Typical reporting scenarios include reconstructing the split history of a specific order line, auditing which warehouse fulfilled each portion of a split, and reviewing quantities by request date. A common query retrieves all splits for a given line, ordered by split sequence:

• SELECT line_id, split_index, ordered_quantity, ship_from_org_id, ship_to_org_id FROM ont.oe_line_split_details WHERE line_id = :line_id ORDER BY split_index;
• Grouping by REQUEST_ID to review the outcome of a single concurrent split program run.
• Aggregating ORDERED_QUANTITY and ORDERED_QUANTITY2 by SHIP_FROM_ORG_ID for warehouse allocation reporting.
• Filtering by CHANGE_REASON_CODE to analyze the distribution of split reasons across a period using REQUEST_DATE.

Related Objects

The documented structure identifies LINE_ID as the principal linkage to the order line entity; the remaining relationships are inferred from standard Order Management architecture.

• OE_ORDER_LINES_ALL — joined on LINE_ID to obtain order header, line number, and item context.
• OE_ORDER_HEADERS_ALL — reached via OE_ORDER_LINES_ALL to retrieve the order number and customer.
• OE_LINE_SPLIT_DETAILS — self-consistent by composite key (LINE_ID, SPLIT_INDEX) for sequencing splits.
• FND_CONCURRENT_REQUESTS — joined on REQUEST_ID to identify the concurrent program and its status.
• ONT.OE_CHANGE_REASONS — referenced by CHANGE_REASON_CODE for reason descriptions.
• Order Management split APIs — the Order Management line-split concurrent programs and OE Order Import interfaces that populate this table.