Results for “ar_customer_profiles”

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

Overview

AR_CUSTOMER_PROFILES is the Oracle Receivables table that stores credit and collections profile information for customers and their business purposes (site uses). It is owned by the AR schema and resides in the Receivables module, and its documented purpose is customer credit information. The table is flagged as VALID in the ETRM 12.2.2 metadata and carries 105 columns, reflecting the broad functional surface of credit management: credit checking, dunning, statements, interest charges, automatic cash application, and collections assignment.

Functionally, the table acts as the operational container that binds a customer to the rules Oracle Receivables applies when processing that customer's transactions. A single customer may hold multiple profile rows, one per site use, which permits different credit limits, collectors, and statement cycles across separate operating locations. Because the FK structure places the table as a dependent of RA_CUSTOMERS, RA_SITE_USES_ALL, and a series of configuration tables, the heuristic Data Vault classification of satellite-leaning is appropriate: AR_CUSTOMER_PROFILES behaves as a descriptive satellite attached to customer and site-use hubs, with each profile row capturing mutable credit attributes over time. In ETRM 12.1.1 and 12.2.2 the table definition is consistent, with only minor column-level differences.

Key Information Stored

The surrogate primary key is CUSTOMER_PROFILE_ID, enforced by AR_CUSTOMER_PROFILES_PK. Two unique indexes act as business-key candidates: AR_CUSTOMER_PROFILES_U1 on CUSTOMER_PROFILE_ID and AR_CUSTOMER_PROFILES_U2 on the CUSTOMER_ID plus SITE_USE_ID combination, which confirms that one profile exists per customer site use. The most significant columns include:

• CUSTOMER_ID — foreign key to RA_CUSTOMERS, identifying the customer the profile governs.
• SITE_USE_ID — foreign key to RA_SITE_USES_ALL, scoping the profile to a specific business purpose or location.
• CUSTOMER_PROFILE_CLASS_ID — foreign key to AR_CUSTOMER_PROFILE_CLASSES, providing the default template from which profile values are derived.
• CREDIT_CHECKING and TOLERANCE — control whether credit checking is enforced and the acceptable overrun percentage.
• CREDIT_LIMIT_EXPIRATION_DATE and REVIEW_CYCLE_DAYS — support periodic credit review workflows.
• CREDIT_HOLD — indicates whether the customer is placed on credit hold.
• COLLECTOR_ID — foreign key to AR_COLLECTORS, assigning the responsible collections agent.
• STATEMENT_CYCLE_ID — foreign key to AR_STATEMENT_CYCLES, driving statement generation timing.
• DUNNING_LETTER_SET_ID and AUTO_DUNNING_DAYS — foreign key to AR_DUNNING_LETTER_SETS and the interval that governs dunning letter output.
• INTEREST_PERIOD_DAYS and PERCENT_COLLECTABLE — drive late charge calculation and provisioning estimates.
• PRIMARY_AUTO_CASH_METHOD, AUTOCASH_HIERARCHY_ID, PAYMENT_GRACE_DAYS, and DISCOUNT_GRACE_DAYS — configure AutoCash behavior.
• GROUPING_RULE_ID — foreign key to RA_GROUPING_RULES, used when consolidating transactions for statements and dunning.
• ACCOUNT_STATUS, RISK_CODE, and CREDIT_RATING — descriptive credit assessment attributes.

The table also carries standard WHO audit columns, the ATTRIBUTE1–15 descriptive flexfield, GLOBAL_ATTRIBUTE1–20 and JGZZ_ATTRIBUTE1–15 localization columns, and concurrent program references such as PROGRAM_ID and REQUEST_ID.

Common Use Cases and Queries

Typical reporting scenarios include locating the credit profile associated with a customer site, auditing customers currently on credit hold, and reviewing profiles nearing credit limit expiration. A simple lookup joins the profile to the customer name:

• SELECT cp.customer_profile_id, cp.customer_id, cp.credit_limit_expiration_date, cp.credit_hold FROM ar_customer_profiles cp WHERE cp.customer_id = :customer_id;
• Collection workload reporting joins AR_COLLECTORS to group profiles by collector and review cycle.
• Statement and dunning configuration audits verify that a valid STATEMENT_CYCLE_ID and DUNNING_LETTER_SET_ID are populated for each active profile.
• Credit exposure analysis combines profile-level tolerance and credit checking with AR_CUSTOMER_PROFILE_AMOUNTS, which references CUSTOMER_PROFILE_ID, to compare authorized limits against aggregated exposure.

Related Objects

The most significant related objects, based on the documented foreign key relationships, are:

• RA_CUSTOMERS — joined on CUSTOMER_ID; the parent customer record.
• RA_SITE_USES_ALL — joined on SITE_USE_ID; scopes the profile to a site use.
• AR_CUSTOMER_PROFILE_CLASSES — joined on CUSTOMER_PROFILE_CLASS_ID; supplies default profile values.
• AR_COLLECTORS — joined on COLLECTOR_ID; identifies the assigned collector.
• AR_STATEMENT_CYCLES — joined on STATEMENT_CYCLE_ID; defines statement timing.
• AR_DUNNING_LETTER_SETS — joined on DUNNING_LETTER_SET_ID; defines dunning letter definitions.
• AR_AUTOCASH_HIERARCHIES — joined on AUTOCASH_HIERARCHY_ID; governs automatic receipt application.
• RA_GROUPING_RULES — joined on GROUPING_RULE_ID; controls transaction grouping for statements and dunning.
• AR_CUSTOMER_PROFILE_AMOUNTS — references CUSTOMER_PROFILE_ID; stores currency-denominated credit limits per profile.

Together these relationships make AR_CUSTOMER_PROFILES the central configuration point for Receivables credit, collections, and cash application processing.