Results for “ar_cust_categories_active_v”

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

Overview

AR_CUST_CATEGORIES_ACTIVE_V is a receivables lookup view owned by the APPS schema in Oracle E-Business Suite. Its purpose is to expose the currently valid customer category values defined in Oracle Receivables, so that forms, reports, and custom code can present or validate customer categories without directly filtering the underlying lookup table. The view returns the lookup code, meaning, and description for every customer category lookup that is both enabled and within its active date range at query time.

The ETRM metadata identifies this object as a VIEW with VALID status in the AR - Receivables product, and the documented view text confirms that it is a thin, single-table projection over AR_LOOKUPS. Because the filter compares the system date against the lookup's start and end active dates, the result set is time-sensitive: a category that has expired or has not yet become active will not appear. As the description notes, the object originated in Release 10SC, making it a long-standing part of the Receivables data model that persists in 12.1.1 and 12.2.2.

Underlying Base Objects

The documented base object is AR_LOOKUPS, itself exposed to the APPS schema as a view. AR_CUST_CATEGORIES_ACTIVE_V is defined entirely over that single source and adds no joins. The WHERE clause applies three conditions: LOOKUP_TYPE must equal 'CUSTOMER_CATEGORY', ENABLED_FLAG must equal 'Y', and the current date must fall between the lookup's START_DATE_ACTIVE and its END_DATE_ACTIVE.

Because there is no dependency on customer, site, or transaction tables, the view is inexpensive to query and is safe for use in value sets and list-of-values definitions. It reflects only the seeded or user-defined lookup values that qualify as active customer categories, so changes made to AR_LOOKUPS are immediately visible through the view without any materialization or refresh step.

Key Columns

• LOOKUP_CODE — the internal code stored on transactions and customers to represent the category. This is the value validated and stored by Receivables.
• MEANING — the user-facing label displayed in forms, reports, and lists of values.
• DESCRIPTION — the longer, optional explanatory text attached to the lookup, useful in reporting where a fuller definition of the category is required.

Common Use Cases and Queries

Typical uses include populating a customer category list of values, driving category-based aging or sales analysis, and validating category values in inbound interfaces. The following query lists all active customer categories:

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

To resolve the descriptive name for a stored code, the view can be joined or subqueried against the customer tables:

• SELECT c.customer_name, v.meaning FROM apps.ar_customers c, apps.ar_cust_categories_active_v v WHERE v.lookup_code = c.category_code;

For aggregate reporting, a category-level count or balance summary can be built by grouping on lookup_code and selecting the meaning for presentation. Because the view already applies the enabled and date-range filters, reports built on it automatically exclude inactive or expired categories, which keeps historical and current reporting consistent with the values Receivables itself would accept.