Search Results interfaced_quantity

Overview

SO_RMA_MTL_INT_V is a read-only database view owned by the APPS schema within the Oracle E-Business Suite Order Entry (OE) module. It presents a consolidated, aggregated picture of Return Material Authorization (RMA) receipt activity by combining data from the RMA material transaction interface with the corresponding RMA receipt records. The view is flagged VALID in the ETRM metadata for both Oracle EBS 12.1.1 and 12.2.2.

The view's primary role is to expose, for each RMA line, the total quantity received and accepted against the quantity that was originally interfaced into inventory. Because the underlying interface and receipt tables can contain multiple transaction rows for a single RMA line, the view collapses those rows using SUM and MAX aggregations. This makes it well suited for reconciliation reporting, RMA receipt status inquiries, and integration monitoring where a one-row-per-RMA-line perspective is required. Consumers performing searches on received_quantity will find this metric surfaced directly from the view, making it a frequent entry point for receipt-quantity analysis.

Underlying Base Objects

The view is defined over two base objects, both referenced through SYNONYM in the APPS schema:

• MTL_SO_RMA_INTERFACE (aliased MTLSRI) — holds RMA line interface records keyed by RMA_INTERFACE_ID.
• MTL_SO_RMA_RECEIPTS (aliased MTLSRR) — holds individual receipt transactions linked to the interface by RMA_INTERFACE_ID.

The join is an outer join (MTLSRR.RMA_INTERFACE_ID(+) = MTLSRI.RMA_INTERFACE_ID), so RMA line interface records with no matching receipts are still returned, with receipt quantities defaulting to zero via NVL. Results are grouped by RMA_LINE_ID, QUANTITY, INVENTORY_ITEM_ID, and COMPONENT_SEQUENCE_ID, ensuring that distinct line/item/component combinations are reported independently. This structure directly supports the aggregation performed by the view and explains why quantity values reflect summed receipt activity rather than single transactions.

Key Columns

• RMA_LINE_ID — the RMA line identifier; the principal grouping key and typical join column to RMA line detail tables.
• RECEIVED_QUANTITY — SUM(NVL(MTLSRR.RECEIVED_QUANTITY,0)); the cumulative quantity received for the RMA line. This is the metric most commonly searched and is central to matching receipts against expected returns.
• RECEIPT_DATE — MAX(MTLSRR.RECEIPT_DATE); the most recent receipt date recorded for the line.
• ACCEPTED_QUANTITY — SUM(NVL(MTLSRR.ACCEPTED_QUANTITY,0)); the cumulative quantity accepted into inventory after inspection.
• INTERFACED_QUANTITY — MTLSRI.QUANTITY; the quantity originally interfaced for the RMA line, providing the comparison baseline for received and accepted totals.

Common Use Cases and Queries

Typical uses include reconciliation of received versus interfaced quantities, identifying partially received RMAs, and confirming acceptance status before crediting a customer. A representative query comparing the three quantity measures is:

SELECT rma_line_id, interfaced_quantity, received_quantity, accepted_quantity, receipt_date FROM apps.so_rma_mtl_int_v WHERE received_quantity > 0 ORDER BY rma_line_id;

To isolate lines where receipt activity lags the interfaced quantity:

SELECT rma_line_id, interfaced_quantity, received_quantity FROM apps.so_rma_mtl_int_v WHERE received_quantity < interfaced_quantity;

Because quantity columns are aggregated, filtering on RECEIVED_QUANTITY in the WHERE clause returns grouped totals rather than individual receipt rows; for transaction-level detail, the base receipt table should be queried directly. All access should respect the APPS schema ownership and standard EBS security conventions.