Search Results ar_lookups




Overview
Explore in AI Chat

Overview

AR_LOOKUPS is a read-only view owned by the APPS schema in Oracle E-Business Suite. It presents a product-restricted slice of Oracle Application Object Library (FND) lookup values, exposing only those lookup types registered against the Receivables application (APPLICATION_ID 222) and the Oracle-published security group (SECURITY_GROUP_ID = 0). The view has been available since Release 11.5 and remains VALID in both 12.1.1 and 12.2.2, though its presence in 12.2.x is predominantly maintained for backward compatibility with custom code and seed data supplied by third parties.

In the EBS architecture, lookups provide the code-to-meaning translation layer used throughout the Receivables module — payment terms classifications, receipt methods, autoaccounting types, transaction category maps, and dozens of similar enumerations. Rather than coding joins directly against FND_LOOKUP_VALUES, developers queries AR_LOOKUPS to obtain the Receivables-specific subset with language filtering already applied. The view therefore acts as a stable, product-scoped interface between the generic FND lookup infrastructure and Receivables reporting, concurrent programs, and third-party integrations.

Underlying Base Objects

The single documented base object is FND_LOOKUP_VALUES (referenced through a synonym). The view is defined as follows:

  • Source: FND_LOOKUP_VALUES LV.
  • Filter 1: LV.LANGUAGE = USERENV('LANG') — restricts rows to the session's current language, ensuring meanings are returned in the user's locale.
  • Filter 2: LV.VIEW_APPLICATION_ID = 222 — constrains the result set to the Receivables application.
  • Filter 3: LV.SECURITY_GROUP_ID = 0 — limits to the published (non-secured) lookup values.

All DML against lookup values occurs on FND_LOOKUP_VALUES; AR_LOOKUPS itself is not updatable. Any maintenance of Receivables lookup codes should be performed through the Application Developer responsibility or the Receivables setup forms, not through direct SQL against this view.

Key Columns

Common Use Cases and Queries

Typical uses include validating a receipt method before insert, driving report parameters, and translating stored codes into meanings for dashboard output. Because the LANGUAGE and APPLICATION_ID filters are built in, the view is especially convenient for localized reporting.

Retrieve all currently active Receivables lookups of a given type:

  • SELECT lookup_code, meaning, description FROM apps.ar_lookups WHERE lookup_type = :p_type AND enabled_flag = 'Y' AND TRUNC(SYSDATE) BETWEEN NVL(start_date_active, SYSDATE) AND NVL(end_date_active, SYSDATE);

Translate a transactional value into its meaning:

  • SELECT al.meaning FROM apps.ar_lookups al WHERE al.lookup_type = 'RECEIPT_METHOD' AND al.lookup_code = :p_code;

Populate a value set or LOV with selectable codes:

  • SELECT meaning, lookup_code FROM apps.ar_lookups WHERE lookup_type = 'INV_TRANSACTION_TYPE' AND enabled_flag = 'Y' ORDER BY meaning;

When joining to Receivables transaction or receipt tables, always constrain on LOOKUP_TYPE and enabled_flag to avoid ambiguity, and consider that attribute columns may carry additional product-specific configuration not documented in the base view definition.