Results for “matched_rect_adj_id”

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

Overview

AP_MATCHED_RECT_ADJ_ALL is a Payables-owned table in the AP schema that tracks receipts which have been modified after an invoice has already been matched to them. In Oracle EBS 12.1.1 and 12.2.2, it serves as the audit and reconciliation bridge between the Payables matching process and the Receiving (RCV) transaction model. When a receipt in Oracle Purchasing/Receiving is adjusted — quantity corrections, returns, or other modifications — after an AP invoice has been matched against it, this table records the linkage between the original (parent) RCV transaction and the resulting adjusted RCV transaction, preserving the history necessary for payables-to-receiving reconciliation, matching holds resolution, and audit reporting.

From a Data Vault modeling perspective, the mined FK structure suggests this object behaves as a link table. It does not store descriptive attributes about a single entity; instead it captures a relationship between two RCV_TRANSACTIONS records (parent and adjusted) plus the timing of that adjustment. This classification is a heuristic suggestion based on the two foreign keys pointing at RCV_TRANSACTIONS.

Key Information Stored

The table contains 14 documented columns. The most significant are:

• MATCHED_RECT_ADJ_ID — Surrogate primary key (AP_MATCHED_RECT_ADJ_ALL_PK) and the sole documented unique index (AP_MATCHED_RECT_ADJ_U1). Uniquely identifies each adjusted-receipt-to-match relationship.
• PARENT_RCV_TXN_ID — Foreign key to RCV_TRANSACTIONS. Identifies the original receipt transaction that was involved in the invoice match.
• ADJUSTED_RCV_TXN_ID — Foreign key to RCV_TRANSACTIONS. Identifies the new/adjusted receipt transaction created after the modification.
• ADJUSTED_DATE — The effective date on which the receipt adjustment was recorded.
• ORG_ID — Operating unit identifier, enabling multi-org (MOAC) security and reporting partitioning.
• CREATED_BY, CREATION_DATE — Standard WHO audit columns capturing who created the record and when.
• LAST_UPDATED_BY, LAST_UPDATE_DATE, LAST_UPDATE_LOGIN — Standard WHO columns tracking the most recent change.
• PROGRAM_ID, PROGRAM_APPLICATION_ID, REQUEST_ID, PROGRAM_UPDATE_DATE — Concurrent program context columns identifying the process that inserted or modified the row.

The surrogate key (MATCHED_RECT_ADJ_ID) is the only documented business-key candidate; no other column combination is enforced as unique, which is expected for a link-style relationship table.

Common Use Cases and Queries

Typical uses include:

• Auditing invoice-to-receipt match integrity when receiving transactions change post-match.
• Reconciling AP matching activity against RCV transaction history for month-end close.
• Investigating quantity-billed versus quantity-received discrepancies and related matching holds.
• Feeding reconciliation reports that compare original and adjusted receipt quantities by operating unit.

Sample query joining to the receiving transaction table:

SELECT m.MATCHED_RECT_ADJ_ID, m.PARENT_RCV_TXN_ID, m.ADJUSTED_RCV_TXN_ID,
  m.ADJUSTED_DATE, m.ORG_ID
FROM AP.AP_MATCHED_RECT_ADJ_ALL m
WHERE m.ORG_ID = :p_org_id
ORDER BY m.ADJUSTED_DATE DESC;

To compare parent and adjusted transactions:

SELECT m.MATCHED_RECT_ADJ_ID, p.TRANSACTION_ID parent_txn, a.TRANSACTION_ID adj_txn,
  m.ADJUSTED_DATE
FROM AP.AP_MATCHED_RECT_ADJ_ALL m
JOIN RCV.RCV_TRANSACTIONS p ON p.TRANSACTION_ID = m.PARENT_RCV_TXN_ID
JOIN RCV.RCV_TRANSACTIONS a ON a.TRANSACTION_ID = m.ADJUSTED_RCV_TXN_ID;

Related Objects

• RCV_TRANSACTIONS — Joined twice: via PARENT_RCV_TXN_ID and ADJUSTED_RCV_TXN_ID. This is the primary dependency, supplying receipt transaction details.
• AP_INVOICE_DISTRIBUTIONS_ALL — Holds the matched distributions; useful when relating an adjustment back to the invoice match.
• AP_INVOICES_ALL — Invoice headers associated with the matched distributions.
• PO_DISTRIBUTIONS_ALL — Purchase order distributions underlying the receipt and invoice match.
• RCV_SHIPMENT_HEADERS and RCV_SHIPMENT_LINES — Shipment context for the parent and adjusted transactions.
• AP_MATCHING_HOLDS / matching-related API tables — Consumed during Payables match validation and hold resolution logic.

The table is queried directly or through Payables matching views and concurrent reconciliation programs; there is no separate public API for direct DML, reinforcing its role as an internally maintained link record.