Search Results ar_standard_text




Overview
Explore in AI Chat

Overview

The AR.AR_STATEMENT_HEADERS table is an interim staging table used by Oracle Receivables during statement generation. When the Print Statements concurrent program is submitted, it populates this table with one row for each statement that will ultimately be produced. Each row is uniquely distinguished by a bill-to site and currency combination, meaning a single customer may appear multiple times if statements are generated across different currencies or ship-to addresses.

The table resides in the APPS_TS_TX_DATA tablespace with a PCT Free of 10. Its documented ETRM status is VALID, and it carries an FND Design Data registration of AR.AR_STATEMENT_HEADERS. Because the table is interim in nature, its contents are typically transient — rows are inserted, processed, printed, and purged by Receivables internal logic rather than being retained as permanent transactional history.

From a Data Vault modeling perspective, the heuristic classification mined from the foreign key structure is link. This reflects the fact that AR_STATEMENT_HEADERS primarily associates independent business entities — customers, addresses, and site uses — creating a relationship record rather than serving as a standalone hub or descriptive satellite. The composite primary key AR_STATEMENT_HEADERS_PK on (SEND_TO_ADDRESS_ID, CUSTOMER_ID) reinforces this associative role.

Key Information Stored

The table contains 47 documented columns spanning identifiers, aging buckets, error flags, and message text. The most significant grouping is as follows:

Business-key candidates emerge from the natural uniqueness of (SEND_TO_ADDRESS_ID, CUSTOMER_ID), which functions simultaneously as primary key and surrogate identifier. The surrogate key in the strict sense is CUSTOMER_ID paired with the address; no single-column surrogate identifier is documented.

Common Use Cases and Queries

The most frequent reporting scenario is diagnosing statement generation output — identifying customers whose statements contain errors or whose calculated balance differs from the stored total.

SELECT customer_id, send_to_address_id, total_amount_due,
       error_amount_different, error_no_lines
FROM   ar.ar_statement_headers
WHERE  request_id = :p_request_id;

Aging-bucket rollups can be produced by summing BUCKET1 through BUCKET5 by currency. Reconciliation queries join to HZ_CUST_ACCOUNTS to resolve customer names. Because rows are keyed by REQUEST_ID, historical reprints can be reconstructed for any specific Print Statements run.

Related Objects

  • HZ_CUST_ACCOUNTS — Joined on CUSTOMER_ID; provides the customer identity.
  • HZ_CUST_ACCT_SITES_ALL — Joined on SEND_TO_ADDRESS_ID; supplies the delivery address.
  • HZ_CUST_SITE_USES_ALL — Joined on SITE_USE_ID; defines the site use context for the statement.
  • AR_STATEMENT_LINES — Companion interim table holding the individual transaction lines belonging to each header.
  • AR_CUSTOMERS — Denormalized customer view frequently joined for statement reporting.
  • FND_CONCURRENT_REQUESTS — Joined on REQUEST_ID to trace the originating concurrent request.

Consult the AR_STATEMENT_HEADERS_PK constraint and the AR_STATEMENT_HEADERS_N1 / _N2 indexes when tuning purge or reporting queries against this interim object.