Search Results ar_hcustomer_profile_amounts

Overview

The AR_HCUSTOMER_PROFILE_AMOUNTS view belongs to the Oracle Receivables (AR) module and presents customer profile amount limits for each currency. In Oracle E-Business Suite Release 12.1.1 and 12.2.2, Receivables allows a single customer profile to hold credit, dunning, interest, and statement thresholds that vary by currency. This view exposes those per-currency amount limits in a reporting-friendly format, giving implementers and developers a stable access point for profile-amount data without needing to know the exact physical table layout.

The object is relevant to the user's search term min_statement_amount, which is one of the columns surfaced by the view and represents the minimum statement amount threshold used by the Statements feature. When a customer's activity falls below this amount, Oracle Receivables suppresses the generation of a statement for that currency, avoiding the cost of issuing negligible statements.

The view serves reporting, integration, and diagnostic purposes: it supports custom extracts, ad hoc queries, and interfaces that need customer credit and collections thresholds at the currency level.

Underlying Base Objects

According to the documented view text, AR_HCUSTOMER_PROFILE_AMOUNTS is defined as a simple projection over the base table HZ_CUST_PROFILE_AMTS. The view text selects the full column list from that table, including the primary key CUST_ACCT_PROFILE_AMT_ID, audit columns (CREATED_BY, CREATION_DATE, LAST_UPDATED_BY, LAST_UPDATE_DATE, LAST_UPDATE_LOGIN), the foreign key CUST_ACCOUNT_PROFILE_ID, and the descriptive and amount columns.

Several columns are aliased within the view text to preserve legacy naming compatibility. Specifically, CUST_ACCOUNT_ID is aliased to CUSTOMER_ID and SITE_USE_ID is aliased to CUSTOMER_SITE_USE_ID, reflecting the historical naming conventions used before the migration to the Trading Community Architecture (TCA) HZ_ tables. The view also carries concurrent program context columns (REQUEST_ID, PROGRAM_APPLICATION_ID, PROGRAM_ID, PROGRAM_UPDATE_DATE), descriptive flexfield attribute columns, and JGZZ (global/localization) and GLOBAL flexfield attribute columns.

The ETRM metadata notes that the view is "Not implemented in this database," indicating it may be absent or non-functional in the specific environment sampled; the definition, however, remains authoritative for environments where it is deployed.

Key Columns

• CUST_ACCT_PROFILE_AMT_ID / CUSTOMER_PROFILE_AMOUNT_ID — primary identifier for the per-currency profile amount record.
• CUST_ACCOUNT_PROFILE_ID / CUSTOMER_PROFILE_ID — foreign key linking the amount limit to the parent customer profile.
• CURRENCY_CODE — the currency to which the amounts apply; a profile may have multiple rows, one per currency.
• TRX_CREDIT_LIMIT — credit limit applied per transaction.
• OVERALL_CREDIT_LIMIT — aggregate credit limit across open transactions.
• MIN_DUNNING_AMOUNT, MIN_DUNNING_INVOICE_AMOUNT — minimum balances and invoice amounts eligible for dunning.
• MAX_INTEREST_CHARGE and INTEREST_RATE — parameters controlling late-charge calculations.
• MIN_STATEMENT_AMOUNT — the minimum balance below which a statement is not generated for the currency.
• AUTO_REC_MIN_RECEIPT_AMOUNT — minimum receipt amount used in automatic receipt creation.
• MIN_FC_BALANCE_AMOUNT, MIN_FC_INVOICE_AMOUNT — minimum foreign-currency balance and invoice thresholds.
• CUST_ACCOUNT_ID, SITE_USE_ID — customer and site identifiers (aliased for legacy compatibility).

Common Use Cases and Queries

The view is commonly used to audit customer credit and collections settings, to feed statement generation logic, and to drive extract reports. A typical query listing statement thresholds by customer and currency follows:

SELECT customer_id,
       customer_profile_id,
       currency_code,
       min_statement_amount,
       overall_credit_limit,
       trx_credit_limit
FROM   ar_hcustomer_profile_amounts
WHERE  currency_code = 'USD'
ORDER  BY customer_id;

Another common pattern joins the view to the customer profile header to report on customers whose minimum statement amount exceeds a chosen value, supporting collections policy review. Because the underlying table stores profile amounts under TCA, extracts often join to HZ_CUST_ACCOUNTS and HZ_CUST_ACCT_SITES_ALL via the aliased customer and site identifiers to produce customer-facing reports.