Results for “ar_sum_ref_event_hist”

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

Overview

The AR_SUM_REF_EVENT_HIST table is a transient staging table in the Oracle Receivables (AR) module of Oracle E-Business Suite. It temporarily stores the history of all AR business events raised by various transactional activities while the Refresh AR Transactions Summary Tables concurrent program executes. The table acts as an internal event buffer that tracks which transactional records—invoices, receipts, applications, adjustments, and payment schedules—have been affected during a summary refresh run, allowing the concurrent program to reconcile and reprocess the Receivables summary tables (such as RA_CUSTOMER_TRX_SUMMARY and related aggregates) consistently.

Because the table holds intermediate processing state rather than persistent business data, its contents are populated and consumed within the lifetime of the refresh concurrent request. Records are typically identified by REQUEST_ID, enabling parallel or overlapping program runs to be isolated from one another. From a heuristic Data Vault modeling perspective, the metadata classifies this object as standalone, meaning it does not participate in a formal hub/link/satellite structure; its single foreign key to CS_KB_HISTORIES_B suggests a lightweight association rather than a fully modeled dimensional relationship. Treat this classification as a modeling suggestion rather than a strict architectural mandate.

Key Information Stored

The documented physical schema for release 12.2.2 exposes 15 columns in the AR schema. The most operationally significant columns are:

• BUSINESS_EVENT_NAME — identifies the type of AR business event raised (for example, invoice creation, receipt application, or adjustment).
• EVENT_KEY — a correlation key that ties the event row back to the originating transaction class.
• REQUEST_ID — the concurrent request identifier of the Refresh AR Transactions Summary Tables run that created the row; this is the primary scoping key for processing and cleanup.
• CUSTOMER_TRX_ID — the invoice or credit memo affected by the event.
• CASH_RECEIPT_ID — the receipt associated with the event.
• RECEIVABLE_APPLICATION_ID — the application linking a receipt to a transaction.
• ADJUSTMENT_ID — the adjustment record involved, where applicable.
• PAYMENT_SCHEDULE_ID — the installment or schedule line affected.
• HISTORY_ID — foreign key to CS_KB_HISTORIES_B, linking the event to a knowledge-base history record.
• PROCESSED_FLAG — indicates whether the row has already been consumed by the summary refresh logic.

The table also carries the standard EBS audit columns (CREATION_DATE, CREATED_BY, LAST_UPDATE_DATE, LAST_UPDATE_BY, LAST_UPDATE_LOGIN). No standalone surrogate numeric primary key is documented; the transactional identifiers (REQUEST_ID together with the business event and entity columns) function as the effective composite key used to locate rows during processing.

Common Use Cases and Queries

The principal use of AR_SUM_REF_EVENT_HIST is diagnostic. DBAs and technical consultants query it to determine which transactions were flagged during a summary refresh run, particularly when the concurrent program terminates abnormally or when summary figures appear inconsistent. A representative query lists pending events for a specific request:

• SELECT BUSINESS_EVENT_NAME, CUSTOMER_TRX_ID, CASH_RECEIPT_ID, PROCESSED_FLAG FROM AR.AR_SUM_REF_EVENT_HIST WHERE REQUEST_ID = :request_id;
• Counting events by type to verify the refresh workload: SELECT BUSINESS_EVENT_NAME, COUNT(*) FROM AR.AR_SUM_REF_EVENT_HIST WHERE REQUEST_ID = :request_id GROUP BY BUSINESS_EVENT_NAME;
• Identifying unprocessed rows: SELECT * FROM AR.AR_SUM_REF_EVENT_HIST WHERE PROCESSED_FLAG = 'N';

Because the table is transient, it should not be used as a reporting source. Rows corresponding to completed requests are eligible for housekeeping, and unusually large residual volumes usually indicate a failed or long-running summary refresh request.

Related Objects

The most relevant dependency is the foreign key from AR_SUM_REF_EVENT_HIST.HISTORY_ID to CS_KB_HISTORIES_B, which links event audit rows to the knowledge-base history framework. The transactional entity columns reference the core Receivables entities that the summary refresh processes: CUSTOMER_TRX_ID joins to RA_CUSTOMER_TRX_ALL, CASH_RECEIPT_ID to AR_CASH_RECEIPTS_ALL, RECEIVABLE_APPLICATION_ID to AR_RECEIVABLE_APPLICATIONS_ALL, ADJUSTMENT_ID to AR_ADJUSTMENTS_ALL, and PAYMENT_SCHEDULE_ID to AR_PAYMENT_SCHEDULES_ALL. The concurrent program Refresh AR Transactions Summary Tables (and its dependent summary tables) is the primary consumer of these event rows, using REQUEST_ID to correlate processing across the run.