Search Results ra_cm_requests_pk

Overview

RA_CM_REQUESTS_ALL is the Receivables (AR) transaction table that stores pending and approved credit memo requests within Oracle E-Business Suite 12.1.1 and 12.2.2. It acts as the staging and approval container for credit memos before or as they are applied against customer transactions. Each row represents a request to issue a credit memo, capturing the requesting customer transaction, the resulting credit memo transaction, approval workflow status, and the monetary breakdown of the requested credit. The table is owned by the AR schema and is documented as VALID in the ETRM 12.2.2 physical schema with 90 columns.

From a Data Vault modeling perspective, the mined foreign-key structure classifies RA_CM_REQUESTS_ALL heuristically as a link table. This is appropriate because it principally resolves relationships between two RA_CUSTOMER_TRX_ALL records — the original transaction and the credit memo transaction — while carrying descriptive attributes and status information. Analysts designing a dimensional or Data Vault layer should treat REQUEST_ID and CUSTOMER_TRX_ID as the composite linkage and isolate descriptive payload attributes into a satellite if finer granularity is required.

Key Information Stored

The table's primary key is documented as RA_CM_REQUESTS_PK, defined on the composite of REQUEST_ID and CUSTOMER_TRX_ID. A separate unique index, RA_CM_REQUESTS_U1, is defined on REQUEST_ID alone, making it the strongest business-key candidate for uniquely identifying a request independently of its transaction association.

• REQUEST_ID — surrogate identifier and unique business key for the credit memo request.
• CUSTOMER_TRX_ID — foreign key to RA_CUSTOMER_TRX_ALL, identifying the original transaction being credited.
• CM_CUSTOMER_TRX_ID — foreign key to RA_CUSTOMER_TRX_ALL, identifying the generated credit memo transaction.
• STATUS — the request lifecycle state (for example, pending or approved).
• APPROVAL_DATE — timestamp when the request was approved.
• CM_REASON_CODE — the reason classification for the credit memo.
• TOTAL_AMOUNT, LINE_AMOUNT, TAX_AMOUNT, FREIGHT_AMOUNT — monetary components of the requested credit.
• LINE_CREDITS_FLAG — indicates whether the credit is applied at line level.
• COMMENTS and INTERNAL_COMMENT — customer-facing and internal annotations.
• ORG_ID — the operating unit, supporting multi-org access control.
• DISPUTE_DATE and RESPONSIBILITY_ID — dispute tracking and the responsibility that owns the request.
• ORIG_TRX_NUMBER and TAX_EX_CERT_NUM — original transaction reference and tax exemption certificate.

Standard EBS audit columns (CREATION_DATE, CREATED_BY, LAST_UPDATE_DATE, LAST_UPDATED_BY, LAST_UPDATE_LOGIN) and the ATTRIBUTE, INTERFACE_HEADER_ATTRIBUTE, and GLOBAL_ATTRIBUTE flexfields are also present for extensibility.

Common Use Cases and Queries

Typical reporting scenarios include tracking the backlog of unapproved credit memo requests, measuring approval cycle time, and reconciling requests to their resulting credit memos. A representative query joining the request to both transaction roles is:

• SELECT r.REQUEST_ID, r.STATUS, r.TOTAL_AMOUNT, r.APPROVAL_DATE FROM RA_CM_REQUESTS_ALL r WHERE r.STATUS = 'PENDING' AND r.ORG_ID = :org_id;
• Join the original transaction: SELECT r.REQUEST_ID, t.TRX_NUMBER FROM RA_CM_REQUESTS_ALL r JOIN RA_CUSTOMER_TRX_ALL t ON r.CUSTOMER_TRX_ID = t.CUSTOMER_TRX_ID;
• Join the credit memo: ... JOIN RA_CUSTOMER_TRX_ALL cm ON r.CM_CUSTOMER_TRX_ID = cm.CUSTOMER_TRX_ID;
• Aggregate approval aging by CM_REASON_CODE for dispute and deduction analysis.

Because the table carries ORG_ID, queries must honor operating unit security, and reporting extracts should filter on STATUS and APPROVAL_DATE to bound large result sets.

Related Objects

• RA_CUSTOMER_TRX_ALL — referenced twice, via CUSTOMER_TRX_ID (original transaction) and CM_CUSTOMER_TRX_ID (credit memo transaction); the primary join target.
• RA_CUSTOMER_TRX_LINES_ALL — line-level detail of the associated transactions, joined through CUSTOMER_TRX_ID.
• RA_CM_REQUESTS_PK / RA_CM_REQUESTS_U1 — the primary and unique indexes governing access paths.
• AR Credit Memo approval workflow and AutoInvoice interface tables — process the request record into a finalized credit memo.
• FND_RESPONSIBILITY / multi-org views — resolve RESPONSIBILITY_ID and ORG_ID for security filtering.

These relationships establish RA_CM_REQUESTS_ALL as the central linkage between a disputed or incorrect transaction and the credit memo issued to resolve it.