Results for “is_it_a_reprint”

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

Overview

AR_STATEMENTS_HISTORY_ALL is a Receivables (AR) module table in the Oracle E-Business Suite that stores the historical record of every customer statement generated by the application. Statements are the periodic documents produced by the AR Statement process and delivered to customers summarizing open balances, aging, and finance charges. This table captures the parameters and totals used at the time each statement was produced, forming an audit and reprint trail that is independent of the current state of the customer's transactions.

The table resides in the AR schema and is documented as VALID in ETRM for both 12.1.1 and 12.2.2, with 24 columns at the physical level. The "_ALL" suffix indicates the table is partitioned by operating unit via the ORG_ID column, which is standard for multi-org enabled Receivables data. From a Data Vault modeling perspective, the mined foreign-key structure suggests classifying this object as a link table: it connects customer, address, and statement cycle dimensions while carrying the transactional facts of a generated statement.

Key Information Stored

The table's identifying and business content revolves around the customer, the delivery address, and the statement run itself. The most significant columns are:

• CUSTOMER_ID — foreign key to HZ_CUST_ACCOUNTS identifying the customer account for whom the statement was produced.
• SEND_TO_ADDRESS_ID — foreign key to HZ_CUST_ACCT_SITES_ALL, the address to which the statement was sent.
• SITE_USE_ID — foreign key to HZ_CUST_SITE_USES_ALL, the site use associated with the statement.
• STATEMENT_CYCLE_ID — foreign key to AR_STATEMENT_CYCLES, the statement cycle that drove the run.
• REMIT_TO_ADDRESS_ID — address used for remittance on the statement.
• BILL_TO_LOCATION — bill-to location identifier captured at generation time.
• STATEMENT_DATE — the date on which the statement was produced.
• CURRENCY_CODE — the currency in which statement amounts were expressed.
• TOTAL_AMOUNT_DUE — the total amount due reported on the statement.
• FINANCE_CHARGES — finance charges applied and shown on the statement.
• MIN_STATEMENT_AMOUNT — the minimum threshold used to decide statement eligibility.
• MONTHLY_INTEREST_RATE — the interest rate applied for finance charge computation.
• STATEMENT_TYPE — the category of statement generated.
• CREDIT_BALANCE_STATEMENTS — flag indicating whether credit-balance statements were included.
• IS_IT_A_REPRINT — indicates whether this record represents a reprint rather than an original generation.

Audit columns (LAST_UPDATED_BY, LAST_UPDATE_DATE, CREATED_BY, CREATION_DATE, LAST_UPDATE_LOGIN) and the multi-org column ORG_ID complete the row. A notable internal identifier, LINE_CLUSTER_ID, along with CUST_CUSTOMER_PROFILE_ID and SITE_CUSTOMER_PROFILE_ID, ties the record to the profile settings in effect at generation time.

Common Use Cases and Queries

Typical scenarios include auditing which statements were produced for a given customer or cycle, reproducing a historical statement for a customer dispute, and reporting on finance charges and balances billed over a period. Because the table stores a snapshot, it is the authoritative source for "what the customer actually received."

• Listing statements for a customer within a date range:

SELECT statement_date, total_amount_due, finance_charges, currency_code
FROM   ar_statements_history_all
WHERE  customer_id = :customer_id
AND    statement_date BETWEEN :from_date AND :to_date
ORDER BY statement_date DESC;

• Identifying reprints versus originals for a cycle:

SELECT h.customer_id, h.statement_date, h.is_it_a_reprint
FROM   ar_statements_history_all h, ar_statement_cycles c
WHERE  h.statement_cycle_id = c.statement_cycle_id
AND    h.org_id = :org_id;

• Aggregating finance charges by currency and cycle for reporting.

Related Objects

The documented foreign keys establish the primary join paths for this table:

• HZ_CUST_ACCOUNTS — joined on AR_STATEMENTS_HISTORY_ALL.CUSTOMER_ID to HZ_CUST_ACCOUNTS.CUST_ACCOUNT_ID.
• HZ_CUST_ACCT_SITES_ALL — joined via SEND_TO_ADDRESS_ID for delivery address resolution.
• HZ_CUST_SITE_USES_ALL — joined via SITE_USE_ID for site use context.
• AR_STATEMENT_CYCLES — joined via STATEMENT_CYCLE_ID, defining the cycle rules used.

In practice these are complemented by AR_CASH_RECEIPTS, AR_PAYMENT_SCHEDULES_ALL, and the Statements concurrent program output, which together let report developers trace a generated statement back to the underlying transactions. Together these relationships make AR_STATEMENTS_HISTORY_ALL the linkage point between customer master data and the statement generation process.