Search Results ar_customer_profile_amounts




Overview
Explore in AI Chat

Overview

The AR_CUSTOMER_PROFILE_AMOUNTS 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. It serves as the central repository for defining and storing customer-specific credit and risk management limits that are denominated in specific currencies. Its primary role is to enforce financial controls by maintaining detailed transaction amount ceilings—such as order and credit limits—for individual customers, their assigned profiles, specific customer sites, and across different currencies. This granular, currency-aware storage is essential for multinational organizations managing credit exposure in multiple legal tenders.

Key Information Stored

The table's structure is designed to link a financial limit to a specific currency and a specific customer context. The primary key is the system-generated CUSTOMER_PROFILE_AMOUNT_ID. Critical foreign key columns establish the necessary relationships: CUSTOMER_PROFILE_ID links to AR_CUSTOMER_PROFILES for profile-level defaults; CUSTOMER_ID links directly to RA_CUSTOMERS for customer-specific overrides; and CUSTOMER_SITE_USE_ID links to RA_SITE_USES_ALL for site-level overrides. The CURRENCY_CODE column, linked to FND_CURRENCIES, dictates the currency of the associated amount limit fields. While the specific limit columns (e.g., CREDIT_LIMIT, ORDER_LIMIT) are not detailed in the provided metadata, the table's description confirms it holds the actual "amount limits" for each defined currency context.

Common Use Cases and Queries

This table is pivotal in credit checking processes during order entry and invoicing. A common operational query involves retrieving the effective credit limit for a customer and site in a transaction's currency to authorize an order. For reporting, analysts frequently aggregate data from this table to analyze credit utilization and exposure by currency or customer segment. A typical SQL pattern for auditing would join to related customer and currency tables:

  • SELECT cust.customer_name, site.location, curr.name, amt.credit_limit
  • FROM ar_customer_profile_amounts amt
  • JOIN ra_customers cust ON amt.customer_id = cust.customer_id
  • JOIN ra_site_uses_all site ON amt.customer_site_use_id = site.site_use_id
  • JOIN fnd_currencies curr ON amt.currency_code = curr.currency_code
  • WHERE amt.customer_profile_id = :p_profile_id;

Data maintenance is typically performed via the Oracle Receivables "Customer Profiles" and "Credit Management" forms, which provide the application logic for hierarchy and precedence between profile, customer, and site-level amounts.

Related Objects

The table maintains defined foreign key relationships with several fundamental EBS tables, as documented in the ETRM metadata. These relationships are crucial for data integrity and application functionality:

  • AR_CUSTOMER_PROFILES: Joined via CUSTOMER_PROFILE_ID. This links the currency-specific amounts to a master customer profile definition.
  • RA_CUSTOMERS: Joined via CUSTOMER_ID. This allows for customer-level overrides of profile amount limits.
  • RA_SITE_USES_ALL: Joined via CUSTOMER_SITE_USE_ID. This enables the most granular level of control, setting amount limits for specific customer ship-to or bill-to sites.
  • FND_CURRENCIES: Joined via CURRENCY_CODE. This validates the currency and provides descriptive information for the amount limits.

These relationships create a flexible hierarchy where a limit defined at the site-use level for a specific currency takes precedence over a customer-level limit, which in turn overrides a profile-level default.