Results for “ap_lookup_types”

32 results




Overview
Explore in AI Chat

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

Overview

AP_LOOKUP_TYPES is a read-only view owned by the APPS schema in Oracle E-Business Suite, defined in the Payables (AP) product. It exposes a filtered subset of the Oracle Application Object Library lookup type definitions maintained in FND_LOOKUP_TYPES_VL. Specifically, the view restricts its result set to lookup types belonging to the application with VIEW_APPLICATION_ID equal to 200, which corresponds to the Payables application. Its purpose is to give developers, reports, and integrations a stable, Payables-scoped entry point to the set of lookup types that code lists and descriptive flexfield validation in the Payables module depend on.

For users searching on the identifier fnd_lookup_types_vl, this object is the materialized, product-specific projection of that base table: rather than querying the full repository of lookup types across all applications, a developer working within Payables queries AP_LOOKUP_TYPES and receives only the lookup types relevant to that module, together with a decoded flag indicating whether users may maintain them at runtime.

Underlying Base Objects

The view is defined over two documented objects. The first is FND_LOOKUP_TYPES_VL, the translatable (VL) view in the Application Object Library that holds lookup type definitions with language-dependent descriptions. The second is FND_GLOBAL, the standard Oracle EBS package supplying session context, most notably the LOOKUP_SECURITY_GROUP function used in the view predicate. The view's SQL text is:

Two filters thereby govern the result: the fixed application scope (200, Payables) and a security-group match enforced through FND_GLOBAL.LOOKUP_SECURITY_GROUP, which ensures that rows are only returned for lookup types the current session is authorized to see. The STATUS in ETRM is VALID, and the underlying FND_LOOKUP_TYPES_VL rows are backed by the FND_LOOKUP_TYPES base table with its translation layer.

Key Columns

The view exposes eight columns, all inherited from FND_LOOKUP_TYPES_VL and transformed as follows:

  • LOOKUP_TYPE — the internal, unique identifier of the lookup type (for example, PAYMENT_METHOD or TERMS). Primary key component used in application logic.
  • DESCRIPTION — the user-facing, translatable description of the lookup type.
  • USER_UPDATABLE_FLAG — a decoded value derived from CUSTOMIZATION_LEVEL: 'Y' when customization level is 'E' (extensible, i.e., users may add lookup values), otherwise 'N'.
  • CREATED_BY — the user who created the lookup type record.
  • CREATION_DATE — creation timestamp.
  • LAST_UPDATED_BY — the user who last modified the record.
  • LAST_UPDATE_DATE — last modification timestamp, commonly used for incremental extracts.
  • LAST_UPDATE_LOGIN — login identifier associated with the last update, useful for audit and concurrency analysis.

Common Use Cases and Queries

The view is typically used to enumerate Payables lookup types, to drive report parameters, and to validate incoming interface data. A basic listing of all Payables lookup types is:

  • SELECT lookup_type, description, user_updatable_flag FROM apps.ap_lookup_types ORDER BY lookup_type;

To find only those lookup types that are user-extensible in a given environment:

  • SELECT lookup_type, description FROM apps.ap_lookup_types WHERE user_updatable_flag = 'Y' ORDER BY 1;

For incremental synchronization into a downstream system, the audit columns provide a watermark:

  • SELECT lookup_type, description, last_update_date FROM apps.ap_lookup_types WHERE last_update_date >= :p_since;

Because the view is filtered by FND_GLOBAL.LOOKUP_SECURITY_GROUP, results honor the caller's session security context; queries should therefore be run with the correct responsibility and application context initialized. Note that this view supplies lookup type headers only. To retrieve the associated lookup values (codes and meanings), join to the corresponding value view keyed on lookup_type, since AP_LOOKUP_TYPES does not expose code, meaning, or tag columns.