Search Results received_quantity

Overview

ICX_SO_RMA_MTL_INT_V is a database view owned by the APPS schema in Oracle E-Business Suite (EBS) 12.1.1 and 12.2.2. It belongs to the ICX product family, Oracle iProcurement, which governs the self-service procurement and requisitioning flows within EBS. The view presents aggregated return material authorization (RMA) receipt and interface information for sales order RMA processing, joining the RMA interface staging area with its associated receipt transaction records.

The EBS metadata classifies this view as Obsolete. This status indicates that Oracle no longer recommends or supports its use in current application logic; it exists primarily for backward compatibility. Despite its deprecated designation, understanding the view remains relevant for administrators auditing supplier return flows, troubleshooting historical integration records, or maintaining custom reports that reference it. Because it is a view rather than a table, it materializes no data of its own and draws all content at runtime from its underlying base objects.

Underlying Base Objects

The view is defined strictly over two documented base objects, both exposed in the APPS schema through synonyms:

• MTL_SO_RMA_INTERFACE — the RMA interface staging table (synonym referenced in EBS 12.2.2 metadata).
• MTL_SO_RMA_RECEIPTS — the RMA receipts table holding received, accepted, and receipt-date information (synonym referenced in EBS 12.2.2 metadata).

The relationship is expressed as an outer join: the receipts table is joined using the (+). That is, MTLSRR.RMA_INTERFACE_ID(+) = MTLSRI.RMA_INTERFACE_ID. This makes MTL_SO_RMA_INTERFACE the driving (preserved) table, so every interface row is returned even when no corresponding receipt exists. In that case, the aggregate quantities default to zero via NVL. The cost of this outer join is a multi-row aggregation, since a single interface row may match multiple receipt rows.

Key Columns

The view exposes five columns, several of which are aggregated results rather than direct passthrough columns:

• RMA_LINE_ID — the grouping identifier inherited from MTL_SO_RMA_INTERFACE, identifying the specific RMA line to which the aggregated quantities pertain.
• RECEIVED_QUANTITY — computed as SUM(NVL(MTLSRR.RECEIVED_QUANTITY, 0)); the total quantity received against the RMA line.
• RECEIPT_DATE — computed as MAX(MTLSRR.RECEIPT_DATE); the latest date on which goods were received against that line.
• ACCEPTED_QUANTITY — computed as SUM(NVL(MTLSRR.ACCEPTED_QUANTITY, 0)); the total quantity accepted after inspection.
• INTERFACED_QUANTITY — taken directly from MTLSRI.QUANTITY, representing the quantity originally recorded on the interface line.

The view groups by MTLSRI.RMA_LINE_ID, MTLSRI.QUANTITY, MTLSRI.INVENTORY_ITEM_ID, and MTLSRI.COMPONENT_SEQUENCE_ID. Consequently, only RMA_LINE_ID is projected outward while the other grouping keys are internal, meaning a single projected row may reflect aggregation across multiple interface records sharing the same line. This is a critical nuance: INVENTORY_ITEM_ID and COMPONENT_SEQUENCE_ID are swallowed by the GROUP BY and not exposed, so users cannot distinguish item- or component-level detail from the output alone.

The RECEIPT_DATE column is the most frequently searched attribute, as it supports reconciliation between what was interfaced and what was actually received, and it is the only date dimension available for time-based filtering on this view.

Common Use Cases and Queries

Because the view carries only aggregated data, it is best suited to summary-level reporting rather than transactional drill-down. Typical scenarios include reconciling interfaced versus received quantities for supplier returns, identifying RMA lines where the latest receipt date falls within a specific period, and detecting discrepancies between received and accepted quantities.

A representative query retrieving line-level RMA status:

SELECT rma_line_id, received_quantity, receipt_date, accepted_quantity, interfaced_quantity FROM apps.icx_so_rma_mtl_int_v WHERE receipt_date >= TRUNC(SYSDATE) - 30;

To surface lines where acceptance lags receipt, exposing possible quality holds:

SELECT rma_line_id, received_quantity, accepted_quantity, (received_quantity - accepted_quantity) rejected_qty FROM apps.icx_so_rma_mtl_int_v WHERE received_quantity > accepted_quantity;

Given the object's obsolete classification, new development should target current RMA receipt and interface objects instead. Where existing reports depend on ICX_SO_RMA_MTL_INT_V, note that filters cannot key on inventory item or component sequence, and receipt_date reflects the maximum date per line, not an individual transaction date.