Search Results hz_customer_profiles




Overview
Explore in AI Chat

Overview

The HZ_CUSTOMER_PROFILES table is a core data object within Oracle E-Business Suite (EBS) Receivables (AR) module, specifically in versions 12.1.1 and 12.2.2. It serves as the central repository for storing and managing credit-related information for customer accounts and their specific sites. Its primary role is to enforce credit policies and manage customer risk by holding attributes that control credit checking, credit limits, payment terms, and dunning activities. This table is integral to the Trading Community Architecture (TCA) model, linking customer profile data directly to the party (HZ_PARTIES), customer account (HZ_CUST_ACCOUNTS), and site use (HZ_CUST_SITE_USES_ALL) entities, thereby enabling granular credit management at both the account and operational site level.

Key Information Stored

The table's structure is designed to capture comprehensive credit profile details. The primary key, CUST_ACCOUNT_PROFILE_ID, uniquely identifies each profile record. Critical foreign keys establish essential relationships: CUST_ACCOUNT_ID links to HZ_CUST_ACCOUNTS, PARTY_ID links to HZ_PARTIES, SITE_USE_ID links to HZ_CUST_SITE_USES_ALL for site-specific profiles, and PROFILE_CLASS_ID links to HZ_CUST_PROFILE_CLASSES for inheriting default values from a profile class. Important data columns include CREDIT_CHECKING (flag to enable credit validation), CREDIT_HOLD (status to place orders on hold), CREDIT_RATING, RISK_CODE, AUTO_REC_INCL_DISPUTE_FLAG (for automatic receipt application), and TAX_PRINTING_OPTION. It also stores financial control parameters like OVERRIDE_TERMS, CREDIT_BALANCE_STATEMENTS, and CONS_INV_FLAG (consolidated invoicing).

Common Use Cases and Queries

This table is central to credit management operations and related reporting. Common use cases include reviewing a customer's credit status before order booking, generating aging reports with credit limit data, and managing credit holds. A typical query to retrieve a customer's primary account-level credit profile would join to the customer account and party tables:

  • SELECT hp.party_name, hca.account_number, hcp.credit_limit, hcp.credit_rating, hcp.credit_hold FROM hz_customer_profiles hcp, hz_cust_accounts hca, hz_parties hp WHERE hcp.cust_account_id = hca.cust_account_id AND hca.party_id = hp.party_id AND hcp.site_use_id IS NULL;

Another frequent scenario involves identifying all site-specific profiles that differ from the account-level defaults, which is crucial for understanding localized credit arrangements. Reporting on customers exceeding a certain percentage of their credit limit also relies heavily on this table.

Related Objects

HZ_CUSTOMER_PROFILES is a nexus within the TCA and Receivables schema. Key related objects, as indicated by its foreign keys, include:

  • HZ_CUST_ACCOUNTS and HZ_PARTIES: Provide the core customer identity.
  • HZ_CUST_SITE_USES_ALL: For associating profiles with specific bill-to or ship-to sites.
  • HZ_CUST_PROFILE_CLASSES: The source for default profile attributes inherited by customer profiles.
  • HZ_CUST_PROFILE_AMTS: A child table that stores currency-specific credit limits and other amounts related to a profile, linked via CUST_ACCOUNT_PROFILE_ID.

From an API perspective, the HZ_CUSTOMER_PROFILE_V2PUB package is the primary public interface for creating, updating, and managing records in this table, ensuring proper validation and business rule enforcement.