Results for “ar_customer_profile_amounts”

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

Overview

AR_CUSTOMER_PROFILE_AMOUNTS is a Receivables (AR) module table that stores customer profile amount limits expressed on a per-currency basis. In Oracle EBS 12.1.1 and 12.2.2, customer profiles define the credit, collections, dunning, interest, and statement behavior applied to a customer or a customer site. Because monetary thresholds must be interpreted in a specific currency, the profile itself holds only the header-level rule set, while AR_CUSTOMER_PROFILE_AMOUNTS holds the currency-denominated values that drive those rules.

The table is owned by the AR schema and is documented in ETRM 12.2.2 as containing 77 columns. Its primary key, AR_CUSTOMER_PROFILE_AMOUNTS_PK, is defined on CUSTOMER_PROFILE_AMOUNT_ID. A second unique index, AR_CUSTOMER_PROFILE_AMOUNTS_U2, covers CUSTOMER_PROFILE_ID together with CURRENCY_CODE, which establishes the true business key: one amount record per profile per currency. Under the heuristic Data Vault classification mined from the foreign key structure, this object is best modeled as a link, since it resolves associations between a customer profile, a customer, a site use, and a currency.

Key Information Stored

The surrogate primary key is CUSTOMER_PROFILE_AMOUNT_ID, generated via AR_CUSTOMER_PROFILE_AMOUNTS_PK. Business-key uniqueness is enforced by the combination of CUSTOMER_PROFILE_ID and CURRENCY_CODE. The most significant functional columns are:

• TRX_CREDIT_LIMIT — transaction credit limit enforced for the associated profile in the given currency.
• OVERALL_CREDIT_LIMIT — aggregate credit limit across all transactions for the customer or site.
• CURRENCY_CODE — the currency in which all amount thresholds on the row are expressed; foreign key to FND_CURRENCIES.
• CUSTOMER_PROFILE_ID — the parent profile definition; foreign key to AR_CUSTOMER_PROFILES.
• CUSTOMER_ID — the customer to which the amount limits apply; foreign key to RA_CUSTOMERS.
• CUSTOMER_SITE_USE_ID — optional site-level scope; foreign key to RA_SITE_USES_ALL.
• MIN_DUNNING_AMOUNT and MIN_DUNNING_INVOICE_AMOUNT — thresholds below which dunning letters are suppressed.
• MIN_STATEMENT_AMOUNT — minimum balance required before a statement is generated.
• MAX_INTEREST_CHARGE and INTEREST_RATE — caps and rates applied during late charge calculation.
• AUTO_REC_MIN_RECEIPT_AMOUNT — smallest receipt eligible for automatic cash application.
• MIN_FC_BALANCE_AMOUNT and MIN_FC_INVOICE_AMOUNT — minimum foreign-currency balance and invoice amounts.
• ATTRIBUTE1–ATTRIBUTE15, JGZZ_ATTRIBUTE1–15, GLOBAL_ATTRIBUTE1–20 — descriptive flexfield and globalization extension columns.

Audit columns include CREATED_BY, CREATION_DATE, LAST_UPDATED_BY, LAST_UPDATE_DATE, LAST_UPDATE_LOGIN, and the concurrent program context (REQUEST_ID, PROGRAM_APPLICATION_ID, PROGRAM_ID, PROGRAM_UPDATE_DATE).

Common Use Cases and Queries

Typical usage includes verifying currency-specific credit ceilings before releasing orders, troubleshooting why dunning or statements were not produced for a customer, and reporting exposure against limits per currency. A representative query joining the profile header is:

• SELECT a.customer_profile_amount_id, a.customer_id, a.currency_code, a.trx_credit_limit, a.overall_credit_limit FROM ar.ar_customer_profile_amounts a WHERE a.customer_profile_id = :profile_id AND a.currency_code = :currency;
• Credit exposure reporting: join to RA_CUSTOMERS on CUSTOMER_ID and compare OVERALL_CREDIT_LIMIT against open balances by currency.
• Collections analysis: identify profiles where MIN_DUNNING_AMOUNT is set unusually high and correlate with uncollected receivables.
• Site-level validation: filter on CUSTOMER_SITE_USE_ID to confirm currency limits for a specific bill-to or ship-to site.

Related Objects

The following objects are referenced through documented foreign keys and are the most significant for joins and data lineage:

• AR_CUSTOMER_PROFILES — joined via AR_CUSTOMER_PROFILE_AMOUNTS.CUSTOMER_PROFILE_ID; holds the profile header rules.
• RA_CUSTOMERS — joined via AR_CUSTOMER_PROFILE_AMOUNTS.CUSTOMER_ID; the customer owning the limits.
• RA_SITE_USES_ALL — joined via AR_CUSTOMER_PROFILE_AMOUNTS.CUSTOMER_SITE_USE_ID; provides site-level context.
• FND_CURRENCIES — joined via AR_CUSTOMER_PROFILE_AMOUNTS.CURRENCY_CODE; defines currency attributes and precision.

Because the business key pairs CUSTOMER_PROFILE_ID with CURRENCY_CODE, extracts and integrations should always carry both values to avoid duplication or ambiguous matches.