Search Results unit_list_percent




Overview
Explore in AI Chat

Overview

The APPS.OE_ORDER_LINES_RM_V view is a reporting and reference-model view owned by the APPS schema and registered in Oracle E-Business Suite under the ONT (Order Management) application, with FND Design Data reference ONT.OE_ORDER_LINES_RM_V. The view presents a denormalized, read-oriented projection of order line data drawn primarily from the Order Management transaction tables, and it is intended for reporting, integration, and downstream consumption rather than for transactional updates. Because its status is VALID and it resides in the APPS schema, it can be referenced directly by custom reports, concurrent programs, and interface extracts across both EBS 12.1.1 and 12.2.2.

The view is of particular interest where users search on the column REFERENCE_CUSTOMER_TRX_LINE_ID. That column associates an order line with a specific Receivables transaction line, supporting reconciliation between OM fulfillment activity and the resulting AR invoice lines. This makes the view a convenient single source for joining sales order detail to billing detail without traversing the underlying OE_ORDER_LINES_ALL table directly.

Underlying Base Objects

The documented view metadata for 12.2.2 identifies the following referenced objects:

  • FND_LANGUAGES (SYNONYM) — supplied for translated columns and language-sensitive joins.
  • OE_ORDER_LINES_ALL (SYNONYM) — the primary source of order line attributes, including identifiers, quantities, pricing, and flags.
  • OE_TRANSACTION_TYPES_ALL (SYNONYM) — source of transaction type attributes such as DOCUMENT_TYPE_CODE.
  • OE_TRANSACTION_TYPES_TL (SYNONYM) — the translated transaction type descriptions.
  • QP_LIST_HEADERS_TL (SYNONYM) — the translated price list header information used to resolve pricing context.

The view therefore consolidates the core order line entity with transaction type and price list reference data. The RM designation indicates a reference model view, meaning it is designed to expose a stable, simplified column set over the more complex transactional base tables. All base objects are referenced via synonyms, so the view resolves against the APPS-owned base tables at runtime.

Key Columns

The view exposes a broad column set. The most significant include:

Common Use Cases and Queries

Typical uses include reconciling shipped order lines to AR invoice lines, extracting order line detail for data warehousing, and auditing invoicing status. The REFERENCE_CUSTOMER_TRX_LINE_ID column is commonly used to tie order lines to receivable transaction lines produced by AutoInvoice or the Order-to-Cash flow.

Sample query reconciling order lines to billing:

  • SELECT l.header_id, l.line_id, l.ordered_item, l.ordered_quantity, l.invoiced_quantity, l.reference_customer_trx_line_id, l.flow_status_code FROM apps.oe_order_lines_rm_v l WHERE l.reference_customer_trx_line_id IS NOT NULL AND l.org_id = :p_org_id;

Sample query for uninvoiced, shippable lines:

  • SELECT line_id, ordered_item, ordered_quantity, schedule_ship_date FROM apps.oe_order_lines_rm_v WHERE invoiced_flag = 'N' AND invoicable_flag = 'Y' AND org_id = :p_org_id;