Results for “extended_price”

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

Overview

SO_LINES_SUMMARY_V is a reporting view owned by the APPS schema in Oracle E-Business Suite, defined within the Order Entry (OE) product family. It presents a denormalized, line-level summary of sales order data by joining order line records with item and unit-of-measure reference information. The view is designed for reporting and integration scenarios in which consumers require a flat, query-friendly structure rather than the normalized relationships of the underlying Order Management tables.

The view carries a VALID status in the data dictionary and is documented for both EBS 12.1.1 and 12.2.2. Its principal value lies in the computed EXTENDED_PRICE column, which multiplies selling price by ordered quantity in a single expression, sparing report authors and interfaces from reproducing that arithmetic. Because the view also resolves the inventory item number and unit of measure description, it is well suited to operational reporting, ad hoc query, and lightweight outbound integration where the full order line detail is not required.

Underlying Base Objects

The view is defined over three documented base objects:

• SO_LINES (VIEW) — the primary source of order line data, supplying header, line number, quantity, pricing, and scheduling attributes.
• MTL_ITEM_FLEXFIELDS (VIEW) — supplied to resolve the inventory item identifier to a human-readable item number and organization. The join predicate is LINE.INVENTORY_ITEM_ID = ITEM.INVENTORY_ITEM_ID.
• MTL_UNITS_OF_MEASURE (SYNONYM) — provides the unit of measure description via the predicate LINE.UNIT_CODE = UOM.UOM_CODE.

The view text uses an inner-join style WHERE clause with no outer-join operators, so lines lacking a matching item or unit of measure are excluded from the result set. Note that all three base objects are themselves views or synonyms rather than base tables, which means the performance profile of SO_LINES_SUMMARY_V ultimately depends on the underlying Order Management and Inventory structures they reference.

Key Columns

• ROW_ID — the ROWID of the originating sales order line, useful as a pseudokey for referencing the source record.
• HEADER_ID — the order header identifier, linking the line to its parent order.
• LINE_NUMBER — the line sequence within the order.
• ITEM — the inventory item number returned from MTL_ITEM_FLEXFIELDS.
• ORGANIZATION_ID — the inventory organization associated with the item.
• ORDERED_QUANTITY — the quantity ordered on the line.
• UNIT_OF_MEASURE — the unit of measure description.
• SELLING_PRICE — the unit selling price for the line.
• EXTENDED_PRICE — computed as NVL(SELLING_PRICE, 0) * NVL(ORDERED_QUANTITY, 0). This is the column users most frequently search for, and it provides a null-safe, pre-calculated line total.
• DATE_REQUESTED_CURRENT, PROMISE_DATE, SCHEDULE_DATE — the current requested date, the promised date, and the scheduled date for the line.

Common Use Cases and Queries

Typical uses include order line summaries for reporting, extended price roll-ups by order or item, and extracts for downstream systems. A representative query returning the extended price per line is:

• SELECT header_id, line_number, item, ordered_quantity, selling_price, extended_price FROM apps.so_lines_summary_v WHERE header_id = :p_header_id ORDER BY line_number;
• SELECT item, SUM(extended_price) total_value FROM apps.so_lines_summary_v GROUP BY item ORDER BY total_value DESC;
• SELECT header_id, SUM(extended_price) order_value FROM apps.so_lines_summary_v WHERE schedule_date BETWEEN :from_date AND :to_date GROUP BY header_id;

Because EXTENDED_PRICE already applies NVL logic to both operands, queries may aggregate the column directly without additional null handling. Users should be aware that the inner joins mean lost-item or lost-UOM lines will not appear, and that the view is a summary projection only — it does not expose all Order Management attributes.