Search Results so_lines_oexorrso_v

Overview

The SO_LINES_OEXORRSO_V view is an Order Entry (OE) reporting object delivered within the Oracle E-Business Suite 12.1.1 and 12.2.2 environments. It exposes order line data drawn primarily from the Oracle Order Management base line table, joined to inventory and customer master reference data to enrich the output with descriptive attributes. The view is designed to present order lines in a denormalized, report-friendly form, combining transactional line attributes with human-readable descriptions for items, warehouses, contacts, and lookup meanings.

A distinguishing characteristic of this view is the presence of the derived column SHIPMENT_SCHEDULE_FLAG, computed as DECODE(LIN.LINE_TYPE_CODE, 'PARENT', 'Y', 'N'). This flag identifies lines that act as shipment schedule parents in the order line hierarchy. The view further exposes SHIPMENT_SCHEDULE_LINE_ID, which links a schedule line back to its parent, supporting analysis of schedule-based ordering and configured item structures. Because it spans pricing, shipping, invoicing, and customer attributes, the view serves as a convenient single-source projection for downstream reporting and integration rather than for transactional update processing.

Underlying Base Objects

The ETRM documentation excerpt lists no referenced base objects and states the view is "Not implemented in this database," meaning the extract was captured from a reference or metadata repository without a live deployment. However, the view text clearly indicates that its principal driving table is the Order Management line table (aliased LIN), which supplies identifiers, quantities, dates, pricing, and status flags. It is joined to the item master (MTL) for ITEM_DESCRIPTION, to the inventory organization table (MTLP) for ORGANIZATION_CODE as the warehouse, to a location table (RSU) for the ship-to location, to the customer account table (RAD) for the ship-to customer identifier, and to a contact table (CON) for the ship-to contact name. Lookup meaning is resolved through a reference alias (SO1) for the shipment priority. These joins transform raw foreign keys into descriptive values, which is the primary purpose of the view.

Key Columns

• ROW_ID, LINE_ID, HEADER_ID — primary row and relational identifiers linking lines to their order header.
• SHIPMENT_SCHEDULE_FLAG — derived indicator set to Y when LINE_TYPE_CODE is 'PARENT', designating a shipment schedule parent line.
• SHIPMENT_SCHEDULE_LINE_ID and PARENT_LINE_ID — establish the parent-child hierarchy for schedule and configuration lines.
• LINE_TYPE_CODE, ITEM_TYPE_CODE, ATO_FLAG, COMPONENT_SEQUENCE_ID — identify line classification and configured/ATO structure.
• ORDERED_QUANTITY, SHIPPED_QUANTITY, CANCELLED_QUANTITY, INVOICED_QUANTITY, QUANTITY_TO_INVOICE — life-cycle quantities.
• ITEM_DESCRIPTION, WAREHOUSE, SHIP_TO_LOCATION, SHIP_TO_CONTACT_NAME, SHIPMENT_PRIORITY — descriptive attributes sourced via joins and lookups.
• Pricing and scheduling columns such as LIST_PRICE, SELLING_PRICE, SCHEDULE_DATE, PROMISE_DATE, DATE_REQUESTED_CURRENT.

Common Use Cases and Queries

Typical uses include shipment schedule reporting, backorder and fulfillment analysis, and extraction feeds for data warehouses. To isolate schedule parent lines, filter on the derived flag:

• SELECT line_id, header_id, line_number, shipment_schedule_line_id, ordered_quantity, schedule_date FROM so_lines_oexorrso_v WHERE shipment_schedule_flag = 'Y';
• SELECT header_id, item_description, warehouse, ordered_quantity, shipped_quantity FROM so_lines_oexorrso_v WHERE ordered_quantity > shipped_quantity;
• SELECT line_id, ship_to_contact_name, ship_to_location, promise_date FROM so_lines_oexorrso_v WHERE TRUNC(promise_date) < SYSDATE;

Because the view is read-only and denormalized, it should be used exclusively for query and reporting workloads, avoiding any assumption that it supports DML.