Results for “ja_lookup_types”

20 results




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

Overview

JA_LOOKUP_TYPES is a reporting-oriented view owned by the APPS schema within the JA — Asia/Pacific Localizations product family. Its documented purpose is to expose the standard lookup types used for QuickCodes (Oracle EBS "lookups"). The view presents a curated, security-filtered projection of the underlying lookup type repository rather than a physical table, meaning it is read-only and derives its row set entirely from the base lookup objects at query time.

Because the view is restricted to VIEW_APPLICATION_ID = 7000 and applies the FND_GLOBAL security function, it surfaces only the lookup types owned by the Asia/Pacific Localizations application. This makes it a specialized, low-noise access path for developers, integrators, and reporting tools that need to enumerate the QuickCode lookup types relevant to JA localizations without scanning the global FND_LOOKUP_TYPES repository. Like other EBS lookup views, it is a thin, stable interface that abstracts the underlying multilingual and security-group logic of the base lookup tables.

Underlying Base Objects

Documented base objects referenced by JA_LOOKUP_TYPES are FND_LOOKUP_TYPES_VL (VIEW) and the FND_GLOBAL (PACKAGE). The view definition selects from FND_LOOKUP_TYPES_VL VL, applying two predicates: VL.VIEW_APPLICATION_ID = 7000 and SECURITY_GROUP_ID = FND_GLOBAL.LOOKUP_SECURITY_GROUP(VL.LOOKUP_TYPE, VL.VIEW_APPLICATION_ID).

  • FND_LOOKUP_TYPES_VL — the base multilingual view providing lookup type rows, translated meanings, and descriptive text; JA_LOOKUP_TYPES projects a subset of its columns.
  • FND_GLOBAL — the standard EBS global utility package whose LOOKUP_SECURITY_GROUP function resolves the caller's lookup security group at runtime, enforcing row-level security.
  • VIEW_APPLICATION_ID = 7000 — the application identifier for Asia/Pacific Localizations, which constrains the result set to JA-owned lookup types.

Key Columns

The view exposes the following columns, several of which come directly from the FND_LOOKUP_TYPES_VL projection. Documented columns include LOOKUP_TYPE, LAST_UPDATE_DATE, LAST_UPDATED_BY, CREATION_DATE, CREATED_BY, LAST_UPDATE_LOGIN, USER_MAINTAINABLE_FLAG, MEANING, and DESCRIPTION.

  • LOOKUP_TYPE — the internal name of the lookup type; the primary identifier for each QuickCode set.
  • MEANING / DESCRIPTION — the translated, user-facing label and descriptive text for the lookup type.
  • USER_MAINTAINABLE_FLAG — indicates whether users may extend or maintain values for the lookup type, distinguishing Oracle-seeded (system) lookup types from those that are user-maintainable.
  • CREATION_DATE / CREATED_BY / LAST_UPDATE_DATE / LAST_UPDATED_BY / LAST_UPDATE_LOGIN — standard EBS audit columns recording who created and last modified the row and when.
  • CUSTOMIZATION_LEVEL — the extensibility/customization setting governing how the lookup type may be modified.

Common Use Cases and Queries

The view is most often used to inventory available QuickCode lookup types for the Asia/Pacific Localizations product and to drive dynamic list-of-values or integration mappings. A frequent need is to list only user-maintainable lookup types, which aligns directly with the search term "user_maintainable_flag."

Sample queries:

  • Enumerate all JA lookup types
SELECT LOOKUP_TYPE, MEANING, DESCRIPTION,
       USER_MAINTAINABLE_FLAG
  FROM APPS.JA_LOOKUP_TYPES
 ORDER BY LOOKUP_TYPE;
  • Filter to user-maintainable lookup types
SELECT LOOKUP_TYPE, MEANING, DESCRIPTION
  FROM APPS.JA_LOOKUP_TYPES
 WHERE USER_MAINTAINABLE_FLAG = 'Y'
 ORDER BY MEANING;
  • Identify recently modified lookup types for audit purposes
SELECT LOOKUP_TYPE, LAST_UPDATED_BY, LAST_UPDATE_DATE
  FROM APPS.JA_LOOKUP_TYPES
 ORDER BY LAST_UPDATE_DATE DESC;

These queries are read-only and safe for reporting. Because row visibility depends on FND_GLOBAL.LOOKUP_SECURITY_GROUP, results reflect the security group of the connected user; integrations and reports should therefore be run under an appropriately privileged account to ensure the intended lookup types are returned.