Search Results so_lines_rma_v




Overview
Explore in AI Chat

Overview

SO_LINES_RMA_V is a reporting view owned by the APPS schema in Oracle E-Business Suite, delivered under the Order Entry (OE) product family. The view presents a denormalized, query-friendly projection of return merchandise authorization (RMA) order lines, combining line-level attributes from the sales order line tables with descriptive and derived data sourced from inventory items, price lists, receivables, and a set of OE_QUERY package functions. Its status is VALID in both 12.1.1 and 12.2.2 reference environments.

Because it joins base order-entry entities and applies business logic at the database layer, the view is commonly used for RMA reporting, returns analysis, reconciliation of received and accepted quantities, and integration extracts where a single row per return line is required. It is not a transactional base table; consumers should treat it as read-only.

Underlying Base Objects

The view is defined over the following documented objects:

The view text confirms that many calculated values are fetched through OE_QUERY function calls rather than direct column references from the underlying tables.

Key Columns

Prominent columns exposed by the view include:

Common Use Cases and Queries

Typical scenarios include returns reconciliation, tracking quantity received versus accepted against an RMA, and reporting against the original referenced order line.

  • Retrieve RMA line details for a specific header.
  • Report received/accepted quantities and actual dates per line.
  • Correlate return lines using line number or link-to-line identifiers for reference tracking.

Sample SQL:

SELECT header_id, line_id, line_number, inventory_item_id, item_description, ordered_quantity, received_quantity, accepted_quantity, actual_receipt_date, actual_accepted_date, warehouse_code FROM apps.so_lines_rma_v WHERE header_id = :p_header_id ORDER BY line_number;

To locate lines by reference or linked line, filter on line_number or link_to_line_id. Because several columns are resolved through OE_QUERY functions, performance can be affected when large result sets are scanned without restrictive predicates.