Search Results ra_cm_request_lines_u1

Overview

The RA_CM_REQUEST_LINES_ALL table in the AR (Receivables) schema stores the individual transaction lines that a customer selected when submitting a credit memo request through the Dispute A Bill feature of iReceivables (referred to as AR Online in Release 11). Each row represents one specific line-level credit request associated with a parent credit memo request, capturing the transaction line identifier and the extended amount of the underlying transaction line. The table contains as many rows as there are selected line-level credit requests for a given credit memo request header.

From a Data Vault modeling perspective, the heuristic classification places this object in the satellite-leaning category. This reflects its role as a dependent structure that records descriptive detail and qualifying context about credit memo requests rather than acting as an independent business hub. The table is owned by the AR schema, carries FND Design Data metadata, and is marked VALID. Its storage resides in the APPS_TS_TX_DATA tablespace with a PCT Free of 10 and a companion unique index in APPS_TS_TX_IDX. The documented physical schema in ETRM 12.2.2 lists 64 columns, the majority of which are descriptive interface and attribute segments.

Key Information Stored

The table is anchored by a composite primary key, RA_CM_REQUEST_LINES_PK, defined on REQUEST_ID and CUSTOMER_TRX_LINE_ID. A corresponding unique index, RA_CM_REQUEST_LINES_U1, enforces the same column pair over APPS_TS_TX_IDX. These two columns therefore function together as the governing identifier for each row and represent the documented business-key candidate.

• REQUEST_ID – Concurrent Program who column identifying the concurrent request that last updated the row; foreign key to FND_CONCURRENT_REQUESTS.REQUEST_ID, and part of the primary key.
• CUSTOMER_TRX_LINE_ID – The transaction line identifier; part of the primary key and a foreign key to RA_CUSTOMER_TRX_LINES_ALL.
• EXTENDED_AMOUNT – The transaction line amount credited.
• QUANTITY – Quantity credited on the line.
• PRICE – Price per unit.
• ORG_ID – Organization identifier, supporting multi-org partitioning.
• INTERFACE_LINE_CONTEXT and INTERFACE_LINE_ATTRIBUTE1 through INTERFACE_LINE_ATTRIBUTE15 – Descriptive flexfield-style interface segments used to carry additional line context.
• ATTRIBUTE_CATEGORY and ATTRIBUTE1 through ATTRIBUTE15 – Standard descriptive attribute columns.
• LAST_UPDATE_DATE, LAST_UPDATED_BY, CREATION_DATE, CREATED_BY, LAST_UPDATE_LOGIN – Standard Who columns recording creation and update audit information, with foreign keys to FND_USER and FND_LOGINS.

Global attribute columns (GLOBAL_ATTRIBUTE1 through GLOBAL_ATTRIBUTE20 and GLOBAL_ATTRIBUTE_CATEGORY) provide further extensibility for localization or cross-module data capture.

Common Use Cases and Queries

Typical scenarios include reconciling credits generated through Dispute A Bill against the underlying transaction lines, auditing credit memo request activity, and reporting on disputed line amounts. A common query joins this table to its parent transaction lines to retrieve the disputed amount and line context:

• Joining RA_CM_REQUEST_LINES_ALL to RA_CUSTOMER_TRX_LINES_ALL on CUSTOMER_TRX_LINE_ID to obtain the disputed transaction line detail alongside the credited EXTENDED_AMOUNT, QUANTITY, and PRICE.
• Aggregating EXTENDED_AMOUNT by REQUEST_ID to total the value of a given credit memo request.
• Filtering by ORG_ID to report line-level credit requests within a specific operating unit.
• Auditing rows using CREATION_DATE, CREATED_BY, and LAST_UPDATE_DATE to trace when line-level credit requests were submitted and by which user.
• Identifying orphaned or unmatched lines by left-joining to RA_CUSTOMER_TRX_LINES_ALL and isolating rows where the transaction line is absent.

Related Objects

The most significant relationships are defined by the documented foreign keys and primary key structure:

• AR.RA_CUSTOMER_TRX_LINES_ALL – Referenced via CUSTOMER_TRX_LINE_ID; the primary parent holding transaction line detail.
• FND_CONCURRENT_REQUESTS – Referenced via REQUEST_ID; identifies the concurrent program that last touched the row.
• FND_USER – Referenced via CREATED_BY and LAST_UPDATED_BY; provides user audit context.
• FND_LOGINS – Referenced via LAST_UPDATE_LOGIN; provides operating system login context.
• The parent credit memo request record, keyed by REQUEST_ID, logically complements the line-level detail stored here.

Together these objects support the Dispute A Bill credit request flow, with RA_CM_REQUEST_LINES_ALL serving as the line-level detail store linked directly to the transaction lines being disputed.