Search Results so_lines_v

Overview

SO_LINES_V is an Order Entry (OE) reporting view in Oracle E-Business Suite that exposes sales order line detail. It is the line-level companion to SO_HEADERS_V, presenting attributes from OE_ORDER_LINES_ALL joined with inventory item master data and order management lookup values. The view is primarily referenced by Oracle's seeded order management inquiry and reporting infrastructure, including the Order Organizer, Sales Orders window flexfield/reference logic, and various Order Entry report programs.

The description metadata explicitly states "Not implemented in this database," indicating the view is defined in Oracle's shipped application schema (typically APPS) but is not materialized as a physical custom object in a given customer instance. Its role is therefore as a read-only reporting and integration surface, consumed by concurrent programs, BI Publisher data templates, and custom extensions that require denormalized order line information without directly joining the underlying transactional tables.

Underlying Base Objects

The view text is defined over the order management line entity, primarily OE_ORDER_LINES_ALL (aliased LIN). Supporting joins supply descriptive attributes:

• MTL_SYSTEM_ITEMS (aliased MTL) — supplies ITEM_DESCRIPTION, BOM_ITEM_TYPE, and SERVICEABLE_PRODUCT_FLAG.
• SO_LOOKUPS (aliased SO2) — resolves ITEM_TYPE_CODE to its MEANING.
• QP_PRICE_LISTS (aliased SPL) — supplies NAME and ROUNDING_FACTOR for price list context.

The view also invokes several OE_QUERY package functions — ATO_INDICATOR, LINE_TOTAL — and derives SHIPMENT_SCHEDULE_FLAG through a DECODE on LINE_TYPE_CODE. No base objects are separately documented in the ETRM metadata; the join relationships must be inferred from the view text itself.

Key Columns

• LINE_ID, HEADER_ID, PARENT_LINE_ID, SERVICE_PARENT_LINE_ID, ATO_LINE_ID — the line's identity and hierarchy within the order.
• LINE_TYPE_CODE, ITEM_TYPE_CODE, ITEM_TYPE — classify the line (e.g., PARENT, STANDARD) and item category with the resolved lookup meaning.
• OPEN_FLAG, ATO_FLAG, ATO_INDICATOR_FLAG, OPTION_FLAG, SHIPMENT_SCHEDULE_FLAG — status and configuration indicators used in fulfillment processing.
• ORDERED_QUANTITY, CANCELLED_QUANTITY, UNIT_CODE — quantity and unit of measure.
• LIST_PRICE, SELLING_PRICE, LIST_PERCENT, SELLING_PERCENT, PRICE_LIST, ROUNDING_FACTOR, TOTAL — pricing components, with TOTAL computed by OE_QUERY.LINE_TOTAL.
• SERVICEABLE_PRODUCT_FLAG, SERVICE_DURATION — service-related attributes important for service-enablement and service_total calculations.
• PRICING_CONTEXT and PRICING_ATTRIBUTE1 through PRICING_ATTRIBUTE10 — pricing flexfield context for advanced pricing.

Common Use Cases and Queries

The view is commonly queried to retrieve order line totals, pricing breakdowns, and item classifications for reporting. A typical query retrieving line-level totals for an order is:

SELECT line_id, header_id, line_number, item_description,
       ordered_quantity, cancelled_quantity, selling_price, total,
       serviceable_product_flag, item_type
FROM   so_lines_v
WHERE  header_id = :p_header_id
ORDER  BY line_number;

Because TOTAL is computed per-line via OE_QUERY.LINE_TOTAL and considers SERVICE_DURATION and SERVICEABLE_PRODUCT_FLAG, the view is the standard source for service_total style aggregations — summing line totals across serviceable lines to produce an order-level service value. A common aggregation is:

SELECT header_id, SUM(total) AS line_total_sum
FROM   so_lines_v
WHERE  header_id = :p_header_id
GROUP  BY header_id;

Other use cases include data extraction for integrations that need item descriptions and lookup meanings alongside order lines, and supporting custom Order Entry reports where joining OE_ORDER_LINES_ALL directly would bypass the view's convenience joins. Query performance depends on the LINE_ID, HEADER_ID, and SOURCE_LINE_ID indexes on the underlying order lines table.