Search Results cust_prof_class_amount_id
Overview
The AR_CUST_PROF_CLASS_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 currency-specific credit limit amounts assigned to customer profile classes. Its primary role is to enforce credit management policies by establishing the maximum allowable transaction amounts for customers belonging to a specific profile class, segmented by currency. This granular, multi-currency support is essential for global enterprises managing credit risk across different operating currencies.
Key Information Stored
The table's structure is designed to link a profile class with a currency and its associated limits. The critical columns include the surrogate primary key, CUST_PROF_CLASS_AMOUNT_ID, and the unique composite key formed by CUSTOMER_PROFILE_CLASS_ID and CURRENCY_CODE. This unique constraint ensures that only one set of amount limits can be defined per profile class per currency. The table holds various amount limit columns, which typically include fields such as CREDIT_LIMIT, OVER_LIMIT_AMOUNT, and potentially other transactional ceilings like ORDER_AMOUNT_LIMIT and DUNNING_LIMIT, as defined in the profile class setup. The CURRENCY_CODE column links to the FND_CURRENCIES table to validate currency definitions.
Common Use Cases and Queries
This table is integral to credit checking and customer transaction processing. When a sales order or invoice is created, the system references this table to validate if the transaction amount exceeds the defined credit limit for the customer's profile class in the transaction currency. Common reporting and operational queries involve joining this table with AR_CUSTOMER_PROFILE_CLASSES and FND_CURRENCIES. A typical SQL pattern to review all currency-specific limits for a profile class would be:
- SELECT pc.NAME, ccy.CURRENCY_CODE, amt.CREDIT_LIMIT
- FROM AR_CUST_PROF_CLASS_AMOUNTS amt,
- AR_CUSTOMER_PROFILE_CLASSES pc,
- FND_CURRENCIES ccy
- WHERE amt.CUSTOMER_PROFILE_CLASS_ID = pc.CUSTOMER_PROFILE_CLASS_ID
- AND amt.CURRENCY_CODE = ccy.CURRENCY_CODE
- AND pc.NAME = '&PROFILE_CLASS_NAME';
Administrative use cases include mass updates of credit limits for a specific currency or auditing the configuration of profile class amounts.
Related Objects
The AR_CUST_PROF_CLASS_AMOUNTS table has defined relationships with several key EBS objects. It is a child table to AR_CUSTOMER_PROFILE_CLASSES via the foreign key on CUSTOMER_PROFILE_CLASS_ID, which ties the amounts to a specific profile class definition. It also references FND_CURRENCIES via the CURRENCY_CODE foreign key for currency validation. The table is directly referenced by customer profile assignments (likely via AR_CUSTOMER_PROFILES) and is critical for the credit management APIs and engine within Receivables. Any programmatic creation or update of profile class amount limits would interact with this table, often through standard Oracle APIs.
-
Table: AR_CUST_PROF_CLASS_AMOUNTS
12.2.2
owner:AR, object_type:TABLE, fnd_design_data:AR.AR_CUST_PROF_CLASS_AMOUNTS, object_name:AR_CUST_PROF_CLASS_AMOUNTS, status:VALID, product: AR - Receivables , description: Customer profile class amount limits for each currency , implementation_dba_data: AR.AR_CUST_PROF_CLASS_AMOUNTS ,
-
Table: AR_CUST_PROF_CLASS_AMOUNTS
12.1.1
owner:AR, object_type:TABLE, fnd_design_data:AR.AR_CUST_PROF_CLASS_AMOUNTS, object_name:AR_CUST_PROF_CLASS_AMOUNTS, status:VALID, product: AR - Receivables , description: Customer profile class amount limits for each currency , implementation_dba_data: AR.AR_CUST_PROF_CLASS_AMOUNTS ,
-
View: AR_HCUST_PROF_CLASS_AMOUNTS
12.2.2
product: AR - Receivables , description: Customer profile class amount limits for each currency , implementation_dba_data: Not implemented in this database ,
-
View: AR_HCUST_PROF_CLASS_AMOUNTS
12.1.1
product: AR - Receivables , description: Customer profile class amount limits for each currency , implementation_dba_data: Not implemented in this database ,