Results for “ar_activity_details_pk”

AI-generated from documented ETRM metadata — verify critical details on the linked pages.

Overview

AR_ACTIVITY_DETAILS is a Receivables (AR) module table that stores line-level detail for receivable activities. In Oracle EBS 12.1.1 and 12.2.2, it is owned by the AR schema and is documented with 48 columns. The table captures the individual components that make up an activity applied against a transaction line — for example, cash receipt applications with the amount, tax, freight, charges, and discount portions recorded separately. Its primary key is AR_ACTIVITY_DETAILS_PK, defined on the LINE_ID column, and a unique index AR_ACTIVITY_DETAILS_U1 (LINE_ID) confirms LINE_ID as the business-key candidate. Based on the FK structure mined into the metadata, the object is classified heuristically as standalone; as a modeling suggestion, this positions it as neither a pure hub nor link, but rather a transactional/satellite-style detail table dependent on other AR entities through logical rather than enforced foreign keys.

Key Information Stored

The surrogate primary key is LINE_ID, which uniquely identifies each activity detail row. The most significant business columns include:

• CASH_RECEIPT_ID — Identifies the cash receipt associated with the activity line, linking the detail to the receipt application.
• CUSTOMER_TRX_LINE_ID — Identifies the customer transaction line to which the activity amount applies.
• ALLOCATED_RECEIPT_AMOUNT — The portion of the receipt amount allocated to this detail line.
• AMOUNT — The primary monetary value of the activity detail.
• TAX, FREIGHT, CHARGES — Component amounts distributed across the line.
• LINE_DISCOUNT, TAX_DISCOUNT, FREIGHT_DISCOUNT — Discount amounts broken out by component.
• LINE_BALANCE, TAX_BALANCE — Remaining balances after the activity is applied.
• APPLY_TO — Determines the target of the application logic.
• CURRENT_ACTIVITY_FLAG — Indicates whether the row represents the current active activity.
• OFFSET_REC_FLAG — Flags offset receipt handling.
• SOURCE_ID, SOURCE_TABLE — Point to the originating record and its source table.
• LINE_ID — Surrogate primary key and business-key candidate per unique index AR_ACTIVITY_DETAILS_U1.
• Standard audit columns (CREATION_DATE, CREATED_BY, LAST_UPDATE_DATE, LAST_UPDATED_BY, LAST_UPDATE_LOGIN, OBJECT_VERSION_NUMBER, CREATED_BY_MODULE) and the ATTRIBUTE1–15 / ATTRIBUTE_CATEGORY descriptive flexfield columns support concurrency control and extensibility.

Common Use Cases and Queries

AR_ACTIVITY_DETAILS is primarily queried for reconciliation and reporting of cash receipt applications. A common pattern joins receipt details to transaction lines to explain how a receipt was applied across tax, freight, and charges:

SELECT a.line_id, a.cash_receipt_id, a.customer_trx_line_id,
       a.amount, a.tax, a.freight, a.charges,
       a.line_discount, a.line_balance, a.current_activity_flag
FROM   ar.ar_activity_details a
WHERE  a.cash_receipt_id = :receipt_id;

Reporting use cases include unapplied or on-account receipt analysis, discount and adjustment reporting, balance trending by transaction line, and audit queries filtered on CURRENT_ACTIVITY_FLAG to isolate the effective activity row. The SOURCE_ID and SOURCE_TABLE columns support lineage tracing back to originating activity records.

Related Objects

The metadata documents AR_ACTIVITY_DETAILS as standalone (no enforced foreign keys in the mined structure), but it logically references key AR objects through its identifier columns:

• AR_CASH_RECEIPTS — joined via AR_ACTIVITY_DETAILS.CASH_RECEIPT_ID.
• AR_CASH_RECEIPT_HISTORY — related through the cash receipt activity trail.
• RA_CUSTOMER_TRX_LINES_ALL — joined via CUSTOMER_TRX_LINE_ID.
• RA_CUSTOMER_TRX_ALL — accessed through the parent transaction line.
• AR_RECEIVABLE_APPLICATIONS_ALL — the application record that the detail supports.
• AR_ADJUSTMENTS_ALL — activity adjustments affecting line balances.
• AR_ACTIVITY_DETAILS_PK / AR_ACTIVITY_DETAILS_U1 — the primary key constraint and unique index on LINE_ID.

These relationships make the table a central reference for tracing how receipt amounts, discounts, and component charges are distributed at the transaction-line level within Receivables.