Results for “mtl_so_rma_interface”
50+ results
AI-generated from documented ETRM metadata — verify critical details on the linked pages.
Overview
MTL_SO_RMA_INTERFACE is a table owned by the INV (Inventory) schema in Oracle E-Business Suite releases 12.1.1 and 12.2.2. It is documented as an obsolete object relative to the newer Order Management system; its stated purpose is limited to data migration, carrying RMA headers and lines into the new Order Management interface. In the context of the legacy Order Entry (OE) interface, the table functioned as a staging and interface surface through which return material authorization transactions were introduced into the order pipeline.
Because the object exists primarily to hold staged transaction data pending migration, the heuristic Data Vault classification derived from its foreign key structure is satellite-leaning. In modeling terms this is a suggestion rather than a mandate: the table behaves as a descriptive satellite keyed to an RMA interface identifier, with secondary references outward to sales orders, items, and RMA receipt records. It is not a true hub, since the identifier it carries is a staging surrogate rather than a durable business entity identifier.
Key Information Stored
The table is documented with 35 columns in ETRM 12.2.2. Its surrogate primary key, defined by the constraint MTL_SO_RMA_INTERFACE_PK, is RMA_INTERFACE_ID — the column most commonly referenced in lookup queries. This identifier is not a business key; it is the staging handle by which downstream objects such as MTL_SO_RMA_RECEIPTS link back to the interface record.
The most significant columns fall into several groups:
- RMA identity: RMA_ID, RMA_LINE_ID, RMA_NUMBER, RMA_LINE_NUMBER, and RMA_TYPE associate the interface row with its return authorization header and line context.
- Order and item references: SALES_ORDER_ID links to MTL_SALES_ORDERS, while INVENTORY_ITEM_ID and ORGANIZATION_ID link to MTL_SYSTEM_ITEMS_B, defining what is being returned and from where.
- Quantities and status: QUANTITY, RECEIVED_QUANTITY, and DELIVERED_QUANTITY track the expected and realized movement of goods, complemented by CLOSED_FLAG and IN_USE_FLAG.
- Receiving attributes: EXPECTED_RECEIPT_DATE, EXPECTED_SUBINVENTORY_NAME, LOT_NUMBER, SERIAL_NUMBER_FLAG, INSPECTION_REQUIRED_FLAG, and INSPECTION_INSTRUCTIONS describe how the return is to be received and inspected.
- Financial and audit context: DISTRIBUTION_ACCOUNT_ID, REQUIRED_FOR_REVENUE_FLAG, and the standard WHO columns (CREATION_DATE, CREATED_BY, LAST_UPDATE_DATE, LAST_UPDATED_BY, LAST_UPDATE_LOGIN) plus the concurrent program columns (REQUEST_ID, PROGRAM_ID, PROGRAM_APPLICATION_ID) support accounting and auditability.
Common Use Cases and Queries
Because the object is obsolete for new implementations, its principal modern use is migration validation and historical reconciliation. A typical query resolves an interface row to its downstream receipt by joining on the primary key:
SELECT r.RMA_INTERFACE_ID, r.RMA_NUMBER, r.RMA_LINE_NUMBER, r.QUANTITY, rc.RECEIPT_NUMBER FROM INV.MTL_SO_RMA_INTERFACE r JOIN INV.MTL_SO_RMA_RECEIPTS rc ON rc.RMA_INTERFACE_ID = r.RMA_INTERFACE_ID;- Locating a record by its identifier:
SELECT * FROM INV.MTL_SO_RMA_INTERFACE WHERE RMA_INTERFACE_ID = :p_id; - Reconciling item and organization context:
SELECT r.RMA_NUMBER, r.INVENTORY_ITEM_ID, r.ORGANIZATION_ID FROM INV.MTL_SO_RMA_INTERFACE r WHERE r.RMA_TYPE = :p_type; - Reporting outstanding returns by expected receipt date for migrations nearing cutover.
Related Objects
The following relationships are documented and are the most operationally significant:
- MTL_SO_RMA_RECEIPTS — references MTL_SO_RMA_INTERFACE.RMA_INTERFACE_ID; the primary dependent object and the main path for receipt-side data.
- MTL_SALES_ORDERS — joined via SALES_ORDER_ID, supplying the originating sales order context.
- MTL_SYSTEM_ITEMS_B — joined via INVENTORY_ITEM_ID and ORGANIZATION_ID, supplying item and inventory organization detail.
- JAI_OM_OE_RMA_LINES — referenced through RMA_LINE_ID, providing RMA line detail used in the OE interface flow.
- Order Management migration and concurrent program objects referenced by REQUEST_ID and PROGRAM_ID, which govern the batch that populates and consumes interface rows.
-
THIS TABLE IS OBSOLETE WITH THE NEW ORDER MANAGEMENT SYSTEM. IT IS USED ONLY FOR DATA MIGRATION FROM THIS TABLE TO THE NEW ORDER MANAGEMENT SYSTEM. .RMA headers and lines for OE interface
-
THIS TABLE IS OBSOLETE WITH THE NEW ORDER MANAGEMENT SYSTEM. IT IS USED ONLY FOR DATA MIGRATION FROM THIS TABLE TO THE NEW ORDER MANAGEMENT SYSTEM. .RMA headers and lines for OE interface
-
Obsolete
APPS.ICX_SO_RMA_MTL_INT_DETAIL_V·↳ MTL_SO_RMA_INTERFACE·↳ MTL_SO_RMA_RECEIPTS·↳ SO_LINE_DETAILS·Explore ICX module →
-
PACKAGE: APPS.RMA_UPDATE 12.1.1
-
PACKAGE: APPS.RMA_UPDATE 12.2.2
-
View: SO_RMA_MTL_INT_V 12.1.1
APPS.SO_RMA_MTL_INT_V·↳ MTL_SO_RMA_INTERFACE·↳ MTL_SO_RMA_RECEIPTS·Explore OE module →
-
APPS.SO_RMA_MTL_INT_DETAIL_V·↳ MTL_SO_RMA_INTERFACE·↳ MTL_SO_RMA_RECEIPTS·↳ SO_LINE_DETAILS·Explore OE module →
-
View: ICX_SO_RMA_MTL_INT_V 12.2.2
Obsolete
APPS.ICX_SO_RMA_MTL_INT_V·↳ MTL_SO_RMA_INTERFACE·↳ MTL_SO_RMA_RECEIPTS·Explore ICX module →
-
View: SO_RMA_MTL_INT_V 12.2.2
APPS.SO_RMA_MTL_INT_V·↳ MTL_SO_RMA_INTERFACE·↳ MTL_SO_RMA_RECEIPTS·Explore OE module →
-
View: ICX_SO_RMA_MTL_INT_V 12.1.1
Obsolete
APPS.ICX_SO_RMA_MTL_INT_V·↳ MTL_SO_RMA_INTERFACE·↳ MTL_SO_RMA_RECEIPTS·Explore ICX module →
-
APPS.SO_RMA_MTL_INT_DETAIL_V·↳ MTL_SO_RMA_INTERFACE·↳ MTL_SO_RMA_RECEIPTS·↳ SO_LINE_DETAILS·Explore OE module →
-
PACKAGE: APPS.OE_CANCEL 12.2.2
-
VIEW: APPS.SO_RMA_MTL_INT_V 12.2.2
-
PACKAGE BODY: APPS.OE_CANCEL 12.2.2
-
VIEW: APPS.SO_RMA_MTL_INT_V 12.1.1
-
APPS.OE_QUERY SQL Statements 12.2.2
-
PACKAGE BODY: APPS.OE_CANCEL 12.1.1
-
PACKAGE: APPS.OE_CANCEL 12.1.1