Results for “error_amount_different”

8 results




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

Overview

AR_STATEMENT_HEADERS is a Receivables (AR) module table in the Oracle E-Business Suite 12.1.1 and 12.2.2 schemas. The ETRM documentation classifies it as an interim table of statement header information. It acts as a short-lived staging area used by the Receivables statement generation program (typically the "Print Statements" concurrent process) to assemble customer statement headers before the final statement output is formatted and printed. Rows are populated during a statement run, consumed by the statement formatting logic, and subsequently purged, which is why the table is described as interim rather than as a persistent transactional store.

From a heuristic Data Vault modeling perspective, the mined FK structure suggests a link classification. The table does not serve as a durable hub for a business entity; instead it associates a customer identifier, a send-to address, and a site use at a point in time (the statement date), which is characteristic of a relationship/link record rather than a standalone hub or satellite.

Key Information Stored

The documented physical schema contains 47 columns. The most consequential for understanding and querying the table are:

The composite surrogate primary key is AR_STATEMENT_HEADERS_PK over (SEND_TO_ADDRESS_ID, CUSTOMER_ID). Because the primary key is composed of foreign-key columns rather than a single generated identifier, it functions as a natural/composite business key rather than a true surrogate.

Common Use Cases and Queries

Primary usage is diagnostic and reporting-oriented. Since the table is interim, it is most often queried during or immediately after a statement run to reconcile generated statements, to investigate why a customer received no statement, or to troubleshoot formatting and address issues.

A representative pattern joins the header to its customer and address parents:

SELECT h.customer_id, h.send_to_address_id, h.statement_date, h.currency_code, h.bucket1, h.bucket2, h.bucket3, h.bucket4, h.bucket5, h.total_amount_due FROM ar_statement_headers h WHERE h.request_id = :request_id;

Error investigation uses the diagnostic columns:

SELECT customer_id, send_to_address_id, error_no_send_to, error_no_remit_to, error_no_lines, error_amount_different FROM ar_statement_headers WHERE request_id = :request_id AND (error_no_send_to = 'Y' OR error_no_remit_to = 'Y' OR error_no_lines = 'Y');

Because the table is cleared between runs, any reporting requirement for historical statement data must rely on archived extracts rather than on AR_STATEMENT_HEADERS itself.

Related Objects

  • HZ_CUST_ACCOUNTS — parent of CUSTOMER_ID; supplies customer name and account number.
  • HZ_CUST_ACCT_SITES_ALL — parent of SEND_TO_ADDRESS_ID; supplies the statement mailing address.
  • HZ_CUST_SITE_USES_ALL — parent of SITE_USE_ID; defines the bill-to/ship-to site use context.
  • AR_STATEMENT_LINES (and associated line detail) — the interim counterpart holding individual open items summarized into the header buckets.
  • FND_CONCURRENT_REQUESTS — join via REQUEST_ID to identify the statement run that produced the rows.
  • AR_CUSTOMERS / customer profile objects referenced by CUST_CUSTOMER_PROFILE_ID and SITE_CUSTOMER_PROFILE_ID — drive statement defaults such as minimum amount and interest rate.

Together these objects confirm the table's role as a transient assembly point within the Receivables statement generation flow rather than a permanent system of record.