Search Results ar_statement_headers_pk

Overview

The AR_STATEMENT_HEADERS table is a core data object within the Oracle E-Business Suite Receivables (AR) module, specifically for versions 12.1.1 and 12.2.2. As defined in the ETRM metadata, it functions as an interim table for statement header information. This indicates its primary role is to serve as a staging or working table during the generation and processing of customer statements. It temporarily holds header-level data that is consolidated from various transactional sources before the final statement is formatted and dispatched, ensuring data integrity and facilitating the batch processing logic inherent to the AR statement cycle.

Key Information Stored

The table's structure is centered on identifying the customer and the precise delivery location for the statement. Its primary key is a composite of CUSTOMER_ID and SEND_TO_ADDRESS_ID, which uniquely identifies a statement header record. The CUSTOMER_ID column links to the Trading Community Architecture (TCA) customer definition (HZ_CUST_ACCOUNTS). The SEND_TO_ADDRESS_ID specifies the exact customer site address for statement delivery, referencing the HZ_CUST_ACCT_SITES_ALL table. A third key column, SITE_USE_ID, provides further granularity by linking to the HZ_CUST_SITE_USES_ALL table, which defines the specific "Bill To" site use associated with the address. Together, these columns ensure statements are correctly targeted based on the customer's account and site-level configuration.

Common Use Cases and Queries

The primary use case for this table is supporting the "Print Statements" process. A typical query might involve joining to TCA tables to retrieve a list of customers and their designated statement addresses that are queued for processing. For troubleshooting or reporting on statement generation batches, one might query this table to verify which customer-site combinations were selected. A sample SQL pattern to analyze statement headers for a specific customer would be:

• SELECT ash.customer_id, ash.send_to_address_id, hca.account_number, hcsua.location
• FROM ar_statement_headers ash,
• hz_cust_accounts hca,
• hz_cust_site_uses_all hcsua
• WHERE ash.customer_id = hca.cust_account_id
• AND ash.site_use_id = hcsua.site_use_id
• AND hca.account_number = '&CUSTOMER_NUMBER';

Related Objects

As per the provided foreign key constraints, AR_STATEMENT_HEADERS has direct dependencies on three critical TCA tables: HZ_CUST_ACCOUNTS, HZ_CUST_ACCT_SITES_ALL, and HZ_CUST_SITE_USES_ALL. This underscores its integration with the centralized customer model. It is logically related to other AR interim tables, such as AR_STATEMENT_LINES, which would hold the detailed transaction lines for each header. The table is primarily accessed and populated by internal Receivables APIs and concurrent programs (e.g., the "Print Statements" program) rather than through direct user interaction. The primary key constraint AR_STATEMENT_HEADERS_PK enforces the fundamental rule that a statement header is defined by a unique customer and delivery address combination.