Search Results hz_customer_profiles_pk

Overview

HZ_CUSTOMER_PROFILES is the Oracle Receivables (AR) table that stores credit, collections, and billing profile information for customer accounts and customer account sites. It sits within the Trading Community Architecture (TCA) data model and holds the "credit side" of a customer relationship — the settings that drive credit checking, dunning, statements, interest charges, late charges, and autcash/collection behavior. A single customer account, or a specific site use within that account, can carry one profile record that governs how Receivables treats its transactions.

Because the table's primary key is a surrogate identifier and its columns describe attributes of a referenced account, site use, or party, the heuristic Data Vault classification is satellite-leaning. In Data Vault terms it is best modeled as a satellite hanging off a customer account or party hub, rather than a hub or link in its own right.

Key Information Stored

The table contains 120 documented columns. The most operationally significant include:

• CUST_ACCOUNT_PROFILE_ID — the surrogate primary key, defined by unique index HZ_CUSTOMER_PROFILES_PK and also by HZ_CUSTOMER_PROFILES_U1.
• CUST_ACCOUNT_ID, SITE_USE_ID, PARTY_ID — the business key candidates (uniquely indexed together as HZ_CUSTOMER_PROFILES_U2) that identify the account, site use, and party the profile belongs to.
• STATUS, ACCOUNT_STATUS, CREDIT_HOLD, CREDIT_CHECKING — credit control flags and status.
• CREDIT_RATING, RISK_CODE, CREDIT_CLASSIFICATION — risk classification attributes.
• CREDIT_ANALYST_ID, COLLECTOR_ID — the assigned credit analyst and collector.
• PROFILE_CLASS_ID — the profile class driving defaults and behavior.
• STANDARD_TERMS, OVERRIDE_TERMS, TOLERANCE, DISCOUNT_TERMS — payment terms and tolerances.
• DUNNING_LETTERS, DUNNING_LETTER_SET_ID — dunning configuration.
• INTEREST_CHARGES, INTEREST_PERIOD_DAYS, LATE_CHARGE_TYPE — late charge and interest settings.
• SEND_STATEMENTS, CREDIT_BALANCE_STATEMENTS, STATEMENT_CYCLE_ID — statement generation controls.
• AUTOCASH_HIERARCHY_ID, AUTOMATCH_SET_ID, LOCKBOX_MATCHING_OPTION — automatic receipt matching.

Common Use Cases and Queries

Typical reporting and integration scenarios include identifying customers on credit hold, listing accounts assigned to a given collector, and reconciling statement cycles.

SELECT p.cust_account_id, p.party_id, p.status,
       p.credit_hold, p.credit_rating, p.risk_code
FROM   hz_customer_profiles p
WHERE  p.credit_hold = 'Y';

Joining to the account master to report customer name and account number:

SELECT a.account_number, p.credit_rating, p.collector_id
FROM   hz_customer_profiles p,
       hz_cust_accounts     a
WHERE  p.cust_account_id = a.cust_account_id
AND    p.status = 'A';

Other common uses include feeding dunning and statement processes, extracting credit classification for risk dashboards, and joining to HZ_CUST_PROFILE_AMTS to report per-currency credit limits that complete the profile.

Related Objects

• HZ_CUST_ACCOUNTS — joined via CUST_ACCOUNT_ID; the customer account master.
• HZ_CUST_SITE_USES_ALL — joined via SITE_USE_ID; site-level usage records.
• HZ_PARTIES — joined via PARTY_ID; the underlying party.
• HZ_CUST_PROFILE_CLASSES — joined via PROFILE_CLASS_ID; profile class defaults.
• AR_COLLECTORS — joined via COLLECTOR_ID.
• AR_STATEMENT_CYCLES — joined via STATEMENT_CYCLE_ID.
• AR_AUTOCASH_HIERARCHIES — joined via AUTOCASH_HIERARCHY_ID.
• HZ_CUST_PROFILE_AMTS and HZ_CUST_PROFILE_AMTS_M — child tables referencing CUST_ACCOUNT_PROFILE_ID.