Search Results ra_cm_requests_u1

Overview

The AR.RA_CM_REQUESTS_ALL table stores credit memo requests submitted by customers through the Dispute A Bill feature of iReceivables (known as AR Online in Release 11). Receivables creates one row in this table for each request a customer submits, and each row carries the parameters required to initiate the Credit Memo Request Workflow. The table is owned by the AR schema, is registered in FND Design Data as AR.RA_CM_REQUESTS_ALL, and resides in the APPS_TS_TX_DATA tablespace with a PCT Free of 10.

The table records the nature of each dispute: the amount, the reason code, customer comments, and whether the request applies to specific invoice lines or to a header-level credit against the total line, tax, or freight. Functionally, it acts as the intake record between a customer-initiated dispute and the resulting credit memo created in Receivables. Based on the foreign key structure mined from the metadata, the heuristic Data Vault classification for this object is a link, since it connects a disputed transaction to a credit memo transaction and captures the request event between them.

Key Information Stored

The table contains 90 documented columns. The most significant are summarized below.

• REQUEST_ID — Surrogate identifier and part of the primary key. It is also documented as a concurrent program WHO column, a foreign key to FND_CONCURRENT_REQUESTS.REQUEST_ID. This is the column behind the unique index RA_CM_REQUESTS_U1 (UNIQUE, APPS_TS_TX_IDX).
• CUSTOMER_TRX_ID — The transaction identifier of the disputed transaction. Part of the composite primary key RA_CM_REQUESTS_PK (REQUEST_ID, CUSTOMER_TRX_ID) and a foreign key to RA_CUSTOMER_TRX_ALL.
• CM_CUSTOMER_TRX_ID — The credit memo identifier, populated once Receivables approves the request and creates the credit memo. Also a foreign key to RA_CUSTOMER_TRX_ALL.
• LINE_CREDITS_FLAG — Y indicates the credit request targets specific lines; N indicates a header-level credit request.
• LINE_AMOUNT, TAX_AMOUNT, FREIGHT_AMOUNT, and TOTAL_AMOUNT — Header-level credit amounts requested for the line, tax, freight, and total respectively.
• CM_REASON_CODE and COMMENTS — The reason for the credit request and free-text customer comments; INTERNAL_COMMENT holds internal remarks.
• STATUS and APPROVAL_DATE — Workflow status of the request and the date the request was approved.
• ORG_ID — Operating unit identifier for multi-org partitioning.
• URL, TRANSACTION_URL, ACTIVITIES_URL — Links used by the request pages.

The surrogate primary key is REQUEST_ID as the unique business-key candidate, but uniqueness in the table is enforced through the composite RA_CM_REQUESTS_PK combining REQUEST_ID and CUSTOMER_TRX_ID.

Common Use Cases and Queries

Dispute and credit memo analysis is the dominant use case. Analysts join this table to RA_CUSTOMER_TRX_ALL to reconcile the disputed invoice with the generated credit memo, and filter on STATUS or APPROVAL_DATE to measure dispute aging and approval throughput. The LINE_CREDITS_FLAG column supports reporting that distinguishes line-level disputes from header-level disputes, while CM_REASON_CODE supports root-cause analysis of customer complaints.

A typical query lists open credit memo requests with their disputed transaction number:

• SELECT r.REQUEST_ID, r.CUSTOMER_TRX_ID, r.CM_CUSTOMER_TRX_ID, r.STATUS, r.TOTAL_AMOUNT, r.CM_REASON_CODE FROM AR.RA_CM_REQUESTS_ALL r WHERE r.STATUS = 'PENDING' ORDER BY r.CREATION_DATE DESC;
• SELECT r.REQUEST_ID, t.TRX_NUMBER, cm.TRX_NUMBER CM_NUMBER, r.LINE_CREDITS_FLAG, r.TOTAL_AMOUNT FROM AR.RA_CM_REQUESTS_ALL r JOIN AR.RA_CUSTOMER_TRX_ALL t ON r.CUSTOMER_TRX_ID = t.CUSTOMER_TRX_ID LEFT JOIN AR.RA_CUSTOMER_TRX_ALL cm ON r.CM_CUSTOMER_TRX_ID = cm.CUSTOMER_TRX_ID;

Data extraction for iReceivables troubleshooting is another frequent pattern: because the URL columns store page links, support teams query them to reproduce a customer's dispute session. The ORG_ID column should be constrained in any multi-org reporting environment.

Related Objects

• AR.RA_CUSTOMER_TRX_ALL — Referenced twice: CUSTOMER_TRX_ID points to the disputed transaction, and CM_CUSTOMER_TRX_ID points to the resulting credit memo.
• FND_CONCURRENT_REQUESTS — REQUEST_ID is documented as a foreign key and WHO column referencing the concurrent program request that last updated the row.
• AR.RA_CM_REQUESTS_PK — The composite primary key constraint (REQUEST_ID, CUSTOMER_TRX_ID) that governs row uniqueness.
• AR.RA_CM_REQUESTS_U1 — The unique index on REQUEST_ID in APPS_TS_TX_IDX, the index referenced by the search term ra_cm_requests_u1.
• Credit Memo Request Workflow — Consumes the parameters captured in this table to initiate the approval and credit memo creation process.
• iReceivables Dispute A Bill (AR Online) — The originating application feature that inserts rows into this table.