Search Results oe_crm_order_lines_v




Overview
Explore in AI Chat

Overview

OE_CRM_ORDER_LINES_V is a compatibility view owned by the APPS schema in Oracle E-Business Suite Releases 12.1.1 and 12.2.2. As its name and ETRM description state, it is a "compatible view provided for CRM usage only," meaning it exists to satisfy the column expectations of Oracle CRM and other downstream integration consumers that were originally written against an earlier data model. The view does not introduce new business logic or aggregation; it is a thin projection over the Order Management order line entity, exposing a stable, flattened set of attributes for order lines.

Its role is principally as a reporting and integration interface. Customers, service, quoting, and tele-sales flows that need to read order line detail without depending on the full, internally volatile structure of OE_ORDER_LINES_ALL can select from this view. Because the view is designated compatibility-only, Oracle reserves the right to keep its column list fixed for CRM purposes while the underlying base table continues to evolve.

Underlying Base Objects

The ETRM metadata documents the view as based on the OE_ORDER_LINES table, referenced through the OE_ORDER_LINES synonym, and the view text in the documentation confirms the projection is drawn from the order line entity (OE_ORDER_LINES_ALL in the physical data model). Only a synonym is listed as a referenced base object, which reflects the standard Oracle EBS practice of exposing the base table to APPS code through a synonym rather than the physical table name.

No joins to headers, customers, or items are embedded in the documented view text; the columns exposed are all intrinsic to the order line record. Contextual values such as customer identifiers are carried as denormalized ID columns on the line itself. Consequently, report writers normally join this view to OE_ORDER_HEADERS_ALL, HZ_CUST_ACCOUNTS, and MTL_SYSTEM_ITEMS_B to resolve descriptive information.

Key Columns

The view exposes a broad set of order line attributes, organized as follows:

Common Use Cases and Queries

Typical scenarios include CRM order status dashboards, quote-to-order conversions, and integrations that must reconcile shipped versus ordered quantities. A representative query joining the view to headers is shown below.

SELECT l.line_id, l.header_id, l.ordered_item, l.ordered_quantity, l.shipped_quantity, h.order_number FROM oe_crm_order_lines_v l, oe_order_headers_all h WHERE l.header_id = h.header_id AND l.org_id = :p_org_id AND h.order_number = :p_order_number;

Regarding the searched term REFERENCE_CUSTOMER_TRX_LINE_ID: this column is not present in the documented column list of OE_CRM_ORDER_LINES_V. The view exposes REFERENCE_LINE_ID, REFERENCE_HEADER_ID, and REFERENCE_TYPE, which relate to source document references, but no customer transaction line identifier. Consumers seeking an invoice line reference must obtain it through the order-to-invoice relationship, for example via OE_ORDER_LINES_ALL and RA_CUSTOMER_TRX_LINES, rather than through this compatibility view.