Search Results ar_hcustomer_profiles

Overview

AR_HCUSTOMER_PROFILES is a backward-compatibility view in the Oracle E-Business Suite Receivables (AR) module that exposes customer credit profile information. The "H" prefix indicates a historical or compatibility view, retained so that older customizations, reports, and integrations written against the legacy AR_CUSTOMER_PROFILES schema continue to function after the underlying data model was migrated to the trading community architecture (TCA) model in Release 11i and later. For Oracle EBS 12.1.1 and 12.2.2, the view presents a denormalized projection of customer credit attributes — credit checking, credit limits, credit ratings, risk codes, dunning and statement configuration, and collector assignments — keyed at the customer account and site-use level.

For users searching on credit_rating, the view is significant because it exposes the CREDIT_RATING column, the alpha-numeric code that classifies a customer's creditworthiness for credit management and review workflows. The view therefore plays a role in credit-oriented reporting, collections analysis, and integrations that need to read or reconcile credit profile attributes without querying the newer TCA base tables directly.

Underlying Base Objects

The ETRM metadata for this view documents no referenced base objects under "Referenced base objects: none documented," and states "Not implemented in this database" under Implementation/DBA Data. This means the view definition is registered in the ETRM reference documentation but is not necessarily deployed in every environment; its presence depends on whether legacy compatibility objects were created during installation or upgrade.

Based on the documented view text, the view is defined over the credit profile entity in Receivables. The primary key column is CUST_ACCOUNT_PROFILE_ID, exposed with the legacy alias CUSTOMER_PROFILE_ID, and the customer identifier is CUST_ACCOUNT_ID, exposed as CUSTOMER_ID. These aliases confirm the view's role as a compatibility layer translating the earlier CUSTOMER_PROFILES structure to the current CUST_ACCOUNT_PROFILES columns. Several columns in the SELECT list are explicitly stubbed as NULL or TO_NUMBER(NULL) — including CREDIT_LIMIT_EXPIRATION_DATE, REVIEW_CYCLE_DAYS, OUTSIDE_REPORTING, UNIQUE_TERMS, AUTO_DUNNING_DAYS, COMBINE_DUNNING_LETTERS, and PRIMARY_AUTO_CASH_METHOD — each annotated "(NO LONGER USED)." These placeholders preserve column positions for legacy consumers while the underlying attributes have been obsoleted.

Key Columns

• CUST_ACCOUNT_PROFILE_ID (alias CUSTOMER_PROFILE_ID) — unique identifier of the customer profile record; the view's primary key.
• CUST_ACCOUNT_ID (alias CUSTOMER_ID) — the customer account to which the credit profile belongs.
• SITE_USE_ID — the site-use level at which the profile applies, supporting account-level and site-level credit settings.
• CREDIT_RATING — the credit rating code assigned to the customer, central to credit review and risk assessment.
• RISK_CODE — the associated risk classification used with credit rating in credit management.
• CREDIT_CHECKING, CREDIT_HOLD, TOLERANCE — control whether credit checking is enforced, whether the account is on credit hold, and the tolerance permitted.
• COLLECTOR_ID — the collector responsible for the account.
• DUNNING_LETTERS, DUNNING_LETTER_SET_ID, INTEREST_CHARGES, INTEREST_PERIOD_DAYS, SEND_STATEMENTS, STATEMENT_CYCLE_ID — collections and statement configuration attributes.
• ACCOUNT_STATUS, PERCENT_COLLECTABLE — status and collectability percentage for credit and collections analysis.
• ATTRIBUTE1–15, GLOBAL_ATTRIBUTE1–5, JGZZ_ATTRIBUTE1–15 — descriptive flexfield and globalization (JGZZ) columns for region-specific extensions.

Common Use Cases and Queries

The view is typically queried for credit exposure reporting, collections dashboards, and migrations or reconciliations that depend on legacy column names. A common query retrieves credit rating and risk code by customer account:

• SELECT customer_id, cust_account_profile_id, credit_rating, risk_code, credit_checking, credit_hold FROM ar_hcustomer_profiles WHERE credit_rating = 'A';
• Listing all profiles on credit hold with their collector and site: SELECT customer_id, site_use_id, collector_id, account_status FROM ar_hcustomer_profiles WHERE credit_hold = 'Y';
• Joining to customers to obtain names alongside credit attributes: SELECT c.customer_name, p.credit_rating, p.risk_code FROM ar_hcustomer_profiles p, hz_cust_accounts c WHERE p.customer_id = c.cust_account_id;
• Profiling statement and dunning configuration: SELECT customer_id, dunning_letter_set_id, statement_cycle_id, send_statements FROM ar_hcustomer_profiles WHERE send_statements = 'Y';

Because the view is a compatibility object and several columns are non-functional placeholders, new development should prefer the current TCA-based credit profile tables, treating AR_HCUSTOMER_PROFILES as a read-only bridge for legacy code.