Search Results ar_customer_profiles




Overview
Explore in AI Chat

Overview

The AR_CUSTOMER_PROFILES table is a core data object within Oracle E-Business Suite Receivables (AR) module, versions 12.1.1 and 12.2.2. It serves as the central repository for storing and managing a customer's credit profile and financial relationship settings. Each record defines the specific credit, collections, invoicing, and payment rules applicable to a customer, either at the overall customer level or, more granularly, at a specific customer site (ship-to, bill-to). Its primary role is to enforce business policies for credit management, cash application, dunning, and customer communications, directly impacting order management holds, transaction creation, and collections activities.

Key Information Stored

The table's structure links a customer (CUSTOMER_ID) and optionally a site (SITE_USE_ID) to a suite of controlling parameters. The primary identifier is CUSTOMER_PROFILE_ID. Key foreign key columns link to master data that defines business rules: CUSTOMER_PROFILE_CLASS_ID for inheriting default profile settings, COLLECTOR_ID for assigning a collections representative, and DUNNING_LETTER_SET_ID for defining overdue notice sequences. Critical operational controls are managed via links to STATEMENT_CYCLE_ID for statement generation, AUTOCASH_HIERARCHY_ID for payment application rules, and GROUPING_RULE_ID for transaction grouping. The table itself stores the relational pointers to these rules; detailed amount-specific limits, such as credit limits and tolerance percentages, are stored in the related AR_CUSTOMER_PROFILE_AMOUNTS table.

Common Use Cases and Queries

This table is central to credit checking, customer maintenance, and collections reporting. A common operational query retrieves the complete profile for a specific customer and site to evaluate credit during order entry. For reporting, analysts often join this table with RA_CUSTOMERS and RA_SITE_USES_ALL to list all customers assigned to a particular collector or analyze profiles by geographic region. Data fixes may involve updating a profile's COLLECTOR_ID during team reassignments. A typical SQL pattern to fetch active customer profile details is:

  • SELECT acp.customer_profile_id, acp.customer_id, acp.site_use_id, acp.collector_id, acp.credit_hold
  • FROM ar_customer_profiles acp, ra_customers rc
  • WHERE acp.customer_id = rc.customer_id
  • AND rc.status = 'A';

Related Objects

AR_CUSTOMER_PROFILES has extensive relationships within the Receivables schema. It is a child of RA_CUSTOMERS and RA_SITE_USES_ALL. Its configuration is heavily dependent on reference tables: AR_CUSTOMER_PROFILE_CLASSES (source of defaults), AR_COLLECTORS, AR_DUNNING_LETTER_SETS, AR_STATEMENT_CYCLES, AR_AUTOCASH_HIERARCHIES, and RA_GROUPING_RULES. Its most direct child is the AR_CUSTOMER_PROFILE_AMOUNTS table, which holds the quantitative limits associated with each profile. In application logic, key APIs such as ARP_CPAPI_PUB (Customer Profile API) and standard views like AR_CUSTOMER_PROFILES_VL are built upon this base table for data validation and presentation.