Results for “unit_code”

AI-generated from documented ETRM metadata — verify critical details on the linked pages.

Overview

MTL_SO_RMA_RECEIPTS is a table owned by the INV (Inventory) schema in Oracle E-Business Suite. Per the ETRM metadata, the object carries the status VALID but is explicitly documented as obsolete under the new Order Management system. Its sole documented purpose is to support data migration from the legacy structure into the replacement Order Management model, holding RMA receipt transactions. In other words, it is a legacy staging and migration artifact rather than an active transactional table in current 12.1.1 and 12.2.2 implementations.

From a Data Vault modeling perspective, the metadata's heuristic classification identifies this object as a link. This is a reasonable modeling suggestion: the table sits at the intersection of an RMA interface record, an inventory item, and an organization, and its foreign keys express those associations rather than describing a single business entity over time. The 21 documented columns combine a surrogate key, reference keys, quantity and date facts, and a small set of descriptive attributes, which is consistent with a link table augmented with lightweight descriptive payload.

Key Information Stored

The documented physical schema contains 21 columns. The most significant are:

• RMA_RECEIPT_ID — the surrogate primary key, enforced by MTL_SO_RMA_RECEIPTS_PK. It is also the single column of the unique index MTL_SO_RMA_RECEIPTS_U1, which makes it the documented business-key candidate.
• RMA_INTERFACE_ID — foreign key to MTL_SO_RMA_INTERFACE, tying each receipt row back to its interface record.
• INVENTORY_ITEM_ID — foreign key to MTL_SYSTEM_ITEMS_B, identifying the returned item.
• ORGANIZATION_ID — the inventory organization in which the receipt occurred; it forms part of the composite reference to MTL_SYSTEM_ITEMS_B.
• RECEIVED_QUANTITY and ACCEPTED_QUANTITY — the quantities received and subsequently accepted.
• RECEIPT_DATE — the transaction date for the RMA receipt.
• LOT_NUMBER — lot control reference for the received item, where lot-controlled.
• UNIT_CODE — the unit of measure code applicable to the received quantity.
• RETURN_SUBINVENTORY_NAME — the subinventory into which the return is directed.
• INSPECTION_COMMENTS — free-text remarks recorded during inspection.
• CLOSED_FLAG — indicates whether the receipt line is closed.
• REQUEST_ID, PROGRAM_APPLICATION_ID, PROGRAM_ID, PROGRAM_UPDATE_DATE — the standard concurrent program audit columns recording the process that created or updated the row.
• CREATED_BY, CREATION_DATE, LAST_UPDATED_BY, LAST_UPDATE_DATE, LAST_UPDATE_LOGIN — the standard Oracle Applications who-columns for row-level auditing.

The surrogate key RMA_RECEIPT_ID should not be conflated with a natural business identifier; the unique index is documented on the same column, so no separate composite business key is defined in the metadata.

Common Use Cases and Queries

Because the table is obsolete and migration-only, practical usage is limited to archaeology of legacy RMA receipt data, reconciliation during or after migration, and reporting on historical returns. Queries typically join the table to its foreign-key targets:

• Reconciling migrated rows against the source interface: join MTL_SO_RMA_RECEIPTS to MTL_SO_RMA_INTERFACE on RMA_INTERFACE_ID and compare RECEIVED_QUANTITY against the replacement model.
• Item-level return history: join to MTL_SYSTEM_ITEMS_B on INVENTORY_ITEM_ID and ORGANIZATION_ID to resolve item and organization descriptions.
• Receipt timing and acceptance reporting: filter on RECEIPT_DATE and compare RECEIVED_QUANTITY with ACCEPTED_QUANTITY to quantify rejected or short receipts.
• Identifying open versus closed legacy receipts using CLOSED_FLAG.

A representative pattern is SELECT r.RMA_RECEIPT_ID, r.RECEIPT_DATE, r.RECEIVED_QUANTITY, r.ACCEPTED_QUANTITY FROM MTL_SO_RMA_RECEIPTS r WHERE r.ORGANIZATION_ID = :org AND r.RECEIPT_DATE >= :from_date, with an outer join to MTL_SYSTEM_ITEMS_B for item detail. Queries should always be restricted by organization and date, given the table's migration scope.

Related Objects

• MTL_SO_RMA_INTERFACE — referenced via RMA_INTERFACE_ID; the parent interface record for each receipt.
• MTL_SYSTEM_ITEMS_B — referenced via INVENTORY_ITEM_ID and ORGANIZATION_ID; supplies item master definitions.
• MTL_SO_RMA_RECEIPTS_PK and MTL_SO_RMA_RECEIPTS_U1 — the primary key constraint and unique index defined on RMA_RECEIPT_ID.
• Adjacent legacy return tables such as RMA interface and RMA receipt staging structures that feed the migration into the new Order Management model.
• Oracle Order Management replacement objects that receive the migrated RMA receipt data, which are the effective successors to this table.

New development should not target MTL_SO_RMA_RECEIPTS; the current Order Management data model should be used instead.