Results for “as_languages_active_v”

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

Overview

AS_LANGUAGES_ACTIVE_V is a database view owned by the APPS schema in Oracle E-Business Suite (documented in ETRM for both 12.1.1 and 12.2.2). It resides in the AS — Sales Foundation product family and is described in the Oracle documentation as the "Active languages view." Its purpose is to present the subset of language lookup values that are currently enabled, providing a convenient, filter-ready source of valid language codes without requiring callers to apply the ENABLED_FLAG predicate themselves.

In Oracle EBS, language values are not stored in a dedicated language master table for this purpose. Instead, they are maintained as lookup codes within the generic lookups framework, keyed by a specific lookup type. The view abstracts that filtering logic so that reports, concurrent programs, forms, and integration interfaces can retrieve only active languages. Because the view already restricts rows to enabled entries, it is well suited for LOV (List of Values) population, validation routines, and reference-data extraction where inactive or obsolete codes must be excluded. As a read-only view, it carries no maintenance overhead and reflects changes to the underlying lookup data immediately.

Underlying Base Objects

The view is defined over a single documented base object: AS_LOOKUPS, itself identified as a view in the ETRM metadata. The documented view text is a simple projection with a filter:

• Source object: AS_LOOKUPS, aliased as ASLKP.
• Filter conditions: LOOKUP_TYPE = 'LANGUAGE' AND ENABLED_FLAG = 'Y'.
• Projected columns: LOOKUP_CODE, MEANING, and DESCRIPTION.

Because the view references AS_LOOKUPS, which in turn resolves to the FND_LOOKUP_VALUES foundation, any change to a language lookup's enabled flag or translated meaning is reflected through this view. This layered dependency means the view inherits the standard lookup security, translation, and caching behavior of the underlying lookups framework. No base tables are directly joined or aggregated; the definition is intentionally minimal, keeping the view lightweight and predictable.

Key Columns

The view exposes three columns, summarized below:

• LOOKUP_CODE — The stored language code from the lookup (for example, a language identifier such as "US" or "JA"). This is the value typically passed to language-dependent logic or stored on transactional records.
• MEANING — The user-facing display name of the language, suitable for list-of-values prompts, report headings, and pick lists.
• DESCRIPTION — The longer descriptive text associated with the language lookup, available for tooltips, help text, or secondary display.

All three columns originate directly from AS_LOOKUPS. The ENABLED_FLAG and LOOKUP_TYPE columns are consumed by the view's WHERE clause and are not exposed, so every row returned is guaranteed to be an active language.

Common Use Cases and Queries

Typical scenarios include populating a language LOV in a custom Sales Foundation screen, producing a reference list for a concurrent report, and validating a submitted language code before insert. A basic query returns all active languages:

• SELECT LOOKUP_CODE, MEANING, DESCRIPTION FROM APPS.AS_LANGUAGES_ACTIVE_V;
• Resolving a display name: join the view on LOOKUP_CODE to translate a stored code into its MEANING for reporting output.
• Validation: query the view with a WHERE LOOKUP_CODE = :code predicate to confirm that a proposed language is active before accepting it.

Because the view is already filtered, it should be preferred over querying AS_LOOKUPS directly whenever only active languages are needed, reducing the risk of presenting disabled codes and simplifying application SQL.