Search Results override_terms




Overview
Explore in AI Chat

Overview

AR_HCUSTOMER_PROFILE_CLASSES is a Receivables (AR) view that exposes customer profile class information. Customer profile classes are the primary grouping mechanism used in Oracle EBS Receivables to control credit, collections, dunning, statements, and interest behavior at the customer level. Rather than defining every credit and collections attribute individually on each customer, Oracle allows customers to be assigned to a profile class, which then drives the default values and processing rules applied during credit checking, dunning, statements, and interest calculation.

The view presents the complete set of configurable profile class attributes, including credit checking settings, tolerance, discount terms, dunning letter configuration, statement options, interest charge definitions, payment and discount grace periods, AutoCash hierarchy, tax printing, and charge-on-finance-charge behavior. Because Oracle's documented ETRM metadata for this object specifies that it is not implemented in this database, the view is not a physical object in a standard deployment; it is documented as view text for reference and reporting purposes. This makes it useful for understanding the canonical column set exposed by profile class data and for building queries where the underlying implementation is available.

The view plays a role in reporting and integration scenarios where profile class attributes must be exposed in a flattened, readable form, for example in credit management reports, collections dashboards, and data migration or conversion extracts.

Underlying Base Objects

The provided ETRM metadata documents no referenced base objects for this view, and the view is explicitly noted as not implemented in the database. In standard Oracle Receivables, customer profile class data is stored in the base table AR_CUSTOMER_PROFILE_CLASSES (and its associated _TL translation table for name and description values), with supporting lookups referencing dunning letter sets, statement cycles, AutoCash hierarchies, and grouping rules. The view text supplied in the ETRM metadata is effectively a projection of the base table columns, including several columns that are marked as no longer used (for example, UNIQUE_TERMS and PRIMARY_AUTO_CASH_METHOD, both returned as NULL literals). Because no base objects are documented in the ETRM record, the view should be treated as a reference definition rather than a guaranteed queryable object in every environment.

Key Columns

Common Use Cases and Queries

Typical uses of this view include credit review reporting, collections configuration validation, and integration extracts that must expose profile class attributes. A common query is to retrieve the review cycle and credit settings for each active profile class:

  • Credit review reporting: SELECT profile_class_id, name, credit_checking, tolerance, review_cycle_days FROM ar_hcustomer_profile_classes WHERE status = 'A';
  • Dunning and statements configuration: SELECT name, dunning_letters, dunning_letter_set_id, statements, statement_cycle_id FROM ar_hcustomer_profile_classes;
  • Interest and grace period analysis: SELECT name, interest_charges, interest_period_days, payment_grace_days, discount_grace_days FROM ar_hcustomer_profile_classes;

Because the ETRM metadata documents the object as not implemented, verify object availability in the target environment before relying on the view in custom reports or integrations, and prefer the underlying AR_CUSTOMER_PROFILE_CLASSES base table where the view is absent.