Search Results so_lines_view_lines_v

Overview

SO_LINES_VIEW_LINES_V is a reporting view in the Oracle Order Entry (OE) module that presents a flattened, query-friendly projection of order line data for Oracle E-Business Suite 12.1.1 and 12.2.2. Its purpose is to expose the principal attributes of sales order lines — quantities, pricing, scheduling, holds, and line hierarchy — without requiring report authors to join the underlying OE_ORDER_LINES_ALL table to multiple lookup and inventory tables manually. Much of the calculated logic is delegated to functions in the OE_QUERY package, so the view returns derived values such as open quantity, extended price, reservation quantity, and formatted line numbers in addition to raw column values. The view is read-only and is intended for reporting and integration scenarios rather than transactional processing.

Underlying Base Objects

The ETRM metadata documents no referenced base objects, and the view is noted as "Not implemented in this database." The view text, however, shows the primary driver table aliased as SL, which corresponds to OE_ORDER_LINES_ALL, with the inventory master item table aliased MSI (MTL_SYSTEM_ITEMS_B) joined to supply item concatenated segments and descriptions. Beyond those two physical tables, the view depends heavily on the OE_QUERY package, calling SCHEDULE_STATUS, HOLD, LINE_TOTAL, OPTION_LINE_NUMBER, SHIPMENT_SCHEDULE_NUMBER, BASE_LINE_NUMBER, RESERVED_QUANTITY, and ITEM_CONC_SEG. This means the view's output is influenced not only by stored row values but also by runtime business logic embedded in PL/SQL functions.

Key Columns

The view exposes identifiers LINE_ID and HEADER_ID that link each row back to its order line and order header. Quantity columns include ORDERED_QUANTITY, CANCELLED_QUANTITY, SHIPPED_QUANTITY, OPEN_QUANTITY (ordered minus cancelled), and RESERVED_QUANTITY. Pricing columns include LIST_PRICE, SELLING_PRICE, DISCOUNT (list minus selling), EXTENDED_PRICE, LINE_TOTAL, and TAX_CODE. Scheduling and fulfillment attributes include SCHEDULE_DATE, DATE_REQUESTED_CURRENT, PROMISE_DATE, SHIP_SET_NUMBER, and SCHEDULE_STATUS. Line hierarchy is represented by PARENT_LINE_ID, SERVICE_PARENT_LINE_ID, SHIPMENT_SCHEDULE_LINE_ID, LINE_NUMBER, OPTION_NUMBER, and SHIPMENT_NUMBER. The SERVICE_PARENT_LINE_ID column is significant for service and warranty line relationships, distinguishing a service line's parent from its structural parent. Item columns ITEM and ITEM_DESC supply the concatenated identifier and description, while LINE_TYPE_CODE and ORIGINAL_SYSTEM_LINE_REFERENCE identify the line category and external source.

Common Use Cases and Queries

Typical uses include open order backlogs, booking and shipment reports, price and discount analysis, and service-line tracing. Because SERVICE_PARENT_LINE_ID is the searched term, a frequent query retrieves service lines and their associated parent order line:

• Open backlog by line: SELECT header_id, line_id, ordered_quantity, open_quantity, schedule_status FROM so_lines_view_lines_v WHERE open_quantity > 0;
• Service-to-parent relationship: SELECT line_id, line_type_code, parent_line_id, service_parent_line_id, item FROM so_lines_view_lines_v WHERE service_parent_line_id IS NOT NULL;
• Pricing review: SELECT line_id, list_price, selling_price, discount, extended_price FROM so_lines_view_lines_v WHERE discount <> 0;
• Reserved versus shipped quantities: SELECT line_id, ordered_quantity, reserved_quantity, shipped_quantity FROM so_lines_view_lines_v;

Report authors should confirm the view exists and is compiled in the target instance before relying on it, since the ETRM metadata flags it as not implemented in that database.