Search Results rule_start_date

Overview

OE_ORDER_LINES_RM_V is a reporting view owned by the APPS schema in Oracle E-Business Suite Release 12.1.1 and 12.2.2. It is defined in the Order Management (ONT) product and carries a VALID status. The suffix "RM_V" indicates a reporting-model view intended primarily for read-only reporting and integration consumption rather than for transactional processing. The view flattens order line data from the Order Management tables into a single, denormalized result set that spans line attributes, pricing, scheduling, shipping, fulfillment, and invoicing indicators.

The view is particularly relevant to users searching for the SHIPPED_FLAG column, since it exposes this attribute explicitly. In the view definition, SHIPPED_FLAG is derived as DECODE(NVL(OEL.SHIPPED_QUANTITY, 0), 0, 'N', 'Y'), meaning it returns 'Y' when the shipped quantity on the order line is non-zero and 'N' otherwise. This makes the view a convenient source for determining, at the line level, whether a shipment has occurred without requiring a join to the shipping or delivery tables.

Underlying Base Objects

The documented base objects referenced by OE_ORDER_LINES_RM_V are:

• FND_LANGUAGES (SYNONYM) — the language base table used in the multilingual join region of the view.
• OE_ORDER_LINES_ALL (SYNONYM) — the primary transactional table supplying the majority of the columns (aliased OEL).
• OE_TRANSACTION_TYPES_ALL (SYNONYM) — provides transaction type context.
• OE_TRANSACTION_TYPES_TL (SYNONYM) — the translated transaction type descriptions.
• QP_LIST_HEADERS_TL (SYNONYM) — the translated price list headers, used for pricing-related lookups.

Although the excerpted view text shows a direct SELECT from OE_ORDER_LINES_ALL (OEL) with references to line type (LT.NAME), the documented object list confirms that the complete view joins to the order transaction type and price list translation tables to resolve descriptive names. Every functional line attribute originates from OE_ORDER_LINES_ALL, making that table the anchor of the view.

Key Columns

The view exposes line identity and header context through LINE_ID, HEADER_ID, ORG_ID, and LINE_NUMBER. A constant, 'SALES_ORDER', is returned as DOCUMENT_TYPE_CODE. Order classification is provided by LINE_TYPE and FLOW_STATUS_CODE.

• ORDERED_QUANTITY — adjusted by LINE_CATEGORY_CODE, returning the ordered quantity negated for returns. LINE_AMOUNT applies the same sign logic to unit selling price multiplied by quantity.
• SHIPPED_QUANTITY, CANCELLED_QUANTITY, FULFILLED_QUANTITY, and SHIPPING_QUANTITY — the core quantity metrics for line progression.
• SHIPPED_FLAG — derived as 'N' when shipped quantity is zero or null, otherwise 'Y'.
• INVOICED_FLAG — derived identically from INVOICED_QUANTITY.
• INVOICABLE_FLAG and SHIPPABLE_FLAG — returned as NULL in this view.
• Pricing columns include UNIT_SELLING_PRICE, UNIT_LIST_PRICE, and their percent variants.
• Scheduling and logistics columns include SCHEDULE_SHIP_DATE, ACTUAL_SHIPMENT_DATE, SHIPPING_METHOD_CODE, FREIGHT_CARRIER_CODE, and SHIPMENT_NUMBER.

Common Use Cases and Queries

The primary use case is line-level shipment status reporting. A typical query to find shipped order lines is:

SELECT line_id, header_id, line_number, ordered_quantity,
       shipped_quantity, shipped_flag
FROM   oe_order_lines_rm_v
WHERE  shipped_flag = 'Y';

Users commonly combine SHIPPED_FLAG with the INVOICED_FLAG to identify delivered-but-unbilled lines, supporting revenue and receivables reconciliation:

SELECT line_id, header_id, ordered_quantity, shipped_flag, invoiced_flag
FROM   oe_order_lines_rm_v
WHERE  shipped_flag = 'Y'
AND    invoiced_flag = 'N';

Because the view adjusts ORDERED_QUANTITY and LINE_AMOUNT for return lines, it is also used to produce net sales reporting where returns reduce the reported totals. The view can be filtered by ORG_ID, SCHEDULE_SHIP_DATE, or FLOW_STATUS_CODE to support operational dashboards and integration feeds requiring a consolidated order line extract.