Search Results charges_schedule




Overview

APPS.AR_CUST_PROF_CLASS_AMTS is a reporting and integration view in Oracle EBS Receivables (AR) that exposes customer profile class amount and charge configuration data. It is defined in the APPS schema and is closely related to the Oracle Advanced Collections / Receivables credit and collections setup, presenting currency-specific credit limits, minimum overdue balance and overdue invoice rules, interest and penalty charges, and charge schedules associated with a customer profile class. In the context of the Oracle EBS 12.1.1 and 12.2.2 releases, the view is primarily consumed by reporting tools, transactional inquiry forms, and integration interfaces that need to resolve profile-class-level amounts into a single readable projection without directly joining the underlying setup tables.

The view is particularly significant when users search for "charges_schedule." The term maps to the INTEREST_TYPE lookup value CHARGES_SCHEDULE, which the view explicitly decodes to derive the associated interest schedule identifier and schedule name. This makes the view the natural access point for any report or interface that must determine whether a profile class uses a charge schedule for interest and penalty calculation.

Underlying Base Objects

The ETRM metadata documents the following referenced base objects for this view:

The view therefore consolidates a transactional setup table with reference and lookup resolution logic, producing a denormalized, user-oriented result set.

Key Columns

Common Use Cases and Queries

Typical use cases include credit limit reporting, collections setup review, and interfaces that must resolve charge schedule assignment per profile class. A representative query to locate profile classes using a charge schedule is:

  • SELECT profile_class_id, currency_code, interest_type, interest_schedule_id, interest_schedule_name FROM apps.ar_cust_prof_class_amts WHERE interest_type = 'CHARGES_SCHEDULE';

The view is also used to list credit limits by currency and to audit interest and penalty thresholds. Because it joins a maintenance package function for lookup meaning, queries should be treated as read-only reference lookups rather than high-volume transactional extracts.