Search Results ra_cm_request_lines_all

Overview

RA_CM_REQUEST_LINES_ALL is an Oracle Receivables (AR) transactional table that stores the line-level detail of pending and approved credit memo requests. In Oracle E-Business Suite 12.1.1 and 12.2.2, this table supports the Credit Memo Request workflow, in which users or external systems request that credit be issued against existing invoice lines. Each row represents a single request line, referencing the customer transaction line that is the subject of the credit request. The table is owned by the AR schema and carries a VALID status in the ETRM repository.

From a dimensional modeling perspective, the documented foreign key structure — a single reference to RA_CUSTOMER_TRX_LINES_ALL combined with descriptive and amount columns — suggests a satellite-leaning classification. In Data Vault terms, the composite key of REQUEST_ID and CUSTOMER_TRX_LINE_ID behaves as a link between the credit request and the underlying transaction line, while the surrounding attribute columns (amounts, quantities, prices, and descriptive flexfields) function as satellite payload. This classification is a heuristic derived from key topology rather than a declared EBS design intent.

Key Information Stored

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

• REQUEST_ID — Identifies the parent credit memo request header. Part of the composite primary key and a core correlation key across the request workflow.
• CUSTOMER_TRX_LINE_ID — References the invoice or credit transaction line to which the request pertains. Also part of the composite primary key and the sole documented foreign key.
• EXTENDED_AMOUNT — The total credit amount requested for the line, typically derived from quantity and price.
• QUANTITY — The number of units for which credit is requested on the line.
• PRICE — The unit price applied to the requested quantity.
• ORG_ID — The operating unit identifier supporting Multi-Org access control and reporting segregation.
• INTERFACE_LINE_CONTEXT and INTERFACE_LINE_ATTRIBUTE1–15 — Descriptive flexfield context and segments used to carry additional interface-line metadata.
• ATTRIBUTE_CATEGORY and ATTRIBUTE1–15 — The standard EBS descriptive flexfield columns for user-defined attributes.
• GLOBAL_ATTRIBUTE_CATEGORY and GLOBAL_ATTRIBUTE1–20 — Global descriptive flexfield columns that support country-specific and localization requirements.
• CREATED_BY, CREATION_DATE, LAST_UPDATED_BY, LAST_UPDATE_DATE, LAST_UPDATE_LOGIN — Standard WHO audit columns tracking record provenance.

The primary key, RA_CM_REQUEST_LINES_PK, is defined on (REQUEST_ID, CUSTOMER_TRX_LINE_ID). The unique index RA_CM_REQUEST_LINES_U1 covers the same two columns, indicating that the business key and the surrogate key coincide here; no independent surrogate identifier is documented.

Common Use Cases and Queries

The table is typically queried to report on outstanding credit requests, to reconcile requested credits against the transaction lines they target, and to drive the approval and credit memo creation process. A representative query lists open request lines with their associated transaction line:

• Join RA_CM_REQUEST_LINES_ALL to RA_CUSTOMER_TRX_LINES_ALL on CUSTOMER_TRX_LINE_ID to retrieve the invoice line context.
• Aggregate EXTENDED_AMOUNT by REQUEST_ID to calculate total requested credit per request header.
• Filter by ORG_ID to enforce operating unit security in custom reports.
• Use INTERFACE_LINE_ATTRIBUTE and ATTRIBUTE columns to surface flexfield-driven categorization in operational reporting.
• Compare QUANTITY and PRICE against the source transaction line to validate credit amounts prior to approval.

Typical SQL follows the pattern SELECT l.request_id, l.customer_trx_line_id, l.extended_amount, t.description FROM ra_cm_request_lines_all l, ra_customer_trx_lines_all t WHERE l.customer_trx_line_id = t.customer_trx_line_id AND l.org_id = :p_org_id.

Related Objects

• RA_CUSTOMER_TRX_LINES_ALL — Referenced through CUSTOMER_TRX_LINE_ID; the foreign key relationship is documented in the ETRM metadata.
• RA_CM_REQUESTS_ALL — The request header table expected to share the REQUEST_ID identifier with this line table.
• RA_CUSTOMER_TRX_ALL — Parent transaction header for the invoice or credit being referenced.
• RA_CUSTOMER_TRX_LINES — The non-_ALL view counterpart commonly used in reporting.
• AR_CREDIT_MEMO_API and related AR credit memo creation interfaces — Consume approved request lines when generating credit memos.
• RA_CM_REQUEST_LINES — The reporting view layered over the _ALL base table.