Search Results hz_cust_profile_classes




Overview
Explore in AI Chat

Overview

HZ_CUST_PROFILE_CLASSES is a Receivables (AR) table owned by the AR schema that stores standard credit profile classes in Oracle E-Business Suite 12.1.1 and 12.2.2. A profile class is a reusable template that groups customer credit, collections, statement, dunning, and interest policies under a single identifier. Individual customer accounts are then assigned to a profile class through the HZ_CUSTOMER_PROFILES table, allowing a single business rule set to govern thousands of customers consistently without maintaining credit parameters at the customer level.

The object is classified in the ETRM as a hub-leaning Data Vault entity, since it holds descriptive business keys and is referenced by dependent transactional and profile satellites. Physically the table is wide: the documented 12.2.2 schema exposes 112 columns, reflecting the breadth of credit and collections functionality that can be standardized within a single profile class.

Key Information Stored

The surrogate primary key is PROFILE_CLASS_ID, defined by the HZ_CUST_PROFILE_CLASSES_PK constraint. A unique index, HZ_CUST_PROFILE_CLASSES_U1, covers the same column and acts as the documented business-key candidate. Surrounding columns include:

Common Use Cases and Queries

The table is most commonly queried to audit credit policy consistency, to report which customers fall under a given profile class, and to troubleshoot why a specific credit check or dunning behavior occurred. A typical three-way join links the class, its aggregate credit amounts, and the assigned customer profiles:

SELECT cpc.name, cpc.credit_checking, cpc.tolerance, cp.customer_id
FROM ar.hz_cust_profile_classes cpc, ar.hz_customer_profiles cp
WHERE cpc.profile_class_id = cp.profile_class_id
AND cpc.status = 'A';

Reporting often aggregates customers by class to confirm uniform assignment, or joins HZ_CUST_PROF_CLASS_AMTS to retrieve the credit limit totals associated with a class. Change-tracking queries use LAST_UPDATE_DATE, CREATED_BY, and LAST_UPDATED_BY to identify recently modified policy templates, which is valuable during audit or period-end close. Because PROFILE_CLASS_ID is the single join key across all dependent tables, most ad-hoc SQL resolves through it.

Related Objects

The FK relationships documented for this object identify the following significant dependencies:

  • HZ_CUSTOMER_PROFILES — references HZ_CUST_PROFILE_CLASSES.PROFILE_CLASS_ID; holds the per-customer profile assignment.
  • HZ_CUSTOMER_PROFILES_M — the multiorg variant of the customer profile table, joining on the same PROFILE_CLASS_ID column.
  • HZ_CUST_PROF_CLASS_AMTS — stores credit limit and currency amounts for each profile class, joined on PROFILE_CLASS_ID.
  • AR_COLLECTORS — referenced through COLLECTOR_ID to source the default collector.
  • AR_AUTOCASH_HIERARCHIES — referenced through AUTOCASH_HIERARCHY_ID for receipt application rules.
  • AR_STATEMENT_CYCLES — referenced through STATEMENT_CYCLE_ID for statement scheduling.

Together these objects form the credit management backbone of Receivables, with HZ_CUST_PROFILE_CLASSES acting as the definable policy hub that customer-level profiles inherit from.