Search Results hz_cust_profile_classes_u1

Overview

AR.HZ_CUST_PROFILE_CLASSES is a foundational Oracle Receivables table that defines reusable customer profile classes—templates that bundle credit, collections, statement, and dunning characteristics shared by a group of customer accounts. Rather than configuring each customer individually, an organization defines a profile class (for example, "Large Independent Retail Stores") once, associates the desired attributes with it, and then assigns customers to that class so each new customer inherits its characteristics. The table resides in the APPS schema under the AR product, uses the APPS_TS_TX_DATA tablespace with PCTFREE 10, and is marked VALID in the ETRM metadata for 12.1.1 and 12.2.2.

From a Data Vault modeling perspective, the mined classification for this object is hub-leaning. The stable business concept is the profile class itself, keyed by a single surrogate identifier with descriptive attributes attached. In a dimensional or Data Vault build, HZ_CUST_PROFILE_CLASSES would most naturally serve as a hub (business key PROFILE_CLASS_ID) with its descriptive credit and collections attributes modeled as a satellite.

Key Information Stored

The table contains 112 documented columns. The most operationally significant are listed below.

• PROFILE_CLASS_ID (NUMBER 15) — surrogate primary key and the column behind unique index HZ_CUST_PROFILE_CLASSES_U1. This is the definitive business-key candidate used by all foreign-key relationships.
• NAME (VARCHAR2 30) — the user-facing name of the profile class.
• STATUS — active/inactive state of the class, controlling whether it is selectable.
• COLLECTOR_ID — foreign key to AR_COLLECTORS; the default collector assigned to the class.
• CREDIT_ANALYST_ID, CREDIT_CHECKING, TOLERANCE, CREDIT_CLASSIFICATION, CREDIT_ITEMS_FLAG — credit control attributes governing limit checking and classification.
• STATEMENT_CYCLE_ID — foreign key to AR_STATEMENT_CYCLES; the billing/statement cycle applied to the class.
• AUTOCASH_HIERARCHY_ID — foreign key to AR_AUTOCASH_HIERARCHIES; the default receipt-matching hierarchy.
• DUNNING_LETTER_SET_ID, DUNNING_LETTERS, COMBINE_DUNNING_LETTERS — dunning letter configuration.
• INTEREST_CHARGES, INTEREST_PERIOD_DAYS, LATE_CHARGE_TYPE, LATE_CHARGE_TERM_ID, LATE_CHARGE_CALCULATION_TRX — late-charge and interest computation settings.
• PAYMENT_GRACE_DAYS, DISCOUNT_GRACE_DAYS, STANDARD_TERMS, OVERRIDE_TERMS, DISCOUNT_TERMS — payment and discount term defaults.
• REVIEW_CYCLE_DAYS, REVIEW_CYCLE, PREV_FUNCTIONAL_CURRENCY (PREF_FUNCTIONAL_CURRENCY) — review scheduling and currency preference.
• AUTO_REC_INCL_DISPUTED_FLAG, DISPUTED_TRANSACTIONS_FLAG, LOCKBOX_MATCHING_OPTION, AUTOMATCH_SET_ID — automatic receipt application behavior.
• ATTRIBUTE1–15, GLOBAL_ATTRIBUTE1–20, GLOBAL_ATTRIBUTE_CATEGORY, and JGZZ_ATTRIBUTE1–15 — the standard flexible/descriptive attribute columns.
• OBJECT_VERSION_NUMBER — optimistic locking column used by the OAF/ADF user interface.

Standard WHO columns (CREATED_BY, CREATION_DATE, LAST_UPDATED_BY, LAST_UPDATE_DATE, LAST_UPDATE_LOGIN) and concurrent program columns (PROGRAM_ID, PROGRAM_APPLICATION_ID, REQUEST_ID, PROGRAM_UPDATE_DATE) provide audit and concurrent-manager traceability.

Common Use Cases and Queries

Typical usage centers on joining profile classes to their assigned customers and resolving the referenced lookup tables. A frequently used pattern lists classes with their collector and statement cycle:

• Reporting: SELECT pc.profile_class_id, pc.name, c.name collector FROM hz_cust_profile_classes pc, ar_collectors c WHERE pc.collector_id = c.collector_id(+);
• Finding active classes: filtering on STATUS = 'A'.
• Auditing credit policy: projecting CREDIT_CHECKING, TOLERANCE, and CREDIT_CLASSIFICATION to verify class-level credit rules.
• Impact analysis: counting how many customers inherit a class via HZ_CUSTOMER_PROFILES.PROFILE_CLASS_ID before modifying it, using a LEFT JOIN aggregate.
• Migration/loading: populating PROFILE_CLASS_ID from a sequence and stamping WHO columns.

Always include the primary key or unique business key (PROFILE_CLASS_ID) in the WHERE clause for point lookups, since HZ_CUST_PROFILE_CLASSES_U1 enforces uniqueness on that column.

Related Objects

Dependency analysis identifies several significant tables related to this hub-leaning object.

• AR_COLLECTORS — referenced by HZ_CUST_PROFILE_CLASSES.COLLECTOR_ID; the default collector for the class.
• AR_STATEMENT_CYCLES — referenced by HZ_CUST_PROFILE_CLASSES.STATEMENT_CYCLE_ID; the statement cycle applied.
• AR_AUTOCASH_HIERARCHIES — referenced by HZ_CUST_PROFILE_CLASSES.AUTOCASH_HIERARCHY_ID; the default AutoCash rule hierarchy.
• HZ_CUSTOMER_PROFILES — references HZ_CUST_PROFILE_CLASSES.PROFILE_CLASS_ID; the per-customer profile instances that inherit class attributes.
• HZ_CUST_PROF_CLASS_AMTS — references HZ_CUST_PROFILE_CLASSES.PROFILE_CLASS_ID; class-level credit amount thresholds.
• HZ_CUSTOMER_PROFILES_M — references HZ_CUST_PROFILE_CLASSES.PROFILE_CLASS_ID; the multi-org (MOAC-aware) customer profile view used by 12.x applications.

These relationships make HZ_CUST_PROFILE_CLASSES the schema anchor through which Receivables credit and collections configuration flows down to individual customer accounts.