Search Results ar_activity_details_u1

Overview

AR.AR_ACTIVITY_DETAILS is a transactional table in the Oracle E-Business Suite Receivables (AR) schema that stores receivable activities at the invoice line level. It is the persistence layer for the line-level applications feature, which allows receipt applications, adjustments, and related financial events to be recorded against individual transaction lines rather than only at the header level. Each row represents the computed activity position of a receivable line with respect to a specific source document such as a cash receipt or an invoice line.

The ETRM metadata classifies this object heuristically as standalone under the Data Vault model, meaning it does not present the classic hub-and-satellite split seen in conformed warehouses. As a modeling suggestion, this table behaves most like a link-plus-satellite hybrid: LINE_ID acts as the unique row identifier, while CUSTOMER_TRX_LINE_ID and CASH_RECEIPT_ID function as the participating business keys connecting transaction lines to receipts. The table resides in the APPS_TS_TX_DATA tablespace with a PCT Free of 10, and its indexes in APPS_TS_TX_IDX reflect the high-frequency access paths used by AutoInvoice, Receipts, and the revenue adjustment processes.

Key Information Stored

The physical schema documents 48 columns. The most operationally significant are:

• LINE_ID – surrogate primary key (AR_ACTIVITY_DETAILS_PK) and the column behind the unique index AR_ACTIVITY_DETAILS_U1. This is the single mandatory uniqueness guarantee on the table.
• CASH_RECEIPT_ID – foreign reference to the applied receipt; indexed by N1 and N3.
• CUSTOMER_TRX_LINE_ID – the invoice line being affected; indexed by N2 and N4.
• SOURCE_ID / SOURCE_TABLE – polymorphic discriminator identifying the originating document and table; both appear in indexes N1 and N2.
• CURRENT_ACTIVITY_FLAG – marks the row as the active current activity for a given receipt or line; used in indexes N3 and N4.
• ALLOCATED_RECEIPT_AMOUNT – the receipt amount applied to the line.
• AMOUNT, TAX, FREIGHT, CHARGES – the corresponding revenue, tax, freight, and charges components of the invoice line.
• LINE_DISCOUNT, TAX_DISCOUNT, FREIGHT_DISCOUNT – discount allocations applied to each revenue component.
• LINE_BALANCE, TAX_BALANCE – remaining balance on the revenue and tax portions of the line after application.
• APPLY_TO – the transaction line number when the application targets revenue or tax specifically.
• OFFSET_REC_FLAG – identifies offsetting (contra) activity rows, typically created when a receipt application generates a corresponding receivable adjustment.
• OBJECT_VERSION_NUMBER – optimistic locking column used by the OAF/BC4J stack.
• GROUP_ID – used by concurrent programs for run-scoped grouping.
• ATTRIBUTE_CATEGORY and ATTRIBUTE1–15 – Descriptive Flexfield segments.
• Standard WHO columns (CREATION_DATE, CREATED_BY, LAST_UPDATE_DATE, LAST_UPDATED_BY, LAST_UPDATE_LOGIN) and CREATED_BY_MODULE for audit and diagnostics.

Common Use Cases and Queries

Typical usage centres on reconciliation and application analysis. Reports commonly reconstruct the receipt-to-line application trail, identify lines that remain partially paid, and compare billed amounts to applied amounts.

• Applications against a specific receipt: filter on CASH_RECEIPT_ID and CURRENT_ACTIVITY_FLAG = 'Y' via AR_ACTIVITY_DETAILS_N3 to retrieve the current application position without scanning superseded rows.
• Open line balance reporting: aggregate LINE_BALANCE and TAX_BALANCE by CUSTOMER_TRX_LINE_ID to find under-applied or over-applied invoice lines.
• Discount analysis: sum LINE_DISCOUNT, TAX_DISCOUNT, FREIGHT_DISCOUNT by cash receipt to audit early-payment discount utilisation.
• Offset identification: query OFFSET_REC_FLAG to separate genuine applications from contra entries generated during adjustment processing.
• Source tracing: join on SOURCE_ID and SOURCE_TABLE to locate the originating document where the application was not driven by a receipt, for example adjustments.

A representative query pattern is:

SELECT LINE_ID, CASH_RECEIPT_ID, CUSTOMER_TRX_LINE_ID, ALLOCATED_RECEIPT_AMOUNT, LINE_BALANCE, TAX_BALANCE FROM AR.AR_ACTIVITY_DETAILS WHERE CUSTOMER_TRX_LINE_ID = :line_id AND CURRENT_ACTIVITY_FLAG = 'Y';

Because all financial columns are NUMBER with no declared scale, always apply appropriate ROUND or currency formatting in reporting layers.

Related Objects

The table connects to the wider Receivables schema through its indexed business keys. The most significant related objects are:

• AR_CASH_RECEIPTS – joined on CASH_RECEIPT_ID; supplies receipt number, date, amount, and status for activity rows.
• AR_CASH_RECEIPT_HISTORY – traces status transitions of the same receipt identified by CASH_RECEIPT_ID.
• RA_CUSTOMER_TRX_LINES – joined on CUSTOMER_TRX_LINE_ID; provides line number, description, quantity, and unit price.
• RA_CUSTOMER_TRX – header context for the line, reached via RA_CUSTOMER_TRX_LINES.
• AR_ADJUSTMENTS and AR_RECEIVABLE_APPLICATIONS – the upstream adjustment and application records whose effects are reflected here.
• RA_CUST_TRX_LINE_GL_DIST – line-level accounting distributions reconciled against activity balances.
• AR_ACTIVITY_DETAILS related views and the line-level applications APIs exposed through the Receipts open interface and Receivables Adjustments API, which maintain rows in this table as applications are created, updated, or reversed.

No enforcing foreign keys are documented against this table in the ETRM metadata, so referential integrity to the parent Receivables entities is maintained procedurally by the application layer rather than by the database.