Results for “ar_customer_classes_active_v”

AI-generated from documented ETRM metadata — verify critical details on the linked pages.

Overview

AR_CUSTOMER_CLASSES_ACTIVE_V is a read-only view owned by the APPS schema in Oracle E-Business Suite Receivables. It exposes the subset of Receivables lookup values that belong to the lookup type 'CUSTOMER CLASS' and are currently active. In practical terms, the view presents the list of customer class codes that a user can assign to a customer or customer site at a given point in time, already filtered for enabled status and effective date range.

The object is documented in ETRM as originating in Release 10SC. In Oracle EBS 12.1.1 and 12.2.2 the view remains present and valid in the APPS schema, with AR_LOOKUPS (itself a view) recorded as the referenced base object. Because customer classes are implemented through the standard lookup mechanism rather than a dedicated table, this view provides a stable, self-filtering interface for reports, concurrent programs, and custom extensions that need the current list of assignable customer classes without re-implementing the lookup and date logic.

The view is intended for query access only. It carries no DML capability, and its output reflects the state of the underlying lookup rows at the moment of query execution.

Underlying Base Objects

The view is defined entirely over AR_LOOKUPS, the Receivables lookup repository. Its defining query is:

• AR_LOOKUPS (LOOK) — source of all lookup rows. The view restricts this set to LOOKUP_TYPE = 'CUSTOMER CLASS'.

Three predicates are applied to the AR_LOOKUPS rows:

• LOOKUP_TYPE = 'CUSTOMER CLASS' — isolates customer class lookups from all other Receivables lookup types.
• ENABLED_FLAG = 'Y' — returns only lookups that have not been disabled.
• TRUNC(SYSDATE) BETWEEN TRUNC(START_DATE_ACTIVE) AND NVL(TRUNC(END_DATE_ACTIVE), SYSDATE) — enforces the active date window, treating a null end date as open-ended.

Because the date predicate is evaluated at runtime, the view is date-sensitive: a customer class lookup whose active window has not yet opened, or has already closed, is automatically excluded from the result set. Administrators maintaining customer classes therefore do so through the standard Receivables lookup maintenance path against AR_LOOKUPS; the view reflects those changes immediately.

Key Columns

The view projects exactly three columns, all inherited from AR_LOOKUPS:

• LOOKUP_CODE — the stored code for the customer class. This is the value persisted on customer and site records and the value used in joins against customer tables.
• MEANING — the user-facing, translatable description of the customer class, typically displayed on forms, reports, and list of values.
• DESCRIPTION — optional free-text detail associated with the lookup, available when additional explanation of the class is required.

No additional columns, such as internal identifiers or audit fields, are exposed. Consumers requiring those attributes must query AR_LOOKUPS directly.

Common Use Cases and Queries

The view is typically used to populate value lists, drive conditional report logic, and validate customer class values supplied by external systems. A simple listing of active customer classes is:

• SELECT lookup_code, meaning, description FROM apps.ar_customer_classes_active_v ORDER BY meaning;

To validate a specific class before assigning it, or to join the view to customer data for reporting:

• SELECT c.customer_name, c.customer_class_code, v.meaning FROM apps.ar_customers c, apps.ar_customer_classes_active_v v WHERE c.customer_class_code = v.lookup_code;

Because the view excludes disabled and out-of-window lookups, it also serves as a lightweight integrity check when comparing against historical customer records: codes present on customers but absent from the view indicate a class that has since been disabled or has expired. For historical or end-dated requirements, query AR_LOOKUPS directly with the appropriate date criteria.