Results for “ar_addr_categories_active_v”

16 results




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

Overview

AR_ADDR_CATEGORIES_ACTIVE_V is a read-only database view owned by the APPS schema in Oracle E-Business Suite Releases 12.1.1 and 12.2.2. It is delivered as part of the Oracle Receivables (AR) product and exposes the subset of Receivables lookup values that represent currently active address categories. Address categories are the user-defined classifications — commonly examples such as Bill To, Ship To, Statement To, or Dunning To — that determine the business purpose of an address recorded against a customer or site.

The view is a filtered projection of the AR_LOOKUPS table. Rather than presenting every seeded and user-defined lookup, it restricts output to rows where LOOKUP_TYPE equals 'ADDRESS_CATEGORY' and ENABLED_FLAG equals 'Y', and further constrains the effective date range so that only categories active on the current system date are returned. Because the filtering is embedded in the view definition, the object is frequently used for reporting, validation, and integration where a current list of valid address categories is required without re-implementing the enablement and date logic. The view carries no DML capability; it is intended strictly for query and reference purposes.

Underlying Base Objects

ETRM documentation identifies a single referenced base object: AR_LOOKUPS, itself a view in the APPS schema that resolves to the underlying lookup tables (FND_LOOKUP_TYPES and FND_LOOKUP_VALUES). AR_ADDR_CATEGORIES_ACTIVE_V therefore inherits the standard Oracle Applications lookup architecture, in which a lookup type groups related codes and each code carries a meaning, description, enablement flag, and effective date range.

The relationship is one of direct selection and filtering. The view does not join additional Receivables entities such as customers, sites, or address usage tables; it presents only the lookup definition rows. Consequently, the view answers the question "which address categories are currently valid?" but not "which categories are assigned to a given customer or site." Assignment-level detail resides in other objects, notably the address usage and customer site tables.

Key Columns

  • LOOKUP_CODE — The internal code stored in transactional and setup tables to identify the address category. This is the value referenced by foreign keys elsewhere in Receivables, making it the most important column for joins.
  • MEANING — The user-facing display name of the category. This is the value typically shown in list of values and printed on reports.
  • DESCRIPTION — Optional free-form commentary describing the purpose or usage of the category.

Although not projected as columns, the filters on LOOKUP_TYPE, ENABLED_FLAG, START_DATE_ACTIVE, and END_DATE_ACTIVE govern which rows appear. The view treats a null END_DATE_ACTIVE as "open ended" by substituting the current system date, so categories without an explicit end date remain visible.

Common Use Cases and Queries

Typical uses include populating selection lists in custom concurrent programs, validating inbound interface data before it is written to Receivables interface tables, and driving ad hoc reporting on customer address classifications. A representative query is:

SELECT lookup_code, meaning, description FROM apps.ar_addr_categories_active_v ORDER BY meaning;

To resolve a stored category code to its display name in a report join, the view is used as a lookup dimension:

SELECT v.meaning FROM apps.ar_addr_categories_active_v v WHERE v.lookup_code = :category_code;

Because the enablement and date filters are already applied, callers obtain results consistent with the Receivables list of values without duplicating that logic. Queries should always reference the view through the APPS schema and account for the possibility that a code retired after a transaction was created will no longer appear, which is expected behavior for an "active" view.